This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
VLAN Trunking
VLAN trunking is also known as tagged VLAN and 802.1Q tagging. The 802.1Q tagging enables a networking device to add information to a frame at Layer 2 to identify the VLAN membership of the frame. Tagging also enables network environments to have VLANs that span multiple devices. A device that receives the packet reads the tag and recognizes the VLAN to which the frame belongs.
When you configure tagging on bridged interfaces, the VLAN configuration must be identical on both ports of the bridge.
Tagged VLANs are not supported on the management interfaces (ports 0/1 and 0/2).
For example, if your WAN link uses VLAN 412, you declare VLAN 412 as a tagged VLAN in the NetScaler instance, and bind it to both ports of the bridge (such as ports 10/1 and 10/2), as shown in the example below.
Figure 1. Tagged VLANs for VLAN trunking. VLAN 412 is tagged
VLANs can be declared in either of two ways:
-
From the System > Settings > Configure NSVLAN Settings dialog box. This method declares a VLAN whose broadcast traffic is isolated from other VLANS. This method is recommended for the management subnet. It requires a restart to take effect.
Note: This VLAN configuration method is neither synchronized nor propagated in high availability mode. Therefore, you must perform the configuration independently on each appliance of a high availability setup.
- From the Create VLANs dialog box (reached from Network > VLANs > Add). This method does not create an isolated broadcast domain, from traffic originating in the NetScaler instance until we bind the NetScaler IP addresses to the VLAN. Adding such a VLAN does not require a restart. This method is recommended for all VLANs except the management subnet.
Share
Share
In this article
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.