Table Of Contents
Configuring Hardware
5.1 Overview
5.2 Using the NE Explorer to Configure 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 an SDCC, LDCC, GCC, OSC, or DWDM OSC Termination
5.3.7 Creating a DCC Tunnel Connection
5.3.8 Using SNMP
5.3.9 Specifying the Preferred Copy—ONS 15600 SONET or ONS 15600 SDH
5.3.10 Enabling Intermediate Path Performance Monitoring
5.3.11 Enabling Pointer Justification Count Monitoring for CTC-Based NEs
5.3.12 Changing the Power Monitoring Threshold for the ONS 15454 SONET and ONS 15454 SDH
5.3.13 Creating an Ethernet Threshold
5.4 Configuring the CRS-1
5.4.1 Explicit Path Configuration Application
5.4.2 MPLS-TE Configuration Application
5.4.3 Interface Common Attributes Configuration Application
5.4.4 Interface Ethernet Configuration Application
5.4.5 Interface POS Configuration Application
5.4.6 SONET Port Configuration Application
5.4.7 Access Control Lists Application
5.4.8 Packet Filter Application
5.4.9 QoS Application
5.4.10 Routing Policy Manager Application
5.4.11 BGP Configuration Application
5.4.12 ISIS Configuration Application
5.4.13 LDP Configuration Application
5.4.14 OSPF Configuration Application
5.4.15 Creating an OSPF Instance
5.4.16 Logical Router Instance Tree
5.4.17 Creating an OSPF Area
5.4.18 RSVP Configuration Application
5.4.19 Telnet
5.4.20 SSHv1 and SSHv2
5.4.21 AAA Administration
5.4.22 Alarm Administration
5.4.23 User Administration
5.4.24 Configuring Secure Socket Layer for the CRS-1
5.5 Configuring the ONS 15200
5.6 Configuring the ONS 15216
5.7 Configuring the ONS 15302 and ONS 15305
5.8 Configuring the ONS 15310, ONS 15327, ONS 15454 SONET, and ONS 15454 SDH
5.8.1 Provisioning an ONS 15310, ONS 15327, ONS 15454 SONET, or ONS 15454 SDH Card Slot
5.8.2 Resetting a Card
5.8.3 Deleting a Card
5.8.4 Changing a Card
5.8.5 Inserting an AIS-V on an STS-1 SD-P
5.8.6 Changing Secure Config Mode—ONS 15454 SONET or ONS 15454 SDH
5.9 Configuring the ONS 15501, ONS 15530, and ONS 15540
5.10 Configuring the ONS 15600 SONET and ONS 15600 SDH
5.10.1 Resetting a Card
5.10.2 Deleting a Card
5.10.3 Changing a Card
5.11 Configuring the ONS 15800, ONS 15801, and ONS 15808
5.11.1 Synchronizing the ONS 15800, ONS 15801, and ONS 15808 Configuration and Inventory
5.11.2 Manually Resetting the ONS 15800, ONS 15801, or ONS 15808
5.11.3 Tagging an ONS 15800, ONS 15801, or ONS 15808 Module as Out of Service
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 NEs
•Configuring Routing Protocols on Optical NEs
•Configuring the CRS-1
•Configuring the ONS 15200
•Configuring the ONS 15216
•Configuring the ONS 15302 and ONS 15305
•Configuring the ONS 15310, 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
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 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-21 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, the NE Explorer is menu-based. Use the Configuration and Administration menu options to configure the CRS-1. For details, see Configuring the CRS-1.
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 Complete the fields described in Table 5-1.
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
|
Grey
|
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
•Using OSPF with CTC-Based NEs
•Using RIP
•Creating an SDCC, LDCC, GCC, OSC, or DWDM OSC Termination
•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. Table 5-2 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 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 default is 40 seconds.
•Transit Delay—Service speed. The default is 1 second.
•Retransmit Int—Time that will elapse before a packet is resent. The 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. Table 5-3 provides field 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 default is 1 second.
•Retransmit Interval—Time that will elapse before a packet is resent. The 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. Table 5-4 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 default is 1 second.
|
Retransmit Interval
|
Specify the time that will elapse before a packet is resent. The default is 5 seconds.
|
Hello Interval
|
Specify the number of seconds between OSPF hello packet advertisements. The 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 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, 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.
Note When you enable RIP, wait for approximately one minute for the default RIP address to become visible.
•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 GNE with multiple external NEs attached with IP addresses in different subnets.
b. The Create RIP Address Summary dialog box opens and allows you to create aggregate addresses that are 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, 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 an SDCC, LDCC, GCC, OSC, or DWDM OSC Termination
The Create SDCC/LDCC/GCC/OSC dialog box allows you to create new terminations 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 property sheet of the NE Explorer, click one of the following tabs. Tabs shown depend on the type of NE selected.
•DCC
•DCC/GCC/OSC
•LDCC
•SDCC
Step 3 Click the subtab that corresponds to the termination that you want to create. For example, to create an LDCC termination, click the LDCC subtab.
Step 4 Click Create. The Create dialog box opens. Table 5-6 provides descriptions.
Note The fields shown in the Create dialog box depend on the type of termination that is being created. The fields shown also depend on the NE type. The title of the dialog box changes depending on your selection.
Step 5 After making your selections, click OK.
Table 5-6 Field Descriptions for the Create Dialog Box
Tab
|
Description
|
SDCC Terminations
|
Select the slot and port for an SDCC termination.
|
LDCC Terminations
|
Select the slot and port for an LDCC termination.
|
GCC Terminations
|
Select the slot and port for a GCC termination.
|
OSC Terminations
|
Select the slot and port for an OSC termination.
|
OSPF Disabled on Link
|
Check if you want to prevent the advertisement of the OSPF routing table.
|
State
|
Select the state of the DCC termination: IS (In Service), OOS (Out of Service), OOS-MT (Out of Service-Maintenance), or OOS-AINS (Out of Service-Auto In Service).
|
GCC Rate
|
Select the GCC rate.
|
5.3.7 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 property sheet 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. Table 5-7 provides descriptions.
Step 5 After making your selections, click OK.
Table 5-7 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.8 Using SNMP
5.3.8.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 most SNMP interfaces have.
5.3.8.2 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. Table 5-8 provides descriptions.
Table 5-8 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-9 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.
Table 5-9 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-9 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.8.3 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-9 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.8.4 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.8.5 Creating an SNMP Trap Destination—ONS 15216 EDFA2
Use the Create SNMP Trap Destination dialog box to create new SNMP trap destinations for ONS 15216 EDFA2 NEs.
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. Table 5-10 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-10 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 UDP port for SNMP.
|
Community Name
|
Type the SNMP community name.
|
Version
|
Enter the trap version number.
|
5.3.8.6 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.8.7 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.8.8 Creating an SNMP View—ONS 15216 EDFA2
Use the Create SNMP View dialog box to create new SNMP views for ONS 15216 EDFA2 NEs.
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. Table 5-11 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-11 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.8.9 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.8.10 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.8.11 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-12 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-12 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.8.12 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.8.13 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.9 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.10 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.
To enable IPPM for CTC-based 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 Select an LTE card. See Table 5-13 for a list of LTE cards.
Table 5-13 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.11 Enabling Pointer Justification Count Monitoring for CTC-Based 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-13 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.12 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.13 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. Table 5-14 provides descriptions.
Step 5 After making your selections, click OK.
Step 6 Click Apply.
Table 5-14 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 may 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 Configuring the CRS-1
This section explains the NE Explorer menu options used to configure the CRS-1.
5.4.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.
Table 5-15 describes the explicit path application fields.
Table 5-15 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, then 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, then click Remove to remove the IP address from the explicit path.
|
5.4.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.4.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.
Table 5-16 describes the Global tab fields.
Table 5-16 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.
|
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.4.2.2 Labels Tab
The Labels tab allows you to configure the range of local labels.
Table 5-17 describes the Labels tab fields.
Table 5-17 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.4.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.4.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.
Table 5-18 describes the General subtab fields.
Table 5-18 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.4.2.3.2 Backup Tunnels Subtab
The Backup Tunnels subtab allows you to specify the backup tunnels for the link.
Table 5-19 describes the Backup Tunnels subtab fields.
Table 5-19 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.4.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.4.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.
Table 5-20 describes the General subtab fields.
Table 5-20 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 shutdown a tunnel, protecting the interface. When this tunnel is down (shutdown 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.4.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).
Table 5-21 describes the Advanced subtab fields.
Table 5-21 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 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
|
Allow 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.4.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.
Table 5-22 describes the Path Selections subtab fields.
Table 5-22 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.4.2.5 Operations Tab
The Operations tab allows you to perform the following tasks:
•Reoptimize tunnels.
•Reset counters.
Table 5-23 describes the Operations tab fields.
Table 5-23 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.4.3 Interface Common Attributes Configuration Application
The Interface Common Attributes Configuration Application contains the following tabs:
•General Tab
•Operation 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.
5.4.3.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).
Table 5-24 describes the General tab fields.
Table 5-24 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 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.
|
5.4.3.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.
Table 5-25 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-25 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 may 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.4.3.1.2 Dampening Subtab
Currently, a router with an unstable data link (also known as a link flap) may 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.
Table 5-26 describes the Dampening subtab fields.
Table 5-26 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.4.3.2 Operation Tab
The Operation tab allows you to manually shutdown the interface.
Table 5-27 describes the Operation tab field.
Table 5-27 Field Descriptions for the Operation Tab
Field
|
Description
|
Shutdown check box
|
Allows you to shutdown the interface. Shutdown administratively brings down an interface.
|
5.4.4 Interface Ethernet Configuration Application
The Interface Ethernet Configuration Application contains the following tabs:
•General Tab
•Ethernet Tab
•Operation 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.4.4.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).
Table 5-28 describes the General tab fields.
Table 5-28 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.
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.4.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.
Table 5-29 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-29 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 may 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 User Datagram Protocol (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.4.4.1.2 Dampening Subtab
Currently, a router with an unstable data link (also known as link flap) may 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.
Table 5-30 describes the Dampening subtab fields.
Table 5-30 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.4.4.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.
Table 5-31 describes the Ethernet tab fields.
Table 5-31 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.4.4.3 Operation Tab
The Operation tab allows you to manually shutdown the interface.
Table 5-32 describes the Operation tab field.
Table 5-32 Field Descriptions for the Operation Tab
Field
|
Description
|
Shutdown check box
|
Allows you to shutdown the Ethernet interface. Shutdown administratively brings down an interface.
|
5.4.5 Interface POS Configuration Application
The Interface POS Configuration Application contains the following tabs:
•General Tab
•POS Tab
•Operation 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 transmission for data. Reliable data transfer depends on timing integrity.
The real-time POS functionality is 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.4.5.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).
Table 5-33 describes the General tab fields.
Table 5-33 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.
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.4.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.
Table 5-34 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 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 may 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 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.4.5.1.2 Dampening Subtab
Currently, a router with an unstable data link (also known as link flap) may 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.
Table 5-35 describes the Dampening subtab fields.
Table 5-35 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.4.5.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.
Table 5-36 describes the POS tab fields.
Table 5-36 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—High-Level Data Link Controller. ISO communications protocol used in X.25 packet switching networks.
|
5.4.5.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.
Table 5-37 describes the PPP Common subtab fields.
Table 5-37 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.4.5.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.
Table 5-38 describes the PAP subtab fields.
Table 5-38 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.4.5.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.
Table 5-39 describes the CHAP subtab fields.
Table 5-39 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.4.5.3 Operation Tab
The Operation tab allows you to manually shutdown the interface.
Table 5-40 describes the Operation tab field.
Table 5-40 Field Descriptions for the Operation Tab
Field
|
Description
|
Shutdown check box
|
Allows you to shutdown the POS interface. Shutdown administratively brings down an interface.
|
5.4.6 SONET Port Configuration Application
The SONET Port Configuration Application contains the following tabs:
•SONET Tab
•Operation Tab
The SONET Port Configuration application allows you to configure the SONET on a router port using Layer 1 SONET transport technology.
5.4.6.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.4.6.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.
Table 5-41 describes the SONET Configuration subtab fields.
Table 5-41 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—Specifies that the controller will clock its sent data from a clock recovered from the receive data stream of the line.
|
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—Chooses SONET framing.
•SDH—Chooses synchronous digital hierarchy (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 Synchronous Digital Hierarchy (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.
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.4.6.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.
Table 5-42 describes the Alarm Reporting subtab fields.
Table 5-42 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.4.6.2 Operation Tab
The Operation tab allows you to enable shutdown on the chosen interface.
Table 5-43 describes the Operation tab field.
Table 5-43 Field Descriptions for the Operation Tab
Field
|
Description
|
Shutdown check box
|
Allows you to shutdown the interface. Shutdown administratively brings down an interface (shuts down the SONET controller and disables SONET controller processing).
|
5.4.7 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.4.7.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.
Table 5-44 describes the Basic subtab fields.
Table 5-44 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, User Datagram Protocol (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, then 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, then 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.4.7.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.
Table 5-45 describes the Advanced subtab fields.
Table 5-45 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)
•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 (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 chosen 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.
|
5.4.7.3 TCP/UDP/SCTP Subtab
The TCP/UDP/SCTP subtab allows you to perform the following tasks:
•Specify the source port comparison criteria.
•Specify the destination port comparison criteria.
•Choose a TCP flag.
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.
Table 5-46 describes the TCP/UDP/SCTP subtab fields.
Table 5-46 Field Descriptions for the TCP/UDP/SCTP Subtab
Field
|
Description
|
Source Port Area
|
operator list
|
Allows you to choose the source comparison operator, which compares source or destination ports. Options are:
•Equal—You must enter a value for the start parameter.
•Great Than—You must enter a value for the start parameter.
•Less Than—You must enter a value for the start parameter.
•Not Equal—You must enter a value for the start parameter.
•Range—You must enter values for the start and end parameters.
This list becomes available when 6 (TCP), 17 (UDP), or 132 (SCTP) is chosen in the Protocol list in the Advanced subtab. (See Advanced Subtab.)
|
start field
|
Allows you to enter the first source port for comparison.
This list becomes available when 6 (TCP), 17 (UDP), or 132 (SCTP) is chosen in the Protocol list in the Advanced subtab (see Advanced Subtab) and an operator is chosen in the operator list in the Source Port area of the TCP/UDP/SCTP tab.
|
start-TCP/SCTP list
|
Allows you to choose a TCP port. This list is available when the start field is empty.
TCP port names can be used only when filtering TCP.
This list becomes available when 6 (TCP) or 132 (SCTP) is chosen in the Protocol list in the Advanced subtab (see Advanced Subtab) and an operator is chosen in the operator list in the Source Port area of the TCP/UDP/SCTP tab.
|
start-UDP list
|
Allows you to choose a UDP port.
UDP port names can be used only when filtering UDP.
This list becomes available when 17 (UDP) is chosen in the Protocol list in the Advanced Subtab (see Advanced Subtab) and an operator is chosen in the operator list in the Source Port area of the TCP/UDP/SCTP tab.
|
end field
|
Allows you to enter the second source port for comparison. Only enter a value in the end field if comparing a range of TCP, SCTP, or UDP ports.
This list becomes available when 6 (TCP), 17 (UDP), or 132 (SCTP) is chosen in the Protocol list in the Advanced subtab (see Advanced Subtab) and Range is chosen for the operator list in the Source Port area of the TCP/UDP/SCTP tab.
|
end-TCP/SCTP list
|
Allows you to choose a TCP port. This list is available when the end field is empty.
TCP port names can be used only when filtering TCP.
This list becomes available when 6 (TCP) or 132 (SCTP) is chosen in the Protocol list in the Advanced subtab (see Advanced Subtab) and Range is chosen for the operator list in the Source Port area of the TCP/UDP/SCTP tab.
|
end-UDP list
|
Allows you to choose a UDP port. This list is available when the end field is empty.
UDP port names can be used only when filtering UDP.
This list becomes available when 17 (UDP) is chosen in the Protocol list in the Advanced subtab (see Advanced Subtab) and Range is chosen for the operator list in the Source Port area of the TCP/UDP/SCTP tab.
|
Destination Port Area
|
operator list
|
Allows you to choose the source comparison operator, which compares source or destination ports. Options are:
•Equal—You must enter a value for the start parameter.
•Great Than—You must enter a value for the start parameter.
•Less Than—You must enter a value for the start parameter.
•Not Equal—You must enter a value for the start parameter.
•Range—You must enter values for the start and end parameters.
This list becomes available when 6 (TCP), 17 (UDP), or 132 (SCTP) is chosen in the Protocol list in the Advanced subtab. (See Advanced Subtab.)
|
start field
|
Allows you to enter the first source port for comparison.
This list becomes available when 6 (TCP), 17 (UDP), or 132 (SCTP) is chosen in the Protocol list in the Advanced subtab (see Advanced Subtab) and an operator is chosen in the operator list in the Source Port area of the TCP/UDP/SCTP tab.
|
start-TCP/SCTP list
|
Allows you to choose a TCP port. This list is available when the start field is empty.
TCP port names can be used only when filtering TCP.
This list becomes available when 6 (TCP) or 132 (SCTP) is chosen in the Protocol list in the Advanced subtab (see Advanced Subtab) and an operator is chosen in the operator list in the Source Port area of the TCP/UDP/SCTP tab.
|
start-UDP list
|
Allows you to choose a UDP port.
UDP port names can be used only when filtering UDP.
This list becomes available when 17 (UDP) is chosen in the Protocol list in the Advanced Subtab (see Advanced Subtab) and an operator is chosen in the operator list in the Source Port area of the TCP/UDP/SCTP tab.
|
end field
|
Allows you to enter the second source port for comparison. Only enter a value in the end field if comparing a range of TCP, SCTP, or UDP ports.
This list becomes available when 6 (TCP), 17 (UDP), or 132 (SCTP) is chosen in the Protocol list in the Advanced subtab (see Advanced Subtab) and Range is chosen for the operator list in the Source Port area of the TCP/UDP/SCTP tab.
|
end-TCP/SCTP list
|
Allows you to choose a TCP port. This list is available when the end field is empty.
TCP port names can be used only when filtering TCP.
This list becomes available when 6 (TCP) or 132 (SCTP) is chosen in the Protocol list in the Advanced subtab (see Advanced Subtab) and Range is chosen for the operator list in the Source Port area of the TCP/UDP/SCTP tab.
|
end-UDP list
|
Allows you to choose a UDP port. This list is available when the end field is empty.
UDP port names can be used only when filtering UDP.
This list becomes available when 17 (UDP) is chosen in the Protocol list in the Advanced subtab (see Advanced Subtab) and Range is chosen for the operator list in the Source Port area of the TCP/UDP/SCTP tab.
|
TCP Only Area
|
TCP Flags
Established check box
|
Allows you to enable an established connection. A match occurs if the TCP datagram has the ACK.
When the Established check box is checked, the ACK and RST check boxes are activated by default.
Checking any of the following check boxes enables matching of the bits:
•ACK—Acknowledgment bit set
•RST—Reset bit set
•SYN—Synchronize bit set
•FIN—Fin bit set; no more data from sender
•PSH—Push function bit set
A match occurs if the TCP datagram has any of the checked bits sets.
|
5.4.7.4 ICMP/IGMP Subtab
The ICMP/IGMP subtab allows you to perform the following tasks:
•Specify the ICMP message type.
•Specify the IGMP message type.
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.
Table 5-47 describes the ICMP/IGMP subtab fields.
Table 5-47 Field Descriptions for the ICMP/IGMP Subtab
Field
|
Description
|
ICMP Area
|
ICMP Message Type field
|
Allows you to enter an ICMP message type for filtering ICMP packets. ICMP packets can be filtered by ICMP message type.
This field is activated when ICMP is the chosen Protocol in the Advanced subtab. (See Advanced Subtab.)
|
ICMP Message Code field
|
Allows you to enter an ICMP message code for filtering ICMP packets. ICMP packets that are filtered by ICMP message type can also be filtered by the ICMP message code.
|
IGMP Area
|
IGMP Message Type field
|
Allows you to enter an ICMP message type for filtering ICMP packets. ICMP packets can be filtered by ICMP message type.
This field is activated when ICMP is the chosen Protocol in the Advanced subtab. (See Advanced Subtab.)
|
5.4.8 Packet Filter Application
The Packet Filter application allows you to control which access control lists (ACLs) are applied to specific interfaces.
The Packet Filter application allows you to perform the following tasks:
•Add an ACL to inbound or outbound traffic on one or more interfaces.
•Remove currently configured ACLs from one or more interfaces.
Table 5-48 Field Descriptions for the Packet Filter Application
Field
|
Description
|
Packet Filter Area
|
Inbound
|
Allows you to choose the inbound packet filter (ACL).
|
Inbound field
|
Allows you to view the ACL chosen using the Select ACL dialog box.
|
Inbound ellipsis button
|
Allows you to choose an ACL from the Select ACL dialog box.
|
Inbound-Count packets in hardware check box
|
Allows you to enable inbound hardware packet counting.
|
Outbound
|
Allows you to choose the outbound packet filter (ACL).
|
Outbound field
|
Allows you to view the ACL chosen using the Select ACL dialog box.
|
Outbound ellipsis button
|
Allows you to choose an ACL from the Select ACL dialog box.
|
Outbound-Count packets in hardware check box
|
Allows you to enable a outbound hardware packet counting.
|
5.4.9 QoS Application
The QoS Application contains the following tabs:
•Classmaps Tab
•Policymaps Tab
•Service Policies Tab
Quality of service (QoS) is a measure of performance for a transmission system that reflects its transmission quality and service availability. QoS efficiently applies network resources to ensure that the greatest breadth of applications can be properly supported while still enabling packet networks to achieve the high levels of utilization essential for enabling profitability.
The QoS application allows you to configure class maps and policy maps, and apply the policy maps to the inbound and outbound traffic on interfaces.
The policy map specifies the traffic policy name and configures a traffic policy. The class map is used for matching packets to a specific class.
5.4.9.1 Classmaps Tab
The Classmaps tab allows you to perform the following tasks:
•Specify a class map name.
•Configure the match settings for the chosen class map.
Table 5-49 describes the Classmaps tab fields.
Table 5-49 Field Descriptions for the Classmaps Tab
Field
|
Description
|
Basics area
|
Name field
|
Allows you to enter the name of the class map for which you want to create or modify class map match criteria. Packets arriving at the interface are checked against the match criteria configured for a class map to determine if the packet belongs to that class.
The class map is used for matching packets to the class whose name you specify.
The name entered in the Name field is used for the class map and for configuring the policy for the class in the policy map.
|
Match Settings Area
|
Match Any check box
|
Allows you to configure the match criteria for a class map to match any. When the Match Any check box is checked, the class map will match all packets (equivalent to the default class).
Match Any specifies that the remaining traffic (after the other match criteria set in the Match Settings area are met) is considered to belong to the class specified by the class map.
|
Match IPv4 Access Group(s)
|
Allows you to choose the match criteria for a class map based on the specified access control lists (ACLs). The Match IPv4 Access Group(s) parameter specifies the ACLs whose contents are used as the match criteria against which packets are checked to determine if they belong to the class specified by the class map.
|
Match IPv4 Access Group(s) field
|
Allows you to view the match criteria chosen using the Select ACL(s) dialog box.
|
Match IPv4 Access Group(s) ellipsis button
|
Allows you to choose the match criteria from the Select ACL(s) dialog box.
|
Match IPv4 DSCP(s)
|
Allows you to choose the IP DSCP values as match criteria for a class map.
This feature examines the higher order 6 bits in the type of service (ToS) byte of the IP header. Up to eight IP Differentiated Services Code Point (DSCP) values can be matched in one match statement. For example, if you wanted the IP DCSP values of 0, 1, 2, 3, 4, 5, 6, and 7 (note that only one of the IP DSCP values must be a successful match criterion, not all of the specified IP DSCP values), enter the match IP DSCP values.
The IP DSCP value is used as a matching criterion only. The value has no mathematical significance. For instance, the IP DSCP value 2 is not greater than 1. The value simply indicates that a packet marked with the DSCP of 2 should be treated differently from a packet marked with a DSCP value of 1. The treatment of these marked packets is defined by the user through the setting of QoS policies.
|
Match IPv4 DSCP(s) field
|
Allows you to view the match criteria chosen using the Select IP DSCP(s) dialog box.
|
Match IPv4 DSCP(s) ellipsis button
|
Allows you to choose the match criteria from the Select IP DSCP(s) dialog box.
|
Match IPv4 Precedence(s)
|
Allows you to choose the IP precedences as match criteria for a class map. This feature examines the higher order 3 bits in the ToS byte of the IP header. Up to four precedences can be matched in one match statement. For example, if you wanted the IP precedences of Routine, Flash, and Internet (note that only one of the IP precedences must be a successful match criterion, not all of the specified IP precedences), enter the match IP precedences.
|
Match IPv4 Precedence(s) field
|
Allows you to view the match criteria chosen using the Select IP Precedence(s) dialog box.
|
Match IPv4 Precedence(s) ellipsis button
|
Allows you to choose the match criteria from the Select IP Precedence(s) dialog box.
Choose a precedence from the Configured IP Precedence(s) list and click Add>> to move it to the Selected IP Precedence(s) list. You can choose multiple precedences. Options are:
•Routine
•Priority
•Immediate
•Flash
•Flash Override
•Critical
•Internet
•Network
|
Match Protocol
|
Allow you to choose the protocols as match criteria for a class map.
|
Match Protocol field
|
Allows you to view the match criteria chosen using the Select IP Protocol(s) dialog box.
|
Match Protocol ellipsis button
|
Allows you to choose the match criteria from the Select IP Protocol(s) dialog box.
|
Match QoS Group
|
Allows you to choose the QoS group values in a class map to match packets.
This feature is used to set the match criteria for examining QoS groups marked on the packet. Up to eight QoS group values can be matched in one match statement. For example, match QoS group 1 2 3 4 5 6 7 returns matches for QoS group variables 1, 2, 3, 4, 5, 6, and 7. Only one of the QoS group values must be a successful match criterion, not all of the specified QoS group values.
The QoS group value is used as a matching criterion only. The value has no mathematical significance. For instance, the QoS group value 2 is not greater than 1. The value simply indicates that a packet marked with the QoS group of 2 should be treated differently from a packet marked with a QoS group value of 1. The treatment of these different packets is defined using the policy map service policy configuration features.
|
Match QoS Group field
|
Allows you to view the match criteria chosen using the Select QoS Group(s) dialog box.
|
Match QoS Group ellipsis button
|
Allows you to choose the match criteria from the Select QoS Group(s) dialog box.
|
Match MPLS EXP topmost(s)
|
Allows you to configure a class map so that the three-bit experimental field in the top-most MPLS labels is examined for experimental (EXP) field values.
This feature is used by the class map to identify Multiprotocol Label Switching (MPLS) experimental value matching on a packet.
Up to four EXP values can be matched in one match statement. For example, if you wanted the EXP values of 0, 1, 2, and 3 (note that only one of the EXP values must be a successful match criterion, not all of the specified EXP values), enter the match MPLS experimental topmost 0 1 2 3 values.
The EXP value is used as a matching criterion only. The value has no mathematical significance. For instance, the EXP value 2 is not greater than 1. The value simply indicates that a packet marked with the EXP value of 2 is different from a packet marked with the EXP value of 1. The treatment of these different packets is defined by the user through the setting of policy map QoS configuration features.
|
Match MPLS EXP topmost(s) field
|
Allows you to view the match criteria chosen using the Select MPLS Experimental Topmost(s) dialog box.
|
Match MPLS EXP topmost(s) ellipsis button
|
Allows you to choose the match criteria from the Select MPLS Experimental Topmost(s) dialog box.
|
Match Discard Class(es)
|
Allows you to use specified discard class values in a class map to match packets.
This feature is used to set the match criteria for examining discard classes marked on the packet. Up to eight discard class values can be matched in one match statement. For example, match discard class 0 1 2 3 4 5 6 7 returns matches for discard class variables 0, 1, 2, 3, 4, 5, 6, and 7. Only one of the discard class values must be a successful match criterion, not all of the specified discard class values.
The discard class value is used as a matching criterion only. The value has no mathematical significance. For instance, the discard class value 2 is not greater than 1. The value simply indicates that a packet marked with the discard class of 2 should be treated differently from a packet marked with a discard class value of 1.
|
Match Discard Class(es) field
|
Allows you to view the match criteria chosen using the Select Discard Class(s) dialog box.
|
Match Discard Class(es) ellipsis button
|
Allows you to choose the match criteria from the Select Discard Class(s) dialog box.
|
5.4.9.2 Policymaps Tab
The Policymaps tab contains five subtabs: Congestion Mgmt, Congestion Avoidance, Police (traffic/conform), Policy (exceed/violate), and Mark. The Congestion Mgmt subtab is displayed by default when the Policymaps tab is clicked.
The Policymaps tab allows you to perform the following tasks:
•Specify a policy map name and sequence number.
•Specify an associated class maps name.
•Configure the congestion management parameters.
•Configure the congestions avoidance parameters.
•Configure the traffic conform, exceed, and violate parameters.
•Configure the mark parameters.
You can recorder the class maps 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.
Table 5-50 describes the Policymaps tab fields.
Table 5-50 Field Descriptions for the Policymaps Tab
Field
|
Description
|
Basics Area
|
Name field
|
Allows you to enter the name of the policy map that can be attached to one or more interfaces to specify a service policy.
A single policy map can be attached to multiple interfaces concurrently. When you attempt to attach a policy map to an interface, the attempt is denied if the available bandwidth on the interface cannot accommodate the total bandwidth requested by class policies comprising the policy map. In this case, any policy map already attached to other interfaces is removed.
|
Sequence Number field
|
Allows you to enter the ordering index for the policy map.
|
Classmap Name field
|
Allows you to enter the name of the class map. The name must be unique among all the ordering indexes for the policy map.
The name is used to configure the policy for the class in the policy map.
|
5.4.9.2.1 Congestion Mgmt Subtab
The Congestion Mgmt subtab allows you to perform the following tasks:
•Specify the shape average parameters.
•Specify the bandwidth parameters.
•Specify the priority parameters.
The bandwidth and priority parameters are used to calculate the total bandwidth available on an interface.
Note Specifying the queue limit is especially important for higher-speed interfaces, in order to meet the minimum bandwidth guarantees required by the interface.
Table 5-51 describes the Congestion Mgmt subtab fields.
Table 5-51 Field Descriptions for the Congestion Mgmt Subtab
Field
|
Description
|
Shape Average check box
|
Enables shape averaging. Shape averaging allows you to shape traffic to the specified bit rate.
|
kbps
|
Allows you to enter the shape average in kilobits per second. The minimum rate is 128 kilobits per second and the rates are in multiples of 128 kilobits per second.
|
kbps radio button
|
Allows you to specify the shape average in kilobits per second.
|
kbps field
|
Allows you to enter the shape average in kilobits per second. The kilobits per second radio button must be chosen to enable the kilobits per second field.
|
percent
|
Allows you to specify average or peak-rate traffic shaping on the basis of a percentage of bandwidth available on an interface.
Specifying the shape average using percent calculates the committed information rate (CIR) based on a percentage of the available bandwidth on the interface. Once a policy map is attached to the interface, the equivalent CIR value in bits per second (bps) is calculated based on the interface bandwidth and the percent value entered. If the CIR percentage is changed after the policy map is attached to the interface, the bps value of the CIR is recalculated.
|
percent radio button
|
Allows you to specify the shape average as a percentage.
|
percent field
|
Allows you to enter the shape average as a percentage. The percent radio button must be chosen to enable the percent field.
|
Bandwidth check box
|
Allows you to enable the configuring of the bandwidth allocated for a class belonging to a policy map.
Bandwidth configuration is used to configure guaranteed bandwidth for a class. When bandwidth is configured, traffic belonging to the class is guaranteed that much bandwidth even during congestion.
|
kbps
|
Allows you to enter the amount of bandwidth, in kilobits per second, to be assigned to the class.
The amount of bandwidth varies according to the interface.
|
kbps radio button
|
Allows you to specify the bandwidth in kilobits per second.
|
kbps field
|
Allows you to enter the bandwidth in kilobits per second. The kilobits per second radio button must be chosen to enable the kilobits per second field.
|
percent
|
Allows you to enter the amount of guaranteed bandwidth, based on an absolute percent of available bandwidth.
During periods of congestion, the classes are serviced in proportion to their configured bandwidth percentages. Available bandwidth is equal to the interface bandwidth minus the sum of all bandwidths reserved by the low latency queueing (LLQ) feature.
|
percent radio button
|
Allows you to specify the bandwidth as a percentage.
|
percent field
|
Allows you to enter the bandwidth as a percentage. The percent radio button must be chosen to enable the percent field.
|
priority radio button
|
Allows you to give priority to a class of traffic belonging to a policy map.
Priority configures LLQ, providing strict priority queueing (PQ). Strict PQ allows delay-sensitive data such as voice to be dequeued and sent before packets in other queues are dequeued.
The Bandwidth and Priority cannot be used in the same class, within the same policy map, but they can be used together in the same policy map. Within a policy map, you can give one or more classes priority status. When multiple classes within a single policy map are configured as priority classes, all traffic from these classes is queued to the same, single priority queue.
When the policy map containing class policy configurations is attached to the interface to stipulate the service policy for that interface, available bandwidth is assessed. If a policy map cannot be attached to a particular interface because of insufficient interface bandwidth, the policy is removed from all interfaces to which it was attached.
|
Queue limit (bytes) field
|
Allows you to enter the maximum number of bytes the queue can hold for a class policy configured in a policy map.
Packets satisfying the match criteria for a class accumulate in the queue reserved for the class until they are sent, which occurs when the queue is serviced by the fair queueing process. When the maximum byte threshold you defined for the class is reached, enqueueing of any further packets to the class queue causes tail drop.
|
Service Policy field
|
Allows you to enter the name of the service policy map. When a service policy map is entered, the policy map is attached to an input interface or output interface.
|
5.4.9.2.2 Congestion Avoidance Subtab
The Congestion Avoidance subtab allows you to specify the random detection parameters.
Table 5-52 describes the Congestion Avoidance subtab fields.
Table 5-52 Field Descriptions for the Congestion Avoidance Subtab
Field
|
Description
|
Discard Class
|
Allows you to choose the discard class and set the thresholds for the discard class.
|
Discard Class field
|
Allows you to view the discard class chosen using the Select Discard Classes and Bandwdith(s) dialog box.
|
Discard Class ellipsis button
|
Allows you to choose the discard class and thresholds from the Select Discard Classes and Bandwidth(s) dialog box.
Enter the minimum threshold for the discard class in the Minimum threshold (bytes) field and the maximum threshold for the discard class in the Maximum threshold (bytes) field. Then choose a discard class value.
|
IP DSCP
|
Allows you to choose the IP DSCP and set the thresholds for the DSCP.
|
IP DSCP field
|
Allows you to view the IP DSCP chosen using the Select DSCPs and Bandwidth(s) dialog box.
|
IP DSCP ellipsis button
|
Allows you to choose the IP DSCP and thresholds from the Select DSCPs and Bandwidth(s) dialog box.
Enter the minimum threshold for the DSCP in the Minimum threshold (bytes) field and the maximum threshold for the DSCP in the Maximum threshold (bytes) field. Then choose a DSCP reserved keyword.
|
IP Precedence
|
Allow you to choose the IP precedence and set the thresholds for the IP precedence.
|
IP Precedence field
|
Allows you to view the IP precedence chosen using the Select IP Precedences and Bandwidth(s) dialog box.
|
IP Precedence ellipsis button
|
Allows you to choose the IP precedence and thresholds from the Select IP Precedences and Bandwidth(s) dialog box.
Enter the minimum threshold for the IP precedence in the Minimum threshold (bytes) field and the maximum threshold for the IP precedence in the Maximum threshold (bytes) field. Then choose an IP precedence value.
|
MPLS EXP topmost
|
Allows you to choose the MPLS EXP topmost value and set the thresholds for the MPLS experimental topmost value.
|
MPLS EXP topmost field
|
Allows you to view the MPLS EXP topmost value chosen using the Select MPLS EXP topmost and Bandwidth(s) dialog box.
|
MPLS EXP topmost ellipsis button
|
Allows you to choose the MPLS EXP topmost value and thresholds from the Select MPLS EXP topmost and Bandwidth(s) dialog box.
Enter the minimum threshold for the MPLS EXP topmost in the Minimum threshold (bytes) field and the maximum threshold for the MPLS EXP topmost in the Maximum threshold (bytes) field. Then choose an MPLS EXP topmost value.
|
5.4.9.2.3 Police (traffic/conform) Subtab
The Police (traffic/conform) subtab allows you to mark packets with different QoS values based on conformance to the service-level agreement. Traffic policing is not executed for traffic that passes through an interface.
The Police (traffic/conform) subtab allows you to perform the following tasks:
•Specify traffic parameters such as rate of traffic and burst size.
•Set the conform action criteria.
Table 5-53 describes the Police (traffic/conform) subtab fields.
Table 5-53 Field Descriptions for the Police (traffic/conform) Subtab
Field
|
Description
|
Traffic Area
|
No CIR radio button
|
Allows you to choose to not configure a committed information rate.
|
CIR (kb/sec) radio button
|
Allows you to choose to specify a committed information rate in kilobytes per second.
|
CIR (kb/sec) field
|
Allows you to enter a committed information rate (CIR) value.
|
CIR (%) radio button
|
Allows you to choose to specify a CIR as a percentage.
|
CIR (%)
|
Allows you to enter a CIR percentage.
|
Burst Size (kb/sec) field
|
Allows you to enter the sustained number of bits that can be sent per interval.
|
Excess Burst Size (kb/sec) field
|
Allows you to enter the maximum number of bits that can exceed the burst size in the first interval in a congestion event.
|
Conform Area
|
Transmit radio button
|
Allows you to set the conform action to transmit. Conform is the action to take on packets that conform to the rate limit. The packets are sent with no alteration.
|
Set MPLS EXP topmost
|
Allows you to set the conform action to MPLS EXP topmost and choose the MPLS EXP topmost value.
|
Set MPLS EXP topmost radio button
|
Allows you to set the conform action to MPLS experimental topmost.
|
Set MPLS EXP topmost list
|
Allows you to choose the MPLS experimental topmost value.
The Set MPLS EXP topmost list sets the MPLS experimental bits from 0 to 7 and sends the packet with the new MPLS experimental bit value setting.
The Set MPLS EXP topmost radio button must be chosen to enable the Set MPLS EXP topmost list.
|
Set Discard Class
|
Allows you to set the conform action to Discard Class and choose a valid discard class value.
|
Set Discard Class radio button
|
Allows you to set the conform action to Discard Class.
|
Set Discard Class list
|
Allows you to choose the Discard Class value.
The Set Discard Class list sets the discard class attribute of a packet and sends the packet with the new discard class setting.
The Set Discard Class radio button must be chosen to enable the Set Discard Class list.
|
Set IP Precedence
|
Allows you to set the conform action to IP Precedence and choose a valid IP precedence value.
|
Set IP Precedence radio button
|
Allows you to set the conform action to IP Precedence.
|
Set IP Precedence list
|
Allows you to choose the IP precedence value. Options are:
•Routine
•Priority
•Immediate
•Flash
•Flash Override
•Critical
•Internet
•Network
The Set IP Precedence list sets the IP precedence and sends the packet with the new IP precedence value setting.
The Set IP Precedence radio button must be chosen to enable the Set IP Precedence list.
|
Set IP DSCP
|
Allows you to set the conform action to IP DSCP and choose a valid IP DSCP value.
|
Set IP DSCP radio button
|
Allows you to set the conform action to IP DSCP.
|
Set IP DSCP list
|
Allows you to choose the IP DSCP value.
The Set IP DSCP list sets the DSCP value and sends the packet with the new DSCP value setting.
The Set IP DSCP radio button must be chosen to enable the Set IP DSCP list.
|
5.4.9.2.4 Police (exceed/violate) Subtab
The Police (exceed/violate) subtab allows you to mark packets with different QoS values based on conformance to the service-level agreement. Traffic policing is not executed for traffic that passes through an interface.
The Police (exceed/violate) subtab allows you to perform the following tasks:
•Specify the traffic exceed parameters.
•Specify the traffic violate parameters.
Table 5-54 describes the Police (exceed/violate) subtab fields.
Table 5-54 Field Descriptions for the Police (exceed/violate) Subtab
Field
|
Description
|
Exceed Area
|
Drop radio button
|
Allows you to set the exceed action to drop. Drop means that the packets are dropped when they exceed the rate limit.
|
Set MPLS EXP topmost
|
Allows you to set the exceed action to MPLS EXP topmost and choose the MPLS EXP topmost value.
|
Set MPLS EXP topmost radio button
|
Allows you to set the exceed action to MPLS EXP topmost.
|
Set MPLS EXP topmost list
|
Allows you to choose the MPLS EXP topmost value.
The Set MPLS EXP topmost list sets the MPLS experimental bits from 0 to 7 and sends the packet with the new MPLS experimental bit value setting.
The Set MPLS EXP topmost radio button must be chosen to enable the Set MPLS EXP topmost list.
|
Set Discard Class
|
Allows you to set the exceed action to discard class and choose a valid discard class value.
|
Set Discard Class radio button
|
Allows you to set the exceed action to Discard Class.
|
Set Discard Class list
|
Allows you to choose the Discard Class value.
The Set Discard Class list sets the discard class attribute of a packet and sends the packet with the new discard class setting.
The Set Discard Class radio button must be chosen to enable the Set Discard Class list.
|
Set IP Precedence
|
Allows you to set the exceed action to IP Precedence and choose a valid IP precedence value.
|
Set IP Precedence radio button
|
Allows you to set the exceed action to IP precedence.
|
Set IP Precedence list
|
Allows you to choose the IP precedence value. Options are:
•Routine
•Priority
•Immediate
•Flash
•Flash Override
•Critical
•Internet
•Network
The Set IP Precedence list sets the IP precedence and sends the packet with the new IP precedence value setting.
The Set IP Precedence radio button must be chosen to enable the Set IP Precedence list.
|
Set IP DSCP
|
Allows you to set the exceed action to IP DSCP and choose a valid IP DSCP value.
|
Set IP DSCP radio button
|
Allows you to set the exceed action to IP DSCP.
|
Set IP DSCP list
|
Allows you to choose the IP DSCP value.
The Set IP DSCP list sets the IP DSCP value and sends the packet with the new IP DSCP value setting.
The Set IP DSCP radio button must be chosen to enable the Set IP DSCP list.
|
Violate Area
|
Drop radio button
|
Allows you to set the violate action to Drop. Drop means that the packets are dropped when the packet sizes violate the normal and maximum burst sizes.
|
Set MPLS EXP topmost
|
Allows you to set the violate action to MPLS EXP topmost and choose the MPLS EXP topmost value.
|
Set MPLS EXP topmost radio button
|
Allows you to set the violate action to MPLS EXP topmost.
|
Set MPLS EXP topmost list
|
Allows you to choose the MPLS EXP topmost value.
The Set MPLS EXT topmost list sets the MPLS experimental bits from 0 to 7 and sends the packet with the new MPLS experimental bit value setting.
The Set MPLS EXP topmost radio button must be chosen to enable the Set MPLS EXP topmost list.
|
Set Discard Class
|
Allows you to set the violate action to Discard Class and choose a valid discard class value.
|
Set Discard Class radio button
|
Allows you to set the violate action to Discard Class.
|
Set Discard Class list
|
Allows you to choose the discard class value.
The Set Discard Class list sets the discard class attribute of a packet and sends the packet with the new discard class setting.
The Set Discard Class radio button must be chosen to enable the Set Discard Class list.
|
Set IP Precedence
|
Allows you to set the violate action to IP Precedence and choose a valid IP precedence value.
|
Set IP Precedence radio button
|
Allows you to set the violate action to IP precedence.
|
Set IP Precedence list
|
Allows you to choose the IP precedence value. Options are:
•Routine
•Priority
•Immediate
•Flash
•Flash Override
•Critical
•Internet
•Network
The Set IP Precedence list sets the IP precedence and sends the packet with the new IP precedence value setting.
The Set IP Precedence radio button must be chosen to enable the Set IP Precedence list.
|
Set IP DSCP
|
Allows you to set the violate action to IP DSCP and choose a valid IP DSCP value.
|
Set IP DSCP radio button
|
Allows you to set the violate action to IP DSCP.
|
Set IP DSCP list
|
Allows you to choose the IP DSCP value.
The Set IP DSCP list sets the IP DSCP value and sends the packet with the new IP DSCP value setting.
The Set IP DSCP radio button must be chosen to enable the Set IP DSCP list.
|
5.4.9.2.5 Mark Subtab
The Mark subtab allows you to set the policy map criteria.
Table 5-55 describes the Mark subtab fields.
Table 5-55 Field Descriptions for the Mark Subtab
Field
|
Description
|
None radio button
|
Allows you to set the mark action to None.
|
Discard Class
|
Allows you to set the discard class and choose a valid discard class value for inbound policies. Choosing a discard class value marks a packet with the discard class value.
|
Discard Class radio button
|
Allows you to set the discard class.
|
Discard Class list
|
Allows you to choose the discard class value.
The Discard Class radio button must be chosen to enable the Discard Class list.
|
MPLS EXP topmost
|
Allows you to set the MPLS EXP topmost and choose the MPLS EXP topmost value.
|
MPLS EXP topmost radio button
|
Allows you to set the MPLS EXP topmost value.
|
MPLS EXP topmost list
|
Allows you to choose the MPLS EXP topmost value.
The MPLS EXP topmost radio button must be chosen to enable the MPLS EXP topmost list.
|
QoS Group
|
Allows you to set the QoS group and choose a valid QoS value for inbound policies. Choosing a QoS group sets a QoS group identifier that can be used later to classify packets.
|
QoS Group radio button
|
Allows you to set the QoS group.
|
QoS Group list
|
Allows you to choose the QoS group value.
The QoS Group radio button must be chosen to enable the QoS Group list.
|
IP Precedence
|
Allows you to set the IP precedence and choose a valid IP precedence value. Choosing an IP precedence sets the precedence value in the packet header.
|
IP Precedence radio button
|
Allows you to set the IP precedence.
|
IP Precedence list
|
Allows you to choose the IP precedence value. Options are:
•Routine
•Priority
•Immediate
•Flash
•Flash Override
•Critical
•Internet
•Network
The IP Precedence radio button must be chosen to enable the IP Precedence list.
|
IP DSCP
|
Allows you to set the IP DSCP and choose a valid IP DSCP value. Choosing an IP DSCP marks a packet by setting the DSCP value in the ToS byte.
|
IP DSCP radio button
|
Allows you to set the IP DSCP.
|
IP DSCP list
|
Allows you to choose the IP DSCP value.
The IP DSCP radio button must be chosen to enable the IP DSCP list.
|
COS
|
Allows you to set the class of service (CoS) and choose a valid COS value.
CoS is an indication of how an upper-layer protocol requires a lower-layer protocol to treat its messages. Also called ToS.
|
COS radio button
|
Allows you to set the COS.
|
COS list
|
Allows you to choose the COS value.
Choosing a CoS sets the Layer 2 CoS value of an outgoing packet.
The COS radio button must be chosen to enable the COS list.
|
5.4.9.3 Service Policies Tab
The Service Policies tab allows you to specify the service policy criteria.
Table 5-56 describes the Service Policies tab fields.
Table 5-56 Field Descriptions for the Service Policies Tab
Field
|
Description
|
Basics Area
|
Inbound Service Policy field
|
Allows you to enter the name of a policy map to attach to an inbound interface to be used as the service policy for that interface.
|
Outbound Service Policy field
|
Allows you to enter the name of a policy map to attach to an outbound interface to be used as the service policy for that interface.
|
5.4.10 Routing Policy Manager Application
The Routing Policy Manager Application contains the following tabs:
•Prefix Lists Tab
•Standard Community Lists Tab
•Expanded Community Lists Tab
•AS Path Access Lists Tab
The Routing Policy Manager application allows you to configure system-wide policy-related information that includes prefix lists, standard and extended community lists, and AS-path access lists.
Routing policy provides a flexible mechanism to route IP traffic to a destination and to provide access control. A routing policy is defined to configure a router to inspect and modify the attributes of routes. The definition of a routing policy in the network determines how routes are processed. Routing protocols make routing decisions to advertise, aggregate, discard, distribute, export, hold, import, redistribute, and otherwise modify routes based on the configured routing policy. Routing policies were previously defined by route maps. However, route maps have limitations and are difficult to maintain and troubleshoot in large networks as configuration sizes increase.
Note To configure Routing Policy Language (RPL), refer to Cisco CRS-1 Series Carrier Routing System Configuration Guide.
5.4.10.1 Prefix Lists Tab
The Prefix Lists tab allows you to specify any routes that have a destination network number address that is permitted by a prefix list.
The Prefix Lists tab allows you to perform the following tasks:
•Specify a prefix list name and sequence number.
•Specify whether to permit or deny packets that match the prefix list criteria.
•Specify the prefix list matching criteria.
You can recorder the prefix 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.
Table 5-57 describes the Prefix Lists tab fields.
Table 5-57 Field Descriptions for the Prefix Lists Tab
Field
|
Description
|
Basics Area
|
Name field
|
Allows you to enter the prefix list name.
|
Sequence Number field
|
Allows you to enter the sequence number of the prefix list.
|
Grant list
|
Allows you to either permit or deny packets that match the prefix list criteria specified in the following fields:
•Prefix
•Prefix Mask
•Min Prefix Length
•Max Prefix Length
Options are:
•Permit—Permits a packet that matches the criteria.
•Deny—Denies the packet that matches the criteria.
|
Prefix field
|
Allows you to enter the IPv4 prefix address to match. Prefix address matching distributes any routes that have a destination network number address that is permitted by a prefix list.
|
Prefix Mask field
|
Allows you to enter the IPv4 prefix mask to match.
|
Min Prefix Length field
|
Allows you to specify the minimum length of the prefix to match.
|
Max Prefix Length field
|
Allows you to specify the maximum length of the prefix to match.
|
Add remark field
|
Allows you to add comments or a description to the prefix list.
|
5.4.10.2 Standard Community Lists Tab
The Standard Community Lists tab allows you to specify the standard community lists name, sequence number, and community numbers, and whether to permit matching.
You can recorder the standard community 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.
Table 5-58 describes the Standard Community Lists tab fields.
Table 5-58 Field Descriptions for the Standard Community Lists Tab
Field
|
Description
|
Standard Community Lists Area
|
List No. field
|
Allows you to enter a value that identifies the standard community list. The standard community list can contain one or more permit or deny groups of communities.
|
Sequence No. field
|
Allows you to enter the sequence number of the standard community list.
|
Grant list
|
Allows you to either permit or deny access for a matching condition.
|
Community Numbers field
|
Allows you to enter up to three standard community numbers.
|
5.4.10.3 Expanded Community Lists Tab
The Expanded Community Lists tab allows you to specify the expanded community lists name and sequence number, and whether to permit matching regular expressions.
You can recorder the expanded community 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.
Table 5-59 describes the Expanded Community Lists tab fields.
Table 5-59 Field Descriptions for the Expanded Community Lists Tab
Field
|
Description
|
Extended Community Lists Area
|
List No field
|
Allows you to enter a value that identifies the expanded community list to use for filtering.
|
Sequence No field
|
Allows you to enter the sequence number of the expanded community list.
|
Action field
|
Allows you to either permit or deny access for a matching condition.
|
Regular Expression field
|
Allows you to enter an autonomous system in the expanded community list using a regular expression.
|
5.4.10.4 AS Path Access Lists Tab
The AS Path Access Lists tab allows you to specify the autonomous system (AS) path access lists name and sequence number, and whether to permit matching regular expressions.
You can recorder the AS path 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.
Table 5-60 describes the AS Path Access Lists tab fields.
Table 5-60 Field Descriptions for the AS Path Access Lists Tab
Field
|
Description
|
AS Path Access Lists Area
|
List No field
|
Allows you to enter a value that identifies the group of AS-path access lists.
|
Sequence No field
|
Allows you to enter the sequence number of the AS-path access list.
|
Filter list
|
Allows you to either permit or deny access for a matching condition.
|
Regular Expression field
|
Allows you to enter an autonomous system in the access list using a regular expression to match the BGP AS-paths.
You can specify an access list filter on both inbound and outbound BGP routes. In addition, you can assign weights based on a set of filters. Each filter is an access list based on regular expressions. If the regular expression matches the representation of the AS-path of the route as an ASCII string, then the permit or deny condition applies. The AS-path does not contain the local AS-number.
|
5.4.11 BGP Configuration Application
The BGP Configuration Application contains the following tabs:
•General Tab
•Networks Tab
•Aggregates Tab
•Redistribution Tab
•Neighbors Tab
•Neighbor Address Family Configuration Window
•Neighbor Groups Tab
•Neighbor Group Address Family Configuration Window
•Session Groups Tab
•AF Groups Tab
•Operations Tab
The BGP Configuration application allows you to configure the Border Gateway Protocol (BGP) routing protocol on the router.
The BGP performs interdomain routing in TCP/IP networks. BGP is an Exterior Gateway Protocol (EGP), which means that it performs routing between multiple autonomous systems and exchanges routing and reachability information with other BGP systems.
Like any routing protocol, BGP maintains routing tables, sends routing updates, and bases routing decisions on routing metrics.
Each BGP router maintains a routing table listing all feasible paths to a particular network. Periodic refreshing of the routing table is not performed. Routing information received from peer routers is retained until an incremental update is received.
BGP devices exchange routing information in the following situations:
•Initial data exchange—When a router first connects to the network, BGP routers exchange their entire BGP routing tables.
•Incremental updates—When the routing table changes, routers send the portion of their routing table that has changed.
BGP routers do not send regularly scheduled routing updates. BGP routing updates advertise only the optimal path to a network.
BGP uses a single routing metric to determine the best path to a given network. This metric consists of an arbitrary unit number specifying the degree of preference of a particular link.
The BGP metric is typically assigned to each link by the network administrator. The value assigned to a link can be based on any number of criteria, including the following:
•Autonomous system count—The number of autonomous systems through which the path passes.
•Type of link—How stable or fast the link is.
•Other factors—Other criteria; for example, delay and cost.
5.4.11.1 General Tab
The General tab contains five subtabs: Cluster ID, Confederation, Graceful Restart, Router ID, and Write Limit. The Cluster ID subtab is displayed by default when the General tab is clicked.
The General tab allows you to perform the following tasks:
•Specify an autonomous system (AS) number, local preference, local metric, send buffer sizes, receive buffer sizes, and best path parameters.
•Configure the global address family modes.
Table 5-61 describes the General tab fields.
Table 5-61 Field Descriptions for the General Tab
Field
|
Description
|
AS Number
|
Allows you to enter the router autonomous system number.
|
Default Local Preference
|
Allows you to enter a value for the default local preference.
Generally, the default value of 100 allows you to easily define a particular path as less preferable than paths with no local preference attribute. The preference is sent to all networking devices in the local AS.
|
Default Metric
|
Allows you to enter the default metric value for the BGP.
A default metric helps solve the problem of redistributing routes with incompatible metrics. Whenever metrics do not convert, using a default metric provides a reasonable substitute and enables the redistribution to proceed.
In BGP, setting the default metric sets the Multi Exit Discriminator (MED) metric.
|
Keepalive (sec)
|
Allows you to enter a value for the frequency, in seconds, with which the software sends keepalive messages to the neighbor.
The configured value for the keepalive time is used, provided it does not exceed a third of the negotiated hold time. If it does, a value of a third of the negotiated hold time will be used.
|
Holdtime (sec)
|
Allows you to enter a value for the interval after not receiving a keepalive message from the neighbor that the software terminates the neighbor BGP session.
Enter 0 to disable keepalive and hold time.
Note that the values 1 and 2 are not allowable because the minimum allowable keepalive time is a third of the holdtime.
|
Socket Receive Size (bytes)
|
Allows you to enter the receive socket buffer size.
|
BGP Receive Size (bytes)
|
Allows you to enter the BGP receive buffer size.
|
Socket Send Size (bytes)
|
Allows you to enter the send socket buffer size.
|
BGP Send Size (bytes)
|
Allows you to enter the BGP write buffer size.
|
Scan Time (sec)
|
Allows you to enter the scanner interval.
|
Update Delay(sec) field
|
Allows you to enter a value for the maximum delay time for a BGP-speaking networking device.
|
Always check box
|
Allows you to disable the keepalive trigger best path and enforce the delay specified in the Update Delay (sec) field.
|
AS Path Loopcheck check box
|
Allows you to enable an autonomous system path for loop checking internal Border Gateway Protocol (iBGP) peers.
|
Auto Policy Soft Reset check box
|
Allows you to enable an automatic soft peer reset on the reconfiguration for BGP peers.
|
Bestpath Compare Router ID check box
|
Allows you to enable the comparison of identical routes received from external BGP (eBGP) peers during the best path selection process and switch the best path to the route with the lowest router ID.
By default, during the best path selection process, when BGP receives identical routes from eBGP peers (all the attributes are the same except for the router ID), the best path is not switched to the route with the lowest router ID if that route was not the first route received. If the Bestpath Compare Router ID check box is checked, then similar routes are compared and the best path is switched to the route with the lowest router ID.
|
Bestpath Med Always check box
|
Allows you to enable the comparison of the MED for paths from neighbors in different autonomous systems.
The software chooses the path with the lowest MED.
By default, during the best path selection process, there is a MED comparison only among paths from the same autonomous system. Checking the Bestpath Med Always check box allows comparison of MEDs among paths regardless of the autonomous system from which the paths are received.
|
Bestpath Med Confed check box
|
Allows you to enable MED comparison among paths learned from confederation peers.
There is a comparison between MEDs only if no external autonomous systems are in the path (an external autonomous system is an autonomous system that is not within the confederation). If an external autonomous system is in the path, then the external MED passes transparently through the confederation, and the comparison is not made.
For example, assume that autonomous systems 65000, 65001, 65002, and 65004 are part of the confederation. Autonomous system 1 is not. The software compares route A with the following four paths:
•path 1 = 65000 65004, med=2
•path 2 = 65001 65004, med=3
•path 3 = 65002 65004, med=4
•path 4 = 65003 1, med=1
If the Bestpath Med Confed check box is checked, the software chooses path 1. The fourth path has a lower MED, but the software does not include path 4 in the MED comparison because an external autonomous system is in this path.
|
Bestpath Med Missing As Worst check box
|
Allows you to have the software consider a missing MED attribute in a path as having a value of infinity, making the path without a MED value the least desirable path.
|
Default Information Originate check box
|
Allows you to enable the distribution of a default route (set the originate network to 0.0.0.0 into the BGP table).
|
Enforce First AS check box
|
Allows you to enable the enforcement of the first autonomous system (known as the AS-path) of a route received from an eBGP peer to be the same as the configured remote autonomous system.
By default, the software ignores any update received from an eBGP neighbor that does not have the autonomous system configured for that neighbor at the beginning of the AS-path. When checked, the Enforce First AS check box applies to all eBGP peers of the networking device.
|
Fast External Fallover check box
|
Allows you to enable the immediate reset of the BGP sessions of any directly adjacent external peers if the link used to reach them goes down.
Performing an immediate session reset allows the network to recover faster when links go down between BGP peers.
|
Log Neighbor Changes check box
|
Allows you to enable logging of BGP neighbor resets.
Log Neighbor Changes enables logging of BGP neighbor status changes (up or down) and resets for troubleshooting network connectivity problems and measuring network stability. Unexpected neighbor resets might indicate high error rates or high packet loss in the network, and should be investigated.
|
Redistribute Internal check box
|
Allows you to enable the redistribution of iBGP routes into an Interior Gateway Protocol (IGP) such as Intermediate System-to-Intermediate System (ISIS) or Open Shortest Path First (OSPF).
Caution Redistributing iBGP routes into IGPs may cause routing loops to form within an autonomous system.
|
AF Mode
|
Allows you to create an address family group for BGP neighbors.
An address family group for BGP neighbors is used to group address family-specific neighbor parameters within an IP address family. Neighbors that have the same address family configuration are able to use the address family group name under that address family. Further, neighbors will inherit the configuration parameters of the entire address family group.
|
AF Mode field
|
Allows you to view the address family group.
|
AF Mode ellipsis button
|
Allows you to configure an address family group from the Global Address Family Configuration window. Configure the global address family using the Family Configuration window. See Global Address Family Configuration Window.
|
5.4.11.1.1 Global Address Family Configuration Window
The Global Address Family Configuration window is opened when the AF Mode ellipsis button is clicked in the General tab.
The Global Address Family Configuration window allows you to perform the following tasks:
•Choose the address family mode.
•Configure the address family distances.
•Specify the number of paths to a single destination.
•Specify the scanner interval.
•Specify a policy name.
•Configure dampening parameters.
Table 5-62 describes the Global Address Family Configuration window fields.
Table 5-62 Field Descriptions for the Global Address Family Configuration Window
Field
|
Description
|
AF Mode list
|
Allows you to choose the address family mode. Options are:
•IPv4Unicast
•IPv4Multicast
•IPv6Unicast
|
Global AF Detail Area
|
External Distance field
|
Allows you to specify the distance for routes external to the AS. The external distance is the administrative distance for BGP external routes. External routes are routes for which the best path is learned from a neighbor external to the autonomous system.
An administrative distance is a rating of the trustworthiness of a routing information source, such as an individual networking device or a group of networking devices. In general, the higher the value, the lower the trust rating. An administrative distance of 255 means the routing information source cannot be trusted at all and should be ignored.
|
Internal Distance field
|
Allows you to specify the distance for routes internal to the AS. This is the administrative distance for BGP internal routes. Internal routes are those routes that are learned from another BGP entity within the same autonomous system.
An administrative distance is a rating of the trustworthiness of a routing information source, such as an individual networking device or a group of networking devices. In general, the higher the value, the lower the trust rating. An administrative distance of 255 means the routing information source cannot be trusted at all and should be ignored.
|
Local Distance field
|
Allows you to specify the distance for local routes. This is the administrative distance for BGP local routes. The local-distance parameter applies to locally generated aggregate routes and backdoor routes installed in the routing table.
Caution Changing the administrative distance of BGP internal routes is considered risky and is not recommended. One problem that can arise is the accumulation of routing table inconsistencies, which can interfere with routing.
An administrative distance is a rating of the trustworthiness of a routing information source, such as an individual networking device or a group of networking devices. In general, the higher the value, the lower the trust rating. An administrative distance of 255 means the routing information source cannot be trusted at all and should be ignored.
|
Maximum Paths field
|
Allows you to enter the maximum number of paths to a single destination.
|
CC Reflection check box
|
Allows you to enable route reflection from a BGP route reflector to clients. Click the CC Reflection check box to enable client-to-client (CC) reflection.
Clients of a route reflector are not required to be fully meshed and the routes from a client are reflected to other clients. However, if the clients are fully meshed, route reflection is not required.
If the neighbors are fully meshed, there is no need for client-to-client reflection. If the neighbors are not fully meshed, the route reflection (RR) configuration can be based on the address family-specific number.
|
Scan Time (sec) field
|
Allows you to specify the scanning intervals of BGP-speaking networking devices.
The specified scan time shortens the interval times where the BGP scanner processes routing information. Internal BGP features may work more efficiently if the routing tables are updated faster.
|
Table Policy field
|
Allows you to specify a routing policy for updates advertised to or received from a BGP neighbor. The policy can be used to filter routes and to modify route attributes.
|
Dampening check box
|
Allows you to enable BGP dampening for the global address family. Check the Dampening check box to enable dampening.
|
Route Policy
|
Allows you to specify the name of the route policy.
|
Route Policy radio button
|
Allows you to select route policy filtering.
|
Route Policy field
|
Allows you to enter the name of the route policy.
This field is enabled when the Route Policy radio button is activated.
|
Counters radio button
|
Allows you to configure dampening using counters. When this radio button is clicked, the Half-Life, Max Suppress, Reuse, and Suppress fields become available in sequence when values are entered into the fields.
|
Half-Life (min) field
|
Allows you to specify the time after which a penalty is decreased. Once the route has been assigned a penalty, the penalty is decreased by half after the half-life period. Penalty reduction happens every 5 seconds.
|
Max Suppress (min) field
|
Allows you to specify the maximum time a route can be suppressed. The default is four times the half-life value. If the default half-life value is selected, the maximum suppress time defaults to 60 minutes.
|
Reuse field
|
Allows you to enter the route reuse value. If the penalty for a flapping route decreases enough to fall below this value, the route is unsuppressed. Routes are unsuppressed in 10-second increments.
|
Suppress field
|
Allows you to enter a value for when route suppression should start. A route is suppressed when its penalty exceeds this limit.
|
5.4.11.1.2 Cluster ID Subtab
The Cluster ID subtab allows you to specify the cluster ID IP address or number.
Table 5-63 describes the Cluster ID subtab fields.
Table 5-63 Field Descriptions for the Cluster ID Subtab
Field
|
Description
|
Cluster ID check box
|
Allows you to enable the configuring of the cluster ID if the BGP cluster has more than one route reflector. Together, a route reflector and its clients form a cluster. Checking the check box enables the IP Address and Number radio buttons. (See IP Address and Number.)
Usually a cluster of clients will have a single route reflector. In that case, the cluster is identified by the software as the networking device ID of the route reflector. In order to increase redundancy and avoid a single point of failure in the network, a cluster might have more than one route reflector. In this case, all route reflectors in the cluster must be configured with the 4-byte cluster ID so that a route reflector can recognize updates from route reflectors in the same cluster.
If the cluster has more than one route reflector, checking the Cluster ID check box configures the cluster ID.
|
IP Address
|
Allows you to enter an IP address for the cluster ID.
|
IP Address radio button
|
Allows you to specify an IP address.
|
IP Address field
|
Allows you to enter an IP address for the cluster ID.
This field is enabled when the IP Address radio button is activated.
|
Number
|
Allows you to enter a number for the cluster ID. The number must be the cluster ID of the networking device acting as a route reflector.
|
Number radio button
|
Allows you to specify a number.
|
Number field
|
Allows you to enter a number for the cluster ID.
This field is enabled when the Number radio button is activated.
|
5.4.11.1.3 Confederation Subtab
The Confederation subtab allows you to perform the following tasks:
•Specify the confederation ID.
•Specify the confederation neighbors.
Table 5-64 describes the Confederation subtab fields.
Table 5-64 Field Descriptions for the Confederation Subtab
Field
|
Description
|
Confederation ID field
|
Allows you to specify a BGP confederation identifier. The confederation ID is an autonomous system number that internally includes multiple autonomous systems.
One way to reduce the iBGP mesh is to divide an autonomous system into multiple autonomous systems and group them into a single confederation. Each autonomous system is fully meshed within itself, and has a few connections to another autonomous system in the same confederation. Even though the peers in different autonomous systems have eBGP sessions, they exchange routing information as if they are iBGP peers. Specifically, the confederation maintains the next hop and local preference information, which allows you to retain a single IGP for all the autonomous systems. To the outside world, the confederation looks like a single autonomous system.
|
Confederation Peers field
|
Allows you to configure the autonomous systems that belong to a confederation by entering the autonomous system numbers for BGP peers that will belong to the confederation.
The autonomous systems specified are visible internally to a confederation. Each autonomous system is fully meshed within itself.
|
5.4.11.1.4 Graceful Restart Subtab
The Graceful Restart subtab allows you to perform the following tasks:
•Specify graceful restart and graceful reset.
•Specify the purge time.
•Specify the restart time.
•Specify the stale path time.
Table 5-65 describes the Graceful Restart subtab fields.
Table 5-65 Field Descriptions for the Graceful Restart Subtab
Field
|
Description
|
Graceful Restart check box
|
Allows you to enable graceful restart support.
|
Graceful Reset check box
|
Allows you to reset gracefully if the configuration change forces a peer reset.
|
Purge Time(sec) field
|
Allows you to enter the maximum time before stale routes are purged.
|
Restart Time(sec) field
|
Allows you to enter the maximum time advertised to neighbors.
|
Stalepath Time(sec) field
|
Allows you to enter the maximum time to wait for the End-of-RIB message from a neighbor that has been restarted before deleting learned routes.
|
5.4.11.1.5 Router ID Subtab
The Router ID subtab allows you to configure a router ID IP address or interface name.
Table 5-66 describes the Router ID subtab fields.
Table 5-66 Field Descriptions for the Router ID Subtab
Field
|
Description
|
Router ID check box
|
Allows you to enable the configuration of a fixed router ID for a BGP-speaking networking device.
A loopback interface, if one is configured, is more effective as an identifier because there is no physical link to go down.
|
IP Address
|
Allows you to specify an IP address for the router ID.
|
IP Address radio button
|
Allows you to specify the IP address.
|
IP Address field
|
Allows you to enter an IP address for the router ID.
This field is enabled when the IP Address radio button is activated.
|
Interface Name
|
Allows you to enter an interface name.
|
Interface Name radio button
|
Allows you to specify an interface name.
|
Interface Name field
|
Allows you to view the chosen interface name.
|
Interface Name ellipsis button
|
Allows you to choose an interface from the Select Interfaces dialog box.
This ellipsis button is enabled when the Interface Name radio button is activated.
|
5.4.11.1.6 Write Limit Subtab
The Write Limit subtab allows you to perform the following tasks:
•Specify a formatted messages limit.
•Specify an enqueued messages limit.
•Disable desynchronization.
Table 5-67 describes the Write Limit subtab fields.
Table 5-67 Field Descriptions for the Write Limit Subtab
Field
|
Description
|
Formatted Messages field
|
Allows you to enter the maximum number of formatted messages for an update group.
|
Enqueued Messages field
|
Allows you to enter the number of messages that can be enqueued in total.
|
Desynchronize check box
|
Allows you to desynchronize. Desynchronization is the process by which BGP will separate and update groups into slow and fast peers so that the slow peers do not increase the update latency of the fast peers.
|
5.4.11.2 Networks Tab
The Networks tab allows you to perform the following tasks:
•Specify the IP address and mask for a network.
•Choose the address family mode.
•Specify a backdoor route.
Table 5-68 describes the Networks tab fields.
Table 5-68 Field Descriptions for the Networks Tab
Field
|
Description
|
Network Area
|
IP Address
|
Allows you to specify a local network that the BGP routing process should originate and advertise to its neighbors.
The BGP determines which local networks will be originated by the networking device and included in routing advertisements to its neighbors. Only routes that are specified using the Networks tab will be originated and advertised to neighbors even if there is a corresponding non-BGP route in the routing table. Such routes can be learned using connected networks, static routing, or dynamic routing using an IGP.
|
IP Address field
|
Allows you to enter an IP address.
|
IP Address ellipsis button
|
Allows you to choose an IP address from the Select IP Address dialog box.
|
AF Mode list
|
Allows you to choose the address family mode. Options are:
•IPv4Unicast
•IPv4Multicast
•IPv6Unicast
|
Mask field
|
Allows you to enter an IP address mask for the network.
|
AutoGenerate Mask button
|
Allows you to automatically generate a mask. Click the button to automatically generate a mask.
|
Policy field
|
Allows you to enter the name of the route policy.
|
Backdoor check box
|
Allows you enable a BGP backdoor route. The backdoor route is to a BGP border networking device. This device will provide better information than the local networking device about the network.
|
5.4.11.3 Aggregates Tab
The Aggregates tab allows you to perform the following tasks:
•Specify the IP address and mask for aggregates.
•Choose the address format mode and optionally choose to generate AS confederation set path information and filter routes from updates.
•Configure the filtering policy for aggregates.
Table 5-69 describes the Aggregates tab fields.
Table 5-69 Field Descriptions for the Aggregates Tab
Field
|
Description
|
Aggregate Address Area
|
IP Address field
|
Allows you to specify an IP address to create an aggregate entry in a BGP routing table.
|
Mask field
|
Allows you to enter an aggregate IP address mask.
|
AutoGenerate Mask button
|
Allows you to automatically generate an aggregate mask. Click the button to automatically generate a mask.
|
AS Set check box
|
Allows you to generate AS set path information.
|
AF Mode list
|
Allows you to choose the address family mode. Options are:
•IPv4Unicast
•IPv4Multicast
•IPv6Unicast
|
|
