Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I am looking to see if anyone else has experianced this problem rather than looking for a solution at this time.We have a standard design with 2 N5Ks set up with vPC using 2232s. Hosts connect to the 2232s with dual 10 Gb adapters. These are VMWare...
I'm not particularly strong with SONET and only have a small SONET network so any help with this question would be greatly appreciated. When line terminating equipment (SONET node) detects a section error what does it do with that frame when it swit...
According to the Cisco documentation the "standby preempt delay reload" command is used to delay preemption after a reload. It also states that the "standby delay reload" is only used to delay HSRP group initialization.standby preempt delay reloadht...
I would like to use EEM, preferable an applet to monitor the number of bytes in an output queue on an interface of a catalyst 6500. Has anyone done this that can provide guidence an/or is there a better way to do this.Preferable I'd like to get an a...
I understand why the A interface for the port channel has been created. It is due to a mismatch and the ones that can be bundled together were put in the A interface. These are LACP etherchannels connected to servers not other switches. Once this ...
I currently do not track this information and have not been able to find a way to get it. I would like it for input as well as output queues. The switches I'm hopeful to monitor are 6500's with Sup32 and Sup720s.
It looks like the logging discriminator command is not available until 12.4(11) and I'm not on that version of code yet. It may be an option when we get there but that's still a quite way off. Are there any other solutions?
Have you actually seen the gratuitous arps in a trace or are you basing this off the vendor documentation? I would get a trace, if you haven't already, to confirm if it is the FW not sending it at failover or the 6513 not seeing it. That trace alon...
