Misleading MIBs

Products ePMP
1

ePMPs have many misleading mibs, for istance:

CAMBIUM-PMP80211-MIB::mgmtVLANVID.0 (.1.3.6.1.4.1.17713.21.3.4.4.2.0)
CAMBIUM-PMP80211-MIB::dataVLANVID.0 (.1.3.6.1.4.1.17713.21.3.4.5.2.0)

Both refer to:

2017-04-26_17-14-22.png

Or duplicated MIBs like:

CAMBIUM-PMP80211-MIB::cambiumManagementIFIPAddress.0 (1.3.6.1.4.1.17713.21.1.4.26.0)
CAMBIUM-PMP80211-MIB::mgmtIFIPAddr.0 (.1.3.6.1.4.1.17713.21.3.4.20.6.0)

Can you tell me which oids should I use? Thanks

P.s I'm using release 3.3 with 3.3 Mib files

2

Hi,

First two OIds you have provided don't refer to same parameter on UI.

CAMBIUM-PMP80211-MIB::mgmtVLANVID.0 (.1.3.6.1.4.1.17713.21.3.4.4.2.0)

First OIDs supposed to be used for Management VLAN Configuration.

CAMBIUM-PMP80211-MIB::dataVLANVID.0 (.1.3.6.1.4.1.17713.21.3.4.5.2.0)

Second one supposed to be used for Data VLAN Configuration.

Another two OIDs you aren't duplicates.

One of them is used for Management Interface configuration(read-write) and other is read-only parameter which represent interfaces in ARP table.

Thank you.

3

Thanks for your reply.

@Fedor wrote:

First two OIds you have provided don't refer to same parameter on UI.

CAMBIUM-PMP80211-MIB::mgmtVLANVID.0 (.1.3.6.1.4.1.17713.21.3.4.4.2.0)

First OIDs supposed to be used for Management VLAN Configuration.

CAMBIUM-PMP80211-MIB::dataVLANVID.0 (.1.3.6.1.4.1.17713.21.3.4.5.2.0)
Second one supposed to be used for Data VLAN Configuration.

 In this test (image below), I'm using separate mgmt interface:

2017-04-27_11-19-14.png

In the next step I want to change the Data VLAN, I've set it previously to 999 from the web interface to see which SNMP OIDs are affected. 

snmpset -v 2c -c Canopy 172.16.90.33 .1.3.6.1.4.1.17713.21.3.4.5.2.0 i 33
CAMBIUM-PMP80211-MIB::dataVLANVID.0 = INTEGER: 33

 Then I saved/applied changes:

snmpset -v 2c -c Canopy 172.16.90.33 .1.3.6.1.4.1.17713.21.4.3.0 i 1
CAMBIUM-PMP80211-MIB::cambiumpmp80211ConfigurationSave.0 = INTEGER: 1

snmpset -v 2c -c Canopy 172.16.90.33 .1.3.6.1.4.1.17713.21.4.4.0 i 1

CAMBIUM-PMP80211-MIB::cambiumpmp80211ConfigurationApply.0 = INTEGER: 1

But the radio boot up with the old parameter:

2017-04-27_11-03-59.png

The snmpget shows that the changes has been saved for the Data VLAN:

snmpget -v 2c -c Canopy 172.16.90.33 .1.3.6.1.4.1.17713.21.3.4.5.2.0
CAMBIUM-PMP80211-MIB::dataVLANVID.0 = INTEGER: 33

...I think that the Data VLAN should be set with the mgmtVLANVID.0: 

snmpget -v 2c -c Canopy 172.16.90.33 .1.3.6.1.4.1.17713.21.3.4.4.2.0
CAMBIUM-PMP80211-MIB::mgmtVLANVID.0 = INTEGER: 999
4

Thanks for your reply.

@Fedor wrote:

First two OIds you have provided don't refer to same parameter on UI.

CAMBIUM-PMP80211-MIB::mgmtVLANVID.0 (.1.3.6.1.4.1.17713.21.3.4.4.2.0)

First OIDs supposed to be used for Management VLAN Configuration.

CAMBIUM-PMP80211-MIB::dataVLANVID.0 (.1.3.6.1.4.1.17713.21.3.4.5.2.0)
Second one supposed to be used for Data VLAN Configuration.

 In this test (image below), I'm using separate mgmt interface:

 2017-04-27_11-19-14.png

In the next step I want to change the Data VLAN, I've set it previously to 999 from the web interface to see which SNMP OIDs are affected. 

snmpset -v 2c -c Canopy 172.16.90.33 .1.3.6.1.4.1.17713.21.3.4.5.2.0 i 33
CAMBIUM-PMP80211-MIB::dataVLANVID.0 = INTEGER: 33

 Then I saved/applied changes:

snmpset -v 2c -c Canopy 172.16.90.33 .1.3.6.1.4.1.17713.21.4.3.0 i 1
CAMBIUM-PMP80211-MIB::cambiumpmp80211ConfigurationSave.0 = INTEGER: 1

snmpset -v 2c -c Canopy 172.16.90.33 .1.3.6.1.4.1.17713.21.4.4.0 i 1

CAMBIUM-PMP80211-MIB::cambiumpmp80211ConfigurationApply.0 = INTEGER: 1

But the radio boot up with the old parameter:

 2017-04-27_11-03-59.png

The snmpget shows that the changes has been saved for the Data VLAN:

snmpget -v 2c -c Canopy 172.16.90.33 .1.3.6.1.4.1.17713.21.3.4.5.2.0
CAMBIUM-PMP80211-MIB::dataVLANVID.0 = INTEGER: 33

...I think that the Data VLAN should be set with the mgmtVLANVID.0: 

