Avaya G700 Troubleshooting Manual page 34

Local Survivable Processor
Symptom
Avaya™ S8300 Media Server
configured as a Local Survivable
Processor (LSP) has IP endpoints
registered with no Avaya™ G700 Media
Gateways registered/ IP endpoints have
no dial tone.
Avaya™ S8300 Media Server
configured as a Local Survivable
Processor (LSP) is backing up an
Avaya™ S8700 Media Server, and the
translations are corrupt on the LSP.
Avaya™ S8300 Media Server
configured as a Local Survivable
Processor (LSP) is backing up an
Avaya™ S8700 Media Server, and
translations have been copied to the
LSP. Now the LSP is in a rolling reboot.
G700 Troubleshooting
Root Cause
The G700 registered briefly 1. Login as craft or cust to the LSP and run the Avaya SA or SAT window.
during its recovery stage,
2. Run list reg to verify that phones are registered with the LSP.
thus allowing the LSP to
- If phones are registered, continue with Step 3.
accept IP phone
- If phones are not registered, this is not the appropriate resolution -- look for
registrations, but the G700 another Root Cause.
then re-registered with the
3. Run display errors and filter on errors.
primary call controller.
4. Look for Maintenance Object name MED_GTWY and Error Type 257 to
indicate the G700 did register.
5. Perform a reset system 4 on the LSP.
The S8300 has a file Escalate the problem.
named btm_parm.conf that
cannot exist on the LSP
when the LSP is backing
up an S8700 or translation
corruptions occur.
The S8300 has a file
Escalate the problem.
named btm_parm.conf that
cannot exist on the LSP
when the LSP is backing
up an S8700 or translation
corruptions occur.
© 2002 Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. or Avaya ECS Ltd., a wholly owned
subsidiary of Avaya Inc., and may be registered in the US an other jurisdictions. All trademarks identified by ® and ™ are registered
trademarks or trademarks, respectively, of Avaya Inc. All other registered trademarks or trademarks are property of their respective
Resolution
Page 3
7/5/2002 4:38 PM