Avaya BayStack Operating System Switching Software (BoSS 3.1) for BayStack 460, 470 aviso descargar pdf (Pagina 46)

215148-D

Table 16

Log Entry

Incompatible interop value, module <physical id> failed to join stack

Explanation

module <physical id> type cannot interoperate with the base unit’s

interop value.

Diagnostic Info

Replace module <physical id> with another module type that is

compatible with the base’s interop value.

Table 17

Log Entry

Incompatible operational mode, module inactive, module <physical

id> failed to join stack

Explanation

module <physical id> has transitioned to inactive state. When there is

a configuration change, the base unit will re-transmit the “UNP”

packet and a unit upon receiving it may find that it is no longer active

or in the stack.

Diagnostic Info

Find out why module <physical id> became inactive.

Table 18

Log Entry

IN stack port wrapped; check for bad cable or unit.

Explanation

The unit did not receive any acknowledgment when it communicates

with its upstream unit.

Diagnostic Info

First, determine whether you have a bad cable or a bad upstream

unit. If the cable connected to IN stack port is bad, the stack port on

both ends of the cable should be wrapped out and the units attached

to the cable should still be in stack. Also, the unit that is attached to

the other end of the cable should have the entry "OUT stack port

wrapped; check for bad cable or unit". Replace the cable with a good

one, and reboot the units that were attached to this cable.

On the other hand, if the upstream unit is bad, the downstream led on

the upstream unit should be amber and the upstream unit will not be

in stack. Replace the upstream unit.

Table 19

Log Entry

OUT stack port wrapped; check for bad cable or unit.

1 2 ... 41 42 43 44 45 46 47 48 49 50 51 ... 85 86

Sin comentarios

Avaya BayStack Operating System Switching Software (BoSS 3.1) for BayStack 460, 470 aviso Pagina 46