Ethernet Switches & Routers

Reply
Occasional Contributor
Posts: 12
Registered: ‎10-29-2014

ipv6 route-map issues xmr

[ Edited ]

So to me this appears to be a bug.

 

Across different version of XMRs and CER platforms  I can get initial ipv6 connectivity to work and after a few attempts at changing the ipv6 destination address it stops working.

 

Reasons for this configuration is to be able to probe multiple providers for same destination via route-map when sourcing from a specific ipv6 address to ensure least latent path is being taken.

 

Example configuration:

 

ipv6 access-list IRP-IPv6-TWTC
permit ipv6 host 2604:4500::22c2 any

 

 

route-map IRP-IPV6 permit 10
match ipv6 address IRP-IPv6-TWTC
set ipv6 next-hop 2001:4870:c2:9::1
set interface null0

 

interface ve 211

ipv6 address 2604:4500::22c1/123
ipv6 enable
ipv6 policy route-map IRP-IPV6

 

 

Server side has address of 2604:4500::22c2  with the gateway of 2604:4500::22c1

 

 From the server running the following command:

 

mtr --address 2604:4500::22c2 2001:4860:4860::8844

 

Resolver: Received error response 2. (server failure)er of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 2604:4500::22c1 0.0% 3 0.3 2.8 0.3 7.1 3.7
2. 2001:4870:c2:9::1 0.0% 3 1.5 0.8 0.4 1.5 0.6
3. 2001:1900:4:3::376 0.0% 3 26.3 26.3 26.3 26.3 0.0
4. 2001:1900:4:3::375 0.0% 3 29.4 29.6 29.4 29.9 0.3
5. vl-52.ear1.Washington12.Level3.net 0.0% 3 29.8 29.8 29.8 29.8 0.0
6. 2001:1900:4:2::372 0.0% 3 29.9 29.9 29.9 30.0 0.0
7. 2001:4860::1:0:9ff 0.0% 3 31.0 31.1 31.0 31.2 0.1
8. 2001:4860::8:0:6374 0.0% 3 30.9 30.9 30.9 30.9 0.0
9. 2001:4860::8:0:5e9d 0.0% 2 30.9 30.9 30.9 30.9 0.0
10. 2001:4860::2:0:b233 0.0% 2 31.0 32.3 31.0 33.6 1.8
11. ???
12. google-public-dns-b.google.com 0.0% 2 31.1 31.1 31.1 31.1 0.0

 

 

Works...

 

 

After a little while this will stop working.

 

If I remove the option to define the source ip address used within MTR it works via the normal path which bypasses the policy bound on the Virtual interface.

 

mtr 2001:4860:4860::8844

My traceroute [v0.75] Mon Feb 1 20:37:56 2016
Resolver: Received error response 2. (server failure)er of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. 2604:4500::22a1 0.0% 2 0.2 0.2 0.2 0.2 0.0
2. fd80::afd:fd39 0.0% 2 1.4 1.2 1.0 1.4 0.3
3. fd80::afe:3d 0.0% 2 6.0 7.1 6.0 8.1 1.4
4. fd00:2604:4500:2c4::afe:1e 0.0% 2 5.9 5.9 5.9 5.9 0.0
5. 2001:478:124::133 0.0% 2 5.9 5.9 5.9 5.9 0.0
6. 2001:4860::1:0:245c 0.0% 2 20.7 20.8 20.7 20.9 0.1
7. 2001:4860::8:0:8eda 0.0% 2 20.4 22.0 20.4 23.7 2.4
8. 2001:4860::2:0:878c 0.0% 2 17.2 17.2 17.2 17.2 0.0
9. ???
10. google-public-dns-b.google.com

 

 

The only way to get this to work once again is to remove the ipv6 policy route-map IRP-IPV6  and then re-bind it, which at that point it will again only work for a few probes and stop all over again.

 

 

