Planning and Implementing VLANs with HP-UX

NOTE: Tagged frames originating from the HPVM guest are not supported and are discarded
at the HPVM virtual switch.
Also, only VLAN identifier configuration is allowed over virtual-switch ports. Currently,
configuration of 802.1p priorities is not allowed.
There are various scenarios where the system administrator can configure the HPVM virtual
switch to utilize the traffic isolation feature of VLAN technology.
In the following example, the HP Integrity Virtual Machines (HPVM) product combines VLAN
technology with the high availability, performance and scalability of the HP Auto Port Aggregation
technology to enable the HPVM system administrator to enforce isolation policies among guests
with resilience and high bandwidth.
6
In Figure 6 the virtual switch ports 1 and 3 for guests A and C, respectively, are configured for
the RED VLAN. Similarly, virtual switch port 2 for guest B is configured for the BLUE VLAN.
Port 4 is not configured for any VLAN.
Figure 6 VLANs in an HPVM Configuration
HPVM Guest A
app1 app2
HPVM Guest C
app1 app2
Virtual NICs
on Guests
HPVM Guest B
app1 app2
HPVM
Host
HPVM Virtual
Switch
Client Y
Client X
Client Z
VLAN-unaware
HPVM Guests
HPVM Host
lan5000
RED VLAN
lan900
lan5001
Blue VLAN
VLAN-aware
network
1 2 3 4
6. When APA is used with HPVM, the load-balancing mode of the link aggregate will always be MAC-address based
for HPVM traffic (regardless of the user-configured load-balancing mode).
VLANs on HP-UX 17