-
-
-
-
Advertisement of SNIP and VIP Routes to Selective Areas
-
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!
Advertisement of SNIP and VIP Routes to Selective Areas
To advertise some SNIP addresses to selective areas, enabling DRADV mode or redistribute connect ZebOS operations cannot be used. This is because these operations send all the connected routes to ZebOS. Also, adding dummy static routes in ZebOS for the required subnets, or adding ACLs in ZebOS to filter unwanted connected routes, is a cumbersome and tedious task.
The Network Route and the Tag options address this issue. You can enable the Network Route option for only one SNIP address per subnet. The connected route for that SNIP address is sent as a kernel route to ZebOS.
For VIP and SNIP addresses, Tag, can be assigned an integer from 1 to 4294967295. This parameter can be set only when Host Route or Network Route is enabled for VIP or SNIP addresses. The tag value associated with VIP and SNIP addresses are also sent along with their routes to ZebOS. Tags with different values can be set for VIP and SNIP routes. These tag values can then be matched in route maps in ZebOS and advertised to selective areas.
Advertise SNIP Routes to Selective Areas
To configure the network route and tag parameters of a SNIP address by using the CLI:
At the command prompt, type:
-
If adding a new SNIP address:
- **add ns ip** <IPAddress>@ <netmask> -**type SNIP** -**networkroute** ( **ENABLED** | **DISABLED** ) -**tag** <positive_integer>
- show ns ip <IPAddress>
-
If reconfiguring an existing SNIP address:
- **set ns ip** <IPAddress>@ <netmask> -**type SNIP** - **networkroute** ( **ENABLED** | **DISABLED** ) -**tag** <positive_integer>
- show ns ip <IPAddress>
To configure the network route and tag parameters of a SNIP address by using GUI:
- Navigate to System> Network > IPs > IPV4s.
- Set the Network Route and Tag parameters while adding a Subnet IP (SNIP) address or modifying an existing Subnet IP address.
Advertise VIP Routes to Selective Areas
To configure the host route and tag parameters of a VIP address by using the CLI:
At the command prompt, type one of the following sets of commands.
-
If adding a new VIP address:
- **add ns ip** <IPAddress>@ <netmask> -**type VIP** -**hostRoute** ( **ENABLED** | **DISABLED** ) -**tag** <positive_integer>
- show ns ip <IPAddress>
-
If reconfiguring an existing VIP address:
- **set ns ip** <IPAddress>@ <netmask> -**type VIP** -**hostRoute** ( **ENABLED** | **DISABLED** ) -**tag** <positive_integer>
- show ns ip <IPAddress>
To configure the network route and tag parameters of a VIP address by using the GUI:
- Navigate to System > Network > IPs > IPV4s.
- Set the Host Route and Tag parameters while adding a VIP address or modifying an existing VIP address.
Share
Share
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.