DLP-D103 Soft-Reset a CE-100T-8 Card Using CTC

Note Soft-resetting the CE-100T-8 card is errorless in most cases. If there is a provisioning change during the soft reset, or if the firmware is replaced during the software upgrade process, the reset is not errorless.

Before configuring the node for RADIUS authentication, you must first add the node as a network device on the RADIUS server. Refer to the User Guide for Cisco Secure ACS for Windows Server for more information about configuring a RADIUS server.

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Superuser only

Caution Do not configure a node for RADIUS authentication until after you have added that node to the RADIUS server and added the RADIUS server to the list of authenticators. If you do not add the node to a RADIUS server prior to activating RADIUS authentication, no user will be able to access the node. Refer to the
User Guide for Cisco Secure ACS for Windows Server for more information about adding a node to a RADIUS server.

Note The following Cisco vendor-specific attribute (VSA) needs to be specified when adding users to the RADIUS server:

Step 3 Enter the RADIUS server IP address in the IP Address field. If the node is an end network element (ENE), enter the IP address of the gateway network element (GNE) in this field.

The GNE passes authentication requests from the ENEs in its network to the RADIUS server, which grants authentication if the GNE is listed as a client on the server.

Caution Because the ENE nodes use the GNE to pass authentication requests to the RADIUS server, you must add the ENEs to the RADIUS server individually for authentication. If you do not add the ENE node to a RADIUS server prior to activating RADIUS authentication, no user will be able to access the node. Refer to the
User Guide for Cisco Secure ACS for Windows Server for more information about adding a node to a RADIUS server.

Step 4 Enter the shared secret in the Shared Secret field. A shared secret is a text string that serves as a password between a RADIUS client and RADIUS server.

Step 5 Enter the RADIUS authentication port number in the Authentication Port field. The default port is 1812. If the node is an ENE, set the authentication port to a number within the range of 1860 to 1869.

Step 6 Enter the RADIUS accounting port in the Accounting Port field. The default port is 1813. If the node is an ENE, set the accounting port to a number within the range of 1870 to 1879.

Step 7 Click OK. The RADIUS server is added to the list of RADIUS authenticators.

Note You can add up to 10 RADIUS servers to a node's list of authenticators.

Step 8 Click Edit to make changes to an existing RADIUS server. You can change the IP address, the shared secret, the authentication port, and the accounting port.

Step 9 Click Delete to delete the selected RADIUS server.

Step 10 Click Move Up or Move Down to reorder the list of RADIUS authenticators. The node requests authentication from the servers sequentially from top to bottom. If one server is unreachable, the node will request authentication from the next RADIUS server on the list.

Step 12 Click the Enable RADIUS Accounting check box if you want to show RADIUS authentication information in the audit trail.

Step 13 Click the Enable the Node as the Final Authenticator check box if you want the node to be the final autheticator. This means that if every RADIUS authenticator is unavailable, the node will authenticate the login rather than locking the user out.

Step 14 Click Apply to save all changes or Reset to clear all changes.

Step 15 Return to your originating procedure (NTP).

DLP-D106 View and Terminate Active Logins

Purpose

This procedure allows you to view active CTC logins, retrieve the last activity time, and terminate all current logins.

Step 2 Click Logout to end the session of every logged-in user. This will log out all current users, excluding the initiating Superuser.

Step 3 Click Retrieve Last Activity Time to display the most recent activity date and time for users in the Last Activity Time field.

Step 4 Return to your originating procedure (NTP).

DLP-D107 Preprovision an SFP or XFP Device

Purpose

This procedure preprovisions Small Form-factor Pluggables (SFPs/XFPs) on the MRC-12, MRC-2.5G-12, and STM64-XFP cards. The SFPs/XFPs are referred to as pluggable port modules (PPMs) in CTC. Cisco-approved STM-1, STM-4, STM-16, STM-64, and multirate PPMs are compatible with the ONS 15454 SDH.

Note Before you install SFPs on the MRC-12 or MRC-2.5G-12 card, refer to the card information in "Optical Cards" chapter of the Cisco ONS 15454 SDH Reference Manual for bandwidth restrictions based on the port where you install the SFP and the cross-connect card being used.

•PPM—Choose the slot number where you want to preprovision the SFP/XFP from the drop-down list.

•PPM Type—Choose the number of ports supported by your SFP/XFP from the drop-down list. If only one port is supported, PPM (1 port) is the only option.

Step 6 Click OK. The newly created port appears in the Pluggable Port Modules area. The row in the Pluggable Port Modules area turns light blue and the Actual Equipment Type column lists the preprovisioned PPM as unknown until the actual SFP/XFP is installed. After the SFP/XFP is installed, the row turns white and the column lists the equipment name.

Step 7 Verify that the PPM appears on the list in the Pluggable Port Modules area. If it does not, repeat Steps 4 through 6.

Step 8 On the Provisioning tab, click the Line subtab. If applicable for the PPM you are preprovisioning, use the Reach and Wavelength columns to configure these parameters as needed.

Note Only the parameters that are editable for the PPMs on a particular platform type are provisionable. For example, some platforms may not have PPMs with configurable wavelengths or reaches. In this case, wavelength and reach are not provisionable.

Sets the VC4 that will be used for pointer justification. If set to 0, no VC4 is monitored. Only one VC4 can be monitored on each STM-N port.

•0 - 1 (STM-1, per port)

•0 - 4 (STM-4, per port)

•0 - 16 (STM-16)

•0 - 64 (STM-64)

Admin State

Sets the port administrative service state unless network conditions prevent the change. For more information about administrative states, refer to the "Administrative and Service States" appendix of the Cisco ONS 15454 SDH Reference Manual.

•Unlocked—Puts the port in service. The port service state changes to Unlocked-enabled.

•Unlocked,automaticInService—Puts the port in automatic in-service. The port service state changes to Unlocked-disabled,automaticInService.

•Locked,disabled—Removes the port from service and disables it. The port service state changes to Locked-enabled,disabled.

•Locked,maintenance—Removes the port from service for maintenance. The port service state changes to Locked-enabled,maintenance.

