EasyManuals Logo

Allied Telesis SwitchBlade x3100 Series User Manual

Allied Telesis SwitchBlade x3100 Series
940 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #513 background imageLoading...
Page #513 background image
Configuring VLAN Based HVLAN Introduction
4-193
Software Reference for SwitchBlade x3100 Series Switches (Layer Two Switching)
The Customer Interfaces that are participating in the VLAN-based HVLAN tunnel should not be a member
of the HVLAN; only the Network direction interfaces are a member of the HVLAN.
The Network Interfaces that are tunneling Customer VLANs via the VLAN-based HVLAN tunnel should
not be a member of the Customer VLANs (the system will configure the Customer VLANs on the Network
Interfaces).
Customer Interfaces that are participating in the VLAN-based HVLAN tunnel can be a member of many
VLANs, tagged or untagged (only one untagged VLAN).
Any single VLAN can map to only one VLAN-based HVLAN tunnel. The HVLAN tunnel is defined by the
creation of the HVLAN and the interfaces that are a member of the HVLAN. When a VLAN is associated
with a tunnel, it will be associated with the tunnel on all of the interfaces that are a member of the tunnel
(HVLAN).
To change the VID of an existing HVLAN, the HVLAN must be removed with the DESTROY HVLAN com-
mand and created again.
Do not use the “tagall=on” setting; this is only used for port-based HVLAN tunneling.
IGMP packets are not tunneled; and therefore, if multicast is to be supported, then the Customer Interface
should be enabled for IGMP Snooping.
DHCP packets can either be tunneled or Relayed/Snooped by the local Network Access product. If tunnel-
ing of DHCP packets is desired, then DHCP Relay/Snooping can be disabled on the Customer Interface for
the VLANs that are to be tunneled, or DHCP Snooping could be used. If the desire is to have the Network
Access product handle the DHCP packets outside of the tunnel, then DHCP Relay (not DHCP Snooping)
can be configured on the Customer Interface for the VLANs.
4.9.5.3 Feature Interactions (Port-based and VLAN-based HVLANs)
An HVLAN can be either Port-based or VLAN-based, but not both.
An HVLAN cannot be changed to/from Port-based from/to VLAN-based; the HVLAN must be destroyed
and recreated to be changed.
4.9.6 Configuration Procedure
The following procedure creates the VLAN-based HVLANs shown in Figure 4-26.
TABLE 4-29 Configuration Procedure for VLAN Based HVLAN
Step Command Description
Create HVLAN
1
CREATE HVLAN=S_200 VID=200 TYPE=VLAN-
TUNNEL
CREATE HVLAN=S_300 VID=300 TYPE=VLAN-
TUNNEL
Creates a VLAN-based HVLAN.

Table of Contents

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the Allied Telesis SwitchBlade x3100 Series and is the answer not in the manual?

Allied Telesis SwitchBlade x3100 Series Specifications

General IconGeneral
BrandAllied Telesis
ModelSwitchBlade x3100 Series
CategorySwitch
LanguageEnglish

Related product manuals