[c-nsp] Cisco ME3600X and Bridge-Domain Routing config question

Mark Tinka mtinka at globaltransit.net
Mon Nov 14 05:30:38 EST 2011


On Monday, November 14, 2011 05:37:18 PM Reuben Farrelly wrote:

> sw1.qld(config-if)# ip address XXX.XXX.96.69
> 255.255.255.252 %IP address cannot be configured on
> bridge domain 780 EFP & Switchports or EFPs
> sw1.qld(config-if)#

I dumped your configuration into two ME3600X's we
have running IOS 12.2(52)EY2a and 15.1(2)EY in our lab, 
and they both work:

On the unit with 12.2(52)EY2a:

lab(config)#int GigabitEthernet0/2
lab(config-if)# switchport trunk allowed vlan none
lab(config-if)#  switchport mode trunk
lab(config-if)#  service instance 780 ethernet
lab(config-if-srv)#encapsulation untagged 
lab(config-if-srv)#bridge-domain 780
Bridge-domain 780 created
VLAN 780 does not exist, creating vlan
lab(config-if-srv)#exit
lab(config-if)#int vlan780
lab(config-if)#ip add
lab(config-if)#ip address 192.168.1.1 255.255.255.252
lab(config-if)#end
lab#sh ver | i IOS
Cisco IOS Software, ME360x Software (ME360x-UNIVERSALK9-M), Version 12.2(52)EY2a, RELEASE SOFTWARE (fc1)
lab#


On the unit with 15.1(2)EY:

lab(config)#int gi0/4
lab(config-if)#switchport trunk allowed vlan none
lab(config-if)# switchport mode trunk
lab(config-if)# no cdp enable
lab(config-if)#service instance 780 ethernet
lab(config-if-srv)#   encapsulation untagged
lab(config-if-srv)#   bridge-domain 780
Bridge-domain 780 created
VLAN 780 does not exist, creating vlan
lab(config-if-srv)#exit
lab(config-if)#int vlan780
lab(config-if)#ip address 192.168.1.1 255.255.255.252
lab(config-if)#do sh ver | i IOS
Cisco IOS Software, ME360x Software (ME360x-UNIVERSALK9-M), Version 15.1(2)EY, RELEASE SOFTWARE (fc1)
lab(config-if)#

> Ok now I'm confused.  The documentation example doesn't
> work either. I'm not too sure where to look next.
> 
> What exactly am I doing wrong?

Interesting...

I'd have suspected licensing issues, but I can't be
certain whether this is an issue. We use the 
"AdvancedMetroIPAccess" license here.

Check out Table 4 here:

http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/12.2_52_ey/release/notes/ol23402.html#wp944314

Maybe Waris can weigh in here.

> I'm running 12.2(52)EY3a on the switches and I cannot
> upgrade to 15.1(2)EY as the units will not link up ports
> with hardcoded speed and duplex (CSCtr83418) and also
> won't switch IPv6 traffic through the switch
> (CSCtr83500) either, even if configured only for IPv4,

Thanks for this information. Unfortunately, the bug ID's
aren't open to the public. I'll have to ask our SE to
"decode" them for us.

We're anxious to upgrade to later code to get a number of
features, not least of which is IPv6, but given the number
of boxes in the network and how young the code still is, 
we're giving it several more months before we do so.

The box is sweet, but is being let down by the code.

> so we're stuck on the old release until some code comes
> out which doesn't break more than it fixes.  Is this
> doable in 15.1(2)EY though anyway?

As you can see from the above.

> > Which reminds me, where -is- 15.1(2)EY rebuild which was
> planned for September, then 30th October, and now it's
> mid November and it's still MIA?  IPv6 anyone?

You know how release dates. Always plan for them to be
off :-).

Cheers,

Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20111114/5aedf8cb/attachment-0001.pgp>


More information about the cisco-nsp mailing list