Specifications

W5-Ethernet-Manual.doc
Version 2.0-01
Watson 5 Ethernet
Operating Manual
Revision: 2006-04-27 3-13
Figure 3-8 shows how Ethernet user interfaces are used for inband management:
MGMT3
ETH1
(ETH2)
(ETH3)
(ETH4)
DSL1
DSL2
DSL3
DSL4
1, 2, 3, 4,
4094
1
2
3
4
1
2
3
4
VLAN 1
V
L
A
N
2
V
L
A
N
3
VL
AN
4
Tagged
Untagged
1
1
Default VLAN Tag
4094
4
0
9
4
Untagged
Figure 3-8: VLAN configuration for Inband Management
For user traffic we have the same configuration as in Figure 3-7. However we have added one addi-
tional VLAN 4094 which is used for inband management. Ports ETH1 and MGMT3 are members of
this VLAN. Because the DSL ports are not member of VLAN 4094 management traffic is isolated
from user traffic and there is no access to management function through the DSL ports.
Note that port MGMT3 must use untagged packets to properly interface with the card controller.
Management packets coming from the card controller are tagged with VLAN 4094 upon ingress into
the bridging function.
3.2.5 Individual and shared forwarding databases
VLANs can have individual or shared forwarding databases (IVL or SVL operation). The Watson 5
Ethernet plugin supports 16 separate forwarding databases which can be freely assigned to VLANs.
Address learning is always done based on MAC addresses without taking VIDs into account.
IVL is required e.g. if a single server is connected to several Ethernet user ports on different VLANs
and all of the server interfaces use the same MAC address. In this case the server MAC address
will appear to move between Ethernet ports and VLANs depending upon which interface has most
recently transmitted a frame. Communication to the server will be disrupted