Get port vlan tag via snmp on HP Procurve

hphp-procurvemonitoringsnmp

I'm trying to write a nagios check that will check if a port is a member of (tagged in) a perticular VLAN.

I've discovered the following SNMP location SNMPv2-SMI::mib-2.17.7.1.4.5.1.1.40 for checking a ports untagged vlan membership. But can't seem to find an equivlent for tagged. I guess since it is a one -> many relationship it may be more complicated.

The switches in question are HP Procurve 2920-48G's

Any hints much appreciated

Thanks
Jona

Best Answer

In the brief research I did, it seems that tagged VLANs are not standardised in SNMP. The HP-VLAN MIB seems to be necessary for this. However, it didn't work for me when I tried walking it on an HP 2810-48G. It may work better for you.

Related Solutions

How to monitor the temperature of a HP Procurve 3500 switch via SNMP

The above OID is specific to the J8162A model of HP switch (not sure what actual model name that is, but that's the switch model ID), which is probably not what the ProCurve 3500YL is.

Only hefty/very large HP ProCurves appear to have actual temperature sensors in them that are wired to return thermistor data (e.g. temperature in Celsius, etc.). Most of them nowadays only return whether or not the sensor data exceeds a pre-defined temperature.

You can find that under the OID tree "hpicfSensorTable", which maps to the following OID base:

1.3.6.1.4.1.11.2.14.11.1.2.6.1

You'll find the ENTITY-MIB (which is a standard and not specific to HP products) entPhysicalVendorType table also useful, except that all the references there refer to you to the HP-specific ones, so it's not of much help. :-)

Regarding the HP-specific ones, here's an example for a ProCurve 2510G-24:

HP-ICF-CHASSIS::hpicfSensorIndex.1 = INTEGER: 1
HP-ICF-CHASSIS::hpicfSensorIndex.2 = INTEGER: 2
HP-ICF-CHASSIS::hpicfSensorIndex.3 = INTEGER: 3
HP-ICF-CHASSIS::hpicfSensorIndex.4 = INTEGER: 4
HP-ICF-CHASSIS::hpicfSensorObjectId.1 = OID: HP-ICF-OID::icfFanSensor
HP-ICF-CHASSIS::hpicfSensorObjectId.2 = OID: HP-ICF-OID::icfPowerSupplySensor
HP-ICF-CHASSIS::hpicfSensorObjectId.3 = OID: HP-ICF-OID::icfPowerSupplySensor
HP-ICF-CHASSIS::hpicfSensorObjectId.4 = OID: HP-ICF-OID::icfTemperatureSensor
HP-ICF-CHASSIS::hpicfSensorNumber.1 = INTEGER: 1
HP-ICF-CHASSIS::hpicfSensorNumber.2 = INTEGER: 1
HP-ICF-CHASSIS::hpicfSensorNumber.3 = INTEGER: 1
HP-ICF-CHASSIS::hpicfSensorNumber.4 = INTEGER: 1
HP-ICF-CHASSIS::hpicfSensorStatus.1 = INTEGER: good(4)
HP-ICF-CHASSIS::hpicfSensorStatus.2 = INTEGER: good(4)
HP-ICF-CHASSIS::hpicfSensorStatus.3 = INTEGER: notPresent(5)
HP-ICF-CHASSIS::hpicfSensorStatus.4 = INTEGER: good(4)
HP-ICF-CHASSIS::hpicfSensorWarnings.1 = Counter32: 0
HP-ICF-CHASSIS::hpicfSensorWarnings.2 = Counter32: 0
HP-ICF-CHASSIS::hpicfSensorWarnings.3 = Counter32: 0
HP-ICF-CHASSIS::hpicfSensorWarnings.4 = Counter32: 0
HP-ICF-CHASSIS::hpicfSensorFailures.1 = Counter32: 0
HP-ICF-CHASSIS::hpicfSensorFailures.2 = Counter32: 0
HP-ICF-CHASSIS::hpicfSensorFailures.3 = Counter32: 0
HP-ICF-CHASSIS::hpicfSensorFailures.4 = Counter32: 0
HP-ICF-CHASSIS::hpicfSensorDescr.1 = STRING: Fan Sensor
HP-ICF-CHASSIS::hpicfSensorDescr.2 = STRING: Power Supply Sensor
HP-ICF-CHASSIS::hpicfSensorDescr.3 = STRING: Redundant Power Supply Sensor
HP-ICF-CHASSIS::hpicfSensorDescr.4 = STRING: Over-temperature Sensor

Security – VLAN security on HP ProCurve 1810G-24

VLANs are no replacement for NAT.

HP ProCurve 1810G-24 is a very nice silent gigabit web-managed L2 switch with VLAN capabilities, SNMP monitoring and more.

You can split the switch into several virtual switches using separate VLANs so that each virtual switch has a virtual port on the physical port of the router.

       VLAN1 VLAN2 VLAN3
Port1    U     T     T
Port2    E     U     E
Port3    E     E     U

Here Port1 is the router, Port2 is Company1, Port3 is Company2, VLAN1 is for network management, VLAN2 and VLAN3 are for the customers.

However you need a router that is capable of having several virtual interfaces for each VLAN and doing NAT for several networks. This is not a stock broadband router.

The router should be capable of accepting traffic with at least 5 different VLAN tags including the default VLAN for the uplink.

Other capabilities to look for in a router for your network:

DHCP server and DHCP relay
Network address translation (NAT)
At least 5 active 802.1Q VLAN tags
Firewall
If a router has an ADSL modem functionality, you could used it to replace the device that installed by your provider.

Best Answer

Related Solutions

How to monitor the temperature of a HP Procurve 3500 switch via SNMP

Security – VLAN security on HP ProCurve 1810G-24

Related Topic