297-5061-901

Wireless Networks Family

SuperNode Data Manager
User Guide

SDMPL011 Standard 01.01 December 1998

Wireless Networks Family

SuperNode Data Manager

User Guide

Publication number: 297-5061-901

Product release: SDMPL011
Document release: Standard 01.01
Date: December 1998

 1998 Northern Telecom

All rights reserved

Printed in the United States of America

NORTHERN TELECOM CONFIDENTIAL: The information contained in this document is the property of Northern
Telecom. Except as specifically authorized in writing by Northern Telecom, the holder of this document shall keep the
information contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to third
parties and use same for evaluation, operation, and maintenance purposes only.

Information is subject to change without notice. Northern Telecom reserves the right to make changes in design or components
as progress in engineering and manufacturing may warrant.
This equipment has been tested and found to comply with the limits for a Class A digital device pursuant to Part 15 of the FCC
Rules, and the radio interference regulations of the Canadian Department of Communications. These limits are designed to
provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This
equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the in-
struction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is
likely to cause harmful interference in which case the user will be required to correct the interference at the user’s own expense
Allowing this equipment to be operated in such a manner as to not provide for proper answer supervision is a violation of Part
68 of FCC Rules, Docket No. 89-114, 55FR46066

DMS, DMS SuperNode, and MAP are trademarks of Nortel. HP, HP-UX, and HP9000 are trademarks of Hewlett-Packard
Company. OSF DCE is a trademark of Open Software Foundation, Inc. UNIX is a trademark licensed exclusively through
X/Open Company Ltd. Sun and SPARC are trademarks of Sun Microsystems, Inc. VT100 is a trademark of Digital Equipment
Corporation. Ethernet is a trademark of Xerox Corporation. AIX and IBM are trademarks of International Business Machines
Corporation. Motorola is a trademark of Motorola, Inc.

Wireless Networks Family SDM–SX User Guide SDMPL011

 iii

Publication history
December 1998
SDMPL011 Standard 01.01. First release of this document.

Wireless Networks Family SDM–SX User Guide SDMPL011

 v

Contents
About this document xiii
When to use this document xiii
How to check the version and issue of this document xiii
References in this document xiii
What precautionary messages mean xiv
How commands, parameters, and responses are presented xv
Input prompt (>) xv
Commands and fixed parameters xv
Variables xv
Multiple keystrokes xvi
Responses xvi

Understanding the SDM-SX 1-1

SDM overview 1-1
SDM hardware 1-3
SDM cabinet 1-4
Modular supervisory panel 1-5
Fan unit 1-5
Front-mounted SDM main chassis hardware 1-5
Rear-mounted SDM main chassis hardware 1-12
Additional provisionable hardware 1-17
SDM software 1-19
SDM base software layer 1-19
SDM service software layer 1-19
SDM application software layer 1-19
Maintenance interfaces 1-20
Administration functions 1-21
LAN-based I/O interface capabilities 1-22
Workstations 1-22
Hubs 1-23
Routers 1-23
Terminal servers 1-24
SDM Log Delivery 1-24
Logreceiver tool 1-25
Log formatting 1-26
Log buffering 1-26
Log delivery commissioning tool (logroute) 1-26
SDM maintenance overview 2-1
SDM monitoring and maintenance positions 2-1

Wireless Networks Family SDM–SX User Guide SDMPL011

vi Contents

Maintaining the SDM using the MAP interface 2-2

Determining the SDM node state at the MAP display 2-3
Using SDM commands at the MAP display 2-7
Monitoring SDM-related alarms at the MAP display 2-19
Logging in to the SDM 2-22
Root user login 2-23
Maint user login 2-23
Return key and Enter key 2-24
Restricted shell 2-25
Restricted shell commands 2-25
Node and application control commands 2-29
Maintaining the SDM using the remote maintenance interface 2-34
Accessing the remote maintenance interface 2-35
Static and dynamic information 2-39
Using the RMI menu system 2-39
Top menu level of the RMI 2-41
Monitoring SDM status and alarms at the RMI 2-42
Maintenance menu level of the RMI 2-46
Connectivity menu level of the RMI 2-49
LAN menu level of the RMI 2-53
Application menu level of the RMI 2-56
System menu level of the RMI 2-60
Hardware menu level of the RMI 2-68
QuerySDM STATUS command 2-71
QuerySDM FLT command 2-72
QuerySDM LOADS command 2-73
QuerySDM CONFIG command 2-75
Locate command 2-76
SDM log reports 2-77
SDM logs 2-77
SDM Log Delivery application 2-81
Logreceiver tool 2-82
Log Delivery commissioning 2-84
Log Delivery device commissioning list 2-85
Log Delivery global commissioning parameters 2-89
Log Delivery CM configuration file commissioning parameters 2-90
Troubleshooting Log Delivery problems 2-91
SDM troubleshooting strategy 2-92
Fault reporting 2-92
Hardware LED status indicators 2-94
State mismatches between the CM and the SDM 2-101
Routine maintenance recommendations 2-104
Maintenance user tasks 2-104
Root user tasks 2-104

SDM system administration overview 3-1

Commissioning SDM software 3-1
Using the SDM commissioning tool 3-2
Log Delivery commissioning parameters 3-4
Administering the SDM using the remote maintenance interface 3-4
Administration menu level of the RMI 3-6

297-5061-901 Standard 01.01 December 1998

 Contents vii

Time and date administration 3-7

User and class administration 3-8
User menu of the RMI 3-9
Software and data backups 3-11
System image backup 3-13
Restoring SDM software and data 3-14
Using the Software Inventory Manger (SWIM) 3-15
About filesets and software states 3-16
Using the Filter command to change the view of the SWIM menu 3-17
Installing new software 3-18
Updating existing software 3-19
Removing Existing Software 3-19
Viewing history information 3-20
Changing default values 3-21
Configuring software 3-22
Enabling and disabling FTP and telnet access 3-23
Upgrading CPU controller modules 3-25
Hardware upgrades 3-25
DCE overview 3-26
DCE cell configuration and maintenance 3-26
Setting up a DCE installation 3-29
DCE commands and status 3-31
Access to DCE-based applications across a firewall 3-32
Adding and removing port restrictions 3-32
Executing SDM-specific DCE commands on other machines 3-32
Invoking DCE-based applications 3-33
DCE application servers after an SDM restore 3-34
DCE problems requiring manual intervention 3-35

SDM maintenance procedures 4-1

Introduction to SDM maintenance procedures 4-1
Explanatory and context-setting information 4-1
Summary flowchart 4-1
Step-action instructions 4-1
Return key and Enter key 4-2

Wireless Networks Family SDM–SX User Guide SDMPL011

viii Contents

Clearing MAP alarms triggered by the SDM APPL SDM minor 4-3
Clearing MAP alarms triggered by the SDM APPL SDM critical 4-25
Clearing MAP alarms triggered by the SDM Ext FSP major 4-44
Cleaning the SDM DAT drive 4-50
Controlling SDM applications 4-54
Adding I/O controller modules 4-59
Removing I/O controller modules 4-67
Establishing a modem connection 4-79
Log Delivery device commissioning 4-84
Log Delivery global parameters commissioning 4-107
Log Delivery CM configuration file commissioning 4-117
Migration from a rootvg system to a rootvg/datavg system 4-127
Creating a logical volume in the data volume group 4-131
Increasing the size of a logical volume 4-135
Changing system thresholds 4-140
Changing logical volume thresholds 4-144
Changing the time interval for performance log SDM620 4-148

SDM hardware replacement procedures 5-1

Introduction to SDM hardware replacement procedures 5-1
Explanatory and context-setting information 5-1
Summary flowchart 5-1
Step-action instructions 5-2
Return key and Enter key 5-2
NTRX50FD CPU personality module 5-3
NTRX50FE, NTRX50FF Fan tray 5-10
NTRX50FG Interconnect module 0 5-19
NTRX50FH Interconnect module 1 5-26
NTRX50CF, NTRX50CG CPU controller module 5-34
NTRX50GN I/O controller module 5-49
NTRX50GP I/O controller module 5-59
NTRX50FS LAN personality module 5-70
NTRX50GA, NTRX50GX DS512 controller module 5-83
NTRX50GH DS512 personality module 5-96

SDM system administration procedures 6-1

Introduction to SDM system administration procedures 6-1
Explanatory and context-setting information 6-1
Summary flowchart 6-1
Step-action instructions 6-1
Return key and Enter key 6-2

297-5061-901 Standard 01.01 December 1998

 Contents ix

Changing a user password 6-3

Adding or removing a maintenance user 6-10
Setting the time zone, date and time 6-18
Creating SDM backup tapes System image backup (S-tape) 6-26
Restoring the SDM Full restore from S-tape 6-35
Changing the root user password when it is not known 6-43
Restoring the SDM Partial restore from the system image tape (S-tape) 6-49
Installing the logreceiver tool 6-57
Distributed Computing Environment Configuring an SDM in a DCE cell 6-61
Distributed Computing Environment Removing an SDM from a DCE cell 6-74
Distributed Computing Environment Creating a DCE user 6-81
Distributed Computing Environment Changing a DCE user password 6-85
Distributed Computing Environment Deleting a DCE user 6-89
Distributed Computing Environment Configuring or reconfiguring a node within a
DCE cell 6-92
Distributed Computing Environment Viewing the dcemonitor status file 6-97
Distributed Computing Environment Shutting down the master server 6-100
Distributed Computing Environment Disabling and enabling dcemonitor 6-106
Distributed Computing Environment Restricting ports to an SDM-defined range
6-110
Distributed Computing Environment Removing port restrictions 6-115
Distributed Computing Environment Restricting ports to a specific range 6-120

SDM commissioning procedures 7-1

Accessing the SDM commissioning tool 7-1
Performing tasks with the SDM commissioning tool 7-1
Commissioning tool procedures 7-2
Manual commissioning input requirements 7-2
Starting the commissioning tool 7-4
Commissioning CM-SDM connectivity 7-9
Commissioning LAN connectivity 7-15
Commissioning LAN nodes 7-22
Commissioning LAN security 7-30
Configuring DCE 7-35
Commissioning miscellaneous items: login greeting and passwords 7-42
Commissioning miscellaneous items: date, time, and time zone 7-48

SDM hardware upgrade procedures 8-1

Explanatory and context-setting information 8-1
Summary flowchart 8-1
Step-action instructions 8-1
Return key and Enter key 8-1
Upgrading the DS512 controller module from NTRX50GA to NTRX50GX 8-3
Upgrading the CPU controller module NTRX50CF 8-16
Upgrading the SDM to an FT system 8-29

List of terms 9-1

Index 10-1
Figures

Wireless Networks Family SDM–SX User Guide SDMPL011

x Contents

SDM position in the DMS SuperNode system 1-2

Front view of SDM cabinet 1-3
Front view of the main chassis 1-6
Front view of the main chassis by slot number 1-7
Module slot number layout 1-8
Controller module LEDs 1-11
Fan tray LEDs on the main chassis 1-12
Rear view of the main chassis 1-13
Rear view of the main chassis by slot number 1-14
Rear view of the interconnect modules 1-16
SDM MAP level 2-3
SDM alarms on the Maintenance banner 2-19
Maint user login 2-24
SDM restricted shell screen 2-25
RMI maintenance levels 2-35
DCE login window 2-37
Enhanced Terminal Access window 2-38
Top menu level of the RMI 2-41
Maintenance menu level 2-46
Connectivity menu level 2-50
Logs at the connectivity menu level 2-51
QuerySDM at the connectivity menu level 2-52
LAN menu level of the RMI 2-53
Logs at the LAN menu level 2-54
QuerySDM at the LAN menu level 2-55
Application menu level 2-57
Logs at the application menu level 2-58
QuerySDM at the application menu level 2-59
System menu level 2-61
Logs at the system menu level 2-62
Storage menu level 2-64
QuerySDM at the system menu level 2-67
Hardware menu level 2-68
Logs at the hardware menu level 2-69
QuerySDM at the hardware menu level 2-70
QuerySDM STATUS command 2-72
QuerySDM FLT command 2-73
QuerySDM LOADS command 2-74
QuerySDM CONFIG command 2-75
Locate command 2-76
Log Delivery commissioning tool 2-85
Log Delivery device list commissioning menu 2-86
Log Delivery commissioning – TCP Device menu example 2-87
Log Delivery commissioning – File device menu example 2-88
Log Delivery global parameters commissioning menu 2-90
Log Delivery CM configuration file commissioning example 2-91
Status LEDs visible on controller modules 2-95
Status LEDs visible on interconnect modules 2-96
Fan tray LEDs 2-98
RMI administration levels 3-5

297-5061-901 Standard 01.01 December 1998

 Contents xi

Administration menu level of the RMI 3-6

User menu 3-10
Backup and Restore Main Menu 3-12
System Image Backup and Restore Menu 3-13
SWIM menu 3-16
Apply menu 3-19
History menu 3-21
Options command menu 3-22
Enabling and disabling FTP and Telnet 3-24
DCE cell configuration 3-28

Tables
SDM node state indicators at the SDM MAP level 2-4
SDM alarms at the MAP alarm banners 2-20
Node control commands 2-31
Application control commands 2-33
SDM components at the RMI 2-43
SDM state indicators at the RMI 2-47
SDM logs generated by the SDM 2-78
2-8 SDM controller module and ICM LEDs 2-96
2-9 SDM system LEDs 2-99
SDM maintenance states – MAP interface vs RMI 2-101
User class profiles 3-8
Configuration script status 3-23
DCE commands – SDM vs remote node 3-33
DCE problem text at RMI Con menu level 3-35
Problems with DCE Networks that host SDM applications 3-47

Wireless Networks Family SDM–SX User Guide SDMPL011

 xiii

About this document

When to use this document
This document contains information for administering and maintaining the
fault-tolerant SuperNode Data Manager (SDM). It is intended for SDM
system administration and maintenance personnel.

How to check the version and issue of this document

The version and issue of the document are indicated by numbers, for
example, 01.01.

The first two digits indicate the version. The version number increases each
time the document is updated to support a new software release. For
example, the first release of a document is 01.01. In the next software
release cycle, the first release of the same document is 02.01.

The second two digits indicate the issue. The issue number increases each
time the document is revised but rereleased in the same software release
cycle. For example, the second release of a document in the same software
release cycle is 01.02.

To determine which version of this document applies to the software in your

office and how documentation for your product is organized, check the
release information in DMS-100 Family Guide to Northern Telecom
Publications, 297-1001-001.

References in this document

The following documents are referred to in this document:
• DMS-100 Family Guide to Northern Telecom Publications,
297-1001-001
• DMS-100 Family Trouble Locating and Clearing Procedures,
297-xxxx-544
• DMS-100 Routine Maintenance Procedures, 297-xxxx-546
• SuperNode Data Manager Enhanced Terminal Access User Guide,
297-5061-904

Wireless Networks Family SDM–SX User Guide SDMPL011

xiv About this document

• SuperNode Data Manager Exception Reporting User Guide,

297-5061-912
• SuperNode Data Manager Secure File Transfer User Guide,
297-5061-913
• SuperNode Data Manager SuperNode Billing Application Application
Guide, 297-5051-300
• OSF DCE Command Reference, ISBN 0-13-185844-0, Release 1.1
(1995) Open Software Foundation, Inc., 11 Cambridge Center,
Cambridge, MA 02142.

What precautionary messages mean

The types of precautionary messages used in Nortel documents include
attention boxes and danger, warning, and caution messages.

An attention box identifies information that is necessary for the proper

performance of a procedure or task, or the correct interpretation of
information or data. Danger, warning, and caution messages indicate
possible risks.

Examples of the precautionary messages follow.

ATTENTION Information needed to perform a task

ATTENTION
If the unused DS-3 ports are not deprovisioned before a DS-1/VT
Mapper is installed, the DS-1 traffic will not be carried through the
DS-1/VT Mapper, even though the DS-1/VT Mapper is properly
provisioned.

DANGER Possibility of personal injury

DANGER
Risk of electrocution
Do not open the front panel of the inverter unless fuses
F1, F2, and F3 have been removed. The inverter contains
high-voltage lines. Until the fuses are removed, the
high-voltage lines are active, and you risk being
electrocuted.

WARNING Possibility of equipment damage

297-5061-901 Standard 01.01 December 1998

 About this document xv

WARNING
Damage to the backplane connector pins
Align the card before seating it, to avoid bending the
backplane connector pins. Use light thumb pressure to
align the card with the connectors. Next, use the levers on
the card to seat the card into the connectors.

CAUTION Possibility of service interruption or degradation

CAUTION
Possible loss of service
Before continuing, confirm that you are removing the card
from the inactive unit of the peripheral module.
Subscriber service will be lost if you remove a card from
the active unit.

How commands, parameters, and responses are presented

Commands, parameters, and responses in this document conform to the
following conventions.

Input prompt (>)

An input prompt (> or #) indicates that the information that follows is a
command or other required input:

>BSY

Commands and fixed parameters

Commands and fixed parameters that are entered at the MAP display are
shown in uppercase letters:

>BSY LINK

UNIX commands and fixed parameters that are entered at the SDM are
shown in lowercase and uppercase letters, depending on the UNIX syntax:

>echo $TERM

Variables
Variables are shown in lowercase letters:

>BSY CTRL ctrl_no

Wireless Networks Family SDM–SX User Guide SDMPL011

xvi About this document

The letters or numbers that the variable represents must be entered. Each
variable is explained in a list that follows the command string.

Multiple keystrokes
Multiple keystrokes, such as control character sequences, are shown
enclosed in angle brackets and separated by a dash. The following example
indicates that you hold down the control key while pressing b:

<CTRL-b>

Responses
Responses generated by the MAP display and the SDM are shown in a
different type:

FP 3 Busy CTRL 0: Command request has been submitted.

FP 3 Busy CTRL 0: Command passed.

The following excerpt from a procedure shows the command syntax used in
this document:

1 Manually busy the CTRL on the inactive plane by typing

>BSY CTRL ctrl_no
and pressing the Enter key.
where
ctrl_no is the number of the CTRL (0 or 1)
Example of a MAP response:
FP 3 Busy CTRL 0: Command request has been submitted.
FP 3 Busy CTRL 0: Command passed.

297-5061-901 Standard 01.01 December 1998

 1-1

Understanding the SDM-SX

This chapter describes the SuperNode Data Manager SX platform, as
follows:
• ”SDM overview” on page 1-1 summarizes the SDM characteristics and
capabilities.
• ”SDM hardware” on page 1-3 describes the hardware of the SDM
platform.
• ”SDM software” on page 1-19 describes the base, service, and
application software provided with the SDM platform, and the
maintenance and administration user interfaces.
• ”LAN-based I/O interface capabilities” on page 1-22 summarizes
equipment configuration capabilities and requirements for connecting
the SDM to the operating company local area network (LAN).
• ”SDM Log Delivery” on page 1-24 describes the SDM Log Delivery
application.

SDM overview
The SDM is a high-performance UNIX-based processing platform that
supports DMS SuperNode operations, administration, maintenance, and
provisioning applications.

In conjunction with the SDM-resident base and application software

developed by Nortel (Northern Telecom), and corresponding DMS-based
hardware and software elements, the SDM platform uses Motorola
technology, and includes the following elements:
• PowerPC 604e microprocessor
• AIX 4.1.5 operating system

Figure 1-1 shows the position of the SDM within the DMS SuperNode
system. The SDM is connected to the message switch (MS) using two
DS512 fiber links from one DS512 controller module. The DS512
controller module is equipped with two ports that connect over separate
links to the two MS planes. These links maintain communication to the MS
if a link fails or if one side of the MS is unavailable. External hardware is

Wireless Networks Family SDM–SX User Guide SDMPL011

1-2 Understanding the fault-tolerant SDM

connected to the SDM through modems using serial ports or through the
operating company LAN using a built-in Ethernet interface.

Figure 1-1xxx
SDM position in the DMS SuperNode system

DMS SuperNode
Computing
module

Message switch

IOC
DS512
MAP

UNIX DS512 interface

processor and controller CPU controller

SCSI controller

Console LAN controller

interface
SDM

Modem
Local External
RS-232C
console LAN (10BASE-T)

PSTN Operating company

LAN equipment OSS

OR Modem
External LAN

UNIX
workstation Router Terminal
Remote server
console
Asynchronous RS-232C

Application VT100 terminal

297-5061-901 Standard 01.01 December 1998

 Understanding the fault-tolerant SDM 1-3

SDM hardware
This section is an overview of the hardware components that can make up
the SDM platform. The SDM chassis mounts in a Nortel C28 Model B
(C28B) DMS Streamlined cabinet as shown in figure 1-2. The input/output
expansion chassis shown in figure 1-2 is optional.

Figure 1-2xxx
Front view of SDM cabinet

Wireless Networks Family SDM–SX User Guide SDMPL011

1-4 Understanding the fault-tolerant SDM

Modular
supervisory panel

Reserved for
future expansion

Not supported
on SX

Fan tray 0
Fan tray 1

Main chassis

Fan unit

SDM cabinet
The SDM cabinet contains the modular supervisor panel (MSP), the main
chassis, and the fan unit. The chassis has 16 slots, of which only seven are
usable on the SX. The remaining slots are reserved for future upgrades to a
fault-tolerant SDM.

Controller modules are located at the front of the main chassis and the I/O
expansion chassis. Each controller module has a P1 and a P2 connector. All

297-5061-901 Standard 01.01 December 1998

 Understanding the fault-tolerant SDM 1-5

controller modules, except for the CPU controller module, use the P1
connector to plug directly into a mid-mounted backplane. The P2 connector
bypasses the backplane and plugs directly into the corresponding personality
module, located at the back of the SDM.

Note: Controller modules are described on pages 1-5 and 1-17.

Each chassis is divided into two domains: domain 0 and domain 1. In each
chassis, slots 1 to 5 make up domain 0, and slots 12 to 16 make up domain
1. (Slots 6 to 11 make up the CPU core.)

Modular supervisory panel

The MSP provides power and alarm monitoring capabilities for the C28B
cabinet. The SDM platform is powered by A and B battery feeds (-48V dc).
Each feed is supplied from a separate breaker in the MSP into interconnect
modules (ICMs), located in the main and I/O expansion chassis.

The SDM computing hardware provides failure indications through volt-free

relay contacts in the ICM. These contacts provide an interface to the MSP
and to the central office alarm system. The status of the SDM is monitored
at the remote maintenance interface (RMI) alarm banner and the MAP alarm
banner. If a fan within the fan unit fails, or a power alarm occurs, the MSP
also activates end-of-aisle lamps on the DMS switching equipment, and
frame-fail lamps on the SDM cabinet.

Fan unit
The fan unit provides cooling in the SDM cabinet, in addition to the fan
trays in the main chassis. The fan trays provide horizontal cooling from the
front to the rear of the SDM. The fan unit provides vertical cooling, forcing
hot air up and out the top of the SDM.

Note: For information on replacing this fan unit or its cooling unit filter,
refer to DMS-100 Family Trouble Locating and Clearing Procedures and
DMS-100 Family Routine Maintenance Procedures included with your DMS
switch.

Front-mounted SDM main chassis hardware

Figure 1-3 shows a front view of the main chassis of the SDM platform.
The front of the chassis is equipped with upper and lower fan trays, and
provisionable controller modules. Minimally, the front of the main chassis
must contain the following controller modules:
• one DS512 controller modules (NTRX50GA) that mount in slot 1
• one I/O controller modules (NTRX50FQ) that mount in slots 2 and 3
• one CPU controller modules (NTRX50FK), with 128-Mbyte memory,
that mount in slots 6 and 7

Wireless Networks Family SDM–SX User Guide SDMPL011

1-6 Understanding the fault-tolerant SDM

• the remaining slots are reserved for future upgrades to a fault-tolerant

SDM
Figure 1-3xxx
Front view of the main chassis

Fan tray 0

Fan tray 1

Figure 1-4 shows the slot numbers contained in domain 0, domain 1, and the
CPU core. It also identifies the required provisionable controller modules
shown in the main chassis in figure 1-3. All other slots are available for
provisioning optional controller modules.

297-5061-901 Standard 01.01 December 1998

 Understanding the fault-tolerant SDM 1-7

Figure 1-4xxx
Front view of the main chassis by slot number

Domain 0 CPU core Domain 1

DS512 controller module

CPU controller module

I/O controller module
Filler faceplate
Filler faceplate

Filler faceplate
Slot 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16

Module slot placement

Figure 1-5 shows the dedicated slot numbers for required modules mounted
at the front and back of the main chassis of the SDM. These slot numbers
must be used for these modules. Unless noted otherwise, other
provisionable equipment can be mounted in any other slot number in the
main chassis. When a controller module occupies two slots, its personality
module occupies the lower slot number. For example, if a controller module
occupies slots 4 and 5 at the front of the SDM, its personality module
occupies slot 4 at the back of the SDM.

Wireless Networks Family SDM–SX User Guide SDMPL011

1-8 Understanding the fault-tolerant SDM

Figure 1-5xxx
Module slot number layout

Personality modules Controller modules

16R 16F
15R 15F
14R 14F
13R 13F
12R 12F
11R
10R 10F
09R 09F
08R NTRX50GS Filler faceplate NTRX50GR Filler faceplate 08F
07R
06R NTRX50FD CPU personality module NTRX50FK CPU controller module 06F
05R 05F
04R 04F
03R 03F
02R NTRX50FS LAN personality module NTRX50FQ I/O controller module 02F
01R NTRX50GH DS512 personality module NTRX50GA DS512 controller module 01F

Rear Front

Legend: Optional provisionable module or filler faceplate

CPU controller module (NTRX50FK)

The CPU controller module is a provisionable item. The module must
mount in slots 6 and 7 at the front of the main SDM chassis. The minimum
memory option of this module is 128 Mbyte (NTRX50FK). However, it is
also available with a memory option of 256 Mbyte (NTRX50FL). Two
additional CPU controller modules are available: the 128-Mbyte
NTRX50CF and the 256-Mbyte NTRX50CG modules.

The CPU controller module contains the main processing power and
memory capacity of the SDM. Each CPU controller module plugs into the
backplane of the main chassis through P1 and P2 connectors. The CPU
controller module is used in conjunction with the CPU personality module
(NTRX50FD). The CPU personality module is located in slot 6 at the back
of the main chassis of the SDM. The CPU personality module provides
console port connections to the CPU controller.

297-5061-901 Standard 01.01 December 1998

 Understanding the fault-tolerant SDM 1-9

DS512 controller module (NTRX50GA)

The DS512 controller module is a provisionable item that must mount in
slots 1 at the front of the main chassis of the SDM. The module supports
two DS512 fiber links that connect to the two MS planes. These two links
are normally all operating. If one link fails, the other link takes over,
ensuring that communication to the computing module (CM) continues.

The DS512 controller module is used in conjunction with the DS512

personality module (NTRX50GH), which is located in slot 1 at the back of
the main chassis of the SDM. The DS512 controller module connects to its
DS512 personality module using a P2 connector.

DS512 controller module (NTRX50GX)

The NTRX50GX DS512 controller module is an enhanced version of the
NTRX50GA DS512 controller module.

The NTRX50GX DS512 controller module is a provisionable item. It must

mount in slot 1 at the front of the main chassis of the SDM. Each module
supports two DS512 fiber pairs that connect to the two MS planes. Under
normal conditions, these two links are in operation.

The NTRX50GX DS512 controller module is used in conjunction with the

DS512 personality module (NTRX50GH). The NTRX50GX module is
located in slot 1 at the back of the main chassis of the SDM. The DS512
controller module connects to its DS512 personality module using a P2
connector.

The NTRX50GX card operates in the same manner as the NTRX50GA card,
but the NTRX50GX card provides the following enhancements:
• the NTRX50GX card has twice the buffer memory per link (16
kilobytes)
• the NTRX50GX card uses buffer memory more efficiently
• the device driver for the NTRX50GX card uses system CPU time more
efficiently and allows higher throughput

The NTRX50GX upgrade is optional. You can install either a NTRX50GX

or a NTRX50GA DS512 controller module. The NTRX50GX upgrade is
recommended to improve the reliability of processes that require a sustained
high-rate of DS512 message transfers.

Wireless Networks Family SDM–SX User Guide SDMPL011

1-10 Understanding the fault-tolerant SDM

The following limitation applies to the NTRX50GX DS512 controller

module. You must have SDMN0010 software to use the NTRX50GX
DS512 controller module.

ATTENTION
The NTRX50GX DS512 controller module requires SDMN0010
software.

I/O controller module (NTRX50FQ)

The I/O controller module is a provisionable item that must mount in slots 2
and 3, at the front of the main chassis of the SDM. The I/O controller
module provides a 3.5-in. 4-Gbyte disk drive unit (DDU), a digital audio
tape (DAT) drive, and an Ethernet interface. The disk drive is used for
storage of the AIX operating system, the SDM base, service and application
software, and data. The DAT drive is used for installation of SDM software,
for software restore in the event of corruption or disk drive failure, and for
performing software and data backups.

For information on performing software backups and restores, refer to the

“SDM system administration overview” and “SDM system administration
procedures” chapters of this document.

The NTRX50FQ I/O controller module is recommended for systems with

limited application storage requirements of less than 1 Gbyte. Application
data is stored in the root volume group (rootvg). To upgrade an I/O
controller module with the data volume group (datavg), manual transfer of
data is required, and application service is interrupted.

The I/O controller module is used in conjunction with the LAN personality
module (NTRX50FS) to provide connectivity using a 10BASE-T port from
the SDM to the operating company LAN. The LAN personality module
mounts in slot 2 at the back of the main chassis. The module is connected to
its I/O controller module using a P2 connector.

Note: The NTRX50FU and NTRX50GP I/O controller modules are

provisionable and can be used in addition to the NTRX50FQ I/O controller
module. For more information on these modules, including their use with
the NTRX50FQ I/O controller module, refer to ”I/O controller module
(NTRX50FU)” on page 1-17, and ”I/O controller module (NTRX50GP)” on
page 1-18.

Optional slots at the front of main chassis

Slots 4 and 5 at the front of the main chassis of the SDM are not used, unless
your SDM contains additional provisionable equipment. All unused slots at

297-5061-901 Standard 01.01 December 1998

 Understanding the fault-tolerant SDM 1-11

the front must be equipped with filler panels to ensure electromagnetic

interference (EMI) compliance, and to distribute cooling air evenly.

Controller module LEDs

Figure 1-6 shows the LEDs on the controller modules at the front of the
main chassis of the SDM. These LEDs are visible on all controller modules
in the main or the optional I/O expansion chassis. These LEDs are described
in further detail on page 2-94.

Figure 1-6xxx
Controller module LEDs

SDM main chassis

IN SERVICE

OUT OF
SERVICE

Fan trays
The main chassis is equipped with two removable fan trays (NTRX50FE
and NTRX50FF) that provide uninterrupted cooling to the main chassis.
Each fan tray has three fans. The fan trays are powered by separate battery
feeds. This ensures uninterrupted cooling during servicing to a fan tray.

Fan tray LEDs

Figure 1-7 shows the LEDs on the fan trays in the main chassis. Both fan
trays in the main chassis contain In Service and Out of Service LEDs. The

Wireless Networks Family SDM–SX User Guide SDMPL011

1-12 Understanding the fault-tolerant SDM

top fan tray (NTRX50FE) in the main chassis contains system status LEDs.
Fan tray LEDs are described in further detail on page 2-94.

Figure 1-7xxx
Fan tray LEDs on the main chassis

SYSTEM
IN SERVICE
COMPONENT
OUT OF SERVICE

FANTRAY 0
IN SERVICE
SDM main chassis
OUT OF
SERVICE

FANTRAY 1
IN SERVICE
OUT OF
SERVICE

Rear-mounted SDM main chassis hardware

Figure 1-8 shows a rear view of the main chassis of the SDM platform. The
rear of the main chassis is equipped with one DS512 personality module
(NTRX50GH) mounted in slot 1. The chassis also contains two interconnect
modules (ICMs) (NTRX50FG and NTRX50FH) that supply power to the
SDM. Other optional personality modules may also be mounted in this
chassis.

The rear of the main chassis must also contain the following:
• one LAN personality module (NTRX50FS) that mounts in slot 2
• one CPU personality module (NTRX50FD) that mounts in slot 6

297-5061-901 Standard 01.01 December 1998

 Understanding the fault-tolerant SDM 1-13

Figure 1-8xxx
Rear view of the main chassis

Interconnect
module 1 Interconnect
module 0

Figure 1-9 shows the slot numbers contained in domain 0, domain 1, and the
CPU core. It also identifies the required provisionable personality modules
in each slot number shown in figure 1-8. All other slots are available for
provisioning optional personality modules.

Wireless Networks Family SDM–SX User Guide SDMPL011

1-14 Understanding the fault-tolerant SDM

Figure 1-9xxx
Rear view of the main chassis by slot number

Domain 1 CPU core Domain 0

DS512 personality module

CPU personality module

LAN personality module

Filler faceplate
Filler faceplate
Filler faceplate
Filler faceplate
Filler faceplate
Filler faceplate
Filler faceplate
Filler faceplate
Filler faceplate
Filler faceplate

Filler faceplate
Filler faceplate
Filler faceplate
Slot 16 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01

DS512 personality module (NTRX50GH)

The DS512 personality module must be mounted in slot 1 at the back of the
main chassis. The DS512 personality module is connected to the DS512
controller module (NTRX50GA) located in slot 1 at the front of the main
chassis.

LAN personality module (NTRX50FS)

The LAN personality module must be mounted in slot 2 at the back of the
main chassis of the SDM. A LAN personality module is connected to the
I/O controller module (NTRX50FQ), in slots 2 and 3 at the front of the main
chassis. The LAN personality module allows for 10BASE–T port
connection to the operating company LAN.

CPU personality module (NTRX50FD)

The CPU personality module must mount in slot 6 at the back of the main
chassis of the SDM. The CPU controller module (NTRX50FK) connects to
the CPU personality module, which provides console and modem port
connection to the CPU controller module. For remote console access, port
SP0 on the CPU personality module must be connected to a modem by a
NTRX5093 cable. Port SP0 can be connected to a VT100 terminal by a
NTRX5094 cable for local console access.

297-5061-901 Standard 01.01 December 1998

 Understanding the fault-tolerant SDM 1-15

Optional slots at the back of main chassis

Slots 3 to 5, 7 to 16 at the back of the main chassis of the SDM are normally
not used, unless your SDM contains optional equipment. All unused slots at
the back must be equipped with filler panels to ensure EMI compliance, and
to distribute cooling air evenly.

Interconnect modules (NTRX50FG, NTRX50FH)

Two interconnect modules (ICMs) are located at the rear of the main chassis
and the I/O expansion chassis of the SDM. These modules are plugged
directly into the backplane. Each ICM supplies -48V dc to its corresponding
domain through separate battery feeds. Each ICM has two LEDS that
indicate when it is in service, or out of service.

Figure 1-10 shows a rear view of the interconnect modules.

Wireless Networks Family SDM–SX User Guide SDMPL011

1-16 Understanding the fault-tolerant SDM

Figure 1-10xxx
Rear view of the interconnect modules

SDM main chassis

rear view

Power Power
cable 1 cable 0
IN OUT OF IN OUT OF
Alarm SERVICE SERVICE SERVICE SERVICE Alarm
cable 1 cable 0

MBUS MBUS MBUS MBUS

PS0 PS1 ALARM PS0 PS1 ALARM

DOMAIN 1 DOMAIN 0

297-5061-901 Standard 01.01 December 1998

 Understanding the fault-tolerant SDM 1-17

Power supply
The hardware on the SDM is powered by A and B battery feeds. Hardware
in domain 0 is powered by battery feed A. Battery feed B powers hardware
in domain 1. Both battery feeds are normally operational. During a
single feed failure, the unaffected domain continues to provide all services.
The A and B battery feeds from the MSP connect to the chassis through the
ICMs at the back of each chassis.

Additional provisionable hardware

This section describes additional provisionable hardware that can be
mounted at the front of the main chassis. These controller modules are not
restricted to designated slot numbers.

Note: The SDM must be equipped with an NTRX50GN or NTRX50FQ I/O

controller module. The capacity of rootvg may be extended by replacing
NTRX50FQ modules with NTRX50GN modules. Rootvg cannot be
extended by adding more modules.

I/O controller module (NTRX50FU)

The NTRX50FU I/O controller module provides two 2-Gbyte DDUs with
Ethernet interfaces and 4 Gbyte of mirrored datavg capacity. To operate the
NTRX50FU module, a LAN personality module (NTRX50FS) must be
mounted in the corresponding slot number at the back of the chassis.

The NTRX50FU module can be used in addition to the NTRX50FQ and

NTRX50GP modules. Datavg may be expanded by up to 16 Gbyte without
service interruption, by adding NTRX50FU modules in pairs. The
NTRX50FU modules may be mounted in any two corresponding slots in
each domain of the main or I/O expansion chassis.

Note: The Ethernet interface on NTRX50FU I/O controller modules is not

supported in this release.

I/O controller module (NTRX50GN)

The NTRX50GN I/O controller module provides a 3.5 in. 4-Gbyte DDU, a
DAT drive, and an Ethernet interface. The disk drive is assigned to rootvg at
installation. The AIX operating system, the SDM base, service and
application software, and data are stored in rootvg.

The DAT drive is used for the following:

• installation of SDM software
• software restore in the event of corruption or disk failure
• performing software backups of rootvg

Wireless Networks Family SDM–SX User Guide SDMPL011

1-18 Understanding the fault-tolerant SDM

The NTRX50GN module mounts in slots 2 and 3 of the main chassis. To

operate this module, a LAN personality module (NTRX50FS) must be
mounted in slot 2 at the back of the main chassis.

Note: Nortel does not recommend using the NTRX50GN module when
additional modules (NTRX50FU or NTRX50GP) are provisioned for
datavg. Use the NTRX50FQ I/O controller module if the system is
equipped with additional datavg modules.

I/O controller module (NTRX50GP)

The NTRX50GP I/O controller module provides two 4-Gbyte DDUs with
Ethernet interfaces. The DDU is used for application data. The I/O
controller module occupies two slots to extend the datavg capacity by
8-Gbyte. To operate the NTRX50GP module, a LAN personality module
(NTRX50FS) must be mounted in the corresponding slot number at the back
of the chassis.

Note: The Ethernet interface on NTRX50GP I/O controller modules is not

supported in this release.

The NTRX50GP module can be used in addition to the NTRX50FQ module,

depending on system requirements. Use an NTRX50FQ module with an
NTRX50GP module to provide 2 Gbyte of rootvg and 8 Gbyte of datavg.
CPU controller module (NTRX50FL, NTRX50CF, NTRX50CG)
The minimum requirement for the SDM is a 128-Mbyte CPU controller
module (NTRX50FK). The controller module contains the main processing
power and memory capacity of the SDM. If you require a memory upgrade,
use one of the following modules.

You may use the additional provisionable NTRX50FL CPU controller

module that has 256 Mbyte DRAM. Two additional CPU controller
modules, NTRX50CF and NTRX50CG, are available in software release
SDMN0010. The NTRX50CF CPU controller module contains a PowerPC
604e microprocessor operating at 200 MHz and has 128 MByte DRAM. The
NTRX50CG CPU controller module also contains a PowerPC 604e
microprocessor operating at 200 MHz and has 256 MByte DRAM.

The CPU controller module mounts in slots 6 and 7 at the front of the main
chassis. The module plugs into the backplane of the main chassis through
P1 and P2 connectors. The CPU controller module is used in conjunction
with the CPU personality module (NTRX50FD), which is located in slot 6 at
the back of the main chassis of the SDM. The CPU personality module
provides console port connections to the CPU controllers.

297-5061-901 Standard 01.01 December 1998

 Understanding the fault-tolerant SDM 1-19

SDM software
SDM software has a three-layer architecture composed of separate base,
service, and application layers. This organization permits parallel
development in each stream, allowing independent delivery of new services
and applications, as well as interim delivery of any maintenance release
software.

The SDM base software layer is responsible for the maintenance and
operation of the SDM. The service layer provides common software utilities
and functions that can be used by multiple SDM applications. The
application software layer provides applications that address DMS switch
operations, administration, maintenance and provisioning (OAM&P).

SDM base software layer

The SDM base software layer consists of the following:
• the AIX 4.1.5 operating system (the proprietary IBM implementation of
UNIX) and server software
• node and process control services
• maintenance and administration services

SDM service software layer

The service software layer provides internal application support software for
use by current and future SDM application packages. The service software
layer consists of the following:
• table access utilities allowing SDM applications to manipulate tables
maintained on the CM
• remote procedure calls (RPC) allowing CM software to raise RPCs to
SDM software. RPCs allow a program running on one host to request
and receive a message containing results of a service on another host.
• Open Software Foundation (OSF) Distributed Computing Environment
(DCE) to provide authentication and authorization mechanisms to ensure
network security
• operational measurement (OM) collection and application programming
interface (API) allowing SDM applications to receive OM data from the
CM

SDM application software layer

The application software layer contains operations, administration, and
maintenance software application packages. This layer contains all SDM
application software installed on your system, including the Log Delivery
application, and the optional Exception Reporting (ER), Enhanced Terminal
Access (ETA) and SuperNode Billing Application (SBA) applications.

Wireless Networks Family SDM–SX User Guide SDMPL011

1-20 Understanding the fault-tolerant SDM

For information on the Log Delivery application, see page 1-24. For
information on optional SDM applications, refer to the following Northern
Telecom Publications (NTPs):
• SuperNode Data Manager Exception Reporting User Guide
• SuperNode Data Manager Enhanced Terminal Access User Guide
• SuperNode Data Manager SuperNode Billing Application Application
Guide

Maintenance interfaces
There are two maintenance interfaces for the SDM:
• the MAP, accessed from the CM
• the RMI, accessed from the SDM

The MAP is the primary access point for maintenance activities. The RMI is
the secondary access point for maintenance activities. Maintenance
activities must be initially performed at the MAP interface. When
connectivity to the CM is not available, the RMI provides access to all
maintenance activities that would normally be performed at the MAP
interface.

MAP-based SDM maintenance

A dedicated SDM maintenance subsystem is provided at the MTC PM level
of the MAP display which allows you to do the following:
• determine the node state and operating condition of the SDM
• alter the state of the SDM for maintenance purposes
• determine the status of connectivity to the SDM
• reboot or halt the SDM
• determine the status of SDM applications, including any faults currently
affecting applications, by using the QuerySDM command (See the
“SDM maintenance overview” chapter for more information.)
• determine the status of the SDM operating system, including any faults
currently affecting system software resources, by using the QuerySDM
command. (See the “SDM maintenance overview” chapter for more
information.)

The MAP display is used to maintain the SDM if the CM is communicating

successfully with the SDM. If the SDM and the CM are unable to
communicate due to a fault on the SDM, the RMI must be used to diagnose
and clear the problem.

See ”Maintaining the SDM using the MAP interface” on page 2-2 for an
overview of MAP-based maintenance capabilities.

297-5061-901 Standard 01.01 December 1998

 Understanding the fault-tolerant SDM 1-21

RMI-based SDM maintenance

The RMI can be accessed by the following methods:
• using a remote or local VT100 terminal console port
• telneting from the operating company LAN (telnet must be enabled)

The RMI provides the following maintenance capabilities:

• access to all maintenance capabilities which would normally be available
through the MAP interface, including state change and monitoring
capabilities, when connectivity to the CM is not available
• control of individual SDM application software packages
• control and maintenance of hardware

For full details on the capabilities provided on the RMI, see ”Maintaining
the SDM using the remote maintenance interface” on page 2-34.

Administration functions
SDM administration is performed by root and maintenance (maint) users,
primarily using UNIX-based utilities at a local or remote VT100 console,
and tools available at the RMI. Administration capabilities supported
through this interface include commissioning of the SDM platform,
commissioning of the Log Delivery application, setup of user groups (root
and maint) and passwords, monitoring system resources, and performing
software backup and restore functions.

Disk partitioning
The AIX operating system provides disk partitioning capability into logical
volumes. Logical volume partitioning provides protection against disk
occupancy errors (full disk), allowing the system to read from and write to
the remaining disks without interruption.

On the SDM, logical volumes are equivalent to file systems. The SDM file
system structure is provisioned by Nortel. The root user can only monitor
file system partitioning and usage using the RMI or the MAP display at the
local or remote VT100 terminal. The root user cannot modify logical
volumes.

For additional information on administering the SDM, see the “System

administration overview” and the “System administration procedures”
chapters of this document.

Wireless Networks Family SDM–SX User Guide SDMPL011

1-22 Understanding the fault-tolerant SDM

LAN-based I/O interface capabilities

LAN-based I/O interfaces are supported on the SDM to the following types
of equipment:
• workstations
• hubs
• routers
• terminal servers

Each of these interface types is discussed in the following subsections.

Workstations
You can configure UNIX workstations as remote user interface (UI) clients
to provide the UI for SDM applications. For product releases before
SDMN0010, the following workstations with the appropriate DCE client
software (OSF DCE version 1.1) support UI clients:
• HP 700/800 series workstations running the HP-UX 9.05 operating
system (or higher)
• Sun SPARC workstations running Solaris 2.4 or later

For product release SDMN0010, the following workstations with the

appropriate DCE client software (OSF DCE version 1.1) support UI clients:
• HP 700/800 series workstations running the HP-UX 10.20 operating
system (or higher) with year 2000 enhancements
• Sun SPARC workstations running the Solaris 2.4 operating system (or
higher) with year 2000 enhancements
• Sun SPARC workstations running the year 2000-compliant Solaris 2.6
operating system (or higher)

Note: UI client performance depends on workstation performance.

297-5061-901 Standard 01.01 December 1998

 Understanding the fault-tolerant SDM 1-23

Hubs
Hubs are required when 10BASE-T or unshielded twisted pair (UTP) LANs
are used. The minimum requirements for a customer-supplied hub
connected to the SDM are as follows:
• compliance with IEEE 802.3/Ethernet 10BASE-T specifications
• internal self-test, diagnostics, and configuration available from a locally
attached terminal or through the Simple Network Management Protocol
(SNMP) over the LAN
• compliance with the Address Resolution Protocol (ARP) broadcast
refinement
• auto segmentation to prevent babbling or erroneous ports from affecting
the operation of the LAN
• support for cascading hubs to expand the LAN
• visual indicators of the LAN status

Routers
Routers perform wide area networking for SDM graphical user interfaces
(GUIs) over other networks, and provide gateway (or protocol translator)
functions.

The minimum requirements for a customer-supplied router used in a

configuration connected to the SDM are as follows:
• compliance with IEEE 802.3/Ethernet 10BASE-T specifications
• internal self-test, diagnostics, and configuration available from a locally
attached terminal or through the SNMP over the LAN
• compliance with the ARP broadcast refinement
• support for a variety of WAN communication facilities (asynchronous
transfer mode [ATM], and channel service unit [CSU]/data service unit
[DSU])
• visual indicators of LAN and port status and connectivity

Wireless Networks Family SDM–SX User Guide SDMPL011

1-24 Understanding the fault-tolerant SDM

Terminal servers
A terminal server can be used to provide asynchronous access to the SDM.
Terminal server ports can either be used instead of integrated asynchronous
application ports or can be provisioned in addition to the integrated ports.
The number of required asynchronous ports is determined by the
engineering rules associated with each application.

The minimum requirements for a terminal server used with the SDM are as
follows:
• compliance with IEEE 802.3/Ethernet 10BASE-T specifications
• telnet and TCP/IP support
• internal self-test, diagnostics, and configuration available from a locally
attached terminal or through the SNMP over the LAN
• compliance with the ARP broadcast refinement
• visual indicators of LAN and port status
• capability to configure terminal servers through a locally attached
terminal (preferred)
• full modem support for dial-up applications
• port speeds of up to 64 kbit/s
• point-to-point protocol availability

SDM Log Delivery

The Log Delivery application, included as part of the base software platform
on the SDM, delivers user-defined streams of DMS SuperNode logs and
SDM platform and application logs to one or more of the following:
• up to 10 operations support systems (OSS), by TCP/IP links from the
SDM to the operating company LAN
• up to 10 UNIX files stored on the SDM

A maximum of 10 Log Delivery output devices can be commissioned (the

sum total of TCP/IP links and UNIX files cannot exceed 10).

The Log Delivery application cannot be used to deliver logs generated by

DMS SuperNode processors other than the CM and the SDM. Logs from
other processor types may continue to be delivered by the standard input
output controller (IOC) log devices by datafilling a valid IOC log device
name for each required processor type in table RLOGDEV. Currently
defined processor types unsupported by SDM Log Delivery are as follows:
• message switch (MS)
• CCS7 link interface unit (LIU7)

297-5061-901 Standard 01.01 December 1998

 Understanding the fault-tolerant SDM 1-25

• frame relay interface unit (FRIU)

• Ethernet interface unit (EIU)
• link interface module (LIM)
• enhanced network (ENET)
• application processor (AP)
• file processor (FP)
• X.25, X.75 link interface unit (XLIU)
• auxiliary processing unit (APU)
• GSM (global system for mobile communications) processor (GSMP)
• voice processing unit (VPU)
• high-speed link interface unit (HLIU)
• network interface unit (NIU)
• high-speed link router (HSLR)
• Ethernet link interface unit (ELIU)
• CDMA (code division multiple access) application unit (CAU)
• CDMA interface unit (CIU)
• cellular authentication and voice privacy unit (CAVU)
• A-interface control element (ACE)

Logreceiver tool
The logreceiver tool is a client application, included with the Log Delivery
application, which runs on a remote workstation and receive logs sent to the
workstation from an SDM by the operating company LAN. The logreceiver
tool can either store these logs in a file, or display them on the screen.

Only the following workstations can be used to run the logreceiver tool in
product release SDMN0010:
• HP 700/800 series workstations running the HP-UX 10.20 operating
system (or higher) with year 2000 enhancements
• Sun SPARC workstations running the Solaris 2.4 operating system (or
higher) with year 2000 enhancements
• Sun SPARC workstations running the year 2000-compliant Solaris 2.6
operating system (or higher)

To route logs from an SDM to a workstation, the SDM must be configured

to send logs to a TCP device whose IP address is the IP address of the

Wireless Networks Family SDM–SX User Guide SDMPL011

1-26 Understanding the fault-tolerant SDM

workstation using the logroute commissioning tool. (For more information,

see ”Commissioning TCP client devices for Log Delivery” on page 2-87).

Refer to the procedure ”Installing the logreceiver tool” on page 6-57 in the
“SDM system administration procedures” chapter of this document for
detailed instructions on how to install the logreceiver tool on a workstation.

Log formatting
The Log Delivery application can format logs using Nortel standard (STD)
or Switching Control Center 2 (SCC2). Logs in STD format specify the
switch name, and if configured, the node (SDM) name. Logs in SCC2
format do not specify the switch or node name. Formatting can be set on a
per-device basis.

Log buffering
In the event that any destination device is unable to receive logs for any
reason, logs are buffered locally on the SDM until the device is ready to
receive logs. The default buffer size is 150. The buffer size can be
modified, using the Log Delivery commissioning tool. The buffer size must
be at least 50 and cannot exceed 300.

Log delivery commissioning tool (logroute)

Log Delivery operating parameters are controlled by an online SDM
commissioning tool, which is used to set up the parameter values, and can
also be used to view or modify these values.

ATTENTION
You must busy and return the Log Delivery application to service to
make new changes changes take affect. An interruption in log routing
to all currently active devices will result. Any logs buffered for
delivery to these devices will be lost during this operation.

ATTENTION
There is no locking mechanism on the logroute tool. Therefore, the
logroute tool must only be run by one user at a time. Otherwise,
changes made by one user may overwrite those of another user.

297-5061-901 Standard 01.01 December 1998

 Understanding the fault-tolerant SDM 1-27

The Log Delivery commissioning tool allows customization of the

following:
• global application parameters including buffer size, reconnect timeout
value, lost logs threshold, ASCII line delimiter and log delimiter
characters, and the number of days to keep log files
• the incoming log stream from the CM, to add or delete individual logs or
log types
• output device list, including device type (UNIX file or TCP output),
parameters specific to the device type, log output format (STD or SCC2)
and the logs or log types to be sent to the device

The Log Delivery commissioning tool includes an online help facility that
provides the valid ranges (and default values, where applicable) for each
customizable parameter.

For additional information on configuring and troubleshooting the Log

Delivery application, see page 2-81.

Wireless Networks Family SDM–SX User Guide SDMPL011

 2-1

SDM maintenance overview

This chapter is an overview of the SDM maintenance capabilities and
methods.

”SDM monitoring and maintenance positions” on page 2-1 describes the

user interfaces and output devices from which you can monitor and maintain
the SDM. These include the CM MAP interface, the SDM remote
maintenance interface (RMI), and the DMS log stream.

”SDM Log Delivery applications” on page 2-81 describes the SDM Log
Delivery application and provides commissioning and troubleshooting
guidelines.

”SDM troubleshooting strategy” on page 2-92 provides recommendations

for isolating and clearing faults on the SDM platform.

”Routine maintenance recommendations” on page 2-104 lists routine

maintenance activities.

SDM monitoring and maintenance positions

Information about the state of the SDM is available from the following
monitoring and maintenance positions:
• maintenance level of the MAP interface. See ”Maintaining the SDM
using the MAP interface” on page 2-2.
• SDM remote maintenance interface. See ”Maintaining the SDM using
the remote maintenance interface” on page 2-34.
• log streams. See ”SDM log reports” on page 2-77.
— from the SDM to an operations support system (OSS) or UNIX file
using the SDM Log Delivery application. See page 1-24 for
additional information.

Each of these maintenance access points is described in the following

sections.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-2 SDM maintenance overview

Maintaining the SDM using the MAP interface

The primary access point for maintaining the SDM is the application
(APPL) subsystem of the MAP interface. The MAP command and display
structure for the SDM is similar to that provided at other MAP levels.
Commands at the SDM level allow you to do the following:
• monitor and alter the state of the SDM
• determine the state of the DS512 interface associated with the SDM
• query status information on the SDM system, application software, and
hardware location
• provide access to the Platform sublevel to monitor and alter the state of
the SDM devices

You can use the MAP interface to maintain the SDM. However, at least one
of the communication links between the computing module (CM) and the
SDM must be in service. If all of the links are out of service, the SDM is
isolated and maintenance must be performed using the RMI, described on
page 2-34.

Figure 2-1 shows an example of the SDM level of the MAP display. The
display shows the SDM status, the number of links out of service, any
current maintenance actions, and provides an SDM-specific command set.
Fault conditions related to the SDM are reported in the alarm banner. In this
example, the SDM is InSv. Using the command set provided, you can
obtain additional details about the condition of the SDM to isolate and
resolve faults.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-3

Figure 2-1xxx
SDM MAP level

CM MS IOD Net PM CCS Lns Trks Ext APPL

. . . . . . . . . .

SDM OAMAP SDM SWMTC SDMBIL

0 Quit . . . .
2 _
3 SDM 0 InSv Links_OOS: .
4 <Maintenance message text area>
5 Trnsl
6 <scrolling text area>
7 Bsy
8 RTS
9 OffL
10
11
12
13
14 QuerySDM
15 Locate
16
17
18 Platform

USERID
Time 19:48 >

Note: The above screen is an example of the SDM Map level for a North
American product.

Determining the SDM node state at the MAP display

The following table lists and describes the SDM node states that are
available on the MAP display at the SDM level. The MAP alarm banner
indicator associated with each state is listed.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-4 SDM maintenance overview

Table 2-1xxx
SDM node state indicators at the SDM MAP level

SDM state Associated Associated

at the APPL SDM
MAP banner banner
interface alarm alarm Meaning of the state

InSv APPL SDM No alarms are present. The SDM is in the in

. . service (InSv) state. The SDM, its applications,
and hardware devices are running normally
without faults, and the CM and the SDM are
communicating successfully.
OffL APPL SDM No alarms are present. The SDM is in the off-line
. . (OffL) state. In the OffL state, the CM and the
SDM are not communicating, and no applications
are running. The SDM is automatically designated
as off-line when datafilled for the first time. It can
also be set to the off-line state from the manual
busy (ManB) state by the OffL command at the
MAP interface.

—continued—

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-5

Table 2-1xxx
SDM node state indicators at the SDM MAP level (continued)

SDM state Associated Associated

at the APPL SDM
MAP banner banner
interface alarm alarm Meaning of the state

ISTb APPL SDM An APPL SDM minor alarm is present. The CM is

SDM ISTb receiving in-service trouble (ISTb) status from the
SDM. One or more of the following conditions
may exist:
• One or more SDM applications cannot run, but
at least one application is running
successfully.
• The SDM cannot communicate with one or
more of the operating company LAN nodes
defined on the SDM.
• A software resource threshold has been
exceeded.
• An SDM application has reported an ISTb
condition.
• A non-critical hardware fault is present.
• All, DS512 links are out of service.
• The SDM has been declared a minor babbler
by the MS. The SDM is sending too much
information before receiving
acknowledgements. See page 2-12 for more
information.
• Disk mirroring is in progress or has failed.
• There is an IP mismatch between the CM and
the SDM.
• A file system has exceeded its alarm threshold
or any volume group is not InSv.
• There is a fault with Distributed Computing
Environment (DCE).

—continued—

Wireless Networks Family SDM–SX User Guide SDMPL011

2-6 SDM maintenance overview

Table 2-1xxx
SDM node state indicators at the SDM MAP level (continued)

SDM state Associated Associated

at the APPL SDM
MAP banner banner
interface alarm alarm Meaning of the state

ManB APPL SDM An APPL SDM minor alarm is present. The SDM
SDM ManB has been manually busied (ManB) by command at
the MAP interface.
ManB (NA) APPL SDM An APPL SDM minor alarm is present. The SDM
SDM ManB has been manually busied by command at the
MAP interface. The CM cannot communicate with
the SDM because the DS512 ports on the MS are
unavailable. The operating condition and local
state of the SDM are unknown to the CM. This is
the case until at least one of the DS512 links is
restored.
ManB/The APPL SDM An APPL SDM minor alarm is present. The SDM
SDM is not SDM ManB has been manually busied by command at the
responding MAP interface. The CM is not receiving messages
from the SDM. The operating condition and local
state of the SDM are unknown to the CM until
communications with the SDM are restored.
SysB APPL SDM An APPL SDM critical alarm is present. The CM
SDM SysB has designated the SDM node state as system
*C* *C* busy (SysB). One or more of the following
conditions exist:
• The CM is receiving system-busy status from
the SDM.
• The SDM is a major or critical babbler. The
SDM is sending too much information before
receiving acknowledgements. See page 2-12
for more information.
• All software applications on the SDM have
failed.

—continued—

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-7

Table 2-1xxx
SDM node state indicators at the SDM MAP level (continued)

SDM state Associated Associated

at the APPL SDM
MAP banner banner
interface alarm alarm Meaning of the state

SysB (NA) APPL SDM An APPL SDM critical alarm is present. The CM
SDM SysB has designated the SDM node state as system
*C* *C* busy (SysB). The CM cannot communicate with
the SDM because the DS512 ports on the MS are
unavailable. The operating condition and local
state of the SDM are unknown to the CM. This is
the case until at least one of the DS512 links is
restored.
SysB/The APPL SDM An APPL SDM critical alarm is present. The CM
SDM is not SDM SysB has designated the SDM node state as system
responding *C* *C* busy (SysB). The SDM node state can be SysB
for the following reasons:
• Communication links between the CM and the
SDM are not operating. The operating
condition and local state of the SDM are
unknown to the CM until communications with
the SDM are restored.
• The SDM has been powered down or is
rebooting after being powered down.
Note: The SysB state is reported as an APPL SDM critical alarm. ISTb and ManB states are
reported as an APPL SDM minor alarm.

—end—

Note: The loss of a DS512 link will not change the SDM node state unless
all the DS512 links are down.

Using SDM commands at the MAP display

The SDM MAP display is accessed at the SDM level of the MTC APPL
level. The following commands are provided at the SDM MAP level:
• Quit is the standard SDM level menu command used to exit the current
MAP level.
• Trnsl displays the link address information for the links between the MS
and the SDM. See ”Using the Trnsl command” on page 2-8 for more
information.
• Bsy sets the SDM to manual busy (ManB) state. See ”Using the Bsy
command” on page 2-9 for more information.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-8 SDM maintenance overview

• RTS returns the SDM to service from manual busy (ManB) state. See
”Using the RTS command” on page 2-10 for more information.
• OffL sets the SDM to offline (OffL) state from manual busy (ManB)
state. Executing the OffL command disables communications between
the CM and SDM.
• QuerySDM provides a variety of information about the status and
configuration of the SDM. See ”Using the QuerySDM command” on
page 2-11 for more information.
• Locate provides a list of hardware modules installed on the SDM and
their physical location. See ”Using the Locate command” on page 2-12
for more information.
• Platform provides access to the SDM platform level for SDM
device-level fault isolation and resolution functions. See ”Using the
Platform command” on page 2-13 for more information.
• RebootSDM is a non-menu command that reboots the SDM. See ”Using
the ReBootSDM command” on page 2-15 for more information.
• HaltSDM is a non-menu command that halts the SDM. See ”Using the
HaltSDM command” on page 2-15 for more information.
• SDMRLogin is a non-menu command that allows you to log in to the
SDM from the CM. See ”Using the SDMRLogin command” on page
2-16 for more information.

Using the Trnsl command

Trnsl displays the link address information for the DS512 links between the
MS and the SDM. When Trnsl is executed, the following information is
displayed:
• the SDM number, domain, and port
• the MS number, card, and port
• the link status and messaging condition
• whether C-side (MS) or P-side (SDM node control) actions are in
progress

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-9

Using the Bsy command

Bsy sets the SDM to manual busy (ManB) state. The system response to the
Bsy command depends on the status of the communication link between the
CM and the SDM:
• If the CM and the SDM are communicating successfully, the CM sends
the Bsy command to the SDM. If the SDM is in service, you receive a
yes/no prompt. This indicates that executing the Bsy command causes a
service interruption (all applications running on the SDM shut down).
Executing the command changes the state of the SDM at the MAP
display to ManB, changes the local state of the SDM (as it appears on the
RMI) to ManB, and shuts down all SDM applications.
• If the CM and the SDM are not communicating, the CM cannot send the
Bsy command to the SDM. The CM view of the SDM state (as it
appears at the MAP display) changes to ManB (NA) or ManB/The SDM
is not responding. This state depends on the reason for the
communication problem. The local state of the SDM (as it appears at the
RMI) and its operating condition are unaffected by the Bsy command.
However, when CM-SDM communications are restored, the SDM aligns
to the current CM view of its state.
You can set the local state of the SDM to ManB when the CM and the
SDM are not communicating. However, the Bsy command must be
executed at the RMI, which shuts down any applications that are
running.

• When the SDM is in OffL state, the CM sets the SDM state to ManB and
enables CM-SDM communication. The CM then sends the Bsy
command to the SDM.

The Bsy command has the options Force and Nowait. The Bsy command
with the Force option overrides the following commands that are in
progress:
• RTS
• RTS Force
• Bsy

The Nowait option is the standard DMS MTC command parameter used to
return command entry capability immediately. That is, you can continue to
enter other commands while the system is executing the Bsy command.
Refer to logs output to determine the progress of the Nowait option.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-10 SDM maintenance overview

Using the RTS command

RTS returns the SDM to service from manual busy state. The system
response to this command depends on the status of the communication link
between the CM and the SDM:
• If the CM and the SDM are communicating successfully, the CM sends
the RTS command to the SDM. If the command executes successfully,
the SDM is returned to service. If there are no faults on the SDM, the
state of the SDM changes to InSv at the MAP interface, and at the RMI.
If one or more applications on the SDM are not running, the SDM state
is ISTb.
• If the CM and the SDM are not communicating, the CM cannot send the
RTS command to the SDM. The CM view of the SDM state (as it
appears at the MAP display) changes to SysB (NA) or SysB/The SDM is
not responding. The state depends on the reason for the communication
problem. The local state of the SDM (at the RMI) and its operating
condition are unaffected by the RTS command. However, when
CM-SDM communications are restored, the SDM aligns to the current
CM view of its state.
• To perform a local return-to-service of the SDM when CM-SDM
communications are down, the RTS command must be executed at the
RMI.

The RTS command has the options Force and Nowait. The Force option
invokes a forced return-to-service of SDM applications. Use the Force
option with caution. It ensures the state change takes place, however, all
errors (IP mismatch) are ignored and checks are bypassed. The Nowait
option is the standard DMS MTC command parameter used to return
command entry capability immediately. That is, you can continue to enter
other commands while the system is executing the RTS command. Refer to
logs output to determine the progress of the Nowait option.

ATTENTION
When the SDM or one of its applications or services is returned to
service from a manual busy (ManB) state, the state of the SDM may
move to in-service (InSV) briefly, then to in-service-trouble (ISTb) for
a few minutes, and finally back to InSv.

The ISTb state is the result of the application not being fully capable
of supplying service during initialization. For example, if the
Operations Measurements application is not yet InSv, the Exception
Reporting application will be ISTb.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-11

Using the QuerySDM command

QuerySDM provides information about the SDM, as follows:
• QuerySDM with no additional parameters displays the status of the SDM
as seen from the MAP display, its IP address on the CM side, and its
physical location as defined in table SDMINV. The slot number is
always blank. This information is displayed regardless of the state of the
CM-SDM communication link.
• If there are no faults on the SDM, and the SDM is in service, QuerySDM
displays the message ”No local SDM fault to report”.
• QuerySDM FLT displays information about SDM software and device
faults. This information is obtained directly from the SDM and is only
displayed if the CM-SDM communication link is functioning. Stopped
processes are not displayed when the node is in ManB state. The
following information is included for device faults:
— the faulty component
— time stamp of the last SDM state change
— the faulty module, its product engineering code (PEC), and location
— other devices on the faulty module and their state
— reason text that describes the fault (if available)
• QuerySDM LOADS displays the version and status of software installed
on the SDM. This information is obtained directly from the SDM and is
only displayed if the CM-SDM communication link is functioning.
• QuerySDM STATUS displays local SDM alarms (LAN connectivity,
CM connectivity, application software, and system software).
QuerySDM STATUS also shows all devices on the SDM, and their
states. This information is obtained directly from the SDM and is only
displayed if the CM-SDM communication link is functioning.
• QuerySDM CONFIG displays configuration data (platform type,
connectivity information, operating company LAN configurations, and
system threshold values) related to the SDM. This information is
obtained directly from the SDM and is only displayed if the CM-SDM
communication link is functioning.

Error messages for QuerySDM with the FLT, LOADS, CONFIG, or

STATUS options are generated for the following reasons:
• The request to the SDM cannot be sent because there are no available
DS512 links.
• The CM timed out before the command complete message was received
from the SDM.
• The SDM is not responding.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-12 SDM maintenance overview

• The SDM is in the OffL or unequipped state.

• Messages could not be sent to the SDM for the following reasons:
— The node maintenance process could not obtain a CM-side message
transport service (MTS) endpoint.
— The node maintenance process could not obtain an SDM-side MTS
endpoint.

• The maximum number of simultaneous SDM commands has been

exceeded. Try the command later.
• An unexpected software error was encountered.

In addition, error messages are generated for QuerySDM FLT for the
following reasons:
• The MS has indicated that the SDM is a minor, major, or critical babbler.
That is, the SDM node is sending too much information before receiving
acknowledgements:
— When the MS indicates that the SDM is a minor babbler, the state of
the SDM on the CM is set to ISTb. An APPL SDM minor alarm is
generated. Refer to the procedure, ”Clearing MAP alarms triggered
by the SDM - APPL SDM minor” on page 4-3.
— When the MS indicates that the SDM is a major babbler, the state of
the SDM on the CM is set to SysB. All links are maintenance open.
Applications can no longer communicate between the SDM and the
CM. An APPL SDM critical alarm is generated. Refer to the
procedure, ”Clearing MAP alarms triggered by the SDM - APPL
critical” on page 4-25.
— When the MS indicates that the SDM is a critical babbler, the state of
the SDM on the CM is set to SysB. All links are closed.
Applications can no longer communicate between the SDM and the
CM. An APPL SDM critical alarm is generated. Refer to the
procedure, ”Clearing MAP alarms triggered by the SDM - APPL
SDM critical” on page 4-25.

Using the Locate command

Locate displays location information about the SDM hardware modules and
the devices they support. The following information is displayed when this
command is executed:
• the type of module, its location (including chassis and slot number), and
PEC
• devices on the module

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-13

The SDM must be in ManB or higher (InSv, SysB or ISTb) state to execute
this command successfully. The Locate command can only be used if the
CM-SDM communication link is up. Error messages are displayed for the
following reasons:
• There is no communication route to send the locate request to the SDM.
• The CM has timed out before receiving a command complete message
from the SDM.
• The SDM is not responding.
• The SDM is in the OffL or unequipped state.
• Messages could not be sent to the SDM for the following reasons:
— The node maintenance process could not obtain a CM-side MTS
endpoint.
— The node maintenance process could not obtain an SDM-side MTS
endpoint.
• The maximum number of simultaneous SDM commands has been
exceeded. Try the command later.
• An unexpected software error was encountered.

Using the Platform command

Platform displays state information on the SDM software components,
hardware modules, and devices. The following information is displayed
when this command is executed:
• SDM application and software state (APPL)
• SDM LAN connectivity state (LAN)
• SDM system software state (SYS)
• CM connectivity state (CON)
• hardware device states. A state is displayed for a hardware device on
domain 0 (D0) and domain 1 (D1).

The Platform command can only be used if the CM-SDM communication

link is up. Error messages are displayed if the CM-SDM communication
link is down or the Platform MAP level could not be allocated.

The following commands are available from the Platform level:

• QUIT is the standard menu command used to exit the current MAP
level.
• TRNSL displays information on the state of the CM to SDM connecting
links. When Trnsl is executed, the following information is displayed:

Wireless Networks Family SDM–SX User Guide SDMPL011

2-14 SDM maintenance overview

— the SDM number, domain, and port

— the MS number, card, and port
— the link status and messaging condition
— whether C-side (MS) or P-side (SDM node control) actions are in
progress

• BSY is a menu command that sets the requested SDM hardware device
to a manual busy (ManB) state. The command has one optional
parameter:
— The FORCE option is the standard DMS MTC command parameter
used to force the state change. Force works even if the change will
cause a service outage. Use the Force option with caution. It ensures
the state change takes place, however, all errors (IP mismatch) are
ignored and checks are bypassed.

CAUTION
Possible service interruption
Using the FORCE option with the BSY command may
cause a possible service interruption. BSY with the
FORCE option overrides any commands in progress.

Error messages for BSY with the FORCE option are generated for the
following reasons:
• The command could not be executed because of lack of SDM resources.
• The CM timed out before the command complete message was received
from the SDM.
• Execution of the command was canceled because the user chose abort or
a negative response to a confirmation prompt.
• The hardware device is already in a ManB state.
• The command could not be executed due to an abnormal condition or
because communications with the SDM are down. The reason is
described by one of the following error messages:
— The SDM is Unequipped
— The SDM is OFFL
— No communication route to the SDM
— No SDM C-side MTS address
— No SDM P-side MTS address
— Software error encountered

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-15

— The SDM is not responding

— Maximum number of SDM command users exceeded
• RTS is a menu command that returns the requested hardware device to
service from a manual busy (ManB) state.
• The QuerySDM command provides a variety of information about the
status and configuration of the SDM. See ”Using the QuerySDM
command” on page 2-11 for more information.
• Locate provides a list of modules and devices installed on the SDM and
their physical location. See ”Using the Locate command” on page 2-12
for more information.

Using the RebootSDM command

RebootSDM is a non-menu command that is used to reboot the SDM. It can
only be executed if the node state is ManB and the links are available.

CAUTION
Reboot message
When a RebootSDM command is issued, the following
message may appear on the SDM’s local console during
the reboot:
Board Configuration Data Failure
Ignore this message. It is not service-affecting.

Using the HaltSDM command

HaltSDM is an unlisted menu command that halts the SDM. It can only be
executed if the node state is ManB and the links are available.

CAUTION
Possible loss of service
If the RebootSDM or HaltSDM command is used on an
SDM/FT system while there is a loss of power to the ICM
on D0 of the main chassis (ICM 0), the system will not
recover from the reboot. A loss of power can be caused
by the removal of the power cable, turning off the circuit
breaker in the MSP, or a faulty ICM 0. Restore power to
ICM 0 and perform a reboot.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-16 SDM maintenance overview

Using the SDMRLogin command

SDMRLogin is a non-menu command that allows root and maint
(maintenance) users to log in to the SDM from any MAPCI level.
Maintenance users are only allowed to perform surveillance and
maintenance activities. They must not alter or create new files.

ATTENTION
Log in as the root user only when the procedure you are performing
requires it. Otherwise, log in as a maint user. If you are logged in as
the root user, use caution when copying, storing, or removing any files
on the SDM.

Copying and storing files in a logical volume, or removing files from a

logical volume, may cause the SDM to fail.

ATTENTION
Executing an SDMRLogin session from the CM to the SDM as the
root user puts you in a restricted shell and does not allow root
privileges. SDMRLogin is used to perform local maintenance
activities. If you need to perform other operations that require root
user privileges, log in to the SDM as the root user.

The SDM must be in InSv or ISTb state to execute the SDMRLogin

command. When the SDMRLogin command is invoked, you are prompted
for your userID, as follows:

SDM Remote Login command in progress. Please wait...

telnet (sdm123)
AIX Version 4
(C) Coprights by IBM and by others 1982, 1994.
login:

You are prompted for your password. The screen then displays the number
of unsuccessful login attempts since your last login, and your last
unsuccessful login attempts.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-17

Password:
************************************************************
** **
** This is a private database. **
** All activity is subject to monitoring. **
** Any UNAUTHORIZED ACCESS OR USE IS PROHIBITED. **
** **
************************************************************
Last unsuccessful login: Sat Apr 12 16:45:20 EDT 1997 on /dev/pts
/4 from 47.208.11.94
Last login: Mon Apr 14 11:46:41 EDT 1997 on /dev/pts/4 from cm

SDM>

Note 1: A password beginning with a numeric character is valid on the

SDM. You can use such a password to access the SDM from any MAPCI
level using the SDMRLogin command. However, to do so, you must enter a
space at the beginning of the password.
Note 2: The UNIX shell prompt must not be modified during an SDM
remote login session. If the prompt is modified, the remote login session
will hang, and must be terminated using the BREAK<hx> command.
You are automatically placed in a restricted shell. Type “help” to display a
command list. The commands available during an SDMRLogin session are
as follows:

bsyapp followed by the application number, moves an application into the

ManB state.

bsyhw followed by the domain number (0 or 1), and the device name, moves
a hardware module to the ManB state. The bsyhw command can also be
used with the FORCE option.

help displays help for commands for the SDMRLogin session. Type HELP
for a list of all commands. Type HELP, followed by a command name, for
help on a specific command.

rtshw followed by the domain number (0 or 1), and the device name, returns
a hardware module to the InSv state.

rtsapp followed by the application number, returns an application to the

InSv state.

offlapp followed by the application number, moves an application to the

OffL state from the ManB state.

locatedisplays location information on SDM hardware modules, and the

devices they support.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-18 SDM maintenance overview

querySDM with no parameters, displays the status of the SDM, and the
number of out-of-service links. QuerySDM FLT displays information on
SDM software and device faults. QuerySDM LOADS displays software
versions installed on the SDM, and their current states. QuerySDM
STATUS displays information on system software connectivity, including
applications and devices, and their states. QuerySDM CONFIG displays
configuration data related to the SDM.

logout logs you out of the SDM.

ls lists the commands available from the SDM Remote Login directory.

pingfollowed by the name or IP address of a network host confirms SDM

LAN connectivity to the network host. For example, ping cm confirms
connectivity to the CM.

ps reports UNIX process status.

who displays users logged on to the SDM.

who_is_on indicates the number of users logged in to the SDM, the number
of users logged on the maintenance menu system, and the state of the SDM.

Enter the Logout command to end the remote login session. Entering the
logout command returns you to the same MAP level from which you entered
the SDMRLogin command. If you enter the Ctrl-b<hx> command, you
return to the command interpreter (CI) level.

Error messages are displayed for the following reasons:

• The SDM is not in the InSv or ISTb state. Put the SDM in the InSv state
and reenter the SDMRLogin command.
• There are eight other SRL sessions active. The maximum number of
SDMRLOGIN sessions allowed from the CM to the SDM is eight.
• The SDM has been taken out of the InSv or ISTb state during an active
SDMRLogin session.
• A telnet session could not be established between the CM and the SDM.
• The terminal that you are using for the remote login does not suppress
the echoing of password entries. You may continue or exit the remote
login session.
• The terminal that you are using for the remote login is being used to
output DMS logs. You may continue or exit the remote login session.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-19

Monitoring SDM-related alarms at the MAP display

The MAP displays SDM alarms under the APPL header of the maintenance
level alarm banner and the SDM header of the APPL level alarm banner.
Figure 2-2 shows an example of an SDM alarm under the APPL header of
the maintenance level alarm banner.

Note: Power-related faults on the SDM also trigger a frame supervisory

panel (FSP) alarm under the external (Ext) header. The modular supervisory
panel (MSP) also provides an audible alarm, and visual indications on the
cabinet and at the end of the aisle.

Figure 2-2xxx
SDM alarms on the Maintenance banner

CM MS IOD Net PM CCS Lns Trks Ext APPL

. . . . . . . . SDM
*C*

Table 2-2 lists the following various maintenance level alarm values
• alarms associated with the SDM
• SDM node states that trigger the alarms
• meaning of each combination of alarm and node state
The SDM node states appearing at the MAP display, represent the CM view
of the state of the SDM. The SDM state at the MAP display is the true state
of the SDM whenever the communication link between the SDM and the
CM is functioning.

If the communication link between the SDM and the CM is not functioning,
the operating condition and local state of the SDM are unknown to the CM.
In this case, the CM designates the SDM as SysB, with a communication
fault, as described in table 2-2. Under these conditions, the SDM state
displayed at the MAP interface and the local node state of the SDM (as it
appears on the RMI) may be mismatched.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-20 SDM maintenance overview

Table 2-2xxx
SDM alarms at the MAP alarm banners

Associated
Alarms on SDM alarm SDM state
Maintenance in APPL at the MAP
banner banner interface Meaning

APPL SDM ISTb An APPL SDM minor alarm is present. The CM is

SDM ISTb receiving in-service trouble (ISTb) status from the
SDM. One or more of the following conditions
may exist:
• One or more SDM applications cannot run, but
at least one application is running
successfully.
• The SDM cannot communicate with one or
more of the operating company LAN nodes
defined on the SDM.
• A system software resource threshold has
been exceeded.
• An SDM application has reported an ISTb
condition.
• A non-critical hardware fault is present.
• At least one, but not all, DS512 links are out of
service.
• The SDM has been declared a minor babbler
by the MS. The SDM is sending too much
information before receiving
acknowledgements. See page 2-12 for more
information.
• Disk mirroring is in progress or has failed.
• There is an IP mismatch between the CM and
the SDM.
• A file system has exceeded its alarm threshold
or any volume group is not InSv.
• There is a fault with Distributed Computing
Environment (DCE).
APPL SDM ManB An APPL SDM minor alarm is present. The SDM
SDM ManB has been manually busied by command at the
MAP interface.

—continued—

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-21

Table 2-2xxx
SDM alarms at the MAP alarm banners (continued)

Associated
Alarms on SDM alarm SDM state
Maintenance in APPL at the MAP
banner banner interface Meaning

ManB (NA) An APPL SDM minor alarm is present. The SDM

has been manually busied by command at the
MAP interface. The CM cannot communicate with
the SDM because the DS512 links cannot transmit
or receive messages. The operating condition and
local state of the SDM are unknown to the CM
until at least one DS512 link is restored.
ManB/The An APPL SDM minor alarm is present. The SDM
SDM is not has been manually busied by command at the
responding MAP interface. The CM is not receiving messages
from the SDM. The operating condition and local
state of the SDM are unknown to the CM until
communications with the SDM are restored.
APPL SDM SysB An APPL SDM critical alarm is present. The CM
SDM SysB has designated the SDM node state as system
*C* *C* busy. One or more of the following conditions
exist:
• The CM is receiving system-busy status from
the SDM.
• The SDM is a major or critical babbler.
• All software applications on the SDM have
failed.
SysB (NA) An APPL SDM critical alarm is present. The CM
has designated the SDM node state as system
busy. The CM cannot communicate with the SDM
because the DS512 interface is unavailable to
transmit or receive messages. The operating
condition and local state of the SDM are unknown
to the CM until communications are restored.

—continued—

Wireless Networks Family SDM–SX User Guide SDMPL011

2-22 SDM maintenance overview

Table 2-2xxx
SDM alarms at the MAP alarm banners (continued)

Associated
Alarms on SDM alarm SDM state
Maintenance in APPL at the MAP
banner banner interface Meaning

SysB/The An APPL SDM critical alarm is present. The CM

SDM is not has designated the SDM node state as system
responding busy. The SDM node state can be SysB for the
following reasons:
• Communication links between the CM and the
SDM are not operating. The operating
condition or local state of the SDM are
unknown to the CM until communications with
the SDM are restored.
• The SDM has been powered down or is
rebooting after being powered down.
Note: The SysB state is reported as an APPL SDM critical alarm. ISTb and ManB states are
reported as an APPL SDM minor alarm.

—end—

Logging in to the SDM

SDM maintenance and administration procedures included in this document
require logging in to the SDM as either the root user or the maintenance
(maint) user. Maintenance users are only allowed to perform surveillance
and maintenance activities, and change their own passwords.

CAUTION
SDM failure
Log in as the root user only when the procedure you are
performing requires it. Otherwise, log in as a maint user.
If you are logged in as the root user, use caution when
copying, storing, or removing any files on the SDM.

Copying and storing files in a logical volume, or

removing files from a logical volume, may cause the
SDM to fail.

This section describes how to log in to the SDM as the root user or the maint
user, and shows the screens that are displayed.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-23

At the prompt, log in to the SDM by typing

login: user
and pressing the Enter key.
where
user is either “root” for root user, “maint” for maintenance user

Enter the required password at the prompt by typing

User’s Password: password
and pressing the Enter key.
where
User is the userID (root, maint) of the user entered at login

password is the userID password

Root user login

When the root user user logs in, the system displays the following
information:
• the last unsuccessful login
• the last login
• the number of local users who logged in locally
• the number of users who logged in to the SDM using ETA
• the number of users who logged in to the CM using ETA
• an alarm banner that displays the status of the SDM and its major
components
Last unsuccessful login: Tue Feb 3 10:43:21 EST on /dev/pts/14 from
47.208.10.44
Last login: Tue Feb 3 15:58:42 EST 1998 on /dev/pts/21 from cm

There are 22 local logins.

There are 2 ETA logins to the SDM.
There are 3 ETA logins to the CM.

Current SDM status:

SDM CON LAN APPL SYS HW
. . . . . .

Maint user login

When the maint user user logs in, the system displays the number of
unsuccessful login attempts since the last login, the last unsuccessful login,
the last login, and an alarm banner that displays the status of the SDM and
its major components. (See page 2-42 for more information on the alarm

Wireless Networks Family SDM–SX User Guide SDMPL011

2-24 SDM maintenance overview

banner,) The system also indicates whether there are other users logged on
to the SDM or the CM by way of the ETA. Figure 2-3 shows the screen that
is displayed when a maint user logs in to the SDM.

Note: All users, except the root user, see the screen shown in figure 2-3.

Figure 2-3xxx
Maint user login

Last login: Fri Nov 21 10:08:12 EDT 1997 on /dev/pts/4 from 47.208.0.93

There are 8 local logins.

There are no ETA logins to the SDM.
There are no ETA logins to the CM.

Current SDM status:

SDM CON LAN APPL SYS HW
. . . . . .

Return key and Enter key

The carriage return key is identified in different ways (such as Enter, Return
or Carriage Return) on various types of terminals. It is always used to enter
commands and parameters into the system.

The procedures contained in this book and in other NTPs instruct you to
press the Enter key after each step. If your terminal has a Return key, press
the Return key instead. Do not press the Enter key located beside the
numeric key pad.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-25

Restricted shell
Figure 2-4 shows the list of restricted shell commands available to maint
users. This screen is displayed when maint users type HELP at the UNIX
prompt. To use the restricted shell after you have accessed the HELP, use
the Quit command.

At the UNIX prompt, enter the desired command. Type HELP to redisplay
the command list shown in figure 2-4. If you wish to access RMI from the
restricted shell, type “sdmmtc”.

Figure 2-4xxx
SDM restricted shell screen

The following commands are available:

sdmmtc - start the SDM Maintenance Interface
billmtc – start the SDM Billing Maintenance Interface
who_is_on – displays the users logged in to the SDM as well as
users logged into the Maintenance Menu System
who – displays users logged on to the SDM in long format
ping <host> – send ICMP ECHO_REQUEST packets to network hosts
logroute – invoke the Log Delivery commissioning tool
listlogfile – list all log files
copylogfile – copy one log file to another
dellogfile – remove log files
viewlogfile – view log file
ftplogfile – start ftp session to transfer log files
help – displays this help information
exit – logout of the SDM
maint:

Restricted shell commands

The commands available in the restricted shell are as follows:

sdmmtc accesses the RMI.

who_is_on indicates the number of users logged in to the SDM, and the
number of users using the RMI. It is useful to determine the number of
users on the system before performing service-affecting procedures.

who displays the names of the users logged on to the SDM, and the time at
which they logged on.

ping confirms SDM LAN connectivity to a network host.

logroute accesses the Log Delivery commissioning tool.

listlogfile lists all log files stored in the /data/logs directory.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-26 SDM maintenance overview

copylogfile copies one log file to another.

dellogfile removes log files stored in the /data/logs directory.

viewlogfile allows you to view a log file stored in the /data/logs directory.

allows you to begin an FTP session to transfer log files. (For more
ftplogfile
information, see page 2-26.)

help displays help information for the restricted shell.

exit logs you out of the SDM.

FTPLOGFILE command
The FTPLOGFILE command changes the current directory to /data/logs and
invokes an FTP client to transfer the log files. Invoking the FTPLOGFILE
command also invokes restricted file transfer protocol (RFTP). RFTP
functions as an FTP client, but some functions are removed to prevent maint
users from saving log files on the SDM.

The following list describes the FTP client commands that are available in
RFTP:
! escapes to the restricted shell.

$ executes a macro.

account sends an account command to a remote server.

append appends to a file.

ascii sets the transfer type to ASCII.

bell sounds a beep when the command is complete.

binary sets the transfer mode to binary.

bye terminates and exits the FTP session.

case toggles mget with uppercase and lowercase ID mapping.

cd changes the remote working directory.

cdup changes a remote working directory to its parent directory.

chmod changes the file permissions of a remote file.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-27

close terminates an FTP session.

cr toggles carriage return stripping when getting an ASCII file.

delete deletes a remote file.

debug toggles the debugging mode. Additional messages are displayed for a
better understanding of what the client is doing.

dir lists the contents of a remote directory.

disconnect terminates an FTP session.

form sets the file transfer format.

glob toggles metacharacter expansion (* and ?) of local file names.

hash toggles whether you wish to display the number of byte blocks
transferred.

help obtains information on any command.

idle sets the idle timer on the remote side.

image sets the transfer mode to binary.

lcd changes the local working directory.

lslists the contents of a remote directory. This command is enabled, but,

you cannot save the listing in a local file.

macdef defines a macro.

mdelete deletes multiple files.

mkdir makes a directory on the remote machine.

mode sets the transfer mode.

modtime determines the last time a file was modified.

mput sends multiple files from the SDM to the remote machine.

nmap sets templates for default file name mapping.

lists the contents of a remote directory. NLIST is the same as the LS

nlist
command, except the contents are not sorted.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-28 SDM maintenance overview

ntrans sets the translation table for default file name mapping.

open opens a connection to a remote file system.

prompt forces prompting on multiple commands.

proxy issues a command on an alternate connection.

sendport toggles the PORT command for each data connection.

put sends one file from the SDM to the remote location.

pwd obtains the working directory on a remote machine.

quit terminates and exits an FTP session.

sends an arbitrary FTP command. Quote is enabled, however, if the

quote
RETR command is invoked, the command is not allowed.

rstatus shows the status of a remote machine.

rhelp gets help from a remote server.

rename renames a file on the remote machine.

reset clears queued command replies.

restart restartsa file transfer at bytecount, a parameter given to restart the

transfer at a certain point.

rmdir removes a directory on a remote machine.

runique toggles the storing of unique copies of local files. If the file already
exists, a “.1” is appended to the file name.

send sends one file from the SDM to the remote location.

site sends a site-specific command to a remote server.

size determines the size of a remote file.

status shows the current status of any of the toggle commands, including the
type of transfer mode.

struct sets a file transfer structure.

system determines the remote system type.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-29

sunique toggles the storing of unique copies of remote files. If the file
already exists, a “.1” is appended to the file name.

tenex sets the transfer mode to tenex.

trace toggles packet tracing.

type sets the file transfer type.

user sends new user information.

umask sets default permission settings on the remote side.

verbose toggles whether you wish to display more messages on the screen.

? obtains local help information.

The following list describes the FTP client commands that are disabled
when RFTP is invoked:
get transfers a file from the remote location to the SDM.

mdir lists the contents of multiple remote directories.

mget transfers multiple files from the remote machine to the SDM.

mls lists the contents of multiple remote directories.

newer gets a file if the remote file is newer than the local file.

recv receives files.

reget gets a file restarting at the end of a local file.

When a disabled command is invoked, an error message is displayed. The

local change directory (LCD) command is enabled to allow the maint user to
change from the /data/logs directory to another directory, if required.

Node and application control commands

Node control commands change the state of the SDM. Application control
commands change the states of the application and service packages. The
SDM node and package states are influenced by each other. When the SDM
is in ManB state, all applications are in ManB state, unless they are in OffL
state. (Applications in OffL state would remain in OffL state.)

Wireless Networks Family SDM–SX User Guide SDMPL011

2-30 SDM maintenance overview

Note: SDM application states depend on the SDM node state. An

application in the ManB state when the SDM is returned to service will be
brought into service. This includes any applications that were manually
busied prior to when the SDM was busied. If you wish to keep an
application out of service, regardless of SDM node state changes, busy the
application and take it off-line.

Similarly, when some applications are ManB, ISTb, or failed state, the SDM
state becomes ISTb. If all applications are in ManB or failed state, the SDM
state becomes SysB. An application in OffL state does not affect the SDM
node state. An application can be returned to service if the SDM state is
InSv, ISTb, or SysB.

Node control commands can only be used locally (from the SDM RMI) if
there is no connectivity between the SDM and the CM. Application control
commands can be used regardless of connectivity between the SDM and the
CM. Node and application commands can be entered at the input command
line by root or maint users during an SDMRLogin session.

Note 1: The root user can use the command line interface at any time to
execute any of the node and application control commands.
Note 2: Node and application commands are not available when maint users
telnet to the SDM. Restricted shell commands are available. When a maint
user establishes an SDMRLogin session, restricted shell commands are
available. However, the user does not have access to the RMI.
Messages are displayed when these restricted shell commands are executed
successfully and when they fail. Commands time out if they cannot
communicate with the node control process. If a command fails, try the
command again. If it continues to fail, contact your next level of support.

Note 3: The node control commands BSYSDM, RTSSDM, OFFLSDM,

REBOOTSDM, and HALTSDM cannot be used during an SDMRLogin
session.
Table 2-3 lists node control commands and their meanings. Application
control commands are listed in table 2-4.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-31

Table 2-3xxx
Node control commands

Command Meaning

BSYSDM [FORCE] This command puts the SDM into the ManB state. This command can
also be used with the FORCE option. (Use the FORCE option with
caution. It ensures that the state change takes place. However, all
errors [IP mismatch] are ignored and checks are bypassed.) No
notification is sent to inform you when the command is complete. Use
QuerySDM to determine when the command has completed.

This command fails if one of the following conditions exists:

• The SDM is already in the ManB state.
• A command is in progress. (BSYSDM with the FORCE option
overrides any commands in progress.)
• The SDM is connected to the CM. Execute the command from
MAPCI.
• Invalid syntax has been entered.
• There is no response from internal software.
RTSSDM [FORCE] This command puts the SDM into the InSv state. This command can
also be used with the FORCE option. (Use the FORCE option with
caution. It ensures that the state change takes place. However, all
errors [IP mismatch] are ignored and checks are bypassed.)

Note: When the SDM or one of its applications or services is returned to

service from a manual busy (ManB) state, the state of the SDM may
move to in-service (InSV) briefly, then to in-service-trouble (ISTb) for a
few minutes, and finally back to InSv. The ISTb state is the result of the
application not being fully capable of supplying service during
initialization. For example, if the Operations Measurements application
is not yet InSv, the Exception Reporting application will be ISTb.

This command fails if one of the following conditions exists:

• The SDM is not in the ManB state.
• A command is in progress. (RTSSDM with the FORCE option only
overrides checks and errors, such as an IP address. A command in
progress causes the RTSSDM FORCE command to fail.)
• The SDM is connected to the CM. Execute the command from
MAPCI.
• There is an IP address mismatch. (RTSSDM with the FORCE
option overrides IP address checks and errors.)

—continued—

Wireless Networks Family SDM–SX User Guide SDMPL011

2-32 SDM maintenance overview

Table 2-3xxx
Node control commands (continued)

Command Meaning

OFFLSDM This command puts the SDM in the OffL state from the ManB state.
This command fails if one of the following conditions exists:
• The SDM is not in the ManB state.
• A command is in progress.
• The SDM is connected to the CM. Execute the command from
MAPCI.
REBOOTSDM This command reboots the SDM. The SDM must be in the OffL or
ManB state. A broadcast message is transmitted to all terminals
connected to the SDM. This command fails if one of the following
conditions exists:
• The SDM is not in the OffL or ManB state.
• A command is in progress.
• The SDM is connected to the CM. Execute the command from the
MAPCI.
HALTSDM This command shuts down the SDM. The SDM must be in the OffL or
ManB state. The SDM must be physically power cycled when this
command is finished. A broadcast message is transmitted to all
terminals connected to the SDM. This command fails if one of the
following conditions exists:
• The SDM is not in the OffL or ManB state.
• A command is in progress.
• The SDM is connected to the CM. Execute the command from
MAPCI.

—end—

Table 2-4 lists application control commands and their meanings.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-33

Table 2-4xxx
Application control commands

Command Meaning

INITPROC This command tells the SDM that changes have been made to the
application configuration file. This command is only used during
installation of applications. It is not normally issued by users.
BSYAPP <package This command, followed by the package number (shown when
number> QuerySDM LOADS is executed), moves an application into the ManB
state. This command fails if one of the following conditions exists:
• The package (a group of software installed on the SDM) is already
in the ManB state.
• The package name is unknown.
• A command is in progress.
RTSAPP <package This command, followed by the package number (shown when
number> QuerySDM LOADS is executed), moves an application into the InSv
state from the ManB or SysB states.

Note: When the SDM or one of its applications or services is returned to

service from a manual busy (ManB) state, the state of the SDM may
move to in-service (InSV) briefly, then to in-service-trouble (ISTb) for a
few minutes, and finally back to InSv. The ISTb state is the result of the
application not being fully capable of supplying service during
initialization. For example, if the Operations Measurements application
is not yet InSv, the Exception Reporting application will be ISTb.

This command fails if one of the following conditions exists:

• The package is already in the InSv state.
• The package is in the OffL state.
• The package name is unknown.
• A command is in progress.
OFFLAPP <package This command, followed by the package number (shown when
number> QuerySDM LOADS is executed), moves an application into OffL state
from ManB state. This command fails if one of the following conditions
exists:
• The package is not in the ManB state.
• The package name is unknown.
• A command is in progress.

—continued—

Wireless Networks Family SDM–SX User Guide SDMPL011

2-34 SDM maintenance overview

Table 2-4xxx
Application control commands (continued)

Command Meaning

QUERYSDM This command displays the following information:

[FLT|LOADS
• QuerySDM with no options displays the state of the node (default),
STATUS|CONFIG]
and the number of links out of service.
• QuerySDM FLT displays all faults on the system.
• QuerySDM LOADS displays the installed and registered application
packages, their version numbers, and their current states and
numeric identifiers.
• QuerySDM STATUS displays the status of system components.
• QuerySDM CONFIG displays the contents of the SDM configuration
file, which lists all commissioned and configurable values.
LOCATE This command displays location information for hardware modules.

—end—

Maintaining the SDM using the remote maintenance interface

The RMI is the secondary maintenance, administrative, and diagnostic tool
for the SDM. This ASCII-based display provides maintenance information
about the overall state of the SDM, alarms, SDM and CM connectivity,
application software, operating system resources, and hardware.

System administration functions include administering user accounts,

software updates, and backup and restore. A restricted shell provides
maintenance users with additional diagnostic tools that are useful for
monitoring and maintaining the system. Context-sensitive help is provided
for all menu screens.

The RMI can be used to alter the state of the SDM if communications
between the SDM and the CM are not functioning. Otherwise, state changes
must be performed at the MTC APPL level of the MAP interface, as
described on page 2-2.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-35

Figure 2-5 shows the top and maintenance menu levels of the RMI. The top
menu level is the starting point for RMI maintenance and administrative
functions. RMI maintenance screens are similar to MAP display screens.
Each RMI maintenance screen contains an alarm banner, command list,
input and output areas, and a clock. The maintenance level functionality is
described in this section. Administrative functions are described in the
“SDM system administrative overview” chapter on page 3-4.

Figure 2-5
RMI maintenance levels

TOP

MTC ADMIN

CON LAN APPL SYS HW

STORAGE

Accessing the remote maintenance interface

There are several methods to access the RMI:
• dialing into the console port (SP0) on the SDM from a
VT100-compatible terminal using a modem connection
• connecting a VT100-compatible terminal directly to SP0 on the CPU
controller module, using a null modem cable
• using a telnet connection from a workstation on the operating company
LAN if telnet is enabled on the SDM. If telnet is not enabled, use the
ETA application (optional).
• using Enhanced Terminal Access (ETA) from a remote workstation to
log in to the SDM in a secure environment. ETA is an optional SDM
application.
• using a VT100-compatible terminal connected to a terminal server on the
operating company LAN, if telnet is enabled on the SDM. If telnet is not
enabled, use the optional ETA application.

Note: SDMRLogin cannot be used to access the RMI.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-36 SDM maintenance overview

Using telnet
Before you try to telnet, set your terminal to emulate a VT100 or an
80-character × 24-line xterm window.

Establish a telnet connection from a UNIX prompt by typing

>telnet sdm_ip_address
and pressing the Enter key.

where
sdm_ip_address is the IP address or the hostname of the SDM
For example, if the IP address of the SDM is 131.129.128.169, type

>telnet 131.129.128.169

When the connection is established, you can log in to the SDM using a valid
user name and password.

Note: Telnet must be enabled to use this method. The default state is
enabled. Nortel recommends that you use ETA to access the SDM remotely
because it authenticates all users in a secure environment. UserIDs and
passwords are passed across the network in an insecure environment when
you telnet to the SDM. ETA is an optional SDM application.

Using Enhanced Terminal Access

ETA is an optional SDM application that provides secure remote access to
the SDM across the operating company’s TCP/IP wide area network (WAN).
ETA is not part of the base platform. If your system includes ETA, telnet
must be disabled to use ETA.

Establish an ETA connection from a UNIX prompt by typing “eta”, and

pressing the Enter key. Figure 2-6 shows the Distributed Computing
Environment (DCE) login screen that is displayed after you establish an
ETA connection. Enter your DCE userID in the principal name field. Use
the tab key to move to the password field. Enter your DCE password, and
press the Enter key or select “OK”.

Note: For more information on the ETA application, refer to the NTP,
SuperNode Data Manager Enhanced Terminal Access User Guide.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-37

Figure 2-6xxx
DCE login window

Principal name

Password

OK Abort

Figure 2-7 shows the Enhanced Terminal Access menu that is displayed
following successful DCE login. This menu displays a list of the switches
which have SDMs in the DCE cell. Highlight a switch name and select
“Access SDM”.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-38 SDM maintenance overview

Figure 2-7xxx
Enhanced Terminal Access window

File Options

Switch Names

OTWAON10FCC
CGRYAB31ABC
WASHDC01FBI
ATLAGA09PEA
WINNMB45COL
LNDNON66WES

Access SDM Access CI/MAP

At the UNIX prompt, access the RMI by typing “sdmmtc”, and pressing the
Enter key.

Using a dial-up connection

Nortel recommends that you use the General DataComm (GDC)
maintenance modem provided with the SDM equipment whenever a console
dial-up modem connection to the SDM from a remote location is required.

For more information on using a dial-up connection to the SDM, refer to the
procedure ”Establishing a modem connection” on page 4-79 in the “SDM
maintenance procedures” chapter of this document.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-39

Static and dynamic information

The RMI displays two types of information – static and dynamic. Static
information is displayed once each time you request it. Static information is
displayed when the QuerySDM, Logs, Tst and Locate commands are
invoked. The information displayed from these commands does not change
until the command is executed a second time. Dynamic information is
displayed at the maintenance menu levels, and at the RMI alarm banner.
The information displayed does not depend on your input. It is updated
whenever there is a change. For example, the alarm banner displays major
components on the SDM and their states. If an application goes to ISTb
state, the APPL component under the alarm banner automatically changes to
ISTb.

Static information is displayed below dynamic information when there is

enough room to include both dynamic and static information. If there is not
enough room, the dynamic information disappears. If MORE is shown at
the command input line, there are additional screens of static information.
Press the Enter key to display additional screens. When the last screen of
static information is displayed, pressing the Enter key clears the output
window and re-displays any dynamic information.

Note: The current state of all hardware modules can be seen dynamically at
the hardware (HW) menu level of the RMI, or the platform MAP level under
the SDM MAP level. The current state of the hardware modules can be
viewed statically with the “MAPCI>QUERYSDM STATUS” command or
the “SDM>QUERYSDM STATUS” command.

Using the RMI menu system

Navigation through the maintenance menu system is linear, meaning that
each menu has only one path leading to it. From any menu, you can do the
following:
• return to the top level of the RMI by typing TOP
• return to the previous menu (except from the top level) by entering the
menu name or using the quit command
• go to a level of the RMI by entering one of the menu names that appear
in the alarm banner, with the exception of SDM
• type the corresponding menu level number or the menu name to access a
menu. For example, to go to the maintenance menu level of the RMI,
select option 2 from the top menu level of the RMI. Alternatively, you
can type MTC at any menu level of the RMI.
• type QUIT ALL to exit the RMI

Wireless Networks Family SDM–SX User Guide SDMPL011

2-40 SDM maintenance overview

• type d <# lines> to scroll down when the dynamic output extends beyond
the current screen. Typing “d” without specifying the number of lines
scrolls down to either the end of the display or the end of the current
page. Typing “d” with the specified number of lines scrolls down to
either the specified number of lines or to the end of the display.
• type u <# lines> to scroll up when the dynamic output extends beyond
the current screen. Typing “u” without specifying the number of lines
scrolls up to either the start of the display or the start of the current page.
Typing “u” with the specified number of lines scrolls up to either the
specified number of lines or the start of the display.

Note: You must press the Enter key after typing each of the RMI commands
described above.

The following set of navigation and interface commands is available at any

maintenance menu level of the RMI:
• The Quit command is always displayed with the other RMI commands
that are available at the current maintenance menu level. Quit is used to
go back to the previous menu. Use this command by typing QUIT or 0
(menu option for Quit). The Quit All command allows you to exit the
RMI from any maintenance menu level, and from the administration and
access menu levels. Use this command by typing QUIT ALL or 0 ALL,
and pressing the Enter key.
• The QuerySDM command can be invoked at any maintenance level
menu of the RMI except the Storage sub-level. QuerySDM has a
number of options that provide different types of information about the
SDM. Use the QuerySDM command by typing QUERYSDM or 14
(menu option for QuerySDM) followed optionally by one of the
QuerySDM parameter values (FLT, STATUS, CONFIG, or LOADS).
See page
• The Locate command can be invoked at any maintenance menu level of
the RMI with the exception of the storage sub-level. Locate provides a
list of modules installed on the SDM and their locations. Use the Locate
command by typing LOCATE or 15 (menu option for Locate). See page
2-76 for more information on the Locate command.
• The Help command is always displayed with the other RMI commands
that are available at the current menu level. The Help command gives
information on a menu or on a command, and how to use it. Help
messages are also displayed when incorrect information is entered. Use
this command by typing the following:
— HELP or 17 (menu option for Help) to get information on the current
screen, and on commands available at that level
— HELP and a command name or by typing 17 and a command name
to get information on that command

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-41

• The Refresh command is always displayed with the other RMI

commands that are available at the current menu level. Use this
command to refresh the screen after using a command that displays static
information, such as Locate or QuerySDM. Use this command by
typing REFRESH or 18 (menu option for Refresh).

The following sections describe each of the menus and displays in the RMI,
and the functionalities they provide.

Top menu level of the RMI

Figure 2-8 shows the top menu level of the RMI, and highlights the major
components found on RMI menu levels.

Note: Users must type “sdmmtc” at the UNIX after logging in.

Figure 2-8xxx
Top menu level of the RMI

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : OtWAONXBCS0
. . . . . . SDM: bmerye76
Fault Tolerant

Mtc
0 Quit
2 Mtc
3 Admin
4
5
6
7
8
9
10
11
12
13
14
15
16
17 Help
18 Refresh

root
Time 19:48 >

This screen is the entry point into the RMI menu system, which is split into
maintenance (Mtc) and administrative (Admin) functions. Figure 2-8 also
shows the common information found on RMI menu screens.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-42 SDM maintenance overview

Note: Administrative functions of the RMI are described in the “SDM

system administrative overview” chapter on page 3-4. To re–access the Top
menu level of the RMI, type TDP from any RMI menu level.

Monitoring SDM status and alarms at the RMI

Each maintenance menu level displays an alarm banner. The information in
the alarm banner is dynamically updated to show the overall state of the
SDM, and the states of its major components. The alarm banner is identical
at all menu levels.

The alarm banner is also displayed at the administration menu level of the
RMI (the starting point for RMI administrative functions). The alarm
banner is also displayed at the access menu level. The alarm banner is not
displayed when the following options are selected from the administration
menu level of the RMI:
• time
• user
• backup
• install

When all SDM components are functioning normally, the alarm banner
shows all components in-service. When SDM faults are detected, the
affected component under the alarm banner dynamically changes from
in-service state to the appropriate fault state. A symbol below each major
component in the alarm banner indicates that component’s state.

The following six components are displayed in the alarm banner:

• SDM displays the overall status of the SDM.
• CON displays the status of the SDM connections to the CM, and the
state of DS512 links. See page 2-49 for more information about this
menu level.
• LAN displays the status of the connectivity to the operating company
LAN. See page 2-53 for more information about this menu level.
• APPL displays the status of the software applications running on the
SDM. See page 2-56 for more information about this menu level.
• SYS displays the status of AIX operating system resources and logical
volumes. See page 2-60 for more information about this menu level.
• HW displays the status of all hardware devices connected to the SDM.
See page 2-68 for more information about this menu level.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-43

All components, except SDM, have their own menu levels that display
further information to assist you in determining why the alarm has occurred.
These menus can be accessed at any level of the RMI by typing the
component name. For example, access the connectivity (Con) menu level of
the RMI by typing CON. SDM node states are described in table 2-6.
Additional information on a particular component can be obtained by using
the QuerySDM command.

SDM major component states are described in table 2-5. States are
displayed symbolically under each component in the alarm banner. These
states can also be displayed on the CM through the QuerySDM status
command, however, additional details at the connectivity, LAN and system
(Sys) menu levels of the RMI are not displayed. (See table 2-6 for the
meaning of the symbols that are displayed on the RMI.)

Table 2-5xxx
SDM components at the RMI

SDM Alarm
component banner
at RMI symbol Explanation and action

SDM Refer to table 2-6 for information on the SDM state.

CON . The SDM is receiving heartbeats from the CM, and there is no IP
mismatch between the SDM and the CM. All DS512 links are InSv.

I There is an IP mismatch or some of the DS512 links are down.

S The SDM is not receiving heartbeats from the CM.

Check for alarms under the APPL header of the alarm banner at the
MTC level of the MAP display. If the SDM is not communicating with the
CM, an SDM critical alarm is displayed at the MAP interface. Use the
procedure ”Clearing MAP alarms triggered by the SDM - APPL SysB
critical” in this document to isolate and clear the fault.

—continued—

Wireless Networks Family SDM–SX User Guide SDMPL011

2-44 SDM maintenance overview

Table 2-5xxx
SDM components at the RMI (continued)

SDM Alarm
component banner
at RMI symbol Explanation and action

LAN . Connectivity between the SDM and the operating company LAN node(s)
is InSv. DCE is functioning normally.

S There is no connectivity between the SDM and the operating company

LAN nodes, and DCE is in SysB state. When DCE is in SysB state, the
SDM applications that use DCE automatically go in ISTb state, and can
no longer operate.

I Connectivity between the SDM and one or more of the operating

company LAN nodes is failing, or an abnormal condition has been
observed with DCE.

To isolate and clear the fault, use the procedure ”Clearing MAP alarms
triggered by the SDM - APPL SysB minor” on page 4-3 in this
document. If the problem is with DCE, refer to the troubleshooting
information in the “SDM system administration overview” chapter of this
document.

Note: If DCE has not been configured using the SDM commissioning
tool, or DCE has not been configured correctly, the DCE state is
unequipped (uneq). If DCE is unequipped, it is not included in the
calculation of the overall LAN or SDM state.

—continued—

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-45

Table 2-5xxx
SDM components at the RMI (continued)

SDM Alarm
component banner
at RMI symbol Explanation and action

APPL . All applications on the SDM are functioning normally.

I One or more applications has reported an ISTb or failed condition. If

there is a mix of different states for the applications, the overall state for
APPL is ISTb.

M All applications have been manually stopped.

S All applications have failed.

O All applications have been put in OffL state. The OffL state does not
generate a alarm.

Use the procedure ”Clearing MAP alarms triggered by the SDM - APPL
SysB minor” on page 4-3 in this document.

Note: The APPL state indicates the state of all applications that are not
in the OffL state.
SYS . There is no operating system software alarm.

I There is one or more operating system software alarms.

Use the procedure ”Clearing MAP alarms triggered by the SDM - APPL
SysB minor” on page 4-3 in this document.
HW . All hardware devices are in service.

I One or more hardware devices are not in service.

Use the QuerySDM and Trnsl commands to isolate the hardware fault.
If required, follow the appropriate hardware replacement procedure in
this document.

Note: The Trnsl command can only be used at the MAP display.

—end—

Commands at the top menu level

The following commands are available at the top menu level of the RMI:
• Mtc is the entry point into the maintenance portion of the RMI. This is
the starting point for all maintenance activities.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-46 SDM maintenance overview

• Admin is the entry point into the administrative portion of the RMI.
This is the starting point for all administration activities.
(Administrative functions of the RMI are described in the “SDM system
administrative overview” chapter on page 3-4.)

Maintenance menu level of the RMI

Figure 2-9 shows the maintenance menu level of the RMI. This menu
provides the entry point for all maintenance functions on the RMI. In the
example shown, the SDM node state and all components are InSv or
functioning normally.

Select option 2 from the top menu level of the RMI to access the
maintenance level. You can also access the maintenance menu level by
typing MTC from any level of the RMI.

Figure 2-9
Maintenance menu level

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
. . . . . . SDM: SDM1

Mtc
0 Quit
2 Con
3 Lan
4 Appl
5 Sys
6 Hw
7 Bsy
8 RTS
9 OffL
10
11
12
13
14 QuerySDM
15 Locate
16
17 Help
18 Refresh

root
Time 19:48 >

Monitoring the SDM node state at the RMI

The SDM Node State: line appears at most maintenance menu levels of the
RMI. It is dynamically updated, and indicates the overall state of the SDM.
The node state of the SDM is also dynamically updated on the alarm banner
that appears on all maintenance menu levels, and the administration menu
level of the RMI. SDM node states are described in table 2-6.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-47

Table 2-6xxx
SDM state indicators at the RMI

Alarm
SDM node banner
state at RMI symbol Meaning Explanation

InSv . in service There are no hardware or software faults on the SDM.

All applications, processes, hardware devices, and
CM and operating company LAN connections are
operational.
ISTb I in service The SDM node state is ISTb if one or more of the
trouble following faults have been reported on the SDM:
• A hardware component is not InSv.
• An operating system software alarm is present.
• Some application software package are not InSv
except OffL software packages.
• Communication between the CM and the SDM
has failed.
• The operating company LAN connectivity has
failed.
• A file system has exceeded its alarm threshold or
any volume group is not InSv.
SysB S system The SDM node state at the RMI shows SysB only if all
busy software applications on the SDM have failed.
ManB M manual The SDM has either received a ManB command from
busy the CM, or has been manually busied at the RMI while
communications to the CM are down. All application
and service software processes have stopped.
OffL O offline The SDM is offline, and is not communicating with the
CM. The SDM has received the OffL command from
the CM, or it has been set to the OffL state locally at
the RMI while isolated from the CM.

The SDM node state at the RMI is normally the same as the CM view of its
state at the MAP display. If the CM and the SDM are unable to
communicate, either because of a fault in the communications link, or
because the SDM is out of service, the node states at the RMI and the MAP
interface may be mismatched. However, when CM-SDM communications
are restored, the SDM node state at the RMI aligns to the current CM view.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-48 SDM maintenance overview

Commands at the maintenance menu level

The following commands are available at the maintenance menu level of the
RMI:
• CON displays the status of SDM connections to the CM. See page 2-49
for more information about this menu level.
• LAN displays the status of the connectivity to the operating company
LAN, and the state of DCE. See page 2-53 for more information about
this menu level.
• APPL displays the status of the software applications running on the
SDM. See page 2-56 for more information about this menu level.
• Sys displays the status of the AIX operating system resources and logical
volumes. See page 2-60 for more information about this menu level.
• HW displays the status of all hardware devices connected to the SDM.
See page 2-68 for more information about this menu level.
• BSY sets the SDM to the manual busy (ManB) state. Select option 7 or
type BSY to invoke this command.
• RTS returns the SDM to service from the ManB state. Select option 8 or
type RTS to invoke this command. The RTS command can also be used
with the FORCE option.
• OFFL is used to set the SDM to the offline state from the ManB state.
Communications between the CM and the SDM are disabled when this
command is executed. Select option 9 or type OFFL to invoke this
command.
• QuerySDM provides information about the status and configuration of
the SDM. The information displayed is always static. (Use the Refresh
command to delete the information displayed by this command.)
QuerySDM, without any parameters, displays information specific to the
current screen. QuerySDM can also be used with the FLT, LOADS,
STATUS and CONFIG options as follows:
— QuerySDM FLT displays all faults present on the SDM. For more
information on this command, see page 2-72.
— QuerySDM LOADS displays all software loaded on the SDM. For
more information on this command, see page 2-73. (At the
application level of the RMI, QuerySDM, without any parameters,
displays the same information. See page 2-58.)
— QuerySDM STATUS displays the status of all hardware devices on
the SDM. For more information on this command, see page 2-71.
(At the hardware level of the RMI, QuerySDM, without any
parameters, displays the same information. See page 2-69.)

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-49

— QuerySDM CONFIG displays all locally-commissioned datafill on

the SDM. For more information on this command, see page 2-75.
(At the system level of the RMI, QuerySDM, without any
parameters, displays the same information. See page 2-66.)
• REBOOTSDM is a hidden command that is used to reboot the SDM. It
is only available to root users and only at the maintenance menu level of
the RMI. The SDM must be in the OffL or ManB state to execute this
command.

CAUTION
Reboot message
When a RebootSDM command is issued, the following
message may appear on the SDM’s local console during
the reboot:
Board Configuration Data Failure
Ignore this message. It is not service-affecting.

• HALTSDM is a hidden command that is used to halt the SDM. It shuts

down the operating system on the SDM. A power recycle is required to
return the SDM to service. The SDM must be in the OffL or ManB state
to execute this command.

Connectivity menu level of the RMI

Figure 2-10 shows the connectivity (Con) menu level of the RMI. This
menu displays the status of the connections from the SDM to the CM. The
heartbeat and the IP address synchronization state of the SDM-CM-LAN are
displayed, as well as the states of DS512 connections. These state indicators
are updated dynamically. In the example shown, the SDM node state and
connectivity to the CM are ISTb. Two of the four DS512 links are closed.

Note 1: The Con menu level of the RMI can take up to 12 minutes to report
that all DS512 links have been closed. This will only occur if all the DS512
links are disconnected from the CM to the SDM. The SDM will report a
CM connectivity alarm due to lost heartbeats within 1 min. The CM will
report this problem immediately. Monitor the DS512 link status at the MS
MAP level.
Note 2: If all links are down for no obvious reason, and the CM, the MS
cards, and the DS512 controller module are in service, the DS512
personality module may be faulty. Replace the DS512 personality module.
If this does not correct the problem, contact Nortel for assistance.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-50 SDM maintenance overview

Note 3: If a single DS512 link remains out of service for more than two
minutes, there may be a link failure. Busy the link manually using the BSY
command from the MS level of the MAP. Then attempt to return it to
service using the RTS command. If the RTS command fails, contact your
next level of support.
Select option 2 from the maintenance menu level of the RMI to access the
connectivity level. You can also access this menu by typing CON from any
menu level of the RMI.

Figure 2-10xxx
Connectivity menu level

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : OTWAONXBCS0
I I . . . . SDM: BMERYE76
Con
0 Quit Heartbeat status: .
2 IP address synchronization .
3
4 Logs
5 DS512 Link States Open
6 Tst I/O domain 0, port 0: Open
7 I/O domain 0, port 1: Open
8 I/O domain 1, port 0: Open
9 I/O domain 1, port 1: Open
10
11
13
14 QuerySDM
15 Locate
16
17 Help
18 Refresh

root
Time 19:48 >

Logs at the connectivity menu leveI

Figure 2-11 shows static information that is displayed when the logs option
is used. The logs option displays the current logs associated with SDM to
CM connectivity. These logs describe the event, and the date and time it
occurred. They are generated when connectivity from the SDM to the CM is
lost or restored. The most recent log is displayed when a connectivity
problem occurs or when it is corrected. The order of the logs is predefined
by base software. Refer to table 2-7 on page 2-78 for more information
about SDM logs and the required actions.

To display the logs, select option 4 or type LOGS at the connectivity menu
level of the RMI. The dynamic information shown in figure 2-10 is replaced

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-51

by the static log information. Press the Enter key to scroll down the screen.
When the last screen of log information is shown, press the Enter key to
redisplay the information that was previously displayed.

Figure 2-11xxx
Logs at the connectivity menu level

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
I I . . . . SDM: SDM1
Con Log information retrieved on Thu Oct 9 08:54:36 1997:
0 Quit
2 SDM600 Connection has been established
3 Type: CM
4 Logs CM Link Up: heartbeat received by the CM
5 Tue Oct 7 08:43:51 1997
6 Tst
7 SDM600 DS512 link up
8 Module Location: Shf:SDMM, Slot:1, Port:0
9 Link open
10 Tue Oct 7 08:08:11 1997
11
12 SDM300 DS512 link down
13 Module Location: Shf:SDMM, Slot 12, Port:1
14 QuerySDM Link closed
15 Locate Tue Oct 7 08:32:41 1997
16
17 Help SDM600 DS512 link up
18 Refresh Module Location: Shft:SDMM, Slot 1, Port:0

root
Time 19:48 MORE...

QuerySDM at the connectivity menu level

Figure 2-12 shows the static information displayed when the QuerySDM
command with no options is used at the connectivity menu level of the RMI.
QuerySDM displays the CM and SDM IP addresses, and the CM/SDM
netmask below the information displayed at the connectivity menu level.

To use this command, select option 14 or type QUERYSDM. For more

information on using this command with its parameters, FLT, LOADS,
STATUS, and CONFIG, see page 2-71.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-52 SDM maintenance overview

Figure 2-12xxx
QuerySDM at the connectivity menu level

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
I I . . . . SDM: SDM1
Con
0 Quit SDM Node State: IsTb
2 CM Connectivity State: IsTb
3
4 Logs Heartbeat status: InSv
5 IP address synchronization: InSv
6 Tst
7 DS512 Link States:
8 I/O domain 0, port 0: Open
9 I/O domain 0, port 1: Closed
10 I/O domain 1, port 0: Open
11 I/O domain 1, port 1: Closed
12
13 CM IP address: 47.105.145.1
14 QuerySDM SDM IP address: 47.105.145.5
15 Locate SDM-CM netmask: 255.255.255.248
16
17 Help
18 Refresh

root
Time 19:48 >

Other commands at the connectivity menu level

The Tst command is used to test the connectivity of the DS512 links to the
CM. The links you wish to test must be closed from the CM before you can
test their connectivity. The Tst command displays static information. To
test a specific link, use the options, DOMAIN and PORT. If the domain and
port numbers are not specified, all links are tested.

Determine the number for DOMAIN as follows:

• Use 0 for DOMAIN if the DS512 controller module is in slot 1 of the
main chassis.
• Use 1 for DOMAIN if the DS512 controller module is in slot 12 of the
main chassis

Use 0 for PORT if you are testing port 0, and 1 for PORT if you are testing
port 1.

For example, typing TST 0 1 to tests the link of the DS512 controller
module in domain 0, and port 1 on the DS512 personality module.

Change is a hidden command for root users only. This command allows you
to change an IP address. Type CHANGE. The system prompts you for

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-53

confirmation. You are prompted for the CM IP address, the SDM IP

address, and the CM-SDM LAN netmask. You may change any, all, or none
of these values. You are prompted to confirm the resulting values before the
change is made.

LAN menu level of the RMI

Figure 2-13 shows the LAN menu level of the RMI. This menu dynamically
updates the status of the connectivity from the SDM to up to four operating
company LAN nodes. The SDM node state, the overall state of the
operating company LAN, and the state of DCE, and the status of the DCE
server are also displayed. In the example shown, the SDM node is ISTb,
and the LAN and DCE states are InSv.

Select option 3 from the maintenance menu level of the RMI to access the
LAN menu level. You can also access this menu by typing LAN from any
menu level of the RMI.

Figure 2-13xxx
LAN menu level of the RMI

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
I I . . . . SDM: SDM1
LAN
0 Quit SDM Node State: IsTb
2 SDM LAN State: InSv
3
4 Logs
5 DCE State: InSv
6
7 # DESCRIPTION HOSTNAME ADDRESS STATE
8 1 626 machine bnode5f 47.105.144.7 InSv
9 2 DCE Server bnode61 47.105.144.9 InSv
10 3
11 4
12
13
14 QuerySDM
15 Locate
16
17 Help
18 Refresh

root
Time 19:48 >

Wireless Networks Family SDM–SX User Guide SDMPL011

2-54 SDM maintenance overview

Logs at the LAN menu level

Figure 2-14 shows the static information that is displayed when the logs
option is used. The logs option displays the current logs associated with
LAN connectivity. These logs describe the event, and the date and time it
occurred. The most recent log is displayed when connectivity from the
SDM to the operating company LAN is lost or not established. The order of
the logs is predefined by base software. Refer to table 2-7 on page 2-78 for
more information about SDM logs and the required actions.

To display the logs, select option 4 or type LOGS at the LAN menu level of
the RMI. The dynamic information shown in figure 2-13 disappears to
make from for the static log information. Press the Enter key to scroll down
the screen. When the last screen of log information is shown, press the
Enter key to re-display the information that was previously displayed.

Figure 2-14xxx
Logs at the LAN menu level

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
I I . . . . SDM: SDM1
LAN Log information retrieved on Thu Oct 9 08:54:36 1997:
0 Quit
2 SDM600 Connection has been established
3 Type: CM
4 Logs SDM: CM Link Up: heartbeat received by the CM
5 Tue Oct 7 08:43:51 1997
6
7 SDM600 Connection has been established
8 Type: CM
9 IP address mismatch cleared
10 Tue Oct 7 08:08:11 1997
11
12 SDM300 DS512 link down
13 Module Location: Shf:SDMM, Slot:1, Port:0
14 QuerySDM Link closed
15 Locate Tue Oct 7 08:32:41 1997
16
17 Help SDM300 DS512 link down
18 Refresh Module Location: Shf:SDMM, Slot:1, Port:1

root
Time 19:48 MORE...

QuerySDM at the LAN menu level

Figure 2-15 shows the static information that is displayed when the
QuerySDM command with no parameters is used at the LAN menu level of
the RMI. QuerySDM displays the SDM hostname, the SDM-to-operating
company LAN IP address, netmask, and gateway status below the
information displayed at the LAN menu level.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-55

To use this command, select option 14 or type QUERYSDM. For more

information on using this command with its parameters FLT, LOADS,
STATUS, and CONFIG, see page 2-71.

Figure 2-15xxx
QuerySDM at the LAN menu level

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
I S . . . . SDM: SDM1
LAN
0 Quit SDM Node State: IsTb
2 SDM LAN State: InSv
3
4 Logs
5 DCE State: InSv
6
7 # DESCRIPTION HOSTNAME ADDRESS STATE
8 1 626 machine bnode5f 47.105.144.7 InSv
9 2 DCE Server bnode61 47.105.144.9 InSv
10 3
11 4
12
13
14 QuerySDM SDM hostname: SDM
15 Locate SDM LAN IP address: 47.105.144.29
16 SDM LAN netmask: 255.255.240.0
17 Help SDM LAN gateway: Uncommissioned
18 Refresh

root
Time 19:48 >

Other commands at the LAN menu level

LAN nodes defined at the RMI are used for monitoring connectivity to hosts
on the operating company LAN. When a LAN node is defined at the RMI,
the SDM periodically checks its connectivity status and raises an alarm if
connectivity fails.
• Add is a hidden command, for root users only, that adds a LAN node
entry into the first available position. You are prompted to enter the
description, hostname, and IP address of the operating company node.
You will then be prompted to confirm, reject, or edit the values for the
first node.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-56 SDM maintenance overview

• Del is a hidden command, for root users only, that removes a specified
operating company LAN node entry. Delete a specific operating
company LAN node entry by typing DEL, followed by the node number
(1 to 4). The screen then displays the hostname, description, and IP
address of the operating company LAN node that you are deleting. You
are also prompted to confirm whether you wish to proceed with deleting
the operating company LAN node.

Change is a hidden command for root users only that changes LAN
parameter values. The parameters are LAN and the node number (1 to 4).
Use the Change command as follows:
• Type CHANGE LAN to change the operating company LAN parameter
values. The SDM hostname, and the operating company LAN’s IP
address, netmask and gateway are each displayed separately on the
screen. Press Enter after each one until you see all values displayed on
the screen. You will then be prompted to confirm, reject or edit the
values. Choose the appropriate response, and complete the desired
action.
• Type CHANGE, followed by the node number (1 to 4) to change a
specific operating company LAN node number. The description of the
specified operating company node, the hostname for the specified
operating company node, and the IP address for the specified operating
company node are each displayed separately on the screen. Press Enter
after each one until you see all values displayed on the screen. You will
then be prompted to confirm, reject or edit the values. Choose the
appropriate response, and complete the desired action.

Note: For information on commissioning SDM-LAN connectivity, refer to

the procedure ”Commissioning SDM-LAN connectivity” in the “SDM
maintenance procedures” chapter of this document.

Application menu level of the RMI

Figure 2-16 shows the application menu level of the RMI. This menu
displays the status of all application and service packages on the SDM. A
package is the SDM software related to a particular application or service.
The application menu level includes the package number, followed by the
package description, the version, and the current state of the package. In the
example shown, the SDM node state is ISTb. The overall SDM application
state is ISTb with three applications InSv and the SuperNode Billing
Application which is SysB (system busy).

Select option 4 from the maintenance menu level of the RMI to access the
application level. You can also access this menu by typing APPL from any
menu level of the RMI.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-57

Figure 2-16xxx
Application menu level

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
I . . I . . SDM: SDM1
Appl
0 Quit SDM Node State: ISTb
2 SDM Application State: ISTb
3
4 Logs
5 # Package Description Version m State
6 1 Log Delivery Service 11.0.29.0 InSv
7 Bsy 2 Table Access Service 11.0.29.0 InSv
8 RTS 3 OM Access Service 11.0.29.0 InSv
9 OffL 4 Exception Reporting 11.0.29.0 InSv
10 5 Secure File Transfer 11.0.29.0 OffL
11 6 Enhanced Terminal Access 11.0.29.0 OffL
12
13
14 QuerySDM
15 Locate Applications Showing: 1 to 6 of 6
16
17 Help
18 Refresh

root
Time 19:48 >

Logs at the application menu level

Figure 2-17 shows the static information that is displayed when the logs
option is used. The logs option displays the current logs associated with
SDM software packages. Each log describes the event, and the date and
time it occurred. The most recent log is displayed when a software
application is not running normally. The order of the logs is predefined by
base software. Refer to table 2-7 on page 2-78 for more information about
SDM logs and the required actions.

To display the logs, select option 4 or type LOGS at the application menu
level of the RMI. The dynamic information shown in figure 2-16 disappears
to make room for the static log information. Press the Enter key to scroll
down the screen. When the last screen of log information is shown, press
the Enter key to re-display the information that was previously displayed.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-58 SDM maintenance overview

Figure 2-17xxx
Logs at the application menu level

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
I I . . . . SDM: SDM1
Appl Log information retrieved on Thu Oct 9 09:45:53 1997:
0 Quit
2 SDM603
3 Package: pk1
4 Logs Process: pk1proc1
5 State: restarted
6 Tue Oct 7 00:00:51 1997
7 Bsy
8 RTS SDM0603
9 OffL Package: SDM_BASE.logs
10 Process: start_sdmlaq
11 State: started
12 Tue Oct 7 14:39:06 1997
13
14 QuerySDM SDM0603
15 Locate Package: SDM_BASE.logs
16 Process: start_RTOsf
17 Help State: started
18 Refresh Tue Oct 7 14:39:07 1997

root
Time 19:48 MORE...

QuerySDM at the application menu level

Figure 2-18 shows the static information that is displayed when the
QuerySDM command, with no parameters, is used at the application menu
level of the RMI. QuerySDM displays the status of software packages on
the SDM.

To use this command, select option 14 or type QUERYSDM. For more

information on using this command with its parameters, FLT, LOADS,
STATUS, and CONFIG, see page 2-71.

Note: QuerySDM at the application menu level of the RMI displays the
same information as QuerySDM LOADS at any RMI maintenance menu
level, and QuerySDM LOADS at the SDM MAP display level. See page
2-73 for more information on QuerySDM LOADS at the RMI, and page
2-11 for more information on QuerySDM LOADS at the SDM MAP display
level.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-59

Figure 2-18xxx
QuerySDM at the application menu level

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
. . . . . . SDM: SDM1
Appl
0 Quit
2 # Application State
3 1 Table Access Service .
4 Logs 2 Log Delivery Service .
5 3 OM Access Service
6 4 Secure File Transfer
7 Bsy 5 Enhanced Terminal Access
8 RTS 6 Exception Reporting
9 OffL
10 Applications showing: 1 to 6 of 6
11 # Package Description Version State
12 Platform Maintenance 11.0.18.0 –––––
13 1 Table Access Service 11.0.18.0 InSv
14 QuerySDM 2 Log Delivery Service 11.0.18.0 InSv
15 Locate 3 OM Access Service 11.0.18.0 InSv
16 4 Secure File Transfer 11.0.18.0 InSv
17 Help 5 Enhanced Termnal Access 11.0.18.0 InSv
18 Refresh 6 Exception Reporting 11.0.18.0 InSv

root
Time 19:48 MORE...

Other commands at the application menu level

The following commands are also available at this level:
• Bsy issues a busy command to a package. When a package is busied,
the execution of all software associated with that package is stopped. To
use this command, select option 7 or type BSY following the package ID
number.
• RTS issues a return-to-service command to a package. When a package
is returned to service, the execution of all software associated with that
application is restarted.
• The information derived from the RTS command is displayed beneath
the information currently displayed at the application level. Use the
Refresh command to redisplay the information that was previously
displayed.
• The FORCE option may be used with RTS to override the execution of
other commands. To use RTS with the FORCE option, type 8 FORCE
or type RTS FORCE, followed by the package ID number.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-60 SDM maintenance overview

ATTENTION
When the SDM or one of its applications or services is returned to
service from a manual busy (ManB) state, the state of the SDM may
move to in-service (InSV) briefly, then to in-service-trouble (ISTb) for
a few minutes, and finally back to InSv.

The ISTb state is the result of the application not being fully capable
of supplying service during initialization. For example, if the
Operations Measurements application is not yet InSv, the Exception
Reporting application will be ISTb.

• OffL issues an offline command to the package. The package must be in

ManB state before the offline command is invoked. An offline package
does not generate an alarm condition. The parameter for this command
is the package ID number.
• The information derived from the OffL command is displayed beneath
the dynamic information. To use this command, select option 9 or type
OFFL, followed by the package ID number.

System menu level of the RMI

Figure 2-19 shows the system menu level of the RMI. This menu provides
information about the operating system, including current CPU usage, swap
space, and process space. Resources that have exceeded their thresholds are
marked by an asterisk (*), and trigger an ISTb alarm.

In the example shown, the SDM node state is ISTb. The SDM storage state
is InSv.

Select option 5 from the maintenance menu level of the RMI to access the
system menu level. You can also access this menu by typing SYS from any
RMI menu level.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-61

Figure 2-19xxx
System menu level

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
. . . . . . SDM: SDM1
Sys
0 Quit SDM Storage State:
2
3 # Description Current / Threshold
4 Logs 1 CPU (run queue entries 0 / 5
5 Storage 2 Number of Processes: 65 / 250
6 3 Number of Zombies: 0 / 3
7 4 Swap Space (% full): 24 / 70
8 5 Number of Swap Queue Entries: 0 / 2
9
10
11
12
13
14 QuerySDM
15 Locate
16
17 Help
18 Refresh

root
Time 19:48 >

Logs at the system menu level

Figure 2-20 shows the static information that is displayed when the logs
option is used. The logs option displays the current logs associated with
system resources. Each log describes the event, and the date and time it
occurred. The most recent log is displayed when system software resources
exceed or return below their alarm thresholds. The order of the logs is
predefined by base software. Refer to table 2-7 on page 2-78 for more
information about SDM logs and the required actions.

To display the logs, select option 4 or type LOGS at the system menu level
of the RMI. The dynamic information shown in figure 2-19 disappears to
make room for the static log information. Press the Enter key to scroll down
the screen. When the last screen of log information is shown, press the
Enter key to redisplay the information that was previously displayed.

Note: When an alarm condition exists, the value displayed on the main
system level menu is the current value for the resource, whereas the value in
the log is the value that caused the threshold to be exceeded.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-62 SDM maintenance overview

Figure 2-20xxx
Logs at the system menu level

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
. . . . . . SDM: SDM1
Sys
0 Quit SDM Storage State:
2
3 # Description Current / Threshold
4 Logs 1 CPU (run queue entries 0 / 5
5 Storage 2 Number of Processes: 65 / 250
6 3 Number of Zombies: 0 / 3
7 4 Swap Space (% full): 24 / 70
8 5 Number of Swap Queue Entries: 0 / 2
9
10 Log information retrieved on Mon Dec 14 12:55:06 1998
11
12
13
14 QuerySDM
15 Locate
16
17 Help
18 Refresh

root
Time 19:48 >

Storage at the system menu level

Figure 2-21 shows the static information that is displayed when the storage
option is used at storage menu level of the RMI. The storage menu level
displays the SDM node, system, storage, and disk mirroring states. It also
displays the volume groups on the system, and their threshold values. The
system shown in figure 2-21 consists of the root volume group (rootvg) and
the data volume group (datavg).

Root users may add disks to the storage system, or change existing logical
volumes. Both root and maint users can display the current list of logical
volumes, including the available free disk space. To view the current list of

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-63

logical volumes, select option 5 at the system menu level of the RMI, or type
STORAGE at any RMI menu level.

CAUTION
Logical volume names
Logical volume names can be created using an unlimited
number of characters. However, a logical volume (LV)
name longer than 21 characters will appear truncated on
the storage menu level of the RMI because the storage
menu only displays 21 characters. When performing an
LV command, use the correct logical volume name
otherwise the command will fail.

The maximum number of logical volumes on a system that can be monitored

through the RMI is 32. In the example shown, seven logical volumes exist.
Rootvg is created automatically by the system at installation time. It
contains a base set of logical volumes that are required to start the system,
including paging space, journal log, boot data and dump storage.

Datavg requires the installation of the NTRX50GP or NTRX50FU I/O

controller module. When the I/O controller module is installed, datavg must
be created. The method by which this is done depends on whether the
system is a new system requiring datavg or an existing system that is
migrating to a rootvg/datavg system. For more information, refer to the
procedures, ”Creating a file system in the data volume group” on page 4-131
and ”Migration from a rootvg system to a rootvg/datavg system” on page
4-127 in the “SDM maintenance procedures” chapter in this document.

If there are additional disks on the system, the datavg volume group is
expanded with the new disks or, datavg is created using the new disks. All
SDM applications should write their data to datavg.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-64 SDM maintenance overview

Figure 2-21xxx
Storage menu level

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
I S . . I . SDM: SDM1
Storage
0 Quit
2 Volume Groups Status Free (MB)
3 rootvg Mirrored 2032
4 datavg Mirrored 11936
5
6 Logical Volume Location Size(MB) % full/ threshold
7 1/ rootvg 88 11/ 80
8 2/ usr rootvg 600 29/ 90
9 3 /var rootvg 200 5/70
10 4 /tmp rootvg 24 5/ 90
11 5 /home rootvg 304 4/ 70
12 6 /sdm rootvg 504 24/ 90
13 7 /data datavg 208 5/ 80
14 Logical volume showing; 1 to 7 of 7

15
16
17 Help
18 Refresh

root
Time 19:48 >

ATTENTION
Nortel recommends that logical volume management operations are
performed from the local console. Nortel also recommends that
logical volume management operations are not performed at the same
time by more than one user with root privileges.

Commands at the storage menu level

Add is a hidden command used by root users to add new disks or a logical
volume to the storage system. The parameter to add one or more disks to the
system is DSK. Add a new disk by typing ADD DSK.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-65

ATTENTION
A logical volume on the SDM must never reach 100% disk full. The
system enters into abnormal conditions when a logical volume reaches
100% disk full.

If the specified logical volume exceeds its alarm threshold, contact

your system administrator. The system administrator must assess the
current condition of the logical volume and take appropriate action
immediately. If required, contact Nortel for assistance.

To add a logical volume, use the following parameters:

• LV indicates a volume.
• VOLUME specifies the name of the volume group that you are creating.
All volume groups are appended to the directory “/data”. Do not
precede the name by “/”.
• SIZE specifies the size of the new logical volume (in Megabytes). Sizes
are rounded up to the next multiple of 4 Mbytes.

For example, typing ADD LV SBA 100 adds a 100-Mbyte file system called
SBA (SuperNode Billing Application).

Change is a hidden command used to expand an existing logical volume, or

to change the alarm threshold for a logical volume. The parameters to
expand an existing logical volume are as follows:
• LV indicates a volume
• VOLUME specifies the name of the volume from the storage menu level
of the RMI. The name must be preceded by “/”.
• SIZE specifies the expanded size of the logical volume (in Mbytes).
Sizes increased are rounded up to the next multiple of 4Mbytes.

For example, typing CHANGE LV SBA 120 expands the current logical
volume SBA by 120 Mbytes.

The parameters to change the alarm threshold for a logical volume are as
follows:
• ENTRYNUMBER specifies the item number to change. (The entry
number is shown to the left of the logical volume range in the storage
menu level of the RMI.)
• NEWTHRESHOLDVALUE specifies the new desired value.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-66 SDM maintenance overview

For example, typing CHANGE 2 80 changes the threshold of the /usr (item
2) volume group shown in figure 2-21 to 80 percent full.

QuerySDM at the system menu level

Figure 2-22 shows the static information that is displayed when the
QuerySDM command with no parameters is used at the system level of the
RMI. QuerySDM displays information on SDM configuration, including
CM connectivity. It also displays the performance log SDM620 pre-defined
time interval (TI).

To use this command, select option 14 or type QUERYSDM. For more

information on using this command with its parameters, FLT, LOADS,
STATUS, and CONFIG, see page 2-71.

The QUERYSDM command can also be used at the system menu level with
an additional parameter, TI. QuerySDM TI displays time interval
information about the performance log SDM620. This log reports current
SDM system performance data, such as CPU usage, number of processes,
swap space occupancy, and logical volume capacities. The pre-defined time
interval is the time in minutes between the generation of two successive
SDM620 logs.

To change the time interval, use the hidden command, CHANGE at the
system menu level. For more information on the Change command, see
”Other commands at the system menu level” on page 2-67.

Note: QuerySDM at the system menu level of the RMI displays the same
information as QuerySDM CONFIG at any RMI maintenance menu level,
and QuerySDM CONFIG at the SDM MAP display level. See page 2-75
for more information on QuerySDM CONFIG at the RMI. See page 2-11
for more information on QuerySDM CONFIG at the SDM MAP display
level.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-67

Figure 2-22xxx
QuerySDM at the system menu level

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
. . . . . . SDM: SDM1
Sys SDM Configuration
0 Quit
2 General
3 ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
4 Logs Platform: FT
5 Storage Console Login Greeting: Welcome to e75
6 Paging Space: 256
7
8 CM Connectivity
9 ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
10 Connectivity type: DS512
11 CM IP address: 47.31.195.1
12 EIU IP address (CM side): Uncommissioned
13 EIU IP address (SDM side): Uncommissioned
14 QuerySDM SDM IP address: 47.31.195.6
15 Locate SDM-CM netmask: 255.255.255.248
16 CM CLLI: FCC1
17 Help
18 Refresh LAN Connectivity

root
Time 19:48 MORE...

Other commands at the system menu leveI

Change is a hidden command for root users only. The CHANGE command
modifies current system threshold values or modifies the time interval value
that controls how often the performance log SDM620 is generated.

The parameters for changing system thresholds are ENTRYNUMBER (the

number shown under # header of the item whose value you wish to change)
and NEWTHRESHOLDVALUE (the new desired value). For example,
CHANGE 7 95.

For example, type CHANGE LV SBA 120 to expand the current logical
volume SBA by 120 Mbytes.

To change the performance log interval, type CHANGE TI and press the
Enter key. Then type the new value and press the Enter key again. You are
prompted to confirm the new value. The time interval must be entered in
minutes. The valid range for this value is 5 to 20 160 minutes, (2 weeks).
See ”Changing system thresholds” on page 4-140 for more information on
how to change the performance log SDM620 time interval.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-68 SDM maintenance overview

The default value for the time interval is 5 min. If a user enters a value of
less than 5 minutes, a warning message appears on the RMI system menu
and the system uses the default value of 5 min. The maximum value for the
time interval is 20 160 minutes or 14 days.

Hardware menu level of the RMI

Figure 2-23 shows the hardware menu level of the RMI. This menu displays
the status of hardware components on the SDM by deviceID in each domain.
In the example shown, the hardware component is ISTb because the CPU
controller module is ISTb. The overall SDM node state is also ISTb.

Select option 6 from the maintenance menu level of the RMI to access the
hardware menu level. You can also access this menu by typing HW from
any maintenance menu level of the RMI.

Figure 2-23xxx
Hardware menu level

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
. . . . . . SDM: SDM1
Hw
0 Quit
2 I I F F C E D D D D D D 5
3 C C A A P T S S S S S A 1
4 Logs M M N N U H K K K K K T 2
5 1 2 1 2 1 2 3 4 5
6 Domain 0 . . . . . . . . . . . . .
7 Bsy Domain 1 . . . . . . . . . . . . .
8 RTS
9
10
11
12
13
14 QuerySDM
15 Locate
16
17 Help
18 Refresh

root
Time 19:48 >

Logs at the hardware menu level

Figure 2-24 shows the static information that is displayed when the logs
option is used. The logs option displays the current logs associated with the
hardware devices. These logs describe the event, and the date and time it
occurred. The most recent log is displayed when the SDM detects that a
hardware device has been returned to the InSv state, or when a hardware

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-69

device is manually taken out of service. The order of the logs is predefined
by base software. The log displays the suspected module, its location and
PEC. It also indicates whether the module needs replacing, and displays
other devices on the module and their state. Refer to table 2-7 on page 2-78
for more information about SDM logs and the required actions.

To display the logs, select option 4 or type LOGS at the system menu level
of the RMI. The dynamic information shown in figure 2-23 disappears to
make room for the static log information. Press the Enter key to scroll down
the screen. When the last screen of log information is shown, press the
Enter key to re-display the information that was previously displayed.

Figure 2-24xxx
Logs at the hardware menu level

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
. . . . . . SDM: SDM1
Hw
0 Quit
2 I I F F C E D D D D D D 5
3 C C A A P T S S S S S A 1
4 Logs M M N N U H K K K K K T 2
5 1 2 1 2 1 2 3 4 5
6 Domain 0 . . . . . . . . . . . . .
7 Bsy Domain 1 . . . . . . . . . . . . .
8 RTS
9 Log information retrieved on Mon Dec 14 14:38:58 1998:
10
11
12
13
14 QuerySDM
15 Locate
16
17 Help
18 Refresh

root
Time 19:48 >

QuerySDM at the hardware menu leveI

Figure 2-25 shows the static information that is displayed when the
QuerySDM command with no parameters is used at the hardware menu
level of the RMI. QuerySDM displays information on SDM configuration,
including CM connectivity.

To use this command, select option 14 or type QUERYSDM. For more

information on using this command with the parameters, FLT, LOADS,
STATUS, and CONFIG, see page 2-71.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-70 SDM maintenance overview

Note: QuerySDM at the hardware menu level of the RMI displays the same
information as QuerySDM STATUS at any RMI maintenance menu level,
and QuerySDM STATUS at the SDM MAP display level. See page 2-71
for more information on QuerySDM STATUS at the RMI, and page 2-11 for
more information on QuerySDM STATUS at the SDM MAP display level.

Figure 2-25xxx
QuerySDM at the hardware menu level

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
. . . . . . SDM: SDM1
Hw
0 Quit
2 I I F F C E D D D D D D 5
3 C C A A P T S S S S S A 1
4 Logs M M N N U H K K K K K T 2
5 1 2 1 2 1 2 3 4 5
6
7 Bsy Domain 0 . . . . . . . . . . . . .
8 RTS Domain 1 . . . . . . . . . . . . .
9
10 A L S C I F F C E D D D D D D 5
11 P A Y O C C A A P T S S S S S A 1
12 P N S N M M N N U H K K K K K T 2
13 1 2 1 2 1 2 3 4 5
14 QuerySDM . . . . DO . . . . . . . . . . . . .
15 Locate D1 . . . . . . . . . . . . .
16
17 Help
18 Refresh

root
Time 19:48 >

Other commands at the hardware menu level

The following commands are also available at this level:
• Bsy busies a hardware device or module. Busying a specific device
busies all devices on the same module. For example, if you busy the
Ethernet LAN controller device on the I/O controller module, all
subtending devices (disk and tape drive) are automatically busied. The
parameters for the Bsy command are DOMAIN and DEVICENAME.
DOMAIN is 0 if the module is in slots 1 to 8, or 1 if the module is in
slots 9 to 16. DEVICENAME is the name of the device you wish to
busy, as shown at the hardware menu level. The information derived
from this command is displayed under the dynamic information. For
example, BSY 0 ETH or 7 0 ETH. The FORCE option may be used
with BSY to bypass error checks.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-71

• Add and Del (delete) are hidden commands for root users only. These
commands add and delete specified modules from the SDM. For more
information on how to add or delete modules, see the procedures
”Adding I/O controller modules” on page 4-59 and ”Removing I/O
controller modules” on page 4-67 in the “SDM maintenance procedures”
chapter in this document.
Note: For this product release, the I/O controller module (NTRX50FU)
is the only module that can be added to the system. This module will not
be functional until the next product release.

• RTS returns a device or module to service. The parameters for the RTS
command are DOMAIN (0 if the module is located in slots 1 to 8, and
DEVICENAME (as displayed on the hardware menu level). The
information generated by this command is displayed beneath the
dynamic information.

Note: Hardware modules must be returned to service at low traffic periods.

Returning them to service at high traffic periods can cause problems.

QuerySDM STATUS command

Figure 2-26 shows the static information that is displayed when the the
QuerySDM STATUS command is invoked. QuerySDM STATUS can be
invoked at any maintenance menu level of the RMI. QuerySDM STATUS
displays the status of SDM applications, SDM to operating company LAN
connectivity, system resources, and SDM-to-CM connectivity. Hardware
status in each domain is also shown. See page 2-47 for information on SDM
state indicators.

In the example shown, all components are InSv and all applications are
running. Connections to the operating company LAN and the DCE server,
as well as system resources are functioning normally. There are no
hardware faults.

Select option 14 with the STATUS option from any maintenance menu level
of the RMI to invoke this command. You can also access this menu by
typing QUERYSDM STATUS. The information is displayed below any
existing dynamic information that was displayed before the command was
invoked. Use the Refresh command to delete the static information.

Note: QuerySDM STATUS displays the same information as QuerySDM at

the hardware menu level of the RMI, and QuerySDM STATUS at the SDM
MAP display level. See page 2-69 for more information on QuerySDM at
the hardware menu level, and page 2-11 for more information on
QuerySDM STATUS at the SDM MAP display level.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-72 SDM maintenance overview

Figure 2-26xxx
QuerySDM STATUS command

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
. . . . . . SDM: SDM1
Mtc
0 Quit SDM Node State: InSv
2 Con
3 LAN A L S C I I F F C E D D D D D D 5
4 Appl P A Y O C C A A P T S S S S S A 1
5 Sys P N S N M M N N U H K K K K K T 2
6 HW
7 Bsy . . . . D0 . . . . . . .
8 RTS D1 . . . . . . .
9 OffL
10
11
12
13
14 QuerySDM
15 Locate
16
17 Help
18 Refresh

root
Time 19:48 >

QuerySDM FLT command

Figure 2-27 shows the static information that is displayed when the
QuerySDM command with the FLT option is invoked. QuerySDM FLT can
be invoked at any maintenance menu level of the RMI. This command
displays information that helps to isolate hardware, software and
connectivity faults on the SDM. QuerySDM FLT displays the following
information:
• the device or software package name where the fault resides
• the state of the device or software package
• the suspected module that contains the fault, and its location and PEC
• a process identification for the software fault
• other devices on the module, and their states
• a text reason detailing the fault (if available)
• a time stamp indicating the last state change

QuerySDM FLT displays the message “No local SDM fault to report” if
there are no hardware, software, or connectivity faults on the SDM. If there

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-73

is only one type of fault on the SDM (for example, software) only the
software faults appear on the display.

In the example shown, a cable fault exists on the LAN personality module.
The state of the device, its location, and possible reason for the fault are
given.

Select option 14 with the FLT option from any maintenance level of the RMI
to invoke this command. You can also access this menu by typing
QUERYSDM FLT. Some dynamic information may disappear when this
command is invoked. Use the Refresh command to delete the static
information displayed by this command.

Figure 2-27xxx
QuerySDM FLT command

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
. . . . . . SDM: SDM1
Mtc
0 Quit
2 Con
3 LAN No local SDM fault to report
4 Appl
5 Sys
6 HW
7 Bsy
8 RTS
9 OffL
10
11
12
13
14 QuerySDM
15 Locate
16
17 Help
18 Refresh

root
Time 19:48 >

QuerySDM LOADS command

Figure 2-28 shows the information that is displayed when QuerySDM with
the LOADS option is invoked. QuerySDM LOADS can be invoked at any
maintenance level of the RMI. This command lists all software loaded on
the SDM, and helps to isolate application faults. In the example shown, all
applications are running.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-74 SDM maintenance overview

Select option 14 with the LOADS option from any maintenance menu of the
RMI to invoke this command. You can also access this menu by typing
QUERYSDM LOADS. Some dynamic information may disappear when
this command is invoked. Use the Refresh command to delete the static
information displayed by this command.

Note: QuerySDM LOADS displays the same information as QuerySDM at

the application menu level of the RMI, and QuerySDM LOADS at the SDM
MAP display level. See page 2-58 for more information on QuerySDM at
the application level, and page 2-11 for more information on QuerySDM
LOADS at the SDM MAP display level.

Figure 2-28xxx
QuerySDM LOADS command

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
. . . . . . SDM: SDM1
Mtc
0 Quit SDM Node State: InSv
2 Con
3 Lan
4 Appl # Package Description Version State
5 Sys Platform Maintenance 11.0.18.0 ––––
6 Hw 1 Log Delivery Service 11.0.18.0 InSv
7 Bsy 2 Table Access Service 11.0.18.0 InSv
8 RTS 3 OM Access Service 11.0.18.0 InSv
9 OffL 4 Exception Reporting 11.0.18.0 InSv
10 5 Secure File Transfer 11.0.18.0 OffL
11 6 Enhanced Terminal Access 11.0.18.0 OffL
12
13
14 QuerySDM
15 Locate
16
17 Help
18 Refresh

root
Time 19:48 >

The following package state indicators are shown:

• “InSv” indicates that all package software is functioning, and no trouble
conditions are reported.
• “IsTb” indicates that one or more software processes in the package have
reported a trouble condition, or that one or more has failed.
• “ManB” indicates a package has been stopped manually.
• “OffL” indicates a package has been put in the offline state.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-75

• “Fail” indicates all UNIX processes associated with a package have

exceeded their daily threshold, and are no longer running.

QuerySDM CONFIG command

Figure 2-29 shows the information that is displayed when QuerySDM with
the CONFIG option is invoked. QuerySDM CONFIG can be invoked at any
maintenance menu level of the RMI. Use this command to determine
configuration settings that were set during commissioning of the SDM. This
command displays information on the following:
• the type of platform, the console login greeting, and paging space
• CM connectivity information, including CM and IP addresses, SDM-CM
netmask, and CM CLLI
• operating company LAN configurations, including IP addresses,
netmask, hostnames, LAN type, and whether FTP and telnet is enabled
or disabled
• system threshold values

Select option 14 with the CONFIG option from any maintenance menu of
the RMI to invoke this command. You can also access this menu by typing
QUERYSDM CONFIG.

Figure 2-29xxx
QuerySDM CONFIG command

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
. . . . . . SDM: SDM1
Mtc SDM Configuration
0 Quit
2 Con General
3 LAN –––––––––––––––––––––––––––––––––––––––––––––––––––––
4 Appl Platform: FT
5 Sys Console Login Greeting: Welcome to e76
6 Hw Paging Space: 256
7 Bsy
8 RTS CM Connectivity
9 OffL –––––––––––––––––––––––––––––––––––––––––––––––––––––
10 Connectivity type: DS512
11 CM IP address: 47.105.145.1
12 EIU IP address (CM side): Uncommissioned
13 EIU IP address (SDM side): Uncommissioned
14 QuerySDM SDM IP address: 47.105.145.5
15 Locate CM-SMD netmask: 255.255.255.248
16 CM CLLI: FCC1
17 Help
18 Refresh LAN Connectivity

root
Time 19:48 MORE...

Wireless Networks Family SDM–SX User Guide SDMPL011

2-76 SDM maintenance overview

Locate command
Figure 2-30 shows the static information that is displayed when the locate
command is invoked. Locate displays information on all modules in the
SDM, and their locations. The dynamic information displayed on a menu
before the Locate command was invoked may disappear to make room for
the information generated by the Locate command. Press the Enter key to
scroll down the screen. When the last screen of information is shown, press
the Enter key to re-display the information that was previously displayed.
Locate displays the following information:
• a description of the hardware device
• the module’s location and slot number (if applicable)
• the module’s PEC
• devices on the module

Select option 15 from any maintenance menu or type LOCATE to use this
command.

Figure 2-30xxx
Locate command

SDM Remote Maintenance Interface

SDM: CON: LAN: APPL: SYS: HW CM : FCC1

. . . . . . SDM: SDM1
Mtc Site Flr RPos Bay_id Shf Description Slot EqPEC
0 Quit HOST 01 A02 CSDM SDMM 512(0) 01 NTRX50GA FRNT
2 Con HOST 01 A02 CSDM SDMM 01 NTRX50GH BACK
3 LAN HOST 01 A02 CSDM SDMM ETH(0),DSK1(0),DAT(0) 02 NTRX50GN FRNT
4 Appl HOST 01 A02 CSDM SDMM 02 NTRX50FS BACK
5 Sys HOST 01 A02 CSDM SDMM DSK2(0),DSK3(0) 04 NTRX50GP FRNT
6 Hw HOST 01 A02 CSDM SDMM CPU(0) 06 NTRX50FK FRNT
7 Bsy HOST 01 A02 CSDM SDMM 06 NTRX50FD BACK
8 RTS HOST 01 A02 CSDM SDMM CPU(1) 10 NTRX50FK FRNT
9 OffL HOST 01 A02 CSDM SDMM 512(1) 12 NTRX50GA FRNT
10 HOST 01 A02 CSDM SDMM 12 NTRX50GH BACK
11 HOST 01 A02 CSDM SDMM ETH(1),DSK1(1),DAT(1) 13 NTRX50GN FRNT
12 HOST 01 A02 CSDM SDMM 13 NTRX50FS BACK
13 HOST 01 A02 CSDM SDMM DSK2(1),DSK3(1) 15 NTRX50GP FRNT
14 QuerySDM HOST 01 A02 CSDM SDMM FAN1(0) –– NTRX50FE FRNT
15 Locate HOST 00 A02 CSDM SDMM FAN1(1) –– NTRX50FF FRNT
16 HOST 01 A02 CSDM SDME ICM1(0) –– NTRX50FG BACK
17 Help HOST 01 A02 CSDM SDME ICM1(1) –– NTRX50FH BACK
18 Refresh HOST 01 A02 CSDM SDME DSK4(0),DSK5(0) 01 NTRX50FU FRNT

root
Time 19:48 MORE...

The list is sorted by shelf and slot numbers. The “SDMM” shelf value
indicates that the module is located in the main chassis. The “SDME” shelf

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-77

value indicates that the module is located in the I/O expansion chassis. The
description field contains the devices on the module and domain numbers.

SDM log reports

One type of log report provides information related to the SDM:
• SDM events are recorded internally to the SDM in a series of UNIX log
reports (SDM logs). These log reports are local to the SDM, and do not
appear in the generic DMS log utility stream. SDM logs are described in
table 2-7 on page 2-78.

SDM logs
The SDM generates detailed customer logs that are available on the SDM
RMI maintenance menu level and from the output of the SDM Log Delivery
application. From the RMI maintenance menu level, logs are available from
the CON/LAN/APPL/SYS and HW levels. SDM logs fall into three
categories: trouble (TBL) logs, state change logs, and information (INFO)
logs.

Trouble logs
TBL logs (SDM3xx) provide an indication of some type of fault for which
corrective action can be taken. These logs are generated for connectivity
failures, system resource problems, and application software and hardware
failures. Each of these trouble conditions corresponds to an alarm on the
SDM RMI alarm banner. When a TBL log is generated by the SDM, the
alarm is displayed under the appropriate component on the RMI alarm
banner to reflect the fault condition.

State change logs

State change logs (SDM5xx) provide information about SDM state changes
to InSv, ManB, ISTb, and SysB. While state changes from InSv to ISTb or
SysB require corrective action, the logs indicating these changes do not
provide detailed information about the reason for the state change. Specific
information is contained in the TBL logs.

When the SDM or the SDM Log Delivery is returned to service from a
ManB state, some logs may be delivered with the CM_CLLI in the Office
ID field of the log header, instead of the datafilled LOG_OFFICE_ID. This
occurs only for logs generated by SDM applications, and only occurs until at
least one log has been delivered that originated from a CM-based
application. The discrepancy corrects itself as soon as the first CM log is
received on the SDM.

Info logs
INFO logs (SDM6xx) provide information about events that do not normally
require corrective action. These logs are generated for system restarts, non
service affecting state changes, and for events that clear TBL logs.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-78 SDM maintenance overview

Table 2-7 lists the SDM logs generated by the SDM, describes the triggers
for each log, and provides a summary of the actions to take.

Table 2-7xxx
SDM logs generated by the SDM

Log Trigger Action

SDM300 The connection from the SDM to the CM See Fault diagnosis with SDM-CM
or the operating company LAN server(s) is communication out of service on page
down. 2-93. Contact your SDM system
administrator or Nortel for assistance.
SDM301 The maintenance system detects that a Check hardware faults, as mirroring
logical volume is not mirrored. may be lost due to a hard disk failure
on the SDM. If a disk has just been
replaced and brought back in-service,
the system may take more than 15
minutes to restore mirroring.
SDM302 The SDM has detected that a system Use the procedure for clearing an APPL
software resource has exceeded its SDM minor alarm on page 4-3 in the
threshold. “SDM maintenance procedures”
chapter of this document to isolate and
clear the problem.
SDM303 An SDM application or software has failed Users with root permissions can
more than three times in a day, or has examine the log files in /usr/adm to
declared itself to be in trouble. determine the cause of the process
failure. If required, contact your SDM
system administrator or Nortel for
assistance.
SDM304 The SDM Log Delivery application cannot Use the Log Delivery online
deliver logs to the specified UNIX file. commissioning tool (logroute) to verify
the existence and validity of the device
name. See page 2-81 for more
information on the logroute tool or the
procedure ”Log Delivery Device
commissioning” on page 4-84. If
required, contact your SDM system
administrator or Nortel for assistance.

—continued—

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-79

Table 2-7xxx
SDM logs generated by the SDM (continued)

Log Trigger Action

SDM306 SDM Table Access software has detected Upgrade the CM software to a version
that the CM software load is incompatible that is compatible with the SDM
with the SDM software load. software.

Note: SDM software should never be

at a lower release level than CM
software.
SDM308 Manual system image backup (S-tape) Check to ensure that the backup tape is
has failed. inserted. If required, contact your SDM
system administrator or Nortel for
assistance.
SDM309 A hardware device is faulty or has been Use the QuerySDM commands from
manually taken out of service. the MAP display. Refer to the
appropriate procedure in the “SDM
hardware replacement procedures” of
this document.

For all other faults, check the cabling to

the module. If you cannot determine
the reason for the fault, contact your
next level of support.
SDM315 SDM Table Access application has Contact your next level of support.
detected corruption in the Data Dictionary
on the CM.
SDM317 A Distributed Computing Environment Contact your next level of support to
(DCE) problem is detected. determine the cause of the failure.
SDM500 Indicates the initial startup of the SDM. None
This log is included in the SDM Log
Delivery log stream, but does not appear
on the RMI.
SDM501 Indicates an SDM state change to in None
service (InSv). This log is included in the
SDM Log Delivery log stream, but does
not appear on the RMI.
SDM502 Indicates an SDM state change to manual None
busy (ManB). This log is included in the
SDM Log Delivery log stream, but does
not appear on the RMI.

—continued—

Wireless Networks Family SDM–SX User Guide SDMPL011

2-80 SDM maintenance overview

Table 2-7xxx
SDM logs generated by the SDM (continued)

Log Trigger Action

SDM503 Indicates an SDM state change to system Refer to the procedure ”Clearing MAP
busy (SysB). This log is included in the alarms triggered by the SDM - APPL
SDM Log Delivery log stream, but does SDM critical” on page 4-25 in this
not appear on the RMI. document.
SDM504 Indicates an SDM state change to Refer to the procedure ”Clearing MAP
in-service trouble (ISTb). This log is alarms triggered by the SDM - APPL
included in the SDM Log Delivery log SDM minor” on page 4-3 in this
stream, but does not appear on the RMI. document.
SDM505 Indicates an SDM state change to offline None
(OffL) state. This log is included in the
SDM Log Delivery log stream, but does
not appear on the RMI.
SDM550 Indicates an SDM node status change. Refer to the following procedures in this
One or more of the following can cause document, depending on the alarm
the status change: code displayed:
• SDM node state • ”Clearing MAP alarms triggered by
the SDM - APPL SDM critical” on
• hardware device
page 4-25 when a critical alarm is
• software component generated.
• application • ”Clearing MAP alarms triggered by
the SDM - APPL SDM minor” on
page 4-3 when a minor alarm is
generated.
SDM600 The connection from the SDM to the CM None
or the operating company LAN server(s)
has been re-established. This log is
generated only after a connectivity failure
has been corrected, and not at system
startup.
SDM601 The maintenance system detects that None
mirroring has been re-established after a
logical volume mirroring failure.
SDM602 A system software resource has returned None
below its alarm threshold (see also SDM
302 log).
SDM603 A fault on an application process has None
cleared (see also SDM 303 log).

—continued—

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-81

Table 2-7xxx
SDM logs generated by the SDM (continued)

Log Trigger Action

SDM604 The SDM Log Delivery application No immediate action is required.

generates this log when the CM does not However, if large numbers of logs are
have enough CPU time to format logs, lost, contact Nortel for assistance.
and discards the logs.
SDM608 A system image backup (S-tape) has None
completed.
SDM609 A hardware device has been returned to None
the in-service state.
SDM616 A log delivery connection attempt was None
rejected.
SDM617 A Distributed Computing Environment None
(DCE) problem is cleared.
SDM619 The OM Access Server has detected a None
corrupt OM Group dNew
troubleshooting guide required for
SDM 11 – no SRuring an OM Schema
download.
SDM620 Reports SDM system performance data None
such as CPU usage, number of
processes, swap space occupancy, and
logical volume capacities.
SDM650 SDM link maintenance requests the None
logging of a failed link maintenance
action. An example of a link maintenance
action is the system testing of a link.

—end—

SDM Log Delivery application

The SDM Log Delivery application provides access through the SDM to the
generic DMS log stream, and local SDM logs. The log stream is available
from the SDM in several ways:
• The log stream can be directed to up to ten operations support systems
(OSS) through TCP/IP.
• The log stream can be directed to up to ten UNIX files on the SDM.

A maximum of ten devices (UNIX files and TCP/IP links) can be

commissioned.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-82 SDM maintenance overview

Logreceiver tool
The logreceiver tool is a client application, included with the Log Delivery
application, that runs on a remote workstation and receives logs sent to the
workstation from an SDM by the operating company LAN. The logreceiver
tool can either store these logs in a file or display them on the screen.

Only the following workstations can be used to run the logreceiver tool in
product release SDMN0010:
• HP 700/800 series workstations running the HP-UX 10.20 operating
system (or higher) with year 2000 enhancements
• Sun SPARC workstations running the Solaris 2.4 operating system (or
higher) with year 2000 enhancements
• Sun SPARC workstations running the year 2000-compliant Solaris 2.6
operating system (or higher)

To route logs from an SDM to a workstation, the SDM must be configured

to send logs to a TCP device, whose IP address is the IP address of the
workstation, using the logroute commissioning tool. A port number must be
included when this TCP device is configured. (For more information, see
”Commissioning TCP-client devices for Log Delivery” on page 2-87).

The logreceiver tool must also be installed on the workstation before logs
can be routed from an SDM to that workstation. Refer to the procedure
”Installing the logreceiver tool” on page 6-57 in the “SDM system
administration procedures” chapter of this document, for detailed
instructions on how to install the logreceiver tool on a workstation.

Once the logreceiver tool has been installed on the workstation and the SDM
has been configured to send logs to a TCP device, the logreceiver tool must
be started on the workstation. The following options are available for
running logreceiver:
• display logs directly on the workstation screen as they are generated
• store logs in a file for viewing when convenient by
— displaying the file using UNIX commands

With each of these options, a command must be issued at the workstation to

start the logreceiver tool’s execution. In all cases, the command must
include a port number. The port number must be the same as the port
number used in configuring the TCP device on the SDM. The port number
must not be in use for any other purpose on the workstation; otherwise an
error message, Failed to listen for connection request on port
xxx, exiting will result. You will then have to change the port number
used in configuring the TCP device on the SDM.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-83

To check the port numbers in use, type

>more /etc/services
and press the Enter key. You will see the list of port numbers in use on
the display. To scroll through the display, press the Enter key again.
To display logs directly on the workstation screen as they are generated, type
>logreceiver port
and press the Enter key.
where
port is the port number used when configuring the TCP device on
the SDM
A message Accepted connection request from host xxx is displayed
just before the first log received is written to the screen.

To store logs in a file, type

>logreceiver port -f filename
and press the Enter key.
where
port is the port number used when configuring the TCP device
on the SDM
filename is the name of the file
Note 1: If the file does not yet exist, it will be created automatically. The
logs from the SDM will be stored in this file. If the file already exists, the
logs from the SDM will be appended to it provided its UNIX access
permissions allow writing to it. In either case, a messsage Accepted
connection request from host xxx will be displayed on the screen just
before the first log received is written to the file.
Note 2: If the file already exists, but its permissions do not allow writing to
it, an error message Failed to open file filename is displayed on the
screen.
Note 3: The file continues to fill up until either the logreceiver execution is
terminated, or all free storage in the file system is exhausted. In the latter
case, the logreceiver execution is terminated automatically, and you must
remove the file or free up some storage.
In all these cases, type “control -c” and press the Enter key to terminate
execution of the logreceiver tool.

Logreceiver cannot execute simultaneously from two different UNIX

windows on a workstation using the same port number. Logreceiver can
execute simultaneously from two or more different UNIX windows on the
same workstation, provided a different port number is used in each

Wireless Networks Family SDM–SX User Guide SDMPL011

2-84 SDM maintenance overview

execution. The executions may involve either the same or different SDMs.
The workstation determines the SDM solely from the port number. If two or
more SDMs are configured to send logs to the same workstation using the
same port number, the workstation will connect to the SDM whose
configuration was activated first. Do not configure two SDMs to the same
workstation using the same port number.

Log Delivery commissioning

Log Delivery operating parameters are controlled by an online SDM
commissioning tool, which is used to set up the application, and can also be
used to view or modify the parameters. To access the logroute tool, log in to
the RMI as maint, and enter the command “logroute”.

For more information on configuring the Log Delivery service, refer to the
procedures ”Log Delivery device commissioning” on page 4-84, ”Log
Delivery global parameters commissioning” on page 4-107, or ”Log
Delivery CM configuration file commissioning” on page 4-117 in the SDM
Maintenance procedures chapter of this book.

The Log Delivery logroute tool allows customization of the following:

• global application parameters including buffer size, reconnect timeout
value, lost logs threshold (number of lost logs before a system log is
generated), ASCII line delimiter and log delimiter characters, and the
number of days to keep log files
• the incoming log stream from the CM, to add or delete individual logs
• client device parameters, including device type (UNIX file or TCP
output), parameters specific to the device type, log output format
(standard [STD] or switching control center 2 [SCC2]), and the log set to
be sent to the device

The Log Delivery logroute tool includes an on-line help facility that
provides the valid ranges (and default values, where applicable) for each
customizable parameter. The commissioning tool is subdivided into three
functional areas:
• Device List (menu option 1)
• Global Parameters (menu option 2)
• CM Configuration File (menu option 3)

Note: When any commissioning changes are saved, the Log Delivery
application must be busied and returned to service for the new settings to
take effect. The Log Delivery application is unavailable for a brief period
while this takes place.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-85

Figure 2-31 shows the top-level Log Commissioning menu that is displayed
when you access the Log Delivery commissioning tool.

Figure 2-31xxx
Log Delivery commissioning tool

Logroute Main Menu

1 – Device List
2 – Global Parameters
3 – CM Configuration File

c:change menu, q:quit, h:help, s:save changes

Warning: You must save, then BSY and RTS the Log Delivery
======== application for any changes to take effect.

Enter command ==>

Log Delivery device commissioning list

The Device List menu specifies the output devices for Log Delivery, and the
device-specific operating characteristics for each defined device. When you
access this menu, the Log Delivery output devices currently defined are
displayed. At initial commissioning time, no output devices are defined, and
all required output devices must be specified. This menu can also be used to
add or delete devices, or to select already-defined devices to change their
specifications. For more information on Log Delivery device
commissioning, refer to the procedure ”Log Delivery device
commissioning” on page 4-84.

Up to 10 output devices (UNIX files and TCP/IP links) in total can be

commissioned. This total of 10 can be made up of any combination of
UNIX files and TCP/IP links.

Figure 2-32 shows an example of the topmost Device List menu. In this
example, one output device (a TCP/IP) has already been commissioned.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-86 SDM maintenance overview

Figure 2-32xxx
Log Delivery device list commissioning menu

Device List

Devices: Type:
1 – HOST: 47.208.7.54 PORT : 5001 TCP

c:change device, a:add device, d:delete device, q:quit, h:help, m:main

Enter command ==>

The Device List menu provides access to the following device-specific

sub-menus:
• TCP Device defines TCP/IP output links to OSSs. For each TCP/IP link,
the IP address of the OSS host machine, the port number to be used on
that machine, and the log format must all be defined.
• File defines SDM-resident UNIX output files. The filename and log
format must be defined for each UNIX file.

At this menu, you can select a device that has already been defined to view
or modify its current parameters, delete a device that is currently defined, or
add a new device. If you choose to add a new device, you are prompted to
enter the device type (TCP or file).

When you select a device that is already defined, or after you specify the
type of device to add, a sub-menu is then displayed that is specific to the
device type. These sub-menus are described in the following subsections:
• ”Commissioning TCP client devices for Log Delivery” on page 2-87
• ”Commissioning file client devices for Log Delivery” on page 2-88

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-87

Commissioning TCP client devices for Log Delivery

Figure 2-33 shows an example of the TCP Device menu, with one device
already defined. All logs are being routed to this device.

Figure 2-33xxx
Log Delivery commissioning – TCP Device menu example

TCP Device

Device Parameters 1 – HOST IP : 47.208.7.54

2 – PORT : 5001
3 – FORMAT : STD

Log Routing ADDREP ALL

c:change parameter, a:add log routing, d:delete log routing

f:forward, b:back, q:quit, h:help, p:previous menu, m:main menu

Enter command ==>

By default, each device receives no logs at initial commissioning; that is, all
logs are suppressed. To route logs to a device, use the “add log routing”
command. Two different types of log routing entries can be added:
• addrep, which puts additional logs into the incoming log stream for the
device
• delrep, which suppresses logs from the incoming log stream

The incoming log stream is the cumulative result of all existing log routing
entries for the device, applied in sequence. Addrep and delrep can be
followed either by ALL, which adds or removes the entire log stream, or by
a specific log or log type.

ATTENTION
To avoid potential problems, when you commission a TCP device
using logroute, Nortel recommends that you select ports above 5000.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-88 SDM maintenance overview

Commissioning file client devices for Log Delivery

Figure 2-34 shows an example of the File device menu, with one device
already defined. No logs are being routed to this device.

Figure 2-34xxx
Log Delivery commissioning – File device menu example

File

Device Parameters 1 – FILENAME : /data/logs/File1

2 – FORMAT : STD

Log Routing

c:change parameter, a:add log routing, d:delete log routing

f:forward, b:back, q:quit, h:help, p:previous menu, m:main menu

Enter command ==>

By default, each device receives no logs at initial commissioning; that is, all
logs are suppressed. To route logs to a device, use the “add log routing”
command. Two different types of log routing entries can be added:
• addrep, which puts additional logs into the incoming log stream for the
device
• delrep, which suppresses logs from the incoming log stream

The incoming log stream is the cumulative result of all existing log routing
entries for the device, applied in sequence. Addrep and delrep can be
followed either by ALL, which adds or removes the entire log stream, or by
a specific log or log type.

To remove log routing entries, use the delete log routing command.

Log delivery file storage

A Log Delivery stream routed to a UNIX file device on the SDM is stored in
the directory /data/logs. When you define the filename using the
commissioning tool, the filename automatically begins with /data/logs.
When defining the filename, you can either append a file name to /data/logs

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-89

or append a subdirectory name, followed by a filename if you are the root

user (subdirectory must already exist). For example, to store the logs in a
file named File1 with no additional directory structure, append File1. If you
wish to store the file in a subdirectory called CMlogs, for example, append
CMlogs/File1.

Log Delivery UNIX files are automatically closed (and a new file started) at
noon and midnight each day. The closed files are appended with a suffix;
either <date>.am or <date>.pm, depending on when the file was closed.
(<date> is the calendar date the file was closed).

The closed files remain stored until manually removed, or until they are
automatically removed when they reach their expiry date. The default
expiry date is five days after file closure. This value can be globally
changed by accessing the Global Parameters menu of the Log Delivery
commissioning tool, and modifying the parameter “Number of days to keep
log files”.

Log Delivery global commissioning parameters

The Global Parameters menu allows you to configure operating
characteristics that apply to the Log Delivery application as a whole. These
parameters apply to all Log Delivery output devices and are independent of
device-specific parameters. Figure 2-35 shows the default values for Global
Parameters commissioning menu. For more information on configuring the
Log Delivery global parameters refer to the procedure ”Log Delivery global
parameters commissioning” on page 4-107.

The global parameters are set to default values at initial installation and
should not require modification in most cases. The ranges are as follows:
• buffer size (number of logs): 50 to 300
• reconnect timeout value (secs): 1 to 3600
• lost logs threshold: 1 to 300
• number of days to keep log files: 1 to 45

The following global parameters are represented by ASCII character codes:

• incoming end of line character
• outgoing end of line characters
• start of log characters
• end of logs characters

These parameters can be modified according to your requirements. The

default values of 10 and 13 shown in figure 2-35 represent line feed (go to
the next line) and carriage return.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-90 SDM maintenance overview

Figure 2-35xxx
Log Delivery global parameters commissioning menu

Global Parameters

1 – Buffer size (number of logs) : 150

2 – Reconnect timeout value (secs) : 15
3 – Lost logs threshold (NT only) : 100
4 – Incoming end of line character : 10
5 – Outgoing end of line characters : 10 13
6 – Start of log characters : 10 13
7 – End of logs characters : 10 13
8 – Number of days to keep log files: 5

c:change item, q:quit, h:help, m:main

Enter command ==>

Log Delivery CM configuration file commissioning parameters

The CM configuration file menu is used to add or delete log reports from the
incoming log stream from the computing module (CM) to the Log Delivery
application. At initial commissioning, all logs in the CM log stream are
included by default, and this parameter does not require manual definition
unless you wish to modify the incoming global log stream. For more
information on configuring the Log Delivery CM configuration file
commissioning parameters, see the procedure ”Log Delivery CM
configuration file commissioning” on page 4-117.

Figure 2-36 shows an example of the CM configuration file commissioning

menu. In this example, one log report (AUDT 100) has been deleted from
the incoming CM log stream.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-91

Figure 2-36xxx
Log Delivery CM configuration file commissioning example

CM Config File

1 – DEL AUDT 100

f:forward, b:back, a:add item, d:delete item

q:quit, h:help, m:main menu

Enter command ==>

Troubleshooting Log Delivery problems

This section describes fault conditions affecting Log Delivery operation and
how to isolate and clear them.

Lost logs
Lost logs can be detected by examining the sequence numbers of the logs at
a client output device and determining if they are sequential. If they are not
sequential, logs are likely being lost. To clear the problem, access the Log
Delivery commissioning tool, select the Global Parameters menu, and
increase the buffer size.

No logs being received at a Log Delivery client

If no logs are being received at a Log Delivery client, check the following
Log Delivery commissioning parameters:
• At the Device Parameters menu of the Log Delivery commissioning tool,
verify that the client is defined, and that the log stream for the client is
defined.

Logs not formatted properly

If the log reports at a Log Delivery client device are not formatted correctly,
access the Log Delivery commissioning tool and check the following:
• At the Device Parameters menu, verify that the correct log format has
been commissioned for the device (STD or SCC2).

Wireless Networks Family SDM–SX User Guide SDMPL011

2-92 SDM maintenance overview

• At the Global Parameters menu, check that the parameters for start and
end of line, and start and end of log, are set correctly.

SDM troubleshooting strategy

ATTENTION
The information contained in this section is an overview only. Use the
detailed procedures provided in this document to isolate and clear any
SDM faults.

This section summarizes troubleshooting information for the SDM

fault-tolerant platform in the following subsections:
• ”Fault reporting” on page 2-92 describes the ways in which SDM faults
may be visible.
• ”Fault diagnosis with SDM-CM communications in service” on page
2-93 describes the ways in which SDM faults may be visible when
SDM-CM communications is in service, and provides a brief overview
on diagnosing such faults.
• ”Fault diagnosis with SDM-CM communications out of service” on page
2-93 describes the ways in which SDM faults may be visible when
SDM-CM communications is out of service, and provides a brief
overview on diagnosing such faults.
• ”Fault diagnosis with the SDM out of service” on page 2-93 describes
the ways in which SDM faults may be visible when the SDM is out of
service. It also provides pointers to procedures and information in this
document to isolate and clear such faults.
• ”Hardware LED status indicators” on page 2-94 describes the meaning
of the LED status indicators on the SDM fault-tolerant hardware.
• ”State mismatches between the CM and the SDM” on page 2-101
describes the conditions under which an SDM state mismatch can occur,
how a mismatch condition is handled, and a comparison of meanings of
SDM node states at the MAP interface and the RMI.

Fault reporting
All SDM faults are visible at the MAPCI SDM display. All service-related
faults are reported under the APPL alarm banner. SDM faults are also
visible at the RMI, and by status LED indicators provided on the SDM
hardware. Power-related and thermal-related SDM problems are also
reported by the EXT alarm, and by the office alarm system.

The RMI is accessible from a local or remote VT100 console, or from the
operating company LAN through telnet (telnet access must be enabled).

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-93

Fault diagnosis with SDM-CM communications in service

The following indicators are displayed when faults occur, and
communications from the SDM to the CM are in service:
• APPL SDM minor alarm at the MAP display
• SDM In Service LED is on; component Out of Service LED is on if
hardware has failed
• SDM state is ISTb at the RMI

If the SDM and the CM are able to communicate successfully by at least one
of the four DS512 links from the SDM to the MS, all SDM fault conditions
can be isolated from the MAP display by accessing the SDM at the
MTC;APPL;SDM level, and issuing the QuerySDM FLT command.

If required, the MAP-based SDM remote login functionality can be used to

perform any required state changes of individual hardware elements before
and after physical replacement. Hardware state changes can also be made at
the RMI. Either of these two interfaces can also be used to stop and restart
SDM applications, if required.

Fault diagnosis with SDM-CM communications out of service

The following indicators are displayed when faults occur, and
communications from the SDM to the CM are out of service:
• APPL SDM critical alarm at the MAP display
• SDM state at the MAP display indicates “Links OOS: 4”, combined with
the qualifier “The SDM is not responding” or “NA”
• SDM System in Service LED is on

If the SDM is in service, but is unable to communicate with the MS, the
communications problem must first be examined using the MTC;MS level
of the MAP display. If required, further diagnosis of the communications
problem can be performed using the RMI, and by physical inspection of the
link hardware.

Fault diagnosis with the SDM out of service

The following indicators are displayed when faults occur with the SDM out
of service:
• APPL SDM critical alarm at the MAP display
• SDM state at the MAP display indicates “The SDM is not responding”
• SDM System In Service LED is off
• EXT alarm at the MAP display if the fault is power-related or due to a
thermal shutdown

Wireless Networks Family SDM–SX User Guide SDMPL011

2-94 SDM maintenance overview

If the SDM is out of service, the problem can be isolated using a local or
remote console, and by examining the status LED indicators provided on the
SDM hardware.

The following information will assist you in diagnosing faults when the
SDM is out of service:
1 If a APPL SDM critical alarm at the MAP display is present, refer to the
appropriate alarm clearing procedure on page 4-25 in the “SDM
maintenance procedures” chapter of this document to isolate and clear
the alarm.
2 If the SDM state at the MAP display indicates “The SDM is not
responding”, refer to the following:
— QuerySDM command reference information on pages 2-11 and 2-48
— SDMRLogin overview section on page 2-16
— the RMI overview on page 2-34
3 If the SDM System In Service LED is off, refer to the following:
— the procedure ”Clearing MAP alarms triggered by the SDM - APPL
SDM critical” on page 4-25 in the “SDM maintenance procedures”
chapter of this document
— the generic MS alarm clearing procedures provided with your DMS
switching system
— the connectivity (Con) menu level of the RMI
4 If an EXT alarm is present at the MAP display due to a power-related
fault or a thermal shutdown, refer to the following:
— the procedure ”Clearing MAP alarms triggered by the SDM - APPL
SDM critical” on page 4-25 in the “SDM maintenance procedures”
chapter of this document
— the procedure ”Clearing MAP alarms triggered by the SDM - Ext
FSP major” on page 4-44 in the “SDM maintenance procedures”
chapter of this document
— hardware LED information on page 2-94

Hardware LED status indicators

The SDM fault-tolerant platform is equipped with a number of LEDs, which
provide information on the status of SDM hardware resources. These
include LEDs visible on both the front and rear of the main and I/O
expansion chassis.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-95

Controller module LEDs

The In Service (green) LED and the Out of Service (red) LED on a
controller module can be on, off or flashing. The controller modules at the
front of both the main chassis and the I/O expansion chassis, contain these
LEDs. The fan tray units in each chassis also contain these LEDs.

Note: The I/O controller module (NTRX50FQ) also contains LEDs on its
tape drive. Refer to the procedure ”Cleaning the SDM-DAT drive” on page
4-50 for further information on the meaning of these LEDs.

Figure 2-37 shows the two LEDs that are visible on each controller module.

Figure 2-37xxx
Status LEDs visible on controller modules

SDM main chassis

IN SERVICE

OUT OF
SERVICE

Interconnect module LEDs

The In Service (green) LED and the Out of Service (red) LED on an
interconnect module (ICM) can be on or off. The ICMs located at the back
of both the main and the I/O expansion chassis contain these LEDs.

Wireless Networks Family SDM–SX User Guide SDMPL011

2-96 SDM maintenance overview

Figure 2-38 shows the two LEDs that are visible on each interconnect
module.

Figure 2-38xxx
Status LEDs visible on interconnect modules

IN OUT OF
SERVICE SERVICE

Table 2-8 shows the various combinations of controller module and ICM
LEDs, and their meanings.

Table 2-8
SDM controller module and ICM LEDs

In Service Out of Service

(green) LED (red) LED Meaning

on off The module is providing service to the system, and

functioning normally.
off off The module is in an undefined state for one of the
following reasons:
• The module has passed its power-on selftest and is
awaiting a command.
• The module has been deleted from the system, but it
is still on the shelf.
on on The power-on selftest diagnostic is running on the module,
or the module has failed its power-on selftest.

—continued—

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-97

Table 2-8
SDM controller module and ICM LEDs (continued)

In Service Out of Service

(green) LED (red) LED Meaning

off on The module is not providing service to the system for one
of the following reasons:
• A fault that was detected by the module has been
acknowledged.
• The module has been taken offline by a command.
Note: Immediately after a fault occurs it is
unacknowledged. Within several seconds, the SDM
becomes aware of the fault. When this occurs, the fault is
acknowledged.
flashing off The module is being reintegrated into the system.
off flashing The module is not providing service to the system. A fault
that was detected by the module has not been
acknowledged.

—end—

Wireless Networks Family SDM–SX User Guide SDMPL011

2-98 SDM maintenance overview

System LEDs
The System In Service (green) LED and the Component Out of Service (red)
LED can be either on, off or flashing. Only the fan tray in the main chassis
contains system LEDs. Figure 2-39 shows the LEDs that are visible on the
fan tray units located in the front of the main chassis.

Figure 2-39xxx
Fan tray LEDs

SYSTEM
IN SERVICE
COMPONENT
OUT OF SERVICE

FANTRAY 0
IN SERVICE
SDM main chassis
OUT OF
SERVICE

FANTRAY 1
IN SERVICE
OUT OF
SERVICE

Table 2-9 describe the various states of the System In Service and the
Component Out of Service LEDs, and their meanings.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-99

Table 2-9
SDM system LEDs

System In Service Component Out of

(green) LED Service (red) LED Meaning

on off The system is running, indicating the following:

• There are no software or hardware modules that
are out of service due to unacknowledged or
acknowledged faults or offline commands.
• No software or hardware modules are being
reintegrated into the system.
Note: Immediately after a fault occurs it is
unacknowledged. Within several seconds, the SDM
becomes aware of the fault. When this occurs, the
fault is acknowledged.
off off The system is not providing service because it has
just been powered on, or has encountered a fatal
fault.
off on The system is not providing service because it is
trying to boot the system software.
off flashing The system is not providing service because a
failure has occurred while booting system software.
on on The system is running, however, at least one
software or hardware module is out of service due to
an acknowledged fault or an offline command. This
state also indicates the following:
• No software or hardware modules are out of
service because of unacknowledged faults.
• No software or hardware modules are being
reintegrated into the system.
Note: Immediately after a fault occurs it is
unacknowledged. Within several seconds, the SDM
becomes aware of the fault. When this occurs, the
fault is acknowledged.

—continued—

Wireless Networks Family SDM–SX User Guide SDMPL011

2-100 SDM maintenance overview

Table 2-9
SDM system LEDs (continued)

System In Service Component Out of

(green) LED Service (red) LED Meaning

on flashing The system is running. No software or hardware

modules are being reintegrated into the system.
This state also indicates the following:
• At least one software or hardware module is out
of service because of unacknowledged faults.
• Some software and/or hardware modules may
be out of service due to acknowledged faults or
offline commands.
flashing off The system is running, however, at least one CPU
controller module or I/O controller module is being
reintegrated into the system. This state also
indicates that no software or hardware modules are
out of service due to unacknowledged or
acknowledged faults, or offline commands.
flashing on The system is running. There are no software or
hardware modules that are out of service due to
unacknowledged faults. This state indicates the
following problems have occurred:
• Some software and/or hardware module is out
of service because of acknowledged faults or
offline commands.
• At least one software or hardware module is
being reintegrated into the system.
flashing flashing The system is running, however, the following
problems have occurred:
• At least one software or hardware module is out
of service because of unacknowledged faults.
• At least one software or hardware modules are
being reintegrated into the system.
• Some software and/or hardware module may be
out of service due to acknowledged faults or
offline commands.

—end—

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-101

State mismatches between the CM and the SDM

Under normal operating conditions, the SDM node states at the MAP display
and the RMI are identical. However, if the link between the CM and the
SDM is down, either due to a fault in the link, or because the SDM itself is
not in service, the SDM node state at the MAP display and the RMI may
become mismatched. When CM-SDM communications are restored, the
SDM node state aligns to the CM view of its state. Manual state changes to
the SDM must be performed at the MAP interface, unless the CM-SDM link
is down, in which case state changes must be performed at the RMI.

Table 2-10 shows a comparison of the CM view and RMI view of the SDM
node states. At the MAP display, the SDM node state can be determined by
accessing the MTC APPL SDM level. At the RMI, the SDM node state is
visible at the RMI.

Table 2-10xxx
SDM maintenance states – MAP interface vs RMI

SDM node states Meaning at the MAP interface Meaning at the RMI

InSv No alarms are present. The CM is Messages between the SDM and
receiving in-service (InSv) status the CM are being successfully sent
from the SDM. and received. All SDM
applications and hardware devices
are in service with no faults.
ISTb An APPL SDM minor alarm is The SDM node state is ISTb if one
present. The CM is receiving or more of the following conditions
in-service trouble (ISTb) status is present on the SDM:
from the SDM.
• A hardware component is not
InSv.
• An operating system software
alarm is present.
• An application software
package is not InSv.
• Communication between the
CM and the SDM has failed.
• Connectivity to a LAN node
has failed.
• A file system has exceeded its
alarm threshold or any volume
group is not InSv.

—continued—

Wireless Networks Family SDM–SX User Guide SDMPL011

2-102 SDM maintenance overview

Table 2-10xxx
SDM maintenance states – MAP interface vs RMI (continued)

SDM node states Meaning at the MAP interface Meaning at the RMI

ManB An APPL SDM minor alarm is The SDM has either received a
present. The SDM has been ManB command from the CM, or
manually busied by command from has been manually busied at the
the MAP interface. Messages are RMI while communications to the
successfully being exchanged CM are down. All application and
between the CM and the SDM. service software processes are
stopped.
ManB (NA) An APPL SDM minor alarm is not applicable
present. The SDM has been
manually busied by command from
the MAP interface. The CM cannot
communicate with the SDM
because the DS512 ports on the
MS are unavailable. The actual
operating condition and local state
of the SDM are unknown to the CM
until at least one of the DS512
links is restored.
ManB/The SDM is not An APPL SDM minor alarm is not applicable
responding present. The SDM has been
manually busied by command from
the MAP interface. The CM is not
receiving messages from the SDM.
The actual operating condition and
local state of the SDM are
unknown to the CM until
communications are restored.
SysB An APPL SDM critical alarm is The SDM node state at the RMI
present. The CM is receiving shows SysB only if all software
system busy (SysB) status from applications on the SDM have
the SDM, indicating that no failed.
applications are running.

—continued—

297-5061-901 Standard 01.01 December 1998

 SDM maintenance overview 2-103

Table 2-10xxx
SDM maintenance states – MAP interface vs RMI (continued)

SDM node states Meaning at the MAP interface Meaning at the RMI

SysB (NA) An APPL SDM critical alarm is not applicable

present. The CM has designated
the SDM node state as
system-busy. The CM cannot
communicate with the SDM
because the DS512 ports on the
MS are unavailable. The actual
operating condition and local state
of the SDM are unknown to the CM
until at least one of the DS512
links is restored.
SysB/The SDM is not An APPL SDM critical alarm is not applicable
responding present. The CM is not receiving
messages from the SDM and has
designated its state as
system-busy. The actual operating
condition and local state of the
SDM are unknown to the CM until
communications are restored. The
SDM has been powered down or is
rebooting. All software
applications on the SDM have
failed.
OffL The SDM has been set to offline The SDM is offline, and is not
(OffL) state by command at the communicating with the CM. The
MAP interface, or the initial datafill SDM has received the OffL
for the SDM has just been command from the CM, or it has
completed. Communications to been set to OffL state locally at the
the SDM are disabled. RMI while isolated from the CM.

—end—

Wireless Networks Family SDM–SX User Guide SDMPL011

2-104 SDM maintenance overview

Routine maintenance recommendations

Nortel recommends that you perform the following activities as part of the
SDM routine maintenance strategy. Some tasks can be performed by
maintenance users, while others require root user permissions for accessing
the SDM.

Maintenance user tasks

The following activities require maintenance user permissions:
• Check dial-up access to SP0 on the CPU personality module by
periodically dialing into the SDM from a remote VT100 terminal and
logging in to the RMI. This ensures that the RMI is readily available for
maintenance purposes.
• If your system is configured with a local VT100 terminal, connected
directly to SP0 by a null modem, log in to the RMI periodically to ensure
it is readily available for maintenance activities.
• Clean the SDM tape drive after the first 4 hours of tape movement of a
new cartridge, and then after each 25 hours of use, using the appropriate
cleaning tape (Hewlett-Packard part number 92283K or equivalent). For
more information, see the procedure ”Cleaning the SDM DAT drive” on
page 4-50 in the “SDM maintenance procedures” chapter of this
document.

Root user tasks

The following activities require root user permissions:
• Backup the SDM software and data as required. Refer to the “SDM
system administration overview” chapter on page 3-1 of this document
for more information.
• Monitor log files in the /var/adm directory for system or security
abnormalities.
.

297-5061-901 Standard 01.01 December 1998

 3-1

SDM system administration overview

ATTENTION
The information in this chapter is intended for SDM system
administrators who have root user privileges for accessing the SDM.
Nortel recommends that SDM system administrators have specialized
AIX training before performing system administration procedures.

ATTENTION
Network File system (NFS) is not supported and should not be used on
the SDM. Network Information Service (NIS) is not supported and
must not be used on the SDM.

WARNING
SDM product support
SDM product support only includes administrative
changes that use either the commands or the SDM
maintenance interface described in this document. Other
administrative changes that are not described in this
document are not supported.

This chapter provides introductory information about administering the

SDM. The information contained in this chapter describes system
administration requirements, specifies limitations and restrictions, and
provides recommendations. Refer to the “SDM system administration
procedures” section in this document for detailed procedures.

Commissioning SDM software

Initial installation and commissioning of SDM platform software is
performed by Nortel, using a detailed installation method (IM). Software
installation includes the base software, and the Log Delivery application,

Wireless Networks Family SDM–SX User Guide SDMPL011

3-2 SDM system administration overview

which are included as part of the platform. Software installation can also
include optional software applications.

The SDM platform and optional application software is delivered on a

digital audio tape (DAT).

Information about commissioning and using optional SDM applications

software is available in the Northern Telecom publication (NTP) for each
application, or in the release notes documents.

Using the SDM commissioning tool

The commissioning tool cannot be accessed from the MAP display or by
remote login to the SDM using the SDMRLOGIN command. The
commissioning tool must be accessed from the local console to perform the
following tasks:
• install the base software
• install optional application software
• configure connectivity to the CM
• configure connectivity to the operating company LAN
• enable or disable file transfer protocol (FTP) and telnet access to the
SDM
• configure base line SDM fault-tolerant hardware devices, including
disks, tape drives, Ethernet cards, and DS512 controller modules
• configure maintenance (maint) and root userIDs
• set platform security, which includes
— file permissions
— passwords
— enable the restricted shell for maint users
• set the date, time and time zone of the system
• set the console login prompt
• configure DCE
• set remote nodes to be monitored by the SDM

The commissioning tool displays an “SDM Commissioning Complete!”

message after all mandatory sections of the commissioning tool are
completed successfully. The optional Distributed Computing Environment
(DCE) section could fail commissioning and the message “SDM
Commissioning Complete!” would still be displayed. If the DCE has not
been successfully commissioned, the “DCE state” is shown as UnEq in the

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-3

LAN menu level of the RMI. Ensure that the DCE commissioning has
completed successfully after entering the DCE commissioning values.

Defining IP addresses for the SDM to CM LAN

The parameters for the SDM to CM LAN are configured when your system
is initially commissioned by Nortel, using a detailed installation method.
The IP addresses for the CM, the DS512 interface, and the CM side of the
SDM are established as part of initial commissioning and do not normally
require subsequent modification. The IP addresses must be consistent with
the values datafilled in the DMS data schema tables that control CM to SDM
connectivity.

Datafill requirements on the DMS switch

The following DMS data schema tables require datafill, in the order listed, to
establish connectivity between the CM and the SDM.
• MSCDINV
• IPNETWRK
• IPHOST
• SDMINV

Table MSCDINV defines cards on the DMS message switch, including those
that support communication to the DS512 modules on the SDM. Table
MSCDINV datafill defines the characteristics of the DS512 link to the
message switch (MS). Two ports on each DS512 personality module are
defined to each support a subrate of 128.

Table IPNETWRK defines the IP address of the CM, allowing the SDM to
communicate with the CM. The SDM cannot communicate with the CM, if
the CM IP address is not defined.

Table IPHOST assigns IP addresses to CM end hosts, and in particular,

defines the number of transmission control protocol (TCP) endpoints (0 to
50) in the CM. TCP allows virtual connections between a program running
on the SDM, and a program running on the CM. A physical connection is
not necessary for communication to occur between two such programs.

Table SDMINV contains configuration information specific to the SDM,

including MS port definitions, locations, and IP addresses. Table SDMINV
defines the DS512 communication between the SDM and the CM. DS512
communication cannot occur without datafilling table SDMINV.

For detailed information on SDM-related datafill of these tables, refer to the

customer data schema NTP for your switching system.

Wireless Networks Family SDM–SX User Guide SDMPL011

3-4 SDM system administration overview

Log Delivery commissioning parameters

Log Delivery operating parameters are controlled by an online SDM
commissioning tool (Logroute) that is used at initial installation to set up the
application, and thereafter to view or modify the parameter values.

The Log Delivery commissioning tool is used to customize the following:

• global application parameters, including
— buffer size
— reconnect timeout value
— lost logs threshold (the number of lost logs before a system log is
generated)
— ASCII line delimiter and log delimeter characters
— the number of days to keep log files

• the incoming log stream from the CM, to add or delete individual logs
• per-device list, including
— device type (UNIX file or TCP/IP link)
— parameters specific to the device type
— log output format (standard [STD], switching control centre 2
[SCC2] or internal)
— logs to be sent to the device

For additional information on commissioning the Log Delivery application,

see page 2-81.

Administering the SDM using the remote maintenance interface

The following maintenance tasks can be performed using the SDM remote
maintenance interface (RMI):
• change the CM connectivity configuration
• change the LAN connectivity configuration
• add, delete or change LAN nodes monitored by the SDM
• change operating system alarm thresholds
• add logical volumes and change their sizes
• add and delete hardware modules
For information about maintenance tasks performed using the RMI, see the
“SDM maintenance overview” chapter of this document.

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-5

The following administrative tasks can be performed using the

administrative level of the SDM remote maintenance interface (RMI):
• change the time zone, time and date
• add and remove users
• password administration
• perform system backup and restore
• enable and disable FTP and telnet access
• install and update software

Figure 3-1 shows the location of the administration level menu items within
the RMI. The top menu level is the starting point for all RMI functions.
The administration and access menu levels of the RMI are similar to MAP
display screens. These screens contain an alarm banner, command list, input
and output areas, and a clock. (See the figure 2-8 on page 2-41 in the “SDM
maintenance overview” chapter for more information.) The time, user,
backup, and install menu options take you to screens that do not resemble
the MAP display. These screens display separate entry fields for user input.

Figure 3-1xxx
RMI administration levels

TOP

MTC ADMIN

TIME USER BACKUP SWIM ACCESS SPLIT

Wireless Networks Family SDM–SX User Guide SDMPL011

3-6 SDM system administration overview

See the “SDM maintenance overview” chapter in this document for an

overview of the RMI which includes how to log in to the RMI and a
description of the maintenance functionality.

Administration menu level of the RMI

Figure 3-2 shows the administration menu level of the SDM Remote
Maintenance Interface menu. Select option 3 from the top level of the RMI
to access the administration level. You can also type ADMIN from any level
of the RMI to access administration functions.

Figure 3-2xxx
Administration menu level of the RMI

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
. . . . . . SDM: SDM1

Admin
0 Quit
2 Time
3 User
4
5 Backup
6 SWIM
7 Access
8 Split
9
10
11
12
13
14
15
16
17 Help
18 Refresh

root
Time 19:48 >

The administration menu level of the RMI has an alarm banner which
dynamically updates the overall state of the SDM and the state of its major
components. The alarm banner is displayed at the administration and access
menu levels of the RMI. For more information about monitoring SDM
status and alarms at the RMI, refer to page 2-42 in the “SDM maintenance
overview” chapter of this document.

The following set of navigation and interface commands is available at the

administration level of the RMI:
• Quit exits the administration level of the RMI. Type QUIT or select
option 0 to use this command.

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-7

• Time changes the time zone, time and date on the SDM. Type TIME or
select option 2 to access this menu.
• User adds and removes users, and administers users and passwords.
Type USER or select option 3 to access the User menu.
• Backup accesses the system backup and restore menus. Type BACKUP
or select option 5 to access the Backup and Restore Main Menu.
• SWIM upgrades or installs SDM software and lets you manage your
SDM files. Type SWIM or select option 6 to install or upgrade software.
• Access changes FTP and telnet settings. Type ACCESS or select option
7 to enable or disable FTP access and telnet access settings.
• Split allows you to upgrade various hardware and software components
with minimal downtime. Type SPLIT or select option 8 to use Split
Mode.
• Help provides information about the administration menu options. Help
messages are also displayed when incorrect information is entered. To
use the Help command, type HELP or selecting option 17 to get
information about the administration menu options.
• The Refresh command refreshes the screen. Type REFRESH or select
option 18 to use this command.

Time and date administration

Time and date administration allows the time zone, date and time of day on
the SDM to be changed. Changes between daylight saving and standard
time are automatically accommodated on the SDM without a need for
manual time and date adjustment. Refer to the procedure ”Setting the time
zone, date and time” on page 6-18 for more information.

Wireless Networks Family SDM–SX User Guide SDMPL011

3-8 SDM system administration overview

User and class administration

Two user classes are provisioned on the SDM: administrative users and
maintenance users. The administrative class consists of the root user. The
maintenance class consists of the maintenance user by default, but additional
maintenance class users can be added. The capabilities available to each
class are listed in table 3-1.

Table 3-1xxx
User class profiles

Class Responsibilities Capabilities

Administration SDM system user and group administration

administration
• adding and removing users
• assigning and restricting user access
• password administration
system image backup and restore

unrestricted shell access

local console access from LAN

setting the time zone, and the date and

time

all maintenance capabilities

Maintenance SDM maintenance maintenance commands (for example,
busy, return to service, and offline)

monitoring system performance

restricted shell access

changing system alarm thresholds

password update
application-specific configuration tools

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-9

Password administration
The root user can change any password on the system at any time.
Maintenance class users can only change their own passwords. The
following conditions apply to user passwords:
• The maximum duration for passwords is four weeks for root users and
nine weeks for maintenance class users.
• Warnings are issued 7 days before the password expires, and are repeated
at each login until the password is changed.
• A user cannot reuse a passwords for 26 weeks after their assignment.
• If a maintenance class user’s password expires, the user has up to 2
weeks after the expiry date to change the password. During this period,
the user is forced to enter a new password before they can log in. If it is
not changed by the end of this 2-week period, the user must reset it
before logging in again.
• The minimum length of passwords is six characters. The password must
contain a minimum of one alphabetic character, and a minimum of one
numeric or special character. (Although more than eight characters can
be entered, only the first eight characters of a password are considered.)

Note: Although passwords beginning with a number are valid, they cannot
currently be accepted following the SDMRLogin command.

Idle logins
All users are logged out automatically after 10 min of inactivity.

User menu of the RMI

The user option at the RMI is the starting point for administering user
passwords, and adding and removing maintenance class users. Figure 3-3
shows the User menu. The user administration tasks that can be done from
the User menu include adding a user, removing a user, and changing a
password. This screen shows all users on the system.

To access the User menu, select option 3 from the administration menu level
of the RMI or type USER from any RMI menu level.

Wireless Networks Family SDM–SX User Guide SDMPL011

3-10 SDM system administration overview

Figure 3-3x
User menu

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
I S . I I . SDM: SDM1

User
0 Quit SDM USERS
2
3 Administrative users:
4 1 root
5
6 Maintenance users:
7 1 maint
8 2 maint1
9 3 randy
10 4 auto1
11
12
13
14
15 Maintenance Users: 1 to 4 of 4
16
17 Help
18 Refresh

root
Time 19:48 >

Adding users to the maintenance class

Refer to the procedure ”SDM users class – Adding or removing a
maintenance user” on page 6-10 in the “SDM system administration
procedures” chapter of this document for more information on how to add
new users. Only the root user may execute this procedure.

Changing a user password

You must know the old password of a user or be the root user to change a
user password. See ”Password administration” on page 3-9 for restrictions
on defining and changing user passwords. User passwords are changed
directly at the User menu.

Refer to the procedure ”Changing user passwords” on page 6-3 in the “SDM
maintenance procedures” chapter of this document for more information on
how to change passwords.

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-11

Removing users from the maintenance class

Removing a maintenance class user is done directly from the User menu.

Refer to the procedure ”SDM users class – Adding or removing a

maintenance user” on page 6-10 in the “SDM system administration
procedures” chapter of this document for more information on how to
remove users. Only the root user may execute this procedure.

Software and data backups

The following sections describe the system image backup procedure. SDM
software and data backups must be performed by the root user. Software
backups are stored on 4-mm digital data storage (DDS) tapes with lengths of
either 90 m or 120 m.

Backups are performed using the SDM backup and restore online utility,
which the root user can access in two ways:
• by logging in to the local or remote VT100 console and typing
“sdmbkup”
• by typing “sdmmtc” after logging in to the SDM to access the RMI.
Select option 3 at the Top level of the RMI, or type ADMIN at any level
to go to the administration menu level of the RMI, then select option 5 or
type BACKUP.

Nortel recommends that tape drive DAT0 is used to perform software and
data backups if your system includes the SuperNode Billing Application
(SBA).

Figure 3-4 shows the Backup and Restore Main Menu. This is the starting
point for performing backup and restore functions.

Wireless Networks Family SDM–SX User Guide SDMPL011

3-12 SDM system administration overview

Figure 3-4xxx
Backup and Restore Main Menu

*** ***********************************************************
*** SuperNode Data Manager
***
*** Backup and Restore Main Menu
*** ***********************************************************
***
*** 0. Exit
***
*** 1. Help
***
*** 2. System Image Backup and Restore
***
***
***
***
*** Please enter your selection (0 to 3) ? ==>

For detailed instructions on performing system image backups, refer to the f

procedure “Creating SDM backup tapes – system image backup (S–tape)”
on page 6-26 in the “SDM system administration procedures” chapter of this
document.

ATTENTION
To backup the SDM to tape, perform a full system (bootable image)
backup after you install or upgrade SDM software. To perform a full
system backup, use the procedure “Creating SDM backup tapes –
System image backup (S–tape)” in chapter 6 of this NTP.

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-13

System image backup

The system image backup is used to back up all files in the root volume
group to a tape called an S-tape. The system image backup includes the
following:
• boot (startup) files
• base operating system (BOS)
• system configuration data
• SDM software
• SDM data

Figure 3-5 shows the System Image Backup and Restore Menu. This menu
is used to perform a system image backup, restore files, and list the contents
of the system image tape (S-tape).

To access this menu, select option 2, System Image Backup and Restore,
from the Backup and Restore Main Menu.

Figure 3-5xxx
System Image Backup and Restore Menu

*** ***********************************************************
*** SuperNode Data Manager
***
*** System Image Backup and Restore Menu
*** ***********************************************************
***
*** 0. Return to the Previous Menu
***
*** 1. Help
***
*** 2. Create a System Image on Tape (S-tape)
***
*** 3. List Contents of the System Image Tape (S-tape)
***
*** 4. Restore Files from the System Image Tape (S-tape)
***
***
*** Please enter your selection (0 to 4) ? ==>

Wireless Networks Family SDM–SX User Guide SDMPL011

3-14 SDM system administration overview

When to perform a system image backup

Nortel recommends that you perform a system image backup after the
following:
• initial installation and commissioning of the SDM
• changes to the configuration of disks or logical volumes
• installation of a new version of SDM platform software

Restoring SDM software and data

This section provides an overview of SDM software restore capabilities and
methods. For detailed instructions on restoring SDM software, refer to the
following procedures in the “SDM system administration procedures”
chapter in this document:
• “Restoring the SDM – Full restore from S-tape” on page 6-35
• “Restoring the SDM – Partial restore from the system image tape
(S-tape)” on page 6-49

SDM restore operations must be performed by the root user. The root user
must be a trained UNIX system administrator who is capable of correctly
identifying files or directories to be restored, and who fully understands the
impact of restoring or overwriting software files.

The SDM is restored by using backup tapes. See ”Software and data
backups” on page 3-11 for information on performing software backups.

Software restores are performed by using the SDM backup and restore
online utility, which the root user can access in two ways:
• by logging in to the local or remote VT100 console and typing
“sdmbkup”
• by typing “sdmmtc” after logging in to the SDM to access the RMI.
Select option 3 or type ADMIN to go to the administration menu level of
the RMI, then select option 5 or type BACKUP.

Note: The full restore must be done at the local VT100 terminal, connected
to the SDM.

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-15

Performing a full SDM restore

A full SDM restore is required if SDM software becomes corrupted, or the
disk drive unit is replaced. A full restore consists of loading the full
contents of the system image tape (S-tape).

Full SDM restores require rebooting the SDM. The SDM reboots
automatically after the S-tape is restored.

ATTENTION
After a full SDM restore is performed you must verify the state of
DCE and any DCE-based application servers. It may be necessary to
perform additional DCE procedures. See the section “DCE
application servers after an SDM restore” on page 3-34 for more
information. Also, refer to the procedure “Restoring the SDM – Full
restore from S-tape” on page 6-35.

Listing the contents of a backup tape

The root user can list the contents of a backup tape by inserting it into the
tape drive and accessing the SDM Backup and Restore Main Menu.

To view the contents of the S-tape, select “System Image Backup and
Restore”, then select “List Contents of the System Image Tape (S-tape)”.

Using the Software Inventory Manger (SWIM)

Use the SWIM (Software Inventory Manager) screen to perform the
following tasks:
• change the view of the SWIM menu
• install new software
• update existing software with a newer version
• remove existing software
• view a history of commands previously executed
• configure software
Figure 3-6 shows the SWIM menu. This screen displays the SDM software
and operating system software installed on the SDM, the version, and its
status.

To access the SWIM menu, select option 6 from the Admin menu.

Wireless Networks Family SDM–SX User Guide SDMPL011

3-16 SDM system administration overview

Figure 3-6xxx
SWIM menu

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM: CM CLLI
. . . . . . SDM: SDM hostname
Filesets: 1 to 5 of 5
SWIM
0 Quit List Filter: SDM
2 Apply # Fileset Description Version Status
3 Config 1 Platform Maintenance 10.0.20.1 FAILED
4 2 Enhanced Terminal Access 10.0.20.0 ARCHIVED
5 History 3 Enhanced Terminal Access 10.0.20.1 APPLIED
6 4 Client Common Resources 10.0.20.0 APPLIED
7 5 Exception Reporting 10.0.20.0 APPLIED
8 Remove
9
10
11 Options
12
13
14
15 Filter
16
17 Help
18 Refresh

root
Time 19:48 >

To scroll up or down the list

• type “up” to scroll to the previous page
• type “down” to scroll to the next page
For information about using the Filter command to specify what you want to
view on the History command screen, see “Viewing history information” in
this chapter.

About filesets and software states

SDM applications are made up of filesets. Software can have a number of
filesets associated with it. For example the SDM Base software is made up
of many filesets, such as the following:

• Platform Maintenance (SDM_BASE.mtce)

• Client Common Resources (SDM_BASE.client)
• Log Delivery Service (SDM_BASE.logs)
• Table Access Service (SDM_BASE.tasl)
• OM Access Service (SDM_BASE.omsl)

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-17

When view the software available on the SDM, SWIM displays the available
software at the fileset level. A fileset can be in one of the following states:

• APPLIED — fileset is currently installed and in use on the SDM

• APPLYING — the install program is currently installing the fileset
• ARCHIVED — the fileset is a backup version used to replace the
version currently in the applied state
• FAILED — the fileset installation failed and the fileset must be
reinstalled before use
• REMOVING — the fileset is being removed from the SDM.
You use SWIM to install new software or apply corrective content to the
software currently on the SDM. Filesets that install new software are
displayed on the Apply menu with an asterisk. These files include all
filesets required to install new software. Filesets that apply corrective
content to existing software contain only the changes required to update or
improve that software.

Fileset naming conventions

Filesets names reveal information about them. The fileset name is made up
of the package name and fileset name. In the following example,

SDM_BASE.mtce 10.0.29.0

SDM_BASE is the package name and mtce is the fileset name. Filesets also
have a four–part serial number associated with them, as shown in the
example above. The first part is the SDM release number. The second part
indicates the version of the software released for a specific market. The third
part is the number of times the software was compiled. The fourth part is the
version of the corrective content, with D indicating the absence of corrective
content.

Using the Filter command to change the view of the SWIM menu
When you first access the SWIM menu, a list of SDM and operating system
filesets is displayed, using their descriptive names. You have the option of
viewing operating system filesets or SDM filesets using the Filter command.

To view all filesets, type

>filter off
and press the Enter key.

Wireless Networks Family SDM–SX User Guide SDMPL011

3-18 SDM system administration overview

To view only SDM filesets, type

>filter sdm
and press the Enter key.

To view only operating system filesets, type

>filter os
and press the Enter key.

You can use an additional condition when specifying the type of filesets you
want to view. For example, using substring text, you can specify that you
want to view all filesets that contain the characters “sft”. If no filesets
contain the substring text, the current list is unchanged. This command is
not case sensitive.

To view all filesets whose names contain specified characters, type

>filter xx
where
xx is the string of specific characteristics

You can also toggle between viewing filesets using their fileset descriptions
or fileset names.

To toggle between descriptive names and fileset names, type

>filter view
and press the Enter key.

Installing new software

Use the Apply command to install new software. New software is delivered
using tapes. Tapes include new software and optional software packages.
For example, software packages include the SDM base software and
applications, such as Enhanced Terminal Access, Exception Reporting, and
Secure File Transfer. Select the Apply command or option 8 from the
SWIM menu to access the Apply menu. For more information about
installing new software, refer to the application user guide.

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-19

Figure 3-7xxx
Apply menu

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
. . . . . . SDM: SDM hostname
Filesets: 1 to 4 of 4
Apply
0 Quit Source device: tape drive in the main chassis slot 2:
2 # Fileset Description Current Available
3 1 Platform Maintenance 10.0.29.0 10.0.29.0 *
4 2 Enhanced Terminal Access 10.0.29.0 10.0.29.0 *
5 Source 3 Secure File Transfer 10.0.29.0 10.0.29.0 *
6 4 Exception Reporting 10.0.29.0 10.0.29.0 *
7 Select
8 Apply
9
10
11
12
13
14
15 Filter
16
17 Help
18 Refresh

root
Time 19:48 >

Updating existing software

Use the Apply command to update existing software. Tapes that include
upgrades to your existing software may include the SDM base software, and
applications such as Enhanced Terminal Access, Exception Reporting, and
Secure File Transfer. These tapes may also contain corrective content for
operating system software. For detailed instructions on how to upgrade
software, refer to the SuperNode Data Manager Platform Software Upgrade
Implementation Guide.

Removing Existing Software

The Remove command lets you remove filesets listed on the SWIM menu.
SWIM lets you remove the following:

• archived filesets
• the current version of corrective content
• products
• dependent filesets

Wireless Networks Family SDM–SX User Guide SDMPL011

3-20 SDM system administration overview

To remove one or more filesets, type

>remove <number> [<number> [...]]

where
number is a fileset number in the list.

Removing archived filesets

An archived fileset is a previous version of a fileset that the SDM no longer
uses. The archived fileset is still stored on the hard disk. SWIM gives you
the option of removing archived filesets, which frees up disk space. When
you remove an archived version of a fileset, you remove all of its previous
versions.

Removing the current version of corrective content

When you remove the current version of corrective content, you remove the
version of the software currently in use. SWIM reverts to the previous
version of the software archived on the SDM, if any.

Removing products
Removing all versions of a fileset permanently removes a product from the
SDM. For example, assume that the SWIM menu displays the following
filesets for Enhanced Terminal Access version 10:

1 Enhanced Terminal Access version 10.0.20.2

2 Enhanced Terminal Access version 10.0.20.1
3 Enhanced Terminal Access version 10.0.20.0
Removing all filesets named Enhanced Terminal Access removes the entire
Enhanced Terminal Access software product from the SDM.

Note: You do not have the option of removing AIX or Platform

Maintenance products using the Remove command. However, you can
remove particular versions of these filesets and revert to previous (archived)
versions.

Removing dependent filesets

Some filesets are dependent on other filesets. When you try to remove a
fileset on which other filesets depend, the dependent filesets are displayed,
and you are prompted to confirm the removal. If you confirm the removal,
all filesets including the dependent ones are removed.

Viewing history information

Use the History command to view a history of the last 200 SWIM
commands you used. The most recent command is listed first. Each
command logged is summarized on three lines. For successful maintenance
commands, the following information is provided:

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-21

• date and time the command was executed

• fileset description or full name
• action
• previous version
• updated version
For failed commands, the following information is provided:

• date and time the command was executed

• a message that indicates why the command failed
• the log file name that contains further information
Figure 3-8xxx
History menu

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
. . . . . . SDM: SDM1
History Entries: 1 to 5 of 35
History
0 Quit List filter: OFF
2 Date Fileset
3 Feb 12 09:38 1998 SDM_BASE.mtce
4 --9.0.21.2 COMMITTED TO 9.0.21.2
5 -–Platform Maintenance
6 Feb 12 09:35: 1998 SDM_BASE.client
7 -–9.0.21.3 REMOVED TO 9.0.21.2
8 -–Client common Resources
9 Feb 12 09:34: 1998 SDM_ETA.eta
10 -–NA INSTALLED TO 9.0.21.0
11 -–Enhanced Terminal Access
12 Feb 12 09:34 1998 Failed–command
13 -–Status: FAILED
14 -–View /sdm/mtce/swm/logFeb12.1
15 Filter Feb 12 09:16 1998 Failed–script
16 -–Status: FAILED
17 Help -–sdmconfig returned an error
18 Refresh

root
Time 19:48 >

Changing default values

The Change command in the Options menu lets you change the default
directory and the DAT alias. Use the Options command to access the
Options menu.

Wireless Networks Family SDM–SX User Guide SDMPL011

3-22 SDM system administration overview

Changing the default directory

To change the default directory, type

>change <option>
where
option is the number that represents the default device.
and press the Enter key.

You are prompted to type a value for the new default directory. Type the
value and press enter.

Figure 3-9xxx
Options command menu

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC11
I. . . I . . SDM: bmery7c8

Apply
0 Quit Specify the new source device:
2
3 To specify a directory on the SDM, enter the directory path.
4
5 Source To specify a tape drive:
6 Enter 0 for the tape drive in the main chassis slot 2.
7 Enter 1 for the tape drive in the main chassis slot 13.
8
9 To specify the default source device, press [Enter].
10 The default is the tape drive in the main chassis slot 2.
11
12
13
14
15 Filter
16
17 Help
18 Refresh

root
Time 19:48 >

Configuring software
After you apply corrective content to existing software or install new
software, you may have to configure the software. A message prompts you
to run the configuration script.

Accessing the Config menu

To access the Config menu, type

>config
and press the Enter key.

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-23

When you access the Config menu, a list of configuration scripts is

displayed. Each script includes the name of the script and the script status.
A script can have one of the following statuses:

Table 3-2xxx
Configuration script status

Config status Description

UNCONFIGURED The script was installed when its fileset was applied,
but has not yet been executed. Execute the script
PASSED before starting the application.

The script has been executed and can be executed

again. Some configuration scripts can be executed
more than once if required.
FAILED The configuration script had previously been
executed but failed.

Executing configuration scripts

To execute all incomplete of failed scripts, type

>config all

and press the Enter key. Alternatively, select a configuration script using the
Select command and use the Config command to execute it, or type config
and the number of the script from the config screen display.

Enabling and disabling FTP and telnet access

You can view or modify FTP and telnet access to the SDM. Select option 7
or type ACCESS at the administration menu level of the RMI or type
ACCESS at any level. Figure 3-10 shows the Access menu level of the
RMI.

In the example shown,

• telnet access is enabled
• file transfer protocol (FTP) access is disabled
• Secure File Transfer (SFT) is in Distributed Computing Environment
(DCE) mode
Note: SFT Access is only displayed on the Access menu if the SFT package
is installed. If SFT is not installed, only telnet and FTP access are displayed.

Wireless Networks Family SDM–SX User Guide SDMPL011

3-24 SDM system administration overview

When SFT is in DCE mode, the following occurs:

• the security encryption is enabled

When SFT is in FTP (non-DCE) mode:

• DCE security is disabled for SFT
• the standard FTP server is disabled
• SFT client cannot connect in this mode, users must use a standard FTP
client
Figure 3-10xxx
Enabling and disabling FTP and Telnet

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
. . . . . . SDM: SDM1

Access Telnet Access: Enabled

0 Quit FTP Access: Disabled
2 SFT Access DCE mode
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17 Help
18 Refresh

root
Time 19:48 >

Commands at the access menu level

Change is a hidden command used to modify FTP and telnet access to the
SDM. The parameters are SFT, TELNET, or FTP. Use the change
command as follows:
Note: The parameter SFT only applies if the SFT package is installed. If
the SFT package is not installed, the parameters are FTP and TELNET.

• Type CHANGE to change SFT and TELNET access.

• Type CHANGE SFT to change only SFT status (DCE or FTP
(non-DCE)).

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-25

• Type CHANGE FTP to change only FTP access (enabled or disabled).

• Type CHANGE TELNET to change only telnet access (enabled or
disabled).

If no parameters are supplied after the change command, the user is

prompted to change both the Telnet and SFT status. The default status of
FTP is Disabled. To change the FTP status to enabled, type change FTP
after changing SFT to DCE mode.

After you enter the change command, you are prompted to confirm your
request.

Upgrading CPU controller modules

Use the Split menu of the Administration level of the RMI to upgrade the
SDM operating system or CPU with little downtime. For information about
upgrades using Split Mode, refer to the “SDM hardware upgrade
procedures” chapter of this document.

Hardware upgrades
The CPU controller modules can be upgraded, and are available in the two
versions:
• NTRX50FL – 256 MByte DRAM
• NTRX50FM – 512 MByte DRAM

The CPU controller modules can be upgraded from:

• NTRX50FK (128 MByte DRAM) to NTRX50FL (256 MByte DRAM)
• NTRX50FK (128 MByte DRAM) to NTRX50FM (512 MByte DRAM)
• NTRX50FL (256 MByte DRAM) to NTRX50FM (512 MByte DRAM)

For detailed instructions on performing these upgrades, refer to the “SDM

hardware upgrade procedures” chapter of this document.

Wireless Networks Family SDM–SX User Guide SDMPL011

3-26 SDM system administration overview

In addition to the required I/O controller module (NTRX50FQ), you may

wish to add the following I/O controller module to increase disk capacity:
• NTRX50FU - 2-Gbyte disk drives and Ethernet

ATTENTION
Adding an I/O controller module (NTRX50FU) does not provide
functionality in this product release. Functionality is provided in the
next product release. Modules can be added now, if desired, to
prepare for the new functionality.

For detailed instructions on adding an I/O controller module, refer to the

procedure ”Adding I/O controller modules” in the “SDM maintenance
procedures” chapter of this document.

DCE overview
Distributed Computing Environment (DCE) allows graphical user interface
(GUI) applications running on remote workstations to communicate securely
with the SDM. These GUI application control operations run on the SDM
and the DMS switch. They run as clients of application servers running on
the SDM, and communicate securely with the SDM by remote procedure
calls (RPCs) supported by DCE.

ATTENTION
The DCE overview section is written for experienced DCE system
administrators who are knowledgeable about DCE and its required
administration procedures.

DCE cell configuration and maintenance

For an SDM to communicate securely with its remote workstations by DCE,
the SDM and the workstations must be configured in the same DCE cell. A
DCE cell consists of all systems having a common DCE realm. In the SDM
context, a DCE cell must contain the following:
• one or more SDMs
• all workstations running GUI applications that will communicate with
those SDMs
• DCE servers that provide DCE services to those SDMs and
workstations:
— security servers that store security information and authenticate users
of the GUI applications

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-27

— cell directory servers (CDSs) that store naming information from the
application servers on the SDM and allow GUI application clients to
locate the application servers
— distributed time servers (DTSs) that allow all machines in the DCE
cell to maintain synchronized clocks

Typically there can be more than one replica of each type of server. For
security servers and CDS servers, one replica is the primary (or master)
replica and all others are slave replicas. For DTS servers, one particular
replica is the time provider.

The following workstations may be used to run GUI applications:

• HP 700/800 workstations with HP-UX 9.05 or later
• SUN SPARC workstations with Solaris 2.4 or later

Nortel recommends that your workstations have operating systems that are
year 2000 compliant, such as the following:

• HP 700/800 series workstations running the HP-UX 10.20 operating

system (or higher) with year 2000 enhancements
• SUN SPARC workstations running the Solaris 2.4 operating system (or
higher) with year 2000 enhancements
• SUN SPARC workstations running the year 2000-compliant Solaris 2.6
operating system (or higher)

The DCE servers can, in principle, be located on any workstation in the

DCE cell. In practice, however, Nortel strongly recommends that all
security servers and, if possible, all CDS servers, be located on dedicated
and physically-secured workstations that are separate from all
GUI-application workstations that use their services. (Other configurations
risk compromising the security arrangements offered by DCE.) The primary
security and CDS servers and the DTS time provider, can all be on the same
workstations, or one/all may be on separate workstations. If a slave security
server is present, it must be on a separate workstation.

Each of the SDMs and GUI-application workstations that use the services of
the DCE servers must run a DTS clerk that interacts with the DTS servers.
If a DTS server is located on a GUI-application workstation, it provides the
DTS clerk the functionality required by that workstation. Figure 3-11 shows
a typical configuration of a DCE cell.

Wireless Networks Family SDM–SX User Guide SDMPL011

3-28 SDM system administration overview

Figure 3-11xxx
DCE cell configuration

Remote W/S

Primary Primary DTS server

security server CDS server (time provider)

DCE cell
boundary Network Remote W/S

GUI application
(client)

DTS clerk
SDM

Application
server Remote W/S
DMS switch

DTS clerk GUI application

(client)

SDM DTS server

Application
server Remote W/S
DMS switch

DTS clerk GUI application

(client)

DTS clerk

Remote W/S

Slave Slave DTS server

security server CDS server

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-29

Setting up a DCE installation

The following steps are required before secure network communication
between GUI-application workstations and SDMs can be established using
DCE:
• DCE software must be installed and configured on all the systems that
will be part of the cell, as outlined in the DCE software vendor’s
installation notes.
• The DCE cell must be configured, including its DCE servers and remote
(GUI application) workstations.
• DCE accounts must be created to accommodate the users of the GUI
applications.
• Each SDM must be added to the DCE cell.
• Application-server software for each GUI application must be installed
on each of the appropriate SDMs within the DCE cell, and registered
with the DCE security and CDS servers.
• Each GUI application must be installed on each of the appropriate
workstations within the DCE cell.

DCE accounts must also be modified to reflect changes in the user

community of the GUI applications.

The following items are covered in the next three sections:

• recommendations on creating the DCE cell
• adding an SDM to the DCE cell
• registering application servers and creating DCE accounts on the DCE
security server

Creating the DCE cell and adding nodes to a cell

The DCE cell must be created using a machine on which one or more of the
DCE servers will reside. Each vendor of DCE software provides a program
that carries out cell creation, and is used to add machines to a DCE cell. The
following is a partial list:

DCE CELL-CREATION
MACHINE PROGRAM NAME
HP9000 dce_config
IBM RS-6000 mkdce
Motorola PowerStack mkdce
Sun SPARC dcesetup

Wireless Networks Family SDM–SX User Guide SDMPL011

3-30 SDM system administration overview

These programs are invoked from the machine’s UNIX prompt. For more
information on creating DCE cells and configuring DCE and client servers,
refer to ”OSF DCE Administration Guide – Core Components” or your DCE
vendor’s installation/configuration information.

Adding an SDM to the DCE cell

Add an SDM into a DCE cell by invoking the SDM commissioning tool
from the local console of that SDM. (No other machines in the DCE cell
can be used to perform this task.)

The SDM can be added to the cell using two different methods:
• full configuration, when you know both the root password of the SDM,
and a DCE administrative account password
• local configuration, when you know only the root password of the SDM

To use full configuration, you must also know the following:

• the name of the DCE cell
• the IP address of each machine hosting the primary DCE security server
• the IP address of the CDS server
• the name of the SDM LAN profile
• the password of the DCE cell administrator

To use local configuration, a user with a DCE administrative account

password must have already executed an enabling administrative procedure
from another AIX-based machine within the DCE cell. You must then know
the following:
• the name of the DCE cell
• the IP address of each machine hosting the primary DCE security and
DTS servers

For more information, see the procedures ”Distributed Computing

Environment – Configuring an SDM in a DCE cell” and in the “SDM
system administration procedures” chapter of this document.

Registering application servers and creating user accounts

All application servers on SDMs within the DCE cell, and GUI applications
users that communicate with an application server using DCE, must have
properly configured accounts registered in the DCE security database
associated with the DCE security server. A DCE administrative account
password is required to perform all registration activities.

Registration can be done from any machine in the DCE cell. Commands to
perform registration activity are available from the UNIX prompts on the

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-31

DCE cell machines. For security reasons, however, Nortel does not
recommend that telnet and Enhanced Terminal Access (ETA) be used when
establishing a registration session.

Note: ETA is an optional SDM application that provides secure remote

access to the SDM across the operating company TCP/IP wide area network
(WAN). For more information on the ETA application, refer to the NTP,
SuperNode Data Manager Enhanced Terminal Access User Guide.

As part of the SDM application-server software installation, a key table

(keytab) file is created to store the application server DCE password (for
presentation whenever DCE communication with the application server is
required). To preserve security, each application keytab file provides
read-only file permissions to the application server, and must deny access to
all other UNIX users.

Note: It is very important that these permissions are not changed, as DCE
security will be compromised.

When an application server on a particular SDM is registered to the DCE

application server, an entry is created in a CDS directory called

• /.:/subsys/NT/SDM/clli

where
clli is the CLLI of the DMS switch to which the SDM is connected.

The CDS directory is created automatically when the first application-server

registration to the DCE security database from that SDM takes place.

For more information on registrations to the DCE security database, refer to

OSF DCE Administration Guide – Core Components or your DCE vendor’s
installation/configuration information.

DCE commands and status

Various DCE commands are available on any machine that has been
included in a DCE cell. To access these commands, type “dcecp” at the
UNIX prompt.

Each SDM that has been included in a DCE cell is equipped with a DCE
monitoring tool called dcemonitor, that determines status and checks for
error conditions. Most DCE troubleshooting activities for an SDM must be
carried out from the SDM itself.

Wireless Networks Family SDM–SX User Guide SDMPL011

3-32 SDM system administration overview

Access to DCE-based applications across a firewall

Special measures must be taken for DCE-based applications to work when
the SDM is separated from
• the DCE cell’s security and CDS servers, by a firewall (or some other
filtering device
• a workstation that runs an SDM client program

The SDM restricts the TCP and universal datagram protocol (UDP) ports
that it uses for accepting DCE RPCs. These RPCs communicate between
application client programs, or DCE management utilities, and DCE-based
programs running on the SDM.

Restricting ports for incoming connections works in combination with

firewalls by implementing a packet-filtering technique. Consult the firewall
vendor documentation to determine if your firewall can be used this way.

Adding and removing port restrictions

DCE port ranges can be restricted to a range that is predefined by SDM
software or to a specified range determined by a system administrator.
When port restrictions are removed, the SDM returns to the default values
for the DCE ports. This allows the DCE ports to be randomly assigned.

For detailed instructions on adding and removing port restrictions, refer to

the following procedures in the “SDM system administration procedures”
chapter in this document:
• ”Restricting ports to an SDM defined range” on page 6-110
• ”Restricting ports to a specific range” on page 6-120
• ”Removing port restrictions” on page 6-115

Executing SDM-specific DCE commands on other machines

Many DCE commands described in this document, that pertain to a specific
SDM, can be executed on any machine configured as a DCE node in the
DCE cell of which that SDM is a member. The exceptions are described in
table 3-3. An administrator DCE login is usually required. For security
reasons, Nortel recommends that, whenever possible, you do not execute
DCE commands from a remote terminal that uses Enhanced Terminal
Access (ETA) or telnet to connect to the SDM. The DCE login is risky in
such cases because the administrator’s userID and password are passed
unprotected over the network.

Interactions between the dcecp program and the DCE security server are
protected by encryption and cannot be compromised. It is not necessary, and
not advised, to run the commands on the same machine as the security
server.

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-33

Table 3-3xxx
DCE commands – SDM vs remote node

Procedures that must be executed from Procedures that can be executed on any node
the SDM that is part of the DCE cell

configuring an SDM in a DCE cell using configuring an SDM in a DCE cell (administrative
full configuration portion only). The administrative portion consists of:
• logging in as any user that can execute UNIX
configuring an SDM in a DCE cell using commands to a machine other than the SDM
local configuration being configured
adding an SDM application server (as • invoking the “mkdce -o admin” command
described in the SDM application NTPs) adding an SDM user

removing an SDM application server creating or modifying SDM application network data
(for example, assigning the ETA CM and SDM
enabling, disabling or viewing dcemonitor userIDs to a user)
data

most DCE troubleshooting problems

Invoking DCE-based applications

Users of DCE-based GUI applications at remote workstations must provide
a userID and password to DCE. This is done in one of three ways,
depending on how the remote workstation has been configured:
• If the workstation has been configured to use integrated DCE login, the
userID and password are provided to DCE automatically each day,
whenever UNIX usage or UNIX login first occurs.
• If the workstation has not been configured to use integrated DCE login,
but a dce_login command is contained in the user’s profile, a dce_login
prompt will be issued when the user logs in to the workstation. All
DCE-usage credentials are valid for several hours, and another dce_login
prompt is issued shortly before their expiry.
• If the workstation has not been configured to use integrated DCE login,
and the user’s profile does not contain a dce_login command, the user
must log in each time a DCE-based application is invoked. (A DCE
login dialog is issued whenever a user tries to invoke such an application
without invoking the dce_login command.) The DCE-usage credentials
must be renewed every few hours; a renewal dialog is issued prior to
their expiry, although renewal can occur after expiry without adverse
impacts.

Wireless Networks Family SDM–SX User Guide SDMPL011

3-34 SDM system administration overview

DCE application servers after an SDM restore

As with a human user, the DCE-based application servers running on the
SDM must log in to DCE to obtain credentials necessary to decrypt the
authentication data coming from GUI clients, and to register in the DCE cell
directory service. Application servers log in to DCE by getting keys, the
equivalent of passwords, from keytab files stored in the non-volatile storage
area of the SDM. Application servers may also need to change their keys to
reinforce security.

The time period after which an application server needs to change its key is
the shorter value of the pwdlife attribute of the server’s account in the DCE
security registry, and the value of the pwdlife attribute for the organization to
which the server belongs. (By default, the SDM servers belong to the
sdm-servers organization.) The default values of both pwdlife attributes are
“forever”, which (if retained) means that the key never gets changed.
However, if the value for either attribute is changed by the DCE
administrator, the SDM servers will automatically modify their keys in the
keytab files before they expire.

If an SDM application server automatically modifies its key between the

time the SDM disk was backed up and the time the SDM was restored from
tape, restoring the SDM from tape will cause the application server to revert
back to an obsolete key. If this occurs, the DCE-based application state is
displayed as failed (Fail) at the application menu level of the RMI. The
same situation occurs if the restore occurs from a tape other than the most
recent one, and the key has been modified at any time since that tape’s
creation. To restore a server that has failed for this reason, it is necessary to
re-execute the command to create the application server’s account in DCE,
as documented in the NTP for the application.

The SDM DCE software which is responsible for the core DCE servers, also
uses a keytab file. If this software gets an obsolete key after a system
restore, DCE will fail on the SDM. The state of DCE is then displayed as
SysB at the LAN menu level of the RMI.

To recover from this situation, the SDM must be removed and reconfigured
in the DCE cell, as documented in the following procedures in the “SDM
system administration procedures” chapter in this document:
• ”Distributed Computing Environment – Removing an SDM from a DCE
cell”
• ”Distributed Computing Environment – Configuring an SDM in a DCE
cell”

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-35

DCE problems requiring manual intervention

ATTENTION
This section contains technical material addressed to experienced DCE
system administrators only. Other users who suspect DCE problems
must contact an experienced DCE administrator, or their next level of
support.

The SDM detects common DCE failure conditions, reports them to the SDM
node control facility, and automatically takes the appropriate recovery action
to clear the problem. Dcemonitor dumps its current status, problems found,
and the recovery action in a file that is regularly rewritten. The status of
DCE, reported by dcemonitor, is displayed under the connectivity level of
the remote maintenance interface (RMI). To view the status file, refer to the
“SDM system administration procedures” chapter in this document.

Table 3-4 lists examples of problem text that is displayed under the LAN
menu level of the RMI, and describes the triggers and solutions for each
problem. Table 3-4 is not representative of all DCE failure conditions, as it
is impossible to predict all failures that may occur.

Table 3-4xxx
DCE problem text at RMI Con menu level

Problem text Trigger Action

/etc/rc.dce file DCE software is not Type “lslpp -L grep dce” to verify
cannot be read installed or was removed fileset installation. (There are
from the SDM. about 20 filesets).

The /etc/rc.dce file was Reinstall the SDM operating

accidentally removed. system software.
DCE has not been DCE is not commissioned Configure DCE on the SDM. Refer
commissioned - daemon on the SDM. to the procedure, ”Distributed
not enabled Computing Environment –
Configuring an SDM in a DCE cell”
on page 6-61 in the “SDM system
administration procedures” chapter
of this document.

—continued—

Wireless Networks Family SDM–SX User Guide SDMPL011

3-36 SDM system administration overview

Table 3-4xxx
DCE problem text at RMI Con menu level (continued)

Problem text Trigger Action

daemon is not running The specified daemon is not Execute the daemon manually as
or running. It may be crashing the root user from a UNIX shell.
after /etc/rc.dce has started Check the DCE command
daemon error message
it. reference manual for the debug
from rc.dce syntax options for more error
information. Depending on the
Note: daemon can be: daemon that is reported as failing,
check for log files under:
• dced
• /opt/dcelocal/var/dced
• sec-client service
• /opt/dcelocal/var/adm/directory
• cdsadv /cds
• dtsd • /opt/dcelocal/var/security
• /opt/dcelocal/var/time/adm/dtsd
• /opt/dcelocal/var/adm/time
• /opt/dcelocal/var/svc/error.log
• /opt/dcelocal/var/svc/fatal.log
The cell security service or Ensure that the cell security
the CDS are malfunctioning. service and the CDS server are
both functioning properly.

The time on the SDM and Use the UNIX date command to
the security server in the check SDM time. Ensure that the
DCE cell are not within 5 SDM time is within 5 minutes of the
min of each other. cell security server time. SDMs
and security servers can be on
different time zones if their times
are within 5 minutes of each other
when they are converted to
universal time clock (UTC).
cannot find telcolan The /etc/hosts file is Check that the /etc/hosts file
entry in /etc/hosts damaged, and dcemonitor contains a line formatted as:
file cannot compute the xxx.xx.xx.xx hostname telcolan.
or operating company LAN IP Fix the /etc/hosts file by setting the
address of the SDM. SDM IP address using the RMI.
cannot extract sdm IP
addr and hostname from
/etc/hosts

—continued—

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-37

Table 3-4xxx
DCE problem text at RMI Con menu level (continued)

Problem text Trigger Action

cannot get the Dcemonitor cannot read the From dcecp, type “hostdata
host_name from the DCE hostname from the catalog”. One of the listed entries
config hostdata hostdata configuration ends with host_name. Then type
database information. “hostdata show host_name”.
Ensure the hostdata output
contains a line formatted as
hostdata/data hosts/hostname.
The hostname is the same as the
UNIX hostname. If you cannot
display hostdata information,
remove and reconfigure DCE on
the SDM.

Refer to the procedures,

”Distributed Computing
Environment – Removing an SDM
from a DCE cell” on page 6-74 and
”Distributed Computing
Environment – Configuring an
SDM in a DCE cell” on page 6-61
in the “SDM system administration
procedures” chapter of this
document.
CDS is malfunctioning.
Ensure that CDS server is
functioning properly.

—continued—

Wireless Networks Family SDM–SX User Guide SDMPL011

3-38 SDM system administration overview

Table 3-4xxx
DCE problem text at RMI Con menu level (continued)

Problem text Trigger Action

cannot list / CDS is malfunctioning. Ensure that the CDS server is

.:/hosts/hostname functioning properly.

The machine “self” principal Check that the ACL on this

does not have all its directory. The machine “self”
permissions set. principal must have all permissions
set.

Check that CDS contains a / .

:/hosts/hostname directory.

Reconfigure DCE on the SDM.

Refer to the procedure,
”Distributed Computing
Environment – Configuring an
SDM in a DCE cell” on page 6-61
in the “SDM system administration
procedures” chapter of this
document.

—continued—

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-39

Table 3-4xxx
DCE problem text at RMI Con menu level (continued)

Problem text Trigger Action

cannot unexport bad The SDM has IP addresses Check the bindings for the faulty / .
IP address from / for the operating company :/hosts/hostname/server entry to
.:/hosts/hostname/serv LAN, and the switch. DCE make sure it does not contain the
er entry daemons export these IP address of the SDM as seen
or addresses in bindings from the CM side.
stored in CDS. Because
/
the switch-side IP address
.:hosts/hostname/serve
cannot be reached from any
r entry contains a bad
client from the operating
IP address, and a good
company LAN, dcemonitor
binding cannot be
looks for these bindings,
computed and removes or replaces
or them with equivalent
cannot re-export I/F bindings containing the
interface UUID to operating company IP
/.:/hosts/hostname/ser address only. This error
ver entry message indicates that this
substitution cannot be done.

CDS is malfunctioning. The Ensure that the CDS server is

machine “self” principal functioning properly. Check the
does not have all its ACL on the CDS server entry. The
permissions set. machine “self” principal must have
all permissions set. Reconfigure
DCE on the SDM. Refer to the
procedure, ”Distributed Computing
Environment – Configuring an
SDM in a DCE cell” on page 6-61
in the “SDM system administration
procedures” chapter of this
document.

—continued—

Wireless Networks Family SDM–SX User Guide SDMPL011

3-40 SDM system administration overview

Table 3-4xxx
DCE problem text at RMI Con menu level (continued)

Problem text Trigger Action

The DCE hostname The SDM UNIX hostname Check the DCE hostname in the
($dce_hostname) (defined in the /etc/hosts file /opt/dcelocal/dce_cf.db. Check
doesn’t match the SDM file) does not match the that the /etc/hosts file contains a
unix hostname: DCE hostname of the SDM line formatted as xxx.xx.xx.xx
(hostname). DCE that was defined when DCE hostname telcolan. If the line is
re-configuration is was commissioned. The incorrect, correct it using the RMI.
required. /etc/hosts file is formatted Reconfigure DCE on the SDM.
incorrectly. Refer to the procedure,
”Distributed Computing
Environment – Configuring an
SDM in a DCE cell” on page 6-61
in the “SDM system administration
procedures” chapter of this
document.
cannot find CLLI (cm Dcemonitor cannot identify The CLLI is dynamically
alias) entry in the CLLI of the switch. transmitted from the CM to the
/etc/hosts file SDM and stored in the /etc/hosts
file. Check the file for a line
formatted as xxx.xx.xx.xx cm clli. If
the file does not contain this line,
execute the Change command at
the connectivity (Con) menu level
of the RMI, and accept the default
values. See the “SDM
maintenance overview” chapter for
more information.
cannot get the list Dcemonitor cannot list the At the dcecp prompt, execute the
of keytabs from the key tables for the machine. dcecp command manually as the
config hostdata root user by typing “keytab
database catalog”. Note the error message.
You may have to reconfigure DCE
on the SDM. If required, refer to
the procedure, ”Distributed
Computing Environment –
Configuring an SDM in a DCE cell”
on page 6-61 in the “SDM system
administration procedures” chapter
of this document.

—continued—

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-41

Table 3-4xxx
DCE problem text at RMI Con menu level (continued)

Problem text Trigger Action

self keytab cannot be Dcemonitor cannot list the At the dcecp prompt, execute the
shown keys for the machine “self” dcecp command manually as the
principal, the principal name root user by typing “keytab show
that the DCE daemon uses. self”. Note the error message.
You may have to reconfigure DCE
on the SDM. If required, refer to
the procedure, ”Distributed
Computing Environment –
Configuring an SDM in a DCE cell”
on page 6-61 in the “SDM system
administration procedures” chapter
of this document.
host data cannot be Dcemonitor cannot list local At the dcecp prompt, execute the
shown host data information. dcecp command manually as the
root user by typing “show hostdata
cell_name”. Note the error
message. You may have to
reconfigure DCE on the SDM. If
required, refer to the procedure,
”Distributed Computing
Environment – Configuring an
SDM in a DCE cell” on page 6-61
in the “SDM system administration
procedures” chapter of this
document.

—continued—

Wireless Networks Family SDM–SX User Guide SDMPL011

3-42 SDM system administration overview

Table 3-4xxx
DCE problem text at RMI Con menu level (continued)

Problem text Trigger Action

Detected a CLLI Dcemonitor has detected Check that the /etc/hosts file
mismatch between that the CLLI portion of one contains a line formatted
principal and the of the application server xxx.xx.xx.xx cm clli. If the CLLI is
SDM’s CLLI: clli. names is different from the incorrect, correct it on the CM. If
Server reconfiguration CLLI of the switch stored in the problem is with the application
is required. the /etc/hosts file because server principal name, remove
of a recent change in the each application server, and
switch CLLI. The format in recreate.
the /etc/hosts file may also
be incorrect. To identify all application servers
on an SDM, type “key show [key
catalog]” at the dcecp prompt.
Refer to the
procedures,”Distributed Computing
Environment – Removing a DCE
based SDM application server” on
page 6-74 and ”Distributed
Computing Environment –
Configuring an SDM in a DCE cell”
on page 6-61 in the “SDM system
administration procedures” chapter
of this document.
endpoint cannot be Dcemonitor cannot list the From the dcecp prompt, execute
shown remote procedure call the dcecp command manually as
(RPC) endpoint information. the root user by typing “show
endpoint”. Note the error
message. You may have to
reconfigure DCE on the SDM. If
required, refer to the procedure,
”Distributed Computing
Environment – Configuring an
SDM in a DCE cell” on page 6-61
in the “SDM system administration
procedures” chapter of this
document.

—continued—

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-43

Table 3-4xxx
DCE problem text at RMI Con menu level (continued)

Problem text Trigger Action

could not get clearing Dcemonitor cannot list the From the dcecp prompt, execute
house information CDS clearing houses. the dcecp command manually as
the root user by typing
“clearinghouse catalog”. Note the
error message.

CDS is malfunctioning. Ensure that the CDS server is

functioning properly.

The IP address of the CDS Check the IP address of the CDS

server may have changed. server. You may have to
Cdsadv cannot find the reconfigure DCE on the SDM. If
server because its required, refer to the procedure,
broadcasts are blocked by a ”Distributed Computing
router. Environment – Configuring an
SDM in a DCE cell” on page 6-61
in the “SDM system administration
procedures” chapter of this
document.
Cdscache cannot be Dcemonitor cannot dump At the dcecp prompt, execute the
dumped the contents of its local dcecp command manually as the
directory cache. root user by typing “cdscache
show clearinghouse”. Note the
error message.

The IP address of the CDS Check the IP address of the CDS

server may have changed. server.

Cdsadv is unable to find the If the SDM is separated by a router

server because its from the CDS server, it depends on
broadcasts are blocked by a defined cached server information
router. stored in the cache. As root user
on the SDM, check the IP
CDS is malfunctioning. addresses by typing:

The IP address does not • “cd /opt/dcelocal/var/adm/

match the IP address of the directory/cds”
CDS server.
• “cat cds_cache.wan”

—continued—

Wireless Networks Family SDM–SX User Guide SDMPL011

3-44 SDM system administration overview

Table 3-4xxx
DCE problem text at RMI Con menu level (continued)

Problem text Trigger Action

The number of the current Check that the current cache dump
cache dump does not match which corresponds to the
the number contained in cds_cache.0000xxxx file, matches
cds_cache.version. the number contained in the
cds_cache.version by typing
• “ls cds_cache*”
• “cat cds_cache.version”
If the cds_cache.0000xxxx file
does not match the number
contained in the
cds_cache.version, rename the
cds_cache.0000xxxxfile and the
cds_cache.version files to a
temporary name, and restart the
daemons by typing

• “/etc/dce.clean”
• “/sdm/mtce/dce/dcestart”
Ensure that the CDS server is
functioning properly.
directory cannot be Dcemonitor cannot perform At the dcecp prompt, execute the
shown a basic CDS command. dcecp command manually as the
CDS is malfunctioning. root user by typing “show dir / .: ”
Ensure that the CDS server is
functioning correctly.

—continued—

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-45

Table 3-4xxx
DCE problem text at RMI Con menu level (continued)

Problem text Trigger Action

could not get dts Dcemonitor cannot get At the dcecp prompt, execute the
synchronization status information from the dcecp command manually as the
information DTS daemon. root user by typing
or • “dta show -all”
clock cannot be shown
• “clock show”
The cell security service or Ensure that the cell security
CDS are malfunctioning. service and the CDS server are
functioning properly.
The time on the SDM is not Use the UNIX date command to
within 5 min of the security check the SDM time. Ensure that
server in the DCE cell. the SDM time is within 5 min of the
cell’s security server. SDMs and
security servers can be on different
time zones if their times are within
5 min of each other when they are
converted to universal time clock
(UTC).
DTS clock not The SDM internal clock is At the dcecp prompt, type “clock
synchronized, not properly synchronized to show” to determine if the
undetermined drift the DTS time servers on the synchronization is improving or
or network. deteriorating. The output of the
command is
DTS drifting, more
1997-01-31-13:52:23.818-05
than 2 minutes off :00I0.751 [-----]
or imprecision. The value after
DTS drifting, more the “I” is the imprecision. Repeat
than 4 minutes off, the command over time, and look
DCE will fail soon at the imprecision. If the
imprecision is decreasing, wait for
the clocks to synchronize
themselves. If the imprecision is
increasing, or is undetermined (as
indicated by a set of dashes), the
problem must be corrected before
the SDM clock differs over 5 min
with the security server clock. If
the time difference exceeds 5 min,
the DCE server to the SDM will
terminate.

—continued—

Wireless Networks Family SDM–SX User Guide SDMPL011

3-46 SDM system administration overview

Table 3-4xxx
DCE problem text at RMI Con menu level (continued)

Problem text Trigger Action

The SDM cannot find Determine if the SDM is finding

enough DTS time servers to enough DTS time servers to
synchronize with. synchronize with by typing “dts
show -all” at the dcecp prompt.
Look at the value for
toofewservers and
nointersections counters.
Check to see if the value is
anything but zero, and whether it is
increasing each time the DTS
attempts to resynchronize.

The SDM does not have Determine if the SDM has access
access to enough local or to enough local or global servers.
global servers. The minimum number of servers is
indicated by the minservers
attribute . Display the minservers
attribute by typing “dts show -all” at
the dcecp prompt.

The LAN profile does not At the dcecp prompt, check the
contain machines that are LAN profile by listing the LAN that
running as DTS local the SDM was commissioned on by
servers. typing
• “profile show / . :/hosts/SDM
hostname/profile”
• “rpcprofile list profile obtained
above”
Ensure the profile contains enough
machines that are running as DTS
local servers. (There must be at
least three DTS servers per LAN).

Review OSF DCE Administration

Guide – Core Components for
more guidelines on how to
administer DTS.

—end—

297-5061-901 Standard 01.01 December 1998

 SDM system administration overview 3-47

Table 3-5xxx
Problems with DCE Networks that host SDM applications

Problem Action

Each of the SDMs in your cell go SysB Contact Nortel Technical Assistance
and the DCE service is SysB on all SDMs
DCE–based programs fail to operate on Contact Nortel Technical Assistance
client workstations
DCE client workstations cannot complete Contact Nortel Technical Assistance
their boot sequence when rebooted
An SDM or a client workstation in the DCE Contact Nortel Technical Assistance
cell is unable to perform any DCE opera-
tions.
Cannot reboot a workstation that is a client in Contact Nortel Technical Assistance
the DCE cell
Cannot bring the server back to service Contact Nortel Technical Assistance

Wireless Networks Family SDM–SX User Guide SDMPL011

 4-1

SDM maintenance procedures

Introduction to SDM maintenance procedures
This chapter contains SDM maintenance procedures that can be performed
by operating company personnel who have maintenance user (or root user)
permissions for accessing the SDM. Each procedure contains the following:
• explanatory and context-setting information
• summary flowchart
• step-action instructions
Note: I/O expansion chassis is not supported.

Explanatory and context-setting information

Depending on the type of procedure, the first page of each procedure may
contain the following headings:
• Indication (where an alarm appears on the MAP display)
• Meaning (what the alarm means)
• Impact (how the alarm affects service)
• Application (why you would perform the procedure)
• Action (how to use the flowchart and step-action instructions)

Summary flowchart
The flowchart is only a summary of the main actions, decision points, and
possible paths you may take. Do not use the summary flowchart to perform
the procedure. Instead, use it to preview what you will be doing and to
prepare for it. For example, if you see that the procedure involves actions at
the SDM site, you will know to advise that office before you begin the
step-action instructions.

Step-action instructions
The step-action instructions tell you how to perform the procedure.
Normally you will perform the steps in order, but you may be directed to
return to a previous step and repeat a sequence. The successful completion

Wireless Networks Family SDM–SX User Guide SDMPL011

4-2 SDM maintenance procedures

of a step may depend on previous steps; therefore, always perform the steps
in the order specified.

The step-action instructions provide the command syntax and system

information you use or see while performing the procedure. For help on
DMS and SDM commands or output, see the “About this document” chapter
at the beginning of this document.

Return key and Enter key

The carriage return key is identified in different ways (such as Enter, Return
or Carriage Return) on various types of terminals. It is always used to enter
commands and parameters into the system.

The procedures contained in this book and in other NTPs instruct you to
press the Enter key after each step. If your terminal has a Return key, press
the Return key instead. Do not press the Enter key located beside the
numeric key pad.

297-5061-901 Standard 01.01 December 1998

 4-3 SDM maintenance procedures 4-3

Clearing MAP alarms triggered by the SDM

APPL SDM minor

Application
CM MS IOD Net PM CCS Lns Trks Ext APPL
. . . . . . . . SDM

Use this procedure to clear an APPL SDM minor MAP alarm that has been
triggered by the SDM.

Indication
At the MTC level of the MAP display, SDM appears under the APPL header
of the alarm banner. This appearance indicates an SDM minor alarm.

Meaning
An SDM minor alarm indicates that the SDM is in manual-busy (ManB) or
in-service trouble (ISTb) state.

Impact
If the SDM state at the MAP display is ManB, the SDM was set to that state
by the MAP command.

If the SDM state at the MAP display is ISTb, the computing module (CM)
is receiving ISTb status from the SDM. One or more of the following
conditions exist:
• One or more SDM applications have failed, but at least one application
has not failed.
• A system software resource has exceeded its alarm threshold.
• The SDM cannot communicate with one or more defined nodes on the
local area network (LAN) of the operating company
• The Distributed Computing Environment (DCE) is not in service
• An SDM application is reporting an in-service trouble condition.
• A hardware device failure has been reported.
• There is an Internet protocol (IP) mismatch between the CM and the
SDM.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-4 SDM maintenance procedures

Clearing MAP alarms triggered by the SDM

APPL SDM minor (continued)
Note: If all SDM applications fail, the SDM node state is system busy
(SysB). The system generates an APPL SDM critical or APPL SysB critical
alarm.

Action
The following flowchart is only a summary of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to clear
the alarm.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-5

Clearing MAP alarms triggered by the SDM

APPL SDM minor (continued)
Summary of Clearing MAP alarms triggered by the SDM–APPL SDM minor

This flowchart summarizes the

procedure.

Use the instructions in the

procedure that follows this
flowchart to perform the
Determine the procedure.
type of fault at
the MAP display

ISTb ManB

Y Isolate and RTS the SDM

Hardware
clear the 1
faults?
hardware fault
N
1
Isolate and
clear the
resource fault

1
End

Wireless Networks Family SDM–SX User Guide SDMPL011

4-6 SDM maintenance procedures

Clearing MAP alarms triggered by the SDM

APPL SDM minor (continued)
Clearing MAP alarms triggered by the SDM – APPL SDM minor
At the MAP display
1 Access the SDM level of the MAP display by typing
>MAPCI; MTC; APPL;SDM
and pressing the Enter key.
Example response:
SDM 0 ISTb Links_OOS: 0

2 Check the node state of the SDM at the MAP display.

If the SDM is Do

ManB step 3
ISTb step 4

3 If applicable, determine from office records or other personnel why the SDM
was set to manual busy state. When permissible, return the SDM to service by
typing
>RTS
and pressing the Enter key.
Response:
SDM RTS initiated.
SDM RTS completed.
Go to step 72.

4 Obtain fault status information from the SDM by typing

>QUERYSDM FLT
and pressing the Enter key.

5 Determine if the response indicates a hardware device fault.

If a hardware device fault is Do

not indicated step 6

indicated step 54

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-7

Clearing MAP alarms triggered by the SDM

APPL SDM minor (continued)

6 Determine the type of fault. Note the log fault type for use in later steps.

If the fault is Do

an exceeded resource threshold step 7

a DCE problem step 15
anything else step 16

7 From the response to the QuerySDM FLT command, determine the type of
system resource that has exceeded its alarm threshold.

If the resource exceeded is Do

swap space step 8

number of processes step 8
number of swap queue entries step 8
number of zombie processes step 8
CPU (number of run queue entries) step 8
logical volume (% full) step 12

8 Access the System (Sys) menu level of the RMI by typing

>SYS
and pressing the Enter key.
Example response:
SDM Node State: ISTb
SDM System State: ISTb
SDM Storage State: InSv

# Description Current/Threshold
1 CPU (run queue entries): 1/ 5
2 Number of Processes: 63/250
3 Number of Zombies: 0/ 3
4 Swap Space (% full): 72/ 70*
5 Number of Swap Queue Entries: 0/ 2

Wireless Networks Family SDM–SX User Guide SDMPL011

4-8 SDM maintenance procedures

Clearing MAP alarms triggered by the SDM

APPL SDM minor (continued)

9 Check the current level of the software resource by locating the resource on the
screen.
Note: A pair of numbers is located in the column next to the software resource.
The first number is the current level of the resource. The second number is the
alarm threshold. In the example response in step 12, the current level of “Swap
Space” is 72. This level exceeded the threshold of 70.

10 If the current level of the software resource is acceptable, increase the size of
the threshold to clear the alarm. Complete the procedure, “Changing system
thresholds,” in this chapter, and return to this point.
Note: If you are not sure of the acceptability of the software resource level, go
to step 91.
If the current level of the software resource is not acceptable, go to step 71.

11 Wait 5 minutes. Check to see if the alarm has cleared.

If the Do

alarm has not cleared step 71

alarm has cleared step 72

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-9

Clearing MAP alarms triggered by the SDM

APPL SDM minor (continued)

12
CAUTION
Potential Service Interruption
A logical volume on the SDM must never reach 100%
disk full. The system enters into abnormal conditions
when a logical volume reaches 100% disk full.

If a logical volume exceeds its alarm threshold,

contact your system administrator. The system
administrator must assess the current condition of the
logical volume and take appropriate action
immediately. If required, contact Nortel for
assistance.

The usage level of the specified logical volume has exceeded its alarm
threshold.
Access the storage menu level of the RMI by typing
>STORAGE
and pressing the Enter key.
Example response:
SDM Node State: ISTb
SDM System State: ISTb
SDM Storage State: ISTb

rootvg:
Volume Size (MB) (% full/ threshold)
1 / 240 52/ 80
2 /usr 204 82/ 90
3 /var 40 35/ 70
4 /tmp 24 21/ 90
5 /home 304 75/ 70*
6 /sdm 304 47/ 90
7 /home/sba 16 7/ 80
(unallocated) 608

Wireless Networks Family SDM–SX User Guide SDMPL011

4-10 SDM maintenance procedures

Clearing MAP alarms triggered by the SDM

APPL SDM minor (continued)

13 If the current usage level of the logical volume is acceptable, increase the size
of the logical volume threshold. Complete the procedure, “Changing logical
volume thresholds,” in this chapter, and return to this point.
Note: Do not change the system threshold if the current usage of the logical
volume is greater than 95%.
If the current usage level of the logical volume is not acceptable, complete the
procedure, “Increasing the size of a file system,” in this chapter. If you require
assistance to help you determine if the current resource is acceptable, go to
step 71.

14 Wait 5 minutes. Check to see if the alarm has cleared.

If the Do

alarm has not cleared step 71

alarm has cleared step 72

15 Have your system administrator isolate and clear the DCE problem.
Note: DCE troubleshooting information is provided in the “SDM system
administration overview” chapter of this document.
Go to step 72.

At the local or remote VT100 console

16 Log in to the SDM as the root user or the maint user.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-11

Clearing MAP alarms triggered by the SDM

APPL SDM minor (continued)

17 Access the top menu level of the remote maintenance interface (RMI) by typing
# sdmmtc
and pressing the Enter key.

18 Access the maintenance (Mtc) menu level of the RMI by typing

>2
and pressing the Enter key.

19 Proceed according to the type of fault defined in step 10 as “anything else.”

If the fault is Do

an application software problem step 20

(package/process fault)
a CM connectivity problem (fault step 29
type CM)
an operating company LAN step 45
connectivity problem (fault type
LAN)

20 Access the application (Appl) menu level of the RMI by typing

>4
and pressing the Enter key.
Example response:
SDM Node State: InSv
SDM Application State: InSv

# Package Description Version State

1 Table Access Service 10.0.29.0 InSv
2 OM Access Service 10.0.29.0 ManB
3 Log Delivery Service 10.0.29.0 InSv

Wireless Networks Family SDM–SX User Guide SDMPL011

4-12 SDM maintenance procedures

Clearing MAP alarms triggered by the SDM

APPL SDM minor (continued)

21 Determine the affected application from the display and note its key number,
shown under the header “#”.

If the package is Do

Table Access Service step 27

Operation Measurements step 27
Log Delivery Service step 27
anything else step 28

22 Proceed depending on the state of the out-of-service application software

package.

If the package state is Do

ManB step 23
ISTb or SysB step 25
Fail step 26

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-13

Clearing MAP alarms triggered by the SDM

APPL SDM minor (continued)

23 The application software package is in manual-busy state. Determine from

office records or other personnel why the application was manually removed
from service. When permissible, return the application software package to
service by typing
>RTS key
and pressing the Enter key.
where
key is the key number of the application, shown under the header “#”.
Response:
Application RTS - Command initiated.
Please wait...
When the RTS command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Response:
Application RTS – Command submitted.
Go to step 72.

24 The specified application software package has been set to in-service trouble
(ISTb) state during initialization. Allow 10 min for the packages to complete
initialization.

If the package Do

remains ISTb step 71

changes to InSv state step 72

Wireless Networks Family SDM–SX User Guide SDMPL011

4-14 SDM maintenance procedures

Clearing MAP alarms triggered by the SDM

APPL SDM minor (continued)

25 The specified application software package was set to system-busy (SysB) or

in-service trouble (ISTb) state because it failed for one of the following reasons:
• The system cannot restart the package.
• The application has restarted and failed three times within its designated
failure threshold (10 min).
At the application menu level of the RMI, manually busy the affected application
software package by typing
>BSY key
and pressing the Enter key.
where
key is the key number of the application, shown under the header “#”
Response:
Application Bsy - Command initiated.
Please wait...
When the Bsy command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Response:
Application Bsy – Command submitted.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-15

Clearing MAP alarms triggered by the SDM

APPL SDM minor (continued)

26 Return the application to service by typing

>RTS key
and pressing the Enter key.
where
key is the key number of the application, shown under the header “#”
Response:
Application RTS - Command initiated.
Please wait...
When the RTS command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Response:
Application RTS – Command submitted.

27 Proceed depending on the state of the application software package.

If the package Do

remains ISTb step 71

changes to InSv state step 72

28 Consult the documentation for the specified application software package to

diagnose and clear the problem.
Go to step 72.

29 Determine if the response indicates an IP address mismatch.

If the response indicates Do

an SDM IP address mismatch step 30

a CM IP address mismatch step 31
anything else step 71

Wireless Networks Family SDM–SX User Guide SDMPL011

4-16 SDM maintenance procedures

Clearing MAP alarms triggered by the SDM

APPL SDM minor (continued)
At the MAP display
30 Access table SDMINV, and record the datafilled value for the SDM CM-side IP
address (field IPADDR), by typing
>TABLE SDMINV; LIST ALL
and pressing the Enter key.
Go to step 32.

At the MAP display

31 Access table IPNETWRK and record the datafilled value for the CM IP address
(field CMIPADDR), by typing
>TABLE IPNETWRK; LIST ALL
and pressing the Enter key.

At the local or remote VT100 console

32 Access the CM-to-SDM connectivity (Con) menu level by typing
>CON
and pressing the Enter key.

33 Determine how the CM IP address, SDM CM-side IP address, and CM/SDM

netmask are commissioned on the SDM by typing
>QUERYSDM
and pressing the Enter key.
Example response:
CM IP Address: 47.105.155.1
SDM IP Address: 47.105.155.6
CM/SDM Netmask: 255.255.255.240

34 Using office records, have your system administrator review the IP address
information to determine the correct values for the system.

If Do

the CM IP address datafill is step 35

incorrect
the SDM CM-side IP address datafill step 36
is incorrect
any of the IP address parameters step 37
are commissioned incorrectly on the
SDM
all values appear to be correct step 71

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-17

Clearing MAP alarms triggered by the SDM

APPL SDM minor (continued)

At the MAP display

35 Correct the datafill for the CM IP address in table IPNETWRK by typing
>TABLE IPNETWRK; CHA CMIPADDR
and pressing the Enter key.
Go to step 72.

36 Correct the datafill for the SDM CM-side IP address in table SDMINV by typing
>TABLE SDMINV; CHA IPADDR
and pressing the Enter key.
Go to step 72.

At the MAP display

37 Manually busy the SDM by typing
>BSY
and pressing the Enter key.
Response:
SDM Bsy initiated.
SDM Bsy completed.

At the local or remote VT100 console

38 At the connectivity (Con) menu level of the RMI, access the change editor for
the CM side IP parameters by typing
>CHANGE
and pressing the Enter key.

39 Each editable parameter is displayed in turn. Press the Enter key until the
parameter you wish to correct is displayed.

40 At the command line, type the correct value and press the Enter key.
Example response:
Values to be changed:
CM IP address: 47.105.145.1
SDM IP address: 47.105.145.6
SDM-SDM LAN netmask: 255.255.255.248

Enter Y to confirm, N to reject or E to edit.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-18 SDM maintenance procedures

Clearing MAP alarms triggered by the SDM

APPL SDM minor (continued)

41 Determine if the displayed values are correct.

If the displayed values are Do

incorrect step 42
correct step 43

42 Edit the values by typing

>E
and pressing the Enter key.
Go to step 39.

43 Save the change and exit the change editor by typing

>Y
and pressing the Enter key.

At the SDM level of the MAP display

44 Return the SDM to service by typing
>RTS
and pressing the Enter key.
Response:
SDM RTS initiated.
SDM RTS completed.
Go to step 72.

45 Contact your LAN network administrator to determine if the communications

problem is external to the SDM. That is, the communications problem is due to
other problems on the operating company LAN. (For example, the LAN host is
out of service.)

If the fault is Do

not on the operating company LAN step 46

on the operating company LAN step 72

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-19

Clearing MAP alarms triggered by the SDM

APPL SDM minor (continued)
At the local or remote VT100 console
46 Access the LAN menu level of the RMI by typing
>LAN
and pressing the Enter key.
Example response:
# DESCRIPTION HOSTNAME ADDRESS STATE
1 626 FT Machine bnode7c8 47.18.32.25 SysB

47 Determine if the IP address shown for the affected LAN hostname is correct.

If the IP address is Do

incorrect step 48
correct step 71

48 Access the change editor by typing

>CHANGE n
and pressing the Enter key.
where
n is the numeric key for the hostname entry, shown under the “#”
header

49 Each editable parameter is displayed in turn. Press the Enter key until the IP
address is displayed.

50 Type the correct IP address for the LAN node at the command line and press
the Enter key.
Example response:
Values to be changed for Telco Node 1:
Telco Node Description: 626 FT Machine
Telco Node Hostname: bnode7c8
Telco IP Address: 47.18.32.52

Enter Y to confirm, N to reject or E to edit.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-20 SDM maintenance procedures

Clearing MAP alarms triggered by the SDM

APPL SDM minor (continued)

51 Determine if the displayed values are correct.

If the displayed values are Do

correct step 52
incorrect step 53

52 Save the change and exit the change editor by typing

>Y
and pressing the Enter key.
Note: The node state changes to InSv within 2 min.
Go to step 72.

53 Edit the values by typing

>E
and pressing the Enter key.
Go to step 49.

At the MAP display

54 Determine if the fault reason indicates a cable fault.

If a cable fault is Do

indicated step 55
not indicated step 57

Note: If there is a cable fault, the Ethernet device is the only faulty device on
the module.

55 From the QuerySDM FLT response, determine which cable is affected and its
location. By physical inspection, determine if the cable has been disconnected
or physically damaged.

If a cable Do

requires reconnection or repair step 56

appears undamaged and correctly step 71
connected

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-21

Clearing MAP alarms triggered by the SDM

APPL SDM minor (continued)

56 Reconnect, repair, or replace the cable as appropriate.

Go to step 72.

57 From the QuerySDM FLT response, determine the affected device type and its
state.

If the device state is Do

ManB step 58
Failed step 63

58 Determine from office records or other personnel why the device was manually
removed from service. When permissible, return the device to service.

59 Log in to the SDM as the root or maint user.

60 Access the top menu level of the remote maintenance interface (RMI) by typing
# sdmmtc
and pressing the Enter key.

61 Access the hardware menu level of the RMI by typing

>HW
and pressing the Enter key.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-22 SDM maintenance procedures

Clearing MAP alarms triggered by the SDM

APPL SDM minor (continued)

62 Return the device to service by typing

>RTS n device
and pressing the Enter key.
where
n is the domain number (0 or 1) of the device that you are returning to
service
device is hardware device name that you are returning to service.
Example response:
Hardware RTS : Domain 0 Device ETH - Command initiated.
Please wait...
When the RTS command is finished, the “Please wait...” message, and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Response:
Hardware RTS : Domain 0 Device ETH – Command submitted.
Go to step 72.

63 Determine if the QuerySDM FLT response indicates an interconnect module

(ICM) failure.

If an ICM failure is Do

indicated step 64
not indicated step 70

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-23

Clearing MAP alarms triggered by the SDM

APPL SDM minor (continued)

64 Have qualified power maintenance personnel verify that power is available from
the MSP to the failed ICM.
Note: If the SDM loses one –48V dc power feed, it continues to provide service
using the other power feed. The loss of one feed removes one input/output
(I/O) domain from service. On the affected modules, the module in-service
LEDs are off, and the out-of-service LEDs are on. These modules cannot be
returned to service until power is restored.

If Do

the ICM has failed due to step 65

interruption of its power feed
the ICM power feed is OK step 70

At the local or remote VT100 console

65 Log in to the SDM as the root user or the maint user.

66 Access the top menu level of the remote maintenance interface (RMI) by typing
# sdmmtc
and pressing the Enter key.

67 Access the hardware menu level of the RMI by typing

>HW
and pressing the Enter key.

68 Have qualified power maintenance personnel restore the power feed to the
ICM.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-24 SDM maintenance procedures

Clearing MAP alarms triggered by the SDM

APPL SDM minor (continued)
(end)

69 At the hardware (Hw) menu level of the RMI, return the main chassis ICM (that
has failed due to loss of power) to service by typing
>RTS 1 ICM
and pressing the Enter key.
Example response:
Hardware RTS : Domain 1 Device ICM – Command initiated.
Please wait...
When the RTS command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Example response:
Hardware RTS: Domain 1 Device ICM – Command submitted.
Note: The out-of-service ICM can be identified by an “F” under its header on
the RMI display. It can also be visually identified at the back of the SDM by its
in-service LED off, and its out-of-service LED on.

70 Replace the failed device using the appropriate procedure in the “SDM
hardware replacement procedures” chapter of this document.
Go to step 72.

71 Contact the personnel responsible for the next level of support.

72 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 4-25 SDM maintenance procedures 4-25

Clearing MAP alarms triggered by the SDM

APPL SDM critical

Application
CM MS IOD Net PM CCS Lns Trks Ext APPL
. . . . . . . . SDM
*C*

Use this procedure to clear an APPL SDM critical MAP alarm that has been
triggered by the SDM.

Indication
At the MTC level of the MAP display, SDM *C* appears under the APPL
header of the alarm banner and indicates an SDM critical alarm.

Meaning
An SDM critical alarm indicates that the SDM is sending system busy status
to the CM because it is out of service, or the CM has designated the SDM as
system busy because it is unable to communicate with the SDM.

Impact
If the SDM is out of service, all SDM applications are unavailable.

If the CM is unable to communicate with the SDM, the local state and
operating condition of the SDM are unknown to the CM. MAP commands
requesting state changes to the SDM are not sent to the SDM, and MAP
requests for information from the SDM cannot be completed. The SDM
remote maintenance interface (RMI) can be used to change the local state of
the SDM, or obtain information about the SDM, when the CM-SDM link is
not functioning. When communications are restored, the SDM local state
aligns itself to the CM view of its state.

Action
The following flowchart is only a summary of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to clear
the alarm.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-26 SDM maintenance procedures

Clearing MAP alarms triggered by the SDM

APPL SDM critical (continued)
Summary of Clearing MAP alarms triggered by the SDM — APPL SDM critical

This flowchart summarizes the

Determine
procedure. To perform the
SDM node
procedure, use the detailed
state at MAP
instructions on page 4-27.

SysB /not SysB (NA) SysB

responding

Ext alarm Consult alarm Return MS ports Busy/RTS the

Y
present? clearing 4 to service SDM
procedure

N
4 3
System In Isolate and clear
Y
Service DS512 fault 4
LED on? 1

N SDM
booting? Y
4
SDM Y Restart when
manually permissible 4
shut down? N
3
N
SDM Y SDM boot
Y
booting? completes? 4

N N
1 3

3 4

Contact Nortel for End

assistance.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-27

Clearing MAP alarms triggered by the SDM

APPL SDM critical (continued)
Clearing MAP alarms triggered by the SDM - APPL SDM critical
At the MAP display
1 Access the SDM level of the MAP display by typing
>MAPCI; MTC; APPL;SDM
and pressing the Enter key.
Example response:
SDM SysB(NA) Links_OOS: 2
2 Determine the state of the SDM.

If the state of the SDM is Do

SysB (NA) step 4

SysB / The SDM is not responding step 3
SysB step 68

3 Determine from the response if any links are out of service, as indicated by
“Links_OOS:” (see step 1).

If Do

any of the links are out of service step 5

all links are in service step 15

4 The CM has designated the SDM as system busy because all four message
switch (MS) ports that provide the DS512 links to the SDM are unavailable. The
SDM may still be operational, but it is unable to communicate with the
computing module (CM).

5 Determine the MS hardware that provides the DS512 links to the SDM by
typing
>TRNSL
and pressing the Enter key.
Example response:
SDM 0 DOMAIN 0 PORT 0 (MS 0:15:0) OK ,C MsgCnd:Closed
SDM 0 DOMAIN 0 PORT 1 (MS 1:15:0) ManB MsgCnd:Closed

6 Record the MS port card number that is associated with the SDM DS512 links.
Note: In the example response shown in step 5, the port card number is 15.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-28 SDM maintenance procedures

Clearing MAP alarms triggered by the SDM

APPL SDM critical (continued)

7 Access the MS level of the MAP display by typing

>MS
and pressing the Enter key.

8 Access the shelf level by typing

>SHELF 0
and pressing the Enter key.

9 Access the MS port card level that is associated with the SDM DS512 links by
typing
>CARD cardno
and pressing the Enter key.
where
cardno is the MS card number noted in step 6.

10 Note the status of the MS port card and its ports. If port status indication is
P-side busy, then continue with step 11. Otherwise, use the generic MS alarm
clearing procedures provided with your DMS switching system to return the
ports to service, and then continue this procedure.

11 Access the SDM level of the MAP display by typing

>APPL;SDM
and pressing the Enter key.
Example response:
SDM 0 InSv Links_OOS: .
12 Determine the state of the SDM.

If the state of the SDM is Do

InSv step 72
SysB (NA) step 71
SysB step 68
SysB /The SDM is not responding step 15
ISTb step 13

13 Allow 2 min for SDM applications to re-establish communications with the CM

and return to service. When this is complete, the SDM state automatically
changes to InSv, unless another fault exists.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-29

Clearing MAP alarms triggered by the SDM

APPL SDM critical (continued)
Note: 2 min is an approximate time value. The actual time required for the
system to restart all applications varies depending on the number and type of
application software packages installed on your SDM.

If the SDM state is Do

InSv step 72
remains ISTb after 2 min step 14

14 Clear the ISTb state using the procedure ”Clearing MAP alarms triggered by the
SDM – APPL SDM minor” on page 4-3 of this document.
Go to step 72.

15 Access the EXT level of the MAP display by typing

>EXT
and pressing the Enter key.

16 List all major EXT alarms by typing

>LIST MAJ
and pressing the Enter key.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-30 SDM maintenance procedures

Clearing MAP alarms triggered by the SDM

APPL SDM critical (continued)

17 Determine if the SDM has triggered an FSP frame fail alarm for the equipment
aisle containing the SDM.

If an SDM-related FSP alarm is Do

present step 18
not present step 19

Note: An EXT FSP major alarm triggered by the SDM indicates that one or
both -48V dc power inputs to the SDM have failed, or that the SDM has shut
down because of thermal failure (overheating).

18 Clear the EXT FSP alarm using the procedure ”Clearing MAP alarms triggered
by the SDM – Ext FSP major” on page 4-44 in this document.
Go to step 72.

At the front of the SDM

19 Determine if the System in Service light is on (green).

SDM main chassis

SYSTEM
IN SERVICE

COMPONENT
OUT OF SERVICE

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-31

Clearing MAP alarms triggered by the SDM

APPL SDM critical (continued)
Note: If the System in Service light is off, but power is available to the system
and it has not shut down because of thermal failure (overheating), one or more
of the following conditions is present or has occurred:
• System software has crashed.
• The system is booting, or the attempt to boot has failed.
• The system cannot boot because the CPU or the I/O controller module
containing the root volume group (rootvg) is out of service.
• The system has been manually shut down.

If the System in Service light is Do

on step 45
off step 20

20 Determine from office records or other personnel if the SDM was manually shut
down.

If the system was Do

manually shut down step 21

not manually shut down step 22

21 When permissible, restart the SDM by continuing this procedure at step 24.

22 Ensure that the local console is connected to SP0 of the CPU personality
module using the designated cable. Ensure that the console is operational and
correctly configured for VT100 operation.

At the local VT100 console

23 Determine if the system is booting.

If the system is Do

booting step 25
not booting, or the boot has failed step 24

Wireless Networks Family SDM–SX User Guide SDMPL011

4-32 SDM maintenance procedures

Clearing MAP alarms triggered by the SDM

APPL SDM critical (continued)
At the front of the MSP
24 Cycle power to the SDM by turning the modular supervisory panel (MSP)
breakers off and on. The MSP breakers supply power to the SDM.

If your system contains Do

a main chassis only turn top two breakers off and

on

At the local VT100 console

25 Monitor the boot process at the local console.

If the boot Do

does not start step 26

starts but does not complete (returns to step 36
the FX-Bug prompt)
completes normally and the login prompt step 35
is displayed

At the front of the SDM

26 Physically verify that the CPU controller module (NTRX50FK, FL, or FM) is
present in the main chassis (slots 6 and 7)

If Do

the CPU controller modules is present step 31

a CPU controller module was removed or step 27
unseated in error

27
WARNING
Static electricity damage
Wear an ESD grounding wrist strap connected to the
C28B cabinet when handling a module. This protects
the module against damage caused by static electricity.

Reinsert the CPU controller module that was removed in error.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-33

Clearing MAP alarms triggered by the SDM

APPL SDM critical (continued)

At the local VT100 console

28 Determine whether the system has begun to boot.

If the system is Do

booting step 30
not booting, or the boot has failed step 29

At the front of the MSP

29 Cycle power to the SDM by turning the MSP breakers off and on. The MSP
breakers supply power to the SDM. Proceed according to the chassis in your
system.

If your system contains Do

a main chassis only turn top two breakers off and

on

At the local VT100 console

30 Monitor the boot process.

If the boot Do

does not start step 31

starts but does not complete (returns to step 36
the FX-Bug prompt)
completes normally and the login prompt step 35
is displayed

At the front of the SDM

31
WARNING
Static electricity damage
Wear an ESD grounding wrist strap connected to the
C28B cabinet when handling a module. This protects
the module against damage caused by static electricity.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-34 SDM maintenance procedures

Clearing MAP alarms triggered by the SDM

APPL SDM critical (continued)

32 Verify that the CPU controller module is seated correctly and passes self tests
by unseating, and then reseating it. Ensure that the CPU controller modules
are seated firmly and the latches are closed snugly. When a CPU controller
module is reseated and its latches closed, both LEDs on the CPU controller
module turn on solid for a brief period, indicating that the module is powered up,
fully seated, and has passed its self tests.

If Do

the CPU controller module fails its self step 33

tests
the CPU controller module pass its self step 34
tests

33 Replace the CPU that failed its self tests. Ensure that the replacement module
has the same product engineering code (PEC), including suffix, as the unit
being removed. The PEC is written on the top locking lever of the module.
(Refer to the appropriate procedure in the “SDM hardware replacement
procedures” chapter in this document.)
At the local VT100 console
34 Monitor the boot process.

If the boot Do

does not start step 71

starts but does not complete (returns to step 36
the FX-Bug prompt)
completes normally and the login prompt step 35
is displayed

At the MAP display

35 Determine the state of the SDM.

If the state of the SDM is Do

InSv step 72
SysB (NA) step 4
SysB step 68

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-35

Clearing MAP alarms triggered by the SDM

APPL SDM critical (continued)

If the state of the SDM is Do

SysB /The SDM is not responding step 45

ISTb step 13

At the front of the SDM

36 Physically verify that the I/O controller module, NTRX50GN that provides root
volume group (rootvg) storage for the system, is present in the main chassis
(slots 2 and 3). Determine if the I/O controller module was accidentally
unseated or removed.

If Do

the I/O controller module is present step 38

the I/O controller module was removed or step 37
unseated in error

37 Reinsert the I/O controller module that was removed in error.

Go to step 39.

38 Unseat and reseat both I/O controller modules in slots 2 and 3. Ensure that
they are seated firmly and that the latches are closed snugly.

At the front of the MSP

39 Cycle power to the SDM by turning the MSP breakers off and on. The MSP
breakers supply power to the SDM. If your system contains a main chassis
only, turn the top 2 breakers off and on.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-36 SDM maintenance procedures

Clearing MAP alarms triggered by the SDM

APPL SDM critical (continued)
At the local VT100 console
40 Monitor the boot process.

If the boot Do

does not start step 41

completes normally and the login prompt step 44
is displayed

41 Perform a system software reinstall using the procedure “Restoring the SDM –
Full restore from S-tape” on page 6-35 of this document. When you have
restored from the S-tape, and you have begun to reboot the system as
instructed by that procedure, return to this point.

42 Monitor the boot process.

If the boot Do

does not complete (returns the FX-Bug step 71

prompt)
completes normally and the login prompt step 43
is displayed

43 Complete the remainder of the procedure “Restoring the SDM – Full restore
from S-tape” on page 6-35 of this document and return to this point.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-37

Clearing MAP alarms triggered by the SDM

APPL SDM critical (continued)
At the MAP display
44 Determine the state of the SDM.

If the state of the SDM is Do

InSv step 72
SysB (NA) step 4
SysB step 68
SysB /The SDM is not responding step 45
ISTb step 13

At the local or remote VT100 console

45 Log in to the SDM as the root or maint user.

46 Access the top menu level of the remote maintenance interface (RMI) by typing
# sdmmtc
and pressing the Enter key.

47 Access the connectivity (Con) menu level of the RMI by typing

>CON
and pressing the Enter key.
Example response
SDM Node State: ISTb
CM Connectivity State: SysB

Heartbeat status: SysB

IP address synchronization: InSv

DS512 Link States:

I/O domain 0, port 0: Closed
I/O domain 0, port 1: Closed

48 Determine the DS512 link states.

If Do

all the links are failed step 59

any of the links are closed step 49

Wireless Networks Family SDM–SX User Guide SDMPL011

4-38 SDM maintenance procedures

Clearing MAP alarms triggered by the SDM

APPL SDM critical (continued)

49 Note the I/O domain number and port number of each closed link.

At the back of the SDM

50 Physically inspect the fiber link connections to the SDM DS512 personality
modules.

If the fiber links Do

require reconnecting or replacement step 51

appear undamaged and are correctly step 53
connected to the SDM

51
CAUTION
Transmit and receive cables
Do not mix the transmit and receive cables for each
domain. Ensure that you reconnect the cables to the
correct slots. Link 0 transmit and link 0 receive
connect to MS0. Link 1 transmit and link 1 receive
connect to MS1.

Reconnect or replace the fibers on the DS512 personality module by pressing

the fiber cable in, and turning it a 1/4 turn to the right.

At the local VT100 console

52 Monitor the link status at the connectivity menu level of the RMI.

If Do

any of the links are closed step 53

all two links are InSv step 72
one link is InSv and one link has failed step 59

Note: Allow 5 min for the SDM link status to update if one or more fibers were
reconnected or replaced.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-39

Clearing MAP alarms triggered by the SDM

APPL SDM critical (continued)
At the MAP display
53 Determine the MS hardware that provides the DS512 links to the SDM by
typing
>TRNSL
and pressing the Enter key.
Example response:
SDM 0 DOMAIN 0 PORT 0 (MS 0:15:0) SysB ,P MsgCnd:Closed
SDM 0 DOMAIN 0 PORT 1 (MS 1:15:0) OK MsgCnd:Open

54 Record the MS port card number associated with the system-busy DS512 links
identified in step 52.
Note: In the example response shown in step 53, the port card number is 15.

At the back of the SDM

55 Physically inspect the fiber link connections to the SDM DS512 personality
modules.

If the fiber links Do

require reconnecting or replacement step 56

appear undamaged and are correctly step 59
connected to the SDM

56
CAUTION
Transmit and receive cables
Do not mix the transmit and receive cables for each
domain. Ensure that you reconnect the cables to the
correct slots. Link 0 transmit and link 0 receive
connect to MS0. Link 1 transmit and link 1 receive
connect to MS1.

Reconnect or replace the fibers on the DS512 personality module(s) by

pressing the fiber cable in, and turning it a 1/4 turn to the right.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-40 SDM maintenance procedures

Clearing MAP alarms triggered by the SDM

APPL SDM critical (continued)
At the MAP display
57 Repeat the TRNSL command by typing
>TRNSL
and pressing the Enter key.
Example response:
SDM 0 DOMAIN 0 PORT 0 (MS 0:15:0) SysB ,P MsgCnd:Closed
SDM 0 DOMAIN 0 PORT 1 (MS 1:15:0) OK MsgCnd:Open

58 Determine the state of the DS512 links.

If Do

any of the links are still closed step 59

all two links are InSv step 72

Note: Allow 5 min for the SDM link status to update if one or more fibers were
reconnected or replaced.

At the local VT100 console

59 Access the hardware (Hw) menu level of the RMI by typing
>HW
and pressing the Enter key.

60 Check the status of the DS512 controller modules, indicated under the “512”
header.

If Do

the DS512 controller module is step 61

manual-busy (indicated by an M)
the DS512 controller modules have failed step 63
(indicated by an F)

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-41

Clearing MAP alarms triggered by the SDM

APPL SDM critical (continued)

61 Determine from office records or other personnel why one DS512 controller
modules is manually busy. When permissible, return the manual-busy DS512
controller module to service by typing
>RTS 0 512
and pressing the Enter key.
Example response:
Hardware RTS : Domain 0 Device 512 – Command initiated.
Please wait...
When the RTS command is finished, the “Please wait...” message, and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Response:
Hardware RTS : Domain 0 Device 512 – Command submitted.

62 Check the status of the DS512 controller modules, indicated under the “512”
header.

If Do

the DS512 controller module is in service step 72

(indicated by a dot)
the DS512 controller modules have failed step 63
(indicated by an F)

At the front of the SDM

63 Physically verify that the DS512 controller module (front slot 1) is present in the
main chassis. Determine if this module was accidentally unseated or removed.

If Do

the DS512 controller module is present step 67

the DS512 controller module was step 64
removed or unseated in error

Note: If both LEDs on the DS512 controller module are off, the module is not
seated correctly.

64 Reinsert the DS512 controller module that was removed or unseated in error.
Ensure that the module is seated firmly and that the latches are closed snugly.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-42 SDM maintenance procedures

Clearing MAP alarms triggered by the SDM

APPL SDM critical (continued)
At the local VT100 console
65 Return the DS512 controller module to service by typing
>RTS 0 512
and pressing the Enter key.

Example response:
Hardware RTS : Domain 0 Device 512 – Command initiated.
Please wait...
When the RTS command is finished, the “Please wait...” message, and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Response:
Hardware RTS : Domain 0 Device 512 – Command submitted.

66 Check the status of the DS512 controller modules, indicated under the “512”
header.

If Do

the DS512 controller module has failed step 67

(indicated by an F)
the DS512 controller module is in service step 72

At the front of the SDM

67 Replace one DS512 controller module using the appropriate procedure in the
“SDM hardware replacement procedures” chapter of this document.
Go to step 70.
Note: You can determine if a DS512 controller module is faulty by viewing the
component out-of-service LED and the system in service LED. If the module is
faulty, the component out-of-service LED is on (red), and the system in service
LED (green) is off.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-43

Clearing MAP alarms triggered by the SDM

APPLAPPL
SDMSDMcritical
critical
(continued)
(end)
At the MAP display
68 The SDM state SysB, with no additional qualifier (NA or / not responding)
indicates that the SDM is communicating successfully with the CM, but that all
SDM applications have failed. Manually busy the SDM by typing
>BSY
and pressing the Enter key.
Response:
SDM Bsy initiated.
SDM Bsy completed.

69 Return the SDM to service by typing

>RTS
and pressing the Enter key.
Response:
SDM RTS initiated.
SDM RTS completed.

70 Determine the state of the SDM.

If the state of the SDM is Do

InSv step 72
SysB (NA) step 71
SysB step 71
SysB /The SDM is not responding step 71
ISTb step 13

71 Contact Nortel for assistance.

72 You have completed this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-44 SDM maintenance procedures 4-44

Clearing MAP alarms triggered by the SDM

Ext FSP major

Application
CM MS IOD Net PM CCS Lns Trks Ext APPL
. . . . . . . . FSP .
M

Use this procedure to clear an EXT FSP major MAP alarm that has been
triggered by the SDM.

Note: The EXT alarm FSP is used to report fault conditions on frame
supervisory panels (FSP) and modular supervisory panels in various types of
cabinets in a DMS switching. This procedure assumes that you have
isolated the SDM as the cause of the FSP alarm. To clear an FSP alarm
generated by another cabinet or frame, or by equipment other than the SDM,
use the EXT FSP alarm clearing procedure in the generic alarm clearing
manual for your DMS switch.

Indication
At the MTC level of the MAP display, FSP preceded by a number appears
under the Ext header of the alarm banner and indicates an external FSP
major alarm.

Meaning
An EXT FSP alarm triggered by the SDM means that one of the following
faults has occurred:
• Input power to the SDM has failed.
• The SDM has shut down because it has reached its maximum allowable
operating temperature threshold.
• The SDM power supply has failed.

Impact
The SDM is out of service and no applications can run.

Action
The following flowchart is only a summary of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to clear
the alarm.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-45

Clearing MAP alarms triggered by the SDM

Ext FSP major (continued)
Summary of Clearing MAP alarms triggered by the SDM - Ext FSP major

Check MSP This flowchart summarizes the

breakers procedure.

Use the instructions in the

procedure that follows this
Breakers Restore power flowchart to perform the
Y 1 procedure.
tripped?

N
Power N Restore power
available? 1

Check SDM
550 logs

Ambient N Check fan Fan Contact next

Y
heat trays, and PM failure? level of support 2
source? logs
Y N
Remove heat Replace fan
source Check alarms
module(s)

Allow SDM to 2
Cycle power to
cool down 3 the SDM

3 2
Monitor boot
1 process End

Wireless Networks Family SDM–SX User Guide SDMPL011

4-46 SDM maintenance procedures

Clearing MAP alarms triggered by the SDM

Ext FSP major (continued)
Clearing MAP alarms triggered by the SDM - Ext FSP major
At the MSP
1 Check the modular supervisory panel (MSP) breakers that supply -48V dv
power to the SDM.

If the breakers have Do

tripped step 2
not tripped step 3

2 The breakers have tripped due to an over-current condition. Have qualified

maintenance personnel inspect the problem. If required, contact Nortel for
assistance. When power is restored, continue this procedure at step 17.
Note: The MSP frame fail LED is lit when a breaker has tripped.

3 Have qualified power maintenance personnel determine if power is available

from the MSP to the SDM.

If power to the SDM is Do

available step 5
not available step 4

4 Have qualified power maintenance personnel restore power. Contact Nortel for
assistance, if required. When power has been restored, continue this
procedure at step 17.

At the local VT100 console

5 The SDM has shut down due to thermal failure (overheating). Verify this by
checking for recent SDM-related SDM 550 logs. If the SDM shut down is due
to thermal failure, then two logs were generated. The first log was generated
when the SDM reached its thermal warning threshold (60° C or 140° F). The
second log was generated to indicate that shutdown will occur in 1 min because
its shutdown thermal threshold has been reached (80° C or 177° F)

At the C28B cabinet containing the SDM

6 Determine if an ambient heat source has caused the thermal shutdown.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-47

Clearing MAP alarms triggered by the SDM

Ext FSP major (continued)
Note: An ambient heat source may consist of an excessively high air
temperature in the vicinity of the SDM, excessive heat from an adjacent frame,
or a combination of these factors.

If Do

an ambient heat source is present step 14

the temperature in the vicinity of the SDM step 7
seems normal

At the front of the SDM

7 Verify that both fan trays are present, and fully seated in the main chassis.

At the local VT100 console

8 Check for recent SDM-related SDM 550 logs indicating failure of one or both
fan tray units.

If a fan failure log is Do

generated step 13
not generated step 9

9 Ensure that the local VT100 console is connected to the SDM with the
designated cable, and that the VT100 console is operational.

At the MSP
10 Cycle power to the SDM by turning both MSP breakers, located at the front of
the MSP, off and on. The MSP breakers supply power to the SDM. Proceed
according to the chassis in your system.

If your system contains Do

a main chassis only turn top two breakers off and

on

At the local VT100 console

11 The SDM begins to reboot. Monitor the boot process. When you see the
following prompt,
Self Test/Boots about to Begin... Press <BREAK> at any time to Abort ALL.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-48 SDM maintenance procedures

Clearing MAP alarms triggered by the SDM

Ext FSP major (continued)
press the Break key repeatedly to interrupt the boot process. The FX-Bug
prompt is then displayed.

At the front of the SDM

12 Check the operation of the three fans in each fan tray module by unseating the
fan module, physically verifying that the fan blades in each fan are rotating, and
then reseat the fan module.

If Do

all fans appear to be operational step 19

one or more fans is faulty step 13

13 Replace the faulty fan module(s), and then continue this procedure at step 16.

At the C28B cabinet containing the SDM

14 Remove or eliminate the heat source that caused the thermal shutdown..

15 Allow the SDM to cool to ensure it has returned below its thermal shutdown
warning threshold (60 degrees C or 140 degrees F).

At the MSP
16 Cycle power to the SDM by turning both MSP breakers, located at the front of
the MSP, off and on. The MSP breakers supply power to the SDM. Proceed
according to the chassis in your system.

If your system contains Do

a main chassis only turn top two breakers off and

on

At the SDM
17 When power is restored, the SDM automatically reboots and returns to service.
Monitor the system’s progress as follows:
• When the SDM has booted successfully, the System in Service LED turns
on solid (green), and the Component Out of Service LED is on (red).
• Immediately following the reboot, all module in service LEDs are off, and
out of service LEDs are on (red). As each module returns to service, its in
service LED turns on (green) and the out of service LED turns off.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-49

Clearing MAP alarms triggered by the SDM

Ext FSP
Ext major
FSP major
(continued)
(end)

• When the CPU controller modules have returned to service, they begin to
reintegrate. During this time (approximately 3 min), the System in Service
LED flashes.
• When the I/O controller modules have returned to service, they begin to
reintegrate and reestablish disk mirroring. During this time (10 to 30 min,
depending on the amount of data stored on the disks), the System in
Service LED flashes.
At the MAP display
18 When disk reintegration is complete, check the APPL alarm banner for
SDM-related alarms. Use the alarm clearing procedures in this document to
clear any faults.
Go to step 20.

19 Contact the personnel responsible for the next level of support.

20 You have completed this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-50 SDM maintenance procedures 4-50

Cleaning the SDM DAT drive

Application
Use this procedure to clean the digital audio tape (DAT) drive in an I/O
controller module.

To clean the DAT drive, use an appropriate DAT drive cleaning cartridge.
Nortel recommends the Maxell cleaning cartridge (part number HS–4/SL or
equivalent). Refer to the documentation that accompanies the cleaning
cartridge for additional information about its use, and the life expectancy of
the cleaning tape.

Nortel recommends that you clean the tape drive heads after the first 4 hours
of tape movement of a new cartridge, and then after each 25 hours of use.

A slowly flashing green LED may indicate that the tape is damaged or needs
replacing. If the LED continues to flash after you have cleaned the DAT
drive, then on replace the cleaning cartridge.

A solid green LED indicates that a tape is inserted with no errors. Slowly
flashing green and amber LEDs indicates that a prerecorded audio cartridge
is inserted and is being played automatically. A rapidly flashing green LED
indicates that the drive cannot write to the tape correctly. Clean the DAT
drive.

A solid amber LED indicates that the drive is reading or writing the tape. If
the amber light flashes rapidly, a hardware fault has occurred.

Note: A flashing LED does not affect operations, and does not indicate that
data has been lost.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-51

Cleaning the SDM DAT drive (continued)

Action
This procedure contains a summary flowchart as an overview of the
procedure. Follow the specific steps to perform this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-52 SDM maintenance procedures

Cleaning the SDM DAT drive (continued)

Summary of Cleaning the SDM DAT drive

This flowchart summarizes the

procedure.

Get cleaning Use the instructions in the

cartridge procedure that follows this
flowchart to perform the
procedure.

Eject tape from

tape drive

Insert cleaning
tape

Remove
cleaning tape
when complete

Reinsert
original tape if
applicable

End

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-53

Cleaning
Cleaning the SDM
the SDM DAT drive
DAT drive (end)
(continued)
Cleaning the SDM DAT drive
At the front of the SDM
1 Obtain a cleaning cartridge (Maxell part number HS–4/CL or equivalent).

2 Press the eject button on the DAT drive and remove the tape cartridge, if
applicable.

3 Insert the cleaning cartridge into the DAT drive.

Note: Cleaning begins automatically. When cleaning is complete, the cartridge
is automatically ejected.

4 Remove the cartridge from the DAT drive.

5 If applicable, re-insert the tape you removed in step 2.

6 You have completed this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-54 SDM maintenance procedures 4-54

Controlling SDM applications

Application
Use this procedure to shut down (manually busy) or restart (return to
service) SDM application software packages. The SDM must be in
in-service (InSv), in-service trouble (ISTb), or system busy (SysB) state to
perform this procedure.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-55

Controlling SDM applications (continued)

Summary of Controlling SDM applications

This flowchart summarizes the

procedure.
Log in to the
RMI
Use the instructions in the
procedure that follows this
flowchart to perform the
procedure.
Access the Mtc
menu level of
the RMI

Check SDM
node state

Access
application
level of RMI

Manually busy Y Manually busy End

an application? the application

Return the
application to
service

N Contact next End

Application in
level of support
service?

Y
End

Wireless Networks Family SDM–SX User Guide SDMPL011

4-56 SDM maintenance procedures

Controlling SDM applications (continued)

Controlling SDM applications
At the local or remote VT100 terminal
1 Log in to the RMI as the root user or the maint user.

2 Access the top menu level of the RMI by typing

# sdmmtc
and pressing the Enter key.

3 Access the maintenance (Mtc) menu level of the RMI by typing

>2
and pressing the Enter key.

4 Determine the SDM node state.

If the SDM node state is Do

InSv, ISTb, or SysB step 6

anything else step 5

5 The SDM must be in InSv, ISTb, or SysB state to change the state of an SDM
software package. Use the appropriate MAP alarm clearing procedure in this
document to return the SDM to service.
Go to step 4.

6 Access the application (Appl) menu level of the RMI by typing

>4
and pressing the Enter key.
Example response:
SDM Node State: ISTb
SDM Application State: ISTb

# Package Description Version State

1 Table Access Service 10.0.29.0 ISTb
2 Operation Measurements 10.0.29.0 ISTb
3 Log Delivery Service 10.0.29.0 InSv

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-57

Controlling SDM applications (continued)

7 Determine the application control activity you wish to perform.

If you want to Do

shut down (manually busy) an SDM step 8

application software package
restart (return to service) an SDM step 11
application software package

8 Manually busy the application software by typing

>BSY n
and pressing the Enter key.
where
n is the number under “#” of the application you wish to shut down
Response:
The application is in service.
This command will cause a service interruption.
Do you wish to proceed?
Please confirm (“YES”, “Y”, “NO”, or “N”):
Note: Busying the application as shown performs an orderly shutdown and can
take up to 2 min.

9 Confirm the Busy command by typing

>Y
and pressing the Enter key.

10 After you confirm the Bsy command, the following is displayed:

Response:
Application Bsy– Command initiated.
Please wait...
When the Bsy command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Response:
Application Bsy – Command submitted.
Go to step 14.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-58 SDM maintenance procedures

Controlling SDM applications (end)

(continued)

11 Return the application to service by typing

>RTS n
and pressing the Enter key.
where
n is the number of the application (from step 8)

Note: If the application is in the offline (OffL) state, it must be set to the
manual-busy state as described in step 8 before entering the Bsy command.
Response:
Application RTS - Command initiated.
Please wait...
When the RTS command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Response:
Application RTS – Command submitted.

12 Determine from the RMI display if the application returned to service

successfully. This is indicated by the state InSv.

If the application state is Do

InSv step 14
anything else step 13

13 Contact the personnel responsible for the next level of support.

14 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 4-59 SDM maintenance procedures 4-59

Adding I/O controller modules

Application
Use this procedure to add the following hardware modules to the SDM:
• NTRX50GP – I/O controller module with two 4-Gbyte disk drives and
Ethernet

To perform this procedure, you must know the following information:

• the chassis SDMM for main chassis
• the I/O controller module’s slot number (from 1 to 16)
• the I/O controller module’s product engineering code (PEC)

Note: I/O controller modules can be added to slots 4 and 5 of the SDM
main chassis.

Note: Each I/O controller module must also have an associated LAN
personality module (NTRX50FS) installed at the back of the SDM. Ethernet
LAN connectivity, however, is only supported by the mandatory
NTRX50GN I/O controller modules located in slots 2 and 3 of the main
chassis.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-60 SDM maintenance procedures

Adding I/O controller modules (continued)

Summary of Adding I/O controller modules

This flowchart summarizes the

Remove the
procedure.
filler face
plates
Use the instructions in the
procedure that follows this
flowchart to perform the
Insert the new
procedure.
I/O controller
modules

Insert the LAN

personality
modules

Log in to the
SDM as the
root user

Access the
hardware level
of the RMI

Add the I/O

controller
module

Monitor the
status of the
new modules

End

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-61

Adding I/O controller modules (continued)

Adding I/O controller modules
At the front of the SDM
1
WARNING
Static electricity damage
Wear an ESD grounding wrist strap connected to the
C28B cabinet when handling a module. This protects
the module against damage caused by static electricity.

2 Remove the filler plates covering the slots in which you will install the new
modules.
Note: I/O controller modules can be added to slots 4 and 5 of the SDM main
chassis.
Note: The rear LAN personality module (NTRX50FS) that is associated with
each NTRX50GP I/O controller module must occupy the lower number of the
two rear slots that are associated with the front module. For example, if the
new I/O controller module occupies front slots 4 and 5, its associated
NTRX50FS LAN personality module must be installed in rear slot 4. The
unused rear slots remain covered by filler plates.

3 Insert the replacement module into the SDM shelf.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-62 SDM maintenance procedures

Adding I/O controller modules (continued)

4 Gently slide the module into the shelf until it is fully inserted.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-63

Adding I/O controller modules (continued)

5 Close the locking lever to secure the module. Ensure that the top micro switch
is lined up with the locking lever to properly seat the module.

Micro switch

6 Tighten the thumbscrews on the module.

At the back of the SDM

7 Insert the new LAN personality module into the SDM shelf.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-64 SDM maintenance procedures

Adding I/O controller modules (continued)

8 Gently slide the LAN personality module into the shelf until it is fully inserted.

9 Tighten the thumbscrews at the top and the bottom of the LAN personality
module.
At the local or remote VT100 console
10 Log in to the SDM as the root user.

11 Access the top menu level of the remote maintenance interface (RMI) by typing
# sdmmtc
and pressing the Enter key.

12 Access the hardware (Hw) menu level by typing

>HW
and pressing the Enter key.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-65

Adding I/O controller modules (continued)

13 Add the logical pair of I/O controller modules by typing
>ADD chassis slot PEC
and pressing the Enter key.
where
chassis is the chassis where the module will be located (“SDMM” for main
chassis)
slot is the lower of the two physical slot numbers the module occupies

14 The ADD command may take several minutes to complete. When the
command is finished, the following message is displayed:
Response:
Hardware Add Module – Command submitted.

15 Monitor the status of the new hardware at the hardware (Hw) menu level of the
RMI. The screen does not initially show the new hardware that has been
added.
Example response
I F C E D 5
C A P T S 1
M N U H K 2

Domain 0 . . . . . .
Domain 1 . . - - - -
The system takes a few seconds to display the appropriate new hardware
elements (DSKn for hard disks). Previously installed disks on the system are
automatically renumbered, as required, to reflect the new hardware
configuration. The status of the new hardware elements may initially appear
on the RMI as “F” (failed).
Example response
I F C E D D D D 5
C A P T S S S A 1
M N U H K K K T 2
1 2 3
Domain 0 . . . . . F F . .
Domain 1 . . - - - - - - -

Wireless Networks Family SDM–SX User Guide SDMPL011

4-66 SDM maintenance procedures

Adding I/O controller modules (end)

(continued)
After a few seconds, the modules are automatically put in service, at which time
their status changes to in service (indicated by a dot).
Example response
I F C E D D D D 5
C A P T S S S A 1
M N U H K K K T 2
1 2 3
Domain 0 . . . . . . . . .
Domain 1 . . - - - - - - -
Note: Devices have been renumbered. Use the Locate command to verify slot
numbers.

16 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 4-67 SDM maintenance procedures 4-67

Removing I/O controller modules

Application
Use this procedure to delete the following hardware modules from the SDM:
• NTRX50GP – I/O controller module with two 4-GByte disk drives and
Ethernet

Note: This procedure can also be followed by the procedure ”Adding I/O
controller modules” on page 4-59 to change or correct the physical location.
The I/O controller modules (NTRX50GN) in slots 2 and 3 of the main
chassis are mandatory for system operation, and cannot be removed.

CAUTION
Re–using an I/O controller module
An I/O controller module must be manually busied and
deleted before it can be re–used in a different slot.

To perform this procedure, you must know the following information:

• the chassis SDMM for main chassis
• the I/O controller module’s slot number (from 1 to 16)
Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-68 SDM maintenance procedures

Removing I/O controller modules (continued)

Summary of Removing I/O controller modules

This flowchart summarizes the

Log in to the procedure.
SDM as the
root user Use the instructions in the
procedure that follows this
flowchart to perform the
Access the procedure.
hardware level
of the RMI

Manually busy
the I/O controller
modules

Delete the I/O

controller
modules

Remove the
I/O controller
modules

Remove the
LAN personality
module

Reinstall the
filler face
plates

End

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-69

Removing I/O controller modules (continued)

Removing I/O controller modules
At the local or remote VT100 console
1 Log in to the SDM as the root user.

2 Access the top menu level of the remote maintenance interface (RMI) by typing
# sdmmtc
and pressing the Enter key.

3 Access the hardware (Hw) menu level by typing

>HW
and pressing the Enter key.

4 Determine the devices on the I/O controller module by using the Locate
command. Use the Locate command by typing
>15
and pressing the Enter key.

5
CAUTION
Deleting an I/O controller module
Deleting an I/O controller module requires you to put
the module in both domains in ManB state. These
modules will not be in service.

Manually busy the module in each domain by typing

>BSY 0 DSKn
and pressing the Enter key.
where
n is the disk number that you are replacing (Use the Locate
command to determine the disk number of the module.)

Example response:
Hardware Bsy – Domain 0 Device DSK2
Busying DSK2(0) will also busy DSK3(0).

Do you wish to proceed?

Please confirm (“YES”, “Y”, “NO”, “N”):

6 Confirm the Bsy command by typing

>Y
and pressing the Enter key.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-70 SDM maintenance procedures

Removing I/O controller modules (continued)

7 After you confirm the Bsy command, the following is displayed:
Response:
Hardware Bsy – Command initiated.
Please wait...
When the Bsy command is finished, the “Please wait...” message, and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Response:
Hardware Bsy – Command submitted.
If you have not yet manually busied the module in both domains, go to step 5.
Otherwise, continue this procedure.
Note: After you see the response to the Bsy command, the I/O controller
module’s state changes to “M” at the hardware menu level of the RMI.

8 Use the Locate command to determine the chassis and slot number of the
module you wish to delete by typing
>15
and pressing the Enter key.
Example response:
Site Flr RPos Bay_id Shf Description Slot EQPEC
HOST 00 00 CSDM SDMM DSK2(0),DSK3(0) 04 NTRX50FU FRNT

Note: The example shown only displays part of the information generated from
the Locate command. Press the Enter key to scroll through the display.

9 Delete the module by typing

>DEL chassis slot
and pressing the Enter key.
where
chassis is the chassis where the module is located (SDMM for the main
chassis)
slot is the slot number (from 1 to 16) where the module is located
Note: In the example response shown in step 8, type DEL SDMM 4.
Example response
Module in slot 4 of SDMM will be deleted.
DSK2(0), DSK3(0) will be deleted.

Do you wish to proceed?

Please confirm (“YES”, “Y”, “NO”, “N”):

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-71

Removing I/O controller modules (continued)

10 If you are sure this is the module you wish to delete, type
>Y
and press the Enter key.

11 The DEL command may take several minutes to complete. When the
command is finished, the following message is displayed:
Response:
Hardware Del Module – Command submitted.

12 In a few seconds, the module disappears from the listing shown at the
hardware menu level of the RMI.
Note: The device numbers change on the screen display.

At the front of the SDM

13
WARNING
Static electricity damage
Wear an electrostatic discharge (ESD) grounding wrist
strap connected to the C28B cabinet when handling a
module. This protects the module against damage
caused by static electricity.

14 Undo the thumbscrews located on the top and the bottom of the I/O controller
module.
Note: The thumbscrews are the captive type, and cannot be removed from the
module.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-72 SDM maintenance procedures

Removing I/O controller modules (continued)

15 Depress the tip of the locking lever on the face of the I/O controller module.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-73

Removing I/O controller modules (continued)

16 Open the locking lever on the face of the module by moving the lever outwards.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-74 SDM maintenance procedures

Removing I/O controller modules (continued)

17 While grasping the locking lever, gently pull the module towards you until it
protrudes about 2 in (5.1 cm) from the SDM shelf.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-75

Removing I/O controller modules (continued)

18 Hold the module by the face plate with one hand while supporting the bottom
edge with the other hand. Gently pull the module toward you until it clears the
shelf.

19 Place the module you have removed in an ESD protective container.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-76 SDM maintenance procedures

Removing I/O controller modules (continued)

At the back of the SDM
20 Determine what kind of hardware module your SDM has.

If you have Do

NTRX50GN step 21
NTRX50GP step 22

21 Disconnect the 10BASE-T cable from the corresponding LAN personality

module, as shown in the following diagram.

22 Loosen the two thumbscrews located at the top and the bottom of the LAN
personality module.
Note: The thumbscrews are the captive type, and cannot be removed from the
module.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-77

Removing I/O controller modules (continued)

23 While grasping the thumbscrews, gently pull the LAN personality module
towards you until it protrudes about 2 in (5.1 cm) from the SDM shelf.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-78 SDM maintenance procedures

Removing I/O controller modules (end)

(continued)

24 Hold the LAN personality module by the face plate with one hand while
supporting the bottom edge with the other hand. Gently pull the module toward
you until it clears the shelf.

25 Place the LAN personality module you have removed in an ESD protective
container.

26 Reinstall the filler plates covering the slots in which you removed the modules.

27 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 4-79 SDM maintenance procedures 4-79

Establishing a modem connection

Application
Nortel recommends that you use the General DataComm (GDC)
maintenance modem provided with the SDM equipment whenever a console
dial-up modem connection to the SDM from a remote location is required.
The GDC maintenance modem is installed and configured as part of the
installation of the SDM.

Use the following procedure to establish a dial-up modem connection to the

SDM from a remote location.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-80 SDM maintenance procedures

Establishing a modem connection (continued)

Summary of Establishing a modem connection

This flowchart summarizes the

procedure.
Connect
modem to Use the instructions in the
console port procedure that follows this
flowchart to perform the
procedure.
Establish a
modem
connection

Modem Y End
connection?

N
Enter AT
commands

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-81

Establishing a modem connection (continued)

Establishing a modem connection
At the SDM
1 If necessary, connect the GDC maintenance modem to the SDM by first
ensuring no other terminal device cables are connected to console port SP0 on
the CPU personality module. Connect the NTRX5093 cable connected to the
GDC maintenance modem to port SP0, and ensure a phone line is connected
to the GDC maintenance modem.
Note: The modem is located in the appropriate MIS frame.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-82 SDM maintenance procedures

Establishing a modem connection (continued)

At a remote VT100 console
2 Use a terminal connected to a V.34 Hayes-compatible modem or other
appropriate communications equipment connected to a V.34 modem, to
establish remote connection to the SDM console port. Establish a modem
connection to the SDM by typing
>atdt dial_in_number
and pressing the Enter key.
where
dial_in_number is the telephone number for the modem attached to serial
port 1
Note: For information on establishing a modem-to-modem connection, refer to
the instructions for establishing a dial-up connection provided with the
communications equipment you are using.

3 Determine if the connection has been established.

If you Do

get a login prompt step 4

do not get a login prompt step 5

4 Log in at the prompt using your userID and password.

Go to step 15.

5 Execute the following steps to reconfigure your modem, starting at step 6. If

you have already executed these commands, and are still having problems,
contact the personnel responsible for your next level of support.

6 Reconfigure the GDC maintenance modem by connecting a VT100 console set

to communicate at 9600 baud directly to the DTE connector on the GDC
maintenance modem. Then enter the AT commands by first typing
>AT&F0
and pressing the Enter key.
Note: The command may or may not be echoed on the screen, depending on
the previous configuration.
Note: If you make a mistake when entering the AT commands, restart the
procedure at this point.

7 When the modem responds “OK”, type

>AT\T7
and press the Enter key.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-83

Establishing
Establishing a modem
a modem connection
connection (end)
(continued)

8 When the modem responds “OK”, type

>AT&R2
and press the Enter key.

9 When the modem responds “OK”, type

>AT&C1
and press the Enter key.

10 When the modem responds “OK”, type

>ATE0
and press the Enter key.

11 When the modem responds “OK”, type

>AT%K1
and press the Enter key.
Note: This command is not echoed on the screen.

12 When the modem responds “OK”, type

>ATQ1
and press the Enter key.
Note: The modem does not respond after you enter ATQ1. The command is
not echoed on the screen.

13 Type
>AT&W0
and press the Enter key.
Note: The modem does not respond after you enter AT&W0. The command is
not echoed on the screen.

14 Type
>AT&Y0
and press the Enter key.
Note: The modem does not respond after you enter AT&Y0. The command is
not echoed on the screen.
Go to step 2.

15 You have completed this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-84 SDM maintenance procedures 4-84

Log Delivery device commissioning

Application
Use this procedure to commission the Log Delivery service and to view and
modify Log Delivery parameters. The online SDM commissioning tool
called Logroute controls Log Delivery operating parameters.

The Logroute Device List menu specifies the output devices that receive
logs from Log Delivery, and the characteristics for each defined device. The
Device List menu displays any defined Log Delivery output devices. At
initial commissioning of the Log Delivery service, there are no output
devices displayed because they are not defined. Define all required output
devices at initial commissioning time. The Device List menu also allows
adding, deleting, and modifying of already defined devices.

The Device List menu provides access to the following device-specific

submenus:
• TCP Device—defines TCP/IP output links to OSSs. For each TCP
device, define the IP address of the OSS host machine, the port number
of the machine, the log format, and the logs that will be routed to the
OSS.
• TCP-IN Device—defines TCP/IP incoming links. For each TCP-IN
device, define the port number to be used on the SDM, the log format,
the remote address of the connecting OSS, and the logs that will be
routed to the OSS.
• File—defines SDM-resident UNIX output files. Define the filename and
log format for each UNIX file, and the logs that will be routed to the file.
A maximum of ten output devices (UNIX files and TCP/IP links) can be
commissioned. Any combination of UNIX files and TCP/IP links can make
up the ten commissioned output devices.

Note: To have commissioning changes take effect after you save the
changes, busy and return the Log Delivery application to service. The Log
Delivery application is not available for a short time during the busy and
return-to-service process.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-85

Log Delivery device commissioning (continued)

Summary of Log Delivery device commissioning

This flowchart summarizes the

Log in to the procedure.
SDM as a
maint user Use the instructions in the
procedure that follows this
flowchart to perform the
Access procedure.
Logroute

Y Add a device
Add a device? 1

N
Route logs Y Route logs to a
to a device 1
device

N
Change a Y Change a
device? device 1

N
Delete a Y Delete a
device? device 1

Save Y BSY and RTS

Add a device?
changes? Log Delivery
application
N

End

Wireless Networks Family SDM–SX User Guide SDMPL011

4-86 SDM maintenance procedures

Log Delivery device commissioning (continued)

Commissioning LAN connectivity
At the local or remote VT100 console
1 Log in to the RMI of the SDM as a maint user.

2 Access the Logroute commissioning tool by typing

>logroute
and pressing the Enter key.
Response:
Logroute Main Menu

1 – Device List
2 – Global Parameters
3 – CM Configuration File

c:change menu, q:quit, h:help, s:save changes

Warning: You must save, then BSY and RTS the Log Delivery
======= application for any changes to take effect.

Enter command ==>

Note: For help on Logroute commands, type h. To scroll down the help menu,
type f. To scroll back through the help menu, type b. To quit the help menu,
type p. To quit out of the Logroute tool, type q at the Logroute Main Menu.

3 Select change by typing

>c
and pressing the Enter key.
Response:
Enter number of main menu option:

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-87

Log Delivery device commissioning (continued)

4 Enter the option number for Device List by typing
>1
and pressing the Enter key.
Note: The following response shows an example where one output device
(TCP/IP 47.208.7.54) has already been commissioned.

Response:
Device List

Devices: Type:
1 – HOST: 47.208.7.54 PORT: 1200 TCP

c:change device, a:add device, d:delete device, q:quit, h:help, m:main

Enter command ==>

5 Proceed according to whether you are adding a device, routing logs to a

device, deleting a device or changing a device.

If you are Do

adding a device step 6

routing logs to a device (new or changed step 37
routing)
changing a device step 54
deleting a device step 51

Note: The changing a device option only allows you to change the device
parameters (HOST IP, PORT, FILENAME, or FORMAT) and not the device’s
log routing.

6 Add a device by typing

>a
and pressing the Enter key.

Response:
Enter device type (t – TCP, i – TCPIN, F – file) ==>

Wireless Networks Family SDM–SX User Guide SDMPL011

4-88 SDM maintenance procedures

Log Delivery device commissioning (continued)

7 Enter the device type by typing
>device type
and pressing the Enter key.
where
devicetype is the device type. t defines TCP/IP output
links to OSSs. i defines an in-bound TCP/IP
connection. f defines SDM-resident UNIX output files.

Note: The following response shows an example for a TCP device type.

Response:
TCP Device

Device Parameters 1 – HOST IP :

2 – PORT :
3 – FORMAT :STD

Log Routing

c:change parameter, a:add log routing, d:delete log routing

f: forward, b:back, q:quit, h:help, p:previous menu, m:main

Enter command ==>

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-89

Log Delivery device commissioning (continued)

8 Proceed according to what kind of device you are adding.

If you are adding a Do

TCP step 9
TCP-IN device step19
File device step 30

9 Select the change option, by typing

>c
and pressing the Enter key.
Response:
Enter number of device parameter to change ==>

10 Select the HOST IP option (to define the new device’s IP address), by typing
>1
and pressing the Enter key.
Response:
Enter host IP address (###.###.###.###) ==>

11 Enter the HOST IP address by typing

>HOST IP
and pressing the Enter key.
where
HOST IP is the IP address of the OSS host machine.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-90 SDM maintenance procedures

Log Delivery device commissioning (continued)

12 Select the change option again by typing

>c
and pressing the Enter key.
Response:
Enter number of device parameter to change ==>

13 Select the PORT option (to define the SDM port number the device will use), by
typing
>2
and pressing the Enter key.
Response:
Enter port number (range – 1024 to 32767) ==>

14 Enter the port number by typing

>PORT NUMBER
and pressing the Enter key.

where
PORT NUMBER is the port number of the OSS host machine. Nortel
recommends that if you are runnning the Log
Receiver tool with the Log Delivery device, you enter
a value between 5001 and 32 767.
Note: STD is the default value for the log format. If you do not want to change
the default value for the log format, go to step 18.

15 Select the change option by typing

>c
and pressing the Enter key.
Response:
Enter number of device parameter to change ==>

16 Select the FORMAT option (to define the format of logs sent to the new
device), by typing
>3
and pressing the Enter key.
Response:
Enter format type (STD or SCC2) ==>

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-91

Log Delivery device commissioning (continued)

17 Enter the FORMAT by typing

>FORMAT
and pressing the Enter key.

where
FORMAT is the log format.

18 Proceed according to your requirements for further device work.

If you Do

want to add log routing to this device step 40

want to work on another device step 5
do not want to do any more device work step 61

19 Select the change option by typing

>c
and pressing the Enter key.
Response:
Enter number of device parameter to change ==>

20 Select the PORT option to define the port on the SDM of the new device by
typing
>1
and pressing the Enter key.
Response:
Enter port number (range - 8550 to 8559) ==>

Wireless Networks Family SDM–SX User Guide SDMPL011

4-92 SDM maintenance procedures

Log Delivery device commissioning (continued)

21 Enter the PORT number by typing

>PORT NUMBER
and pressing the Enter key.
where:
PORT NUMBER is the port on the SDM to which the remote OSS
connects. Enter a value between 8550 and 8559.
Response:
TCP-IN DEVICE

Device Parameters
1 – PORT : 8558
2 – FORMAT : STD
3 – REMOTE ADDRESS : any
Log Routing

c:change change parameter, a:add log routing, d:delete log routing

f:forward, b:back, q:quit, h:help, p:previous menu, m:main menu

Enter command ==>

22 Select the change option by typing

>c
and pressing the Enter key.
Response:
Enter number of device parameter to change ==>

23 Select the Format option to define the format of the logs sent to the new device
by typing
>2
and pressing the Enter key.
Response:
Enter format type (STD or SCC2) ==>

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-93

Log Delivery device commissioning (continued)

24 Enter the FORMAT by typing

>FORMAT
and pressing the Enter key.

where
FORMAT is the log format.

Response:
TCP-IN DEVICE

Device Parameters
1 – PORT : 8558
2 – FORMAT : SCC2
3 – REMOTE ADDRESS : any
Log Routing

c:change change parameter, a:add log routing, d:delete log routing

f:forward, b:back, q:quit, h:help, p:previous menu, m:main menu

Enter command ==>

25 Proceed according to your requirements for your TCP-IN device.

If you Do

want to specify a REMOTE ADDRESS step 26

want to add log routing to this device step 42
do not want to do any more device work step 61
want to work on another device step 5

26 Select the change option by typing

>c
and pressing the Enter key.
Response:
Enter number of device parameter to change ==>

27 Select the REMOTE ADDRESS option to specify the IP address of the remote
OSS by typing
>3
and pressing the Enter key.
Response:
Enter host IP address (###.###.###.###) or a for any ==>

Wireless Networks Family SDM–SX User Guide SDMPL011

4-94 SDM maintenance procedures

Log Delivery device commissioning (continued)

28 Enter the REMOTE ADDRESS by typing

>REMOTE ADDRESS
and pressing the Enter key.

where
REMOTE ADDRESS is the IP address of the OSS host machine or a for
any host. If the REMOTE ADDRESS parameter is
set to ”any”, the device accepts a connection from
any IP address. Otherwise, the device only accepts
a connection from a specified address.

Response:
TCP-IN DEVICE

Device Parameters
1 – PORT : 8558
2 – FORMAT : SCC2
3 – REMOTE ADDRESS : 47.208.12.237
Log Routing

c:change change parameter, a:add log routing, d:delete log routing

f:forward, b:back, q:quit, h:help, p:previous menu, m:main menu

Enter command ==>

If you Do

want to add log routing to this device step 42

do not want to do any more device work step 61
want to work on another device step 5

29 Select the change option again by typing

>c
and pressing the Enter key.
Response:
Enter number of device parameter to change ==>

30 Access the change option to define the filename of the SDM-resident UNIX
output files by typing
>c
and pressing the Enter key.
Response:
Enter number of device parameter to change ==>

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-95

Log Delivery device commissioning (continued)

31 Select the option FILENAME (to define the file’s UNIX name), by typing
>1
and pressing the Enter key.
Response:
Enter file name ==> /data/logs/

32 Enter the file name by typing

>FILENAME
and pressing the Enter key.
where
FILENAME is the name of the UNIX file.
Response:
File

Device Parameters 1 – FILENAME :/data/logs/logs

2 – FORMAT :STD

Log Routing

c:change parameter, a:add log routing, d:delete log routing

f: forward, b:back, q:quit, h:help, p:previous menu, m:main

Enter command ==>

Note: STD is the default value for the log format. If you do not want to change
the default value for the log format, go to step 36.

33 Select the change option by typing

>c
and pressing the Enter key.
Response:
Enter number of device parameter to change ==>

34 Select the option FORMAT (to define the log format), by typing
>2
and pressing the Enter key.
Response:
Enter format (STD or SCC2) ==>

Wireless Networks Family SDM–SX User Guide SDMPL011

4-96 SDM maintenance procedures

Log Delivery device commissioning (continued)

35 Enter the format by typing

>FORMAT
and pressing the Enter key.
where
FORMAT is the log format. STD is the default value.
Response:
File

Device Parameters 1 – FILENAME :/data/logs/LOGS

2 – FORMAT :STD

Log Routing

c:change parameter, a:add log routing, d:delete log routing

f: forward, b:back, q:quit, h:help, p:previous menu, m:main

Enter command ==>

36 Proceed according to your requirements for further device work.

If you Do

want to add log routing to this device step 40

want to work on another file device step 5
do not want to do any more device work step 61

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-97

Log Delivery device commissioning (continued)

37 Select the change option by typing

>c
and pressing the Enter key.

Response:
Device List

Devices: Type:
1 – HOST: 99.99.99.99 PORT: 9999 TCP
2 – HOST: 47.208.165.54 PORT 1002 TCP
3 – /data/logs/logs

c:change device, a:add device, d:delete device, q:quit, h:help, m:main

Enter number of device to change ==>

38 Enter the number of the device by typing

>n
and pressing the Enter key.
where
n is the number of the device you want to change.
Response:

c:change parameter, a:log routing, d:delete log routing, f:forward,

b:back, q:quit, h:help, p:previous menu, m:main

Enter command ==>

39 Proceed according to whether you are adding or deleting log routing.

If you Do

want to add log routing step 40

want to delete log routing step 48

Wireless Networks Family SDM–SX User Guide SDMPL011

4-98 SDM maintenance procedures

Log Delivery device commissioning (continued)

40 Select the add log routing option by typing

>a
and pressing the Enter key.
Response:
Enter – a: addrep or d: delrep ==>

41 Decide if you want the new routing entry to add log(s) to the currently-defined
stream (addrep) or delete log(s) from the currently-defined stream (delrep).

If you Do

want to add log(s) step 42

want to delete log(s) step 45

42 Use the addrep command by typing

>a
and pressing the Enter key.

Response:
Enter log identifier (”log_type” or ”log_type log_number”) ==>

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-99

Log Delivery device commissioning (continued)

43 Enter the log identifier by typing

>log identifier
and pressing the Enter key.
where
log identifier is the log type, or log type and log number.
Note: If both the log name and log number are entered, the log name and
number must be separated by a space.

Response:
File

Device Parameters: :
1 – FILENAME :/data/logs/logs
2 – FORMAT :SCC2

Log Routing 3 – ADDREP PM 100

c:change parameter, a:add log routing, d:delete log routing,

f: forward, b:back, q:quit, h:help, p:previous menu, m:main

Enter command ==>

44 Proceed according to your requirements for further device work.

If you Do

want to do more log routing on this step 39

device
want to work on another device step 5
do not want to do any more device work step 61

45 Use the delrep command by typing

>d
and pressing the Enter key.

Response:
Enter log identifier (”log_type” or ”log_type log_number”) ==>

Wireless Networks Family SDM–SX User Guide SDMPL011

4-100 SDM maintenance procedures

Log Delivery device commissioning (continued)

46 Enter the log identifier by typing

>log identifier
and pressing the Enter key.
where
log identifier is the log type or log type number.
Note: If both the log name and log number are entered, the log name and
number must be separated by a space.

Response:
File

Device Parameters: :
1 – FILENAME :/data/logs/logs
2 – FORMAT :SCC2

Log Routing 3 – ADDREP PM 100

4 – DELREP PM 103

c:change parameter, a:add log routing, d:delete log routing,

f: forward, b:back, q:quit, h:help, p:previous menu, m:main

Enter command ==>

47 Proceed according to your requirements for further device work.

If you Do

want to do more log routing on this step 39

device
want to work on another device step 5
do not want to do any more device work step 61

48 Delete log routing by typing

>d
and pressing the Enter key.

Response:
Enter log routing number to delete ==>

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-101

Log Delivery device commissioning (continued)

49 Enter the number of the log routing from the File Menu by typing
>n
and pressing the Enter key.
where
n is the number of the log routing you want to delete.
50 Proceed according to your requirements for further device work.

If you Do

want to do more log routing on this step 39

device
want to work on another device step 5
do not want to do any more device work step 61

51 Delete a device by typing

>d
and pressing the Enter key.

Response:
Enter device number to delete ==>

52 Enter the device number by typing

>device number
and pressing the Enter key.
where
device number is the menu number of the device you want to delete.

53 Proceed according to your requirements for further device work.

If you Do

want to work on another device step 5

do not want to do any more device work step 61

Wireless Networks Family SDM–SX User Guide SDMPL011

4-102 SDM maintenance procedures

Log Delivery device commissioning (continued)

54 Select the change device option by typing

>c
and pressing the Enter key.

Response:
Enter number of device to change ==>

55 Enter the menu number of the device you want to change by typing
>#
and pressing the Enter key.
where
# is the menu number of the device you want to change.
Response:
TCP Device

Device Parameters 1 – HOST IP :47.208.7.54

2 – PORT :1212
3 – FORMAT :STD

Log Routing

c:change parameter, a:add log routing, d:delete log routing

f: forward, b:back, q:quit, h:help, p:previous menu, m:main

Enter command ==>

56 Select the change parameter option by typing

>c
and pressing the Enter key.

Response:
Enter number of device parameter to change ==>

57 Enter the menu number of the parameter you want to change

>#
and pressing the Enter key.
where
# is the menu number of the parameter you want to change.
Note: For a TCP or TCPIN device, the parameters are HOST IP, PORT, and
FORMAT. For a File device, the parameters are FILE and FORMAT.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-103

Log Delivery device commissioning (continued)

58 Enter the new value and press the Enter key.

59 Return to step 56 and repeat until you change every parameter you want to
change.

60 Proceed according to your requirements for further device work.

If you Do

want to work on another device step 5

do not want to do any more device work step 61

61 Return to the Logroute Main Menu by typing

>m
and pressing the Enter key.

62 Determine if you want to save any values you entered.

If you Do

want to save the changes step 63

do not want to save the changes step 77

63 Save the values you entered by typing

>s
and pressing the Enter key.

Response:
Logroute Main Menu

1 – Device List
2 – Global Parameters
3 – CM Configuration File

c:change menu, q:quit, h:help, s:save changes

Warning: You must save, then BSY and RTS the Log Delivery
======= application for any changes to take effect.

Save completed –– press return to continue

Wireless Networks Family SDM–SX User Guide SDMPL011

4-104 SDM maintenance procedures

Log Delivery device commissioning (continued)

64 Press enter key and quit the Logroute tool by typing

>q
and pressing the Enter key.
Response:
NOTE: Configuration data has changed
BSY and RTS the Log Delivery application
for changes to take effect.

maint:

65 Log out from the SDM by typing

>exit
and pressing the Enter key.

66 Determine if you want to activate the values you saved.

If you Do

want to activate the values step 67

do not want to activate the values step 80

67 Log in to the SDM as the root user.

68 Access the top menu level of the RMI by typing

#sdmmtc
and pressing the Enter key.

69 Access the maintenance (MTC) menu level of the RMI by typing

>MTC
and pressing the Enter key.

70 Access the application (APPL) menu level of the RMI by typing

>APPL
and pressing the Enter key.
Example response:
# Package Description Version State
1 Table Access Service 10.0.29.0 InSv
2 OM Access Service 10.0.29.0 InSv
3 Log Delivery Service 10.0.29.0 InSv

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-105

Log Delivery device commissioning (continued)

71 Determine the number for the Log Delivery Service (shown under the header
“#”).

72 Manually busy the Log Delivery Service by typing

>BSY n
and pressing the Enter key.
where
n is the number under “#” of the Log Delivery Service from step 71.
Response:
The application is in service.
This command will cause a service interruption.
Do you wish to proceed?
Please confirm (“YES”, “Y”, “NO”, or “N”):
Note: Busying the Log Delivery Service performs an orderly shutdown and can
take up to 2 min.

73 Confirm the Busy command by typing

>Y
and pressing the Enter key.

74 After you confirm the Bsy command, the following is displayed:

Response:
Application Bsy– Command initiated.
Please wait...
When the Bsy command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Response:
Application Bsy – Command submitted.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-106 SDM maintenance procedures

Log Delivery device commissioning (end)

(continued)

75 Return the application to service by typing

>RTS n
and pressing the Enter key.
where
n is the number of the application (from step 71 )

Response:
Application RTS - Command initiated.
Please wait...
When the RTS command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Response:
Application RTS – Command submitted.

76 Quit the RMI by typing

>QUIT ALL
and pressing the Enter key.
Go to step 80.

77 Quit out of the Logroute tool without saving any of the values you have entered,
by typing
>q
and pressing the Enter key.

Response:
Parameters have changed, do you want to save changes (y/n)?

Note: If you did not enter any changes, this message will not appear. Go to
step 80.

78 Indicate that you do not want to save your changes by typing

>n
and pressing the Enter key.

79 Log out from the SDM by typing

>exit
and pressing the Enter key.

80 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 4-107 SDM maintenance procedures 4-107

Log Delivery global parameters commissioning

Application
Use this procedure to commission the Log Delivery global parameters. The
online Log Delivery commissioning tool called Logroute controls Log
Delivery global parameters. The Log Delivery global parameters apply to
all Log Delivery output devices and are separate from device-specific
parameters.

The Logroute tool allows customization of the following global parameters:

• buffer size (number of logs)
• reconnect timeout value (secs)
• lost logs threshold (number of lost logs before the system generates a
design log) Note: This parameter is for Nortel personnel only.
• ASCII line delimiter and log delimiter characters
• the number of days to keep log files

The global parameters are set to default values at initial installation and
should not require modification. If the global parameters do require
modification, the ranges and default for each numeric parameter are as
follows:
• buffer size (number of logs): range is 50 to 300, default is 150
• reconnect timeout value (secs): range is 1 to 3600, default is 15
• lost logs threshold: range is 1 to 300, default is 100 (–1 turns this option
off)
• number of days to keep log files: range is 1 to 45, default is 5

The remaining global parameters are represented by ASCII character codes.

For more information on these parameters including their ranges, see the
Logroute help menu. The values for the global parameters represented by
ASCII character codes are as follows:
• incoming end of line character: default is 10 which corresponds to a
line-feed character (go to the next line)
• outgoing end of line characters: default is 10 13 which represents a line
feed (go to the next line) followed by a carriage return
• start of log characters: default is 10 13 which represents a line feed (go
to the next line) followed by a carriage return
• end of logs characters: default is 10 13 which represents a line feed (go
to the next line) followed by a carriage return

Wireless Networks Family SDM–SX User Guide SDMPL011

4-108 SDM maintenance procedures

Log Delivery global parameters commissioning (continued)

Note: To have any commissioning changes take effect after you save the
changes, busy and return the Log Delivery application to service. The Log
Delivery application is not available for a short time during the busy and
return-to-service process.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-109

Log Delivery global parameters commissioning (continued)

Summary of Log Delivery global parameters commissioning

This flowchart summarizes the

procedure.

Use the instructions in the

Log in to the procedure that follows this
SDM as a flowchart to perform the
maint user procedure.

Access
Logroute

Change Y
parame- Change the 1
ters? parameters

Activating Y Log in to the

changes? SDM as a root
user
N
2
BSY and RTS
Log Delivery
application

N
2

End

Wireless Networks Family SDM–SX User Guide SDMPL011

4-110 SDM maintenance procedures

Log Delivery global parameters commissioning (continued)

Commissioning LAN connectivity
At the local or remote VT100 console
1 Log in to the RMI of the SDM as a maint user.

2 Access the Logroute commissioning tool by typing

#logroute
and pressing the Enter key.
Response:
Logroute Main Menu

1 – Device List
2 – Global Parameters
3 – CM Configuration File

c:change menu, q:quit, h:help, s:save changes

Warning: You must save, then BSY and RTS the Log Delivery
======= application for any changes to take effect.

Enter command ==>

Note: For help on Logroute commands, type h. To scroll down the help menu,
type f. To scroll back through the help menu, type b. To quit the help menu,
type p. To quit out of the Logroute tool, type q at the Logroute Main Menu.

3 Select change by typing

>c
and pressing the Enter key.
Response:
Enter number of main menu option:

4 Enter the option number for Global Parameters by typing

>2
and pressing the Enter key.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-111

Log Delivery global parameters commissioning (continued)

Response:
Global Parameters

1 – Buffer size (number of logs) : 150

2 – Reconnect timeout value (secs) : 15
3 – Lost logs threshold (NT only) : 100
4 – Incoming end of line character : 10
5 – Outgoing end of line characters : 10 13
6 – Start of log characters : 10 13
7 – End of logs characters : 10 13
8 – Number of days to keep log files : 5

c:change item, q:quit, h:help, m:main

Enter command ==>

Note: This display shows the default values for the Global Parameters menu.

5 Select the change item option by typing

>c
and pressing the Enter key.

Response:
Enter number of global parameter to change ==>

6 Enter the menu number of the parameter you want to change by typing
>#
and pressing the Enter key.
where
# is the menu number of the global parameter you want to change.
Note: The following display shows an example response for changing the
buffer size parameter.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-112 SDM maintenance procedures

Log Delivery global parameters commissioning (continued)

Response:
Global Parameters

1 – Buffer size (number of logs) : 150

2 – Reconnect timeout value (secs) : 15
3 – Lost logs threshold (NT only) : 100
4 – Incoming end of line character : 10
5 – Outgoing end of line characters : 10 13
6 – Start of log characters : 10 13
7 – End of logs characters : 10 13
8 – Number of days to keep log files : 5

c:change item, q:quit, h:help, m:main

Enter buffer size (range – 50 To 300) ==>

Note: The log and line delimiters (incoming and outgoing end of line
characters, and start and end of log characters) must be entered as decimal or
hexadecimal ASCII code. See the Help menu for details.

7 Enter a value. The changed value appears on the Global Parameter menu.

8 Determine if you want to change any other Global Parameters.

If you are Do

changing another parameter step 5

not changing another parameter step 9

9 Return to the Logroute Main Menu by typing

>m
and pressing the Enter key.

10 Determine if you want to save your changes.

If you are Do

saving your changes step 11

not saving your changes step 25

11 Save the values you entered by typing

>s
and pressing the Enter key.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-113

Log Delivery global parameters commissioning (continued)

Response:
Logroute Main Menu

1 – Device List
2 – Global Parameters
3 – CM Configuration File

c:change menu, q:quit, h:help, s:save changes

Warning: You must save, then BSY and RTS the Log Delivery
======= application for any changes to take effect.

Save completed –– press return to continue

12 Press the enter key and quit the Logroute tool by typing
>q
and pressing the Enter key.
Response:
NOTE: Configuration data has changed
BSY and RTS the Log Delivery application
for changes to take effect.

maint:

13 Log out from the SDM by typing

>exit
and pressing the Enter key.

14 Determine if you want to activate the values you saved.

If you Do

want to activate the values step 15

do not want to activate the values step 28

Note: Saved changes to the global parameters will not take effect unless you
proceed to step 15.

15 Log in to the SDM as the root user.

16 Access the top menu level of the RMI by typing

#sdmmtc
and pressing the Enter key.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-114 SDM maintenance procedures

Log Delivery global parameters commissioning (continued)

17 Access the maintenance (MTC) menu level of the RMI by typing
>MTC
and pressing the Enter key.

18 Access the application (APPL) menu level of the RMI by typing

>APPL
and pressing the Enter key.
Example response:
# Package Description Version State
1 Table Access Service 10.0.29.0 InSv
2 OM Access Service 10.0.29.0 InSv
3 Log Delivery Service 10.0.29.0 InSv

19 Determine the number for the Log Delivery Service (shown under the header
“#”).

20 Manually busy the application software by typing

>BSY n
and pressing the Enter key.
where
n is the number under “#” of the Log Delivery Service
Response:
The application is in service.
This command will cause a service interruption.
Do you wish to proceed?
Please confirm (“YES”, “Y”, “NO”, or “N”):
Note: Busying the Log Delivery Service performs an orderly shutdown and can
take up to 2 min.

21 Confirm the Busy command by typing

>Y
and pressing the Enter key.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-115

Log Delivery global parameters commissioning (continued)

22 After you confirm the Bsy command, the following is displayed:
Response:
Application Bsy– Command initiated.
Please wait...
When the Bsy command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Response:
Application Bsy – Command submitted.

23 Return the Log Delivery Service to service by typing

>RTS n
and pressing the Enter key.
where
n is the number of the Log Delivery Service (from step 18 )

Response:
Application RTS - Command initiated.
Please wait...
When the RTS command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”. Go to step 28.
Response:
Application RTS – Command submitted.

24 Press enter key and quit the RMI by typing

>QUIT ALL
and pressing the Enter key.
Go to step 27.

25 Quit out of the Logroute tool without saving any of the values you have entered,
by typing
>q
and pressing the Enter key.

Response:
Parameters have changed, do you want to save changes (y/n)?

Note: If you did not enter any changes, the message above will not appear. Go
to step 27.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-116 SDM maintenance procedures

Log Delivery global parameters commissioning (end)

(continued)

26 Indicate that you do not want to save your changes by typing

>n
and pressing the Enter key.

27 Log out from the SDM by typing

>exit
and pressing the Enter key.

28 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 4-117 SDM maintenance procedures 4-117

Log Delivery CM configuration file commissioning

Application
Use this procedure to commission the Log Delivery computing module
(CM) configuration file parameters. When the Log Delivery service is first
installed, it receives all logs in the CM log stream by default. The CM
configuration file parameters do not require change unless you wish to
modify the incoming global log stream. Use the CM configuration file
menu in the Logroute commissioning tool to add or delete log reports to or
from the incoming CM log stream.

Note: To have any commissioning changes take effect after you save the
changes, busy and return the Log Delivery application to service. The Log
Delivery application is not available for a short time during the busy and
return-to-service process.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-118 SDM maintenance procedures

Log Delivery CM configuration file commissioning (continued)

Summary of Log Delivery CM configuration file commissioning

Log in to the This flowchart summarizes the

SDM as a procedure.
maint user
Use the instructions in the
procedure that follows this
Access flowchart to perform the
Logroute procedure.

Add an Y
item? Add an item 1

Y
Delete an Delete an item
item? 1

Activate Y Log in to the

changes? SDM as a root
user

2 N
BSY and RTS
Log Delivery
application

End

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-119

Log Delivery CM configuration file commissioning (continued)

Commissioning LAN connectivity
At the local or remote VT100 console
1 Log in to the RMI of the SDM as a maint user.

2 Access the logroute commissioning tool by typing

>logroute
and pressing the Enter key.
Response:
Logroute Main Menu

1 – Device List
2 – Global Parameters
3 – CM Configuration File

c:change menu, q:quit, h:help, s:save changes

Warning: You must save, then BSY and RTS the Log Delivery
======= application for any changes to take effect.

Enter command ==>

Note: For help on Logroute commands, type h. To scroll down the help menu,
type f. To scroll back through the help menu, type b. To quit the help menu,
type p. To quit out of the Logroute tool, type q at the Logroute Main Menu.

3 Select change by typing

>c
and pressing the Enter key.
Response:
Enter number of main menu option:

4 Enter the option number for CM Configuration File by typing

>3
and pressing the Enter key.
Note: The following display shows an example response where one log report
(CM 100) has been deleted from the incoming CM log stream.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-120 SDM maintenance procedures

Log Delivery CM configuration file commissioning (continued)

Response:
CM Config File

1 – DEL CM 100

f:forward, b:back a:add item, d: delete item

q:quit, h:help, m:main menu

Enter command ==>

5 Determine how you want to change the CM Config File.

If you want to Do

add an item to the list step 6

delete an item from the list step 10
return to the main menu step 13

6 Enter the menu option for adding an item by typing

>a
and pressing the Enter key.

Response:
Enter – a: addrep or d: delrep (or n for NOCMLOGS) ==>

7 Determine if you want the new list item to be a log addition or a log deletion by
typing
>n
and pressing the Enter key.
where
n is the letter associated with the task you want to
perform. Type a for a log addition (addrep). Type d for log
deletion (delrep).

Response:
Enter log identifier (”log_type”, or ”log_type log_number”) ==>

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-121

Log Delivery CM configuration file commissioning (continued)

8 Enter the log identifier by typing
>log identifier
and pressing the Enter key.
where
log identifier is the log type, or log type and number to be added
or deleted.
Note: If the log name and log number are both present, they must be
separated by a space. In the following response, all PM logs were deleted by
typing d pm.

Response:
CM Config File

1 – DEL CM 100
2 – DEL PM

f:forward, b:back a:add item, d:delete item

q:quit, h:help, m:main menu

Enter – a: addrep or d: delrep (or n for NOCMLOGS) ==>

9 Determine if you want to make more changes to the CM log stream list.

If you Do

want to make more changes step 5

do not want to make more changes step 14

10 Enter the menu option for deleting an item from the log stream list by typing
>d
and pressing the Enter key.

Response:
Enter item number to delete ==>

Wireless Networks Family SDM–SX User Guide SDMPL011

4-122 SDM maintenance procedures

Log Delivery CM configuration file commissioning (continued)

11 Enter the number of the item you want to delete from the list by typing
>#
and pressing the Enter key.
where
# is the number of the item from the list that you want to delete.

12 Determine if you want to make more changes to the CM log stream list.

If you Do

want to make more changes step 5

do not want to make more changes step 14

13 Return to the Logroute Main Menu by typing

>m
and pressing the Enter key.

14 Determine if you want to save any values you entered.

If you Do

want to save the changes step 13

do not want to save the changes step 29

15 Save the values you entered by typing

>s
and pressing the Enter key.
Note: After you save the changes you made to the CM log stream, the
changes must be activated. Busy and return the log delivery application to
service to have the changes take effect.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-123

Log Delivery CM configuration file commissioning (continued)

Response:
Logroute Main Menu

1 – Device List
2 – Global Parameters
3 – CM Configuration File

c:change menu, q:quit, h:help, s:save changes

Warning: You must save, then BSY and RTS the Log Delivery
======= application for any changes to take effect.

Save completed –– press return to continue

16 Press the enter key and quit the Logroute tool by typing
>q
and pressing the Enter key.
Response:
NOTE: Configuration data has changed
BSY and RTS the Log Delivery application
for changes to take effect.

maint:

17 Log out from the SDM by typing

>exit
and pressing the Enter key.

18 Determine if you want to activate the values you saved.

If you Do

want to activate the values step 19

do not want to activate the values step 32

19 Log in to the SDM as the root user.

20 Access the top menu level of the RMI by typing

#sdmmtc
and pressing the Enter key.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-124 SDM maintenance procedures

Log Delivery CM configuration file commissioning (continued)

21 Access the maintenance (MTC) menu level of the RMI by typing
>MTC
and pressing the Enter key.

22 Access the application (APPL) menu level of the RMI by typing

>APPL
and pressing the Enter key.
Example response:
# Package Description Version State
1 Table Access Service 10.0.29.0 InSv
2 OM Access Service 10.0.29.0 InSv
3 Log Delivery Service 10.0.29.0 InSv

23 Note the number of the Log Delivery Service (shown under the header “#”).

24 Manually busy the Log Delivery Service by typing

>BSY n
and pressing the Enter key.
where
n is the number of the Log Delivery Service (from step 23)
Response:
The application is in service.
This command will cause a service interruption.
Do you wish to proceed?
Please confirm (“YES”, “Y”, “NO”, or “N”):
Note: Busying the Log Delivery Service performs an orderly shutdown and can
take up to 2 min.

25 Confirm the Busy command by typing

>Y
and pressing the Enter key.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-125

Log Delivery CM configuration file commissioning (continued)

26 After you confirm the Bsy command, the following is displayed:
Response:
Application Bsy– Command initiated.
Please wait...
When the Bsy command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Response:
Application Bsy – Command submitted.

27 Return the Log Delivery Service to service by typing

>RTS n
and pressing the Enter key.
where
n is the number of the Log Delivery Service (from step 22)

Response:
Application RTS - Command initiated.
Please wait...
When the RTS command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”. Go to step 32.
Response:
Application RTS – Command submitted.

28 Quit the RMI by typing

>QUIT ALL
and pressing the Enter key.
Go to step 31.

29 Quit out of the CM Config File menu without saving any of the values you have
entered, by typing
>q
and pressing the Enter key.

Response:
Parameters have changed, do you want to save changes (y/n)?

Note: If you did not enter any changes, the message above will not appear.
Go to step 31.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-126 SDM maintenance procedures

Log Delivery CM configuration file commissioning (end)

(continued)

30 Indicate that you do not want to save your changes by typing

>n
and pressing the Enter key.

31 Log out from the SDM by typing

>exit
and pressing the Enter key.

32 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 4-127 SDM maintenance procedures 4-127

Migration from a rootvg system to a rootvg/datavg system

Application

ATTENTION
This procedure must be performed by a trained AIX system
administrator who has root user privileges to access the SDM.

ATTENTION
Perform this procedure after your system has been installed with the
required I/O controller module installed in the appropriate slots in the
main chassis. If you have not installed the required modules, refer to
the procedure ”Adding I/O controller modules” on page 4-59 in the
“SDM maintenance procedures” chapter of this document.

ATTENTION
This procedure requires that your system is MANB. Therefore, it is
recommended that you add a datavg when you upgrade the SDM. For
information about upgrading SDM software, refer to the Platform
Software Upgrade Implementation Guide.

Logical volume data can be stored in the root volume group (rootvg) or the
data volume group (datavg). Nortel recommends that you create datavg for
logical volumes with large amounts of data. If you do not create datavg,
logical volume data is stored in rootvg.

ATTENTION
Datavg is supported on 1 MFIO (in NTRX50GP). This provides 8
Gbyte storage capacity.

Use this procedure to move from a rootvg system to a system with both
rootvg and datavg. This procedure creates datavg, and moves logical
volumes from rootvg to datavg. Do not use this procedure if you have a new
system that requires datavg. Refer to the procedure ”Creating a logical
volume in the data volume group” on page 4-131 in the “SDM maintenance
procedures” chapter in this document.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-128 SDM maintenance procedures

Migration from a rootvg system to a rootvg/datavg system (continued)

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-129

Migration from a rootvg system to a rootvg/datavg system (continued)

Summary of Migration from a rootvg system to a rootvg/datavg system

Busy the SDM This flowchart summarizes the

procedure.

Use the instructions in the

procedure that follows this
Restrict use of flowchart to perform the
the SDM procedure.

Access the
hardware level
of the SDM

Insert new
MFIOs

Add and bring

online new
MFIOs

Create and
migrate to
Datavg

Return the
SDM to service

End

Wireless Networks Family SDM–SX User Guide SDMPL011

4-130 SDM maintenance procedures

Migration from a rootvg system to a rootvg/datavg system (end)

(continued)
Creating a data volume group
At the SDM level of the MAP display
1
Busy the SDM by typing
>BSY
and pressing the Enter key.
Response:
SDM is in service.
This command will cause a service interruption.
Do you wish to proceed?
Please confirm (“YES”, “Y”, “NO”, or “N”)
At the local or remote VT100 console
2 Disable telnet at the ADMIN level of the RMI to ensure no other user access to
SDM during the volume group migration.

3 Access the hardware screen of the RMI by typing

>hw
and pressing the Enter key.

4 To quit from RMI, type

>quit all
5 Move the filesystem from rootvg to datavg by typing
#movevg
and pressing the Enter key.
At the SDM level of the MAP display
6 Return the SDM to service by typing
>RTS
and pressing the Enter key.

7 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 4-131 SDM maintenance procedures 4-131

Creating a logical volume in the data volume group

Application

ATTENTION
This procedure must be performed by a trained Advanced Interactive
Executive (AIX) system administrator who has root user privileges to
access the SDM.

ATTENTION
Perform this procedure after your system has been installed with the
required I/O controller module installed in the appropriate slots in the
main chassis. If you have not installed the required modules, refer to
the procedure “Adding I/O controller modules” in this chapter.

Use this procedure if you have a new system that requires the data volume
group (datavg) to store logical volume data. If you have a root volume
group (rootvg) system, and wish to add datavg to your system, use the
procedure “Migration from a rootvg system to a rootvg/datavg system” on
page 4-127 in this chapter.

ATTENTION
The logical volume management feature prevents you from creating
more than 32 logical volumes.

There is no impact on functionality and no increased risk of

jeopardizing data. The amount of free space displayed in the
unallocated field of the storage menu level screen always displays the
correct data.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-132 SDM maintenance procedures

Creating a logical volume in the data volume group (continued)

Summary of Creating a logical volume in the data volume group

This flowchart summarizes the

procedure.

Log in to the Use the instructions in the

SDM as root procedure that follows this
flowchart to perform the
procedure.

Access the
RMI

Access the
storage level of
the RMI

Add the new

datavg disk

Create a new
logical volume

End

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-133

Creating a logical volume in the data volume group (continued)

Creating a data volume group

At the local VT100 console
1 Log in to the SDM as the root user.

2 Access the top menu level of the remote maintenance interface (RMI) by typing
# sdmmtc
and pressing the Enter key.

3 Access the system (Sys) menu level of the RMI by typing

>SYS
and pressing the Enter key.

4 Access the storage menu level of the RMI by typing

>5
and pressing the Enter key.
Example response:
rootvg:
Volume Size (MB) (% full/ threshold)
1 / 20 25/ 80
2 /usr 192 85/ 90
3 /var 40 11/ 80
4 /tmp 24 6/ 90
5 /home 300 4/ 70
6 /sdm 300 44/ 90
(unallocated) 608
Note: The example response shows part of the information displayed at the
storage menu level of the RMI. There are no logical volumes in datavg.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-134 SDM maintenance procedures

Creating a logical volume in the data volume group (end)

(continued)

5 Add a new disk by typing

>ADD VG
and pressing the Enter key.
Example response:
The following disks will be added to the system:

Datavg is currently being created...

The system informs you when the disk has been added successfully.
Example response:
All disks were successfully added.

Command complete.
Note 1: This step automatically adds datavg.
Note 2: An error message is displayed if the disks are not added successfully.
If this occurs, contact the personnel responsible for the next level of support.

6 Create the new logical volume by typing

>add lv xxx Mbyte
and pressing the Enter key.
where
xxx is the new logical volume name
Mbyte is the size of the logical volume in Mbyte
Example response:
Creating volume sba.
Note: An error message appears if you enter a backslash as part of the logical
volume name.
Example input:
>add lv abc/def 20
Note: If directory xxx already exists, and you try to create a new logical volume
with the same name as directory xxx, an error message appears.
Example response:
ERROR: Mountpoint for the new filesystem /xxx
already exists.

7 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 4-135 SDM maintenance procedures 4-135

Increasing the size of a logical volume

Application

ATTENTION
This procedure must be performed by a trained Advanced Interactive
Executive (AIX) system administrator who has root user privileges to
access the SDM.

Use this procedure to allocate more disk space to a logical volume.

WARNING
Increasing the size of a logical volume may limit future
software upgrade capability.
SDM logical volumes are pre-engineered to sizes that are
adequate for Nortel customers. Do not increase the size of
a logical volume unless absolutely necessary. If you need
to change the size of a logical volume, do so only with the
assistance of Nortel Technical Assistance and Support.
Failure to follow this warning may jeopardize future
software upgrade capability.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-136 SDM maintenance procedures

Increasing the size of a logical volume (continued)

Summary of Increasing the size of a logical volume

This flowchart summarizes the

procedure.

Log in to the Use the instructions in the

SDM as root procedure that follows this
flowchart to perform the
procedure.

Access the
RMI

Access the
storage level of
the RMI

Change the
logical volume
size

End

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-137

Increasing the size of a logical volume (continued)

Increasing the size of a logical volume
At the local VT100 console
1 Log in to the SDM as the root user.

2 Access the top menu level of the remote maintenance interface (RMI) by typing
# sdmmtc
and pressing the Enter key.

3 Access the system (Sys) menu level of the RMI by typing

>SYS
and pressing the Enter key.

4 Access the storage menu level of the RMI by typing

>5
and pressing the Enter key.
Example response:
SDM Node State: ISTb
SDM System State: ISTb
SDM Storage State: ISTb

rootvg:
Volume Size (MB) (% full/ threshold)
1 / 240 52/ 80
2 /usr 204 82/ 90
3 /var 40 35/ 70
4 /tmp 24 21/ 90
5 /home 304 75/ 70*
6 /sdm 304 47/ 90
7 /home/sba 16 7/ 80
(unallocated) 608
Note: The example response only shows part of the information displayed at
the storage menu level of the RMI.

5 Determine if there is unallocated disk space that can be used to increase a

logical volume.

If there is Do

enough disk space step 6

not enough disk space step 8

6 Identify the logical volume whose size you want to increase. Note the volume
name of the logical volume on the left of the System menu of the RMI.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-138 SDM maintenance procedures

Increasing the size of a logical volume (continued)

7

ATTENTION
A logical volume on the SDM must never reach 100% full. System
behaviour cannot be predicted when a logical volume reaches 100%
full. If the occupancy level of the specified logical volume has
exceeded its alarm threshold, contact your system administrator to
assess the current condition of the logical volume.

Change the size of the logical volume by typing

>change lv /xx Mbyte
and pressing the Enter key.
where
/xx is the name of the logical volume
Mbyte is the size in Mbytes to be added to the logical volume. The size
must be less than the amount of unallocated disk space.
Note: The first slash which represents the the logical volume is optional. For
example, you can type the command in either of the following ways:
>change lv /sba Mbyte
>change lv sba Mbyte
Example input:
>change lv /home 48
Example response:
Expanding Volume /home

More...

SDM Node State InSv

SDM System State InSv
SDM Storage State InSv
(rootvg):
Volume Size (MB) (% full/ threshold)
1 / 240 52/ 80
2 /usr 204 82/ 90
3 /var 40 35/ 70
4 /tmp 24 21/ 90
5 /home 352 65/ 70
6 /sdm 304 47/ 90
7 /home/sba 16 7/ 80
(unallocated) 560

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-139

Increasing
Increasing the of
the size size of a logical
a logical volumevolume (end)
(continued)
In the example response, the logical volume /home was expanded by 48
Mbytes.
Note: The SDM may round the new size to the nearest 4-, 8-, or 16-Mbyte
increment. For a 4-Gbyte disk, add 8- or 16-Mbyte multiples. When the logical
volume is created, the operating system determines the multiple that has to be
used.

8 Contact your next level of support.

9 You have completed this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-140 SDM maintenance procedures 4-140

Changing system thresholds

Application
Use this procedure to change SDM system thresholds. You can change the
following SDM system thresholds at the system menu level of the Remote
Maintenance Interface (RMI):
• CPU (run queue entries)
• Number of Processes
• Number of Zombies
• Swap Space (% full)
• Number of Swap Queue Entries
Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-141

Changing system thresholds (continued)

Summary of Changing system thresholds

This flowchart summarizes the

procedure.

Log in to the Use the instructions in the

SDM procedure that follows this
flowchart to perform the
procedure.

Access the
RMI

Access the
system menu
of the RMI

Identify the
threshold you
want to change

Change the
threshold

Threshold N Contact the next

changed level of support
correctly?

Y
End

Wireless Networks Family SDM–SX User Guide SDMPL011

4-142 SDM maintenance procedures

Changing system thresholds (continued)

Changing system thresholds
At the local VT100 console
1 Log in to the SDM.

2 Access the top menu level of the remote maintenance interface (RMI) by typing
# sdmmtc
and pressing the Enter key.

3 Access the system (Sys) menu level of the RMI by typing

>SYS
and pressing the Enter key.
Response:
SDM Node State: ISTb
SDM System State: ISTb
SDM Storage State: InSv

# Description Current/Threshold
1 CPU (run queue entries): 1/ 5
2 Number of Processes: 63/250
3 Number of Zombies: 0/ 3
4 Swap Space (% full): 72/ 70*
5 Number of Swap Queue Entries: 0/ 2

4 Identify which system threshold you want to change. Note the entry number of
the system threshold on the left of the RMI System menu. The number is
shown under the header “#”.
In the example in step 3, the entry number for CPU threshold is 1. The entry
number for the Number of Processes threshold is 2. The entry number for the
Number of Zombies is 3. The entry number for the Swap Space threshold is 4
and the entry number for Number of Swap Queue Entries is 5.
The current threshold value is shown under the header “Current/Threshold”.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-143

Changing
Changing system
system thresholds
thresholds (end)
(continued)

5 Change the system threshold by typing

>CHANGE n n1
and pressing the Enter key.
where
n is the entry number of the threshold you want to change
n1 is the new threshold value
Example input:
>CHANGE 4 80
Note: Here, the threshold for “Swap Space” changes from 70 to 80.
Example response:
SDM Node State: InSv
SDM System State: InSv
SDM Storage State: InSv

# Description Current/Threshold
1 CPU (run queue entries): 1/ 5
2 Number of Processes: 63/250
3 Number of Zombies: 0/ 3
4 Swap Space (% full): 72/ 80
5 Number of Swap Queue Entries: 0/ 2

Command submitted.

6 Wait 5 min. Check to see that the system threshold changed to the value that
you entered.
If the system threshold did not change correctly, contact the personnel
responsible for the next level of support.

7 You have completed this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-144 SDM maintenance procedures 4-144

Changing logical volume thresholds

Application
Use this procedure to change SDM logical volume thresholds. You can
change the following SDM logical volume thresholds at the storage level of
the Remote Maintenance Interface (RMI):
• /
• /usr
• /var
• /tmp
• /home
• /sdm
You can also change logical volume thresholds added by operating company
personnel.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-145

Changing logical volume thresholds (continued)

Summary of Changing logical volume thresholds

This flowchart summarizes the

procedure.

Log in to the Use the instructions in the

SDM procedure that follows this
flowchart to perform the
procedure.

Access the
RMI

Access the
storage menu
of the RMI

Identify the
threshold you
want to change

Change the
threshold

Threshold N Contact the next

changed level of support
correctly?

Y
End

Wireless Networks Family SDM–SX User Guide SDMPL011

4-146 SDM maintenance procedures

Changing logical volume thresholds (continued)

Changing system thresholds
At the local VT100 console
1 Log in to the SDM.

2 Access the top menu level of the remote maintenance interface (RMI) by typing
# sdmmtc
and pressing the Enter key.

3 Access the system (Sys) menu level of the RMI by typing

>STORAGE
and pressing the Enter key.
Response:
SDM Node State: ISTb
SDM System State: ISTb
SDM Storage State: ISTb

rootvg:
Volume Size (MB) (% full/ threshold)
1 / 240 52/ 80
2 /usr 204 82/ 90
3 /var 40 35/ 70
4 /tmp 24 21/ 90
5 /home 304 75/ 70*
6 /sdm 304 47/ 90
7 /home/sba 16 7/ 80
(unallocated) 608

4 Identify which logical volume threshold you want to change. Note the entry
number of the logical volume threshold on the left of the RMI System menu.
The number is shown under the header “#”.
The current threshold value is shown under the header “Current/Threshold” .

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-147

Changing
Changing logical
logical volume
volume thresholds
thresholds (end)
(continued)

5 Change the logical volume threshold by typing

>CHANGE n n1
and pressing the Enter key.
where
n is the entry number of the threshold you want to change
n1 is the new threshold value
Example input:
>CHANGE 5 80
Note: The threshold for “/home” has changed from 70 to 80.
Example response:
SDM Node State: InSv
SDM System State: InSv
SDM Storage State: InSv

rootvg:
Volume Size (MB) (% full/ threshold)
1 / 240 52/ 80
2 /usr 204 82/ 90
3 /var 40 35/ 70
4 /tmp 24 21/ 90
5 /home 304 75/ 80
6 /sdm 304 47/ 90
7 /home/sba 16 7/ 80
(unallocated) 608

6 Wait 5 min. Check to see that the logical volume threshold changed to the
value that you entered.
If the logical volume threshold did not change correctly, contact the personnel
responsible for the next level of support.

7 You have completed this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-148 SDM maintenance procedures 4-148

Changing the time interval for performance log SDM620

Application
Use this procedure to change the time interval for performance log SDM620.
Log report SDM620 reports the following examples of current SDM system
performance data:
• CPU use
• number of processes
• system thresholds for swap space occupancy
• logical volume capacities
The time interval defines how frequently the SDM generates the SDM620
log report.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-149

Changing the time interval for performance log SDM620 (continued)

Summary of Changing the time interval for performance log SDM620

This flowchart summarizes the

procedure.

Log in to the Use the instructions in the

SDM procedure that follows this
flowchart to perform the
procedure.

Access the
system menu
of the RMI

Change the
time interval for
SDM620 log

Confirm the
value

End

Wireless Networks Family SDM–SX User Guide SDMPL011

4-150 SDM maintenance procedures

Changing the time interval for performance log SDM620 (continued)

Changing the time interval for performance log SDM620
At the local VT100 console
1 Log in to the SDM as the root user.

2 Access the top menu level of the remote maintenance interface (RMI) by typing
# sdmmtc
and pressing the Enter key.

3 Access the system (Sys) menu level of the RMI by typing

>SYS
and pressing the Enter key.
Response:
SDM Node State: InSv
SDM System State: InSv
SDM Storage State: InSv

# Description Current/Threshold
1 CPU (run queue entries): 1/ 5
2 Number of Processes: 63/250
3 Number of Zombies: 0/250
4 Swap Space (% full): 16/ 70
5 Number of Swap Queue Entries: 0/ 2

Command submitted.

4 Check the performance log interval value by typing

>QUERYSDM
and pressing the Enter key 3 times.
Response:
System Indicator Thresholds (threshold/default)
–––––––––––––––––––––––––––––––––––––––––––––––––––––
Number of events before log: 4
CPU (Run Queue Entries): 12
Number of Processes: 250
Number of Zombies: 3
Swap Space (% full): 70
Number of Swap Queue Entries: 2

Performance Log Time Interval: 5

Note: In the preceding response, the performance log time interval is 5.

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 4-151

Changing the time interval for performance log SDM620 (continued)

5 Change the Performance Log Time Interval by typing
>CHANGE TI
and pressing the Enter key.
Response:
Time Interval: 5
Note: The system displays the current time interval value. In the preceding
response, the time interval is the default value of 5.

6 Enter the Performance Log Time Interval value by typing

>n
and pressing the Enter key.
where
n is the value in minutes. The valid range for this field is 5 to 20 160
(14 days) min. The default value is 5 min. The system will
not let you enter a value less than 5 min.
Response:
Values to be changed:
Performance Log Time Interval: 6 minutes
ENTER Y TO CONFIRM, N TO REJECT OR E TO EDIT.

7 Decide if you want to confirm the value you entered.

If you want to Do

confirm the value step 8

reject the value step 9
edit the value step 10

8 Confirm the value by typing

>Y
and pressing the Enter key.
Response:
Change Time Interval – Command initiated.
Please wait...

Change Time Interval – Command initiated.

Go to step 12.

Wireless Networks Family SDM–SX User Guide SDMPL011

4-152 SDM maintenance procedures

Changing the time interval for performance log SDM620 (end)

(continued)

9 Reject the value by typing

>N
and pressing the Enter key.
Response:
Change Time Interval – Command cancelled.

Go to step 12.

10 Edit the value by typing

>E
and pressing the Enter key.
Response:
Time Interval: 6
Note: The system displays the current time interval value. In the preceding
response, the time interval value is 6.

11 Enter the time interval value by typing

>n
and pressing the Enter key.
where
n is the time interval value. The time interval value must be entered
in minutes. The valid range for this field is 5 to 20 160 (14 days)
min. The default value is 5 min.
Response:
Values to be changed:
Performance Log Time Interval: 6 minutes
ENTER Y TO CONFIRM, N TO REJECT OR E TO EDIT.

Return to step 7.

12 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 5-1

SDM hardware replacement procedures

Introduction to SDM hardware replacement procedures

WARNING
SDM hardware warranty
This chapter only describes how to replace SDM
hardware. Do not attempt to open or disassemble any
SDM hardware modules. This may damage SDM
hardware, and violates the SDM product warranty.

CAUTION
System damage
Do not plug in any hardware modules that will not be
used. Extra modules may confuse the system after a
reboot or an installation from tape.

This chapter contains SDM hardware replacement procedures. Each

procedure contains the following:
• explanatory and context-setting information
• summary flowchart
• step-action instructions

Explanatory and context-setting information

The first page of each procedure contains the following headings:
• Application (why you would perform the procedure)
• Action (how to use the flowchart and step-action instructions)

Summary flowchart
The flowchart is only a summary of the main actions, decision points, and
possible paths you may take. Do not use the summary flowchart to perform
the procedure. Instead, use it to preview what you will be doing and to

Wireless Networks Family SDM–SX User Guide SDMPL011

5-2 SDM hardware replacement and extension procedures

prepare for it. For example, if you see that these instructions involve
another office, you will know to advise that office before you begin the
step-action instructions.

Step-action instructions
The step-action instructions tell you how to perform the procedure.
Normally you will perform the steps in order, but you may be directed to
return to a previous step and repeat a sequence. The successful completion
of a step may depend on previous steps; therefore, always perform the steps
in the order specified.

While following the step-action instructions, you may be sent to other

procedures of this book to perform a set of instructions, or to another NTP
for a related procedure. If this happens, you will be told when to return to
the original instructions, and to which point in those instructions you should
go.

The step-action instructions provide the command syntax and system

information you use or see while performing the procedure. For help on
DMS and SDM commands or output, see the “About this document” chapter
at the beginning of this document.

Return key and Enter key

The carriage return key is identified in different ways (such as Enter, Return
or Carriage Return) on various types of terminals. It is always used to enter
commands and parameters into the system.

The procedures contained in this book and in other NTPs instruct you to
press the Enter key after each step. If your terminal has a Return key, press
the Return key instead. Do not press the Enter key located beside the
numeric key pad.

297-5061-901 Standard 01.01 December 1998

 5-3 SDM hardware replacement procedures 5-3

NTRX50FD
CPU personality module

Application
Use this procedure to replace the CPU personality module, located at the
rear of the main chassis (slot 6) of a fault-tolerant SDM.

Nortel PEC Name

NTRX50FD CPU personality module

Action
The following flowchart is only a summary of the procedure. To replace the
CPU personality card, use the instructions in the step-action procedure that
follows the flowchart.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-4 SDM hardware replacement procedures

NTRX50FD
CPU personality module (continued)
Summary of Replacing a CPU personality module

This flowchart summarizes the

procedure.
Obtain the
replacement Use the instructions in the
module procedure that follows this
flowchart to perform the
procedure.
Log out of the
local or remote
console

Disconnect the
console cable

Remove the
personality
module

Replace the
personality
module

Reconnect the
console cable

Re-establish
asynchronous
connection

End

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-5

NTRX50FD
CPU personality module (continued)
Replacing a CPU personality module

1 Obtain a replacement CPU personality module. Ensure that the replacement

module has the same product engineering code (PEC), including suffix, as the
unit being removed. The PEC is written at the top of the module.

At the local or remote VT100 console

2 If you are logged in to the local or remote console, log out by typing
#ogout
and pressing the Enter key.

3
WARNING
Static electricity damage
Wear an electrostatic discharge (ESD) grounding wrist
strap connected to the C28B cabinet when handling a
module. This protects the module against damage
caused by static electricity.

At the back of the SDM

4 Disconnect the console cable (labelled SP0) connected to the CPU personality
module.

5 Loosen the two thumbscrews located at the top and bottom of the CPU
personality module.
Note: The thumbscrews are the captive type, and cannot be removed from the
module.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-6 SDM hardware replacement procedures

NTRX50FD
CPU personality module (continued)

6 While grasping the thumbscrews, gently pull the module towards you until it
protrudes about 2 in. (5.1 cm) from the SDM shelf.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-7

NTRX50FD
CPU personality module (continued)

7 Hold the module by the face plate with one hand while supporting the bottom
edge with the other hand. Gently pull the module toward you until it clears the
shelf.

8 Place the module you have removed in an ESD protective container.

9 Insert the replacement module into the SDM shelf.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-8 SDM hardware replacement procedures

NTRX50FD
CPU personality module (continued)

10 Gently slide the CPU personality module into the shelf until it is fully inserted.

11 Tighten the thumbscrews at the top and the bottom of the CPU personality
module.

12 Reconnect the console cable to the CPU personality module.

At the local or remote VT100 console

13 If you are using the local VT100 console, the asynchronous connection is
re-established automatically. Go to step 16.
If you are using a remote VT100 console, re-establish the asynchronous
connection to the SDM, continue this procedure.

14 Log in to the SDM.

15 Press the Enter key when you see the prompt, “TERM=(vt100)”. The console
prompt is then displayed.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-9

NTRX50FD
CPU CPU
personality module
personality module
(continued)
(end)

16 You have completed this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-10 SDM hardware replacement procedures 5-10

NTRX50FE, NTRX50FF
Fan tray

Application
Use this procedure to replace the fan tray located at the front of the main
chassis of an SDM-SX system.

Action
The following flowchart is only a summary of the procedure. To replace the
fan tray, use the instructions in the step-action procedure that follows the
flowchart.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-11

NTRX50FE, NTRX50FF
Fan tray (continued)
Summary of replacing fan tray

This flowchart summarizes the

Obtain the procedure.
replacement
module Use the instructions in the
procedure that follows this
flowchart to perform the
procedure.
Log in to the
RMI as the root
or maint user

Busy the fan

tray from the
HW level of the
RMI

Remove the
fan tray

Replace the
fan tray

RTS the fan tray

from the HW
level of the RMI

End

Wireless Networks Family SDM–SX User Guide SDMPL011

5-12 SDM hardware replacement procedures

NTRX50FE, NTRX50FF
Fan tray (continued)
Replacing fan tray

1 Obtain a replacement fan tray. Make sure that the replacement has the same
product engineering code (PEC), including suffix, as the unit being removed.
The PEC is shown on the left-hand locking lever of the fan tray.

At the local or remote VT100 console

2 Log in to the SDM as the root or maint user.

3 Access the RMI by typing

#sdmmtc
and pressing the Enter key.

4 Access the hardware level of the RMI by typing

>HW
and pressing the Enter key.

5 Busy the fan tray by typing

>BSY n FAN
and pressing the Enter key.
where
n 0 for domain 0
1 for domain 1
Example response:

Hardware Bsy: Domain 0 Device FAN – Command submitted

Do you wish to proceed?

Please confirm (“YES”, “Y”, “NO”, or “N”)

6 Continue by typing
>y
and pressing the Enter key.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-13

NTRX50FE, NTRX50FF
Fan tray (continued)
At the local or remote VT100 console
7
WARNING
Static electricity damage
Wear an electrostatic discharge (ESD) grounding wrist
strap connected to the C28B cabinet when handling a
module. This protects the module against damage
caused by static electricity.

8 Depress the tips of the locking levers on the face of the fan tray.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-14 SDM hardware replacement procedures

NTRX50FE, NTRX50FF
Fan tray (continued)

9 Open the locking levers on the face of the fan tray by moving the levers
outwards.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-15

NTRX50FE, NTRX50FF
Fan tray (continued)

10 While grasping the locking levers, gently pull the fan tray towards you until the
module protrudes about 2 in. (5.1 cm) from the equipment shelf.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-16 SDM hardware replacement procedures

NTRX50FE, NTRX50FF
Fan tray (continued)

11 Hold the fan tray by the face plate with one hand while supporting the bottom
edge with the other hand. Gently pull the fan tray toward you until it clears the
shelf.

12 Place the fan tray you have removed in an ESD protective container.

13 Insert the replacement fan tray into the shelf.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-17

NTRX50FE, NTRX50FF
Fan tray (continued)

14 Gently slide the fan tray into the shelf until it is almost fully inserted.

15 Partially close the locking levers, and continue to slide the fan tray until it is fully
inserted into the shelf. The locking levers lock by themselves when the fan tray
is fully inserted.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-18 SDM hardware replacement procedures

NTRX50FE, NTRX50FF
Fan tray (continued)

16 RTS fan tray by typing

>RTS n FAN
and pressing the Enter key.

where
n 0 for domain 0
1 for domain 1
Example response:

Hardware RTS: Domain 0 Device FAN – Command submitted

Do you wish to proceed?

Please confirm (“YES”, “Y”, “NO”, or “N”)

17 You have completed the procedure.

297-5061-901 Standard 01.01 December 1998

 5-19 SDM hardware replacement procedures 5-19

NTRX50FG
Interconnect module 0

Application
Use this procedure to replace an interconnect module (ICM) in domain 0,
located at the right hand side at the back of the main chassis of an SDM-SX
system.

Nortel PEC Name

NTRX50FG Interconnect module 0

Note: If you are replacing the ICM because it is indicated as failed (F) at the
hardware menu level of the remote maintenance interface (RMI), verify that
a loss of DC input power did not cause the ICM failure.

Action
The following flowchart summarizes the procedure. To replace interconnect
module 0, use the instructions in the step-action procedure that follows the
flowchart.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-20 SDM hardware replacement procedures

NTRX50FG
Interconnect module 0 (continued)
Summary of Replacing interconnect module 0

This flowchart summarizes the

Obtain the
procedure.
replacement
module
Use the instructions in the
1 procedure that follows this
flowchart to perform the
Log in to the Restore power procedure.
RMI as the root to domain 0
or maint user

Access the Return the

SDM level on SDM to service
the MAP from the MAP

Busy the SDM End

from the MAP

Shut down the

SDM from the
RMI

Turn the power

off to SDM
domain 0

Remove ICM 0

Replace ICM 0

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-21

NTRX50FG
Interconnect module 0 (continued)
Replacing an interconnect module 0

1 Obtain a replacement interconnect module. Make sure that the replacement

has the same product engineering code (PEC), including suffix, as the unit
being removed. The PEC is shown at the top, left-hand of the ICM.

At the local or remote VT100 console

2 Log in to the SDM as the root or maint user.
At the MAP display
3 Access the SDM level of the MAP display by typing
>MAPCI;MTC;APPL;SDM
and pressing the Enter key.
Example response:
SDM InSv
4 Manually busy the SDM by typing
>BSY
and pressing the Enter key.
Response:
SDM is in service.
This command will cause a service interruption.
Do you wish to proceed?
Please confirm (”YES”, ”Y”, ”NO”, or ”N”)
5 Confirm the Busy command by typing
>Y
and pressing the Enter key.
Response:
SDM Bsy initiated.
SDM Bsy completed.
At the local or remote VT100 console
6 Log in to the SDM as the root user. If SDM does not respond, go to step 8.

7 Shut down the SDM by typing

# shutdown
and pressing the Enter key.
Example response:
Shutdown in 1 minute
FXBug>

Wireless Networks Family SDM–SX User Guide SDMPL011

5-22 SDM hardware replacement procedures

NTRX50FG
Interconnect module 0 (continued)
At the front of the MSP
8 Shut off power to SDM domain 0 by turning off the left modular supervisory
panel (MSP) breaker.

At the back of the SDM

9
WARNING
Static electricity damage
Wear an electrostatic discharge (ESD) grounding wrist
strap connected to the C28B cabinet when handling a
module. This protects the module against damage
caused by static electricity.

10 Disconnect the alarm cable from ICM 0.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-23

NTRX50FG
Interconnect module 0 (continued)

11 Disconnect the power cable from ICM 0.

12 Loosen the two thumbscrews on ICM 0.

Note: The thumbscrews are the captive type, and cannot be removed from the
module.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-24 SDM hardware replacement procedures

NTRX50FG
Interconnect module 0 (continued)

13 Remove ICM 0 by gently sliding it out of the chassis.

14 Place the module you have removed in an ESD protective container.

15 Gently insert and seat the replacement ICM 0.

16 Secure the replacement ICM by tightening the two captive screws.

17 Reconnect the power cable to ICM 0.

18 Reconnect the alarm cable to ICM 0, if required (see step 10).

At the front of the MSP

19 Restore power to SDM domain 0 by switching on the MSP breaker turned off in
step 8.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-25

NTRX50FG
Interconnect module
Interconnect 0 (continued)
module 0 (end)
At the local or remote VT100 console
20 Allow the reboot to continue uninterrupted. If the reboot is interrupted, go to
step 21. If not, continue to step 23.

21 Contact the personnel responsible for the next level of support.

22 You have completed this procedure.

At the MAP display
23 Return the SDM to service by typing
>RTS
and pressing the Enter key.
Response:
SDM RTS initiated.
SDM RTS completed.
24 The system automatically returns all modules to service.

25 Complete the procedure by typing

>QUIT ALL
and pressing the Enter key.

26 You have completed this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-26 SDM hardware replacement procedures 5-26

NTRX50FH
Interconnect module 1

Application
Use this procedure to replace an interconnect module in domain 1, located at
the left hand side at the rear of the main chassis of an SDM–SX system.

Nortel PEC Name

NTRX50FH Interconnect module 1

Action
The following flowchart is only a summary of the procedure. To replace
interconnect module 1, use the instructions in the step-action procedure that
follows the flowchart.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-27

NTRX50FH
Interconnect module 1 (continued)
Summary of replacing interconnect module 1

This flowchart summarizes the

Obtain the 1
procedure.
replacement
module Replace ICM 1
Use the instructions in the
procedure that follows this
flowchart to perform the
Log in to the
procedure.
RMI as the root
or maint user Reconnect the
power cable to
ICM 1
Access the
hardware level
of the RMI Reconnect the
alarm cable to
ICM 1
Manually busy
ICM 1
Restore power
to SDM
domain 1
Turn power off
to SDM
domain 1
Return ICM 1
to service

Disconnect the
alarm cable
from ICM 1
End

Disconnect the
power cable
from ICM 1

Remove ICM 1

Wireless Networks Family SDM–SX User Guide SDMPL011

5-28 SDM hardware replacement procedures

NTRX50FH
Interconnect module 1 (continued)
Replacing interconnect module 1

1 Obtain a replacement interconnect module. Ensure that the replacement has

the same product engineering code (PEC), including suffix, as the unit being
removed. The PEC is written at the top, left-hand side of the ICM.

At the local or remote VT100 console

2 Log in to the SDM as the root or maint user.

3 Access the top menu level of the RMI by typing

# sdmmtc
and pressing the Enter key.

4 Access the hardware (Hw) menu level of the RMI by typing

>HW
and pressing the Enter key.

5 Manually busy ICM 1 by typing

>BSY 1 ICM
and pressing the Enter key.
Response:
Hardware Bsy – Domain 1 Device ICM
This action will affect all devices in I/O domain 1.

Do you wish to proceed?

Please confirm (“YES”, “Y”, “NO”, “N”)

6 Confirm the Bsy command by typing

>Y
and pressing the Enter key.
Note: When you manually busy ICM 1, all subtending devices, fan tray 1 in
domain 1 is placed in the CBsy state.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-29

NTRX50FH
Interconnect module 1 (continued)

7 After you confirm the Bsy command, the following is displayed:

Response:
Hardware Bsy : Domain 1 Device ICM – Command initiated.
Please wait...
Several warnings are displayed. The “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Response:
Hardware Bsy: Domain 1 Device ICM – Command submitted.
Note: At the hardware menu level of the RMI, the state of the interconnect
module and all subtending devices changes to “M”. The out-of-service LED on
the module is on (red).

At the back of the SDM

8
CAUTION
Potential service interruption
Ensure that you disconnect power to ICM 1. If you
disconnect power to the remaining in-service ICM
(ICM 0), you will shut down the entire SDM.

At the front of the MSP

9 Shut off all power to SDM domain 1 by turning off the right modular supervisory
panel (MSP) breaker.
At the back of the SDM

WARNING
Static electricity damage
Wear an electrostatic discharge (ESD) grounding wrist
strap connected to the C28B cabinet when handling a
module. This protects the module against damage
caused by static electricity.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-30 SDM hardware replacement procedures

NTRX50FH
Interconnect module 1 (continued)

10 Disconnect the alarm cable from ICM 1.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-31

NTRX50FH
Interconnect module 1 (continued)

11 Disconnect the power cable from ICM 1.

CAUTION
Potential service interruption
Ensure that you disconnect the power cable from ICM
1. If you disconnect the power cable to the remaining
in-service ICM (ICM 0), you will shut down the entire
SDM.

12 Loosen the two thumbscrews on ICM 1.

Note: The thumbscrews are the captive type, and cannot be removed from the
module.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-32 SDM hardware replacement procedures

NTRX50FH
Interconnect module 1 (continued)

13 Remove ICM 1 by gently sliding it out of the chassis.

14 Place the module you have removed in an ESD protective container.

15 Gently insert and seat the replacement ICM 1.

16 Secure the replacement ICM by tightening the two captive screws.

17 Reconnect the power cable to ICM 1.

18 Reconnect the alarm cable to ICM 1, if required (see step 10).

At the front of the MSP

19 Restore power to SDM domain 1 by switching on the MSP breaker turned off in
step 8.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-33

NTRX50FH
Interconnect module
Interconnect 1 (continued)
module 1 (end)
At the local or remote VT100 console
20 At the hardware menu level of the RMI, return ICM 1 to service by typing
>RTS 1 ICM
and pressing the Enter key
Response:
Hardware RTS : Domain 1 Device ICM – Command initiated.
Please wait...
When the RTS command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Response:
Hardware RTS : Domain 1 Device ICM – Command submitted.
At the back of the SDM
21 Allow 5 min for the interconnect modules to reintegrate. Check the LEDs on the
ICM that you replaced.

If Do

the ICM in-service LED is off, and the step 22

out-of-service LED is on (solid red or
flashing red)
the ICM in-service LED is on (solid green), step 23
and the out-of-service LED is off

22 Contact the personnel responsible for the next level of support.

23 You have completed this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-34 SDM hardware replacement procedures 5-34

NTRX50CF, NTRX50CG
CPU controller module

Application
Use this procedure to replace the CPU controller modules, located at the
front of the main chassis in slots 6 and 7.

Nortel PEC Name

NTRX50CF 200 MHz 604e CPU with 256 MByte DRAM

NTRX50CG 200 MHz 604e CPU with 256 MByte DRAM

Action
The following flowchart is only a summary of the procedure. To replace the
CPU controller module, use the instructions in the step-action procedure that
follows the flowchart.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-35

NTRX50CF, NTRX50CG
CPU controller module (continued)
Summary of Replacing a CPU controller module

This flowchart summarizes the

Obtain the procedure.
replacement
module Use the instructions in the
procedure that follows this
flowchart to perform the
Log in to the procedure.
RMI as the root
or maint user

Accessthe
Access SDM
level level
SDM on MAP
on
the MAP

Busy the SDM

at the MAP

1
Shutdown the Reboot the
SDM from the SDM
RMI.

Remove Return the

SDM to service
from the MAP

Replace End

Wireless Networks Family SDM–SX User Guide SDMPL011

5-36 SDM hardware replacement procedures

NTRX50CF, NTRX50CG
CPU controller module (continued)
Replacing a CPU controller module

1 Obtain a replacement CPU controller module. Ensure that the replacement

module has the same product engineering code (PEC), including suffix, as the
unit being removed. The PEC is shown on the top locking lever of the module.

At the local or remote VT100 console

2 Log in to the SDM as the root or maint user.
At the MAP display
3 Access the SDM level of the MAP display by typing
>MAPCI; MTC; APPL; SDM
and pressing the Enter key.
Example response:
SDM InSv
4 Manually busy the SDM by typing
>BSY
and pressing the Enter key.
Response:
SDM is in service.
This command will cause a service interruption.
Do you wish to proceed?
Please confirm (“YES”, “Y”, “NO”, or “N”)

5 Confirm the Busy command by typing

>Y
and pressing the Enter key.
Response:
SDM Bsy initiated.
SDM Bsy completed.

At the local or remote VT100 console

6 Log in to the SDM as the root user.

7 Interrupt the boot process when the “COLD start” message appears by pressing
the Break key.
Example response:
FX-Bug>

Note: The “COLD start” message does not appear for about 2 min.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-37

NTRX50CF, NTRX50CG
CPU controller module (continued)

8 Determine the current Greenwich Mean Time (GMT) setting on the existing
CPU controller modules by typing
FX-Bug>time
and pressing the Enter key.
Example response:
FRI APR 11 18:41:49:00

9 Record the date and time response.

Note: If you are using a clock set to your local time to set the GMT on the new
CPU controller modules, use the response in step 20 to calculate the number of
hours that your local time differs from GMT.
At the MSP
1 Interrupt power to the SDM by turning off the MSP break, located at the front of
the MSP. The MSP breaker supplies power to the SDM.
At the front of the SDM
2
WARNING
Static electricity damage
Wear an electrostatic discharge (ESD) grounding wrist
strap connected to the C28B cabinet when handling a
module. This protects the module against damage
caused by static electricity.

Undo the thumbscrews located on the top and the bottom of the CPU controller
module.
Note: The thumbscrews are the captive type, and cannot be removed from the
module.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-38 SDM hardware replacement procedures

NTRX50CF, NTRX50CG
CPU controller module (continued)

3 Depress the tips of the locking levers on the face of the CPU controller module.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-39

NTRX50CF, NTRX50CG
CPU controller module (continued)

4 Open the locking levers on the face of the module by moving the levers
outwards.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-40 SDM hardware replacement procedures

NTRX50CF, NTRX50CG
CPU controller module (continued)

5 While grasping the locking levers, gently pull each module towards you until it
protrudes about 2 in (5.1 cm) from the SDM shelf.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-41

NTRX50CF, NTRX50CG
CPU controller module (continued)

6 Hold the module by the face plate with one hand while supporting the bottom
edge with the other hand. Gently pull the module toward you until it clears the
shelf.

7 Place the module you have removed in an ESD protective container.

8 Insert the replacement module into the SDM shelf.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-42 SDM hardware replacement procedures

NTRX50CF, NTRX50CG
CPU controller module (continued)

9 Gently slide the module into the shelf until it is fully inserted.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-43

NTRX50CF, NTRX50CG
CPU controller module (continued)

10 Close the locking levers to secure the module. Ensure that both the top and
bottom micro switches are lined up with the locking levers to properly seat the
module.

Micro switch

Wireless Networks Family SDM–SX User Guide SDMPL011

5-44 SDM hardware replacement procedures

NTRX50CF, NTRX50CG
CPU controller module (continued)

11 Hold the module by the face plate with one hand while supporting the bottom
edge with the other hand. Gently pull the module toward you until it clears the
shelf.

12 Place the module you have removed in an ESD protective container.

13 Insert the replacement module into the SDM shelf.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-45

NTRX50CF, NTRX50CG
CPU controller module (continued)

14 Gently slide the module into the shelf until it is fully inserted.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-46 SDM hardware replacement procedures

NTRX50CF, NTRX50CG
CPU controller module (continued)

15 Close the locking levers to secure the module. Ensure that both the top and
bottom micro switches are lined up with the locking levers to properly seat the
module.

Micro switch

16 Tighten the thumbscrews on the module.

At the local or remote VT100 console
17 Interrupt the boot process when the “COLD start” message appears by pressing
the Break key.
Example response:
FX-Bug>

Note: The “COLD start” message does not appear for about 2 min.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-47

NTRX50CF, NTRX50CG
CPU controller module (continued)

18 Determine the current Greenwich Mean Time (GMT) setting on the new CPU
controller modules by typing
FX-Bug>time
and pressing the Enter key.
Example response:
FRI APR 11 18:21:41:00

19 Determine if the GMT setting for the new CPU controller modules is correct.

If the GMT setting is Do

incorrect step 20
correct step 21

20 Correct the time setting to the current GMT by typing

FX-Bug>set mmddyyhhmm
and pressing the Enter key.
where
mm is the the numeric month of the year (01 to 12)
dd is the the numeric day of the month (01 to 31)
yy is the the last two digits of the current year (00 to 99)
hh is the current hour (00 to 23)
mm is the current minute (00 to 59)

CAUTION
Potential loss of service
Ensure that the GMT setting on the new CPU
controller modules is later than the setting on the
previous CPU controller modules (as recorded in step
8). If the system is rebooted with a GMT setting that
is earlier than the time the system was shut down,
system configuration and status information may be
corrupted.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-48 SDM hardware replacement procedures

NTRX50CF, NTRX50CG
CPU controller module (continued)
(end)

21 Boot the SDM from disk by typing

FX-Bug>pboot 1 0
and pressing the Enter key.

22 Allow the reboot to continue uninterrupted.

23 At the login prompt, log in to the SDM as the root user.

24 Restore the bootlist by typing

# bootlist -m normal hdisk0
and pressing the Enter key.

At the MAP display

25 Return the SDM to service by typing
>RTS
and pressing the Enter key.
Response:
SDM RTS initiated.
SDM RTS completed.

26 The system automatically returns all modules to service.

27 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 5-49 SDM hardware replacement procedures 5-49

NTRX50GN
I/O controller module

Application
Use this procedure to replace the I/O controller module, located at the front
of the main chassis (slots 2 and 3 on the SDM-SX system.)

Nortel PEC Name

NTRX50GN I/O controller module with 4-Gbyte disk drive, DAT

and Ethernet

Action
The following flowchart is only a summary of the procedure. To replace the
I/O controller module, use the instructions in the step-action procedure that
follows the flowchart.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-50 SDM hardware replacement procedures

NTRX50GN
I/O controller module (continued)
Summary of replacing an I/O controller module

Obtain the This flowchart summarizes the

replacement procedure.
module
Use the instructions in the
procedure that follows this
Log in to the flowchart to perform the
RMI as the root procedure.
or maint user

Create a
system backup
tape

1
Access the Reboot the
Access
SDM SDM
level Reboot SDM
SDM from
levelthe
from on MAP
MAP

Busy the SDM Restart the

from the MAP SDM

Shut down the End

SDM from the
RMI

Eject the tape

if required

Remove the
Remove
I/O I/O
controller
Controller

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-51

NTRX50GN
I/O controller module (continued)
Replacing an I/O controller module

1 Obtain a replacement I/O controller module. Ensure that the replacement

module has the same product engineering code (PEC), including suffix, as the
unit being removed. The PEC is shown on the top locking lever of the module.

At the local or remote VT100 console

2 Log in to the SDM as the root or maint user.
At the MAP display
3 Access the SDM level of the MAP display by typing
>MAPCI; MTC; APPL; SDM
and pressing the Enter key.

Example response:
SDM InSv
4 Manually busy the SDM by typing
>BSY
and pressing the Enter key.
Response:
SDM is in service.
This command will cause a service interruption.
Do you wish to proceed?
Please confirm (”YES”, ”Y”, ”NO”, or ”N”)
5 Confirm the Busy command by typing
>Y
and pressing the Enter key.
Example response:
SDM Bsy initiated.
SDM Bsy completed.

Note: If the SDM is not running, go to step 7.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-52 SDM hardware replacement procedures

NTRX50GN
I/O controller module (continued)

6 Halt the SDM by typing

>haltsdm
and pressing the Enter key.
Response:
SDM is in service.
This command will cause a service interruption.
Do you wish to proceed?
Please confirm (”YES”, ”Y”, ”NO”, or ”N”)
7 Confirm to proceed by typing
>Y
8 Depress the tip of the locking lever on the face of the I/O controller module.

Undo the thumbscrews located on the top and the bottom of the I/O controller
module.
Note: The thumbscrews are the captive type, and cannot be removed from the
module.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-53

NTRX50GN
I/O controller module (continued)

9 Open the locking lever on the face of the module by moving the lever outwards.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-54 SDM hardware replacement procedures

NTRX50GN
I/O controller module (continued)

10 While grasping the locking lever, gently pull the module towards you until it
protrudes about 2 in. (5.1 cm) from the SDM shelf.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-55

NTRX50GN
I/O controller module (continued)

11 Hold the module by the face plate with one hand while supporting the bottom
edge with the other hand. Gently pull the module toward you until it clears the
shelf.

12 Place the module you have removed in an ESD protective container.

13 Insert the replacement module into the SDM shelf.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-56 SDM hardware replacement procedures

NTRX50GN
I/O controller module (continued)

14 Gently slide the module into the shelf until it is fully inserted.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-57

NTRX50GN
I/O controller module (continued)

15 Close the locking lever to secure the module. Ensure that the top micro switch
is lined up with the locking lever to properly seat the module.

Micro switch

16 Tighten the thumbscrews on the module.

Note: When the replacement I/O controller module is inserted, both its LEDs
turn on and off briefly, indicating that the module is seated correctly, is receiving
power, and has passed its self tests. The module’s in-service LED then turns
off, and its out-of-service LED turns on.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-58 SDM hardware replacement procedures

NTRX50GN
I/O controller module (continued)
(end)
At the local or remote VT100 console
17 Restore using system backup procedure located in Chapter 6 of the SDM–SX
User Guide.
At the MAP display
18 Return the SDM to service by typing
>RTS
and pressing the Enter key.

Response:
SDM RTS initiated.
SDM RTS completed.

The system automatically returns all modules to service.

19 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 5-59 SDM hardware replacement procedures 5-59

NTRX50GP
I/O controller module

Application
Use this procedure to replace the I/O controller module, located at the front
of the main chassis (slots 2 and 3 on the SDM-SX system.)

Nortel PEC Name

NTRX50GP I/O controller module with 4-Gbyte disk drive, DAT

and Ethernet

Action
The following flowchart is only a summary of the procedure. To replace the
I/O controller module, use the instructions in the step-action procedure that
follows the flowchart.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-60 SDM hardware replacement procedures

NTRX50GP
I/O controller module (continued)
Summary of replacing an I/O controller module

Obtain the This flowchart summarizes the

replacement procedure.
module
Use the instructions in the
procedure that follows this
Log in to the flowchart to perform the
RMI as the root procedure.
or maint user

Create a
system backup
tape

1
Access the Reboot the
Access
SDM SDM
level Reboot SDM
SDM from
levelthe
from on MAP
MAP

Busy the SDM Restart the

from the MAP SDM

Shut down the End

SDM from the
RMI

Eject the tape

if required

Remove the
Remove
I/O I/O
controller
Controller

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-61

NTRX50GP
I/O controller module (continued)
Replacing an I/O controller module

1 Obtain a replacement I/O controller module. Ensure that the replacement

module has the same product engineering code (PEC), including suffix, as the
unit being removed. The PEC is shown on the top locking lever of the module.

At the local or remote VT100 console

2 Log in to the SDM as the root or maint user.
At the MAP display
3 Access the SDM level of the MAP display by typing
>MAPCI; MTC; APPL; SDM
and pressing the Enter key.

Example response:
SDM InSv
4 Manually busy the SDM by typing
>BSY
and pressing the Enter key.
Response:
SDM is in service.
This command will cause a service interruption.
Do you wish to proceed?
Please confirm (”YES”, ”Y”, ”NO”, or ”N”)
5 Confirm the Busy command by typing
>Y
and pressing the Enter key.
Example response:
SDM Bsy initiated.
SDM Bsy completed.

Note: If the SDM is not running, go to step 7.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-62 SDM hardware replacement procedures

NTRX50GP
I/O controller module (continued)

6 Halt the SDM by typing

>haltsdm
and pressing the Enter key.

7 Depress the tip of the locking lever on the face of the I/O controller module.

Undo the thumbscrews located on the top and the bottom of the I/O controller
module.
Note: The thumbscrews are the captive type, and cannot be removed from the
module.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-63

NTRX50GP
I/O controller module (continued)

8 Open the locking lever on the face of the module by moving the lever outwards.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-64 SDM hardware replacement procedures

NTRX50GP
I/O controller module (continued)

9 While grasping the locking lever, gently pull the module towards you until it
protrudes about 2 in. (5.1 cm) from the SDM shelf.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-65

NTRX50GP
I/O controller module (continued)

10 Hold the module by the face plate with one hand while supporting the bottom
edge with the other hand. Gently pull the module toward you until it clears the
shelf.

11 Place the module you have removed in an ESD protective container.

12 Insert the replacement module into the SDM shelf.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-66 SDM hardware replacement procedures

NTRX50GP
I/O controller module (continued)

13 Gently slide the module into the shelf until it is fully inserted.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-67

NTRX50GP
I/O controller module (continued)

14 Close the locking lever to secure the module. Ensure that the top micro switch
is lined up with the locking lever to properly seat the module.

Micro switch

15 Tighten the thumbscrews on the module.

Note: When the replacement I/O controller module is inserted, both its LEDs
turn on and off briefly, indicating that the module is seated correctly, is receiving
power, and has passed its self tests. The module’s in-service LED then turns
off, and its out-of-service LED turns on.
At the RMI
16 Access the top menu level of the RMI by typing
#sdmmtc
and pressing the Enter key.

17 Access the RMI hardware (Hw) level by typing

>HW
and pressing the Enter key.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-68 SDM hardware replacement procedures

NTRX50GP
I/O controller module (continued)

18 Return the new disks to service by typing

>rts 0 dsk2
and pressing the Enter key.

19 Allow the new disks to complete the return to service.

20 Exit the RMI by typing

>quit all
and pressing the Enter key.
At the local or remote VT100 console
21 Reboot the SDM by typing
#shutdown –Fr
and pressing the Enter key.
At the MAP display
22 Log into SDM as root user.

23 Type
#exportvg datavg
and press the Enter key.

24 Type
#rmfs /data
and press the Enter key.

25 Type
#rmdir /data
and press the Enter key.
At the MAP display
26 Access the top menu level of the RMI by typing
#sdmmtc
and pressing the Enter key.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-69

NTRX50GP
I/O controller module
I/O controller module
(continued)
(end)

27 Access the storage menu level of the RMI by typing

>storage
and pressing the Enter key.

28 Type
>add vg
and press the Enter key at the RMI storage level.

29 Type
>add lv /data 200
and press the Enter key at the RMI storage level.

30 Exit the RMI level by typing

>quit all
and pressing the Enter key.

31 Type
#cd /
at the UNIX prompt. Press the Enter key.

32 Type
#chmod 775 data
at the UNIX prompt. Press the Enter key.

33 Type
#chown root:maint data
at the UNIX prompt. Press the Enter key.

34 Return the SDM to service by typing

>rts
and pressing the Enter key.

35 You have completed this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-70 SDM hardware replacement procedures 5-70

NTRX50FS
LAN personality module

Application
Use this procedure to replace a LAN personality module, located at the rear
of the main chassis (slot 2 on the SDM-SX system.)

Nortel PEC Name

NTRX50FS LAN personality module

Note: Each I/O controller module must also have an associated LAN
personality module (NTRX50FS) installed at the back of the SDM. Ethernet
LAN connectivity, however, is only supported by the mandatory
NTRX50FQ or NTRX50GN I/O controller modules located in slots 2 and 3
at the front of the main chassis.

Action
The following flowchart is only a summary of the procedure. To replace the
LAN personality module, use the instructions in the step-action procedure
that follows the flowchart.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-71

NTRX50FS
LAN personality module (continued)
Summary of Replacing a LAN personality module

Obtain the
replacement This flowchart
module summarizes the
procedure.
1

Log in to the Reboot SDM Use the instructions in

RMI as the root the procedure that
or maint user follows this flowchart
to perform the
procedure.
Access the RTS
RTSSDM
SDMatat
SDM level on MAP
MAP
the MAP

Busy the SDM End

from the MAP

Shutdown the
SDM from RMI

Determine the
location of the
hardware

Remove LAN
personality
module

Replace LAN
personality
module

Wireless Networks Family SDM–SX User Guide SDMPL011

5-72 SDM hardware replacement procedures

NTRX50FS
LAN personality module (continued)
Replacing a LAN personality module

1 Obtain a replacement LAN personality module. Ensure that the replacement

module has the same product engineering code (PEC), including suffix, as the
unit being removed. The PEC is written at the top of the module.

At the local or remote VT100 console

2 Log in to the SDM as the root or maint user.
At the MAP display
3 Access the SDM level of the MAP display by typing
>MAPCI; MTC; APPL; SDM

Example response:
SDM InSv
4 Manually busy the SDM by typing
>BSY
and pressing the Enter key.
Response:
SDM is in service.
This command will cause a service interruption.
Do you wish to proceed?
Please confirm (”YES”, ”Y”, ”NO”, or ”N”)
5 Confirm the busy command by typing
>Y
and pressing the Enter key.
Example response:
SDM Bsy initiated.
SDM Bsy completed.
6 Press the <break> key to get the FXbug prompt.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-73

NTRX50FS
LAN personality module (continued)

7 Issue a shutdown on the SDM RMI by typing

#shutdown –Fr
and pressing the Enter key.
Example response:
At the front of the SDM
8
WARNING
Static electricity damage
Wear an electrostatic discharge (ESD) grounding wrist
strap connected to the C28B cabinet when handling a
module. This protects the module against damage
caused by static electricity.

Press the eject button to remove the tape (if present) from the tape drive.

9 Undo the thumbscrews located on the top and bottom of the I/O controller
module associated with the LAN personality module you wish to replace.
Note: The thumbscrews are the captive type, and cannot be removed from the
module.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-74 SDM hardware replacement procedures

NTRX50FS
LAN personality module (continued)

10 Depress the tip of the locking lever on the face of the I/O controller module.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-75

NTRX50FS
LAN personality module (continued)

11 Open the locking lever on the face of the module by moving the lever outwards.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-76 SDM hardware replacement procedures

NTRX50FS
LAN personality module (continued)
At the back of the SDM
12 Determine what kind of hardware module your SDM has.

If you have Do

NTRX50GN step 13
NTRX50GP step 15

13 Label the 10BASE–T cable connected to the LAN personality module you wish
to replace.

14 Disconnect the 10BASE-T cable, as shown in the following diagram.

15 Loosen the two thumbscrews located at the top and the bottom of the LAN
personality module.
Note: The thumbscrews are the captive type, and cannot be removed from the
module.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-77

NTRX50FS
LAN personality module (continued)

16 While grasping the thumbscrews, gently pull the LAN personality module
towards you until it protrudes about 2 in. (5.1 cm) from the SDM shelf.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-78 SDM hardware replacement procedures

NTRX50FS
LAN personality module (continued)

17 Hold the LAN personality module by the face plate with one hand while
supporting the bottom edge with the other hand. Gently pull the module toward
you until it clears the shelf.

18 Place the LAN personality module you have removed in an ESD protective
container.

19 Insert the replacement LAN personality module into the SDM shelf.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-79

NTRX50FS
LAN personality module (continued)

20 Gently slide the LAN personality module into the shelf until it is fully inserted.

21 Tighten the thumbscrews at the top and the bottom of the LAN personality
module.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-80 SDM hardware replacement procedures

NTRX50FS
LAN personality module (continued)

22 Determine whether you need to reconnect the 10BASE-T cable.

If you have Do

NTRX50GN step 23
NTRX50GP step 24

23 Reconnect the 10BASE-T cable to the LAN personality module. If you wish,
remove the label that you put on the cable in step 13.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-81

NTRX50FS
LAN personality module (continued)
At the front of the SDM
24 Close the locking lever to secure the I/O controller module you unseated in step
9. Ensure that the top micro switch is lined up with the locking lever to properly
seat the module.

Micro switch

25 Tighten the thumbscrews on the I/O controller module.

Note: When the replacement I/O controller module is inserted, both LEDs on
the module turn on and off briefly, indicating that the module is seated correctly,
is receiving power, and has passed its self tests. The in-service light on the I/O
controller module turns off, and its out-of-service light turns on (red).
At the local or remote VT100 console
26 Reboot the SDM by typing
FXBug>pboot 1 0
and press the Enter key.
Example response after reboot sequence:
login:

Wireless Networks Family SDM–SX User Guide SDMPL011

5-82 SDM hardware replacement procedures

NTRX50FS
LAN personality module (continued)
(end)
At the MAP display
27 Return the SDM to service by typing
>RTS
and pressing the Enter key.
Response:
SDM RTS initiated.
SDM RTS completed.

The system autormatically returns all modules to service.

28 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 5-83 SDM hardware replacement procedures 5-83

NTRX50GA, NTRX50GX
DS512 controller module

Application
Use this procedure to replace the DS512 controller module, located at the
front of the main chassis (slot 1 on the SDM-SX system.)

Nortel PEC Name

NTRX50GA DS512 controller module

NTRX50GX Enhanced DS512 controller module

Action
The following flowchart is only a summary of the procedure. To replace the
DS512 controller module, use the instructions in the step-action procedure
that follows the flowchart.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-84 SDM hardware replacement procedures

NTRX50GA, NTRX50GX
DS512 controller module (continued)
Summary of Replacing a DS512 controller module

Obtain the This flowchart summarizes the

replacement procedure.
module
Use the instructions in the
procedure that follows this
Busy the SDM flowchart to perform the
from the MAP procedure.

Manually busy
the DS512 links

Manually busy
the DS512
controller module

Replace the
DS512 controller
module

Return the DS512

controller module
to service

Return the DS512

links to service

RTS the SDM End

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-85

NTRX50GA, NTRX50GX
DS512 controller module (continued)
Replacing a DS512 controller module

1 Obtain a replacement DS512 controller module. Ensure that the replacement

module has the same product engineering code (PEC), including suffix, as the
unit being removed. The PEC is shown on the top locking lever of the module.

At the MAP display

2 Access the SDM MAP display level by typing
>MAPCI; MTC; APPL; SDM
and pressing the Enter key.
Example response:
SDM InSv

3 Manually busy the SDM by typing

>BSY
and pressing the Enter key.
Response:
SDM is in service.
This command will cause a service interruption.
Do you wish to proceed?
Please confirm (”YES”, ”Y”, ”NO”, ”N”)

4 Confirm the Busy command by typing

>Y
and pressing the Enter key.

Response:
SDM Bsy initiated.
SDM Bsy completed.
5 Display the message (MS) port modules that provides the DS512 links to the
SDM, by typing
>TRNSL

and pressing the Enter key.

Example response:
SDM 0 DOMAIN 0 PORT 0 (MS 0:15:0) OK MsgCnd:Open
SDM 0 DOMAIN 0 PORT 1 (MS 1:15:0) OK MsgCnd:Open

Wireless Networks Family SDM–SX User Guide SDMPL011

5-86 SDM hardware replacement procedures

NTRX50GA, NTRX50GX
DS512 controller module (continued)

6 Record the MS port module number associated with the SDM DS512 links.
The MS port number is the middle number shown in the parentheses.
Note: In the example response shown in step 5, the port module number is 15.

7 Access the MS level of the MAP display by typing

>MS
and pressing the Enter key.

8 Access the shelf level by typing

>SHELF 0
and pressing the Enter key.

9 Access the MS port module level that is associated with the SDM DS512 links
by typing
>CHAIN cardno
and pressing the Enter key.
where
cardno is the MS port module number recorded in step 6
10 Manually busy the DS512 link between MS plane 0 and the SDM DS512
controller module you wish to replace by typing
>BSY 0 LINK 0
and pressing the Enter key.
Example response:
Request to MAN BUSY MS: 0 shelf: 0 chain:19 link: 0 submitted.
Request to MAN BUSY MS: 0 shelf: 0 chain:19 link: 0 passed.

Note: The state for the DS512 link changes to “M” for MS plane.

11 Manually busy the DS512 link between MS plane 1 and the SDM DS512
controller module you wish to replace by typing
>BSY 1 LINK 0 force
and pressing the Enter key.
Example response:
Request to MAN BUSY MS: 1 shelf: 0 chain:19 link: 0 submitted.
Request to MAN BUSY MS: 1 shelf: 1 chain:19 link: 0 passed.

Note: The state for the DS512 link changes to “M” for MS plane 1.

At the local or remote VT100 console

12 Log in to the SDM as the root or maint user.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-87

NTRX50GA, NTRX50GX
DS512 controller module (continued)

13 Access the top menu level of the remote maintenance interface (RMI) by typing
# sdmmtc
and pressing the Enter key.

14 Access the hardware (Hw) menu level of the RMI by typing

>HW
and pressing the Enter key.

15 Manually busy the DS512 controller module by typing

>BSY 0 512 Force
and pressing the Enter key.

Example response:
Hardware Bsy – Domain 0 Device 512
Redundant device not in-service.
Warning: This command will isolate the SDM.

Do you wish to proceed?

Please confirm (“YES”, “Y”, “NO”, or “N”)

16 Confirm the Bsy command by typing

>Y
and pressing the Enter key.

17 After you confirm the Bsy command, the following is displayed:

Example response:
Hardware Bsy : Domain 0 Device 512 – Command initiated.
Please wait...
When the Bsy command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Example response:
Hardware Bsy : Domain 0 Device 512 – Command submitted.
Note: At the hardware menu level of the RMI, the state of the DS512
controller module changes to “M”.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-88 SDM hardware replacement procedures

NTRX50GA, NTRX50GX
DS512 controller module (continued)
At the front of the SDM
18
WARNING
Static electricity damage
Wear an electrostatic discharge (ESD) grounding wrist
strap connected to the C28B cabinet when handling a
module. This protects the module against damage
caused by static electricity.

19 Undo the thumbscrews located on the top and the bottom of the DS512
controller module.
Note: The thumbscrews are the captive type, and cannot be removed from the
module.

20 Depress the tips of the locking levers on the face of the DS512 controller
module.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-89

NTRX50GA, NTRX50GX
DS512 controller module (continued)

21 Open the locking levers on the face of the module by moving the levers
outwards.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-90 SDM hardware replacement procedures

NTRX50GA, NTRX50GX
DS512 controller module (continued)

22 While grasping the locking levers, gently pull the module towards you until it
protrudes about 2 in. (5.1 cm) from the SDM shelf.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-91

NTRX50GA, NTRX50GX
DS512 controller module (continued)

23 Hold the module by the face plate with one hand while supporting the bottom
edge with the other hand. Gently pull the module toward you until it clears the
shelf.

24 Place the module you have removed in an ESD protective container.

25 Insert the replacement module into the SDM shelf.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-92 SDM hardware replacement procedures

NTRX50GA, NTRX50GX
DS512 controller module (continued)

26 Gently slide the module into the shelf until it is fully inserted.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-93

NTRX50GA, NTRX50GX
DS512 controller module (continued)

27 Close the locking levers to secure the module. Ensure that both the top and
bottom micro switches are lined up with the locking levers to properly seat the
module.

Micro switch

Wireless Networks Family SDM–SX User Guide SDMPL011

5-94 SDM hardware replacement procedures

NTRX50GA, NTRX50GX
DS512 controller module (continued)
At the local or remote VT100 console
28 At the hardware level of the RMI, return the DS512 controller module to service
by typing
>RTS 0 512
and pressing the Enter key.

Example response:
Hardware RTS : Domain 0 Device 512 – Command initiated.
Please wait...
When the RTS command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Example response:
Hardware RTS : Domain 0 Device 512 – Command submitted.
Note: At the hardware menu level of the RMI, the state of the DS512 controller
module changes to a dot (.), indicating the module has returned to service.
The in service LED on the DS512 controller module is on (green).

At the MAP display

29 At the MS port module level of the MAP display (accessed in step 9), return to
service the DS512 link between MS plane 0 and the DS512 controller module
you replaced by typing
>RTS 0 LINK 0
and pressing the Enter key.
Example response:
Request to RTS MS: 0 shelf: 0 chain:19 link: 0 submitted.
Request to RTS MS: 0 shelf: 0 chain:19 link: 0 passed.
Note: The state for the DS512 link changes to a dot (.) if the SDM DS512 link
is in service. Otherwise, the state for DS512 link changes to a “P”.
At the MS port level of the MAP
30 Return to service the DS512 link between MS plane 1 and the DS512 controller
module you replaced by typing
>RTS 1 LINK 0
and pressing the Enter key.
Example response:
Request to RTS MS: 1 shelf: 0 chain:19 link: 1 submitted.
Request to RTS MS: 1 shelf: 0 chain:19 link: 1 passed.
Note: The state for the DS512 link changes to a dot (.) if the SDM DS512 link
is in service. Otherwise, the state for DS512 link changes to a “P”.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-95

NTRX50GA, NTRX50GX
DS512 controller
DS512 module
controller module
(continued)
(end)
At the SDM MAP level
31 Return the SDM to service by typing
>RTS
and pressing the Enter key.

Response:
SDM RTS initiated.
SDM RTS completed.

The system automatically returns all modules to service.

32 You have completed this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-96 SDM hardware replacement procedures 5-96

NTRX50GH
DS512 personality module

Application
Use this procedure to replace the DS512 personality module, located at the
rear of the main chassis (slot 1 on the SDM-SX system.)

Nortel PEC Name

NTRX50GH DS512 personality module

Action
The following flowchart is only a summary of the procedure. To replace the
DS512 personality module, use the instructions in the step-action procedure
that follows the flowchart.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-97

NTRX50GH
DS512 personality module (continued)
Summary of Replacing a DS512 personality module

This flowchart
Obtain the summarizes
replacement 1 the procedure.
module
Access
Manuallythe
busy Use the
hardware
the DS512level instructions in
Access the of the RMI
links the procedure
SDM MAP that follows this
display level flowchart to
Manually busy perform the
the DS512 procedure.
Busy the SDM controller module
from the MAP

Unseat the
DS512 controller
Display the MS module
port modules

Remove DS512
personality
Access the MS module
level of the
MAP display
Replace DS512
2
personality
Access the module Return the
shelf level DS512 links to
service
Seat the DS512
controller module
Access the MS Return the SDM
port module to service
level
Return the
DS512 controller
Manually busy to service End
the DS512
links
2

Wireless Networks Family SDM–SX User Guide SDMPL011

5-98 SDM hardware replacement procedures

NTRX50GH
DS512 personality module (continued)
Replacing a DS512 personality module

1 Obtain a replacement DS512 personality module. Make sure that the

replacement module has the same product engineering code (PEC), including
suffix, as the unit being removed. The PEC is shown at the top of the module.

2 Access the SDM MAP display level by typing

>MAPCI; MTC; APPL; SDM
and pressing the Enter key.
Example response:
SDM InSv
3 Manually Busy the SDM by typing
>BSY
and pressing the Enter key.
Response:
SDM is in service.
This command will cause a service interruption.
Do you wish to proceed?
Please confirm (”YES”, ”Y”, ”NO”, ”N”)
4 Confirm the Busy command by typing
>Y
and pressing the Enter key.

Response:
SDM Bsy initiated.
SDM Bsy completed.
At the MAP display
5 Display the message (MS) port modules which provide the DS512 links to the
SDM by typing
>TRNSL
and pressing the Enter key.
Example response:
SDM 0 DOMAIN 0 PORT 0 (MS 0:15:0) OK MsgCnd:Open
SDM 0 DOMAIN 0 PORT 1 (MS 1:15:0) OK MsgCnd:Open

6 Record the MS port module number associated with the SDM DS512 links.
The MS port number is the middle number shown in the parentheses.
Note: In the example response shown in step 5, the port module number is 15.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-99

NTRX50GH
DS512 personality module (continued)

7 Access the MS level of the MAP display by typing

>MS
and pressing the Enter key.

8 Access the shelf level by typing

>SHELF 0
and pressing the Enter key.

9 Access the MS port module level associated with the SDM DS512 links by
typing
>CHAIN cardno
and pressing the Enter key.
cardno is the MS module port number recorded in step 6

10 Manually busy the DS512 link between MS plane 0 and the SDM DS512
personality module you wish to replace by typing
>BSY 0 LINK 0
and pressing the Enter key.
Example response:
Request to MAN BUSY MS: 0 shelf: 0 chain:19 link: 0 submitted.
Request to MAN BUSY MS: 0 shelf: 0 chain:19 link: 0 passed.

Note: The state for the DS512 link changes to “M” for MS plane.

11 Manually busy the DS512 link between MS plane 1 and the SDM DS512
personality module you wish to replace by typing
>BSY 1 LINK 0 force
and pressing the Enter key.
Example response:
Request to MAN BUSY MS: 1 shelf: 0 chain:19 link: 0 submitted.
Request to MAN BUSY MS: 1 shelf: 1 chain:19 link: 0 passed.

Note: The state for the DS512 link changes to “M” for MS plane 1.

At the local or remote VT100 console

12 Log in to the SDM as the root or maint user.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-100 SDM hardware replacement procedures

NTRX50GH
DS512 personality module (continued)

13 Access the top menu level of the remote maintenance interface (RMI) by typing
# sdmmtc
and pressing the Enter key.

14 Access the hardware (Hw) menu level of the RMI by typing

>HW
and pressing the Enter key.

15 Manually busy the DS512 controller module by typing

>BSY 0 512 force
and pressing the Enter key.

Example response:
Hardware Bsy – Domain 0 Device 512

Do you wish to proceed?

Please confirm (“YES”, “Y”, “NO”, “N”)

16 Confirm the Bsy command by typing

>Y
and pressing the Enter key.

17 After you confirm the Bsy command, the following is displayed:

Response:
Hardware Bsy : Domain 0 Device 512 – Command initiated.
Please wait...
When the Bsy command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Response:
Hardware Bsy : Domain 0 Device 512 – Command submitted.
Note: At the hardware menu level of the RMI, the state of the DS512 controller
module changes to “M”. The out-of-service LED on the module is on (red).

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-101

NTRX50GH
DS512 personality module (continued)
At the front of the SDM
18
WARNING
Static electricity damage
Wear an electrostatic (ESD) grounding wrist strap
connected to the C28B cabinet when handling a
module. This protects the module against damage
caused by static electricity.

19 Undo the thumbscrews located on the top and bottom of the DS512 controller
module associated with the DS512 personality module you wish to replace.
Note: The thumbscrews are the captive type, and cannot be removed from the
module.

20 Depress the tips of the locking levers on the face of the DS512 controller
module.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-102 SDM hardware replacement procedures

NTRX50GH
DS512 personality module (continued)

21 Open the locking levers on the face of the DS512 controller module by moving
the levers outwards.

At the back of the SDM

22 Loosen the two thumbscrews located at the top and the bottom of the DS512
personality module.
Note: The thumbscrews are the captive type, and cannot be removed from the
module.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-103

NTRX50GH
DS512 personality module (continued)

23
CAUTION
Disconnecting transmit and receive cables
Do not mix the transmit and receive cables for each
domain. If you have not already done so, label these
cables to ensure that you reconnect the cables to the
correct slots. Link 0 transmit and link 0 receive
connect to MS0. Link 1 transmit and link 1 receive
connect to MS1.

Disconnect the four DS512 fiber cables on the DS512 personality module by
pressing the fiber cable in, and turning it a 1/4 turn to the left.

24 While grasping the thumbscrews, gently pull the DS512 personality module
towards you until it protrudes about 2 in. (5.1 cm) from the SDM shelf.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-104 SDM hardware replacement procedures

NTRX50GH
DS512 personality module (continued)

25 Hold the module by the face plate with one hand while supporting the bottom
edge with the other hand. Gently pull the DS512 personality module toward
you until it clears the shelf.

26 Place the DS512 personality module you have removed in an ESD protective
container.

27 Insert the replacement DS512 personality module into the SDM shelf.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-105

NTRX50GH
DS512 personality module (continued)

28 Gently slide the DS512 personality module into the shelf until it is fully inserted.

29 Tighten the thumbscrews at the top and the bottom of the DS512 personality
module.

30
CAUTION
Reconnecting transmit and receive cables
Do not mix the transmit and receive cables for each
domain. Ensure that you reconnect the cables to the
correct slots. Link 0 transmit and link 0 receive
connect to MS0. Link 1 transmit and link 1 receive
connect to MS1.

Reconnect the two DS512 fiber cables on the DS512 personality module by
pressing the fiber cable in, and turning it a 1/4 turn to the right.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-106 SDM hardware replacement procedures

NTRX50GH
DS512 personality module (continued)
At the front of the SDM
31 Close the locking levers to secure the DS512 controller module. Ensure that
both the top and bottom micro switches are lined up with the locking levers to
properly seat the module.

Micro switch

32 Tighten the thumbscrews on the DS512 controller module.

At the local or remote VT100 console

33 At the hardware menu level of the RMI, return the DS512 controller module to
service by typing
>RTS 0 512
and pressing the Enter key.

297-5061-901 Standard 01.01 December 1998

 SDM hardware replacement procedures 5-107

NTRX50GH
DS512 personality module (continued)
Example response:
Hardware RTS : Domain 0 Device 512 – Command initiated.
Please wait...
When the RTS command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Example response:
Hardware RTS : Domain 0 Device 512 – Command submitted.
Note: At the hardware menu level of the RMI, the state of the DS512 controller
module changes to a dot (.), indicating the module has returned to service.
The in-service LED on the DS512 controller module is on (green).

At the MAP display

34 At the MS port module level of the MAP (accessed in step 9), return to service
the DS512 link between MS plane 0 and the DS512 personality module you
replaced by typing
>RTS 0 LINK 0
and pressing the Enter key.
Example response:
Request to RTS MS: 0 shelf: 0 chain:19 link: 0 submitted.
Request to RTS MS: 0 shelf: 0 chain:19 link: 0 passed.
Note: The state for the DS512 link changes to a dot (.) if the SDM DS512 link
is inservice. Otherwise, the state for DS512 link changes to a “P”.
At the MS post module level of the MAP
35 Return to service the DS512 link between MS plane 1 and the DS512
personality module you replaced by typing
>RTS 1 LINK 0
and pressing the Enter key.
Example response:
Request to RTS MS: 1 shelf: 0 chain:19 link: 1 submitted.
Request to RTS MS: 1 shelf: 0 chain:19 link: 1 passed.
Note: The state for the DS512 link changes to a dot (.) if the SDM DS512 link
is inservice. Otherwise, the state for DS512 link changes to a “P”.

Wireless Networks Family SDM–SX User Guide SDMPL011

5-108 SDM hardware replacement procedures

NTRX50GH
DS512 personality module (continued)
(end)
At the SDM MAP level
36 Return the SDM to service by typing
>RTS
and pressing the Enter key.

Response:
SDM RTS initiated.
SDM RTS completed.

The system automatically returns all modules to service.

37 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 6-1

SDM system administration procedures

Introduction to SDM system administration procedures
This chapter contains SDM system administration procedures. Each
procedure contains the following:
• explanatory and context-setting information
• summary flowchart
• step-action instructions

Explanatory and context-setting information

The first page of each procedure contains the following headings:
• Application (why you would perform the procedure)
• Action (how to use the flowchart and step-action instructions)

Summary flowchart
The flowchart is only a summary of the main actions, decision points, and
possible paths you may take. Do not use the summary flowchart to perform
the procedure. Instead, use it to preview what you will be doing and to
prepare for it.

Step-action instructions
The step-action instructions tell you how to perform the procedure.
Normally you will perform the steps in order, but you may be directed to
return to a previous step and repeat a sequence. The successful completion
of a step may depend on previous steps; therefore, always perform the steps
in the order specified.

While following the step-action instructions, you may be sent to other

procedures of this book to perform a set of instructions, or to another NTP
for a related procedure. If this happens, you will be told when to return to
the original instructions, and to which point in those instructions you should
go.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-2 SDM system administration procedures

Return key and Enter key

The carriage return key is identified in different ways (such as Enter, Return
or Carriage Return) on various types of terminals. It is always used to enter
commands and parameters into the system.

The procedures contained in this book and in other NTPs instruct you to
press the Enter key after each step. If your terminal has a Return key, press
the Return key instead. Do not press the Enter key located beside the
numeric key pad.

297-5061-901 Standard 01.01 December 1998

 6-3 SDM system administration procedures 6-3

Changing a user password

Application
Use this procedure to change a user password or to set up a temporary
password for a new user. For more information on password administration,
see page 3-9.

Note: Maintenance users and root users can change their own passwords if
they know their current passwords. The root user can change the password
of any other user on the system at any time without knowing the current
password of the account.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-4 SDM system administration procedures

Changing a user password (continued)

Summary of Changing a user password

This flowchart summarizes the

procedure.

Use the instructions in the

Log in to the procedure that follows this
SDM flowchart to perform the
procedure.

Access the
Admin level of
the RMI

Select User
from the Admin
menu

Change the
password

Change Y
another
password?

End

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-5

Changing a user password (continued)

Changing a user password
At the local or remote VT100 terminal
1 If you are not already logged in to the SDM, log in as either the root user or a
maint user.

2 Proceed according to whether you are logged in as a root or maint user.

If you are a Do

maint user step 3

root user step 11

3 Change your password by typing

>change
Example response:

Changing password for “maint”

maint’s Old password:

Wireless Networks Family SDM–SX User Guide SDMPL011

6-6 SDM system administration procedures

Changing a user password (continued)

4 Enter your old password by typing
>password
and pressing the Enter key.
where
password is your current password

Example response:

Changing password for “maint”

maint’s Old password:
maint’s New password:

5 Enter the new password by typing

>password
and pressing the Enter key.
where
password is a minimum six-character string containing at least one
alphabetic character, and at least one numeric or special
character. Although a password can contain more than eight
characters, only the first eight characters are considered.
Example response:

Changing password for “maint”

maint’s Old password
maint’s New password:
Enter the new password again:

6 If you get an error message, go to step 16.

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-7

Changing a user password (continued)

7 Retype the password and press the Enter key.
Example response:

Changing password for “maint”

maint’s Old password:
maint’s New password:

The system returns you to the User menu. Go to step 15.

8 Access the top menu level of the RMI by typing

# sdmmtc
and pressing the Enter key.

9 Select the administration menu level of the RMI by typing

>3
and pressing the Enter key.

10 Select User by typing

>3
and pressing the Enter key. The User menu is displayed.

11 Change a user password by typing

>change userID
and pressing the Enter key.
where
userID is the userID of the user for whom you are changing the
password

Wireless Networks Family SDM–SX User Guide SDMPL011

6-8 SDM system administration procedures

Changing a user password (continued)

Note: If no userID is specified, the system will change the password of the
current user.
Example response:

Changing password for “root”

root’s New password:

12 Enter the new password by typing

>password
and pressing the Enter key.
where
password is a minimum six-character string containing at least one
alphabetic character, and at least one numeric or special
character. Although a password can contain more than eight
characters, only the first eight characters are considered.
Example response:

Changing password for “root”

root’s New password:
Enter the new password again:

13 Retype the password and press the Enter key. The system returns you to the
User menu.

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-9

Changing
Changing a user
a user password
password (end)
(continued)

Example response:

Changing password for “root”

root’s New password:
Enter the new password again:
...
Please press ’Enter’ when ready...

Note: If the root user changes a maint user’s password, the change is
temporary. The maint user will be asked to change the password again at the
next login.
The system returns you to the User menu.

14 Determine if you want to change another password.

If you Do

want to change another password step 11

do not want to change another step 15
password

15 Exit the RMI by typing

>QUIT ALL
and pressing the Enter key. Go to Step 17.

16 Contact your next level of support.

17 You have completed this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-10 SDM system administration procedures 6-10

Adding or removing a maintenance user

Application
Use this procedure to add or remove a maintenance class user. This
procedure must be performed by the root user.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-11

Adding or removing a maintenance user (continued)

Summary of Adding or removing a maintenance user

This flowchart summarizes the

procedure.
Log in to the
SDM as the Use the instructions that follow
root user this flowchart to perform the
procedure.

Access the
Admin level of
the RMI

Select User
from the Admin
menu

Y Add a user to
Add a user? the system 1

Change Y Change the

pass- password for 1
word? the new user
N

Y Remove a user
Remove a user? from the system 1

N
End

Wireless Networks Family SDM–SX User Guide SDMPL011

6-12 SDM system administration procedures

Adding or removing a maintenance user (continued)

Adding or removing a maintenance user
At the local or remote VT100 console
1 Log in to the SDM as the root user.

2 Access the top menu level of the Remote Maintenance Interface (RMI) by
typing
# sdmmtc
and pressing the Enter key. The top menu level of the RMI is displayed.

3 Select the administration (Admin) menu level of the RMI by typing

>3
and pressing the Enter key.

4 Select User by typing

>3
and pressing the Enter key. The User menu is displayed.
Example response:

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
I S . I I . SDM: SDM1

User SDM USERS

0 Quit
2
3 Administrative users:
4 1 root
5
6 Maintenance users:
7 1 maint
8 2 maint1
9 3 randy
10 4 auto1
11
12
13
14
15 Maintenance Users: 1 to 4 of 4
16
17 Help
18 Refresh

root
Time 19:48 >

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-13

Adding or removing a maintenance user (continued)

5 Determine whether you want to add, remove, or change the password of a
user.

If you want to Do

add a user step 6

change a user password step 8
remove a user step 12

6 Add a maintenance user by typing

add: userID
where
userID is the userID of the new user
and pressing the Enter key.
Example response:

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
I S . I I . SDM: SDM1

User SDM USERS

0 Quit
2
3 Administrative users:
4 1 root
5
6 Maintenance users:
7 1 maint
8 2 maint1
9 3 randy
10 4 auto1
11
12
13
14
15 Maintenance Users: 1 to 4 of 4
16
17 Help
18 Refresh

root
Time 19:48 >add smith

Wireless Networks Family SDM–SX User Guide SDMPL011

6-14 SDM system administration procedures

Adding or removing a maintenance user (continued)

The User menu immediately displays the new userID. (In the example below,
the userID Smith was added.
Note: To activate a user, you need to set the password. Use the change
command to set the password.
Example response:

SDM Remote Maintenance Interface

SDM CON LAN APPL SYS HW CM : FCC1
I S . I I . SDM: SDM1

User SDM USERS

0 Quit
2
3 Administrative users:
4 1 root
5
6 Maintenance users:
7 1 maint
8 2 maint1
9 3 randy
10 4 auto1
11 5 smith
12
13 To activate the account for ’smith’,
14 use the CHANGE command to set the password.
15
16 Maintenance Users: 1 to 5 of 5
17 Help
18 Refresh

root
Time 19:48 >

7 Determine whether you want to activate the user or add another user.

If you Do

want to activate the user step 8

want to add another user step 6
do not want to add another user step 17

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-15

Adding or removing a maintenance user (continued)

8 Set or change a password for the user by typing
change userID
and pressing the Enter key.
where
userID is the userID of the user for whom you are changing the
password
Note: If no userID is specified, the system will change the password of the root
user.
Example response:

Changing password for “smith”

smith’s New password:

9 Enter the new password by typing

password
and pressing the Enter key.
where
password is a minimum six-character string containing at least one
alphabetic character, and at least one numeric or special
character. Although a password can contain more than eight
characters, only the first eight characters are considered.

Example response:

Changing password for “Smith”

Smith’s New password:
Enter the new password again:

Wireless Networks Family SDM–SX User Guide SDMPL011

6-16 SDM system administration procedures

Adding or removing a maintenance user (continued)

10 Retype the password and press enter. The system returns you to the User
menu.

Changing password for “Smith”

Smith’s New password:
Enter the new password again:

The system returns you to the User menu.

11 Determine if you want to change another userID password.

If you Do

want to change another password step 8

do not want to change another step 17
password

12 Remove a user by typing

delete userID
and pressing the Enter key.
where
userID is the userID of the user you are deleting
The system immediately deletes the userID and redisplays the User menu. (In
the example following, the userID Smith was added.)
Response:
Are you sure you want to delete this user?
Do you wish to proceed?
Please confirm (”YES”, ”Y”, ”NO”, or ”N”):

13 Decide if you really want to delete the user.

If you Do

want to delete the user step 14

do not want to delete the user step 15

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-17

Adding
Adding or removing
or removing a maintenance
a maintenance user user (end)
(continued)

14 Confirm that you want to delete the user by typing

>Y
and pressing the Enter key.
Go to step 16.

15 Confirm that you do not want to delete the user by typing

>N
and pressing the Enter key.

16 Determine if you want to remove another user from the system.

If you Do

want to remove another user step 12

do not want to remove another user step 17

17 Exit the RMI by typing

>QUIT ALL
and pressing the Enter key.

18 You have completed this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-18 SDM system administration procedures 6-18

Setting the time zone, date and time

Application

ATTENTION
This procedure must be performed only by UNIX system
administration personnel who have root user permissions for accessing
the SDM.

ATTENTION
The time zone, date and time on the SDM cannot be changed when
DCE is operational. The SDM must also be in ManB or OffL state to
change the time zone, date and time.

Use this procedure to set the time zone, and date and time on the SDM.
Once you have entered the new time zone, and the date and time, the values
are recalculated from the system clock and displayed on the screen to
confirm the change.

The SDM must be rebooted after changing the time zone, date and time.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-19

Setting the time zone, date and time (continued)

Summary of Setting the time zone, date and time

This flowchart summarizes the

Manually busy
procedure.
the SDM at the
MAP display
Use the instructions in the
procedure that follows this
flowchart to perform the
Log in to the procedure.
SDM as root
user

Access the
Admin level of
the RMI

Select the
Time option

Change the
time zone

Change the
date and time

Reboot the
SDM at the
MAP display

Return the End

SDM to service

Wireless Networks Family SDM–SX User Guide SDMPL011

6-20 SDM system administration procedures

Setting the time zone, date and time (continued)

Setting the time zone, date and time
At the MAP display
1 Access the SDM from the APPL level of the MAP display by typing
>MAPCI; MTC;APPL;SDM
and pressing the Enter key.

2 Determine the SDM node state.

If the SDM node state is Do

in service (InSv) step 4

anything else step 3

3 A fault exists on the SDM, or another SDM maintenance activity is already in

progress. Clear the fault or complete the maintenance activity, as appropriate.
Clear the faults by checking for SDM-related alarms under the APPL header of
the MAP display alarm banner, and use the appropriate alarm clearing
procedure in the “SDM maintenance procedures” chapter of this document to
clear the fault before continuing this procedure.
Go to step 2.

4
CAUTION
Loss of service
Manually busying the SDM shuts down all
applications without warning to the application users.

Manually busy the SDM by typing

>BSY
and pressing the Enter key.
Response:
SDM is in service.
This command will cause a service interruption.
Do you wish to proceed?
Please confirm (“YES”, “Y”, “NO”, “N”)

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-21

Setting the time zone, date and time (continued)

5 Confirm the Bsy command by typing
>Y
and pressing the Enter key.
Response:
SDM Bsy initiated.
SDM Bsy completed.
At the local or remote VT100 terminal
6 Log in to the SDM as the root user.

7 Access the top menu level of the RMI by typing

# sdmmtc
and pressing the Enter key.

8 Select the administration (Admin) menu level of the RMI by typing

>3
and pressing the Enter key.

9 Select Time by typing

>2
and pressing the Enter key. The SDM Remote Maintenance Interface is
displayed. Press the Enter key again. The Use Daylight Savings Time screen is
displayed.
Response:

Use DAYLIGHT SAVINGS TIME?

Move cursor to desired item and press Enter.

# Does this time zone go on

# DAYLIGHT SAVINGS TIME?
#
1 yes
2 no

F1=Help F2=Refresh F3=Cancel

F8=Image F10=Exit Enter=Do
/=Find n=Find Next

10 Use the arrow key to select “yes” (option 1) to the question, “Does this time
zone go on daylight savings time?” if at some time in the year daylight savings
time will be applied to this time zone. Otherwise, select “no” (option 2). Press
the Enter key when you have selected the appropriate response.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-22 SDM system administration procedures

Setting the time zone, date and time (continued)

11 The CUT (Coordinated Universal Time) Time Zone screen is displayed. Use
the up and down arrows to choose the appropriate time zone, and then press
the Enter key.
Note: All time zones do not fit on a single screen display. Use the up and
down arrow keys to view the rest of the time zones.
Response:

CUT (Coordinated Universal Time) Time Zone

Move cursor to desired item and press Enter.

[TOP]
(CUTOGDT) Coordinated Universal Time (CUT)
(GMTOBST) United Kingdom (CUT)
(AZOREST1AZOREDT) Azores; Cape Verde (CUT -1)
(FALKST2FALKDT0 Falkland Islands (CUT -2)
(GRNLNDST3GRNLNDDT) Greenland; East Brazil (CUT -3)
(AST4ADT) Central Brazil (CUT -4)
(EST5EDT) Eastern U.S.; Colombia (CUT -5)
(CST6CT) Central U.S.; Honduras (CUT -6)
(MST7MDT) Mountain U.S. (CUT -7)
(PST8PDT) Pacific U.S.; Yukon (CUT -8)
[MORE...19]

F1=Help F2=Refresh F3=Cancel

F8=Image F10=Exit Enter=Do
/=Find n=Find Next

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-23

Setting the time zone, date and time (continued)

12 The Change / Show Date, Time, & Time Zone screen is displayed. Use the up
and down arrows to move the cursor to a date or time entry you want to
change. Repeat until you modify all the entries you want to change. Press the
Enter key.
Example response:

Change / Show Date, Time, & Time Zone

Type or select values in entry fields.

Press Enter AFTER making all desired changes.

[Entry Fields]
Old time zone EST5EDT
Time zone [CUT0GDT]
Does this time zone go on daylight savings time? yes

* YEAR (00-99) [97] #

* MONTH (01-12) [02] #
* DAY (01-31) [26] #

* HOUR (00-23) [21] #

* MINUTES (00-59) [18] #
* SECONDS (00-59) [00] #

F1=Help F2=Refresh F3=Cancel F4=List

F5=Reset F6=Command F7=Edit F8=Image
F9=Shell F10=Exit Enter=Do

Special attention is required when you use the screen in the preceding example
response. The default offset for daylight savings time change is set according
to the rule in North America. According to this rule, the move from standard
time to daylight savings time occurs on the first Sunday of April. That is, clock
time is moved forward one hour. The move from daylight savings time to
standard time occurs on the last Sunday of October. That is, clock time is
moved backward one hour.
If you are outside of North America, you need to manually set the time zone. In
the time zone window, select a time zone and enter the date and time values.
Manually add the offset variable.

For example, change the selected time zone “NFT-1DFT” for Norway and
France to “NFT-1DFT,M3.5.0,M10.4.0/2:00”.
Note 1: The offset variable “M3.5.0,M10.4.0/2:00” added to the time zone
means the following:
• time changes forward at 2 a.m. on Sunday of the fifth week of March.
• time changes backward at 2 a.m. on Sunday of the fourth week of October.

Note 2: The time indicated in Note 1 is only an example. Check with

appropriate personnel for the hour that daylight savings time occurs.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-24 SDM system administration procedures

Setting the time zone, date and time (continued)

13 The Command Status screen is displayed. The command status is shown as
“running” while the changes are being processed. The command status
changes to “OK” when processing is complete. The date, time and time zone
are displayed.
Example response:

COMMAND STATUS

Command: OK stdout: yes stderr: no

Before command completion, additional instructions may appear below.

Wed Feb 26 21:18:00 CUT 1997

Any changes made to the time zone will take effect at your next login
session.

F1=Help F2=Refresh F3=Cancel

F8=Image F10=Exit Enter=Do
/=Find n=Find Next

14 Exit the command status screen by pressing the F3 key.

At the SDM level of the MAP display

15 Reboot the SDM by typing
>REBOOTSDM
and pressing the Enter key.
Response:
Communication with the SDM will be down for approximately
10 minutes.

Do you wish to proceed?

Please confirm (“YES”, “Y”, “NO”, or “NO”):

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-25

Setting
Setting the time
the time zone,zone,
date date and time
and time (end)
(continued)

16 Confirm that you want to proceed by typing

>Y
and pressing the Enter key.
Response:
SDM 0 ManB Links_00S: .
/ RebootSDM in progress
SDM 0 RebootSDM initiated.
Note: The command response indicates that the command has been
successfully received by the SDM. The maintenance flag, “Reboot SDM in
progress” is displayed until the SDM recovers from the reboot. When the
maintenance flag message disappears, continue with the next step.

17 Return the SDM to service by typing

>RTS
and pressing the Enter key.
Response:
SDM InSv Links_00S: .

SDM RTS initiated.

SDM RTS completed.

Note: If there are no other faults on the system, then the SDM applications
automatically return to service immediately following the completion of the
reboot.

18 You have completed this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-26 SDM system administration procedures 6-26

Creating SDM backup tapes

System image backup (S-tape)

Application

ATTENTION
This procedure must be performed by a trained AIX system
administrator with root user privileges to access the SDM.

ATTENTION
The files under the /data file system are excluded from system image
backup. The files under the /data file system are temporary files that
do not require backing up.

Use this procedure to create a system image backup tape (S-tape). The
system image includes the following:
• boot (startup) files
• AIX operating system
• system configuration data
• SDM software

Nortel (Northern Telecom) recommends that you perform a system image

backup after the following:
• initial installation and commissioning of the SDM
• changes to the configuration of disks or logical volumes
• installation of a new version of SDM platform software

A system image backup takes a minimum of 10 min to complete, depending

on the size of your file systems.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-27

Creating SDM backup tapes

System image backup (S-tape) (continued)
Summary of System image backup

This flowchart summarizes the

procedure.

Use the instructions that follow

this flowchart to perform the
Log in to the procedure.
SDM as the
root user

Access the 2 3
online backup
Exit the RMI List the
utility
contents of the
S-tape

Insert the DAT

tape View the Insert the DAT
s-tape.log file tape

Perform the
system image 1 1
backup

N Contact your
Successful? next level of
support
Y

N N Remove and End

View s-tape.log List the S-tape? label the
file? S-tape
Y Y
2 3

Wireless Networks Family SDM–SX User Guide SDMPL011

6-28 SDM system administration procedures

Creating SDM backup tapes

System image backup (S-tape) (continued)
System image backup
At the local or remote VT100 console
1 Log in to the SDM as the root user.

2 Access the RMI by typing

# sdmmtc
and pressing the Enter key.

3 Access the administration (Admin) menu level of the RMI by typing

>ADMIN
and pressing the Enter key.

4 Access the Backup and Restore Main Menu by typing

>5
and pressing the Enter key.
Note: If another person attempts to use the Backup and Restore utility when it
is in use, an error message is displayed.
Example response:
Currently there is a backup running on bnode73.
Please execute yours later.
Exiting . . .

5 From the Backup and Restore Main Menu, select “System Image Backup and
Restore” by typing
>2
and pressing the Enter key.
Note: If disk mirroring for all volume groups is not Mirrored, an error message
is displayed. You are prompted to return to the System Image Backup and
Restore Main Menu.

6 From the System Image Backup and Restore Menu, select “Create a System
Image on Tape (S-tape)” by typing
>2
and pressing the Enter key.

7 You are prompted to insert a tape in the drive you have selected.
Example response:
Please insert a 4mm DAT tape into the tape drive DAT0.

Caution:
This action will overwrite the contents of the inserted tape.
Do you want to proceed? ( y | n )
==>

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-29

Creating SDM backup tapes

System image backup (S-tape) (continued)

At the SDM
8 Ensure that the appropriate SDM tape drive contains a 4-mm digital audio tape
(DAT) either 90 m or 120 m long. This tape will be designated as the system
image backup tape (S-tape).

At the local or remote console

9 When you are certain you are using the correct tape, type
>y
and press the Enter key.

10 Read the system message to determine if there is enough room on the

temporary directory for the system image backup to proceed.
Note: If there is not enough room on the temporary directory, an error
message appears.
Example response:
Rewinding the tape...

The /tmp directory is not big enough.

Trying to expand /tmp by 6600KB...

Failed to expand the /tmp directory

because there isn’t enough free disk space left on the rootvg.

Please erase some files under /tmp directory to create at least 6600KB
for the full system image backup.

Enter any key and return to exit ==>

If there is Do

enough disk space step 13

not enough disk space step 11

11 Erase enough files from the temporary directory to create the required amount
of disk space specified in the error message by typing
>rm –rf /tmp/*
and press the Enter key.
Note: If you have trouble erasing files from the temporary directory to free up
disk space, contact the personnel responsible for your next level of support.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-30 SDM system administration procedures

Creating SDM backup tapes

System image backup (S-tape) (continued)

12 Execute the system image backup again.

13 The system image backup begins.

Note: This backup process takes approximately 10 min to complete,
depending on the amount of data stored on the disk.
Example response:
Rewinding the tape...

Starting the system image backup on bnode73.

The backup takes a minimum of 10 minutes,

depending on the size of your file systems.

When the backup is complete, you will be asked

to remove the tape from the tape drive.

System image backup is in progress ...

14 Read the system message.

If the backup Do

is successfully completed step 15

fails step 38

15 The system informs you if the backup is successful. When the backup is
complete, the system also prompts you to remove the tape and label it as an
S-tape.
Example response:
The tape backup started on Wed Oct 16 08:21:15 EDT 1997
completed successfully on Wed Oct 16 08:37:37 EDT 1997.
A log file /tmp/s-tape.log has been created.

Please remove the backup tape from the tape drive.

Label the tape as shown below and store it in a safe place.

System Image Tape (S-tape)

The Machine Node Id: bnode73
Date: Wed Oct 16 08:37:37 EDT 1997

Eject the S-tape from the tape drive? ( y | n )

==>

16 Determine if you wish to eject the S-tape. Type “y” to eject the tape, and “n” if
you do not wish to eject the tape.

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-31

Creating SDM backup tapes

System image backup (S-tape) (continued)
Note: If you wish to list the contents of the tape, do not eject the tape. Go to
step 29.
If you eject the tape, the screen displays “Tape ejected.” below the information
displayed in step 15. You are then prompted to return to the System Image
Backup and Restore Main Menu.
Response:
Tape ejected.

Would you like to return to the previous menu? ( y | n)

Nortel recommends that you place the write-protect tab of the S-tape in the
open position, to prevent accidental erasing.

17 When you are ready for the system to return to the System Image Backup and
Restore Main Menu, type
>y
and press the Enter key.

18 Determine if the backup is successful. The system informs you if the system
image backup is successful, as shown in the response in step 15. You may
also wish to view the s-tape.log file or list the files on the S-tape.

If Do

you wish to view the s-tape.log file step 19

you wish to list the S-tape step 28
the backup is successful step 35
the backup fails step 38

Wireless Networks Family SDM–SX User Guide SDMPL011

6-32 SDM system administration procedures

Creating SDM backup tapes

System image backup (S-tape) (continued)

19 Exit the System Image Backup and Restore Main Menu by typing
>0
and pressing the Enter key.

20 Exit the RMI by typing

>QUIT ALL
and pressing the Enter key.

21 Access the s-tape.log file by typing

# cd /tmp
at the prompt and pressing the Enter key.

22 Scroll through the file by typing

# more s–tape.log
and pressing the Enter key. This screen informs you that the system image
backup was completed successfully.
Example response:
bosboot: Boot image is 5881 512 byte blocks.
0+1 records in.
1+0 records out.

Backing up the system...

...................................................................
....
0512 038 mksysb: Backup Completed Successfully.

The S-tape backup started on Wed Oct 16 09:24:07 EDT 1997

completed successfully on Wed Oct 16 09:36:03 EDT 1997

23 Determine if you wish to list the S-tape.

If you Do

wish to list the S-tape step 24

do not wish to list the S-tape step 39

24 Return to the login directory by typing

# cd
and pressing the Enter key.

25 Access the RMI by typing

# sdmmtc
and pressing the Enter key.

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-33

Creating SDM backup tapes

System image backup (S-tape) (continued)

26 Access the administration (Admin) menu level of the RMI by typing

>ADMIN
and pressing the Enter key.

27 Access the Backup and Restore Main Menu by typing

>5
and pressing the Enter key.

28 From the Backup and Restore Main Menu, select “System Image Backup and
Restore” by typing
>2
and pressing the Enter key.

29 From the System Image Backup and Restore Menu, select “List Contents of the
System Image Tape (S-tape)” by typing
>3
and pressing the Enter key.

30 You are prompted to insert the S-tape into the tape drive DAT0.
Example response:
Please insert your System Image Backup tape (S-tape) into
the tape drive DAT0 and allow at least 5 minutes to
complete the listing.

A log file will be saved in /tmp/s-tape.toc.

Are you ready to proceed? ( y | n )

At the SDM
31 Insert the S-tape into the tape drive you selected.

At the local or remote VT100 terminal

32 When you are ready to continue this procedure, type
>y
and press the Enter key.

33 The contents of the S-tape are displayed. When the listing is complete, the
system prompts you to return to the System Image Backup and Restore Menu.
Response:
Would you like to return to the previous menu? ( y | n )

Wireless Networks Family SDM–SX User Guide SDMPL011

6-34 SDM system administration procedures

Creating SDM backup tapes

System image backup (S-tape) (continued)
(end)

34 Return to the System Image Backup and Restore Menu, by typing

>y
and pressing the Enter key.

At the SDM
35 If you have not already done so, remove the S-tape from the tape drive by
pressing the eject button on the tape drive. Label the tape according to your
office procedures, and store it in a safe location.

At the local or remote VT100 terminal

36 Exit the System Image Backup and Restore Menu, by typing
>0
and pressing the Enter key.

37 Exit the Backup and Restore Main Menu, by typing

>0
and pressing the Enter key.
Note: If you wish to exit the RMI, type QUIT ALL and press the Enter key.
Go to step 39.

38 Contact the personnel responsible for the next level of support.

39 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 6-35 SDM system administration procedures 6-35

Restoring the SDM

Full restore from S-tape

Application

ATTENTION
This procedure must be performed by a trained AIX system
administrator who has root user privileges to access the SDM.

Use this procedure to perform a full restore of the SDM software load from
the system image backup tape (S-tape). A full software restore is required
when the SDM is out of service because the software load has become
corrupted.

This procedure must be performed by the root user from a local VT100
console as shown in the following figure.

SDM site
SDM

Console
port
VT100 terminal

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the recovery task.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-36 SDM system administration procedures

Restoring the SDM

Full restore from S-tape (continued)
Summary of Full restore from S-tape

1
This flowchart summarizes the
Insert the Reboot the procedure.
S-tape SDM
Use the instructions that follow
this flowchart to perform the
procedure.
Boot the SDM Check the DCE
and disrupt boot state at the RMI
procedure

Enter system Check the

diagnostics application(s)
mode state

Change the Perform DCE

settings, if procedures, as
required required

Restore the Perform

system image datavg restore,
from S-tape if required

Remove the Create a new

S-tape system image
backup tape

Log in to the
SDM as the End
root user

Access the Access the

backup and backup and 1
restore utility restore utility

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-37

Restoring the SDM

Full restore from S-tape (continued)
Full restore from S-tape
At the SDM
1 Ensure that the SDM tape drives (slot 2 or 13 in the main chassis) contains the
system image backup tape (S-tape).

At the MSP
2 Boot the SDM by turning the power off, then on, using the MSP breaker that
supplies power to the SDM.

At the local VT100 console

3 When the system displays “COLD start...”, press the Break key or the Esc key
twice to interrupt the boot process. The system takes about 4 min to initialize.

4 Proceed, depending on the prompt that is displayed on the screen.

If the prompt is Do

FX-Bug step 7
FX-Bug and you are in a menu step 5
FX-Diag step 6

5 From the selection menu, select “Go to System Debugger”, by typing

>3
and pressing the Enter key.
Go to step 7.

6 Switch the directory to FX-Bug, by typing

>sd
and pressing the Enter key.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-38 SDM system administration procedures

Restoring the SDM

Full restore from S-tape (continued)

7 View the input/output devices on the SDM to verify the address of the tape drive
from the FX-Bug prompt. Type
Fx-Bug>ioi
and press the Enter key.
Example response:
CLUN DLUN CNTRL-TYPE DADDR DTYPE RM Inquiry–Data
1 0 IO 0 $00 N SEAGATE ST11200N ST 31200 0660
3 0 IO 0 $00 N SEAGATE ST12400N ST32430 0660
1 50 IO 5 $01 Y ARCHIVE Python 28388-XXX 5.45

Note: In the example response, the tape drive is ARCHIVE.

Wait for the FX-Bug prompt, and then type
Fx-Bug>pboot <address for Archive Python>
and press the Enter key.
In the example, the following are valid choices:
• pboot 1 50 if the tape drive is located in slot 2
8 Wait about 4 min after the pboot command is entered. You are then asked to
define the console setting and the language setting. To define the console
setting, select option 1 and press the Enter key.
Note: When you define the console setting, the “1” is not echoed on the
screen.
Type1 to select the language setting, and press the Enter key. The Welcome to
Base Operating System Installation and Maintenance menu is then displayed.

9 Select “Change/Show Installation Settings and Install” by typing

>2
and pressing the Enter key. The System Backup Installation and Settings menu
is displayed.
Example response:
System Backup Installation and Settings

Either type 0 and press Enter to install with the current settings, or
type the number of the setting you want to change and press Enter.

Setting: Current Choice(s):

1 Disk(s) where you want to install hdisk0...
Use Maps No
2 Shrink File System No

>>> 0 Install with the settings listed above.

Note: “...” shown under Current Choice(s) indicates that more than one disk is
currently in use.

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-39

Restoring the SDM

Full restore from S-tape (continued)

10 The default disk for the installation is hdisk0, located in slot 2 of the main
chassis. If your SDM contains one disk drive in each domain of the main
chassis, accept the default setting. If you have additional disk drives, you may
wish to change the settings.

To Do

change the current settings step 11

use the current settings step 14

11 To change the disks where you want to install the backup image, type
>1
and press the Enter key.
The Change Disk(s) Where You Want to Install menu is displayed.
Example response:
Change Disk(s) Where You Want to Install

Type one or more numbers for the disk(s) to be used for installation and
press Enter. To cancel a choice, type the corresponding number and Press
Enter. At least one bootable disk must be selected. The current choice
is indicated by >>>.

Name Location Code Size(MB) VG Status Bootable Maps

This menu displays the list of all available disks on which you can install the
system backup image. The currently selected disks are indicated by >>>.

12 To select a disk or disks, enter the number of the disk, and press the Enter key.
To deselect a selected disk, enter its number again and press the Enter key.

13 When you have finished entering the settings, the System Backup Installation
and Settings menu is displayed. Type
>0
and press the Enter key.

Go to step 10.

14 To accept the current settings type

>0
and press the Enter key.

15 The restore process begins, and lasts at least 30 min. During the restore
process, the screen displays the approximate percentage of tasks completed,
and the elapsed time.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-40 SDM system administration procedures

Restoring the SDM

Full restore from S-tape (continued)
Note: As part of the restore, the system reboots automatically and displays the
login prompt.

At the SDM
16 Remove the S-tape from the tape drive when the reboot is completed and store
it in a secure location.
At the local or remote terminal
17 Log in to the SDM as the root user. Press the Enter key when you see the
“TERM=(vt100)” prompt.

18 Access the remote maintenance interface (RMI) by typing

# sdmmtc
and pressing the Enter key.

19 Access the system (Sys) menu level by typing

>SYS
and pressing the Enter key.

20 Access the storage menu level by typing

>5
and pressing the Enter key.
Example response:
Disk mirroring (rootvg): Mirrored
Volume Size(MB) (% full/ threshold)
1 / 20 25/ 80
2 /usr 192 85/ 90
3 /var 40 17/ 80
4 /tmp 20 11/ 90
5 /home 300 27/ 70
6 /sdm 192 65/ 90
(unallocated) 972

21 Log in to the SDM as the root user. Press the Enter key when you see the
“TERM=(vt100)” prompt.

22 Access the RMI by typing

# sdmmtc
and pressing the Enter key. The top menu level of the RMI is displayed.

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-41

Restoring the SDM

Full restore from S-tape (continued)

23 Access the LAN menu level of the RMI by typing

>LAN
and pressing the Enter key.
Check the state of DCE.
Example response:
DCE State: SysB

24 Access the application (APPL) menu level of the RMI to check the state of any
DCE-based applications. Type
>APPL
and press the Enter key.
Example response:
# Package Description Version State
1 Table Access Service 10.0.29.0 InSv
2 Operation Measurements 10.0.29.0 InSv
3 Log Delivery Service 10.0.29.0 InSv

25 DCE and DCE-based applications may fail if the keytab files restored from tape
contain obsolete keys. If the DCE state is displayed as SysB at the LAN menu
level of the RMI (step 23), and the logs displayed indicate an error with the
security client service in DCE, restore the service by performing the following
procedures described in the “SDM system administration procedures” chapter
of this document:
• ”Distributed Computing Environment-Removing an SDM from a DCE cell”
on page 6-74
• ”Distributed Computing Environment-Configuring an SDM in a DCE cell” on
page 6-61
If some DCE-based applications are faulty (Fail state, see step 24), restore
them by executing the procedure to add the application server to the DCE cell.
This procedure is documented in the NTP for each specific application.

26 Proceed depending on if your system includes the data volume group (datavg).

If your system Do

has datavg step 27

does not have datavg step 34

Note: Datavg is shown at the storage menu level of the RMI.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-42 SDM system administration procedures

Restoring the SDM

Full restore from S-tape (continued)
(end)

27 Exit the RMI by typing

>QUIT ALL
and pressing the Enter key.
Identify the ID of the small computer systems interface (SCSI) to the hard disk
number, by typing

28 Identify the ID of the small computer systems interface (SCSI) to the hard disk
number, by typing
# lsdev -Cc disk
and pressing the Enter key.

29 Identify the disks that are part of the root volume group (rootvg) and datavg, by
typing
# lspv
and pressing the Enter key.

30 For each volume group, run the hard disk number by typing
# importvg -y datavg hdisk#
and pressing the Enter key.
Note: The hdisk# is any disk that does not belong to rootvg, but used to belong
to datavg.

31 For each volume group other than rootvg, type

# varyonvg volume group
and press the Enter key.
where
volume group is rootvg or datavg
32 Synchronize the object data manager (ODM) and mount all file systems on
reboot, by typing
# shutdown -Fr
and pressing the Enter key.

33 You must create a new system image backup tape. Refer to the procedure
”Creating SDM backup tapes– System image backup tape (S-tape)” on page
6-26 in this document.

34 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 6-43 SDM system administration procedures 6-43

Changing the root user password when it is not known

Application
Use this procedure to change the root user password when it is not known.
If the ETA application is installed and in service, use that application to open
a root user session. Then, use the procedure “Changing a user password”
session to change the root password.

Action
The following flowchart summarizes the procedure. Use the instructions in
the step-action procedure that follows the flowchart to perform the task.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-44 SDM system administration procedures

Changing the root user password when it is not known

(continued)

Summary for Recovering a system when the root password is unknown

Busy and take This flowchart summarizes the

the SDM procedure.
off-line
Use the instructions in the
procedure that follows this
Insert the flowchart to perform the
s-tape into the procedure.
DAT drive

Break the boot

process

Select the
correct options
from screens

Type the new

password and
confirm

Remove the
s-tape

Reboot the
system

End

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-45

Changing the root user password when it is not known

(continued)

Recovering a system when the root password is unknown

At the SDM level of the MAP display
1 Manually busy the SDM by typing
>BSY
and pressing the Enter key. You are prompted to confirm whether you want to
busy the SDM.

2 Confirm that you want to manually busy the SDM by typing

>Y
and pressing the Enter key.

3 Take the SDM off-line by typing

>OFFL
and pressing the Enter key.
At the local console
4 Insert the latest system backup tape (s-tape) into DAT drive (0) (slot 2).

5 Power down the SDM.

6 Restore power to the SDM to initiate booting.

7 Wait until the console shows that the system has started to boot.
Example output:
Selftest/Boots about to Begin... Press <BREAK> at anytime
to Abort ALL

Wireless Networks Family SDM–SX User Guide SDMPL011

6-46 SDM system administration procedures

Changing the root user password when it is not known

(continued)

Press the Break key to exit the boot process.

8 From the Fx-Bug prompt type

Fx-Bug>pboot 1 50
and press the Enter key. The system displays various messages. When they
are completed, proceed to the next step.

9 At the Please define the system console screen, type

>1
and press the Enter key.

10 At the second interactive screen, select 1 for English.

11 At the Welcome to base operating system installation and maintenance screen,

select 3 to begin the maintenance mode for system recovery.

12 At the Maintenance screen, select 1 to access a root volume group.

13 At the Warning screen, select 0.

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-47

Changing the root user password when it is not known

(continued)

14 The Access a root volume group screen displays the volume groups with the
disks they contain. Each disk has a name, (for example, hdisk0) and a location
code (for example 4056 c1–f2–00–0,0).
Type the number of the volume group whose location code contains the
characters “c1–f2”. Press the Enter key.
Example output:
1) Volume Group 002e43cdaa6655f5 contains these disks:
hdisk1 4056 c1-f4-00-0,0 hdisk2 4056 c1-f4-00-1,0
hdisk3 4056 c1-f4-00-0,0 hdisk4 4056c1-f15-00-1,0
2) Volume Group 002e43cda6d92fc7 contains these disks:
hdisk0 4056 c1-f2-00-0,0 hdisk3 4056c1-f13-00-0,0
15 At the Volume group information screen, select 1 to access the volume group
and start a shell.

16 At the shell prompt type

# passwd root
and press the Enter key. The system prompts you for a new root password.

17 Type the new root password. When prompted, re-enter the new root password.

18 Confirm the password change by typing

# ls –l /etc/passwd
and pressing the Enter key.
Example output:
–rw–r––r–– 1 root root 11539 Jul 9 12:37 /etc/passwd
19 Check that the date and time that are displayed as a result of step 18 are the
current date and time.

If the current date and time Do

are displayed step 20

are not displayed step 22

Wireless Networks Family SDM–SX User Guide SDMPL011

6-48 SDM system administration procedures

Changing the root user password when it is not known

(continued)
(end)

20 Remove the s-tape.

21 Reboot the system by typing

#shutdown –Fr
and pressing the Enter key. When the reboot completes, the login prompt
appears. You must then use the new password to log in as the root user.

22 Contact your next level of support.

23 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 6-49 SDM system administration procedures 6-49

Restoring the SDM

Partial restore from the system image tape (S-tape)

Application

ATTENTION
This procedure must be performed by a trained AIX system
administrator who has root user privileges to access the SDM.

CAUTION
Possible loss of data
Use this procedure at the discretion of the system
administrator. Perform a partial restore only if you are
familiar with the files, and know exactly which files are to
be restored. If you restore the wrong files, you may
inadvertently corrupt SDM software.

Use this procedure to restore individual files or sets of files from the system
image backup tape (S-tape). This procedure can be performed by the root
user from a local or remote terminal.
Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the recovery task.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-50 SDM system administration procedures

Restoring the SDM

Partial restore from the system image tape (S-tape) (continued)
Summary of Partial restore from the system image tape (S-tape)

Log in to the This flowchart summarizes the

SDM as the procedure.
root user
Use the instructions that follow
this flowchart to perform the
procedure.

3
2
Access the
backup and List the
Exit the RMI contents of the
restore utility
S-tape

List the contents

of the S-tape, if View the Insert the DAT
required s-tape.restore tape
file

Restore files or 1
1
directories as
appropriate

N Contact your
Successful? next level of
support
Y

View the N N Remove the End

List the
s-tape.restore S-tape
S-tape?
file?
Y Y
2 3

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-51

Restoring the SDM

Partial restore from the system image tape (S-tape) (continued)
Partial restore from the system image tape (S-tape)
At the local or remote console
1 Log in to the SDM as the root user.

2 Access the RMI by typing

# sdmmtc
and pressing the Enter key.

3 Access the system (Sys) menu level by typing

>SYS
and pressing the Enter key.

4 Access the storage menu level by typing

>5
and pressing the Enter key.
Example response:
Volume Size(MB) (% full/ threshold)
1 / 20 25/ 80
2 /usr 192 85/ 90
3 /var 40 17/ 80
4 /tmp 20 11/ 90
5 /home 300 27/ 70
6 /sdm 192 65/ 90
(unallocated) 972

Volume Size(MB) (% full/ threshold)

7 /data 112 4/ 80
(unallocated) 8000

Wireless Networks Family SDM–SX User Guide SDMPL011

6-52 SDM system administration procedures

Restoring the SDM

Partial restore from the system image tape (S-tape) (continued)

5 Access the administration (Admin) menu level of the RMI by typing

>ADMIN
and pressing the Enter key.

6 Access the Backup and Restore Main Menu by typing

>5
and pressing the Enter key.
Note: If another person attempts to use the backup and restore utility when it is
in use, an error message is displayed on the screen.
Example response:
Currently there is a backup running on bnode73.
Please execute yours later.
Exiting . . .

and pressing the Enter key.

Note: If disk mirroring for all volume groups is not Mirrored, an error message
is displayed. You are prompted to return to the System Image Backup and
Restore Menu.

7 Determine if you need to list the contents of the S-tape to determine the full
path name of the directory or file you wish to restore.

If you Do

wish to list the S-tape step 8

do not wish to list the S-tape step 15

8 From the System Image Backup and Restore Menu, select “List Contents of the
System Image Tape (S-tape)” by typing
>3
and pressing the Enter key.

9 After you select option 3, the system prompts you to insert the S-tape into the
appropriate tape drive.
Example response:
Please insert your System Image Backup tape (S-tape) into
the tape drive DAT0 and allow at least 5 minutes
to complete the listing.

A log file will be saved in /tmp/s-tape.toc.

Are you ready to proceed? ( y | n )

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-53

Restoring the SDM

Partial restore from the system image tape (S-tape) (continued)
At the SDM
10 Insert the S-tape into the tape drive you selected.

At the local or remote VT100 console

11 When you are ready to continue this procedure, type
>y
and press the Enter key.

12 The contents of the S-tape are listed on the screen. When the listing is
complete, the system prompts you to return to the System Image Backup and
Restore Menu.
Response:
Would you like to return to the previous menu? ( y | n )

13 Return to the System Image Backup and Restore Menu by typing

>y
and pressing the Enter key.

14 The next step of this procedure depends on why you are listing the contents of
the S-tape.

If you are verifying Do

that the file has been restored step 21

the file name or directory that you step 15
wish to restore

15 From the System Image Backup and Restore Menu, select “Restore Files from
the System Image Tape (S-tape)” by typing
>4
and pressing the Enter key.

16 After you select option 4, you are prompted to insert the S-tape into the tape
drive. A warning is displayed advising that this procedure must only be
completed by qualified SDM system administrators. The warning also advises
that files and directories must be entered exactly as they appear in the file
listing. Insert the S-tape in the appropriate tape drive.
Response:
Are you ready to enter the name of the file or directory? ( y | n )

Wireless Networks Family SDM–SX User Guide SDMPL011

6-54 SDM system administration procedures

Restoring the SDM

Partial restore from the system image tape (S-tape) (continued)

17 Continue this procedure, by typing

>y
and pressing the Enter key.
Response:
Enter the name of the directory or file that you wish to
restore as ./<your-full-path>/<your-file-or-directory>.

Note: Tape processing may take a few minutes to complete.

A log file /tmp/s-tape.restore will be created.

==>

18 Enter the full path name of the directory or file that you wish to restore, exactly
as shown in the file listing, including “./” at the beginning. A log file
/tmp/s-tape.restore is created when the restore is completed.
Note: An error message is displayed if the restore is unsuccessful. If this
occurs, go to step 21.

19 During the restore process, the screen will not display any additional
information. When the file restore is complete, the file you have restored is
displayed. The system then prompts you to return to the System Image Backup
and Restore Menu.
Response:
Would you like to return to the previous menu? ( y | n )

Note: If the restore has failed, an error message is displayed before the
prompt, advising you to list the contents of the tape, and perform the procedure
again.

20 To return to the System Image Backup and Restore Menu, type

>y
and press the Enter key.

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-55

Restoring the SDM

Partial restore from the system image tape (S-tape) (continued)

21 Determine if the restore was successful. The system displays the file that you
have restored, as described in step 19. You may also wish to view the
s-tape.restore file or list the files on the S-tape.

If Do

the restore is successful step 27

the restore failed step 30
you wish to view the s-tape.restore step 22
file
you wish to list the S-tape step 8

22 Return to the Backup and Restore Main Menu, by typing

>0
and pressing the Enter key.

23 Exit the Backup and Restore Main Menu, by typing

>0
and pressing the Enter key.

24 Exit the RMI by typing

>QUIT ALL
and pressing the Enter key.

25 Access the s-tape.restore file by typing

# cd /tmp
at the prompt and pressing the Enter key.
Scroll through the file by typing
# more s-tape.restore
and pressing the Enter key. Continue pressing the Enter key until the files you
have restored, and the date of the restore are displayed.

26 Proceed as follows.

If the restore Do

is successful step 29
failed step 30

Wireless Networks Family SDM–SX User Guide SDMPL011

6-56 SDM system administration procedures

Restoring the SDM

Partial restore from the system image tape (S-tape) (continued)
(end)

27 Return to the Backup and Restore Main Menu, by typing

>0
and pressing the Enter key.

28 Exit the Backup and Restore Main Menu, by typing

>0
and pressing the Enter key.
Note: If you wish to exit the RMI, type QUIT ALL and press the Enter key.

At the SDM
29 Remove the S-tape and store it in a secure place.
Go to step 31.

30 Contact the personnel responsible for the next level of support.

31 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 6-57 SDM system administration procedures 6-57

Installing the logreceiver tool

Application

ATTENTION
This procedure must be performed by a trained AIX system
administrator who has root user privileges to access the SDM, execute
access to FTP on the SDM, and write permissions to the directory
where the logreceiver tool will be installed.

Use this procedure to install the logreceiver tool on a workstation. The

procedure accesses the logreceiver software stored on an SDM to which the
workstation can connect, and installs it in a specified directory location on
the workstation.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-58 SDM system administration procedures

Installing the logreceiver tool (continued)

Summary of Installing the logreceiver tool

This flowchart summarizes the

Log in to the procedure.
SDM as the
root user Use the instructions in the
procedure that follows this
flowchart to perform the
Go to the procedure.
logreceiver
software directory

FTP to the
client machine

Go to the
logreceiver
install directory

Set the data

transfer mode
to binary

Transfer the
file

Exit FTP

Log in to the Go to the Change the file End

client machine logreceiver permissions
install directory

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-59

Installing the logreceiver tool (continued)

Installing the logreceiver tool
At the local or remote VT100 terminal
1 Log in as the root user to the SDM where the logreceiver tool is stored.

2 Go to the SDM directory that contains the logreceiver tool by typing

# cd /sdm/logs/osf
and pressing the Enter key.

3 FTP to the client machine where the logreceiver tool is to be installed, by typing
# ftp client
and pressing the Enter key.
where
client is the IP address of the client workstation where you are installing
the logreceiver tool
4 When prompted for “Name:”, type
>root
and press the Enter key.

5 When prompted for “Password:”, type

>password
and press the Enter key.
where
password is the root password for the client machine.
6 Go to the client machine directory where you wish to install the logreceiver tool
by typing
ftp>cd install_dir
and pressing the Enter key.
where
install_dir is the client machine directory where the logreceiver tool is to
be installed. The logreceiver tool can be installed in a
directory of the client’s choice or it could be installed in the
/sdm/bin directory.

7 Set the data transfer mode to binary by typing

ftp>bin
and pressing the Enter key.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-60 SDM system administration procedures

Installing the logreceiver tool (end)

(continued)

8 Determine if the client machine is a SUN or HP (Hewlett Packard) workstation.

If the client machine is a Do

an HP workstation step 9
a SUN workstation step 10

9 Send the software from the SDM to the client machine (HP workstation) by
typing
ftp>put logreceiver.hp logreceiver
and pressing the Enter key.
Go to step 11.

10 Send the software from the SDM to the client machine (SUN workstation) by
typing
ftp>put logreceiver.sun logreceiver
and pressing the Enter key.

11 Exit FTP by typing

ftp>quit
and pressing the Enter key.

12 Log in to the workstation.

13 Go to the directory where the logreceiver is installed by typing

# cd install_dir
and pressing the Enter key.
where
install_dir is the directory where the logreceiver tool was installed (see
step 6)
14 Alter the permission so that logreceiver can be executed from within that
directory, by typing
# chmod a+rx logreceiver
and pressing the Enter key.

15 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 6-61 SDM system administration procedures 6-61

Distributed Computing Environment

Configuring an SDM in a DCE cell

Application

ATTENTION
This procedure must be performed by a trained Distributed Computing
Environment (DCE) system administrator who knows DCE
administration procedures.

ATTENTION
If you use the default cell_admin “master administrator” account (full
configuration only), the administrative user’s password is sent in clear
text across the network when you use telnet to access the SDM
remotely. Nortel recommends that you execute the command from a
terminal that is attached to the SDM console port, to ensure password
security.

When an SDM is installed, it must be configured in the DCE cell to function

properly. This procedure assumes that a DCE cell is already in operation.

To perform this procedure you must know the password to use the
cell_admin DCE account (or principal) that is automatically created with the
DCE cell. The cell_admin DCE account has the required privileges to make
changes to the DCE cell.

Alternatively, the cell_admin principal can also create a subadministrator

account with limited privileges for the sole purpose of adding SDMs to the
DCE cell. If you choose to create a subadministrator account, the following
privileges are required:
• quotas to create principals
• read and insert permissions on the / .:/hosts cell directory service (CDS)
directory

Before performing this procedure, determine if you are going to configure

the SDM in the DCE cell using full configuration (one step) or local
configuration (two steps). Nortel recommends that you use full
configuration to perform this procedure because it is simpler, less prone to
errors, and it is controlled by the SDM commissioning tool.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-62 SDM system administration procedures

Distributed Computing Environment

Configuring an SDM in a DCE cell (continued)
To configure the SDM in a DCE cell using the full configuration procedure,
you must be able to
• log on as the root user to the SDM that is being configured
• provide a DCE administrator account principal name (cell_admin or an
equivalent principal), and its password, and all other required parameters
when running the “sdmconfig” program

If, for security reasons, the user configuring the SDM into the DCE cell
cannot obtain both the root password of the SDM, and the cell_admin
password, use local DCE configuration. To use local configuration, you
must be able to
• log in as the DCE administrator to a machine (another SDM, a Motorola
PowerStack or an IBM RS-6000 workstation) other than the SDM being
configured. This machine is an active node in the DCE cell, and it must
be running the AIX version of DCE. It is not necessary to log in as the
root user.
— If you are performing this step on an SDM that is already configured
in the DCE cell, the “mkdce” command is not accessible to the
maintenance (maint) user. You must, therefore, log in as the root
user to that SDM. If you cannot log in as root, have the root user add
a special user on that SDM that the DCE administrator can use to
perform the local configuration procedure. Refer to the procedure
”Adding or removing a maintenance user” on page 6-10 in this
document. Ensure that this special user’s initial program field is set
to /bin/csh or some other UNIX shell other than
/sdmtools/bin/cm_screener.
• run the “mkdce -o admin” command providing a DCE administrator
account principal name and password, and the hostname and IP address
of the SDM being preconfigured. The “mkdce” program is only
available on machines that run the AIX version of DCE.
• log in as root to the SDM being configured, and run the “sdmconfig”
program and provide all the required parameters for local SDM DCE
configuration

Note: You cannot commission DCE until you have commissioned the LAN.
If you attempt to commission DCE before commissioning the LAN, an error
message will be displayed. For information on LAN commissioning, refer
to the procedure ”Commissioning SDM-LAN connectivity” in the “SDM
maintenance procedures” chapter of this document.

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-63

Distributed Computing Environment

Configuring an SDM in a DCE cell (continued)
Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-64 SDM system administration procedures

Distributed Computing Environment

Configuring an SDM in a DCE cell (continued)
Summary of Configuring an SDM in a DCE cell

This flowchart summarizes the

procedure.
Determine
Use the instructions that follow
configuration
this flowchart to perform the
type
procedure.

Y Log in to other Create entries

Local DCE
AIX machine in for SDM being
configuration?
the DCE cell configured

N
Log in as root
to SDM being
added to cell

Invoke
sdmconfig

Enter required
information

Confirm
information

End

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-65

Distributed Computing Environment

Configuring an SDM in a DCE cell (continued)
Configuring an SDM in a DCE cell
At the SDM
1 Determine which method you wish to use to configure the SDM in a DCE cell.

If you are using Do

full DCE configuration step 5

local DCE configuration step 2

2 Log in as any user that can execute UNIX commands to a machine other than
the SDM being configured. This machine must be an active node in the DCE
cell, and must be running the AIX version of DCE.

3 Create entries for the SDM being configured in the DCE servers by typing
>mkdce -o admin -a DCE_admin_principal_name -h
target_SDM_hostname -i IP_address_of_the_target_SDM -p profile_name
all_cl
and pressing the Enter key
where
DCE_admin_principal_name is the DCE administrator’s principal name
target_SDM_hostname is the hostname of the SDM that you are
configuring in the DCE cell
IP_address_of_the_taget_SDM is the IP address of the SDM that you are
configuring in the DCE cell
profile_name is the name of the DCE LAN profile for
the SDM. To use the default profile
(lan_profile), omit this parameter, and the
“-p” before it.

Example response:
Configuring Security Client (sec_cl) for dce_host bnode76
on
machine 47.105.144.30 ...
Password must be changed!
Complete admin configuration of Security Client (sec_cl)
for
dce_host bnode76 on machine 47.105.144.30

Configuring CDS Clerk (cds_cl) for dce_host bnode76 on

machine 47.105.144.30 ...

Wireless Networks Family SDM–SX User Guide SDMPL011

6-66 SDM system administration procedures

Distributed Computing Environment

Configuring an SDM in a DCE cell (continued)
Modifying acls on hosts/bnode76
Modifying acls on hosts/bnode76/self
Modifying acls on hosts/bnode76/cds-clerk
Modifying acls on hosts/bnode76/profile
Modifying acls on / .:/lan-profile

Completed admin configuration of CDS Clerk (cds_cl) for

dce_host bnode76 on machine 47.105.144.30

Cell administrator’s portion of client configuration has

completed
successfully. Root administrator for
47.105.144.30 should now complete the client configuration
on that
machine.

4 At the prompt, enter the password for the DCE account cell_admin by typing
>password
and pressing the Enter key.
where
password is the password for the DCE account cell_admin

5 Log in as the root user to the SDM that you are adding to the DCE cell.

6 Invoke the SDM commissioning tool by typing

# sdmconfig
and pressing the Enter key.

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-67

Distributed Computing Environment

Configuring an SDM in a DCE cell (continued)

7 The DCE configuration screen is displayed.

Response:
SDM COMMISSIONING

DCE

You will be asked to select:

–Local DCE configuration, or
–Full DCE configuration

After your selection, you will be prompted for the

following information:
- the DCE cell name
- the DCE hostname of the SDM
- the IP address and hostname of the master Security
Server
- the IP address and hostname of the CDS Server
- the LAN profile for the SDM (FULL configuration only)
- the DCE Principal Name (FULL configuration only)
- the DCE Principal (or equivalent) password (FULL
configuration only)

Do you wish to proceed with DCE commissioning? [YES]

Note 1: DCE hostname is the name set to the UNIX hostname for the SDM. If
you enter a different name, the DCE application server initialization may fail.
Note 2: LAN profile is the name of the DCE LAN profile that supports the
portion of the cell (LAN) that this SDM is in. The LAN profile is mainly used for
defining the local Distributed Time Service (DTS) servers that provide time
synchronization for “electronically close” DCE nodes. For a small DCE cell, you
can select the default LAN profile (lan-profile); then all the nodes in the cell will
use the same set of DTS local servers.

8 Ensure that you know the required information shown in step 7. To proceed
with DCE commissioning, press the Enter key. You are then prompted to select
Local or Full DCE commissioning.
Response:
SDM COMMISSIONING

DCE

Please select either (L)ocal or (F)ull DCE commissioning:

Wireless Networks Family SDM–SX User Guide SDMPL011

6-68 SDM system administration procedures

Distributed Computing Environment

Configuring an SDM in a DCE cell (continued)

9 Proceed according to the method you are using to configure the SDM in a DCE
cell.

If you are using Do

full DCE configuration step 10

local DCE configuration step 16

10 Select full DCE configuration by typing

>F
and pressing the Enter key.

11 For full DCE configuration, you are prompted to enter the following information
in the order shown. Press the Enter key to get prompted for the next
information request.
• the DCE principal name
• the DCE cell name
• the IP address of the master Security Server
• the hostname of the master Security Server
• the IP address of the cell directory service (CDS) server
• the LAN profile for the SDM
Example response:
SDM COMMISSIONING

FULL DCE CONFIGURATION

Please enter the DCE principal name: [cell_admin]

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-69

Distributed Computing Environment

Configuring an SDM in a DCE cell (continued)

12 Enter the required information, as prompted. When you have entered all
required information, the values are displayed on the screen. You are
prompted to confirm whether the values are correct.
Example response:
SDM COMMISSIONING

FULL DCE CONFIGURATION

The following values have been entered:

DCE Administrator Principal Name: cell_admin

DCE Cell Name: sdmdev.bnr.ca
Security Server IP Address: 47.105.144.9
Security Server Hostname: bnode61
CDS Server IP Address: 47.105.144.9
CDS Server Hostname: bnode61
LAN Profile name: lan-red_105-profile

Are these values correct? [YES}

13 If the values are correct, press the Enter key. Full DCE configuration begins
immediately.
Note: If you type “N” for no, you are prompted to re-enter the information in
step 11. Enter the required information when prompted.

14 You will then be prompted to enter the DCE administrator’s password at the
beginning of this process. When you enter the password, full configuration
continues. Each item is displayed on the screen when it has been successfully
configured.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-70 SDM system administration procedures

Distributed Computing Environment

Configuring an SDM in a DCE cell (continued)
Note: In the following example response, after the system displays the
message, “Testing DCE stability....,” the system may display DCE configuration
messages until the DCE is stable.
Example response:
SDM COMMISSIONING

FULL DCE CONFIGURATION

Starting DCE commissioning...

Please enter the DCE administrator’s password:

Configuring RPC Endpoint Mapper (rpc)...
Suspending the DCE Monitor process during commissioning...
RPC Endpoint Mapper (rpc) configured successfully

Configuring Security Client (sec_cl)...

Password must be changed!
Security Client (sec_cl) configured successfully

Configuring CDS Clerk (cds_cl)...

Password must be changed!
Waiting (up to 2 minutes) for cdsadv to find a CDS server.
Found a CDS server.

Modifying acls on hosts/bnode64

Modifying acls on hosts/bnode64/self
Modifying acls on hosts/bnode64/cds-clerk
Modifying acls on hosts/bnode64/profile
Modifying acls on /.:/lan-red_105-profile

CDS Clerk (cds_cl) configured successfully

Configuring DTS Clerk (dts_cl)...

DTS Clerk (dts_cl) configured successfully

Current state of DCE configuration:

cds_cl COMPLETE CDS Clerk
dts_cl COMPLETE DTS Clerk
rpc COMPLETE RPC Endpoint Mapper
sec_cl COMPLETE Security Client

DCE has been installed.

Testing DCE stability....

DCE is stable.

Un-suspending DCE Monitor process...

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-71

Distributed Computing Environment

Configuring an SDM in a DCE cell (continued)

15 A message is displayed to inform you that DCE has been successfully

commissioned on the SDM. You are then prompted to press the Enter key to
continue.
Response:
DCE Commissioning PASSED

HIT ENTER TO CONTINUE

Go to step 23.

16 Select local DCE configuration by typing

>L
and pressing the Enter key.

17 For local DCE configuration, you are prompted to enter the following
information in the order shown. Press the Enter key to get prompted for the
next information request.
• the DCE cell name
• the DCE hostname of the SDM
• the IP address of the master security server
• the hostname of the master security server
• the IP address of the cell directory service (CDS) server
Response:
SDM COMMISSIONING

LOCAL DCE CONFIGURATION

Please enter the DCE cell name:

Wireless Networks Family SDM–SX User Guide SDMPL011

6-72 SDM system administration procedures

Distributed Computing Environment

Configuring an SDM in a DCE cell (continued)

18 When all the information is entered, the values are displayed on the screen.
You are then prompted to confirm that the values are correct.
Response:
SDM COMMISSIONING

LOCAL DCE CONFIGURATION

The following values have been entered:

DCE Cell Name: sdmdev.bnr.ca

Security Server IP Address: 47.105.144.9
Security Server Hostname: bnode61
CDS Server IP Address: 47.105.144.9
CDS Server Hostname: bnode61

Are these values correct? [YES}

19 If the values are correct, press the Enter key. Local configuration begins
immediately.
Note: If you type “N” for no, you are prompted to re-enter the information in
step 17. Enter the required information when prompted.

20 You will be prompted to enter the DCE administrator’s password at the

beginning of this process. When you enter the password, local configuration
continues. Each item is displayed on the screen when it has been successfully
configured.
Example response:
SDM COMMISSIONING

LOCAL DCE CONFIGURATION

Commissioning DCE - Suspending the DCE Monitor process

during commissioning...

Un-suspending DCE Monitor process...

21 A message is displayed on the screen to inform you that DCE has been
successfully commissioned on the SDM.
Response:
DCE Commissioning PASSED

HIT ENTER TO CONTINUE

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-73

Distributed Computing Environment

Configuring an SDM
Configuring in a DCE
an SDM cell (continued)
in a DCE cell (end)

22 Press the Enter key. If DCE is the last item to be commissioned on the SDM,
you will see the following message:
Response:
SDM COMMISSIONING

SDM Commissioning complete!

#
If there are other items to be commissioned, the appropriate screen is
displayed.

23 You have completed this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-74 SDM system administration procedures 6-74

Distributed Computing Environment

Removing an SDM from a DCE cell

Application

ATTENTION
This procedure must be performed by a trained Distributed Computing
Environment (DCE) system administrator who knows DCE
administration procedures.

ATTENTION
If you use the default cell_admin “master administrator” account (full
removal only), the administrative user’s password is sent in clear text
across the network when you use telnet to access the SDM remotely.
Nortel recommends that you execute the command from a terminal
that is attached to the SDM console port, to ensure password security.

If an SDM is being taken out of service permanently, it must be removed

from the DCE cell. It may also be necessary to remove the SDM from the
DCE cell if there is a DCE error condition that cannot be fixed by other
means.

To perform this procedure, you must know the password to use the
cell_admin DCE account (or principal) that is automatically created with the
DCE cell. The cell_admin DCE account has the required privileges to make
changes to a DCE cell.

Alternatively, the cell_admin principal can also create a subadministrator

account with limited privileges for the sole purpose of maintaining SDMs in
the DCE cell. If you choose to create a subadministrator account, the
following privileges are required:
• quotas to create principals
• read and insert permissions on the / .:/hosts cell directory service (CDS)
directory

Before performing this procedure, determine if you are going to remove the
SDM from the DCE cell using full removal (one step) or local removal (two
steps). Nortel recommends that you use full removal to perform this
procedure because it is simpler, and less prone to errors.

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-75

Distributed Computing Environment

Removing an SDM from a DCE cell (continued)
To remove the SDM from a DCE cell using the full removal procedure, you
must be able to
• log on as the root user to the SDM that is being removed
• provide a DCE administrator account principal name (cell_admin or an
equivalent principal), and its password, and all other required parameters
when running the “rmdce” program

If, for security reasons, the user removing the SDM from the DCE cell
cannot obtain both the root password of the SDM, and the cell_admin
password, use local DCE removal. To use local removal, you must be able
to
• log in as the root user to the SDM that is being removed
• run the “rmdce -o local” command
• log in as the DCE administrator to a machine (another SDM, a Motorola
PowerStack or an IBM RS-6000 workstation) other than the SDM being
removed. This machine is an active node in the DCE cell, and it must be
running the AIX version of DCE. It is not necessary to log in as the root
user.
— If you are performing this step on an SDM that is already configured
in the DCE cell, the “rmdce” command is not accessible to the
maintenance (maint) user. You must, therefore, log in as the root
user to that SDM. If you cannot log in as root, have the root user add
a special user on that SDM that the DCE administrator can use to
perform the local removal procedure. Refer to the procedure
”Adding or removing a maintenance user” on page 6-10 in this
document. Ensure that this special user’s initial program field is set
to /bin/csh or some other UNIX shell other than
/sdmtools/bin/cm_screener.
• run the “rmdce -o admin” command providing a DCE administrator
account principal name and password, and the hostname and IP address
of the SDM being pre-configured. The “rmdce” program is only
available on machines that run the AIX version of DCE.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-76 SDM system administration procedures

Distributed Computing Environment

Removing an SDM from a DCE cell (continued)
Summary of Removing an SDM from a DCE cell

This flowchart summarizes the

procedure.
Determine
configuration Use the instructions that follow
type this flowchart to perform the
procedure.

Log in to SDM
being removed
from DCE cell

Disable
dcemonitor

Local DCE N Remove SDM Re-enable

configuration? from DCE cell dcemonitor
(rmdce)
Y
Remove SDM
from DCE cell

Log in to other
AIX machine in
DCE cell

Remove entries
for target SDM

End

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-77

Distributed Computing Environment

Removing an SDM from a DCE cell (continued)
Removing an SDM from a DCE cell
At the SDM
1 Determine which method you wish to use to remove the SDM from the DCE
cell.

If you are using Do

full DCE removal step 2

local DCE removal step 8

2 Log in as the root user to the SDM that is being removed from the DCE cell.

3 Disable the DCE monitor program to prevent it from interfering with this
procedure. Refer to the procedure ”Distributed Computing Environment –
Disabling and enabling dcemonitor” on page 6-106 in the “SDM system
administration procedures” chapter of this document. When you have disabled
dcemonitor, continue this procedure.

4 Remove the SDM from the DCE cell by typing

# rmdce -a administrator_principal all_cl
and pressing the Enter key.
where
administrator_principal is the DCE administrator’s principal name

Wireless Networks Family SDM–SX User Guide SDMPL011

6-78 SDM system administration procedures

Distributed Computing Environment

Removing an SDM from a DCE cell (continued)

5 At the prompt, enter the password for the DCE account cell_admin by typing
# password
and pressing the Enter key.
where
password is the password for the DCE account cell_admin

Response:

Unconfiguring DTS Clerk (dts_cl)...

DTS Clerk (dts_cl) unconfigured successfully

Unconfiguring CDS Clerk (cds_cl)...

CDS Clerk (cds_cl) unconfigured successfully

Unconfiguring Security Client (sec_cl)...

Security Client (sec_cl) unconfigured successfully

Unconfiguring RPC Endpoint Mapper (rpc)...

RPC Endpoint Mapper (rpc) unconfigured successfully

Current state of DCE configuration:

No components are configured
#

6 When you see the message “No components are configured”, the SDM has
been removed from the DCE cell.

7 Enable the DCE monitor program that was disabled in step 3. Refer to the
procedure ”Distributed Computing Environment – Disabling and enabling
dcemonitor” on page 6-106 in the “SDM system administration procedures”
chapter of this document. When you have enabled dcemonitor, go to step 16.

8 Log in as the root user to the SDM that is being removed from the DCE cell.

9 Disable the DCE monitor program to prevent it from interfering with this
procedure. Refer to the procedure ”Distributed Computing Environment –
Disabling and enabling dcemonitor” on page 6-106 in the “SDM system
administration procedures” chapter of this document. When you have disabled
dcemonitor, continue this procedure.

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-79

Distributed Computing Environment

Removing an SDM from a DCE cell (continued)

10 Remove the local DCE components from the SDM by typing

# rmdce -o local all_cl
and pressing the Enter key.
Response:
Unconfiguring DTS Clerk (dts_cl)...
DTS Clerk (dts_cl) unconfigured successfully on the
local machine

Unconfiguring CDS Clerk (cds_cl)...

CDS Clerk (cds_cl) unconfigured successfully on the
local machine

Unconfiguring Security Client (sec_cl)...

Security Client (sec_cl) unconfigured successfully on the
local machine

Unconfiguring RPC Endpoint Mapper (rpc)...

RPC Endpoint Mapper (rpc) unconfigured successfully on the
local machine

Current state of DCE configuration:

No components are configured
#

11 When you see the message “No components are configured”, the SDM has
been removed from the DCE cell.

12 Enable the DCE monitor program that was disabled in step 9. Refer to the
procedure ”Distributed Computing Environment – Disabling and enabling
dcemonitor” on page 6-106 in the “SDM system administration procedures”
chapter of this document. When you have enabled dcemonitor, continue this
procedure.

13 Log in to any machine (another SDM, a Motorola PowerStack or an IBM

RS-6000 workstation) other than the SDM being removed. This machine is an
active node in the DCE cell, and it is running the AIX version of DCE. It is not
necessary to log in as the root user.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-80 SDM system administration procedures

Distributed Computing Environment

Removing an SDM from a DCE cell (continued)
(end)

14 Remove the entries for the SDM you are removing from the DCE servers by
typing
# rmdce -o admin -h machine name -a cell_admin all_cl
and pressing the Enter key
where
machine name is the name of the SDM you are removing

15 At the prompt, enter the password for the DCE account cell_admin by typing
>password
and pressing the Enter key.
where
password is the password for the DCE account cell_admin
Note: If the DCE host has a distributed file system (DFS) client (dfs_cl)
configured, the DFS client cannot be used until the host has been reconfigured
as a DCE client.
Example response:

Password must be changed!

Unconfiguring DTS Clerk (dts_cl) for
DCE host bnode64 ...
DTS Clerk (dts_cl) unconfigured successfully for
DCE host bnode64

Unconfiguring CDS Clerk (cds_cl) for

DCE host bnode64 ...
CDS Clerk (cds_cl) unconfigured successfully for
DCE host bnode64

Unconfiguring Security Client (sec_cl) for

DCE host bnode64 ...
Security Client (sec_cl) unconfigured successfully for
DCE host bnode64

16 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 6-81 SDM system administration procedures 6-81

Distributed Computing Environment

Creating a DCE user

Application

ATTENTION
This procedure must be performed by a trained Distributed Computing
Environment (DCE) system administrator who knows DCE
administration procedures.

Use this procedure to create a DCE user account for a user that runs SDM
graphical user interface (GUI) client programs.

Invoking the create_dce_user command creates a new DCE user and makes
the user a member of a specified group. Use groups for access control
purposes to categorize users with similar job functions. You only need a
DCE account to run an SDM GUI program. There may be some exceptions
for specific SDM applications. For any exceptions, refer to the
documentation OSF DCE Command Reference, provided with the
application.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-82 SDM system administration procedures

Distributed Computing Environment

Creating a DCE user (continued)
Summary of Creating a DCE user

This flowchart summarizes the

procedure.

Use the instructions that follow

this flowchart to perform the
procedure.

Create a DCE
user

1
Y
Create another
Create another 1
DCE user
DCE user?

End

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-83

Distributed Computing Environment

Creating a DCE user (continued)
Creating a DCE user
At the SDM client workstation
1 Create a DCE user by typing
>/sdm/bin/create_dce_user
2 Enter the user ID at the prompt by typing
>DCE administrator user ID[cell_admin]: UserID
and pressing the Enter key.
where
UserID is the user ID of the DCE administrator
Note: cell_admin is the default value. If you do not specify a user Id, the
system enters the default value.

3 Enter the DCE administrator password at the prompt by typing

>DCE administrator password:password
and pressing the Enter key.
where
password is the password for the administrator account that you are
using
Note: The password is not echoed on the screen.

4 Enter the name of the DCE user by typing

>New DCE user ID:userID
and pressing the Enter key.
where
userID is the user ID of the new DCE user
Response:

Enter the full name of the person associated with this

user ID:
5 Enter the full name of the person associated with the user ID by typing
>fullname
and pressing the Enter key.
where
fullname is the full name of the person associated with the user ID
6 Enter the user group by typing
>User group [sdm–users]:sdm–maint
and pressing the Enter key.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-84 SDM system administration procedures

Distributed Computing Environment

Creating a DCE user (continued)
(end)
where
sdm–maint is the user group of the DCE user
Example response:
The ”sdm–maint” group doesn’t exist! it will be created.
Note: sdm–users is the default value. If no user group is specified, the
system enters the default value.

7 Enter the user password by typing

>User password:password
and pressing the Enter key.
where
password is the password for the DCE user ID
Note: The password is not echoed on the screen.

8 Re-enter the user password by typing

>Re–enter user password:password
and pressing the Enter key.
Example response:
The new DCE user ID ”joe” has been created.

9 Determine if you want to create another DCE user.

If you Do

want to create another user step 1

do not want to create another user step 11

10 Contact the personnel responsible for the next level of support.

11 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 6-85 SDM system administration procedures 6-85

Distributed Computing Environment

Changing a DCE user password

Application
Use this procedure to change a DCE user password.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-86 SDM system administration procedures

Distributed Computing Environment

Changing a DCE user password (continued)
Summary of Changing a DCE user password

This flowchart summarizes the

procedure.

Use the instructions that follow

this flowchart to perform the
procedure.

Change a DCE
a DCE user
password

1
Change Y Change
another another 1
password? password
N

End

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-87

Distributed Computing Environment

Changing a DCE user password (continued)
Changing a DCE user password
At the SDM client workstation
1 Change a DCE user password by typing
>/sdm/bin/change_dce_password
Response:
DCE user ID:

2 Enter the user ID of the user for whom you are changing the password by
typing
>userID
and pressing the Enter key.
where
userID is the user ID of the user for whom you are changing the
password
Response:
Old password:

3 Enter the old password by typing

>password
and pressing the Enter key.
where
password is the old password of the user for whom you are changing
the password
Note: The password is not echoed on the screen.

Response:
New password:

4 Enter the new password by typing

>password
and pressing the Enter key.
where
password is the new password of the user
Response:
Re-enter password:

Wireless Networks Family SDM–SX User Guide SDMPL011

6-88 SDM system administration procedures

Distributed Computing Environment

Changing a DCE user password (continued)
(end)

Note: The password is not echoed on the screen.

5 Re-enter the user password by typing

>password
and pressing the Enter key.
Example response:
The password for ”joe” has been changed.

6 Determine if you want to change another DCE user password.

If you Do

want to change another password step 1

do not want to change another step 7
password

7 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 6-89 SDM system administration procedures 6-89

Distributed Computing Environment

Deleting a DCE user

Application

ATTENTION
This procedure must be performed by a trained Distributed Computing
Environment (DCE) system administrator who knows DCE
administration procedures.

Use this procedure to delete a DCE user.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-90 SDM system administration procedures

Distributed Computing Environment

Deleting a DCE user (continued)
Summary of Deleting a DCE user

This flowchart summarizes the

procedure.

Use the instructions that follow

this flowchart to perform the
procedure.

Delete a DCE
user

Delete another Delete another 1

user? user

End

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-91

Distributed Computing Environment

Deleting a DCE
Deleting user user
a DCE (continued)
(end)
Deleting a DCE user
At the SDM client workstation
1 Delete a DCE user by typing
>/sdm/bin/delete_dce_user
Response:
DCE administrator user ID [cell_admin]:

2 Enter the user ID at the prompt by typing

>userID
and pressing the Enter key.
where
userID is the user ID of the DCE administrator
Note: cell_admin is the default value. If you do not specify a user Id, the
system enters the default value.
Response:
DCE user ID to be deleted:

3 Enter the DCE user ID to be deleted by typing

>userID
and pressing the Enter key.
where
userID is the user ID of the user to be deleted
Example response:
The DCE user ID ”joe” has been deleted.

4 Determine if you want to delete another DCE user.

If you Do

want to delete another password step 1

do not want to delete another step 5
password

5 You have completed this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-92 SDM system administration procedures 6-92

Distributed Computing Environment

Configuring or reconfiguring a node within a DCE cell

Application

ATTENTION
This procedure must be performed by a trained Distributed Computing
Environment (DCE) system administrator who knows DCE
administration procedures.

ATTENTION
This procedure does not apply if you are configuring a DCE master
server. To configure a DCE master server, refer to your DCE vendor’s
documentation.

Use this procedure to configure a new node or to reconfigure an existing

node within a DCE cell. This procedure updates the pe_site file for each
client or server within a DCE cell. The pe_site file contains the IP addresses
and other binding information for both master server and backup server.

Action
The following flowchart summarizes the procedure. Use the instructions in
the step-action procedure that follows the flowchart to perform the task.

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-93

Distributed Computing Environment

Configuring or reconfiguring a node within a DCE cell (continued)
Summary of configuring or reconfiguring a node within a DCE cell

This flowchart summarizes the

procedure.

Use the instructions that follow

Log in to the this flowchart to perform the
client workstation procedure.

Is this an HP N
workstation?

Y
Set up the
remote admin Is this a SUN N
variable workstation?

Configure the Configure the

workstation as a workstation as a Unknown
client or server DCE client or workstation
server type

Change the End

DCE daemon End
startup
parameter

Restart the
DCE daemon

Check
End the End
End
pc_site acl

Wireless Networks Family SDM–SX User Guide SDMPL011

6-94 SDM system administration procedures

Distributed Computing Environment

Configuring or reconfiguring a node within a DCE cell (continued)
Configuring or reconfiguring a node within a DCE cell
At the client workstation
1 Login to the workstation as a root user.

2 Determine the operating system by typing

> uname
and pressing the Enter key.
Example response:
HP-UX
3 Proceed depending on the type of operating system on the workstation:

If you are running Go to

HP-UX step 4
SunOS step 9
Other step 19

4 Determine your login shell by typing

> finger root
and pressing the Enter key.
Example response:
Login name: root In real life: 000-Admin (0000)
Directory: /bmr/users/root Shell: /bin/csh
On since Jul 29 09:20:37 on pts/0 from bmerh7b
45 minutes Idle Time
No unread mail
No Plan.
5 Proceed depending on the shell type.

If you are running Go to

shell = csh step 6

shell = ksh or sh step 7

6 Set up the remote administration capability by typing

> setenv REMOTE_ADMIN y
and pressing the Enter key.

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-95

Distributed Computing Environment

Configuring or reconfiguring a node within a DCE cell (continued)
Go to step 8.

7 Set up the remote administration capability by typing

> export REMOTE_ADMIN=y
and pressing the Enter key.

8 Follow your vendor’s instruction to configure the HP workstation as a DCE

client or server within the DCE cell.
Go to step 13.

9 Follow your vendor’s instructions to configure the SUN workstation as a DCE

client or server within the DCE cell.

10 Modify the DCE daemon startup option. Use a text editor to edit the file
setup_state located in /opt/dcelocal/etc/setup_state. Change the line
startup_dced= ’ ’ into startup_dced=’–x’ and save the file.

11 Stop the DCE daemon by typing

> /etc/init.d/dce stop
and pressing the Enter key.
Example response:
Deactivating and stopping DTS
Executing ”dcecp –c dts deactivate; dts stop”
Waiting for dtsd to exit
WARNING Process dtsd did not stop
Killing dtsd
Killing cdsadv
Deactivating secval service
Killing dced
12 Start the DCE daemon by typing
> /etc/init.d/dce start
and pressing the Enter key.
Example response:
Starting process dced
Starting process secd
Activating secval service

Starting process cdsadv

Starting process dtsd
13 Invoke the DCE control program (dcecp) by typing
>dcecp
and pressing the Enter key.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-96 SDM system administration procedures

Distributed Computing Environment

Configuring or reconfiguring a node within a DCE cell (continued)
(end)

14 Check the pe_site acl at the prompt by typing

dcecp>acl show / . :/$_h/config/hostdata/pe_site
at the dcecp prompt, and pressing the Enter key.
Example response:
{unauthenticated –––r–}
{user hosts/bmerye6d/self cdprw}
{group subsys/dce/dced–admin cdprw}
{any_other –––r–}
15 Proceed depending on the dced–admin acl.

If the line “group

subsys/dce/dced-admin ...” Go to

did not show on the display step 16

is shown on the display step 17

16 Add dced-admin acl to pe_site by typing

dcecp>acl modify / . :/$_h/config/hostdata/pe_site -add {group
subsys/dce/dced-adm}
17 Exit dcecp by typing
dcecp>exit
at the prompt, and pressing the Enter key.

18 Log out of the workstation by typing

>exit
and pressing the Enter key.
Go to step 20.

19 For this type of operating system, contact your next level of support.

20 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 6-97 SDM system administration procedures 6-97

Distributed Computing Environment

Viewing the dcemonitor status file

Application

ATTENTION
This procedure must be performed by a trained Distributed Computing
Environment (DCE) system administrator who knows DCE
administration procedures.

The SDM detects common DCE failure conditions, reports them to the SDM
node control facility, and automatically takes the appropriate recovery action
to clear the problem. The status of DCE, reported by dcemonitor, is
displayed under the LAN connectivity menu level of the SDM remote
maintenance interface (RMI).

This automatic DCE maintenance is performed by the dcemonitor script.

The dcemonitor sript is a Tool Command Language (TCL) script that is
continuously executed by a DCE control program (dcecp) running in the
SDM platform. Dcemonitor dumps its current status, problems found, and
the recovery action in a file that is regularly rewritten. By viewing the
contents of the status file, you can determine what caused the DCE state
change.

This procedure assists you when dcemonitor cannot fix the problem, and
manual intervention is necessary. Problems requiring manual intervention
include:
• the server identifies a mismatch resulting from a change to the switch
Common Language Location Identifier (CLLI)
• the SDM hostname is changed
• the SDM has been restored from a backup tape

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-98 SDM system administration procedures

Distributed Computing Environment

Viewing the dcemonitor status file (continued)
Summary of Viewing the dcemonitor status file

This flowchart summarizes the

procedure.

Use the instructions that follow

this flowchart to perform the
Log in to the procedure.
SDM as root
user

Go to
dcemonitor
directory

Determine
when file was
written

View contents
of the file

End

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-99

Distributed Computing Environment

Viewing the dcemonitor
Viewing status
the dcemonitor file (continued)
status file (end)
Viewing the dcemonitor status file
At the local VT100 console or remote workstation
1 Log in to the SDM as the root user

2 Go to the dcemonitor data directory by typing

# cd /data/mtce/dce
and pressing the Enter key.

3 Determine when the file was last written by typing

# ls -l dce_mon_status
and pressing the Enter key.

4 View the contents of the status file by typing

# cat dce_mon_status
and pressing the Enter key.

5 You have completed this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-100 SDM system administration procedures 6-100

Distributed Computing Environment

Shutting down the master server

Application

ATTENTION
This procedure must be performed by a trained Distributed Computing
Environment (DCE) system administrator who knows DCE
administration procedures.

Use this procedure when a master server malfunctions, or when you want to
designate a different master server.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-101

Distributed Computing Environment

Shutting down the master server (continued)
Summary of Shutting down the master server

Log into the This flowchart summarizes the

client procedure.
workstation
Use the instructions that follow
this flowchart to perform the
Log into the SUN N procedure.
DCE workstation?

Y HP N
Update the workstation?
HP DCE
pe–site files master server
shut down Unknown
workstation
SUN DCE type? Contact
master server next level of
Replicate CDS
End Logout from shut down
master server support
directories
workstation
Logout from 1
1 master server
Logout from workstation
DCE
1

Logout from
the client
workstation
1
Log into the DCE
master server End
workstation

Wireless Networks Family SDM–SX User Guide SDMPL011

6-102 SDM system administration procedures

Distributed Computing Environment

Shutting down the master server (continued)
Shutting down the master DCE server
At the SDM client workstation
1 Log into the client workstation.

2 Log into DCE using the userID of the administrator by typing

>dce_login administrator name
and pressing the Enter key.
where
administrator name is the userID of the administrator.
3 Enter the administrator password at the ”Enter password:” prompt by typing
password
and pressing the Enter key.
where
password is the password for the administrator account you are using.
4 Access the /sdm/bin directory by typing
> cd /sdm/bin
and pressing the Enter key.

5 Update the pe_site file by typing

> ./update_pe_site
and pressing the Enter key.
Example response:
These are the registry servers currently running in the
cell:
”bmers38”
”bmerye6d” ”master”
answer y for ”Yes” will update all pe_site data
from above servers on each node within the cell.

Do you want to continue? [y]

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-103

Distributed Computing Environment

Shutting down the master server (continued)

6 Confirm the command by typing

>y
and pressing the Enter key.
Example response:
host ”bmers38” pe_site data is successfully updated
host ”bmers80” pe_site data is successfully updated
host ”bmersa00” pe_site data is successfully updated
host ”bmery7c8” pe_site data is successfully updated

Security registry pe_site data update complete.

Note: If DCE is not running properly on a node, it does not work properly with
the backup server. After you fix the DCE problem, on the machine redo step 5
and step 6.

7 Replicate CDS directories by typing

> ./replicate_cds_dirs
and pressing the Enter key.
Example response:
The directories from master CDS server/clearinghouse
”/.../sdmver.bnr.ca/bmerye6d_ch”
will be replicated to the following replicas;
”/.../sdmver.bnr.ca/bmerha86_ch”
answer y for ”Yes” will perform the replication.

Do you want to continue? [y]

8 Confirm the command by typing

>y
and pressing the Enter key.
Example response:
Directory /.:/hosts has been replicated in replica CDS
bmerha86_ch
Directory /.:/subsy has been replicated in replica CDS
bmerha86_ch
Directory /.:/subsys/dce has been replicated in replica
CDS bmerha86_ch
Directory /.:/subsys/NT has been replicated in replica CDS
bmerha86_ch
CDS replica directory replicated completed

Wireless Networks Family SDM–SX User Guide SDMPL011

6-104 SDM system administration procedures

Distributed Computing Environment

Shutting down the master server (continued)

9 Log out from DCE by typing

> exit
and pressing the Enter key.

10 Log out of the client workstation by typing

> exit
and pressing the Enter key.

11 Log into the DCE master server workstation as the root user.

12 Determine the operating system by typing

> uname
and pressing the Enter key.
Example response:
HP-UX
13 Proceed depending on the type of operating system on the workstation:

If you are running Do

HP-UX step 14, 15, and 19

SunOS step 16, 17, and 19
Other step 18

14 Follow the HP vendor’s DCE configuration instructions to shut down the master
server.

15 Log out of the master server workstation by typing

> exit
and pressing the Enter key.
Go to step 19.

16 Follow the SUN vendor’s DCE configuration instructions to shut down the
master server.

17 Log out of the master server workstation by typing

> exit
and pressing the Enter key.
Go to step 19

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-105

Distributed Computing Environment

Shutting downdown
Shutting the master server
the master server
(continued)
(end)

18 For this type of operating system, contact your next level of support.

19 You have completed this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-106 SDM system administration procedures 6-106

Distributed Computing Environment

Disabling and enabling dcemonitor

Application

ATTENTION
This procedure must be performed by a trained Distributed Computing
Environment (DCE) system administrator who knows DCE
administration procedures.

When dcemonitor cannot solve a service-affecting DCE problem, it attempts

to solve the problem by killing the DCE daemons using /etc/dce.clean, and
restarting them using /etc/rc.dce. If this does not solve the problem,
dcemonitor waits 3 min, and repeats these operations indefinitely.

The “DCE Monitor present action:” line in the dce_mon_status file will be
“restart” if dcemonitor is doing recovery by restarts. If dcemonitor
constantly kills DCE daemons, the DCE environment on the SDM becomes
unstable. This can seriously impair your ability to fix the problem.

This procedure prevents dcemonitor from restarting and killing DCE

daemons by suspending these operations for 1 hour. After 1 hour,
dcemonitor resumes these activities.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-107

Distributed Computing Environment

Disabling and enabling dcemonitor (continued)
Summary of Disabling and enabling dcemonitor

This flowchart summarizes the

procedure.

Use the instructions that follow

Log in to the this flowchart to perform the
SDM as root procedure.
user

Go to
dcemonitor
directory

Edit
suspension
control file

Change the
control word

Close the file

Disabled Y Dcemonitor
dcemonitor? suspended for
1 hour
N

End

Wireless Networks Family SDM–SX User Guide SDMPL011

6-108 SDM system administration procedures

Distributed Computing Environment

Disabling and enabling dcemonitor (continued)
Disabling and enabling dcemonitor
At the local VT100 console or remote workstation
1 Log in to the SDM as the root user

2 Go to the dcemonitor data directory by typing

# cd /data/mtce/dce
and pressing the Enter key.

3 Edit the dcemonitor suspension control file by typing

# vi dce_mon_suspend
and pressing the Enter key. This file contains one word.

4 Determine whether you wish to disable or enable dcemonitor

If you wish to Do

disable dcemonitor step 7

enable dcemonitor step 5

5 Modify the control word by typing

>cw
The word suspend is replaced by “suspen$”.

6 Enable dcemonitor by typing the activation control word

>active
The $ from “suspen$” (step 5) remains.

Go to step 9.

7 Modify the control word by typing

>cw
The word active is replaced by “activ$”.

8 Disable dcemonitor by typing the suspension control word

>suspend

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-109

Distributed Computing Environment

Disabling and enabling
Disabling dcemonitor
and enabling dcemonitor
(continued)
(end)

9 Close the file by pressing the Esc key and typing

>: wq
and pressing the Enter key.
Dcemonitor stops killing and restarting DCE daemons for one hour.
Note: After an hour dcemonitor continues to restart and kill DCE daemons.
The “active$” and “$” disappear when you press the Esc key.

10 You have completed this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-110 SDM system administration procedures 6-110

Distributed Computing Environment

Restricting ports to an SDM-defined range

Application

ATTENTION
This procedure must be performed by a trained Distributed Computing
Environment (DCE) system administrator who knows DCE
administration procedures.

Use the following procedure to restrict the ports to a range that is predefined
by the SDM software, and a range that will coexist with other SDM
applications. You must have root user privileges to perform this procedure.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-111

Distributed Computing Environment

Restricting ports to an SDM-defined range (continued)
Summary of Restricting ports to an SDM-defined range

Log in to the This flowchart summarizes the

SDM as the procedure.
root user
Use the instructions that follow
this flowchart to perform the
Restrict the procedure.
ports

Note the range

of the ports

Access the top

menu level of
the RMI

Access the
LAN menu
level

Access the
APPL menu
level

Busy the
application

Return the End

application to
service

Wireless Networks Family SDM–SX User Guide SDMPL011

6-112 SDM system administration procedures

Distributed Computing Environment

Restricting ports to an SDM-defined range (continued)
Restricting ports to an SDM-defined range
At the client workstation
1 Log in to the SDM as the root user

2 Restrict the ports to an SDM-defined range by typing

# restrict_dce_ports system_defined
and pressing the Enter key.
Response:
The following port ranges have been configured
TCP: 4500–4540 UDP: 4500–4540

3 Note the range of ports that are printed by the script. Use thse values for the
firewall configuration.

4 Access the top menu level of the remote maintenance interface (RMI) by typing
# sdmmtc
and pressing the Enter key.

5 Access the LAN menu level of the RMI by typing

>LAN
and pressing the Enter key.

6 Wait for DCE to go to InSv. This may take several minutes.

Response:
DCE State: InSv

7 Access the application (APPL) menu level of the RMI by typing

>APPL
and pressing the Enter key.
Example response:
# Package Description Version State
1 Table Access Service 10.0.29.0 InSv
2 OM Access Service 10.0.29.0 InSv
3 Log Delivery Service 10.0.29.0 InSv

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-113

Distributed Computing Environment

Restricting ports to an SDM-defined range (continued)

8 Determine the key number for the application (shown under the header “#”).

9 Manually busy the application software by typing

>BSY n
and pressing the Enter key.
where
n is the number under “#” of the application you wish to busy
Response:
The application is in service.
This command will cause a service interruption.
Do you wish to proceed?
Please confirm (“YES”, “Y”, “NO”, or “N”):
Note: Busying the application as shown performs an orderly shutdown and can
take up to 2 min.

10 Confirm the Busy command by typing

>Y
and pressing the Enter key.

11 After you confirm the Bsy command, the following is displayed:

Response:
Application Bsy– Command initiated.
Please wait...
When the Bsy command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Response:
Application Bsy – Command submitted.

12 Return the application to service by typing

>RTS n
and pressing the Enter key.
where
n is the number of the application (from step 9 )

Wireless Networks Family SDM–SX User Guide SDMPL011

6-114 SDM system administration procedures

Distributed Computing Environment

Restricting ports to an SDM-defined range (continued)
(end)
Response:
Application RTS - Command initiated.
Please wait...
When the RTS command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Response:
Application RTS – Command submitted.

13 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 6-115 SDM system administration procedures 6-115

Distributed Computing Environment

Removing port restrictions

Application

ATTENTION
This procedure must be performed by a trained Distributed Computing
Environment (DCE) system administrator who knows DCE
administration procedures.

Use the following procedure to return the SDM to the system default values.
DCE ports will be randomly assigned when you complete this procedure.
You must have root user privileges to perform this procedure.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-116 SDM system administration procedures

Distributed Computing Environment

Removing port restrictions (continued)
Summary of Removing port restrictions

This flowchart summarizes the

Log in to the procedure.
SDM as the
root user Use the instructions that follow
this flowchart to perform the
procedure.
Remove the
port
restrictions

Access the top

menu level of
the RMI

Access the
LAN menu
level

Access the
APPL menu
level

Busy the
application

Return the
application to
service

End

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-117

Distributed Computing Environment

Removing port restrictions (continued)
Removing port restrictions
At the client workstation
1 Log in to the SDM as the root user

2 Restrict the ports to an SDM-defined range by typing

# restrict_dce_ports unrestricted
and pressing the Enter key.
Response:
DCE servers port range restrictions have been removed.

3 Access the top menu level of the remote maintenance interface (RMI) by typing
# sdmmtc
and pressing the Enter key.

4 Access the LAN menu level of the RMI by typing

>LAN
and pressing the Enter key.

5 Wait for DCE to go to InSv. This may take several minutes.

Response:
DCE State: InSv

6 Access the application (APPL) menu level of the RMI by typing

>APPL
and pressing the Enter key.
Example response:
# Package Description Version State
1 Table Access Service 10.0.29.0 InSv
2 OM Access Service 10.0.29.0 InSv
3 Log Delivery Service 10.0.29.0 InSv

Wireless Networks Family SDM–SX User Guide SDMPL011

6-118 SDM system administration procedures

Distributed Computing Environment

Removing port restrictions (continued)

7 Determine the key number for the application (shown under the header “#”).

8 Manually busy the application software by typing

>BSY n
and pressing the Enter key.
where
n is the number under “#” of the application you wish to busy
Response:
The application is in service.
This command will cause a service interruption.
Do you wish to proceed?
Please confirm (“YES”, “Y”, “NO”, or “N”):
Note: Busying the application as shown performs an orderly shutdown and can
take up to 2 min.

9 Confirm the Busy command by typing

>Y
and pressing the Enter key.

10 After you confirm the Bsy command, the following is displayed:

Response:
Application Bsy – Command initiated.
Please wait...
When the Bsy command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Response:
Application Bsy – Command submitted.

11 Return the application to service by typing

>RTS n
and pressing the Enter key.
where
n is the number of the application (from step 8 )

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-119

Distributed Computing Environment

Removing port restrictions
Removing port restrictions
(continued)
(end)
Response:
Application RTS - Command initiated.
Please wait...
When the RTS command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Response:
Application RTS – Command submitted.

12 You have completed this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

6-120 SDM system administration procedures 6-120

Distributed Computing Environment

Restricting ports to a specific range

Application

ATTENTION
This procedure must be performed by a trained Distributed Computing
Environment (DCE) system administrator who knows DCE
administration procedures.

Use the following procedure to restrict the ports to a specific range. You
must have root user privileges to perform this procedure.

Action
The following flowchart provides an overview of the procedure. Use the
instructions in the step-action procedure that follows the flowchart to
perform the task.

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-121

Distributed Computing Environment

Restricting ports to a specific range (continued)
Summary of Restricting ports to a specific range

This flowchart summarizes the

Log in to the procedure.
SDM as the
root user Use the instructions that follow
this flowchart to perform the
procedure.
Restrict the
ports

Access the top

menu level of
the RMI

Access the
LAN menu
level

Access the
APPL menu
level

Busy the
application

Return the
application to
service

End

Wireless Networks Family SDM–SX User Guide SDMPL011

6-122 SDM system administration procedures

Distributed Computing Environment

Restricting ports to a specific range (continued)
Restricting ports to specific range
At the client workstation
1 Log in to the SDM as the root user

2 Restrict the ports to an SDM-defined range by typing

# restrict_dce_ports tcp a:b upd c:d
and pressing the Enter key.
where
a is the start of the range for TCP ports (must be greater than 1024
b is the end of the range for TCP ports (must be less than 32,000)
c is the start of the range for universal datagram protocol (UDP) ports (must
be greater than 1024)
d is the end of the range for UDP ports (must be less than 32,000)
Example response:
The following port ranges have been configured
TCP: 3000-3050 UDP: 3000-3050

3 Access the top menu level of the remote maintenance interface (RMI) by typing
# sdmmtc
and pressing the Enter key.

4 Access the LAN menu level of the RMI by typing

>LAN
and pressing the Enter key.

5 Wait for DCE to go to InSv. This may take several minutes.

Response:
DCE State: InSv

6 Access the application (APPL) menu level of the RMI by typing

>APPL
and pressing the Enter key.
Example response:
# Package Description Version State
1 Table Access Service 10.0.29.0 InSv
2 OM Access Service 10.0.29.0 InSv
3 Log Delivery Service 10.0.29.0 InSv

297-5061-901 Standard 01.01 December 1998

 SDM system administration procedures 6-123

Distributed Computing Environment

Restricting ports to a specific range (continued)

7 Determine the key number for the application (shown under the header “#”).

8 Manually busy the application software by typing

>BSY n
and pressing the Enter key.
where
n is the number under “#” of the application you wish to busy
Response:
The application is in service.
This command will cause a service interruption.
Do you wish to proceed?
Please confirm (“YES”, “Y”, “NO”, or “N”):
Note: Busying the application as shown performs an orderly shutdown and can
take up to 2 min.

9 Confirm the Busy command by typing

>Y
and pressing the Enter key.

10 After you confirm the Bsy command, the following is displayed:

Response:
Application Bsy – Command initiated.
Please wait...
When the Bsy command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Response:
Application Bsy – Command submitted.

11 Return the application to service by typing

>RTS n
and pressing the Enter key.
where
n is the number of the application (from step 8 )

Wireless Networks Family SDM–SX User Guide SDMPL011

6-124 SDM system administration procedures

Distributed Computing Environment

Restricting ports to a specific range (continued)
(end)
Response:
Application RTS - Command initiated.
Please wait...
When the RTS command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Response:
Application RTS – Command submitted.

12 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 7-1

SDM commissioning procedures

This chapter describes how to use the SuperNode Data Manager (SDM)
commissioning tool. You require root user privileges to perform the
commissioning procedures.

ATTENTION
The information in this chapter is intended for SDM system
administrators who have root user privileges. Nortel recommends that
SDM system administrators have specialized Advanced Interactive
Executive (AIX) training before performing system administration
procedures.

Accessing the SDM commissioning tool

You can access the commissioning tool from the local console. See the
procedure, “Starting the commissioning tool”, in this chapter. You cannot
access the commissioning tool from the MAP display or by remote login to
the SDM using the SDMRLOGIN command.

Performing tasks with the SDM commissioning tool

Use the commissioning tool to do the following:
• configure connectivity between the computing module (CM) and the
SDM
• configure connectivity to the operating company local area network
(LAN)
• set remote nodes on the operating company LAN to be monitored by the
SDM
• enable or disable file transfer protocol (FTP) and telnet access to the
SDM
• configure the distributed computing environment (DCE)
• set the console login prompt

Wireless Networks Family SDM–SX User Guide SDMPL011

7-2 SDM maintenance procedures

• configure maintenance (maint) and root userIDs

• set the date, time, and time zone of the system

Commissioning tool procedures

The first procedure, “Starting the commissioning tool”, describes how to
start the commissioning tool and how to use it to begin initial
commissioning of an SDM. The first procedure also describes how to
control the re-commissioning of an SDM.

The remaining procedures describe manual commissioning tasks. You

execute these procedures in sequence during initial commissioning of an
SDM. You select these procedures from a menu for individual execution
during recomissioning of an SDM. These procedures include commissioning
of the following:
• CM-SDM connectivity
• LAN connectivity
• LAN nodes
• LAN security
• DCE
• miscellaneous commissioning items:
— login greeting
— password
— date, time, and time zone

Manual commissioning input requirements

The manual commissioning procedures require you to enter site-specific
information for each commissioning task.

You must know the following information to commission CM-SDM

connectivity for the first time:
• CM Internet protocol (IP) address
• SDM IP address
• netmask for the CM-SDM LAN
• CM common-language location identifier (CLLI)
You must know the following information to commission LAN connectivity
for the first time:
• SDM hostname
• SDM LAN IP address

297-5061-901 Standard 01.01 December 1998

 SDM maintenance procedures 7-3

• SDM LAN netmask

• SDM LAN type
• SDM LAN gateway IP address (if a gateway is required)

You must know the following information to commission LAN nodes for the
first time:
• hostnames for the LAN nodes you want to commission
• IP addresses for the LAN nodes you want to commission

You must know the following information to commission DCE for the first
time:
• DCE cell name
• IP address and hostname of the master security server
• IP address and hostname of the cell directory server (CDS) server
• LAN profile for the SDM
• DCE principal name
• DCE principal (or equivalent) password

Each time you proceed with a particular task, the SDM prompts you for
values. After you enter all the values, the SDM prompts you to confirm the
values you have entered. If you enter an incorrect value, an error message
indicating a problem appears. The system prompts you again for the
information and provides you with an abort option. At the end of each task
(except for setting passwords), the system displays a summary of the values
you entered. At this time, you have a final opportunity to change the values.

During initial commissioning, you can defer some manual commissioning

tasks to a later time. At the end of the initial commissioning process, a
menu appears indicating the status of each manual commissioning task. The
commissioning tool then allows you to commission any item you have
deferred, or to recommission any of the items.

Anytime after initial commissioning, you can change some or all of the
SDM commissioning values by using the commissioning tool.

Wireless Networks Family SDM–SX User Guide SDMPL011

7-4 Commissioning the SDM 7-4

Starting the commissioning tool

Application
Use this procedure to start the commissioning tool, either to commission the
SDM for the first time or to re-commission it.

If you are commissioning the SDM for the first time, you invoke an
automated procedure that runs all commissioning tasks not requiring input
information. Once the automated procedure is complete, you execute in
sequence several manual commissioning tasks that require additional
information from you.

If you are re-commissioning the SDM, you access the menu for running
commissioning tasks requiring input information directly. The automated
procedure does not need to be re-executed when re-commissioning the
SDM.

Note: During initial commissioning, some manual tasks offer you the option
of deferring them to a later time or date. You can execute deferred tasks
anytime after initial commissioning is completed. However, it is advisable
however, not to defer manual commissioning tasks.

Action
The following flowchart summarizes the procedure. Use the instructions in
the step-action procedure that follows the flowchart to perform the task.

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-5

Starting the commissioning tool (continued)

Summary of Starting the commissioning tool

This flowchart summarizes the

procedure.
Initial N Use the instructions in the
commissioning of procedure that follows this
the SDM ? flowchart to perform the
Y procedure.
Enter
Automated
sdmconfig
commissioning
executes
Enter the menu
number of a
Start next manual manual
commissioning task commissioning
task

Provide input
information as Provide input
required by the information as
task required by the
task

Task executes
Task
executes

N Y Want to run Y
Last task? another task?

N
End

Wireless Networks Family SDM–SX User Guide SDMPL011

7-6 Commissioning the SDM

Starting the commissioning tool (continued)

Procedure 7-1: Starting the commissioning tool
At the local VT100 console
1 Proceed according to whether you are commissioning the SDM for the first time
or recommissioning the SDM.

If you Do

are commissioning the SDM for the first step 2

time
are recommissioning the SDM step 5

2 The commissioning tool is invoked automatically following base software

installation. The system responds as follows:
SDM COMMISSIONING

You are about to commission this system as a Supernode

Data Manager (SDM).
If you choose to proceed, a series of commissioning tasks
will be
performed automatically.
Once the automated commissioning tasks have completed
successfully, the
following tasks can be completed manually:
– CM–SDM connectivity
– LAN connectivity
– LAN nodes
– LAN security
– DCE configuration
– Miscellaneous
– Login greeting
– Root and maint user passwords
– Date, time and time zone

Do you wish to proceed?

Please confirm (”YES”, ”Y”, ”NO”, or ”N”)

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-7

Starting the commissioning tool (continued)

3 Begin the automated commissioning tasks by typing
>Y
and pressing the Enter key.
Response:
SDM COMMISSIONING

Determining Platform Type – PASSED (system detected

as SX)

Creating sdm.modules file – PASSED

Checking Module Positions – PASSED

Commissioning Default Groups – PASSED

Commissioning File Systems – PASSED

Commissioning SDM Directories – PASSED

Commissioning Default Users – PASSED

Commissioning SDM Environment – PASSED

HIT ENTER TO CONTINUE

4 Press the Enter key when you are ready to continue with the manual
commissioning tasks that require site specific information. Go to the next
procedure in this chapter, “Commissioning CM-SDM connectivity.”

5 Begin recommissioning by typing

# sdmconfig
and pressing the Enter key.

Wireless Networks Family SDM–SX User Guide SDMPL011

7-8 Commissioning the SDM

Starting the commissioning tool (end)

(continued)

6 The system responds by displaying the SDM commissioning status menu.

Example response:
SDM COMMISSIONING
SDM COMMISSIONING STATUS MENU

0 Exit
1 CM-SDM connectivity PASSED
2 LAN connectivity PASSED
3 LAN nodes PASSED
4 LAN security PASSED
5 DCE configuration PASSED
6 Login greeting hello SDM!
7 Date & time zone Wed May 6 1998 EST5EDT

Please enter your selection (0–7):

7 Enter the menu number of the task you wish to execute by typing
>n
and pressing the Enter key.
where
n is the menu number of the task you wish to execute
Follow the procedure in this chapter that corresponds to the menu item you
choose. When you finish each procedure, the SDM commissioning status menu
opens.

8 Choose another commissioning task or press 0 to exit.

9 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 7-9 Commissioning the SDM 7-9

Commissioning CM-SDM connectivity

Application
Use this procedure to commission CM-SDM connectivity.

You must know the following information to commission CM-SDM

connectivity for the first time:
• CM IP address
• SDM IP address
• netmask for the CM-SDM LAN
• CM CLLI

Defining IP addresses for the SDM to CM LAN

The parameters for the SDM to CM LAN are configured when Nortel
initially commissions the SDM. The initial commissioning establishes the
IP addresses for the CM, the DS512 interface, and the CM side of the SDM.
The IP addresses must be consistent with the entries in the DMS data
schema tables SDMINV and IPNETWRK that control CM to SDM
connectivity.

Action
The following flowchart summarizes the procedure. Use the instructions in
the step-action procedure that follows the flowchart to perform the task.

Wireless Networks Family SDM–SX User Guide SDMPL011

7-10 Commissioning the SDM

Commissioning CM-SDM connectivity (continued)

Summary of Commissioning CM-SDM connectivity

This flowchart summarizes the

procedure.

Use the instructions in the

1 procedure that follows this
2
flowchart to perform the
Determine if you procedure.
wish to proceed Enter the CM
IP address

Continue
CM-SDM N Enter the SDM IP
commission? address

Y
2
Enter the
CM-SDM
netmask

Enter the CM
CLLI

Are the N
values 1
correct?
Y

Confirm the
values

End

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-11

Commissioning CM-SDM connectivity (continued)

Commissioning CM-SDM connectivity
At the local VT100 console
1 At the start of the manual commissioning of CM-SDM connectivity, one of the
following appears.
If you are performing an initial commissioning of the CM-SDM connectivity, the
following CM-SDM connectivity preview window appears:
SDM COMMISSIONING
CM–SDM CONNECTIVITY

You will be prompted for the following information:

– CM IP address
– SDM IP address
– CM-SDM netmask
– CM CLLI

Do you wish to proceed?

Please confirm (”YES”, ”Y”, ”NO”, or ”N”)
If you are recommissioning the CM-SDM connectivity, the system displays the
CM-SDM connectivity preview window with the current values.

Example response:
SDM COMMISSIONING
CM–SDM CONNECTIVITY

The current CM-SDM connectivity values are:

– CM IP address: 47.31.195.1
– SDM IP address: 47.31.195.1
– CM-SDM netmask: 255.255.0.0
– CM CLLI: FCC4

Do you wish to recommission?

Please confirm (”YES”, ”Y”, ”NO”, or ”N”)

2 Proceed according to whether you want to continue with CM-SDM connectivity

commissioning:

If you Go to

do not want to continue step 3

want to continue step 4

Wireless Networks Family SDM–SX User Guide SDMPL011

7-12 Commissioning the SDM

Commissioning CM-SDM connectivity (continued)

3 To discontinue commissioning CM-SDM connectivity, type
>N
and press the Enter key.
If you are performing initial commissioning of CM-SDM connectivity, the system
responds with the following prompt:
SDM COMMISSIONING
CM–SDM CONNECTIVITY

The commissioning of the CM-SDM connection has been

deferred.

This task can be commissioned at a later time through

the SDM commissioning status menu.

HIT ENTER TO CONTINUE

In that case, go to step 12.
If you are recommissioning CM-SDM connectivity, this prompt is not displayed.
In that case, go to step 13.

4 To continue with commissioning CM-SDM connectivity, type

>Y
and press the Enter key.
If you are doing initial commissioning, the system responds with the message:
Installing DS512 device driver...please wait...

There iss a waiting period of 5 to 10 minutes. The above message and the
waiting period are not observed if you are recommissioning the SDM.

The system responds with the following prompt:

Please enter the CM IP address:
If you are recommissioning the system, the current values are already
available. The current value appears in square [ ] brackets at the end of each
prompt. To accept this value, press the Enter key. Steps 5 through 8 tell you
how to change the current values.

5 Enter the CM IP address by typing

>address
and pressing the Enter key.
where
address is the IP address of the CM that you are commissioning
The system responds with the following prompt:
Please enter the SDM IP address:

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-13

Commissioning CM-SDM connectivity (continued)

6 Enter the SDM IP address by typing

>address
and pressing the Enter key.
where
SDM IP address is the IP address of the SDM that you are
commissioning
The system responds with the following prompt:
Please enter the CM-SDM netmask:

7 Enter the CM-SDM netmask by typing

>netmask
and pressing the Enter key.
where
netmask is the CM-SDM netmask of the CM-SDM that you
are commissioning
The system responds with the following prompt:
Please enter the CM CLLI:

8 Enter the CM CLLI by typing

>clli
and pressing the Enter key.
where
clli is the CM CLLI that you are commissioning
Example response:
CM–SDM CONNECTIVITY

The following values have been entered:

CM IP address: 47.105.150.1
SDM IP address: 47.105.150.6
CM–SDM netmask: 255.255.255.248
CM CLLI: FCC11

Are these values correct?

Please confirm (”YES”, ”Y”, ”NO”, or ”N”)

Wireless Networks Family SDM–SX User Guide SDMPL011

7-14 Commissioning the SDM

Commissioning CM-SDM connectivity (end)

(continued)

9 Proceed according to whether the values are correct.

If you wish to Do

cancel or change a value step 10

accept the values step 11

10 To change a value, type

>N
and press the Enter key.
Go to step 1.

11 Confirm the CM-SDM connectivity values by typing

>Y
and pressing the Enter key.
Response:
Commissioning CM–SDM connectivity – PASSED

HIT ENTER TO CONTINUE

Note: If commissioning fails, check the values and repeat this procedure.

12 Press the Enter key.

13 You have completed the CM-SDM connectivity commissioning.

If you are performing initial commissioning, the system displays the prompt for
the next manual commissioning task, the LAN connectivity preview window. Go
to the next procedure in this chapter, “Commissioning LAN connectivity”.
If you are recommissioning the SDM, the system returns to the SDM
commissioning status menu. Return to step 6 of the procedure “Starting the
commissioning tool” in this chapter.

297-5061-901 Standard 01.01 December 1998

 7-15 Commissioning the SDM 7-15

Commissioning LAN connectivity

Application
Use this procedure to commission LAN connectivity.

You must know the following information to commission LAN connectivity

for the first time:
• SDM hostname
• SDM LAN IP address
• SDM LAN netmask
• SDM LAN type
• SDM LAN gateway IP address (if a gateway is required)

Note: You must perform this procedure before commissioning either LAN
nodes or the DCE. For information on commissioning LAN nodes, refer to
the procedure “Commissioning LAN nodes”, in Chapter 7. For information
on commissioning DCE, refer to the procedure, “Configuring DCE ”, in
chapter 7.

Action
The following flowchart summarizes the procedure. Use the instructions in
the step-action procedure that follows the flowchart to perform the task.

Wireless Networks Family SDM–SX User Guide SDMPL011

7-16 Commissioning the SDM

Commissioning LAN connectivity (continued)

Summary of Commissioning LAN connectivity

1 This flowchart summarizes the

Determine if you Continue LAN procedure.
wish to proceed N
connectivity 2
commissioning? Use the instructions in the
procedure that follows this
Y flowchart to perform the
procedure.
Enter the SDM
hostname

Enter the SDM

LAN IP
address

Enter the SDM

LAN netmask

Enter the SDM

LAN type

Need to enter N Are the N

SDM LAN gateway values 1
IP address? correct?

Y Y

Enter the SDM Confirm LAN

LAN gateway connectivity
IP address values

3
End
2

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-17

Commissioning LAN connectivity (continued)

Commissioning LAN connectivity
At the local VT100 console
1 At the start of the manual commissioning of LAN connectivity, one of the
following appears.
If you are performing an initial commissioning of LAN connectivity, the system
displays the following LAN connectivity preview window:
SDM COMMISSIONING
LAN CONNECTIVITY

You will be prompted for the following information:

– SDM hostname
– SDM LAN IP address
– SDM LAN netmask
– SDM LAN type
– SDM LAN gateway (OPTIONAL)

Do you wish to proceed?

Please confirm (”YES”, ”Y”, ”NO”, or ”N”)

If you are recommissioning LAN connectivity, the system displays the LAN
connectivity preview window with the current values.

Example response:
SDM COMMISSIONING
LAN CONNECTIVITY

You will be prompted for the following information:

– SDM hostname: bmerye76

– SDM LAN IP address: 47.105.144.30
– SDM LAN netmask: 255.255.240.0
– SDM LAN type: Standard
– SDM LAN gateway: (not entered)

Do you wish to recommission?

Please confirm (”YES”, ”Y”, ”NO”, or ”N”)

2 Proceed according to whether you want to commission LAN connectivity.

If you Do

do not want to continue step 3

want to continue step 4

Wireless Networks Family SDM–SX User Guide SDMPL011

7-18 Commissioning the SDM

Commissioning LAN connectivity (continued)

3 Avoid commissioning LAN connectivity by typing
>N
and pressing the Enter key.
The following response is displayed during initial commissioning of LAN
connectivity only:
SDM COMMISSIONING
LAN CONNECTIVITY

The commissioning of the LAN connection has been deferred.

This task can be commissioned at a later time through the

SDM commissioning status menu.

HIT ENTER TO CONTINUE.

In that case, go to step 14.

If you are recommissioning LAN connectivity, the above response is not
displayed. Go to step 15.

4 To proceed with commissioning LAN connectivity, type

>Y
and press the Enter key.
The system responds with the following prompt.

SDM COMMISSIONING
LAN CONNECTIVITY

Please enter the SDM hostname:

If you are recommissioning the SDM, the current values are already available.
The current value appears in square [ ] brackets at the end of each prompt. To
accept this value, press the Enter key. Steps 5 through 9 tell you how to
change the current values.

5 Enter the SDM hostname by typing

>hostname
and pressing the Enter key.
where
hostname is the SDM hostname to which you are commissioning LAN
connectivity
The system responds with the following prompt:
Please enter the SDM LAN IP address:

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-19

Commissioning LAN connectivity (continued)

6 Enter the SDM LAN IP address by typing
>address
and pressing the Enter key.
where
address is the IP address of the LAN that you are commissioning
The system responds with the following prompt:
Please enter the SDM LAN netmask:

7 Enter the LAN netmask by typing

>netmask
and pressing the Enter key.
where
netmask is the LAN netmask of the LAN that you are
commissioning
The system responds with the following prompt:
Please select the LAN type, either (S)tandard or (I)EEE
802.3:

8 Enter the SDM LAN type by typing

>type
and pressing the Enter key.
where
type is the LAN type of the LAN that you are commissioning
Note: The default setting for the SDM LAN type is “Standard”. You must
commission the SDM to the same Ethernet settings as your workstations and
DCE servers.

CAUTION
Risk of service interruption
If you do not know the correct SDM LAN type for
your network, contact your local LAN support
personnel. Once you choose an SDM to LAN
connection, you cannot change it without reinstalling
the operating system. If you reinstall the operating
system, you lose all existing information and you must
recommission the SDM. In addition, you must
reinstall and configure all SDM applications.

The system responds with the following prompt:

Wireless Networks Family SDM–SX User Guide SDMPL011

7-20 Commissioning the SDM

Commissioning LAN connectivity (continued)

Please enter the SDM LAN gateway IP: [No Gateway]

9 Proceed according to whether you are entering the SDM LAN gateway IP
address.

If you are Do

entering the SDM LAN gateway IP step 10

address
not entering the SDM LAN gateway IP step 11
address

10 Enter the SDM LAN gateway IP address by typing

>gateway address
and pressing the Enter key.
where
gateway address is the SDM LAN gateway IP address of the LAN
that you are commissioning
Go to step 12.

11 If you do not wish to enter a SDM LAN gateway IP address, press the Enter
key.

12 The system displays the LAN commissioning values you have entered.
Example response:
SDM COMMISSIONING
LAN CONNECTIVITY

The following values have been entered:

SDM hostname: bnode75

SDM LAN IP address: 47.105.144.29
SDM LAN netmask: 255.255.240.0
SDM LAN type: Standard
SDM LAN gateway: 47.105.144.1

Are these values correct?

Please confirm (”YES”, ”Y”, ”NO”, or ”N”)

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-21

Commissioning
Commissioning LAN LAN connectivity
connectivity (end)
(continued)
Proceed according to whether the values are correct.

If you wish to Do

change a value step 12

confirm the values step 13

13 To change a value, type

>N
and press the Enter key.
Go to step 1.

14 Confirm the LAN connectivity values by typing

>Y
and pressing the Enter key. The response may take up to 5 minutes to
complete.
Response:
Commissioning LAN connectivity – PASSED

HIT ENTER TO CONTINUE

15 Press the Enter key.

16 You have completed commissioning LAN connectivity.

If you are performing initial commissioning of the SDM, the system displays the
prompt for the next manual commissioning task, the LAN nodes commissioning
preview window. Go to the next procedure in this chapter, “Commissioning LAN
nodes”.
If you are recommissioning the SDM, the system returns to the SDM
commissioning status menu. Return to step 6 of the procedure “Starting the
commissioning tool” in this chapter.

Wireless Networks Family SDM–SX User Guide SDMPL011

7-22 Commissioning the SDM 7-22

Commissioning LAN nodes

Application
Use this procedure to commission LAN nodes. You can commission a
maximum of four LAN nodes.

You must know the following information to commission LAN nodes for the
first time:
• hostnames of the LAN nodes you want to commission
• IP addresses of the LAN nodes you want to commission

Note 1: This procedure does not include commissioning SDM-LAN

connectivity. You must perform the procedure, “Commissioning LAN
connectivity”, in this chapter before you commission LAN nodes.
Note 2: LAN nodes can also be defined at the remote maintenance interface
(RMI). For more information, see “Other commands at the LAN menu
level” in the “SDM maintenance overview” chapter.
Action
The following flowchart summarizes the procedure. Use the instructions in
the step-action procedure that follows the flowchart to perform the task.

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-23

Commissioning LAN nodes (continued)

Summary of Commissioning LAN nodes

This flowchart summarizes the

1 procedure.
Determine if
you wish to Select the LAN Use the instructions in the
proceed node number procedure that follows this
flowchart to perform the
procedure.

Continue the 2
N Has the node
LAN node Y been previously
1 Confirm LAN
commissioning? commissioned? connectivity
values
N Y
3 Do you want to
Y Commission Y
delete or 1
another
recommission
node?
the node?
N
N
Enter the Exit the LAN
description of nodes
the LAN node selection menu

Enter the End

hostname of 3
the LAN node

Enter the LAN

IP address of
the LAN node

Are the N
values 1
correct?
Y

Wireless Networks Family SDM–SX User Guide SDMPL011

7-24 Commissioning the SDM

Commissioning LAN nodes (continued)

Commissioning LAN nodes
At the local VT100 console
1 At the start of the manual commissioning of LAN nodes, one of the following
appears.
If you are performing an initial commissioning of LAN nodes, the system
displays the following LAN nodes commissioning preview window:
SDM COMMISSIONING
LAN NODES

You will be prompted for the following information:

– The description for 1–4 LAN nodes

– The hostname for 1–4 LAN nodes
– The IP address for 1–4 LAN nodes

Do you wish to proceed?

Please confirm (”YES”, ”Y”, ”NO”, or ”N”)
If you are recommissioning LAN nodes, the system displays the LAN nodes
commissioning preview window with the current values.

Example response:
SDM COMMISSIONING
LAN NODES

The current LAN node values are:

LAN node 1 description: my machine

LAN node 1 hostname: bmerh169
LAN node 1 IP address: 47.208.3.98
LAN node 2 description:
LAN node 2 hostname:
LAN node 2 IP address:
LAN node 3 description:
LAN node 3 hostname:
LAN node 3 IP address:
LAN node 4 description:
LAN node 4 hostname:
LAN node 4 IP address:

Do you wish to recommission?

Please confirm (”YES”, ”Y”, ”NO”, or ”N”)

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-25

Commissioning LAN nodes (continued)

2 Proceed according to whether you wish to commission the LAN nodes.

If you Do

do not want to continue step 3

want to continue step 4

3 To discontinue commissioning the LAN nodes, type

>N
and press the Enter key.
The following response appears during initial commissioning of LAN nodes
only:
LAN NODES

The commissioning of the LAN Nodes has been deferred.

This task can be commissioned at a later time through the

SDM Commissioning Status Menu.

HIT ENTER TO CONTINUE.

In that case, go to step 16.

If you are recommissioning a LAN node, the above response will not be
displayed. In that case, go to step 17.

4 To begin commissioning LAN nodes, type

>Y
and press the Enter key.
The system displays the LAN nodes selection menu.
Example response:
SDM COMMISSIONING
LAN NODES

0 EXIT
1 LAN node 1 UNCOMMISSIONED
2 LAN node 2 UNCOMMISSIONED
3 LAN node 3 UNCOMMISSIONED
4 LAN node 4 UNCOMMISSIONED

Please select the number of the LAN node you wish to commission (1-4):

Wireless Networks Family SDM–SX User Guide SDMPL011

7-26 Commissioning the SDM

Commissioning LAN nodes (continued)

5 Select the number of the LAN node by typing
>n
and pressing the Enter key.
where
n is the value 1 to 4 depending on which LAN node number you
wish to commission

6 If the node you have selected has not been commissioned, proceed to step 9.
Otherwise, the following message appears:

Please select either (C)ommission or (D)elete this LAN node?

If you Do

want to delete the LAN node step 7

want to re-commission the LAN node step 8

7 Select the delete option by typing

>d
and pressing the Enter key.
Go to step 14.

8 Select the commissioning option by typing

>c
and pressing the Enter key.
Note: Current values (if any) appear in square [] brackets at the end of each
prompt. To accept a value, press the Enter key. Steps 9 through 11 tell you how
to change the current values.
Example response:
Please enter the description for LAN node 1: [operating node]

9 Enter the description for the LAN node by typing

>node
and pressing the Enter key.
where
node is the description for the LAN node
Example response:
Please enter the hostname for LAN node 1: [bmerha83]

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-27

Commissioning LAN nodes (continued)

10 Enter the hostname for the LAN node by typing
>hostname
and pressing the Enter key.
where
hostname is the hostname for the LAN node
Example response:
Please enter the IP address for LAN node 1: [47.208.12.237]

11 Enter the IP address for the LAN node by typing

>address
and pressing the Enter key.
where
address is the IP address for the LAN node. The format is
xxx.xxx.xxx.xxx, where xxx is a number from 0 to 255.
Example response:
SDM COMMISSIONING
LAN NODES

The following values have been entered:

LAN node 1 description: my machine

LAN node 1 hostname: bmerh169
LAN node 1 IP address: 47.208.3.98

Are these values correct?

Please confirm (”YES”, ”Y”, ”NO”, or ”N”)

Proceed according to whether the values are correct

If you want to Do

change a value step 12

confirm the values step 13

12 To change a value, type

>N
and press the Enter key.
Go to step 14.

Wireless Networks Family SDM–SX User Guide SDMPL011

7-28 Commissioning the SDM

Commissioning LAN nodes (continued)

13 Confirm the LAN node values by typing
>Y
and pressing the Enter key.
Response:
Commissioning LAN node 1 – PASSED

HIT ENTER TO CONTINUE

14 Press the Enter key.

15 The system displays the LAN nodes selection menu.

Example response:
LAN NODES

0 EXIT
1 LAN node 1 COMMISSIONED
2 LAN node 2 UNCOMMISSIONED
3 LAN node 3 UNCOMMISSIONED
4 LAN node 4 UNCOMMISSIONED

Select the number of the LAN node you wish to commission (1–4):

Proceed according to the following.

If you Do

want to commission another LAN node step 5

or change values for a commissioned
LAN node
do not want to commission another LAN step 17
node or change any values

16 To finish commissioning LAN nodes, type

>0
and press the Enter key.

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-29

Commissioning
Commissioning LAN LAN nodes
nodes (end)
(continued)
The system displays the values for each LAN node.
Example response:
SDM COMMISSIONING
LAN NODES

The LAN Node commissioned values are as follows:

LAN node 1 description: my machine

LAN node 1 hostname: bmerh169
LAN node 1 IP address: 47.208.3.98

LAN node 2 description: Uncommissioned

LAN node 2 hostname: Uncommissioned
LAN node 2 IP address: Uncommissioned

LAN node 3 description: Uncommissioned

LAN node 3 hostname: Uncommissioned
LAN node 3 IP address: Uncommissioned

LAN node 4 description: Uncommissioned

LAN node 4 hostname: Uncommissioned
LAN node 4 IP address: Uncommissioned

HIT ENTER TO CONTINUE

17 Press the Enter key.

18 You have completed commissioning LAN nodes.

If you are performing initial commissioning of the SDM, the system displays the
prompt for the next manual commissioning task. The next task is the LAN
security preview window. Go to the next procedure in this chapter,
“Commissioning LAN security”.
If you are recommissioning the SDM, the SDM commissioning status menu
appears. Return to step 6 of the procedure, “Starting the Commissioning tool”,
in this chapter.

Wireless Networks Family SDM–SX User Guide SDMPL011

7-30 Commissioning the SDM 7-30

Commissioning LAN security

Application
Use this procedure to commission LAN security. This procedure lets you
enable or disable LAN security for inbound telnet and FTP connections.

Action
The following flowchart summarizes the procedure. Use the instructions in
the step-action procedure that follows the flowchart to perform the task.

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-31

Commissioning LAN security (continued)

Summary of Commissioning LAN security

This flowchart summarizes the

procedure.

Use the instructions in the

Determine if procedure that follows this
you wish to flowchart to perform the
proceed procedure.
1
Initial Y Enable or
commissioning? 1 disable telnet

Continue LAN N Enable or

security disable FTP
Commissioning?

Y
1
Are the
N
values 1
correct?
Y

Confirm LAN
security values

End

Wireless Networks Family SDM–SX User Guide SDMPL011

7-32 Commissioning the SDM

Commissioning LAN security (continued)

Commissioning LAN security

At the local VT100 console
At the start of the manual commissioning of LAN security, one of the following
appears.

1 If this is the first time you are commissioning LAN security, the system displays
the following LAN security preview window:
SDM COMMISSIONING
LAN SECURITY

You will be prompted for the following information:

– the security setting for Telnet (enabled or disabled)

– the security setting for FTP (enabled or disabled)

HIT ENTER TO CONTINUE

If you are recommissioning LAN security, the system displays the LAN security
preview window with the current values.

Example response:
SDM COMMISSIONING
LAN SECURITY

The current LAN security values are:

Inbound Telnet: ENABLED

Inbound FTP: DISABLED

Do you wish to recommission?

Please confirm (”YES”, ”Y”, ”NO”, or ”N”)
2 If you are performing the initial commissioning of the SDM, press the Enter key.
The system displays the following prompt:
Inbound Telnet:
Please select either (E)nable or (D)isable Telnet:

Go to step 5.
If you are recommissioning the SDM, proceed according to whether you want to
recommission LAN security.

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-33

Commissioning LAN security (continued)

If you want to Do

avoid recommissioning LAN security step 3

proceed with recommissioning LAN step 4
security

3 Avoid recommissioning LAN security by typing

>N
and pressing the Enter key.
Go to step 10.

4 To recommission LAN security, type

>Y
and press the Enter key.
The system displays the following prompt:
Inbound Telnet:
Please select either (E)nable or (D)isable Telnet:

5 Telnet can either be enabled or disabled at this point. Enable or disable telnet
by typing
>E
to enable telnet, or
>D
to disable telnet,
and pressing the Enter key.
The system displays the following prompt:
Inbound FTP
Please select either (E)nable or (D)isable FTP:
6 FTP can be enabled or disabled at this point. Enable or disable FTP by typing
>E
to enable FTP, or
>D
to disable FTP,
and pressing the Enter key.

Wireless Networks Family SDM–SX User Guide SDMPL011

7-34 Commissioning the SDM

Commissioning LAN security (end)

(continued)
Example response:
SDM COMMISSIONING
LAN SECURITY

The following values have been entered:

Inbound Telnet: ENABLED

Inbound FTP: DISABLED

Are these values correct?

Please confirm (”YES”, ”Y”, ”NO”, or ”N”)

Note: The values displayed reflect the choices you have entered.
Proceed according to whether the values are correct.

If you want to Do

change a value step 7

confirm the values step 8

7 To change a value, type

>N
and press the Enter key.
Go to step 1.

8 Confirm the LAN security values by typing

>Y
and pressing the Enter key.
Response:
Commissioning LAN security – PASSED

HIT ENTER TO CONTINUE

9 Press the Enter key.

10 You have completed commissioning LAN security.

If you are performing initial commissioning of the SDM, the system displays the
prompt for the next manual commissioning task, the DCE configuration preview
window. Go to the next procedure in this chapter, “Configuring DCE”.
If you are recommissioning the SDM, the system returns to the SDM
commissioning status menu. Return to step 6 of the procedure, “Starting the
Commissioning tool”, in this chapter.

297-5061-901 Standard 01.01 December 1998

 7-35 Commissioning the SDM 7-35

Configuring DCE

Application
Use this procedure to configure DCE.

You must know the following information to commission DCE for the first
time:
• DCE cell name
• IP address and hostname of the master security server
• IP address and hostname of the CDS server
• LAN profile name for the SDM
• DCE principal name
• DCE principal or equivalent password

Action
The following flowchart summarizes the procedure. Use the instructions in
the step-action procedure that follows the flowchart to perform the task.

Wireless Networks Family SDM–SX User Guide SDMPL011

7-36 Commissioning the SDM

Configuring DCE (continued)

Summary of Configuring DCE

1 2 This flowchart summarizes the

procedure.
Determine if Enter the DCE
you wish to principal name Use the instructions in the
proceed procedure that follows this
flowchart to perform the
procedure.
Enter the DCE
Continue N
cell name
configuring
DCE?

Y
Enter the IP
Select the address of the
DCE master security
configuration server

2 Enter the
hostname of
the master
security server

Enter the IP
address of the
CDS server 3

Confirm DCE
commissioning
Enter the LAN
values
profile name

Enter the
Are the password of
N the DCE
values 1
correct? administrator

Y
3
End

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-37

Configuring DCE (continued)

Configuring DCE
At the local VT100 console
1 At the start of manual configuration of DCE, one of the following appears.
If you are performing an initial commissioning of DCE, the system displays the
following DCE configuration preview window:
SDM COMMISSIONING
DCE CONFIGURATION

You will be asked to select:

– Local DCE configuration, or
– Full DCE configuration

After your selection, you will be prompted for the

following information:
- the DCE cell name
- the IP address and hostname of the master security
server
- the IP address and hostname of the CDS Server
- the LAN profile name for the SDM (FULL configuration
only)
- the DCE principal name (FULL configuration only)
- the DCE principal (or equivalent) password (FULL
configuration only)

Do you wish to proceed?

Please confirm (”YES”, ”Y”, ”NO”, or ”N”)
If you are recommissioning DCE, the system displays the preview window with
the current values.

Example response:
SDM COMMISSIONING
DCE CONFIGURATION

The current DCE values are:

DCE administrator principal name: cell_admin

DCE cell name: sdmdev.bnr.ca
DCE configuration: full
Master security server IP address: 47.105.144.21
Master security server hostname: bmerye6d
CDS server IP address: 47.105.144.21
CDS server hostname: bmerye6d
LAN profile name: lan-profile

Do you wish to recommission?

Please confirm (”YES”, ”Y”, ”NO”, or ”N”)

Wireless Networks Family SDM–SX User Guide SDMPL011

7-38 Commissioning the SDM

Configuring DCE (continued)

Note 1: DCE hostname is the hostname for the DCE server. If you enter a
different name, the DCE application server initialization can fail.
Note 2: LAN profile is the name of the DCE LAN profile that supports the
portion of the cell (LAN) where this SDM resides. The LAN profile defines the
local Distributed Time Service (DTS) servers that provide time synchronization
for the DCE nodes. For a small DCE cell, you can select the default LAN profile
(lan-profile). If you do so, all the nodes in the cell use the same set of DTS
local servers.

2 Proceed according to whether you wish to commission DCE.

If you want to Do

avoid DCE commissioning step 3

continue with DCE commissioning step 4

3 Avoid DCE commissioning by typing

>N
and pressing the Enter key.
For initial DCE commissioning only:
DCE CONFIGURATION

The commissioning of DCE has been deferred.

This task can be commissioned at a later time through the

SDM Commissioning Status Menu.

HIT ENTER TO CONTINUE.

In that case, go to step 15.
If you are recommissioning DCE, go to step 16.

4 To proceed with DCE commissioning, type

>Y
and press the Enter key.
The system displays the following prompt:
SDM COMMISSIONING
DCE CONFIGURATION

Please select either (L)ocal or (F)ull DCE commissioning:

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-39

Configuring DCE (continued)

5 Select full DCE configuration by typing
>F
and pressing the Enter key.
The system responds with the following prompt:
SDM COMMISSIONING
FULL DCE CONFIGURATION

Please enter the DCE principal name:[cell_admin]

Note: The value in square brackets [] is the default value. Press the Enter key
to use the default.

6 Enter the DCE principal name and press the Enter key.
The system responds with the following prompt:
Please enter the DCE cell name:

7 Enter the DCE cell name and press the Enter key.
The system responds with the following prompt:
Please enter the IP address of the master security server:

8 Enter the IP address of the master security server and press the Enter key.
The system responds with the following prompt:
Please enter the hostname of the master security server:

9 Enter the hostname of the master security server and press the Enter key.
The system responds with the following prompt:
Please enter the IP address of the CDS server:

10 Enter the IP address of the CDS server and press the Enter key.
The system responds with the following prompt:
Please enter the LAN profile name for the SDM:
[lan–profile]
Note: The value in square brackets [] is the default value. Press the Enter key
to see the defaults.

Wireless Networks Family SDM–SX User Guide SDMPL011

7-40 Commissioning the SDM

Configuring DCE (continued)

11 Enter the LAN profile name for the SDM and press the Enter key.
The DCE configuration values you have entered appear. The system prompts
you to confirm the values:

Example response:
SDM COMMISSIONING
FULL DCE CONFIGURATION

The following values have been entered:

DCE administrator principal name: cell_admin

DCE cell name: sdmdev.bnr.ca
Master security server IP address: 47.105.144.9
Master security server hostname: bnode61
CDS server IP address: 47.105.144.9
CDS server hostname: bnode61
LAN profile name: lan-red_105-profile

Are these values correct?

Please confirm (”YES”, ”Y”, ”NO”, or ”N”)
Proceed according to whether the values are correct.

If you wish to Do

change a value step 12

confirm the values step 13

12 To change a value, type

>N
and press the Enter key.
Go to step 1.

13 If the values are correct, type

>Y
and press the Enter key.
Full DCE configuration begins.
Example response:
Starting DCE commissioning...

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-41

Configuring
Configuring DCE DCE (end)
(continued)

14 The system prompts you to enter the password of the DCE administrator at the
beginning of the DCE configuration process. When you enter the password,
DCE configuration continues. The system displays various items on the screen
when they are successfully configured.
When DCE commissioning has finished, the system displays the following
message:
Example response:
DCE Commissioning PASSED

HIT ENTER TO CONTINUE

15 Press the Enter key.

16 You have completed the procedure.

If you are performing initial commissioning of the SDM, the system displays the
prompt for the next manual commissioning task, the miscellaneous preview
window. Go to the next procedure in this chapter, “Commissioning
miscellaneous items: login greeting and passwords.”
If you are recommissioning the SDM, the SDM commissioning status menu
appears. Return to step 6 of the procedure, “Starting the Commissioning tool”,
in this chapter.

Wireless Networks Family SDM–SX User Guide SDMPL011

7-42 Commissioning the SDM 7-42

Commissioning miscellaneous items:

login greeting and passwords

Application
Use this section to commission miscellaneous items on the SDM.

The following items are discussed in this section:

• login greeting
• passwords

Action
The following flowchart summarizes the procedure. Use the instructions in
the step-action procedure that follows the flowchart to perform the task.

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-43

Commissioning miscellaneous items:

login greeting and passwords (continued)
Summary of Commissioning miscellaneous items: login greeting and passwords

1 This flowchart summarizes the

Enter the login procedure.
greeting
Use the instructions in the
procedure that follows this
flowchart to perform the
procedure.
Is the
N 1
greeting
correct?
Y

Confirm the
greeting

Initial N End
commissioning?

Enter the root

user password

Reenter the
root user
password

Enter maint
user password

Reenter the
maint user 2
password

Wireless Networks Family SDM–SX User Guide SDMPL011

7-44 Commissioning the SDM

Commissioning miscellaneous items:

login greeting and passwords (continued)
Commissioning miscellaneous items: login greeting and passwords
At the local VT100 console
1 Proceed according to which items you are commissioning.

If you are Do

performing initial commissioning of step 2

miscellaneous items
recommissioning the login greeting step 3

Note: You cannot recommission passwords using the commissioning tool. For
information about changing a password, see the “Changing a user password”
section in chapter 3 of this document. For procedures on changing a user
password, see chapter 6 of this document.

2 The system displays the following miscellaneous preview menu:

SDM COMMISSIONING
MISCELLANEOUS

You will be prompted for the following information:

– SDM login greeting

– Passwords for root and maint users
– Date, time and time zone

HIT ENTER TO CONTINUE

Press the Enter key.

3 The system displays the following login greeting preview prompt:

SDM COMMISSIONING
LOGIN GREETING

Please enter the SDM login greeting: [SDM Console]

Enter the login greeting at the prompt by typing
>console
and pressing the Enter key.
where
console is the name of the SDM console
Note: Press the Enter key to use the default value shown in square [] brackets
after the prompt.
The system displays the following prompt:

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-45

Commissioning miscellaneous items:

login greeting and passwords (continued)
SDM COMMISSIONING
LOGIN GREETING

The following value has been entered:

SDM Login Greeting: SDM console

Is this value correct?

Please confirm (”YES”, ”Y”, ”NO”, or ”N”)

4 Proceed according to whether the value is correct.

If you wish to Do

change the value step 5

confirm the value step 6

5 To change a value, type

>N
and press the Enter key. The system returns you to step 3.

6 Confirm the login greeting value by typing

>Y
and pressing the Enter key.
Response:
Commissioning SDM login greeting – PASSED

HIT ENTER TO CONTINUE

If you are performing initial commissioning of miscellaneous items: login

greeting and passwords, go to step 7.
If you are recommissioning the login greeting, go to step 13.

Wireless Networks Family SDM–SX User Guide SDMPL011

7-46 Commissioning the SDM

Commissioning miscellaneous items:

login greeting and passwords (continued)

7 Press the Enter key.

The system displays the Passwords configuration preview window:
SDM COMMISSIONING
PASSWORDS

You will be prompted for the passwords for the ’root’ and
’maint’ users. You will have ONE minute to change each
password.

IMPORTANT: Do not lose the password for the ’root’ user!

HIT ENTER TO CONTINUE

8 Press the Enter key.

Response:
Changing password for ”root”
root’s New password:
9 Enter the new root user password by typing
>password
and pressing the Enter key.
where
password is a minimum six-character string containing at least one
alphabetic character, and at least one numeric or special
character. Although a password can contain more than eight
characters, the system considers only the first eight characters.
Response:
Enter the new password again:

10 Enter the new root user password again and press the Enter key.
The system prompts you to change the password for the maint user ID:
Changing password for ”maint”
maint’s New password:

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-47

Commissioning miscellaneous items:

login greeting and passwords (continued)

11 Enter the new maint user password by typing

>password
and pressing the Enter key.
where
password is a minimum six-character string containing at least one
alphabetic character, and at least one numeric or special
character. Although a password can contain more than eight
characters, the system considers only the first eight characters.
Response:
Enter the new password again:

12 Enter the new maintuser password again.

Response:
HIT ENTER TO CONTINUE

13 Press the Enter key.

14 You have completed this procedure.

If you are performing initial commissioning of the SDM, the system displays the
prompt for the next manual commissioning task, the date, time, and time zone
configuration preview window. Go to the next procedure in this chapter,
“Commissioning miscellaneous items: date, time, and time zone”.
If you are recommissioning the SDM, the system returns to the SDM
commissioning status menu. Return to step 6 of the procedure, “Starting the
commissioning tool”, in this chapter.

Wireless Networks Family SDM–SX User Guide SDMPL011

7-48 Commissioning the SDM 7-48

Commissioning miscellaneous items:

date, time, and time zone

Application
Use this procedure to commission the date, time, and time zone on the SDM.

Action
The following flowchart summarizes the procedure. Use the instructions in
the step-action procedure that follows the flowchart to perform the task.

CAUTION
Inability to recommission time zone
You must commission the time zone properly. With
the exception of initial commissioning, you do not
have the option of recommissioning the date, time,
and time zone if DCE is running and in service.

To recommission the date, time, and time zone, the node state must either be
ManB or OffL, and the node must not be DCE synchronized. Refer to the
procedure, “Distributed computing environment: Removing an SDM from a
DCE cell”, in chapter 6. This restriction does not apply to initial
commissioning.

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-49

Commissioning miscellaneous items:

date, time, and time zone (continued)
Summary of Commissioning miscellaneous items: date, time, and time zone

This flowchart summarizes the

procedure.
Choose the
DST option for Use the instructions in the
your region procedure that follows this
flowchart to perform the
procedure.
Choose the
time zone from
the CUT
screen

Exit the
command
status screen

Reboot the Y Reboot

SDM? executes

End

Wireless Networks Family SDM–SX User Guide SDMPL011

7-50 Commissioning the SDM

Commissioning miscellaneous items:

date, time, and time zone (continued)
Commissioning miscellaneous items: date, time, and time zones
At the local VT100 console
1 The system displays the prompt for the date, time, and time zone configuration
preview window.
SDM COMMISSIONING

DATE, TIME AND TIME ZONE

You will be prompted for time and date information. Once

you have entered the information, you will need to reboot
the SDM for the changes to take effect.

HIT ENTER TO CONTINUE

2 Press the Enter key.

The system displays the Change / Show Date, Time, and Time Zone screen.

Change / Show Date, Time, and Time Zone

Move cursor to desired item and press Enter.

Change / Show Date & Time

Change Time Zone Using System Defined Values
Change Time Zone Using User Entered Values

F1=Help F2=Refresh F3=Cancel F8=Image

F9=Shell F10=Exit Enter=Do

3 Proceed according to the daylight saving time conventions for your region.

If you Do

follow the daylight saving time step 5

conventions for North America
do not follow the daylight saving time step 4
conventions for North America

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-51

Commissioning miscellaneous items:

date, time, and time zone (continued)

Note: Under North American conventions, the move from standard time to
daylight saving time occurs on the first Sunday of April. On this day, clock time
is moved forward one hour at 2:00 a.m. The move from daylight saving time to
standard time occurs on the last Sunday of October. On this day, clock time is
moved backward one hour at 2:00 a.m.
Note: If you do not follow the North American daylight saving time zone
conventions, check with appropriate personnel for the dates and times that
daylight saving changes occur in your region.

4 Select Change Time Zone Using User Entered Values on the Change / Show
Date, Time, and Time Zone screen, and press the Enter key. The Change Time
Zone screen appears.

Change Time Zone

Type or select values in entry fields.

Press Enter AFTER making all desired changes.

[Entry Fields]
* Standard Time ID(only alphabets) [CST]
* Standard Time Offset from CUT ([+|–]HH:MM:SS) [–06:00:00]
Daylight Saving Time ID(only alphabets) [CDT]
Daylight Saving Time Offset from CUT ([+|–]HH:MM:SS) [05:00:00]
Start Daylight Saving Day ([Mmm.ww.dd|Jn]) [M04.1.00]
Start Daylight Saving Time(HH:MM:SS) [02:00:00]
Stop Daylight Saving Day([Mmm.ww.dd|Jn]) [M10.4.00]
Stop Daylight Saving Time(HH:MM:SS) [02:00:00]

F1=Help F2=Refresh F3=Cancel

F5=Reset F6=Command F7=Edit
F9=Shell F10=Exit

Use the up and down arrow keys to move the cursor and highlight the entries in
the entry fields. Change the value in the field after you highlight it. When you
finish changing the values in the fields, press the Enter key and go to step 9.
The following table explains each of the value fields in the Change Time Zone
window, and their formats.

Wireless Networks Family SDM–SX User Guide SDMPL011

7-52 Commissioning the SDM

Commissioning miscellaneous items:

date, time, and time zone (continued)

Field or subfield Value Description

Standard Time ID Alphabetic Any identifier you wish to use for

characters your region’s standard time.

Standard Time Identifies the value that must be

Offset from CUT added to or subtracted from local
standard time to equal Coordinated
Universal Time (CUT). This field
contains the subfields HH:MM:SS,
as follows.

[+|–] HH Range of integers Identifies the number of hours in the

(required) between –12 and offset, and whether to add or
+11 subtract the offset.
MM (optional) Numeric between Identifies the number of minutes in
0 and 59. Always the offset.
preceded by a
colon (:)
SS (optional) Numeric between Identifies the number of seconds in
0 and 59. Always the offset.
preceded by a
colon (:)

Daylight Saving Alphabetic Any identifier you want to use for

Time ID characters your region’s daylight saving time.

Daylight Saving Identifies the value that must be

Time Offset from added to or subtracted from local
CUT daylight time to equal CUT. This field
contains the subfields HH:MM:SS
(as explained under Standard Time
Offset from CUT, preceding.)

—continued—

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-53

Commissioning miscellaneous items:

date, time, and time zone (continued)

Field or subfield Value Description

Start Daylight Identifies the date on which daylight

Saving Day saving time starts. This field contains
the subfields Mmm.ww.dd or Jn, as
follows.

M Constant Indicates that the date is being

specified using the mm.ww.dd
subfields.
mm Numeric between Identifies the month.
1 and 12
ww Numeric between Identifies the number of the week
1 and 5 (one within the month, as follows:
digit), always
• 1 if the date falls on the 1st to
preceded by a
the 7th day
period (.)
• 2 if the date falls on the 8th to
the 14th day
• 3 if the date falls on the 15th to
the 21st day
• 4 if the date falls on the 22nd to
the 28th day
• 5 if the date falls on the 29th to
the 31st day
dd Numeric between Identifies the day of the week, as
0 and 6, always follows:
preceded by a
• 0 for Sunday
period (.)
• 1 for Monday
• 2 for Tuesday
• 3 for Wednesday
• 4 for Thursday
• 5 for Friday
• 6 for Saturday

—continued—

Wireless Networks Family SDM–SX User Guide SDMPL011

7-54 Commissioning the SDM

Commissioning miscellaneous items:

date, time, and time zone (continued)

Field or subfield Value Description

J Constant Indicates that the date string is being

specified using a 365-day calendar.
n Numeric between Indicates the number of the date in a
1 and 365 365-day calendar year.

Start Daylight None Identifies the time at which Daylight

Saving Time Saving Time starts. This field
contains the subfields HH:MM:SS
(as explained in Standard Time
Offset from CUT, preceding, but
without a plus or minus sign on the
HH subfield).
Stop Daylight None Identifies the date on which Daylight
Saving Day Saving Time stops. This field
contains the subfields Mmm.ww.dd
or Jn (as explained Start Daylight
Saving Day, preceding).
Stop Daylight Identifies the time at which Daylight
Saving Time Saving Time stops. This field
contains the subfields HH:MM:SS
(as explained in Standard Time
Offset from CUT, but without a plus
(+) or minus (–) sign on the HH
subfield).

—end—

5 Select Change Time Zone Using System Defined Values on the Change / Show
Date, Time, and Time Zone screen, and press the Enter key.

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-55

Commissioning miscellaneous items:

date, time, and time zone (continued)
The Use Daylight Savings Time? screen appears:

Use DAYLIGHT SAVINGS TIME?

Move cursor to desired item and press Enter.

# Does this time zone go on

# DAYLIGHT SAVING TIME?

1 yes
2 no

F1=Help F2=Refresh F3=Cancel

F8=Image F10=Exit Enter=Do
/=Find n=Find Next

6 Use the up and down arrow keys to select an option in response to the
question, “Does this time zone go on daylight saving time?” Select “yes” (option
1) if at some time in the year daylight saving time is applied to this time zone.
Otherwise, select “no” (option 2). Press the Enter key when you have selected
the appropriate response.
The system displays the CUT (Coordinated Universal Time) Time Zone screen:

Example response:

CUT (Coordinated Universal Time) Time Zone

Move cursor to desired item and press Enter.

[TOP]
(CUTOGDT) Coordinated Universal Time (CUT)
(GMTOBST) United Kingdom (CUT)
(AZOREST1AZOREDT) Azores; Cape Verde (CUT -1)
(FALKST2FALKDT) Falkland Islands (CUT -2)
(GRNLNDST3GRNLNDDT) Greenland; East Brazil (CUT -3)
(AST4ADT) Central Brazil (CUT -4)
(EST5EDT) Eastern U.S.; Colombia (CUT -5)
(CST6CT) Central U.S.; Honduras (CUT -6)
(MST7MDT) Mountain U.S. (CUT -7)
(PST8PDT) Pacific U.S.; Yukon (CUT -8)
[MORE...19]

F1=Help F2=Refresh F3=Cancel

F8=Image F10=Exit Enter=Do
/=Find n=Find Next

Wireless Networks Family SDM–SX User Guide SDMPL011

7-56 Commissioning the SDM

Commissioning miscellaneous items:

date, time, and time zone (continued)
Each option in the CUT Time Zone screen corresponds to a Greenwich Mean
Time (GMT) value, as shown in the following table.

Offset CUT
Name on screen Text on screen value on GMT value
screen
CUT0GDT Coordinated Universal Time CUT GMT
GNT0BST United Kingdom CUT GMT
AZOREST1AZOREDT Azores; Cape Verde CUT -1 GMT -01:00
FALKST2FALKDT Falkland Islands CUT -2 GMT -02:00
GRNLNDST3GRNLNDDT Greenland; East Brazil CUT -3 GMT -03:00
AST4ADT Central Brazil CUT -4 GMT -04:00
EST5EDT Eastern U.S.; Columbia CUT -5 GMT -05:00
CST6CDT Central U.S.; Honduras CUT -6 GMT -06:00
MST7MDT Mountain U.S. CUT -7 GMT -07:00
PST8PDT Pacific U.S.; Yukon CUT -8 GMT -08:00
AST9ADT Alaska CUT -9 GMT -09:00
HST10HDT Hawaii; Aleutian CUT -10 GMT -10:00
BST11BDT Bering Straits CUT -11 GMT -11:00
NZST–12NZDT New Zealand CUT +12 GMT +12:00
MET–11METDT Solomon Islands CUT +11 GMT +11:00
EET–10EETDT Eastern Australia CUT +10 GMT +10:00
JST–9JDT Japan CUT +9 GMT +09:00
KORST–9KORDT Korea CUT +9 GMT +09:00
WAUST–8WAUDT Western Australia CUT +8 GMT+08:00
TAIST–8TAIDT Taiwan CUT +8 GMT +08:00
THAIST–7THAIDT Thailand CUT +7 GMT +07:00
TASHST–6TASHDT Tashkent; Central Asia CUT +6 GMT +06:00
PAKST–5PAKDT Pakistan CUT +5 GMT +05:00
WST–4WDT Gorki, Central Asia; Oman CUT +4 GMT +04:00
MEST–3MEDT Turkey CUT +3 GMT +03:00

—continued—

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-57

Commissioning miscellaneous items:

date, time, and time zone (continued)

Offset CUT
Name on screen Text on screen value on GMT value
screen
SAUST–3SAUDT Saudi Arabia CUT +3 GMT +03:00
WET–2WET Finland CUT +2 GMT +02:00
USAST–2USADT South Africa CUT +2 GMT+ 02:00
NFT–1DFT Norway; France CUT +1 GMT +01:00

—end—

7 Use the up and down arrow keys to select the time zone you use. Then press
the Enter key. The Change Time Zone screen appears.

Change Time Zone

Type or select values in entry fields.

Press Enter AFTER making all desired changes.

[Entry Fields]
Time zone EST5EDT

Day Light Savings Time Offset from CUT ([+|–] HH:MM: []

SS)
Start Daylight Savings Day ([Mmm.ww.dd|Jn]) []
Start Daylight Savings Day (HH:MM:SS) []
Stop Daylight Savings Day ([Mmm.ww.dd|Jn]) []
Stop Daylight Savings Day (HH:MM:SS) []

F1=Help F2=Refresh F3=Cancel F4=List

F5=Reset F6=Command F7=Edit F8=Image
F9=Shell F10=Exit Enter=Do

8 You do not need to change the variables on the Change Time Zone screen.
Press the Enter Key.

Wireless Networks Family SDM–SX User Guide SDMPL011

7-58 Commissioning the SDM

Commissioning miscellaneous items:

date, time, and time zone (continued)

9 The Command Status screen appears. The command status is shown as

“running” while the changes are being processed. The command status
changes to “OK” when processing is complete. The date, time, and time zone
appear.
Example response:

COMMAND STATUS

Command: OK stdout: yes stderr: no

Before command completion, additional instructions may appear below.

Wed May 6 21:18:00 EDT 1998

Any changes made to the time zone will take effect at your next login
session.

F1=Help F2=Refresh F3=Cancel

F8=Image F10=Exit Enter=Do
/=Find n=Find Next

Note: If the command status changes to “Failed”, repeat this procedure.

10 Exit the Command Status screen by pressing the F10 key, Esc+10, or PF10
keys.
Response:
SDM COMMISSIONING
DATE , TIME AND TIME ZONE

Your time and date information has been entered. For this
information to take effect, you will need to reboot the
SDM.

Do you wish to reboot the SDM now?

Please confirm (”YES”, ”Y”, ”NO”, or ”N”)

If you wish to Do

defer rebooting the SDM step 11

reboot the SDM step 12

297-5061-901 Standard 01.01 December 1998

 Commissioning the SDM 7-59

Commissioning miscellaneous items:

date, time, and time zone (continued)

11 Defer rebooting the SDM by typing

>N
and pressing the Enter key.

You have completed commissioning miscellaneous items: date, time and time
zone. Go to step 6 of the procedure, “Starting the commissioning tool”, at the
beginning of this chapter.

12 To reboot the SDM, type

>Y
and press the Enter key. Wait until the reboot completes and the login prompt
reappears.

13 You have completed the procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

 8-1

SDM hardware upgrade procedures

This chapter contains SDM hardware upgrade procedures.
Each procedure contains the following:
• explanatory and context-setting information
• summary flowchart
• step-action instructions

Explanatory and context-setting information

The first page of each procedure contains the following headings:
• Application (why you perform the procedure)
• Impact (how the procedure affects service)
• Action (how to use the flowchart and step-action instructions)

Summary flowchart
The flowchart is only a summary of the main actions, decision points, and
possible paths you can take. Do not use the summary flowchart to perform
the procedure. Instead, use it to preview what you will be doing and to
prepare for it.

Step-action instructions
The step-action instructions tell you how to perform the procedure. The
successful completion of a step may depend on previous steps; therefore,
always perform the steps in the order specified.

The step-action instructions provide the command syntax and system

information you use or see while performing the procedure. For help on
DMS and SDM commands or output, see the “About this document” chapter
at the beginning of this document.

Return key and Enter key

The carriage return key is identified in different ways (such as Enter, Return
or Carriage Return) on various types of terminals. It is always used to enter
commands and parameters into the system.

Wireless Networks Family SDM–SX User Guide SDMPL011

8-2 SDM hardware upgrade procedures

The procedures contained in this book and in other NTPs instruct you to
press the Enter key after each step. If your terminal has a Return key, press
the Return key instead. Do not press the Enter key located beside the
numeric key pad.

297-5061-901 Standard 01.01 December 1998

 8-3 SDM hardware upgrade procedures 8-3

Upgrading the DS512 controller

module from NTRX50GA to NTRX50GX

Application
Use this procedure to perform the DS512 controller module upgrade from an
NTRX50GA to an NTRX50GX module.

Note 1: The NTRX50GA and NTRX50GX DS512 controller modules

function identically. The NTRX50GX DS512 controller module has
increased buffer memory with 16 kilobytes per link.
Note 2: The following limitation applies to the NTRX50GX DS512
controller module. The NTRX50GX DS512 controller module requires
software version SDMN0010 (or higher).
Before you begin this procedure, you must
• have an NTRX50GX controller module
• have packaging material in which to return the NTRX50GA controller
module

Impact
During this procedure, the SDM–SX system must be taken out of service.
All applications will be unavailable until the upgrade is completed.

Action
The following flowchart is only a summary of the procedure. To upgrade
the DS512 controller module, use the instructions in the step-action
procedure that follows the flowchart.

Wireless Networks Family SDM–SX User Guide SDMPL011

8-4 SDM hardware upgrade procedures

Upgrading the DS512 controller

module from NTRX50GA to NTRX50GX (continued)
Summary of Upgrading the DS512 controller module from NTRX50GA to NTRX50GX

This flowchart summarizes the

procedure.
Obtain the
replacement 1 Use the instructions in the
module procedure that follows this
Return the DS512 flowchart to perform the
module to service procedure.
Access the
SDM MAP
display level
Return the
DS512 links to
service
Busy the SDM

RTS the SDM

Manually busy
the DS512
links
End

Access
Manuallythe
busy
hardware
the DS512level
of the RMI
links

Manually busy
the DS512
module

Replace the
DS512 module
(slot 1)

297-5061-901 Standard 01.01 December 1998

 SDM hardware upgrade procedures 8-5

Upgrading the DS512 controller

module from NTRX50GA to NTRX50GX (continued)
Upgrading the DS512 controller module

1 Obtain an NTRX50GX DS512 controller module. Make sure that the upgrade
module has the correct product engineering code (PEC). The PEC is written on
the top locking lever of the module.

At the MAP display

2 Access the SDM MAP display level by typing
>MAPCI; MTC; APPL; SDM
and pressing the Enter key.

3 Display the card numbers that provide the DS512 links to the SDM by typing
>TRNSL
and pressing the Enter key.

Response:
SDM 0 PORT 0 (MS 0:15:0) OK MsgCnd:Open
SDM 1 PORT 1 (MS 1:15:0) OK MsgCnd:Open

4 Record the card number associated with the SDM DS512 links. The card
number is the middle number shown in the parentheses.
Note: In the example response shown in step 3, the card number is 15.

5 Manually busy the SDM by typing

>BSY
and pressing the Enter key.
Response:
SDM is in service.
This command will cause a service interruption.
Do you wish to proceed?
Please confirm (”YES”, ”Y”, ”NO, or ”N”)
6 Confirm the Busy command by typing
>Y
and pressing the Enter key.
Response:
SDM Bsy initiated.
SDM Bsy completed.

Wireless Networks Family SDM–SX User Guide SDMPL011

8-6 SDM hardware upgrade procedures

Upgrading the DS512 controller

module from NTRX50GA to NTRX50GX (continued)

7 Access the MS level of the MAP display by typing

>MS
and pressing the Enter key.

8 Access the shelf level by typing

>SHELF
and pressing the Enter key.

9 Access the card number level that is associated with the SDM DS512 links by
typing
>CHAIN cardno
and pressing the Enter key.
where
cardno is the card number recorded in step 4.
10 Manually busy the DS512 link between MS plane 0 and the SDM DS512
controller module you wish to replace by typing
>BSY 0 LINK 0
and pressing the Enter key.
Example response:
Request to MAN BUSY MS: 0 shelf: 0 chain:15 link: 0 submitted.
Request to MAN BUSY MS: 0 shelf: 0 chain:15 link: 0 passed.

Note: The state for the DS512 link changes to “M” for MS plane 0.

11 Manually busy the DS512 link between MS plane 1 and the SDM DS512
controller module you wish to replace by typing
>BSY 1 LINK 0
and pressing the Enter key.
Example response:
Request to MAN BUSY MS: 1 shelf: 0 chain:15 link: 0 submitted.
Request to MAN BUSY MS: 1 shelf: 0 chain:15 link: 0 passed.

Note: The state for the DS512 link changes to “M” for MS plane 1.

At the local or remote VT100 console

12 Log in to the SDM as the root or maint user.

297-5061-901 Standard 01.01 December 1998

 SDM hardware upgrade procedures 8-7

Upgrading the DS512 controller

module from NTRX50GA to NTRX50GX (continued)

13 Access the top menu level of the remote maintenance interface (RMI) by typing
# sdmmtc
and pressing the Enter key.

14 Access the hardware (Hw) menu level of the RMI by typing

>HW
and pressing the Enter key.

15 Manually busy the DS512 controller module by typing

>BSY 0 512 force
and pressing the Enter key.
Example response:
Hardware Bsy – Domain 0 Device 512

Do you wish to proceed?

Please confirm (“YES”, “Y”, “NO”, “N”)

16 Confirm the Busy command by typing

>Y
and pressing the Enter key.
Example response:
Hardware Bsy : Domain 0 Device 512 – Command initiated.
Please wait...
When the Bsy command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Example response:
Hardware Bsy : Domain 0 Device 512 – Command submitted.
Note: At the hardware menu level of the RMI, the state of the DS512
controller module changes to “M”.

At the front of the SDM

17
WARNING
Static electricity damage
Wear an electrostatic discharge (ESD) grounding wrist
strap connected to the C28B cabinet when handling a
module. This protects the module against damage
caused by static electricity.

Wireless Networks Family SDM–SX User Guide SDMPL011

8-8 SDM hardware upgrade procedures

Upgrading the DS512 controller

module from NTRX50GA to NTRX50GX (continued)
Locate the NTGX50GA card in slot 1.

18 Undo the thumbscrews located (if present) on the top and the bottom of the
DS512 controller module.
Note: The thumbscrews are the captive type, and cannot be removed from the
module.

19 Depress the tips of the locking levers on the face of the DS512 controller
module.

297-5061-901 Standard 01.01 December 1998

 SDM hardware upgrade procedures 8-9

Upgrading the DS512 controller

module from NTRX50GA to NTRX50GX (continued)

20 Open the locking levers on the face of the module by moving the levers
outwards.

Wireless Networks Family SDM–SX User Guide SDMPL011

8-10 SDM hardware upgrade procedures

Upgrading the DS512 controller

module from NTRX50GA to NTRX50GX (continued)

21 While grasping the locking levers, gently pull the module towards you until it
protrudes about 2 in. (5.1 cm) from the SDM shelf.

297-5061-901 Standard 01.01 December 1998

 SDM hardware upgrade procedures 8-11

Upgrading the DS512 controller

module from NTRX50GA to NTRX50GX (continued)

22 Hold the module by the face plate with one hand while supporting the bottom
edge with the other hand. Gently pull the module toward you until it clears the
shelf.

23 Place the module you have removed in an ESD protective container.

At the local or remote VT100 console

24 Exit from the RMI by typing
> quit all
and pressing the Enter key.
The system returns to the AIX prompt (#).

25 For the DS512 module you have removed, delete the information from the SDM
configuration database by typing
# ftds512clean 0
and pressing the Enter key.
At the front of the SDM
26 Insert the replacement module into the SDM shelf.

Wireless Networks Family SDM–SX User Guide SDMPL011

8-12 SDM hardware upgrade procedures

Upgrading the DS512 controller

module from NTRX50GA to NTRX50GX (continued)

27 Gently slide the module into the shelf until it is fully inserted.

297-5061-901 Standard 01.01 December 1998

 SDM hardware upgrade procedures 8-13

Upgrading the DS512 controller

module from NTRX50GA to NTRX50GX (continued)

28 To properly seat the module, make sure that both the top and bottom micro
switches are lined up with the levers. Close the locking levers to secure the
module.

Micro switch

29 Tighten the thumbscrews (if present) on the module.

Wireless Networks Family SDM–SX User Guide SDMPL011

8-14 SDM hardware upgrade procedures

Upgrading the DS512 controller

module from NTRX50GA to NTRX50GX (continued)
At the local or remote VT100 console
30 At the hardware level of the RMI, return the DS512 controller module to service
by typing
>RTS 0 512
and pressing the Enter key.
Example response:
Hardware RTS : Domain 0 Device 512 – Command initiated.
Please wait...
When the RTS command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Example response:
Hardware RTS : Domain 0 Device 512 – Command submitted.
Note: At the hardware menu level of the RMI, the state of the DS512 controller
module changes to a dot (.). This change indicates that the module has
returned to service. The in-service LED on the DS512 controller module is on
(green).

At the MAP display

31 Access the MS port module level of the MAP display (accessed in step 9).
Return to service the DS512 link between MS plane 0 and the DS512 controller
module you replaced by typing
>RTS 0 LINK 0
and pressing the Enter key.

Example response:
Request to RTS MS: 0 shelf: 0 chain:15 link: 0 submitted.
Request to RTS MS: 0 shelf: 0 chain:15 link: 0 passed.
Note: The state for the DS512 link changes to a dot (.) if the SDM DS512 link
is in service. Otherwise, the state for DS512 link changes to a “P”.

297-5061-901 Standard 01.01 December 1998

 SDM hardware upgrade procedures 8-15

Upgrading the DS512 controller

module fromfrom
module NTRX50GA to NTRX50GX
NTRX50GA to NTRX50GX
(continued)
(end)

32 Return to service the DS512 link between MS plane 1 and the DS512 controller
module you replaced by typing
>RTS 1 LINK 0
and pressing the Enter key.
Example response:
Request to RTS MS: 1 shelf: 0 chain:15 link: 1 submitted.
Request to RTS MS: 1 shelf: 0 chain:15 link: 1 passed.
Note: The state for the DS512 link changes to a dot (.) if the SDM DS512 link
is in-service. Otherwise, the state for DS512 link changes to a “P”.
When the Busy command is finished, the “Please wait...” message and the
command confirmation disappear. The word “initiated” also changes to
“submitted”.
Example response:
Hardware Bsy : Domain 1 Device 512 – Command submitted.
Note: At the hardware menu level of the RMI, the state of the DS512 controller
module changes to “M”.
At the MAP display
33 Return the SDM to service by typing
>RTS
and pressing the Enter key.
Response:
SDM RTS initiated.
SDM RTS completed.
The system automatically returns all modules to service.

34 You have completed this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

8-16 SDM hardware upgrade procedures 8-16

Upgrading the CPU controller

module NTRX50CF

Application
Use this procedure to upgrade or downgrade CPU controller modules.

The following CPU controller module upgrade path is supported. You can
upgrade to the NTRX50CG-200 MHz 604e CPU module with 256 MByte
DRAM from the following module:
• NTRX50CF 200-MHz 604e CPU module with 128 MByte DRAM

Note: The function of each of these CPU controller modules is identical.

Only the amount of memory and clock speed distinguish one CPU controller
module from another.

Impact
This procedure requires the complete shutdown of the SDM and all its
applications.

Action
The following flowchart is only a summary of the procedure. To upgrade
the CPU controller module, use the instructions in the step-action procedure
that follows the flowchart.

297-5061-901 Standard 01.01 December 1998

 SDM hardware upgrade procedures 8-17

Upgrading the CPU controller

module NTRX50CF (continued)
Summary of Upgrading or downgrading the CPU controller module

This flowchart summarizes the

Busy the SDM procedure.
from the APPL
level of MAP Use the instructions in the
procedure that follows this
flowchart to perform the
Log in to the procedure.
SDM as the
root user
1 2

Delete the Restore power Boot the SDM Extend paging

CPU database to the SDM from the disk space (for
information upgrades only)

Shut down the GMT Y At the prompt, Verify page

SDM and correct? log in as the spacing
initiate reboot root user
N

Determine the Correct the Restore the N Upgrading

GMT for the time setting bootlist firmware?
CPU
Y

Upgrading N End. Go to
Turn off MSP
breakers CPU? “Upgrading
CPU firmware”
Y
2
Replace CPU Return the
controller SDM to service
module

1
End

Wireless Networks Family SDM–SX User Guide SDMPL011

8-18 SDM hardware upgrade procedures

Upgrading the CPU controller

module NTRX50CF (continued)
Upgrading or downgrading the CPU controller module

1 Access the SDM level of the MAP display by typing

>MAPCI; MTC; APPL;SDM
and pressing the Enter key.
Example response:
SDM InSv
2 Manually busy the SDM by typing
>BSY
and pressing the Enter key.
Response:
SDM is in service.
This command will cause a service interruption.
Do you wish to proceed?
Please confirm (“YES”, “Y”, “NO”, or “N”)

3 Confirm the Busy command by typing

>Y
and pressing the Enter key.
Response:
SDM Bsy initiated.
SDM Bsy completed.
At the local or remote VT100 console
4 Log in to the SDM as the root user.

5 Delete the SDM configuration database information for the CPU controller
modules currently installed on the system by typing
# ftcpuclean
and pressing the Enter key.

6 Shut down the SDM and initiate a reboot by typing

# shutdown –Fr
and pressing the Enter key.

7 Interrupt the boot process when the “COLD start” message appears by pressing
the Break key.
Example response:
FX-Bug>
Note: The “COLD start” message does not appear for about 2 min.

297-5061-901 Standard 01.01 December 1998

 SDM hardware upgrade procedures 8-19

Upgrading the CPU controller

module NTRX50CF (continued)

8 Determine the current Greenwich Mean Time (GMT) setting on the existing
CPU controller modules by typing
FX–Bug>time
and pressing the Enter key.
Example response:
FRI APR 11 18:41:49:00

Note: The time setting is the correct GMT setting. It does not necessarily
reflect the local date and time.

9 Record the date and time response.

Note: If you are using a clock set to your local time to set the GMT on the new
CPU controller modules, use the response in step 8 to calculate the number of
hours that your local time differs from GMT.

At the modular supervisory panel (MSP)

10 Interrupt power to the SDM by turning off the domain 0 breaker. The MSP
breakers, located at the front of the MSP, supply power to the SDM.

At the front of the SDM

11 You must replace the CPU controller modules one at a time using the
instructions that follow. If you are upgrading CPU–0 in domain 0, remove the
CPU controller module from slots 6 and 7. If you are upgrading CPU–2 in
domain 1, remove the CPU controller module from slots 10 and 11.

WARNING
Static electricity damage
Wear an electrostatic discharge (ESD) grounding wrist
strap connected to the C28B cabinet when handling a
module. This protects the module against damage
caused by static electricity.

Undo the thumbscrews located on the top and the bottom of the CPU controller
module.
Note: The thumbscrews are the captive type, and cannot be removed from the
module.

Wireless Networks Family SDM–SX User Guide SDMPL011

8-20 SDM hardware upgrade procedures

Upgrading the CPU controller

module NTRX50CF (continued)

12 Depress the tips of the locking levers on the face of the CPU controller module.

297-5061-901 Standard 01.01 December 1998

 SDM hardware upgrade procedures 8-21

Upgrading the CPU controller

module NTRX50CF (continued)

13 Open the locking levers on the face of the module by moving the levers
outwards.

Wireless Networks Family SDM–SX User Guide SDMPL011

8-22 SDM hardware upgrade procedures

Upgrading the CPU controller

module NTRX50CF (continued)

14 While grasping the locking levers, gently pull the module towards you until it
protrudes about 2 in. (5.1 cm) from the SDM shelf.

297-5061-901 Standard 01.01 December 1998

 SDM hardware upgrade procedures 8-23

Upgrading the CPU controller

module NTRX50CF (continued)

15 Hold the module by the face plate with one hand while supporting the bottom
edge with the other hand. Gently pull the module toward you until it clears the
shelf.

16 Place the module you have removed in an ESD protective container.

17 Insert the replacement module into the SDM shelf.

Wireless Networks Family SDM–SX User Guide SDMPL011

8-24 SDM hardware upgrade procedures

Upgrading the CPU controller

module NTRX50CF (continued)

18 Gently slide the module into the shelf until it is fully inserted.

297-5061-901 Standard 01.01 December 1998

 SDM hardware upgrade procedures 8-25

Upgrading the CPU controller

module NTRX50CF (continued)

19 Close the locking levers to secure the module. Ensure that both the top and
bottom micro switches are lined up with the locking levers to properly seat the
module.

Micro switch

20 Tighten the thumbscrews on the module.

At the MSP
21 Restore power to the SDM by turning on the domin 0 breaker.
Note: When you restore power, both LEDs on the modules turn on briefly, then
off. This action indicates that the module is seated correctly, is receiving power,
and has passed its self tests. After about 1 min the in-service light on the CPU
controller module turns on. The out-of-service light remains off.

At the local or remote VT100 console

22 Interrupt the boot process when the “COLD start” message appears by pressing
the Break key.
Example response:
FX-Bug>

Wireless Networks Family SDM–SX User Guide SDMPL011

8-26 SDM hardware upgrade procedures

Upgrading the CPU controller

module NTRX50CF (continued)
Note: The “COLD start” message appears within about 5 min.

23 Determine the current Greenwich Mean Time (GMT) setting on the new CPU
controller modules by typing
FX–Bug>time
and pressing the Enter key.
Example response:
FRI APR 11 18:21:41:00

24 Determine if the GMT setting for the new CPU controller modules is correct.

If the GMT setting is Do

incorrect step 25
correct step 26

25 Correct the time setting to the current GMT by typing

FX–Bug>set mmddyyhhmm
and pressing the Enter key.
where
mm is the the numeric month of the year (01 to 12)
dd is the the numeric day of the month (01 to 31)
yy is the the last two digits of the current year (00 to 99)
hh is the current hour (00 to 23)
mm is the current minute (00 to 59)

CAUTION
Potential loss of service
Ensure that the GMT setting on the new CPU
controller modules is later than the setting on the
previous modules. See step 9. Do not reboot the
system if the GMT setting is earlier than the time of
the shut down. This action can corrupt the system
configuration and status information.

297-5061-901 Standard 01.01 December 1998

 SDM hardware upgrade procedures 8-27

Upgrading the CPU controller

module NTRX50CF (continued)

26 Boot the SDM from disk by typing

FX–Bug>pboot 1 0
and pressing the Enter key.

27 Allow the reboot to continue uninterrupted.

28
At the login prompt, log in to the SDM as the root user.

29 Restore the bootlist by typing

# bootlist –m normal hdisk0
and pressing the Enter key.

30 Log in to the RMI by typing

# sdmmtc
and pressing the Enter key.

31 Determine if you are upgrading or downgrading a module.

If Go to

you are upgrading a module step 32

you are downgrading a module step 34

32 Extend the paging space by typing

# sdmconfig cpu
and pressing the Enter key.
The paging space is now reset at twice the memory size of the CPU.
1‘
33 Verify that you have sufficient paging space by typing
# lsps –a
and pressing the Enter key.
Example response of paging space for a 128-MByte system:
Page Space Physical Volume Volume Group Size %Used
Active Auto Type
hd6 hdisk0 rootvg 256MB 23
yes yes lv
In the example, the Size (of memory) column displays twice the memory size of
the CPU. A system with a CPU with 128 MBytes of memory must have a
paging space memory of 256 MBytes.

Wireless Networks Family SDM–SX User Guide SDMPL011

8-28 SDM hardware upgrade procedures

Upgrading the CPU controller

module NTRX50CF (continued)
(end)
Note: If the paging space has not increased, repeat steps 32 to 33. If, after
repeating steps 32 to 33, you have not been able to increase the paging space,
contact Nortel Technical Assistance.

34 Determine if you are upgrading firmware.

If Do

you are upgrading firmware step 37

you are not upgrading firmware step 35

At the MAP display

35 Return the SDM to service by typing
>RTS
and pressing the Enter key.
Response:
SDM RTS initiated.
SDM RTS completed.

36 The system automatically returns all modules to service.

37 You have completed this procedure.

If you are upgrading your CPU firmware, go to the procedure titled “Upgrading
CPU firmware” in this chapter.

297-5061-901 Standard 01.01 December 1998

 8-29 SDM hardware upgrade procedures 8-29

Upgrading the SDM to an FT system

Application
Use this procedure to upgrade the SDM from an SX system to an FT system.

CAUTION
System image backup
Before you perform this procedure, ensure that you
perform a system image backup. Refer to the
procedure, “Creating SDM backup tapes – System
image backup (S-tape)” on page 6-26 in this
document.

CAUTION
Application shutdown
This procedure takes two to three hours to complete.
Applications will not be available.

The following hardware modules must be available before you begin this
procedure:
• CPU controller module to match the module already in the system in
slots 6 and 7
• DS512 interface front and rear modules as in slot 1 front and rear
• I/O controller front and rear modules found in front slots 2 and 3, and
rear slot 2
• I/O controller front module found in slots 4 and 5 if equipped.

Note: Two NT0X97AE fiber optic cables must be installed to connect the
DS512 interface in slot 12 to the message switch.

Action
This procedure contains a summary flowchart as an overview of the
procedure. Follow the specific steps to perform this procedure.

Wireless Networks Family SDM–SX User Guide SDMPL011

8-30 SDM hardware upgrade procedures

Upgrading the SDM to an FT system (continued)

Summary of Upgrading the SDM to an FT system

Perform a This flowchart summarizes the

system image procedure.
backup
Use the instructions in the
procedure that follows this
Access the flowchart to perform the
SDM level of procedure.
the MAP

Busy the SDM

Offline the
SDM

Update table
SDMINV

Plug in the
new modules

Log in to the
SDM as the
root user

Run part 1 and Busy the SDM Return the End

part 2 of the SDM to service
upgrade

297-5061-901 Standard 01.01 December 1998

 SDM hardware upgrade procedures 8-31

Upgrading the SDM to an FT system (continued)

Cleaning the SDM DAT drive
At the MAP display
1 Access the SDM level of the MAP display by typing
>MAPCI; MTC; APPL;SDM
and pressing the Enter key.

2 Manually busy the SDM by typing

>BSY
and pressing the Enter key.
Response:
SDM is in service.
This command will cause a service interruption.
Do you wish to proceed?
Please confirm (“YES”, “Y”, “NO”, or “N”)

3 Confirm the Busy command by typing

>Y
and pressing the Enter key.
Response:
SDM Bsy initiated.
SDM Bsy completed.

4 Offline the SDM by typing

>BSY;OFFL
and pressing the Enter key.

5 Update the CM datafill in table SDMINV to include the two additional DS512
links as follows:
Change field CONFIG to FT.
Change field LINKS to include the second link pair.
Note: For more information on changing tables, refer to the DMS100 Family
Translations Guide, 297-xxxx-350.
At the SDM
6 Plug the new modules in the following order:
Rear modules:
DS512 personality module (NTRX50GH) in rear slot 12
LAN personality module (NTRX50FS) in rear slot 13
Front modules:
CPU controller modules (NTRX50CF or NTRX50CG) in slots 10 and 11

Wireless Networks Family SDM–SX User Guide SDMPL011

8-32 SDM hardware upgrade procedures

Upgrading the SDM to an FT system (continued)

DS512 controller module (NTRX50GA or NTRX50GX) in slot 12
I/O controller modules (NTRX50GN) in slots 13 and 14
If slots 4 and 5 are equipped, plug in NTRX50GP in slots 15 and 16.
At a telnet window or at the console terminal
7 Log into the SDM as the root user.

8 Run the SX-to-FT upgrade part 1, by typing

#/sdm/mtce/sct/SXtoFT_part1
and pressing the Enter key.
Response:

SDM COMMISSIONING

You are about to commission this system as a Supernode Data Manager

(SDM).
If you choose to proceed, a series of commissioning tasks will be
performed automatically.
Once the automated commissioning tasks have been completed
successfully, the following tasks can be completed manually:
–CM-SDM connectivity
–LAN connectivity
–LAN nodes
–LAN security
–DCE configuration
–Miscellaneous
–Login greeting
–Root and maint user passwords
–Date, time and time zone

Do you wish to proceed?

Please confirm (“YES”, “Y”, “NO”, or “N’)

297-5061-901 Standard 01.01 December 1998

 SDM hardware upgrade procedures 8-33

Upgrading the SDM to an FT system (continued)

9 Run commissioning by typing
>Y
and pressing the Enter key.
Response:

SDM COMMISSIONING

Determining Platform Type –System detected as FT

Creating sdm.modules File –PASSED

Checking Module Positions –PASSED

Commissioning Default Groups –PASSED

Commissioning File Systems –PASSED

Commissioning SDM Directories –PASSED

Commissioning Default Users –PASSED

Commissioning SDM Environment –PASSED

HIT ENTER TO CONTINUE

10 Continue by pressing the Enter key.

Response:

SDM COMMISSIONING

0 Exit
1 CM-SDM connectivity PASSED
2 LAN connectivity PASSED
3 LAN nodes PASSED
4 LAN security PASSED
5 DCE configuration PASSED
6 Login greeting Welcome to e78 Uncommissioned
7 Date & time zoneThu Nove 12 1998 EST5EDT

Please enter your selection (0–7)

Wireless Networks Family SDM–SX User Guide SDMPL011

8-34 SDM hardware upgrade procedures

Upgrading the SDM to an FT system (end)

(continued)

11 Exit the commissioning tool by typing

>0
and pressing the Enter key.

12 The system then reboots after displaying the message shown below.
Response:
The system will be rebooted now...
13 When the system is up, log into the SDM as the root user.

14 Run the SX-to-FT upgrade part 2, by typing

#/sdm/mtce/sct/SXtoFT_part2
and pressing the Enter key.
Response:
Please be aware that the SXtoFT_part1 command must be
executed prior to running this command

Do you wish to proceed?

(“YES’, “Y”, “NO”, or “N”)

Note: The system prompt is not displayed during the re-integration of rootvg
and datavg. If you wish to see the progress, telnet to the SDM and view the
storage screen of the RMI.

15 Proceed the upgrade by typing

>Y
and pressing the Enter key.

16 When the second part is completed successfully, create a system image

backup. Refer to the procedure, “Creating SDM backup tapes – System image
backup (S-tape) on page 6-26 in this document.
At the MAP display
17 Access the SDM level of the MAP display by typing
>MAPCI; MTC; APPL;SDM
and pressing the Enter key.

18 Manually busy and return the SDM to service by typing

>BSY;RTS
and pressing the Enter key.

19 You have completed this procedure.

297-5061-901 Standard 01.01 December 1998

 9-1

List of terms
802.3 10BASE-T
An IEEE standard for operating Ethernet LANs on twisted-pair cable with a
transmission rate of 10 Mbit/s.

10BASE-T
An Ethernet LAN that works on twisted pair wiring similar to telephone
cabling.

Access Control List (ACL)

A set of entries associated with a file that specify permissions for all
possible user ID and group ID combinations.

ACL
See Access Control List (ACL).

Advanced Interactive Executor (AIX)

The IBM implementation of UNIX. AIX is the base operating system in the
SDM.

AIX
See Advanced Interactive Executor (AIX).

alarm
A signal that is visual, audible, or both that is used to alert operating
company personnel to a condition requiring attention.

backplane
Connector blocks and special wiring on the rear of a shelf. Printed circuit
board modules normally mount in front of the backplane.

boot
The process of loading, initializing, and running an operating system.

C28B
See C28 model B DMS streamlined cabinet (C28B).

Wireless Networks Family SDM–SX User Guide SDMPL011

9-2 List of terms

C28 model B DMS streamlined cabinet (C28B)

A cabinet used to house customer-specified equipment.

cell
In DCE, a collection of objects that are controlled by a registry database.

channel service unit (CSU)

Line bridging devices that allow several inputs to share one output. CSUs
exist to handle any input/output combination of synchronous or
asynchronous terminals, computer ports, or modems. These units are also
called modem sharing units, digital bridges, port sharing units, digital
sharing devices, modem contention units, multiple access units, control
signal activated electronic switches or data-activated electronic switches.

client
A computer or program that requests one or more services from a server.

CLLI
See common language location identifier (CLLI).

CM
See computing module (CM).

common language location identifier (CLLI)

A standard identification method for trunk groups in the following form:

aaaa bb xx yyyy

where:

aaaa
is the city code
bb
is the province or state code
xx
is the trunk group identifier
yyyy
is the trunk number

computing module (CM)

The central processor and memory element of DMS SuperNode. The CM
consists of a pair of CPUs with associated memory that operate in a
synchronous matched mode on two separate planes. Only one plane is
active; it maintains overall control of the system while the other plane is on
standby.

297-5061-901 Standard 01.01 December 1998

 List of terms 9-3

correlated log
An incoming log report that has been processed (correlated) by the
knowledge base. A problem instance is associated with this log.

CSU
See channel service unit (CSU).

data service unit (DSU)

Also called digital service unit. Converts RS-232-C or other terminal
interface to DSX-1 interface.

datavg
See data volume group (datavg).

data volume group (datavg)

A logical volume on the SDM used to store application data. If datavg is not
present on a system, application data is stored in the root volume group
group).

DCE
See Distributed Computing Environment (DCE).

directory
A named portion of the UNIX file system.

disk mirroring
The SDM stores a mirror copy of all data that is written to a logical volume.
In the event of a filure to one disk, the system is able to read from and write
to the remaining disk without interruption.

Distributed Computing Environment

An architecture consisting of standard programming, interfaces, conventions
and server functionalities (remote procedure call) for distributing
applications transparently across networks.

DMS SuperNode
The central control and messaging component of the DMS-100 switch.
DMS SuperNode consists of two major elements, the computing module
(CM) and the message switch (MS). The CM is the central processing and
memory element. The MS is the messaging hub for the switch.

DRAM
Dynamic random access memory

Wireless Networks Family SDM–SX User Guide SDMPL011

9-4 List of terms

DSU
See data service unit (DSU).

dynamic information
Information that is displayed and updated automatically. Dynamic
information can be displayed without typing a command. An alarm banner,
for example, is updated automatically. Other information that requires a
command input does not require the command to be invoked a second time
to show updates to the displayed screen.

electromagnetic interference (EMI)

The phenomenon resulting when electromagnetic energy causes an
unacceptable or undesirable response, malfunction, degradation, or
interruption of the intended operation of the electronic equipment,
subsystem, or system.
Enhanced Terminal Access (ETA) application
The Enhanced Terminal Access application provides secure access to the
SDM and the CM from a GUI running on a remote workstation.
erasable programmable read-only memory (EPROM)
A type of read-only memory in which data is initially programmable as in
programmable read-only memory (PROM). Unlike PROM, in which the
program is fixed (cannot be changed) after initialization, EPROM internal
data can be erased and changed after the initial program has been installed.

ESD
Electrostatic discharge

Ethernet
A physical and data link protocol used for LANs.

exception report
A log that indicates that a certain number of logs have been generated in a
certain time period. All exception reports are log type EXC900, by default.

Exception Reporting (ER) application

The Exception Reporting application performs event correlation, and
generates exception reports.
fault tolerant
On the SDM, a hardware platform that can survive a single point of failure
without an associated loss of service.

297-5061-901 Standard 01.01 December 1998

 List of terms 9-5

file system
A hierarchical structure of files and directories that resides on a single
logical volume. A file system must be mounted onto a directory mount
point. When multiple file systems are mounted, a directory structure is
created that presents the images of a single file system.

file transfer protocol (FTP)

A service that supports file transfer between local and remote consoles over
a TCP/IP network.

FTP
See file transfer protocol (FTP).

graphical user interface (GUI)

Point and click iconic interface for user-to-computer interaction.

GUI
See graphical user interface (GUI).

halting
Bringing the system to a complete stop so that no processes are running.

HP
Hewlett Packard

IEEE
Institute of Electrical and Electronic Engineers

IOC
See I/O controller (IOC).

I/O controller (IOC)

An equipment shelf that provides an interface between up to 36 I/O devices
and the central message controller (CMC). The IOC contains a peripheral
processor (PP) that independently performs local tasks, thus relieving the
load on the CPU.

inference engine
A software module that generates exception report logs.

IP
Internet protocol

Wireless Networks Family SDM–SX User Guide SDMPL011

9-6 List of terms

knowledge base
The knowledge base analyzes incoming computing module (CM) logs and
identifies the type of exception report to be generated.

LAN
See local area network (LAN).
LED
See light-emitting diode (LED).

light-emitting diode (LED)

A solid-state device which emits light when the appropriate voltage is
applied to it. The LEDs are used in the DMS-100 switch components as
front panel indicators, and they are usually off when equipment status is
normal.

LIM
See link interface module (LIM).

link interface module (LIM)

A peripheral module (PM) that controls messaging between link interface
units (LIU) in a link peripheral processor (LPP). The LIM also controls
messages between the LPP and the DMS-bus component. A LIM consists
of two LIM units and two frame transport buses (F-bus). The two LIM units
operate in a load-sharing mode with each other. See also link peripheral
processor (LPP).

link peripheral processor (LPP)

The DMS SuperNode equipment frame or cabinet that contains two types of
peripheral modules (PM): a link interface module (LIM) and one or more
application-specific units (ASU). See also link interface module (LIM).

local area network (LAN)

A network that permits the interconnection and intercommunication of
multiple computers, primarily for the sharing of resources such as data
storage devices and printers.

local console
A console that is connected directly to the SDM with an RS-232 null modem
cable. Any other console is a remote console.

log category
A common group of log types that the knowledge base handles in a generic
fashion.

297-5061-901 Standard 01.01 December 1998

 List of terms 9-7

Log Delivery application

The Log Delivery application delivers computing module (CM) and SDM
log reports to an operations support system by way of a TCP/IP connection.

log report
A message sent from the DMS switch whenever a significant event has
occurred in the switch or one of its peripherals. A log report includes state
and activity reports as well as reports on hardware and software faults, test
results, and other events or conditions likely to affect the performance of the
switch. A log report can be generated in response to a system or manual
action.

Two types of log reports apply to the SDM. The main DMS log stream
reports SDM events in the PM series of logs. The SDM also reports events
locally in the SDM series of logs - this log stream is not part of the main
DMS log stream. The SDM Log Delivery application provides access to
both streams through the SDM. For additional information on log reports
applicable to the SDM, see the Maintenance Overview chapter of this
document.

log type
A string used to identify a log. The string is made up of two parts: a log
name of up to five characters, and a 3-digit log number. This string is used
as the key for customizing threshold values.
logical volume
A storage device, similar to a disk section but of flexible size, that can hold a
file system, raw data, application programs, or swap.

LPP
See link peripheral processor (LPP).

maint (maintenance) user

Monitors SDM system performance, and performs required maintenance
tasks. Maint users have restricted shell access.

maintenance and administration position

See MAP.

master replica
In DCE, the first instance of a specific DCE server in the cell. The master
replica is the only replica that can be modified. Only one master replica
exists at one time.

Wireless Networks Family SDM–SX User Guide SDMPL011

9-8 List of terms

MAP
Maintenance and administration position. A group of components that
provides a user interface between operating company personnel and the
DMS-100 family of switches. The interface consists of a video display unit
(VDU) and keyboard, a voice communications module, test facilities, and
special furniture.

MAPCI
MAP command interpreter

MAU
Media access unit

message switch (MS)

A high-capacity communications facility that functions as the messaging
hub of the dual-plane combined core (DPCC) of a DMS SuperNode
processor. The MS controls messaging between the DMS-bus components
by concentrating and distributing messages and by allowing other DMS
components to communicate directly with each other.

modular supervisory panel (MSP)

A hardware device that accepts the frame battery feed and ground return
from the power distribution center (PDC). The MSP distributes the battery
feed, by means of subsidiary fuses and feeds, to the shelves of the frame or
bay in which it is mounted. The MSP also contains alarm circuits.

MS
See message switch (MS).

MSP
See modular supervisory panel (MSP).

MTC
An abbreviation for maintenance. MTC is the first-level maintenance
subsystem of the MAP. See also MAP.

netmask
A 32-bit bit mask which shows how an Internet address is to be divided into
network, subnet and host parts.

node
The terminating point of a link. With respect to DMS peripheral modules, a
node is defined as a unit of intelligence within a system. The SDM is
viewed by the DMS system as a peripheral module, linked to the DMS

297-5061-901 Standard 01.01 December 1998

 List of terms 9-9

system by an Ethernet link. See the chapter Understanding the fault tolerant
SDM for additional information.

OAM
See operation, administration, and maintenance (OAM).

OAM&P
Operation, administration, maintenance, and provisioning

operating company (OC)

The owner or operator of a DMS switch.

operation, administration, and maintenance (OAM)

All the tasks necessary for providing, maintaining, or modifying the services
provided by a switching system. These tasks include provisioning of
hardware, creation of service, verification of new service, billing and trouble
recognition and clearance.

OSS
Operations support system

PEC
See product engineering code (PEC).

PID
See process ID (PID).

PowerPC
Performance Optimized with Enhanced RISC for Personal Computers; the
microprocessor architecture used in the SDM. PowerPC by is used by
Motorola, Inc. under license by IBM. The term PowerPC is a trademark of
IBM.

process
In UNIX, a program that is currently executing.

process ID (PID)
An integer assigned to a UNIX process that uniquely identifies the process.
No two processes can have the same process ID.

product engineering code (PEC)

An eight-character unique identifier for each marketable hardware item
manufactured by Nortel.

Wireless Networks Family SDM–SX User Guide SDMPL011

9-10 List of terms

read-only replica
In DCE, a type of replica. The read-only replica is a copy of a directory that
contains changes made to the master replica. The read-only replica is used
only for looking up information.

reboot
Taking the operating system from a running state down to a stopped state,
and back to a running state.

remote console
Any console that is not connected directly to the SDM with an RS-232 null
modem cable.

remote maintenance interface (RMI)

The user interface for the SDM which provides node maintenance,
administration, and monitoring functions. This interface is accessible to the
root or maint user at the local or remote VT100 terminal, or from the
operating company LAN. See the “SDM maintenance overview” and the
“SDM system administration overview” chapters of this document for a full
description of the RMI.

remote procedure call (RPC)

A protocol which allows a service running on one host to cause code to be
executed on another host. RPC is used to implement the client server model
of distributed computing. An RPC is implemented by sending request
messages to a remote system (the server) to execute a designated procedure,
and a result message returned to the caller (the client).

replica
In DCE, each physical copy of a directory, including the original. Two types
exist: master, and read-only.

restricted shell
A shell is restricted when a user is restricted to using specific UNIX
commands.

RMI
See remote maintenance interface (RMI).

root user
The SDM system administrator. Responsibilities include adding and
removing users from the SDM, assigning and restricting user access, and
password administration. A root user has unrestricted shell access.

297-5061-901 Standard 01.01 December 1998

 List of terms 9-11

rootvg
See root volume group (rootvg).

root volume group (rootvg)

A logical volume on the SDM used to store the AIX operating system,
platform software, application executables, shared libraries, static and
configuration files.

RPC
See remote procedure call (RPC).

RS-232
The industry standard for a 25-pin interface that connects computers and
peripheral equipment such as modems and printers.
SCC2
Switching control centre 2. Log header used for logs sent to an SCC2 mini
computer for processing.

SCSI
Small computer system interface

SDM
SuperNode Data Manager

STD
Standard. Standard or normal log header format

Secure File Transfer

An SDM application that provides secure file transfers to the computing
module (CM) and/or the SuperNode Data Manager (SDM) from a remote
node across an operating company’s TCP/IP wide area network (WAN).

server
A powerful, centralized computer (or program) designed to provide
information to clients upon request. The SDM acts as the server for
distributed software applications.

shell
A command line interpreter that reads user input and executes UNIX
commands.
SMIT
System management interface tool.

Wireless Networks Family SDM–SX User Guide SDMPL011

9-12 List of terms

SNMP
Simple Network Management Protocol

S-tape
System image software backup tape

static information
Information that is displayed once each time a command is invoked..
Updates to the information on the screen are not automatically displayed.

SuperNode Billing Application (SBA)

SBA provides a distributed, high capacity scalable billing system that
enhances the functionality of all SuperNode switch types.

TCP
Transmission Control Protocol

TCP/IP
Transmission Control Protocol/Internet Protocol

telnet
A program that acts as a terminal emulator, allowing you to connect
remotely to other terminals.

UI
User interface

UNIX
A computer operating system.

uncorrelated log
An incoming log report for which there are no rules in the knowledge base,
or the rules have been disabled. Enabling and disabling the rules is done
using the Log Customization Utility and does not require resetting the expert
system.
unseat
Cards can be unseated from line concentrating modules (LCM), ISDN line
concentrating modules (LCMI), remote cluster controllers (RCC), ISDN
remote cluster controllers (RCCI), and remote maintenance modules
(RMM).

unshielded twisted pair (UTP)

A cable medium with one or more pairs of twisted insulated copper
conductors bound in a single plastic sheath.

297-5061-901 Standard 01.01 December 1998

 List of terms 9-13

UTP
See unshielded twisted pair (UTP).

Wireless Networks Family SDM–SX User Guide SDMPL011

 10-1

Index
Symbols stopping and starting 4-54
Application states, at the RMI 2-45
! command, restricted shell 2-26
ASCII command, restricted shell 2-26
? command, restricted shell 2-29
Assigning slot numbers 1-7
$ command, restricted shell 2-26
**Empty** 5-86, 6-59, 7-4, 7-9, 7-15, 7-22, 7-30,
7-35, 7-42, 7-48 B
Backing up software and data, overview 3-11
A Backup command, RMI 3-7
Backup tapes
Access command, RMI 3-7
full restore from, procedure 6-35
Account command, restricted shell 2-26
partial restore, procedure 6-49
Add command, RMI 2-55, 2-64, 2-71
system image backup, procedure 6-26
Adding disks 2-64
Base layer software, components 1-19
Adding I/O controller modules 4-59
Bell command, restricted shell 2-26
Adding logical volumes 2-65
Binary command, restricted shell 2-26
Adding new maintenance users 6-10
Bsy command, MAP 2-9
Adding new users 3-10
Bsy command, RMI 2-48, 2-59, 2-70
Alarm clearing procedures
Bsyapp command 2-33
APPL SDM critical 4-25
Bsyapp command, SDMRLogin 2-17
APPL SDM minor 4-3
Bsyhw command, SDMRLogin 2-17
Ext FSP Major 4-44
Bsysdm command 2-31
Alarm monitoring
Bye command, restricted shell 2-26
at the MAP 2-19
at the RMI 2-42
Append command, restricted shell 2-26 C
Appl command, RMI 2-48 C28B cabinet 1-3, 1-4
APPL SDM critical, alarm clearing procedure 4-25 Case command, restricted shell 2-26
APPL SDM minor, alarm clearing procedure 4-3 Cd command, restricted shell 2-26
Application control commands Change command, RMI 2-53, 2-56, 2-65, 2-67
Bsyapp command 2-33 Changing a DCE user password 6-43, 6-85
Initproc command 2-33 Changing logical volumes 2-65, 2-67
Offlapp command 2-33 Changing passwords 3-10
overview 2-29 changing Performance Log time interval 2-66
QuerySDM command 2-34 Changing system thresholds 4-140, 4-144
Rtsapp command 2-33 Changing theshold values 2-66
Application layer software, components 1-19 Changing time interval, performance log 4-148
Application software Chmod command, restricted shell 2-26
Log Delivery, overview 1-24 Close command, restricted shell 2-27
Logreceiver tool, installing on client workstations Commands
6-57 application control

Wireless Networks Family SDM–SX User Guide SDMPL011

10-2 Index

Bsyapp command 2-33 Help command 2-26, 2-27

Initproc command 2-33 Idle command 2-27
Offlapp command 2-33 Image command 2-27
QuerySDM command 2-34 Lcd command 2-27
Rtsapp command 2-33 Listlogfile command 2-25
MAP Logroute command 2-25
Bsy command 2-9 Ls command 2-27
HaltSDM command 2-15 Macdef command 2-27
Locate command 2-12 Mdelete command 2-27
OffL command 2-8 Mdir command 2-29
overview 2-7 Mget command 2-29
Platform command 2-13 Mkdir command 2-27
QuerySDM command 2-11 Mls command 2-29
Quit command 2-7 Mode command 2-27
RebootSDM command 2-15 Modtime command 2-27
RTS command 2-10 Mput command 2-27
SDMRLogin command 2-16 Newer command 2-29
Trnsl command 2-8 Nlist command 2-27
node control Nmap command 2-27
Bsysdm command 2-31 Ntrans command 2-28
Haltsdm command 2-32 Open command 2-28
Offlsdm command 2-32 Ping command 2-25
Rebootsdm command 2-32 Prompt command 2-28
Rtssdm FORCE command 2-31 Proxy command 2-28
restricted shell Put command 2-28
! command 2-26 Pwd command 2-28
? command 2-29 Quit command 2-28
$ command 2-26 Quote command 2-28
Account command 2-26 Recv command 2-29
Append command 2-26 Reget command 2-29
ASCII command 2-26 Rename command 2-28
Bell command 2-26 Reset command 2-28
Binary command 2-26 Restart command 2-28
Bye command 2-26 restricted file transfer 2-26
Case command 2-26 Rhelp command 2-28
Cd command 2-26 Rmdir command 2-28
Chmod command 2-26 Rstatus command 2-28
Close command 2-27 Runique command 2-28
Copylogfile command 2-26 Sdmmtc command 2-25
Cr command 2-27 Send command 2-28
Debug command 2-27 Sendport command 2-28
Delete command 2-27 Site command 2-28
Dellogfile command 2-26 Size command 2-28
Dir command 2-27 Status command 2-28
Disconnect command 2-27 Struct command 2-28
Exit command 2-26 Sunique command 2-29
Form command 2-27 System command 2-28
Ftplogfile command 2-26 Tenex command 2-29
Get command 2-29 Trace command 2-29
Glob command 2-27 Type command 2-29
Hash command 2-27 Umask command 2-29

297-5061-901 Standard 01.01 December 1998

 Index 10-3

User command 2-29 RMI maintenance menu level

Verbose command 2-29 Appl command 2-48
Viewlogfile command 2-26 Bsy command 2-48
Who command 2-25 Con command 2-48
Who_is_on command 2-25 Hw command 2-48
RMI LAN command 2-48
administration menu level 3-6 OffL command 2-48
Help command 2-40 QuerySDM command 2-48
Locate command 2-40, 2-76 RTS command 2-48
maintenance menu level 2-48 Sys command 2-48
QuerySDM CONFIG command 2-75 RMI storage menu level
QuerySDM FLT command 2-72 Add command 2-64
QuerySDM LOADS command 2-73 Change command 2-65
QuerySDM STATUS command 2-71 RMI system menu level
Quit all command 2-40 Change command 2-67
Quit command 2-40, 3-6 Logs command 2-61
Refresh command 2-41 QuerySDM command 2-66
top menu level 2-45 Storage command 2-62
RMI access menu level, Change command 3-24 RMI top menu level
RMI administration menu level Admin command 2-46
Access command 3-7 Mtc command 2-45
Backup command 3-7 SDMRLogin session
Help command 3-7 Bsyapp command 2-17
Install command 3-7 Bsyhw command 2-17
Refresh command 3-7 Help command 2-17
Split command 3-7 Locate command 2-17
Time command 3-7 Logout command 2-18
User command 3-7 Ls command 2-18
RMI application menu level Offlapp command 2-17
Bsy command 2-59 Ping command 2-18
Logs command 2-57 Ps command 2-18
OffL command 2-60 QuerySDM command 2-18
QuerySDM command 2-58 Rtsapp command 2-17
RTS command 2-59 Rtshw command 2-17
RMI connectivity menu level Who command 2-18
Change command 2-53 Who_is_on command 2-18
Logs command 2-50 Commissioning
QuerySDM command 2-51 Log Delivery application 2-84
Tst command 2-52 overview 3-1
RMI hardware menu level SDM platform software, overview 3-2, 7-1, 7-2
Add command 2-71 commissioning
Bsy command 2-70 Log delivery CM configuration file 4-117
Del command 2-71 Log delivery device 4-84
Logs command 2-68 Log delivery global parameters 4-107
QuerySDM command 2-69 Commissioning DCE 6-61
RMI LAN menu level Commissioning SDM–LAN connectivity 7-4, 7-9,
Add command 2-55 7-15, 7-22, 7-30, 7-35, 7-42, 7-48
Change command 2-56 Con command, RMI 2-48
Del command 2-56 Configuring an SDM in DCE cell 6-61
Logs command 2-54 Connectivity states, at the RMI 2-43
QuerySDM command 2-54 Controlling SDM applications 4-54

Wireless Networks Family SDM–SX User Guide SDMPL011

10-4 Index

Copylogfile command, restricted shell 2-26 troubleshooting 3-23, 3-35

CPU controller module viewing dcemonitor status file, procedure 6-97
description 1-5, 1-8, 1-18 DCE cells
hardware replacement procedure 5-34 configuring an SDM 6-61
upgrading, detailed procedure 8-3, 8-16 removing an SDM 6-74
CPU personality module DCE commissioning 6-61
description 1-12, 1-14 dcemonitor
hardware replacement procedure 5-3 disabling 6-106
Cr command, restricted shell 2-27 enabling 6-106
Creating a DCE user 6-81 viewing status file 6-97
Debug command, restricted shell 2-27
D Del command, RMI 2-56, 2-71
Delete command, restricted shell 2-27
Data
Deleting a DCE user 6-89, 6-92, 6-100
backup and restore overview 3-11
Deleting I/O controller modules 4-67
restoring, overview 3-14
Dellogfile command, restricted shell 2-26
Datafill required on DMS 3-3
Dir command, restricted shell 2-27
Datavg
Disabling dcemonitor 6-106
creating on a new system 4-131, 4-135
Disconnect command, restricted shell 2-27
moving to a rootvg/datavg system 4-127
Disk partitioning, description 1-21
Date and time, setting 6-18
Disks, adding 2-64
Date, time and time zone, overview 3-7
DS512 controller module
DCE
description 1-9
adding nodes to a cell 3-29
hardware replacement procedure 5-83
adding port restrictions 3-32
DS512 personality module
adding SDM to cell 3-30
description 1-14
application servers after restore 3-34
hardware replacement procedure 5-96
cell configuration and maintenance 3-26
Dynamic information 2-39
changing a DCE user password 6-43, 6-85
commands 3-31
configuring an SDM, procedure 6-61 E
creating a user 6-81 Enabling dcemonitor 6-106
creating DCE cell 3-29 Enhanced Terminal Access, using 2-36
creating user accounts 3-30 Enter key and Return key 2-24
Deleting a DCE user 6-89, 6-92, 6-100 Exit command, restricted shell 2-26
disabling dcemonitor, procedure 6-106 Ext alarms, SDM related, overview 2-19
enabling dcemonitor, procedure 6-106 Ext FSP Major, alarm clearing procedure 4-44
executing commands 3-32
firewalls 3-32
full configuration 3-30
F
Fan trays
GUI application workstations 3-27
description 1-11
installation requirements 3-29
hardware replacement procedure 5-10
local configuration 3-30
Fan unit 1-5
monitoring status 3-31
File storage, Log Delivery application 2-88
overview 3-26
File systems
registering application servers 3-30
creating datavg on a new system 4-131, 4-135
removing an SDM, procedure 6-74
moving to a rootvg/datavg system 4-127
removing port restrictions 3-32
Files, partial restore from system image 6-49
procedure 6-115
Form command, restricted shell 2-27
restricting ports to an SDM–defined range, proce-
FTP access 3-23
dure 6-110, 6-120
Ftplogfile command, restricted shell 2-26
starting applications 3-33

297-5061-901 Standard 01.01 December 1998

 Index 10-5

Full SDM restore, overview 3-15 Interconnect module 0, hardware replacement proce-
Functions, administration 1-21 dure 5-19
Interconnect module 1, hardware replacement proce-
G dure 5-26
Interconnect modules, description 1-15
Get command, restricted shell 2-29
Interfaces, to operating company LAN 1-22
Glob command, restricted shell 2-27
IP addresses, defining on SDM to CM LAN 3-3,
7-9
H Isolating faults
HaltSDM command, MAP 2-15 hardware LEDs 2-94
Haltsdm command 2-32 Log Delivery application 2-91
Hardware replacement procedures ISTb node state, at the RMI 2-47
NTRX50FD CPU personality module 5-3 ISTb state, at the MAP 2-3
NTRX50FE, upper fan tray 5-10
NTRX50FG Interconnect module 0 5-19
NTRX50FH Interconnect module 1 5-26
L
LAN command, RMI 2-48
NTRX50FK CPU contoller module 5-34
LAN personality module
NTRX50FL CPU controller module 5-34
description 1-14
NTRX50FM CPU controller module 5-34
hardware replacement procedure 5-70
NTRX50FQ I/O controller module 5-49, 5-59
LAN states, at the RMI 2-44
NTRX50FS LAN personality module 5-70
Lcd command, restricted shell 2-27
NTRX50FU I/O controller module 5-49, 5-59
LEDs
NTRX50GA DS512 controller module 5-83
controller modules 1-11, 2-95
NTRX50GH DS512 personality module 5-96
DAT drive 2-95
NTRX50GN I/O controller module 5-49, 5-59
fan trays 1-11
NTRX50GP I/O controller module 5-49, 5-59
interconnect modules 1-15, 2-95
NTRX50KD, upper fan tray 5-10
on fan tray units 2-98
Hardware states, at the RMI 2-45
Listlogfile command, restricted shell 2-25
Hardware upgrades, overview 3-25
Locate command, MAP 2-12
Hash command, restricted shell 2-27
Locate command, RMI 2-76
Help command, restricted shell 2-26, 2-27
Locate command, SDMRLogin 2-17
Help command, RMI 3-7
Log Delivery, device commissioning 4-84
Help command, SDMRLogin 2-17
Log Delivery application
Hubs, requirements 1-23
commissioning
Hw command, RMI 2-48
accessing commissioning tool 2-84
CM configuration file 2-90
I overview 2-84
I/O controller module UNIX file client devices 2-88
description 1-5, 1-10, 1-17, 1-18 commissioning tool
hardware replacement procedure 5-49, 5-59 Device List menu 2-85
I/O controller modules Global Parameters menu 2-89
adding 4-59 TCP client devices 2-87
deleting 4-67 log output format 2-84
I/O personaltiy module, description 1-12 Logreceiver tool 1-25, 2-82
Idle command, restricted shell 2-27 overview 1-24, 1-26, 2-81
Idle logins 3-9 troubleshooting 2-91
Image command, restricted shell 2-27 Log Delivery CM configuration file commissiong
Initproc command 2-33 4-117
Install command, RMI 3-7 Log Delivery global parameters commissioning
InSv node state, at the RMI 2-47 4-107
InSv state, at the MAP 2-3 Log output format, Log Delivery application 2-84

Wireless Networks Family SDM–SX User Guide SDMPL011

10-6 Index

Log reports Mdelete command, restricted shell 2-27

generated by the SDM 2-77 Mdir command, restricted shell 2-29
Log Delivery application 2-81 Mget command, restricted shell 2-29
overview 2-77 Mkdir command, restricted shell 2-27
Logging in to the SDM 2-22 Mls command, restricted shell 2-29
as maint user 2-23 Mode command, restricted shell 2-27
as root user 2-23 Modem
Logical volumes AT commands 4-79
adding 2-65 dialing in to SDM 2-38, 4-79
changing 2-65, 2-67 Modtime command, restricted shell 2-27
description 1-21 Mput command, restricted shell 2-27
maximum number 2-63 MSP 1-5
viewing 2-63
Logout command, SDMRLogin 2-18
Logreceiver tool, installing on client workstations
N
Newer command, restricted shell 2-29
6-57
Nlist command, restricted shell 2-27
Logroute command, restricted shell 2-25
Nmap command, restricted shell 2-27
logroute command 2-84
Node control commands
Logs command, RMI 2-50, 2-54, 2-57, 2-61, 2-68
Bsysdm command 2-31
Ls command, restricted shell 2-27
Haltsdm command 2-32
Ls command, SDMRLogin 2-18
Offlsdm command 2-32
overview 2-29
M Rebootsdm command 2-32
Macdef command, restricted shell 2-27 Rtssdm FORCE command 2-31
Main chassis hardware Node states, description of 2-46, 2-47
front equipment 1-5 Ntrans command, restricted shell 2-28
front optional slots 1-10 NTRX50CF, description 1-8, 1-18
rear equipment 1-12 NTRX50CG, description 1-8, 1-18
rear optional slots 1-15 NTRX50FD
Maint user, logging in to SDM 2-23 description 1-12, 1-14
Maintaining the SDM hardware replacement procedure 5-3
using the MAP, overview 1-20 NTRX50FE
using the RMI, overview 1-21 description 1-11
Maintenance hardware replacement procedure 5-10
routine tasks 2-104 NTRX50FF, description 1-11
user interfaces 1-20 NTRX50FG
maintenance class, adding new user, overview 3-10 description 1-15
ManB node state, at the RMI 2-47 hardware replacement procedure 5-19
ManB state, at the MAP 2-3 NTRX50FH
MAP, alarm monitoring 2-19 description 1-15
MAP commands hardware replacement procedure 5-26
Bsy 2-9 NTRX50FK
HaltSDM 2-15 description 1-5, 1-8
Locate 2-12 hardware replacement procedure 5-34
overview 2-7 NTRX50FL
Platform 2-13 description 1-8, 1-18
QuerySDM 2-11 hardware replacement procedure 5-34
RebootSDM 2-15 NTRX50FM, hardware replacement procedure
RTS 2-10 5-34
SDMRLogin 2-16 NTRX50FQ
Trnsl 2-8 description 1-5, 1-10

297-5061-901 Standard 01.01 December 1998

 Index 10-7

hardware replacement procedure 5-49, 5-59 Provisionable hardware 1-17

NTRX50FS Proxy command, restricted shell 2-28
description 1-12, 1-14 Ps command, SDMRLogin 2-18
hardware replacement procedure 5-70 Put command, restricted shell 2-28
NTRX50FU Pwd command, restricted shell 2-28
description 1-17
hardware replacement procedure 5-49, 5-59
NTRX50GA
Q
QuerySDM command 2-34
description 1-5, 1-9
MAP 2-11
hardware replacement procedure 5-83
QuerySDM command, RMI 2-48, 2-51, 2-54, 2-58,
NTRX50GH
2-66, 2-69
description 1-14
QuerySDM command, SDMRLogin 2-18
hardware replacement procedure 5-96
QuerySDM CONFIG command 2-75
NTRX50GN
QuerySDM FLT command, RMI 2-72
description 1-17
QuerySDM LOADS command, RMI 2-73
hardware replacement procedure 5-49, 5-59
QuerySDM STATUS command, RMI 2-71
NTRX50GP
Quit command, restricted shell 2-28
description 1-18
Quit command, MAP 2-7
hardware replacement procedure 5-49, 5-59
Quote command, restricted shell 2-28
NTRX50GX, description 1-9
NTRX50KD, hardware replacement procedure
5-10 R
RebootSDM command, MAP 2-15
Rebootsdm command 2-32
O Recv command, restricted shell 2-29
OffL command, MAP 2-8
Refresh command, RMI 3-7
OffL command, RMI 2-48, 2-60
Reget command, restricted shell 2-29
OffL node state, at the RMI 2-47
Remote maintenance interface
OffL state, at the MAP 2-3
access menu level, Change command 3-24
Offlapp command 2-33
accessing 2-35
Offlapp command, SDMRLogin 2-17
using a modem 2-38, 4-79
Offlsdm command 2-32
using Enhanced Terminal Access 2-36
Open command, restricted shell 2-28
using telnet 2-36
administration menu level
P Access command 3-7, 3-23
Passwords adding new users 3-10
administering 3-9 Backup command 3-7, 3-11
changing 3-10 changing passwords 3-10
changing maintenance user 6-3 Help command 3-7
Performance Log, Changing time interval 4-148 Install command 3-7
Performance Log, time interval, changing 2-66 overview 3-6
Ping command 2-18 Refresh command 3-7
restricted shell 2-25 removing users 3-11
Platform command, MAP 2-13 Split command 3-7
Platform commissioning tool 3-2, 7-1, 7-2 Time command 3-7
Ports User command 3-7, 3-9
removing restrictions 6-115 administration menu levels 3-5
restricting to an SDM–defined range 6-110, application menu level
6-120 Bsy command 2-59
Power supply 1-17 Logs command 2-57
input power 1-5 OffL command 2-60
Prompt command, restricted shell 2-28 overview 2-56

Wireless Networks Family SDM–SX User Guide SDMPL011

10-8 Index

QuerySDM command 2-58 QuerySDM FLT command 2-72

RTS command 2-59 QuerySDM LOADS command 2-73
connectivity menu level QuerySDM STATUS command 2-71
Change command 2-53 SDM state monitoring 2-46
Logs command 2-50 static information 2-39
overview 2-49 storage menu level
QuerySDM command 2-51 Add command 2-64
Tst command 2-52 Change command 2-65
description 2-34, 3-4 system menu level
dynamic information 2-39 Change command 2-67
hardware menu level Logs command 2-61
Add command 2-71 overview 2-60
Bsy command 2-70 QuerySDM command 2-66
Del command 2-71 Storage command 2-62
Logs command 2-68 top menu level
overview 2-68 Admin command 2-46
QuerySDM command 2-69 Mtc command 2-45
LAN menu level overview 2-41
Add command 2-55 Removing an SDM from DCE cell 6-74
Change command 2-56 Removing maintenance user 6-10
Del command 2-56 Removing port restrictions 6-115
Logs command 2-54 Removing users 3-11
overview 2-53 Rename command, restricted shell 2-28
QuerySDM command 2-54 Replacing SDM hardware
Locate command 2-76 NTRX50FD CPU personality module 5-3
maintenance levels 2-35 NTRX50FE, upper fan tray 5-10
maintenance menu level NTRX50FG, Interconnect module 0 5-19
Appl command 2-48 NTRX50FH, Interconnect module 1 5-26
Bsy command 2-48 NTRX50FK CPU controller module 5-34
Con command 2-48 NTRX50FL CPU controller module 5-34
Hw command 2-48 NTRX50FM CPU controller module 5-34
LAN command 2-48 NTRX50FQ I/O controller module 5-49, 5-59
OffL command 2-48 NTRX50FS LAN personality module 5-70
overview 2-46 NTRX50FU I/O controller module 5-49, 5-59
QuerySDM command 2-48 NTRX50GA DS512 controller module 5-83
RTS command 2-48 NTRX50GH DS512 personality module 5-96
Sys command 2-48 NTRX50GN I/O controller module 5-49, 5-59
menu components 2-41 NTRX50GP I/O controller module 5-49, 5-59
menu system NTRX50KD, upper fan tray 5-10
administration menu level 3-6 Reporting faults, overview 2-92
application menu level 2-56 Reset command, restricted shell 2-28
connectivity menu level 2-49 Restart command, restricted shell 2-28
hardware menu level 2-68 Restoring software and data, overview 3-11, 3-14
LAN menu level 2-53 Restricted file transfer, restricted shell 2-26
maintenance menu level 2-46 Restricted shell
overview 2-39 Copylogfile command 2-26
system menu level 2-60 Dellogfile command 2-26
top menu level 2-41 description of 2-25
monitoring alarms 2-42 Exit command 2-26
monitoring states 2-42 Ftplogfile command 2-26
QuerySDM CONFIG command 2-75 Help command 2-26

297-5061-901 Standard 01.01 December 1998

 Index 10-9

Listlogfile command 2-25 Recv command 2-29

Logroute command 2-25 Reget command 2-29
Ping command 2-25 Rename command 2-28
restricted file transfer 2-26 Reset command 2-28
! command 2-26 Restart command 2-28
? command 2-29 Rhelp command 2-28
$ command 2-26 Rmdir command 2-28
Account command 2-26 Rstatus command 2-28
Append command 2-26 Runique command 2-28
ASCII command 2-26 Send command 2-28
Bell command 2-26 Sendport command 2-28
Binary command 2-26 Site command 2-28
Bye command 2-26 Size command 2-28
Case command 2-26 Status command 2-28
Cd command 2-26 Struct command 2-28
Chmod command 2-26 Sunique command 2-29
Close command 2-27 System command 2-28
Cr command 2-27 Tenex command 2-29
Debug command 2-27 Trace command 2-29
Delete command 2-27 Type command 2-29
Dir command 2-27 Umask command 2-29
Disconnect command 2-27 User command 2-29
Form command 2-27 Verbose command 2-29
Get command 2-29 Sdmmtc command 2-25
Glob command 2-27 Viewlogfile command 2-26
Hash command 2-27 Who command 2-25
Help command 2-27 Who_is_on command 2-25
Idle command 2-27 Restricting ports to an SDM–defined range 6-110,
Image command 2-27 6-120
Lcd command 2-27 Return key and Enter key 2-24, 4-2, 6-2, 8-1
Ls command 2-27 Rhelp command, restricted shell 2-28
Macdef command 2-27 Rmdir command, restricted shell 2-28
Mdelete command 2-27 RMI
Mdir command 2-29 accessing, using a modem 4-79
Mget command 2-29 administration menu level, Time command 3-7
Mkdir command 2-27 hardware menu level, overview 2-68
Mls command 2-29 menu components 2-41
Mode command 2-27 menu system, application menu level 2-56
Modtime command 2-27 system menu level, overview 2-60
Mput command 2-27 Root user, logging in to SDM 2-23
Newer command 2-29 Routers, requirements 1-23
Nlist command 2-27 Rstatus command, restricted shell 2-28
Nmap command 2-27 RTS command, MAP 2-10
Ntrans command 2-28 RTS command, RMI 2-48, 2-59
Open command 2-28 RTSapp command 2-33
Prompt command 2-28 Rtsapp command, SDMRLogin 2-17
Proxy command 2-28 Rtshw command, SDMRLogin 2-17
Put command 2-28 Rtssdm FORCE command 2-31
Pwd command 2-28 Runique command, restricted shell 2-28
Quit command 2-28
Quote command 2-28

Wireless Networks Family SDM–SX User Guide SDMPL011

10-10 Index

S Sunique command, restricted shell 2-29

Sys command, RMI 2-48
SDM alarms, SDM related, overview 2-19
SysB node state, at the RMI 2-47
SDM Backup utility 3-11, 3-14
SysB state, at the MAP 2-3
SDM logs 2-77
System command, restricted shell 2-28
SDM MAP level 2-2
System image backup
SDM to CM LAN, commissioning IP addresses
overview 3-13
3-3, 7-9
procedure 6-26
SDM–LAN connectivity commissioning 7-4, 7-9,
System image tape, partial restore of files, procedure
7-15, 7-22, 7-30, 7-35, 7-42, 7-48
6-49
sdmbkup command 3-11, 3-14
System recovery
Sdmmtc command, restricted shell 2-25
full restore from backup tapes 6-35
SDMRLogin
restoring files 6-49
Bsyapp command 2-17
System states, at the RMI 2-45
Bsyhw command 2-17
Help command 2-17
Locate command 2-17 T
Logout command 2-18 Tape drive, cleaning procedure 4-50
Ls command 2-18 Tapes
Offlapp command 2-17 for backup and restore 3-11
Ping command 2-18 listing contents of backup tape 3-15
Ps command 2-18 telnet, using 2-36
QuerySDM command 2-18 Telnet access 3-23
Rtsapp command 2-17 Tenex command, restricted shell 2-29
Rtshw command 2-17 Terminal servers, description 1-24
Who command 2-18 Theshold values, changing 2-66
Who_is_on command 2-18 Time and date, setting 6-18
SDMRLogin command, MAP 2-16 Time command, RMI 3-7
Send command, restricted shell 2-28 Time zone, setting 6-18
Sendport command, restricted shell 2-28 Time zone, date and time, overview 3-7
Service layer software, components 1-19 Trace command, restricted shell 2-29
SFT access 3-23 Trnsl command, MAP 2-8
Site command, restricted shell 2-28 Troubleshooting
Size command, restricted shell 2-28 fault diagnosis 2-93
Slot numbers, assigning 1-7 fault reporting 2-92
Software Log Delivery application 2-91
application layer 1-19 the SDM fault tolerant platform 2-92
backup and restore overview 3-11 Tst command, RMI 2-52
base layer 1-19 Type command, restricted shell 2-29
installation and commissioning 3-1
service layer 1-19
Software and data, restoring, overview 3-14
U
Umask command, restricted shell 2-29
Split command, RMI 3-7 Uprading to an FT system 8-29
State mismatches 2-101 User class profiles 3-8
State monitoring User command, restricted shell 2-29
at the MAP display 2-3 User command, RMI 3-7
at the RMI 2-42, 2-46 User group capabilities 3-8
Static information 2-39 User interfaces, for maintenance 1-20
Status command, restricted shell 2-28 Users class, removing users, overview 3-11
Storage command, RMI 2-62 Users group
Struct command, restricted shell 2-28

297-5061-901 Standard 01.01 December 1998

 Index 10-11

adding new user, procedure 6-10

removing a user, procedure 6-10
W
Who command, restricted shell 2-25
Who command, SDMRLogin 2-18
V Who_is_on command, restricted shell 2-25
Verbose command, restricted shell 2-29 Who_is_on command, SDMRLogin 2-18
Viewing dcemonitor status file 6-97 Workstations, clients supported by the SDM 1-22
Viewing logical volumes 2-63
Viewlogfile command, restricted shell 2-26

Wireless Networks Family SDM–SX User Guide SDMPL011

Wireless Networks Family
SuperNode Data Manager
User Guide

Product Documentation—Dept 3423

Northern Telecom
P.O. Box 13010
RTP, NC 27709–3010
1–800–684–2273
(1–800–NTI–CARE)
 1998 Northern Telecom
All rights reserved
NORTHERN TELECOM CONFIDENTIAL: The
information contained in this document is the property of
Northern Telecom. Except as specifically authorized in writing
by Northern Telecom, the holder of this document shall keep
the information contained herein confidential and shall protect
same in whole or in part from disclosure and dissemination to
third parties and use same for evaluation, operation, and
maintenance purposes only.
Information is subject to change without notice. Northern
Telecom reserves the right to make changes in design or
components as progress in engineering and manufacturing
may warrant.This equipment has been tested and found to
comply with the limits for a Class A digital device pursuant to
Part 15 of the FCC Rules, and the radio interference
regulations of the Canadian Department of Communications.
These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in
a commercial environment. This equipment generates, uses
and can radiate radio frequency energy and, if not installed and
used in accordance with the instruction manual, may cause
harmful interference to radio communications. Operation of this
equipment in a residential area is likely to cause harmful
interference in which case the user will be required to correct
the interference at the user’s own expense
Allowing this equipment to be operated in such a manner as to
not provide for proper answer supervision is a violation of Part
68 of FCC Rules, Docket No. 89-114, 55FR46066
DMS, DMS SuperNode, and MAP are trademarks of Nortel.
HP, HP-UX, and HP9000 are trademarks of Hewlett-Packard
Company. OSF DCE is a trademark of Open Software
Foundation, Inc. UNIX is a trademark licensed exclusively
through X/Open Company Ltd. Sun and SPARC are
trademarks of Sun Microsystems, Inc. VT100 is a trademark of
Digital Equipment Corporation. Ethernet is a trademark of
Xerox Corporation. AIX and IBM are trademarks of
International Business Machines Corporation. Motorola is a
trademark of Motorola, Inc.
Publication number: 297-5061-901
Product release: SDMPL011
Document release: Standard 01.01
Date: December 1998
Printed in the United States of America