We often have our older Catalyst 5000 and 5500 devices report a 'No Response' failure for scheduled VMPS reconfirmations. Manually forcing a reconfirmation one or more times will eventually succeed.
I have been able to watch traffic between a client and the server and there are plenty of VQP requests and responses taking place. So, I am wondering if anyone knows whether the VMPS reconfirmation is really an all-or-nothing operation or if a failure resulting in 'No Response' really just means that at least 1 port/MAC was not able to be confirmed.
I have been told that this is actually explained in a paper somewhere on this site. From what I have been able to gather, if there is even 1 port that does not reconfirm then the overall status is set to 'No Response'. I think what is causing this is a UDP overflow that sometimes occurs for individual reconfirms.
We've moved all vmp serving off of the catalyst devices and onto a machine running openvmps (vmps.sf.net). It is working better for us. After replacing our existing vmp servers (cat5k/sup3) with new 6500/sup720's we promptly began having outages due to non-reconfirmation all over the place. Specifically, ports on the servers themselves would rarely ever reconfirm if at all.
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.