Broadcom
Posts: 6
Registered: ‎12-05-2012

Re: ipv6 route-map issues xmr

Can you please provide the software version you are running?

 

Occasional Contributor
Posts: 12
Registered: ‎10-29-2014

Re: ipv6 route-map issues xmr

on the XMRs 5.6.0f

 

on the CER router that I've tested on:   5.5.0c 

New Contributor
Posts: 2
Registered: ‎08-27-2016

Re: ipv6 route-map issues xmr

Did you ever figure out a resolution to this issue?
Occasional Contributor
Posts: 12
Registered: ‎10-29-2014

Re: ipv6 route-map issues xmr

It appears that moving my edge-routers to juniper MX 960s this problem is resolved.

 

Brocade was unwilling to even start a support case since we didn't have the particular devices under contract and then they also wanted to "recertify" the devices, basically wanted 15k to start a support case on this bug within their software.  Very sad say since I've used brocade when it was foundry and had used the first pair of NI40g's in another network which had a hardware related issue and they had flown staff in that time to identify the issue in a real-world network.

 

Again None of this was a configuration related issue it was all correct, however something within their software was causing this problem and to no help of brocade. Maybe with broadcom aquiring them they will stop trying to nickel and dime their customers and keep loosing the ones who have been loyal to them for such a long time.

 

Sorry, if you have support contract maybe you can bring this issue up with them and _maybe_ in a few months they might have a resolution/fix for this?  Since I can't wait that long, we've decided to start the process of replacing all XMR/CER routers with Juniper MX routers, which isn't a easy task, however so far it appears to be a much stable platform and some of the ideas that I've though brocade to have implemented are already implemented within juniper.  Sure there's a learning curve with juniper however it appears to have way more features and configuration options than any of the brocade devices.

Community Manager
Posts: 181
Registered: ‎03-03-2014

Re: ipv6 route-map issues xmr

@Dan.Protich

 

While we still encourage the community to assist with your post, I wanted to let you I have passed your questions on to our TAC Engagement team and they will be reaching out to you shortly to gather some more information regarding your configuration so we can get you in touch with the correct group.  Note: There may be a slight delay due to the holiday weekend.

 

Dan on a side note we did not have this Community Escalation process in place during your first post earilier in 2016.  

 

I encourage you to continue to post in the community and let me know if there is any way I can help. Once your post is resolved, we will make sure to post the resolution back to the community to help other members.

 

You can find out more about the TAC Engaged program by clicking on the image below.

 

Thank you

Jason McClellan
Community Manager
@jason_cmgr

 

TAC Engaged

Contributor
Posts: 66
Registered: ‎02-25-2016

Re: ipv6 route-map issues xmr

I think the TAC engagement comes too late ;-)

 

Although for the original post I feel there is some information missing:
- What kind of IRP? iBGP?
- Routing table of IRP before and after the "failure"
- ipv6 ndp cache
- On the failure: Does is stop routing or will it route via "normal" route?
- Configuration of the "master" ethernet interface
- Is it route-only or could some traffic switched into?

 

Basically from the route-map, if 2001:4870:c2:9::1 is not a legible next-hop (for reasons whatever) it will also just install a null0-route for your source.

Regards
Jörg Kost
Occasional Contributor
Posts: 12
Registered: ‎10-29-2014

Re: ipv6 route-map issues xmr

This route-map is used for probing external network to make intelligent route decisions. (least latent and packetloss)

 

V4 works fine w/o issues V6 doesn't.

 

The server doing the queries is a direct path (vlan) to the interface(Virtual) on the Edge Router in question.

 

The nexthop of 2001:4870:c2:9::1 is valid this is the peering router of TWTC our side of the circuit is ::2 at no time does this v6 address become unavailable.

 

The probing address used for queries directy to provider in question is: 2604:4500::22c2  If this path fails I expect it to go to null and not fall on another provider hence the strict forwarding based on the policy of the next hop if next-hop is unavilable then send to null (Otherwise routing decisions will continue to flow and if a problem exists within a provider it will not re-route around since the probing still works)

 

