Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-5011

Citrix ADC (NetScaler) GSLB vservers & services

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • None
    • Default
    • None

    Attachments

      1. image-2025-04-16-10-40-02-964.png
        image-2025-04-16-10-40-02-964.png
        12 kB
      2. image-2025-04-16-10-40-39-664.png
        image-2025-04-16-10-40-39-664.png
        11 kB
      3. SomethingWentWrongGSLBvserver.PNG
        SomethingWentWrongGSLBvserver.PNG
        658 kB
      4. TestlbDiscovery.txt
        103 kB
      5. testLBPollDebug.txt
        1.01 MB

      Activity

        [OBS-5011] Citrix ADC (NetScaler) GSLB vservers & services

        Citrix themselves breaks out GSLB into it's own sections in it's own tooling.  So It might make sense for observium to split them from traditional netscaler Virtual Servers, Services, Service groups etc.

        Below screenshots are from Citrix's own netscaler console.

        vs traditional 

        SHGWawa Sam Hernandez-Gill added a comment - Citrix themselves breaks out GSLB into it's own sections in it's own tooling.  So It might make sense for observium to split them from traditional netscaler Virtual Servers, Services, Service groups etc. Below screenshots are from Citrix's own netscaler console. vs traditional 

        Not sure if GSLB vserver's need to be treated differently than regular old vserver's on Citrix Netscalers, but when trying to use the Observium GUI to view one, the application returns the "Oops! Something went wrong. <ScaredHamster>

         

        SHGWawa Sam Hernandez-Gill added a comment - Not sure if GSLB vserver's need to be treated differently than regular old vserver's on Citrix Netscalers, but when trying to use the Observium GUI to view one, the application returns the "Oops! Something went wrong. <ScaredHamster>  

        General questions and device support can be discussed in our Discord channel, click here to join.


        Please make and attach additional information about the device:

        • full snmp dump from device:

          snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
          snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

          If device not support SNMP version 2c, replace -v2c with -v1.

        • If you have problems with discovery or poller processes, please do and attach these debugs:

          ./discovery.php -d -h <device>
          ./poller.php -d -h <device>

        • additionally attach device and/or vendor specific MIB files

        This comment is added automatically.

        bot Observium Bot added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files This comment is added automatically.

        People

          landy Mike Stupalov
          SHGWawa Sam Hernandez-Gill
          Votes:
          0 Vote for this issue
          Watchers:
          2 Start watching this issue

          Dates

            Created:
            Updated: