ser

Yes please!

Latest version: Transmode TM-3000 DWDM and Packet Optical

I've uploaded pollers for the TM3000. I have a few more I need to upload though. I've done the amps, transponders, PM's, alarms and some of the EMXP features (MPLS-TP). If you need any help, let me know. 

Which Transmode products are you using? I have a case open with Transmode to add IF-MIB support for the EMXP products (it would be really handy if they would just show up as interfaces!).

I have a few older Cisco Switches that do this as well. I found disabling 64 bit counters fixed it. I am guessing the 64 bit counters are broken on the device software.

There is actually a known bug on the SR issue. If you have a maint contract you should be able to get TAC to dig it up.

What does the value of the sensor 1.3.6.1.4.1.9.9.91.1.1.1.1.4.3085 and the status 1.3.6.1.4.1.9.9.91.1.1.1.1.5.3085 show? SensorStatus enumerates to: 1:ok 2:unavailable 3:nonoperational And the value of that sensor should return something like 329 based on the "show int trans" you showed earlier.

My vote is for them to display all the sensors under "List Resources" so we can select what we want/don't want. [edit] And also, all the resources that are related to specific ethernet interfaces should really be displayed with the specific interface they are part of, and not separately. Solarwinds could make my NOC's day…

Robert, See case 425740

This is the battle I have been having with Solarwinds. They do not seem to understand why this is an issue and support seems to be getting a lot of pushback from the dev's. My only suggestion is to open a case with Solarwinds, and do not let them close it. 

SW Support told me "next quarter", and then tried to close my case. 

1310 is an interesting number. Are these LR optics by chance? It almost seems like in your case they are loading the wrong # into the MIB. 1310 being the frequency of the optic rather then the mA threshold.

I'd like to see this as well. Most of my SLA measurements require me to be able to compare sites to each other, and we are adding sites often enough that it would be much easier if I had a way to add a new site without adding everything by hand again.

Agreed. But I think the option of ignoring certain sensors is a good thing for Solarwinds to do, because there are still cases where there are sensors that need to be ignored (I have had a long running issue with hardware monitors in SAM, on hardware that has extra fan status inputs on motherboards not being used). 

I have several vmware nodes showing up with hardware faults because of the way the supermicro chassis interfaces with the motherboard. For example: not all the fan connectors are used. See the attached screenshot.

The Transmode MIBS are in the latest database. I made universal device pollers for the selection of Transmode gear we use on our network. I will upload them to thwack when I have some time. I agree, some native support would be nice for the Transmode gear. Not everything is easy to do with the udp's. 

Net-SNMP just shows up as Net-SNMP. Would be nice if it showed the machine type Object NameObject Identifier netSnmpTCs1.3.6.1.4.1.8072.3.1.1 hpux91.3.6.1.4.1.8072.3.2.1 linux1.3.6.1.4.1.8072.3.2.10 bsdi1.3.6.1.4.1.8072.3.2.11 openbsd1.3.6.1.4.1.8072.3.2.12 win321.3.6.1.4.1.8072.3.2.13…

Cisco Secure Access Control System 5.3 OID: .1.3.6.1.2.1.47.1.1.1.1.13.1 ping.. still missing.

You can edit the database to disable individual sensors. Look at the APM_HardwareItem table Edit: Ok so it doesn't work as well as I thought.

Solarwinds has a fix that solved about 95% of the problems we are having with the hardware monitoring. There is an outstanding issue with interfaces that are in the shutdown and not monitored by Orion still going into alarms about low power levels, etc (ie: if you stop using a 10G interface, remove it from Orion, and admin…

I don't think you read the thread carefully enough. The Ciscos themselves are in warning/alarm state as well. Look below, every where you are seeing "--" to the right of the (mA) col, is "low warning" state. This is straight out of the Cisco router. It is actually correct for Solarwinds to be reporting this in Hardware…

It's going to be in entSensorValue 1.3.6.1.4.1.9.9.91.1.1.1.1

Does XE have "show snmp mib entity indexmapping". I only have IOS and IOS-XR so I can't try it on XE. If it does have indexmapping, does the bias current sensor show up here?

I just showed that to someone at cisco, thanks! 

What if you just do "show interface transceiver" (without detail). I've never seen Current not show up before. What hardware/ios was this?

I have a case open with solarwinds about disabling individual h/w monitors (371894) and another one about unknown hardware monitors, and bias current errors (408508). I also have a friend at Cisco TAC that is trying to get some traction on this as well.

I can't find a way to make this work with UDP's. The entity MIB refers to unique numbers that are not the same as the ifIndex ID that is used by the Interfaces. I'm sure there is a way solarwinds could make this work, but there doesn't appear to be a way to do it with UDP's. The values are stored in enitySensorMIB…

+1 on this. 

1.3.6.1.4.1.1896.1 Symmetricom NTS-200

Cisco Secure Access Control System 5.3 OID: .1.3.6.1.2.1.47.1.1.1.1.13.1