Details

    • Bug
    • Resolution: Unresolved
    • Minor
    • None
    • Professional Edition
    • Web Interface
    • software platform

    Description

      Just upgrade community version with subscription version. I can see all other bandwidth, CPU, Disk graph of BigIP F5 but not showing SSL connection etc. Do i need to do anything on F5 or its configuration issue?

      Please need your help to fix this issue.

      Attachments

        Activity

          [OBS-1861] F5 SSL graph missing

          If i run this command on F5 device i am seeing following:

          [root@f5a:Active:In Sync] ~ # snmpwalk -c public localhost ltmVirtualServAddr
          F5-BIGIP-LOCAL-MIB::ltmVirtualServAddr."/Common/vip1_http" = Hex-STRING: 4A C9 63 78
          F5-BIGIP-LOCAL-MIB::ltmVirtualServAddr."/Common/vip1_https" = Hex-STRING: 4A C9 63 78
          F5-BIGIP-LOCAL-MIB::ltmVirtualServAddr."/Common/vip2_http" = Hex-STRING: 40 5E FD B1
          F5-BIGIP-LOCAL-MIB::ltmVirtualServAddr."/Common/vip2_https" = Hex-STRING: 40 5E FD B1
          F5-BIGIP-LOCAL-MIB::ltmVirtualServAddr."/Common/vip3_http" = STRING: "F*>."
          F5-BIGIP-LOCAL-MIB::ltmVirtualServAddr."/Common/vip3_http" = Hex-STRING: 40 5E FC 13
          F5-BIGIP-LOCAL-MIB::ltmVirtualServAddr."/Common/my_IP_Forwarding__virtual_server" = Hex-STRING: 00 00 00 00

          satish.lx Satish Patel added a comment - If i run this command on F5 device i am seeing following: [root@f5a:Active:In Sync] ~ # snmpwalk -c public localhost ltmVirtualServAddr F5-BIGIP-LOCAL-MIB::ltmVirtualServAddr."/Common/vip1_http" = Hex-STRING: 4A C9 63 78 F5-BIGIP-LOCAL-MIB::ltmVirtualServAddr."/Common/vip1_https" = Hex-STRING: 4A C9 63 78 F5-BIGIP-LOCAL-MIB::ltmVirtualServAddr."/Common/vip2_http" = Hex-STRING: 40 5E FD B1 F5-BIGIP-LOCAL-MIB::ltmVirtualServAddr."/Common/vip2_https" = Hex-STRING: 40 5E FD B1 F5-BIGIP-LOCAL-MIB::ltmVirtualServAddr."/Common/vip3_http" = STRING: "F*>." F5-BIGIP-LOCAL-MIB::ltmVirtualServAddr."/Common/vip3_http" = Hex-STRING: 40 5E FC 13 F5-BIGIP-LOCAL-MIB::ltmVirtualServAddr."/Common/my_IP_Forwarding__virtual_server" = Hex-STRING: 00 00 00 00

          MIBs don't do what you think they do. These errors are caused by your device not returning data for the requested OIDs.

          adama Adam Armstrong added a comment - MIBs don't do what you think they do. These errors are caused by your device not returning data for the requested OIDs.

          Update:

          I have added latest F5 device running 11.6.0 version. It is showing correct device type but look like many missing MIBs. In your base observium you have mibs version 11.5.0, I believe it need 11.6.0 see following screenshot.

          satish.lx Satish Patel added a comment - Update: I have added latest F5 device running 11.6.0 version. It is showing correct device type but look like many missing MIBs. In your base observium you have mibs version 11.5.0, I believe it need 11.6.0 see following screenshot.

          Crap!! My bad

          Whatever F5 i am testing with it has bug (version 11.6.0). - Showing Device type: Linux

          I tried other F5 which is running version (11.6.0 with latest Hotfix). - Showing Device type: F5

          Let me add this device in Observium and pull graphs. I will update you as soon as i see SSL and other F5 stats

          satish.lx Satish Patel added a comment - Crap!! My bad Whatever F5 i am testing with it has bug (version 11.6.0). - Showing Device type: Linux I tried other F5 which is running version (11.6.0 with latest Hotfix). - Showing Device type: F5 Let me add this device in Observium and pull graphs. I will update you as soon as i see SSL and other F5 stats

          DO NOT put foreign MIBs into Observium's MIBs directory.

          To fix this, from inside the Observium directory :

          rm -rf mibs
          svn up

          What is the sysObjectID.0 and sysDescr.0 for these devices?

          Observium's F5 support relies on the sysObjectID being within .1.3.6.1.4.1.3375.2.1.3.4.

          adama Adam Armstrong added a comment - DO NOT put foreign MIBs into Observium's MIBs directory. To fix this, from inside the Observium directory : rm -rf mibs svn up What is the sysObjectID.0 and sysDescr.0 for these devices? Observium's F5 support relies on the sysObjectID being within .1.3.6.1.4.1.3375.2.1.3.4.

          I after digging into more:

          Look like Observium doesn't detecting its F5, it's showing it is Linux box and monitoring standard CPU, DIsk etc.. I thought its missing MIBs so i download and copy all F5 11.6.0 mibs to /var/observium/mibs/f5 directory. still no luck.

          We have many many F5 and if this is not going to work then i am screwed

          satish.lx Satish Patel added a comment - I after digging into more: Look like Observium doesn't detecting its F5, it's showing it is Linux box and monitoring standard CPU, DIsk etc.. I thought its missing MIBs so i download and copy all F5 11.6.0 mibs to /var/observium/mibs/f5 directory. still no luck. We have many many F5 and if this is not going to work then i am screwed

          FYI,

          I did this and using trunk, should i use stable?

          svn co http://svn.observium.org/svn/observium/trunk observium

          satish.lx Satish Patel added a comment - FYI, I did this and using trunk, should i use stable? svn co http://svn.observium.org/svn/observium/trunk observium

          Adam,

          I am opened this issue, I don't know how to report you guys so just label it with "BUG"

          satish.lx Satish Patel added a comment - Adam, I am opened this issue, I don't know how to report you guys so just label it with "BUG"

          People

            adama Adam Armstrong
            satish.lx Satish Patel
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: