Troubleshooting - AT&T OneVision DEFINITY G3 Fault Management Management Manual

Verifying connectivity

Hide thumbs Also See for OneVision DEFINITY G3 Fault Management:

Table of Contents

TroubleShooting

2. Add the following to your PATH:

/usr/OneVision/bin

3. Type mapmerge map_db

NOTE:

If you renamed map_db, replace map_db with your filename.

Result: Mapmerge integrates the new functionality of the icon state,

Inform, into your map database.

4. Repeat this procedure for each map database you customized.

TroubleShooting

If the Proxy Agent is not in contact with a DEFINITY switch, check the following

common causes for a disconnect:

Can the Proxy Agent dial out?

— Is the modem working?

— Is the phone line connected? Do you get a dial tone?

Does the Proxy Agent have a current, correct login and password for the

DEFINITY switch?

You can check the login and password on the Proxy Agent

Communications form. For more information, see Chapter 4 in the

OneVision DEFINITY G3 Proxy Agent Installation and Connectivity guide.

Is a switch management port available? Does it give a modem tone? (Call

the modem from a voice station to check.)

Can you log into the switch management port from another terminal and

modem?

Can your NMS access the Proxy Agent? (Telnet to the Proxy Agent to find

out.)

Is the Proxy Agent running? (Telnet to the Proxy Agent and run g3stat

For GIS StarSENTRY users: Did you run the Map Merge program after you

installed Fault Management?

If the Proxy Agent is still disconnected from the switch after you check all of these

items, call the Technical Service Center for assistance.

Issue 1 June 1995

Table of Contents

Do you have a question about the OneVision DEFINITY G3 Fault Management and is the answer not in the manual?