Cisco ONS 15454 DWDM Configuration Guide, Release 9.3

Turn Up a Node

---

This chapter explains how to provision a single Cisco ONS 15454 dense wavelength division multiplexing (DWDM) node and turn it up for service, including assigning the node name, date, and time; provisioning timing references; provisioning network attributes such as IP address and default router; setting up users and user security; installing cards; and creating DWDM connections.

Note The procedures and tasks described in this chapter for the Cisco ONS 15454 platform is applicable to the Cisco ONS 15454 M2 and Cisco ONS 15454 M6 platforms, unless noted otherwise.

Note Procedures in this chapter require that you have a network plan calculated for your DWDM network with Cisco Transport Planner, Release 9.2. Cisco Transport Planner is a DWDM planning tool that is available from your Cisco account representative. Cisco Transport Planner prepares a shelf plan for each network node and calculates the power and attenuation levels for the DWDM cards installed in the node. For information about Cisco Transport Planner, contact your Cisco account representative. For instructions on using Cisco Transport Planner, refer to the Cisco Transport Planner DWDM Operations Guide.

Note Unless otherwise specified, in this document “ONS 15454” refers to both ANSI (ONS 15454) and ETSI (ONS 15454 SDH) shelf assemblies.

Note Cisco Transport Controller (CTC) views referenced in these procedures depend on the ONS 15454 mode. In single-shelf mode, the views are network, node, and card. In multishelf mode, the views are network, multishelf, shelf, and card. For more information about CTC views, refer to CTC Enhancements, Operations, and Shortcuts.

Before You Begin

This section lists the non-trouble procedures (NTPs) needed to turn up a DWDM node. Turn to an NTP for applicable detail-level procedures (DLPs), known as tasks.

1. G139 Verify Cisco Transport Planner Reports and Files—Complete this procedure first.

2. G22 Verify Common Card Installation—Complete this procedure next.

3. G250 Verify Digital Image Signing (DIS) Information—Complete this procedure to retrieve the software signature information and version of the digitally signed software. You can also retrieve the public keys installed on the node using this procedure.s

4. G144 Provision a Multishelf Node—Complete this procedure as needed.

5. G23 Create Users and Assign Security —Complete this procedure to create CTC users and assign their security levels.

6. G24 Set Up Name, Date, Time, and Contact Information—Continue with this procedure to set the node name, date, time, location, and contact information.

7. G25 Set Battery Power Monitor Thresholds—Continue with this procedure to set the node battery power thresholds.

8. G26 Set Up CTC Network Access—Continue with this procedure to provision the IP address, default router, subnet mask, and other network configuration settings.

9. G194 Set Up EMS Secure Access to the ONS 15454—Continue with this procedure to connect the CTC in secure mode.

10. G341 Set Up Secure Access to the ONS 15454 TL1—Continue with this procedure to enable secure access to TL1.

11. G27 Set Up the ONS 15454 for Firewall Access—Continue with this procedure if the ONS 15454 will be accessed behind firewalls.

12. G28 Create FTP Host—Continue with this procedure if to create FTP host for ENE database backup.

13. G132 Provision OSI—Continue with this procedure if the ONS 15454 will be installed in networks with third-party, Open Systems Interconnection (OSI)-based network elements (NEs).

14. G29 Set Up SNMP —Complete this procedure if Simple Network Management Protocol (SNMP) will be used for network monitoring.

15. G143 Import the Cisco Transport Planner NE Update Configuration File—Complete this procedure to preprovision the ONS 15454 slots and install the card and automatic node setup (ANS) parameters.

16. G328 Add, Modify, or Delete ANS Parameters—Complete this procedure, as needed, to add or delete ANS parameters.

17. G30 Install the DWDM Cards —Complete this procedure to install the DWDM cards, including the OSCM, OSC-CSM, 32WSS, 32WSS-L, 40-WSS-C, 40-WSS-CE, 40-WXC-C, 80-WXC-C, 40-SMR1-C, 40-SMR2-C, OPT-BST, OPT-BST-E, OPT-BST-L, OPT-AMP-L, OPT-AMP-17-C, OPT-AMP-C, OPT-RAMP-C, OPT-RAMP-CE, OPT-PRE, 32MUX-O, 40-MUX-C, 32DMX-O, 32DMX, 32DMX-L, 40-DMX-C, 40-DMX-CE, 4MD-xx.x, AD-1C-xx.x, AD-2C-xx.x, AD-4C-xx.x, AD-1B-xx.x, AD-4B-xx.x, MMU, PSM, TDC-CC and TDC-FC.

18. G31 Install the DWDM Dispersion Compensating Units—Complete this procedure, as needed, to install a dispersion compensating unit (DCU).

19. G179 Install the TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, ADM-10G, and OTU2_XP Cards—Complete this procedure, as needed, to install transponder (TXP), muxponder (MXP), GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE, ADM-10G, or OTU2_XP cards.

20. G123 Install the Filler Cards—Complete this procedure, as needed, to install ONS 15454 filler cards.

21. G239 Add and Delete Passive Units —Complete this procedure, as needed, to add or delete passive units.

22. G34 Install Fiber-Optic Cables on DWDM Cards and DCUs —Complete this procedure, as needed, to install the fiber-optic cables on the DWDM cards.

23. G140 Install Fiber-Optic Cables Between Terminal, Hub, or ROADM Nodes —Complete this procedure, as needed, to connect TXP, MXP, GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE, ADM-10G, or OTU2_XP cards to DWDM cards in a terminal, hub, or reconfigurable optical add-drop multiplexer (ROADM) node through the patch panel.

24. G185 Install Fiber-Optic Cables between Mesh Nodes —Complete this procedure, as needed, to connect 40-WXC-C or 80-WXC-C cards in a mesh node to the 4-degree or 8-degree patch panel.

25. G141 Install Fiber-Optic Cables for Y-Cable Protection Modules —Complete this procedure, as needed, to connect fiber-optic cables to Y-cable modules from client TXP, MXP, GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards.

26. G152 Create and Verify Internal Patchcords—Complete this procedure to calculate the DWDM cable connections.

27. G209 Create, Edit, and Delete Optical Sides—Complete this procedure to create, edit, and delete an optical side.

28. G38 Provision OSC Terminations—Complete this procedure next.

29. G37 Run Automatic Node Setup—Complete this procedure next.

30. G39 Verify OSCM Transmit Power—Complete this procedure next.

31. G163 Upgrade Nodes in Single-Shelf Mode to Multishelf Mode—Complete this procedure as needed.

32. G210 Provision Node for SNMPv3 —Complete this procedure if Simple Network Management Protocol version 3(SNMPv3) will be used for network monitoring.

NTP-G139 Verify Cisco Transport Planner Reports and Files

Step 1 Verify that you have the Cisco Transport Planner reports and files shown in Table 14-1 for the node that you will provision. The reports and files can be provided in one of the following ways:

• If you have Cisco Transport Planner, verify that you have the electronic network design plan from which you can generate the reports in Cisco Transport Planner. For information about generating the reports, refer to the Cisco Transport Planner DWDM Operations Guide .
• If you do not have Cisco Transport Planner, you must have printouts of all reports listed in Table 14-1 except the Assisted Configuration Setup file. Assisted Configuration Setup is an electronic file that will be imported into CTC. You must be able to access it from the CTC computer used to provision the node
• If you not do not have all the reports and files listed in Table 14-1 , do not continue. See your site planner or network planner for the required information and files.

Step 2 Print Table 14-1 for reference. You will need information from the reports during node turn-up.

Stop. You have completed this procedure.

NTP-G22 Verify Common Card Installation

Step 1 Verify the following:

• TCC2/TCC2P/TCC3 cards are installed in Slots 7 and 11 on the ONS 15454 shelf.
• Two TNC/TNCE/TSC/TSCE cards are installed in Slots 1 and 8 on the ONS 15454 M6 shelf.
• A stand-alone TNC/TNCE/TSC/TSCE card is installed in Slot 1 on the ONS 15454 M2 shelf.

Step 2 Verify that the FAIL LED is off on both TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE cards.

Step 3 Verify that the green ACT (active) LED is illuminated on one TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE card and that the amber STBY (standby) LED is illuminated on the other TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE card.

Note If the TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE cards are not installed, or if their LEDs are not operating as described, do not continue. Complete the “DLP-G33 Install the TCC2, TCC2P, or TCC3 Card” or “DLP-G604 Install the TNC TNCE, TSC, or TSCE Card” task in the Cisco CPT and Cisco ONS 15454 Hardware Installation Guide or refer to the Cisco ONS 15454 DWDM Troubleshooting Guide to resolve installation problems before proceeding to Step 4.

Step 4 (On 15454-DWDM shelf) If the AIC-I card is installed, verify that it is installed in Slot 9 and that its ACT (active) LED displays a solid green light.

Note If the AIC-I card is not installed and the card is required by the Cisco Transport Planner shelf layout, or if it is installed and its LEDs are not operating as described, do not continue. Complete the “DLP-G34 Install the AIC-I Card” task in the Cisco CPT and Cisco ONS 15454 Hardware Installation Guide or refer to the Cisco ONS 15454 DWDM Troubleshooting Guide to resolve installation problems before proceeding to Step 5.

Step 5 Verify that the software release shown on the LCD matches the software release required for your network. On the LCD, the software release is shown under the platform (SONET or SDH) and date/temperature. If the release does not match, perform one of the following procedures:

• Perform a software upgrade using a ONS 15454 software CD or ONS 15454 SDH software CD. Refer to the release-specific software upgrade document.
• On ONS 15454, replace the TCC2/TCC2P/TCC3 cards with cards containing the correct release.
• On ONS 15454 M6, replace the LCD and TNC/TNCE/TSC/TSCE cards with cards containing the correct release.
• On ONS 15454 M2, replace the power module and TNC/TNCE/TSC/TSCE cards with cards containing the correct release.

Step 6 (On ONS 15454 shelf) If the node will be configured as a multishelf node, verify that redundant MS-ISC-100T cards are installed (Slots 6 and 12 are recommended) and that the green ACT (active) LED is illuminated on both cards.

Note If the MS-ISC-100T card is not installed and the card is required by the Cisco Transport Planner shelf layout, or if the card’s LEDs are not operating as described, do not continue. Complete the “DLP-G309 Install the MS-ISC-100T Card” task in the Cisco CPT and Cisco ONS 15454 Hardware Installation Guide or refer to the Cisco ONS 15454 DWDM Troubleshooting Guide to resolve installation problems before proceeding to the next procedure.

Stop . You have completed this procedure .

NTP-G250 Verify Digital Image Signing (DIS) Information

Note The DIS information is applicable for TNC/TNCE/TSC/TSCE cards in the ONS 15454 M2 and ONS 15454 M6 platforms.

Step 1 Complete the DLP-G46 Log into CTC task at the node where you want to verify the DIS information.

Step 2 Do the following as applicable:

a. To retrieve the digitally signed software version, go to Step 3.

b. To retrieve the software signature information, go to Step 4.

c. To retrieve the public keys installed on the node, go to Step 5.

Step 3 In node view (single-shelf mode) or multishelf view (multishelf mode), click Maintenance > Software tab to retrieve the digitally signed software version. The following columns appear in the pane:

• Node—Displays the node name or IP address.
• Type—Displays the node type.
• Node Status —Displays the node status, which is based on the highest alarm level at the node.
• Working Version —Displays the working ONS node software version (the general software release number [n.n.n] followed by the specific software release identification number). For example, 9.2.0 (09.20-X10E-02.06).
• Protect Version —Displays the protect ONS node software version (the general software release number [n.n.n] followed by the specific software release identification number). For example, 9.2.0 (09.20-X10E-02.06).
• Download Status —Displays the status of any in-progress network software downloads.

Step 4 In node view (single-shelf mode) or shelf view (multishelf view), click Maintenance > DIS > Info > Retrieve Signature Information tab to retrieve signature information. The following information is displayed in the pane:

• Attribute — The following information is displayed:

– Organization Name—Displays the owner of the software image.

– Organization Unit—Displays the business unit within Cisco.

– Serial Number—Displays the serial number of the certificate with the digital signature.

– Common Name—Displays the name of the platform.

– Hash Algorithm—Displays the hashing algorithm used.

– Image Type—Shows the type of the image-Development or Production.

– Key Version—Indicates the key version used to digitally sign the image. A key version is identified with an alphabetical character that ranges from A to Z.

– Sign Algorithm—Refers to the RSA algorithm.

• Working Software Information— Displays the signature information of the working software.
• Protect Software Information— Displays the signature information of the protect software.

Note To refresh the signature information, click Refresh Signature Information.

Step 5 In node view (single-shelf mode) or shelf view (multishelf mode), click Maintenance > DIS > Available Keys > Retrieve All Keys tabs to retrieve public key information. The following information is displayed in the pane:

• Key Type— Displays the public key available on the system for verification:

– Release Key— Verifies release images.

– Development Key— Verifies the development images.

• Public Key Algorithm— Displays the name of the algorithm used for public key cryptography.
• Exponent— Displays the exponent of the public key algorithm—release or development keys.
• Key Version— Displays the key version used for verification.
• Modulus —Displays the modulus of the public key algorithm with a size of 2048 bits.

Note To refresh the public key information, click Refresh All Keys.

Stop. You have completed this procedure.

NTP-G144 Provision a Multishelf Node

Step 1 Complete the DLP-G46 Log into CTC task at the node that you want to configure as a multishelf node.

Step 2 If you want to set up the login node as the node controller, complete the following steps. If not, continue with Step 3.

a. In node view (single-node mode) or multishelf view (multishelf mode), click the Provisioning > General > Multishelf Config tabs.

b. Click Enable as Node Controller .

c. From the LAN Config drop-down list, complete one of the following:

• Choose Ethernet Switch if MS-ISC-100T cards or the Catalyst 2950 or the Catalyst 3560 switches are already installed and configured. Choose the public VLAN ID and private VLAN ID for the ONS 15454 multishelf node. In case of an ONS 15454 M6, the public VLAN ID and private VLAN ID are static (1 and 2 respectively).

Note Public VLAN ID is used by the node controller to communicate with the external network. Private VLAN ID is used by the node controller to communicate with the subtending shelves.

Note If the ONS 15454 M6 shelf is used as the node controller, then you can connect the subtending shelves directly to the MSM ports on the ECU. However, a Catalyst 3560 switch can also be used along with the ONS 15454 M6 node controller to extend the number of subtending shelves.

• Choose Stand-Alone if MS-ISC-100T cards are not installed yet but will be included in the final layout. This option will allow a safe migration of the TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE card database when the multishelf configuration is complete.

d. Click Apply .

e. In the confirmation dialog box, click Yes to allow the node to reboot. The CTC view changes to network view and the node icon changes to gray. Wait for the reboot to finish. (This might take several minutes.)

f. After the node reboots, double-click the node. The multishelf view appears.

Note The shelf ID of the node controller is automatically assigned as 1.

Step 3 If you want to add a node as a subtending shelf (either ONS 15454 or ONS 15454 M6) in the multishelf configuration, complete the following steps. If not, you have completed this procedure.

Note A Cisco ONS 15454 node configured with TCC2P and TCC3 cards must not be added to a multishelf configuration containing either of the following configurations:

• Cisco ONS 15454 node with TCC3 as the node controller
• Cisco ONS 15454 M6 node with TNC as the node controller

a. In multishelf view, right-click the white space in the rack and choose Add Shelf from the shortcut menu.

b. Select the type of subtending shelf (ONS 15454 or ONS 15454 M6).

c. In the Shelf ID Selection dialog box, choose a shelf ID (from 2 to 30) from the drop-down list.

d. Click OK . The shelf appears in multishelf view.

e. Disconnect the cross-over (CAT-5) LAN cable from the RJ-45 LAN (TCP/IP) port of the ONS 15454 subtending shelf TCC2/TCC2P/TCC3 card in Slot 11 or Slot 7, or from the EMS RJ-45 LAN (TCP/IP) on the ONS 15454 M6 subtending shelf that correspond to the TNC/TNCE/TSC/TSCE card.

f. Connect your Windows PC or Solaris workstation network interface card (NIC) to the RJ-45 LAN (TCP/IP) port on the TCC2/TCC2P/TCC3 card in Slot 11 or Slot 7, or to the EMS RJ-45 LAN (TCP/IP) on the ONS 15454 M6 subtending shelf that correspond to the TNC/TNCE/TSC/TSCE card.

g. Complete the DLP-G46 Log into CTC task at the subtending shelf.

h. Click the Provisioning > General > Multishelf Config tabs.

i. Click Enable as Subtended Shelf .

j. From the Shelf ID drop-down list, choose the shelf ID that you created in Step c .

k. Click Apply .

l. In the confirmation dialog box, click Yes to reboot the shelf. The CTC view changes to network view and the node icon changes to gray. Wait for the reboot to finish. (This might take several minutes.)

m. Disconnect your Windows PC or Solaris workstation NIC from the RJ-45 LAN (TCP/IP) port of the ONS 15454 subtending shelf TCC2/TCC2P/TCC3 card in Slot 11 or Slot 7, or from the EMS RJ-45 LAN (TCP/IP) on the ONS 15454 M6 subtending shelf that correspond to the TNC/TNCE/TSC/TSCE card.

n. Reconnect the cross-over (CAT-5) LAN cable (disconnected in Step e ) to the RJ-45 LAN (TCP/IP) port of the subtending shelf TCC2/TCC2P/TCC3 card in Slot 11 or Slot 7, or to the EMS RJ-45 LAN (TCP/IP) on the ONS 15454 M6 subtending shelf that correspond to the TNC/TNCE/TSC/TSCE card.

o. Repeat Steps a through n to set up additional subtending shelves.

Note To connect the subtending shelves to the node controller, refer to the applicable procedures in the Cisco CPT and Cisco ONS 15454 Hardware Installation Guide.

Note Non-LAN connected Multishelf nodes are not manageable from CTC unless SOCKS Proxy is enabled on the node.

Stop. You have completed this procedure.

NTP-G23 Create Users and Assign Security

Step 1 Complete the DLP-G46 Log into CTC task at the node where you need to create users. If you are already logged in, continue with Step 2.

Note You must log in as a Superuser to create additional users. The CISCO15 user provided with each ONS 15454 can be used to set up other ONS 15454 users. You can add up to 500 users to one ONS 15454.

Step 2 Complete the G54 Create a New User on a Single Node or the G55 Create a New User on Multiple Nodes as needed.

Note You must add the same user name and password to each node that a user will access.

Step 3 If you want to modify the security policy settings, including password aging and idle user timeout policies, complete the NTP-G88 Modify Users and Change Security procedure.

Stop . You have completed this procedure .

DLP-G54 Create a New User on a Single Node

Step 1 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > Security > Users tabs.

Step 2 In the Users window, click Create .

Step 3 In the Create User dialog box, enter the following:

