3Com 4510G, Руководство по настройке

Страница: 139 / 1166

6-13
To do… Use the command… Remarks
Enter Layer-2
aggregate
interface view
interface
bridge-aggregation
interface-number
group view
Enter port
group view
port-group manual
port-group-name
Use either command.
z
In Ethernet interface view,
the subsequent
configurations apply to the
current port.
z
In port group view, the
subsequent configurations
apply to all ports in the
port group.
z
In Layer-2 aggregate
interface view, the
subsequent configurations
apply to the Layer-2
aggregate interface and
all its member ports.
Configure the port link type as
hybrid
port link-type hybrid
Required
Configure the port(s) to permit the
packets of the specified
protocol-based VLANs to pass
through untagged
port hybrid vlan vlan-id-list
{
tagged
|
untagged
}
Required
Associate the hybrid port(s) with
the specified protocol-based
VLAN
port hybrid protocol-vlan
vlan vlan-id
{
protocol-index
[
to protocol-end
] |
all
}
Required
z
Do not configure both the
dsap-id
and
ssap-id
arguments in the
protocol-vlan
command as 0xe0
or 0xff when configuring the user-defined template for
llc
encapsulation. Otherwise, the
encapsulation format of the matching packets will be the same as that of the
ipx llc
or
ipx raw
packets respectively.
z
When you use the
mode
keyword to configure a user-defined protocol template, do not set
etype-id
in
ethernetii etype etype-id
to 0x0800, 0x8137, 0x809b, or 0x86dd. Otherwise, the
encapsulation format of the matching packets will be the same as that of the IPv4, IPX, AppleTalk,
and IPv6 packets respectively.
z
A protocol-based VLAN on a hybrid port can process only untagged inbound packets, whereas the
voice VLAN in automatic mode on a hybrid port can process only tagged voice traffic. Therefore,
do not configure a VLAN as both a protocol-based VLAN and a voice VLAN. For more information,
refer to
Voice VLAN Configuration .
z
After you configure a command on a Layer-2 aggregate interface, the system starts applying the
configuration to the aggregate interface and its aggregation member ports. If the system fails to do
that on the aggregate interface, it stops applying the configuration to the aggregation member
ports. If it fails to do that on an aggregation member port, it simply skips the port and moves to the
next port.