Alcatel-Lucent 9500 MPR

jasonm1975

I am trying to add an Alcatel-Lucent 9500 MPR Microwave Radio to SolarWinds.

It validates as OK, but does not disover any interfaces.

Just curious if anyone reading this post had any success on adding this Microwave Radio to Solarwinds. We have another Alcatel-Lucent product called a 7705 which is new as well and was able to add it with no problem.

Find more posts tagged with

Accepted answers

All comments

bshopp

I am guessing this device does not support the IF-MIB and most likely some proprietary implementation for interface information. Easy way to check is to do a MIB walk of the device or try and walk the IF-MIB to see if you get any results.

jasonm1975

Brandon,

One the the vendor said was for me to try something similiar to this procedure which doesn't make a lot of sence to me but here is what they suggested...

Here are the commands to register TSM server onto MPR9500. I have included the output as well.

Note:

1. the entries will be in the table for 1 year. The will be removed automatically after 1 year.

2. In this example, TSM server address is 143.209.84.128, MPR IP address is 172.22.124.9

3. you need an snmp tool package, such as Net-SNMP, that has snmpwalk, snmpset commands

>>>> Step 1: To modify table opticsIMMgrPollingInfoTable <<<<

H:\>snmpwalk -v 2c -c private 172.22.124.9 .1.3.6.1.4.1.637.54.1.1.6.1.8

SNMPv2-SMI::enterprises.637.54.1.1.6.1.8.1.2.1 = IpAddress: 172.22.124.3

SNMPv2-SMI::enterprises.637.54.1.1.6.1.8.1.2.2 = IpAddress: 143.209.82.176

SNMPv2-SMI::enterprises.637.54.1.1.6.1.8.1.3.1 = STRING: "162"

SNMPv2-SMI::enterprises.637.54.1.1.6.1.8.1.3.2 = STRING: "162"

SNMPv2-SMI::enterprises.637.54.1.1.6.1.8.1.4.1 = INTEGER: 86400

SNMPv2-SMI::enterprises.637.54.1.1.6.1.8.1.4.2 = INTEGER: 86400

SNMPv2-SMI::enterprises.637.54.1.1.6.1.8.1.5.1 = INTEGER: 5

SNMPv2-SMI::enterprises.637.54.1.1.6.1.8.1.5.2 = INTEGER: 5

SNMPv2-SMI::enterprises.637.54.1.1.6.1.8.1.6.1 = INTEGER: 1

SNMPv2-SMI::enterprises.637.54.1.1.6.1.8.1.6.2 = INTEGER: 1

Note: From the above output, your new entry will be on row 3, so replace the X below with "3"

H:\>snmpset -v 2c -c private 172.22.124.9 .1.3.6.1.4.1.637.54.1.1.6.1.8.1.6.X i 5 .1.3.6.1.4.1.637.54.1.1.6.1.8.1.2.X a 143.209.84.128 .1.3.6.1.4.1.637.54.1.1.6.1.8.1.3.X s 162 .1.3.6.1.4.1.637.54.1.1.6.1.8.1.4.X i 31536000 .1.3.6.1.4.1.637.54.1.1.6.1.8.1.5.X i 1

SNMPv2-SMI::enterprises.637.54.1.1.6.1.8.1.6.3 = INTEGER: 5

SNMPv2-SMI::enterprises.637.54.1.1.6.1.8.1.2.3 = IpAddress: 143.209.84.128

SNMPv2-SMI::enterprises.637.54.1.1.6.1.8.1.3.3 = STRING: "162"

SNMPv2-SMI::enterprises.637.54.1.1.6.1.8.1.4.3 = INTEGER: 31536000

SNMPv2-SMI::enterprises.637.54.1.1.6.1.8.1.5.3 = INTEGER: 1

Note: setting the timeout value to 86400 will make the entry expire in 24 hours, while timeout value of 31536000 will last for one year.

H:\>snmpset -v 2c -c private 172.22.124.9 .1.3.6.1.4.1.637.54.1.1.6.1.8.1.6.X i 1

SNMPv2-SMI::enterprises.637.54.1.1.6.1.8.1.6.3 = INTEGER: 1

>>>> Step 1 <<<<

>>>> Step 2: To modify table tsdimEFDTable <<<<

H:\>snmpwalk -v 2c -c private 172.22.124.9 .1.3.6.1.4.1.637.54.1.1.3.1.8

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.2.1 = IpAddress: 172.22.124.3

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.2.2 = IpAddress: 143.209.82.176

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.3.1 = OID: SNMPv2-SMI::enterprises.63

7.54.1.1.3.1.6

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.3.2 = OID: SNMPv2-SMI::enterprises.63

7.54.1.1.3.1.6

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.4.1 = OID: SNMPv2-SMI::enterprises.63

7.54.1.1.3.1.7

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.4.2 = OID: SNMPv2-SMI::enterprises.63

7.54.1.1.3.1.7

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.5.1 = STRING: "162"

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.5.2 = STRING: "162"

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.6.1 = INTEGER: 6

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.6.2 = INTEGER: 6

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.7.1 = INTEGER: 1

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.7.2 = INTEGER: 1

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.9.1 = INTEGER: 1

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.9.2 = INTEGER: 1

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.10.1 = INTEGER: 1

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.10.2 = INTEGER: 1

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.11.1 = INTEGER: 1

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.11.2 = INTEGER: 2

Note: From the above output, your new entry will be on row 3, so replace the Y below with "3", and X with value from Step 1.

H:\>snmpset -v 2c -c private 172.22.124.9 .1.3.6.1.4.1.637.54.1.1.3.1.8.1.10.Y i 5 .1.3.6.1.4.1.637.54.1.1.3.1.8.1.2.Y a 143.209.84.128 .1.3.6.1.4.1.637.54.1.1.3.1.8.1.5.Y s 162 .1.3.6.1.4.1.637.54.1.1.3.1.8.1.4.Y o .1.3.6.1.4.1.637.54.1.1.3.1.7 .1.3.6.1.4.1.637.54.1.1.3.1.8.1.3.Y o .1.3.6.1.4.1.637.54.1.1.3.1.6 .1.3.6.1.4.1.637.54.1.1.3.1.8.1.7.Y i 1 .1.3.6.1.4.1.637.54.1.1.3.1.8.1.6.Y i 6 .1.3.6.1.4.1.637.54.1.1.3.1.8.1.11.Y i X

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.10.3 = INTEGER: 5

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.2.3 = IpAddress: 143.209.84.128

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.5.3 = STRING: "162"

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.4.3 = OID: SNMPv2-SMI::enterprises.63

7.54.1.1.3.1.7

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.3.3 = OID: SNMPv2-SMI::enterprises.63

7.54.1.1.3.1.6

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.7.3 = INTEGER: 1

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.6.3 = INTEGER: 6

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.11.3 = INTEGER: 3

H:\>snmpset -v 2c -c private 172.22.124.9 .1.3.6.1.4.1.637.54.1.1.3.1.8.1.10.Y i 1

SNMPv2-SMI::enterprises.637.54.1.1.3.1.8.1.10.3 = INTEGER: 1

Note: In the above example, all ending value "X" in ".1.3.6.1.4.1.637.54.1.1.3.1.8.1.11.Y i X" referes to the row number from Step 1, which should be "3" in this example.

>>>> Step 2 <<<<

>>>> Step 3: To verify both tables <<<<