cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
828
Views
0
Helpful
1
Replies

Bug in 15.0(1)SE2 for 3560/3750 - IPv6 Loopback Interface?

I have two 3560 switches - a 3560G-24 and a 3560-48.  I am running the latest IOS release on each switch - 15.0(1)SE2 on the 3560G and 12.2(55)SE5 on the 3560.  I am running the same SDM template on each (desktop IPv4 and IPv6 default) and have IPv6 running.  The two switches share a common VLAN to a WAN router with a /64 IPv6 network, OSPFv3 is running on this and I have route visibility and full connectivity.  The WAN router and the two switches each have a loopback interface that has a /128 IPv6 address with OSPFv3 enabled.  The routing table contains these /128 networks.  I cannot access the interface on the 3560G but have no issues with the 3560.  The only difference I can see is the IOS version.

!3560G

interface Loopback0

ipv6 address xxxx:xxxx:xxxx:FFFF::2/128

ipv6 enable

ipv6 ospf 1 area 0

!3560

interface Loopback0

ipv6 address xxxx:xxxx:xxxx:FFFF::3/128

ipv6 enable

ipv6 ospf 1 area 0

!WAN Router

interface Loopback0

ipv6 address xxxx:xxxx:xxxx:FFFF::1/128

ipv6 enable

ipv6 ospf 1 area 0

Of the debugging I have done it appears the packets are hitting the 3560G but it isn't 'seeing' them.

I think this is a bug but can't seem to find any more information regarding it?

Andy

1 Reply 1

Although not in the release notes this has been fixed in 15.0(2)SE.

Andy

Review Cisco Networking for a $25 gift card