09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - Avaya Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Communication Manager Maintenance Object Repair Procedures<br />

minute. The repeat parameter may be used to close the relay for a longer length of time where<br />

the number of the repeat is the number of minutes for which the device will be activated (5<br />

minutes is the suggested repeat value).<br />

Note:<br />

Note: S8700-series servers and S8500 servers equipped with G650 carriers will differ<br />

from this MO, in that the IPSI board provides the CPAD leads. The intent for the<br />

feature is in other ways the same.<br />

The test customer-alarm location command is provided to allow a technician to check<br />

if the customer-provided alarming device is correctly installed and functional. See<br />

Customer-Provided Alarming Device Test (#115) for a description of the test. It is recommended<br />

that this test be run at least once after both the switch and the customer alarm have been<br />

installed.<br />

Connectivity paths<br />

The server communicates with a PN’s Maintenance circuit pack via the following path. (Uplink<br />

messages back from this Maintenance circuit pack to the server take the reverse path.)<br />

Messages flow from the server’s processor to an IPSI connected PN’s TN2312AP IPSI circuit<br />

pack’s Packet Interface circuit, over this PN’s LAN bus to its Expansion Interface circuit pack,<br />

across the fiber link to the active PN’s Expansion Interface circuit pack, and over a serial link to<br />

the PN’s Maintenance circuit pack.<br />

The PN’s Maintenance circuit pack must be physically inserted into the dedicated slot marked<br />

Maintenance in the A carrier of the PN. The serial links from the PN’s Maintenance circuit pack<br />

to the Expansion Interface circuit packs are physically connected from this dedicated slot to<br />

slots 2A01 and 2B02 (2B02 is used only if there is duplicated Port Network Connectivity). The<br />

serial link from slot 2A01 to the maintenance slot is hard-wired into the backplane of carrier A,<br />

whereas the serial link from slot 2B02 to the maintenance slot is a ribbon cable connecting the<br />

two slots. The serial link from the PN’s Maintenance circuit pack to the terminal is also a ribbon<br />

cable which plugs into a connector labeled TERM on the back of carrier A.<br />

The maintenance strategy for the PN’s Maintenance circuit pack consists of checking the<br />

integrity of the communications path to/from the PN’s Maintenance circuit pack, testing<br />

individual hardware components on the PN’s Maintenance circuit pack, and keeping the alarm<br />

LEDs up-to-date. The individual hardware components include the serial interfaces which<br />

handle the serial links connected to the PN’s Maintenance circuit pack. There are three serial<br />

interfaces, one for each possible Expansion Interface circuit pack and one for the terminal.<br />

Since the PN’s Maintenance circuit pack supports environmental maintenance in the PN,<br />

trouble with the PN’s Maintenance circuit pack can cause environmental maintenance to falsely<br />

detect problems. In a multicarrier cabinet PN, these environmental MOs include: POWER<br />

(Battery and Battery Charger), CARR-POW (Carrier Port Power Unit), AC-POWER (AC Power),<br />

CABINET (Cabinet Sensors), EMG-XFER (Emergency Transfer), EXT-DEV (External Device<br />

Alarm), and CUST-ALM (Customer-Provided Alarming Device). In a single carrier cabinet PN,<br />

these environmental MOs include DC-POWER (Single Carrier Cabinet Power), EMG-XFER<br />

(Emergency Transfer), EXT-DEV (External Device Alarm), and CUST-ALM (Customer-Provided<br />

Alarming Device).<br />

954 Maintenance <strong>Alarms</strong> for <strong>Avaya</strong> Communication Manager, Media Gateways and <strong>Server</strong>s

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!