Passport

Operations and Maintenance

Guide
241-7001-150
Passport
Operations and Maintenance
Guide
Publication: 241-7001-150
Document status: Standard
Document version: 4S3
Document date: May 1998
1998 Northern Telecom
Printed in Canada
Nortel, Magellan, DPN, and Passport are trademarks of Northern Telecom.
Sun is a trademark of Sun Microsystems Incorporated.
UNIX is a trademark of Novell Incorporated.
IBM is a trademark of International Business Machines Corporation.
5
Passport Operations and Maintenance Guide 4S3
Publication history
May 1998
4S3 Standard
Commercial availability. Contains information for release 4.2.
At time of publication, the V.54 loopback test on E1C is not generally
available. Subsequent 4.2 supplement reports will discuss its general
availability.
6 Publication history
241-7001-150 4S3
7
Passport Operations and Maintenance Guide 4S3
Contents
About this document 39
Who should read this guide 39
What you need to know 39
Related documents 40
About the procedures in this book 41
Nortel support services 41
Conventions 41
Chapter 1
Before you begin 43
Prerequisites 43
Definition of operations and maintenance 44
The process 44
Chapter 2
Passports text interface 47
Provisioning mode and operational mode 47
Interface prompt 48
Default information 48
The text interface screen 48
Alarm screens 55
Chapter 3
Operator commands 57
Related documents 57
NMS sessions and operational parameters 57
Component-specific commands 58
Operational fundamentals 58
Capability sets 58
8 Contents
241-7001-150 4S3
Common commands and operator modes 59
Operator commands 60
Command quick reference 60
Some hints for using commands 62
Detailed command descriptions 63
Command format 64
Error responses 65
Data types 65
help (h) 65
set (s) 68
add (a) 70
delete (del) 71
list (l) 72
display (d) 74
lock 82
unlock 83
Chapter 4
Provisioning system description 85
Related documents 85
Passport provisioning views 85
Current view 86
Edit view 87
Saved views 88
Committed view 92
Saved view development: example 93
Overview of provisioning system commands 98
Other commands used in provisioning mode 102
Provisioning commands and scope and impact 102
The reloadcp command 102
Detailed command descriptions 102
activate prov 103
apply prov 106
check prov 108
clear prov 113
commit prov 115
confirm prov 117
copy prov 119
end prov 122
load prov 122
save prov 124
Contents 9
Passport Operations and Maintenance Guide 4S3
start prov 127
stop prov 129
tidy prov 130
Chapter 5
Provisioning processes 137
Command format and conventions 138
Displaying provisioning status 139
Provisioning processes 141
Bulk provisioning 142
Regular order processing 146
Immediate or emergency provisioning 153
Using partial views 158
Global data changes 163
Scheduled network configuration changes 163
Chapter 6
Software installation 165
Related documents 166
Quick access to software installation procedures 166
Prerequisites 166
Installed Passport node 166
Installed UNIX workstation 167
Workstation hard disk capacity requirements 167
Summary of the software installation process 168
Step 1: Receive software from Nortel 168
Step 2: Set up the software distribution site 169
Step 3: Transfer software to the software distribution site 169
Step 4: Download and configure the software files 169
Step 5: Maintain directories at the software distribution site 169
Overview of Passport software 172
Backward compatibility 172
Software partitioning 172
Application versions and application version lists 173
Software hierarchy 175
Logical processors and logical processor types 179
Setting up the software distribution site 181
Defining software distribution site userids and default
directories 182
Setting up UNIX directories and files 182
10 Contents
241-7001-150 4S3
Transferring Passport software to the software distribution site 182
Installing software from the CD-ROM on a workstation 183
Installing and configuring software on Passport 184
Planning software installation 184
Configuring Passport software 185
Establishing the status of the software on the node 186
Ensuring free space on the file system 188
Downloading the files to disk 189
Updating the application version list 191
The next step 194
Configuring a new processor card 194
Downgrading to a previous software version 196
If things go wrong 197
Managing the software distribution site 197
Prerequisites 198
Adding new software 198
Removing unwanted software 198
Chapter 7
Initial node provisioning steps 201
Provisioning node security 201
Provisioning the node 202
Provisioning the data collection system 203
Installing and provisioning services 204
Chapter 8
Node security 205
Related documents 206
About the provisioning procedures in this chapter 206
Quick access to node security procedures 206
Prerequisites for configuring Passport security 206
Passport security features 207
Valid IP address list 207
Userid and its attributes 207
Login 210
Logging of operator commands 210
Local operator security 210
Adding a userid component 210
Adding a separate userid and password for alarm collection 213
Adding an IP access component 213
Contents 11
Passport Operations and Maintenance Guide 4S3
Copying an existing userid for a new user 214
Changing the password on an existing userid 215
Changing attributes on an existing userid 216
Deleting an existing userid component 216
Chapter 9
Node provisioning 217
Related documents 217
About the provisioning procedures in this chapter 217
Quick access to node provisioning procedures 217
Provisioning information in other locations 218
Provisioning new processor cards and ports 218
Provisioning a service 218
Provisioning the external address plan 218
Provisioning the DPN Gateway 219
Prerequisites for node provisioning 219
Provisioning access before using Magellan NMS 219
Provisioning the node name, identifier and region identifier 220
MAC addresses and logical processors 222
Provisioning the trunks 224
Provisioning dynamic trunk speed change 227
ISDN dial backup 227
Scheduled ISDN bandwidth on demand 229
Dynamic ISDN bandwidth on demand 230
ISDN dial backup with scheduled BWoD 231
ISDN dial backup with dynamic BWoD 232
Inverse multiplexing 233
Provisioning module-wide data 234
Chapter 10
Network management connectivity provisioning 237
Quick access to provisioning procedures 237
Passport NMS connectivity options 238
Conceptual view of NMS connectivity 239
Advantages of using VR IP on edge Passport nodes 241
Service and hardware requirements 241
IP interface over VC 244
IPIVC features 246
IPIVC components and attributes 246
Provisioning the IPIVC 247
12 Contents
241-7001-150 4S3
IP interface over Frame Relay 250
IPIFR features 251
IPIFR compliance to standards 252
IPIFR components and attributes 252
Connection options 253
IP routing and IPIFR 254
Provisioning the IPIFR 267
ILS network management via ethernet 282
Ethernet connectivity to an ILS-only network 284
ILS-only network to non-ILS network connectivity 285
Chapter 11
Processor card provisioning 293
Prerequisites 293
Provisioning a control processor 293
Adding a new standby control processor 294
Removing a standby control processor 295
Provisioning control and function processor 296
Provisioning DS1 and E1 function processors 297
Provisionable DS1 and E1 attributes 297
Provisioning a DS1 or E1 card and its logical processors and
ports 300
Provisioning V.11 and V.35 function processors 304
Provisionable V.11 and V.35 attributes 304
Provisioning a V.11 or V.35 card and its logical processors and
ports 306
Provisioning DS1C and E1C function processors 309
Provisionable DS1C and E1C attributes 309
Provisioning a DS1C or E1C card and its logical processors and
ports 312
Provisioning DS3 and E3 function processors 316
Provisionable DS3 and E3 attributes 316
Provisioning a DS3 or E3 card and its logical processors and
ports 318
Provisioning DS3c function processors 320
Provisionable DS3c attributes 320
Provisioning a DS3c card and its logical processors and ports 322
Provisioning HSSI function processors 326
Provisionable HSSI attributes 326
Provisioning the HSSI function processor and its port 327
Provisioning three-port DS1 and E1 ATM function processors 330
Contents 13
Passport Operations and Maintenance Guide 4S3
Provisionable three-port DS1 and E1 ATM attributes 330
Provisioning a three-port DS1 or E1 ATM card and its logical
processors and ports 332
Provisioning eight-port DS1 and E1 ATM function processors 337
Provisionable eight-port DS1 and E1 ATM attributes 337
Provisioning an eight-port DS1 or E1 ATM card and its logical
processors and ports 341
Provisioning JT2 ATM function processors 345
Provisionable JT2 ATM attributes 345
Provisioning a JT2 ATM card and its logical processors and
ports 346
Provisioning DS3 and E3 ATM function processors 350
Provisionable DS3 and E3 ATM attributes 350
Provisioning a DS3 or E3 ATM card and its logical processors and
ports 352
Provisioning OC3 function processors 356
Provisionable OC3 attributes 356
Provisioning an OC3 card and its logical processors and ports 358
Provisioning AAL1 function processors 362
Provisionable AAL1 attributes 362
Provisioning an AAL1 function processor and its logical processors
and ports 370
Provisioning DS1 and E1 Voice function processors 373
Provisionable DS1 and E1 Voice attributes 374
Provisioning a new DS1 or E1 Voice function processor and its
logical processors and ports 375
Provisioning J2MV function processors 379
Provisionable J2MV attributes 379
Provisioning new J2MV function processors and its logical
processors and ports 380
Provisioning the Ethernet function processor 383
Provisionable Ethernet attributes 383
Provisioning an Ethernet card and its logical processors and
ports 385
Provisioning the FDDI function processor 389
Provisionable FDDI attributes 389
Provisioning a FDDI card and its logical processors and ports 392
Provisioning the Token Ring function processor 396
Provisionable Token Ring attributes 396
Provisioning a Token Ring card and its logical processors and
ports 398
14 Contents
241-7001-150 4S3
Provisioning MVP function processors 402
Provisionable MVP attributes 402
Provisioning a MVP function processor and its logical processors
and ports 402
Chapter 12
Component control 407
Related documents 407
Commands 408
Quick access to component control procedures 408
Prerequisites for performing node control 409
Determining the state of a component 409
Controlling the network management interface system 409
Restricting access through a specified interface 410
Terminating a user session 411
Immediately terminating multiple user sessions 411
Releasing a locked interface 412
Controlling logical processors and processor cards 412
Temporarily disabling logical processors 413
Re-enabling logical processors 414
Temporarily disabling cards 414
Immediately disabling cards 415
Re-enabling cards 415
Controlling the buses 415
Preparing bus components for testing 416
Controlling the data collection system 417
Controlling the trunks 417
Disabling a trunk 418
Re-enabling a trunk 419
The trunk restaging mechanism 420
Controlling the disk 420
Preparing a disk for testing 421
Controlling the ports 421
Preparing port components for testing 423
Chapter 13
Node monitoring 425
Prerequisites 426
Related documents 426
Quick access to component control procedures 426
Contents 15
Passport Operations and Maintenance Guide 4S3
Monitoring commands 428
Command capability set 428
Hints for entering commands 428
Views 428
Operating modes 428
The list command 429
The display command 429
Command responses 430
OSI management states 430
Monitoring shelf management systems 431
Determining hardware failures 431
Determining which buses are in service 431
Determining the status of a bus 431
Displaying all currently provisioned logical processors 432
Determining the status of a logical processor 432
Determining the restart behavior of LPs 432
Determining the memory capacity of a processor card 433
Determining the card type 433
Displaying operational port components 434
Displaying provisionable attributes of port components 434
Displaying information about the file system 435
Displaying file system disk information 435
Monitoring the Passport network management systems 435
Determining the number of user sessions 436
Displaying user sessions 436
Querying userids 437
Monitoring the routing system 437
Displaying node name, node identifier, namsID or region
identifier 440
Displaying neighboring node link information 440
Displaying information about a specific link group 441
Listing all the nodes in the Passport network 442
Determining link groups 442
Displaying information about link groups in the network 443
Displaying information about PORS trunks in the link group 443
Displaying routing topology information 443
Listing the reachable DPN addresses in the network 444
Displaying routing control statistics 446
Determining network information using the rtg dpn ping
command 446
Determining Frame Relay Virtual Circuit (VC) information using the
16 Contents
241-7001-150 4S3
VC ping command 452
Displaying PORS connections on a Passport node 455
Displaying VNS connections on a Passport node 455
Virtual circuit recovery 456
Recovery initiation 457
The ifTable 458
Chapter 14
Data collection 459
Related documents 459
About the provisioning procedures in this chapter 460
Quick access to data collection procedures 460
Prerequisites for data collection 460
Data collection setup and operation guidelines 460
Accounting data 461
Statistics data 461
Alarm data 462
SCN data 462
Log data 462
Debug data 463
Trap data 463
File transfer 463
Creating a new spooling file 464
Displaying a filename 464
Displaying attributes 464
Directories 465
Filenames 465
Resetting the agent queue sizes 466
Resetting the maximum number of files to be kept on disk 467
Setting up the spooling option 468
Creating a new spooling file 470
Displaying the queue attributes of data collection components 471
Displaying the filename of the spooling file 473
Setting up a time-of-day accounting schedule 473
Chapter 15
Statistics 477
Related documents 477
About the provisioning procedures in this chapter 477
Quick access to statistics collection procedures 478
Contents 17
Passport Operations and Maintenance Guide 4S3
Passport statistics collection 478
Passport 478
Magellan Data Provider host 478
File Prober host 479
Network Engineering host 481
Benefits of Passport statistics collection 481
Description of on-switch statistics generation 481
Setting up statistics collection on Passport 489
Provisionable statistics attributes 489
Provisioning procedures for statistics 491
Chapter 16
Troubleshooting the Passport node 493
Quick access to troubleshooting procedures 494
Alarms 494
Alarm cutoff procedure 495
Service-specific problems 497
Passport Trace System 497
The troubleshooting process 497
Three steps of the troubleshooting process 497
Using the process to handle common problems 498
Node outage problems 498
Control processor problems 499
Function processor problems 503
Detecting problems with a specific card 507
File system problems 512
Trunk problems 514
DPN Gateway problems 517
Data collection system problems 521
Chapter 17
Diagnostic tests 523
Related documents 524
Prerequisites for diagnostic testing 524
Quick access to diagnostic test procedures 524
Serial port testing 525
Port tests and loopbacks 526
Generic test process 536
Testing a serial port on DS1, E1, DS1 MVP, E1 MVP, TTC2M MVP,
and J2MV FPs 536
18 Contents
241-7001-150 4S3
Testing a DS1 tributary on a DS3C function processor 543
Testing a serial port on DS3, E3, DS3C, JT2, and OC-3 FPs 545
Testing a serial port on V35 and V11 FPs 549
V54 remote loopback 553
Testing a serial port on a HSSI FP 566
Setting up a local external loopback for the far end 568
Setting up a local payload loopback for the far end 569
Displaying serial port test results 570
Interpreting serial port test results 572
Card testing 573
Changing the card test setup 574
Testing a card 577
Displaying card test results 579
Interpreting card test results 580
Terminator card testing 582
Bus testing 583
Automatic testing of the alternate bus clock source 584
Manually testing a bus 585
Setting automatic bus testing 586
Displaying bus test results 587
Interpreting bus test results 590
Disk testing 593
Disk test types 593
Testing a disk 595
Displaying disk test results 596
Chapter 18
Shelf management 599
Related documents 600
Provisioning procedures 600
Quick access to procedures 600
Software management 601
Removing unused software files 602
Resetting, reloading, and restarting a processor card 605
The reset command 605
The reloadcp command 606
The restart command 606
The switchover command 607
Locking and unlocking processor cards 607
Changing a processor cards software load 607
Creating, modifying, or deleting a logical processor 608
Contents 19
Passport Operations and Maintenance Guide 4S3
Changing a logical processors logical processor type 608
Adding more software features to an LPT 609
Removing a software feature from an LPT 610
CP redundancy 611
Warm standby 613
Hot standby 614
Hot standby behavior characteristics 615
Conditions and limitations 620
Services supporting hot standby CP redundancy 623
Deployment of hot standby CP redundancy 624
Disabling and enabling hot standby CP redundancy 625
File system 627
What is disk synchronization? 627
Disruptions in disk synchronization 627
Automatic synchronization 628
Manual synchronization 628
File system commands 628
Synchronizing disks 631
Changing the volume name of a disk 631
Formatting a disk 632
Replacing a control processor in a single-CP node 633
Replacing a control processor in a two-CP node 640
Adding a second control processor to a single-CP system 641
Maintaining a node that has different size disks 642
Setting the network time 643
Setting the network time offset 644
Resetting the network time after a power off 645
Chapter 19
Regularly scheduled activities 647
Appendix
OSI state combinations 649
OSI states 649
Data collection system component states 650
File system component states 650
Trunk component states 652
Routing 653
DPN Gateway over Frame Relay component states 653
Network management interface system component states 655
Control Processor port management system component states 656
20 Contents
241-7001-150 4S3
Framer component states 658
Shelf Management system component states 658
Function processor port management system component states 661
DS1, E1, and MVP 662
DS1 ATM and E1 ATM 664
HSSI 667
V.11 and V.35 669
DS1 Voice and E1 Voice 670
J2MV 673
DS3 and E3 675
DS3 ATM and E3 ATM 677
JT2 ATM 679
DS1C and E1C 681
OC3 683
FDDI 685
Ethernet 685
Token Ring 686
Index 687
Contents 21
Passport Operations and Maintenance Guide 4S3
List of figures
Figure 1 Format of screenprovisioning mode or operational
mode 49
Figure 2 Sample screen, valid command in provisioning
mode 51
Figure 3 Sample screen, valid command in operational mode 51
Figure 4 Sample screen, invalid command in provisioning
mode 52
Figure 5 Sample screen, command failed because of syntax
error 53
Figure 6 Alarm format 55
Figure 7 Passport views 87
Figure 8 Relationship between provisioning views and
commands 101
Figure 9 Procedure flowchart for bulk provisioning 143
Figure 10 Procedure flowchart for data entry in regular order
processing 147
Figure 11 Procedure flowchart for activating in regular order
processing 150
Figure 12 Procedure flowchart for immediate or emergency
provisioning 155
Figure 13 Using partial views 160
Figure 14 The software installation process 171
Figure 15 Passport software structure 173
Figure 16 Example versions of Passport applications 174
Figure 17 Application version list examples 175
Figure 18 Passport software directory structure at a software
distribution site 176
Figure 19 Passport SDS software directory structure: optional MIB
and online documentation 178
Figure 20 ExampleRelationship between LPs, LPTs, and
processor cards in a 16-slot Passport switch 180
Figure 21 View migration during a software upgrade 192
Figure 22 Conceptual view of Passport NMS connectivity 240
Figure 23 NMS workstation access to Passport network over X.25
SVCs 245
Figure 24 NMS workstation access to Passport network over
Frame Relay VC 250
Figure 25 IP network with only PVC point-to-point IP
connections 256
22 Contents
241-7001-150 4S3
Figure 26 Static IP routes network example 258
Figure 27 IP default route for gateway routing 260
Figure 28 IP default route for path redundancy 262
Figure 29 Example of an edge Passport node (1) and two internal
Passport nodes (2 and 3) provisioned for Frame Relay
access for NMS 270
Figure 30 Parameters for a static IP route for a non-directly
connected IP network 279
Figure 31 Parameters for a default route to provide path
redundancy 281
Figure 32 Ethernet connection to an ILS-only network for network
management 283
Figure 33 ILS-only network to non-ILS network connectivity 286
Figure 34 Connection between an ILS-only network NMS
workstation and a non-ILS network 290
Figure 35 Connection between an ILS-only network and a non-ILS
network NMS workstation 292
Figure 36 Provisionable DS1 components and attributes 298
Figure 37 Provisionable E1 components and attributes 299
Figure 38 Provisionable V.11 and V.35 components and
attributes 305
Figure 39 Provisionable DS1C components and attributes 310
Figure 40 Provisionable E1C components and attributes 311
Figure 41 Provisionable DS3 and E3 components and
attributes 317
Figure 42 Provisionable DS3c components and attributes 321
Figure 43 Provisionable HSSI components and attributes 326
Figure 44 Provisionable three-port DS1 ATM components and
attributes 331
Figure 45 Provisionable three-port E1 ATM components and
attributes 332
Figure 46 Provisionable eight-port DS1 ATM components and
attributes 338
Figure 47 Provisionable eight-port E1 ATM components and
attributes 339
Figure 48 Provisionable JT2 ATM components and attributes 346
Figure 49 Provisionable DS3 and E3 ATM components and
attributes 351
Figure 50 Components and attributes to be provisioned on an
OC-3 ATM card 357
Contents 23
Passport Operations and Maintenance Guide 4S3
Figure 51 Provisionable DS1 AAL1 components and
attributes 363
Figure 52 Provisionable E1 AAL1 components and attributes 364
Figure 53 Provisionable DS1 voice components and
attributes 374
Figure 54 Provisionable E1 voice components and attributes 375
Figure 55 Provisionable J2MV components and attributes 379
Figure 56 Provisionable attributes for the Ethernet function
processor 384
Figure 57 Provisionable FDDI components and attributes
(Part 1) 390
Figure 58 Provisionable FDDI components and attributes
(Part 2) 391
Figure 59 Provisionable attributes for the Token Ring function
processor 397
Figure 60 Sample networkDPN-100 and Passport 439
Figure 61 rtg dpn ping query packet 449
Figure 62 Sample networkPassport nodes in a mixed
network 457
Figure 63 Magellan network planning and engineering statistics
flow 480
Figure 64 Collection times of Passport statistics 482
Figure 65 Provisionable components and attributes for statistics
collection 490
Figure 66 Alarm cutoff switch 496
Figure 67 LED status displays 511
Figure 68 Test loopback configurations on a DS1 or E1 ATM
components 537
Figure 69 Test configurations for DS1, E1, DS1 MVP, E1 MVP,
TTC2M MVP, and J2MV components 538
Figure 70 Test loopback configurations on DS1 and E1 AAL1
components 538
Figure 71 Test configurations on DS1 and E1 AAL1 Channel
components 539
Figure 72 Test configurations for DS1 tributary on DS3C FPs 544
Figure 73 Test configurations for DS3 and E3 non-ATM FPs 546
Figure 74 Test loopback configurations on a DS3 and E3 ATM
FPs 546
Figure 75 Test loopback configurations on a JT2 ATM FP 547
Figure 76 Test loopback configurations on an OC-3 ATM FP 547
Figure 77 Test configurations for V35, V11, and HSSI FPs 550
24 Contents
241-7001-150 4S3
Figure 78 DS1C to a fractional T1 network configuration 556
Figure 79 DS1C to a DDS network configuration 556
Figure 80 V.54 and PN127 E1C test configuration 557
Figure 81 V54 remote loopback test configuration 558
Figure 82 V.54 and PN127 remote loopback test
configuration 561
Contents 25
Passport Operations and Maintenance Guide 4S3
List of tables
Table 1 Fields of the text interface 50
Table 2 Keyboard shortcuts 54
Table 3 Quick reference to operator commands 61
Table 4 Options for the help command 67
Table 5 Options for the add command 71
Table 6 Options for the list command 73
Table 7 Options for the display command 76
Table 8 Options for the lock command 83
Table 9 Format of saved views 89
Table 10 Example of saved view development 93
Table 11 Quick reference to Provisioning system commands 99
Table 12 Options for the activate prov command 104
Table 13 Options for the apply prov command 107
Table 14 Options for the check prov command 109
Table 15 Options for the clear prov command 114
Table 16 Options for the commit prov command 117
Table 17 Options for the copy prov command 120
Table 18 Options for the load prov command 123
Table 19 Options for the save prov command 125
Table 20 Options for the start prov command 128
Table 21 Options for the tidy prov command 132
Table 22 Summary of characteristics of provisioning
operations 141
Table 23 Provisioning node security 202
Table 24 Provisioning a node 203
Table 25 Service and hardware requirements 241
Table 26 IP routing table for Passport node 1 of Figure 25 255
Table 27 Static IP route table for Passport node 1 of
Figure 26 259
Table 28 IP default route for gateway routing for Passport node 1
of Figure 27 261
Table 29 IP default route for path redundancy for Passport node 1
of Figure 28 263
Table 30 Routing table after vc19 comes up 264
Table 31 Routing table after vc16, vc17, and vc18 come up 265
Table 32 IRouting table after vc16 fails 265
Table 33 IRouting table after vc16 and vc19 fail 266
Table 34 Provisionable attributes for a port on an eight-port DS1
ATM FP 340
26 Contents
241-7001-150 4S3
Table 35 Provisionable attributes for a port on an eight-port E1
ATM FP 341
Table 36 Provisionable attributes for a port on a DS1 AAL1
FP 365
Table 37 Provisionable attributes for a port on an E1 AAL1
FP 368
Table 38 Commands 408
Table 39 Trunk statistics record 483
Table 40 DpnGateway statistics record 484
Table 41 LP statistics record 485
Table 42 Framer (Port) statistics record 485
Table 43 Timechange statistics record 486
Table 44 Voice Route statistics record 486
Table 45 Voice Subroute statistics record 487
Table 46 Signaling channel statistics record 487
Table 47 CAS signaling statistics record 488
Table 48 Voice networking call server statistics record 489
Table 49 Provisionable statistics attribute in the Collector
component 490
Table 50 Provisionable statistics attributes in the Spooler
component 491
Table 51 Troubleshooting node outage problems 499
Table 52 Troubleshooting control processor problems 500
Table 53 Troubleshooting function processor problems 504
Table 54 Detecting problems with a specific card 508
Table 55 Troubleshooting file system problems 512
Table 56 Troubleshooting problems with trunks 514
Table 57 Troubleshooting DPN gateway problems 518
Table 58 Troubleshooting problems with the data collection
system 521
Table 59 Component tests on function processors 527
Table 60 Pin connections for DS1, E1, DS1 MVP, E1 MVP,
TTC2M MVP, and J2MV FP electrical loopback 539
Table 61 Pin connections for V11 and V35 electrical
loopback 551
Table 62 Summary of V54 supported and unsupported
items 554
Table 63 Loopback troubleshooting 566
Table 64 Serial port test result attributes and uses 571
Table 65 Interpreting port test results 572
Table 66 Card test result attributes and uses 579
Contents 27
Passport Operations and Maintenance Guide 4S3
Table 67 Interpreting card test results 581
Table 68 Bus test result attributes and uses 588
Table 69 Interpreting bus test results 590
Table 70 Disk test result attributes and uses 597
Table 71 Command impacts in different standby modes 613
Table 72 Service support for hot standby CP redundancy 623
Table 73 Hot standby CP redundancy behaviors by network
deployment 625
Table 74 File system commands 628
Table 75 Regularly scheduled software activities 647
Table 76 Regularly scheduled hardware activities 648
Table 77 Spooler component state combination 650
Table 78 FileSystem component state combination 650
Table 79 Disk component state combination 651
Table 80 Test component state combination 651
Table 81 Trunk component state combination 652
Table 82 Unacknowledged component state combination 652
Table 83 Topology component state combination 653
Table 84 Transport Resource Manager component state
combination 653
Table 85 FrMux component state combination 653
Table 86 FrMuxLmi component state combination 654
Table 87 DataLinkConnectionIdentifier component state
combination 654
Table 88 FrAccess component state combination 655
Table 89 FTP, local, FMIP, or Telnet manager component state
combination 655
Table 90 Control Processor Channel (Chan) component state
combination 656
Table 91 Control Processor Test component state
combination 657
Table 92 Control and function processor Framer component state
combination 658
Table 93 Control and function processor Card component state
combination 658
Table 94 Control and function processor LogicalProcessor (LP)
component state combination 659
Table 95 Bus component state combination 659
Table 96 BusTest component state combination 659
Table 97 CardBusTap component state combination 660
Table 98 CardTest component state combination 661
28 Contents
241-7001-150 4S3
Table 99 DS1 component state combination 662
Table 100 E1 component state combination 662
Table 101 DS1 and E1 Channel (Chan) component state
combination 663
Table 102 DS1 and E1 Test component state combination 664
Table 103 DS1 component state combination 664
Table 104 E1 component state combination 665
Table 105 DS1 ATM and E1 ATM Channel (Chan) component
state combination 666
Table 106 DS1 ATM and E1 ATM Test component state
combination 667
Table 107 HSSI component state combination 667
Table 108 HSSI Test component state combination 668
Table 109 V35 component state combination 669
Table 110 X21 component state combination 669
Table 111 V.11 and V.35 Test component state combination 670
Table 112 E1 component state combination 670
Table 113 DS1 component state combination 671
Table 114 DS1 Voice and E1 Voice Channel (Chan) component
state combination 672
Table 115 DS1 Voice and E1 Voice Test component state
combination 672
Table 116 DS1 Voice and E1 Voice Framer component state
combination 673
Table 117 J2MV E1 component state combination 673
Table 118 J2MV Channel (Chan) component state
combination 674
Table 119 J2MV Test component state combination 674
Table 120 DS3 component state combination 675
Table 121 E3 component state combination 675
Table 122 DS3 and E3 Test component state combination 676
Table 123 DS3 component state combination 677
Table 124 E3 component state combination 678
Table 125 DS3 ATM and E3 ATM Test component state
combination 679
Table 126 JT2 component state combination 679
Table 127 JT2 ATM Test component state combination 680
Table 128 E1 component state combination 681
Table 129 DS1 component state combination 681
Table 130 DS1C and E1C Channel (Chan) component state
combination 682
Contents 29
Passport Operations and Maintenance Guide 4S3
Table 131 DS1C and E1C Test component state combination 682
Table 132 OC3 Sonet/Sdh component state combination 683
Table 133 OC3 Test component state combination 684
Table 134 OC3 Path component state combination 684
Table 135 FDDI (FI) component state combination 685
Table 136 Ethernet (en) component state combination 685
Table 137 Token Ring component state combination 686
30 Contents
241-7001-150 4S3
List of procedures
Procedure 1 Activating the edit view 105
Procedure 2 Activating a saved view 105
Procedure 3 Applying a saved view (delta format) 107
Procedure 4 Successful check prov command with no
options 110
Procedure 5 Example of successful and unsuccessful check prov
commands 111
Procedure 6 Clearing all non-permanent components from the edit
view 114
Procedure 7 Clearing all components associated with a removed
feature 115
Procedure 8 Committing the current view and storing in a saved
view 117
Procedure 9 Successfully confirming the activation 118
Procedure 10 Attempting to confirm before successful view
activation 119
Procedure 11 Copying components within the edit view 121
Procedure 12 Ending provisioning mode 122
Procedure 13 Loading a saved view into the edit view 124
Procedure 14 Loading a non-existent saved view 124
Procedure 15 Storing a component in a partial saved view 126
Procedure 16 Storing the current view in ASCII format 126
Procedure 17 Successfully entering provisioning mode 128
Procedure 18 Successfully entering provisioning mode 129
Procedure 19 Stopping a long-running provisioning system
command 130
Procedure 20 Examples of tidy prov command options 134
Procedure 21 Displaying provisioning and saved view status and
attributes 139
Procedure 22 Bulk provisioning process 144
Procedure 23 Performing data entry for regular order
processing 151
Procedure 24 Performing view activation for regular order
processing 151
Procedure 25 Performing immediate or emergency
provisioning 156
Procedure 26 Moving provisioning data to another node using a
partial view 161
Contents 31
Passport Operations and Maintenance Guide 4S3
Procedure 27 Installing the software from the CD-ROM on a
workstation 183
Procedure 28 Determining what software is already on the
node 186
Procedure 29 Ensuring free space on the file system 188
Procedure 30 Downloading the files to disk 189
Procedure 31 Updating the nodes AVL with a new version of
software 192
Procedure 32 Configuring a DS1 card 194
Procedure 33 Downgrading using a view from the previous
version 197
Procedure 34 Removing an application version 198
Procedure 35 Removing an application version directory 199
Procedure 36 Removing other SDS files and directories 199
Procedure 37 Adding a userid component 211
Procedure 38 Adding an IpAccess component 213
Procedure 39 Copying an existing userid for a new user 214
Procedure 40 Changing the password of a userid 215
Procedure 41 Changing attributes on an existing Userid
component 216
Procedure 42 Deleting a userid component 216
Procedure 43 Provisioning the node name and identifier 221
Procedure 44 Determining the MAC address of a port 223
Procedure 45 Assigning a local MAC address for a token ring
port 223
Procedure 46 Provisioning a trunk 224
Procedure 47 Provisioning ISDN dial backup 228
Procedure 48 Provisioning scheduled ISDN BWoD 229
Procedure 49 Provisioning alarms for dynamic ISDN BWoD 230
Procedure 50 Provisioning ISDN dial backup with scheduled
BWoD 231
Procedure 51 Provisioning ISDN dial backup with dynamic
BWoD 232
Procedure 52 Provisioning inverse multiplexing 233
Procedure 53 Provisioning the IPIVC using a text interface
device 247
Procedure 54 Deleting the IPIVC feature and component 268
Procedure 55 Provisioning the IPIFR on either an edge- or internal-
Passport node using a text interface device 271
Procedure 56 Provisioning subsequent LCNs, for connectivity to
additional management stations 273
32 Contents
241-7001-150 4S3
Procedure 57 Provisioning Frame Relay user-to-network access for
NMS on the edge Passport node 274
Procedure 58 Provisioning a static IP route for a non-directly
connected IP network 279
Procedure 59 Provisioning a default route for path redundancy 282
Procedure 60 Provisioning an ethernet connection to an ILS-only
network for network management 284
Procedure 61 Provisioning NMS workstation 1 to manage the ILS
network 288
Procedure 62 Provisioning NMS workstation 1 to additionally
manage the non-ILS network 288
Procedure 63 Provisioning an IPIFR static route (for Passport
3) 289
Procedure 64 Provisioning an IPIFR default route (for Passport
4) 289
Procedure 65 Provisioning NMS workstation 2 to additionally
manage the ILS-only network 291
Procedure 66 Provisioning a new standby control processor 294
Procedure 67 Removing a standby control processor 295
Procedure 68 Provisioning a DS1 or E1 function processor and its
LPs and ports 300
Procedure 69 Provisioning a V.11 or V.35 function processor and its
LPs and ports 306
Procedure 70 Provisioning a DS1C or E1C function processor and
its LPs and ports 312
Procedure 71 Provisioning a DS3 or E3 function processor and its
LP and port 318
Procedure 72 Provisioning a DS3c function processor and its LPs
and ports 322
Procedure 73 Provisioning a HSSI function processor and its LPs
and ports 327
Procedure 74 Provisioning a three-port DS1 or E1 ATM function
processor and its LPs and ports 333
Procedure 75 Provisioning an eight-port DS1 or E1 ATM function
processor 341
Procedure 76 Provisioning a JT2 ATM function processor and its LP
and port 346
Procedure 77 Provisioning a DS3 or E3 ATM function processor and
its LP and port 352
Procedure 78 Provisioning a new OC-3 ATM function processor and
its LP and port 358
Contents 33
Passport Operations and Maintenance Guide 4S3
Procedure 79 Provisioning a 4-port DS1 AAL1 or 4-port E1 AAL1
function processor and its LPs and ports 370
Procedure 80 Provisioning a DS1 or E1 voice function processor
and its ports 375
Procedure 81 Provisioning a new J2MV function processor and its
port 380
Procedure 82 Provisioning an Ethernet function processor and its
LPs and ports 385
Procedure 83 Provisioning a FDDI function processor and its LP
and port 392
Procedure 84 Provisioning a Token Ring function processor and its
LP and ports 398
Procedure 85 Provisioning an MVP function processor and its
ports 402
Procedure 86 Determining the state of a component using a text
interface device 409
Procedure 87 Terminating access through a specified interface
using a text interface device 410
Procedure 88 Terminating a user session 411
Procedure 89 Immediately terminating multiple user sessions 411
Procedure 90 Releasing a locked interface 412
Procedure 91 Temporarily disabling a logical processor 413
Procedure 92 Re-enabling a logical processor 414
Procedure 93 Temporarily disabling a card 414
Procedure 94 Immediately disabling a card 415
Procedure 95 Re-enabling a card 415
Procedure 96 Preparing a bus for testing 416
Procedure 97 Four methods of disabling a trunk 418
Procedure 98 Re-enabling a trunk 419
Procedure 99 Preparing a disk for testing 421
Procedure 100 Preparing a port for testing 423
Procedure 101 Determining a hardware failure 431
Procedure 102 Determining which buses are in service 431
Procedure 103 Determining the status of a bus 431
Procedure 104 Displaying a list of all existing logical processors 432
Procedure 105 Determining the status of a logical processor 432
Procedure 106 Determining the restart capability of LPs 432
Procedure 107 Determining the memory capacity of a processor
card 433
Procedure 108 Determining the card type in a given slot 433
34 Contents
241-7001-150 4S3
Procedure 109 Displaying the attributes of an operational port
component 434
Procedure 110 Displaying the provisionable attributes of a port
components 434
Procedure 111 Displaying information about the file system 435
Procedure 112 Displaying all the operational attributes of the file
system 435
Procedure 113 Displaying the number of user sessions 436
Procedure 114 Displaying the sessions logged on a network
management interface 436
Procedure 115 Displaying all the userids logged on to a network
management interface 437
Procedure 116 Displaying node identifier 440
Procedure 117 Listing neighboring node information 440
Procedure 118 Finding out about a specific link group 441
Procedure 119 Displaying information about logical network
numbers 441
Procedure 120 Finding out about a specific link 441
Procedure 121 Determining level of access to other nodes 442
Procedure 122 Determining link groups 442
Procedure 123 Displaying operational data about a trunk group 443
Procedure 124 Displaying PORS trunk information 443
Procedure 125 Displaying routing topology information 443
Procedure 126 Determining reachable DPN addresses 444
Procedure 127 Determining the delay and throughput metrics and
next hop link groups 445
Procedure 128 Displaying routing control statistics 446
Procedure 129 Displaying information on one path using the rtg dpn
ping command 449
Procedure 130 Displaying information on all paths using the rtg dpn
ping command 450
Procedure 131 Displaying round trip delay information using the rtg
dpn ping command 451
Procedure 132 Displaying Frame Relay VC path information using
the VC ping command 453
Procedure 133 Displaying round trip delay information for a Frame
Relay VC using the VC ping command 454
Procedure 134 Displaying PORS connections on a Passport
node 455
Procedure 135 Display VNS connections on a Passport node 455
Procedure 136 Resetting the agent queue sizes 466
Contents 35
Passport Operations and Maintenance Guide 4S3
Procedure 137 Specifying the maximum number of files to be kept on
disk 467
Procedure 138 Setting up the spooling option 469
Procedure 139 Creating a new spooling file 471
Procedure 140 Displaying queue attributes 471
Procedure 141 Displaying the filename of a spooling file 473
Procedure 142 Setting up a time-of-day accounting schedule 474
Procedure 143 Provisioning Passport statistics 491
Procedure 144 Cutting off alarms 495
Procedure 145 Determining why the node is out of service 499
Procedure 146 Determining why the control processors do not
load 501
Procedure 147 Determining the cause of a control processor
crash 502
Procedure 148 Determining why the standby control processor does
not load 503
Procedure 149 Determining why a function processor does not
load 505
Procedure 150 Determining the cause of a function processor
crash 506
Procedure 151 Determining why the file system is not
operational 512
Procedure 152 Determining why a file can not be saved to disk 513
Procedure 153 Determining the cause of a trunk failure 515
Procedure 154 Determining why a trunk does not remain
connected 516
Procedure 155 Determining the cause of a DpnGateway failure 519
Procedure 156 Determining why a dpngateway does not remain
connected 520
Procedure 157 Testing a serial port on DS1, E1, DS1 MVP, E1 MVP,
TTC2M MVP, and J2MV FPs 540
Procedure 158 Testing a Channel on DS1 and E1 AAL1 FPs 542
Procedure 159 Testing a DS1 tributary on a DS3C FP 544
Procedure 160 Testing a serial port on DS3, E3, DS3C, JT2, and OC-
3 FPs 548
Procedure 161 Testing a V35 or V11 serial port 552
Procedure 162 V54 remote loopback test for DS1C 558
Procedure 163 V54 remote loopback test for E1C 561
Procedure 164 PN127 remote loopback test for E1C 563
Procedure 165 Testing a serial port on a HSSI FP 566
36 Contents
241-7001-150 4S3
Procedure 166 Setting up a local external loopback for the far-
end 568
Procedure 167 Setting up a local payload loopback for the far-
end 569
Procedure 168 Displaying serial port test results 570
Procedure 169 Changing the card test setup 575
Procedure 170 Testing a card 577
Procedure 171 Displaying card test results 579
Procedure 172 Terminator card testing 582
Procedure 173 Testing a bus 585
Procedure 174 Setting automatic testing of the alternate clock
source 586
Procedure 175 Displaying bus test results 587
Procedure 176 Testing a disk 595
Procedure 177 Displaying disk test results 596
Procedure 178 Cleaning up unused files associated with any
application version 603
Procedure 179 Cleaning up unused files associated with a specific
application version 604
Procedure 180 Resetting a logical processor 605
Procedure 181 Resetting a shelf 605
Procedure 182 Resetting a card 605
Procedure 183 Reloading a control processor 606
Procedure 184 Restarting a logical processor 606
Procedure 185 Restarting a card 606
Procedure 186 Switching from the active LP to the standby 607
Procedure 187 Changing the logical processors logical processor
type 608
Procedure 188 Adding more software features to a logical processor
type 609
Procedure 189 Removing a software feature from a logical processor
type 610
Procedure 190 Disabling hot standby CP redundancy 626
Procedure 191 Enabling hot standby CP redundancy 626
Procedure 192 Synchronizing the active and standby disks 631
Procedure 193 Changing a disks volume name 631
Procedure 194 Formatting a disk 632
Procedure 195 Replacing a control processor in a single-CP system
(donor node is available and NMS backup is
available) 636
Contents 37
Passport Operations and Maintenance Guide 4S3
Procedure 196 Replacing a control processor in a single-CP system
(donor node is available and NMS backup is not
available) 637
Procedure 197 Replacing a control processor in a single-CP system
(donor node is not available and NMS backup is
available) 638
Procedure 198 Replacing a control processor in a single-CP system
(donor node is not available and NMS backup is not
available) 639
Procedure 199 Replacing a control processor in a two-CP
system 640
Procedure 200 Adding a second control processor 641
Procedure 201 Setting network time 643
Procedure 202 Setting the time offset 645
Procedure 203 Resetting the network time and the time offset after a
power off 645
38 Contents
241-7001-150 4S3
39
Passport Operations and Maintenance Guide 4S3
About this document
This document explains how to operate and maintain a Passport node or
network through a text interface device such as a VT-100 terminal.
Descriptions and procedures are provided for the following OA&M areas:
regularly scheduled activities
installing Passport software
provisioning your Passport node
diagnostic testing
shelf management
monitoring the Passport node
gathering statistics and performance data
troubleshooting
Who should read this guide
This guide is for persons who perform operational, administration, and
maintenance tasks.
What you need to know
This guide assumes that you understand the architecture and operation of
Passport and DPN-100 products. Knowledge of DPN-100 is required if your
network incorporates a call server resource module (CSRM). You also require
a basic-level knowledge of UNIX.
40 About this document
241-7001-150 4S3
You can acquire product knowledge by reading 241-7001-110, Passport
General Description. Specically, before undertaking operations and
maintenance activities, you should have an understanding of the following
product areas:
Passport concepts:
Passport hardware and software
Passport installation, commissioning, and provisioning
Passport-to-Passport interworking
Passport-to-DPN-100 interworking
DPN-100 concepts:
routing, trunking, and addressing
network installation, provisioning, operation, and maintenance
service protocols
UNIX:
a working knowledge of UNIX workstations
a working knowledge of the UNIX operating system, its facilities
and commands (such skills are those typically acquired through an
introductory UNIX course, and through experience performing
tasks such as file creation, maintenance, and manipulation)
standard network operations and maintenance activities
Magellan Network Management System (NMS) workstation concepts
Related documents
If you are using paper-based version of the Passport documentation library,
see the 241-7001-000, Passport Documentation Guide for a complete list of
Passport documents. If you are using an on-line version of the library, see the
Passport InfoMap, which will provide you with links to other documents.
Also, included with the software release is the Passport Supplement, which
provides information on last minute updates.
About this document 41
Passport Operations and Maintenance Guide 4S3
For information on the UNIX operating system, a recommended UNIX guide
is: Sobell, Mark G. A Practical Guide to the UNIX System, 2nd ed. California:
The Benjamin/Cummings Publishing Co., 1989.
About the procedures in this book
This document contains the procedures necessary to download Passport
software from the software distribution site, and to provision, monitor, and
maintain a Passport node. Detailed information on components and attributes
is provided in 241-7501-210, Passport Components.
Nortel support services
To contact Nortel (Northern Telecom) for information on customer service
and training, see 241-7001-110, Passport General Description, appendix
Nortel support services.
Conventions
Typographic conventions used throughout this document are explained in the
following points.
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.
42 About this document
241-7001-150 4S3
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 option 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 specification 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 /).
43
Passport Operations and Maintenance Guide 4S3
Chapter 1
Before you begin
This chapter provides an overview of the process for operating and
maintaining the Magellan Passport node. Operations and maintenance
procedures are completed using either a text interface device or Nortels
proprietary Magellan Network Management System (NMS).
Before reading this chapter, you should be familiar with Passport and its
capabilities as described in 241-7001-110, Passport General Description.
Prerequisites
Before you can use the procedures described in this document, the Passport
node must be fully installed and connected to the network as described in the
following documents:
241-7001-125, Passport Hardware Installation Guide
241-7001-130, Passport Startup Guide
Also, either a text interface device or a network management workstation
must be set up. See 241-7001-125, Passport Hardware Installation Guide for
details on how to connect a text interface device.
Except where noted, descriptions and procedures are provided for operators
working with Passport through a VT-100 terminal or a terminal emulator. If
you are using Nortels proprietary Magellan Network Management System
(NMS) see 241-6001-023, NMS Architect for Passport User Guide.
44 Chapter 1
241-7001-150 4S3
Denition of operations and maintenance
The operations and maintenance of a Passport node includes procedures for
software installation, provisioning, monitoring, data collection, and fault
management.
The process
There are six steps (summarized in the following paragraphs) involved in
operating and maintaining a Passport node. These steps are also used for the
process of upgrading software.
Step 1: Install and congure the software
After you have completed all hardware installation and start-up procedures,
you can install and configure the Passport software.
Software installation on page 165 provides information on how to install
and configure the software on the Passport.
Step 2A and B: Provision the node
After the software is installed, you complete additional provisioning
activities required for node security and user services.
Provisioning system description on page 85 provides introductory
information that serves as a basis for the provisioning tasks presented in
subsequent chapters.
Initial node provisioning steps on page 201 summarizes the
provisioning process for a Passport node.
Provisioning node security is described in Node security on page 205.
Provisioning trunks is described in Node provisioning on page 217.
Provisioning cards is described in Processor card provisioning on
page 293.
Step 3: Set up data collection
The next step is to set up data collection. This involves making any necessary
changes to the default settings on agents, collectors, and spoolers on the node,
and setting up Magellan NMS to collect accounting data for transfer to a
billing host.
Before you begin 45
Passport Operations and Maintenance Guide 4S3
Setting up agents, collectors, and spoolers is described in Data collection
on page 459. Setting up accounting data collection is described in
241-7501-400, Passport Accounting Reference Guide.
Step 4: Test new hardware
Test all new hardware to ensure that it is operating within specified
parameters. Procedures for testing new hardware are provided in Diagnostic
tests on page 523.
Step 5: Monitor the node
Once the node is up and running, you should continually monitor it to ensure
that it is operating at peak efficiency and to detect any faults that may occur.
Node monitoring on page 425 describes how to list and display
components and attributes that define Passport functionality.
Step 6: Maintain the node
Node maintenance involves the following tasks:
provisioning as service needs change and grow, as described in Node
security on page 205 and Node provisioning on page 217
testing new hardware that is added to expand services or increase
redundancy, as described in Diagnostic tests on page 523
detecting and replacing faulty hardware, as described in
Component control on page 407
Diagnostic tests on page 523
Shelf management on page 599
Troubleshooting the Passport node on page 493
adding new software, as described in Shelf management on page 599
46 Chapter 1
241-7001-150 4S3
47
Passport Operations and Maintenance Guide 4S3
Chapter 2
Passports text interface
This chapter describes how to use a text interface such as a VT-100 terminal
or terminal emulator when provisioning, operating, and monitoring a
Passport node. The text interface characteristics depend on whether you are
in provisioning mode, in operational mode, or encountering alarms. The
characteristics of these modes are described in the following sections.
Except where noted, descriptions and procedures are provided for operators
working with Passport through a VT-100 terminal or a terminal emulator. If
you are using Northern Telecoms proprietary Magellan Network
Management System (NMS) see 241-6001-023, NMS Architect for Passport
User Guide.
Provisioning mode and operational mode
Provisioning mode is used to create and modify views of current data or data
on file. Operational mode is used to display current operating parameters and
conditions.
Provisioning mode and operational mode are distinguished by two
characteristics:
the interface prompt
the defaults for information displayed.
These characteristics are described below.
48 Chapter 2
241-7001-150 4S3
Interface prompt
The command line prompt is the most indicative feature of each mode since
it is always displayed on-screen. When in provisioning mode, the prompt for
the command line appears as
PROV #>
where:
# is the current command number
When in operational mode, the prompt for the command line appears as
#>
where:
# is the current command number
As you enter commands, the system interprets the validity of each command.
If the command is valid, the interface responds with ok and processes the
command. If the command is not valid, the system responds with command
failed and does not process it.
Default information
When in provisioning mode, the interface defaults to operating with
provisioning data. For example, if you issue a display command in this mode,
the system displays provisioning data associated with the specied
component. For more information on provisioning data, see Provisioning
system description on page 85.
When in operational mode, the interface defaults to operational data - that is,
the component and attribute settings currently in use. For example, if you
issue a display command in this mode, the system displays operating data
associated with the specied component.
The text interface screen
The user interface on a VT-100 terminal or terminal emulator consists of
commands that you enter,
responses to those commands provided by the Passport system.
Passports text interface 49
Passport Operations and Maintenance Guide 4S3
Both commands and responses have specific formats so that you can interpret
them more effectively.
The topics in the next sections introduce you to text interface screens, both
commands and alarms.
Command screens
Format of screenprovisioning mode or operational mode on page 49
shows the format of the text interface for either provisioning mode or
operational mode. Descriptions of all fields shown follow in Fields of the
text interface on page 50. Sample screen, valid command in provisioning
mode on page 51, Sample screen, invalid command in provisioning mode
on page 52, and Sample screen, command failed because of syntax error on
page 53 provide examples of how the text interface behaves in different
situations when you are issuing commands.
Figure 1
Format of screenprovisioning mode or operational mode
PPT 0769 001 AA
prompt #> <command> command line
<component>
<data>
.
. response
.
<data>
<status> <date> <time> status line
50 Chapter 2
241-7001-150 4S3
Table 1
Fields of the text interface
Field Description
prompt The system prompt differs according to the mode
(operational or provisioning). The prompt for
provisioning mode is PROV #>. The prompt for
operational mode is #>.
command The command field can be one of many forms. For a
description of acceptable command formats, see
"Command format", on page 64.
component The full name of the component including the instance
value associated with it (if any). Example: FrUni/5.
data The systems response to the command.
Responses vary according to the command and the
component. For example, the data field may begin with
a line of text such as The following components
have been created, followed by a list of data. In the
case of an unsuccessful command, the data field
provides details on why the command has failed. For
example, Invalid syntax.
For a description of all possible responses, see the
appropriate section of 241-7501-210, Passport
Components.
status Status indicates that the command has executed or
failed.
If the command is successful, the status appears as ok.
If the command is unsuccessful, the status appears as
command failed.
date These fields indicate the date the command executed or
failed.
time The time the command executed or failed. The format is
YYYY-MM-DD HH:MM:SS.SS.
Passports text interface 51
Passport Operations and Maintenance Guide 4S3
Command responses
The command response consists of the component, the data, and the status
elds. If the system cannot process the command, the response is called an
error response.
Figure 2
Sample screen, valid command in provisioning mode
Figure 3
Sample screen, valid command in operational mode
PPT 0770 001 AA
PROV 4> set shelf card/1 cardType de1
Shelf Card/1
ok 1993-05-04 18:15:52.67
PROV 5>
5> display -p shelf card/1
Shelf Card/1
cardType = V35
configuredLPs = Lp/2
ok 1993-05-04 18:15:54.03
6>
PPT 0022 001 AA
52 Chapter 2
241-7001-150 4S3
Figure 4
Sample screen, invalid command in provisioning mode
Command syntax errors
When elements of the command line cannot be interpreted, the command is
invalid and the system issues a syntax error. A syntax error occurs if one of
the following conditions apply:
The type of component, attribute, or option name is unknown or invalid.
The particular name of the component is not dened in the system.
The component instance number is incorrect.
An incorrect data type is entered.
Note: See "Data types" on page 65 for information on data types and
proper syntax. See 241-7501-210, Passport Components, for
information on specic components.
The value associated with a particular attribute for input does not match
the acceptable value range for the eld.
An invalid command is entered (that is, you cannot apply the verb to the
component or attribute).
PPT 0771 001 AA
PROV 9> add shelf
Shelf
The 'Add' command is not allowed for this component.
command failed 1996-06-12 12:29:59.58
PROV 10>
Passports text interface 53
Passport Operations and Maintenance Guide 4S3
Syntax error format
All syntax errors have a common format. Sample screen, command failed
because of syntax error on page 53 shows a command that has failed because
of a syntax error. The error response contains the following elds:
Invalid syntaxGives the reason that the data cannot be interpreted.
The text contained in curly brackets { } indicates the problem area. The
text that follows the brackets identies the problem. In the sample screen
in Sample screen, command failed because of syntax error on page 53,
the system cannot interpret the attribute or group identier.
InputRepeats the command and includes curly brackets { } around
the element which it could not interpret. In the example, an invalid
attribute, serviceCategory, causes the command to fail.
The status line follows with a statement that the command has failed.
Figure 5
Sample screen, command failed because of syntax error
Keyboard shortcuts
The text interface provides a set of keyboard shortcuts that can be used to
accelerate your work in either provisioning and operational mode. Many of
these shortcuts permit you to edit the command line. Other shortcuts permit
you to control the display of the system response. Keyboard shortcuts on
page 54 summarizes these shortcuts.
PPT 0768 001 AA
11> lck shelf
Shelf
Invalid syntax: (verb) incompatible with <components>.
Input: (lck) <shelf>
command failed 1996-06-12 12:33:18.38
12>
54 Chapter 2
241-7001-150 4S3
Table 2
Keyboard shortcuts
Key Description
Up-Arrow Recalls recently used commands for edit or reuse.
Up to 10 commands are held in a queue. Each
time you press the Up-Arrow key, you step back
through the commands in the queue.
Down-Arrow Allows you to step forward through the command
queue.
Left-Arrow and
Right-Arrow
Moves the cursor over the command presently
shown without affecting the characters in the
command.
Backspace or Delete Deletes the character before the cursor.
Control-D Deletes the character under the cursor.
Control-A Moves the cursor to the beginning of the
command.
Control-E Moves the cursor to the end of the command.
Control-K Deletes text from the cursor character to the end
of the command.
Return Sends the edited command.
Control-S Suspends the response to a command.
This keystroke is useful where a command
response is longer than 24 lines.
If you suspend output for too long a period,
buffering limitations may cause the interface to
discard some subsequent output. If the session is
registered to display a data stream (alarm, SCN,
log, or debug data), any of this data that is
generated in the time the response was frozen are
discarded.
If a Telnet interface is frozen for a long time, and a
large amount of subsequent output is queued, the
underlying TCP connection may time out and
terminate itself, bringing down the Telnet session.
(Sheet 1 of 2)
Passports text interface 55
Passport Operations and Maintenance Guide 4S3
Alarm screens
Alarm format on page 55 shows the format of a Passport alarm as it is
displayed on a text interface device.
Figure 6
Alarm format
For complete information on alarm formats and OSI states, see 241-7501-
230, Passport Alarms.
Control-Q Resumes suspended output.
Control-C Cancels a response, and can be used to interrupt
and discard an overly long response. One Control-
C cancels only the current response, and does not
affect other queued responses.
Table 2 (continued)
Keyboard shortcuts
Key Description
(Sheet 2 of 2)
<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>]
<Component name>; <date> <time>
PPT 0025 001 AA
56 Chapter 2
241-7001-150 4S3
57
Passport Operations and Maintenance Guide 4S3
Chapter 3
Operator commands
This chapter describes the common commands that can be issued while
provisioning, operating, or monitoring a Passport.
The chapter begins with a description of operational fundamentals and ends
with detailed descriptions of all common Passport commands. After reading
this chapter, you will have a good understanding of common operator
commands. Before proceeding with this chapter, you should be familiar with
the information in Passports text interface on page 47.
Except where noted, descriptions and procedures are provided for operators
working with Passport through a VT-100 terminal or a terminal emulator. If
you are using Nortels proprietary Magellan Network Management System
(NMS) see 241-6001-023, NMS Architect for Passport User Guide.
Related documents
For additional information related to operator commands, see 241-7501-210,
Passport Components.
NMS sessions and operational parameters
Passport supports up to 35 NMS sessions simultaneously.
Under congested conditions, NMS sessions for operators with impact of
system administrator or less may not be read, which in turn may cause NMS
to drop the connections after a time-out period; only NMS sessions for
operators with impact of debug are read. Even under severely congested
conditions, NMS sessions for operators with impact of debug are maintained.
Commands are read serially until congestion is reduced or eliminated.
58 Chapter 3
241-7001-150 4S3
Session management is handled by the system. Provisioning and operator
intervention are not required.
The objective of this approach is to reduce traffic overhead incurred by
operations and maintenance commands from operators, when these
commands are not essential for maintenance or fault clearing. In this way, the
system provides mechanisms for automatically governing operator traffic
without isolating the node entirely. The ramifications are that surveillance for
the node is temporarily lost until congestion is reduced, but connections
supporting essential maintenance and fault clearing functions are maintained.
Component-specic commands
This chapter describes Passport common commands only and does not deal
with component-specific commands. For details on these commands, see
241-7501-210, Passport Components.
ProvisioningSystem commands are covered in Provisioning system
description on page 85.
Operational fundamentals
The next sections introduce you to some operational fundamentals, including
command capability sets
operator modes
Passport views
Capability sets
Every command has a capability set associated with it. The capability set
indicates what type of authorization is required to query, modify, delete, or
create a component and its attributes.
Each operator has an associated scope, impact and customer identier (CID).
A combination of scope, impact, and CID determines each operators
capability set.
For information, see Userid and its attributes on page 207.
Operator commands 59
Passport Operations and Maintenance Guide 4S3
Common commands and operator modes
When and how you use Passport commands, depends on the current operating
mode. At any given time, you will either be in operational mode or
provisioning mode. For additional information on modes, see "Provisioning
mode and operational mode" on page 47.
Common commands that can be used in operational mode
These commands are used outside of provisioning mode, and can be applied
to almost all Passport components. These commands include
display
list
set
help
lock
unlock
Common commands that can be used in provisioning mode
These commands are common to all components, and can be applied to
almost all Passport components. These commands include
add
delete
display
list
set
help
Provisioning system commands
These commands are specic to the ProvisioningSystem component. They
include
activate prov
apply prov
check prov
60 Chapter 3
241-7001-150 4S3
clear prov
commit prov
conrm prov
copy prov
end prov
load prov
save prov
start prov
stop prov
tidy prov
For more information on provisioning system commands, see Provisioning
system description on page 85
Component-specic commands
These commands are unique to individual Passport subsystems. Most
component-specific commands are operational commands.
Operator commands
The following sections provide
some hints on using Passport commands
rules about command format and syntax
detailed descriptions of all Passport common commands
A command quick reference provides a summary of common commands.
Command quick reference
To quickly find the command you need, see Quick reference to operator
commands on page 61.
Operator commands 61
Passport Operations and Maintenance Guide 4S3
Table 3
Quick reference to operator commands
Command Description Modes Location
help Used to provide information about commands,
components and attributes.
Provisioning
Operational
"help (h)" on
page 65
set Used to change the value of an attribute for a
particular component.
Provisioning
Operational
"set (s)" on
page 68
add Used to add a new component to the edit view. Provisioning "add (a)" on
page 70
delete Used to remove a component (and its
subcomponents) from the edit view.
Provisioning "delete (del)"
on page 71
list Displays subcomponents of a component. In
provisioning mode, by default, list applies to
provisioned subcomponents in the edit view. In
operational mode, by default, list applies to all
operational and provisioned subcomponents in the
current view.
Provisioning
Operational
"list (l)" on
page 72
display Used to display all the attributes for a particular
component in a particular view. In provisioning
mode, by default, display applies to provisionable
attributes of a component in the edit view. In
operational mode, by default, display applies to all
operational attributes of a component in the current
view.
Note: When the wildcard character (*) is appended
to a component name, the display format is tabular,
unless the notabular (-n) option is used.
Provisioning
Operational
"display (d)"
on page 74
lock Used to prevent additional use of a component,
such that eventually the component will not be in
use operationally.
Operational "lock" on
page 82
unlock Used to change the operational use of a
component. It is normally used after the lock
command. After unlock has been issued, the
component is ready to provide service.
Operational "unlock" on
page 83
62 Chapter 3
241-7001-150 4S3
Some hints for using commands
The following sections provide some hints for entering command data
quickly and easily. Topics include
component and attribute abbreviations
verb abbreviations
case sensitivity
Component and attribute abbreviations
When entering options, component names, enumerated values and attribute
names you can use either the abbreviation of the option, component,
enumerated option or attribute, or the minimum amount of characters to
unambiguously identify the full name or the abbreviation.
For example, for the ProvisioningSystem(prov) component, you may type the
full name:
display ProvisioningSystem
or you may type the abbreviation:
display prov
or you may try typing the rst couple of letters:
display pr
The system will check to see if there are any other components that
correspond to this combination of characters. If the combination is truly
unambiguous, it will be accepted. If the characters correspond to more than
one component, it is considered ambiguous and the system will not accept it.
The interface will indicate the ambiguity by issuing an error response.
Note: Although some component and attribute abbreviations are
included in this guide, you should consult 241-7501-210, Passport
Components, for a complete listing of abbreviations.
Verb abbreviations
A verb is the action portion of the command form (for example, set, add,
lock, display, and so on). You may type verbs using
the full name
Operator commands 63
Passport Operations and Maintenance Guide 4S3
the abbreviation
the shortest unambiguous match
Note 1: Whenever verbs appear with upper and lowercase characters,
you must match the uppercase exactly.
Note 2: Verb abbreviations are included in the individual command
descriptions beginning with help (h) on page 65.
Case sensitivity
The general rule for case sensitivity is that the system does not distinguish
between upper and lowercase characters for verbs, components and
attributes. You may use all lowercase characters even if the full name and
abbreviation contain uppercase characters.
For example, for LogicalProcessorType (Lpt) component, you may type:
logicalprocessortype
or you may try:
logicalprocessorty
or use the abbreviation:
lpt
There are two exceptions to the general case sensitivity rule. The interface is
case sensitive when interpreting, processing and displaying the following:
string attribute values
string option values
Detailed command descriptions
The following sections provide detailed descriptions of all Passport common
commands. Each detailed description includes the following:
Verb abbreviationthe verb abbreviation, if any, is included in
parenthesis beside the verb title
For example, in add (a) on page 70, the add verb is followed by (a).
This means that you may type an a rather than the full word add.
Descriptionwhat the command does
64 Chapter 3
241-7001-150 4S3
Syntaxthe form the command must take. Wherever possible, the
abbreviated command options are used, allowing you to type commands
quickly and decreasing the chance of error.
Impactthe level of operator capability required to use a command
Optionsthe options that make the command behave in a manner other
that specied by its default
Examplespractical examples of how to use the command. See the
section titled Conventions on page 41.
Command format
Before issuing any commands discussed in the following sections, it is
important that you understand proper command syntax and format.
Syntax conventions
All command descriptions in this chapter follow these conventions:
nonproportional spaced bold type
Nonproportional spaced bold type represents words that you should type.
[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.
|
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.
Command forms
All common commands use a variation of the following form:
verb [-options[(option_value)]]... component_name
[attribute_name| group_name]...
Operator commands 65
Passport Operations and Maintenance Guide 4S3
A verb is the action portion of the command form.
An option (in some cases, accompanied by an option_value) causes the
command to behave in a manner other than that dictated by its defaults.
A component name consists of a sequence of the component type followed by
the component instance value. For example, FrUni/5 DLCI/64 is a
component name. In the case where only one instance of a component can
exist on a Passport (for example, the Shelf component), the component type
appears by itself and is not appended by a component instance.
The component type is a component without a particular instance value.
For example, FrUni is a type since it species a particular type of
component, but does not specify a particular FrUni instance on the node.
The component instance is the unique name (under a particular
component type) that is used to specify the name of a particular instance
of a component class. For example, in FrUni/5, 5 is the instance.
The term component class is also used in some of the commands and
command examples in this chapter. Component class is a concatenation of
component types. For example, FrUni Dlci is a component class because it
does not contain any instance values.
Error responses
If the system cannot interpret and process the command, it displays an error
response to indicate the failure. For a description of all possible error
messages see 241-7501-210, Passport Components.
Data types
When issuing a set command, you should be aware of data types. Data types
specify the structure of the attributes data (for example, decimal, hex, BCD,
to name a few). A data type species the set of values it can assume for an
attribute. See 241-7501-210, Passport Components for further information
on data types.
help (h)
The help command is used to view information about commands,
components, and attributes. The help command may be entered in any mode
(provisioning or operational) and can be used in several ways.
66 Chapter 3
241-7001-150 4S3
Syntax
help [component_class]
Provides a description of the component class, a list of attributes of the
component class, a list of verbs that can be applied to the component class,
and the list of allowed subcomponents.
If the component class is not specied, the following information is
displayed:
a list of verbs that do not require a component (that is, verbs that can be
applied to the node)
a list of allowed top-level components
details of the command
help component_class {attribute_name| group_name}
Displays detailed information on the attributes or attribute groups specified.
help -verb(verb) [component_class]
Displays a detailed description of the verb specified.
help -sub[component_class]
Displays a hierarchical diagram of the types of components that can exist as
subcomponents of the specified component.
Impact
Passive
Operator commands 67
Passport Operations and Maintenance Guide 4S3
Options
The help command and syntax errors
When issuing the help command, a syntax error can result if you enter an
invalid component name, type, or attribute.
In the event of a syntax error, the system response always species the invalid
item, (that is, the verb, component, or attribute) with curly brackets {}. For
example:
Help rtg top xxxxx
displays the following response:
Rtg Top
Invalid syntax: {component/attribute/group name}
unexpected, value unrecognized.
Input=Help rtg top {xxxxx}
command failed 1993-07-08 03:13:05.14
The brackets indicate that xxxxx is invalid.
By reissuing the help command (this time applying it to the component that
appears just before the invalid item), you can get a list of what
subcomponents and attributes are valid for the component. For example:
Help rtg top
displays a list of all valid subcomponents and attributes for the Topology
component.
You can now retry the command, substituting the invalid xxxxx with the
proper component or attribute.
Table 4
Options for the help command
Option Abbreviation Description
-verb -v Used to display a verbs full name and
abbreviation, its impact, and a list of
available options
-subcomponent -sub Used to display full component class
hierarchy
68 Chapter 3
241-7001-150 4S3
Examples
Here are some examples of typical command usage.
Using help:
help
Displays help command usage, the node name, top-level components,
subcomponents and verbs.
Using help to nd out the options of the start prov command:
help -verb(start) prov
Both the impact and the possible options for the verb appear.
Using help to nd out information on a component class:
help shelf card
Displays the instance type, scope, subcomponents, provisionable
attribute groups, operational attribute groups, and verbs that can be
issued against the component.
Using help to nd out the subcomponent hierarchy of a component class:
help -sub software
The software component hierarchy appears.
Using help to nd out information on an attribute of a component class:
help sw lpt/CP featureList
Displays the read and write access, the criticality, the data type, the
possible values, and the default (if any) for the attribute.
set (s)
The set command is used to change the value of an attribute for a particular
component. Provisionable attributes can be modied only while you are in
provisioning mode. Some operational attributes can be set when you are in
provisioning or operational mode.
Note: The set command can be issued once to set multiple attributes of
a component. If the system cannot set one of the attributes, the best
effort approach is applied to set the remaining attributes. That is, some
attributes may be successfully set while other may fail.
Operator commands 69
Passport Operations and Maintenance Guide 4S3
Syntax
set component_name attribute_name attribute_value
[,attribute_name attribute_value]...
The specific syntax of the attribute value depends on the data type of the
attribute name.
For information on data types, see 241-7501-210, Passport Components.
Impact
Configuration
Options
There are no options for this command.
Note: Some attributes may require a higher impact value. See 241-7501-
210, Passport Components for information on write access for specic
attributes.
Examples
Here are some examples of typical command usage.
Successfully setting a Card components cardType attribute:
First display all the cards on the shelf to determine the attribute that
requires setting:
display -n shelf card/*
A list of all existing cards and their attributes appears:
Shelf Card/0
cardType = CP
configuredLPs = LP/0
Shelf Card/1
cardType =
configuredLPs =
Use the set command to set the cardType attribute (for example, V35):
set shelf card/1 cardtype V35
Now display all the cards on the shelf again to see the change:
display -n shelf card/*
70 Chapter 3
241-7001-150 4S3
Shelf Card/0
cardType = CP
configuredLPs = LP/0
Shelf Card/1
cardType = V35
configuredLPs =
Similarly, you can use the set command to set the conguredLPs
attribute.
add (a)
The add command is used to create a component (with its default values) in
the edit view. Add can be used only in provisioning mode.
By default, all superior components must already exist for add to be
successful. You can use the -superiors option to override this and
automatically create all superior components that do not currently exist.
Associated with every component type is a set of default values for each of
its attributes. When you add a particular instance of a component type, the
attributes for the component are set to the default values.
Note 1: All mandatory subcomponents are added by the system. Only
the rst six subcomponents are shown; if there are more than six
subcomponents, a message indicates the number of unseen
subcomponents.
Note 2: To add a component associated with a new feature or
application, that feature or application must be specied in the software
application version list or feature list. See Software installation on
page 165, and, for information on specic components, to 241-7501-
210, Passport Components.
Syntax
add [-superiors] component_name
Impact
Configuration
Note: Some components may require a higher impact. See 241-7501-
210, Passport Components for information on specic components.
Operator commands 71
Passport Operations and Maintenance Guide 4S3
Options
Example
Here is an example of typical command usage.
Creating a component (for example, a LogicalProcessor component):
add lp/<n>
where:
<n> is the instance value of the logical processor
A message appears indicating that the component has been created.
delete (del)
The delete command is used to remove a component (and its subcomponents)
from the edit view. Delete is used in provisioning mode only.
All provisioned links between the deleted component and any other
component are also removed from the edit view.
Activating the edit view results in the removal of the deleted components and
subcomponents from the running system. This terminates the service
provided by these components and their subcomponents.
Note 1: The copy prov command can be used to undo an accidental
delete. See "copy prov" on page 119.
Note 2: You may not be able to remove some components using the
delete command. In this situation, you can use the clear prov command
with the removedFeature option. See "clear prov" on page 113 for details.
Syntax
delete component_name
Table 5
Options for the add command
Option Abbreviation Description
-superiors Shortest
unambiguous
match
Specifies that all superior components
referenced in component_name, which
do not currently exist, should be
created.
72 Chapter 3
241-7001-150 4S3
Impact
Configuration
Note: Some components may require a higher impact. See 241-7501-
210, Passport Components for information on specic components.
Options
There are no options for this command.
Examples
Here are some examples of typical command usage.
Deleting a component (for example, a LogicalProcessor component):
delete lp/<n>
where:
<n> is the instance value of the logical processor
A message appears indicating that the component has been deleted.
Attempting to delete a permanent component (for example, a Shelf
component):
delete shelf
A message appears indicating that the command is not allowed for this
component.
list (l)
The list command is used to display the subcomponents of a particular
component in a particular view.
The component you specify can be either a component name, in which case
all the subcomponents of the named component are listed, or it can have the
following form:
[<component_name>] <component_type>/*
in which case only the subcomponents of the component which are of the
specied type are listed.
If the operator session is in provisioning mode, the component instances
displayed are those in the edit view, and only provisioned
subcomponents are displayed.
Operator commands 73
Passport Operations and Maintenance Guide 4S3
If the operator session is not in provisioning mode, the component
instances displayed are those in the current view, and both provisioned
and operational subcomponents are displayed.
Syntax
list [-c] [-p] [-o] [component_name] [component_type/*]
Note: Even if a component is not replicated (that is there can only be one
instance of it), the system accepts the wildcard character (*).
Impact
Passive
Options
Examples
Here are some examples of typical command usage.
Listing all top-level components:
list
A list of all the nodes top level components appears.
Listing all top-level components of the FrameRelayUni (FrUni)
component that exist in the current view:
list -c FrUni/*
A list of all FrameRelayUni components appears.
Table 6
Options for the list command
Option Abbreviation Description
-current -c Used to display subcomponents from
the current view when you are in
provisioning mode.
-provisioned
Components
-p Used to display provisioned
subcomponents of a component.
-operational
Components
-o Used to display operational
subcomponents of a component.
74 Chapter 3
241-7001-150 4S3
Listing all subcomponents of a particular component (for example
FrUni/1) while you are in provisioning mode:
list FrUni/1
A list displaying all the subcomponents of the component appears.
Note: The /* notation is also permitted for components that are not
replicated. For example to list all Shelf components, type:
list shelf/*
A list of all the shelf components appears.
display (d)
The display command is used to show the operational or provisioned (or both)
attributes for a particular component or set of components.
The output of the display command varies depending which mode you are
currently in, whether or not you specify the groups or attributes, and which
options you choose. Some components have so many attributes that not all
can be shown. An indication of the hidden attributes is made in front of the
table. To see the hidden attributes, use the -notabular (-n) option or specify
those attributes explicitly.
The operator can modify the screen width to accommodate all the attributes
and the Response column by using the set command as shown in the example
below. The screen width ranges from 79 to 2000 characters.
Example
me
indicates the current connection, such as:
Nmis Telnet Session/1
To change the screen width, use the following format:
set Nmis Telnet Session/1 width 132
Nmis Telnet Session/1
ok 1994-10-14 23:28:10:12
Operator commands 75
Passport Operations and Maintenance Guide 4S3
If you are in provisioning mode, display defaults to display the provisioning
data in the edit view. If you are not in provisioning mode, display defaults to
display operational data in the current view.
Syntax
To display the values of all provisioning or operational attributes for a
component in a particular view, use one of the following forms:
display [-c] [-p] [-o] <component_name>
display [-c [-p] [-o] <component_name> *
display [-c] [-p] [-o] [<component_name>]
<component_type>/*
Appending a wildcard character * to the component_name or
component_type allows the command to target multiple components and the
display format is tabular. You can use wildcard characters and request the
line-by-line (non-tabular) format by using the -n (notabular) option.
display -n [-c] [-p] [-o] <component_name> *
display -n [-c] [-p] [-o] [<component_name>]
<component_type>/*
To display specic attribute information about a particular component:
display [-c] <component_name> <attribute_name>
display [-c] [<component_name>] <component_type>/*
[<attribute_name>]
To display attribute groups of a component in the indicated view by using one
of the following forms:
display [-c] <component_name> <attribute_group_name>
display [-c] [<component_name>] <component_type>/*
<attribute_group_name>
Impact
Passive
Note: Some attributes may require a higher impact value. See the read
access specication for the attribute in 241-7501-210, Passport
Components.
76 Chapter 3
241-7001-150 4S3
Options
The output of the display command varies depending on the mode you are
currently in, whether or not you specify the groups or attributes, and which
options you choose. The following situations indicate which combinations of
options will work for you in operational mode and provisioning mode.
You are in provisioning mode and you specify a group or attribute.
Note: The default view in provisioning mode is the edit view.
To display specific data in the edit view:
d <component_name> <attribute_name>
To display specic data in the current view:
d -c <component_name> <attribute_name>
You are in provisioning mode you do not specify a group or attribute. The
default view in provisioning mode is the edit view.
To display attributes in the edit view (if any)
d <component_name>
Table 7
Options for the display command
Option Abbreviation Description
-current -c Used to display data from the current
view when in the provisioning mode.
-provisioned
Data
-p Used to display provisioned data.
Provisioned data (or attributes),
configured by the network operator or
administrator, cause Passport
subsystems or services to perform or
behave in a certain manner.
-operational
Data
-o Used to display operational data.
Operational data (or attributes)
provides information used for
monitoring the operation of Passport
and its services (for example, OSI state,
status and statistical data.)
Operator commands 77
Passport Operations and Maintenance Guide 4S3
To display operational data in the current view
d -c -o <component_name>
To display all provisioned attributes in the current view
d -c <component_name>
To display both operational and provisioned data in the current view:
d -c -o -p <component_name>
You are in operational mode and you specify a group or attribute. The
default view in operational mode is the current view.
To display all data for a particular component in the current view
d <component_name> <attribute_name>
where:
<attribute_name> is either a provisioned attribute or an operational
attribute
You are in operational mode and you do not specify a group or attribute.
The default view in operational mode is the current view.
To display all operational attributes of a component
d <component_name>
To display the provisioned attributes in the current view
d -p <component_name>
To display both provisioned and operational attributes of a component:
d -o -p <component_name>
Examples
Here are some examples of typical command usage.
To display all provisioned attributes of a component, for example, the
FrameRelayUni (FrUni) component:
display FrUni/<n> Framer
where:
<n> is the instance value of the FrUni component
To successfully display a single attribute of a component:
78 Chapter 3
241-7001-150 4S3
display FrUni/<n> Framer crcError
Note: crcError is an attribute of the Framer component.
Selected attributes of a component can be displayed by separating the
attribute names with commas. For example, to display usage state and
remote end of all trunks on a module:
display -o -c trk/* usage, remote
Note: usage and remote are attributes of the Trunk component.
To display a provisioned attribute of all existing components of a
particular component type
display FrUni/* customerIdentifier
Note: * is a wildcard character representing all FrUni components, and
customerIdentier is an attribute of the FrUni component.
To display all the operational attributes of a component (from the current
view) while you are in provisioning mode:
display -o -c FrUni/1
To display all the provisionable attributes of a component (in the current
view) while you are in operational mode:
display -p FrUni/1
To display the provisionable attributes of a component, for example, the
LogicalProcessor (lp) component, in tabular format, enter the following:
d lp/*
The display format on an 80-character width screen is as follows:
EM/OTTAWA
Use -noTabular to see the many hidden attributes.
+==+-----+----+-----+--------------------+------+------+-------
|Lp|osiAd|osiO|osiUs| activeCard |mainCa|spareC|restart
| | min |per | age | |rdStat|ardSta|OnCpSwi
| | | | | | us | tus | tch
+==+-----+----+-----+--------------------+------+------+-------
| 0|unlck|ena |activ|Shelf Card/0 |active|notPro|false
| 1|unlck|ena |activ|Shelf Card/1 |active|notPro|false
| 4|unlck|ena |activ|Shelf Card/4 |active|notPro|false
| 5|unlck|ena |activ|Shelf Card/5 |active|notPro|true
ok
Operator commands 79
Passport Operations and Maintenance Guide 4S3
To display the attributes not listed in the table in line-by-line format, use
the notabular option. Enter the following:
d -n lp/0
The display format is as follows:
Lp/0
adminState = unlocked
operationalState = enabled
usageState = active
availabilityStatus =
proceduralStatus =
controlStatus =
alarmStatus =
standbyStatus = notSet
unknownStatus = false
activeCard = Shelf Card/0
mainCardStatus = active
spareCardStatus = notProvisioned
restartOnCpSwitch = false
memoryCapacity = fastRam : 22991 kbyte
normalRam : 22991 kbyte
sharedRam : 22991 kbyte
sharedMsgBlockCapacity = 512 kbyte
localMsgBlockCapacity = 512 kbyte
timeInterval = 7 minutes
cpuUtil = 0 %
cpuUtilAvg = 4 %
cpuUtilAvgMin = 1 %
cpuUtilAvgMax = 25 %
memoryUsage = fastRam : 0 kbyte
normalRam : 17175 kbyte
sharedRam : 0 kbyte
memoryUsageAvg = fastRam : 0 kbyte
normalRam : 17174 kbyte
sharedRam : 0 kbyte
memoryUsageAvgMin = fastRam : 0 kbyte
normalRam : 17145 kbyte
sharedRam : 0 kbyte
memoryUsageAvgMax = fastRam : 0 kbyte
normalRam : 17185 kbyte
sharedRam : 0 kbyte
sharedMsgBlockUsage = 4 kbyte
sharedMsgBlockUsageAvg = 2 kbyte
80 Chapter 3
241-7001-150 4S3
sharedMsgBlockUsageAvgMin = 0 kbyte
sharedMsgBlockUsageAvgMax = 8 kbyte
localMsgBlockUsage = 5 kbyte
localMsgBlockUsageAvg = 3 kbyte
localMsgBlockUsageMin = 0 kbyte
localMsgBlockUsageMax = 29 kbyte
ok
To display specic attributes of a component in tabular format, enter the
following:
d lp/* OsiAdmin, OsiUsage
The display format on an 80-character width screen is as follows:
EM/OTTAWA
+==+-----+-----+----------------------------------------
|Lp|osiAd|osiUs|Response
| | min | age |
+==+-----+-----+----------------------------------------
| 0|unlck|activ|
| 1|unlck|activ|
| 4|unlck|activ|
| 5|unlck|activ|
ok
Note: The Response column does not always appear in the tabular
format; this column is displayed only if there is sufcient space. This is
also true for attribute columns.
To display the same attributes in line-by-line format, use the notabular
option. Enter the following:
d -n lp/* OsiAdmin, OsiUsage
The display format is as follows:
Lp/0
adminState = unlocked
usageState = active
Lp/1
adminState = unlocked
usageState = active
Lp/4
adminState = unlocked
usageState = active
Lp/5
adminState = unlocked
Operator commands 81
Passport Operations and Maintenance Guide 4S3
usageState = active
ok
To display the attributes of a multi-indexed component in tabular format,
enter the following:
d vr/1 snmp acl/*
The display format on an 80-character width screen is as follows:
Vr/1 Snmp Acl/*
+======+=======+=========+-------+-------+------
|target|subject|resources| priv |storage|status
| | | |r v| |
| | | |e 2| |
| | | |s g t| |
| | | |p s e r| |
| | | |o e t a| |
| | | |n t s p| |
+======+=======+=========+-------+-------+------
| 1| 2| 1|. . * .|nonVol |active
| 2| 1| 1|* . . *|nonVol |active
| 3| 4| 2|. * * .|nonVol |active
| 4| 3| 2|* . . .|nonVol |active
ok
Note 1: The component instance (index) columns are separated by a
double dashed line (===) and the attribute/response columns are
separated by a single dashed line (---).
Note 2: In the above display example, priv is a bit set attribute where *
indicates an ON bit and . indicates an OFF bit.
To display the same attributes in line-by-line format, use the notabular
option. Enter the following:
d -n vr/1 snmp acl/*
The display format is as follows:
Vr/1 Snmp Acl/1,2,1
privileges = ~response ~set gets ~v2trap
rowStorageType = nonVolatile
rowStatus = active
Vr/1 Snmp Acl/2,1,1
privileges = response ~set ~gets v2trap
rowStorageType = nonVolatile
rowStatus = active
Vr/1 Snmp Acl/3,4,2
82 Chapter 3
241-7001-150 4S3
privileges = ~response set gets ~v2trap
rowStorageType = nonVolatile
rowStatus = active
Vr/1 Snmp Acl/4,3,2
privileges = response ~set ~gets ~v2trap
rowStorageType = nonVolatile
rowStatus = active
ok
To display the attributes of a specic index within a multi-indexed
component, enter the index value:
d vr/1 snmp acl/*,*,1
The display format on an 80-character width screen is as follows:
Vr/1 Snmp Acl/*
+======+=======+=========+-------+-------+------
|target|subject|resources| priv |storage|status
| | | |r v| |
| | | |e 2| |
| | | |s g t| |
| | | |p s e r| |
| | | |o e t a| |
| | | |n t s p| |
+======+=======+=========+-------+-------+------
| 1| 2| 1|. . * .|nonVol |active
| 2| 1| 1|* . . *|nonVol |active
ok
To display a specic attribute of a specic index within a multi-indexed
component, enter the index value and the attribute name:
d vr/1 snmp acl/*,*,1 storage
The display format on an 80-character width screen is as follows:
Vr/1 Snmp Acl/*
+======+=======+=========+-------+-------------------------
|target|subject|resources|storage|Response
+======+=======+=========+-------+-------------------------
| 1| 2| 1|nonVol |
| 2| 1| 1|nonVol |
ok
lock
The lock command is used to turn off a component so that it is no longer in
use operationally.
Operator commands 83
Passport Operations and Maintenance Guide 4S3
For more information on the lock command and its affect on different
components, see Component control on page 407.
Syntax
lock [-f] <component_name>
Impact
Service
Options
The syntax of the lock command when applied to a trunk component includes
an additional option. The syntax is as follows:
lock [-force] [-forever] trunk/<n>
See "Controlling the trunks" on page 417 for a description of the -forever
option.
Examples
Here are some examples of typical command usage.
Locking a component (for example, FrameRelayUni).
lock FrUni/<n>
where:
<n> is the instance value of the FrUni component
unlock
The unlock command is used to change the operational use of a component.
It is typically used after the lock command. After the unlock command has
been issued, the component may provide service.
Table 8
Options for the lock command
Option Abbreviation Description
-force -f Used to immediately prevent (or stop)
the use of a component operationally.
84 Chapter 3
241-7001-150 4S3
Note: If you attempt to unlock a component that is already in the shutting
down state, a message may appear indicating that a shutting down is in
progress and you cannot unlock the component.
Syntax
unlock <component_name>
Impact
Service
Options
There are no options for this command.
Examples
Here are some examples of typical command usage.
Unlocking a component (for example, FileSystem).
unlock fs
Attempting to unlock a FileSystem component in the shutting down state.
unlock fs
A message appears indicating that the command has failed because the
component is in a shutting down state.
85
Passport Operations and Maintenance Guide 4S3
Chapter 4
Provisioning system description
This chapter describes the file system and command syntax for the Passport
provisioning system. Examples of typical provisioning processes and
sessions are provided in Provisioning processes on page 137.
Except where noted, descriptions and procedures are provided for operators
working with Passport through a VT-100 terminal or a terminal emulator. For
information on using Nortels proprietary Magellan Network Management
System (NMS), see 241-6001-023, NMS Architect for Passport User Guide.
Related documents
See the following documents for additional information related to
provisioning and provisioning fundamentals:
241-7001-130, Passport Startup Guide
241-7501-210, Passport Components
Passport provisioning views
The provisioned and operational parameters on a Passport node are a set of
data entries. A set of data entries that defines both a nodes capabilities
(access services, for example) and the specific characteristics of its
performance is called a view.
Passport has four types of views:
current view: This view contains the set of provisioned and operational
data that denes the current conguration of the Passport node.
86 Chapter 4
241-7001-150 4S3
edit view: This view is the set of provisioned data to which data can be
changed or appended. It is used for controlled modications to the
current view. Once an edit view is complete, it can be activated as a
current view.
saved view: These views are copies of either the current view or the edit
view. Saved views are stored on the control processor (CP) disk.
committed view: This is a saved view in the system; it is the rollback
point to which the node returns upon reset, restart, or switchover.
The current and edit views are held in memory; the saved and committed
views are stored on disk on the CP. The basic relationship between views is
shown in Passport views on page 87. These relationships are described
further in "Overview of provisioning system commands" on page 98.
Current view
The provisioning system is designed so that changes are not made directly to
the current view. The only actions permitted on the current view are:
storing it as a saved view on disk
committing it as the default view
The only way to change the current view is to overwrite it with either the edit
view or a saved view. If an edit view is activated but not committed, the node
initiates a reset, restart, or switchover based on the last committed view.
Provisioning system description 87
Passport Operations and Maintenance Guide 4S3
Figure 7
Passport views
Edit view
The edit view is key to making changes or additions to the provisioned
parameters of a Passport node. To work in the edit view, you must start a
provisioning session. In the edit view, the following actions are permitted:
load provisioning data from a saved view into the edit view
apply changes that are stored in a saved view to the edit view
delete non-permanent provisioning data from the edit view
copy provisioning data from the current view into the edit view
Passport node
Current
Edit view
Memory
AB.full.110
AB.full.111
AB.full.112
Disk

Committed view
view
88 Chapter 4
241-7001-150 4S3
complete a semantic check of the edit view
save the provisioning data in the edit view to a saved view
activate the view to make the edit view the current view (overwrite the
current view)
These activities are achieved through a set of provisioning commands that are
collectively referred to as Passport provisioning system commands.
Saved views
Both the current view and the edit view can be saved to disk. However, unlike
the current and edit view, of which there is one of each, there can be multiple
saved views. The number of saved views is limited only by the capacity of the
CPs disk.
An edit view can be saved so that it can be reopened and changed at a later
date. Saving an edit view is useful during on-going planning for a service
upgrade or expansion, or whenever a nodes performance requires fine-
tuning. In this sense, an edit view represents on-going work-in-progress.
Full saved views
A saved view can be either full or partial, which are selected using the options
for the save prov command.
A full view includes all configuration data from either an edit or a current
view. It is ready to be loaded into the edit view, where it can be semantically
checked and activated as the current view. A full saved view can also be
directly activated as the current view, provided that the full view has
undergone a complete semantic check. If the full saved view was not checked
before saving, a full semantic check must be completed after loading it into
the edit view and before activating.
Partial saved views
A partial view is a subset of an edit view, and contains complete provisioning
data for a single component, including its subcomponents and all associated
attributes. Its configuration data can be loaded into the edit view to either
change the provisioning for an existing component or to add a component to
the edit view configuration. Once incorporated into the edit view, the
Provisioning system description 89
Passport Operations and Maintenance Guide 4S3
component can then be semantically checked. Partial views are useful for
saving component hierarchies that can be used on other Passport nodes in a
network. A partial view cannot be activated.
Saved view formats
Saved views are stored in one of several formats. The format is determined
by the options included in the save prov command or, in the case of the
committed view, by the commit prov command. Formats are described in
Format of saved views on page 89.
Table 9
Format of saved views
Saved view
format
Associated
view
Contents and characteristics Storage format
portable Current or
edit views
Includes all configuration data.
A portable saved view can be moved from
one Passport node to another, on which it
can be loaded into the edit view and further
modified to suite that nodes environment.
Passport internal
ASCII Current or
edit views
Includes all configuration data.
ASCII types can be used in non-Passport
tools and for generating configuration
printouts.
ASCII
commit Committed
view
Includes all configuration data in the
committed view.
This type is a specialized version of a
current view; it is in a Passport-internal
format that enables fast activation.
Passport internal
(Sheet 1 of 2)
90 Chapter 4
241-7001-150 4S3
delta Edit view Includes the changes made between the
current view and the edit view. It is,
therefore, much smaller and faster to Load
or Save than the other formats. A view
containing this format can be loaded or have
the changes applied to the edit view. This
provides a mechanism to propagate a set of
changes from one view to another. A view
containing only this format can be activated
if this would not require a system reload. To
generate this format, issue Save Prov
without the -component, -ascii or -portable
options.
Delta types can also be applied to any edit
view.
Passport internal
part (partial) Current or
edit views
Includes all information about a component
including all sub-components and
associated attributes.
As with ASCII types, part types can be used
in non-Passport tools for generating
configuration printouts.
ASCII
downgrade Current or
edit view
Includes all configuration data in an ASCII
format that can be read by all versions of
Passport.
Although the format can be read, the
components and attributes stored in it may
not be recognized by all versions of
Passport.
ASCII
Pre-4.X
provisioning
files
Current and
edit view
Includes all information about the Passport
configuration.
Passport internal
Note: Pre-4.X provisioning les can be converted to portable or ASCII format (depending on the
view type) if loaded into the edit view on the current release.
Table 9 (continued)
Format of saved views
Saved view
format
Associated
view
Contents and characteristics Storage format
(Sheet 2 of 2)
Provisioning system description 91
Passport Operations and Maintenance Guide 4S3
Saved view naming conventions
Saved views are stored in files or sub-directories that are identified with the
following three-part naming convention:
<name>.<type>.<number>
Each part of the lename is derived as follows:
<name>: supplied by the operator as the primary lename; it must be
between 1 and 31 characters long may contain only alphanumeric
characters and underscores. This part of the lename is case-sensitive,
and cannot be the words edit or current.
<type>: set by the system as either full or part.
<number>: set by the system as a three-digit number that identies the
sequence of views as changes are made through the edit view; the
number is incremented by 1 each time a saved view is created. For new
lenames, the number is always 001.
The following behaviors occur when partial lenames are used in
provisioning system command lines:
if number is omitted from the option value, the most recent view (with
the highest number) beginning with name.type is used
if both type and number are omitted from the option value, the most
recent (complete) view beginning with name.full is used. In otherwords,
if you only have partial lenames, use the partial lename with the
highest number, and if you have partial and full lenames, use the full
lename with the highest number.
Saved view directory and le structures
Saved views are stored in subdirectories and les on disk in the Passport
provisioning directory. The provisioning system assigns a unique lename to
each sub-directory. Under each sub-directory, les under some or all of the
following le names may be found:
portable
ascii
lp0, lp1, lp2, and so on up to lp15 (the committed view les)
92 Chapter 4
241-7001-150 4S3
delta
view (a Passport internal system le)
Committed view
A committed view is a saved view version of a current view, but with special
characteristics:
A committed views purpose is to provide a rollback point to which the
node returns upon reset, restart, or switchover.
A committed view is stored in a Passport internal format that efciently
serves the requirements of a CP reset, restart, or switchover functions.
In some instances, a committed view may not be identical to the current view
that is in memory at any given time. When an edit view is activated as the
current view, the current view and the committed view are different. The
current view contains newly updated configuration data, while the committed
view contains configuration data based on a previous current view.
CAUTION
Risk of damaging conguration data
Because the Passport provisioning system looks for
saved views according to specic lename formats and
le relationships, moving or renaming directories and
les through the Passport leSystem commands (or
through a non-Passport utility or application) may
destroy the integrity of the database. Affected views
cannot be recovered unless they have been backed up to
NMS or an equivalent system. Use the tidy prov
command to remove views. Use list prov view/* in
operational mode to list saved views.
If directories or les must be modied through a non-
Passport utility or application, changes should be made
on copies that have been moved off the Passport disks.
Provisioning system description 93
Passport Operations and Maintenance Guide 4S3
Only when the current view is committed are the two views identical. The
following conditions must be met before the current view can be committed:
if the current view is not saved, then a view lename must be entered on
the command line when the commit is requested
in a dual-CP node, disks must be synchronized
Saved view development: example
The sequence of actions in Example of saved view development on page 93
illustrates how views are stored on disk. The table shows the following
information:
Note: The following table represents a typical scenario. Depending on
the circumstance, the user may have slightly different results.
a step number, which shows the sequential order in which the operations
are completed
a description of the operation, with notes if required; this column does
not show the command syntax used to complete the operation
the lename for the edit view, as a result of the operation
the lename for the current view, as a result of the operation
the lename for all saved views on disk, including the formats associated
with each lename
Table 10
Example of saved view development
Step Action Filename of the
edit view
Filename of the
current view
Filename (s) of saved
view (s) and their
formats
1 Initial State - current and
edit views are identical
today.full.001 today.full.001 today.full.001
- commit
- portable
2 Make changes unnamed today.full.001 today.full.001
- commit
- portable
(Sheet 1 of 6)
94 Chapter 4
241-7001-150 4S3
3 Save the edit view today.full.002 today.full.001 today.full.001
- commit
- portable
today.full.002
- delta
4 Make changes unnamed today.full.001 today.full.001
- commit
- portable
today.full.002
- delta
5 Save the edit view today.full.003 today.full.001 today.full.001
- commit
- portable
today.full.002
- delta
today.full.003
- delta
6 Check, activate, and
confirm the edit view,
and commit the current
view
today.full.003 today.full.004 today.full.001
- commit
- portable
today.full.002
- delta
today.full.003
- delta
today.full.004
- commit
- portable
Table 10 (continued)
Example of saved view development
Step Action Filename of the
edit view
Filename of the
current view
Filename (s) of saved
view (s) and their
formats
(Sheet 2 of 6)
Provisioning system description 95
Passport Operations and Maintenance Guide 4S3
7 Clear the edit view and
copy the current view
into the edit view
today.full.004 today.full.004 today.full.001
- commit
- portable
today.full.002
- delta
today.full.003
- delta
today.full.004
- commit
- portable
8 Save a component today.full.004 today.full.004 today.full.001
- commit
- portable
today.full.002
- delta
today.full.003
- delta
today.full.004
- commit
- portable
today.part.001
- part
Table 10 (continued)
Example of saved view development
Step Action Filename of the
edit view
Filename of the
current view
Filename (s) of saved
view (s) and their
formats
(Sheet 3 of 6)
96 Chapter 4
241-7001-150 4S3
9 Make changes unnamed today.full.004 today.full.001
- commit
- portable
today.full.002
- delta
today.full.003
- delta
today.full.004
- commit
- portable
today.part.001
- part
10 Save the edit view today.full.005 today.full.004 today.full.001
- commit
- portable
today.full.002
- delta
today.full.003
- delta
today.full.004
- commit
- portable
today.part.001
- part
today.full.005
- delta
Table 10 (continued)
Example of saved view development
Step Action Filename of the
edit view
Filename of the
current view
Filename (s) of saved
view (s) and their
formats
(Sheet 4 of 6)
Provisioning system description 97
Passport Operations and Maintenance Guide 4S3
11 Save the edit view in
ASCII format
today.full.005 today.full.004 today.full.001
- commit
- portable
today.full.002
- delta
today.full.003
- delta
today.full.004
- commit
- portable
today.part.001
- part
today.full.005
- delta
- ascii
Table 10 (continued)
Example of saved view development
Step Action Filename of the
edit view
Filename of the
current view
Filename (s) of saved
view (s) and their
formats
(Sheet 5 of 6)
98 Chapter 4
241-7001-150 4S3
Overview of provisioning system commands
Provisioning system commands provide the functionality required to
manipulate whole views (current view or edit view) or to provision specific
components. To quickly find a command, see Quick reference to
Provisioning system commands on page 99.
Detailed command descriptions begin on Detailed command descriptions
on page 102 of this chapter.
12 Check, activate, and
confirm the edit view,
and commit the current
view
today.full.005 today.full.005 today.full.001
- commit
- portable
today.full.002
- delta
today.full.003
- delta
today.full.004
- commit
- portable
today.part.001
- part
today.full.005
- delta
- ascii
- commit
- portable
Table 10 (continued)
Example of saved view development
Step Action Filename of the
edit view
Filename of the
current view
Filename (s) of saved
view (s) and their
formats
(Sheet 6 of 6)
Provisioning system description 99
Passport Operations and Maintenance Guide 4S3
Table 11
Quick reference to Provisioning system commands
Command Description Mode(s) Page
activate prov Activates (brings into service) the provisioning data
changes in the edit view or from a specified saved
view.
Provisioning
or
operational
"activate
prov" on
page 103
apply prov Applies a previously-stored set of changes to the
edit view.
Provisioning "apply prov"
on page 106
check prov Checks the provisioning data in the edit view to
ensure that it is semantically correct. This command
must be used prior to the activate prov command.
Provisioning "check prov"
on page 108
clear prov When used with no options, removes all non-
permanent components (and their subcomponents)
from the edit view. Components (and their
subcomponents) that cannot be deleted are not
affected.
Provisioning "clear prov"
on page 113
commit prov Makes the current view of the provisioning data the
committed view. The committed view is the
configuration that the node activates following a CP
restart, reset, or switchover.
Provisioning
or
operational
"commit
prov" on
page 115
confirm prov Use to confirm the last activate prov command. A
confirm prov command must be issued following
each activate prov command. This ensures that
management connectivity will not be lost when a
new provisioning view is brought into service.
If the operator cannot confirm, then the node resets
after 20 min, using the last committed view.
Provisioning
or
operational
"confirm
prov" on
page 117
copy prov Copies all or part of a current or edit view. Provisioning "copy prov"
on page 119
end prov Exits provisioning mode. Provisioning "end prov" on
page 122
load prov Loads a saved view into the edit view. Provisioning "load prov"
on page 122
save prov Stores all or part of either the edit view or the current
view in a saved view.
Provisioning "save prov"
on page 124
(Sheet 1 of 2)
100 Chapter 4
241-7001-150 4S3
The relationship between commands and Passport views is illustrated in
Relationship between provisioning views and commands on page 101.
start prov Enters provisioning mode. Only one operator
session can be in provisioning mode at a given time.
A start prov command is normally rejected if another
session is in provisioning mode.
Operational "start prov"
on page 127
stop prov Stops execution of these long-running provisioning
commands: apply prov, check prov, load prov, and
save prov.
Provisioning "stop prov"
on page 129
tidy prov Deletes saved views. Provisioning
or
Operational
"tidy prov" on
page 130
Table 11 (continued)
Quick reference to Provisioning system commands
Command Description Mode(s) Page
(Sheet 2 of 2)
Provisioning system description 101
Passport Operations and Maintenance Guide 4S3
Figure 8
Relationship between provisioning views and commands
Edit Current
View view
Saved
view formats
load
save
activate and
conrm
check
clear
tidy
copy
portable
commit
delta
commit
ASCII
part
copy
save
switchover, reset
rollback, restart
apply
activate and
conrm
switchover, reset
rollback, restart
102 Chapter 4
241-7001-150 4S3
Other commands used in provisioning mode
Some common commands other than provisioning system commands can be
used in provisioning mode. These commands include
add (see add (a) on page 70)
delete (see delete (del) on page 71)
display (see display (d) on page 74)
list (see list (l) on page 72)
set (see set (s) on page 68)
help (see help (h) on page 65)
Provisioning commands and scope and impact
Most provisioning commands require an impact of conguration (or higher)
and a scope of application. However, the activate prov, conrm prov, and
commit prov commands can be used by a user with an impact of service.
The reloadcp command
An alternative to the start prov, load prov, check prov, and activate prov,
sequence is the reloadcp command. The reloadcp command forces a CP to
reload using a specied saved view. Once the CP has reloaded, some or all
function processors are reloaded. For information of how to use the reloadcp
command, see "Resetting, reloading, and restarting a processor card" on page
605.
Detailed command descriptions
Each detailed description includes the following information:
Description: functional description.
Syntax: structure of the command line, including options and option
values.
Impact: operator capability required to use a command.
Options: scope and impact of options.
Examples: practical examples illustrate typical command usage.
Provisioning system description 103
Passport Operations and Maintenance Guide 4S3
activate prov
Use the activate prov command to bring into service either the edit view or a
saved view.
Operators should always complete a semantic check of the edit view (using
the check prov command) before issuing the activate prov command. If a
semantic check has not been completed for the view, Passport automatically
starts the check before the activate process begins.
When an unchecked provisioning view is activated, the provisioning system
runs a semantic check. If there are semantic problems with the view, the
system issues errors and warnings. Some warnings issued by the semantic
checker are considered critical (for example, a service may have to be
restarted to activate the specified provisioning data change, or a complete
system restart may be required). If a semantic check error or critical warning
occurs, then the activate command is aborted. For critical warnings, this
behavior can be overridden by using the -force option.
When a provisioning view is activated, the provisioning system checks to
ensure that all the software necessary to activate the components in the view
is currently running on the module. If any necessary software is missing, the
command fails and a list of missing software is displayed.
After the activate prov command is complete, the operator must issue a
confirm prov command within 20 minutes to prevent automatic re-activation
of the committed view. Note that the committed view is not necessarily the
same as the view which was in effect prior to the activation.
Activating a view may delete certain components in the current view. Some
components temporarily go out of service if the nature of the changes are
critical to the provisioned data.
An activation may also result in a CP restart or reload causing all services on
the Passport node to fail. When this happens, the user must wait until the
restart or reload is complete and then continue with the confirm prov
command. If an activation results in a CP reset or reload, and the edit view is
not saved, it is automatically put into a temporary saved view.
104 Chapter 4
241-7001-150 4S3
Syntax
activate [-file(<filename>)] [-force] prov
Impact
Configuration (to activate the edit view)
Service (to activate a saved view)
Options
Using activate prov with no options copies the edit view into the current view.
Table 12
Options for the activate prov command
Option Abbreviation Description
-file
(<filename>)
shortest
unambiguous
match
Use this option to activate a saved view.
If the command is issued in operational
mode, the activate prov command can only
be used with the -file option and therefore
can activate only a saved view and not the
edit view. The activate prov command
cannot be used with the -file option if
another operator session is in provisioning
mode.
The <filename> option value identifies the
saved view using the three-part view
filename. See Saved view naming
conventions on page 91 for behavior
characteristics in the command line.
-force shortest
unambiguous
match
The -force option overrides the check for
required software, and loads and activates
by reloading the module with the view.
The -force option also overrides critical
warnings and continued to activate the
view.
Note: Semantic check errors cannot be
overridden.
Provisioning system description 105
Passport Operations and Maintenance Guide 4S3
Examples
The following procedures illustrate typical command line usage.
Procedure 1
Activating the edit view
1 From within a provisioning session, issue the activate prov command with
no options:
activate prov
An alarm appears, followed by a message. The alarm warns all operators
on the node that an unconrmed activation has occurred. The message
prompts the operator to conrm the activation by issuing the conrm prov
command.
Prov; 1996-11-20 07:54:14.92
SET warning operator operationalCondition 70000007
ADMIN: unlocked OPER: enabled USAGE: busy
AVAIL: PROC: reporting CNTRL:
ALARM: STBY: notSet UNKNW: false
Id: 0F000026 Rel: Lp/0
Com: Activation complete.
Enter 'confirm prov' to confirm activation or
rollback will occur in 20 minutes.
Int: 15/1/3/39955; casCPmainEntry.cc;470;p4.0d.26
Prov
You have 20 minutes in which to confirm activation.
ok
Procedure 2
Activating a saved view
1 In operational mode, issue the activate prov command with the -le
option:
activate -file(DZL_test.full.023) prov
An alarm appears, followed by a message. The alarm warns all operators
on the node that an unconrmed activation has occurred. The message
prompts the operator to conrm the activation by issuing the conrm prov
command.
Prov
Invoking Load prov command.
Prov; 1996-11-20 08:09:20.87
SET warning operator operationalCondition 70000007
.
. <text deleted>
.
106 Chapter 4
241-7001-150 4S3
Int: 15/1/3/39955; casCPmainEntry.cc;470; p4.0d.26
Loaded file DZL_test.full.023.
You have 20 minutes in which to confirm activation.
ok
apply prov
Use the apply prov command to apply the changes in a saved view to the edit
view. Only saved views with a delta format can be used with this command.
The apply prov command can be issued only if either the edit view has been
saved or the edit view is identical to the current view.
When a provisioning view is applied using this command, the provisioning
system checks to ensure that all the software necessary to activate the
components in the view is currently running on the module. If any necessary
software is missing, the command fails and a list of missing software is
displayed.
If the information in the saved view differs from the edit view, then the edit
view prevails and warning messages are displayed. Operators must note
conflicts and resolve as necessary.
Syntax
apply -file(<filename>) [-force] prov
Impact
Configuration
Options
The apply prov command must always include the -file option.
Provisioning system description 107
Passport Operations and Maintenance Guide 4S3
Example
The following procedure illustrates typical command line usage.
Procedure 3
Applying a saved view (delta format)
1 From within a provisioning session, issue the apply prov command, using
the mandatory -le option.
apply -file(AXL_test.full.004) prov
The saved changes are applied from the saved view to the edit view, and
conicts are resolved or reported.
Prov
Loaded or applied file AXL_test.full.004.
ok
Related commands
See also load prov on page 122 and stop prov on page 129.
Table 13
Options for the apply prov command
Option Abbreviation Description
-file
(<filename>)
shortest
unambiguous
match
This is a mandatory option.
The <filename> option value identifies the
saved view using the three-part view
filename. See Saved view naming
conventions on page 91 for behavior
characteristics in the command line.
-force shortest
unambiguous
match
The -force option overrides the check for
required software, and applies the saved
view regardless of the software running on
the node.
The -force option also ensures that the
provisioning system continues to process
the entire view rather than stopping after 5
semantic errors are encountered.
108 Chapter 4
241-7001-150 4S3
check prov
Use the check prov command to ensure that the provisioning data in the edit
view is semantically correct. Use this command before the activate prov
command. All errors must be corrected before the activate prov can be
successfully completed.
Note: If you have changed a Software, LogicalProcessor,
LogicalProcessorType, or Card component, you cannot run the check
prov command while a start sw dld, tidy sw, or a remove sw command is
in progress.
During a full semantic check, the system issues a warning for each
component that will go out of service because of critical provisioning data
changes. When the edit view is activated, these components go out of service
and then return to service after the activate is complete. See "activate prov"
on page 103 for more information on view activation.
Syntax
check [-stopOnError] [[-component (<name>)
[-nonrecursive]] [-changed] prov
Impact
Configuration
Options
When check prov is used with no options, the system undertakes a full
semantic check of the edit view.
Provisioning system description 109
Passport Operations and Maintenance Guide 4S3
Table 14
Options for the check prov command
Options Abbreviation Description
-changed shortest
unambiguous
match
Limits the semantic check to only those
components that are in the edit view and
are new or changed from the current view.
This option cannot be used if the
-component option is used.
Note: This option is useful in accelerating
the semantic check. However, to activate
the edit view, a successful full semantic
check must be completed.
-component
(<component_
name>)
shortest
unambiguous
match
Requests a semantic check of the
indicated component and its
subcomponents. This option starts a fully
recursive check of the component, its
associated subcomponents, and all
associated attributes. Out of service
warnings are not issued.
This option cannot be used if the -changed
option is used.
Note: This option is useful where only a
single component is affected by changes
made in a provisioning session. The result
is a greatly accelerated semantic check.
However, to activate the edit view, a
successful full semantic check must be
completed.
(Sheet 1 of 2)
110 Chapter 4
241-7001-150 4S3
Examples
The following procedures illustrate typical command line usage.
Procedure 4
Successful check prov command with no options
1 Start a semantic check with no options:
check prov
A warning appears to indicate which components will be taken out of
service as a result of the change. For example, after a critical change to
-nonrecursive shortest
unambiguous
match
Limits a semantic check to a single
component; that is, subcomponents and
their associated attributes are not
checked.
This option must be used with the
-component option.
Note: This option is useful where only the
top layer of a single component is affected
by changes made in a provisioning
session. The result is still greater
acceleration of the semantic check.
However, to activate the edit view, a
successful full semantic check of all
components must be completed.
-stopOnError shortest
unambiguous
match
Stops the check when the first semantic
error is found.
If this option is not used, the provisioning
system attempts to find as many errors as
possible (maximum of five errors).
Table 14 (continued)
Options for the check prov command
Options Abbreviation Description
(Sheet 2 of 2)
Provisioning system description 111
Passport Operations and Maintenance Guide 4S3
the FrameRelayUni/2 component, the following might appear after
issuing the check prov command:
Prov
Warning: The following components will be taken out
of service:
FrUni/2
The following procedure illustrates how the check prov command works
when semantically incorrect provisioning is introduced. Adding an ATM
interface is used as the example.
Procedure 5
Example of successful and unsuccessful check prov commands
1 Start a provisioning session.
start prov
The response is:
Prov
The edit view is identical to the current view.
ok
2 Add an ATM interface.
add atmif/21
The response is:
AtmIf/21
The following components have been created:
AtmIf/21 ConnMap
AtmIf/21 CA
AtmIf/21
ok
3 Set connection map attributes to values that exceed acceptable ranges.
set atmif/21 connmap numNonZeroVpisForVccs 16; set
atmif/21 connmap numVccsPerNonZeroVpi 2048
Note: These values are within the ranges dened for each attribute.
The response is:
AtmIf/21 ConnMap
ok
112 Chapter 4
241-7001-150 4S3
4 Complete a non-recursive semantic check of the AtmIf/21 component.
check -component(atmif/21) -nonrecursive prov
The response is:
Prov
ok
The check prov command is successful because the non-recursive option
limits the semantic check to the AtmIf component; the ConnectionMap
subcomponent, where the illegal values have been set, is not included in
the check.
5 For an example of check prov, a DS1 port is rst added.
add lp/2 ds1/3
The response is:
Lp/2 DS1/3
The following components have been created:
Lp/2 DS1/3 Chan/0
Lp/2 DS1/3
ok
6 Complete a semantic check of the AtmIf/21 component, including all
dependant subcomponents and attributes.
check -component(atmif/21) prov
The response is:
AtmIf/21
Error:
Reason: maxVpcs exceeds space provisioned in
connMap component
AtmIf/21 ConnMap
Error:
Reason: Too many VCCs allocated, reduce size of
Programmable VCC Space or VPI Zero Space
Prov
Semantic check failed. This view cannot be
activated.
command failed
In this check, the errors at the ConnectionMap component level are
raised, since all components are included in the check (the -nonrecursive
option is not used).
7 Complete a semantic check of all changed components.
Provisioning system description 113
Passport Operations and Maintenance Guide 4S3
check -changed prov
The response is:
AtmIf/21
Error:
Reason: maxVpcs exceeds space provisioned in
connMap component
AtmIf/21 ConnMap
Error:
Reason: Too many VCCs allocated, reduce size of
Programmable VCC Space or VPI Zero Space
Lp/2 DS1/3 Chan/0
Error:
Attribute: timeslots
Reason: Must have at least one timeslot
provisioned.
Prov
Semantic check failed. This view cannot be
activated.
command failed
Related commands
See also stop prov on page 129.
clear prov
Use the clear prov command to remove nonpermanent components (and their
subcomponents) from the edit view. Components that cannot be deleted are
not affected by this command.
Syntax
clear [-removedFeature] prov
Impact
System administration
Options
When used with no options, the clear prov command removes all non-
permanent components (and their subcomponents) from the edit view.
114 Chapter 4
241-7001-150 4S3
Examples
The following procedures illustrate typical command line usage.
Procedure 6
Clearing all non-permanent components from the edit view
1 Use the list command to display all the top-level components.
list *
The response is:
FrUni/1
Sw
Shelf
ok
2 Issue the clear prov command to delete the non-permanent components.
clear prov
3 Issue the list command again.
list *
The response is:
Sw
Shelf
ok
Table 15
Options for the clear prov command
Option Abbreviation Description
-removed
Feature
rf This option is typically used when one or
more features have been removed from
one or more LPTs. It specifies that all
components, both permanent and
nonpermanent, and which have their
associated software unloaded from the
LPs that are affected by the changed
LPTs, are to be removed from the edit
view.
Provisioning system description 115
Passport Operations and Maintenance Guide 4S3
In the following procedure, assume that frameRelayUni/1 has been removed
from the feature list.
Procedure 7
Clearing all components associated with a removed feature
1 Use the list command to display all the top-level components.
list *
The response is:
Col/*
Sw
Shelf
Lp/*
Rtg
Mod
Ac
Npi/*
FrUni/1
ok
2 Issue the clear prov command with the -removedFeature option.
clear -removedFeature prov
3 Use the list command to display all the top-level components.
list *
The response is:
Col/*
Sw
Shelf
Lp/*
Rtg
Mod
Ac
ok
commit prov
Use the commit prov command to set the current view of the provisioning data
as the committed view. This activity may entail saving the current view in
portable or commit formats. The commit prov command is used after the
activate prov and conrm prov commands have been successfully completed.
116 Chapter 4
241-7001-150 4S3
Note: When the commit prov command is issued before using the
conrm prov command, the conrmation is automatically completed.
The committed view is the conguration that the node activates following a
CP reset, restart, or switchover. The following conditions must be met before
the current view can be committed:
The current view must be stored in a saved view prior to committing it;
if not, a view lename must be entered on the command line when the
commit is requested. This ensures that the current view is stored in a
saved view with a portable format.
in a dual-CP node, disks must be synchronized
Note: In a dual-CP node, the commit prov command may cause a reload
of the standby CP.
When issued from operational mode, the commit prov command fails if
another operator session is in provisioning mode.
Syntax
commit [-file(<filename>)] prov
Impact
Service
Provisioning system description 117
Passport Operations and Maintenance Guide 4S3
Options
Examples
The following procedure illustrates typical command line usage.
Procedure 8
Committing the current view and storing in a saved view
1 Issue the commit prov command using the -le option.
commit -file(DZL_test) prov
The response is:
Prov
Saving the current view into DZL_test.full.001
with formats: commit, portable.
The committed file is DZL_test.full.001.
ok
conrm prov
The confirm prov command is issued after the activate prov command. It
serves as user confirmation to activate the edit view. After the confirmation
is complete, the current view is the same as the edit view.
Table 16
Options for the commit prov command
Option Abbreviation Description
-file
(<filename>)
shortest
unambiguous
match
This option specifies the name of the
saved view in which the current view is to
be stored.
If this option is not specified and the
current view has not been stored in a
saved view, an error message response is
generated.
The <filename> option value identifies the
saved view using the three-part view
filename. See Saved view naming
conventions on page 91 for behavior
characteristics in the command line.
118 Chapter 4
241-7001-150 4S3
If the activate command is not confirmed within the 20 min, a system restart
occurs and the committed view is reactivated by the system. Service is
disrupted while the restart is in progress, and the level of disruption depends
on the level of CP redundancy in the shelf. The confirm prov command can
be used both in and out of provisioning mode.
When issued from operational mode, the confirm prov command fails if
another operator session is in provisioning mode.
Syntax
confirm prov
Impact
Service
Options
There are no options for this command.
Examples
The following procedures illustrate typical command line usage.
Procedure 9
Successfully conrming the activation
1 Activate the edit view.
activate prov
The response is:
Prov
Invoking Activate prov command.
Prov; 1996-11-20 14:08:20.04
SET warning operator operationalCondition 70000007
ADMIN: unlocked OPER: enabled USAGE: busy
AVAIL: PROC: reporting CNTRL:
ALARM: STBY: notSet UNKNW: false
Id: 0F000020 Rel: Lp/0
Com: Activation complete.
Enter 'confirm prov' to confirm activation or
rollback will occur in 20 minutes.
Int: 15/1/3/63507; casCPmainEntry.cc;447; p4.0d.27
You have 20 minutes in which to confirm activation.
ok
Provisioning system description 119
Passport Operations and Maintenance Guide 4S3
In this example, the activate prov command is issued before a check prov
was invoked. The command therefore starts a semantic check before the
activation.
2 Issue the conrm prov command.
confirm prov
The response is:
Prov; 1996-11-20 14:10:47.49
CLR cleared operator operationalCondition 70000007
ADMIN: unlocked OPER: enabled USAGE: busy
AVAIL: PROC: reporting CNTRL:
ALARM: STBY: notSet UNKNW: false
Id: 0F000021 Rel: Lp/0
Com: Activation confirmed. Rollback will not occur.
Int: 15/1/3/63783;
casResolverVerbProvConfirm.cc;171; p4.0d.27
Prov
ok
Procedure 10
Attempting to conrm before successful view activation
Issue the conrm prov command.
PROV 99> confirm prov
A message appears indicating that the command has failed because there
is no unconrmed activation.
Prov
You must activate the edit view first, then confirm.
command failed
copy prov
Use the copy prov command to copy components from the current view into
the edit view, or to copy components within the edit view alone. The
following characteristics inherent in the copy prov command:
If the command is used to copy a full view, all components are copied
and no restrictions apply.
If the command is used to copy a component or partial view (edit view
to edit view or current view to edit view), the system may change data so
that it does not conict with existing data (for example, DNAs,
120 Chapter 4
241-7001-150 4S3
passwords, and all link attributes). In situations where the system does
change data, a warning appears on the text interface device to specify that
the values have been modied.
Syntax
copy [-source(<component_name>) [-current]
[-nonrecursive] [-destination(<component_name>)]] prov
Impact
The impact depends on the add impact of the component.
Options
The default source view depends on the options specied:
If no options are used, the default source view is the current view, and the
complete view is copied.
If the -source option only is used, the default source view is the current
view.
If both the -source and the -destination options are used, the default
source view is the edit view. However, the -current option can used to
change the default source view to the current view.
Table 17
Options for the copy prov command
Option Abbreviation Description
-current shortest
unambiguous
match
Requests that the source view is the
current view.
This option is used to change the default
source view when copying a component. It
is valid only if the -source and -destination
options are used.
-destination
(<component_
name>)
shortest
unambiguous
match
Renames the copied component to the
filename specified in the option value.
This option is valid only if the -source
option is used.
(Sheet 1 of 2)
Provisioning system description 121
Passport Operations and Maintenance Guide 4S3
Examples
The following example procedure copies FrameRelayUni/1 to
FrameRelayUni/2 in the edit view.
Procedure 11
Copying components within the edit view
1 Use the list command to display the components.
list FrUni/*
The response is:
FrUni/1
ok
-nonrecursive shortest
unambiguous
match
Requests that only the indicated
component is copied and not its
subcomponents.
This option is permitted only if the -source
option is used.
-source
(<component_
name>)
shortest
unambiguous
match
Copies the identified component from
either the edit view or the current view. The
following behaviors occur:
if only the -source option is used, the
current view is the source view
if the -destination option is used, the
edit view is the source view
if the -destination and -current options
are used, the current view is the source
view.
If there are any conflicts between
component names in the edit view, then
the copy fails and no changes are applied
to the edit view.
Table 17 (continued)
Options for the copy prov command
Option Abbreviation Description
(Sheet 2 of 2)
122 Chapter 4
241-7001-150 4S3
2 Use the copy prov command to copy the FrUni/1 component from the edit
view to a new component under a different name, also in the edit view.
copy -source(FriUni/1) -destination(FriUni/2) prov
3 Issue the list command again to verify that the copy occurred.
list FrUni/*
The response is:
FrUni/1
FrUni/2
ok
end prov
Use the end prov command to exit provisioning mode. After exiting
provisioning mode, the system prompt changes from PROV> to > .
Syntax
end prov
Impact
Configuration
Options
There are no options for this command.
Examples
The following procedures illustrate typical command line usage.
Procedure 12
Ending provisioning mode
1 Exit provisioning mode:
end prov
The response is:
Prov
ok
load prov
Use the load prov command to load a saved view into the edit view.
Provisioning system description 123
Passport Operations and Maintenance Guide 4S3
When the load prov command its issued, it is possible that the software
required to load and activate the view is not currently running on the node. In
this case, the load command fails, and on-screen messages identify which
software modules need to be loaded. This behavior can be overridden by
using the -force option.
Syntax
load [-force] -file(<name<.type<.number>>>) prov
Impact
Configuration
Options
The load prov command must always include the -file option.
Table 18
Options for the load prov command
Option Abbreviation Description
-file
(<filename>)
shortest
unambiguous
match
This is a mandatory option.
The <filename> option value identifies the
saved view using the three-part view
filename. See Saved view naming
conventions on page 91 for behavior
characteristics in the command line.
-force shortest
unambiguous
match
The -force option overrides the check for
required software, and applies the saved
view regardless of the software running on
the node.
The -force option also ensures that the
provisioning system continues to process
the entire view rather than stopping after 5
errors.
124 Chapter 4
241-7001-150 4S3
Examples
The following procedures illustrate typical command line usage.
Procedure 13
Loading a saved view into the edit view
1 Issue the load prov command, specifying a view by only the name portion
of its lename.
load -file(AB0045) prov
The response is:
Prov
Loaded file "AB0045.full.024"
ok
Procedure 14
Loading a non-existent saved view
1 Issue the load prov command, specifying a non-existent view:
load -file(AXL_test.full.000) prov
A message appears indicating that the command has failed because the
view could not be found (000 is not used as a sequence number, therefore
the view is non-existent).
Prov
The specified file does not exist.
command failed
Related commands
See also apply prov on page 106 and stop prov on page 129.
save prov
The save prov command is used to store all or part of either a current view or
an edit view in a saved view.
Syntax
save [-file(<filename>)] [-component(<component_name>)]
[-portable] [-ascii] [-current] [-downgrade] prov
Impact
Configuration
Provisioning system description 125
Passport Operations and Maintenance Guide 4S3
Options
When no options are used, the edit view is stored in a saved view against the
last loaded, saved, or committed view name and the number is incremented
by 1.
Table 19
Options for the save prov command
Option Abbreviation Description
-ascii shortest
unambiguous
match
Stores the view in ASCII format.
Use this format to export the view to a non-
Passport application.
-component
(<component_
name>)
shortest
unambiguous
match
Stores the specified component and its
subcomponent hierarchy in a saved view
of type part.
Note: The -le(<lename>) option must
be used with this option. The links to other
components are not saved in this case.
-current shortest
unambiguous
match
Stores the current view in a saved view of
portable format.
Note: If this option is not used, the edit
view is saved.
-file
(<name>)
shortest
unambiguous
match
The <name> option value identifies the
saved view using only the name portion of
the three-part filename. The Passport
system supplies the type and number.
If the name is entered is an existing name,
the view is saved under that name and its
number is incremented by 1.
If the name is entered is a new name (that
is, not on disk), the view is saved under the
new name and its number is reset to 001.
(Sheet 1 of 2)
126 Chapter 4
241-7001-150 4S3
Examples
The following procedures illustrate typical command line usage.
Procedure 15
Storing a component in a partial saved view
1 Issue the save prov command using the -le and -component options.
save -file(AXL_test) -component(FrUni/1) prov
A message appears indicating that the data has been saved.
Prov
Saving the edit view into AXL_test.part.001 with
formats: part.
The provisioning data is saved in file
AXL_test.part.001.
ok
Procedure 16
Storing the current view in ASCII format
1 Issue the save prov command using the -ascii, -le, and -current options.
save -ascii -file(TEL_test) -current prov
The response is:
Prov
Saving the current view into TEL_test.full.001 with
formats: ascii.
ok
-portable shortest
unambiguous
match
Stores the view in a saved view of portable
format.
Use this option to create a view that can be
reused on another Passport node.
-downgrade shortest
unambiguous
match
Stores the view in a saved view with a
format that is compatible with previous
software versions.
You cannot use this option in combination
with the -ascii or -portable options.
Table 19 (continued)
Options for the save prov command
Option Abbreviation Description
(Sheet 2 of 2)
Provisioning system description 127
Passport Operations and Maintenance Guide 4S3
ASCII format is useful for exporting provisioning views in a format
compatible with the NMS Architect for Passports Global Data Manager
(GDM).
Related commands
See also stop prov on page 129.
start prov
Use the start prov command to enter provisioning mode.
Only one operator can be in provisioning mode at any given time for a
particular node (two or more operators can be logged into the node to examine
the current view). When entering provisioning mode, the system prompt
changes from > to PROV> .
After a start prov, the system responds with one of two possible responses to
indicate to the user whether the edit view is equal to the current view. These
responses are:
Prov
The edit view is identical to the current view.
ok
or
Prov
The edit view differs from the current view.
Changed xx provisioning attribute(s) in the edit view.
ok
Syntax
start [-force] prov
Impact
Configuration
128 Chapter 4
241-7001-150 4S3
Options
Example
The following procedure illustrates typical command line usage.
Procedure 17
Successfully entering provisioning mode
1 Issue the start prov command without options.
start prov
An example response is:
Prov
The edit view is identical to the current view.
ok
Table 20
Options for the start prov command
Option Abbreviation Description
-force shortest
unambiguous
match
Used by the system administrator to enter
a provisioning session currently in use by
another operator.
This option forces the other operator out,
and the system administrator who issued
the command takes over the session
initiated by that operator. The contents of
the edit view are preserved, and any
outstanding commands issued by the
previous operator run to completion (that
is, in progress commands are not aborted).
The system generates an alarm to inform
the other operator that he or she has been
forced out.
Provisioning system description 129
Passport Operations and Maintenance Guide 4S3
Procedure 18
Successfully entering provisioning mode
1 Issue the start prov command with the -force option.
start -force prov
An example response is:
Prov; 1996-11-20 17:09:41.25
MSG warning operator operationalCondition 70000012
ADMIN: unlocked OPER: enabled USAGE: busy
AVAIL: PROC: reporting CNTRL:
ALARM: STBY: notSet UNKNW: false
Id: 0F000022 Rel:
Com: The provisioning operator has been forced off by the
System Administrator.
Int: 15/1/3/63507; casResolverVerbProvStart.cc;195;
p4.0d.27
Prov
The edit view is identical to the current view.
ok
stop prov
The stop prov command is used whenever a long-running command must be
aborted. Use this command to stop any of the following provisioning
commands that may be in progress:
apply prov
check prov
load prov
save prov
The in-progress command may still take a few seconds to terminate.
Syntax
stop prov
Impact
Configuration
Options
There are no options for this command.
130 Chapter 4
241-7001-150 4S3
Example
The following procedure illustrates typical command line usage.
Procedure 19
Stopping a long-running provisioning system command
1 Issue the stop prov command.
stop prov
The response is:
Prov
ok
Note: The in-progress command response is:
-command cancelled
The activityProgress attribute indicates that the current provisioning
activity will be stopped as soon as possible.
tidy prov
Use the tidy prov command to remove saved views from the system disk. Use
this command both in and out of provisioning mode. When the system
encounters a file system error, it cancels the tidy prov command and provides
details on the nature of the error. The tidy prov command provides the only
supported method of removing saved views.
The following views are not removed when the tidy prov command is used,
regardless of the command options:
the committed view
the most recent complete saved view used by one of the activate prov,
commit prov, load prov, or save prov commands
the saved view containing the data in the current view
saved views that are write-protected (read-only)
les or directories that are not identied with the standard
<name>.<type>.<number> format
saved views in portable format that support dependant saved views in
delta format
Provisioning system description 131
Passport Operations and Maintenance Guide 4S3
Note: Do not tidy old views immediately after performing a software
upgrade. If problems arise as a result of the upgrade, you will need an old
view to downgrade so you can downgrade to the previous software
version.
Syntax
tidy [-all] [-keep(<filename> <filename> ...)]
[-fromDate(<date>) -toDate(<date>)]
[-remove(<filename> <filename> ...)] [-software] prov
At least one option must be specified when issuing the tidy prov command.
The -all and date options are mutually exclusive. The fromDate and toDate
options must always be used together.
Impact
Configuration
Options
none
Implicit name matching
: The -keep and -remove options support implicit name matching, based on
the saved view naming conventions described in Saved view naming
conventions on page 91. Matching works in this way:
If number is omitted from the option value, all views beginning with
name.type are kept or removed.
If both type and number are omitted from the option value, all views
beginning with name are kept or removed.
132 Chapter 4
241-7001-150 4S3
Table 21
Options for the tidy prov command
Option Abbreviation Description
-all shortest
unambiguous
match
Removes all saved views except those
views that cannot be removed by the tidy
prov command.
The -all option cannot be used with the
-fromDate and -toDate options.
-fromDate
(<date>)
-toDate
(<date>)
shortest
unambiguous
match
Removes all saved views with a date
stamp that falls within the defined range.
The date option value is in the form
YYYY-MM-DD.
If the -fromDate option is more recent than
the -toDate option, the system displays an
error response indicating that the option
values are incorrect.
(Sheet 1 of 3)
Provisioning system description 133
Passport Operations and Maintenance Guide 4S3
-keep
(<filename>)
shortest
unambiguous
match
The -keep option specifies a list of views
that will not be removed. The -keep option
takes precedence over all other tidy
options.
If the -keep option is specified by itself,
then all views will be removed except for
those views specified in the keep list.
If either the -remove or the date option is
specified with the -keep option, then only
those views that are not on the keep list
and are specified by the -remove or date
option will be removed.
This option supports implicit name
matching (see Implicit name matching on
page 131).
The <filename> option value identifies the
saved view using the three-part view
filename. Where multiple views are
specified, each filename is separated by a
space. See Saved view naming
conventions on page 91 for information on
filename format.
Table 21 (continued)
Options for the tidy prov command
Option Abbreviation Description
(Sheet 2 of 3)
134 Chapter 4
241-7001-150 4S3
Examples
The following procedures illustrate typical command line usage.
Procedure 20
Examples of tidy prov command options
1 To remove views from a specic period, issue the tidy prov command
using the -fromDate and -toDate options.
tidy -fromDate(1995-01-01) -toDate(1995-12-31) prov
2 To remove all views, issue the tidy prov command with the -all option.
tidy -all prov
3 To remove all views except for those views specied in the keep list, issue
the tidy prov command with the -keep option.
tidy -keep(AB03sn.full.067) prov
-remove
(<filename>)
-rm Removes the saved views specified in the
option value.
This option supports implicit name
matching (see Implicit name matching on
page 131).
The <filename> option value identifies the
saved view using the three-part view
filename. Where multiple views are
specified, each filename is separated by a
space. See Saved view naming
conventions on page 91 for information on
filename format.
-software shortest
unambiguous
match
This option is reserved for future use and
currently has no effect.
Table 21 (continued)
Options for the tidy prov command
Option Abbreviation Description
(Sheet 3 of 3)
Provisioning system description 135
Passport Operations and Maintenance Guide 4S3
4 To remove all provisioning views that match a specic lename, except
specied saved views (in this example, AB05sn.full.49 and
AB05sn.full.067), use the -keep and -remove options.
tidy -remove(AB05sn) -keep(AB05sn.full.049
AB05sn.full.067) prov
In this example, the last view used (AB05sn.full.069) is part of the set
dened by the -remove option. Since it is the last le, it cannot be deleted.
Therefore all of the views named AB05sn are deleted except:
AB05sn.full.069, AB05sn.full.049 and AB05sn.full.067.
5 To remove a single view, use the -remove option and specify the view
using a complete lename.
tidy -remove(AB05sn.full.049) prov
136 Chapter 4
241-7001-150 4S3
137
Passport Operations and Maintenance Guide 4S3
Chapter 5
Provisioning processes
Passport provisioning is designed as an open-ended system that can support
many office processes and procedures. This chapter describes some typical
processes and procedures for adding and modifying the provisioning data on
a node.
To illustrate the provisioning concepts described in Provisioning system
description on page 85, this chapter provides descriptions and examples of
the following processes:
displaying provisioning status
bulk provisioning
regular order processing
immediate processing
creating partial saved views of single component hierarchies
global data changes
network conguration changes
For detailed descriptions of commands and file systems, see Provisioning
system description on page 85.
Before reading this chapter, read Operator commands on page 57 for
information on entering commands through a VT-100 terminal or terminal
emulator. Except where noted, descriptions and procedures are provided for
operators working with Passport through a VT-100 terminal or terminal
138 Chapter 5
241-7001-150 4S3
emulator. For information on using Nortels proprietary Magellan Network
Management System (NMS), see 241-6001-023, NMS Architect for Passport
User Guide.
Command format and conventions
Before using the provisioning system commands, be familiar with proper
command syntax and format. See the following chapters and sections for
more information:
Provisioning system description on page 85 for a description of the
provisioning le system and command syntax
Conventions on page 41 for a description of typographic conventions
"Keyboard shortcuts" on page 53 for a list of keyboard shortcuts
All common commands use a variation of the following format:
verb [-options [(<option_value>)]]... component_name
[attribute_name| group_name]...
An option causes the command to behave in a manner different from its
default values. Options sometimes need an option value. Angled brackets
indicate an operator-supplied value. Parentheses are required as part of
syntax, as illustrated in command lines.
The following characteristics apply to the use of components when entered as
part of provisioning system command lines:
A component name consists of a component type followed by a
component instance value. For example, FrUni/5 DLCI/64 is a
component name. In the case where only one instance of a component
can exist on a Passport (for example, the Shelf component), the
component type appears by itself and is not appended by a component
instance.
The component type is the component without a particular instance
value. For example, FrUni is a type since it species a particular type of
component, but does not specify a particular FrUni instance on the node.
The component instance is the unique name (under a particular
component type) that is used to identify a particular instance of a
component class. For example, in FrUni/5, 5 is the instance.
Provisioning processes 139
Passport Operations and Maintenance Guide 4S3
The term component class is also used in some of the commands and
command examples in this chapter and in Provisioning system description
on page 85. Component class is a concatenation of component types. For
example, FrUni Dlci is a component class because it does not contain any
instance values.
Displaying provisioning status
The display and list commands can be used to
show current provisioning status
list all saved views on disk
list characteristics of a saved view
Displaying provisioning and saved view status and attributes on page 139
demonstrates how these commands are used, with an example of the results
obtained.
Procedure 21
Displaying provisioning and saved view status and attributes
1 List the saved views currently on disk.
list prov view/*
The results of the command are shown in the example output below.
Prov View/current
Prov View/edit
Prov View/BD0028B.full.001
Prov View/BD0028B.full.002
Prov View/BD0028B.full.006
Prov View/BD0030B.full.001
Prov View/BD0030B.full.002
Prov View/BD0031A_port.full.002
Prov View/BD0032C.full.001
Prov View/BD0032C.full.002
Prov View/BD0032C.full.003
Prov View/BD0032C.full.004
Prov View/BD0032C.full.005
Prov View/another_BD0031A.full.001
Prov View/historicalFormat.full.122
Prov View/initial_state.full.120
Prov View/junk2.full.001
140 Chapter 5
241-7001-150 4S3
Prov View/new_BD0031A.full.001
ok 1996-12-12 08:22:41.50
2 Display the status of the provisioning system.
display prov
The results of the command are shown in the example output below.
Prov
adminState = unlocked
operationalState = enabled
usageState = idle
provisioningActivity = none
activityProgress = n/a
committedFileName = BD0032C.full.004
currentViewFileName = BD0032C.full.004
lastUsedFileName = BD0032C.full.004
provisioningSession =
provisioningUser = none
checkRequired = yes
nextFileSequenceNumber = 1
confirmRequired = no
provisioningDirectory = /provisioning
editViewName = BD0032C.full.004
editViewAddedComponents = 0
editViewDeletedComponents = 0
editViewChangedComponents = 0
ok 1996-12-12 08:22:48.03
3 List the attributes of a single saved view.
display prov view/BD0032c.full.004
The results of the command are shown in the example output below.
Prov View/BD0032c.full.004
user = troy
checkState = full
formats = ascii port
version = BD0031A
creationDate = 1996-12-07 13:13:52
baseView = BD0031A_atmtest_dec4.full.008
components = 344
ok 1996-12-12 15:30:55.43
Provisioning processes 141
Passport Operations and Maintenance Guide 4S3
Provisioning processes
As described in Provisioning system description on page 85, the Passport
provisioning system is open-ended and can be adapted to specic
administration requirements and processes. Some typical provisioning
processes are:
bulk provisioning
regular order processing
immediate provisioning
global data changes
scheduled network conguration changes
These provisioning processes are summarized in Summary of characteristics
of provisioning operations on page 141.
Table 22
Summary of characteristics of provisioning operations
Process Planning required Time of activation
Bulk provisioning Planned in advance Immediate or delayed
Regular customer-
order processing
Daily activity Delayed and several
sets of changes are
activated in bulk
Activation of regular
customer orders
Completed at pre-
determined times,
probably daily as an
over-night process
Immediate
Immediate provisioning Unplanned Immediate
Global data changes Planned in advance Immediate
Network configuration
changes
Planned in advance Immediate
Note: In some ofces, a single person might perform all types of tasks; in
others, two or more people may share tasks.
142 Chapter 5
241-7001-150 4S3
These provisioning processes are described in detail in the following
subsections.
Bulk provisioning
Bulk provisioning involves entering a large number of changes. This process
is most often used during initial installation when the node is not carrying
traffic. The number of provisioning sessions can be either one or many, and
activation can be either immediate or delayed. When provisioning in bulk, the
operator typically uses the NMS Passport provisioning API to load the set of
provisioning changes from a saved view into the edit view.
The bulk provisioning process follows these general steps:
Start the provisioning session.
If the node conguration and operating parameters are based on another
node in the network, load a saved view into the edit view.
Make all required changes (one or more sessions).
Complete a full semantic check on the edit view, correcting all
provisioning errors found.
Store the changes in a saved view (optional).
Move the edit view to the current view by activating the edit view and
conrming.
Stored the current view in a saved view.
Commit the current view (which creates a saved view of the default
conguration that the node returns to on reset or reload).
The steps used in bulk provisioning are illustrated in Procedure flowchart for
bulk provisioning on page 143.
Provisioning processes 143
Passport Operations and Maintenance Guide 4S3
Figure 9
Procedure owchart for bulk provisioning
Make changes
Do a check
prov and
Activate the
and additions
Confirm the
activation
A
B
C
Optionally, store
edit view as a
saved view
edit view
Start provisioning
Save the
current view
End provisioning
correct if needed
Commit the
current view
144 Chapter 5
241-7001-150 4S3
This procedure corresponds to the provisioning processes that are described
throughout the Passport documentation suite. Sub-processes are summarized
in the following points:
A represents how provisioning mode is started, and consists of a single
step (step 1 on page 144). In the procedures provided throughout the
Passport documentation suite, this step is referred to as Start
provisioning mode.
B represents the details of provisioning the node, which is the focus of
the provisioning procedures that are provided both in other chapters both
in this document and in the Passport service documents. In this example,
B is represented by a single summary step (step 2 on page 144) but is,
in practice, two or more provisioning steps that add, set, or delete specic
components and attributes.
C represents how provisioning mode is ended, and consists of a series
of steps (step 3 on page 145 to step 9 on page 146) that make the
conguration operational. In the procedures provided throughout the
Passport documentation suite, this sub-process is referred to as End
provisioning mode.
This provisioning procedure can also be used for global data changes and
scheduled network conguration changes.
Procedure 22
Bulk provisioning process
1 Start provisioning mode.
start prov
2 Make changes and additions to the edit view using the following
commands:
load prov
copy prov
apply prov
add
set
delete
The load prov, copy prov, and apply prov commands are used with
provisioning views; the add, set, and delete commands are used with
components and attributes.
Provisioning processes 145
Passport Operations and Maintenance Guide 4S3
3 When all changes and additions are complete, start and complete a full
semantic check of the edit view.
check prov
Provisioning errors are reported on-screen. All errors must be corrected
before you can move on to the next step.
During a full semantic check, the system issues warnings for components
affected by critical provisioning data changes (that is, changes may
require components to be out of service before the change can be
activated).
4 Optionally, store the edit view as a saved view.
save [-file(<filename>)] prov
where:
<lename> is an optional user-supplied designation for the saved view.
The -le parameter is optional, and is used only if the new saved view
needs a unique lename. The system automatically resets the sequence
number to 001.
5 Activate the view.
activate prov
This command copies provisioning data from the edit view into the current
view. When the activate is complete, the current view and the edit view
are identical.
Note: An activate command may cause the system to reload. If a reload
occurs, wait until the node comes back up, then log on and enter
provisioning mode again to issue the conrm prov command.
6 Conrm the activation.
confirm prov
The conrm command veries that the newly activated edit view allows
proper access to the node. Conrm the view within 20 minutes after the
activation is complete, otherwise the node automatically restarts using the
committed view. A maximum of one committed view can be saved to disk.
7 Save the current view.
save -current prov
146 Chapter 5
241-7001-150 4S3
8 Commit the current view.
commit prov
This command creates a special saved view of all conguration
information in the current view. This committed current view now
becomes the view that the node uses whenever undergoing a reload,
restart, or switchover.
Note 1: If a new current view is not committed at this time, the node uses
the last committed view in the event of a reload, restart, or switchover.
Note 2: After a software migration or incremental software load occurs
on the CP, a full semantic check is required before the commit is allowed.
9 End the provisioning session.
end prov
Regular order processing
Regular order processing involves entering a small set of changes for
activation at the next scheduled activation session. During the period between
one activation session and the next, there may be multiple sets of changes,
entered by multiple operators. Changes accumulate until the next activation
session. Generally, operators are data entry clerks working from job sheets.
This process is possible because regular order processing does not have to be
activated immediately (as in immediate or emergency provisioning - see
Immediate or emergency provisioning on page 153). Data entry can be
completed as orders are received. Activation, and the resolution of any
provisioning errors that may arise, can be completed in a single session by an
experienced and knowledgable operator.
Regular order processing constitutes the bulk of changes that occur after the
node is in service. The process undertaken by the data-entry clerks includes
the following steps:
Start the provisioning session.
Make the necessary changes.
Complete a semantic check on the changes, correcting all provisioning
errors found.
Store the changes in a saved view (optional).
end provisioning
Provisioning processes 147
Passport Operations and Maintenance Guide 4S3
The steps used in the data entry portion of regular order processing are
illustrated in the flowchart in Procedure flowchart for data entry in regular
order processing on page 147.
Figure 10
Procedure owchart for data entry in regular order processing
A
B
C
Store the
edit view as a
saved view
Make changes
and additions
Start provisioning
Do a check
prov and
correct if needed
End provisioning
148 Chapter 5
241-7001-150 4S3
As with bulk provisioning, this example of regular order processing also
corresponds to the provisioning processes described throughout the Passport
documentation suite. The sub-processes are summarized in the following
points:
A represents how provisioning mode is started, and consists of a single
step (step 1 on page 151). In the procedures provided throughout the
Passport documentation suite, this step is referred to as Start
provisioning mode.
B represents the details of provisioning the node, which is the focus of
the provisioning procedures that are provided both in other chapters in
this document and in the Passport service documents. In this example,
B is represented by a single step (step 2 on page 151) but is, in practice,
two or more provisioning steps that add, set, or delete specic
components and attributes.
C represents how provisioning mode is ended, and consists of two
steps (step 3 and step 5 on page 151) for completing a semantic check of
the changes and storing those changes in a saved view.
In the procedures provided throughout the Passport documentation suite,
this set of steps is referred to as End provisioning mode. It is
interchangeable with the set of steps labelled C under Bulk
provisioning on page 142.
Note: In the data entry portion of regular order processing, the changes
are not activated.
At a scheduled time, an operator activates all changes entered since the last
activation by completing the following steps:
Start the provisioning session.
Load the saved view that is to activated into the edit view.
Complete a full semantic check on the edit view, correcting all
provisioning errors found.
Store the changes to a saved view (optional).
Move the edit view to the current view by activating the edit view and
conrming.
Provisioning processes 149
Passport Operations and Maintenance Guide 4S3
Store the current view as a saved view.
Commit the current view (which creates a commit view of the default
conguration that the node returns to on reset or reload).
end provisioning.
The steps used in regular order processing are illustrated in Procedure
flowchart for data entry in regular order processing on page 147.
150 Chapter 5
241-7001-150 4S3
Figure 11
Procedure owchart for activating in regular order processing
Start provisioning
Do a check
prov and
correct if needed
Activate the
Confirm the
activation
Optionally, store
edit view as a
saved view
edit view
Save the
current view
Commit the
current view
End provisioning
Provisioning processes 151
Passport Operations and Maintenance Guide 4S3
Regular order processing is described in two procedures: Performing data
entry for regular order processing on page 151 describes how to complete
operator data entry, and Performing view activation for regular order
processing on page 151 describes how to complete activation.
Procedure 23
Performing data entry for regular order processing
1 Start provisioning mode.
start prov
2 Make changes and additions to the edit view using the following
commands:
add
delete
set
The add, set, and delete commands are used with components and
attributes. The load prov, copy prov, and apply prov commands are rarely
used in regular order processing.
3 When all changes and additions are complete, start and complete a
semantic check of the changes made.
check -changed prov
The -changed parameter requests that only components that are in the
edit view and are new or changed from the current view are semantically
checked. As a result, the semantic check is completed in much less time
than if a full check is done.
4 Optionally, store the edit view as a saved view.
save prov
5 End the provisioning session.
end prov
Procedure 24
Performing view activation for regular order processing
1 Start provisioning mode.
start prov
2 Start and complete a full semantic check of the edit view.
check prov
152 Chapter 5
241-7001-150 4S3
Provisioning errors are reported on-screen. All errors must be corrected
before you can move on to the next step.
During a full semantic check, the system issues warnings for components
affected by critical provisioning data changes (that is, changes that may
require components to be out of service before the change can be
activated).
3 Optionally, store the edit view as a saved view.
save [-file(<filename>)] prov
where:
<lename> is an optional user-supplied designation for the saved view
The -le parameter is optional, and is used only if the new saved view
needs a unique lename. The system automatically resets the sequence
number to 001.
4 Activate the view.
activate prov
This command copies provisioning data from the edit view into the current
view. When the activation is complete, the current view and the edit view
are identical.
Note: An activate command may cause the system to reload. If a reload
occurs, the user should wait until the node comes back up, then log on
and enter provisioning mode again to issue the conrm prov command.
5 Conrm the view.
confirm prov
The conrm command veries that the newly activated edit view allows
proper access to the node. Conrm the view within 20 minutes after the
activation is complete, otherwise the node automatically restarts using the
committed view. A maximum of one committed view can be saved to disk.
6 Save the current view.
save -current prov
7 Commit the current view.
commit prov
This command creates a special saved view of all conguration
information in the current view. This committed current view now
becomes the view that the node uses whenever undergoing a reload,
restart, or switchover.
Provisioning processes 153
Passport Operations and Maintenance Guide 4S3
Note: If a new current view is not committed at this time, the node uses
the last committed view in the event of a reload, restart, or switchover.
8 End the provisioning session.
end prov
Immediate or emergency provisioning
Immediate or emergency provisioning is undertaken when a change must be
activated without delay but without disturbing (or being disturbed by) regular
order processing changes that have been entered for the next scheduled
activation. In typical office operations, immediate or emergency provisioning
changes are infrequent.
Immediate provisioning includes the following steps:
Ensure that any previously-entered changes are stored in a saved view,
and note the name of this view.
Complete the immediate change through the following steps:
Load the view of the system as it was before regular order
processing was undertaken (this load operation involves copying the
current view into the edit view).
Make the changes to the edit view (adding, deleting, and
modifying).
Complete a semantic check.
Activate and conrm the edit view.
Store the changes in a new saved view.
Note: The edit view and the current view are now the same. These views
include the new changes required for immediate provisioning but do not
include the changes made during regular order processing since the last
view activation.
Propagate regular order processing to the new edit view by applying the
delta view edit view.
154 Chapter 5
241-7001-150 4S3
The steps used in immediate provisioning are illustrated in Procedure
flowchart for immediate or emergency provisioning on page 155 and
described in Performing immediate or emergency provisioning on
page 156.
Provisioning processes 155
Passport Operations and Maintenance Guide 4S3
Figure 12
Procedure owchart for immediate or emergency provisioning
Commit the
new current
view
Copy current
view into edit view
Merge regular
order processing
to edit view
Start provisioning
Make changes
and additions
Activate the
edit view
Save the
Confirm the
activation
Additional
changes
needed?
Yes
Save the
edit view
Do a check
prov and
correct if needed
No
End provisioning
merged
changes
156 Chapter 5
241-7001-150 4S3
Procedure 25
Performing immediate or emergency provisioning
1 Start provisioning mode.
start prov
2 Store the edit view as a saved view. Record the lename under which the
view is saved (the lename is displayed on-screen when the save prov
command is complete).
save prov
3 Clear all provisioning data from the edit view and copy the current view
into the edit view.
clear prov
copy prov
4 Make changes and additions to the edit view using the following
commands:
add
delete
set
The add, set, and delete commands are used with components and
attributes. The load prov, copy prov, and apply prov commands are rarely
used in immediate or emergency provisioning.
5 When all changes and additions are complete, start and complete a full
semantic check of the edit view.
check prov
Provisioning errors are reported on-screen. All errors must be corrected
before you can move on to the next step.
During a full semantic check, the system issues warnings for components
affected by critical provisioning data changes (that is, changes may
require components to be out of service before the change can be
activated).
6 Activate the view.
activate prov
This command copies provisioning data from the edit view into the current
view. When the activation is complete, the current view and the edit view
are identical.
Provisioning processes 157
Passport Operations and Maintenance Guide 4S3
Note: An activate command may cause the system to reload. If a reload
occurs, wait until the node comes back up, then log on and enter
provisioning mode again to issue the conrm prov command.
7 Conrm the view.
confirm prov
The conrm command veries that the newly activated edit view allows
proper access to the node. Conrm the view within 20 minutes after the
activation is complete, otherwise the node automatically restarts using the
committed view.
8 If you need to make additional changes, go back to step 4. Otherwise,
continue with step 9.
9 Save the current view.
save -current prov
10 Commit the current view.
commit prov
This command creates a special saved view of all conguration
information in the current view. This committed current view now
becomes the view that the node uses whenever undergoing a reload,
restart, or switchover.
Note: If a new current view is not committed at this time, the node uses
the last committed view in the event of a reload, restart, or switchover.
11 Apply the saved view that you recorded at step 2.
apply -file(<filename>) prov
where:
<lename> is the name of the saved view recorded at step 2.
Observe the messages that appear on the screen. These messages
identify problems that occur when applying the saved view.
12 Save the merged changes.
save prov
13 Once all provisioning is completed, end the provisioning session.
end prov
158 Chapter 5
241-7001-150 4S3
This process assumes that the operator making the immediate or emergency
provisioning change does not need to include the changes from regular order
processing in the immediate activation.
If all regular order processing that has been entered since the last activation
can be included with the immediate change, do the following:
Ensure that any previously-entered changes are stored in a saved view.
Complete the immediate changes through the following steps:
Make the immediate or emergency change to the edit view (adding,
deleting, and modifying components).
Complete a semantic check.
Activate and conrm the edit view.
Store the changes in a new saved view.
Using partial views
Partial saved views can be used for developing provisioning data on one node
and then using that data on other nodes in a network. While this procedure is
not a high-level office process, it is a good procedure to understand.
Creating a partial view consists of the following steps:
Start the provisioning session.
Add a new component or make changes to an existing component.
Run a semantic check on the component to ensure that typographical and
logical errors have not been introduced.
Store the component in a partial saved view.
FTP the partial saved view to a second node.
Start a provisioning session on the second node.
Load the partial saved view on the second node.
Run a full semantic check on the second node to ensure that the
components provisioning data integrates with the nodes environment.
Activate and conrm the edit view.
Provisioning processes 159
Passport Operations and Maintenance Guide 4S3
Store the changes in a saved view.
The steps used in immediate provisioning are illustrated in the flowchart in
Procedure flowchart for immediate or emergency provisioning on page 155
and described in Performing immediate or emergency provisioning on
page 156.
160 Chapter 5
241-7001-150 4S3
Figure 13
Using partial views
Load partial view
into edit view
on second node
Start provisioning
Store component
as a partial view
Move partial view
to second node
Start provisioning
on second node
Edit data for
the component
Do a check
prov and
correct if needed
Activate the
Confirm the
activation
edit view
Save the
current view
Commit the
current view
End provisioning
Do a check
prov and
correct if needed
Provisioning processes 161
Passport Operations and Maintenance Guide 4S3
Procedure 26
Moving provisioning data to another node using a partial view
1 Start provisioning mode.
start prov
2 Make changes and additions to the component in the edit view using the
following commands:
add
delete
set
The add, set, and delete commands are used with components and
attributes.
3 When all changes and additions are complete, start and complete a
semantic check on the component.
check -component(<component_name>) prov
where:
<component_name> is the name of the component, including instance
value.
Provisioning errors are reported on-screen. Correct all errors before
continuing with the next step.
4 Save the component in a partial saved view.
save -file(<filename>) -component(<component_name>)
prov
where:
<lename> is an optional user-supplied designation for the saved view.
The -le parameter is optional, unless the -component option is used.
5 FTP the partial saved view to a second node. For a description of the FTP
process, see 241-6001-023, NMS Architect for Passport User Guide.
Note: The views entire subdirectory must be moved.
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
162 Chapter 5
241-7001-150 4S3
8 Start and complete a full semantic check of the edit view.
check prov
Provisioning errors are reported on-screen. All errors must be corrected
before you can move on to the next step.
During a full semantic check, the system issues warnings for components
affected by critical provisioning data changes (that is, changes may
require components to be out of service before the change can be
affected). Components return to service when the edit view is activated.
9 Activate the view.
activate prov
This command copies provisioning data from the edit view into the current
view. When the activation is complete, the current view and the edit view
are identical.
Note: An activate command may cause the system to reload. If a reload
occurs, wait until the node comes back up, then log on and enter
provisioning mode again to issue the conrm prov command.
10 Conrm the view.
confirm prov
The conrm command veries that the newly activated edit view allows
proper access to the node. Conrm the view within 20 minutes after the
activation is complete, otherwise the node automatically restarts using the
committed view. A maximum of one committed view can be saved to disk.
11 Save the current view.
save -current prov
12 Commit the current view.
commit prov
This command creates a special saved view of all conguration
information in the current view. This committed current view now
becomes the view that the node uses whenever undergoing a reload,
restart, or switchover.
Note: If a new current view is not committed at this time, the node uses
the last committed view in the event of a reload, restart, or switchover.
13 End the provisioning session.
end prov
Provisioning processes 163
Passport Operations and Maintenance Guide 4S3
Global data changes
Global data changes involve a common change to a large number of
components. This type of change is infrequent and is not part of regular order
processing. Common changes may be required across the following:
a large number of components
multiple Passport nodes
The process for implementing changes is similar to the process for bulk
provisioning. This process may involve a large number of commands that are
entered through the Passport text-based interface. See Bulk provisioning on
page 142 for a description of process specifics and procedures. The operator
can also use the NMS Architect Passport Global Data Manager.
Scheduled network conguration changes
Scheduled network configuration changes consist of planned modifications
that affect network topology (for example, the addition of a new trunk).
Generally, these changes do not form part of regular order processing, and are
undertaken at pre-determined times. Changes are activated immediately.
The process for implementing changes is similar to the process for immediate
provisioning. See Immediate or emergency provisioning on page 153 for a
description of process specifics and command sequence. Since changes are
scheduled so that regular data-entry work is not interrupted, saving and
restoring the data-entry environment is unnecessary in most cases.
Where changes to network topology are severe and involve removing or
repositioning trunks, saving to a provisioning data file is recommended.
Further, data entry for services must be undertaken to move services off
redundant network features before those features are removed. The objective
is to reduce or eliminate service disruptions.
164 Chapter 5
241-7001-150 4S3
165
Passport Operations and Maintenance Guide 4S3
Chapter 6
Software installation
This chapter describes how to install software onto the Passport node, both
for initial installation and for subsequent upgrades after the node is in
operation.
Topics covered include:
prerequisites for software installation
summary of the software installation process
overview of Passport software
setting up the software distribution site (SDS)
software installation and conguration
managing software les on the SDS
After reading this chapter, you will be able to install software on the Magellan
Passport using a text interface device.
Except where noted, descriptions and procedures are provided for operators
working with Passport through a VT-100 terminal or a terminal emulator. If
you are using Nortels proprietary Magellan Network Management System
(NMS) see 241-6001-023, NMS Architect for Passport User Guide.
166 Chapter 6
241-7001-150 4S3
Related documents
See the following documents for additional information related to software
installation:
241-7001-005, Passport List of Terms
Passport Supplement for each release of software
Quick access to software installation procedures
To quickly nd the procedures you need, see the following list:
"Installing the software from the CD-ROM on a workstation" on page
183
"Determining what software is already on the node" on page 186
"Downloading the les to disk" on page 189
"Updating the nodes AVL with a new version of software" on page 192
"Conguring a DS1 card" on page 194
"Downgrading using a view from the previous version" on page 197
"Removing an application version" on page 198
"Removing an application version directory" on page 199
"Removing other SDS les and directories" on page 199
Prerequisites
The following topics in this section identify the equipment and software that
must be in place before you begin software installation. Hardware and
software prerequisites include:
Installed Passport node
Installed UNIX workstation
Installed Passport node
The Passport nodes on which you will install software must be operational
and connected to the network, as described in the following documents:
241-7001-125, Passport Hardware Installation Guide
241-7001-130, Passport Startup Guide
Software installation 167
Passport Operations and Maintenance Guide 4S3
At least one control processor and one function processor (a trunk card for
IPIVC) must be installed. A control and function processor (CFP1) alone is
also sufficient for the Passport to be operational and connected to the
network. Other processor cards do not have to be installed at this time.
You need a CD-ROM containing Passport software. The software is installed
onto the SDS as described in this chapter.
You will need the Passport Supplement that is shipped with the software.
Installed UNIX workstation
The workstation you are going to use for software distributionthe SDS
must be fully installed and operational. The workstation must have the
following characteristics:
runs under the UNIX operating system
sufcient hard disk space to accommodate Passport software
congured with a CD-ROM drive (Rockridge format)
userids and passwords are in place for FTP and remote login sessions
connected to the network, with an IP address
You should be comfortable with basic UNIX commands and how to use
them, especially those used for creating and removing directories.
Workstation hard disk capacity requirements
The approximate hard disk space requirements for each Passport release are
detailed in the following points:
Passport software: 55 to 60 Mbytes
management information base (MIB) les: 4.5 Mbytes
Note: File size requirements for the MIB may double to 9 to 10 Mbytes
in future releases if SNMP Version 1.0 and SNMP Version 2.0 coexist on
the SDS.
online documentation: 50 to 55 Mbytes
The disk space requirements change from release to release.
168 Chapter 6
241-7001-150 4S3
Hard disk space requirements increase accordingly if the SDS must support
multiple software releases, including MIBs and online documentation. Since
the files for the MIB and the online documentation are optional, disk space
can be engineered if resources are limited and must be carefully managed.
Summary of the software installation process
Installing software on a Passport node involves downloading software to the
node and configuring that software. This process is completed every time you
are adding new services, capabilities, or features, or when you are upgrading
existing software.
The process for installing software on the Passport is describe below. A
flowchart that summarizes the process is shown in The software installation
process on page 171.
Step 1: Receive software from Nortel
Software is delivered on CD-ROM. It is shipped to the site designated when
the Passport node was orderedeither to the Passport hardware site, or to the
SDS. As new Passport software is released, you automatically receive a
software update on CD-ROM, again delivered to the site designated in the
order.
Along with the software, you also receive documentation that provides you
with specifics on identifying the software files you need for operating or
upgrading applications and capabilities.
If a software-related problem or an emergency occurs, Nortel can provide you
with fixed software. Also, if you issue a customer service request (CSR) for
a serious software problem, you will receive an emergency fix as soon as
possible. Fixes are then applied to the next version of a currently supported
application.
Note: Software for a new node is also loaded and precongured on the
control processors disk.
Software installation 169
Passport Operations and Maintenance Guide 4S3
Step 2: Set up the software distribution site
The SDS is a workstation that has been set up for storage, management, and
distribution of Passport software. Nortel recommends that you use a
workstation that has enough capacity to handle software distribution. The
workstation must be UNIX-based and IP-addressable.
Before Passport software can be transferred from CD-ROM to the
workstation at the SDS, the workstation must be configured for receiving and
managing the software. This process involves setting up appropriate
directories and files as described in "Setting up the software distribution site"
on page 181.
Note: Nortel recommends that you set up no more than one SDS per
network. If you must have more than one SDS per network, ensure that
each node or group of nodes gets new software from the same SDS each
time.
Step 3: Transfer software to the software distribution site
Once the directory structure has been set up at the SDS, the software is
transferred from CD-ROM onto the SDS as described in "Transferring
Passport software to the software distribution site" on page 182.
Note: If you are using an NMS workstation, install the Passport service
data description (SDD) les onto the NMS now. The procedure is
contained in 241-6001-303, NMS Administrator Guide.
Step 4: Download and congure the software les
With the software installed on the SDS, it can then be downloaded to each
Passport node and configured. This process is described in "Installing and
configuring software on Passport" on page 184.
Step 5: Maintain directories at the software distribution site
Because Passport copies the software directly from the SDS, it is important
that the les at the SDS are well maintained. Maintenance activities ensure
that:
required software is installed
obsolete les are removed
170 Chapter 6
241-7001-150 4S3
directories are structured correctly
These activities are described in "Managing the software distribution site" on
page 197.
Software installation 171
Passport Operations and Maintenance Guide 4S3
Figure 14
The software installation process
Step 3:
Transfer software from CD-ROM
to software distribution site
Step 1:
Receive software from Nortel
Step 2:
Set up the software distribution
site
Step 4:
Install and configure software
Step 5 (optional):
Maintain directories at software
distribution site
Begin
End
PPT 0027 001 AC
172 Chapter 6
241-7001-150 4S3
Overview of Passport software
Passport software is modular, which permits users to select, add, and upgrade
software applications according to service needs and the growth of the
network.
Passport software is divided into base and application software modules:
Base software supports Passport functionality and access services. See
the Passport Supplement that is shipped with the software release.
Application software supports access services or supports external
functionality. Examples of application software are Frame Relay, routing
les for supporting specic access services, and software for trunk
connectivity. Application software is also described in 241-7001-110,
Passport General Description as well as in the user guides.
Backward compatibility
In most cases, Passport software is backward compatible. New software can
load provisioning files and interpret provisioning views created using a
previous version of the software. Consult the Passport Supplement for any
backward compatibility exceptions.
Software partitioning
Passport software is partitioned into distinct applications. This modularity
allows you to
obtain Passport software for the individual applications
download and distribute software for individual applications to Passport
nodes
upgrade software versions for individual applications
Each software application consists of a set of software files. Passport
software structure on page 173 shows the software structure of Passport
applications.
Software installation 173
Passport Operations and Maintenance Guide 4S3
Figure 15
Passport software structure
Application versions and application version lists
To understand how to install software on a Passport node, you must
understand application versions and application version lists (AVL).
Application versions
A particular version of an application is called an application version (AV).
Each AV is identified by an application version number.
For example, AV numbers for a specific application could be: AA01, AA02,
and AB01, where AA01 is the oldest version and AB01 is the newest.
Example versions of Passport applications on page 174 is a representation
of various AVs of both application and base software.
Note: In this example a non-backward-compatible change is introduced
in base version AB01 as indicated by the simultaneous release of new
AVs of the other software.
ACCESS
SERVICES
TRUNKS
NETWORKING
BASE
PPT 0028 001 AA
174 Chapter 6
241-7001-150 4S3
Figure 16
Example versions of Passport applications
Application version list
An application version list (AVL) specifies the selected version for each
application to run on a Passport node. Application version list examples on
page 175 shows how an AVL is created for a Passport node when you select
various AVs.
Note: The AVL is a provisionable attribute of the Passport software (SW)
component.
In the example in Application version list examples on page 175, the AVL
specifies that version AB01 of Base, version AB01 of Appl1, version AB02
of Appl2, and version AB03 of Appl3 are selected as the versions of software
to run on the Passport node.
Appl 3
Appl 2
Appl 1
Base
AA01 AA02 AA03 AA04
AA01 AB01
AB02
AA01 AB01 AA02
AA01 AA02 AB01 AB02
PPT 0029 001 AA
Software installation 175
Passport Operations and Maintenance Guide 4S3
Figure 17
Application version list examples
Software hierarchy
Passport software released on CD-ROM is structured so that it can be
installed on the workstation at the SDS in the hierarchical directory structure
shown in Passport software directory structure at a software distribution
site on page 176.
Setting up these directories at the SDS, as described in "Setting up the
software distribution site" on page 181, is the prerequisite to transferring files
from CD-ROM, as described in "Transferring Passport software to the
software distribution site" on page 182.
Passport software directory structure at a software distribution site on
page 176 shows the four required levels of the hierarchy, from top to bottom,
as follows:
user-dened home directorythe default login directory
Appl 3
Appl 2
Appl 1
Base
AA01 AA02 AA03 AA04
AA01 AB01 AB02
AA01 AB01 AA02
AA01 AA02 AB01 AB02
PPT 0030 001 AA
176 Chapter 6
241-7001-150 4S3
softwarethe software directory
applicationdirectories containing software AV directories (base is
managed as an application)
application versiondirectories, each containing all control les and
object les for a particular version of the application
The directory structure maintained on a Passport node is similar to the
hierarchical structure installed on the workstation.
Note: During installation, the installation program creates a default
directory (/nortel) into which the MIBs and online documentation are
copied. For Passport software, you must dene your own directory
structure.
Figure 18
Passport software directory structure at a software distribution site
<Application 2> <Application 1> base
User defined
AA01 AA01 AA02 AA01 AB01
User-defined
home directory
Application
Application
version
Software installation 177
Passport Operations and Maintenance Guide 4S3
Optional software: MIB and online documentation
Installing files for MIB and online documentation is optional. The directory
structure for these options is illustrated in Passport SDS software directory
structure: optional MIB and online documentation on page 178.
178 Chapter 6
241-7001-150 4S3
Figure 19
Passport SDS software directory structure: optional MIB and online documentation
PPT 0772 001 AA
Note: The bin directory contains the viewer files, if installed.
passport
passport
files files
software
version
software
version
mibs
magellan
magellan
bin
/nortel
management documentation
release dir's release dir's
Software installation 179
Passport Operations and Maintenance Guide 4S3
Logical processors and logical processor types
Logical processors (LP) and logical processor types (LPT) provide the
mechanism for mapping software to processor cards.
Key to this process is the premise that software is not physically linked to a
processor card, but rather to a logical entity called a logical processor. This
topic is explored below. Refer also to ExampleRelationship between LPs,
LPTs, and processor cards in a 16-slot Passport switch on page 180.
Logical processors
Each LP represents the entire body of software to be run on a processor card
for delivering one or more Passport services or capabilities. Because the LP
is a logical entity, it can be mapped to any processor card to suit the Passport
configuration. Moreover, an LP can be mapped to one processor card as the
main (active) card for supporting a service, and to a spare card for backup if
the main card fails.
Mapping of LPs to processor cards
permits exibility in conguring the Passport node
allows the operation of the node to respond dynamically to changes in the
availability of processor cards. Applications associated with an LP can
continue even though the physical location of the software has changed.
Logical processor types
Each LPT defines the features and, implicitly, the software files, needed by
an LP. Note that it is possible for LPs that run the same software to share the
same LPT.
180 Chapter 6
241-7001-150 4S3
Figure 20
ExampleRelationship between LPs, LPTs, and processor cards in a 16-slot Passport
switch
Supposing in ExampleRelationship between LPs, LPTs, and processor
cards in a 16-slot Passport switch on page 180 that LPT/FRS represents the
software load required to run the Frame Relay service. Then, both LP/5 and
LP/8 provide Frame Relay services on the processor cards they are mapped
to. In this instance, both card 1 and card 3 are actively running Frame Relay
with card 2 as backup to card 1. Cards 1 and 2 could be, for example, DS1
processor cards, and card 3 could be a V.35 processor card.
Also in the example, the software associated with LP/0 is control processor
software. The card in slot 0 must be a CP. If the shelf is configured for CP
redundancy, the second CP must be in the last slot on shelf. In this case, the
CP in slot 0 is configured as the main CP and the one in slot 15 is configured
as the spare.
Logical processor types
(LPT)
Logical processors
(LP)
Processor cards
(Cards)
(cardType)
LPT/FRS
LPT/CP
LP/0
LP/8
LP/5
Card/0
Card/1
Card/2
Card/3
Card/15
Primary mapping (main)
A user-specified feature name
PPT 0032 001 AA
Software installation 181
Passport Operations and Maintenance Guide 4S3
Slot 0 can also support a control and function processor (CFP1) in a 3-slot and
5-slot Passport switch. Slot 0 in a 3-slot Passport switch will only support
CFP1. The CFP1 does not support redundancy.
Summary of LP, LPT, and card provisionable attributes
The following list is a summary of provisionable attributes used to congure
LPs, LPTs, and cards during software conguration. Provisioning these
attributes enables services (features) on the Passport node.
LPT
featureLista list of features (services) loaded (or to be loaded) on
the processor
systemCongurationsystem conguration parameters on start-up
(this cannot be modied)
commentText an arbitrary string that can be used to describe the
LPT
LP
mainCardthe main processor card assigned to the LP
spareCardthe spare processor card (if available) assigned to the
LP
logicalProcessorTypethe LPT that species the software assigned
to the LP
customerIdentierthe LPs Passport customer identier
card
cardTypespecies the type of card to be used
Setting up the software distribution site
The topics in this section describe how to prepare the SDS for receiving
software that will be transferred from the CD-ROM. Topics include
dening userids that can be used by Passport when placing an FTP call
setting up UNIX directories and les
Refer also to 241-7001-900, Passport SNMP User Guide.
182 Chapter 6
241-7001-150 4S3
Dening software distribution site userids and default
directories
Contact the system administrator to set up your userid and default login
directory. Follow these guidelines when setting up userids:
Ensure that the userid has read-access to all software les.
Make sure that the default login directory has a subdirectory called
software.
Nortel recommends that you assign to each userid only those access
privileges that are necessary for the owner to carry out operations,
administration, and maintenance tasks.
Setting up UNIX directories and les
The UNIX directories required to store Passport software applications, MIBs,
and online documentation are set up during the installation procedure
described in "Transferring Passport software to the software distribution site"
on page 182. You must define the directory for the Passport software
applications, using option 1 in the installation program. The directories
required for the Passport MIBs and online documentation are created
automatically by the installation program.
Each AV, MIB, and online documentation release resides in a subdirectory
(see Passport software directory structure at a software distribution site on
page 176 and Passport SDS software directory structure: optional MIB and
online documentation on page 178).
Transferring Passport software to the software distribution
site
This section provides the procedure for transferring Passport software files
from CD-ROM to the directories and files set up at the SDS.
Before performing the procedures in this section, ensure that the SDS has
been set up, as described in "Setting up the software distribution site" on page
181.
Software installation 183
Passport Operations and Maintenance Guide 4S3
Installing software from the CD-ROM on a workstation
Installing the software from the CD-ROM on a workstation on page 183
provides the steps for transferring software from the CD-ROM to a
workstation (Sun OS 4.1.3U1 or 4.1.4, Solaris, HP, or IBM).
The installation program lets you install the optional MIB les and online
documentation les. These les can be installed at this time, or at any time in
the future.
Procedure 27
Installing the software from the CD-ROM on a workstation
1 Log on to the workstation with a userid that has the appropriate privileges.
2 Create a directory onto which the CD can be mounted. Note that if
mountable CDs have been used in the past for other applications, this
directory may already exist.
cd /
mkdir /cdrom
Note: To create the /cdrom directory, you may have to be logged on as
root.
3 Mount the CD (do not perform this step if you are using Solaris).
For Sun OS:
mount -rt hsfs /dev/sr0/cdrom
For HP (HPUX):
mount -rt cdfs /dev/dsk/c20ld2s0/cdrom
For IBM (AIX):
mount -rv cdrfs /dev/cd0/cdrom
Note: To mount the CD as outlined in this step, you may have to be
logged on as root.
4 Start the installation program. Ensure that you have the Passport
Supplement documents.
If you are using Sun OS, HPUX, or AIX:
/cdrom/install
If you are using Solaris:
/cdrom/cdrom0/install
184 Chapter 6
241-7001-150 4S3
5 Follow the prompts to install Passport software, MIBs, and online
documentation.
The installation program indicates when the installation is complete.
Note 1: Passport software applications are installed in the directory you
dene using option 1 of the installation program. Online documentation
and viewer les are installed under the directory /nortel/documentation/
magellan/passport; the MIBs are installed under the directory /nortel/
management/mibs/magellan/passport).
Note 2: If you are using an NMS workstation, install the Passport service
data description (SDD) les onto the NMS now. The procedure is
contained in 241-6001-303, NMS Administrator Guide.
6 Once the software has been successfully installed, log in as root user and
unmount the CD.
If you are using Sun OS, HPUX, or AIX:
umount /cdrom
If you are using Solaris:
eject cdrom
Installing and conguring software on Passport
The topics in this section describe how to install and configure software on an
existing or new Magellan Passport node using a text interface device.
Planning software installation
Do the following before starting the procedures in this chapter.
Read over the procedures to make sure that you understand what is
required. Gather information that you need.
Have the Passport Supplement received with the software handy. You
need it to identify the software les for the applications to be installed or
upgraded on the node.
Understand the compatibilities of the software you are installing with
other software operating on the node. Also consider compatibilities of
software in general if you need to roll back to an earlier software version.
See the Passport Supplement for this information.
Ensure that you have the required capability set associated with your
userid to access the node. (See "Userid and its attributes" on page 207 for
an explanation of capability sets.)
Software installation 185
Passport Operations and Maintenance Guide 4S3
Know the IP address, userid, and password for the SDS where the
required software is stored.
Understand the hardware conguration (or the proposed hardware
conguration) of the node; that is, type of processor cards installed and
their slot locations.
Note: It is not necessary to have all function processors installed before
you install software if you use the local console.
Determine the services and capabilities to be supported by each
processor card. Then determine the AVs required by the Passport node in
support of these services and capabilities so that you can compile the
AVL.
Determine which cards you will use as spares so that you can congure
the LPs accordingly.
Conguring Passport software
Configuring software on a Passport node entails defining which service or
capabilities (features) will be supported on which processor card. This is done
by provisioning the SW, LPT, LP, and Card components.
Semantic checks are performed to ensure that there are no inconsistencies
within the components specified.
The following steps must be performed to congure software on a Passport
node:
establish the status of the software on the node
ensure that there is enough space available on the le system
download software les from the SDS to the nodes hard disk
update the nodes AVL
Use the other procedures in this section as required. They tell you how to
congure a new processor card
change a processor cards software load
create, modify, or delete an LP
186 Chapter 6
241-7001-150 4S3
add more software features to an LPT
remove a software feature from an LPT
downgrade to a previous software version
Establishing the status of the software on the node
Follow the steps in this section to verify the current status of the software on
the node. As you proceed, track the current software versions and features to
establish a ground zero reference point.
Procedure 28
Determining what software is already on the node
1 Determine which versions of application software are currently available
on the nodes disk.
list sw av/*
A list of all of the currently available applications is displayed, in the form:
Sw Av/base_AQ0123A
Sw Av/base_AQ0123B
Sw Av/bridge_AQ0123B
Sw Av/frameRelay_AQ0123B
Sw Av/inwBase_AQ0123A
Sw Av/inwBase_AQ0123A
Sw Av/ip_AQ0123A
Sw Av/ip_AQ0123B
Sw Av/netSentry_AQ0123A
Sw Av/netSentry_AQ0123B
Sw Av/networking_AQ0123A
Sw Av/networking_AQ0123B
Sw Av/trunks_AQ0123B
Sw Av/wanDte_AQ0123B
2 Determine which version of software is currently active.
display -p sw avl
A list of the applications that are currently active is displayed, in the form:
avList = base_AQ0123b, networking_AQ0123b,
trunks_AQ0123b, frameRelay_AQ0123b
Note 1: In this example, the version of base, networking, trunks and
frameRelay software that is currently active is AQ0123b.
Software installation 187
Passport Operations and Maintenance Guide 4S3
Note 2: Each example of a response in this procedure is illustrative only.
The information that is actually displayed in response to any command
varies depending on the conguration of the node.
3 Determine which features are provisioned on each LP.
display -p -n sw lpt/*
For each LPT, the featureList attribute species which features have been
provisioned. The logicalProcessors attribute species which LPs use this
LPT:
Sw Lpt/ATMBASE
commentText = ""
featureList = atmBearerService,atmTrunks
systemConfig = default
logicalProcessors = Lp/1,Lp/4
Sw Lpt/ATMTRK
commentText = ""
featureList = atmTrunks
systemConfig = default
logicalProcessors =
Sw Lpt/CP
commentText = ""
featureList =
systemConfig = default
logicalProcessors = Lp/0
Sw Lpt/FRATM
commentText = ""
featureList = frameRelayAtm
systemConfig = default
logicalProcessors =
Sw Lpt/FRATMGTY
commentText = ""
featureList = frameRelayAtm,frameRelayUni
systemConfig = default
logicalProcessors = Lp/5
Sw Lpt/FRATMGTYSVC
commentText = ""
featureList = frameRelayAtm,frameRelayUniPvcSvc
systemConfig = default
logicalProcessors = Lp/2
Sw Lpt/FRUNI
commentText = ""
featureList = frameRelayUni
systemConfig = default
logicalProcessors =
188 Chapter 6
241-7001-150 4S3
Sw Lpt/NLOFR
commentText = ""
featureList = frameRelayMux,utpTrunks,frDpnTrunks
systemConfig = default
logicalProcessors = Lp/6
Sw Lpt/TRK
commentText = ""
featureList = unackTrunks
systemConfig = default
logicalProcessors = Lp/3
ok
Note 1: This example shows that LP/0 is congured with the IPIVC
feature, LP/1 and LP/2 are congured with the frameRelayUni feature and
LP/3 is congured with the unackTrunks feature.
Note 2: To display information in tabular format, omit the -n parameter
from the command line.
4 Determine which features are associated with a particular application. For
example frameRelay_AQ0123B.
list Sw Av/frameRelay_AQ0123B Feat/*
The variants of the feature software are displayed in the form:
Sw Av/FrameRelay_AQ0123B Feat/frameRelayUni
Sw Av/FrameRelay_AQ0123B Feat/frameRelayNni
Note: Repeat this step for all of the applications of interest to you.
Ensuring free space on the le system
If you have a large amount of software installed on your Passport node, you
may not have enough free space on the le system to install more software.
In this case, you will have to remove unused software and provisioning les
from the le system before you install new software.
Procedure 29
Ensuring free space on the le system
1 Determine the space currently available on the le system.
display fs
The status of the le system is displayed in the following form:
Fs
adminState = unlocked
operationalState = enabled
usageState = active
Software installation 189
Passport Operations and Maintenance Guide 4S3
volumeName = MainDisk
activeDisk = Fs Disk/0
syncStatus = unSynchronized
syncProgress = 0 %
capacity = 811122688 bytes
freeSpace = 544079872 bytes
usage = 33 %
The freeSpace value indicates the number of bytes available on the le
system.
2 If the le system does not have enough available space, remove any
unused software and provisioning les.
For information on removing software les, see Removing unused
software les on page 602. For information on removing provisioning
les, see tidy prov on page 130.
Downloading the les to disk
Follow the procedure in this section to download the software les from the
SDS to the hard disk on the node.
Procedure 30
Downloading the les to disk
1 Verify that the downloader is inactive.
display sw dld
The status of the downloader is displayed, in the form:
Sw Dld
avBeingDownloaded =
status = inactive
filesToTransfer = 0
avListToDownload =
downloadedAvList =
2 Specify the software you want to download, for example:
set sw dld avListToDownload trunks_AQ0123C
frameRelay_AQ0123C
3 View the list of software to be downloaded.
display sw dld
The status of the downloader is displayed, in the form:
190 Chapter 6
241-7001-150 4S3
Sw Dld
avBeingDownloaded =
status = inactive
filesToTransfer = 0
avListToDownload = trunks_AQ0123C, frameRelay_AQ0123C
downloadedAvList =
4 Start the download.
start -h(<ipAddress>) -u(<userId>)
-p(<password>) sw dld
where <ipAddress> is the IP address of the SDS
Note: The values shown within the parentheses in this example are for
illustrative purposes only. An example of values for the above command
line is start -h(47.236.0.21) -u(sysOp) -p(happy) sw dld.
The download process is initiated.
5 Monitor the progress of the download process.
display sw dld
The status of the downloader is displayed, in the form:
Sw Dld
avBeingDownloaded = trunks_AQ0123C
status = inProgress
filesToTransfer = 17
avListToDownload = trunks_AQ0123C, frameRelay_AQ0123C
downloadedAvList =
Note: Repeat this step as often as desired. The information that is
displayed changes according to the status of the download process at the
time you issue the display sw dld command.
6 Verify that the download process is terminated.
display sw dld
Once all of the queued les are downloaded, the status of the downloader
is similar to the example below:
Sw Dld
avBeingDownloaded =
status = inactive
filesToTransfer = 0
avListToDownload =
downloadedAvList = trunks_AQ0123C, frameRelay_AQ0123C
Software installation 191
Passport Operations and Maintenance Guide 4S3
7 Verify that the download succeeded.
list sw av/*
A list of all of the currently available application software is displayed, in
the form:
Sw Av/base_AQ0123A
Sw Av/base_AQ0123B
Sw Av/frameRelay_AQ0123A
Sw Av/frameRelay_AQ0123B
Sw Av/frameRelay_AQ0123C
Sw Av/networking_AQ0123A
Sw Av/networking_AQ0123B
Sw Av/trunks_AQ0123A
Sw Av/trunks_AQ0123B
Sw Av/trunks_AQ0123C
8 Review the list to conrm that the applications you downloaded are there.
Updating the application version list
After downloading new versions of your applications to the hard disk, you
can load the applications onto the processors. First, you update the
application version list (AVL) to change the version of the applications.
Then, you activate the view with the new AVL and the applications are
loaded onto the processors.
View migration
Each version of software has an associated component model. The model
defines the components and attributes you can use with the software version.
Often, the component model changes between software versions.
The current and edit view store their provisioned data using the component
model of the currently running software. When you update the AVL of the
edit view and activate it, you change the currently running software and move
from one component model to another.
If you are upgrading the software (updating the AVL with newer application
software), Passport automatically converts the provisioned data stored in the
activated view so it fits into the component model of the newer software. This
conversion process is called view migration. View migration during a
software upgrade on page 192 shows an example where the component
model of the new software has a new component (B) which has a new
192 Chapter 6
241-7001-150 4S3
attribute (4) and also contains attributes (2 and 3) from an old component (A).
The provisioned data from the old component model is automatically moved
so that it fits into the new component model.
Note: When upgrading, always keep a copy of the provisioning le that
was running prior to updating the AVL until you are certain that the new
software functions properly. If you have to downgrade back to the old
version of the software, you will need this le.
Figure 21
View migration during a software upgrade
Procedure 31
Updating the nodes AVL with a new version of software
1 Enter provisioning mode.
start prov
2 Display the current AVL.
display sw avl
The current AVL displays as in the following example:
Sw
avList = base_AQ0123B, frameRelay_AQ0123B,
networking_AQ0123B, trunks_AQ0123B
Root
Component A
attribute 1
attribute 2
attribute 3
view
migration
Root
Component A
attribute 1
Component B
attribute 2
attribute 3
attribute 4
New Software
Old Software
Software installation 193
Passport Operations and Maintenance Guide 4S3
3 Replace the old application versions with new application versions in the
AVL.
To replace specic application versions, use the tilde (~) character in a set
command to delete the old versions and then use another set command
to add the new versions. For example:
set sw avl ~trunks_AQ0123B ~frameRelay_AQ01236B
set sw avl trunks_AQ0123C frameRelay_AQ0123C
To replace all the application versions with new versions, use the
exclamation mark (!) (to empty the AVL) along with the new versions in a
single set command. For example:
set sw avl ! base_AQ0123C frameRelay_AQ0123C
networking_AQ0123C trunks_AQ0123C
4 Display the edited AVL to verify that the proper software is in place.
display sw avl
The AVL displays as in the following example:
Sw
avList = base_AQ0123C, frameRelay_AQ0123C,
networking_AQ0123C, trunks_AQ0123C
5 Verify that the provisioning changes are acceptable.
check prov
Passport responds with a message specifying whether or not any
processor reboots will occur when the new provisioning data is activated.
6 Activate the new software.
activate prov
Note: If the stand-by CP resets during the software activation, continue
the standard software activation sequence on the active CP. Allow both
CPs to load the new software and perform the remaining steps on the
active CP.
7 Enter provisioning mode again.
start prov
8 Conrm provisioning.
confirm prov
9 Verify that the provisioning changes are acceptable.
194 Chapter 6
241-7001-150 4S3
check prov
10 Activate the checked provisioning view.
activate prov
11 Conrm provisioning.
confirm prov
12 After running any tests on the new software, make it the committed view.
commit -file(<name>) prov
where:
<name> is the name you want to give the view containing the new
software
The next step
The next step is to configure the processor cards and to create or modify the
LPs and LPTs. Configuring a DS1 card on page 194 is an example of how
to configure a new processor card. For information on creating and modifying
LPs and LPTs, see Changing a processor cards software load on page 607.
Conguring a new processor card
Follow the procedures in this section to congure a processor card. These
procedures provide an example of how to provision a DS1 function processor
card.
Procedure 32
Conguring a DS1 card
1 Enter provisioning mode.
start prov
2 Display the current shelf conguration:
display -p shelf card/*
Shelf
+====+------+--------------------+---------------
|Card| card | configuredLPs |Response
+====+------+--------------------+---------------
| 0|CP |Lp/0 |
| 1|V35 |Lp/1 |
| 2|V35 |Lp/2 |
| 3|DS1 |Lp/3 |
| 4|none | |
Software installation 195
Passport Operations and Maintenance Guide 4S3
| 5|none | |
| 6|none | |
| 7|none | |
| 8|none | |
| 9|none | |
| 10|none | |
| 11|none | |
| 12|none | |
| 13|none | |
| 14|none | |
| 15|CP |Lp/0 |
ok 1994-10-28 13:53:47.16
3 Assign a card type to a slot:
set shelf card/4 cardType DS1
4 Add an LP component:
add lp/8
5 Link the LP to the card:
set lp/8 mainCard shelf card/4
6 Add an LPT component (the LPT name in this case is lptname):
add sw lpt/lptname
Note: No new LPT component needs to be added if an existing LPT with
the appropriate features already exists.
7 Add application features.
set sw lpt/lptname featureList frameRelayNni
Note: For the purposes of this example, the Frame Relay NNI feature is
added to the list.
8 Link the LPT to the LP:
set lp/8 lpt sw lpt/lptname
9 Display the Card, LP, and LPT congurations:
display shelf card/4
Shelf Card/4
cardType = DS1
configuredLPs = Lp/8
ok 1994-10-28 14:07:14.74
display lp/8
196 Chapter 6
241-7001-150 4S3
Lp/8
mainCard = Shelf Card/4
spareCard =
logicalProcessorType = Sw Lpt/lptname
customerIdentifier = 0
ok 1994-10-28 14:07:24.07
display sw lpt/lptname
Sw Lpt/lptname
commentText = ""
featureList = frameRelayNni
systemConfig = default
logicalProcessors = Lp/8
ok 1994-10-28 14:07:37.32
10 Verify that the provisioning changes are acceptable.
check prov
11 Bring the new processor card into service.
activate prov
Prov
You have 20 minutes in which to confirm activation.
ok 1994-10-28 14:08:31.05
12 Conrm provisioning.
confirm prov
13 After running any tests on the new software, you can make it the
committed provisioning data.
commit -file(<filename>) prov
where:
<filename> is the name you want to give the le containing the new
software
14 End the provisioning session:
end prov
Downgrading to a previous software version
You may want to downgrade the software running on the Passport to a
previous version. You can downgrade by reloading the CP using a view that
was saved while running the previous version of the software.
Software installation 197
Passport Operations and Maintenance Guide 4S3
Procedure 33
Downgrading using a view from the previous version
1 Reload the control processor using a view from the previous version.
reloadcp -file(<name>) lp/0
where:
<name> is the name of the view saved while running the previous
software version.
The Passport resets itself and runs the previous version of software.
If things go wrong
Passport notifies you if installation of software has been successful, or if it
fails.
Sometimes, the software installation process fails due to a network problem
or failure (such as the failure of power, the FTP connection, Passport node, or
control processor). Proceed as follows:
Determine whether the problem can be isolated to a Passport node. If so,
see Troubleshooting the Passport node on page 493 for
troubleshooting and maintenance procedures.
Once you have resolved the problem, restart the software installation
from the beginning of the process.
When you restart the software installation process, Passport
removes any partial or corrupted les damaged during the failure
checks the les successfully downloaded before the failure (Passport
does not download any les that already exist on its hard disk)
The software installation process may also fail because you ran out of space
on the Passport file system. If this situation occurs, you will have to delete
unused files. See Ensuring free space on the file system on page 188.
Managing the software distribution site
This section describes how to manage the SDS after it has been set up as
described in "Setting up the software distribution site" on page 181.
198 Chapter 6
241-7001-150 4S3
Basically, this involves two tasks:
setting up directories for new software
removing old software releases and, as necessary, directories
Prerequisites
Key to maintaining the SDS involves analyzing needs to determine
what software needs to be retained at the SDS
what needs to be removed or replaced
Adding new software
To place new software onto the SDS, see "Transferring Passport software to
the software distribution site" on page 182.
Removing unwanted software
The following procedures describe how to remove unwanted software,
specically AVs and applications. For further information, see Removing
unused software les on page 602.
Removing an application version
Proceed as follows to remove an AV directory.
Procedure 34
Removing an application version
1 Change to the appropriate AV directory.
cd ~/software
Note: ~ represents the home directory of the FTP login account.
2 Remove the AV by typing the UNIX rm (remove) command.
rm -rf <application>/<version>
Note: -r is the recursive option used to remove a directory, all its les
and subdirectories.
For example, to remove version AA01 of Base, type the following:
rm -rf base/AA01
Software installation 199
Passport Operations and Maintenance Guide 4S3
Removing an application
Proceed as follows to remove an application directory.
Procedure 35
Removing an application version directory
1 Go to the appropriate application directory.
cd ~/software
Note: ~ represents the home directory of the FTP login account.
2 Remove the application by typing the UNIX rm (remove) command.
rm -rf <application>
Note: -r is the recursive option used to remove a directory, all its les
and subdirectories.
For example, to remove all versions of the Frame Relay application, type:
rm -rf FrameRelay
Removing other SDS les and directories (including MIBs and
online documentation)
Proceed as follows to remove other les and directories that are used for
Passport, including those that contain MIBs and online documentation.
Procedure 36
Removing other SDS les and directories
1 Cd to the appropriate directory.
2 Check to make sure you are in the correct directory.
pwd
The actual name (not the alias) of the directory you are in appears.
3 Ensure that the les you want to remove are in that directory.
ls -l
4 Use the UNIX remove command to remove all the subdirectories and les
in that directory.
rm -r *
5 Go back up one level in the directory hierarchy.
cd ..
6 Remove the directory that you have just cleared of all its les.
200 Chapter 6
241-7001-150 4S3
rmdir <directory_name>
201
Passport Operations and Maintenance Guide 4S3
Chapter 7
Initial node provisioning steps
This chapter provides an overview of the steps required to provision the
Passport node. After reading this chapter, you will have an understanding of
the on-switch provisioning fundamentals. By following the steps and
references in this chapter carefully, you will ensure that the node becomes
fully operational.
Except where noted, descriptions and procedures are provided for operators
working with Passport through a VT-100 terminal or a terminal emulator. If
you are using Nortels proprietary Magellan Network Management System
(NMS) see 241-6001-023, NMS Architect for Passport User Guide.
Provisioning node security
Provisioning node security is a first time activity. It is the first thing that must
be provisioned on a new node.
Node security can later be provisioned on an ongoing basis. Provisioning
node security involves the following tasks:
adding userids
adding IP access
changing userids
changing IP access
See Provisioning node security on page 202 for a list of the tasks that are
involved in provisioning node security and references to detailed procedures.
202 Chapter 7
241-7001-150 4S3
Provisioning the node
Once you have provisioned node security, the following components must be
provisioned (see Provisioning a node on page 203 for more information):
nodeName and nodeId: The node identier (nodeId) is a 12-character
ASCII string that uniquely identies the node for routing purposes. The
node identier is used in the routing control packets sent by the node to
other Passport nodes in the network. The node identier for each node in
the network is learned from the Passport routing protocol packets.
Although both components are provisioned during the StartUp process
(241-7001-130, Passport Startup Guide) there is a procedure in this
chapter for reprovisioning them if necessary.
Cards and ports: This involves provisioning the logicalProcessor,
logicalProcessorType, Card, and Port components.
CAUTION
Provision userids and IP access numbers
immediately
The rst provisioning task must be to provision at least
one userid with system administration impact followed
by all other userids and IP access numbers. If no userids
or IP access numbers are provisioned, anyone logging in
receives the highest impact (debug), the highest scope
(network), and a customer identier (CID) of 0.
Table 23
Provisioning node security
Task Location
1 Adding system administration
userids; Nortel recommends that
at least two be added per node.
2 Adding userids
3 Adding IP access
Node security on page 205
Initial node provisioning steps 203
Passport Operations and Maintenance Guide 4S3
Trunks: Trunks can be added once the card (to which the trunk will be
connected) and its ports have been provisioned. Provisioning a trunk
involves adding a Trunk component and setting its attributes.
Topology: This involves provisioning the updateInterval attribute (this
attribute must be the same for all nodes in the network). Topology
maintains a topological database that describes the complete Passport
network topology and the outbound costs on all trunk groups.
IP over VC interface or IP over FR interface: These provide a connection
between the Magellan Network Management System (NMS)
workstation and the Passport node. You can provision only one or the
other (either IPIVC or IPIFR). See 241-7001-130, Passport Startup
Guide, for details on how to set up the initial IPIVC or IPIFR. If further
IPIVC or IPIFR provisioning is required, see Node provisioning on
page 217 in this document.
Provisioning the data collection system
After you have completed the provisioning mentioned in previous sections,
you may want to provision the data collection system. You can avoid
provisioning the data collection system by using the defaults.
The data collection system must be provisioned to collect specified data types
on the node. Data types include logs, alarms, state change notifications
(SCN), debug, statistics, and accounting.
Table 24
Provisioning a node
Task Location
1 Provisioning cards and ports.
2 Provisioning a trunk.
3 Provisioning the topology.
4 Provisioning the IPIVC interface
or the IPIFR interface.
1: Processor card provisioning on
page 293
2 to 4:
Node provisioning on page 217
204 Chapter 7
241-7001-150 4S3
Provisioning the data collection system is described in Data collection on
page 459. More details on accounting are provided in 241-7501-400,
Passport Accounting Reference Guide.
Installing and provisioning services
Add access services to tailor the node to node and network requirements. Any
or all of the access services can be added after all of the previously mentioned
provisioning is performed. See the individual access service guides for more
information on installing and provisioning a particular service.
205
Passport Operations and Maintenance Guide 4S3
Chapter 8
Node security
This chapter describes how to setup operator access to the Passport, and login
and logout procedures for authorized operators. After reading this chapter,
you will be able to configure userids and access privileges on the Passport.
For information on network security, see the appropriate service guide for the
networking feature.
Except where noted, descriptions and procedures are provided for operators
working with Passport through a VT-100 terminal or a terminal emulator. If
you are using Nortels proprietary Magellan Network Management System
(NMS) see 241-6001-023, NMS Architect for Passport User Guide.
CAUTION
Provision userids and IP access numbers
immediately
The rst provisioning task must be to provision at least
one userid with system administration impact followed
by all other userids and IP access numbers. If no userids
or IP access numbers are provisioned, anyone logging in
receives the highest impact (debug), the highest scope
(network), and a customer identier (CID) of 0
(netman).
206 Chapter 8
241-7001-150 4S3
Related documents
See the following documents for additional information related to node
security:
241-7001-110, Passport General Description
241-7001-870, Passport Security and Access Control User Guide
241-7001-900, Passport SNMP User Guide
241-7501-210, Passport Components
The document 241-7001-870, Passport Security and Access Control User
Guide details a utility for gathering statistics and controlling packets passing
through a node.
About the provisioning procedures in this chapter
The intent of this chapter is to focus on the steps and commands necessary to
provision the node. To maintain this focus, details on the components and
attributes (for example, default values) referred to in the various procedures
of this chapter are contained in 241-7501-210, Passport Components.
If you are using Nortels proprietary NMS, see 241-6001-023, NMS Architect
for Passport User Guide.
Quick access to node security procedures
To quickly nd the procedures you need, see the following list:
"Adding a userid component" on page 211
"Adding an IpAccess component" on page 213
"Copying an existing userid for a new user" on page 214
"Changing the password on an existing userid" on page 215
"Changing the password of a userid" on page 215
"Deleting a userid component" on page 216
Prerequisites for conguring Passport security
Your userid must have a system administration impact to perform the
procedures in this chapter.
Node security 207
Passport Operations and Maintenance Guide 4S3
For security reasons, Passport does not provide a means by which you can
retrieve lost passwords. Therefore, it is very important to remember the
password for at least one user with system administration impact. If you
forget your password, Passport access is only possible with the assistance of
a system administrator. If this is not possible, contact Nortel support for
assistance.
Passport security features
The Passport node maintains the following security information:
a list of IP host addresses from which connections are accepted
information on userids, passwords, capabilities, customer identiers, and
interfaces
a record of successful and invalid login attempts
a record of operator commands issued to the node
Valid IP address list
The Passport node maintains a list of IP host addresses from which
connections to the node are accepted. All other connections are cleared, and
an alarm is generated for security tracking. These IP host connections apply
to Telnet, FMIP, and FTP interfaces.
Userid and its attributes
Associated with each user on a node is a userid and a password. This is the
primary authentication system on the node. The userid and password are
configured by the system administrator and stored in a provisioning file.
Userids and passwords must be configured on each node.
Userids are between one and eight characters in length. You must have a
system administration impact to change userids. The following attributes are
part of the Userid component:
password
customerIdentier
commandScope
commandImpact
208 Chapter 8
241-7001-150 4S3
allowedAccess
loginDirectory
Note: Capability sets control the abilities of each user. The capability set
that is applied to each user consists of a scope, an impact and a CID. The
system administrator must congure a capability set for each user.
password
The password is case-sensitive and can be from ve to eight characters in
length. You must have a system administration impact to change passwords.
The Passport node does not perform any aging or re-use checking on the
password. The password is stored in encrypted form.
customerIdentier
The CID is used in customer network management (CNM) to constrain the
user to those components that belong to the same CID. A CNM operator can
send commands only to components provisioned with the same CID as the
operator. Also, a CNM operator receives only data collection system data,
such as alarms, which is generated by components provisioned with the same
CID as the operator. The special CID of 0 is reserved for the network owner,
known as the network manager (netman).
Note: Only users with a CID of 0 are permitted to carry out provisioning
procedures.
commandScope
The command scope determines the importance of the components on which
the userid is allowed to execute commands. For example, if a userid is
provisioned with a scope of device, the user can execute commands against
all components that themselves have a scope of device. The scope is
hierarchical: a userid provisioned with a scope of network can also manage
components with a scope of device or application. Scope capabilities are
Network the userid can manage components that affect the operation
of the entire network. For example, Trunk components have a scope of
network.
Device the userid can manage components that affect the operation of
the entire Passport node. For example, LogicalProcessor components
and FileSystem components have a scope of device.
Node security 209
Passport Operations and Maintenance Guide 4S3
Application/line the userid can manage components that affect the
operation of a single application or access port. All Port components, for
example, have a scope of application.
commandImpact
The command impact determines the importance of the commands which the
userid will be allowed to execute. The impact is hierarchical: a Userid
component provisioned with debug impact can also issue all other commands
at lower impact levels. Impact capabilities are as follows:
Debug the userid can issue debug commands. This is the highest
impact level and is used primarily by Nortel personnel to resolve
problems that may occur in the eld.
Note 1: Exercise extreme caution when using debug commands as they
have the potential to cause system failure.
Note 2: If a users impact is provisioned to debug, then the users scope
should also be set to network.
System administration the userid can issue provisioning commands on
security components. This means that the user can add, delete, display,
and set the Userid and IpAccess subcomponents of the AccessControl
component.
Conguration the userid can issue provisioning commands to alter the
provisioned conguration of the Passport node, such as start prov, add,
delete, and set.
Service the userid can issue operational commands that may affect the
service of running components, such as lock and unlock, and can issue
provisioning commands to activate, conrm, and commit provisioning
data les that have been previously edited and saved by a user with a
higher impact level.
Passive the userid can issue only query commands that display
unrestricted information but otherwise do not affect the operation or
conguration of the Passport node. Commands such as list and display
can be used with an impact of passive. Passive is the lowest impact level.
210 Chapter 8
241-7001-150 4S3
allowedAccess
The allowedAccess attribute constrains a user to certain specied interface
types. The interface type can be set to one or more of the following:
local operator
FMIP (Nortels proprietary management interface protocol)
Telnet
FTP
Login
A maximum of three invalid login attempts are allowed after which the
interface becomes locked for two minutes.
Logging of operator commands
Most operator actions and commands that are issued to a node are stored on
a disk le. The following commands are stored:
all login attempts (successful and invalid)
all non-passive ASCII commands (for example, set and lock) issued by
Telnet, local operators, and FMIP command consoles)
all logouts
all FTP commands
Local operator security
Connection to a Passport local operator requires physical access to the
Passport node. You can ensure access control to the local operator by
restricting physical connections to the V.24 port on the control processors.
Note: If a modem is connected to the V.24 port for remote control, make
sure that the modem is not readily accessible through the telephone
network.
Adding a userid component
This section explains how to add a new userid and how to set userid attributes.
When a node is first provisioned, at least one userid with a system
administration impact must be provisioned. Nortel recommends that at least
two userids exist with the system administration impact.
Node security 211
Passport Operations and Maintenance Guide 4S3
You must be in provisioning mode to perform the steps in this procedure. See
Provisioning system description on page 85 for details on how to start and
end provisioning mode.
Procedure 37
Adding a userid component
1 Start provisioning mode.
2 Add the userid component.
add Ac Userid/<userid>
where:
<userid> is from one to eight characters in length
Note: Ac is the abbreviation for the AccessControl component.
3 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 system administrator or higher
can set a password.
Note 3: Once set, the password cannot be displayed.
4 Set the customer identier (CID).
set Ac Userid/<userid> customerIdentifier <identifier>
where:
<userid> is from one to eight characters in length
<identifier> is any number between 0 and 8191. The CID constrains
the user to those components that belong to the same CID.
5 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 this
command is not entered.
212 Chapter 8
241-7001-150 4S3
Note: For the Architect for Passport tool, <scope> must be set to
network.
6 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 system
administration. The command impact is automatically set to the default of
passive if this command is not entered.
7 Set the allowed network management interfaces (NMIF).
set Ac Userid/<userid> allowedAccess <NMIF>
where:
<userid> is from one to eight characters in length
<NMIF> is one or more of: local (default), FMIP, telnet, or FTP. This
constrains the user to the specied interface types that can be used. The
allowed NMIF is automatically set to the default of local if this command
is not entered.
The allowed NMIF should be set as follows for each tool:
text interface device <NMIF> = local
NMS Integrated Command Console <NMIF> = FMIP
Architect for Passport <NMIF> = FMIP
standard Telnet <NMIF> = telnet
Note: If you want to disallow an NMIF, you can type the NMIF name
preceded by a tilde (~) character. For example, to disallow ftp, you would
type:
set Ac Userid/<userid> allowedAccess local fmip telnet
~ftp
8 Set the users 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 this
command is not entered. / is the conventional symbol for root directory.
Node security 213
Passport Operations and Maintenance Guide 4S3
9 Optionally, you may check your new userid by issuing the display
command.
display Ac Userid/<userid>
where:
<userid> is from one to eight characters in length
10 End provisioning mode.
Adding a separate userid and password for alarm collection
Use the steps outlined in Adding a userid component on page 211 to add an
additional userid and password that will allow you to collect Passport Alarms
through the FMIP Management Data Router (FMDR) server process on
Magellan Network Management System (NMS). For more information on
FMDR, see 241-6001-303, NMS Administrator Guide.
Note: For this userid, scope must be network, impact must be service and
allowed NMIF must be FMIP.
Adding an IP access component
This section explains how to add an IpAccess component. This component
contains an IP address of the device that has permission to access the node.
Each device has its own IpAccess component unless a mask is used. If a mask
is used, only one IpAccess component is required for each subnetwork. A
mask is a number in the form of an IP address that tells the node to allow all
IP addresses that belong to a certain subnetwork to access the node.
You must be in provisioning mode to perform the steps in this procedure. See
Provisioning system description on page 85 for details on how to start and
end provisioning mode.
Procedure 38
Adding an IpAccess component
1 Start provisioning mode.
2 Add an IpAccess component.
add Ac IpAccess/<IPaddress1>
where:
<IP address1> is the address of the device that requires access to the
node
214 Chapter 8
241-7001-150 4S3
Note: Ac is the abbreviation for the AccessControl component.
3 Set the mask on the IpAccess component.
set Ac IpAccess/<IPaddress1> IpAddressMask
<maskIPaddress>
where:
<IP address1> is the address of the device that requires access to the
node
<maskIPaddress> is the mask, which is a number in the form of an IP
address. The purpose of the mask is to tell the node to allow access to
the node for all IP addresses that belong to a certain subnetwork.
Note: 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 belonging to
LAN 47.208.133.xxx (dened in step 2 above; xxx would actually be
entered as 0 in step 2), to access the node. The node veries only the rst
three sets of bytes in the IP address.
Another option would be to set the mask to 255.255.0.0 to tell the node to
ignore the last two bytes in the IP address. In this case all devices
belonging to 47.208.xxx.xxx would have access to the node.
4 End provisioning mode.
Copying an existing userid for a new user
This section explains how to copy a userid and all of its attributes for a new
user. You may want to do this if you have a large number of users that will
have the same attributes; that is, where the only difference is the userid and
the password. This reduces the need to reset attributes every time you add a
new user. Once the component has been copied, only the password needs to
be changed; optionally, attributes may also be changed. All attributes are
described in Adding a userid component on page 211.
Note: This procedure can be performed only by a system administrator.
You must be in provisioning mode to perform the steps in this procedure. See
Provisioning system description on page 85 for details on how to start and
end provisioning mode.
Procedure 39
Copying an existing userid for a new user
1 Start provisioning mode.
Node security 215
Passport Operations and Maintenance Guide 4S3
2 Copy the Userid component. Make sure that the component being copied
has been activated and committed before you copy it, otherwise the copy
command will not work.
copy -s(Ac Userid/<olduserid>) -d(Ac Userid/
<newuserid>) prov
where:
-s is the source option
-d is the destination option
<olduserid> is the existing userid
<newuserid> the userid of the new user
For more information on options that can be used with the copy prov
command, see "copy prov" on page 119.
Note: Ac is the abbreviation for the AccessControl component.
3 Set the password.
set Ac Userid/<newuserid> password <password>
where:
<newuserid> the userid of the new user
<password> is from ve to eight characters in length
4 Optionally, set any attributes that need to be changed.
5 End provisioning mode.
Changing the password on an existing userid
This section explains how to change the password on an existing userid.
Optionally, attributes may also be changed. All attributes are described in
Adding a userid component on page 211.
Note: Only a user with root privileges, such as a system administrator,
can perform this task.
You must be in provisioning mode to perform the steps in this procedure. See
Provisioning system description on page 85 for details on how to start and
end provisioning mode.
Procedure 40
Changing the password of a userid
1 Start provisioning mode.
2 Set the password.
216 Chapter 8
241-7001-150 4S3
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: Ac is the abbreviation for the AccessControl component.
3 End provisioning mode.
Changing attributes on an existing userid
This section explains how to change the userid attributes of an existing Userid
component. All attributes are described in Adding a userid component on
page 211.
You must be in provisioning mode to perform the steps in this procedure. See
Provisioning system description on page 85 for details on how to start and
end provisioning mode.
Procedure 41
Changing attributes on an existing Userid component
1 Start provisioning mode.
2 Optionally, set any attributes that need to be changed. For details on
userid attributes, see Procedure 37 on page 211.
3 End provisioning mode.
Deleting an existing userid component
This section explains how to delete an existing userid. You must be in
provisioning mode to perform the steps in this procedure. See Provisioning
system description on page 85 for details on how to start and end
provisioning mode.
Procedure 42
Deleting a userid component
1 Start provisioning mode.
2 Remove the userid component.
del Ac Userid/<userid>
where:
<userid> is from one to eight characters in length
3 End provisioning mode.
217
Passport Operations and Maintenance Guide 4S3
Chapter 9
Node provisioning
This chapter provides descriptions and procedures for provisioning a Passport
node. After reading this chapter, you will be able to provision the node and
its interfaces to other nodes using a VT-100 terminal or terminal emulator.
Except where noted, descriptions and procedures are provided for operators
working with Passport through a VT-100 terminal or a terminal emulator. If
you are using Nortels proprietary Magellan Network Management System
(NMS) see 241-6001-023, NMS Architect for Passport User Guide.
Related documents
See the following documents for additional information related to node
provisioning:
241-7501-210, Passport Components
241-7001-320, Passport Call Server for Frame Relay Networks User
Guide
241-7001-803, Passport IP Routing User Guide
About the provisioning procedures in this chapter
This chapter focuses on the steps and commands necessary to provision the
node. Details on the components and attributes can be found in
241-7501-210, Passport Components.
Quick access to node provisioning procedures
To nd procedures quickly, see the following list:
"Provisioning the node name and identier" on page 221
218 Chapter 9
241-7001-150 4S3
"Determining the MAC address of a port" on page 223
"Provisioning a trunk" on page 224
"Provisioning dynamic trunk speed change" on page 227
Provisioning information in other locations
Some provisioning procedures are covered in other chapters or are in other
documents as explained below.
Provisioning new processor cards and ports
Information on how to provision processor cards and ports is described in
Processor card provisioning on page 293. To provision the CFP1, see
241-7001-170, Passport Control and Function Processor (CFP1) User
Guide. For details on logical processors (LP) and LP types, see "Logical
processors and logical processor types" on page 179.
Provisioning a service
Service provisioning is covered in the individual user guides for each service.
See "Installing and provisioning services" on page 204.
You can provision more than one service on the same V.11, V.35, DS1, E1 or
Token-Ring function processor (FP). For specific combinations of services
please see the 241-7501-100, Passport Performance Specifications
Reference Guide.
Provisioning the external address plan
Passport supports the DPN address plan manager. The DPN address plan
accepts information on the DPN addresses in a network, determines routes to
each address, and constructs packet forwarding tables so that each address
can be reached. Provisioning the external address plan is described in
241-7001-200, Passport and DPN-100 Interworking Guide.
Node provisioning 219
Passport Operations and Maintenance Guide 4S3
Provisioning the DPN Gateway
See 241-7001-200, Passport and DPN-100 Interworking Guide for
information on how to provision the DPN Gateway using the DpnGateway
component. The DpnGateway component is used to establish a connection
between a Passport node and a DPN-100 module.
Note: If the DPN end of a Passport to DPN connection terminates on a
dedicated PE286, the connection is not supported.
Prerequisites for node provisioning
Your userid must have a scope of network and an impact of configuration to
perform the procedures described in this chapter.
Note: Only users with a CID of 0 are permitted to carry out provisioning
procedures.
Before you perform any procedures in this document, read and perform the
procedures described in 241-7001-130, Passport Startup Guide.
Provisioning access before using Magellan NMS
There are three ways to access a Passport-only network using Magellan
NMS:
IP interface over virtual circuits (IPIVC)
IP interface over Frame Relay (IPIFR)
ethernet connection to an ILS network
Access must be provisioned before you can use Magellan NMS.
The IPIVC provides a connection between the Passport node and the
Magellan NMS via X.25. The IPIVC can be set up by performing the
procedures described in 241-7001-130, Passport Startup Guide. Further
details on how to provision the IPIVC are provided in Provisioning module-
wide data on page 234.
220 Chapter 9
241-7001-150 4S3
The IPIFR also provides a connection between the Passport node and the
Magellan NMS using Frame Relay. The IPIFR can be set up by performing
the procedures described in 241-7001-130, Passport Startup Guide. Further
details on how to provision the IPIFR are provided in Provisioning the
IPIFR on page 267.
A Passport ILS network can be connected to Magellan NMS via ethernet.
Details on how to provision the ethernet connection are provided in "ILS
network management via ethernet" on page 282.
Provisioning the node name, identier and region identier
This section explains how to provision the Passport node name, node
identifier and region identifier. These attributes exist under the ModuleData
component; one for each Passport node. This component comes up
automatically when a Passport node boots.
The nodeName attribute is a unique name given to each Passport node in
order to identify the node from other nodes within the network.
The node identier is a number that uniquely identies the node component
instance in the Magellan Passport autonomous network. The node identier
is used in the routing control and some data packets sent by this node to other
Passport nodes in the network.
The node identifiers for all other nodes in the network are read from the
Passport routing protocol packets.
You must be in provisioning mode to perform the steps in this procedure. See
Provisioning system description on page 85 for details on how to enter and
exit provisioning mode.
CAUTION
Node restart
Changing the node identier, node name or region
identier results in a node restart.
Node provisioning 221
Passport Operations and Maintenance Guide 4S3
The region identier attribute is used to identify the nodes that belong to a
topology region within a network. Neighbor nodes exchange region identier
values during trunk staging in order to determine whether or not they belong
to the same topology region.
Procedure 43
Provisioning the node name and identier
1 Start provisioning mode.
2 Set the Passport node identier.
set Mod nodeid <nodeid>
where:
<nodeid> can be set to any number between 1 and 4095. The node
identier must be unique for each Passport node.
Note: Mod is the abbreviation for the ModuleData component.
3 Set the Passport node name.
set Mod nodeName <NodeName>
where:
<NodeName> can be set to a 12 character ASCII string that is unique to
every Passport node in a network. It is globally available on the module.
The default is NONAME.
Note: The following characters are not permitted in the node name:
<
>
/
:
*
$ if used by itself (that is LA$ is a valid name but $ is an invalid
name)
4 Set the Passport region identier.
set Mod regionId <regionId>
5 End provisioning mode.
222 Chapter 9
241-7001-150 4S3
MAC addresses and logical processors
A media access control (MAC) terminator card supplies the control processor
(CP) with the base MAC address and the range of MAC addresses for local
area network (LAN) cards such as fiber distributed data interface (FDDI),
ethernet or token ring. A MAC address is unique for an end system in a
network. This address consists of a 12-character hexadecimal string (6 bytes)
used by a bridge, router, or between end systems.
At the factory, each Passport node is assigned a unique set of MAC addresses
consisting of a base address and a range of addresses. For each LP a set of 64
MAC addresses is assigned. Each Passport node has 1024 MAC addresses
(64 addresses X 16 LPs).
Example
If the base address of a Passport shelf is
00-20-1B-AB-CD-00, the MAC address range for the shelf is
00-20-1B-AB-CD-00 to 00-20-1B-AB-D0-FF (a range of 3FF hex i.e.
1024).
The CP divides the block of MAC addresses so that each LP has 64 MAC
addresses. The first 64 MAC addresses are assigned to the CP (LP/0), the next
64 MAC addresses are assigned to LP/1, and so on. Each LP can have a main
card and optionally, a spare card. If the main card fails, it automatically
switches to the spare card and retains the same MAC addresses.
MAC addresses are assigned to all the LPs of a shelf, regardless of the LP
type. Only the FDDI, ethernet and token ring components support MAC
addressing. The MAC addresses cannot be changed through provisioning
except for the token ring component. The MAC address for the token ring
component can be automatically set by the CP or locally by the user. To set
the MAC address locally, see Assigning a local MAC address for a token
ring port on page 223.
To determine the MAC addresses of a LP, multiply the LP number by 0x40
(64 decimal) and add the shelfs base MAC address.
Node provisioning 223
Passport Operations and Maintenance Guide 4S3
Example
If the base address of a Passport shelf is
00-20-1B-AB-CD-00, the base MAC address for LP 4 is
00-20-1B-AB-CD-00 + (0x40 * 4). Add 0x3F to the LP base address to
obtain the range of MAC addresses for the LP. In this case the range is
00-20-1B-AB-CE-00 to 00-20-1B-AB-CE-3F.
When a LAN card is provisioned, a MAC address is assigned to the ports
macAddress attribute. Port 0 is assigned the lowest address in the address
range for the associated LP, Port 1 is assigned the second lowest address and
so on.
Example
If the base address of a 16-slot Passport shelf is
00-20-1B-AB-CD-00, the MAC address for LP 4 Port 5 is
00-20-1B-AB-CD-00 + (0x40 * 4) + 5. In this case the MAC address is
00-20-1B-AB-CE-05.
Procedure 44
Determining the MAC address of a port
1 To determine the specic address of a provisioned functional processor
port using an operator command, enter:
d lp/<n> <port>/<m> macAddress
where:
<n> is the number of the logical processor and can be between 0 and 15.
Use the display command to see which cards are currently congured.
<port> can be FDDI, EN, or TR.
<m> can be any number between 0 and 5 for EN, between 0 and 3 for TR,
and 0 for FDDI.
Note: On a CFP1, the values for Ethernet (EN) or Token Ring (TR) ports
can be 4 or 5.
Procedure 45
Assigning a local MAC address for a token ring port
1 To assign a specic MAC address to a provisioned functional processor
port, enter the following provisioning command:
set lp/<n> tokenring/<m> nodeAddress <xx-xx-xx-xx-xx-
xx>
224 Chapter 9
241-7001-150 4S3
where:
<n> is the number of the logical processor and can be between 0 and 15.
Use the display command to see which cards are currently congured.
<m> can be any number between 0 and 3 for TR
<xx-xx-xx-xx-xx-xx> is the user defined MAC address.
Note: On a CFP1, the values for Token Ring (TR) ports can be 4 or 5.
Provisioning the trunks
This section explains how to add a new trunk and how to set trunk attributes.
It covers provisioning Unacknowledged Trunks for connectionless routing
only. If you are provisioning the trunks to carry PORS trafc, see:
241-7001-400, Passport Voice Transport User Guide
241-7001-510, Passport HDLC Transparent Data Service User Guide
241-7001-520, Passport Bit Transparent Data Service User Guide.
If you are provisioning ATM-based Logical Trunks, see 241-7001-710,
Passport ATM Adaptation: Logical Trunks User Guide.
You must be in provisioning mode to perform the steps in this procedure. See
Provisioning system description on page 85 for details on how to enter and
exit provisioning mode.
Procedure 46
Provisioning a trunk
1 Start provisioning mode.
2 Provision the LPs, cards, and ports. The provisioning of these hardware
components is described in Processor card provisioning on page 293,
or, in the case of the CFP1, in 241-7001-170, Passport Control and
Function Processor (CFP1) User Guide.
3 Add a trunk.
add trunk/<n>
where:
<n> is the instance number of the trunk between 0 and 65535
Note: The Trunk component provides the node-to-node connection. This
component must be provisioned on both ends of the connection, that is,
on both Passport nodes.
Node provisioning 225
Passport Operations and Maintenance Guide 4S3
4 Select the link protocol.
add trunk/<n> <protocol>
where:
<n> is the instance number of the trunk between 0 and 65535
<protocol> is Unacknowledged or atm. The Unacknowledged
component provides a Layer 2 protocol that adds the minimum amount of
overhead to data on the link. The Framer component is added
automatically to the selected link protocol component.
Note 1: The Framer component should have the value of the
framingType attribute set to interrupting if a PathAdministrator component
is provisioned.
Note 2: For further information on ATM provisioning for trunks, see 241-
7001-710, Passport ATM Adaptation: Logical Trunks User Guide.
5 Dene the path administrator (optional).
add trunk/<n> pa
where:
<n> is the instance number of the trunk between 0 and 65535
Note: The path administrator allows the trunk to support PORS trafc.
6 Link the Framer component to the required Port (for DS3, E3, V35, X21,
or CFP1 function processors) or Channel component (if using DS1 or E1).
For DS3, E3, V35, X21, or CFP1 cards, type:
set trunk/<n> <protocol> framer interfaceName lp/<p>
<port>/<m>
where:
<n> is the instance number of the trunk between 0 and 65535
<protocol> is Unacknowledged
<port> is DS3, E3, V35 or X21
<m> is the port number
<p> is the logical processor number
For DS1 or E1 cards, type:
set trunk/<n> <protocol> framer interfaceName lp/<p>
<port>/<m> channel/<c>
where:
<n> is the instance number of the trunk between 0 and 65535
<protocol> is Unacknowledged
<port> is DS1 or E1
<m> is the port number
226 Chapter 9
241-7001-150 4S3
<c> is the channel instance
<p> is the logical processor number
Note: DS1V, E1V, J2MV, DS1C, E1C, and DS3C function processors do
not support trunking.
7 Set the framing type.
set trunk/<n> <protocol> framer framingType <type>
where:
<n> is the instance number of the trunk between 0 and 65535
<protocol> is Unacknowledged
<type> is interrupting if the trunk is for a PORS service, and hdlc for any
other type of service
8 If you need notication of Passport Trunk utilization over a provisioned
bandwidth threshold, set the trunk utilization alarm threshold mechanism.
Provision utilization thresholds for each Unack Framer component.
set trk/<n> unack framer linkUtilAlarmStatus <status>
set trk/<n> unack framer minorLinkUtilAlarmThreshold
<value>
set trk/<n> unack framer majorLinkUtilAlarmThreshold
<value>
set trk/<n> unack framer
criticalLinkUtilAlarmThreshold <value>
where:
<n> is the instance number of the trunk between 0 and 65535
linkUtilAlarmStatus <status> is enabled or disabled
minorLinkUtilAlarmThreshold <value> species the minor alarm
threshold percentage (0% to 100%).
majorLinkUtilAlarmThreshold <value> species the major alarm
threshold percentage (0% to 100%).
criticalLinkUtilAlarmThreshold <value> species the critical
alarm threshold percentage (0% to 100%).
Note 1: The Trunk utilization alarm mechanism is turned off by default.
Note 2: An alarm threshold of 100% disables that threshold.
9 End provisioning mode.
Node provisioning 227
Passport Operations and Maintenance Guide 4S3
Provisioning dynamic trunk speed change
This section explains how to provision the dynamic trunk speed change
feature. This feature consists of the following applications:
ISDN dial backup - resumes connectivity between two Passport nodes
when a leased line failure occurs
ISDN bandwidth on demand (BWoD) - enables a Passport node to adapt
to additional bandwidth when the capacity of the dedicated facility is
exceeded
inverse multiplexing - enables a trunk to support more than four physical
connections between adjacent Passport nodes
For a description of this feature, see 241-7001-110, Passport General
Description.
The dynamic trunk speed change feature also supports Passport trunking on
the integrated Passport Inverse Multiplexing for ATM (IMA). For details and
provisioning procedures for IMA, see 241-7001-710, Passport ATM
Adaptation: Logical Trunks User Guide.
You must be in provisioning mode to perform the steps in this procedure. See
Provisioning system description on page 85 for details on how to enter and
exit provisioning mode.
ISDN dial backup
In the ISDN dial backup application, the trunk speed change reporting
mechanism is enabled. Trunk speed variations are propagated to the routing
systems.
When the leased line fails, the trunk either disables and re-enables with a
small amount of bandwidth or is informed of a sudden bandwidth decrease.
The trunk reports the speed decrease immediately to the routing system; it
reacts to the speed decrease as soon as possible to avoid severe traffic
congestion.
The ISDN devices can be programmed to automatically dial up a number of
lines at a time until an expected total number of lines are dialed up. In these
cases, the dialed up speed increases in steps. To avoid these transient speed
228 Chapter 9
241-7001-150 4S3
updates from overloading the routing system, the trunk speed change
reporting mechanism allows you to customize the granularity and the
frequency of the speed increase updates.
Reporting speed changes
The dynamic trunk speed change feature has seven provisionable threshold
levels for reporting the speed changes. In the ISDN dial backup application,
the trunk runs in one of two modes: normal speed and backup speed.
If only the backup speed is provisioned as the threshold level, the following
speed increases are reported to the routing system:
when the expected backup speed is obtained
when the normal speed provided by the leased line is obtained
The current measured speed is reported to the routing system if the next
threshold level to the last reported speed, or the expected normal speed is
reached and remains above that level after the hold-off time.
Procedure 47
Provisioning ISDN dial backup
1 Start provisioning mode.
2 Provision the trunk according to Provisioning a trunk on page 224.
3 Select a threshold for reporting a speed change.
set trunk/<n> speedReportingThresholds <expected-
speed-of-backup-lines, expected-speed-of-leased-line>
where:
<n> is the instance number of the trunk
4 Set the period for delaying the speed change report. Default is 30
seconds.
set trunk/<n> speedReportingHoldOff <30 seconds>
where:
<n> is the instance number of the trunk
5 If required, the speed change alarms can be set to indicate when the
third-party device is in backup mode.
set trunk/<n> lowSpeedAlarmThreshold <expected-speed-
of-leased-line>
Node provisioning 229
Passport Operations and Maintenance Guide 4S3
If the measured speed decreases below the leased line speed, the low-
speed alarm is set indicating that the leased line failure has occurred and
the third-party device is either in backup mode, or it is dialing up the
backup lines. The alarm is cleared when the measured speed returns to
the expected leased line speed.
set trunk/<n> highSpeedAlarmThreshold <4294967295>
where:
<n> is the instance number of the trunk
Note: No high-speed alarm is set due to a speed increase.
Scheduled ISDN bandwidth on demand
In the scheduled ISDN bandwidth on demand (BWoD) application, the trunk
speed change reporting mechanism is enabled. Trunk speed variations are
propagated to the routing systems.
The ISDN devices can be programmed to automatically dial up a number of
lines at a time until an expected total number of lines are dialed up. In this
application, the speed increases in steps. To avoid transient speed updates
from overloading the routing system, the trunk speed change reporting
mechanism allows you to customize the granularity and frequency of the
speed increase updates.
Reporting speed changes
In the scheduled ISDN BWoD application, the trunk runs in one of two
modes: normal speed and peak speed. A maximum of seven values can be
specied through the speedReportingThresholds attribute. In the following
procedure, two thresholds (the expected speed of leased line and the expected
peak speed) are provisioned.
Procedure 48
Provisioning scheduled ISDN BWoD
1 Start provisioning mode.
2 Provision the trunk according to Provisioning a trunk on page 224.
3 Select a threshold for reporting a speed change.
set trunk/<n> speedReportingThresholds <expected-
speed-of-leased-line, expected-peak-speed>
where:
<n> is the instance number of the trunk
230 Chapter 9
241-7001-150 4S3
4 Set the period for delaying the speed change report. Default is 30
seconds.
set trunk/<n> speedReportingHoldOff <30 seconds>
where:
<n> is the instance number of the trunk
5 If required, the speed change alarms can be set to indicate when the
third-party device is using the BWoD mode of operation.
set trunk/<n> highSpeedAlarmThreshold <expected-speed-
of-leased-line>
If the measured speed increases above the leased line speed, the high-
speed alarm is set indicating that the third-party device is using extra
bandwidth. The alarm is cleared when the measured speed returns to the
expected leased line speed.
set trunk/<n> lowSpeedAlarmThreshold <0>
where:
<n> is the instance number of the trunk
Note: No alarm is set due to a speed decrease.
Dynamic ISDN bandwidth on demand
In the dynamic ISDN bandwidth on demand (BWoD) application, the trunk
speed change reporting mechanism is disabled. Trunk speed variations are
not propagated to the routing systems.
If it is required to use the speed change alarms to indicate when the third-party
device is in the BWoD mode, the threshold alarms can be provisioned as
follows:
Procedure 49
Provisioning alarms for dynamic ISDN BWoD
1 Start provisioning mode.
2 Provision the trunk according to Provisioning a trunk on page 224.
3 If required, the speed change alarms can be set to indicate when the
third-party device is using the BWoD mode of operation.
set trunk/<n> highSpeedAlarmThreshold <expected-speed-
of-leased-line>
If the measured speed increases above the leased line speed, the high-
speed alarm is set indicating that the third-party device is using extra
Node provisioning 231
Passport Operations and Maintenance Guide 4S3
bandwidth. The alarm is cleared when the measured speed returns to the
expected leased line speed.
set trunk/<n> lowSpeedAlarmThreshold <0>
where:
<n> is the instance number of the trunk
Note: No alarm is set due to a speed decrease.
ISDN dial backup with scheduled BWoD
In this application, the trunk speed change reporting mechanism is enabled.
Trunk speed variations are propagated to the routing systems.
Reporting speed changes
In the ISDN dial backup with scheduled BWoD application, the trunk runs in
one of three modes: normal speed, peak speed, and backup speed. The
expected backup speed, expected speed of leased lines, and the expected peak
speed are provisioned as the threshold values.
Only three speed increases are reported:
when the expected backup speed is obtained
when the normal speed provided by the leased line is obtained
when the expected peak speed is obtained
A maximum of seven threshold values can be provisioned for the
speedReportingThresholds attribute.
Procedure 50
Provisioning ISDN dial backup with scheduled BWoD
1 Start provisioning mode.
2 Provision the trunk according to Provisioning a trunk on page 224.
3 Select a threshold for reporting a speed change.
set trunk/<n> speedReportingThresholds <expected-
backup-speed, expected-speed-of-leased-line,
expected-peak-speed>
where:
<n> is the instance number of the trunk
4 Set the period for delaying the speed change report. Default is 30
seconds.
232 Chapter 9
241-7001-150 4S3
set trunk/<n> speedReportingHoldOff <30 seconds>
where:
<n> is the instance number of the trunk
5 If required, the speed change alarms can be set to indicate when the
third-party device is using either the backup or the scheduled BWoD
mode of operation.
set trunk/<n> lowSpeedAlarmThreshold <expected-speed-
of-leased-line>
set trunk/<n> highSpeedAlarmThreshold <expected-speed-
of-leased-line>
where:
<n> is the instance number of the trunk
If the measured speed decreases below the leased line speed, the low
decrease alarm is set indicating that a leased line failure has occurred
and the third-party device is either in backup mode or it is dialing up the
back up lines. The alarm is cleared when the measured speed returns to
the expected leased line speed.
If the measured speed increases above the leased line speed, the high-
speed alarm is set indicating that the third party device is using extra
scheduled bandwidth. The alarm is cleared when the measured speed
returns to the expected leased line speed.
ISDN dial backup with dynamic BWoD
In the dial backup application, the trunk speed change reporting mechanism
is enabled. Trunk speed variations are propagated to the routing systems. In
the dynamic BWoD application, the trunk speed change reporting mechanism
is disabled. Trunk speed variations are not propagated to the routing systems.
Procedure 51
Provisioning ISDN dial backup with dynamic BWoD
1 Start provisioning mode.
2 Provision the trunk according to Provisioning a trunk on page 224.
3 Select a threshold for reporting a speed change.
set trunk/<n> speedReportingThresholds <expected-
backup-speed, expected-speed-of-leased-line>
where:
<n> is the instance number of the trunk
Node provisioning 233
Passport Operations and Maintenance Guide 4S3
4 Set the period for delaying the speed change report. Default is 30
seconds.
set trunk/<n> speedReportingHoldOff <30 seconds>
where:
<n> is the instance number of the trunk
5 If required, the speed change alarms can be set to indicate when the
third-party device is using either the backup or the dynamic BWoD mode
of operation.
set trunk/<n> lowSpeedAlarmThreshold <expected-speed-
of-leased-line>
set trunk/<n> highSpeedAlarmThreshold <expected-speed-
of-leased-line>
where:
<n> is the instance number of the trunk
If the measured speed decreases below the leased line speed, the low-
speed alarm is set indicating that a leased line failure has occurred and
the third-party device is either in backup mode or it is dialing up the back
up lines. The alarm is cleared when the measured speed returns to the
expected leased line speed.
If the measured speed increases above the leased line speed, the high-
speed alarm is set indicating that the third party device is using extra
bandwidth that is dialed up dynamically to accommodate the trafc peaks.
The alarm is cleared when the measured speed returns to the expected
leased line speed.
Inverse multiplexing
In the inverse multiplexing application, the trunk speed change reporting
mechanism is enabled. Trunk speed variations are propagated to the routing
systems.
Procedure 52
Provisioning inverse multiplexing
1 Start provisioning mode.
2 Provision the trunk according to Provisioning a trunk on page 224.
3 Set the threshold for reporting the speed change.
set trunk/<n> speedReportingThresholds <level1,
level2, level3, expected-normal-bandwidth>
234 Chapter 9
241-7001-150 4S3
where:
<n> is the instance number of the trunk
4 Set the period for delaying the speed change report. Default is 30
seconds.
set trunk/<n> speedReportingHoldOff <30 seconds>
5 If required, the speed change alarms can be set to indicate when the
third-party device experiences facility problems.
set trunk/<n> lowSpeedAlarmThreshold <expected-normal-
bandwidth>
If the measured speed decreases below the expected normal bandwidth,
the low-speed alarm is set indicating a facility problem. The alarm is
cleared when the measured speed returns to the expected normal speed.
set trunk/<n> highSpeedAlarmThreshold <4294967295>
where:
<n> is the instance number of the trunk
No high-speed alarm is set due to a speed increase.
Provisioning module-wide data
Module-wide data is used to define a number of general characteristics for
systems on a module (node). Module-wide attributes exist under the
ModuleData component and VirtualCircuitSystem component (an optional
subcomponent of the ModuleData component).
All nodes across a Passport subnet must have the same values for all attributes
in order to communicate with each other (with the exception of the following
attributes, which can have the same values or different values:
callSetupTimer, callRetryTimer, and delaySubnetAcks).
At start-up time, ModuleData attributes (nodeId, nodeName, and namsId) are
provisioned using the Passport StartUp software.
The set of attributes existing under the VirtualCircuitSystem component are
not provisioned during start-up, but are assigned default values. Although
defaults exist, you may want to customize the attributes to better suit the
requirements of the network. Values for these attributes vary according to
users requirements, therefore this document does not provide detailed
procedures on what values you should provision for them.
Node provisioning 235
Passport Operations and Maintenance Guide 4S3
If you do decide to reprovision module-wide values, do so with extreme
caution. Call Nortel for assistance if necessary.
Note: Only the network administrator can provision the ModuleData
and VirtualCircuitSystem components.
CAUTION
Risk of data loss
Reprovisioning module-wide attributes can cause the
node to become isolated from other nodes in the
network. Changing provisioning data can lead to loss of
data as a result of change in data ow.
236 Chapter 9
241-7001-150 4S3
237
Passport Operations and Maintenance Guide 4S3
Chapter 10
Network management connectivity
provisioning
This chapter provides an overview of Passport NMS connectivity options and
describes how to provision a Passport node for network management
functions via the following connections:
IP interface over VC
IP interface over Frame Relay
ILS network management via ethernet
Quick access to provisioning procedures
To nd procedures quickly, see the following list:
for IPIVC:
"Provisioning the IPIVC using a text interface device" on page 247
for IPIFR:
"Deleting the IPIVC feature and component" on page 268
"Provisioning the IPIFR on either an edge- or internal- Passport
node using a text interface device" on page 271
"Provisioning subsequent LCNs, for connectivity to additional
management stations" on page 273
"Provisioning Frame Relay user-to-network access for NMS on the
edge Passport node" on page 274
"Provisioning a static IP route for a non-directly connected IP
network" on page 279
238 Chapter 10
241-7001-150 4S3
"Provisioning a default route for path redundancy" on page 282
for ILS network management via ethernet:
Provisioning an ethernet connection to an ILS-only network for
network management on page 284
"Provisioning NMS workstation 1 to manage the ILS network" on
page 288
"Provisioning NMS workstation 1 to additionally manage the non-
ILS network" on page 288
"Provisioning an IPIFR static route (for Passport 3)" on page 289
"Provisioning an IPIFR default route (for Passport 4)" on page 289
"Provisioning NMS workstation 2 to additionally manage the ILS-
only network" on page 291
Passport NMS connectivity options
Passport NMS connectivity provides an IP connection between management
devices (MDs) and Passport nodes. A Passport node can function as either a
simple IP endstation host or an IP router via the following subsystems:
IPI subsystem: a simple, low cost, non-routing / non-forwarding IP
interface to a Passport node (basically providing IP endstation host
functionality). The IPI subsystem provides the following features:
simple static IP routing
static ARP
path redundancy between itself and attached IP routers (that is, the
IP network)
a choice of link layer interfaces:
X.25 DCE
frame relay DCE running RFC1490 (multi-protocol
interconnect over frame relay)
VR IP subsystem: a routing- / forwarding- capable IP interface to a
Passport node (basically providing IP router functionality). The VR IP
subsystem provides the following features:
Network management connectivity provisioning 239
Passport Operations and Maintenance Guide 4S3
a choice of IP routing, address resolution, and related protocols:
IARP, static ARP entries
static IP routes, RIP / RouteD, OSPF, EGP,
with exible import and export policies on distribution of
routing information
exible IP forwarding policies
a choice of media / link layer IP protocol ports:
ethernet, FDDI, token ring
ATM (RFC1483)
Passport trunks via VNS
frame relay (RFC1490), X.25
Note: A Passport node should use either one of the IP subsystems, but
not both.
Conceptual view of NMS connectivity
Figure 22 provides a conceptual view of Passport NMS connectivity. In this
diagram the following conventions are used:
Management Devices (MDs) are workstations running the management
applications
Management Sites (MSs) are, typically, geographically dispersed
clusters of one or more MDs. The MDs within an MS may be networked
together with LANs. The MSs may be networked together with WANs.
Management Networks (MNs) are LAN/WAN networks of MSs/MDs;
none of these are necessarily Passport nodes
Passport network is the Passport network to be managed; it is not
necessarily an IP Network
edge Passport nodes are the nodes which have a link connection to the
MN (that is, the MN interface). Typically there are 2-5 edge Passport
nodes. These (optionally) can be IP routers (that is, using VR IP).
240 Chapter 10
241-7001-150 4S3
internal Passport nodes are the nodes which have a Passport network
connection to the MN. Typically these constitute 90% of the nodes in the
Passport network. If VR is to be used on an internal node for data
reasons, then use VR IP on the node for network management.
Otherwise, these nodes should use IPI, to reduce engineering costs and
provisioning steps. The internal and edge nodes of a Passport network
may be a mixture of VR IP and IP Passport nodes.
Figure 22
Conceptual view of Passport NMS connectivity
Passport Network
Management Network (MN)
MN interface
WAN
internal
internal
internal
edge
internal
edge
edge
MS
MD
MD
MD
MS
MD
WAN
MS
MD
MD
MD
Passport node
Network management connectivity provisioning 241
Passport Operations and Maintenance Guide 4S3
Advantages of using VR IP on edge Passport nodes
Consider the following points when deciding between provisioning an edge
Passport node with either an IPI or VR IP subsystem:
VR IP provides a large choice of physical and link layer interfaces which
the Passport network can support for in-band management connectivity.
For example, ethernet, FDDI, token ring, ATM (RFC1483), frame relay
(RFC1490) and X.25.
VR IP embeds the functionality of the external IP router (which is
providing the LAN for the MDs) into the Passport network. This
provides a more integrated and network manageable solution than having
different products in the network.
Service and hardware requirements
Table 25 provides an overview of service configurations and hardware
requirements for Passport node connectivity options.
Table 25
Service and hardware requirements
Management
Network
Interface
Passport
Network
Transport
Media
Type of
Passport
Node
Service and Hardware
Requirements
Comments
Frame Relay Frame Relay IPI edge
Passport
FP: FrUni port
FP: Trunk port
CP: ipiFr
Trunk port is shared
with other data
IPI internal
Passport
FP: Trunk port
CP: ipiFr
VR IP
internal
Passport
FP: FrDte vFramer,
FrUni vFramer
FP: Trunk port
CP: VR IP
(Sheet 1 of 4)
242 Chapter 10
241-7001-150 4S3
X.25 X.25 IPI edge
Passport
DPN module
FP: DpnGateway port
FP: Trunk port
CP: ipiVc
Trunk port is shared
with other data
IPI internal
Passport
FP: Trunk port
CP: ipiVc
VR IP
internal
Passport
DPN module
FP: X25Dte port
CP: VR IP
Table 25 (continued)
Service and hardware requirements
Management
Network
Interface
Passport
Network
Transport
Media
Type of
Passport
Node
Service and Hardware
Requirements
Comments
(Sheet 2 of 4)
Network management connectivity provisioning 243
Passport Operations and Maintenance Guide 4S3
Ethernet VNS VR IP edge
Passport
FP: Ethernet port
FP: Trunk port, VNS
[FP: ILS Fwdr]
CP: VR IP
Trunk port is shared
with other data
ILS Fwdr card is only
required if atmTrunks
are used for VNS
VR IP
internal
Passport
FP: Trunk port, VNS
[FP: ILS Fwdr]
CP: VR IP
Frame Relay VR IP edge
Passport
FP: Ethernet port
FP: FrDte vFramer,
FrUni vFramer
FP: Trunk port
CP: VR IP
Trunk port is shared
with other data
IPI internal
Passport
FP: Trunk port
CP: ipiFr
VR IP
internal
Passport
FP: FrDte vFramer,
FrUni vFramer
FP: Trunk port
CP: VR IP
Table 25 (continued)
Service and hardware requirements
Management
Network
Interface
Passport
Network
Transport
Media
Type of
Passport
Node
Service and Hardware
Requirements
Comments
(Sheet 3 of 4)
244 Chapter 10
241-7001-150 4S3
IP interface over VC
IP Interface over Virtual Circuit (IPIVC) provides an X.25 connection
between an NMS workstation and a Passport node via a Passport Virtual
Circuit. IPIVC connections are illustrated in Figure 23.
Note: A DPN module (possibly part of a DPN network) provides the
X.25 interface to the management device.
The IPIVC must first be provisioned via an ASCII-based terminal that is
connected to a Passport node by a local interface. Thereafter, an external
network management system such as Magellan NMS can establish a
connection to the node.
Ethernet ATM VR IP edge
Passport
FP: Ethernet port
FP: AtmMpe,
Atmlf port
FP: ILS Fwdr
CP: VR IP
VR IP
internal
Passport
FP: AtmMpe,
Atmlf port
FP: ILS Fwdr
CP: VR IP
Table 25 (continued)
Service and hardware requirements
Management
Network
Interface
Passport
Network
Transport
Media
Type of
Passport
Node
Service and Hardware
Requirements
Comments
(Sheet 4 of 4)
Network management connectivity provisioning 245
Passport Operations and Maintenance Guide 4S3
Figure 23
NMS workstation access to Passport network over X.25 SVCs
Further details on how to provision the IPIVC are provided in Provisioning
the IPIVC using a text interface device on page 247. Refer also to 241-7001-
130, Passport Startup Guide for information on provisioning your initial link
to NMS.
X.25
DPN GateWay
Passport network
NMIF
IP
TCP
Ethernet LAN
NMIF
NMIF
Passport
node
NMS
DPN
Network
IP default route
(the only SVC of IPIVC
which can route to a network
of NMS workstations)
SVCs
NMS
NMS 1
NMS 2
NMS 3 NMS 4
X.25
X.25
UDP
TELNET FMIP FTP SNMP
IPIVC
NMIF
246 Chapter 10
241-7001-150 4S3
IPIVC features
IPIVC supports the following features:
UDP datagram and TCP connection-oriented transport for network
management functions
direct connection between an NMS workstation and a Passport node via
an X.25 SVC and a DPN network
indirect connection between a network of NMS workstations and a
Passport node via an IP-routing-capable device The IP-routing-capable
device has an X.25 connection to the Passport node and an arbitrary link
layer connection (for example, ethernet) to the NMS workstations
Note: This indirect connection is only supported over the IP default
route.
IP path redundancy to NMS workstations, providing an IP default route
up to 24 direct connections
IPIVC components and attributes
The IPIVC interface is dened by the following components:
IPIVC component: The IPIVC component allows external network
management devices to access the node. The IPIVC component contains
two provisionable attributes, the IPAddress and the
maximumNumberOfLCN. The IPIVC must have a unique IP address that
represents the address of the network interface and a unique DNA for
setting up the virtual circuit (VC).
DNA component: The DNA component contains a subset of all attributes
that apply to a VC. The DNA attribute of each Passport node must be
unique in the network.
CUG component: The CUG component contains attributes that dene
options associated with national or international closed user group
(CUG) IDs. The CUG is used to group a number of DNAs. The CUG
provides security by ensuring that only authorized Magellan NMSs (with
the proper CUG) are allowed access. In other words, the external
network management systems that initiate a connection to the node
(through the IPIVC) must all be members of the CUG provisioned on the
IPIVC.
Network management connectivity provisioning 247
Passport Operations and Maintenance Guide 4S3
LCN component: The LogicalChannelNumber (LCN) component is a
dynamic subcomponent of the IPIVC component. The LCN is
responsible for the logical connection with the VC. There can be up to 24
instances of the LCN component on the IPIVCin other words, the
IPIVC can support up to 24 VCs. The instance value of this component
ranges from 16 to 39.
DefaultRoute component: The DefaultRoute (DR) component is an
optional subcomponent of the IPIVC component. The default route is the
predened IP route used when no specic logical connection has been
assigned from the Passport to a given IP address. The attributes in this
component are the IPAddress and the DNA of the remote end to which the
default route is to be directed.
The default route is also used to access Magellan NMS workstations that
are indirectly connected to the DPN or Passport network via an IP-
routing-capable device.
Provisioning the IPIVC
You must be in provisioning mode to perform the steps in this procedure. See
Provisioning system description on page 85 for details on how to enter and
exit provisioning mode.
Prerequisites
To set up the initial IPIVC link, perform the procedures described in
241-7001-130, Passport Startup Guide. Once the initial IPIVC is
provisioned, you can perform further provisioning, if required, using the
following procedure.
Procedure 53
Provisioning the IPIVC using a text interface device
1 Start provisioning mode.
To provision the initial IPIVC, CP, FP, and DPN Gateway, perform the
procedures described in 241-7001-130, Passport Startup Guide. Further
details on provisioning a port are provided in Processor card
provisioning on page 293. Further details on how to provision a DPN
Gateway are provided in 241-7001-200, Passport and DPN-100
Interworking Guide.
2 Set the IP address of the IPIVC interface.
set IpiVc ipAddress <IP Address>
248 Chapter 10
241-7001-150 4S3
where <IP Address> is unique for each IPIVC. This IP address cannot
be the same as the IP address of IPIVCs on other nodes, or the IP
address of the remote device. The IP address has a default value of
0.0.0.0; which must be changed to any number higher than 0.0.0.0 up to
255.255.255.255. The IP address cannot be set to 0.0.0.0. Once the IP
address is changed, all existing X.25 calls using this IPIVC are cleared.
3 Set the DNA of the IPIVC interface.
set IpiVc dna dataNetworkAddress <DN Address>
where:
<DN Address> is a unique customer dened number that can contain up
to 14 digits. This DNA must be unique in the network.
4 Set the NumberingPlanIndicator (NPI) component.
set IpiVc dna npi <NPI>
where:
<NPI> is either x121 or e164
5 Set the CUG type.
set IpiVc dna cug type <cugtype>
where:
<cugtype> is either Ncug (a national CUG) or Icug (an international
CUG)
6 Set the DNIC of the CUG.
set IpiVc dna cug Dnic <cugDnic>
How the DNIC is set depends on the type of CUG provisioned. If the CUG
type is set to Icug, this eld must be given the appropriate value. If the
CUG type is set to Ncug, this eld remains all zeros.
7 Set the CUG interlock code.
set IpiVc dna cug interlockCode <code>
where:
<code> species the interlock code of a national or international CUG
call. The code must be the same as the code assigned to the group of
Magellan NMSs authorized to access the node. The code attribute can be
set to any number between 0 and 65535.
8 Optionally, add the default route (DR). Ensure that the remote default IP
address and the default DNA are both provisioned.
add IpiVc Dr
Network management connectivity provisioning 249
Passport Operations and Maintenance Guide 4S3
The default route (DR) is a user-dened VC that is used if the IP route for
a given IP address is unknown. A default route should be added to each
node. A maximum of one default route is allowed. The default route is also
used to access Magellan NMS workstations that are indirectly connected
to the DPN or Passport network via an IP-routing-capable device.
9 Set the remote IP address.
set IpiVc Dr callingIpAddress <IP Address>
where:
<IP Address> is the remote address (where the X.25 call is originated)
of the default route. The IP address has a default value of 0.0.0.0 which
must be changed to any number higher than 0.0.0.0 up to
255.255.255.255. This IP address cannot be set to 0.0.0.0. This IP
address must be unique; that is, it cannot be the same as the IP address
assigned to the IPIVC.
10 Set the remote DNA.
set IpiVc Dr callingDataNetworkAddress <DN Address>
where:
<DN Address> contains up to 14 digits. This DNA cannot be the same
as the DNA of the IPIVC.
When the remote DNA is changed, IPIVC takes one of the following
actions:
If no VC has been set up using the old remote DNA, the IPIVC
replaces the old attribute value of the remote DNA with the new one.
It then checks whether a VC has already been established using the
new attribute value as the destination DNA. If such a VC exists, this
VC is marked as the default VC. Once a default VC is located, IPIVC
stops searching.
If a VC has been set up using the old remote DNA, the IPIVC stops
using this VC as the default VC. It then proceeds with the actions
described in the rst scenario described above.
11 Set the remote NPI.
set IpiVc Dr callingNPI <NPI>
where:
<NPI> is either x121 or e164.
250 Chapter 10
241-7001-150 4S3
IP interface over Frame Relay
IP Interface over Frame Relay (IPIFR) connects a Magellan NMS
workstation to a Passport node via Passport Frame Relay service. Figure 24
illustrates IPIFR connections.
A Passport node can only support one of either IPIFR or IPIVC. The two
features cannot simultaneously co-exist on a Passport node. This means that
multiple NMS workstations can only manage the same Passport node if they
all access the node via the same service, which can be either DPN X.25 or
Passport Frame Relay.
Figure 24
NMS workstation access to Passport network over Frame Relay VC
Passport network
Passport
node
NMS 2
NMS 3
NMS 1
Frame
Ethernet LAN
NMS 4 NMS 5
IP Router
Ethernet LAN
Passport
Network
Relay
PVCs
IPIFR
FRUNI/3
FRUNI/2
FRUNI/1
NMS 6
NMIF
IP
TCP
NMIF
NMIF
UDP
TELNET FMIP FTP SNMP
NMIF
Network management connectivity provisioning 251
Passport Operations and Maintenance Guide 4S3
IPIFR features
IPIFR supports the following features:
UDP datagram and TCP connection-oriented transport for network
management functions
direct connection between an NMS workstation and a Passport node via
a Frame Relay Permanent Virtual Circuit (PVC)
Note: Combined with the Passport Call Router feature, IPIFR provides
a stand-alone Passport-node-only Frame Relay network. Refer to the
following documents:
241-7001-320, Passport Call Server for Frame Relay Networks
User Guide
241-6001-100, NMS Installer Guide
241-6001-303, NMS Administrator Guide
indirect connection between a network of NMS workstations and a
Passport node via an IP-routing-capable device (for example an IP router,
Frame Relay Access Device (FRAD), or NMS workstation running an IP
routing daemon) The IP-routing-capable device has a frame relay
connection to the Passport node and an arbitrary link layer connection
(for example, ethernet) to the NMS workstations
the indirect connections are provisioned using static IP routes. The
following types of IP routes are supported:
host
subnetwork
network
This provides a minimum level of IP routing. It also reduces the
amount of provisioning required for NMS workstation connectivity,
compared to directly connecting all of the NMS workstation hosts to
a Passport network.
Note: The direct and indirect connections are not mutually exclusive
congurations. A workstation can simultaneously be connected to the
network directly and indirectly.
252 Chapter 10
241-7001-150 4S3
improved IP path redundancy to NMS workstations, providing a backed-
up IP default route
up to 24 direct or network connections
IPIFR compliance to standards
RFC1294 describes an encapsulation method for carrying network
interconnect trafc over a frame relay backbone. IPIFR complies to RFC1294
as follows:
If the rst two octets in a data packet received from a Frame Relay PVC
are 03 CC, the network layer protocol is dened as IP. The rst two
octets are removed and the rest of the packet is forwarded to an IP device.
Otherwise, if the rst two octets are not 03 CC, the packet is dropped.
Octets 03 CC are inserted at the beginning of a data packet that is sent
to a Frame Relay PVC to dene the network layer protocol as IP.
IPIFR components and attributes
The IPIFR interface is dened by the following components:
IPIFR component: The IPIFR component allows external network
management devices to access the node. The IPIFR component contains
three provisionable attributes, ipAddress, subnetMask, and
maximumNumberOfLCN. The IPIFR must have a unique IP address that
represents the address of the network interface and a unique DNA for
setting up the VC.
DNA component: The DNA component contains a subset of all attributes
that apply to all VCs. The dataNetworkAddress attribute of each Passport
node must be unique in the network.
LCN component: The LogicalChannelNumber (LCN) component is a
subcomponent of the IPIFR component. There can be up to 24 instances
of the LCN component on the IPIFR, allowing the IPIFR to support up to
24 VCs. The instance value of this component ranges from 16 to 39. At
least one LCN must exist to connect with an NMS workstation.
Additional LCNs can be provisioned to provide redundant access from
this Passport node to multiple network management workstations.
The LCN component contains a remoteIpAddress attribute for
Network management connectivity provisioning 253
Passport Operations and Maintenance Guide 4S3
provisioning the far end IP address of a Frame Relay PVC point-to-point
IP connection. The following two address resolution mechanisms are
available for determining the far-end IP address of the LCNs:
static ARP (used when remoteIpAddress is set) uses the provisioned
IP address of the LCNs remoteIpAddress attribute
address gleaning (used when remoteIpAddress is not set) inspects
the source address of the rst packet received on the LCN
Note: Use the static ARP method if this LCN is connected to an IP-
routing-capable device.
DC component: The DirectCall (DC) component is a subcomponent of
the LCN component. It denes a Frame Relay PVC between the IPIFR
and the Frame Relay user-to-network interface (UNI) to which the
Magellan NMS workstation is connected. To enable this connection to be
made, the Frame Relay user-to-network interface must have a
corresponding DC component provisioned with mirrored information.
StaticRoute component: The StaticRoute (Sr) component represents the
static IP route to a host, subnetwork, network IP address or default route
IP address. Sr contains two attributes, gatewayIpAddress and
backupGatewayIpAddress. Backup gateways are only supported for the
default route (that is, StaticRoute/0.0.0.0).
Route component: The Route (R) component is dynamically indexed by
the destination IP address. Route represents an active IP route to the
destination IP address. Static IP routes (that is, IPFR Srs) are only listed
here if the route is active (that is, the interface to the routes gateway is
up). Route contains three attributes, gatewayIpAddress, type and
interfaceName.
Connection options
NMS workstations can be connected to a Passport node via either of the
following options:
direct connection
indirect connection
254 Chapter 10
241-7001-150 4S3
Direct connection
An NMS workstation, such as NMS1 in Figure 24 on page 250, with a direct
connection to a Passport node can configure a Frame Relay PVC to IPIFR on
the Passport node to establish a TCP/IP connection.
Indirect connection
An IP-routing-capable device (such as NMS4 in Figure 24 on page 250) with
a frame relay connection to a Passport node can be congured with a Frame
Relay PVC to the IPIFR service on the Passport node. After the appropriate
static routes are provisioned on the Passport node, any NMS workstation
(such as NMS5 or 6 in Figure 24) on the same LAN can establish TCP/IP
connections over this Frame Relay PVC connection.
Single LAN conguration
If only a single LAN conguration exists, then the IP address of the IP-
routing-capable device can be provisioned as the gateway IP of the IP
default route (that is, StaticRoute/0.0.0.0) for the IPIFR component on a
Passport node. This allows outgoing IP datagrams from a Passport node
to be routed over the frame relay connection to the IP-routing-capable
device when no direct connection is available.
Multiple LAN conguration
If multiple LAN congurations exist, then specic static IP routes can be
provisioned for the IPIFR component on a Passport node. A static IP
route allows selected outgoing IP datagrams (based on host, subnetwork
or network criteria) to be routed over a selected frame relay connection
to an IP-routing-capable device. This provides a exible mechanism for
provisioning IP connectivity to NMS workstations when a direct
connection is not available.
IP routing and IPIFR
IP routing information is obtained by IPIFR from the following sources:
Frame Relay PVC point-to-point connections
static IP routes
default IP route
Network management connectivity provisioning 255
Passport Operations and Maintenance Guide 4S3
Frame Relay PVC point-to-point connections
IPIFR views each PVC as a point-to-point IP connection. Each PVC has an
interface or port definition which contains a local IP address, a local subnet
mask, and a destination IP address. The local IP address and subnet mask is
the same for all IPIFR PVCs. The destination IP address is either provisioned
or dynamically learned by inspecting the address of the first IP packet
received on the PVC.
Note: This differs from typical frame relay IP protocol port
implementations which are modeled as a broadcast interface talking to a
subnet, and use an ARP cache to map PVCs to destination IP addresses
within the subnet. The ARP cache is typically populated by running the
Inverse ARP protocol (IARP).
The advantage to provisioning the destination IP address of the Frame Relay
PVC connection is that the IP route from a Passport node to an NMS
workstation can be established as soon as the Frame Relay PVC is
established. Otherwise, the IP route cannot be established until after the
directly connected device sends an IP packet to the Passport module.
The completed definition of each PVC point-to-point IP link results in an IP
routing table entry. The routing table entry is a direct (non-gateway), host
route to the interfaces destination IP address. For example, the routing table
entries for a Passport module with three PVCs connecting to its IPIFR service
(see Figure 25 on page 256) is shown in Table 26.
Figure 25 illustrates Passport node 1 and the network configuration
associated with Table 26.
Table 26
IP routing table for Passport node 1 of Figure 25
Destination IP Gateway IP Type Interface Name
136.55.20.200 136.55.20.1 host vc16
136.55.20.201 136.55.20.1 host vc17
136.55.20.202 136.55.20.1 host vc18
256 Chapter 10
241-7001-150 4S3
Figure 25
IP network with only PVC point-to-point IP connections
Static IP routes
Provisioned static IP routes provide the ability to specify IP routes to NMS
workstations which are not directly connected, via a Frame Relay PVC, to the
Passport module. Three types of static IP routes are supported:
host routesIP routes to a single IP node.
subnetwork routes for the IP network that contains the Passport node
IP routes to a group of IP nodes determined by the network and
subnetwork portions of their IP addresses.
network routesIP routes to a group of IP nodes determined by the
network portion of their IP addresses.
Note 1: Subnetwork routes to remote networks (networks that do not
contain the Passport node) are NOT supported. Only network or host
routes to remote networks are supported.
Passport
network
Frame Relay
vc16
vc17
vc18
136.55.20.1
136.55.20.200
136.55.20.201
136.55.20.202
(FF.FF.FF.00)
2
1
3
4
PVCs
Network management connectivity provisioning 257
Passport Operations and Maintenance Guide 4S3
Note 2: If the IP network that contains the Passport node is subnetted,
then only subnetwork and host routes are supported in this IP network;
network routes are not supported. Network and host routes are still
supported in remote networks.
Note 3: IPIFR does not support variable-length subnetting. Only a single
subnet mask may be specied for all the VC interfaces managed by
IPIFR.
Only one static IP route can be specified for any particular host, subnetwork,
or network instance.
A maximum of 50 static IP routes are allowed to be provisioned for IPIFR.
When determining an IP route for a specific destination IP address, an exact
match of a host route is checked first, and then, if no route has been found,
the (sub)network routes are hierarchically searched.
The denition of a static IP route is done by specifying a {destination IP
address, gateway IP address} pair; where:
destination IP species the target host, subnetwork, or network IP
address(es); that is, where you want to route.
gateway IP species the IP address of the host which is the rst hop in a
multiple hop IP route to the destination IP address.
The destination IP address is interpreted as either a host address, a
subnetwork address, or a network address by using the appropriate network
mask and, if applicable, the local subnetwork mask. Specically, the
algorithm is as follows:
1 determine the IP network of the destination IP address
2 if the IP network of the destination IP address is the same as the IP
network of the Passport node (that is, the local IP address of IPIFR), then
use the known subnet mask for this network (that is, the subnet mask
dened for IPIFR) to determine if the hostId portion of the IP address is
non-zero or zero.
A non-zero hostId indicates a host route
258 Chapter 10
241-7001-150 4S3
a zero hostId indicates a subnetwork route
3 if the IP network of the destination IP address is not the same as the IP
network of the Passport module (that is, the local IP address of IPIFR),
then the subnet mask is unknown for this network. Use the pure network
mask to determine if the hostId portion of the IP address is non-zero or
zero.
A non-zero hostId indicates a host route
A zero hostId indicates a network route.
Figure 26
Static IP routes network example
running
an IP
routing
daemon
vc16
2
1
Passport
network
4
3
Frame Relay
vc17
vc18
136.55.20.1 (FF.FF.FF.00)
136.55.20.200
136.55.20.201
136.55.20.202
47.15.0.0
PVCs
47.12.0.0 47.12.5.1
running
an IP
routing
daemon
136.55.25.0
running
an IP
routing
daemon
Network management connectivity provisioning 259
Passport Operations and Maintenance Guide 4S3
IP default route
There are three modes for IPIFRs IP default route behaviour:
no IP default route
a singly dened IP default route
a backed-up IP default route
These modes are described as follows:
No IP default route
If no IP default route is provisioned for IPIFR, then if no specic host,
subnetwork or network route can be found for an outgoing IP data
packet, the packet will be dropped.
A singly dened IP default route
A single gateway IP address can be provisioned as the IP default route.
When a connection is successfully setup for which the calling IP address
matches this provisioned default route gateway IP address, this
connection is agged as the default route. As such if no specic host,
subnetwork or network route can be found for an outgoing IP data
packet, the IP data packet will be routed to this specied gateway IP
address.
Table 27
Static IP route table for Passport node 1 of Figure 26
Destination IP Gateway IP Type Interface Name
136.55.20.200 136.55.20.1 host vc16
136.55.20.201 136.55.20.1 host vc17
136.55.20.202 136.55.20.1 host vc18
47.12.5.1 136.55.20.201 host vc17
136.55.25.0 136.55.20.200 network vc16
47.0.0.0 136.55.20.202 network vc18
260 Chapter 10
241-7001-150 4S3
This functionality can be used for the following two purposes:
the ability to route to an indirectly connected LAN of NMS workstations.
the ability to provide IP path redundancy between the NMS workstations
and the Passport module.
These purposes are described as follows:
routing to an indirectly connected LAN of NMS workstations
This is a historic use of the IP default route prior to the static IP route
capability in IPIFR. It is limited by the fact that there can only be one
such indirect (sub)network route. This usage is illustrated in Figure 27
and Table 26.
Figure 27
IP default route for gateway routing
running
an IP
routing
daemon
vc16
2
1
Passport
network
4
3
Frame Relay
vc17
vc18
136.55.20.1 (FF.FF.FF.00)
136.55.20.200 136.55.20.201
136.55.20.202
47.15.0.0
PVCs
Network management connectivity provisioning 261
Passport Operations and Maintenance Guide 4S3
path redundancy
The IP default route can also be used to provide IP path redundancy.
Whenever a Frame Relay PVC interface becomes disabled (either due to
the internal Passport VC clearing or the LMI indicating that the far-end
link is down) all IP routes associated with this Frame Relay PVCs IP
interface, both direct and gateway routes are removed from the IP routing
table. This results in subsequent IP route searches to the destination IP
addresses associated with the removed IP routes, using the IP default
route.
The gateway IP address specied as the IP Default route must have
physical connectivity and IP reachability to ALL NMS workstations in
order to actually provide a redundant IP path. Continuing the example
from Figure 27 on page 260, see Figure 28 on page 262 where path
redundancy, via the IP default route, required additional IP Routers
connected (potentially via a WAN) between the management sites.
The actual realization of the WANs in these gures could be done by
using the Passport network.
The IP Path Redundancy provided has the following two limitations:
The chosen gateway IP for the IP default route may not be the
optimal IP route for all destination IP addresses.
In the example of Figure 27, vc17 would have been a more
optimal alternate route for the 136.55.25 subnet, than vc19.
Table 28
IP default route for gateway routing for Passport node 1 of Figure 27
Destination IP Gateway IP Type Interface Name
136.55.20.200 136.55.20.1 host vc16
136.55.20.201 136.55.20.1 host vc17
136.55.20.202 136.55.20.1 host vc18
0.0.0.0
(the IP default route)
136.55.20.202 network vc18
262 Chapter 10
241-7001-150 4S3
If access to the chosen gateway IP for the IP default route fails (e.g.
a VC or LMI failure), then the IP path redundancy is lost, even
though there may actually be an alternate physical route available.
In other words, there must be both physical connectivity and IP
reachability (via IP routing information) in order to route IP packets.
Two link failures, one being the default route, would result in loss of
IP connectivity to a host or network.
In the example, if both vc16 and vc19 (the default route) failed,
then the 136.55.25 subnet would be unreachable, even though
vc17 or vc18 could have been used.
Figure 28
IP default route for path redundancy
vc16
2
Passport
network
Frame Relay
vc17
vc18
136.55.20.1 (FF.FF.FF.00)
136.55.20.200
136.55.20.201
136.55.20.202
136.55.25.0
47.15.0.0 47.12.0.0
47.12.5.1
WAN
136.55.20.203
running
an IP
routing
daemon
running
an IP
routing
daemon
running
an IP
routing
daemon
IP
Router
vc19
1
4
PVCs
IP
Router
IP
Router
3
Network management connectivity provisioning 263
Passport Operations and Maintenance Guide 4S3
A backed-up IP default route
The backed-up IP default route functionality addresses the multiple
failure limitation of the singly dened IP default route solution to IP path
redundancy.
IPIFR lets you dene a subset of all the Frame Relay PVC point-to-point
IP links which can potentially be used as the IP default route. Only one
Frame Relay PVC IP link is used as the IP default route at any one instant
of time. The specic Frame Relay PVC IP link is chosen based on
whether the link is listed as a gateway for use as the IP default route, and
whether the Frame Relay PVC is enabled (that is, the VC is up and the
LMI is up).
When a link or LMI failure causes the IP default route to change to a
backup default route, the following will occur:
All existing TCP-based connections, such as telnet, ftp, and fmip,
will fail. It is possible to establish new TCP-based connections
immediately.
UDP/connectionless services, such as SNMP and XNTP, will not be
affected.
Table 29
IP default route for path redundancy for Passport node 1 of Figure 28
Destination IP Gateway IP Type Interface Name
136.55.20.200 136.55.20.1 host vc16
136.55.20.201 136.55.20.1 host vc17
136.55.20.202 136.55.20.1 host vc18
136.55.20.203 136.55.20.1 host vc19
47.12.5.1 136.55.20.201 host vc17
136.55.25.0 136.55.20.200 network vc16
47.0.0.0 136.55.20.202 network vc18
0.0.0.0
(the IP default route)
136.55.20.203 network vc19
264 Chapter 10
241-7001-150 4S3
Referring to Figure 28 on page 262 and the previous example,
assume all IPIFR PVCs are listed as possible gateways for the IP
default route,
assume all PVCs are initially down.
The routing table is empty.
vc19 comes up
the direct route associated with this point-to-point IP link is
added to the IP Routing table,
any static IP routes using vc19 as a gateway are added to the
IP Routing table. In this example, there are none.
since the IP default route is unassigned, and vc19 is listed as
a possible gateway for the IP default route, vc19 is set as the
current gateway for the IP default route.
The routing table becomes:
vc16, vc17, and vc18 come up.
For each PVC:
the direct route associated with this point-to-point IP link is
added to the IP Routing table,
any static IP routes using this PVC as a gateway are added to the
IP Routing table,
since the IP default route is already assigned,
do NOT update the IP default route
Table 30
Routing table after vc19 comes up
Destination IP Gateway IP Type Interface Name
136.55.20.203 136.55.20.1 host vc19
0.0.0.0
(the IP default route)
136.55.20.203 network vc19
Network management connectivity provisioning 265
Passport Operations and Maintenance Guide 4S3
The routing table becomes:
if vc16 fails, then
all IP routes associated with vc16 as a gateway, are removed,
the IP default route is unchanged,
routing to the 136.55.25.0 would now go through vc19,
all other IP routing would remain unchanged.
The routing table becomes:
Table 31
Routing table after vc16, vc17, and vc18 come up
Destination IP Gateway IP Type Interface Name
136.55.20.200 136.55.20.1 host vc16
136.55.20.201 136.55.20.1 host vc17
136.55.20.202 136.55.20.1 host vc18
136.55.20.203 136.55.20.1 host vc19
47.12.5.1 136.55.20.201 host vc17
136.55.25.0 136.55.20.200 network vc16
47.0.0.0 136.55.20.202 network vc18
0.0.0.0 136.55.20.203 network vc19
Table 32
IRouting table after vc16 fails
Destination IP Gateway IP Type Interface Name
136.55.20.201 136.55.20.1 host vc17
136.55.20.202 136.55.20.1 host vc18
136.55.20.203 136.55.20.1 host vc19
47.12.5.1 136.55.20.201 host vc17
(Sheet 1 of 2)
266 Chapter 10
241-7001-150 4S3
if vc16 AND vc19 fails, then
all IP routes associated with either vc16 or vc19 as a
gateway, are removed,
the IP default route will be changed to either vc17 or vc18
depending on which Frame Relay PVC is UP and which of the
Frame Relay PVCs are listed as a gateway for use as the IP
default route. If both are valid gateways and up, the order in
which the gateways are specied in the
backupGatewayIpAddress attribute determines the PVC to
choose (lowest index gets priority).
Therefore, say, vc17 is chosen as the new IP default route, and
the IP routing table is updated
routing to the 136.55.25.0 would now go through vc17,
all other IP routing would remain unchanged.
The routing table becomes:
47.0.0.0 136.55.20.202 network vc18
0.0.0.0 136.55.20.203 network vc19
Table 33
IRouting table after vc16 and vc19 fail
Destination IP Gateway IP Type Interface Name
136.55.20.201 136.55.20.1 host vc17
136.55.20.202 136.55.20.1 host vc18
47.12.5.1 136.55.20.201 host vc17
47.0.0.0 136.55.20.202 network vc18
0.0.0.0 136.55.20.201 network vc19
Table 32 (continued)
IRouting table after vc16 fails
Destination IP Gateway IP Type Interface Name
(Sheet 2 of 2)
Network management connectivity provisioning 267
Passport Operations and Maintenance Guide 4S3
Note: This functionality still has the limitation that the chosen gateway
IP for the IP default route may not be the optimal IP route for all
destination IP addresses.
Provisioning the IPIFR
This section describes the following tasks:
Preparing to provision IPIFR (if IPIVC already exists)
Provisioning a Passport node to access an NMS workstation
Provisioning a Passport node for an indirect connection to an IP
network
Provisioning a default route for path redundancy
Note: You must be in provisioning mode to perform the steps in these
procedures. See Provisioning system description on page 85 for details
on how to enter and exit provisioning mode.
Unless an IPIVC already exists, the IPIFR must be provisioned via an ASCII-
based terminal that is connected to a Passport node by a local interface. Once
IPIVC or IPIFR are initially provisioned, an external network management
system such as Magellan NMS can establish a connection to the node for
further provisioning.
CAUTION
CP Ethernet port can interfere with IPIFR routing
If you congure the unsupported Ethernet port on the
CP, it can interfere with IPIFR routing.
If the CP Ethernet port is in the same IP network as
IPIFR, then the Ethernet interface and the IPIFR
interface must have the same subnet mask. In addition,
the direct IP route associated with the Ethernet interface
will not work if provisioned as a static route under
IPIFR.
268 Chapter 10
241-7001-150 4S3
Preparing to provision IPIFR (if IPIVC already exists)
If you are changing to IPIFR from an existing IPIVC connection, you must
delete the IPIVC feature and component using the following procedure before
you can provision the IPIFR. To set up the initial IPIFR link, perform the
procedures described in 241-7001-130, Passport Startup Guide.
Procedure 54
Deleting the IPIVC feature and component
1 Start provisioning mode.
2 Add the IPIFR feature in the LPT/CP feature list.
set sw lpt/cp featureList ipifr
3 Display the feature list to ensure that IPIFR has been added.
d sw lpt/cp
4 Perform a semantic check to ensure consistency across all components
and their data.
check prov
5 Propagate the editing view throughout the node.
activate prov
6 Conrm the provisioning.
confirm prov
Note: If you do not conrm the provisioning at this point, an automatic
rollback will occur, causing the node to restart using the last committed
view saved on disk.
7 Remove the IPIVC feature from the LPT/CP feature list.
set sw lpt/cp featureList ~ ipivc
8 Display the feature list to ensure that IPIVC has been deleted.
d sw lpt/cp
9 Delete the IPIVC component.
delete ipivc
10 Provision the IPIFR component and Frame Relay UNI as described in
Provisioning the IPIFR on either an edge- or internal- Passport node
using a text interface device.
Network management connectivity provisioning 269
Passport Operations and Maintenance Guide 4S3
Provisioning a Passport node to access an NMS workstation
Provisioning an edge Passport node for IPIFR requires the following:
Provisioning the IPIFR on either an edge- or internal- Passport node
using a text interface device
Provisioning subsequent LCNs, for connectivity to additional
management stations
Provisioning Frame Relay user-to-network access for NMS on the edge
Passport node with DLCIs to all internal Passport nodes IPIFR services
Provisioning an internal Passport node for IPIFR requires the following:
Provisioning the IPIFR on either an edge- or internal- Passport node
using a text interface device
Figure 29 illustrates some of the parameters that are provisioned on a Passport
node to support IPIFR. To reach this configuration, complete Procedure 55.
You must set up the IPIFR and the initial LCN by performing the procedures
described in 241-7001-130, Passport Startup Guide. Once the IPIFR and the
initial LCN are provisioned, you can perform further provisioning, if
required, using the following procedures.
Note: You must add the module-wide virtual-circuit system (modVCS)
component and set the network ID code before you can provision the
initial IPIFR. For more information on this procedure, see 241-7001-130,
Passport Startup Guide. For more information on this component, see
241-7501-210, Passport Components.
270 Chapter 10
241-7001-150 4S3
Figure 29
Example of an edge Passport node (1) and two internal Passport nodes (2 and 3) provisioned
for Frame Relay access for NMS
Frame Relay connection
Frame Relay VC connection
Passport node1
DLCI=100
IPIFR
DNA=991
IP=1.1.1.1
LCN=16
NMS 1
IP = 1.2.3.4
FRUNI/1
DNA=111
Passport node 2
IPIFR
DNA=992
IP=1.1.1.2
LCN=16
DLCI=101
Trunk or Network Connection
Passport node3
IPIFR
DNA=993
IP=1.1.1.3
LCN=16
DLCI=102
(edge) (internal)
(internal)
FRUNI/1
DNA=222
NMS 2
IP = 2.2.3.4
LCN=17
LCN=17
Network management connectivity provisioning 271
Passport Operations and Maintenance Guide 4S3
Procedure 55
Provisioning the IPIFR on either an edge- or internal- Passport node
using a text interface device
Note: If you have already added the IPIFR component and the initial LCN
during startup, it is not necessary to perform this procedure.
1 Start provisioning mode.
2 If you havent already done so using startup or Deleting the IPIVC feature
and component on page 268, add the IPIFR component.
add IPIFR
The creation of the IPIFR component results in the creation of the
dataNetworkAddress (DNA) subcomponent.
3 Set the IP address of the IPIFR interface.
set IPIFR ipAddress <IP Address>
where:
<IP Address> is unique for each IPIFR. This IP address cannot be the
same as the IP address of IPIFRs on other nodes, or the IP address of
the remote device. The IP address has a default value of 0.0.0.0; this
must be changed to any number higher than 0.0.0.0 and up to
255.255.255.255. The IP address cannot be set to 0.0.0.0. Once the IP
address is changed, all existing sessions using this IPIFR are cleared.
4 Set the subnetMask attribute.
set IPIFR subnetMask <subnetMask Address>
where:
<subnetMask Address> indicates the IP address of the subnetwork to
which this Passport node belongs. ANDing the subnetMask with the IP
address provides the IP subnetwork address. Once the subnetMask is
changed, all existing sessions using this IPIFR are cleared.
5 Add the DNA to the IPIFR.
add IPIFR dna
6 Set the DNA of the IPIFR interface.
set IPIFR dna dataNetworkAddress <DN Address>
where:
<DN Address> is a unique customer-dened number that can contain
up to 14 digits. This DNA must be unique in the network.
272 Chapter 10
241-7001-150 4S3
7 Set the NumberingPlanIndicator (NPI) attribute.
set IPIFR dna npi <NPI>
where:
<NPI> is either e164 or x121 (x121 is used in packet-switched data
networks)
8 Add the LCN subcomponent to the IPIFR.
add IPIFR Lcn/<Logical Channel Number>
where:
<Logical Channel Number> is the instance number for the logical
channel and ranges between 16 and 39
9 Set the remoteIpAddress attribute (effectively the static ARP entry).
set IPIFR Lcn/<Logical Channel Number> remoteIpAddress
<Address>
where:
<Logical Channel Number> is the instance number for the logical
channel and ranges between 16 and 39
<Address> is the IP address of the NMS workstation or IP-routing-
capable device connected to this Lcn interface
10 Set the remote DNA for the DC component of the LCN.
set IPIFR Lcn/<Logical Channel Number> DC remoteDna <DN
Address>
where:
<Logical Channel Number> is the instance number for the logical
channel and ranges between 16 and 39
<DN Address> species the remote-end DNA link (that is, the FrUnis
DNA of the edge Passport node)
Note: When you create the Lcn component, the DirectCall (Dc)
component is automatically created.
CAUTION
IPIFR Provisioning Rule
Set the remoteIpAddress attribute if you are connecting
to an IP-routing-capable device.
Network management connectivity provisioning 273
Passport Operations and Maintenance Guide 4S3
11 Set the remote DLCI for the DC component of the LCN.
set IPIFR LCN/<Logical Channel Number> DC remoteDlci
<DLCI>
where:
<Logical Channel Number> is the instance number for the logical
channel and ranges between 16 and 39
<DLCI> species the remote end DLCI link (that is, the DLCI of the FrUni
on the edge Passport node)
Note: Leave the type attribute set to the default value
permanentSlave.
Procedure 56
Provisioning subsequent LCNs, for connectivity to additional
management stations
Note: Perform this procedure for each LCN that is required by your
network conguration after provisioning the initial LCN, as described in
Provisioning the IPIFR on either an edge- or internal- Passport node
using a text interface device.
1 Add the LCN subcomponent to the IPIFR.
add IPIFR Lcn/<Logical Channel Number>
where:
<Logical Channel Number> is the instance number for the logical
channel and ranges between 16 and 39
2 Set the remoteIpAddress attribute (effectively the static ARP entry).
set IPIFR Lcn/<Logical Channel Number> remoteIpAddress
<Address>
where:
<Logical Channel Number> is the instance number for the logical
channel and ranges between 16 and 39
<Address> is the IP address of the NMS workstation or IP-routing-
capable device connected to this Lcn interface
CAUTION
IPIFR Provisioning Rule
Set the remoteIpAddress attribute if you are connecting
to an IP-routing-capable device.
274 Chapter 10
241-7001-150 4S3
3 Set the remote DNA for the DC component of the LCN.
set IPIFR Lcn/<Logical Channel Number> DC remoteDna <DN
Address>
where:
<Logical Channel Number> is the instance number for the logical
channel and ranges between 16 and 39
<DN Address> species the remote-end DNA link (that is, the FrUnis
DNA of the edge Passport node)
Note: When you create the Lcn component, the DirectCall (Dc)
component is automatically created.
4 Set the remote DLCI for the DC component of the LCN.
set IPIFR LCN/<Logical Channel Number> DC remoteDlci
<DLCI>
where:
<Logical Channel Number> is the instance number for the logical
channel and ranges between 16 and 39
<DLCI> species the remote end DLCI link (that is, the DLCI of the FrUni
on the edge Passport node)
Note: Leave the type attribute set to the default value
permanentSlave.
Procedure 57
Provisioning Frame Relay user-to-network access for NMS on the edge
Passport node
Note: Perform this procedure only on a Passport node that is directly
connected to either an NMS workstation or an IP router.
1 Ensure that the Frame Relay UNI feature is activated.
2 Add the FRUni component that will connect to the IPIFR.
add FrUni/<FRUni instance>
where:
<FRUni instance> is the instance number for the FRUni component
The creation of the FrUni component results in the creation of three
subcomponents:
DataNetworkAddress (DNA)
Framer
LocalManagementInterface (LMI)
Network management connectivity provisioning 275
Passport Operations and Maintenance Guide 4S3
3 Link the Framer component to the hardware using the set command.
set FrUni/<FRUni instance> FRAMER interfaceName lp/<LP
instance> <port>/<port instance>
where:
<FRUni instance> is the instance number for the FRUni component
<LP instance> is the instance number for the LP and can be any
number between 1 and 15
<port> is X21 or V35
<port instance> is the X.21 (V.11) or V.35 port to which the link from
the NMS connects
4 Set the following attributes for the DataNetworkAddress (DNA)
component.
set FrUni/<FRUni instance> dna npi <NPI>
where:
<FRUni instance> is the instance number for the FRUni component
<NPI> is either e164 or x121 (x121 is used in packet-switched data
networks)
5 Set the DNA of the FrUni interface.
set FrUni/<FRUni instance> dna dataNetworkAddress <DN
Address>
where:
<FRUni instance> is the instance number for the FRUni component
<DN Address> is a unique customer dened number that can contain up
to 14 digits. This DNA must be unique in the network.
6 Set the default priority of the DNA component to high.
set FrUni/<FRUni instance> dna outDefaultPriority High
where:
<FRUni instance> is the instance number for the FRUni component
Note: Always use high priority for NMS.
7 Set the defaultTransferPriority to delay.
set FrUni/<FRUni instance> dna
defaultTransferPriority 11
where:
<FRUni instance> is the instance number for the FRUni component
276 Chapter 10
241-7001-150 4S3
Note: Always use delay sensitivity for NMS. When the transfer priority is
set at 11, the trunk queue is set to interrupting, the routing metric is set to
delay, and the egress queue is set to high.
8 Set the procedures attribute of the LocalManagementInterface (LMI)
component.
set FrUni/<FRUni instance> Lmi procedures <proc>
where:
<FRUni instance> is the instance number for the FRUni component
<proc> is either none or ANSI
Note: Setting LMI procedures is critical to the proper provisioning of this
feature. The LMI procedures of the Passport FrUni service must match
the setting for the workstations or routers frame relay DTE port.
9 Set the remainder of the attributes for the Lmi provisionable component.
The default values for the attributes are used in this step for the purpose
of explanation.
set FrUni/<FRUni instance> Lmi asyncStatusReport off
set FrUni/<FRUni instance> Lmi errorEventThreshold 3
set FrUni/<FRUni instance> Lmi eventCount 4
set FrUni/<FRUni instance> Lmi checkPointTimer 15
set FrUni/<FRUni instance> Lmi messageCountTimer 20
where:
<FRUni instance> is the instance number for the FRUni component
10 Add the Frame Relay DataLinkConnectionIdentier (Dlci) component:
Note: Repeat steps 10 to 13 for each DLCI to each internal Passport
node.
add FrUni/<FRUni instance> Dlci/<DLCI instance>
where:
<FRUni instance> is the instance number for the FRUni component
<DLCI instance> is the instance number for the DLCI component
Note: When you create the Dlci component, the DirectCall (Dc)
component is automatically created.
Network management connectivity provisioning 277
Passport Operations and Maintenance Guide 4S3
11 Set the rate enforcement attribute off for the Dlci component.
set FrUni/<FRUni instance> Dlci/<DLCI instance> Sp
rateEnforcement off
where:
<FRUni instance> is the instance number for the FRUni component
Sp is the serviceParameters subcomponent
<DLCI instance> is the instance number for the DLCI component
12 Set the maximum frame size attribute to 1600 for the Dlci component:
set Fruni/<FRUni instance> Dlci/<DLCI instance> Sp
maximumFrameSize 1600
where:
<FRUni instance> is the instance number for the FRUni component
Sp is the serviceParameters subcomponent
<DLCI instance> is the instance number for the DLCI component
Note: Accept the default values for the rest of the attributes under the
FRUni DLCI component. They are not used when the rateEnforcement
attribute is off.
13 Set the attributes for the Dc component.
set FrUni/<FRUni instance> Dlci/<DLCI instance> Dc
remoteDlci <DLCI>
set FrUni/<FRUni instance> Dlci/<DLCI instance> Dc
type permanentMaster
set FrUni/<FRUni instance> Dlci/<DLCI instance> Dc
remoteDna <DN Address>
where:
<FRUni instance> is the instance number for the FRUni component
<DLCI instance> is the instance number for the DLCI component
<DLCI> species the remote-end DLCI link (that is, the LCN of the
internal Passport nodes ipiFr)
<DN Address> species the remote-end DNA link (that is, the DNA of
the internal Passport nodes ipiFr)
Note: Setting the Dlci attribute to permanentMaster is critical to proper
provisioning of this feature.
14 To suppress accounting records generation for all Dlci components
provisioned on the Frame Relay service port:
set frUni/<FRUni instance> dna/<dna_instance>
accountCollection ~bill
278 Chapter 10
241-7001-150 4S3
15 To suppress accounting records generation on the Frame Relay service
Dlci component which is originating the call to IPIFR, set the accounting
attribute to off:
set Fruni/<FRUni instance> Dlci/<DLCI instance> Sp
accounting off
Provisioning a Passport node for an indirect connection to an IP
network
Figure 30 illustrates some of the parameters that are provisioned on a Passport
node to support an indirect connection to an IP network. To reach this
configuration, complete Procedure 58.
Network management connectivity provisioning 279
Passport Operations and Maintenance Guide 4S3
Figure 30
Parameters for a static IP route for a non-directly connected IP network
Procedure 58
Provisioning a static IP route for a non-directly connected IP network
Note 1: Figure 30 shows workstation NMS1 providing routing for the
1.2.0.0 subnet LAN. This procedure describes how to provision Passport
node1 from NMS1 or Operator Console 1 so that it can be managed by
any NMS workstation on the 1.2.0.0. subnet.
Note 2: Performing Procedure 55 and Procedure 57 on Passport node 1
and Procedure 55 on Passport node 2 are prerequisites to performing
Procedure 58.
LEGEND:
Frame Relay Link
Frame Relay VC connection
Trunk or Network Link Connection
NMS 2
IPIFR
DNA=992
IP=1.1.1.2
LCN=16
PASSPORT - 2
NMS 1
IP = 1.2.3.4
FRUNI/1
PASSPORT - 1
DLCI=100
DNA=111
IPIFR
DNA=991
IP=1.1.1.1
LCN=16
DLCI=101
IP = 2.2.3.4
FRUNI/1
DNA=122
LCN=17
DLCI=100
LCN=17
DLCI=101
IP = 1.2.0.0
running
an IP
routing
daemon
280 Chapter 10
241-7001-150 4S3
1 Provision an IPIFR SR component for the IP route to the 1.2.0.0 subnet:
add IPIFR Sr/1.2.0.0
set IPIFR Sr/1.2.0.0 gatewayIpAddress 1.2.3.4
Note: To ensure proper address resolution, ensure that the LCN
connecting to 1.2.3.4 gateway has static ARP provisioned (that is, the
remoteIpAddress of the LCN is set).
2 Repeat step 1 for Passport node 2.
Provisioning a default route for path redundancy
Figure 31 illustrates some of the parameters that are provisioned on a Passport
node to support a default route for path redundancy. To reach this
configuration, complete Procedure 59.
Network management connectivity provisioning 281
Passport Operations and Maintenance Guide 4S3
Figure 31
Parameters for a default route to provide path redundancy
Provisioning a default route for path redundancy on page 282 describes
how to specify a primary gateway (and a list of backup gateways) as the IP
default route, for path redundancy.
Note 1: Performing Procedure 55 and Procedure 57 on Passport node 1
and Procedure 55 on Passport node 2 are prerequisites to performing
Procedure 59.
Note: To use the IP default route for path redundancy, all of the NMS
workstations are required to be IP-reachable by each gateway specied
for the default route. In Figure 31 this is achieved by interconnecting
subnets 1.2 and 2.2 via IP routers.
NMS 1
IP = 1.2.3.4
FRUNI/1
PASSPORT - 1
DLCI=100
DNA=111
IPIFR
DNA=991
IP=1.1.1.1
LCN=16
DLCI=101
LCN=17
IP = 1.2.0.0
IP
Router
running
an IP
routing
daemon
NMS 2
IPIFR
DNA=992
IP=1.1.1.2
LCN=16
PASSPORT - 2
IP = 2.2.3.4
FRUNI/1
DNA=122
DLCI=100
LCN=17
DLCI=101
IP
Router
IP = 2.2.0.0
282 Chapter 10
241-7001-150 4S3
Procedure 59
Provisioning a default route for path redundancy
1 Provision an IPIFR Sr/0.0.0.0 component with the appropriate gateways:
add IPIFR Sr/0.0.0.0
set IPIFR Sr/0.0.0.0 gatewayIpAddress 1.2.3.4
set IPIFR Sr/0.0.0.0 backupGatewayIpAddress !
set IPIFR Sr/0.0.0.0 backupGatewayIpAddress 1 2.2.3.4
where:
<!> ensures that the backup gateways are cleared.
Note 1: Repeat the last set command, to dene additional backup
gateways (for example, backupGatewayIpAddress 2 3.2.3.4) if they are
available.
Note 2: To ensure proper address resolution, ensure that the LCNs
connecting to 1.2.3.4 and 2.2.3.4 gateways has static ARP provisioned
(that is, the remoteIpAddress of the LCNs is set).
2 Repeat step 1 for Passport node 2.
ILS network management via ethernet
An NMS workstation can be directly connected to a Passport inter-LAN
switching (ILS) network via an ethernet connection, as shown in Ethernet
connection to an ILS-only network for network management on page 283.
The ILS network can then be managed via SNMP, telnet, ftp, or FMIP
applications over the ethernet connection. See the following documents for a
detailed description of ILS networks:
241-7001-110, Passport General Description
241-7001-111, Passport Hardware Description
241-7001-800, Passport Getting Started Bridging and Routing
241-7001-803, Passport IP Routing User Guide
Network management connectivity provisioning 283
Passport Operations and Maintenance Guide 4S3
Figure 32
Ethernet connection to an ILS-only network for network management
VR
PPT 0937 001 AA
Passport 1
Ethernet
Ethernet
FP
NMS
workstation
Passport 2
PP
PP PP
PP
VR
VR
PP
PP
VR
Passport 3
Virtual Router
Protocol Port
any ILS link that is capable of carrying IP traffic
(for example: ethernet, token ring, FDDI, PPP, frame relay, or VNS)
PP PP
284 Chapter 10
241-7001-150 4S3
Ethernet connectivity to an ILS-only network
In an ILS-only network, management traffic is treated as normal data traffic.
Since the management traffic is IP-based, IP routing must be provisioned or
already running on each virtual router.
Provisioning ethernet connectivity
To connect an NMS workstation directly to a Passport ILS-only network, a
port on a Passport Ethernet FP is provisioned as a standard ethernet protocol
port. The following procedure creates an ethernet port on Lp/7 Enet/0, gives
it an IP address and links it to the virtual router.
Procedure 60
Provisioning an ethernet connection to an ILS-only network for network
management
1 Provision a virtual router with an IP port on Passport 1 (see Ethernet
connection to an ILS-only network for network management on
page 283).
add Vr/1
add Vr/1 Pp/LANET6070000
add Vr/1 Pp/LANET6070000 IpPort
2 Provision the IP addresses.
add Vr/1 Pp/LANET6070000 IpPort LogicalIf/
131.147.20.33
set Vr/1 Pp/LANET6070000 IpPort LogicalIf/
131.147.20.33 netMask 255.255.255.224,
broadcastAddress 131.147.20.63
Connect the NMS workstation and Passport 1 on the same subnet. See
NTP 241-7001-803, Passport IP Routing User Guide.
3 Provision an ethernet port on Passport 1.
add Lp/7 Enet/0
4 Provision a LAN application.
add La/70
set La/70 Framer interfaceName Lp/7 Enet/0
5 Link the ethernet port to the virtual router.
set Vr/1 Pp/LANET6070000 linkToMedia La/70
Network management connectivity provisioning 285
Passport Operations and Maintenance Guide 4S3
6 On the NMS workstation, use the passport.cong program to add the IP
address of the protocol port (which manages the Passport node) to le /
opt/MagellanNMS/cfg/HGDS.cfg. See 241-6001-303, NMS Administrator
Guide.
Note: Use the IP address of the most stable port (for example, the
ethernet port).
At this point, the NMS workstation can directly communicate with Passport 1
(see Ethernet connection to an ILS-only network for network management
on page 283) assuming all IP routing issues are resolved.
ILS-only network to non-ILS network connectivity
An ILS-only network can be connected to a non-ILS network. And the NMS
workstations that were previously managing either network can manage the
entire combined network. See ILS-only network to non-ILS network
connectivity on page 286.
CAUTION
ILS Provisioning Rule
All ILS FPs in a node must be provisioned with the same
combination of IP, IPX, Bridging, VNS, netSentry and
SRES features, whether or not each FP has a physical
port associated with those features. Failure to follow this
rule will result in a software alarm Potential error in
feature list provisioning and may cause packets to be
lost or misrouted. This restriction does not apply to the
WAN features X25 DTE, PPP or Frame Relay DTE.
For example, if Lp/1 has an associated sw lpt/xx feature
list provisioned with IP and Bridge, and we add Lp/2
which needs to support just IP, then Lp/2 must have both
IP and Bridge provisioned. If Lp/3 which needs to
support just IPX is added, then Lp/1, Lp/2 and Lp/3
must have IP, Bridge and IPX provisioned.
286 Chapter 10
241-7001-150 4S3
Figure 33
ILS-only network to non-ILS network connectivity
PPT 0934 001 AA
NMS
workstation 1
Ethernet
DTE
(FrUni)
ILS-only network
Non-ILS network
Passport 1
NMS
workstation 2
DTE DCE
Frame
Relay
(FrUni)
Passport 4 Passport 3
Passport 2
Frame
Relay
Frame
Relay
DCE
Network management connectivity provisioning 287
Passport Operations and Maintenance Guide 4S3
Managing combined networks from an ILS-only network NMS
workstation
An NMS workstation connected to (and managing) an ILS-only network can
also manage a non-ILS network. This section describes how to create the
example configuration shown in Connection between an ILS-only network
NMS workstation and a non-ILS network on page 290.
The non-ILS nodes can only be managed via IPIFR. IPIFR supports an
indirect connection between an NMS workstation and IPIFR via an IP-
routing-capable device. In this scenario, the IP-routing-capable device is the
Passport 2 nodes IP router, VR IP.
Note: The IP addresses to be used must all be from the same IP subnet
since the Frame Relay connections will appear as a single network.
Passport 2 requires the following:
a virtual router
an FrDte protocol port on the virtual router
(optionally) disable ARP and routing protocols on the FrDtes protocol
port
Note: This is not required if remoteIpAddress (that is, static ARP) of the
IPIFR LCN is provisioned.
physical connectivity to the FrUni on Passport 3
multiple StDlcis (one per non-ILS Passport)
static ARP table entries to associate the remote IPIFRs IpAddress with
the appropriate StDlci
linkage of the StDlcis into the RemoteGroup (under the FrDte)
linkage of the RemoteGroup to the protocol port
Passport 3 requires the following:
a FrUni physically connected to the FrDte on Passport 2
Dlcis for the IPIFRs of each non-ILS Passport node (Passport nodes 3
and 4) where the DLCI number matches that of the FrDtes StDlci
288 Chapter 10
241-7001-150 4S3
Passports 3 and 4 require the following:
an IPIFR to connect with the FrUni in Passport 3
the IpAddress and subnetMask of the IPIFR to be in the same subnet as
that of the FrDtes protocol port in Passport 2
provision the Lcn and remoteIpAddress of the IPIFR.
an IPIFR StaticRoute to NMS1, referencing Passport 2's FrDte logicalIf
in the gatewayIpAddress attribute
Procedure 61
Provisioning NMS workstation 1 to manage the ILS network
1 From NMS workstation 1, provision an ethernet connection to the
adjacent Passport node in the ILS network, as described in "Provisioning
an ethernet connection to an ILS-only network for network management"
on page 284.
NMS workstation 1 can now manage Passports 1 and 2.
Procedure 62
Provisioning NMS workstation 1 to additionally manage the non-ILS
network
1 Provision a FrUni on Passport 3.
That is, provision VCs d and e from the FrUni on Passport 3 to the IPIFR
service on Passports 4 and 3 respectively. See "IP interface over Frame
Relay" on page 250 for additional information.
2 Add FrDte, protocol port and remote group on Passport 2 to be used for
connectivity to non-ILS Passports. See 241-7001-802, Passport Frame
Relay DTE Access User Guide and 241-7001-803, Passport IP Routing
User Guide for provisioning details.
Note: Disable inverse-arp and ensure that no routing protocols (for
example, RIP or OSPF) are running on the FrDte protocol port.
set Vr/1 Pp/FrDte6070000 IpPort arpStatus disabled
This ensures that the rst packet that the IPIFR receives on Passports 3
and 4 is fromNMS workstation 1, and not from any intervening router. This
enables the IPIFR service to route trafc back to NMS workstation 1.
Note: This is not required if remoteIpAddress of the IPIFR LCN is
provisioned.
Network management connectivity provisioning 289
Passport Operations and Maintenance Guide 4S3
3 Provision a StaticDlci under FrDte on Passport 2 for each of the IPIFRs
that will be managed. The StaticDlci number under the FrDte must match
the corresponding DLCI number under the FrUni on Passport 3.
4 Add static ARP table entries on Passport 2 to map each IP address of the
IPIFR to the corresponding StaticDlci number for each non-ILS node.
add Vr/1 ip arp hostentry/<ipifr ipaddress>
set Vr/1 ip arp hostentry/<ipifr ipaddress>
permanentVirtualCircuitNumber <DlciNumber>
NMS workstation 1 can now manage Passports 3 and 4, as well as 1 and 2.
Procedure 63
Provisioning an IPIFR static route (for Passport 3)
This procedure shows how to congure an IPIFR static route in the
example conguration shown in Connection between an ILS-only
network NMS workstation and a non-ILS network on page 290.
1 Add an IPIFR StaticRoute component.
add ipifr StaticRoute/<NMS 1 address>
Note: NMS 1 address can also be a subnetwork or network route.
2 Provision the callingIPAddress attribute with the IP address of the
adjacent Passport node in the ILS network (Passport 2).
set ipifr StaticRoute/<NMS 1 address> gatewayIpAddress
<Passport 2s frDte IP> address
Procedure 64
Provisioning an IPIFR default route (for Passport 4)
As an alternative to a specic static route, this procedure shows how to
congure an IPIFR default route (for routing to NMS1) in the example
conguration shown in Connection between an ILS-only network NMS
workstation and a non-ILS network on page 290.
1 Add an IPIFR defaultRoute component.
add StaticRoute/0.0.0.0
2 Provision the gateway attribute with the IP address of the adjacent
Passport node in the ILS network (Passport 2).
set ipifr StaticRoute/0.0.0.0 gatewayIpAddress
<Passport 2s frDte IP address>
290 Chapter 10
241-7001-150 4S3
Figure 34
Connection between an ILS-only network NMS workstation and a non-ILS network
PPT 0935 001 AA
NMS
workstation 1
Ethernet
ILS link
DTE
Frame
Relay
(FrUni)
ILS-only network
Non-ILS network
Passport 1
Passport 4
Virtual Circuit (VC)
Passport 3
Passport 2
PP
IPIFR IPIFR
PP PP PP
VR
d
e
VR
Frame
Relay
DCE
Network management connectivity provisioning 291
Passport Operations and Maintenance Guide 4S3
Managing combined networks from a non-ILS network NMS
workstation
An NMS workstation connected to (and managing) a non-ILS network can
also manage an ILS-only network. See Connection between an ILS-only
network and a non-ILS network NMS workstation on page 292. In this
scenario the non-ILS network looks like a WAN to the NMS workstation,
providing connectivity to the ILS-only network.
To provision the connections between NMS workstation 2 and each Passport
node in the non-ILS network, see "IP interface over Frame Relay" on page
250.
Procedure 65
Provisioning NMS workstation 2 to additionally manage the ILS-only
network
1 Provision VC c between Passports 3 and 4 (that is, the WAN connection
through the non-ILS network).
Note: In the FrUni to FrUni VC setup, dene one side (it does not matter
which one) as a slave and the other side as a master.
2 Add FrDte, protocol port and remote group on Passport 2 to be used for
connectivity to non-ILS Passports. See 241-7001-802, Passport Frame
Relay DTE Access User Guide for provisioning details.
Note: The IP address of the NMS workstation must be in the same
subnet as the FrDte protocol port.
3 Provision a StaticDlci under FrDte on Passport 2 for the NMS workstation.
The StaticDlci number under the FrDte must match the corresponding
DLCI number under the FrUni on Passport 3.
4 Provision a static ARP table entry to map the NMS workstations IP
address to the StaticDlci that is associated with VC c.
add Vr/1 ip arp hostEntry/<NMS2 IP address>
set Vr/1 ip arp hostEntry/<NMS2 IP address> permanent
<dlci>
5 On the NMS workstation, use the passport.frconfig program to provision
a new DLCI for VC c to file /opt/MagellanNMS/cfg/HGDS.cfg. See 241-
6001-303, NMS Administrator Guide.
6 Provision the routing table for NMS workstation 2 to forward trafc
destined for Passports 1 and 2 out the Frame Relay port of Passport 3 (via
the DLCI that is associated with VC c).
292 Chapter 10
241-7001-150 4S3
NMS workstation 2 can now manage Passports 1 and 2, as well as 3 and 4.
Figure 35
Connection between an ILS-only network and a non-ILS network NMS workstation
PPT 0936 001 AA
ILS link
DTE
Frame
Relay
(FrUni)
ILS-only network
Non-ILS network
Passport 1
NMS
workstation 2
DTE DCE
Frame
Relay
(FrUni)
Passport 4
Virtual Circuit (VC)
Passport 3
Passport 2
PP
IPIFR IPIFR
PP
PP
VR
a b
c
VR
Frame
Relay
DCE
293
Passport Operations and Maintenance Guide 4S3
Chapter 11
Processor card provisioning
This chapter provides descriptions and procedures for provisioning control
processors and function processors. You only need to provision new function
processors. Replacement function processors do not need to be provisioned.
Before you perform the procedures in this chapter, you should be familiar
with the provisioning fundamentals explained in Provisioning system
description on page 85.
You must be in provisioning mode to perform the steps in these procedures.
See "Provisioning processes" on page 137 for details on how to enter and exit
from provisioning mode.
Prerequisites
Before you provision a card, you must:
perform startup procedures (241-7001-130, Passport Startup Guide)
install your software ("Software installation" on page 165)
provision the node (Node provisioning on page 217)
Provisioning a control processor
This section contains instructions for provisioning standby control processors
using an ASCII text interface device. It also contains instructions on how to
remove a standby control processor.
You only need to provision a control processor if you are installing a new one
in the last slot of the shelf to run as the standby control processor. For
example, with 16-slot Passport switch, you only have to provision a new
294 Chapter 11
241-7001-150 4S3
standby control processor in slot 15. You do not need to provision
replacement standby control processors, or main control processors (always
in slot 0). Main control processors are provisioned automatically during the
start-up process. A standby control processor for the shelf can also be
provisioned during the startup process. For more information, see 241-7001-
130, Passport Startup Guide.
If you no longer want to use a standby control processor on the shelf, you will
have to physically remove the standby control processor and then delete its
provisioning.
Adding a new standby control processor
Provisioning a new standby control processor on page 294 explains how to
provision a new control in the last slot of the shelf. You only have to provision
a standby control processor the rst time you add it to the shelf. Replacement
standby control processors do not need to be provisioned.
Procedure 66
Provisioning a new standby control processor
1 Enter provisioning mode.
start Prov
2 Use the display command to see which cards are currently congured.
display Shelf Card/*
For more information on the display command, see "Operator
commands" on page 57.
3 If the card does not already exist, add it to the shelf.
add Shelf Card/<n>
where:
<n> is the slot number of the standby control processor. The standby
control processor is always in the last slot of the shelf.
4 Set the Card component cardType attribute.
set Shelf Card/<n> cardType CP
where:
<n> is the slot number of the standby control processor.
5 Set the spareCard attribute.
set Lp/0 spareCard Shelf Card/<n>
Processor card provisioning 295
Passport Operations and Maintenance Guide 4S3
where:
<n> is the slot number of the standby control processor.
6 Perform a semantic check to ensure consistency across all components
and their data.
check Prov
7 Save the new view to disk.
save Prov
8 Use the activate command to propagate the editing view throughout the
module.
activate Prov
The editing view becomes the current view when this command is used.
9 Conrm that the editing view has become the current view.
confirm Prov
10 Commit the new view.
commit Prov
11 Exit from provisioning mode.
end Prov
Note: For instructions on testing hardware after it is installed, see
"Diagnostic tests" on page 523.
Removing a standby control processor
Removing a standby control processor on page 295 explains how to
remove a standby control processor and to delete its provisioning so that the
shelf no longer uses control processor redundancy.
Procedure 67
Removing a standby control processor
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 standby control processor is active.
2 If the standby control processor is active, switchover the control
processors so that the main control processor is active.
296 Chapter 11
241-7001-150 4S3
switchover Lp/0
3 Remove the standby control processor.
See 241-7001-126, Passport Hardware Maintenance Guide for
information on removing a control processor.
4 Enter provisioning mode.
start Prov
5 Remove the standby conguration.
set Lp/0 spareCard !
6 Remove the card conguration.
set Shelf Card/<n> cardType none
where:
<n> is the slot number of the standby control processor. The standby
control processor is always in the last slot of the shelf.
7 Perform a semantic check.
check Prov
8 Save the new view to disk.
save Prov
9 Activate the provisioning changes.
activate Prov
10 Conrm the provisioning changes.
confirm Prov
11 Commit the new view.
commit Prov
12 Exit from provisioning mode.
end Prov
Provisioning control and function processor
Information on how to provision the control and function processor (CFP1)
can be found in 241-7001-170, Passport Control and Function Processor
(CFP1) User Guide.
Processor card provisioning 297
Passport Operations and Maintenance Guide 4S3
Provisioning DS1 and E1 function processors
This section contains instructions for provisioning DS1 and E1 cards, LPs,
and ports using an ASCII text interface device.
Provisionable DS1 and E1 attributes
Provisionable DS1 components and attributes on page 298 and
Provisionable E1 components and attributes on page 299 show
provisionable components and attributes for DS1 and E1 function processors.
For detailed information about provisionable attributes, see 241-7501-210,
Passport Components.
298 Chapter 11
241-7001-150 4S3
Figure 36
Provisionable DS1 components and attributes
Root
LP
LP
DS1
Channel (Chan)
Provisioned (Prov)
lineType
zeroCoding
clockingSource
raiAlarmType
lineLength
CustomerIdentierData (CidData)
customerIdentier
AdminInfo
vendor
commentText
IfEntryProv
ifAdminStatus
ifIndex
Provisioned (Prov)
timeslots (ts)
timeslotDataRate
applicationFramerName
CustomerIdentierData (CidData)
customerIdentier
IfEntryProv
ifAdminStatus
ifIndex
Processor card provisioning 299
Passport Operations and Maintenance Guide 4S3
Figure 37
Provisionable E1 components and attributes
Root
LP
LP
E1
Channel (Chan)
Provisioned (Prov)
lineType
clockingSource
crc4Mode
sendRaiOnAis
CustomerIdentierData (CidData)
customerIdentier
AdminInfo
vendor
commentText
IfEntryProv
ifAdminStatus
ifIndex
Provisioned (Prov)
timeslots (ts)
timeslotDataRate
applicationFramerName
CustomerIdentierData (CidData)
customerIdentier
IfEntryProv
ifAdminStatus
ifIndex
300 Chapter 11
241-7001-150 4S3
Provisioning a DS1 or E1 card and its logical processors and
ports
Provisioning a DS1 or E1 function processor and its LPs and ports on
page 300 explains how to provision a new DS1 and E1 function processor
using a text interface device.
Note: The required congurations are loaded on the card only when you
use the activate command in provisioning mode. For detailed
information about logical processors, see "Logical processors and logical
processor types" on page 179.
Procedure 68
Provisioning a DS1 or E1 function processor and its LPs and ports
1 Enter provisioning mode.
start prov
2 Use the display command to see which cards are currently congured.
display shelf card/*
For more information on the display command, see "Operator
commands" on page 57.
3 If the card does not already exist, add it to the shelf.
add shelf card/<n>
where:
<n> is the slot number and can be between 1 and 15 for function
processors.
4 Provision the new processor card by setting the Card component
cardType attribute.
set shelf card/<n> cardType <cardtype>
where:
<n>, the slot number, can be between 1 and 15 for function processors
<cardtype> is DS1 or E1 for four port DS1 or E1, 8pDS1 for eight port
DS1.
5 If a suitable LP type does not exist already, provision a new LP type (LPT)
by adding a logical processor type component and set its featureList
attribute.
To determine the LPTs which exist already use the command:
Processor card provisioning 301
Passport Operations and Maintenance Guide 4S3
l sw lpt/*
Add an LPT.
add SW lpt/<LPT Name>
set SW lpt/<LPT Name> FeatureList <feature1>
<feature2> <feature3>
where:
<LPT Name> can contain up to 25 alphanumeric characters. This name
is customer dened. The LPT determines which software or feature the
LP will run.
Note 1: You can provision more than one service on each DS1 or E1 FP.
The features must be specied in order of priorityfor example,
<feature1> should be the feature for which you want the best
performance. Currently, the only services you can provision together on
the same FP are any combination of Frame Relay UNI, Frame Relay NNI,
DPN Gateway, unacknowledged trunks, and PORS trunks.
Note 2: The featureList attribute <feature> is described in the related
service user guide. (For more information on a particular featureList
attribute, see the appropriate service guide. If you are using paper-based
version of the Passport documentation library, see the 241-7001-000,
Passport Documentation Guide for a complete list of Passport
documents. If you are using an on-line version of the library, see the
Passport InfoMap, which will provide you with links to other documents).
6 Provision new LPs to run the selected logical processor type software on
the processor card. To do this, add a Logical Processor component and
complete the appropriate provisioning.
add lp/<n>
where:
<n> can be set to any number between 1 and 15.
7 Set the mainCard attribute.
set lp/<n> mainCard Shelf Card/<m>
where:
<m> is the number of the card slot. For example, to link to card1, enter 1
as the <m> value.
8 Set the spareCard attribute (optional).
set lp/<n> spareCard Shelf Card/<m>
where:
<m> is the number of the card slot.
302 Chapter 11
241-7001-150 4S3
9 Set the logicalProcessorType attribute to use the feature set dened by
<lpt name>.
set lp/<n> lpt SW lpt/<lpt name>
where:
<lpt name> can contain up to 25 alphanumeric characters (see the
service guides for additional information).
10 Set the CID attribute (optional).
set lp/<n> cid <CID>
where:
<CID> is the customer identier. The customer identier constrains the
user to those components that belong to the same customer identier.
This can be set to any number between 0 and 8191.
11 Add a port depending on the type of interface required. The interface has
default values assigned to its attributes.
add lp/<n> <port>/<m>
where:
<n> is the LP number
<port> is DS1 or E1
<m> is the port number. The interface has default values assigned to its
attributes. The set command can be used to change specic attributes.
<m> can be set to any number between 0 and 3 for four port DS1/E1, or
0 and 7 for eight port DS1.
12 Add a Channel component to the DS1/E1 port. Channel 0 is added
automatically when a DS1 or E1 port is added. Up to four channels can
be added to each DS1/E1 port (optional).
add lp/<n> <port>/<m> chan/<p>
where:
<p> can be set from 0 to 3 for DS1/E1 on specic ports. For the four port
DS1 and E1, up to 4 channels can be added on ports 1 and 3 with the
other 2 ports disabled. For the eight port DS1, up to 4 channels can be
added on ports 1 and 5 with the other 6 ports disabled.
13 Assign timeslots to the Channel component.
set lp/<n> <port>/<m> chan/<p> timeslots <timeslots>
where:
<timeslots> can be a set of numbers between 1 and 24 for DS1 and
between 1 and 31 for E1.
Processor card provisioning 303
Passport Operations and Maintenance Guide 4S3
For example, <timeslots> can be set to 4 6 8 10 14 22.
Note: If the E1 lineType attribute is set to CAS (channel associated
signalling), timeslot number 16 cannot be used.
14 Assign a data rate for the timeslots on the Channel component.
set lp/<n> <port>/<m> chan/<p> timeslotDataRate <rate>
where:
<rate> is doNotOverride, or 56K. If you select doNotOverride, the data
rate is determined by the card type and zeroCoding value (DS1 card
only). For more information, see 241-7501-210, Passport Components.
Note: If you have set zeroCoding to AMI, we recommend you set the data
rate to 56K. Otherwise, your channel may experience data errors.
15 Repeat steps 12 to 14 for each channel.
16 Set provisionable attributes.
set lp/<n> <port>/<m> <attribute> <attributevalue>
where:
<attribute> is one of the provisionable attributes described in
Provisionable DS1 components and attributes on page 298 and
Provisionable E1 components and attributes on page 299.
Note: If you are setting up a DS1 or E1 trunk between two Passports that
are co-located, you must set the clockingSource attributes 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.
17 Perform a semantic check on the provisioning data.
check prov
18 Save the new view to disk
save prov
19 Activate the provisioning data
activate prov
Note: The editing view becomes the current view when this command is
used.
20 Conrm the activation.
confirm prov
21 Commit the new view.
304 Chapter 11
241-7001-150 4S3
commit prov
22 Exit from provisioning mode.
end prov
Note: For instructions on testing hardware after it is installed, see
"Diagnostic tests" on page 523. There is a list of diagnostic tests that you
can perform on DS1 and E1 cards in Component tests on function
processors on page 527.
Provisioning V.11 and V.35 function processors
This section contains instructions for provisioning V.11 and V.35 cards, LPs,
and ports using an ASCII text interface device.
Provisionable V.11 and V.35 attributes
Provisionable V.11 and V.35 components and attributes on page 305
shows provisionable components and attributes for V.11 and V.35 function
processors. For detailed information about provisionable attributes, see
241-7501-210, Passport Components.
Processor card provisioning 305
Passport Operations and Maintenance Guide 4S3
Figure 38
Provisionable V.11 and V.35 components and attributes
CustomerIdentierData (CidData)
CustomerIdentierData (CidData)
AdminInfo
vendor
commentText
AdminInfo
vendor
commentText
Root
LP
V35
Provisioned (Prov)
linkMode
readyLineState
dataTransferLineState
lineStatusTimeOut
lineSpeed
clockingSource
dteDataClockSource
applicationFramerName
customerIdentier
customerIdentier
X21
linkMode
readyLineState
dataTransferLineState
lineStatusTimeOut
lineSpeed
clockingSource
dteDataClockSource
applicationFramerName
lineTerminationRequired
Provisioned (Prov)
306 Chapter 11
241-7001-150 4S3
Provisioning a V.11 or V.35 card and its logical processors and
ports
Provisioning a V.11 or V.35 function processor and its LPs and ports on
page 306 explains how to provision a new V.11 and V.35 function processor
using a text interface device.
Note: The required congurations are loaded on the card only when you
use the activate command in provisioning mode. For detailed
information about logical processors, see "Logical processors and logical
processor types" on page 179.
Procedure 69
Provisioning a V.11 or V.35 function processor and its LPs and ports
1 Enter provisioning mode.
start prov
2 Use the display command to see which cards are currently congured.
display shelf card/*
For more information on the display command, see "Operator
commands" on page 57.
3 If the card does not already exist, add it to the shelf.
add shelf card/<n>
where:
<n> is the slot number and can be between 1 and 15 for function
processors.
4 Provision the new processor card by setting the Card component
cardType attribute.
set shelf card/<n> cardType <cardtype>
where:
<n>, the slot number, can be between 1 and 15 for function processors.
<cardtype> is V11 (for an X.21 interface) or V35
5 If a suitable LP type does not exist already, provision a new LP type (LPT)
by adding a logical processor type component and set its featureList
attribute.
add SW lpt/<LPT Name>
Processor card provisioning 307
Passport Operations and Maintenance Guide 4S3
set SW lpt/<LPT Name> FeatureList <feature1>
<feature2> <feature3>
where:
<LPT Name> can contain up to 25 alphanumeric characters (see the
service guides for additional information). This name is customer dened.
The LPT determines which software or feature the LP will run.
Note 1: You can provision more than one service on each V.11 or V.35
FP. The features must be specied in order of priorityfor example,
<feature1> should be the feature for which you want the best
performance. The services you can provision together on one FP are:
any combination of Frame Relay UNI, Frame Relay NNI, DPN
Gateway, unacknowledged trunks, and PORS trunks
BTDS and HTDS
Note 2: The featureList attribute <feature> is described in the related
service user guide. (For more information on a particular featureList
attribute, see the appropriate service guide. If you are using paper-based
version of the Passport documentation library, see the 241-7001-000,
Passport Documentation Guide for a complete list of Passport
documents. If you are using an on-line version of the library, see the
Passport InfoMap, which will provide you with links to other documents).
6 Provision a new LP to run the selected logical processor type software on
the processor card. To do this, add a Logical Processor component and
complete the appropriate provisioning.
add lp/<n>
where <n> can be set to any number between 1 and 15.
7 Set the mainCard attribute.
set lp/<n> mainCard Shelf Card/<m>
where <m> is the number of the Card component. For example, to link to
card1, enter 1 as the <m> value.
8 Set the logicalProcessorType attribute.
set lp/<n> lpt sw lpt/<lpt name>
where <lpt name> can contain up to 25 alphanumeric characters.
9 Set the CID attribute (optional).
set lp/<n> cid <CID>
308 Chapter 11
241-7001-150 4S3
where <CID> is the customer identier. The customer identier constrains
the user to those components that belong to the same customer identier.
This can be set to any number between 0 and 8191.
10 Add a port depending on the type of interface required. The interface has
default values assigned to its attributes.
add lp/<n> <port>/<m>
where: <port> is X21 (for a V.11 card) or V35. The interface has default
values assigned to its attributes. The set command can be used to
change specic attributes.
11 Set provisionable attributes.
set lp/<n> <port>/<m> <attribute> <attributevalue>
where: <attribute> is one of the provisionable attributes described in
Provisionable V.11 and V.35 components and attributes on page 305.
12 Perform a semantic check on the provisioning data.
check prov
13 Save the new view to disk.
save prov
14 Activate the provisioning data.
activate prov
Note: The editing view becomes the current view when this command is
used.
15 Conrm the activation.
confirm prov
16 Exit from provisioning mode.
end prov
Note: For instructions on testing hardware after it is installed, see
"Diagnostic tests" on page 523. There is a list of diagnostic tests that you
can perform on V.11 and V.35 in Component tests on function
processors on page 527.
Processor card provisioning 309
Passport Operations and Maintenance Guide 4S3
Provisioning DS1C and E1C function processors
This section contains instructions for provisioning DS1C and E1C function
processors (FP), LPs, and ports using an ASCII text interface device.
Provisionable DS1C and E1C attributes
Provisionable DS1C components and attributes on page 310 and
Provisionable E1C components and attributes on page 311 show
provisionable components and attributes for DS1C and E1C FPs. For detailed
information about provisionable attributes, see 241-7501-210, Passport
Components.
310 Chapter 11
241-7001-150 4S3
Figure 39
Provisionable DS1C components and attributes
Root
LP
LP
DS1
Channel (Chan)
Provisioned (Prov)
lineType
zeroCoding
clockingSource
raiAlarmType
lineLength
CustomerIdentierData (CidData)
customerIdentier
AdminInfo
vendor
commentText
IfEntryProv
ifAdminStatus
ifIndex
Provisioned (Prov)
timeslots (ts)
timeslotDataRate
applicationFramerName
CustomerIdentierData (CidData)
customerIdentier
IfEntryProv
ifAdminStatus
ifIndex
Processor card provisioning 311
Passport Operations and Maintenance Guide 4S3
Figure 40
Provisionable E1C components and attributes
Root
LP
LP
E1
Channel (Chan)
Provisioned (Prov)
lineType
clockingSource
crc4Mode
sendRaiOnAis
CustomerIdentierData (CidData)
customerIdentier
AdminInfo
vendor
commentText
IfEntryProv
ifAdminStatus
ifIndex
Provisioned (Prov)
timeslots (ts)
timeslotDataRate
applicationFramerName
CustomerIdentierData (CidData)
customerIdentier
IfEntryProv
ifAdminStatus
ifIndex
312 Chapter 11
241-7001-150 4S3
Provisioning a DS1C or E1C card and its logical processors
and ports
This section explains how to provision a new DS1C or E1C FP using a text
interface device.
Note: The required congurations are loaded on the card only when you
use the activate command in provisioning mode. For detailed
information about logical processors, see "Logical processors and logical
processor types" on page 179.
Procedure 70
Provisioning a DS1C or E1C function processor and its LPs and ports
1 Enter provisioning mode.
start prov
2 Use the display command to see which cards are currently congured.
display shelf card/*
For more information on the display command, see "Operator
commands" on page 57.
3 If the card does not already exist, add it to the shelf.
add shelf card/<n>
where:
<n> is the slot number and can be between 1 and 15 for function
processors.
4 Provision the new processor card by setting the Card component
cardType attribute.
set shelf card/<n> cardType <cardtype>
where:
<n>, the slot number, is between 1 and 15
<cardtype> is DS1C or E1C.
5 If a suitable LP type does not already exist, provision a new LP type (LPT)
by adding a logical processor type component and set its featureList
attribute.
add SW lpt/<LPT Name>
set SW lpt/<LPT Name> FeatureList <feature1>
<feature2> <feature3>
Processor card provisioning 313
Passport Operations and Maintenance Guide 4S3
where:
<LPT Name> can contain up to 25 alphanumeric characters. This name
is customer-dened. The LPT determines which software or feature the
LP will run.
Note: The featureList attribute <feature> is described in the related
service user guide. (For more information on a particular featureList
attribute, see the appropriate service guide. If you are using paper-based
version of the Passport documentation library, see the 241-7001-000,
Passport Documentation Guide for a complete list of Passport
documents. If you are using an on-line version of the library, see the
Passport InfoMap, which will provide you with links to other documents).
6 Provision new LPs to run the selected logical processor type software on
the processor card. To do this, add a Logical Processor component and
complete the appropriate provisioning.
add lp/<n>
where:
<n> is between 1 and 15
7 To provision the card as a main card, set the mainCard attribute.
set lp/<n> mainCard Shelf Card/<m>
where:
<n> is the LP number
<m> is the number of the card slot. For example, to link to card1, enter 1
as the <m> value
or
To provision the card as a spare card, set the spareCard attribute.
set lp/<n> spareCard Shelf Card/<m>
where:
<n> is the LP number
<m> is the number of the card slot
8 Set the logicalProcessorType attribute.
set lp/<n> lpt SW lpt/<lpt name>
where:
<n> is the LP number
<lpt name> can contain up to 25 alphanumeric characters (see the
service guides for additional information)
314 Chapter 11
241-7001-150 4S3
9 Set the CID attribute (optional).
set lp/<n> cid <CID>
where:
<n> is the LP number
<CID> is the customer identier. The customer identier constrains the
user to those components that belong to the same customer identier.
This can be set to any number between 0 and 8191.
10 Add a port depending on the type of interface required. The interface has
default values assigned to its attributes.
add lp/<n> <port>/<m>
where:
<n> is the LP number
<port> is DS1 or E1
<m> is the port number (can be set to any number between 0 and 3)
The interface has default values assigned to its attributes. The set
command can be used to change specic attributes.
11 Add a Channel component to the DS1 or E1 component. Channel 0 is
added automatically when a DS1 or E1 component is added. Up to 24
channels can be added to each DS1 component and up to 31 channels
can be added to each E1 component (optional).
add lp/<n> <port>/<m> chan/<p>
where:
<n> is the LP number
<port> is DS1 or E1
<p> can be set to a number from 1 through 23 for DS1C cards and to a
number from 1 through 31 for E1C cards (Channel 0 is added
automatically).
12 Assign timeslots to the Channel component.
set lp/<n> <port>/<m> chan/<p> timeslots <timeslots>
where:
<n> is the LP number
<port> is DS1 or E1
<m> is the port number
<p> can be set to a number from 1 through 23
<timeslots> can be a set of numbers between 1 and 24 for DS1 and
between 1 and 31 for E1. For example, <timeslots> can be set to 4 6 8
10 14 22.
Processor card provisioning 315
Passport Operations and Maintenance Guide 4S3
Note: If the E1 lineType attribute is set to CAS (channel associated
signalling), timeslot 16 cannot be used.
Repeat steps 11 and 12 for each channel.
13 Set provisionable attributes.
set lp/<n> <port>/<m> <attribute> <attributevalue>
where:
<n> is the LP number
<port> is DS1 or E1
<m> is the port number
<attribute> is one of the provisionable attributes described in
Provisionable DS1C components and attributes on page 310 or
Provisionable E1C components and attributes on page 311.
Note: If you are setting up a DS1C or E1C line between two Passports
that are co-located, you must set the clockingSource attributes 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.
14 Perform a semantic check on the provisioning data.
check prov
15 Save the new view to disk.
save prov
16 Activate the provisioning data.
activate prov
Note: The editing view becomes the current view when this command is
used.
17 Conrm the activation.
confirm prov
18 Exit from provisioning mode.
end prov
Note: For instructions on testing hardware after it is installed, see
"Diagnostic tests" on page 523. There is a list of diagnostic tests that you
can perform on DS1C and E1C cards in Component tests on function
processors on page 527.
316 Chapter 11
241-7001-150 4S3
Provisioning DS3 and E3 function processors
This section contains instructions for provisioning DS3 and E3 cards and
ports using an ASCII text interface device.
Provisionable DS3 and E3 attributes
Provisionable DS3 and E3 components and attributes on page 317 shows
provisionable components and attributes for DS3 and E3 function processors.
For detailed information about provisionable attributes, see 241-7501-210,
Passport Components.
Processor card provisioning 317
Passport Operations and Maintenance Guide 4S3
Figure 41
Provisionable DS3 and E3 components and attributes
Root
LP
E3
lineLength
clockingSource
applicationFramerName
linkAlarmActivationThreshold
linkAlarmScanInterval
Provisioned (Prov)
CustomerIdentierData (CidData)
AdminInfo
vendor
commentText
LP
DS3
cbitParity
lineLength
clockingSource
applicationFramerName
Provisioned (Prov)
CustomerIdentierData (CidData)
AdminInfo
vendor
commentText
customerIdentier
customerIdentier
318 Chapter 11
241-7001-150 4S3
Provisioning a DS3 or E3 card and its logical processors and
ports
This section explains how to provision a new DS3 or E3 function processor
using a text interface device.
Note: The required conguration is loaded on the card only when you
use the activate command in provisioning mode. For detailed
information about logical processors, see "Logical processors and logical
processor types" on page 179.
Procedure 71
Provisioning a DS3 or E3 function processor and its LP and port
1 Enter provisioning mode.
start prov
2 Use the display command to see which cards are currently congured.
display shelf card/*
For more information on the display command, see "Operator
commands" on page 57.
3 If the card does not already exist, add it to the shelf.
add shelf card/<n>
where:
<n> is the slot number and can be between 1 and 15 for function
processors.
4 Provision the new processor card by setting the Card component
cardType attribute.
set shelf card/<n> cardType <cardtype>
where:
<n>, the slot number, can be between 1 and 15 for function processors
<cardtype> is DS3 or E3
5 If a suitable LP type does not exist already, provision a new LP type (LPT)
by adding a logical processor type component and set its featureList
attribute.
add SW lpt/<LPT Name>
set SW lpt/<LPT Name> FeatureList <feature1>
<feature2> <feature3>
Processor card provisioning 319
Passport Operations and Maintenance Guide 4S3
where:
<LPT Name> can contain up to 25 alphanumeric characters. This name
is customer-dened. The LPT determines which software or feature this
LP will run.
Note: The features supported for DS3 and E3 are unackTrunks and
porsTrunks.
6 Provision a new LP to run the selected logical processor type software on
the processor card. To do this, add a Logical Processor component and
complete the appropriate provisioning.
add lp/<n>
where:
<n> can be set to any number between 1 and 15.
7 Set the mainCard attribute.
set lp/<n> mainCard Shelf Card/<m>
where:
<m> is the number of the Card component. For example, to link to card1,
enter 1 as the <m> value.
8 Set the logicalProcessorType attribute.
set lp/<n> lpt sw lpt/<lpt name>
where <lpt name> can contain up to 25 alphanumeric characters.
9 Set the CID attribute (optional).
set lp/<n> cid <CID>
where:
<CID> is the customer identier. The customer identier constrains the
user to those components that belong to the same customer identier.
This can be set to any number between 0 and 8191.
10 Add a port depending on the type of interface required. The interface has
default values assigned to its attributes.
add lp/<n> <port>
where:
<port> is DS3 or E3
The interface has default values assigned to its attributes. The set
command can be used to change specic attributes.
320 Chapter 11
241-7001-150 4S3
11 Set provisionable attributes.
set lp/<n> <port> <attribute> <attributevalue>
where:
<attribute> is one of the provisionable attributes described in
Provisionable DS3 and E3 components and attributes on page 317.
12 Perform a semantic check on the provisioning data.
check prov
13 Save the new view to disk.
save prov
14 Activate the provisioning data.
activate prov
Note: The editing view becomes the current view when this command is
used.
15 Conrm the activation.
confirm prov
16 Exit from provisioning mode.
end prov
Note: For instructions on testing hardware after it is installed, see
"Diagnostic tests" on page 523. There is a list of diagnostic tests that you
can perform on DS3 and E3 cards in Component tests on function
processors on page 527.
Provisioning DS3c function processors
This section contains instructions for provisioning DS3c function processors
(FP), LPs, and ports using an ASCII text interface device.
Provisionable DS3c attributes
Provisionable DS3c components and attributes on page 321 shows
provisionable components and attributes for DS3c FPs. For detailed
information about provisionable attributes, see 241-7501-210, Passport
Components.
Processor card provisioning 321
Passport Operations and Maintenance Guide 4S3
Figure 42
Provisionable DS3c components and attributes
Root
LP
DS3
DS1
Provisioned (Prov)
cbitParity
mapping
lineLength
clockingSource
applicationFramerName (null)
CustomerIdentierData (CidData)
customerIdentier
AdminInfo
vendor
commentText
IfEntryProv
ifAdminStatus
ifIndex
Provisioned (Prov)
lineType
zeroCoding
clockingSource
CustomerIdentierData (CidData)
customerIdentier
AdminInfo
vendor
commentText
IfEntryProv
ifAdminStatus
ifIndex
Channel (chan)
Provisioned (Prov)
timeslots (ts)
timeslotDataRate
applicationFramerName
CustomerIdentierData (CidData)
customerIdentier
IfEntryProv
ifAdminStatus
ifIndex
322 Chapter 11
241-7001-150 4S3
Provisioning a DS3c card and its logical processors and ports
This section explains how to provision a new DS3c FP using a text interface
device.
Note: The required congurations are loaded on the card only when you
use the activate command in provisioning mode. For detailed
information about logical processors, see "Logical processors and logical
processor types" on page 179.
Procedure 72
Provisioning a DS3c function processor and its LPs and ports
1 Enter provisioning mode.
start prov
2 Use the display command to see which cards are currently congured.
display shelf card/*
For more information on the display command, see "Operator
commands" on page 57.
3 If the card does not already exist, add it to the shelf.
add shelf card/<n>
where:
<n> is the slot number and can be between 1 and 15 for function
processors.
4 Provision the new processor card by setting the Card component
cardType attribute.
set shelf card/<n> cardType <cardtype>
where:
<n>, the slot number, is between 1 and 15
<cardtype> is 1pDS3C
5 If a suitable LP type does not already exist, provision a new LP type (LPT)
by adding a LPT component and set its featureList attribute.
add SW lpt/<LPT Name>
set SW lpt/<LPT Name> FeatureList <feature1>
<feature2> <feature3>
where:
<LPT Name> can contain up to 25 alphanumeric characters. This name
Processor card provisioning 323
Passport Operations and Maintenance Guide 4S3
is customer-dened. The LPT determines which software or feature the
LP will run.
Note: The featureList attribute <feature> is described in the related
service user guide. (For more information on a particular featureList
attribute, see the appropriate service guide. If you are using a paper-
based version of the Passport documentation library, see 241-7001-000,
Passport Documentation Guide for a complete list of Passport
documents. If you are using an on-line version of the library, see the
Passport InfoMap, which will provide you with links to other documents).
6 Provision new LPs to run the selected logical processor type software on
the processor card. To do this, add a Logical Processor component and
complete the appropriate provisioning.
add lp/<n>
where:
<n> is between 1 and 15
7 If the card you are provisioning is to be the main card, set the mainCard
attribute.
set lp/<n> mainCard Shelf Card/<m>
where:
<n> is the LP number
<m> is the number of the card slot. For example, to link to card1, enter 1
as the <m> value
or
If the card you are provisioning is to be a spare card, set the spareCard
attribute.
set lp/<n> spareCard Shelf Card/<m>
where:
<n> is the LP number
<m> is the number of the card slot
8 Set the logicalProcessorType attribute.
set lp/<n> lpt SW lpt/<lpt name>
where:
<n> is the LP number
<lpt name> can contain up to 25 alphanumeric characters (see the
service guides for additional information)
324 Chapter 11
241-7001-150 4S3
9 Set the CID attribute (optional).
set lp/<n> cid <CID>
where:
<n> is the LP number
<CID> is the customer identier. The customer identier constrains the
user to those components that belong to the same customer identier.
This can be set to any number between 0 and 8191.
10 Add a port depending on the type of interface required. The interface has
default values assigned to its attributes.
add lp/<n> <port>/<m>
where:
<n> is the LP number
<port> is DS3
<m> is the port number (can only be set to 0)
The interface has default values assigned to its attributes. The set
command can be used to change specic attributes.
11 Add a DS1 component to the DS3 component. DS1/1 is added
automatically when a DS3 component is added. Up to 28 DS1s can be
added to each DS3 component.
When a DS1 component is added, a chan/0 component is automatically
added with 24 timeslots.
add lp/<n> <port>/0 DS1/<p>
where:
<n> is the LP number
<port> is DS3
<p> can be set to a number from 1 through 28 for DS3c cards (Channel
0 is added automatically).
12 Assign timeslots to the Channel component.
set lp/<n> <port>/0 DS1/<p> chan/0 timeslots <timeslots>
where:
<n> is the LP number
<port> is DS3
<p> can be set to a number from 1 through 28
<timeslots> can be a set of numbers between 1 and 24 for DS3c. For
example, <timeslots> can be set to 4 6 8 10 14 22.
Repeat steps 11 and 12 for each DS1.
Processor card provisioning 325
Passport Operations and Maintenance Guide 4S3
13 Set provisionable attributes.
set lp/<n> <port>/0 <attribute> <attributevalue>
where:
<n> is the LP number
<port> is DS3
<attribute> is one of the provisionable attributes described in
Provisionable DS3c components and attributes on page 321.
Note 1: Attributes can also be set at the DS1 and chan component levels.
Note 2: You must set the clockingSource attributes for DS1 components
as one of the following combinations: local at one end and line at the
other, or module at one end and line at the other.
Note 3: You can not mix local and module DS1 clocking sources on a
DS3C FP.
Note 4: The only valid clocking source for the DS3 component is local.
14 Perform a semantic check on the provisioning data.
check prov
15 Save the new view to disk.
save prov
16 Activate the provisioning data.
activate prov
Note: The editing view becomes the current view when this command is
used.
17 Conrm the activation.
confirm prov
18 Exit from provisioning mode.
end prov
Note: For instructions on testing hardware after it is installed, see
"Diagnostic tests" on page 523. There is a list of diagnostic tests that you
can perform on DS3c cards in Component tests on function processors
on page 527.
326 Chapter 11
241-7001-150 4S3
Provisioning HSSI function processors
This section contains instructions for provisioning HSSI cards, LPs, and ports
using an ASCII text interface device.
Provisionable HSSI attributes
Provisionable HSSI components and attributes on page 326 shows
provisionable components and attributes for HSSI function processors. For
detailed information about provisionable attributes, see 241-7501-210,
Passport Components.
Figure 43
Provisionable HSSI components and attributes
Root
LP
HSSI
Provisioned (Prov)
linkMode
readyLineState
dataTransferLineState
lineSpeed
applicationFramerName
CustomerIdentierData (CidData)
customerIdentier
AdminInfo
vendor
commentText
Processor card provisioning 327
Passport Operations and Maintenance Guide 4S3
Provisioning the HSSI function processor and its port
This section explains how to provision a new HSSI function processor using
a text interface device.
Note: The required congurations are loaded on the card only when you
use the activate command in provisioning mode. For detailed
information about logical processors, see "Logical processors and logical
processor types" on page 179.
Procedure 73
Provisioning a HSSI function processor and its LPs and ports
1 Enter provisioning mode.
start prov
2 Use the display command to see which cards are currently congured.
display shelf card/*
For more information on the display command, see "Operator
commands" on page 57.
3 If the card does not already exist, add it to the shelf.
add shelf card/<n>
where:
<n> is the slot number and can be between 1 and 15 for function
processors.
4 Provision the new processor card by setting the Card component
cardType attribute.
set shelf card/<n> cardType <cardtype>
where:
<n>, the slot number, can be between 1 and 15 for function processors.
<cardtype> is HSSI
5 If a suitable LP type does not exist already, provision a new LP type (LPT)
by adding a logical processor type component and set its featureList
attribute.
add SW lpt/<LPT Name>
set SW lpt/<LPT Name> FeatureList <feature1>
<feature2> <feature3>
328 Chapter 11
241-7001-150 4S3
where:
<LPT Name> can contain up to 25 alphanumeric characters (see the
service guides for additional information). This name is customer dened.
The LPT determines which software or feature the LP will run.
Note 1: Either Frame Relay UNI or Frame Relay NNI can be provisioned
on a HSSI FP. The software for both features can be loaded on a card but
only one can be operated any time. For best performance, the feature that
is normally running should be <feature1>. The HDLC software can also
be loaded on HSSI by using the feature name hdlctransparent.
Note 2: The featureList attribute <feature> is described in the related
service user guide. (For more information on a particular featureList
attribute, see the appropriate service guide. If you are using paper-based
version of the Passport documentation library, see the 241-7001-000,
Passport Documentation Guide for a complete list of Passport
documents. If you are using an on-line version of the library, see the
Passport InfoMap, which will provide you with links to other documents).
6 Provision a new LP to run the selected logical processor type software on
the processor card. To do this, add a Logical Processor component and
complete the appropriate provisioning.
add lp/<n>
where:
<n> can be set to any number between 1 and 15.
7 Set the mainCard attribute.
set lp/<n> mainCard Shelf Card/<m>
where:
<m> is the number of the Card component. For example, to link to card1,
enter 1 as the <m> value.
8 Set the logicalProcessorType attribute.
set lp/<n> lpt sw lpt/<lpt name>
where:
<lpt name> can contain up to 25 alphanumeric characters.
9 Set the CID attribute (optional).
set lp/<n> cid <CID>
where:
<CID> is the customer identier. The customer identier constrains the
user to those components that belong to the same customer identier.
This can be set to any number between 0 and 8191.
Processor card provisioning 329
Passport Operations and Maintenance Guide 4S3
10 Add a port depending on the type of interface required. The interface has
default values assigned to its attributes.
add lp/<n> <port>/<m>
where:
<port> is HSSI. The interface has default values assigned to its
attributes. The set command can be used to change specic attributes.
<m> is 0
11 Set provisionable attributes.
set lp/<n> <port>/<m> <attribute> <attributevalue>
where:
<attribute> is one of the provisionable attributes described in
Provisionable HSSI components and attributes on page 326.
12 Perform a semantic check on the provisioning data.
check prov
13 Save the new view to disk
save prov
14 Activate the provisioning data
activate prov
Note: The editing view becomes the current view when this command is
used.
15 Conrm the activation.
confirm prov
16 Exit from provisioning mode.
end prov
Note: For instructions on testing hardware after it is installed, see
"Diagnostic tests" on page 523. There is a list of diagnostic tests that you
can perform on HSSI in Component tests on function processors on
page 527.
330 Chapter 11
241-7001-150 4S3
Provisioning three-port DS1 and E1 ATM function
processors
This section contains instructions for provisioning DS1 and E1 ATM cards,
LPs, and ports using an ASCII text interface device.
Provisionable three-port DS1 and E1 ATM attributes
Provisionable three-port DS1 ATM components and attributes on page 331
and Provisionable three-port E1 ATM components and attributes on
page 332 show provisionable components and attributes for DS1 and E1
ATM function processors. For detailed information about provisionable
attributes, see 241-7501-210, Passport Components.
Processor card provisioning 331
Passport Operations and Maintenance Guide 4S3
Figure 44
Provisionable three-port DS1 ATM components and attributes
Root
LP
DS1
Provisioned (Prov)
lineType
zeroCoding
clockingSource
raiAlarmType
lineLength
CustomerIdentierData (CidData)
customerIdentier
AdminInfo (AdminInfo)
vendor
commentText
AtmCell
Provisioned (Prov)
alarmActDelay
scrambleCellPayload
Channel (Chan)
332 Chapter 11
241-7001-150 4S3
Figure 45
Provisionable three-port E1 ATM components and attributes
Provisioning a three-port DS1 or E1 ATM card and its logical
processors and ports
This section explains how to provision a new DS1 and E1 ATM function
processor using a text interface device.
Note 1: The required congurations are loaded on the card only when
you use the activate command in provisioning mode. For detailed
information about logical processors, see "Logical processors and logical
processor types" on page 179.
Root
LP
E1
Provisioned (Prov)
lineType
clockingSource
crc4Mode
CustomerIdentierData (CidData)
customerIdentier
AdminInfo (AdminInfo)
vendor
commentText
AtmCell
Provisioned (Prov)
alarmActDelay
scrambleCellPayload
Channel (Chan)
sendRaiOnAis
Processor card provisioning 333
Passport Operations and Maintenance Guide 4S3
Note 2: For specic information on components and attributes, see
241-7501-210, Passport Components.
Procedure 74
Provisioning a three-port DS1 or E1 ATM function processor and its LPs
and ports
1 Enter provisioning mode.
start prov
2 Use the display command to see which cards are currently congured.
display shelf card/*
For more information on the display command, see "Operator
commands" on page 57.
3 If the card does not already exist, add it to the shelf.
add shelf card/<n>
where:
<n> is the slot number and can be between 1 and 15 for function
processors.
4 Provision the new processor card by setting the Card component
cardType attribute.
set shelf card/<n> cardType <cardtype>
where:
<n>, the slot number, can be between 1 and 15 for function processors
<cardtype> is 3pDS1Atm or 3pE1Atm
5 If a suitable LP type does not exist already, provision a new LP type (LPT)
by adding a logicalProcessorType component and set its featureList
attribute.
To determine the LPTs which exist already use the command:
l sw lpt/*
Add an LPT.
add sw lpt/<lpt name>
set sw lpt/<lpt name> FeatureList <feature1>
<feature2> <feature3>
where:
<lpt name> can contain up to 25 alphanumeric characters. This name
334 Chapter 11
241-7001-150 4S3
is customer dened. The LPT determines which software or feature the
LP will run.
Note: The featureList attribute <feature> is described in the related
service user guide. (For more information on a particular featureList
attribute, see the appropriate service guide. If you are using paper-based
version of the Passport documentation library, see the 241-7001-000,
Passport Documentation Guide for a complete list of Passport
documents. If you are using an on-line version of the library, see the
Passport InfoMap, which will provide you with links to other documents).
6 Provision the new LPs to run the selected software logical processor type
on the processor card. To do this, add a LogicalProcessor component and
complete the appropriate provisioning.
add lp/<n>
where:
<n> can be set to any number between 1 and 15.
7 Set the mainCard attribute to tell the system which slot to associate with
which LP.
set lp/<n> mainCard Shelf Card/<m>
where:
<m> is the number of the card slot. For example, to link to card1, enter 1
as the <m> value.
8 Set the logicalProcessorType attribute to use the feature set dened by
<lpt name>.
set lp/<n> lpt sw lpt/<lpt name>
9 Set the CID attribute (optional).
set lp/<n> cid <CID>
where:
<CID> is the customer identier. The customer identier constrains the
user to those components that belong to the same customer identier.
This can be set to any number between 0 and 8191. Only users with a CID
of 0 are permitted to carry out provisioning procedures. For more
information about CID, see Userid and its attributes on page 207.
10 Add a port depending on the type of interface required. The interface has
default values assigned to its attributes.
add lp/<n> <port>/<m>
Processor card provisioning 335
Passport Operations and Maintenance Guide 4S3
where:
<n> is the LP number
<port> is DS1 or E1
<m> is 0, 1, or 2, the number of the port being added
The interface has default values assigned to its attributes. The set
command can be used to change specic attributes.
When the ports are added, mandatory subcomponents chan/0, chan/0
cell, and Test will be added automatically as subcomponents to the DS1
and E1 components.
11 Set provisionable attributes.
set lp/<n> <port>/<m> <attribute> <attributevalue>
where:
<attribute> is one of the provisionable attributes described in
Provisionable three-port DS1 ATM components and attributes on
page 331 and Provisionable three-port E1 ATM components and
attributes on page 332.
<m> is the port number
Note 1: DS1 ATM function processors support only ESF linetype.
Note 2: Use of the full number of timeslots for the DS1 and E1 ATM FPs
is required:
for DS1A: timeslots 1-24;
for E1A CAS linetype: timeslots 1-15, 17-31;
for E1A CCS linetype: timeslots 1-15, 17-31;
Some examples of setting provisionable attributes follow:
The clocking source used for synchronizing the transmit clock may be
local or module. To set the FP local oscillator as the signal to synchronize
the transmit clock on the FP use the command:
set lp/<n> DS1/<m> clockingSource local
The three port DS1 ATM FP provides a single, common, transmit clock for
all ports on the board. Therefore, all the ports on a single FP must be
congured to have the same clock source. See description of clocking
and synchronization in 241-7001-111, Passport Hardware Description.
The attribute lineType denes the framing mode used on E1 ports. Valid
values are:
CAS (channel associated signalling) indicates that timeslot 16 within
the E1 frame is reserved for multiframe signalling, and that only 30
timeslots are available for data
336 Chapter 11
241-7001-150 4S3
CCS (common channel signalling) indicates that timeslots 1- 15 and
17-31 are all available for data
To set an E1 port to CAS mode use the command
set lp/<n> E1/<m> lineType cas
The cell payload is scrambled by default, according to ITU-T
Recommendation I.432. You can turn cell payload scrambling off for a
port on an ATM card. Use the command
set lp/<n> DS3/<m> cell scrambleCellPayload off
Note: When cell payload scrambling is turned off for ATM ports, there is
a possibility of false cell header delineation errors.
12 Perform a semantic check on the provisioning data.
check prov
13 Save the new view to disk.
save prov
14 Activate the provisioning data.
activate prov
Note: The editing view becomes the current view when this command is
used.
15 Conrm the activation.
confirm prov
16 Exit from provisioning mode.
end prov
Note: For instructions on testing hardware after it is installed, see
"Diagnostic tests" on page 523. There is a list of diagnostic tests that you
can perform on DS1 and E1 ATM cards in Component tests on function
processors on page 527.
The ports are now provisioned but still must be linked to an ATM interface
before they can provide any service. For details see the section on
provisioning an AtmInterface component in 241-7001-700, Passport ATM
Core Services User Guide.
Processor card provisioning 337
Passport Operations and Maintenance Guide 4S3
Provisioning eight-port DS1 and E1 ATM function
processors
This section contains the provisionable attributes for the eight-port DS1 and
E1 ATM function processors and provides instructions for provisioning these
FPs, along with their LPs and ports, using an ASCII text interface device.
Provisionable eight-port DS1 and E1 ATM attributes
The component hierarchies for eight-port DS1/E1 ATM FPs are illustrated in
the following gures:
DS1 - Provisionable eight-port DS1 ATM components and attributes
on page 338
E1 - Provisionable eight-port E1 ATM components and attributes on
page 339
A summary of the specic provisionable attributes, excluding the
CustomerIdentierData, AdminInfo, and IfEntryProv component groups
which are the same as for other DS1/E1 components, can be found in the
following tables:
DS1 - Provisionable attributes for a port on an eight-port DS1 ATM FP
on page 340
E1 - Provisionable attributes for a port on an eight-port E1 ATM FP on
page 341
For detailed information about provisionable attributes, see 241-7501-210,
Passport Components.
338 Chapter 11
241-7001-150 4S3
Figure 46
Provisionable eight-port DS1 ATM components and attributes
Root
LP
DS1
Provisioned (Prov)
lineType
zeroCoding
clockingSource
raiAlarmType
lineLength
CustomerIdentierData (CidData)
customerIdentier
AdminInfo (AdminInfo)
vendor
commentText
AtmCell
Provisioned (Prov)
alarmActDelay
scrambleCellPayload
Channel (Chan)
Processor card provisioning 339
Passport Operations and Maintenance Guide 4S3
Figure 47
Provisionable eight-port E1 ATM components and attributes
Root
LP
E1
Provisioned (Prov)
lineType
clockingSource
crc4Mode
CustomerIdentierData (CidData)
customerIdentier
AdminInfo (AdminInfo)
vendor
commentText
AtmCell
Provisioned (Prov)
alarmActDelay
scrambleCellPayload
Channel (Chan)
sendRaiOnAis
340 Chapter 11
241-7001-150 4S3
Table 34
Provisionable attributes for a port on an eight-port DS1 ATM FP
Attribute Values Description
clockingSource module (default - if NS
component is present)
Uses a clock that is phase-locked to the CP
reference clock over the Passport
backplane. It is recommended that this
value should always be used, unless local
testing is being performed.
line Uses the clock recovered from the receive
line data on the FP.
local (default - if NS
component is not present)
Uses the local oscillator on the FP for the
transmit port.
lineType esf 24 frames per multiframe.
raiAlarmType fdl Uses the facility data link (FDL) for the
alarm, by sending a repeated pattern of
eight 0s followed by eight 1s on the FDL
link.
Note: This value is only valid for a line type
of esf.
zeroCoding b8zs Any string of eight consecutive 0s to be
replaced with the B8ZS code.
lineLength 0 to 655 feet Equalization calculations based on
increments of 110 feet. Ranges used are 0-
110, 110-220, ..., 550-655.
Processor card provisioning 341
Passport Operations and Maintenance Guide 4S3
Provisioning an eight-port DS1 or E1 ATM card and its logical
processors and ports
This section explains how to provision a new eight-port DS1/E1 ATM
function processor using a text interface device.
Note 1: The required congurations are loaded on the card only when
you use the activate command in provisioning mode.
Note 2: For specic information on components and attributes, see 241-
7501-210, Passport Components.
Procedure 75
Provisioning an eight-port DS1 or E1 ATM function processor
1 Enter provisioning mode.
start prov
2 Use the display command to see which cards are currently congured.
display shelf card/*
Table 35
Provisionable attributes for a port on an eight-port E1 ATM FP
Attribute Values Description
clockingSource module (default - if NS
component is present)
Uses a clock that is phase-locked to the CP
reference clock over the Passport
backplane. It is recommended that this
value should always be used, unless local
testing is being performed.
line Uses the clock recovered from the receive
line on the port.
local (default - if NS
component is not present)
Uses the local oscillator on the FP for the
transmit port.
lineType ccs 30 timeslots available for data.
crc4Mode on
off
Enables cyclical redundancy check
generation and verification on the E1 line.
sendRaiOnAis yes Sets the remote alarm indication and the
alarm indication signal.
342 Chapter 11
241-7001-150 4S3
For more information on the display command, see "Operator
commands" on page 57.
3 If the card does not already exist, add it to the shelf.
add shelf card/<n>
where:
<n> is the slot number and can be between 1 and 15 for function
processors.
4 Provision the new processor card by setting the Card component
cardType attribute.
set shelf card/<n> cardType <cardtype>
where:
<cardtype> is 8pDS1Atm or 8pE1Atm
5 If a suitable LP type does not exist already, provision a new LP type (LPT)
by adding a logical processor type component and set its featureList
attribute.
To determine the LPTs which exist already use the command:
l sw lpt/*
Add an LPT.
add sw lpt/<lpt name>
set sw lpt/<lpt name> FeatureList <feature1>
<feature2> <feature3>
where:
<LPT Name> can contain up to 25 alphanumeric characters. This name
is customer dened. The LPT determines which software or feature the
LP will run.
Note: The featureList attribute <feature> is described in the related
service user guide. (For more information on a particular featureList
attribute, see the appropriate service guide. If you are using paper-based
version of the Passport documentation library, see the 241-7001-000,
Passport Documentation Guide for a complete list of Passport
documents. If you are using an on-line version of the library, see the
Passport InfoMap, which will provide you with links to other documents).
Processor card provisioning 343
Passport Operations and Maintenance Guide 4S3
6 Provision new LPs to run the selected logical processor type software on
the processor card. To do this, add a Logical Processor component and
complete the appropriate provisioning.
add lp/<n>
where:
<n> can be set to any number between 1 and 15.
7 Set the mainCard attribute to tell the system which slot to associate with
which LP.
set lp/<n> mainCard Shelf Card/<m>
where:
<m> is the number of the card slot. For example, to link to card1, enter 1
as the <m> value.
8 Set the logicalProcessorType attribute to use the feature set dened by
<lpt name>.
set lp/<n> lpt sw lpt/<lpt name>
9 Set the CID attribute (optional).
set lp/<n> cid <CID>
where:
<CID> is the customer identier. The customer identier constrains the
user to those components that belong to the same customer identier.
This can be set to any number between 0 and 8191. Only users with a CID
of 0 are permitted to carry out provisioning procedures. For more
information about CID see Userid and its attributes on page 207.
10 Add a port depending on the type of interface required. The interface has
default values assigned to its attributes.
add lp/<n> <port>/<m>
where:
<n> is the LP number
<port> is DS1 or E1
<m> is 0 through 7 is the number of the port being added
The interface has default values assigned to its attributes. The set
command can be used to change specic attributes.
When the ports are added, mandatory subcomponents chan/0 and
chan/0 cell, are added automatically as subcomponents to the DS1 and
E1 components.
344 Chapter 11
241-7001-150 4S3
Note: If trafc shaping (per-VC queueing) is enabled, then only port
instances 0 to 3 can be used for independent ATM links. For IMA link
groups, any port instance can potentially be used. See the provisioning
section in 241-7001-730, Passport Inverse Multiplexing for ATM User
Guide for details. Trafc shaping is enabled if the perVcQueueInterfaces
attribute under the Arc subcomponent of the Lp is set to any value other
than 0. For details, see 241-7001-700, Passport ATM Core Services User
Guide
11 Set provisionable attributes.
set lp/<n> <port>/<m> <attribute> <attributevalue>
where:
<attribute> is one of the provisionable attributes described in
Provisionable attributes for a port on an eight-port DS1 ATM FP on
page 340 and Provisionable attributes for a port on an eight-port E1 ATM
FP on page 341.
<m> is the port number
Note 1: DS1 ATM function processors support only ESF linetype.
Note 2: Use of the full number of timeslots for the DS1 and E1 ATM FPs
is required:
for DS1A: timeslots 1-24;
for E1A CCS linetype: timeslots 1-15, 17-31;
Some examples of setting provisionable attributes follow:
The clocking source used for synchronizing the transmit clock may be
local, line or module. To set the FP local oscillator as the signal to
synchronize the transmit clock on the FP use the command:
set lp/<n> DS1/<m> clockingSource local
The attribute lineType denes the framing mode used on E1 ports. CCS
(common channel signalling) is the only valid value. It indicates that
timeslots 1- 15 and 17-31 are all available for data
To set an E1 port to CCS mode use the command
set lp/<n> E1/<m> lineType CCS
The cell payload is scrambled by default, according to ITU-T
Recommendation I.432. You can turn cell payload scrambling off for a
port on an ATM card. Use the command
set lp/<n> DS3/<m> cell scrambleCellPayload off
Note: When cell payload scrambling is turned off for ATM ports, there is
a possibility of false cell header delineation errors.
Processor card provisioning 345
Passport Operations and Maintenance Guide 4S3
12 Perform a semantic check on the provisioning data.
check prov
13 Save the new view to disk.
save prov
14 Activate the provisioning data.
activate prov
Note: The editing view becomes the current view when this command is
used.
15 Conrm the activation.
confirm prov
16 Exit from provisioning mode.
end prov
Note: For instructions on testing hardware after it is installed, see
Diagnostic tests on page 523.
The ports are now provisioned but, if you intend to use them as independent
ATM links, you must still link each port to an ATM interface before
providing any service. For details, see the section on provisioning an
AtmInterface component in 241-7001-700, Passport ATM Core Services
User Guide.
If you are using the IMA feature, then the ports must be bound to an IMA link
group. The IMA link groups must then be bound to an ATM interface. See
241-7001-730, Passport Inverse Multiplexing for ATM User Guide for
details.
Provisioning JT2 ATM function processors
This section contains instructions for provisioning JT2 ATM cards and ports
using an ASCII text interface device.
Provisionable JT2 ATM attributes
Provisionable JT2 ATM components and attributes on page 346 shows
provisionable components and attributes for JT2 ATM function processors.
For detailed information about provisionable attributes, see 241-7501-210,
Passport Components.
346 Chapter 11
241-7001-150 4S3
Figure 48
Provisionable JT2 ATM components and attributes
Provisioning a JT2 ATM card and its logical processors and
ports
This section explains how to provision a new JT2 ATM function processor
using a text interface device. Each port must be provisioned individually.
Note: The required conguration is loaded on the card only when you
use the activate command in provisioning mode. For detailed
information about logical processors, see "Logical processors and logical
processor types" on page 179.
Procedure 76
Provisioning a JT2 ATM function processor and its LP and port
1 Enter provisioning mode.
start prov
Provisioned (Prov)
alarmActDelay
scrambleCellPayload
Provisioned (Prov)
clockingSource
lineLength
applicationFramerName
CustomerIdentierData (CidData)
customerIdentier
AdminInfo
vendor
commentText
AtmCell
Root
LP
JT2
Processor card provisioning 347
Passport Operations and Maintenance Guide 4S3
2 Use the display command to see which cards are currently congured.
display shelf card/*
For more information on the display command, see "Operator
commands" on page 57.
3 If the card does not already exist, add it to the shelf.
add shelf card/<n>
where:
<n> is the slot number and can be between 1 and 15 for function
processors.
4 Provision a new processor card by setting the Card component cardType
attribute.
set shelf card/<n> cardType <cardtype>
where:
<n> can be between 1 and 14 for function processors
<cardtype> is 2pJ6mAtm
5 If a suitable LP type does not exist already, provision a new LP type (LPT)
by adding a logical processor type component and set its featureList
attribute.
To determine the LPTs which exist already use the command:
l sw lpt/*
Add an LPT.
add sw lpt/<lpt name>
set sw lpt/<lpt name> FeatureList <feature1>
<feature2> <feature3>
where:
<lpt name> can contain up to 25 alphanumeric characters. This name
is customer-dened. The LPT determines which software or feature this
LP will run.
Note: The features supported for JT2 ATM FPs are atmTrunks,
atmBearerService, and porsTrunks.
6 Provision a new LP to run the selected logical processor type software on
the processor card. To do this, add a Logical Processor component and
complete the appropriate provisioning.
add lp/<n>
348 Chapter 11
241-7001-150 4S3
where:
<n> can be set to any number between 1 and 14.
7 Set the mainCard attribute to tell the system which slot to associate with
which LP.
set lp/<n> mainCard Shelf Card/<m>
where:
<m> is the number of the Card component. For example, to link to card1,
enter 1 as the <m> value.
8 Set the logicalProcessorType attribute to use the feature set dened by
<lpt name>.
set lp/<n> lpt sw lpt/<lpt name>
9 Set the CID attribute (optional).
set lp/<n> cid <CID>
where:
<CID> is the customer identier. The customer identier constrains the
user to those components that belong to the same customer identier.
This can be set to any number between 0 and 8191. Only users with a CID
of 0 are permitted to carry out provisioning procedures. For more
information about CID see Userid and its attributes on page 207.
10 Add the type of port which is supported by this function processor. The
interface has default values assigned to its attributes. You must add each
port individually.
add lp/<n> <port>/<m>
where:
<port> is JT2, the type of port
<m> is 0 or 1, the number of the port being added
The interface has default values assigned to its attributes. The set
command can be used to change specic attributes.
When the ports are added mandatory subcomponents ATMCell and Test
will be automatically added under the JT2 component.
11 Set provisionable attributes.
set lp/<n> <port>/<m> <attribute> <attributevalue>
where:
<attribute> is one of the provisionable attributes described in
Provisionable JT2 ATM components and attributes on page 346.
<m> is the port number
Processor card provisioning 349
Passport Operations and Maintenance Guide 4S3
Some examples follow:
set lp/n JT2/<m> clockingSource local
The clocking source may be set to local, module, line, or other port. See
the description of clocking and synchronization in 241-7001-111,
Passport Hardware Description.
The cell payload is scrambled by default, according to ITU-T
Recommendation I.432. You can turn cell payload scrambling off for a
port on an ATM card. Use the command
set lp/<n> DS3/<m> cell scrambleCellPayload off
Note: When cell payload scrambling is turned off for ATM ports, there is
a possibility of false cell header delineation errors.
12 Perform a semantic check on the provisioning data.
check prov
13 Save the new view to disk
save prov
14 Activate the provisioning data
activate prov
Note: The editing view becomes the current view which the node uses,
when this command is used.
15 Conrm the activation.
confirm prov
16 Exit from provisioning mode.
end prov
Note: For instructions on testing hardware after it is installed, see
"Diagnostic tests" on page 523. There is a list of diagnostic tests that you
can perform on JT2 ATM cards in Component tests on function
processors on page 527.
The ports are now provisioned but still must be linked to an ATM Interface
before each is available for use in providing any service. For information on
linking to and provisioning an AtmInterface component see 241-7001-700,
Passport ATM Core Services User Guide.
350 Chapter 11
241-7001-150 4S3
Provisioning DS3 and E3 ATM function processors
This section contains instructions for provisioning DS3 and E3 ATM cards
and ports using an ASCII text interface device.
Provisionable DS3 and E3 ATM attributes
Provisionable DS3 and E3 ATM components and attributes on page 351
shows provisionable components and attributes for DS3 and E3 ATM
function processors. For detailed information about provisionable attributes,
see 241-7501-210, Passport Components.
Processor card provisioning 351
Passport Operations and Maintenance Guide 4S3
Figure 49
Provisionable DS3 and E3 ATM components and attributes
Root
LP
DS3
Provisioned (Prov)
cbitParity
mapping
lineLength
clockingSource
applicationFramerName
CustomerIdentierData (CidData)
customerIdentier
AdminInfo
vendor
commentText
AtmCell
alarmActDelay E3
scrambleCellPayload
Provisioned (Prov)
CustomerIdentierData (CidData)
customerIdentier
AdminInfo
vendor
commentText
AtmCell
Provisioned(Prov)
alarmActDelay
scrambleCellPayload
Provisioned (Prov)
G832
Provisioned(Prov)
trailTraceExpected
trailTraceTransmitted
Note: G832 component is only
applicable if framing attribute is
set to G832
lineLength
mapping
framing
clockingSource
applicationFramerName
linkAlarmActivationThreshold
linkAlarmScanInterval
352 Chapter 11
241-7001-150 4S3
Provisioning a DS3 or E3 ATM card and its logical processors
and ports
This section explains how to provision a new DS3 or E3 ATM function
processor using a text interface device. Each port must be provisioned
individually.
Note: The required conguration is loaded on the card only when you
use the activate command in provisioning mode. For detailed
information about logical processors, see "Logical processors and logical
processor types" on page 179.
Procedure 77
Provisioning a DS3 or E3 ATM function processor and its LP and port
1 Enter provisioning mode.
start prov
2 Use the display command to see which cards are currently congured.
display shelf card/*
For more information on the display command, see "Operator
commands" on page 57.
3 If the card does not already exist, add it to the shelf.
add shelf card/<n>
where:
<n> is the slot number and can be between 1 and 15 for function
processors.
4 Provision the new processor card by setting the Card component
cardType attribute.
set shelf card/<n> cardType <cardtype>
where:
<n>, the slot number, can be between 1 and 15 for function processors
<cardtype> is 3pDS3Atm or 3pE3Atm
5 Use the display command to verify that you have provisioned the card
properly.
display shelf card/*
Processor card provisioning 353
Passport Operations and Maintenance Guide 4S3
6 If a suitable LP type does not exist already, provision a new LP type (LPT)
by adding a logical processor type component and set its featureList
attribute.
To determine the LPTs which exist already use the command:
l sw lpt/*
To add an LPT.
add sw lpt/<lpt name>
set sw lpt/<lpt name> FeatureList <feature1>
<feature2> <feature3>
where:
<lpt name> can contain up to 25 alphanumeric characters. This name
is customer-dened. The LPT determines which software or feature this
LP will run.
Note: The features supported for DS3 and E3 ATM FPs are porsTrunks,
atmTrunks and atmBearerService.
7 Provision a new LP to run the selected logical processor type software on
the processor card. To do this, add a Logical Processor component and
complete the appropriate provisioning.
add lp/<n>
where:
<n> can be set to any number between 1 and 15. For consistency, the
recommended value of <n> is the slot number the card is in.
8 Set the mainCard attribute to tell the system which slot to associate with
which LP.
set lp/<n> mainCard Shelf Card/<m>
where:
<m> is the number of the Card component, which should be set to the slot
number for consistency. That is, <m> should equal <n>.
9 Set the logicalProcessorType attribute to use the feature set dened by
<lpt name>.
set lp/<n> lpt sw lpt/<lpt name>
10 Set the CID attribute (optional).
set lp/<n> cid <CID>
where:
<CID> is the customer identier. The customer identier constrains the
354 Chapter 11
241-7001-150 4S3
user to those components that belong to the same customer identier.
This can be set to any number between 0 and 8191. Only users with a CID
of 0 are permitted to carry out provisioning procedures. For more
information about CID see Userid and its attributes on page 207.
11 Add the type of port which is supported by this function processor. The
interface has default values assigned to its attributes. You must add each
port individually.
Note: If you have an E3 ATM function processor, do not add a port if it
will not be used. Unused ports should not be provisioned.
add lp/<n> <port>/<m>
where:
<port> is DS3 or E3, the type of port
<m> is 0, 1, or 2, the number of the port being added
The interface has default values assigned to its attributes. The set
command can be used to change specic attributes.
When the ports are added mandatory subcomponents ATMCell and Test
will be automatically added under the DS3 and E3 components. For an
E3 port, the subcomponent G832 is automatically added.
12 Set provisionable attributes.
set lp/<n> <port>/<m> <attribute> <attributevalue>
where:
<attribute> is one of the provisionable attributes described in
Provisionable DS3 and E3 ATM components and attributes on
page 351.
<m> is the port number
Some examples follow.
If the port is a DS3 port, C-Bit Parity mode is automatically provisioned for
3 port Atm-based DS3 cards. If you do not wish to use C-Bit Parity mode,
use the command
set lp/<n> DS3/<m> cBitParity OFF
Cells are directly mapped into the DS3 or E3 payloads by default for the
3 port ATM-based DS3 and E3 cards. You can use plcp cell mapping
instead of the default direct mapping for a port on either a DS3 or an E3
card. Use the command
set lp/<n> E3/<m> mapping PLCP
Processor card provisioning 355
Passport Operations and Maintenance Guide 4S3
The mapping affects the reference source used when line clocking source
is selected. For direct mapping, the clock is recovered from the received
DS3 or E3 bitstream at 44.736 MHz or 34.368 MHz. For plcp mapping,
the clock is recovered from the received PLCP framing at 8 kHz.
For 3 port E3 ATM-based cards, the framing format dened by ITU-
T G.832 is used by default, although the older format dened by ITU-T
G.751 is still available. If the port is an E3 port, and you wish to use the
older framing format dened in ITU-T G.751, use the command
set lp/<n> E3/<m> framing g751
After setting the framing format to G751, the G832 component
(automatically generated when the VCC is created) must be deleted.
The cell payload is scrambled by default, according to ITU-T
Recommendation I.432. You can turn cell payload scrambling off for a
port on an ATM card. Use the command
set lp/<n> DS3/<m> cell scrambleCellPayload off
Note 1: When cell payload scrambling is turned off for ATM ports, there
is a possibility of false cell header delineation errors.
Note 2: For more information on these, and other, components and
provisionable attributes see 241-7501-210, Passport Components.
13 Perform a semantic check on the provisioning data.
check prov
14 Save the new view to disk
save prov
15 Activate the provisioning data
activate prov
Note: The editing view becomes the current view which the node uses,
when this command is used.
16 Conrm the activation.
confirm prov
17 Exit from provisioning mode.
end prov
356 Chapter 11
241-7001-150 4S3
Note: For instructions on testing hardware after it is installed, see
"Diagnostic tests" on page 523. There is a list of diagnostic tests that you
can perform on DS3 and E3 ATM cards in Component tests on function
processors on page 527.
The ports are now provisioned but still must be linked to an ATM Interface
before each is available for use in providing any service. For information on
linking to and provisioning an AtmInterface component see 241-7001-700,
Passport ATM Core Services User Guide.
Provisioning OC3 function processors
This section contains instructions for provisioning OC-3 ATM cards and
ports using an ASCII text interface device.
Provisionable OC3 attributes
Components and attributes to be provisioned on an OC-3 ATM card on
page 357 shows provisionable components and attributes for OC-3 ATM
function processors. For detailed information about provisionable attributes,
see 241-7501-210, Passport Components.
Processor card provisioning 357
Passport Operations and Maintenance Guide 4S3
Figure 50
Components and attributes to be provisioned on an OC-3 ATM card
clockingSource
Path
Path
clockingSource
AtmCell
applicationFramerName
scrambleCellPayload
alarmActDelay
AtmCell
applicationFramerName
Sdh
Sonet
LP
vendor
commentText
vendor
commentText
AdminInfo
Provisioned (Prov)
CustomerIdentierData (CidData)
customerIdentier
AdminInfo
CustomerIdentierData (CidData)
customerIdentier
Provisioned (Prov)
Provisioned (Prov)
CustomerIdentierData (CidData)
customerIdentier
Provisioned (Prov)
CustomerIdentierData (CidData)
customerIdentier
Provisioned (Prov)
Root
scrambleCellPayload
alarmActDelay
Provisioned (Prov)
358 Chapter 11
241-7001-150 4S3
Provisioning an OC3 card and its logical processors and
ports
This section explains how to provision a new OC-3 ATM function processor
using a text interface device. For a full description of any component or
attribute, see 241-7501-210, Passport Components.
Note: The required conguration is loaded on the card only when you
use the activate command in provisioning mode. For detailed
information about logical processors, see "Logical processors and logical
processor types" on page 179.
Procedure 78
Provisioning a new OC-3 ATM function processor and its LP and port
1 Enter provisioning mode.
start prov
2 Use the display command to see which cards are currently congured.
display shelf card/*
For more information on the display command, see "Operator
commands" on page 57.
3 If the card does not already exist, add it to the shelf.
add shelf card/<n>
where:
<n> is the slot number and can be between 1 and 15 for function
processors.
4 Provision the new processor card by setting the Card component
cardType attribute.
set shelf card/<n> cardType <cardtype>
where:
<n>, the slot number, can be between 1 and 15 for function processors.
<cardtype> is 3pOC3MmAtm or 3pOC3SmAtm
5 Use the display command to verify that you have provisioned the card
properly.
display shelf card/*
6 To determine which software features the LP will run, an LPType
component must be associated with the LP. To use the OC-3 ATM FP, the
Processor card provisioning 359
Passport Operations and Maintenance Guide 4S3
LP type must contain one of the features supported for LPs attached to
OC-3 cards, that is atmTrunks and/or atmBearerService.
If a suitable LP type does not exist already, provision a new LP type (LPT)
by adding a logical processor type component and set its featureList
attribute.
To determine the LPTs which exist already use the command:
l sw lpt/*
To add an LPT.
add SW lpt/<lpt name>
set SW lpt/<lpt name> FeatureList <feature1>
<feature2> <feature3>
where:
<LPT Name> can contain up to 25 alphanumeric characters. This name
is customer-dened.
Note: The features supported for LPs attached to OC-3 cards are
porsTrunks, atmTrunks, and atmBearerService.
7 Provision a new LP to run the selected logical processor type software on
the processor card. To do this, add a Logical Processor component and
complete the appropriate provisioning.
add lp/<n>
where:
<n> can be set to any number between 1 and 15. For consistency, the
recommended value of <n> is the slot number the card is in.
8 Set the mainCard attribute to tell the system which slot to associate with
which LP.
set lp/<n> mainCard Shelf Card/<m>
where:
<m> is the number of the Card component, which should be set to the slot
number for consistency. That is, <m> should equal <n>.
9 Set the logicalProcessorType attribute to use the feature set dened by
<lpt name> as determined in step 3.
set lp/<n> logicalProcessorType sw lpt/<lpt name>
10 Set the CID attribute (optional).
set lp/<n> cid <CID>
360 Chapter 11
241-7001-150 4S3
where:
<CID> is the customer identier. The customer identier constrains the
user to those components that belong to the same customer identier.
This can be set to any number between 0 and 8191. Default is 0. Only
users with a CID of 0 are permitted to carry out provisioning procedures.
For more information about CID see Userid and its attributes on
page 207.
11 Add a port depending on the type of interface required. The interface has
default values assigned to its attributes.
add lp/<n> <port>/<m>
where:
<port> is SONET or SDH
<m> is the port number 0, 1, or 2.
The interface has default values assigned to its attributes. The set
command can be used to change specic attributes.
Subcomponents Path, Test (both under Sonet), and ATMCell (under
Path) will be automatically created when a new port is added and
activated.
12 Set SONET or SDH provisionable attributes.
set lp/<n> <port>/<m> <attribute> <attributevalue>
where:
<port> is SONET or SDH
<m> is the port number 0, 1, or 2
<attribute> is one of the provisionable attributes listed in
Components and attributes to be provisioned on an OC-3 ATM card on
page 357.
An example follows.
The cell payload is scrambled by default, according to ITU-T
Recommendation I.432. You can turn cell payload scrambling off for a
port on an ATM card. Use the command
set lp/<n> DS3/<m> cell scrambleCellPayload off
Note: When cell payload scrambling is turned off for ATM ports, there is
a possibility of false cell header delineation errors.
13 Set SONET or SDH Path component attributes.
set lp/<n> <port>/<m> path/0 <attribute> <attributevalue>
Processor card provisioning 361
Passport Operations and Maintenance Guide 4S3
where:
<port> is SONET or SDH
<attribute> is one of the provisionable Path component attributes
14 Set SONET or SDH Path ATMCell component attributes.
set lp/<n> <port>/<m> path/0 cell <attribute>
<attributevalue>
where:
<port> is SONET or SDH
<attribute> is one of the provisionable Path ATMCell component
attributes
15 Perform a semantic check on the provisioning data.
check prov
16 Activate the provisioning data
activate prov
Note: The editing view becomes the current view when this command is
used.
17 Conrm the activation.
confirm prov
18 Save the new view to disk.
save prov
19 Commit the new view.
commit prov
20 Exit from provisioning mode.
end prov
Note: For instructions on testing hardware after it is installed, see
"Diagnostic tests" on page 523. There is a list of diagnostic tests that you
can perform on OC3M cards in Component tests on function processors
on page 527.
The ports are now provisioned but still must be linked to an ATM Interface
before each is available for use in providing any service. For information on
linking to and provisioning an AtmInterface component see 241-7001-700,
Passport ATM Core Services User Guide.
362 Chapter 11
241-7001-150 4S3
Provisioning AAL1 function processors
This section contains instructions for provisioning DS1 AAL1 and E1 AAL1
function processors, LPs, and ports using an ASCII text interface device.
You only need to provision new function processors. Replacement function
processors do not need to be provisioned.
Note: Before you perform the procedure in this section, you should be
familiar with the provisioning fundamentals explained in Provisioning
system description on page 85.
Provisionable AAL1 attributes
Provisionable DS1 AAL1 components and attributes on page 363 and
Provisionable E1 AAL1 components and attributes on page 364 shows
provisionable components and attributes for DS1 AAL1 and E1 AAL1
function processors. For detailed information about provisionable attributes,
see 241-7501-210, Passport Components.
Processor card provisioning 363
Passport Operations and Maintenance Guide 4S3
Figure 51
Provisionable DS1 AAL1 components and attributes
Root
LP
LP
DS1 AAL1
Channel (Chan) component
Provisioned (Prov) group
lineType
zeroCoding
clockingSource
raiAlarmType
lineLength
CustomerIdentierData (CidData)
vendor
commonText
Provisioned (Prov) group
timeslots (ts)
timeslotDataRate
applicationFramerName
TrunkConditioning
replacementData
signalOneDuration
signalOne
signalTwo
364 Chapter 11
241-7001-150 4S3
Figure 52
Provisionable E1 AAL1 components and attributes
The provisionable attributes for a port on a DS1 AAL1 FP are shown in
Table 36. The provisionable attributes for a port on an E1 AAL1 FP are
shown in Table 37.
Note: For detailed information about provisionable attributes, see
241-7501-210, Passport Components.
Root
LP
LP
E1 AAL1
Channel (Chan) component
Provisioned (Prov) group
lineType
clockingSource
crc4Mode
sendRaiOnAis
CustomerIdentierData (CidData)
vendor
commonText
Provisioned (Prov) group
timeslots (ts)
timeslotDataRate
applicationFramerName
TrunkConditioning
replacementData
signalOneDuration
signalOne
signalTwo
Processor card provisioning 365
Passport Operations and Maintenance Guide 4S3
Table 36
Provisionable attributes for a port on a DS1 AAL1 FP
Attribute Values Description
clockingSources module (DEFAULT if
Network Clock
Synchronization
component is
provisioned)
Uses the clock from the
Passport backplane that is
phase-locked to the CP
reference clock. It is
recommended that this value
should always be used,
unless local testing is being
performed.
Note: The clocking source
must be set to module at
both ends of the service.
local (DEFAULT if
Network Clock
Synchronization
component is not
provisioned
Uses the local oscillator on
the FP for the transmit port.
line Uses the clock recovered
from the receive line data on
the FP.
otherPort Uses the clock mode
selected for one of the other
ports. This option is only
valid when line has been
selected for one of the other
ports.
srts Uses the synchronous
Residual Time Stamp
(SRTS) in the AAL1 cell to
regenerate the transmit
clock based on the primary
reference clock in the
Passport switch. This option
is valid only for unstructured
AAL1 data services.
lineType esf (DEFAULT) 24 frames per multiframe.
(Sheet 1 of 3)
366 Chapter 11
241-7001-150 4S3
d4 D4 framing, 12 frames per
superframe.
d4Cas D4 framing, 12 frames per
superframe with CAS
unframed Data has no frame structure.
esfCas 24 frames per multiframe
with CAS.
raiAlarmType fdl (DEFAULT)
SBit
Uses the Facility Data Link
(FDL) for the alarm, by
sending a repeated pattern
of eight 0s followed by eight
1s on the FDL link.
Note: This value is only
valid for a line type of esf or
esfCas.
This attribute is not
supported for AAL1 FPs.
Bit2 RAI is sent by setting bit 2 in
all timeslots to 0.
zeroCoding b8zs (DEFAULT) Any string of eight
consecutive 0s to be
replaced with the B8ZS
code.
bit7stuffing Bit 7 of an all 0 channel
byte replaced by a 1.
AMI AMI with no zero code
suppression.
lineLength 0-655 feet (DEFAULT
is 0)
Table 36 (continued)
Provisionable attributes for a port on a DS1 AAL1 FP (continued)
Attribute Values Description
(Sheet 2 of 3)
Processor card provisioning 367
Passport Operations and Maintenance Guide 4S3
timeslots 1 to 24 A list of timeslots used by the
CHAN component. For DS1
AAL1 unstructured service,
all timeslots are used
(1, 2, 3, ...24).
replacementData 8-bit value
recommended values
for DS1 are 0x7F (idle)
and 0x1A (OOS)
The trunk conditioning
(defined in the TC
component) that is applied to
the timeslots selected for the
CHAN component under
fault conditions for structured
services.
signalOneDuration integer value from 0 to
60 seconds (0 is
DEFAULT)
Defines the duration for
which signalOne data is
transmitted during fault
conditions in the CHAN
timeslots with CAS line
types.
signalOne 4-bit vector, in which
each bit is set to 0 or 1
(1111 is DEFAULT)
with a line type of
d4Cas, the only valid
values are 0101, 1010,
1111, or 0000
Data value inserted into the
ABCD signalling bits for the
CAS timeslots under fault
conditions. This data is
transmitted for the length of
time specified by the
signalOneDuration attribute.
signalTwo 4-bit vector, in which
each bit is set to 0 or 1
(1111 is DEFAULT)
with a line type of
d4Cas, the only valid
values are 0101, 1010,
1111, or 0000
Data value inserted into the
ABCD signalling bits for the
CAS timeslots under fault
conditions. This data is
transmitted after the time
provisioned in
signalOneDuration has
expired.
Table 36 (continued)
Provisionable attributes for a port on a DS1 AAL1 FP (continued)
Attribute Values Description
(Sheet 3 of 3)
368 Chapter 11
241-7001-150 4S3
Table 37
Provisionable attributes for a port on an E1 AAL1 FP
Attribute Values Description
Clocking Sources module (DEFAULT if
Network Clock
Synchronization
component is
provisioned)
Same as DS1 Clocking
sources, described in
Table 36.
line (DEFAULT if
Network Clock
Synchronization
component is not
provisioned)
local
otherPort
srts Uses the synchronous
Residual Time Stamp
(SRTS) in the AAL1 cell to
regenerate the transmit
clock based on the primary
reference clock in the
Passport switch. This option
is valid only for unstructured
AAL1 data services.
lineType unframed
cas (DEFAULT)
Data has no frame structure.
Timeslot 16 is reserved for
multiframe signaling. Only
30 timeslots are available for
data.
ccs Timeslot 16 is available for
data. (CCS is not processed
on AAL1 FPs.)
Note: For each lineType; the
contents of all timeslots,
including TS 16, are carried
transparently.
(Sheet 1 of 3)
Processor card provisioning 369
Passport Operations and Maintenance Guide 4S3
CRC4Mode off (DEFAULT) If the lineType is unframed,
and unstructured
performance monitoring
mode is in use, set this
attribute to off.
on If the lineType is cas or ccs,
and CRC4 error checking is
enabled (for example, on
equipment outside of the
Passport subnet), set this
attribute to on.
sendRaiOnAis yes (DEFAULT)
no
Remote alarm is sent when
an AIS alarm is received.
Remote alarm is not sent
when an AIS alarm is
received.
timeslots 1 to 31 A list of timeslots used by the
CHAN component. For E1
AAL1 unstructured service,
all timeslots are used
(1, 2, 3, ...31). The framing
bits (timeslot 0) are carried
but not represented.
replacementData 8-bit value
recommended values
for E1 are 0x54 (idle)
and 0xFF (OOS)
The trunk conditioning
(defined in the TC
component) that is applied to
the timeslots selected for the
CHAN component under
fault conditions for structured
services.
Table 37 (continued)
Provisionable attributes for a port on an E1 AAL1 FP (continued)
Attribute Values Description
(Sheet 2 of 3)
370 Chapter 11
241-7001-150 4S3
Provisioning an AAL1 function processor and its logical
processors and ports
Procedure 79 explains how to provision a new DS1 AAL1 or E1 AAL1
function processor using a text interface device.
Note: For detailed information about logical processors, see Logical
processors and logical processor types on page 179.
Procedure 79
Provisioning a 4-port DS1 AAL1 or 4-port E1 AAL1 function processor
and its LPs and ports
1 Enter provisioning mode.
start prov
signalOneDuration integer value from 0 to
60 seconds (0 is
DEFAULT)
Defines the duration for
which signalOne data is
transmitted during fault
conditions in the CHAN
timeslots with CAS line
types.
signalOne 4-bit vector, in which
each bit is set to 0 or 1
(1111 is DEFAULT)
Data value inserted into the
ABCD signalling bits for the
CAS timeslots under fault
conditions. This data is
transmitted for the length of
time specified by the
signalOneDuration attribute.
signalTwo 4-bit vector, in which
each bit is set to 0 or 1
(1111 is DEFAULT)
Data value inserted into the
ABCD signalling bits for the
CAS timeslots under fault
conditions. This data is
transmitted after the time
provisioned in
signalOneDuration has
expired.
Table 37 (continued)
Provisionable attributes for a port on an E1 AAL1 FP (continued)
Attribute Values Description
(Sheet 3 of 3)
Processor card provisioning 371
Passport Operations and Maintenance Guide 4S3
2 Use the display command to see which cards are currently congured.
display shelf card/*
For more information on the display command, see "Operator
commands" on page 57.
3 If the card does not already exist, add it to the shelf.
add shelf card/<n>
where:
<n> is the slot number and can be between 1 and 15 for function
processors.
4 Provision the new FP by setting the Card component cardType attribute.
set shelf card/<n> cardType <cardtype>
where:
<n>, the slot number, can be between 1 and 14 for function processors
<cardtype> is 4pDS1Aal1 or 4pE1Aal1.
5 If a suitable LP type does not exist already, provision a new LP type (LPT)
by adding a logical processor type component and set its featureList
attribute.
To determine the LPTs which exist already use the command:
l sw lpt/*
Add an LPT. Note that the feature list for the AAL1 FP is null. This ensures
that the FP only picks up the base software (which is all that it needs).
add sw lpt/<lpt name>
set sw lpt/<lpt name> FeatureList !
where:
<LPT Name> can contain up to 25 alphanumeric characters. This name
is customer dened. The LPT determines which software or feature the
LP will run.
6 Provision new LPs to run the selected logical processor type software on
the function processor. To do this, add a Logical Processor component
and complete the appropriate provisioning.
add lp/<n>
where:
<n> can be set to any number between 1 and 14.
372 Chapter 11
241-7001-150 4S3
7 Set the mainCard attribute to tell the system which slot to associate with
which LP.
set lp/<n> mainCard Shelf Card/<m>
where:
<m> is the number of the function processor slot. For example, to link to
card1, enter 1 as the <m> value.
8 Set the logicalProcessorType attribute to use the feature set dened by
<lpt name>.
set lp/<n> lpt sw lpt/<lpt name>
where:
<lpt name> must match that dened in step 5.
9 Set the CID attribute (optional).
set lp/<n> cid <CID>
where:
<CID> is the customer identier. The customer identier constrains the
user to those components that belong to the same customer identier.
This can be set to any number between 0 and 8191. Only users with a CID
of 0 are permitted to carry out provisioning procedures. For more
information about CID see Node security on page 205.
10 Add a port depending on the type of interface required. The interface has
default values assigned to its attributes.
add lp/<n> <port>/<m>
where:
<n> is the LP number
<port> is DS1 or E1
<m> is the number of the port being added, and must be 0 to 3.
The interface has default values assigned to its attributes. The set
command can be used to change specic attributes.
Mandatory subcomponents will automatically be added for the selected
port. For DS1 or E1 components, a Chan component will be added which
has channel number 0 (that is, Chan/0). If Chan/0 is unacceptable to the
user, it will be necessary to delete it and add an appropriate alternative,
as follows:
delete lp/<n> <port>/<m> chan/0
add lp/<n> <port>/<m> chan/<q>
Processor card provisioning 373
Passport Operations and Maintenance Guide 4S3
where:
<q> is the number of the chan being added, between 0 and 23 for DS1,
and between 0 and 30 for E1.
11 Set provisionable attributes.
set lp/<n> <port>/<m> <attribute> <attributevalue>
where:
<attribute> is one of the provisionable attributes described in Table 36
on page 365 or Table 37 on page 368.
<m> is the port number
12 The channel component (chan) must be assigned timeslots using the set
command. For unstructured services, all timeslots must be provisioned.
For a DS1 function processor:
set lp/<n> ds1/<m> chan/<q> timeslots 1 2 3 4 5 6 7 8
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
For an E1 function processor:
set lp/<n> e1/<m> chan/<q> timeslots 1 2 3 4 5 6 7 8 9
10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
28 29 30 31
13 If the service type is structured, add a TC (trunk conditioning) component
to the chan component.
add lp/<n> chan/<p> tc
At this point the FP has one port provisioned and is ready to have an AAL1
service added.
Note: For instructions on testing hardware after it is installed, see
Diagnostic tests on page 523.
Provisioning DS1 and E1 Voice function processors
This section contains instructions for provisioning DS1 and E1 voice function
processors and ports using an ASCII text interface device.
If you want to provision a new DS1 or E1 voice function processor and its
ports using Architect for Passport on an NMS workstation, see 241-6001-023,
NMS Architect for Passport User Guide.
374 Chapter 11
241-7001-150 4S3
Provisionable DS1 and E1 Voice attributes
Provisionable DS1 voice components and attributes on page 374 and
Provisionable E1 voice components and attributes on page 375 show
provisionable components and attributes for DS1 and E1 voice function
processors. For detailed information about provisionable attributes, see
241-7501-210, Passport Components.
Figure 53
Provisionable DS1 voice components and attributes
Root
LP
LP
DS1
Provisioned (Prov)
lineType
zeroCoding
clockingSource
raiAlarmType
lineLength
CustomerIdentierData (CidData)
customerIdentier
AdminInfo (AdminInfo)
vendor
commentText
Channel (Chan)
Provisioned (Prov)
timeSlots
applicationFramerName
CustomerIdentierData (CidData)
customerIdentier
Processor card provisioning 375
Passport Operations and Maintenance Guide 4S3
Figure 54
Provisionable E1 voice components and attributes
Provisioning a new DS1 or E1 Voice function processor and
its logical processors and ports
This section explains how to provision a new DS1 or E1 voice processor card
and its ports using a text interface device or an NMS workstation command
console.
Note: The logical processor is loaded on the card only when you use the
activate command in provisioning mode.
Procedure 80
Provisioning a DS1 or E1 voice function processor and its ports
1 Start provisioning mode.
start prov
Root
LP
LP
E1
Provisioned (Prov)
lineType
clockingSource
crc4Mode
CustomerIdentierData (CidData)
customerIdentier
AdminInfo (AdminInfo)
vendor
commentText
Channel (Chan)
Provisioned (Prov)
timeSlots
applicationFramerName
CustomerIdentierData (CidData)
customerIdentier
376 Chapter 11
241-7001-150 4S3
2 Use the display command to see which cards are currently congured.
display shelf card/*
For more information on the display command, see "Operator
commands" on page 57.
3 If the card does not already exist, add it to the shelf.
add shelf card/<n>
where:
<n> is the slot number and can be between 1 and 15 for function
processors.
4 Provision the new processor card by setting the Card component
cardType attribute.
set shelf card/<n> cardType <card type>
where:
<n>, the slot number, can be between 1 and 15 for function processors.
<card type> is 1pDS1V or 1pE1V.
5 If a suitable logical processor type does not exist already, provision a new
logical processor type (LPT) by adding a logical processor type
component and set its featureList attribute.
add SW lpt/<LPT Name>
set SW lpt/<LPT Name> FeatureList <feature1>
<feature2> <featurE1V>
where <LPT Name> can contain up to 25 alphanumeric characters. This
name is customer dened. The LPT determines which software or feature
this LP will run.
Note: The featureList attribute <feature> is described in the related
service user guide. (For more information on a particular featureList
attribute, see the appropriate service guide. If you are using paper-based
version of the Passport documentation library, see the 241-7001-000,
Passport Documentation Guide for a complete list of Passport
documents. If you are using an on-line version of the library, see the
Passport InfoMap, which will provide you with links to other documents).
6 Provision a new logical processor (LP) to run the selected logical
processor type software on the processor card. To do this, add a Logical
Processor component and complete the appropriate provisioning.
add lp/<n>
where <n> can be set to any number between 1 and 15.
Processor card provisioning 377
Passport Operations and Maintenance Guide 4S3
7 Add a port depending on the type of interface required. The interface has
default values assigned to its attributes.
add lp/<n> <port>/<m>
where:
<port> is DS1 or E1. The interface has default values assigned to its
attributes. The set command can be used to change specic attributes.
<m> must be set to 0 for 1pDS1V or 1pE1V cards.
8 Add a Channel component to the DS1 or E1 port.
add lp/<n> <port>/<m> chan/<p>
where <p> can be set from 0 to 23 for 1pDS1V and 0 to 30 for 1pE1V.
9 Assign timeslots to the Channel component.
set lp/<n> <port>/<m> chan/<p> timeslots <timeslots>
where <timeslots> can be a set of numbers between 1 and 24 for 1pDS1V
and between 1 and 31 for 1pE1V. Typically each channel is associated
with one timeslot.
10 Set the mainCard attribute.
set lp/<n> mainCard Shelf Card/<m>
where <m> is the number of the Card component. For example, to link to
card1, enter 1 as the <m> value.
11 Set the spareCard attribute (optional).
set lp/<n> spareCard Shelf Card/<m>
where <m> is the number of the Card component.
12 Set the logicalProcessorType attribute.
set lp/<n> lpt SW lpt/<lpt name>
where <lpt name> can contain up to 25 alphanumeric characters.
13 Set the CID attribute (optional).
set lp/<n> cid <CID>
where <CID> is the customer identier. The customer identier constrains
the user to those components that belong to the same customer identier.
This can be set to any number between 0 and 8191.
378 Chapter 11
241-7001-150 4S3
14 Add an application component and complete the appropriate
provisioning. The application component varies depending on the
application that you are adding.
add <application>/<n>
where <application> can be set to trunks or DpnGateway.
where <n> is any user-dened integer between 0 and 200 that is assigned
to an application.
Note: A Framer component is added automatically when the application
is added. The framer component has default values assigned to its
attributes. Use the set command to change specic attributes.
15 Link the application(s) to the port.
set BTDS/<n> framer interfaceName
set VS/<n> framer interfaceName
16 Perform a semantic check on the provisioning data.
check prov
17 Save the new view to disk.
save prov
18 Activate the provisioning data.
activate prov
Note: The editing view becomes the current view when this command is
used.
19 Conrm the activation.
confirm prov
20 Exit from provisioning mode.
end prov
Note: For instructions on testing hardware after it is installed, see
"Diagnostic tests" on page 523.
Processor card provisioning 379
Passport Operations and Maintenance Guide 4S3
Provisioning J2MV function processors
This section contains instructions for provisioning J2MV function processors
and ports using an ASCII text interface device.
If you want to provision a new J2MV function processor and its ports using
Architect for Passport on an NMS workstation, see 241-6001-023, NMS
Architect for Passport User Guide.
Provisionable J2MV attributes
Provisionable J2MV components and attributes on page 379 shows
provisionable components and attributes for J2MV function processors. For
detailed information about provisionable attributes, see 241-7501-210,
Passport Components.
Figure 55
Provisionable J2MV components and attributes
Root
LP
LP
E1
Provisioned (Prov)
lineType
clockingSource
crc4Mode
CustomerIdentierData (CidData)
customerIdentier
AdminInfo (AdminInfo)
vendor
commentText
Channel (Chan)
Provisioned (Prov)
timeSlots
applicationFramerName
CustomerIdentierData (CidData)
customerIdentier
380 Chapter 11
241-7001-150 4S3
Note: A J2MV card is provisioned to use an E1 port with CAS, A-bit
signalling, and CRC4 off. The J2MV function processor converts TTC
protocol to E1 and vice versa.
Provisioning new J2MV function processors and its logical
processors and ports
This section explains how to provision a new J2MV processor card and its
ports using a text interface device or an NMS workstation command console.
Note: The logical processor is loaded on the card only when you use the
activate command in provisioning mode.
Procedure 81
Provisioning a new J2MV function processor and its port
1 Start provisioning mode.
start prov
2 Use the display command to see which cards are currently congured.
display shelf card/*
For more information on the display command, see "Operator
commands" on page 57.
3 If the card does not already exist, add it to the shelf.
add shelf card/<n>
where:
<n> is the slot number and can be between 1 and 15 for function
processors.
4 Provision the new processor card by setting the Card component
cardType attribute.
set shelf card/<n> cardType <card type>
where: <n>, the slot number, can be between 1 and 15 for function
processors.
<card type> is J2MV.
5 If a suitable logical processor type does not exist already, provision a new
logical processor type (LPT) by adding a logical processor type
component and set its featureList attribute.
add SW lpt/<LPT Name>
Processor card provisioning 381
Passport Operations and Maintenance Guide 4S3
set SW lpt/<LPT Name> FeatureList <feature1>
<feature2> <featurE1V>
where <LPT Name> can contain up to 25 alphanumeric characters. This
name is customer dened. The LPT determines which software or feature
this LP will run.
Note: The featureList attribute <feature> is described in the related
service user guide. (For more information on a particular featureList
attribute, see the appropriate service guide. If you are using paper-based
version of the Passport documentation library, see the 241-7001-000,
Passport Documentation Guide for a complete list of Passport
documents. If you are using an on-line version of the library, see the
Passport InfoMap, which will provide you with links to other documents).
6 Provision a new logical processor (LP) to run the selected logical
processor type software on the processor card. To do this, add a Logical
Processor component and complete the appropriate provisioning.
add lp/<n>
where <n> can be set to any number between 1 and 15.
7 Add a port depending on the type of interface required. The interface has
default values assigned to its attributes.
add lp/<n> <port>/<m>
where:
<port> is E1. The interface has default values assigned to its attributes.
The set command can be used to change specic attributes.
<m> must be set to 0 for J2MV card.
Note: Chan/0 is added by the system when lp/<n>E1/0 is added.
8 Add a Channel component to the E1 port.
add lp/<n> <port>/<m> chan/<p>
where <p> can be set from 0 to 30.
9 Assign timeslots to the Channel component.
set lp/<n> <port>/<m> chan/<p> timeslots <timeslots>
where <timeslots> can be a set of numbers between 1 and 31. Typically
each channel is associated with one timeslot.
Note: Timeslot 16 is reserved and should not be used.
382 Chapter 11
241-7001-150 4S3
10 Set the mainCard attribute.
set lp/<n> mainCard Shelf Card/<m>
where <m> is the number of the Card component. For example, to link to
card1, enter 1 as the <m> value.
11 Set the logicalProcessorType attribute.
set lp/<n> lpt SW lpt/<lpt name>
where <lpt name> can contain up to 25 alphanumeric characters.
12 Set the CID attribute (optional).
set lp/<n> cid <CID>
where <CID> is the customer identier. The customer identier constrains
the user to those components that belong to the same customer identier.
This can be set to any number between 0 and 8191.
13 Add an application component and complete the appropriate
provisioning. The application component varies depending on the
application that you are adding.
add <application>/<n>
where <application> can be set to Vs or BTDS.
where <n> is any user-dened integer between 0 and 99999 that is
assigned to an application.
Note: A Framer component is added automatically when the application
is added. The framer component has default values assigned to its
attributes. Use the set command to change specic attributes.
14 Link the application(s) to the port.
set BTDS/<n> framer interfaceName
set VS/<n> framer interfaceName
set VS/<n> plc remotename EM/xxxxx
set VS/<n> framer transportsignalling yes
15 Perform a semantic check on the provisioning data.
check prov
16 Save the new view to disk
save prov
17 Activate the provisioning data
Processor card provisioning 383
Passport Operations and Maintenance Guide 4S3
activate prov
Note: The editing view becomes the current view when this command is
used.
18 Conrm the activation.
confirm prov
19 Exit from provisioning mode.
end prov
Note: For instructions on testing hardware after it is installed, see
"Diagnostic tests" on page 523. There is a list of diagnostic tests that you
can perform on J2MV cards in Component tests on function processors
on page 527.
Provisioning the Ethernet function processor
This section contains instructions for provisioning the Ethernet function
processor (FP), logical processors (LPs), and ports using an ASCII text
interface device. Provisionable attributes
Provisionable Ethernet attributes
Provisionable attributes for the Ethernet function processor on page 384
shows the provisionable components and attributes for Ethernet function
processors. For detailed information about provisionable attributes, see
241-7501-210, Passport Components.
384 Chapter 11
241-7001-150 4S3
Figure 56
Provisionable attributes for the Ethernet function processor
Root
Lp
En
Customer IdentifierData (CidData)
customerIdentifier
ifEntryProv (ifEntry)
IfAdminStatus
ifIndex (iFI)
Provisioned (Prov)
heartbeaPacket
applicationFramerName
AdminInfo (AdminInfo)
vendor
commentText
DebugProv
defaultTraceLevel
La
CustomerIdentifierData (CIdData)
customerIdentifier (cid)
MediaProvisioned (MediaProv)
linkToProtocolPort
ifEntryProv (ifEntryProv)
ifAdminStatus
ifIndex
Framer
Provisioned (Prov)
interfaceName
Processor card provisioning 385
Passport Operations and Maintenance Guide 4S3
Provisioning an Ethernet card and its logical processors and
ports
This section explains how to provision a new Ethernet function processor
using a text interface device.
Note: The required congurations are loaded on the card only when you
use the activate command in provisioning mode. For detailed
information about logical processors, see "Logical processors and logical
processor types" on page 179.
Procedure 82
Provisioning an Ethernet function processor and its LPs and ports
1 Enter provisioning mode
start prov
2 Use the display command to see which cards are currently congured.
display shelf card/*
For more information on the display command, see "Operator
commands" on page 57.
3 If the card does not already exist, add it to the shelf.
add shelf card/<n>
where:
<n> is the slot number and can be between 1 and 15 for function
processors.
4 Provision the new processor card by setting the Card component
cardType attribute.
set shelf card/<n> cardType <cardtype>
where:
<n>, the slot number, is between 1 and 15
<cardtype> is Ethernet 10BASE-T (6pEth10BaseT).
5 If a suitable logical processor type (LPT) does not exist already, provision
a new LPT by adding a logical processor type component and set its
featureList attribute.
add sw lpt/<lpt_name>
set sw lpt/<lpt_name> featureList <feature1>
<feature2> <feature3> ...
386 Chapter 11
241-7001-150 4S3
where:
<lpt_name> can contain up to 25 alphanumeric characters. This name
is customer dened. The LPT determines which software or feature the
LP will run.
<feature_x> identies the feature list attribute
Note: The featureList attribute <feature> is described in the related
service user guide. (For more information on a particular featureList
attribute, see the appropriate service guide. If you are using paper-based
version of the Passport documentation library, see the 241-7001-000,
Passport Documentation Guide for a complete list of Passport
documents. If you are using an on-line version of the library, see the
Passport InfoMap, which will provide you with links to other documents).
6 Provision new LPs to run the selected logical processor type software on
the processor card. To do this, add a LP component and complete the
appropriate provisioning.
add lp/<n>
where:
<n> is the instance number of the FP
7 If the card you are provisioning is the main card, set the mainCard
attribute.
set lp/<n> mainCard shelf card/<m>
where:
<n> is the number of the LP
<m> is the number of the card slot. For example, to link to card1, enter 1
as the m value.
or
If the card you are provisioning is to be a spare card, set the spareCard
attribute.
set lp/<n> spareCard shelf card/<m>
where:
<n> is the number of the LP
<m> is the number of the card slot.
8 Set the logicalProcessorType attribute
set lp/<n> lpt sw lpt/<lpt_name>
where:
<n> is the LP number
Processor card provisioning 387
Passport Operations and Maintenance Guide 4S3
<lpt_name> can contain up to 25 alphanumeric characters (see the
service guides for additional information).
9 Set the CID attribute (optional)
set lp/<n> cid <cid>
where:
<n> is the LP number
<cid> is the customer identier. The customer identier constrains the
user to those components that belong to the same customer identier.
This can be set to any number between 0 and 8191.
10 Add a port for each physical interface. The interface has default values
assigned to its attributes.
add lp/<n> en/<m>
where:
<n> is the LP number
<m> is the port number (can be set to any number between 0 and 5). The
interface has default values assigned to its attributes. The set command
can be used to change specic attributes.
11 Add a LAN application component
add Lan/<value>
where:
<value> is a number in the range from 0 to 255. It is recommended that
the selected number represent the LP number and application port
number, for example 52, where 5 indicates the LP number and 2
indicates the port number.
12 Link the LAN application to the logical port
set lp/<n> en/<m> applicationFranerName Lan/<value>
Framer
or
set Lan/<value> Framer interfaceName lp/<x> en/<y>
where:
<n> is the LP number
<m> is the port number
<value> is a number in the range from 0 to 255
<x> is the LP number
<y> is the port number (must be set in the range from 0 to 5)
388 Chapter 11
241-7001-150 4S3
The applicationFramerName attribute contains the component name of
the Framer (Lan/<value> Framer) that is associated with the Ethernet
component.
13 Add a virtual router
add vr/<vr_name>
where:
<vr_name> is the name assigned to this instance of the virtual router.
The instance value is an alphanumeric string up to 20 characters long.
The current release of Passport supports only one virtual router per node.
Its designation or name is usually the number 1
14 Add a protocol port
add vr/<vr_name> pp/<pp_id>
where:
<vr_name> is the name assigned to this instance of the virtual router
<pp_id> is the instance value ASCII string assigned to the protocol port
15 Link the LAN application to the physical port
set Lan/<value> linkToProtocolPort vr/<vr_name> pp/
<pp_id>
or
set vr/<vr_name> pp/pp_id> linkToMedia Lan/<value>
where:
<value> is a number in the range from 0 to 255
<vr_name> is the name assigned to this instance of the virtual router
<pp_id> is the instance value ASCII string assigned to the protocol port
16 Perform a semantic check on the provisioning data.
check prov
17 Activate the provisioning data
activate prov
Note: The editing view becomes the current view when this command is
used.
18 Conrm the activation.
confirm prov
19 Save the new view to disk
save prov
Processor card provisioning 389
Passport Operations and Maintenance Guide 4S3
20 Commit the new provisioning view after testing
commit prov
21 Exit from provisioning mode.
end prov
Note: For instructions on testing hardware after it is installed, see
"Diagnostic tests" on page 523. There is a list of diagnostic tests that you
can perform on the Ethernet card in Component tests on function
processors on page 527.
Provisioning the FDDI function processor
This section contains instructions for provisioning the FDDI functional
processor (FP), logical processors (LPs), and ports using an ASCII text
interface device.
Provisionable FDDI attributes
Provisionable FDDI components and attributes (Part 1) on page 390 and
Provisionable FDDI components and attributes (Part 2) on page 391 show
the provisionable components and attributes for the FDDI function processor.
For detailed information about provisionable attributes, see 241-7501-210,
Passport Components.
390 Chapter 11
241-7001-150 4S3
Figure 57
Provisionable FDDI components and attributes (Part 1)
Root
Lp
Fi
CustomerIdentifierData (CIdData)
customerIdentifier (cid)
IfEntryProv (IfEntry)
IfAdminStatus IfState)
IfIndex (IfI)
SmtProvisioned (SmtProv)
userData
acceptAa
acceptBb
acceptAs
acceptBs
acceptAm
acceptBm
useThruBa
fddimibSMTContPol
neighborNotifyInterval
statusReportPolicy
traceMaxExpirationTimer
MacProvisioned (MacProv)
tokenRequestTimer
tokenMaxTimer
validTransmissionTimer
fddimibMACFrmErrThreshold
fddimibMACUnitdataEnable
AdminInfo (AdminInfo)
vendor
commentText
DebugProv
defaultTraceLevel
Processor card provisioning 391
Passport Operations and Maintenance Guide 4S3
Figure 58
Provisionable FDDI components and attributes (Part 2)
PhysicalLayer (Phy)
Provisionable (Prov)
lerCutoff
lerAlarm
linkErrorMonitor
La
CustomerIdentifierData (CIdData)
customerIdentifier (cid)
MediaProvisioned (MediaProv)
linkToProtocolPort
ifEntryProv (ifEntryProv)
ifAdminStatus
ifIndex
Framer
Provisioned (Prov)
interfaceName
392 Chapter 11
241-7001-150 4S3
Provisioning a FDDI card and its logical processors and ports
This section explains how to provision a new FDDI function processor using
a text interface device.
Note: The required congurations are loaded on the card only when you
use the activate command in provisioning mode. For detailed
information about logical processors, see "Logical processors and logical
processor types" on page 179.
Procedure 83
Provisioning a FDDI function processor and its LP and port
1 Enter provisioning mode.
start prov
2 Use the display command to see which cards are currently congured.
display shelf card/*
For more information on the display command, see "Operator
commands" on page 57.
3 If the card does not already exist, add it to the shelf.
add shelf card/<n>
where:
<n> is the slot number and can be between 1 and 15 for function
processors.
4 Provision the new processor card by setting the Card component
cardType attribute.
set shelf card/<n> cardType <cardtype>
where:
<n>, the slot number, is between 1 and 15
<cardtype> is FDDI multimode (lpFddiMultimode) or single mode
(lpFddiSinglemode).
5 If a suitable logical processor type (LPT) does not exist already, provision
a new LPT by adding a logical processor type component and set its
featureList attribute.
add sw lpt/<lpt_name>
set sw lpt/<lpt_name> featureList <feature_1>
<feature_2> <feature_3> ...
Processor card provisioning 393
Passport Operations and Maintenance Guide 4S3
where:
<lpt_name> can contain up to 25 alphanumeric characters. This name
is customer dened. The LPT determines which software or feature the
LP will run.
<feature_x> identies the feature list attribute
Note: The featureList attribute <feature> is described in the related
service user guide. (For more information on a particular featureList
attribute, see the appropriate service guide. If you are using paper-based
version of the Passport documentation library, see the 241-7001-000,
Passport Documentation Guide for a complete list of Passport
documents. If you are using an on-line version of the library, see the
Passport InfoMap, which will provide you with links to other documents).
6 Provision new LPs to run the selected LPT software on the processor
card. To do this, add a LP component and complete the appropriate
provisioning.
add lp/<n>
where:
<n> is the instance number of the FP
7 If the card you are provisioning is the main card, set the mainCard
attribute.
set lp/<n> mainCard shelf card/<m>
where:
<n> is the LP number
<m> is the number of the card slot. For example, to link to card1, enter 1
as the <m> value.
or
If the card you are provisioning is to be a spare card, set the spareCard
attribute.
set lp/<n> spareCard shelf card/<m>
where:
<n> is the LP number
<m> is the number of the card slot.
8 Set the logicalProcessorType attribute
set lp/<n> lpt sw lpt/<lpt_name>
where:
<n> is the LP number
394 Chapter 11
241-7001-150 4S3
<lpt_name> can contain up to 25 alphanumeric characters (see the
service guides for additional information).
9 Set the CID attribute (optional).
set lp/<n> cid <cid>
where:
<n> is the LP number
<cid> is the customer identier. The customer identier constrains the
user to those components that belong to the same customer identier.
This can be set to any number between 0 and 8191.
10 Add a port for the single FDDI interface (port 0). The interface has default
values assigned to its attributes.
add lp/<n> fi/<m>
where:
<n> is the LP number
<m> is the FDDI port number (always 0). The interface has default values
assigned to its attributes. The set command can be used to change
specic attributes.
11 Add a LAN application component.
add Lan/<value>
where:
<value> is a number in the range from 0 to 255. It is recommended that
the selected number represent the LP number and application port
number, for example 52, where 5 indicates the LP number and 2
indicates the port number.
12 Link the LAN application to the logical port.
set lp/<n> fi/<m> applicationFramerName Lan/<value>
Framer
or
set Lan/<value> Framer interfaceName lp/<x> fi/<y>
where:
<n> is the LP number
<m> is the port number
<value> is a number in the range from 0 to 255
<x> is the LP number
<y> is the port number (must be set to 0)
Processor card provisioning 395
Passport Operations and Maintenance Guide 4S3
The applicationFramerName attribute contains the component name of
the Framer (Lan/<value> Framer) that is associated with the FDDI
component.
13 Add a virtual router.
add vr/<vr_name>
where:
<vr_name> is the name assigned to this instance of the virtual router The
instance value is an alphanumeric string up to 20 characters long. The
current release of Passport supports only one virtual router per node. Its
designation or name is usually the number 1
14 Add a protocol port
add vr/<vr_name> pp/<pp_id>
where:
<vr_name> is the name assigned to this instance of the virtual router
<pp_id> is the instance value ASCII string assigned to the protocol port
15 Link the LAN application to the physical port
set Lan/<value> linkToProtocolPort vr/<vr_name> pp/
<pp_id>
or
set vr/<vr_name> pp/pp_id> linkToMedia Lan/<value>
where:
<value> is a number in the range from 0 to 255
<vr_name> is the name assigned to this instance of the virtual router
<pp_id> is the instance value ASCII string assigned to the protocol port
16 Perform a semantic check on the provisioning data
check prov
17 Activate the provisioning data
activate prov
Note: The editing view becomes the current view when this command is
used.
18 Conrm the activation.
confirm prov
19 Save the new view to disk
save prov
396 Chapter 11
241-7001-150 4S3
20 Commit the new provisioning view after testing
commit prov
21 Exit from provisioning mode.
end prov
Note: For instructions on testing hardware after it is installed, see
"Diagnostic tests" on page 523. There is a list of diagnostic tests that you
can perform on the FDDI card in Component tests on function
processors on page 527.
Provisioning the Token Ring function processor
This section contains instructions for provisioning the FDDI function
processor (FP) and ports using an ASCII text interface device.
Provisionable Token Ring attributes
Provisionable attributes for the Token Ring function processor on page 397
shows the provisionable components and attributes for the token ring function
processor. For detailed information about provisionable attributes, see
241-7501-210, Passport Components.
Processor card provisioning 397
Passport Operations and Maintenance Guide 4S3
Figure 59
Provisionable attributes for the Token Ring function processor
Root
Lp
Tr
CustomerIdentifierData (CidData)
customerIdentifier
ifEntryProv (ifEntry)
IfAdminStatus
ifIndex (iFI)
Provisioned (Prov)
ringSpeed
monitorParticipate
DebugProv
defaultTraceLevel
nodeAddress
functionAddress
groupAddress
productId
applicationFramerName
La
CustomerIdentifierData (CIdData)
customerIdentifier (cid)
MediaProvisioned (MediaProv)
linkToProtocolPort
ifEntryProv (ifEntryProv)
ifAdminStatus
ifIndex
Framer
Provisioned (Prov)
interfaceName
398 Chapter 11
241-7001-150 4S3
Provisioning a Token Ring card and its logical processors and
ports
This section explains how to provision a new Token Ring function processor
using a text interface device.
Note: The required congurations are loaded on the card only when you
use the activate command in provisioning mode. For detailed
information about logical processors, see "Logical processors and logical
processor types" on page 179.
Procedure 84
Provisioning a Token Ring function processor and its LP and ports
1 Enter provisioning mode.
start prov
2 Use the display command to see which cards are currently congured.
display shelf card/*
For more information on the display command, see "Operator
commands" on page 57.
3 If the card does not already exist, add it to the shelf.
add shelf card/<n>
where:
<n> is the slot number and can be between 1 and 15 for function
processors.
4 Provision the new processor card by setting the Card component
cardType attribute.
set shelf card/<n> cardType <cardtype>
where:
<n>, the slot number, is between 1 and 15
<cardtype> is Token Ring (4pTokenRing).
5 If a suitable logical processor type (LPT) does not exist already, provision
a new LPT by adding a logicalProcessorType component and set its
featureList attribute.
add sw lpt/<lpt name>
set sw lpt/<lpt name> featureList <feature1>
<feature2> <feature3> ...
Processor card provisioning 399
Passport Operations and Maintenance Guide 4S3
where:
<lpt name> can contain up to 25 alphanumeric characters. This name is
customer-dened. The LPT determines which software or feature the LP
runs.
Note: The featureList attribute <feature> is described in the related
service user guide. (For more information on a particular featureList
attribute, see the appropriate service guide. If you are using paper-based
version of the Passport documentation library, see the 241-7001-000,
Passport Documentation Guide for a complete list of Passport
documents. If you are using an on-line version of the library, see the
Passport InfoMap, which will provide you with links to other documents).
6 Provision new LPs to run the selected logical processor type software on
the processor card. To do this, add a LP component and complete the
appropriate provisioning.
add lp/<n>
where:
<n> is the instance number of the FP.
7 If the card you are provisioning is to be the main card, set the mainCard
attribute.
set lp/<n> mainCard shelf card/<m>
where:
<n> is the LP number
<m> is the number of the card slot. For example, to link to card1, enter 1
as the m value.
8 If the card you are provisioning is to be a spare card, set the spareCard
attribute.
set lp/<n> spareCard shelf card/<m>
where:
<n> is the LP number
<m> is the number of the card slot.
9 Set the logicalProcessorType attribute.
set lp/<n> lpt sw lpt/<lpt name>
where:
<n> is the LP number
<lpt name> can contain up to 25 alphanumeric characters (see the
service guides for additional information).
400 Chapter 11
241-7001-150 4S3
10 Set the CID attribute (optional).
set lp<n> cid <cid>
where:
<n> is the LP number
<cid> is the customer identier. The customer identier constrains the
user to those components that belong to the same customer identier.
This can be set to any number between 0 and 8191.
11 Add a port for each physical interface. The interface has default values
assigned to its attributes.
add lp/<n> tr/<m>
where:
<n> is the LP number
<m> is the port number (can be set to any number between 0 and 3). The
interface has default values assigned to its attributes. The set command
can be used to change specic attributes.
12 Add a LAN application component.
add Lan/<value>
where:
<value> is a number in the range from 0 to 255. It is recommended that
the selected number represent the LP number and application port
number, for example 52, where 5 indicates the LP number and 2
indicates the port number.
13 Link the LAN application to the logical port.
set lp/<n> tr/<m> applicationFramerName Lan/<value>
Framer
or
set Lan/<value> Framer interfaceName lp/<x> tr/<y>
where:
<n> is the LP number
<m> is the port number
<value> is a number in the range from 0 to 255
<x> is the LP number
<y> is the port number (must be set in the range from 0 to 3)
The applicationFramerName attribute contains the component name of
the Framer (Lan/<value> Framer) that is associated with the Token Ring
component.
Processor card provisioning 401
Passport Operations and Maintenance Guide 4S3
14 Add a virtual router, if one was not previously provisioned.
add vr/<vr_name>
where:
<vr_name> is the name assigned to this instance of the virtual router The
instance value is an alphanumeric string up to 20 characters long. The
current release of ERS supports only one virtual router per node. Its
designation or name is usually the number 1
15 Add a protocol port.
add vr/<vr_name> pp/<pp_id>
where:
<vr_name> is the name assigned to this instance of the virtual router
<pp_id> is the instance value ASCII string assigned to the protocol port
16 Link the LAN application to the physical port.
set Lan/<value> linkToProtocolPort vr/<vr_name> pp/
<pp_id>
or
set vr/<vr_name> pp/pp_id> linkToMedia Lan/<value>
where:
<value> is a number in the range from 0 to 255
<vr_name> is the name assigned to this instance of the virtual router
<pp_id> is the instance value ASCII string assigned to the protocol port
17 Perform a semantic check on the provisioning data.
check prov
18 Activate the provisioning data
activate prov
Note: The editing view becomes the current view when this command is
used.
19 Conrm the activation.
confirm prov
20 Save the new view to disk.
save prov
21 Commit the new provisioning view after testing.
commit prov
402 Chapter 11
241-7001-150 4S3
22 Exit from provisioning mode.
end prov
Note: For instructions on testing hardware after it is installed, see
Diagnostic tests on page 523. There is a list of diagnostic tests in
Component tests on function processors on page 527.
Provisioning MVP function processors
This section contains instructions for provisioning Multipurpose Voice
Platform (MVP) function processors1pDS1Mvp, 1pE1Mvp, and
1pTTC2mMvpand ports using an ASCII text interface device. To
provision a new MVP function processor (FP) and its ports using Architect
for Passport on an NMS workstation, see 241-6001-023, NMS Architect for
Passport User Guide.
Provisionable MVP attributes
The 1pDS1Mvp function processor is provisioned under a DS1 logical
processor and port. The 1pE1Mvp and 1pTTC2mMvp function processors
are provisioned under E1 logical processors and ports. See Provisionable
DS1 components and attributes on page 298 and Provisionable E1
components and attributes on page 299 for details on provisionable
components and attributes which apply to provisioning MVP FPs. For
detailed information about provisionable attributes, see 241-7501-210,
Passport Components.
Provisioning a MVP function processor and its logical
processors and ports
This section explains how to provision a MVP processor card and its ports
using a text interface device or an NMS workstation command console.
Note: The logical processor is loaded on the card only when you use the
activate command in provisioning mode.
Procedure 85
Provisioning an MVP function processor and its ports
1 Start provisioning mode.
start prov
Processor card provisioning 403
Passport Operations and Maintenance Guide 4S3
2 Use the display command to see which cards are currently congured.
display shelf card/*
For more information on the display command, see "Operator
commands" on page 57.
3 If the card does not already exist, add it to the shelf.
add shelf card/<n>
where:
<n> is the slot number and can be between 1 and 15 for function
processors.
4 Provision the new processor card by setting the Card component
cardType attribute.
set shelf card/<n> cardType <card type>
where:
<n> is the slot number and can be between 1 and 15 for function
processors.
<card type> is 1pDS1Mvp, 1pE1Mvp or 1pTTC2mMvp.
5 If a suitable logical processor type does not exist already, provision a new
logical processor type (LPT) by adding a logical processor type
component and set its featureList attribute.
add SW lpt/<LPT Name>
set SW lpt/<LPT Name> FeatureList <feature1>
<feature2> <feature3> ...
where:
<LPT Name> can contain up to 25 alphanumeric characters. This name
is customer dened. The LPT determines which software or feature this
LP will run.
Note: The featureList attribute <feature> is described in the related
service user guide. (For more information on a particular featureList
attribute, see the appropriate service guide. If you are using paper-based
version of the Passport documentation library, see the 241-7001-000,
Passport Documentation Guide for a complete list of Passport
documents. If you are using an on-line version of the library, see the
Passport InfoMap, which will provide you with links to other documents).
6 Provision a new logical processor (LP) to run the selected logical
processor type software on the processor card. To do this, add a Logical
Processor component and complete the appropriate provisioning.
404 Chapter 11
241-7001-150 4S3
add lp/<n>
where:
<n> can be set to any number between 1 and 15.
7 Add a port depending on the type of interface required. The interface has
default values assigned to its attributes.
add lp/<n> <port>/<p>
where:
<port> is DS1 for 1pDS1Mvp or E1for 1pE1Mvp and 1pTTC2mMvp. The
interface has default values assigned to its attributes. The set command
can be used to change specic attributes.
<p> must be set to 0 for MVP cards.
8 Add a Channel component to the DS1 or E1 port.
add lp/<n> <port>/<m> chan/<p>
where:
<p> can be set from 0 to 23 for 1pDS1Mvp and 0 to 30 for 1pE1Mvp and
1pTTC2mMvp.
9 Assign timeslots to the Channel component.
set lp/<n> <port>/<m> chan/<p> timeslots <timeslots>
where:
<timeslots> can be a set of numbers between 1 and 24 for 1pDS1Mvp
and between 1 and 31 for 1pE1Mvp and 1pTTC2mMvp. Typically each
channel is associated with one timeslot.
10 Set the mainCard attribute.
set lp/<n> mainCard Shelf Card/<m>
where:
<m> is the number of the Card component. For example, to link to card1,
enter 1 as the <m> value.
11 Set the spareCard attribute (optional).
set lp/<n> spareCard Shelf Card/<m>
where <m> is the number of the Card component.
12 Set the logicalProcessorType attribute.
set lp/<n> lpt SW lpt/<lpt name>
where <lpt name> can contain up to 25 alphanumeric characters.
13 Set the CID attribute (optional).
Processor card provisioning 405
Passport Operations and Maintenance Guide 4S3
set lp/<n> cid <CID>
where:
<CID> is the customer identier. The customer identier constrains the
user to those components that belong to the same customer identier.
This can be set to any number between 0 and 8191.
14 Add an application component and complete the appropriate
provisioning. The application component varies depending on the
application that you are adding.
add <application>/<n>
where:
<application> can be set to trunks or DpnGateway.
<n> is any user-dened integer between 0 and 200 that is assigned to an
application.
Note: A Framer component is added automatically when the application
is added. The framer component has default values assigned to its
attributes. Use the set command to change specic attributes.
15 Link the application(s) to the port.
set <application>/<u> framer interfaceName lp/<n>
<port>/<p> chan/<q>
16 Perform a semantic check on the provisioning data.
check prov
17 Activate the provisioning data.
activate prov
Note: The editing view becomes the current view when this command is
used.
18 Conrm the activation.
confirm prov
19 Save the new view to disk.
save prov
20 Exit from provisioning mode.
end prov
Note: For instructions on testing hardware after it is installed, see
"Diagnostic tests" on page 523.
406 Chapter 11
241-7001-150 4S3
407
Passport Operations and Maintenance Guide 4S3
Chapter 12
Component control
This chapter explains how to control user sessions and access, and how to
lock and unlock components. Locking a component puts it out of service
while unlocking it brings it back into service. You may want to put a
component out of service to test the component, or to disable a service
provided by that component.
If, for example, node monitoring reveals a problem, it is usually necessary to
place a component out of service until the problem can be corrected. Once a
component is out of service, diagnostic testing can usually be performed as
described in Diagnostic tests on page 523. Once testing is complete and any
problems have been corrected, the component can be unlocked and placed
back into service. See OSI state combinations on page 649 for a list of OSI
component state combinations.
After reading this chapter, you will be able to place components in and out of
service using an ASCII text interface device such as a VT-100 terminal.
Except where noted, descriptions and procedures are provided for operators
working with Passport through a VT-100 terminal or a terminal emulator. If
you are using Nortels proprietary Magellan Network Management System
(NMS) see 241-6001-023, NMS Architect for Passport User Guide.
Related documents
See 241-7501-210, Passport Components for additional information related
to component control.
408 Chapter 12
241-7001-150 4S3
Commands
The following commands are used for locking and unlocking components.
Quick access to component control procedures
To nd procedures quickly, see the following list.
"Determining the state of a component using a text interface device" on
page 409
"Terminating access through a specied interface using a text interface
device" on page 410
"Terminating a user session" on page 411
"Immediately terminating multiple user sessions" on page 411
"Releasing a locked interface" on page 412
"Temporarily disabling a logical processor" on page 413
"Re-enabling a logical processor" on page 414
"Temporarily disabling a card" on page 414
"Immediately disabling a card" on page 415
"Re-enabling a card" on page 415
"Preparing a bus for testing" on page 416
Table 38
Commands
Command Description
clear Used to clear a session. See "Terminating a user session"
on page 411.
lock Used to prevent additional use of a component. That is, the
component is locked as soon as its current activity is
complete. A locked component is no longer operational.
lock -force Used to immediately prevent (or stop) the use of a
component operationally.
unlock Used to bring a locked component back into service.
Component control 409
Passport Operations and Maintenance Guide 4S3
"Four methods of disabling a trunk" on page 418
"Re-enabling a trunk" on page 419
"Preparing a disk for testing" on page 421
"Preparing a port for testing" on page 423
Prerequisites for performing node control
Your userid must have an impact of service to perform most of the procedures
in this chapter. To perform File system procedures, your userid must have an
impact of conguration.
Determining the state of a component
The procedures in this chapter explain how to lock components so that they
are out of service, and how to unlock them to bring them back in service.
Before locking a component, however, you may want to verify its state,
locked or unlocked, or the state of other components. Use the display
command to determine if the component is locked or unlocked. These states
are dened in the adminState attribute under each component.
Procedure 86
Determining the state of a component using a text interface device
1 Display the administrative state of the component.
display -c <component_name> adminState
where:
<component_name> is the name of the component
Note: -c is a short form for the -current option.
Controlling the network management interface system
The network management interface system (NMIS) consists of four interface
manager components. Each manager component can contain one or more
session components. A session component is created when a user logs on
through an interface manager. Manager components can be locked. Session
components can only be cleared. An alarm is issued whenever an NMIS
component becomes locked. The manager components are Local Interface
manager, Telnet Interface manager, FMIP Interface manager, and FTP
Interface manager.
410 Chapter 12
241-7001-150 4S3
Note 1: The lock, unlock, and clear commands require system
administration impact to be used on NMIS managers and sessions.
Note 2: Users cannot use the lock -force or lock commands on their own
manager, or clear their own session.
Note 3: The local interface manager and all its local interface sessions
are always unlocked. You cannot use the lock or lock -force commands
on them.
Note 4: When a user session is cleared, the session is immediately
terminated and no longer exists. Sessions cannot be locked or unlocked.
For more details on the Network Management Interface system, see Node
security on page 205 and 241-7001-110, Passport General Description.
Restricting access through a specied interface
The following procedure explains how to terminate access through a specied
interface by placing the interface out of service. All current sessions continue
until they are complete and no further sessions are started until the unlock
command is issued. To place an interface out of service, you must lock the
appropriate interface manager component.
Procedure 87
Terminating access through a specied interface using a text interface
device
1 Lock the interface manager component.
lock nmis <interface>
where:
<interface> is one of FTP, FMIP, or Telnet. You can lock any manager
component except your manager. Your manager component is the
component you are using to interface to the node. The manager moves
to shutting-down state and is suspended from setting up further sessions.
All current sessions continue until they are complete and no further
sessions are started.
Component control 411
Passport Operations and Maintenance Guide 4S3
Terminating a user session
Individual user sessions can be terminated. The specied session is
immediately terminated when the clear command is issued against that
session.
Procedure 88
Terminating a user session
1 Display all sessions to determine which one is to be cleared.
list -c nmis <interface>
where:
<interface> is one of: Telnet, FMIP, or FTP
Note: -c is the abbreviation for the -current view option.
2 Clear the session component.
clear nmis <interface> session/<n>
where:
<interface> is one of: Telnet, FMIP, or FTP
<n> is the session number (1 to 8 for Telnet, 1 to 16 for FMIP and FTP)
The session is cleared.
Immediately terminating multiple user sessions
Multiple user sessions can be terminated by issuing a lock -force command to
the interface manager component that those sessions belong to. All user
sessions are terminated immediately.
Alternatively, you can issue the clear command many times; once against
each session you want to terminate immediately. See "Terminating access
through a specied interface using a text interface device" on page 410 for
details.
Procedure 89
Immediately terminating multiple user sessions
1 Force the lock on the nmis component along with all sessions currently
running under that component.
lock -force nmis <interface>
where:
<interface> is one of Telnet, FMIP, or FTP
412 Chapter 12
241-7001-150 4S3
The manager component immediately terminates all its sessions, moves
to a locked state, and is suspended from setting up further sessions.
Note: You can lock any nmis component except your own. The local
interface manager cannot be locked using the lock -force command.
Releasing a locked interface
The following procedure explains how to release or unlock a locked manager
component.
Procedure 90
Releasing a locked interface
1 Unlock the nmis component.
unlock nmis <interface>
where:
<interface> is one of Telnet, FMIP, or FTP
Note: The unlock command can be issued against any nmis component
that is in a locked state. The unlock command moves the manager to an
unlocked state.
Controlling logical processors and processor cards
Logical processors and logical processor types provide the mechanism for
mapping software to processor cards and for providing processor card
redundancy.
An LP can be mapped to any processor card in the Passport conguration. It
also can be mapped to both a main processor card for supporting a service,
and to a spare card for backup.
Note: Main and spare cards must be the same type.
The LP manages function processor redundancy by allowing the operation of
the node to respond dynamically to changes in the availability of processor
cards. Applications associated with an LP can continue even though the
physical location of the software has changed.
The following procedures apply only to function processors since control
processors cannot be locked.
Component control 413
Passport Operations and Maintenance Guide 4S3
For more details on logical processors and processor cards, see "Logical
processors and logical processor types" on page 179.
Temporarily disabling logical processors
Locking a logical processor means that the specied logical processor will
not be activated. For example, you can congure and then lock a number of
logical processors that are not required immediately; they can be unlocked
when they are required. An alarm is issued when a logical processor is locked.
Procedure 91
Temporarily disabling a logical processor
1 Lock the LogicalProcessor component.
lock lp/<n>
where:
<n> is the number of the logical processor
Note: The logical processor continues to operate until it terminates or
until an operator command terminates it.
2 Optionally, force the lock on the logical processor.
lock -force lp/<n>
where:
<n> is the number of the logical processor
The logical processor is immediately locked and the LED on the faceplate
of the corresponding function processor turns red.
CAUTION
Risk of data loss if lock -force is used
Before using the lock -force command on a card or
logical processor component, it is recommended that
you lock any services (Frame Relay for example) or
trunks running on the card. Otherwise a loss of data can
result.
414 Chapter 12
241-7001-150 4S3
Re-enabling logical processors
A LogicalProcessor component that has been disabled using the lock
command can be re-enabled by issuing an unlock command against that
locked component.
Procedure 92
Re-enabling a logical processor
1 Unlock the LogicalProcessor component.
unlock lp/<n>
where:
<n> is the number of the logical processor
The faceplate LED pulses red while the software is loading, and turns
green when this process is successfully completed.
Temporarily disabling cards
Locking a Card component means that no logical processor will be assigned
to execute on that card. An alarm is issued when a Card component is locked.
Note 1: Only function processors can be locked; control processors
cannot be locked.
Note 2: If a spare card is not available, locking a logical processor or
locking a card achieves a similar effect, that is, the logical processor does
not execute. However, if there is a spare card, locking the primary card
causes the logical processor to be assigned to the spare card. It is thus
possible to manually induce a switchover to a spare card by temporarily
locking the card on which the logical processor is currently executing. A
switchover can also be induced using the switchover command as
described in Shelf management on page 599.
Procedure 93
Temporarily disabling a card
1 Lock the Card component to disable a processor card.
lock shelf card/<n>
where:
<n> is the number of the card
Component control 415
Passport Operations and Maintenance Guide 4S3
Note: No logical processor can be assigned to the card. If a lock
command is issued while the card is running a logical processor, the card
is allowed to continue executing the currently assigned logical processor
for as long as it keeps on running. In such a case, the card is said to be
in a shutting-down state. The card becomes locked as soon as the logical
processor stops running.
Immediately disabling cards
Locking a Card component means that no logical processor will be assigned
to execute on that card.
Procedure 94
Immediately disabling a card
1 Force the lock on the Card component.
lock -force shelf card/<n>
where:
<n> is the number of the card
The card is shut down immediately. An alarm is generated to indicate that
a card has been locked.
Re-enabling cards
If a Card component has been disabled due to a lock or lock -force command,
it can be re-enabled using the unlock command.
Procedure 95
Re-enabling a card
1 Unlock the Card component.
unlock shelf card/<n>
where:
<n> is the number of the card
Controlling the buses
There are two Bus components on each node. These Bus components can be
locked and unlocked. By default both buses are unlocked. When an operator
issues a request to lock a bus, the node rst ensures that the other bus is
enabled and unlocked before locking the bus; if the other bus is out of service,
the request is rejected.
416 Chapter 12
241-7001-150 4S3
Once a bus has been locked, it normally remains locked until an unlock
command is received from an operator.
The lock state is preserved if the active control processor crashes or if the
standby control processor becomes active; however, if the entire Passport
node is restarted or reset, the lock is removed. An alarm is issued whenever a
bus becomes locked.
For more details on Passport buses, see 241-7001-110, Passport General
Description.
Preparing bus components for testing
Buses are locked before testing, and unlocked afterwards. The following
procedure explains how to lock and unlock a bus.
Procedure 96
Preparing a bus for testing
1 Lock the bus for testing purposes. The other bus must be unlocked and
enabled, otherwise the lock command will fail.
lock shelf bus/<b>
where:
<b> is either X or Y
Note: The lock -force command has the same effect as the lock
command.
2 Optionally, perform necessary testing.
See Diagnostic tests on page 523 for details on test procedures that can
be performed.
CAUTION
Risk of data loss
Locking a bus may result in loss of data. Bus system
capacity is reduced by half when a bus is locked,
therefore data loss due to congestion may increase.
Also, if problems occur on the second bus, card crashes
may occur. To reduce the risk of data loss, do not lock a
bus during peak periods of trafc.
Component control 417
Passport Operations and Maintenance Guide 4S3
3 Release the bus.
unlock shelf bus/<b>
where:
<b> is either X or Y
Controlling the data collection system
The data collection system consists of three main types of components:
Collector, Agent, and Spooler.
The Collector and Agent components cannot be locked since they are both
essential for switch operations. Only the Spooler component can be locked.
For more details on the data collection system, see Data collection on
page 459 and 241-7001-110, Passport General Description.
Controlling the trunks
The trunk must be locked before port tests can be performed. The Trunk
component controls a logical port on a function processor. This Trunk
component provides a connection to a Trunk component on another network
element. For details on trunk components, see 241-7501-210, Passport
Components. An alarm is issued whenever a trunk becomes locked.
When a trunk is locked for a port test, its operational state becomes
disabled and its administrative state becomes locked. The administrative
state becomes unlocked after ve minutes even if the test is not complete.
The operational state, however, remains disabled until the test is complete.
Once the test is complete, the operational state changes to the enabled state
and the trunk attempts to become operational.
CAUTION
Risk of data loss
Locking a trunk can result in the loss of data. To reduce
the risk of data loss, do not lock a trunk during peak
periods of trafc.
418 Chapter 12
241-7001-150 4S3
Disabling a trunk
The following procedure explains how to lock Trunk components.
Procedure 97
Four methods of disabling a trunk
1 Lock the trunk.
lock trunk/<n>
where:
<n> is the instance number of the trunk between 0 and 65535
This command sets the trunk to the OSI administrative locked state,
disabling the trunk for 5 minutes. Next, the trunk returns to the OSI
unlocked state and attempts to restage with the remote network
element. If the trunk is supporting LogicalChannel subcomponents, it
enters the OSI administrative ShuttingDown state and waits for all of
these channels to go away before it starts the disabling sequence. An
unlock command can be issued during this time, returning the trunk to the
unlocked state and continuing to provide service.
2 Force a lock on a trunk.
lock -force trunk/<n>
where:
<n> is the instance number of the trunk between 0 and 65535
This command sets the trunk to the OSI administrative locked state,
disabling the trunk for 5 minutes. Next, the trunk returns to the OSI
unlocked state and attempts to restage with the remote network
element. If the trunk is supporting LogicalChannel subcomponents, it
enters the OSI administrative ShuttingDown state and forces all of
these channels to go away before it starts the disabling sequence. An
unlock command can be issued during this time, returning the trunk to the
unlocked state and continuing to provide service. Only LogicalChannels
that had not yet been disabled continue to provide service.
Note: Use the lock -force command carefully to avoid isolating a
Passport node.
3 Lock a trunk indenitely.
lock -forever trunk/<n>
where:
<n> is the instance number of the trunk between 0 and 65535
This command sets the trunk to the OSI administrative locked state,
disabling the trunk indenitely. An unlock command is required to put the
Component control 419
Passport Operations and Maintenance Guide 4S3
trunk in the OSI unlocked state for an attempt to restage with the remote
network element. If the trunk is supporting LogicalChannel
subcomponents, it enters the OSI administrative ShuttingDown state
and waits for all of these channels to go away before it starts the disabling
sequence. An unlock command can be issued during this time, returning
the trunk to the unlocked state and continuing to provide service.
4 Force a lock on a trunk indenitely.
lock -force -forever trunk/<n>
where:
<n> is the instance number of the trunk between 0 and 65535
This command sets the trunk to the OSI administrative locked state,
disabling the trunk indenitely. An unlock command is required to put the
trunk in the OSI unlocked state for an attempt to restage with the remote
network element. If the trunk is supporting LogicalChannel
subcomponents, it enters the OSI administrative ShuttingDown state
and forces all of these channels to go away before it starts the disabling
sequence. An unlock command can be issued during this time, returning
the trunk to the unlocked state and continuing to provide service. But,
only LogicalChannels that had not yet been disabled continue to provide
service.
Re-enabling a trunk
If a trunk has been disabled due to a lock -forever or lock -force -forever
command, it can be re-enabled using the unlock command. Alternately, if a
trunk has been disabled with a lock or lock -force command, it will re-enable
itself within 5 minutes of being locked.
Procedure 98
Re-enabling a trunk
1 Unlock the trunk.
unlock trunk/<n>
where:
<n> is the instance number of the trunk between 0 and 65535
Note: Issuing this command results in the trunk attempting to restage.
420 Chapter 12
241-7001-150 4S3
The trunk restaging mechanism
Trunks implement a backoff mechanism when restaging from a hardware
related fault. This mechanism reduces the amount of routing traffic that
would otherwise be generated by a trunk that was repeatedly enabled and
disabled.
The first time a trunk is disabled due to a facility problem, it waits for 10
seconds after the facility is operational before attempting to restage.
Subsequent failures result in the trunk waiting for 20 and then for 40 seconds
after the facility is operational before attempting to restage. This restaging
mechanism cycles through the 10-, 20-, and 40-second periods until the trunk
is successful.
Once a trunk is operating error-free for 10 minutes, the restaging mechanism
is reset to start at the 10-second waiting period.
Controlling the disk
The disk test cannot tolerate any interruptions from normal disk operations,
so the disk must be locked before the disk test is performed. Once the Disk
component is locked, all normal disk operations are rejected until the
component is enabled by the unlock command. An alarm is issued whenever
a disk becomes locked.
CAUTION
Risk of operational data loss
Using the format command on a disk causes a loss of
operational data. See Shelf management on page 599
for details on how to format a disk. Performing a disk
test may cause a loss of operational data. See
Diagnostic tests on page 523 for details on how to
perform diagnostic tests on the disk.
Component control 421
Passport Operations and Maintenance Guide 4S3
Preparing a disk for testing
The following procedure explains how to lock and unlock Disk components.
Procedure 99
Preparing a disk for testing
1 If you are using a single-disk system, lock the FileSystem component.
lock fs
2 Lock the Disk component.
lock fs disk/<n>
where:
<n> is the number of the disk. The disk number corresponds to the slot
number of the CP that holds the disk.
The disk moves to a shutting-down state. That is, current operations
continue to run until complete and then the disk becomes locked. Once
the disk is locked, all disk operations are disallowed except for FORMAT
and TEST. The lock and lock -force commands have the same effect on
the disk component.
3 Optionally, perform necessary operations.
Note: See Diagnostic tests on page 523 for details on test procedures
that can be performed.
4 Unlock the Disk component when maintenance procedures are complete.
unlock fs disk/<n>
where:
<n>is the number of the disk. The disk number corresponds to the slot
number of the CP that holds the disk.
Controlling the ports
The following components can be locked:
DS1 component (manages the DS1 ports on DS1, DS1V, DS3C, DS1C,
three-port DS1 ATM, eight-port DS1 ATM, and DS1 AAL1 function
processors)
E1 component (manages the E1 ports on E1, E1V, J2MV, E1C, three-port
E1 ATM, eight-port E1 ATM and E1 AAL1 function processors)
DS3 component (manages the DS3 ports on DS3, DS3C, and DS3 ATM
function processors)
422 Chapter 12
241-7001-150 4S3
E3 component (manages the E3 ports on an E3 and E3 ATM function
processor)
Channel component (controls a group of timeslots that form a fractional
group on a DS1 or E1 port)
V35 component (manages the V.35 ports on a V.35 function processor
and a CFP1)
X21 component (manages the V.11 ports on a V.11 function processor
and a CFP1)
FDDI component (manages the FDDI port on a FDDI function
processor)
EN component (manages the Ethernet ports on an Ethernet function
processor and a CFP1)
TR component (manages the TR ports on a V.35 function processor and
a CFP1)
JT2 component (manages JT2 ports on a JT2 ATM function processor)
Sonet component (manages ports using synchronous optical network
[SONET] on OC-3 ATM function processors)
Sdh component (manages ports using synchronous digital hierarchy
[SDH] on OC-3 ATM function processors)
Note: These components must be locked before loopback testing can be
performed on them.
For details on port components, see 241-7501-210, Passport Components.
CAUTION
Risk of data loss
Before locking a port component, lock any services (for
example, Frame Relay) or trunks running on the port.
Otherwise, a loss of data may result.
Component control 423
Passport Operations and Maintenance Guide 4S3
Preparing port components for testing
The following procedure explains how to lock and unlock port components.
Procedure 100
Preparing a port for testing
1 Lock the component that is to be tested.
lock lp/<n> <port>/<m>
where:
<n> is the number of the LP
<port> is one of DS1, E1, DS3, E3, V35, X21, FDDI, EN, and TR
<m> is the instance number of the port, and can be set to
0 to 3 for DS1, E1, and TR
0 to 7 for V35, X21 and the 8-port DS1/E1 ATM FPs
0 to 2 for ports on DS3 ATM, E3 ATM, OC-3 ATM and 3-port DS1/
E1 ATM FPs
0 to 1 for ports on the JT2 ATM FP
0 for DS3, E3, and FDDI
Note 1: The lock and lock -force commands have the same effect on all
port management system components.
Note 2: On a CFP1, the values for V.35 and X.21 ports can be from
0 to 3, and the values for Ethernet (EN) or Token Ring (TR) ports can be
4 or 5.
Note 3: If you have an E3 ATM function processor, do not lock any of its
ports for a long period of time. You should lock its ports only while
performing testing and maintenance procedures. Unlock the port
immediately after completing the procedures.
2 Optionally, lock the Channel component.
lock lp/<n> <port>/<m> channel/<p>
where:
<n> is the number of the LP
<port> is DS1 or E1
<m> is 0 to 3
<p> is 0 to 23
Note: The lock and lock -force commands have the same effect on the
Channel component.
3 Optionally, perform necessary operations.
See Diagnostic tests on page 523 for details on test procedures that can
be performed.
424 Chapter 12
241-7001-150 4S3
4 Unlock the component.
unlock lp/<n> <port>/<m>
where:
<n> is the number of the LP
<port> is one of DS1, E1, DS3, E3, V35, X21, FDDI, EN, and TR
<m> is the instance number of the port, and can be set to
0 to 3 for DS1, E1, and TR
0 to 7 for V35, X21 and the 8-port DS1/E1 ATM FPs
0 to 2 for ports on DS3 ATM, E3 ATM, OC-3 ATM and 3-port DS1/
E1 ATM FPs
0 to 1 for ports on the JT2 ATM FP
0 for DS3 and E3, and is not required for FDDI
425
Passport Operations and Maintenance Guide 4S3
Chapter 13
Node monitoring
After reading this chapter you will know how to query components and
attributes (both operational and provisionable) for the purpose of finding out
important operational and statistical information about the Magellan
Passport.
Topics in this chapter include:
a description of the list and display commands
how to monitor node management systems
how to monitor the network management system
how to monitor the routing system and use the rtg dpn ping and VC ping
commands
An understanding of the components and their associated attributes coupled
with knowledge of how to use the list and display commands will enable you
to monitor the Passport node quickly and easily.
Familiarity with the Open Systems Interconnection (OSI) fundamentals will
help you understand the information in this chapter.
Except where noted, descriptions and procedures are provided for operators
working with Passport through a VT-100 terminal or a terminal emulator. If
you are using Nortels proprietary Magellan Network Management System
(NMS) see 241-6001-023, NMS Architect for Passport User Guide.
426 Chapter 13
241-7001-150 4S3
Prerequisites
An understanding of Magellan Passport and operational terms and concepts
(as discussed in Software installation on page 165 and Provisioning
system description on page 85) is essential to understanding topics in this
chapter.
Related documents
See the following documents for additional information:
241-7501-210, Passport Components
241-7001-110, Passport General Description
241-7001-200, Passport and DPN-100 Interworking Guide
Quick access to component control procedures
To nd procedures quickly, see the following list:
"Determining a hardware failure" on page 431
"Determining which buses are in service" on page 431
"Determining the status of a bus" on page 431
"Displaying a list of all existing logical processors" on page 432
"Determining the status of a logical processor" on page 432
"Determining the restart capability of LPs" on page 432
"Determining the memory capacity of a processor card" on page 433
"Determining the card type in a given slot" on page 433
"Displaying the attributes of an operational port component" on page 434
"Displaying the provisionable attributes of a port components" on page
434
"Displaying information about the le system" on page 435
"Displaying all the operational attributes of the le system" on page 435
"Displaying the number of user sessions" on page 436
"Displaying the sessions logged on a network management interface" on
page 436
Node monitoring 427
Passport Operations and Maintenance Guide 4S3
"Displaying all the userids logged on to a network management
interface" on page 437
"Displaying node identier" on page 440
"Listing neighboring node information" on page 440
"Finding out about a specic link group" on page 441
"Displaying information about logical network numbers" on page 441
"Finding out about a specic link" on page 441
"Determining level of access to other nodes" on page 442
"Determining link groups" on page 442
"Displaying operational data about a trunk group" on page 443
"Displaying PORS trunk information" on page 443
"Displaying routing topology information" on page 443
"Determining reachable DPN addresses" on page 444
"Determining the delay and throughput metrics and next hop link
groups" on page 445
"Displaying routing control statistics" on page 446
"Displaying information on one path using the rtg dpn ping command"
on page 449
"Displaying information on all paths using the rtg dpn ping command"
on page 450
"Displaying round trip delay information using the rtg dpn ping
command" on page 451
"Displaying Frame Relay VC path information using the VC ping
command" on page 453
"Displaying round trip delay information for a Frame Relay VC using the
VC ping command" on page 454
"Displaying PORS connections on a Passport node" on page 455
428 Chapter 13
241-7001-150 4S3
Monitoring commands
Two commands, list and display, can be used to monitor the node. The
following sections tell you about commands in general and then refer you to
the appropriate place in this book to get additional details on how to use them.
Note: Both commands can be used in provisioning mode or outside
provisioning mode.
Command capability set
The list and display commands have passive impact level. The scope is
dependent upon the component you are monitoring. For more information on
scope and impact see "Overview of provisioning system commands" on page
98.
Hints for entering commands
For hints and shortcuts on entering commands, see "Some hints for using
commands" on page 62.
Views
Within Passport, there can be up to two views of provisioning data, as
follows:
current viewrepresents the actual running conguration of the node.
This view cannot be provisioned by the operator.
edit viewrepresents a potential next conguration of the node. This
view contains provisioning data that the operator may edit through
operator commands.
For more information on views, see Operator commands on page 57.
Operating modes
When issuing commands necessary to monitor the node, you will be in either
provisioning mode or operational mode. In most circumstances, Passport
provides command options that allow you to issue commands (and get the
same results) from either provisioning mode or operational mode.
provisioning modeis the mode you are in as soon as you issue the start
prov command. You must be in this mode to make changes to the edit
view of a node. The PROV> prompt on the text interface indicates that you
Node monitoring 429
Passport Operations and Maintenance Guide 4S3
are in provisioning mode. If you issue a display command in this mode,
without specifying any options, the display defaults to show all the
provisionable attributes of a component and their current values.
operational modeis the mode you are in when you are not in
provisioning mode. The > prompt on the text interface indicates that you
are in operational mode. If you issue a display command in this mode,
without specifying any options, the display defaults to show all the
operational attributes of a component and their current values.
For more information on operational and provisionable attributes, see
241-7501-210, Passport Components.
The list command
The list command is used to show the subcomponents of a particular
component, as follows:
If the operator session is in provisioning mode, the component instances
displayed are those in the edit view, and only provisioned
subcomponents are displayed.
If the operator session is in operational mode, the component instances
displayed are those in the current view, and both provisioned and
operational subcomponents are displayed.
For information on the list command, in particular command syntax and
options, see "list (l)" on page 72.
The display command
The display command can be used in various ways to display different types
of component and attribute information. Most commonly, it is used to display
the value of the operational or provisioned (or both) attributes for a particular
component or set of components.
The output of the display command varies depending which mode you are
currently in, whether or not you specify the groups or attributes, and which
options you choose. If you are in provisioning mode, the display command
shows provisioning data in the edit view. If you are in operational mode, the
display command shows operational data in the current view.
430 Chapter 13
241-7001-150 4S3
Note: Appending a wildcard character * to the component_name or
component_type allows the command to target multiple components and
the display format is tabular. You can use wildcard characters and request
the line-by-line (non-tabular) format by using the -n (notabular) option.
For information on the display command, in particular command syntax and
options, see "display (d)" on page 74.
Command responses
If, for some reason, the system cannot interpret and process the command, a
command response appears on the screen to indicate the problem area. For a
description of all possible error messages, see 241-7501-210, Passport
Components.
OSI management states
Almost every operational component has a set of attributes that indicates its
OSI management state. The OSI management state of a component indicates
key aspects of a components usability, operability, and availability at any
given time.
The three primary factors affecting the state of a component are operability,
usage and administration:
Operability indicates whether or not a component is installed and
working. The two possible operational states of a component are
disabled and enabled.
Usage indicates whether or not the component is actively in use, and if
so, whether or not it has spare capacity for additional users. The usage
state attribute has one of three possible values: idle, active, or busy.
Administration indicates what permissions and prohibitions are in place.
This state is imposed through the management system and has a state of
locked, unlocked, or shutting down.
Note: Not all components support all possible OSI attribute values.
Node monitoring 431
Passport Operations and Maintenance Guide 4S3
Monitoring shelf management systems
Shelf management consists of the following subsystems:
shelf management systems
port management system
le system
The following sections show you how to display useful information about
these subsystems. For more information, see 241-7001-110, Passport
General Description.
Determining hardware failures
Procedure 101
Determining a hardware failure
1 Determine if any hardware components have failed.
display shelf hardwareFailures
The system reports any hardware component failures.
The three possible failures are card, power converter, or cooling unit. If
any of these fail, see the appropriate procedure in 241-7001-125,
Passport Hardware Installation Guide.
Determining which buses are in service
Procedure 102
Determining which buses are in service
1 Determine which buses are in service.
display shelf busOperatingMode
The busOperatingMode attribute is displayed 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
Determining the status of a bus
Procedure 103
Determining the status of a bus
1 Display the status of a particular bus.
display shelf bus/<n>
432 Chapter 13
241-7001-150 4S3
where:
<n> is the bus instance value (X or Y)
A list of operational attributes of the bus component appears.
Displaying all currently provisioned logical processors
Procedure 104
Displaying a list of all existing logical processors
1 Display a list of all existing logical processors (LP).
list lp/*
A list of existing logical processors appears.
Note: * is a wildcard character representing all instances
Determining the status of a logical processor
Procedure 105
Determining the status of a logical processor
1 Display the status of a particular logical processor (LP).
display lp/<n>
where:
<n> is the instance value of the LP
A list of the logical processors operational attributes appears.
Determining the restart behavior of LPs
Procedure 106
Determining the restart capability of LPs
1 Display the capability of all LPs.
display lp/* restartOnCpSwitch
All provisioned LPs on the switch are listed.
A value of false in the restartOnCpSwitch column indicates that the LP
supports hot standby CP redundancy, however the LP may still get
restarted during CP switchover if the other redundancy requirements are
not met. Assuming that all the other redundancy requirements are met
when a CP switchover occurs, call processing on the LP continues
uninterrupted for calls that were already established. New calls on this LP
may not get established until the switchover is completed. For a
description of the other redundancy requirements, see "CP redundancy"
on page 611.
Node monitoring 433
Passport Operations and Maintenance Guide 4S3
A value of true indicates that the LP restarts when a CP switchover
occurs; call processing is interrupted. This value indicates one of the
following conditions are true:
some or all services on the LP do not support hot standby CP
redundancy.
hot standby CP redundancy has been disabled for the entire node
See "Disabling and enabling hot standby CP redundancy" on page 625 for
information on disabling hot standby CP redundancy.
Determining the memory capacity of a processor card
Procedure 107
Determining the memory capacity of a processor card
1 Display the memory capacity of a processor card.
display shelf card/<n>
where:
<n> is the slot number of the card. Card slot 0 is always reserved for the
control processor.
Some of the attributes displayed are memory capacity, memory usage,
and CPU utilization (expressed as a percentage).
Determining the card type
Procedure 108
Determining the card type in a given slot
1 Display the card type of the card inserted in particular slot.
display shelf card/<n> insertedcardType
where:
<n> is the card slot number and insertedCardType is the attribute
determining the type of card
The insertedCardType attribute appears.
434 Chapter 13
241-7001-150 4S3
Displaying operational port components
Procedure 109
Displaying the attributes of an operational port component
1 Display both the operational and provisionable attributes of a V35, X21,
DS1, E1, DS3, E3, sonet, sdh, Ethernet, TokenRing, or FDDI component.
display lp/<n> <port>/<m>
where:
<port> is DS1, E1, DS3, E3, JT2, HSSI, Sonet, Sdh, X21, V35, FDDI,
TR, or EN
<n> is the instance number of the LP
<m> is the port number, which can be set to
0 to 7 for ports on the V.35, V.11, 8-port DS1, and 8-port DS1/E1 ATM FPs
0 to 5 for Ethernet cards
0 to 3 for ports on 4-portDS1, E1, DS1C, E1C, TR cards
0 to 3 for DS1/E1 AAL1 FPs and V.35 or V.11 (X21) port components on
CFP1 FPs
4 to 5 for EN and TR port components on CFP1 cards
0 to 2 for ports on 3-port DS1/E1 ATM, DS3/E3 ATM, OC-3 ATM FPs
0 or 1 for ports on JT2 ATM cards
0 for ports on HSSI, DS1V, E1V, J2MV, DS3, E3, DS3C, FDDI cards
The operational attributes of the component appear.
Displaying provisionable attributes of port components
Procedure 110
Displaying the provisionable attributes of a port components
1 To display the provisionable attributes of a V35, X21, DS1, E1, DS3, E3,
FDDI, or EN component:
display -p lp/<n> <port>/<m>
where:
<port> is DS1, E1, DS3, E3, JT2, HSSI, Sonet, Sdh, X21, V35, FDDI,
EN, or TR
<n> is the instance number of the LP
<m> is the port number, which can be set to
0 to 7 for ports on the V.35, V.11, 8-port DS1, and 8-port DS1/E1 ATM FPs
0 to 5 for Ethernet cards
0 to 3 for ports on 4-port DS1, E1, DS1C, E1C, TR cards
0 to 3 for DS1/E1 AAL1 FPs and V.35 or V.11 (X21) port components on
CFP1 FPs
4 to 5 for EN and TR port components on CFP1 cards
0 to 2 for ports on 3-port DS1/E1 ATM, DS3/E3 ATM, OC-3 ATM FPs
Node monitoring 435
Passport Operations and Maintenance Guide 4S3
0 or 1 for ports on JT2 ATM cards
0 for ports on HSSI, DS1V, E1V, J2MV, DS3, E3, DS3C, FDDI cards
A list of provisionable attributes and their values appear.
Displaying information about the le system
Procedure 111
Displaying information about the le system
1 Display information about the le system.
display fs
Note: fs is the abbreviation for the FileSystem component.
A list of operational le system attributes and their values appear.
Displaying le system disk information
Procedure 112
Displaying all the operational attributes of the le system
1 Display all the operational attributes of the le system disk.
display fs disk/<n>
where:
<n> is the number of the disk. The disk number corresponds to the slot
number of the CP that holds the disk.
A list of le system disk attributes and their values appear.
Note 1: fs is the abbreviation for the FileSystem component.
Note 2: If there are different numbers of bad blocks on the disks in a dual-
disk system, the reported free space differs on the two disks.
Monitoring the Passport network management systems
The network management system includes the following:
provisioning system
data collection system
network management interface system
The following sections describe how to monitor the network management
interface system only. For details on monitoring the data collection system,
see Data collection on page 459.
436 Chapter 13
241-7001-150 4S3
The provisioning systems functions are limited to processing and
implementing operator commands and provisioning the Passport system.
Monitoring these functions through operator commands is not required.
For more information on the component administration system and the data
collection system, see 241-7001-110, Passport General Description.
In the subsequent sections, the following component abbreviations are used:
NMIS = network management interface system
FMIP = the proprietary management protocol (based on OSI/ASN.1
principles) that is used between a Passport switch and the Magellan
Network Management System (NMS) to manage the Passport modules
Determining the number of user sessions
Procedure 113
Displaying the number of user sessions
1 Display the number of sessions of a particular network management
interface (NMIF) currently running on the node.
display nmis <NMIF>
or
display nmis <NMIF> active
where:
<NMIF> is one of Telnet, Local, FMIP, or FTP
The number of active local sessions appears.
Displaying user sessions
Procedure 114
Displaying the sessions logged on a network management interface
1 Display the sessions logged on to a particular NMIF.
list nmis <NMIF> *
where:
<NMIF> is one of Telnet, Local, FMIP, or FTP
A list of the current sessions appears.
Node monitoring 437
Passport Operations and Maintenance Guide 4S3
Querying userids
Procedure 115
Displaying all the userids logged on to a network management interface
1 Display all the userids logged on to an NMIF.
display nmis <NMIF> session/* userid
where:
<NMIF> is one of Telnet, Local, FMIP, or FTP
A listing of all userids logged on to the NMIF appears.
Monitoring the routing system
The routing system provides network connectivity and routing between
nodes. The routing system has a network-wide scope, implemented by
software distributed on each node of the network. All nodes are in
communication with each other.
The routing system performs the following primary functions:
discovers the network topology and propagates this information across
the network
distributes internal and external address plans
creates and maintains packet forwarding tables on each Passport node
forwards the packets, using the routing tables to make path selections
The following sections provide details on how to query information about the
routing system. Sample networkDPN-100 and Passport on page 439 is
included to help clarify the information in each section. For specifics on the
attributes that result from the queries, see 241-7501-210, Passport
Components.
Note: Many of the routing-specic terms used in this section are not
dened here. See 241-7501-310, Passport Networking Introduction, for
a description of the routing systems.
In the following sections, these component abbreviations are used:
top = topology
rtg = routing
438 Chapter 13
241-7001-150 4S3
dpn = DPNAddressPlan
trm = transportResource
lg = linkGroup
n = node
Node monitoring 439
Passport Operations and Maintenance Guide 4S3
Figure 60
Sample networkDPN-100 and Passport
Passport2
Passport4
Passport3
Passport0
Passport1
Nodeld = 502
Mid = 1086
Passport RID subnetwork
RID = 83
Passport RID subnetwork
RID = 84
Trunk
Trunk
Trunk
Nodeld = 504
Mid = 1088
Nodeld = 503
Mid = 1087
DPN subnetwork
RID = 64
Mid = 1080
RID = 54
Mid = 1081
RM1
RM2
Nodeld = 501
Mid = 1085
Nodeld = 500
Mid = 1084
Trunk
Trunk
Trunk
AM
Mid = 1087
DPN Gateway
DPN Gateway
PPT 0037 001 AA
440 Chapter 13
241-7001-150 4S3
Displaying node name, node identier, namsID or region
identier
Information on node name and node identier are specied by the
ModuleData component.
Procedure 116
Displaying node identier
1 Display the node identier and the region identier.
display -p mod
Note: mod is an abbreviation for the ModuleData component, and -p is
the option that species provisionable attributes of the ModuleData
component.
The provisionable attributes of the node appear, for example:
nodeId = 500
nodeName = Passport0
namsId = 2502
regionId = 23
Displaying neighboring node link information
The TransportResource component that resides on all Passport nodes is
responsible for managing link resources. It acts as an intermediary between a
link and all the routing systems that use that link. It provides important
operational information on a particular Passports neighboring nodes.
Procedure 117
Listing neighboring node information
1 Determine trunk information with respect to neighboring nodes.
list trm *
Information about trunks connected to neighboring nodes, for example:
Trm Lg/R64
Trm Lg/Passport1
Trm Lg/Passport2
Trm Lk/1
Trm Lk/2
.
.
.
Trm Lk/<last link number>
Note: The link number can range from 1 to 1023.
Node monitoring 441
Passport Operations and Maintenance Guide 4S3
Displaying information about a specic link group
There may be up to four links in a group, including both groups of trunks and
groups of DPN gateways. If a link is active, it appears as a subcomponent of
trm and a subcomponent of trm lg/<n>. Trunks and DPN gateways cannot be
in the same group.
Procedure 118
Finding out about a specic link group
1 Display information about a specic link group.
list trm lg/<link group instance> *
where:
<link group instance> is the name of the neighboring node
The links and the logical network numbers supported in the link group to
that neighboring node appear, for example:
Trm Lg/Passport1 Lk/<link instance>
Trm Lg/Passport1 LNN/<Logical Network Number instance>
Note: One or two logical network numbers (LNN) can be supported by a
link group. LNN0 is for all Passport-to-Passport trunks. LNN1 is for all
trunks (Passport-to-Passport and Passport-to-DPN).
Procedure 119
Displaying information about logical network numbers
1 Display information about a specic logical network number.
display trm lg/<link group instance> LNN/<LNN
instance>
where:
<LNN instance> is the instance of the logical network number
A list of operational attributes of the logical network number appears.
Procedure 120
Finding out about a specic link
1 Display information about a specic link.
display trm lg/<link group instance> Link/<link
instance>
where:
<link instance> is the instance of the link
442 Chapter 13
241-7001-150 4S3
Listing all the nodes in the Passport network
The Topology (top) component resides on all Passport nodes and is
responsible for maintaining information describing the network topology and
outbound costs on all trunk groups.
Note 1: Topology provides a view of the Passport network only.
Passport-to-DPN-100 connections are not included under the Topology
component.
Note 2: If a network is divided into topology regions, only the regions
in which the command was made will appear on the screen.
Procedure 121
Determining level of access to other nodes
1 Obtain a view of the nodes you can access.
list rtg top node/*
A list of all operational Passport nodes that you have a pathway to,
appears, for example:
Rtg Top Node/Passport0
Rtg Top Node/Passport1
Determining link groups
Procedure 122
Determining link groups
1 Display the various link groups on other Passport nodes that connect to
Passport node neighbors.
list rtg top node/<your node name> lg/*
where:
<your node name> is the name of the node
Any outgoing link groups that connect the node to a neighboring node
appear, for example:
Rtg Top Node/Passport1 Lg/Passport0
The example indicates that there is one link group going in the direction
from Passport1 to Passport0.
Node monitoring 443
Passport Operations and Maintenance Guide 4S3
Displaying information about link groups in the network
Procedure 123
Displaying operational data about a trunk group
1 Display operational data about a trunk group.
display rtg top Node/<your node name> lg/<neighboring
node name>
where:
<your node name> is the name of the node
<neighboring node name> is the name of a neighboring node
Operational attributes for the trunk group appear.
Displaying information about PORS trunks in the link group
Procedure 124
Displaying PORS trunk information
1 Display data about PORS trunks in the network.
display rtg top n/<node name 1> lg/<node name 2> trk/*
where:
<node name 1> is the name of the node from which the PORS trunks
are outgoing
<node name 2> is the name of the node to which the PORS trunks are
going
A list of operational and provisionable attributes appears for each PORS
trunk going in the direction from the rst node specied to the second
node specied.
Displaying routing topology information
Procedure 125
Displaying routing topology information
1 Display operational routing statistics.
display rtg top
A list of operational attributes containing topology statistics appears. The
values of the attributes are an indication of the trafc load being placed on
the network.
444 Chapter 13
241-7001-150 4S3
Listing the reachable DPN addresses in the network
At some point in time, you may want to determine which nodes, Passport
subnetworks, or access modules (AM) and resource modules (RM) such as a
call server resource module (CSRM) are reachable from the Passport node.
Procedure 126
Determining reachable DPN addresses
1 List all reachable nodes, as identied by their MIDs.
list Rtg Dpn Mid/*
The instance value of each listed Mid component is the MID of a
reachable node.
2 List all reachable Passport subnetworks, as identied by their RIDs.
list Rtg Dpn Rid/*
The instance value of each listed Rid component is the RID of a reachable
subnetwork.
3 List all reachable CSRM functions.
list Rtg Dpn Cs/*
The instance value of each listed Cs component represents a reachable
CSRM function. The instance values can be the following:
scr (Source Call Routing Agent)
dcr (Destination Call Routing Agent)
gscr (Gateway Source Call Router Server)
gdcr (Gateway Destination Call Router Server)
grman (Gateway Call Routing Manager)
crd (Call Redirection Server)
lcr (Limping Call Redirection Server)
nui (Network User Identier Remote Server Interface)
lnui (Limping Network User Identier)
npm (Network Process Monitor System)
4 Optionally, you can list all nodes, subnetworks, and CSRM functions, as
well as other operational components.
list Rtg Dpn *
Node monitoring 445
Passport Operations and Maintenance Guide 4S3
Procedure 127
Determining the delay and throughput metrics and next hop link groups
1 Display the delay and throughput metrics and the next hop link groups to
reach a particular component.
display rtg dpn Rid/<rid number>
where:
<rid number> is the RID of the component for which you want to
determine delay and throughput metrics and next hop link groups
The delay metric and throughput metric appear.
For more information on delay and throughput metrics, see 241-7001-
200, Passport and DPN-100 Interworking Guide.
OR
2 Display the delay and throughput metrics for any AM connected to a
Passport node.
display rtg dpn Mid/<mid number>
where:
<mid number> is the AM for which you want to determine delay and
throughput metrics and next hop link groups
The delay metric, throughput metric, and next hop link group(s) (for the
AM) appear.
OR
3 Display delay and throughput metrics for a DPN-100 Call Server.
display rtg dpn CS/<callServer>
OR
4 Display delay and throughput metrics for a Mid in the Passport network
(for example Mid/1085).
display rtg dpn Mid/<mid number>
where:
<mid number> is the MID of the component for which you want to
determine delay and throughput metrics and next hop link groups
The delay metric, throughput metric, and next hop link groups appear.
446 Chapter 13
241-7001-150 4S3
Displaying routing control statistics
Procedure 128
Displaying routing control statistics
1 Display control statistics concerning the routing of DPN trafc to all
Passport nodes in the RID subnetwork.
display rtg dpn
A list of operational attributes appears.
Determining network information using the rtg dpn ping
command
You can use the rtg dpn ping command to determine network information as
follows:
the reachability of another node
the path(s) to another node
the round trip delay to another node
Options also exist to specify packet attributes such as reliability, sensitivity,
and priority, and to define the round trip delay packet size.
The rtg dpn ping command format is
ping [-allPaths] [-reliability(<type>)
-sensitivity(<type>) -priority(<type>)] [-rtd
[-sendPktDataSize(numBytes)
-returnPktDataSize(numBytes)]] rtg dpn Rid/<rid number>
Mid/<Mid number>
where:
-allPaths requests every path between the nodes be displayed
-reliability <type> is normal or high
-sensitivity <type> is delay or throughput
-priority <type> is normal or high
-roundTripDelay (-rtd) is used to measure round trip delay
-sendPktDataSize specifies the number of bytes in the packet sent to the
destination
-returnPktDataSize specifies the number of bytes in the packet returned
Node monitoring 447
Passport Operations and Maintenance Guide 4S3
from the destination
<rid number> is the RID of the destination node
<mid number> is the MID of the destination node
Sample ping commands are given below:
ping rtg dpn rid/41
ping -all rtg dpn rid/41
ping -rel(n) -sens(d) rtg dpn rid/41 mid/20
ping rtg dpn mid/20
ping -rtd -send(20) -ret(30) rtg dpn rid/84 mid/30
Determining paths using the rtg dpn ping command
You can determine paths from one node to another node in a network that
supports the RID/MID address plan using the ping command. The ping
command causes one or more query packets to be sent to the destination you
specify, RID or MID, or both. The system displays a record of the path(s)
taken.
An option exists to display one path or all paths. With no options, the ping
command displays only one possible path to the destination. When the ping
-allPaths command is specified, all paths that are in use for the destination are
displayed. The ping -allPaths command can be used for a Passport node or
DPN-100 module destination.
Rtg dpn ping command path selection options
Options that affect the path selection process are reliability, sensitivity, and
priority. Reliability specifies whether a packet can take an overflow path
(high reliability) or is to be discarded (normal reliability) when congestion is
encountered. High reliability is the default option. Sensitivity specifies
whether a minimum delay path or a maximum throughput path is selected.
Throughput sensitivity is used as a default. Priority is the importance of the
packet. High priority packets are less likely to be discarded than the default
normal priority packets.
448 Chapter 13
241-7001-150 4S3
Determining round trip delay information using the rtg dpn ping
command
You can use the roundTripDelay (-rtd) option of the ping command to
measure and display round trip delay to Passport nodes and DPN-100
modules. The round trip delay displays a measurement of the time it takes to
send a packet from a source node to a destination node and back.
The response contains the average, minimum, and maximum round trip
delays to the destination, in milliseconds. Five samples are used to calculate
these delay values.
Note: The -rtd option is ignored if the -all option is specied.
Round trip delay query packet size for the rtg dpn ping command
The size of the data in the delay query packets sent and returned each defaults
to 128 bytes. You can specify the send and return packet data size, in bytes,
with the -sendPktDataSize and -returnPktDataSize options, respectively. Any
combination of packet data size options can be used. The -sendPktDataSize
and -returnPktDataSize options are ignored if the -rtd option is not specied.
In addition to the data carried in the query packets, there is a 2-byte common
header and an 11-byte DPRS header on the front of each packet. Therefore,
the total size of a query packet with 128 bytes of data is 141 bytes.
Furthermore, 12 bytes of the data portion of the query packet are used to carry
ping control information. For this reason the minimum data size in either
direction that can be specified is 12 bytes. If less than 12 bytes is specified,
12 is used.
Note: The query packet size was designed to mimic a DPRS Frame
Relay packet size. Both packets will be identical in total length if they
carry the same number of bytes of actual data.
Node monitoring 449
Passport Operations and Maintenance Guide 4S3
Figure 61
rtg dpn ping query packet
t
Responses to the rtg dpn ping command
The normal responses to the rtg dpn ping command are shown in the path
examples for Displaying information on one path using the rtg dpn ping
command on page 449 and Displaying information on all paths using the
rtg dpn ping command on page 450. See Displaying round trip delay
information using the rtg dpn ping command on page 451 for responses to
the ping round-trip-delay option and sensitivity examples. If the system
cannot interpret and process the command, it displays an error response to
indicate the failure. For a description of all possible error messages see
241-7501-210, Passport Components.
Note: A timeout results if no response occurs within 15 seconds of the
ping query being sent.
Requesting one path using the rtg dpn ping command
You can nd one path between nodes as follows:
Procedure 129
Displaying information on one path using the rtg dpn ping command
1 Display information about one possible path between two nodes.
ping rtg dpn Rid/<rid number> Mid/<mid number>
where:
<rid number> is the RID of the destination node
<mid number> is the MID of the destination node
PPT 2195 001 AA
Byte
0
Passport
common
header
DPRS
header
Ping
control
information
Byte
2
Byte
13
Byte
25
Byte
141
Data
450 Chapter 13
241-7001-150 4S3
Example
The following example shows a path to an access module (AM) at RID
4 and MID 478 through two Passport nodes:
ping rtg dpn rid/4 mid/478
Rtg Dpn Rid/4 Mid/478
Rid = 4 Mid = 1161 Pid = 0
Rid = 4 Mid = 1160 Pid = 0
Rid = 4 Mid = 478 Pid = 659459
Note: Pid is the process identier of the trunk process that received the
packet on each RM or AM. This information is not available on Passport
nodes and is set to 0.
Requesting all paths using the rtg dpn ping command
You can request all paths between nodes as follows:
Procedure 130
Displaying information on all paths using the rtg dpn ping command
1 Display information about the paths between two nodes.
ping -all rtg dpn Rid/<rid number> Mid/<mid number>
where:
all requests every path between the nodes be displayed
<rid number> is the RID of the destination node
<mid number> is the MID of the destination node
Example
The following example shows all paths to the destination node RID 84
and MID 1103:
ping -all rtg dpn rid/84 mid/1103
Rtg Dpn Rid/84 Mid/1103
16 packets were sent, 16 packets were returned.
Path 1 used 4 time(s):
Rid = 84 Mid = 1115 Pid = 0
Rid = 84 Mid = 1122 Pid = 0
Rid = 84 Mid = 1103 Pid = 0
Path 2 used 4 time(s):
Rid = 84 Mid = 1115 Pid = 0
Rid = 84 Mid = 1109 Pid = 0
Rid = 84 Mid = 1103 Pid = 0
Path 3 used 8 time(s):
Node monitoring 451
Passport Operations and Maintenance Guide 4S3
Rid = 84 Mid = 1377 Pid = 0
Rid = 84 Mid = 1109 Pid = 0
Rid = 84 Mid = 1103 Pid = 0
Displaying round trip delay information using the rtg dpn ping
command
You can measure round trip delay between nodes as follows:
Procedure 131
Displaying round trip delay information using the rtg dpn ping command
1 Display information about the round trip delay from one node to another
node.
ping -rtd [-sendPktDataSize(numBytes)
-returnPktDataSize(numBytes)] rtg dpn Rid/<rid number>
Mid/<Mid number>
where:
roundTripDelay (rtd) is used to measure round trip delay
sendPktDataSize species the number of bytes in the packet sent to
the destination
returnPktDataSize species the number of bytes in the packet
returned from the destination
<rid number> is the RID of the destination node
<mid number> is the MID of the destination node
Example
The following is an example of the ping round trip delay command with
the send packet data size option set to 30 and return packet data size
option set to 20:
ping -rtd -sendPktDataSize(30) -returnPktDataSize(20)
rtg dpn rid/84 mid/1103
Rtg Dpn Rid/84 Mid/1103
sendPktDataSize = 30 bytes
returnPktDataSize = 20 bytes
pktEmissionPriority = normal
numRTDPktSent = 5
numRTDPktReceived = 5
averageRTD = 11 msec
minimumRTD = 11 msec
maximumRTD = 13 msec
452 Chapter 13
241-7001-150 4S3
Determining Frame Relay Virtual Circuit (VC) information
using the VC ping command
You can use the VC ping command to determine network information as
follows:
discover the path taken by a particular Frame Relay VC, for both FrUni
and FrNni
to discover the VC round trip delay information
The VC ping command may be used to determine a VC path to a Passport
node or DPN-100 module destination. The -rtd option does not work for VCs
with the far end on DPN-100 modules.
The sensitivity, reliability, and priority path characteristics in use for the
Frame Relay VC are also used by the Frame Relay VC ping query packets.
For example, if the Frame Relay VC is using the delay class of service, then
so will the ping query packets.
Measuring round trip delay is explained in the section "Displaying round trip
delay information for a Frame Relay Virtual Circuit (VC) using the VC ping
command" on page 453.
The VC ping command format is
ping -rtd [-sendPktDataSize(numBytes)
-returnPktDataSize(numBytes)] Fr/<instance>
Dlci/<instance> Vc
where:
roundTripDelay (rtd) is used to measure round trip delay
sendPktDataSize specifies the number of bytes in the packet sent to the
destination
returnPktDataSize specifies the number of bytes in the packet returned
from the destination
<instance> is the instance of the FrUni or FrNni and of the Dlci
Sample VC ping commands are given below:
ping fruni/20 dlci/200 vc
ping -rtd -send(30) -ret(20) fruni/20 dlci/200 vc
Node monitoring 453
Passport Operations and Maintenance Guide 4S3
Displaying round trip delay information for a Frame Relay Virtual
Circuit (VC) using the VC ping command
The roundTripDelay (-rtd) option of the VC ping command allows you to
measure and display the round trip delay of the Frame Relay connection. The
response contains the average, minimum, and maximum round trip delays to
the destination, in milliseconds. Five samples are used to calculate the delay.
The VC ping command with the -rtd option does not work if the far-end node
for the Frame Relay connection is a DPN-100 module.
The path taken by the ping -rtd vc command query packets, in both the
forward and reverse directions, is the same path that the VC data takes in each
direction. The only difference is that these packets start at the control
processor (CP) on the source node and reply from the CP on the destination
node. This contrasts to the actual data path starting at and ending at the Frame
Relay DLCI function processors (FPs). The path through the links and
intermediate nodes is identical.
The size of the packet sent and returned is the same as with the rtg dpn ping
command. See "Round trip delay query packet size for the rtg dpn ping
command" on page 448 for more information.
Displaying Frame Relay VC path information using the VC ping
command
You can request VC path information as follows:
Procedure 132
Displaying Frame Relay VC path information using the VC ping
command
1 Display path information about the Frame Relay VC.
ping Fr/<instance> Dlci/<instance> Vc
where:
<instance> is the instance of the FrUni or FrNni and of the Dlci
Example
The following example shows the path for the VC with the FrUni
instance set to 10 and DLCI instance set to 100 using the VC ping
command:
ping fruni/10 dlci/100 vc
454 Chapter 13
241-7001-150 4S3
FrUni/10 Dlci/100 Vc
Destination Rid = 82, Mid = 1103. VC path taken is:
Rid = 84 Mid = 1122 Pid = 0
Rid = 84 Mid = 1103 Pid = 0
Displaying round trip delay information for a Frame Relay Virtual
Circuit (VC) using the VC ping command
You can request Frame Relay VC round trip delay information as follows:
Procedure 133
Displaying round trip delay information for a Frame Relay VC using the
VC ping command
1 Display information about the round trip delay for a Frame Relay VC.
ping -rtd [-sendPktDataSize(numBytes)
-returnPktDataSize(numBytes)] Fr/<instance> Dlci/
<instance> Vc
where:
roundTripDelay (rtd) is used to measure round trip delay
sendPktDataSize species the number of bytes in the packet sent to
the destination
returnPktDataSize species the number of bytes in the packet
returned from the destination
<instance> is the instance of the FrUni or FrNni and of the Dlci
Example
The following is an example of the VC ping round trip delay command
with the send packet data size option set to 30 and return packet data size
option set to 20 for VC FrUni instance 10 and DLCI instance 100:
ping -rtd -sendPktDataSize(30) -returnPktDataSize(20)
fruni/10 dlci/100 vc
FrUni/10 Dlci/100 Vc
sendPktDataSize = 30 bytes
returnPktDataSize = 20 bytes
pktEmissionPriority = normal
numRTDPktSent = 5
numRTDPktReceived = 5
averageRTD = 11 msec
minimumRTD = 11 msec
maximumRTD = 12 msec
Node monitoring 455
Passport Operations and Maintenance Guide 4S3
Displaying PORS connections on a Passport node
Note 1: Path optimization is an optional feature. To activate it on a node,
this feature must be provisioned. Enter the provisioning mode and type
the command add rtg pors to activate this feature on each node that
PORS resides on.
Note 2: PORS has to be added to the Routing component before looking
at Optimization.
You can use the display the number of PORS connections and the
optimization status.
Procedure 134
Displaying PORS connections on a Passport node
1 Display information on the number of PORS connections on a node and
the optimization status.
display rtg pors
Information on the number of PORS connections and the optimization
status appears, for example:
Rtg PORS
activeConnections = 7
optimizationState = scheduled
lastOptimizationTime = 1995-10-01 20:06:42.56
nextOptimizationTime = 1995-10-01 20:36:42.56
optimizationPasses = 5
optimizationProgress = 0%
pathsOptimized = 3
totalpathsOptimized = 4
ok 1995-10-01 20:06:48.5
Displaying VNS connections on a Passport node
In the following procedure, a VNS instance of 5 is used.
Procedure 135
Display VNS connections on a Passport node
1 Display all nodes that can be reached by a specic VNS instance.
l rtg Vns/5 node/*
A list of nodes that can be reached by the VNS connection appears, for
example:
Rtg Vns/5 Node/74
456 Chapter 13
241-7001-150 4S3
Rtg Vns/5 Node/75
Rtg Vns/5 Node/431
ok 1995-10-01 20:06:48
Virtual circuit recovery
A virtual circuit (VC) provides the user with the equivalent of a physical
connection to a destination address using shared facilities. Virtual circuits can
be permanent (PVC) or switched (SVC). A virtual circuit will fail only when
the components supporting the end points fail.
In establishing a path to connect two endpoints, the VC typically selects a
primary RM (or RID) to route the packet through. In a sample mixed
Magellan DPN and Passport network (see Sample networkPassport nodes
in a mixed network on page 457) when the access link between the primary
RM and AM or the primary RM itself becomes non-operational, the VC path
attempts to recover from the failure by using the alternate RM and access link
(for example an alternate RID).
Node monitoring 457
Passport Operations and Maintenance Guide 4S3
Figure 62
Sample networkPassport nodes in a mixed network
Recovery initiation
Typically, the following steps take place in a VC recovery:
Each VC maintains a heartbeat or an idle probe at 60 seconds interval
after which the idle probe is retransmitted. Packets such as retransmitted
data or idle probe are retransmitted every 3 seconds if no
acknowledgment is received. A total of 3 attempts are made and each
attempt is separated by a 3 second time interval.
After that, the Passport VC sets a timer and waits for a recovery request
from the other end of the VC.
If a recovery request from the remote VC arrives, the information from
the recovery request is used to establish the path using the alternate RID.
Passport4
Passport3
Nodeld = 502
Mid = 1086
Passport RID subnetwork
RID = 83
Trunk
Trunk
Trunk
Nodeld = 504
Mid = 1088
Nodeld = 503
Mid = 1087
Passport2
RM RM
AM
PPT 0038 001 AA
458 Chapter 13
241-7001-150 4S3
If a recovery request does not arrive, the VC will timeout and the VC will
be disconnected. This timeout value is set to 15 seconds. For a PVC, call
establishment is attempted and retried repeatedly until the call is
established.
Note: Passport VC does not initiate a recovery request because the
Passport VC resides in a Passport RID subnet already. Therefore, if a
network path is broken, the Passport VC in a Passport only network will
not receive any recovery requests and will therefore, eventually be
disconnected.
The ifTable
The ifTable provides a basic model of a network device containing a set of
interfaces. Currently, the ifTable and a proposal for its evolution are dened
in two RFCs:
RFC 1213 Management Information Base for network management of
TCP/IP-based internets: MIB-II
RFC 1573 Evolution of the Interfaces Group of MIB-II
For further information, see 241-7001-900, Passport SNMP User Guide.
459
Passport Operations and Maintenance Guide 4S3
Chapter 14
Data collection
After reading this chapter, you will be able to set up and manage the collected
accounting, statistics, log, alarm, state change notification (SCN), trap, and
debug data on the Passport node using a VT-100 terminal or terminal
emulator.
For further information on Passport statistics collection, see Statistics on
page 477. For further information on accounting, see 241-7501-400,
Passport Accounting Reference Guide. For further information on SNMP
traps, see 241-7001-900, Passport SNMP User Guide.
For further information on how operational data is generated and collected,
see 241-7001-110, Passport General Description.
Except where noted, descriptions and procedures are provided for operators
working with Passport through a VT-100 terminal or a terminal emulator. If
you are using Nortels proprietary Magellan Network Management System
(NMS) see 241-6001-023, NMS Architect for Passport User Guide.
Related documents
See the following documents for additional information related to data
collection:
241-7001-110, Passport General Description
241-7501-210, Passport Components
460 Chapter 14
241-7001-150 4S3
About the provisioning procedures in this chapter
The intent of this chapter is to focus on the steps and commands necessary to
provision the node so that data collection occurs. Details on components and
attributes are fully described in 241-7501-210, Passport Components.
Quick access to data collection procedures
To nd procedures quickly, see the following list:
"Resetting the agent queue sizes" on page 466
"Specifying the maximum number of les to be kept on disk" on page
467
"Specifying the maximum number of les to be kept on disk" on page
467
"Setting up the spooling option" on page 469
"Creating a new spooling le" on page 471
"Displaying queue attributes" on page 471
"Displaying the lename of a spooling le" on page 473
"Setting up a time-of-day accounting schedule" on page 474
Prerequisites for data collection
To perform the procedures in this chapter, your userid must have a scope of
device and an impact of service as a minimum permissions level.
Before you perform the procedures in this chapter, you should have an
understanding of how operational data is generated and collected. For details,
see 241-7001-110, Passport General Description.
Data collection setup and operation guidelines
Guidelines for using data collection facilities are provided in the following
paragraphs. You can bypass the setup procedures described in this chapter by
using the Passport default settings. However, as each Passport configuration
varies, you may want to modify the defaults for increased efficiency.
Data collection 461
Passport Operations and Maintenance Guide 4S3
Once you understand the engineering requirements for each Passport node in
the network, you can use the following procedures to modify data collection
on a node-by-node basis:
"Resetting the agent queue sizes" on page 466
"Specifying the maximum number of les to be kept on disk" on page
467
"Setting up the spooling option" on page 469
If you are not using a particular data type, you should set its agent queue size
to 0 (zero) and set its spooling option to off. Otherwise memory and disk
space will be used unnecessarily.
Accounting data
Accounting data is used for billing. If you are using accounting data, see
241-6001-309, NMS Magellan Data Provider User Guide, 241-6001-806,
NMS MDP Data Formats Reference Guide and 241-7501-400, Passport
Accounting Reference Guide.
On the node, accounting data is available only from the spooled data files.
If accounting data is important, use the default provisioning values. If
accounting data is not required, set its agent queue size to 0 (zero) and turn its
spooling option to off.
Statistics data
Statistics data is used for mid- to long-term planning and network
engineering. If you are using statistics data, see 241-6001-309, NMS
Magellan Data Provider User Guide.
On the node, statistics data is available only from the spooled data files.
If statistics data is required, set its agent queue size to a non-zero value and
set the spooling option to on.
462 Chapter 14
241-7001-150 4S3
Alarm data
Alarm data is essential to a thorough real-time surveillance of the node. This
data is also used for post-processing and analysis of down-time and other
service-affecting problems. Each alarm is described in 241-7501-230,
Passport Alarms.
You can set up alarm collection through any of the following interfaces: local
operator, telnet, Magellan NMS (via FMIP NMIF), Spooler, or SNMP Agent
(as Traps).
Note 1: We recommend that alarm data collection remains active at all
times. This precaution ensures that you have sufcient information to
analyze the cause of problems, should they occur.
Note 2: If the Passport is isolated from NMS or any outside operator (not
connected to any trunks) and the trunks are reconnected, a maximum of
15 alarms can be lost during the reconnection process due to IP buffering
limitations. More than 15 alarms can be lost if the queue size on Passport
for alarm data collection is too small. You can increase the queue size,
but keep in mind that larger queues use more memory. See Resetting the
agent queue sizes on page 466 for more information.
SCN data
SCN data is used by Nortels proprietary network management system
(Magellan NMS) to update a database called the Network Model. The
Network Model is a common repository of network configuration
information that can be used by any number of applications on Magellan
NMS. Therefore, if you are not using NMS, turn SCN data off by setting its
agent queue size to 0 (zero) and setting its spooling option to off.
You can request collection of SCN data through any of the following
interfaces: local operator, telnet, Magellan NMS (via FMIP NMIF), or
Spooler.
Log data
Operator logs are used to monitor the operator command activity on a node.
You can request logs data collection through any of the following interfaces:
local operator, telnet, or Spooler.
Data collection 463
Passport Operations and Maintenance Guide 4S3
Initially, you may not be using log data so the default agent queue size is 0
(zero), and the spooling option is off. If you are using log data, set the agent
queue size to a non-zero value. If you want to use the spooler, set the spooling
option to on.
Debug data
Debug data is generated for debugging purposes under application-specific
circumstances. Collection of debug data should be done only on a temporary
basis, since the volume of data can be very high. Consult appropriate
application user guides for details about specific use of debug data.
You can request debug data collection through any of the following
interfaces: local operator, telnet, or Spooler.
The default agent queue size is 0 (zero), and the spooling option is off. If you
are using debug data, set the agent queue size to a non-zero value. If you want
to use the spooler, set the spooling option to on.
Trap data
Traps are used for real-time surveillance of a node in the context of SNMP
management of your node. For further information on SNMP traps, see
241-7001-900, Passport SNMP User Guide.
You can request trap data through the SNMP Agent only.
To collect trap data, use the default provisioning values. If you are not using
SNMP to manage the Passport node or if you are using SNMP but you are not
collecting traps, set the agent queue size to 0 (zero). The spooling option is
not available.
File transfer
For all file transfer of spooling files, Nortel recommends that you use the
Magellan Data Provider (MDP). See 241-6001-309, NMS Magellan Data
Provider User Guide for further details.
464 Chapter 14
241-7001-150 4S3
MDP performs some necessary reformatting of the data in the files, in
addition to the actual transfer of files from the node. MDP also provides the
necessary interfaces to the appropriate hosts which process the data (for
example, the billing host which processes accounting data or the network
engineering host which processes statistics data).
Technically, FTP can be used to simply transfer files. However, the
information received through FTP will be unformatted. For this reason, direct
use of FTP to transfer spooling files is not recommended.
Note: MDP does not support retrieval and processing of debug data les.
Creating a new spooling le
Use the procedure "Creating a new spooling le" on page 471 to close a
spooling file and open a new one for a particular data type. For example, if
File Prober is going to run at a certain time (to transfer closed accounting files
to a billing host) and a large file is still open, you can close that file so that it
is included in the file transfer. See 241-7501-400, Passport Accounting
Reference Guide for details on File Prober.
Displaying a lename
You may want to use the procedure "Displaying the filename of a spooling
file" on page 473 to find out which files are currently open.
Displaying attributes
Typically, you use the procedure "Displaying queue attributes" on page 471
for statistical analysis of Passport node engineering.
CAUTION
Nortel recommends that you remove les from the node
on a regular basis. You can do this by using the
Magellan Data Provider to retrieve the les and then
delete them. It is very important that you do this before
the maximum number of les on the disk is reached.
Data collection 465
Passport Operations and Maintenance Guide 4S3
Directories
The spooled les on a Passport disk are located in the following directories:
/spooled/closed/<data type>
/spooled/opened/<data type>
<data type> is one of account, alarm, log, debug, scn, trap, or stats. Data
files are spooled into these directories on the Passport node.
Filenames
The names for all spooled data les on a Passport disk have the following
structure:
<data type>.MMDDhhmm.xxx
where:
<MMDDhhmm> refers to the date and time at which the file was opened
<MM> is the month (01-12)
<DD> is the day (01-31)
<hh> is the hour (00-23)
<mm> is the minutes (00-59)
<xxx> is the sequence number (000-999); this number is generated when the
file is opened
<data type> is account, alarm, log, debug, scn, trap, or stats
CAUTION
Do not delete or read opened les
Never delete opened les. Deleting opened les may
cause the control processor to go down. Also, do not
read opened les since they may not be complete. If
necessary, use the newle command to close the opened
le as described in the procedure "Creating a new
spooling le" on page 471. A new le is opened and the
original le is closed. It can then be read.
466 Chapter 14
241-7001-150 4S3
Resetting the agent queue sizes
The following procedure explains how to reset the agent queue sizes. If this
procedure is not performed, the default agent queue sizes are used.
Agent queue sizes are typically changed when new engineering requirements
are identified or at initial setup when engineering requirements are first
determined.
For example, you may find that the Agent component is discarding
information of a particular data type. This discard activity typically occurs if
the queue size is too small for the amount of data sent for that data type. This
chapter includes a procedure that you can use to nd out how much data, if
any, has been discarded by an Agent component (for details, see the procedure
"Displaying queue attributes" on page 471). With this information, you can
select a more appropriate queue size for that data type.
See Provisioning system description on page 85 for details on how to enter
and exit provisioning mode.
Procedure 136
Resetting the agent queue sizes
1 Start provisioning mode.
2 Set the maximum queue size for each data type as appropriate. You only
have to set the queue size value once. (After you set the value, the
system distributes it to each agent.)
set Col/<datatype> agentQ <size>
where:
<datatype> is one of alarm, account, debug, log, scn, trap, or stats
<size> species the maximum amount of information (in records) that an
agent data queue can accept
CAUTION
Risk of operational data loss
When its queue is full, the agent discards any additional
operational data originating on the processor where the
Agent resides.
Data collection 467
Passport Operations and Maintenance Guide 4S3
Note 1: Col is an abbreviation for the Collector component, and agentQ
is an abbreviation for the agentQueueSize attribute.
Note 2: When the queue is full and more data is offered to the agent, it
is discarded.
Note 3: The size should be set to 0 if no data is to be accepted. This does
not prevent applications from generating data. Therefore, if possible,
congure the application so that it does not generate data that is not
required. This allows the application to perform more efciently.
Note 4: If you want to collect a particular data type, the minimum queue
size that can be set is 20. This is because there are threshold alarms that
are triggered more often than necessary with small queue sizes.
Note 5: The defaults are as follows: alarm (100), account (10000), debug
(0), log (0), scn (200), trap (50), and stats (0). These units are in records.
3 End provisioning mode.
Resetting the maximum number of les to be kept on disk
This procedure can be performed on a Spooler component to specify the
maximum number of closed les (for the specied data type) that should be
kept in the closed directory. The following defaults are used:
alarm: 50 les
account: 200 les
debug: 2 les
log: 10 les
scn: 10 les
trap: 2 les
stats: 200 les
See Provisioning system description on page 85 for details on how to enter
and exit provisioning mode.
Procedure 137
Specifying the maximum number of les to be kept on disk
1 Start provisioning mode.
468 Chapter 14
241-7001-150 4S3
2 Reset the maximum number of les that should be kept on disk for the
specied data type.
set Col/<datatype> Sp maxFile <number>
where:
<datatype> is one of alarm, account, log, debug, scn, trap, or stats
<number> species the number of les to be kept on disk (any integer
between 1 and 200)
Note 1: Col is an abbreviation for the Collector component, Sp is an
abbreviation for the Spooler component, and maxFile is an abbreviation
for the maximumNumberOfFiles attribute.
Note 2: If the /spooled/closed/<datatype> directory has more
les than the new maximum, the oldest les are discarded.
3 End provisioning mode.
Setting up the spooling option
The spooling option species whether or not the specied data type is spooled
to the disk. Setting a spooler to off has the same effect as locking the spooler
with one exception: after a processor restart, the locked spooler becomes
unlocked but keeps its original setting of either on or off. The following
defaults are used:
alarm: off
account: on
log: off
debug: off
scn: off
trap: off
stats: on
Note: A semantic check prevents spooling from being turned on for the
trap stream.
Data collection 469
Passport Operations and Maintenance Guide 4S3
See Provisioning system description on page 85 for details on how to enter
and exit provisioning mode.
Procedure 138
Setting up the spooling option
1 Start provisioning mode.
2 Turn the spooling option on.
set Col/<datatype> Sp spool <ON/OFF>
CAUTION 1
Data may already be spooled when NMIF logs in
If a spooler is set to on when the control processor
comes up, data can start flowing to the spooler
immediately.
Therefore, if some data (such as alarms) is already
spooled when an NMIF session is set up, the user will
not see any of that data. That is, alarms that were
spooled before the NMIF is set up are only on the disk.
Subsequent data is sent to both the NMIF and the
spooler.
On rare occasions, the NMS Active Alarms display may
not be cleared after a node reload if the spooler, local
operator, or telnet session logs in too quickly.
CAUTION 2
Risk of operational data loss
If a spooler containing data is set to off (as described in
the procedure "Setting up the spooling option" on page
469), the data currently held by the spooler is lost.
Ensure that the spooler is empty before turning it off.
Use the display command, as described in the procedure
"Displaying queue attributes" on page 471, to see if the
Spooler component contains any data.
470 Chapter 14
241-7001-150 4S3
where:
<datatype> is one of alarm, log, account, debug, scn, trap, or stats
<ON/OFF> is set to on if data needs to be spooled on the switch and set
to off if the data type does not need to be spooled
Note: Col is an abbreviation for the Collector component, Sp is an
abbreviation for the Spooler component, and spool is an abbreviation for
the spooling attribute.
3 End provisioning mode.
Creating a new spooling le
Create a new spooling file when you want to retrieve the latest set of data of
a particular data type.
The newle command causes the spooler to open a new le to continue
spooling. If the new le can be opened, the existing spooling le is closed and
moved into the standard closed disk directory. From there, the closed le can
be retrieved for analysis.
If the new file cannot be opened (due to a file system error), the existing file
is not closed; the file remains in the opened directory. All spooling stops
while the file system error is in effect, and the spooler holds onto data until
this error is corrected. Once the file system error is corrected, the spooler
resends all queued data to the file system. The data collection system (DCS)
then continues spooling to the old file as long as there is room on the disk, or
until the spooler reaches the maximum file size (approximately 0.5 Mbyte).
If the maximum file size is reached, the spooling file is closed and a new file
is opened.
Also, all open spooling files are closed at 00:00 hours (midnight) each day;
so that the files are not left open indefinitely.
If an open spooling file contains information that you would like to retrieve
immediately, you can close the file by issuing the newle command. The le
closes and a new one opens, and the closed le can then be retrieved. File
closure is necessary because only closed les can be retrieved from the
Passport node.
Data collection 471
Passport Operations and Maintenance Guide 4S3
The following prerequisites must be met before creating a new spooling le:
The spooling option of the Spooler component must be provisioned to on
before the following procedure can be performed.
The le system must be available.
Procedure 139
Creating a new spooling le
1 Create the new le.
newfile Col/<datatype> Sp
where:
<datatype> is one of log, alarm, scn, account, debug, trap, or stats
Note: Col is an abbreviation for the Collector component, and Sp is an
abbreviation for the Spooler component.
2 Optionally, transfer closed les to another location for analysis.
Displaying the queue attributes of data collection
components
This procedure can be performed on Collector, Agent, and Spooler
components to nd out how many records they have received from processes
which send data to them, since the processor last restarted. This procedure is
typically used for statistical analysis of Passport node engineering.
The following queue attributes can be displayed:
recordsRx
currentQueueSize
recordsDiscarded
Procedure 140
Displaying queue attributes
1 Display the number of records received by a collector, agent, or spooler.
display Col/<datatype> recordsRx
display Col/<datatype> Ag/<n> recordsRx
display Col/<datatype> Sp recordsRx
472 Chapter 14
241-7001-150 4S3
where:
<datatype> is one of log, alarm, scn, account, debug, trap, or stats
<n> is the card number
Note: Col is an abbreviation for the Collector component, Ag is an
abbreviation for the Agent component, and Sp is an abbreviation for the
Spooler component.
2 Display the number of records held in a collector, agent, or spooler.
display Col/<datatype> currentQueueSize
display Col/<datatype> Ag/<n> currentQueueSize
display Col/<datatype> Sp currentQueueSize
where:
<datatype> is one of log, alarm, scn, account, debug, trap, or stats
3 Display the number of records that have been discarded by a collector,
agent, or spooler, since the processor last restarted.
display Col/<datatype> recordsDiscarded
display Col/<datatype> Ag/<n> recordsDiscarded
display Col/<datatype> Sp recordsDiscarded
where:
<datatype> is one of log, alarm, scn, account, debug, trap, or stats
<n> is the card number
Note: This command can be applied to the Agent component to nd out
how many records have been discarded, due to queue overowing. In the
case of the Spooler component, this command indicates how many
records were discarded, due to the spooling option being provisioned to
off after being on.
If data is being discarded by the agents, you may want to increase the
queue size for that data type; this is described in the procedure "Resetting
the agent queue sizes" on page 466.
.
Data collection 473
Passport Operations and Maintenance Guide 4S3
Displaying the lename of the spooling le
This procedure can be performed on a spooler component to nd out the name
of the open le into which data is currently being spooled.
Procedure 141
Displaying the lename of a spooling le
1 Display the lename.
display Col/<datatype> Sp spoolingFileName
where:
<datatype> is one of log, alarm, scn, account, debug, trap, or stats
Note: Col is an abbreviation for the Collector component, and Sp is an
abbreviation for the Spooler component.
The lename is displayed if a le is open. The full pathname is also
provided with the lename (for example, a typical path and lename
would be shown as /spooled/opened/alarm/
alarm.MMDDhhmm.xxx).
Setting up a time-of-day accounting schedule
The Collector/accounting component uses the collectionTimes attribute to
specify the scheduled times at which accounting data is collected. These
scheduled times apply to a 24-hour period. The schedule repeats the
following day unless a new schedule is provisioned.
Note: The collectionTimes attribute exists for all Collectors. However,
setting it for any Collector other than accounting has no effect.
Rules and restrictions
When setting up a time-of-day accounting schedule the following rules and
restrictions apply:
There is a limit of 24 entries (checked by the system when you issue a
check prov command).
You can enter the times in any order.
Duplicates are not permitted and are prevented by the system upon data
entry.
The collection times are triggered in chronological order.
474 Chapter 14
241-7001-150 4S3
Entries may not be less than one hour apart or more than 12 hours apart
(implying that at least two scheduled times are required). Both conditions
are checked when you issue a check prov command.
If no entries are made (TODA disabled), the virtual circuit (VC), ATM
or Voice Networking accounting start their own 12-hour accounting
timer if time-of-day is not provisioned.
If any valid collection times are provisioned, then the time-of-day
accounting (TODA) method is used in place of the 12-hour accounting.
Note: If a hot standby CP switchover occurs just prior to an Accounting
TODA changeover event or just prior to a Stats collection event (on the
hour or 15, 30, and 45 minutes past the hour) such that there is no active
CP available at the time of the event, then the collection of data will not
occur as scheduled.
See Provisioning system description on page 85 for details on how to start
and end provisioning mode.
Procedure 142
Setting up a time-of-day accounting schedule
1 Start provisioning mode.
2 Optionally, display the current setting for time-of-day accounting.
display Col/account collectionTimes
Note: Col is an abbreviation for the Collector component, and account
species the accounting data type.
3 Set the times at which the scheduled changeovers are to occur.
set Col/account collectionTimes <time value>
where:
<time value> is the hour and minutes of a scheduled changeover
(which should conform to the rules and restrictions listed above).
Note: Only accounting applications need the capability to generate data
in this way. Setting this attribute for other streams has no effect. For more
information, see the information on data types in 241-7501-210, Passport
Components.
4 Optionally, any time value entry can be removed.
set Col/account collectionTimes ~ <time value>
Data collection 475
Passport Operations and Maintenance Guide 4S3
where:
<time value> is the hour and minutes of a scheduled changeover
5 Also, time values can be removed and other time values added
simultaneously.
set Col/account collectionTimes ~15 13 10 9
The time value of 15:00 is removed and the time values of 13:00, 10:00,
and 9:00 are added.
6 Furthermore, all time values can be removed by performing the following:
set Col/account collectionTimes !
All previously set time values are removed.
7 End provisioning mode.
476 Chapter 14
241-7001-150 4S3
477
Passport Operations and Maintenance Guide 4S3
Chapter 15
Statistics
After reading this chapter, you will be able to set up and manage Magellan
Passport statistics collection using an ASCII text interface device such as a
VT-100 terminal or the Magellan Network Management System (NMS).
For further information on how to generate and collect operational data, see
241-7001-110, Passport General Description.
Except where noted, descriptions and procedures are provided for operators
working with Passport through a VT-100 terminal or a terminal emulator. If
you are using Nortels proprietary Magellan NMS, see 241-6001-023, NMS
Architect for Passport User Guide.
Related documents
See the following documents for additional information related to statistics:
241-7001-110, Passport General Description
241-7501-210, Passport Components
About the provisioning procedures in this chapter
The intent of this chapter is to focus on the steps and commands necessary to
provision the node. To maintain this focus, details on the components and
attributes (for example, default values) referred to in the various procedures
of this chapter are contained in 241-7501-210, Passport Components.
478 Chapter 15
241-7001-150 4S3
Quick access to statistics collection procedures
To nd procedures quickly, see the following list:
"Provisioning Passport statistics" on page 491
Passport statistics collection
Passport network planning and engineering statistics are generated through a
variety of subsystems and flow through the Data Collection System (DCS) as
a separate stream of data. Statistics records are then retrieved and converted
into Bulk format by the Magellan Data Provider (MDP). Lastly, the converted
records are transferred to the Network Engineering host. The flow of statistics
through the system is illustrated in Magellan network planning and
engineering statistics flow on page 480.
The main modules used for statistics collection include:
the Passport nodes in the network
workstations running File Prober
the Magellan Data Provider host
the Network Engineering host
Passport
The Passport nodes rely on File Prober to invoke the transfer of Passport
statistics records to the Magellan Data Provider host through FTP.
Magellan Data Provider host
The Data Collection System (DCS) collects statistics data from Passport. The
Magellan Data Provider (MDP) retrieves and converts the data before
transferring the data to the Network Engineering host. The statistics, which
are received from Passport in FMIP format, are converted into Bulk format (a
form of ASCII/EBCDIC) before they are stored on MDP.
Once the collected data has been converted and stored on MDP it is
transferred to the Network Engineering host.
Statistics 479
Passport Operations and Maintenance Guide 4S3
File Prober host
The File Prober is a scheduled UNIX cron job. When activated, File Prober
probes the specified Passport nodes for closed statistics files. It transfers the
files through proxy FTP directly to the Magellan Data Provider hosts spool
directory. The whole session is logged into a file which is stored in the home
directory of the local user on the File Prober host. By default, the transferred
files are removed from the Passport node if the transaction is completed
successfully.
480 Chapter 15
241-7001-150 4S3
Figure 63
Magellan network planning and engineering statistics ow
Network
engineering
and planning
analysis using
statistics
Data collection,
storage, and
conversion
Bulk
format
Network
Engineering
host
Magellan
Data
Provider
File Prober
host
Passport
FMIP
format
proxy
FTP
statistics
are generated
on switch
FTP
Legend
Proxy FTP
Data flow
PPT 0055 001 AA
Statistics 481
Passport Operations and Maintenance Guide 4S3
The File Prober and the Magellan Data Provider host can co-exist on the same
workstation provided the workstation has sufficient resources and network
connectivity.
Network Engineering host
The Network Engineering host uses Passport statistics data for network
engineering and planning analysis.
Benets of Passport statistics collection
Passport statistics collection offers the following benets:
Provides network operators with performance data which allows
customers to calculate specic network parameters. These network
parameters can be used to modify or re-engineer their network
requirements.
Provides the infrastructure to allow collection of new statistics in the
future.
Consolidates the NMS administration procedures for accounting and
performance data management on one host, the Magellan Data Provider.
Since the collection times of spooled statistics are synchronized with
network time (UTC) throughout a Passport network, data correlation is
possible.
Enhances future capability of supporting third-party software which
collects any type of spooled performance data.
Description of on-switch statistics generation
Passport statistics are collected by the Data Collection System (DCS) using
existing Collector, Spooler, and Agent components. These components and
their associated attributes are used to provide the capability to control data
collection on Passport. For information on the DCS in general, see Data
collection on page 459.
Collection of statistics on Passport occurs every 15 minutes on the hour, and
15, 30, and 45 minutes past the hour. The collection times are synchronized
with network time (UTC) throughout a Passport network. Collection times
are illustrated in Collection times of Passport statistics on page 482. If
statistics collection is turned on at 10:05 am, then statistics are collected at
482 Chapter 15
241-7001-150 4S3
10:15 for the time interval between 10:00 am and 10:15 am. Following this,
statistics are collected for 15 minute intervals at 10:30, 10:45, 11:00, and so
on.
Figure 64
Collection times of Passport statistics
Statistics records are spooled to the Passport disk and stored in statistics les.
These les are organized in a directory structure similar to other types of
spooled data. See "Directories" on page 465. Statistics les are closed under
one of the following times or situations:
at midnight every day
when a le becomes larger than 500 Kbytes
when a Newfile command is issued to the Statistics Spooler
if the active control processor resets, restarts, or reboots
if the le system service is disrupted (for example, the le system is
locked)
Statistics collection is enabled by provisioning the agentQueueSize attribute
of the Collector component to a value greater than zero. Statistics records are
then generated on a per component basis. The attribute names that are used in
the different records are presented in
Trunk statistics record on page 483,
Collect
Statistics
Statistics turned on
10:05 am
Network Time
10:00... 10:15 10:30... 10:45... 11:00... 11:15...
Collect
Statistics
Collect
Statistics
Collect
Statistics
Collect
Statistics
5
min
10
min
15
min
PPT 0056 001 AA
Statistics 483
Passport Operations and Maintenance Guide 4S3
DpnGateway statistics record on page 484,
LP statistics record on page 485,
Framer (Port) statistics record on page 485,
Timechange statistics record on page 486
Voice Route statistics record on page 486
Signaling channel statistics record on page 487
Voice Subroute statistics record on page 487
CAS signaling statistics record on page 488
Voice networking call server statistics record on page 489
You can use these tables as a starting point to locate details on each attribute
in 241-7501-210, Passport Components.
Table 39
Trunk statistics record
Trunk
measuredSpeedToIfMax
measuredSpeedToIfMin
measuredSpeedToIfCurrent
measuredRoundTripDelayMax
measuredRoundTripDelayMin
measuredRoundTripDelayCurrent
fwdPktFromIf
fwdDiscUnforwardFromIf
fwdOctetFromIf
remoteComponentName
porsNormPktFromIf
porsNormDiscUnforwardFromIf
(Sheet 1 of 2)
484 Chapter 15
241-7001-150 4S3
porsNormOctetFromIf
porsIntPktFromIf
porsIntDiscUnforwardFromIf
porsIntOctetFromIf
vnsPktFromIf
vnsDiscUnforwardFromIf
vnsOctetFromIf
Table 40
DpnGateway statistics record
DpnGateway
measuredSpeedToIfMax
measuredSpeedToIfMin
measuredSpeedToIfCurrent
measuredRoundTripDelayMax
measuredRoundTripDelayMin
measuredRoundTripDelayCurrent
fwdPktFromIf
fwdDiscUnforwardFromIf
fwdOctetFromIf
remoteComponentName
Table 39 (continued)
Trunk statistics record
Trunk
(Sheet 2 of 2)
Statistics 485
Passport Operations and Maintenance Guide 4S3
Table 41
LP statistics record
Logical Processor
cardNumber
cardStatus
cpuUtilAvg
cpuUtilAvgMin
cpuUtilAvgMax
memoryCapacity
memoryUsageAvg
memoryUsageAvgMin
memoryUsageAvgMax
sharedMsgBlockCapacity
sharedMsgBlockUsageAvg
sharedMsgBlockUsageAvgMin
sharedMsgBlockUsageAvgMax
localMsgBlockCapacity
localMsgBlockUsageAvg
localMsgBlockUsageMin
localMsgBlockUsageMax
Table 42
Framer (Port) statistics record
<service> Framer
rxBytes
rxFrames
txBytes
(Sheet 1 of 2)
486 Chapter 15
241-7001-150 4S3
txFrames
rxTotalLinkUtil
Note: <service> can be any one of the
following: Trunk Unacked, DpnGateway
Utp, FrameRelayUni, FrameRelayNni,
FrameRelayMux, Voice Service, Bit
Transparent Data Service, Hdlc Transparent
Data Service, or X25 Dte Lapb.
Table 43
Timechange statistics record
Col/stats
oldDateTime
newDateTime
Note: This record is inserted into the
statistics data stream any time there is an
adjustment of network time by more than 20
seconds.
Table 44
Voice Route statistics record
Voice Route
totalCallsFromSubnet
callsClearedNoChannel
callsClearedOutOfService
callsRejected
Table 42 (continued)
Framer (Port) statistics record
<service> Framer
(Sheet 2 of 2)
Statistics 487
Passport Operations and Maintenance Guide 4S3
Table 45
Voice Subroute statistics record
Voice Subroute
totalCallsFromIf
totalFailedCallsFromIf
invalidNumberingPlanCalls
addressResolutionFailedCalls
addressIncompleteCalls
pathAttributesNotMetCalls
pathSetupTimeOutCalls
callsRejectedLocally
callsRejectedByFarEnd
peakActiveChannels
peakActiveVoiceChannels
peakActiveModemChannels
peakActiveDataChannels
peakActiveFaxRelayChannels
totalCalls
totalCallsSeconds
voiceRouteInstance
Table 46
Signaling channel statistics record
SignallingChannel Statistics
totalCallsFromIf
peakActiveChannels
peakActiveVoiceChannels
(Sheet 1 of 2)
488 Chapter 15
241-7001-150 4S3
peakActiveDataChannels
totalCallsToIf
nonCallAssocSessionsToIf
nonCallAssocSessionsFromIf
frmToIf
frmFromIf
octetFromIf
octetToIf
Table 47
CAS signaling statistics record
CAS Signaling
totalCallsOutgoing
totalCallsIncoming
seizeFailures
releaseFailures
outgoingAnsweredCalls
incomingAnsweredCalls
peakActiveChannels
Table 46 (continued)
Signaling channel statistics record
SignallingChannel Statistics
(Sheet 2 of 2)
Statistics 489
Passport Operations and Maintenance Guide 4S3
Setting up statistics collection on Passport
This section consists of two subsections, "Provisionable statistics attributes"
on page 489 and "Provisioning procedures for statistics" on page 491. The
first subsection describes the component hierarchy which lists the
provisionable components and attributes for the statistics feature and a brief
description of each. The second subsection describes the provisioning
procedures used to enable and disable statistics collection and spooling.
Note: Before provisioning to enable statistics collection and spooling,
the MDP and the le prober on MDP must be set up and active. This
preparatory step ensures that the MDP is available to retrieve the records
that Passport generates.
Provisionable statistics attributes
The provisionable components and attributes for collection of Passport
statistics are shown in Provisionable components and attributes for statistics
collection on page 490. Provisionable statistics attribute in the Collector
component on page 490 and Provisionable statistics attributes in the
Spooler component on page 491 provide a brief description of the attributes
used to provision the Passport statistics. For more information about
components and attributes, see 241-7501-210, Passport Components.
Table 48
Voice networking call server statistics record
Voice Networking Call Server
totalTranslations
completeTranslations
incompleteTranslations
failedTranslations
usageCount
490 Chapter 15
241-7001-150 4S3
Figure 65
Provisionable components and attributes for statistics collection
Table 49
Provisionable statistics attribute in the Collector component
Attribute name Attribute description
agentQueueSize This attribute specifies the maximum size of the
data queues for each of the agents. When set to
0, statistics are not collected by the node. When
set to a non-zero number, statistics will be
collected on the node.
Enterprise Module (EM)
Collector
agentQueueSize
Spooler
spooling
maximumNumberOfFiles
PPT 0058 001 AB
Statistics 491
Passport Operations and Maintenance Guide 4S3
Provisioning procedures for statistics
Procedure 143
Provisioning Passport statistics
1 Start provisioning mode.
2 To turn the Passport statistics feature on, type.
set Col/stats agentqueuesize 200
where:
any non-zero number specied for agentqueuesize will turn the statistics
collection on. Setting this value to 0, will turn the Passport statistics
collection off.
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 will not be spooled to the disk.
4 Set maximum number of les that can exist in a closed directory. Type:
set Col/stats Sp maxFile <number>
where:
<number> species the number of les to be kept on disk (any integer
between 1 and 200)
5 End provisioning mode.
Table 50
Provisionable statistics attributes in the Spooler component
Attribute name Attribute description
spooling This attribute specifies whether the data type
specified is spooled to the Passport disk. This
value must be set to on to permit spooling of
statistics. If set to off, the data type specified will
not be spooled to the disk.
maximumNumberOfFiles This attribute specifies the maximum number of
files that can contain statistics which can exist in
the closed directory.
492 Chapter 15
241-7001-150 4S3
493
Passport Operations and Maintenance Guide 4S3
Chapter 16
Troubleshooting the Passport node
This chapter describes troubleshooting procedures for specic sub-systems in
the Passport in which problems may occur. These areas include
node outage
control processors
function processors
le system
trunks
DPN gateway
data collection system
Each area is presented in a single section that includes a table that summarizes
the symptom, probable causes, and corrective action (including any
troubleshooting procedures that are needed).
For information on contacting Nortel for technical support, see Nortel
support services in 241-7001-110, Passport General Description.
Except where noted, descriptions and procedures are provided for operators
working with Passport through a VT-100 terminal or a terminal emulator. If
you are using Nortels proprietary Magellan Network Management System
(NMS) see 241-6001-023, NMS Architect for Passport User Guide.
494 Chapter 16
241-7001-150 4S3
Quick access to troubleshooting procedures
To quickly nd the procedures you need, see the following list:
"Cutting off alarms" on page 495
"Determining why the node is out of service" on page 499
"Determining why the control processors do not load" on page 501
"Determining the cause of a control processor crash" on page 502
"Determining why the standby control processor does not load" on page
503
"Determining why a function processor does not load" on page 505
"Determining the cause of a function processor crash" on page 506
"Determining why the le system is not operational" on page 512
"Determining why a le can not be saved to disk" on page 513
"Determining the cause of a trunk failure" on page 515
"Determining why a trunk does not remain connected" on page 516
"Determining the cause of a DpnGateway failure" on page 519
"Determining why a dpngateway does not remain connected" on page
520
"Data collection system problems" on page 521 (troubleshooting table
only - no procedure available)
Alarms
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.
For more information on alarms, see 241-7501-230, Passport Alarms.
Troubleshooting the Passport node 495
Passport Operations and Maintenance Guide 4S3
Alarm cutoff procedure
On a 16-slot Passport switch installed in a Passport cabinet, you must clear
the external indicators for major alarms using an alarm cutoff switch. After
resolving a major alarm, see Cutting off alarms on page 495 to turn off the
external indicators for the major alarm.
The alarm cutoff switch is located at the top left of the Passport cabinet (see
Alarm cutoff switch on page 496). A single, momentary depression of this
push-button switch resets all major alarm contacts to their normally open
positions, but only if the fault has been corrected.
For information on clearing the external alarm indicators for other Passport
configurations, see 241-7001-125, Passport Hardware Installation Guide.
Procedure 144
Cutting off alarms
1 Open the Passport cabinet door.
2 Press the alarm cutoff switch, shown in Alarm cutoff switch on page 496.
All external alarm indicators for the Passport node are reset.
496 Chapter 16
241-7001-150 4S3
Figure 66
Alarm cutoff switch
DCP70117
DCP70117
Alarm cutoff
switch
Troubleshooting the Passport node 497
Passport Operations and Maintenance Guide 4S3
Service-specic problems
If you find 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.
Passport Trace System
You can monitor incoming and outgoing data of a particular service, using the
Passport Trace System (PTS). It provides an efficient and cost effective
means of monitoring data flow without interrupting regular network
activities.
The Passport Trace System defines which frames are to be traced, copies the
data, appends a trace header and sends the traced data to a centralized receiver
using a virtual circuit (VC). Multiple trace sessions can be performed
simultaneously.
The Passport Trace System traces data from a centralized location in real
time, without disconnecting the customer during trace sessions.
For more information about Trace, see 241-7001-160, Passport Trace User
Guide.
The troubleshooting process
The objective of effective troubleshooting is to identify the problem quickly,
isolate the cause, and resolve the fault. Troubleshooting should be undertaken
and completed promptly to avoid disruption in service or loss of data.
Three steps of the troubleshooting process
Each step in the flowchart is described in the following paragraphs.
Identify the problem
An alarm displayed on the VT-100 terminal usually provides a clear
indication of which component has failed and the corrective action required.
This on-screen alarm read-out is supported by LED indicators on the
hardware components.
498 Chapter 16
241-7001-150 4S3
When you receive an alarm indication, see the Symptoms column in the
appropriate table in this chapter, beginning with Node outage problems on
page 498. Also see 241-7501-230, Passport Alarms, for alarm information.
Determine the cause
Determine the cause of the problem by referring to the Probable causes
column in the appropriate table in this chapter, and by using the procedures
that begin with Node outage problems on page 498.
Resolve the problem
Problem resolution involves specific corrective activities that are described in
procedures located through the Passport documentation suite. See the
Corrective measures column in the appropriate table in this chapter,
beginning with Node outage problems on page 498. Entries in this column
will indicate the appropriate action to take, or will direct you to another
procedure if further troubleshooting is needed.
Using the process to handle common problems
The information in subsequent sections of this chapter provides details on
how to troubleshoot specic problems that may occur during operations. For
ease of reference, summary information is presented in tabular format. Each
troubleshooting summary table consists of three columns:
symptom identies the problem
probable causes identies how to determine cause
corrective measures identies references to procedures in this and other
documents
Node outage problems
Node outage problems can generally be traced to power interrupts or a
complete control processor (or CFP1) outage (stand-by control processor is
not available). A troubleshooting summary is provided in Troubleshooting
node outage problems on page 499.
Troubleshooting the Passport node 499
Passport Operations and Maintenance Guide 4S3
Procedure 145
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-7001-
125, Passport 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-7001-125,
Passport Hardware Installation Guide. Go to "Control processor
problems" on page 499 to continue the troubleshooting analysis.
Control processor problems
Problems can affect both the active and the stand-by control processor. A
troubleshooting summary is provided in Troubleshooting control processor
problems on page 500.
For procedures to troubleshoot a configuration with a CFP1, see 241-7001-
170, Passport Control and Function Processor (CFP1) User Guide.
Note: If the control processor (either active or stand-by) that does not
load has been in storage, see Troubleshooting control processor
problems on page 500.
Table 51
Troubleshooting node outage problems
Symptom Probable causes Corrective measures
Entire Passport node is out of
service (no components are
functioning)
Loss of power to the cabinet Restore power to the cabinet.
Power converters failed Replace failed power
converters.
All control processors (or the
CFP1) have failed
See "Control processor
problems" on page 499.
500 Chapter 16
241-7001-150 4S3
Table 52
Troubleshooting control processor problems
Symptom Probable causes Corrective measures
Control processor does not
load
Processor failure Replace the control processor.
See 241-7001-125, Passport
Hardware Installation Guide.
Control processor does not
load and the Passport
continually attempts to reboot.
Incompatibility of the control
processors firmware with the
Passports newer shelf (AC
shelf NTBP05BA or higher, or
DC shelf NTBP64BA or
higher). This can happen when
you use an older control
processor card that has been
held in storage.
Check whether 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
technical support for further
instructions (see Nortel
support services in 241-7001-
110, Passport General
Description). Do not return the
control processor to Nortel.
Control processor crashes Hardware failure Replace the control processor.
See 241-7001-125, Passport
Hardware Installation Guide.
Software problem Contact Nortel technical
support. See Nortel support
services in 241-7001-110,
Passport General Description.
Memory exhaustion Reduce the number of
applications running on the
Passport node.
(Sheet 1 of 2)
Troubleshooting the Passport node 501
Passport Operations and Maintenance Guide 4S3
Procedure 146
Determining why the control processors do not load
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.
Standby control processor
does not load
Processor failure Replace the control processor.
See 241-7001-125, Passport
Hardware Installation Guide.
File system failure See "File system problems" on
page 512.
Bus failure Contact Nortel. See Nortel
support services in 241-7001-
110, Passport General
Description
Standby control processor
does not load and the Passport
continually attempts to reboot.
Incompatibility of the control
processors firmware with the
Passports newer shelf (AC
shelf NTBP05BA or higher, or
DC shelf NTBP64BA or
higher). This can happen when
you use an older control
processor card that has been
held in storage.
Check whether 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
technical support for further
instructions (see Nortel
support services in 241-7001-
110, Passport General
Description). Do not return the
control processor to Nortel.
Table 52 (continued)
Troubleshooting control processor problems
Symptom Probable causes Corrective measures
(Sheet 2 of 2)
502 Chapter 16
241-7001-150 4S3
2 Remove and re-insert the control processor.
If the new control processors LED does not ash red, replace the control
processor.
If the control processor loads, use the startup procedure to bring the
Passport node back into the network, and then restore the disk using the
backup/restore utility.
3 Monitor the information output by the control processor on the local
display terminal as the control processor attempts to load.
If the loading information indicates that a specic le cannot be loaded
from the disk, then the disk is corrupted. Use the appropriate CP
replacement procedure from Shelf management on page 599. Restore
the disk from a backup copy, using the procedure in 241-6001-023, NMS
Architect for Passport User Guide.
Note: If redundant control processors are used and the standby control
processor now crossloads, reformat the standby control processor s disk.
If the loading information indicates bus errors are occurring, contact
Nortel (see Nortel support services in 241-7001-110, Passport General
Description).
Procedure 147
Determining the cause of a control processor crash
1 Replace the failed control processor.
If this corrects the problem, exit this procedure and return the failed
control processor for repair.
2 Issue the display command for the card that the failed control processor
resides on:
display shelf card/<slot> util
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 applications running on the Passport node.
3 Open a customer service request for Nortel if the previous steps fail to
resolve the problem.
Note: Include the trap data information from the 7012 0101 alarms,
issued by the control processor upon reloading, for analysis.
Troubleshooting the Passport node 503
Passport Operations and Maintenance Guide 4S3
Procedure 148
Determining why the standby control processor does not load
1 Test the card using the procedures from the sections titled "Serial port
testing" on page 525.
2 Replace the failed control processor.
If this corrects the problem, exit this procedure and return the failed
control processor for repair.
3 Issue the display command for the le system.
display fs osistate
If adminState = unlocked, operationalState = enabled and
usageState = active, you have veried that the le system is
functioning. It is possible that a le on the hard disk is corrupted or
missing. Use procedure "Testing a disk" on page 595 to verify that the disk
is ne and then load the software from a backup copy using procedure
"Replacing a control processor in a two-CP system" on page 640.
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 "File system
problems" on page 512 to continue the troubleshooting analysis.
4 Issue the display command for the bus taps:
display shelf bus/<n> busTapStatus
where <n> is either bus X or bus Y
If busTapStatus = OK for the standby control processor slot, you have
veried that the bus is functioning.
If busTapStatus = none or busTapStatus = failed, replace the
control processor. If the bus tap still does not function, contact Nortel.
Function processor problems
Function processors can experience problems with hardware and software
integrity, as well as more subtle problems in the areas of bus failure and
provisioning errors. A troubleshooting summary is provided in
Troubleshooting function processor problems on page 504.
Note: If a function processor that does not load has been in storage, see
Troubleshooting function processor problems on page 504 before
performing Procedure 149 on page 505.
504 Chapter 16
241-7001-150 4S3
Table 53
Troubleshooting function processor problems
Symptom Probable causes Corrective measures
Function processor does not
load
Processor failure Replace the function
processor. See 241-7001-125,
Passport Hardware Installation
Guide.
File system failure See "File system problems" on
page 512.
Bus failure Contact Nortel (see Nortel
support services in 241-7001-
110, Passport General
Description).
Configuration error Examine the provisioning data
and reconfigure as necessary.
Function processor crashes Hardware failure Replace the function
processor. See 241-7001-125,
Passport Hardware Installation
Guide.
Software problem Contact Nortel technical
support. See Nortel support
services in 241-7001-110,
Passport General Description.
Memory exhaustion Reduce the number of
applications running on the
function processor.
(Sheet 1 of 2)
Troubleshooting the Passport node 505
Passport Operations and Maintenance Guide 4S3
Procedure 149
Determining why a function processor does not load
1 Issue the display command for the failed function processor:
display lp/<slot> osistate
where:
<slot> is the slot number of the failed function processor.
If adminState = unlocked, operationalState = enabled, and
usageState = active, you have veried that the function processor
is operational. Exit this procedure.
2 Test the card using the procedures "Serial port testing" on page 525.
3 Remove and reinsert the failed function processor.
If this corrects the problem, exit this procedure and monitor the function
processor for reoccurrences. If the problem persists, go to step 4.
Function processor does not
load and the Passport
continually attempts to reboot.
Incompatibility of the function
processors firmware with the
Passports newer shelf (ac
shelf NTBP05BA or higher, or
DC shelf NTBP64BA or
higher). This can happen when
you use an older function
processor card that has been
held in storage.
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 Nortel
technical support for further
instructions (see Nortel
support services in 241-7001-
110, Passport General
Description). Do not return the
function processor to Nortel.
Table 53 (continued)
Troubleshooting function processor problems
Symptom Probable causes Corrective measures
(Sheet 2 of 2)
506 Chapter 16
241-7001-150 4S3
4 Replace the failed function processor.
If this corrects the problem, exit this procedure and return the failed
function processor for repair.
5 Issue the display command for the le system on the failed function
processor:
display fs osistate
If adminState = unlocked, operationalState = enabled, and
usageState = active, you have veried that the le system is
functioning. It is possible that a le on the hard disk is corrupted or
missing. Use the procedures in the section titled "Disk testing" on page
593 to verify that the disk is ne and then load the software from a backup
copy using the procedures in "Replacing a control processor in a single-
CP node" on page 633 and "Replacing a control processor in a two-CP
node" on page 640.
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 "File system
problems" on page 512 to continue the troubleshooting analysis.
6 Issue the display command for the bus Taps:
display shelf bus/<n> busTapStatus
where:
<n> is either X or Y
If busTapStatus = OK for the function processor slot, you have veried
that the bus is functioning.
If busTapStatus = none or busTapStatus = failed, replace the
function processor. If the bus tap still does not function, contact Nortel.
Note: Try using a different slot to provide service until the shelf is
replaced.
Procedure 150
Determining the cause of a function processor crash
1 Replace the failed function processor.
If this corrects the problem, exit this procedure and return the failed
function processor for repair.
2 Issue the display command for the card that the failed function processor
resides on:
display shelf card/<slot> util
Troubleshooting the Passport node 507
Passport Operations and Maintenance Guide 4S3
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 applications running on the function processor.
3 Open a customer service request for Nortel if the previous steps fail to
resolve the problem. See Nortel support services in 241-7001-110,
Passport General Description.
Note: Include the trap data information from the 7012 0101 alarms,
issued by the function processor upon reloading, for analysis.
Detecting problems with a specic card
Detecting problems with a specific card on page 508 shows the ways you
may detect problems with a specific card.
508 Chapter 16
241-7001-150 4S3
Table 54
Detecting problems with a specific card
Method of card problem detection Action
The LED status display on the card is red
(see LED status displays on page 511).
Replace the card with another card of the same type
that you know is working. (For instructions, see 241-
7001-125, Passport Hardware Installation Guide.)
If the problem persists, see troubleshooting
procedures in Function processor problems on
page 503.
If the problem is resolved after replacing the suspect
card with a known functioning card, contact your
local Nortel technical support group (see Nortel
support services in 241-7001-110, Passport
General Description) and arrange to return the
defective card. For instructions on packing the card,
see 241-7001-125, Passport Hardware Installation
Guide.
The LED status display on the card is red
and the function processor continually
attempts to reboot.
Incompatibility of the function processors firmware
with your Passports newer shelf (ac shelf
NTBP05BA or higher, or DC shelf NTBP64BA or
higher). This can happen when you use an older
function processor card that has been held in
storage.
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 technical support group for further
instructions. Do not return the function processor to
Nortel.
The LED status display on the card is
yellow.
Make sure that you have the right type of FP
provisioned.
(Sheet 1 of 3)
Troubleshooting the Passport node 509
Passport Operations and Maintenance Guide 4S3
The appropriate LED on the termination
panel is not lit.
The fuse on the associated card may be blown.
Replace the card with another card of the same type
that you know is working. (For instructions, see 241-
7001-125, Passport Hardware Installation Guide.)
If the problem is resolved after replacing the suspect
card with a known functioning card, contact your
local Nortel technical support group (see Nortel
support services n 241-7001-110, Passport
General Description) and arrange to return the
defective card. For instructions on installing,
removing and packing the card, see 241-7001-125,
Passport Hardware Installation Guide.
An alarm occurs to indicate there is a
problem with the card or with the far-end
card.
See 241-7501-230, Passport Alarms.
You detect a problem while running
diagnostic tests or while performing node
troubleshooting.
See Function processor problems on page 503.
Loss of frame 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.
Table 54 (continued)
Detecting problems with a specific card
Method of card problem detection Action
(Sheet 2 of 3)
510 Chapter 16
241-7001-150 4S3
A link problem is occurring that may be
caused by the card.
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 the expected
incoming modem signals are supplied by the
connecting device.
Check cable connections. Make sure the
connectors have no bent pins.
Make sure that the correct termination panel is used
for the card. (See 241-7001-125, Passport
Hardware Installation Guide.)
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 panels lights dont come on. Check cable pins for breakage.
Table 54 (continued)
Detecting problems with a specific card
Method of card problem detection Action
(Sheet 3 of 3)
Troubleshooting the Passport node 511
Passport Operations and Maintenance Guide 4S3
Figure 67
LED status displays
No power is reaching the card.
Card is powered and is either performing
self-tests, or after 30 seconds, is faulty.
Card has passed self-tests but has not yet
fully loaded its software.
Card's software is fully loaded but not yet
activated. It may be initializing or in standby
mode.
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 while another type was inserted.)
No colour
Solid red
Slow pulsing red
Slow pulsing green
Fast pulsing green
Solid green
Solid amber
Card status LED status
display
512 Chapter 16
241-7001-150 4S3
File system problems
File system problems are related to either the file system software or to the
disk subsystem on the control processor. A troubleshooting summary is
provided in Troubleshooting file system problems on page 512.
Procedure 151
Determining why the le system is not operational
1 Issue the display command for the le system:
display fs osistate
If adminState = unlocked, operationalState = enabled, and
usageState = active, you have veried that the le system is
functioning. Exit this procedure.
If adminState = 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 = disabled, it is likely that all disks have failed.
Go to step 2.
2 Issue the lock and unlock command for the failed le system.
lock fs
unlock fs
By locking and then immediately unlocking the failed le system, you may
clear a software related problem.
3 Issue the display command for the failed disk:
display fs disk/<n> osistate
Table 55
Troubleshooting file system problems
Symptom Probable causes Corrective measures
File system not operational File system locked Issue unlock fs command.
All disks failed Replace control processors.
Cannot save to disk File system not operational Issue the unlock fs command.
Disks are full Remove unnecessary files
from the disk.
Troubleshooting the Passport node 513
Passport Operations and Maintenance Guide 4S3
where:
<n> is the number of the failed disk
If operationalState = disabled for a given disk, that disk has
failed.
4 Issue the lock and unlock commands for the failed disk.
lock fs disk/<n>
unlock fs disk/<n>
where:
<n> is the number of the failed disk.
By locking and then immediately unlocking the failed disk, you may clear
a software related problem. If the disk still fails, go to step 5.
5 Replace the control processor that holds the failed disk using the
procedures in 241-7001-125, Passport Hardware Installation Guide.
Bring the Passport node back into the network by using the procedures in
241-7001-130, Passport Startup Guide.
Note: Restore the disks from backup copies using the procedure in
"Replacing a control processor in a single-CP node" on page 633 and
"Replacing a control processor in a two-CP node" on page 640.
Alternately, restore the backup copy to the new control processors disks
in a Passport node that is not part of the live network. Replace the
standby control processor with the new control processor and then use a
control processor switchover to bring the new control processor on-line.
Procedure 152
Determining why a le can not be saved to disk
1 Issue the display command for the le system.
display fs osistate
If adminState = unlocked, operationalState = enabled, and
usageState = active, you have veried that 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. Go to procedure
"Determining why the le system is not operational" on page 512 to
continue through troubleshooting analysis.
If the free space available is less than the size of the le to be saved,
remove any unnecessary les from the disk and reissue the save
command.
514 Chapter 16
241-7001-150 4S3
Trunk problems
Trunk problems are related to either the function processor or to the facility.
A troubleshooting summary is provided in Troubleshooting problems with
trunks on page 514. If the trunk is an ATM-based Logical Trunk, see
241-7001-710, Passport ATM Adaptation: Logical Trunks User Guide.
Table 56
Troubleshooting problems with trunks
Symptom Probable causes Corrective measures
Cannot establish trunk Processor module failure Replace the function
processor. See 241-7001-125,
Passport Hardware Installation
Guide. In a CFP1 configuration,
you may have to replace the
CFP1 card. (See 241-7001-
170, Passport Control and
Function Processor (CFP1)
User Guide.)
Port failure
Facilities failure Contact the service provider or
Nortel for assistance. See
Nortel support services in
241-7001-110, Passport
General Description.
Configuration error Examine the provisioning data
and reconfigure as necessary.
(Sheet 1 of 2)
Troubleshooting the Passport node 515
Passport Operations and Maintenance Guide 4S3
Procedure 153
Determining the cause of a trunk failure
1 Issue the display command for the failed trunk.
display trunk/<n> osistate
where:
<n> is the instance number of the failed trunk
If adminState = unlocked, operationalState = enabled, and
usageState = busy, you have veried that the trunk is operational. Exit
this procedure.
If adminState = locked, consult with the operator who took the trunk
out of service to verify that the trunk can now be unlocked, and then issue
the unlock command. If the trunk stages, you have veried that the trunk
is operational. Exit this procedure or go to step 2 to verify the status of the
logical processor.
If operationalState = disabled and availabilityStatus =
dependency, a hardware failure is indicated. The possible failed
components include the function processor, the individual port and the
trunk facilities. Go to step 2 to verify the status of the logical processor.
Cannot maintain trunk
connectivity
Port error Replace the function
processor. See 241-7001-125,
Passport Hardware Installation
Guide. If the function processor
is a CFP1 card, see 241-7001-
170, Passport Control and
Function Processor (CFP1)
User Guide.)
Facility error Contact the service provider or
Nortel for assistance. See
Nortel support services in
241-7001-110, Passport
General Description.
Remote function processor is
crashing
See "Function processor
problems" on page 503.
Table 56 (continued)
Troubleshooting problems with trunks
Symptom Probable causes Corrective measures
(Sheet 2 of 2)
516 Chapter 16
241-7001-150 4S3
If operationalState = disabled and availabilityStatus =
<empty>, the problem originates at the remote end. Repeat this
procedure (Determining the cause of a trunk failure on page 515) at the
remote end.
2 Issue the display command for the logical processor on the failed trunk:
display lp/<n> osistate
where:
<n> is the instance number of the failed logical processor
Note: Determine the logical processor and port assignments by using the
following command display -p trunk/<n> unacked framer.
If adminState = unlocked, operationalState = enabled, and
usageState = busy, you have veried that the logical processor is
operational. Go to step 3 to verify the status of the port.
If operationalState = disabled and availabilityStatus =
dependency, a function processor failure is indicated. Go to the
"Function processor problems" on page 503 to continue the
troubleshooting analysis.
Note: For information on ATM trunks, see 241-7001-710, Passport ATM
Adaptation: Logical Trunks User Guide.
3 Issue the display command for the physical port on the failed trunk:
display lp/<slot> <trunkType>/<port>
where:
<slot> is the slot number of the failed trunk
<trunkType> is the type of trunk that failed
<port> is the port number of the failed trunk
For example, display lp/10 v35/0 or display lp/3 ds1/3.
If the operationalState = disabled, go to the section entitled
"Serial port testing" on page 525 to continue the troubleshooting analysis.
Note: For information on ATM trunks, see 241-7001-710, Passport ATM
Adaptation: Logical Trunks User Guide.
Procedure 154
Determining why a trunk does not remain connected
1 Issue the display command for the failed trunk.
display trunk/<n> unacked framer
Troubleshooting the Passport node 517
Passport Operations and Maintenance Guide 4S3
where:
<n> is the instance number of the failed trunk
Examine the counts for the errors that are displayed.
2 Wait a few seconds and reissue the display command for the failed trunk.
display trunk/<n> unacked framer
where:
<n> is the instance number of the failed trunk
Once again, examine the counts for the errors that are displayed.
If any of these counts are increasing, use the appropriate port testing
procedure in Diagnostic tests on page 523 to isolate the problem to the
port on the function processor or the communications facility.
If the counts are not increasing, the problem is likely located at the remote
end of the trunk. Move to that remote Passport node and continue
troubleshooting. If the trunks function processor is crashing, see the
section "Determining the cause of a function processor crash" on page
506 to continue the analysis.
Note: For information on ATM trunks, see 241-7001-710, Passport ATM
Adaptation: Logical Trunks User Guide.
DPN Gateway problems
Problems with the DPN gateway are related to the function processor, the
facility, or the remote DPN element. A troubleshooting summary is provided
in Troubleshooting DPN gateway problems on page 518. If the DPN
Gateway is a Frame Relay-based DPN Gateway, see 241-7001-200, Passport
and DPN-100 Interworking Guide.
518 Chapter 16
241-7001-150 4S3
Table 57
Troubleshooting DPN gateway problems
Symptom Probable causes Corrective measures
Cannot establish dpngateway Processor module failure Replace the function
processor. See 241-7001-125,
Passport Hardware Installation
Guide. In a CFP1 configuration,
you may have to replace the
CFP1 card. (See 241-7001-
170, Passport Control and
Function Processor (CFP1)
User Guide.)
Port failure
Facilities failure Contact the service provider or
Nortel for assistance. See
Nortel support services in
241-7001-110, Passport
General Description.
Configuration error Examine the provisioning data
and reconfigure as necessary.
Cannot maintain dpngateway
connectivity
Port failure Replace the function
processor. See 241-7001-125,
Passport Hardware Installation
Guide. In a CFP1 configuration,
you may have to replace the
CFP1 card. (See 241-7001-
170, Passport Control and
Function Processor (CFP1)
User Guide.)
Facilities failure Contact the service provider or
Nortel for assistance. See
Nortel support services in
241-7001-110, Passport
General Description.
Remote DPN processor
element is crashing
See the DPN documentation
suite.
Troubleshooting the Passport node 519
Passport Operations and Maintenance Guide 4S3
Procedure 155
Determining the cause of a DpnGateway failure
1 Issue the display command for the failed dpngateway.
display dpngateway/<n> osistate
where:
<n> is the number of the failed dpngateway.
If adminState = unlocked, operationalState = enabled, and
usageState = busy, you have veried that the DPN Gateway is
operational. Exit this procedure.
If adminState = locked, consult with the operator who took the DPN
Gateway out of service to verify that the DPN Gateway can now be
unlocked and then issue the unlock command. If the DPN Gateway
stages, you have veried that the DPN Gateway is operational. Exit this
procedure or go to step 2 to verify the status of the logical processor.
If operationalState = disabled and availabilityStatus =
dependency, a hardware failure is indicated. The possible failed
components include the function processor, the individual port and the
dpngateway facilities. Go to step 2 to verify the status of the logical
processor.
If operationalState = disabled and availabilityStatus =
<empty>, the problem originates at the remote end. Repeat this
procedure (Determining the cause of a DpnGateway failure on
page 519) at the remote end.
2 Issue the display command for the logical processor on the failed DPN
Gateway:
display lp/<n> osistate
where:
<n> is the logical processor number of the failed DPN Gateway
Note: Determine the logical processor and port assignments by using the
following command display -p dpngateway/<n> utp framer.
If adminState = unlocked, operationalState = enabled, and
usageState = busy, you have veried that the logical processor is
operational. Verify the status of the port.
If operationalState = disabled and availabilityStatus =
dependency, a function processor failure is indicated. Go to section
"Function processor problems" on page 503 to continue the
troubleshooting analysis.
520 Chapter 16
241-7001-150 4S3
3 Issue the display command for the physical port on the failed DPN
Gateway:
display lp/<n> <port>/<m>
where:
<port> is V35, X21, DS1, E1
<n> is the instance number of the LP
<m> is the port number and can be set to any number between 0 and 3
for DS1/E1. For a V35/X21 function processor, the port number can be
any number between 0 and 7. On a CFP1, the port number for V35/X21
port is between 0 and 3.
For example, display lp/10 v35/0 or display lp/3 ds1/3.
If the operationalState = disabled, use the port testing procedure
"Serial port testing" on page 525 to continue the troubleshooting analysis.
Procedure 156
Determining why a dpngateway does not remain connected
1 Issue the display command for the failed dpngateway.
display dpngateway/<n> utp framer
where:
<n> is the number of the failed DPN Gateway
Examine the counts for the errors that are displayed.
2 Wait a few seconds and reissue the display command for the failed DPN
Gateway.
display dpngateway/<n> utp framer
where:
<n> is the number of the failed DPN Gateway
Once again, examine the counts for the errors that are displayed.
If any of these counts are increasing, use the port testing procedure
"Serial port testing" on page 525 to isolate the problem to the port on the
function processor or the communications facility.
If the counts are not increasing, the problem is likely located at the remote
end of the DPN Gateway. Move to that remote Passport node and
continue troubleshooting. If the DPN Gateways function processor is
crashing, see the section titled "Determining the cause of a function
processor crash" on page 506 to continue the analysis.
Troubleshooting the Passport node 521
Passport Operations and Maintenance Guide 4S3
Data collection system problems
Problems with the data collection system are related to the device capacity. A
troubleshooting summary is provided in Troubleshooting problems with the
data collection system on page 521.
Table 58
Troubleshooting problems with the data collection system
Symptom Probable causes Corrective measures
A device is not receiving the
data collection information
(alarm, SCN, log, and debug
data) it requested.
The control processors
message block usage is close
to capacity, probably due to
routing table updates. (May
also apply to a CFP1.)
At least one device will be
receiving all of the data
collection information. Check
all the devices in the network to
locate the information.
522 Chapter 16
241-7001-150 4S3
523
Passport Operations and Maintenance Guide 4S3
Chapter 17
Diagnostic tests
Diagnostic testing allows the operator to test new hardware that is added to
the Passport node and to test hardware that is not functioning properly within
the node. The following tests are available:
port tests, which are used to ensure the card ports can send and receive
data
card tests, which are used to stress test the card
bus tests, which are used to ensure that cards can communicate with other
cards in the node
disk tests, which are used to verify disk integrity or to undertake disk
maintenance
The tests described in this chapter cover the following hardware:
serial ports
cards
buses
disks
Except where noted, descriptions and procedures are provided for operators
working with Passport through a VT-100 terminal or a terminal emulator. If
you are using Nortels proprietary Magellan Network Management System
(NMS) see 241-6001-023, NMS Architect for Passport User Guide.
524 Chapter 17
241-7001-150 4S3
Related documents
See 241-7501-210, Passport Components for additional information related
to diagnostic testing.
Prerequisites for diagnostic testing
You must have system administrator impact to complete the procedures in
this chapter.
Quick access to diagnostic test procedures
To nd procedures quickly, see the following list:
"Testing a serial port on DS1, E1, DS1 MVP, E1 MVP, TTC2MMVP,
and J2MV FPs" on page 540
"Testing a serial port on DS3, E3, DS3C, JT2, and OC-3 FPs" on page
548
"Testing a V35 or V11 serial port" on page 552
"V54 remote loopback testing on a DS1C FP" on page 557
V54 and PN127 remote loopback testing on a E1C FP on page 560
"Testing a serial port on a HSSI FP" on page 566
"Setting up a local external loopback for the far-end" on page 568
"Setting up a local payload loopback for the far-end" on page 569
"Displaying serial port test results" on page 570
"Changing the card test setup" on page 575
"Testing a card" on page 577
"Displaying card test results" on page 579
"Terminator card testing" on page 582
"Testing a bus" on page 585
"Displaying bus test results" on page 587
"Testing a disk" on page 595
"Displaying disk test results" on page 596
Diagnostic tests 525
Passport Operations and Maintenance Guide 4S3
Serial port testing
Serial port diagnostic testing is supported on the components that manage the
port hardware for the function processor (FP):
DS1 component (manages the DS1 ports on DS1, DS1V, DS1 MVP,
DS1C, DS1 ATM, DS1 AAL1, and DS3C function processors)
E1 component (manages the E1 ports on E1, E1V, E1 MVP, J2MV, E1C,
E1 AAl1, E1 ATM, and TTC2M MVP function processors)
DS3 component (manages the DS3 port on DS3, DS3C, and DS3 ATM
function processors)
E3 component (manages the E3 port on E3 and E3 ATM function
processors)
Channel component (controls a group of timeslots that form a fractional
group on a DS1 or E1 port)
HSSI component (manages the HSSI port on a HSSI function processor)
JT2 component (manages the JT2 ports on a JT2 ATM function
processor)
V35 component (manages the V.35 ports on a V.35 function processor
and on a control and function processor [CFP1])
X21 component (manages the V.11 ports on a V.11 function processor
and on a control and function processor [CFP1])
Sonet component (manages the Sonet-provisioned ports on an OC-3
ATM function processor)
Sdh component (manages the Sdh-provisioned ports on an OC-3 ATM
function processor)
There are two groups of diagnostic tests: initial diagnostic tests and
maintenance tests.
Initial diagnostic tests help ensure that ports are fault-free when initialized.
The system runs initial diagnostic tests on a port at initial start up and
whenever the port state is moved into the UNLOCKED state from the
LOCKED state. These initial diagnostic tests are fully automated and do not
require operator intervention.
526 Chapter 17
241-7001-150 4S3
Maintenance tests are used to isolate problem areas on FPs and facilities.
These tests are used to verify that data is properly transmitted and received
along known segments of a link. The following tests are supported:
card loop test
manual loop test
local loop test
remote loop test
Maintenance tests do require manual operation. Essential to maintenance
testing is the insertion of loopbacks. A loopback is used to isolate portions of
the FP or the facility so that the cause of a problem can be narrowed down.
Loopbacks can be set up either through operator commands (controlled
through software) or through direct manipulation of hardware.
To perform a test, the port under test must be out of service (locked). In cases
when the port (for example, HSSI or DS3) responds to a loopback request
through the line connection, an alarm is generated.
Port tests and loopbacks
Strictly speaking, there are four port tests that you can initiate from the local
Passport node. There are also two loopbacks that you set up at the local node
in support of testing initiated for a far-end node. Both tests and loopbacks are
set up through the type attribute of the Test component. Lastly, there is the
physical loopback that you can insert at the hardware level by cross-
connecting the transmit and receive pins.
Component tests on function processors on page 527 summarizes the
maintenance loopback tests and types that are supported through software for
all ATM and non-ATM components.
Diagnostic tests 527
Passport Operations and Maintenance Guide 4S3
Table 59
Component tests on function processors
Component
/Function
processor
Tests Loopbacks
Card
loop
Local
loop
Manual
loop
Remote
loop
Remote
loop
this trib
V54
remote
PN127
remote
External Pay
load
DS1/E1/J2M
(see Notes 1,
2, 9,10)
X X X X X X
Three-port
DS1 ATM
(see Note 3)
X X X X X
Eight-port
DS1 ATM
(see Note 4)
X X X X X
E1 (see
Notes 1, 2,
10 and 11)
X X X X X
One port
DS1 MVP
(See Notes
5, 6)
X X X X
One port
E1 MVP
(See Notes
5, 6)
X X X X
One port
TTC2M MVP
(See Notes
5, 6)
X X X X
Three-port
E1 ATM (see
Note 3)
X X X X
Eight-port
E1 ATM
(see Note 4)
X X X X
(Sheet 1 of 4)
528 Chapter 17
241-7001-150 4S3
Channel X X X
Channel
ATM
DS3 (see
Note 7)
X X X X X
DS3 ATM X X X X X
E3 X X X X
E3 ATM X X X X
JT2 ATM X X X X
DS1 AAL1
(see Notes
12, 13)
X X X X
E1 AAL1
(see Note 9)
X X X
Channel
under AAL1
(see Note
12)
X X
Sonet X X X
Sdh X X X
HSSI (see
Note 8)
X X X X
V35 X X X
CFP1
- V.11
- V.35
X
X
X X
X
X X
X
Table 59 (continued)
Component tests on function processors
Component
/Function
processor
Tests Loopbacks
Card
loop
Local
loop
Manual
loop
Remote
loop
Remote
loop
this trib
V54
remote
PN127
remote
External Pay
load
(Sheet 2 of 4)
Diagnostic tests 529
Passport Operations and Maintenance Guide 4S3
X21 (V.11) X X X X X
Note 1: The remote loop test cannot be done on DS1C or E1C FPs.
Note 2: There are restrictions on attribute settings for diagnostic tests to run on DS1V, E1V, and
J2MV FPs. frmSize must remain at the default setting, and frmPatternType must stay at the default
setting of CustomizedPattern.
Note 3: The payload loop on the DS1 and E1 operates with the clockingSource attribute set to
module or local.
Note 4: Eight-port DS1/E1 ATM FPs support card, manual and remote loop tests only if the port
has a provisioned link to an AtmIf component. All other port tests supported on these FPs are
always available. Ports linked directly to AtmIf components are independent links, as contrasted
with ports that are part of an IMA link group. For details on the difference between IMA links and
independent links, see 241-7001-730, Passport Inverse Multiplexing for ATM User Guide.
Note 5: There is a restriction on setting the frmSize attribute for diagnostic tests to run on
DS1 MVP, E1 MVP, and TTC2M MVP FPs. frmSize cannot exceed 1024.
Note 6: The DS1 MVP loop tests cannot run on a channel associated with timeslot 25 when the
linetype is CAS; the E1 MVP and TTC2M MVP loop tests cannot run on a channel associated with
timeslot 16 when the linetype is CAS.
Table 59 (continued)
Component tests on function processors
Component
/Function
processor
Tests Loopbacks
Card
loop
Local
loop
Manual
loop
Remote
loop
Remote
loop
this trib
V54
remote
PN127
remote
External Pay
load
(Sheet 3 of 4)
530 Chapter 17
241-7001-150 4S3
Tests send data through some or all of a connection. Tests involve setting up
a loopback: for some tests and components, the loopback is set up
automatically through software when the test is defined, while for other tests,
a loopback is set up either by inserting a physical loopback at some point on
the link or by setting component attributes.
A loopback is set up within the local node so that tests can be initiated for
ports on a far-end node. Of itself, a loopback does not initiate a test. On
Passport, loopbacks are set up through component attributes.
The key difference between tests and loopbacks is that tests produce test
results for the local node, while loopbacks do not.
When working with these diagnostic tests, you should always keep in mind
the relationship between the test you are initiating and the loopbacks set up
for that test.
Note 7: The DS3 remote loop test is supported only when the DS3 CbitParity attribute is set to
on. Payload loopbacks are not supported on the DS3C FP.
Note 8: For HSSI, local loop is HSSI LA loopback-type, that is the HSSI Local Digital Loopback
(loop A).
Note 9: The remoteLoopThisTrib test is supported only on the DS1 component of a DS3C FP and
only when the DS3 CbitParity attribute is set to on.
Note 10: The V54 remote loopback test is only available for the DS1C and E1C FPs.
Note 11: The PN127 remote loopback test is only available for the E1C FP.
Note 12: The AAL1 tests are not available when only single timeslot AAL1 CES services are
provisioned.
Note 13: The remote loop test is supported only when the DS1 linetype attribute is set to esf or
esfcas.
Table 59 (continued)
Component tests on function processors
Component
/Function
processor
Tests Loopbacks
Card
loop
Local
loop
Manual
loop
Remote
loop
Remote
loop
this trib
V54
remote
PN127
remote
External Pay
load
(Sheet 4 of 4)
Diagnostic tests 531
Passport Operations and Maintenance Guide 4S3
Card loopback test
The card test is used to test the internal circuits and processors of the FP. It is
supported on all components, both ATM and non-ATM.
The card test automatically loops a test pattern at some point on the link
interface; that is, the test pattern is not sent out on the link. The pattern
received is compared to the pattern transmitted. On the DS1C and E1C FPs,
you can test only one channel component at one time.
The card test is set up through software by setting the type attribute to card.
Hardware modications are not required for this test.
Local loopback test
The local test is used to test the line interface up to but not including the
facility. It is supported on the X21 and HSSI components only.
When this test is initiated, the system automatically sends a request to the
local modem to loop back to the port under test. The specified test pattern is
then transmitted to the local modem as test data. At the end of the test, the
system automatically sends a request to the local modem to take down the
loopback.
A local test is set up by setting the type attribute to localloop. Hardware
modications are not required for diagnostic testing.
Specifics related to the component types are identified in the following
paragraphs.
X21. When setting up local tests on ports associated with an X21 component,
the component must be configured as DTE for the local loop test to run
properly. The X21 component does not respond to a local test request from
the far-end.
532 Chapter 17
241-7001-150 4S3
HSSI. The HSSI local loopback test (also called HSSI Local Digital
Loopback or Loop A) is used to test the link between a DTE and a DCE. the
test is initiated on the DTE side of the connection. The loopback set up and
test is handled by the system in this way:
On the DTE side, the HSSI Local Loop test asserts the LA and LB
loopback control leads and then sends out a test pattern to the other end
DCE for a preset time after a dataStartDelay period.
On the DCE side, the FP detects ON state of the LA and LB loopback
control leads and issues an alarm to warn the operator that the loopback
request has been received and as a result service on this port will be
suspended while the test is in progress. The OSI state at the DCE is
changed to reect this condition.
The DCE implements the loopback at the link controller and the entire
port is looped back. The DCE then asserts the TM signal toward the
DTE.
When the test is completed, the DTE turns off the LA and LB loopback
control leads.
On the DCE side, the FP detects the OFF state of the LA and LB
loopback control leads and takes down the loopback.
The DCE clears the alarm to let the operator know that service will
resume at this port, and sets the OSI state back to the previous state. The
DCE then turns off the TM signal.
Note: The HSSI DCE only responds to the loopback request from the
DTE if it is in the unlocked state.
Manual loopback test
The manual test can be used to test:
the local interface by using a local cable loopback
the line and far-end interface by using an external loopback at the far end
the line and far-end card by using a payload loopback at the far-end
It is supported on all components, both ATM and non-ATM.
Diagnostic tests 533
Passport Operations and Maintenance Guide 4S3
In this test, a loopback must be inserted at some point along the connection,
either through hardware manipulation (a connector or cable) or through a
facility loopback (either the external or payload loopbacks set up on the far-
end). The test can then be initiated, and the test pattern transmitted is
compared to the test pattern received.
The manual test is selected by setting the type attribute to manual.
Note 1: For manual tests on DS1, DS3, and E3 ports, the loop lengths
must be within the required range and the lineLength provisionable
attribute under the DS1, DS3, and E3 components must be properly set.
If the looped signal is not re-amplied, the round-trip loop length for
DS1 cannot exceed 223 m (655 ft), the DS3 round-trip loop length cannot
exceed 153 m (450 ft), and the E3 round-trip loop length cannot exceed
300 m (880 ft).
Note 2: Special attention must be paid to ensure that a clocking source
is available for the test.
Note 3: For a manual test on HSSI components, a physical loopback
through hardware manipulation is not possible. If a manual test is
initiated, an external loopback must be set up on the far-end node.
Remote loopback test
The remote test is used to test to the full length of the facility. This test is
supported on the DS1 (except on DS1C and DS1V FPs), and DS3 components
(both ATM and non-ATM), and on X21 components. Details about each
component remote loop test are provided in the following paragraphs.
The remote loop test is selected by setting the type attribute to remoteLoop.
DS1 remote test. On the DS1 port, a repeated bit pattern (00001) is sent out
of the link to request the far-end CSU to set up a remote loopback. Then the
specified test pattern is transmitted to the remote CSU as test data. At the end
of the test, the Test component automatically requests the remote loop to be
taken down by sending another repeated bit pattern (001).
Note: The DS1 remote loop test is not supported on DS1 ports on DS1V
and DS1C cards.
534 Chapter 17
241-7001-150 4S3
DS3 remote test. On the DS3 port, a line loopback activate signal (carried
over C-bits) is sent over the link to force the remote DS3 port to loop the
signal. The loopback is held until the line loopback deactivate signal is sent
out of the link.
The DS3 remote loop test is supported only when using DS3 C-bit parity
framing mode (the DS3 CbitParity attribute is set to ON). With the attribute
setting, the DS3 component also responds to a remote test request.
X21 remote test. The X21 remote loop test automatically requests the remote
modem to loop back to the port under test. Then the specied test pattern is
transmitted to the remote modem as test data. At the end of the test, the test
component automatically requests the remote loop to be taken down. The X21
component must be configured as DTE for the remote loop test to run
properly.
The X21 component does not respond to a remote loop test request.
Remote loop this trib test
The remote loop this trib test is used to test the full length of the facility. This
test is supported on the DS1 components of the DS3C FP only.
The remote loop this trib test is selected by setting the type attribute to
remoteLoopThisTrib.
On the DS3 port of a DS3C FP, a DS1 line loopback activate signal (carried
over Cbits) is sent over the DS3 link to force a remote DS1 component to loop
the DS1 signal. The loopback is held until a DS1 line loopback deactivate
signal is sent out of the DS3 link.
The DS1 remote loop this trib test is supported only when using DS3 Cbit
parity framing mode (the DS3 CbitParity attribute is set to on).
V54 remote loopback
The V54 remote loopback test is used to test the full length of the facility.
This test is supported on DS1 components of the DS1C FP and E1
components of the E1C FP.
The V54 remote loopback test is selected by setting the type attribute to
v54remoteLoop.
Diagnostic tests 535
Passport Operations and Maintenance Guide 4S3
PN127 remote loopback
The PN127 remote loopback test is used to test the full length of the facility.
This test is supported on the E1 components of the E1C FP.
The PN127 remote loopback test is selected by setting the type attribute to
pn127RemoteLoop.
External loopback
The external loopback (also called line loopback) is used to set up a loopback
on the local node to test ports on a far-end node. This loopback is supported
on all components, both ATM and non-ATM.
The incoming bit stream is looped back out of the function processor. The bit
stream is not terminated, and hence data is neither drawn out of the frame nor
processed. Specic for each component are dened in the following points:
For V35, X21, HSSI, and Channel components, the external loopback is
established at the link controller. In the case of the Channel component,
only the timeslots associated with that particular channel are looped.
Other timeslots dened on other Channel components are not disturbed.
For the DS1, E1, DS3, and E3 components, the external loopback is
established at the line interface circuitry.
The external loopback is not a test, and therefore does not produce test results
for the local node.
The external loop is set up through software by setting the type attribute to
externalloop. Compare this loopback with "Payload loopback" on page
535. When setting up this loopback, you need information on the LP number,
the port instance, and the duration of the test.
Payload loopback
The payload loopback is used to set up a loopback on the local node to support
testing ports on a far-end node. This loopback is supported on DS1 and E1
ATM components, the channel component on DS1 and E1 AAL1 FPs, DS3
and E3 components (both ATM and non-ATM), the i960 for MVP function
processors, and on the JT2 component.
536 Chapter 17
241-7001-150 4S3
The incoming payload is looped back out of the function processor. During
the test, the DS3 or E3 frames (physical level) are terminated and the payload
data is looped over the link controller device.
The payload loopback is not a test, and therefore does not produce test results
for the local node.
The payload loopback is set up by setting the type attribute to payloadLoop.
When setting up this loopback, you need information on the LP number, the
port instance, and the duration of the test.
Generic test process
The generic process for serial port testing is as follows:
1 Lock the port.
2 Select the card type.
3 Start the test.
4 Unlock the card.
Specific test requirements for each port type are described in greater detail in
the following sections.
Testing a serial port on DS1, E1, DS1 MVP, E1 MVP,
TTC2M MVP, and J2MV FPs
This section describes how to test a serial port on DS1, E1, DS1 MVP,
E1 MVP, TTC2MMVP, and J2MV FPs. It also describes how to test a
specific channel on DS1C, E1C, and DS1 and E1 AAL1 FPs. The test and
loopback configurations supported on ATM components are shown in Test
loopback configurations on a DS1 or E1 ATM components on page 537.
Configurations supported on non-ATM and non-AAL1 channelized
components are shown in Test configurations for DS1, E1, DS1 MVP,
E1 MVP, TTC2MMVP, and J2MV components on page 538.
Configurations for DS1 and E1 AAL1 components are shown in "Test
loopback configurations on DS1 and E1 AAL1 components" on page 538.
Diagnostic tests 537
Passport Operations and Maintenance Guide 4S3
Configurations supported on DS1 and E1 AAL1 Channel components are
shown in "Test configurations on DS1 and E1 AAL1 Channel components"
on page 539.
When you initiate either a card or a remote test, the system sets up the
loopback for you. When you initiate the manual loop test, you must set up one
of the following conditions:
a local physical loopback
an external or payload loopback at the far-end node
Figure 68
Test loopback congurations on a DS1 or E1 ATM components
Far-end
DS1/E1
Framer
Payload
Loop
External
Loop
Card
Loop
Manual
Loop
Remote
Loop
(DS1 only)
DS1A
or E1A
Tx/Rx
A
ATM
Cell
Mux/
Demux
PPT 0774 001 AB
B C
538 Chapter 17
241-7001-150 4S3
Figure 69
Test congurations for DS1, E1, DS1 MVP, E1 MVP, TTC2M MVP, and
J2MV components
Figure 70
Test loopback congurations on DS1 and E1 AAL1 components
CSU
Remote loop
(DS1 only)
Manual
loop
Card
loop
External
loop
Link
controller
Line
interface
Function processor
PPT 0040 001 AA
CSU
AAL1
CQC
Controller
External
Loop
Card
Loop
Far-end
PDH
Line
I/f
Framer
Remote
Loop
Manual
Loop
Diagnostic tests 539
Passport Operations and Maintenance Guide 4S3
Figure 71
Test congurations on DS1 and E1 AAL1 Channel components
To make hardware modifications required for a physical loopback, connect
the ports transmit pins to the receive pins. Pin correspondence is shown in
Pin connections for DS1, E1, DS1 MVP, E1 MVP, TTC2MMVP, and
J2MV FP electrical loopback on page 539. See 241-7001-111, Passport
Hardware Description for detailed information on pin outs.
Table 60
Pin connections for DS1, E1, DS1 MVP, E1 MVP, TTC2M MVP, and J2MV
FP electrical loopback
Pin no Pin name TO Pin no Pin name
DS1 (8-port) (see Note 1)
8 Port x, transmit + 7 Port x, receive +
15 Port x, transmit - 14 Port x, receive -
1 Port y, transmit + 2 Port y, receive +
9 Port y, transmit - 10 Port y, receive -
DS1 (4-port), DS1C, E1, E1C, and DS1/E1 AAL1 (see Note 1)
8 Port x, transmit + 7 Port x, receive +
15 Port x, transmit - 14 Port x, receive -
(Sheet 1 of 2)
AAL1
CQC
Controller
Far-end
PDH Line
I/f Framer
Manual
Loop
Payload
Loop
540 Chapter 17
241-7001-150 4S3
Pin cross-connections can be inserted at any point on the link.
The external loopback is set up using "Setting up a local external loopback
for the far-end" on page 568; the payload loopback is set up using "Setting up
a local payload loopback for the far-end" on page 569.
Procedure 157
Testing a serial port on DS1, E1, DS1 MVP, E1 MVP, TTC2M MVP, and
J2MV FPs
If either an external or a payload loopback is used in this test, it must be
in effect at all times during the test. Before initiating the test, ensure that
the loopback is in effect at the far-end node, and will remain in place for
the duration of the test.
1 Specify the test type for this port.
1 Port y, transmit + 2 Port y, receive +
9 Port y, transmit - 10 Port y, receive -
DS1V, E1V, DS1 MVP, and E1 MVP (see Note 2)
8 transmit + 7 receive +
15 transmit - 14 receive -
J2MV and TTC2M MVP (see Note 2)
4 transmit + 2 receive +
11 transmit - 9 receive -
Note 1: The DS1 8-port card has four connectors on the faceplate, while the
DS1 4-port, DS1C, E1, E1C, and DS1/ E1 AAL1 cards have two connectors.
Each connector supports two ports. In this table, Port x refers to the rst port,
and Port y refers to the second port on the same connector. The pin-out
congurations are identical for all connectors and ports. The important rule
of thumb is that transmit and receive pins match up by polarity.
Note 2: The DS1V, E1V, DS1 MVP, E1 MVP, TTC2M MVP, and J2MV are
single port cards.
Table 60 (continued)
Pin connections for DS1, E1, DS1 MVP, E1 MVP, TTC2M MVP, and J2MV
FP electrical loopback
Pin no Pin name TO Pin no Pin name
(Sheet 2 of 2)
Diagnostic tests 541
Passport Operations and Maintenance Guide 4S3
set lp/<n> <port>/<m> test type <testtype>
where:
<n> is the instance number of the logical processor associated with the
port
<port> is one of DS1 or E1
<m> is the instance number of the port to be tested:
0 to 7 for ports on 8-port DS1 and 8-port DS1/E1 ATM cards
0 to 3 for ports on 4-port DS1, DS1C, E1, E1C, DS1/E1 AAL1 cards
0 to 2 for ports on 3-port DS1/E1 ATM cards
0 for ports on DS1V, E1V, DS1 MVP, E1 MVP, TTC2M MVP, and
J2MV cards
<testtype> is one of card, manual, or remoteLoop
Note 1: The remote loopback (type = remoteLoop) is not supported on
the E1, E1 ATM, E1 AAL1, DS1C, and E1C FPs.
Note 2: Eight-port DS1/E1 ATM FPs support card, manual and remote
loop tests only if the port has a provisioned link to an AtmIf component
(see Table 59 on page 527 for details).
Note 3: The ports that are available on ATM FPs depend on whether
trafc shaping is enabled. For details, see the section on trafc shaping in
241-7001-700, Passport ATM Core Services User Guide.
2 Set the time needed to run the test.
set lp/<n> <port>/<m> test duration <limit>
where:
<limit> is the duration (in minutes) that the test will run. The default time
limit is one minute.
3 Lock the port.
lock lp/<n> <port>/<m>
Note: When the port is locked, it cannot provide service.
4 If the test requires a physical loopback through hardware modication,
insert the loopback at the appropriate point on the link.
If you need either an external loopback or a payload loopback set up for
the far-end node, do this now. You need to dene the LP number, port
instance, and duration of the test.
The external loopback is set up using "Setting up a local external
loopback for the far-end" on page 568; the payload loopback is set up
using "Setting up a local payload loopback for the far-end" on page 569.
Note: The payload loopback is supported on DS1 and E1 ATM FPs only.
542 Chapter 17
241-7001-150 4S3
5 Start the port test.
start lp/<n> <port>/<m> test
6 Optionally, display test statistics.
display lp/<n> <port>/<m> test
7 Stop the test.
stop lp/<n> <port>/<m> test
8 If you set up a physical or far-end external or payload loopback, remove
it now.
9 Unlock the port to restore service.
unlock lp/<n> <port>/<m>
Procedure 158
Testing a Channel on DS1 and E1 AAL1 FPs
If either a manual or a payload loopback is used in this test, it must be in
effect at all times during the test. Before initiating the test, ensure that the
loopback is in effect and remains for the duration of the test.
1 Specify the test type for this channel.
set lp/<n> <port>/<m> channel/<c> test type <testtype>
where:
<n> is the instance number of the logical processor associated with the
port
<port> is one of DS1 or E1
<m> is the instance number of the port containing the channel to be
tested:
0 to 3 for ports on 4-port DS1 and E1 AAL1 cards.
<c> is the instance number of the channel to be tested:
0 to 23 for channels on DS1 AAL1 cards
0 to 31 for channels on E1 AAL1 cards
<testtype> is one of manual, or payload.
2 Set the time needed to run the test.
set lp/<n> <port>/<m> channel/<c> test duration
<limit>
where:
<limit> is the duration (in minutes) that the test will run. The default time
limit is one minute.
Diagnostic tests 543
Passport Operations and Maintenance Guide 4S3
3 Lock the channel.
lock lp/<n> <port>/<m> channel/<c>
Note: When the channel is locked, it cannot provide service.
4 If the test requires a physical loopback through hardware modication,
insert the loopback at the appropriate point on the link.
5 Start the channel test.
start lp/<n> <port>/<m> channel/<c> test
6 Optionally, display test statistics.
display lp/<n> <port>/<m> channel/<c> test
7 Stop the test.
stop lp/<n> <port>/<m> channel/<c> test
8 If you set up a physical loopback, remove it now.
9 Unlock the channel to restore service.
unlock lp/<n> <port>/<m> channel/<c>
Testing a DS1 tributary on a DS3C function processor
This section describes how to test a DS1 tributary on a DS3C function
processor. The test and loopback configurations supported are shown in "Test
configurations for DS1 tributary on DS3C FPs" on page 544.
544 Chapter 17
241-7001-150 4S3
Figure 72
Test congurations for DS1 tributary on DS3C FPs
When you initiate a card test, a remote test, or a remote loop this trib test, the
system sets up the loopback for you. When you initiate the manual loop test,
you must set one of the following conditions before running the test:
a local physical loopback (see Pin connections for DS1, E1, DS1 MVP,
E1 MVP, TTC2MMVP, and J2MV FP electrical loopback on
page 539)
an external loopback at the far-end node
The external loopback is set up using Setting up a local external loopback
for the far-end on page 568.
Procedure 159
Testing a DS1 tributary on a DS3C FP
1 Specify the test type for the tributary
set lp/<n> ds3/0 ds1/<m> test type <testtype>
where:
<n> is the instance number of the logical processor associated with the
DS3C
<m> is the instance of the DS1 tributary (1 to 28)
<testtype> is one of card, manual, remoteloop, remoteloopthistrib
Note: The remoteloopthistrib test is supported only when the DS3
CbitParity attribute is set to on.
Far-end
CSU or
DSU
Passport node
DS1C FP
Remote loop
(Channel only)
PPT 1080 000 AA
Diagnostic tests 545
Passport Operations and Maintenance Guide 4S3
2 Set the time needed to run the test.
set lp/<n> ds3/0 ds1/<m> test duration <limit>
where:
<limit> is the duration (in minutes) that the test will run. The default time
limit is one minute.
3 Lock the DS1 tributary
lock lp/<n> ds3/0 ds1/<m>
Note: When the tributary is locked, it can not provide service.
4 If the test requires a physical loopback through hardware modication,
insert the loopback at the appropriate point on the link.
If you need an external loopback set up for the far-end node, do this now.
You need to dene the LP number, port instance, and duration of the test.
The external loopback is set up using "Setting up a local external
loopback for the far-end" on page 568.
5 Start the DS1 tributary test
start lp/<n> ds3/0 ds1/<m> test
6 Optionally, display test statistics.
display lp/<n> ds3/0 ds1/<m> test
7 Wait for the test timer to expire, or stop the test.
stop lp/<n> ds3/0 ds1/<m> test
8 If you set a physical or far-end external loopback, remove it now.
9 Unlock the DS1 tributary to restore service.
unlock lp/<n> ds3/0 ds1/<m>
Testing a serial port on DS3, E3, DS3C, JT2, and OC-3 FPs
This section describes how to test a serial port on DS3, E3, DS3C, JT2, and
OC-3 FPs. The test and loopback congurations supported are shown in:
Test congurations for DS3 and E3 non-ATM FPs on page 546
Test loopback congurations on a DS3 and E3 ATM FPs on page 546
Test loopback congurations on a JT2 ATM FP on page 547
Test loopback congurations on an OC-3 ATM FP on page 547
546 Chapter 17
241-7001-150 4S3
Figure 73
Test congurations for DS3 and E3 non-ATM FPs
Note: DS3C FPs have no payload loop.
Figure 74
Test loopback congurations on a DS3 and E3 ATM FPs
Far-end
terminal
Remote loop
(DS3 only)
Manual
loop
Card
loop
External
loop
Link
controller
Line
interface
Function processor
Payload
loop
PPT 0041 001 AA
Far-end
SUNI-PDH
Payload
Loop
External
Loop
Card
Loop
Manual
Loop
Remote
Loop
(DS3 only)
DS3A
/E3A
Tx/Rx
A
ATM
Cell
Mux/
Demux
PPT 0773 001 AA
B C
Diagnostic tests 547
Passport Operations and Maintenance Guide 4S3
Figure 75
Test loopback congurations on a JT2 ATM FP
Figure 76
Test loopback congurations on an OC-3 ATM FP
When you initiate either a card or a remote test, the system sets up the
loopback for you. When you initiate the manual loop test, you must set up one
of the following conditions prior to running the test:
a local physical loopback
an external or payload loopback at the far-end node
SUNI-PDH
Payload
Loop
External
Loop
Card
Loop
Manual
Loop
JT2
Framer
A
JT2
Line
I/F
ATM
Cell
Mux/
Demux
PPT 0775 001 AA
C D
SUNI-LITE
Card
Loop
External
Loop
Manual
Loop
Optical
I/F
ATM
Cell
Mux/
Demux
PPT 0776 001 AA
548 Chapter 17
241-7001-150 4S3
To make hardware modifications required for a physical loopback, connect
the transmit connector to the receive connector using a cable. The loopback
can be inserted at any point on the link. Provision the line links to reflect the
length of cable used for the loopback.
The external loopback is set up using "Setting up a local external loopback
for the far-end" on page 568; the payload loopback is set up using "Setting up
a local payload loopback for the far-end" on page 569.
Procedure 160
Testing a serial port on DS3, E3, DS3C, JT2, and OC-3 FPs
If either an external or a payload loopback is used in this test, it must be
in effect at all times during the test. Before initiating the test, ensure that
the loopback is in effect at the far-end node, and will remain in place for
the duration of the test.
1 Specify the test type for this port.
set lp/<n> <port>/<m> test type <testtype>
where:
<n> is the instance number of the logical processor associated with the
port
<port> is one of DS3, E3, JT2, Sonet, or Sdh
<m> is the instance number of the port to be tested:
0 to 2 for ports on DS3 and E3 ATM cards, and OC-3 ATM cards
0 or 1 for ports on JT2 ATM cards
0 for ports on DS3 and E3 non-ATM cards and DS3C cards
<testtype> is one of card, manual, localLoop, remoteLoop
Note: The remote test is not supported on E3 and JT2 cards. The DS3
remote loop test is supported only when the DS3 CbitParity attribute is set
to on. The local loop test is not supported on the DS3C FP.
2 Set the time needed to run the test.
set lp/<n> <port>/<m> test duration <limit>
where:
<limit> is the duration (in minutes) that the test will run. The default time
limit is one minute.
3 Lock the port.
lock lp/<n> <port>/<m>
Note: When the port is locked, it cannot provide service.
Diagnostic tests 549
Passport Operations and Maintenance Guide 4S3
4 If the test requires a physical loopback through hardware modication,
insert the loopback at the appropriate point on the link.
If you need either an external loopback or a payload loopback set up for
the far-end node, do this now. You need to dene the LP number, port
instance, and duration of the test.
The external loopback is set up using "Setting up a local external
loopback for the far-end" on page 568; the payload loopback is set up
using "Setting up a local payload loopback for the far-end" on page 569.
5 Start the port test.
start lp/<n> <port>/<m> test
6 Optionally, display test statistics.
display lp/<n> <port>/<m> test
7 Wait for the test timer to expire, or stop the test.
stop lp/<n> <port>/<m> test
8 If you set up a physical or far-end external or payload loopback, remove
it now.
9 Unlock the port to restore service.
unlock lp/<n> <port>/<m>
Testing a serial port on V35 and V11 FPs
This section describes how to test a serial port on V35 and V11 FPs. The test
and loopback configurations supported are shown in Test configurations for
V35, V11, and HSSI FPs on page 550.
Note: You can also test V.35 and V.11 (X21) serial ports on a control
and function processor (CFP1).
550 Chapter 17
241-7001-150 4S3
Figure 77
Test congurations for V35, V11, and HSSI FPs
When you initiate a card test, a local test, or a remote test, the system sets up
the loopback for you. When you initiate the manual loop test, you must set up
one of the following conditions:
a local physical loopback (V35 and V11 ports, DCE mode only)
an external loopback at the far-end node (V35 and V11 ports in both DCE
and DTE modes, and HSSI ports)
For manual tests on V35 and V11 ports, how the test is undertaken depends
on whether the port is configured for DTE mode or for DCE mode.
The external loopback is set up using "Setting up a local external loopback
for the far-end" on page 568.
Manual testing V35 and V11 ports in DTE mode
On DTE ports, manual testing using a physical loopback inserted at the
termination panel is not supported. Manual testing can only be initiated where
either test equipment or another Passport provides a loopback point. In this
test configuration, the equipment that provides the loopback also provides the
clock source.
Remote loop
(X21 only)
External
loop
Link
controller
Line
interface
Function processor
Card
loop
Local loop
(X21+HSSI only)
Manual
loop
CSU or
modem
Channel
service unit
(CSU) or
modem
PPT 0042 001 AA
Diagnostic tests 551
Passport Operations and Maintenance Guide 4S3
Manual testing V35 and V11 ports in DCE mode
If the port is provisioned for dteDataClockSource = fromDce, physical
looping of the clock is not required.
Note: If you need to insert a physical clock loopback at the termination
panel, you must enter provisioning mode and change the value for the
dteDataClockSource to fromDte. When the test is completed, change the
clock source back to fromDce.
If the port is provisioned for dteDataClockSource = fromDte, physical
looping of the clock can be used (see Pin connections for V11 and V35
electrical loopback on page 551). Alternately, external test equipment or
another Passport with external loopback in effect can be used at the loopback
point.
In each of these test configurations, looping of the transmit pins to the receive
pins is used if a physical loopback is needed. To make hardware
modifications required for a physical loopback on V35 and V11 ports,
connect the transmit pins to the receive pins. The loopback can be inserted at
the termination panel only.
Table 61
Pin connections for V11 and V35 electrical loopback
Pin no Pin name TO Pin no Pin name
V35 (see Note)
2 TXDA 4 RXDA
9 TXDB 11 RXDB
6 TSET (DTE) B 7 TSETB
13 TEST (DTE) A 14 TSETA
V11 (see Note)
2 TA 4 RA
9 TB 11 RB
6 SA 7 XA
(Sheet 1 of 2)
552 Chapter 17
241-7001-150 4S3
See the appropriate hardware guide for detailed information on pin outs.
Testing a V35 or V11 serial port
This procedure describes how to test a V35 or V11 serial port.
Procedure 161
Testing a V35 or V11 serial port
If an external loopback is used in this test, it must be in effect at all times
during the test. Before initiating the test, ensure that the loopback is in
effect at the far-end node, and will remain in place for the duration of the
test.
1 Specify the test type for this port.
set lp/<n> <port>/<m> test type <testtype>
where:
<n> is the instance number of the logical processor associated with the
port
<port> is one of V35 or X21
<m> is the instance number of the port to be tested (0 to 7)
<testtype> is one of card, manual, localLoop, or remoteLoop
The instance number <m> for V.35 and V.11 (X21) serial ports on the
CFP1 can be from 0 to 3.
Note: Local and remote tests are not supported on V35 FPs.
2 Set the time needed to run the test.
set lp/<n> <port>/<m> test duration <limit>
where:
<limit> is the duration (in minutes) that the test will run. The default time
limit is one minute.
13 SB 14 XB
Note: Pin cross-connections for the clock source is optional (pins 6, 7, 13,
and 14 for both V35 and V11 ports).
Table 61 (continued)
Pin connections for V11 and V35 electrical loopback (continued)
Pin no Pin name TO Pin no Pin name
(Sheet 2 of 2)
Diagnostic tests 553
Passport Operations and Maintenance Guide 4S3
3 Lock the port.
lock lp/<n> <port>/<m>
Note: When the port is locked, it cannot provide service.
4 If the test requires a physical loopback through hardware modication,
insert the loopback at the appropriate point on the link.
If you need an external loopback set up for the far-end node, do this now.
You need to dene the LP number, port instance, and duration of the test.
The external loopback is set up using "Setting up a local external
loopback for the far-end" on page 568.
5 Start the port test.
start lp/<n> <port>/<m> test
6 Optionally, display test statistics.
display lp/<n> <port>/<m> test
7 Stop the test.
stop lp/<n> <port>/<m> test
8 If you set up a physical or far-end external loopback, remove it now.
9 Unlock the port to restore service.
unlock lp/<n> <port>/<m>
V54 remote loopback
This section describes the following:
V54 remote loopback support
V54 remote loopback testing on a DS1C FP
V54 and PN127 remote loopback testing on a E1C FP
V54/PN127 remote loopback troubleshooting
V54 remote loopback support
This section details the scope of support in various equipment configurations.
It provides a summary of supported and unsupported items in the table
Summary of V54 supported and unsupported items on page 554.
554 Chapter 17
241-7001-150 4S3
Table 62
Summary of V54 supported and unsupported items
Network
configuration
Supported Unsupported
DS1C to a Fractional
T1 network
(see DS1C to a
fractional T1 network
configuration on
page 556)
One Nx64 kbps (N = 1 to 24)
Chan component with B8ZS line
coding and ESF framing format
running one V54 test per port
One Nx64 kbps (N = 1 to 24)
Chan component with AMI line
coding and ESF or D4 framing
format
One Nx56 kbps (N = 1 to 24)
Chan component with B8ZS/AMI
line coding and ESF/D4 framing
format running one V54 test per
port
V54 loopback test can be initiated
from one Chan component per
DS1C port without affecting trafc
on other channels off the same
port
DS1C to a DDS
network
(see DS1C to a DDS
network
configuration on
page 556)
DDS Customer Primary Channel
Data Rate of 64 kbps (Clear
Channel), 72.0 kbps OCU/Loop
Data Rate, a DS1conguration of
B8ZS line coding, and ESF
framing format
DS1C does not respond to DDS
Network Control Codes
DS1C does not transport DDS
Network Control Codes
DS1C to a DDS
network
(see DS1C to a DDS
network
configuration on
page 556)
DDS Customer Primary Channel
Data Rate of 56 kbps, 56 kbps
OCU/Loop Data Rate, a DS1
conguration of B8ZS line coding
and ESF framing format
DDS Secondary Channel
Signalling either standard or
proprietary
Supports only 56 kbps and 64
kbps Customer Primary Channel
Data Rate
Applicable to a DS1C
to a Fractional T1
network and DS1C to
a DDS network
DS1C sends V54 loop-up and
loop-down patterns to remote DSI
as part of one V54 test cycle
DS1C does not respond to V54
loop-up and loop-down patterns
that are generated externally
(Sheet 1 of 2)
Diagnostic tests 555
Passport Operations and Maintenance Guide 4S3
Maximum one V54 test per DS1C
port at a time
DS1C ignores V54
acknowledgment signalling
Maximum four simultaneous V54
tests per DS1C card such that
there is one V54 test running per
port
E1C test
conguration
(see V.54 and
PN127 E1C test
configuration on
page 557)
One Nx64 kbps (N = 1 to 31)
Chan component using ccs
framing format running one V.54
test per port.
V.54 loopback test can be
initiated from one Chan
component per E1C port without
effecting trafc on other channels
on that specic port.
Rates lower than 64 kbps are
not supported.
PN127 E1C test
conguration
(see V.54 and
PN127 E1C test
conguration on
page 557)
One Nx64 kbps (N = 1 to 31)
Chan component using ccs
framing format running one V.54
test per port.

V.54 loopback test can be

initiated from one Chan
component per E1C port without
effecting trafc on other channels
on that specic port.
Rates lower than 64 kbps are
not supported.
Table 62 (continued)
Summary of V54 supported and unsupported items
Network
configuration
Supported Unsupported
(Sheet 2 of 2)
556 Chapter 17
241-7001-150 4S3
Figure 78
DS1C to a fractional T1 network conguration
Figure 79
DS1C to a DDS network conguration
PPT 1097 001 AA
Passport node
DS1 level connection
DS0 level connection
V35 connection
DS1C
DSU/CSU
DSU/CSU
DSU/CSU
DTE
DTE
DTE

Fractional
T1 network
PPT 1098 001 AB
Passport node
DS1 level connection
DS0 level connection
V35 connection
DS1C
DDS DSU
DDS DSU
DDS DSU
DTE
DTE
DTE

DDS
network
Diagnostic tests 557
Passport Operations and Maintenance Guide 4S3
Figure 80
V.54 and PN127 E1C test conguration
V54 remote loopback testing on a DS1C FP
This section describes how to perform a V54 remote loopback test on a DS1C
FP. The test and loopback configurations supported are shown in the figure
V54 remote loopback test configuration on page 558.
PPT 1097 002 AA
Passport node
E1 level connection
V35 connection
E1C
NTU DTE
DTE
DTE

Fractional
E1 network
NTU
NTU
558 Chapter 17
241-7001-150 4S3
Figure 81
V54 remote loopback test conguration
Procedure 162
V54 remote loopback test for DS1C
For this procedure, assume that there is a DS1C FP provisioned in the
Passport node, and that the connection to the CSU/DSU is up and
running. The following steps are required to invoke and terminate the V54
remote loopback test.
Note: The DS1C FP supports V54 remote loopback for 64 kbps and
56 kbps timeslot data rates. Make sure it is provisioned to the correct
timeslot data rate expected by the far-end circuit termination equipment.
1 Lock the specied channel.
3> lock lp/5 ds1/2 ch/0
Lp/5 DS1/2 Chan 0
ok 1997-03-22 20:40:27.58
2 Specify the test type for this channel.
4> set lp/5 ds1/2 ch/0 test type v54RemoteLoop
Lp/5 DS1/2 Chan/0 Test
ok 1997-03-22 20:50:02.91
3 Start the test.
5> start lp/5 ds1/2 ch/0 test
Far-end
CSU or
DSU
Passport node
DS1C FP
Remote loop
(Channel only)
PPT 1080 000 AA
Diagnostic tests 559
Passport Operations and Maintenance Guide 4S3
Lp/5 DS1/2 Chan/0 Test
Test started.
4 While the V54 remote loopback test is running, you can display the
current test results.
6> display lp/5 ds1/2 ch/0 Test
Lp/5 DS1/2 Chan/0 Test
adminState = unlocked
operationalState = enabled
usageState = busy
purpose = ?
type = v54RemoteLoop
frmSize = 1024 bytes
frmPatternType = ccitt32kBitPattern
customizedPattern = 55555555 Hex
dataStartDelay = 0 seconds
displayInterval = 5 minutes
duration = 1 minutes
elapsedTime = 0 minutes
timeRemaining = 1 minutes
causeOfTermination = testRunning
bitsTx = 57344
bytesTx = 7168
frmTx = 7
bitsRx = 0
bytesRx = 0
frmRx = 0
erroredFrmRx = 0
bitErrorRate = 0e+00
ok 1997-03-22 01:58:11.32
5 When the V54 remote loopback test is complete, the cumulative test
results are displayed.
--- Response 5 continued ...
Lp/5 DS1/2 Chan/0 Test
elapsedTime = 1 minutes
timeRemaining = 0 minutes
bitsTx = 6004736
bytesTx = 750592
frmTx = 733
bitsRx = 6004736
bytesRx = 750592
frmRx = 733
erroredFrmRx = 0
560 Chapter 17
241-7001-150 4S3
bitErrorRate = 0e+00
Test stopped.
ok 1997-03-22 01:59:09.37
6 If the V54 remote loopback test is halted before its completion, only the
short response is displayed.
6> stop lp/5 ds1/2 ch/0 test
--- Response 7 continued ...
Lp/5 DS1/2 Chan/0 Test
elapsedTime = 0 minutes
timeRemaining = 0 minutes
bitsTx = 3309568
bytesTx = 413696
frmTx = 404
bitsRx = 3309568
bytesRx = 413696
frmRx = 404
erroredFrmRx = 0
bitErrorRate = 0e+00
Test stopped.
ok 1997-03-22 02:00:30.24
V54 and PN127 remote loopback testing on a E1C FP
This section describes how to perform a V54 and PN127 remote loopback test
on a E1C FP. The test and loopback configurations supported are shown in
the figure V.54 and PN127 remote loopback test configuration on
page 561.
Diagnostic tests 561
Passport Operations and Maintenance Guide 4S3
Figure 82
V.54 and PN127 remote loopback test conguration
For this procedure, assume that there is a E1C FP provisioned in the Passport
node, and that the connection to the NTU is up and running. The following
steps are required to invoke and terminate the V54 and PN127 remote
loopback test.
Note: The E1C FP supports V54 remote loopback for 64 kbps timeslot
data rates. Make sure it is provisioned to the correct timeslot data rate
expected by the far-end circuit termination equipment.
Procedure 163
V54 remote loopback test for E1C
1 Lock the specied channel.
lock lp/4 e1/0 ch/0
Lp/4 e1/0 Chan 0
ok
2 Specify the test type for this channel.
set lp/4 e1/0 ch/0 test type v54RemoteLoop
Lp/4 e1/0 Chan/0 Test
ok
3 Start the test.
Far-end
NTU
Passport node
E1C FP
Remote loop
(Channel only)
PPT 1080 002 AA
562 Chapter 17
241-7001-150 4S3
start lp/4 e1/0 ch/0 test
Lp/4 e1/0 Chan/0 Test
Test started.
4 While the V54 remote loopback test is running, you can display the
current test results.
display lp/4 e1/0 ch/0 Test
Lp/4 e1/0 Chan/0 Test
adminState = unlocked
operationalState = enabled
usageState = busy
purpose = ?
type = v54RemoteLoop
frmSize = 1024 bytes
frmPatternType = ccitt32kBitPattern
customizedPattern = 55555555 Hex
dataStartDelay = 0 seconds
displayInterval = 5 minutes
duration = 1 minutes
elapsedTime = 0 minutes
timeRemaining = 1 minutes
causeOfTermination = testRunning
bitsTx = 4284416
bytesTx = 535552
frmTx = 523
bitsRx = 4276224
bytesRx = 534528
frmRx = 522
erroredFrmRx = 0
bitErrorRate = 0e+00
ok
5 When the V54 remote loopback test is complete, the cumulative test
results are displayed.
--- Response 30 continued ...
Lp/4 e1/0 Chan/0 Test
elapsedTime = 1 minutes
timeRemaining = 0 minutes
bitsTx = 53444608
bytesTx = 6680576
frmTx = 6524
bitsRx = 53444608
bytesRx = 6680576
Diagnostic tests 563
Passport Operations and Maintenance Guide 4S3
frmRx = 6524
erroredFrmRx = 0
bitErrorRate = 0e+00
Test stopped.
ok
6 If the V54 remote loopback test is halted before its completion, only the
short response is displayed.
stop lp/4 e1/0 ch/0 test
--- Response 7 continued ...
Lp/4 e1/0 Chan/0 Test
elapsedTime = 0 minutes
timeRemaining = 0 minutes
bitsTx = 502224608
bytesTx = 62760786
frmTx = 4538
bitsRx = 50111706
bytesRx = 6030166
frmRx = 3286
erroredFrmRx = 0
bitErrorRate = 0e+00
Test stopped.
ok
Procedure 164
PN127 remote loopback test for E1C
1 Lock the specied channel.
lock lp/4 e1/3 ch/0
Lp/4 e1/3 Chan 0
ok
2 Specify the test type for this channel.
set lp/4 e1/3 ch/0 test type pn127RemoteLoop
Lp/4 e1/3 Chan/0 Test
ok
3 Start the test.
start lp/4 e1/3 ch/0 test
Lp/4 e1/3 Chan/0 Test
Test started.
564 Chapter 17
241-7001-150 4S3
4 While the V54 remote loopback test is running, you can display the
current test results.
display lp/4 e1/3 ch/0 Test
Lp/4 e1/3 Chan/0 Test
adminState = unlocked
operationalState = enabled
usageState = busy
purpose = ?
type = pn127RemoteLoop
frmSize = 1024 bytes
frmPatternType = ccitt32kBitPattern
customizedPattern = 55555555 Hex
dataStartDelay = 0 seconds
displayInterval = 5 minutes
duration = 1 minutes
elapsedTime = 0 minutes
timeRemaining = 1 minutes
causeOfTermination = testRunning
bitsTx = 2072576
bytesTx = 259072
frmTx = 253
bitsRx = 2064384
bytesRx = 258048
frmRx = 252
erroredFrmRx = 0
bitErrorRate = 0e+00
ok
5 When the V54 remote loopback test is complete, the cumulative test
results are displayed.
--- Response 30 continued ...
Lp/4 e1/3 Chan/0 Test
elapsedTime = 1 minutes
timeRemaining = 0 minutes
bitsTx = 3497984
bytesTx = 437248
frmTx = 427
bitsRx = 3497984
bytesRx = 437248
frmRx = 427
erroredFrmRx = 0
bitErrorRate = 0e+00
Diagnostic tests 565
Passport Operations and Maintenance Guide 4S3
Test stopped.
ok
6 If the V54 remote loopback test is halted before its completion, only the
short response is displayed.
stop lp/4 e1/3 ch/0 test
--- Response 7 continued ...
Lp/4 e1/3 Chan/0 Test
elapsedTime = 0 minutes
timeRemaining = 0 minutes
bitsTx = 2873816
bytesTx = 305764
frmTx = 323
bitsRx = 3079648
bytesRx = 353328
frmRx = 357
erroredFrmRx = 0
bitErrorRate = 0e+00
Test stopped.
ok
V54/PN127 remote loopback troubleshooting
This section describes the troubleshooting procedures in the table Loopback
troubleshooting on page 566.
566 Chapter 17
241-7001-150 4S3
Testing a serial port on a HSSI FP
HSSI ports are manually tested using an external loopback at the far-end
node. Manual testing using a physical loopback is not supported.
Procedure 165
Testing a serial port on a HSSI FP
If an external loopback is used in this test, it must be in effect at all times
during the test. Before initiating the test, ensure that the loopback is in
Table 63
Loopback troubleshooting
Problem Solution
frmRx not increasing after
starting the test
It takes about six seconds to actually see the test data looped back
because the CSU/DSU takes six seconds to respond to the loop-
up pattern that is sent from the Passport node. If after six seconds,
the frmRx counter is still not incrementing, the CSU/DSU is not
triggered to loop back. There could be a connection problem with
the CSU/DSU.
Verification of loopback
removal upon test
completion
Since there is no acknowledgment for the loop-down pattern, it is
hard to tell when the CSU/DSU is out of loopback mode. To make
sure that the CSU/DSU is out of loopback mode, perform another
manual loop from the Passport node. If the loop is not down, then
the frmTx and frmRx counters both increase. If the loop is down,
then the frmRx counter does not increase.
Error frames at the
beginning of the test
Some of the CSU/DSU equipment takes longer to respond to the
loop-up pattern. On the Passport node, you only have to wait for
six seconds for the CSU/DSU to go to loopback mode and start
sending the real test data. Meanwhile, the CSU/DSU responds to
the loop-up pattern by sending the acknowledge pattern. If the
reception of the acknowledge pattern finishes after the six second
period, there will be error frames.
To avoid this condition, set the dataStartDelay attribute inside the
test component to be a value other than 0; the real test data will
commence after this specified time in seconds.
Random error frames during
the test
Random error frames could be caused by a non-terminated V.351
cable connected to the CSU/DSU. Check the cabling to make sure
that this is not the problem; a non-terminated cable could pick up
noise that disrupts the normal test data and results in error frames.
Diagnostic tests 567
Passport Operations and Maintenance Guide 4S3
effect at the far-end node, and will remain in place for the duration of the
test.
1 Specify the test type for this port.
set lp/<n> HSSI/0 test type <testtype>
where:
<n> is the instance number of the logical processor associated with the
port
<testtype> is one of card, manual, or localLoop
2 Set the time needed to run the test.
set lp/<n> HSSI/0 test duration <limit>
where:
<limit> is the duration (in minutes) that the test will run. The default time
limit is one minute.
3 Lock the port.
lock lp/<n> HSSI/0
Note: When the port is locked, it cannot provide service.
4 If the test requires an external loopback set up for the far-end node, do
this now. You need to dene the LP number, port instance, and duration
of the test.
The external loopback is set up using "Setting up a local external
loopback for the far-end" on page 568.
5 Start the port test.
start lp/<n> HSSI/0 test
6 Optionally, display test statistics.
display lp/<n> HSSI/0 test
7 Stop the test.
stop lp/<n> HSSI/0 test
8 If you set up a physical or far-end external loopback, remove it now.
9 Unlock the port to restore service.
unlock lp/<n> HSSI/0
568 Chapter 17
241-7001-150 4S3
Setting up a local external loopback for the far end
Use this procedure to set up an external loopback on the local node as
required for testing a port on the far-end node. You need information on the
target LP and port needed for the loopback and the time required to complete
the test.
Note: This loopback must be in effect at all times during the port test.
When setting up this loopback, be certain that the loopback starts before
the test begins and terminates after the test completes.
Procedure 166
Setting up a local external loopback for the far-end
1 Check that the port is either receiving a clock source from the line or
providing its own clock source.
2 Lock the port on the LP that will be used for the test.
lock lp/<n> <port>/<m>
where:
<n> is the instance number of the logical processor linked to the port to
be tested
<port> is one of DS1, E1, DS3, E3, JT2, HSSI, Sonet, Sdh, X21, or V35
<m> is the instance number of the port to be tested and can be set to:
0 to 7 for ports on 8-port DS1, V.35, V.11, and 8-port DS1/E1 ATM cards
0 to 3 for ports on 4-port DS1, E1, DS1C, E1C and DS1/E1 AAL1 cards
0 to 2 for ports on DS1, E1, DS3, E3, 3-port DS1/E1 ATM, DS3/E3 ATM,
and OC-3 ATM cards
0 to 3 for ports on V35 or V.11 (X21) ports on CFP1 cards
0 or 1 for ports on JT2 cards
0 for ports on DS1V, E1V, J2MV, DS3, E3, and HSSI cards
3 Set the type attribute for external loopback.
set lp/<n> <port>/<m> test type externalLoop
4 Set the maximum amount of time you will allow the test to run.
set lp/<n> <port>/<m> test duration <limit>
where:
<limit> is the duration (in minutes) that the test will run (the default is 1
min)
Note: Always set the duration to a value that is higher than that used at
the far-end (where the test is initiated).
Diagnostic tests 569
Passport Operations and Maintenance Guide 4S3
5 Activate the external loopback.
start lp/<n> <port>/<m> test
6 Wait until the operator at the far-end ofce indicates that testing is
complete.
7 Wait for the test duration timer to expire, or stop the external loopback.
stop lp/<n> <port>/<m> test
8 Unlock the port on the LP that was used for the test.
unlock lp/<n> <port>/<m>
Setting up a local payload loopback for the far end
Use this procedure to set up the payload loopback on the local node as
required for testing ports on the far-end node. You need information on the
target LP and port needed for the loopback and the time required to complete
the test.
Note: This loopback must be in effect at all times during the port test.
When setting up this loopback, be certain that the loopback starts before
the test begins and terminates after the test completes.
Procedure 167
Setting up a local payload loopback for the far-end
1 Check that the port is either receiving a clock source from the line or
providing its own clock source.
2 Lock the port on the LP that will be used for the test.
lock lp/<n> <port>/<m>
where:
<n> is the instance number of the logical processor linked to the port to
be tested
<port> is one of DS3, E3, or JT2
<m> is the instance number of the port to be tested and can be set to:
0 to 7 for ports on 8-port DS1/E1 ATM FPs
0 to 2 for ports on 3-port DS1/E1 ATM, DS3/E3 ATM cards
0 or 1 for ports on JT2 cards
0 for ports on DS3 and E3 cards
3 Set the type attribute for payload loopback.
set lp/<n> <port>/<m> test type payloadLoop
570 Chapter 17
241-7001-150 4S3
4 Set the maximum amount of time you will allow the test to run.
set lp/<n> <port>/<m> test duration <limit>
where:
<limit> is the duration (in minutes) that the test will run (the default is 1
min)
Note: Always set the duration to a value that is higher than that used at
the far-end (where the test is initiated).
5 Activate the external loopback.
start lp/<n> <port>/<m> test
6 Wait until the operator at the far-end ofce indicates that testing is
complete.
7 Wait for the test duration timer to expire, or stop the external loopback.
stop lp/<n> <port>/<m> test
8 Unlock the port on the LP that was used for the test.
unlock lp/<n> <port>/<m>
Displaying serial port test results
The following procedure explains how to display the attributes of the serial
port test.
Procedure 168
Displaying serial port test results
1 Display characteristics associated with the test.
display lp/<n> <port>/<m> test
where:
<n> is the instance number of the logical processor linked to the port
being tested
<port> is one of DS1, E1, DS3, E3, JT2, HSSI, Sonet, Sdh, X21, or V35
<m> is the instance number of the port to be tested and can be set to:
0 to 7 for ports on 8-port DS1, V.35, V.11, and 8-port DS1/E1 ATM cards
0 to 3 for ports on 4-port DS1, E1, DS1C, E1C and DS1/E1 AAL1 cards
0 to 2 for ports on DS1, E1, DS3, E3, 3-port DS1/E1 ATM, DS3/E3 ATM,
and OC-3 ATM cards
0 to 3 for ports on V35 or V.11 (X21) ports on CFP1 cards
0 or 1 for ports on JT2 cards
0 for ports on DS1V, E1V, J2MV, DS3, E3, J2MV and HSSI cards
Diagnostic tests 571
Passport Operations and Maintenance Guide 4S3
The results obtained for each test attribute are summarized in Serial port
test result attributes and uses on page 571.
Table 64
Serial port test result attributes and uses
Attribute Use
bitErrorRate Displays the calculated bit error rate on the link.
bitsRx Displays the total number of bits received during the
test period.
bitsTx Displays the total number of bits sent during the test
period.
bytesRx Displays the total number of bytes received during
the test period.
bytesTx Displays the total number of bytes sent during the
test period.
causeOfTermination Displays the reason the port test ended. May be one
of:
neverStarted: the port test has not been started.
testRunning: the port test is currently running.
testTimeExpired: the port test ran for the specified
duration.
stoppedByOperator: a Stop command was issued.
elapseTime Displays the length of time (in minutes) that the port
test has been running.
erroredFrmRx Displays the total number of errored frames
received during the test period.
frmRx Displays the total number of frames received during
the test period.
frmTx Displays the total number of frames sent during the
test period.
timeRemaining Displays the maximum length of time (in minutes)
that the port test will continue to run before stopping.
572 Chapter 17
241-7001-150 4S3
Interpreting serial port test results
The following table explains how to interpret port test results. For each test,
a number of remedial actions are suggested to correct certain problems. In
each case, the test can be rerun either after each remedial action, or after a
number of remedial actions are completed. See Interpreting port test results
on page 572.
Note: There are no results to interpret from the external and payload
loopback.
Table 65
Interpreting port test results
Test type Processor/
port type
How to interpret test results
Card test All types If no frames are returned, or if errored frames are returned:
1) ensure that you have not matched incompatible card types
(see note 1)
2) rerun the card test
3) replace that card
Manual test All types If no frames are received, or if errored frames are received:
1) check the far-end loop
2) check the cabling
3) ensure that both ends of the connection are provisioned
properly (see note 2)
4) ensure that a clock source is available
5) remove devices that may be creating a noisy environment
6) run the card test
7) replace the card
8) rerun the manual test
(Sheet 1 of 2)
Diagnostic tests 573
Passport Operations and Maintenance Guide 4S3
Card testing
The card test allows the operator to stress test new or existing cards under
controlled conditions. The test circulates frames over the Passport bus
between the card under test and a distinct target card, thereby exercising both
cards and consuming bus bandwidth. The test frames follow the same route
Local test V11, HSSI If no frames are received, or if errored frames are received:
1) check the modem and modem connections
2) check the cabling
3) check the far-end loop
4) remove devices that may be creating a noisy environment
5) run the card test
6) run the manual loop test
7) replace the card
8) rerun the local test
9) check far-end DCE OSI state (HSSI only)
Remote test DS1, DS1 ATM,
DS1V, DS3,
DS3 ATM, V11,
DS1 AAL1
If no frames are received, or if errored frames are received:
1) check the CSU, its settings (whether the CSU supports
inband remote loop), and check the CSU connections for DS1,
DS1 ATM, DS1V, DS3, DS3 ATM, and DS1 AAL1
2) check the modem and modem connections for V.11
3) check the cabling
4) check the far-end loop
5) remove devices that may be creating a noisy environment
6) run the card test
7) run the manual loop test
8) replace the card
9) rerun the remote test
Note 1: A card test will fail if the card you are testing and the card you specify as the target card
have different processing capabilities. Therefore, you must target a PM1 card when you test a
PM1 card. You must target a PM2 card when you test a PM2 card. And, you must target an ATM
card when you test an ATM card.
Note 2: For a V.11 in manual test mode: if errored frames are received, check the setting of the
V.11 termination dip switch. Make sure that the setting is correct for the speed and cable length in
the test conguration. See 241-7001-125, Passport Hardware Installation Guide.
Table 65 (continued)
Interpreting port test results
Test type Processor/
port type
How to interpret test results
(Sheet 2 of 2)
574 Chapter 17
241-7001-150 4S3
to their destination as normal frames. If the Passport node is in dual-bus
mode, each card test that is activated consumes bandwidth from both
800 Mbit/s buses in equal amounts; if the module is in single-bus mode, only
the bus in service is used.
The test frames generated by the card under test are grouped into the
following two independent streams:
The loading frame stream circulates a set of loading frames between the
card under test and the target card as rapidly as possible. The intent of this
stream is to verify the operation of the cards and the Passport bus under
a controlled load.
The verication stream transmits a series of verication frames from the
card under test to the target card. As each frame is returned, its contents
are veried and the next verication frame in the series is transmitted.
The intent of this stream is to verify that frames are not being corrupted
during the transfer from card to card.
The card test can be configured to send frames from either or both streams.
The priority, size, and content of the test frames can also be controlled.
Each card in Passport can run the card test independently. The operator can
run the card test on any subset of the cards simultaneously and can specify
different test frame configurations for each test. It is also possible for a card
to act as the target card for more than one card under test, and for a card to act
as a target card while it is itself under test. The flexibility provided by the card
test allows the operator to tailor a set of tests to suit office requirements.
Changing the card test setup
The following procedure explains how to change the attributes that control
the behavior of the card test. These attributes are
targetCard
frmTypes
frmPriorities
frmSize
frmPatternType
Diagnostic tests 575
Passport Operations and Maintenance Guide 4S3
customizedPattern
duration
Procedure 169
Changing the card test setup
1 Set the target card to which frames are to be sent during the test.
set shelf card/<n> test targetCard <targetNum>
where:
<n> is the instance number of the card to be tested
<targetNum> is the instance number of the target card
The card test will not operate when its own card is the target card; thus, if
<targetNum> is equal to <n> the test cannot be started. This is the
default target selection.
Note: A card test will fail if the card you are testing and the card you
specify as the target card have different processing capabilities.
Therefore, you must target a PM1 card when you test a PM1 card. You
must target a PM2 card when you test a PM2 card. And, you must target
an ATM card when you test an ATM card.
2 Optionally, set the types of frames that are sent during the test.
set shelf card/<n> test frmTypes <typeSet>
where:
<n> is the instance number of the card to be tested
<typeSet> alters the set of frame types and is any combination of
<type> (adds the specied frame type to the set)
!<type> (clears the set and adds the specied frame type to the set)
~<type> (removes the specied frame type from the set)
<type> is either loading or verication
Note: The default is to send both loading and verication frames.
3 Optionally, set the priorities of frames that are sent during the test.
set shelf card/<n> test frmPriorities <prioritySet>
where:
<n> is the instance number of the card to be tested
<prioritySet> alters the set of frame priorities and is any combination
of
576 Chapter 17
241-7001-150 4S3
<priority> (adds the specied frame priority to the set)
!<priority> (clears the set and adds the specied frame priority
to the set)
~<priority> (removes the specied frame priority from the set)
<priority> is either lowPriority or highPriority
Note: The default is to send low-priority frames only.
4 Optionally, set the size of frames that are sent during the test.
set shelf card/<n> test frmSize <priority> <size>
where:
<n> is the instance number of the card to be tested
<priority> is low Priority
<size> is a value from 16 to 16000 bytes
Note 1: The default is low-priority frames containing 8192 bytes.
Note 2: Larger test frames are useful in generating high bus utilization
rates; however, they can also cause congestion, resulting in data loss.
5 Optionally, set the pattern used to ll frames that are sent during the test.
set shelf card/<n> test frmPatternType <patternType>
where:
<n> is the instance number of the card to be tested
<patternType> is one of
ccitt32kBitPattern (a pseudo-random sequence of 32 Kbit is
used)
ccitt8MBitPattern, (a pseudo-random sequence of 8 Mbit is
used)
customizedPattern (the pattern dened by the
customizedPattern attribute is used)
Note: The default is a pseudo-random sequence of 32 Kbit.
6 Optionally, set the 32-bit customized pattern used to ll frames that are
sent during the test.
set shelf card/<n> test customizedPattern <pattern>
where:
<n> is the instance number of the card to be tested
<pattern> is a hexadecimal value from 00000000 to FFFFFFFF
Note 1: The default is a pattern of alternating 0 and 1 bits.
Diagnostic tests 577
Passport Operations and Maintenance Guide 4S3
Note 2: The value of this attribute is ignored if frmPatternType does not
have the value customizedPattern.
7 Optionally, set the maximum amount of time that the test is allowed to run.
set shelf card/<n> test duration <limit_value>
where:
<n> is the instance number of the card to be tested
<limit_value> species the maximum length of time, in minutes, that
the card test is allowed to run
Note: The default limit is 60 minutes.
Testing a card
The following procedure explains how to test a card.
Note: Ensure that you have set the target card (see Changing the card
test setup on page 575). The card test will not operate when its own card
is the target card. This is the default target selection.
Procedure 170
Testing a card
1 Optionally, lock the bus that is not to be used in the test. The bus that will
be used in the test must be unlocked and enabled, otherwise the lock
command will fail.
lock shelf bus/<b>
where:
<b> is the instance value of the bus that is not used in the test (either X
or Y)
Note: If the test is run with both buses in service, they are used equally.
CAUTION
Risk of data loss
The activation of a card test consumes processor time
and bus bandwidth on both the card under test and the
target card. Care must be taken when conguring card
tests to ensure that the test frames generated during the
tests do not cause data loss due to congestion.
578 Chapter 17
241-7001-150 4S3
2 Optionally, ensure the card test is properly congured for the desired test.
display shelf card/<n> test setup
where:
<n> is the instance number of the card to be tested
Note 1: The procedure for understanding and changing the conguration
of the test is described in "Changing the card test setup" on page 574.
Note 2: The card test conguration cannot be changed once the test has
been started.
3 Start the card test.
start shelf card/<n> test
where:
<n> is the instance number of the card to be tested
The test stops automatically if the target card becomes non-operational;
otherwise it continues until the specied time limit has been reached.
4 Optionally, you may end the card test prematurely.
stop shelf card/<n> test
where:
<n> is the instance number of the card being tested
5 You may view the results of a test while the test is in progress or after it
has terminated.
display shelf card/<n> test results
where:
<n> is the instance number of the card that was tested
Note: Each attribute describing the results of a test may be displayed
individually; see "Displaying card test results" on page 579.
6 Once the test is complete, release the other bus if it was locked during the
test.
unlock shelf bus/<b>
where:
<b> is the instance value of the bus that was not used in the test (either
X or Y)
Diagnostic tests 579
Passport Operations and Maintenance Guide 4S3
Displaying card test results
The following procedure describes how to display the attributes of the card
test.
Procedure 171
Displaying card test results
1 Display amount of time the test has run.
display shelf card/<n> test <attribute>
where:
<n> is the instance number of the card being tested
<attribute> is one of the following: causeOfTermination, elapsedTime,
loadingFrmData, timeRemaining, vericationFrmData
The results obtained through each attribute are summarized in Card test
result attributes and uses on page 579.
Table 66
Card test result attributes and uses
Attribute Use
causeOfTermination Displays the reason the card test ended. May be
one of
neverStarted: the card test has not been started.
testRunning: the card test is currently running.
testTimeExpired: the card test ran for the
specified duration.
stoppedByOperator: a Stop command was
issued.
targetFailed: the target card became non-
operational.
elapsedTime Displays the length of time (in minutes) that the card
test has been running.
loadingFrmData Displays the number of loading frames that have
been transmitted to the Test component on the
target card and the number of loading frames that
were not successfully returned by the Test
component on the target card.
(Sheet 1 of 2)
580 Chapter 17
241-7001-150 4S3
Interpreting card test results
The following table explains how to interpret card test results. For each test,
a number of remedial actions are suggested to correct certain problems. In
each case, the test can be rerun either after each remedial action, or after a
number of remedial actions are completed. See Interpreting card test results
on page 581.
timeRemaining Displays the maximum length of time (in minutes)
that the card test will continue to run before
stopping.
vericationFrmData Displays the number of verification frames that were
returned by the Test component on the target card
and the number of verification frames that had
incorrect bits when returned.
Table 66 (continued)
Card test result attributes and uses
Attribute Use
(Sheet 2 of 2)
Diagnostic tests 581
Passport Operations and Maintenance Guide 4S3
.
Table 67
Interpreting card test results
Test type Test result Remedial action
Loading
frame stream
The loadingFrmData attribute shows
framesSent>0 and framesLost=0.
This means that loading frames are
circulating properly between the card
under test and the target card.
No remedial action is required.
The loadingFrmData attribute shows
framesSent>0 and framesLost>0.
This means that loading frames are
being lost as they circulate between the
card under test and the target card.
Frames can be lost due to congestion,
mismatched card types, or hardware
problems. Congestion can be reduced
by using smaller test frames or
decreasing the amount of data passing
through the cards. Ensure that the card
you test and the card you specify as the
target card have the same processing
capabilities (see note 1 on page 573). If
the problem persists, try running bus
tests to isolate the defective hardware
item.
The loadingFrmData attribute shows
framesSent=0 and framesLost=0.
This means that the card under test was
unable to contact the target card in order
to begin the test.
No remedial action is required if the
loading frame stream was not enabled
during the test. Otherwise, try each of
the following actions in turn; after each
action, rerun the card test to see if the
problem still exists:
1) Verify that both cards are operational
and that the test setup specifies that
loading frames are to be sent.
2) Reset the target card.
3) Reset the card under test.
(Sheet 1 of 2)
582 Chapter 17
241-7001-150 4S3
Terminator card testing
This procedure explains how to test for a bad terminator card.
Procedure 172
Terminator card testing
1 Log in to the Passport node using an account with debug permission.
Verification
frame stream
The verificationFrmData attribute shows
framesTested>0 and framesBad=0.
This means that verification frames are
circulating properly between the card
under test and the target card.
No remedial action is required.
The verificationFrmData attribute shows
framesTested>0 and framesBad>0.
This means that verification frames are
being corrupted as they circulate
between the card under test and the
target card.
Rerun the card test using a different
target card. If the problem disappears,
replace the original target card; if the
problem persists, replace the card under
test. Rerun the original test.
If the problem persists after both the
card under test and the target card have
been replaced, contact Nortel.
The verificationFrmData attribute shows
framesTested=0 and framesBad=0.
This means that the card under test was
unable to contact the target card in order
to begin the test OR that the verification
frames are being lost due to congestion
or due to hardware problems.
No remedial action is required if the
verification frame stream was not
enabled during the test. Otherwise try
each of the following actions in turn;
after each action, rerun the card test to
see if the problem still exists:
1) Verify that both cards are operational
and that the test setup specifies that
verification frames are to be sent.
2) Rerun the test with the loading frame
stream enabled and use the results of
that test to isolate the cause of the
problem.
Table 67 (continued)
Interpreting card test results
Test type Test result Remedial action
(Sheet 2 of 2)
Diagnostic tests 583
Passport Operations and Maintenance Guide 4S3
2 Issue the following commands:
< os
OS> set verbose
set verbose
OS> sysDebug_g = 15
sysDebug_g = 15
<sysDebug_g set to 15 (0x0000000f) >
OS> sysGetShelfInfo 1
sysGetShelfInfo 1
<Calling sysGetShelfInfo (0x1)>
Opening the TTY port
CTS pin is 1
<Return value = 0 (0x00000000) >
This implies that the terminator card is faulty and should be replaced with
a new terminator card.
Bus testing
The bus test can be used to exercise the buses on a regular basis, to test newly
installed shelf hardware, or as a response to an alarm generated by the system.
The bus test ensures that the bus taps on a specic bus are functioning
properly at minimal utilization rates. This test involves only bus taps on
operational cards (active and standby LPs). If an operational card becomes
nonoperational or fails to respond during the test, it is dropped from the test
and is not allowed to rejoin; however, the results of any tests on its bus tap up
to that point are preserved. The results of the test can help to determine which
portions of the bus system are faulty, if any.
The bus test is composed of several different tests. These tests are completed
in the following order:
bus tap self-test: each bus tap executes its self-test
clock source test: each bus tap ensures that it can receive clock signals
from the active control processor clock source and the alternate clock
source (if present)
broadcast test: each bus tap ensures that it can receive a broadcast frame
over the backplane from every operational card (including itself)
584 Chapter 17
241-7001-150 4S3
ping test: each bus tap ensures that it can receive a low priority non-
broadcast frame over the backplane from every operational card
(including itself)
Once all of the tests have been completed, the ping test is repeated
continuously until the bus test is terminated. This repetition helps to detect
transient bus faults.
The bus to be tested must first be locked to ensure that it is not used for any
other purpose while testing is in progress. Once the bus is locked, the tester
can start and stop the test using operator commands. The test also stops
automatically after a specified time interval, or if it detects a bus tap self-test
failure, an active control processor clock source test failure, or a broadcast
test failure. The results of the test can be viewed at any time while it is running
or after its completion. The result values are reset when the test is next
initiated.
Automatic testing of the alternate bus clock source
Automatic testing of the alternate bus clock source can be enabled or
disabled. By default, automatic testing is enabled. When enabled, tests are
undertaken at the following times:
every 24 hours (from the time of the last test)
after an LP state change
after failure or recovery of the active CP bus clock source
Since tests can cause minor loss of traffic, you may wish to disable the
automatic testing function, in which case no testing of the alternate bus clock
source is undertaken. Regardless of the automatic setting, operators can still
undertake manual bus testing as described in this chapter.
Diagnostic tests 585
Passport Operations and Maintenance Guide 4S3
Manually testing a bus
The following procedure explains how to manually test a bus.
Prerequisites
Be sure that the bus that is not being tested is unlocked and enabled.
Otherwise the lock command will fail on the bus that is being tested.
Procedure 173
Testing a bus
1 Lock the bus for testing purposes. The other bus must be unlocked and
enabled, otherwise the lock command will fail.
lock shelf bus/<b>
where:
<b> is the instance value of the bus to be tested (either X or Y)
2 Optionally, set the maximum amount of time that you will allow the test to
run.
set shelf bus/<b> test duration <limit_value>
where:
<b> is the instance value of the bus to be tested (either X or Y)
<limit_value> species the maximum length of time, in minutes, that
the bus test is allowed to run
Note: The time limit cannot be changed once the test has started. The
default time limit is 1 minute.
3 Start the bus test.
start shelf bus/<b> test
CAUTION
Risk of data loss
Testing buses may result in loss of data. Bus system
capacity is reduced by half when a bus is locked,
therefore data loss due to congestion may increase.
Also, if problems occur on the second bus, card crashes
may occur. To reduce the risk of data loss, do not lock a
bus during peak periods of trafc.
586 Chapter 17
241-7001-150 4S3
where:
<b> is the instance value of the bus to be tested (either X or Y)
Note: The test stops automatically if it detects a failure that prevents
subsequent portions of the bus test from executing; otherwise, it
continues until the specied time limit has been reached.
4 Optionally, you may end the bus test prematurely.
stop shelf bus/<b> test
where:
<b> is the instance value of the bus being tested (either X or Y)
5 You may view the results of a test while the bus test is still in progress or
after it has terminated.
display shelf bus/<b> test results
where:
<b> is the instance value of the bus that was tested (either X or Y)
Note: Each attribute describing the results of a test may be displayed
individually; see "Displaying bus test results" on page 587.
6 Once the test is complete, release the bus.
unlock shelf bus/<b>
where:
<b> is the instance value of the bus that was tested (either X or Y)
Setting automatic bus testing
Use the following procedure to enable or disable automatic testing of the
alternate clock source.
Procedure 174
Setting automatic testing of the alternate clock source
1 Start provisioning mode.
2 To enable automatic testing, enter
set shelf test automaticBusClockTest enable
or to disable automatic testing, enter
set shelf test automaticBusClockTest disable
3 End provisioning mode.
Diagnostic tests 587
Passport Operations and Maintenance Guide 4S3
Displaying bus test results
The following procedure explains how to display the attributes describing the
results of the bus test.
Procedure 175
Displaying bus test results
1 Display amount of time the test has run.
display shelf bus/<b> test attribute
where:
<b> is the instance value of the bus being tested (either X or Y)
<attribute> is one of the following: broadcastTestResults,
causeOfTermination, clockSource, elapsedTime, pingTestFailures,
pingTests, selfTestResults, testResults, testsDone, timeRemaining
The results obtained through each attribute are summarized in Bus test
result attributes and uses on page 588.
588 Chapter 17
241-7001-150 4S3
Table 68
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 will have one of the
following values assigned to it:
+: a broadcast message was successfully sent from the transmitting bus
tap to the receiving bus tap.
X: a broadcast message was not successfully sent from the transmitting
bus tap to the receiving bus tap.
. : the associated pair of bus taps was not tested.
Note: The bus test terminates automatically if a failure is detected in the
broadcast test.
causeOfTermination Displays the reason the bus test ended. May be one of
neverStarted: the bus test has not been started
testRunning: the bus test is currently running
testTimeExpired: the bus test ran for the specified duration
stoppedByOperator: a Stop command was issued
selfTestFailure: a failure was detected during the bus tap self-test
clockSourceFailure: a failure was detected during the test of the
active CP clock source
broadcastFailure: a failure was detected during the broadcast test
clockSourceTest
Results
Displays the results of the clock source test, indexed by the clock source
and the slot numbers of the cards containing the bus taps involved. Each
entry will have one of the following values assigned to it:
+: 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.
. : the bus tap was not tested against the clock source.
Note: The bus tap self-test terminates automatically if a failure is
detected involving the active control processor (CP) clock source.
elapsedTime Displays the length of time (in minutes) that the bus test has been running
(Sheet 1 of 2)
Diagnostic tests 589
Passport Operations and Maintenance Guide 4S3
pingTestFailures Displays the number of ping test failures detected, indexed by the slot
numbers of the cards containing the bus taps involved. Each failure
represents a single low-priority frame that was not successfully
transmitted from the transmitting bus tap to the receiving bus tap.
Note: The bus test does not terminate automatically if a failure is
detected 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.
selfTestResults Displays the results of the bus tap self-test, indexed by the slot numbers
of the cards containing the bus taps involved. Each entry will have one of
the following values assigned to it:
+: the bus tap passed its self-test.
X: the bus tap failed its self-test.
. : the bus tap was not tested.
Note: The bus test terminates automatically if a failure is detected in the
bus tap self-test.
testsDone Displays the tests that have been completed during the bus test. May
display zero or one of the following:
selfTest: the bus tap self-test has been completed
clockSourceTest: the clock source test has been completed
broadcastTest: the broadcast test has been completed
pingTest: at least one ping test has been completed
timeRemaining Displays the maximum length of time (in minutes) that the bus test will
continue to run before stopping
Table 68 (continued)
Bus test result attributes and uses
Attribute Use
(Sheet 2 of 2)
590 Chapter 17
241-7001-150 4S3
Interpreting bus test results
The following table explains how to interpret bus test results. For each test, a
number of remedial actions are suggested to correct certain problems. In each
case, the test can be rerun either after each remedial action, or after a number
of remedial actions are completed. See Interpreting bus test results on
page 590.
Table 69
Interpreting bus test results
Test type Test result Remedial action
Bus tap self-
test\
An entry in the selfTestResults attribute
shows a +. This means that the bus tap
on the corresponding card passed the
self-test.
No remedial action is required.
An entry in the selfTestResults attribute
shows an X. This means that the bus tap
on the corresponding card failed the
self-test.
The bus test is terminated before going
on to the next test.
Replace the card. Rerun the test to
verify that the problem has been
corrected.
An entry in the selfTestResults attribute
shows a .. This means that the bus tap
on the corresponding card was not
tested.
No remedial action is required if the card
is not an active or standby LP;
otherwise, rerun the bus test.
(Sheet 1 of 4)
Diagnostic tests 591
Passport Operations and Maintenance Guide 4S3
Clock source
test
An entry in the clockSourceTestResults
attribute shows a +. This means that the
bus tap on the corresponding card was
able to receive clock signals from the
specified clock source.
No remedial action is required.
An entry in the clockSourceTestResults
attribute shows an X. This means that
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.
Most likely point of failure if a given clock
source fails for only one card:
1) card that failed test
2) card containing clock source
3) backplane
Most likely point of failure if a given clock
source fails for multiple cards:
1) card containing clock source
2) cards that failed test
3) backplane
Note: The alternate clock source is
provided by the card at the opposite end
of the shelf from the active control
processor. If the slot is empty, no
alternate clock source is available.
An entry in the clockSourceTestResults
attribute shows a .. This means that the
bus tap on the corresponding card was
not tested against the specified clock
source.
No remedial action is required if the card
is not an active or standby LP;
otherwise, rerun the bus test.
Table 69 (continued)
Interpreting bus test results
Test type Test result Remedial action
(Sheet 2 of 4)
592 Chapter 17
241-7001-150 4S3
Broadcast
test
An entry in the broadcastTestResults
attribute shows a +. This means that a
broadcast frame was successfully sent
from the transmitting bus tap to the
receiving bus tap.
No remedial action is required.
An entry in the broadcastTestResults
attribute shows an X. This means that a
broadcast frame was not successfully
sent from the transmitting bus tap to the
receiving bus tap.
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.
Most likely point of failure:
1) cards corresponding to rows or
columns containing X but not +, in order
of decreasing number of Xs
2) cards corresponding to rows or
columns containing X and +, in order of
decreasing number of Xs
3) backplane
An entry in the broadcastTestResults
attribute shows a .. This means that the
corresponding pair of bus taps was not
tested.
No remedial action is required if either of
the cards containing the bus taps is not
an active or standby LP; otherwise,
rerun the bus test.
Table 69 (continued)
Interpreting bus test results
Test type Test result Remedial action
(Sheet 3 of 4)
Diagnostic tests 593
Passport Operations and Maintenance Guide 4S3
Disk testing
Disk testing is used to verify disk integrity and to carry or maintenance tasks.
Note: You can run disk tests on a disabled active control processor.
However, you cannot run disk tests on a disabled standby control
processor.
Disk test types
There are two classes of tests for hard disks:
destructive tests, which alter the contents of the disk (the disk must be
reformatted after the test)
Ping test An entry in the pingTestFailures attribute
is 0 and the corresponding entry in the
pingTests attribute is equal to the largest
entry in that table. This means that a
low-priority frame was successfully sent
from the transmitting bus tap to the
receiving bus tap during each ping test.
No remedial action is required.
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. This
means that a low-priority frame was not
successfully sent from the transmitting
bus tap 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.
Most likely point of failure:
1) cards corresponding to rows or
columns of ping test failures adding to a
value greater than 0, in order of
decreasing sums
2) backplane
An entry in the pingTests attribute is
smaller than the largest entry. This
means that the corresponding pair of
bus taps was not tested by some of the
ping tests.
No remedial action is required if either of
the cards containing the bus taps is not
an active or standby LP; otherwise,
rerun the bus test.
Table 69 (continued)
Interpreting bus test results
Test type Test result Remedial action
(Sheet 4 of 4)
594 Chapter 17
241-7001-150 4S3
non-destructive tests, which do not alter the data on the disk and can be
run at any time
Non-destructive tests
There are three types of non-destructive tests, as follows:
disk read test: reads every sector on the disk once. The read test marks
any bad sectors that it nds. The le system stops using those bad sectors.
Approximate test duration is 4 minutes. If the test reveals an error,
proceed with the lesystem check test (see below).
aky bit detection test: Reads every sector on the disk twice and
compares the two read results searching for intermittent errors.
Approximate test duration is 8 minutes. (This may vary depending on the
disk contents.) If the test reveals an error, proceed with the lesystem
check test (see below).
lesystem check test: This test which only takes a few seconds, does a
le system sanity check and frees lost clusters. The test tries to correct
any bad sectors. When a bad sector is found, the test attempts to recreate
the new sector using information from its shadowed sector.
For example, a read test recognizes sector 220 as a bad sector and marks
it as such. Since sector 220 is shadowed by sector 221, the test copies
information from sector 221 into a new sector such as 222 for example.
If sector 220 is in the middle of a le however, the whole le is removed.
Note: You must run the lesystem check test if either the disk read test
or aky bit detection test indicate errors.
Test a disk only when a fault in the disk hardware is suspected. Note that you
cannot do an filesystem check test to the disk on the active control processor.
The attributes of the Test component can be modied only when the test is
idle.
Destructive tests
There is one type of destructive test called a surface analysis test. This test is
used only as a last resort (that is, if the previous tests fail to reveal the error.)
The surface analysis test writes a pattern to the disk and reads back the pattern
to determine the condition of the magnetic surface of the disk. Approximate
test duration is 16 minutes.
Diagnostic tests 595
Passport Operations and Maintenance Guide 4S3
Testing a disk
The following procedure explains how to test a disk.
Note: In a dual-disk system, only the standby disk should be tested. If
you want to test the active disk, issue the command switchover LP/0.
Procedure 176
Testing a disk
1 Set the test type.
set fs disk/<n> test type <type>
where:
<n> is the number of the disk you want to test. The disk number
corresponds to the slot number of the CP that holds the disk.
<type> is one of diskRead, akyBitDetection, lesystemCheck, or
surfaceAnalysis
Note: The surfaceAnalysis test should never be initiated on a CFP1 with
a single disk system.
2 Lock the FileSystem component.
lock fs
Note: This step applies only to a single-disk system.
3 Lock the disk.
lock fs disk/<n>
where:
<n> is the number of the disk being tested
4 Start the test.
start fs disk/<n> test
where:
<n> is the number of the disk being tested
CAUTION
Risk of data loss
Never initiate a surface analysis test on a single-disk
system. The test will erase all data on the disk and
reformat the disk.
596 Chapter 17
241-7001-150 4S3
5 Optionally, you may stop the test before it is complete.
stop fs disk/<n> test
where:
<n> is the number of the disk being tested
Note: You may stop the test, but not the cycle that is currently running
(that is, the current cycle is allowed to run until completion).
6 Unlock the disk.
unlock fs disk/<n>
where:
<n> is the number of the disk that was tested
7 Unlock the FileSystem component.
unlock fs
If you are doing a surface analysis test, proceed with step 8. If you are
doing any other disk tests, proceed to step 9.
8 Reset the control processor. (Note that this step is only necessary if you
are doing surface analysis.)
reset shelf card/<n>
where:
<n> is the number of the control processor that holds the disk you tested
The standby control processor (CP) will attempt 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
Displaying disk test results
The following procedure describes how to display the attributes of the disk
test. Results are complete only after the test has ended.
Procedure 177
Displaying disk test results
1 Display the cause of test termination.
display fs disk/<n> test <attribute>
where:
<n> is the number of the disk you tested. The disk number corresponds
Diagnostic tests 597
Passport Operations and Maintenance Guide 4S3
to the slot number of the CP that holds the disk.
<attribute> is one of the following attributes: results,
causeOfTermination, natureOfError, severity, elapsedTime,
testExecutionCount
The results obtained through each attribute are summarized in Disk test
result attributes and uses on page 597.
Table 70
Disk test result attributes and uses
Attribute Use
causeOfTermination Displays the reason the disk test ended. May be one of
testCountReached: the test ran the number of times specified in the
attribute testCount and ended normally
error: the test was terminated by an error that is recorded in the
natureOfError attribute
neverStarted: the disk test was not started
stoppedByOperator: a Stop command was issued
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 Displays the elapsed time (in minutes) since the test was started.
natureOfError Describes the type of the error found by a test. The type of error may be
one of
logical: can be fixed by a filesystem check test followed by a
synchronization
media: indicates that a fault in the disk hardware is suspected
failedToComplete: indicates that the test was terminated
results Displays all results associated with the attributes in this table.
(Sheet 1 of 2)
598 Chapter 17
241-7001-150 4S3
severity Displays the severity of the error found by the test. May be one of
no data was lost
data was lost
hardware problem
testExecutionCount Displays the number of times the test had actually run.
Table 70 (continued)
Disk test result attributes and uses
Attribute Use
(Sheet 2 of 2)
599
Passport Operations and Maintenance Guide 4S3
Chapter 18
Shelf management
This chapter provides the necessary procedures and operator commands to
maintain the Magellan Passport node.
After reading this chapter, you will be able to
clean up unused software les
reboot a processor card
specify what software to load on a processor card
modify logical processor types
synchronize all disks in the le system
enable and disable hot standby control processor (CP) redundancy on
two-CP shelf congurations
format a disk
recover from control processor (CP) failures
maintain a node that has different size disks
synchronize network time
Shelf management procedures which are covered elsewhere in the guide are
not repeated in this chapter; instead, there is a reference to where the
procedure can be found.
Before reading this chapter, you should have a general understanding of
Magellan Passport gained through reading 241-7001-110, Passport General
Description.
600 Chapter 18
241-7001-150 4S3
Except where noted, descriptions and procedures are provided for operators
working with Passport through a VT-100 terminal or a terminal emulator. If
you are using Nortels proprietary Magellan Network Management System
(NMS) see 241-6001-023, NMS Architect for Passport User Guide.
Related documents
See the following documents for additional information maintenance and
shelf management:
241-7001-110, Passport General Description
241-7001-125, Passport Hardware Installation Guide
241-7501-210, Passport Components
Provisioning procedures
End provisioning mode in the procedures that follow involves a number of
detailed steps. See Provisioning system description on page 85 for details
on how to end provisioning mode.
Quick access to procedures
To nd procedures quickly, see the following list:
"Cleaning up unused les associated with any application version" on
page 603
"Cleaning up unused les associated with a specic application version"
on page 604
"Resetting a logical processor" on page 605
"Resetting a shelf" on page 605
"Resetting a card" on page 605
"Reloading a control processor" on page 606
"Restarting a logical processor" on page 606
"Restarting a card" on page 606
"Changing the logical processors logical processor type" on page 608
"Adding more software features to a logical processor type" on page 609
Shelf management 601
Passport Operations and Maintenance Guide 4S3
"Disabling hot standby CP redundancy" on page 626
"Enabling hot standby CP redundancy" on page 626
"Synchronizing the active and standby disks" on page 631
"Changing a disks volume name" on page 631
"Formatting a disk" on page 632
"Replacing a control processor in a single-CP system (donor node is
available and NMS backup is available)" on page 636
"Replacing a control processor in a single-CP system (donor node is
available and NMS backup is not available)" on page 637
"Replacing a control processor in a single-CP system (donor node is not
available and NMS backup is available)" on page 638
"Replacing a control processor in a single-CP system (donor node is not
available and NMS backup is not available)" on page 639
"Replacing a control processor in a two-CP system" on page 640
"Adding a second control processor" on page 641
"Setting network time" on page 643
"Setting the time offset" on page 645
"Resetting the network time and the time offset after a power off" on
page 645
Software management
In Magellan Passport, there are two kinds of software upgrades: software
version upgrades and feature list upgrades, as follows:
Software version upgrades affect which version of software is running on
the node. These upgrades require the application version list to be
updated.
Feature list upgrades affect which software gets loaded on individual
processors. These upgrades require the feature list of one or more logical
processor types to be updated.
602 Chapter 18
241-7001-150 4S3
In some cases, a software version upgrade may require both application
version list and feature list upgrades. For example, when a software version
upgrade introduces a new feature, the new feature is added to the feature list.
In this case, a feature list upgrade is also required.
For procedures on downloading and upgrading software, see Software
installation on page 165. Information on cleaning up unused software files
is found in Cleaning up unused files associated with any application
version on page 603 and Cleaning up unused files associated with a specific
application version on page 604.
Removing unused software les
You can remove software files that are no longer required by the current view,
edit view, or any other provisioning file residing in the provisioning
directory. Passport provides two commands, tidy and remove, to allow you
clean up unused les.
Both the tidy and remove commands are used in operational mode only (that
is, you are not performing any provisioning activities).
The tidy command
The tidy command removes all unreferenced ApplicationVersion (AV)
operational subcomponents along with all their associated software files from
the disk. This means that an AV can be removed only if the AV is not
referenced by the current views AVL or by the AVL of any other
semantically checked view saved in a file on disk.
The syntax for the tidy command is
tidy sw
You can use the -query option to nd out which AVs will be deleted if you
issue the tidy sw command. For example:
tidy -q sw
displays the names of each AV that will be deleted
Note 1: The tidy command will fail if a check prov, start download, or
remove command is in progress.
Shelf management 603
Passport Operations and Maintenance Guide 4S3
If the AV is referenced by the current views AVL or by the AVL of any other
semantically checked view, you can issue the tidy prov command to remove
provisioning files.
Using the tidy prov command causes the system to remove old provisioning
views from the disk. For details on the tidy prov command, see "tidy prov" on
page 130.
Procedure 178
Cleaning up unused les associated with any application version
1 Optionally, list the components that currently exist under the Software
(SW) component.
list sw
A list of all software subcomponents appears.
2 Issue the tidy SW command.
tidy sw
The system responds with a list of all AVs that have been removed.
3 Issue the list command again, for a list of the remaining AVs.
list sw
A list of all remaining software subcomponents appears.
Note: Be careful not to confuse the tidy sw command with the tidy prov
command. The tidy prov command removes only provisioning les!
CAUTION
Loss of important les may result from tidy
command
Use the tidy command with extreme caution as it deletes
not only old versions of software files, but also all
software files not linked to a logical processor type
(LPT).
604 Chapter 18
241-7001-150 4S3
The remove command
The remove command removes an AV component and the associated software
files from the disk (as long as they are unreferenced). This means that an AV
can be removed only if the AV is not referenced by the current views AVL
or by the AVL of any other semantically checked view.
Note 1: The remove command fails if a start download, tidy, or check
prov command is in progress.
Note 2: There is mutual exclusivity among the start download, tidy,
remove, and check prov commands.
The syntax for the remove command is
remove sw av/<application version>
Cleaning up unused les associated with a specic application version on
page 604 explains how to eliminate unused les using the remove command.
Procedure 179
Cleaning up unused les associated with a specic application version
1 Issue the remove sw command.
remove sw av/<application version>
where:
<application version> is the application version name
Note: av is an abbreviation for the ApplicationVersion component.
The system responds with a message conrming that the AV has been
removed.
Note: The command fails if the ApplicationVersion component is
referenced by an application version list in any view (that is, the editing
view or any provisioning le saved on disk). When you issue the remove
command the system displays the names of any provisioning les or
views that reference this AV (that is, those les that are preventing the
removal of the AV). To remove the AV, you must remove the appropriate
les and then issue the command again.
Shelf management 605
Passport Operations and Maintenance Guide 4S3
Resetting, reloading, and restarting a processor card
The shelf management system provides operator commands to reset, restart,
or reload processors. Any one of these commands causes the processor to
reboot. In some cases, a reset, reload, or restart command may induce a
switchover (that is, the standby processor card becomes the active processor
card.) See "CP redundancy" on page 611 for more details.
The reset command
The reset command resets all Passport hardware and reloads the software. It
can be issued against a processor card, a logical processor (LP), or the shelf.
Areset command issued against an LP applies to the processor card on which
the logical processor is mapped. A reset command issued against the shelf
applies to all processor cards on the shelf.
Procedure 180
Resetting a logical processor
1 Issue the reset command.
reset lp/<n>
where:
<n> is the instance of the logical processor
Note: lp is an abbreviation for the LogicalProcessor component.
Procedure 181
Resetting a shelf
1 Issue the reset command.
reset shelf
Procedure 182
Resetting a card
1 Issue the reset command.
reset shelf Card/<n>
where:
<n> is the number of the card
606 Chapter 18
241-7001-150 4S3
The reloadcp command
The reloadcp command forces a control processor to reload using an arbitrary
provisioning le. All function processors are also reloaded.
Procedure 183
Reloading a control processor
1 Issue the reloadCP command.
reloadcp -f(<filename>) -force lp/0
where:
<filename> is the name of the provisioning le used to reload the
control processor
Note: The -force option has an effect only when a spare control
processor is not congured. It indicates that it is okay to process the
reloadCP command even if no standby control processor is available.
The restart command
The restart command resets Passport hardware (except for memory) and
reinitializes the software without reloading it. It can be issued against either
a logical processor or a card.
Note: In order for the restart command to work on a control processor,
the control processor must be running a committed software load. If the
software load is not committed, the control processor is reset instead of
restarted.
Procedure 184
Restarting a logical processor
1 Issue the restart command.
restart lp/n
where:
<n> is the instance of the logical processor
Note: lp is an abbreviation for the LogicalProcessor component.
Procedure 185
Restarting a card
1 Issue the restart command.
restart shelf card/n
Shelf management 607
Passport Operations and Maintenance Guide 4S3
where:
<n> is the number of the card
The switchover command
The switchover command switches control between the main and spare cards
of a given LP.
Procedure 186
Switching from the active LP to the standby
1 Issue the switchover command.
switchover lp/<n>
where:
<n> is the number that identies the LP
Note: See CP redundancy on page 611 for information on the
restrictions and limitations regarding manual CP switchovers.
Locking and unlocking processor cards
The lock and unlock commands allow you to lock and unlock processor cards.
For details on locking and unlocking processor cards and other Passport
components, see Component control on page 407.
Changing a processor cards software load
There are several different ways to change the software load associated with
a processor card:
create a new LPT with the new software and map the existing processor
cards LP to this new LPT
locate an LPT within the Passport node that contains the software you
require and map the existing processor cards LP to this LPT
Note: This option should be chosen if more than one logical processor
references the logical processor type and the network operator does not
want to change the software loads on the other logical processors.
Otherwise, the rst option should be used (unless a suitable logical
processor type already exists).
change the software associated with an LPT to include the new software
you require
608 Chapter 18
241-7001-150 4S3
Creating, modifying, or deleting a logical processor
The following guidelines apply when modifying, deleting, or creating a new
LP:
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 Passport switch, the main must be Card/0 and
the spare must be Card/15.
On a 3-slot Passport switch, you cannot spare the control processor.
Therefore, Lp/0 can reference only Card/0 as its main card.
No two LPs can reference the same processor card.
The card components referenced by the LPs main card and spare card
attributes should have identical card types.
Changing a logical processors logical processor type
The following procedure explains how to change the logical processor type
that a logical processor references. The LPT determines which software an
LP will run.
Procedure 187
Changing the logical processors logical processor type
1 Enter provisioning mode.
start prov
2 Provision a new LogicalProcessorType (LPT) component. Do this only if
a suitable logical processor type does not already exist. To do this, add an
LPT component and set its featureList attribute.
add sw lpt/<lpt name>
set sw lpt/<lpt name> fl <feature list>
where:
<lpt name> can contain up to 25 alphanumeric characters (this name is
customer-dened)
<feature list> is the name of one or more software features that
need to be loaded
3 Change the logical processor type that is referenced by the logical
processor.
Shelf management 609
Passport Operations and Maintenance Guide 4S3
set lp/<n> lpt sw lpt/<lptname>
where:
<n> is the number of the logical processor
<lpt name> is the name of the logical processor type
4 End provisioning mode.
Adding more software features to an LPT
Follow the procedure in this section to provision a processor with a new
software feature by adding more application features to an LPTs feature list.
Note: For the purposes of this example, assume that you are adding the
Frame Relay UNI feature to LP/8.
Procedure 188
Adding more software features to a logical processor type
1 Enter provisioning mode.
start prov
2 Determine which LPT is currently being used by LP/8.
display lp/8 lpt
LP/8
logicalProcessorType = Sw Lpt/lptname
This response shows that LPT/lptname is currently being used by LP/8.
3 Determine which features are already provisioned on the LPT.
display sw lpt/lptname featureList
The feature list for the LPT is displayed:
Sw Lpt/lptname
featureList = frameRelayNni
ok 1994-10-28 14:09:37.32
Note: This shows that the LPT has the Frame Relay NNI feature.
4 Add more application features.
Note: For the purposes of this example, the Frame Relay UNI feature is
added to the list.
set sw lpt/lptname featureList frameRelayUni
5 Verify that the features were added successfully.
610 Chapter 18
241-7001-150 4S3
display sw lpt/lptname featureList
Sw Lpt/lptname
featureList = frameRelayNni, frameRelayUni
6 Verify that the provisioning changes are acceptable.
check prov
7 Load the new software.
activate prov
8 Conrm provisioning.
confirm prov
9 After running any tests on the new software, you can make it the
committed provisioning data.
commit -file(<filename>) prov
where:
<filename> is the name you want to give to the le containing the new
software
Removing a software feature from an LPT
Follow the procedure in this section to remove software features from an
LPTs feature list.
Note 1: When you delete a feature from an LPT that is referenced by an
LP, the FP for that LP will reboot. If this feature is the last one of its type
to be removed from the Passport, the LP for the CP may also reboot. For
these reasons, you may want to wait to delete features from LPTs that are
referenced by LPs until an appropriate time for a reboot, such as a
maintenance period.
Note 2: For the purposes of this example, assume that you are removing
the Frame Relay NNI feature from lpt/lptname.
Procedure 189
Removing a software feature from a logical processor type
1 Enter provisioning mode.
start prov
2 Display the features on the node.
display sw lpt/lptname featureList
Shelf management 611
Passport Operations and Maintenance Guide 4S3
3 Delete the feature.
set sw lpt/lptname featureList ~frameRelayNni
4 Verify that the feature was successfully removed.
display sw lpt/lptname featureList
Sw Lpt/lptname
featureList = frameRelayUni
5 Verify that the provisioning changes are acceptable.
check prov
The system will respond with a message specifying which processors will
reboot when the new provisioning data is activated.
6 Unload the software.
activate prov
7 Conrm provisioning.
confirm prov
8 After running any tests on the new software, you can make it the
committed provisioning data.
commit -file(<filename>) prov
where:
<filename> is the name you want to give the le containing the new
software
CP redundancy
Passports that are equipped with two CP cards operate with one CP in the
active state and the other in the standby state.
If the active CP fails, the standby automatically takes over. This activity is
referred to as a system-initiated CP switchover. Failures that cause a system-
initiated switchover include:
faults detected by the active CPs processor or memory management
hardware.
Faults may be failures in either hardware or software, such as memory
parity error, write protection violation, memory access exception
(address out of range), and divide by 0.
612 Chapter 18
241-7001-150 4S3
software-detected unrecoverable errors
local disk failure occurred
faults detected by the standby CP (for example, the active CPs bus
interface fails on both buses)
When a switchover occurs due to a CP failure and the failed CP subsequently
recovers, an automatic switch-back to the originally active CP does not occur.
If required, the operator can initiate a manual switchover.
Note: Not all failures on the CP cause a system-initiated switchover to
occur. For example, if the stratum 3 clock on the active CP fails, an alarm
is generated but a switchover does not occur.
A manual CP switchover is operator-initiated through commands entered at
the console. A manual switchover is not permitted if any of the following is
true:
there is either no standby CP or the standby CP is not operational
the disks on the two CPs are not synchronized
a software upgrade is in progress
the standby CP is in the process of loading the committed view and
operator initiated the switchover with command switchover lp/0.
There are two CP standby modes: warm (no state synchronization with FPs)
and hot (full state synchronization with supporting FPs). Hot standby CP
redundancy is the default mode. Depending on FP and service configurations,
some or all FPs on a shelf may behave in one mode or the other when a
switchover occurs.
Note 1: OSI standards use different terminology when referring to
standby modes. The standards consider both CP standby modes to be
cold standby.
Note 2: Before setting up sparing between CPs, check the product
equipment codes (PECs) of the active and spare CPs. To make full use of
the increased memory and disk space newer control processors contain,
all eight digits of the PECs must match.
Shelf management 613
Passport Operations and Maintenance Guide 4S3
The effect of manual commands on hot and warm redundancy are
summarized in Command impacts in different standby modes on page 613.
Warm standby
Warm standby ensures that the standby CP is available. However, in this
mode the CP states are not synchronized with the FP states.
Table 71
Command impacts in different standby modes
Result
Command Warm standby Hot standby
reset shelf all CP and FP cards reset and
reload, just as at power-up
same as warm standby case
reset shelf card/<active_cp>
or
reset lp/0
active CP resets and reloads;
standby CP takes over
(note 1); all active FPs restart
(note 2)
active CP resets and reloads;
standby CP takes over
(note 1); FPs stay up (note 3
and 5)
restart shelf card/<active_cp>
or
restart lp/0
active CP restarts; standby CP
takes over (note 1); all active
FPs restart (note 2)
active CP restarts; standby CP
takes over (note 1); FPs stay
up (note 3 and 5)
switchover lp/0 (note 4) active CP restarts; standby CP
takes over; all active FPs
restart (note 2)
active CP restarts; standby CP
takes over; FPs stay up
(note 3)
Note 1: Standby takes over if it is operational and the two CP disks were in sync prior to the reset
command. If the disks were not in sync, the standby waits for up to two minutes before taking over;
if the originally active CP recovers within that time, it remains the active CP.
Note 2: FPs which are running as standby are not restarted.
Note 3: FPs stay up subject to the restrictions noted in Conditions and limitations on page 620.
Note 4: Command will be blocked while the committed provisioning view is being loaded on the
standby CP.
Note 5: FPs will go down if the command is issued within 10 minutes from the last hot standby
switchover.
614 Chapter 18
241-7001-150 4S3
To achieve shelf synchronization when a switchover occurs, the shelf and the
processors must restart. This action in turn removes all processors from
service until the restart is complete: connections originating and terminating
on the shelf are dropped, and the network re-routes connections around the
node. When the restart is complete, connections are re-established and
processing resumes. This restart occurs automatically, regardless of whether
the switchover is initiated by the system or the operator.
Hot standby
Hot standby CP redundancy ensures that state information is synchronized
between the standby CP and all FPs that support hot standby. When a
switchover occurs, those FPs associated with services that support hot
standby continue call processing uninterrupted. FPs associated with services
that do not support hot standby undergo a restart as in warm standby mode.
The operator can disable or re-enable hot standby as required. When enabled,
connection and data transfer continues in these ways:
Frame relay, ATM, voice, and transparent data connections remain in
service and data continues to ow.
Frame and cell trunks remain in service and data continues to ow.
Accounting data on FPs is preserved.
These behaviors are subject to the restrictions and limitations described in
Conditions and limitations on page 620.
Benets of hot standby CP redundancy
Specic benets of hot standby are described in the following points:
from an end-user perspective, connection long-term reliability is
improved
fewer disruptions to the network
less impact on existing connections
where services support hot standby, call setup outage time is reduced
most accounting data is preserved
manual CP switchover no longer causes a shelf restart
Shelf management 615
Passport Operations and Maintenance Guide 4S3
regularly scheduled CP switchovers may be done with minimal impact
to services
impact of switching between the stratum clocks on the two CPs is
minimized
There are no backwards compatibility issues. A Passport running a software
level that support hot standby CP redundancy (whether the feature is enabled
or disabled) may be connected to Passports running software in which hot
standby is not supported. The operational behavior in a mixed redundancy
network configuration is described in Deployment of hot standby CP
redundancy on page 624.
Hot standby behavior characteristics
Hot standby affects the operation of the node in the following areas:
access services
trunks
DPN gateways
network management and component states
alarms, logs, accounting, and statistics
card tests
user interface recovery
Characteristics in each of these areas is described in the following
subsections.
CAUTION
Risk of damage to the CP
Do not remove the active CP from the shelf as a way of
simulating active CP failure.
To test the behavior of hot standby CP redundancy
under CP failure conditions, the recommended
procedure is to use the restart lp/0 command.
616 Chapter 18
241-7001-150 4S3
Access services
When a CP switchover occurs, existing connections remain in service and
data continues to ow for the following services:
frame relay
ATM bearer services
voice
transparent data
For these services, new calls can be originated by or can terminate on the node
after a delay of approximately 30 s from the time the switchover is initiated.
This delay represents the time needed for the standby CP to become active
and for the call servers to re-initialize on the new CP and be ready to process
new call requests. No service is given priority over any other in the recovery
process. OA&M for these services operates as described in Network
management on page 617 and Alarms, logs, accounting, and statistics on
page 618.
Connections with an end point on the active CP are not preserved when the
CP switchover occurs. Call setup routines in progress are lost; in the case of
PVCs, call setup is retried automatically while for SVCs the originator must
retry the call setup.
When a CP switchover occurs, connections are dropped for the following
services:
LAN services (IP, IPX, Bridging)
LAN media (Ethernet, Token Ring, FDDI)
WAN services (Frame Relay DTE, X25 DTE, PPP)
APPN/SNA
That is, these services do not support hot standby CP redundancy. An FP
providing any of these services is restarted when a CP switchover occurs: any
connections on that FP are dropped and data flow is interrupted until the FP
recovers.
Shelf management 617
Passport Operations and Maintenance Guide 4S3
An FP which contains a mixture of services restarts on CP switchover if one
or more services do not support hot standby CP redundancy. For details on
supportability for specific services, see Service support for hot standby CP
redundancy on page 623.
Trunks
When a CP switchover occurs, frame/cell trunks and ATM trunks remain in
service and data continues to flow on existing connections. Voice and
transparent data call setup requests transiting the node are unaffected by CP
switchover. OA&M for these services operates as described in Network
management on page 617 and Alarms, logs, accounting, and statistics on
page 618.
DPN gateways
DPN gateways re-stage when a CP switchover occurs. This means that the
external network routes around this node. Although the gateway re-stages, the
presence of a DPN gateway on an FP does not cause that FP to restart.
Network management
When a CP switchover occurs, network management sessions are terminated
and connections to the active CP are dropped. Any context information such
as an edit view is lost. The mechanism for re-establishing the connection
depends on the protocol used for network management.
The behavior of NMS sessions under switchover conditions are described in
the following points:
FMIP connections that terminate on the active CP are dropped and must
be re-established by the NMS (for surveillance, this happens
automatically without user intervention).
Telnet connections that terminate on the active CP are dropped and must
be manually re-established by the operator.
Local console sessions running on the active CP must be manually re-
established (that is, the operator must log in again).
SNMP agents are restarted and a cold start trap is generated by each
SNMP agent when it restarts. Any SNMP request that is processing when
the switchover occurs is lost; SNMP requests that are issued during the
30-second recovery period may time out.
618 Chapter 18
241-7001-150 4S3
In addition, some state changes occur as a result of a switchover:
Most components of the shelf management system (for example, Shelf,
Card, Lp) and any CP-resident components that were locked by an
operator command are unlocked. The Bus component remains locked if
locked prior to the switchover.
Any operational attributes of CP-resident components that have been set
by the operator revert to default values.
The sysUpTime attribute is reset to 0 following a switchover.
The effect of CP switchover on an NMS is unchanged by this feature; when
a switchover occurs:
the switchover is observed by NMS surveillance
other NMS activities such as provisioning, backup/restore, software
download, and performance viewer sessions are terminated and must be
manually restarted; that is, the context must be re-established by the user
(it is not necessary to restart the NMS tools or to redo authentication)
An operator can issue a command requesting a CP switchover. A manually
requested CP switchover has the same capabilities and limitations as a
system-initiated switchover that occurs due to CP failure.
Alarms, logs, accounting, and statistics
Accounting records queued on FPs which stay up during CP switchover and
the counters used to produce these records are preserved across CP
switchover. These records have been generated but not yet delivered to the
CP. Accounting records are generated under these conditions:
when a call terminates
at the start of a new Time of Day Accounting (TODA) interval (or every
12 hours, if TODA is not used)
Collected data (alarms, logs, etc.) is not affected by CP switchover, except
that any data collected by the failed CP but not yet delivered to its destination
(either the disk or the network management station) may be lost. In addition,
up to two events in transit from an FP (in each collected data stream) may
be lost when a CP switchover occurs.
Shelf management 619
Passport Operations and Maintenance Guide 4S3
Spooled data (both for statistics and accounting) that has been written to disk
when the switchover occurs is preserved. Up to 4K bytes (on average 2K
bytes) of data that is destined for the disk but is not yet written is lost. The
disk buffer is flushed either whenever it becomes full or when it is not empty
and no data has been written to it during the preceding 5 min interval. In the
case of accounting data, the flush timer is 10 s rather than 5 min.
The following statistics are affected by CP switchover:
ifTable and SNMP agent statistics are reset to 0 by a switchover
accumulated packet forwarding statistics are reset to 0 by a switchover
Card tests
Any card test that is in progress when a CP switchover occurs continues to
run unless the source card (the card specified in the Start command) is the
standby CP when the test was started.
User-interface recovery
The user interface recovery time following a hot standby CP switchover
varies and is a function of the following:
number of components on the node
concurrent activity on the node
and the state of the provisioning information on the standby CP.
To speed up user interface recovery following a switchover, the system loads
a copy of the committed provisioning view on the standby CP during the boot
process. Further, the system loads a new committed view on the standby CP
whenever the operator commits the current view.
Following a CP switchover, the system reactivates the components residing
on the CP and the components residing on the FPs that restarted during the
switchover. Components residing on FPs that did not restart have to re-
register with the provisioning system. Alarm 70000007 is used to indicate
that component activation is complete. Depending on the number of
components on the node, components re-registration may not be completed
when the alarm is generated.
620 Chapter 18
241-7001-150 4S3
If a CP switchover occurs while the system is loading a committed le onto
the standby CP, the following occurs:
FPs running a supported conguration stay in service during the
switchover as long as all the conditions required for a hot standby CP
switchover are met
user interface recovery time is signicantly longer, particularly if many
components are provisioned; in this scenario, the entire committed le is
re-loaded before the FP components can re-register
In the worst case, the user interface (that is, operator access to components)
is unavailable for approximately the same length of time that it would be
unavailable following a full shelf reboot. To guard against this condition, the
system prohibits manual switchover using the command switchover lp/0
while the committed file is loading on the standby CP.
Note: CP RESET and RESTART commands are not prohibited during
the loading action. Issuing these commands to the active CP effectively
forces a CP switchover in dual CP systems.
The time needed for the re-registration of active components with the new CP
varies and depends on the total number of components and the other activities
taking place on the newly active CP. For example, new call requests may slow
down the components re-registration process. Components are available to
the user interface as they re-register. From a user point of view, this means
that commands against components that have not yet re-register fail until they
re-register.
Conditions and limitations
There are conditions that must be met before a hot standby switchover is
permitted, and some limitations to the degree of success that is obtained when
the switchover is complete.
Node-level conditions
When one or more node-level conditions are not met, all FPs on the node
restart when a CP switchover occurs.
Shelf management 621
Passport Operations and Maintenance Guide 4S3
When the active CP fails, the standby determines whether it should attempt a
hot standby switchover. If permitted, the CP reinitializes its application
software in active mode; otherwise a shelf restart occurs.
Hot standby switchover is attempted when all of the following conditions are
met:
there is a standby CP
the standby CP is fault-free
hot standby CP redundancy is enabled (see Disabling and enabling hot
standby CP redundancy on page 625)
the provisioned data le loaded on the standby CP is identical to that in
the committed view (incompatible data files occur when a software
upgrade is in progress: all FPs are restarted (and reloaded)
10 minutes or more has elapsed since complete recovery from the last hot
standby switchover
Note 1: Passport starts a 10 min timer after a hot standby switchover
recovery is complete. If the newly active CP fails or if a manual
switchover is attempted within that 10 min period, Passport initiates a
full shelf reset. This reset is required because both CPs have failed within
a 10 min period. The reset restores proper operation. This behavior is a
safety mechanism that prevents faulty CPs from repeatedly initiating
switchover.
Note 2: Manual switchovers triggered by using the command
switchover lp/0, are not subject to the 10 min timer. Typing this
command will cause an attempted hot standby switchover subject to the
conditions and limitations described above.
If any one or more of these conditions are not met, a shelf restart occurs.
Even if the standby CP does not restart the shelf, some or all of the FPs can
elect to restart as described in Per-FP conditions on page 622.
622 Chapter 18
241-7001-150 4S3
Per-FP conditions
Even if all node-level conditions are satised, a given FP may restart when a
CP switchover occurs. An FP completes a successful hot standby switchover
when all of the following conditions are met.
All features provisioned on the FP support hot standby.
If several different features are provisioned on a single FP, and any one
of them does not support hot standby, then that FP and all the applications
on it are restarted (that is, none of the application instances resident on
that FP can provide hot standby).
The provisioned data loaded on the FP matches that of the newly active
CP.
For example, if the FP is running uncommitted data, an FP restart occurs.
The current state of all applications on the FP does not preclude hot
standby CP redundancy.
Restarting the FP is a permitted (though not preferred) recovery strategy
for applications that cannot otherwise recover following a CP switchover
(no currently supported feature restarts an FP for this reason).
The newly active CP resynchronizes with the FP within a reasonable
time (approximately 60 s).
Failure to resynchronize within this time period may occur if the CP
disks are not synchronized at the time of the switchover.
Limitations
Hot standby CP redundancy does not guarantee that the switchover is always
successfully completed. Failure conditions may cause links to be taken down
as necessary to affect recovery.
Examples of conditions which may cause a link to be taken down are:
the software running on the node connected to this link has not been
upgraded to a level which can support hot standby CP redundancy; that
is, all links to switches running old software are taken down (see
Deployment of hot standby CP redundancy on page 624)
Shelf management 623
Passport Operations and Maintenance Guide 4S3
Services supporting hot standby CP redundancy
A feature is said to support CP switchover if it can recover from a switchover
without restarting the FP. For any given FP, the presence of any feature not
supporting hot standby CP redundancy causes the FP to restart when a
switchover occurs.
Service support for hot standby CP redundancy on page 623 identifies
which services support hot standby CP redundancy.
Table 72
Service support for hot standby CP redundancy
Feature Supports hot standby
atmBearerService yes
atmTrunks yes
bitTransparent yes
bridge no
dpnRouting yes
dpnTrunks (see note) yes
echoCancellor yes
frameRelayDte no
frameRelayNni yes
frameRelayUni yes
frameRelayUniPvcSvc yes
hdlcTransparent yes
ip no
ipx no
netSentry no
networkNode (SNA) no
porsTrunks yes
ppp no
(Sheet 1 of 2)
624 Chapter 18
241-7001-150 4S3
Deployment of hot standby CP redundancy
There are no software compatibility issues constraining deployment of hot
standby CP redundancy in a Passport network. However, to obtain the full
benefit of this feature on any given node in the network, the software on
neighboring Passports must be upgraded to a level which includes this
feature.
For any trunk connecting Passport node A on which the software level
supports hot standby CP redundancy to Passport node B configured with a
software level that does not include this feature, that trunk restages whenever
a CP switchover occurs on node A. However, the FP for this trunk on node
A remains in service, provided node and FP level restrictions are met,
regardless of the software level of node B.
If node B does have this feature in its software and hot standby CP
redundancy is enabled on node A, then trunks connecting node A to node
B stay up when a CP switchover occurs on node A, again provided node
and FP level restrictions are met. This behavior occurs regardless of whether
the feature is enabled on node B or not.
silenceSuppressor yes
unackTrunks yes
vns no
vtds yes
voice yes
voiceCompressor yes
x25Dte no
Note: Provisioning dpnTrunks on an FP does not cause that FP to restart
on CP switchover, but all DPN trunks re-stage if a switchover occurs; the
network routes trafc destined for DPN nodes around this node while DPN
trunks re-stage.
Table 72 (continued)
Service support for hot standby CP redundancy
Feature Supports hot standby
(Sheet 2 of 2)
Shelf management 625
Passport Operations and Maintenance Guide 4S3
Hot standby CP redundancy behaviors by network deployment on page 625
summarizes trunk and FP behavior for all possible network deployment
configurations.
Disabling and enabling hot standby CP redundancy
Hot standby CP redundancy permits the standby CP to acquire state
information when the active CP fails. This allows FPs associated with
services that support hot standby CP redundancy to continue operating
without interruption.
By default, this capability is enabled. It can be disabled by including the
noHitlessCpSwitch feature in the feature list of the Sw Lpt component
provisioned on the CPs. When hot standby is disabled, warm standby is still
provided.
Note: OSI standards consider both CP standby modes to be cold standby.
Therefore, when you display the OSI standby status of a CP, it will
indicate cold standby, regardless of whether the CP is in warm or hot
standby mode.
For more information on software features, see Software installation on
page 165. For detailed procedures on adding software features, see Adding
more software features to an LPT on page 609; for detailed procedures on
removing software features, see Removing a software feature from an LPT
on page 610.
Table 73
Hot standby CP redundancy behaviors by network deployment
Hot standby CP redundancy
capability on node A
Hot standby CP redundancy
capability on node B
Trunk FP
behavior
(on node A)
Trunk A-B
behavior
Available Enabled Available Enabled
no N/A (dont care) (dont care) goes down goes down
yes no (dont care) (dont care) goes down goes down
yes yes no N/A stays up goes down
yes yes yes (dont care) stays up stays up
626 Chapter 18
241-7001-150 4S3
The procedures in this section assume that you are in edit mode for
provisioning. For introductory discussions on provisioning and provisioning
views, see Provisioning system description on page 85 in this document
and to 241-7501-210, Passport Components.
Procedure 190
Disabling hot standby CP redundancy
Use this procedure to disable hot standby CP redundancy. When
disabled, the standby CP in warm standby mode.
1 Add the noHitlessCpSwitch application feature.
> set sw lpt/<lptname> featureList noHitlessCpSwitch
where:
<lptname> is the name of the logical processor type associated with the
CP.
By adding the noHitlessCpSwitch feature, the hot standby capability is
disabled.
2 Commit the provisioning view.
Procedure 191
Enabling hot standby CP redundancy
Use this procedure to enable hot standby CP redundancy. Since hot
standby is enabled by default, this procedure is used whenever the
feature has been disabled.
1 Delete the noHitlessCpSwitch application feature.
> set sw lpt/<lptname> featureList ~noHitlessCpSwitch
where:
<lptname> is the name of the logical processor type associated with the
CP.
By deleting the noHitlessCpSwitch feature, hot standby is enabled.
2 Commit the provisioning view.
Note: Committing the provisioning view causes a CP reboot.
Shelf management 627
Passport Operations and Maintenance Guide 4S3
File system
The following sections deal with the Passport file system, in particular the
procedures and processes that deal with disk synchronization.
For a detailed description of the file system and its features, see 241-7001-
110, Passport General Description.
Before performing any of the procedures in subsequent sections, you should
note the following le system rules:
File names and path names are case-sensitive.
File and directory names cannot be longer than 40 characters.
File names, including the path, cannot be longer than 128 characters,
although on-line help indicates a maximum of 140 characters. However,
on-line help does not take into account the 12 characters that the system
reserves for internal device names.
Note: Slashes (/) count as characters, but quotes ( ) do not.
Directory names, including the path, cannot exceed 125 characters (three
are reserved for internal use).
The maximum hierarchy depth is 10 directory levels.
The root directory can have a maximum of 60 items (that is, directories
and les).
The only characters that can appear in a lename are the alphanumeric
characters, the. (dot) and the _ (underscore).
What is disk synchronization?
Disks are in sync when modifications on the active disk are shadowed on the
standby disk.
Disruptions in disk synchronization
Although disks are maintained in synchronization, there may be some
situations when a given operation has been performed on one disk and not the
other. If there is a loss of power during this time, the two disks will not match
after the node has rebooted.
628 Chapter 18
241-7001-150 4S3
A disk hardware failure can also cause the disks to go out of sync. If one of
the two disks in the system fails, the switch continues to operate on one disk.
The system will not update the failed disk.
Automatic synchronization
The synchronization process starts automatically in the following situations:
when you insert a standby control processor having an identical disk
volume name to that of the active control processor
when you power up a shelf having two control processors with the same
disk volume name
Manual synchronization
You can manually initiate the synchronization process by issuing the
synchronize command.
File system commands
This section provides a list and brief description of the commands (and their
abbreviations) that you can use in conjunction with the FileSystem
component. For details on command options and responses, see
241-7501-210, Passport Components.
Table 74
File system commands
Command Description
Synchronize (sync) Synchronizes the standby disk with the active disk.
ListFile (ls) Lists the contents of a directory. The directory is
specified by the -p pathname option.
The -s option displays the status, but not the
contents of the current directory.
The -n option displays file/dir which is newer than
the given file name.
If no pathname is specified, the current working
directory is used.
(Sheet 1 of 3)
Shelf management 629
Passport Operations and Maintenance Guide 4S3
Move (mv) Moves or renames files. The source and
destination files are specified by the -s option and
the -d option respectively. Both -s and -d are
mandatory.
When using this command, it is good practice to
move files to a directory and not the root. The root
should be reserved for directories only.
Remove Removes files. The file is specified by the
pathname supplied in the -p option (mandatory).
The -r option causes a recursive delete of all
subdirectories. You must use this option to remove
any directory including an empty one.
The -f option causes protected files to be
unprotected and removed.
CAUTION
Possible damage to data integrity
Do not remove directories at the root. These
directories contain necessary system data and
software. In particular, never remove a /tmp
directory as its removal causes a system failure.
Copy (cp) Copies files. The source and destination files are
specified by the -s and the destination -d option
respectively. Both -s and -d are mandatory.
The -r option causes directories and
subdirectories to be recursively copied.
When using this command, it is good practice to
copy files to a directory and not the root. The root
should be reserved for directories only.
Protect Protects files. The file is specified by the pathname
supplied in the -p option. Note that this command
is only effective when protecting files. You cannot
use it to protect directories.
Table 74 (continued)
File system commands
Command Description
(Sheet 2 of 3)
630 Chapter 18
241-7001-150 4S3
Disk full conditions
When a disk is 85% full, an alarm is generated within 5 min. However, by
issuing the display fs command, an operator can force the alarm to appear
immediately.
The alarm is cleared when the disk is at 75% full (or below). The clear alarm
will appear within 5 min or as soon as the operator issues the display fs
command.
When you encounter disk full conditions, you must remove any unused
software and provisioning files. For information on removing software files,
see Removing unused software files on page 602. For information on
removing provisioning files, see tidy prov on page 130.
Unprotect Unprotects files. The file is specified by the
pathname supplied in the -p option.
Touch Creates an empty file if the specified file does not
exist. If the file exists, the time stamp for the file is
updated to the current time. The file is specified by
the pathname supplied in the -p option.
The -date(yyyy-mm-dd hh:mm:ss) option is used
to update the files modification time. If this option
is not specified, then the files modification time is
updated with the current date and time.
MakeDirectory (mkdir) Creates new directories. The directory is specified
by the pathname supplied in the -p option.
Chdir (cd) Changes the current working directory. The
directory is specified by the pathname supplied in
the -p option.
WorkingDirectory (pwd) Displays the working directory.
Table 74 (continued)
File system commands
Command Description
(Sheet 3 of 3)
Shelf management 631
Passport Operations and Maintenance Guide 4S3
Synchronizing disks
At start-up time, the le system automatically synchronizes the standby and
active disks if they both have the same volume name. If the disks do not have
the same volume name, you have to manually synchronize the disks using the
steps provided in Synchronizing the active and standby disks on page 631.
Procedure 192
Synchronizing the active and standby disks
1 Synchronize the disks.
sync fs
The active and standby disks are now synchronized. The system also
ensures at this point that both disks have the same volume name. The
volume name is taken from the active CP.
Depending on the amount of data stored on the active disk and the
difference between the two disks, the synchronization could take several
hours.
Changing the volume name of a disk
If you want to change a disks volume name, follow the steps in Changing a
disks volume name on page 631.
Procedure 193
Changing a disks volume name
1 Lock the le system.
lock fs
Note 1: fs is an abbreviation for the FileSystem component.
Note 2: This step is necessary only for the active control processor.
2 Lock the disk.
lock fs disk/<n>
where:
<n> is the number of the disk. The disk number corresponds to the slot
number of the CP that holds the disk.
3 Set the volume names on each of the two disks.
set fs disk/<n> volumeName <volumename>
where:
<n> is the number of the disk
<volumename> is the volume name of the disk (up to 11 characters)
632 Chapter 18
241-7001-150 4S3
4 Unlock the disk.
unlock fs disk/<n>
where:
<n> is the number of the disk
5 Unlock the le system.
unlock fs
Formatting a disk
The following procedure explains how to format a disk.
Note: Passport may format the disk drive to a different size than the
physical size indicated on the drive.
Procedure 194
Formatting a disk
1 Lock the disk on the standby CP.
lock fs disk/<n>
where:
<n> is the slot number of the standby CP
CAUTION
Loss of important les may result from using the
format command
The format command erases all les on the disk and
resets the disk volume name.
If your node has only one control processor (CP), do not
format its disk. You should only format a disk if you
have two CPs and one of them is in standby mode.
Never format the disk on the active CP.
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.
Shelf management 633
Passport Operations and Maintenance Guide 4S3
2 Format the disk on the standby CP.
format -v(<volumename>) [-backward] fs disk/<n>
where:
<volumename> is the name of the volume (optional)
<n> is the slot number of the standby CP
[-backward] is an option used to reformat a disk to the maximum size
supported in a pre-le enhancements supported software (optional)
Note: If you do not specify the volume name, the rst 11 characters of the
node name become the volume name.
3 Reset the standby CP.
reset shelf card/<n>
where:
<n> is the slot number of the standby CP
The standby CP attempts to load from its disk, which it cannot do because
its disk is now blank. After four attempts, it initiates a crossload from the
active CP.
4 When the standby CP comes up, synchronize the le system.
sync fs
The synchronization can take several hours depending on the amount of
data stored on the active disk.
Replacing a control processor in a single-CP node
Passport nodes commissioned with a single CP do not have redundant control
and file processing systems. If the single CP fails for any reason, a standby is
not available as a backup. Hence, service is interrupted and recovery must be
undertaken immediately.
Note: For instructions on replacing a CFP1 card, see 241-7001-170,
Passport Control and Function Processor (CFP1) User Guide.
634 Chapter 18
241-7001-150 4S3
There are four scenarios in which CP recovery in a single-CP node can occur.
These scenarios are dened by the availability of an NMS backup of the failed
nodes provisioning les and the availability of a donor node for obtaining a
standby CP. These scenarios are identied in the following points and are
ordered from best-case to worst-case:
a recent backup of provisioning les is available on the NMS and a
redundant node within the same Passport group is available as a donor
node
a recent backup of provisioning les is available on the NMS and a
redundant node within the same Passport group is not available as a
donor node
a recent backup of provisioning les is not available on the NMS and a
redundant node within the same Passport group is available as a donor
node
a recent backup of provisioning les is not available on the NMS and a
redundant node within the same Passport group is not available as a
donor node
Notes on CP recovery for single-CP nodes
The PPBACKUP maintenance utility should be run regularly as a cron job
through the NMS or whenever provisioning changes are made. This practice
ensures that backups of the provisioning files are always available.
When using a donor node to reload software and provisioning files for the
failed node, the donor must be within the same Passport group as defined
through the NMS. See 241-6001-023, NMS Architect for Passport User
Guide, for more information on Passport groups.
There are three parts to the recovery scenario for single-CP systems:
re-establish connection to the network (and the NMS if available)
re-install software
reprovision the new control processor
Each part is discussed in the following sections.
Shelf management 635
Passport Operations and Maintenance Guide 4S3
Re-establishing connection to the network
Re-establishing the connection to the network depends on the configuration
of both the network and the Passport nodes in the network.
If there is a Passport available (a donor node) that has a fault-free standby CP
which can be removed without undue risk of service degradation, then that
standby CP can be used to replace the failed CP in the single-CP system (the
recipient node). In this way, the connection to the network (and the NMS if
used) is quickly re-established without undertaking the startup routines
described in 241-7001-130, Passport Startup Guide. Software and
provisioning data can then be reintroduced to the failed system. In the donor
node, a new CP can be installed in the standby slot and the disks synchronized
to re-establish CP and disk redundancy.
If there are no nodes in the network that support a standby CP, re-establishing
connection to the network involves undertaking the startup routines described
in 241-7001-130, Passport Startup Guide. Once the trunk is available,
software and provisioning data can then be reintroduced to the failed system.
Reinstalling software
When the first step of installing the new CP is complete, software must be
reinstalled as the second step.
Even if the new CP is obtained from a donor node, the software configuration
will probably differ between the donor and the recipient. It is always best to
reinstall software in this recovery scenario.
Before you can re-install the software that supports the level of service
offered by the node, you must clean up the files on the disk. In some cases,
you will want to reformat the CPs disk to ensure that the disk is free of
unnecessary files.
If the network makes extensive use of the NMS to provision nodes and create
node file system backups, you can use the NMS to reinstall the software. If
an NMS-based backup is not available, reinstall the software using the
procedures outlined in Software installation on page 165 of this document.
636 Chapter 18
241-7001-150 4S3
Reprovisioning the new control processor
The steps undertaken to reprovision the failed node depends on the tools used
to manage the network.
If you are using the NMS and a backup of the most current view of the
operational data has been maintained, then this view can be downloaded. If a
backup is not available, or network management is undertaken through an
ASCII terminal, then the node must be manually reprovisioned.
Procedure 195
Replacing a control processor in a single-CP system (donor node is
available and NMS backup is available)
1 Remove the standby CP from the shelf of the donor node.
Note: You will install this CP on the failed node once you have congured
a new standby CP on the donor node.
2 Insert a new CP into the standby slot of the donor node.
3 Synchronize the new standby disk with the active disk on the donor node.
sync fs
Note 1: The new standby disk should be the same size as the active disk.
If not, see "Adding a second control processor to a single-CP system" on
page 641.
Note 2: Depending on the amount of data stored on the active disk and
the difference between the two disks, the synchronization could take
several hours.
4 Remove the failed CP from the shelf of the failed Passport.
5 Install the CP you removed from the donor node into the active slot of the
failed Passport.
6 When the CP comes up (green LED is lit), clean up the le system of the
CP.
You should remove any unnecessary les from the disk, including unused
software, unused provisioning les, and the spooling les stored in the
/spooled/closed directory. For information on removing les, see the
following:
tidy prov on page 130
Removing unused software les on page 602
File system commands on page 628
Shelf management 637
Passport Operations and Maintenance Guide 4S3
7 Restore the les from the last NMS backup. See 241-6001-023, NMS
Architect for Passport User Guide for procedures on le restore.
8 Activate the provisioning le that was running when the last backup to the
NMS was made.
reloadcp -f(<filename>) lp/0
where:
<filename> is the name of the provisioning le used to reload the
control processor
9 If provisioning view has changed since the last NMS backup was made,
enter the changes now. Use procedures in the following chapters:
Provisioning system description on page 85
Initial node provisioning steps on page 201
Node security on page 205
Node provisioning on page 217
Procedure 196
Replacing a control processor in a single-CP system (donor node is
available and NMS backup is not available)
1 Remove the standby CP from the shelf of the donor node.
Note: You will install this CP on the failed node once you have congured
a new standby CP on the donor node.
2 Insert a new CP into the standby slot of the donor node.
3 Synchronize the new standby disk with the active disk on the donor node.
sync fs
Note 1: The new standby disk should be the same size as the active disk.
If not, see "Adding a second control processor to a single-CP system" on
page 641.
Note 2: Depending on the amount of data stored on the active disk and
the difference between the two disks, the synchronization could take
several hours.
4 Remove the failed CP from the shelf of the failed Passport.
5 Install the CP you removed from the donor node into the active slot of the
failed Passport.
6 When the CP comes up (green LED is lit), clean up the le system of the
CP.
638 Chapter 18
241-7001-150 4S3
You should remove any unnecessary les from the disk, including unused
software, unused provisioning les, and the spooling les stored in the
/spooled/closed directory. For information on removing les, see the
following:
tidy prov on page 130
Removing unused software les on page 602
File system commands on page 628
7 Install the application versions (AV) for the node using the procedures
described in Software installation on page 165.
8 Provision the node using the procedures in the following chapters:
Provisioning processes on page 137
Initial node provisioning steps on page 201
Node security on page 205
Node provisioning on page 217
Your ofce should have a printout of the most recent operational
provisioning view. You can use this printout for reprovisioning.
Procedure 197
Replacing a control processor in a single-CP system (donor node is not
available and NMS backup is available)
1 Obtain a new CP from the spare cards inventory.
2 On the failed Passport, remove the failed CP from the shelf.
3 Insert the new CP into the active slot on the shelf of the failed Passport.
4 Re-establish the connection to the network using the startup procedures
described in 241-7001-130, Passport Startup Guide.
5 Clean up the le system of the new CP.
You should remove any unnecessary les from the disk, including unused
software, unused provisioning les, and the spooling les stored in the
/spooled/closed directory. For information on removing les, see the
following:
tidy prov on page 130
Removing unused software les on page 602
File system commands on page 628
Shelf management 639
Passport Operations and Maintenance Guide 4S3
6 Restore the les from the last NMS backup. See 241-6001-023, NMS
Architect for Passport User Guide for procedures on le restore.
7 When the CP comes up (green LED is lit), activate the provisioning le
that was running when the last backup to the NMS was made.
reloadcp -f(<filename>) lp/0
where:
<filename> is the name of the provisioning le used to reload the
control processor
8 If provisioning view has changed since the last NMS backup was made,
enter the changes now. Use procedures in the following chapters:
Provisioning processes on page 137
Initial node provisioning steps on page 201
Node security on page 205
Node provisioning on page 217
Procedure 198
Replacing a control processor in a single-CP system (donor node is not
available and NMS backup is not available)
1 Obtain a new CP from the spare cards inventory.
2 On the failed Passport, remove the failed CP from the shelf.
3 Insert the new CP into the active slot on the shelf of the failed Passport.
4 Re-establish the connection to the network using the startup procedures
described in 241-7001-130, Passport Startup Guide.
5 Clean up the le system of the new CP.
You should remove any unnecessary les from the disk, including unused
software, unused provisioning les, and the spooling les stored in the
/spooled/closed directory. For information on removing les, see the
following:
tidy prov on page 130
Removing unused software les on page 602
File system commands on page 628
6 Reinstall the application versions (AV) for the node using the procedures
described in Software installation on page 165.
640 Chapter 18
241-7001-150 4S3
7 Reprovision the node using the procedures in the following chapters:
Provisioning processes on page 137
Initial node provisioning steps on page 201
Node security on page 205
Node provisioning on page 217
Your ofce should have a printout of the most recent operational
provisioning view. You can use this printout for reprovisioning.
Replacing a control processor in a two-CP node
Passport nodes with two CPs have the advantage of redundancy for both
control and file processing systems. Should the active CP fail for any reason,
the standby CP can take over processing. The faulty CP can then be replaced
without interruption in service.
Note: There is a possibility, however remote, that both CPs can fail
simultaneously. In this situation, the recovery scenario is similar to that
for a single-CP system. See the discussion and procedures described
under "Replacing a control processor in a single-CP node" on page 633.
The following procedure explains how to replace and synchronize a disk
(containing software) in a two-disk system.
Note: The size of the replacement disk does not necessarily have to
equal the size of the disk you are replacing.
Procedure 199
Replacing a control processor in a two-CP system
1 If necessary, force the control processor you want to remove to become
the standby control processor by using the switchover command.
switchover lp/0
2 Remove the standby control processor. See 241-7001-125, Passport
Hardware Installation Guide for the procedure to remove a control
processor.
3 Insert a new control processor in the standby slot and wait for it to come
up.
4 If necessary, log on as local operator.
Shelf management 641
Passport Operations and Maintenance Guide 4S3
5 Conrm that both disks are present.
list fs
Note: fs is an abbreviation for the FileSystem component.
6 Check to see If the volume name of the new control processor is different
from the active control processor.
d fs disk/*
If the volume names of the two disks differ, proceed to the next step to
perform manual synchronization. If the volume names are the same,
automatic synchronization occurs, eliminating the need to manually
synchronize.
7 Issue the sync command. Perform this step only if the volume names
differ.
sync fs
An alarm appears to indicate that the le system is now synchronized.
Adding a second control processor to a single-CP system
The following procedure explains how to add another control processor to a
single-CP system.
Procedure 200
Adding a second control processor
1 Provision the new CP for the standby slot. See Processor card
provisioning on page 293 for the procedure required to provision the
standby CP.
2 Insert a new control processor in the standby slot.
3 If necessary, log on as local operator.
4 Conrm that both disks are present.
list fs
Note: fs is an abbreviation for the FileSystem component.
5 Synchronize the new standby disk with the active disk.
sync fs
An alarm appears to indicate that the File system is now synchronized.
642 Chapter 18
241-7001-150 4S3
6 Check to see if the volume name for the new standby control processor
is the same as the volume name for the active control processor.
d fs disk/*
7 If the volume name of the standby is different, change the volume name
on the standby CP using "Changing a disks volume name" on page 631.
Maintaining a node that has different size disks
This section explains how to maintain a dual control processor node that has
different size disks.
The two disks on a dual control processor node are used as is, whether or not
the two disks are different sizes. No special formatting is required. The file
system operates as if the two disks are the same size until the smallest disk is
full. Once the smallest disk is full, the file system responds as outlined in the
following subsections.
Note: The feature that permits you to install disks of different sizes is
intended as an upgrade measure for the nodes disk subsystems. This
feature permits you to upgrade disks one at a time so that there is no
impact on services. It is not recommended that you operate the node for
more than a few hours if the conguration includes disks of different
sizes. If the node must operate in this conguration for an extended
period, the smaller disk should be set as the active disk to ensure that the
system does not lose disk redundancy.
Where the larger disk is the active disk
Once the standby (smallest) disk is full, the le system is unable to provide
redundancy. This reduction in service is signalled by the following two
alarms:
7008 1002 File system full
7008 1019 File system lost disk redundancy
The File system full alarm is immediately cleared and the file system
capacity and free space are set to equal the active (larger) disks capacity. The
file system service is not affected. However, data redundancy is now off. This
is a normal transition from a dual-disk (redundant) file system to a single-disk
file system.
Shelf management 643
Passport Operations and Maintenance Guide 4S3
Note: Manually synchronizing the le system at this time results in the
error message Insufficient standby disk capacity, followed by
the alarm File system synchronization failed. Rebooting the
standby control processor at this time results in the alarmFile system
synchronization failed.
To clear all of the previous alarms, remove unused provisioning and software
filed from the active (larger) disk and resynchronize the file system. (For
more information on tidying disks, see Software management on
page 601.)
Where the larger disk is the standby disk
Once the active (smaller) disk is full, the file system can no longer record
data. Immediate action is required to ensure that data is not lost due to a full
file system.
To restore service and clear all alarms, remove unused provisioning and
software files from the active disk and resynchronize the file system. (For
more information on tidying disks, see Software management on
page 601.)
Setting the network time
The Time component provides access to the network time. The network time
is the date and time that is common across the whole network. It is the time
used for timestamps, displayed on alarms and accounting data.
If you set the time on each Passport node individually, there is no notion of
zonal time, therefore Nortel recommends that you use Universal Time
Coordinated (UTC). If you have the Magellan Network Management System
(NMS) (Nortels proprietary network management system), you can set the
network time by adding an offset to the NMS reference time, which is UTC.
Procedure 201
Setting network time
1 Under the Time component, set the networkTime attribute to the current
date and time.
Note 1: It is not necessary to create the Time component because
Passport creates it automatically at startup time.
644 Chapter 18
241-7001-150 4S3
Note 2: The set command fails if the Time component is synchronized
with Network Time Protocol (NTP). If you issue a display command on the
Time component, the system shows the synchronization status.
set Time networkTime <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
The new time appears on the interface.
Setting the network time offset
Setting the time offset on page 645 explains how to set the network time
offset to change network time from UTC to local time using a text interface
device.
The time offset range is from 0 to 1440 min (24 hours). A time offset between
0 and 720 min (12 hours) represents a time ahead of UTC (or east of the prime
meridian). A time offset value between 721-1439 min (23 hours, 59 min)
represents a time behind UTC (or west of the prime meridian).
Example1: Setting the time to UTC
If you are in a location that uses UTC, the timeOffset attribute should be
at 0. 0 is the default, and means that network time is equal to UTC.
Example2: Setting the time ahead of UTC
If you are in a country east of the prime meridian, add 60 min to the
minimum time offset (0) for each hour you are ahead of UTC. For
example, if 14:00 UTC is 16:00 in your time zone, set the timeOffset
attribute to 120.
Example3: Setting the time behind UTC
If you are in a country west of the prime meridian (for example, the
United States), subtract 60 from the maximum time offset (1440) for
each hour you are behind UTC. For example, if 20:00 UTC is 16:00 in
your time zone, set the timeOffset attribute to 1200 (that is, 1440 - (4
X60)).
Shelf management 645
Passport Operations and Maintenance Guide 4S3
Procedure 202
Setting the time offset
1 Display the current setting of the time offset (optional).
display Time
Note: It is not necessary to create the Time component because the
system creates it automatically at startup time.
2 Set the timeOffset attribute of the Time component.
set Time timeOffset <offset value>
where:
<offset value> is an integer between 0 and 1440 (min)
Resetting the network time after a power off
If you are resetting the network time after a power off, you must set the time
offset before you set the network time.
Note: If the node has already synchronized with the XNTP (Network
Time Protocol), then the second command is disallowed.
Procedure 203
Resetting the network time and the time offset after a power off
Note: The following procedure is required only if the node was powered
off for more than 24 hours.
1 Set the time offset:
CAUTION
Corruption of accounting records and alarm
timestamps
The time offset must be the same on every node in the
network. It is the operator responsibility to set it
manually on every node.
If different nodes are set to different times, then
accounting records are corrupted, because they are
generated according to the time. If two alarms on
different nodes are generated at same time, they would
have different time stamps.
646 Chapter 18
241-7001-150 4S3
set Time timeOffset <offset value>
where:
<offset value> is an integer between 0 and 1440 (min)
2 Set the network time.
set Time networkTime <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
647
Passport Operations and Maintenance Guide 4S3
Chapter 19
Regularly scheduled activities
This chapter lists activities you must perform regularly to maintain the
Passport node.
Regularly scheduled software activities on page 647 and Regularly
scheduled hardware activities on page 648 list activities for daily, weekly,
and monthly schedules with references to the appropriate chapter or
document for details. The frequency of activities can vary according to office
requirements.
Table 75
Regularly scheduled software activities
Frequency of
activity
Activity Where to find procedure
Daily Time-of-day accounting Data collection on
page 459
Sending Passport
accounting data to a billing
host
241-7501-400, Passport
Accounting Reference Guide
Weekly Checking synchronization Shelf management on
page 599
Checking spooling Data collection on
page 459
Backing up service data 241-6001-023, NMS
Architect for Passport User
Guide
(Sheet 1 of 2)
648 Chapter 19
241-7001-150 4S3
Monthly Cleaning up software files Shelf management on
page 599
Cleaning up provisioning
files
"tidy prov" on page 130
Table 76
Regularly scheduled hardware activities
Frequency of
activity
Activity Where to find procedure
Daily no daily activities needed
Weekly no weekly activities needed
Monthly Changing the air filter 241-7001-125, Passport
Hardware Installation Guide
Bus test Diagnostic tests on
page 523
Card test Diagnostic tests on
page 523
Port test Diagnostic tests on
page 523
Disk test Diagnostic tests on
page 523
Table 75 (continued)
Regularly scheduled software activities
Frequency of
activity
Activity Where to find procedure
(Sheet 2 of 2)
649
Passport Operations and Maintenance Guide 4S3
Appendix
OSI state combinations
This appendix provides information on OSI component states combinations.
OSI states
The Magellan Passport node uses component state definitions according to
the OSI standards. Components that do not provide any behavior do not
require any component state variables defined and are not discussed in this
appendix.
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-7501-230, Passport Alarms.
650 Appendix
241-7001-150 4S3
Data collection system component states
File system component states
Table 77
Spooler component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle This is valid when the spooler is unable to spool due to some file
system error. It also could be provisioned off.
Unlocked, Enabled, Idle This is typically valid when the spooler is provisioned 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, this
case is transient.
Unlocked, Enabled, Active This is valid when the spooler has a spooling file open and is
registered with the collector to receive records. It does not
necessarily mean that it is spooling a record at this moment, but
rather is ready to do so when required.
Locked, Disabled, Idle This is valid when the spooler is administratively prohibited from
spooling and also has detected an outstanding filesystem error.
It also could be provisioned to off.
Locked, Enabled, Idle This is valid either when provisioned off or when the spooler is
administratively prohibited from spooling but otherwise would be
ready to try and open a file and register for the data.
Table 78
FileSystem component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Enabled, Active The file system is in normal operating state.
Unlocked, Disabled, Idle The file system is not available due to internal problems.
Locked, Disabled, Idle The file system is not available and is also locked.
(Sheet 1 of 2)
OSI state combinations 651
Passport Operations and Maintenance Guide 4S3
Locked, Enabled, Idle The file system is capable of providing service but is manually
locked.
Shutting down, Enabled, Active The file system is performing some tasks. It will enter the locked
state as soon as the task is complete.
Table 79
Disk component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Enabled, Active The disk is in normal operating state.
Unlocked, Disabled, Idle The disk is not available due to internal problems.
Locked, Disabled, Idle The disk is not available and is also locked.
Locked, Enabled, Idle The disk is capable of providing service but is manually locked.
Shutting down, Enabled, Active A lock command has been issued, while the disk is performing a
certain task. It will enter the locked state as soon as the task is
complete.
Table 80
Test component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Enabled, Idle Test can be run, but is not currently running.
Unlocked, Enabled, Active Test is running.
Unlocked, Disabled, Idle Test cannot be run because the corresponding disk is not
locked.
Table 78 (continued)
FileSystem component state combination
Combination (Administrative,
Operational, Usage)
Details
(Sheet 2 of 2)
652 Appendix
241-7001-150 4S3
Trunk component states
Table 81
Trunk component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the trunk inoperable. The Atm, Utp or
Unacknowledged subcomponent reporting link down is a
possible cause. Bad line state and excessive line state changes
are possible causes.
Unlocked, Enabled, Idle The Unacknowledged subcomponent is offering service and the
trunk is now staging with the remote.
Unlocked, Enabled, Busy The Trunk component is in use. The component does not
service any user (that is, any component) but has successfully
joined packet routing.
Locked, Disabled, Idle In addition to a lock/lock -force command being in effect, the
Atm, Utp, or Unacknowledged subcomponent is reporting link
down. Bad line state and excessive line state changes are
possible causes.
ShuttingDown, Enabled, Busy A lock command is in effect. The Trunk component is waiting for
any logicalChannel subcomponents to go away before entering
the locked state.
Table 82
Unacknowledged component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the Unacknowledged component
inoperable. Framer component reporting a link down is a
possible causes.
Unlocked, Enabled, Idle The Framer subcomponent is offering service and the
Unacknowledged component is now waiting for the parent
component to start using it.
Unlocked, Enabled, Busy The Unacknowledged component is in use. The component
services only one user (a Trunk component) at a time.
OSI state combinations 653
Passport Operations and Maintenance Guide 4S3
Routing
DPN Gateway over Frame Relay component states
Table 83
Topology component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Enabled, Active Topology is exchanging routing protocol data units with
Passport neighbors. It is capable of mapping additional Passport
nodes in its topological database.
Unlocked, Enabled, Busy Topology is operational, but its topological database cannot
accept more Passport nodes. The number of Passport nodes
stored in the topology database has reached the maximum
network node number (256).
Table 84
Transport Resource Manager component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Enabled, Active The TransportResource component is operational and is
communicating with each of the Passport trunks and gateways
configured in the module. It is able to receive and process
requests.
Table 85
FrMux component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Enabled, Idle The FrMux is ready to provide service. There are no user
Applications defined on the interface.
Unlocked, Enabled, Active The FrMux is in service supporting at least one user Application.
(Sheet 1 of 2)
654 Appendix
241-7001-150 4S3
Unlocked, Disabled, Idle The FrMux is waiting for the access facility to become available.
Locked, Disabled, Idle A lock or lock-forever operator command is in effect.
Table 86
FrMuxLmi component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Enabled, Busy The LMI is in service. LMI frames are being exchanged.
Unlocked, Disabled, Idle The LMI is not operational while waiting for the interface to
become available. This is probably due to failure of the access
facility.
Table 87
DataLinkConnectionIdentifier component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Enabled, Busy The DLCI component is operational and in service.
Unlocked, Disabled, Idle The DLCI is not operational while waiting for either the interface
to become available or for the FrConnection to be established.
Table 85 (continued)
FrMux component state combination
Combination (Administrative,
Operational, Usage)
Details
(Sheet 2 of 2)
OSI state combinations 655
Passport Operations and Maintenance Guide 4S3
Network management interface system component states
All NMIS managers have the same OSI state combinations. Therefore, in the
table below, the term manager component is a generic term which refers to
any of FTP, local, FMIP, or Telnet manager.
Table 88
FrAccess component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Enabled, Idle The associated DLCI component is offering service and
FrAccess is waiting for the parent component to start using it.
Unlocked, Enabled, Busy The FrAccess component is in use. The component services
only one user (a DpnGateway component) at a time.
Unlocked, Disabled, Idle External factors render the FrAccess component inoperable. A
possible cause is that the DLCI component is reporting a failed
link.
Table 89
FTP, local, FMIP, or Telnet manager component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Enabled, Idle The manager component is operable, but currently not in use. A
manager component can be ready for service, but if no
connection is established between the interface and an external
device, then the manager component remains in the idle state.
Unlocked, Enabled, Active The manager component enters the active state when a
connection is established successfully to an external device
Unlocked, Enabled, Busy The manager component enters this state when the maximum
number of sessions that a manager component is allowed to
establish has been reached.
(Sheet 1 of 2)
656 Appendix
241-7001-150 4S3
Control Processor port management system component
states
Shutting down, Enabled, Active The manager is prohibited from accepting any new connection
establishment requests. When all existing sessions are cleared
by users, this component changes to the locked state.
Locked, Enabled, Idle. The manager is prohibited from accepting any new connection
establishment requests and there are no connections between
the interface and an external device.
Table 90
Control Processor Channel (Chan) component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the CHAN component inoperable (for
example, total BPV error threshold reached).
Unlocked, Enabled, Idle Not in use. The CHAN component is being provisioned, waiting
for binding.
Unlocked, Enabled, Busy The CHAN component is in use. The CHAN component can
only service one user at a time.
Shutting Down, Enabled, Busy A lock/lock -force operator command is issued while the CHAN
component is being used. The CHAN component is in the
process of terminating the user so that it can go into a Locked
state.
An Unlock operator command brings the component into an
Unlocked state.
(Sheet 1 of 2)
Table 89 (continued)
FTP, local, FMIP, or Telnet manager component state combination
Combination (Administrative,
Operational, Usage)
Details
(Sheet 2 of 2)
OSI state combinations 657
Passport Operations and Maintenance Guide 4S3
Locked, Enabled, Idle A lock/lock -force operator command is in effect. The CHAN
component is otherwise ready to service a user. A test is most
likely to be carried out.
Locked, Disabled, Idle Some hardware test failed and the CHAN component is in the
Locked state.
Table 91
Control Processor Test component state combination
Combination (Administrative,
Operational, Usage)
Details
Locked, Disabled, Idle The hardware component is unlocked. No resource is available
to the Test component. Start test requests will be rejected.
Locked, Enabled, Idle The hardware component is locked. A port and line test can be
performed.
Unlocked, Enabled, Active A START command has been issued, the Test process is being
created.
Unlocked, Enabled, Busy The TEST component is in use. A TEST component is created
by a V35, X21, DS1, E1, CHAN, DS3, or E3 component and only
services that particular component. A TEST component is
created when the parent hardware component receives a start
test command from the operator. A test is terminated either
when the prescribed timer expires or a stop test command is
issued by the operator or when the test fails. Then the TEST
component terminates itself. The test results and operational
attributes are then maintained by the parent component
Shutting Down, Enabled, Busy A stop operator command is issued while the Test component is
being used. The Test component is in the process of terminating
the test Framer so that it can go into a Locked state
Table 90 (continued)
Control Processor Channel (Chan) component state combination
Combination (Administrative,
Operational, Usage)
Details
(Sheet 2 of 2)
658 Appendix
241-7001-150 4S3
Framer component states
Shelf Management system component states
Table 92
Control and function processor Framer component state combination
Combination (Administrative,
Operational, Usage)
Details
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 line problem.
Unlocked, Enabled, Idle Not in use.
Unlocked, Enabled, Busy The FRAMER component is in use. The FRAMER component
services only one user (an application component) at a time.
Table 93
Control and function processor Card component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle The card is not ready to be assigned an LP.
Unlocked, Enabled, Idle The card is ready to be assigned an LP, but none has yet been
assigned.
Unlocked, Enabled, Active The card has been assigned an LP.
Shutting down, Enabled, Active The card is executing an LP, but the card will be locked as soon
as the LP stops running.
Locked, Enabled, Idle The card is not allowed to be assigned an LP.
Locked, Disabled, Idle The card is not allowed to be assigned an LP, but even if it was
allowed to, it would not be ready for it.
OSI state combinations 659
Passport Operations and Maintenance Guide 4S3
Table 94
Control and function processor LogicalProcessor (LP) component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle The LP is not available for service.
Unlocked, Enabled, Active The active instance of the LP is running.
Shutting down, Enabled, Active The active instance of the LP is running, but will be locked as
soon as it is stops running.
Locked, Disabled, Idle The LP is not allowed to be assigned to any processor card.
Table 95
Bus component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Enabled, Active The bus is in service.
Unlocked, Disabled, Idle The bus is not in service because at least one operational card
is unable to access the bus. Its availability status is Dependency.
Locked, Enabled, Idle The bus is not in service because the network administration has
locked it.
Locked, Disabled, Idle 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 96
BusTest component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle A bus test cannot be started because the bus is unlocked.
(Sheet 1 of 2)
660 Appendix
241-7001-150 4S3
Unlocked, Enabled, Idle An operator request can start the bus test.
Unlocked, Enabled, Busy A bus test is in progress.
Table 97
CardBusTap component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle The bus tap is non-operational because of one of the following
reasons:
It failed its self-test.
It is unable to receive clock signals from the bus.
It has detected too many parity errors on the bus.
OR
The bus tap is operational but is not being used to communicate
with other operational cards because the bus is disabled or
locked. Its availability status is Dependency.
Unlocked, Enabled, Active The bus tap is operational and is communicating with other
operational cards.
Table 96 (continued)
BusTest component state combination
Combination (Administrative,
Operational, Usage)
Details
(Sheet 2 of 2)
OSI state combinations 661
Passport Operations and Maintenance Guide 4S3
Function processor port management system component
states
Refer to the following for the appropriate component state combinations:
DS1, E1, and MVP on page 662
DS1 ATM and E1 ATM on page 664
HSSI on page 667
V.11 and V.35 on page 669
DS1 Voice and E1 Voice on page 670
J2MV on page 673
DS3 and E3 on page 675
DS3 ATM and E3 ATM on page 677
JT2 ATM on page 679
DS1C and E1C on page 681
OC3 on page 683
Table 98
CardTest component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle The operator cannot perform a card test because of one of the
following reasons:
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 A card test is not in progress but an operator request can start
one.
Unlocked, Enabled, Busy A card test is in progress.
662 Appendix
241-7001-150 4S3
FDDI on page 685
Ethernet on page 685
Token Ring on page 686
DS1, E1, and MVP
Table 99
DS1 component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the DS1 port inoperable because of
detection and declaration of at least one of the following alarms:
losAlarm, lofAlarm, rxAisAlarm.
Unlocked, Enabled, Busy The DS1 component is in use.
Locked, Enabled, Idle A lock operator command is in effect. The DS1 component is
otherwise ready to service a user. A test is running.
Locked, Disabled, Idle Some hardware test failed or
the DS1 component has been put in the Locked state by the
operator or
external factors render the DS1 port inoperable.
Table 100
E1 component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the E1 port inoperable because of
detection and declaration of at least one of the following alarms:
losAlarm, lofAlarm, rxAisAlarm, multifrmLofAlarm,
rxMultifrmRaiAlarm, or txMultifrmRaiAlarm.
Unlocked, Enabled, Busy The E1 component is in use.
(Sheet 1 of 2)
OSI state combinations 663
Passport Operations and Maintenance Guide 4S3
Locked, Enabled, Idle A lock operator command is in effect. The E1 component is
otherwise ready to service a user. A test is running.
Locked, Disabled, Idle Some hardware test failed or
the E1 component has been put in the Locked state by the
operator or
external factors render the E1 port inoperable.
Table 101
DS1 and E1 Channel (Chan) component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the CHAN component inoperable
because of DS1 or E1 alarms.
Unlocked, Enabled, Idle Not in use. The CHAN component is being provisioned, waiting
for binding from an application.
Unlocked, Enabled, Busy The CHAN component is in use. The CHAN component can
only service one user at a time.
Locked, Enabled, Idle A lock operator command is in effect. The CHAN component is
otherwise ready to service a user. A test is running.
Locked, Disabled, Idle Some hardware test failed or the CHAN component has been
put in the Locked state by the operator.
Table 100 (continued)
E1 component state combination
Combination (Administrative,
Operational, Usage)
Details
(Sheet 2 of 2)
664 Appendix
241-7001-150 4S3
DS1 ATM and E1 ATM
Table 102
DS1 and E1 Test component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle The hardware component is unlocked. No resource is available
to the Test component. Start test requests will be rejected.
Unlocked, Enabled, Busy The TEST component is in use. A TEST component is created
by a DS1, E1, or CHAN component and only services that
particular component. A test is terminated either when the
prescribed timer expires or a stop test command is issued by the
operator.
Table 103
DS1 component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the DS1 interface inoperable through
condition detection and declaration of at least one of the
following alarms: losAlarm, lofAlarm, rxAisAlarm, or
Through the detection of a request command by the far DS1
interface to loop back the incoming signal.
Unlocked, Enabled, Idle The DS1 component is not in use. The line input has been
recognized as good. Clocks are available.
Unlocked, Enabled, Busy The DS1 component is in use. That is, the DS1 component has
a Channel subcomponent.
ShuttingDown, Enabled, Busy A lock command has been issued against the DS1 component,
but the Channel subcomponent is not yet suspended.
(Sheet 1 of 2)
OSI state combinations 665
Passport Operations and Maintenance Guide 4S3
Locked, Enabled, Idle A lock operator command is in effect and the DS1 component is
operating in test mode (availabilityStatus: inTest).
Locked, Disabled, Idle A lock operator command is in effect and the component is in
one of the following conditions:
Left ofine (availabilityStatus: ofine)
Some hardware test failed (availabilityStatus: failed)
If running in test mode external factors will cause errors
(availabilityStatus: inTest). Bad line state and excessive line
state changes are possible causes.
Table 104
E1 component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the E1 interface inoperable through
condition detection and declaration of at least one of the
following alarms: losAlarm, lofAlarm, rxAisAlarm,
multifrmLofAlarm.
Unlocked, Enabled, Idle The E1 component is not in use. The line input has been
recognized as good. Clocks are available.
Unlocked, Enabled, Busy The E1 component is in use. That is, the E1 component has a
Channel subcomponent.
ShuttingDown, Enabled, Busy A lock command has been issued against the E1 component,
but the Channel subcomponent is not yet suspended.
(Sheet 1 of 2)
Table 103 (continued)
DS1 component state combination
Combination (Administrative,
Operational, Usage)
Details
(Sheet 2 of 2)
666 Appendix
241-7001-150 4S3
Locked, Enabled, Idle A lock operator command is in effect and the E1 component is
operating in test mode (availabilityStatus: inTest).
Locked, Disabled, Idle A lock operator command is in effect and the component is in
one of the following conditions:
Left ofine (availabilityStatus: ofine)
Some hardware test failed (availabilityStatus: failed)
If running in test mode external factors will cause errors
(availabilityStatus: inTest). Bad line state and excessive line
state changes are possible causes.
Table 105
DS1 ATM and E1 ATM Channel (Chan) component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the CHAN component inoperable
because of DS1 or E1 alarms. Also caused by detection of
lcdAlarm, and by the locking of the associated port component.
Unlocked, Enabled, Idle Not in use. The CHAN component is being provisioned, waiting
for binding from an application.
Unlocked, Enabled, Busy The CHAN component is in use. The CHAN component can
only service one user at a time.
Unlocked, Enabled, Idle The Chan component is not in use. Waiting for binding to an
ATmIf component.
ShuttingDown, Enabled, Busy A lock operator command is in effect. Waiting for a bound
application to suspend.
Locked, Disabled, Idle Some hardware test failed or the CHAN component has been
put in the Locked state by the operator.
Table 104 (continued)
E1 component state combination
Combination (Administrative,
Operational, Usage)
Details
(Sheet 2 of 2)
OSI state combinations 667
Passport Operations and Maintenance Guide 4S3
HSSI
Table 106
DS1 ATM and E1 ATM Test component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle The hardware component is unlocked. No resource is available
to the Test component. Start test requests will be rejected.
Unlocked, Enabled, Busy The TEST component is in use. A TEST component is created
by a CHAN, DS1, or E1 component and only services that
particular component. A test is terminated either when the
prescribed timer expires or a stop test command is issued by the
operator.
Table 107
HSSI component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the HSSI port inoperable through
condition detection and declaration of at least one of the
following alarms: alarms related to actualLinkMode, incorrect
link cable, input modem signal doe not meet expected.
Unlocked, Enabled, Idle The component is not in use. Being provisioned, waiting for
binding to a FRAMER component. The line input has been
recognized as good. Clocks are available.
Unlocked, Enabled, Busy The HSSI component is in use. The HSSI component services
only one user (a FRAMER component) at a time.
(Sheet 1 of 2)
668 Appendix
241-7001-150 4S3
Locked, Enabled, Idle A lock operator command is in effect and the HSSI component
is operating in test mode (availabilityStatus: inTest).
Locked, Disabled, Idle A lock operator command is in effect and the component is in
one of the following conditions:
Left ofine (availabilityStatus: ofine)
Some hardware test failed (availabilityStatus: failed)
If running in test mode external factors will cause errors
(availabilityStatus: inTest). Bad line state and excessive line
state changes are possible causes.
Table 108
HSSI Test component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle The hardware component is unlocked. No resource is available
to the Test component. Start test requests will be rejected.
Unlocked, Enabled, Busy The TEST component is in use. A TEST component is created
by a HSSI component and only services that particular
component. A test is terminated either when the prescribed timer
expires or a stop test command is issued by the operator.
Table 107 (continued)
HSSI component state combination
Combination (Administrative,
Operational, Usage)
Details
(Sheet 2 of 2)
OSI state combinations 669
Passport Operations and Maintenance Guide 4S3
V.11 and V.35
Table 109
V35 component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the V.35 port inoperable. Bad line state
and excessive line state changes are possible causes. Lack of
clocks will also disable the port.
Unlocked, Enabled, Idle The component is not in use. Waiting for a binding to a FRAMER
component. The line input has been recognized as good. Clocks
are available.
Unlocked, Enabled, Busy The V35 component is in use. The V35 component services only
one user (a FRAMER component) at a time.
Locked, Enabled, Idle A port and line test is in progress.
Locked, Disabled, Idle Some hardware test failed or the V35 component has been put
in the Locked state by the operator.
A lock operator command is in effect.
Table 110
X21 component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the X21 interface inoperable. Bad line
state and excessive line state changes are possible causes.
Lack of clocks will also disable the port.
Unlocked, Enabled, Idle The component is not in use. Being provisioned, waiting for
binding. The line input has been recognized as good. Clocks are
available.
Unlocked, Enabled, Busy The X21 component is in use. The X21 component services only
one user (a FRAMER component) at a time.
(Sheet 1 of 2)
670 Appendix
241-7001-150 4S3
DS1 Voice and E1 Voice
Locked, Enabled, Idle A port and line test is in progress.
Locked, Disabled, Idle Some hardware test failed or the X21 component has been put
in the Locked state by the operator.
A lock operator command is in effect.
Table 111
V.11 and V.35 Test component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle The hardware component is unlocked. No resource is available
to the Test component. Start test requests will be rejected.
Unlocked, Enabled, Busy The TEST component is in use. A TEST component is created
by a V35, X21, DS1, E1, CHAN, DS3, or E3 component and only
services that particular component. A test is terminated either
when the prescribed timer expires or a stop test command is
issued by the operator.
Table 112
E1 component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the E1 port inoperable because of
detection and declaration of at least one of the following alarms:
losAlarm, lofAlarm, rxAisAlarm, multifrmLofAlarm,
rxMultifrmRaiAlarm, or txMultifrmRaiAlarm.
Unlocked, Enabled, Busy The E1 component is in use.
(Sheet 1 of 2)
Table 110 (continued)
X21 component state combination
Combination (Administrative,
Operational, Usage)
Details
(Sheet 2 of 2)
OSI state combinations 671
Passport Operations and Maintenance Guide 4S3
Locked, Enabled, Idle A lock/lock -force operator command is in effect. The E1
component is otherwise ready to service a user. A test is
running.
Locked, Disabled, Idle Some hardware test failed or
the E1 component has been put in the Locked state by the
operator or
external factors render the E1 port inoperable.
Table 113
DS1 component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the DS1 port inoperable because of
detection and declaration of at least one of the following alarms:
losAlarm, lofAlarm, rxAisAlarm.
Unlocked, Enabled, Busy The DS1 component is in use.
Locked, Enabled, Idle A lock/lock operator command is in effect. The DS1 component
is otherwise ready to service a user. A test is running
Locked, Disabled, Idle Some hardware test failed or
the DS1 component has been put in the Locked state by the
operator or
external factors render the DS1 port inoperable.
Table 112 (continued)
E1 component state combination
Combination (Administrative,
Operational, Usage)
Details
(Sheet 2 of 2)
672 Appendix
241-7001-150 4S3
Table 114
DS1 Voice and E1 Voice Channel (Chan) component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the CHAN component inoperable
because of DS1 or E1 alarms.
Unlocked, Enabled, Idle Not in use. The CHAN component is being provisioned, waiting
for binding from an application.
Unlocked, Enabled, Busy The CHAN component is in use. The CHAN component can
only service one user at a time.
Locked, Enabled, Idle A lock/lock operator command is in effect. The CHAN
component is otherwise ready to service a user. A test is
running.
Locked, Disabled, Idle Some hardware test failed or the CHAN component has been
put in the Locked state by the operator.
Table 115
DS1 Voice and E1 Voice Test component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle The hardware component is unlocked. No resource is available
to the Test component. Start test requests will be rejected.
Unlocked, Enabled, Busy The TEST component is in use. A TEST component is created
by a V35, X21, DS1, E1, CHAN, DS3, or E3 component and only
services that particular component. A test is terminated either
when the prescribed timer expires or a stop test command is
issued by the operator.
OSI state combinations 673
Passport Operations and Maintenance Guide 4S3
J2MV
Table 116
DS1 Voice and E1 Voice Framer component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle A component that the FRAMER component depends on is not
available. A likely cause is that the port component (for example,
a V35 component) is locked for testing.
Unlocked, Enabled, Busy The FRAMER component is in use. The FRAMER component
services only one user (an application component) at a time.
Table 117
J2MV E1 component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the E1 port inoperable because of
detection and declaration of at least one of the following alarms:
losAlarm, lofAlarm, rxAisAlarm, multifrmLofAlarm,
rxMultifrmRaiAlarm, or txMultifrmRaiAlarm.
Unlocked, Enabled, Busy The E1 component is in use.
Locked, Enabled, Idle A lock/lock -force operator command is in effect. The E1
component is otherwise ready to service a user. A test is
running.
Locked, Disabled, Idle Some hardware test failed or
the E1 component has been put in the Locked state by the
operator or
external factors render the E1 port inoperable.
674 Appendix
241-7001-150 4S3
Table 118
J2MV Channel (Chan) component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the CHAN component inoperable
because of E1 alarms.
Unlocked, Enabled, Idle Not in use. The CHAN component is being provisioned, waiting
for binding from an application.
Unlocked, Enabled, Busy The CHAN component is in use. The CHAN component can
only service one user at a time.
Locked, Enabled, Idle A lock/lock operator command is in effect. The CHAN
component is otherwise ready to service a user. A test is
running.
Locked, Disabled, Idle Some hardware test failed or the CHAN component has been
put in the Locked state by the operator.
Table 119
J2MV Test component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle The hardware component is unlocked. No resource is available
to the Test component. Start test requests will be rejected.
Unlocked, Enabled, Busy The TEST component is in use. A TEST component is created
by a V35, X21, DS1, E1, CHAN, DS3, or E3 component and only
services that particular component. A test is terminated either
when the prescribed timer expires or a stop test command is
issued by the operator.
OSI state combinations 675
Passport Operations and Maintenance Guide 4S3
DS3 and E3
Table 120
DS3 component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the DS3 interface inoperable because of
detection and declaration of at least one of the following alarms:
losAlarm, lofAlarm, rxAisAlarm, rxRaiAlarm, or the interface is
being requested to loop back the incoming signal by the far DS3
interface.
Unlocked, Enabled, Idle The component is not in use. Being provisioned, waiting for
binding. The line input has been recognized as good. Clocks are
available.
Unlocked, Enabled, Busy The DS3 component is in use. The DS3 component services
only one user (a FRAMER component) at a time.
Locked, Enabled, Idle A port and line test is in progress.
Locked, Disabled, Idle Some hardware test failed and the DS3 component has been
put in the Locked state by the operator.
A lock/lock operator command is in effect.
Table 121
E3 component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the E3 interface inoperable because of
detection and declaration of at least one of the following alarms:
losAlarm, lofAlarm, rxAisAlarm, rxRaiAlarm, or the interface is
being requested to loop back the incoming signal by the far E3
interface.
Unlocked, Enabled, Idle The component is not in use. Being provisioned, waiting for
binding. The line input has been recognized as good. Clocks are
available.
(Sheet 1 of 2)
676 Appendix
241-7001-150 4S3
Unlocked, Enabled, Busy The E3 component is in use. The E3 component services only
one user (a FRAMER component) at a time.
Locked, Enabled, Idle A port and line test is in progress.
Locked, Disabled, Idle Some hardware test failed and the E3 component has been put
in the Locked state by the operator.
A lock/lock operator command is in effect.
Table 122
DS3 and E3 Test component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle The hardware component is unlocked. No resource is available
to the Test component. Start test requests will be rejected.
Unlocked, Enabled, Busy The TEST component is in use. A TEST component is created
by a V35, X21, DS1, E1, CHAN, DS3, or E3 component and only
services that particular component. A test is terminated either
when the prescribed timer expires or a stop test command is
issued by the operator.
Table 121 (continued)
E3 component state combination
Combination (Administrative,
Operational, Usage)
Details
(Sheet 2 of 2)
OSI state combinations 677
Passport Operations and Maintenance Guide 4S3
DS3 ATM and E3 ATM
Table 123
DS3 component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the DS3 interface inoperable through
condition detection and declaration of at least one of the
following alarms: losAlarm, lofAlarm, rxAisAlarm, rxRaiAlarm,
lcdAlarm, rxIdle.
Or through the detection of a request command by the far DS3
interface to loop back the incoming signal.
When the PLCP option is turned on, PLCP lofAlarm and PLCP
rxRaiAlarm also cause the component to go disabled.
Unlocked, Enabled, Idle The component is not in use. Being provisioned, waiting for
binding. The line input has been recognized as good. Clocks are
available.
Unlocked, Enabled, Busy The DS3 component is in use. The DS3 component services
only one user (an ATM interface component) at a time.
Unlocked, Enabled,
Shutting Down
A lock command has been issued against the DS3 component
which is waiting for the ATM interface component to go into a
disabled mode before the DS3 component completes the lock
sequence and shuts down.
Locked, Enabled, Idle A lock operator command is in effect and the DS3 component is
operating in test mode (availabilityStatus: inTest).
Locked, Disabled, Idle A lock operator command is in effect and the component is in
one of the following conditions:
Left ofine (availabilityStatus: ofine)
Some hardware test failed (availabilityStatus: failed)
If running in test mode external factors will cause errors
(availabilityStatus: inTest). Bad line state and excessive line
state changes are possible causes.
678 Appendix
241-7001-150 4S3
Table 124
E3 component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the E3 interface inoperable through
condition detection and declaration of at least one of the
following alarms: losAlarm, lofAlarm, rxAisAlarm, rxRaiAlarm,
lcdAlarm.
When the PLCP option is turned on, PLCP lofAlarm and PLCP
rxRaiAlarm also cause the component to go disabled.
Unlocked, Enabled, Idle The component is not in use. Being provisioned, waiting for
binding. The line input has been recognized as good. Clocks are
available.
Unlocked, Enabled, Busy The E3 component is in use. The E3 component services only
one user (an ATM Interface component) at a time.
Unlocked, Enabled,
Shutting Down
A lock command has been issued against the E3 component
which is waiting for the ATM interface component to go into a
disabled mode before the E3 component completes the lock
sequence and shuts down.
Locked, Enabled, Idle A lock operator command is in effect and the E3 component is
operating in test mode (availabilityStatus: inTest).
Locked, Disabled, Idle A lock operator command is in effect and the component is in
one of the following conditions:
Left ofine (availabilityStatus: ofine)
Some hardware test failed (availabilityStatus: failed)
If running in test mode external factors will cause errors
(availabilityStatus: inTest). Bad line state and excessive line
state changes are possible causes.
OSI state combinations 679
Passport Operations and Maintenance Guide 4S3
JT2 ATM
Table 125
DS3 ATM and E3 ATM Test component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle The hardware component is unlocked. No resource is available
to the Test component. Start test requests will be rejected.
Unlocked, Enabled, Idle The hardware component is locked. A port and line test can be
performed.
Unlocked, Enabled, Busy The TEST component is in use. A TEST component is created
by a CHAN, DS1, E1, DS3, E3, V35, X21, Sonet, or Sdh
component and only services that particular component. A test
is terminated either when the prescribed timer expires or a stop
test command is issued by the operator.
Table 126
JT2 component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the JT2 interface inoperable through
condition detection and declaration of at least one of the
following alarms: losAlarm, lofAlarm, rxAisPhysicalAlarm,
rxAisPayloadAlarm, rxRaiAlarm, lcdAlarm.
Unlocked, Enabled, Idle The component is not in use. Being provisioned, waiting for
binding. The line input has been recognized as good. Clocks are
available.
Unlocked, Enabled, Busy The JT2 component is in use. The JT2 component services only
one user (an ATM interface component) at a time.
ShuttingDown, Enabled, Busy A lock command has been issued against the JT2 component
which is waiting for the ATM interface component to go into a
disabled mode before the JT2 component completes the lock
sequence and shuts down.
(Sheet 1 of 2)
680 Appendix
241-7001-150 4S3
Locked, Enabled, Idle A lock operator command is in effect and the JT2 component is
operating in test mode (availabilityStatus: inTest).
Locked, Disabled, Idle A lock operator command is in effect and the component is in
one of the following conditions:
Left ofine (availabilityStatus: ofine)
Some hardware test failed (availabilityStatus: failed)
If running in test mode external factors will cause errors
(availabilityStatus: inTest). Bad line state and excessive line
state changes are possible causes.
Table 127
JT2 ATM Test component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle The hardware component is unlocked. No resource is available
to the Test component. Start test requests will be rejected.
Unlocked, Enabled, Idle The hardware component is locked. A port and line test can be
performed.
Unlocked, Enabled, Busy The TEST component is in use. A TEST component is created
by a JT2 component and only services that particular
component. A test is terminated either when the prescribed timer
expires or a stop test command is issued by the operator.
Table 126 (continued)
JT2 component state combination
Combination (Administrative,
Operational, Usage)
Details
(Sheet 2 of 2)
OSI state combinations 681
Passport Operations and Maintenance Guide 4S3
DS1C and E1C
Table 128
E1 component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the E1 port inoperable because of
detection and declaration of at least one of the following alarms:
losAlarm, lofAlarm, rxAisAlarm, multifrmLofAlarm,
rxMultifrmRaiAlarm, or txMultifrmRaiAlarm.
Unlocked, Enabled, Busy The E1 component is in use.
Locked, Enabled, Idle A lock/lock operator command is in effect. The E1 component is
otherwise ready to service a user. A test is running.
Locked, Disabled, Idle Some hardware test failed or
the E1 component has been put in the Locked state by the
operator or
external factors render the E1 port inoperable.
Table 129
DS1 component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the DS1 port inoperable because of
detection and declaration of at least one of the following alarms:
losAlarm, lofAlarm, rxAisAlarm.
Unlocked, Enabled, Busy The DS1 component is in use.
Locked, Enabled, Idle A lock/lock operator command is in effect. The DS1 component
is otherwise ready to service a user. A test is running.
Locked, Disabled, Idle Some hardware test failed or
the DS1 component has been put in the Locked state by the
operator or
external factors render the DS1 port inoperable.
682 Appendix
241-7001-150 4S3
Table 130
DS1C and E1C Channel (Chan) component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the CHAN component inoperable
because of DS1 or E1 alarms.
Unlocked, Enabled, Idle Not in use. The CHAN component is being provisioned, waiting
for binding from an application.
Unlocked, Enabled, Busy The CHAN component is in use. The CHAN component can
only service one user at a time.
Locked, Enabled, Idle A lock/lock -force operator command is in effect. The CHAN
component is otherwise ready to service a user. A test is
running.
Locked, Disabled, Idle Some hardware test failed or
the CHAN component has been put in the Locked state by
the operator or
external factors render the DS1 or E1 port inoperable.
Table 131
DS1C and E1C Test component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle The hardware component is unlocked. No resource is available
to the Test component. Start test requests will be rejected.
Unlocked, Enabled, Busy The TEST component is in use. A TEST component is created
by a V35, X21, DS1, E1, CHAN, DS3, or E3 component and only
services that particular component. A test is terminated either
when the prescribed timer expires or a stop test command is
issued by the operator.
OSI state combinations 683
Passport Operations and Maintenance Guide 4S3
OC3
Table 132
OC3 Sonet/Sdh component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the Sonet/Sdh interface inoperable
through condition detection and declaration of at least one of the
following alarms: losAlarm, lofAlarm, rxAisAlarm, rxRfiAlarm,
lcdAlarm.
Unlocked, Enabled, Idle The component is not in use. Being provisioned, waiting for
binding. The line input has been recognized as good. Clocks are
available.
Unlocked, Enabled, Busy The Sonet/Sdh component is in use. The Sonet/Sdh component
has one Path component under it.
Unlocked, Enabled,
Shutting Down
A lock command has been issued against the Sonet/Sdh
component but the Path component under it is not yet
suspended.
Locked, Enabled, Idle A lock operator command is in effect and the Sonet/Sdh
component is operating in test mode (availabilityStatus: inTest).
Locked, Disabled, Idle A lock operator command is in effect and the component is in
one of the following conditions:
Left ofine (availabilityStatus: ofine)
Some hardware test failed (availabilityStatus: failed)
If running in test mode external factors will cause errors
(availabilityStatus: inTest). Bad line state and excessive line
state changes are possible causes.
684 Appendix
241-7001-150 4S3
Table 133
OC3 Test component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle The hardware component is unlocked. No resource is available
to the Test component. Start test requests will be rejected.
Unlocked, Enabled, Idle The hardware component is locked. A port and line test can be
performed.
Unlocked, Enabled, Busy The TEST component is in use. A TEST component is created
by a CHAN, DS1, E1, DS3, E3, V35, X21, Sonet, or Sdh
component and only services that particular component. A test
is terminated either when the prescribed timer expires or a stop
test command is issued by the operator.
Table 134
OC3 Path component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle External factors render the Path component inoperable because
of detection and declaration of at least one of the following
alarms: lopAlarm, rxAisAlarm, rxRfiAlarm,
signalLabelMismatch. Either a bad path state or the Sonet/Sdh
is disabled. If the Sonet/Sdh is disabled either Sonet/Sdh is
locked or there is a bad Sonet/Sdh signal.
Unlocked, Enabled, Idle Not in use. Waiting for a binding to an ATM interface component.
Unlocked, Enabled, Busy The Path component is in use. The Path component services
only one user (an ATM interface component) at a time.
Unlocked, Enabled,
Shutting Down
A lock command has been issued against the Path component
which is waiting for the ATM interface component to go into a
disabled mode before the Path component completes the lock
sequence and shuts down.
Locked, Disabled, Idle A Lock operator command is in effect.
OSI state combinations 685
Passport Operations and Maintenance Guide 4S3
FDDI
Ethernet
Table 135
FDDI (FI) component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle The component is disabled due to a broken physical
disconnection, bad line state, etc.
Unlocked, Enabled, Idle The component is not in use, waiting to bind to the framer.
Unlocked, Enabled, Busy The component is in use. The FDDI component can only service
one framer component at a time, therefore, no usage states are
active.
Shutting Down, Enabled, Busy The component is going from the unlocked to the locked state. It
is in the process of gracefully shutting down and breaking the
link to the framer component.
Locked, Enabled, Idle A lock command is in effect. The component could be put into
test mode.
Locked, Disabled, Idle A hardware test failed or a physical connection was broken while
in the locked state.
Table 136
Ethernet (en) component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle The component is disabled due to a broken physical
disconnection, bad line state, etc.
Unlocked, Enabled, Idle The component is not in use, waiting to bind to the framer.
Unlocked, Enabled, Busy The component is in use. This component can only service one
framer component at a time therefore no usage states are
active.
Shutting Down, Enabled, Busy The component is going from the unlocked to the locked state. It
is in the process of gracefully shutting down and breaking the
link to the framer component.
(Sheet 1 of 2)
686 Appendix
241-7001-150 4S3
Token Ring
Locked, Enabled, Idle A lock command is in effect. The component could be put into
test mode.
Locked, Disabled, Idle A hardware test failed or a physical connection was broken while
in the locked state.
Table 137
Token Ring component state combination
Combination (Administrative,
Operational, Usage)
Details
Unlocked, Disabled, Idle The component is disabled due to a broken physical disconnec-
tion, bad line state, etc.
Unlocked, Enabled, Idle The component is not in use, waiting to bind to the framer
Unlocked, Enabled, Busy The component is in use. This token ring component can only
service one framer component at a time therefore no usage
states are active.
Shutting Down, Enabled, Busy The component is going from the unlocked to the locked state.
It is in the process of gracefully shutting down and breaking the
link to the framer component.
Locked, Enabled, Idle A lock command is in effect. The component could be put into
test mode.
Locked, Disabled, Idle A hardware test failed or a physical connection was broken
while in the locked state.
Table 136 (continued)
Ethernet (en) component state combination
Combination (Administrative,
Operational, Usage)
Details
(Sheet 2 of 2)
687
Passport Operations and Maintenance Guide 4S3
A
AAL1 CES attributes
Clocking Sources 340, 365, 368
Line Length 366
lineType 365
Zero Coding 366
access
restricting 410
services 204
activate prov 99
add (a) command 70
adding
IpAccess component 213
second control processor to a single-disk
system 641
separate userid and password for alarm
collection 213
userid component 210
agent queue sizes 466
alarms 494
data 462
screens 55
application les
removing 198
application version 173
application version directory
removing 199
application version list 174
application/line scope 209
apply prov 99
Architect for Passport 373, 379, 402
ASCII text interface device 293, 297, 304,
309, 316, 320, 326, 330, 337, 345,
350, 356, 362, 373, 379, 383, 389,
396, 402
attributes 309, 320
changing 216
types 52, 65
automatic synchronization 628
B
Backspace key 54
broadcast test 583, 592
bus tap self-test 583, 590
bus tests 583, 648
displaying results 587
interpreting results 590
buses
controlling 415
determining status 431
determining which buses are in service 431
C
capability set 58
card component state combination 658
card tests 572, 648
changing the setup 574
displaying results 579
interpreting results 580
loop test 526, 527
Index
688 Index
241-7001-150 4S3
Test component 531
cards
locking and unlocking 607
provisionable attributes 181
case sensitivity rules 63
cd command 630
CD-ROM 183
changing
attributes on an existing userid 216
card test setup 574
logical processor type 608
password on an existing userid 215
processor cards software load 607
channel (Chan) component state
combination 656, 663, 666, 672, 674,
682
check prov 99
CID
See customer identier
cleaning up software les 602, 648
clear prov 99
clock source test 583, 591
Clocking Sources 340, 365, 368
commands
activate prov 103
add 70
apply prov 106
cd 630
check prov 108
clear prov 113
command forms 64
commit prov 115
component-specic 58, 60
conrm prov 117
copy 629
copy prov 119
delete 71
detailed descriptions 63
display 74, 429
end prov 122
error responses 65
format 64, 138
help 65
hints for using 62
list 72, 429
load prov 122
lock 82
mkdir 630
move 629
node monitoring 428
protect 629
provisioning system commands 59
pwd 630
quick reference 60
reloadcp 102, 606
remove 604, 629
reset 605
responses 51, 430
restart 606
rtg dpn ping 446
save prov 124
set 68
start prov 127
switchover 607, 640
syntax conventions 64
tidy 602
tidy prov 130
touch 630
unlock 83
unprotect 630
VC ping 452
commit prov 99
component control 407
buses 415
cards 414
data collection system 417
disks 420
locking a card 415
locking a logical processor 413
locking and unlocking an interface 412
network management interface system 409
ports 421
Index 689
Passport Operations and Maintenance Guide 4S3
prerequisites 409
procedures 408
restricting access 410
terminating a session 411
terminating multiple sessions 411
trunks 417
component states
data collection system 650
le system 650
network management interface system 655
trunk 652
components 309, 320
class 65, 139
instance 138
instance value 65
locking 408
name 65
type 65, 138
unlocking 408
conguration impact 209
conrm prov 99
control processor
adding 641
replacing 633, 640
synchronizing disk 633, 640
troubleshooting 499
control processors
provisioning 296
Control-A 54
Control-C 55
Control-D 54
Control-E 54
Control-K 54
controlling
buses 415
components 407
disks 420
logical processors and processor cards 412
network management interface system 409
ports 421
trunks 417
Control-Q 54, 55
conventions 41
copy command 629
copy prov 99
copying
existing userid for a new user 214
CP recovery
re-establishing network connection 635
reinstalling software 635
reprovisioning 636
single-CP nodes 634
current view 85, 428
customer identier 58, 205, 208, 219
D
data collection 44, 459
accounting data 461
agent queue sizes 466
alarm data 462
creating a new spooling le 464, 470
directories 465
displaying queue attributes 471
le transfer 463
lename of spooling le 473
lenames 465
logs and debug data 462
maximum number of les 467
prerequisites 460
procedures 460, 477
SCN data 462
setup and operation guidelines 460
spooling option 468
time-of-day accounting schedules 473
data collection system 203
component states 650
controlling 417
troubleshooting 521
debug impact 209
default information 48
delete (del) command 71
Delete key 54
690 Index
241-7001-150 4S3
destructive tests 594
determining
buses in service 431
card type 433
component states 409
frame relay VC path using the ping
command 452
hardware failures 431
link groups 442
memory capacity of a processor card 433
paths to nodes using the rtg dpn ping
command 446
status of a bus 431
device scope 208
diagnostic tests 407, 523
cards 573
disks 593
prerequisites 524
related documents 524
directories 465
setting up 198
software 182
UNIX 182
disabling
cards 415
trunks 418
disk
automatic synchronization 628
changing volume name 631
controlling 420
destructive tests 594
displaying information 435
displaying test results 596
formatting 632
full 630
manual synchronization 628
non-destructive tests 594
preparing for testing 421
replacing control processor 633, 640
synchronization 627
synchronization disruptions 627
synchronizing 633, 640
tests 648
using a larger active disk 642
using a larger standby disk 643
using different size disks 642
diskRead test 594
display (d) command 74
displaying
all nodes in the network 442
amount of records 471
attributes 464
bus test results 587
card test results 579
disk information 435
disk test results 596
le system information 435
lename 464
lename of the spooling le 473
Frame Relay VC round trip delay
information 454
frame relay VC round trip delay
information 453
information about a specic link group 441
information about PORS trunks 443
information about trunk groups 443
neighboring node link information 440
node identier 440
port components 434
port test results 570
provisionable attributes of port
components 434
provisioned logical processors 432
reachable DPN-100 nodes 444
routing control statistics 446
routing topology information 443
rtg dpn ping round trip delay information
451
user sessions 436
Down-Arrow 54
DPN Gateway troubleshooting 517
DPN-100 nodes
Index 691
Passport Operations and Maintenance Guide 4S3
displaying 444
DS1 component state combination 662, 664,
671, 681
DS3 component state combination 675, 677
dynamic trunk speed change 227
E
E1 component state combination 662, 665,
670, 673, 681, 686
E3 component state combination 675, 678
edit view 86, 428
end prov 99
error responses 65
Ethernet component state combination 685
External 535
external loop test 527
external loopback
Test component 535
F
FDDI component state combination 685
File Prober 464, 479
le system 627
commands 628
component states 650
displaying information 435
troubleshooting 512
lenames 465
lesystemCheck test 594
akyBitDetection test 594
FMIP interface 210
formatting a disk 632
FTP interface 210
full view 88
function processor
troubleshooting 503
function processors
attributes 309, 320
components 309, 320
provisioning 304, 309, 315, 316, 318, 325,
329, 346, 350, 352, 356, 358, 373,
378, 379, 383, 389, 396, 402, 405
testing 315, 325
H
hardware
testing 45, 315, 325
hardware failures
monitoring 431
help (h) command 65
I
impact 58, 205, 209
installation
planning 184
prerequisites 166
software 184
interfaces
allowed 210
IP address 185
IP address list 207
IP interface over Frame Relay
components and attributes 252
features 251
IP routing 254
provisioning 267
standards compliance 252
IP interface over VC
components and attributes 246
features 246
provisioning 247
IPIFR
See IP interface over Frame Relay
IPIVC
See IP interface over VC
J
JT2 component state combination 679
692 Index
241-7001-150 4S3
K
keyboard shortcuts 53
Backspace key 54
Control-A 54
Control-C 55
Control-D 54
Control-E 54
Control-K 54
Control-Q 55
Control-S 54
Delete key 54
Down-Arrow 54
Left-Arrow 54
Return key 54
Right-Arrow 54
Up-Arrow 54
L
LED 511
Left-Arrow 54
Line Length 366
lineType 365
link groups
determining 442
displaying information about 441
list (l) command 72
load prov 99
loading frame stream 574, 581
local loop test 526, 527, 573
local operator
interface 210
security 210
local test
HSSI 532
Test component 531
X21 (V11) 531
lock command 82
locking a card component 414
locking and unlocking processor cards 607
logging of operator commands 210
logical processor types 179, 607
adding more features 609
provisionable attributes 181
removing features 610
logical processors 179, 412, 607
cards 412
controlling 412
deleting 608
modifying 608
provisionable attributes 181
re-enabling 414
status 432
logical processors, provisioning 318, 346,
352, 358
LogicalProcessor (LP) component state
combination 659
login 210
logs 463
LP 383, 385, 387, 394, 400
LP restart capability
status 432
LPT 385
M
Magellan data collection system
File Prober 479
Magellan Data Provider 478
Network Engineering host 481
Passport 478
Magellan Data Provider 478
maintenance
hardware 648
scheduled activities 647
software 647
manual loop test 526, 527, 572
Test component 532
manual synchronization 628
MDP
See Magellan Data Provider
mkdir command 630
module-wide data 234
Index 693
Passport Operations and Maintenance Guide 4S3
monitoring
bus status 431
buses 431
card types 433
commands 428
hardware failures 431
logical processor status 432
LP restart capability 432
network management systems 435
node 45, 425
number of user sessions 436
port components 434
provisioned logical processors 432
routing system 437
shelf management systems 431
move command 629
N
Network Engineering host 481
network management connectivity 237
network management interface system
component states 655
controlling 409
network scope 208
network time
setting 643
New processor cards and ports
provisioning with Architect for
Passport 308
NMS workstation command console 375, 380,
402
node identier 202
displaying 440
provisioning 220
node link information
displaying 440
node maintenance 45
node monitoring 45, 425
network management system 435
node name 202
provisioning 220
node outage
troubleshooting 498
node provisioning 44, 217
IP interface over Frame Relay 250
IP interface over VC 246
node name and identier 220
prerequisites 219
procedures 217
related documents 217
topology component 234
node security 205
non-destructive tests 594
O
operating modes 428
operational mode 48, 59
default information 48
operations and maintenance denition 44
operator
commands 57
modes 59
OSI states 430, 649
determining component states 409
P
partial view 88
passive impact 209
Passport 478
Passport views 85
password
attribute 208
changing 215
payload loopback
Test component 535
ping
rtg dpn command 446
test 584, 593
VC command 452
port management system component
states 656, 661
694 Index
241-7001-150 4S3
port tests 526
displaying results 570
interpreting results 572
manual loop test 532
ports
controlling 421
preparing for testing 423
provisioning 318, 346, 352, 358
tests 648
prerequisites
for provisioning cards 293, 396
prompt 48
protect command 629
provisioning 315, 325
after StartUp 202
disk les 87
DPN Gateway 219
external address plan 218
fundamentals 85, 137
impact 102
initial steps 201
IP interface over Frame Relay 267
IP interface over VC 235, 247
module-wide data 234
node 44, 217
node name and identier 220
related documents 85
scope 102
trunks 224
provisioning cards 304, 309, 316, 329, 350,
356, 373, 378, 379, 383, 389, 396,
402, 405
provisioning mode 48, 59
default information 48
provisioning new cards and ports
with Architect for Passport 308
provisioning new cards, LPs, and ports 306,
327
provisioning system commands 98
pwd command 630
R
re-enabling
cards 415
trunks 419
releasing a locked interface 412
reloadcp command 606
reloading processor cards 606
remote loop test 526, 527, 573
remote test
DS1 533
DS3 534
Test component 533
X21 (V11) 534
remove command 604, 629
reset command 605
resetting
agent queue sizes 466
maximum number of les to be kept on
disk 467
processor cards 605
restart command 606
restricting access though a specied
interface 410
Return key 54
Right-Arrow 54
routing control statistics
displaying 446
routing system monitoring 437
routing topology
displaying information about 443
S
save prov 99
saved view 86
saved views
le naming 91
full 88
partial 88
SCN data 462
scope 58, 205, 208
Index 695
Passport Operations and Maintenance Guide 4S3
security 205
adding a userid component 210
copying an existing userid 214
features 207
login 210
prerequisites for conguring 206
procedures 206
userid attributes 207
valid IP address list 207
serial port loopbacks
external 535
payload 535
serial port tests
card 531
local 531
manual 532
remote 533
service impact 209
set (s) command 68
setting up
spooling option 468
time-of-day accounting schedule 473
shelf management 599
changing an LPT 608
le system 627
provisioning procedures 600
setting network time 643
shelf management system
component states 658
monitoring 431
software
adding 198
application version 173
application version list 174
cleaning up les 602
determining status 186, 188
directory 182
directory structure 176, 178
downloading 189
feature list upgrades 601
hierarchy 175
installation 184
installing on software distribution site 183
management 601
on CD-ROM 183
partitioning 172
removing 198
transferring to software distribution
site 182
version upgrades 601
software distribution site 169, 181
removing les 199
transferring les to 182
userids 182
Sonet/SDH component state combination 683
spooling
checking 647
creating a new le 464, 470
setting up 468
start prov 100, 127
statistics
by component 482
collection 478
generation on-switch 481
provisioning 491
setting up 489
status display LED 511
stop prov 100
surface analysis test 594
switchover command 607, 640
synchronization
automatic 628
checking 647
disks 631
manual 628
network time 643
syntax
error 53
errors 67
system administration impact 209
696 Index
241-7001-150 4S3
T
Telnet interface 210
test component state combination 657, 664,
667, 668, 670, 672, 674, 676, 679,
680, 682, 684
testing
cards 295, 304, 308, 320, 329, 336, 345,
349, 356, 361, 378, 383, 389, 396,
402, 405
testing cards 373
tests
broadcast 583, 592
bus 583, 648
bus tap self-test 583, 590
card 573, 648
card loop 526, 527
clock source 583, 591
diagnostic 523
disk 593, 648
diskRead 594
external loop 527
lesystemCheck 594
akyBitDetection 594
function processors 315, 325
hardware 45
local loop 526, 527
manual loop 526, 527
non-destructuve 594
ping 584, 593
port 648
remote loop 526, 527
surface analysis 594
text interface 47
alarm format 55
alarm screens 55
command screens 49
prompt 48
screens 48
text interface device 293, 297, 304, 309, 316,
320, 326, 330, 337, 345, 350, 356,
362, 373, 375, 379, 380, 383, 389,
396, 402
tidy command 602
tidy prov 100
time-of-day accounting 473, 647
topology component state combination 653
touch command 630
Trace System, Passport 497
transport resource manager component state
combination 653
troubleshooting 493
alarm cutoff 495
control processor 499
data collection system 521
DPN Gateway 517
le system 512
function processor 503
general 497
node outage 498
trunks 514
trunk component states 652
trunks
controlling 417
disabling 418
displaying information about 443
displaying PORS information 443
provisioning 224
re-enabling 419
troubleshooting 514
U
UNIX directories and les 182
unlock command 83
unprotect command 630
Up-Arrow 54
user sessions
determining number 436
terminating 411
userids
adding 210
attributes 207
for software distribution site 182
Index 697
Passport Operations and Maintenance Guide 4S3
querying 437
V
V54 remote loopback test 527, 557, 560
verbs
abbreviations 62
options 65, 138
verication frame stream 582
verication stream 574
views 428
current 85, 428
edit 86, 428
save 86
understanding 85
virtual circuit recovery 456
virtual router
ethernet card provisioning 388
FDDI function processor provisioning 395
ILS network management 284292
token ring card provisioning 401
volume name of a disk
changing 631
W
workstation 183
X
X21 component state combination 669
Z
Zero Coding 366
698 Index
241-7001-150 4S3
Passport
Operations and Maintenance
Guide
Release 4.2
Address comments to:
Senior Manager, EDN Product Documentation
Northern Telecom
PO Box 3511 Station C
Ottawa ON K1Y 4H7
Canada
1998 Northern Telecom
Nortel, Magellan, DPN, and Passport are trademarks of Northern
Telecom.
Sun is a trademark of Sun Microsystems Incorporated.
UNIX is a trademark of Novell Incorporated.
IBM is a trademark of International Business Machines Corporation.
Publication: 241-7001-150
Document status: Standard
Document version: 4S3
Document date: May 1998
Printed in Canada