We run a number of Cisco Call Managers (version 3.1 & 3.3(3)srx) across our clients, and use SNMP tools to collect performance data such as; 5 min average CPU utilisation, free physical memory, temperature sensor state, and hard disk % used. Up until December, these OIDs were providing correct data and working fine.
During December we applied patch (OS upgrades 2000-2-5 & sr4) to all Call Managers. Since applying the patch, the physical memory free OID will return the total memory value, and not the memory free value we are used to seeing. This means for the past few months our memory counters have flat lined at the amount of physical memory installed in the system, and are of little or no use to use.
It also means we have been unable to apply our thresholds to (and escalate in the case of continuous low free memory) this counter, putting our customers at risk of system crashes due to undetected out-of-memory conditions.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...