You can see from below that prior to applying the route map it takes the default path.

 

Then afterwards applying the route-map it takes the configured path.

 

Which is then followed by failures and the only way to recover it to re-bind this pbr back to the virtual interface. Which will again only allow it to work for a short period.

 

The default path works without issue when the policy applied interface fails.

 


[root@hivelocity (Hivelocity) ~]# mtr -6 ipv6.google.com --address 2604:4500::22c2 -r -c 10
HOST: hivelocity.noction.net Loss% Snt Last Avg Best Wrst StDev
1. 2604:4500::22c1 0.0% 10 0.2 1.2 0.2 5.3 2.1
2. fd00:2604:4500:2c4::afe:9 0.0% 10 13.2 13.2 13.2 13.3 0.0
3. 2001:478:132::41 0.0% 10 13.2 14.6 13.2 27.1 4.4
4. 2001:4860::1:0:8bd5 0.0% 10 13.6 13.5 13.4 13.6 0.0
5. 2001:4860::8:0:ce2d 0.0% 10 14.7 14.9 14.0 18.6 1.6
6. 2001:4860::c:0:d108 0.0% 10 23.3 24.1 20.7 48.6 8.6
7. 2001:4860::2:0:b233 0.0% 10 20.6 21.0 20.5 24.8 1.3
8. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
9. qh-in-x8b.1e100.net 0.0% 10 20.5 20.5 20.5 20.6 0.0


ipv6 policy route-map applied:


[root@hivelocity (Hivelocity) ~]# mtr -6 ipv6.google.com --address 2604:4500::22c2 -r -c 3
HOST: hivelocity.noction.net Loss% Snt Last Avg Best Wrst StDev
1. 2604:4500::22c1 0.0% 3 0.4 3.1 0.4 7.2 3.6
2. 2001:4870:c2:9::1 0.0% 3 0.4 0.6 0.4 0.9 0.3
3. 2001:450:2001:1000:0:67:1716 0.0% 3 8.6 8.6 8.5 8.7 0.1
4. ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
5. lo-0-v6.ear2.Miami2.Level3.n 0.0% 3 7.9 7.9 7.9 7.9 0.0
6. Google-level3-50G.Miami.Leve 0.0% 3 7.8 7.8 7.8 7.8 0.0
7. 2001:4860::1:0:245b 0.0% 3 31.4 25.7 20.3 31.4 5.5
8. 2001:4860::8:0:ce30 0.0% 3 26.9 26.9 26.9 26.9 0.0
9. 2001:4860::c:0:d109 0.0% 3 26.7 26.8 26.7 26.9 0.1
10. 2001:4860::2:0:b234 0.0% 3 26.6 27.2 26.6 28.4 1.0
11. ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
12. qg-in-x8b.1e100.net 0.0% 3 26.5 26.6 26.5 26.6 0.0
[root@hivelocity (Hivelocity) ~]#

 

Example of actions needed to make work again after it stops working:

 

SSH@EBR2.tpa.hivelocity.net#config t
SSH@EBR2.tpa.hivelocity.net(config)#inter ve 211
SSH@EBR2.tpa.hivelocity.net(config-vif-211)#show clock
12:54:49.614 GMT-04 Mon Nov 28 2016
SSH@EBR2.tpa.hivelocity.net(config-vif-211)#no ipv6 policy route-map IRP-IPV6
SSH@EBR2.tpa.hivelocity.net(config-vif-211)#show clock
12:55:10.477 GMT-04 Mon Nov 28 2016
SSH@EBR2.tpa.hivelocity.net(config-vif-211)#ipv6 policy route-map IRP-IPV6
SSH@EBR2.tpa.hivelocity.net(config-vif-211)#show clock
12:55:14.235 GMT-04 Mon Nov 28 2016
SSH@EBR2.tpa.hivelocity.net(config-vif-211)#


