User guide

Configuring Network Services Profile Management
438
AlliedView NMS Administration Guide
Note: For profiles for EPON interfaces and their QoS policies, refer to 6.11.11. Note that the iMAP_EPON device class in QOS
policies/actions is an 'exclusive' device class; a policy or flow cannot be used with any other device-class once assigned to the
iMAP_EPON device class.
Note: For the ADSL port profile the user can specify for a service VLAN the VC (0-3) as well as the VPI, VCI, and framing.
Note: The ADSL-Bond profile is used to support the G.bond (ITU G.998) for ADSL interfaces. It includes references to a primary and
secondary ADSL port profile. Refer to 6.10.12.
Note: Port Direction is available for the port profile for ether-like ports. Using the port profile, you can set the port direction on all
ether-like cards, including the GE24POE. The setting can also be changed from the Service Management Form. For
information on the devices where this changing of port direction occurs and cautions, refer to 7.9.5 for iMG7x6MOD and
6.10.2.3 for GE24POE.
Note: Related to the previous Note, with the provisioning of iMG devices with 1G WAN ports, the default for the Etherlike port
Profile includes the field Direction (either Network or Customer). Moreover, the default for this field is changed to Customer
(rather than the implicit Network). As a result new port profiles should be created with the port direction set to match the
provisioning scenario in which they will be used. Otherwise, there will be an error when trying to deploy the profile. For
example, with the XE6 card, if the Direction is not explicitly set to Network, you will get the error message “Invalid
provisioning value.”
Note: For existing Ethernet port profiles these changes are not an issue, because they will not have the port direction field explicitly
set. However, new port profiles should be created with the port direction set to match the provisioning scenario in which they
will be used, as follows:
Note: For Etherlike, ADSL, SHDSL, and VDSL ports, the user can include the STP and BPDU Cop attributes. These are included in a
separate STP tab for the profiles. For information on STP parameters and the BPDU Cop feature, refer to the iMAP
documentation.
Following are the device level parameters associated with the profile types.
• Rapier
• HWPRIORITY (Priority to COS Queue mapping)
• MAXPACKETS, MAXLATENCY
• SwitchBlade 9800
• PRIORITYQUEUEING (enable/disable and setting to QOS or VLANPRIORITY)
• HWSCHEDULER (STRICT, LOWERPRIORITY, or INTERNALMEM)
• VLANQUEUEMAP (Priority to COS Queue mapping)
• VLAN Tag User Priority Mapping (Enable/disable)
• VLANREMAP (Input priority to Output priority mapping)
• iMAP Device (7x00, 9x00)
• VLANQUEUEMAP (Priority to COS Queue mapping)
Table 6-7 lists the port parameters supported by Profile Management.
TABLE 6-7 Comparison of Ethernet Port Parameters for Profile Management
Parameter Rapier Device Switchblade / 9800 Device
iMAP Device
(9x00)
Speed/Duplex x x x
Broadcast limit x
Destination lookup failure limit x
Learn x