MUX VLAN
Background
On a data center network, the data center administrator has the following requirements: All servers of the data center can access the external network. Some servers can communicate, whereas some servers are isolated. To allow all servers to access external networks, configure communication between VLANs. If there are a large number of servers in a data center, assign VLANs to servers that cannot communicate with each other. This wastes VLAN IDs and requires great workload on network configuration and maintenance.
Multiplex VLAN (MUX VLAN) controls network resources by VLAN. MUX VLAN allows some servers in a data center to communicate and some servers to be isolated. In addition, MUX VLAN saves VLAN IDs and facilitates maintenance.
Basic Concepts
As shown in Table 5-6, a MUX VLAN is classified into principal VLANs and subordinate VLANs; a subordinate VLAN is classified into separate VLANs and group VLANs.
MUX VLAN |
VLAN Type |
Associated Port |
Access Authority |
---|---|---|---|
Principal VLAN |
- |
Principal port |
A principal port can communicate with all ports in a MUX VLAN. |
Subordinate VLAN |
Separate VLAN |
Separate port |
A separate port can communicate only with a principal port and is isolated from other types of ports. A separate VLAN must be bound to a principal VLAN. |
Group VLAN |
Group port |
A group port can communicate with a principal port and the other ports in the same group, but cannot communicate with ports in other groups or a separate port. A group VLAN must be bound to a principal VLAN. |
Principle of Communication in MUX VLAN
As shown in Figure 5-15, the principal port connects to the external network, the separate port connects to users who do not need to communicate, and the group port connects to users who need to communication. By doing this, internal users of the data center can communicate and some users are isolated.