Re: 4321 interface configuration, Metro Ethernet, Point to Multipoint

the metro ethernet service provides you with a virtual single broadcast domain.

No special configuration is needed on the L2 CE nodes that can talk directly between each others.

How the service provider builds the service is transparent to you.

The only point of attention is the following:

the service can be provided at port level or for a single specific vlan-id in 802.1Q tag.

In the first case you are free to use untagged frames or tagged frames and it can support multiple Vlans.

So you could "divide" your flat topology by using Vlan based subinterfaces on the Head office devices.

If the service is vlan based you need to use the specified vlan-id in order to have your frames carried over the metro ethernet service.

Multiple broadcast domains could be built by using 802.1Q tunneling and double Vlan tags but this requires configuration on your switches.

With new service you are not going to peer with the SP for routing purposes (like it happens in MPLS L3 VPN) and you can use the routing protocol that you want your neighbors will be your own devices and not the ISP PE node.

If the number of remote sites is high a flat topology can be a problem.

If you only have two remote offices you can use the flat topology with no problems.

Re: 4321 interface configuration, Metro Ethernet, Point to Multipoint

We have 10 remote LANs so I was wanting to put a router for braodcasts plus I'm already setup for different IP's at the remote sites.

I thought about VLAN but I think I'm best served with routers. I'm just not sure how to setup the interfaces to do that. At the remote sites, it's a single interface no problem. I just need help with the configuration of the Main Site router.

Re: 4321 interface configuration, Metro Ethernet, Point to Multipoint

I have a test network setup.

After reading and thinking of the answers here, I decided to try having one 4321 at the HQ and have the remote 2960 MetroE come into sub interfaces on the router. I created vlans on the remote 2960 and matching sub interfaces on the 4321.

On the 4321, I can ping a pc on the remote 2960 network. On a pc on the 4321 local network, I can only ping the local ip and the local subinterface ip, but not across to remote 2960 interface.

On the remote 2960, I can only ping the 4321's two interfaces, the directly connected subinterface and the interface of the 4321's local network. A PC on remote 2960 pings across to both ip's on the 4321 subint and 4321 local network. Both the remote 2960 and the pc connected to the remote 2960 can not ping pass the router to the HQ network.

Enterprise Switching Business Unit is glad to announce Beta release 16.12.2 for all Catalyst 9200/9300/9400/9500/9600 and Catalyst 3650/3850 Platforms. This release is made available to allow users to test, evaluate and share fee...
view more

Purpose of the document
This document describes the general recommendations or best practices when designing and deploying the Cisco SD-Access technology. The document assumes that the reader has a general overview of Cisco's SD-Access for Distributed C...
view more

Do you currently have hands-on networking experience? If you do, we'd love to hear from you!
Your feedback will be reviewed and analyzed by our team to directly influence a networking management and monitoring product.
Take the 20-min or les...
view more