[rbak-nsp] ipv6 - strange ?? (ping)

Marcin Kuczera marcin at leon.pl
Sun Mar 29 12:57:06 EDT 2009


David Freedman wrote:
 > Well, I would be interested to know if the problem goes away if you 
shutdown/deconfigure vlan102
 > (and optionally clear nd cache as well)
 >
 > If not then it is more likely to be a bug.

well, looks like a bug... next one to be reported...

[bgp1]RedBack_SE100#show ipv6 inter

Intf name:      dhcp
Intf state:     Up (Loopback)             IPv6 MTU:       0
Address:
Link local addr:
Number of Bound Circuits (incl. dynamic) = 1

Intf name:      vlan101
Intf state:     Up                        IPv6 MTU:       1500
Description:    Silweb
Address:        2a01:1d8:7fff:fffd:1::15  Prefix len:     126
Link local addr:fe80::230:88ff:fe12:59e
Number of Bound Circuits (incl. dynamic) = 1

Bindings: (Total Bound Circuits 1)
Encapsulation  Circuit
dot1q          2/1 vlan-id 101

Intf name:      vlan201
Intf state:     Up                        IPv6 MTU:       1500
Description:    serwerownia komercyjna
Address:        2a02:c40:1::1             Prefix len:     48
Link local addr:fe80::230:88ff:fe12:5a0
Number of Bound Circuits (incl. dynamic) = 1

Bindings: (Total Bound Circuits 1)
Encapsulation  Circuit
dot1q          2/2 vlan-id 201
[bgp1]RedBack_SE100#ping 2a01:1d8:7fff:fffd:1::15
PING6 2a01:1d8:7fff:fffd:1::15 : 8 data bytes
timeout is 1 second, source 2a01:1d8:7fff:fffd:1::15
.....
--- 2a01:1d8:7fff:fffd:1::15 ping6 statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
[bgp1]RedBack_SE100#ping 2a01:1d8:7fff:fffd:1::16
PING6 2a01:1d8:7fff:fffd:1::16 : 8 data bytes
timeout is 1 second, source 2a01:1d8:7fff:fffd:1::15
.....
--- 2a01:1d8:7fff:fffd:1::16 ping6 statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
[bgp1]RedBack_SE100#

- clear nd cache done before ping.

Regards,
Marcin




 > Dave.
 >
 >
 > ------------------------------------------------
 > David Freedman
 > Group Network Engineering
 > Claranet Limited
 > http://www.clara.net
 >
 >
 >
 > -----Original Message-----
 > From: Marcin Kuczera [mailto:marcin at leon.pl]
 > Sent: Sun 3/29/2009 13:57
 > To: David Freedman
 > Cc: redback-nsp at puck.nether.net
 > Subject: Re: [rbak-nsp] ipv6 - strange ?? (ping)
 >
 > David Freedman wrote:
 >  > Can you paste output of your "show nd int" and "show nd neighbor" ?
 >
 > [bgp1]RedBack_SE100#show nd interface
 > Intf Grid  Mac Address       Status Circuit             IPv6 Address
 > 0x10000003 00:30:88:12:05:9f Up     2/1:1023:63/1/2/12
 > 2a01:1d8:7fff:fffd:1::15/126
 > 0x10000004 00:00:10:0b:31:21 Up     2/1:1023:63/1/2/13
 > 2001:7f8:42::a501:3000:1/64
 > 0x10000014 00:30:88:12:05:a0 Up     2/2:1023:63/1/2/40  2a02:c40:1::1/48
 > [bgp1]RedBack_SE100#show nd ne
 > [bgp1]RedBack_SE100#show nd neighbor
 > IPv6 Address                    Age    Link-layer Addr   State  Circuit
 > 2001:7f8:42::a500:8545:1        17     00:0c:29:d0:86:68 reach  2/1
 > vlan-id 102
 > 2001:7f8:42::a501:3000:1        0      00:00:10:0b:31:21 intf   2/1
 > vlan-id 102
 > 2a01:1d8:7fff:fffd:1::15        0      00:30:88:12:05:9f intf   2/1
 > vlan-id 101
 > 2a01:1d8:7fff:fffd:1::16        5      00:21:59:0c:2e:72 reach  2/1
 > vlan-id 101
 > 2a02:c40:1::1                   0      00:30:88:12:05:a0 intf   2/2
 > vlan-id 201
 > 2a02:c40:1::2                   39     00:02:b3:26:44:95 reach  2/2
 > vlan-id 201
 > fe80::20e:38ff:fe67:f908        0      00:0e:38:67:f9:08 incmp  2/1
 > vlan-id 102
 > fe80::230:88ff:fe12:59e         0      00:30:88:12:05:9f intf   2/1
 > vlan-id 101
 > fe80::230:88ff:fe12:5a0         0      00:30:88:12:05:a0 intf   2/2
 > vlan-id 201
 > [bgp1]RedBack_SE100#
 >
 > (link-local for vlan101 is modified by me)
 >
 > MArcin
 >
 >
 >
 >
 >  >
 >  > ------------------------------------------------
 >  > David Freedman
 >  > Group Network Engineering
 >  > Claranet Limited
 >  > http://www.clara.net
 >  >
 >  >
 >  >
 >  > -----Original Message-----
 >  > From: Marcin Kuczera [mailto:marcin at leon.pl]
 >  > Sent: Sun 3/29/2009 13:39
 >  > To: David Freedman
 >  > Cc: redback-nsp at puck.nether.net
 >  > Subject: Re: [rbak-nsp] ipv6 - strange ?? (ping)
 >  >
 >  > David Freedman wrote:
 >  >  >
 >  >  > Your output is a bit hard to parse , but I can see you have two 
