Table Of Contents
Configuring Hardware
5.1 Overview
5.2 Using the NE Explorer to Configure Optical NEs
5.2.1 Exporting an NE Configuration
5.2.2 Understanding the Color Scheme Used for Port and Alarm Status on CTC-Based NEs
5.3 Configuring Routing Protocols on Optical NEs
5.3.1 Specifying a Routing Protocol
5.3.2 Viewing Routing Tables for CTC-Based NEs
5.3.3 Creating Static Routes for CTC-Based NEs
5.3.4 Using OSPF with CTC-Based NEs
5.3.5 Using RIP
5.3.6 Creating and Modifying an SDCC, LDCC, or GCC Termination on Transponder Cards
5.3.7 Creating and Modifying an SDCC, LDCC, GCC, or OSC Termination on SONET or SDH Cards
5.3.8 Creating a DCC Tunnel Connection
5.3.9 Using SNMP
5.3.10 Configuring FTP Hosts for CTC-Based NEs
5.3.11 Specifying the Preferred Copy—ONS 15600 SONET or ONS 15600 SDH
5.3.12 Enabling Intermediate Path Performance Monitoring
5.3.13 Enabling Pointer Justification Count Monitoring for CTC-Based NEs
5.3.14 Changing the Power Monitoring Threshold for the ONS 15454 SONET and ONS 15454 SDH
5.3.15 Changing the Power Monitoring Threshold for the ONS 15600 SONET and ONS 15600 SDH
5.3.16 Creating an Ethernet Threshold
5.4 Synchronizing the Network for Optical Devices
5.4.1 Synchronization Settings for the ONS 15310 CL, ONS 15310 MA SONET, ONS 15327, ONS 15454 SONET, and ONS 15600 SONET
5.4.2 Synchronization Settings for the ONS 15310 MA SDH, ONS 15454 SDH, and ONS 15600 SDH
5.5 Synchronizing the Network for MGX Voice Gateway Devices
5.5.1 Viewing Clock Sources
5.6 Configuring the MDS 9000
5.7 Configuring the ONS 15216
5.8 Configuring the ONS 15302 and ONS 15305 Earlier than R3.0
5.9 Configuring the ONS 15305 R3.0, ONS 15310 CL, ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15327, ONS 15454 SONET, and ONS 15454 SDH
5.9.1 Launching the CTM NE Explorer
5.9.2 Launching CTC
5.9.3 Launching TL1
5.9.4 Provisioning an ONS 15305 R3.0, ONS 15310 CL, ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15327, ONS 15454 SONET, or ONS 15454 SDH Card Slot
5.9.5 Resetting a Card
5.9.6 Deleting a Card
5.9.7 Changing a Card
5.9.8 Inserting an AIS-V on an STS-1 SD-P
5.9.9 Changing Secure Config Mode—ONS 15454 SONET or ONS 15454 SDH
5.10 Configuring the ONS 15501, ONS 15530, and ONS 15540
5.11 Configuring the ONS 15600 SONET and ONS 15600 SDH
5.11.1 Launching the CTM NE Explorer
5.11.2 Launching CTC
5.11.3 Resetting a Card
5.11.4 Deleting a Card
5.11.5 Changing a Card
5.12 Configuring the ONS 15800, ONS 15801, and ONS 15808
5.12.1 Synchronizing the ONS 15800, ONS 15801, and ONS 15808 Configuration and Inventory
5.12.2 Manually Resetting the ONS 15800, ONS 15801, or ONS 15808
5.12.3 Tagging an ONS 15800, ONS 15801, or ONS 15808 Module as Out of Service
5.13 Configuring MGX Voice Gateway Devices
5.13.1 How Do I Manage My Network with the Chassis View?
5.13.2 How Do I Manage My Network with the Configuration Center?
5.13.3 How Do I Manage Templates for NEs?
5.13.4 How Do I Configure MGX Voice Gateway Devices?
5.13.5 How Do I Create or Modify APS?
Configuring Hardware
This chapter describes the various NE configuration procedures that can be managed by CTM. This chapter contains the following sections:
•
Overview
•Using the NE Explorer to Configure Optical NEs
•Configuring Routing Protocols on Optical NEs
•Synchronizing the Network for Optical Devices
•Synchronizing the Network for MGX Voice Gateway Devices
•Configuring the MDS 9000
•Configuring the ONS 15216
•Configuring the ONS 15302 and ONS 15305 Earlier than R3.0
•Configuring the ONS 15305 R3.0, ONS 15310 CL, ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15327, ONS 15454 SONET, and ONS 15454 SDH
•Configuring the ONS 15501, ONS 15530, and ONS 15540
•Configuring the ONS 15600 SONET and ONS 15600 SDH
•Configuring the ONS 15800, ONS 15801, and ONS 15808
•Configuring MGX Voice Gateway Devices
5.1 Overview
In order for CTM to communicate with NEs, certain configuration tasks must be performed on the NEs. Until these configuration tasks are completed, CTM cannot contact the NEs, and no management can begin.
Before CTM can manage NEs, the following conditions must be met:
•Ethernet—Management Ethernet port must be configured.
•Password—Current privileged command password must be configured.
•Telnet—Gigabit Route Processor (GRP) should accept a Telnet session.
•SNMP—GRP must be SNMP-manageable.
Configuration management functions control, identify, retrieve data from, and provide data to network resources to deliver customer services. Configuration management includes broad categories traditionally known as network planning and engineering, installation, network and service provisioning, service planning and negotiation, and status and control.
5.2 Using the NE Explorer to Configure Optical 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-12 on page 1-26 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 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.
5.2.1 Exporting an NE Configuration
Use the NE Configuration Export dialog box to save the NE configuration information for ONS 1580x NEs.
Step 1 In the Domain Explorer tree, select an ONS 1580x NE.
Step 2 Choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 3 In the NE Explorer window, choose Configuration > Export NE Configuration. The NE Configuration Export dialog box opens.
Step 4 Configure the fields. The following table provides descriptions.
Step 5 After making your selections, click OK.
Step 6 Click Yes in the confirmation dialog box. While the export is in progress, a progress bar tracks the percentage to completion.
Step 7 A confirmation dialog box indicates that the data was successfully exported. Click OK.
Table 5-1 Field Descriptions for the NE Configuration Export Dialog Box
Field
|
Description
|
Field Separator
|
You can export the data as comma-separated values (CSV) or tab-separated values (TSV), which are formats commonly used to import data into spreadsheet and database applications for further analysis and manipulation. Click Other if you want to separate the CTM data values with a different character. An error occurs if you select Other but do not insert a separator character.
|
Enclose text in double quotes if it has separator
|
If checked, exported text is enclosed in double quotation marks if that text has a separator. If you choose the CSV format, you must check this option to avoid generating an error.
|
Export configuration of the selected module only
|
If checked, only the selected module's configuration is exported.
|
Export to file
|
By default, exported data is stored in the C:\Cisco\TransportManagerClient<version_number>\exports or /opt/CiscoTransportManagerClient<version_number>/exports directory under the name that you provide in the Export to file text box. Click Browse to change the file location. An error occurs if you do not specify a filename for the configuration file.
|
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 for OC and STM cards that are physically present on the NE and are provisioned in CTM.
Figure 5-1 shows the color scheme used to represent the port state and alarm status. Figure 5-2 and Figure 5-3 show how the color-coded ports appear in the Network Explorer window.
Figure 5-1 Colors of Port State and Alarm Status
Row
|
Color
|
Port State
|
Port State Abbreviation
|
Alarm Status
|
1
|
Gray
|
Out of Service
|
OOS_DSBLD
|
—
|
2
|
Cyan
|
Out of Service-Maintenance
|
OOS_MT
|
—
|
3
|
Purple
|
In Service
|
IS_AINS
|
—
|
4
|
Green
|
In Service
|
IS
|
Clear
|
5
|
Light blue
|
In Service
|
IS
|
Warning
|
6
|
Yellow
|
In Service
|
IS
|
Minor
|
7
|
Orange
|
In Service
|
IS
|
Major
|
8
|
Red
|
In Service
|
IS
|
Critical
|
Figure 5-2 Sample of Ports with OOS, OOS_MT, IS_AINS, and IS States
Figure 5-3 Sample of Ports in IS State with Critical, Major, Minor, and Warning Alarms
5.3 Configuring Routing Protocols on Optical NEs
This section describes how to configure the various routing protocols supported by CTM. This section contains the following information:
•Specifying a Routing Protocol
•Viewing Routing Tables for CTC-Based NEs
•Creating Static Routes for CTC-Based NEs
•Using OSPF with CTC-Based NEs
•Using RIP
•Creating and Modifying an SDCC, LDCC, or GCC Termination on Transponder Cards
•Creating and Modifying an SDCC, LDCC, GCC, or OSC Termination on SONET or SDH Cards
•Creating a DCC Tunnel Connection
•Using SNMP
•Configuring FTP Hosts for CTC-Based NEs
•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
•Changing the Power Monitoring Threshold for the ONS 15600 SONET and ONS 15600 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. The following table provides field descriptions.
Table 5-2 Field Descriptions for the Routing Table
Field
|
Description
|
Destination
|
Displays the IP address of the destination network or host.
|
Mask
|
Displays the subnet mask used to reach the destination network or host.
|
Gateway
|
Displays the IP address of the gateway used to reach the destination network or host.
|
Usage
|
Displays the number of times the listed route has been used.
|
Interface
|
Displays the node interface used to access the destination.
|
5.3.3 Creating Static Routes for CTC-Based NEs
Step 1 In the Domain Explorer tree, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Network tab.
Step 3 Click the Static Routes subtab.
Step 4 Click Create. The Create New Static Route dialog box opens. The following table provides descriptions.
Step 5 After making your selections, click OK.
Table 5-3 Field Descriptions for the Create New Static Route Dialog Box
Field
|
Description
|
Destination IP
|
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).
|
Subnet 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.
•Confirm Authentication Key—Re-enter the OSPF authentication key to confirm it.
•Router Priority—Designated router for a subnet.
•Hello Interval—Number of seconds between OSPF hello packet advertisements sent by OSPF routers. The Cisco default is 10 seconds.
•Dead Interval—Number of seconds that will pass while an OSPF router's packets are not visible before its neighbors declare the router down. The Cisco default is 40 seconds.
•Transit Delay—Service speed. The Cisco default is 1 second.
•Retransmit Int—Time that will elapse before a packet is resent. The Cisco default is 5 seconds.
•LAN Metric—Cost for sending packets across the LAN. Values should be greater than zero.
Step 5 Click Apply.
5.3.4.1 Creating an OSPF Area Range
Note The ONS 15305 R3.0 does not support OSPF area ranges.
Step 1 In the Domain Explorer tree, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Network tab.
Step 3 Click the OSPF subtab and check the OSPF Active on LAN check box. (See Using OSPF with CTC-Based NEs for more information.)
Step 4 Click Apply.
Step 5 Click the OSPF Area Range subtab.
Step 6 Click Create. The Create OSPF Area Range dialog box opens. The following table provides descriptions.
Step 7 After making your selections, click OK.
Note If no range address is created when enabling OSPF on a LAN from CTM, you must manually provision the OSPF area range address for the respective range area IDs, as described in this procedure. Alternately, enable OSPF from CTC so that the range address is created when OSPF is enabled. This is a known issue that has been tracked using DDTS number CSCin62975.
Table 5-4 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.
|
Mask
|
Enter the subnet mask.
|
Advertise
|
Check this check box if you want the area range to be advertised.
|
5.3.4.2 Deleting an OSPF Area Range
Note The ONS 15305 R3.0 does not support OSPF area ranges.
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.
Note The ONS 15305 R3.0 does not support OSPF virtual links.
5.3.4.3.1 Viewing OSPF Virtual Links
Step 1 In the Domain Explorer tree, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Network tab.
Step 3 Click the OSPF Virtual Links subtab. The following information is displayed:
•Neighbor—Router ID of the Area 0 router.
•Transit Delay—Service speed. The Cisco default is 1 second.
•Retransmit Interval—Time that will elapse before a packet is resent. The Cisco default is 5 seconds.
•Hello Interval—Number of seconds between OSPF hello packet advertisements sent by OSPF routers.
•Dead Interval—Number of seconds that will pass while the packets of an OSPF router are not visible before its neighbors declare the router down.
•Authentication Type—Authentication type.
•Auth Key—Authentication key.
5.3.4.3.2 Creating an OSPF Virtual Link
Step 1 In the Domain Explorer tree, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Network tab.
Step 3 Click the OSPF subtab and check the OSPF Active on LAN check box. (See Using OSPF with CTC-Based NEs for more information.)
Step 4 Click Apply.
Step 5 Click the OSPF Virtual Links subtab.
Step 6 Click Create. The Create New Virtual Link dialog box opens and allows you to define a link between OSPF area border routers. The following table provides descriptions.
Step 7 After making your selections, click OK.
Table 5-5 Field Descriptions for the Create New Virtual Link Dialog Box
Field
|
Description
|
Neighbor
|
Specify the IP address of the Area 0 router.
|
Transit Delay
|
Specify the service speed. The Cisco default is 1 second.
|
Retransmit Interval
|
Specify the time that will elapse before a packet is resent. The Cisco default is 5 seconds.
|
Hello Interval
|
Specify the number of seconds between OSPF hello packet advertisements. The Cisco default is 10 seconds.
|
Dead Interval
|
Specify the number of seconds that will pass while the packets of an OSPF router are not visible before its neighbors declare the router down. The Cisco default is 40 seconds.
|
Authentication Type
|
Specify the authentication type. Select Simple Password if the router where the NE is connected uses authentication. Otherwise, select No Authentication.
|
Authentication Key
|
Enter the OSPF key (password) if authentication is enabled.
|
Confirm Authentication Key
|
Reenter the authentication key to confirm it.
|
5.3.4.3.3 Modifying an OSPF Virtual Link
Step 1 In the Domain Explorer tree, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Network tab.
Step 3 Click the OSPF Virtual Links subtab.
Step 4 Select an OSPF virtual link to modify; then click Edit.
Step 5 The Modify Virtual Link dialog box opens. Modify the following:
•Neighbor—Enter the new IP address.
•Transit Delay—Indicates the service speed.
•Retransmit Delay—Sets the time that will elapse before a packet is resent.
•Hello Interval—Sets the number of seconds between OSPF hello packet advertisements sent by OSPF routers.
•Dead Interval—Sets the number of seconds that will pass while an OSPF router's packets are not visible before its neighbors declare the router down.
•Authentication Type—Select the authentication type. Select either No Authentication or Simple Authentication.
•Auth Key—If Simple Authentication is selected as authentication type, enter the authentication key.
•Confirm Auth Key—Re-enter the authentication key.
Step 6 Click OK.
5.3.4.3.4 Deleting an OSPF Virtual Link
Step 1 In the Domain Explorer tree, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Network tab.
Step 3 Click the OSPF Virtual Links subtab.
Step 4 Select an OSPF virtual link to delete; then, click Delete.
Step 5 Click Yes in the confirmation dialog box.
5.3.5 Using RIP
Step 1 In the Domain Explorer tree, select an ONS 15310 CL, ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15327, ONS 15454 SONET, or ONS 15454 SDH NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Network tab.
Step 3 Click the RIP subtab.
Step 4 Complete the following:
•RIP Active—Check to enable RIP.
•RIP Type—Select the RIP version from the drop-down list.
•Metric—Select 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—Re-enter the password to confirm it.
Step 5 If you want to create an address summary, complete the following steps:
a. Click Create. Complete the address summary only if the NE is a gateway network element (GNE) with multiple end NEs attached and IP addresses in different subnets.
b. In the Create RIP Address Summary dialog box that opens, create aggregate addresses, which will be represented in the routing table by a summary address. Table 5-6 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-6 Field Descriptions for the Create RIP Address Summary Dialog Box
Field
|
Description
|
Summary Address
|
Specify the IP address of the RIP summary. This field is set to the NE IP address, with an applied mask of 255.255.255.0. For example, if the NE IP address is 10.20.30.15, the summary address is 10.20.30.0.
|
Mask Length
|
Enter the subnet mask length. The valid range is from 1 to 24.
|
Mask Address
|
Display only. View the subnet mask address, which is 255.255.255.0 by default.
|
Cost
|
Enter the hop count metric (the number of hops between the NE and the destination). The valid range is from 1 to 15. The smaller the number of hops, the higher the priority.
|
5.3.5.1 Viewing the RIP Routing Table
Step 1 In the Domain Explorer tree, select an ONS 15310 CL, ONS 15310 MA SONET, ONS 15310 MA SDH, 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—Display only. The IP address of the destination network or host.
•Mask—Display only. The subnet mask used to reach the destination host or network.
•Gateway—Display only. The IP address of the gateway used to reach the destination network or host.
•Cost—Display only. The hop count metric. The valid range is 1 to 15.
5.3.6 Creating and Modifying an SDCC, LDCC, or GCC Termination on Transponder Cards
Step 1 In the Domain Explorer tree, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane of the NE Explorer, click one of the following tabs. Tabs shown depend on the type of NE selected.
•DCC—DCC (Data Communications Channel) carries provisioning and maintenance data/information between network elements in the SONET overhead.
•DCC/GCC/OSC—GCC (General Communications Channel) is used for transponders and muxponders in dense wavelength division multiplexing (DWDM) applications. Optical Service Channel (OSC) is a bidirectional channel that connects two adjacent nodes in a DWDM ring.
•LDCC—LDCC (Line Data Communications Channel or Line DCC) is a 576-kb/s data communications channel embedded in the section overhead for OAM&P traffic between two NEs.
•SDCC—SDCC (Section Data Communications Channel or Section DCC) is a 192-kb/s data communications channel embedded in the section overhead for OAM&P traffic between two NEs.
Step 3 Click the subtab that corresponds to the termination that you want to create or modify. For example, to create or modify an LDCC termination, click the LDCC subtab.
Step 4 Complete one of the following options, depending on whether you want to create a new termination or modify an existing one:
•Click the Create button above the Transponder area. The Create <SDCC, LDCC, GCC, or OSC> dialog box opens and allows you to create new terminations on transponder cards. The following table provides descriptions.
Note The fields shown in the Create <SDCC, LDCC, GCC, or OSC> dialog box depend on the type of termination that is being created. The fields shown also depend on the NE type.
•Select an existing termination and click the Edit button above the Transponder area. The Edit <SDCC, LDCC, GCC, or OSC> dialog box opens and allows you to modify existing terminations on transponder cards. The following table provides descriptions.
Note The fields shown in the Edit <SDCC, LDCC, GCC, or OSC> dialog box depend on the type of termination that is being modified. The fields shown also depend on the NE type.
Step 5 After making your selections, click OK.
Table 5-7 Field Descriptions for the Create or Modify <SDCC, LDCC, GCC, or OSC> Dialog Box
Tab
|
Description
|
SDCC/LDCC Info
|
(Available for SDCC and LDCC terminations) Displays the slot and port number of the SDCC or LDCC termination.
Note For OTU2_XP cards, the card name might be shown as XP_4_10G_LINE_CARD.
|
GCC Terminations
|
(Available for GCC terminations) Displays the slot and port number of the GCC termination.
Note For OTU2_XP cards, the card name might be shown as XP_4_10G_LINE_CARD.
|
OSPF Disabled on Link
|
Indicates whether Open Shortest Path First (OSPF) is disabled on the link. OSPF should be disabled only when the slot and port connect to third-party equipment that does not support OSPF.
|
Foreign
|
If checked, it means that the far-end node is a non-ONS node.
|
Admin State
|
Indicates the SDCC or LDCC port state. Select one of the following:
Note Admin state options that appear in the drop-down list depend on the NE type.
•Leave Unchanged
•IS
•OOS MT
•IS AINS
|
Layer3/Layer 2 Config
|
Layer3 (Layer2) Config
|
Select one of the following:
•OSI (LAPD)—When selected, all fields in the OSI Subnet and LAPD areas are enabled. The Layer 3 protocol used for the DCC is OSI (IP not applicable); the Layer 2 protocol is LAPD. The OSI (LAPD) option applies only to SDCC and is disabled for all other DCC types.
•IP (PPP)—When selected, all fields in the OSI Subnet and LAPD areas are disabled. The Layer 3 protocol used for the DCC is IP only; the Layer 2 protocol is PPP.
•OSI and IP (PPP)—When selected, only the fields in the OSI Subnet area are enabled. The Layer 3 protocol includes both OSI and IP, but the Layer 2 protocol remains as PPP.
Note When editing an existing DCC, you can toggle between the IP (PPP) and OSI and IP (PPP) options if either option exists on the DCC.
Note If the DCC is configured as OSI (LAPD), you cannot modify the Layer 3/Layer 2 configuration.
|
OSI Subnet
|
Router Number
|
The OSI virtual router where the subnet (SDCC or LDCC) is provisioned.
|
IS-IS Cost
|
Sets the cost for sending packets on the subnet. This is used by OSPF routers to calculate the shortest path.
|
ISH
|
Sets the Intermediate System Hello (ISH) protocol data unit (PDU) propagation frequency. Intermediate system NEs send ISHs to other ESs and ISs to inform them about the NETs they serve. The Cisco default is 10 seconds. The range is from 10 to 1000 seconds.
|
ESH
|
Sets the End System Hello (ESH) propagation frequency. End system NEs transmit ESHs to inform other ESs and ISs about the NSAPs they serve. The Cisco default is 10 seconds. The range is from 10 to 1000 seconds.
|
IIH
|
Sets the Intermediate System to Intermediate System Hello PDU propagation frequency. The IS-IS Hello PDUs establish and maintain adjacencies between ISs. The Cisco default is 3 seconds. The range is from 1 to 600 seconds.
|
LAPD
|
Acknowledgement
|
Indicates the Link Access Protocol on the D channel (LAPD) acknowledgement type. Select either:
•Acknowledged Information Transfer Service (AITS)
•Unacknowledged Information Transfer Service (UITS)
|
T200
|
Shows the time between Set Asynchronous Balanced Mode (SABM) frame transmissions. The range is from 0.2 to 20 seconds.
|
T203
|
Shows the maximum time between LAPD frame exchanges. The range is from 4 to 120 seconds.
|
Mode
|
Indicates the LAPD frame command/response role. Values are:
•Network
•User
|
MTU
|
Sets the maximum transfer unit (MTU).
|
5.3.7 Creating and Modifying an SDCC, LDCC, GCC, or OSC Termination on SONET or SDH Cards
Step 1 In the Domain Explorer tree, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane of the NE Explorer, click one of the following tabs. Tabs shown depend on the type of NE selected.
•DCC—DCC carries provisioning and maintenance data/information between network elements in the SONET overhead.
•DCC/GCC/OSC—GCC is used for transponders and muxponders in DWDM applications. OSC is a bidirectional channel that connects two adjacent nodes in a DWDM ring.
•LDCC—LDCC is a 576-kb/s data communications channel embedded in the section overhead for OAM&P traffic between two NEs.
•SDCC—SDCC is a 192-kb/s data communications channel embedded in the section overhead for OAM&P traffic between two NEs.
Step 3 Click the subtab that corresponds to the termination that you want to create or modify. For example, to create or modify an LDCC termination, click the LDCC subtab.
Step 4 Complete one of the following options, depending on whether you want to create a new termination or modify an existing one:
•Click the Create button above the SONET/SDH area. The Create <SDCC, LDCC, GCC, or OSC> dialog box opens and allows you to create new terminations on SONET or SDH cards. The following table provides descriptions.
Note The fields shown in the Create <SDCC, LDCC, GCC, or OSC> dialog box depend on the type of termination that is being created. The fields shown also depend on the NE type.
•Select an existing termination and click the Edit button above the SONET/SDH area. The Edit <SDCC, LDCC, GCC, or OSC> dialog box opens and allows you to modify existing terminations on SONET or SDH cards. The following table provides descriptions.
Note The fields shown in the Edit <SDCC, LDCC, GCC, or OSC> dialog box depend on the type of termination that is being modified. The fields shown also depend on the NE type.
Step 5 After making your selections, click OK.
Table 5-8 Field Descriptions for the Create or Edit <SDCC, LDCC, GCC, or OSC> Dialog Box
Field
|
Description
|
SDCC/LDCC Info
|
(Available for SDCC and LDCC terminations) Displays the slot and port number of the SDCC or LDCC termination.
|
GCC Terminations
|
(Available for GCC terminations) Displays the slot and port number of the GCC termination.
|
OSC Terminations
|
(Available for OSC terminations) Displays the slot and port number of the OSC termination.
|
OSPF Disabled on Link
|
Indicates whether Open Shortest Path First (OSPF) is disabled on the link. OSPF should be disabled only when the slot and port connect to third-party equipment that does not support OSPF.
|
Foreign
|
If checked, it means that the far-end node is a non-ONS node.
|
Admin State
|
Indicates the SDCC or LDCC port state. Select one of the following:
Note Admin state options that appear in the drop-down list depend on the NE type.
•Leave Unchanged
•IS
•OOS MT
•IS AINS
|
GCC Rate
|
(Available for GCC terminations) Select the GCC rate.
|
Layer3/Layer 2 Config
|
Layer3 (Layer2) Config
|
Select one of the following:
•OSI (LAPD)—When selected, all fields in the OSI Subnet and LAPD areas are enabled. The Layer 3 protocol used for the DCC is OSI (IP not applicable); the Layer 2 protocol is LAPD. The OSI (LAPD) option applies only to SDCC and is disabled for all other DCC types.
•IP (PPP)—When selected, all fields in the OSI Subnet and LAPD areas are disabled. The Layer 3 protocol used for the DCC is IP only; the Layer 2 protocol is PPP.
•OSI and IP (PPP)—When selected, only the fields in the OSI Subnet area are enabled. The Layer 3 protocol includes both OSI and IP, but the Layer 2 protocol remains as PPP.
Note When editing an existing DCC, you can toggle between the IP (PPP) and OSI and IP (PPP) options if either option exists on the DCC.
Note If the DCC is configured as OSI (LAPD), you cannot modify the Layer 3/Layer 2 configuration.
|
OSI Subnet
|
Router Number
|
The OSI virtual router where the subnet (SDCC, LDCC, GCC, or OSC) is provisioned.
|
IS-IS Cost
|
Sets the cost for sending packets on the subnet. This is used by OSPF routers to calculate the shortest path.
|
ISH
|
Sets the Intermediate System Hello (ISH) protocol data unit (PDU) propagation frequency. Intermediate system NEs send ISHs to other ESs and ISs to inform them about the NETs they serve. The Cisco default is 10 seconds. The range is from 10 to 1000 seconds.
|
ESH
|
Sets the End System Hello (ESH) propagation frequency. End system NEs transmit ESHs to inform other ESs and ISs about the NSAPs they serve. The Cisco default is 10 seconds. The range is from 10 to 1000 seconds.
|
IIH
|
Sets the Intermediate System to Intermediate System Hello PDU propagation frequency. The IS-IS Hello PDUs establish and maintain adjacencies between ISs. The Cisco default is 3 seconds. The range is from 1 to 600 seconds.
|
LAPD
|
Acknowledgement
|
Indicates the Link Access Protocol on the D channel (LAPD) acknowledgement type. Select either:
•Acknowledged Information Transfer Service (AITS)
•Unacknowledged Information Transfer Service (UITS)
|
T200
|
Shows the time between Set Asynchronous Balanced Mode (SABM) frame transmissions. The range is from 0.2 to 20 seconds.
|
T203
|
Shows the maximum time between LAPD frame exchanges. The range is from 4 to 120 seconds.
|
Mode
|
Indicates the LAPD frame command/response role. Values are:
•Network
•User
|
MTU
|
Sets the maximum transfer unit (MTU).
|
5.3.8 Creating a DCC Tunnel Connection
The Create DCC Tunnel Connection dialog box allows you to create new DCC tunnel connections for the ONS 15454 SONET R3.3 and earlier.
Step 1 In the Domain Explorer tree, select the R3.3 or earlier ONS 15454 SONET NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane of the NE Explorer, click the DCC/GCC/OSC tab.
Step 3 Click the DCC Tunnel Connection subtab.
Step 4 Click Create. The Create dialog box opens. The following table provides descriptions.
Step 5 After making your selections, click OK.
Table 5-9 Field Descriptions for the Create DCC Tunnel Connection Dialog Box
Field
|
Description
|
From A
|
Select a beginning interface for the DCC tunnel.
|
From B
|
Select an ending interface for the DCC tunnel.
|
5.3.9 Using SNMP
5.3.9.1 Changing the SNMP Community String—CTC-Based NEs
Use the SNMP Trap Destination dialog box in CTC to provision community names for all SNMP requests (for example, get, next, bulk, and set) for CTC-based NEs R3.3 and later. Any SNMP request that uses a community name that matches a community name in the list of provisioned SNMP trap destinations is considered valid.
If an SNMP request contains an invalid community name (one that does not match a provisioned community name), the request is dropped silently. The MIB variable snmpInBadCommunityNames increments, and an authenticationFailure trap is sent.
Due to security concerns, the community names public and private do not have the special meaning that they have in most SNMP interfaces.
5.3.9.2 Configuring SNMP for CTC-Based NEs
Step 1 Select a CTC-based NE in the Domain Explorer tree and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Network tab; then, click the SNMP subtab. Fields shown depend on the type of NE that is selected.
Step 3 To allow SNMP proxy, check the Allow SNMP Proxy check box.
Step 4 To use the SNMP management software with the NE, check the Allow SNMP Set check box.
Step 5 Click Apply.
Step 6 Click Create. The Create SNMP Trap Destination dialog box opens. The following table provides descriptions.
Step 7 After making your selections, click OK.
Step 8 Click Apply.
Table 5-10 Field Descriptions for the Create SNMP Trap Destination Dialog Box
Field
|
Description
|
IP Address
|
Enter the IP address of your NMS.
|
Community Name
|
Enter the SNMP community name. For a description of SNMP community names, refer to the SNMP information in the NE reference guide.
Note The community name is a form of authentication and access control. The community name assigned to the ONS 15600 is case-sensitive and must match the community name of the NMS.
|
UDP Port
|
Set the UDP port for SNMP. The Cisco default port is 162. Allowed UDP port values are 162, 391, and values between 1024 and 65535.
|
Trap Version
|
Set the Trap Version field for either SNMPv1 or SNMPv2. See your NMS documentation to determine whether to use SNMPv1 or SNMPv2.
|
Max Traps per Second (not applicable to all NEs)
|
Enter the maximum number of traps per second that will be sent to the SNMP manager. A zero value indicates that there is no maximum and all traps are sent to the SNMP manager.
|
5.3.9.3 Creating an SNMP Community—ONS 15216 EDFA2
The Create SNMP Community View dialog box allows you to create an SNMP community for the ONS 15216 EDFA2.
Note SNMP views are supported only for EDFA2 R2.4.0. The SNMP tab is not present in the EDFA2 R2.1.1 and R2.3.0.
Step 1 In the Domain Explorer, select an ONS 15216 EDFA2 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click the SNMP Community Table subtab.
Step 4 Click Create. The Create SNMP Community View dialog box opens. The following table provides descriptions.
Table 5-11 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-12 for the SNMP operation decimal values.
|
IP Address
|
Enter the IP address from which network management traffic for the new SNMP community originates.
|
Subnet Mask
|
Enter the subnet mask for the source IP address.
|
Step 5 After making your selections, click OK in the Create SNMP Community View dialog box.
Step 6 Click Apply in the node properties pane. The new SNMP community is listed in the SNMP Community table.
The following table displays the decimal values for the different SNMP operations. For example, 255 is the sum of all decimal values and specifies access to all SNMP operations. This sum is the default private community. 247 is the sum for all SNMP operations with the exception of the Set operation. This sum is the default public community.
Table 5-12 SNMP Operation Decimal Values
SNMP Operation
|
Decimal Values
|
Get
|
1
|
GetNext
|
2
|
Response (enable for all community strings)
|
4
|
Set
|
8
|
SNMPv1-Trap
|
16
|
GetBulk
|
32
|
Inform (enable for all community strings)
|
64
|
SNMPv2-Trap (enable for all community strings)
|
128
|
5.3.9.4 Modifying an SNMP Community—ONS 15216 EDFA2
Step 1 In the Domain Explorer, select an ONS 15216 EDFA2 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click the SNMP Community Table subtab.
Step 4 In the SNMP Community table, select the SNMP community to modify.
Step 5 Double-click a specific field and modify the following:
•Community Name—New community string.
•View Index—New index number.
•Privilege—New access privilege that governs what management operations a particular community can perform. These privileges are expressed as a sum of values, where each value represents a particular operation. See Table 5-12 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—Display only.
Step 6 Click Apply.
5.3.9.5 Deleting an SNMP Community—ONS 15216 EDFA2
Step 1 In the Domain Explorer, select an ONS 15216 EDFA2 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click the SNMP Community Table subtab.
Step 4 In the SNMP Community table, select an SNMP community to delete.
Step 5 Click Delete; then, click OK.
Step 6 Click Apply.
5.3.9.6 Creating an SNMP Trap Destination—ONS 15216 EDFA2
Step 1 In the Domain Explorer, select an ONS 15216 EDFA2 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click the Trap Destination Table subtab.
Step 4 Click Create. The Create Trap Destination dialog box opens. The following table provides descriptions.
Step 5 After making your selections, click OK.
Step 6 Click Apply in the node properties pane. The new SNMP trap destination is listed in the Trap Destination table.
Table 5-13 Field Descriptions for the Create Trap Destination Dialog Box
Field
|
Description
|
IP Address
|
Type the SNMP trap destination IP address.
|
UDP Port
|
Set the trap destination User Datagram Protocol (UDP) port for SNMP.
|
Community Name
|
Type the SNMP community name.
|
Version
|
Enter the trap version number.
|
5.3.9.7 Modifying an SNMP Trap Destination—ONS 15216 EDFA2
Step 1 In the Domain Explorer, select an ONS 15216 EDFA2 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click the Trap Destination Table subtab.
Step 4 In the Trap Destination table, select the SNMP trap destination to modify.
Step 5 Double-click a specific field and modify the following:
•IP Address—IP address of the SNMP trap destination.
•UDP Port—UDP port number of the SNMP trap destination.
•Community Name—SNMP trap destination community string name.
•Version—Select the version from the pull-down menu.
•View Index—New index number.
•Status—Display only.
Step 6 Click Apply.
5.3.9.8 Deleting an SNMP Trap Destination—ONS 15216 EDFA2
Step 1 In the Domain Explorer, select an ONS 15216 EDFA2 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click the Trap Destination Table subtab.
Step 4 In the Trap Destination table, select an SNMP trap destination to delete.
Step 5 Click Delete; then, click OK.
Step 6 Click Apply.
5.3.9.9 Creating an SNMP View—ONS 15216 EDFA2
Step 1 In the Domain Explorer, select an ONS 15216 EDFA2 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click the SNMP Views subtab.
Step 4 Click Create. The Create SNMP View dialog box opens. The following table provides descriptions.
Step 5 After making your selections, click OK.
Step 6 Click Apply in the node properties pane. The new SNMP view is listed in the SNMP Views table.
Table 5-14 Field Descriptions for the Create SNMP View Dialog Box
Field
|
Description
|
View Index
|
Enter the view index number, which is a unique value for each MIB view.
|
Subtree
|
Enter an object identifier that designates a subtree element in the MIB hierarchy.
|
Mask
|
Enter the bit mask that identifies objects in the subtree.
|
Type
|
From the pull-down menu, select the flag that specifies the status of the view. Values are included and excluded.
|
5.3.9.10 Modifying an SNMP View—ONS 15216 EDFA2
Step 1 In the Domain Explorer, select an ONS 15216 EDFA2 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click the SNMP Views subtab.
Step 4 In the SNMP Views table, select the SNMP view to modify.
Step 5 Double-click a specific field and modify the following:
•View Index—Display only.
•Subtree—Display 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—Display only.
Step 6 Click Apply.
5.3.9.11 Deleting an SNMP View—ONS 15216 EDFA2
Step 1 In the Domain Explorer, select an ONS 15216 EDFA2 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click the SNMP Views subtab.
Step 4 In the SNMP Views table, select an SNMP view to delete.
Step 5 Click Delete; then, click OK.
Step 6 Click Apply.
5.3.9.12 Creating an SNMP Trap Destination—ONS 15216 EDFA3
Step 1 In the Domain Explorer, select an ONS 15216 EDFA3 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click Add Row. The Create Trap Destination table opens. The following table 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-15 Field Descriptions for the Trap Destination Table Subtab
Field
|
Description
|
IP Address
|
Enter the trap destination IP address.
|
UDP Port
|
Set the trap destination UDP port for SNMP.
|
Community Name
|
Enter the SNMP trap destination community string name.
|
Version
|
Enter the trap version number.
|
5.3.9.13 Modifying an SNMP Trap Destination—ONS 15216 EDFA3
Step 1 In the Domain Explorer, select an ONS 15216 EDFA3 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click the Trap Destination Table subtab.
Step 4 In the Trap Destination table, select the SNMP trap destination to modify.
Step 5 Double-click a specific field and modify the following:
•IP Address—IP address of the SNMP trap destination.
•UDP Port—UDP port number of the SNMP trap destination.
•Community Name—SNMP trap destination community string name.
•Version—Select the version from the pull-down menu.
Step 6 Click Apply.
5.3.9.14 Deleting an SNMP Trap Destination—ONS 15216 EDFA3
Step 1 In the Domain Explorer, select an ONS 15216 EDFA3 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the SNMP tab.
Step 3 Click the Trap Destination Table subtab.
Step 4 In the Trap Destination table, select an SNMP trap destination to delete; then, click Delete Row.
Step 5 Click Apply.
5.3.10 Configuring FTP Hosts for CTC-Based NEs
The following sections describe how to configure database backup or restore and software download to an ENE when a firewall is enabled. You can provision a list of legal FTP hosts for which the firewall opens for all FTP commands. You can configure the FTP hosts to expire after a certain amount of time, after which time the FTP relay resumes blocking all FTP access for the ENEs.
5.3.10.1 Creating an FTP Host
Step 1 In a CTC-based GNE/ENE configuration with proxy/firewall enabled, select one of the following NEs in the Domain Explorer tree and choose Configuration > NE Explorer (or click the Open NE Explorer tool):
•ONS 15310 CL
•ONS 15310 MA SONET
•ONS 15310 MA SDH
•ONS 15454 SONET
•ONS 15454 SDH
•ONS 15600 SONET
•ONS 15600 SDH
Step 2 In the node properties pane, click the Network tab; then, click the FTP Hosts subtab.
Step 3 Click the Create button. The Create New FTP Host dialog box opens.
Note You can create up to a maximum of 12 FTP hosts.
Step 4 Configure the fields described in the following table.
Step 5 Click OK. The new FTP host is created and appears in the FTP Hosts subtab.
Table 5-16 Field Descriptions for the Create New FTP Host Dialog Box
Field
|
Description
|
FTP Host Address
|
Enter the FTP host IP address.
|
Prefix Length
|
Specify the FTP host subnet mask length.
|
Enable FTP Relay
|
Check this check box to enable FTP relay. If FTP relay is disabled, the FTP Relay Timer field is dimmed.
|
FTP Relay Timer
|
Enter the number of minutes for the FTP relay to continue, after which time the FTP relay resumes blocking all FTP access for the ENEs.
|
5.3.10.2 Creating FTP Hosts on Multiple NEs Simultaneously
Use the FTP Hosts Creation wizard to create FTP hosts on multiple NEs simultaneously in a GNE/ENE firewall environment.
Step 1 In a CTC-based GNE/ENE configuration with proxy/firewall enabled, choose Administration > Bulk FTP Configuration in the Domain Explorer. The FTP Hosts Creation wizard opens.
Step 2 In the Add FTP Hosts pane, click Add Row. For each new FTP host, configure the following information:
•FTP host address—Enter the IP address for the FTP host.
•Prefix length—Specify the subnet mask length for the FTP host.
•FTP relay—Enable or disable FTP relay. If FTP relay is disabled, the FTP Relay Timer field is dimmed.
•FTP relay timer—Enter the number of minutes for the FTP relay to continue, after which time the FTP relay resumes blocking all FTP access for the ENEs.
Step 3 Repeat Step 2 for each new FTP host that you want to create. If you make a mistake, select the row and click Delete Selected Row. When you are finished, click Next.
Step 4 In the Save the FTP Hosts pane, complete the following substeps:
a. In the Available NEs list, select the NEs on which to add the new FTP hosts and click Add. The NEs move to the Selected NEs list.
b. In the Job Comments area, enter comments about the bulk FTP host creation, if needed.
c. In the Time (time zone) area, set a time for the operation. Click Now to begin FTP host creation immediately, or click At Time and specify when to begin the operation. You can specify a time based on 5-minute increments. The time zone can be GMT, a user-defined offset from GMT, or local time, depending on what is specified in the User Preferences dialog box.
d. Click Finish.
Step 5 To view the results of the operation, check the Job Monitor table (Administration > Job Monitor). After the bulk FTP host creation succeeds, the details are displayed in the NE Explorer node properties pane > Network tab > FTP Hosts subtab for each NE.
5.3.10.3 Modifying an FTP Host
Step 1 In the Domain Explorer tree, select the NE that contains the FTP that you want to modify and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Network tab; then, click the FTP Hosts subtab.
Step 3 Modify the following fields in the FTP Hosts subtab:
•FTP Host Address—Display only.
•Prefix Length—Display only.
•Enable FTP Relay—Check this check box to enable FTP relay. If FTP relay is disabled, the FTP Relay Timer field is dimmed.
•FTP Relay Timer—Modify the number of minutes for the FTP relay to continue, after which time the FTP relay resumes blocking all FTP access for the ENEs.
Step 4 Click Apply. The modified FTP host appears in the FTP Hosts subtab.
5.3.10.4 Deleting an FTP Host
Step 1 In the Domain Explorer tree, select the NE that contains the FTP host and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the node properties pane, click the Network tab; then, click the FTP Hosts subtab.
Step 3 Select the FTP host that you want to delete; then, click the Delete button.
Step 4 In the confirmation dialog box, click Yes. The FTP host disappears from the FTP Hosts subtab.
5.3.11 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.12 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.
Note IPPM is not supported for the CTC-based ONS 15305 R3.0.
Step 1 In the Domain Explorer, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 Select an LTE card. The following table lists the LTE cards.
Table 5-17 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.13 Enabling Pointer Justification Count Monitoring for CTC-Based NEs
Note Pointer justification count monitoring is not available for the ONS 15600 SONET and ONS 15600 SDH NEs.
Pointers are used in CTC-based NEs to compensate for frequency and phase variations. They provide a way to align the phase variations in STS and VT payloads. Pointer justification counts indicate timing differences on SONET networks.
There are positive pointer justification count (PPJC) and negative pointer justification count (NPJC) parameters. PPJC is a count of path-detected (PPJC-Pdet) or path-generated (PPJC-Pgen) positive pointer justifications. NPJC is a count of path-detected (NPJC-Pdet) or path-generated (NPJC-Pgen) negative pointer justifications depending on the specific PM name.
A consistent pointer justification count indicates clock synchronization problems between nodes. A difference between the counts means the node transmitting the original pointer justification has timing variations with the node detecting and transmitting this count. Positive pointer adjustments occur when the frame rate of the synchronous payload envelope (SPE) is too slow in relation to the rate of the STS-1.
To enable performance monitoring of the pointer justification count:
Step 1 In the Domain Explorer, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 Select an LTE card. See Table 5-17 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.14 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 General tab.
Step 3 Click the Power Monitor subtab.
Step 4 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—Display only.
Note You can set thresholds in 0.5 VDC increments.
Step 5 Click Apply.
5.3.15 Changing the Power Monitoring Threshold for the ONS 15600 SONET and ONS 15600 SDH
Step 1 In the Domain Explorer tree, select an 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 General tab.
Step 3 Click the Power Monitor subtab.
Step 4 In the Voltage Thresholds area, select the threshold for the following:
•ELWBATVG—Very low battery voltage.
•LWBATVG—Low battery voltage. Available on ONS 15600 SONET only.
•HIBATVG—High battery voltage. Available on ONS 15600 SONET only.
•EHIBATVG—Very high battery voltage.
•Current Voltage Environment—Display only.
Note You can set thresholds in 0.5 VDC increments.
Step 5 Click Apply.
5.3.16 Creating an Ethernet Threshold
The Create Ethernet Threshold dialog box allows you to create new Ethernet thresholds for the G1000-2, G1000-4, ETH100, ETH1000, and ML-series cards for ONS 15327, ONS 15454 SONET, and ONS 15454 SDH NEs.
Step 1 In the Domain Explorer, select a CTC-based NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the NE Explorer tree, select an Ethernet card.
Step 3 Click the Thresholds tab.
Step 4 Click Create. The Create Ether Thresholds dialog box opens. The following table provides descriptions.
Step 5 After making your selections, click OK.
Step 6 Click Apply.
Table 5-18 Field Descriptions for the Create Ethernet Thresholds Dialog Box
Field
|
Description
|
Slot
|
Select a slot for the new Ethernet threshold.
|
Port
|
Select a port for the selected slot. If you select All, the threshold is created on all ports for that slot. This operation might take several minutes to complete.
|
Variable
|
Select a variable for the new Ethernet threshold. The list of variables differs based on the type of card that is installed in the slot selected in the Slot field.
|
Alarm Type
|
Select an alarm type for the new Ethernet threshold. Available alarm types are Rising, Falling, and Rising and Falling.
|
Sample Type
|
Select a sample type for the new Ethernet threshold. Available sample types are Relative and Absolute.
|
Sample Period
|
Enter a sample period for the new Ethernet threshold. The sample period is measured in seconds.
|
Rising Threshold
|
Enter a rising threshold for the new Ethernet threshold. The value must be equal to or greater than the Falling Threshold value.
|
Falling Threshold
|
Enter a falling threshold for the new Ethernet threshold. The value must be equal to or less than the Rising Threshold value.
|
5.4 Synchronizing the Network for Optical Devices
Use the NE Explorer to synchronize the CTC-based NEs in your network. The following sections describe the synchronization settings in detail.
5.4.1 Synchronization Settings for the ONS 15310 CL, ONS 15310 MA SONET, ONS 15327, ONS 15454 SONET, and ONS 15600 SONET
Full Cisco IOS configuration synchronization is performed automatically by CTM to keep the NE and the CTM Data Provisioning Service synchronized. Full configuration resynchronization might be delayed depending on CTM server usage. For more information, see Chapter 7, "Provisioning Services and Connections."
Synchronization status messaging (SSM) is a SONET protocol that communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SONET Line layer. These messages enable SONET devices to automatically select the highest quality timing reference and to avoid timing loops.
SSM messages are either Generation 1 or Generation 2. Generation 1 is the first and most widely deployed SSM message set. Generation 2 is a newer version. If SSM is enabled, consult the timing reference documentation to determine which message set to use. The following tables show the Generation 1 and Generation 2 message sets.
Table 5-19 SSM Generation 1 Message Set
Message
|
Quality
|
Description
|
PRS
|
1
|
Primary reference source—Stratum 1
|
STU
|
2
|
Synchronization traceability unknown
|
ST2
|
3
|
Stratum 2
|
ST3
|
4
|
Stratum 3
|
SMC
|
5
|
SONET minimum clock
|
ST4
|
6
|
Stratum 4
|
DUS
|
7
|
Do not use for timing synchronization
|
RES
|
—
|
Reserved; quality level set by user
|
Table 5-20 SSM Generation 2 Message Set
Message
|
Quality
|
Description
|
PRS
|
1
|
Primary reference source—Stratum 1
|
STU
|
2
|
Sync traceability unknown
|
ST2
|
3
|
Stratum 2
|
TNC
|
4
|
Transit node clock
|
ST3E
|
5
|
Stratum 3E
|
ST3
|
6
|
Stratum 3
|
SMC
|
7
|
SONET minimum clock
|
ST4
|
8
|
Stratum 4
|
DUS
|
9
|
Do not use for timing synchronization
|
RES
|
—
|
Reserved; quality level set by user
|
Note Alarms relating to PM collection indicate that the load on the system is high. Reduce the load on the system before proceeding.
5.4.1.1 Setting Up External or Line Timing for CTC-Based SONET NEs
Step 1 Select an ONS 15310 CL, ONS 15310 MA SONET, ONS 15327, ONS 15454 SONET, or ONS 15600 SONET NE and choose Configuration > NE Explorer.
Step 2 In the node property pane, click the Timing tab. Fields shown depend on the NE that is selected.
Step 3 In the General Timing section of the General subtab, complete the following information:
•Timing Mode—Set to External if the NE derives its timing from a building integrated timing supply (BITS) source wired to the backplane pins; set to Line if timing is derived from an OC-N card that is optically connected to the timing node. A third option, Mixed, allows users to set external and line timing references.
Caution Because mixed timing can cause timing loops, Cisco does not recommend its use. Use this mode with care.
Note The Mixed option is not applicable to the ONS 15600 SONET.
•SSM Message Set—Choose the message set level supported by the network. If a Generation 1 node receives a Generation 2 message, the message will be mapped down to the next available Generation 1. For example, an ST3E message becomes an ST3.
•Revertive—If checked, the NE reverts to a primary reference source after the conditions that caused it to switch to a secondary timing reference are corrected.
•Reversion Time—If Revertive is checked, indicate the amount of time that the NE will wait before reverting back to its primary timing source.
•Quality of RES—If the timing source supports the reserved S1 byte, set the timing quality here. (Most timing sources do not use RES.) Qualities are displayed in descending quality order as ranges. For example, ST3 < RES < ST2 means the timing reference is higher than a Stratum 3 and lower than a Stratum 2.
Step 4 In the BITS Facilities section of the General subtab, complete the following information:
Note The BITS Facilities section sets the parameters for BITS1 and BITS2 timing references. Many of these settings are determined by the timing source manufacturer. If the equipment is timed through BITS Out, set the timing parameters to meet the requirements of the equipment.
•In State—If Timing Mode is set to External or Mixed, set In State for BITS 1 and/or BITS 2 to in service (IS), depending on whether one or both BITS input pin pairs on the backplane are connected to the external timing source. If Timing Mode is set to Line, set the In State to OOS (Out of Service).
•Out State—If equipment is connected to the node's BITS output pins on the backplane and you want to time the equipment from a node reference, set Out State for BITS 1 and/or BITS 2 to IS, depending on which BITS output pins are used for external equipment. If equipment is not attached to the BITS output pins, set the Out State to OOS.
•Coding—Set to the coding used by the BITS reference: B8ZS (binary 8-zero substitution) or AMI (alternate mark inversion).
•Framing—Set to the framing used by the BITS reference: ESF (Extended Superframe) or SF(D4) (Super Frame). SSM is not available with Super Frame.
•Sync Messaging—Check to enable SSM.
•AIS Threshold (Not applicable to the ONS 15600 SONET)—Sets the quality level where a node sends an alarm indication signal (AIS) from the BITS 1 Out and BITS 2 Out backplane pins. When a node times at or below the AIS threshold quality, an AIS is sent. This is used when SSM is disabled or when the frame is SF.
•LBO (Not applicable to the ONS 15600 SONET)—If you are timing an external device connected to the BITS Out pins, set the distance between the device and the NE. Options are 0-133 ft. (Cisco default), 134-266 ft., 267-399 ft., 400-533 ft., and 534-655 ft.
Step 5 In the Reference List subtab, complete the following information:
Note Reference lists define up to three timing references for the node and up to six BITS Out references. BITS Out references define the timing references used by equipment that can be attached to the node BITS Out pins on the backplane. If you attach equipment to BITS Out pins, you normally attach it to a node with Line mode because equipment near the External timing reference can be directly wired to the reference.
•NE References—Define up to three timing references (Ref-1, Ref-2, Ref-3). The node uses Reference 1 unless a failure occurs on that reference, in which case the node uses Reference 2. If that fails, the node uses Reference 3, which is typically set to Internal Clock. This is the Stratum 3 clock provided on the TCC+/TCC2 card. The options displayed depend on the Timing Mode setting:
–Timing Mode set to External—Options are BITS1, BITS2, and Internal Clock.
–Timing Mode set to Line—Options are the node's working OC-N cards (non-DWDM nodes), OSC cards (DWDM nodes), and Internal Clock. Select the cards and ports that are directly or indirectly connected to the node wired to the BITS source; that is, the node's trunk (span) cards. Set Reference 1 to the trunk card that is closest to the BITS source. For example, if slot 5 is connected to the node wired to the BITS source, select slot 5 as Reference 1.
–Timing Mode set to Mixed—Both BITS and optical cards are available, which allows you to set a mixture of external BITS and OC-N trunk cards as timing references.
•BITS 1 Out/BITS 2 Out—Define the timing references for equipment wired to the BITS Out backplane pins. BITS 1 Out and BITS 2 Out are enabled when BITS 1 and BITS 2 facilities are put in service. If Timing Mode is set to external, choose the OC-N card used to set timing. If Timing Mode is set to Line, you can choose an OC-N card or choose NE reference to have BITS 1 out and/or BITS 2 Out follow the same timing reference as the NE.
Step 6 In the Status subtab, complete the following information:
•NE Clock
–NE Reference—Set the NE timing reference to internal, BITS 1, or BITS 2.
–Status—Display only. Displays the status of the NE clock.
–Operations—Execute a switch on the NE timing reference.
•BITS 1 OUT
–BITS 1 Out—Set the BITS 1 Out timing reference.
–Status—Display only. Displays the status of the BITS 1 out timing reference.
–Operations—Execute a switch on the BITS 1 out timing reference.
•BITS 2 OUT
–BITS 2 Out—Set the BITS 2 Out timing reference.
–Status—Display only. Displays the status of the BITS 2 out timing reference.
–Operations—Execute a switch on the BITS 2 out timing reference.
Step 7 In the Timing Report subtab, you can view the timing status report summary for the node.
Step 8 Click Apply.
Note Refer to the relevant ONS 15310 CL, ONS 15310 MA, ONS 15327, ONS 15454, or ONS 15600 troubleshooting guide for timing-related alarms.
5.4.1.2 Setting Up Internal Timing for CTC-Based SONET NEs
If no BITS source is available, set up internal timing by timing all nodes in the ring from the internal clock of one node.
Caution Internal timing is Stratum 3 and not intended for permanent use. All nodes should be timed to a Stratum 2 or better primary reference source.
Complete the following steps to set up internal timing for CTC-based SONET NEs:
Step 1 Select an ONS 15310 CL, ONS 15310 MA SONET, ONS 15327, ONS 15454 SONET, or ONS 15600 SONET NE and choose Configuration > NE Explorer.
Step 2 In the node property pane, click the Timing tab. Fields shown depend on the NE that is selected.
Step 3 In the General Timing section of the General subtab, enter the following information:
•Timing Mode—Set to External.
•SSM Message Set—Set to Generation 1.
•Revertive—Not relevant for internal timing; the default setting (checked) is sufficient.
•Reversion Time—The default setting is sufficient.
•Quality of RES—Set to RES=DUS.
Step 4 In the BITS Facilities section of the General subtab, enter the following information:
•In State—Set BITS 1 and BITS 2 to OOS.
•Out State—Set BITS 1 and BITS 2 to OOS.
•Coding—Not relevant for internal timing. The default (B8ZS) is sufficient.
•Framing—Not relevant for internal timing. The default (ESF) is sufficient.
•Sync Messaging—Checked.
•AIS Threshold—Not available.
•LBO—Not relevant.
Step 5 In the Reference List subtab, enter the following information:
•NE References
–Ref-1—Set to Internal Clock.
–Ref-2—Set to Internal Clock.
–Ref-3—Set to Internal Clock.
•BITS 1 Out/BITS 2 Out—Set to None.
Step 6 Click Apply.
Step 7 In the Domain Explorer tree, select the node that you set up in Step 1 through Step 6 and choose Configuration > NE Explorer.
Step 8 In the Timing tab, enter the same information that was entered in Step 3, except for the following:
•In the General Timing section of the General subtab, set the Timing Mode field to Line.
•In the NE References section of the Reference List subtab:
–Ref-1—Set to the OC-N trunk (span) card (non-DWDM node) or OSC card (DWDM) with the closest connection to the node.
–Ref-2—Set to the OC-N trunk (span) card (non-DWDM node) or OSC card (DWDM) with the next closest connection to the node.
–Ref-3—Set to Internal Clock.
Step 9 Click Apply.
Step 10 Repeat Step 3 through Step 9 for each node in the ring that will be timed from the internal clock of the selected node.
5.4.2 Synchronization Settings for the ONS 15310 MA SDH, ONS 15454 SDH, and ONS 15600 SDH
SSM communicates information about the quality of the timing source. SSM messages are carried on the S1 byte of the SDH section overhead. These messages enable SDH devices to automatically select the highest quality timing reference and to avoid timing loops.
SSM messages are either Generation 1 or Generation 2. Generation 1 is the first and most widely deployed SSM message set. Generation 2 is a newer version. If you enable SSM for the ONS 15454 SDH, consult your timing reference documentation to determine which message set to use. The following table shows the SDH message set.
Table 5-21 SDH SSM Message Set
Message
|
Quality
|
Description
|
G811
|
1
|
Primary reference clock
|
STU
|
2
|
Synchronization traceability unknown
|
G812T
|
3
|
Transit node clock traceable
|
G812L
|
4
|
Local node clock traceable
|
SETS
|
5
|
Synchronous equipment
|
DUS
|
6
|
Do not use for timing synchronization
|
Note Alarms relating to PM collection indicate that the load on the system is high. Reduce the load on the system before proceeding.
5.4.2.1 Setting Up External or Line Timing for CTC-Based SDH NEs
Step 1 Select an ONS 15310 MA SDH, ONS 15454 SDH, or ONS 15600 SDH NE and choose Configuration > NE Explorer.
Step 2 In the node property pane, select the Timing tab. Fields shown depend on the NE that is selected.
Step 3 In the General Timing section of the General subtab, complete the following information:
•Timing Mode
–For the ONS 15310 MA SDH and ONS 15454 SDH:
Choose External if the ONS 15310 MA SDH or ONS 15454 SDH NE derives its timing from an MIC-C/T/P FMEC; choose Line if timing is derived from an STM-N card (non-DWDM node) or OSC card (DWDM node) that is optically connected to the timing node. A third option, Mixed, allows you to set external and line timing references.
–For the ONS 15600 SDH:
Choose External if the ONS 15600 SDH NE derives its timing from a BITS source wired to the backplane; choose Line if timing is derived from an STM-N card that is optionally connected to the timing node. A third option, Mixed, allows you to set external and line timing references.
Caution Because mixed timing may cause timing loops, Cisco does not recommend its use. Use this mode with care.
•Revertive—If checked, the NE reverts to a primary reference source after the conditions that caused it to switch to a secondary timing reference are corrected.
•Reversion Time—If Revertive is checked, indicate the amount of time the NE will wait before reverting to its primary timing source.
•SSM Message Set (Applicable to the ONS 15600 SDH)—Enabled only if T1 signal type is selected. Choose the message set level supported by the network.
Step 4 In the BITS Facilities section of the General subtab, complete the following information:
Note The BITS Facilities section sets the parameters for your BITS 1 and BITS 2 timing references. Many of these settings are determined by the timing source manufacturer. If equipment is timed through BITS Out, you can set timing parameters to meet the requirements of the equipment.
•Facility Type—Choose the facility type that applies to the signal supported in your market. For example, 64 KHz is used in Japan. E1, 2.048 MHz, and 64 KHz are physical signal modes used to transmit the external clock (from a GPS, for example) to BITS.
•In State—If Timing Mode is set to External or Mixed, set In State for BITS 1 and/or BITS 2 to in service (IS), depending whether one or both BITS input pin pairs on the backplane are connected to the external timing source. If Timing Mode is set to Line, set In State to Locked.
•Out State—If equipment is connected to the node's BITS output pins on the backplane and you want to time the equipment from a node reference, set Out State for BITS 1 and/or BITS 2 to IS, depending on which BITS output pins are used for external equipment. If equipment is not attached to the BITS output pins, set Out State to Locked.
•State (Applicable to the ONS 15600 SDH)—For nodes using external timing, set State to Unlocked.
•Coding—Choose the coding used by your BITS reference: HDB3 or AMI. If you selected 2.048 MHz or 64 KHz, the coding option is disabled.
•Framing—Choose the framing used by your BITS reference: unframed, FAS, FAS + CAS, FAS + CRC, or FAS + CAS + CRC. If you selected 2.048 MHz or 64 KHz, the framing option is disabled.
•Sync Messaging—Select the check box to enable SSM. SSM is used to deliver clock quality. SSM options supported in SDH are G811, STU, G812T, G812L, SETS, DUS (ordered from high quality to low quality). If you selected 2.048 MHz, 64 KHz, or E1 with FAS, or if FAS + CAS framing is provisioned, the SSM option is disabled.
•AIS Threshold (Applicable to the ONS 15310 MA SDH and ONS 15454 SDH)—Sets the quality level at which a node sends an alarm indication signal (AIS) from the BITS 1 Out and BITS 2 Out FMEC connectors. When a node times at or below the AIS threshold quality, an AIS is raised. (The AIS threshold is used when SSM is disabled or framing is set to unframed, FAS, or FAS + CAS.)
•LBO (Applicable to the ONS 15310 MA SDH and ONS 15454 SDH)—Choose a BITS cable length. Line build out (LBO) relates to the BITS cable length.
•Cable Type (Applicable to the ONS 15600 SDH)—Choose 75 ohm or 120 ohm.
•Sa bit—Choose one of 5 Sa bits (4, 5, 6, 7, or 8). The Sa bit transmits the SSM message. If you selected 2.048 MHz or 64 KHz, the Sa bit option is disabled.
Step 5 In the Reference List subtab, complete the following information:
Note Reference lists define up to three timing references for the node and up to six BITS Out references. BITS Out references define the timing references used by equipment attached to the node's MIC-C/T/P FMEC Timing A Out and Timing B Out connectors. If you attach equipment to the Timing A Out or Timing B Out connector, you normally attach it to a node with line mode because equipment near the external timing reference can be directly wired to the reference.
•NE References—Allows you to define three timing references (Ref-1, Ref-2, Ref-3). The node uses Reference 1 unless a failure occurs on that reference, in which case the node uses Reference 2. If Reference 2 fails, the node uses Reference 3, which is typically set to Internal Clock. The internal clock is the Stratum 3 clock provided on the TCC2. The options displayed depend on the Timing Mode setting:
–Timing Mode set to External—Options are BITS 1, BITS 2, and Internal Clock.
–Timing Mode set to Line—For the ONS 15310 MA SDH and ONS 15454 SDH, options are the node's working OC-N cards (non-DWDM nodes), OSC cards (DWDM nodes), and Internal Clock. For the ONS 15600 SDH, options are Internal Clock and the node's STM-N ports, except for the ports that have been specified as protection ports in 1+1 groups (Linear Multiplex Section Protection [LMSP] groups). Select the cards and ports that are directly or indirectly connected to the node wired to the BITS source; that is, select the node's trunk cards. Set Reference 1 to the trunk card that is closest to the BITS source. For example, if Slot 5 is connected to the node wired to the BITS source, select Slot 5 as Reference 1.
–Timing Mode set to Mixed—Both BITS and optical cards are available, allowing you to set a mixture of external BITS and optical trunk (span) cards as timing references.
•BITS 1 Out/BITS 2 Out References (Applicable to the ONS 15310 MA SDH and ONS 15454 SDH)—Define the timing references for equipment connected to the Timing A Out or Timing B Out FMEC connector. Normally, Timing Out is used with line nodes, so the options displayed are the working optical cards. Timing A Out and Timing B Out are enabled as soon as BITS 1 and BITS 2 facilities are placed in service.
Step 6 In the Status subtab, complete the following information:
•NE Clock
–NE Reference—Set the NE timing reference to internal, BITS 1, or BITS 2.
–Status—Display only. Displays the status of the NE clock.
–Operations—Execute a switch on the NE timing reference.
•BITS 1 OUT
–BITS 1 Out—Set the BITS 1 out timing reference.
–Status—Display only. Displays the status of the BITS 1 out timing reference.
–Operations—Execute a switch on the BITS 1 out timing reference.
•BITS 2 OUT
–BITS 2 Out—Set the BITS 2 out timing reference.
–Status—Display only. Displays the status of the BITS 2 out timing reference.
–Operations—Execute a switch on the BITS 2 out timing reference.
Step 7 In the Timing Report subtab, you can view the timing status report summary for the node.
Step 8 Click Apply.
Note Refer to the Cisco ONS 15454 SDH Troubleshooting Guide or Cisco ONS 15600 SDH Troubleshooting Guide for timing-related alarms.
5.4.2.2 Setting Up Internal Timing for CTC-Based SDH NEs
If no BITS source is available, you can set up internal timing by timing all nodes in the ring from the internal clock of one node.
Caution Internal timing is Stratum 3 and not intended for permanent use. All nodes should be timed to a Stratum 2 or better primary reference source.
Complete the following steps to set up internal timing for CTC-based SDH NEs:
Step 1 Select an ONS 15310 MA SDH, ONS 15454 SDH, or ONS 15600 SDH NE and choose Configuration > NE Explorer.
Step 2 In the node property pane, select the Timing tab.
Step 3 In the General Timing section of the General subtab, enter the following information:
•Timing Mode—Choose External.
•Revertive—Not applicable for internal timing; the default setting (checked) is sufficient.
•Reversion Time—Not applicable; leave unchanged.
Step 4 In the BITS Facilities section of the General subtab, enter the following information:
•Facility Type—Choose the facility type that applies to the signal supported in your market. For example, 64 KHz is used in Japan. E1, 2.048 MHz, and 64 KHz are physical signal modes used to transmit the external clock (from a GPS, for example) to BITS.
•In State—Set BITS 1 and BITS 2 to Locked.
•Out State—Set BITS 1 and BITS 2 to Locked.
•State (Applicable to the ONS 15600 SDH)—Set BITS 1 and BITS 2 to Locked.
•Coding—Not relevant for internal timing; the default is sufficient.
•Framing—Not relevant for internal timing; the default is sufficient.
•Sync Messaging—Checked automatically. SSM is used to deliver clock quality. SSM options supported in SDH are G811, STU, G812T, G812L, SETS, DUS (ordered from high quality to low quality). If you selected 2.048 MHz or 64 KHz, the SSM option is disabled.
•AIS Threshold—Not relevant for internal timing.
•LBO—Not relevant for internal timing.
•Sa bit—Not relevant for internal timing.
Step 5 In the Reference List subtab, enter the following information:
•NE References
–Ref-1—Set to Internal Clock.
–Ref-2—Set to Internal Clock.
–Ref-3—Set to Internal Clock.
•BITS 1 Out/BITS 2 Out (Applicable to the ONS 15310 MA SDH and ONS 1545 SDH)—Set to None.
Step 6 Click Apply.
Step 7 In the Domain Explorer tree, select the node that you set up in Step 1 to Step 6 and choose Configuration > NE Explorer.
Step 8 In the Timing tab, complete the following:
•In the General Timing section of the General subtab:
–Timing Mode—Set to Line.
–Revertive—Not applicable for internal timing; the default setting is sufficient.
–Reversion Time—Not applicable for internal timing; the default setting is sufficient.
•In the NE References section of the Reference List subtab:
–Ref-1—Set to the STM-N trunk card with the closest connection to the node.
–Ref-2—Set to the STM-N trunk card with the next closest connection to the node.
–Ref-3—Set to Internal Clock.
Step 9 Click Apply.
Step 10 Repeat Steps 7 through 9 for each node that will be timed by the node.
5.5 Synchronizing the Network for MGX Voice Gateway Devices
The CTM server and managed nodes must be synchronized with the same date and time. If the CTM server and managed nodes do not have the same date and time, there might be inconsistencies in retrieving time-sensitive data.
5.5.1 Viewing Clock Sources
CTM supports manual clock configuration. This configures both a primary and secondary clock source, which are distributed throughout the network. The secondary clock source takes over if the primary clock source fails. You can configure a network setup with one master clock source, and a secondary to ensure network clock stability.
On Cisco MGX 8850 (PXM45) switches, clock source configuration is done on a PXM45 card, and clock sourcing information is passed to other nodes over AXSM lines.
Clock synchronization is done directly on the Cisco MGX 8880 using the CLI.
The following topics are used to manage and configure clock sources:
•Configuring Global Clocking
•Displaying the List of Available Clock Sources
•Displaying the List of Manual Clock Sources
•Creating a Manual Clock Source
5.5.1.1 Configuring Global Clocking
Step 1 In the Domain Explorer tree, select the node and choose Configuration > MGX Voice Gateway > Configuration Center.
Step 2 Drag and drop the node from the Hierarchy pane to the right-most pane.
Step 3 Click the Elements tab to display the Configuration Window for Elements.
Step 4 Click the Clocking tab to display the Global Clocking Configuration window.
Step 5 Choose Global Clocking Configuration from the Category drop-down list.
Step 6 The Distribution Method is manual. This specifies that the network clock source is statically configured in the device.
Step 7 Enter the maximum network diameter, measured in hops, in the Max Diameter field. The range is from 3 to 20. The Cisco default value is 20.
•Change Time—The time when the global clocking was configured.
•Clock Source—The clock source from the list of available clock sources.
Step 8 Click Apply to apply the global clocking configuration settings.
5.5.1.2 Displaying the List of Available Clock Sources
Step 1 In the Domain Explorer, right-click the PNNI node from the Hierarchy pane and choose Configuration Center.
Step 2 Click the Elements tab to display the Configuration Window for Elements.
Step 3 Click the Clocking tab to display Clocking Configuration window.
Step 4 Choose Available Clock Sources to display the list of available clock sources from the Category drop-down list.
5.5.1.3 Displaying the List of Manual Clock Sources
Step 1 In the Domain Explorer, right-click the PNNI node from the Hierarchy pane and choose Configuration Center.
Step 2 Click the Elements tab to display the Configuration Window for Elements.
Step 3 Click the Clocking tab to display Clocking Configuration window.
Step 4 Choose Manual Clock Sources to display the list of available manual clock sources from the Category drop-down list.
5.5.1.4 Creating a Manual Clock Source
Step 1 In the Domain Explorer, right-click the PNNI node from the Hierarchy pane and choose Configuration Center.
Step 2 Click the Elements tab to display the Configuration Window for Elements.
Step 3 Click the Clocking tab to display Clocking Configuration window.
Step 4 Choose Manual Clock Sources from the Category drop-down list.
Step 5 Click Create to display the Manual Clock Source Configuration Window.
Step 6 Choose one of the following clock source options from the Priority drop-down list:
•primary— Configures an available network clock source to be the primary manual clock source.
•secondary—Configures an available network clock source to be the secondary manual clock source.
•default—Configures an available network clock source to be the default manual clock source.
Step 7 Enter the index value that is used to identify the primary, secondary, or default manual clock source in the Clock Source Index field.
Step 8 Click Apply to create a manual clock source.
5.6 Configuring the MDS 9000
Use the Fabric Manager to manage and configure MDS 9000 devices. The Fabric Manager provides:
•Fabric discovery and topology mapping
•Multiple switch configuration
•VSAN and zone management
•Fabric checker, switch health, and zone merge analysis
•End-to-end connectivity and traceroute analysis
To launch the Fabric Manager:
Step 1 In the Domain Explorer tree, select the MDS 9000 NE that will be configured and choose Configuration > MDS 9000 > Launch Fabric Manager. The initial Java-based Fabric Manager screen launches.
Note If the Fabric Manager is not already installed, you will be guided through the installation steps.
Step 2 In the Open Fabric dialog box, enter your username and password. The default username is admin; the default password is blank.
Step 3 Click Options.
Step 4 Fill in the following fields:
•FM Server—Leave it set to localhost (the default).
•Fabric Seed Switch—Specify the IP address of the seed MDS 9000 node.
•Read Community—Enter the read community string; the default is public.
•Write Community—Enter the write community string; the default is private.
•SNMPv3—Check this check box to log in using SNMPv3. (Leave the check box unchecked to log in using SNMPv2.) If you check SNMPv3, fill in the User Name, Password, and Privacy Password fields for SNMPv3 authentication.
•SHA—Specify the authentication protocol to use for authenticating the user. Values are MD5 (the default) or SHA.
•AES—Specify the type of privacy protocol to use for encryption. Values are DES (the default) or AES.
•Load from Database—The Fabric Manager stores discovered information in the database. If you load from the database, information is retrieved faster and you are notified of changes since the last discovery. (Note that you lose enclosure information.) The default is to load from the database.
•Use SNMP Proxy—SNMP uses UDP. The ports that it uses are random. If you are working through a restricted firewall, you can set up a Fabric Manager server inside the firewall, open preconfigured TCP ports in the firewall, and use a TCP tunnel to proxy SNMP traffic from the Fabric Manager client through the Fabric Manager server.
Step 5 Click Open. The Fabric Manager application launches. Refer to the MDS 9000 hardware documentation for information about using Fabric Manager.
5.7 Configuring the ONS 15216
Step 1 In the Domain Explorer tree, select the ONS 15216 NE that will be configured and choose Configuration > NE Explorer (or click the Open NE Explorer tool). The NE Explorer window displays configuration information for the selected ONS 15216 NE.
Step 2 Make any necessary changes to the fields in the properties pane that corresponds to the NE or its components. Click Apply to save the changes to the CTM database and apply the changes to the NE.
5.8 Configuring the ONS 15302 and ONS 15305 Earlier than R3.0
Within CTM, use Cisco Edge Craft to configure ONS 15302 and ONS 15305 NEs earlier than R3.0. (For the ONS 15305 R3.0, use the CTM NE Explorer. See Configuring the ONS 15305 R3.0, ONS 15310 CL, ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15327, ONS 15454 SONET, and ONS 15454 SDH.) Select the ONS 15302 or ONS 15305 NE in the Domain Explorer tree and choose Configuration > ONS 15302 or ONS 15305 > Launch Cisco Edge Craft. Refer to the "Installing the CTM R9.0 Client and Cisco Edge Craft" chapter in the Cisco Transport Manager Release 9.0 Installation Guide for instructions on how to start Cisco Edge Craft.
Note To configure ONS 15302 and ONS 15305 NEs through Cisco Edge Craft, refer to Cisco Edge Craft Software Guide.
5.9 Configuring the ONS 15305 R3.0, ONS 15310 CL, ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15327, ONS 15454 SONET, and ONS 15454 SDH
You can use the CTM NE Explorer, CTC, or TL1 to configure CTC-based NEs.
5.9.1 Launching the CTM NE Explorer
Step 1 In the Domain Explorer tree, select the NE that will be configured and choose Configuration > NE Explorer. The NE Explorer window displays configuration information about the selected NE.
Step 2 Make any necessary changes to the fields in the properties pane that corresponds to the NE or its components. Click Apply to save the changes to the CTM database and apply the changes to the NE.
5.9.2 Launching CTC
Only the latest CTC release is launched from CTM, regardless of the NE release you selected. If you need to use other CTC releases, launch CTC from a web browser and connect directly to the NE that has the required CTC release.
Step 1 In the Domain Explorer tree, Subnetwork Explorer tree, or Network Map, select the NE that will be configured and choose Configuration > CTC-Based SONET NEs or CTC-Based SDH NEs > Launch CTC.
Step 2 The Launch CTC dialog box opens with the Username and Password fields filled in with the values contained in the CTM Users table for that user. If the CTC Username value for that user is empty in the CTM Users table, the fields in the Launch CTC dialog box are empty; enter the username and password.
Step 3 Check the Enable Socks Server check box to set the CTC DSS property (ctc.proxy.designatedgnes), which contains all of the GNEs present in the network partition. This feature speeds up network discovery and enables the cross-launch of CTC on all NEs that are not directly connected to the LAN.
Step 4 Click OK.
5.9.3 Launching TL1
In the Domain Explorer tree, Subnetwork Explorer tree, or Network Map, select the NE that will be configured and choose Configuration > CTC-Based SONET NEs or CTC-Based SDH NEs > Launch TL1 Interface. This launches a Telnet session directed at the TL1 port on the NE.
5.9.4 Provisioning an ONS 15305 R3.0, ONS 15310 CL, ONS 15310 MA SONET, ONS 15310 MA SDH, ONS 15327, ONS 15454 SONET, or ONS 15454 SDH Card Slot
You can use this procedure to reset, delete, or change a card.
Step 1 In the Domain Explorer tree, select the NE that will be configured and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the tree view or in the shelf view of the node properties pane, right-click an unprovisioned slot and choose Add Card from the shortcut menu.
Step 3 Select the type of card. The list of cards in the Add Card menu depends on the NE and the slot selected.
Step 4 Click OK in the confirmation dialog box.
It might take several minutes for the newly provisioned card to be added on the NE. During this time, it is possible to add additional cards on the same slot. However, only the first card added will be shown in the NE Explorer tree view and in the shelf view.
5.9.5 Resetting a Card
Step 1 In the Domain Explorer tree, select the NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the tree view or in the shelf view of the node properties pane, right-click the card that you want to reset and choose Reset Card from the shortcut menu.
Step 3 Click OK in the confirmation dialog box.
5.9.6 Deleting a Card
Step 1 In the Domain Explorer tree, select the NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the tree view or in the shelf view of the node properties pane, right-click the card that you want to delete and choose Delete Card from the shortcut menu.
Note For the ONS 15310 CL, ONS 15310 MA SONET, and ONS 15310 MA SDH, you cannot delete the CTX card.
Step 3 Click OK in the confirmation dialog box.
5.9.7 Changing a Card
Step 1 In the Domain Explorer tree, select the NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the tree view or in the shelf view of the node properties pane, right-click the card that you want to change and choose Change Card from the shortcut menu.
Note For the ONS 15310 CL, ONS 15310 MA SONET, and ONS 15310 MA SDH, you cannot change the CTX card.
Step 3 Select the type of the new card. The list of cards in the Change Card menu depends on the slot selected.
Step 4 Click OK in the confirmation dialog box.
Tip If you receive a mismatched equipment alarm (MEA) after changing a card, troubleshoot the MEA with the Cisco ONS 15454 Troubleshooting Guide.
5.9.8 Inserting an AIS-V on an STS-1 SD-P
Note This procedure does not apply to the ONS 15454 SDH.
Step 1 In the Domain Explorer tree, select the ONS 15305 R3.0, ONS 15310 CL, ONS 15310 MA SONET, ONS 15327, or ONS 15454 SONET 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 AIS-V Insertion on STS-1 Signal Degrade-Path area, complete the following substeps:
a. Check the Insert AIS-V on STS-1 SD-P check box to insert an AIS-V on the STS-1 Signal Degrade-Path.
b. Click OK in the warning message dialog box.
c. Select the SD-P BER from the drop-down list.
Step 4 Click Apply.
5.9.9 Changing Secure Config Mode—ONS 15454 SONET or ONS 15454 SDH
The TCC2P card supports secure config mode. When the secure mode is ON, the NE has two IP addresses, one for the backplane and one for the front port. The front port IP address is used by the DCC-connected NEs. The secure config mode feature applies to the ONS 15454 SONET R5.0 and ONS 15454 SDH R5.0 and later.
The Secure Config Mode subtab allows you to configure the secure config mode. The fields shown depend on whether the NE is in secure mode. For example, the Backplane Ethernet Port values are displayed only when the NE is in secure mode.
Step 1 In the Domain Explorer tree, select the 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 Secure Config Mode subtab.
Step 4 Click the Change Mode button. The Change Secure Mode dialog box opens.
Note The Change Mode button is enabled only if an active TCC2P card exists on the NE.
Step 5 Complete one of the following options, depending on your configuration:
•If you are changing the secure mode from secure to nonsecure, fill in the fields described in Table 5-22.
•If you are changing the secure mode from nonsecure to secure, fill in the fields described in Table 5-23.
Step 6 Click OK.
Table 5-22 Field Descriptions for the Change Secure Mode Dialog Box when the NE Is Secure
Field
|
Description
|
Node IP Address
|
Backplane LAN Port
|
Click this radio button to use the IP address currently assigned to the backplane LAN port as the IP address of the NE in normal (nonsecure) mode.
|
TCC LAN Port
|
Click this radio button to use the IP address currently assigned to the TCC LAN port as the IP address of the NE in normal (nonsecure) mode.
|
New IP Address
|
Click this radio button to use neither the backplane nor the TCC LAN port IP address, but instead assign a completely new IP address to the NE.
|
IP Address
|
(Available only if New IP Address is selected) Enter the backplane IP address.
|
Net/Subnet Mask Length
|
(Available only if New IP Address is selected) Enter the mask length of the secure IP address. Use the up or down arrows to change the mask length.
|
Default Router
|
(Available only if New IP Address is selected) Enter the address of the default router for this NE.
|
Gateway Settings
|
Enable Proxy Server on Port
|
If checked, the ONS 15454 SONET or ONS 15454 SDH serves as a proxy for connections between the CTM server and NEs that are DCC-connected to the proxy NE. The CTM server establishes connections to DCC-connected nodes through the proxy node. The CTM server can connect to nodes that it cannot directly reach from the host on which it runs. The proxy server uses port number 1080.
If unchecked, the node does not proxy.
|
End Network Element (ENE)
|
(Available only if Enable Proxy Server on Port is checked) Enables the node to proxy as an ENE.
|
Gateway Network Element (GNE)
|
(Available only if Enable Proxy Server on Port is checked) Enables the node to proxy as a GNE.
|
Proxy-only
|
(Available only if Enable Proxy Server on Port is checked) Enables proxy only.
|
Table 5-23 Field Descriptions for the Change Secure Mode Dialog Box when the NE Is Not Secure
Field
|
Description
|
TCC Ethernet Port
|
IP Address
|
Enter the TCC Ethernet port IP address.
|
Net/Subnet Mask Length
|
Enter the mask length of the secure IP address. Use the up or down arrows to change the mask length.
|
Backplane Ethernet Port
|
IP Address
|
Enter the backplane Ethernet port IP address.
|
Default Router
|
Enter the address of the default router for this NE.
|
Subnet Mask
|
Enter the subnet mask of the secure IP address.
|
Gateway Settings
|
Enable Proxy Server on Port
|
If checked, the ONS 15454 SONET or ONS 15454 SDH serves as a proxy for connections between the CTM server and NEs that are DCC-connected to the proxy NE. The CTM server establishes connections to DCC-connected nodes through the proxy node. The CTM server can connect to nodes that it cannot directly reach from the host on which it runs. The proxy server uses port number 1080.
Note When you are changing the config mode to secure, you cannot disable proxy.
If unchecked, the node does not proxy.
|
End Network Element (ENE)
|
(Available only if Enable Proxy Server on Port is checked) Enables the node to proxy as an ENE.
|
Gateway Network Element (GNE)
|
(Available only if Enable Proxy Server on Port is checked) Enables the node to proxy as a GNE.
|
Proxy-only
|
(Available only if Enable Proxy Server on Port is checked) Enables proxy only.
|
5.10 Configuring the ONS 15501, ONS 15530, and ONS 15540
Within CTM, use CiscoView to configure ONS 15501, ONS 15530, and ONS 15540 NEs and monitor their configuration and performance. CiscoView is a browser-based, graphical, SNMP-based, device management tool that provides real-time views of ONS 15501, ONS 15530, and ONS 15540 NEs. These views deliver a continuously updated physical picture of device configuration and performance. CiscoView allows:
•Configuration of parameters for devices, cards, and interfaces
•Monitoring of real-time statistics for interfaces, resource utilization, and device performance
•Management of dual CPUs
CiscoView is embedded in flash memory for the ONS 15540 and ONS 15530.
Launch CiscoView from the Domain Explorer, Network Map, or Subnetwork Explorer by using one of the following options:
•Double-click the ONS 15501, ONS 15530, or ONS 15540 NE
•Select the NE and choose Configuration > ONS 155XX > Launch CiscoView
•Right-click the NE and choose Launch CiscoView
Note If CiscoView is not installed on the NE or if you need to install an updated version, see the relevant hardware installation and configuration guide.
CiscoView configuration and monitoring dialog boxes include online help. For information about using the CiscoView application, see Appendix J, "Using CiscoView to Configure and Monitor ONS 15501, ONS 15530, and ONS 15540 NEs."
5.11 Configuring the ONS 15600 SONET and ONS 15600 SDH
You can use the CTM NE Explorer or CTC to configure ONS 15600 SONET and ONS 15600 SDH NEs.
5.11.1 Launching the CTM NE Explorer
Step 1 In the Domain Explorer tree, select the ONS 15600 SONET or ONS 15600 SDH NE that will be configured and choose Configuration > NE Explorer (or click the Open NE Explorer tool). The NE Explorer window displays configuration information about the selected ONS 15600 SONET or ONS 15600 SDH NE.
Step 2 Make any necessary changes to the fields in the properties pane that corresponds to the NE or its components. Click Apply to save the changes to the CTM database and apply the changes to the NE.
5.11.2 Launching CTC
See Launching CTC, which also applies to ONS 15600 SONET and ONS 15600 SDH NEs.
5.11.3 Resetting a Card
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 Click the Shelf View tab.
Step 3 On the shelf graphic, right-click a card and select either Hard Reset Card or Soft Reset Card from the shortcut menu.
Step 4 Click OK in the confirmation message box.
5.11.4 Deleting a Card
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 tree view or in the shelf view of the node properties pane, right-click the card that you want to delete and choose Delete Card from the shortcut menu.
Step 3 Click OK in the confirmation dialog box.
5.11.5 Changing a Card
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 tree view or in the shelf view of the node properties pane, right-click the card that you want to change and choose Change Card from the shortcut menu.
Step 3 Select the type of the new card. The list of cards in the Change Card menu depends on the slot selected.
Step 4 Click OK in the confirmation dialog box.
5.12 Configuring the ONS 15800, ONS 15801, and ONS 15808
Step 1 In the Domain Explorer tree, select the ONS 15800, ONS 15801, or ONS 15808 NE that will be configured and choose Configuration > NE Explorer (or click the Open NE Explorer tool). The NE Explorer window displays configuration information about the selected NE.
Step 2 Make any necessary changes to the fields in the properties pane that corresponds to the NE or its components. Click Apply to save the changes to the CTM database and apply the changes to the ONS 15800, ONS 15801, or ONS 15808 NE.
Step 3 If the user input is not saved successfully, a warning message is displayed. Click Details to see which values were not updated; then, click OK and edit the values.
Note The ONS 1580x can also be configured using TL1. In the Domain Explorer tree, select the NE that will be configured and choose Configuration > ONS 15800, ONS 15801, or ONS 15808 > Launch TL1 Interface. This launches a Telnet session directed at the TL1 port on the NE. You can launch up to a maximum of five TL1 sessions.
5.12.1 Synchronizing the ONS 15800, ONS 15801, and ONS 15808 Configuration and Inventory
To manually synchronize the ONS 15800, ONS 15801, or ONS 15808 configuration and inventory, complete the following steps:
Step 1 In the Domain Explorer tree, select an ONS 15800, ONS 15801, or ONS 15808 NE and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the NE Explorer window, choose File > Refresh Data.
Step 3 In the Refresh Data dialog box, click the From Network Element radio button; then, click OK.
Step 4 Click Yes to confirm the synchronization.
5.12.2 Manually Resetting the ONS 15800, ONS 15801, or ONS 15808
Use the Reset Network Element option to perform a software reset of the TL1 agent. This procedure does not affect traffic, but CTM will lose connectivity to the ONS 15800, ONS 15801, or ONS 15808 until the reset is complete.
Caution While the ONS 15800, ONS 15801, or ONS 15808 is booting, the Reset Network Element option is unavailable. Before manually resetting an ONS 15800, ONS 15801, or ONS 15808, take into account that the NE will be unavailable during the reset.
Complete the following steps to manually reset the ONS 15800, ONS 15801, or ONS 15808 NE:
Step 1 In the Domain Explorer window, select an ONS 15800, ONS 15801, or ONS 15808 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the NE Explorer window, choose File > Reset Network Element.
Step 3 Click Yes in the confirmation dialog box.
5.12.3 Tagging an ONS 15800, ONS 15801, or ONS 15808 Module as Out of Service
To suppress the alarms from an ONS 15800, ONS 15801, or ONS 15808 module, tag the module as Out of Service.
Step 1 In the Domain Explorer tree, select an ONS 15800, ONS 15801, or ONS 15808 and choose Configuration > NE Explorer (or click the Open NE Explorer tool).
Step 2 In the NE Explorer tree, select a provisioned slot to open its properties pane. Click the Identification tab.
Step 3 In the State field, choose Out of Service.
Step 4 Click Apply.
5.13 Configuring MGX Voice Gateway Devices
Note CTM R9.0 supports AXSM-16-T3E3/B in 8830/B with PXM45/c.
This section helps you use the Configuration Center and Chassis View to configure your MGX Voice Gateway devices, and contains the following information:
•How Do I Manage My Network with the Chassis View?
•How Do I Manage My Network with the Configuration Center?
•How Do I Manage Templates for NEs?
•How Do I Configure MGX Voice Gateway Devices?
•How Do I Create or Modify APS?
5.13.1 How Do I Manage My Network with the Chassis View?
The Chassis View provides a graphical view of equipment status for the operational and alarm status of each card, port, or line, which is represented with a predefined color. By default, the front view opens (click the Rear View tab to switch views).
This section contains the following information:
•Launching Chassis View
•Navigating with Chassis View
•Accessing NEs
•Chassis View LED Colors
5.13.1.1 Launching Chassis View
To launch Chassis View from the Domain Explorer:
•Click a node; then, choose Configuration > MGX Voice Gateway > Chassis View.
To launch Chassis View from the Diagnostic Center, Configuration Center, or Statistics Report, do any of the following:
•Click the Chassis View tool from the toolbar.
•Choose Tools > Chassis View.
•Right-click an NE in the Hierarchy pane and choose Chassis View from the pop-up menu. Once the Chassis View opens, the corresponding window opens in the Configuration pane. (See Figure B-1.)
5.13.1.2 Navigating with Chassis View
The Chassis View main window contains the following components:
•Menu bar—See Table 5-24.
•Toolbar—See Table 5-25.
•Hierarchy, Configuration, and Inspector panes—See Table 5-26.
Table 5-24 Chassis View—Menu Bar Options
Menu Bar Options
|
Task
|
File
|
Close
|
Closes the current Chassis View main window when you are running multiple sessions of the Chassis View. If you are running only one session, that single session is closed.
|
Exit
|
Exits the Chassis View instance and the other sessions. This option works only on the window in which the option is selected. When you have started other Chassis Views, they continue to run.
Exits the Chassis View instance and the other sessions. This option will close all the Chassis View windows launched in this CTM session.
|
Edit
|
Copy
|
Copies the selected object and puts it into the Clipboard.
|
Paste
|
Pastes the object into the Clipboard and inserts it to the target area.
|
Tools
|
Chassis View
|
Launches the Chassis View for the selected object. For more information, see How Do I Manage My Network with the Chassis View?.
|
Configuration Center
|
Launches the Configuration Center for the selected object.
|
Diagnostic Center
|
Launches the Diagnostic Center for the selected object. For more information, see Chapter 9, "Managing Faults."
|
Statistics Report
|
Launches the Statistics Report for the selected object. For more information, see Chapter 10, "Managing Performance."
|
Administration
|
Allows you to perform administration-type tasks, such as:
•CTM Audit Trail—Allows you to access audit trail files for specified days.
•Telnet—(Only available when an NE is selected) Opens a command line tool to telnet to MGX switches.
•SSH—(Only available when an NE is selected) Opens a command line tool to gain secure shell access to MGX switches.
|
Help
|
Color Legend
|
Displays the CTM color legend.
|
Contents
|
Displays the contents for online help.
|
Table 5-25 Chassis View—Toolbar Buttons
Option
|
Task
|
Chassis View
|
Launches the Chassis View for the selected object.
If no object is selected, the Chassis View launches, and the right area is empty.
|
Configuration Center
|
Launches the Configuration Center for the selected object.
If no object is selected, the Configuration Center launches, and the right area is empty.
|
Diagnostics Center
|
Launches the Diagnostics Center for the selected object.
If no object is selected, the Diagnostics Center launches, and the right area is empty.
|
Statistics Report
|
Launches the Statistics Report.
|
Administration
|
Launches the CTM Audit Trail Viewer. For more information, see 8.5.3 Viewing the Audit Trail File—MGX Voice Gateway Devices, page 8-84.
|
Table 5-26 Chassis View—Hierarchy, Configuration, and Inspector Pane Descriptions
Options
|
Task
|
Hierarchy pane
|
Allows you to navigate to objects and displays the objects for selection and configuration. For more information, see Chapter 2, "Basic Concepts."
|
Inspector pane
|
Provides a list of detailed status information for the NE selected in the Hierarchy pane. For more information, see Chapter 2, "Basic Concepts."
|
Configuration pane
|
Displays the chassis view for the selected object. If no object is selected, the Configuration pane will be empty.
Within the Configuration pane, there are two tabs:
•Front View—Shows the front view configuration.
•Rear View—Shows the rear view configuration.
|
|
5.13.1.3 Accessing NEs
To view the chassis view for an NE in the Hierarchy pane:
•Drag and drop the NE from the Hierarchy pane into the Configuration pane
•Double-click the NE in the Hierarchy pane
The corresponding view opens or is highlighted in the Configuration pane.
Tip Any window within the Hierarchy pane can be "pinned" down by clicking on the pin tool, located in the bottom right corner of each window. This means that when you open other windows, the tacked down window will remain open. For more information on this feature, see Chapter 2, "Basic Concepts."
5.13.1.4 Chassis View LED Colors
The following table describes the LED colors that are used in the Chassis View.
Table 5-27 LED Colors for Chassis View
Color
|
State
|
Red
|
Critical
|
Orange
|
Major
|
Yellow
|
Minor
|
Green
|
Up, OK, and Clear
|
Purple
|
Self-test (loopback)
|
Gray
|
Down (unmanaged)
|
Blue
|
Unknown
|
Cyan
|
Not defined
|
5.13.2 How Do I Manage My Network with the Configuration Center?
By managing NEs with the Configuration Center, you can:
•Configure numerous managed device objects, such as configuration settings, interface status, and so forth in a media gateway.
•Display and modify the values for almost all of the objects.
•Perform tasks, such as element configuration and connection management.
These tasks are used to manage the NE configurations through the Configuration Center:
•Launching the Configuration Center
•Navigating with the Configuration Center
•Navigating Within Tables
5.13.2.1 Launching the Configuration Center
To launch the Configuration Center from the Domain Explorer:
•Click a node and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration pane for that node opens.
To launch the Configuration Center from the Diagnostic Center, Chassis View, or Statistics Report, do any of the following:
•Click the Configuration Center tool within the toolbar.
•Choose Tools > Configuration Center.
•Right-click an NE and choose Configuration Center from the pop-up menu. Once the Configuration Center opens, the corresponding window opens in the Configuration pane.
After the Configuration Center application is launched, the Configuration Center main window opens. For information about the main window components, see Navigating with the Configuration Center.
5.13.2.2 Navigating with the Configuration Center
The Configuration Center main window contains the following components:
•Menu bar—See Table 5-28.
•Toolbar—See Table 5-29.
•Hierarchy, Configuration, and Inspector panes—See Table 5-30.
Table 5-28 Configuration Center—Menu Bar Options
Menu Bar Options
|
Task
|
File
|
Close
|
Closes the current Configuration Center main window when you are running multiple sessions of the Configuration Center. If you are running only one session, that single session is closed.
|
Exit
|
Exits the Configuration Center instance and the other sessions. This option works only on the window in which the option is selected. When you have started other Configuration Centers, they continue to run.
Exits the Configuration Center instance and the other sessions. This option will close all the Configuration windows launched in this CTM session.
|
Edit
|
Cut
|
Removes the selection from the text field.
|
Copy
|
Copies the selected object and puts it into the Clipboard.
|
Paste
|
Pastes the object into the Clipboard and inserts it to the target area.
|
Connection Templates
|
(Only applicable from the Connections tab) Displays connection templates.
|
Show Unused Descriptors
|
(Only applicable from the Connections tab) Shows unused descriptors.
|
Tools
|
Chassis View
|
Launches the Chassis View for the selected object. For more information, see How Do I Manage My Network with the Chassis View?.
|
Configuration Center
|
Launches the Configuration Center for the selected object.
Note See 6.11 MGX Voice Gateway Cards, page 6-26 for additional information on how to configure your MGX Voice Gateway cards using the Configuration Center.
|
Diagnostic Center
|
Launches the Diagnostic Center for the selected object. For more information, see Chapter 9, "Managing Faults."
|
Statistics Report
|
Launches the Statistics Report for the selected object. For more information, see Chapter 10, "Managing Performance."
|
Administration
|
Allows you to perform administration-type tasks, such as:
•CTM Audit Trail—Allows you to access audit trail files for specified days.
•Telnet—(Only available when an NE is selected) Opens a command line tool to telnet to MGX switches.
•SSH—(Only available when an NE is selected) Opens a command line tool to gain secure shell access to MGX switches.
|
Help
|
Color Legend
|
Displays the CTM color legend.
|
Contents
|
Displays the contents for online help.
|
Table 5-29 Configuration Center—Toolbar Buttons
Option
|
Task
|
Chassis View
|
Launches the Chassis View for the selected object.
If no object is selected, the Chassis View launches, and the right area is empty.
|
Configuration Center
|
Launches the Configuration Center for the selected object.
If no object is selected, the Configuration Center launches, and the right area is empty.
|
Diagnostics Center
|
Launches the Diagnostics Center for the selected object.
If no object is selected, the Diagnostics Center launches, and the right area is empty.
|
Statistics Report
|
Launches the Statistics Report.
|
Administration
|
Launches the CTM Audit Trail Viewer. For more information, see 8.5.3 Viewing the Audit Trail File—MGX Voice Gateway Devices, page 8-84.
|
Table 5-30 Configuration Center—Hierarchy, Configuration, and Inspector Pane Descriptions
Options
|
Task
|
Hierarchy pane
|
Navigates and selects objects for configuration. For more information, see Chapter 2, "Basic Concepts."
Within the Hierarchy pane, there are two tabs:
•Elements—Configures the node, card, line, and port.
•Connections—Configures the connections.
|
|
Configuration pane
|
Depending on the active tab (Elements or Connections), the configuration details for the selected object appear. If an object is not selected, the Configuration pane is empty.
Fields within the Configuration pane with an asterisk (*) indicate required fields. Fields that have been modified appear blue.
|
Inspector pane
|
Provides a list of detailed status information for the NE selected from the Hierarchy pane. For more information, see Chapter 2, "Basic Concepts."
|
5.13.2.3 Navigating Within Tables
Many tabs within the Configuration pane contain tables. Each table contains the following buttons:
Note Some of these buttons might be grayed out, depending on availability.
•Create—Allows you to create a new table entry
•Details—Allows you to view or modify detailed information about a selected entry
•Delete—Allows you to delete an entry
•Refresh—Refreshes the table
If you select the Create or Details button, a new window opens. This window contains the following buttons:
Note Some of these buttons might be grayed out, depending on availability.
•Apply—Applies any modifications or additions
•Save As—Allows you to save the current parameters as a named template
•Load From—Provides a list of templates to load parameters from
•Delete—Deletes the information
•Refresh—Refreshes the data
5.13.3 How Do I Manage Templates for NEs?
•Saving Templates for NEs
•Loading or Deleting Templates for NEs
5.13.3.1 Saving Templates for NEs
For any specified NE (such as a node, card, line, port, or connection), you can save the current parameters as a template.
Note For details on creating connection templates, see Chapter 7, "Provisioning Services and Connections."
Step 1 From the Configuration Center main window, under the Elements tab, double-click the node, card, line, port, or connection whose parameters you want to save; then, click Save As to display the Save Template window.
Step 2 Enter the new name for the template in the Save As field.
Step 3 Enter a description for the template in the Description field.
Step 4 Ensure that the listed categories are correct in the Selected Categories area.
Step 5 Click Save to save the current NE template, or Cancel to exit without saving.
5.13.3.2 Loading or Deleting Templates for NEs
Step 1 From the Configuration Center main window, under the Elements tab, double-click the node, card, line, port, or connection for which you want to load or delete a template.
Step 2 Under the appropriate subtab, click Load From to display a list of available templates.
Step 3 Select the template name from the list of templates.
Step 4 Do any of the following:
•Click Load to load the template for a particular category group
•Click Delete to delete an existing template
•Click Cancel to exit without saving
•Click Refresh to refresh the window
5.13.4 How Do I Configure MGX Voice Gateway Devices?
•Configuring a Node
•Enabling or Disabling SSHv1, FTP, and Telnet Access to the Node
•Configuring the SNMP Version in CTM
•Displaying Cards Within a Node
•Verifying a Specific Card for the Node
•Managing Node Peripherals
•Viewing Node Controllers
•Managing Node Clocking
•Configuring Daylight Saving Time
5.13.4.1 Configuring a Node
Select an MGX node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens. The Node tab opens by default. The following table provides descriptions.
Step 1 Check or configure each field, as applicable.
Note Some fields are grayed out, meaning they are not configurable.
Step 2 Click Apply to apply the current node configuration settings.
Note For a description of all buttons within this tab, see Navigating Within Tables.
Table 5-31 Field Descriptions for the Node Tab
Field
|
Description
|
NE Provided Description
|
System description of the managed node as provided by the MGX.
|
Up Time
|
System up time of the current node.
|
Contact
|
Contact person for the managed node.
|
Location Stored in NE
|
Physical location of the node as configured and stored in the MGX.
|
Node Name
|
Administratively assigned name for the node.
|
Integrated Alarm Status
|
Display only. Integrated alarm status of the shelf. The following options are valid:
•Clear
•Minor
•Major
•Critical
|
Filtered Alarm Status
|
Display only. Filtered alarm status of the shelf. The following options are valid:
•Clear
•Minor
•Major
•Critical
|
Date and Time
|
Current local date and time for the system.
|
Clock Lost on Reboot (if applicable)
|
Indicates whether the system can preserve knowledge of current date and time across a system reboot.
|
System Country
|
Country where the system is physically located.
|
SSHv1 Access
|
Choose to enable or disable SSHv1 access to the switch. When this field is set to Enable, SSHV1 access to the switch is allowed. When this field is set to Disable, SSHv1 and Telnet access to the switch are disabled. When access is enabled again, only SSHV1 is enabled; Telnet must be enabled separately.
Note This field is visible only for MGX NE versions 5.5 and later.
|
FTP Access
|
Choose to enable or disable FTP access to the switch. When this field is set to Enable, FTP access to the switch is allowed. When this field is set to Disable, FTP and Telnet access to the switch are disabled. When access is enabled again, only FTP is enabled; Telnet must be enabled separately.
Note This field is visible only for MGX NE versions 5.5 and later.
|
Telnet Access
|
Choose to enable or disable Telnet access to the switch.
Note This field is visible only for MGX NE versions 5.5 and later.
|
Descriptor
|
Node descriptor.
|
5.13.4.2 Enabling or Disabling SSHv1, FTP, and Telnet Access to the Node
Select an MGX node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens. The Node tab opens by default.
Step 1 Configure the SSHv1 Access, FTP Access, and Telnet Access fields, as applicable. Table 5-31 provides descriptions.
Note Some fields are grayed out, meaning they are not configurable.
Step 2 Click Apply to apply the current SSHv1, FTP, and Telnet access node configuration settings.
Note For a description of all buttons within this tab, see Navigating Within Tables.
5.13.4.3 Configuring the SNMP Version in CTM
You can include the SNMP version when you add MGX NEs.
To add the MGX NE in SNMPv1 or SNMPv3 mode, follow these steps:
Note Use the cnfsnmpmode command to change the MGX SNMP mode to SNMPv3.
Step 1 Choose File > Add Network Element to add the NE.
Step 2 Specify the node IP address and click Next.
Step 3 Specify the SNMP version and click Finish.
Perform the following steps to change the MGX NE version from SNMPv1 to SNMPv3 or from SNMPv3 to SNMPv1:
Note The node moves to an unmanaged state in CTM if you change the SNMP version on the node from SNMPv1 to SNMPv3 or from SNMPv3 to SNMPv1 when CTM is managing the node in SNMPv1 or SNMPv3. In addition, CTM tries to manage the node using SNMPv1 only.
If you need to change the SNMP mode, you must first change the mode on the node, and then on the CTM server.
Step 1 Select the NE in the Domain Explorer.
Step 2 Click the Network Element Properties pane > NE Authentication tab.
Step 3 In the CTM Server - NE Connection area, click the SNMPv1 or SNMPv3 radio button to specify the SNMP version.
Step 4 Click Save.
5.13.4.4 Displaying Cards Within a Node
Displaying cards within a node allows you to verify that the correct cards are installed in the correct slots, and that the back cards installed are indeed compatible with the front cards they serve.
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens.
Step 2 Click the Cards tab to display a summary report of all the cards installed on the node. The Cards category opens by default in the drop-down list.
Note For detailed information on the Redundancy Info option, see Chapter 4, "Maintaining an Efficient Network."
5.13.4.5 Verifying a Specific Card for the Node
You can verify a card when the objects to be managed are associated with a particular card.
Step 1 Under the Cards tab (see Configuring the SNMP Version in CTM) select the card from the summary report; then, click Details.
Alternately, within the Configuration Center Hierarchy pane, double-click the card you want to view details for.
The Card tab opens. Table 5-32 provides descriptions.
Step 2 Choose one of the following card configurations from the Category drop-down list:
•Front Card Configuration
•Back Card Configuration
•Sec Back Card Configuration (optional)
•System Information (RPM only)
•Entity Sensors (VXSM only)
•Card Information (VISM-PR only)
•Daughter Card Information (VISM-PR only)
Note The Back Card Configuration or Sec Back Card Configuration options are display only.
Step 3 (Optional) Under the Front Card Configuration option, enter the card descriptor in the Descriptor field.
Note The Descriptor field is valid for the whole Card Configuration, but is available only from the first category of that card configuration, in this case the Front Card Configuration.
Step 4 (Optional) Under the System Information option, enter the Node Name.
Step 5 Click Apply to modify the card descriptor and to verify that the information for the card is valid.
Note For a description of all buttons within this tab, see Navigating Within Tables.
Table 5-32 Field Descriptions for the Cards Tab
Field
|
Description
|
Front, Back, and Sec Back Card Configuration (applicable fields vary for each)
|
(Operational) Status
|
Operational state of the module.
|
Card Description
|
Front card description.
|
Admin Status
|
Administrative control of the module.
|
Type
|
Textual description of physical entity.
|
Slot Number
|
Number of the physical entity.
|
Hardware (HW) Revision
|
Vendor-specific hardware description string.
|
Firmware (FW) Revision
|
Vendor-specific firmware description string.
|
SW Revision
|
Vendor-specific software description string.
|
Serial Number
|
Vendor-specific serial number string.
|
Orderable Part No
|
Name of the manufacturer.
|
Reset Reason
|
Reason for last reset.
|
Card Uptime
|
Displays the uptime of the current card. The following cards support this feature: AXSMXG, MPSM-T3E3-155, MPSM-16-T1E1, PXM1E, PXM45, RPM, VXSM, and VISM.
|
Descriptor
|
Card descriptor.
|
Secondary Description (RPM only)
|
Secondary back card description.
|
Secondary Serial Number (RPM only)
|
Secondary back card serial number.
|
Secondary Hardware Revision (RPM only)
|
Secondary back card hardware revision.
|
Secondary Firmware Revision (RPM only)
|
Secondary back card firmware revision.
|
Secondary Operational Status (RPM only)
|
Secondary back card operational status.
|
Save Running Config button (RPM only)
|
Allows you to save any configuration changes on the router, in order to keep those changes after a reboot.
|
System Information (RPM only)
|
Sys Description
|
Textual description of the system entity.
|
Up Time
|
Time (in hundredths of a second) since the network management portion of the system was last reinitialized.
|
Contact
|
ID and contact information of the contact person for this managed node.
|
Node Name
|
Administratively assigned name for the managed node.
|
Location
|
Physical location of the node.
|
Services
|
Indicates a set of services that the system offers.
|
Entity Sensors, Entity Sensors Tab
|
Sensor Description
|
Textual description of the sensor.
|
Sensor Type
|
Type of data reported by the entSensorValue. This variable is set by the agent at startup and the value does not change during operation.
|
Sensor Scale
|
Indicates the exponent to apply to sensor values reported by entSensorValue. This variable is set by the agent at startup and the value does not change during operation.
|
Sensor Value
|
Reports the most recent measurement detected by the sensor.
|
Sensor State
|
Indicates the present operational state of the sensor.
|
Entity Sensors, Sensor Threshold Tab
|
Threshold Index
|
Index that uniquely identifies an entry in the entSensorThreshold table. This index permits the same sensor to have several different thresholds.
|
Threshold Severity
|
Severity of this threshold.
|
Threshold Relation
|
Relation between sense or value and threshold value, required to trigger the alarm.
|
Threshold Value
|
Value of the threshold.
|
Threshold Evaluation
|
Result of the most recent evaluation of the threshold.
|
Threshold Notification
|
Controls generation of entSensorThresholdNotification for this threshold.
|
Card Information (VISM-PR only)
|
Slot Number
|
Slot number of the card.
|
Card Type
|
This object holds the type of the card, for processor module as well as service module.
|
Card Change Type
|
Type of card change.
|
Daughter Card Information (VISM-PR only)
|
Daughter Card Serial Number
|
The serial number is on the nonvolatile RAM on the P daughter card, entered by the manufacturer.
|
Daughter Card Description
|
Describes the VISM-PR daughter card.
|
Daughter Card Hardware (HW) Revision
|
Hardware revision number for the daughter card.
|
5.13.4.6 Managing Node Peripherals
These tasks are used to manage peripherals:
•Displaying IP Interfaces
•Configuring Serial Interfaces
•Displaying Sensors
5.13.4.6.1 Displaying IP Interfaces
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens.
Step 2 Click the Peripherals tab. The IP Interfaces option opens by default in the Category drop-down list.
Step 3 (Optional) Click Refresh to refresh the table.
Note For a description of all buttons within this tab, see Navigating Within Tables.
5.13.4.6.2 Configuring Serial Interfaces
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens.
Step 2 Click the Peripherals tab.
Step 3 Choose the Serial Interfaces option from the Category drop-down list.
Step 4 (Optional) Click Details to view or modify information about a selected controller. The Serial Interface tab opens. The following table provides descriptions.
a. Enter the speed, and configure the stop bits and parity, if applicable.
b. Click Apply.
Note For a description of all buttons within this tab, see Navigating Within Tables.
Table 5-33 Field Descriptions for the Serial Interfaces Tab
Field
|
Description
|
Port Index
|
Interface index of the port.
|
Speed (Bits Per Second)
|
The input speed of the port.
|
Stop bits
|
The number of stop bits on the port:
•NA
•one
•two
•oneAndHalf
•dynamic
|
Parity
|
The port's sense of a character parity bit:
•NA
•none
•odd
•even
•mark
•space
|
5.13.4.6.3 Displaying Sensors
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens.
Step 2 Click the Peripherals tab.
Step 3 Choose the Sensors option from the Category drop-down list to open the Sensors table. The following table provides descriptions.
Step 4 (Optional) Click Refresh to refresh the table.
Table 5-34 Field Descriptions for the Sensors Table
Field
|
Description
|
Description
|
Specifies the type of environmental state, such as temperature, DC voltage, bottom fan tray, and so forth.
|
Value
|
Reports the most recent measurement seen by the sensor.
|
Type
|
Indicates the type of data reported by the Value parameter. The variable is set by the agent at startup and the value does not change during operation.
|
Value Last Updated
|
Indicates the status of the value.
|
Value Time Stamp
|
Indicates the date and time of the value reported in the Value parameter.
|
Update Rate
|
Indicates the rate at which the agent updates the Value parameter.
|
5.13.4.7 Viewing Node Controllers
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens.
Step 2 Click the Controllers tab. The following table provides descriptions.
Step 3 (Optional) Click any one of the following buttons:
•Create to create a new controller
•Details to view or modify information about a selected controller
•Delete to delete a controller
•Refresh to refresh the table
Table 5-35 Field Descriptions for the Controllers Table
Field
|
Description
|
Controller ID
|
Unique value for VSI controller (VSI master).
|
Controller Type
|
Identifies the controller type.
|
Controller Name
|
Name chosen by the user for the VSI controller.
|
Controller Shelf Location
|
Identifies the location of the controller shelf.
|
Controller Location
|
Identifies the location of the controller.
|
5.13.4.8 Managing Node Clocking
On Cisco MGX 8850 (PXM1E) switches, clock source configuration is done on the PXM1E card and passed to other nodes over PXM1E lines.
On Cisco MGX 8850 (PXM45) switches, clock source configuration is done on a PXM45 card, and clock sourcing information is passed to other nodes over ATM Switch Service Module (AXSM) lines.
CTM supports the manual clock configuration method of network clock synchronization for the Cisco MGX switches. Manual clock configuration configures both primary and secondary clock sources, which are distributed throughout the network. The secondary clock source takes over if the primary clock source fails. You can configure a network setup with one master clock source, and a secondary to ensure network clock stability.
You can manage three types of node clocking:
•Configuring Global Clocking
•Viewing Available Clock Sources
•Viewing or Creating Manual Clock Sources
5.13.4.8.1 Configuring Global Clocking
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens.
Step 2 Click the Clocking tab. The Global Clocking Configuration option opens by default in the Category drop-down list. Table 5-36 provides descriptions.
Step 3 (Optional) Modify the fields as necessary.
Step 4 (Optional) Click any one of the following buttons:
•Apply—Applies any modifications or additions
•Save As—Allows you to save the current parameters as a named template
•Load From—Provides a list of templates to load parameters from
•Refresh—Refreshes the data
5.13.4.8.2 Viewing Available Clock Sources
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens.
Step 2 Click the Clocking tab.
Step 3 Choose the Available Clock Sources option from the Category drop-down list. Table 5-36 provides descriptions.
Step 4 (Optional) Click Refresh to reload the table data.
Note For a description of all buttons within this tab, see Navigating Within Tables.
5.13.4.8.3 Viewing or Creating Manual Clock Sources
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens.
Step 2 Click the Clocking tab.
Step 3 Choose the Manual Clock Sources option from the Category drop-down list. Table 5-36 provides descriptions.
Step 4 To create a new clock source, proceed as follows:
a. Click Create. Complete the following fields:
•Priority
•Clock Source Index
b. Click Apply.
Note For a description of all buttons within this tab, see Navigating Within Tables.
Table 5-36 Field Descriptions for the Clocking Tab
Field
|
Description
|
Global Clocking Configuration
|
Distribution Method
|
Method used to distribute the network clock for the device.
|
Stratum
|
Contains the stratum level of the node.
|
Max Diameter
|
The maximum possible height of a network clock distribution tree in the network.
|
Change Reason
|
Reason for the most recent change made to a network clock source, as indicated by the change in the value of "ciscoWanChangeTimeStamp."
|
Change Time
|
Value of sysUpTime when the most recent change of a network clock source occurred.
|
Clock Source
|
Description of the clock source associated with this entry.
|
Available Clock Sources
|
Clock Index
|
Clock index number.
|
Clock Source
|
Description of the clock source associated with this entry.
|
Type
|
Type of clock.
|
Manual Clock Sources Table
|
Clock Source
|
Description of the clock source associated with this entry.
|
Manual Clock Index
|
Manual clock index number.
|
Manual Source Priority
|
Manual source priority.
|
Health
|
Health of the clock source.
|
Manual Clock Sources Create Window
|
Priority
|
Value used to configure an available network clock source to be the primary, secondary, or default manual clock source.
|
Clock Source Index
|
An index value used to identify the primary, secondary, or default manual clock source.
|
Clock Source
|
Description of the clock source associated with this entry.
|
Health
|
Health of the clock source.
|
5.13.4.9 Configuring Daylight Saving Time
CTM supports the ability to enable and configure Daylight Saving Time for the Cisco MGX switches.
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens.
Step 2 Click the Daylight Savings tab.
Step 3 Choose the appropriate values from the drop-down lists. Table 5-37 provides descriptions.
Step 4 Click Apply.
Note For a description of all buttons within this tab, see Navigating Within Tables.
Table 5-37 Field Descriptions for the Daylight Savings Tab
Field
|
Description
|
Summer Time Status
|
Enable (true) or disable (false) the daylight saving time feature in the switch.
|
Standard Time Zone GMT Offset
|
Set the standard time zone offset from GMT in multiples of 60 minutes.
|
Summer Time Zone GMT Offset
|
Set the summer time zone offset from GMT in multiples of 60 minutes.
|
Recurring Start Week
|
Select the week in which summer time starts. Values are First Week, Second Week, Third Week, Fourth Week, Fifth Week, and Last Week.
|
Recurring Start Day
|
Select the day on which summer time starts.
|
Recurring Start Month
|
Select the month in which summer time starts.
|
Recurring Start Time
|
Select the time at which summer time starts. Enter the time using the format XX:YY, where XX stands for hours and YY stands for minutes.
|
Recurring End Week
|
Select the week in which summer time ends. Values are First Week, Second Week, Third Week, Fourth Week, Fifth Week, and Last Week.
|
Recurring End Day
|
Select the day on which summer time ends.
|
Recurring End Month
|
Select the month in which summer time ends.
|
Recurring End Time
|
Select the time at which summer time ends. Enter the time using the format XX:YY, where XX stands for hours and YY stands for minutes.
|
5.13.5 How Do I Create or Modify APS?
Automatic Protection Switching (APS) can be configured on SONET lines within SRME, AXSM, and VXSM OC-type cards.
If you are setting up APS on multiple cards, you must first set up an APS connector and then set up redundancy on the node (for details on setting up redundancy, see 4.5.11 Configuring Card Redundancy—MGX Voice Gateway Devices, page 4-92).
Step 1 Select a node in the Domain Explorer tree and choose Configuration > MGX Voice Gateway > Configuration Center. The Configuration window for the selected node opens.
Step 2 Double-click an AXSM, SRME, or VXSM card.
Step 3 Click the Sonet Line APS tab. Under the Sonet Line APS tab, you can:
•Click Create to create a new Sonet Line APS
•Select the line you want to modify and click Details
Step 4 Configure the fields. The following table provides descriptions.
Step 5 Click Apply to save any changes.
Table 5-38 Field Descriptions for the Sonet Line APS Tab
Field
|
Description
|
Working Bay
|
Working bay number.
|
Working Line
|
Working line number.
|
Protection Slot
|
Protection slot number.
|
Protection Bay
|
Protection bay number.
|
Protection Line
|
Protection line number.
|
APS Mode
|
Configures APS architecture mode on the working/protection line pairs.
|
Active Line
|
Indicates which line is active.
|
Signal Fault BER
|
Contains the bit error rate threshold for signal fault detection on the working line.
|
Signal Degrade BER
|
Contains the bit error rate threshold for signal degrade detection on the working line.
|
Switch Back Time
|
Contains the interval (in minutes) to wait before attempting to switch back to the working line.
|
Switching Direction
|
Configures the switching direction supported by this APS line.
|
APS Revertive
|
Configures the APS revertive or nonrevertive option.
|
APS Operational Direction
|
Shows the actual APS direction that is implemented on the near-end terminal.
|
APS Operational Mode
|
Shows the actual APS architecture mode that is implemented on the near-end terminal.
|
Channel Protocol
|
Allows configuration of APS channel protocol to be implemented at the near-end terminal.
|
Line Failure Status
|
APS line failure status.
|
Line Switch Reason
|
APS line switch reason.
|
Working Section
|
Indicates which working section is the APS primary section.
|
