Hi Harold, Thanks a lot for your reply..Let me know if  my understanding is correct: 1. Cisco sends both unlabelled and labelled ipv6 prefixes to juniper after bgp is established 2. Juniper drops BGP sessiona fter seeing NLRI with native IPv6 3. Cisco needs to have route-map policy which matches all ip v6 prefixes with next-hop as native ipv6 and use "set -mpls-label" command to send them out with labels so that Juniper does not drop BGP. Also, can you provide me with a sample config of the route-map and if can match conditions beased on next hop? I need to get back to customer for the IOS version..As of now I have control only over Juniper box. Thanks Mukundh ... View more

Thanks for the reply Nagendra... I have another related query regarding this. We have BGP neighborship flapping between 2 routers ...One is Cisco 7204 and another is Juniper M120 I think.... The Juniper logs show that BGP is flapped due to family inet6 not configured on the Juniper end and Juniper is receiving BGP advertisements with native IPv6 as next hop from Cisco when it shouldn't be receiving that.. The following are commands on Cisco and Juniper... ##### CISCO#### outer bgp 5603 neighbor 95.176.254.10 inherit peer-session LAR  neighbor 95.176.254.10 description --- M320-LAB-LJ-CIGALETOVA  address-family ipv4   neighbor 95.176.254.10 activate   neighbor 95.176.254.10 inherit peer-policy LAR-ipv4  address-family ipv6   neighbor 95.176.254.10 activate   neighbor 95.176.254.10 send-community both   neighbor 95.176.254.10 route-reflector-client   neighbor 95.176.254.10 send-label template peer-session LAR   remote-as 5603   update-source Loopback0   timers 30 90 exit-peer-session template peer-policy LAR-ipv4   route-map LAR-ipv4-out out   route-reflector-client   soft-reconfiguration inbound   send-community both exit-peer-policy ####JUNIPER#### protocols{bgp{ group I-BGP-IPV4 {             type internal;             family inet {                 unicast;             }             family inet6 {                 labeled-unicast {                     explicit-null;                 }             }             export RR-Export-All;             neighbor 95.176.255.254 {                 description C7201-RR-IP-CIGALETOVA;                 local-address 95.176.254.10;             }             neighbor 95.176.255.252 {                 description C7201-RR-IP-CIGALETOVA;                 local-address 95.176.254.10;             }         } By the cisco command above, shouldn't cisco be sending only labelled ipv6 prefixes or am I wrong in this. And if Cisco sends both unlabelled and labelled prefixes, is there a way to make it send only ipv6 prefixes? Thanks Mukundh ... View more

Thank you Sam, Neeraj and Peter for the responses. So it really depends on the transport protocol , TCP or UDP, whether ARP table refreshes cause a disruption. ... View more

Hi Jouni I think i might be mistaken about the Active/Active part. I do not have access to the firewall and just have its config. The " sh ver" showed Failover as Active/Active and i assumed it is active/active. But the failover configs doesnot show any failover cotexts. Here is failover configs from primary ASA. Does it mean it is in active/standby: failover failover lan unit primary failover lan interface failover Management0/0 failover polltime unit 1 holdtime 3 failover polltime interface 2 holdtime 10 failover key ***** failover link failover Management0/0 failover interface ip failover 1.1.1.1 255.255.255.252 standby 1.1.1.2 Thanks Mukundh ... View more

Hi Julio, You are correct. I had to reduce deadtime to resolve the issue. Thanks for your help Mukundh ... View more