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

Add discovery/polling of source NAT utilization on SRX

Details

    • Improvement
    • Resolution: Unresolved
    • Major
    • None
    • Enterprise Edition
    • OS
    • None
    • JunOS SRX

    Description

      Source NAT pools are a resource that can be exhausted and cause service impact. We would like to monitor / alert on them for our SRX firewalls. This is exposed in JUNIPER-JS-NAT-MIB::jnxJsNatIfSrcPoolPortTable:

      SNMP table: JUNIPER-JS-NAT-MIB::jnxJsSrcNatStatsTable jnxJsNatSrcPoolName jnxJsNatSrcXlatedAddrType jnxJsNatSrcPoolType jnxJsNatSrcNumPortInuse jnxJsNatSrcNumSessions jnxJsNatSrcNumPortAvail jnxJsNatSrcNumAddressAvail jnxJsNatSrcNumAddressInuse
      		 
                 test-pool                      ipv4             withPAT                       0                      0                   64512                          1                          1

      On some older devices, the jnxJsNatSrcNumPortAvail jnxJsNatSrcNumAddressAvail jnxJsNatSrcNumAddressInuse OIDs are not available.

      Attachments

        Activity

          [OBS-4303] Add discovery/polling of source NAT utilization on SRX
          bot Observium Bot made changes -
          Status Original: Open [ 1 ] New: Pending Response [ 10000 ]
          Tims Keenan created issue -
          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 -ObentxU <hostname> .1 > myagent.snmpwalk
            		 
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -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 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -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
            Tims Keenan
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: