User guide

Configuring Network Services Profile Management
450
AlliedView NMS Administration Guide
Note: The table used to display the Port Profile usage will be that same table that indicates the Customer ID associated with each
port. This panel is named “Configured Ports”.
1. Select the “Ports” panel under the Network Inventory Object.
2. The Ports panel will contain a table that lists the configured ports in the network. The columns in the table include the
device/slot/port of the port, the customer id associated with the port, and the Port Profile associated with the port with an
indication as to whether the port configuration is in sync with the Port Profile settings defined in the NMS.
6.10.9.2 Viewing Profile to Device Associations
The user can view a list of devices that indicate which Device Profile each of the devices is currently using. This view will also
indicate whether the parameters set on the device are still consistent with the Device Profile defined on the NMS.
1. Select the “Profile Association” panel under “Nodes”.
2. The Profile Association panel will contain a table that lists the devices in the network. The columns in the table include
the name, type, ip address, and Device Profile with an indication whether the device configuration is in sync with the Device
Profile settings defined in the NMS.
6.10.10 Keeping the Profile Parameters and Ports/Devices in Sync
Over time, either through the NMS or directly with the devices, the user can make changes to the devices or ports so that
they are no longer in sync with the configuration defined in the Profiles. The NMS must discover this discrepancy and keep
the Ports and Profile Association Panels up to date.
• To check for changes made directly to the device that affect the device level configuration, the NMS rediscovery process
compares the values on the device with the Device Profile that was applied to it and update the Node table accordingly.
This means that a change on the device will go undetected by the NMS only until the next rediscovery of the device is
automatically invoked by the NMS.
• To check for changes made directly to the device that affect the port configuration, the NMS rediscovery process will
compare the port configuration on the device with the Port Profile that was applied to it and update the Configured
Ports table accordingly. This means that a change on the device will go undetected by the NMS only until the next
rediscovery of the device is automatically invoked by the NMS.
• For changes made through the NMS, the applications that make the changes to a device or port will update the NMS
tables immediately.
Note: When a profile is out of sync with what has been defined on the device, a “*” is next to the profile name in the Profile column
of the Port or Device table.
6.10.11 Coordination of External and NMS Profiles
As described above, the AlliedView NMS profiles operate at the network service level; a profile is created for a card type or
port type, and can then be applied to multiple interfaces over multiple devices. Moreover, the profiles include a more global
set of attributes, such as traffic and performance management attributes. Finally, the profiles are filled out using pull-down
menus and GUIs, ensuring there is less chance of error.
For the iMAP, prior to release 11.0, if a Profile was created at the NMS and applied to an interface, the iMAP output for the
interface would not show that an NMS profile had been applied.
In release 11.0, this is changed; when the NMS sets the port attributes by deploying an NMS profile, the
SHOW INTERFACE
command on the iMAP displays the NMS profile name that has been applied as an External Profile name. Moreover, if at the
NMS a port is de provisioned, the iMAP output for External Profile is set to None.
At the NMS, when an iMAP port is displayed, the current value of the External Profile name will be displayed at or near the
bottom of the view-only attributes, labeled “Interface Profile Name”. Normally this name will match the Profile name
deployed by the NMS (displayed upper right). Refer to the following figure.