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)
此内容已动态机器翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
This content has been machine translated dynamically.
This content has been machine translated dynamically.
This content has been machine translated dynamically.
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.
这篇文章已经过机器翻译.放弃
Translation failed!
Routing in a cluster
Routing in a cluster works in much the same way as routing in a standalone system. A few points to note:
-
All routing configurations must be performed from the cluster IP address and the configurations are propagated to the other cluster nodes.
-
Routing runs only on spotted SNIP addresses and NSIP addresses.
-
Routes are limited to the maximum number of ECMP routes supported by the upstream router.
-
Node-specific routing configurations must be performed by using the owner-node argument as follows:
! interface vlan97 ! router ospf owner-node 0 ospf router-id 97.131.0.1 exit-owner-node owner-node 1 ospf router-id 97.131.0.2 exit-owner-node owner-node 2 ospf router-id 97.131.0.3 exit-owner-node redistribute kernel network 97.0.0.0/8 area 0 !
-
Retrieve node-specific routing configurations by specifying the node(s) in the owner-node argument as follows:
> vtysh ns# owner-node 0 1 ns(node-0 1)# show cluster state ns(node-0 1)# exit-owner-node
-
Clear node-specific routing configurations by specifying the node(s) in the owner-node argument as follows:
> vtysh ns# owner-node 0 1 ns(node-0 1)# clear config ns(node-0 1)# exit-owner-node
-
Routing protocol daemons can run and adjacencies can be formed on active and inactive nodes of a cluster.
-
Only active nodes advertise host routes to striped VIP addresses. Spotted VIP addresses are advertised by active owner node.
-
Active and inactive nodes can learn dynamic routes and install them into the routing table.
-
Routes learnt on a node are propagated to other nodes in the cluster only if route propagation is configured. This is mostly needed in asymmetric topologies where the unconnected nodes may not be able to form adjacencies.
ns(config)# ns route-install propagate
Note*
Make sure that route propagation is not configured in a symmetric cluster topology as it can result in making the node unavailable to the cluster.
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix 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 Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.