Table of Contents
Advertisement
Configuring ERP
•
Deleting an ERP service VLAN and it's associated NNI ports is only allowed when the ERP ring itself
is deleted using the no for of the erp-ring command. None of the VLAN Stacking CLI commands can
remove a service VLAN consisting of an NNI-SVLAN association.
Configuring ERP Protected SVLANs
An SVLAN becomes an ERP protected SVLAN when the SVLAN is associated with two NNI ports that
also serve as ring ports. In this case, the SVLAN is automatically protected as part of the association with
NNI ring ports.
The following sequence of configuration commands provides an example of how SVLANs are automati-
cally added as protected SVLANs to an ERP ring:
-> ethernet-service svlan 100
-> ethernet-service svlan 200
-> ethernet-service svlan 300
-> ethernet-service svlan 400
-> ethernet-service svlan 100 nni port 1/1-2
-> ethernet-service svlan 200 nni port 1/1-2
-> ethernet-service svlan 300 nni port 1/1-2
-> erp-ring 10 port1 1/1 port 2 1/2 service-vlan 400 level 1
In the above example:
•
SVLANs 100, 200, and 300 are automatically added as protected VLANs when the ring is created.
This is due to the NNI ports being part of ERP ring 10.
•
SVLAN 400 is also automatically added as a protected VLAN when it is configured as the service
VLAN for the ring.
Use the
show erp
command to verify the configured VLAN Stacking ERP ring configuration. For more
information about these commands, see the OmniSwitch CLI Reference Guide.
OmniSwitch AOS Release 7 Network Configuration Guide
March 2011
Configuring an ERP Ring
page 9-15
Advertisement
Table of Contents
