Enhanced Classic LAN, Release Release 12.2.1

First Hop Redundancy Protocol

Specifies the FHRP protocol. Options are:

Routing Protocol

Specifies the VRF-Lite Agg-Core/Edge or Collapsed Core-WAN peering protocol options. Options are:

BGP ASN

This field becomes editable if you selected ebgp in the Routing Protocol field.

Enter the BGP AS number the fabric is associated with. This must be same as existing fabric.

Enable Performance Monitoring

Check the check box to enable performance monitoring.

Ensure that you do not clear interface counters from the Command Line Interface of the switches. Clearing interface counters can cause the Performance Monitor to display incorrect data for traffic utilization. If you must clear the counters and the switch has both clear counters and clear counters snmp commands (not all switches have the clear counters snmp command), ensure that you run both the main and the SNMP commands simultaneously. For example, you must run the clear counters interface ethernet slot/port command followed by the clear counters interface ethernet slot/port snmp command. This can lead to a one time spike.

Spanning Tree Root Bridge Protocol

Specify the protocol to be used for configuring Root Bridge: Options are:

Spanning Tree settings and bridge configurations are applicable at the Aggregation layer only.

Spanning Tree VLAN Range

Specify the VLAN range. For example:

1, 3-5, 7, 9-11

The default value is 1-3967. Applicable only for Aggregation devices.

MST Instance Range

Specify the MST instance range. For example:

0-3,5,7-9

The default value is 0. Applicable only for Aggregation devices.

Spanning Tree Bridge Priority

Specify the bridge priority for the spanning tree in increments of 4096. Applicable only for Aggregation devices.

Spanning Tree Hello Interval

Set the number of seconds between the generation of config spanning-tree Bridge Protocol Data Unit (BPDU).

The default value is 2. Applicable only for Aggregation devices.

Spanning Tree Forward Delay

Set the number of seconds for the forward delay timer.

The default value is 15. Applicable only for Aggregation devices.

Spanning Tree Max Age Interval

Set the maximum number of seconds the information in a spanning-tree Bridge Protocol Data Unit (BPDU) is valid.

The default value is 20. Applicable only for Aggregation devices.

Spanning Tree Pathcost Method

Options are:

Applicable only for Aggregation devices.

vPC Auto Recovery Time

Specifies the vPC auto recovery time-out period in seconds.

vPC Delay Restore Time

Specifies the vPC delay restore period in seconds.

vPC Peer Link Port Channel ID

Specifies the Port Channel ID for a vPC Peer Link. Default value in this field is 500.

vPC IPv6 ND Synchronize

Enables IPv6 Neighbor Discovery synchronization between vPC switches. The check box is enabled by default. Uncheck the check box to disable the function.

vPC Domain Id Range

Specifies the vPC Domain Id range to use for new pairings.

vPC Layer-3 Peer-Router Option

Enables the Layer 3 device to form peering adjacency with both the peers.

Configure this command in both the peers. If you configure this command only on one of the peers or you disable it on one peer, the operational state of layer 3 peer-router gets disabled. You get a notification when there is a change in the operational state.

OSPF Process Tag

This field becomes editable if you selected ospf in the Routing Protocol field under the General Parameters tab.

The OSPF Routing Process Tag. Maximum size is 20.

OSPF Area ID

This field becomes editable in these conditions:

The OSPF Area ID in an IP address format.

OSPFv3 Process Tag

This field becomes editable if you selected ospf in the Routing Protocol field under the General Parameters tab.

The OSPFv3 Routing Process Tag. Maximum size is 20.

OSPFv3 Area ID

This field becomes editable in these conditions:

The OSPFv3 Area ID in an IP address format.

Enable BGP Authentication

This field becomes editable if you selected ebgp in the Routing Protocol field under the General Parameters tab.

Select the check box to enable BGP authentication. Deselect the check box to disable it. If you enable this field, the BGP Password Key Encryption Type and BGP Neighbor Password fields are enabled.

BGP Password Key Encryption Type

This field becomes editable in these conditions:

Choose the 3 for 3DES encryption type, or 7 for Cisco encryption type.

BGP Neighbor Password

