Cisco Nexus 9000 Series Configuration Manual page 28

Configuring an ITD Service
Step 6
Step 7
Cisco Nexus 9000 Series NX-OS Intelligent Traffic Director Configuration Guide, Release 9.x
20
Command or Action
virtual [ip | ipv6] {ipv4-address
ipv4-network-mask | ipv6-address
ipv6-network-mask} [tcp | udp {port-number
| any}] [advertise {enable | disable} [active]]
Example:
switch(config-itd)# virtual ip
100.100.100.100 255.255.255.255 udp 443
advertise enable active
Example:
switch(config-itd)# virtual ipv6
100::100 128 udp 443
Enter one of the following commands to
determine how traffic is reassigned after a node
failure:
• [no] failaction node reassign
• [no] failaction node least-bucket
• [no] failaction bucket distribute
Example:
switch(config-itd)# failaction node
reassign
Example:
switch(config-itd)# failaction node
least-bucket
Example:
switch(config-itd)# failaction bucket
distribute
Purpose
• mask-position—Specifies the
load-balance mask position number. The
range is from 0 to 23.
Configures the virtual IPv4 or IPv6 address of
the ITD service.
The tcp and udp options specify that the
virtual IP address will accept flows from the
specified protocol. The port range is from 0 to
65535.
The advertise {enable | disable} [active]
option specifies whether the virtual IP route is
advertised to neighboring devices.
For IPv6 ITD, the advertise enable
Note
and the advertise enable active
options are available in the CLI but
they are not supported.
The failaction node reassign command
assigns failed node traffic to the first available
active node. When a node is down, the traffic
or bucket associated with the node is
reassigned to the first active node found in the
configured set of nodes. If the newly
reassigned node also fails, the traffic or bucket
is reassigned to the next available active node.
Once the failed node becomes active again,
traffic is diverted back to the new node, and
the node resumes serving the connections.
The failaction node least-bucket command
assigns the failed node buckets to the active
node with the least number of buckets after a
node failure. For multiple node failures, this
command determines the least-bucketed node
and assigns all of the buckets of the failed node
to the least-bucketed active node.
The failaction bucket distribute command
evenly distributes traffic across all available
nodes (rather than to just one active node) after
a node failure. This command detects failures
faster and reprograms TCAMs quicker than
the other failaction commands. This command
is not supported for standby nodes.
For IPv6 ITD, the failaction bucket
Note
distribute command is available in
CLI but it is not supported.
Configuring ITD