[root@hivelocity (Hivelocity) ~]# date
Mon Nov 28 11:55:25 EST 2016
[root@hivelocity (Hivelocity) ~]# mtr -6 ipv6.google.com --address 2604:4500::22c2 -r -c 3
HOST: hivelocity.noction.net Loss% Snt Last Avg Best Wrst StDev
1. 2604:4500::22c1 0.0% 3 0.3 4.9 0.3 8.8 4.3
2. 2001:4870:c2:9::1 0.0% 3 0.5 0.4 0.4 0.5 0.0
3. 2001:450:2001:1000:0:67:1716 0.0% 3 8.6 8.6 8.6 8.6 0.0
4. ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
5. lo-0-v6.ear2.Miami2.Level3.n 0.0% 3 7.9 7.9 7.9 7.9 0.0
6. Google-level3-50G.Miami.Leve 0.0% 3 7.8 7.8 7.8 7.8 0.0
7. 2001:4860::1:0:245c 0.0% 3 20.3 20.3 20.3 20.4 0.0
8. 2001:4860::8:0:ce2f 0.0% 3 104.1 70.0 41.4 104.1 31.7
9. 2001:4860::c:0:d10a 0.0% 3 40.8 49.5 40.8 56.4 8.0
10. 2001:4860::2:0:9f68 0.0% 3 26.6 26.8 26.6 27.2 0.3
11. ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
12. qn-in-x64.1e100.net 0.0% 3 26.6 26.6 26.6 26.6 0.0
[root@hivelocity (Hivelocity) ~]# date
Mon Nov 28 11:55:35 EST 2016
[root@hivelocity (Hivelocity) ~]# mtr -6 ipv6.google.com --address 2604:4500::22c2 -r -c 3
HOST: hivelocity.noction.net Loss% Snt Last Avg Best Wrst StDev
1. 2604:4500::22c1 0.0% 3 7.9 2.9 0.3 7.9 4.4
2. 2001:4870:c2:9::1 0.0% 3 0.4 0.5 0.4 0.5 0.0
3. 2001:450:2001:1000:0:67:1716 0.0% 3 8.5 12.6 8.5 20.9 7.1
4. ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
5. lo-0-v6.ear2.Miami2.Level3.n 0.0% 3 8.0 7.9 7.9 8.0 0.0
6. Google-level3-50G.Miami.Leve 0.0% 3 7.8 7.8 7.8 7.8 0.0
7. 2001:4860::1:0:245b 0.0% 3 20.4 20.3 20.2 20.4 0.1
8. 2001:4860::8:0:ce30 0.0% 3 26.9 26.9 26.9 26.9 0.0
9. 2001:4860::c:0:d109 0.0% 3 26.9 26.9 26.9 27.0 0.1
10. 2001:4860::2:0:b234 0.0% 3 35.1 29.5 26.7 35.1 4.9
11. ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
12. qg-in-x8b.1e100.net 0.0% 3 26.6 26.6 26.6 26.6 0.0
[root@hivelocity (Hivelocity) ~]# date
Mon Nov 28 11:55:42 EST 2016
[root@hivelocity (Hivelocity) ~]# mtr -6 ipv6.google.com --address 2604:4500::22c2 -r -c 3
HOST: hivelocity.noction.net Loss% Snt Last Avg Best Wrst StDev
1. 2604:4500::22c1 0.0% 3 0.3 3.2 0.3 9.0 5.0
2. 2001:4870:c2:9::1 0.0% 3 0.5 0.5 0.4 0.5 0.0
3. 2001:450:2001:1000:0:67:1716 0.0% 3 8.6 8.6 8.5 8.6 0.0
4. ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
5. lo-0-v6.ear2.Miami2.Level3.n 0.0% 3 8.0 8.0 8.0 8.1 0.1
6. Google-level3-50G.Miami.Leve 0.0% 3 7.8 19.6 7.8 43.1 20.4
7. 2001:4860::1:0:245c 0.0% 3 20.3 25.1 20.2 34.9 8.4
8. 2001:4860::8:0:ce2f 0.0% 3 20.1 25.4 20.1 31.5 5.7
9. 2001:4860::c:0:d10a 0.0% 3 26.8 26.8 26.8 26.8 0.0
10. 2001:4860::2:0:b233 0.0% 3 26.6 26.6 26.5 26.6 0.0
11. ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
12. qh-in-x8b.1e100.net 0.0% 3 26.6 26.6 26.6 26.6 0.0
[root@hivelocity (Hivelocity) ~]# date
Mon Nov 28 11:55:49 EST 2016
[root@hivelocity (Hivelocity) ~]# mtr -6 ipv6.google.com --address 2604:4500::22c2 -r -c 3
HOST: hivelocity.noction.net Loss% Snt Last Avg Best Wrst StDev
1. 2604:4500::22c1 0.0% 3 0.3 0.4 0.3 0.6 0.1
2. 2001:4870:c2:9::1 0.0% 3 0.5 0.4 0.4 0.5 0.0
3. 2001:450:2001:1000:0:67:1716 0.0% 3 8.6 8.6 8.5 8.6 0.0
4. ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
5. lo-0-v6.ear2.Miami2.Level3.n 0.0% 3 7.9 7.9 7.9 8.0 0.0
6. Google-level3-50G.Miami.Leve 0.0% 3 7.8 7.9 7.8 8.1 0.1
7. 2001:4860::1:0:245c 0.0% 3 20.3 20.4 20.2 20.5 0.2
8. 2001:4860::8:0:ce2f 0.0% 3 20.1 34.8 20.1 64.2 25.4
9. 2001:4860::c:0:d10a 0.0% 3 26.7 42.8 26.7 74.9 27.7
10. 2001:4860::2:0:9f68 0.0% 3 26.6 26.7 26.6 26.9 0.2
11. ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
12. qn-in-x64.1e100.net 0.0% 3 26.6 26.6 26.6 26.6 0.0
[root@hivelocity (Hivelocity) ~]# date
Mon Nov 28 11:55:56 EST 2016
[root@hivelocity (Hivelocity) ~]# mtr -6 ipv6.google.com --address 2604:4500::22c2 -r -c 3
HOST: hivelocity.noction.net Loss% Snt Last Avg Best Wrst StDev
1. 2604:4500::22c1 0.0% 3 0.4 3.2 0.4 6.2 2.9
2. 2001:4870:c2:9::1 0.0% 3 0.4 0.4 0.4 0.5 0.0
3. 2001:450:2001:1000:0:67:1716 0.0% 3 8.5 8.6 8.5 8.6 0.0
4. ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
5. lo-0-v6.ear2.Miami2.Level3.n 0.0% 3 7.9 7.9 7.9 8.0 0.0
6. Google-level3-50G.Miami.Leve 0.0% 3 7.8 7.8 7.8 7.8 0.0
7. 2001:4860::1:0:245c 0.0% 3 25.4 22.0 20.2 25.4 3.0
8. 2001:4860::8:0:ce2f 0.0% 3 20.1 20.1 20.1 20.1 0.0
9. 2001:4860::c:0:d10a 0.0% 3 33.7 33.2 26.7 39.2 6.3
^[[A^[[A 10. 2001:4860::2:0:9f28 0.0% 3 26.6 27.2 26.6 28.4 1.0
11. ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
12. qr-in-x65.1e100.net 0.0% 3 26.5 26.5 26.5 26.5 0.0
[root@hivelocity (Hivelocity) ~]# date
Mon Nov 28 11:56:04 EST 2016
[root@hivelocity (Hivelocity) ~]# date
Mon Nov 28 11:56:12 EST 2016
[root@hivelocity (Hivelocity) ~]# mtr -6 ipv6.google.com --address 2604:4500::22c2 -r -c 3
HOST: hivelocity.noction.net Loss% Snt Last Avg Best Wrst StDev
1. 2604:4500::22c1 66.7% 3 0.4 0.4 0.4 0.4 0.0
2. 2001:4870:c2:9::1 66.7% 3 0.5 0.5 0.5 0.5 0.0
3. 2001:450:2001:1000:0:67:1716 66.7% 3 8.6 8.6 8.6 8.6 0.0
4. ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
5. lo-0-v6.ear2.Miami2.Level3.n 66.7% 3 7.9 7.9 7.9 7.9 0.0
6. Google-level3-50G.Miami.Leve 66.7% 3 7.8 7.8 7.8 7.8 0.0
7. 2001:4860::1:0:245c 66.7% 3 20.2 20.2 20.2 20.2 0.0
8. 2001:4860::8:0:ce2f 66.7% 3 20.1 20.1 20.1 20.1 0.0
9. 2001:4860::c:0:d10a 66.7% 3 26.7 26.7 26.7 26.7 0.0
10. 2001:4860::2:0:b233 66.7% 3 99.6 99.6 99.6 99.6 0.0
11. ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
12. qh-in-x8b.1e100.net 66.7% 3 26.6 26.6 26.6 26.6 0.0
[root@hivelocity (Hivelocity) ~]# mtr -6 ipv6.google.com --address 2604:4500::22c2 -r -c 3
HOST: hivelocity.noction.net Loss% Snt Last Avg Best Wrst StDev
[root@hivelocity (Hivelocity) ~]# date
Mon Nov 28 11:56:33 EST 2016
[root@hivelocity (Hivelocity) ~]# mtr -6 ipv6.google.com --address 2604:4500::22c2 -r -c 3
HOST: hivelocity.noction.net Loss% Snt Last Avg Best Wrst StDev
[root@hivelocity (Hivelocity) ~]#

 

 

 

SSH@EBR2.tpa.hivelocity.net#show ipv6 cache
Total IPv6 and IPv6 VPN Cache Entry Usage on LPs:
Module Host Network Free Total
1 55 35012 73129 108196
2 55 35012 73129 108196
3 55 35012 73129 108196
4 53 35012 73131 108196
5 55 35012 73129 108196
6 53 35012 73131 108196

 

 

 

SSH@EBR2.tpa.hivelocity.net(config)#inter ve 211
SSH@EBR2.tpa.hivelocity.net(config-vif-211)#no ipv6 policy route-map IRP-IPV6
SSH@EBR2.tpa.hivelocity.net(config-vif-211)#show clock
13:19:58.011 GMT-04 Mon Nov 28 2016
SSH@EBR2.tpa.hivelocity.net(config-vif-211)#ipv6 policy route-map IRP-IPV6
SSH@EBR2.tpa.hivelocity.net(config-vif-211)#show clock
13:21:33.639 GMT-04 Mon Nov 28 2016
SSH@EBR2.tpa.hivelocity.net(config-vif-211)#

 

 

 

[root@hivelocity (Hivelocity) ~]# date
Mon Nov 28 12:21:36 EST 2016
[root@hivelocity (Hivelocity) ~]# mtr -6 ipv6.google.com --address 2604:4500::22c2 -r -c 3
HOST: hivelocity.noction.net Loss% Snt Last Avg Best Wrst StDev
1. 2604:4500::22c1 0.0% 3 4.2 4.6 0.4 9.2 4.4
2. 2001:4870:c2:9::1 0.0% 3 0.4 0.5 0.4 0.7 0.1
3. 2001:450:2001:1000:0:67:1716 0.0% 3 8.6 8.5 8.5 8.6 0.0
4. ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
5. lo-0-v6.ear2.Miami2.Level3.n 0.0% 3 8.0 8.0 7.9 8.0 0.0
6. Google-level3-50G.Miami.Leve 33.3% 3 14.1 10.9 7.8 14.1 4.4
7. 2001:4860::1:0:245c 0.0% 3 20.3 25.3 20.3 35.3 8.6
8. 2001:4860::8:0:ce2e 0.0% 3 26.8 26.8 26.8 26.8 0.0
9. 2001:4860::c:4000:d673 0.0% 3 26.8 26.9 26.8 27.1 0.2
10. 2001:4860::2:0:6dd0 0.0% 3 26.6 26.6 26.6 26.6 0.0
11. ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
12. qk-in-x64.1e100.net 0.0% 3 26.6 26.6 26.6 26.6 0.0
[root@hivelocity (Hivelocity) ~]# mtr -6 ipv6.google.com --address 2604:4500::22a2 -r -c 3
HOST: hivelocity.noction.net Loss% Snt Last Avg Best Wrst StDev
1. 2604:4500::22a1 0.0% 3 0.2 0.2 0.2 0.3 0.0
2. fd80::afd:fd39 0.0% 3 0.8 0.8 0.7 0.8 0.1
3. fd80::afe:3d 0.0% 3 2.3 0.9 0.3 2.3 1.2
4. fd00:2604:4500:2c4::afe:9 0.0% 3 13.2 14.1 13.2 15.9 1.5
5. 2001:478:132::41 0.0% 3 31.2 21.0 15.8 31.2 8.9
6. 2001:4860::1:0:c90f 0.0% 3 13.4 13.4 13.4 13.4 0.0
7. 2001:4860::8:0:ce2d 0.0% 3 14.1 14.0 14.0 14.1 0.0
8. 2001:4860::c:0:d108 0.0% 3 23.8 23.8 23.8 23.9 0.1
9. 2001:4860::2:0:b233 0.0% 3 20.5 20.6 20.5 20.6 0.0
10. ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
11. qh-in-x66.1e100.net 0.0% 3 20.5 20.5 20.5 20.5 0.0
[root@hivelocity (Hivelocity) ~]# mtr -6 ipv6.google.com --address 2604:4500::22c2 -r -c 3
HOST: hivelocity.noction.net Loss% Snt Last Avg Best Wrst StDev
1. 2604:4500::22c1 0.0% 3 0.3 2.4 0.3 6.4 3.5
2. 2001:4870:c2:9::1 0.0% 3 0.5 0.5 0.4 0.5 0.0
3. 2001:450:2001:1000:0:67:1716 0.0% 3 8.6 8.6 8.5 8.6 0.0
4. ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
5. lo-0-v6.ear2.Miami2.Level3.n 0.0% 3 8.0 8.0 8.0 8.0 0.0
6. Google-level3-50G.Miami.Leve 0.0% 3 7.8 8.2 7.8 9.0 0.7
7. 2001:4860::1:0:245b 0.0% 3 20.3 20.3 20.3 20.3 0.0
8. 2001:4860::8:0:ce30 0.0% 3 26.8 26.8 26.8 26.9 0.0
9. 2001:4860::c:0:d109 0.0% 3 26.9 26.9 26.8 27.0 0.1
10. 2001:4860::2:0:9f68 0.0% 3 26.7 26.6 26.6 26.7 0.0
11. ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
12. qr-in-x66.1e100.net 0.0% 3 26.6 26.6 26.5 26.6 0.0
[root@hivelocity (Hivelocity) ~]# date
Mon Nov 28 12:22:01 EST 2016
[root@hivelocity (Hivelocity) ~]# date
Mon Nov 28 12:22:11 EST 2016
[root@hivelocity (Hivelocity) ~]# mtr -6 ipv6.google.com --address 2604:4500::22c2 -r -c 3
HOST: hivelocity.noction.net Loss% Snt Last Avg Best Wrst StDev
1. 2604:4500::22c1 0.0% 3 0.3 1.7 0.3 4.5 2.4
2. 2001:4870:c2:9::1 0.0% 3 0.5 0.5 0.5 0.6 0.1
3. 2001:450:2001:1000:0:67:1716 0.0% 3 8.6 8.6 8.6 8.6 0.0
4. ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
5. lo-0-v6.ear2.Miami2.Level3.n 33.3% 3 7.9 8.0 7.9 8.0 0.0
6. Google-level3-50G.Miami.Leve 33.3% 3 7.8 7.8 7.8 7.8 0.0
7. 2001:4860::1:0:245b 33.3% 3 23.2 21.8 20.3 23.2 2.1
8. 2001:4860::8:0:ce2d 33.3% 3 20.1 20.5 20.1 20.8 0.5
9. 2001:4860::c:0:d108 33.3% 3 27.0 27.0 27.0 27.0 0.0
10. 2001:4860::2:0:b234 33.3% 3 26.7 26.7 26.7 26.7 0.0
11. ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
12. qg-in-x65.1e100.net 33.3% 3 26.6 26.6 26.6 26.6 0.0
[root@hivelocity (Hivelocity) ~]# date
Mon Nov 28 12:22:30 EST 2016
[root@hivelocity (Hivelocity) ~]# mtr -6 ipv6.google.com --address 2604:4500::22c2 -r -c 3
HOST: hivelocity.noction.net Loss% Snt Last Avg Best Wrst StDev
[root@hivelocity (Hivelocity) ~]# date
Mon Nov 28 12:22:41 EST 2016
[root@hivelocity (Hivelocity) ~]# mtr -6 ipv6.google.com --address 2604:4500::22a2 -r -c 3
HOST: hivelocity.noction.net Loss% Snt Last Avg Best Wrst StDev
1. 2604:4500::22a1 0.0% 3 0.3 0.3 0.2 0.3 0.0
2. fd80::afd:fd39 0.0% 3 1.1 0.9 0.7 1.1 0.2
3. fd80::afe:3d 0.0% 3 1.5 0.8 0.3 1.5 0.7
4. fd00:2604:4500:2c4::afe:9 0.0% 3 15.9 14.1 13.2 15.9 1.5
5. 2001:478:132::41 0.0% 3 15.8 15.8 15.8 15.8 0.0
6. 2001:4860::1:0:8bd5 0.0% 3 16.4 16.5 16.4 16.6 0.1
7. 2001:4860::8:0:ce2e 0.0% 3 23.4 23.4 23.4 23.5 0.1
8. 2001:4860::c:4000:d673 0.0% 3 23.8 23.8 23.8 24.0 0.1
9. 2001:4860::2:0:9f28 0.0% 3 23.6 23.6 23.5 23.6 0.0
10. ??? 100.0 3 0.0 0.0 0.0 0.0 0.0
11. qr-in-x66.1e100.net 0.0% 3 20.5 20.6 20.5 20.6 0.1
[root@hivelocity (Hivelocity) ~]# date
Mon Nov 28 12:22:50 EST 2016
[root@hivelocity (Hivelocity) ~]#

 

 

 

Community Manager
Posts: 181
Registered: ‎03-03-2014

Re: ipv6 route-map issues xmr

@Dan.Protich

 

Details received - working on escalation.

 

Thank you

Jason McClellan
Community Manager
@jason_cmgr

TAC Engaged

Contributor
Posts: 66
Registered: ‎02-25-2016

Re: ipv6 route-map issues xmr

I have tested your examples successfully on 5.4.0f, no issues, however I am not directly connected like in your configuration. But I have also checked the release notes till 6.00 and have not found any defect so far. Maybe I will have a chance for testing with 5.6 tomorrow. 

Regards
Jörg Kost

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.

vADC is now Pulse Secure
Download FREE NVMe eBook