Hi, Situation: Cisco 3750 stack containing 6 members. CPU for ages @ 20-23 % with totally no spikes or extra load. With some heavy acl's and a few logg options it seems to slow thing down and even provides packetloss at some busy moments. I am trying to find out how I can monitor each member individualy with it's CPU load. I do not fully trust the totals of the normal MIB with SNMP. Is there a way to have a CPU readout for each member ? Trying the @<nr> with the community string does not provide me any. vm-pub#sho switch Switch/Stack Mac Address : 0016.c7e3.ca00                                            H/W   Current Switch#  Role   Mac Address     Priority Version  State ---------------------------------------------------------- *1       Master 0016.c7e3.ca00     15     0       Ready 2       Member 0017.9451.bb00     14     0       Ready 3       Member 0015.63a6.8b80     13     0       Ready 4       Member 0016.c793.c980     12     0       Ready 5       Member 0017.9451.df00     11     0       Ready 6       Member 0015.635e.d680     10     0       Ready SNMPwalk at the designated MIB does this : [adm@infra1 ~]$ snmpwalk -v2c -c testcomm@1 vm-pub .1.3.6.1.4.1.9.9.109.1.1.1.1.5 SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.5.1 = Gauge32: 23 [adm@infra1 ~]$ snmpwalk -v2c -c testcomm@2 vm-pub .1.3.6.1.4.1.9.9.109.1.1.1.1.5 SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.5.1 = Gauge32: 23 [adm@infra1 ~]$ snmpwalk -v2c -c testcomm@3 vm-pub .1.3.6.1.4.1.9.9.109.1.1.1.1.5 Timeout: No Response from vm-pub idem for #4, 5 and 6. Thanks in advance.. ... View more

Hi, I am having some difficulties to have a stable connection on a Cisco 881. I have a IP Sla running with an ICMP-ECHO towards the uplink router. Linked with this is a tracking on the IP SLA so I can shutdown an HRSP instance with the tracking. The desired result is with this that when the nexthop becomes unavailable HSRP switches to the second router with the backup connection. Regardless whatever timeout or threshold, the tracking switches at a random point when the line is somewhat congested. Debugging it shows me only a time-out on the IP SLA. Is there anything possible to get the icmp-echo to retry it 2-3 times or so before going it's status is set to failure? Searching the Cisco site does not hand me out the right answers. Any alternatives are also welcome. Current configuration track 1 ip sla 1 interface Vlan10 ip address 10.0.1.125 255.255.255.128 standby 1 ip 10.0.1.126 standby 1 priority 200 standby 1 preempt standby 1 authentication ***** standby 1 track 1 shutdown ip sla 1 icmp-echo 172.31.0.3 source-interface Vlan10 frequency 10 timeout 9000 threshold 8500 ip sla 1 schedule 1 life forever start-time now In italic the line which does not help at all. ... View more

Hi, Im having difficulties to get the QoS configurations working on a Cisco 7609 chassis with the sup720 supervisor card. The goal is to do some shaping and queuing in the upstream towards the device in the subnet on this interface vlan. Problem of the configuration class-map match-any class-prio5 match ip precedence 5 match mpls experimental topmost 5 class-map match-any class-prio1 match ip precedence 1 match mpls experimental topmost 1 policy-map policy-p20-40-egress class class-prio5 bandwidth percent 20 class class-prio1 bandwidth percent 40 class class-default random-detect MLS QoS is enabled Trying to get the policy enabled on the interface vlan (in or output) does not work and I receive the following error cr1.ams2(config)#int vlan 467 cr1.ams2(config-if)#service-policy output policy-p20-40-egress bandwidth percent command is not supported in output direction for this interface Configuration failed! cr1.ams2(config-if)#service-policy input policy-p20-40-egress bandwidth percent command is not supported in input direction for this interface Configuration failed! Trying to figure out why this does not work hasn't delivered me the desired results or satisfying answer. What could I do to understand the problem and most off all to get it working. All the advice is welcom! ... View more