I2C - Avaya Media Processing Server 1000 Hardware Installation And Maintenance

Hide thumbs Also See for Media Processing Server 1000:
Table of Contents

Advertisement

3. Verify the configuration of the bootptab and check that all MAC/IP addresses are correct.
4. Remove one NIC from the backplane to determine if an arbitration problem exists.
5. Verify that the NICs are booted in the backplane. If the NIC fails to boot due to a hardware or
configuration problem it resets and tries to reload. When the card reboots, all Ethernet
connections to the cards in the backplane are interrupted.
6. Check the status of external Ethernet hubs or switches.
7. Check the server for reboot or failure.
8. Review the alarm log to gain additional information about the failure.

I2C

A NIC monitors several hardware devices in its chassis through an I2C buss. Several I2C busses
are in the backplane; most are shared, but a dedicated I2C exists for backplane slots 1 through 6. A
shared buss implies that all devices attach to a common buss and each part is addressable from
control logic. On a shared buss, a device must release control of the buss before other devices are
addressable.
The following is a list of shared I2C busses:
• power supply temperature control buss
• power supply voltage monitor buss
• power supply power utilization or current buss
• SCSI disk control
• TMS temperature control buss
the NIC uses the dedicated slot to retrieve the EEPROM settings, including part number and
revision, from the various TMS hardware in the backplane.
Devices attached to the I2C buss receive power from an unswitched 5-volt supply. the NIC can then
retrieve information from the EEPROMs of the devices even though power for the slot is off.
To interpret information retrieved from the I2C buss, the EEPROM on the device must be
programmed, and the NIC must recognize the device from the cardtypes.cfg table.
The following can cause shared buss errors:
• faulty device on a shared buss that does not release control
• unrecognized device – no entry for device in cardtypes.cfg
• EEPROM on device not programmed
Troubleshooting
1. Review the alarm log to determine if there is a conflict in the card types file.
2. Check the status using the NCD chassisinfo command for an unprogrammed device.
3. Because the I2c receives power from an unswitched voltage source, the only way to isolate
a fault is to remove all cards including power supplies from the backplane. Install one NIC,
October 2014
Avaya Media Processing Server 1000 Hardware Installation and Maintenance
Comments? infodev@avaya.com
I2C
191

Advertisement

Table of Contents
loading

Table of Contents