[c-nsp] Resilient Ethernet Protocol (REP)
Dimitris Befas
dimitris.befas at gmail.com
Thu Jan 11 08:49:17 EST 2018
Actually you have to be able to transport the following frames:
1. LSL (hellos) (untagged frames towards multicast mac 01:80:c2:00:00:00)
2. HFL (link failures etc) (REP admin vlan (un)tagged towards multicast mac
01:00:0c:cc:cc:ce)
The proposed configuration of Michalis works fine if you can dedicate the
whole interface.
On Jan 11, 2018 15:28, <michalis.bersimis at hq.cyta.gr> wrote:
> I don't have a ME3600 that in ME3800 I have used the following
> configuration , which applies only xconnect to the whole interface, and can
> pass all frames inside the EoMPLS tunnel
>
>
> Me 3600 PE1:
> interface GigabitEthernet0/xx
> no switchport
> mtu 9216
> no ip address
> service-policy input ratelimit_200Mb
> xconnect xxx.xxx.xxx.xxx 100 encapsulation mpls
>
> Me 3600 PE2:
> interface GigabitEthernet0/yy
> no switchport
> mtu 9216
> no ip address
> service-policy input ratelimit_200Mb
> xconnect yyy.yyy.yyy.yyy 100 encapsulation mpls
>
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
More information about the cisco-nsp
mailing list