diff --git a/docs/en-US/pvlan.xml b/docs/en-US/pvlan.xml index d569507f973..f647d932538 100644 --- a/docs/en-US/pvlan.xml +++ b/docs/en-US/pvlan.xml @@ -113,19 +113,19 @@ ports. Configure the switch port connected to the router in PVLAN promiscuous trunk mode, which would translate an isolated VLAN to primary VLAN for the PVLAN-unaware router. Note that only Cisco Catalyst 4500 has the PVLAN promiscuous trunk mode to connect - both normal VLAN and PVLAN to a PVLAN-unaware switch. For other Catalyst PVLAN support - switch, connect the switch to upper switch by using cables. The number of cables should be - greater than the number of PVLANs used. + both normal VLAN and PVLAN to a PVLAN-unaware switch. For the other Catalyst PVLAN support + switch, connect the switch to upper switch by using cables, one each for a PVLAN + pair. Configure private VLAN on your physical switches out-of-band. - Before you use PVLAN on XenServer and KVM, enable Open vSwitch (OVS) . + Before you use PVLAN on XenServer and KVM, enable Open vSwitch (OVS). - OVS on XenServer and KVM does not support PVLAN. Therefore, simulate PVLAN on OVS - for XenServer and KVM by modifying the flow table and tagging every traffic leaving - guest VMs with the secondary VLAN ID. + OVS on XenServer and KVM does not support PVLAN natively. Therefore, &PRODUCT; + managed to simulate PVLAN on OVS for XenServer and KVM by modifying the flow + table. @@ -176,8 +176,8 @@ VLAN ID: The unique ID of the VLAN. - Isolated VLAN ID: The unique ID of the Secondary - Isolated VLAN. + Secondary Isolated VLAN ID: The unique ID of the + Secondary Isolated VLAN. For the description on Secondary Isolated VLAN, see .