TOC Index Search

 

Troubleshooting

Modem Does Not Answer


 
Possible Cause
Check/See
Probable Fix
There is no power to the modem.
Check the power source.
Apply power to the modem.
The modem is not connected.
The modem should be connected with a D25F cord through a 25 to 9 pin adapter to COM2.
Connect the modem correctly.
The normal D4 conductor cord is not plugged in to the correct port.
Make sure that the normal D4 cord is plugged into the Dial portion, not the Phone portion, of the modem.
Plug the normal D4 cord into the Dial portion of the modem.
There is no continuity.

Fill in the Alarm Screen.
  1. Enter the product ID in the Product ID field.
  2. If the product ID is not known, enter 2200000000

  3. Enter a valid telephone number in the Alarm Destination field.
  4. Press F8 (Chg-Keys).
  5. Press F1 (Test_Alrm).
  6. If you entered 2200000000 in Step 1 call INADS for the correct number.

The Backup Alarm Is Activated Daily at 3:00 A.M.


 
Possible Cause
Check/See
Probable Fix
The disk cartridge is not in the removable disk cartridge drive.
Check the position of the disk cartridge in the drive.
Position the disk cartridge correctly.
The disk cartridge is write protected.
Check the read/write dial on the disk cartridge.
Place the read/write dial in the "not safe" position.
The disk cartridge is not formatted.
Check the format status of the disk cartridge.
Format the disk cartridge.
The disk cartridge drive is not working correctly.
Check the operation of the disk cartridge drive during a backup.

The DCIU Link Is Not Functioning


 
Possible Cause
Check/See
Probable Fix
The DCIU Link is not assigned properly.
Check the administrator's log for translation error entries.
Check the assignment parameters in the installation manual for both the switch and the Avaya Intuity system.
Reassign the DCIU Link.
The assigned node number is not correct.
System 85 and G2 See procedure 275, word 3, field 8.
Change the Avaya Intuity node setting to match the switch setting.
If the node number listed in the Avaya Intuity system is above 20 escalate to tier 3.
DEFINITY G1 See the Display Dial Plan.

If UDP is off then the correct node number is 1.

If UDP is on determine the correct node number from the RNX field. If this field is blank then escalate to tier 3.
Change the Avaya Intuity node number to match the switch.
DEFINITY G3 See the Display Dial Plan page one.
Change the Avaya Intuity node setting to match the switch setting. If the node number listed in the Avaya Intuity system is above 20 escalate to tier 3.
Incorrect link connections.
Check for proper connections.
Adjust the connections as needed.

The Voice Ports Are Answering in Stand-alone Mode


 
Possible Cause
Check/See
Probable Fix
The ports are not assigned in the correct order.
Check the connection order by dialing the ports directly and through the UCD.
Reassign the ports.
Incorrect entry in Services to Call Numbers field or Startup Services field.
Check the entry in the Services to Call Numbers field or the Startup Services field.
Enter the correct numbers.
The link to the switch is out of service.
Check the link to the switch.
Subscribers have the wrong host PBX assigned.
Check the host PBX.
Reassign the host PBX.

DCS AUDIX� Does Not Work


 
Possible Cause
Check/See
Probable Fix
The DCS is not functional.
Check the DCS status.
Escalate to tier 3.
The Avaya Intuity system is blank on the switch screen.
See design personnel for the correct translations.
Input correct translations and save. If this does not work escalate to tier 3.

Cannot Assign Voice Ports


 
Possible Cause
Check/See
Probable Fix
Additional port activation has not been purchased by the customer.
Verify number of ports purchased by the customer. Access Customer/Services Administration from the Avaya Intuity Administration menu. Access the Feature Options screen and see the voice_ports line.
Contact sales personnel.

System Will Not Outcall


 
Possible Cause
Check/See
Probable Fix
The voice port translations are incorrect for trunk access.
Check the voice port translations for the FRL and access.
Correct the voice port translations.

System Will Not Boot


 
Possible Cause
Check/See
Probable Fix
There is a diskette in the "A" drive.
Check the "A" drive.
Remove the diskette.
The external SCSI connector circuit card terminating module is not properly connected.
Check the terminating module connection.
Properly connect the terminating module.
There is an odd number of SIMMs installed on the CPU circuit card.
Check the number of SIMMs on the CPU circuit card.
Correct the SIMM configuration.
If the system displays the following message, the problem could be the diskette cable orientation.
BIOS Not Installed
Check the diskette cable orientation on the CPU circuit card.
The tracer on the cable should be on the right as you look at the CPU circuit card.

Optional Features Not Working


 
Possible Cause
Check/See
Probable Fix
The Avaya Intuity version does not support the optional feature.
Check the Avaya Intuity version.
Contact a sales representative concerning a migration or upgrade.
The optional feature is not activated.
Check the activated optional features on the Feature Options screen.
If the customer has purchased the optional feature, activate the optional feature.
If the customer has not purchased the optional feature, refer them to their sales representative.

System Memory Test Fails


 
Possible Cause
Check/See
Probable Fix
There is a SIMM missing from the CPU circuit card.
Check the number of SIMMs on the CPU circuit card.
Correct the SIMM configuration.
There is a a defective SIMM on the CPU circuit card.
Check the condition of the SIMMs on the CPU circuit card.
Replace the defective SIMM.

The Keyboard Is Not Operating


 
Possible Cause
Check/See
Probable Fix
The keyboard is not plugged in.
Check the keyboard connection.
Shut down the system and plug in the keyboard.
The keyboard is "frozen."
Check the keyboard connection.
The keyboard cable is not connected to the CPU circuit card.
Check the keyboard cable connection.
Reconnect the keyboard cable.

Monitor Is Not Operating


 
Possible Cause
Check/See
Probable Fix
The video controller circuit card which has been installed is not compatible with the CPU circuit card.
Check the video controller circuit card.
Replace the video controller circuit card with a supported circuit card.
The monitor has not been turned on.
Check the monitor switch.
Turn on the monitor.
The monitor brightness has been turned down.
Check the monitor brightness knob.
Turn up the brightness.

Tip/Ring Circuit Card Is Not Recognized by the Avaya Intuity System


 
Possible Cause
Check/See
Probable Fix
The tip/ring card has incorrect switch settings.
Check the switch settings on the tip/ring cards.
The Tip/Ring cards are incorrectly numbered.
There is nothing to check in this instance. If this is the suspected problem continue with the probable fix.
Renumber the Tip/Ring circuit cards.

The Printer Is Not Operating


 
Possible Cause
Check/See
Probable Fix
The printer is not turned on.
Check the power indicator light.
Turn the printer on.
The printer cable is not connected correctly.
Check the printer connection.
Reconnect the printer.
The Avaya Intuity system has not been configured correctly.
Check the system configuration.
Reconfigure the system.
The printer has not been configured correctly.
Check the printer configuration.
Reconfigure the printer.
The printer is out of paper.
Check the paper supply.
Add paper.
The printer is jammed.
Check the printer operating panel.
Remove the paper jam.

Non-RAID Hard Disk Drive Access Troubleshooting

The following system messages are associated with non-RAID hard disk drive access failures.

The System Displays No Boot Device Available Message with Ident-Strings

If the system displays the following message along with one or more SCSI device ident-strings see the troubleshooting procedures in the System Displays No Boot Device Available Message with Ident-Strings table.

SCSI target 0 LUN 0 not found
Target-LUN x-0.....
....
Target-LUN y-0....

No boot device available
Strike F1 to retry boot, F2 for setup utility


 
Table: System Displays No Boot Device Available Message with Ident-Strings
Possible Cause
Check/See
Probable Fix
Insufficient power voltages.
Check the power supply output voltage.
  1. If the power voltage is not 5V, replace the power supply.
  2. Reboot the system.
The power cable is not properly attached to Hard Disk Drive 0.
Check the Hard Disk Drive 0 power cable connection.
  1. Correct the power cable connection to Hard Disk Drive 0.
The SCSI Bus cable is not properly attached to Hard Disk Drive 0.
Check the Hard Disk Drive 0 SCSI Bus cable connection.
  1. Correct the SCSI Bus cable connection to Hard Disk Drive 0.
The SCSI Bus cable is defective.
Check the SCSI Bus cable.
  1. Replace the SCSI Bus cable.
A pin on the Hard Disk Drive 0 SCSI Bus cable connector is bent or broken.
Check the pins on Hard Disk Drive 0 by doing the following:
  1. Remove the SCSI Bus cable.
  2. Check the pins on the hard disk drive.
  1. If a pin is bent, straighten the pin.
  2. If a pin is broken, replace the hard disk drive.

A pin on the CPU circuit card SCSI Bus cable connector is bent or broken.
Check the pins on the CPU circuit card by doing the following:
  1. Remove the SCSI Bus cable.
  2. Check the pins on the circuit card.
  1. If a pin is bent, straighten the pin.
  2. If a pin is broken, replace the CPU circuit card.

Hard Disk Drive 0 has been corrupted and the system can not access the boot image.
Check the status of Hard Disk Drive 0.
  1. If the system has a remote maintenance circuit card diagnose the hard disk drive.
  2. If the system is mirrored, boot off of the backup hard disk drive.
  3. If the system did not boot perform a surface analysis on all hard disk drives.
  4. If the system is not mirrored perform a surface analysis.
  5. Replace any hard disk drive as necessary

    If the surface analysis does not indicate that the disk should be replaced, reload the system.

The System Displays SCSI Target 0 LUN 0 Not Found Message with Several Additional Messages

If the system displays the following series of messages see the troubleshooting procedures in the System Displays SCSI Target 0 LUN 0 Not Found Message with Several Additional Messages table.

The system displays the following message:

Checking for SCSI target 0 LUN 0

After several minutes the system displays the following messages:

SCSI target 0 LUN 0 not found
Target-LUN x-0.....
....
Target-LUN y-0....

No boot device available
Strike F1 to retry boot, F2 for setup utility


 
Table: System Displays SCSI Target 0 LUN 0 Not Found Message with Several Additional Messages
Possible Cause
Check/See
Probable Fix
Hard Disk Drive 0 has been corrupted and the system can not access the boot image.
Check the status of Hard Disk Drive 0.
  1. If the system has a remote maintenance circuit card diagnose the hard disk drive and replace if necessary.
  2. If the system is mirrored, boot off of the backup hard disk drive.
  3. If the system did not boot perform a surface analysis on all hard disk drives.
  4. If the system is not mirrored perform a surface analysis.
  5. Replace any hard disk drive as necessary

    If the surface analysis does not indicate that the disk should be replaced, reload the system.

The System Displays SCSI Target 0 LUN 0 Not Found Message and Stalls

If the system displays the following message and stalls see the troubleshooting procedures in the System Displays SCSI Target 0 LUN 0 Not Found Message and Stalls table.

SCSI target 0 LUN 0 not found

At this point the system stalls.
 

Note: If you press CONTROL+ALT+DELETE the system displays the following message:
No boot device available
Strike F1 to retry boot, F2 for setup utility


 
Table: System Displays SCSI Target 0 LUN 0 Not Found Message and Stalls
Possible Cause
Check/See
Probable Fix
Hard Disk Drive 0 is defective.
Check the status of Hard Disk Drive 0.
  1. Replace Hard Disk Drive 0.

No Ident-Strings Are Displayed during Boot Procedure

If the system does not display ident-strings during the boot procedure see the troubleshooting procedures in the No Ident-Strings Are Displayed during Boot Procedure table.

Note: Once the system has tried to access the SCSI devices it will try to access Hard Disk Drive 0. If the system displays the UNIX logo, Hard Disk Drive 0 has been successfully accessed.
 