link
 >  >  > local addresses the same :
 >  >  >
 >  >  >  > Intf name:      vlan101
 >  >  >  >        Link local addr:fe80::230:88ff:fe12:59f  Number of Bound
 >  > Circuits
 >  >  >  >
 >  >  >  > Intf name:      vlan102
 >  >  >  >        Link local addr:fe80::230:88ff:fe12:59f  Number of Bound
 >  > Circuits
 >  >
 >  > you are right, that's strage.. but - assigned automatically
 >  >
 >  >  > Can you ping vlan201 (which has a different link-local)?
 >  >
 >  > nope..
 >  > [bgp1]RedBack_SE100#ping 2a02:c40:1::1
 >  > PING6 2a02:c40:1::1 : 8 data bytes
 >  > timeout is 1 second, source 2a02:c40:1::1
 >  > .....
 >  > --- 2a02:c40:1::1 ping6 statistics ---
 >  > 5 packets transmitted, 0 packets received, 100% packet loss
 >  > [bgp1]RedBack_SE100#
 >  >
 >  >  > According to RFC, these should be "scoped" if they are going to be
 >  >  > shared, but I don't
 >  >  > see any evidence of scoping going on here.
 >  >  >
 >  >  > As a test, can you try changing link-local address of one of 
the vlans
 >  >  > to something else?
 >  >
 >  > I did, but it didn't help...
 >  >
 >  > Marcin
 >  >
 >  >
 >  >
 >  >  > Dave.
 >  >  >
 >  >  >
 >  >  > ------------------------------------------------
 >  >  > David Freedman
 >  >  > Group Network Engineering
 >  >  > Claranet Limited
 >  >  > http://www.clara.net
 >  >  >
 >  >  >
 >  >  >
 >  >  > -----Original Message-----
 >  >  > From: Marcin Kuczera [mailto:marcin at leon.pl]
 >  >  > Sent: Sun 3/29/2009 12:58
 >  >  > To: David Freedman
 >  >  > Cc: redback-nsp at puck.nether.net
 >  >  > Subject: Re: [rbak-nsp] ipv6 - strange ?? (ping)
 >  >  >
 >  >  > David Freedman wrote:
 >  >  >  >
 >  >  >  > What is the source IPv6 interface for your pings?
 >  >  >
 >  >  > Look - the ping goes to the other end of p2p interface (vlan102 
is p2mp,
 >  >  > because it is IX).
 >  >  > So - i.e. for vlan101 if I ping 2a01:1d8:7fff:fffd:1::16, the 
