I just deployed a nexus 7010 switch at a server farm. after deployment, it was notices that there are surges in latency across the network. The default gateway was then moved to the nexus, with this pinging from an host on the same subnet there is intermitent burst is latency
When you ping from or to the Nexus 7000, the packet needs to be processed in software (read CPU). This will introduce latency for your pings. Also, if you have CoPP enabled then you might be dropping ping packets because of that. The above behavior is expected.
If you are having issues if you ping from one server to another which goes through Nexus, then we should be processing it in hardware. If you are having issues for this kind of behavior then this is not expected and needs to investigate.
Some helpful commands to check drops: show interface eth x/y
show interface eth x/y counter detail all
Check Drop for packets going to CPU (These two commands needs to be done from default VDC)
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.