Q-BRIDGE-MIB and HPE devices

Seems to work fine, many thanks

Please try with r9990.

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

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?

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"

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

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

Regards
Christian

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

Hi Mike,

I finally got a response from HPE. Does this help you?

I see following questions in case:

"What MIB do you use when collecting VLAN information (tagged/untagged) on ports? Is it the Q-BRIDGE-MIB? If yes, how do you know if a port is tagged or untagged? What logic goes into this? Because IMC platform seems to know this, but when polling the device with SNMP there is no clear way of knowing this."

 __ 

What MIB do you use when collecting VLAN information (tagged/untagged) on ports? Is it the Q-BRIDGE-MIB?

• Yes, I think IMC is using the standard OIDs like QBridge MIB. To explain it better, I’m sending you the OIDs:

1.3.111.2.802.1.1.4.1.4.2.1.5 (ieee8021QBridgeVlanCurrentEgressPorts)

1.3.111.2.802.1.1.4.1.4.2.1.6 (ieee8021QBridgeVlanCurrentUntaggedPorts)

As you can see both are different and that is explaining if the port is tagged or untagged

And here one another example

1.3.6.1.2.1.17.7.1.4.3.1.4 is dot1qVlanStaticUntaggedPorts, part of dot1qVlanStaticTable, defined in Q-BRIDGE-MIB. If a port is listed by this object, it is untagged. If a port is listed in dot1qVlanStaticEgressPorts, also part of dot1qVlanStaticTable, but not listed in dot1qVlanStaticUntaggedPorts, then it is tagged.

Both dot1qVlanStaticEgressPorts and dot1qVlanStaticUntaggedPorts are of type PortList, also defined in Q-BRIDGE-MIB. Each bit of each octet corresponds to one ifIndex, with the most significant bit of the first octet being ifIndex=1, the next bit being ifIndex=2, and so on. If the bit is 1, it is a member; if it is 0 then it is not.

I found here some more info about this: https://gtacknowledge.extremenetworks.com/articles/Q_A/What-is-the-SNMP-OID-to-know-the-ports-assigned-to-VLANs

Hi Mike,

I think you are right. I will check with HPE support if there is another MIB that can be used to collect this information