1) Layer 3 stack routing (?) problem after slave unit restarts.
Boot code: 20003
----- LAN1 SGE2000 Level 3 stack:
`-----------Unit 2 (slave)
Unit 1 (master)
The problem scenario:
NB: It is only applicable to the situation when we use different subnets, in other words,
the Layer 3 functionality of SGE2000 is involved. No such issues appear when all the hosts
are in one VLAN, whether they are connected to different units in a stack or not.
If the connection between Unit 1 and 2 is lost (I unplug the cable), slave unit ( Unit 2 ) resets,
and comes up back to operation as a slave. It's OK.
But the host ws1 (from LAN2) is not able to communicate to cmputers in LAN1 after the event.
If I go to the web interface of the stack and do the ARP-table flush, some pings may pass
but the next second the connectivity is lost again.
All the ports involved in communication are in "forwarding" state.
Sometimes, if I do a manual flush on Dynamic table in Bridging, communication
becomes OK. Sometimes it doesn't help. Even if flushing arp cache too.
If I unplug ws1 from the switch and plug it back, the connectivity becomes OK.
Flushing arp cache on ws1 doesn't help.
If I restart the whole stack, the connectivity is OK.
What's the problem with restarting a slave unit? Why the routing connectivity is lost?
2) Another problem is when trying to bind an ACL to the interface
it simply reports:
|Line No.||Error Type||Value||Diagnostic|
|1||Unknown value||Cannot apply because lack of HW resources..|