12.07.2015 Views

Management Guide - Kamery IP

Management Guide - Kamery IP

Management Guide - Kamery IP

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

VLAN Configuration3Enabling QinQ Tunneling on the SwitchThe switch can be configured to operate in normal VLAN mode or IEEE 802.1Q(QinQ) tunneling mode which is used for passing Layer 2 traffic across a serviceprovider’s metropolitan area network. You can also globally set the Tag ProtocolIdentifier (TPID) value of the tunnel port if the attached client is using a nonstandard2-byte ethertype to identify 802.1Q tagged frames.Command Usage• Use the TPID field to set a custom 802.1Q ethertype value on the selectedinterface. This feature allows the switch to interoperate with third-party switchesthat do not use the standard 0x8100 ethertype to identify 802.1Q-tagged frames.For example, if 0x1234 is set as the custom 802.1Q ethertype on a trunk port,incoming frames containing that ethertype are assigned to the VLAN contained inthe tag following the ethertype field, as they would be with a standard 802.1Q trunk.Frames arriving on the port containing any other ethertype are looked upon asuntagged frames, and assigned to the native VLAN of that port.• All ports on the switch will be set to the same ethertype.Command Attributes• 802.1Q Tunnel Status – Sets the switch to QinQ mode, and allows the QinQtunnel port to be configured. The default is for the switch to function in normalmode.• 802.1Q Ethernet Type – The Tag Protocol Identifier (TPID) specifies the ethertypeof incoming packets on a tunnel port. (Range: hexadecimal 0800-FFFF;Default: 8100)Web – Click VLAN, 802.1Q VLAN, 802.1Q Tunnel Status. Check the Enabled box,set the TPID of the ports if the client is using a non-standard ethertype to identify802.1Q tagged frames, and click Apply.Figure 3-133 802.1Q Tunnel Status and Ethernet Type3-235

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!