|
|
The Cisco WAN Equipment Module supports provisioning of circuits across a subnetwork composed of BPX WAN switching nodes, IGX WAN switching nodes and MGX 8220 (formally known as AXIS and MGX 8850 feeder shelves.
The Cisco WAN Equipment Module supports the provisioning of ATM services across a backbone network of BPX switches. It supports the following BPX switching cards:
The Cisco WAN Equipment Module supports the following IGX switching cards:
The Cisco Equipment Module supports the provisioning of ATM, Frame Relay, FR-ATM Interworking, Circuit Emulation, and CE-ATM Interworking services for MGX 8220 feeder shelves (formerly known as AXIS). The Equipment Module supports the following MGX 8220 feeder shelf cards:
The Cisco Equipment Module supports the provisioning of ATM, Frame Relay, FR-ATM Interworking, Circuit Emulation, and CE-ATM Interworking services for MGX 8850 feeder shelves. The Equipment Module supports the following MGX 8850 shelf cards:
When configuring MGX 8850 feeder notes, the trap IP address should match theNWIP ATM IP address.
MGX 8850 firmware prohibits the proper deletion of circuits with VPI=0. To force CPC to bypass VPI=o during autogeneration, edit the $CCP CONFIG/syconfig.site file and add in the following line:
CS.8850NoVPIO = 1
| Vendor | Firmware | Version |
|---|---|---|
Cisco | BPX 8600 | 9.2.30 |
Cisco | MGX 8220 | 5.0.10 |
Cisco | MGX 8850 | 1.1.30 |
Cisco | IGX 8400 | 9.2.30 |
The Equipment Module uses the Cisco WAN Manager (CWM) through the Service Agent SNMP interface. The software requirements are highlighted below:
| Vendor | Product | Version | Notes |
|---|---|---|---|
Cisco | Cisco WAN Manager | 9.2.07, or 9.2.08 | Firmware in network elements must be compatible with this release. |
If you are using CWM 9.2.07then you must set CS.CWM9207SUPPORT=1 in the $CCP_CONFIG/syavconfig.site file. Remember to remove the "#" from the beginning of #CS.CWM9207SUPPORT=1.
The Equipment Module provides an event logging daemon to track event log changes from CWM. The daemon is started/stopped in the workstation boot and runs independently of CPC.
![]() |
Note In order to configure the CWM Equipment Module you must have installed it during the CPC Server and Client installation procedures. For more information about installing CPC, refer to the chapter titled "Initial Installation". |
To configure the Equipment Module to make CPC operational, you must complete the following steps:
Step 2 Account Installation
Step 3 Logging Account and Daemon Installation
Step 4 System Upload
Step 5 Upload (if configuration information has changed)
Step 6 Add Inter Network Links (Topology) Information
Step 7 Logical ports (as required)
Step 8 Element Profiles
Step 9 Cisco Equipment Module Maintenance
The Cisco WAN Equipment Module implements an overall timeout for service provisioning transactions. Network Timeout is defined by the environment variables CCP_ACTIVATION_TIMEOUT (Default=45 seconds) and CCP_RESET_TIMEOUT (Default=45 seconds). They define the maximum interval (measured in seconds) allowed for each service element activation and for the rollback of each service element, respectively. The maximum interval amounts to the maximum time that elapses before the NIF times out. For example, if CCP_ACTIVATION_TIMEOUT=180, the NIF is allowed three minutes to activate an item in an Transaction.
The default settings are used if the NIF detects that these variables are not set in the environment.
Network Timeout requires shutting down the server if it not already down, setting the variables and then restarting it to pick up the environment changes.
To set the CCP_ACTIVATION_TIMEOUT environment variable.
SYnpt -h
Step 2 Set the environment variable to an integer (measured in seconds) that amounts to the maximum time to elapse before the NIF times out:
export CCP_ACTIVATION_TIMEOUT=120
To set the CCP_RESET_TIMEOUT environment variable:
Step 3 Set the environment variable to an integer (measuredin seconds) that amounts to the maximum time to elapse before the NIF times out:
export CCP_RESET_TIMEOUT=90
Step 4 Bring CPC up by sourcing the server environment. To source the environment, run the following commands in succession:
cd /opt/SU/CPC/Server/mng/utility . syccpovdef
An upload account is required to enable uploads from the network. An upload account is required on every CWM host in your network.
Step 2 Login as the root account on the CWM host. Use admintool or the procedure you would normally use to create new login accounts to create the sycsupld account. Use the account settings listed in Table 8-2
| Account Parameter | Example Value | Notes |
|---|---|---|
User Name | sycsupld | sycsupld is recommended, because this is the default used in several areas. |
User ID | 1004 | User ID is not critical |
Primary Group | 10 | Group ID is not critical |
Secondary Group |
| None required |
Comment | CPC Upload Account |
|
Login Shell | Korn (/bin/ksh) | The Korn shell is mandatory. |
Password | Normal Password | Expiry features are optional. You should not set your password to expire. |
Create Home Dir | Yes | Home directory is required for .profile file |
Path | /disk1/users/sycsupld | Home directory is required--use whatever path is appropriate for new user login accounts in your organization |
Step 3 In the home directory of the sycsupld account, create or edit the .profile file to set the following environment variables:
export ONCONFIG=onconfig.CWMHost
export INFORMIXDIR=/usr/users/informix
export INFORMIXSERVER=CWMHost
export PATH=$PATH:$INFORMIXDIR/bin
export PS1="<${LOGNAME}@$(hostname)>"
Step 4 Login as the sycsupld on the CWM host.
Step 5 Test the account configuration by using the Informix utility dbaccess to verify access to the CWM database db_access.
Step 6 Place a copy of the CSSVPlusInstall.tar file in the sycsupld home directory. The file is found in the /opt/CPC/Server/mng/template directory on the CPC Server host.
Step 7 On the CWM host, execute the following commands to install the CPC upload procedures into the CWM database:
cd $HOME tar xvf CSSVPlusInstall.tar cd CSSVPlusInstall installSql <stratacom>
![]() |
Note Ignore any Informix 674/111 errors which may occur; these are harmless. |
Step 8 On the CPC Server host, in a runtime environment, edit the userId and password of the upload account in the syavconfig.site file in the $CCP_CONFIG directory. CS.UPLDACCT should be edited to be the same as the CWM host upload account User Name and CS.UPLDPASS should be edited to be the same as the CWM host upload account password. Execute the following commands:
cd $CCP CONFIG vi syavconfig.site CS.UPLDACCT=sycsupld CS.UPLDPASS=trustno1
Step 9 If CPC is running, allow it to recognize the changed values in the syavconfig.site file by entering:
SYnpt -r
![]() |
Note Perform step 8 in the event that the upload account userId or password changes. |
An event logging account and daemon must be installed on the CPC Server host for any event logging to become operational. The event logging features can be installed only after the upload account(s) has been installed.
Step 2 In the home directory of the sycsevnt account, create or edit the .profile file to set the following:
| Account Parameter | Example Value | Notes |
|---|---|---|
User Name | sycsevnt | sycsevnt is recommended, because this is the default used in several areas. |
User ID | 1004 | User ID is not critical |
Primary Group | 10 | Group ID must be the same as CPC server user group |
Secondary Group |
| None required |
Comment | CPC Event Logging Account |
|
Login Shell | Korn (/bin/ksh) | The Korn shell is mandatory. |
Password | Normal Password | Expiry features are optional. You should not set your password to expire. |
Create Home Dir | Yes | Home directory is required for a .profile file. |
Path | /disk1/users/sycsevnt | Home directory is required--use whatever path is appropriate for new user login accounts in your organization |
Step 3 environment variables (as per the CPC Administrator account):
export INFORMIXDIR=<informix_path>
export ONCONFIG=<onconfig_file>
export INFORMIXSERVER=<informix_server>
export PATH=$PATH:$INFORMIXDIR/bin
. /opt/CPC/Server/mng/utility/syccpovdef
export PS1="<${LOGNAME}@$( hostname )>"
Step 4 Login as sycsevnt on the CPC Server hosts and execute the following commands:
cp /opt/CPC/Client/mng/template/CSEventLogger.tar $HOME cd $HOME tar xvf CSEventLogger.tar
This will create a subdirectory called CSEventLogger containing a number of files.
Step 5 Sign on as the root and copy the file CSeventCtrl from the user /disk1/users/sycsevnt/CSEventLogger directory into the /etc/init.d directory.
![]() |
Note If the event logging account is not sycsevnt, edit CSeventCtrl and csnetworkname (where networkname is the name of the network) as directed by the internal comments. If the event logging account password is not trustno1, edit csnetworkname as directed by the internal comments. |
Step 6 Execute the following commands:
cd /etc/rc3.d ln -s /etc/init.d/CSeventCtrl SssCSeventCtrl cd /etc/rc2.d ln -s /etc/init.d/CSeventCtrl KkkCSeventCtrl
The ss/kk values should be selected to be consistent with other start/shutdown scripts. In addition, when the daemon starts, it assumes that the CWM Informix server has been started.
Step 7 On the CPC Client host, in a runtime environment, edit the userId and password of the event logging account in the syavconfig.site file in the $CCP_CONFIG directory. CS.EVNTACCT should be edited to be the same as the CWM host event logging account User Name and CS.EVNTPASS should be edited to be the same as the CWM host event logging account password.
Step 8 Sign on to the event logging account and edit the CSevent.ksh file (located in the $HOME/CSEventLogger directory), as directed by the internal comments. This must be done any time when networks are added or deleted in CPC.
Step 9 When CPC is running, the daemon polls for network node and fabric changes at a default rate of once per hour. To change this rate, set the environment variable CSEVENTPOLLTIME in the .profile file of the event logging account to the desired number of seconds between polls.
Step 10 To implement the above changes, execute:
/usr/sbin/shutdown y g0 i6
In the event that the event logging account userId or password changes, perform the following steps:
Step 2 On the CPC Client host, in a runtime environment, edit the user Id and password of the event logging account in the syavconfig.site file in the $CCP_CONFIG directory. CS_EVNTACCT should be edited to be the same as the CWM host event logging account User Name and CS.EVNTPASS should be edited to be the same as the CWM host event logging account password.
Step 3 Execute:
/usr/sbin/shutdown -y -g0 -i6
In order to provision services, the CPC database must have detailed knowledge of the managed subnetworks. Using a procedure called upload, objects are created within the CPC database that represent objects of the managed network (for example, objects managed by CWM). The upload function takes precedence over any Transactions which are running at the time of upload. If the upload function makes a change back to the fabric which affects a running Transaction (such as deleting a logical port that the threader has decided to use) then this Transaction fails and must be restarted.
CPC supports the following types of upload:
![]() |
Note The term upload does not refer to the creation of inter-network links because they are outside the scope of any single Equipment Module. See the section titled "Adding Inter-Network Links (Topology) Information" later in this chapter. |
Depending on network load, CWM activity, and other factors, network changes may not be stored in the CWM database for several minutes. An CPC upload performed in the interval before the network change is stored in the CWM database will result in the new network changes, such as the creation of new circuits, not being uploaded.
A network object must be created in order to perform an Upload.
One network object must be created for each network managed by Cisco WAN Manager. The following steps explain how to create and upload a network object.
Step 2 Click the Cisco WAN Network folder to highlight it.
Step 3 Click a Cisco WAN Network object folder to highlight it.
Step 4 Click the Subset Viewer button on toolbar.
Step 5 Enter the attribute values in the available row of cells.
Step 6 When creating a network object, the Subset Viewer provides the following attribute fields:
Step 7 Save the network object by clicking the save button on the toolbar.
Step 8 Apply the Transaction by clicking the apply button on the toolbar.
Step 9 To specify other attributes, click a cell in the row to highlight the row and click the Object Viewer button on the toolbar.
When creating a network object, the Object Viewer provides the following attribute fields:
Step 10 Save the network object by clicking the save button in the Object Viewer.
Step 11 Apply the Transaction by clicking the apply button on the toolbar.
| Attribute | Description | Acceptable Values | Default Value |
|---|---|---|---|
Common Attributes | |||
Name | Network name. This must match the name assigned to the subnetwork by CWM. Note: While CWM does not require network names to be unique, the CWM Equipment Module imposes this restriction. THe CWM network name can be found by examining the $HOME/config.sv file in the CWM account. | Text string (up to 64 characters) |
|
Customer | The Service Customer | Text string (up to 16 characters) |
|
Domain | The VPN domain name. | Text string (up to 16 characters) |
|
Common Parameters | |||
Containing Network | This is the name of the network of which this network object is a subnet (optional). | Text string (up to 32 characters) |
|
Transit Cost | This is the cost of crossing the sub-network. This attribute is used by the Threader to determine the lowest cost path when threading a service (Mandatory). | 0-2147483647 | 50 |
Class | The CPC class name for the network object | CSnt | Csnt* |
Opaque | The threading strategy (opaque or transparent). | True, False | True |
Use Backup EMS | Specify whether or not to use a back EMS. Disabled to use the primary EMS. Enabled to use the backup EMS. | True, False | False |
Pre-provisioned | Not supported in this release. | None, Init, Full | None* |
Network Addressing | |||
Primary Network Addressing | |||
Management Host | The name or IP address of the CWM host. | Text string (up to 32 characters) |
|
UDP Port | The port used by CWM SNMP. This is typically assigned the value 8161 | 0-2147483647 | 8161 |
SNMP Community | The SNMP community configured in CWM SNMP This typically assigned the value private. | Text string (up to 32 characters) | private |
CWM Backup Database Name | The name of the database being used by CWM. This can be found as the value of SVDB_NAME in the $HOME/config/svplus.conf file in the CWM account. This is typically assigned the value stratacom.use.backup EMS: disabled to use the primary EMS, enabled to use the backup EMS. This default is disabled. | Text string (up to 18 characters) | stratacom |
Backup Network Addressing | |||
Management Host | The name or IP address of the backup CWM host. | Text string (up to 32 characters) |
|
UDP Port | The port used by CWM SNMP. This is typically assigned the value 8161. | 0-2147483647 | 8161 |
SNMP Community | The SNMP community configured in CWM SNMP This is typically assigned the value private. | Text string (up to 32 characters) | private |
CWM Backup Database Name | The name of the database being used by CWM. This can be found as the value of SVDB_NAME in the $HOME/config/svplus.conf file in the CWM account. This is typically assigned the value stratacom.use.backup EMS: disabled to use the primary EMS, enabled to use the backup EMS. The default is disabled. | Text string (up to 18 characters) | stratacom |
Specific Information | |||
CWM Major Release | The CWM major release version. | Text string (up to 20 characters) |
|
CWM Full Version | The version of CWM being used. After database migration, this attribute needs to be set. | Text string (up to 20 characters) |
|
Each Object Viewer will contain the following specifications under the tab "Common Attributes":
| Attribute Name | Description | Acceptable Values |
|---|---|---|
Name | Specify the profile name. | text string (up to 24 characters) |
Customer | Specify the customer name. | text string (up to 16 characters) |
Domain | Specify the domain name. | text string (up to 16 characters) |
You must upload the nodes for the network object before uploading the fabric and service elements. Complete the following steps to upload the nodes in the network:
Step 2 Double-click the Cisco WAN Network folder to open it. You can select objects in the Cisco WAN Network list or you can filter your request for specific criteria. Refer to the section "Tree Viewer" in the chapter titled "GUI Navigation", for more information on filtering in the tree viewer.
Step 3 Click the Cisco WAN Network object folder to open it.
Step 4 Select find nodes from the Element menu.
Step 5 When the upload is complete, upload windows will display. If there were errors during the upload they appear in the upload output window.
![]() |
Note BXM T3/E3 ports require CWM version 9.2.07 to be uploaded. IGX FRM cards show up as "FRP" cards in CPC. This has no effect on provisioning logical ports and circuits |
When you first create a network object, you may want to upload just the fabric and service elements for the network object. The fabric elements for a network object are nodes, physical ports and logical ports. The service elements are the objects used to create services (for example, PVCs). Complete the following steps to upload the fabric and service elements:
Step 2 Double-click the Cisco WAN Network folder to open it. You can select objects in the Cisco WAN Network list or you can filter your request for specific criteria. Refer to the section "Tree Viewer" in the chapter titled "GUI Navigation", for more information on filtering in tree viewer.
Step 3 Click the Cisco WAN Network object folder to highlight it.
Step 4 Click the Cisco WAN Network object to highlight it. Enter search criteria in the appropriate filter fields to find the network object you want to upload for and then click the get list button on the toolbar. To list all the network object, double-click the Cisco WAN Switch folder.
Step 5 Click the object from the list to highlight it.
Step 6 Select load both from the Element menu. The upload beings.
Step 7 When the upload is complete, upload windows will display. If there were errors during the upload they appear in the upload output window.
When you first create a network object, you may want to upload just the fabric elements. The fabric elements for a network object are physical ports and logical ports. Complete the following steps to upload the fabric and service elements.
Step 2 Double-click the Cisco WAN Network folder to open it. You can select objects in the Cisco WAN Network list or you can filter your request for specific criteria. Refer to the section "Tree Viewer" in the chapter titled "GUI Navigation", for more information on filtering in tree viewer.
Step 3 Click the Cisco WAN Network object folder to highlight it.
Step 4 Click the Cisco WAN Network object to highlight it. Enter search criteria in the appropriate filter fields to find the network object you want to upload for and then click the get list button on the toolbar. To list all the network objects, double-click the Cisco WAN Switch folder.
Step 5 Click the object from the list to highlight it.
Step 6 Select load both from the Element menu. The upload begins.
Step 7 When the upload is complete, upload request and output windows will display. If there were errors during the upload they appear in the upload output window.
After you upload the fabric elements for a network object, you may want to upload the service elements in the network. Complete the following steps to upload the service elements:
Step 2 Double-click the Cisco WAN Network folder to open it. You can select objects in the Cisco WAN Network list or you can filter your request for specific criteria. Refer to the section "Tree Viewer" in the chapter titled "GUI Navigation", for more information on filtering in the tree viewer.
Step 3 Click the Cisco WAN Network object folder to highlight it.
Step 4 Click the Cisco WAN Network object to highlight it. Enter search criteria in the appropriate filter fields to find the network object you want to upload for and then click the get list button on the toolbar. To list all the network objects, double-click the Cisco WAN Switch folder.
Step 5 Click the object from the list to highlight it.
Step 6 Select load services from the Element menu. The upload begins.
Step 7 When the upload is complete, upload request and output windows will display. If there were errors during the upload they appear in the upload output window.
Complete the following steps to upload the fabric and service elements for a particular node:
Step 2 Double-click the Cisco WAN Network folder to open it. You can select objects in the Cisco WAN Network list or you can filter your request for specific criteria. Refer to the section "Tree Viewer" in the chapter titled "GUI Navigation", for more information on filtering in tree viewer.
Step 3 Double-click a network object folder to open it.
Step 4 Click the Cisco WAN Switch folder to highlight it. Enter search criteria in the appropriate filter fields to find the node you want to upload for and then click the get list button on the toolbar. To list all the nodes, double-click the Cisco WAN Switch folder.
Step 5 Click the node from the list to highlight it.
Step 6 Select load fabric from the Element menu.
Step 7 When the upload is complete, upload request and output windows will display. If there were errors during the upload they appear in the upload output window.
Upload the fabric elements such as logical ports and physical ports for a particular node by completing the following steps:
Step 2 Double-click the Cisco WAN Network folder to open it. You can select objects in the Cisco WAN Network list or you can filter your request for specific criteria. Refer to the section "Tree Viewer" in the chapter titled "GUI Navigation", for more information on filtering in tree viewer.
Step 3 Double-click a network object folder to open it.
Step 4 Click the Cisco WAN Network object to highlight it. Enter search criteria in the appropriate filter fields to find the network object you want to upload for and then click the get list button on the toolbar. To list all the network objects, double-click the Cisco WAN Switch folder.
Step 5 Click the node from the list to highlight it.
Step 6 Select load fabric from the Element menu.
Step 7 When the upload is complete, upload request and output windows will display. If there were errors during the upload they appear in the upload output window.
This upload is used for incremental uploads. It finds all connection objects attached to the node. This procedure is not part of the initial Service element uploading.
Upload the Service elements of a particular node by completing the following steps:
Step 2 Double-click the Cisco WAN Network folder to open it. You can select objects in the Cisco WAN Network list or you can filter your request for specific criteria. Refer to the section "Tree Viewer" in the chapter titled "GUI Navigation", for more information on filtering in tree viewer.
Step 3 Double-click a network object folder to open it.
Step 4 Click the Cisco WAN Network object to highlight it. Enter search criteria in the appropriate filter fields to find the network object you want to upload for and then click the get list button on the toolbar. To list all the network objects, double-click the Cisco WAN Switch folder.
Step 5 Click the node from the list to highlight it.
Step 6 Select load services from the Element menu.
Step 7 When the upload is complete, upload request and output windows will display. If there were errors during the upload they appear in the upload output window.
Step 2 Double-click the specific UploadRequest folder to open it.
Step 3 Double-click the specific upload request folder to open it.
Step 4 Double-click the UploadRequest folder to open it.
Step 5 Click the AuditLog to highlight it and select Log Viewer from the View menu.
The CPC database must be continually updated in order to stay synchronized if changes are being made to nodes in the network. You should re-upload after any of the following:
To re-upload you only need to upload the fabric and Service elements of a particular node. For more information, refer to the sections above titled, "Uploading the Fabric Elements for a Network Object" and "Uploading the Service Elements for a Network Object."
After uploading new fabric elements and Service elements, you may need to add extra topology information which the upload function is unable to determine (perhaps because the information is not known to the node or subnet manager). Topology information or internetwork links are outside the scope of a single node or subnet manager and must be added manually through the CPC GUI or the FTI.
Step 2 Double-click the Cisco WAN Network folder to open it. You can select objects in the Cisco WAN Network list or you can filter your request for specific criteria. Refer to the section "Tree Viewer" in the chapter titled "GUI Navigation", for more information on filtering in tree viewer.
Step 3 Double-click the Cisco WAN Network object folder to open it.
Step 4 Click the Cisco WAN Network object to highlight it. Enter search criteria in the appropriate filter fields to find the network object you want to upload for and then click the get list button on the toolbar. To list all the network objects, double-click the Cisco WAN Switch folder.
Step 5 Double-click the specific node folder to open it.
Step 6 Click a Cisco logical port folder (for example, Cisco ATM Logical Port) to highlight it. Enter search criteria in the appropriate filter fields to find a specific logical port and then click the get list button the toolbar.
Step 7 Double-click the specific logical port folder to open it
Step 8 Click the Link folder to highlight it
Step 9 To select a logical port, click it from the Tree Viewer and select copy from the Edit menu
Step 10 Paste the chosen logical port in the Link subset viewer by selecting paste from the Edit menu. The Link Subset Viewer has a cell for Local Logical Port another for Remote Logical Port, representing the two endpoints of the internetwork link. You must choose a logical port for both endpoints.
Step 11 You can create a locked or unlocked link. If you want to create a link, but disallow any provisioning of services across it, select Locked by clicking the empty cell below either of the Lport Status menus. When the cell is clicked, a pull down menu will appear. If you want CPC to use the link, leave the default value Unlocked.
Step 12 If you are not satisfied with a value, click the appropriate field and modify it.
Step 13 Save the Link by clicking the save button on the toolbar.
Step 14 Repeat the above procedure for the creation of each internetworking link.
For the Cisco Equipment Module, you can pre-configure logical port profiles for ATM, Frame Relay, and Circuit Emulation logical ports.
To create a logical port profile, complete the following steps:
Step 2 Double-click the Equipment Module folder to open it.
Step 3 Double-click the Cisco WAN Equipment Module folder to open it.
Step 4 Click the folder that represents the logical port profile you want to create (for example, Cisco WAN ATM LPort Profile) to highlight it.
Step 5 Click the Subset Viewer button on the toolbar.
Step 6 Enter the appropriate attribute values in the available row of cells.
Step 7 Save the profile by clicking the save button on the toolbar.
Step 8 To specify other attributes, click the row to highlight it and select the Object Viewer button on the toolbar. For more information about the configurable attributes and their values, refer to the logical port profile attribute tables later in this chapter. Make sure to specify a name for the profile.
Step 9 Save the profile by clicking the save button on the toolbar.
Step 10 Apply the Transaction by clicking the apply button on the toolbar.
![]() |
Note Attribute fields in the subset viewer can be added, modified and deleted if required. Refer to the section "Customization" in the chapter titled "GUI Navigation", for more information on customizing the subset viewer. |
To modify a logical port profile, complete the following steps:
Step 2 Double-click the Equipment Module folder to open it.
Step 3 Double-click the Cisco WAN Equipment Module folder to open it.
Step 4 Click the folder that represents the logical port profile you want to modify (for example, Cisco WAN ATM LPort Profile) to highlight it.
Step 5 Click the Subset Viewer button on the toolbar.
Step 6 Click the get list button on the toolbar to get a list of profiles.
Step 7 Click the cell containing the attribute you want to modify and enter a new value.
Step 8 Save the profile by clicking the save button on the toolbar.
Step 9 To modify other attributes, click the row to highlight it and select the Object Viewer button on the toolbar. For more information about the configurable attributes and their values, refer to the logical port profile attribute tables later in this chapter.
Step 10 Save the profile by clicking the save button in the object viewer.
Step 11 Apply the Transaction by clicking the apply button on the toolbar.
To delete a logical port profile, complete the following steps:
Step 2 Double-click the Equipment Module folder to open it.
Step 3 Double-click the Cisco WAN Equipment Module folder to open it.
Step 4 Double-click the folder that represents the type of logical port profile you want to delete (for example, Cisco WAN ATM LPort Profile).
Step 5 Click the specific profile to highlight it.
Step 6 Click the delete button on the toolbar.
Step 7 Apply the Transaction by clicking on the apply button on the toolbar
.
Figure 8-1 shows a Cisco Logical Port Profile Object Viewer.

The Cisco ATM logical port profile provides you with access to the ATM attributes that you can configure for an ATM logical port. The information you provide in the logical port profile is communicated back to CWM through the Equipment Module and helps to define the type of service you are provisioning in the network. If you do not create logical port profiles, the Equipment Module will communicate the values specified in the default logical port profile to CWM.
Table 8-7 below lists the configurable attributes for the logical port profile.
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
Common Attributes | |||
Protocol | Specify the protocol. |
| ATM |
Signalling Role | You use the DCE logical port type to communicate with most ATM CPE. A DCE logical port represents the "network side" equipment. This logical port type supports all types of PVCs. The DTE is almost identical to the DCE logical port type except for with SVC applications, it assumes the role of the "user guide" of the UNI signalling interface. | DCE, DTE | DCE |
NNI Enable | You can enable or disable NNI for the logical port. | Enable, Disable | Disable |
Admin Status | Specify the administrative status for the logical port. | Unlocked, Locked, Shutting Down | Unlocked |
Maximum Connections | Specify the maximum number of connections for the logical port. |
| 0 |
Service Object Id | Specify the Service Object Id. |
|
|
Class | Specify the CPC class for the logical port object. |
| CSal |
Peer Logical Port | Specify the peer logical port (nodename/portname) |
|
|
QOS | Specify the QOS. |
|
|
Group | Specify the group. |
|
|
Priority | Specify the priority. |
| 0 |
Bandwidth | |||
Maximum | Specify the maximum bandwidth (incoming and outgoing). |
|
|
Nominal Threshold | Specify the nominal threshold percentage (incoming and outgoing). |
| 100 |
Committed | Specify the committed bandwidth (incoming and outgoing). |
| 0 |
AUSM/BXM Specific Parameters | |||
SV+ Port Number | Specify the SV+ Port Number |
|
|
Signalling Protocol | Specify the signalling protocol. | None, LMI, ILMI | None |
LMI/ILMI VPI | Specify the VPI. |
| 0 |
LMI/ILMI VCI | Specify the VCI. |
| 16 |
Max VPI bits | Specify the maximum VPI bits. |
| 8 |
Max VCI bits | Specify the maximum VCI bits |
| 16 |
Min SVC VPI 1 |
|
| -1 |
Min SVC VPI |
|
| -1 |
Override CAC 2 | The override CAC toggle. |
| Enable |
LMI Parameters (BXM) | |||
LMI Polling | You can enable or disable LMI polling. | Enable, Disable | Disable |
T393 Link Integrity Timer | Set the link integrity timer. |
| 10 |
T394 Update Status Timer | Set the update status timer. |
| 10 |
T396 Polling Timer | Set the polling timer. |
| 10 |
N394 Status Enquiry Retransmit | Specify the status enquiry retransmit. |
| 5 |
N395 Update Status Retransmit | Specify the update status retransmit. |
| 5 |
ILMI Parameters | |||
ILMI Trap | You can enable or disable ILMI trap. | Enable, Disable | Disable |
Minimum Trap Interval | Specify the minimum trap interval. |
| 1 |
Keep Alive Poll | You can enable or disable keep alive poll. | Enable, Disable | Disable |
N491 Error Threshold | Specify the error threshold. |
| 3 |
N492 Event Threshold | Specify the event threshold. |
| 4 |
T491 Polling Interval | Specify the polling interval. |
| 30 |
T493 Enquiry Interval | Specify the enquiry interval. |
| 10 |
PLCP Configuration3 | |||
Cell Framing |
| ATM, Plcp, Other | ATM |
Cell Scrambling |
| NoScramble, Scramble | Scramble |
PLPP Loopback |
| NoLoopBack, RemoteLoopBack, LocalLoopBack | NoLoopBack |
Single Bit Error Correction |
| Enable, Disable | Disable |
Port Queue Configuration (CBR, VBR, ABR, UBR) 4 | |||
Queue Depth |
|
| 200 (CBR, UBR), 900 (VBR, ABR) |
High CLP Threshold |
|
| 180 (CBR, UBR), 800 (VBR, ABR) |
Low CLP Threshold |
|
| 160 (CBR, UBR), 700 (VBR, ABR) |
EFCI Threshold |
|
| 160 (CBR, UBR), 700 (VBR, ABR) |
ATM Address | |||
ATM Address | Specify the ATM address. |
|
|
ATM Address Type | Specify the ATM address type. | AESA, E.164, Private | Private |
Cisco AUSM IMA Parameters | |||
Maximum Differential Delay | Specify the maximum differential delay. | 1-280 | 1 |
Minimum Receive Links | Specify number of receive links. | 1-8 | 1 |
Minimum Transmit Links | Specify number of transmit links. | 1-8 | 1 |
Number of Redundant Lines | Specify number of redundant lines. | 0-8 | 0 |
Cisco AUSM.BXM Specific Parameters | |||
Port type | Specify the port type | ATM, IMA | ATM |
The Cisco ATM PVC logical port profile provides you with access to the ATM attributes that you can configure for an ATM logical port. The information you provide in the logical port profile is communicated to CWM through the Equipment Module and helps to define the type of service you are provisioning in the network. If you do not create logical port profiles, the Equipment Module will communicate the values specified in the default logical port profile to CWM.
The Cisco Frame Relay logical port profile provides you with access to the Frame Relay attributes that you can configure for a Frame Relay logical port. The information you provide in the logical port profile is communicated to CWM through the Equipment Module and helps to define the type of service you are provisioning in the network. If you do not create logical port profiles, the Equipment Module will communicate the values specified in the default logical port profile to CWM.
Table 8-10 below lists the configurable attributes for the logical port profile.
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
Common Attributes | |||
Protocol | Specify the protocol type. |
| FR |
Signalling Role | You use the DCE logical port type to communicate with most ATM CPE. A DCE logical port represents the "network side" equipment. This logical port type supports all types of PVCs. The DTE is almost identical to the DCE logical port type except for with SVC applications, it assumes the role of the "user guide" of the UNI signalling interface. | DCE, DTE | DCE |
NNI Enable | You can enable or disable NNI for the logical port. | Enable, Disable | Disable |
Admin Status | Specify the administrative status for the logical port. | Unlocked, Locked, Shutting Down | Unlocked |
Maximum Connections | Specify the maximum number of connections for the logical port. |
| 0 |
Service Object Id | Specify the Service Object Id. |
|
|
Class | Specify the CPC class for the logical port object. |
| CSal |
Peer Logical Port | Specify the peer logical port (nodename/portname) |
|
|
QOS | Specify the QOS. |
|
|
Group | Specify the group. |
|
|
Priority | Specify the priority. |
| 0 |
Bandwidth | |||
Maximum | Specify the maximum bandwidth (incoming and outgoing). |
|
|
Nominal Threshold | Specify the nominal threshold percentage (incoming and outgoing). | 0 - 100% | 100 |
Committed | Specify the committed bandwidth (incoming and outgoing). |
| 0 |
Allocated Channels | |||
CWM Admin State | The CWN admin state. | Enable, Disable | Enable |
SV+ Port Number | Specify the SV+Port Number |
|
|
Starting Channel | Specify the starting channel. |
|
|
Channel Speed | Specify the channel speed. | 56 k, 64k | 64k |
Address Length | Specify the address length. | 2Byte10, 3Byte10, 3Byte16, 4Byte17, 4Byte23 | 2Byte10 |
Frame Relay FRSM Specific Parameters | |||
Port Type | Specify the port type. | FR, FR-FUNI, FR-FWD | FR |
Min Flags Between Frames | Specify the minimum flags between frames. |
| 1 |
ECN Queue Threshold | Specify the ECN queue threshold. |
| 65535 |
DE Threshold1 | Specify the DE Threshold. |
| 100 |
| 1This parameter is not delivered to CWM due to CWM issues. |
The Cisco Circuit Emulation logical port profile provides you with access to the CE attributes that you can configure for a CE logical port. The information you provide in the logical port profile is communicated to CWM through the Equipment Module and helps to define the type of service you are provisioning in the network. If you do not create logical port profiles, the Equipment Module will communicate the values specified in the default logical port profile to CWM.
Table 8-9 below lists the configurable attributes for the logical port profile.
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
Common Attributes | |||
Protocol | Specify the protocol type. |
| CBR |
Signalling Role | You use the DCE logical port type to communicate with most ATM CPE. A DCE logical port represents the "network side" equipment. This logical port type supports all types of PVCs. The DTE is almost identical to the DCE logical port type except for with SVC applications, it assumes the role of the "user guide" of the UNI signalling interface. | DCE, DTE | DCE |
Admin Status | Specify the administrative status for the logical port. | Unlocked, Locked, Shutting Down | Unlocked |
Protocol Management/Sigalling | |||
LMI Operation Mode | Specify the LMI operation mode. | None, noasync-LMI, uni-AnnexA, uni-AnnexD, nni-AnnexA, nni-AnnexD | None |
N391 Full State Polling Counter | Set the full state polling counter. |
| 6 |
N392 Error Threshold | Specify the error threshold. |
| 3 |
N393 Monitored Event Count | Specify the monitored event count. |
| 4 |
Asynchronous Updates | Specify asynchronous updates. | yes, no | no |
T391 Link Integrity Timer | Set the link integrity timer. |
| 10 |
T392 Polling Verification Timer | Set the polling verification timer. |
| 15 |
Enhanced LMI | You can enable or disable the enhanced LMI., | Enable, Disable |
|
CLLM Parameters | |||
CLLM | You can enable or disable the CLLM admin state. | Enable, Disable | Disable |
Xmt Status | Set the Xmt status timer. |
| 40 |
Frame Relay IGX Specific Parameters | |||
Port Queue Depth | Specify the port queue depth. |
| 65535 |
Maximum Connections | Specify the maximum number of connections. |
| 0 |
Service Object Id | Specify the Service Object Id. |
|
|
Class | Specify the Activator class for the logical port object. |
| CScl |
Peer Logical Port | Specify the peer logical port. |
|
|
QOS | Specify the QOS. |
|
|
Group | Specify the group. |
|
|
Priority | Specify the priority. |
| 0 |
Bandwidth | |||
Maximum Bandwidth Available | Specify the maximum bandwidth available (AZ connection and ZA connection). |
|
|
Committed Bandwidth Nominal Threshold | Specify the committed bandwidth nominal threshold percentage (AZ connection and ZA connection). | 0 -100% | 100 |
Committed Bandwidth | Specify the committed bandwidth (AZ connection and ZA connection). |
| 0 |
Allocated Channels | |||
Service Port Type | Specify the service port type. | Structured, Unstructured, Framing | Structured |
Circuit Interface Type | Specify the circuit interface type. | unknown, DS1, E1, notused, subrate, OC3, broadband, E3, T3 | DS1 |
Starting Channel | Specify the starting channel. |
| 0 |
You can create, modify, delete, and re-name Frame Relay, Circuit Emulation, and ATM logical ports.
Table 8-10 below lists the logical ports that are supported for each card type.
| Card Type | Create | Modify | Delete |
|---|---|---|---|
ASI (T3/E3/OC3) | Yes | Yes | Yes |
BXM (all) | Yes | Yes | Yes |
FRSM (all) | Yes | Yes | Yes |
AUSM-4 | No | Yes | No |
AUSM-8 | No | Yes | Yes |
CESM - 4T1 | No | Yes | No |
CESM - 8T1/E1 | Yes | Yes | Yes |
UXM (V.35,8T1) | Yes | Yes | Yes |
UFM-U (V.35) | Yes | Yes | Yes |
UFM-C (8T1) | Yes | Yes | Yes |
FRM-U (V.35) | Yes | Yes | Yes |
FRM-C (T1) | Yes | Yes | Yes |
To create logical ports, complete the following procedure. When creating CBR or Frame Relay logical ports, select the appropriate physical port to allow for proper channel verification when the port is being saved.
Step 2 Double-click the Cisco WAN Network folder to open it. You can select objects in the Cisco WAN Network list or you can filter your request for specific criteria. Refer to the section "Tree Viewer" in the chapter titled "GUI Navigation" for more information on filtering in the tree viewer.
Step 3 Double-click a Cisco WAN Network object folder to open it.
Step 4 Click the Cisco WAN Switch folder to highlight it. Enter search criteria in the appropriate filter fields to find the node that contains the logical port you want to create and then click the get list button on the toolbar. To list all of the nodes, double-click the Cisco WAN Switch folder.
Step 5 Double-click the specific node to open it.
Step 6 Click the type of logical port that you are creating from the list (for example, Cisco WAN FR Logical Port).
Step 7 Click the Subset Viewer button on the toolbar.
Step 8 Fill in the attribute fields with the required values.
Step 9 Save the profile by clicking the save button on the toolbar.
Step 10 To specify other attributes, click the row to highlight it and click the Object Viewer button on the toolbar. You must select a physical port to which the logical port belongs.
Step 11 Save the logical port by clicking the save button on the toolbar.
Step 12 Apply the transaction by clicking the apply button on the toolbar.
![]() |
Note You must use the copy and paste mechanism when entering a value for the physical port that will contain the logical port. Manually entered physical port values are not supported. |
You can modify Frame Relay and ATM logical ports.
Step 2 Double-click the Cisco WAN Network folder to open it. You can select objects in the Cisco WAN Network list or you can filter your request for specific criteria. Refer to the section "Tree Viewer" in the chapter titled "GUI Navigation" for more information on filtering in the tree viewer.
Step 3 Double-click a Cisco WAN Network object folder to open it.
Step 4 Click the Cisco WAN Switch folder to highlight it. Enter search criteria in the appropriate filter fields to find the node that contains the logical port you want to create and then click the get list button on the toolbar. To list all of the nodes, double-click the Cisco WAN Switch folder.
Step 5 Double-click a node folder to open it.
Step 6 Click the type of logical port that you want to modify from the list (for example, Cisco WAN FR Logical Port).
Step 7 Click the Subset Viewer button on the toolbar.
Step 8 Enter search criteria in the appropriate filter fields to find the logical port you want to modify and click the get list button on the toolbar. To list all of the logical ports, double-click the folder containing the type of logical port (for example, Cisco WAN FR Logical Port).
Step 9 Click the cell containing the attribute you want to modify and enter a new value.
Step 10 Save the modifications by clicking the save button on the toolbar
Step 11 To specify other attributes, click the row to highlight it and click the Object Viewer button on the toolbar.
Step 12 Save the modifications by clicking the save button on the toolbar.
Step 13 Apply the Transaction by clicking the apply button on the toolbar.
You can delete Frame Relay and ATM logical ports. To delete a logical port, complete the following steps:
Step 2 Double-click the Cisco WAN Network folder to open it. You can select objects in the Cisco WAN Network list or you can filter your request for specific criteria. Refer to the section "Tree Viewer" in the chapter titled "GUI Navigation", for more information on filtering in the tree viewer.
Step 3 Double-click a Cisco WAN Network object folder to open it.
Step 4 Click the Cisco WAN Switch folder to highlight it. Enter search criteria in the appropriate filter fields to find the node that contains the logical port you want to create and then click the get list button on the toolbar. To list all of the nodes, double-click the Cisco WAN Switch folder.
Step 5 Click the type of logical port that you want to delete from the list (for example, Cisco WAN FR Logical Port) to highlight it.
Step 6 Enter search criteria in the appropriate filter fields to find the logical port you want to delete and click the get list button on the toolbar.
Step 7 Click the specific logical port you want to delete to highlight it.
Step 8 Click the delete button on the toolbar.
Step 9 Apply the Transaction by clicking the apply button on the toolbar.
![]() |
Note The error "First digit:no such variable" may appear in a site log while trying to delete a logical port. This indicates that the firmware for one of the switches has not uploaded correctly from CWM. Re-install the firmware on the switch in question and re-upload nodes such that the attribute "Firmware Release Revision" in the Node object viewer contains a valid value. |
The Cisco WAN Equipment Module allows the Equipment Module name and the EMS name of a logical port to be changed from the default names assigned during the initial upload. The default names are in the form <slot>.<port> for ATM logical ports and in the form <slot>.<line>.<port> for Frame Relay and Circuit Emulation logical ports.
After initial upload, an CPC client can modify Equipment Module names and EMS names through the FTI or the GUI. The names can be changed to any combination of characters, except <number>.<number>[.<number>]. When either of these name attributes is modified, the Equipment Module verifies that the new name is unique within the containing node.
A name attribute reset to its default value when the user sets the name attribute to an empty string. The Equipment Module logical port name is stored in the CPC database as srname. The EMS logical port name is stored in the CPC database as sremsname.
A Transaction must be opened to change a name attribute.
CPC names Frame Relay, ATM, and CBR logical ports in the same manner as the CWM Connection Manager. Table 8-11 shows the mapping of logical port naming from CWM to CPC:
| Circuit type Card | CWM Attributes Used for Name | CPC Attributes Used for Name |
|---|---|---|
Frame Relay (FRSM) | Slot_number.physical_port_number (i.e. 8.8.1) | Slot_Number.PortNumber.start_channel |
Frame Relay (FRP/ UFM) | Slot_number.logical_port_number (i.e. 3.19) | Slot_Number.CWM Port Number |
ATM (ALL) | Slot_number.logical_port_number (i.e.5.1) | Slot_Number.CWM Port Number |
CBR (ALL) | Slot_number.physical_port_number (i.e. 10.3.24) | Slot_Number.PortNumber.starting_channel |
Service element profiles provide you with access to the Cisco-specific attributes for a particular service. There is a corresponding Service element profile for each service type that the Equipment Module supports. Default profiles provide the initial (default) attribute values for the corresponding object class whenever such a new object is created.
For a given Service element, more than one profile may be defined. For example, there may be a Frame Relay PVC Profile for each class of service (CoS), "Gold," "Silver," and "Bronze." For a given object, only one profile may be associated at any one time.
Since profiles themselves are objects which you can create and modify, they provide a means to store and name commonly used sets of attributes and provide a reliable shorthand method of configuring any number of new objects. A profile has most of the same attributes as the corresponding object class. Some attributes of the object class are not included in the profile because they are expected to be unique for each object. For example, the DLCI on a Frame Relay PVC would not be a profile attribute. Similarly, an object's name is not a profile attribute.
The attributes of a profile are referred to as initial value attributes because they are used to assign the initial values to the corresponding object. Once a new object has been created based on a profile, changes to profile attribute values do not cause any changes to the corresponding object. The only time the profile attributes affect the object is when you create a new object or when you reassign an existing object to the same or different profile.
For the CWM Equipment Module, you can create Service element profiles for the following supported services:
This section details the procedures for creating, modifying, and deleting Service element profiles, and then provides the specific configurable attributes for each Service element profile for this Equipment Module.
If you provide values for these attributes and also provides values in other places when you are creating a service (either during service creation or in a Service object profile) the threader will override the values based on the following scale of priorities:
1. Object Subset Viewer--All information provided in Service object subset viewer n is used by CPC.
2. Object Profile--The CPC will only use the information provided in the Service object profile for values that are either not available or not specified in the service object subset viewer.
3. Element Profile--The CPC uses values from the Service element profile for all attributes that are not present or not specified in the Service object profile or on service object subset viewer.
Step 2 Double-click the Equipment Module folder to open it.
Step 3 Double-click the Cisco WAN Equipment Module folder to open it.
Step 4 Click the folder that represents the service element profile you want to create (for example, Cisco FR-FR Profile) to highlight it.
Step 5 Click the Subset Viewer button on the toolbar.
Step 6 Enter a Name for the profile and enter the appropriate attribute values inthe available row of cells
Step 7 Save the profile by clicking the save button on the toolbar.
Step 8 To specify other attributes, click the row to highlight it and click the Obect Viewer button on the toolbar. For more information about the configurable attributes and their values, refer to the attribute tables in this section.
Step 9 Save the profile by clicking the save button on the toolbar.
Step 10 Apply the Transaction by clicking the apply button on the toolbar.
![]() |
Note Attribute fields in the subset viewer can be added, modified and deleted if required. Refer to the section "Customization" in the chapter titled "GUI Navigation", for more information on customizing the subset viewer. |
To modify a Service element profile, complete the following steps:
Step 2 Double-click the Equipment Module folder to open it.
Step 3 Double-click the Cisco WAN Equipment Module folder to open it.
Step 4 Click the folder that represents service element profile you want to modify (for example, Cisco FR-FR PVC Profile) to highlight it.
Step 5 Click the Subset Viewer button on the toolbar.
Step 6 Click the get list button on the toolbar to get a list of service element profiles.
Step 7 Click a profile and modify the values in the available row of cells.
Step 8 Save the profile by clicking the save button on the toolbar.
Step 9 To specify other attributes, highlight the row and click the Object Viewer button on the toolbar. For more information about the configurable attributes and their values, refer to the attribute tables in this section.
Step 10 Save the profile by clicking the save button on the toolbar.
Step 11 Apply the Transaction by clicking the apply button on the toolbar.
To delete a Service element profile, complete the following steps:
Step 2 Double-click the Equipment Module folder to open it.
Step 3 Double-click the Cisco WAN Equipment Module folder to open it.
Step 4 Double-click the type of profile that you want to delete (for example, Cisco FR-FR PVC Profile)
Step 5 Click the specific profile to highlight it.
Step 6 Click the delete button on the toolbar.
Step 7 Apply the Transaction by clicking the apply button on the toolbar.
Figure 8-2 shows a Cisco Service Element Profile Object Viewer.

The Cisco CE Service element profile provides you with access to the additional CE attributes that you can configure for a CE service through CWM. The information you provide in the Service element profile is communicated to CWM through the Equipment Module and helps to define the type of service you are provisioning in the network. If you do not create Service element profiles, the Equipment Module will communicate the values specified in the default Service element profile to the CWM.
Table 8-12 below lists the configurable attributes for the CE-PE PVC profile. Descriptions are not provided for the attributes located in the Common or Lport Associations sections on the screen. For more information about the attributes listed in these areas, refer to the chapter titled "Provisioning Private Line Services"
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
Circuit Emulation Parameters | |||
Max Size of Reassembly Buffer | Specify the maximum size of the reassembly buffer. | 0-65535 | 6000 |
Max Cell Arrival Jitter | Specify the size of the cell arrival jitter that the reassembly process can handle. | 1000-65535 | 10000 |
Cell Loss Integration Period | Specify the cell loss integration period (in ms). |
| 2500 |
Onhook Code | Specify the onhook code. | 0-15 |
|
Idle Detection | Specify idle detection. | disable, enableOnhook | disable |
Idle Suppression | Specify idle suppression. | disable, enable | disable |
Utilization | Specify the percentage of channel bandwidth utilization. | 0-100% | 100 |
Circuit Emulation Common Parameters | |||
CBR Clock Mode | Specify the CBR clock mode. | Sync, Srts, Adaptive | Sync |
Number of User Octets per Cell1 | Specify the number of user octets per cell. | 0-47 | 47 |
Direction of Flow | Specify the direction of flow. | Duplex, SimplexA2Z, SimplexZ2A, P2multiA2Z, P2multiZ2A | Duplex |
CAS Bits Carried by Service | Specify channel associated signaling. | Basic, E1, DS1SF, DS1ESF, J2 | Basic |
Reroute Priority | Specify the reroute priority. | 0-15 (the lower the value, the higher the | 0 |
Trunk to avoid2 | This parameter allows you to select whether or not to avoid satellite links and terrestrial links. The default is NONE which indicates not to avoid these trunks. | NONE, | NONE |
Avoid ZCS Trunks3 | This parameter specifies whether or not to avoid trunks with Zero Code Suppression (ZCS). DISABLED indicates that ZCS trunks are available for use. | enabled or | disabled |
Attributes | |||
sra primtp | The original A logical port that is being back up by UNI resiliency (nodename/portname). |
|
|
srunipriority | The UNI recovery priority. |
| 0 |
srz primtp | The original Z logical port that is being backed up by UNI resiliency (nodename/portname). |
|
|
The Cisco CE-ATM Service element profile provides you with access to the additional CE and ATM attributes that you can configure for a CE-ATM service through CWM. The information you provide in the Service element profile is communicated to CWM through the Equipment Module and helps to define the type of service you are provisioning in the network. If you do not create Service element profiles, the Equipment Module will communicate the values specified in the default Service element profile to the CWM.
Table 8-13 below lists the configurable attributes for the CE-ATM PVC profile. Descriptions are not provided for the attributes located in the first Common Attributes section and Lport Associates section, or ATM Parameters sections in the object viewer. For more information about the attributes listed in these areas, refer the to chapters titled "Provisioning ATM Services" and "Provisioning Private Line Services. "
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
Common Attributes | |||
Override CAC1 | The override CAC toggle. |
| Enable |
Preferred Route | Specify the preferred route. |
|
|
Enable Cell Routing | You can enable or disable cell routing. |
| Disable |
CE Attributes | |||
Re-assembly Size2 | Specify the maximum re-assembly size. | 0-65535 | 6000 |
Max CDV Jitter | Specify the size of the cell arrival jitter that the re-assembly process can handle. | 1000-65535 | 10000 |
Cell Loss Integration Period | Specify the cell loss integration period (in ms). | 1000-65535 | 2500 |
Unused User Octets/Cell3 | Specify the number of unused user octets per cell. | 0-47 | 47 |
Onhook Code | Specify the onhook code. | 0-15 |
|
Idle Detection | Specify the idle detection. | disable, enableOnhook | disable |
CBR Clock Mode4 | Specify the direction of flow. | Duplex, SimplexA2Z, SimplexZ2A, P2multiA2Z, P2multiZ2A | Duplex |
CAS bits Carried by Service5 | Specify channel associated signaling. | Basic, E1, DS1SF, DS1ESF, J2 | Basic |
Avoid ZCS trunks6 | This parameter specifies whether or not to avoid trunks with Zero Code Suppression (ZCS). DISABLED indicates that ZCS trunks are available for use. | enabled or disabled | disabled |
Trunk to Avoid7 | This parameter allows you to select whether or not to avoid satellite links and terrestrial links. The default is NONE which indicates not to avoid these trunks. | NONE, SATELLITE, or TERRESTRIAL | NONE |
Originating-- Terminating Utilization | Specify the originating-terminating percentage of channel bandwidth utilization. | 0-100% | 100 |
Terminating-- Originating Utilization | Specify the terminating-originating percentage of channel bandwidth utilization. | 0-100% | 100 |
Reroute Priority | Specify the reroute priority. | 0-15 (the lower the value, the higher the | 0 |
The Cisco ATM Service element profile provides you with access to the additional ATM attributes that you can configure for an ATM service through CWM. The information you provide in the Service element profile is communicated to CWM through the Equipment Module and helps to define the type of service you are provisioning in the network. If you do not create Service element profiles, the Equipment Module will communicate the values specified in the default Service element profile to the CWM.
Table 8-14 below lists the configurable attributes for the ATM-ATM PVC profile. Descriptions are not provided for the attributes located in the Common section and limited descriptions are provided for the ATM Attributes and BPX/AXIS Attributes sections in the object viewer. For more information about the ATM attributes listed in the profile, refer to the chapter titled "Provisioning ATM Services"
| Attribute Name | Description | Acceptable values | Default value |
|---|---|---|---|
ATM LPort Associations | |||
VCI | This is the VCI. If you want to let CPC auto-select the VPI, enter 0. | 0-65535 | 0 |
VPI | This is the VPI. If you want to let CPC auto-select the VPI, enter -1. | -1-4095 | -1 |
ATM Attributes | |||
Circuit Type | This is the circuit type. | VC, VP | VC |
Class of Service | You can specify the class of service for traffic. The class of service determines which traffic descriptor you can select | ABR, CBR, UBR, nrt-VBR, rt_VBR | ABR |
Fixed Round Trip Time | This attribute specifies the round-trip time in milli-seconds. | 0-16700000 | 0 |
Bandwidth (Kb/s) | This is the bandwidth. | 0-2147483647 | 0 |
Primary Logical Port | The original logical port that is being backed up by UNI resiliency (nodename/portname). | text string (up to 44 characters) | 0 |
Sustainable Cell Rate (cells/s) | SCR is the maximum average cell transmission rate that is allowed over a given period of time on a given circuit. It allows the network to allocate sufficient resources for guaranteeing the network performance objectives are met. | 0-2147483647 | 0 |
Peak Cell Rate (cells/s)1 | PCR is the maximum allowed cell transmission rate. It defines the shortest time period between cells and provides the highest guarantee that network performance objectives (based on cell loss ratio) will be met. | 0-2147483647 | 0 |
Minimum Cell Rate (cells/s)2 | MCR is the minimum cell rate, which is the minimum allocated bandwidth for a connection. | 0-2147483647 | 0 |
Maximum Burst Size (cells) | MBS is the maximum number of cells that can be received at the PCR. This allows a burst of cells to arrive at a rate higher than the SCR. If the burst is larger than anticipated, the additional cells are either tagged or dropped. This parameter applies only to VBR traffic. | 10-5000000 | 1000 |
CDVT (microseconds) | Cell Delay Variation Tolerance establishes the time scale over which the PCR is policed. This is set to allow for jitter (CDV). | 0-250000 | 0 |
Traffic Desc | This is the traffic descriptor type which describes the specified traffic parameters for the service (for more information see the chapter titled "Provisioning ATM Services" | depending on the QoS, one of Other, ABR_FC, ABR_NFC3, CBR.1, UBR.1, UBR.2, VBR.1, VBR.2, VBR.3 | ABR_NFC |
Initial Cell Rate (cells/sec) | Specify the initial cell rate in cells/sec. | 0-2147483647 | 0 |
Rate Increase Factor | This parameters specifies the rate increase factor as a fraction. | 1/32768, 1/16374, 1/8192, 1/4096, 1/2048, 1/1024, 1/512, 1/256, 1/128, 1/64, 1/32, 1/16, 1/8, 1/2, 1 |
|
NRM (cells)4 | This parameter specifies the NRM in cells. | 2-256 | 32 |
Rate Decrease Factor | This parameters specifies the rate increase factor as a fraction. | 1/32768, 1/16374, 1/8192, 1/4096, 1/2048, 1/1024, 1/512, 1/256, 1/128, 1/64, 1/32, 1/16, 1/8, 1/2, 1 |
|
ACR Decrease Time Factor | Specify the ACR decrease time factor. | 62-255000 | 1000 |
BPX/MGX Attributes | |||
Override CAC5 | The override CAC toggle. |
| Disabled |
Preferred Route | Specify the preferred route. |
|
|
Enable Cell Routing | You can enable or disable cell routing. |
| Enabled |
Trunk to avoid6 | This parameter allows you to select whether or not to avoid satellite links and terrestrial links. The default is NONE which indicates not to avoid these trunks. | NONE, | NONE |
Avoid ZCS trunks7 | This parameter specifies whether or not to avoid trunks with Zero Code Suppression (ZCS). DISABLED indicates that ZCS trunks are available for use. | enabled or | disabled |
Reroute | This specifies the reroute priority. | 0-15 (the lower the value, the higher the | 0 |
BPX/AXIS AZ/ZA Connection | |||
Frame Discard | You can ENABLE or DISABLE frame discard. | ENABLE or | ENABLE |
Utilization (%) | This parameter specifies the percentage of channel bandwidth utilization. If CAC (cell admission control) is disabled on the node, then this should be set to 0. | 0-100% | 100 |
TRM (milliseconds) | This parameter specifies the TRM in milliseconds. | 0-100% | 100 |
Ext Segment Flow Ctrl/BCM | This parameter allows you to enable or disable the generation of BCM cells when congestion is detected in the connection. | enabled or disabled | disabled |
ABR Policing8 | This parameter specifies the value of ABR policing. | NONE, VBR.1, VBR.2, VBR.3, CBR.1 | None |
UPC Enable | Enable the UPC. |
|
|
Low Cell Loss Priority | This parameter specifies the low cell loss priority as a percentage. | 1-100 | 35 |
Hi Cell Loss Priority | This parameter specifies the hi cell loss priority as a percentage. | 1-100 | 80 |
VC Queue Depth | This parameter specified the VC queue depth in cells/s. | 1-64000 | 1366 |
EFCI Queue Size | This parameter specifies the EFCI queue size as a percentage. | 1-100 | 100 |
Initial Burst Size | This parameter specifies the initial burst size as a percentage. | 0-24000 | 1 |
Foresight PCR | This parameter specifies the foresight peak cell rate. | 0-2147483647 | 50 |
SCR Policing | This parameter specifies the value of SCR policing. | Clp0, Clp0and1, Off |
|
CLP Tagging | You can enable or disable CLP tagging. | Enable, Disable |
|
Foresight Attributes (AZ/ZA Connection) | |||
Rate Increase Factor9 | This parameter specifies the rate increase factor in cells/s. | 0-1412832 | 10 |
Rate Decrease Factor | This parameter specifies the rate decrease factor as a percentage. | 0-100 | 87 |
The Cisco Frame Relay Service element profile provides you with access to the additional Frame Relay attributes that you can configure for an Frame Relay service through CWM. The information you provide in the Service element profile is communicated back to CWM through the Equipment Module and helps to define the type of service you are provisioning in the network. If you do not create Service element profiles, the Equipment Module will communicate the values specified in the default Service element profile to the CWM.
Table 8-15 below lists the configurable attributes for the FR-FR PVC profile. Descriptions are not provided for the attributes located in the Common Attributes section in the object viewer. For more information about the Frame Relay attributes listed in the profile, refer to the chapter titled "Provisioning Frame Relay Services"
| Attribute Name | Description | Acceptable values | Default value |
|---|---|---|---|
Frame Relay Parameters | |||
DLCI | The Data Link Channel Identifier. | 0-2147483647 | 0 |
CIR | The rate at which the network commits to transfer information under normal conditions. The rate is averaged over a minimum time interval (Tc). | 0-5200 | 20 |
FR Attributes | |||
Frame Relay Priority | This is the Frame Relay priority. | HIGH, MEDIUM, LOW | HIGH |
FR Attributes Transmission Direction | |||
CIR (Kb/s) | The rate at which the network commits to transfer information under normal conditions. The rate is averaged over a minimum time interval (Tc). | 0-5200 | 20 |
Be (Kb) | Excess burst is the maximum number of bits in excess of the committed burst (Bc) that the network will attempt to transfer over the Tc under normal conditions. | 0-524 | 41 |
Bc (Kb) | Committed burst is the maximum number of bits of user data that the network commits to transfer during the Tc at the CIR under normal conditions. | 0-524 | 41 |
Primary Logical Port | The original logical port that is being backed up by UNI resiliency. |
|
|
Bandwidth (Kb/s) | This is the bandwidth. | 0-2147483647 | 0 |
Max Frame Size (bytes) | This is the maximum frame size. | 0-2147483647 | 0 |
BPX Parameters | |||
Trunk to avoid1 | This parameter allows you to select whether or not to avoid satellite links and terrestrial links. The default is NONE which indicates not to avoid these trunks. | NONE, | NONE |
Avoid ZCS trunks2 | This parameter specifies whether or not to avoid trunks with Zero Code Suppression (ZCS). DISABLED indicates that ZCS trunks are available for use. | enabled or | disabled |
Reroute | This is the reroute priority. | 0-15 | 0 |
Foresight | This parameter specifies whether or not to use Foresight, which is a Flow Control Mechanism by which the data flow is controlled depending on the network load. | enabled or | disabled |
Interworking | |||
Interworking Type | Network interworking (N_IW) transports Frame Relay packets across an intermediate ATM network to another Frame Relay network. The frames are encapsulated into ATM cells. Service interworking (S-IW) adapts Frame relay packets into ATM cells for transmission onto an ATM network. After the ATM cells enter the network, the network can send them to ATM-attached devices or Frame Relay devices. | N_IW, S_IW | N_IW |
Service IW Mode | For translated protocol mapping, the system determines the protocol type and remaps the Frame Relay protocol to the ATM protocol, and vice versa. For transparent protocol mapping, the system does not determine the protocol type, it only removes the Frame Relay header and transfers the payload transparently between the Frame Relay and ATM networks. | TRANSLATED, TRANSPARENT | TRANSLATED |
EFCI Determination | This parameter allows you to set mapping from Frame Relay FECN (Forward Explicit Congestional Notification) bits to the ATM EFCI (Explicit Forward Congestion Indication) bit to 9. | 0, FECN | 0 |
CLP | This parameter allows you to set mapping from the Frame Relay DE bit to the ATM CLP bit of 0 or 1. | DE, 0, 1 | DE |
ATM DE | This parameter allows you to set mapping from the ATM CLP bit of 0 or 1 to the Frame Relay DE bit. | CLP, FR, 0, 1 | CLP |
Utilization (%) | This parameter specifies the percentage of channel bandwidth utilization. | 0-100% | 100 |
MIR | Specify the MIR. | 0-153600 | 20 |
QIR | Specify the QIR. | 0-153600 | 20 |
PIR | Specify the PIR. | 0-153600 | 20 |
CMAX (packets) | Specify the CMAX. | 0-255 | 10 |
Initial Burst Size/IBS (bytes) | This parameter specifies the initial burst size. | 0-65535 | 100 |
DeTagging | You can enable or disable DeTagging for the ingress direction. | DISABLE, ENABLE | DISABLE |
EcnQSize (bytes) | The threshold setting used by the explicit congestion notification feature for this endpoint's transmit queue. The value is specified in bytes. | 0-65535 | 65535 |
VcQSize (bytes) | This attribute specifies the maximum queue depth (in bytes) for this endpoint. | 1-65535 | 65535 |
IngressDeThreshold (bytes) | This specifies the maximum queue depth, before the cells become discard eligible (in the ingress direction). | 0-65535 | 32768 |
EgressQ | This specifies the maximum queue depth before dropping the cells (in the egress direction). | 0-65535 | 65535 |
EgressDeThreshold (bytes) | This specifies the maximum queue depth, before the cells become discard eligible (in the egress direction). | 0-65535 | 32768 |
EgressEcn | This specifies the threshold setting used by the explicit congestion notification feature (in the egress direction). | 0-65535 | 65535 |
EgressQ | This specifies one of the two possible port queues. | HIGH | HIGH |
| 1This parameter is not delivered to CWM due to CWM issues. 2Refer to footnote 1. |
The Cisco Frame Relay-ATM Interworking Service element profile provides you with access to the additional Frame Relay and ATM attributes that you can configure for a Frame Relay-ATM service through CWM. The information you provide in the Service element profile is communicated to CWM through the Equipment Module and helps to define the type of service you are provisioning in the network. If you do not create Service element profiles, the Equipment Module will communicate the values specified in the default Service element profile to the CWM.
Table 8-16 below lists the configurable attributes for the Service FR-ATM Interworking PVC profile. Descriptions are not provided for the attributes located in the Common Attributes and LPort Associations sections on the screen. For more information about the Frame Relay-ATM interworking attributes listed in the profile, refer to the chapter titled "Provisioning Frame Relay-ATM Interworking Services."
| Attribute Name | Description | Acceptable Values | Default Value |
|---|---|---|---|
Frame Relay Attributes | |||
Frame Relay Priority | This is the Frame Relay priority. | HIGH, MEDIUM, LOW | HIGH |
Interworking Type | Network interworking (N_IW) transports Frame Relay packets across an intermediate ATM network to another Frame Relay network. The frames are encapsulated into ATM cells. Service interworking (S_IW) adapts Frame relay packets into ATM cells for transmission onto an ATM network. After the ATM cells enter the network, the network can send them to ATM-attached devices or Frame Relay devices. | N_IW, S_IW | N_IW |
CLP Determination | This parameter allows you to set mapping from the Frame Relay DE (Discard Eligible) bit to the ATM CLP (Cell loss priority) bit of 0 or 1. | DE, 0, 1 | DE |
Service IW Mode | For translated protocol mapping, the system determines the protocol type and remaps the Frame Relay protocol to the ATM protocol, and vice versa. For transparent protocol mapping, the system does not determine the protocol type, it only removes the Frame Relay header and transfers the payload transparently between the Frame Relay and ATM networks. | TRANSLATED, TRANSPARENT | TRANSLATED |
FR Attributes Transmission Direction | |||
CIR | The rate at which the network commits to transfer information under normal conditions. The rate is averaged over a minimum time interval (Tc). | 0-5200 | 20 |
Be (Kb) | Excess burst is the maximum number of bits in excess of the committed burst (Bc) that the network will attempt to transfer over the Tc under normal conditions. | 0-524 | 41 |
Bc (Kb) | Committed burst is the maximum number of bits of user data that the network commits to transfer during the Tc at the CIR under normal conditions. | 0-524 | 41 |
Bandwidth (Kb/s) | This is the bandwidth. | 0-2147483647 | 0 |
Primary Logical Port | The original logical port that is being backed up by UNI resiliency. |
|
|
Max Frame Size (bytes) | This is the maximum frame size. | 0-2147483647 | 0 |
ATM Attributes | |||
Class of Service | This is the ATM class of service. | CBR, nrt_VBR, rt_VBR, ABR and UBR | nrt_VBR |
DE Determination | This parameter allows you to set the mapping from the ATM bit of 0 or 1 to the Frame Relay DE bit. | CLP, FR, ", 1 | CLP |
EFCI Determination | This parameter allows you to set mapping from Frame Relay FECN (Forward Explicit Congestional Notification) bits to the ATM EFCI (Explicit Forward Congestion Indication) bit to 9. | 0, FECN | 0 |
Bandwidth (Kb/s) | This is the bandwidth. | 0-2147483647 | 0 |
Sustainable Cell Rate (cells/) | SCR is the maximum average cell transmission rate that is allowed over a given period of time on a given circuit. It allows the network to allocate sufficient resources for guaranteeing the network performance objectives are met. | 0-2147483647 | 0 |
Peak Cell Rate (cell/s) | PCR is the maximum allowed cell transmission rate. It defines the shortest time period between cells and provides the highest guarantee that network performance objectives (based on cell loss ratio) will be met. | 0-2147483647 | 1000 |
Maximum Burst Size (cells) | MBS is the maximum number of cells that can be received at the PCR. This allows a burst of cells to arrive at a rate higher than the SCR. If the burst is larger than anticipated, the additional cells are either tagged or dropped. This parameter applies only to VBR traffic. | 10-5000000 | 0 |
CDVT (microseconds) | Cell Delay Variation Tolerance establishes the time scale over which the PCR is policed. This is set to allow for jitter (CDV). | 0-250000 | 0
|
Minimum Cell Rate (cells/s) | MCR is the minimum cell rate, which is the minimum allocated bandwidth for a connection. | 0-2147483647 | 0 |
Traffic Desc | This is the traffic descriptor type which describes the specified traffic parameters for the service (for more information see the chapter titled "Provisioning ATM Services" | CBR.1, VBR.2, VCBR.3, ABR.FS, UBR.1, UBR.2 | VBR.3 |
ATM Attributes ATM to FR Direction |
|
|
|
Initial Cell Rate1 | Specify the initial cell rate in cells/s | 0-2147483647 | 50 |
ACR Decrease Time Factor | Specify the ACR decrease time factor. | 62-255000 | 1000 |
CWM Attributes | |||
Override CAC2 | The override CAC toggle. |
| Disabled |
Preferred Route | Specify the preferred route. | text string (up to 22 characters) |
|
Enable Cell Routing | You can enable or disable cell routing. |
| Disabled |
Trunk to Avoid | This parameter allows you to select whether or not to avoid satellite links and terrestrial links. The default is NONE which indicates not to avoid these trunks. | enabled or disabled | disabled |
Reroute Priority | This s is the reroute priority. | 0-15 (the lower the value, the higher the priority) | 0 |
CWM ATM Parameters | |||
ZA Utilization (%) | This parameter specifies the percentage of channel bandwidth utilization. | 0-100% | 100 |
Frame Discard | You can enable or disable frame discard. | DISABLE, ENABLE | DISABLE |
Rate Increase Factor | Specify the rate increase factor. | 0-1412832 | 10 |
Rate Decrease Factor | Specify the rate decrease factor. | 0-100% | 87 |
TRM | Specify the TRM (in milliseconds) | 1-100 | 100 |
Ext. Segment Flow Ctrl/BCM |
|
| Disabled |
Low Cell Loss Priority | This parameter specifies the low cell loss priority as a percentage. | 1-100 | 35 |
Hi Cell Loss Priority | This parameter specifies the hi cell loss priority as a percentage. | 1-100 | 80 |
VC Queue Depth | This parameter specifies the VC queue depth in cells/s. | 1-64000 | 1366 |
EFCI |
|
|
|
MIR | Specify the MIR. | 0-153600 | 20 |
QIR | Specify the QIR. | 0-153600 | 20 |
PIR | Specify the PIR. | 0-153600 | 20 |
CMAX (packets) | Specify the CMAX. | 0-255 | 10 |
Initial Burst Size/IBS (bytes) | This parameter specifies the initial burst size. | 0-65535 | 100 |
DeTagging | You can enable or disable DeTagging for the ingress direction. | DISABLE, ENABLE | DISABLE |
EcnQSize (bytes) | The threshold setting used by the explicit congestion notification feature for this endpoint's transmit queue. The value is specified in bytes. | 0-65535 | 65535 |
VcQSize (bytes) | This attribute specifies the maximum queue depth (in bytes) for this endpoint. | 1-65535 | 65535 |
IngressDeThreshold (bytes) | This specifies the maximum queue depth, before the cells become discard eligible (in the ingress direction). | 0-65535 | 32768 |
EgressQ | This specifies the maximum queue depth before dropping the cells (in the egress direction). | 0-65535 | 65535 |
EgressDeThreshold (bytes) | This specifies the maximum queue depth, before the cells become discard eligible (in the egress direction). | 0-65535 | 32768 |
EgressEcn | This specifies the threshold setting used by the explicit congestion notification feature (in the egress direction). | 0-65535 | 65535 |
EgressQ | This specifies one of the two possible port queues. | HIGH | HIGH |
Initial Burst Size (bytes) | The initial burst size. | 0-65535 | 100 |
DeTagging | You can enable or disable DeTagging for the ingress direction. | DISABLE, ENABLE | DISABLE |
Ingress EcnQSize (bytes) | The threshold setting used by the explicit congestion notification feature for this endpoint's transmit queue. This value is specified in bytes. | 0-65535 | 65535 |
Ingress VcQSize (bytes) | This attribute specifies the maximum queue depth (in bytes) for this endpoint. | 1-65535 | 65535 |
Ingress DeThreshold (bytes) | This specifies the maximum queue depth, before the cells become discard eligible (in the ingress direction). | 0-65535 | 32768 |
EgressQ | This specifies the maximum queue depth before dropping the cells (in the egress direction). | 0-65535 | 65535 |
EgressDeThreshold (bytes) | This specifies the maximum queue depth, before the cells become discard eligible (in the egress direction). | 0-65535 | 32768 |
EgressEcn | This specifies the threshold setting used by the explicit congestion notification feature (in the egress direction). | 0-65535 | 65535 |
EgressQ | This specifies the priority of the queue in the egress direction. | HIGH | HIGH |
| 1These attributes are only applicable to ABR with FS feature IW PVC. 2This parameter not delivered to CWM due to CWM issues. |
The Cisco Equipment Module supports manual EMS changeover. Changeover switches the upload and provisioning to a backup CWM. The Equipment Module stores two sets of EMS information in the Network object, one set for the primary EMS and one set for the backup EMS.
Changeover to the backup EMS and change back to the primary EMS can be performed manually by the Operator by running a script. A sample script titled "csEMSChangeover" is located in $CCP_REL/mng/utility.
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Thu Aug 3 16:39:12 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.