Viewing Topology
Click the Topology tab in the left frame to view the topology in the network.
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains the following sections:
Click the Topology tab in the left frame to view the topology in the network.
When you click Port Definition tab in the GUI, the Port Definition screen is displayed. Select the switch from the drop-down list to configure the ports.
On the Port Definition screen, the following two tabs are displayed:
Port Configuration
SPAN Destination
Click the Port Configuration tab, the following tabs are displayed:
Configure Multiple Ports
Remove port Configuration
Add Service Node
Add Monitoring Device
When you click Configure Multiple Ports tab, the Configure Multiple Ports window is displayed. The following details are displayed on the screen: Number, Status, Port Name, Type, In Use, Port ID, and Action.
Note |
Beginning with Cisco Nexus Data Broker, Release 3.1, the interface description is updated from the Cisco Nexus Data Broker GUI to the switch and the interface description is also available from the switch into the Cisco Nexus Data Broker GUI. When using in Openflow mode, the NX-API auxiliary connection is required for this functionality to work. |
Note |
On the Port Configuration tab, the port name and the interface are displayed as hyperlinks. When you click the port name, you can view the running configuration for that interface on the tab. |
If you want to remove any ports, select the port and click Remove port Configuration tab.
Click Add Service Node to add a service node.
Click Add Monitoring Device to add a monitoring device.
On the Port Configuration screen, the following port details are displayed for the selected node:
Serial Number
Status
Port name
Type
In Use
Port ID
Action—When you click Configure, the Configure Ports window is displayed.
On the SPAN Destination tab, the following details are displayed:
SPAN Destination Name
SPAN Destinations
Node Connector
Monitor Port Type
Description
Step 1 |
Select the switch for which you want to configure the port details on the Port Configuration screen. |
||||||||||
Step 2 |
Click Configure under Action. The Configure Ports window is displayed. |
||||||||||
Step 3 |
In the Configure Ports window, configure the port type from the Select a port type drop-down list by selecting one of the following options:
Monitoring Device—Creates a monitoring device for capturing traffic and configures the corresponding delivery port. Edge Port-SPAN—Creates an edge port for incoming traffic connected to an upstream switch that is configured as a SPAN destination. Edge Port-TAP—Creates an edge port for incoming traffic connected to a physical TAP port. Production Port—Creates a production port for the ingress and egress traffic.
When you select the port type, the title of the window changes to Manage Configure Ports. |
||||||||||
Step 4 |
(Optional) In the Port Description field, enter the port description. Beginning with Cisco Nexus Data Broker, Release 3.1, the interface description is updated from the Cisco Nexus Data Broker GUI to the switch and the interface description is also available from the switch into the Cisco Nexus Data Broker GUI. When using in Openflow mode, the NX-API auxiliary connection is required for this functionality to work. |
||||||||||
Step 5 |
Enter VLAN ID for the port. The port is configured as dot1q to preserve any production VLAN information. The VLAN ID is used to identify the port that the traffic is coming from. |
||||||||||
Step 6 |
(Optional) If APIC is available, you can select the ACI side port and designate it as the SPAN destination port. |
||||||||||
Step 7 |
In the Enable Packet Truncation field, enter the packet length. |
||||||||||
Step 8 |
A check box is added for Block Tx and it is applicable only for Edge-SPAN where you can block the traffic that is being transmitted out of Edge-SPAN interface. |
||||||||||
Step 9 |
Click Submit to save the settings or click Clear to clear the details. Once you configure a port, you can click Edit under Action on the Port Configuration screen to edit the port details. You can click Remove under Action on the Port Configuration screen to clear the port details. |
Starting with NDB Release 3.4, you can edit the select fields under Port configuration(Edge-Span, Edge-Tap or Production) while in use. Ports can be edited in all the modes of connection. The following table lists the fields that you can edit for port in use.:
Section |
Field |
Editable |
---|---|---|
Port Configuration |
Port Description |
Yes |
Block Tx |
Yes |
|
Port Type |
No |
|
VLAN Packet Truncation |
No |
|
Drop ICMPv6 Neighbour Solicitation |
Yes |
|
Enable Timestamp Taggin |
Yes |
Step 1 |
Select the switch for which you want to configure the port details on the Port Configuration screen. |
||
Step 2 |
Click Enable/Disable to enable or disable the selected port.
|
When you configure a port as an edge SPAN port and the port is connected to the API side, you can select the pod, node, and port from the ACI side and set the port as SPAN destination.
Note |
You can add SPAN destination only after APIC has been successfully added to the network. |
Step 1 |
Select the switch for which you want to configure the port details on the Port Configuration screen. |
Step 2 |
Click Configure under Action. The Configure Ports window is displayed. |
Step 3 |
In the Configure Ports window, configure the port type from the Select a port type drop-down list by selecting one of the following options:
Monitoring Device—Creates a monitoring device for capturing traffic and configures the corresponding delivery port. Edge Port-SPAN—Creates an edge port for incoming traffic connected to an upstream switch that is configured as a SPAN destination. Edge Port-TAP—Creates an edge port for incoming traffic connected to a physical TAP port. Production Port—Creates a production port for the ingress and egress traffic. When you select the port type, the title of the window changes to Manage Configure Ports. |
Step 4 |
In the SPAN DESTINATION pane, select the pod from the Pod drop-down list. |
Step 5 |
Select the ACI leaf from the Leaf drop-down list. |
Step 6 |
Select the port from the ACI side from the Port drop-down list and set the interface as SPAN destination. |
Step 7 |
Click Submit to save the settings. The port is now configured as SPAN destination part and it is displayed on the Port Definition screen. |
You can configure multiple ports for a node.
Step 1 |
Click Configure Multiple Ports on the Port Configuration screen. The Configure Multiple Ports window is displayed. |
Step 2 |
Use CTRL/SHIFT to select multiple ports in the Select Ports field. |
Step 3 |
Select port type from the drop-down list in the Select Port Type field. |
Step 4 |
Click Submit to save the settings. |
You can create a port group and add the ports to the connection.
Note |
Starting with Cisco Nexus Data Broker, Release 3.2, you can create port groups for different source ports. The port groups can be a combination of the edge-span and the edge-tap ports across different switches. You can select ports, define port groups, provide a name to the port group, select the port group in a connection screen (only one port group per connection), and use the ports defined in the port group as source ports for creating a connection. Selecting individual ports is disabled when using a port group. You cannot edit the port group even if it is part of a connection. The connection is automatically updated with the new port group. Deleting a port group is not allowed when the port group is in use. |
Complete the following steps to configure port groups:
Step 1 |
Select the switch for which you want to configure the port details on the Port Configuration screen. |
Step 2 |
Click Port Groups tab in the left frame. |
Step 3 |
Click + Add Group to create a port group. |
Step 4 |
In the Create Port Group window, enter the group name in the Group Name field. |
Step 5 |
In the Select Node field, select a node, for example, N9K-116. |
Step 6 |
In the Select Port field, select a port, for example, Ethernet1/1 (Ethernet1/1). You can add only edge-span and edge-tap ports and you cannot add production ports to the port groups. |
Step 7 |
Click + Add To Group to add the port to the group. You can add multiple ports to the group. |
Step 8 |
Click Apply. The port group is displayed on the Port Groups screen with the following information for the group, for example, Name, Connection Name, Ports and Action. |
Starting with NDB 3.4 release, you can edit the port groups that are currently in use in a connection. This feature is supported on the switches running in NX-API, OpenFlow, or NX-AUX mode.
Step 1 |
Select the switch for which you want to configure the port details on the Port Group pane. |
Step 2 |
Click Edit on the listed table row. |
The following table lists the fields that you can edit for a Port Group that is currently in use:
Section |
Field |
Editable |
---|---|---|
Port Group |
Port Description |
Yes |
Port |
Yes |
|
Port Name |
Yes (If the port is not part of an active connection) |
|
Port Group |
Yes (If the port group is not part of an active connection) |
To add a new monitoring device, complete these steps:
Step 1 |
Navigate to the Monitoring Device tab under Configuration. |
||||||||||||||||
Step 2 |
Click Add Monitoring Device. |
||||||||||||||||
Step 3 |
In the Monitoring Device window, complete the following fields:
|
||||||||||||||||
Step 4 |
Click Submit to create the monitoring device. |
Starting with Cisco NDB, Release 3.4, you can edit a monitoring device configuration using the NDB GUI. Support to edit description of a Monitoring device is available for NX-API, OpenFlow, and NX-AUX based switches. For the OpenFlow devices, the updated descriptions are synchronized to NDB User Interface (UI) only. For NX-API and NX-AUX devices, the updates are synchronized to NDB UI and the switch interface.
The following table lists the fields that you can configure for Monitoring Devices:
Section |
Field |
Editable |
---|---|---|
Monitor Devices |
Monitor Devices Name |
Yes (If the monitoring device is not in use) |
Port Description |
Yes |
|
Block Rx |
Yes |
|
Icons |
Yes |
|
Enable Timestamp Tagging |
Yes |
Step 1 |
Navigate to the Service Nodes tab under Configuration and click + Service Node. |
Step 2 |
In the Add Service Node window, enter the name of the service node. |
Step 3 |
Select the ingress port for the service node from the Service Node Ingress Port drop-down list. |
Step 4 |
Select the egress port for the service node from the Service Node Egress Port drop-down list. |
Step 5 |
Enable health check on a service node by selecting the Service Node Health Check option. Beginning with Cisco Nexus Data Broker, Release 3.2, you can configure the wait interval in the config.ini file before the health check is up. The ServiceNodeHealthCheckWaitInterval is the variable in the config.ini file to set the wait interval. If you do not specify a value or if the value is 0 for the wait interval in the config.ini file, the default value of 5 Seconds is used. The wait interval is not applicable if the port is in shutdown state. This option works only in the 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. |
Step 6 |
Select a service node icon from the available options. |
Step 7 |
Click Save. |
Starting with Cisco NDB, Release 3.4, you can now edit and configure Service Node fields using the NDB GUI. For the OpenFlow devices, the updated descriptions are synchronized to NDB User Interface (UI) only. For NX-API and NX-AUX devices, the updates are synchronized to NDB UI and the switch interface.
The following table lists the fields that you can configure for an active Service Node:
Section |
Field |
Editable |
---|---|---|
Service Node |
Description |
Yes |
Icon |
Yes |
|
Service Node Health Check |
Yes |
|
Service Node Name |
Yes (If the service node is not in use) |
|
Service Node Ingress Port |
No |
|
Service Node Egress Port |
No |
|
Ingress port Description |
Yes |
|
Egress port Description |
Yes |
Note |
UDF is supported on Cisco Nexus 9000 Series switches in NXAPI mode with NXOS version higher than Release 7.0(3)I5(2). |
Note |
You can configure a maximum of four UDF for a Cisco Nexus 9000 Series switch. For 9200 and 9300-EX series switches, you can configure a maximum of two UDFs. |
To use UDF to manage traffic, you need to:
Define a UDF, see Define a UDF.
Create a filter using the UDF, see Adding a Filter.
Apply the filter (configured with UDF) to a connection to manage traffic, see Adding a Connection.
Complete the following steps to define a UDF:
Command or Action | Purpose | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Step 1 |
Log into NDB application. |
|||||||||||
Step 2 |
Navigate to Configuration tab, click UDF Definition to define a user defined filter. The UDF Definition window is displayed. |
|||||||||||
Step 3 |
In the UDF Definition window, complete the following fields: |
|
||||||||||
Step 4 |
Click Add UDF. The newly added UDF appears in the UDF Definition window. |
|
IPv4
IPv6
ARP
MPLS Unicast
MPLS Multicast
MAC
Note |
The hardware command that is a pre-requisite for the IPv6 feature is hardware access-list tcam region ipv6-ifacl 512 double-wide . |
Step 1 |
On the Filters tab, click Add Filter to add a filter. The Add Filter window is displayed. |
||||||||||||||||||||||
Step 2 |
In the Filter Description section of the Add Filter window, complete the following fields:
|
||||||||||||||||||||||
Step 3 |
In the Layer 2 section of the Add Filter window, complete the following fields:
|
||||||||||||||||||||||
Step 4 |
In the Layer 3 section of the Add Filter window, update the following fields:
|
||||||||||||||||||||||
Step 5 |
In the Layer 4 section of the Add Filter dialog box, complete the following fields:
|
||||||||||||||||||||||
Step 6 |
In the Layer 7 section of the Add Filter dialog box, complete the following fields:
|
||||||||||||||||||||||
Step 7 |
Click Add Filter. |
Starting with Cisco Nexus Data Broker, Release 3.3, advanced filtering option is available to manage the traffic. Advanced filtering provides multiple options to filter (permit or deny) the traffic based on Ethernet type and attributes such as Acknowledgment, FIN, Fragments , PSH, RST, SYN, DSCP, Precedence, TTL, packet-length, and NVE. Advanced filtering is available for the following Ethernet types and options:
Data Type |
Supported Options |
---|---|
IPv4 |
DSCP, Fragment, Precendence, and TTL |
IPv4 with TCP |
Acknowledgment, DSCP, Fragment, FIN, Precedence, PSH, RST, SYN, and TTL |
IPv4 with UDP |
DSCP, Fragment, Precendence, and TTL |
IPv6 |
DSCP and Fragment |
IPv6 with TCP |
Acknowledgment, DSCP, Fragment, FIN, PSH, RST, and SYN |
IPv6 with UDP |
DSCP and Fragment |
Important |
Advanced Filtering is available only for NX-API on Cisco Nexus 9000 platform. |
Important |
|
Configure DSCP and Precedence together in advance filtering.
Configure fragments and ACK or SYN or FIN or PSH or RST together in advance filtering.
Configure fragments and port numbers with UDP and IPv4 or IPv6 Combination
Configure Precedence and HTTP Methods with IPv4 and TCP Combination.
Add a filter to be assigned to the connection.
Configure a monitoring device (optional).
Configure an edge port or multiple edge ports (optional).
Step 1 |
On the Connections tab, click + Connection. The Add Connections window is displayed. |
||||||||||||||||||||||
Step 2 |
In the Add Connections window, you can add the Connection Name and the Priority of the connection in the Connection Details area:
|
||||||||||||||||||||||
Step 3 |
In the Allow Matching Traffic area, modify the following fields:
|
||||||||||||||||||||||
Step 4 |
In the Drop Matching Traffic area, complete the following fields:
|
||||||||||||||||||||||
Step 5 |
In the Source Ports (Optional) area, complete the following fields:
|
||||||||||||||||||||||
Step 6 |
Do one of the following:
The following fields are displayed on the Connection Setup screen:
|
Note |
Beginning with Cisco Nexus Data Broker, Release 3.2, if you have added two or more interfaces (source ports) using the Connections tab, two interfaces (source ports) are displayed by default. If you have more than two interfaces (source ports) in the Connections tab, you can expand or collapse the source ports by using more... or less... options that are provided in the GUI. |
Click i Search Connections tab in the Connections screen to search for the connections using the keywords, Success, Installing, Creating, Partial, and Failed.
Beginning with Cisco Nexus Data Broker, Release 3.3, you can now add a new connection with AutoPriority. This functionality provides the flexibility to group multiple destination devices and filters in a connection. The priority of a connection with Auto-Priority is set to the value configured in config.ini file. You can configure the connection.autopriority.priorityValue attribute in the config.ini file with a priority value to be used for all the new connections with auto-priority. The connection information lists the allowed filters along with the destination devices.
Follow these restrictions and usage guidelines for creating a connection with auto-priority:
ACL Overlapping is not supported for the filters of the same protocol type (different IP address and Ports) assigned to different destination devices, because only the filters are prioritized.
To add a new connection with AutoPriority across devices (with multiple hops), the QinQ VLAN configuration is required.
You can configure only one connection with Auto-Priority mode for each source port/port group.
Connection with AutoPriority is a BETA release.
To add a new connection with Auto-Priority, complete these steps:
Ensure that you have configured the monitoring device, destination device, and filters before adding a new connection.
Command or Action | Purpose | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Step 1 |
Log into the NDB application. |
|||||||||||||||||||||
Step 2 |
Navigate to Configuration -> Connection, and click New Connection with AutoPriority (Beta) to add a new connection. The New Connection with AutoPriority (Beta) window is displayed. |
|||||||||||||||||||||
Step 3 |
In the New Connection with AutoPriority (Beta) window, complete the following fields: |
|
Note |
The redirection setup feature is supported on Cisco Nexus 3000 Series and Cisco Nexus 9300 switches with Release 7.x. Cisco Nexus Data Broker lets you configure redirection policies that match specific traffic, redirecting it through multiple security tools before it enters or exits your data center using redirection. |
Add a filter to be assigned to the redirection.
Configure a monitoring device (optional).
Configure an edge port or multiple edge ports (optional).
The production ingress port, the production egress port, and the service node should be on the same redirection switch.
Step 1 |
On the Redirections tab, click + Redirection. The Add Redirection window is displayed. |
||||||||||||||||
Step 2 |
In the Add Redirection window, you can add the Redirection Name and the Priority of the redirection in the Redirection Details area:
|
||||||||||||||||
Step 3 |
In the Matching Traffic area, modify the following fields:
|
||||||||||||||||
Step 4 |
In the Redirection Switch area, modify the following fields:
|
||||||||||||||||
Step 5 |
In the Service Nodes (OPTIONAL) area, complete the following fields:
|
||||||||||||||||
Step 6 |
Select the Reverse ServiceNode Direction option to enable reverse direction on the service node. 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. |
||||||||||||||||
Step 7 |
In the Production Ports area, complete the following fields:
|
||||||||||||||||
Step 8 |
In the Delievery Devices to copy traffic (OPTIONAL) area, complete the following fields:
|
||||||||||||||||
Step 9 |
Do one of the following:
|
||||||||||||||||
Step 10 |
When you click Install Redirection to save the redirection and install it at the same time, the redirection path on the redirection switch is displayed on the production ingress ports, service nodes, and the production egress ports. |
||||||||||||||||
Step 11 |
Click Flow Statistics to view the flow statistics for the redirection switch. The following fields provide information on the flow statistics:
|
||||||||||||||||
Step 12 |
Click Close to close the flow statistics display window. |
View the flow and port statistics for the switches on the Statistics tab.
Note |
When you select a switch on the statistics page, the Auto Refresh tab for the switch is ON by default. Click Auto Refresh: Off to disable auto refresh on the Statistics tab. The screen is refreshed every 30 seconds and the updated statistics for the switch are displayed on the screen. |
Step 1 |
Navigate to the Statistics tab under Configuration and click a node from the drop-down list to check and view the flow and port statistics of that node. 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:
|
||
Step 2 |
Click the Ports tab to check the ports statistics. You can view the ports statistics as displayed in the following fields.
|
Starting with Cisco NDB Release 3.4, port statistics are shown along with the connection path information in the NDB GUI. This feature is supported for Nexus 9K and Nexus 3K Series switches based on NX-API, OpenFlow, and NX-AUX mode.
To view the port statistics for a connection, complete the following steps:
Step 1 |
Navigate to CONFIGURATION -> Connections . |
Step 2 |
On the Connection page, click a connection name for which you want to view the port statistics. |
Step 3 |
Click Port Statistics to open the Flow Statistics page. |
Step 4 |
Click Port tab to view the port statistics for the selected connection. |
Starting with Cisco NDB release 3.4, you can now clear port and flow statistics using the NDB GUI. You can either clear all the port related statistics for a switch or clear statistics for a specific port on the switch. For This feature is currently available only for NXAPI based Nexus 9K and Nexus 3K switches.
To clear flow statistics, complete the following steps:
Step 1 |
Navigate to the CONFIGURATION → Statistics and click the Flows tab to clear flow statistic. Click Delete ALL to clear all the flow statistics such as byte count and packet count for the switch. |
Step 2 |
Click the Ports tab to clear port statistics.
|
Starting with Cisco NDB release 3.6, you can now remove and purge all the configuration information (such as connection and redirection) associated with a device that has been removed from the NDB.
To remove device configuration, complete the following steps:
Step 1 |
Navigate to the . |
Step 2 |
Select the devices for which you want to remove all the configuration information and click Remove devices . All the configurations associated with the removed device will be deleted from NDB database. |
On the SPAN Sessions tab, the following fields are displayed:
SPAN Session
Filter
Devices
SPAN Source
SPAN Destination
You can add a SPAN session in ACI.
Step 1 |
Click + SPAN Session to add a SPAN session. The Add SPAN Session window is displayed. |
||
Step 2 |
In the Add SPAN Session window, add a session name in the SPAN Session Name field. |
||
Step 3 |
(Optional) Select a connection in the Select Connections field. |
||
Step 4 |
In the Action pane, select a priority for the SPAN session. |
||
Step 5 |
Select a rule using the drop-down list in the Rule Filter field. You can select the default filter rule, Default-Match-IP or select another filter from the drop-down list. The available filter rules are Default-Match-IP, Match-HTTP, Match-vlan, and Default-Match-all. |
||
Step 6 |
Select a destination device to which the traffic is sent. |
||
Step 7 |
In the SPAN SOURCES pane, select the device type as ACI or NXOS in the Select Device Type field. When you select ACI device and click +Add SPAN Source, the Add Leaf Ports or +Add EPG tabs are displayed. |
||
Step 8 |
In the SPAN SOURCES pane, when you select the device type as NXOS in the Select Device Type field and click +Add SPAN Source, the Add Interface or Add VLAN tabs are displayed. This field allows to add NXOS SPAN session via NXAPI. It allows to add 2 types of SPAN sources. If you need to add interface as source, click + ADD SPAN Source and click Interface. If you need to allow traffic of a particular VLAN, click VLAN.
|
||
Step 9 |
When you click +Add Interface, the Add Production Switch Interface window is displayed. You can select a node, select an interface, and click Submit. |
||
Step 10 |
When you click +Add VLAN, the Add Production Switch VLAN window is displayed. You can select a node, enter a VLAN, and click Submit. |
||
Step 11 |
In the SPAN Destination field, you can select the SPAN destination. This field displays SPAN destination for ACI in the ACI SPAN session or SPAN destination for NXOS in the NXOS SPAN session.
|
||
Step 12 |
Click Add SPAN Session. 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. |
||
Step 13 |
Click OK. 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. |
Starting with Cisco Nexus Data Broker,Release 3.4, you can now export and import the device configuration in JSON file format.The configuration file includes information about connected as well as disconnected devices with configuration information such as filters, ports, connections, and redirections.
Complete the following steps to export a configuration from NDB:
Command or Action | Purpose | |
---|---|---|
Step 1 |
Log into the NDB application. |
|
Step 2 |
Navigate to Administration -> System -> Configuration, and click Export tab. |
|
Step 3 |
Select a device for exporting the configuration from the Configuration Pane. |
|
Step 4 |
(Optional) Select Include Connections check box to include connection information such as filters, connections, service nodes, and redirections. |
|
Step 5 |
Click Generate new Configuration. |
|
Step 6 |
Click Save to save the configuration. |
Complete the following steps to import a configuration into NDB:
Command or Action | Purpose | |
---|---|---|
Step 1 |
Log into the NDB application. |
|
Step 2 |
Navigate to Administration -> System -> Configuration, and click Import tab. |
|
Step 3 |
Click Choose Configuration, the File Upload dialog box appears. |
|
Step 4 |
Select a configuration and click Open. The selected configuration appears in the Configuration Pane. |
|
Step 5 |
Select a configuration from the Configuration Pane. |
|
Step 6 |
(Optional) Select Include Connections check box to include connection information such as filters, connections, service nodes, and redirections. |
|
Step 7 |
Click Apply to apply the configuration to NDB. |
Starting with Cisco NDB Release 3.4, you can now manage the Sampled Flow (sFlow) on NDB switches that are based on NX-API. This feature is currently not available for OpenFlow and NX-AUX based switches. sFlow allows you to monitor real-time traffic in data networks that contain switches and routers. It uses the sampling mechanism in the sFlow agent software on switches and routers to monitor traffic and to forward the sample data to the central data collector.
To enable sFlow on a port, complete the following steps:
Step 1 |
Log into the NDB GUI. |
||||||||||||||||||||||
Step 2 |
Navigate to CONFIGURATION -> Port Definition tab. |
||||||||||||||||||||||
Step 3 |
Click Configure Node to open the Node Configuration pane. The Node Configuration window is displayed. |
||||||||||||||||||||||
Step 4 |
Click Configure sFlow to open the Configure sFlow pane. |
||||||||||||||||||||||
Step 5 |
Select Enable sFlow from the Enable/Disable sFlow drop-down list to open the Confiigure sFlow pane. |
||||||||||||||||||||||
Step 6 |
In the Confiigure sFlow pane, enter the following details and click Submit.
|
Add device to Cisco Nexus Data Broker using NX-API.
Step 1 |
In the topology diagram, click the node for which you wish to configure MPLS tag stripping. |
Step 2 |
In the Port Configuration window, click Configure Node. The Node Configuration window is displayed. |
Step 3 |
In the Symmetric Load Balancing on Port Channel drop-down list, select the Hashing Option. |
Step 4 |
In the MPLS Strip Configuration drop-down list, choose one of the following:
|
Step 5 |
When you select Enable MPLS Strip option, the Label Age field is displayed. In the field, enter a value for the MPLS strip label age. The range for MPLS strip label age configuration is 61-31622400. |
Step 6 |
Click Submit. |
The following table lists the symmetric and non-symmetric load balancing options:
Configuration type |
Hashing Configuration |
Platforms |
Options |
---|---|---|---|
Symmetric |
SOURCE_DESTINATION |
N9K*, N3K-C3164XXX, N3K-C32XXX |
IP, IP-GRE, IP-L4PORT, IP-L4PORT-VLAN, IP-VLAN, L4PORT, MAC |
Rest |
IP, IP-GRE, PORT, MAC, IP-ONLY, PORT-ONLY |
||
Non-symmetric |
SOURCE DESTINATION |
N9K*, N3K-C3164XXX, N3K-C32XXX |
IP, IP-GRE, IP-L4PORT, IP-L4PORT-VLAN, IP-VLAN, L4PORT, MAC |
Rest |
IP, IP-GRE, PORT, MAC |
Starting with Cisco NDB Release 3.4, you can configure PTP Timestamping feature using the NDB GUI. PTP is a time synchronization protocol for nodes distributed across a network. Its hardware timestamp feature provides greater accuracy than other time synchronization protocols such as Network Time Protocol (NTP).
A PTP system can consist of a combination of PTP and non-PTP devices. PTP devices include ordinary clocks, boundary clocks, and transparent clocks. Non-PTP devices include ordinary network switches, routers, and other infrastructure devices.
PTP is a distributed protocol that specifies how real-time PTP clocks in the system synchronize with each other. These clocks are organized into a master-member synchronization hierarchy with the grandmaster clock, the clock at the top of the hierarchy, determining the reference time for the entire system. Synchronization is achieved by exchanging PTP timing messages, with the members using the timing information to adjust their clocks to the time of their master in the hierarchy. PTP operates within a logical scope called a PTP domain.
Note |
For Cisco NDB 3.4 release and later, PTP Time-stamping feature is supported on the Cisco Nexus 93XXX-EX and 92XX Series switches. |
Note |
You need to enable PTP for all the devices in the network to ensure PTP clock time synchronization. |
Note |
After PTP is configured. the default PTP configuration is synchronized with all the ISL ports of the corresponding device. |
To configure PTP using NDB GUI, complete these steps:
Step 1 |
Log into Cisco NDB GUI. |
Step 2 |
Navigate to CONFIGURATION -> Port Definition tab. |
Step 3 |
Click Configure Node to open the Node Configuration pane. |
Step 4 |
Click Configure PTP to open the Configure PTP pane. |
Step 5 |
Select Enable PTP from the Enable/Disable PTP drop-down list. |
Step 6 |
Enter the PTP source IP address in the Source IP Address text field. |
Step 7 |
Select the interfaces on which you want to enable PTP from the Select Port(s) list. |
Step 8 |
Click Submit to enable PTP on the selected interfaces. |
Starting with Cisco NDB Release 3.5, you can configure packet truncation on egress ports for Cisco Nexus 9300 FX and EX series switches. Packet truncation involves discarding bytes from a packet starting at a specified byte position. All the data after the specified byte position is discarded. Packet truncation is required when the main information of interest is in the header of a packet or in the initial part of the packet.
Note |
You can configure a maximum of four monitoring devices with packet truncation on a switch. |
To configure packet truncation on a device, you need to:
To configure a packet truncation interface, complete these steps:
Step 1 |
Log into NDB. |
||
Step 2 |
Navigate to the and select the switch for which you plan to configure packet truncation. |
||
Step 3 |
Click PORT CONFIGURATION tab. |
||
Step 4 |
Click Configure for the interface selected for configuration. |
||
Step 5 |
In the Configure Ports pane, click Select a port type and then click Packet Truncation Port. |
||
Step 6 |
(Optional) Enter description for the port in the Port Description text field. |
||
Step 7 |
Click Submit to create a packet truncation port. By default a packet truncation port is blocked for ingress traffic.
|
After the packet truncation port is created, you need to create a monitoring device with the packet truncation port. For more information, see Define a Monitoring Device with Packet Truncation Interface section.
Complete the following steps to define a monitoring device with a packet truncation interface:
Step 1 |
Navigate to the and select the switch for which you plan to configure packet truncation. |
||||||||||
Step 2 |
Click PORT CONFIGURATION tab. |
||||||||||
Step 3 |
Click Configure for the interface selected for configuration. |
||||||||||
Step 4 |
In the Configure Ports pane, click Add Monitoring Device. |
||||||||||
Step 5 |
In the Monitoring Device window, complete the following fields:
|
||||||||||
Step 6 |
Select Packet Truncation. |
||||||||||
Step 7 |
Enter maximum packet size in the MTU Size text field. The MTU size can be between 320 and 1518 bytes. |
||||||||||
Step 8 |
From the Select Packet Truncation Port drop-down list, select the packet truncation port you created on the same switch. |
||||||||||
Step 9 |
(Optional) Select device icon for the monitoring device. |
||||||||||
Step 10 |
Click Submit to create the monitoring device. |
Create a new connection using the monitoring device to implement the packet truncation feature. For more information, see Adding Connections.