Table: No Ident-Strings Are Displayed during Boot Procedure
Possible Cause
Check/See
Probable Fix
The SCSI Bus cable is not connected properly to the CPU circuit card.
Check the SCSI cable connection to the circuit card.
  1. Correct the SCSI cable connection to the circuit card.
A pin on the SCSI Bus cable connection to the CPU circuit card is broken or bent.
Check the pins on the CPU circuit card.
  1. If a pin is bent, straighten the pin.
  2. If a pin is broken, replace the circuit card.

The System Displays Failure to Load MIP, SIP, or vfs_mount Message

If the system displays one of the following messages see the troubleshooting procedures in the System Displays Failure to Load MIP, SIP, or vfs_mount Message table.

Note: Once the system has tried to access the SCSI devices it will try to access Hard Disk Drive 0. If the system displays the UNIX logo, Hard Disk Drive 0 has been successfully accessed.

Can not load MIP

Can not load SIP

vfs_mount failed
 
Table: System Displays Failure to Load MIP, SIP, or vfs_mount Message
Possible Cause
Check/See
Probable Fix
The stand file system is corrupted.
Check the stand file status.
  1. If the system is not mirrored, or if the problem persists, restore or reload the system.

A Working System Displays WARNING Disk Drive HA0 TC0 LUX - Check Condition Message

If the system displays the following message see the troubleshooting procedures in the Working System Displays WARNING Disk Drive HA0 TC0 LUX - Check Condition Message table.

WARNING: Disk Drive HA0 TC0 LUx - Check Condition

where x is a small integer


 
Table: Working System Displays WARNING Disk Drive HA0 TC0 LUX - Check Condition Message
Possible Cause
Check/See
Probable Fix
Hard Disk Drive 0 is defective.
Check the status of Hard Disk Drive 0.
  1. Replace Hard Disk Drive 0.

The System Is Up But Not Fully Operational or Is Unpredictable

If the system is up but it is not fully operational or it is unpredictable see the troubleshooting procedures in the System Is Up But Not Fully Operational or Is Unpredictable table.
 
Table: System Is Up But Not Fully Operational or Is Unpredictable
Possible Cause
Check/See
Probable Fix
The input voltage is not correct.
Check the voltage on the line entering the power supply.
  1. Shut down the system.
  2. Inform the customer of the problem in their wiring.
The power supply output voltage is not correct.
Check the voltage on the power supply output cables.
  1. Replace the power supply.
The file system is partially corrupted.
Check the system file system.
  1. If the system is not mirrored, or if the problem persists, restore or reload the system.

System with Remote Maintenance Circuit Card Displays SCSI Disk Failure Message after POST

If, after completing the POST and memory test, the system stalls and displays messages indicating a remote maintenance circuit card and SCSI hard disk drive failure see the troubleshooting procedures in the System with Remote Maintenance Circuit Card Displays SCSI Disk Failure Message after POST table.


 
Table: System with Remote Maintenance Circuit Card Displays SCSI Disk Failure Message after POST
Possible Cause
Check/See
Probable Fix
The remote maintenance circuit card address is set to C000-CFFF.
Check the remote maintenance circuit card address.
  1. Place the BEC selector switch in the off position.
  2. Shut down the system.
  3. Reboot the system.
  4. Set the remote maintenance circuit card address to DC000-DCFFF.
  5. Stop the voice system.
  6. Shut down the system.
  7. Place the BEC selector switch in the on position.
  8. Reboot the system.

Troubleshooting Defective Blocks on Hard Disk Drives

It is not always necessary to replace a hard disk drive with defective blocks. If the defective blocks do not affect the overall system performance it is not necessary to replace the hard disk drive. Monitor the system performance prior to replacing a hard disk drive.

RAID System Displays Message BIOS Not Installed

If your system is a RAID system ignore either of the following message when displayed at startup:


Avaya Communication
http://www.avaya.com
Avaya UCS Information Development
TOC Index Search