Table Of Contents
Configuring Hardware
5.1 Overview
5.2 Using the NE Explorer to Configure Optical and Core Router NEs
5.2.1 Exporting an NE Configuration
5.2.2 Understanding the Color Scheme Used for Port and Alarm Status on CTC-Based NEs
5.3 Configuring Routing Protocols on Optical NEs
5.3.1 Specifying a Routing Protocol
5.3.2 Viewing Routing Tables for CTC-Based NEs
5.3.3 Creating Static Routes for CTC-Based NEs
5.3.4 Using OSPF with CTC-Based NEs
5.3.5 Using RIP
5.3.6 Creating and Modifying an SDCC, LDCC, or GCC Termination on Transponder Cards
5.3.7 Creating and Modifying an SDCC, LDCC, GCC, or OSC Termination on SONET or SDH Cards
5.3.8 Creating a DCC Tunnel Connection
5.3.9 Using SNMP
5.3.10 Specifying the Preferred Copy—ONS 15600 SONET or ONS 15600 SDH
5.3.11 Enabling Intermediate Path Performance Monitoring
5.3.12 Enabling Pointer Justification Count Monitoring for CTC-Based NEs
5.3.13 Changing the Power Monitoring Threshold for the ONS 15454 SONET and ONS 15454 SDH
5.3.14 Creating an Ethernet Threshold
5.4 Synchronizing the Network for Optical Devices
5.4.1 Synchronization Settings for the ONS 15310 CL, ONS 15310 MA, ONS 15327, ONS 15454 SONET, and ONS 15600 SONET
5.4.2 Synchronization Settings for the ONS 15454 SDH and ONS 15600 SDH
5.5 Synchronizing the Network for MGX Voice Gateway Devices
5.5.1 Viewing Clocking Sources
5.6 Configuring and Administering the CRS-1 and XR 12000
5.6.1 Explicit Path Configuration Application
5.6.2 MPLS-TE Configuration Application
5.6.3 VRF Application
5.6.4 Interface Common Attributes Configuration Application
5.6.5 Interface Ethernet Configuration Application
5.6.6 Interface POS Configuration Application
5.6.7 SONET Port Configuration Application
5.6.8 Access Control Lists Application
5.6.9 Packet Filter Application
5.6.10 QoS Application
5.6.11 Routing Policy Manager Application
5.6.12 BGP Configuration Application—CRS-1 and XR 12000 R3.0 and R3.2
5.6.13 BGP Configuration Application—CRS-1 and XR 12000 R3.3
5.6.14 ISIS Configuration Application
5.6.15 LDP Configuration Application
5.6.16 OSPF Configuration Application
5.6.17 RSVP Configuration Application
5.6.18 Static Route Configuration
5.6.19 Template Configuration
5.6.20 Telnet Plus
5.6.21 SSHv1 and SSHv2
5.6.22 AAA Administration
5.6.23 Alarm Administration
5.6.24 User Administration
5.6.25 Rolling Back to a Checkpoint for the CRS-1 and XR 12000
5.6.26 Configuring Secure Socket Layer for the CRS-1 and XR 12000
5.7 Configuring the MDS 9000
5.8 Configuring the ONS 15216
5.9 Configuring the ONS 15302 and ONS 15305
5.10 Configuring the ONS 15310 CL, ONS 15310 MA, ONS 15327, ONS 15454 SONET, and ONS 15454 SDH
5.10.1 Provisioning an ONS 15310 CL, ONS 15310 MA, ONS 15327, ONS 15454 SONET, or ONS 15454 SDH Card Slot
5.10.2 Resetting a Card
5.10.3 Deleting a Card
5.10.4 Changing a Card
5.10.5 Inserting an AIS-V on an STS-1 SD-P
5.10.6 Changing Secure Config Mode—ONS 15454 SONET or ONS 15454 SDH
5.11 Configuring the ONS 15501, ONS 15530, and ONS 15540
5.12 Configuring the ONS 15600 SONET and ONS 15600 SDH
5.12.1 Resetting a Card
5.12.2 Deleting a Card
5.12.3 Changing a Card
5.13 Configuring the ONS 15800, ONS 15801, and ONS 15808
5.13.1 Synchronizing the ONS 15800, ONS 15801, and ONS 15808 Configuration and Inventory
5.13.2 Manually Resetting the ONS 15800, ONS 15801, or ONS 15808
5.13.3 Tagging an ONS 15800, ONS 15801, or ONS 15808 Module as Out of Service
5.14 Configuring MGX Voice Gateway Devices
5.14.1 How Do I Manage My Network with the Chassis View?
5.14.2 How Do I Manage My Network with the Configuration Center?
5.14.3 How Do I Manage Templates for NEs?
5.14.4 How Do I Configure MGX Voice Gateway Devices?
5.14.5 How Do I Create or Modify APS?
Configuring Hardware
This chapter describes the various NE configuration procedures that can be managed by CTM. This chapter contains the following sections:
•
Overview
•Using the NE Explorer to Configure Optical and Core Router NEs
•Configuring Routing Protocols on Optical NEs
•Synchronizing the Network for Optical Devices
•Synchronizing the Network for MGX Voice Gateway Devices
•Configuring and Administering the CRS-1 and XR 12000
•Configuring the MDS 9000
•Configuring the ONS 15216
•Configuring the ONS 15302 and ONS 15305
•Configuring the ONS 15310 CL, ONS 15310 MA, ONS 15327, ONS 15454 SONET, and ONS 15454 SDH
•Configuring the ONS 15501, ONS 15530, and ONS 15540
•Configuring the ONS 15600 SONET and ONS 15600 SDH
•Configuring the ONS 15800, ONS 15801, and ONS 15808
•Configuring MGX Voice Gateway Devices
5.1 Overview
In order for CTM to communicate with NEs, certain configuration tasks must be performed on the NEs. Until these configuration tasks are completed, CTM cannot contact the NEs, and no management can begin.
Before CTM can manage NEs, the following conditions must be met:
•Ethernet—Management Ethernet port must be configured.
•Password—Current privileged command password must be configured.
•Telnet—Gigabit Route Processor (GRP) should accept a Telnet session.
•SNMP—GRP must be SNMP-manageable.
Configuration management functions control, identify, retrieve data from, and provide data to network resources to deliver customer services. Configuration management includes broad categories traditionally known as network planning and engineering, installation, network and service provisioning, service planning and negotiation, and status and control.
5.2 Using the NE Explorer to Configure Optical and Core Router NEs
Step 1 In the Domain Explorer window, select the NE that you want to configure.
Note Not all NEs have an associated NE Explorer. See Table 1-11 on page 1-25 for more information.
Step 2 Choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 3 In the NE Explorer tree, click the top-level NE node to open the node properties pane.
Step 4 Complete one of the following options, depending on the NE type:
•For optical NEs, click the tab (or subtab) that corresponds to the setting(s) you want to change. Modify the settings. For drop-down lists, select an item from the list. For numerics or editable text fields, double-click the field and type the new number or text. Click Apply.
•For the CRS-1 and XR 12000, the NE Explorer is menu-based. Use the Configuration and Administration menu options to configure the CRS-1 and XR 12000. For details, see Configuring and Administering the CRS-1 and XR 12000.
5.2.1 Exporting an NE Configuration
Use the NE Configuration Export dialog box to save the NE configuration information for CTC-based and ONS 1580x NEs.
Step 1 In the Domain Explorer tree, select a CTC-based or ONS 1580x NE.
Step 2 Choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 3 In the NE Explorer window, choose Configuration > Export NE Configuration. The NE Configuration Export dialog box opens.
Step 4 Configure the fields. The following table provides descriptions.
Step 5 After making your selections, click OK.
Step 6 Click Yes in the confirmation dialog box. While the export is in progress, a progress bar tracks the percentage to completion.
Step 7 A confirmation dialog box indicates that the data was successfully exported. Click OK.
Table 5-1 Field Descriptions for the NE Configuration Export Dialog Box
Field
|
Description
|
Field Separator
|
You can export the data as comma-separated values (CSV) or tab-separated values (TSV), which are formats commonly used to import data into spreadsheet and database applications for further analysis and manipulation. Click Other if you want to separate the CTM data values with a different character. An error occurs if you select Other but do not insert a separator character.
|
Enclose text in double quotes if it has separator
|
If checked, exported text is enclosed in double quotation marks if that text has a separator. If you choose the CSV format, you must check this option to avoid generating an error.
|
Export configuration of the selected module only
|
If checked, only the selected module's configuration is exported.
|
Export to file
|
By default, exported data is stored in the C:\Cisco\TransportManagerClient<version_number>\exports or /opt/CiscoTransportManagerClient<version_number>/exports directory under the name that you provide in the Export to file text box. Click Browse to change the file location. An error occurs if you do not specify a filename for the configuration file.
|
Below is an example of the exported information:
Date:,1/04/2005 10:06:29.893 AM,
ENDMODULE:,sjc4-310a-168-238,
5.2.2 Understanding the Color Scheme Used for Port and Alarm Status on CTC-Based NEs
The NE Explorer shelf views and card-level views for CTC-based NEs report the port and alarm status as a background color. This background color feature is configurable; you can enable or disable the display of background port color in the NE Explorer. This feature is available only if the card is physically present on the NE and is provisioned in CTM.
Figure 5-1 shows the color scheme used to represent the port state and alarm status. Figure 5-2 and Figure 5-3 show how the color-coded ports appear in the Network Explorer window.
Figure 5-1 Colors of Port State and Alarm Status
Row
|
Color
|
Port State
|
Port State Abbreviation
|
Alarm Status
|
1
|
Gray
|
Out of Service
|
OOS_DSBLD
|
—
|
2
|
Cyan
|
Out of Service-Maintenance
|
OOS_MT
|
—
|
3
|
Purple
|
In Service
|
IS_AINS
|
—
|
4
|
Green
|
In Service
|
IS
|
Clear
|
5
|
Light blue
|
In Service
|
IS
|
Warning
|
6
|
Yellow
|
In Service
|
IS
|
Minor
|
7
|
Orange
|
In Service
|
IS
|
Major
|
8
|
Red
|
In Service
|
IS
|
Critical
|
Figure 5-2 Sample of Ports with OOS, OOS_MT, IS_AINS, and IS States
Figure 5-3 Sample of Ports in IS State with Critical, Major, Minor, and Warning Alarms
5.3 Configuring Routing Protocols on Optical NEs
This section describes how to configure the various routing protocols supported by CTM. This section contains the following information:
•Specifying a Routing Protocol
•Viewing Routing Tables for CTC-Based NEs
•Creating Static Routes for CTC-Based NEs
•Using OSPF with CTC-Based NEs
•Using RIP
•Creating and Modifying an SDCC, LDCC, or GCC Termination on Transponder Cards
•Creating and Modifying an SDCC, LDCC, GCC, or OSC Termination on SONET or SDH Cards
•Creating a DCC Tunnel Connection
•Using SNMP
•Specifying the Preferred Copy—ONS 15600 SONET or ONS 15600 SDH
•Enabling Intermediate Path Performance Monitoring
•Enabling Pointer Justification Count Monitoring for CTC-Based NEs
•Changing the Power Monitoring Threshold for the ONS 15454 SONET and ONS 15454 SDH
•Creating an Ethernet Threshold
5.3.1 Specifying a Routing Protocol
CTM allows you to choose a routing protocol for the LAN interface for CTC-based NEs. You can choose one of the following:
•Open Shortest Path First (OSPF)
•Routing Information Protocol (RIP)
•SNMP
By default, no routing protocol is specified.
5.3.2 Viewing Routing Tables for CTC-Based NEs
Step 1 In the Domain Explorer tree, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Network tab.
Step 3 Click the Routing Table subtab.
5.3.3 Creating Static Routes for CTC-Based NEs
Step 1 In the Domain Explorer tree, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Network tab.
Step 3 Click the Static Routes subtab.
Step 4 Click Create. The Create New Static Route dialog box opens. The following table provides descriptions.
Step 5 After making your selections, click OK.
Table 5-2 Field Descriptions for the Create New Static Route Dialog Box
Field
|
Description
|
Destination
|
Enter the IP address of the computer running CTM.
|
Length
|
Enter the subnet mask length (a decimal number representing the subnet mask length, in bits).
|
Mask
|
Enter the subnetwork mask IP address.
|
Next Hop
|
Enter the IP address of the router port or the node IP address if the CTM computer is connected to the node directly.
|
Cost
|
Enter the number of hops between the NE and the computer running CTM.
|
5.3.4 Using OSPF with CTC-Based NEs
Step 1 In the Domain Explorer tree, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Network tab.
Step 3 Click the OSPF subtab.
Step 4 Complete the following fields. Fields shown depend on the type of NE selected.
•DCC OSPF Area ID—Number that identifies the NE as a unique OSPF area. It can be between 0.0.0.0 and 255.255.255.255. The number must be unique to the LAN OSPF area.
•SDCC Metric—Cost of sending packets across the SDCC, which is used by OSPF routers to calculate the shortest path.
•LDCC Metric—Cost of sending packets across the LDCC, which is used by OSPF routers to calculate the shortest path.
•OSPF Active on LAN—When checked, it enables the OSPF topology to be advertised to OSPF routers on the LAN.
•LAN Port Area ID—OSPF area ID for the router port where the NE is connected. This number is different from the DCC OSPF Area ID.
•Authentication Type—Displays either one of the following:
–Simple Password—If the router where the NE is connected uses authentication.
–No Authentication—If the router where the NE is connected does not use authentication.
•Authentication Key—Displays the OSPF key (or password) if authentication is enabled.
•Router Priority—Designated router for a subnet.
•Hello Interval—Number of seconds between OSPF hello packet advertisements sent by OSPF routers. The Cisco default is 10 seconds.
•Dead Interval—Number of seconds that will pass while an OSPF router's packets are not visible before its neighbors declare the router down. The Cisco default is 40 seconds.
•Transit Delay—Service speed. The Cisco default is 1 second.
•Retransmit Int—Time that will elapse before a packet is resent. The Cisco default is 5 seconds.
•LAN Metric—Cost for sending packets across the LAN. Values should be greater than zero.
Step 5 Click Apply.
5.3.4.1 Creating an OSPF Area Range
Step 1 In the Domain Explorer tree, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Network tab.
Step 3 Click the OSPF subtab and check the OSPF Active on LAN check box. (See Using OSPF with CTC-Based NEs for more information.)
Step 4 Click Apply.
Step 5 Click the OSPF Area Range subtab.
Step 6 Click Create. The Create OSPF Area Range dialog box opens. The following table provides descriptions.
Step 7 After making your selections, click OK.
Note If no range address is created when enabling OSPF on a LAN from CTM, you must manually provision the OSPF area range address for the respective range area IDs, as described in this procedure. Alternately, enable OSPF from CTC so that the range address is created when OSPF is enabled. This is a known issue that has been tracked using DDTS number CSCin62975.
Table 5-3 Field Descriptions for the Create OSPF Area Range Dialog Box
Field
|
Description
|
Range Address
|
Enter the area IP address for the NEs that reside within the OSPF area. For example, if the OSPF area includes nodes with IP addresses 10.10.20.100, 10.10.30.150, 10.10.40.200, and 10.10.50.250, the range address would be 10.10.0.0.
|
Range Area ID
|
Enter the OSPF area ID for the NEs. This is either the ID in the DCC OSPF Area ID field or the ID in the Area ID for LAN Port field. The ID cannot be 0.0.0.0.
|
Mask Length
|
Enter the subnet mask length.
|
Advertise
|
Check this check box if you want the area range to be advertised.
|
5.3.4.2 Deleting an OSPF Area Range
Step 1 In the Domain Explorer tree, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Network tab.
Step 3 Click the OSPF Area Range subtab.
Step 4 Select the OSPF area range from the table; then, click Delete.
Step 5 Click OK in the confirmation message box.
5.3.4.3 Managing OSPF Virtual Links
The following sections describe how to manage OSPF virtual links.
5.3.4.3.1 Viewing OSPF Virtual Links
Step 1 In the Domain Explorer tree, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Network tab.
Step 3 Click the OSPF Virtual Links subtab. The following information is displayed:
•Neighbor—Router ID of the Area 0 router.
•Transit Delay—Service speed. The Cisco default is 1 second.
•Retransmit Interval—Time that will elapse before a packet is resent. The Cisco default is 5 seconds.
•Hello Interval—Number of seconds between OSPF hello packet advertisements sent by OSPF routers.
•Dead Interval—Number of seconds that will pass while the packets of an OSPF router are not visible before its neighbors declare the router down.
•Authentication Type—Authentication type.
•Auth Key—Authentication key.
5.3.4.3.2 Creating an OSPF Virtual Link
Step 1 In the Domain Explorer tree, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Network tab.
Step 3 Click the OSPF subtab and check the OSPF Active on LAN check box. (See Using OSPF with CTC-Based NEs for more information.)
Step 4 Click Apply.
Step 5 Click the OSPF Virtual Links subtab.
Step 6 Click Create. The Create New Virtual Link dialog box opens and allows you to define a link between OSPF area border routers. The following table provides descriptions.
Step 7 After making your selections, click OK.
Table 5-4 Field Descriptions for the Create New Virtual Link Dialog Box
Field
|
Description
|
Neighbor
|
Specify the IP address of the Area 0 router.
|
Transit Delay
|
Specify the service speed. The Cisco default is 1 second.
|
Retransmit Interval
|
Specify the time that will elapse before a packet is resent. The Cisco default is 5 seconds.
|
Hello Interval
|
Specify the number of seconds between OSPF hello packet advertisements. The Cisco default is 10 seconds.
|
Dead Interval
|
Specify the number of seconds that will pass while the packets of an OSPF router are not visible before its neighbors declare the router down. The Cisco default is 40 seconds.
|
Authentication Type
|
Specify the authentication type. Select Simple Password if the router where the NE is connected uses authentication. Otherwise, select No Authentication.
|
Authentication Key
|
Enter the OSPF key (password) if authentication is enabled.
|
Confirm Authentication Key
|
Reenter the authentication key to confirm it.
|
5.3.4.3.3 Modifying an OSPF Virtual Link
Step 1 In the Domain Explorer tree, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Network tab.
Step 3 Click the OSPF Virtual Links subtab.
Step 4 Select an OSPF virtual link to modify; then click Edit.
Step 5 The Modify Virtual Link dialog box opens. Modify the following:
•Neighbor—Enter the new IP address.
•Transit Delay—Indicates the service speed.
•Retransmit Delay—Sets the time that will elapse before a packet is resent.
•Hello Interval—Sets the number of seconds between OSPF hello packet advertisements sent by OSPF routers.
•Dead Interval—Sets the number of seconds that will pass while an OSPF router's packets are not visible before its neighbors declare the router down.
•Authentication Type—Select the authentication type. Select either No Authentication or Simple Authentication.
•Auth Key—If Simple Authentication is selected as authentication type, enter the authentication key.
•Confirm Auth Key—Re-enter the authentication key.
Step 6 Click OK.
5.3.4.3.4 Deleting an OSPF Virtual Link
Step 1 In the Domain Explorer tree, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Network tab.
Step 3 Click the OSPF Virtual Links subtab.
Step 4 Select an OSPF virtual link to delete; then, click Delete.
Step 5 Click Yes in the confirmation dialog box.
5.3.5 Using RIP
Step 1 In the Domain Explorer tree, select an ONS 15310 CL, ONS 15310 MA, ONS 15327, ONS 15454 SONET, or ONS 15454 SDH NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Network tab.
Step 3 Click the RIP subtab.
Step 4 Complete the following:
•RIP Active—Check to enable RIP.
•RIP Type—Select the RIP version from the pull-down menu.
•Metric—Set to a number between 1 and 15. This represents the number of hops.
•Authentication Type—By default, RIP is set to No Authentication. If the router that the NE is connected to requires authentication, set this to Simple Password.
•Authentication Key—If the Authentication Type is set to Simple Password, enter the password.
•Confirm Authentication Key—Enter the same password to confirm it.
Step 5 If you want to create an address summary, complete the following steps:
a. Click Create. Complete the address summary only if the NE is a gateway network element (GNE) with multiple end NEs attached and IP addresses in different subnets.
b. In the Create RIP Address Summary dialog box that opens, create aggregate addresses, which will be represented in the routing table by a summary address. Table 5-5 provides descriptions. The NEs use the IP summary address for RIP to advertise a summarized local IP address pool on the NE so that the address pool can be provided to clients.
c. After making your selections, click OK. The RIP address information is displayed in the RIP Address Summary table.
Step 6 If you want to delete a RIP address, complete the following steps:
a. Select the RIP address from the RIP Address Summary table and click Delete.
b. Click Yes in the confirmation dialog box.
Step 7 Click Apply.
Note Both the OSPF and RIP tabs are enabled if no routing advertisement is enabled. If either OSPF or RIP is enabled, the other routing protocol is disabled.
Table 5-5 Field Descriptions for the Create RIP Address Summary Dialog Box
Field
|
Description
|
Summary Address
|
Specify the IP address of the RIP summary.
|
Mask Length
|
Enter the subnet mask length.
|
Mask Address
|
(Read-only) View the subnet mask address.
|
Cost
|
Enter the hop count metric (the number of hops between the NE and the destination). The valid range is 1 to 15. The smaller the number of hops, the higher the priority.
|
5.3.5.1 Viewing the RIP Routing Table
Step 1 In the Domain Explorer tree, select an ONS 15310 CL, ONS 15310 MA, ONS 15327, ONS 15454 SONET, or ONS 15454 SDH NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Network tab.
Step 3 Click the RIP Routing Table subtab. The RIP Routing table is displayed with the following information:
•Destination—(Read-only) Displays the IP address of the destination network or host.
•Mask—(Read-only) Displays the subnet mask used to reach the destination host or network.
•Gateway—(Read-only) Displays the IP address of the gateway used to reach the destination network or host.
•Cost—(Read-only) Displays the hop count metric. The valid range is 1 to 15.
5.3.6 Creating and Modifying an SDCC, LDCC, or GCC Termination on Transponder Cards
Step 1 In the Domain Explorer tree, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane of the NE Explorer, click one of the following tabs. Tabs shown depend on the type of NE selected.
•DCC
DCC (Data Communications Channel) carries provisioning and maintenance data/information between network elements in the SONET overhead.
•DCC/GCC/OSC
GCC (General Communications Channel) is used for transponders and muxponders in dense wavelength division multiplexing (DWDM) applications.
Optical Service Channel (OSC) is a bidirectional channel that connects two adjacent nodes in a DWDM ring
•LDCC
LDCC (Line Data Communications Channel or Line DCC) is a 576-kbps data communications channel embedded in the section overhead for OAM&P traffic between two NEs.
•SDCC
SDCC (Section Data Communications Channel or Section DCC) is a 192-kbps data communications channel embedded in the section overhead for OAM&P traffic between two NEs.
Step 3 Click the subtab that corresponds to the termination that you want to create or modify. For example, to create or modify an LDCC termination, click the LDCC subtab.
Step 4 Complete one of the following options, depending on whether you want to create a new termination or modify an existing one:
•Click the Create button above the Transponder area. The Create <SDCC, LDCC, GCC, or OSC> dialog box opens and allows you to create new terminations on transponder cards. Table 5-6 provides descriptions.
Note The fields shown in the Create <SDCC, LDCC, GCC, or OSC> dialog box depend on the type of termination that is being created. The fields shown also depend on the NE type.
•Select an existing termination and click the Edit button above the Transponder area. The Edit <SDCC, LDCC, GCC, or OSC> dialog box opens and allows you to modify existing terminations on transponder cards. The following table provides descriptions.
Note The fields shown in the Edit <SDCC, LDCC, GCC, or OSC> dialog box depend on the type of termination that is being modified. The fields shown also depend on the NE type.
Step 5 After making your selections, click OK.
Table 5-6 Field Descriptions for the Create or Modify <SDCC, LDCC, GCC, or OSC> Dialog Box
Tab
|
Description
|
SDCC/LDCC Info
|
(Available for SDCC and LDCC termination.) Displays the slot and port number of the SDCC or LDCC termination.
|
OSPF Disabled on Link
|
Indicates whether Open Shortest Path First (OSPF) is disabled on the link. OSPF should be disabled only when the slot and port connect to third-party equipment that does not support OSPF.
|
Foreign
|
If checked, it means that the far-end node is a non-ONS node.
|
Admin State
|
Indicates the SDCC or LDCC port state. Select one of the following:
Note Admin state options that appear in the drop-down list depend on the NE type.
•Leave Unchanged
•IS
•OOS DSBLD
•OOS MT
•IS AINS
•unlocked
•locked, disabled
•locked, maintenance
•unlocked, automaticInService
|
Layer3/Layer 2 Config
|
Layer3 (Layer2) Config
|
Select one of the following:
•OSI (LAPD)—When selected, all fields in the OSI Subnet and LAPD areas are enabled. The Layer 3 protocol used for the DCC is OSI (IP not applicable); the Layer 2 protocol is LAPD. The OSI (LAPD) option applies only to SDCC and is disabled for all other DCC types.
•IP (PPP)—When selected, all fields in the OSI Subnet and LAPD areas are disabled. The Layer 3 protocol used for the DCC is IP only; the Layer 2 protocol is PPP.
•OSI and IP (PPP)—When selected, only the fields in the OSI Subnet area are enabled. The Layer 3 protocol includes both OSI and IP, but the Layer 2 protocol remains as PPP.
Note When editing an existing DCC, you can toggle between the IP (PPP) and OSI and IP (PPP) options if either option exists on the DCC.
Note If the DCC is configured as OSI (LAPD), you cannot modify the Layer 3/Layer 2 configuration.
|
OSI Subnet
|
Router Number
|
The OSI virtual router where the subnet (SDCC or LDCC) is provisioned.
|
IS-IS Cost
|
Sets the cost for sending packets on the subnet. This is used by OSPF routers to calculate the shortest path.
|
ISH
|
Sets the Intermediate System Hello (ISH) protocol data unit (PDU) propagation frequency. Intermediate system NEs send ISHs to other ESs and ISs to inform them about the NETs they serve. The Cisco default is 10 seconds. The range is from 10 to 1000 seconds.
|
ESH
|
Sets the End System Hello (ESH) propagation frequency. End system NEs transmit ESHs to inform other ESs and ISs about the NSAPs they serve. The Cisco default is 10 seconds. The range is from 10 to 1000 seconds.
|
IIH
|
Sets the Intermediate System to Intermediate System Hello PDU propagation frequency. The IS-IS Hello PDUs establish and maintain adjacencies between ISs. The Cisco default is 3 seconds. The range is from 1 to 600 seconds.
|
LAPD
|
Acknowledgement
|
Indicates the Link Access Protocol on the D channel (LAPD) acknowledgement type. Select either:
•Acknowledged Information Transfer Service (AITS)
•Unacknowledged Information Transfer Service (UITS)
|
T200
|
Shows the time between Set Asynchronous Balanced Mode (SABM) frame transmissions. The range is from 0.2 to 20 seconds.
|
T203
|
Shows the maximum time between LAPD frame exchanges. The range is from 4 to 120 seconds.
|
Mode
|
Indicates the LAPD frame command/response role. Values are:
•Network
•User
|
MTU
|
Sets the maximum transfer unit (MTU).
|
5.3.7 Creating and Modifying an SDCC, LDCC, GCC, or OSC Termination on SONET or SDH Cards
Step 1 In the Domain Explorer tree, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane of the NE Explorer, click one of the following tabs. Tabs shown depend on the type of NE selected.
•DCC
DCC (Data Communications Channel) carries provisioning and maintenance data/information between network elements in the SONET overhead.
•DCC/GCC/OSC
GCC (General Communications Channel) is used for transponders and muxponders in dense wavelength division multiplexing (DWDM) applications.
Optical Service Channel (OSC) is a bidirectional channel that connects two adjacent nodes in a DWDM ring
•LDCC
LDCC (Line Data Communications Channel or Line DCC) is a 576-kbps data communications channel embedded in the section overhead for OAM&P traffic between two NEs.
•SDCC
SDCC (Section Data Communications Channel or Section DCC) is a 192-kbps data communications channel embedded in the section overhead for OAM&P traffic between two NEs.
Step 3 Click the subtab that corresponds to the termination that you want to create or modify. For example, to create or modify an LDCC termination, click the LDCC subtab.
Step 4 Complete one of the following options, depending on whether you want to create a new termination or modify an existing one:
•Click the Create button above the SONET/SDH area. The Create <SDCC, LDCC, GCC, or OSC> dialog box opens and allows you to create new terminations on SONET or SDH cards. Table 5-7 provides descriptions.
Note The fields shown in the Create <SDCC, LDCC, GCC, or OSC> dialog box depend on the type of termination that is being created. The fields shown also depend on the NE type.
•Select an existing termination and click the Edit button above the SONET/SDH area. The Edit <SDCC, LDCC, GCC, or OSC> dialog box opens and allows you to modify existing terminations on SONET or SDH cards. Table 5-7 provides descriptions.
Note The fields shown in the Edit <SDCC, LDCC, GCC, or OSC> dialog box depend on the type of termination that is being modified. The fields shown also depend on the NE type.
Step 5 After making your selections, click OK.
Table 5-7 Field Descriptions for the Create or Edit <SDCC, LDCC, GCC, or OSC> Dialog Box
Field
|
Description
|
SDCC/LDCC Info
|
(Available for SDCC and LDCC termination.) Displays the slot and port number of the SDCC or LDCC termination.
|
GCC Terminations
|
(Available for GCC termination.) Displays the slot and port number of the GCC termination.
|
OSC Terminations
|
(Available for OSC termination.) Displays the slot and port number of the OSC termination.
|
OSPF Disabled on Link
|
Indicates whether Open Shortest Path First (OSPF) is disabled on the link. OSPF should be disabled only when the slot and port connect to third-party equipment that does not support OSPF.
|
Foreign
|
If checked, it means that the far-end node is a non-ONS node.
|
Admin State
|
Indicates the SDCC or LDCC port state. Select one of the following:
Note Admin state options that appear in the drop-down list depend on the NE type.
•Leave Unchanged
•IS
•OOS DSBLD
•OOS MT
•IS AINS
•unlocked
•locked, disabled
•locked, maintenance
•unlocked, automaticInService
|
GCC Rate
|
(Available for GCC termination.) Select the GCC rate.
|
Layer3/Layer 2 Config
|
Layer3 (Layer2) Config
|
Select one of the following:
•OSI (LAPD)—When selected, all fields in the OSI Subnet and LAPD areas are enabled. The Layer 3 protocol used for the DCC is OSI (IP not applicable); the Layer 2 protocol is LAPD. The OSI (LAPD) option applies only to SDCC and is disabled for all other DCC types.
•IP (PPP)—When selected, all fields in the OSI Subnet and LAPD areas are disabled. The Layer 3 protocol used for the DCC is IP only; the Layer 2 protocol is PPP.
•OSI and IP (PPP)—When selected, only the fields in the OSI Subnet area are enabled. The Layer 3 protocol includes both OSI and IP, but the Layer 2 protocol remains as PPP.
Note When editing an existing DCC, you can toggle between the IP (PPP) and OSI and IP (PPP) options if either option exists on the DCC.
Note If the DCC is configured as OSI (LAPD), you cannot modify the Layer 3/Layer 2 configuration.
|
OSI Subnet
|
Router Number
|
The OSI virtual router where the subnet (SDCC, LDCC, GCC, or OSC) is provisioned.
|
IS-IS Cost
|
Sets the cost for sending packets on the subnet. This is used by OSPF routers to calculate the shortest path.
|
ISH
|
Sets the Intermediate System Hello (ISH) protocol data unit (PDU) propagation frequency. Intermediate system NEs send ISHs to other ESs and ISs to inform them about the NETs they serve. The Cisco default is 10 seconds. The range is from 10 to 1000 seconds.
|
ESH
|
Sets the End System Hello (ESH) propagation frequency. End system NEs transmit ESHs to inform other ESs and ISs about the NSAPs they serve. The Cisco default is 10 seconds. The range is from 10 to 1000 seconds.
|
IIH
|
Sets the Intermediate System to Intermediate System Hello PDU propagation frequency. The IS-IS Hello PDUs establish and maintain adjacencies between ISs. The Cisco default is 3 seconds. The range is from 1 to 600 seconds.
|
LAPD
|
Acknowledgement
|
Indicates the Link Access Protocol on the D channel (LAPD) acknowledgement type. Select either:
•Acknowledged Information Transfer Service (AITS)
•Unacknowledged Information Transfer Service (UITS)
|
T200
|
Shows the time between Set Asynchronous Balanced Mode (SABM) frame transmissions. The range is from 0.2 to 20 seconds.
|
T203
|
Shows the maximum time between LAPD frame exchanges. The range is from 4 to 120 seconds.
|
Mode
|
Indicates the LAPD frame command/response role. Values are:
•Network
•User
|
MTU
|
Sets the maximum transfer unit (MTU).
|
5.3.8 Creating a DCC Tunnel Connection
The Create DCC Tunnel Connection dialog box allows you to create new DCC tunnel connections for the ONS 15454 SONET R3.3 and earlier.
Step 1 In the Domain Explorer tree, select the R3.3 or earlier ONS 15454 SONET NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane of the NE Explorer, click the DCC/GCC/OSC tab.
Step 3 Click the DCC Tunnel Connection subtab.
Step 4 Click Create. The Create dialog box opens. The following table provides descriptions.
Step 5 After making your selections, click OK.
Table 5-8 Field Descriptions for the Create DCC Tunnel Connection Dialog Box
Field
|
Description
|
From A
|
Select a beginning interface for the DCC tunnel.
|
From B
|
Select an ending interface for the DCC tunnel.
|
5.3.9 Using SNMP
5.3.9.1 Changing the SNMP Community String—CTC-Based NEs
Use the SNMP Trap Destination dialog box in CTC to provision community names for all SNMP requests (for example, get, next, bulk, and set) for CTC-based NEs R3.3 and later. Any SNMP request that uses a community name that matches a community name in the list of provisioned SNMP trap destinations is considered valid.
If an SNMP request contains an invalid community name (one that does not match a provisioned community name), the request is dropped silently. The MIB variable snmpInBadCommunityNames increments, and an authenticationFailure trap is sent.
Due to security concerns, the community names public and private do not have the special meaning that they have in most SNMP interfaces.
5.3.9.2 Configuring SNMP for CTC-Based NEs
Step 1 Select a CTC-based NE in the Domain Explorer tree and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Network tab; then, click the SNMP subtab.
Step 3 (Not applicable to the ONS 15600) To allow SNMP proxy, check the Allow SNMP Proxy check box.
Step 4 (Not applicable to the ONS 15600) To use the SNMP management software with the NE, check the Allow SNMP Set check box.
Step 5 (Not applicable to the ONS 15600) Click Apply.
Step 6 Click Create. The Create SNMP Trap Destination dialog box opens. The following table provides descriptions.
Step 7 After making your selections, click OK.
Step 8 Click Apply.
Table 5-9 Field Descriptions for the Create SNMP Trap Destination Dialog Box
Field
|
Description
|
IP Address
|
Enter the IP address of your NMS.
|
Community Name
|
Enter the SNMP community name. For a description of SNMP community names, refer to the SNMP information in the NE reference guide.
Note The community name is a form of authentication and access control. The community name assigned to the ONS 15600 is case-sensitive and must match the community name of the NMS.
|
UDP Port
|
Set the UDP port for SNMP. The Cisco default port is 162. Allowed UDP port values are 162, 391, and values between 1024 and 65535.
|
Trap Version
|
Set the Trap Version field for either SNMPv1 or SNMPv2. See your NMS documentation to determine whether to use SNMPv1 or SNMPv2.
|
Max Traps per Second (not applicable to the ONS 15600)
|
Enter the maximum number of traps per second that will be sent to the SNMP manager. A zero value indicates that there is no maximum and all traps are sent to the SNMP manager.
|
5.3.9.3 Creating an SNMP Community—ONS 15216 EDFA2
The Create SNMP Community View dialog box allows you to create an SNMP community for the ONS 15216 EDFA2.
Note SNMP views are supported only for the EDFA2 R2.4.0 and later. The SNMP tab is not present in the EDFA2 R2.1.1 and R2.3.0.
Step 1 In the Domain Explorer, select an ONS 15216 EDFA2 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click the SNMP Community Table subtab.
Step 4 Click Create. The Create SNMP Community View dialog box opens. The following table provides descriptions.
Table 5-10 Field Descriptions for the Create SNMP Community View Dialog Box
Field
|
Description
|
Community Name
|
Enter the SNMP community name.
|
Privileges
|
Enter the access privileges that govern what management operations a particular community can perform. These privileges are expressed as a sum of values, where each value represents a particular operation. See Table 5-11 for the SNMP operation decimal values.
|
IP Address
|
Enter the IP address from which network management traffic for the new SNMP community originates.
|
Subnet Mask
|
Enter the subnet mask for the source IP address.
|
Step 5 After making your selections, click OK in the Create SNMP Community View dialog box.
Step 6 Click Apply in the node properties pane. The new SNMP community is listed in the SNMP Community table.
The following table displays the decimal values for the different SNMP operations. For example, 255 is the sum of all decimal values and specifies access to all SNMP operations. This sum is the default private community. 247 is the sum for all SNMP operations with the exception of the Set operation. This sum is the default public community.
Table 5-11 SNMP Operation Decimal Values
SNMP Operation
|
Decimal Values
|
Get
|
1
|
GetNext
|
2
|
Response (enable for all community strings)
|
4
|
Set
|
8
|
SNMPv1-Trap
|
16
|
GetBulk
|
32
|
Inform (enable for all community strings)
|
64
|
SNMPv2-Trap (enable for all community strings)
|
128
|
5.3.9.4 Modifying an SNMP Community—ONS 15216 EDFA2
Step 1 In the Domain Explorer, select an ONS 15216 EDFA2 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click the SNMP Community Table subtab.
Step 4 In the SNMP Community table, select the SNMP community to modify.
Step 5 Double-click a specific field and modify the following:
•Community Name—New community string.
•View Index—New index number.
•Privilege—New access privilege that governs what management operations a particular community can perform. These privileges are expressed as a sum of values, where each value represents a particular operation. See Table 5-11 for the SNMP operation decimal values.
•IP Address—New IP address from which network management traffic for the new SNMP community originates.
•Subnet Mask—New subnet mask for the source IP address.
•Status—Read-only.
Step 6 Click Apply.
5.3.9.5 Deleting an SNMP Community—ONS 15216 EDFA2
Step 1 In the Domain Explorer, select an ONS 15216 EDFA2 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click the SNMP Community Table subtab.
Step 4 In the SNMP Community table, select an SNMP community to delete.
Step 5 Click Delete; then, click OK.
Step 6 Click Apply.
5.3.9.6 Creating an SNMP Trap Destination—ONS 15216 EDFA2
Step 1 In the Domain Explorer, select an ONS 15216 EDFA2 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click the Trap Destination Table subtab.
Step 4 Click Create. The Create Trap Destination dialog box opens. The following table provides descriptions.
Step 5 After making your selections, click OK.
Step 6 Click Apply in the node properties pane. The new SNMP trap destination is listed in the Trap Destination table.
Table 5-12 Field Descriptions for the Create Trap Destination Dialog Box
Field
|
Description
|
IP Address
|
Type the SNMP trap destination IP address.
|
UDP Port
|
Set the trap destination User Datagram Protocol (UDP) port for SNMP.
|
Community Name
|
Type the SNMP community name.
|
Version
|
Enter the trap version number.
|
5.3.9.7 Modifying an SNMP Trap Destination—ONS 15216 EDFA2
Step 1 In the Domain Explorer, select an ONS 15216 EDFA2 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click the Trap Destination Table subtab.
Step 4 In the Trap Destination table, select the SNMP trap destination to modify.
Step 5 Double-click a specific field and modify the following:
•IP Address—IP address of the SNMP trap destination.
•UDP Port—UDP port number of the SNMP trap destination.
•Community Name—SNMP trap destination community string name.
•Version—Select the version from the pull-down menu.
•View Index—New index number.
•Status—Read-only.
Step 6 Click Apply.
5.3.9.8 Deleting an SNMP Trap Destination—ONS 15216 EDFA2
Step 1 In the Domain Explorer, select an ONS 15216 EDFA2 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click the Trap Destination Table subtab.
Step 4 In the Trap Destination table, select an SNMP trap destination to delete.
Step 5 Click Delete; then, click OK.
Step 6 Click Apply.
5.3.9.9 Creating an SNMP View—ONS 15216 EDFA2
Step 1 In the Domain Explorer, select an ONS 15216 EDFA2 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click the SNMP Views subtab.
Step 4 Click Create. The Create SNMP View dialog box opens. The following table provides descriptions.
Step 5 After making your selections, click OK.
Step 6 Click Apply in the node properties pane. The new SNMP view is listed in the SNMP Views table.
Table 5-13 Field Descriptions for the Create SNMP View Dialog Box
Field
|
Description
|
View Index
|
Enter the view index number, which is a unique value for each MIB view.
|
Subtree
|
Enter an object identifier that designates a subtree element in the MIB hierarchy.
|
Mask
|
Enter the bit mask that identifies objects in the subtree.
|
Type
|
From the pull-down menu, select the flag that specifies the status of the view. Values are included and excluded.
|
5.3.9.10 Modifying an SNMP View—ONS 15216 EDFA2
Step 1 In the Domain Explorer, select an ONS 15216 EDFA2 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click the SNMP Views subtab.
Step 4 In the SNMP Views table, select the SNMP view to modify.
Step 5 Double-click a specific field and modify the following:
•View Index—Read-only.
•Subtree—Read-only.
•Mask—Modify the bit mask that identifies objects in the subtree.
•Type—From the pull-down menu, select the flag that specifies the status of the view.
•Status—Read-only.
Step 6 Click Apply.
5.3.9.11 Deleting an SNMP View—ONS 15216 EDFA2
Step 1 In the Domain Explorer, select an ONS 15216 EDFA2 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click the SNMP Views subtab.
Step 4 In the SNMP Views table, select an SNMP view to delete.
Step 5 Click Delete; then, click OK.
Step 6 Click Apply.
5.3.9.12 Creating an SNMP Trap Destination—ONS 15216 EDFA3
Step 1 In the Domain Explorer, select an ONS 15216 EDFA3 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click Add Row. The Create Trap Destination table opens. Table 5-14 provides descriptions.
Step 4 After making your selections, click OK.
Step 5 Click Apply in the node properties pane. The new SNMP trap destination is listed in the Trap Destination table.
Note A maximum of 10 SNMP hosts can be configured for the EDFA3. (The EDFA2 has no such restriction.)
Table 5-14 Field Descriptions for the Trap Destination Table Subtab
Field
|
Description
|
IP Address
|
Enter the trap destination IP address.
|
UDP Port
|
Set the trap destination UDP port for SNMP.
|
Community Name
|
Enter the SNMP trap destination community string name.
|
Version
|
Enter the trap version number.
|
5.3.9.13 Modifying an SNMP Trap Destination—ONS 15216 EDFA3
Step 1 In the Domain Explorer, select an ONS 15216 EDFA3 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click the Trap Destination Table subtab.
Step 4 In the Trap Destination table, select the SNMP trap destination to modify.
Step 5 Double-click a specific field and modify the following:
•IP Address—IP address of the SNMP trap destination.
•UDP Port—UDP port number of the SNMP trap destination.
•Community Name—SNMP trap destination community string name.
•Version—Select the version from the pull-down menu.
Step 6 Click Apply.
5.3.9.14 Deleting an SNMP Trap Destination—ONS 15216 EDFA3
Step 1 In the Domain Explorer, select an ONS 15216 EDFA3 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click the Trap Destination Table subtab.
Step 4 In the Trap Destination table, select an SNMP trap destination to delete; then, click Delete Row.
Step 5 Click Apply.
5.3.10 Specifying the Preferred Copy—ONS 15600 SONET or ONS 15600 SDH
Step 1 In the Domain Explorer tree, select the ONS 15600 SONET or ONS 15600 SDH NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Maintenance tab.
Step 3 In the Preferred Copy subtab > Data Copy area, select the preferred data from the Preferred Data pull-down list.
Step 4 Click Apply.
5.3.11 Enabling Intermediate Path Performance Monitoring
Most CTC-based networks use line-terminating equipment (LTE) to enable intermediate path performance monitoring (IPPM). IPPM allows you to transparently monitor a transmission signal originating from any equipment without terminating the channel of that signal. To use IPPM, create the STS circuit on the DS-N cards; then, enable IPPM on the EC1-12 or OC-N cards that carry the circuit.
Note IPPM occurs only on STS paths that have IPPM enabled; threshold crossing alerts (TCAs) are raised only for PM parameters on the IPPM-enabled paths. The monitored IPPM parameters are STS CV-P, STS ES-P, STS SES-P, STS UAS-P, and STS FC-P.
Step 1 In the Domain Explorer, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 Select an LTE card. The following table lists the LTE cards.
Table 5-15 Traffic Cards that Terminate the Line (LTE Cards)
NE
|
Line-Terminating Equipment
|
ONS 15327
|
XTC-14
|
XTC-28-3
|
OC3 IR4 1310
|
OC12 IR 1310
|
OC12 LR 1550
|
OC48 IR 1310
|
OC48 LR 1550
|
—
|
ONS 15454 SONET
|
Electrical LTE
|
EC1-12
|
DS1-14
|
DS1N-14
|
DS3-12
|
DS3N-12
|
DS3-12E
|
DS3N-12E
|
DS3XM-6
|
DS3i/DS3iN
|
—
|
Optical LTE
|
OC3 IR 4/STM1 SH 1310
|
OC3 IR/STM1 SH 1310-8
|
OC12 IR/STM4 SH 1310
|
OC12 LR/STM4 LH 1310
|
OC12 LR/STM4 LH 1550
|
OC12 IR/STM4 SH 1310-4
|
OC48 IR 1310
|
OC48 LR 1550
|
OC48 IR/STM16 SH AS 1310
|
OC48 LR/STM16 LH AS 1550
|
OC48 ELR/STM16 EH 100 GHz
|
OC48 ELR 200 GHz
|
OC192 SR/STM64 IO 1310
|
OC192 IR/STM64 SH 1550
|
OC192 LR/STM64 LH 1550
|
OC192 LR/STM64 LH ITU 15xx.xx
|
TXP_MR_10G
|
MXP_2.5G_10G
|
ONS 15454 SDH
|
Electrical LTE
|
E1-N-14
|
E1-42
|
E3-12
|
DS3i-N-12
|
STM1E-12
|
—
|
Optical LTE
|
OC3 IR 4/STM1 SH 1310
|
OC3 IR/STM1 SH 1310-8
|
OC12 IR/STM4 SH 1310
|
OC12 LR/STM4 LH 1310
|
OC12 LR/STM4 LH 1550
|
OC12 IR/STM4 SH 1310-4
|
OC48 IR/STM16 SH AS 1310
|
OC48 LR/STM16 LH AS 1550
|
OC48 ELR/STM16 EH 100 GHz
|
OC192 SR/STM64 IO 1310
|
OC192 IR/STM64 SH 1550
|
OC192 LR/STM64 LH 1550
|
OC192 LR/STM64 LH ITU 15xx.xx
|
—
|
ONS 15600
|
OC48/STM16 LR/LH 16 Port 1550
|
OC192/STM64 LR/LH 4 Port 1550
|
Step 3 Click the STS tab.
Step 4 Click the STS Config subtab.
Step 5 Check the IPPM Enabled check box.
Step 6 Click Apply.
5.3.12 Enabling Pointer Justification Count Monitoring for CTC-Based NEs
Note Pointer justification count monitoring is not available for the ONS 15600 SONET and ONS 15600 SDH NEs.
Pointers are used in CTC-based NEs to compensate for frequency and phase variations. They provide a way to align the phase variations in STS and VT payloads. Pointer justification counts indicate timing differences on SONET networks.
There are positive pointer justification count (PPJC) and negative pointer justification count (NPJC) parameters. PPJC is a count of path-detected (PPJC-Pdet) or path-generated (PPJC-Pgen) positive pointer justifications. NPJC is a count of path-detected (NPJC-Pdet) or path-generated (NPJC-Pgen) negative pointer justifications depending on the specific PM name.
A consistent pointer justification count indicates clock synchronization problems between nodes. A difference between the counts means the node transmitting the original pointer justification has timing variations with the node detecting and transmitting this count. Positive pointer adjustments occur when the frame rate of the synchronous payload envelope (SPE) is too slow in relation to the rate of the STS-1.
To enable performance monitoring of the pointer justification count:
Step 1 In the Domain Explorer, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 Select an LTE card. See Table 5-15 for a list of LTE cards.
Step 3 Click the Line tab.
Step 4 Click the Line Config subtab.
Step 5 Double-click the PJStsMon# field and select a number:
•The value Off means pointer justification monitoring is disabled.
•The values 1 to n are the STS numbers on one port. One STS per port can be enabled from the PJStsMon# menu, as follows:
–EC1-12 PJStsMon# card field: 0 or 1 can be selected on a total of 12 ports.
–OC-3 PJStsMon# card field: 1, 2, or 3 can be selected on a total of 4 ports.
–OC-12 PJStsMon# card field: Between 1 and 12 can be selected on 1 port.
–OC-48 PJStsMon# card field: Between 1 and 48 can be selected on 1 port.
–OC-192 PJStsMon# card field: Between 1 and 192 can be selected on 1 port.
Step 6 Click Apply.
5.3.13 Changing the Power Monitoring Threshold for the ONS 15454 SONET and ONS 15454 SDH
Step 1 In the Domain Explorer tree, select an ONS 154545 SONET or ONS 15454 SDH NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Identification tab.
Step 3 In the Voltage Thresholds area, select the threshold for the following:
•ELWBATVG—Very low battery voltage.
•LWBATVG—Low battery voltage. Available on ONS 15454 SONET only.
•HIBATVG—High battery voltage. Available on ONS 15454 SONET only.
•EHIBATVG—Very high battery voltage.
•Current Voltage Environment—Read-only.
Note You can set thresholds in 0.5 VDC increments.
Step 4 Click Apply.
5.3.14 Creating an Ethernet Threshold
The Create Ethernet Threshold dialog box allows you to create new Ethernet thresholds for the G1000-2, G1000-4, ETH100, ETH1000, and ML-series cards for ONS 15327, ONS 15454 SONET, and ONS 15454 SDH NEs.
Step 1 In the Domain Explorer, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the NE Explorer tree, select an Ethernet card.
Step 3 Click the Thresholds tab.
Step 4 Click Create. The Create Ether Thresholds dialog box opens. The following table provides descriptions.
Step 5 After making your selections, click OK.
Step 6 Click Apply.
Table 5-16 Field Descriptions for the Create Ethernet Thresholds Dialog Box
Field
|
Description
|
Slot
|
Select a slot for the new Ethernet threshold.
|
Port
|
Select a port for the selected slot. If you select All, the threshold is created on all ports for that slot. This operation might take several minutes to complete.
|
Variable
|
Select a variable for the new Ethernet threshold. The list of variables differs based on the type of card that is installed in the slot selected in the Slot field.
|
Alarm Type
|
Select an alarm type for the new Ethernet threshold. Available alarm types are Rising, Falling, and Rising and Falling.
|
Sample Type
|
Select a sample type for the new Ethernet threshold. Available sample types are Relative and Absolute.
|
Sample Period
|
Enter a sample period for the new Ethernet threshold. The sample period is measured in seconds.
|
Rising Threshold
|
Enter a rising threshold for the new Ethernet threshold. The value must be equal to or greater than the Falling Threshold value.
|
Falling Threshold
|
Enter a falling threshold for the new Ethernet threshold. The value must be equal to or less than the Rising Threshold value.
|
5.4 Synchronizing the Network for Optical Devices
Use the NE Explorer to synchronize the CTC-based NEs in your network. The following sections describe the synchronization settings in detail.
5.4.1 Synchronization Settings for the ONS 15310 CL, ONS 15310 MA, ONS 15327, ONS 15454 SONET, and ONS 15600 SONET
Full Cisco IOS configuration synchronization is performed automatically by CTM to keep the NE and the CTM Data Provisioning Service synchronized. Full configuration resynchronization might be delayed depending on the usage of the CTM server.
For more information, see Chapter 7, "Provisioning Services and Connections."
Synchronization status messaging (SSM) is a SONET protocol that communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SONET Line layer. These messages enable SONET devices to automatically select the highest quality timing reference and to avoid timing loops.
SSM messages are either Generation 1 or Generation 2. Generation 1 is the first and most widely deployed SSM message set. Generation 2 is a newer version. If SSM is enabled, consult the timing reference documentation to determine which message set to use. The following tables show the Generation 1 and Generation 2 message sets.
Table 5-17 SSM Generation 1 Message Set
Message
|
Quality
|
Description
|
PRS
|
1
|
Primary reference source—Stratum 1
|
STU
|
2
|
Synchronization traceability unknown
|
ST2
|
3
|
Stratum 2
|
ST3
|
4
|
Stratum 3
|
SMC
|
5
|
SONET minimum clock
|
ST4
|
6
|
Stratum 4
|
DUS
|
7
|
Do not use for timing synchronization
|
RES
|
—
|
Reserved; quality level set by user
|
Table 5-18 SSM Generation 2 Message Set
Message
|
Quality
|
Description
|
PRS
|
1
|
Primary reference source—Stratum 1
|
STU
|
2
|
Sync traceability unknown
|
ST2
|
3
|
Stratum 2
|
TNC
|
4
|
Transit node clock
|
ST3E
|
5
|
Stratum 3E
|
ST3
|
6
|
Stratum 3
|
SMC
|
7
|
SONET minimum clock
|
ST4
|
8
|
Stratum 4
|
DUS
|
9
|
Do not use for timing synchronization
|
RES
|
—
|
Reserved; quality level set by user
|
Note Alarms relating to PM collection indicate that the load on the system is high. Reduce the load on the system before proceeding.
5.4.1.1 Setting Up External or Line Timing for CTC-Based SONET NEs
Step 1 Select an ONS 15310 CL, ONS 15310 MA, ONS 15327, ONS 15454 SONET, or ONS 15600 SONET NE and choose Configuration > NE Explorer.
Step 2 In the node property pane, click the Timing tab. Fields shown depend on the NE that is selected.
Step 3 In the General Timing section of the General subtab, complete the following information:
•Timing Mode—Set to External if the NE derives its timing from a building integrated timing supply (BITS) source wired to the backplane pins; set to Line if timing is derived from an OC-N card that is optically connected to the timing node. A third option, Mixed, allows users to set external and line timing references.
Caution Because mixed timing can cause timing loops, Cisco does not recommend its use. Use this mode with care.
Note The Mixed option is not applicable to the ONS 15600 SONET.
•SSM Message Set—Choose the message set level supported by the network. If a Generation 1 node receives a Generation 2 message, the message will be mapped down to the next available Generation 1. For example, an ST3E message becomes an ST3.
•Revertive—If checked, the NE reverts to a primary reference source after the conditions that caused it to switch to a secondary timing reference are corrected.
•Reversion Time—If Revertive is checked, indicate the amount of time that the NE will wait before reverting back to its primary timing source.
•Quality of RES—If the timing source supports the reserved S1 byte, set the timing quality here. (Most timing sources do not use RES.) Qualities are displayed in descending quality order as ranges. For example, ST3 < RES < ST2 means the timing reference is higher than a Stratum 3 and lower than a Stratum 2.
Step 4 In the BITS Facilities section of the General subtab, complete the following information:
Note The BITS Facilities section sets the parameters for BITS1 and BITS2 timing references. Many of these settings are determined by the timing source manufacturer. If the equipment is timed through BITS Out, set the timing parameters to meet the requirements of the equipment.
•In State—If Timing Mode is set to External or Mixed, set the In State for BITS 1 and/or BITS 2 to IS (In Service) depending on whether one or both BITS input pin pairs on the backplane are connected to the external timing source. If Timing Mode is set to Line, set the In State to OOS (Out of Service).
•Out State—If equipment is connected to the node's BITS output pins on the backplane and you want to time the equipment from a node reference, set the Out State for BITS 1 and/or BITS 2 to IS, depending on which BITS output pins are used for external equipment. If equipment is not attached to the BITS output pins, set the Out State to OOS.
•Coding—Set to the coding used by the BITS reference, either B8ZS (binary 8-zero substitution) or AMI (alternate mark inversion).
•Framing—Set to the framing used by the BITS reference, either ESF (Extended Superframe) or SF(D4) (Super Frame). SSM is not available with Super Frame.
•Sync Messaging—Check to enable SSM.
•AIS Threshold (Not applicable to the ONS 15600 SONET)—Sets the quality level where a node sends an alarm indication signal (AIS) from the BITS 1 Out and BITS 2 Out backplane pins. When a node times at or below the AIS threshold quality, an AIS is sent. This is used when SSM is disabled or when the frame is SF.
•LBO (Not applicable to the ONS 15600 SONET)—If you are timing an external device connected to the BITS Out pins, set the distance between the device and the NE. Options are 0-133 ft. (Cisco default), 134-266 ft., 267-399 ft., 400-533 ft., and 534-655 ft.
Step 5 In the Reference List subtab, complete the following information:
Note Reference lists define up to three timing references for the node and up to six BITS Out references. BITS Out references define the timing references used by equipment that can be attached to the node BITS Out pins on the backplane. If you attach equipment to BITS Out pins, you normally attach it to a node with Line mode because equipment near the External timing reference can be directly wired to the reference.
•NE References—Define up to three timing references (Ref-1, Ref-2, Ref-3). The node uses Reference 1 unless a failure occurs to that reference, in which case the node uses Reference 2. If that fails, the node uses Reference 3, which is typically set to Internal Clock. This is the Stratum 3 clock provided on the TCC+/TCC2 card. The options displayed depend on the Timing Mode setting:
–Timing Mode set to External—Options are BITS1, BITS2, and Internal Clock.
–Timing Mode set to Line—Options are the node's working OC-N cards (non-DWDM nodes), OSC cards (DWDM nodes), and Internal Clock. Select the cards/ports that are directly or indirectly connected to the node wired to the BITS source; that is, the node's trunk (span) cards. Set Reference 1 to the trunk card that is closest to the BITS source. For example, if slot 5 is connected to the node wired to the BITS source, select slot 5 as Reference 1.
–Timing Mode set to Mixed—Both BITS and optical cards are available, which allows you to set a mixture of external BITS and OC-N trunk cards as timing references.
•BITS 1 Out/BITS 2 Out—Define the timing references for equipment wired to the BITS Out backplane pins. BITS 1 Out and BITS 2 Out are enabled when BITS 1 and BITS 2 facilities are put in service. If Timing Mode is set to external, choose the OC-N card used to set timing. If Timing Mode is set to Line, you can choose an OC-N card or choose NE reference to have BITS 1 out and/or BITS 2 Out follow the same timing reference as the NE.
Step 6 In the Status subtab, complete the following information:
•NE Clock
–NE Reference—Set the NE timing reference to internal, BITS 1, or BITS 2.
–Status—Read only. Displays the status of the NE clock.
–Operations—Execute a switch on the NE timing reference.
•BITS 1 OUT
–BITS 1 Out—Set the BITS 1 Out timing reference.
–Status—Read only. Displays the status of the BITS 1 out timing reference.
–Operations—Execute a switch on the BITS 1 out timing reference.
•BITS 2 OUT
–BITS 2 Out—Set the BITS 2 Out timing reference.
–Status—Read only. Displays the status of the BITS 2 out timing reference.
–Operations—Execute a switch on the BITS 2 out timing reference.
Step 7 In the Timing Report subtab, you can view the timing status report summary for the node.
Step 8 Click Apply.
Note Refer to the relevant ONS 15310 CL, ONS 15310 MA, ONS 15327, ONS 15454, or ONS 15600 troubleshooting guide for timing-related alarms.
5.4.1.2 Setting Up Internal Timing for CTC-Based SONET NEs
If no BITS source is available, set up internal timing by timing all nodes in the ring from the internal clock of one node.
Caution Internal timing is Stratum 3 and not intended for permanent use. All nodes should be timed to a Stratum 2 or better primary reference source.
Step 1 Select an ONS 15310 CL, ONS 15310 MA, ONS 15327, ONS 15454 SONET, or ONS 15600 SONET NE and choose Configuration > NE Explorer.
Step 2 In the node property pane, click the Timing tab. Fields shown depend on the NE that is selected.
Step 3 In the General Timing section of the General subtab, enter the following information:
•Timing Mode—Set to External.
•SSM Message Set—Set to Generation 1.
•Revertive—Not relevant for internal timing; the default setting (checked) is sufficient.
•Reversion Time—The default setting is sufficient.
•Quality of RES—Set to RES=DUS.
Step 4 In the BITS Facilities section of the General subtab, enter the following information:
•In State—Set BITS 1 and BITS 2 to OOS.
•Out State—Set BITS 1 and BITS 2 to OOS.
•Coding—Not relevant for internal timing. The default (B8ZS) is sufficient.
•Framing—Not relevant for internal timing. The default (ESF) is sufficient.
•Sync Messaging—Checked.
•AIS Threshold—Not available.
•LBO—Not relevant.
Step 5 In the Reference List subtab, enter the following information:
•NE References
–Ref-1—Set to Internal Clock.
–Ref-2—Set to Internal Clock.
–Ref-3—Set to Internal Clock.
•BITS 1 Out/BITS 2 Out—Set to None.
Step 6 Click Apply.
Step 7 In the Domain Explorer tree, select the node that will be timed from the node that was set up in Steps 1 through 6 and choose Configuration > NE Explorer.
Step 8 In the Timing tab, enter the same information that was entered in Step 3, except for the following:
•In the General Timing section of the General subtab, set the Timing Mode field to Line.
•In the NE References section of the Reference List subtab:
–Ref-1—Set to the OC-N trunk (span) card (non-DWDM node) or OSC card (DWDM) with the closest connection to the node.
–Ref-2—Set to the OC-N trunk (span) card (non-DWDM node) or OSC card (DWDM) with the next closest connection to the node.
–Ref-3—Set to Internal Clock.
Step 9 Click Apply.
Step 10 Repeat Steps 3 through 9 at each node that will be timed by the node.
5.4.2 Synchronization Settings for the ONS 15454 SDH and ONS 15600 SDH
SSM communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SDH section overhead. These messages enable SDH devices to automatically select the highest quality timing reference and to avoid timing loops.
SSM messages are either Generation 1 or Generation 2. Generation 1 is the first and most widely deployed SSM message set. Generation 2 is a newer version. If you enable SSM for the ONS 15454 SDH, consult your timing reference documentation to determine which message set to use. The following table shows the SDH message set.
Table 5-19 SDH SSM Message Set
Message
|
Quality
|
Description
|
G811
|
1
|
Primary reference clock
|
STU
|
2
|
Synchronization traceability unknown
|
G812T
|
3
|
Transit node clock traceable
|
G812L
|
4
|
Local node clock traceable
|
SETS
|
5
|
Synchronous equipment
|
DUS
|
6
|
Do not use for timing synchronization
|
Note Alarms relating to PM collection indicate that the load on the system is high. Reduce the load on the system before proceeding.
5.4.2.1 Setting Up External or Line Timing for CTC-Based SDH NEs
Step 1 Select an ONS 15454 SDH or ONS 15600 SDH NE and choose Configuration > NE Explorer.
Step 2 In the node property pane, select the Timing tab. Fields shown depend on the NE that is selected.
Step 3 In the General Timing section of the General subtab, complete the following information:
•Timing Mode
–For the ONS 15454 SDH:
Choose External if the ONS 15454 SDH NE derives its timing from an MIC-C/T/P FMEC; choose Line if timing is derived from an STM-N card (non-DWDM node) or OSC card (DWDM node) that is optically connected to the timing node. A third option, Mixed, allows you to set external and line timing references.
–For the ONS 15600 SDH:
Choose External if the ONS 15600 SDH NE derives its timing from a BITS source wired to the backplane; choose Line if timing is derived from an STM-N card that is optionally connected to the timing node. A third option, Mixed, allows you to set external and line timing references.
Caution Because mixed timing may cause timing loops, Cisco does not recommend its use. Use this mode with care.
•Revertive—If checked, the NE reverts to a primary reference source after the conditions that caused it to switch to a secondary timing reference are corrected.
•Reversion Time—If Revertive is checked, indicate the amount of time the NE will wait before reverting to its primary timing source.
•SSM Message Set (Applicable to the ONS 15600 SDH)—Enabled only if T1 signal type is selected. Choose the message set level supported by the network.
•Hold Off Time (Applicable to the ONS 15600 SDH)—If a value other than zero is provided, then this is the amount of time the ONS 15600 SDH will wait before including a previously failed timing source as available and valid.
Step 4 In the BITS Facilities section of the General subtab, complete the following information:
Note The BITS Facilities section sets the parameters for your BITS 1 and BITS 2 timing references. Many of these settings are determined by the timing source manufacturer. If equipment is timed through BITS Out, you can set timing parameters to meet the requirements of the equipment.
•E1, T1, 2.048 MHz, 64 KHz—Choose E1, T1, 2.048 MHz, or 64 KHz depending on the signal supported in your market. For example, 64 KHz is used in Japan. E1, 2.048 MHz, and 64 KHz are physical signal modes used to transmit the external clock (from a GPS, for example) to BITS.
•In State—If Timing Mode is set to External or Mixed, set the In State for BITS 1 and/or BITS 2 to IS (in service) depending whether one or both BITS input pin pairs on the backplane are connected to the external timing source. If Timing Mode is set to Line, set the In State to OOS (Out of Service)
•Out State—If equipment is connected to the node's BITS output pins on the backplane and you want to time the equipment from a node reference, set the Out State for BITS 1 and/or BITS 2 to IS (in service), depending on which BITS output pins are used for external equipment. If equipment is not attached to the BITS output pins, set the Out State to OOS (out of service).
•State (Applicable to the ONS 15600 SDH)—For nodes using external timing, set the State to IS (In Service).
•Coding—Choose the coding used by your BITS reference, either HDB3 or AMI. If you selected 2.048 MHz or 64 KHz, the coding option is disabled.
•Framing—Choose the framing used by your BITS reference, either unframed, FAS, FAS + CAS, FAS + CRC, or FAS + CAS + CRC. If you selected 2.048 MHz or 64 KHz, the framing option is disabled.
•Sync Messaging—Select the check box to enable SSM. SSM is used to deliver clock quality. The SSM supported in SDH is G811, STU, G812T, G812L, SETS, DUS (ordered from high quality to low quality). If you selected 2.048 MHz, 64 KHz, or E1 with FAS or if FAS + CAS framing is provisioned, the SSM option is disabled.
•AIS Threshold (Applicable to the ONS 15454 SDH)—Sets the quality level at which a node sends an alarm indication signal (AIS) from the BITS 1 Out and BITS 2 Out FMEC connectors. When a node times at or below the AIS threshold quality, an AIS is raised. (The AIS threshold is used when SSM is disabled or framing is set to unframed, FAS, or FAS + CAS.)
•LBO (Applicable to the ONS 15454 SDH)—Choose a BITS cable length. Line build out (LBO) relates to the BITS cable length.
•Cable Type (Applicable to the ONS 15600 SDH)—Choose 75 ohm or 120 ohm.
•Sa bit—Choose one of 5 Sa bits (4, 5, 6, 7, or 8). The Sa bit transmits the SSM message. If you selected 2.048 MHz or 64 KHz, the Sa bit option is disabled.
Step 5 In the Reference List subtab, complete the following information:
Note Reference lists define up to three timing references for the node and up to six BITS Out references. BITS Out references define the timing references used by equipment attached to the node's MIC-C/T/P FMEC Timing A Out and Timing B Out connectors. If you attach equipment to the Timing A Out or Timing B Out connector, you normally attach it to a node with line mode because equipment near the external timing reference can be directly wired to the reference.
•NE References—Allows you to define three timing references (Ref-1, Ref-2, Ref-3). The node uses Reference 1 unless a failure occurs to that reference, in which case the node uses Reference 2. If Reference 2 fails the node uses Reference 3, which is typically set to Internal Clock. The internal clock is the Stratum 3 clock provided on the TCC2. The options displayed depend on the Timing Mode setting:
–Timing Mode set to External—Options are BITS 1, BITS 2, and Internal Clock.
–Timing Mode set to Line—For the ONS 15454 SDH, options are the node's working OC-N cards (non-DWDM nodes), OSC cards (DWDM nodes), and Internal Clock. For the ONS 15600 SDH, options are the node's STM-N ports (except for the ports that have been specified as protection ports in 1+1 [LMSP] (Linear Multiplex Section protection) protection groups) and Internal Clock. Select the cards/ports that are directly or indirectly connected to the node wired to the BITS source; that is, select the node's trunk cards. Set Reference 1 to the trunk card that is closest to the BITS source. For example, if Slot 5 is connected to the node wired to the BITS source, select Slot 5 as Reference 1.
–Timing Mode set to Mixed—Both BITS and optical cards are available, allowing you to set a mixture of external BITS and optical trunk (span) cards as timing references.
•BITS 1 Out/BITS 2 Out References (Applicable to the ONS 15454 SDH)—Define the timing references for equipment connected to the Timing A Out or Timing B Out FMEC connector. Normally, Timing Out is used with line nodes, so the options displayed are the working optical cards. Timing A Out and Timing B Out are enabled as soon as BITS 1 and BITS 2 facilities are placed in service.
Step 6 In the Status subtab, complete the following information:
•NE Clock
–NE Reference—Set the NE timing reference to internal, BITS 1, or BITS 2.
–Status—Read only. Displays the status of the NE clock.
–Operations—Execute a switch on the NE timing reference.
•BITS 1 OUT
–BITS 1 Out—Set the BITS 1 out timing reference.
–Status—Read only. Displays the status of the BITS 1 out timing reference.
–Operations—Execute a switch on the BITS 1 out timing reference.
•BITS 2 OUT
–BITS 2 Out—Set the BITS 2 out timing reference.
–Status—Read only. Displays the status of the BITS 2 out timing reference.
–Operations—Execute a switch on the BITS 2 out timing reference.
Step 7 In the Timing Report subtab, you can view the timing status report summary for the node.
Step 8 Click Apply.
Note Refer to the Cisco ONS 15454 SDH Troubleshooting Guide or Cisco ONS 15600 SDH Troubleshooting Guide for timing-related alarms.
5.4.2.2 Setting Up Internal Timing for CTC-Based SDH NEs
If no BITS source is available, you can set up internal timing by timing all nodes in the ring from the internal clock of one node.
Caution Internal timing is Stratum 3 and not intended for permanent use. All nodes should be timed to a Stratum 2 or better primary reference source.
Step 1 Select an ONS 15454 SDH or ONS 15600 SDH NE and choose Configuration > NE Explorer.
Step 2 In the node property pane, select the Timing tab.
Step 3 In the General Timing section of the General subtab, enter the following information:
•Timing Mode—Choose External.
•Revertive—Not applicable for internal timing; the default setting (checked) is sufficient.
•Reversion Time—Not applicable; leave unchanged.
Step 4 In the BITS Facilities section of the General subtab, enter the following information:
•E1, T1, 2.048 MHz, 64 KHz—Choose E1, T1, 2.048 MHz, or 64 KHz depending on the signal supported in your market. For example, 64 KHz is used in Japan. E1, 2.048 MHz, and 64 KHz are physical signal modes used to transmit the external clock (from a GPS, for example) to BITS.
•In State—Set BITS 1 and BITS 2 to OOS.
•Out State—Set BITS 1 and BITS 2 to OOS.
•State (Applicable to the ONS 15600 SDH)—Set BITS 1 and BITS 2 to OOS.
•Coding—Not relevant for internal timing; the default is sufficient.
•Framing—Not relevant for internal timing; the default is sufficient.
•Sync Messaging—Checked automatically. SSM is used to deliver clock quality. The SSM supported in SDH is G811, STU, G812T, G812L, SETS, DUS (ordered from high quality to low quality). If you selected 2.048 MHz or 64 KHz, the SSM option is disabled.
•AIS Threshold—Not relevant for internal timing.
•LBO—Not relevant for internal timing.
•Sa bit—Not relevant for internal timing.
Step 5 In the Reference List subtab, enter the following information:
•NE References
–Ref-1—Set to Internal Clock.
–Ref-2—Set to Internal Clock.
–Ref-3—Set to Internal Clock.
•BITS 1 Out/BITS 2 Out (Applicable to the ONS 1545 SDH)—Set to None.
Step 6 Click Apply.
Step 7 In the Domain Explorer tree, select the node that will be timed from the node that was set up in Steps 1 through 7 and choose Configuration > NE Explorer.
Step 8 In the Timing tab, complete the following:
•In the General Timing section of the General subtab:
–Timing Mode—Set to Line.
–Revertive—Not applicable for internal timing; the default setting is sufficient.
–Reversion Time—Not applicable for internal timing; the default setting is sufficient.
•In the NE References section of the Reference List subtab:
–Ref-1—Set to the STM-N trunk card with the closest connection to the node.
–Ref-2—Set to the STM-N trunk card with the next closest connection to the node.
–Ref-3—Set to Internal Clock.
Step 9 Click Apply.
Step 10 Repeat Steps 7 through 9 for each node that will be timed by the node.
5.5 Synchronizing the Network for MGX Voice Gateway Devices
The CTM server and managed nodes must be synchronized with the same date and time. If the CTM server and managed nodes do not have the same date and time, there might be inconsistencies in retrieving time-sensitive data.
5.5.1 Viewing Clocking Sources
CTM supports manual clock configuration. This configures both a primary and secondary clock source, which are distributed throughout the network. The secondary clock source takes over if the primary clock source fails. You can configure a network setup with one master clock source, and a secondary to ensure network clock stability.
On Cisco MGX 8850 (PXM45) switches, clock source configuration is done on a PXM45 card, and clock sourcing information is passed to other nodes over AXSM lines.
Clock synchronization is done directly on the Cisco MGX 8880 using the CLI.
These topics are used to manage and configure clocking sources:
•Configuring Global Clocking
•Displaying the List of Available Clock Sources
•Displaying the List of Manual Clock Sources
•Creating a Manual Clock Source
5.5.1.1 Configuring Global Clocking
Step 1 In the Domain Explorer tree, select the node and choose Configuration > MGX Voice Gateway > Configuration Center.
Step 2 Drag and drop the node from the Hierarchy pane to the right-most pane.
Step 3 Click the Elements tab to display the Configuration Window for Elements.
Step 4 Click the Clocking tab to display the Global Clocking Configuration window.
Step 5 Choose Global Clocking Configuration from the Category drop-down list.
Step 6 The Distribution Method is manual. This specifies that the network clock source is statically configured in the device.
Step 7 Enter the maximum network diameter, measured in hops, in the Max Diameter field.
The range is from 3-20. The Cisco default value is 20.
Note Change Time—The time when the global clocking was configured.
Clock Source—The clock source from the list of available clocking source
Step 8 Click Apply to apply the global clocking configuration settings.
5.5.1.2 Displaying the List of Available Clock Sources
To display the available clock sources:
Step 1 In the Domain Explorer, right-click the PNNI node from the Hierarchy pane and choose Configuration Center.
Step 2 Click the Elements tab to display the Configuration Window for Elements.
Step 3 Click the Clocking tab to display Clocking Configuration window.
Step 4 Choose Available Clock Sources to display the list of available clock sources from the Category drop-down list.
5.5.1.3 Displaying the List of Manual Clock Sources
To display a list of manual clock sources:
Step 1 In the Domain Explorer, right-click the PNNI node from the Hierarchy pane and choose Configuration Center.
Step 2 Click the Elements tab to display the Configuration Window for Elements.
Step 3 Click the Clocking tab to display Clocking Configuration window.
Step 4 Choose Manual Clock Sources from the Category drop-down list.
5.5.1.4 Creating a Manual Clock Source
To create a manual clock source:
Step 1 In the Domain Explorer, right-click the PNNI node from the Hierarchy pane and choose Configuration Center.
Step 2 Click the Elements tab to display the Configuration Window for Elements.
Step 3 Click the Clocking tab to display Clocking Configuration window.
Step 4 Choose Manual Clock Sources from the Category drop-down list.
Step 5 Click Create to display the Manual Clock Source Configuration Window.
Step 6 Choose one of the following clock source options from the Priority drop-down list:
•primary— Configures an available network clock source to be the primary manual clock source.
•secondary—Configures an available network clock source to be the secondary manual clock source.
•default—Configures an available network clock source to be the default manual clock source.
Step 7 Enter the index value that is used to identify the primary, secondary, or default manual clock source in the Clock Source Index field.
Step 8 Click Apply to create a manual clock source.
5.6 Configuring and Administering the CRS-1 and XR 12000
This section explains the NE Explorer menu options used to configure the CRS-1 and XR 12000.
Tip See Appendix A, "CRS-1 and XR 12000 NE Explorer—Configuration and Administration Application Icons" for an explanation of the icons available in the CRS-1 NE Explorer and XR 12000 NE Explorer configuration and administration applications.
The CRS-1 NE Explorer and XR 12000 NE Explorer Configuration and Administration menus allow access to a number of applications, as follows:
Tip You can move your cursor over each port in rack view to display availability and alarm information.
5.6.1 Explicit Path Configuration Application
The Explicit Path Configuration application allows you to configure the explicit path. An IP explicit path is a list of IP addresses, each representing a node or link in the explicit path.
The following table describes the explicit path application fields.
Table 5-21 Field Descriptions for the Explicit Path Configuration Application Window
Field
|
Description
|
Basics Area
|
Category list
|
Allows you to choose whether an IP explicit path name or identifier will be entered in the Name/ID field. Options are:
•Name—The IP explicit path is identified by a name.
•Identifier—The IP explicit path is identified by an identifier number.
|
Name/Id field
|
Allows you to enter a name or identifier for the IP explicit path.
|
Enable check box
|
Allows you to enable or disable the IP explicit path.
|
Path Details Table
|
Index column
|
Displays the index number for the link in the IP explicit path. This value is automatically generated and the field is read-only.
|
IP Address column
|
Displays the IP address for the link in the IP explicit path.
Double-clicking the cell activates it and allows you to enter the IP address.
|
Exclude column
|
Allows you to exclude or include the link in the IP explicit path.
Double-clicking the cell changes the value from false to true or from true to false.
|
Up and Down arrows
|
Allows you to reorder the IP addresses in the explicit path. Choose a row in the table and use the arrows to move the row up or down. The index number is automatically modified based on location in the table relative to other records in the same list.
|
Add button
|
Allows you to add an IP address to the explicit path. Click the Add button; then, click the IP Address cell in the table and enter a valid IP address.
|
Remove button
|
Allows you to remove the chosen IP address from the explicit path. Choose a row in the table and click Remove to remove the IP address from the explicit path.
|
5.6.2 MPLS-TE Configuration Application
The MPLS-TE Configuration application contains the following tabs:
•Global Tab
•Labels Tab
•Links Tab
•Tunnel Head Tab
•Operations Tab
The MPLS-TE Configuration application allows you to configure MPLS-TE for a Cisco router.
MPLS is a standards-based solution driven by the Internet Engineering Task Force (IETF) that was devised to convert the Internet and IP backbones into business-class transport mediums. Traffic engineering is the process of adjusting bandwidth allocations to accommodate high-priority traffic. In MPLS-TE, the upstream router creates a network tunnel for a particular traffic destination, reserving the bandwidth required for that tunnel. This network tunnel lets IP match the abilities of ATM or Frame Relay, which both offer that capability under private virtual channels (PVCs).
MPLS traffic engineering automatically establishes and maintains label-switched paths (LSPs) across the backbone using Resource Reservation Protocol (RSVP) by either:
•Dynamic path option
•Explicit path option (manually)
Available resources are flooded throughout the network by means of extensions to a link-state-based Interior Gateway Protocol (IGP).
MPLS-TE enables an MPLS backbone to replicate and expand on the traffic engineering capabilities of Layer 2 ATM and Frame Relay networks. MPLS is an integration of Layer 2 and Layer 3 technologies. By making traditional Layer 2 features available to Layer 3, MPLS enables traffic engineering.
MPLS-TE uses IGP (Intermediate System-to-Intermediate System [ISIS] and Open Shortest Path First [OSPF]) to flood bandwidth information through a network. It also uses RSVP extensions to distribute labels and constraint-based routing to compute paths in the network. These extensions have been defined in RFC 3209.
MPLS-TE provides connectivity failure protection using fast reroute (FRR). FRR protects primary tunnels by using preprovisioned backup tunnels. During a failure condition, the primary tunnel switches over to the backup tunnel.
5.6.2.1 Global Tab
The Global tab allows you to perform the following tasks:
•Configure the use of explicit-null labels or implicit-null labels.
•Specify the maximum bandwidth hold time and flooding interval.
•Configure the tunnel reoptimization frequency.
The following table describes the Global tab fields.
Table 5-22 Field Descriptions for the Global Tab
Field
|
Description
|
Basics Area
|
Advertise explicit null check box
|
Allows you to specify that tunnels originating from the router use explicit-null labels.
|
Maximum Tunnels field
|
Allows you to specify the maximum number of tunnels.
|
Link Management Timers Area
|
Max bandwidth holdtime (secs) field
|
Allows you to set the length of time that bandwidth is held for an RSVP setup message while waiting for the corresponding RSVP Resv message to come back.
|
Flooding interval (secs) field
|
Allows you to set the length of the interval for periodic flooding.
|
Tunnel Reoptimization Area
|
Frequency (secs) field
|
Allows you to control the frequency with which tunnels with established LSP are checked for better paths. A value of 0 disables reoptimization.
|
Fast Reroute Promotion Timer (secs) field
|
Allows you to set the fast reroute backup promotion timer.
|
Topology Hold-down Timer (secs) field
|
Allows you to set the link hold-down timer when path admission fails on the link, and is used in the next path calculation.
|
Path Selection Metric Type list
|
Allows you to choose the metric to use for path calculation. Options are:
•IGP
•TE
|
5.6.2.2 Labels Tab
The Labels tab allows you to configure the range of local labels.
The following table describes the Labels tab fields.
Table 5-23 Field Descriptions for the Labels Tab
Field
|
Description
|
Basics Area
|
Table Id field
|
Allows you to specify the index of the label table to display.
|
Label Range Area
|
Min field
|
Allows you to configure the range minimum of local labels available for use on packet interfaces. The minimum is the smallest label allowed in the label space.
The range provided in the Min and Max fields is used by all MPLS applications that allocate local labels (for dynamic label switching, MPLS traffic engineering, and MPLS virtual private networks [VPNs]).
Labels 0 through 15 are reserved by the IETF and cannot be included in the range.
|
Max field
|
Allows you to configure the range maximum of local labels available for use on packet interfaces. The maximum is the largest label allowed in the label space.
The range provided in the Min and Max fields is used by all MPLS applications that allocate local labels (for dynamic label switching, MPLS traffic engineering, and MPLS VPNs).
Labels 0 through 15 are reserved by the IETF and cannot be included in the range.
|
5.6.2.3 Links Tab
The Links tab contains General and Backup Tunnels subtabs. The General subtab is displayed by default when the Links tab is clicked.
The Links tab allows you to perform the following tasks:
•Enable MPLS on the link.
•Set flooding thresholds for the interface.
•Specify backup tunnels.
•Configure the administrative weight.
•Configure the attribute flags.
5.6.2.3.1 General Subtab
The General subtab allows you to perform the following tasks:
•Specify the link name.
•Set flooding thresholds for the interface.
•Configure the administrative weight.
•Configure the attribute flags.
The following table describes the General subtab fields.
Table 5-24 Field Descriptions for the General Subtab
Field
|
Description
|
Basics Area
|
Name
|
Allows you to specify the name of the interface to be MPLS-TE enabled.
|
Name field
|
Allows you to enter the name of the interface to be MPLS-enabled.
|
Name ellipsis button
|
Allows you to choose the name of the interface to be MPLS-enabled using the Select Interfaces dialog box.
|
Administrative weight field
|
Allows you to specify the cost of the link. The Administrative weight field overrides the IGP administrative weight (cost) of the link.
|
Attribute flags field
|
Allows you to set the user-specified attribute flags for the interface.
This field assigns attributes to a link so that tunnels with matching attributes (represented by their affinity bits) prefer this link instead of others that do not match.
The interface is flooded globally, allowing it to be used as a tunnel head-end path selection criterion.
|
Flooding Thresholds Area
|
Up Thresholds (%) field
|
Allows you to set up the flooding thresholds for increased resource availability. You can enter up to 14 space-delimited values within the specified range.
The up and down flooding thresholds set the reserved bandwidth thresholds for a link.
When a threshold is crossed, MPLS traffic engineering link management advertises updated link information. If no thresholds are crossed, changes can be flooded periodically unless periodic flooding is disabled.
|
Down Thresholds (%) field
|
Allows you to set the flooding thresholds for decreased resource availability. You can enter up to 14 space-delimited values within the specified range.
The up and down flooding thresholds set the reserved bandwidth thresholds for a link.
When a threshold is crossed, MPLS traffic engineering link management advertises updated link information. If no thresholds are crossed, changes can be flooded periodically unless periodic flooding is disabled.
|
5.6.2.3.2 Backup Tunnels Subtab
The Backup Tunnels subtab allows you to specify the backup tunnels for the link.
The following table describes the Backup Tunnels subtab fields.
Table 5-25 Field Descriptions for the Backup Tunnels Subtab
Field
|
Description
|
Tunnel Number list
|
Allows you to enter which tunnels to use as backup tunnels.
Clicking Add adds a blank row in the list, which allows you to double-click the row and enter a valid tunnel number.
Clicking Remove removes the chosen tunnel from the list.
|
5.6.2.4 Tunnel Head Tab
The Tunnel Head tab contains three subtabs: General, Advanced, and Path Selection. The General subtab is displayed by default when the Tunnel Head tab is clicked.
The Tunnel Head tab allows you to perform the following tasks:
•Configure tunnel parameters including path, bandwidth, and source IP address.
•Specify and configure the shortest path first (SPF) calculation.
•Specify bandwidth.
•Enable record route and fast reroute.
•Specify the tunnel path selection metric used for path calculation.
5.6.2.4.1 General Subtab
The General subtab allows you to perform the following tasks:
•Specify the tunnel name, destination, and bandwidth.
•Specify the tunnel IP address.
•Configure the tunnel priorities.
•Configure the tunnel affinities.
The following table describes the General subtab fields.
Table 5-26 Field Descriptions for the General Subtab
Field
|
Description
|
Basics Area
|
Tunnel Name field
|
Allows you to enter a tunnel name.
|
Destination field
|
Allows you to enter the destination of the tunnel.
|
Bandwidth (kbps) field
|
Allows you to enter the bandwidth required for an MPLS traffic engineering tunnel.
|
Reserve Bandwidth from SubPool field
|
Allows you to choose bandwidth from a subpool rather than the global pool.
|
Shutdown check box
|
Allows you to choose to shut down a tunnel, protecting the interface. When this tunnel is shut down or removed, the traffic that it was carrying is rerouted onto another tunnel (if available).
|
IP Address Area
|
None radio button
|
Allows you to specify that the IP address is not configured. You can configure a tunnel without specifying the IP address.
|
Unnumbered
|
Allows you to configure the IP address for the tunnel without an explicit address.
|
Unnumbered radio button
|
Allows you to enable IP processing without an explicit address.
|
Unnumbered field
|
Allows you to enter a valid interface name. The Unnumbered radio button must be chosen to enable the Unnumbered field.
|
Unnumbered ellipsis button
|
Allows you to choose an interface from the Select Interfaces dialog box. The Unnumbered radio button must be chosen to enable the Unnumbered ellipsis button.
|
IP/Mask
|
Allows you to configure the IP address for the tunnel using an IPv4 address and mask or prefix length.
|
IP/Mask radio button
|
Allows you to enable IP processing with an explicit address.
|
IP/Mask field
|
Allows you to enter a valid IPv4 address and mask or prefix length for the tunnel. The IP/Mask radio button must be chosen to enable the IP/Mask field.
|
Priority Area
|
Setup Priority field
|
Allows you to enter a setup priority. The priority is used when signaling an LSP for the tunnel to determine which existing tunnels can be preempted.
A lower priority number indicates a higher priority. Therefore, an LSP with a setup priority of 0 can preempt any LSP with a non-0 priority.
When an LSP is being signaled and an interface does not currently have enough bandwidth available for that LSP, the call admission software preempts lower-priority LSPs so that the new LSP can be admitted. (LSPs are preempted if the new LSPs are allowed to be admitted.)
The new LSP priority is its setup priority and the existing LSP priority is its hold priority. The two priorities make it possible to signal an LSP with a low setup priority (so that the LSP does not preempt other LSPs on setup) but a high hold priority (so that the LSP is not preempted after it is established). Setup priority and hold priority are typically configured to be equal, and setup priority cannot be better (numerically smaller) than the hold priority.
|
Hold Priority field
|
Allows you to enter a hold priority. This is the hold priority associated with an LSP for the tunnel to determine if it should be preempted by other LSPs that are being signaled.
A lower priority number indicates a higher priority. Therefore, an LSP with a setup priority of 0 can preempt any LSP with a non-0 priority.
When an LSP is being signaled and an interface does not currently have enough bandwidth available for that LSP, the call admission software preempts lower-priority LSPs so that the new LSP can be admitted. (LSPs are preempted if the new LSPs are allowed to be admitted.)
The new LSP priority is its setup priority and the existing LSP priority is its hold priority. The two priorities make it possible to signal an LSP with a low setup priority (so that the LSP does not preempt other LSPs on setup) but a high hold priority (so that the LSP is not preempted after it is established). Setup priority and hold priority are typically configured to be equal, and setup priority cannot be better (numerically smaller) than the hold priority.
|
Affinity Area
|
Affinity Bits field
|
Allows you to enter the affinity bits value required for links carrying the tunnel. The affinity determines the attributes of the links that this tunnel will use (that is, the attributes for which the tunnel has an affinity).
|
Affinity Mask field
|
Allows you to set the affinity mask value required for links carrying the tunnel. The affinity determines the attributes of the links that this tunnel will use (that is, the attributes for which the tunnel has an affinity).
The attribute mask determines which link attribute the router should check. If a bit in the mask is 0, the attribute value of a link or that bit is irrelevant. If a bit in the mask is 1, the attribute value of that link and the required affinity of the tunnel for that bit must match. A tunnel can use a link if the tunnel affinity equals the link attributes and the tunnel affinity mask. Any properties set to 1 in the affinity should also be 1 in the mask.
In other words, affinity and mask should be set such that:
tunnel affinity = (tunnel affinity and tunnel affinity mask)
|
5.6.2.4.2 Advanced Subtab
The Advanced subtab allows you to perform the following tasks:
•Configure the autoroute parameters.
•Configure the backup bandwidth parameters.
•Enable reserving backup bandwidth.
•Enable fast reroute.
•Set the load-sharing for each tunnel (indicate the proportion of total traffic you want to be allocated into each individual tunnel).
The following table describes the Advanced subtab fields.
Table 5-27 Field Descriptions for the Advanced Subtab
Field
|
Description
|
Autoroute Area
|
Auto Announce check box
|
Allows you to specify that the IGP (routing protocol) should use the tunnel (if the tunnel is up) in its enhanced SPF calculation.
Currently, the only way to forward traffic onto a tunnel is to enable this feature or explicitly configure forwarding (for example, with an interface static route).
|
IGP Metric Subarea
|
Default radio button
|
Allows you to choose the default IP traffic engineering tunnel metric that the IGP-enhanced SPF calculation will use. The Cisco default is metric relative 0.
|
Relative
|
Allows you to choose to use the relative metric that the IGP-enhanced SPF calculation will use.
|
Relative radio button
|
Allows you to choose the relative metric as the IGP metric.
|
Relative field
|
Allows you to enter a relative metric. A positive, negative, or zero metric value is required. The Relative radio button must be chosen to enable the Relative field.
|
Absolute
|
Allows you to choose to use the absolute metric that the IGP-enhanced SPF calculation will use.
|
Absolute radio button
|
Allows you to choose the absolute metric as the IGP metric.
|
Absolute field
|
Allows you to enter an absolute metric. A positive metric value is required. The Absolute radio button must be chosen to enable the Absolute field.
|
Backup Bandwidth Area
|
Reserve Backup Bandwidth check box
|
Allows you to enable or disable reserve backup bandwidth.
|
From Pool field
|
Allows you to choose the pool for the reserve backup bandwidth. Options are:
•Any Pool—The backup bandwidth in any pool provided by an MPLS traffic engineering backup tunnel.
•Global Pool—The backup bandwidth in a global pool provided by an MPLS traffic engineering backup tunnel.
•Sub Pool—The backup bandwidth in a subpool provided by an MPLS traffic engineering backup tunnel. Only LSPs using bandwidth from the subpool can use the backup tunnel.
|
Unlimited Bandwidth radio button
|
Allows you to set the reserve backup bandwidth for the tunnel to unlimited.
|
Limited Bandwidth
|
Allows you to limit the reserve backup bandwidth for the tunnel.
|
Limited Bandwidth radio button
|
Allows you to enable limiting the reserve backup bandwidth for the tunnel.
|
Limited Bandwidth field
|
Allows you to enter the reserve backup bandwidth.
|
Other Area
|
Record Route check box
|
Allows you to document the route used by a tunnel.
|
Fast Reroute check box
|
Allows you to enable fast-reroute protection for the tunnel.
|
5.6.2.4.3 Path Selections Subtab
The Path Selections subtab allows you to perform the following tasks:
•Choose the path selection metric.
•Choose the available IP path and set the path options.
The following table describes the Path Selections subtab fields.
Table 5-28 Field Descriptions for the Path Selections Subtab
Field
|
Description
|
Path Selection Metric Area
|
Path Selection Metric list
|
Allows you to choose the tunnel path selection metric to be used for path calculation. Options are:
•Use IGP Metric
•Use MPLS-TE Metric
|
Path Option Area
|
Available IP Path list
|
Allows you to choose a path option for the tunnel.
Choose a path option from the Available IP Path list; then, click the To arrow to add the path to the Path Options table.
|
Path Options table
|
Allows you to configure several path options for a single tunnel. For example, there can be several explicit path options and a dynamic option for one tunnel. The following fields are in the Path Options table:
•Preference—This is a sequential number automatically generated. This field is not user-configurable.
•Name/ID—This field contains the path name or path number of the IP explicit path that the tunnel uses with this path option. This field is not user-configurable.
•Type—This field indicates whether the LSP path is dynamically calculated (Dynamic) or is an IP explicit path (Explicit). This field is not user-configurable.
•Lockdown—By default the LSP is reoptimized. The field shows false. Double-clicking the field changes the value from false to true or from true to false.
|
Up and Down arrows
|
Allows you to reorder the path options. Choose a row in the table; then, use the arrows to move the row up or down. The preference number is automatically modified based on location in the table relative to other records in the same list.
|
5.6.2.5 Operations Tab
The Operations tab allows you to perform the following tasks:
•Reoptimize tunnels.
•Reset counters.
The following table describes the Operations tab fields.
Table 5-29 Field Descriptions for the Operations Tab
Field
|
Description
|
Reoptimize Tunnels Area
|
All tunnels radio button
|
Allows you to choose all tunnels for reoptimization.
|
This tunnel
|
Allows you to choose the tunnel for reoptimization.
|
This tunnel radio button
|
Allows you to enable the reoptimization of a specific tunnel.
|
This tunnel field
|
Allows you to enter a tunnel name. The This tunnel radio button must be chosen to enable the This tunnel field.
|
Reoptimize Tunnels button
|
Tunnel reoptimization looks for a more optimal path for the tunnel.
Allows you to look for an optimal path for all tunnels or a specified tunnel. When the button is clicked, the Confirm dialog box prompts you to confirm that you want to reoptimize the tunnels. If you click Yes, the tunnels are reoptimized; if you click No, the tunnels are not reoptimized.
|
Clear Counters Area
|
All Counters radio button
|
Allows you to clear all counters for tunnels.
|
Summary Counters radio button
|
Allows you to clear only summary counters for tunnels.
|
For this tunnel
|
Allows you to choose a tunnel. Only counters for this tunnel will be cleared.
|
For this tunnel radio button
|
Allows you to enable the reoptimization of a specific tunnel.
|
For this tunnel field
|
Allows you to enter a tunnel name. The For this tunnel radio button must be chosen to enable the For this tunnel field.
|
Clear Counters button
|
Counters include tunnel input and output counters. Clearing counters for tunnels clears (sets to zero) counters so that you can monitor the tunnel traffic easily.
Allows you to clear counters. When the button is clicked, the Confirm dialog box prompts you to confirm that you want to clear the counters. If you click Yes, the counters are cleared; if you click No, the counters are not cleared.
|
5.6.3 VRF Application
The VPN routing and forwarding (VRF) applications contains the following tabs:
•General Tab
•Address Family Tab
The VRF application allows you to configure VRFs for a Cisco router. A VRF contains the routing information that defines the customer's virtual private network (VPN) site that is attached to a Provider Edge (PE) router. A VPN is associated with one or more VRFs.
A VRF consists of the following elements:
•An IP routing table
•A derived Cisco express forwarding (CEF) table
•A set of interface that use the CEF table
•A set of rules and routing protocols that determine what goes into the forwarding table
The router maintains a separate routing and CEF table for each VRF. This prevents information from being sent outside to the VPN and allows the same subnet to be used in several VPNs without causing duplicate IP address problems. VRF configuration defines the VPN membership parameters such as the following:
•Route Descriptor (RD)—Used to create routing and forwarding tables for a VRF.
•Route Targets (RT)—Used to create a route-target extended community for a VRF.
5.6.3.1 General Tab
The General tab allows you to specify basic VRF information. The following table describes fields in the General tab.
Table 5-30 Field Description for the General Tab
Field
|
Description
|
VRF Name
|
Allows you to enter the VRF name. VRF name can have a maximum of 32 characters.
|
Description
|
Allows you to enter a description of the VRF. The description can have a maximum of 244 characters.
|
5.6.3.2 Address Family Tab
The Address Family tab allows you to specify address family information. The following table describes fields in the Address Family tab.
Table 5-31 Field Description for the Address Family Tab
Field
|
Description
|
VRF Name field
|
Allows you to specify the VRF name.
|
VRF Name ellipsis button
|
Allows you to select the name of the VRF from the Select VRF dialog box.
|
AF Mode list
|
Allows you to view the address family configuration associated with the VRF.
|
Import Route Policy
|
Allows you to specify the route policy that gets imported into the VRF. Use this to provide finer control and discard prefixes that do not match a configured policy.
|
Export Route Policy
|
Allows you to specify the route policy that gets exported from the VRF. Use this to provide finer control and discard prefixes that do not match a configured policy.
|
Import Route Targets
|
Type list
|
Allows you to specify the type of import route target.
|
AS
|
Allows you to enter the AS number. Value must be between 0 and 65535. Default value is 0.
|
AS Index
|
Allows you to enter the AS index number. Value must be between 0 and 4294967295. Default value is 0.
|
IP Address
|
Allows you to enter the IP address.
|
IP Address Index
|
Allows you to enter the IP address index number. Value must be between 0 and 4294967295. Default value is 0.
|
>>
|
Allows you to add a route target information to the Import Route Target List.
|
<<
|
Allows you to remove a route target information to the Import Route Target List.
|
Import Route Target List
|
Provides a list of import route targets.
|
Export Route Targets
|
Type
|
Allows you to specify the type of export route target.
|
AS
|
Allows you to enter the AS number. Value must be between 0 and 65535. Default value is 0.
|
AS Index
|
Allows you to enter the AS index number. Value must be between 0 and 4294967295. Default value is 0.
|
IP Address
|
Allows you to enter the IP address.
|
IP Address Index
|
Allows you to enter the IP address index number. Value must be between 0 and 4294967295. Default value is 0.
|
>>
|
Allows you to add a route target information to the Export Route Target List.
|
<<
|
Allows you to remove a route target information to the Export Route Target List.
|
Export Route Target List
|
Provides a list of export route targets.
|
5.6.3.3 Cross-launching Another VRF Application
From an existing CRS-1 or XR 12000 NE's VRF application, you can launch a neighbor NE's VRF application while maintaining and passing the existing application's context.
Step 1 From the VRF application window, click either the General or Address Family tab.
Step 2 Select a record from the list.
Step 3 Right-click and select either Configure Peer VRF from the General tab or Configure Peer VRF AF from the Address Family tab.
Step 4 Choose an IP address from the Select IP Address dialog box.
Another NE Explorer is launched, which displays the VRF application of the neighbor NE. A record is automatically added to the General or Address Family tab that has the same entries as the record where you launched the peer application.
5.6.4 Interface Common Attributes Configuration Application
The Interface Common Attributes Configuration application contains the following tabs:
•Physical Interfaces Tab
•Logical Interfaces Tab
The Interface Common Attributes Configuration application allows you to configure interface attributes that are common across all interfaces, including Ethernet and Packet-over-SONET (POS). Configuration of common attributes prevents the need to enter the same data numerous times across various interfaces.
When a common attribute is configured in the Ethernet or POS application, the changes can be displayed and edited in the Interface Common Attributes Configuration application.
Tip You can move your cursor over each port in rack view to display availability and alarm information.
5.6.4.1 Physical Interfaces Tab
The Physical Interfaces tab contains IPv4 Configuration and Dampening subtabs. The IPv4 Configuration subtab is displayed by default when the Physical Interfaces tab is clicked.
The Physical Interfaces tab allows you to perform the following tasks:
•Provide a description of the interface.
•Specify the maximum transmission unit (MTU) Layer 2 value.
•Choose to enable or disable the Cisco Discovery Protocol (CDP).
•Allows you to manually shut down the interface.
The following table describes fields in the Physical Interfaces table.
Table 5-32 Field Descriptions for the Physical Interfaces Table
Field
|
Description
|
Interface Name
|
Displays the name of the interface.
|
Description
|
Allows you to enter a description of the interface.
|
IP Address
|
Allows you to enter a valid IP address. The IP Address radio button must be chosen to enable the IP Address field.
|
Mask
|
Allows you to enter a valid mask for the IP address of the interface.
|
MTU Layer 2 (bytes)
|
Allows you to enter an MTU Layer 2 value in bytes for the interface. This value is the maximum packet size or MTU size.
|
CDP
|
Allows you to enable or disable CDP on the interface. When CDP is set to the Disable (Default) value on the NE, the Disable (Default) value will not appear in the running configuration.
|
VRF
|
Allows you to enter the VPN Routing and Forwarding (VRF) name.
|
Enable IPv4 Processing
|
Enables IPv4 processing, which allows you to either set primary and secondary IP Version 4 addresses for an interface or set an unnumbered interface to make this interface use the unnumbered interface IP address.
|
Unnumbered Option
|
Allows you to enable IP v4 processing.
|
Unnumbered
|
Displays the chosen interface name.
|
IP Address Option
|
Allows you to configure the IPv4 address.
|
MTU Layer 3 (bytes)
|
Allows you to enter a valid MTU Layer 3 size in bytes. The MTU Layer 3 field contains the maximum MTU available for IP traffic.
|
ICMP Mask Reply
|
Allows you to configure the software to respond to ICMP mask requests by sending ICMP mask reply messages to the interface.
|
Disable Unreachables
|
Allows you to disable ICMP unreachable messages.
|
Enable ICMP Unreachable Message
|
Allows you to enable ICMP unreachable messages. If the software receives a nonbroadcast packet destined for itself and that uses a protocol it does not recognize, the software sends an Internet Control Message Protocol (ICMP) unreachable message to the source. If the software receives a datagram that it cannot deliver to its ultimate destination because it does not know any route to the destination address, it replies to the originator of the datagram with an ICMP host unreachable message.
|
Dampening
|
Allows you to enable state dampening for the interface.
|
Half Life (min)
|
Allows you to enter a time after which a penalty is decreased (decay half-life).
|
Reuse
|
Allows you to set the reuse threshold. An interface state is unsuppressed if the penalty for an interface decreases enough to fall below the reuse threshold.
|
Suppress
|
Allows you to set a suppress threshold. An interface state is suppressed when its penalty (increased by state flaps) exceeds the suppress threshold.
|
Max Suppress (min)
|
Allows you to set the maximum time (in minutes) an interface state can be suppressed. A reasonable rule is to configure the maximum suppress to approximately four times the half-life value.
|
Oper Status
|
Displays the operational status of the interface.
|
Shutdown
|
Allows you to shut down the interface administratively.
|
The following table describes the Physical Interfaces tab fields.
Table 5-33 Field Descriptions for the Physical Interfaces Tab
Field
|
Description
|
Description field
|
Allows you to enter a description of the interface.
|
MTU Layer 2 (bytes) field
|
Allows you to enter an MTU Layer 2 value in bytes for the interface. This value is the maximum packet size or MTU size.
The following are the default MTUs according to media type:
•Ethernet—1514 bytes
•POS—4474 bytes
•Tunnel—1500 bytes
•Loopback—1514 bytes
Each interface has a default maximum packet size or MTU size. This number generally defaults to the largest size possible for that interface type.
|
CDP list
|
Allows you to enable or disable CDP on the interface.
CDP is disabled by default at the global level. CDP is supported on all interfaces except for Spatial Reuse Protocol (SRP) interfaces. To start sending and receiving CDP information on the interface, choose enable. Choose disable to stop sending and receiving CDP information on the interface.
CDP allows Cisco routers to discover each other in a protocol/media independent way. It allows a device to advertise its existence to other devices, and also to detect all other devices on the same LAN (or on the other side of a WAN). CDP is a hello-based protocol, and all devices running CDP will periodically advertise their attributes to their neighbors.
|
Shutdown check box
|
Allows you to shut down the interface administratively.
|
5.6.4.1.1 IPv4 Configuration Subtab
The IPv4 Configuration subtab allows you to perform the following tasks:
•Specify the IPv4 address and mask.
•Specify secondary addresses for the interface.
•Specify the IPv4 MTU for the interface.
•Configure the software response to Internet Control Message Protocol (ICMP) mask requests.
•Specify helper addresses for the interface.
The following table describes the IPv4 Configuration subtab fields.
Note If any networking device on a network segment uses a secondary address, all other devices on that same segment must also use a secondary address from the same network or subnet. Inconsistent use of secondary addresses on a network segment can quickly cause routing loops.
Table 5-34 Field Descriptions for the IPv4 Configuration Subtab
Field
|
Description
|
IPv4 Configuration Area
|
Enable IPv4 Processing check box
|
Enables IPv4 processing, which allows you to either set primary and secondary IP Version 4 addresses for an interface or set an unnumbered interface to make this interface use the unnumbered interface IP address.
An interface can have one primary IP address and multiple secondary IP addresses. Packets generated by the software always use the primary IP address. Therefore, all networking devices on a segment should share the same primary network number.
|
Unnumbered
|
Allows you to enable IPv4 processing without an explicit address.
|
Unnumbered radio button
|
Allows you to enable IP v4 processing.
|
Unnumbered field
|
Allows you to view the chosen interface name.
|
Unnumbered ellipsis button
|
Allows you to choose an interface from the Select Interfaces dialog box. The Unnumbered radio button must be chosen to enable the Unnumbered field.
|
IP Address
|
Allows you to enter a valid IPv4 address for the interface.
|
IP Address radio button
|
Allows you to configure the IPv4 address.
|
IP Address field
|
Allows you to enter a valid IP address. The IP Address radio button must be chosen to enable the IP Address field.
|
Mask field
|
Allows you to enter a valid mask for the IP address of the interface.
|
Secondary Addresses table
|
Allows you to specify secondary IP addresses for the interface. Click the Add button to add a secondary address. Choose an address in the table and click Remove to delete a secondary address from the interface.
Double-click a cell in the IP Address column to activate it and enter the IP address for the secondary address. Double-click a cell in the Mask column to activate it and enter the mask for the secondary address.
There can be more than one secondary address specified. Secondary addresses are treated like primary addresses, except that the system never generates datagrams other than routing updates with secondary source addresses. IP broadcasts and Address Resolution Protocol (ARP) requests are handled properly, as are interface routes in the IP routing table.
Secondary IP addresses can be used in a variety of situations. The following are the most common applications:
•There might not be enough host addresses for a particular network segment. For example, your subnetting allows up to 254 hosts per logical subnet, but on one physical subnet you need to have 300 host addresses. Using secondary IP addresses on the networking devices allows you to have two logical subnets using one physical subnet.
•Many older networks were built using Level 2 bridges. The judicious use of secondary addresses can aid in the transition to a subnetted, router-based network. Routers on an older, bridged segment can be easily made aware that there are many subnets on that segment.
•Two subnets of a single network might otherwise be separated by another network. This situation is not permitted when subnets are in use. In these instances, the first network is extended, or layered on top of the second network using secondary addresses.
|
General Area
|
MTU Layer 3 (bytes) field
|
Allows you to enter a valid MTU Layer 3 size in bytes. The MTU Layer 3 field contains the maximum MTU available for IP traffic.
|
ICMP Mask Reply check box
|
Allows you to configure the software to respond to ICMP mask requests by sending ICMP mask reply messages to the interface.
Hosts can determine subnet masks using the ICMP mask request message. Networking devices respond to this request with an ICMP mask reply message.
|
Helper Addresses table
|
Allows you to specify helper addresses for the interface. Helper addresses are the addresses to which the software forwards User Datagram Protocol (UDP) broadcasts/packets, including BOOTP, received on an interface.
Click the Add button to add a helper address. Choose an address in the table and click Remove to delete a helper address from the interface. There can be more than one helper address for an interface.
Double-click a cell in the Helper IP Address column to activate it and enter the IP address for the helper address.
One common application that requires helper addresses is Dynamic Host Configuration Protocol (DHCP), which is defined in RFC 1531. DHCP protocol information is carried inside of BOOTP packets. To enable BOOTP broadcast forwarding for a set of clients, configure a helper address on the networking device interface closest to the client. The helper address should specify the address of the DHCP server. If you have multiple servers, you can configure one helper address for each server. Because BOOTP packets are forwarded by default, DHCP information can now be forwarded by the networking device. The DHCP server now receives broadcasts from the DHCP clients.
|
5.6.4.1.2 Dampening Subtab
Currently, a router with an unstable data link (also known as a link flap) can remove itself from service and return to service several times in a matter of seconds, requiring all other routers to rebuild their routing tables with each event. Dampening enables a router experiencing link flap to remove itself from network routing tables until return to data-link stability is ensured. Once the link is stable, an up event is sent and the route is added back to the routing table.
With interface state dampening, the interface will immediately remove itself from the routing table on the down event (link flap). If there are multiple link flaps in a short period of time, the interface will ignore the next up event. The interface will remain down until the data link has stabilized based on the dampening configuration parameters. Dampening can ignore up events but cannot ignore down events unless the interface is already down.
Dampening delivers resiliency improvements that include the following:
•Faster convergence—Routers that are not experiencing link flap reach convergence sooner, because routing tables are not rebuilt each time the offending router leaves and enters service. Faster convergence provides a more stable network because a router remains out of service until it is ready to enter service, ensuring fewer transitions.
•Increased network stability—A router with data-link problems removes itself from service until the data link is consistently stable. Other routers simply redirect traffic around the affected router until data-link issues are resolved, thus ensuring that the router loses no data packets.
The Dampening subtab allows you to perform the following tasks:
•Enable dampening for the interface.
•Configure the half-life, suppress, reuse, and maximum suppress values.
The following table describes the Dampening subtab fields.
Table 5-35 Field Descriptions for the Dampening Subtab
Field
|
Description
|
Dampening Attributes Area
|
Dampening check box
|
Allows you to enable state dampening for the interface.
|
HalfLife (min) field
|
Allows you to enter a time after which a penalty is decreased (decay half-life).
Once the interface has been assigned a penalty, the penalty is decreased by half after the half-life period.
|
Suppress field
|
Allows you to set a suppress threshold. An interface state is suppressed when its penalty (increased by state flaps) exceeds the suppress threshold.
|
Reuse field
|
Allows you to set the reuse threshold. An interface state is unsuppressed if the penalty for an interface decreases enough to fall below the reuse threshold.
|
Max Suppress (min) field
|
Allows you to set the maximum time (in minutes) an interface state can be suppressed. A reasonable rule is to configure the maximum suppress to approximately four times the half-life value.
|
5.6.4.2 Logical Interfaces Tab
The Logical Interfaces tab contains IPv4 Configuration and Dampening subtabs. The IPv4 Configuration subtab is displayed by default when the Logical Interfaces tab is clicked.
The Logical Interfaces tab allows you to perform the following tasks:
•Provide a description of the interface.
•Indicate whether the interface is a loopback interface or not.
•Specify the number of loopback instances.
The following table describes fields in the Logical Interfaces table.
Table 5-36 Field Descriptions for the Logical Interfaces Table
Field
|
Description
|
Interface Name
|
Displays the name of the interface.
|
Description
|
Allows you to enter a description of the interface.
|
IP Address
|
Allows you to enter a valid IP address. The IP Address radio button must be chosen to enable the IP Address field.
|
Mask
|
Allows you to enter a valid mask for the IP address of the interface.
|
MTU Layer 2 (bytes)
|
Allows you to enter an MTU Layer 2 value in bytes for the interface. This value is the maximum packet size or MTU size.
|
VRF
|
Allows you to enter a VRF name.
|
Enable IPv4 Processing
|
Enables IPv4 processing, which allows you to either set primary and secondary IP Version 4 addresses for an interface or set an unnumbered interface to make this interface use the unnumbered interface IP address.
|
Unnumbered Option
|
Allows you to enable IP v4 processing.
|
Unnumbered
|
Displays the chosen interface name.
|
IP Address Option
|
Allows you to configure the IPv4 address.
|
MTU Layer 3 (bytes)
|
Allows you to enter a valid MTU Layer 3 size in bytes. The MTU Layer 3 field contains the maximum MTU available for IP traffic.
|
ICMP Mask Reply
|
Allows you to configure the software to respond to ICMP mask requests by sending ICMP mask reply messages to the interface.
|
Disable Unreachables
|
Allows you to disable ICMP unreachable messages.
|
Enable ICMP Unreachable Message
|
Allows you to enable ICMP unreachable messages. If the software receives a nonbroadcast packet destined for itself and that uses a protocol it does not recognize, the software sends an Internet Control Message Protocol (ICMP) unreachable message to the source. If the software receives a datagram that it cannot deliver to its ultimate destination because it does not know any route to the destination address, it replies to the originator of the datagram with an ICMP host unreachable message.
|
Dampening
|
Allows you to enable state dampening for the interface.
|
Half Life (min)
|
Allows you to enter a time after which a penalty is decreased (decay half-life).
|
Reuse
|
Allows you to set the reuse threshold. An interface state is unsuppressed if the penalty for an interface decreases enough to fall below the reuse threshold.
|
Suppress
|
Allows you to set a suppress threshold. An interface state is suppressed when its penalty (increased by state flaps) exceeds the suppress threshold.
|
Max Suppress (min)
|
Allows you to set the maximum time (in minutes) an interface state can be suppressed. A reasonable rule is to configure the maximum suppress to approximately four times the half-life value.
|
Oper Status
|
Displays the operational status of the interface.
|
Shutdown
|
Allows you to shut down the interface administratively.
|
The following table describes the Logical Interfaces tab fields.
Table 5-37 Field Descriptions for the Logical Interfaces Tab
Field
|
Description
|
Description field
|
Allows you to enter a description of the interface.
|
Loopback radio button
|
If selected, it allows you to add, delete, and modify loopback interfaces.
|
Null radio button
|
If selected, it allows you to modify null interfaces.
|
Instance field
|
Allows you to specify a loopback instance number. This is applicable to loopback interfaces.
|
Shutdown check box
|
Allows you to shut down the interface administratively.
|
5.6.4.2.1 IPv4 Configuration Subtab
The IPv4 Configuration subtab allows you to perform the following tasks:
•Specify the IPv4 address and mask.
•Specify secondary addresses for the interface.
•Specify the IPv4 MTU for the interface.
•Configure the software response to Internet Control Message Protocol (ICMP) mask requests.
•Specify helper addresses for the interface.
The following table describes the IPv4 Configuration subtab fields.
Note If any networking device on a network segment uses a secondary address, all other devices on that same segment must also use a secondary address from the same network or subnet. Inconsistent use of secondary addresses on a network segment can quickly cause routing loops.
Table 5-38 Field Descriptions for the IPv4 Configuration Subtab
Field
|
Description
|
IPv4 Configuration Area
|
Enable IPv4 Processing check box
|
Enables IPv4 processing, which allows you to either set primary and secondary IP Version 4 addresses for an interface or set an unnumbered interface to make this interface use the unnumbered interface IP address.
An interface can have one primary IP address and multiple secondary IP addresses. Packets generated by the software always use the primary IP address. Therefore, all networking devices on a segment should share the same primary network number.
|
Unnumbered
|
Allows you to enable IPv4 processing without an explicit address.
|
Unnumbered radio button
|
Allows you to enable IP v4 processing.
|
Unnumbered field
|
Allows you to view the chosen interface name.
|
Unnumbered ellipsis button
|
Allows you to choose an interface from the Select Interfaces dialog box. The Unnumbered radio button must be chosen to enable the Unnumbered field.
|
IP Address
|
Allows you to enter a valid IPv4 address for the interface.
|
IP Address radio button
|
Allows you to configure the IPv4 address.
|
IP Address field
|
Allows you to enter a valid IP address. The IP Address radio button must be chosen to enable the IP Address field.
|
Mask field
|
Allows you to enter a valid mask for the IP address of the interface.
|
Secondary Addresses table
|
Allows you to specify secondary IP addresses for the interface. Click the Add button to add a secondary address. Choose an address in the table and click Remove to delete a secondary address from the interface.
Double-click a cell in the IP Address column to activate it and enter the IP address for the secondary address. Double-click a cell in the Mask column to activate it and enter the mask for the secondary address.
There can be more than one secondary address specified. Secondary addresses are treated like primary addresses, except that the system never generates datagrams other than routing updates with secondary source addresses. IP broadcasts and Address Resolution Protocol (ARP) requests are handled properly, as are interface routes in the IP routing table.
Secondary IP addresses can be used in a variety of situations. The following are the most common applications:
•There might not be enough host addresses for a particular network segment. For example, your subnetting allows up to 254 hosts per logical subnet, but on one physical subnet you need to have 300 host addresses. Using secondary IP addresses on the networking devices allows you to have two logical subnets using one physical subnet.
•Many older networks were built using Level 2 bridges. The judicious use of secondary addresses can aid in the transition to a subnetted, router-based network. Routers on an older, bridged segment can be easily made aware that there are many subnets on that segment.
•Two subnets of a single network might otherwise be separated by another network. This situation is not permitted when subnets are in use. In these instances, the first network is extended, or layered on top of the second network using secondary addresses.
|
General Area
|
MTU Layer 3 (bytes) field
|
Allows you to enter a valid MTU Layer 3 size in bytes. The MTU Layer 3 field contains the maximum MTU available for IP traffic.
|
ICMP Mask Reply check box
|
Allows you to configure the software to respond to ICMP mask requests by sending ICMP mask reply messages to the interface.
Hosts can determine subnet masks using the ICMP mask request message. Networking devices respond to this request with an ICMP mask reply message.
|
Enable ICMP Unreachables
|
Allows you to enable ICMP unreachable messages. If the software receives a nonbroadcast packet destined for itself and that uses a protocol it does not recognize, the software sends an Internet Control Message Protocol (ICMP) unreachable message to the source. If the software receives a datagram that it cannot deliver to its ultimate destination because it does not know any route to the destination address, it replies to the originator of the datagram with an ICMP host unreachable message.
|
Helper Addresses table
|
Allows you to specify helper addresses for the interface. Helper addresses are the addresses to which the software forwards User Datagram Protocol (UDP) broadcasts/packets, including BOOTP, received on an interface.
Click the Add button to add a helper address. Choose an address in the table and click Remove to delete a helper address from the interface. There can be more than one helper address for an interface.
Double-click a cell in the Helper IP Address column to activate it and enter the IP address for the helper address.
One common application that requires helper addresses is Dynamic Host Configuration Protocol (DHCP), which is defined in RFC 1531. DHCP protocol information is carried inside of BOOTP packets. To enable BOOTP broadcast forwarding for a set of clients, configure a helper address on the networking device interface closest to the client. The helper address should specify the address of the DHCP server. If you have multiple servers, you can configure one helper address for each server. Because BOOTP packets are forwarded by default, DHCP information can now be forwarded by the networking device. The DHCP server now receives broadcasts from the DHCP clients.
|
5.6.4.2.2 Dampening Subtab
Currently, a router with an unstable data link (also known as a link flap) can remove itself from service and return to service several times in a matter of seconds, requiring all other routers to rebuild their routing tables with each event. Dampening enables a router experiencing link flap to remove itself from network routing tables until return to data-link stability is ensured. Once the link is stable, an up event is sent and the route is added back to the routing table.
With interface state dampening, the interface will immediately remove itself from the routing table on the down event (link flap). If there are multiple link flaps in a short period of time, the interface will ignore the next up event. The interface will remain down until the data link has stabilized based on the dampening configuration parameters. Dampening can ignore up events but cannot ignore down events unless the interface is already down.
Dampening delivers resiliency improvements that include the following:
•Faster convergence—Routers that are not experiencing link flap reach convergence sooner, because routing tables are not rebuilt each time the offending router leaves and enters service. Faster convergence provides a more stable network because a router remains out of service until it is ready to enter service, ensuring fewer transitions.
•Increased network stability—A router with data-link problems removes itself from service until the data link is consistently stable. Other routers simply redirect traffic around the affected router until data-link issues are resolved, thus ensuring that the router loses no data packets.
The Dampening subtab allows you to perform the following tasks:
•Enable dampening for the interface.
•Configure the half-life, suppress, reuse, and maximum suppress values.
The following table describes the Dampening subtab fields.
Table 5-39 Field Descriptions for the Dampening Subtab
Field
|
Description
|
Dampening Attributes Area
|
Dampening check box
|
Allows you to enable state dampening for the interface.
|
HalfLife (min) field
|
Allows you to enter a time after which a penalty is decreased (decay half-life).
Once the interface has been assigned a penalty, the penalty is decreased by half after the half-life period.
|
Suppress field
|
Allows you to set a suppress threshold. An interface state is suppressed when its penalty (increased by state flaps) exceeds the suppress threshold.
|
Reuse field
|
Allows you to set the reuse threshold. An interface state is unsuppressed if the penalty for an interface decreases enough to fall below the reuse threshold.
|
Max Suppress (min) field
|
Allows you to set the maximum time (in minutes) an interface state can be suppressed. A reasonable rule is to configure the maximum suppress to approximately four times the half-life value.
|
5.6.5 Interface Ethernet Configuration Application
The Interface Ethernet Configuration application contains the following tabs:
•General Tab
•Ethernet Tab
•Administration Tab
The Interface Ethernet Configuration application allows you to configure interface attributes that are specific to Ethernet interfaces. With the exception of the attributes in the Ethernet tab, when an attribute is configured in the Interface Ethernet Configuration application, the changes can be displayed and edited in the common application. See Interface Common Attributes Configuration Application for information on the common application.
5.6.5.1 General Tab
The General tab contains two subtabs: IPv4 Configuration and Dampening. The IPv4 Configuration subtab is displayed by default when the General tab is clicked.
The General tab allows you to perform the following tasks:
•Provide a description of the interface.
•Specify the maximum transmission unit (MTU) Layer 2 value.
•Choose to enable or disable the Cisco Discovery Protocol (CDP).
The following table describes the General tab fields.
Table 5-40 Field Descriptions for the General Tab
Field
|
Description
|
Description field
|
Allows you to enter a description of the interface.
|
MTU Layer 2 (bytes) field
|
Allows you to enter an MTU Layer 2 value in bytes for the Ethernet interface. This value is the maximum packet size or MTU size.
Each interface has a default maximum packet size or MTU size. This number generally defaults to the largest size possible for that interface type.
|
CDP list
|
Allows you to enable or disable CDP on the Ethernet interface. When CDP is set to the Disable(Default) value on the NE, the Disable(Default) value will not appear in the running configuration.
CDP is disabled by default at the global level. CDP is supported on all interfaces except for Spatial Reuse Protocol (SRP) interfaces. To start sending and receiving CDP information on the interface, choose enable. Choose disable to stop sending and receiving CDP information on the interface.
CDP allows Cisco routers to discover each other in a protocol- and media-independent way. It allows a device to advertise its existence to devices, and also to detect all other devices on the same LAN (or on the other side of a WAN). CDP is a hello-based protocol, and all devices running CDP will periodically advertise their attributes to their neighbors.
|
5.6.5.1.1 IPv4 Configuration Subtab
The IPv4 Configuration subtab allows you to perform the following tasks:
•Specify the IPv4 address and mask.
•Specify secondary addresses for the interface.
•Specify the IPv4 MTU for the interface.
•Configure the software response to Internet Control Message Protocol (ICMP) mask requests.
•Specify helper addresses for the interface.
The following table describes the IPv4 Configuration subtab fields.
Note If any networking device on a network segment uses a secondary address, all other devices on that same segment must also use a secondary address from the same network or subnet. Inconsistent use of secondary addresses on a network segment can quickly cause routing loops.
Table 5-41 Field Descriptions for the IPv4 Configuration Subtab
Field
|
Description
|
IPv4 Configuration Area
|
Enable IPv4 Processing check box
|
Enables IPv4 processing, which allows you to either set primary and secondary IP Version 4 addresses for an interface or set an unnumbered interface to make this interface use the unnumbered interface IP address.
An interface can have one primary IP address and multiple secondary IP addresses. Packets generated by the software always use the primary IP address. Therefore, all networking devices on a segment should share the same primary network number.
|
Unnumbered
|
Allows you to enable IPv4 processing without an explicit address.
|
Unnumbered radio button
|
Allows you to enable IP v4 processing.
|
Unnumbered field
|
Allows you to enter a valid interface name. The Unnumbered radio button must be chosen to enable the Unnumbered field.
|
Unnumbered ellipsis button
|
Allows you to choose an interface from the Select Interfaces dialog box. The Unnumbered radio button must be chosen to enable the Unnumbered field.
|
IP Address
|
Allows you to enter a valid IPv4 address for the interface.
|
IP Address radio button
|
Allows you to configure the IPv4 address.
|
IP Address field
|
Allows you to enter a valid IP address. The IP Address radio button must be chosen to enable the IP Address field.
|
Mask field
|
Allows you to enter a valid mask for the IP address of the interface.
|
Secondary Addresses table
|
Allows you to specify secondary IP addresses for the interface. Click the Add button to add a secondary address. Choose an address in the table and click Remove to delete a secondary address from the interface.
Double-click a cell in the IP Address column to activate it and enter the IP address for the secondary address. Double-click a cell in the Mask column to activate it and enter the mask for the secondary address.
There can be more than one secondary address specified. Secondary addresses are treated like primary addresses, except that the system never generates datagrams other than routing updates with secondary source addresses. IP broadcasts and Address Resolution Protocol (ARP) requests are handled properly, as are interface routes in the IP routing table.
Secondary IP addresses can be used in a variety of situations. The following are the most common applications:
•There might not be enough host addresses for a particular network segment. For example, your subnetting allows up to 254 hosts per logical subnet, but on one physical subnet you need to have 300 host addresses. Using secondary IP addresses on the networking devices allows you to have two logical subnets using one physical subnet.
•Many older networks were built using Level 2 bridges. The judicious use of secondary addresses can aid in the transition to a subnetted, router-based network. Routers on an older, bridged segment can be easily made aware that there are many subnets on that segment.
•Two subnets of a single network might otherwise be separated by another network. This situation is not permitted when subnets are in use. In these instances, the first network is extended, or layered on top of the second network using secondary addresses.
|
General Area
|
MTU Layer 3 (bytes) field
|
Allows you to enter a valid MTU Layer 3 size in bytes. The MTU Layer 3 field contains the maximum MTU available for IP traffic.
|
ICMP Mask Replay check box
|
Allows you to configure the software response to ICMP mask requests by sending ICMP mask reply messages to the interface.
Hosts can determine subnet masks using the ICMP mask request message. Networking devices respond to this request with an ICMP mask reply message.
|
Helper Addresses table
|
Allows you to specify helper addresses for the interface. Helper addresses are the addresses to which the software forwards UDP broadcasts and packets, including BOOTP, received on an interface.
Click the Add button to add a helper address. Choose an address in the table and click Remove to delete a helper address from the interface. There can be more than one helper address for an interface.
Double-click a cell in the Helper IP Address column to activate it and enter the IP address for the helper address.
One common application that requires helper addresses is Dynamic Host Configuration Protocol (DHCP), which is defined in RFC 1531. DHCP protocol information is carried inside of BOOTP packets. To enable BOOTP broadcast forwarding for a set of clients, configure a helper address on the networking device interface closest to the client. The helper address should specify the address of the DHCP server. If you have multiple servers, you can configure one helper address for each server. Because BOOTP packets are forwarded by default, DHCP information can now be forwarded by the networking device. The DHCP server now receives broadcasts from the DHCP clients.
|
5.6.5.1.2 Dampening Subtab
Currently, a router with an unstable data link (also known as link flap) can remove itself from service and return to service several times in a matter of seconds, requiring all other routers to rebuild their routing tables with each event. Dampening enables a router experiencing link flap to remove itself from network routing tables until return to data-link stability is ensured. Once the link is stable, an up event is sent and the route is added back to the routing table.
With interface state dampening, the interface will immediately remove itself from the routing table on the down event (link flap). If there are multiple link flaps in a short period of time, the interface will ignore the next up event. The interface will remain down until the data link has stabilized based on the dampening configuration parameters. Dampening can ignore up events but cannot ignore down events unless the interface is already down.
Dampening delivers resiliency improvements that include the following:
•Faster convergence—Routers that are not experiencing link flap reach convergence sooner, because routing tables are not rebuilt each time the offending router leaves and enters service. Faster convergence provides a more stable network because a router remains out of service until it is ready to enter service, ensuring fewer transitions.
•Increased network stability—A router with data-link problems removes itself from service until the data link is consistently stable, so other routers simply redirect traffic around the affected router until data-link issues are resolved, thus ensuring that the router loses no data packets.
The Dampening subtab allows you to perform the following tasks:
•Enable dampening for the interface.
•Configure the half-life, suppress, reuse, and maximum suppress values.
The following table describes the Dampening subtab fields.
Table 5-42 Field Descriptions for the Dampening Subtab
Field
|
Description
|
IPv4 Configuration Area
|
Dampening check box
|
Allows you to enable state dampening for the interface.
|
HalfLife (min) field
|
Allows you to enter a time after which a penalty is decreased (decay half-life).
Once the interface has been assigned a penalty, the penalty is decreased by half after the half-life period.
|
Suppress field
|
Allows you to set a suppress threshold. An interface state is suppressed when its penalty (increased by state flaps) exceeds the suppress threshold.
|
Reuse field
|
Allows you to set the reuse threshold. An interface state is unsuppressed if the penalty for an interface decreases enough to fall below the reuse threshold.
|
Max Suppress (min) field
|
Allows you to set the maximum time (in minutes) an interface state can be suppressed. A reasonable rule is to configure the maximum suppress to approximately four times the half-life value.
|
5.6.5.2 Ethernet Tab
The Ethernet tab allows you to perform the following tasks:
•Specify an Address Resolution Protocol (ARP) timeout length.
•Enable proxy ARP.
•Configure the Ethernet driver parameters.
The following table describes the Ethernet tab fields.
Table 5-43 Field Descriptions for the Ethernet Tab
Field
|
Description
|
ARP Configuration Area
|
ARP Timeout (sec) field
|
Allows you to enter an ARP timeout length.
The ARP timeout length specifies how long dynamic entries learned on an interface remain in the ARP cache.
|
Proxy ARP check box
|
Allows you to enable or disable proxy ARP. Check the check box to enable proxy ARP or uncheck the check box to disable proxy ARP.
When proxy ARP is disabled, the networking device responds to ARP requests received on an interface only if one of the following conditions is met:
•The target IP address in the ARP request is the same as the interface IP address on which the request is received.
•The target IP address in the ARP request has a statically configured ARP alias.
When proxy ARP is enabled, the networking device also responds to ARP requests that meet all of the following criteria:
•The target IP address is not on the same physical network (LAN) on which the request is received.
•The networking device has one or more routes to the target IP address.
•All of the routes to the target IP address go through interfaces other than the one on which the request is received.
|
Ethernet Driver Configuration Area
|
MAC Address field
|
Allows you to enter a valid MAC address for the Ethernet driver.
|
Speed list
|
Allows you to choose the Ethernet connection speed. Options are:
•10 Mbps = Ethernet
•100 Mbps = FastEthernet
•1000 Mbps = GigabitEthernet
|
Media Type list
|
Allows you to choose the media type. Options are:
•AUI—Attachment unit interface. Institute of Electrical and Electronics Engineers (IEEE) 802.3 interface between a media attachment unit (MAU) and a network interface card (NIC). Also called transceiver cable.
•RJ45—Registered jack 45.
•MII—Media independent interface. Standard specification for the interface between network controller chips and their associated media interface chips. The MII automatically senses 10- and 100-MHz Ethernet speeds.
|
Duplex Type Configuration Subarea
|
Enable Duplex check box
|
Allows you to enable or disable a duplex configuration.
|
Full Duplex radio button
|
Allows you to choose full duplex. The Enable Duplex check box must be enabled for this radio button to be available.
|
Half Duplex radio button
|
Allows you to choose half duplex. The Enable Duplex check box must be enabled for this radio button to be available.
|
5.6.5.3 Administration Tab
The Administration tab allows you to manually shut down the interface.
The following table describes the Administration tab field.
Table 5-44 Field Descriptions for the Administration Tab
Field
|
Description
|
Shutdown check box
|
Allows you to shut down the Ethernet interface administratively.
|
5.6.6 Interface POS Configuration Application
The Interface POS Configuration application contains the following tabs:
•General Tab
•POS Tab
•Administration Tab
The Interface POS Configuration application allows you to configure interface attributes that are specific to packet-over-SONET (POS) interfaces. With the exception of the attributes in the POS tab, when an attribute is configured in the Interface POS Configuration application, the changes can be displayed and edited in the common application. See Interface Common Attributes Configuration Application for information on the common application.
POS provides a method for efficiently carrying data packets in SONET or Synchronous Digital Hierarchy (SDH) frames. High-bandwidth capacity and efficient link utilization are characteristics that make POS largely preferred for building the core of data networks. POS uses PPP in High-Level Data Link Control (HDLC)-like framing for data encapsulation at Layer 2 (data link) of the Open System Interconnection (OSI) stack. This method provides efficient packet delineation and error control.
In addition to high-bandwidth efficiency, POS offers secure and reliable data transmission. Reliable data transfer depends on timing integrity.
The real-time POS functions are performed in hardware, according to the hardware configuration offline setup. Configured hardware events are detected by the framer application-specific integrated circuits (ASICs) and the control is passed to the software. The generic POS driver is responsible for providing a mechanism to configure the hardware on a per-interface basis, handle interface state transitions, and collect POS-related statistics.
5.6.6.1 General Tab
The General tab contains IPv4 Configuration and Dampening subtabs. The IPv4 Configuration subtab is displayed by default when the General tab is clicked.
The General tab allows you to perform the following tasks:
•Provide a description of the interface.
•Specify the maximum transmission unit (MTU) Layer 2 value.
•Choose to enable or disable the Cisco Discovery Protocol (CDP).
The following table describes the General tab fields.
Table 5-45 Field Descriptions for the General Tab
Field
|
Description
|
Description field
|
Allows you to enter a description of the interface.
|
MTU Layer 2 (bytes) field
|
Allows you to enter an MTU Layer 2 value in bytes for the POS interface. This value is the maximum packet size or MTU size.
Each interface has a default maximum packet size or MTU size. This number generally defaults to the largest size possible for that interface type.
|
CDP list
|
Allows you to enable or disable CDP on the POS interface. When CDP is set to the Disable(Default) value on the NE, the Disable(Default) value will not appear in the running configuration.
CDP is disabled by default at the global level. CDP is supported on all interfaces except for Spatial Reuse Protocol (SRP) interfaces. To start sending and receiving CDP information on the interface, choose enable. Choose disable to stop sending and receiving CDP information on the interface.
CDP allows Cisco routers to discover each other in a protocol- and media-independent way. It allows a device to advertise its existence to other devices, and also to detect all other devices on the same LAN (or on the other side of a WAN). CDP is a hello-based protocol, and all devices running CDP will periodically advertise their attributes to their neighbors.
|
5.6.6.1.1 IPv4 Configuration Subtab
The IPv4 Configuration subtab allows you to perform the following tasks:
•Specify the IPv4 address and mask.
•Specify secondary addresses for the interface.
•Specify the IPv4 MTU for the interface.
•Configure the software response to Internet Control Message Protocol (ICMP) mask requests.
•Specify helper addresses for the interface.
The following table describes the IPv4 Configuration subtab fields.
Note If any networking device on a network segment uses a secondary address, all other devices on that same segment must also use a secondary address from the same network or subnet. Inconsistent use of secondary addresses on a network segment can quickly cause routing loops.
Table 5-46 Field Descriptions for the IPv4 Configuration Subtab
Field
|
Description
|
IPv4 Configuration Area
|
Enable IPv4 Processing check box
|
Enables IPv4 processing, which allows you to either set primary and secondary IP Version 4 addresses for an interface or set an unnumbered interface to make this interface use the unnumbered interface IP address.
An interface can have one primary IP address and multiple secondary IP addresses. Packets generated by the software always use the primary IP address. Therefore, all networking devices on a segment should share the same primary network number.
|
Unnumbered
|
Allows you to enable IPv4 processing without an explicit address.
|
Unnumbered radio button
|
Allows you to enable IPv4 processing.
|
Unnumbered field
|
Allows you to enter a valid interface name. The Unnumbered radio button must be chosen to enable the Unnumbered field.
|
Unnumbered ellipsis button
|
Allows you to choose an interface from the Select Interfaces dialog box. The Unnumbered radio button must be chosen to enable the Unnumbered field.
|
IP Address
|
Allows you to enter a valid IPv4 address for the interface.
|
IP Address radio button
|
Allows you to configure the IPv4 address.
|
IP Address field
|
Allows you to enter a valid IP address. The IP Address radio button must be chosen to enable the IP Address field.
|
Mask field
|
Allows you to enter a valid mask for the IP address of the interface.
|
Secondary Addresses table
|
Allows you to specify secondary IP addresses for the interface. Click the Add button to add a secondary address. Choose an address in the table and click Remove to delete a secondary address from the interface.
Double-click a cell in the IP Address column to activate it and enter the IP address for the secondary address. Double-click a cell in the Mask column to activate it and enter the mask for the secondary address.
There can be more than one secondary address specified. Secondary addresses are treated like primary addresses, except that the system never generates datagrams other than routing updates with secondary source addresses. IP broadcasts and ARP requests are handled properly, as are interface routes in the IP routing table.
Secondary IP addresses can be used in a variety of situations. The following are the most common applications:
•There might not be enough host addresses for a particular network segment. For example, your subnetting allows up to 254 hosts per logical subnet, but on one physical subnet you need to have 300 host addresses. Using secondary IP addresses on the networking devices allows you to have two logical subnets using one physical subnet.
•Many older networks were built using Level 2 bridges. The judicious use of secondary addresses can aid in the transition to a subnetted, router-based network. Routers on an older, bridged segment can be easily made aware that there are many subnets on that segment.
•Two subnets of a single network might otherwise be separated by another network. This situation is not permitted when subnets are in use. In these instances, the first network is extended, or layered on top of the second network using secondary addresses.
|
General Area
|
MTU Layer 3 (bytes) field
|
Allows you to enter a valid MTU Layer 3 size in bytes. The MTU Layer 3 field contains the maximum MTU available for IP traffic.
|
ICMP Mask Reply check box
|
Allows you to configure the software response to ICMP mask requests by sending ICMP mask reply messages to the interface.
Hosts can determine subnet masks using the ICMP mask request message. Networking devices respond to this request with an ICMP mask reply message.
|
Helper Addresses table
|
Allows you to specify helper addresses for the interface. Helper addresses are the addresses to which the software forwards UDP broadcasts/packets, including BOOTP, received on an interface.
Click the Add button to add a helper address. Choose an address in the table and click Remove to delete a helper address from the interface. There can be more than one helper address for an interface.
Double-click a cell in the Helper IP Address column to activate it and enter the IP address for the helper address.
One common application that requires helper addresses is Dynamic Host Configuration Protocol (DHCP), which is defined in RFC 1531. DHCP protocol information is carried inside of BOOTP packets. To enable BOOTP broadcast forwarding for a set of clients, configure a helper address on the networking device interface closest to the client. The helper address should specify the address of the DHCP server. If you have multiple servers, you can configure one helper address for each server. Because BOOTP packets are forwarded by default, DHCP information can now be forwarded by the networking device. The DHCP server now receives broadcasts from the DHCP clients.
|
5.6.6.1.2 Dampening Subtab
Currently, a router with an unstable data link (also known as link flap) can remove itself from service and return to service several times in a matter of seconds, requiring all other routers to rebuild their routing tables with each event. Dampening enables a router experiencing link flap to remove itself from network routing tables until return to data-link stability is ensured. Once the link is stable, an up event is sent and the route is added back to the routing table.
With interface state dampening, the interface will immediately remove itself from the routing table on the down event (link flap). If there are multiple link flaps in a short period of time, the interface will ignore the next up event. The interface will remain down until the data link has stabilized based on the dampening configuration parameters. Dampening can ignore up events but cannot ignore down events unless the interface is already down.
Dampening delivers resiliency improvements that include the following:
•Faster convergence—Routers that are not experiencing link flap reach convergence sooner, because routing tables are not rebuilt each time the offending router leaves and enters service. Faster convergence provides a more stable network because a router remains out of service until it is ready to enter service, ensuring fewer transitions.
•Increased network stability—A router with data-link problems removes itself from service until the data link is consistently stable, so other routers simply redirect traffic around the affected router until data-link issues are resolved, thus ensuring that the router loses no data packets.
The Dampening subtab allows you to perform the following tasks:
•Enable dampening for the interface.
•Configure the half-life, suppress, reuse, and maximum suppress values.
The following table describes the Dampening subtab fields.
Table 5-47 Field Descriptions for the Dampening Subtab
Field
|
Description
|
Dampening check box
|
Allows you to enable state dampening for the interface.
|
HalfLife (min) field
|
Allows you to enter a time after which a penalty is decreased (decay half-life).
Once the interface has been assigned a penalty, the penalty is decreased by half after the half-life period.
|
Suppress field
|
Allows you to set a suppress threshold. An interface state is suppressed when its penalty (increased by state flaps) exceeds the suppress threshold.
|
Reuse field
|
Allows you to set the reuse threshold. An interface state is unsuppressed if the penalty for an interface decreases enough to fall below the reuse threshold.
|
Max Suppress (min) field
|
Allows you to set the maximum time (in minutes) an interface state can be suppressed. A reasonable rule is to configure the maximum suppress to approximately four times the half-life value.
|
5.6.6.2 POS Tab
The POS tab contains three subtabs: PPP Common, PAP, and CHAP. The PPP Common subtab is displayed by default when the POS tab is clicked.
The POS tab allows you to perform the following tasks:
•Configure encapsulation.
•Configure PPP parameters.
•Configure Password Authentication Protocol (PAP) parameters.
•Configure Challenge Handshake Authentication Protocol (CHAP) parameters.
The following table describes the POS tab fields.
Table 5-48 Field Descriptions for the POS Tab
Field
|
Description
|
Encapsulation list
|
Allows you to choose the encapsulation type for the interface. Options are:
•ppp—Point-to-Point Protocol. Standard protocol for sending data over synchronous serial links.
•hdlc(Default)—High-Level Data Link Controller. ISO communications protocol used in X.25 packet switching networks. When the encapsulation type is set to the hdlc(Default) value on the NE, the hdlc(Default) value will not appear in the running configuration.
|
5.6.6.2.1 PPP Common Subtab
The PPP Common subtab allows you to perform the following tasks:
•Configure the number of authentication retries, unacknowledged confirmation requests, consecutive negative acknowledgments, and unacknowledged terminate requests.
•Enable authentication types.
•Configure the timeout parameters.
The following table describes the PPP Common subtab fields.
Table 5-49 Field Descriptions for the PPP Common Subtab
Field
|
Description
|
Max Authentication Failures field
|
Allows you to enter a specified number of authentication retries. After the number of specified retries is reached, the interface is reset.
|
Max Conf Requests field
|
Allows you to enter the number of unacknowledged confirmation requests.
|
Max Consecutive Conf Naks field
|
Allows you to enter the number of consecutive negative acknowledgments.
|
Max Terminate Requests field
|
Allows you to enter the number of unacknowledged terminate requests.
|
Authentication Area
|
PAP check box
|
Allows you to choose PAP authentication.
|
CHAP check box
|
Allows you to choose CHAP authentication.
|
MS-CHAP check box
|
Allows you to choose MS-CHAP authentication.
|
Authentication List field
|
Allows you to specify an authentication to be used with the interface. Type default to use the default list. This list is enabled when at least one of PAP, CHAP, or MS-CHAP is selected.
|
Timeout Parameters Area
|
Authentication Timeout (sec) field
|
Allows you to specify the maximum time to wait for a response to an authentication packet.
|
NCP Timeout (sec) field
|
Allows you to set a time limit for the successful negotiation of at least one network layer protocol after a PPP connection is established. If no network protocol is negotiated in the given time, the connection is disconnected.
The Network Control Protocol (NCP) timeout protects against the establishment of links that are physically up and carrying traffic at the link level, but are unusable for carrying data traffic due to failure to negotiate the capability to transport any network-level data. Timeout is particularly useful for dialed connections, where it is usually undesirable to leave a telephone circuit active when it cannot carry network traffic.
|
Retry Timeout (sec) field
|
Allows you to set a time limit for the maximum amount of time PPP should wait for a response to any control packet it sends.
|
5.6.6.2.2 PAP Subtab
The PAP subtab allows you to perform the following tasks:
•Refuse PAP authentication from peers.
•Specify the PAP username and password.
The following table describes the PAP subtab fields.
Table 5-50 Field Descriptions for the PAP Subtab
Field
|
Description
|
Refuse PAP list
|
Allows you to refuse PAP authentication from peers requesting it.
Authentication is disabled for all calls, meaning that all attempts by the peer to force the user to authenticate using PAP will be refused. If outbound PAP has been enabled, PAP will be suggested as the authentication method in the refusal packet.
|
PAP Username field
|
Allows you to enter a username to reenable remote PAP support for an interface and include the sent-username and password in the PAP authentication request packet to the peer. This field allows you to replace username configurations on any dialer interface or asynchronous group interface.
|
PAP Password field
|
Allows you to enter a password to reenable remote PAP support for an interface and include the sent-username and password in the PAP authentication request packet to the peer. This field allows you to replace password configurations on any dialer interface or asynchronous group interface.
|
PAP Encryption check box
|
Allows you to enable PAP encryption.
|
5.6.6.2.3 CHAP Subtab
The CHAP subtab allows you to perform the following tasks:
•Refuse CHAP authentication from peers.
•Specify the CHAP username and password.
The following table describes the CHAP subtab fields.
Table 5-51 Field Descriptions for the CHAP Subtab
Field
|
Description
|
Refuse CHAP list
|
Allows you to refuse CHAP authentication from peers requesting it.
Authentication is disabled for all calls, meaning that all attempts by the peer to force the user to authenticate using CHAP will be refused. If outbound CHAP has been enabled, CHAP will be suggested as the authentication method in the refusal packet.
|
CHAP Host Name field
|
Allows you to enter a username to enable a router calling a collection of routers that do not support this command (such as routers running older Cisco IOS software images) to configure a common CHAP secret password to use in response to challenges from an unknown peer.
The CHAP hostname is used for remote CHAP authentication only (when routers authenticate to the peer) and does not affect local CHAP authentication.
|
CHAP Password field
|
Allows you to enter a password to enable a router calling a collection of routers that do not support this command (such as routers running older Cisco IOS software images) to configure a common CHAP secret password to use in response to challenges from an unknown peer.
The CHAP password is used for remote CHAP authentication only (when routers authenticate to the peer) and does not affect local CHAP authentication.
|
CHAP Encryption check box
|
Allows you to enable CHAP encryption.
|
5.6.6.3 Administration Tab
The Administration tab allows you to manually shut down the interface.
The following table describes the Administration tab field.
Table 5-52 Field Descriptions for the Administration Tab
Field
|
Description
|
Shutdown check box
|
Allows you to shut down the POS interface administratively.
|
5.6.7 SONET Port Configuration Application
The SONET Port Configuration application contains the following tabs:
•SONET Tab
•Administration Tab
The SONET Port Configuration application allows you to configure the SONET on a router port using Layer 1 SONET transport technology.
5.6.7.1 SONET Tab
The SONET tab contains SONET Configuration and Alarm Reporting subtabs. The SONET Configuration subtab is displayed by default when the SONET tab is clicked.
The SONET tab allows you to perform the following tasks:
•Configure SONET for the interface.
•Configure the alarm reporting parameters for the interface.
5.6.7.1.1 SONET Configuration Subtab
The SONET Configuration subtab allows you to perform the following tasks:
•Configure a clock source.
•Configure a loopback source.
•Specify the framing for the SONET controller.
•Configure the section, line, and path parameters.
The following table describes the SONET Configuration subtab fields.
Table 5-53 Field Descriptions for the SONET Configuration Subtab
Field
|
Description
|
General Area
|
Clock Source list
|
Allows you to choose which reference clock is used by the sender for the sent signal on SONET ports. Options are:
•Internal—Specifies that the controller will clock its sent data from its internal clock.
•Line(Default)—Specifies that the controller will clock its sent data from a clock recovered from the receive data stream of the line. When the Clock Source list is set to the Line(Default) value on the NE, the Line(Default) value will not appear in the running configuration.
|
Loopback list
|
Allows you to choose the SONET controller for loopback mode. Options are:
•Internal—In the terminal (internal) loopback, the sent signal is looped back to the receiver.
•Line—In the facility (line) loopback, the signal received from the far end is looped back and sent on the line.
The two loopback modes cannot be active at the same time.
|
Framing list
|
Allows you to choose the framing used on the SONET controller. Options are:
•SONET(Default)—Chooses SONET framing. When the Framing list is set to the SONET(Default) value on the NE, the SONET(Default) value will not appear in the running configuration.
•SDH—Chooses SDH framing.
|
Section Area
|
Identifier (J0/C1) Byte field
|
Allows you to enter the JO/C1 byte value in the SONET section overhead. For interoperability with SDH equipment in Japan, use the value 0x01.
The value that you use for the trace byte depends on the type of equipment being used.
|
Line Area
|
Bits s1 and s0 of H1 Byte field
|
Allows you to enter the s1 and s0 bits value of the H1 byte in the SONET line overhead.
•For SONET mode, use 0.
•For SDH mode, use 2.
The values for the s1 and s0 bits can be from 0 to 3. Values 1 and 3 are undefined.
|
AIS When Shutdown check box
|
Allows you to enable automatic insertion of a Line Alarm Indication Signal (LAIS) in the sent SONET signal whenever the SONET port enters the administratively down state.
When the line is placed in administrative shutdown state, a signal is sent to downstream equipment, indicating that there is a problem with the line. LAIS is ignored if automatic protection switching (APS) is running for the corresponding port, because the setting must be enabled for proper APS operation.
|
Delay Trigger (msec) field
|
Allows you to specify the line defects hold-off delay value. The delay trigger is the amount of time a defect must persist before a recovery action, such as protection switching, takes place. If the defect disappears within the delay trigger time, the protection activity is not triggered.
|
Path Area
|
Delay Trigger (msec) field
|
Allows you to specify the path defects hold-off delay value. The delay trigger is the amount of time a defect must persist before a recovery action, such as protection switching, takes place. If the defect disappears within the delay trigger time, the protection activity is not triggered.
|
SPE Content (C2) Byte field
|
Allows you to enter the transmit C2 byte value. This SONET path overhead value allows you to meet a specific standards requirement or to ensure interoperability with equipment from another vendor.
The SONET standards permit or require user access for configuration of some bytes or bits in the SONET path overhead.
|
AIS When Shutdown check box
|
Allows you to enable automatic insertion of a LAIS in the sent SONET signal whenever the SONET port enters the administratively down state.
When the line is placed in administrative shutdown state, a signal is sent to downstream equipment, indicating that there is a problem with the line. LAIS is ignored if APS is running for the corresponding port, because the setting must be enabled for proper APS operation.
|
Scrambling list
|
Allows you to enable SONET payload scrambling on a SONET path. When the Scrambling list is set to the Enabled(Default) value on the NE, the Enabled(Default) value will not appear in the running configuration.
SONET payload scrambling applies a self-synchronous scrambler (x43+1) to the Synchronous Payload Envelope (SPE) of the controller to ensure sufficient bit transition density. Both ends of the connection must be configured using SONET path scrambling.
|
Trace (J1) Buffer field
|
Allows you to enter the user-defined path trace message in the J1 bytes of the SONET path overhead. This trace buffer value allows you to meet specific standards requirements or to ensure interoperability.
|
Shutdown UNEQ check box
|
This check box allows you to enable the automatic insertion of Path Unequipped (UNEQ) code (0x00) in the sent SONET path overhead C2 byte when the SONET path enters an administratively down state.
|
5.6.7.1.2 Alarm Reporting Subtab
The Alarm Reporting subtab allows you to perform the following tasks:
•Set the section alarm threshold and reporting parameters.
•Set the line alarm threshold and reporting parameters.
•Set the path alarm threshold and reporting parameters.
The following table describes the Alarm Reporting subtab fields.
Table 5-54 Field Descriptions for the Alarm Reporting Subtab
Field
|
Description
|
Section Area
|
Threshold B1 BER field
|
Allows you to set the B1 bit error rate (BER) threshold values of the specified alarms for a SONET controller (10 to the power -n).
|
Report LOF check box
|
Allows you to enable Section Loss of Frame (SLOF) reporting.
|
Report B1 BER check box
|
Allows you to enable B1 BER TCA reporting.
|
Report LOS check box
|
Allows you to enable Section Loss of Signal (SLOS) reporting.
|
Line Area
|
Threshold B2 BER field
|
Allows you to set the B2 BER threshold values of the specified alarms for a SONET controller (10 to the power -n).
|
Threshold SF BER field
|
Allows you to set the signal failure (SF) BER threshold values of the specified alarms for a SONET controller (10 to the power -n).
|
Threshold SD BER field
|
Allows you to set the signal degrade (SD) BER threshold values of the specified alarms for a SONET controller (10 to the power -n).
|
Report B2 BER check box
|
Allows you to enable B2 BER TCA reporting. Check the check box to enable B2 BER TCA reporting and uncheck the check box to disable B2 BER TCA reporting.
|
Report SD BER check box
|
Allows you to enable SD BER reporting.
|
Report AIS check box
|
Allows you to enable LAIS reporting.
|
Report RDI check box
|
Allows you to enable Line Remote Defect Indication (LRDI) reporting.
|
Report SF BER check box
|
Allows you to enable SF BER reporting.
|
Path Area
|
Threshold B3 BER field
|
Allows you to set the B3 BER threshold values of the specified alarms for a SONET controller (10 to the power -n).
|
Report B3 BER check box
|
Allows you to enable B3 BER reporting.
|
Report RDI check box
|
Allows you to enable Path RDI reporting.
|
Report AIS check box
|
Allows you to enable Path AIS reporting.
|
Report LOP check box
|
Allows you to enable Path Loss of Pointer (LOP) reporting.
|
Report UNEQ check box
|
Allows you to enable Path UNEQ reporting.
|
5.6.7.2 Administration Tab
The Administration tab allows you to enable shutdown on the chosen interface.
The following table describes the Administration tab field.
Table 5-55 Field Descriptions for the Administration Tab
Field
|
Description
|
Shutdown check box
|
Allows you to shut down the interface administratively (shut down the SONET controller and disable SONET controller processing).
|
5.6.8 Access Control Lists Application
The Access Control Lists application contains the following subtabs:
•Basic Subtab
•Advanced Subtab
•TCP/UDP/SCTP Subtab
•ICMP/IGMP Subtab
The Access Control Lists application allows you to configure IP Version 4 (IPv4) access lists.
An access control list (ACL) consists of one or more access control entries (ACEs) that collectively define the network traffic profile. This profile can then be referenced by Craft Works Interface (CWI) features such as traffic filtering, priority or custom queueing, and dynamic access control. Each ACL includes an action element (permit or deny) and a filter element based on criteria such as source address, destination address, protocol, and protocol-specific parameters.
You can reorder the access lists by clicking the blue up and down arrows on the left side of the Application table. Each time an arrow is clicked, the chosen record moves up or down one row in the Application table and the sequence number is automatically modified based on location in the table relative to other records in the same list.
5.6.8.1 Basic Subtab
The Basic subtab allows you to perform the following tasks:
•Specify an access control list name and sequence number.
•Choose to permit or deny packet matching.
•Choose whether to log matches.
•Specify source and destination traffic matching criteria.
•Specify a remark for the ACL.
The following table describes the Basic subtab fields.
Table 5-56 Field Descriptions for the Basic Subtab
Field
|
Description
|
Basics Area
|
Name field
|
Allows you to enter the name of the ACL.
|
Sequence Number field
|
Allows you to enter the sequence number for the ACL.
The sequence number is the number of the statement in the access list. This number determines the order of the statements in the access list.
|
Grant list
|
Allows you to specify whether packets that match the ACL are permitted or denied. Options are:
•Permit—Packets that match the ACL are permitted.
•Deny—Packets that match the ACL are denied.
|
Logging list
|
Allows you to specify whether to log matches against the input and how the log match is done. A packet is matched for a new flow defined by a combination of the source address, destination address, source port, and destination port. Options are:
•Log—Causes an informational logging message about the packet that matches the entry to be sent to the console. The message includes the access list number, whether the packet was permitted or denied; the protocol, whether it was TCP, UDP, Internet Control Message Protocol (ICMP), or a number; and, if appropriate, the source and destination addresses and source and destination port numbers. The message is generated for the first packet that matches, and then at 5-minute intervals, including the number of packets permitted or denied in the prior 5-minute interval.
•LogInput—Provides the same function as the log, except that the logging message also includes the input interface.
|
Traffic Area
|
Source-any radio button
|
Allows you to use the default value for source IPv4 address matching.
|
Source-address radio button
|
Allows you to specify a source IPv4 address to match.
The source must be the number of the network or host from which the packet is being sent.
|
Source-wildcard field
|
Allows you to enter the wildcard bits to be applied to the source. The wildcard bits are the opposite of the IP address mask. If a bit is zero, it is considered for filtering.
This field is enabled when the Source-address radio button is activated.
|
Destination-any radio button
|
Allows you to use the default value for destination IPv4 address matching.
|
Destination-address radio button
|
Allows you to specify a destination IPv4 address to match.
The destination must be the number of the network or host to which the packet is being sent.
|
Destination-wildcard field
|
Allows you to enter the wildcard bits to be applied to the destination. The wildcard bits are the opposite of the IP address mask. If a bit is zero, it is considered for filtering.
This field is enabled when the address radio button is activated.
|
Remark Area
|
Add remark field
|
Allows you to enter comments or a description of the ACL.
|
5.6.8.2 Advanced Subtab
The Advanced subtab allows you to perform the following tasks:
•Specify an IP protocol the ACL must match.
•Choose to enable or disable Differentiated Services Code Point (DSCP) matching.
•Choose to enable or disable IP precedence matching.
•Specify whether to search for noninitial fragments.
You can reorder the access lists by clicking the blue up and down arrows on the left side of the Application table. Each time an arrow is clicked, the chosen record moves up or down one row in the Application table and the sequence number is automatically modified based on location in the table relative to other records in the same list.
The following table describes the Advanced subtab fields.
Table 5-57 Field Descriptions for the Advanced Subtab
Field
|
Description
|
Advanced Area
|
Protocol list
|
Allows you to choose the IP protocol that the ACL must match. Options are:
•0 (IP)(Default) is the default value. When the Protocol list is set to the 0 (IP)(Default) value on the NE, the 0 (IP)(Default) value will not appear in the running configuration.
•1 (ICMP)
•2 (IGMP)
•3 (GGP)
•4 (IPinIP)
•6 (TCP)
•8 (EGP)
•12 (PUP)
•17 (UDP)
•22 (IDP)
•29 (TP)
•46 (RSVP)
•47 (GRE)
•50 (ESP)
•51 (AHP)
•80 (AHP)
•88 (EIGRP)
•89 (OSPF)
•94 (NOSIP)
•98 (ENCAP)
•103 (PIM)
•108 (PCP)
•115 (L2TPV)
•120 (UTI)
•132 (SCTP)
•255 (RAW)
The integers from 0 to 255 represent an IP protocol number.
|
DSCP or Precedence Area
|
None radio button
|
Allows you to disable DSCP and precedence for the chosen ACL.
|
DSCP
|
Allows you to enable DSCP matching. DSCP provides quality of service (QoS) control.
|
DSCP radio button
|
Allows you to enable DSCP matching.
|
DSCP list
|
Allows you to choose a DSCP reserved keyword to match packets from the list. Options are:
•0—(Cisco default) Default DSCP (000000)
•8 (CS1)—CS1 (precedence 1) DSCP (001000)
•10 (AF11)—AF11 DSCP (001010)
•12 (AF12)—AF12 DSCP (001100)
•14 (AF13)—AF13 DSCP (001110)
•16 (CS2)—CS2 (precedence 2) DSCP (010000)
•18 (AF21)—AF21 DSCP (010010)
•20 (AF22)—AF22 DSCP (010100)
•22 (AF23)—AF23 DSCP (010110)
•24 (CS3)—CS3 (precedence 3) DSCP (011000)
•26 (AF31)—AF31 DSCP (011010)
•28 (AF32)—AF32 DSCP (011100)
•30 (AF33)—AF33 DSCP (011110)
•32 (CS4)—CS4 (precedence 4) DSCP (100000)
•34 (AF41)—AF41 DSCP (100010)
•36 (AF42)—AF42 DSCP (100100)
•38 (AF43)—AF43 DSCP (100110)
•40 (CS5)—CS5 (precedence 5) DSCP (101000)
•46 (EF)—EF DSCP (101110)
•48 (CS6)—CS6 (precedence 6) DSCP (110000)
•56 (CS7)—CS7 (precedence 7) DSCP (111000)
The DSCP radio button must be clicked to enable the DSCP list.
|
Precedence
|
Allows you to enable precedence. Packets can be filtered by precedence level, as specified by a number from 0 to 7, or by name.
|
Precedence radio button
|
Allows you to enable precedence.
|
Precedence list
|
Allows you to choose the precedence level. Options are:
•0 (Routine)
•1 (Priority)
•2 (Immediate)
•3 (Flash)
•4 (Flash Override)
•5 (Critical)
•6 (Internet)
•7 (Network)
The Precedence radio button must be chosen to enable the Precedence list.
|
Check Noninitial Fragments check box
|
Allows you to check for noninitial fragments of IPv4 packets when applying the chosen access list entry.
|