Note CTC will not allow you to change a port service state from Unlocked-enabled to Locked-enabled,disabled. You must first change a port to the Locked-enabled,maintenance service state before putting it in the Locked-enabled,disabled service state.

Service State

(Display only) Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, refer to the "Administrative and Service States" appendix of the Cisco ONS 15454 SDH Reference Manual.

•Unlocked-enabled—The port is fully operational and performing as provisioned.

•Unlocked-disabled,automaticInService—The port is out-of-service, but traffic is carried. Alarm reporting is suppressed. The ONS node monitors the ports for an error-free signal. After an error-free signal is detected, the port stays in the Unlocked-disabled,automaticInService state for the duration of the soak period. After the soak period ends, the port service state changes to Unlocked-enabled.

•Locked-enabled,disabled—The port is out-of-service and unable to carry traffic.

•Locked-enabled,maintenance—The port is out-of-service for maintenance. Alarm reporting is suppressed, but traffic is carried and loopbacks are allowed.

AINS Soak

Sets the automatic in-service soak period.

•Duration of valid input signal, in hh.mm format, after which the card becomes in service (IS) automatically

•0 to 48 hours, 15-minute increments

Type

Displays the port as SDH.

•SDH

ALS Mode

Sets the automatic laser shutdown function.

•Disabled

•Auto Restart

•Manual Restart

•Manual Restart for Test

Reach

(Does not apply to all cards) Allows you to provision the reach value. You can also choose Auto Provision, which allows the system to automatically provision the reach from the PPM reach value on the hardware.

The options that appear in the drop-down list depend on the card:

•SR (short reach, up to 2 km distance)

•SR-1 (up to 2 km distance)

•IR-1 (intermediate reach, up to 15 km distance)

•IR-2 (up to 40 km distance)

•LR-1 (long reach, up to 40 km distance)

•LR-2 (up to 80 km distance)

•LR-3 (up to 80 km distance)

Wavelength

(Does not apply to all cards) Allows you to provision the wavelength frequency.

Step 1 In node view, double-click the card where you want to change the optics settings.

Step 2 Click the Provisioning> Optics Thresholds tabs.

Step 3 Modify any of the settings described in Table 18-2 by clicking in the field you want to modify. In some fields you can choose an option from a drop-down list; in others you can type a value or select or deselect a check box.

Table 18-2 Optics Thresholds Settings

Parameter

Description

Options

Port

(Display only) Port number.

•1 (STM-64, STM64-XFP)

•1-12 (MRC_12, MRC-2.5G-12)

LBC-LOW

Laser bias current-minimum.

Default (15 min/1 day): 50 percent

LBC-HIGH

Laser bias current-maximum.

Default (15 min/1 day): 150 percent

OPT-LOW

Optical power transmitted-minimum.

Default (15 min/1 day): 80 percent

OPT-HIGH

Optical power transmitted-maximum.

Default (15 min/1 day): 120 percent

OPR-LOW

Optical power received-minimum.

Default (15 min/1 day): 50 percent

OPR-HIGH

Optical power received-maximum.

Default (15 min/1 day): 200 percent

Set OPR

Setting the optical power received establishes the received power level as 100 percent. If the receiver power decreases, then the OPR percentage decreases to reflect the loss in receiver power. For example, if the receiver power decreases by 3 dBm, the OPR decreases 50 percent.

Click SET.

Types

Sets the type of alert that occurs when a threshold is crossed. To change the type of threshold, choose one and click Refresh.

•TCA (threshold cross alert)

•Alarm

Intervals

Sets the time interval for collecting parameter counts. To change the time interval, choose the desired interval and click Refresh.

•15 Min

•1 Day

Step 4 Click Apply.

Step 5 Return to your originating procedure (NTP).

DLP-D111 Changing the Maximum Number of Session Entries for Alarm History

Purpose

This task changes the maximum number of session entries included in the alarm history. Use this task to extend the history list in order to save information for future reference or troubleshooting.

This button causes CTC to retrieve a current alarm summary for the card, node, or network. This step is optional because CTC updates the Alarms window automatically as raise/clear messages arrive from the node.

Note Alarms that have been raised during the session will have a check mark in the Alarms window New column. When you click Synchronize, the check mark disappears.

Step 3 Return to your originating procedure (NTP).

DLP-D114 View Conditions

Purpose

Use this task to view conditions [events with a Not Reported (NR) severity] at the card, node, or network level. The Conditions tab gives you a clear record of changes or events that do not result in alarms.

Events that are reported as Major (MJ), Minor (MN), or Critical (CR) severities are alarms. Events that are reported as Not Alarmed (NA) are conditions. Conditions that are not reported at all are marked NR in the Conditions window severity column.

Conditions that have a default severity of CR, MJ, MN, or NA but are not reported due to exclusion or suppression are shown as NR in the Conditions window.

Note When a port is placed in the Locked-enabled,maintenance service state, it raises an Alarms Suppressed for Maintenance (AS-MT) condition. For information about alarm and condition troubleshooting, refer to the Cisco ONS 15454 SDH Troubleshooting Guide.

Note When a port is placed in the Unlocked-disabled,automaticInService service state but is not connected to a valid signal, it generates a loss of signal (LOS) alarm.

Step 3 If you want to apply exclusion rules, check the Exclude Same Root Cause check box at the node or network view, but do not check the Exclude Same Root Cause check box in card view.

An exclusion rule eliminates all lower-level alarms or conditions that originate from the same cause. For example, a fiber break might cause an LOS alarm, an alarm indication signal (AIS) condition, and a signal failure (SF) condition. If you check the Exclude Same Root Cause check box, only the LOS alarm will appear.

Step 4 Return to your originating procedure (NTP).

DLP-D117 Apply Alarm Profiles to Cards and Nodes

Purpose

This task applies a custom or default alarm profile to cards or nodes.

a. Click the Node Profile drop-down arrow at the bottom of the window (Figure 18-6).

b. Choose the new alarm profile from the drop-down list.

c. Click Apply.

Step 4 To reapply a previous alarm profile after you have applied a new one, select the previous profile and click Apply again.

Step 5 Return to your originating procedure (NTP).

DLP-D121 Enable Pointer Justification Count Performance Monitoring

Purpose

This task enables pointer justification counts, which provide a way to align the phase variations in VC4 payloads and to monitor the clock synchronization between nodes. A consistent, large, pointer justification count indicates clock synchronization problems between nodes.

Step 5 In the Service State field, confirm that the port isin the Unlocked-enabled service state.

Step 6 If the port is Unlocked-enabled, click Apply. If the port is out of service (Locked-enabled,disabled; Locked-enabled,maintenance; Unlocked-disabled,automaticInService), choose Unlocked in the Admin State drop-down list and click Apply.

Step 5 View the Curr column to find PM counts for the current 15-minute interval.

Each monitored performance parameter has corresponding threshold values for the current time period. If the value of the counter exceeds the threshold value for a particular 15-minute interval, a threshold crossing alert (TCA) is raised. The number represents the counter value for each specific performance monitoring parameter.

Note If a complete 15-minute interval count is not possible, the value appears with a yellow background. An incomplete or incorrect count can be caused by monitoring for less than 15 minutes after the counter started, changing node timing settings, changing the time zone settings, replacing a card, resetting a card, or changing port states. When the problem is corrected, the subsequent 15-minute interval appears with a white background.

Step 7 Return to your originating procedure (NTP).

DLP-D125 Refresh PM Counts at One-Day Intervals

Purpose

This task changes the window view to display PM parameters in one-day intervals.

Step 1 In node view, double-click the card where you want to view PM counts. The card view appears.

Step 2 Click the Performance tab.

Step 3 Click the 1 day radio button.

Step 4 Click Refresh. Performance monitoring appears in 1-day intervals synchronized with the time of day.

Step 5 View the Curr column to find PM counts for the current 1-day interval.

Each monitored performance parameter has corresponding threshold values for the current time period. If the value of the counter exceeds the threshold value for a particular 1-day interval, a TCA is raised. The number represents the counter value for each specific performance monitoring parameter.

Note If a complete count over a 1-day interval is not possible, the value appears with a yellow background. An incomplete or incorrect count can be caused by monitoring for less than 24 hours after the counter started, changing node timing settings, changing the time zone settings, replacing a card, resetting a card, or changing port states. When the problem is corrected, the subsequent 1-day interval appears with a white background.

Step 7 Return to your originating procedure (NTP).

DLP-D126 View Near-End PM Counts

Purpose

This task enables you to view near-end PM counts for the selected card and port.

Step 1 In node view, double-click the card where you want to view PM counts. The card view appears.

Step 2 Click the Performance tab.

Step 3 Click the Far End radio button.

Step 4 Click Refresh. All PM parameters recorded by the far-end node for the selected card on the outgoing signal appear. For PM parameter definitions, refer to the "Performance Monitoring" chapter in the Cisco ONS 15454 SDH Reference Manual.

Step 5 View the Curr column to find PM counts for the current time interval.

Step 6 View the Prev-n columns to find PM counts for the previous time intervals.

Step 7 Return to your originating procedure (NTP).

DLP-D129 Reset Current PM Counts

Purpose

This task clears the current PM count, but it does not clear the cumulative PM count. This task allows you to see how quickly PM counts rise.

Step 1 In node view, double-click the card where you want to view PM counts. The card view appears.

Step 2 Click the Performance tab.

Step 3 Click Baseline.

The Baseline button clears the PM counts displayed in the current time interval, but does not clear the PM counts on the card. When the current time interval expires or the window view changes, the total number of PM counts on the card and on the window appear in the appropriate column. The baseline values are discarded if you change views to a different window and then return to the Performance Monitoring window.

Step 4 View the current statistics columns to observe changes to PM counts for the current time interval.

Step 5 Return to your originating procedure (NTP).

DLP-D131 Search for Circuits

Purpose

This task searches for ONS 15454 SDH circuits at the network, node, or card level.

•Port—Click the PPM number and port number from the drop-down list. The first number indicates the PPM and the second number indicates the port number on the PPM. For example, the first PPM displays as 1-1 and the second PPM displays as 2-1.

•Port Type—Click the type of port from the drop-down list. The port type list displays the supported port rates on your PPM. See Table 18-4 for definitions of the supported rates on the MRC-12 and MRC-2.5G-12 cards.

Note Before deleting a PPM, delete the PPM from the provisioning pane.

Step 1 Determine if the PPM can be deleted.

You cannot delete a port on a PPM if it is in service, part of a protection group, has a communications channel termination in use, is used as a timing source, has circuits, or has overhead circuits. As needed, complete the following procedures and tasks:

Step 2 In node view, double-click the MRC-1,2, MRC-2.5G-12, or STM64-XFP card where you want to delete PPM settings.

Step 3 Click the Provisioning> Pluggable Port Modulestabs.

Step 4 To delete a PPM and the associated ports:

a. Click the PPM line that appears in the Pluggable Port Modules area. The highlight changes to dark blue.

b. Click Delete. The Delete PPM dialog box appears.

c. Click Yes. The PPM provisioning is removed from the Pluggable Port Modules area and the Pluggable Ports area.

Step 5 Verify that the PPM provisioning is deleted:

•If the PPM was preprovisioned, CTC shows an empty slot in CTC after it is deleted.

•If the SFP (PPM) is physically present when you delete the PPM provisioning, CTC transitions to the deleted state; the ports (if any) are deleted, and the PPM is represented as a gray graphic in CTC. The SFP can be provisioned again in CTC or the equipment can be removed, in which case the removal causes the graphic to disappear.

Step 1 In node view, double-click the CE-100T-8 or CE-MR-10 card graphic to open the card.

Step 2 Click the Provisioning > EtherPorts tabs.

Step 3 For each CE-100T-8 or CE-MR-10 port, provision the following parameters:

•Port Name—If you want to label the port, enter the port name.

Note Circuit table displays port name of the POS port and not the Ethernet port.

•Admin State—Choose Unlocked to put the port in service.

•Expected Speed—Choose the expected speed of the device that is or will be attached to the Ethernet port. If you know the speed, choose 100 Mbps or 10 Mbps (for CE-100T-8), or 1000 Mbps, 100 Mbps, or 10 Mbps (for CE-MR-10) to match the attached device. If you do not know the speed, choosing Auto enables autonegotiation for the speed of the port, and the CE-100T-8 or CE-MR-10 port will attempt to negotiate a mutually acceptable speed with the attached device.

•Expected Duplex—Choose the expected duplex of the device that is or will be attached to the Ethernet port. If you know the duplex, choose Full or Half to match the attached device. If you do not know the duplex, choosing Auto enables autonegotiation for the duplex of the port, and the CE-100T-8 or CE-MR-10 port will attempt to negotiate a mutually acceptable duplex with the attached device.

•Enable Flow Control—Click this check box to enable flow control on the port (default). If you do not want to enable flow control, uncheck the box. The CE-100T-8 or CE-MR-10 attempts to negotiate symmetrical flow control with the attached device.

•802.1Q VLAN CoS—For a class-of-service (CoS)-tagged frame, the CE-100T-8 or CE-MR-10 can map the eight priorities specified in CoS for either priority or best effort treatment. Any CoS class higher than the class specified in CTC is mapped to priority, which is the treatment geared towards low latency. By default, the CoS is set to 7, which is the highest CoS value. The default results in all traffic being treated as best effort.

•IP ToS—The CE-100T-8 and CE-MR-10 can also map any of the 256 priorities specified in IP type of service (ToS) to either priority or best effort treatment. Any ToS class higher than the class specified in CTC is mapped to priority, which is the treatment geared towards low latency. By default, the ToS is set to 255, which is the highest ToS value. This results in all traffic being sent to the best effort queue by default.

Note Untagged traffic is treated as best effort.

Note If traffic is tagged with both CoS and IP ToS, then the CoS value is used, unless the CoS value is 7.

Step 4 Click Apply.

Step 5 Refresh the Ethernet statistics:

a. Click the Performance > Ether Ports > Statistics tabs.

b. Click Refresh.

Note Reprovisioning an Ethernet port on the CE-100T-8 or CE-MR-10 card does not reset the Ethernet statistics for that port.

Step 6 Return to your originating procedure (NTP).

DLP-D137 Provision a J1 Path Trace on STM-N Ports

Purpose

This task monitors a path trace on VC4 high-order ports within the circuit path.

Tools/Equipment

The STM-N ports that you want to monitor must be on STM-N cards capable of receiving path trace. See Table 19-5 for a list of applicable cards.

•Auto—Uses the first string received from the port at the other path trace end as the current expected string. An alarm is raised when a string that differs from the baseline is received. For STM-N ports, Auto is recommended because Manual mode requires you to trace the circuit on the Edit Circuit window to determine whether the port is the source or destination path.

•Manual—Uses the Current Expected String field as the baseline string. An alarm is raised when a string that differs from the Current Expected String is received.

Note It is not necessary to set the format (16 or 64 bytes) for the expected string; the path trace process automatically determines the format.

Step 7 If you set the Path Trace Mode field to Manual, enter the string that the STM-N port should receive in the New Expected String field. To do this, trace the circuit path on the detailed circuit window to determine whether the port is in the circuit source or destination path, then set the New Expected String to the string transmitted by the circuit source or destination. If you set the Path Trace Mode field to Auto, skip this step.

Step 8 Click Apply, then click Close.

Step 9 Return to your originating procedure (NTP).

DLP-D140 Change the Node Name, Date, Time, and Contact Information

Purpose

This task changes basic information such as node name, date, time, and contact information.

Step 1 In node view, double-click the CE-100T-8, CE-1000-4, or CE-MR-10 card graphic to open the card.

Step 2 Click the Provisioning > POS Ports tabs.

Step 3 For each CE-100T-8, CE-1000-4, or CE-MR-10 port, provision the following parameters:

•Port Name—If you want to label the port, enter the port name.

Note Circuit table displays port name of the POS port and not the Ethernet port.

•Admin State—Choose Unlocked to put the port in service.

•Framing Type—Choose GPF-F POS framing (the default) or HDLC POS framing. The framing type needs to match the framing type of the POS device at the end of the SONET circuit.

•Encap CRC—With GFP-F framing, the user can configure a 32-bit cyclic redundancy check (CRC) (the default) or none (no CRC). HDLC framing provides a set 32-bit CRC. The CRC should be set to match the CRC of the POS device on the end of the SONET circuit.

Note For more details about the interoperability of ONS Ethernet cards, including information on encapsulation, framing, and CRC, refer to the "POS on ONS Ethernet Cards" chapter of the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide.

Note The CE-Series cards use LEX encapsulation, which is the primary POS encapsulation used in ONS Ethernet cards.

•Entire Frame—Prints the entire CTC window including the graphical view of the card, node, or network. This option is available for all windows.

•Tabbed View—Prints the lower half of the CTC window containing tabs and data. The printout includes the selected tab (on top) and the data shown in the tab window. For example, if you print the History window Tabbed View, you print only history items appearing in the window. This option is available for all windows.

•Table Contents—Prints CTC data in table format without graphical representations of shelves, cards, or tabs. This option does not apply to:

The Table Contents option prints all the data contained in a table and the table column headings. For example, if you print the History window Table Contents view, you print all data included in the table whether or not items appear in the window.

Tip When you print using the Tabbed View option, it can be difficult to distinguish whether the printout applies to the network, node, or card view. To determine the view, compare the tabs on the printout. The network, node, and card views are identical except that the network view does not contain an Inventory tab or a Performance tab.

Figure 18-9 Selecting CTC Data For Print

Step 4 Click OK.

Step 5 In the Windows Print dialog box, click a printer and click OK.

Step 6 Repeat this task for each window that you want to print.

Step 7 Return to your originating procedure (NTP).

DLP-D147 Export CTC Data

Purpose

This task exports CTC table data as delineated text to view or edit the data in text editor, word processing, spreadsheet, database management, or web browser applications. You can also export data from the Edit Circuits window.

•As HTML—Saves data as a simple HTML table file without graphics. The file must be viewed or edited with applications such as Netscape Navigator, Microsoft Internet Explorer, or another application capable of opening HTML files.

•As CSV—Saves the CTC table as comma-separated values (CSV). This option does not apply to the Maintenance > Timing > Report window.

•As TSV—Saves the CTC table as tab-separated values (TSV).

Figure 18-10 Selecting CTC Data For Export

Step 5 If you want to open a file in a text editor or word processor application, procedures vary. Typically, you can use the File > Open command to view the CTC data, or you can double-click the file name and choose an application such as Notepad.

Text editor and word processor applications format the data exactly as it is exported, including comma or tab separators. All applications that open the data files allow you to format the data.

Step 6 If you want to open the file in spreadsheet and database management applications, procedures vary. Typically, you need to open the application, choose File > Import, and then choose a delimited file to format the data in cells.

Spreadsheet and database management programs also allow you to manage the exported data.

Note Domains created by one user are visible to all users who log into the network.

Note To allow users of any security level to create local domains, that is, domains that are visible on the home CTC session only, superusers can change the CTC.network.LocalDomainCreationAndViewing NE default value to TRUE. A TRUE value means any user can maintain the domain information in his or her Preferences file, meaning domain changes will not affect other CTC sessions. (The default value is FALSE, meaning domain information affects all CTC sessions and only superusers can create a domain or put a node into a domain.) See the "NTP-D345 Edit Network Element Defaults" procedure to change NE default values.

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

Step 2 Right-click the network map and choose Create New Domain from the shortcut menu.

Step 3 When the domain icon appears on the map, click the map name and type the domain name.

Note Domain changes, such as added or removed node icons, are visible to all users who log into the network.

Note To allow users of any security level to create local domains, that is, domains that are visible on the home CTC session only, superusers can change the CTC.network.LocalDomainCreationAndViewing NE default value to TRUE. A TRUE value means any user can maintain the domain information in his or her Preferences file, meaning domain changes will not affect other CTC sessions. (The default value is FALSE, meaning domain information affects all CTC sessions and only superusers can create a domain or put a node into a domain.) See the "NTP-D345 Edit Network Element Defaults" procedure to change NE default values.

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

Step 2 Locate the domain action you want in Table 18-5 and complete the appropriate steps.

Table 18-5 Managing Domains

Domain action

Steps

Move a domain

Drag and drop the domain icon to the new location.

Rename a domain

Right-click the domain icon and choose Rename Domain from the shortcut menu. Type the new name in the domain name field.

Add a node to a domain

Drag and drop the node icon to the domain icon.

Move a node from a domain to the network map

Open the domain and right-click a node. Choose Move Node Back to Parent View.

Open a domain

Complete one of the following:

•Double-click the domain icon.

•Right-click the domain and choose Open Domain.

Return to network view

Right-click the domain view area and choose Go to Parent View from the shortcut menu.

Preview domain contents

Right-click the domain icon and choose Show Domain Overview. The domain icon shows a small preview of the nodes in the domain. To turn off the domain overview, right-click the overview and select Show Domain Overview.

Remove domain

Right-click the domain icon and choose Remove Domain. Any nodes residing in the domain are returned to the network map.

Step 3 Return to your originating procedure (NTP).

DLP-D150 Modify a 1:1 Protection Group

Purpose

This task modifies a 1:1 protection group for electrical cards (E3-12 and DS3i-N-12) cards.

Step 2 In the Protection Groups area, click the 1:1 protection group you want to modify.

Step 3 In the Selected Group area, you can modify the following, as needed:

•Name—Type the changes to the protection group name. The name can have up to 32 alphanumeric characters.

•Revertive—Check this box if you want traffic to revert to the working card after failure conditions stay corrected for the amount of time chosen from the Reversion Time drop-down list. Uncheck if you do not want traffic to revert.

•Reversion time—If the Revertive check box is selected, choose the reversion time from the Reversion time drop-down list. The range is 0.5 to 12.0 minutes. The default is 5.0 minutes. This is the amount of time that will elapse before the traffic reverts to the working card. Traffic can revert when conditions causing the switch are cleared.

•Trap Version—Choose either SNMPv1 or SNMPv2. Refer to your NMS documentation to determine whether to use SNMPv1 or SNMPv2.

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

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

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

Step 7 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 Enable SNMP Proxy check box on the SNMP tab.

Step 8 If you want to allow using generic SNMP MIBs, check the Use Generic MIB check box.

Step 3 In the Protection Groups area, click the 1:N protection group you want to modify.

Step 4 In the Selected Group area, change any of the following, as needed:

•Name—Type the changes to the protection group name. The name can have up to 32 alphanumeric characters.

•Available Entities—If cards are available, they will appear here. Use the arrow buttons to move them into the Working Cards column.

•Working Entities—Use the arrow buttons to move cards out of the Working Cards column.

•Reversion Time—Choose a reversion time from the drop-down list. The range is 0.5 to 12.0 minutes. The default is 5.0 minutes. This is the amount of time that will elapse before the traffic reverts to the working card. Traffic can revert when conditions causing the switch are cleared.

•Community—Enter the SNMP community name. (For more information about SNMP, refer to the "SNMP" chapter in the Cisco ONS 15454 SDH Reference Manual.)

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

•UDP Port—The default UDP port for SNMP traps is 162.

•Trap Version—Choose either SNMPv1 or SNMPv2. Refer to your NMS documentation to determine whether to use SNMPv1 or SNMPv2.

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

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

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

Step 7 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 Enable SNMP Proxy check box on the SNMP tab.

For more information about the SNMP proxy feature, refer to the "SNMP" chapter of the Cisco ONS 15454 SDH Reference Manual.

Step 8 Click Apply.

Step 9 If you are setting up SNMP proxies, you can set up to three relays for each trap address to convey SNMP traps from the NE to the NMS. To do this, complete the following substeps:

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

b. If the node you are logged into is an ENE, set the Relay A address to the GNE and type its community name in the community field. If there are NEs between the GNE and ENE, you can enter up to two SNMP proxy relay addresses and community names in the fields for Relay and Relay C. When doing this, consult the following guidelines:

•If the NE is directly connected to the GNE, enter the address and community name of the GNE for Relay A.

•If this NE is connected to the GNE through other NEs, enter the address and community name of the GNE for Relay A and the address and community name of NE 1 for Relay B and NE 2 for Relay C.

The SNMP proxy directs SNMP traps in the following general order:

ENE > RELAY A > RELAY B > RELAY C > NMS

For example:

•If there is are 0 intermediate relays, the order is ENE > RELAY A (GNE) > NMS

Step 2 In the Protection Groups area, click the 1+1 protection group you want to modify.

Step 3 In the Selected Group area, you can modify the following, as needed:

•Name—Type the changes to the protection group name. The name can have up to 32 alphanumeric characters.

•Bidirectional switching—Check or uncheck.

•Revertive—Check this box if you want traffic to revert to the working card after failure conditions stay corrected for the amount of time chosen from the Reversion Time drop-down list. Uncheck if you do not want traffic to revert.

•Reversion time—If the Revertive check box is selected, choose the reversion time from the Reversion time drop-down list. The range is 0.5 to 12.0 minutes. The default is 5.0 minutes. This is the amount of time that will elapse before the traffic reverts to the working card. Traffic can revert when conditions causing the switch are cleared.

Step 2 In the General Timing section, change any of the following information:

•Timing Mode

Note Because mixed timing can cause timing loops, Cisco does not recommend using the Mixed Timing option. Use this mode with care.

•Revertive

•Reversion Time

Step 3 In the Reference Lists area, you can change the following information:

Note Reference lists define up to three timing references for the node and up to six BITS Out references. BITS Out references define the timing references used by equipment that can be attached to the node's BITS pins on the MIC-C/T/P. If you attach equipment to BITS Out pins, you normally attach it to a node with Line mode because equipment near the external timing reference can be directly wired to the reference.

•NE Reference

•BITS-1 Out

•BITS-2 Out

Step 4 Click the BITS Facilities tab.

Step 5 In the BITS In and BITS Out areas, you can change the following information:

Note The BITS Facilities section sets the parameters for your BITS-1 and BITS-2 timing references. Many of these settings are determined by the timing source manufacturer. If equipment is timed through BITS Out, you can set timing parameters to meet the requirements of the equipment.

Note CTC will allow you to delete other Superusers only if at least one Superuser remains. For example, you can delete the CISCO15 user only if you have created another Superuser. Use this option with caution.

Step 1 In node view, select the Provisioning > Security > Users tabs.

Step 2 Choose the user you want to delete.

Step 3 Click Delete.

Step 4 In the Delete User dialog box, verify that the user name displayed is the one you want to delete.

Note CTC will allow you to delete other Superuser only if at least one Superuser remains. For example, you can delete the CISCO15 user only if you have created another Superuser. Use this option with caution.

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

Step 2 Click the Provisioning > Security > Users tabs. Highlight the name of the user you want to delete.

Step 3 Click Delete. The Delete User dialog box appears.

Step 4 Click OK. A Change Results confirmation dialog box appears.

Step 5 Click OK to acknowledge the changes. Confirm that the changes appear; if not, repeat the task.

Step 6 Return to your originating procedure (NTP).

DLP-D162 Format and Enter NMS Community String for SNMP Command or Operation

Purpose

This procedure describes how to format a network management system (NMS) community string to execute the following SNMP commands for GNEs and ENEs: Get, GetBulk, GetNext, and Set.

Step 1 If the SNMP Get command (or other operation) is enabled on the ONS 15454 SDH configured as a GNE, enter the community name assigned to the GNE in community name field on the MIB browser.

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

Step 2 If the SNMP Get command (or other operation) is enabled for the ENE through a SOCKS proxy-enabled GNE, create a formatted string to enter in the MIB browser community name field. Refer to the following examples when constructing this string for your browser:

•Formatted community string input example 1:

allviews{192.168.7.4,,,net7node4}

If "allviews" is a valid community name value at the proxy-enabled SNMP agent (the GNE), the GNE is expected to forward the PDU to 192.168.7.4 at Port 161. The outgoing PDU will have "net7node4" as the community name. This is the valid community name for the ENE with address 192.168.7.4.

•Formatted community string input example 2:

allviews{192.168.7.99,,,enter7{192.168.9.6,161,,net9node6}}

If "allviews" is a valid community name value at the proxy-enabled GNE, the GNE is expected to forward the PDU to 192.168.7.99 at the default port (Port 161) with a community name of "enter7{192.168.9.6,161,,net9node6}". The system with the address 192.168.7.99 (the NE between the GNE and the ENE) forwards this PDU to 192.168.9.6 at Port 161 (at the ENE) with a community name of "net9node6". The community name "enter7" is valid for the NE between the GNE and the ENE and "net9node6" is a valid community name for the ENE.

Step 3 Log into the NMS where the browser is installed to retrieve the network information from the ONS 15454 SDH.

Step 4 On this computer, go to Start and click the SNMP MIB browser application.

Step 5 In the Host and Community areas, enter the IP address of the GNE through which the ONS 15454 SDH with the information to be retrieved can be reached.

Step 6 In the Community area, enter the community string as explained in Step 2.

DLP-D165 Provision OSI Routing Mode

Purpose

This task provisions the Open System Interconnection (OSI) routing mode. Complete this task when the ONS 15454 SDH is connected to networks with third party network elements (NEs) that use the OSI protocol stack for data communications network (DCN) communication.

Caution Do not complete this task until you confirm the role of the node within the network. It will be either an ES, IS Level 1, or IS Level 1/Level 2. This decision must be carefully considered. For additional information about OSI provisioning, refer to the "Management Network Connectivity" chapter of the
Cisco ONS 15454 SDH Reference Manual.
Caution Link State Protocol (LSP) buffers must be the same at all NEs within the network, or loss of visibility might occur. Do not modify the LSP buffers unless you confirm that all NEs within the OSI have the same buffer size.
Caution LSP buffer sizes cannot be greater than the LAP-D maximum transmission unit (MTU) size within the OSI area.

Note For ONS 15454 SDH 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, click the Provisioning > OSI > Main Setup tabs.

Step 2 Choose a routing mode:

•End System—The ONS 15454 SDH 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.

•Intermediate System Level 1—The ONS 15454 SDH 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 SDH 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.

•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 network element (NE) is the target of the Type 1 PDU, and PDUs are not propagated to the NE from which the PDU was received.

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

•TARP PDUs L2 Propagation—If checked (default), TARP Type 2 PDUs received by the node that 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 TARP PDUs L2 Propagation is only used when the Node Routing Area is provisioned to Intermediate System Level 1/Level 2.

•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 L2 TARP Data Cache 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 LDP 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.

•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 LDB 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-D167 Add a Static TID-to-NSAP Entry to the TARP Data Cache

Purpose

This task adds a static TID-to-NSAP entry to the TDC. The static entries are required for NEs that do not support TARP and are similar to static routes. For a specific TID, you must force a specific NSAP.

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.

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 2to 24 alphanumeric characters (0-9, a-f) in length.

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

•ESH—Sets the End System Hello (ESH) propagation frequency. End system NEs transmit 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 PDU propagation frequency. Intermediate system NEs send ISHs to other ESs and ISs to inform them about the IS NETs it serves. The default is 10 seconds. The range is 10 to 1000 seconds.

•IIH—Sets the Intermediate System to Intermediate System Hello PDU propagation frequency. The IS-IS Hello PDUs establish and maintain adjacencies between ISs. The 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-D174 Create an IP-Over-CLNS Tunnel

Purpose

This task creates an IP-over-ConnectionLess Network Service (CLNS) tunnel to allow ONS 15454 SDH nodes to communicate across equipment and networks that use the OSI protocol stack.

Caution IP-over-CLNS tunnels require two endpoints. You will create one point on an ONS 15454 SDH. The other endpoint is generally provisioned on non-ONS equipment including routers and other vendor NEs. Before you begin, verify that you have the capability to create an OSI-over-IP tunnel on the other equipment location.

Step 1 In node view, click the Provisioning > OSI > Tunnels tabs.

Step 2 Click Create.

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

–GRE—Creates a Generic Routing Encapsulation 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.

Caution Always verify that the IP-over-CLNS tunnel type you choose is supported by the equipment at the other end of the tunnel.

•IP Address—Enter the IP address of the IP-over-CLNS tunnel 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.

DLP-D178 Change the OSI Routing Mode

Caution Do not complete this procedure until you confirm the role of the node within the network. It will be either an ES, IS Level 1, or IS Level 1/Level 2. This decision must be carefully considered. For additional information about OSI provisioning, refer to the "Management Network Connectivity" chapter of the
Cisco ONS 15454 SDH Reference Manual.
Caution LSP buffers must be the same at all NEs within the network, or loss of visibility could occur. Do not modify the LSP buffers unless you are sure that all NEs within the OSI have the same buffer size.
Caution LSP buffer sizes cannot be greater than the LAP-D MTU size within the OSI area.

Step 1 Verify the following:

•All L1/L2 virtual routers on the NE must reside in the same area. This means that all neighboring virtual routers must have at least one common area address.

•For OSI L1/L2 to ES routing mode changes, only one L1/L2 virtual router and no more than one subnet can be configured.

•For OSI L1 to ES routing mode changes, only one L1 virtual router and no more than one subnet can be configured.

Step 2 In node view, click the Provisioning > OSI tabs.

Step 3 Choose one of the following routing modes:

•End System—The ONS 15454 SDH 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 SDH 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.

Note Changing a routing mode should be carefully considered. Additional information about OSI ESs and ISs and the ES-IS and IS-IS protocols are provided in the "Management Network Connectivity" chapter of the Cisco ONS 15454 SDH Reference Manual.

Step 4 Although Cisco does not recommend changing the LSP (Link State Protocol Data Unit) buffer sizes, you can adjust the buffers in the following fields:

•L1 LSP Buffer Size—Adjusts the Level 1 link state PDU buffer size.

•L2 LSP Buffer Size—Adjusts the Level 2 link state PDU buffer size.

Step 5 Return to your originating procedure (NTP).

DLP-D179 Edit the OSI Router Configuration

Purpose

This task allows you to edit the OSI router configuration, including enabling and disabling OSI routers, editing the primary area address, and creating or editing additional area addresses.

b. For enabled routers, edit the primary area address, if needed. The address can be between 8 and 24 alphanumeric characters in length.

c. If you want to add or edit an area address to the primary area, enter the address at the bottom of the Multiple Area Addresses area. The area address can be 2 to 26 numeric characters (0-9) in length. Click Add.

d. Click OK.

Step 4 Return to your originating procedure (NTP).

DLP-D180 Edit the OSI Subnetwork Point of Attachment

Purpose

This task allows you to view and edit the OSI subnetwork point of attachment parameters. The parameters are initially provisioned when you create a Section DCC (SDCC), Line DCC (LDCC), generic communications channel (GCC), or optical service channel (OSC), or when you enable the LAN subnet.

•ESH—The End System Hello PDU propagation frequency. An end system 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—The Intermediate System Hello PDU propagation frequency. An intermediate system NE sends ISHs to other ESs and ISs to inform them about the NETs it serves. The default is 10 seconds. The range is 10 to 1000 seconds.

•IIH—The Intermediate System to Intermediate System Hello 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.

Note The IS-IS Cost and DIS Priority parameters are provisioned when you create or enable a subnet. You cannot change the parameters after the subnet is created. To change the DIS Priority and IS-IS Cost parameters, delete the subnet and create a new one.

Click OK.

Step 4 Return to your originating procedure (NTP).

DLP-D181 Edit an IP-Over-CLNS Tunnel

Purpose

This task allows you to edit the parameters of an IP-over-CLNS tunnel.

Caution Changing the IP or NSAP addresses or an IP-over-CLNS tunnel can cause loss of NE visibility or NE isolation. Do not change network addresses until you verify the changes with your network administrator.

Step 1 In node view, click the Provisioning > OSI > Tunnels tabs.

Step 2 Click Edit.

Step 3 In the Edit IP Over OSI Tunnel dialog box, complete the following fields:

–GRE—Creates a Generic Routing Encapsulation 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.

Caution Always verify that the IP-over-CLNS tunnel type you choose is supported by the equipment at the other end of the tunnel.

•IP Address—Enter the IP address of the IP-over-CLNS tunnel 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.

DLP-D183 View IS-IS Routing Information Base

Purpose

This task allows you to view the Intermediate System to Intermediate System (IS-IS) protocol routing information base (RIB). IS-IS is an OSI routing protocol that floods the network with information about NEs on the network. Each NE uses the information to build a complete and consistent picture of a network topology. The IS-IS RIB shows the network view from the perspective of the IS node.

Step 3 If additional routers are enabled, you can view their RIBs by choosing the router number in the Router field and clicking Refresh.

Step 4 Return to your originating procedure (NTP).

DLP-D184 View ES-IS Routing Information Base

Purpose

This task allows you to view the End System to Intermediate System (ES-IS) protocol RIB. ES-IS is an OSI protocol that defines how end systems (hosts) and intermediate systems (routers) learn about each other. For ESs, the ES-IS RIB shows the network view from the perspective of the ES node. For ISs, the ES-IS RIB shows the network view from the perspective of the IS node.

Note After you have selected the circuit properties in the Circuit Source dialog box according to the specific circuit creation procedure, you are ready to provision the circuit source.

Step 1 From the Node drop-down list, choose the node where the source will originate.

Step 2 From the Slot drop-down list, choose the slot containing the STM-N, MRC-12, or MRC-2.5G-12 card where the circuit will originate (Figure 18-11). If you choose an STM-N card, you can map the VC11 to VC4 for optical transport.

Figure 18-11 Defining the Circuit Source on an STM-16 Card

Step 3 Choose the port from the Port drop-down list.

Step 4 From the VC4 drop-down list, choose the source VC4.

Step 5 From the TUG3 drop-down list, choose the source TUG3.

Step 6 From the TUG2 drop-down list, choose the source TUG2.

Step 7 From the VC11 drop-down list, choose the source VC11.

Step 8 If you need to create a secondary source, for example, a subnetwork connection protection (SNCP) ring bridge/selector circuit entry point in a multivendor SNCP ring, click Use Secondary Source and repeat Steps 1 through 7 to define the secondary source. If you do not need to create a secondary source, continue with Step 9.

Step 11 From the Slot drop-down list, choose the slot containing the destination card. You can choose a MRC-12, MRC-2.5G-12, or STM-N card to map the VC11 to a VC4 for optical transport.

Step 12 Depending on the destination card, choose the destination port from the drop-down lists that appear based on the card selected in Step 11. See Table 6-2 for a list of valid options. CTC does not show ports, VC4s, TUG3s, TUG2s, or VC11s already used by other circuits.

Note If you and a user working on the same network choose the same VC4, TUG3, TUG2, or VC11 simultaneously, one of you receives a Path in Use error and is unable to complete the circuit. The user with the incomplete circuit needs to choose new destination parameters.

Step 13 If you need to create a secondary destination, for example, an SNCP ring bridge/selector circuit exit point in a multivendor SNCP ring, click Use Secondary Destination and repeat Steps 10 through 12 to define the secondary destination.

DLP-D187 Provision a Low-Order VC11 Circuit Route

You must have the Route Review and Edit page of the Circuit Creation wizard open.

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher

Step 1 In the Circuit Creation wizard in the Route Review and Edit area, click the source node icon if it is not already selected.

Step 2 Starting with a span on the source node, click the arrow of the span you want the circuit to travel. The arrow turns white. In the Selected Span area, the From and To fields provide span information. The source VC11 appears.

Step 3 If you want to change the source VC11, adjust the Source VC11 field; otherwise, continue with Step 4.

Step 5 Click Add Span. The span is added to the Included Spans list and the span arrow turns blue.

Step 6 Repeat Steps 2 through 5 until the circuit is provisioned from the source to the destination node through all intermediary nodes. If Fully Protect Path is checked in the Circuit Routing Preferences area, you must complete the following steps:

•Add two spans for all SNCP ring or unprotected portions of the circuit route from the source to the destination.

•Add one span for all MS-SPRing or 1+1 portions of the route from the source to the destination.

Step 2 Observe the Timing Mode field to see the type of timing (Line, External, Mixed) that has been set for that node.

Step 3 Scroll down to the Reference List and observe the NE Reference fields to see the timing references provisioned for that node.

Step 4 If the removed node was the only building integrated timing supply (BITS) timing source, perform the following:

a. Contact your synchronization coordinator or appropriate personnel before continuing with this procedure.

b. Look for another node on the ring that can be used as a BITS source and set that node's Timing Mode to External. Choose that node as the primary timing source for all other nodes in the ring. See the "DLP-D157 Change the Node Timing Source" task.

c. If no node in the reduced ring can be used as a BITS source, choose one node to be your internal timing source. Set that node's Timing Mode to External, set the BITS-1 and BITS-2 BITS In State to OOS, and set the NE Reference to Internal. Then, choose line timing for all other nodes in the ring. This forces the first node to be their primary timing source. (See the "DLP-D157 Change the Node Timing Source" task.)

Note This type of timing conforms to SETS requirements and is not considered optimal.

Step 5 If the removed node was not the only BITS timing source, provision the adjacent nodes to line timing using SDH links (east and west) as timing sources, traceable to the node with external BITS timing. See the "NTP-D28 Set Up Timing" procedure.

Step 6 Return to your originating procedure (NTP).

DLP-D196 Delete an MS-SPRing from a Single Node

Purpose

This task deletes an MS-SPRing from a node after you remove the node from an MS-SPRing.