Step 1 If the Java Plug-in Security Warning dialog box appears, choose one of the following options:

•Yes (Grant This Session)—Installs the public-key certificate to your PC only for the current session. After the session is ended, the certificate is deleted. This dialog box will appear the next time you log into the ONS 15454 SDH.

•No (Deny)—Denies permission to install certificate. If you choose this option, you cannot log into the ONS 15454 SDH.

•Always (Grant Always)—Installs the public-key certificate and does not delete it after the session is over. Cisco recommends this option.

•Yes—Removes the modified Java policy file from your PC. Choose this option only if you will log into ONS 15454 SDH nodes running Software R4.1 software or later.

•No—Does not remove the modified Java policy file from your PC. Choose this option if you will log into ONS 15454 SDH nodes running Software R4.0 or earlier. If you choose No, this dialog box will appear every time you log into the ONS 15454 SDH. If you do not want it to appear, check the Do not show the message again check box.

Caution If you delete the Java policy file, you cannot log into nodes running Software R4.0 and earlier. If you delete the file and want to log into an ONS 15454 SDH running an earlier release, insert the software CD for the release into your PC CD-ROM and run the CTC setup wizard to reinstall the Java policy file.

Step 3 Return to your originating procedure (NTP).

DLP-D421 View STM-N PM Parameters

Purpose

This task enables you to view performance monitoring (PM) counts on an STM-N card and port to detect possible performance problems.

Step 6 To monitor another port on a multiport card, choose another line from the Line drop-down list and click Refresh.

Step 7 Return to your originating procedure (NTP).

DLP-D422 Change the JRE Version

Purpose

This task changes the Java Runtime Environment (JRE) version, which is useful if you would like to upgrade to a later JRE version from an earlier one without using the software CD. This does not affect the browser default version. After selecting the desired JRE version, you must exit CTC. The next time you log into a node, the new JRE version will be used.

DLP-D424 View Alarm or Event History

Purpose

Use this task to view past cleared and uncleared ONS 15454 SDH alarm messages at the card, node, or network level. This task is useful for troubleshooting configuration, traffic, or connectivity issues that are indicated by alarms.

Step 1 Decide whether you want to view the alarm message history at node, network, or card level.

Step 2 To view node alarm history:

a. Click the History > Session tabs to view the alarms and conditions (events) raised during the current session.

b. Click the History > Shelf tabs to view the alarm and condition history for the node.

If you check the Alarms check box, the node's alarm history appears. If you check the Events check box, the node's Not Alarmed and transient event history appears. If you check both check boxes, you will retrieve node history for alarms and events.

c. Click Retrieve to view all available messages for the History > Shelf tab.

Tip Double-click an alarm in the alarm table or an event (condition) message in the history table to display the view that corresponds to the alarm message. For example, double-clicking a card alarm takes you to card view. In network view, double-clicking a node alarm takes you to node view.

Step 3 To view network alarm history from node view:

a. From the View menu, choose Go to Network View.

b. Click the History tab.

Alarms and conditions (events) raised during the current session appear.

Step 4 To view card alarm history from node view:

a. From the View menu, choose Go to Previous View.

b. Double-click a card on the shelf graphic to open the card-level view.

Note TCC2/TCC2P cards and cross-connect cards do not have a card view.

c. Click the History > Session tabs to view the alarm messages raised during the current session.

d. Click the History > Card tabs and click Retrieve to retrieve all available alarm messages for the card.

If you check the Alarms check box, the node's alarm history appears. If you check the Events check box, the node's Not Alarmed and transient event history appears. If you check both check boxes, you will retrieve node history for alarms and events.

Note The ONS 15454 SDH can store up to 640 critical alarm messages, 640 major alarm messages, 640 minor alarm messages, and 640 condition messages. When any of these limits is reached, the ONS 15454 SDH discards the oldest events in that category.

Raised and cleared alarm messages (and events, if selected) appear.

Step 5 Return to your originating procedure (NTP).

DLP-D425 Create a New or Cloned Alarm Severity Profile

Purpose

This task creates a custom severity profile or clones and modifies the default severity profile.

Step 2 If you want to create a new profile based upon the default profile in use, click New. Then go to Step 8.

Step 3 If you want to create a profile using an existing profile located on the node:

a. Click Load and From Node in the Load Profile(s) dialog box.

b. Click the node name you are logged into in the Node Names list.

c. Click the name of an existing profile in the Profile Names list, such as Default. Then go to Step 5.

Step 4 If you want to create a profile using an existing profile located in a file that is stored locally or on a network drive:

a. Click From File in the Load Profile(s) dialog box.

b. Click Browse.

c. Navigate to the file location in the Open dialog box.

d. Click Open.

Note All default or user-defined severity settings that are Critical (CR) or Major (MJ) are demoted to Minor (MN) in Non-Service-Affecting (NSA) situations as defined in Telcordia GR-474.

Step 5 Click OK.

The alarm severity profile appears in the Alarm Profiles window (Figure 21-2). The alarm profile list contains a master list of alarms that is used for a mixed node network. Some of these alarms might not be used in all ONS nodes.

Figure 21-2 Network View Alarm Profiles Window

Step 6 Right-click anywhere in the profile column to display the profile editing shortcut menu. (Refer to Step 9 for further information about the Default profile.)

Step 7 Click Clone in the shortcut menu.

Tip To see the full list of profiles, including those available for loading or cloning, click Available. You must load a profile before you can clone it.

Step 8 In the New Profile or Clone Profile dialog box, enter a name in the New Profile Name field.

Profile names must be unique. If you try to import or name a profile that has the same name as another profile, CTC adds a suffix to create a new name. Long file names are supported.

Step 9 Click OK.

A new alarm profile (named in Step 8) is created. This profile duplicates the default profile severities and appears at the right of the previous profile column in the Alarm Profiles window. You can select it and drag it to a different position.

Note Up to ten profiles, including the two reserved profiles, Inherited and Default, can be stored in CTC.

The Default profile sets severities to standard IEEE settings. If an alarm has an Inherited profile, it inherits (copies) its severity from the same alarm's severity at the higher level. For example, if you choose the Inherited profile from the network view, the severities at the lower levels (node, card, and port) will be copied from this selection. A card with an Inherited profile copies the severities used by the node that contains the card. (If you are creating profiles, you can apply these separately at the network level or at the card level. To do this, refer to the "DLP-D117 Apply Alarm Profiles to Cards and Nodes" task.)

Step 10 Modify (customize) the new alarm profile:

a. In the new alarm profile column, double-click the alarm severity you want to change in the custom profile.

b. Choose a severity from the drop-down list.

c. Repeat Steps 10a and 10b for each severity you want to customize. Refer to the following guidelines when you view the alarms or conditions after making modifications:

•All CR or MJ default or user-defined severity settings are demoted to MN in NSA situations.

•Default severities are used for all alarms and conditions until you create and apply a new profile.

•Changing a severity to inherited (I) or unset (U) does not change the severity of the alarm.

Step 11 After you have customized the new alarm profile, right-click the profile column to highlight it.

Note A previously created alarm profile cannot be deleted unless it has been stored on the node. If the profile is visible on the Alarm Profiles tab but is not listed in the Select Node/Profile Combinations to Delete dialog box, continue with Step 8.

Step 4 Click the node names in the Node Names list to highlight the profile location.

Tip If you hold the Shift key down, you can select consecutive node names. If you hold the Ctrl key down, you can select any combination of nodes.

Step 5 Click the profile name(s) you want to delete in the Profile Names list.

Step 6 Click OK.

Step 7 Click Yes in the Delete Alarm Profile dialog box.

Note If you delete a profile from a node, it still appears in the network view Provisioning > Alarm Profiles window unless you remove it using the following step.

Step 8 To remove the alarm profile from the window, right-click the column of the profile you deleted and choose Remove from the shortcut menu.

Note If a node and profile combination is selected but does not exist, a warning appears: "One or more of the profile(s) selected do not exist on one or more of the node(s) selected." For example, this warning appears if Node A has only Profile 1 stored and the user tries to delete both Profile 1 and Profile 2 from Node A. However, the operation still removes Profile 1 from Node A.

Note The Default and Inherited special profiles cannot be deleted and do not appear in the Select Node/Profile Combination for Delete window.

Step 1 At node, network, or card view, click the Alarms, Conditions, or History tab.

Step 2 Click the Filter button at the lower-left of the bottom toolbar.

The filter dialog box appears, displaying the General tab. Figure 21-6 shows the Alarm Filter dialog box; the Conditions and History tabs have similar dialog boxes.

Figure 21-6 Alarm Filter Dialog Box General Tab

In the General tab Show Severity area, you can choose which alarm severities will show through the alarm filter and provision a time period during which filtered alarms show through the filter. To change the alarm severities shown in the filter, go to Step 3. To change the time period filter for the alarms, go to Step 4.

Step 3 In the Show Severity area, click the check boxes for the severities (CR, MJ, MN, or Not Alarmed [NA]) that you want to be reported at the network level. Leave severity check boxes deselected (unchecked) to prevent those severities from appearing.

When alarm filtering is disabled, all alarms show.

Step 4 In the Time area, click the Show alarms between time limits check box to enable it. Click the up and down arrows in the From Date, To Date, and Time fields to modify what period of alarms are shown.

To modify filter parameters for conditions, continue with Step 5. If you do not need to modify them, continue with Step 6.

Caution If multiple CTC sessions are open, suppressing alarms in one session suppresses the alarms in all other open sessions.

Note Alarm suppression at the node level does not supersede alarm suppression at the card or port level. Suppression can exist independently for all three entities, and each entity will raise a separate Alarms Suppressed by User Command (AS-CMD) alarm.

All raised alarms for the node will change color to white in the Alarms window and their status will change to cleared. After suppressing alarms, clicking Synchronize in the Alarms window will remove cleared alarms from the window. However, an AS-CMD alarm will show in node or card view to indicate that node-level alarms were suppressed; this alarm will show System in the Object column.

Note The only way to suppress building integrated timing supply (BITS), power source, or system alarms is to suppress alarms for the entire node. These cannot be suppressed separately.

Step 3 To suppress alarms for individual cards:

a. Locate the card row (using the Location column for the slot number or the Eqpt Type column for the equipment name).

Alarms that directly apply to this card change appearance as described in Step 2. For example, if you suppressed raised alarms for an STM-3 card in Slot 16, raised alarms for this card will change in node or card view. The AS-CMD alarm will show the slot number in the Object number. For example, if you suppressed alarms for a Slot 16 STM-3 card, the AS-CMD object will be SLOT-16.

Alarms that apply directly to this port change appearance as described in Step 2. (However, alarms raised on the entire card will remain raised.) A raised AS-CMD alarm that shows the port as its object appears in either alarm window. For example, if you suppressed alarms for Port 1 on the Slot 16 STM-3 card, the alarm object will be FAC-16-1.

Step 8 Return to your originating procedure (NTP).

DLP-D431 Discontinue Alarm Suppression

Purpose

This task discontinues alarm suppression and reenables alarm reporting on a port, card, or node.

Suppressed alarms will reappear in the Alarms window. (They might have previously been cleared from the window using the Synchronize button.) The AS-CMD alarm with the System object will be cleared in all views.

Suppressed alarms will reappear in the Alarms window. (They might have previously been cleared from the window using the Synchronize button.) The AS-CMD alarm with the slot object (for example, SLOT-16) will be cleared in all views.

Step 3 To discontinue alarm suppression for ports, click the following tabs:

Step 4 Uncheck the Suppress Alarms check box for the port(s) you no longer want to suppress.

Step 5 Click Apply.

Suppressed alarms will reappear in the Alarms window. (They might have previously been cleared from the window using the Synchronize button.) The AS-CMD alarm with the port object (for example, FAC-16-1) will be cleared in all views.

Step 6 Return to your originating procedure (NTP).

DLP-D432 View Port Status on the LCD

Purpose

This task allows you to view STM-N port status without using CTC. The LCD shows the working/protection provisioning status and the active/standby line status for ports in 1+1 and multiplex section-shared protection ring (MS-SPRing) configurations. For unprotected and subnetwork connection protection (SNCP) ports, the LCD always shows "Working/Active."

DLP-D433 Run the CTC Installation Wizard for Windows

Purpose

This task installs the CTC online user manuals, Acrobat Reader 6.0.1, Java Runtime Environment (JRE) 5.0, and the CTC Java Archive (JAR) files. JRE 5.0 is required to run Software Release 9.0. Preinstalling the CTC JAR files saves time at initial login. If the JAR files are not installed, they are downloaded from the TCC2/TCC2P card the first time you log in.

Step 2 Verify that Service Pack 6a or later is installed. From Windows Start menu, choose Programs > Administrative Tools > Windows NT Diagnostics and check the service pack on the Version tab of the Windows NT Diagnostics dialog box. If Service Pack 6a or later is not installed, do not continue. Install Service Pack 6a following the computer upgrade procedures for your site. Go to Step 4.

Step 4 Insert the Cisco ONS 15454 SDH Release 9.0 software CD into your computer CD drive. The installation program begins running automatically. If it does not start, navigate to the CD directory and double-click setup.exe.

The Cisco Transport Controller Installation wizard displays the components that will be installed on your computer:

•Java Runtime Environment 5.0

•Acrobat Reader 6.0.1

•Online User Manuals

•CTC JAR files

Note JRE 5.0 is required to run Release 9.0. Preinstalling the CTC JAR files saves time at initial login. If the JAR files are not installed, they are downloaded from the TCC2/TCC2P card the first time you log in.

Step 5 Click Next.

Step 6 Complete one of the following:

•Click Typical to install both the Java Runtime Environment and the online user manuals.

•Click Custom if you want to install either the JRE or the online user manuals.

Step 7 Click Next.

Step 8 Complete the following, as applicable:

•If you selected Typical in Step 6, skip this step and proceed to Step 9.

•If you selected Custom, select the CTC component that you want to install and click Next.

Step 9 The directory where the installation wizard will install the CTC online user manuals appears. The default is C:\Program Files\Cisco\CTC\Documentation.

•If you want to change the CTC online user manuals directory, type the new directory path in the Directory Name field, or click Browse to navigate to the directory.

•If you do not want to change the directory, skip this step.

Step 10 Click Next.

Step 11 Review the components that will be installed. If you want to change your selections:

•If you selected Typical in Step 6, click Back twice to return to the installation setup type page. Choose Custom and repeat Steps 7 through 10.

•If you selected Custom in Step 6, click Back once or twice (depending on the components selected) until the component selection page appears. Repeat Steps 8 through 10.

Step 12 Click Next. It might take a few minutes for the JRE installation wizard to appear. If you selected Custom in Step 6 and need to install a JRE, continue with Step 14.

Step 13 To install the JRE, complete the following:

a. In the Java 2 Runtime Environment License Agreement dialog box, view the license agreement and choose one of the following:

•I accept the terms of the license agreement—Accepts the license agreement. Continue with Step b.

•I do not accept the terms of the license agreement—Disables the Next button on the Java 2 Runtime Environment License Agreement dialog box. Click Cancel to return to the CTC installation wizard. CTC will not install the JRE. Continue with Step 14.

Note If JRE 1.4.2 is already installed on your computer, the License Agreement page does not appear. You must click Next and then choose Modify to change the JRE installation or Remove to uninstall the JRE. If you choose Modify and click Next, continue with Step e. If you choose Remove and click Next, continue with Step i.

b. Click Next.

c. Choose one of the following:

•Click Typical to install all JRE features. If you select Typical, the JRE version installed will automatically become the default JRE version for your browsers.

•Click Custom if you want to select the components to install and select the browsers that will use the JRE version.

d. Click Next.

e. If you selected Typical, continue with Step i. If you selected Custom, click the drop-down list for each program feature that you want to install and choose the desired setting. The program features include:

•Java 2 Runtime Environment—(Default) Installs JRE 1.4.2 with support for European languages.

•Support for Additional Languages—Adds support for non-European languages.

To modify the directory where the JRE version is installed, click Change, navigate to the desired directory, and click OK.

f. Click Next.

g. In the Browser Registration dialog box, check the browsers that you want to register with the Java Plug-In. The JRE version will be the default for the selected browsers. It is acceptable to leave both browser check boxes unchecked.

Note Setting the JRE as the default for these browsers might cause problems with these browsers.

DLP-D434 Run the CTC Installation Wizard for UNIX

Purpose

This task installs the CTC online user manuals, Acrobat Reader 6.0.1, JRE 1.4.2, and the CTC JAR files. JRE 1.4.2 or 5.0 is required to run CTC Software R9.0. Preinstalling the CTC JAR files saves time at initial login. If the JAR files are not installed, they are downloaded from the TCC2/TCC2P card the first time you login.

Step 8 The directory where the installation wizard will install CTC online user manuals appears. The default is /usr/doc/ctc.

•If you want to change the CTC online user manuals directory, type the new directory path in the Directory Name field, or click Browse to navigate to the directory.

•If you do not want to change the CTC online user manuals directory, skip this step.

Step 9 Click Next.

Step 10 Review the components that will be installed. To change the components, complete one of the following:

•If you selected Typical in Step 5, click Back twice to return to the installation setup type page. Choose Custom and repeat Steps 6 through 9.

•If you selected Custom in Step 5, click Back once or twice (depending on the components selected) until the component selection page appears.Repeat Steps 7 through 9.

Step 11 Click Next. It might take a few minutes for the JRE installation wizard to appear. If you selected Custom in Step 6 and need to instal l a JRE, continue with Step 13.

Step 12 To install the JRE, complete the following:

a. In the Java 2 Runtime Environment License Agreement dialog box, view the license agreement and choose one of the following:

•I accept the terms of the license agreement—Accepts the license agreement. Continue with Step b.

•I do not accept the terms of the license agreement—Disables the Next button on the Java 2 Runtime Environment License Agreement dialog box. Click Cancel to return to the CTC installation wizard. CTC will not install the JRE. Continue with Step 13.

Note If JRE 5.0 is already installed on your computer, the License Agreement page does not appear. You must click Next and then choose Modify to change the JRE installation or Remove to uninstall the JRE. If you choose Modify and click Next, continue with Step e. If you choose Remove and click Next, continue with Step i.

b. Click Next.

c. Choose one of the following:

•Click Typical to install all JRE features. If you select Typical, the JRE version installed will automatically become the default JRE version for your browsers.

•Click Custom if you want to select the components to install and select the browsers that will use the JRE version.

d. Click Next.

e. If you selected Typical, continue with Step i. If you selected Custom, click the drop-down list for each program feature that you want to install and choose the desired setting. The program features include:

•Java 2 Runtime Environment—(Default) Installs JRE 5.0 with support for European languages.

•Support for Additional Languages—Adds support for non-European languages.

To modify the directory where the JRE version is installed, click Change, navigate to the desired directory, and click OK.

f. Click Next.

g. In the Browser Registration dialog box, check the browsers that you want to register with the Java Plug-In. The JRE version will be the default for the selected browsers. It is acceptable to leave both browser check boxes unchecked.

Note Setting the JRE version as the default for these browsers might cause problems with these browsers.

•Restore Timeout—Sets a time delay for enabling of front and backplane access when DCC connections are lost and "DCC only" is chosen in LAN Access. Front and backplane access is enabled after the restore timeout period has passed. Front and backplane access is disabled as soon as DCC connections are restored.

•Disable IPv4 access for IPv6 enabled ports— Select this option to disable IPv4 on ports which are IPv6 enabled. Before you select this option, ensure that IPv6 is enabled and the node is not in multishelf mode.

Step 3 In the Shell Access area, set the shell program used to access the node:

•Access State: Allows you to set the shell program access mode to Disable (disables shell access) or Non-Secure, Secure. Secure mode allows access to the node using the Secure Shell (SSH) program. SSH is a terminal-remote host Internet protocol that uses encrypted links.

•Telnet Port: Allows access to the node using the Telnet port. Telnet is the terminal-remote host Internet protocol developed for the Advanced Agency Research Project Network (ARPANET). Port 23 is the default.

•Enable Shell Password: If checked, enables the SSH password. To disable the password, you must uncheck the check box and click Apply. You must type the password in the confirmation dialog box and click OK to disable it.

•Default - TCC Fixed—(Default) Uses Port 57790 to connect to ONS 15454s on the same side of the firewall or if no firewall is used. This option can be used for access through a firewall if Port 57790 is open.

Places port in service, out of service, or out of service-maintenance.

•IS

•OOS

•OOS_MT

Port Rate

Selects the Fibre Channel interface.

•1 Gbps

•2 Gbps

Link Rate

Displays the actual rate of the port.

—

Max GBIC Rate

Displays the maximum Gigabit Interface Converter (GBIC) rate. Cisco supports two GBICs for the FC_MR-4 card (ONS-GX-2FC-SML and ONS-GX-2FC-MMI). If used with another GBIC, "Contact GBIC vendor" appears in this field.

—

Enable Link Recovery

Enables or disables link recovery if a local port is inoperable. If enabled, a link reset occurs when there is a loss of transport from a cross-connect switch, a protection switch, or an upgrade.

Step 6 From the Port drop-down list, choose the applicable port on the Ethernet card that you selected.

Step 7 From the Variable drop-down list, choose the variable. See Table 21-2 for a list of the Ethernet threshold variables available in this field.

Table 21-2 Ethernet Threshold Variables (MIBs)

Variable

Definition

iflnOctets

Total number of octets received on the interface, including framing octets.

iflnUcastPkts

Total number of unicast packets delivered to an appropriate protocol.

ifInMulticastPkts

(G-Series only) Number of multicast frames received error free.

ifInBroadcastPkts

(G-Series only) The number of packets, delivered by this sublayer to a higher (sub)layer, that were addressed to a broadcast address at this sublayer.

ifInDiscards

(G-Series only) The number of inbound packets that were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol.

iflnErrors

Number of inbound packets discarded because they contain errors.

ifOutOctets

Total number of transmitted octets, including framing packets.

ifOutUcastPkts

Total number of unicast packets requested to transmit to a single address.

ifOutMulticastPkts

(G-Series only) Number of multicast frames transmitted error free.

ifOutBroadcastPkts

(G-Series only) The total number of packets that higher-level protocols requested be transmitted, and that were addressed to a broadcast address at this sublayer, including those that were discarded or not sent.

ifOutDiscards

(G-Series only) The number of outbound packets that were chosen to be discarded even though no errors had been detected that would prevent their being transmitted.

dot3statsAlignmentErrors

Number of frames with an alignment error, that is, the length is not an integral number of octets and the frame cannot pass the frame check sequence (FCS) test.

dot3StatsFCSErrors

Number of frames with frame check errors, that is, there is an integral number of octets, but an incorrect FCS.

dot3StatsSingleCollisionFrames

(Not supported by E-Series or G-Series) Number of successfully transmitted frames that had exactly one collision.

dot3StatsMutlipleCollisionFrames

(Not supported by E-Series or G-Series) Number of successfully transmitted frames that had multiple collisions.

dot3StatsDeferredTransmissions

(Not supported by E-Series or G-Series) Number of times the first transmission was delayed because the medium was busy.

dot3StatsLateCollisions

(Not supported by E-Series or G-Series) Number of times that a collision was detected later than 64 octets into the transmission (also added into collision count).

dot3StatsExcessiveCollisions

(Not supported by E-Series or G-Series) Number of frames where transmissions failed because of excessive collisions.

dot3StatsCarrierSenseErrors

(G-Series only) The number of transmission errors on a particular interface that are not otherwise counted.

dot3StatsSQETestErrors

(G-Series only) A count of times that the SQE TEST ERROR message is generated by the physical signaling sublayer (PLS) sublayer for a particular interface.

etherStatsBroadcastPkts

The total number of good packets received that were directed to the broadcast address. This does not include multicast packets.

etherStatsCollisions

An estimate of the total number of collisions on this Ethernet segment. The value returned depends on the location of the RMON probe. Section 8.2.1.3 (10Base5) and Section 10.3.1.3 (10Base2) of IEEE 802.3 state that a station must detect a collision in the receive mode, if three or more stations are transmitting simultaneously. A repeater port must detect a collision when two or more stations are transmitting simultaneously. Thus, a probe placed on a repeater port could record more collisions than a probe connected to a station on the same segment.

Probe location plays a much smaller role when considering 10BaseT. Section 14.2.1.4 (10BaseT) of IEEE 802.3 defines a collision as the simultaneous presence of signals on the DO and RD circuits (transmitting and receiving at the same time). A 10BaseT station can only detect collisions when it is transmitting. Thus, probes placed on a station and a repeater should report the same number of collisions.

An RMON probe inside a repeater should report collisions between the repeater and one or more other hosts (transmit collisions as defined by IEEE 802.3k) plus receiver collisions observed on any coax segments to which the repeater is connected.

etherStatsCollisionFrames

An estimate of the total number of collisions on this Ethernet segment. The value returned depends on the location of the RMON probe. Section 8.2.1.3 (10Base5) and Section 10.3.1.3 (10Base2) of IEEE 802.3 state that a station must detect a collision in the receive mode, if three or more stations are transmitting simultaneously. A repeater port must detect a collision when two or more stations are transmitting simultaneously. Thus, a probe placed on a repeater port could record more collisions than a probe connected to a station on the same segment.

Probe location plays a much smaller role when considering 10BaseT. Section 14.2.1.4 (10BaseT) of IEEE 802.3 defines a collision as the simultaneous presence of signals on the DO and RD circuits (transmitting and receiving at the same time). A 10BaseT station can only detect collisions when it is transmitting. Thus, probes placed on a station and a repeater should report the same number of collisions.

An RMON probe inside a repeater should report collisions between the repeater and one or more other hosts (transmit collisions as defined by IEEE 802.3k) plus receiver collisions observed on any coax segments to which the repeater is connected.

etherStatsDropEvents

The total number of events in which packets were dropped by the probe due to lack of resources. This number is not necessarily the number of packets dropped; it is just the number of times this condition has been detected.

etherStatsJabbers

Total number of octets of data (including bad packets) received on the network.

etherStatsMulticastPkts

The total number of good packets received that were directed to a multicast address. This number does not include packets directed to the broadcast.

etherStatsUndersizePkts

Number of packets received with a length less than 64 octets.

etherStatsFragments

Total number of packets that are not an integral number of octets or have a bad FCS, and that are less than 64 octets long.

etherStatsPkts64Octets

Total number of packets received (including error packets) that were 64 octets in length.

etherStatsPkts65to127Octets

Total number of packets received (including error packets) that were 65 to 172 octets in length.

etherStatsPkts128to255Octets

Total number of packets received (including error packets) that were 128 to 255 octets in length.

etherStatsPkts256to511Octets

Total number of packets received (including error packets) that were 256 to 511 octets in length.

etherStatsPkts512to1023Octets

Total number of packets received (including error packets) that were 512 to 1023 octets in length.

etherStatsPkts1024to1518Octets

Total number of packets received (including error packets) that were 1024 to 1518 octets in length.

etherStatsJabbers

Total number of packets longer than 1518 octets that were not an integral number of octets or had a bad FCS.

etherStatsCollisions

Best estimate of the total number of collisions on this segment.

etherStatsCollisionFrames

Best estimate of the total number of frame collisions on this segment.

etherStatsCRCAlignErrors

Total number of packets with a length between 64 and 1518 octets, inclusive, that had a bad FCS or were not an integral number of octets in length.

receivePauseFrames

(G-Series only) The number of received IEEE 802.x pause frames.

transmitPauseFrames

(G-Series only) The number of transmitted IEEE 802.x pause frames.

receivePktsDroppedInternalCongestion

(G-Series only) The number of received framed dropped due to frame buffer overflow as well as other reasons.

transmitPktsDroppedInternalCongestion

(G-Series only) The number of frames dropped in the transmit direction due to frame buffer overflow as well as other reasons.

txTotalPkts

Total number of transmit packets.

rxTotalPkts

Total number of receive packets.

Step 8 From the Alarm Type drop-down list, indicate whether the event will be triggered by the rising threshold, falling threshold, or both the rising and falling thresholds.

Step 9 From the Sample Type drop-down list,choose either Relative or Absolute. Relative restricts the threshold to use the number of occurrences in the user-set sample period. Absolute sets the threshold to use the total number of occurrences, regardless of time period.

Step 10 Type in an appropriate number of seconds in the Sample Period field.

Step 11 Type in the appropriate number of occurrences in the Rising Threshold field.

For a rising type of alarm, the measured value must move from below the falling threshold to above the rising threshold. For example, if a network is running below a falling threshold of 400 collisions every 15 seconds and a problem causes 1001 collisions in 15 seconds, the excess collisions trigger an alarm.

Step 12 Enter the appropriate number of occurrences in the Falling Threshold field. In most cases a falling threshold is set lower than the rising threshold.

A falling threshold is the counterpart to a rising threshold. When the number of occurrences is above the rising threshold and then drops below a falling threshold, it resets the rising threshold. For example, when the network problem that caused 1001 collisions in 15 seconds subsides and creates only 799 collisions in 15 seconds, occurrences fall below a falling threshold of 800 collisions. This resets the rising threshold so that if network collisions again spike over a 1000 per 15 second period, an event again triggers when the rising threshold is crossed. An event is triggered only the first time a rising threshold is exceeded (otherwise a single network problem might cause a rising threshold to be exceeded multiple times and cause a flood of events).

Step 13 Click OK to complete the procedure.

Step 14 Return to your originating procedure (NTP).

DLP-D442 Preprovision a Slot

Purpose

This task preprovisions a card slot in CTC before you physically install the card in the ONS 15454 SDH.

Step 1 In node view, right-click the empty slot where you will later install a card.

Step 2 From the Add Card shortcut menu, choose the card type that will be installed. Only cards that can be installed in the slot appear in the Add Card shortcut menu.

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

Step 3 Return to your originating procedure (NTP).

DLP-D457 Refresh E-Series and G-Series Ethernet PM Counts

Purpose

This task changes the window view to display specified E-Series and G-Series Ethernet PM counts in time intervals depending on the interval option selected.

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

If a complete count over the selected interval is not possible, the value appears with a yellow background. For example, if you selected the 1-day interval, 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-D458 Monitor PM Counts for a Selected Signal

Purpose

This task uses signal-type selections to monitor near-end or far-end PM counts for specific signals on a 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.

Different port and signal-type drop-down lists appear depending on the card type and the circuit type. The appropriate signal types (DS3i, E1, E3, STM-N line, and VC4) appear based on the selected card. For example, the STM16 LH AS 1550 card lists the line and VC4 PM parameters as signal types, which enables you to select both the line and the VC4 within the specified line.

Step 3 In the signal type drop-down lists, click one of the following options:

•Port: n (card port number)

•Line: n (STM line number)

•VC4: n (VC path number within the STM line)

Figure 21-10 shows the Line drop-down list in the Performance window for an STM-16 card.

Figure 21-10 Line Drop-down List for an STM-16 Card

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

Caution Pressing the Clear button can mask problems if used incorrectly. This button is commonly used for testing purposes. After pressing this button, the current bin is marked invalid. Also note that the unavailable seconds (UAS) state is not cleared if you were counting UAS; therefore, this count could be unreliable when UAS is no longer incrementing.

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 Clear.

Step 4 In the Clear Statistics dialog box, choose one of the following options:

•Displayed statistics—Clearing the displayed statistics erases from the card and the window all PM counts associated with the current combination of statistics on the selected port. This means that the selected time interval, direction, and signal type counts are erased from the card and the window.

•All statistics for port x—Clearing all statistics for port x erases from the card and the window all PM counts associated with all combinations of the statistics on the selected port. This means that all time intervals, directions, and signal type counts are erased from the card and the window.

•All statistics for card—Clearing all statistics for a card erases from the card and the window all PM counts for all ports.

Step 5 Choose OK to clear the selected statistics.

Step 6 Verify that the selected PM counts have been cleared.

Step 7 Return to your originating procedure (NTP).

DLP-D460 View FC_MR-4 Statistics PM Parameters

Purpose

This task enables you to view current statistical PM counts on an FC_MR-4 card and port to detect possible performance problems.

Step 4 View the PM parameter names that appear in the Param column. The current PM parameter values appear in the port number columns. For PM parameter definitions, refer to the "Performance Monitoring" chapter in the Cisco ONS 15454 SDH Reference Manual.

Step 5 Return to your originating procedure (NTP).

DLP-D461 View FC_MR-4 Utilization PM Parameters

Purpose

This task enables you to view line utilization PM counts on an FC_MR-4 card and port to detect possible performance problems.

Step 5 From the Port drop-down list, choose the applicable port on the FC_MR-4 card you selected.

Step 6 From the Variable drop-down list, choose the variable. See Table 21-3 for a list of the FC_MR-4 threshold variables available in this field in line rate mode. See Table 21-4 for a list of the FC_MR-4 threshold variables available in this fields in enhanced mode.

Total number of octets received on the interface, including framing octets.

ifInDiscards

The number of inbound packets that were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol.

iflnErrors

Number of inbound packets discarded because they contain errors.

ifOutOctets

Total number of transmitted octets, including framing packets.

ifOutDiscards

The number of outbound packets that were chosen to be discarded even though no errors had been detected to prevent their being transmitted.

fcIngressRxDistanceExtBuffers

The maximum number of GFP buffers that are available at the GFP receiver.

fcEgressTxDistanceExtBuffers

The number of GFP buffers that the GFP transmitter is allowed to transmit. Remote GFP receiver tells the GFP transmitter how many buffers it has available.

fcStatsLinkRecoveries

The number of times a link reset was initiated due to a GFP out of frame condition. This is only valid when link recovery is enabled and is not valid when distance extension is enabled.

fcStatsRxCredits

The maximum number of Fibre Channel credits that the Fibre Channel/fiber connectivity (FICON) link partner will allow the FCMR Fibre Channel/FICON transmitter to transmit (that is, the maximum number of frames the link partner can receive).

fcStatsTxCredits

The number of Fibre Channel credits that the FCMR Fibre Channel/ficon transmitter is left with. This is the number of frames that the Fibre Channel/FICON transmitter has available to send.

Note The Tx credits increment whenever a credit is received from the link partner, and decrement when a frame is sent.

fcStatsZeroTxCredits

A count that increments when the Fibre Channel/FICON Tx credits go from a nonzero value to zero.

fibreStatsInvalidOrderedSets

Received ordered sets that are not recognized as part of the defined Fibre Channel control words.

fibreStatsEncodingDispErrors

Received control words that cannot be decoded due to invalid disparity.

fibreStatsRxFramesTooLong

Received oversize Fibre Channel frames that are greater than 2148 including CRC.

fibreStatsRxFramesBadCRC

Received Fibre Channel frames with bad CRC.

fibreStatsRxFrames

Received total Fibre Channel frames.

fibreStatsRxOctets

Received total Fibre Channel data bytes within a frame.

fibreStatsTxFramesBadCRC

Transmitted Fibre Channel frames with bad CRC.

fibreStatsTxFrames

Transmitted total Fibre Channel frames.

fibreStatsTxOctets

Transmitted total Fibre Channel data bytes within a frame.

fibreStatsLinkResets

Total number of link resets initiated by FCMR port when link recovery port setting is enabled.

gfpStatsRxSBitErrors

Received GFP frames with single bit errors in the core header (these errors are correctable).

gfpStatsRxMBitErrors

Received GFP frames with multiple bit errors in the core header (these errors are not correctable).

Total number of superblock CRC errors with the receive transparent GFP frame. A transparent GFP frame has multiple superblocks which each contain Fibre Channel data.

8b10bInvalidOrderedSets

Total number of ordered sets not compliant to Gigabit Ethernet/Fibre Channel (GE/FC) standard.

8b10bStatsEncodingDispErrors

Total number of code groups that violate GE/FC disparity errors.

Step 7 From the Alarm Type drop-down list, indicate whether the event will be triggered by the rising threshold, falling threshold, or both the rising and falling thresholds.

Step 8 From the Sample Type drop-down list,choose either Relative or Absolute. Relative restricts the threshold to use the number of occurrences in the user-set sample period. Absolute sets the threshold to use the total number of occurrences, regardless of time period.

Step 9 Type in an appropriate number of seconds in the Sample Period field.

Step 10 Type in the appropriate number of occurrences in the Rising Threshold field.

For a rising type of alarm, the measured value must move from below the falling threshold to above the rising threshold. For example, if a network is running below a rising threshold of 1000 collisions every 15 seconds and a problem causes 1001 collisions in 15 seconds, the excess occurrences trigger an alarm.

Step 11 Enter the appropriate number of occurrences in the Falling Threshold field. In most cases, a falling threshold is set lower than the rising threshold.

A falling threshold is the counterpart to a rising threshold. When the number of occurrences is above the rising threshold and then drops below a falling threshold, it resets the rising threshold. For example, when the network problem that caused 1001 collisions in 15 seconds subsides and creates only 799 collisions in 15 seconds, occurrences fall below a falling threshold of 800 collisions. This resets the rising threshold so that if network collisions again spike over a 1000 per 15-second period, an event again triggers when the rising threshold is crossed. An event is triggered only the first time a rising threshold is exceeded (otherwise, a single network problem might cause a rising threshold to be exceeded multiple times and cause a flood of events).

Step 4 In the MS-SPRing Creation dialog box, set the MS-SPRing properties:

•Ring Type—Choose two-fiber.

•Speed—Choose the MS-SPRing speed: STM-4, STM-16, or STM-64. The speed must match the STM-N speed of the MS-SPRing trunk (span) cards.

Note If you are creating an STM-4 MS-SPRing and will eventually upgrade it to STM-16 or STM-64, use the single-port STM-4 cards (OC12 IR/STM4 SH 1310, OC12 IR/STM4 SH 1310, or OC12 IR/STM4 SH 1310). You cannot upgrade an MS-SPRing on a four-port STM-4 (OC12/STM4-4) because STM-16 and STM-64 cards are single-port cards.

•Ring Name—Assign a ring name. The name can be from 1 to 6 characters in length. Any alphanumeric character string is permissible, and upper and lower case letters can be combined. Do not use the character string "All" in either uppercase or lowercase letters; this is a TL1 keyword and will be rejected. Do not choose a name that is already assigned to another MS-SPRing.

•Reversion time—Set the amount of time that will pass before the traffic reverts to the original working path following a ring switch. The default is 5 minutes. Ring reversions can be set to Never.

Step 5 Click Next. If the network graphic appears, go to Step 6. If CTC determines that an MS-SPRing cannot be created, for example, not enough optical cards are installed or it finds circuits with SNCP selectors, a "Cannot Create MS-SPRing" message appears. If this occurs, complete the following steps:

a. Click OK.

b. In the Create MS-SPRing window, click Excluded Nodes. Review the information explaining why the MS-SPRing could not be created, then click OK.

c. Depending on the problem, click Back to start over or click Cancel to cancel the operation.

Step 6 In the network graphic, double-click an MS-SPRing span line. If the span line is DCC connected to other MS-SPRing cards constituting a complete ring, the lines turn blue and the Finish button appears. If the lines do not form a complete ring, double-click span lines until a complete ring is formed. When the ring is DCC connected, go to the next step.

Step 7 Click Finish. If the MS-SPRing window appears with the MS-SPRing you created, go to Step 8. If a "Cannot Create MS-SPRing" or "Error While Creating MS-SPRing" message appears:

a. Click OK.

b. In the Create MS-SPRing window, click Excluded Nodes. Review the information explaining why the MS-SPRing could not be created, then click OK.

c. Depending on the problem, click Back to start over or click Cancel to cancel the operation.

Note The numbers in parentheses after the node name are the MS-SPRing node IDs assigned by CTC. Every ONS 15454 SDH in an MS-SPRing is given a unique node ID, 0 through 31. To change it, complete the "DLP-D24 Change an MS-SPRing Node ID" task.

Step 9 Return to your originating procedure (NTP).

DLP-D469 Create a Two-Fiber MS-SPRing Manually

Purpose

This task creates a two-fiber MS-SPRing at each MS-SPRing-provisioned node without using the MS-SPRing wizard.

Step 4 In the Create MS-SPRing dialog box, set the MS-SPRing properties:

•Ring Type—Choose two-fiber.

•Ring Name—Assign a ring name. You must use the same ring name for each node in the MS-SPRing. Any alphanumeric character string is permissible, and uppercase and lowercase letters can be combined. Do not use the character string "All" in either upper or lower case letters; this is a TL1 keyword and will be rejected. Do not choose a name that is already assigned to another MS-SPRing.

•Node ID—Choose a Node ID from the drop-down list (0 through 31). The Node ID identifies the node to the MS-SPRing. Nodes in the same MS-SPRing must have unique Node IDs.

•Reversion time—Set the amount of time that will pass before the traffic reverts to the original working path. The default is 5 minutes. All nodes in an MS-SPRing must have the same reversion time setting.

•West Line—Assign the west MS-SPRing port for the node from the drop-down list.

•East Line—Assign the east MS-SPRing port for the node from the drop-down list.

Step 5 Click OK.

Note Some or all of the following alarms will appear until all the MS-SPRing nodes are provisioned: E-W MISMATCH, RING MISMATCH, APSCIMP, APSDFLTK, and MS-SPRINGOSYNC. The alarms clear after you configure all of the nodes in the MS-SPRing.

Step 6 From the View menu, choose Go to Other Node.

Step 7 In the Select Node dialog box, choose the next node that you want to add to the MS-SPRing.

Step 8 Repeat Steps 1 through 7 at each node that you want to add to the MS-SPRing. When all nodes have been added, continue with Step 9.

Step 9 From the View menu, choose Go to Network View. After 10 to 15 seconds, verify the following:

Step 1 In the Circuit Routing Preferences area of the Unprotected to SNCP page, uncheck Route Automatically.

Step 2 Click Next. In the Route Review and Edit area, node icons appear for you to route the circuit. The circuit source node is selected. Green arrows pointing from the source node to other network nodes indicate spans that are available for routing the circuit.

Step 3 Click Finish.

Step 4 Return to your originating procedure (NTP).

DLP-D471 Automatically Route an SNCP Circuit for a Topology Upgrade

Purpose

This task creates an automatically routed SNCP circuit during a conversion from an unprotected point-to-point or linear ADM system to an SNCP.

Note This task requires the use of automatic routing. Automatic routing is not available if both the Automatic Circuit Routing NE default and the Network Circuit Automatic Routing Overridable NE default are set to FALSE. For a full description of these defaults see the "Network Element Defaults" appendix in the Cisco ONS 15454 SDH Reference Manual.

Step 1 In the Circuit Routing Preferences area of the Unprotected to SNCP page, check Route Automatically.

Step 2 Check the Review Route Before Creation check box if you want to review and edit the circuit route before the circuit is created.

Step 3 Choose one of the following:

•Nodal Diversity Required—Ensures that the primary and alternate paths within SNCP portions of the complete circuit path are nodally diverse.

•Nodal Diversity Desired—Specifies that node diversity is preferred, but if node diversity is not possible, CTC creates fiber-diverse paths for the SNCP portion of the complete circuit path.

•Link Diversity Only—Specifies that only fiber-diverse primary and alternate paths for SNCP portions of the complete circuit path are needed. The paths might be node-diverse, but CTC does not check for node diversity.

Step 4 If you selected Review Route Before Creation in Step 2, complete the following substeps. If not, continue with Step 5.

a. Click Next.

b. Review the circuit route. To add or delete a circuit span, choose a node on the circuit route. Blue arrows show the circuit route. Green arrows indicate spans that you can add. Click a span arrowhead, then click Include to include the span or Remove to remove the span.

Step 3 In the Login Node box, enter the ONS NE node name or IP address. (If the address was entered previously, you can choose it from the drop-down menu.)

Step 4 Select the CTC version you want to launch from the following choices in the drop-down menu:

•Same version as the login node: Select if you want to launch the same CTC version as the login node version, even if more recent versions of CTC are available in the cache.

•Latest version available: Select if you want to launch the latest CTC version available. If the cache has a newer CTC version than the login node, that CTC version will be used. Otherwise the same CTC version as the login node will be used.

•Version x.xx: Select if you want to launch a specific CTC version.

Note Cisco recommends that you always use the "Same version as the login node" unless the use of newer CTC versions is desired (for example, when CTC must manage a network containing mixed version NEs).

Note Because each CTC version requires particular JRE versions, the CTC Launcher will prompt the user for the location of a suitable JRE whenever a new CTC version is launched for the first time using a file chooser dialog (if a suitable JRE version is not known by the launcher yet). That JRE information is then saved in the user's preferences file. From the selection dialog, select any appropriate JRE directory.

After the JRE version is selected, the CTC will be launched. The required jar files will be downloaded into the new cache if they are missing. The CTC Login window will appear after a few seconds.

Step 7 Return to your originating procedure (NTP).

DLP-D475 Create a TL1 Tunnel Using the CTC Launcher

Purpose

This task creates a TL1 tunnel using the CTC Launcher, and the tunnel transports the TCP traffic to and from ONS ENEs through the OSI-based GNE.

•Far End TID—Enter the TID of the ONS ENE at the far end of the tunnel. The TID is the name entered in the Node Name field on the node view Provisioning > General tab.

•Host Name/IP Address—Enter the GNE DNS host name or IP address through which the tunnel will established. This is the third-party vendor GNE that is connected to an ONS node through an OSI DCC network. CTC uses TCP/IP over a DCN to reach the GNE. The GNE accepts TL1 connections from the network and can forward TL1 traffic to the end network elements (ENEs).

•Choose a port option:

–Use Default TL1 Port—Choose this option if you want to use the default TL1 port 3081 and 3082.

–Use Other TL1 Port—Choose this option if the GNE uses a different TL1 port. Enter the port number in the box next to the User Other TL1 Port radio button.

•TL1 Encoding Mode—Choose the TL1 encoding:

–LV + Binary Payload— TL1 messages are delimited by LV (length value) headers and TCP traffic is encapsulated in binary form. Cisco recommends this option because it is the most efficient encoding mode. However, you must verify that the GNE supports LV + Binary Payload encoding.

•Far End TID—Enter the TID of the ONS ENE at the far end of the tunnel. The ENE must be a Cisco ONS NE. The TID is the name entered in the Node Name field on the node view Provisioning > General tab.

•Host Name/IP Address—Enter the GNE DNS host name or IP address through which the tunnel will established. This is the third-party vendor GNE that is connected to an ONS NE with an OSI DCC. CTC uses TCP/IP over a DCN to reach the GNE. The GNE accepts TL1 connections from the network and can forward TL1 traffic to the ENEs.

•Choose a port option:

–Use Default TL1 Port—Choose this option if you want to use the GNE default TL1 port. TL1 uses standard ports, such as 3081 and 3082, unless custom TL1 ports are defined.

–Use Other TL1 Port—Choose this option if the GNE uses a different TL1 port. Enter the port number in the box next to the User Other TL1 Port radio button.

•TL1 Encoding Mode—Choose the TL1 encoding:

–LV + Binary Payload— TL1 messages are delimited by LV (length value) headers and TCP traffic is encapsulated in binary form. Cisco recommends this option because it is the most efficient. However, you must verify that the GNE supports LV + Binary Payload encoding.

The Target ID of the NE at the far end of the tunnel. This NE is an ONS NE. It is typically connected with an OSI DCC to a third-party vender GNE. CTC manages this NE.

GNE Host

The GNE host or IP address through which the tunnel is established. This is generally a third-party vendor GNE that is connected to an ONS NE with an OSI DCC. CTC uses TCP/IP over a DCN to reach the GNE. The GNE accepts TL1 connections from the network and can forward TL1 traffic to the ENEs.

Port

The TCP port number where the GNE accepts TL1 connections coming from the DCN. These port numbers are standard (such as 3081 and 3082) unless custom port numbers are provisioned on the GNE.

•Raw—TL1 messages are delimited by semi-columns only, and the TCP traffic is encapsulated using Base64 encoding.

GNE TID

The GNE TID is shown when the GNE requires a local TL1 ACT-USER login before forwarding TL1 traffic to ENEs. If present, CTC asks the user for the ACT-USER user ID and password when the tunnel is opened.

State

Indicates the tunnel state:

OPEN—A tunnel is currently open and carrying TCP traffic.

RETRY PENDING—The TL1 connection carrying the tunnel has been disconnected and a retry to reconnect it is pending. (CTC automatically attempts to reconnect the tunnel at regular intervals. During that time all ENEs behind the tunnel are unreachable.)

(empty)—No tunnel is currently open.

Far End IP

The IP address of the ONS NE that is at the far end of the TL1 tunnel. This information is retrieved from the NE when the tunnel is established.

Sockets

The number of active TCP sockets that are multiplexed in the tunnel. This information is automatically updated in real time.

Retries

Indicates the number of times CTC tried to reopen a tunnel. If a network problem causes a tunnel to go down, CTC automatically tries to reopen it at regular intervals. This information is automatically updated in real time.

Rx Bytes

Shows the number of bytes of management traffic that were received over the tunnel. This information is automatically updated in real time.

Tx Bytes

Shows the number of bytes of management traffic that were transmitted over the tunnel. This information is automatically updated in real time.

•Use Default TL1 Port—Choose this option if you want to use the GNE default TL1 port. TL1 uses standard ports, such as 3081 and 3082, unless custom TL1 ports are defined.

•Use Other TL1 Port—Choose this option if the GNE uses a different TL1 port. Enter the port number in the box next to the User Other TL1 Port radio button.

•TL1 Encoding Mode—Choose the TL1 encoding:

–LV + Binary Payload— TL1 messages are delimited by LV (length value) headers and TCP traffic is encapsulated in binary form. Cisco recommends this option because it is the most efficient. However, you must verify that the GNE supports LV + Binary Payload encoding.

Step 2 In the TL1 Tunnels window, click the tunnel you want to delete.

Step 3 Click Delete.

Step 4 In the confirmation dialog box, click OK.

Step 5 Return to your originating procedure (NTP).

DLP-D480 Install or Reinstall the CTC JAR Files

Purpose

This task installs or reinstalls the CTC JAR files into the CTC cache directory on your PC. This is useful when you are using a new CTC version and want to install or reinstall the CTC JAR files without logging into a node or using the StartCTC application (StartCTC.exe).

Note The CTC cache installer is also available on Cisco.com. If you are downloading the SetupCtc-version.exe (where version is the release version, for example, SetupCtc-085000.exe) file from Cisco.com, skip Step 1 and Step 2.

Step 3 Copy the SetupCtc-version.exe file to your local hard drive. Use any location that is convenient for you to access, such as the Windows desktop. Ensure that you have enough disk space to copy and extract the SetupCtc-version.exe file.

Step 4 Double-click the SetupCtc-version.exe file. This creates a directory named SetupCtc-version (at the same location), which contains the LDCACHE.exe file and other CTC files.

Step 5 Double-click the LDCACHE.exe file to install or reinstall the new CTC JAR files into the CTC cache directory on your PC.

Step 6 Return to your originating procedure (NTP).

DLP-D481 Configuring Windows Vista to Support CTC

Purpose

This task describes the configurations that must be done in Windows Vista operating system prior to launching CTC.

Note Performa full installation of Windows Vista operating system on your computer. If Windows Vista is installed through operating system upgrade, then CTC will not work. Refer to the manufacturer's user guide for instructions on how to install Windows Vista.

Step 3 Change the Admin State of the port to Locked,Maintenance or Locked,Disabled for the corresponding port number.

Step 4 In the Line area, enable the link integrity soak timer feature by unchecking the check box in the Link Integrity Disable column for the corresponding port number. The Link Integrity Disable option is available only for CE-1000 card.

Step 5 Enter the desired link integrity soak duration in the Link Integrity Timer column for the corresponding port number. Enter the link integrity soak duration in the range between 200 and 5000 ms, in multiples of 100 ms.

Step 3 In the Create Views dialog box, enter the following information:

•Name—Name of the view.

•Subtree OID—The MIB subtree which, when combined with the mask, defines the family of subtrees.

•Bit Mask—A family of view subtrees. Each bit in the bit mask corresponds to a sub-identifier of the subtree OID.

•Type—Select the view type. Options are Include and Exclude. Type defines whether the family of subtrees that are defined by the subtree OID and the bit mask combination are included or excluded from the notification filter.

Step 4 Click OK to save the information.

Step 5 Return to your originating procedure (NTP).

DLP-D485 Create Group Access

Purpose

This procedure creates a user group and configures the access parameters for the users in the group.

Step 3 In the Configure SNMPv3 Trap dialog box, enter the following information:

•Target Address—Target to which the traps should be sent. Use an IPv4 or an IPv6 address.

•UDP Port—UDP port number that the host uses. Default value is 162.

•User Name—Specify the name of the user on the host that connects to the agent.

•Security Level—Select one of the following options:

–noAuthNoPriv—Uses a user name match for authentication.

–AuthNoPriv—Provides authentication based on the HMAC-MD5 or HMAC-SHA algorithms.

–AuthPriv—Provides authentication based on the HMAC-MD5 or HMAC-SHA algorithms. Provides DES 56-bit encryption based on the CBC-DES (DES-56) standard, in addition to authentication.

•Filter Profile—Select this check box and enter the filter profile name. Traps are sent only if you provide a filter profile name and create a notification filter. This field is optional and traps can also be sent without providing a filter profile and create a notification filter. For more information, see "DLP-D488 Create Notification Filters" task.

•Proxy Traps Only—If selected, forwards only proxy traps from the ENE. Traps from this node are not sent to the trap destination identified by this entry.

•Proxy Tags—Specify a list of tags. The tag list is needed on a GNE only if an ENE needs to send traps to the trap destination identified by this entry, and wants to use the GNE as the proxy.

Step 3 In the Create Notify dialog box, enter the following information:

•Filter Profile Name—Specify a name for the filter.

•Subtree OID—The MIB subtree which, when combined with the mask, defines the family of subtrees.

•Bit Mask—A family of view subtrees. Each bit in the bit mask corresponds to a sub-identifier of the subtree OID.

•View Type—Select the view type. Options are Include and Exclude. Type defines whether the family of subtrees that are defined by the subtree OID and the bit mask combination are included or excluded from the notification filter.

•Select the GNE to be used as the SNMPv3 proxy server from the drop-down list.

•Select the Enable IPv6 Target/Trap check box if the nodes and the NMS stations are on an IPv6 network.

Step 3 In the SNMPv3 Proxy Forwarder Table area, click Auto Create.

Step 4 In the Automatic Configuration of SNMPv3 Proxy Forwarder dialog box, enter the following information:

•Proxy Type—Select the type of proxies to be forwarded. The options are Read and Write.

•Security Level—Select the security level for the incoming requests that are to be forwarded. The options are:

–noAuthNoPriv—Uses a username match for authentication.

–AuthNoPriv—Provides authentication based on the HMAC-MD5 or HMAC-SHA algorithms.

–AuthPriv—Provides authentication based on the HMAC-MD5 or HMAC-SHA algorithms. Provides DES 56-bit encryption based on the CBC-DES (DES-56) standard, in addition to authentication.

•Target Address List—Select the proxy destination.

•Local User Name—Select the user name from the list of users.

Note When you configure SNMPv3 Proxy Forwarder Table automatically, the default_group is used on the ENE. The default_group does not have write access. To enable write access and allow SNMP sets, you need to edit the default_group on ENE.

Step 5 Click OK to save the settings.

Step 6 Return to your originating procedure (NTP).

DLP-D491 Manually Configure the SNMPv3 Proxy Trap Forwarder Table

Purpose

This procedure creates an entry in the SNMPv3 Proxy Trap Forwarder Table.

•Remote Trap Source—Select the IP address from which the traps are sent. If the IP address is not listed, enter the IP address manually.

•Context Engine ID—Specify the context engine ID of the ENE from which traps need to be forwarded. This field is automatically populated if the source of trap is selected. If the source of trap is not specified, you need to manually enter the context engine ID.

•Target Tag—Specify the tag name. The tag identifies the list of NMS that should receive the forwarded traps. Traps are forwarded to all GNE Trap destinations whose proxy tags list contains this tag.

•Remote User Details

–User Name—Specify the user name.

–Security Level—Select the security level for the user. The options are noAuthNoPriv, AuthNoPriv, and AuthPriv.

•Authentication—Select the authentication algorithm.

–Protocol—Select the authentication algorithm you want to use. The options are NONE, MD5, and SHA. Default is None.

–Password—Enter the password if you select MD5 or SHA.

•Privacy—Enables the host to encrypt the contents of the message that is sent to the agent.

–Protocol—Select NONE or DES as the privacy authentication algorithm. Encryption is disabled if NONE is selected.

–Password—Enter the password if you select DES. The password should not exceed 64 characters.

Step 1 In node view, double-click the ML-Series card graphic to open the card.

Step 2 Click the Provisioning > Ether Ports tabs.

Step 3 For each port, provision the following parameters:

•Port—The fixed number identifier for the specific port.

•Port Name—Configurable 12 character alphanumeric identifier for the port.

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

•Admin State—Configured port state, which is administratively active or inactive.

•PSAS (Pre Service Alarm Suppress)—A check indicates alarm suppression is set on the port for the time designated in the Soak Time column.

•Soak Time—Desired soak time in hours and minutes. Use this column when you have checked PSAS to suppress alarms. Once the port detects a signal, the countdown begins for the designated soak time. Soak time hours can be set from 0 to 48. Soak time minutes can be set from 0 to 45 in 15 minute increments.

•Link State—Status between signaling points at port and attached device.

Step 1 In node view, double-click the ML-Series card graphic to open the card.

Step 2 Click the Provisioning > POS Ports tabs.

Step 3 For each port, provision the following parameters:

•Port—The fixed number identifier for the specific port.

•Port Name—The configurable 12 character alphanumeric identifier for the port.

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

•Admin State—The configured port state, which is administratively active or inactive. Possible values are UP and DOWN. For the UP value to appear, a POS port must be both administratively active and have a SONET/SDH circuit provisioned.

•PSAS—A check indicates alarm suppression is set on the port for the time designated in the Soak Time column.

•Soak Time—The desired soak time in hours and minutes. Use this column when you have checked PSAS to suppress alarms. Once the port detects a signal, the countdown begins for the designated soak time. Soak time hours can be set from 0 to 48. Soak time minutes can be set from 0 to 45 in 15 minute increments.

•Link State—The status between signaling points at port and attached device. Possible values are UP and DOWN.