what is the bug detail, is it related by ttl?
On Friday, November 8, 2013, Danny Pinto <[email protected]> wrote: > Just got confirmed with a SR . Bug on SR. VRRP v6 on XR does not work with other platforms. > Thanks. > Regards, > Danny > > On Thursday, 7 November 2013 6:38 PM, Xu Hu <[email protected]> wrote: > > one recommendation is that check the ttl value for xr and junos. > I got one case regarding iOS & IOS-XR, then cannot talk, finnaly i sniffer the detail packet and found that the default ttl value is different, so both cannot recognise each other. > > On Wednesday, November 6, 2013, Danny Pinto <[email protected]> wrote: >> >> >> Thanks I able to get VRRP working on v6 between two XR 12K boxes. >> >> But when I try to get VRRP working between a XR12K and JunOS on MX . v4 VRRP works fine. >> >> VRRP v6 does not come up , getting some checksum errors on the debug for v6 and both the boxes are becoming masters ! Any clue ? >> >> Anything needs to be done to get VRRP v6 working between XR and JunOS. ? below is configuration & logs . >> >> >> XR 12000 >> >> >> >> interface Gi0/2/1/6.451 >> description VRRP Test 2 >> ipv4 address 172.0.51.2 255.255.255.248 >> ipv6 address 2001:1234:0:e::451:2/112 >> dot1q vlan 451 >> >> >> router vrrp >> interface Gi0/2/1/6.451 >> address-family ipv4 >> vrrp 10 version 3 >> priority 110 >> address 172.0.51.3 >> ! >> ! >> address-family ipv6 >> vrrp 10 >> priority 110 >> address linklocal fe80::cafe:1 >> address global 2001:1234:0:e::451:3 >> ! >> >> >> Juniper MX >> >> @sar4.BLB# show interfaces ge-0/1/9.451 >> description "VRRP Test 2 cr2.BLB"; >> vlan-id 451; >> family inet { >> address 172.0.51.1/29 { >> vrrp-group 10 { >> virtual-address 172.0.51.3; >> priority 200; >> } >> } >> } >> family inet6 { >> address 2001:1234:0:e::451:1/112 { >> vrrp-inet6-group 10 { >> virtual-inet6-address 2001:1234:0:e::451:3; >> virtual-link-local-address fe80::cafe:1; >> priority 200; >> } >> } >> } >> >> show protocols vrrp | display set >> set protocols vrrp traceoptions file VRRP >> set protocols vrrp traceoptions flag all >> deactivate protocols vrrp traceoptions >> set protocols vrrp version-3 >> >> >> >> Error logs >> >> I see follow logs on XR debugs. V4 is working okay.checksum errors for IPv6 >> >> RP/0/9/CPU0:Nov 6 09:34:08.166 : vrrp[1108]: Gi0/2/1/6.451: Prot err: src fe80::8271:1f01:c3f1:2832: Received packet has invalid checksum: 31410 >> RP/0/9/CPU0:Nov 6 09:34:08.238 : vrrp[1108]: Gi0/2/1/6.451: VR10: Pkt: ADVER: In: pri 200 src 172.0.51.1 >> RP/0/9/CPU0:Nov 6 09:34:08.238 : vrrp[1108]: Gi0/2/1/6.451: VR10: IPv4: Prot evt: Out: Master_Down timer restarted for 3 sec, 570 msec >> g aRP/0/9/CPU0:Nov 6 09:34:09.030 : vrrp[1108]: Gi0/2/1/6.451: Prot err: src fe80::8271:1f01:c3f1:2832: Received packet has invalid checksum: 31410 >> >> >> RP/0/9/CPU0:cr2.BLB#show vrrp interface Gi0/2/1/6.451 >> Wed Nov 6 09:35:27.334 IST >> IPv4 Virtual Routers: > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
