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

Q-BRIDGE-MIB and HPE devices

Details

    • Vendor Bug
    • Resolution: Fixed
    • Trivial
    • None
    • Professional Edition
    • Poller
    • None

    Description

      Hi,

      All HPE devices we own, have their interfaces marked as "dot1Q" even if it is an access port. I think you first need to check if an interface is present in any VLAN in dot1qVlanCurrentUntaggedPorts

      This will return a hex table so some form of conversion needs to be done

      dot1qVlanStaticUntaggedPorts.1354 = "
      3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
      00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
      00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
      00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
      00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "

      3C = 0011 1100
      VLAN 1354 is untagged on port with index 3,4,5,6 (gi-1/0/3-6)

      I have attached pictures that will help describe the case, and a debug (-d -m ports)

      Regards
      Christian

      Attachments

        1. debug.txt
          199 kB
        2. pic1.JPG
          pic1.JPG
          34 kB
        3. pic2.JPG
          pic2.JPG
          16 kB
        4. pic3.JPG
          pic3.JPG
          51 kB
        5. pic4.JPG
          pic4.JPG
          62 kB

        Activity

          [OBS-2987] Q-BRIDGE-MIB and HPE devices
          cheri001 Christian Eriksson added a comment -

          Seems to work fine, many thanks

          cheri001 Christian Eriksson added a comment - Seems to work fine, many thanks
          landy Mike Stupalov added a comment -

          Please try with r9990.

          landy Mike Stupalov added a comment - Please try with r9990.
          cheri001 Christian Eriksson added a comment -

          VLAN 117 is just an example, and in this case port 5-6 is not a member of it

          cheri001 Christian Eriksson added a comment - VLAN 117 is just an example, and in this case port 5-6 is not a member of it
          landy Mike Stupalov added a comment -

          Hrm, in this case:

          .1.3.111.2.802.1.1.4.1.4.2.1.6.0.1.117 = Hex-STRING: F3 FF FE 00
          		 
          .1.3.111.2.802.1.1.4.1.4.2.1.5.0.1.117 = Hex-STRING: F3 FF FF F0

          ports 5,6 in which state?

          landy Mike Stupalov added a comment - Hrm, in this case: .1.3.111.2.802.1.1.4.1.4.2.1.6.0.1.117 = Hex-STRING: F3 FF FE 00 .1.3.111.2.802.1.1.4.1.4.2.1.5.0.1.117 = Hex-STRING: F3 FF FF F0 ports 5,6 in which state?
          cheri001 Christian Eriksson added a comment -

          I mean to say if port exists in..not VLAN 

          "If vlan X exists in dot1qVlanCurrentEgressPorts but not in dot1qVlanCurrentUntaggedPorts it is a trunk
          If vlan X exists in both, it is an access port"

          cheri001 Christian Eriksson added a comment - I mean to say if port exists in..not VLAN  "If vlan X exists in dot1qVlanCurrentEgressPorts but not in dot1qVlanCurrentUntaggedPorts it is a trunk If vlan X exists in both, it is an access port"
          cheri001 Christian Eriksson added a comment -

          Sorry to resurrect this case, but I think you need to check;

          dot1qVlanCurrentEgressPorts contains all ports, tagged and untagged
          dot1qVlanCurrentUntaggedPorts contains only untagged ports

          If vlan X exists in dot1qVlanCurrentEgressPorts but not in dot1qVlanCurrentUntaggedPorts it is a trunk
          If vlan X exists in both, it is an access port

          Below is tagged vlan 3000 on port 25-28
          .1.3.6.1.2.1.17.7.1.4.2.1.4.0.3000 = Hex-STRING: 00 00 01 F0
          .1.3.6.1.2.1.17.7.1.4.2.1.5.0.3000 = Hex-STRING: 00 00 00 00

          Below is vlan 117 tagged on ports 24-28 but also untagged on ports 1-4,7-23
          .1.3.111.2.802.1.1.4.1.4.2.1.6.0.1.117 = Hex-STRING: F3 FF FE 00
          .1.3.111.2.802.1.1.4.1.4.2.1.5.0.1.117 = Hex-STRING: F3 FF FF F0

          This seems to be the case with all HPE gear unfortunately

          Regards
          Christian

          cheri001 Christian Eriksson added a comment - Sorry to resurrect this case, but I think you need to check; dot1qVlanCurrentEgressPorts contains all ports, tagged and untagged dot1qVlanCurrentUntaggedPorts contains only untagged ports If vlan X exists in dot1qVlanCurrentEgressPorts but not in dot1qVlanCurrentUntaggedPorts it is a trunk If vlan X exists in both, it is an access port Below is tagged vlan 3000 on port 25-28 .1.3.6.1.2.1.17.7.1.4.2.1.4.0.3000 = Hex-STRING: 00 00 01 F0 .1.3.6.1.2.1.17.7.1.4.2.1.5.0.3000 = Hex-STRING: 00 00 00 00 Below is vlan 117 tagged on ports 24-28 but also untagged on ports 1-4,7-23 .1.3.111.2.802.1.1.4.1.4.2.1.6.0.1.117 = Hex-STRING: F3 FF FE 00 .1.3.111.2.802.1.1.4.1.4.2.1.5.0.1.117 = Hex-STRING: F3 FF FF F0 This seems to be the case with all HPE gear unfortunately Regards Christian
          cheri001 Christian Eriksson added a comment -

          Nope, not responding at all..
          If there is nothing to be done you can close this

          Regards
          Christian

          cheri001 Christian Eriksson added a comment - Nope, not responding at all.. If there is nothing to be done you can close this Regards Christian
          landy Mike Stupalov added a comment -

          I'm not sure that this MIB/Oids supported (exist) on this platform. On tested by me device (ver 7.1.045) this Oids not exist..

          Can you test your device?:

          snmpwalk -v2c -c <community> <hostname> 1.3.111.2.802.1.1.4.1.4.2.1.5

          landy Mike Stupalov added a comment - I'm not sure that this MIB/Oids supported (exist) on this platform. On tested by me device (ver 7.1.045) this Oids not exist.. Can you test your device?: snmpwalk -v2c -c <community> <hostname> 1.3.111.2.802.1.1.4.1.4.2.1.5

          People

            landy Mike Stupalov
            cheri001 Christian Eriksson
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: