Table 11. state change table – Allied Telesis Layer 3 Gigabit Ethernet Switch x600-24Ts-POE User Manual

Page 53

Advertising
background image

x600 Series Layer 3 Gigabit Ethernet Switches Installation Guide

53

Table 11. State Change Table

Event on Master Node

Reaction on

Master

Reaction on Stack

Member

Reaction on Stack

Member

With Resiliency Link

Without Resiliency Link

Both stack links removed

No change

Fallback action

1

Re-elect master

2

XEM-STK Removed or Faulty No change

Fallback action

1

Re-elect master

2

Hardware reset (or fault)

Reset / offline

Re-elect master

Re-elect master

2

Run the NO STACK ENABLE
command

3

No change

Fallback action

1

Not allowed

Displays Error Message

Software application problem
(lock-up or continual crashes)

Reboot as stack
member

Re-elect master

Re-elect master

Software crash or lock-up

Frozen

4

Re-elect master

Re-elect master

Power-down or PSU failure

Powered down

Re-elect master

Re-elect master

Event on Stack Member

Node

Reaction on

Master

Reaction on Stack

Member

Reaction on Stack

Member

Both stack links removed

No change

Fallback action

1

Re-elect master

2

XEM-STK removed or faulty

No change

Fallback action

1

Re-elect master

2

Hardware reset (or fault)

No change

Reset/offline

Reset/offline

Run the NO STACK ENABLE
command

3

No change

Fallback action

1

Fallback action

1

Software application failover
(lock-up or continual crashes)

No change

Re-boot as slave

Reboot as stack member

software crash or lock-up

No change

Frozen

4

Frozen

4

Power-down / PSU failure

No change

Powered Down

Powered down

1.

The fallback action on a slave is first to run the fallback config script. Where there is no fallback
script, the switch will disable all its switch ports.

2.

The stack member assumes the role of stack master. In specific situations, this condition could
result in a stack containing two masters. This would present problems with network management
and the control of links that were previously aggregated.

3. The following situation will apply to a switch that has been removed from the stack by the using the

NO STACK ENABLE command:
— The switch will be unaware of further faults within the stack it of which it was previously a mem-
ber.
— If this switch is powered cycled, all links previously shutdown will remain down as a result of
running the NO STACK ENABLE command”.

4. If the slave’s ports are still up, this may cause downstream switches with trunked ports to operate incorrectly.

Advertising