|
|
The ATM Signaling (Global) category provides two subcategories:
When the ATM Signaling (Global) category is selected, the default window displayed is the Closed User Group window.
If you select the ATM Signaling (Global) category, the Closed User Group window opens. The Closed User Group window (Figure 6-25) allows you to create a new closed user group or modify an existing group.
The action buttons are as follows:

If you select the Enable/Disable Closed User Group on Interface category, the Enable/Disable Closed User Group on Interface window (Figure 6-26) opens and allows you to create a new entry. To create a new entry, click Create and assign values to the fields. After values are entered, click Apply to commit to set configuration to the switch.

The ATM Signaling Diagnosis category provides the following subcategories:
When the ATM Signaling Diagnosis category is selected, the default window displayed is the Signaling Diagnosis Filter window.
If you select the ATM Signaling Diagnosis category, the Signaling Diagnosis Filter window opens. The Signaling Diagnosis Filter window (Figure 6-27) opens and allows you to create a new entry. To create a new entry, click Create and assign values to the fields. After values are entered, click Apply to commit to set configuration to the switch. (See "Hints for Creating a Signaling Diagnosis Filter Entry" for more information.)

When defining the fields, consider the following:
If you select the Enable/Disable Signaling Diagnosis category, the Enable/Disable Signaling Diagnosis window (Figure 6-28) allows you to enable or disable the call failure filter. After selecting enable or disable, click Modify to commit the modification.

The PNNI (Global) category allows you to access the Private Network-Network Interface (PNNI). The following subcategories are available:
When the PNNI (Global) category is selected, the default window opened is the PNNI Route Address window.
If you select the PNNI (Global) category, the PNNI Route Address window opens. The PNNI Route Address window (Figure 6-29) displays PNNI route information for the switch.

The action buttons are as follows:
When defining the fields, consider the following:
If you select the PNNI Rerouting Group category, the PNNI Rerouting Group window opens. The PNNI Rerouting Group window (Figure 6-30) displays PNNI rerouting group information for the device.

If you select the Cisco PNNI Base Group category, the Cisco PNNI Base Group window opens. The Cisco PNNI Base Group window (Figure 6-31) displays Cisco-specific PNNI base group information for the device and allows you to modify the current configuration. To modify the current configuration, edit the field(s) and click Modify to commit the modification. If an invalid value is entered, an error message opens. (See "Hints for Modifying Cisco PNNI Base Group Entry" for more information.)

When defining the fields, consider the following:
If you select the PNNI Node Basic category, the PNNI Node Basic window opens. The PNNI Route Address window (Figure 6-32) displays basic configuration information for the PNNI nodes defined on the device.

The action buttons are as follows:
If you select the PNNI Node Advanced category, the PNNI Node Advanced window opens. The PNNI Node Advanced window (Figure 6-33) displays advanced configuration information for the PNNI nodes defined on the device and allows you to modify the current configuration. To modify the current configuration, edit the field(s) and click Modify to commit the modification. If an invalid value is entered, an error message opens.

If you select the Cisco PNNI Node category, the PNNI Node Basic window opens. The PNNI Route Address window (Figure 6-34) displays Cisco-specific configuration information for the PNNI nodes defined on the device.

The action buttons are as follows:
When defining the fields, consider the following:
If you select the PNNI Node Timer category, the PNNI Node Timer window opens. The PNNI Node Timer window (Figure 6-35) displays timer information for the PNNI nodes defined on the device and allows you to modify the current configuration. To modify the current configuration, edit the field(s) and click Modify to commit the modification. If an invalid value is entered, an error message opens. (See "Hints for Modifying a PNNI Node Timer Entry" for more information.)

When defining the fields, consider the following:
If you select the PNNI Link category, the PNNI Link window opens. The PNNI Link window (Figure 6-36) displays link information for the PNNI nodes defined on the device.

If you select the PNNI Neighbor Ports category, the PNNI Neighbor Ports window opens. The PNNI Neighbor Ports window (Figure 6-37) displays information about the neighboring peer nodes for the PNNI nodes defined on the device.

If you select the PNNI Summary category, the PNNI Summary window opens. The PNNI Summary window (Figure 6-38) displays PNNI summary information for the PNNI nodes defined on the device.

The action buttons are as follows:
If you select the PNNI Scope Mapping category, the PNNI Scope Mapping window opens. The PNNI Scope Mapping window (Figure 6-39) displays PNNI hierarchical levels for each node defined on the device.

The action buttons are as follows:
If you select the Cisco PNNI Precedence category, the Cisco PNNI Precedence window opens. The Cisco PNNI Precedence window (Figure 6-40) defines the PNNI precedence value for each address type on the device and allows you to modify the current configuration. To modify the current configuration, edit the field(s) and click Modify to commit the modification. If an invalid value is entered, an error message opens.

If you select the Cisco PNNI Route Address category, the Cisco PNNI Route Address window opens. The Cisco PNNI Route Address window (Figure 6-41) defines the PNNI forwarding address used for call matching on the device. To modify the current configuration, edit the field(s) and click Modify to commit the modification. If an invalid value is entered, an error message opens.

|
|