Table Of Contents
DPNSS Feature Transparency
Feature Overview
Restrictions
Related Features and Technologies
Changes to Cisco MGC Software Architecture
Related Documentation
Supported Standards, MIBs, and RFCs
Prerequisites
Configuration Tasks
Troubleshooting Tips
Provisioning Tasks
Planning for Provisioning
Provisioning Procedures
Troubleshooting Tips
Alarm Troubleshooting Procedures
Signaling Channel Troubleshooting Procedures
Monitoring and Maintaining
Regular Operations
Configuration Example
Provisioning Example
Command Reference
New MML Commands
Modified MML Commands
Reference Information
XECfgParm.dat Parameters
Alarms
Measurements
Components
External Node Types
Provisioning Worksheets
Obtaining Technical Assistance
Cisco.com
Technical Assistance Center
Glossary
DPNSS Feature Transparency
Document Release History
Publication Date
|
Comments
|
May 15, 2003
|
Initial version of the document.
|
Feature History
Release
|
Modification
|
9.4(1)
|
This feature was introduced on the Cisco MGC software.
|
This document describes the (DPNSS) Feature Transparency Feature. This feature is described in the following sections:
•
Feature Overview
• Supported Standards, MIBs, and RFCs
• Prerequisites
• Configuration Tasks
• Provisioning Tasks
• Monitoring and Maintaining
• Configuration Example
• Provisioning Example
• Command Reference
• Reference Information
• Obtaining Technical Assistance
• Glossary
Feature Overview
This feature enables support on the Cisco PGW 2200 of feature transparancy for DPNSS.
This feature provides the following:
•IUA interface can be used with Cisco access servers that support DPNSS signaling
Restrictions
The types of Cisco access servers supported by this feature is limited. The Cisco access servers that can be used for this feature are listed below.
•Cisco 2600
•Cisco AS 3600
•Cisco AS 3660
Related Features and Technologies
The following features and technologies are related to this feature:
•Support for DPNSS Feature (for the Cisco access servers)
•Support for the IUA with SCTP Feature (for the Cisco PGW 2200 and Cisco access servers)
Changes to Cisco MGC Software Architecture
This section describes the changes to Cisco MGC software architecture to support this feature.
Input/Output Subsystem
The Input/Output (I/O) subsystem consists of the I/O channel controllers (IOCC) and the I/O channel manager (IOCM), which manages them.
•The IOCM manages all IOCCs and keeps the hardware resource states of the hardware controlled by the IOCCs.
•The IOCCs provide
–A protocol-specific, message-based interface that allows nodes and platforms external to the Cisco MGC to communicate with the Cisco MGC.
–An interface that allows buffering of messages to the call engine's event dispatcher queue.
•The Cisco MGC I/O subsystem includes the following IOCCs:
–Signaling System 7 (SS7)—Contains MTP3 used for backhauling SS7 signaling to the
Cisco MGC from a Cisco SLT.
–ISDN Level 3—Provides backhauling of ISDN (standard variants) to the Cisco MGC from a media gateway.
–Q.931+—A stateless IOCC, for a Cisco-proprietary protocol (RLM), which is a special version of ISDN that enables forwardhauling of Q931+ signaling to a media gateway used with a Cisco PGW 2200 configured for signaling environments.
–Media Gateway Control Protocol (MGCP)—Enables communication to media gateways and trunking gateways for setting up bearer channel connections used in Cisco PGW 2200 configured for call control environments.
–Extended ISDN User Part (E-ISUP)—Cisco-proprietary internal interface that enables the transport of endpoint and media gateway specific information between two (or more) Cisco MGCs. This protocol uses an enhanced ISUP base to support all ANSI and ITU ISUP messaging and elements, as well as additional fields to support transport of service information (such as local number portability (LNP), 800 numbers, and so on).
–Session Initiation Protocol (SIP)—Enables the Cisco MGC to receive and send SIP messages using the User Datagram Protocol (UDP).
–Transport Adapter Layer Interface (TALI)—Enables communication between the Cisco MGC and the Tekelec IP7 Secure Gateway signaling gateway. One TALI IOCC can communicate with up to two Tekelec IP7 Secure Gateways.
–IUA—Added in Release 9.4, this IOCC enables backhauling of ISDN Q.921 User messages over IP using SCTP. This IOCC is used between a Cisco PGW 2200 and media gateways.
–Message Transfer Part Level 3 (MTP3) User Adaptation (M3UA)—Added in Release 9.4, this IOCC enables the transport of any SS7 MTP Level 3 User signaling (for example, ISUP and TUP messages) over IP using SCTP. This IOCC is used between a Cisco PGW 2200 and Cisco ITP.
–Signaling Control Connection Part (SCCP) User Adaptation (SUA)—Added in Release 9.4, this IOCC enables the transport of any SCCP user signaling (for example, TCAP messages) over IP using SCTP. This IOCC is used between a Cisco PGW 2200 and Cisco ITP.
–(DPNSS)—Added in Release 9.4, this IOCC enables the tranparent transport of DPNSS data over IP. This IOCC is used between media gateways that support DPNSS.
Related Documentation
This document contains information that is related strictly to this feature. The documents that contain additional information related to the Cisco Media Gateway Controller (MGC) are listed below:
•Cisco MGC Hardware Installation Guide
•Regulatory Compliance and Safety Information for the Cisco Media Gateway Controller
•Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide
•Release Notes for Cisco Media Gateway Controller Software Release 9.4(1)
•Cisco Media Gateway Controller Software Release 9 Provisioning Guide
•Cisco Media Gateway Controller Software Release 9 Dial Plan Guide
•Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide
•Cisco Media Gateway Controller Software Release 9 MML Command Reference Guide
•Cisco Media Gateway Controller Software Release 9 Messages Reference Guide
•Cisco Media Gateway Controller Software Release 9 Billing Interface Guide
•Cisco Media Gateway Controller Software Release 9 Management Information Base Guide
Supported Standards, MIBs, and RFCs
This section identifies the new or modified standards, MIBs, or RFCs that are supported by this feature.
Standards
•DPNSS
•IUA
•SCTP
MIBs
New MIBs are available for this feature. There is a new MIB for each new measurement. You can find a list of the new measurements in the
"Measurements" section. For more information on the MIBs used in the Cisco MGC software, refer to the
Cisco Media Gateway Controller Release 9 Management Information Base Guide.
RFCs
•SCTP - RFC-2960
•IUA - RFC-3057
Prerequisites
You must have Cisco Media Gateway Controller (MGC) software Release 9.4(1). Prerequisites for this release can be found in the Release Notes for the Cisco Media Gateway Controller Software Release 9.4(1).
Configuration Tasks
This sections contains the steps necessary for configuration of the Cisco MGC software to support this feature. For information on installing and configuring the Cisco MGC software on your system, refer to the Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide, coming back to this section once you encounter the *.IP_NextHop1 parameter in the XECfgParm.dat file.
Note You only need to configure the *.IP_NextHop parameters when the Cisc o MGC hosts are on different subnets. If your hosts are on the same subnet, do not perform the procedure below.
Caution Configuration of the Cisco MGC software requires that the system software be shut down. In a simplex system, calls cannot be processed during system shut down. In a continuous service system, your system loses the ability to maintain calls during a critical event while the system software on one of the PGW hosts is shut down.
Caution The other XECfgParm.dat parameters associated with this feature should not be modified.
To configure the next hop IP addresses, perform the following steps:
Step 1 If you have not already done so, open the /opt/CiscoMGC/etc/XECfgParm.dat file on the active and standby Cisco PGW hosts using a text editor, such as vi.
Step 2 If you have not already done so, ensure that the pom.dataSync parameter is set to false on the active and standby Cisco PGW hosts.
Step 3 Search for the *.IP_NextHop1 parameter and enter the IP address of your first next hop destination on the active and standby Cisco PGW hosts.
Note The IP address should be expressed in decimal dot notation (for example, 10.25.81.5).
Step 4 Repeat Step 3 for every next hop destination (*.IP_NextHop2, *.IP_NextHop3, etc.) you want to identify on the active and standby Cisco PGW hosts. Up to eight next hop IP addresses can be specified.
Step 5 Return to the Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide and continue from where you left off. You will need to go to the "Adding DPNSS Connections" section in this document later if you intend to use an IUA interface for data backhaul between your Cisco PGW 2200 and your associated Cisco access server(s).
Troubleshooting Tips
If the next hop IP addresses you have entered are incorrect, perform the following steps. For more information on troubleshooting the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide.
To ensure proper functioning of this feature, you must enter next hop IP addresses in the XECfgParm.dat file. These IP addresses are used when the next hop router IP addresses on the Cisco PGW hosts do not match. To enter next hop IP addresses, perform the following steps:
Caution The other XECfgParm.dat parameters associated with this feature should not be modified.
Step 1 Log in to the standby Cisco MGC as root and change directories to the etc subdirectory by entering the following UNIX command:
cd /opt/CiscoMGC/etc
Step 2 Open the XECfgParm.dat using a text editor, such as vi.
Step 3 Search for the *.IP_NextHop1 parameter and enter the IP address of your first next hop destination.
Note The IP address should be expressed in decimal dot notation (for example, 10.25.81.5).
Step 4 Repeat Step 3 for every next hop destination (*.IP_NextHop2, *.IP_NextHop3, etc.) you want to identify. Up to eight next hop IP addresses can be specified.
Step 5 Save your changes and close the text editor.
Step 6 Manually stop the Cisco MGC software on the standby Cisco MGC by entering the following UNIX command:
/etc/init.d/CiscoMGC stop
Step 7 Once the software shutdown is complete, manually start the Cisco MGC software on the standby Cisco MGC by entering the following command:
/etc/init.d/CiscoMGC start
Step 8 Log in to the active Cisco MGC, start an MML session, and enter the following command:
sw-over::confirm
Site alarms are automatically set until the OOS Cisco PGW host is returned to an IS state.
Step 9 Repeat steps 2 through 8 for the newly standby Cisco PGW host.
Provisioning Tasks
The following sections describe the provisioning tasks related to this feature:
• Planning for Provisioning
• Provisioning Procedures
• Troubleshooting Tips
Planning for Provisioning
This section lists the data that you must gather to successfully provision this feature. For more information on planning the provisioning for the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Collecting External Node Data
The external node component type represents another node with which the MGC communicates. You must be ready to enter the following data:
•MML name
•Component description
•The type of the external node
•ISDN Signaling Type
The parameters for EXTNODE are defined in Table 11.
Collecting DPNSS Path Data
This component represents an DPNSS signaling service to a particular Cisco access server. Refer to the "Restrictions" section for more information on the Cisco access servers that require the use of a DPNSS signaling service. You must be ready to enter the following data:
•Unique ID of this component and component name used in MML commands
•Component description
•MML name of the associated external node
•Customer group ID
•Identify this path as either A side, B side, or neither
•Signaling Port Number (physical port on the Cisco access server)
•Signaling Port Slot (physical slot on the Cisco access server)
The DPNSS signaling service component structure is shown in Table 12.
Collecting IP Route Data (optional)
The IP route represents a static IP route. IP routes are only required for this feature when the Cisco PGW hosts are not on the same subnet as the Cisco access servers. If your system requires IP routes, you must be ready to enter the following data:
•IP route name
•Component description
•Destination hostname or IP address
•Subnet mask of Destination (optional)
•Next hop router IP address
•Local IP address
•Priority
The IP route component information can be listed in Table 13.
Collecting SCTP Association Data
The SCTP association represents the connection between the Cisco MGC and a Cisco access server. You must be ready to enter the following data:
•MML Name of the SCTP association
•Description of this component
•Signaling Type
•MML Name of the SGP
•First local address
•Second local address (optional)
•Local SCTP port number (optional)
•The highest priority destination address
•The lowest priority destination address (optional)
•Destination SCTP port number. (optional)
•External Node's MML name
•MML Name of first IPROUTE (optional)
•MML Name of second IPROUTE (optional)
•Number of bytes to advertise for the local receive window. (optional)
•Maximum number of times to retransmit SCTP INIT message (optional)
•Maximum initial timer retransmission value (optional)
•Maximum number of retransmissions over all destination address before the association is declared failed (optional)
•Maximum time after a datagram is received before a SCPT SACK is sent (optional)
•Maximum time SCTP waits for other outgoing datagrams for bundling (optional)
•Minimum value allowed for the retransmission timer (optional)
•Maximum value allowed for the retransmission timer (optional)
•Time between heartbeats. The heartbeat is this value plus the current retransmission timeout value (optional).
•Internet Protocol Precedence. This value is placed in the IP PRECEDENCE portion of the Type Of Service field for outgoing SCTP datagrams (optional)
•Differential Service Code Point. This value is placed in the DSCP portion of the Type Of Service field for outgoing SCTP datagrams (optional)
•Maximum number of retransmissions to either PEERADDR1 or PEERADDR2 before it is declared failed (optional)
The SCTP association component structure is shown in Table 14.
Provisioning Procedures
Provision the transport path for DPNSS data between the Cisco PGW 2200 and the external Cisco access server nodes. Communication between the Cisco PGW 2200 and the Cisco access servers is provisioned to provide a reliable communication path between the two platforms.
This provisioning is performed when an external node is modified to use an SCTP-based protocol or when a new external node is added to the Cisco PGW 2200. This section covers the following provisioning topics:
• Provisioning Basics
• Adding DPNSS Connections
• Modifying DPNSS Components
• Deleting DPNSS Components
Provisioning Basics
The procedures in this section describe how to start a provisioning session and how to save and activate the changes you have made.
• Starting a Provisioning Session
• Saving and Activating your Provisioning Changes
• Ending a Provisioning Session Without Activating your Changes
• Retrieving Provisioning Data
For more detailed information about provisioning your Cisco PGW 2200, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Starting a Provisioning Session
You may need to start a provisioning session as part of your system operations. To do this, log into the active Cisco MGC, start an MML session, and enter the following command:
prov-sta::srcver="curr_ver",dstver="mod_ver"
Where:
•curr_ver—The name of the current configuration version. In place of the name of the current configuration version, you can also enter:
–new—A new default session configuration; no existing source configuration is available.
–active—Selects the active configuration as the source for configuration changes.
Note If you do not know the name of your current configuration session, you can use the procedure in the "Retrieving Data on the Current Provisioning Session" section.
•mod_ver—A new configuration version name that contains your provisioning changes.
For example, to use a configuration version called ver1 as the basis for a version to be called ver2, you would enter the following command:
prov-sta::srcver="ver1",dstver="ver2"
Once a provisioning session is underway, you may use the prov-add, prov-ed, or prov-dlt MML commands to add, modify, and delete components on your system. This document describes how to add, modify, and delete M3UA and SUA components. For more information on provisioning other components on your Cisco PGW 2200, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
There are two ways to close your provisioning session: saving and activating your provisioning changes, as described in the "Saving and Activating your Provisioning Changes" section or ending your provisioning session without saving and activating your changes, as described in the "Ending a Provisioning Session Without Activating your Changes" section.
Saving and Activating your Provisioning Changes
When you have completed making provisioning changes in your session, you must enter a command to save and activate your changes. There are two different provisioning MML commands that do this: prov-cpy and prov-dply.
Caution Using the
prov-cpy and
prov-dply MML commands can severely impact your system's call processing performance, depending on the extent of your provisioning changes. We recommend that these commands be issued during a maintenance window when traffic is minimal.
The prov-cpy MML command is used to save and activate your changes on the active Cisco MGC. This command is typically used to save and activate changes on a Cisco MGC in a simplex configuration. However, you can use the prov-cpy MML command on Cisco MGCs in high-availability or continuous-service configurations, to save and activate your changes on the active Cisco MGC. If you choose to do this, you should enter the prov-sync MML command immediately afterwards, to have your changes saved and activated on the standby Cisco MGC.
Note When you enter the prov-cpy command, your provisioning session is also automatically ended. If you want to make additional provisioning changes, you must start a new provisioning session as described in the "Starting a Provisioning Session" section.
Caution Using the
prov-sync MML command can severely impact your system's call processing performance. We recommend that this command be issued during a maintenance window when traffic is minimal.
Note When the prov-sync MML command is used to synchronize the provisioning settings on the standby MGC host with current settings on the active MGC host, the system does not indicate when the synchronization process has failed.
The prov-dply MML command is used to save and activate your changes on the active and standby
Cisco MGCs. This command is typically used to save and activate changes on Cisco MGCs in high-availability or continuous-service configurations. This command should not be used on a Cisco MGC in a simplex configuration.
Note When you enter the prov-dply command, your provisioning session is also automatically ended, unless an error occurs during execution. If you want to make additional provisioning changes, you must start a new provisioning session as described in the "Starting a Provisioning Session" section.
Ending a Provisioning Session Without Activating your Changes
You may find that you want to end a provisioning session without saving and activating the changes you have entered during your session. If this is the case, you can enter the prov-stp MML command. This command ends your current provisioning session and your changes are not entered.
Retrieving Provisioning Data
You can use the prov-rtrv MML command to retrieve information about your current provisioning settings. The ways in which you can use this command to retrieve provisioning data are described in the following sections:
• Retrieving Data for an Individual Component
• Retrieving Data for Select Components
• Retrieving Data for All Components of a Particular Type
• Retrieving Data on the Current Provisioning Session
• Retrieving Data on Supported Signaling Protocols
Retrieving Data for an Individual Component
You can retrieve provisioning data on any individual component on your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
prov-rtrv:component:name=MML_name
Where:
•component—The MML component type associated with the desired component. You can find a complete list of MML component types in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
•MML_name—The MML name for the desired component. You can determine the MML names for the various components using the prov-rtrv:all MML command.
For example, to view the provisioning data for an IUA signaling service called iua1, you would enter the following command:
prov-rtrv:sigsvcprop:name="iua1"
The system returns a response similar to the following:
<<get system response>>
Retrieving Data for Select Components
You can retrieve data on select the components provisioned on your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
prov-rtrv:all
Note This command returns data on all signaling components, except for signaling service and linkset properties.
The system returns a response similar to the following:
<< get system response >>
Retrieving Data for All Components of a Particular Type
You can retrieve provisioning data on all components of a particular type on your system. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
prov-rtrv:component:"all"
Where: component is the MML component type associated with the desired component group. You can find a complete list of MML component types in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Note Components that are used to retrieve signaling or routing properties (that is sigsvcprop, lnksetprop, and trnkgrpprop) cannot use this command. The properties for only one signaling or routing component can be listed per command instance. Please use the following format:
prov-rtrv:propComp:name="compName" | name="ss7famName"
Where:
propComp—MML component name appropriate to the property type you want to retrieve, as listed below:
sigsvcprop—Provides maintenance access to the properties of signaling services.
trnkgrpprop—Provides maintenance access to the properties of trunk groups
lnksetprop—Provides maintenance access to the properties of linksets.
compName - MML name of a previously provisioned signaling service or trunk group.
ss7famName - MML name of the SS7 family associated with the desired linkset.
For example, to view the provisioning data for all signaling services, you would enter the following command:
prov-rtrv:naspath:"all"
The system returns a response similar to the following:
<< get system response >>
Retrieving Data on the Current Provisioning Session
You can retrieve provisioning data on the current provisioning session. To do this, log in to the active Cisco MGC, start an MML session, and enter the following command:
prov-rtrv:session
The system returns a response similar to the following:
MGC-02 - Media Gateway Controller 2003-01-13 13:39:19
M RTRV
"session=jtest:session"
/*
Session ID = mml1
SRCVER = active
DSTVER = jtest
*/
Retrieving Data on Supported Signaling Protocols
You can retrieve protocol data for the current provisioning session. To do this, log in to the active
Cisco MGC, start an MML session, and enter the following command:
prov-rtrv:variants
The system returns a response similar to the following:
<< get system response >>
Adding DPNSS Connections
This section contains the procedures that you must perform to add DPNSS connections to your Cisco PGW 2200 provisioning data. When provisioning the components that enable the Cisco PGW 2200 to support DPNSS, perform the procedures in the following order.
• Adding Cisco Access Server External Nodes
• Adding IP Routes (optional)
• Adding SCTP Associations
• Adding DPNSS Signaling Services
Adding Cisco Access Server External Nodes
To add Cisco access server external nodes, perform the following steps:
Step 1 Start a provisioning session as described in the "Starting a Provisioning Session" section.
Step 2 Enter the following command to add a Cisco access server external node:
prov-add:extnode:name="name", desc="description", type="as", isdnsigtype="iua"
Where:
•name—The name you want to give to the component. The name can be as many as 20 characters long and can contain numbers, letters, and the dash (-) symbol. The name should begin with a letter.
•description—The long name assigned that can be as many as 128 alphanumeric characters in length.
•as—The MML name for the type of Cisco access server. Valid values can be found in the "External Node Types" section.
For example, to add a Cisco access server external node named va-3600-36, you would enter the following command:
prov-add:extnode:name="va-3600-36", desc="3600", type="AS3600", isdnsigtype="iua"
Step 3 Repeat Step 2 for each Cisco access server external node you want to add to your provisioning data.
Step 4 If there are no other components that you need to provision, end your provisioning session as described in the "Saving and Activating your Provisioning Changes" section.
Otherwise, proceed to the "Adding IP Routes (optional)" section if your Cisco PGW 2200 is on a different subnet from the associated access server, or proceed to the "Adding SCTP Associations" section if they are on the same subnet.
Adding IP Routes (optional)
IP routes are required for your provisioning data if your Cisco PGW hosts are not on the same subnet as the Cisco access servers. To add IP routes, perform the following steps:
Step 1 If you do not already have an active provisioning session, start one as described in the "Starting a Provisioning Session" section.
Step 2 Enter the following command to add an IP route:
prov-add:iproute:name="name", desc="description", netmask="mask", nexthop="nhop",
ipaddr="addr", dest="destination"
Where:
•name—The name you want to give to the component. The name can be as many as 20 characters long and can contain numbers, letters, and the dash (-) symbol. The name should begin with a letter.
•description—The long name assigned that can be as many as 128 alphanumeric characters in length.
•mask—Subnet mask of the destination (optional). The value should be expressed as an IP Address in decimal dot notation (default is 255.255.255.255).
•nhop—Next hop router hostname, IP address, or one of the following property names defined in the XECfgParm.dat file:
–IP_NextHop
–IP_NextHop2
–IP_NextHop3
–IP_NextHop4
–IP_NextHop5
–IP_NextHop6
–IP_NextHop7
–IP_NextHop8
–IP_Addr1
–IP_Addr2
–IP_Addr3
–IP_Addr4
IP Address should be in decimal dot notation and the hostname must be less than or equal to 32 characters.
•addr—Local IP address. IP Address should be one of the following property names defined in the XECfgParm.dat file:
–IP_Addr1
–IP_Addr2
–IP_Addr3
–IP_Addr4
•destination—Destination hostname or IP address. IP Address should be in decimal dot notation and the hostname must be less than or equal to 32 characters.
For example, to add an IP route named iprte1, you would enter the following command:
prov-add:IPROUTE:NAME="iprte1", DESC="IP Route 1", dest="10.82.80.0", ipaddr="IP_Addr1",
netmask="255.255.255.0", nexthop="10.82.82.1"
Step 3 Repeat Step 2 for each IP route you want to add to your provisioning data.
Step 4 If there are no other components that you need to provision, end your provisioning session as described in the "Saving and Activating your Provisioning Changes" section.
Otherwise, proceed to the "Adding SCTP Associations" section.
Adding SCTP Associations
To add SCTP associations, perform the following steps:
Step 1 If you do not already have an active provisioning session, start one as described in the "Starting a Provisioning Session" section.
Step 2 Enter the following command to add an SCTP association:
prov-add:association:name="name", desc="description", type="IUA", ipaddr1="addr1",
ipaddr2="addr2", peeraddr1="paddr1", peeraddr2="paddr2", extnode="gway",
iproute1="iprte1", iproute2="iprte2"
Where:
•name—The name you want to give to the component. The name can be as many as 20 characters long and can contain numbers, letters, and the dash (-) symbol. The name should begin with a letter.
•description—The long name assigned that can be as many as 128 alphanumeric characters in length.
•addr1—First local IP address, as defined by the following XECfgParm.dat parameters:
–IP_Addr1
–IP_Addr2
–IP_Addr3
–IP_Addr4
•addr2—Second local IP address, as defined by the following XECfgParm.dat parameters:
–IP_Addr1
–IP_Addr2
–IP_Addr3
–IP_Addr4
–N/A (default value)
•paddr1—Highest priority destination address, expressed in dot notation.
•paddr2—Lowest priority destination address, expressed in dot notation. This parameter is optional. The default value for this parameter is 0.0.0.0.
•gway—MML name of a previously entered Cisco access server external node.
•iprte1—MML name of a previously entered IP route (optional).
•iprte2—MML name of a previously entered IP route (optional).
For example, to add an SCTP association named nasassoc1, you would enter the following command:
prov-add:ASSOCIATION:NAME="dpnssassoc1",DESC="DPNSS Association 1", TYPE="IUA",
IPADDR1="IP_Addr1", IPADDR2="IP_Addr2", PEERADDR1="10.82.80.187",
PEERADDR2="10.82.81.164", extnode="va-3600-37, IPROUTE1="iprte1", IPROUTE2="iprte2"
Note The parameters listed above are those required to create an SCTP association for an IUA interface. For a complete list of parameters for this component, refer to the "SCTP Association" section.
Step 3 Repeat Step 2 for each SCTP association you want to add to your provisioning data.
Step 4 If there are no other components that you need to provision, end your provisioning session as described in the "Saving and Activating your Provisioning Changes" section.
Otherwise, proceed to the "Adding DPNSS Signaling Services" section.
Adding DPNSS Signaling Services
To add DPNSS signaling services, perform the following steps:
Step 1 If you do not already have an active provisioning session, start one as described in the "Starting a Provisioning Session" section.
Step 2 Enter the following command to add a DPNSS signaling service:
prov-add:dpnsspath:name="name", desc="description", extnode="mgw", abflag="side",
sigport=portnum, sigslot=slotnum
Where:
•name—The name you want to give to the component. The name can be as many as 20 characters long and can contain numbers, letters, and the dash (-) symbol. The name should begin with a letter.
•description—The long name assigned that can be as many as 128 alphanumeric characters in length.
•mgw—MML name of a previously defined external node. Valid types are:
–C2600
–AS3600
–AS3660
•side—DPNSS side for this signaling service (optional). Value values are A (for A side), B (for B side), and N (for not applicable) (N)
•portnum—Number for physical port on the access server (optional). Valid values: 0-167 (0).
•slotnum—Number for physical slot on the access server (optional). Valid values: 0-63 (0).
For example, to add a DPNSS signaling service named dpnsvc1, you would enter the following command:
prov-add:naspath:NAME="dpnsvc1",DESC="IUA DPNSS path", extnode="va-3660-20", abflag="a",
sigport=45, sigslot=10
Step 3 Repeat Step 2 for each DPNSS signaling service you want to add to your provisioning data.
Step 4 If there are no other components that you need to provision, end your provisioning session as described in the "Saving and Activating your Provisioning Changes" section.
Modifying DPNSS Components
The following sections contain the procedures for modifying the various IUA connections in your Cisco PGW 2200 provisioning data:
• Modifying Cisco Access Server External Nodes
• Modifying IP Routes
• Modifying DPNSS Signaling Services
• Modifying SCTP Associations
Modifying Cisco Access Server External Nodes
Desc is the only parameter that can be modified for an existing Cisco access server external node. To edit the description of a Cisco access server external node, perform the following steps:
Step 1 Start a provisioning session as described in the "Starting a Provisioning Session" section.
Step 2 Enter the following command to edit a Cisco access server external node:
prov-ed:extnode:name="name", desc="description"
Where:
•name—MML name of the Cisco access server external node to be modified.
•description—The long name assigned that can be as many as 128 alphanumeric characters in length.
For example, to modify an Cisco access server external node named va-3600-37, you would enter the following command:
prov-ed:extnode:name="va-3600-37", desc="3600 supporting DPNSS"
Step 3 Repeat the above steps for each Cisco access server external node you want to modify in your provisioning data.
Step 4 If there are no other components that you need to provision, end your provisioning session as described in the "Saving and Activating your Provisioning Changes" section.
Modifying DPNSS Signaling Services
You can modify the description, DPNSS side identification, signaling port number, and signaling slot number in a DPNSS signaling service. To modify DPNSS signaling services, perform the following steps:
Step 1 Shut down the D-channel(s) on the associated access server(s). Refer to the documentation for the access server for more information on shutting down D-channels.
Step 2 Set the DPNSS signaling services to be modified to the Out-of-Service (OOS) state by entering the following MML command:
set-dest:sig_srv:OOS
Where sig_srv is the MML name of the DPNSS signaling services to be modified.
Step 3 Repeat Step 2 for each of the DPNSS signaling services to be modified.
Step 4 Start a provisioning session as described in the "Starting a Provisioning Session" section.
Step 5 Enter the following command to modify an DPNSS signaling service:
prov-ed:dpnsspath:name="name", desc="description", abflag="side", sigport=portnum,
sigslot=slotnum
Where:
•name—MML name of the component to be modified.
•description—The long name assigned that can be as many as 128 alphanumeric characters in length.
•mgw—MML name of a previously defined external node. Valid types are:
–C2600
–AS3600
–AS3660
•side—DPNSS side for this signaling service (optional). Value values are A (for A side), B (for B side), and N (for not applicable) (N)
•portnum—Number for physical port on the access server (optional). Valid values: 0-167 (0).
•slotnum—Number for physical slot on the access server (optional). Valid values: 0-63 (0).
For example, to modify the DPNSS side identification on a DPNSS signaling service named dpnsvc1, you would enter the following command:
prov-ed:dpnsspath:NAME="dpnsvc1", abflag="n"
Step 6 Repeat Step 5 for each DPNSS signaling service you want to modify in your provisioning data.
Step 7 If there are no other components that you need to provision, end your provisioning session as described in the "Saving and Activating your Provisioning Changes" section.
Step 8 Set the modified DPNSS signaling services to the In-Service (IS) state by entering the following MML command for each signaling service:
set-dest:sig_srv:IS
Where sig_srv is the MML name of the modified DPNSS signaling service.
Step 9 Restore the D-channel(s) on the associated access server(s). Refer to the documentation for the media gateway for more information on shutting down D-channels.
Modifying IP Routes
The only IP route parameter that cannot be modified is the name. To modify IP routes, perform the following steps:
Step 1 Set the IP route to be modified to the OOS state as described in the "Setting the Service State of an IP Route" section.
Step 2 Repeat Step 1 for each IP route to be modified.
Step 3 Start a provisioning session as described in the "Starting a Provisioning Session" section.
Step 4 Enter the following command to modify an IP route:
prov-ed:iproute:name="name", desc="description", netmask="mask", nexthop="nhop",
ipaddr="addr", dest="destination"
Where:
•name—MML name of the IP route to be modified.
•description—The long name assigned that can be as many as 128 alphanumeric characters in length.
•mask—Subnet mask of the destination (optional). The value should be expressed as an IP Address in decimal dot notation (default is 255.255.255.255).
•nhop—Next hop router hostname, IP address, or one of the following property names defined in the XECfgParm.dat file:
–IP_NextHop
–IP_NextHop2
–IP_NextHop3
–IP_NextHop4
–IP_NextHop5
–IP_NextHop6
–IP_NextHop7
–IP_NextHop8
–IP_Addr1
–IP_Addr2
–IP_Addr3
–IP_Addr4
IP Address should be in decimal dot notation and the hostname must be less than or equal to 32 characters.
•addr—Local IP address. IP Address should be one of the following property names defined in the XECfgParm.dat file:
–IP_Addr1
–IP_Addr2
–IP_Addr3
–IP_Addr4
•destination—Destination hostname or IP address. IP Address should be in decimal dot notation and the hostname must be less than or equal to 32 characters.
For example, to modify the destination and local IP address in an IP route named iparte1, you would enter the following command:
prov-ed:IPROUTE:NAME="iprte1", dest="10.82.80.1", ipaddr="IP_Addr2"
Step 5 Repeat the Step 4 for each IP route you want to modify in your provisioning data.
Step 6 If there are no other components that you need to provision, end your provisioning session as described in the "Saving and Activating your Provisioning Changes" section.
Step 7 Set the IP route to be modified to the IS state as described in the "Setting the Service State of an IP Route" section.
Modifying SCTP Associations
Only the name, type, and extnode parameters cannot be modified for an SCTP association. To modify SCTP associations, perform the following steps:
Step 1 Set the SCTP association to be modified to the OOS state as described in the "Setting the Service State of an Association" section.
Step 2 Repeat Step 1 for each SCTP association to be modified.
Step 3 Start a provisioning session as described in the "Starting a Provisioning Session" section.
Step 4 Enter the following command to modify an SCTP association:
prov-ed:association:name="name", desc="description", ipaddr1="addr1", ipaddr2="addr2",
peeraddr1="paddr1", peeraddr2="paddr2", iproute1="iprte1", iproute2="iprte2"
Where:
•name—MML name of the SCTP association to be modified.
•description—The long name assigned that can be as many as 128 alphanumeric characters in length.
•addr1—First local IP address, as defined by the following XECfgParm.dat parameters:
–IP_Addr1
–IP_Addr2
–IP_Addr3
–IP_Addr4
•addr2—Second local IP address, as defined by the following XECfgParm.dat parameters:
–IP_Addr1
–IP_Addr2
–IP_Addr3
–IP_Addr4
–N/A (default value)
•paddr1—Highest priority destination address, expressed in dot notation.
•paddr2—Lowest priority destination address, expressed in dot notation. This parameter is optional. The default value for this parameter is 0.0.0.0.
•iprte1—MML name of a previously entered IP route (optional).
•iprte2—MML name of a previously entered IP route (optional).
For example, to modify the local IP addresses for an SCTP association named nasassoc1, you would enter the following command:
prov-ed:ASSOCIATION:NAME="dpnssassoc1", IPADDR1="IP_Addr2", IPADDR2="IP_Addr3"
Step 5 Repeat the Step 4 for each SCTP association you want to modify in your provisioning data.
Step 6 If there are no other components that you need to provision, end your provisioning session as described in the "Saving and Activating your Provisioning Changes" section.
Step 7 Set the SCTP association to be modified to the IS state as described in the "Setting the Service State of an Association" section.
Deleting DPNSS Components
The following sections contain the procedures for modifying the various IUA connections in your Cisco PGW 2200 provisioning data:
• Deleting Cisco Access Server External Nodes
• Deleting DPNSS Signaling Services
• Deleting IP Routes
• Deleting SCTP Associations
Deleting Cisco Access Server External Nodes
To delete Cisco access server external nodes, perform the following steps:
Step 1 Set the interface on the external node that is associated with the Cisco MGC software to the out-of-service state. Refer to the documentation for your media gateway for more information on taking interfaces out-of-service.
Step 2 Delete the signaling service(s) associated with this external node. To delete a DPNSS signaling service, perform the steps in the "Deleting DPNSS Signaling Services" section.
Step 3 If your system uses IP routes for this external node, delete the IP routes as described in the "Deleting IP Routes" section.
Step 4 Delete the SCTP associations for this external node, as described in the "Deleting SCTP Associations" section.
Step 5 Enter the following command to delete a Cisco access server external node:
prov-dlt:extnode:name="name"
Where name is the MML name of the Cisco access server external node to be deleted.
For example, to delete an Cisco access server external node named va-3600-37, you would enter the following command:
prov-dlt:extnode:name="va-3600-37"
Step 6 Repeat the above steps for each Cisco access server external node you want to delete from your provisioning data.
Deleting DPNSS Signaling Services
To delete DPNSS signaling services, perform the following steps:
Step 1 Log in to the active Cisco MGC, start an MML session, and enter the following command:
set-dest:sig_srv:OOS
Where sig_srv is the MML name of the desired signaling service.
For example, to set the service state of a signaling service called sigsrv1 to OOS, enter the following command:
set-dest:sigsrv1:OOS
Step 2 Block all of the CICs associated with this signaling service using the following MML command:
blk-cic:sig_svc:all
Where sig_svc is the MML name of the signaling service associated with the CICs to be blocked.
Step 3 Delete the bearer channels associated with this signaling service using the following MML command:
prov-dlt:switchtrnk:dstsrv="sig_svc", "all"
Where sig_svc is the MML name of this signaling service.
Step 4 If trunk groups are provisioned for this signaling servce, delete the trunk groups using the following MML command:
prov-dlt:trnkgrp:dstsrv="sig_svc", "all"
Where sig_svc is the MML name of this signaling service.
Step 5 Enter the following command to delete a DPNSS signaling service:
prov-dlt:dpnsspath:name="name"
Where name is the MML name of the DPNSS signaling service to be deleted.
For example, to delete an DPNSS signaling service named dpnsvc1, you would enter the following command:
prov-dlt:DPNSSPATH:NAME="dpnsvc1"
Step 6 Repeat the above steps for each DPNSS signaling service you want to delete from your provisioning data.
Deleting IP Routes
To delete IP routes, perform the following steps:
Step 1 Set the service state of the IP route to OOS, as described in the "Setting the Service State of an IP Route" section.
Step 2 Delete any components that used this route as a parameter. To delete SCTP associations, perform the steps found in the "Deleting SCTP Associations" section .
Step 3 Enter the following command to delete an IP route:
prov-dlt:iproute:name="name"
Where name is the MML name of the IP route to be deleted.
For example, to delete an IP route named iprte1, you would enter the following command:
prov-dlt:IPROUTE:NAME="iprte1"
Step 4 Repeat the above steps for each IP route you want to delete from your provisioning data.
Deleting SCTP Associations
To delete SCTP associations, perform the following steps:
Step 1 Set the service state of the SCTP association to OOS, as described in the "Setting the Service State of an Association" section.
Step 2 Enter the following command to delete an SCTP association:
prov-dlt:association:name="name"
Where name is the MML name of the association you want to delete.
For example, to delete an SCTP association named nasassoc1, you would enter the following command:
prov-dlt:ASSOCIATION:NAME="nasassoc1"
Step 3 Repeat the above steps for each SCTP association you want to delete from your provisioning data.
Troubleshooting Tips
The following sections contain troubleshooting procedures related to provisioning:
• Alarm Troubleshooting Procedures
• Signaling Channel Troubleshooting Procedures
For more information on troubleshooting the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide.
Alarm Troubleshooting Procedures
The alarms listed below are the new and modified alarms associated with this feature that require user action to be rectified. For a complete list of Cisco MGC alarms, refer to the Cisco Media Gateway Controller Software Release 9 System Messages Guide.
Association Degraded
This alarm occurs when one of the destination address for an SCTP association has failed, but the association is still up.
Corrective Action
To correct the problem identified by this alarm, perform the procedure in the "Resolving an Association Alarm" section.
Association Fail
This alarm occurs when an SCTP association has failed due to an IP connectivity failure or an out-of-service destination.
Corrective Action
To correct the problem identified by this alarm, perform the procedure in the "Resolving an Association Alarm" section.
IP RTE CONF FAIL
This alarm occurs when an IP route cannot find the local interface defined by its IP address parameter.
Corrective Action
To correct the problem identified by this alarm, perform the following steps:
Step 1 Verify that the IP address settings for the identified IP route are correct, using the prov-rtrv MML command, as described in the "Retrieving Provisioning Data" section.
If the IP address settings for your IP route are correct, proceed to Step 2.
If the provisioned settings for your IP route are incorrect, start a dynamic reconfiguration session to change the settings, as described in the "Modifying IP Routes" section.
Step 2 Verify that the other provisioned settings for the identified IP route obtained in Step 1 are correct.
If the other provisioned settings for your IP route are correct, proceed to Step 3.
If the provisioned settings for your IP route are incorrect, start a dynamic reconfiguration session to change the settings, as described in the "Modifying IP Routes" section.
Step 3 Contact the Cisco TAC to further analyze the problem and determine a solution. For more information about contacting the Cisco TAC, refer to the "Obtaining Technical Assistance" section.
IP RTE FAIL
This alarm occurs when an IP route is in the OOS state with a cause other thatn off-duty or commanded out-of-service.
Corrective Action
To correct the problem identified by this alarm, perform the following steps:
Step 1 Verify that the provisioned settings for the identified IP route are correct, using the prov-rtrv MML command, as described in the "Retrieving Provisioning Data" section.
If the provisioned settings for your IP route are correct, proceed to Step 2.
If the provisioned settings for your IP route are incorrect, start a dynamic reconfiguration session to change the settings, as described in the "Modifying IP Routes" section.
Step 2 Contact the Cisco TAC to further analyze the problem and determine a solution. For more information about contacting the Cisco TAC, refer to the "Obtaining Technical Assistance" section.
LIF FAIL
This alarm occurs when a local Ethernet interface has failed.
Corrective Action
To correct the problem identified by this alarm, perform the following steps:
Note If the Association Degraded or Association Failed alarms occur along with this alarm, follow the procedure defined in the "Resolving an Association Alarm" section.
Step 1 Verify that the provisioned settings for the identified line interface are correct, using the prov-rtrv MML command, as described in the "Retrieving Provisioning Data" section.
If the provisioned settings for your line interface are correct, proceed to Step 4.
If the provisioned settings for your line interface are incorrect, proceed to Step 2.
Step 2 Place the identified line interface in the out-of-service administrative state, as described in the "Setting the Administrative State" section of the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide.
Start a dynamic reconfiguration session to change the settings, as described in the "Invoking Dynamic Reconfiguration" section of the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide.
Step 3 Place the identified line interface in the in-service administrative state, as described in the "Setting the Administrative State" section of the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide.
If that does not resolve the problem, proceed to Step 4.
Step 4 Contact the Cisco TAC to further analyze the problem and determine a solution. For more information about contacting the Cisco TAC, refer to the "Obtaining Technical Assistance" section.
Wrong IP Path
This alarm occurs when an IP route or local interface associated with the identified component cannot be used. This can happen when one of the following occurs:
•A route has been overridden by another route in the operating system routing table.
•A route configured on your system has been deleted using the UNIX command route delete.
•An IP link or route has been provisioned incorrectly.
Corrective Action
This alarm can also occur if an IP signaling channel has been misconfigured. Use the netstat -rnv UNIX command to retrieve the current operating system routing table.
To correct the problem identified by this alarm, perform the following steps:
Step 1 Log in to the active Cisco MGC and retrieve the current operating system routing table using the following UNIX command:
netstat -rnv
The system returns a response similar to the following:
IRE Table: IPv4
Destination Mask Gateway Device Flags
----------------- ---------------- -------------- ------ -----
10.82.80.0 255.255.255.0 10.82.82.1 UGH
10.82.81.0 255.255.255.0 10.82.83.1 UGH
10.82.82.0 255.255.255.0 10.82.82.112 hme0 U
10.82.83.0 255.255.255.0 10.82.83.112 hme1 U
default 0.0.0.0 10.82.82.1 UG
224.0.0.0 240.0.0.0 10.82.82.112 hme0 U
127.0.0.1 255.255.255.255 127.0.0.1 lo0 UH
Step 2 If the response does not contain the route identified in the alarm, open the operating system routing table file using a text editor such as vi. Otherwise, proceed to Step 5.
Step 3 Add the route to the routing table using the appropriate text editor command.
Step 4 Save the file and exit the editing session. If this resolves the problem, the procedure is complete. Otherwise, proceed to Step 5.
Step 5 Verify that the provisioned settings for the identified IP link are correct, using the prov-rtrv MML command, as described in the "Retrieving Provisioning Data" section.
If the provisioned settings for your IP link are correct, proceed to Step 6.
If the provisioned settings for your IP link are incorrect, start a dynamic reconfiguration session to change the settings, as described in the "Invoking Dynamic Reconfiguration" section of the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide.
Step 6 Contact the Cisco TAC to further analyze the problem and determine a solution. For more information about contacting the Cisco TAC, refer to the "Obtaining Technical Assistance" section.
Signaling Channel Troubleshooting Procedures
The following signaling channel troubleshooting procedures are new for this feature:
• Resolving an Association Alarm
• Setting the Service State of an Association
• Setting the Service State of an IP Route
Resolving an Association Alarm
When referred here by an alarm indicating a failure on an association, perform the following steps:
Step 1 If this alarm occurs along with a LIF FAIL alarm on the local IP address (ADDR1 and ADDR2), proceed to Step 2. Otherwise, proceed to Step 4.
Step 2 Verify the functioning of the cabling between the Cisco MGC and the LAN switch.
If the cables are functioning properly, proceed to Step 3.
If bad cable(s) are found, replace them. If that resolves the problem, the procedure is complete. Otherwise, proceed to Step 3.
Step 3 Verify the functioning of the associated LAN switch. Refer to the documentation for your LAN switch for the steps necessary for verifying its proper functioning.
If the LAN switch is functioning properly, proceed to Step 6.
If the LAN switch is not functioning properly, refer to documentation for the LAN switch for the appropriate troubleshooting procedures. If that corrects the problem, the procedure is complete. Otherwise, proceed to Step 6.
Step 4 Debug the IP connectivity between the Cisco MGC and the associated access server.
If the IP connectivity is working correctly, proceed to Step 5.
If the IP connectivity is not working correctly, fix the identified problem. If that corrects the problem, the procedure is complete. Otherwise, proceed to Step 5.
Step 5 Determine the health of the associated access server.
If the access server is working correctly, proceed to Step 6.
If the access server is not healthy, fix the problem using the procedures in the user documentation for the access server. If that corrects the problem, the procedure is complete. Otherwise, proceed to Step 6.
Step 6 Contact the Cisco TAC to further analyze the problem and determine a solution. For more information about contacting the Cisco TAC, refer to the "Obtaining Technical Assistance" section.
Setting the Service State of an Association
To change the service state of an association, log in to the active Cisco MGC, start an MML session, and enter the following command:
set-association:assoc_name:serv_state[,confirm]
Where:
•assoc_name—MML name of the association you want to modify.
•serv_state—Service state to which you want to change. Valid values for IP links are IS, OOS, and FOOS.
•confirm—This parameter is required when you are setting the service state to OOS or FOOS.
Note This command cannot be used on the standby Cisco MGC.
For example, to set the service state of the association, assoc1, to OOS, enter the following command:
set-association:assoc1:OOS,confirm
You can verify that the selected association is in the proper service state by performing the procedure in the "Retrieving the Service State for Associations" section.
Setting the Service State of an IP Route
To change the service state of an IP route, log in to the active Cisco MGC, start an MML session, and enter the following command:
set-iproute:iproute_name:serv_state[,confirm]
Where:
•iproute_name—MML name of the IP route you want to modify.
•serv_state—Service state to which you want to change. Valid values for IP links are IS, OOS, and FOOS.
•confirm—This parameter is required when you are setting the service state to OOS or FOOS.
Note This command cannot be used on the standby Cisco MGC.
An IP route in any of the following combinations of primary and secondary service states can be set to OOS or FOOS:
•IS
•OOS, CONF
•OOS, OFF_DUTY
•OOS, STDBY
For an IP route to be set to IS, it must have a primary service state of OOS and secondary service state of COOS.
For example, you would enter the following command to set the service state of an IP route called iprte1 to OOS:
set-iproute:iprte1:OOS,confirm
Note You can verify that the selected IP route is in the proper service state by performing the procedure in the "Retrieving the Service State for IP Routes" section.
Monitoring and Maintaining
The following sections contain the procedures required for proper monitoring and maintenance of this feature. For more information on operational tasks for the rest of the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide
Regular Operations
Introduction of this feature requires the new procedures for managing signaling channels.
Managing Signaling Channels
The following sections are new or modified for Release 9.4:
• Retrieving the Service State for Associations
• Retrieving the Service State for IP Routes
Retrieving the Service State for Associations
To retrieve the service state for an individual association, log in to the active Cisco MGC, start an MML session, and enter the following command:
rtrv-association:assoc_name
For example, to retrieve the service state of an association called assoc1, enter the following command:
rtrv-association:assoc1
The system returns a message similar to the following:
Media Gateway Controller 2000-03-26 20:26:18
M RTRV
"assoc1:IS"
To retrieve attributes for all of the associations, log in to the active Cisco MGC, start an MML session, and enter the following command:
rtrv-association:all
The system returns a message similar to the following:
Media Gateway Controller 2000-03-26 19:23:23
M RTRV
"assoc1:OOS
"assoc2:OOS
"assoc3:OOS
"assoc4:OOS
The valid service states for an association are described in the following sections. If the association is in any other state than IS, attempt to bring it into service, as described in the "Resolving an Association Alarm" section.
Association Primary Service States
The PST field shows the current primary service state of the association. Table 1 lists the valid primary service state values:
Table 1 Association Primary Service States
Link State ID
|
Link State
|
Description
|
INB
|
Install busy
|
When a system is first configured, all associations default to this state.
|
IS
|
In-service
|
Association is IS and fully operational. This is its normal operating state.
|
OOS
|
Out-of-service
|
Association is OOS. The system is actively trying to restore the association.
|
Association Secondary Service States
The SST field shows the current secondary service state of the specified association. Table 2 lists the valid secondary service state values:
Table 2 Association Secondary Service States
Link State ID
|
Link State
|
Description
|
COOS
|
Commanded out-of-service
|
Association has been commanded OOS by the operator.
|
STBY
|
Standby
|
Association on the standby Cisco MGC.
|
CONF
|
Configuration
|
Association is OOS due to a configuration failure.
|
Retrieving the Service State for IP Routes
To retrieve the service state for an individual IP route, log in to the active Cisco MGC, start an MML session, and enter the following command:
rtrv-iproute:iproute_name
For example, to retrieve the service state of an IP route called iprte1, enter the following command:
rtrv-iproute:iprte1
The system returns a message similar to the following:
Media Gateway Controller 2000-03-26 20:26:18
M RTRV
"iprte1:IS"
To retrieve attributes for all of the IP routes, log in to the active Cisco MGC, start an MML session, and enter the following command:
rtrv-iproute:all
The system returns a message similar to the following:
Media Gateway Controller 2000-03-26 19:23:23
M RTRV
"iprte1:IS
"iprte2:IS
The valid service states for an IP route are described in the following sections. If the route is in any other state than IS, attempt to bring it into service, as described in the "Setting the Service State of an IP Route" section.
IP Route Primary Service States
The PST field shows the current primary service state of the IP route. Table 3 lists the valid primary service state values:
Table 3 IP Route Primary Service States
Link State ID
|
Link State
|
Description
|
IS
|
In-service
|
Route is IS and fully operational. This is its normal operating state.
|
OOS
|
Out-of-service
|
Route is OOS. The system is actively trying to restore the link.
|
IP Route Secondary Service States
The SST field shows the current secondary service state of the specified IP route. Table 4 lists the valid secondary service state values:
Table 4 IP Route Secondary Service States
Link State ID
|
Link State
|
Description
|
COOS
|
Commanded out-of-service
|
Route has been commanded OOS by the operator.
|
STBY
|
Standby
|
Routes on the standby Cisco MGC.
|
OFF_DUTY
|
Off duty
|
Route is available for use, but not currently being used.
|
CONF
|
Configuration
|
Route is OOS due to a configuration failure.
|
Configuration Example
This section provides a configuration example of the associated XECfgParm.dat parameters for this feature. Additional configuration examples for the Cisco MGC software can be found in the Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide.
Note Configuration of XECfgParm.dat parameters for this feature is only required when the Cisco MGC hosts are not in the same subnet.
*.IP_NextHop1 = 147.21.135.10
*.IP_NextHop2 = 147.15.170.11
*.IP_NextHop3 = 0.0.0.0
*.IP_NextHop4 = 0.0.0.0
*.IP_NextHop5 = 0.0.0.0
*.IP_NextHop6 = 0.0.0.0
*.IP_NextHop7 = 0.0.0.0
*.IP_NextHop8 = 0.0.0.0
Provisioning Example
This section provides an examples of provisioning for this feature. Additional examples of provisioning for the Cisco MGC software can be found in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
________________________________________
; IP Route
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:IPROUTE:NAME="iprte1",DEST="10.82.80.0",NETMASK="255.255.255.0",NEXTHOP="10.82.82
.1",IPADDR="IP_Addr1",DESC="IP Route 1"
prov-add:IPROUTE:NAME="iprte2",DEST="10.82.81.0",NETMASK="255.255.255.0",NEXTHOP="10.82.82
.1",IPADDR="IP_Addr2",DESC="IP Route 2"
________________________________________
; SS7 External Node
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:extnode:NAME="va-2600-165",TYPE="SLT",DESC="2611 SLT RUDP E1"
prov-add:extnode:NAME="va-2600-166",TYPE="SLT",DESC="2611 SLT RUDP E1"
________________________________________
; Point Codes
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:OPC:NAME="opc",DESC="Own pointcode",NETADDR="1.1.3",NETIND=2,TYPE="TRUEOPC"
prov-add:DPC:NAME="dpc1",DESC="Destination pointcode1",NETADDR="1.1.1",NETIND=2
prov-add:DPC:NAME="dpc2",DESC="Destination pointcode2",NETADDR="1.1.2",NETIND=2
________________________________________
; Signal Services to Inet via SLT
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:SS7PATH:NAME="ss7svc1",DESC="SS7 to dpc1",DPC="dpc1", OPC="opc", MDO="Q761_BASE"
prov-add:SS7PATH:NAME="ss7svc2",DESC="SS7 to dpc2",DPC="dpc2", OPC="opc", MDO="Q761_BASE"
________________________________________
; SS7 linksets
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:LNKSET:NAME="ls1",DESC="linkset 1 to dpc1",APC="dpc1",PROTO="SS7-ITU",TYPE="IP"
prov-add:LNKSET:NAME="ls2",DESC="linkset 2 to dpc2",APC="dpc2",PROTO="SS7-ITU",TYPE="IP"
________________________________________
; SS7 route
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:SS7ROUTE:NAME="rte1",DESC="SS7 Rte
1-dpc1",OPC="opc",DPC="dpc1",LNKSET="ls1",PRI=1
prov-add:SS7ROUTE:NAME="rte2",DESC="SS7 Rte
2-dpc2",OPC="opc",DPC="dpc2",LNKSET="ls2",PRI=1
________________________________________
; Sessionset
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:sessionset:NAME="slt1",ipaddr1="IP_Addr1",ipaddr2="IP_Addr2", PORT=7000,
PEERADDR1="10.82.80.188",PEERADDR2="10.82.81.165",PEERPORT=7000,extnode="va-2600-165",
TYPE="BSMV0",IPROUTE1="iprte1", IPROUTE2="iprte2"
prov-add:sessionset:NAME="slt2",ipaddr1="IP_Addr1",ipaddr2="IP_Addr2",
PORT=7000,PEERADDR1="10.82.80.191",PEERADDR2="10.82.81.166",PEERPORT=7000,
extnode="va-2600-166", TYPE="BSMV0",IPROUTE1="iprte1", IPROUTE2="iprte2"
________________________________________
; C7IPLinks
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:C7IPLNK:NAME="ls1lk1",DESC="SS7ANSI", LNKSET="ls1",
sessionset="slt1",SLC=0,PRI=1,TIMESLOT=0
prov-add:C7IPLNK:NAME="ls2lk1",DESC="SS7ANSI",
LNKSET="ls2",sessionset="slt1",SLC=0,PRI=1,TIMESLOT=2
prov-add:C7IPLNK:NAME="ls1lk2",DESC="SS7ANSI", LNKSET="ls1",
sessionset="slt2",SLC=1,PRI=1,TIMESLOT=0
prov-add:C7IPLNK:NAME="ls2lk2",DESC="SS7ANSI",
LNKSET="ls2",sessionset="slt2",SLC=1,PRI=1,TIMESLOT=2
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; External Node
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:EXTNODE:NAME="va-3660-20",TYPE="AS3660",DESC="IUA DPNSS", ISDNSIGTYPE="IUA"
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; SCTP Association
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
prov-add:ASSOCIATION:NAME="dpnssassoc2",ipaddr1="IP_Addr3",ipaddr2="IP_Addr4",
PEERADDR1="10.82.80.31",PEERADDR2="10.82.81.31", extnode="va-3660-20",
TYPE="IUA",IPROUTE1="iprte1",IPROUTE2="iprte2"
Command Reference
This section documents new, modified, or deleted Man-Machine Language (MML) commands. All other commands are documented in the Cisco Media Gateway Controller Software Release 9 MML Command Reference Guide.
New MML Commands
This section contains the MML commands that are new for this feature.
RTRV-ASSOCIATION—Display State of SCTP Association
Purpose:
|
This MML command displays the primary and secondary states of an SCTP association.
|
Syntax:
|
rtrv-association:assoc_name
rtrv-association:all
|
Input Description:
|
•Assoc_name—MML name of a previously configured SCTP association.
•All—All associations
|
Output Description:
|
SCTP Association—MML name of SCTP association specified.
PST—Primary state; valid values are:
–INB—Installed busy; association has been created but has not yet been commanded IN or OOS with the set-association command.
–IS—In service
–OOS—Out of service
SST—Secondary state; valid values are:
–COOS—Commanded out of service
–STBY—The local platform state is standby
–CONF—Out of service due to a configuration failure
|
Example:
|
The MML command shown in the following example retrieves the state of all associations:
mml> rtrv-association:all
MGC-01 - Media Gateway Controller 2001-01-01 18:57:26
M RTRV
"assoc1:IS"
"assoc2:OOS,COOS"
;
|
Comments:
|
Performance Impact Category: A.
|
RTRV-IPROUTE—Display Primary and Secondary States of an IP Route
Purpose:
|
This MML command displays the primary and secondary states of an IP route.
|
Syntax:
|
rtrv-iproute:ip_route_name
rtrv-iproute:all
|
Input Description:
|
•Ip_route_name—MML name of a previously configured IP route.
•All—Retrieves the primary state of all IP routes.
|
Output Description:
|
IP route—MML name of the specified IP route.
PST—Primary state; valid values are:
–IS—In service
–OOS—Out of service
SST—Secondary state; valid values are:
–COOS—Commanded out of service
–STBY—The local platform state is standby
–OFF_DUTY—The link is available for use but is not currently being used.
–CONF—The link is out of service due to a configuration failure.
|
Example:
|
The MML command shown in the following example retrieves the state of all IP routes:
mml> rtrv-iproute:all
MGC-01 - Media Gateway Controller 2002-06-25 15:13:40.983 EST
M RTRV
"iproute1:IS"
"iproute2:IS"
|
Comments:
|
Performance Impact Category:A
|
SET-ASSOCIATION—Changing Association Primary State
Purpose:
|
This MML command changes the primary state of an SCTP association.
|
Syntax:
|
set-association:assoc_name:PST[,confirm]
|
Input Description:
|
•Assoc_name—MML name of a previously configured SCTP association.
•PST—Desired primary state; valid values are IS, OOS, or FOOS
•Confirm—Verify desired state. This parameter must be used when the primary state desired is OOS or FOOS
|
Example:
|
The MML command shown in the following example changes the primary state of an association to out of service:
mml> set-association:assoc1:OOS,confirm
|
Comments:
|
Performance Impact Category: A
|
SET-IPROUTE—Changing IP Route Primary State
Purpose:
|
This MML command changes the primary and secondary states of an IP route.
|
Syntax:
|
set-iproute:ip_route_name:pst[,confirm]
|
Input Description:
|
•IP_rout_name—MML name of a previously configured IP route.
•PST—Desired primary state; valid values are IS, OOS, or FOOS
•Confirm—Must be used when you set the primary state to OOS or FOOS to verify the new state. An IP route in any of the following states can be commanded OOS or FOOS:
–IS
–OOS,CONF
–OOS,OFF_DUTY
–OOS,STBY.
|
Example:
|
The MML command shown in the following example changes the primary state of an IP route to out of service:
mml> set-iproute:iproute1:oos,confirm
|
Comments:
|
Performance Impact Category: A
|
Modified MML Commands
This section contains the MML commands that were modified for this feature.
PROV-ADD—Add Provisioning Component
Purpose:
|
This MML command adds a component to the Cisco MGC configuration.
|
Syntax:
|
prov-add:<comp>:name="<MML name>",<param name>=<param value>,...
prov-add:lnksetprop:name="<protocol family>",<param name>=<param value>,...
|
Input Description:
|
•lnksetprop—MML NE component consisting of parameters for which you can tune linkset communications. See Appendix A of the Cisco Media Gateway Controller Software Release 9 Provisioning Guide for a list of linkset property parameters.
•comp—MML component type name for the type of configuration you are creating. The component type must match one of the component types listed in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide. If <comp> is EXTNODE, then the <param name> TYPE must be present and needs to take a set of values (refer to the second example below).
•name—MML component name for the new object you are creating (as many as ten characters).
•protocol family—Name of the protocol family for which you are provisioning linkset properties. Use PROV-RTRV:VARIANTS for a list of protocol families configured for your system.
•param name—The name of a valid configuration parameter for the specified component type. Parameter names are listed in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
•param value—The value you want to assign to the parameter. If the parameter value is a string, it should be surrounded by quotation marks.
To define more than one parameter, enter additional param name=param value descriptions on the command line.
|
Example:
|
The MML command shown in the following example adds the origination point code for the MGC configuration:
mml> PROV-ADD:opc:NAME="opc",DESC="Point code of CP1",netaddr="0.0.1",
netind=2,type="TRUEOPC"
Media Gateway Controller - MGC-01 2000-01-12 15:19:51
M COMPLD
"opc"
;
|
Example:
|
The MML command shown in the following example adds an external node to the MGC configuration:
mml> PROV-ADD:EXTNODE:NAME="TOTO2",DESC="TATA",TYPE="MGX8260"
Media Gateway Controller - MGC-02 2000-05-08 18:05:55
M COMPLD
"extnode"
;
|
Comments:
|
Performance Impact Category: B
Refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide for a description of using the PROV commands for provisioning and for a description of components, parameter names, and parameter values used in provisioning the MGC.
|
PROV-DLT—Delete Components or Parameters
Purpose:
|
This MML command deletes a provisioned component.
|
Syntax:
|
prov-dlt:<comp>:name="<MML name>"
prov-dlt:lnksetprop:name="<protocol family>"
|
Input Description:
|
•lnksetprop—MML NE component consisting of parameters for which you can tune linkset communications. See Appendix A of the Cisco Media Gateway Controller Software Release 9 Provisioning Guide for a list of linkset property parameters.
•comp—MML component type name for the type of component you are modifying. The entered parameter must match one of the component types listed in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
•name—MML name of the component you are modifying.
•protocol family—Name of the protocol family for which you are provisioning linkset properties. Use PROV-RTRV:VARIANTS for a list of protocol families configured for your system.
|
Example:
|
The MML command shown in the following example deletes the point code component "opc":
mml> PROV-DLT:opc:NAME="opc"
Media Gateway Controller - MGC-01 2000-01-12 15:19:51
M COMPLD
"opc"
;
|
Comments:
|
Perform PROV-STA—Start Provisioning Session before using this command.
Performance Impact Category: B
Refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide for a description of using the PROV commands for provisioning and for a description of components, parameter names, parameter descriptions, and parameter values used in provisioning.
|
PROV-ED—Modify Provisioned Component
Purpose:
|
This MML command modifies a provisioned component.
Note Only those parameters that need to be modified must be entered.
|
Syntax:
|
prov-ed:<comp>:name="<MML name>",<param name>=<param value>,...
prov-add:lnksetprop:name="<protocol family>",<param name>=<param
value>,...
|
Input Description:
|
•lnksetprop—MML NE component consisting of parameters for which you can tune linkset communications. See Appendix A of the Cisco Media Gateway Controller Software Release 9 Provisioning Guide for a list of linkset property parameters.
•comp—MML component type name for the type of component you are modifying. The entered parameter must match one of the component types listed in the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
•name—MML name for the component you are modifying. You cannot change the component name.
•protocol family—Name of the protocol family for which you are provisioning linkset properties. Use PROV-RTRV:VARIANTS for a list of protocol families configured for your system.
•param name—The name of each configuration parameter you want to change. The parameter names must be valid for the specified component type. Refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide for a description of components, parameter names, parameter descriptions, and parameter values.
•param value—The new value you want to assign to the parameter. If the parameter value is a string, it should be surrounded by quotation marks.
Note To modify more than one parameter, enter additional param name=value descriptions on the command line.
|
Example:
|
The MML command shown in the following example changes the description of the provisioned point code "opc":
mml> PROV-ED:opc:NAME="opc", DESC="Point code for this SSP"
Media Gateway Controller - MGC-01 2000-01-12 15:19:51
M COMPLD
"opc"
;
|
Comments:
|
Perform PROV-STA—Start Provisioning Session before using this command.
Performance Impact Category: B
Refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide for information on using the PROV commands for provisioning and for a description of components, parameter names, and parameter values used in provisioning.
|
RTRV-IPLNK—Display Primary and Secondary States of an IP Link
Purpose:
|
This MML command displays the primary and secondary states of an IP link.
|
Syntax:
|
rtrv-iplnk:ip_link_name
rtrv-iplnk:all
|
Input Description:
|
•IP_link_name—MML name of a previously configured IP link.
•All—Retrieves the primary state of all IP links.
|
Output Description:
|
IP link—MML name of the specified IP link.
PST—Primary state; valid values are:
–INB—Installed busy; association has been created but has not yet been commanded IN or OOS with the set-iplnk command.
–IS—In service
–OOS—Out of service
SST—Secondary state; valid values are:
–COOS—Commanded out of service
–STBY—The local platform state is standby
–OFF_DUTY—The link is available for use but is not currently being used.
–CONF—The link is out of service due to a configuration failure.
|
Example:
|
The MML command shown in the following example retrieves the state of all IP links:
mml> rtrv-iplnk:all
MGC-01 - Media Gateway Controller 2002-06-25 15:13:40.983 EST
M RTRV
"iplink1:IS"
"iplink2:IS"
|
Comments:
|
Performance Impact Category: TBD.
|
Reference Information
The following sections contain reference material related to this feature. Information is included on the following areas:
• XECfgParm.dat Parameters
• Alarms
• Measurements
• Components
• External Node Types
• Provisioning Worksheets
XECfgParm.dat Parameters
The XECfgParm.dat file configuration parameters added for this feature are in the table below.
Configuration Parameter
|
Definition
|
*.IUA.maxNasExtNodes
|
Defines the maximum number of external nodes that can be defined with an ISDN signaling type of IUA. This number also represents the maximum number of IUA associations that can be provisioned.
Valid value: 256
Note Do not change this value.
|
*.IUA.maxNasPathsPerExtNode
|
Defines the maximum number of NAS signaling services that can be assigned to each external node with an ISDN signaling type of IUA.
Valid value: 112
Note Do not change this value.
|
*.IUA.maxNasPaths
|
Defines the maximum number of IUA signaling services that can be provisioned.
Valid value:1500
Note Do not change this value.
|
*.IP_NextHop1
*.IP_NextHop2
*.IP_NextHop3
*.IP_NextHop4
*.IP_NextHop5
*.IP_NextHop6
*.IP_NextHop7
*.IP_NextHop8
|
Defines the IP addresses of up to eight next hop counters. These IP addresses are used when the next hop router IP addresses on the Cisco PGW hosts do not match.
Default: 0.0.0.0
Valid values: An IP address expressed in decimal dot notation.
|
For information on the other XECfgParm.dat parameters, refer to the Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide.
Alarms
This section contains the alarms that are added and modified to support this feature. For information on the other alarms for the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Messages Reference Guide.
New Alarms
The alarms that are added for this feature are listed below.
Association Degraded
Description A destination address of the association has failed, and the association is still in an UP state.
Severity Minor
Cause This alarm is reported when one of the association destination addresses has failed.
Type 1 (Communication error).
Action Refer to the "Association Degraded" section.
Association Fail
Description The SCTP association has failed.
Severity Major
Cause This alarm is reported when the destination node is out of service or there is an IP connectivity failure.
Type 1 (Communication error)
Action Refer to the "Association Fail" section.
Wrong IP Path
Description The IP route or local interface provisioned for the specified component is not being used.
Severity Minor
Cause This alarm is reported when generic analysis cannot access the conditional route description table.
Type 1 (Communication error).
Action Refer to the "Wrong IP Path" section.
Modified Alarms
The alarms that are modified for this feature are described in the following section.
IP RTE CONF FAIL
Description IP route is out of service due to a configuration failure.
Severity Information
Cause This existing alarm is now generated against the IP route components instead of signal channel components Indicates that an IP route is out of service because of a configuration failure.
Type 1 (No error)
Action Refer to the "IP RTE CONF FAIL" section.
IP RTE FAIL
Description IP route is out of service. This existing alarm is now generated by IP route objects instead of the signal channel components.
Severity Information
Cause Indicates that an IP route is out of service.
Type 1 (No error)
Action Refer to the "IP RTE FAIL" section.
LIF FAIL
Description Line interface failure.
Severity Major
Cause This existing alarm is now generated against local interface components. The line interface (LIF) has failed. All physical lines to the Cisco MGC and local interface components can raise this alarm.
Type 4 (Equipment error alarm)
Action Refer to the "LIF FAIL" section.
M-OOS
Description Resource has been manually taken OOS.
Severity Minor
Cause A software process not necessary for normal system operation has been requested manually out of service. This existing alarm is now generated against IP route components.
Type 1 (Communication alarm)
Action Restore the process to the in-service state using the user interface. IP routes can be returned to service using the procedure in the "Setting the Service State of an IP Route" section.
Measurements
Table 5 contains the system measurements that are added to support this feature. For information on the other system measurements, refer to the Cisco Media Gateway Controller Software Release 9 Operations, Maintenance, and Troubleshooting Guide.
Table 5 New Operational Measurements
MML Counter Group:Name
|
Description
|
Related Components
|
Logging Interval
|
IUA GROUP
IUA: ASPUpTx
IUA: ASPUpAckRx
|
IUA message statistics
Number of application server process (ASP) Up messages sent from the Cisco MGC to the media gateway on this SCTP association, indicating that it is ready to receive traffic or maintenance messages.
Number of ASP Up Acknowledgement messages received by the Cisco MGC from the media gateway on this SCTP association.
|
Association
|
15, 60, 24
15, 60, 24
|
IUA: ASPDnTx
IUA: ASPDnAckRx
IUA: ASPActTx
|
Number of ASP Down messages sent from the Cisco MGC to the media gateway on this SCTP association, indicating that it is not ready to receive traffic or maintenance messages.
Number of ASP Up Acknowledgement messages received by the Cisco MGC from the media gateway on this SCTP association.
Number of ASP Active messages sent from the Cisco MGC to the media gateway on this SCTP association, indicating that it is active.
|
|
15, 60, 24
15, 60, 24
15, 60, 24
|
IUA: ASPActAckRx
IUA: ASPInactTx
IUA: ASPInactAckRx
IUA: ErrorRx
|
Number of ASP Active Acknowledgement messages received by the Cisco MGC from the media gateway on this SCTP association.
Number of ASP Inactive messages sent from the Cisco MGC to the media gateway on this SCTP association, indicating that it is inactive.
Number of ASP Inactive Acknowledgement messages received by the Cisco MGC from the media gateway on this SCTP association.
Number of Error messages received by the Cisco MGC from the media gateway on this SCTP association.
|
|
15, 60, 24
15, 60, 24
15, 60, 24
15, 60, 24
|
IUA: NotifyRx
IUA: DataRqt
|
Number of Notify messages received by the Cisco MGC from the media gateway on this SCTP association. These messages provide autonomous indications of IUA events on the media gateway.
Number of Data messages sent from the Cisco MGC to the media gateway on this SCTP association, which are to be transmitted using the Q.921 acknowledged information transfer service.
|
|
15, 60, 24
15, 60, 24
|
IUA GROUP (continued)
IUA: DataInd
IUA: UnitDataRqt
IUA: UnitDataInd
|
IUA message statistics (continued)
Number of Data messages received by the Cisco MGC from the media gateway on this SCTP association which are to be received using the Q.921 acknowledged information transfer service.
Number of Data messages sent from the Cisco MGC to the media gateway on this SCTP association, which are to be transmitted using the Q.21 unacknowledged information transfer service.
Number of Data messages received by the Cisco MGC from the media gateway on this SCTP association, which are to be received using the Q.21 unacknowledged information transfer service.
|
Association
|
15, 60, 24
15, 60, 24
15, 60, 24
|
IUA: EstRqt
IUA: EstConf
IUA: EstInd
IUA: RelRqt
IUA: RelConf
IUA: RelInd
|
Number of requests to establish this SCTP association.
Number of confirms that IUA has established an SCTP association with the media gateway.
Number of times the media gateway has informed Link Management that the Cisco MGC has established an SCTP association.
Number of requests to release an SCTP association with a media gateway.
Number of confirms that IUA has released an SCTP association with the media gateway.
Number of times the media gateway has informed Link Management that the Cisco MGC has released an SCTP association.
|
|
15, 60, 24
15, 60, 24
15, 60, 24
15, 60, 24
15, 60, 24
15, 60, 24
|
SCTP-GROUP
SCTP: OOTB
SCTP: InvalidChksum
SCTP: CtrlTx
SCTP: OrdDataTx
SCTP: UnordDataTx
SCTP: CtrlRx
|
SCTP traffic statistics
Number of out of the blue packets received.
Number of checksum error packets received.
Number control chunks sent.
Number of ordered data chunks sent.
Number of unordered data chunks sent.
Number control chunks received.
|
Association
|
15, 60, 24
15, 60, 24
15, 60, 24
15, 60, 24
15, 60, 24
15, 60, 24
|
SCTP: OrdDataRx
SCTP: UnordDataRx
SCTP: DataSegTx
SCTP: DataSegRx
SCTP: AssocFailures
SCTP: DestFailures
SCTP: PeerRestarted
|
Number of ordered data chunks received.
Number of unordered data chunks received.
Number of SCTP data segments sent.
Number of SCTP data segments received.
Number of association failures.
Number of destination failures.
Number of peer restarts.
|
|
15, 60, 24
15, 60, 24
15, 60, 24
15, 60, 24
15, 60, 24
15, 60, 24
15, 60, 24
|
Components
The sections below contain the provisioning components that are added and modified for this feature. For information on the rest of the components in the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
New Components
The following provisioning components are added for this feature.
DPNSS Signaling Service
The DPNSS signaling service component type represents a DPNSS signaling path that is back-hauled over IP to/from a Network Access Server (destination). Its MML name is as follows:
•MML Name—DPNSSPATH
The DPNSS signaling service component structure is shown in Table 6.
Table 6 DPNSS Signaling Service Component Structure
Parameter MML Name
|
Parameter Description
|
Parameter Values (Default)
|
NAME
|
IP route name
|
The name can be as many as 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter.
|
DESC
|
Component description
|
The description can be up to any 128 characters.
|
EXTNODE
|
External node MML name
|
MML name of a previously defined external node.
|
CUSTGRPID
|
Customer group ID
|
Four digit ID; (0000).
|
ABFLAG
|
DPNSS Side
|
Valid values are a (for A side), b (for B side), and n (for not applicable); (n)
|
SIGSLOT
|
Physical Slot on the NAS defining the NFAS Group (optional)
|
An integer, 0 through 63; (0).
|
SIGPORT
|
Physical Port on the slot of NAS defining the NFAS Groupl. (optional)
|
An integer, 0 through 167
|
The following parameters cannot be modified:
•NAME
•EXTNODE
The following rules apply when creating or editing DPNSS signaling paths:
•The maximum number of combined DPNSSPATHs and IUA NASPATHs per IUA External Node is 112.
•An ASSOCIATION must be defined with same EXTNODE attribute as the DPNSSPATH. If this ASSOCIATION hasn't been defined when the DPNSSPATH is added/edited, a warning is issued. If the ASSOCIATION still hasn't been defined when provisioning session is copied or deployed, an error message is generated and the copy or deployment is stopped.
•If the ASSOCIATION with the same EXTNODE value as the DPNSSPATH is deleted, a warning message is issued to inform the user that the DPNSSPATH must also be deleted. If it hasn't when the provisioning session is copied or deployed, an error message is generated and the copy or deployment is stopped.
IP Route
The IP route represents a static IP route. Its MML name is as follows:
• MML Name—IPROUTE
The IP route component structure is shown in Table 7.
Table 7 IPROUTE Component Structure
Parameter MML Name
|
Parameter Description
|
Parameter Values (Default)
|
NAME
|
IP route name
|
The name can be as many as 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter.
|
DESC
|
Component description
|
The description can be up to any 128 characters.
|
DEST
|
Destination hostname or IP address
|
IP Address in decimal dot notation or hostname that is less than or equal to 32 characters.
|
NETMASK
|
Subnet mask of Destination (optional)
|
IP Address in decimal dot notation. (255.255.255.255)
|
NEXTHOP
|
Next hop router IP address
|
IP Address or hostname that is less than or equal to 32 characters, or one of the following property names defined in XECfgParm.dat:
IP_NextHop1, IP_NextHop2, IP_NextHop8,
IP_Addr1, IP_Addr2, or IP_Addr4.
|
IPADDR
|
Local IP address
|
IP_Addr1, IP_Addr2, IP_Addr3, or IP_Addr4.
|
PRI
|
Priority
|
1 through 65535; (1)
|
Note NAME is the only parameter for this command that cannot be modified.
The following rules apply when creating or editing IP Routes:
•The NETMASK attribute is validated by the system. For your provisioning set-up to work correctly, its value (when converted to binary) must have at least one leading 1 and cannot have any trailing 1s after the first 0. The values 255.255.0.0 and 255.255.255.128 are valid. The values 0.0.255.255, 255.0.0.255, and 0.0.0.0 are invalid.
•Ensure the destination resolves to a non-zero address.
•When the resolved destination address is bit ORed with the netmask value, the result is equal to the netmask (for example, a destination of 10.11.12.13 and a netmask of 255.255.0.0 would be invalid because the ORed result would be 255.255.12.13, which is not equal to 255.255.0.0).
•The combination of DESTINATION, NETMASK, and IPADDR must be unique for each IP Route.
•The combination of DESTINATION, NETMASK, and PRI must be unique for each IP Route.
•When an IP Route is specified in a link object (for example, IPLNK, SESSIONSET, or ASSOCIATION), the IP address resolved from the PEERADDR attribute must be checked against the DESTINATION and NETMASK attributes to verify the IPROUTE is valid.
•When an IP Route is specified in a link object (for example, IPLNK, SESSIONSET, or ASSOCIATION), the IPADDR must match the IPADDR of the link.
•When an IPROUTE is not specified for a link object (having that option), the IP Address resolved from the PEERADDR attribute must be checked against the defined IPROUTES to verify that it should not be assigned an IPROUTE. If the PEERADDR is on the same subnet as the DESTINATION (based on the NETMASK), and if the IPADDR matches the IPADDR of the link object, then use IPROUTE.
•If the NEXTHOP attribute is a hostname or symbolic name from XECfgParm.dat, it can resolve to the address 0.0.0.0, which indicates the IPROUTE is not used. The IPROUTE status shows up in the rtrv-iproute:all command output when in the OOS, OFF_DUTY state.
•If the resolved NEXTHOP address is not 0.0.0.0, it must be on the same subnet of the IPADDR.
The commands to retrieve and set the service state of an IP route can be found in the "Retrieving the Service State for IP Routes" section and the "Setting the Service State of an IP Route" section, respectively.
SCTP Association
The SCTP association represents the connection between the Cisco MGC and a Cisco access server. Its MML name is as follows:
• MML Name—ASSOCIATION
Table 8 Association Component Structure
Parameter MML Name
|
Parameter Description
|
Parameter Values (Default)
|
NAME
|
Unique ID of this component and component name used in MML commands
|
The name can be up to 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
|
DESC
|
Unique ID of this component and component name used in MML commands
|
The name can be up to 128 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with an alphabetic character.
|
TYPE
|
Signaling Type
|
The type of protocol to be used. Values: M3UA, SUA, and IUA
|
SGP
|
SGP's MML name (optional)
|
MML name of a previously configured SGP. Used for M3UA and SUA interfaces.
|
IPADDR1
|
First local address
|
IP_Addr1, IP_Addr2, IP_Addr3, or IP_Addr4.
|
IPADDR2
|
Second local address (optional)
|
IP_Addr1, IP_Addr2, IP_Addr3, IP_Addr4, or N/A.
(N/A)
|
PORT
|
Local SCTP port number (optional)
|
From 1024 through 65535.
Defaults to 9900 for IUA.
Defaults to 2905 for M3UA.
Defaults to 14001 for SUA.
|
PEERADDR1
|
The highest priority destination address
|
IP address
|
PEERADDR2
|
The lowest priority destination address (optional)
|
IP address; (0.0.0.0).
|
PEERPORT
|
Destination SCTP port number. (optional)
|
From 1024 through 65535.
Defaults to 9900 for IUA.
Defaults to 2905 for M3UA.
Defaults to 14001 for SUA.
|
EXTNODE
|
External Node's MML name (optional)
|
MML name of a previously configured external node. Used in IUA interfaces.
|
IPROUTE1
|
MML Name of first IPROUTE (optional)
|
MML name of a previously configured IPROUTE.
|
IPROUTE2
|
MML Name of second IPROUTE (optional)
|
MML name of a previously configured IPROUTE.
|
RCVWIN
|
Number of bytes to advertise for the local receive window. (optional)
|
From 1500 through 65535 (18000).
|
MAXINITRETRANS
|
Maximum number of times to retransmit SCTP INIT message (optional)
|
0 through 100;(10)
0 means use SCTP internal default
|
MAXINITRTO
|
Maximum initial timer retransmission value (optional)
|
0, 300 through 3000 (2000)
0 means use SCTP internal default.
|
MAXRETRANS
|
Maximum number of retransmissions over all destination address before the association is declared failed (optional)
|
From 1 through 10 (5).
Note This value is not to exceed MAXRETRANSDEST * the number of destinations.
|
CUMSACKTO
|
Maximum time after a datagram is received before a SCPT SACK is sent (optional)
|
From 100 through 500 ms; (300).
|
BUNDLETO
|
Maximum time SCTP will wait for other outgoing datagrams for bundling (optional)
|
From 100 through 600 ms; (100).
|
MINRTO
|
Minimum value allowed for the retransmission timer (optional)
|
From 300 through 3000 ms; (300).
|
MAXRTO
|
Maximum value allowed for the retransmission timer (optional)
|
From 1000 through 3000 ms; (3000).
|
HBTO
|
Time between heartbeats. The heartbeat will be this value plus the current retransmission timeout value (optional).
|
The value can be 0, or from 300 through 10000 ms; (2000).
0 means disabled.
|
IPPRECEDENCE
|
Internet Protocol Precedence. This value will be place in the IP PRECEDENCE portion of the Type Of Service field for outgoing SCTP datagrams (optional)
Refer to the right column.
|
ROUTINE 000
PRIORITY 001
IMMEDIATE 010
FLASH 011
FLASH-OVERRIDE 100
CRITICAL 101
INTERNET 110
NETWORK; (ROUTINE) 111
|
DSCP
|
Differential Service Code Point. This value is place in the DSCP portion of the Type Of Service field for outgoing SCTP datagrams (optional)
|
EF 101110—Expedited Forwarding
AF11 001010—Assured Forwarding
Class 1 Low Drop Precedence
AF12 001100—Assured Forwarding
Class 1 Medium Drop Precedence
AF13 001110—Assured Forwarding
Class 1 High Drop Precedence
AF21 010010—Assured Forwarding
Class 2 Low Drop Precedence
AF22 010100—Assured Forwarding 2
Medium Drop Precedence
AF23 010110—Assured Forwarding
Class 2 High Drop Precedence
AF31 011010—Assured Forwarding
Class 3 Low Drop Precedence
AF32 011100—Assured Forwarding
Class 3 Medium Drop Precedence
AF33 011110—Assured Forwarding
Class 3 High Drop Precedence
AF41 100010—Assured Forwarding
Class 4 Low Drop Precedence
AF42 100100—Assured Forwarding
Class 4 Medium Drop Precedence
AF43 100110—Assured Forwarding
Class 4 High Drop Precedence
N/A; (N/A)
|
MAXRETRANSDEST
|
Maximum number of retransmissions to either PEERADDR1 or PEERADDR2 before it is declared failed (optional)
|
From 1 through 10; (3).
|
The SCTP association component structure is shown in Table 8.
The following parameters cannot be modified:
•NAME
•EXTNODE
•TYPE
•SGP
The following rules apply when creating/editing SCTP associations:
•Only one association with a type of IUA can be assigned to an external node
•If the type of the association is IUA, the associated external node must have its ISDN signaling type set to IUA, and that external node must be able to support IUA signaling.
•If two associations have the same port value, the values of IPADDR1 and IPADDR2 must either be the same or both different.
•The values of IPADDR1 and IPADDR2 must be different
•If the value of IPPRECEDENCE is not ROUTINE, the value of DSCP must be N/A
•If the value of DSCP is not N/A, the value of IPPRECEDENCE must be ROUTINE
•The value of MAXRTO must be greater than or equal to the value of MINRTO
•When a peer IP address (PEERADDR1 or PEERADDR2) is not on the local subnet of IPADDR1 or IPADDR2, that peer IP address cannot be on the subnet of any other local interface, even if it is not defined within the Cisco MGC software
•When a peer IP address (PEERADDR1 or PEERADDR2) is not on the local subnet of IPADDR1 or IPADDR2, an IP route (IPROUTE1 or IPROUTE2, respectively) must be specified
•When an IP route is specified, the values set in PEERADDR1 and PEERADDR2 are checked against the DESTINATION and NETMASK values of the IP route(s) to verify that the IP route is valid.
•When an IP route is specified, its value for IPADDR must match the related IP address of the association. In other words, IPROUTE1 should have an IPADDR that matches IPADDR1 on the association, and IPROUTE 2 should have an IPADDR that matches IPADDR2 on the association.
•When an IP route is not specified, the IP address resolved from the PEERADDR1 or PEERADDR2 parameter is checked against the defined IP routes to verify that it should not be assigned to one of those IP routes. If the peer address is on the same subnet as an IP route, the link should use that IP route.
•The value of PEERADDR1 cannot be 0.0.0.0 or 255.255.255.255, and the value of PEERADDR2 cannot be 255.255.255.255
•When a hostname is specified for a peer IP address, the hostname must resolve to an IP address.
•PEERADDR1 and PEERADDR2 can resolve to the same IP Address. If the external node only has one IP address and two IP addresses (IPADDR1 and IPADDR2) are defined, PEERADDR2 should be set to the same value as PEERADDR1.
•Associations, session sets, IP links, SIP links, and SS7 signaling gateway links that share a peer address (that is, PEERADDR, PEERADDR1, or PEERADDR2) must be assigned directly or indirectly to the same external node
•When you are deleting an association, and a NASPATH uses the same external node, a warning message is issued to inform the you that the NASPATH must also be deleted. If it hasn't when the provisioning session is copied or deployed, an error message will be generated and the copy or deployment will be stopped.
•The value of PORT cannot be set to the same value as the PORT attribute of any IP link, session set, SIP link, or SS7 signaling gateway link
•If a value for IPADDR2 or PEERADDR2 is specified, values for IPADDR1 or PEERADDR1 must also be specified. In other words, you cannot have one local address and two remote addresses, or two local addresses and one remote address.
•An IP link, session set, SS7 signaling gateway link, or another association with a different external or signaling gateway node cannot use the resolved value set in PEERADDR1 or PEERADDR2.
•Only one association can be defined to an SS7 signaling gateway process (SGP)
•A value for EXTNODE can be defined only when the association type is IUA
•A value for SGP can be defined only when the association type is M3UA or SUA
•The maximum number of associations with a type of M3UA is defined in the XECfgParm.dat parameter, M3UA.maxSgp
•The maximum number of associations with a type of SUA is defined in the XECfgParm.dat parameter, SUA.maxSgp
The commands to retrieve and set the service state of an association can be found in the "Retrieving the Service State for Associations" section and the "Setting the Service State of an Association" section, respectively.
Modified Components
The following components are modified for this feature.
External Node
The external node component type represents another node with which the MGC communicates. Its MML name is as follows:
•MML Name—EXTNODE
The parameters for EXTNODE are defined in Table 9.
Table 9 External Node Component Structure
Parameter MML Name
|
Parameter Description
|
Parameter Values (Default)
|
NAME
|
MML name
|
The name can be as many as 20 alphanumeric characters. No special characters other than "-" are allowed. The name should begin with a letter.
|
DESC
|
Component description
|
The description can be up to 128 characters.
|
TYPE
|
The type of the external node
|
Valid values can be found in the "External Node Types" section.
|
ISDNSIGTYPE
|
ISDN Signaling Type
|
Valid values are IUA or N/A (default is N/A). Added this parameter in software Release 9.4(1)T.
|
GROUP
|
M3UA/SUA Group Number
|
Value is 1-100 for M3UA or SUA nodes. Value is 0 for nodes that do not support M3UA or SUA. Added this parameter in software Release 9.4(1)T.
|
Note DESC is the only parameter for this command that can be modified:
The following rules apply when creating/editing external nodes:
•TYPE must be one of the valid external node types.
•The maximum number of external nodes with an ISDNSIGTYPE of IUA is 256.
External Node Types
Table 10 lists the valid external node types for this release of Cisco MGC software.
Table 10 External Node Types
External Node MML Name
|
Release
|
Supported Signaling Service Types
|
AS3600
|
Release 9.1(5) and up
|
MGCP IPFAS NAS IUA
|
AS3660
|
Release 9.1(5) and up
|
MGCP IPFAS NAS IUA
|
AS5200
|
Release 9.1(5) and up
|
IPFAS NAS
|
AS5300
|
Release 9.1(5) and up
|
MGCP IPFAS NAS IUA
|
AS5350
|
Release 9.2(2) and up
|
MGCP IPFAS NAS BSMV0 IUA
|
AS5400
|
Release 9.2(2) and up
|
MGCP IPFAS NAS BSMV0 IUA
|
AS5800
|
Release 9.1(5) and up
|
IPFAS NAS
|
AS5850
|
Release 9.1(5) and up
|
IPFAS NAS
|
AS7200
|
Release 9.1(5) and up
|
MGCP IPFAS NAS
|
CAT8510
|
Release 9.1(5) and up
|
MGCP
|
CAT8540
|
Release 9.1(5) and up
|
MGCP
|
C2600
|
Release 9.4(1) and up
|
MGCP IPFAS IUA
|
H323
|
Release 9.1(5) and up
|
EISUP
|
ITP
|
Release 9.4(1) and up
|
M3UA SUA
|
LS1010
|
Release 9.1(5) and up
|
MGCP
|
MC3810
|
Release 9.1(5) and up
|
MGCP IPFAS
|
MGC
|
Release 9.1(5) and up
|
EISUP
|
MGX8260
|
Release 9.1(5) and up
|
MGCP IPFAS NAS
|
MGX8850
|
Release 9.1(5) and up
|
MGCP SGCP IPFAS
|
SLT
|
Release 9.2(2) and up
|
BSMV0
|
TALISS7
|
Release 9.1(5) and up
|
SS7SG
|
UNKNOWN
|
Release 9.1(5) and up
|
UNKNOWN
|
Provisioning Worksheets
This section contains worksheets for the provisioning components required for this feature. For worksheets covering the rest of the provisioning components in the Cisco MGC software, refer to the Cisco Media Gateway Controller Software Release 9 Provisioning Guide.
Table 11 External Node Worksheet Example
Name
|
Type
|
ISDN Signaling Type
|
Group
|
Description
|
va-3600-37
|
AS3600
|
iua
|
|
DPNSS conn to va-3600-37
|
| |
|
|
|
|
| |
|
|
|
|
| |
|
|
|
|
| |
|
|
|
|
| |
|
|
|
|
| |
|
|
|
|
| |
|
|
|
|
| |
|
|
|
|
| |
|
|
|
|
Table 12 DPNSS Signaling Service Worksheet Example
Name
|
External Node
|
Customer Group ID
|
DPNSS Side
|
Signaling Port
|
Signaling Slot
|
Description
|
dpnsvc2
|
va-3660-20
|
|
A
|
0
|
0
|
IUA DPNSSpath to GW
|
| |
|
|
|
|
|
|
| |
|
|
|
|
|
|
| |
|
|
|
|
|
|
| |
|
|
|
|
|
|
| |
|
|
|
|
|
|
| |
|
|
|
|
|
|
| |
|
|
|
|
|
|
| |
|
|
|
|
|
|
| |
|
|
|
|
|
|
Table 13 IP Route Worksheet Example (optional)
Name
|
Destination
|
Subnet Mask
|
Next Hop
|
IP Address
|
Priority
|
Description
|
iproute1
|
va-3600-37
|
255.255.255.0
|
va-3600-36
|
175.25.211.17
|
1
|
IP route to va-3600-37
|
| |
|
|
|
|
|
|
| |
|
|
|
|
|
|
| |
|
|
|
|
|
|
| |
|
|
|
|
|
|
| |
|
|
|
|
|
|
| |
|
|
|
|
|
|
| |
|
|
|
|
|
|
| |
|
|
|
|
|
|
| |
|
|
|
|
|
|
Table 14 SCTP Association Worksheet Example
Parameter
|
Parameter Value
|
Name
|
nasassoc1
|
|
|
|
|
|
Description
|
DPNSS IUA association 1
|
|
|
|
|
|
Signaling Type
|
IUA
|
|
|
|
|
|
SGP name
|
|
|
|
|
|
|
First local address
|
IP_Addr1
|
|
|
|
|
|
Second local address (optional)
|
IP_Addr2
|
|
|
|
|
|
Local SCTP port number (optional)
|
|
|
|
|
|
|
Highest priority destination address
|
10.82.80.30
|
|
|
|
|
|
Lowest priority destination address (optional)
|
10.82.81.30
|
|
|
|
|
|
Destination SCTP port number (optional)
|
|
|
|
|
|
|
External node name
|
va-3600-37
|
|
|
|
|
|
First IP route name (optional)
|
iprte1
|
|
|
|
|
|
Second IP route name (optional)
|
iprte2
|
|
|
|
|
|
Number of bytes to advertise for the local receive window. (optional)
|
|
|
|
|
|
|
Maximum number of times to retransmit SCTP INIT message (optional)
|
|
|
|
|
|
|
Maximum initial timer retransmission value (optional)
|
|
|
|
|
|
|
Maximum number of retransmissions over all destination address before the association is declared failed (optional)
|
|
|
|
|
|
|
Maximum time after a datagram is received before a SCPT SACK is sent (optional)
|
|
|
|
|
|
|
Maximum time SCTP will wait for other outgoing datagrams for bundling (optional)
|
|
|
|
|
|
|
Minimum value allowed for the retransmission timer (optional)
|
|
|
|
|
|
|
Maximum value allowed for the retransmission timer (optional)
|
|
|
|
|
|
|
Time between heartbeats (optional).
|
|
|
|
|
|
|
IP Precedence (optional)
|
|
|
|
|
|
|
Differential Service Code Point (optional)
|
|
|
|
|
|
|
Maximum number of retransmissions to either peer address 1 or 2 before it is declared failed (optional)
|
|
|
|
|
|
|
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you with these tasks:
•Streamline business processes and improve productivity
•Resolve technical issues with online support
•Download and test software packages
•Order Cisco learning materials and merchandise
•Register for online skill assessment, training, and certification programs
If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:
http://www.cisco.com
Technical Assistance Center
The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Cisco TAC inquiries are categorized according to the urgency of the issue:
•Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.
•Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
•Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.
•Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.
The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to this URL:
http://www.cisco.com/tac
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:
http://www.cisco.com/register/
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
Glossary
Table 15 contains definitions of acronyms and technical terms used in this feature module.
Table 15 Glossary
Term
|
Definition
|
ANSI
|
American National Standards Institute
|
CIC
|
Carrier Identification Code
|
DPNSS
|
Digital Private Network Signaling System—A PBX standard developed in the United Kingdom.
|
EISUP
|
Extended ISDN User Part—A proprietary protocol used to communicate between Cisco MGC nodes and between a Cisco MGC node and a Cisco H.323 System Interface.
|
I/O
|
Input/Output
|
IOCC
|
Input/Output Channel Controller
|
IOCM
|
Input/Output Channel Controller Manager
|
ISDN
|
Integrated Services Digital Network
|
ISUP
|
ISDN User Part
|
ITU
|
International Telecommunication Union
|
IUA
|
ISDN Q.921 User Adaptation Layer
|
LNP
|
Local Number Portability
|
M3UA
|
Message Transfer Point Level 3 User Adaptation
|
MGC
|
Media Gateway Controller
|
MGCP
|
Media Gateway Control Protocol
|
MIB
|
Managed Information Base
|
MML
|
Man-Machine Language
|
MTP3
|
Message Transfer Point Level 3
|
NAS
|
Network Access Server
|
NFAS
|
Non-Facility Associated Signaling
|
PSTN
|
Public Switched Telephone Network
|
Q.931
|
ITU Document that defines the ISDN connection control protocol.
|
Q.921
|
ITU Document that defines the data link protocol used on an ISDN D-channel. Also known as Link Access Protocol - D Channel (LAPD)
|
RFC
|
Return For Comment—A proposed standards document. There are RFCs for both IUA and SCTP.
|
RLM
|
Redundant Link Manager—A proprietary protocol used for the transport of Q.931 data between a Cisco MGC host and an associated media gateway.
|
SCCP
|
Service Connection Control Part
|
SCTP
|
Stream Controlled Transmission Protocol
|
SIGTRAN
|
Signaling Transport—An IETF working group that addresses the transport of packet-based PSTN signaling over IP networks.
|
SIP
|
Session Initiation Protocol
|
SS7
|
Signaling System 7
|
SUA
|
SCCP User Adaptation
|
TALI
|
Transport Adapter Layer Interface
|
TCAP
|
Transaction Capability Application Part
|
UDP
|
User Datagram Protocol
|
