User guide

Provisioning the iMG/RG Installation Procedures
807
AlliedView NMS Administration Guide
FIGURE 7-134 Advanced Port Attributes - Custom VLANs
7.9.9 Error Conditions when Provisioning
7.9.9.1 Access Island and Open Access
Since provisioning each model involves a different VLAN configuration, the following steps will produce an error message:
• In both the RG General Profile and Service Profiles no service VLANs are datafilled
• There is conflict between the VLAN configuration in the iMG/RG General Profile and in the Service Profiles
• The Profiles and provisioned VLANs don’t match, and so the iMG/RG in the Inventory table will have a * under the
appropriate Profile
7.10 Installation Procedures
7.10.1 Overview
With the use of the AlliedView NMS profiles and DHCP, the installation, reconfiguration, and de-installation of iMGs/RGs
does not involve complex (and therefore error-prone) procedures. These procedures can be grouped into two main areas:
1. Installing, reconfiguring, and removing the iMG/RG using AlliedView NMS
2. Changing an iMG/RG that was not configured using the AlliedView NMS to one that does
In the first area, the initial installation of an iMG/RG (out of the box) includes most of the steps that are needed when
reconfiguring or removing the iMG/RG, in a different sequence.
A special procedure is the changing of the Customer ID, since certain steps must be followed to ensure the ID has been
changed. Refer to 7.10.10.
Note: The procedures here will assume that the user is performing these procedures for the Access Island. Whenever there is a
change in a step needed to accommodate the open Access model, this change will be highlighted.
Note: In release 10.0, NMS supports translations on the iMAP ports. For all of the following procedures, if the procedure includes
adding a translation (or translations) to the iMG/RG configuration, the iMAP port profile that includes the translation must be
applied before changes are made to the iMG/RG profiles.