• Name—Type the user name. The name must be a minimum of six and a maximum of 20 alphanumeric (a-z, A-Z, 0-9) characters. For Transaction Language One (TL1) compatibility, the user name must be 6 to 10 characters.
• Password—Type the user password. The password length, by default, is set to a minimum of six and a maximum of 20 characters. You can configure the default values in node view using the Provisioning > NE Defaults > Node > security > passwordComplexity tabs. The minimum length can be set to eight, ten or twelve characters, and the maximum length to 80 characters. The password must be a combination of alphanumeric (a-z, A-Z, 0-9) and special (+, #,%) characters, where at least two characters are not alphabetic and at least one character is a special character. For TL1 compatibility, the password must be six to ten characters.

Note The password must not contain the user name.

• Confirm Password—Type the password again to confirm it.
• Security Level—Choose a security level for the user: RETRIEVE , MAINTENANCE , PROVISIONING , or SUPERUSER .

Note Each security level has a different idle time. The idle time is the length of time that CTC can remain idle before the password must be reentered. The defaults are: Retrieve user = unlimited, Maintenance user = 60 minutes, Provisioning user = 30 minutes, and Superuser = 15 minutes. To change the idle times, see the NTP-G88 Modify Users and Change Security procedure.

Step 4 Click OK .

Step 5 Return to your originating procedure (NTP).

DLP-G55 Create a New User on Multiple Nodes

Note All nodes where you want to add users must be accessible in network view.

Step 1 From the View menu, choose Go to Network View .

Step 2 Click the Provisioning > Security > Users tabs.

Step 3 In the Users window, click Create .

Step 4 In the Create User dialog box, enter the following:

• Name—Type the user name. The name must be a minimum of six and a maximum of 20 alphanumeric (a-z, A-Z, 0-9) characters. For TL1 compatibility, the user name must be 6 to 10 characters.
• Password—Type the user password. The password length, by default, is set to a minimum of six and a maximum of 20 characters. You can configure the default values in node view through Provisioning > NE Defaults > Node > security > passwordComplexity. The minimum length can be set to eight, ten or twelve characters, and the maximum length to 80 characters. The password must be a combination of alphanumeric (a-z, A-Z, 0-9) and special (+, #,%) characters, where at least two characters are not alphabetic and at least one character is a special character. For TL1 compatibility, the password must be six to ten characters. The password must not contain the user name.
• Confirm Password—Type the password again to confirm it.
• Security Level—Choose a security level for the user: RETRIEVE , MAINTENANCE , PROVISIONING , or SUPERUSER .

Note Each security level has a different idle time. The idle time is the length of time that CTC can remain idle before it locks up and the password must be reentered. The defaults are: Retrieve user = unlimited, Maintenance user = 60 minutes, Provisioning user = 30 minutes, and Superuser = 15 minutes. To change the idle times, refer to the NTP-G88 Modify Users and Change Security procedure.

Step 5 In the Select Applicable Nodes area, deselect any nodes where you do not want to add the user (all network nodes are selected by default).

Step 6 Click OK .

Step 7 In the User Creation Results dialog box, verify that the user was added to all the nodes chosen in Step 5. If not, click OK and repeat Steps 2 through 6 . If the user was added to all nodes, click OK and continue with the next step.

Step 8 Return to your originating procedure (NTP).

NTP-G24 Set Up Name, Date, Time, and Contact Information

Step 1 Complete the DLP-G46 Log into CTC task for the node you will turn up. If you are already logged in, continue with Step 2.

Step 2 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > General > General tabs.

Step 3 In the Node Name/TID field, type a name for the node. For TL1 compliance, names must begin with an alpha character and have no more than 20 alphanumeric (a-z, A-Z, 0-9) characters.

Note To avoid errors when you import the Cisco Transport Planner configuration file using the G143 Import the Cisco Transport Planner NE Update Configuration File, the CTC node name and the Cisco Transport Planner site name should be the same (or at least easy to identify).

Step 4 (Optional) In the Contact field, type the name of the node contact person and the phone number, up to 255 characters.

Step 5 (Optional) In the Latitude field, enter the node latitude: N (north) or S (south), degrees, and minutes.

Step 6 (Optional) In the Longitude field, enter the node longitude: E (east) or W (west), degrees, and minutes.

Note The latitude and longitude values only indicate the geographical position of the nodes in the actual network and not the CTC node position.

Step 7 (Optional) In the Description field, type a description of the node. The description can be a maximum of 255 characters.

Step 8 (Optional) Check the Use NTP/SNTP Server check box if you want CTC to use a Network Time Protocol (NTP) or Simple Network Time Protocol (SNTP) server to set the date and time of the node. Using an NTP or SNTP server ensures that all ONS 15454 network nodes use the same date and time reference. The server synchronizes the node’s time after power outages or software upgrades.

a. If you check the Use NTP/SNTP Server check box, complete the following fields:

– Use NTP/SNTP Server—Type the IP address of the primary NTP/SNTP server connected to the ONS 15454 or of another ONS 15454/15600/15310-CL/15310-MA as GNE with NTP/SNTP enabled that is connected to the ONS 15454 ENE.

– Backup NTP/SNTP Server—Type the IP address of the secondary NTP/SNTP server connected to the ONS 15454 or of another ONS 15454/15600/15310-CL/15310-MA as GNE with NTP/SNTP enabled that is connected to the ONS 15454 ENE.

When the primary NTP/SNTP server fails or is not reachable, the node uses the secondary NTP/SNTP server to synchronize its date and time. If both the primary and secondary NTP/SNTP servers fail or are not reachable, an SNTP-FAIL alarm is raised. The node checks for the availability of the primary or secondary NTP/SNTP server at regular intervals until it can get the time from any one of the NTP/SNTP servers. After the node gets the time from any one server, it synchronizes its date and time with the server’s date and time and the SNTP-FAIL alarm is cleared. For each retry and resynchronization, the node checks the availability of the primary NTP/SNTP server first, followed by the secondary NTP/SNTP server. The node synchronizes its date and time every hour.

Note You will not be able to identify which NTP/SNTP server is being used for synchronization.

Note If you plan to check gateway network element (GNE) for the ONS 15454 SOCKS proxy server (see G56 Provision IP Settings), external ONS 15454 nodes must reference the gateway ONS 15454 for NTP/SNTP timing. For more information about the ONS 15454 gateway settings, refer to Chapter22, “Manage Network Connectivity”

b. If you do not check Use SNTP/NTP Server, complete the Date and Time fields. The ONS 15454 will use these fields for alarm dates and times. By default, CTC displays all alarms in the CTC computer time zone for consistency. To change the display to the node time zone, complete the DLP-G118 Display Alarms and Conditions Using Time Zone task.

• Date—Type the current date in the format m/d/yyyy, for example, September 24, 2002 is 9/24/2002.
• Time—Type the current time in the format hh:mm:ss, for example, 11:24:58. The ONS 15454 uses a 24-hour clock, so 10:00 PM is entered as 22:00:00.

Step 9 Click the Time Zone field and choose a city within your time zone from the drop-down list. The list displays the 80 World Time Zones from –11 through 0 (GMT) to +14. Continental United States time zones are GMT-05:00 (Eastern), GMT-06:00 (Central), GMT-07:00 (Mountain), and GMT-08:00 (Pacific).

Step 10 Check the Use Daylight Savings Time check box if the time zone that you chose uses Daylight Savings Time.

Note The Insert AIS-V on STS-1 SD-P and SD-P BER field are not used in DWDM networks.

Step 11 Click Apply .

Step 12 In the confirmation dialog box, click Yes .

Step 13 Review the node information. If you need to make corrections, repeat Steps 3 through 12 to enter the corrections. If the information is correct, continue with the G25 Set Battery Power Monitor Thresholds.

Stop . You have completed this procedure .

NTP-G25 Set Battery Power Monitor Thresholds

Note When the thresholds are crossed, the TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE card generates warning alarms in CTC. For ONS 15454 power specifications, see the Hardware Specifications.

Step 1 Complete the DLP-G46 Log into CTC task for the node that you will set up. If you are already logged in, continue with Step 2.

Step 2 In node view (single-shelf mode) or shelf view (multishelf mode), click the Provisioning > General > Power Monitor tabs.

Note In multishelf mode, power monitor thresholds must be provisioned separately for each shelf within the multishelf including the node controller and all subtending shelves.

Step 3 To change the extreme low battery voltage threshold in 0.5 VDC increments, choose a voltage from the ELWBATVGVdc drop-down list.

Step 4 To change the low battery voltage threshold in 0.5 VDC increments, choose a voltage from the LWBATVGVdc drop-down list.

Step 5 To change the high battery voltage threshold in 0.5 VDC increments, choose a voltage from the HIBATVGVdc drop-down list.

Step 6 To change the extreme high battery voltage threshold in 0.5 VDC increments, choose a voltage from the EHIBATVGVdc drop-down list.

Step 7 Click Apply.

Stop . You have completed this procedure .

NTP-G26 Set Up CTC Network Access

Step 1 Complete the DLP-G46 Log into CTC task. If you are already logged in, continue with Step 2.

Step 2 Complete the G56 Provision IP Settings to provision the ONS 15454 IP address, subnet mask, default router, DHCP server, IIOP listener port, and SOCKS proxy server settings.

Tip If you cannot log into the node, you can change its IP address, default router, and network mask by using the LCD on the ONS 15454 fan-tray assembly (unless LCD provisioning is suppressed). See the G57 Set the IP Address, Default Router, and Network Mask Using the LCD for instructions. However, you cannot use the LCD to provision any other network settings. In an ONS 15454 M2 shelf assembly, the LCD is on the fan-tray assembly. In an ONS 15454 M6 shelf assembly, the LCD is a separate unit installed above the external connection unit (ECU).

Note When accessing CTC from a machine running Windows XP operating system, CTC may sometimes fail to reconnect to a GNE when the GNE proxies for several ENE nodes (approximately 15 ENE nodes). This can happen when there is a side switch or when the LAN is enabled/disabled. This is due to the Windows XP operating system limiting the number of simultaneous TCP/IP connection attempts. As a workaround, close the existing CTC session and relaunch CTC on the GNE node. You can configure a designated socks server list on the CTC to mitigate the problem.

Step 3 If TCC2P/TCC3/TNC/TNCE/TSC/TSCE cards are installed and you want to turn on the ONS 15454 secure mode, which allows two IP addresses to be provisioned for the node, complete the G264 Enable Node Security Mode. Secure mode is not available if TCC2 cards are installed.

Step 4 If static routes are needed, complete the G58 Create a Static Route. For more information about static routes, refer to Chapter22, “Manage Network Connectivity”

Step 5 If the ONS 15454 is connected to a LAN or WAN that uses OSPF and you want to share routing information between the LAN or WAN and the ONS network, complete the G59 Set Up or Change Open Shortest Path First Protocol.

Step 6 If the ONS 15454 is connected to a LAN or WAN that uses RIP, complete the G60 Set Up or Change Routing Information Protocol.

Step 7 Complete the G439 Provision the Designated SOCKS Servers after the network is provisioned and one or more of the following conditions exist:

• SOCKS proxy is enabled.
• The ratio of ENEs to GNEs is greater than eight to one.
• Most ENEs do not have LAN connectivity.

Stop . You have completed this procedure .

DLP-G56 Provision IP Settings

Step 1 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > Network > General tabs.

Step 2 Complete the following information in the fields listed:

• IP Address—Type the IP address assigned to the ONS 15454 node.

Note If TCC2P/TCC3/TNC/TNCE/TSC/TSCE cards are installed, dual IP addressing is available using the secure mode. When secure mode is off (sometimes called repeater mode), the IP address entered in the IP Address field applies to the backplane LAN port (ONS 15454), EMS RJ-45 port or Craft port on the ECU (ONS 15454 M6), EMS RJ-45 port on the power module (ONS 15454 M2), and the TCC2P/TCC3/TNC/TNCE/TSC/TSCE TCP/IP (LAN) port. When secure mode is on, the IP Address field shows the address assigned to the TCC2P/TCC3/TNC/TNCE/TSC/TSCE TCP/IP (LAN) port and the Superuser can enable or disable display of the backplane IP address. See the G264 Enable Node Security Mode as needed. Refer to “Manage Network Connectivity,” for more information about secure mode.

• Net/Subnet Mask Length—Type the subnet mask length (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 nodes in the same subnet.
• MAC Address—(Display only) Displays the ONS 15454 IEEE 802 MAC address.

Note In secure mode, the front and back TCP/IP (LAN) ports are assigned different MAC addresses, and the backplane information can be hidden or revealed by a Superuser.

• Default Router—If the ONS 15454 is connected to a LAN, enter the IP address of the default router. The default router forwards packets to network devices that the ONS 15454 cannot directly access. This field is ignored if any of the following are true:

– The ONS 15454 is not connected to a LAN.

– The SOCKS proxy server is enabled and the ONS 15454 is provisioned as an end network element (ENE).

– OSPF is enabled on both the ONS 15454 and the LAN where the ONS 15454 is connected. (OSPF is provisioned in the G59 Set Up or Change Open Shortest Path First Protocol.)

• LCD IP Setting—Choose one of the following:

– Allow Configuration —Displays the node IP address on the LCD and allows users to change the IP settings using the LCD. This option enables the G57 Set the IP Address, Default Router, and Network Mask Using the LCD.

– Display Only —Displays the node IP address on the LCD but does not allow users to change the IP settings using the LCD.

– Suppress Display —Suppresses the node IP address display on the LCD.

• Suppress CTC IP Display—Check this check box if you want to prevent the node IP address from appearing in CTC to users with Provisioning, Maintenance, or Retrieve security levels. (The IP address suppression is not applied to users with Superuser security level.)

Note IP address suppression is not applied to users with Superuser security level. However, in secure mode the backplane IP address visibility can be restricted to only a locally connected Superuser viewing the routing table. In this case, the backplane IP address is not revealed to any user at any other NE, either on the routing table or in autonomous messages (such as the TL1 REPT DBCHG message, alarms, and performance monitoring [PM] reporting).

• IPv6 Configuration—Allows provisioning of IPv6 addresses. After you provision an IPv6 address, you can access the device using the IPv6 address. Configure these settings only if you want to enable IPv6 on the node. IPv6 cannot be configured using the LCD push buttons.

– Enable IPv6—Select this check box to assign an IPv6 address to the node. The IPv6 Address, Prefix Length, and IPv6 Default Router fields are enabled only if this check box is selected. The check box is disabled by default.

Note Enable SOCKS Proxy on Port check box is enabled when you enable IPv6 and can be disabled only when IPv6 is disabled.

Note By default, when IPv6 is enabled, the node processes both IPv4 and IPv6 packets on the LAN interface. If you want the node to process only IPv6 packets, you need to disable IPv4 on the node. For more information, see DLP-G317 Change Node Access and PM Clearing Privilege.

– IPv6 Address—Enter the IPv6 address that you want to assign to the node. This IP address is the global unicast IPv6 address. This field is disabled if the Enable IPv6 check box is not selected.

– Prefix Length—Enter the prefix length of the IPv6 address. This field is disabled if the Enable IPv6 check box is not selected.

– IPv6 Default Router—Enter the IPv6 address of the default router of the IPv6 NE. This is optional. This field is disabled if the Enable IPv6 check box is not selected.

Note The ONS 15454 DWDM uses NAT-PT internally to support native IPv6. NAT-PT uses the IPv4 address range 128.0.0.0 to 128.0.1.254 for packet translation. Do not use this address range when you enable IPv6 feature.

Note You can provision IPv6 in secure or nonsecure mode. To enable secure mode, see G264 Enable Node Security Mode.

• Forward DHCP Request To—Check this check box to enable DHCP. Also, enter the DHCP server IP address in the Request To field. Unchecked is the default. If you will enable any of the gateway settings to implement the ONS 15454 SOCKS proxy server features, do not check this check box.

Note If you enable DHCP, computers connected to an ONS 15454 node can obtain temporary IP addresses from an external DHCP server. The ONS 15454 only forwards DHCP requests; it does not act as a DHCP server.

• Gateway Settings—Provisions the ONS 15454 SOCKS proxy server features. (SOCKS is a standard proxy protocol for IP-based applications.) Do not change these options until you review Scenario 7 “Provisioning the ONS 15454 Proxy Server” in Chapter22, “Manage Network Connectivity” In SOCKS proxy server networks, the ONS 15454 is either an ENE, a GNE, or a proxy-only server. Provisioning must be consistent for each NE type.
• Enable SOCKS proxy server on port—If checked, the ONS 15454 serves as a proxy for connections between CTC clients and ONS 15454 nodes that are connected by data communications channels (DCCs) to the proxy ONS 15454. The CTC client establishes connections to DCC-connected nodes through the proxy node. The CTC client does not require IP connectivity to the DCC-connected nodes; it only requires IP connectivity to the proxy ONS 15454. If the Enable SOCKS proxy server on port check box is unchecked, the node does not proxy for any CTC clients. When this box is checked, you can provision one of the following options:

– External Network Element (ENE) —Choose this option when the ONS 15454 is not connected to a LAN but has DCC connections to other ONS nodes. A CTC computer connected to the ENE through the TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE card TCP/IP (craft) port can manage nodes that have DCC connections to the ENE. However, the CTC computer does not have direct IP connectivity to these nodes or to any LAN or WAN that those nodes might be connected to.

– Gateway Network Element (GNE) —Choose this option when the ONS 15454 is connected to a LAN and has DCC connections to other nodes. A CTC computer connected to the LAN can manage all nodes that have DCC connections to the GNE, but the CTC computer does not have direct IP connectivity to them. The GNE option isolates the LAN from the DCC network so that IP traffic originating from the DCC-connected nodes and any CTC computers connected to them is prevented from reaching the LAN.

– SOCKS proxy only —Choose this option when the ONS 15454 is connected to a LAN and the LAN is separated from the node by a firewall. The SOCKS proxy only option is the same as the GNE option, except that the SOCKS proxy only option does not isolate the DCC network from the LAN.

Note If a node is provisioned in secure mode, it is automatically provisioned as a GNE with SOCKS proxy enabled. However, this provisioning can be overridden, and the secure node can be changed to an ENE. In secure mode, SOCKS cannot be disabled. For information about provisioning, including GNE and ENE status, see the G264 Enable Node Security Mode.

Step 3 Click Apply .

Step 4 Click Yes in the confirmation dialog box.

The TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE cards reboot one at a time if changes were made to the IP address, subnet mask, or gateway settings. During this time (approximately 5 to 6 minutes), the active and standby TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE card LEDs will blink, turn on, and turn off at different intervals. Eventually, a “Lost node connection, switching to network view” message appears.

Step 5 Click OK . The network view appears. The node icon appears in gray, during which time you cannot access the node.

Step 6 Double-click the node icon when it becomes green.

Step 7 Return to your originating procedure (NTP).

DLP-G439 Provision the Designated SOCKS Servers

Note To complete this task, you must have either the IP addresses or DNS names of all ONS 15454s in the network with LAN access that have SOCKS proxy enabled.

Note SOCKS proxy servers can be any accessible ONS network nodes that have LAN access, including the ONS 15310-MA, ONS 15310-CL, ONS 15454, ONS 15454 SDH, ONS 15600, ONS 15600 SDH, ONS 15454 M6, and ONS 15454 M2 nodes.

Note You must repeat this task any time that changes to SOCKS proxy server nodes occur, for example, whenever LAN connectivity is added to or removed from a node, or when nodes are added or removed from the network.

Note If you cannot log into a network node, complete the DLP-G46 Log into CTC task choosing the Disable Network Discovery option. Complete this task, then login again with network discovery enabled.

Step 1 From the CTC Edit menu, choose Preferences .

Step 2 In the Preferences dialog box, click the SOCKS tab.

Step 3 In the Designated SOCKS Server field, type the IP address or DNS node name of the first ONS 15454 SOCKS server. The ONS 15454 that you enter must have SOCKS proxy server enabled, and it must have LAN access.

Step 4 Click Add . The node is added to the SOCKS server list. If you need to remove a node on the list, click Remove .

Step 5 Repeat Steps 3 and 4 to add all qualified ONS 15454s within the network. Add all ONS nodes that have SOCKS proxy enabled and are connected to the LAN.

Step 6 Click Check All Servers . CTC verifies that all nodes can perform as SOCKS servers. Once verified, a check is placed next to the node IP address or node name in the SOCKS server list. An X placed next to the node indicates one or more of the following:

• The entry does not correspond to a valid DNS name.
• The numeric IP address is invalid.
• The node cannot be reached.
• The node can be reached, but the SOCKS port cannot be accessed, for example, a firewall problem might exist.

Step 7 Click Apply . The list of ONS 15454 nodes, including ones that received an X in Step 6, are added as SOCKS servers.

Step 8 Click OK to close the Preferences dialog box.

Step 9 Return to your originating procedure (NTP).

DLP-G57 Set the IP Address, Default Router, and Network Mask Using the LCD

Note You cannot perform this task if the LCD IP Display field on the node view Provisioning > Network tab is set to Display Only or Suppress Display. See the G56 Provision IP Settings to view or change the LCD IP Display field. If the node is locked in secure mode with the LCD display disabled, you will not be able to change this provisioning unless the lock is disabled by Cisco Technical Support. Refer to “Manage Network Connectivity,” for more information about secure mode.

Note The LCD reverts to normal display mode after 5 seconds of button inactivity.

Step 1 On the ONS 15454 front panel, repeatedly press the Slot button until SHELF appears on the first line of the LCD. You are in the Shelf menu.

Note In an ONS 15454 M2 shelf assembly, the LCD panel and the Slot, Port, and Status buttons are present on the fan-tray assembly. In an ONS 15454 M6 shelf assembly, the LCD is a separate unit installed above the external connection unit (ECU); the Slot, Port, and Status buttons are present on the LCD unit.

Step 2 Repeatedly press the Port button until the following information appears:

• To change the node IP address, Node Status=IpAddress (Figure 14-1)
• To change the node network mask, Node Status=Net Mask
• To change the default router IP address, Node Status=Default Rtr

Figure 14-1 Selecting the IP Address Option—ONS 15454 Shelf Assembly

Step 3 Press the Status button to display the node IP address (Figure 14-2), the node subnet mask length, or the default router IP address.

Figure 14-2 Changing the IP Address—ONS 15454 Shelf Assembly

Step 4 Push the Slot button to move to the digit of the IP address, subnet mask, or default router that you want to change. The selected digit flashes.

Tip The Slot, Status, and Port button positions correspond to the positions of the commands shown on the LCD. For example, in Figure 14-2, you press the Slot button to invoke the Next command and the Status button to invoke the Done command.

Step 5 Press the Port button to cycle the IP address, subnet mask, or default router to the correct digit.

Step 6 When the change is complete, press the Status button to return to the relevant Node Status menu.

Step 7 Repeatedly press the Port button until the Shelf Save Configuration option appears (Figure 14-3).

Figure 14-3 Selecting the Save Configuration Option—ONS 15454 Shelf Assembly

Step 8 Press the Status button to choose the Save Configuration option.

A Save and REBOOT message appears (Figure 14-4).

Figure 14-4 Saving and Rebooting the TCC2/TCC2P/TCC3—ONS 15454 Shelf Assembly

Step 9 Press the Slot button to apply the new IP address, subnet mask, or default router configuration or press Port to cancel the configuration.

Note The IP address and default router must be on the same subnet. If not, you cannot apply the configuration.

Step 10 Saving the new configuration causes the TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE cards to reboot. During the reboot, a “TCC may Reset” message appears on the LCD. The LCD returns to the normal alternating display after both TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE cards finish rebooting.

Step 11 Return to your originating procedure (NTP).

DLP-G264 Enable Node Security Mode

Note The node will reboot after you complete this task, causing a temporary disconnection between the CTC computer and the node.

Note If an OTS-to-OTS PPC is created between nodes, it will no longer function if the node Security Mode is enabled (see G264 Enable Node Security Mode). The reason for this is that if the Secure mode is enabled, it is no longer possible for the DCN extension feature to use the LAN interface to extend the internal network (due to the network isolation in this configuration mode). The result is that the topology discovery on the OTS-to-OTS PPC no longer operates.

Step 1 Click the Provisioning > Security > Data Comm tabs.

Note The security mode options are not available in CTC if TCC2 cards or a mix of TCC2 and TCC2P cards are installed.

Step 2 Click Change Mode .

Step 3 Review the information on the Change Secure Mode page, then click Next .

Step 4 On the TCC Ethernet Port page, enter the IP address and subnet mask for the TCC2P/TCC3/TNC/TNCE/TSC/TSCE TCP/IP (LAN) port. The IP address cannot reside on the same subnet as the backplane LAN port (ONS 15454) and the EMS port (ONS 15454 M2 and M6).

Step 5 Click Next .

Step 6 If needed, on the Backplane Ethernet Port page, modify the backplane IP address, subnet mask, and default router. (You normally do not modify these fields if no network changes have occurred.)

Step 7 Click Next .

Step 8 On the SOCKS Proxy Server Settings page, choose one of the following options:

• External Network Element (ENE) —If selected, the CTC computer is only visible to the ONS 15454 where the CTC computer is connected. The CTC computer is not visible to the nodes connected to the DCC. In addition, firewall is enabled, which means that the node prevents IP traffic from being routed between the DCC and the LAN port.
• Gateway Network Element (GNE) —If selected, the CTC computer is visible to other DCC-connected nodes. The node prevents IP traffic from being routed between the DCC and the LAN port.

Note The SOCKS proxy server is automatically enabled when you enable secure mode.

Step 9 Click Finish .

Within the next 30 to 40 seconds, the TCC2P/TCC3/TNC/TNCE/TSC/TSCE cards reboot. CTC switches to network view, and the CTC Alerts dialog box appears. In network view, the node changes to gray and a DISCONNECTED condition appears in the Alarms tab.

Step 10 In the CTC Alerts dialog box, click Close . Wait for the reboot to finish. (This might take several minutes.)

Step 11 After the DISCONNECTED condition clears, complete the following steps to suppress the backplane IP address from appearing in CTC and the LCD. If you do not want to suppress the backplane IP address display, continue with Step 12.

a. Display the node in node view (single-shelf mode) or multishelf view (multishelf mode).

b. Click the Provisioning > Security > Data Comm tabs.

c. In the LCD IP Setting field, choose Suppress Display . The IP address will not appear on the ONS 15454 LCD.

d. Check the Suppress CTC IP Address check box. The IP address will not appear in the CTC information area or the Provisioning > Security > Data Comm tabs.

e. Click Apply .

Note After you turn on secure mode, the TCC2P/TCC3/TNC/TNCE/TSC/TSCE IP address becomes the node IP address.

Step 12 Return to your originating procedure (NTP).

DLP-G58 Create a Static Route

Step 1 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > Network tabs.

Step 2 Click the Static Routing tab. Click Create .

Step 3 In the Create Static Route dialog box, enter the following:

• Destination—Enter the IP address of the computer running CTC. To limit access to one computer, enter the full IP address and a subnet mask of 255.255.255.255. To allow access to all computers on the 192.168.1.0 subnet, enter 192.168.1.0 and a subnet mask of 255.255.255.0. You can enter a destination of 0.0.0.0 to allow access to all CTC computers that connect to the router.
• Mask—Enter a subnet mask. If the destination is a host route (that is, one CTC computer), enter a 32-bit subnet mask (255.255.255.255). If the destination is a subnet, adjust the subnet mask accordingly, for example, 255.255.255.0. If the destination is 0.0.0.0, CTC automatically enters a subnet mask of 0.0.0.0 to provide access to all CTC computers. You cannot change this value.
• Next Hop—Enter the IP address of the router port or the node IP address if the CTC computer is connected to the node directly.
• Cost—Enter the number of hops between the ONS 15454 and the computer.

Step 4 Click OK . Verify that the static route appears in the Static Route window.

Note Static route networking examples are provided in the Chapter22, “Manage Network Connectivity”

Step 5 Return to your originating procedure (NTP).

DLP-G59 Set Up or Change Open Shortest Path First Protocol

Step 1 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > Network > OSPF tabs.

Step 2 On the top left side of the OSPF area, complete the following:

• DCC/GCC OSPF Area ID Table—In dotted decimal format, enter the number that identifies the ONS 15454 nodes as a unique OSPF area ID. The Area ID can be any number between 000.000.000.000 and 255.255.255.255, but must be unique to the LAN OSPF area.

ANSI Nodes

• SDCC Metric—This value is normally unchanged. It sets a cost for sending packets across the Section DCC, which is used by OSPF routers to calculate the shortest path. This value should always be higher than the LAN metric. The default SDCC metric is 100.
• LDCC Metric—Sets a cost for sending packets across the Line DCC. This value should always be lower than the SDCC metric. The default LDCC metric is 33. It is usually not changed.

ETSI Nodes

• RS-DCC Metric—This value is normally unchanged. It sets a cost for sending packets across the regenerator section DCC (RS-DCC), which is used by OSPF routers to calculate the shortest path. This value should always be higher than the LAN metric. The default RS-DCC metric is 100.
• MS-DCC Metric—Sets a cost for sending packets across the multiplex section DCC (MS-DCC). This value should always be lower than the SDCC metric. The default MS-DCC metric is 33. It is usually not changed.

Step 3 In the OSPF on LAN area, complete the following:

• OSPF active on LAN—When checked, enables the ONS 15454 OSPF topology to be advertised to OSPF routers on the LAN. Enable this field on ONS 15454 nodes that directly connect to OSPF routers.
• LAN Port Area ID—Enter the OSPF area ID (dotted decimal format) for the router port where the ONS 15454 is connected. (This number is different from the DCC/GCC OSPF Area ID.)

Step 4 By default, OSPF is set to No Authentication. If the OSPF router requires authentication, complete the following steps. If not, continue with Step 5.

a. Click the No Authentication button.

b. In the Edit Authentication Key dialog box, complete the following:

• Type—Choose Simple Password .
• Enter Authentication Key—Enter the password.
• Confirm Authentication Key—Enter the same password to confirm it.

c. Click OK .

The authentication button label changes to Simple Password.

Step 5 Provision the OSPF priority and interval settings. The OSPF priority and interval defaults are the defaults most commonly used by OSPF routers. Verify that these defaults match the ones used by the OSPF router where the ONS 15454 is connected.

• Router Priority—Provision the router priority, which determines the designated router for a subnet.
• Hello Interval (sec)—Provision the number of seconds between OSPF hello packet advertisements sent by OSPF routers. Ten seconds is the default.
• Dead Interval—Provision the number of seconds that will pass while an OSPF router’s packets are not visible before its neighbors declare the router down. Forty seconds is the default.
• Transit Delay (sec)—Provision the service speed. One second is the default.
• Retransmit Interval (sec)—Provision the number of seconds that will elapse before a packet is resent. Five seconds is the default.
• LAN Metric—Provision the cost for sending packets across the LAN. This value should always be lower than the SDCC or RS-DCC metric. Ten is the default.

Step 6 Under OSPF Area Range Table, create an area range table if one is needed:

Note Area range tables consolidate the information that is outside an OSPF area border. One ONS 15454 in the ONS 15454 OSPF area is connected to the OSPF router. An area range table on this node points the router to the other nodes that reside within the ONS 15454 OSPF area.

a. Click Create .

b. In the Create Area Range dialog box, enter the following:

• Range Address—Enter the area IP address for the ONS 15454 nodes that reside within the OSPF area. For example, if the ONS 15454 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 ONS 15454 nodes. This is either the ID in the DCC OSPF Area ID field or the ID in the Area ID for LAN Port field.
• Mask Length—Enter the subnet mask length. In the Range Address example, this is 16.
• Advertise—Check this box if you want to advertise the OSPF range table.

c. Click OK .

Step 7 All OSPF areas must be connected to Area 0. If the ONS 15454 OSPF area is not physically connected to Area 0, use the following steps to create a virtual link table that will provide the disconnected area with a logical path to Area 0:

a. Under the OSPF Virtual Link Table, click Create .

b. In the Create Virtual Link dialog box, complete the following fields. OSPF settings must match OSPF settings for the ONS 15454 OSPF area:

• Neighbor—Enter the router ID of the Area 0 router.
• Transit Delay (sec)—Enter the service speed. One second is the default.
• Hello Int (sec)—Provision the number of seconds between OSPF hello packet advertisements sent by OSPF routers. Ten seconds is the default.
• Auth Type—If the router where the ONS 15454 is connected uses authentication, choose Simple Password . Otherwise, choose No Authentication .
• Retransmit Int (sec)—Provision the time that will elapse, in seconds, before a packet is resent. Five seconds is the default.
• Dead Int (sec)—Provision the number of seconds that will pass while an OSPF router’s packets are not visible before its neighbors declare the router down. Forty seconds is the default.

c. Click OK .

Step 8 After entering the ONS 15454 OSPF area data, click Apply .

If you changed the Area ID, the TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE cards reset, one at a time. The reset takes approximately 10 to 15 minutes.

Step 9 Return to your originating procedure (NTP).

DLP-G60 Set Up or Change Routing Information Protocol

Step 1 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > Network > RIP tabs.

Step 2 Check the RIP Active check box if you are activating RIP.

Step 3 Choose either RIP Version 1 or RIP Version 2 from the drop-down list, depending on which version is supported in your network.

Step 4 Set the RIP metric. The RIP metric can be set to a number between 1 and 15 and represents the number of hops.

Step 5 By default, RIP is set to No Authentication. If the router that the ONS 15454 is connected to requires authentication, complete the following steps. If not, continue with Step 6.

a. Click the No Authentication button.

b. In the Edit Authentication Key dialog box, complete the following:

• Type—Choose Simple Password .
• Enter Authentication Key—Enter the password.
• Confirm Authentication Key—Enter the same password to confirm it.

c. Click OK .

The authentication button label changes to Simple Password.

Step 6 If you want to complete an address summary, complete the following steps. If not, continue with Step 7. Complete the address summary only if the ONS 15454 is a gateway NE with multiple external ONS 15454 NEs attached with IP addresses in different subnets.

a. In the RIP Address Summary area, click Create .

b. In the Create Address Summary dialog box, complete the following:

• Summary Address—Enter the summary IP address.
• Mask Length—Enter the subnet mask length using the up and down arrows.
• Hops—Enter the number of hops. The smaller the number of hops, the higher the priority.

c. Click OK .

Step 7 Return to your originating procedure (NTP).

NTP-G194 Set Up EMS Secure Access to the ONS 15454

Step 1 In node view, click the Provisioning > Security > Access pane.

Step 2 Under the EMS Access area, change the Access State to Secure.

Step 3 Click Apply. The CTC disconnects and reconnects through a secure socket connection.

Step 4 To create a secure connection, enter https://node-address.

Note After setting up a CTC connection in secure mode, http requests are automatically redirected to https mode.

Step 5 A first time connection is authenticated by the Website Certification is Not Known dialog box. Accept the certificate and click OK. The Security Error: Domain Name Mismatch dialog box appears. Click OK to continue.

Stop. You have completed this procedure.

NTP-G341 Set Up Secure Access to the ONS 15454 TL1

Step 1 In the node view, click the Provisioning > Security > Access pane.

Step 2 Under the TL1 Access area, change the Access State to Secure.

Step 3 Click Apply.

Existing non-secure TL1 sessions, if any, are terminated.

Step 4 To create a secure TL1 connection, enter the following command at the UNIX or Linux prompt:

ssh -l username node-ip -p port-number

The port number for secure TL1 is 4083.

Note Use any SSH client on Windows.

Stop. You have completed this procedure.

NTP-G27 Set Up the ONS 15454 for Firewall Access

Step 1 Log into a node that is behind the firewall. See the DLP-G46 Log into CTC task for instructions. If you are already logged in, continue with Step 2.

Step 2 If the ONS 15454 node is in a protected network and the CTC computer is in an external network, complete the G61 Provision the IIOP Listener Port on the ONS 15454.

Figure 14-5 shows ONS 15454 nodes in a protected network and the CTC computer in an external network. For the computer to access the ONS 15454 nodes, you must provision the IIOP listener port specified by your firewall administrator on the ONS 15454.

Figure 14-5 Nodes Behind a Firewall

Step 3 If the CTC computer resides behind a firewall, complete the G62 Provision the IIOP Listener Port on the CTC Computer.

Figure 14-6 shows a CTC computer and ONS 15454 behind firewalls. For the computer to access the ONS 15454, you must provision the IIOP port on the CTC computer and on the ONS 15454.

Figure 14-6 CTC Computer and ONS 15454 Nodes Residing Behind Firewalls

Stop . You have completed this procedure .

NTP-G28 Create FTP Host

Step 1 Complete the DLP-G46 Log into CTC task. If you are already logged in, continue with Step 2.

Step 2 If you want to turn on the ONS 15454 secure mode, which allows two IPv4 addresses to be provisioned for the node if TCC2P/TCC3/TNC/TNCE/TSC/TSCE cards are installed, complete the G264 Enable Node Security Mode. Refer to the “Manage Network Connectivity,” for information about secure mode.

Step 3 In Node view, click the Provisioning > Network > FTP Hosts tabs.

Step 4 Click Create.

Step 5 Enter a valid IP address in the FTP Host Address field. A maximum of 12 host can be entered.

Note In ONS 15454 Software Release 9.1 and later, you can configure an IPv6 address for an FTP server, in addition to an IPv4 address.

Step 6 The Mask is automatically set according to the Net/Subnet Mask length specified in “G56 Provision IP Settings” section. To change the Mask, click the Up/Down arrows on the Length menu.

Step 7 Check the FTP Relay Enable radio button to allow FTP commands at the GNE relay. If you will enable the relay at a later time, go to Step 9. Certain TL1 commands executed on an ENE require FTP access into the Data Communication Network (DCN), the FTP relay on the GNE provides this access. The FTP hosts that you have configured in CTC can be used with the TL1 COPY-RFILE (for database backup and restore or software download) or COPY-IOSCFG (for Cisco IOS Configuration File backup and restore) commands.

Step 8 Enter the time, in minutes, that FTP Relay will be enabled. A valid entry is a number between 0 and 60. The number 0 disallows FTP command relay. After the specified time has elapsed the FTP Relay Enable flag is unset and FTP command relay is disallowed.

Step 9 Click OK.

Step 10 Repeat Step 4 through Step 9 to provision additional FTP Hosts.

Stop . You have completed this procedure .

DLP-G61 Provision the IIOP Listener Port on the ONS 15454

Note If the Enable SOCKS proxy on port 1080 check box is checked, CTC will use Port 1080 and ignore the configured IIOP port setting. If the check box is later unchecked, the configured IIOP listener port will be used.

Step 1 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > Security > Access tabs.

Step 2 In the TCC CORBA (IIOP) Listener Port area, choose a listener port option:

• Default - TCC Fixed —Uses Port 57790 to connect to ONS 15454 nodes on the same side of the firewall or if no firewall is used (default). This option can be used for access through a firewall if Port 57790 is available.
• Standard Constant —Uses Port 683, the Common Object Request Broker Architecture (CORBA) default port number.
• Other Constant —If Port 683 is not used, type the IIOP port specified by your firewall administrator.

Step 3 Click Apply .

Step 4 When the Change Network Configuration message appears, click Yes .

The TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE cards reboot, one at a time. The reboot takes approximately 15 minutes.

Step 5 Return to your originating procedure (NTP).

DLP-G62 Provision the IIOP Listener Port on the CTC Computer

Step 1 From the Edit menu, choose Preferences .

Step 2 In the Preferences dialog box, click the Firewall tab.

Step 3 In the CTC CORBA (IIOP) Listener Port area, choose a listener port option:

• Default - Variable —Use to connect to ONS 15454 nodes from within a firewall or if no firewall is used (default).
• Standard Constant —Use Port 683, the CORBA default port number.
• Other Constant —If Port 683 is not used, enter the IIOP port defined by your administrator.

Step 4 Click Apply . A warning appears telling you that the port change will apply during the next CTC login.

Step 5 Click OK .

Step 6 In the Preferences dialog box, click OK .

Step 7 To access the ONS 15454 using the IIOP port, log out of CTC then log back in. (To log out, choose Exit from the File menu).

Step 8 Return to your originating procedure (NTP).

NTP-G132 Provision OSI

Note This procedure requires provisioning of non-ONS equipment including routers and third party NEs. Do not begin until you have the capability to complete that provisioning.

Step 1 Complete the DLP-G46 Log into CTC task at the node where you want to provision the OSI. If you are already logged in, continue with Step 2.

Step 2 As needed, complete the following tasks:

• G283 Provision OSI Routing Mode—Complete this task first.
• G284 Provision the TARP Operating Parameters—Complete this task second.
• G285 Add a Static TID-to-NSAP Entry to the TARP Data Cache—Complete this task as needed.
• G287 Add a TARP Manual Adjacency Table Entry—Complete this task as needed.
• G288 Provision OSI Routers—Complete this task as needed.
• G289 Provision Additional Manual Area Addresses—Complete this task as needed.
• G290 Enable the OSI Subnet on the LAN Interface—Complete this task as needed.
• G291 Create an IP-Over-CLNS Tunnel—Complete this task as needed.

Stop. You have completed this procedure.

DLP-G283 Provision OSI Routing Mode

Note For ONS 15454 nodes, three virtual routers can be provisioned. The node primary Network Service Access Point (NSAP) address is also the Router 1 primary manual area address. To edit the primary NSAP, you must edit the Router 1 primary manual area address. After you enable Router 1 on the Routers subtab, the Change Primary Area Address button is available to edit the address.

Step 1 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > OSI tabs.

Step 2 Choose a routing mode:

• End System —The ONS 15454 performs OSI end system (ES) functions and relies upon an intermediate system (IS) for communication with nodes that reside within its OSI area.

Note The End System routing mode is not available if more than one virtual router is enabled.

• I ntermediate System Level 1 —The ONS 15454 performs OSI IS functions. It communicates with IS and ES nodes that reside within its OSI area. It depends upon an IS L1/L2 node to communicate with IS and ES nodes that reside outside its OSI area.
• Intermediate System Level 1/Level 2 —The ONS 15454 performs IS functions. It communicates with IS and ES nodes that reside within its OSI area. It also communicates with IS L1/L2 nodes that reside in other OSI areas. Before choosing this option, verify the following:

– The node is connected to another IS Level 1/Level 2 node that resides in a different OSI area.

– The node is connected to all nodes within its area that are provisioned as IS L1/L2.

Step 3 If needed, change the LSP data buffers:

• L1 LSP Buffer Size—Adjusts the Level 1 link state protocol data unit (PDU) buffer size. The default is 512. It should not be changed.
• L2 LSP Buffer Size—Adjusts the Level 2 link state PDU buffer size. The default is 512. It should not be changed.

Step 4 Return to your originating procedure (NTP).

DLP-G284 Provision the TARP Operating Parameters

Step 1 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > OSI > TARP > Config tabs.

Step 2 Provision the following parameters, as needed:

• TARP PDUs L1 Propagation—If checked (default), TARP Type 1 PDUs that are received by the node and are not excluded by the LDB are propagated to other NEs within the Level 1 OSI area. (Type 1 PDUs request a protocol address that matches a target identifier [TID] within a Level 1 routing area.) The propagation does not occur if the NE is the target of the Type 1 PDU, and PDUs are not propagated to the NE from which the PDU was received.

Note The TARP PDUs L1 Propagation parameter is not used when the Node Routing Area (on the Provisioning > OSI > Main Setup tab) is set to End System.

• TARP PDUs L2 Propagation—If checked (default), TARP Type 2 PDUs that are received by the node and are not excluded by the LDB are propagated to other NEs within the Level 2 OSI areas. (Type 2 PDUs request a protocol address that matches a TID within a Level 2 routing area.) The propagation occurs if the NE is not the target of the Type 2 PDU, and PDUs are not propagated to the NE from which the PDU was received.

Note The TARP PDUs L2 Propagation parameter is only used when the Node Routing Area is provisioned to Intermediate System Level 1/Level 2.

• TARP PDUs Origination—If checked (default), the node performs all TARP origination functions including:

– TID-to-NSAP resolution requests (originate TARP Type 1 and Type 2 PDUs)

– NSAP-to-TID requests (originate Type 5 PDUs)

– TARP address changes (originate Type 4 PDUs)

Note TARP Echo and NSAP to TID are not supported.

• TARP Data Cache—If checked (default), the node maintains a TARP data cache (TDC). The TDC is a database of TID-to-NSAP pairs created from TARP Type 3 PDUs received by the node and modified by TARP Type 4 PDUs (TID-to-NSAP updates or corrections). TARP 3 PDUs are responses to Type 1 and Type 2 PDUs. The TDC can also be populated with static entries entered on the TARP > Static TDC tab.

Note TARP Data Cache is only used when the TARP PDUs Origination parameter is enabled.

• L2 TARP Data Cache—If checked (default), the TIDs and NSAPs of NEs originating Type 2 requests are added to the TDC before the node propagates the requests to other NEs.

Note The L2 TARP Data Cache parameter is designed for Intermediate System Level 1/Level 2 nodes that are connected to other Intermediate System Level 1/Level 2 nodes. Enabling the parameter for Intermediate System Level 1 nodes is not recommended.

• LDB—If checked (default), enables the TARP loop detection buffer. The LDB prevents TARP PDUs from being sent more than once on the same subnet.

Note The LDB parameter is not used if the Node Routing Mode is provisioned to End System or if the TARP PDUs L1 Propagation parameter is not enabled.

• LAN TARP Storm Suppression—If checked (default), enables TARP storm suppression. This function prevents redundant TARP PDUs from being unnecessarily propagated across the LAN network.
• Send Type 4 PDU on Startup—If checked, a TARP Type 4 PDU is originated during the initial ONS 15454 startup. Type 4 PDUs indicate that a TID or NSAP change has occurred at the NE. (The default setting is not enabled.)
• Type 4 PDU Delay—Sets the amount of time that will pass before the Type 4 PDU is generated when Send Type 4 PDU on Startup is enabled. 60 seconds is the default. The range is 0 to 255 seconds.

Note The Send Type 4 PDU on Startup and Type 4 PDU Delay parameters are not used if TARP PDUs Origination is not enabled.

• LDB Entry—Sets the TARP loop detection buffer timer. The loop detection buffer time is assigned to each LDB entry for which the TARP sequence number (tar-seq) is zero. The default is 5 minutes. The range is 1 to 10 minutes.
• LDB Flush—Sets the frequency period for flushing the LDB. The default is 5 minutes. The range is 0 to 1440 minutes.
• T1—Sets the amount of time to wait for a response to a Type 1 PDU. Type 1 PDUs seek a specific NE TID within an OSI Level 1 area. The default is 15 seconds. The range is 0 to 3600 seconds.
• T2—Sets the amount of time to wait for a response to a Type 2 PDU. TARP Type 2 PDUs seek a specific NE TID value within OSI Level 1 and Level 2 areas. The default is 25 seconds. The range is 0 to 3600 seconds.
• T3—Sets the amount of time to wait for an address resolution request. The default is 40 seconds. The range is 0 to 3600 seconds.
• T4—Sets the amount of time to wait for an error recovery. This timer begins after the T2 timer expires without finding the requested NE TID. The default is 20 seconds. The range is 0 to 3600 seconds.

Note The T1, T2, and T4 timers are not used if the TARP PDUs Origination check box is not checked.

Step 3 Click Apply .

Step 4 Return to your originating procedure (NTP).

DLP-G285 Add a Static TID-to-NSAP Entry to the TARP Data Cache

Step 1 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > OSI > TARP > Static TDC tabs.

Step 2 Click Add Static Entry .

Step 3 In the Add Static Entry dialog box, enter the following:

• TID—Enter the TID of the NE. (For ONS nodes, the TID is the Node Name parameter on the node or multishelf view Provisioning > General tab.)
• NSAP—Enter the OSI NSAP address in the NSAP field or, if preferred, click Use Mask and enter the address in the Masked NSAP Entry dialog box.

Step 4 Click OK to close the Masked NSAP Entry dialog box, if used, and then click OK to close the Add Static Entry dialog box.

Step 5 Return to your originating procedure (NTP).

DLP-G287 Add a TARP Manual Adjacency Table Entry

Step 1 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > OSI > TARP > MAT tabs.

Step 2 Click Add .

Step 3 In the Add TARP Manual Adjacency Table Entry dialog box, enter the following:

• Level—Sets the TARP Type Code that will be sent:

– Level 1 —Indicates that the adjacency is within the same area as the current node. The entry generates Type 1 PDUs.

– Level 2 —Indicates that the adjacency is in a different area than the current node. The entry generates Type 2 PDUs.

• NSAP—Enter the OSI NSAP address in the NSAP field or, if preferred, click Use Mask and enter the address in the Masked NSAP Entry dialog box.

Step 4 Click OK to close the Masked NSAP Entry dialog box, if used, and then click OK to close the Add Static Entry dialog box.

Step 5 Return to your originating procedure (NTP).

DLP-G288 Provision OSI Routers

Note Router 1 must be enabled before you can enable and edit the primary manual area addresses for Routers 2 and 3.

Note The Router 1 manual area address, System ID, and Selector “00” create the node NSAP address. Changing the Router 1 manual area address changes the node NSAP address.

Note The System ID for Router 1 is the node MAC address. The System IDs for Routers 2 and 3 are created by adding 1 and 2 respectively to the Router 1 System ID. You cannot edit the System IDs.

Step 1 Click the Provisioning > OSI > Routers > Setup tabs.

Step 2 Chose the router you want provision and click Edit . The OSI Router Editor dialog box appears.

Step 3 In the OSI Router Editor dialog box:

a. Check Enable Router to enable the router and make its primary area address available for editing.

b. Click the manual area address, then click Edit .

c. In the Edit Manual Area Address dialog box, edit the primary area address in the Area Address field. If you prefer, click Use Mask and enter the edits in the Masked NSAP Entry dialog box. The address (hexadecimal format) can be 8 to 24 alphanumeric characters (0–9, a–f) in length.

d. Click OK successively to close the following dialog boxes: Masked NSAP Entry (if used), Edit Manual Area Address, and OSI Router Editor.

Step 4 Return to your originating procedure (NTP).

DLP-G289 Provision Additional Manual Area Addresses

Step 1 Click the Provisioning > OSI > Routers > Setup tabs.

Step 2 Chose the router where you want provision an additional manual area address and click Edit . The OSI Router Editor dialog box appears.

Step 3 In the OSI Router Editor dialog box:

a. Check Enable Router to enable the router and make its primary area address available for editing.

b. Click the manual area address, then click Add .

c. In the Add Manual Area Address dialog box, enter the primary area address in the Area Address field. If you prefer, click Use Mask and enter the address in the Masked NSAP Entry dialog box. The address (hexadecimal format) can be 2 to 24 alphanumeric characters (0–9, a–f) in length.

d. Click OK successively to close the following dialog boxes: Masked NSAP Entry (if used), Add Manual Area Address, and OSI Router Editor.

Step 4 Return to your originating procedure (NTP).

DLP-G290 Enable the OSI Subnet on the LAN Interface

Note When you create communication channels (optical service channel [OSC] or generic communications channel [GCC]), OSI subnetwork points of attachment are enabled on the communication channels. See the G38 Provision OSC Terminations and the G76 Provision DCC/GCC Terminations.

Note The OSI subnetwork point of attachment cannot be enabled for the LAN interface if the OSI routing mode is set to ES.

Note If secure mode is on, the OSI subnet is enabled on the backplane LAN port, not the front TCC2P/TCC3/TNC/TNCE/TSC/TSCE TCP/IP (LAN) port.

Step 1 Click the Provisioning > OSI > Routers > Subnet tabs.

Step 2 Click Enable LAN Subnet .

Step 3 In the Enable LAN Subnet dialog box, complete the following fields:

• ESH—Sets the End System Hello (ESH) propagation frequency. An ES NE transmits ESHs to inform other ESs and ISs about the NSAPs it serves. The default is 10 seconds. The range is 10 to 1000 seconds.
• ISH—Sets the Intermediate System Hello (ISH) PDU propagation frequency. An intermediate system NE sends ISHs to other ESs and ISs to inform them about the IS NEs it serves. The default is 10 seconds. The range is 10 to 1000 seconds.
• IIH—Sets the Intermediate System to Intermediate System Hello (IIH) PDU propagation frequency. The IS-IS Hello PDUs establish and maintain adjacencies between ISs. The default is 3 seconds. The range is 1 to 600 seconds.
• IS-IS Cost—Sets the cost for sending packets on the LAN subnet. The IS-IS protocol uses the cost to calculate the shortest routing path. The default IS-IS cost for LAN subnets is 20. It normally should not be changed.
• DIS Priority—Sets the designated intermediate system (DIS) priority. In IS-IS networks, one router is elected to serve as the DIS (LAN subnets only). Cisco router DIS priority is 64. For the ONS 15454 LAN subnet, the default DIS priority is 63. It normally should not be changed.

Step 4 Click OK .

Step 5 Return to your originating procedure (NTP).

DLP-G291 Create an IP-Over-CLNS Tunnel

Step 1 Click the Provisioning > OSI > Tunnels tabs.

Step 2 Click Create .

Step 3 In the Create IP Over CLNS Tunnel dialog box, complete the following fields:

• Tunnel Type—Choose a tunnel type:

– Cisco —Creates the proprietary Cisco IP tunnel. Cisco IP tunnels add the CLNS header to the IP packets.

– GRE —Creates a generic routing encapsulation (GRE) tunnel. GRE tunnels add the CLNS header and a GRE header to the IP packets.

The Cisco proprietary tunnel is slightly more efficient than the GRE tunnel because it does not add the GRE header to each IP packet. The two tunnel types are not compatible. Most Cisco routers support the Cisco IP tunnel, while only a few support both GRE and Cisco IP tunnels. You generally should create Cisco IP tunnels if you are tunneling between two Cisco routers or between a Cisco router and an ONS node.

• IP Address—Enter the IP address of the IP-over-CLNS tunnel destination.
• IP Mask—Enter the IP address subnet mask of the IP-over-CLNS destination.
• OSPF Metric—Enter the OSPF metric for sending packets across the IP-over-CLNS tunnel. The OSPF metric, or cost, is used by OSPF routers to calculate the shortest path. The default is 110. Normally, it is not be changed unless you are creating multiple tunnel routes and want to prioritize routing by assigning different metrics.
• NSAP Address—Enter the destination NE or OSI router NSAP address.

Step 4 Click OK .

Step 5 Provision the other tunnel endpoint using the documentation provided by the manufacturer of the third party vendor NE.

Step 6 Return to your originating procedure (NTP).

NTP-G29 Set Up SNMP

Step 1 Complete the DLP-G46 Log into CTC task at the node where you want to set up SNMP. If you are already logged in, continue with Step 2.

Step 2 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > SNMP tabs.

Step 3 In the Trap Destinations area, click Create .

Step 4 Complete the following in the Create SNMP Trap Destination dialog box (Figure 14-7):

• Destination IP Address—Type the IP address of your network management system (NMS). If the node you are logged into is an ENE, set the destination address to the GNE.

Note In ONS 15454 Software Release 9.1 and later, you can configure IPv6 addresses for SNMPv2/v3 trap destinations and SNMPv3 proxy targets, in addition to IPv4 addresses.

• Community—Type the SNMP community name. For a description of SNMP community names, refer to the SNMP document.

Note The community name is a form of authentication and access control. The community name assigned to the ONS 15454 is case-sensitive and must match the community name of the NMS.

• UDP Port—The default User Datagram Protocol (UDP) port for SNMP is 162.
• Trap version—Choose either SNMPv1 or SNMPv2. Refer to your NMS documentation to determine which version to use.

Figure 14-7 Creating an SNMP Trap

Step 5 Click OK . The node IP address of the node where you provisioned the new trap destination appears in the Trap Destinations area.

Step 6 Click the node IP address in the Trap Destinations area. Verify the SNMP information that appears in the Selected Destination list.

Step 7 If you want the SNMP agent to accept SNMP SET requests on certain MIBs, click the Allow SNMP Sets check box. If this box is not checked, SET requests are rejected.

Step 8 If you want to set up the SNMP proxy feature to allow network management, message reporting, and performance statistic retrieval across ONS firewalls, click the Allow SNMP Proxy check box located on the SNMP tab.

Note The Use Generic MIB check box is normally not checked for MSTP. It is checked only when the ONS 15454 resides in networks with multiple ONS products, and the network management system requires MIBs with the same name to have the same object IDs. By default, the ONS 15454 uses the CERENT-454-MIBs. Other ONS products, such as the ONS 15600, the ONS 15327, and ONS 15310-CL, use the CERENT-GENERIC-MIBs. If Use Generic MIB is checked, the ONS 15454 will use the CERENT-GENERIC-MIBs so the object IDs will be the same for all products.

Note Using the ONS firewall proxy feature effectively breaches the ONS firewall to exchange management information.

For more information about the SNMP proxy feature, refer to SNMP .

Step 9 Click Apply.

Step 10 If you are setting up SNMP proxies, you can set up to three relays that send SNMP trap error counts back to the NE for each trap destination address:

a. Click the first trap destination IP address. The address and its community name appear in the Destination fields.

b. Enter up to three SNMP Proxy relay addresses and community names in the fields for Relay A, Relay B, and Relay C.

Note The community names specified for each relay node must match one of the provisioned SNMP community names in the NE.

Note The SNMP proxy directs SNMP traps from this node through Relay A to Relay B to Relay C to the trap destination. Ensure that you enter the IP addresses in the correct order so that this sequence runs correctly.

Step 11 Click Apply.

Stop . You have completed this procedure .

NTP-G143 Import the Cisco Transport Planner NE Update Configuration File

Note The Cisco Transport Planner configuration file contains parameters for the node, shelf, card type, port (including the card’s wavelength), pluggable port module (PPM), as well as OTN and FEC parameters. Only the values present in XML format appear in the configuration file parameters; if the values are not in XML format, a column appears blank. The XML file values are independently reported and do not affect any configuration changes that you apply.

Step 1 Complete the DLP-G46 Log into CTC task at the node where you want to import the Cisco Transport Planner configuration file. If you are already logged in, continue with Step 2.

Step 2 If you choose the Provision Node Layout option to preprovision the cards in the shelf, complete the following steps. If not, continue with Step 3.

a. Display the node in node view (single-shelf mode) or multishelf view (multishelf mode).

b. Verify that the common control cards (TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE, AIC-I and MSC-ISC) cards are the only cards installed. If in single or multishelf mode, verify that each shelf in the multishelf has two TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE cards.

• If common control cards are the only cards installed, continue with Step 3.
• If other cards appear, continue with Step c .

c. If a physical card other than the common control cards is installed, remove it from the shelf.

d. If preprovisioned DWDM cards are present, delete them using the G351 Delete a Card in CTC, then repeat Steps a and b .

Step 3 If you have not created a log file to record the results of the NE update, complete the following steps. If a log file has been created, continue with Step 4.

a. Open a text editor or word processing application.

b. Create a new text (TXT) document with a file name of your choosing.

c. Save the text document in a directory that is easy to navigate to from CTC.

Step 4 In CTC node view (single-shelf mode) or multishelf view, click the Provisioning > WDM-ANS > Node Setup tabs.

Step 5 Choose Load latest installation file from node to reload the latest XML file that was applied and stored in the node. Continue with Step 8.

Step 6 Choose Load installation file from network repository and navigate to the Cisco Transport Planner node setup file containing the parameters for the network where the node resides. This option downloads the XML file from the remote server. Continue with Step 8.

Step 7 In the field under Select XML file, type the path to the Cisco Transport Planner node setup file containing the parameters for the network where your node resides, or click Browse and navigate to the file on your computer. Click the file, then click Open. The file will have an XML extension. Continue with Step 8.

Step 8 In the field under Select Log file, type the path to the text file that you created in Step 3, or click Browse and navigate to the file on your computer or a network server where you want the node setup results recorded.

Note The log file records the parameters that were updated successfully and provides an explanation of why an update could not be completed. Each node setup session overwrites the log file contents. If you want to save the results from a previous NE update, save the log file with new name.

Step 9 Click Apply .

Step 10 When Load installation file from network repository option is chosen, the FTP Remote Installation File Node-Name page appears.

a. When the node is configured as a Gateway Network Element (GNE) node, enter the parameters (host name, port, user name, password, remote directory, and XML file name of the remote server) and click Next.

b. When the node is configured as a Elementary Network Element (ENE) node, an additional parameter called GNE Selector appear. From the GNE Selector drop-down list, select the appropriate GNE in the network. The FTP relay must be configured on the selected GNE to the remote server where the XML file is stored. See G28 Create FTP Host to configure the FTP relay on the selected GNE.

Step 11 When the Node Setup Selection for Node-Name page appears, complete the following steps. If not, continue with Step 12.

a. Choose the node profile that you want to apply to the node. The Cisco Transport Planner XML file contains profiles for all nodes in the network. Choose the profile that applies to the node you are provisioning.

b. Click Next .

Step 12 On the Node Setup for node name page, choose one or more of the following:

• Node Layout—Preprovisions the slots in each shelf in CTC for the cards defined in the network plan. Choose this option when no DWDM cards are installed. (Errors will occur if cards are installed or the slots are preprovisioned.) Preprovisioning the slots before the physical cards are installed ensures that card installers place the cards in the correct slots. Preprovisioning the slots is also useful if you want to set up the network prior to card installation. The node layout also preprovisions the chassis and passive units.
• Card Parameters—If checked, provisions the following parameters, if the cards are installed.

– TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, ADM-10G, and OTU2_XP cards—Provisions the OTN and FEC parameters.

– OPT-AMP-L, OPT-AMP-17-C, OPT-AMP-C, OPT-EDFA-17, OPT-EDFA-24, GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards—Provisions the card mode.

• Pluggable Port Modules— If checked, allows the provisioning of PPMs on TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, ADM-10G, and OTU2_XP cards, including PPM payloads.
• Internal Patchcords—If checked, allows creation of internal patchcords among cards provisioned in the node.
• Optical Sides—If checked, allows the provisioning of optical sides.
• ANS Parameters—If checked, installs the ANS parameters. ANS parameters provision the values required for the node to function within the specified network design. ANS parameters include span losses, optical power, optics thresholds, amplifier working mode, gain, tilt, and many others. Refer to Chapter 12, “Node Reference” for a list of ONS 15454 ANS parameters.

Note If you are importing the Cisco Transport Planner configuration file for the first time, you normally choose all available options.

• Skip Interactive Mode—If checked, CTC provisions all the chosen setup components automatically without allowing you to view the results after each one.
• Save Installation Files (XML and log) On Node—If checked, CTC saves the XML and log files on the node.

Step 13 Click Next. If you chose Skip Interactive Mode, continue with Step 14. If not, the wizard page that appears depends on the options chosen in Step 12: Complete the steps shown in Table 14-2 for each option.

Table 14-2 NE Update Wizard Options

NE Update Function
Node/Shelves Layout	View the cards and slots on the left side of the page and verify that they are the same as the layout in the Cisco Transport Planner Shelf Layout (see Table 14-1). If the cards and slots match, click Apply . If not, click Cancel . and contact your next level of support to verify that you have the correct node setup file. If the site has a multishelf configuration, click Next and repeat this step for each shelf at the site. CTC preprovisions the slots. (This might take a few seconds.) The results appear in the Log window. Slots that are successfully provisioned display an “Applied” status. A “Slot not empty” status appears if slots cannot be provisioned because a card is physically installed or the slot is already provisioned. If this occurs, complete the following steps. Otherwise, continue with the next NE Update function. 1. Click Cancel , then click Yes in the confirmation dialog box. The slot preprovisioning does not revert when you click Cancel. 2. If a physical card is installed, remove it from the shelf. 3. Perform one of the following steps: – Delete all the preprovisioned slots using the G351 Delete a Card in CTC, then repeat Steps 2 through Step 13. – Delete the slot where the Slot Not Empty error occurred using the G351 Delete a Card in CTC. Complete the G353 Preprovision a Slot to provision the slot manually, then repeat Steps 2 through 13 making sure to uncheck the Provision Node Layout option in Step 12. Note When you preprovision a slot, the card is purple in the CTC shelf graphic and “NP” (not present) appears on the card. After the physical card is installed, the card changes to white and “NP” is removed from the CTC shelf graphic.
Passive Units Layout	1. Review the passive unit settings. 2. Click Apply . 3. Click Next.
Pluggable Port Modules	1. Review the PPM settings for each TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, and OTU2_XP card. 2. Click Apply . 3. Click Next.
Card Parameters	1. Review the OTN, FEC, and card mode settings for each TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, and OTU2_XP card. 2. Click Apply . 3. Click Next.
Internal Patchcords	1. Review the internal patchcords. 2. Click Apply . 3. Click Next.
Optical Sides	1. Review the optical side assignments. 2. Click Apply . 3. Click Next.
ANS Parameters	1. Review the ANS parameters on the left half of the page. c. Click Apply . The log file displays the results. At the end, a Done status will appear. If a parameter could not be applied, a Setting Refused status appears. If this occurs, contact your next level of support.
Select All	1. If checked, selects all the options.
Skip Interactive Mode	If checked, CTC provisions all the chosen setup components automatically without allowing you to view the results after each one.
Save Installation Files (XML and log) On Node	If checked, CTC saves the XML and log files on the node.

Step 14 Click Finish , then click OK in the Wizard Complete confirmation dialog box. The confirmation box indicates whether the xml import process was completed successfully.

Note Common control cards are not provisioned by Cisco Transport Planner.

Stop . You have completed this procedure .

DLP-G351 Delete a Card in CTC

Note It is recommended that the card be physically removed from its slot before deleting it from CTC.

Step 1 Verify that the following conditions are not present. (During node turn-up, these conditions are normally not present):

• The card is a TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE card.
• The card is part of a protection group.
• The card has optical channels or overhead circuits provisioned.
• The card is being used for timing.
• The card has an OSC/GCC termination.
• A port on the card is being used for a Link Management Protocol (LMP) channel or link.
• The card is part of an optical side.
• The card is assigned to DWDM patchcords.
• If a port on the card is in service.
• If a port on the card is part of a circuit.

If any of these conditions exist, do not continue. You will not be able to delete the card until the card is removed from protection groups; circuits, DCC, and GCCs are deleted; a different timing source is provisioned, and the LMP link or channel is deleted.

• To replace a TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE card, refer to the Cisco ONS 15454 DWDM Troubleshooting Guide .
• To delete a protection group, see the NTP-G83 Modify or Delete Card Protection Settings procedure..
• To delete optical channels see the G347 Delete Optical Channel Client Connections and the G106 Delete Optical Channel Network Connections; to delete overhead circuits, see the G112 Delete Overhead Circuits.
• To remove the card as a timing source, see the NTP-G87 Change Node Timing Parameters procedure.
• To remove OSC or GCC terminations, see the NTP-G85 Modify or Delete OSC Terminations, GCC Terminations, and Provisionable Patchcords procedure.
• To delete LMP channels or links, see G164 Configure Link Management Protocol.
• To remove a DWDM patchcord, see the G355 Delete an Internal Patchcord.
• To remove an optical side, see the G480 Delete an Optical Side.

Step 2 On the shelf graphic in CTC, right-click the card that you want to remove and choose Delete Card .

Note A deleted card no longer reboots and reappears in CTC after R5.0.

Step 3 Return to your originating procedure (NTP).

DLP-G353 Preprovision a Slot

Step 1 In node view (single-shelf mode) or multishelf view (multishelf mode), right-click an empty slot where you want to install a card.

Step 2 From the Add Card shortcut menu, choose the card type that will be installed based on the Cisco Transport Planner shelf layout (see Table 14-1). Only cards that can be installed in the slot appear in the Add Card shortcut menu. Table 14-3 shows the Add Card shortcut menu, submenu, card groups, and menu options or cards that they reference.

Note When you preprovision a slot, the card appears purple in the CTC shelf graphic (the card appears as white when a card is installed in the slot). NP on the card graphic indicates that the card is not physically installed.

Step 3 Repeat Step 2 until all the cards shown in the Cisco Transport Planner shelf layout are provisioned in CTC.

Stop . You have completed this procedure .

NTP-G320 Configure the Node as a Non-DWDM Network

Step 1 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > WDM-ANS > Provisioning tabs.

Step 2 From the Selector area, select Network Type.

Step 3 Choose Not-DWDM, from the Value drop-down list. Click Apply.

Step 4 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > WDM-ANS > Port Status tabs.

Step 5 Click the Launch ANS button. The relevant ports in the node will be in IS state.

Step 6 Click OK .

Step 7 Return to your originating procedure (NTP).

DLP-G693 Configure the Amplifier

Step 1 Display the amplifier card in card view.

Step 2 Click the Provisioning > Card tabs.

Step 3 Select the working mode from the Card Working Mode drop-down list.

Step 4 Change to node view (single-shelf mode) or multishelf view (multishelf mode), then click the Provisioning > WDM-ANS > Provisioning tabs.

Step 5 From the Selector area, select the amplifier slot. If the default parameters are present, continue with Step 6. If not, click Add to add the Channel LOS Threshold, Amplifier Tilt, Power, and Amplifier Working Mode parameters. To add the ANS parameters, see the G541 Add an ANS Parameter for instructions.

Step 6 Click the value of the ANS parameter that you want to modify and enter the new value specified in Table 14-4. To modify the ANS parameters, see the G681 Modify an ANS Parameter for instructions.

Step 7 Click Apply .

Step 8 Click the Provisioning > WDM-ANS > Port Status tabs.

Step 9 Click Launch ANS .

Step 10 In the Apply Launch ANS dialog box, click Yes .

Step 11 In the Launch ANS confirmation dialog box, click OK .

Step 12 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > WDM-ANS > Provisioning tabs.

Step 13 Verify the following in the Results column:

• Success - Changed —The parameter has been successfully changed with the ports in IS.

Step 14 Verify that the Set By column displays t he value “ANS” or “APC” as the application that sets the ANS parameter.

Step 15 Return to your originating procedure (NTP).

DLP-G694 Configure the PSM

Step 1 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > WDM-ANS > Provisioning tabs.

Step 2 From the Selector area, select the PSM slot. If the default parameters are present, continue with Step 3. If not, click Add to add the Channel LOS Threshold and VOA Attenuation parameters. To add the ANS parameters, see the G541 Add an ANS Parameter for instructions.

Step 3 Click the value of the ANS parameter that you want to modify and enter the new value specified in Table 14-4. To modify the ANS parameters, see the G681 Modify an ANS Parameter for instructions.

Step 4 Click Apply .

Step 5 Click the Provisioning > WDM-ANS > Port Status tabs.

Step 6 Click Launch ANS .

Step 7 In the Apply Launch ANS dialog box, click Yes .

Step 8 In the Launch ANS confirmation dialog box, click OK .

Step 9 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > WDM-ANS > Provisioning tabs.

Step 10 Verify the following in the Results column:

• Success - Changed —The parameter has been successfully changed with the ports in IS.

Step 11 Verify that the Set By column displays t he value “ANS” or “APC” as the application that sets the ANS parameter.

Step 12 Return to your originating procedure (NTP).

NTP-G328 Add, Modify, or Delete ANS Parameters

Note It is recommended that you use the Cisco Transport Planner XML configuration file to provision the ANS parameters instead of manually adding all the parameters in CTC. ANS provisioning parameters must be manually changed only by Cisco qualified personnel. Provisioning the ANS parameters incorrectly (either as preamplifier or booster input power thresholds) may impact traffic.

Step 1 Complete the DLP-G46 Log into CTC task at the node where you want to add, modify, or delete the ANS parameters. If you are already logged in, continue with Step 2.

Step 2 As needed, complete the following tasks:

• Complete the G541 Add an ANS Parameter.
• Complete the G681 Modify an ANS Parameter.
• Complete the G542 Delete an ANS Parameter.

Stop . You have completed this procedure .

DLP-G541 Add an ANS Parameter

Step 1 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > WDM-ANS > Provisioning tabs.

Step 2 Click Add . The Add ANS Parameter dialog box appears.

Step 3 Select the ANS parameter from the Parameter drop-down list.

Step 4 In the Port Selection area, complete the following fields:

• Type—Displays the card type.
• Shelf—Choose the shelf from the drop-down list.
• Slot—Choose the card from the Slot drop-down list. The drop-down list lists all the cards that support the ANS parameter selected in Step 3 .
• Port—Choose the port from the Port drop-down list. The drop-down list lists all the ports for the card selected in Step 4 that support the ANS parameter selected in Step 3 .

Step 5 Choose the granularity as OTS or OCH from the Granularity drop-down list.

Note Granularity can be set only for the ANS parameters applied to the LINE-RX, LINE-TX, COM-RX, or COM-TX ports.

Step 6 Type or choose the value for the ANS parameter in the Value field.

Step 7 Click OK .

Step 8 Return to your originating procedure (NTP).

DLP-G681 Modify an ANS Parameter

Note Do not begin this procedure until the Cisco Transport Planner NE Update file is created for the node. You must import the new NE Update file and run ANS to recalculate the ANS parameters for the node.

Step 1 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > WDM-ANS > Provisioning tabs.

Step 2 Click the value of the ANS parameter that you want to modify and enter the new value.

Note See Table 14-6 for supported ANS parameter ranges and values that can be specified.

Note The modified ANS parameter value is applied only after running the ANS.