im not able to access video...request you to upload again please ... View more

Hi You need FP to run Anycast HSRP. With OTV you can localize HSRP between two DC via HSRP Filtering.   Please find required configuration for HSRP filtering in this document   http://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/overlay-transport-virtualization-otv/white_paper_c11-702185.html#wp9001588   Please let us know if you need any further clarification   Regards, Sandip ... View more

Hi Answer to your question Q.1 is a specific VDC for OTV still required on current releases ? Ans.1: Yes, you still need separate VDC for OTV, in future release OTV and SVI will be supported in single VDC - is Anycast HSRP supported to build Active/Active topologies between DC ? Ans. 2: Anycast HSRP supported sure for Fabricpath used as DCI   Regards, Sandip   ... View more

Hi tporembski   Yes, this is technically supported. It is important to note that it is still necessary to have a separate vPC peer-link and vPC Peer-Keepalive Link infrastructure for each VDC deployed. Regards, ... View more

Hi Tenaro   OTV is supported on ASR1K as well apart from N7K OTV is mainly designed for Data Center, You just need IP rechability between two site to run OTV, you do not specifically need MPLS as we require for VPLS, AToM. You do not need pseduowire to run OTV. OTV elimiates flooding as it use multicast and proxy arp to send messages to the clients. OTV is simpler to configure and manage. Many more advantages of deploying OTV compare to other tunneling protocol you can find in this document   http://www.cisco.com/c/en/us/products/collateral/switches/nexus-7000-series-switches/white_paper_c11-574984.html   Please let us know if you have any further query   Regards, ... View more

Hi Vo,   It will be supported on F3 line card in future release   Regards, Sandip ... View more

Hi Mike 802.1ae not supported on any of the N5K device   Regards, Sandip ... View more

Hi Please read below quote, I hope this will answer your question   MPLS LDP Session Protection uses LDP Targeted Hellos to protect LDP sessions. Take, for example, two directly connected routers that have LDP enabled and can reach each other through alternate IP routes in the network. An LDP session that exists between two routers is called an LDP Link Hello Adjacency. When MPLS LDP Session Protection is enabled, an LDP Targeted Hello Adjacency is also established for the LDP session. If the link between the two routers fails, the LDP Link Adjacency also fails. However, if the LDP peer is still reachable through IP, the LDP session stays up, because the LDP Targeted Hello Adjacency still exists between the routers. When the directly connected link recovers, the session does not need to be reestablished, and LDP bindings for prefixes do not need to be relearned.   http://www.cisco.com/c/en/us/td/docs/ios/mpls/configuration/guide/12_2sy/mp_12_2sy_book/mp_ldp_sessn_prot.html   Let me know if you have further query Regards, Sandip ... View more

Hi , Can you let me know which error ru getting ? and what is the image ? Did you try with clear / hard bgp reset ? Regards, Sandip     ... View more

Hi Paul Would be great if you can provide your requirement in details Regards, Sandip ... View more