This field becomes editable in these conditions:

Enter the VRF Lite BGP neighbor password as a hex string.

Enable OSPF Authentication

This field becomes editable if you selected ospf in the Routing Protocol field under the General Parameters tab.

Select the check box to enable OSPF authentication. Deselect the check box to disable it. If you enable this field, the OSPF Authentication Key ID and OSPF Authentication Key fields get enabled.

OSPF Authentication Key ID

This field becomes editable in these conditions:

The Key ID is populated.

OSPF Authentication Key

This field becomes editable in these conditions:

The OSPF authentication key must be the 3DES key from the switch. NOTE: Plain text passwords are not supported. Log in to the switch, retrieve the encrypted key and enter it in this field. Refer to the Retrieving the Authentication Key section for details.

VRF Template

Specifies the VRF template for creating VRFs. These are pre-built, best practice templates for VRFs that are provided with NDFC. You do not have to specify a template but one is automatically selected.

Network Template

Specifies the network template for creating networks. These are pre-built, best practice templates for networks that are provided with NDFC. You do not have to specify a template but one is automatically selected.

Layer 2 Host Interface MTU

Specifies the MTU for the layer 2 host interface. This value should be an even number.

Unshut Host Interfaces by Default

Check this check box to unshut the host interfaces by default.

Power Supply Mode

Choose the appropriate power supply mode.

CoPP Profile

Choose the appropriate Control Plane Policing (CoPP) profile policy for the fabric. By default, the strict option is populated.

Brownfield Network Name Format

Enter the format to be used to build the overlay network name during a brownfield import or migration. The network name should not contain any white spaces or special characters except underscore and hyphen. The network name must not be changed once the brownfield migration has been initiated. See the Creating Networks for the Standalone Fabric section for the naming convention of the network name.

The syntax is [<string> | VLAN_ID] and the default value is Auto_Net_VLANVLAN_ID. When you create networks, the name is generated according to the syntax you specify.

The following list describes the variables in the syntax:

An example overlay network name: Site_VLAN1234

Ignore this field for greenfield deployments.

Enable CDP for Bootstrapped Switch

Enables CDP on management (mgmt0) interface for bootstrapped switch. By default, for bootstrapped switches, CDP is disabled on the mgmt0 interface.

Enable Tenant DHCP

Check the check box to enable feature dhcp and associated configurations globally on all switches in the fabric. This is a pre-requisite for support of DHCP for overlay networks that are part of the tenant VRFs.

Ensure that Enable Tenant DHCP is enabled before enabling DHCP-related parameters in the overlay profiles.

Enable NX-API

Specifies enabling of NX-API on HTTPS.

NX-API HTTPS Port Number

Field becomes active if the Enable NX-API option is enabled.

Enter the NX-API HTTPS port number. Default value is 443.

Enable HTTP NX-API

Specifies enabling of NX-API on HTTP. Enable this check box and the Enable NX-API check box to use HTTP. This check box is checked by default. If you uncheck this check box, the applications that use NX-API and supported by Cisco Nexus Dashboard Fabric Controller, such as Endpoint Locator (EPL), Layer 4-Layer 7 services (L4-L7 services), VXLAN OAM, and so on, start using the HTTPS instead of HTTP.

If you check the Enable NX-API check box and the Enable NX-API on HTTP check box, applications use HTTP.

NX-API HTTP Port Number

Field becomes active if the Enable HTTP NX-API option is enabled.Enter the NX-API HTTPS port number. Default value is 80.

Enable Strict Config Compliance

Enable the Strict Config Compliance feature by selecting this check box. It enables bi-directional compliance checks to flag additional configs in the running config that are not in the intent/expected config. By default, this feature is disabled.

Enable AAA IP Authorization

Enables AAA IP authorization, when IP Authorization is enabled in the remote authentication server. This is required to support Nexus Dashboard Fabric Controller in scenarios where customers have strict control of which IP addresses can have access to the switches.

Enable NDFC as Trap Host

Select this check box to enable Nexus Dashboard Fabric Controller as an SNMP trap destination. Typically, for a native HA Nexus Dashboard Fabric Controller deployment, the eth1 VIP IP address will be configured as SNMP trap destination on the switches. By default, this check box is enabled.

Enable Agg/Access Auto Pairing

For back-to-back vPCs, enable this option to automatically pair aggregation and access devices based on topology.

Create Route-map fabric-rmap-redist-subnet

Enable this option to create a route map fabric-rmap-redist-subnet. This route-map matches tag 12345.

Greenfield Cleanup Option

Enable this field to clean the switch configuration without a reloads when PreserveConfig=no. Valid options are Enable or Disable.

Aggregation Freeform Config

Additional CLIs for all Aggregation devices as captured from show running configuration.

Access Freeform Config

Additional CLIs for all Access devices as captured from show running configuration.

Field

Description

Network VLAN Range

VLAN range for the per switch overlay network (min:2, max:4094).

Aggregation-Core/Aggregation-Edge Connectivity

Specify the option for the VRF Lite Aggregation-Core and Aggregation-Edge Router Inter-Fabric connection. Options are:

VRF-Lite Subinterface dot1q Range

Specifies the per Aggregation dot1q Range for VRF Lite connectivity (min:2, max:4093).

Auto Generate VRF Lite Configuration on Aggregation and Core/Edge

Option that controls the automatic generation of the VRF Lite sub-interface and peering configurations on the Aggregation & Core/Edge devices. When this option is enabled, the automatically created VRF Lite links will have the 'Auto Generate Flag' enabled.

VRF Lite IP Version

Select the IP version for VRF Lite.Options are:

IPv4 VRF Subnet IP Range and IPv4 VRF Subnet Mask Length

The IPv4 address range to assign peer-to-peer Aggregation-Core connections, and peering between vPC Aggregation switches.

Update the fields as needed. The values shown in your screen are automatically generated.

If you want to update the IP address ranges or the VRF/Network VLAN ranges, ensure that it does not overlap with other ranges. You should only update one range of values at a time. If you want to update more than one range of values, do it in separate instances. For example, if you want to update Layer 2 and Layer 3 ranges, you should do the following:

IPv6 VRF Subnet IP Range and IPv6 VRF Subnet Mask Length

The IPv6 address range to assign peer-to-peer Aggregation-Core connections, and peering between vPC Aggregation switches.

Update the fields as needed. The values shown in your screen are automatically generated. If you want to update the IP address ranges or the VRF/Network VLAN ranges, ensure that it does not overlap with other ranges. You should only update one range of values at a time. If you want to update more than one range of values, do it in separate instances. For example, if you want to update Layer 2 and Layer 3 ranges, you should do the following:

VRF Lite VLAN Range

VLAN range for Per VRF SVI Peering between Aggregation pairs (min:2, max:4094).

DNS Server IPs

Specifies the comma separated list of IP addresses (v4/v6) of the DNS servers.

DNS Server VRFs

Specifies one VRF for all DNS servers or a comma separated list of VRFs, one per DNS server.

NTP Server IPs

Specifies comma separated list of IP addresses (v4/v6) of the NTP server.

NTP Server VRFs

Specifies one VRF for all NTP servers or a comma separated list of VRFs, one per NTP server.

Syslog Server IPs

Specifies the comma separated list of IP addresses (v4/v6) IP address of the syslog servers, if used.

Syslog Server Severity

Specifies the comma separated list of syslog severity values, one per syslog server. The minimum value is 0 and the maximum value is 7. To specify a higher severity, enter a higher number.

Syslog Server VRFs

Specifies one VRF for all syslog servers or a comma separated list of VRFs, one per syslog server.

AAA Freeform Config

Specifies the AAA freeform configurations.

If AAA configurations are specified in the fabric settings, switch_freeform PTI with source as UNDERLAY_AAA and description as AAA Configurations will be created.

Banner

Specifies the message of the day banner.

Enable Bootstrap

Select this check box to enable the bootstrap feature. Bootstrap allows easy day-0 import and bring-up of new devices into an existing fabric. Bootstrap leverages the NX-OS POAP functionality.

To add more switches and for POAP capability, chose check box for Enable Bootstrap and Enable Local DHCP Server.

After you enable bootstrap, you can enable the DHCP server for automatic IP address assignment using one of the following methods:

Enable Local DHCP Server

Select this check box to initiate enabling of automatic IP address assignment through the local DHCP server. When you select this check box, the DHCP Scope Start Address and DHCP Scope End Address fields become editable.

If you do not select this check box, Nexus Dashboard Fabric Controller uses the remote or external DHCP server for automatic IP address assignment.

DHCP Version

Select DHCPv4 or DHCPv6 from this drop-down list. When you select DHCPv4, the Switch Mgmt IPv6 Subnet Prefix field is disabled. If you select DHCPv6, the Switch Mgmt IP Subnet Prefix is disabled.

Cisco Nexus 9000 and 3000 Series Switches support IPv6 POAP only when switches are either Layer-2 adjacent (eth1 or out-of-band subnet must be a /64) or they are L3 adjacent residing in some IPv6 /64 subnet. Subnet prefixes other than /64 are not supported.

DHCP Scope Start Address and DHCP Scope End Address

Specifies the first and last IP addresses of the IP address range to be used for the switch out of band POAP.

Switch Mgmt Default Gateway

Specifies the default gateway for the management VRF on the switch.

Switch Mgmt IP Subnet Prefix

Specifies the prefix for the Mgmt0 interface on the switch. The prefix should be between 8 and 30.

DHCP scope and management default gateway IP address specification: If you specify the management default gateway IP address 10.0.1.1 and subnet mask 24, ensure that the DHCP scope is within the specified subnet, between 10.0.1.2 and 10.0.1.254.

DHCPv4 Multi Subnet Scope

Specifies the field to enter one subnet scope per line. This field is editable after you check the Enable Local DHCP Server check box.The format of the scope should be defined as:

DHCP Scope Start Address, DHCP Scope End Address, Switch Management Default Gateway, Switch Management Subnet Prefix

For example: 10.6.0.2, 10.6.0.9, 10.6.0.1, 24

Enable AAA Config

Select this check box to include AAA configurations from the Manageability tab as part of the device start-up config post bootstrap.

Bootstrap Freeform Config

(Optional) Enter additional commands as needed. For example, if you require some additional configurations to be pushed to the device and be available post device bootstrap, they can be captured in this field, to save the desired intent. After the devices boot up, they will contain the configuration defined in the Bootstrap Freeform Config field.

Copy-paste the running-config to a freeform config field with correct indentation, as seen in the running configuration on the NX-OS switches. The freeform config must match the running config. For more information, see Enabling Freeform Configurations on Fabric Switches.

Hourly Fabric Backup

Select the check box to enable an hourly backup of fabric configurations and the intent. The hourly backups are triggered during the first 10 minutes of the hour.

Scheduled Fabric Backup

Check the check box to enable a daily backup. This backup tracks changes in running configurations on the fabric devices that are not tracked by configuration compliance.

Scheduled Time

Specify the scheduled backup time in a 24-hour format. This field is enabled if you check the Scheduled Fabric Backup check box.

Select both the check boxes to enable both back up processes. The backup process is initiated after you click Save.

The scheduled backups are triggered exactly at the time you specify with a delay of up to two minutes. The scheduled backups are triggered regardless of the configuration deployment status.

The number of fabric backups that will be retained on NDFC is decided by the Admin > System Settings > Server Settings > LAN Fabric > Maximum Backups per Fabric.

The number of archived files that can be retained is set in the # Number of archived files per device to be retained: field in the Server Properties window.

Note: To trigger an immediate backup, do the following:

You can also initiate the fabric backup in the fabric topology window. Click Backup Now in the Actions pane.

Enable Netflow

Check this check box to enable Netflow on Aggregation devices for this fabric. By default, Netflow is disabled. On Enable, NetFlow configuration will be applied to all Aggregation devices that support Netflow.

When Netflow is enabled on the fabric, you can choose not to have netflow on a particular switch by having a dummy no_netflow PTI.

If netflow is not enabled at the fabric level, an error message is generated when you enable netflow at the interface, network, or VRF level. For information about Netflow support for Cisco NDFC, see section "Netflow Support" in Understanding LAN Fabrics.