snmpget -v 2c -c Canopy 172.16.90.33 .1.3.6.1.4.1.17713.21.3.4.4.2.0
CAMBIUM-PMP80211-MIB::mgmtVLANVID.0 = INTEGER: 999
5

Thanks for your reply.

@Fedor wrote:

First two OIds you have provided don't refer to same parameter on UI.

CAMBIUM-PMP80211-MIB::mgmtVLANVID.0 (.1.3.6.1.4.1.17713.21.3.4.4.2.0)

First OIDs supposed to be used for Management VLAN Configuration.

CAMBIUM-PMP80211-MIB::dataVLANVID.0 (.1.3.6.1.4.1.17713.21.3.4.5.2.0)
Second one supposed to be used for Data VLAN Configuration.

 In this test (image below), I'm using separate mgmt interface:

2017-04-27_11-19-14.png

In the next step I want to change the Data VLAN, I've set it previously to 999 from the web interface to see which SNMP OIDs are affected. 

snmpset -v 2c -c Canopy 172.16.90.33 .1.3.6.1.4.1.17713.21.3.4.5.2.0 i 33
CAMBIUM-PMP80211-MIB::dataVLANVID.0 = INTEGER: 33

 Then I saved/applied changes:

snmpset -v 2c -c Canopy 172.16.90.33 .1.3.6.1.4.1.17713.21.4.3.0 i 1
CAMBIUM-PMP80211-MIB::cambiumpmp80211ConfigurationSave.0 = INTEGER: 1

snmpset -v 2c -c Canopy 172.16.90.33 .1.3.6.1.4.1.17713.21.4.4.0 i 1

CAMBIUM-PMP80211-MIB::cambiumpmp80211ConfigurationApply.0 = INTEGER: 1

But the radio boot up with the old parameter (imagelink)

The snmpget shows that the changes has been saved for the Data VLAN:

snmpget -v 2c -c Canopy 172.16.90.33 .1.3.6.1.4.1.17713.21.3.4.5.2.0
CAMBIUM-PMP80211-MIB::dataVLANVID.0 = INTEGER: 33

...I think that the Data VLAN should be set with the mgmtVLANVID.0: 

snmpget -v 2c -c Canopy 172.16.90.33 .1.3.6.1.4.1.17713.21.3.4.4.2.0
CAMBIUM-PMP80211-MIB::mgmtVLANVID.0 = INTEGER: 999
6

Thanks for your reply.

@Fedor wrote:

First two OIds you have provided don't refer to same parameter on UI.

CAMBIUM-PMP80211-MIB::mgmtVLANVID.0 (.1.3.6.1.4.1.17713.21.3.4.4.2.0)

First OIDs supposed to be used for Management VLAN Configuration.

CAMBIUM-PMP80211-MIB::dataVLANVID.0 (.1.3.6.1.4.1.17713.21.3.4.5.2.0)
Second one supposed to be used for Data VLAN Configuration.

 In this test (image), I'm using separate mgmt interface

In the next step I want to change the Data VLAN, I've set it previously to 999 from the web interface to see which SNMP OIDs are affected. 

snmpset -v 2c -c Canopy 172.16.90.33 .1.3.6.1.4.1.17713.21.3.4.5.2.0 i 33
CAMBIUM-PMP80211-MIB::dataVLANVID.0 = INTEGER: 33

 Then I saved/applied changes:

snmpset -v 2c -c Canopy 172.16.90.33 .1.3.6.1.4.1.17713.21.4.3.0 i 1
CAMBIUM-PMP80211-MIB::cambiumpmp80211ConfigurationSave.0 = INTEGER: 1

snmpset -v 2c -c Canopy 172.16.90.33 .1.3.6.1.4.1.17713.21.4.4.0 i 1

CAMBIUM-PMP80211-MIB::cambiumpmp80211ConfigurationApply.0 = INTEGER: 1

But the radio boot up with the old parameter (imagelink)

The snmpget shows that the changes has been saved for the Data VLAN:

snmpget -v 2c -c Canopy 172.16.90.33 .1.3.6.1.4.1.17713.21.3.4.5.2.0
CAMBIUM-PMP80211-MIB::dataVLANVID.0 = INTEGER: 33

...I think that the Data VLAN should be set with the mgmtVLANVID.0: 

snmpget -v 2c -c Canopy 172.16.90.33 .1.3.6.1.4.1.17713.21.3.4.4.2.0
CAMBIUM-PMP80211-MIB::mgmtVLANVID.0 = INTEGER: 999
7

Hi,

Data VLAN OID works properly for me.

Please find CLI output:

snmpget -v 2c -c public localhost .1.3.6.1.4.1.17713.21.3.4.5.2.0                                                                       
.1.3.6.1.4.1.17713.21.3.4.5.2.0 = INTEGER: 99


root@ePMP1000_cd089b:~# snmpset -v 2c -c private localhost .1.3.6.1.4.1.17713.21.3.4.5.2.0 i 100                                                                
.1.3.6.1.4.1.17713.21.3.4.5.2.0 = INTEGER: 100                                  
root@ePMP1000_cd089b:~# snmpset -v 2c -c private localhost 1.3.6.1.4.1.17713.21.4.4.0 i 1                                                                       
.1.3.6.1.4.1.17713.21.4.4.0 = INTEGER: 1     



# snmpget -v 2c -c public localhost .1.3.6.1.4.1.17713.21.3.4.5.2.0                                                                       
.1.3.6.1.4.1.17713.21.3.4.5.2.0 = INTEGER: 100

Please try to use OID for Configuration Apply after parameter configuration.

Thank you.

1 Like