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

Service-awareness of Nokia 7705/7750 devices - QOS

Details

    Description

      Hi.

      On Nokia devices, an access port with dot1q (or qinq) encapsulation is bound to a service, that contains a SAP with port:vlan or port:vlan.vlan in QinQ mode.

      Could it be possible to detect the service-id, any SAP configured and monitor the sap-ingress and/or sap-egress queues commited to that service access point? 

       

      This would be very handy for visualizing the per-service QOS markings, both for documentation, but also troubleshooting and show-off to executive in an executive summary report. 

      Observium handles this perfectly on network ports, but sometimes the aggregated QOS queues is not whats needed  

       

      Attachments

        1. enos-h.txt
          37.22 MB
          Christoffer Smørås

        Activity

          [OBS-3674] Service-awareness of Nokia 7705/7750 devices - QOS
          Stoffen Christoffer Smørås added a comment -

          SNMPwalk was added at the time of creation.

          Stoffen Christoffer Smørås added a comment - SNMPwalk was added at the time of creation.
          bot Observium Bot added a comment -

          Please make and attach additional information about the device:

          • full snmp dump from device: 

            snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
            		 
            snmpwalk -v2c -c <community>  --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

          Note, this comment is added automatically.

          bot Observium Bot added a comment - Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --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 Note, this comment is added automatically.

          People

            landy Mike Stupalov
            Stoffen Christoffer Smørås
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: