MK F5DWB

Passport 7400, 8700, 15000
Operations and Maintenance Guide
241-5701-605
Passport 7400, 8700, 15000
Publication: 241-5701-605 Document status: Standard Document version: 2.0S1 Document date: July 2000
Copyright 2000 Nortel Networks. All Rights Reserved. Printed in Canada NORTEL, NORTEL NETWORKS, the globemark design, the NORTEL NETWORKS corporate logo, DPN, and PASSPORT are trademarks of Nortel Networks. VT100 is a trademark of Digital Equipment Corporation. UNIX is a trademark licensed exclusively through X/Open Company Ltd. Sun, SunOS, and Solaris are trademarks of Sun Microsystems, Inc. HP-UX is a trademark of Hewlett-Packard Company.
Publication history
July 2000
2.0S1 Standard General availability. Contains information on Passport 7400, 8700, 15000 for the PCR 2.0 GA release.
Passport 7400, 8700, 15000 Operations and Maintenance Guide
2.0S1
Publication history
241-5701-605 2.0S1
Contents
About this document
Who should read this document and why 17 What you need to know 17 How this document is organized 19 Whats new in this document 20 Text conventions 20 Related documents 21 How to get more help 22
17
Chapter 1 General information

Logging into a Passport node 23 Entering user information 24 Using telnet on a Passport node 24 Passports text interface 26 Operational mode and provisional mode 27 Commands 28 Alarms 30 Keyboard shortcuts 31 Passport provisioning views 32 Changing the conguration using the provisioning system 33 Entering provisioning changes 33 Activating and committing provisioning changes 35 Provisioning for immediate activation 39 Displaying saved views on the disk 43 Copying a component conguration to another node 43
23
2.0S1
Contents
Chapter 2 Configuring and maintaining Passport
47
Initial setup process 48 Conguring node security 48 Conguring the basic node 49 Conguring the data collection system 49 Regularly scheduled activities 50 Working with the alarm/BITS card 52 Replacing an alarm/BITS card 53 Working with the node 53 Displaying the backplane type 54 Conguring the node identication 54 Displaying the node identication 56 Conguring general service parameters 56 Working with date and time 56 Reference time, network time, and module time 57 Conguring the time in a network 57 Conguring the time on a node 59 Working with the fabric card on a Passport 15000 64 Conguring the fabric card component 65 Locking and unlocking a fabric card 65 Displaying the operating mode of the fabric cards 66 Displaying the status of a fabric card 67 Working with the bus on a Passport 7400 or Passport 8700 series switch 67 Locking and unlocking a bus 68 Displaying the bus operating mode 69 Displaying the status of a bus 69 Enabling and disabling automatic bus clock source testing 70 Displaying the status of the bus clock source 70 Manually testing the bus clock source 72 Working with processor cards 72 Conguring a new processor card 74 Displaying the card type in a given slot 75 Displaying information about daughter cards on a Passport 7400 or
241-5701-605 2.0S1
Contents 9
Passport 8700 series switch 76 Displaying the memory capacity of a processor card 77 Locking a processor card 77 Unlocking a processor card 78 Reinitializing a processor card 79 Working with equipment protection of electrical interface on Passport 80 Working with line protection of optical interfaces on Passport 7400 or Passport 8700 80 Working with line protection of optical interface FPs on Passport 15000 83 Working with line and equipment protection of optical interfaces on Passport 15000 84 Working with control processors 87 Conguring the OAM Ethernet port 89 Changing the switchover behavior of the OAM Ethernet port 91 Changing the statistics gathered from the OAM Ethernet port 92 Changing the line speed of the OAM Ethernet port on CP3 control processors 92 Changing the duplex mode of the OAM Ethernet port on CP3 control processors 93 Specifying a static route to connect to the OAM Ethernet port 93 Displaying information about the OAM Ethernet port 94 Disabling and enabling hot standby for CP switchover 94 Adding a spare control processor to a single-CP node 95 Removing a spare control processor 97 Replacing a control processor in a single-CP node 99 Replacing a control processor in a two-CP node 105 Upgrading a CP2 control processor to a CP3 control processor in a single-CP node 106 Upgrading a CP2 control processor to a CP3 control processor in a two-CP node 107 Downgrading a CP3 control processor to a CP2 control processor 110 Working with logical processors 110 Adding a logical processor type 113
2.0S1
10
Contents
Conguring the software features of an LPT 114 Adding a logical processor 116 Changing the LPT used by a logical processor 118 Deleting a logical processor 119 Displaying the status of a logical processor 120 Displaying CP switchover behavior of a logical processor 121 Temporarily disabling a logical processor 122 Re-enabling logical processors 123 Switching between active and standby processor cards 124 Working with the le system 125 File system restrictions 125 Disk full conditions 126 Displaying information about the le system 127 Synchronizing disks 127 Changing the volume name of a disk 128 Formatting a disk 129 Working with the data collection system 130 Changing agent queue sizes 131 Displaying data collection queue statistics 133 Conguring the spooling option 134 Conguring the maximum number of closed spooling les 136 Displaying the names of the spooling les 138 Creating a new spooling le 139
Chapter 3 Configuring network clock synchronization

Conguration basics for network clock synchronization 141 Notes on clocking for V.35 and X.25 function processors 144 Notes on clocking for Passport 15000 145 Displaying the current source of timing 145 Conguring ports to provide a line timing source 145 Conguring an external timing source on a Passport 15000 146 Activating network synchronization 147 Removing a reference 147 Setting a component to free run if previously congured with references 148
241-5701-605 2.0S1
141
Contents 11
Conguration for specic function processors 148 Conguring network clock synchronization for DS1 or E1 function processor 148 Conguring network clock synchronization for DS3 or E3 function processor 149 Conguring network clock synchronization for V35 or X21 control processor 149 Conguring network clock synchronization for voice or MVP/MVP-E function processors 150 Example of conguring an external clock source 151 Two-node network (Node A commands) 152 Two-node network with an external clock source (Node B commands) 153 Congure clocking with multiple references 154
Chapter 4 Troubleshooting
155
Troubleshooting process 156 Identifying the problem 156 Determining the cause 156 Resolving the problem 156 Getting troubleshooting information 157 Alarm data 157 Displaying the OSI states of a component 157 Performing diagnostic tests 158 Troubleshooting the node 158 Determining why the node is out of service 159 Troubleshooting the fabric card on a Passport 15000 159 Testing a fabric card 160 Interpreting fabric card test results 161 Troubleshooting the bus on a Passport 7400 or Passport 8700 series switch 166 Testing a bus 167 Interpreting bus test results 168 Troubleshooting function processors 174 Methods for detecting function processor problems 177
2.0S1
12
Contents
Determining why a function processor does not load software 181 Determining the cause of a function processor crash 182 Collecting diagnostic information 183 Troubleshooting control processors 184 Determining why a control processor does not load 189 Determining why the standby control processor does not load 189 Determining the cause of a control processor crash 190 Troubleshooting the OAM Ethernet port 191 Types of OAM Ethernet port tests 192 Testing the OAM Ethernet port 192 Troubleshooting the le system 194 Determining why a le cannot be saved 195 Determining why the le system is not operational 196 Testing a disk 197 Interpreting disk test results 200 Troubleshooting the data collection system 201
Chapter 5 Statistics
Enabling statistics collection 203 Displaying statistics collection information 205
203
Chapter 6 Accounting
Conguring accounting 207 Viewing accounting data 208 Conguring a time-of-day accounting schedule 208
207
Chapter 7 Security
User administration 211 Adding a new user 212 Copying an existing userID for a new user 214 Changing a password 215 Secure method for setting a password 216 Changing user attributes 218
211
241-5701-605 2.0S1
Contents 13
Deleting a userID 218 Controlling user sessions 219 Displaying the number of user sessions 219 Displaying users 220 Restricting access through a specic interface 220 Terminating a user session 220 Immediately terminating multiple user sessions 221 Releasing a locked interface 222 Enabling and disabling password encryption for telnet sessions 222 Conguring authorized IP access 223
Appendix OSI states
225
Data collection system component states 226 File system component states 226 Network management interface system component states 228 Port management system component states 229 Framer component states 232 Processor card component states 233 Fabric card component states for the Passport 15000 235 Bus component states for the Passport 7400 or Passport 8700 series switch 237
2.0S1
14 Contents
List of gures
Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Using telnet on a Passport node 25 Sample command and response 29 Sample syntax error 30 Alarm format 30 Flowchart for entering provisioning changes 34 Flowchart for activating provisioning changes 37 Flowchart for immediate provisioning 40 Flowchart for using partial views 44 Sample relationship between LPTs, LPs, and processor cards 113 Components and attributes used for network clocking synchronization 142 Example of a V35/X21 two-node network 144 Example: selecting a V35 or X21 port as a reference for the CP 150 Example of a two-node network 151 Example: results of Node A commands 153 Example: results of Node B command 154
241-5701-605 2.0S1
Contents 15
List of tables
Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14 Table 15 Table 16 Table 17 Table 18 Table 19 Table 20 Table 21 Table 22 Table 23 Table 24 Table 25 Table 26 Table 27 Table 28 Table 29 Table 30 Table 31 Table 32 Table 33 Keyboard shortcuts 31 Regularly scheduled node activities 50 Regularly scheduled hardware activities 51 Interpreting bus clock source status 71 Troubleshooting node outage problems 159 Fabric card test result attributes and uses 162 Interpreting fabric card test results 164 Bus test result attributes and uses 169 Interpreting bus test results 171 Troubleshooting function processor problems 175 Methods for detecting function processor problems 178 LED status display 180 Troubleshooting control processor problems 185 Troubleshooting file system problems 194 Disk test results 200 Troubleshooting problems with the data collection system 201 Spooler component state combination 226 FileSystem component state combination 227 Disk component state combination 227 Disk Test component state combination 228 FTP, local, FMIP, or telnet manager component state combination 228 Port Channel component state combination 229 Port Test component state combination 230 Passport 7400 or Passport 8700 series Aps component state combination 231 Passport 15000 Laps component state combination 231 OamEthernet port state combination 232 Control and function processor Framer component state combination 233 Card component state combination 233 LogicalProcessor component state combination 234 Card test component state combination 234 Fabric card component state combination 235 Fabric card test component state combination 236 Fabric port component state combination 237
2.0S1
16 Contents
Table 34 Table 35 Table 36
Bus component state combination 238 BusTest component state combination 238 BusTap component state combination 239
241-5701-605 2.0S1
17
About this document

This document, 241-5701-605 Passport 7400, 8700, 15000 Operations and Maintenance Guide, explains how to operate and maintain a Passport node or network through a text interface device such as a VT100 terminal. The following topics are discussed in this section: Who should read this document and why (page 17) What you need to know (page 17) How this document is organized (page 19) Whats new in this document (page 20) Text conventions (page 20) Related documents (page 21) How to get more help (page 22)
Who should read this document and why

This guide is for persons who operate, administer, or maintain Passport.
What you need to know

This guide assumes that you understand Passport and DPN-100 architecture and operation. If your network incorporates a call server resource module (CSRM), make sure you are familiar with DPN-100. You also require basic UNIX knowledge.
2.0S1
18
About this document
You can acquire product knowledge by reading 241-1501-030 Passport 15000 Overview or 241-5701-030 Passport 7400, 8700 Overview. Before you operate and maintain Passport, make sure you understand the following: Passport concepts Passport hardware and software Passport installation, commissioning, and provisioning Passport-to-Passport interworking Passport-to-DPN-100 interworking (applicable to Passport 7400 or Passport 8700 series only) DPN-100 concepts routing, trunking, and addressing network installation, provisioning, operation, and maintenance service protocols UNIX UNIX workstations UNIX operating system, its facilities and commands standard network operations and maintenance activities Network Management System (NMS) workstation concepts
Before you can use the procedures described in this document, the Passport node must be installed and connected to the network as described in the following documents: 241-1501-210 Passport 15000 Hardware Installation Guide or 241-5701-210 Passport 7400, 8700 Hardware Installation Guide 241-5701-270 Passport 7400, 8700, 15000 Software Installation Guide
Also, you must set up either a text interface device or a network management workstation. See 241-1501-210 Passport 15000 Hardware Installation Guide or 241-5701-210 Passport 7400, 8700 Hardware Installation Guide for details on how to connect a text interface device.
241-5701-605 2.0S1
About this document 19
Except where noted, this guide provides procedures for operators working with Passport through either a VT100 terminal or a terminal emulator. If you are using NMS, see 241-6001-023 NMS Architect for Passport User Guide.
How this document is organized

This document contains the following sections: General information (page 23). This section contains general information about operating and maintaining a Passport node. It includes information on Passports text interface, provisioning views, and software installation. Conguring and maintaining Passport (page 47) This section contains procedures for conguring and maintaining the parts of your Passport node. Conguring network clock synchronization (page 141) This section contains conguration considerations and procedures for clocking in a Passport network. Troubleshooting (page 155) This section contains procedures for troubleshooting the parts of your Passport node. Statistics (page 203) This section contains procedures related to the collection of statistics on your Passport node. Accounting (page 207) This section contains procedures for setting up accounting on your Passport node. Security (page 211) This section contains procedures for setting up security on your Passport node. It includes information on users and authorized access.
2.0S1
20
About this document
OSI states (page 225) This section contains OSI state combination tables for basic Passport components. These tables help you when troubleshooting.
You can nd more descriptive information on each of these areas in 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals.
Whats new in this document

There are no changes in this document for this release.
Text conventions
This document uses the following text conventions:
nonproportional spaced plain type
Nonproportional spaced plain type represents system generated text or text that appears on your screen.
nonproportional spaced bold type
Nonproportional spaced bold type represents words that you should type or that you should select on the screen. italics Statements that appear in italics in a procedure explain the results of a particular step and appear immediately following the step. Words that appear in italics in text are for naming. [optional_parameter] Words in square brackets represent optional parameters. The command can be entered with or without the words in the square brackets. <general_term> Words in angle brackets represent variables which are to be replaced with specic values.
241-5701-605 2.0S1
About this document 21
UPPERCASE, lowercase Passport commands are not case-sensitive and do not have to match commands and parameters exactly as shown in this document, with the exception of string options values (for example, le and directory names) and string attribute values.
| This symbol separates items from which you may select one; for example, ON|OFF indicates that you may specify ON or OFF. If you do not make a choice, a default ON is assumed.
... Three dots in a command indicate that the parameter may be repeated more than once in succession.
The term absolute pathname refers to the full specication of a path starting from the root directory. Absolute pathnames always begin with the slash ( / ) symbol. A relative pathname takes the current directory as its starting point, and starts with any alphanumeric character (other than /).
Related documents
This document is closely related to 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals. This document contains operations and maintenance procedures, while 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals contains operations and maintenance concepts. Another closely related document is 241-5701-050 Passport 7400, 8700, 15000 Commands. This document details the commands you use to operate and maintain Passport. For information on last minute updates, see the Passport 15000 Release Report or Passport 7400 Release Report, which you receive with each software release. For information on performance specications, see the Passport 15000 Engineering Notes and Guidelines.
Passport 7400, 8700, 15000 Operations and Maintenance Guide 2.0S1
22
About this document
How to get more help

For information on training, problem reporting, and technical support, see the Nortel Networks support services section in the product overview document.
241-5701-605 2.0S1
23
Chapter 1 General information

This chapter contains the following basic information you need to operate and maintain your Passport node: Logging into a Passport node (page 23) Passports text interface (page 26) Passport provisioning views (page 32) Changing the conguration using the provisioning system (page 33)
Logging into a Passport node

When you log into a Passport node, you are in Passports text interface where you can view alarms and enter commands. There are three ways to log into a Passport node: from the local VT100 terminal or VT100 terminal emulator from a telnet client (on a management workstation or another Passport node) from the Command Console in Network Management System (NMS)
When setting up your local VT100 or terminal emulator, make sure it is set to 9600 bits/s, 1 stop bit, no parity.
2.0S1
24 Chapter 1 General information
Regardless of how you log in, you must provide valid user information for that node. In some cases, the IP address of the workstation you are using must be on the valid IP address list for the node. For more information, see 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals. For more information on logging onto a Passport node, see the following: Entering user information (page 24) Using telnet on a Passport node on page 24
Entering user information

When you log onto a Passport node, you must provide user information consisting of a valid user ID and password. Passport allows three invalid login attempts. After three invalid attempts, you must wait one minute before attempting to login again.
1 2 Enter your user ID at the Enter login prompt. Enter a password at the Enter password prompt. You have now logged in to the Passport node.
Using telnet on a Passport node

When you log into a Passport node using telnet on a management workstation, Passport acts as a telnet server. The telnet server accepts up to eight incoming telnet connections. The Passport 7400 series switch can also act as a telnet client. It can make outgoing telnet connections to telnet servers. Since Passport can behave as both a telnet client and a server, you can use the telnet Vr command on a Passport node to connect to another Passport node. You can also use the telnet Vr command to connect to any device supporting standard telnet access. The Passport node or device must be accessible through a management or customer virtual router. The gure Using telnet on a Passport node on page 25 illustrates how you can use the telnet Vr command to connect from one Passport node to another. First you telnet to Passport 1 from a management workstation using a telnet client application. Once you are logged into the telnet server on Passport 1,
241-5701-605 2.0S1
Chapter 1 General information 25
you can use the telnet Vr command to establish a telnet connection to Passport 2. You are now using the telnet client on Passport 1 to connect to the telnet server on Passport 2.
Figure 1 Using telnet on a Passport node
telnet client
telnet server
management workstation
Passport 2 (Passport 15000) telnet server telnet client
Passport 1 (Passport 7400 series)
telnet connection IP connection
You can only use the telnet Vr command on a Passport node when: You have accessed the node through the telnet network management interface. The node has a properly congured virtual router. Your user ID is allowed outgoing telnet access. For information on setting outgoing telnet access, see Changing user attributes on page 218.
To successfully set up an outgoing telnet connection: The IP address of the device you are connecting to must be accessible through a management or customer virtual router on the node. In other words, the IP address must be within the address space of the specied virtual router. You must have a user ID and password for the remote device.
2.0S1
If you are connecting to another Passport node and that node has IP address checking enabled, the IP address of your node must be on the valid IP address list.
Connect to a Passport node or any other device supporting standard telnet access. telnet -ipAddress(<remoteAddress>) Vr/<n> where: <remoteAddress> is the IP address of the remote device to which you want to connect. <n> is the instance number of the virtual router that can access the IP address.
When prompted, enter a user ID and password for the remote device. If you are connected to another Passport node, the connection is transparent. Command responses and alarms appear on screen as if you had directly connected to the node from a management workstation. If you are uncertain which Passport node you are connected to, use the me command.
Passports text interface

In Passports text interface, you can enter commands to congure the node, control the state of system, and perform diagnostic tests. The text interface has two modes: provisioning and operational. In provisioning mode, you enter commands to congure the node. In operational mode, you enter commands to control the state of the system and to perform diagnostic tests. In both modes, you can view alarms, which indicate faults. The following sections describe the characteristics of Passports text interface: Operational mode and provisional mode (page 27) Commands (page 28) Alarms (page 30) Keyboard shortcuts (page 31)
241-5701-605 2.0S1
Operational mode and provisional mode

When you initially log into a Passport node, you are in operational mode. Passport uses the following command prompt when you are in operational mode:
#>
where: # is the current command number In operational mode, you work with operational components and attributes. In operational mode, you can list operational components and display operational attributes to determine the current operating parameters for the node control the state of parts of the node by locking and unlocking components set certain operational attributes and enter commands to perform diagnostic tests
To change from operational mode to provisioning mode, use the start Prov command. Only one user can be in provisioning mode at a time. Passport uses the following command prompt whenever you are in provisioning mode:
PROV #>
where: # is the current command number In provisioning mode, you work with the provisionable components and attributes which contain the current and future congurations of the node. You can add and delete components, and display and set provisionable attributes. You can also verify your changes and then activate them as the new node conguration. You end provisioning mode and return to operational mode using the end Prov command. For information on operational and provisionable attributes, see 241-5701-060 Passport 7400, 8700, 15000 Components.
2.0S1
Commands
There are four pieces of information for every command: command line component command response status line
Sample command and response (page 29) provides a sample command and all its associated information. The command line is where you enter a Passport command. The prompt for the command line changes depending on whether you are in operational mode (#>) or provisioning mode (PROV #>). In the example, the prompt indicates provisioning mode. For information on commands and their syntax, see 241-5701-050 Passport 7400, 8700, 15000 Commands. After you enter a command, Passport rst responds with the full name of the component affected by the command. In the example, the command affects the Shelf Card/0 component. Following the component name is the particular response of the command. Depending on the command, the response can be one line or pages of information. In the example, the command responds with the provisionable attributes of the Shelf Card/0 component. After the response is the status line. The status line reports the status of the command (ok or command failed) and the date and time (in the YYYY-MMDD HH:MM:SS.SS format).
241-5701-605 2.0S1
If the command is unsuccessful, the status line indicates that the command failed and the response provides details on why it failed. When a command fails because you enter it incorrectly, Passport replaces the command response with the syntax error information. Syntax error information contains the following two pieces of information: invalid syntax input
The gure Sample syntax error (page 30) provides a sample of an incorrectly entered command. The invalid syntax line describes the syntax error. The description has the incorrect part (for example, verb, component, or attribute) of the command in curly brackets ({}) followed by an explanation. In the example, the command contains the incorrect component name Cord (instead of Card). The invalid syntax line explains that Passport does not recognize the component name. The input line repeats the command you entered with curly brackets ({}) around the part of the command that Passport cannot interpret. In the example, the unrecognized word Cord has curly brackets around it.
Figure 2 Sample command and response command line component name response status line PROV 2> display Shelf Card/0 Shelf Card/0 cardType = CPeE configuredLPs = Lp/0 sparingConnection = notApplicable commentText = "" ok XXXX-09-24 15:39:54.95
2.0S1
30 Chapter 1 General information Figure 3 Sample syntax error 4> lock Shelf Cord/0 Shelf Invalid syntax: {component name} unexpected, value unrecognized. Input: lock Shelf {Cord}/0 command failed XXXX-09-24 15:42:24.12
Alarms
Whenever Passport detects an error or a signicant event, it displays an alarm on the text interface. The alarm contains information about the component detecting the problem or event, the state of the component when it generated the alarm, and a description of the condition. The gure Alarm format (page 30) illustrates the format of a Passport alarm displayed on a text interface device. For detailed information on the alarm format, see 241-5701-500 Passport 6400, 7400, 8700, 15000 Alarms.
Figure 4 Alarm format
<Component name>; <date> <time> <status> <severity> <type> <cause> <alarm index> ADMIN: <admin> OPER: <oper> USAGE: <usage> AVAIL: <avail> PROC: <proc> CNTRL: <control> ALARM: <alarms> STBY <stdby> UNKNW: <unknown> Id: <notifId> Rel: [<relatedComp1>; <relatedComp2>;...] [Com: <commentData>] [Op: <operatorData>] Int: <process id>; <filemane>; <linenumber>; <version> [<internalData>]
PPT 0025 001 AA
241-5701-605 2.0S1
Keyboard shortcuts
The text interface provides a set of keyboard shortcuts you can use in either provisioning or operational mode. The shortcuts allow you to edit the command line and control the display of command responses. The table Keyboard shortcuts (page 31) summarizes these shortcuts.
Table 1 Keyboard shortcuts Key Up Arrow and Down Arrow Description Recalls recently used commands for edit or reuse. Passport stores the last 10 commands in a queue. Each time you press the Up Arrow key, you step back through the command queue. The Down Arrow key steps forward through the command queue. Moves the cursor over the command without affecting the characters in the command. Deletes the character preceding the cursor. Deletes the character under the cursor. Moves the cursor to the beginning of the command line. Moves the cursor to the end of the command line. Moves the cursor back one character at a time. Inserts a paragraph return. Deletes text from the character under the cursor to the end of the command line. Moves the cursor down one line at a time. Moves the cursor up one line at a time. Sends the command to Passport for processing.
Left Arrow and Right Arrow Backspace or Delete Control-D Control-A Control-E Control-H Control-J or Control-M Control-K Control-N Control-P Return or Enter
(Sheet 1 of 2)
2.0S1
32 Chapter 1 General information Table 1 (continued) Keyboard shortcuts Key Control-S Description Suspends the response from a command. This shortcut is useful where a command response is longer than 24 lines. If you suspend output for a long period of time, the text interface discards some subsequent output. If the session is registered to display a data stream (alarm, SCN, log, or debug data), the session discards all the data generated while response is suspended. If you suspend a telnet interface for a long time and a large amount of subsequent output is queued, the underlying TCP connection can terminate, bringing down the telnet session. Control-Q Control-C Resumes suspended output. Cancels a response. One Control-C cancels only the current response, and does not affect other queued responses.
(Sheet 2 of 2)
Passport provisioning views

The provisional and operational parameters of your Passport node are stored in views. Passport has four types of views: current, edit, saved and committed. The current view contains the current conguration for the node. The edit view contains a potential new conguration. Saved views are views that have been saved to the le system. The committed view is a special saved view that a Passport node uses when it starts up. The current and edit views are held in memory; the saved and committed views are stored on the le system. For detailed information on these views, see 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals.
241-5701-605 2.0S1
Changing the conguration using the provisioning system

You must use the provisioning system to make changes to the conguration of your Passport. The provisioning system maintains an edit view, which represents a potential new conguration. After you have made changes to the edit view, you can activate it so that it becomes the current conguration, which is called the current view. In most cases, you do not want to activate conguration changes immediately after you enter them in the edit view. Some changes require your node to restart, which causes service outages. A new conguration can also create errors when you activate it. For these reasons, enter a number of conguration changes and then activate all of them during a scheduled service period. The following sections explain how to enter and activate your conguration changes: Entering provisioning changes (page 33) Activating and committing provisioning changes (page 35)
If you need to make immediate provisioning changes to isolate or correct network problems, see Provisioning for immediate activation (page 39). To check the names and characteristics of the saved views stored on disk, see Displaying saved views on the disk (page 43).
Entering provisioning changes

Only one user at a time can make provisioning changes. Passport stores any changes you make to the edit view for the next user making provisioning changes. To ensure that your changes are not lost, save the edit view before ending your provisioning session. The gure Flowchart for entering provisioning changes (page 34) illustrates the steps to follow when entering provisioning changes.
2.0S1
34 Chapter 1 General information Figure 5 Flowchart for entering provisioning changes
Start provisioning start Prov
Make changes add delete set
Verify the changes check Prov
Save the edit view save Prov
End provisioning end Prov

PPT 2702 001 AA
Enter provisioning mode. start Prov When you enter provisioning mode, Passport indicates the differences, if any, between the current and the edit view. Passport reports added and deleted components as well as changed attributes.
241-5701-605 2.0S1
Chapter 1 General information 35 2 If you want to discard any previous changes made to the edit view, copy the current view into the edit view. copy Prov The edit view and the current view are now identical. 3 Make changes to the edit view by adding and deleting components, and setting attribute values. add <component_name> delete <component_name> set <component_name> <attribute> <value> 4 Verify the provisioning changes you have made. check Prov Correct any errors before continuing, and then verify the provisioning changes again. You can speed up the verication by checking only components in the edit view that are different from those in the current view. check -changed Prov
Note: This command does not check the components that are dependent upon the changed components.
5 Save the edit view. save Prov 6 End the provisioning session. end Prov To activate the provisioning changes you have just entered, see Activating and committing provisioning changes (page 35).
Activating and committing provisioning changes

Provisioning changes become effective only after you activate them. During activation, the edit view becomes the current view and any changes made to the edit view become active. After you activate the new conguration in the edit view, you must conrm that the activation was successful.
2.0S1
Once you have conrmed the activation, you can make the new conguration the committed view. The committed view is the permanent conguration of the node. When a Passport node restarts, it uses the conguration in the committed view. If you do not commit the view, the changes will be in effect only for the current conguration and will be lost on a subsequent restart. The gure Flowchart for activating provisioning changes (page 37) illustrates the steps you follow when activating provisioning changes.
241-5701-605 2.0S1
Chapter 1 General information 37 Figure 6 Flowchart for activating provisioning changes
Start provisioning start Prov
Verify the changes check Prov
Activate the edit view activate Prov
Confirm the activation confirm Prov
Commit the configuration commit Prov
End provisioning end Prov
PPT 2703 001 AA
2.0S1
38 Chapter 1 General information 1 Enter provisioning mode. start Prov When you enter provisioning mode, Passport indicates the differences, if any, between the current and the edit view. Passport reports added and deleted components, as well as changed attributes. 2 If the edit view does not contain the conguration changes you want to activate, load the conguration changes from a saved view. load -file(<view_name>) Prov where: <view_name> is the name of the saved view. To determine which saved views are available, see Displaying saved views on the disk (page 43). 3 Verify the provisioning changes. check Prov Correct any errors before continuing, and then verify the provisioning changes again. Passport warns you if activating these provisioning changes requires a service, function processor, or the entire node to restart. If there is a restart, service outage and potential data loss results. 4 Optionally, save the edit view. save Prov 5 Activate the edit view. activate Prov When the activation is complete, the current view and the edit view are identical.
Note: If activating the edit view causes the node to restart, wait until the node comes back up, then log on and enter provisioning mode again (using the start Prov command).
6 Conrm that the activation was successful. confirm prov The conrm command veries that the newly activated edit view allows proper access to the node. If you do not conrm the activation within 20 minutes, the node automatically restarts using the committed view.
241-5701-605 2.0S1
Chapter 1 General information 39 7 If you want the new conguration (which is now in the current view) to become the permanent conguration for the node, commit it. commit Prov If you do not commit the current view, the next time the node restarts it uses the previously committed view, and the changes you just activated are lost.
Note: If the changes you have activated include changes to the software running on the node, you will have to verify, activate, and conrm the changes again (see step 3 to step 6).
8 End the provisioning session. end Prov
Provisioning for immediate activation

Sometimes when you are troubleshooting, you need to make immediate conguration changes to isolate or correct a network problem. In this situation, you activate only specic conguration changes, not the accumulated changes stored in the edit view. When you undertake provisioning for immediate activation, save all the accumulated changes in the edit view so you can make specic conguration changes. Once you have completed your immediate activation, merge the saved changes back into the edit view. The gure Flowchart for immediate provisioning (page 40) illustrates the process.
2.0S1
40 Chapter 1 General information Figure 7 Flowchart for immediate provisioning
Start provisioning
Save the edit view
Copy current view into edit view
Make changes and additions
Commit the new current view
Do a check prov and correct if needed
Merge regular order processing to the edit view
Activate the edit view Yes Additional changes needed?
Save the merged changes
Confirm the activation
End provisioning No
PPT 2704 001 AA
241-5701-605 2.0S1
Chapter 1 General information 41 1 Enter provisioning mode: start Prov 2 Store the edit view as a saved view: save Prov Record the lename of the saved view. The lename appears when the command completes. 3 Discard all previous changes made to the edit view and copy the current view into the edit view: copy Prov The edit view and the current view are now identical. 4 Make changes to the edit view by adding and deleting components, and setting attribute values: add <component_name> delete <component_name> set <component_name> <attribute> <value> 5 Verify the provisioning changes: check Prov Correct any errors before continuing, and then verify the provisioning changes again. Passport warns you if activating these provisioning changes requires a service, function processor, or the entire node to restart. If there is a restart, service outage and potential data loss results. 6 If you want to create a new le containing these changes, save the edit view: save Prov 7 Activate the edit view: activate Prov When the activation is complete, the current view and the edit view are identical.
2.0S1
42 Chapter 1 General information 8 Conrm that the activation was successful: confirm Prov The conrm command veries that the newly activated edit view allows proper access to the node. If you do not conrm the activation within 20 minutes, the node will automatically restart using the committed view. 9 If you want the new conguration (which is now in the current view) to become the permanent conguration for the node, commit it: commit Prov If you do not commit the current view, the next time the node restarts it uses the previously committed view and the changes you just activated are lost.
Note: If the changes you have activated include changes to the software running on the node, you have to verify, activate, and conrm the changes again (see step 5 to step 8).
10 Apply the changes you saved at step 2 to the edit view: apply -file(<view_name>) Prov where: <view_name> is the name of the view you saved at step 2 Watch the messages that appear when you apply the saved view. The messages indicate any conicts between the changes you have just made and those stored in the saved view. Resolve these conicts before continuing. 11 Verify the provisioning changes: check Prov Correct any errors before continuing, then verify the provisioning changes again. 12 Save the edit view: save Prov 13 End the provisioning session: end Prov
241-5701-605 2.0S1
Displaying saved views on the disk

Before you load a saved view into the edit view, you can check the names and characteristics of all saved views stored on the disk.
1 Display the saved views currently on disk: display Prov View/* This command displays, in a table format, each saved view currently on the disk along with the user who created it, its check state (failed, unknown, partial, softwareChanged, or full), its format (ascii, commit, delta, part, or portable), and its associated software version (the version of base software running when the view was saved). 2 Display all the characteristics of a particular saved view: display Prov View/<view_name> where: <view_name> is the name of a saved view.
Copying a component conguration to another node

Partial saved views can be used for developing a conguration for a component on one node and then using that conguration on other nodes in the network. The gure Flowchart for using partial views (page 44) illustrates the steps for developing a conguration for a component on one node and then using that conguration on other nodes in the network.
2.0S1
44 Chapter 1 General information Figure 8 Flowchart for using partial views
Start provisioning
Load partial view into edit view
Edit the component
Verify the changes
Verify the component
Activate the edit view
Store component in a partial view
Confirm the activation
Move partial view to second node
Commit the configuration
Start provisioning on second node
End provisioning
PPT 2705 001 AA
241-5701-605 2.0S1
Chapter 1 General information 45 1 Start provisioning mode: start Prov 2 Make changes to a component: add <component_name> set <component_name> <attribute> <value> 3 Verify the changes you have made to the component: check -component(<component_name>) Prov where: <component_name> is the name of the component, including its instance value. Correct any errors before continuing, and then verify the component again. 4 Save the component in a partial saved view: save -file(<filename>) -component(<component_name>) Prov where: <lename> is the base software name of the saved view. <component_name> is the name of the component, including its instance value. 5 Transfer the partial saved view to a second node using FTP. For a description of the FTP process, see 241-6001-023 NMS Architect for Passport User Guide.
Note: You must move the views entire subdirectory.

6 Start provisioning on the second node: start Prov 7 Load the partial view into the edit view on the second node: load -file(<filename>) Prov where: <lename> 8 is the name of the partial saved view.
Verify the provisioning changes: check Prov Correct any errors before continuing, and then verify the provisioning changes again.
2.0S1
46 Chapter 1 General information Passport warns you if activating these provisioning changes requires a service, function processor, or the entire node to restart. If there is a restart, service outage and potential data loss results. 9 Activate the edit view: activate Prov When the activation is complete, the current view and the edit view are identical.
10 Conrm that the activation was successful: confirm Prov The conrm command veries that the newly activated edit view allows proper access to the node. If you do not conrm the activation within 20 minutes, the node automatically restarts using the committed view. 11 If you want the new conguration (which is now in the current view) to become the permanent conguration for the node, commit it: commit Prov If you do not commit the current view, the next time the node restarts it uses the previously committed view and the changes you just activated are lost. 12 End the provisioning session: end Prov
241-5701-605 2.0S1
47
Chapter 2 Conguring and maintaining Passport

The conguration and maintenance of a Passport node involves working with the basic parts of a Passport. For each part, you can set values, display operating characteristics, and perform maintenance tasks. You perform some conguration and maintenance tasks when you initially set up a new Passport node. You must perform other tasks on a regular basis to maintain the performance of your node. For more information on how to perform initial setup, schedule ongoing maintenance, and work with the various parts of Passport, see the following sections: Initial setup process (page 48) Regularly scheduled activities (page 50) Working with the alarm/BITS card (page 52) Working with the node (page 53) Working with date and time (page 56) Working with the fabric card on a Passport 15000 (page 64) Working with the bus on a Passport 7400 or Passport 8700 series switch (page 67) Working with processor cards (page 72) Working with control processors (page 87) Working with logical processors (page 110)
2.0S1
48 Chapter 2 Configuring and maintaining Passport
Working with the le system (page 125) Working with the data collection system (page 130)
Initial setup process

Before you can begin the initial setup on a new Passport node, you must make sure the node is operational and able to connect to the network. For information on getting your node into this state, see 241-5701-270 Passport 7400, 8700, 15000 Software Installation Guide. The initial setup tasks for a new node are Conguring node security (page 48) Conguring the basic node (page 49) Conguring the data collection system (page 49)
Once you have all these areas set up, you can add access services to meet node and network requirements. See the individual access service guides for more information on installing and conguring a particular service.
Conguring node security

The rst thing you must do on a new node is to provision the node security, otherwise anyone who logs onto the node is given complete control over the node. For more information on Passport security, see 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals.
CAUTION
Provision user IDs immediately
The rst conguring task must be to provision at least one user ID with system administration impact. If you do not provision a user ID, your Passport node has no security. Anyone can access the node without a user ID and password.
241-5701-605 2.0S1
Chapter 2 Configuring and maintaining Passport 49 1 Add system administration user IDs. See User administration (page 211) for details. 2 Add other user IDs as required. See User administration (page 211) for details. 3 Add the devices you want to allow remote access to the node. Identify the allowed devices by their IP address. See Conguring authorized IP access (page 223) for details.
Conguring the basic node

A basic node conguration species the name and identier of the node, the processor cards and their ports, the Passport trunks that connect the node to other nodes, and a network management interface.
1 Congure the node name and node identier. See Working with the node (page 53) for details. 2 Congure the cards and ports. See 241-1501-610 Passport 15000 FP Conguration and Testing Guide or 241-5701-610 Passport 7400, 8700 FP Conguration and Testing Guide for details. 3 Congure the Passport trunks. See 241-5701-420 Passport 7400, 8700, 15000 Trunking Guide for details. 4 Congure the IP interface over virtual circuit (IPIVC) or the IP interface over Frame Relay (IPIFR) for network management connections. See 241-5701-270 Passport 7400, 8700, 15000 Software Installation Guide for details.
Conguring the data collection system

Data is critical to operating and maintaining a Passport node. The data collection system collects data about the operation of the node and can store that data on the le system for future analysis.
2.0S1
To set up the data collection system, set the following parameters: agent queue size for each logical processor spooling option maximum number of les to keep on disk
For procedures on setting these parameters, see Working with the data collection system (page 130). For more information on the data collection system, see 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals.
Regularly scheduled activities

To maintain the performance of your Passport node, you must regularly perform a number of maintenance activities. The following tables indicate when to perform the activities: Regularly scheduled node activities (page 50) Regularly scheduled hardware activities (page 51)
Table 2 Regularly scheduled node activities Frequency of activity Daily Activity Time-of-day accounting Where to find procedure Configuring a time-of-day accounting schedule (page 208) 241-5701-650 Passport 7400, 8700, 15000 Accounting Reference Working with the file system (page 125) Working with the data collection system (page 130)
Sending Passport accounting data to a billing host Weekly Checking synchronization Checking spooling
(Sheet 1 of 2)
241-5701-605 2.0S1
Chapter 2 Configuring and maintaining Passport 51 Table 2 (continued) Regularly scheduled node activities Frequency of activity Activity Backing up service data Where to find procedure 241-6001-023 NMS Architect for Passport User Guide 241-5701-270 Passport 7400, 8700, 15000 Software Installation Guide The tidy Prov command in 241-5701-050 Passport 7400, 8700, 15000 Commands Manually testing the bus clock source (page 72)
Monthly
Cleaning up software files
Cleaning up configuration files
If you have automatic bus clock source testing disabled, perform a manual bus clock source test.
Note: This activity applies to Passport 7400 or Passport 8700 only.

(Sheet 2 of 2)
Table 3 Regularly scheduled hardware activities Frequency of activity Daily Weekly Monthly Activity No daily activities needed No weekly activities needed Changing the air filter 241-1501-215 Passport 15000 Hardware Maintenance Guide or 241-5701-215 Passport 7400, 8700 Hardware Maintenance Guide Where to find procedure
(Sheet 1 of 2)
2.0S1
52 Chapter 2 Configuring and maintaining Passport Table 3 (continued) Regularly scheduled hardware activities Frequency of activity Activity Fabric card test Where to find procedure
Working with the fabric card on a Passport 15000 Note: This activity applies to (page 64) Passport 15000 only. Bus test Working with the bus on a Passport 7400 or Note: This activity applies to Passport 8700 series switch Passport 7400 or (page 67) Passport 8700 only. Card test 241-1501-610 Passport 15000 FP Conguration and Testing Guide or 241-5701-610 Passport 7400, 8700 FP Conguration and Testing Guide 241-1501-610 Passport 15000 FP Conguration and Testing Guide or 241-5701-610 Passport 7400, 8700 FP Conguration and Testing Guide Working with the file system (page 125)
Port test
Disk test
(Sheet 2 of 2)
Working with the alarm/BITS card

The alarm/BITS card terminates cables that originate from the breaker interface panel (BIP) and the cooling unit. When the card is removed, the control processor assumes the loss of signal indicates a problem. The control processor generates a high temperature alarm and a cooling unit alarm although no action is necessary. While the card is removed, all audible and visual alarms are turned off. When the card is replaced, any alarms previously ON, return to the ON state.
241-5701-605 2.0S1
Chapter 2 Configuring and maintaining Passport 53
Replacing an alarm/BITS card

Perform the following steps in operational mode.
CAUTION
System impact minimization
To minimize the impact to the system, you need to lock all external timing components before you remove the alarm/ BITS card.
1 Find out which external timing ports are in use. display lp/0 * 2 Lock each external timing port. If a DS1 line is being used, enter lock lp/0 EDS1/<port number> If an E1 line is being used, enter lock lp/0 EE1/<port number> where: <port number> is 0 or 1. 3 4 Remove the alarm/BITS card. See Replacing Alarm/BITS module in 241-1501-215 Passport 15000 Hardware Maintenance Guide. After replacing the card, unlock the external timing ports. If a DS1 line is being used, enter unlock lp/0 EDS1/<port number> If an E1 line is being used, enter unlock lp/0 EE1/<port number> where: <port number> is 0 or 1.
Working with the node

This section explains how to modify and display settings that affect the entire node, including the Passport node name, node identier and region identier. This section also describes how to set the time on a Passport node.
2.0S1
For information on working with node-wide values, see the following sections: Displaying the backplane type (page 54) Conguring the node identication (page 54) Displaying the node identication (page 56) Conguring general service parameters (page 56)
For more information on node-wide settings, see 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals.
Displaying the backplane type

The shelfType attribute of the Shelf component indicates whether the node is a Passport 15000, Passport 8700 or Passport 7400 series switch. Perform the following command in operation mode.
1 Determine whether the backplane is bus-based or fabric-based. display Shelf shelfType The shelfType attribute displays with one of the following values: busBasedShelf for Passport 7400 or Passport 8700 fabricBasedShelf for Passport 15000
Conguring the node identication

A Passport node has three pieces of identication: node identier, node name, and region identier. The node identier is a unique number that identies the node. The node name is a unique name that identies the node. The region identier identies the topology region of the node. Perform the following steps in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system (page 33).
241-5701-605 2.0S1
CAUTION
Node restart
Changing the node identier, node name, or region identier results in a node restart.
Set the Passport node identier: set Mod nodeid <nodeid> where: <nodeid> can be any number between 1 and 4095. The node identier must be unique for each Passport node.
Set the Passport node name: set Mod nodeName <name> where: <name> is a 12-character ASCII string that is unique to every Passport node in a network. The default is NONAME. You cannot use the following characters in the node name: < > / : *
You cannot use a single $ character as a node name, but you can use it in combination with other characters. For example, LA$ is a valid node name, but $ is not. 3 Set the Passport region identier: set Mod regionId <regionId> where: <regionId> can be any number between 0 and 126. 4 Set the Passport network administration (nams) identier: set Mod namsId <namsId> where: <namsId> can be any number between 256 and 49151. It must be unique across the entire network of Passport nodes supporting the transport of DPN trafc as well as all RMs and AMs in the network.
2.0S1
Displaying the node identication

The ModuleData component contains a number of attributes that identify your Passport node. The node name also appears as the instance value of the EM component. Perform the following command in operational mode.
1 Display the node identier and the region identier: display -p ModuleData The identication attributes of the node appear. For example: nodeId = nodeName namsId = regionId 500 = Passport0 2502 = 23
Conguring general service parameters

Some Passport services require general parameters for the entire node. The Passport Startup software sets these parameters, represented by the VirtualCircuitSystem and FrameRelaySystem components of the Passport 7400 series, to default values. Many of these values must be the same on all Passport nodes within a subnet for the nodes to communicate. If you change these values, do so with extreme caution. Call Nortel Networks for assistance if necessary.
CAUTION
Risk of data loss
Changing the node-wide attributes of the VirtualCircuitSystem and FrameRelaySystem components can cause the node to become isolated from other nodes in the network. This node isolation can cause data loss.
Working with date and time

The following sections contain conceptual information about managing date and time of day in a Passport network, as well as procedures for conguring date and time on a Passport node:
241-5701-605 2.0S1
Reference time, network time, and module time (page 57)
Conguring the time in a network (page 57) Conguring the time on a node (page 59)
Reference time, network time, and module time

There are three types of time to consider when conguring the time on a Passport node: reference time, network time, and module time. The reference time is the date and time that is the ofcial reference around the world. The universally accepted reference time is Coordinated Universal Time (UTC) which, in general, is equivalent to Greenwich Mean Time (GMT). The network time is the date and time that is common across the whole network. This is the date and time to which all nodes in the network synchronize internally. Nortel Networks recommends that you use the Coordinated Universal Time (UTC) for the network time. The network time is controlled by one or more time servers. The module time is the time on a particular Passport node. In most cases, you synchronize the module time on a node to the network time on a time server and then adjust for time zone differences using a time zone offset. Passport uses the module time for timestamps in alarms, accounting records, and other timestamped data.
CAUTION
Risk of confusion in the interpretation of alarm and accounting record timestamps
Nortel Networks recommends that your network be synchronized to a reliable time server running reference time. Failure to do so may result in difculties when correlating time between multiple Passport nodes.
Conguring the time in a network

There main approaches to conguring time in a Passport network are presented in the following sections: Operating the whole network using reference time (page 58) Operating the whole network in a single time zone (page 58) Operating each node in its own time zone (page 58)
2.0S1
Operating the whole network using reference time This approach is recommended by Nortel Networks. It guarantees there is no confusion with the date and time presented in alarms, accounting records, and other timestamped data. All such data generated by the network has the same, consistent timestamp based on UTC. With this approach, a time offset of zero is congured on each node in the Passport network. As well, the whole network is synchronized to a common time reference, see Synchronizing with a network time server (page 60). In this manner, the reference time is used as network time as well as module time. Operating the whole network in a single time zone This approach may be used by networks where all nodes are within the same time zone or which are operated as if all nodes are in the same time zone. All alarm, accounting records, and other timestamped data has the same, consistent timestamp based on a single time zone. With this approach, a non-zero time offset representing a specic time zone is selected to be used for the whole network. The selected time offset is congured on each node in the Passport network. As well, the whole network is synchronized to a common time reference, see Synchronizing with a network time server (page 60). In this manner, the time in the chosen time zone is used as network time as well as module time. Although the reference time (UTC) is used to synchronize all Passports in the network, each node displays time using the selected, common time offset. In this manner, the date and time reported by all nodes in the network is the same. Operating each node in its own time zone This approach may be used by networks which require that each node in the network display the time based on the time zone in which the node resides. All alarm, accounting record, and other timestamped data has a timestamp which corresponds to the time on the node it is coming from.
241-5701-605 2.0S1
With this approach, a different time offset is congured on each node in the Passport network. Nonetheless, the whole network is still synchronized to a common time reference, see Synchronizing with a network time server (page 60). Although the reference time (UTC) is used to synchronize all Passports in the network, each node displays time using its own time offset, based on the time zone in which the node resides. In this manner, the date and time reported by all nodes in the network may be different.
CAUTION
Risk of confusion in the interpretation of alarm and accounting record timestamps
Nortel Networks recommends that nodes not be operated each with its own time offset as there is a risk of confusion in the timestamp of alarms and accounting records. For example, two nodes in different time zones would generate a different timestamp for accounting records produced on both nodes at the exact same time.
Conguring the time on a node

For information on working with the time on a node, see the following sections: Displaying the current time on the node (page 60) Synchronizing with a network time server (page 60) Conguring the time zone offset (page 61) Manually conguring the module time (page 62) Conguring the time after a power off (page 63) Displaying information on the time and network time servers (page 64)
For more information on the time on a node, see 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals.
2.0S1
Displaying the current time on the node The current time on the node is stored in the moduleTime attribute of the Time component. It reects the current date and time on the node, including the time offset. Perform the following command in operational mode.
1 Display the moduleTime attribute. display Time moduleTime The current time on the node appears in the form yyyy-mm-dd hh:mm:ss.
Synchronizing with a network time server You can synchronize your Passport node with up to 10 management devices (MD) that are acting as network time servers. An MD can be any workstation running either stand-alone Network Management System (NMS), NMS with public network time protocol (NTP), or some other management system running public NTP. Passport XNTP is the software feature on Passport switches that controls network time synchronization. See 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals for more information on Passport XNTP. See RFC 1305, Network Time Protocol (Version 3) for more information on public NTP. In case a network time server is not specied, Passport automatically attempts to synchronize with an NMS workstation it can reach using its IP interface over frame relay (IPIFR) or its IP interface over virtual circuit (IPIVC). If time servers are deleted when Passport is up and running, then Passport does not synchronize with an NMS workstation. For example, automatic synchronization works at startup if no time servers are specied. Perform the following steps in provisioning mode.
1 Add a Server component for each network time server: add Time Server/<n> where: <n> is the instance of the Server component. You can provision up to 10 Server components (decimal 1-10) on a Passport node. 2 Specify the IP address of the network time server: set Time Server/<n> ipAddress <address> 241-5701-605 2.0S1
Chapter 2 Configuring and maintaining Passport 61 where: <address> is the IP address of the MD that you wish to set as a time server to your node 3 Select the IP routing stack for time server connectivity: set Time Server/<n> ipStack <type> where: <type> is either ipiFrIpiVc (for frame relay/X.25 connectivity to a time server MD) or VrIp (for IP virtual router connectivity to a time server MD).
Conguring the time zone offset You set the time zone offset using the offset attribute of the Time component. The time zone offset value ranges from -720 to 720 minutes, which represents a range of 24 hours (-12 hours to +12 hours). A time offset between 0 and 720 minutes (+12 hours) represents a time ahead of UTC (or east of the prime meridian). A time offset value between 0 and -720 minutes (-12 hours) represents a time behind UTC (or west of the prime meridian). For example If you operating the whole network using reference time, set the time zone offset to 0 (the default value). If you are operating the whole network in a time zone east of the prime meridian, add 60 minutes to the minimum time zone offset (0) for each hour you are ahead of UTC. For example, if your time zone is two hours ahead of UTC, set the time zone offset to 120. If you are operating the whole network in a time zone west of the prime meridian (for example, Eastern Standard Time), subtract 60 from the minimum time zone offset (0) for each hour you are behind UTC. For example, if your time zone is four hours behind UTC, set the time zone offset to -240.
2.0S1
CAUTION
Risk of confusion in the interpretation of accounting records and alarm timestamps
Nortel Networks recommends that you set the time zone offset to the same value for every node in the same network. If nodes in the same network have different time zone offsets and two alarms on different nodes are generated at the exact same time, they have different timestamps. This may result in difculties when correlating time between the two Passport nodes. Perform this command in provisioning mode.
1 Set the offset attribute of the Time component to the number of minutes the nodes local time is before or after the network time: set Time offset <offset> where: <offset > is the number of minutes from the network time. You can enter a value between -720 and 720.
Manually conguring the module time If you cannot or do not want to synchronize the time on your node with the network time, you can manually set the module time. You cannot manually set the time if your node is already synchronized with a network time server. Perform the following steps in provisioning mode.
1 Check the synchronization status of your node: display Time syncStatus The synchronization status appears. 2 If the syncStatus attribute is unsynchronized, set the moduleTime attribute to the current date and time: set Time moduleTime <yyyy>-<mm>-<dd> <hh>:<mm>:<ss> where: <yyyy> is the year. <mm> is the month. 241-5701-605 2.0S1
Chapter 2 Configuring and maintaining Passport 63 <dd> is the day. <hh> is the hour. <mm> is the minute. <ss> is the second.
CAUTION
Risk of confusion in the interpretation of accounting records and alarm timestamps
Nortel Networks recommends that you synchronize all nodes in a network from a reliable time reference. When set manually, the node time will not initially be precisely the same on all network nodes and will also eventually drift out of synchronization due to de different precisions of the local clocks on each node. This will eventually result in alarms and accounting records not reporting an accurate timestamp. Conguring the time after a power off If you are resetting the module time after a power off, you must always set the module time before you set the time offset. If the node has already synchronized with the network time server, then the system will automatically disallow the resetting of module time on the node. However, you will still be able to set the offset time if required. If the node is powered off for more than 24 hours, perform the following steps in provisioning mode.
1 Set the module time. set Time moduleTime <yyyy>-<mm>-<dd> <hh>:<mm>:<ss> where: <yyyy> is the year. <mm> is the month. <dd> is the day. <hh> is the hour. <mm> is the minute. <ss> is the second. 2 Set the time offset by issuing the following command:
2.0S1
64 Chapter 2 Configuring and maintaining Passport set Time offset <offset value> where: <offset value> is an integer between -720 and 720 (minutes).
Displaying information on the time and network time servers Information about the time on your node and its network time servers is represented by the Time and Server components. You can get information about the time and the network time servers by displaying the attributes of these components. Perform the following steps in operational mode.
1 Display the operational attributes of the Time component: display Time A number of attributes display, including the current module time, the offset, synchronization status, and time server sources. 2 Display the provisionable attributes of the congured time servers: display -p Time Server/* 3 Display the operational attributes of the congured time servers: display Time Server/* 4 Display the operational attributes of a particular time server: display Time Server/<n> where: <n> is the instance value of the Server component.
Working with the fabric card on a Passport 15000

The fabric card enables the processor cards on a Passport 15000 to communicate with each other. There are two fabric cards, each represented by an instance of the FabricCard component (x and y). When both fabric cards are operational, the node is in dual-fabric mode. When one fabric card is disabled, the node is in single-fabric mode. When Passport 15000 detects errors on a fabric card, it automatically disables that fabric card.
241-5701-605 2.0S1
You can prevent a fabric card from carrying data using the lock command. The fabric card remains locked until you unlock it using the unlock command. You can only lock a fabric card if both fabric cards are unlocked and enabled. If a control processor switchover occurs, a locked fabric card remains locked. However, if the node restarts, a locked fabric card becomes unlocked. See the following sections for information on working with fabric cards: Conguring the fabric card component (page 65) Locking and unlocking a fabric card (page 65) Displaying the operating mode of the fabric cards (page 66) Displaying the status of a fabric card (page 67)
For more details on Passport 15000 fabric cards, see 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals.
Conguring the fabric card component

Two fabric card instances, Shelf FabricCard/x and Shelf FabricCard/y are automatically added to the Shelf component hierarchy during system initialization. Therefore, manual provisioning is not required. Note: The FabricCard component cannot be deleted.
Locking and unlocking a fabric card

You can lock a fabric card to temporarily prevent it from carrying data. When you perform fabric card tests you need to lock the fabric card. After testing, make sure you unlock the fabric card. For information on testing a fabric card, see Troubleshooting the fabric card on a Passport 15000 (page 159). Perform the following steps in operational mode.
1 Lock the fabric card: lock Shelf fabricCard/<n> where: <n> is either x or y.
2.0S1
66 Chapter 2 Configuring and maintaining Passport You can only lock a fabric card if the other fabric card is unlocked and enabled. 2 3 While the fabric card is locked, perform any necessary testing. Unlock the fabric card: unlock Shelf fabricCard/<n> where: <n> is either x or y.
CAUTION
Risk of data loss
To reduce the risk of data loss, do not lock the fabric card during peak periods of trafc. The fabric card system capacity has no redundancy when a fabric card is locked, potentially causing data loss due to congestion. If problems occur on the enabled fabric card, card crashes may also occur.
Displaying the operating mode of the fabric cards

The backplaneOperatingMode attribute of the Shelf component indicates whether both fabric cards are in service (dual-fabric mode) or only one fabric card is in service (single-fabric mode). Perform the following step in operational mode.
1 Determine which fabric cards are in service. display Shelf backplaneOperatingMode The backplaneOperatingMode attribute appears with one of the following values: dualFabricboth fabric cards are in service singleFabricXfabric card x is in service, but fabric card y is out of service singleFabricYfabric card y is in service, but fabric card x is out of service
241-5701-605 2.0S1
Displaying the status of a fabric card

The attributes of the FabricCard component give you information on the status of a fabric card.
CAUTION
Risk of data loss
To reduce the risk of data loss, do not lock a fabric card during peak periods of trafc. Fabric card system capacity is reduced by half when a fabric card is locked, potentially causing data loss due to congestion. If problems occur on the enabled fabric card, card crashes may also occur. Perform the following command in operational mode.
1 Display the status of a particular fabric card. display Shelf fabricCard/<n> where: <n> is either x or y A list of operational attributes of the FabricCard component appears.
Working with the bus on a Passport 7400 or Passport 8700 series switch
The bus enables the processor cards on a Passport 7400 or Passport 8700 series switch to communicate with each other. There are two buses, each represented by an instance of the Bus component (x and y). When both buses are operational, the node is in dual-bus mode. When one bus is disabled, the node is in single-bus mode. When Passport 7400 or Passport 8700 detects errors on a bus, it automatically disables that bus. You prevent a bus from carrying data using the lock command. The bus remains locked until you unlock it using the unlock command. You can only lock a bus if both buses are unlocked and enabled. If a control processor switchover occurs, a locked bus remains locked. However if the node restarts, a locked bus becomes unlocked.
Passport 7400 or Passport 8700 provides automatic testing of the bus clock source. Since the bus clock source test can cause minor data loss, you can disable the automatic testing. If you have disabled the automatic testing, it is a good idea to manually test the bus clock source at least once a month. See the following sections for information on working with buses: Locking and unlocking a bus (page 68) Displaying the bus operating mode (page 69) Displaying the status of a bus (page 69) Enabling and disabling automatic bus clock source testing (page 70) Displaying the status of the bus clock source (page 70) Manually testing the bus clock source (page 72)
For more details on Passport 7400 or Passport 8700 buses, see 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals.
Locking and unlocking a bus

You can lock a bus to temporarily prevent it from carrying data. When you perform bus tests you must lock the bus. After testing, make sure you unlock the bus. For information on testing a bus, see Troubleshooting the bus on a Passport 7400 or Passport 8700 series switch (page 166). Perform the following steps in operational mode.
CAUTION
Risk of data loss
To reduce the risk of data loss, do not lock a bus during peak periods of trafc. Bus system capacity is reduced by half when a bus is locked, potentially causing minimal data loss due to congestion. If problems occur on the enabled bus, card crashes may also occur.
1 Lock the bus:
241-5701-605 2.0S1
Chapter 2 Configuring and maintaining Passport 69 lock Shelf Bus/<n> where: <n> is either x or y. You can only lock a bus if the other bus is unlocked and enabled. 2 3 While the bus is locked, perform any necessary testing. Unlock the bus: unlock Shelf Bus/<n> where: <n> is either x or y.
Displaying the bus operating mode

The busOperatingMode attribute of the Shelf component indicates whether the both buses are in service (dual-bus mode) or only one bus is in service (single-bus mode). Perform the following command in operational mode.
1 Determine which buses are in service: display Shelf busOperatingMode The busOperatingMode attribute appears with one of the following values: dualBusboth buses are in service singleBusXbus x in service, but bus y is out of service singleBusYbus y is in service, but bus x is out of service
Displaying the status of a bus

The attributes of the Bus component give you information on the status of a bus. Perform the following command in operational mode.
1 Display the status of a particular bus: display Shelf Bus/<n> where: <n> is either x or y
2.0S1
70 Chapter 2 Configuring and maintaining Passport A list of operational attributes of the Bus component appears.
Enabling and disabling automatic bus clock source testing

The automatic bus clock source test can cause minor data loss. You can enable and disable the automatic testing. By default, automatic bus clock source testing is disabled. If you disable automatic testing, you should manually test the bus clock source at least once a month. See Manually testing the bus clock source (page 72). Perform the following steps in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system (page 33).
1 To enable automatic testing, set the automaticBusClockTest attribute to enabled: set Shelf Test automaticBusClockTest enabled 2 To disable automatic testing, set the automaticBusClockTest attribute to disabled: set shelf test automaticBusClockTest disabled
Displaying the status of the bus clock source

When Passport 7400 or Passport 8700 is performing automatic bus clock source testing, you can determine the status of the bus clock source by displaying the clockSourceStatus attribute. This attribute also shows the status of the bus clock source after a manual test. The table Interpreting bus clock source status (page 71) describes the possible values of the clockSourceStatus attribute and remedial action you can take based on the value. Perform the following command in operational mode.
1 Display the status of the bus clock source: display Shelf Bus/* clockSourceStatus Use the table Interpreting bus clock source status (page 71) to interpret the value of the attribute.
241-5701-605 2.0S1
Table 4 Interpreting bus clock source status Test result ok failed Explanation All operational cards can receive signals from the clock source. No remedial action is necessary. At least one operational card is unable to receive signals from the clock source. This condition causes an alarm. Replace the hardware item that is most likely to have failed (see below) and rerun the bus test. Repeat until you correct the problem. The following are the most likely points of failure, in order, if a clock source fails for only one card: card that failed test card containing the clock source backplane The following are the most likely points of failure, in order, if a clock source fails for multiple cards: card containing the clock source cards that failed test backplane The card at the opposite end of the shelf from the active control processor provides the alternate clock source. If the slot is empty, no alternate clock source is available. unknown The status of the clock source is not known. This is the normal clock source status when the automatic bus clock source testing is disabled. To determine the status of the clock source, manually run the bus clock source test. See Manually testing the bus clock source (page 72). The clock source is currently being tested. The new test will be run after the current test is complete. The LP associated with the alternate clock source is down or not provisioned.
testInProgress notApplicable
2.0S1
Manually testing the bus clock source

If automatic bus clock source testing is disabled, perform a bus clock source test at least once each month. Testing the bus clock source can cause minor loss of data. For this reason, run the test when bus utilization is low. Use the following command to determine the percentage of bus utilization:
display Shelf Bus/* utilization
You cannot manually test the bus clock source when the bus is in single-bus mode. Perform the following steps in operational mode.
1 Set the type of test to busClock: set Shelf Test type busClock The default value for the type attribute is busClock. 2 Start the test: run Shelf Test 3 Display the test results: display Shelf Test busClockTestResult There are three possible responses to the bus clock source test: pass fail noTestThis response indicates that the test did not run because the shelf is in single-bus mode.
For more information on the status of the bus clock source, see Displaying the status of the bus clock source (page 70).
Working with processor cards

Passport has two general types of processor cards: control processors and function processors. Control processors manage the function processor cards on the shelf and provide basic system capabilities. Function processors provide communication connections and services.
241-5701-605 2.0S1
Instances of the Card component (a subcomponent of Shelf) represent each processor card. The instance number corresponds to the number of the slot in which the card is inserted. Slot numbers start at 0. Passport reserves slot 0 for the main control processor. Passport 15000 designates slot 1 for the spare control processor. The Passport 7400 or Passport 8700 designates the last slot of the shelf for the spare control processor. In the case of the Passport 7400 or Passport 8700, some processor cards have daughter cards, which are specialized cards attached to the function processor. The DaughterCard subcomponent of the Card component represents the daughter cards present on a processor card. Logical processors (LP) represent the software conguration that runs on processor cards. When you spare processor cards, more than one processor card can run the software conguration dened in the LP. There are two ways you can use LPs to implement processor card equipment sparing. The rst method uses a single LP. For example see Working with equipment protection of electrical interface on Passport (page 80). Whereas, the second method uses two LPs. For example see Working with line protection of optical interface FPs on Passport 15000 (page 83). For more information on line APS, LPs and equipment sparing, see 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals Before setting up sparing between processor cards, check the product equipment codes (PECs) of the active and spare cards. For control processors, all eight digits of the PECs must match. For function processors, the rst six digits (four letters and two numbers) must match. Note: Some Passport 7400 and Passport 8700 processor cards have equivalent PECs. See 241-5701-200 Passport 7400, 8700 Hardware Description for a list of equivalent PECs. Except where noted, processor cards with equivalent PECs can be used as spares for each other. For procedures related to LPs, see Working with logical processors (page 110). To perform maintenance activities, it is often necessary to lock and unlock, and reinitialize processor cards.
2.0S1
For more information on working with processor cards, see the following sections: Conguring a new processor card (page 74) Displaying the card type in a given slot (page 75) Displaying information about daughter cards on a Passport 7400 or Passport 8700 series switch (page 76) Displaying the memory capacity of a processor card (page 77) Locking a processor card (page 77) Unlocking a processor card (page 78) Reinitializing a processor card (page 79) Working with equipment protection of electrical interface on Passport (page 80) Working with line protection of optical interfaces on Passport 7400 or Passport 8700 (page 80) Working with line protection of optical interface FPs on Passport 15000 (page 83) Working with line and equipment protection of optical interfaces on Passport 15000 (page 84)
For more information on processor cards, see 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals.
Conguring a new processor card

When you insert a new processor card into a slot on a Passport shelf, you must congure the processor card so that Passport can use it. For information on installing a processor card, see 241-1501-210 Passport 15000 Hardware Installation Guide or 241-5701-210 Passport 7400, 8700 Hardware Installation Guide. Perform the following steps in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system (page 33).
241-5701-605 2.0S1
Chapter 2 Configuring and maintaining Passport 75 1 Add a new Card component instance to represent the processor card: add Shelf Card/<m> where: <m> is the slot number in which you inserted the new processor card. Passport numbers its slots starting at zero (0). If the Card component instance already exists, you can skip this step. 2 Set the type of the new processor card: set Shelf Card/<m> cardType <type> where: <m> is the slot number of the new processor card. <type> is the type of the processor card. For information on the type associated with a particular processor card, see 241-1501-610 Passport 15000 FP Conguration and Testing Guide or 241-7401-610 Passport 7400 FP Conguration and Testing Guide. 3 If you are using the processor card as part of a one-for-n sparing conguration, congure where the processor card connects on the sparing panel: set Shelf Card/<m> sparingConnection <connector> where: <m> is the slot number of the new processor card. <connector> is the connector on the sparing panel. If the processor card is the spare card, use the value spare. If the processor card is the main card on a Passport 7400 series, use one of the following values: mainA, mainB, mainC, and mainD. If the processor card is the main card on a Passport 15000, use one of the following values: mainA, mainB, mainC, mainD, mainE, and mainF. For more information on sparing, see Working with equipment protection of electrical interface on Passport (page 80).
Displaying the card type in a given slot

Passport supports a number of different types of processor cards. The type of the card inserted into a slot on the shelf (as indicated by the operational attribute insertedCardType) must match the congured card type (as indicated by the provisionable attribute cardType). If the inserted card type does not match the congured card type, the processor card does not start and its status LED turns solid amber.
2.0S1

1 Display the card type of the card inserted in a particular slot: display Shelf Card/<m> insertedcardType where: <m> is the slot number of the card. 2 Display the type of card congured for the slot. display Shelf Card/<m> cardType where: <m> is the slot number of the card. Slot 0 and slot 1 are reserved for the control processor. If the congured card type does not match the inserted card type, the processor card does not start.
Displaying information about daughter cards on a Passport 7400 or Passport 8700 series switch
Some processor cards on a Passport 7400 or Passport 8700 series switch have daughter cards that provide specialized functions. The daughter cards are attached to the processor card and are represented by instances of the DaughterCard component. The instance value, which is automatically set by Passport, indicates the location of the daughter card. The attributes of the component indicate the type, memory size, and product equipment code of the daughter card. Perform the following steps in operational mode.
1 List all processor cards that have daughter cards: list Shelf Card/* DaughterCard/* A list of all daughter cards on all processor cards displays. 2 Display information about the daughter cards on a particular processor card: display Shelf Card/<m> DaughterCard/* where: <m> is the slot number of the processor card.
241-5701-605 2.0S1
Chapter 2 Configuring and maintaining Passport 77 A table displays with information about each daughter card on the processor card.
Displaying the memory capacity of a processor card

When you set up sparing between CPs, make sure both CPs have the same amount of memory and disk space. Use the following procedure to determine the memory capacity of a processor card. You can also use this procedure to determine how much memory the card is using.
1 Display the memory capacity and utilization of a processor card: display Shelf Card/<m> capacity, utilization where: <m> is the slot number of the card. Slot 0 and slot 1 are reserved for the control processor. Some of the attributes displayed are memory capacity, memory usage, and CPU utilization. CPU utilization is expressed as a percentage.
Locking a processor card

Locking a processor card prevents it from running the software conguration dened in its logical processor (LP). If the processor card is currently running an LP, locking the processor card puts the processor card into the shutting down state. The processor card stays in the shutting down state until the LP stops running. An LP stops running when you lock it or when some condition causes it to restart (an operator command or an error). After the LP stops running, the processor card moves to the locked state. You can move a processor card immediately into the locked state (skipping the shutting down state) using the force option of the lock command. For Passport 7400 or Passport 8700, when you lock a processor card using the force option, the LP immediately restarts and the processor card moves into the locked state. For Passport 15000, when you lock a processor card using the force option, the processor card moves immediately into the locked state. The LP restarts only when you restart the Passport 15000 processor card.
2.0S1
If you lock a processor card that has a dened spare card, the logical processor switches over to the standby processor card. For Passport 7400 or Passport 8700, when a processor card is locked, its LED status light is slowpulsing green. For Passport 15000, when a processor card is locked, its LED status light is solid red. Perform the following steps in operational mode.
1 Lock the processor card: lock Shelf Card/<m> where: <m> is the slot number of the card. You cannot lock a control processor. If the processor card is already running a logical processor, the processor card moves to the shutting down state until the logical processor stops running. 2 If you want to lock the processor card immediately and bypass intermediate states, use the -force option: lock -force Shelf Card/<m> where: <m> is the slot number of the card. You cannot lock a control processor. For Passport 7400 or Passport 8700, the processor card restarts and immediately moves to the locked state. For Passport 15000, the processor card immediately moves to the locked state.
Unlocking a processor card

If you have locked a processor card with the lock command or the lock command with the force option, you can unlock it using the unlock command. After you unlock a processor card in a Passport 7400 or Passport 8700 switch, it loads and starts running its logical processor (if dened). After you unlock a processor card in a Passport 15000 switch, it restarts g its logical processor (if dened). Perform the following command in operational mode.
1 Unlock the processor card: unlock Shelf Card/<m>
241-5701-605 2.0S1
Chapter 2 Configuring and maintaining Passport 79 where: <m> is the slot number of the card. You cannot lock a control processor.
Reinitializing a processor card

Passport provides two methods for reinitializing a processor card: resetting and restarting. When you reset a processor card, its hardware resets, it runs self tests, and reloads the software dened in its logical processor. When you restart a processor card, its hardware resets but it does not clear the loaded software out of memory. The processor card reinitializes the software in memory, but it does not reload the software from the le system. This behavior generally makes restarting a processor card faster than resetting the card. If you reset or restart a spared processor card, a switchover to the standby processor card occurs. When you reset a control processor, the control processor loads the committed view. You can only restart a control processor if it is currently running the committed view. Perform the following steps in operational mode.
1 Reinitialize an individual processor card. For a complete reinitialization, use the reset command: reset Shelf Card/<m> where: <m> is the slot number of the card. Slot 0 and slot 1 are reserved for the control processor. For a faster reinitialization, use the restart command: restart Shelf Card/<m> where: <m> is the slot number of the card. Slot 0 and slot 1 are reserved for the control processor. 2 If you want to reset all the processor cards, enter reset Shelf
2.0S1
Working with equipment protection of electrical interface on Passport

You can provide function processor redundancy using spare function processor cards. The spare function processor takes over in case the main function processor fails. Passport supports two types of equipment sparing for FPs with electrical interfaces: one-for-one sparing and one-for-n sparing. In one-for-one sparing, a single spare FP acts as a backup for a single main FP. In one-for-n sparing on a Passport 7400 or Passport 8700 series switch, a single FP acts as a backup for up to four main FPs. In one-for-n sparing on a Passport 15000 switch, a single FP acts as a backup for up to six main FPs. Note: In a one-for-one sparing conguration, hot standby services are hitless. Whereas, in a one-for-n conguration, hot standby services are not hitless. To congure electrical interface FP sparing for Passport 7400 or Passport 8700, see 241-5701-610 Passport 7400, 8700 FP Conguration and Testing Guide. To congure electrical interface FP sparing for Passport 15000, see 241-1501-610 Passport 15000 FP Conguration and Testing Guide. Equipment sparing for FPs with electrical interfaces requires proper hardware conguration and, in some cases, the installation of a sparing panel. For information on setting up the hardware to support equipment sparing of FPs with electrical interfaces, see 241-1501-210 Passport 15000 Hardware Installation Guide or 241-5701-210 Passport 7400, 8700 Hardware Installation Guide.
Working with line protection of optical interfaces on Passport 7400 or Passport 8700
Line automatic protection switching (line APS) is a standards-dened feature enabling a form of SONET line sparing on optical FPs. Under line APS, two lines are dened: working and protection. While both lines carry the user payload, only one is deemed active at any time. The active line is the line from which the receiving end takes its data.
241-5701-605 2.0S1
When the working line is active, the protection line operates as a backup. Line failure, signal degradation or an operator command can cause the active line to switch from working to protection. Line APS standards dene two switching schemes: revertive and nonrevertive. Revertive switching causes the active channel to revert to the designated working line when the condition causing the switchover is cleared. Non-revertive switching allows the protection line to remain active until the criteria for a switchover are met and an operator issues a manual switchover. The non-revertive scheme is the default for optical FPs. A line APS system can operate in either unidirectional mode or bidirectional mode. In unidirectional mode, each end decides independently from which line it will receive data. In bidirectional mode, the two ends negotiate to determine the active line. Unidirectional mode is the default. Refer to the following sections for information on working with line APS: Locking the protection line on Passport 7400 or Passport 8700 (page 81) Switching between the working and protection line on Passport 7400 or Passport 8700 (page 82) Clearing switch requests on Passport 7400 or Passport 8700 (page 82) Displaying the status of line APS on Passport 7400 or Passport 8700 (page 82)
For information on provisioning line APS, see 241-5701-610 Passport 7400, 8700 FP Conguration and Testing Guide. Locking the protection line on Passport 7400 or Passport 8700 There are several commands the operator can use to dictate which line is active. The protectionLockout verb locks out the protection line from being used as the active channel. If the protection line is active when protectionLockout is issued, the working line becomes active. Issue the following command to lock out the protection line:
protectionLockout Aps/<n>
2.0S1
where: <n> is the instance of the Aps component. Switching between the working and protection line on Passport 7400 or Passport 8700 The switch verb is used to effect a switch of the active line. The -force option is used to invoke the changeover with the higher priority nearEndRequest value of forcedSwitch. When -force is not used as an option, the nearEndRequest value is the lower priority manualSwitch.
switch -protectionToWorking [-force] Aps/<n>
You can issue the switch command when the Aps component is locked or unlocked. Clearing switch requests on Passport 7400 or Passport 8700 Use the clear command to clear the following nearEndRequest values: lockoutOfProtection forcedSwitch manualSwitch
Use the clear command:

clear Aps/<n>
where: <n> is the instance of the Aps component Displaying the status of line APS on Passport 7400 or Passport 8700 To determine the active channel on the near end, use the following command:
display Aps/<n> nearEndRxActiveChannel
To determine why a particular line is active on the near end, poll the nearEndRequest attribute:
display Aps/<n> nearEndRequest, nearEndRequestChannel
To determine why a particular line is active on the far end, poll the farEndRequest attribute:
display Aps/<n> farEndRequest, farEndRequestChannel
241-5701-605 2.0S1
where: <n> is the instance of the Aps component. The possible returned values for both nearEndRequest and farEndRequest are the same, as listed below: signalDegrade or signalFailsignal degradation or signal failure has occurred on the receive side of the line in question. lockoutOfProtectionthe verb protectionLockout is in effect on the line in question. manualSwitchthe switch command is in effect on the line in question. forcedSwitchthe switch -force command is in effect on the line in question. waitToRestorethe protection line is active, the switching scheme is revertive, and the request to switch to protection has cleared on the working line. Use the timeUntilRestore attribute to determine the number of minutes that will pass before the system automatically switches back to the working line:
display Aps/<n> timeUntilRestore
where: <n> is the instance of the Aps component. reverseRequestthe near end is responding to a request sent by the far end. This happens only in bidirectional mode. doNotRevertthe protection line is active, the switching scheme is nonrevertive, and the request to switch to protection has cleared on the working line. Line APS will not automatically switch back to the working line. noRequestthe working line is active and no commands are in effect.
Working with line protection of optical interface FPs on Passport 15000

This type of equipment sparing uses: an LP to dene the main port where a service runs
2.0S1
a second LP to dene a spare port where the service runs if the FP containing the main port fails. SONET line automatic protection switching (line APS) to link the ports from both LPs
To congure equipment sparing of FPs with optical ports, see 241-1501-610 Passport 15000 FP Conguration and Testing Guide. Optical FP sparing requires that the FPs be installed in specic card slots in the Passport 15000 switch. For information on setting up the hardware to support function processor sparing, see 241-1501-210 Passport 15000 Hardware Installation Guide.
Working with line and equipment protection of optical interfaces on Passport 15000
Line automatic protection switching (line APS) on a Passport 15000 node extends the line APS functionality available from Passport 7400 or Passport 8700 series nodes. Line APS on a Passport 15000 node: is implemented using the LineAutomaticProtectionSwitching (Laps) component applies to predetermined pairs of ports on a single FP to provide the same level of functionality as with Passport 7400 or Passport 8700 series nodes. This is called single-FP APS. can also apply to predetermined pairs of ports on a pair of FPs. This is called dual-FP APS.
Both single-FP APS and dual-FP APS on a Passport 15000 node offer: revertive and non-revertive switching schemes unidirectional and bidirectional operating modes
The defaults are the same as for Passport 7400 series or Passport 8700 nodes.
241-5701-605 2.0S1
Refer to the following sections for information on working with line APS on a Passport 15000 node: Locking the protection line on Passport 15000 (page 85) Switching between the working and protection line on Passport 15000 (page 85) Clearing switch requests on Passport 15000 (page 85) Displaying the status of line APS on Passport 15000 (page 86)
For information on provisioning line APS, see 241-1501-610 Passport 15000 FP Conguration and Testing Guide. Locking the protection line on Passport 15000 There are several commands the operator can use to dictate which line is active. The protectionLockout verb locks out the protection line from being used as the active channel. If the protection line is active when protectionLockout is issued, the working line becomes active. Issue the following command to lock out the protection line:
protectionLockout Laps/<n>
where: <n> is the instance of the Laps component. Switching between the working and protection line on Passport 15000 The switch verb is used to effect a switch of the active line. The -force option is used to invoke the changeover with the higher priority nearEndRequest value of forcedSwitch. When -force is not used as an option, the nearEndRequest value is the lower priority manualSwitch.
switch -protectionToWorking [-force] Laps/<n>
You can issue the switch command when the Laps component is locked or unlocked. Clearing switch requests on Passport 15000 Use the clear command to clear the following nearEndRequest values: lockoutOfProtection
2.0S1
forcedSwitch manualSwitch
Use the clear command:

clear Laps/<n>
where: <n> is the instance of the Laps component Displaying the status of line APS on Passport 15000 To determine the active channel on the near end, use the following command:
display Laps/<n> nearEndRxActiveChannel
To determine why a particular line is active on the near end, poll the nearEndRequest attribute:
display Laps/<n> nearEndRequest, nearEndRequestChannel
To determine why a particular line is active on the far end, poll the farEndRequest attribute:
display Laps/<n> farEndRequest, farEndRequestChannel
where: <n> is the instance of the Laps component. The possible returned values for both nearEndRequest and farEndRequest are the same, as listed below: signalDegrade or signalFailsignal degradation or signal failure has occurred on the receive side of the line in question. lockoutOfProtectionthe verb protectionLockout is in effect on the line in question. manualSwitchthe switch command is in effect on the line in question. forcedSwitchthe switch -force command is in effect on the line in question.
241-5701-605 2.0S1
waitToRestorethe protection line is active, the switching scheme is revertive, and the request to switch to protection has cleared on the working line. Use the timeUntilRestore attribute to determine the number of minutes that will pass before the system automatically switches back to the working line:
display Laps/<n> timeUntilRestore
where: <n> is the instance of the Laps component. reverseRequestthe near end is responding to a request sent by the far end. This happens only in bidirectional mode. doNotRevertthe protection line is active, the switching scheme is nonrevertive, and the request to switch to protection has cleared on the working line. Line APS will not automatically switch back to the working line. noRequestthe working line is active and no commands are in effect.
Working with control processors

Control processors (CP) manage all the processor cards on the shelf and provide basic system capabilities, such as timing for the bus, le storage, data collection, command processing, and interfaces for management devices. Passport 15000 has two types of control processors: CP2 and CP3. CP2 offers a lower-cost option, while CP3 offers increased processing power and connection space. Because a CP is critical to the whole node, you often use two CPs to provide redundancy. If the active CP fails, Passport automatically switches over to the standby CP. If you enable it, the function processors with applications that support hot standby for CP switchover, continue running uninterrupted during the switchover from active to standby CP. Before setting up sparing between processor cards, check the product equipment codes (PECs) of the active and spare cards. For control processors, all eight digits of the PECs must match.
2.0S1
Note: Some Passport 7400 or Passport 8700 processor cards have equivalent PECs. See 241-5701-200 Passport 7400, 8700 Hardware Description for a list of equivalent PECs. Except where noted, processor cards with equivalent PECs can be used as spares for each other. The StartUp utility automatically congures the main control processor when you initially set up the node. You can also congure a spare control processor using the StartUp utility. For more information, see 241-5701-270 Passport 7400, 8700, 15000 Software Installation Guide. The following sections contain procedures for working with the Ethernet port of a control processor: Conguring the OAM Ethernet port (page 89) Changing the switchover behavior of the OAM Ethernet port (page 91) Changing the statistics gathered from the OAM Ethernet port (page 92) Changing the line speed of the OAM Ethernet port on CP3 control processors (page 92) Changing the duplex mode of the OAM Ethernet port on CP3 control processors (page 93) Specifying a static route to connect to the OAM Ethernet port (page 93) Displaying information about the OAM Ethernet port (page 94)
For descriptive information on the OAM Ethernet port, see 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals. The following sections contain procedures for working with control processors on both single- and two-CP nodes: Disabling and enabling hot standby for CP switchover (page 94) Adding a spare control processor to a single-CP node (page 95) Replacing a control processor in a single-CP node (page 99) Replacing a control processor in a two-CP node (page 105)
241-5701-605 2.0S1
Upgrading a CP2 control processor to a CP3 control processor in a single-CP node (page 106) Upgrading a CP2 control processor to a CP3 control processor in a twoCP node (page 107) Downgrading a CP3 control processor to a CP2 control processor (page 110)
For more information on control processors and hot standby for CP switchover, see 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals.
Conguring the OAM Ethernet port

The Ethernet port is congured through the LogicalProcessor component. When you connect to the Ethernet port on a two-CP node through a hub, your NMS connectivity is also spared. Perform the following steps in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system (page 33).
1 Add the oamEnet and ip features to the feature list (FL) of the control processor: set Sw Lpt/CP featureList oamEnet ip 2 Check and activate the feature list conguration by entering the following commands: check prov activate prov 3 Add the oamEthernet component to the control processors logical processor: add Lp/0 oamEnet/0 4 Create a LAN media application by adding a LanApplication component: add La/0 Adding this component automatically creates a Framer subcomponent.
2.0S1
90 Chapter 2 Configuring and maintaining Passport 5 Associate the LAN media application with the OAM Ethernet port by setting the interfaceName attribute of the Framer subcomponent to the OamEthernet component: set La/0 Framer interfaceName Lp/0 oamEnet/0 6 Add a VirtualRouter component: add VR/0 7 Add an InternetProtocol component under the VirtualRouter component: add VR/0 IP 8 If you are conguring remote network management connectivity on a Passport 7400 or Passport 8700 node, add a RoutingInformationProtocol component under the InternetProtocol component. However, if you are conguring remote network management connectivity on a Passport 15000 node, add a StaticRoute component under the InternetProtocol component. add VR/0 IP <r> where: <r> is the RoutingInformationProtocol component for the Passport 7400 or Passport 8700 node or the StaticRoute component for the Passport 15000 node. 9 Add a ProtocolPort component under the VirtualRouter component: add VR/0 ProtocolPort/oam0 10 Map the LanApplication component to the ProtocolPort component by setting the linkToProtocolPort attribute: set La/0 linkToProtocolPort VR/0 ProtocolPort/oam0 11 Add an IpPort component under the ProtocolPort component: add VR/0 ProtocolPort/oam0 Ipport 12 Add an IpLogicalInterface component under the IpPort component: add VR/0 ProtocolPort/oam0 Ipport IpLogicalInterface/ <IPaddress> where: <IPaddress> is the IP address of the OAM Ethernet port.
241-5701-605 2.0S1
Chapter 2 Configuring and maintaining Passport 91 13 Set the netmask attribute of the IpLogicalInterface component to an appropriate IP address: set VR/0 ProtocolPort/oam0 Ipport IpLogicalInterface/ <IPaddress> netmask <netmaskaddress> where: <IPaddress> is the IP address of the OAM Ethernet port. <netmaskaddress> is the netmask address. 14 Set the broadcastAddress attribute of the IpLogicalInterface component to an appropriate IP address: set VR/0 ProtocolPort/oam0 ipport IpLogicalInterface/ <IPaddress> broadcastAddress <broadcastaddress> where: <IPaddress> is the IP address of the OAM Ethernet port. <broadcastaddress> is the broadcast address. 15 If you are conguring remote network management connectivity on a Passport 7400 or Passport 8700 node, add a RoutingInformationProtocolInterface component under the IpLogicalInterface component. However, if you are conguring remote network management connectivity on a Passport 15000 node, add a StaticRouteInterface component under the IpLogicalInterface component.: add VR/0 ProtocolPort/oam0 Ipport IpLogicalInterface/ <IPaddress> where: <IPaddress> is the IP address of the OAM Ethernet port. is the RoutingInformationProtocolInterface component for the Passport 7400 or Passport 8700 node or the StaticRouteInterface component for the Passport 15000 node.
Changing the switchover behavior of the OAM Ethernet port

Perform the following steps in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system (page 33).
1 Display the current switchover behavior of the port:
2.0S1
92 Chapter 2 Configuring and maintaining Passport display Lp/0 oamEnet/0 switchoverOnFailure 2 Set the switchoverOnFailure attribute to the required value: set Lp/0 oamEnet/0 switchoverOnFailure <value> where: <value> is either enabled or disabled. The default is enabled.
Changing the statistics gathered from the OAM Ethernet port

Perform the following command in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system (page 33).
1 Set the extendedStatistics attribute to the required value: set Lp/0 oamEnet/0 extendedStatistics <value> where: <value> is either enabled or disabled. The default is disabled.
Changing the line speed of the OAM Ethernet port on CP3 control processors
For CP3 control processors only, the OAM Ethernet port can operate at different line speeds. Perform the following command in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system (page 33).
1 Set the lineSpeed attribute to the required value: set Lp/0 oamEnet/0 lineSpeed <value> where: <value> is autoCong, tenMeg or hundredMeg. The default is autoCong.
Note: When set to autoCong, the CP3 control processor automatically sets the line speed to match the requirements of the far end hub. The actual line speed can be obtained from the actualLineSpeed attribute.
241-5701-605 2.0S1
Changing the duplex mode of the OAM Ethernet port on CP3 control processors
For CP3 control processors only, the OAM Ethernet port can operate in half or full duplex mode. Perform the following command in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system (page 33).
1 Set the duplexMode attribute to the required value: set Lp/0 oamEnet/0 duplexMode <value> where: <value> is autoCong, half or full. The default is autoCong.
Note: When set to autoCong, the CP3 control processor automatically sets the duplex mode to match the requirements of the far end hub. The actual duplex mode can be obtained from the actualDuplexMode attribute.
Specifying a static route to connect to the OAM Ethernet port

Local network management connectivity permits the use of static routes. The use of static routes depends on the conguration of the IP network that uses the OAM Ethernet port. You may need to provision static routes on the OAM Ethernet port to allow connections to the IP network to work properly. Perform the following command in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system (page 33).
1 Add a static route entry to the OAM Ethernet port: add -superiors VR/0 IP Static RouteEntry/ <ip_address_1>,255.255.255.0,0 NextHop/<ip_address_2> where: <ip_address_1> is the IP address of the network management workstation. <ip_address_2> is the IP address of the gateway router.
2.0S1
Displaying information about the OAM Ethernet port

In addition to generating a primary set and an extended set of statistics to describe the behavior of the port, the Ethernet port has operational attributes to indicate the status of the port on both the active and standby control processors, as well as to indicate its MAC address. Perform the following command in operational mode.
1 View the operational attributes of the port, OSI states, and statistics: display Lp/0 oamEnet/0
Disabling and enabling hot standby for CP switchover

Hot standby for CP switchover allows function processors running services that support it to continue operating without interruption during a CP switchover. For information on determining the behavior of function processors during a CP switchover, see Displaying CP switchover behavior of a logical processor (page 121). By default, hot standby for CP switchover is enabled. You can disable it by including the noHitlessCpSwitch feature in the feature list of the CP logical processor type. When hot standby for CP switchover is disabled, cold standby for CP switchover is still available. Note: OSI standards use different terminology when referring to standby modes. When you display the standbyStatus attribute for the CP logical processor (Lp/0), it reports notSet for both standby modes. Hot standby for CP switchover does not support the removal of the active control processor. Removing the active control processor causes unexpected behavior on the bus of a Passport 7400 or Passport 8700 series switch or the fabric of a Passport 15000 switch and can cause all processors cards to reset. For information on replacing the active control processor, see Replacing a control processor in a two-CP node (page 105). Perform the following command in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system (page 33).
241-5701-605 2.0S1
Chapter 2 Configuring and maintaining Passport 95 1 If you want to enable hot standby for CP switchover, delete the noHitlessCpSwitch feature: set Sw Lpt/CP featureList ~noHitlessCpSwitch When the noHitlessCpSwitch feature is not on the feature list of the CP logical processor type, hot standby for CP switchover is enabled. 2 If you want to disable hot standby for CP switchover, add the noHitlessCpSwitch feature: set Sw Lpt/CP featureList noHitlessCpSwitch When the noHitlessCpSwitch feature is on the feature list of the CP logical processor type, hot standby for CP switchover is disabled.
Adding a spare control processor to a single-CP node

You must congure a spare control processor only if you are installing a second control processor on a node that has only a single control processor. Once you have congured the spare CP, you do not need to recongure it to replace the spare CP. For information on replacing a CP, see Replacing a control processor in a two-CP node (page 105). With Passport 15000, the spare control processor belongs in slot 1. With Passport 7400 or Passport 8700 series switches, the spare control processor always goes in the last slot of the shelf. For example, if you have a 16-slot Passport switch, you must insert the new spare control processor in slot 15. For all Passport switches, the slot that normally houses the spare control processor can house a function processor if the node has only a single control processor operating without a spare. When you add a spare CP, make sure all eight digits of the product equipment codes for both CPs match. This ensures that the spare CP has the same amount of memory and disk space as the main CP. Note: Some Passport 7400 or Passport 8700 processor cards have equivalent PECs. See 241-5701-200 Passport 7400, 8700 Hardware Description for a list of equivalent PECs. Except where noted, processor cards with equivalent PECs can be used as spares for each other.
2.0S1
To add a spare control processor to a single-CP node, you must provision the spare CP, insert it on the shelf, and synchronize its disk to the active CP. Note: A spare CP can provide NMS connectivity redundancy when NMS is connected through the OAM Ethernet port of the control processors. For information on conguring the Ethernet port, see Conguring the OAM Ethernet port (page 89). For information on cabling the Ethernet port, see 241-1501-210 Passport 15000 Hardware Installation Guide or 241-5701-210 Passport 7400, 8700 Hardware Installation Guide. If you no longer want to use a spare control processor, you must physically remove the spare control processor and then delete its conguration. See Removing a spare control processor (page 97) for more information. Perform the following commands in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system (page 33).
1 Show which cards are currently congured: display Shelf Card/* 2 If the card does not already exist, add it to the shelf: add Shelf Card/<m> where: <m> is the slot number of the spare control processor. Passport 15000 designates slot 1 for the spare control processor. In the case of Passport 7400 or Passport 8700 series switches, the spare control processor is located in the last slot of the shelf. 3 Specify CP as the type of processor card: set Shelf Card/<m> cardType <c> where: <m> is the slot number of the spare control processor. <c> is the card type. The card type can be CP, CPeD or CPeE. 4 Set the spareCard attribute: set Lp/0 spareCard Shelf Card/<m> where: <m> is the slot number of the spare control processor.
241-5701-605 2.0S1
Chapter 2 Configuring and maintaining Passport 97 5 Verify that the provisioning changes you have made are acceptable. check Prov Correct any errors, and then verify the provisioning changes again. 6 Activate and commit the provisioning changes. activate Prov confirm Prov commit Prov For more information on this step, see Activating and committing provisioning changes (page 35). 7 End provisioning mode. end Prov 8 Insert a new control processor in the spare CP slot. Passport 15000 designates slot 1 for the spare control processor. In the case of Passport 7400 or Passport 8700 series switches, the spare control processor is located in the last slot of the shelf. See 241-1501-210 Passport 15000 Hardware Installation Guide or 241-5701-210 Passport 7400, 8700 Hardware Installation Guide for information on physically installing a control processor. 9 After the second control processor starts (its status LED is ashing green), verify that the disks on both CPs are available. list Fs Disk/* Two instances of the Disk component appear, one for each control processor. 10 Synchronize the new standby disk with the active disk. synchronize Fs When the synchronization is complete, an alarm appears to indicate that the le system is now synchronized.
Removing a spare control processor

You can disable control processor redundancy by removing the spare control processor. When you remove a spare control processor to disable control processor redundancy, you must also delete its conguration. Perform the following steps in operational mode.
2.0S1
98 Chapter 2 Configuring and maintaining Passport 1 Determine which control processor is currently active: display Lp/0 mainCardStatus, spareCardStatus If the mainCardStatus attribute has a value of active, then the main control processor is active. If the spareCardStatus attribute has a value of active, then the spare control processor is active. 2 If the spare control processor is active, switchover the control processors so that the main control processor is active: switchover Lp/0
Note: A switchover of LP/0 causes a temporary loss of connectivity until the other CP becomes active.
3 Remove the spare control processor. See 241-1501-215 Passport 15000 Hardware Maintenance Guide or 241-5701-215 Passport 7400, 8700 Hardware Maintenance Guide for information on removing a control processor. 4 Enter provisioning mode: start Prov 5 Remove the spare conguration: set Lp/0 spareCard ! 6 Remove the card conguration: set Shelf Card/<m> cardType none where: <m> is the slot number of the spare control processor. Passport 15000 designates slot 1 for the spare control processor. In the case of Passport 7400 or Passport 8700 series switches, the spare control processor is located in the last slot of the shelf. 7 Verify that the provisioning changes you have made are acceptable: check Prov Correct any errors, and then verify the provisioning changes again. 8 Activate and commit the provisioning changes: activate Prov confirm Prov commit Prov
241-5701-605 2.0S1
Chapter 2 Configuring and maintaining Passport 99 For more information on this step, see Activating and committing provisioning changes (page 35). 9 End provisioning mode: end Prov
Replacing a control processor in a single-CP node

A Passport node with a single CP has no backup in the event of a failure of the CP. A CP failure interrupts all services on the node. You must replace the failed CP immediately. There are three general steps in replacing a control processor in single-CP node: 1 Re-establish connection to the network (and NMS, if available). The quickest way to re-establish connection to the network is to take the standby CP from a donor node. A donor node is a two-CP node within the same Passport group as dened in NMS. See 241-6001-023 NMS Architect for Passport User Guide, for more information on Passport groups. If a donor node is not available, you must follow the startup procedures described in 241-5701-270 Passport 7400, 8700, 15000 Software Installation Guide, to re-establish a connection to the network. 2 Reinstall the software. If you have an NMS backup of the node, you can use NMS to reinstall the software. If you do not have a backup, you must reinstall the nodes software using the procedures described in 241-5701-270 Passport 7400, 8700, 15000 Software Installation Guide. 3 Recongure the node. If you have an NMS backup of the node, you can use NMS to congure the node. If you do not have a backup, you must manually recongure the node.
2.0S1
How you replace the control processor depends on whether or not you have a recent NMS backup of the node and whether or not you have a donor node available in the network. The following sections explain how to replace a control processor for each of the backup and donor node combinations: Replacing a control processor using a donor node and backup (page 100) Replacing a control processor using a donor node only (page 102) Replacing a control processor using backup only (page 103) Replacing a control processor without a donor node or backup (page 104)
Replacing a control processor using a donor node and backup When you have both a donor node and an NMS backup, you can take the spare CP from the donor node and insert it in the node with the failed CP. The spare CP allows you to quickly re-establish a connection to the network on the failed node. Once connected to the network, you can restore the software and conguration using the NMS backup. For information on removing a control processor, see 241-1501-215 Passport 15000 Hardware Maintenance Guide or 241-5701-215 Passport 7400, 8700 Hardware Maintenance Guide. For information on installing a control processor, see 241-1501-210 Passport 15000 Hardware Installation Guide or 241-5701-210 Passport 7400, 8700 Hardware Installation Guide. Perform the following steps in operational mode.
1 If necessary, force the main CP on the donor node to become the active CP: switchover Lp/0
2 Remove the spare CP from the shelf of the donor node. You will install this CP on the failed node once you have congured a new spare CP on the donor node. Insert a new CP into the spare slot of the donor node. With Passport 15000, the spare CP resides in slot 1. In the case of
241-5701-605 2.0S1
Chapter 2 Configuring and maintaining Passport 101 Passport 7400 or Passport 8700 series switches, the spare CP resides in the last slot of the shelf. Nortel Networks recommends that the new spare CP have the same size disk as the main CP. 4 Synchronize the new standby disk with the active disk on the donor node: synchronize Fs This step can take several hours, depending on the amount of data stored on the active disk and the difference between the two disks. 5 6 7 Remove the failed CP from the shelf of the failed Passport. Install the CP you removed from the donor node into the main slot (slot 0) of the failed Passport. When the CP comes up (LED is lit solid green), clean up the disk. Remove any unnecessary les including unused software, unused provisioning les, and the spooling les stored in the /spooled/closed directory. For information on removing les, see the following: 8 tidy Prov, tidy Sw, remove Sw Av, and remove Fs commands in 241-5701-050 Passport 7400, 8700, 15000 Commands 241-5701-270 Passport 7400, 8700, 15000 Software Installation Guide
Change the node name, node ID, and the addresses of the IPIVC interface, the IPIFR interface or the OAM Ethernet port to the values of the failed node. This step allows you to restore your connection to the network and NMS. For information on changing the node name and ID, see Conguring the node identication (page 54). For information on changing the address of IPIVC or IPIFR, see 241-7001-135 Passport NMS Connectivity User Guide.
Restore the les from the last NMS backup. See 241-6001-023 NMS Architect for Passport User Guide for procedures on le restore.
10 Activate the provisioning view that was running when the last backup to the NMS was made: reloadCp -file(<view>) Lp/0 where: <view> is the name of the provisioning view. If the provisioning view changed since the last NMS backup, you must manually recongure the changes. Passport 7400, 8700, 15000 Operations and Maintenance Guide 2.0S1
Replacing a control processor using a donor node only When you have only a donor node, you can take the spare CP from the donor node and insert it in the node with the failed control processor. The spare CP allows you to quickly re-establish a connection to the network on the failed node. Once connected to the network, you must manually reinstall the software and recongure the node. For information on removing a control processor, see 241-1501-215 Passport 15000 Hardware Maintenance Guide or 241-5701-215 Passport 7400, 8700 Hardware Maintenance Guide. For information on installing a control processor, see 241-1501-210 Passport 15000 Hardware Installation Guide or 241-5701-210 Passport 7400, 8700 Hardware Installation Guide. Perform the following steps in operational mode.
1 If necessary, force the main CP on the donor node to become the active control processor: switchover Lp/0
2 Remove the spare CP from the shelf of the donor node. You will install this CP on the failed node once you have congured a new spare CP on the donor node. Insert a new CP into the spare slot of the donor node. With Passport 15000, the spare CP resides in slot 1. In the case of Passport 7400 or Passport 8700 series switches, the spare CP resides in the last slot of the shelf. Nortel Networks recommends that the new spare CP have the same size disk as the main CP. 4 Synchronize the new standby disk with the active disk on the donor node: synchronize Fs This step can take several hours, depending on the amount of data stored on the active disk and the difference between the two disks. 5 6 Remove the failed CP from the shelf of the failed Passport. Install the CP you removed from the donor node into the main slot (slot 0) of the failed Passport.
241-5701-605 2.0S1
Chapter 2 Configuring and maintaining Passport 103 7 When the CP comes up (LED is lit solid green), clean up the disk. Remove any unnecessary les including unused software, unused provisioning les, and the spooling les stored in the /spooled/closed directory. For information on removing les, see the following: 8 tidy Prov, tidy Sw, remove Sw Av, and remove Fs commands in 241-5701-050 Passport 7400, 8700, 15000 Commands 241-5701-270 Passport 7400, 8700, 15000 Software Installation Guide
Change the node name, node ID, and the addresses of the IPIVC interface, the IPIFR interface or the OAM Ethernet port to the values of the failed node. This step allows you to restore your connection to the network and NMS. For information on changing the node name and ID, see Conguring the node identication (page 54). For information on changing the address of IPIVC or IPIFR, see 241-7001-135 Passport NMS Connectivity User Guide.
Install the application versions (AVs) for the node using the procedures described in 241-5701-275 Passport 7400, 8700, 15000 Commissioning Guide.
10 Manually recongure the node.
Replacing a control processor using backup only When you only have an NMS backup, you must replace the failed CP with a new CP. You must then re-establish connection to the network using the startup procedures. Once connected to the network, you can restore the software and conguration using the NMS backup. For information on removing a control processor, see 241-1501-215 Passport 15000 Hardware Maintenance Guide or 241-5701-215 Passport 7400, 8700 Hardware Maintenance Guide. For information on installing a control processor, see 241-1501-210 Passport 15000 Hardware Installation Guide or 241-5701-210 Passport 7400, 8700 Hardware Installation Guide. Perform the following steps in operational mode.
1 2 3 Obtain a new CP. Remove the failed CP from the shelf on the failed Passport. Insert the new CP into the main slot (slot 0) of the failed Passport.
2.0S1
104 Chapter 2 Configuring and maintaining Passport 4 Re-establish the connection to the network using the startup procedures in 241-5701-270 Passport 7400, 8700, 15000 Software Installation Guide. Clean up the le system of the new CP. Remove any unnecessary les including unused software, unused provisioning les, and the spooling les stored in the /spooled/closed directory. For information on removing les, see the following: 6 7 tidy Prov, tidy Sw, remove Sw Av, and remove Fs commands in 241-5701-050 Passport 7400, 8700, 15000 Commands 241-5701-270 Passport 7400, 8700, 15000 Software Installation Guide
Restore the les from the last NMS backup. See 241-6001-023 NMS Architect for Passport User Guide for procedures on le restore. Activate the provisioning view that was running when the last backup to the NMS was made: reloadCp -file(<view>) Lp/0 where: <view> is the name of the provisioning view. If the provisioning view changed since the last NMS backup, you must manually recongure the changes.
Replacing a control processor without a donor node or backup When you do not have a donor node or NMS backup, you must replace the failed CP with a new CP. You must then re-establish connection to the network using the startup procedures. Once connected to the network, you must manually reinstall the software and recongure the node. For information on removing a control processor, see 241-1501-215 Passport 15000 Hardware Maintenance Guide or 241-5701-215 Passport 7400, 8700 Hardware Maintenance Guide. For information on installing a control processor, see 241-1501-210 Passport 15000 Hardware Installation Guide or 241-5701-210 Passport 7400, 8700 Hardware Installation Guide.
1 2 3 Obtain a new CP. Remove the failed CP from the shelf on the failed Passport. Insert the new CP into the main slot (slot 0) on the shelf of the failed Passport.
241-5701-605 2.0S1
Chapter 2 Configuring and maintaining Passport 105 4 Re-establish the connection to the network using the startup procedures described in 241-5701-270 Passport 7400, 8700, 15000 Software Installation Guide. Clean up the le system of the new CP. Remove any unnecessary les including unused software, unused provisioning les, and the spooling les stored in the /spooled/closed directory. For information on removing les, see the following: 6 tidy Prov, tidy Sw, remove Sw Av, and remove Fs commands in 241-5701-050 Passport 7400, 8700, 15000 Commands 241-5701-270 Passport 7400, 8700, 15000 Software Installation Guide
Reinstall the application versions (AVs) for the node using the procedures described in 241-5701-275 Passport 7400, 8700, 15000 Commissioning Guide. Manually recongure the node.
Replacing a control processor in a two-CP node

In a two-CP node, you can remove the standby CP without interrupting service on the node. If the active CP fails, Passport performs an automatic switchover. With the failed CP as the standby, you can remove it and replace it with a new CP. In the unlikely event that both CPs fail simultaneously, follow the procedures in Replacing a control processor in a single-CP node (page 99). Perform the following steps in operational mode.
1 If necessary, force the CP you want to remove to become the standby control processor: switchover Lp/0
2 Remove the standby CP. See 241-1501-215 Passport 15000 Hardware Maintenance Guide or 241-5701-215 Passport 7400, 8700 Hardware Maintenance Guide, for information on removing a CP.
2.0S1
106 Chapter 2 Configuring and maintaining Passport 3 Insert a new control processor in the standby slot and wait for it to come up. See 241-1501-210 Passport 15000 Hardware Installation Guide or 241-5701-210 Passport 7400, 8700 Hardware Installation Guide, for information on installing a CP. Log on as a local operator if you want to witness the boot process of the new CP. 4 After the new CP starts loading software (its status LED is quickly ashing green), verify that the disks on both CPs are available. list Fs Disk/* Two instances of the Disk component appear, one for each control processor.
Note: If the new CP has the same volume name as the active CP, the new standby disk is automatically synchronized with the active disk. Disk synchronization can take a long time (up to an hour or more). When synchronization is complete, an alarm appears indicating that the le system is now synchronized.
5 If the new standby disk did not automatically synchronize with the active disk, manually synchronize the two disks. synchronize Fs This command can take a long time (up to an hour or more). When synchronization is complete, an alarm appears indicating that the le system is now synchronized.
Upgrading a CP2 control processor to a CP3 control processor in a single-CP node

CP3 control processors are used in Passport 15000 nodes only. Before upgrading a CP2 control processor to a CP3 control processor, ensure that the node is operating with software that supports the CP3 control processor. The CP3 control processor requires PowerPC applications. Before downloading the software that will run on the CP3 control processor, ensure that the processorTargets attribute of the Software Download component is set to i960 ppc.
241-5701-605 2.0S1
See the Passport 15000 Release Report to see which software vintage supports the CP3 control processor. See 241-5701-270 Passport 7400, 8700, 15000 Software Installation Guide to verify: the vintage of the software that the node is currently using whether the nodes application version list (AVL) contains application versions that support Power PC (ppc) applications
Also, you can reduce the time required to upgrade to a CP3 control processor by doing the following: Turn off data collection, to minimize le system activity. Minimize the accounting data on the CPs disk. Keep only the minimum number of software versions on the CPs disk.
CAUTION Upgrading a CP2 control processor to a CP3 control processor has the same service impact as replacing a CP2 control processor. Some new call connections may not be set up during CP switchover. To upgrade a CP2 control processor to a CP3 control processor, follow the same procedures as in Replacing a control processor in a single-CP node on page 99 except that the new control processor is a CP3.
Upgrading a CP2 control processor to a CP3 control processor in a two-CP node

CP3 control processors are used in Passport 15000 nodes only. Before upgrading a CP2 control processor to a CP3 control processor, ensure that the node is operating with software that supports the CP3 control processor. The CP3 control processor requires PowerPC applications. Before downloading the software that will run on the CP3 control processor, ensure that the processorTargets attribute of the Software Download component is set to i960 ppc.
2.0S1
See the Passport 15000 Release Report to see which software vintage supports the CP3 control processor. See 241-5701-270 Passport 7400, 8700, 15000 Software Installation Guide to verify: the vintage of the software that the node is currently using whether the nodes application version list (AVL) contains application versions that support Power PC (ppc) applications
Also, you can reduce the time required to upgrade to a CP3 control processor by doing the following: Turn off data collection, to minimize le system activity. Minimize the accounting data on the CPs disk. Keep only the minimum number of software versions on the CPs disk.
CAUTION Upgrading a CP2 control processor to a CP3 control processor has the same service impact as replacing a CP2 control processor. Some new call connections may not be set up during CP switchover. To upgrade a CP2 control processor to a CP3 control processor, follow the same procedure as if replacing a defective CP, except that the new control processor is a CP3. In a two-CP node, you repeat the procedure twice; once for each CP in the node. Note: A two-CP node should operate with a CP3 and a CP2 control processor only during the upgrade procedure. Normal operation requires that a two-CP node operates with two identical CPs, either two CP3 control processors or two CP2 control processors. Perform the following steps in operational mode.
1 If necessary, force the CP you want to upgrade to become the standby control processor: switchover Lp/0
241-5701-605 2.0S1
2 3 Remove the standby CP. See 241-1501-215 Passport 15000 Hardware Maintenance Guide for information on removing a CP. Insert a CP3 control processor in the standby slot and wait for it to come up. See 241-1501-210 Passport 15000 Hardware Installation Guide for information on installing a CP. Log on as a local operator if you want to witness the boot process of the new CP. 4 After the new CP3 starts loading software (its status LED is quickly ashing green), verify that the disks on both CPs are available. list Fs Disk/* Two instances of the Disk component appear, one for each control processor.
Note: If the new CP3 control processor has the same volume name as the active CP, the new standby disk is automatically synchronized with the active disk. Disk synchronization can take a long time (up to an hour or more). When synchronization is complete, an alarm appears indicating that the le system is now synchronized.
5 If the new standby disk did not automatically synchronize with the active disk, manually synchronize the two disks. synchronize Fs This command can take a long time (up to an hour or more). When synchronization is complete, an alarm appears indicating that the le system is now synchronized. 6 Force the remaining CP2 control processor to become the standby control processor: switchover Lp/0
7 Repeat step 2 to step 5 of this procedure for the remaining CP2 control processor.
2.0S1
Downgrading a CP3 control processor to a CP2 control processor

Before downgrading a CP3 control processor to a CP2 control processor, ensure that: the node is operating with software that supports the CP2 control processor. The CP2 control processor requires i960 applications. Before downloading the software that will run on the CP2 control processor, ensure that the processorTargets attribute of the Software Download component is set to i960 ppc. See 241-5701-270 Passport 7400, 8700, 15000 Software Installation Guide to verify whether the nodes application version list (AVL) contains application versions that support i960 applications the nodes le system ts on the CP2 hard disk. See Displaying information about the le system on page 127 for details. The hard disk of a CP3 control processor has a greater capacity than that of a CP2 control processor. See Upgrading a CP2 control processor to a CP3 control processor in a single-CP node on page 106 for tips on reducing the le system. To downgrade a CP3 control processor to a CP2 control processor, follow the same procedure in Upgrading a CP2 control processor to a CP3 control processor in a single-CP node on page 106 except the node is currently using CP3 control processors and the new CPs are CP2 control processors.
Working with logical processors

Passport software does not link to a processor card directly. Rather, it links to a logical entity called a logical processor (LP). Each LP represents the software that delivers Passport services or capabilities. You can associate an LP with one or more processor cards.
241-5701-605 2.0S1
When you associate an LP with more than one processor card, you have processor card sparing. In a sparing conguration, one processor card is the main and the other is the spare. Typically, the main processor card is active and provides the services and capabilities of the logical processor. The spare card is in standby mode, waiting to take over in case the main card fails. Before setting up sparing between processor cards, check the product equipment codes (PECs) of the active and spare cards. For control processors, all eight digits of the PECs must match. For function processors, the rst six digits (four letters and two numbers) must match. Note: Some Passport 7400 or Passport 8700 processor cards have equivalent PECs. See 241-5701-200 Passport 7400, 8700 Hardware Description for a list of equivalent PECs. Except where noted, processor cards with equivalent PECs can be used as spares for each other. If the main card fails, Passport performs an automatic switchover. During a switchover, the standby processor card becomes active and the active processor card comes up as standby. You can manually switch the active and standby processor cards using the switchover command. Passport supports one-for-one sparing, in which one processor cards serves as a standby for a single processor card. Passport also supports one-for-n sparing, in which one Passport 7400 or Passport 8700 processor serves as a standby for up to four processor cards and one Passport 15000 processor serves as a standby for up to six processor cards. Both types of sparing require specic hardware congurations. For information on the hardware requirements of sparing, see 241-1501-210 Passport 15000 Hardware Installation Guide or 241-5701-210 Passport 7400, 8700 Hardware Installation Guide. A logical processor type (LPT) denes the software associated with an LP. An LPT is a group of software features that you can assign to many logical processors. The gure Sample relationship between LPTs, LPs, and processor cards (page 113) illustrates a one-for-n sparing conguration of LPTs, LPs, and processor cards. The LPs 1 and 2 both share the same LPT. LP 1 has processor card 1 as its main card and processor card 2 as its spare card. LP 2 has
2.0S1
processor card 3 as its main card and processor card 2 as it spare card. If either card 1 or 3 fails, card 2 takes over. For this conguration to work, you must correctly connect the processor cards to a sparing panel and provision the sparing connection. For information on provisioning the sparing connection, see Conguring a new processor card (page 74). While working with logical processors, you can use the following procedures: Adding a logical processor type (page 113) Conguring the software features of an LPT (page 114) Adding a logical processor (page 116) Changing the LPT used by a logical processor (page 118) Deleting a logical processor (page 119) Displaying the status of a logical processor (page 120) Displaying CP switchover behavior of a logical processor (page 121) Temporarily disabling a logical processor (page 122) Re-enabling logical processors (page 123) Switching between active and standby processor cards (page 124)
For more information on logical processors, see 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals.
241-5701-605 2.0S1
Chapter 2 Configuring and maintaining Passport 113 Figure 9 Sample relationship between LPTs, LPs, and processor cards
Lpt/CFG
Lp/2
Card/2
Card/3
Lp/3
Card/4
Software Main Spare

PPT 2706 001 AA
Adding a logical processor type

Logical processor types (LPT) dene a group of software features you can assign to a logical processor. You can only use features that are part of a software application version (AV) currently available on the node. You can assign more than one feature to an LPT. Always specify the features in order of priority, with the rst feature being the feature for which you want the best performance. Exactly which combinations of features you can use depends on the type of the processor card you intend to associate with the LPT (through the logical processor). For a list of supported feature combinations, see Passport 15000 Engineering Notes and Guidelines.
2.0S1
Perform the following commands in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system (page 33).
1 Add a new LogicalProcessorType (Lpt) component: add Sw Lpt/<lpt_name> where: <lpt_name> is a name for the LPT. The name can contain up to 25 alphanumeric characters. Passport converts the name to all uppercase letters. 2 Dene the feature list: set Sw Lpt/<lpt_name> featureList <features> where: <lpt_name> is the name of the LPT. <features> is a list of the features of the LPT separated by spaces. Make sure you specify the features in order of priority. The rst feature on the list should be the one for which you want the best performance. You can display all features available on your node using the following command: list Sw Av/* Feature/* The feature names are the instance values of the Feature component.
Conguring the software features of an LPT

You can add and delete software features from an LPT by changing its featureList attribute. When changing the featureList attribute, make sure you specify the features in order of priority. The rst feature listed should be the feature for which you want the best performance.
CAUTION
Deleting a feature from an in-use LPT
If you delete a feature from an in-use LPT (referenced by a logical processor), the active processor card and the standby processor card reset. If no other in-use LPT contains the feature, the whole node can reset.
241-5701-605 2.0S1
With Passport 15000, applications and features fall into three categories: hot standby, warm standby and cold standby. See 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals for denitions. Do not create an LPT that mixes cold standby applications or features with hot standby or a warm standby applications or features. A single cold standby application or feature in an LPT changes all other applications and features into cold standby. Perform the following commands in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system (page 33).
1 Add or delete features from the feature list of the LPT: set Sw Lpt/<lpt_name> featureList <featurechanges> where: <lpt_name> is the name of the LPT for which you are changing the features. <featurechanges> is a list of feature changes separated by spaces. Make sure your modied feature list species the features in order of priority. The rst feature on the list should be the one for which you want the best performance. To delete a feature, put a tilde (~) before the feature name. For example, to delete the atmTrunks feature, use the following in <featurechanges>: ~atmTrunks To add a feature, include the feature name on the list. To add the atmTrunks feature, use the following in <featurechanges>: atmTrunks To clear the feature list and replace it with a new list, use an exclamation point (!) as the rst element in the list. For example, to clear the current feature list and replace it with the atmTrunks feature, use the following list of changes: ! atmTrunks For more information on removing features, see the section Deleting a logical processor (page 119). 2 Verify that the changes are successful: display Sw Lpt/<lpt_name> featureList
2.0S1
116 Chapter 2 Configuring and maintaining Passport where: <lpt_name> is the name of the LPT.
Adding a logical processor

Logical processors dene the software, sparing, and port congurations of processor cards. You must associate a logical processor type (LPT), which is a list of software features, to every logical processor. Use the following sparing guidelines when creating a new LP: With Passport 15000, control processors on Lp/0 can only reference the cards in slots 0 and 1. The card in slot 0 must be congured as the main card. The card in slot 1 must be congured as the spare card. With the Passport 7400 or Passport 8700 series switches, control processors on Lp/0 can only reference the cards in the rst and last slots of the switch. The card in the rst slot must be congured as the main card. The card in the last slot must be congured as the spare card. For example in a 16-slot switch, the main card must be Card/0 and the spare must be Card/15. Lp/0 must be spared to ensure redundancy of NMS connectivity when NMS is connected through the Ethernet port of the control processor. No two logical processors can reference the same processor card as main. The main and spare processor cards of a logical processor must be of identical card types. Before setting up sparing between processor cards, check the product equipment codes (PECs) of the active and spare cards. For control processors, all eight digits of the PECs must match. For function processors, the rst six digits (four letters and two numbers) must match. Note: Some Passport 7400 or Passport 8700 processor cards have equivalent PECs. See 241-5701-210 Passport 7400, 8700 Hardware Installation Guide for a list of equivalent PECs. Except where noted, processor cards with equivalent PECs can be used as spares for each other.
241-5701-605 2.0S1
For information on creating an LPT, see Adding a logical processor type (page 113). For more information on sparing, see Working with equipment protection of electrical interface on Passport (page 80) and Adding a spare control processor to a single-CP node (page 95). Once you have the software and sparing congured, you can congure the ports on the processor card by adding port subcomponents to the LogicalProcessor component. For information on conguring ports, see 241-1501-610 Passport 15000 FP Conguration and Testing Guide or 241-5701-610 Passport 7400, 8700 FP Conguration and Testing Guide. Perform the following commands in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system (page 33).
1 Add a LogicalProcessor (Lp) component: add Lp/<n> where: <n> is the number of the logical processor. You can use any integer from 1 through 15. Passport reserves 0 for the control processor. 2 Display existing LPTs and their features to determine if any are suitable: display Sw Lpt/* featureList If a suitable LPT does not exist, create one using the procedure Adding a logical processor type (page 113). 3 Set the LPT for the logical processor: set Lp/<n> logicalProcessorType Sw Lpt/<lpt_name> where: <n> is the number of the logical processor. <lpt_name> is the name of the LPT you want to use. 4 Set the main card for the logical processor: set Lp/<n> mainCard Shelf Card/<m> where: <n> is the number of the logical processor. <m> is the slot number of the main card. Passport numbers its slots starting at 0. 5 Optionally, set the spare card for the logical processor: Passport 7400, 8700, 15000 Operations and Maintenance Guide 2.0S1
118 Chapter 2 Configuring and maintaining Passport set Lp/<n> spareCard Shelf Card/<m> where: <n> is the instance value of the logical processor. <m> is the slot number of the spare card. Passport numbers its slots starting at 0. In a one-for-n sparing conguration, you can congure up to six logical processors with the same spare card in the case of Passport 15000, or up to four logical processors with the Passport 7400 or Passport 8700 series. To support this conguration, you must connect the processor cards to a sparing panel. You must also provision the sparing connection. For information on the hardware requirements of one-for-n sparing, see 241-1501-210 Passport 15000 Hardware Installation Guide or 241-5701-210 Passport 7400, 8700 Hardware Installation Guide. For information on provisioning the sparing connection, see Conguring a new processor card (page 74).
Changing the LPT used by a logical processor

You can change the software running on a logical processor by changing its LPT. The LPT denes the software features of the logical processor. For more information, see Conguring the software features of an LPT (page 114). Perform the following commands in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system (page 33).
1 Display existing LPTs and their features to determine if any are suitable: display Sw Lpt/* featureList If a suitable LPT does not exist, create one using the procedure Adding a logical processor type (page 113). 2 Set the LPT for the logical processor: set Lp/<n> logicalProcessorType Sw Lpt/<lpt_name> where: <n> is the number of the logical processor. <lpt_name> is the name of the LPT you want to use.
241-5701-605 2.0S1
Deleting a logical processor

Deleting a logical processor involves deleting its LogicalProcessor (Lp) component. When you delete an Lp component, you also delete all its subcomponents. You must also delete services which were associated with the deleted Lp component. To delete all associated services simultaneously, use the clear -rf prov command. Or you can delete every associated service individually using the delete command. If you delete a logical processor and are left with a processor card with no logical processor assigned to it, that processor card will not load when you activate your provisioning changes. If you delete the last logical processor running a particular software feature, the CP resets when you activate your provisioning changes. This situation occurs when the deleted logical processor uses an LPT that fullls both of the following conditions: The LPT is not used by any other logical processor. The LPT contains a feature not contained by any other currently used LPT.
1 Delete the logical processor: delete Lp/<n> where: <n> is number of the logical processor you want to delete. This command deletes the Lp component and all its subcomponents. The number of components deleted appears. 2 Check the provisioning changes. check Prov If you have deleted the logical processor of an active card, the semantic check indicates that the card will reset when you activate the provisioning
2.0S1
120 Chapter 2 Configuring and maintaining Passport changes. If you have deleted the last logical processor running a particular software feature, the semantic check also indicates that the control processor will reset when you activate the provisioning. 3 If you want these changes as well as other changes made in the edit view to take effect immediately, activate and commit the provisioning changes. activate Prov confirm Prov commit Prov 4 End provisioning mode. end Prov
Displaying the status of a logical processor

To determine the status of a logical processor, you can display its operational and provisionable attributes. You can also display the operational and provisionable attributes of the port subcomponents of the logical processor. Perform the following steps in operational mode.
1 Display the operational attributes of the logical processor: display Lp/<n> where: <n> is the number of the logical processor. A list of the logical processors operational attributes appears. You can display a table of operational attributes for all logical processors using the following command: display Lp/* 2 Display the provisionable attributes of the logical processor: display -p Lp/<n> where: <n> is the number of the logical processor. A list of the logical processors provisionable attributes appears. You can display a table of provisionable attributes for all logical processors using the following command: display -p Lp/*
241-5701-605 2.0S1
Chapter 2 Configuring and maintaining Passport 121 3 Display the operational attributes of a port on a logical processor: display Lp/<n> <port>/<m> where: <n> is the number of the logical processor. <port> is name of the port component. <m> is the port number. Refer to card-specic sections in 241-1501-610 Passport 15000 FP Conguration and Testing Guide or 241-5701-610 Passport 7400, 8700 FP Conguration and Testing Guide for appropriate port name and numbers. A list of the ports operational attributes appears. You can display a table of operational attributes for all ports of a logical processor using the following command: display Lp/<n> <port>/* 4 Display the provisionable attributes of a port on a logical processor: display -p Lp/<n> <port>/<m> where: <n> is the number of the logical processor. <port> is name of the port component. <m> is the port number. Refer to card-specic sections in 241-1501-610 Passport 15000 FP Conguration and Testing Guide or 241-5701-610 Passport 7400, 8700 FP Conguration and Testing Guide for appropriate port name and numbers. A list of the ports provisionable attributes appears. You can display a table of provisionable attributes for all ports of a logical processor using the following command: display -p Lp/<n> <port>/*
Displaying CP switchover behavior of a logical processor

With hot standby CP redundancy enabled, some logical processors continue running when a CP switchover occurs. A logical processor can only continue running if all its congured features support hot standby redundancy and the node is congured for hot standby redundancy.
2.0S1
Note: A switchover of LP/0 causes a temporary loss of connectivity until the other CP becomes active. You can determine if a particular logical processor is congured to restart on a CP switchover by displaying the value of its restartOnCpSwitch attribute. If the attribute has a value of false and all other hot standby requirements are met, call processing on the logical processor continues uninterrupted for established calls during a CP switchover. The logical processor cannot establish new calls until the switchover is complete. A value of false for the restartOnCpSwitch attribute does not guarantee that the logical processor will not restart on a CP switchover. If other hot standby redundancy requirements are not met, the logical processor restarts. For a list of other requirements, see 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals. A value of true indicates that the logical processor is congured to restart when a CP switchover occurs. For information on enabling hot standby CP redundancy, see Disabling and enabling hot standby for CP switchover (page 94). Perform the following command in operational mode.
1 Display the CP switchover behavior of all logical processors: display Lp/* restartOnCpSwitch
Temporarily disabling a logical processor

You can disable a logical processor (LP) using the lock command. Locking a logical processor prevents it from running the software conguration dened in its logical processor type (LPT). Since a locked LP cannot run its software, it is disabled. When you lock a running LP, the LP moves into the shutting down state. The LP stays in the shutting down state until some condition causes it to stop running (an operator command or an error). Once the LP stops running, it moves to the locked state.
241-5701-605 2.0S1
You can immediately disable (skipping the shutting down state) an LP using the force option of the lock command. When you use the force option, the LP immediately restarts and the LP moves into the locked state. When a logical processor is locked, the LED status display on its main processor card is slow-pulsing red. Perform the following steps in operational mode.
1 Lock the logical processor: lock Lp/<n> where: <n> is the number of the logical processor. You cannot lock Lp/0 (the control processor). If the logical processor is already running, it moves to the shutting down state and continues to run until some condition causes it to stop running. 2 If you want to lock the logical processor immediately, and bypass all intermediate states, use the force option: lock -force Lp/<n> where: <n> is the number of the logical processor. You cannot lock Lp/0 (the control processor). The logical processor restarts and immediately moves to the locked state.
Re-enabling logical processors

If you have disabled a logical processor using the lock command, you can reenable it using the unlock command. After you unlock a logical processor, the LED status display light on its main processor card quickly pulses red while the software loads. Once the software is loaded, the processor card becomes enabled. Perform the following command in operational mode.
1 Unlock the logical processor: unlock Lp/<n>
2.0S1
124 Chapter 2 Configuring and maintaining Passport where: <n> is the number of the logical processor.
Switching between active and standby processor cards

If Passport detects an error on the active processor card, it automatically switches to the standby processor card (if one exists). You can manually switch between the active and standby processor cards of a logical processor using the switchover Lp command. You can also schedule a switchover for a later time and cancel a scheduled switchover. You cannot schedule a switchover for the control processor (Lp/ 0). See 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals, for information about the restrictions and limitations regarding switchovers between control processors. Perform the following steps in operational mode.
1 Immediately switch between the active and standby processor card: switchover Lp/<n> where: <n> is the number of the logical processor.
Note: A switchover of Lp/0 causes a temporary loss of connectivity until the other CP becomes active.
2 To schedule a switchover for a later time, use the switchover Lp command with the time option. switchover -time(<yyyy>-<mm>-<dd> <hh>:<mm>) Lp/<n> where: <n> is the number of the logical processor. You cannot schedule a switchover for the control processor (Lp/0). <yyyy> is the four-digit year. <mm> is the two-digit month. <dd> is the two-digit day. <hh> is the two-digit hour. <mm> is the two-digit minute. 3 To cancel a scheduled switchover, use the switchover Lp command with the cancel option:
241-5701-605 2.0S1
Chapter 2 Configuring and maintaining Passport 125 switchover -cancel Lp/<n> where: <n> is the number of the logical processor.
Working with the le system

The Passport le system stores the software, conguration les, and data generated by the node. The le system consists of up to two physical disks, one on each of the control processors. When the two disks are synchronized, Passport dynamically copies the information on the active control processors disk to the standby control processors disk. See the following sections for information on working with the le system: File system restrictions (page 125) Disk full conditions (page 126) Displaying information about the le system (page 127) Synchronizing disks (page 127) Changing the volume name of a disk (page 128) Formatting a disk (page 129)
For more information on the le system, see 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals.
File system restrictions

To perform le system procedures, your user ID must have a minimum impact level of conguration. The following restrictions apply when working with directories and les: The only characters that can appear in a le name are letters, numbers, the dot (.) character, and the underscore (_) character. File names and directory names are case-sensitive. If a le or directory name contains a slash (/), it must be enclosed in quotes (" "). File and directory names cannot be longer than 40 characters.
2.0S1
File names with their full path cannot be longer than 128 characters. Note: Slashes (/) count as characters, but quotes (" ") do not.
Directory names with their full path cannot exceed 125 characters. You can have a maximum of 10 directory levels. The root directory can have a maximum of 110 items (directories and les). When you copy a protected le, the new le is not protected.
CAUTION
Risk of damaging conguration data
The Passport provisioning system looks for saved views according to specic le name formats and le relationships. If you move or rename directories and les using the Passport le system commands (or using a non-Passport utility or application), you can destroy the integrity of the saved-view database. Affected saved views cannot be recovered unless you have backed them up. Only use the tidy prov command to remove saved views.
Disk full conditions

When a disk is 85% full, Passport generates a set alarm as a warning. The alarm clears when the disk is at 75% full (or below). When you encounter disk full conditions, spooling of data records stops and the disks on a two-CP node become unsynchronized. To x a full disk problem, you must remove any unused software and provisioning les. For information on removing software les, see 241-5701-270 Passport 7400, 8700, 15000 Software Installation Guide. For information on removing provisioning les, see the tidy Prov command in 241-5701-050 Passport 7400, 8700, 15000 Commands. After removing unused les, you must manually synchronize the disks on a two-CP node using the synchronize command. Spooling of data records restarts automatically when disk goes below 90% full.
241-5701-605 2.0S1
Displaying information about the le system

You can get information about the le system and its disks by displaying their operational attributes. These attributes provide information about the status, usage, and available space of the le system as a whole and on individual disks. Perform the following steps in operational mode.
1 Display information about the le system: display Fs Displayed information includes the volume name, synchronization status, capacity, free space, and usage percentage. 2 Display information about the disks of the le system: display Fs Disk/* Displayed information includes the volume name, capacity, and free space on the disk. The instance number of the Disk component corresponds to the slot number of the control processor that holds the disk. If there are different numbers of bad blocks on the disks in a dual-disk system, the reported free space can differ on the two disks.
Synchronizing disks
At start-up, the le system automatically synchronizes both the standby and active disks if they have the same volume name. If the disks do not have the same volume name, you can manually synchronize the disks. For information on changing the volume name of a disk, see Changing the volume name of a disk (page 128). Perform the following command in operational mode.
1 Synchronize the disks. synchronize Fs Depending on the amount of stored data on the active disk and the difference between the two disks, the synchronization can take several hours.
2.0S1
128 Chapter 2 Configuring and maintaining Passport When the synchronization is complete, the active and standby disks are synchronized. Passport also ensures that both disks have the same volume name. It takes the volume name from the disk on the active control processor.
Changing the volume name of a disk

You can change the volume name of a disk by setting its volumeName attribute. The disks on the active and standby control processors must have the same volume name for Passport to automatically synchronize them. Perform the following steps in operational mode.
1 If you are changing the volume name of the active control processors disk, lock the le system: lock Fs
CAUTION
Locking the le system
Minimize the time you spend in lock Fs. Locking the le system results in a condition where provisioning activity can fail, downloading can fail, and spooling can stop if you stay in this state too long.
2 Lock the disk whose volume name you want to change: lock Fs Disk/<n> where: <n> is the number of the disk. The disk number corresponds to the slot number of the control processor that holds the disk. 3 Set the volume names on the disk: set Fs Disk/<n> volumeName <volumename> where: <n> is the number of the disk. The disk number corresponds to the slot number of the control processor that holds the disk. <volumename> is the new volume name of the disk (up to 11 characters) 4 Unlock the disk: unlock Fs Disk/<n>
241-5701-605 2.0S1
Chapter 2 Configuring and maintaining Passport 129 where: <n> is the number of the disk. The disk number corresponds to the slot number of the control processor that holds the disk. 5 If you previously locked the le system, unlock it: unlock Fs
Formatting a disk
When you format a disk, you erase all les and directories on the disk and reset the volume name of the disk. To support synchronization between different-sized disks, Passport can format a disk to a size smaller than its physical capacity. Perform the following steps in operational mode.
CAUTION
Never format the disk on the active control processor. Loss of important les can result from using the format command.
If your node has only one control processor (CP), do not format its disk. Only format a disk if you have two CPs and one of them is in standby mode. If you need to format the disk on the active CP and you have a two-CP node, rst use the switchover command to make the active CP the standby. Once it has become the standby CP, you can format its disk.
1 Lock the disk on the standby control processor: lock Fs Disk/<n> where: <n> is the slot number of the standby control processor. 2 Format the disk on the standby control processor to its maximum size: format -volumename(<volumename>) Fs Disk/<n> where: <volumename> is the volume name of the disk. If you do not specify a
2.0S1
130 Chapter 2 Configuring and maintaining Passport volume name, Passport uses the rst 11 characters of the node name. <n> is the slot number of the standby control processor. If you want to format the disk to a smaller size to maintain backward compatibility with older equipment, use the -backward option. format -volumename(<volumename>) -backward Fs Disk/<n> 3 Make a disk read test to exclude all bad disk media in the le system. Due to the above format, the bad disk medium information is lost and needs to be re-established. Set test type. set Fs disk/<n> test type diskRead 5 Start the test. start Fs disk/<n> test 6 7 Wait for its completion. Fix the le system due to the possible bad media found. set Fs disk/<n> test type filesystemCheck start fs disk/<n> test 8 9 Wait for its completion. Unlock the disk. unlock Fs Disk/<n> where: <n> is the slot number of the standby control processor. 10 Synchronize the le system: synchronize Fs The synchronization can take several hours depending on the amount of data on the active disk.
Working with the data collection system

The Passport data collection system collects various types of data and either sends it to a network management interface, spools it to the le system (for example, accounting data), or both (for example, alarms data).
241-5701-605 2.0S1
The data collection system consists of agents, collectors, and spoolers. Agents gather data from the processor cards and send the data to the collectors. The collectors (one for each data type) collect the data from the agents and send it to the network management interfaces, the spoolers, the SNMP agents, or all three. The spoolers (one for each data type) format the data and save it on the le system. Each agent, collector, and spooler has a queue that stores data records while waiting for processing. If a queue lls up, the data collection system starts to discard records. See the following sections for information on working with the data collection system: Changing agent queue sizes (page 131) Displaying data collection queue statistics (page 133) Conguring the spooling option (page 134) Conguring the maximum number of closed spooling les (page 136) Creating a new spooling le (page 139)
For more information on the data collection system, see 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals.
Changing agent queue sizes

Each logical processor has its own agent queue size settings. If you do not change the agent queue sizes of a logical processor, it uses the default queue size for each of its data types. A queue size of 0 (zero) means that the agent discards all data records of that type. This procedure describes how to change the agent queue size. Typically, you change agent queue sizes at initial setup or when you identify new engineering requirements. For example, if you need to collect statistics for performance monitoring on a logical processor, you must change the agent queue size for stats data from its default of 0 (all stats data is discarded) to a value such as 100 on the logical processor.
2.0S1
In other situations, an agent can discard information of a particular data type if the queue size is too small for the amount of data sent to it. To nd out how much data, if any, an agent has discarded, see the procedure Displaying data collection queue statistics (page 133). With this information, you can select a more appropriate queue size for that data type. However, you must be careful not to overload system resources with high queue size settings. For guidelines on determining appropriate values for agent queue sizes, see the Passport Engineering Notes and Guidelines. The default agent queue sizes are alarm: 100 records accounting: 10 000 records debug: 0 records log: 50 records scn: 200 records trap: 50 records stats: 0 records
CAUTION
Risk of operational data loss
When its queue is full, the agent discards any additional operational data originating on the logical processor.
Add a component to override the agent queue size for each data type you want to reset: add Lp/<n> Eng DataStream/<datatype> Override where: <n> is the number of the logical processor. <datatype> is one of alarm, accounting, debug, log, scn, trap, or stats.
241-5701-605 2.0S1
Note: Only add a DataStream/log component to Lp/0. Lp/0 is the only logical processor that supports the DataStream/log component since only control processors generate log data.
2 Set the maximum queue size for each data type: set Lp/<n> Eng Ds/<datatype> Ov agentQueueSize <size> where: <n> is the number of the logical processor. <datatype> is one of alarm, accounting, debug, log, scn, trap, or stats. <size> species the maximum number of records the queue can hold.
Note 1: Set the size to 0 (zero) if you want the agent to discard all data of this type. A setting of 0 (zero), however, does not prevent applications from generating the data. If possible, congure the application so that it does not generate this unrequired data. Note 2: If you want to collect a particular data type, do not set the queue size smaller than 20. Small queue sizes trigger queue threshold alarms more often than necessary.
Displaying data collection queue statistics

You can review the statistics for each data collection queue. The following information is available for collector, agent, and spooler queues: records currently in the queue (currentQueueSize attribute) received records (recordsRx attribute) discarded records (recordsDiscarded attribute)
Agent queues also provide information on the number of records that applications were unable to generate due to some limitation (recordsNotGenerated attribute). Perform the following steps in operational mode.
1 Display the queue statistics for the collectors: display Col/* Statistics This command displays a table containing the queue information for each data type. 2 Display the queue statistics for the agents: display Col/* Ag/* Statistics, AgentStatistics
2.0S1
134 Chapter 2 Configuring and maintaining Passport This command displays a table showing queue information for each data type on each logical processor. An agent discards records if its queue size is too small. If an agent is discarding records, you may want to increase the agent queue size of its LP. However, you must be careful not to overload system resources with high queue size settings. For guidelines on determining appropriate values for agent queues sizes, see the Passport Engineering Notes and Guidelines. When records are not generated, it usually indicates that some reengineering is necessary. 3 Display the queue statistics for the spoolers: display Col/* Sp Statistics This command displays a table showing queue information for each data type. A spooler discards records if its spooling option is turned off while the spooler still contains records.
Conguring the spooling option

The spooling option species whether or not a specied data type spools to the le system. The procedure Conguring the spooling option (page 134) describes how to specify whether or not a data type spools to the le system. The default settings for the spooling option are alarm: on accounting: on log: on debug: off scn: on trap: off stats: on
You cannot turn spooling on for the trap stream. If you want to stop spooling the accounting or stats stream, you must either lock its spooler or set its agent queue size to 0 (zero) for all logical processors (see Changing agent queue sizes (page 131)).
241-5701-605 2.0S1
Setting a spooler to off has the same immediate effect as locking it (see the lock command in 241-5701-050 Passport 7400, 8700, 15000 Commands). However, after a processor restarts, a locked spooler becomes unlocked but keeps its original spooling setting of either on or off.
CAUTION
Data may spool before NMIS session starts
If a spooler is set to on, data can begin spooling as soon as the control processor becomes active. If data that spools and appears in a user session (such as alarms) has already spooled before you log on, that data will not appear in your user session. For example, alarms that spool before you establish a user session are only spooled to disk and do not appear in your user session. On rare occasions, the NMS Active Alarms display does not clear after a node reload if the spooler, local operator, telnet session, or SNMP agent logs in too quickly.
CAUTION
Risk of operational data loss
If a spooler containing data is set to off, the data currently held in the spooler queue is lost. Ensure that the spooler queue is empty before turning the spooler off. Perform the following command in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system (page 33).
1 Change the spooling option: set Col/<datatype> Sp spool <setting> where: <datatype> is one of alarm, log, accounting, debug, scn, or stats. <setting> is ON or OFF. if you want to spool the data type, use ON. If you do not want to spool the data type, use OFF.
2.0S1
Conguring the maximum number of closed spooling les

There are two types of spooling les: open and closed. An open spooling le is a le in which Passport is currently writing new data records. Once the open spooling le reaches its maximum size, Passport closes the le. Passport closes all open spooling les regardless of their size at 00:00 hours (midnight). You can also manually close a spooling le. See Creating a new spooling le (page 139). The procedure Changing the maximum number of closed spooling les (page 137) describes how to set the maximum number of spooling les for a data type. Passport can limit the number of closed spooling les stored on the le system for each data type. The default maximums are alarm: 20 les accounting: 200 les debug: 2 les log: 10 les scn: 10 les stats: 200 les
When the number of les for a data type reaches its maximum, Passport discards the oldest les for that data type to make room for newly closed data les. The highest number of closed les you can specify for any data type is 200. However, you can keep an unlimited number of les by setting the number of closed les to 0 (zero).
241-5701-605 2.0S1
CAUTION
Risk of data loss and service interruption
If you set the spooler to keep an unlimited number of les, the disk can ll up with data les. When the disk is full, data records will be lost because Passport cannot save new data les. Passport also cannot support le system redundancy and cannot always perform necessary functions when the active disk is full. If you use this setting, carefully monitor disk usage. In most cases, if you set a new maximum that is lower than the number of closed les currently on the disk, Passport discards the oldest closed les until only the new maximum number of les remain. For example, if you currently have 200 closed les on the disk and you set the maximum number of les to 125, Passport discards 75 of the oldest closed les. If you try to set a new maximum for a data type and there are already over 250 closed les on the disk, Passport does not discard any les. Instead, Passport operates as if it is keeping an unlimited number of les. For example, you have 400 closed les on the disk because you set the maximum number of les to 0 (unlimited). You now change the maximum to 200. Passport ignores the new maximum and continues to keep an unlimited number of les. Passport generates an alarm to warn you of this situation. This behavior prevents large amounts of system resources from being used to delete closed les. You need to remove the closed les using the Management Data Provider to get Passport to enforce the new maximum. See 241-6001-309 NMS Management Data Provider User Guide for details. For guidelines on determining appropriate values for maximum closed spooler les, see the Passport 15000 Engineering Notes and Guidelines. Changing the maximum number of closed spooling les Perform the following steps in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system (page 33).
1 Display the current maximum le settings for all data types:
2.0S1
138 Chapter 2 Configuring and maintaining Passport display Col/* Sp maxFile 2 Specify the maximum number of les to be kept on disk for each data type: set Col/<datatype> Sp maxFile <number> where: <datatype> is one of alarm, accounting, log, debug, scn, trap, or stats. <number> species the number of les to be kept on disk (any integer between 1 and 200). If you want to keep an unlimited number of les, enter 0 (zero). However, carefully monitor disk usage when using the unlimited setting.
Note: If the /spooled/closed/<datatype> directory has more les than the new maximum, Passport discards the oldest les until it reaches the new maximum. If, however, the directory contains over 250 closed les, Passport does not delete les, does not limit the number of les, and generates an alarm.
Displaying the names of the spooling les

You can display the name of the open spooling le for each data type using the spoolingFileName attribute. You can display the names of closed spooling les by listing the subdirectories of the /spooled/closed directory on the Passport le system. Perform the following steps in operational mode.
241-5701-605 2.0S1
Chapter 2 Configuring and maintaining Passport 139 1 Display the le names of all open spooling les: display Col/* Sp spoolingFileName This command gives you a table listing the le name of the spooling le for each data type. The le name is displayed if a le is open. The full path name is also available with the le name (for example, a typical path and le name would be /spooled/opened/alarm/alarm.MMDDhhmm.xxx). 2 Display the le names of closed spooling les for a data type: ls -path(/spooled/closed/<datatype>) Fs where: <datatype> is one of alarm, log, accounting, debug, scn, or stats. This command lists all the closed spooling les for the particular data type. The command only displays the le name (for example, alarm.MMDDhhmm.xxx).
Creating a new spooling le

Create a new spooling le when you want to retrieve the latest set of data of a particular data type. Once Passport creates a new spooling le, it closes the open spooling le. You can only retrieve closed spooling les. Once the spooling le is closed, you can retrieve the latest set of data for analysis. For example, if the Management Data Provider is going to run at a certain time (to transfer closed accounting les to a billing host) and a large spooling le is still open, you can close that le to include in the le transfer. See 241-6001-309 NMS Management Data Provider User Guide for details on Management Data Provider. You can use the procedure Displaying the names of the spooling les (page 138) to nd out which les are currently open. Passport automatically closes a spooling le and creates a new open spooling le when the le reaches its maximum size (approximately 0.5 Mbyte) or if a le system is disabled or locked. Passport also closes all open spooling les at 00:00 hour (midnight). Perform the following steps in operational mode.
2.0S1
140 Chapter 2 Configuring and maintaining Passport 1 Create the new spooling le. newfile Col/<datatype> Sp where: <datatype> is one of log, alarm, scn, accounting, debug, or stats. Passport creates a new spooling le and then closes the existing open spooling le. 2 Optionally, transfer closed les to another location for analysis using management data provider (MDP).
241-5701-605 2.0S1
141
Chapter 3 Conguring network clock synchronization

This section describes conguration considerations and procedures for clocking in a Passport network. Information is organized into the following sections: Conguration basics for network clock synchronization (page 141) Displaying the current source of timing (page 145) Conguring ports to provide a line timing source (page 145) Conguring an external timing source on a Passport 15000 (page 146) Activating network synchronization (page 147) Removing a reference (page 147) Setting a component to free run if previously congured with references (page 148) Conguration for specic function processors (page 148) Example of conguring an external clock source (page 151)
Conguration basics for network clock synchronization

The gure Components and attributes used for network clocking synchronization (page 142) shows the congurable software and logical hardware components and attributes for network clock synchronization. The term reference indicates a reference for the CP. The reference receives the network clock signal from another node and passes it to the CP (to use as a reference).
2.0S1
142 Chapter 3 Configuring network clock synchronization Figure 10 Components and attributes used for network clocking synchronization
Logical Hardware components
Software components
Root
Root
LP
DS1 (E1, etc.) clockingSource
networkSync primaryReference secondaryReference TertiaryReference
Root
LP
V35 (X21, etc.) clockingSource linkMode
Note: Only a subset of the provisionable attributes is provided under the heading Logical hardware components
PPT 0529 001 AA
241-5701-605 2.0S1
Chapter 3 Configuring network clock synchronization 143
There are two parts to conguring network clock synchronization. The rst part involves the NetworkSynchronization (NS) component. The second part involves the conguring the physical ports that make use of network clock synchronization. A node can be made a slave by conguring a choice of physical ports from which the Stratum-3 can derive its clock. If no physical ports are congured in the NS component, then the node will run as a master (with the Stratum-3 free-running at its centre frequency). Note: If all of the NS components congured ports in the slave node are out of service, then the Stratum-3 will be free-running in hold-over mode. The physical ports can be made to synchronize with a clocking source (using the port attribute clockingSource) which can be module, local, or line. The value module means the CPs Stratum-3 clock is used to generate the ports transmit clock, local means the ports own crystal is used, and line means the clock signal received from the port is used to generate the transmit clock. For more information on clocking, see 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals. Passport nodes derive clock synchronization from three timing reference signals: An external timing reference signal is a non-trafc carrying link that uses an E1 or DS1 signal. This source applies to Passport 15000 only. A line timing reference signal is extracted from an incoming trafc carrying signal. An internal timing reference signal uses the internal oscillator of the physical card.
For additional descriptive information about network clock synchronization, see 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals.
2.0S1
144 Chapter 3 Configuring network clock synchronization
Notes on clocking for V.35 and X.25 function processors

Care must be taken when setting the clockingSource and linkmode attributes for nodes which contains V35/X21 function processors. The gure Example of a V35/X21 two-node network (page 144) shows a V35/X21 two-node network which contains Node A and Node B. If we wish to set up Node A as the master clock source with Node Bs clock signal synchronized to Node As clock, the following points must be addressed. To designate Node A as the master end, set the linkmode attribute for Node A to dce. To designate Node B as the slave end, set the linkmode attribute for Node B to dte.
Figure 11 Example of a V35/X21 two-node network
Node A: Master
DCE
DTE
Node B; Synchronized to Node As Stratum-3 clock
PP LP/1 V35/0 LP/5 V35/0
PP
PPT 0558 001 AA
Since the clockingSource attribute is used to select an outgoing clock source and is not related to the incoming clock, the clockingSource attribute for Node A should be set to module. Since Node B is not used for external clocking, its clockingSource attribute does not have to be set. Note: When setting the linkmode attribute, the user must be aware of the physical termination of the individual V35/X21 function processor on the node. If the V35/X21 function processor is physically connected to a specic port type (for example dte) and the user sets the linkmode attribute to dce, the hardware connection overrides the congured linkmode attribute setting. The end result is the congured setting for the
241-5701-605 2.0S1
Chapter 3 Configuring network clock synchronization 145
linkmode attribute will not be recognize. To avoid this problem, the user must ensure that the congured setting for the linkmode attribute matches the physical termination of the function processor. It must be remembered that the output ports of an individual V35/X21 function processor are grouped into two separate connections. Ports 0 through 3 represent one connection and ports 4 through 7 represent another connection. Each of these connections can either be set to either dte or dce depending on its physical connection. For the connections which are physically connected as dce, and the ports which have their linkmode attributes set as dce, the clockingsource attribute must be set to the same value for all ports on this connection. These values are either module, local, or line. For example, if the rst connection (which includes ports 0 through 3) is connected as dce and the linkmode attributes for these ports are set to dce, the value set for the clockingsource attribute for ports 0 through 3 must all be the same. This is not applicable if the connection is set to dte.
Notes on clocking for Passport 15000

Passport 15000 supports mixed timing modes (a combination of external and line timing). However, when dening the primary, secondary, and tertiary sources of the synchronization signal, ensure that you do not create potential timing loops.
Displaying the current source of timing

To display the current source of timing, use the following command in operational mode.
display NetworkSynchronization activeReference
Conguring ports to provide a line timing source

Perform the following steps in prov mode. For information on working in prov mode, see Changing the conguration using the provisioning system (page 33).
1 Set all ports of the LP to synchronize with the Stratum-3 clock on the node. set Lp/<n> <port_type>/<m> clockingSource module where: <n> is number of the LP receiving or sending the synchronization signal. Passport 7400, 8700, 15000 Operations and Maintenance Guide 2.0S1
146 Chapter 3 Configuring network clock synchronization <port_type> is the type of port, such as a ds1. <m> is a port number. 2 Repeat step 1 for all ports on the logical processor.
Conguring an external timing source on a Passport 15000

1 Determine what kind of signal is expected: display sh card/0 cardType If the control processor is of type CPeD, the signal is from a DS1 line. If the control processor is of type CPeE, the signal is from an E1 line. 2 Add the external timing feature to the feature list (FL) of the control processor: set Sw Lpt/cp featureList externalTiming 3 Verify the conguration changes, activate the edit view, and conrm that the activation was successful: check Prov activate Prov confirm Prov 4 Dene one or both external timing ports to receive the signal. If the signal is from a DS1 line, enter add lp/0 EDS1/<port> If the signal is from an E1 line, enter add lp/0 EE1/<port> where: <port> is 0 or 1 5 If the signal is from a DS1 line, set the congurable attributes. set lp/0 EDS1/<port> lineType <mode> where: <port> is 0 or 1 <mode> is d4 or esf
241-5701-605 2.0S1
Chapter 3 Configuring network clock synchronization 147 6 Verify the conguration changes, activate the edit view, commit the new conguration, and save the edit view: check Prov activate Prov commit Prov save Prov
Activating network synchronization

1 Create the network synchronization component: add networkSynchronization 2 Dene up to three sources of the timing signal: set networkSynchronization primaryReference <path1> set networkSynchronization secondaryReference <path2> set networkSynchronization tertiaryReference <path3> where: <path1>, <path2> and <path3> are the port instances of the timing signal sources congured for external or line timing.
Note 1: If there are no references from which the node can receive a timing signal, do not congure any references. This will force the node clocking to run in free-run mode. Note 2: Although the individual ports of an optical interface card congured for APS can each serve independently as a reference source, the pair of them as dened by the Aps component instance cannot be used as a single reference source.
Removing a reference
To remove a previously congured reference, set the particular attribute without identifying a new reference. For example:
set NetworkSync tertiaryReference
In this example, with the attribute parameter omitted, the tertiary reference is set to nil (no reference).
Setting a component to free run if previously congured with references

To force the NetworkSynchronization component to free run, set all the references without values. For example:
set NetworkSync primaryReference set NetworkSync secondaryReference set NetworkSync tertiaryReference
As described in the previous section, omitting the attribute parameter sets the references to nil (no reference).
Conguration for specic function processors

This section includes procedures for conguring network clock synchronization for specic function processors: Conguring network clock synchronization for DS1 or E1 function processor (page 148) Conguring network clock synchronization for DS3 or E3 function processor (page 149) Conguring network clock synchronization for V35 or X21 control processor (page 149) Conguring network clock synchronization for voice or MVP/MVP-E function processors (page 150)
Conguring network clock synchronization for DS1 or E1 function processor

1 To allow a DS1 or E1 port to use the reference clock source from the CP: set lp/5 ds1/1 clockingSource module If one port is selected with a clockingSource as module, no other port can be congured with a clockingSource as local on the same lp. 2 To select a DS1 or E1 port as a possible reference for the network clock synchronization: set networkSync primaryReference lp/5 ds1/1
241-5701-605 2.0S1
Chapter 3 Configuring network clock synchronization 149 The clockingSource attribute can be set to line or module in order that the ds1 port be considered as a reference for the NetworkSynchronization component.
Conguring network clock synchronization for DS3 or E3 function processor

On a 4-port channelized DS3 function processor or a 4-port channelized ATM DS3 function processor, the only valid value is sameAsDs3. A DS1 must have the same clocking source as its parent DS3.
1 To allow a DS3 or E3 port to use the reference clock source from the CP: set lp/3 ds3 clockingSource module 2 To select a DS3 or E3 port as one of the possible references for the CP (receiver of the network clock signal from another source), you can select either module or line for the clockingSource attribute. set lp/3 ds3 clockingSource line set networkSync primaryReference lp/3 ds3
Conguring network clock synchronization for V35 or X21 control processor

1 To allow a V35/X21 port to use the reference clock source from the CP (possible provider of the network clock signal): set lp/7 x21/0 clockingSource module set lp/7 x21/0 linkMode dce The linkMode attribute must be set to dce. Remember, the actual link mode is set when you congure your hardware. The hardware setup is shown by the actualLinkMode attribute (operational attribute).
Note: If one port is selected with a clockingSource of module, all other dce ports on that LP must select module for their clockingSource.
2 To select a V35/X21 port as a reference for the CP (receiver of the network clock signal from another source): set lp/7 V35/0 linkMode dte set networkSync primaryReference lp/5 v35/0 The linkMode attribute should be set to dte. Remember, the link mode is set when you congure your hardware. The hardware setup is shown by the actualLinkMode attribute (operational attribute) which is Passport 7400, 8700, 15000 Operations and Maintenance Guide 2.0S1
150 Chapter 3 Configuring network clock synchronization noncongurable. Setting the linkmode attribute will not override the hardware conguration. The incoming clock must be a multiple of 56 kbit/s or 64 kbit/s ranging from 56 kbit/s to 2048 kbit/s. The gure Example: selecting a V35 or X21 port as a reference for the CP (page 150) provides a graphical representation of this procedure. Figure 12 Example: selecting a V35 or X21 port as a reference for the CP
Reference for CP
Provider from CP
CP
DTE V35
DTE V35 Master
CP
PPT 0562 001 AA
Conguring network clock synchronization for voice or MVP/ MVP-E function processors
Use the following information when conguring network clock synchronization for voice or MVP/MVP-E function processors:
1 To allow a voice or MVP/MVP-E function processor port to use the reference clock source from the CP: set lp/5 <port>/0 clockingSource module where: <port> is ds1 for 1pDS1V, 1pDS1Mvp, 1pDS1Mvpe FPs, or e1 for 1pE1V, J2Mv, 1pTtc2mMvp, 1pE1Mvp, 1pE1Mvpe and 1pTtc2mMvpe FPs. 2 To select a voice or MVP/MVP-E function processor port as a possible reference for network clock synchronization:
241-5701-605 2.0S1
Chapter 3 Configuring network clock synchronization 151 set NetworkSync primaryReference lp/5 <port>/0 3 The clockingSource attribute can be line or module for a DS1 port to be considered as a reference for the NetworkSynchronization component, but it is good practice to always set it to module. set lp/5 ds1/0 clockingSource module
Example of conguring an external clock source

This section provides an example of conguring an external clock source for a network with two nodes. Information is organized into the following sections: Two-node network (Node A commands) (page 152) Two-node network with an external clock source (Node B commands) (page 153) Congure clocking with multiple references (page 154)
In this example, the objective is to set up the Stratum-3 clock on Node A to synchronize with an external clock source. The external clock source must be Stratum-3 or higher. Node A becomes the clock source for the rest of the Passport network. Node B synchronizes to the clock on Node A, as shown in the following gure.
Figure 13 Example of a two-node network
Node A: Master External Clock Source LP/2 DS1/0 PP LP/1 DS1/0
Node B; Synchronized to Node A PP LP/5 DS1/0

PPT 0531 001 AA
2.0S1
Two-node network (Node A commands)

1 Enter prov mode on Node A. start Prov 2 Add the NetworkSync component. add NetworkSync The NetworkSync component does not need an instance value. d ns NS primaryReference = secondaryReference = tertiaryReference =
Note: If there is not an external reference for Passport 7400, 8700, 15000 to slave off of, then do not congure any references. This will force the Passport 7400, 8700, 15000 clocking to free run.
3 Select the source for the reference clock for the module. Typically the secondaryReference and the tertiaryReference attributes would also be set at this point. set NetworkSync primaryReference lp/2 ds1/0 4 Set the transmit clock port lp/2 ds1/0 (logical processor instance 2, ds1 port instance 0) to synchronize with Node As Stratum-3 clock. To do this, use the module value for the clockingSource attribute. set lp/2 ds1/0 clockingSource module
Note: This clockingSource attribute could be set to line, but it is good practice to always set it to module.
The clocking source for this module and the rest of the Passport network slaving off of this module will now be synchronized to the external equipment. 5 Set port lp/1 ds1/0 (this is the Passport trunk to Node B) to synchronize with Node As Stratum-3 clock. set lp/1 ds1/0 clockingSource module
Note: This ports clockingSource attribute must be set to module. If it is set to line or local, Node Bs clocking would be isolated from Node A.
241-5701-605 2.0S1
Chapter 3 Configuring network clock synchronization 153 The clocking used by this port is now synchronized with Node As Stratum-3 clock (see the gure Example: results of Node A commands (page 153)). 6 Exit the prov mode.
Figure 14 Example: results of Node A commands
Node A: CP DS1 Ip/2 Stratum-3 clock Ip/1 DS1

PPT 0532 001 AA
Two-node network with an external clock source (Node B commands)

1 Enter the prov mode on Node B. start Prov 2 Add the NS component. It does not need an instance value. add NetworkSync At this point you may wish to use the display command to display the component. 3 Set the NS component to reference lp/5 ds1/0 (logical processor instance 5, ds1 port instance 0). If this were a larger network you might set secondary and perhaps tertiary references at this point. These would back up the primary reference in case of network problems. set NetworkSync primaryReference lp/5 ds1/0 4 Though the clockingSource attribute does not have to be changed from its default, it is good practice to always set it to module. set lp/5 ds1/0 clockingSource module 5 Exit the prov mode.
2.0S1
154 Chapter 3 Configuring network clock synchronization Figure 15 Example: results of Node B command
NodeB CP DS1
Stratum-3 clock
PPT 0533 001 AA
Congure clocking with multiple references

You can congure different sources for the reference clock for a module through the following commands:
set NetworkSync primaryReference lp/2 ds1/1 set NetworkSync secondaryReference lp/4 e1/1 set NetworkSync tertiaryReference lp/5 v35/0
In the preceding example, lp/2 ds1/1 is the rst reference for the NetworkSynchronization (NS) component. If this port fails (for example, due to loss of signal or loss of frame), the next port (lp/4 e1/1) is the reference. If the reference clock source congured under the primaryReference attribute does not provide a stable clocking source, the NS component can remain in the synchronizing state without switching to the secondary or tertiary reference. In this situation, you can manually change the reference clock source by reconguring the primaryReference and secondaryReference attributes (the system generates an alarm if the NS component remains in the synchronizing state for more than fteen minutes).
241-5701-605 2.0S1
155
Chapter 4 Troubleshooting
Passport provides troubleshooting information and a number of hardware diagnostic tests to help you detect and solve problems on your node. For more information on Passport troubleshooting, see the following sections: Troubleshooting process (page 156) Getting troubleshooting information (page 157) Troubleshooting the node (page 158) Troubleshooting the fabric card on a Passport 15000 (page 159) Troubleshooting the bus on a Passport 7400 or Passport 8700 series switch (page 166) Troubleshooting function processors (page 174) Troubleshooting control processors (page 184) Troubleshooting the OAM Ethernet port (page 191) Troubleshooting the le system (page 194) Troubleshooting the data collection system (page 201)
2.0S1
156 Chapter 4 Troubleshooting
Troubleshooting process
There are three steps in the troubleshooting process: 1 2 3 Identifying the problem (page 156) Determining the cause (page 156) Resolving the problem (page 156)
Identifying the problem

An alarm displayed on the VT100 terminal usually provides a clear indication of which component has failed and the required corrective action. When you have a hardware problem, the LED status indicators on the hardware can help you identify the problem. When you receive an alarm indication, see the Symptoms column in the troubleshooting tables, beginning with Troubleshooting node outage problems (page 159). Also see 241-5701-500 Passport 6400, 7400, 8700, 15000 Alarms, for alarm information. You can get extra information about the problem by displaying the OSI state of the affected component or components. See Displaying the OSI states of a component (page 157). If you determine that the problem pertains to a service, see that services document for troubleshooting guidelines. For example, if the problem is with frame relay UNI, see 241-7001-300 Passport Frame Relay UNI User Guide.
Determining the cause

Determine the cause of the problem by referring to the Probable causes column in the troubleshooting tables and by using the procedures beginning with Troubleshooting the node (page 158).
Resolving the problem

Problem resolution involves specic corrective activities that are described in procedures throughout the Passport documentation suite. See the Corrective measures column in the troubleshooting tables, beginning with Troubleshooting node outage problems (page 159). Entries in this column indicate the appropriate action to take or direct you to another procedure if necessary.
241-5701-605 2.0S1
Chapter 4 Troubleshooting 157
Getting troubleshooting information

The following information can help you determine problems with the operation of your node. Alarm data (page 157) Displaying the OSI states of a component (page 157)
For more information, see 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals.
Alarm data
An alarm appears on the terminal when a component of the Passport node detects a fault or failure condition with either itself or another component on the node. Alarms also appear when a component undergoes a signicant state change. For example, an alarm appears when the operational state of an Lp changes from enabled to disabled. For more information on alarms, see 241-5701-500 Passport 6400, 7400, 8700, 15000 Alarms.
Displaying the OSI states of a component

The OSI state of a component indicates key aspects of a components usability, operability, and availability at any given time. There are three OSI states: administrative state operational state usage state
The administrative state indicates whether or not an operator has locked the component. The possible values for administrative state are locked, unlocked, and shutting down. The shutting down state means that an operator has issued the lock command and the component is in the process of moving from the unlocked to the locked state. The operational state indicates whether or not the component is operational. The possible values for operational state are enabled and disabled.
2.0S1
The usage state indicates whether or not the component is in use and whether or not it has spare capacity. The possible values for usage state are idle, active, and busy. An idle component is not in use. An active component is in use and has spare capacity. A busy component is in use but does not have spare capacity. Perform the following command in operational mode.
1 Display the OSI state of the component: display <component_name> OsiState where: <component_name> is the name of the component.
Performing diagnostic tests

Diagnostic tests allow you to test the hardware on your Passport node. If you suspect a hardware failure is causing a problem, use a diagnostic test. A diagnostic test involves the following steps: 1 2 3 4 Lock the component (not required for all diagnostic tests). Congure the test by setting the attributes in the Setup group of the Test component. Run the test. Examine the results stored in the attributes of the Results group.
Troubleshooting the node

You can usually trace node outage problems to power interrupts or a control processor failure (when a standby control processor is not available). See the table Troubleshooting node outage problems (page 159) for detailed troubleshooting information. The procedure Determining why the node is out of service (page 159) describes the steps for troubleshooting node outage problems.
241-5701-605 2.0S1
Chapter 4 Troubleshooting 159 Table 5 Troubleshooting node outage problems Symptom Entire Passport node is out of service (no components are functioning) Probable causes Loss of power to the cabinet Power converters failed All control processors have failed Corrective measures Restore power to the cabinet. Replace failed power converters. See Troubleshooting control processor problems (page 185).
Determining why the node is out of service

1 Verify that the cabinet is receiving power. The green LED labeled Power on the door of the cabinet is lit when the cabinet is receiving power. If the LED is not lit, restore power to the cabinet. For more information on the cabinet door LED, see 241-1501-210 Passport 15000 Hardware Installation Guide or 241-7401-210 Passport 7400 Hardware Installation Guide. 2 Verify that the power converters are receiving power. The LED on a power converter is lit when the converter is receiving power. For more information on the power converter LED, see 241-1501-210 Passport 15000 Hardware Installation Guide or 241-7401-210 Passport 7400 Hardware Installation Guide. Go to Troubleshooting control processor problems (page 185) to continue the troubleshooting analysis.
Troubleshooting the fabric card on a Passport 15000

If you detect a problem with the fabric card, you need to test the fabric card to determine the cause. The complete fabric card test actually has several tests which take place in the following order: 1 2 3 4 self test port test broadcast test ping test
2.0S1
Once all of the tests are complete, the ping test repeats continuously until the fabric card test ends. This repetition helps to detect transient fabric card faults. See the following sections for information on performing fabric card diagnostic tests: Testing a fabric card (page 160) Interpreting fabric card test results (page 161)
Testing a fabric card

The fabric card enables communication between the processor cards on your node. To test a fabric card, you need to lock it, leaving it unable to transport data from processor card to processor card. You need to test each of the two Passport fabric cards individually to prevent a node outage. While you are testing one fabric card, the other fabric card continues to provide service to the processor cards on the node. Perform the following commands in operational mode.
1 Lock the fabric card for testing purposes. The other fabric card must be unlocked and enabled; otherwise, the lock command fails. lock Shelf fabricCard/<n> where: <n> is either X or Y. 2 Set the maximum amount of time that you will allow the test to run: set Shelf fabricCard/<n> Test duration <limit_value> where: <n> is the instance value of the fabric card you are testing (either X or Y) <limit_value> species the maximum length of time, in minutes, that the fabric card test will run. The default is 2 minutes. You cannot change the time limit after the test has started. 3 Start the fabric card test: start Shelf fabricCard/<n> Test where: <n> is the instance value of the fabric card you are testing (either X or Y).
241-5701-605 2.0S1
Chapter 4 Troubleshooting 161 The test stops automatically if it detects a failure that prevents subsequent portions of the fabric card test from executing. Otherwise, the test continues for the specied duration. 4 If you want to end the test before the specied duration, enter stop Shelf fabricCard/<n> Test where: <n> is the instance value of the fabric card you are testing (either X or Y). 5 You can view the results of a test while the fabric card test is still in progress or after it has completed: display Shelf fabricCard/<n> Test Results where: <n> is the instance value of the fabric card you are testing (either X or Y). For information on the interpreting the results of the fabric card test, see Interpreting fabric card test results (page 161). 6 Once the test is complete, unlock the fabric card: unlock shelf fabricCard/<n> where: <n> is the instance value of the fabric card you locked in step 1.
Interpreting fabric card test results

The table Fabric card test result attributes and uses (page 162) describes each of the test result attributes and its possible values. The table Interpreting fabric card test results (page 164) describes the possible results of each fabric card test. For each test, the table suggests a number of remedial actions to correct certain problems. After you perform the remedial action, perform the fabric card test again. See Testing a fabric card (page 160).
2.0S1
162 Chapter 4 Troubleshooting Table 6 Fabric card test result attributes and uses Attribute Use Displays the reason the fabric card test ended. The reason can be one of the following: neverStarted: no one has started the fabric card test testRunning: the fabric card test is currently running testTimeExpired: the fabric card test ran for the specied duration stoppedByOperator: an operator issued a Stop Fabric Card Test command selfTestFailure: there was a failure during the fabric self-test portTestFailure: there was a failure during the port test broadcastFailure: there was a failure during the broadcast test
causeOfTermination
elapsedTime
timeRemaining
Displays the length of time (in minutes) that the fabric test has been running. Displays the maximum length of time (in minutes) that the fabric card test will continue to run before stopping. Displays the tests completed during the fabric card test. The attribute can have the value 0 or one of the following: selfTest: The fabric card self-test was completed. portTest: The port test was completed. broadcastTest: The broadcast test was completed. pingTest: At least one ping test was completed.
testsDone
selfTestResults
(Sheet 1 of 2)
Records the results of the fabrics self test. The result is either OK, failed, or noTest. The fabric test terminates automatically if a failure is detected.
241-5701-605 2.0S1
Chapter 4 Troubleshooting 163 Table 6 (continued) Fabric card test result attributes and uses Attribute Use Displays the results of the fabric port test, indexed by the slot numbers of the cards containing the fabric ports involved. Each entry has one of the following values: +: The port passed its self-test. X: The port failed its self-test. . : There was no test of the port.
portTestResults
Note: The port test terminates automatically if there is a failure in the fabric port test. broadcastTestResults Displays the results of the broadcast test, indexed by the slot numbers of the cards containing the fabric ports involved. Each entry has one of the following values assigned to it:
+: The transmitting fabric port successfully sent a broadcast message to the receiving fabric port. X: The transmitting fabric port did not successfully send a broadcast message to the receiving fabric port. . : There was no test of the associated pair of fabric ports.
Note: The fabric card test terminates automatically if there is a failure in the broadcast test. pingTests
Displays the number of ping tests completed for each fabric port, indexed by the slot numbers of cards containing the fabric ports involved. Each test attempts to transmit a single low-priority frame from the transmitting fabric port to the receiving fabric port. Displays the number of ping test failures, indexed by the slot numbers of the cards containing the fabric ports involved. Each failure represents a single low-priority frame that was not successfully transmitted from the transmitting fabric port to the receiving fabric port.
pingTestFailures
Note: The fabric card test does not terminate automatically if a failure occurs during this test.
(Sheet 2 of 2)
2.0S1
164 Chapter 4 Troubleshooting Table 7 Interpreting fabric card test results Test type Fabric card self-test Test result Remedial action
An entry in the selfTestResults attribute No remedial action is necessary. shows OK. The fabric card on the corresponding card passed the self-test. An entry in the selfTestResults attribute shows failed. The fabric card on the corresponding card failed the self test. The fabric card test terminates. An entry in the selfTestResults attribute If the card is not associated with an LP, shows noTest. There was no test of the no action is required. If the card is fabric card on the corresponding card. associated with an LP, run the test again. Replace the card. Rerun the test to verify that the problem has been corrected.
Port self-test
An entry in the portTestResults attribute No remedial action is necessary. shows a +. The port on the corresponding card passed the self-test. An entry in the portTestResults attribute Replace the card. Rerun the test to shows an X. The port on the verify that the problem has been corresponding card failed the self-test. corrected. The bus test terminates. An entry in the portTestResults attribute If the card is not associated with an LP, shows a .. There was no test of the port no action is required. If the card is on the corresponding card. associated with an LP, run the test again.
(Sheet 1 of 3)
241-5701-605 2.0S1
Chapter 4 Troubleshooting 165 Table 7 (continued) Interpreting fabric card test results Test type Broadcast test Test result An entry in the broadcastTestResults attribute shows a +. A broadcast frame was successfully sent from the transmitting fabric card to the receiving fabric card. An entry in the broadcastTestResults attribute shows an X. A broadcast frame was not successfully sent from the transmitting fabric card to the receiving fabric card. The fabric card test terminates. Remedial action No remedial action is necessary.
Replace the hardware item that is most likely to have failed (see below) and rerun the fabric card test. Repeat until the problem is corrected. The most likely point of failure is the cards corresponding to rows or columns containing X but not +, in order of decreasing number of Xs cards corresponding to rows or columns containing X and +, in order of decreasing number of Xs backplane
An entry in the broadcastTestResults If the card is not associated with an LP, attribute shows a .. The corresponding no action is required. If the card is associated with an LP, run the test pair of fabric cards was not tested. again.
(Sheet 2 of 3)
2.0S1
166 Chapter 4 Troubleshooting Table 7 (continued) Interpreting fabric card test results Test type Ping test Test result Remedial action
An entry in the pingTestFailures attribute No remedial action is necessary. is 0 and the corresponding entry in the pingTests attribute is equal to the largest entry in that table. The transmitting fabric card successfully sent a lowpriority frame to the receiving fabric card during each ping test. An entry in the pingTestFailures attribute is greater than 0 and the corresponding entry in the pingTests attribute is equal to the largest entry in that table. The transmitting fabric card did not successfully send a low-priority frame to the receiving fabric card during each ping test. Replace the hardware item that is most likely to have failed (see below) and rerun the fabric card test. Repeat until the problem is corrected. The most likely point of failure is the cards corresponding to rows or columns of ping test failures adding to a value greater than 0, in order of decreasing sums backplane An entry in the pingTests attribute is smaller than the largest entry. Some of the ping tests did not test the corresponding pair of fabric cards. No remedial action is necessary if either of the cards containing the fabric cards is associated with an LP. If either of the cards containing the fabric cards is associated with an LP, run the test again.
(Sheet 3 of 3)
Troubleshooting the bus on a Passport 7400 or Passport 8700 series switch

If you detect a problem with the bus, you should test the bus to determine the cause. The complete bus test actually has several tests which take place the following order: 1 2 3 bus tap self-test clock source test broadcast test
241-5701-605 2.0S1
ping test
Once all of the tests are complete, the ping test repeats continuously until the bus test ends. This repetition helps to detect transient bus faults. See the following sections for information on performing bus diagnostic tests: Testing a bus (page 167) Interpreting bus test results (page 168)
Testing a bus
The bus enables communication between the processor cards on your node. To test a bus you must lock it, leaving it unable to transport data from processor card to processor card. You must test each of the two Passport buses individually to prevent a node outage. While you are testing one bus, the other bus continues to provide service to the processor cards on the node. Perform the following steps in operational mode.
CAUTION
Testing a bus can result in loss of data
When you lock a bus to test it, total bus capacity decreases by half. Because of the reduced capacity, congestion can occur leading to data loss. Also, if problems occur on the unlocked bus, processor card crashes can occur. To reduce the risk of data loss, do not test a bus during peak periods of trafc.
1 Lock the bus for testing purposes. The other bus must be unlocked and enabled, otherwise the lock command fails. lock Shelf Bus/<n> where: <n> is either x or y. 2 Set the maximum amount of time that you will allow the test to run: set Shelf Bus/ Test duration <limit_value> where: is the instance value of the bus you are testing (either X or Y).
2.0S1
168 Chapter 4 Troubleshooting <limit_value> species the maximum length of time, in minutes, that the bus test will run. The default is 1 minute. You cannot change the time limit after the test has started. 3 Start the bus test: start Shelf Bus/ Test where: is the instance value of the bus you are testing (either X or Y). The test stops automatically if it detects a failure that prevents subsequent portions of the bus test from executing. Otherwise, the test continues for the specied duration. 4 If you want to end the test before the specied duration, enter: stop Shelf Bus/ Test where: is the instance value of the bus you are testing (either X or Y). 5 You can view the results of a test while the bus test is still in progress or after it has completed: display Shelf Bus/ Test Results where: is the instance value of the bus you are testing (either X or Y). For information on the interpreting the results of the bus test, see Interpreting bus test results (page 168). 6 Once the test is complete, unlock the bus: unlock shelf bus/ where: is the instance value of the bus you are testing (either X or Y).
Interpreting bus test results

The table Bus test result attributes and uses (page 169) describes each of the test result attributes and its possible values. The table Interpreting bus test results (page 171) describes the possible results of each bus test. For each test, the table suggests a number of remedial actions to correct certain problems. After you perform the remedial action, perform the bus test again. See Testing a bus (page 167).
241-5701-605 2.0S1
Chapter 4 Troubleshooting 169 Table 8 Bus test result attributes and uses Attribute Use
broadcastTestResults Displays the results of the broadcast test, indexed by the slot numbers of the cards containing the bus taps involved. Each entry has one of the following values assigned to it:
+: The transmitting bus tap successfully sent a broadcast message to the receiving bus tap. X: The transmitting bus tap did not successfully send a broadcast message to the receiving bus tap. . : There was no test of the associated pair of bus taps.
Note: The bus test terminates automatically if there is a failure in the broadcast test. causeOfTermination
Displays the reason the bus test ended. The reason can be one of neverStarted: no one has started the bus test testRunning: the bus test is currently running testTimeExpired: the bus test ran for the specied duration stoppedByOperator: an operator issued a Stop Bus Test command selfTestFailure: there was a failure during the bus tap self-test clockSourceFailure: there was a failure during the test of the active CP clock source broadcastFailure: there was a failure during the broadcast test
clockSourceTestResu Displays the results of the clock source test, indexed by the clock source lts and the slot numbers of the cards containing the bus taps involved. Each entry has one of the following values:
+: The bus tap was able to receive clock signals from the clock source. X: The bus tap was unable to receive clock signals from the clock source. . : There was no test of the bus tap against the clock source.
Note: The bus tap self-test terminates automatically if there is a failure involving the active control processor (CP) clock source.
(Sheet 1 of 2)
2.0S1
170 Chapter 4 Troubleshooting Table 8 (continued) Bus test result attributes and uses Attribute Use Displays the length of time (in minutes) that the bus test has been running. Displays the number of ping test failures, indexed by the slot numbers of the cards containing the bus taps involved. Each failure represents a single low-priority frame that did not successfully transmit from the transmitting bus tap to the receiving bus tap.
elapsedTime pingTestFailures
Note: The bus test does not terminate automatically if a failure occurs during this test. pingTests
Displays the number of ping tests completed for each bus tap, indexed by the slot numbers of cards containing the bus taps involved. Each test attempts to transmit a single low-priority frame from the transmitting bus tap to the receiving bus tap. Displays the results of the bus tap self-test, indexed by the slot numbers of the cards containing the bus taps involved. Each entry has one of the following values: +: The bus tap passed its self-test. X: The bus tap failed its self-test. . : There was no test of the bus tap.
selfTestResults
Note: The bus test terminates automatically if there is a failure in the bus tap self-test. testsDone
Displays the tests completed during the bus test. The attribute can have the value 0 or one of the following: selfTest: The bus tap self-test was completed. clockSourceTest: The clock source test was completed. broadcastTest: The broadcast test was completed. pingTest: At least one ping test was completed.
timeRemaining
(Sheet 2 of 2)
Displays the maximum length of time (in minutes) that the bus test will continue to run before stopping.
241-5701-605 2.0S1
Chapter 4 Troubleshooting 171 Table 9 Interpreting bus test results Test type Bus tap selftest Test result Remedial action
An entry in the selfTestResults attribute No remedial action is necessary. shows a +. The bus tap on the corresponding card passed the self-test. An entry in the selfTestResults attribute shows an X. The bus tap on the corresponding card failed the self-test. The bus test terminates. An entry in the selfTestResults attribute If the card is not associated with an LP, shows a .. There was no test of the bus no action is required. If the card is tap on the corresponding card. associated with an LP, run the test again. Replace the card. Rerun the test to verify that the problem has been corrected.
(Sheet 1 of 4)
2.0S1
172 Chapter 4 Troubleshooting Table 9 (continued) Interpreting bus test results Test type Test result Remedial action No remedial action is necessary.
Clock source An entry in the clockSourceTestResults test attribute shows a +. The bus tap on the corresponding card was able to receive clock signals from the specified clock source. An entry in the clockSourceTestResults attribute shows an X. The bus tap on the corresponding card was unable to receive clock signals from the specified clock source. If the clock source being tested is the active control processor clock source the bus test is terminated before going on to the next test.
Replace the hardware item that is most likely to have failed (see below) and rerun the bus test. Repeat until the problem is corrected. The following are the most likely points of failure, in order, if a clock source fails for only one card: card that failed test card containing the clock source backplane The following are the most likely points of failure, in order, if a clock source fails for multiple cards: card containing the clock source cards that failed test backplane The card at the opposite end of the shelf from the active control processor provides the alternate clock source. If the slot is empty, no alternate clock source is available.
An entry in the clockSourceTestResults attribute shows a .. There was no test of the bus tap on the corresponding card against the specified clock source.
(Sheet 2 of 4)
If the card is not associated with an LP, no action is required. If the card is associated with an LP, run the test again.
241-5701-605 2.0S1
Chapter 4 Troubleshooting 173 Table 9 (continued) Interpreting bus test results Test type Broadcast test Test result Remedial action
An entry in the broadcastTestResults No remedial action is necessary. attribute shows a +. A broadcast frame was successfully sent from the transmitting bus tap to the receiving bus tap. An entry in the broadcastTestResults attribute shows an X. A broadcast frame was not successfully sent from the transmitting bus tap to the receiving bus tap. The bus test terminates. Replace the hardware item that is most likely to have failed (see below) and rerun the bus test. Repeat until the problem is corrected. The most likely point of failure is the cards corresponding to rows or columns containing X but not +, in order of decreasing number of Xs cards corresponding to rows or columns containing X and +, in order of decreasing number of Xs backplane An entry in the broadcastTestResults If the card is not associated with an LP, attribute shows a .. The corresponding no action is required. If the card is associated with an LP, run the test pair of bus taps was not tested. again.
(Sheet 3 of 4)
2.0S1
174 Chapter 4 Troubleshooting Table 9 (continued) Interpreting bus test results Test type Ping test Test result Remedial action
An entry in the pingTestFailures attribute No remedial action is necessary. is 0 and the corresponding entry in the pingTests attribute is equal to the largest entry in that table. The transmitting bus tap successfully sent a low-priority frame to the receiving bus tap during each ping test. An entry in the pingTestFailures attribute is greater than 0 and the corresponding entry in the pingTests attribute is equal to the largest entry in that table. The transmitting bus tap did not successfully send a low-priority frame to the receiving bus tap during each ping test. Replace the hardware item that is most likely to have failed (see below) and rerun the bus test. Repeat until the problem is corrected. The most likely point of failure is the cards corresponding to rows or columns of ping test failures adding to a value greater than 0, in order of decreasing sums backplane An entry in the pingTests attribute is smaller than the largest entry. Some of the ping tests did not test the corresponding pair of bus taps. If the card is not associated with an LP, no action is required. If the card is associated with an LP, run the test again.
(Sheet 4 of 4)
Troubleshooting function processors

Function processors can experience problems with hardware and software integrity. Bus and fabric card failure and provisioning errors can also create function processor problems. See the table Troubleshooting function processor problems (page 175) for detailed troubleshooting information. See the following sections for more information on troubleshooting function processors: Methods for detecting function processor problems (page 177) Determining why a function processor does not load software (page 181)
241-5701-605 2.0S1
Determining the cause of a function processor crash (page 182) Collecting diagnostic information (page 183)
For information on handling symptoms that can occur when installing an OC-48 FP in a Passport 15000, see the troubleshooting section in NTP 241-1501-610 Passport 15000 FP Conguration and Testing Guide.
Table 10 Troubleshooting function processor problems Symptom Function processor does not load Probable causes Processor failure Corrective measures Replace the function processor. See 241-1501-210 Passport 15000 Hardware Installation Guide or 241-7401-210 Passport 7400 Hardware Installation Guide. See Troubleshooting the file system (page 194).
File system failure Fabric card failure
Contact Nortel Networks (see 241-1501-030 Passport 15000 Note: This cause applies only Overview). to the Passport 15000. Contact Nortel Networks (see 241-7401-030 Passport 7400 Note: This cause applies only Overview). to the Passport 7400 series switch. Configuration error Unsupported PEC Examine the provisioning data and reconfigure as necessary. Bus failure
Replace with a card supported by Passport 7400. See Note: This cause applies only 241-7401-200 Passport 7400 to the Passport 7400 series Hardware Description for a list switch. of cards supported by Passport 7400.
(Sheet 1 of 2)
2.0S1
176 Chapter 4 Troubleshooting Table 10 (continued) Troubleshooting function processor problems Symptom Function processor crashes Probable causes Hardware failure Corrective measures Replace the function processor. See 241-1501-210 Passport 15000 Hardware Installation Guide or 241-7401-210 Passport 7400 Hardware Installation Guide. Collect diagnostic information for the processor card and then contact Nortel Networks technical support. See 241-1501-030 Passport 15000 Overview or 241-7401-030 Passport 7400 Overview. Reduce the number of applications running on the function processor. Check whether the function processor has been in storage.
Software problem
Memory exhaustion
Function processor does not load and the Passport continually attempts to reboot
If an older Passport shelf (ac shelf NTBP05AA or DC shelf NTBP64AA) is available, use that shelf to load the function processor with R1.2.3 or higher software. You can then install the function processor in the Note: This cause applies only newer shelf. to the Passport 7400 series If an older Passport shelf is not switch. available, contact Nortel Networks technical support for further instructions (see 241-7401-030 Passport 7400 Overview). Do not return the function processor to Nortel Networks.
Incompatibility of the function processors firmware with the Passports newer shelf (ac shelf NTBP05BA or higher, or DC shelf NTBP64BA or higher). This problem can happen when you use an older function processor card that has been held in storage.
(Sheet 2 of 2)
241-5701-605 2.0S1
Methods for detecting function processor problems

The table Methods for detecting function processor problems (page 178) details ways of detecting function processor problems and suggests actions to take. One of the main indicators of a problem with a processor card is its LED status display. The table LED status display (page 180) describes the meaning of the various colors of the processor card LED display.
2.0S1
178 Chapter 4 Troubleshooting Table 11 Methods for detecting function processor problems Observation The LED status display on the card is red (see LED status display (page 180)). Action Replace the card with another card of the same type that you know is working. (For instructions, see 241-1501-210 Passport 15000 Hardware Installation Guide or 241-7401-210 Passport 7400 Hardware Installation Guide.) If the problem persists, see troubleshooting procedures in Troubleshooting function processors (page 174). If you resolve the problem by replacing the suspect card with a known functioning card, contact your local Nortel Networks technical support group (see 241-1501-030 Passport 15000 Overview or 241-7401-030 Passport 7400 Overview), and arrange to return the defective card. For instructions on packing the card, see 241-1501-210 Passport 15000 Hardware Installation Guide or 241-7401-210 Passport 7400 Hardware Installation Guide. The LED status display on the card is red and the function processor continually attempts to reboot. The function processors firmware is incompatible with your Passports newer shelf (ac shelf NTBP05BA or higher, or DC shelf NTBP64BA or higher). This problem can happen when you use an older function processor card. Check whether the function processor has been in storage. If an older Passport shelf (ac shelf NTBP05AA or DC shelf NTBP64AA) is available, use that shelf to load the function processor with R1.2.3 or higher software. You can then install the function processor in the newer shelf. If an older Passport shelf is not available, contact your local Nortel Networks technical support group for further instructions. Do not return the function processor to Nortel Networks.
(Sheet 1 of 3)
Note: This observation applies to the Passport 7400 series switch only.
241-5701-605 2.0S1
Chapter 4 Troubleshooting 179 Table 11 (continued) Methods for detecting function processor problems Observation Action
The LED status display on the card is solid Make sure that you have provisioned the right type amber. of FP. For Passport 7400, make sure that card has a valid PEC. See 241-7401-200 Passport 7400 Hardware Description for a list of cards supported by Passport 7400. The appropriate LED on the sparing panel Check if the fuse on the associated card is blown. is not lit. Replace the card with another card of the same type that you know is working. (For instructions, see 241-1501-210 Passport 15000 Hardware Installation Guide or 241-7401-210 Passport 7400 Hardware Installation Guide.) If you resolve the problem by replacing the suspect card with a known functioning card, contact your local Nortel Networks technical support group (see 241-5701-270 Passport 7400, 8700, 15000 Software Installation Guide), and arrange to return the defective card. For instructions on installing, removing and packing the card, see 241-1501-210 Passport 15000 Hardware Installation Guide or 241-7401-210 Passport 7400 Hardware Installation Guide. An alarm occurs to indicate there is a problem with the card or with the far-end card. You detect a problem while running diagnostic tests or while performing node troubleshooting. See 241-5701-500 Passport 6400, 7400, 8700, 15000 Alarms. See Troubleshooting function processors (page 174).
Frame loss or framing errors are occurring. Set the clockingSource attributes of the ports as one of the following combinations: local at one end and line at the other, module at one end and line at the other, or module at both ends.
(Sheet 2 of 3)
2.0S1
180 Chapter 4 Troubleshooting Table 11 (continued) Methods for detecting function processor problems Observation A link problem is occurring, possibly caused by the card. Action Check to make sure the provisioning data is correct. Ensure that the required modem signals (readyLineState and dataTransferLineState) are provisioned to the ON state and that connecting device is supplying the expected incoming modem signals. Check cable connections. Make sure the connectors have no bent pins. Make sure that you are using the correct termination panel for the card. (See 241-1501-030 Passport 15000 Overview or 241-7401-030 Passport 7400 Overview.) For function processors that use an optical connection: Check cable connections. Make sure the optical connectors are clean. Check to ensure that the pins on the optical bypass switch are not bent. Termination panel lights do not come on.
(Sheet 3 of 3)
Check cable pins for breakage.
Table 12 LED status display LED display No color Solid red Card status No power is reaching the card. Card is powered and is either performing self-tests or, after 30 seconds, is faulty. For Passport 15000, the card may also be locked. Slow pulsing red
(Sheet 1 of 2)
Card has passed self-tests but has not yet fully loaded its software.
241-5701-605 2.0S1
Chapter 4 Troubleshooting 181 Table 12 (continued) LED status display LED display Slow pulsing green Card status Cards software is fully loaded but not yet activated. It may be initializing or in standby mode. For Passport 7400, the card may also be locked. Fast pulsing green Solid green Solid amber Card is running as standby. Card is in active service. Card is not faulty, but cannot operate. (For example, the slot was provisioned for one card type but another type was inserted or, for Passport 7400, the card is unsupported.)
(Sheet 2 of 2)
Determining why a function processor does not load software

There are ve possible causes when a function processor does not load its software: processor card failure, le system failure, bus failure, fabric card failure, or conguration. Use the following procedures to determine which of these conditions is preventing the function processor from loading its software. Perform the following steps in operational mode.
1 Determine the OSI states of the function processor: display Shelf Card/<m> OsiState where: <m> is the slot number of the function processor. If adminState is unlocked, operationalState is enabled, and usageState is active, the function processor is operational. Exit this procedure. 2 Test the card using the procedures in 241-1501-610 Passport 15000 FP Conguration and Testing Guide or 241-7401-610 Passport 7400 FP Conguration and Testing Guide. Remove and reinsert the failed function processor. If this action corrects the problem, exit this procedure and monitor the function processor for reoccurrences. If the problem persists, go to step 4.
2.0S1
182 Chapter 4 Troubleshooting 4 Replace the failed function processor. If this action corrects the problem, exit this procedure and return the failed function processor for repair. 5 Determine the OSI states for the le system: display Fs OsiState If adminState is unlocked, operationalState is enabled, and usageState is active, the le system is functioning. If any of the OSI state attributes for the le system have values other than those shown above, the le system is not available. Go to Troubleshooting the le system (page 194) to continue the troubleshooting analysis. 6 If you are working with a Passport 15000, determine the cardPortStatus of the fabric card ports: display Shelf FabricCard/<n> CardPort/<m> cardPortStatus If cardPortStatus is OK for the function processor slot, you have veried that the fabric card is functioning. If cardPortStatus is none or is failed, replace the function processor. Try using a different slot to provide service until you can replace the shelf. If the fabric card still does not function, contact Nortel Networks. 7 If you are working with a Passport 7400 series switch, determine the busTapStatus of the bus taps: display Shelf Bus/* busTapStatus If busTapStatus is OK for the function processor slot, you have veried that the bus is functioning. If busTapStatus is none or busTapStatus is failed, replace the function processor. Try using a different slot to provide service until you can replace the shelf. If the bus tap still does not function, contact Nortel Networks.
Determining the cause of a function processor crash

When a function processor crashes, use the following procedure to determine the cause.
241-5701-605 2.0S1
Perform the following commands in operational mode.

1 2 Collect diagnostic information about the function processor crash. See Collecting diagnostic information (page 183). Replace the failed function processor. If this action corrects the problem, exit this procedure and return the failed function processor for repair. 3 Determine the memory utilization for the processor card: display Shelf Card/<m> Utilization, Capacity where: <m> is the slot number of the function processor Compare the memory and message block usage against the capacity for the card. If the memory is near or at exhaustion, exit this procedure and reduce the number of features running on the function processor. See Conguring the software features of an LPT (page 114). 4 Open a customer service request for Nortel Networks if the previous steps fail to resolve the problem. See 241-1501-030 Passport 15000 Overview or 241-7401-030 Passport 7400 Overview. Include the diagnostic information collected in step 1 for analysis.
Collecting diagnostic information

When a processor card detects a critical fault or a recoverable error, it stores diagnostic information about the error, even if the processor reloads. Nortel Networks support personnel can analyze this diagnostic information and use it for troubleshooting. You can collect diagnostic information about the last critical fault and the last recoverable error on a processor card by displaying operational subcomponents of the Card component. These components contain line-byline detail of the last critical fault (trap data) and last recoverable error. Once you have displayed the diagnostic information and stored it for analysis, you can clear the information from the processor. You can also collect diagnostic information for analysis by turning on the spooling of debug data to a le and then recreating the error. After you have recreated the error, the diagnostic information is contained in the debug data le.
2.0S1
If a function processor that does not load has been in storage, see the table Troubleshooting function processor problems (page 175) before collecting diagnostic information. Perform the following commands in operational mode.
1 2 Start a telnet session to the Passport node that is set to log screen output to a le. Display the diagnostic information about the last critical fault on the processor: display Shelf Card/<m> Diag TrapData Line/* where: <m> is the slot number of the processor. 3 Display the diagnostic information about the last recoverable error on the processor: display Shelf Card/<m> Diag RecoverableError Line/* where: <m> is the slot number of the processor. 4 When you are certain the diagnostic information has successfully been logged to a le, clear it from memory: clear Shelf Card/<m> Diag TrapData clear Shelf Card/<m> Diag RecoverableError where: <m> is the slot number of the processor.
Troubleshooting control processors

The most common problems with a control processor are software load failures and crashes. These problems can affect both the active and the standby control processor. The table Troubleshooting control processor problems (page 185) provides detailed troubleshooting information for control processors. See the following sections for more information on troubleshooting control processors:
241-5701-605 2.0S1
Determining why a control processor does not load (page 189)
Determining why the standby control processor does not load (page 189) Determining the cause of a control processor crash (page 190)
Table 13 Troubleshooting control processor problems Symptom Control processor does not load. Probable causes Processor failure Corrective measures Replace the control processor. See Replacing a control processor in a single-CP node (page 99) or Replacing a control processor in a two-CP node (page 105).
Contact Nortel Networks (see 241-1501-030 Passport 15000 Note: This cause applies only Overview). to the Passport 15000. Replace with a card supported by Passport 7400. See Note: This cause applies only 241-7401-200 Passport 7400 to the Passport 7400 series Hardware Description for a list switch. of cards supported by Passport 7400.
(Sheet 1 of 4)
Fabric card failure
Unsupported PEC
2.0S1
186 Chapter 4 Troubleshooting Table 13 (continued) Troubleshooting control processor problems Symptom Control processor does not load and the Passport continually attempts to reboot. Probable causes Corrective measures Check if the control processor has been in storage. If an older Passport shelf (AC shelf NTBP05AA or DC shelf NTBP64AA) is available, use that shelf to load the control processor with R1.2.3 or higher software. You can then install the control processor in the newer shelf. If an older Passport shelf is not available, contact Nortel Networks technical support for further instructions (see 241-7401-030 Passport 7400 Overview). Do not return the control processor to Nortel Networks. Control processor crashes. Hardware failure Replace the control processor. See Replacing a control processor in a single-CP node (page 99) or Replacing a control processor in a two-CP node (page 105). Collect diagnostic information for the control processor and contact Nortel Networks technical support. See 241-1501-030 Passport 15000 Overview or 241-7401-030 Passport 7400 Overview. Reduce the number of applications running on the Passport node.
Incompatibility of the control processors firmware with the Passports newer shelf (AC shelf NTBP05BA or higher, or Note: This symptom applies to DC shelf NTBP64BA or the Passport 7400 series higher). This problem can switch only. happen when you use an older control processor card that has been held in storage.
Software problem
Memory exhaustion
(Sheet 2 of 4)
241-5701-605 2.0S1
Chapter 4 Troubleshooting 187 Table 13 (continued) Troubleshooting control processor problems Symptom Control processor switchover. Probable causes OAM Ethernet port failure Corrective measures Troubleshoot the OAM Ethernet port. See Troubleshooting the OAM Ethernet port (page 191).
(Sheet 3 of 4)
2.0S1
188 Chapter 4 Troubleshooting Table 13 (continued) Troubleshooting control processor problems Symptom Standby control processor does not load. Probable causes Processor failure Corrective measures Replace the control processor. See Replacing a control processor in a single-CP node (page 99) or Replacing a control processor in a two-CP node (page 105). See Troubleshooting the file system (page 194).
File system failure Fabric card failure
Contact Nortel Networks. See 241-1501-030 Passport 15000 Note: This cause applies to the Overview Passport 15000 only. Contact Nortel Networks. See 241-7401-030 Passport 7400 Note: This cause applies to the Overview Passport 7400 series switch only. Standby control processor Incompatibility of the control does not load and the Passport processors firmware with the continually attempts to reboot. Passports newer shelf (AC shelf NTBP05BA or higher, or Note: This symptom applies to DC shelf NTBP64BA or the Passport 7400 series higher). This problem can switch only. happen when you use an older control processor card that has been held in storage. Check if the control processor has been in storage. If an older Passport shelf (AC shelf NTBP05AA or DC shelf NTBP64AA) is available, use that shelf to load the control processor with R1.2.3 or higher software. You can then install the control processor in the newer shelf. If an older Passport shelf is not available, contact Nortel Networks technical support for further instructions (see 241-7401-030 Passport 7400 Overview). Do not return the control processor to Nortel Networks.
(Sheet 4 of 4)
Bus failure
241-5701-605 2.0S1
Determining why a control processor does not load

There are a number of reasons why a control processor does not load. Perform the following steps.
1 Verify that one of the control processors is attempting to load. The control processors LED ashes red whenever the control processor is loading. If the control processor is loading, wait a few minutes to determine if the attempt to load is likely to succeed. If the load attempt is successful, exit this procedure. If the load attempt fails, go to step 2. 2 Remove and reinsert the control processor. If this action corrects the problem, exit this procedure and monitor the control processor for reoccurrences. If the problem persists, go to step 3. 3 Monitor the information output of the control processor on the local terminal as the control processor attempts to load. If the information output indicates that a specic le cannot be loaded from the disk, then the disk is corrupt. Replace the control processor and restore the disk from a backup copy using the procedure in 241-6001-023 NMS Architect for Passport User Guide.
Note: If you are using redundant control processors and the standby control processor now crossloads, reformat the standby control processors disk. See Formatting a disk (page 129).
If the loading information indicates that bus errors are occurring, contact Nortel Networks (see 241-1501-030 Passport 15000 Overview or 241-7401-030 Passport 7400 Overview).
Determining why the standby control processor does not load

There are a number of reasons why a standby control processor does not load. Perform the following steps in operational mode.
1 Test the control processor using the procedures from 241-1501-610 Passport 15000 FP Conguration and Testing Guide or 241-7401-610 Passport 7400 FP Conguration and Testing Guide. Replace the standby control processor. See Replacing a control processor in a single-CP node (page 99) or Replacing a control processor in a two-CP node (page 105). If this
2.0S1
190 Chapter 4 Troubleshooting action corrects the problem, exit this procedure and return the failed control processor for repair. 3 Determine the OSI states for the le system: display Fs OsiState If adminState is unlocked, operationalState is enabled, and usageState is active, the le system is functioning. If any of the OSI state attributes for the le system have values other than those shown above, the le system is not available. Go to Troubleshooting the le system (page 194) to continue the troubleshooting analysis. 4 If you are using a Passport 15000, determine the cardPortStatus of the fabric card ports: display Shelf FabricCard/<n> CardPort/* If CardPortStatus is OK for the standby control processor slot, you have veried that the fabric is functioning. If CardPortStatus is none or is failed, replace the standby control processor. See Replacing a control processor in a single-CP node (page 99) or Replacing a control processor in a two-CP node (page 105). If the fabric card port still does not function, contact Nortel Networks. 5 If you are using a Passport 7400 series switch, determine the busTapStatus of the bus taps: display Shelf Bus/* busTapStatus If busTapStatus is OK for the standby control processor slot, you have veried that the bus is functioning. If busTapStatus is none or busTapStatus is failed, replace the standby control processor. See Replacing a control processor in a single-CP node (page 99) or Replacing a control processor in a two-CP node (page 105). If the bus tap still does not function, contact Nortel Networks.
Determining the cause of a control processor crash

1 Collect diagnostic information about the control processor crash. See Collecting diagnostic information (page 183).
241-5701-605 2.0S1
Chapter 4 Troubleshooting 191 2 Replace the failed control processor. See Replacing a control processor in a single-CP node (page 99) or Replacing a control processor in a two-CP node (page 105). If this corrects the problem, exit this procedure and return the failed control processor for repair. 3 Determine the memory utilization for the control processor: display Shelf Card/<m> Utilization, Capacity where: <m> is the slot number of the control processor. Compare the memory and message block usage against the capacity for the control processor. If the memory is near or at exhaustion, exit this procedure and reduce the number of features running on the Passport node. See Conguring the software features of an LPT (page 114). 4 Open a customer service request for Nortel Networks if the previous steps fail to resolve the problem. See 241-1501-030 Passport 15000 Overview or 241-7401-030 Passport 7400 Overview. Include the diagnostic information collected in step 1 for analysis.
Troubleshooting the OAM Ethernet port

There are two conditions related to the OAM Ethernet port component that can cause a CP switchover. Failure of the initial port test: If the switchoverOnFailure attribute is set to enabled, the operational attribute standbyStatus has the value available. Any failure of the initial port tests on the Ethernet port initiates a CP switchover. Failure of the steady state link: If there is an absence of trafc on the link for a period of more than 25 seconds, a time domain reectometry (TDR) test is performed on the link. If the TDR test fails and the switchoverOnFailure and standbyStatus attributes are set to enabled and available respectively, a CP switchover occurs. Note: If either of these two error conditions occur, only one CP switchover happens. The operational attributes activeStatus and standbyStatus allow the port to keep track of the states of both OAM Ethernet ports so that the CP can correctly determine when a switchover is appropriate.
2.0S1
Note: If switchoverfailure is enabled and lp/0 oamenet standbystatus is set to available, an approximate two minute loss of Ethernet connectivity on both standby and active CP OAM Ethernet ports will trigger a CP switchover and an OAM Ethernet port initialization failure on the new active CP. The OAM Ethernet port will be locked and no other telnet connections can be established until you lock or unlock the active CP OAM Ethernet port. Note: If the OAM Ethernet port test fails during the initialization of an active CP, the CP Ethernet port will remain locked in the not available state even if the cause of the failure disappears. For example, if the Ethernet cable is disconnected and then reconnected, the CP Ethernet port will remain locked in the not available state. See the following sections for information on testing the OAM Ethernet port: Types of OAM Ethernet port tests (page 192) Testing the OAM Ethernet port (page 192)
Types of OAM Ethernet port tests

There are four tests that you can execute on the Ethernet port. The rst three verify the port device; the fourth one veries the link. The hardware test veries the Ethernet controller hardware logic. The conguration test veries the conguration of the device driver. The memory map test veries the memory map for receive and transmit buffers lists. The TDR test detects open or short circuits and their distance from the port.
Testing the OAM Ethernet port

241-5701-605 2.0S1
CAUTION
Potential loss of NMS connectivity
Locking the OAM Ethernet port disconnects all connections to the Passport that use this port. Ensure that the connection through which you are issuing the lock command does not use the OAM Ethernet port.
1 Lock the OAM Ethernet port: lock -force -forever Lp/0 oamEnet/0
Note 1: Use the -force option to place the port in an immediate locked state, without going through the shutting down state. Note 2: Use the -forever option to lock the port permanently until you issue an unlock command. Without this option, the port locks for a maximum of 5 minutes before being unlocked automatically.
2 Assign the type of test to be conducted: set Lp/0 oamEnet/0 Test type <type> where: <type> is one of hardwareLogic, conguration, memoryMap, or tdr.
Note: These four tests are mutually exclusive. They cannot execute concurrently.
3 Initiate the test: start Lp/0 oamEnet/0 Test
Note: It is not necessary to use the stop command as the test takes a very small amount of time to execute. If an error occurs and the test does not terminate properly, the hardware detects this and terminates the test.
4 Review the results of the test: display Lp/0 oamEnet/0 Test The tests return pass/fail information. If an Ethernet port fails any test, switch to the standby CP and contact your Nortel Networks representative. 5 If the Ethernet port passes all tests, unlock the port: unlock Lp/0 oamEnet/0
2.0S1
Troubleshooting the le system

File system problems relate to either the le system software or to the disk subsystem on the control processor. The table Troubleshooting le system problems (page 194) details how to troubleshoot the le system. See the following sections for more information on troubleshooting the le system: Determining why a le cannot be saved (page 195) Determining why the le system is not operational (page 196) Testing a disk (page 197) Interpreting disk test results (page 200)
Table 14 Troubleshooting file system problems Symptom File system not operational Probable causes File system locked All disks failed Corrective measures Issue unlock Fs command. Replace the control processors. See Replacing a control processor in a singleCP node (page 99) or Replacing a control processor in a two-CP node (page 105).
(Sheet 1 of 2)
241-5701-605 2.0S1
Chapter 4 Troubleshooting 195 Table 14 (continued) Troubleshooting file system problems Symptom Cannot save to disk Probable causes File system locked Disks are full Corrective measures Issue the unlock Fs command. Remove unnecessary files from the disk. To remove unnecessary provisioning files, issue the tidy Prov command. To remove unnecessary spooling files use the Management Data Provider, or issue the remove Fs command. To remove unnecessary software files, see 241-5701-270 Passport 7400, 8700, 15000 Software Installation Guide.
(Sheet 2 of 2)
Determining why a le cannot be saved

If you cannot save a le, there are two possible causes: the le system is not functioning or it is full. The following procedure helps you determine why you cannot save a le. Perform the following steps in operational mode.
1 Determine the OSI states for the le system: display Fs OsiState If adminState is unlocked, operationalState is enabled, and usageState is active, the le system is functioning. Exit this procedure. If any of the OSI state attributes for the le system have values other than those shown above, the le system is not available. See the procedure Determining why the le system is not operational (page 196) to continue through troubleshooting analysis. 2 Determine the available free space on the le system: display Fs freeSpace
2.0S1
196 Chapter 4 Troubleshooting If the available free space is less than the size of the le to be saved, remove any unnecessary les from the disk. To remove unnecessary provisioning les, issue the tidy Prov command. To remove unnecessary spooling les use the Management Data Provider, or issue the remove Fs command. To remove unnecessary software les, see 241-5701-270 Passport 7400, 8700, 15000 Software Installation Guide.
Determining why the le system is not operational

1 Determine the OSI states for the le system: display Fs OsiState If adminState is unlocked, operationalState is enabled, and usageState is active, the le system is functioning. Exit this procedure. If adminState is locked, consult with the operator who took the le system out of service to verify that the le system can now be unlocked and then issue the unlock Fs command. Exit this procedure. If operationalState is disabled, it is likely that all disks have failed. Go to step 2. 2 Lock and unlock the failed le system: lock Fs unlock Fs By locking and then immediately unlocking the failed le system, you can sometimes clear a software related problem. 3 Determine the OSI states for the disks: display Fs Disk/* OsiState If operationalState is disabled for a given disk, that disk has failed. 4 Lock and unlock the failed disk: lock Fs Disk/<n> unlock Fs Disk/<n> where: <n> is the number of the failed disk. The disk number corresponds to the slot number of the control processor holding the disk.
241-5701-605 2.0S1
Chapter 4 Troubleshooting 197 By locking and then immediately unlocking the failed disk, you can sometimes clear a software related problem. If the disk still fails, go to step 5. 5 Perform a disk test. See Testing a disk (page 197). 6 If the previous steps have failed to restore the disk, replace the control processor that holds the failed disk. See Replacing a control processor in a single-CP node (page 99) or Replacing a control processor in a twoCP node (page 105).
Testing a disk
Test a disk only when you suspect a fault in the disk hardware. Note that you cannot test the disk on the active control processor. The procedure Testing a disk (page 198) details how to test a disk. The disk tests cannot tolerate any interruptions from normal disk operations, so you must lock the disk before testing it. A locked disk cannot perform normal disk operations. There are four types of tests for disks: Disk read testreads every sector on the disk once, marking bad sectors. If the test detects an error, proceed with the le system check test. This test takes about four minutes. Flaky bit detection testreads every sector on the disk twice and compares the two read results. If the test reveals an error, proceed with the le system check test. This test takes about eight minutes. File system check testperforms a le system sanity check, frees lost clusters, and attempts to correct bad sectors. This test takes a few seconds. You must run the le system check test if either the disk read test or aky bit detection test indicate errors. Surface analysis testwrites a pattern to the disk and reads back the pattern to determine the condition of the magnetic surface of the disk. This test destroys the contents of the disk. Only use this test if all other disk tests have failed to reveal the error. This test takes about 16 minutes.
2.0S1
Only test the standby disk on a dual-disk node. If the disk you want to test is currently active, switch control between the active and standby control processors. See Switching between active and standby processor cards (page 124). Testing a disk Perform the following steps in operational mode.
CAUTION
Risk of operational data records loss
Performing a disk test can cause a loss of operational data. When you lock a disk on a single-CP node, Passport cannot spool operational data records to the disk.
CAUTION
Risk of data loss
Never initiate a surface analysis test on a single-disk system. The test erases all data on the disk and reformats the disk.
1 Set the test type: set Fs Disk/<n> Test type <type> where: <n> is the number of the disk to be tested. The disk number corresponds to the slot number of the control processor that holds the disk. <type> is one of diskRead, akyBitDetection, lesystemCheck, or surfaceAnalysis. 2 If you are working on a single-disk node, lock the le system: lock Fs 3 Lock the disk: lock Fs Disk/<n> where: <n> is the number of the disk to be tested. 4 Start the test:
241-5701-605 2.0S1
Chapter 4 Troubleshooting 199 start Fs Disk/<n> Test where: <n> is the number of the disk to be tested. 5 If you want to stop the test before it is complete, enter stop Fs Disk/<n> Test where: <n> is the number of the disk being tested.
Note: The test does not always stop immediately. The test completes its current cycle before ending.
6 Unlock the disk: unlock Fs Disk/<n> where: <n> is the number of the disk that was tested. 7 If you previously locked the le system, unlock it: unlock Fs If you performed a surface analysis test, proceed with step 8. If you are doing any other disk tests, proceed to step 10. 8 If you performed a surface analysis test, reset the control processor: reset Shelf Card/<m> where: <m> is the number of the control processor containing the disk you tested. The standby control processor (CP) attempts to load from its disk four times before it initiates a crossload from the active CP. 9 When the standby CP comes up, use the sync command to restore le system synchronization: sync Fs 10 Display the disk test results: display Fs Disk/<n> Test Results where: <n> is the number of the disk that you tested. See Interpreting disk test results (page 200) for information on the values of the result attributes. Passport 7400, 8700, 15000 Operations and Maintenance Guide 2.0S1
Interpreting disk test results

The table Disk test results (page 200) describes the possible results of the disk tests.
Table 15 Disk test results Attribute Use
causeOfTermination Displays the reason the disk test ended. The reason can be one of the following:
testCountReached: The test ran the specied number of times in the attribute testCount and ended normally. error: An error terminated the test. The error is described in the natureOfError attribute. neverStarted: The disk test has not started. stoppedByOperator: An operator issued a Stop Shelf Disk Test command. testTimeExpired: The duration of the test expired. testRunning: The test is still running. unknown: The test terminated for unknown reasons. internalError: An internal error terminated the test.
elapsedTime natureOfError
Displays the elapsed time (in minutes) since the test started. Describes the type of the error found by a test. The type of error can be one of the following: logical: A lesystem check test followed by a synchronization can x the error. media: There is a suspected fault in the disk hardware. failedToComplete: The test terminated.
results
(Sheet 1 of 2)
Displays all results associated with the attributes in this table.
241-5701-605 2.0S1
Chapter 4 Troubleshooting 201 Table 15 (continued) Disk test results Attribute Use Displays the severity of the error found by the test. The severity can be one of the following: no lost data lost data hardware problem
severity
testExecutionCount
(Sheet 2 of 2)
Displays the number of times the test ran.
Troubleshooting the data collection system

Problems with the data collection system are usually related to device capacity. The table Troubleshooting problems with the data collection system (page 201) details how to troubleshoot the data collection system.
Table 16 Troubleshooting problems with the data collection system Symptom A network management interface or the spooler is not receiving the data collection information (alarm, SCN, log, and debug data) it requested. Probable causes The control processors message block usage is close to capacity, probably due to routing table updates. Corrective measures At least one network management interface or the spooler will be receiving all of the data collection information. Check all of the network management interfaces in the network, or the spooling files on the disk, to locate the information.
2.0S1
241-5701-605 2.0S1
203
Chapter 5 Statistics
The data collection system collects Passport statistics. When enabled, the data collection collects the values of particular attributes and spools them to disk. Once on disk, you can remove statistics les using the Management Data Provider. See 241-6001-309 NMS Management Data Provider User Guide for details. For more information on the data collection system, see Working with the data collection system (page 130). For more information on Passport statistics, see 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals. For complete information on statistics attributes collected for each component, see 241-5701-060 Passport 7400, 8700, 15000 Components. See the following sections for more information on statistics: Enabling statistics collection (page 203) Displaying statistics collection information (page 205)
Enabling statistics collection

By default, the data collection system does not collect statistics data. The agent queue size for statistics data is set to 0 (zero), which causes the agent to discard all statistics data.
2.0S1
204 Chapter 5 Statistics
To turn on statistics collection for a logical processor, you can use the following typical settings: maximum agent queue size: 100 spooling option: on maximum les in closed directory: 200
For additional guidelines on setting these parameters, see the Passport Engineering Notes and Guidelines Use the following procedure to congure the data collection system to collect Passport statistics for a logical processor and spool them to disk. To perform this procedure, your userid must have a minimum scope of device and a minimum impact of service. Perform the following steps in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system (page 33).
1 If you want to reset the statistics agent queue size on an LP, add an Override component: add Lp/<n> Eng DataStream/stats Override where: <n> is the number of the logical processor. 2 Set the maximum agent queue size for the LP: set Lp/<n> Eng Ds/stats Ov agentQueueSize <size> where: <n> is the number of the logical processor. <size> is the maximum number of records in the queue. Use a value between 20 and 200, depending on the number of applications congured on that LP to generate records. 3 Turn the spooling option on: set Col/stats Sp spool on The value must be set to on to permit spooling of Passport statistics. If set to off, statistics do not spool to the disk.
241-5701-605 2.0S1
Chapter 5 Statistics 205 4 Set the maximum number of les that can exist in a closed directory: set Col/stats Sp maxFile <number> where: <number> species the number of les to be kept on disk (any integer between 1 and 200). If you do not want the spooler to limit the number of statistics les kept on disk, enter 0 (zero). If you set this attribute to 0 (zero), you can ll the disk with statistics data les. Carefully monitor disk usage.
Displaying statistics collection information

Use this procedure to display information about the number of statistics records processed by the data collection system since the last processor restart. The following information is available for statistics collectors, agents, and spoolers: records currently in the queue (currentQueueSize attribute) received records (recordsRx attribute) discarded records (recordsDiscarded attribute)
Statistics agents also provide information on the number of records that applications were unable to generate due to some limitation (recordsNotGenerated attribute). Perform the following commands in operational mode.
1 Display the queue information for the statistics collector: display Col/stats Statistics 2 Display the queue information for the statistics agents: display Col/stats Ag/* Statistics, AgentStatistics This command displays a table showing queue information for each logical processor. An agent discards records if its queue size is too small. If an agent is discarding records, you may want to increase the agent queue size of its LP. However, you must be careful not to overload system resources with high queue size settings. For guidelines on determining appropriate
2.0S1
206 Chapter 5 Statistics values for agent queues sizes, see the Passport Engineering Notes and Guidelines. When records are not generated, it usually indicates that some reengineering is necessary. 3 Display the queue information for the statistics spooler: display Col/stats Sp Statistics A spooler discards records if its spooling option is turned off while the spooler still contains records.
241-5701-605 2.0S1
207
Chapter 6 Accounting
The data collection system collects accounting records from the logical processors. It collects accounting records when a call clears and at a collection time in the time-of-day accounting (TODA) schedule. In most cases, you can use the data collection defaults for accounting information collection. See Working with the data collection system (page 130) for more information on data collection defaults. For more information on Passport accounting, see 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals. You can also nd detailed information about accounting in 241-5701-650 Passport 7400, 8700, 15000 Accounting Reference. See the following sections for more information on accounting: Conguring accounting (page 207) Viewing accounting data (page 208) Conguring a time-of-day accounting schedule (page 208)
Conguring accounting
Use the following procedure to congure the data collection system to collect Passport accounting information on the node. Perform the following steps in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system (page 33).
2.0S1
208 Chapter 6 Accounting 1 If you want to reset the accounting agent queue size on an LP, add an Override component: add Lp/<n> Eng DataStream/accounting Override where: <n> is the number of the logical processor.
Note: When you add a DataStream component, Passport automatically adds an Override (Ov) component.
2 Set the maximum queue size for the LP: set Lp/<n> Eng Ds/acc Ov agentQueueSize <size> where: <n> is the number of the logical processor. <size> is the maximum number of records. Using a value of 0 will turn accounting record collection off for the specied LP. 3 Turn the spooling option on: set Col/acc Sp spool on The value must be set to on to permit spooling of Passport accounting information. If set to off, accounting information does not spool to the disk. 4 Set the maximum number of les that can exist in a closed directory: set Col/acc Sp maxFile <number> where: <number> species the number of les to be kept on disk (any integer between 1 and 200). If you do not want the spooler to limit the number of accounting les kept on disk, enter 0 (zero).
Viewing accounting data

You can use Network Management System (NMS) to view accounting data. Refer to 241-6001-309 NMS Management Data Provider User Guide for more information.
Conguring a time-of-day accounting schedule

You can dene when Passport collects accounting records by setting up a time-of-day accounting (TODA) schedule. You use the collectionTimes attribute to specify the TODA schedule. These scheduled times apply to a
241-5701-605 2.0S1
Chapter 6 Accounting 209
24-hour period. The schedule repeats the following day unless you set up a new schedule. The procedure Conguring a time-of-day accounting schedule (page 208) describes how to set the collectionTimes attribute. Use the following guidelines to set up a TODA schedule: Limit the number of entries to 24. Enter collection times in any order. However, accounting data collection occurs chronologically. Only include entries that are at least one hour apart and at most 12 hours apart. If you request data collection before one hour has passed since the last collection, Passport waits for one hour to pass before collecting the data. This occurs even if you change the time-of-day accounting schedule or adjust network time.
If you do not provision TODA, the virtual circuit (VC), or ATM, the accounting system starts its own 12-hour accounting timer. If you provision any valid collection times, Passport uses the TODA schedule. The collectionTimes attribute exists for all Collector component instances. However, if you set this attribute for any Collector component other than the accounting instance, it has no effect. Perform the following steps in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system (page 33).
1 Display the current setting for time-of-day accounting: display Col/accounting collectionTimes 2 Add schedule times for accounting record collection: set Col/accounting collectionTimes <time> where: <time> is the time of a scheduled collection (conform to the rules and restrictions listed previously). Use a 24-hour time in the format HH:MM. You can enter more than one scheduled collection time by separating them with a space.
2.0S1
210 Chapter 6 Accounting 3 Remove a scheduled collection time, as required: set Col/accounting collectionTimes ~<time> where: <time> is the time of the scheduled collection you want to remove.
241-5701-605 2.0S1
211
Chapter 7 Security
You maintain Passport security by controlling user access and a list of IP addresses allowed to access your node. See the following sections for information on managing Passport security: User administration (page 211) Controlling user sessions (page 219) Conguring authorized IP access (page 223)
For more information on Passport security, see 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals.
User administration
The following procedures allow you to maintain Passport user information. Adding a new user (page 212) Copying an existing userID for a new user (page 214) Changing a password (page 215) Changing user attributes (page 218) Deleting a userID (page 218)
2.0S1
212 Chapter 7 Security
Adding a new user

When you rst set up a node, you must dene at least one userID with systemAdministration impact. Nortel Networks recommends that at least two userIDs exist with systemAdministration impact. Nortel Networks also recommends that you dene a userID that allows you to view Passport alarms on the Network Management System (NMS) workstation. This userID must have a scope of network, impact of service, and allowed access of FMIP. For more information, see 241-6001-303 NMS Administrator Guide. Unless this is a new node, you must have systemAdministration impact to add a new user. Perform the following steps in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system (page 33).
1 Add a Userid component: add accessControl Userid/<userID> where: <userID> is from one to eight characters in length. 2 Set the password: set Ac Userid/<userID> password <password> where: <userID> is from one to eight characters in length. <password> is from ve to eight characters in length.
Note 1: Passwords are case-sensitive. Note 2: Only users with an impact level of systemAdministration or higher can set a password. Note 3: When you set a password, it displays on the user interface. Once set, the password cannot be displayed.
3 Set the customer identier (CID): set Ac Userid/<userID> customerIdentifier <identifier> where: <userID> is from one to eight characters in length. 241-5701-605 2.0S1
Chapter 7 Security 213 <identier> is any number between 0 and 8191. The CID constrains the user to those components that belong to the same CID, except 0 which can access any component. 4 Set the command scope for the user: set Ac Userid/<userID> commandScope <scope> where: <userID> is from one to eight characters in length. <scope> is one of application (default), device, or network. The command scope is automatically set to the default of application if you do not enter this command.
Note: In the NMS for Architect for Passport tool, <scope> must be set to network.
5 Set the command impact for the user: set Ac Userid/<userID> commandImpact <impact> where: <userID> is from one to eight characters in length. <impact> is one of passive (default), service, conguration, or systemAdministration. The command impact is automatically set to the default of passive if you do not enter this command. 6 Set the allowed network management interfaces: set Ac Userid/<userID> allowedAccess <interface> where: <userID> is from one to eight characters in length. <interface> is one or more of local (default), FMIP, telnet, or FTP. This value constrains the user to the specied interface types. The allowed interface is automatically set to the default of local if you do not enter this command. The following indicates which interface to use for each tool: directly connected VT100 terminallocal NMS Integrated Command ConsoleFMIP NMS surveillanceFMIP Architect for PassportFMIP standard telnettelnet OMS network management systemtelnet standard FTPFTP 2.0S1
214 Chapter 7 Security If you want to disallow an interface, you can type the interface name preceded by a tilde (~) character. For example, to allow access from all interfaces except FTP, enter the following: set Ac Userid/<userID> allowedAccess local fmip telnet ~ftp 7 Set the allowed out access for the user: set Ac Userid/<userid> allowedOutAccess <interface> where: <userid> is from one to eight characters in length. <interface> is either telnet or ~telnet. If you want to allow the user to establish outgoing telnet connections, use telnet. If you dont want the user to establish outgoing telnet connections, use ~telnet. The default is ~telnet. 8 Optionally, you can set the user login directory for le system commands or FTP commands: set Ac Userid/<userID> loginDirectory <directory> where: <userID> is from one to eight characters in length. <directory> is the users login directory.
Note: The directory is automatically set to the default of / if you do not enter this command. / is the root directory.
9 Optionally, you can check your new userID: display Ac Userid/<userID> where: <userID> is from one to eight characters in length.
Copying an existing userID for a new user

You can copy a userID and all of its attributes, except password attributes, if you have a large number of users that will have the same attributes where the only difference is the userID and the password. This technique reduces the need to reset attributes every time you add a new user. Once you copy a Userid component, you only need to change the password. If you want to change other attributes, see Changing user attributes (page 218). You must have systemAdministration impact to copy an existing userID.
241-5701-605 2.0S1
Chapter 7 Security 215
Perform the following steps in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system on page 33.
1 Copy the Userid component: copy -s(Ac Userid/<olduserID>) -d(Ac Userid/ <newuserID>) Prov where: <olduserID> is the existing userID. <newuserID> is the userID of the new user. 2 Set the password for the new userID: set Ac Userid/<newuserID> password <password> where: <newuserID> is the userID of the new user. <password> is from ve to eight characters in length.
Note: When you set a password, it displays on the user interface. Once set, the password cannot be displayed.
3 If you want to change the attributes of the new Userid component, do so with the set command.
Changing a password
The following procedure explains how to change the password on an existing userID. Individual users cannot change their passwords. Only the system administrator (systemAdministration impact) can change a password. When you change a password, the actual characters of the password appear on the user interface. To keep passwords private, make sure your workstation is in a secure area before changing a password. For more information on password security, see Secure method for setting a password on page 216. Perform the following command in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system on page 33.
1 Set the password: set Ac Userid/<userID> password <password>
2.0S1
216 Chapter 7 Security where: <userID> is the name of the userID for which you are changing the password. <password> is the new password. The password must be from ve to eight characters long.
Secure method for setting a password

When setting an initial password for a user or changing an existing password, there are the following security risks: The actual characters of the password appear on the user interface. When you are not using a local session, the password travels over the network in easy-to-read ASCII format. Local and telnet sessions have a command recall queue, which stores the last 10 commands. The command in which you set the password can be recalled from the queue using the Up-Arrow and Down-Arrow keys.
The following procedure describes a method for minimizing the security risk when setting a password. It assumes that you have a physically secure Passport where you can make password changes and that you need to change a password on another, insecure Passport. It also assumes that the user ID that needs the changed password exists on both the secure and the insecure node. Only the system administrator (systemAdministration impact) can change a password.
1 Log into a secure Passport node. You should access this node from a workstation in a physically secure area using a local VT100 session. You can also use a telnet session as long as you use a secure connection. Do not establish a telnet session across a public network. Start provisioning mode. start Prov 3 Set the password. set Ac Userid/<userID> password <password> where: <userID> is name of the user ID for which you are setting the password <password> is the password. The password must be from ve to eight characters long.
241-5701-605 2.0S1
Chapter 7 Security 217 4 Save the Userid component with the changed password. save -component(Ac Userid/<userID>) -file(<name>) Prov where: <userID> is name of the user ID with the changed password <name> is a descriptive name for the partial saved view.
Note: When you save a partial saved view i to the le system, uses its complete name in the form <name>.part.<num>, where <num> is an automatically generated sequence number. The save Prov command responds with the complete name of the view, for example, UserRoot.part.001.
5 End provisioning mode. end Prov 6 Log out of the secure node to clear the command recall queue. logout 7 Transfer the partial saved view containing the Userid component from the secure node to an insecure node using FTP. You must use the complete name of the view, which is in the form <name>.part.<num>.
Note: Since FTP does not have a secure login mechanism, do not use the same user ID for FTP access as you have stored in the partial saved view.
a. Transfer the partial saved view from the secure node to a workstation using FTP. You can nd the partial saved view you created in the /provisioning directory of the Passport node. Transfer the partial saved view from the workstation to the insecure node using FTP. Put it in the /provisioning directory.
b. 8 9
Log into the insecure node. Start provisioning mode. start Prov
10 Load the partial saved view. load -file(<viewname>) Prov where: <viewname> is the complete name of the partial saved view, which is in the form <name>.part.<num>. 11 Verify that the provisioning changes you have made are acceptable.
2.0S1
218 Chapter 7 Security check Prov Correct any errors, and then verify the provisioning changes again. 12 If you want these changes as well as other changes made in the edit view to take effect immediately, activate and commit the provisioning changes. activate Prov confirm Prov commit Prov For more information on this step, see Activating and committing provisioning changes on page 35. 13 End provisioning mode. end Prov
Changing user attributes

This section explains how to change the user attributes of an existing Userid component. For a description of all user attributes, see Adding a new user (page 212). You can also nd descriptions of the attributes in 241-5701-600 Passport 7400, 8700, 15000 Operations and Maintenance Fundamentals. You must have systemAdministration impact to change user attributes. Perform the following command in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system on page 33.
1 Change the attributes of the Userid component: set Ac Userid/<userID> <attribute> <value> where: <attribute> is any attribute that corresponds to userid. <value> is any value that corresponds to the chosen attribute.
Deleting a userID
This section explains how to delete an existing userID. You must have systemAdministration impact to delete a user. Perform the following command in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system on page 33.
241-5701-605 2.0S1
Chapter 7 Security 219 1 Remove the Userid component: delete accessControl Userid/<userID> where: <userID> is from one to eight characters in length.
Controlling user sessions

The following procedures allow you to control the user connections (sessions) to your Passport node: Displaying the number of user sessions (page 219) Displaying users (page 220) Restricting access through a specic interface (page 220) Terminating a user session (page 220) Immediately terminating multiple user sessions (page 221) Releasing a locked interface (page 222) Enabling and disabling password encryption for telnet sessions (page 222)
Displaying the number of user sessions

The following procedure lets you determine how many users are logged into the node and which network management interfaces they are using. Perform the following steps in operational mode.
1 Display the number of current sessions of a particular network management interface: display Nmis <interface> activeSessions where: <interface> is one of telnet, local, fmip, or ftp. 2 Display the sessions logged on to a particular network management interface: list Nmis <interface> * where: <interface> is one of telnet, local, fmip, or ftp.
2.0S1
Displaying users
Use the following procedure to display the users logged into each network management interface. Perform the following command in operational mode.
1 Display all the users logged on to a network management interface: display Nmis <interface> Session/* userid where: <interface> is one of telnet, local, fmip, or ftp.
Restricting access through a specic interface

The following procedure explains how to terminate access through a specied interface by placing the interface out of service. To place an interface out of service, you lock the appropriate interface component. All current sessions continue until they are complete and no further sessions start until you issue the unlock command. You must have systemAdministration impact to perform this procedure. You cannot restrict access through the local interface. Perform the following command in operational mode.
1 Lock the interface component: lock Nmis <interface> where: <interface> is one of ftp, fmip, or telnet. You can lock any interface component except the interface you are currently using to access the node. The interface moves to a shutting-down state and does not allow set up of further sessions. All current sessions continue until they are complete. If you lock the telnet interface while you have a current telnet session, you can still set up outgoing telnet client connections (using the telnet Vr command), but you cannot set up new incoming telnet sessions.
Terminating a user session

You can terminate individual user sessions using the clear Nmis <interface> Session command against that session.
241-5701-605 2.0S1
Chapter 7 Security 221
You must have systemAdministration impact to terminate a user session. You cannot terminate a user session on the local interface. Perform the following steps in operational mode.
1 Display all current sessions: list Nmis <interface> * where: <interface> is one of telnet, fmip, or ftp. This command lists all sessions on the interface. Each session has a unique instance number. 2 Clear the Session component: clear Nmis <interface> Session/<n> where: <interface> is one of telnet, fmip, or ftp. <n> is the session number you want to terminate. The user session terminates. If a telnet session has a client connection (as represented by the Client subcomponent), the command also terminates the client connection.
Immediately terminating multiple user sessions

You can immediately terminate multiple user sessions by immediately shutting down an interface using the lock command with the force option. All sessions on the interface terminate and new sessions cannot be set up. You must have systemAdministration impact to terminate multiple user sessions. You cannot terminate user sessions on the local interface. To terminate an individual user session, see Terminating a user session (page 220). Perform the following command in operational mode.
1 Force the lock on the interface component: lock -force Nmis <interface>
2.0S1
222 Chapter 7 Security where: <interface> is one of telnet, fmip, or ftp. You cannot lock the interface you are currently using to access the node. The interface immediately terminates all its sessions, moves to a locked state, and does not set up further sessions.
Releasing a locked interface

The following procedure explains how to release or unlock a locked network management interface. Perform the following command in operational mode.
1 Unlock the interface component: unlock Nmis <interface> where: <interface> is one of telnet, fmip, or ftp. Once the interface is unlocked it can set up new sessions, enabling user access on the interface.
Enabling and disabling password encryption for telnet sessions

You can enable public key authentication of passwords on telnet sessions. When enabled, you can log into a Passport node from an OMS network management workstation and have your password encrypted using a public key encryption algorithm. This encryption ensures that your password travels across the network securely. The public authentication process used by Passport is only supported by the telnet client of the OMS network management system. If you enable public key authentication for the telnet session, you will not be able to use other telnet clients (for example, UNIX telnet and Passport telnet Vr command) to access the node. Perform the following command in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system on page 33.
1 Enable or disable password encryption for telnet sessions:
241-5701-605 2.0S1
Chapter 7 Security 223 set accessControl publicKeyAuth <setting> where: <setting> is telnet to enable or ~telnet to disable password encryption.
Conguring authorized IP access

The IpAccess component prevents users from logging into a Passport node from an unauthorized device. You create a list of devices that have permission to access the node. You specify a individual device using its IP address. You can specify an entire IP subnetwork using an IP address and a subnetwork mask. If you do not add an IpAccess component, all devices are permitted to access the node, regardless of their IP address. Perform the following steps in provisioning mode. For information on working in provisioning mode, see Changing the conguration using the provisioning system on page 33.
1 Add an IpAccess component: add accessControl IpAccess/<address> where: <address> is the IP address of the device to which you are giving permission to access the node. 2 To allow access to a subnetwork, set the subnetwork mask: set Ac IpAccess/<address> IpAddressMask <mask> where: <address> is the IP address of a device in the subnetwork to which you are giving permission to access the node. <mask> is a special IP address that indicates which byte of the IP address to ignore when evaluating an incoming IP address. For example, setting the mask to 255.255.255.0 tells the node to ignore the last byte in the address. This allows all devices with their rst three bytes identical to the IP address set in step 2 to access the node. The mask, combined with the IP address, denes a subnetwork.
2.0S1
241-5701-605 2.0S1
225
Appendix OSI states

The Passport node uses component state denitions according to the OSI standards. Components that are always up and never change state do not require any dened component state variables. A component has three high-level state variables: an operational state, a usage state, and an administrative state. These states are the primary factors affecting the management state of a component and are described in detail in 241-5701-500 Passport 6400, 7400, 8700, 15000 Alarms. See the following sections for information on the state variables of particular components: Data collection system component states (page 226) File system component states (page 226) Network management interface system component states (page 228) Port management system component states (page 229) Framer component states (page 232) Processor card component states (page 233) Fabric card component states for the Passport 15000 (page 235) Bus component states for the Passport 7400 or Passport 8700 series switch (page 237)
2.0S1
226 Appendix OSI states
Data collection system component states

The table Spooler component state combination (page 226) describes the component state combinations of the Spooler component.
Table 17 Spooler component state combination Combination (Administrative, Details Operational, Usage) Unlocked, Disabled, Idle This combination occurs when the spooler is unable to spool due to some file system error. This combination can also occur when spooling is turned off. This combination typically occurs when the spooling is turned off. It can also occur when all the conditions for spooling have been met (file system OK, administratively allowed to spool) but the spooler is not yet completely initialized (file not opened yet, not registered with the collector, and so on). For the most part, the state represented by this combination is transient. This combination occurs when the spooler has a spooling file open and is registered with the collector to receive records. The spooler may or may not be spooling a record, but it is ready to spool a record. This combination occurs when the spooler is administratively prohibited from spooling and has also detected an outstanding file system error. This combination can also occur when spooling is turned off. This combination occurs when the spooler is administratively prohibited from spooling but otherwise would be ready to try and open a file and register for the data.
Unlocked, Enabled, Idle
Unlocked, Enabled, Active
Locked, Disabled, Idle
Locked, Enabled, Idle
File system component states

The following tables describe the component state combinations for components of the le system. The table FileSystem component state combination (page 227) describes the component state combinations for the FileSystem component. The table Disk component state combination (page 227) describes the component state combinations for the Disk component. The table Disk Test component state combination (page 228) describes the component state combinations for the Disk Test component.
241-5701-605 2.0S1
Appendix OSI states 227 Table 18 FileSystem component state combination Combination (Administrative, Details Operational, Usage) Unlocked, Enabled, Active Unlocked, Disabled, Idle Locked, Disabled, Idle Locked, Enabled, Idle The file system is in normal operating state. The file system is not available due to internal problems. The file system is not available and is also locked. The file system is capable of providing service but is manually locked.
Shutting down, Enabled, Active The file system is performing some tasks. The file system will enter the locked state as soon as the task is complete.
Table 19 Disk component state combination Combination (Administrative, Details Operational, Usage) Unlocked, Enabled, Active Unlocked, Disabled, Idle Locked, Disabled, Idle Locked, Enabled, Idle The disk is in normal operating state. The disk is not available due to internal problems. The disk is not available and is also locked. The disk is capable of providing service but is manually locked.
Shutting down, Enabled, Active An operator has issued a lock command while the disk is performing a certain task. The disk will enter the locked state as soon as the task is complete.
2.0S1
228 Appendix OSI states Table 20 Disk Test component state combination Combination (Administrative, Details Operational, Usage) Unlocked, Enabled, Idle Unlocked, Enabled, Active Unlocked, Disabled, Idle The test can run, but is not currently running. The test is running. The test cannot run because the corresponding disk is not locked.
Network management interface system component states

All NMIS managers have the same OSI state combinations. In the table below, the term manager generically refers to any of FTP, local, FMIP, or telnet.
Table 21 FTP, local, FMIP, or telnet manager component state combination Combination (Administrative, Details Operational, Usage) Unlocked, Enabled, Idle The manager component is operable, but currently not in use. A manager component can be ready for service, but if there is no connection between the interface and an external device, then the manager component remains in the idle state. The manager component enters the active state when there is one or more connections to an external device but fewer than the maximum number of connections. The manager component enters this combination when the manager reaches it maximum number of sessions.
Unlocked, Enabled, Active
Unlocked, Enabled, Busy
Shutting down, Enabled, Active The manager cannot accept any new connection establishment requests. When all existing user sessions clear, the manager moves to the locked administrative state. Locked, Enabled, Idle. The manager cannot accept any new connection establishment requests. There are currently no connections between the interface and an external device.
241-5701-605 2.0S1
Appendix OSI states 229
Port management system component states

The following tables describe the component state combinations for components of the port management system. The table Port Channel component state combination (page 229) describes the component state combinations for the Channel component. The table Port Test component state combination (page 230) describes the component state combinations for the port Test component. The table Passport 7400 or Passport 8700 series Aps component state combination (page 231) describes the component state combinations for the AutomaticProtectionSwitching (Aps) component for Passport 7400 or Passport 8700 series switches. The table Passport 15000 Laps component state combination (page 231) describes the component state combinations for the LineAutomaticProtectionSwitching (Laps) component for Passport 15000 switches. The table OamEthernet port state combination (page 232) describes the component state combinations for the OamEthernet component.
See also 241-1501-610 Passport 15000 FP Conguration and Testing Guide for descriptions of the state combinations for ports of specic FPs.
Table 22 Port Channel component state combination Combination (Administrative, Details Operational, Usage) Unlocked, Disabled, Idle Unlocked, Enabled, Idle Unlocked, Enabled, Busy
(Sheet 1 of 2)
External factors render the Channel component inoperable (for example, total BPV error threshold reached). Not in use. The Channel component is being provisioned or waiting for binding. The Channel component is in use. The Channel component can only service one user at a time.
2.0S1
230 Appendix OSI states Table 22 (continued) Port Channel component state combination Combination (Administrative, Details Operational, Usage) Shutting Down, Enabled, Busy The operator issued a lock command while the Channel component was in use. The Channel component is in the process of terminating the user so that it can go into a locked administrative state. An unlock command brings the component into an unlocked administrative state. Locked, Enabled, Idle Locked, Disabled, Idle
(Sheet 2 of 2)
A lock command is in effect. The Channel component is otherwise ready to service a user. A hardware test failed and the Channel component is in the locked administrative state.
Table 23 Port Test component state combination Combination (Administrative, Details Operational, Usage) Locked, Disabled, Idle Locked, Enabled, Idle Unlocked, Enabled, Active Unlocked, Enabled, Busy Shutting Down, Enabled, Busy The hardware component is locked. No resource is available to the Test component. Start test requests will be rejected. The hardware component is locked. A port and line test can be performed. A start command has been issued, the Test process is being created. The Test component is in use. An operator issued a stop command while the Test component was in use. The Test component is in the process of terminating so that it can go into a locked administrative state.
241-5701-605 2.0S1
Appendix OSI states 231 Table 24 Passport 7400 or Passport 8700 series Aps component state combination Combination (Administrative, Details Operational, Usage) Unlocked, Disabled, Idle Unlocked, Enabled, Idle Unlocked, Enabled, Busy Shutting Down, Enabled, Busy Locked, Enabled, Idle Locked, Disabled, Idle The Aps component is inoperable due to both the working and protection lines being disabled. The Aps component is not in use. Waiting for binding to an application component. The Aps component is in use. The Aps component can service only one user at a time. A lock operator command is in effect. Waiting for a bound application to become suspended. The Aps component is running in test mode. A lock operator command is in effect and the component is in one of the following conditions: left ofine (availabilityStatus: ofine) if running in test mode (availabilityStatus: inTest), the Aps component is inoperable due to both the working and the protection lines being disabled.
Table 25 Passport 15000 Laps component state combination Combination (Administrative, Details Operational, Usage) Unlocked, Disabled, Idle Unlocked, Enabled, Idle Unlocked, Enabled, Busy Shutting Down, Enabled, Busy
(Sheet 1 of 2)
The Laps component is inoperable due to both the working and protection lines being disabled. The Laps component is not in use. Waiting for binding to an application component. The Laps component is in use. The Laps component can service only one user at a time. A lock operator command is in effect. Waiting for a bound application to become suspended.
2.0S1
232 Appendix OSI states Table 25 (continued) Passport 15000 Laps component state combination Combination (Administrative, Details Operational, Usage) Locked, Enabled, Idle Locked, Disabled, Idle The Laps component is running in test mode. A lock operator command is in effect and the component is in one of the following conditions: left ofine (availabilityStatus: ofine) if running in test mode (availabilityStatus: inTest), the Laps component is inoperable due to both the working and the protection lines being disabled.
(Sheet 2 of 2)
Table 26 OamEthernet port state combination Combination (Administrative, Details Operational, Usage) Unlocked, Disabled, Idle Unlocked, Enabled, Idle Unlocked, Enabled, Active The Lp/0 oamEthernet/0 component is disabled because of broken hardware or a faulty Ethernet connection to the port. The component is not in use. It is waiting for the LAN application component to bind to it. The component is in use.
Shutting Down, Enabled, Active The server component is going from the unlocked state to the locked state. Locked, Disabled, Idle Locked, Enabled, Idle A lock command is in effect. The component can be placed in the test mode. A lock command is in effect. A hardware test failed.
Framer component states

The table Control and function processor Framer component state combination (page 233) describes the component state combinations of the Framer component.
241-5701-605 2.0S1
Appendix OSI states 233 Table 27 Control and function processor Framer component state combination Combination (Administrative, Details Operational, Usage) Unlocked, Disabled, Idle A component that the Framer component depends on has failed. A likely cause is that the port component (for example, a V35 component) is locked for testing. External factors render the Framer component inoperable. Correct the line problem. Unlocked, Enabled, Idle Unlocked, Enabled, Busy The component is not in use. The Framer component is in use. The Framer component services only one user (an application component) at a time.
Processor card component states

The following tables describe the component state combinations for components related to processor cards. The table Card component state combination (page 233) describes the component state combinations for the Card component. The table LogicalProcessor component state combination (page 234) describes the component state combinations for the LogicalProcessor (Lp) component. The table Card test component state combination (page 234) describes the component state combinations for the Shelf Card Test component.
Table 28 Card component state combination Combination (Administrative, Details Operational, Usage) Unlocked, Disabled, Idle Unlocked, Enabled, Idle Unlocked, Enabled, Active The card is not ready for an LP assignment. The card is ready for an LP assignment, but has not received one. The card is running an LP.
Shutting down, Enabled, Active The card is running an LP, but the card will lock as soon as the LP stops running.
(Sheet 1 of 2)
2.0S1
234 Appendix OSI states Table 28 (continued) Card component state combination Combination (Administrative, Details Operational, Usage) Locked, Enabled, Idle Locked, Disabled, Idle
(Sheet 2 of 2)
The lock operator command is preventing an LP assignment for the card. The lock operator command is preventing an LP assignment for the card. However, the card is not ready for an LP assignment.
Table 29 LogicalProcessor component state combination Combination (Administrative, Details Operational, Usage) Unlocked, Disabled, Idle Unlocked, Enabled, Active The LP is not available for service. The active instance of the LP is running.
Shutting down, Enabled, Active The active instance of the LP is running, but will lock as soon as it stops running. Locked, Disabled, Idle The lock operator command prevents the assignment of the LP to a processor card.
Table 30 Card test component state combination Combination (Administrative, Details Operational, Usage) Unlocked, Disabled, Idle The operator cannot perform a card test because: The target card of the card test is non-operational. The target card of the card test is identical to the source card. Unlocked, Enabled, Idle Unlocked, Enabled, Busy A card test is not in progress but an operator request can start one. A card test is in progress.
241-5701-605 2.0S1
Appendix OSI states 235
Fabric card component states for the Passport 15000

The following tables describe the component state combinations for components related to the fabric card. The table Fabric card component state combination (page 235) describes the component state combinations for the FabricCard component. The table Fabric card test component state combination (page 236) describes the component state combinations for the Test subcomponent of the Fabric card component. The table Fabric port component state combination (page 237) describes the component state combinations for the FabricPort subcomponent of the Shelf Card component.
Table 31 Fabric card component state combination Combination (Administrative, Operational, Usage) Unlocked, Enabled, Active Unlocked, Disabled, Idle Availability Status (empty) InTest failed depend notInstalled Locked, Disabled, Idle InTest failed depend notInstalled
(Sheet 1 of 2)
Details
The component is in service. The component is not in service because the operator is testing it. The component is not in service because at least one failure condition was detected. The component is not in service because it is dependent on another component. The component is not in service because the hardware was removed. The component is not in service because the operator is testing it. The component was locked by the operator and at least one failure condition was detected. The component was locked by the operator and is dependent on another component. The component was locked by the operator and the hardware was removed.
2.0S1
236 Appendix OSI states Table 31 (continued) Fabric card component state combination Combination (Administrative, Operational, Usage) Locked, Enabled, Idle Availability Status (empty) InTest
(Sheet 2 of 2)
Details
The component was locked by the operator. Service is not provided. The component was locked by the operator, who is performing a test of the component.
Table 32 Fabric card test component state combination Combination (Administrative, Details Operational, Usage) Unlocked, Disabled, Idle Unlocked, Enabled, Idle Unlocked, Enabled, Busy A fabric card test cannot start because of an error. An operator request can start the fabric card test. A fabric card test is in progress.
241-5701-605 2.0S1
Appendix OSI states 237 Table 33 Fabric port component state combination Combination (Administrative, Details Operational, Usage) Unlocked, Disabled, Idle The fabric port is not operational for one of the following reasons: The fabric port failed its self-test. The fabric port is unable to receive clock signals from the fabric. The fabric port has detected too many parity errors on the fabric card. OR The fabric port is operational but is not communicating with other operational cards because the fabric is disabled or locked. The fabric ports availability status is dependency. Unlocked, Enabled, Active The fabric port is operational and is communicating with other operational cards.
Bus component states for the Passport 7400 or Passport 8700 series switch
The following tables describe the component state combinations for components related to the bus. The table Bus component state combination (page 238) describes the component state combinations for the Bus component. The table BusTest component state combination (page 238) describes the component state combinations for the Test subcomponent of the Bus component. The table BusTap component state combination (page 239) describes the component state combinations for the BusTap subcomponent of the Shelf Card component.
2.0S1
238 Appendix OSI states Table 34 Bus component state combination Combination (Administrative, Details Operational, Usage) Unlocked, Enabled, Active Unlocked, Disabled, Idle Locked, Enabled, Idle Locked, Disabled, Idle The bus is in service. The bus is not in service because at least one operational card is unable to access the bus. Its availability status is dependency. The bus is not in service because the network administration has locked it. The bus is not in service because the network administration has locked it and at least one operational card is unable to access the bus. Its availability status is In Test if a bus test is in progress. Otherwise, its availability status is Dependency.
Table 35 BusTest component state combination Combination (Administrative, Details Operational, Usage) Unlocked, Disabled, Idle Unlocked, Enabled, Idle Unlocked, Enabled, Busy A bus test cannot start because of an error. An operator request can start the bus test. A bus test is in progress.
241-5701-605 2.0S1
Appendix OSI states 239 Table 36 BusTap component state combination Combination (Administrative, Details Operational, Usage) Unlocked, Disabled, Idle The bus tap is non operational for one of the following reasons: The bus tap failed its self-test. The bus tap is unable to receive clock signals from the bus. The bus tap has detected too many parity errors on the bus. OR The bus tap is operational but is not communicating with other operational cards because the bus is disabled or locked. The bus taps availability status is dependency. Unlocked, Enabled, Active The bus tap is operational and is communicating with other operational cards.
2.0S1
240 Appendix OSI states
241-5701-605 2.0S1
Passport 7400, 8700, 15000

Release 2.0 Copyright 2000 Nortel Networks. All Rights Reserved. NORTEL, NORTEL NETWORKS, the globemark design, the NORTEL NETWORKS corporate logo, DPN, and PASSPORT are trademarks of Nortel Networks. VT100 is a trademark of Digital Equipment Corporation. UNIX is a trademark licensed exclusively through X/Open Company Ltd. Sun, SunOS, and Solaris are trademarks of Sun Microsystems, Inc. HP-UX is a trademark of Hewlett-Packard Company. Publication: 241-5701-605 Document status: Standard Document version: 2.0S1 Document date: July 2000 Printed in Canada

MK F5DWB

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MK F5DWB

Uploaded by

Copyright:

Available Formats

Passport 7400, 8700, 15000

Operations and Maintenance Guide

Passport 7400, 8700, 15000

Operations and Maintenance Guide

Passport 7400, 8700, 15000 Operations and Maintenance Guide

Chapter 1 General information

Passport 7400, 8700, 15000 Operations and Maintenance Guide

Chapter 2 Configuring and maintaining Passport

Passport 7400, 8700, 15000 Operations and Maintenance Guide

Chapter 3 Configuring network clock synchronization

Passport 7400, 8700, 15000 Operations and Maintenance Guide

Appendix OSI states

Passport 7400, 8700, 15000 Operations and Maintenance Guide

Passport 7400, 8700, 15000 Operations and Maintenance Guide

Table 34 Table 35 Table 36

About this document

Who should read this document and why

What you need to know

Passport 7400, 8700, 15000 Operations and Maintenance Guide

About this document

About this document 19

How this document is organized

Passport 7400, 8700, 15000 Operations and Maintenance Guide

About this document

Whats new in this document

About this document 21

About this document

How to get more help

Chapter 1 General information

Logging into a Passport node

Passport 7400, 8700, 15000 Operations and Maintenance Guide

24 Chapter 1 General information

Entering user information

Using telnet on a Passport node

Chapter 1 General information 25

Passport 2 (Passport 15000) telnet server telnet client

Passport 1 (Passport 7400 series)

telnet connection IP connection

Passport 7400, 8700, 15000 Operations and Maintenance Guide

26 Chapter 1 General information

Passports text interface

Chapter 1 General information 27

Operational mode and provisional mode

Passport 7400, 8700, 15000 Operations and Maintenance Guide

28 Chapter 1 General information

Chapter 1 General information 29

Passport 7400, 8700, 15000 Operations and Maintenance Guide

Chapter 1 General information 31

Passport 7400, 8700, 15000 Operations and Maintenance Guide

Passport provisioning views

Chapter 1 General information 33

Changing the conguration using the provisioning system

Entering provisioning changes

Passport 7400, 8700, 15000 Operations and Maintenance Guide

34 Chapter 1 General information Figure 5 Flowchart for entering provisioning changes

Start provisioning start Prov

Make changes add delete set

Verify the changes check Prov

Save the edit view save Prov

End provisioning end Prov

Activating and committing provisioning changes

Passport 7400, 8700, 15000 Operations and Maintenance Guide

36 Chapter 1 General information