source is
 >  >  > 2a01:1d8:7fff:fffd:1::15 (from outgoing interface, just like in 
ipv4).
 >  >  >
 >  >  >  > Is it reachable by all the destinations you are pinging?
 >  >  >
 >  >  > yes, I'am pinging point-to-point ends..
 >  >  > The biggest problem is with... pinging myself !
 >  >  >
 >  >  >  > Also, do you have an admin acl in place on the context?
 >  >  >
 >  >  > no ACLs.
 >  >  >
 >  >  > At the first interface setup (vlan101) both ends were 
responding, after
 >  >  > adding vlan102 ipv6 everything started behaving strange..
 >  >  >
 >  >  > Regards,
 >  >  > Marcin
 >  >  >
 >  >  >
 >  >  >
 >  >  >  >
 >  >  >  > ------------------------------------------------
 >  >  >  > David Freedman
 >  >  >  > Group Network Engineering
 >  >  >  > Claranet Limited
 >  >  >  > http://www.clara.net
 >  >  >  >
 >  >  >  >
 >  >  >  >
 >  >  >  > -----Original Message-----
 >  >  >  > From: redback-nsp-bounces at puck.nether.net on behalf of 
Marcin Kuczera
 >  >  >  > Sent: Sun 3/29/2009 11:41
 >  >  >  > To: redback-nsp at puck.nether.net
 >  >  >  > Subject: [rbak-nsp] ipv6 - strange ?? (ping)
 >  >  >  >
 >  >  >  >
 >  >  >  >
 >  >  >  > Look at that, I have IPv6 /32 prefix, advertised via BGP.
 >  >  >  > Both peers are UP.
 >  >  >  > Neighbor              AS  MsgRcvd  MsgSent    TblVer  InQ 
OutQ Rst
 >  >  >  > Up/Down  PfxRcvd/Sent
 >  >  >  > 2001:7f8:42::a500:8545:1     8545     3095     3491 
22392    > 0    0
 >  >  >  >   14    2d01h     38      1
 >  >  >  > 2a01:1d8:7fff:fffd:1::16    15744    11432     7919 
22392    > 0    0
 >  >  >  >    4    2d08h   1579      1
 >  >  >  >
 >  >  >  > My interfaces:
 >  >  >  >
 >  >  >  > Intf name:      vlan101
 >  >  >  > Intf state:     Up                        IPv6 MTU:       1500
 >  >  >  >        Description:    Silweb
 >  >  >  > Address:        2a01:1d8:7fff:fffd:1::15  Prefix len:     126
 >  >  >  >        Link local addr:fe80::230:88ff:fe12:59f  Number of Bound
 >  > Circuits
 >  >  >  > (incl. dynamic) = 1
 >  >  >  >
 >  >  >  > Intf name:      vlan102
 >  >  >  > Intf state:     Up                        IPv6 MTU:       1500
 >  >  >  >        Description:    PLIX
 >  >  >  > Address:        2001:7f8:42::a501:3000:1  Prefix len:     64
 >  >  >  >        Link local addr:fe80::230:88ff:fe12:59f  Number of Bound
 >  > Circuits
 >  >  >  > (incl. dynamic) = 1
 >  >  >  >
 >  >  >  > Intf name:      vlan201
 >  >  >  > Intf state:     Up                        IPv6 MTU:       1500
 >  >  >  >        Description:    serwerownia komercyjna
 >  >  >  > Address:        2a02:c40:1::1             Prefix len:     48
 >  >  >  >        Link local addr:fe80::230:88ff:fe12:5a0  Number of Bound
 >  > Circuits
 >  >  >  > (incl. dynamic) = 1
 >  >  >  >
 >  >  >  > ##################
 >  >  >  > now - the problem (vlan101):
 >  >  >  > [bgp1]RedBack_SE100#ping 2a01:1d8:7fff:fffd:1::15
 >  >  >  > PING6 2a01:1d8:7fff:fffd:1::15 : 8 data bytes
 >  >  >  > timeout is 1 second, source 2a01:1d8:7fff:fffd:1::15
 >  >  >  > .....
 >  >  >  > --- 2a01:1d8:7fff:fffd:1::15 ping6 statistics ---
 >  >  >  > 5 packets transmitted, 0 packets received, 100% packet loss
 >  >  >  > [bgp1]RedBack_SE100#ping 2a01:1d8:7fff:fffd:1::16
 >  >  >  > PING6 2a01:1d8:7fff:fffd:1::16 : 8 data bytes
 >  >  >  > timeout is 1 second, source 2a01:1d8:7fff:fffd:1::15
 >  >  >  > .....
 >  >  >  > --- 2a01:1d8:7fff:fffd:1::16 ping6 statistics ---
 >  >  >  > 5 packets transmitted, 0 packets received, 100% packet loss
 >  >  >  >
 >  >  >  > 1  2a01:1d8:7fff:fffd:1::15  3.955 ms  3.489 ms  3.761 ms
 >  >  >  > [bgp1]RedBack_SE100#trace 2a01:1d8:7fff:fffd:1::16
 >  >  >  > traceroute6 to 2a01:1d8:7fff:fffd:1::16 from 
