Thanks ... that should work for now. -----Original Message----- From: Todd Bertolozzi [mailto:berto@voyager.net] Sent: Friday, August 02, 2002 12:07 PM To: usr-tc@mailman.xmission.com Subject: RE: [USR-TC] [USC-TC] HiperNMC OIDs I was looking around for a trap oid that would do this but for now the easiest thing I've found is to highlight all the DSP's (card level)...setup an autoresponse trap for a module non-operational. I add to the script a "generate autoresponse snmp trap" so I know a card has "gone yellow" and then also add a "reset module" so that as soon as it goes yellow the chassis tries to reset it. It's important to have a trap sent too so that you know an event has happend on your network. Else you could get into a loop where the card goes out of service...the chassis resets it, it comes back up, then goes out of service, chassis resets it again...etc, etc...loop. You can verify this is working by doing the setup I indicated. Save everything...then issue a remove from service command on the dsp. You will notice that the chassis indicated that it did a hardware reset instead of removing it from service provided you have the autoresponse setup correctly. When I get around to finding that OID that you want I will post it but I'm caught up in other stuff at the moment. Todd -----Original Message----- From: usr-tc-admin@mailman.xmission.com [mailto:usr-tc-admin@mailman.xmission.com]On Behalf Of MacDonald, James Sent: Friday, August 02, 2002 11:54 AM To: 'usr-tc@mailman.xmission.com' Subject: RE: [USR-TC] [USC-TC] HiperNMC OIDs Interesting ... I'm looking for one that will tell me if the slot is on the Management BUS or not ... I.e. in Yellow alarm in TCM. Did you get this from another list of OID's? If so, can you provide the list? thanks Jim -----Original Message----- From: Todd Bertolozzi [mailto:berto@voyager.net] Sent: Friday, August 02, 2002 11:19 AM To: usr-tc@mailman.xmission.com Subject: RE: [USR-TC] [USC-TC] HiperNMC OIDs Not exactly sure which one you want put if you do a walk against the nmc with .1.3.6.1.4.1.429.1.27.2.1.6 you will get the span line status. Todd -----Original Message----- From: usr-tc-admin@mailman.xmission.com [mailto:usr-tc-admin@mailman.xmission.com]On Behalf Of MacDonald, James Sent: Friday, August 02, 2002 11:12 AM To: 'usr-tc@mailman.xmission.com' Subject: [USR-TC] [USC-TC] HiperNMC OIDs Anyone know the OID to get the specific slot in alarm ... I can get the NMC alarms in general and am able to convert them to codes ... but instead of just finding an MBUS failure I wanted to narrow it down to a specific slot assignment. Thanks,
James MacDonald, CCNP Senior Platform Manager, IP Network Operations AT&T Canada Corp. 370 King St W., 6th Floor Toronto, ON M5V1J9 Ph: 416-204-5793 Fx: 416-204-5744 Emergency: 416-204-5700 (NMC Hotline) Email: james.macdonald@attcanada.com
_______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc _______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc _______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc _______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc