Thank Muthukumar Shunmugiah to help set up this blog
We often get questions about management HA traffic between pairs. cameras and sometimes it can be confusing. This blog covers some key points that should help in the HA deployments of various types.
- To understand the reasons for HA failover please check the following link
- http://edocssand.citrix.com/proddocs/topic/ns-system-10 -map / ns failover-con.html -nw-ha-undrstndg-causes
- Only NSIP is used to send traffic hA
- UDP ports 3003 and 3010 are used to hA communication
- default traffic HA is sent untagged
- to send the marked HA traffic - NSVLAN or tagall option can be used
- Heartbeats are sent to all interfaces on which the peer can be reached NS / resolved
- There is no need to send Heartbeats on critical interfaces
- When traffic untagged HA is necessary:
- is NSVLAN not activated: traffic is sent to all interfaces on which the pair can be resolved
- NSVLAN is enabled without imprint traffic is sent only from these interfaces including native VLAN is NSVLAN
- on the unit that is connected to NetScaler
- If more interfaces are connected between NS and the connected device - interfaces on the connected device must not have the same native VLAN
- When the need is to send tagged traffic:
- Enable NSVLAN with marking: HA traffic is tagged with NSVLAN and is sent only from those whose VLAN interfaces native is NSVLAN
- tagall When tagall is enabled on the interface, the traffic is sent with the native VLAN tag of the interface
- on device connected to NetScaler
- VLAN Tagged should always be part of the allowed VLANs
- Even the native VLAN must be part of the allowed VLANs
0 Komentar