On Thu, 10 Feb 2000, Greg Coffey wrote:
How do you monitor the busied out ones, how do you find them?
With a very ugly bug-ridden script I wrote in perl... Trust me, you don't want it. It would take more time to set it up for your site than it would for you to write your own :) Here's the OIDs I look at: # chassis items $oid_chas_opstat=".iso.org.dod.internet.private.enterprises.usr.nas.chs.uchasEnt ity.uchasEntityTable.uchasEntityEntry.uchasEntityOperStatus"; $oid_chas_ps=".iso.org.dod.internet.private.enterprises.usr.nas.chs.uchasPowerSu pply.uchasPowerSupplyTable.uchasPowerSupplyEntry.uchasPowerSupplyOperStatus"; $oid_chas_ps_out=".iso.org.dod.internet.private.enterprises.usr.nas.chs.uchasPow erSupply.uchasPowerSupplyOutTable.uchasPowerSupplyOutEntry.uchasPowerSupplyOutWa rnings"; $oid_chas_env=".iso.org.dod.internet.private.enterprises.usr.nas.chs.uchasEnviro n.uchasEnvironTable.uchasEnvironEntry.uchasEnvironStatus"; #nmc items $oid_nmc_stat=".iso.org.dod.internet.private.enterprises.usr.nas.nmc.nmcStat.nmc StatStatus"; $oid_nmc_temp=".iso.org.dod.internet.private.enterprises.usr.nas.nmc.nmcStat.nmc StatTemperature"; $oid_nmc_test=".iso.org.dod.internet.private.enterprises.usr.nas.nmc.nmcStat.nmc StatPowerUpTstFailures"; #ds0-level items (PRI/T1 card only) $oid_ds0_stat=".iso.org.dod.internet.private.enterprises.usr.nas.ds0.ds0StatTabl e.ds0StatEntry.ds0StatDs0"; $oid_ds0_statmodem=".iso.org.dod.internet.private.enterprises.usr.nas.ds0.ds0Sta tTable.ds0StatEntry.ds0StatModem"; #ds0-level items (HiPer DSP) $oid_rds0_stat=".iso.org.dod.internet.private.enterprises.usr.nas.rds0.usrds0Sta tTable.usrds0StatEntry.usrds0StatDs0"; $oid_rds0_statserv=".iso.org.dod.internet.private.enterprises.usr.nas.rds0.usrds 0StatTable.usrds0StatEntry.usrds0StatDs0SrvcState"; #ds1-level items (PRI/T1 card only) $oid_ds1_curstat=".iso.org.dod.internet.experimental.ds1.ds1CurrentTable.ds1Curr entEntry"; #ds1-level items (HiPer DSP) $oid_dsx1_curstat="transmission.ds1.dsx1CurrentTable.dsx1CurrentEntry"; I'm sure there's some stuff missing, but this catches a number of little things and emails me more often than it should... Any other ideas on things to look at? To see call-failure rates, I think I'd have to get chassis accounting set up and all, which is a whole 'nother project. Or look at my radacct logs in mysql for patterns... Charles
At 06:56 PM 2/10/00 -0500, you wrote:
Hi,
One thing I've noticed since going to 4.2.32 on my ARCs is that my monitoring script shows at least 4 to 8 modems per chassis busied out. A software reset on just the modem will bring it back...
Is this a known issue? The only thing that changed was the ARC upgrade, quads have been running the latest since it came out. Also, "list int" will show all of the modems "UP/UP" even when they are busied out.
Any ideas?
Thanks,
Charles
-- =-----------------= = | Charles Sprickman Internet Channel | | INCH System Administration Team (212)243-5200 | | spork@inch.com access@inch.com | = =----------------=
- To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.
Thanks, Greg Coffey <gcoffey@vcn.com> Visionary Communications V 307-234-5443 F 307-234-5446 100 N. Center Suite #100, Casper, WY 82601 www.vcn.com _________________________________________________________ Fight spam now! Get your free anti-spam service at http://www.brightmail.com
- To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.
- To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.