Management Center and Reporting

 View Only
  • 1.  Reporter stopped working after ProxySG upgrades

    Posted Oct 20, 2020 04:52 PM
    Hello.

    I currently have a reporter on code version 10.1.5.3 and our proxies were upgraded to ASG 6.7.4.13.  Since the upgrade they have stopped receiving traffic data.  I've tried to restart the reporter but the reporter is not receiving any data anymore.  Do you know if the reporter should be upgraded or do you have any recommendations on how to troubleshoot the connection?


  • 2.  RE: Reporter stopped working after ProxySG upgrades

    Posted Oct 21, 2020 11:02 AM
    I was able to get this working again by restoring to a backup and then loading the database.  I still had a question about upgrading however.  I am unable to upload the newest image file to the reporter on the CLI from management center.  I have already enabled http access and http-proxy isn't enabled.  In addition, the management center is already setup to communicate to the reporter so I don't understand the issue.

    Reporter# installed-systems add http://X.X.X.X:8080/fs/download/7f54a9c8e68f48f69d7fca63c37b6dfd
    "http://X.X.X.X:8080/fs/download/7f54a9c8e68f48f69d7fca63c37b6dfd" is not a valid URL - unable to install image

    Is there something else needed to allow it to pull the file from the management center?


  • 3.  RE: Reporter stopped working after ProxySG upgrades

    Broadcom Employee
    Posted Oct 21, 2020 04:13 PM
    Hi JeMann,

    From a the perspective of coming pulling a file off of Management Center, it appears you are doing all the right things. The things I look out for when accessing a HTTP file on Management Center:

    • enable http access 
      • config(#) security http enable
    • copy the URL of the hosted file
    • replace the https with http, and the port from 8082 to 8080
    and when finished installing file, disable http access 

    At this stage, if you sure nothing is being mistyped in the terminal, I would try and isolate whether this is a hosting on MC issue, or a possible Reporter issue. I would try and load the URL you are giving Reporter into a browser and see if you get a download prompt. If you don't, then you know it is somewhere with MC. If you do, then you are looking more closely at either Reporter, or the connection between the two.

    Also, are you trying to upgrade from 10.1.5.3 directly to 10.5? You will want to at least make a step on 10.3. I would review the release notes for the version specific upgrade information. 

    Hope this helps!





  • 4.  RE: Reporter stopped working after ProxySG upgrades

    Posted Oct 21, 2020 05:07 PM
    Hello Jacob.

    I was able to finally figure this out.  I used a separate local http server to grab the new image.  I already upgraded the reporter but had to re-create the database because the old database would not load.  This might be due to the jump up in code but not sure...  I don't see any data popping up yet but I'm sure the database may need some time to sift through the data and populate.


  • 5.  RE: Reporter stopped working after ProxySG upgrades

    Broadcom Employee
    Posted Oct 22, 2020 05:03 PM
    Reporter 10.1.x is EOL since 2019 the info is on this article https://knowledge.broadcom.com/external/article?legacyId=info5439, Try upgrading the reporter to 10.5.2.2, this is the recommended version. The upgrade steps are on the release notes for 10.5.1.1, in the Broadcom portal download section. The path for this upgrade should be 10.1---10.3.x--10.5.x you could no go directly from 10.1. The path is in the release notes too.


  • 6.  RE: Reporter stopped working after ProxySG upgrades

    Posted Oct 22, 2020 05:10 PM
    I already upgraded the reporter directly to 10.5.2.2 and its been receiving updates from the proxy logs.  I can see data of the traffic on the gui again.


  • 7.  RE: Reporter stopped working after ProxySG upgrades

    Posted Nov 22, 2021 07:21 PM
    Hello!,

    Like JeMann we were presented with the case that the reporter did not show traffic, the solution we found was:

    Disabling Web Application Attribute Perform the following steps in the CLI:

    1. Enter enable
    2. Enter the admin password
    3. Enter stop-reporter
    4. Enter and
    5. Enter configure edit preferences.cfg
    6. Append the following lines to the config file in the specified order: intelligence_services = {web_app_attr_download = "false"} # intelligence_services
    7. Enter configure commit preferences.cfg
    8. Enter start-reporter
    9. Enter y

    The trick was in append the line "intelligence_services" below the line that contains "subscription"

    Thus we recover the GUI and the reporter changed to the "loaded" state. Unfortunately the TCP protocol was broken so we had to change it to the SCP protocol.

    I hope I can help you!