This chapter explains how to set up a Cisco ONS 15454 SDH node using Cisco Transport Controller (CTC). Table 3-1 lists node setup topics. Table 3-2 lists node setup procedures. The chapter also includes a list of required information for node setup. Refer to "Set Up PC and Log Into CTC" for CTC setup procedures.
If the ONS 15454 SDH will be connected to a network, you will need:
The IP address and subnet mask to assign to the node
The IP address of the default router
The IP address of the Dynamic Host Configuration Protocol (DHCP) server (if DHCP is used)
If you are responsible for setting up IP networking for the ONS 15454 SDH network, see "IP Networking," for more information.
To create card protection groups, you will need to know:
The card protection scheme that will be used and what cards will be included in it
The SDH protection topology that will be used for the node
Note You must be able to log into the node to complete node provisioning. If you cannot log into the node,
see the "Setting Up the CTC Computer"
section.
3.2 Setting Up Basic Node Information
Setting basic information for each Cisco ONS 15454 SDH node is one of the first provisioning tasks you perform. This information includes node name, location, contact, latitude, longitude, dates, and time.
Procedure: Add the Node Name, Contact, Location, Date, and Time
Purpose
Use this procedure to set node name, location, contact, latitude, longitude, dates, and time.
Step 1 Start CTC for an ONS 15454 SDH node. The CTC node view is displayed.
Step 2 Click the Provisioning > General tabs (Figure 3-1).
Figure 3-1 Setting up general node information
Step 3 Enter the following:
Node Name—Type a name for the node. For TL1 compliance, names must begin with an alphabetical character and have no more than 20 alphanumeric characters. (TL1 is not available in SDH Software R3.4 and earlier.)
Contact—Type the name of the node contact person and the phone number (optional).
Location—Type the node location, for example, a city name or specific office location (optional).
Latitude—Enter the node latitude: N (North) or S (South), degrees, and minutes (optional).
Longitude—Enter the node longitude: E (East) or W (West), degrees, and minutes (optional).
CTC uses the latitude and longitude to position node icons on the network view map.
Note You can also position nodes manually by pressing Ctrl and dragging the node icon to a
new location.
To convert a coordinate in degrees to degrees and minutes, multiply the number after the decimal by 60. For example, the latitude 38.250739 converts to 38 degrees, 15 minutes (.250739 x 60 = 15.0443, rounded to the nearest whole number).
Use SNTP/NTP Server—When checked, CTC uses a Simple Network Time Protocol (SNTP) server or a Network Time Protocol (NTP) server to set the date and time of the node. Using an SNTP/NTP server ensures that all ONS 15454 SDH network nodes use the same date and time reference. The server synchronizes the time of the nodes after power outages or software upgrades.
If you check Use SNTP/NTP Server, type the server's IP address in the next field. If you do not use an SNTP/NTP server, complete the Date, Time, and Time Zone fields. The ONS 15454 SDH will use these fields for alarm dates and times. (CTC displays all alarms in the login node's time zone for cross-network consistency.)
Date—Type the current date if you did not select Use SNTP/NTP Server.
Time—Type the current time if you did not select Use SNTP/NTP Server.
Time Zone—Select the time zone if you did not select Use SNTP/NTP Server.
Step 4 Click Apply.
Procedure: Set a Port Name for a Card
Purpose
Use this procedure to assign a name to one port on a card.
Prerequisite Procedures
Verify card installation
Onsite/Remote
Onsite or remote
Step 1 Log into the node where you want to set a port name for a card or cards. The node (default) view displays. See the "Log Into CTC" procedure for instructions.
Step 2 Double-click the card that has the port you want to provision.
Step 3 Click the Provisioning tab.
Step 4 Click the Name column for the port number you are naming and enter the desired port name.
The port name can be up to 32 alphanumeric/special characters and is blank by default.
Step 5 Click Apply.
3.3 Setting Up Network Information
Before you connect a node to other nodes or to a LAN, you must change the default IP address that is shipped with each ONS 15454 SDH (192.168.1.1). IP addresses are unique identifiers for devices—called hosts—that connect to TCP/IP networks. Every IP address includes a network number, which is assigned to an organization, and a host (device) number, which the organization's LAN administrator assigns to an individual network device.
Subnetting enables LAN administrators to create subnetworks that are transparent to the Internet. Within networks, ONS 15454 SDH nodes often exist as subnetworks, which are created by adding a subnet mask to the ONS 15454 SDH IP address.
Procedure: Set Up Network Information
Purpose
Use this procedure to start provisioning a network. Additional ONS 15454 SDH networking information and procedures, including IP addressing examples, static route scenarios, and Open Shortest Path First (OSPF) protocol options, are provided in "IP Networking."
Prerequisite Information
The IP address and subnet mask to assign to the node
The IP address of the default router
The IP address of the DHCP server (if DHCP is used)
Onsite/Remote
Onsite or remote
Step 1 Log into CTC or navigate to the node view. Click the Provisioning > Network > General tabs (Figure 3-2).
Figure 3-2 Setting up general network information
Step 2 Complete the following:
IP Address—Type the IP address assigned to the ONS 15454 SDH node.
Default Router—Check this field if the ONS 15454 SDH must communicate with a device on a network that the ONS 15454 SDH is not connected to. The ONS 15454 SDH forwards the packets to the default router. Type the IP address of the router in this field. If the ONS 15454 SDH is not connected to a LAN, leave the field blank.
Subnet Mask Length—If the ONS 15454 SDH is part of a subnet, type the subnet mask length (a decimal number representing the subnet mask length in bits) or click the arrows to adjust the subnet mask length. The subnet mask length is the same for all ONS 15454 SDH nodes in the same subnet.
Note The MAC Address field is read only. It displays the ONS 15454
SDH address used by the IEEE 802 Media Access Control (MAC) layer.
Forward DHCP Requests To—When checked, this field forwards Dynamic Host Configuration Protocol requests to the IP address entered in the Request To field. DHCP is a TCP/IP protocol that enables CTC computers to get temporary IP addresses from a server. If you enable DHCP, CTC computers that are directly connected to an ONS 15454 SDH node can find temporary IP addresses from the DHCP server.
Craft Access Only—When this choice is enabled, the ONS 15454 SDH neither installs nor advertises default or static routes. CTC computers can communicate with the ONS 15454 SDH, but they cannot communicate directly with any other DCC-connected ONS 15454 SDH.
In a configuration where all nodes are on the same subnet, if you start a CTC session before proper provisioning, the login node appears grey in the CTC network view. Other CTC users are not be able to open the grey-colored node to access their node. Provision a static route on the node that is LAN-connected, or, if you are directly connected to the node, provision craft access. For procedures, see the "Scenario 5: Using Static Routes to Connect to LANs" section or the "Scenario 9: Using the Proxy Server Features" section.
Enable Proxy—When this choice is enabled, the ONS 15454 SDH responds to CTC client requests with a list of DCC-connected ONS 15454 SDH nodes for which the node serves as a proxy. The CTC client establishes connections through the proxy server for any ONS 15454 SDH in the returned list. By using the proxy, the CTC client can connect to nodes that the PC on which the CTC client runs cannot access. If Enable Proxy is off, the node responds to CTC requests with an empty list, indicating that it is not willing to serve as a proxy.
Enable Firewall—If this choice is selected, the node prevents IP traffic from being routed between the DCC and the LAN port. The ONS 15454 SDH can communicate with machines connected to the LAN port or connected through the DCC. However, the DCC-connected machines cannot communicate with the LAN-connected machines, and the LAN-connected machines cannot communicate with the DCC-connected machines. A CTC node using the LAN to reach the firewalling node can use the proxy capability to manage the unreachable, DCC-connected nodes. CTC connected to a DCC-connected node can only manage other DCC-connected nodes and the firewall itself.
Step 3 Click Apply.
Step 4 Click Yes in the confirmation dialog box.
Changing the network configuration causes both ONS 15454 SDH TCC-I cards to reboot, one at a time.
Note CTC software does not monitor for the presence or absence of FMECs unless the TCC-I card(s) is
active/standby. During transitional states such as power-up or TCC-I reset, CTC ignores the FMEC
inventory displayed in node view.
Procedure: Change IP Address, Default Router, and Network Mask Using the LCD
Purpose
You can change the ONS 15454 SDH IP address, subnet mask, and default router address using the Slot, Status, and Port buttons on the front panel LCD.
Prerequisite Procedures
The IP address and subnet mask to assign to the node
The IP address of the default router
The IP address of the DHCP server (if DHCP is used)
Onsite/Remote
Onsite or remote
Step 1 On the ONS 15454 SDH front panel, repeatedly press the Slot button until Node appears on the LCD.
Note The LCD reverts to normal display mode after 5 seconds of button inactivity.
Step 2 Repeatedly press the Port button until the following displays:
To change the node IP address, "Status=IpAddress" (Figure 3-3)
To change the node network mask, "Status=Net Mask"
To change the default router IP address, "Status=Default Rtr"
Figure 3-3 Selecting the IP address option
Step 3 Press the Status button to display the node IP address (Figure 3-4), the node subnet mask length, or the default router IP address.
Figure 3-4 Changing the IP address
Step 4 Push the Slot button to move to the IP address or subnet mask digit you need to change. The selected digit flashes.
Step 5 Press the Port button to cycle the IP address or subnet mask digit to the correct digit.
Step 6 When the change is complete, press the Status button to return to the Node menu.
Step 7 Repeatedly press the Port button until the Save Configuration option appears (Figure 3-5).
Figure 3-5 Selecting the save configuration option
Step 8 Press the Status button to select the Save Configuration option.
Step 9 Press the Slot button to save the new IP address configuration. (Or press Port to cancel the configuration.)
Saving the new configuration causes the TCC-I cards to reboot. During the reboot, a "Saving Changes - TCC Reset" message displays on the LCD. The LCD returns to the normal alternating display after the TCC-I reboot is complete.
Note CTC software does not monitor for the presence or absence of FMECs unless the TCC-I card(s) is
active/standby. During transitional states such as power-up or TCC-I reset, CTC ignores the FMEC
inventory displayed in node view.
3.4 Creating Users and Setting Security
Use the CISCO15 user, provided with each ONS 15454 SDH, to set up other ONS 15454 SDH users. You can add up to 500 users to one ONS 15454 SDH. Each ONS 15454 SDH user can be assigned one of the following security levels:
Retrieve users can retrieve and view CTC information but cannot set or modify parameters.
Maintenance users can access only the ONS 15454 SDH maintenance options.
Provisioning users can access provisioning and maintenance options.
Superusers can perform all of the functions of the other security levels as well as set names, passwords, and security levels for other users.
Note The CISCO15 superuser can be deleted if you have at least one other superuser defined. When
CISCO15 is deleted, all new users must use passwords unless the database is deleted.
Each ONS 15454 SDH user has a specified amount of time that he or she can leave the system idle before the CTC window is locked. The lockouts prevent unauthorized users from making changes. Higher-level users have shorter idle times, as shown in Table 3-3.
Table 3-3 ONS 15454 SDH User Idle Times
Security Level
Idle Time
Superuser
15 minutes
Provisioning
30 minutes
Maintenance
60 minutes
Retrieve
Unlimited
Table 3-4 shows the actions that each user can perform in node view. In the following tables, Yes means the user can use the specified tab or screen. Table cells with dashes (—) mean the user cannot use the specified tab.
Table 3-4 ONS 15454 SDH Security Levels—Node View
CTC Tab
Subtab
Actions
Retrieve
Maint.
Provision.
Super-user
Alarms
—
Synchronize alarms
Yes
Yes
Yes
Yes
Filter alarms
Yes
Yes
Yes
Yes
Delete cleared alarms
Yes
Yes
Yes
Yes
Conditions
—
Retrieve conditions
Yes
Yes
Yes
Yes
Filter
Yes
Yes
Yes
Yes
History
Session
Filter
Yes
Yes
Yes
Yes
Node
Retrieve and filter alarms and events
Yes
Yes
Yes
Yes
Circuits
—
Create, delete, edit, or filter circuits
No
No
Yes
Yes
Search for circuits
Yes
Yes
Yes
Yes
Provisioning
General
Edit
No
No
Yes
Yes
Ether Bridge
Spanning Trees: Edit
No
No
Yes
Yes
Thresholds: Create or delete
No
No
Yes
Yes
Network
General: Edit
No
No
No
Yes
Static Routing: Create, edit, or delete
No
No
Yes
Yes
OSPF: Edit
Edit area ID
Edit area ID
Yes
Yes
Routing Information Protocol (RIP): Edit
No
No
Yes
Yes
Protection
Create, delete, or edit
No
No
Yes
Yes
Browse groups
Yes
Yes
Yes
Yes
MS-SPRing
All (MS-SPRing), view ring map, and squelch table
No
Partial view
Partial edit
Yes
Security
Users: Create or delete
No
No
No
Yes
Users: Change password
Same user
Same user
Same user
All users
Legal disclaimer: HTML/Preview
View only
View only
View only
Yes
SNMP
Create, delete, or edit
No
No
No
Yes
Browse trap destinations
Yes
Yes
Yes
Yes
SDH DCC
Create, delete, or edit
No
No
No
Yes
View SDCC terminations
Yes
Yes
Yes
Yes
Timing
Edit
No
Partial edit
Yes
Yes
Alarm Behavior
Edit
No
No
Yes
Yes
Defaults Editor
Import or export
No
Export only
Export only
Yes
UCP
Node, neighbor, IPCC, interface, circuit
No
No
Yes
Yes
Inventory
—
Delete card
No
No
Yes
Yes
Reset card
No
Yes
Yes
Yes
View equipment information
Yes
Yes
Yes
Yes
Maintenance
Database
Backup or restore
No
No
No
Yes
Ether Bridge
Spanning tree retrieve
Yes
Yes
Yes
Yes
Spanning tree clear/clear all
No
Yes
Yes
Yes
MAC table retrieve
Yes
Yes
Yes
Yes
MAC table clear/clear all
No
Yes
Yes
Yes
Trunk utilization refresh
Yes
Yes
Yes
Yes
Protection
Switch/lockout operations
View only
View only
Yes
Yes
MS-SPRing
MS-SPRing maintenance
No
Yes
Yes
Yes
Software
Download/activate/revert
No
No
No
Yes
XC Cards
Switch/lock/unlock
No
Yes
Yes
Yes
Overhead XConnect
View port, circuit, and circuit type
No
Yes
Yes
Yes
Diagnostic
Retrieve diagnostics file
No
No
No
Yes
Lamp test
No
Yes
Yes
Yes
Timing
Edit
No
Yes
Yes
Yes
Audit
Retrieve audit trail
Yes
Yes
Yes
Yes
Routing Table
Refresh
Yes
Yes
Yes
Yes
RIP Routing Table
Refresh
Yes
Yes
Yes
Yes
Procedure: Set Up Passwords from Network View
You can perform ONS 15454 SDH user management tasks from network or node view. If you perform user management tasks in node view, you must add the same user name and password to each node the user will access. See the "Set Up Passwords from Node View" procedure for more information.
Purpose
Create new users with security settings from network view. In network view, you can add, edit, or delete users from multiple nodes at one time.
Step 1 In network view, select the Provisioning > Security tabs (Figure 3-7).
Step 2 On the Security pane, click Create.
Figure 3-7 Creating new users from the network view
Step 3 In the Create User dialog box, enter the following:
Name—Type the user name.
Password—Type the user password. The password must contain alphanumeric characters, where at least one character is numerical (0-9) and at least one special character is used (+, #,%), for example, testpass+12. The password cannot contain the associated user ID. For example, if your user ID is maintenance, the password cannot be maintenance12+.
Note For TL1 compliance, the password must be a minimum of six and a maximum of ten
alphanumeric characters, where at least one character is numerical (0-9) and at least one
special character is used (+, #,%), for example, ILM+12. (TL1 is not available in SDH
Software R3.4 and earlier.)
Confirm Password—Type the password again to confirm it.
Security Level—Select the user's security level:
Retrieve users can retrieve and view CTC information but cannot set or modify parameters.
Maintenance users can access only the ONS 15454 SDH maintenance options.
Provisioning users can access provisioning and maintenance options.
Superusers can perform all of the functions of the other security levels as well as set names, passwords, and security levels for other users.
Step 4 In the Select applicable nodes list box, deselect any nodes where you do not want to add the user. (All network nodes are selected by default.)
Step 5 Click OK.
Note New users can also be created from node view. If you add a user in node view, you can only add, edit,
or delete users from that node (Figure
3-8).
Procedure: Set Up Passwords from Node View
Note This procedure sets up one user and password for one node. You must repeat this procedure for every
node a user needs to open. If you add a user in network view, you can assign a single user to multiple
nodes by clicking a check box. See the
"Set Up Passwords from Network View"
procedure for more information.
Purpose
Use this procedure to create new users, assign passwords, and set security levels one node at a time.
Step 1 In node view, select the Provisioning > Security > User tabs (Figure 3-8).
Step 2 On the User tab, click Create.
Figure 3-8 Creating new users from the node view
Step 3 In the Create User dialog box, enter the following:
Name—Type the user name.
Password—Type the user password. The password must contain alphanumeric characters, where at least one character is numerical (0-9) and at least one special character is used (+, #,%), for example, testpass+12. The password cannot contain the associated user ID. For example, if your user ID is maintenance, the password cannot be maintenance12+.
Note For TL1 compliance, the password must be a minimum of six and a maximum of ten
alphanumeric characters, where at least one character is numerical (0-9) and at least one
special character is used (+, #,%), for example, ILM+12. (TL1 is not available in SDH
Software R3.4 and earlier.)
Confirm Password—Type the password again to confirm it.
Security Level—Select the user's security level:
Retrieve users can retrieve and view CTC information but cannot set or modify parameters.
Maintenance users can access only the ONS 15454 SDH maintenance options.
Provisioning users can access provisioning and maintenance options.
Superusers can perform all of the functions of the other security levels as well as set names, passwords, and security levels for other users.
Step 1 In network view, select the Provisioning > Security tabs.
Step 2 Click a name in the list of users.
Figure 3-9 Changing a user's security settings from the network view
Step 3 In the Selected User dialog box, edit the user information: name, password, password confirmation, and/or security level. (A superuser does not need to enter an old password. Other users must enter their old password when changing their own passwords.)
Step 4 If you do not want the user changes to apply to all network nodes, deselect the nodes that you do not want to change in the Change Users dialog box.
Step 5 Click OK.
Changed user permissions and access levels do not take effect until the user logs out of CTC and logs back in.
Note User security settings can also be changed from node view
(Figure 3-10).
Figure 3-10 Changing a user's security settings from the node view
Step 1 In network view, select the Provisioning > Security tabs (Figure 3-11).
Step 2 Click Delete.
Figure 3-11 Deleting a user from the network view
Step 3 In the Delete User dialog box, enter the name of the user you want to delete.
Step 4 If you do not want to delete the user from all network nodes, deselect the nodes.
Step 5 Click OK and click Apply.
Note User security settings can also be deleted from node view
(Figure 3-12).
Figure 3-12 Deleting a user from the node view
3.5 Setting Up ONS 15454 SDH Timing
SDH timing parameters must be set for each ONS 15454 SDH.
3.5.1 Timing Sources and Modes
Each ONS 15454 SDH independently accepts its timing reference from one of three sources:
The Timing A and Timing B connectors on the MIC-C/T/P FMEC in Slot 24.
Note CTC refers to Timing A and Timing B as BITS (building integrated timing supply) 1 and BITS 2.
An STM-N card installed in the ONS 15454 SDH. The STM-N card is connected to a node that receives timing through a BITS source.
The internal ST3 clock on the TCC-I card.
You can set ONS 15454 SDH timing to one of three modes: external, line, or mixed. If timing is coming from the MIC-C/T/P FMEC timing connector, set ONS 15454 SDH timing to external. If the timing comes from an STM-N card, set the timing to line.
Note The line timing mode is not available for 64 KHz BITS facilities.
In typical ONS 15454 SDH networks:
One node is set to external. The external node derives its timing from a MIC-C/T/P FMEC timing connector. The MIC-C/T/P FMEC, in turn, derives its timing from a Primary Reference Source (PRS) such as a Stratum 1 clock or global positioning satellite (GPS) signal.
The other nodes are set to line. The line nodes derive timing from the externally timed node through the STM-N trunk cards.
You can set three timing references for each ONS 15454 SDH. The first two references are typically two FMEC-level sources, or two line-level sources optically connected to a node with a BITS source. The third reference is the internal clock provided on every ONS 15454 SDH TCC-I card. This clock is a Stratum 3 (ST3). If an ONS 15454 SDH becomes isolated, timing is maintained at the ST3 level.
Caution Mixed timing allows you to select both external and line timing sources. Cisco does not recommend its use because it can create timing loops. Use this mode with caution.
3.5.2 Network Timing Example
Figure 3-13 shows an ONS 15454 SDH network timing setup example. Node 1 is set to external timing. Two timing references are set to BITS. These are Stratum 1 timing sources connected to the MIC-C/T/P FMEC. The third reference is set to internal clock. The Timing A and Timing B out connectors on the MIC-C/T/P FMEC of Node 3 are used to provide timing to outside equipment.
In the example, Slots 5 and 6 contain the trunk cards. Timing at Nodes 2, 3, and 4 is set to line, and the timing references are set to the trunk cards based on distance from the MIC-C/T/P FMEC. Reference 1 is set to the trunk card closest to the timing source. At Node 2, Reference 1 is Slot 5 because it is connected to Node 1. At Node 4, Reference 1 is set to Slot 6 because it is connected to Node 1. At Node 3, Reference 1 could be either trunk card because they are equal distance from Node 1.
Figure 3-13 NS 15454 SDH timing example
3.5.3 Synchronization Status Message
Synchronization Status Message (SSM) communicates information about the quality of the timing source. The SSM supported in SDH is G.811, STU, G812T, G812L, SETS, DUS (ordered from high quality to low quality). SSM messages are carried on bits 5 to 8 of SDH overhead byte S1. They enable SDH devices to automatically select the highest quality timing reference and to avoid timing loops.
Note The message set in the San1 to San4 column is a copy of the set defined in SDH bits 5 to 8 of byte S1.
Table 3-5 Assignment of Bit Patterns as Shown in ITU G.704
Step 1 From the CTC node view, click the Provisioning > Timing tabs (Figure 3-14).
Figure 3-14 Setting Up external, line, or mixed ONS 15454 SDH timing
Step 2 In the General Timing section, complete the following information:
Timing Mode—Choose External if the ONS 15454 SDH derives its timing from a MIC-C/T/P FMEC; choose Line if timing is derived from an STM-N card that is optically connected to the timing node. A third option, Mixed, allows you to set external and line timing references. (Because mixed timing may cause timing loops, Cisco does not recommend its use. Use this mode with care.)
Revertive—If this check box is selected, the ONS 15454 SDH reverts to a primary reference source after the conditions that caused it to switch to a secondary timing reference are corrected.
Revertive Time—If Revertive is checked, indicate the amount of time the ONS 15454 SDH will wait before reverting to its primary timing source.
Step 3 In the BITS Facilities section, complete the following information:
Note The BITS Facilities section sets the parameters for your BITS1 and
BITS2 timing references. Many of these settings are determined by the timing source
manufacturer. If equipment is timed through BITS Out, you can set timing parameters to
meet the requirements of the equipment.
E1, 2.048 MHz, 64 KHz—Choose E1, 2.048 MHz, or 64 KHz depending on the signal supported in your market. For example, 64 KHz is used in Japan. E1, 2.048 MHz, and 64 KHz are physical signal modes used to transmit the external clock (from a GPS, for example) to BITS.
State—Set the BITS reference to IS (In Service) or OOS (Out of Service). For nodes set to line timing with no equipment timed through BITS Out, set Stateto OOS. For nodes using External timing or Line timing with equipment timed through BITS Out, set State to IS.
Coding—Choose the coding used by your BITS reference, either HDB3 or AMI. If you selected 2.048 MHz, or 64 KHz, the coding option is disabled.
Framing—Choose the framing used by your BITS reference, either unframed, FAS, FAS + CAS, FAS + CRC, or FAS + CAS + CRC. If you selected 2.048 MHz or 64 KHz, the framing option is disabled.
Sync Messaging—Select the check box to enable SSM. SSM is used to deliver clock quality. The SSM supported in SDH is G811, STU, G812T, G812L, SETS, DUS (ordered from high quality to low quality). If you selected 2.048 MHz or 64 KHz, the SSM option is disabled.
AIS Threshold—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 sent. (The AIS threshold is used when Sync. Messaging is disabled or framing is set to unframed, FAS, or FAS + CAS.)
LBO—Choose a BITS cable length. Line build out (LBO) relates to the BITS cable length.
Sa bit—Choose one of 5 Sa bits (Sa4, Sa5, Sa6, Sa7, or Sa8). The Sa bit transmits the SSM message. If you selected 2.048 MHz or 64 KHz, the Sa bit option is disabled.
Step 4 Under Reference Lists, complete the information (Figure 3-15):
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 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 Reference—Allows you to define three timing references (Ref 1, Ref 2, Ref 3). The node uses Reference 1 unless a failure occurs to that reference, in which case, the node uses Reference 2. If Reference 2 fails, the node uses Reference 3, which is typically set to Internal Clock. The internal clock is the Stratum 3 clock provided on the TCC-I. The options displayed depend on the Timing Mode setting.
Timing Mode set to External—Your options are BITS1, BITS2, and Internal Clock.
Timing Mode set to Line—Your options are the node's working optical cards and Internal Clock. Select the cards/ports that are directly or indirectly connected to the node wired to the BITS source, that is, select the node's trunk cards. Set Reference 1 to the trunk card that is closest to the BITS source. For example, if Slot 5 is connected to the node wired to the BITS source, select Slot 5 as Reference 1.
Timing Mode set to Mixed—Both BITS and optical cards are available, allowing you to set a mixture of external BITS and optical trunk cards as timing references.
BITS 1 Out/BITS 2 Out—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.
Figure 3-15 Reference list in the ONS 15454 SDH Timing tab
Step 5 Click Apply.
Note Refer to the Cisco ONS 15454 SDH Troubleshooting and Maintenance Guide for timing-related
alarms.
Procedure: Set Up Internal Timing for the ONS 15454 SDH
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. Internal timing is Stratum 3 and not intended for permanent use. All ONS 15454 SDH nodes should be timed to a Stratum 2 or better primary reference source.
Note CTC refers to Timing A and Timing B as BITS 1 and BITS 2. The MIC-C/T/P
FMEC connector is labeled as Timing A and Timing B.
Step 1 Log into the node that will serve as the timing source.
Step 2 From the CTC node view, click the Provisioning > Timing tabs (Figure 3-16).
Figure 3-16 Setting up internal ONS 15454 SDH timing
Step 3 In the General Timing section, enter the following:
Timing Mode—Choose External.
Revertive—Not relevant for internal timing; the default setting (checked) is sufficient.
Revertive Time—Not relevant for internal timing; the default setting (5 minutes) is sufficient.
Step 4 In the BITS Facilities section, enter the following information:
E1, 2.048 MHz, 64 KHz—Choose E1, 2.048 MHz, or 64 KHz depending on the signal supported in your market. For example, 64 KHz is used in Japan. E1, 2.048 MHz, and 64 KHz are physical signal modes used to transmit the external clock (from a GPS for example) to BITS.
State—Set BITS 1 and BITS 2 to OOS (Out of Service).
Coding—Not relevant for internal timing; the default (HDB3) is sufficient.
Framing—Not relevant for internal timing; the default (FAS + CAS + CRC) is sufficient.
Sync Messaging—The box is checked automatically. SSM is used to deliver clock quality. The SSM supported in SDH is G811, STU, G812T, G812L, SETS, DUS (ordered from high quality to low quality). If you selected 2.048 MHz, or 64 KHz, the SSM option is disabled.
AIS Threshold—Not relevant for internal timing.
LBO—Not relevant for internal timing; line build out (LBO) relates to the BITS cable length.
Sa bit—Not relevant for internal timing; the Sa bit is used to transmit the SSM message.
Step 5 In the Reference Lists section, enter the following information:
NE Reference
Ref1—Set to Internal Clock.
Ref2—Set to Internal Clock.
Ref3—Set to Internal Clock.
BITS 1 Out/BITS 2 Out—Set to None.
Step 6 Click Apply.
Step 7 Log into a node that will be timed from the node that was set up in Step 1 to Step 6.
Step 8 In the CTC node view, click the Provisioning > Timing tabs.
Step 9 In the General Timing section, enter the following:
Timing Mode—Set to Line.
Revertive—Not relevant for internal timing; the default setting (checked) is sufficient.
Revertive Time—The default setting (5 minutes) is sufficient.
Step 10 In the Reference Lists section, enter the following:
NE Reference
Ref-1—Use the pull-down menu to choose the STM-N trunk card with the closest connection to the node in Step 3.
Ref-2—Use the pull-down menu to choose the STM-N trunk card with the next closest connection to the node in Step 3.
Ref-3—Use the pull-down menu to choose Internal Clock.
Step 11 Click Apply.
Step 12 Repeat Step 7 to Step 11 at each node that will be timed by the node serving as the timing source.
3.6 Creating Card ProtectionGroups
The ONS 15454 SDH provides several card protection methods. When you set up protection for ONS 15454 SDH cards, you must choose between maximum protection and maximum slot availability. The highest protection reduces the number of available card slots; the highest slot availability reduces the protection. Table 3-6 shows the protection types that can be set up for ONS 15454 SDH cards.
Table 3-6 Protection Types
Type
Cards
Description
1:1
E1-N-14
E3-12
DS3i-N-12
Pairs one working card with one protect card. Install the protect card in an odd-numbered slot and the working card in an even-numbered slot. Use the slot that is next to the protect slot, toward the center of the shelf. For example: protect in slot 1, working in Slot 2; protect in Slot 3, working in Slot 4; protect in Slot 15, working in Slot 14.
1:N
E1-N-14
DS3i-N-12
Assigns one protect card for several working cards. The maximum is 1:5. Protect cards (E1-N-14, DS3i-N-12) must be installed in Slots 3 or 15 and the cards they protect must be on the same side of the shelf. Protect cards must match the cards they protect. For example, a E1-N-14 can only protect E1-N-14 cards. If a failure clears, traffic reverts to the working card after the reversion time has elapsed.
1+1
Any optical
Pairs a working optical port with a protect optical port. Protect ports must match the working ports. For example, Port 1 of an STM-1 card can only be protected by Port 1 of another STM-1 card. Cards do not need to be in adjoining slots.
Unprotected
Any
Unprotected cards can cause signal loss if a card fails or incurs a signal error. However, because no card slots are reserved for protection, unprotected schemes maximize the service available for use on the ONS 15454 SDH. Unprotected is the default protection type.
Procedure: Create Protection Groups
Purpose
Use this procedure to create card protection groups for the ONS 15454 SDH. Unprotected cards can cause signal loss if a card fails or incurs a signal error.
Step 1 From the CTC node view, click the Provisioning > Protection tabs.
Step 2 Under Protection Groups, click Create.
Figure 3-17 Creating card protection groups
Step 3 In the Create Protection Group dialog box, enter the following:
Name—Type a name for the protection group. The name can have up to 32 alphanumeric characters.
Type—Choose the protection type (1:1, 1:N, or 1+1) from the pull-down menu. The protection selected determines the cards that are available to serve as protect and working cards. For example, if you choose 1:N protection, only E1-N-14 and DS3i-N-12 cards are displayed.
Protect Card or Port—Choose the protect card (if you are using 1:1 or 1:N) or protect port (if you are using 1+1) from the pull-down menu.
Based on these selections, a list of available working cards or ports is displayed under Available Cards or Available Ports. Figure 3-18 shows a 1:1 protection group.
Figure 3-18 Creating a 1:1 protection group
Step 4 From the Available Cards or Available Ports list, choose the card or port that you want to be the working card or port (the card(s) or port(s) that will be protected by the card or port selected in Protect Cards or Protect Ports). Click the top arrow button to move each card or port to the Working Cards or Working Ports list.
Step 5 Complete the remaining fields:
Bidirectional switching—(optical cards only) Check if you want both the transmit and the receive channels to switch if a failure occurs to one.
Revertive—If checked, the ONS 15454 SDH reverts traffic to the working card or port after failure conditions stay corrected for the amount of time entered in the Reversion time field.
Reversion time—If Revertive is checked, enter the amount of time that will elapse after a failure is corrected before the ONS 15454 SDH will revert to the working card or port.
Step 6 Click OK.
Caution Before running traffic on a protected card within a protection group, enable the ports of all protection group cards. See the "Put Ports In or Out of Service" procedure.
Step 1 From the CTC node view, click the Provisioning > Protection tabs.
Step 2 In the Protection Groups section, choose a protection group.
Step 3 In the Selected Group section, edit the fields as appropriate:
Name—Type a name for the protection group. The name can have up to 32 alphanumeric characters.
Type—Choose the protection type (1:1, 1:N, or 1+1) from the pull-down menu. The protection selected determines the cards that are available to serve as protect and working cards. For example, if you choose 1:1 protection, only E1, E3, and DS3i cards are displayed.
Protect Card or Port—Choose the protect card (if you are using 1:1 or 1:N) or protect port (if you are using 1+1) from the pull-down menu.
Based on these selections, a list of available working cards or ports is displayed under Available Cards or Available Ports.
Step 4 From the Available Cards or Available Ports list, choose the card or port that you want to be the working card or port (that is, the card(s) or port(s) that will be protected by the card or port selected in Protect Cards or Protect Ports). Click the top arrow button to move each card or port to the Working Cards or Working Ports list.
Step 5 Complete the remaining fields:
Bidirectional switching—(optical cards only) Click if you want both the transmit and the receive channels to switch if a failure occurs to one.
Revertive—If checked, the ONS 15454 SDH reverts traffic to the working card or port after a failure has been corrected for the amount of time entered in the Reversion time field.
Reversion time—If Revertive is checked, enter the amount of time following a failure correction that the ONS 15454 SDH will revert to the working card or port.
Step 6 Click Apply.
Procedure: Delete Protection Groups
Purpose
Use this procedure to delete a card protection group.
Step 1 From the CTC node view, click the Maintenance > Protection tabs.
Step 2 Verify that working traffic is not running on the protect card:
a. In the Protection Groups section, choose the group you want to delete.
b. In the Selected Group section, verify that the protect card is in standby mode. If the protect card is in standby mode, continue with Step 3. If it is active, complete Step c.
c. If the working card is in standby mode, manually switch traffic back to the working card. In the Selected Group pane, click the working card, then click Manual. Verify that the protect card switches to standby mode and the working card is active. If the protect card is standby, continue with Step 3. If the protect card is still active, do not continue. Begin troubleshooting procedures or call technical support.
Step 3 From the node view, click the Provisioning > Protection tabs.
Step 4 In the Protection Groups section, click a protection group.
Step 5 Click Delete.
3.7 Setting Network Element Defaults
This section describes the factory-configured (default) network element (NE) settings for the Cisco ONS 15454 SDH. It includes descriptions of card default settings and node default settings and provides procedures for importing, exporting and editing the settings. Ethernet card settings are not included in the factory-configured settings.
The NE defaults are pre-installed on each ONS 15454 SDH (on the TCC-I cards). The NE defaults include card-level and node-level defaults.
If you use the Defaults Editor or import a new defaults file, that is, if defaults are changed, the changes apply only to cards installed subsequently (after the defaults change) or to slots pre-provisioned subsequently. A new defaults file will not take effect for cards already installed when the change takes place or for slots already pre-provisioned when the change takes place.
Changes made manually to the node-level default settings (either when you initially turn up a node or change node settings later) override the default settings. If you change the default settings, using either the Defaults Editor or by importing a new defaults file, the new defaults take effect immediately.
Use the following procedures if you need to edit, import, or export NE defaults.
Procedure: Edit Network Element Defaults
Purpose
This procedure edits the NE defaults using the NE Defaults Editor. The new defaults can either be applied only to the node on which they are edited or exported to a file and imported for use on other nodes.
Step 1 After logging into the node, click the Provisioning>Defaults Editor tabs.
Step 2 Under Defaults Selector, choose either a card (if editing card-level defaults) or NODE (if editing node-level defaults). Clicking on NODE lists all available NE defaults (both node- and card-level) under Property Name.
Step 3 Locate a default you want to change under Property Name.
Step 4 Click in the Default Value column for the default property you are changing and either choose a value from the drop-down menu (available for some node-level settings only), or type in the desired new value.
Note Clicking Reset before clicking Apply will return all values to their original setting.
Step 5 Click Apply (click in the Property Name column to activate the Apply button if it is unavailable).
Step 6 A dialog box opens telling you that applying defaults for node level attributes overrides current provisioning and asks if you want to continue. Click Yes.
Note Changes to node settings take effect upon clicking Apply. Changes to the IIOP Listener Port
setting reboots the TCC-I. Changes made to card settings using the Defaults Editor do not
change the settings for cards that are currently installed. Card settings must be manually
changed by opening the cards.
Procedure: Import Network Element Defaults
Purpose
This procedure imports the NE defaults using the NE Defaults Editor. The defaults can either be imported from the CTC software CD (factory defaults) or from a customized file exported and saved from a node.
Step 1 After logging into the node, click the Provisioning>Defaults Editor tabs.
Step 2 Click Import.
Step 3 Click Browse and browse to the file you are importing if the correct file name and location of the desired file do not appear in the Import Defaults from File dialog box.
Step 4 When the correct file name and location appear in the dialog box, click OK.
A pencil icon will appear next to any default value that will be changed as a result of importing the new defaults file.
Step 5 Click Apply.
Step 6 A dialog box opens telling you that applying defaults for node level attributes overrides current provisioning and asks if you want to continue. Click Yes.
Note Changes to node settings take effect upon clicking Apply. Changes to the IIOP Listener Port setting
reboots the TCC-I. Changes made to card settings using the Defaults Editor do not change the settings
for cards that are currently installed. Card settings must be manually changed by opening the cards.
Procedure: Export Network Element Defaults
Purpose
This procedure exports the NE defaults using the NE Defaults Editor. The exported defaults can be imported to other nodes.
Step 1 After logging into the node, click the Provisioning>Defaults Editor tabs.
Step 2 Click Export.
Step 3 Click Browse and browse to the location where you want to export the file if it does not appear in the Export Defaults to File dialog box.
Step 4 Change the file name to something easy to remember (the file name has no extension).
Step 5 Click OK.
3.7.1 Card Default Settings
The tables in this section list the default settings for each card. Cisco provides the following settings preprovisioned for the ONS 15454 optical and electrical cards:
Auto In-Service (AINS) Soak Time (E1, E3, DS3I, and STM-N cards) is the length of time that elapses between an AINS port receiving a valid signal and when it automatically changes to in-service status.
Line Type (E1 and DS3I cards) defines the type of framing used.
Loopback (DS3I) defines whether or not far end loopbacks are inhibited for the DS3I card.
Line Length (DS3I) defines the distance (in feet) from the backplane connection to the next termination point.
Port State (E1, E3, DS3I, and STM-N cards) sets the port to one of the four available states (IS, OOS, OOS_MT, or OOS_AINS), depending on whether you need ports in or out of service.
PM Threshold Settings (E1, E3, DS3I, and STM-N cards) set the performance monitoring parameters for gathering performance data and detecting problems early.
Table 3-12 lists the STM4-4 card default settings.
Table 3-12 STM4-4 Cards Default Settings
Property Name
Default Value
STM4-4.config.line.AINSSoakTime
08:00 (hours:minutes)
STM4-4.config.line.State
OOS
STM4-4.pmthresholds.ms.farend.15min.BBE
5315 (count)
STM4-4.pmthresholds.ms.farend.15min.EB
5315 (count)
STM4-4.pmthresholds.ms.farend.15min.ES
87 (seconds)
STM4-4.pmthresholds.ms.farend.15min.SES
1 (seconds)
STM4-4.pmthresholds.ms.farend.15min.UAS
3 (seconds)
STM4-4.pmthresholds.ms.farend.1day.BBE
53150 (count)
STM4-4.pmthresholds.ms.farend.1day.EB
53150 (count)
STM4-4.pmthresholds.ms.farend.1day.ES
864 (seconds)
STM4-4.pmthresholds.ms.farend.1day.SES
4 (seconds)
STM4-4.pmthresholds.ms.farend.1day.UAS
10 (seconds)
STM4-4.pmthresholds.ms.nearend.15min.BBE
5315 (count)
STM4-4.pmthresholds.ms.nearend.15min.EB
5315 (count)
STM4-4.pmthresholds.ms.nearend.15min.ES
87 (seconds)
STM4-4.pmthresholds.ms.nearend.15min.NPJC-PDET
60 (count)
STM4-4.pmthresholds.ms.nearend.15min.NPJC-PGEN
60 (count)
STM4-4.pmthresholds.ms.nearend.15min.PPJC-PDET
60 (count)
STM4-4.pmthresholds.ms.nearend.15min.PPJC-PGEN
60 (count)
STM4-4.pmthresholds.ms.nearend.15min.PSC
1 (count)
STM4-4.pmthresholds.ms.nearend.15min.PSC-W
1 (count)
STM4-4.pmthresholds.ms.nearend.15min.PSD
300 (seconds)
STM4-4.pmthresholds.ms.nearend.15min.PSD-W
300 (seconds)
STM4-4.pmthresholds.ms.nearend.15min.SES
1 (seconds)
STM4-4.pmthresholds.ms.nearend.15min.UAS
3 (seconds)
STM4-4.pmthresholds.ms.nearend.1day.BBE
53150 (count)
STM4-4.pmthresholds.ms.nearend.1day.EB
53150 (count)
STM4-4.pmthresholds.ms.nearend.1day.ES
864 (seconds)
STM4-4.pmthresholds.ms.nearend.1day.NPJC-PDET
5760 (count)
STM4-4.pmthresholds.ms.nearend.1day.NPJC-PGEN
5760 (count)
STM4-4.pmthresholds.ms.nearend.1day.PPJC-PDET
5760 (count)
STM4-4.pmthresholds.ms.nearend.1day.PPJC-PGEN
5760 (count)
STM4-4.pmthresholds.ms.nearend.1day.PSC
5 (count)
STM4-4.pmthresholds.ms.nearend.1day.PSC-W
5 (count)
STM4-4.pmthresholds.ms.nearend.1day.PSD
600 (seconds)
STM4-4.pmthresholds.ms.nearend.1day.PSD-W
600 (seconds)
STM4-4.pmthresholds.ms.nearend.1day.SES
4 (seconds)
STM4-4.pmthresholds.ms.nearend.1day.UAS
10 (seconds)
STM4-4.pmthresholds.path.nearend.15min.BBE
25 (count)
STM4-4.pmthresholds.path.nearend.15min.EB
15 (count)
STM4-4.pmthresholds.path.nearend.15min.ES
12 (seconds)
STM4-4.pmthresholds.path.nearend.15min.SES
3 (seconds)
STM4-4.pmthresholds.path.nearend.15min.UAS
10 (seconds)
STM4-4.pmthresholds.path.nearend.1day.BBE
250 (count)
STM4-4.pmthresholds.path.nearend.1day.EB
125 (count)
STM4-4.pmthresholds.path.nearend.1day.ES
100 (seconds)
STM4-4.pmthresholds.path.nearend.1day.SES
7 (seconds)
STM4-4.pmthresholds.path.nearend.1day.UAS
10 (seconds)
STM4-4.pmthresholds.rs.nearend.15min.BBE
10000 (count)
STM4-4.pmthresholds.rs.nearend.15min.EB
10000 (count)
STM4-4.pmthresholds.rs.nearend.15min.ES
500 (seconds)
STM4-4.pmthresholds.rs.nearend.15min.SES
500 (seconds)
STM4-4.pmthresholds.rs.nearend.1day.BBE
100000 (count)
STM4-4.pmthresholds.rs.nearend.1day.EB
100000 (count)
STM4-4.pmthresholds.rs.nearend.1day.ES
5000 (seconds)
STM4-4.pmthresholds.rs.nearend.1day.SES
5000 (seconds)
Table 3-13 lists the STM-16 card default settings.
Table 3-13 STM-16 Cards Default Settings
Property Name
Default Value
STM16.config.line.AINSSoakTime
08:00 (hours:minutes)
STM16.config.line.State
OOS
STM16.pmthresholds.ms.farend.15min.BBE
21260 (count)
STM16.pmthresholds.ms.farend.15min.EB
21260 (count)
STM16.pmthresholds.ms.farend.15min.ES
87 (seconds)
STM16.pmthresholds.ms.farend.15min.SES
1 (seconds)
STM16.pmthresholds.ms.farend.15min.UAS
3 (seconds)
STM16.pmthresholds.ms.farend.1day.BBE
212600 (count)
STM16.pmthresholds.ms.farend.1day.EB
212600 (count)
STM16.pmthresholds.ms.farend.1day.ES
864 (seconds)
STM16.pmthresholds.ms.farend.1day.SES
4 (seconds)
STM16.pmthresholds.ms.farend.1day.UAS
10 (seconds)
STM16.pmthresholds.ms.nearend.15min.BBE
21260 (count)
STM16.pmthresholds.ms.nearend.15min.EB
21260 (count)
STM16.pmthresholds.ms.nearend.15min.ES
87 (seconds)
STM16.pmthresholds.ms.nearend.15min.NPJC-PDET
60 (count)
STM16.pmthresholds.ms.nearend.15min.NPJC-PGEN
60 (count)
STM16.pmthresholds.ms.nearend.15min.PPJC-PDET
60 (count)
STM16.pmthresholds.ms.nearend.15min.PPJC-PGEN
60 (count)
STM16.pmthresholds.ms.nearend.15min.PSC
1 (count)
STM16.pmthresholds.ms.nearend.15min.PSC-R
1 (count)
STM16.pmthresholds.ms.nearend.15min.PSC-S
1 (count)
STM16.pmthresholds.ms.nearend.15min.PSC-W
1 (count)
STM16.pmthresholds.ms.nearend.15min.PSD
300 (seconds)
STM16.pmthresholds.ms.nearend.15min.PSD-R
300 (seconds)
STM16.pmthresholds.ms.nearend.15min.PSD-S
300 (seconds)
STM16.pmthresholds.ms.nearend.15min.PSD-W
300 (seconds)
STM16.pmthresholds.ms.nearend.15min.SES
1 (seconds)
STM16.pmthresholds.ms.nearend.15min.UAS
3 (seconds)
STM16.pmthresholds.ms.nearend.1day.BBE
212600 (count)
STM16.pmthresholds.ms.nearend.1day.EB
212600 (count)
STM16.pmthresholds.ms.nearend.1day.ES
864 (seconds)
STM16.pmthresholds.ms.nearend.1day.NPJC-PDET
5760 (count)
STM16.pmthresholds.ms.nearend.1day.NPJC-PGEN
5760 (count)
STM16.pmthresholds.ms.nearend.1day.PPJC-PDET
5760 (count)
STM16.pmthresholds.ms.nearend.1day.PPJC-PGEN
5760 (count)
STM16.pmthresholds.ms.nearend.1day.PSC
5 (count)
STM16.pmthresholds.ms.nearend.1day.PSC-R
5 (count)
STM16.pmthresholds.ms.nearend.1day.PSC-S
5 (count)
STM16.pmthresholds.ms.nearend.1day.PSC-W
5 (count)
STM16.pmthresholds.ms.nearend.1day.PSD
600 (seconds)
STM16.pmthresholds.ms.nearend.1day.PSD-R
600 (seconds)
STM16.pmthresholds.ms.nearend.1day.PSD-S
600 (seconds)
STM16.pmthresholds.ms.nearend.1day.PSD-W
600 (seconds)
STM16.pmthresholds.ms.nearend.1day.SES
4 (seconds)
STM16.pmthresholds.ms.nearend.1day.UAS
10 (seconds)
STM16.pmthresholds.path.nearend.15min.BBE
25 (count)
STM16.pmthresholds.path.nearend.15min.EB
15 (count)
STM16.pmthresholds.path.nearend.15min.ES
12 (seconds)
STM16.pmthresholds.path.nearend.15min.SES
3 (seconds)
STM16.pmthresholds.path.nearend.15min.UAS
10 (seconds)
STM16.pmthresholds.path.nearend.1day.BBE
250 (count)
STM16.pmthresholds.path.nearend.1day.EB
125 (count)
STM16.pmthresholds.path.nearend.1day.ES
100 (seconds)
STM16.pmthresholds.path.nearend.1day.SES
7 (seconds)
STM16.pmthresholds.path.nearend.1day.UAS
10 (seconds)
STM16.pmthresholds.rs.nearend.15min.BBE
10000 (count)
STM16.pmthresholds.rs.nearend.15min.EB
10000 (count)
STM16.pmthresholds.rs.nearend.15min.ES
500 (seconds)
STM16.pmthresholds.rs.nearend.15min.SES
500 (seconds)
STM16.pmthresholds.rs.nearend.1day.BBE
100000 (count)
STM16.pmthresholds.rs.nearend.1day.EB
100000 (count)
STM16.pmthresholds.rs.nearend.1day.ES
5000 (seconds)
STM16.pmthresholds.rs.nearend.1day.SES
5000 (seconds)
Table 3-14 lists the STM-64 card default settings.
Table 3-14 STM-64 Cards Default Settings
Property Name
Default Value
STM64.config.line.AINSSoakTime
08:00 (hours:minutes)
STM64.config.line.State
OOS
STM64.pmthresholds.ms.farend.15min.BBE
85040 (count)
STM64.pmthresholds.ms.farend.15min.EB
85040 (count)
STM64.pmthresholds.ms.farend.15min.ES
87 (seconds)
STM64.pmthresholds.ms.farend.15min.SES
1 (seconds)
STM64.pmthresholds.ms.farend.15min.UAS
3 (seconds)
STM64.pmthresholds.ms.farend.1day.BBE
85040 (count)
STM64.pmthresholds.ms.farend.1day.EB
85040 (count)
STM64.pmthresholds.ms.farend.1day.ES
864 (seconds)
STM64.pmthresholds.ms.farend.1day.SES
4 (seconds)
STM64.pmthresholds.ms.farend.1day.UAS
10 (seconds)
STM64.pmthresholds.ms.nearend.15min.BBE
85040 (count)
STM64.pmthresholds.ms.nearend.15min.EB
85040 (count)
STM64.pmthresholds.ms.nearend.15min.ES
87 (seconds)
STM64.pmthresholds.ms.nearend.15min.NPJC-PDET
60 (count)
STM64.pmthresholds.ms.nearend.15min.NPJC-PGEN
60 (count)
STM64.pmthresholds.ms.nearend.15min.PPJC-PDET
60 (count)
STM64.pmthresholds.ms.nearend.15min.PPJC-PGEN
60 (count)
STM64.pmthresholds.ms.nearend.15min.PSC
1 (count)
STM64.pmthresholds.ms.nearend.15min.PSC-R
1 (count)
STM64.pmthresholds.ms.nearend.15min.PSC-S
1 (count)
STM64.pmthresholds.ms.nearend.15min.PSC-W
1 (count)
STM64.pmthresholds.ms.nearend.15min.PSD
300 (seconds)
STM64.pmthresholds.ms.nearend.15min.PSD-R
300 (seconds)
STM64.pmthresholds.ms.nearend.15min.PSD-S
300 (seconds)
STM64.pmthresholds.ms.nearend.15min.PSD-W
300 (seconds)
STM64.pmthresholds.ms.nearend.15min.SES
1 (seconds)
STM64.pmthresholds.ms.nearend.15min.UAS
3 (seconds)
STM64.pmthresholds.ms.nearend.1day.BBE
850400 (count)
STM64.pmthresholds.ms.nearend.1day.EB
850400 (count)
STM64.pmthresholds.ms.nearend.1day.ES
864 (seconds)
STM64.pmthresholds.ms.nearend.1day.NPJC-PDET
5760 (count)
STM64.pmthresholds.ms.nearend.1day.NPJC-PGEN
5760 (count)
STM64.pmthresholds.ms.nearend.1day.PPJC-PDET
5760 (count)
STM64.pmthresholds.ms.nearend.1day.PPJC-PGEN
5760 (count)
STM64.pmthresholds.ms.nearend.1day.PSC
5 (count)
STM64.pmthresholds.ms.nearend.1day.PSC-R
5 (count)
STM64.pmthresholds.ms.nearend.1day.PSC-S
5 (count)
STM64.pmthresholds.ms.nearend.1day.PSC-W
5 (count)
STM64.pmthresholds.ms.nearend.1day.PSD
600 (seconds)
STM64.pmthresholds.ms.nearend.1day.PSD-R
600 (seconds)
STM64.pmthresholds.ms.nearend.1day.PSD-S
600 (seconds)
STM64.pmthresholds.ms.nearend.1day.PSD-W
600 (seconds)
STM64.pmthresholds.ms.nearend.1day.SES
4 (seconds)
STM64.pmthresholds.ms.nearend.1day.UAS
10 (seconds)
STM64.pmthresholds.path.nearend.15min.BBE
25 (count)
STM64.pmthresholds.path.nearend.15min.EB
15 (count)
STM64.pmthresholds.path.nearend.15min.ES
12 (seconds)
STM64.pmthresholds.path.nearend.15min.SES
3 (seconds)
STM64.pmthresholds.path.nearend.15min.UAS
10 (seconds)
STM64.pmthresholds.path.nearend.1day.BBE
250 (count)
STM64.pmthresholds.path.nearend.1day.EB
125 (count)
STM64.pmthresholds.path.nearend.1day.ES
100 (seconds)
STM64.pmthresholds.path.nearend.1day.SES
7 (seconds)
STM64.pmthresholds.path.nearend.1day.UAS
10 (seconds)
STM64.pmthresholds.rs.nearend.15min.BBE
10000 (count)
STM64.pmthresholds.rs.nearend.15min.EB
10000 (count)
STM64.pmthresholds.rs.nearend.15min.ES
500 (seconds)
STM64.pmthresholds.rs.nearend.15min.SES
500 (seconds)
STM64.pmthresholds.rs.nearend.1day.BBE
100000 (count)
STM64.pmthresholds.rs.nearend.1day.EB
100000 (count)
STM64.pmthresholds.rs.nearend.1day.ES
5000 (seconds)
STM64.pmthresholds.rs.nearend.1day.SES
5000 (seconds)
3.7.2 Node Default Settings
Table 3-15 lists the ONS 15454 SDH node-level default settings for the Cisco ONS 15454 SDH. Cisco provides the following types of settings preprovisioned for each ONS 15454 SDH node:
Subnetwork connection protection (SNCP) reversion
MS-SPRing reversion
LMSP protection
IIOP listener port
Timing parameters
Table 3-15 Node Default Settings
Property Name
Default Value
NODE.circuits.sncp.ReversionTime
5.0 (minutes)
NODE.circuits.sncp.Revertive
FALSE
NODE.general.DefaultsDescription
Factory defaults
NODE.general.IIOPListenerPort (reboots node)
57790 (port #)
NODE.general.LoginWarningMessage
Warning This system is restricted to authorized users for business purposes. Unauthorized access is a violation of the law. This service may be monitored for administrative and security reasons. By proceeding, you consent to this monitoring.
