User guide

VLAN Translations Configuration Profile Management
6-53
AlliedView NMS Administration Guide (Configuring Network Services)
• ADSL24A/B, SHDSL24, ADSL24SA, ADSL24AE, NTE8, VDSL24A/B, ADSL48A/B (customer interfaces)
• The following cards do not support VLAN translation:
• CES8, EPON2
• The Port-based HVLAN and translation feature are not compatible on the same port. Once a port is configured with the
HVLAN option, it cannot use the translation feature, and vice-versa. This applies to the cards that support both of these
features (GE3, XE1, GE8).
• The FE/FX10 does not support both translated and non-translated VLANs on the same port in order to avoid the mixing
of a non-translated VLAN traffic onto translated VLAN traffic (which is undesirable) and as such will drop non-trans-
lated VLANs. The other card types that support translation do not drop non-translated traffic. Users should be careful in
their network design to ensure this.
6.10 Profile Management
In the AlliedView NMS, a profile is a set of configuration parameters that is given a unique name. This profile can then be
applied to an object (device or port) in the network.
Note: The interactions between device-based and network-based Profiles are explained in Section 6.10.11.
The following subsections explain Profile Management as follows:
• Profile Configuration - The creation, modification, and deletion of the profiles on the NMS.
• Profile Deployment - The application of the profiles defined in NMS to selected objects (devices or ports) in the network.
• Profile Monitoring - The monitoring of the devices and ports in the network to keep the NMS user informed as to which
devices or ports are using which profiles, and whether the configuration of the devices or ports continues to match the
Profile that was applied to it.