Here is a recent posting that may apply to your situation:
Subject: Re: [NV-L] Loading CISCO Traps
Take a look at the Cisco mib "ciscoMgmt", in particular the
ciscoProcessMIBObjects,cpmCPU,cpmCPUTotalTable and its entries for process cpu
utilization and ciscoMemoryPoolMIB.ciscoMemoryPoolObjects.ciscoMemoryPoolTable
for memory utilization (both are under "ciscoMgmt".)
Also check out the following:
ciscoLS1010ChassisMIBNotificationPrefix {1.3.6.1.4.1.9.5.11.2}
ciscoEsConfig {1.3.6.1.4.1.9.5.14.1.1}
ciscoEsStack {1.3.6.1.4.1.9.5.14.2}
ciscoEsPort {1.3.6.1.4.1.9.5.14.4}
ciscoEsEChannel {1.3.6.1.4.1.9.5.14.6}
ciscoEsVLANs {1.3.6.1.4.1.9.5.14.8}
ciscoTsConfig {1.3.6.1.4.1.9.5.32.1.1}
ciscoTsStack {1.3.6.1.4.1.9.5.32.2}
ciscoTsPort {1.3.6.1.4.1.9.5.32.4}
ciscoTsVLANs {1.3.6.1.4.1.9.5.32.6}
ciscoTsTChannel {1.3.6.1.4.1.9.5.32.7}
cisco-dcd {1.3.6.1.4.1.9.5}
cisco {1.3.6.1.4.1.9}
ciscoLS1010ChassisFailureNotification
ciscoLS1010ChassisChangeNotification
ciscoLS1010acctngFileNearlyFull
ciscoLS1010acctngFileFull.
Regards,
ken
|