Information About EVC Local Connect
Benefits of EVC Local Connect
•
L2CP forwarding using hardware is enabled by mac-address-table evc-xconnect l2pt-forward-all
command. This ensures transparent control frames forwarding and avoid certain frames getting dropped
by CPU.
Prerequisites for EVC Local Connect
•
EVC Local connect requires advancedmetroipaccess licence.
•
Ensure EFPs are configured without any Bridge-Domain or Xconnect mapped to it.
Restrictions for EVC Local Connect
•
EVC Local connect is not supported on Port-Channel interfaces.
•
CFM is not supported on EVC which contains local connect.
•
L2 Protocol Peer and L2 Protocol Tunnel are not supported.
•
L2 Protocol forward is the default behavior.
•
Only Internal Ethernet Loopback is supported. External Ethernet Loopback is not supported.
•
EVC local connect over Trunk is not supported.
•
Port based local connect is not supported.
Scaling
•
Only 512 EVC Local connect sessions are supported. Maximum is 2048 allocated for scale and this
2048 will be shared between L2VPN and Local connect.
•
Local connect shares Internal Bridge-Domain space with L2VPN, following changes are supported.
◦
L2VPN counter will now be a combination of (EOMPLS tunnels , VPLS PW and 2 * Local connect
sessions)
◦
When 512 local connect sessions are configured, then you can configure only 1024 EOMPLS
sessions. When you configure the 1025th EOMPLS session the throw object download
error is displayed. Still all 1025 EOMPLS sessions are in UP state.
◦
After configuring 2048 EOMPLS successfully, if you configure a local connect session, an error
is displayed in syslog as resources are exhausted. All the 2048 EOMPLS and the local
connect session are in UP state.
Carrier Ethernet Configuration Guide (Cisco ASR 920 Series)
52
EVC Local Connect
Information About EVC Local Connect
To Next Page
Loading...
Need help?
General
