ME3600 EVC config

Unanswered Question
Feb 26th, 2012

I am new to metro ethernet and have two ME3600x switches.  We are connecting multiple customers between to locations  and I'd like to map them to different EVC's between the two metro switches at each location.  I am attaching a diagram of a proposed architecture.  can anyone assist/recommend a config.  The link tothe SP network between ME3600's is a dedicated ME private line service.  Thanks for any assistance.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 0 (0 ratings)
waris Mon, 02/27/2012 - 12:26

What is the interface configuration between the two ME? Is it trunk?

At UNI, you can match on encap 16, match on untagged and match on the entire range for the trunk. The core interface is important since it may add second tag.

Refer to ME3600X configuration guide for detailed interface configuration.

http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/release/12.2_52_ey/configuration/guide/swevc.html

-Waris

bmarms Wed, 03/07/2012 - 06:31

I was able to get my metro switches configured and working properly but am having an issue accessing the MGMT port from my NMS station attached to CoreA. (see attached image).  I can access the other switch OOB MGMT ports from the NMS attached to CoreA but not the metro.  I can access the metro OOB MGMT port from CoreB.  Any ideas?

kishore.chennupati Sat, 03/10/2012 - 05:08

are the apprioprate vlans trunked across the ME3600's??? looks like your OOB vlans are not trunked across??

bmarms Sat, 03/10/2012 - 05:13

The OOB vlan is trunked across the .1q link to the metro switch from the core switch. The Mac address of the OOB interface is not being dynamically learned on CoreA for some reason. I entered a static entry in the CoreA cam table, but I still can't access from my NMS. I have a TAC case open, but they've been unable to resolve.

Sent from Cisco Technical Support iPhone App

bmarms Sat, 03/10/2012 - 05:15

should also mention the metro is configured to match on a range of vlans as well as untagged traffic from the CoreA and B switches

Sent from Cisco Technical Support iPhone App

kishore.chennupati Sat, 03/10/2012 - 05:33

what model is the core A switch?? is it only the OOB vlan that is having issues or other vlans as well?? does the ME3600X on the right side see the mac address of the say CoreB mgmt interface??

bmarms Sat, 03/10/2012 - 05:43

Both cores are 6500's. I can access every other device on the OOB vlan from either side EXCEPT the metros. So, from the core a side I can't get to the b side metro. From the core b side, I can't get to the a side metro. I can get to everything else on the OOB vlan

Sent from Cisco Technical Support iPhone App

bmarms Tue, 03/13/2012 - 10:46

This is an IOS bug wehre the metro is only checking the first 40 bits of the source mac, vs all 48, on ingress and dropping the frame since it is recognizing it as itself.  cisco is releasing a new IOS version to fix this bug on 3/19/2012

Actions

Login or Register to take actions

This Discussion

Posted February 26, 2012 at 12:19 PM
Stats:
Replies:8 Avg. Rating:
Views:1900 Votes:0
Shares:0
Tags: No tags.

Discussions Leaderboard