Alcatel-Lucent 6850-48 网络指南

下载
页码 1162
Configuring VLAN Rule Definitions
Defining VLAN Rules
page 8-18
OmniSwitch AOS Release 6 Network Configuration Guide
September 2009
-> vlan 200 protocol ethertype 0800
ERROR: Part of ip ethernet protocol class - use <vlan # protocol ip-e2> instead
The following table lists keywords for specifying a protocol type:
Note that specifying a SNAP protocol type restricts classification of mobile port traffic to the ethertype 
value found in the IEEE 802.2 SNAP LLC frame header.
Use the no form of the 
 command to remove a protocol rule.
-> vlan 1504 no protocol dsapssap f0/f0
Defining Port Rules
Port rules do not require mobile port traffic to trigger dynamic assignment. When this type of rule is 
defined, the specified mobile port is immediately assigned to the specified VLAN. As a result, port rules 
are often used for silent network devices, which do not trigger dynamic assignment because they do not 
send traffic.
Port rules only apply to outgoing mobile port broadcast types of traffic and do not classify incoming traf-
fic. In addition, multiple VLANs can have the same port rule defined. The advantage to this is that broad-
cast traffic from multiple VLANs is forwarded out one physical mobile port. When a mobile port is 
specified in a port rule, however, its incoming traffic is still classified for VLAN assignment in the same 
manner as all other mobile port traffic. 
To define a port rule, enter vlan followed by an existing VLAN ID then port followed by a mobile 
slot/port designation. For example, the following command creates a port rule for VLAN 755:
-> vlan 755 port 2/3
In this example, all traffic on VLAN 755 is flooded out mobile port 2 on slot 3. 
Note that it is possible to define a port rule for a non-mobile (fixed, untagged) port, however, the rule is 
not active until mobility is enabled on the port. 
Use the no form of the 
-> vlan 755 no port 2/3
protocol type keywords
ip-e2
ip-snap
ipx-e2
ipx-novell
ipx-llc
ipx-snap
decnet
appletalk
ethertype
dsapssap
snap