2a01:1d8:7fff:fffd:1::15,
 >  >  >  > 30 hops max, 12 byte packets
 >  >  >  > 1  * * *
 >  >  >  > ^C[bgp1]RedBack_SE100#trace 2a01:1d8:7fff:fffd:1::15
 >  >  >  > traceroute6 to 2a01:1d8:7fff:fffd:1::15 from 
2a01:1d8:7fff:fffd:1::15,
 >  >  >  > 30 hops max, 12 byte packets
 >  >  >  > 1  2a01:1d8:7fff:fffd:1::15  4.172 ms  1.481 ms  1.656 ms
 >  >  >  >
 >  >  >  > (vlan102):
 >  >  >  > [bgp1]RedBack_SE100#ping 2001:7f8:42::a500:8545:1
 >  >  >  > PING6 2001:7f8:42::a500:8545:1 : 8 data bytes
 >  >  >  > timeout is 1 second, source 2001:7f8:42::a501:3000:1
 >  >  >  > !!!!!
 >  >  >  >
 >  >  >  > --- 2001:7f8:42::a500:8545:1 ping6 statistics ---
 >  >  >  > 5 packets transmitted, 5 packets received, 0% packet loss
 >  >  >  > round-trip min/avg/max/std-dev = 6.649/7.014/7.445/0.317 ms
 >  >  >  > [bgp1]RedBack_SE100#ping 2001:7f8:42::a501:3000:1
 >  >  >  > PING6 2001:7f8:42::a501:3000:1 : 8 data bytes
 >  >  >  > timeout is 1 second, source 2001:7f8:42::a501:3000:1
 >  >  >  > .....
 >  >  >  > --- 2001:7f8:42::a501:3000:1 ping6 statistics ---
 >  >  >  > 5 packets transmitted, 0 packets received, 100% packet loss
 >  >  >  > [bgp1]RedBack_SE100#trace 2001:7f8:42::a501:3000:1
 >  >  >  > traceroute6 to 2001:7f8:42::a501:3000:1 from 
2001:7f8:42::a501:3000:1,
 >  >  >  > 30 hops max, 12 byte packets
 >  >  >  > 1  2001:7f8:42::a501:3000:1  3.839 ms  2.355 ms  2.785 ms
 >  >  >  >
 >  >  >  >
 >  >  >  > What is going wrong ???
 >  >  >  > Is it so unstable or what ???
 >  >  >  > SEOS 6.1.4.1.p4
 >  >  >  >
 >  >  >  >
 >  >  >  > Regards,
 >  >  >  > Marcin
 >  >  >  >
 >  >  >  >
 >  >  >  >
 >  >  >  > _______________________________________________
 >  >  >  > redback-nsp mailing list
 >  >  >  > redback-nsp at puck.nether.net
 >  >  >  > https://puck.nether.net/mailman/listinfo/redback-nsp
 >  >  >  >
 >  >  >
 >  >  >
 >  >
 >  >
 >
 >




More information about the redback-nsp mailing list