IV

_________________________________________________________________________________

Contents__________________________________________________________________________________________________________

About this document

Chapter 1: DMS Info 1-1General 1-1Image Building 1-1DMS Software Changes 1-1Lab Operations Team Members 1-2

Chapter 2: DMS Login 2-1Sources from which DMS commands are recognized: 2-1VT100 Terminals 2-2After login 2-3Changing your Password 2-3Main area's within the DMS that lab users will require access to: 2-4MTC Screen layout 2-5

Chapter 3: PM Map Level 3-1POSTing and Troubleshooting from the PM Map level 3-1 Peripheral loading and RTSing 3-3Block diagram of PSide/CSide terminology 3-5

Chapter 4: DCH Map Level 4-1POSTing and Troubleshooting from the DCH Map level: 4-1 TMS to NAV simplified flow chart 4-3POSTing and Troubleshooting from the DCH Map level cont.: 4-4 Front view of TMS shelf layout 4-5

Chapter 5: ISG Map Level 5-1POSTing and Troubleshooting from the ISG Map level 5-1

Chapter 6: TPC Map Level 6-1POSTing and Troubleshooting from the TPC Map level 6-1

Chapter 7: MP Map Level 7-1POSTing and Troubleshooting from the MP Map Level 7-1

________________________________________________________________________________________________DMS User Guide

Contents V__________________________________________________________________________________________________________

Chapter 8: CARRIER Map Level 8-1POSTing and Troubleshooting from the CARRIER Map Level. 8-1 POSTing all CARRIERS within a PM: 8-3Posting an induvidual CARRIER 8-3

Chapter 9: TTP Map Level 9-1POSTing and Troubleshooting from the TTP Map level 9-1

Chapter 10: LNS Map Level 10-1POSTing and Troubleshooting from the LNS Map level 10-1

Chapter 11 :TRAVER 11-1Introduction 11-1TRAVER of Line to Trunk 11-1 TRAVER of a Trunk to Line Call 11-4

Chapter 12:LOGUTIL 12-1Using Logutil 12-1

Chapter 13: CallTrak 13-1CallTrak Introduction: 13-1 Performing a CallTrak: 13-1 Example 1: First Leg of the Call 13-2 Example 2: Send Leg of the Call 13-5 Example 3: Third Leg of the Call 13-7

Chapter 14: DMS Image Dumps and SLM Tape Back-ups 14-1Taking an Image Dump and Tape Back-up 14-1Clearing/Setting Boot Files: 14-4Booting a SuperNode: 14-5

Chapter 15: Disaster Recovery 15-1Restoring Power: 15-1

_________________________________________________________________________________________________StanStandard 1.0 August 2003

VI

_________________________________________________________________________________________________

About this document_________________________________________________________________________________________________

The following table provides an overview of the contents of each chapter.

Chapter Subject/s

1) DMS Info General information about the lab and the lab Operations

Team.

2) DMS login Lists the various DMS access methods available.

3) PM Map level Posting and Troubleshooting from the Peripheral Module

(PM) Map level.

4) DCH Map level Posting and Troubleshooting from the D-Channel Handler

(DCH) Map level.

5) ISG Map level Posting and Troubleshooting from the ISDN Service

Group (ISG) Map Level.

6) TPC Map level Posting and Troubleshooting from the TOPS Position

Controller (TPC) Map Level.

7) MP Map level Posting and Troubleshooting from the Maintenance

Position (MP) Map Level.

8) CARRIER Map Posting and Troubleshooting from the CARRIER Map

level Level.

9) TTP Map level Posting and Troubleshooting from the Trunk Test

Position (TTP) Map Level

10) LNS Map Posting and Troubleshooting from the LiNeS (LNS)

level Map Level

11) TRAVER Introduction to TRAnslations VERification tool.

12) Logutil Lists the steps required to view DMS logs

__________________________________________________________________________________________________________DMS User Guide

About this document VII__________________________________________________________________________________________________________

Chapter Subject/s

13) CallTrak Lists the steps required to capture call details via

CallTrak

14) DMS Image Details the commands required to take a manual Image

Dumps & SLM Dump, back-up the files on disk to tape, and Booting a SuperNode

Tape Back-ups

15) Disaster A quick overview of the steps required to restore power

Recovery and software to the DMS in the event of a prolonged

______________________________________________________________________________________________________________________Standard 1.0 August 2003

2-1

Chapter 2: DMS Login

This chapter lists the various DMS access methods available.

Sources from which DMS commands are recognized:

DMS commands and queries must be initiated from one of the following sources

i) VT100 MAP Terminals, presently located behind ROCHA isle "D"

ii) XTERM, via UNIX box or EXCEED.

Before any command sequence can be input, the selected terminal must be, "logged in" to the switch.

________________________________________________________________DMS User Guide

2-2 Chapter 2: DMS Login______________________________________________________________________________________________________________________

VT100 Terminals

A) Check monitor label to ensure that the terminal is connected to the correct switch (ROCHA or ROCHB).

B) Ensure that the SuperNode is in an operating state by verifying it's status on the proper Restart Terminal InterFace (RTIF). All RTIF's are labeled and sit on the shelves above the VT100 Terminals. The status appears on the top line of the inverse video and should be flashing "A1".

C) Return to the MAP terminal and press the canriage return a couple of times.

If the terminal is already "logged" in, a cursor (>) will appear on the screen as well as an information line. You should now be able to proceed with your command sequences.

If the terminal does not respond to (cr), proceed with the following:

i) Press the "REFRESH" key twice. A ">> " will appear on the left hand side of the screen and you may hear a "beep."

ii) When this occurs, type >LOGIN (c/r).

iii) The DMS will respond with "User name," type your user name (c/r).

iv) The DMS will then ask for "Password," type your password (c/r).

At this point the DMS should provide you with info about the switch you are on.

See your DMS Lab Prime if you do not already possess a User name and Password, or use our visitor-user names "GuestX" and Password "GuestY," where X=1, 2, or 3, and Y=A, B, or C, respectively.

________________________________________________________________________________________Standard 1.0 August 2003

Chapter 2: DMS Login 2-3______________________________________________________________________________________________________________________

After Login

Before proceeding, get into the habit of scanning all information displayed on your screen! Every 180 days the DMS will WARN YOU to enter a new password. When a password change is necessary a message will be displayed on your terminal telling you how many login sessions you have left before you will no longer be able to login!

Changing your Password

To change your password, type >PASSWORD (c/r) and then satisfy the prompts offered by the DMS.

_______________________________________________________________________________DMS User Guide

2-4 Chapter 2: DMS Login__________________________________________________________________________________________________________

Main are Main areas within the DMS that lab users may require access to: Throughout the rest of this document you must type (c/r) at the end of every command line, even though it is not shown from this point on.

Generally speaking most DMS users within our group will require access to three main areas within the DMS, and they are PM, Trks, & Lns. Accessing the PM map level will allow you to work with any DMS Extended Peripheral Module (XPM). The Trks map level will allow you to work with your Tl's. While the Lns map level will allow you to troubleshoot potential telephone Line Card problems.

To access map levels type> MAPCI; MTC from this point you can directly access anyone of the 10 main Map levels listed across the top of your screen. So to enter the PM level at this point, type> PM. As can be seen below all DMS commands can be strung together using a semi colon.

All optional parameters are in Italic.

i.e.: >MAPCI;MTC;PM;POST LTC 0 (See Page 3-2 for GUI Display)

This will bring you into the PM level, post LTC 0, and allow you to access all the sub commands and sub levels within the main PM map level. Once in a main Map level one can change to any other main Map level by typing the desired heading which is listed across the top of the screen.

_Figure 2-1

_______________________________________________________________________________________Standard 1.0 August 2003

Chapter 2: DMS Login 2-5______________________________________________________________________________________________________________________

MTC Scr MTC Screen LayoutAll Alarm displays vary depending on system status, and all Map level Displays in this document represent TEAM Windows.

Figure 2-2

________________________________________________________________________________________

DMS User Guide

3-1______________________________________________________________________________________________________________________

Chapter 3: PM Map Level

This chapter covers Posting and troubleshooting from the Peripheral Module (PM) Map Level.

POSTing and Troubleshooting from the PM Map Level

All optional parameters are in Italic

To post an Extended Peripheral Module (XPM), type:

> MAPCI; MTC; PM; POST LTC 0

The following list is a breakdown of each line of information displayed in Figure 3-1.

Top Line: Info on type of connection and Switch name

2nd Line: Main Map levels. All allow access to Commands & Sub levels

3rd Line: Highest Alarms within each main Map level ( . = No Alarms)

4th Line: Severity of alarm. (*C* = Critical, M = Major, =Minor)

5th Line: Headings for potential status of all PM's

6th Line: Overall view of all PM's and their present status

7th Line: Overall view of all PM's of posted type and their present status

8th to 10th Line: Overall status of PM & status of each unit within the PM

Shaded Area: Command Bar. Numbers are equivalent of text, (ie:7 = Bsy)

________________________________________________________________________________________DMS User Guide

3-2 Chapter 3: PM Map level

Figure 3-1: GUI Display

_______________________________________________________________________________________Standard 1.0 August 2003

Chapter 3: PM Map level 3-3

______________________________________________________________________________________________________________________

Peripheral Loading and RTSing***************************************************************From this point forward, before attempting to effect any of the procedures outlined in this document, make sure you fully understand who/what will be affected by your actions!*********************************************************************

It may be necessary at times to reload the DMS peripherals. A power failure (depending on the severity) may cause the Extended Peripheral Modules (XPM's) to lose their software load. In most instances the DMS software will proceed with the reload once the SuperNode is returned to service. It will also be necessary to reload an XPM if a maintenance action required a power down or if the current XPM software load needs to be upgraded or has been corrupted. The XPM loading procedures are as follows:

1) XPM's (LTC, DTC, DTCI, TMS)

From the MAP terminal type in:

> MAPCI; MTC; PM; POST LTC 0

As can be seen in Figure 3-1, the terminal will display the overall status of the peripheral (in this case LTC 0), as well as the status of both units within the peripheral. In this particular case the overall status of LTC 0 is ISTb (In Service Trouble). However, Unit 0 is Act InSv (Active In Service), while Unit 1 is Inact InSv (Inactive) and as such both require no maintenance. The overall PM ISTb alarm (line 8 on Fig.3-1) is a result of 3 PSide Link failures. PSide links are links to other nodes like NAV. Thus the problem in this case must be inspected from the Trks map level, (Page 8-1, of this document)

If the status of the PM or any Units within is SysB (SYStem Bsy) - wait up to 20 minutes. The system software may be trying to reload the PM. If it is still SysB after 20 minutes, utilize one of the following procedures.

Note: After any RTS (Retum To Service) command it is normal for the affected equipment to change from a ManB (Manual Busy) state to an ISTb state for a few minutes before achieving an InSv state.

A) Overall PM status is OffL Set up an interview with me to see more…………………………………………………………….………………………………………………………………

B) Overall PM status is ManB Set up an interview with me to see more…………………………………………………………….……………………………………………………………….

______________________________________________________________________________________________________________________ DMS User Guide