This option works only in OpenFlow mode. The controller or the NDB injects a packet in the service node ingress port and the packet is received at the egress port. the packets are checked at the interval of every 5 seconds. If five packets are not received in 5 seconds, the health of the service node is considered as down.

For the service node, a new field is displayed in the details: Service Node Status. This field displays the status of the service node.

• Click Save Connection to save the connection, but not to install it until later.
• Click Install Connection to save the connection and install it at the same time.
• Click Close to exit the connection without saving it.

The following fields are displayed on the Connection Setup screen.

• Name

• Allow Filters

• Drop Filters

• Source Ports

• Devices

• Priority

• Last Modified By

• Description

When you enable this option and click Submit, the ingress and egress ports of the service node are swapped and reverse redirection is enabled on the service node. The option is also displayed as enabled in the Redirections tab.

• Click Save Redirection to save the redirection, but not to install it until later.
• Click Install Redirection to save the redirection and install it at the same time.
• Click Close to exit the redirection without saving it.

The following fields provide information on the flow statistics:

• In Port field—The Input port(s) from which the traffic is matched. An asterisk ("*") indicates any input port.

• DL Drc field—The source MAC address to be matched for the incoming traffic. An asterisk ("*") indicates any source MAC address.

• DL Dst field—The destination MAC address to be matched for the incoming traffic. An asterisk ("*") indicates any destination MAC address.

• DL Type field—The Ethertype to be matched for the incoming traffic. For example, "IPv4" or "IPv6" is used for all IP traffic types.

• DL VLAN field—The VLAN ID to be matched for the incoming traffic. An asterisk ("*") indicates any VLAN ID.

• VLAN PCP field—The VLAN priority to be matched for the incoming traffic. An asterisk ("*") is almost always displayed in this field.

• NW Src field—The IPv4 or IPv6 source address for the incoming traffic. An asterisk ("*") indicates any source address based on IPv4 or IPv6 Ethertypes.

• NW Dst field—The IPv4 or IPv6 destination address for the incoming traffic. An asterisk ("*") indicates any destination address based on IPv4 or IPv6 Ethertypes.

• NW Proto field—The network protocol to be matched for the incoming traffic. For example, "6" indicates the TCP protocol.

• TP Src field—The source port associated with the network protocol to be matched for the incoming traffic. An asterisk ("*") indicates any port value.

• TP Dst field—The destination port associated with the network protocol to be matched for the incoming traffic. An asterisk ("*") indicates any port value.

• Actions field—The output action to be performed for the traffic matching the criteria specified, for example, "OUTPUT = OF|2".

• Byte Count field—The aggregate traffic volume shown in bytes that match the specified flow connection.

• Packet Count field—The aggregate traffic volume shown in packets that match the specified flow connection.

• Duration Seconds field—The amount of time, in milliseconds, that the specific flow connection has been installed in the switch.

• Idle Timeout field—The amount of time, in milliseconds, that the flow can be idle before it is removed from the flow table.

• Priority field—The priority assigned to the flow. The flows with higher priority numbers take precedence.

You can also navigate to the statistics of another switch by selecting the switch in the drop down box.

You can view the flow statistics, for example:

• Flow Name

• In Port

• DL Source

• DL Destination

• DL Type

• DL VLAN

• VLAN PCP

• NW Source

• NW Destination

• NW Proto

• TP Source

• TP Destination

• AP HttpMd

• AP TcpOptLn

• Actions

• Byte Count

• Packet Count

• Duration Seconds

• Idle Timeout

• Priority

You can view the ports statistics as displayed in the following fields.

• Port Name

• Rx Packets

• Tx Packets

• Rx Bytes

• Tx Bytes

• Rx Rate (kbps)

• Tx rate (kbps)

• Rx Drops

• Tx Drops

• Rx Errors

• Tx Errors

• Rx Frame Errors

• Rx Overrun Errors

• Rx CRC Errors

• Collisions

The available filter rules are Default-Match-IP, Match-HTTP, Match-vlan, and Default-Match-all.

1. In the Add Leaf Ports window, select a pod using the drop-down list in the POD field.
2. Select a node using the drop-down list in the Node field.
3. Select a port using the drop-down list in the Port field.
4. Click Add Leaf Ports.
5. In the SPAN SOURCES pane, select a direction from the Incoming, Outgoing, or Both options.

   The selected Span source is displayed in the Span Source field.

6. If you select +Add EPG to add EPG source, select a tenant using the drop-down list in the Tenant field in the Add EPG window.

   Note	All EPG interfaces work only when all the ports are within the same leaf switch. If same EPG is across multiple switches, you have to select the leaf switch and the associated ports. One SPAN session needs to be setup for each leaf switch.

7. Select a profile using the drop-down list in the Profile field.
8. Select EPG associated with the tenant using the drop-down list in the EPG field.

   The selected SPAN Source is displayed.

9. Select Include All EPG Interfaces option.

   When you enable this option, the statically configured interfaces are added to the EPG.

   Note	This option can be used only when all EPG sources are within the same leaf switch.

   If the EPG is selected, by default, Cisco Nexus Data Broker listens for the changes in the statically configured interfaces of the selected EPG. If there is any change, it is applied to the SPAN session. The web socket connection is not secured with the certificates. To disable the event listening, add enableWebSocketHandle=false in the config.ini file under xnc/configuration folder.

10. Click Add EPG.

A message box is displayed asking you to confirm, Are you sure you want to add SPAN session?, if you want to add the SPAN session.

As a result, a SPAN session is set up in ACI. It also sets up a connection automatically on the Cisco Nexus Data Broker with the same SPAN session name and this connection redirects the traffic from that source port to the monitoring device.

You can set up additional SPAN sessions. You can append a new SPAN session to the existing connection. In that case, you can select the new SPAN session in the Add SPAN Session window, use the same connection that is previous ly created, select new SPAN sources from different leaf ports, select the SPAN destination, and add the SPAN session.

It creates a new session in ACI, but it appends an existing connection to include the new traffic on the Cisco Nexus Data Broker side.

You can edit or clone the existing SPAN sessions. If you want to remove a SPAN session, click the session and click Remove SPAN Session(s) A message box is displayed asking you to confirm, Remove the following sessions?, if you want to remove the displayed SPAN session. Click Remove SPAN Sessions to confirm. If the SPAN session is using an existing connection, the connection is updated automatically with the changes. If it is the last connection associated with the SPAN session, the connection is deleted.