Chapter 1. New and Changed Information for this Release

New and Changed Information for this Release

Chapter 2. Overview

Network Device Management Tasks You Can Perform in Cisco UCS Director

Network Device Management Tasks You Cannot Perform in Cisco UCS Director

Orchestration Tasks for Network Device Management

Adding a Network Device Account

Collecting Inventory for a Network Device

Configuring the Polling Interval

Viewing Connectivity and Topology for Network Devices

Verifying Network Device Details in a Pod Environment

Chapter 3. Configuring Multiple Spanning Tree

About MST

Configuring an MST Instance

Enabling MST and Configuring MST Network Parameters

Chapter 4. Configuring Per VLAN Rapid Spanning Tree Plus

About PVST+

Configuring PVST+

Chapter 5. Configuring VLAN Trunking Protocol

About VTP

Configuring VTP

Chapter 6. Managing MAC Addresses

About MAC Addresses

Adding a MAC Address to a Switch

Removing a MAC Address from a Switch

Assigning MAC Address to a Port

Unassigning MAC Address from a Port

Configuring the Aging Time for the MAC Address Table

Chapter 7. Managing Virtual Device Contexts

About VDCs

Creating a VDC

Allocating a Port to a VDC

Removing a Port from a VDC

Removing a VDC

Chapter 8. Managing Ports

About Ports

Configuring a Port

Configuring an STP Port

Configuring a Port License

Managing Port Profiles

Creating a Port Profile

Managing Port Channels

Creating a Port Channel

Configuring a Private VLAN Port Profile

Chapter 9. Configuring SVI

About SVI

Configuring a SVI

Deleting a SVI

Chapter 10. Managing TrustSec

About Cisco Trustsec

Refreshing TrustSec

Chapter 11. Configuring SGT Exchange Protocol Connection

About SXP Connection

Configuring an SXP Peer Connection

Chapter 12. Configuring HSRP

About HSRP

Configuring HSRP

Chapter 13. Managing FC Alias

About FC Alias

Creating a FC Alias

Updating a FC Alias

Deleting a FC Alias

Chapter 14. Configuring Access Ports

About Access Ports

Configuring an Access Port

Chapter 15. Managing Access Control Lists

About Access Control Lists

Creating an ACL

Configuring Context ACL

Adding a MAC ACL Rule or an IP ACL Rule

Chapter 16. Configuring Network Address Translation

About NAT

Configuring NAT

Configuring Context NAT

Chapter 17. Configuring Quality of Services

About Quality of Service Policies

Configuring a QoS Policy

Deleting a QoS Policy

Chapter 18. Managing Service Policies

About Service Policies

Updating a Service Policy

Chapter 19. Managing Trunks

About Trunks

Configuring a Trunk

Updating a Trunk

Chapter 20. Managing Virtual Fibre Channels

About VFCs

Creating a VFC

Associating a VFC

Chapter 21. Managing VLANs

About VLANs

Creating a VLAN

Assigning a VLAN to a User Group

Unassigning a VLAN from a User Group

Configuring a Private VLAN Port

Creating a Private Primary and Secondary VLAN

Associating a Private Primary and Secondary VLAN

Disassociating a Private VLAN

Removing a Private VLAN Port

Deleting a Private VLAN

Deleting a VLAN

Chapter 22. Managing Virtual Port Channels

About vPCs

Configuring a vPC Domain

Configuring a vPC Port Channel

Removing a vPC

Chapter 23. Managing SAN Zones and SAN Zonesets

About SAN Zone and Zonesets

About Smart Zoning

Creating a SAN Zone

Enabling Smart Zoning

Adding a Member to a SAN Zone

Deleting a SAN Zone

Creating a SAN Zoneset

Adding a Member to a SAN Zoneset

Deleting a SAN Zoneset

Chapter 24. Managing Virtual Storage Area Networks

About VSANs

Creating a VSAN

Deleting a VSAN

Chapter 25. Managing Virtual Extensible LANs

About VXLANs

Creating a VXLAN

Encapsulating a VXLAN

Assigning a VXLAN to a Port Profile

Unassigning a VXLAN from a Port Profile

Removing a VXLAN

Chapter 26. Configuring ASA Context

About ASA Context

Creating an ASA Context

Chapter 27. Configuring the Cisco Nexus 1000V Switch for Microsoft Hyper-V

About Microsoft System Center Virtual Machine Manager

About the Cisco Nexus 1000V Switch for the Microsoft Hyper-V Configuration

Configuring the Cisco Nexus 1000V Switch for Microsoft Hyper-V

Managing Logical Networks

Creating a Logical Network

Managing Network Segment Pools

Creating a Network Segment Pool

Managing IP Pool Templates

Creating an IP Pool Template

Managing Network Segments

Creating a Network Segment

Managing Network Uplinks

Creating an Uplink Network

Managing VXLAN Range

Managing Tenant VRF

Chapter 28. Monitoring and Reporting

About General Reports

About Detail Reports

About Cisco ISE

About the Service Request Details Report

Exporting an Inventory Report

Chapter 29. Troubleshooting

Troubleshooting Cisco UCS Director Connectivity

Troubleshooting Cisco UCS Director Bare Metal Agent Connectivity

Preface

Audience

Conventions

Related Documentation

Documentation Feedback

Obtaining Documentation and Submitting a Service Request

Copyright Page

Chapter 1. New and Changed Information for this Release

- New and Changed Information for this Release

New and Changed Information for this Release

The following table provides an overview of the significant changes to this guide for this current release. The table does not provide an exhaustive list of all changes made to this guide or of all new features in this release.

New Features and Changed Behavior in Cisco UCS Director, Release 6.0

Feature

Description

Where Documented

Additional fields added to various configuration tasks

The following fields have been added to the Configure Trunk task: MTU and Port Channel.

The following fields have been added to the Configure vPC Domain task: Delay Restore, Peer Gateway, and Auto Recovery.

A "No Shutdown" check box has been added to the Create VLAN task.

A "Description" field has been added to the Access Configuration task.

Configuring a Trunk

Configuring a vPC Domain

Creating a VLAN

Configuring an Access Port

New workflow tasks

The following new workflow tasks have been added to the Task library in Cisco UCS Director :

- Adding Physical Network Account

- Push NTP Configuration

- Delete NTP Configuration

- Configure Host Name

- Delete Host Name

- Reset Password

- Create VRF

- Delete VRF

-

Chapter 2. Overview

This chapter contains the following sections:

- Network Device Management Tasks You Can Perform in Cisco UCS Director

- Network Device Management Tasks You Cannot Perform in Cisco UCS Director

- Orchestration Tasks for Network Device Management

- Adding a Network Device Account

- Collecting Inventory for a Network Device

- Configuring the Polling Interval

- Viewing Connectivity and Topology for Network Devices

- Verifying Network Device Details in a Pod Environment

Network Device Management Tasks You Can Perform in Cisco UCS Director

You can use Cisco UCS Director to perform management, monitoring, and reporting tasks for network devices within a domain.

Configuration and Administration

You can configure the following network device protocols and components in Cisco UCS Director:

- Ports and trunks

- Multiple Spanning Tree (MST), Per VLAN Spanning Tree (PVST), and VLAN Trunking Protocol (VTP)

- Storage area network (SAN) zones and zonesets

- Virtual device contexts (VDCs), virtual Fibre Channels (VFCs), and virtual port channel (vPC) domains

- VLANs and private VLANs

- Virtual storage area networks (VSANs)

- Virtual extensible local area networks (VXLANs)

Monitoring and Reporting

You can also use Cisco UCS Director to monitor and report on network devices, including:

- Service detail requests

- Configurations

- Modules

- Interfaces

- Port capabilities and profiles

- Pool policies and usage

- MAC address table configurations

- Quality of Service (QoS) policy and class maps

- Service detail requests

- SAN zones and zonesets

- vPC information

- VSAN, VLAN, and Private VLAN information

Network Device Management Tasks You Cannot Perform in Cisco UCS Director

You cannot use Cisco UCS Director to perform certain network device management tasks within a Cisco UCS domain, such as the following:

- Firmware upgrades

- User management

Orchestration Tasks for Network Device Management

Cisco UCS Director includes orchestration features that allow you to automate configuration and management of network domain devices in workflows.

A complete list of the network device orchestration tasks is available in the Workflow Designer and in the Task Library.

For more information about orchestration in Cisco UCS Director, see the Cisco UCS Director Orchestration Guide.

Adding a Network Device Account

In order to create a network devices account, first add a network element in Cisco UCS Director. After a network device is added as a network element in Cisco UCS Director, it appears under the Managed Network Element tab.

Before You Begin

You must be logged in to the appliance to complete this task.

Step 1

On the menu bar, choose Administration > Physical Accounts.

Step 2

Choose the Managed Network Elements tab.

Step 3

Click Add Network Element.

Step 4

In the Add Network Element dialog box, complete the following fields:

Name

Description

Pod drop-down list

Choose the pod to which the network element belongs.

Device Category drop-down list

Choose the device category for this network element. For example: F5 Load Balancer.

Device IP field

The IP address for this device.

Use Credential Policy check box

Click the check box to use a policy to assign the credentials for the device instead of manually entering them. You may browse and choose an existing policy or create a new policy.

Note:
Ensure that you have provided the appropriate protocol value for the device category. For example, if the device category is F5 Load Balance, the protocol value could be HTTP or HTTPs. If the device category is Cisco ASA, the protocol value could be Telnet or SSH.

The following fields appear if you have not clicked the Use Credential Policy check box.

Protocol drop-down list

Choose the protocol to be used to communicate with the device. The list may include the following:

- Telnet

- SSH

- HTTP

- HTTPS

Note:
The values in this drop-down list vary based on the selected device category. For example, if the device category is F5 Load Balance, the available options are HTTP and HTTPs. If the device category is Cisco ASA, the available options are Telnet and SSH.

Port field

The port to use to access the device. This value appears based on the value selected in the Protocol field. You can modify this value, if necessary.

Login field

The login name for the device.

Password field

The password associated with the login name.

Enable Password field

The password to enable access to the device. This field appears only for the following category of devices:

- Cisco ASA

- Brocade Fabric OS

- Brocade Network OS

- Cisco IOS

Step 5

Click Submit.

Adding the device triggers the system task inventory collection. The polling interval configured on the System Tasks tab specifies the frequency of inventory collection.

What to Do Next

To test the connectivity to the device, choose the device, then click the Test Connection button. To edit the credentials of the network device, choose the device, then click the Edit Credentials button. To remove a network device, choose the device, then click the Delete Network Element button.

Collecting Inventory for a Network Device

Step 1

On the menu tab, choose Physical > Network.

Step 2

In the Network pane, choose the pod.

Step 3

Click the Managed Network Elements tab.

Step 4

Select the network device for which you want to collect inventory.

Step 5

Click Collect Inventory.

Configuring the Polling Interval

The polling interval specifies the frequency of inventory collection.

Step 1

On the menu bar, choose Administration > System.

Step 2

Click the System Tasks tab.

Step 3

Choose an inventory task of the account and click Manage Task.

Step 4

From the Minutes drop-down list, choose the polling interval.

Step 5

Click Submit.

Viewing Connectivity and Topology for Network Devices

You can view the connectivity and topology diagram for any network device. You can choose to view a hierarchical, concentric, circular, or force-directed mode.

Step 1

On the menu tab, choose Physical > Network.

Step 2

In the Network pane, choose the pod.

Step 3

Click the Managed Network Elements tab.

Step 4

Select the network device that you want to view.

Step 5

Click View Connectivity.

Step 6

In the Topology View - Network Device Connectivity dialog box, complete the following fields:

Name

Description

View Mode drop-down list

Choose one of the following:

- Hierarchical

- Concentric

- Circular

- Force directed

Show Link Labels check box

Check this check box to show link labels in the topology.

Allow Item Spacing check box

Check this check box to allow line spacing in the view.

Step 7

Click Close when you are finished verifying the connectivity of the network devices and determining their topology.

Verifying Network Device Details in a Pod Environment

After the network device is added to the pod, all discovered components of the pod environment are displayed at the account level.

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, click the pod.

Step 3

Click the Managed Network Elements tab.

Step 4

Click the network device, and click View Details. All information about the device appears in the Summary tab. You can choose other tabs to see specific details, such as interfaces, modules, VLANs, port profiles, and so on, depending on the network device.

Chapter 3. Configuring Multiple Spanning Tree

This chapter contains the following sections:

- About MST

- Configuring an MST Instance

- Enabling MST and Configuring MST Network Parameters

About MST

Multiple Spanning Tree (MST) is the IEEE 802.1s standard that allows two or more VLANs to be assigned to a spanning tree instance. Each instance has a spanning tree topology independent of other spanning tree instances. This architecture provides multiple forwarding paths for data traffic, enables load balancing, and reduces the number of Spanning Tree Protocol (STP) instances required to support a large number of VLANs. MST improves the fault tolerance of the network because a failure in one instance (forwarding path) does not affect other instances (forwarding paths). MST instances with the same name, revision number, and VLAN-to-instance mapping combine to form an MST region. The MST region appears as a single bridge to spanning tree configurations outside the region. MST fails over to IEEE 802.1D STP when it receives an 802.1D message from a neighboring switch.

Note

Spanning tree is used to refer to IEEE 802.1w and IEEE 802.1s. If the text is discussing the IEEE 802.1D Spanning Tree Protocol, 802.1D is stated specifically.

In Cisco UCS Director, MST configuration is supported on the following Cisco network devices:

- Cisco Nexus 3000 Series switches

- Cisco Nexus 5000, 5500, and 5672 Series switches

- Cisco Nexus 6000 Series switches

- Cisco Nexus 7000 Series switches

- Cisco Nexus 9000 Series switches

Configuring an MST Instance

You can configure an MST instance on a network.

Step 1

On the menu bar, click Physical > Network.

Step 2

In the Network pane, choose the pod.

Step 3

Click the Managed Network Elements tab.

Step 4

Select the network device to be configured.

Step 5

Click the down-arrow icon, and choose Configure MST Instance.
You can alternatively choose Configure MST Instance command on the Summary tab that appears on selection of the network device from the left pane.

Step 6

In the Configure MST Instance dialog box, complete the following fields:

Name

Description

MST Instance field

The MST ID number.

VLAN field

The VLAN to apply in this MST ID.

Step 7

Click Submit.

Enabling MST and Configuring MST Network Parameters

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, choose the pod.

Step 3

Click the Managed Network Elements tab.

Step 4

Select the network device to be configured.

Step 5

Click the down-arrow icon, and choose Configure MST.
You can alternatively choose Configure MST command on the Summary tab that appears on selection of the network device from the left pane.

Step 6

In the Configure MST dialog box, complete the following fields:

Name

Description

Enable MST check box

Check this check box to enable MST.

Note:
To disable MST, uncheck this check box.

Name field

(Required) The MST region name for the bridge. The name string has a maximum length of 32 characters and is case-sensitive. The default is an empty string.
Note:
For two or more bridges to be in the same MST region, they must have the identical MST name, VLAN-to-instance mapping, and MST revision number.

Revision field

(Required) The revision number is an unsigned 16-bit number that identifies the revision of the current MST configuration.

Hello Time field

The hello time between each bridge protocol data unit (BPDU) that is sent on the root bridge port that is used for all MST instances. These messages mean that the switch is alive. For seconds, the range is from 1 to 10, and the default is 2 seconds.

Forward Time field

The forward delay time for all MST instances that a port waits before changing from its spanning tree blocking and learning states to the forwarding state. For seconds, the range is from 4 to 30, and the default is 15 seconds.

Max Hop Count field

The Max Hop Count to be used. This is the maximum number of hops for the MST region. A region is the equivalent of Border Gateway Protocol (BGP) Autonomous Systems, which is a group of switches placed under common administration.

Max Age in seconds field

The maximum-aging time for all MST instances. The maximum-aging time is the number of seconds that a switch waits without receiving spanning tree configuration messages before attempting a reconfiguration. For seconds, the range is from 6 to 40, and the default is 20 seconds.

Copy Running configuration to Startup configuration check box

Check this check box to copy the running configuration to the startup configuration.

Step 7

In the Select Items dialog box, check the check boxes to choose individual ports, and click Select.

Step 8

Click Submit.

Chapter 4. Configuring Per VLAN Rapid Spanning Tree Plus

This chapter contains the following sections:

- About PVST+

- Configuring PVST+

About PVST+

Per VLAN Rapid Spanning Tree Plus (PVST+), is an updated implementation of the Spanning Tree Protocol (STP) that allows you to create one spanning tree topology for each VLAN. PVST+ is the default STP mode on the switch and uses inter switch-link (ISL) trunking and allows a VLAN trunk to forward some VLANs while blocking other VLANs. Because PVST+ treats each VLAN as a separate network, it can load balance traffic (at Layer 2) by forwarding some VLANs on one trunk and other VLANs on another trunk without causing a spanning tree loop.

In Cisco UCS Director, PVST+ configuration is supported on the following Cisco network devices:

- Cisco Nexus 3000 Series switches

- Cisco Nexus 5000, 5500, and 5672 Series switches

- Cisco Nexus 6000 Series switches

- Cisco Nexus 7000 Series switches

- Cisco Nexus 9000 Series switches

Note

For more detailed information about PVST+ and configuration guidelines for PVST+, see the Cisco NX-OS Software Configuration Guides.

Configuring PVST+

Per VLAN Rapid Spanning Tree Plus (PVST+) maintains a spanning tree instance for each VLAN that you configure.

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, choose the pod.

Step 3

Click the Managed Network Elements tab.

Step 4

Select the network device to be configured.

Step 5

Click the down-arrow icon, and choose Configure PVST.
You can alternatively choose Configure PVST command on the Summary tab that appears on selection of the network device from the left pane.

Step 6

In the Configure PVST dialog box, complete the following fields:

Name

Description

Enable PVST check box

Check this check box to enable PVST+ on the device.

VLAN field

The VLAN ID within the valid range. The valid VLAN ID range value can be 2 through 4094 (except reserved VLAN values).

PVST Root Mode check box

Check this check box to enable PVST+ root mode which defines the tree with a root bridge and a loop-free path from the root to all switches in the network. STP forces redundant data paths into a blocked state. If a network segment in the spanning tree fails and a redundant path exists, the STP algorithm recalculates the spanning tree topology and activates the blocked path.

Priority drop-down list

Choose the STP port priority on the switch. This parameter is used to determine which port is put in the forwarding state and which port is put in the blocking state.

Path Cost drop-down list

Choose the STP path cost (long or short). This parameter is used to determine which port is put in the forwarding state and which port is put in the blocking state.

Copy Running configuration to Startup configuration check box

Check this check box to copy the running configuration to the startup configuration.

Step 7

Click Submit.

Chapter 5. Configuring VLAN Trunking Protocol

This chapter contains the following sections:

- About VTP

- Configuring VTP

About VTP

VLAN Trunking Protocol (VTP) reduces the administration in a switched network. When you configure a new VLAN on one VTP server, the VLAN is distributed through all switches in the domain, which reduces the need to configure the same VLAN everywhere.

In Cisco UCS Director, VTP configuration is supported on the following Cisco network devices:

- Cisco Nexus 3000 Series switches

- Cisco Nexus 5000, 5500, and 5672 Series switches

- Cisco Nexus 6000 Series switches

- Cisco Nexus 7000 Series switches

- Cisco Nexus 9300 and 9500 Series switches

Note

For more detailed information about VTP and configuration guidelines for VTP, see the Cisco NX-OS Software Configuration Guides.

Configuring VTP

You can enable or disable the VLAN Trunking Protocol (VTP) to relay VTP packets on a network.

Note

Ensure that you are in the correct virtual device context (VDC). VLAN names and IDs can be repeated in different VDCs, so you must verify that you are working in the correct VDC.

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, choose the pod.

Step 3

Select the network device to be configured.

Step 4

Click the VTP Status tab.

Step 5

Select the VTP to be configured.

Step 6

Click Configure VTP.

Step 7

In the Configure VTP dialog box, complete the following fields:

Name

Description

Enable VTP Feature check box

Check this check box to enable VTP.

Domain Name field

The name of the VTP domain that you want this switch to join.

VTP version drop-down list

Choose either VTP version 1 or 2.

Note:
If you are using VTP in a Token Ring environment, you must use version 2.

File Name field

The filename.

Password field

The password.

VTP mode drop-down list

Choose one of the following VTP modes: Client, Server, Transparent, or Off.

Note:   By default, the VTP mode is set as Transparent for the Cisco Nexus 9300 Series switches.

Copy Running configuration to Startup configuration check box

Check this check box to copy the running configuration to the startup configuration.

Step 8

Click Submit.

Chapter 6. Managing MAC Addresses

This chapter contains the following sections:

- About MAC Addresses

- Adding a MAC Address to a Switch

- Removing a MAC Address from a Switch

- Assigning MAC Address to a Port

- Unassigning MAC Address from a Port

- Configuring the Aging Time for the MAC Address Table

About MAC Addresses

The Media Access Control (MAC) address is a unique value that is associated with a network device. Layer 2 ports correlate the MAC address on a packet with the Layer 2 port information for that packet using the MAC address table. A MAC address table is built using the MAC source addresses of the frames received.

In Cisco UCS Director, MAC configuration is supported on the following Cisco network devices:

- Cisco Nexus 1000 Series switches

- Cisco Nexus 3000 Series switches

- Cisco Nexus 5000, 5500, and 5672 Series switches

- Cisco Nexus 6000 Series switches

- Cisco Nexus 7000 Series switches

- Cisco Nexus 9300 and 9500 Series switches

Note

For more detailed information about MAC addresses and configuration guidelines for MAC addresses, see the Cisco NX-OS Software Configuration Guides.

Adding a MAC Address to a Switch

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device that needs to be configured.

Step 4

Click the MAC Address Table tab.

Step 5

Click Create MAC Address.

Step 6

In the MAC Address Parameters dialog box, complete the following fields:

Name

Description

MAC Address field

The MAC address that is added to the switch MAC address table.

VLAN ID Select button

In the Select dialog box, choose the VLAN ID number associated with this MAC address.

Select Port Select button

In the Select dialog box, choose the LAN port (channel) for this VLAN ID number.

Copy Running configuration to Startup configuration check box

Check this check box to copy the running configuration to the startup configuration.

Step 7

Click Submit.

Removing a MAC Address from a Switch

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device for which you need to delete the MAC address.

Step 4

Click the MAC Address Table tab.

Step 5

Choose the MAC address to be deleted.

Step 6

Click Delete.

Step 7

In the MAC Address Parameters dialog box, complete the following fields:

Name

Description

MAC Address button

The MAC address on the switch that you selected for deletion.

VLAN ID field

The VLAN ID number associated with the MAC address.

Copy Running configuration to Startup configuration check box

Check this check box to copy the running configuration to the startup configuration.

Step 8

Click Submit.

Assigning MAC Address to a Port

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the MAC Address Table tab.

Step 5

Choose a MAC address to be assigned to a port.

Step 6

Click Assign MAC Address Port.

Step 7

In the MAC Address Parameters dialog box, complete the following fields:

Name

Description

MAC Address field

The MAC address to be assigned to a port.

Select Port button

Click Select. In the Select dialog box, choose the LAN port (channel).

Copy Running configuration to Startup configuration check box

Check this check box to copy the running configuration to the startup configuration.

Step 8

Click Submit.

Unassigning MAC Address from a Port

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the MAC Address Table tab.

Step 5

Click Unassign MAC Address Port.

Step 6

In the MAC Address Parameters dialog box, complete the following fields:

Name

Description

Select Port button

Click Select. In the Select dialog box, choose the LAN port (channel).

Copy Running configuration to Startup configuration check box

Check this check box to copy the running configuration to the startup configuration.

Step 7

Click Submit.

Configuring the Aging Time for the MAC Address Table

You can configure the amount of time that an entry (the packet source MAC address and port that packet ingresses) remains in the MAC address table.

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the MAC Address Table Configuration tab.

Step 5

Click Configure MAC Address Table.

Step 6

In the MAC Address Parameters dialog box, complete the following fields:

Name

Description

Age Time field

The time from 120 to 918,000 seconds before an entry ages out and is discarded from the MAC address table. The number 0 disables MAC aging. You can use multiples of 5. The default is 300 seconds. If a VLAN is not specified, the aging specification applies to all VLANs.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 7

Click Submit.

Chapter 7. Managing Virtual Device Contexts

This chapter contains the following sections:

- About VDCs

- Creating a VDC

- Allocating a Port to a VDC

- Removing a Port from a VDC

- Removing a VDC

About VDCs

Virtual device contexts (VDCs) allow switches to be virtualized at the device level. Each configured VDC presents itself as a unique device to connected users under that physical switch. The VDC runs as a separate logical entity within the switch. It maintains its own unique set of running software processes, has its own configuration, and is managed by a separate administrator.

In Cisco UCS Director, you can manage VDCs on the following Cisco network devices:

- Cisco Nexus 7000 Series switches

Note

For more detailed information about VDCs and configuration guidelines for VDCs, see the Cisco NX-OS Software Configuration Guides.

Creating a VDC

You can create a VDC for a Cisco Nexus 7000 Series switch.

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod and select the Cisco Nexus 7000 Series switch.

Step 3

Click the VDC tab.

Step 4

Click Create VDC.

Step 5

In the Create VDC dialog box, complete the following fields:

Name

Description

VDC Name field

The name of the VDC.

Module Type field

The name of the module type. For example, F2e Series.

HA Policy check box

Check this check box to enable the high-availability (HA) policy for the switch when an unrecoverable VDC fault occurs.

VDC Number field

The VDC number. VDC number 1 is reserved for the default VDC. The nondefault VDC numbers are from 2 to 9.

VDC Password field

The VDC administrator user account password.

VDC Template Name drop-down list

Choose the VDC template name. VDC resource templates set the minimum and maximum limits for shared physical device resources when you create the VDC.

Select VDC Type drop-down list

Choose the VDC type.

Copy Running configuration to Startup configuration check box

Check this check box to copy the running VDC configuration to the startup configuration.

Step 6

Click Submit.

Allocating a Port to a VDC

You can assign a port to a VDC that belongs to a Cisco Nexus 7000 Series switch.

Before You Begin

You must create a virtual device context (VDC) on a Cisco Nexus 7000 Series switch.

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod and select the Cisco Nexus 7000 Series switch.

Step 3

Click the VDC tab.

Step 4

Select the VDC to which you want to assign a port.

Step 5

Click Assign Port to VDC.

Step 6

In the Allocate Port VDC dialog box, complete the following fields:

Name

Description

VDC Name field

The name of the VDC.

Select Port button

Click Select. In the Select Items dialog box, choose the port to assign to the VDC and click Select.

Copy Running configuration to Startup configuration check box

Check this check box to copy the running VDC configuration to the startup configuration.

Step 7

Click Submit.

Removing a Port from a VDC

You can remove a port belonging to a virtual device context (VDC) on a Cisco Nexus 7000 Series switch.

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod and select the Cisco Nexus 7000 Series switch.

Step 3

Click the VDC tab.

Step 4

Select the VDC and click Remove Port from VDC.

Step 5

In the Remove VDC dialog box, complete the following fields:

Name

Description

VDC Name field

The name of the VDC.

Select Port button

Choose the port that you want to remove from the VDC.

Copy Running configuration to Startup configuration check box

Check this check box to copy the running VDC configuration to the startup configuration.

Step 6

Click Submit.

Removing a VDC

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod and select the Cisco Nexus 7000 Series switch.

Step 3

Click the VDC tab.

Step 4

Select the VDC that you want to remove.

Step 5

Click Remove VDC.
You can alternatively choose commands by clicking the down-arrow icon.

Step 6

In the Remove VDC dialog box, complete the following field:

Name

Description

Copy Running configuration to Startup configuration check box

Check this check box to copy the running configuration to the startup configuration.

Step 7

Click Submit.

Chapter 8. Managing Ports

This chapter contains the following sections:

- About Ports

- Configuring a Port

- Configuring an STP Port

- Configuring a Port License

- Managing Port Profiles

- Managing Port Channels

- Configuring a Private VLAN Port Profile

About Ports

Switch ports are Layer 2-only interfaces that are associated with a physical port. Switch ports belong to one or more VLANs. A switch port can be an access port, a trunk port, or a tunnel port. Switch ports are used to manage the physical interface and associated Layer 2 protocols; they do not handle routing or bridging.

In Cisco UCS Director, you can configure ports and port profiles on the following Cisco network devices:

- Cisco Nexus 1000 and 1110 Series switches

- Cisco Nexus 3000 Series switches

- Cisco Nexus 5000, 5500, and 5672 Series switches

- Cisco Nexus 6000 Series switches

- Cisco Nexus 7000 Series switches

- Cisco Nexus 9300 and 9500 Series switches

- Cisco MDS 9100 Series switches

- Cisco MDS 9500 Series switches

- Cisco MDS 9700 Series switches

- Cisco ASA 5500 Series firewall

- Cisco IOS Devices

- Cisco Adaptive Security Virtual Appliance (ASAv)

Note

For more detailed information about managing ports, see the Cisco NX-OS Software Configuration Guides.

Configuring a Port

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the Interfaces tab.

Step 5

Choose an interface to be configured.

Step 6

Click Configure Port.

Step 7

In the Configure Port dialog box, complete the following fields:

Name

Description

Select Port field

The port to be configured is displayed.

Enable check box

Check the check box to enable the port.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 8

Click Submit.

Configuring an STP Port

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.
The summary status of the device is displayed.

Step 4

Click Configure STP Port.

Step 5

In the Configure STP Port dialog box, complete the following fields:

Name

Description

Select Port Select button

(Required) Click Select. In the Select dialog box, choose the designated STP port.

Continue to Step 7 if the required parameters are specified for this port.

VLAN field

The VLAN ID number from 1 to 4094.

Cost Auto check box

Check this check box to enable automatic choosing of the least costly port path. Port costs break a tie for the designated port.

Hello Time field

The hello time to be used on this port. This is the time between each bridge protocol data unit (BPDU) that is sent on a port.

Forward Time field

The forward delay to be used on this port. This is the time that is spent in the listening and learning state.

Max Age field

The maximum length of time before a bridge port saves its configuration BPDU information.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 6

Click Submit.

Configuring a Port License

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.
The summary status of the device is displayed.

Step 4

Click Configure Port License.

Step 5

In the Configure Port License dialog box, complete the following fields:

Name

Description

Select Port drop-down

Choose a port from the list.

Acquire check box

Check this check box to acquire the license.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 6

Click Submit.

Managing Port Profiles

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, choose the pod.

Step 3

In the Managed Network Elements tab, choose the network device that needs to be configured.

Step 4

Click View Details.

Step 5

Click the Port Profiles tab. The port profiles created in the network device are displayed. The channel group mode and subgroup type of the port profile appear only when you choose the network device that is configured with Hyper-V. The Port Profiles tab provides the following actions:

Action

Description

Refresh

Refreshes the current page.

Favorite

Adds this page to the Favorites tab which displays the page that you go to most often.

Create Port Profile

Creates a port profile in the network device.

When you choose a port profile, the following additional action appears:

Action

Description

View Details

Appears when you choose the network device that is not configured with Hyper-V. Click View Details to view the service request details of the port profile.

Delete Port Profile

Deletes a port profile.

Update Port Profile

Updates a port profile.

Publish Port Profile

This action appears when you choose the network device that is configured with Hyper-V. Click Publish Port Profile to publish the port profile to System Center Virtual Machine Manager (SCVMM).

Manage Tag

Adds a tag to the port profile, edits the assigned tag, and deletes the tag from the port profile.

Note:   The tags that are assigned with the taggable entities as physical storage and network device are displayed. For more information on the tab library, see Cisco UCS Director Administration Guide.

Add Tags

Adds a tag to the port profile.

Note:   The tags that are assigned with the taggable entities as physical storage and network device are displayed. For more information on the tab library, see Cisco UCS Director Administration Guide.

Delete Tags

Deletes the tag(s) from the port profile.

Note:   The tags that are assigned with the taggable entities as physical storage and network device are displayed. For more information on the tab library, see Cisco UCS Director Administration Guide.

- Creating a Port Profile

Creating a Port Profile

The port profile that you create for a network device is available as a distributed port group on VMware vCenter if there is a connection between the Virtual Supervisor Module (VSM) and vCenter.

Step 1

Navigate to the Port Profiles tab.
For more information about how to navigate to the Port Profiles tab, see Managing Port Profiles.

Step 2

Click Create Port Profile.

Step 3

In the Port Profile Configuration dialog box, complete the fields.

When you choose the network device that is not configured with Hyper-V, you see the following fields:

Name

Description

Port Profile Name field

(Required) The name for the network device port profile.

Description field

The description of the port profile.

Port Profile Type drop-down list

Choose one of the following: Vethernet or Ethernet.

Mode drop-down list

Choose one of the following: Access or Trunk.

Access VLAN drop-down list

(Required) Choose the access VLAN type.

Enable VXLAN Capability check box

Check this check box to enable the virtual extensible LAN (VXLAN) capability on this port profile. Uncheck the check box if you do not want to enable the VXLAN capability.

IP address field

The IP network address.

IP network mask field

The subnetwork address mask for this network.

IP next-hop address field

The IP next-hop address.

QOS Policy Map drop-down list

Choose the quality of service (QoS) policy map to apply to the port profile if applicable.

Select Sgt field

This field appears when you choose Vethernet as the port profile type. Click Select. In the Select dialog box, choose an SGT.

Note:
SGT support is provided for the Cisco Nexus 1000v and Cisco Nexus 1110 switches.

Copy Running configuration to Startup configuration check box

Check this check box to copy the running port profile configuration to the startup configuration.

When you choose the network device that is configured with Hyper-V, you see the following fields:

Name

Description

Port Profile Name field

(Required) The name for the network device port profile.

Description field

The description of the port profile.

Port Profile Type drop-down list

Choose one of the following: Ethernet or Vethernet.

Defining a port profile type as Ethernet allows the port profile to be used for physical (Ethernet) ports. In a vCenter server, the corresponding port group can be selected and assigned to physical ports (PNICs).

Publish Port Profile check box

This check box appears when you choose Vethernet as the port profile type. Check this check box to publish the port profile to System Center Virtual Machine Manager (SCVMM).

Publish Port Profile Name check box

This field appears when you check the Publish Port Profile check box. The name for the published port profile name.

Channel Group Mode drop-down list

This drop-down list appears when you choose Ethernet as the port profile type. Choose one of the following:

- Sub-Group—Subgroups are logically smaller port channels that can consist of one or more uplinks to the physical switch.

- Mac-Pinning—If you are connecting to multiple upstream switches that do not support port channels, MAC pinning is the preferred configuration. MAC pinning designates that one subgroup per Ethernet member port must be automatically assigned.

Sub Group Type drop-down list

This drop-down list appears when you choose Sub-Group as the channel sub-group mode. Choose one of the following:

- CDP—Automatically creates subgroups using information from the Cisco Discovery Protocol (CDP) packets.

- Manual—Manually configures port channel subgroups to manage the traffic flow on multiple upstream switches. This option is required for a port channel that connects to multiple upstream switches where CDP is not configured.

Mode drop-down list

Choose one of the following as mode:

- Trunk—Automatically creates subgroups using information from the Cisco Discovery Protocol (CDP) packets.

- Access—Manually configures port channel subgroups to manage the traffic flow on multiple upstream switches. This option is required for a port channel that connects to multiple upstream switches where CDP is not configured.

Allowed VLANs field

This field appears when you choose Trunk as the mode. Click Select and choose VLANs that are allowed on the trunk link.

Enable VXLAN Capability check box

This field appears when you choose Vethernet as the port profile type and Access as the mode of port profile. Check this check box to enable the virtual extensible LAN (VXLAN) capability on this port profile. Uncheck the check box if you do not want to enable the VXLAN capability.

Access VLAN field

This field appears when you choose Access as the mode. Choose the VLAN for which this access port carries traffic.

Add to System VLAN check box

Check this check box to add the port profile to system VLAN.

System VLAN field

This field appears when you check the Add to System VLAN check box. Click Select and choose system VLAN to which you need to add the port profile.

Copy Running configuration to Startup configuration check box

Check this check box to copy the running port profile configuration to the startup configuration.

Step 4

Click Submit.

Managing Port Channels

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, choose the pod.

Step 3

In the Managed Network Elements tab, choose the network device to be configured.

Step 4

Click View Details.

Step 5

Click the Interfaces tab. The interfaces created in the network device are displayed. The Interfaces tab provides the following actions:

Action

Description

Refresh

Refreshes the current page.

Favorite

Adds this page to the Favorites tab which displays the page that you go to most often.

Create Port Channel

Creates a port channel in the network device.

When you choose a port channel, the following actions appear:

Action

Description

Configure Port

Configures a port.

Delete Port Channel

Deletes a port channel.

Manage Tag

Adds a tag to the port channel, edits the assigned tag, and deletes the tag from the port channel.

Note:   The tags that are assigned with the taggable entities as physical storage and network device are displayed. For more information on the tab library, see Cisco UCS Director Administration Guide.

Add Tags

Adds a tag to the port channel.

Note:   The tags that are assigned with the taggable entities as physical storage and network device are displayed. For more information on the tab library, see Cisco UCS Director Administration Guide.

Delete Tags

Deletes the tags from the port channel.

Note:   The tags that are assigned with the taggable entities as physical storage and network device are displayed. For more information on the tab library, see Cisco UCS Director Administration Guide.

Configure Access

Configures the interface as an access port.

Configure Trunk

Configures the interface as a trunk port.

Update Trunk

Updates the trunk port that is configured on the interface.

- Creating a Port Channel

Creating a Port Channel

Step 1

Navigate to the Interfaces tab.
For more information about how to navigate to the Interfaces tab, see Managing Port Channels.

Step 2

In the Network pane, expand the pod.

Step 3

Choose the network device to be configured.

Step 4

Click the Interfaces tab.

Step 5

Click Create Port Channel.

Step 6

In the Create Port Channel dialog box, complete the following fields:

Name

Description

Port Channel Number field

The port channel number that you choose within the valid range. The valid port channel range value can be between 1 and 4096.

Description field

The description of the port channel.

Copy Running configuration to Startup configuration check box

Check this check box to copy the running configuration to the startup configuration.

Step 7

Click Submit.

Configuring a Private VLAN Port Profile

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Choose the network device to be configured.

Step 4

Click the Private VLANs tab.

Step 5

Click Configure Private VLAN Port Profile.

Step 6

In the Configure Private VLAN Port Profile dialog box, complete the following fields:

Name

Description

Port Profile Name field

(Required) The port profile name.

Port Profile Type drop-down list

The port profile type.

Trunk check box

Check this check box to create the port profile in trunk mode.

Type drop-down list

Choose either host or promiscuous.

Primary VLAN ID drop-down list

Choose the primary VLAN ID.

Secondary VLAN ID Select button

Click Select. In the Select Items dialog box, choose the valid secondary VLAN ID(s) and click Select.

Copy Running configuration to Startup configuration check box

Check this check box to copy the running configuration to the startup configuration.

Step 7

Click Submit.

Chapter 9. Configuring SVI

This chapter contains the following sections:

- About SVI

- Configuring a SVI

- Deleting a SVI

About SVI

A switch virtual interfaces (SVI) or VLAN interface, is a virtual routed interface that connects a VLAN on the device to the Layer 3 router engine on the same device. Only one VLAN interface can be associated with a VLAN, but configure a VLAN interface for a VLAN only when you want to route between VLANs or to provide IP host connectivity to the device through a virtual routing and forwarding (VRF) instance that is not the management VRF. When you enable VLAN interface creation, Cisco NX-OS creates a VLAN interface for the default VLAN (VLAN 1) to permit remote switch administration.

Enable the VLAN network interface feature before you can configure it.

In Cisco UCS Director, SVI configuration is supported on the following Cisco network devices:

- Cisco Nexus 5000, 5500, and 5672 Series switches

- Cisco Nexus 7000 Series switches

Configuring a SVI

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the Interfaces tab.

Step 5

Click Add SVI.

Step 6

In the Configure SVI dialog box, complete the following fields:

Name

Description

VLAN Interface Number field

The VLAN interface number within the valid range. The valid VLAN interface range value can be 1 to 4094.

Description field

The description of the VLAN interface.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 7

Click Submit.

Deleting a SVI

Step 1

In the Interface tab, select the interface to be deleted.

Step 2

Click Remove SVI. The Remove SVI dialog box appears to confirm deletion of SVI.

Step 3

Check the Copy Running configuration to Startup configuration check box to copy the configuration to the startup configuration.

Step 4

Click Submit.

Chapter 10. Managing TrustSec

This chapter contains the following sections:

- About Cisco Trustsec

- Refreshing TrustSec

About Cisco Trustsec

Cisco TrustSec provides an access-control solution that builds upon an existing identity-aware infrastructure to ensure data confidentiality between network devices and integrate security access services on one platform. In the Cisco TrustSec solution, enforcement devices utilize a combination of user attributes and endpoint attributes to make role-based and identity-based access control decisions. The availability and propagation of this information is used to apply security solutions across networks at the access, distribution, and core layers of the network.

In Cisco UCS Director, you can manage Cisco Trustsec on the following Cisco network devices:

- Cisco ASA 5500 Series firewall

- Cisco Adaptive Security Virtual Appliance (ASAv)

Refreshing TrustSec

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.
The summary of the device is displayed.

Step 4

Click TrustSec Refresh.

Step 5

In the TrustSec Refresh dialog box, complete the following field:

Name

Description

Copy Running configuration to Startup configuration check box field

Check the check box to copy the running configuration to the startup configuration.

Step 6

Click Submit.

Chapter 11. Configuring SGT Exchange Protocol Connection

This chapter contains the following sections:

- About SXP Connection

- Configuring an SXP Peer Connection

About SXP Connection

You can use the Security Group Tag (SGT) Exchange Protocol (SXP) to propagate the SGTs across network devices that do not have hardware support for Cisco TrustSec.

In Cisco UCS Director, SXP connection is supported on the following Cisco network devices:

- Cisco Nexus 1000 Series switches

- Cisco Nexus 5000, 5500, and 5672 Series switches

- Cisco Nexus 7000 Series switches

- Cisco ASA 5500 Series firewall

- Cisco Adaptive Security Virtual Appliance (ASAv)

Configuring an SXP Peer Connection

You must configure the SXP peer connection on both of the devices. One device is the speaker and the other is the listener. When using password protection, make sure to use the same password on both ends.

Note

If a default SXP source IP address is not configured and you do not configure an SXP source address in the connection, the Cisco TrustSec software derives the SXP source IP address from existing local IP addresses. The SXP source address might be different for each TCP connection initiated from the switch.

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Note:   For configuring SXP peer connection on Cisco Nexus 7000 Series switches, click the VDC tab, choose the Ethernet type VDC, and click View Details.

Step 4

Click the SXP Connection Peers tab.

Step 5

Click Add.

Step 6

In the Configure SXP Connection Peer dialog box, complete the following fields:

Name

Description

Enable SXP check box

Check the check box to enable SXP.

Default Source IP Address field

The IP address of the default source device.

Note:
If no address is specified, the connection uses the default source address, if configured, or the address of the port.

Default Password field

The password that SXP uses for the connection.

Peer IP Address field

The IP address of the peer device.

Source IP Address field

The IP address of the source device.

Password Option drop-down list

Choose one of the following as the password option:

- None—Do not use a password.

- Default—Use the default SXP password.

Mode drop-down list

Choose one of the following modes to specify the role of the remote peer device:

- Peer—The specified mode refers to the peer device.

- Local—The specified mode refers to the local device.

VRF field

The Virtual Routing and Forwarding (VRF) to the peer.

Role drop-down list

Choose one of the following as the role of the device:

- Listener—Default. Specifies that the device is the listener in the connection.

- Speaker—Specifies that the device is the speaker in the connection.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 7

Click Submit.

Chapter 12. Configuring HSRP

This chapter contains the following sections:

- About HSRP

- Configuring HSRP

About HSRP

Hot Standby Router Protocol (HSRP) provides high network availability by providing redundancy for IP traffic from hosts on networks. HSRP routes IP traffic without relying on the availability of any single router. It enables a set of router interfaces to work together to present the appearance of a single virtual router or default gateway to the hosts on a LAN.

When HSRP is configured on a network or segment, it provides a virtual Media Access Control (MAC) address and an IP address that is shared among a group of configured routers. HSRP allows two or more HSRP-configured routers to use the MAC address and IP network address of a virtual router. The virtual router does not exist; it represents the common target for routers that are configured to provide backup to each other. One of the routers is selected to be the active router and another to be the standby router. The standby router assumes control of the group MAC address and IP address when the designated active router fail.

In Cisco UCS Director, HSRP configuration is supported on the following Cisco network devices:

- Cisco Nexus 5000, 5500, and 5672 Series switches

- Cisco Nexus 7000 Series switches

Configuring HSRP

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, choose the pod.

Step 3

Select the network device to be configured.

Step 4

Click View Details.

Note:   For configuring HSRP on Cisco Nexus 7000 Series switches, expand the pod and choose the network device. Click the VDC tab, choose the Ethernet type VDC, and click View Details.

Step 5

Click the HSRP tab.

Step 6

Click Add.

Step 7

In the Configure HSRP dialog box, complete the following fields:

Name

Description

Interface Name field

Click Select and choose an interface on which you want to enable HSRP.

Description field

Description for the selected interface.

Enable Interface check box

Check the check box to enable the interface.

Interface IP Address field

The IP address of the interface.

IP Network Mask field

The network mask address of the interface.

HSRP Group Number field

The group number to which the command applies. The valid range is from 0 to 4095.

Authentication Text field

Enter a string to be carried in all HSRP messages.

Min Preempt Delay Time field

The time that is set to cause the local router to postpone taking over the active role for the number of seconds shown. The range is 0 to 3600 (1 hour); the default is 0 (no delay before taking over).

Priority field

Sets the group priority. The valid range is from 1 to 255; the default is 100.

Lower Threshold Time field

Sets the lower threshold time. The valid range is from 0 to 255 and must be lesser than priority.

Upper Threshold Time field

Sets the upper threshold time. The valid range is from 0 to 255 and must be greater than lower threshold time and priority.

Hello Interval field

The hello interval in seconds. The range is from 1 to 254; the default is 3 seconds.

Hold Time Interval field

The time in seconds before the active or standby router is declared to be down. The range is from 1 to 255; the default is 10 seconds.

Virtual IP Address field

The virtual IP address of the hot standby router interface. You must enter the virtual IP address for at least one of the interfaces; it can be learned on the other interfaces.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 8

Click Submit.

Chapter 13. Managing FC Alias

This chapter contains the following sections:

- About FC Alias

- Creating a FC Alias

- Updating a FC Alias

- Deleting a FC Alias

About FC Alias

FC Alias is the alias for World Wide Port Names (WWPNs) on the fabric for a particular VSAN.

In Cisco UCS Director, you can manage FC Alias on the following Cisco network devices:

- Cisco Nexus 5000, 5500, and 5672 Series switches

- Cisco Nexus 7000 Series switches

- Cisco MDS 9100 Series switches

- Cisco MDS 9500 Series switches

- Cisco MDS 9700 Series switches

Creating a FC Alias

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, choose the pod.

Step 3

Select the network device to be configured.

Step 4

Click View Details.

Note:   For creating a FC Alias for Cisco Nexus 7000 Series switches, expand the pod and choose the network device. Click the VDC tab, choose the storage type VDC, and click View Details.

Step 5

Click the FCAlias tab.

Step 6

Click Add.

Step 7

In the Create FCAlias dialog box, complete the following fields:

Name

Description

FC Alias Name field

Name of the alias.

VSAN Id field

Click Select. In the Select dialog box, choose the VSAN ID.

Member Type drop-down

Choose one of the following as the type of member:

- DeviceAlias

- pWWN

- fWWN

Member field

The value for the member.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 8

Click Submit.

Updating a FC Alias

Step 1

In the FCAlias tab, select the FC Alias to be updated.

Step 2

Click Modify.

Step 3

In the Update FCAlias dialog box, complete the following fields:

Name

Description

VDC Name field

Click Select. In the Select dialog box, choose the VDC.

Members List table

The list of members in the Alias.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 4

Click Submit.

Deleting a FC Alias

Step 1

In the FCAlias tab, select the FC Alias to be deleted.

Step 2

Click Delete. The Delete FCAlias dialog box appears to confirm deletion of FC Alias.

Step 3

Check the Copy Running configuration to Startup configuration check box to copy the configuration to the startup configuration.

Step 4

Click Submit.

Chapter 14. Configuring Access Ports

This chapter contains the following sections:

- About Access Ports

- Configuring an Access Port

About Access Ports

Access ports in switches are used to connect end devices such as workstations and printers. When you configure an access port, define which VLAN that the port belongs to.

In Cisco UCS Director, you can configure access ports on the following Cisco network devices:

- Cisco Nexus 3000 Series switches

- Cisco Nexus 5000 Series switches

- Cisco Nexus 7000 Series switches

- Cisco Nexus 6000 Series switches

- Cisco Nexus 9300 and 9500 Series switches

Configuring an Access Port

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the Interfaces tab.

Step 5

Select the interface that you want to configure as an access port.

Step 6

Click Configure Access.

Step 7

In the Access Configuration dialog box, complete the following fields:

Name

Description

Select Port field

The port that you want to configure as an access port.

Access VLAN field

Choose a VLAN to which you want to associate the port.

STP Port Type drop-down list

Choose one of the following as the port type for the Spanning Tree Protocol (STP) to use:

- edge

- network

- normal

Description

Optionally, enter a description for the access port configuration.

Copy Running configuration to Startup configuration check box

Check the box to copy the running configuration to the startup configuration.

Step 8

Click Submit.

Chapter 15. Managing Access Control Lists

This chapter contains the following sections:

- About Access Control Lists

- Creating an ACL

- Configuring Context ACL

- Adding a MAC ACL Rule or an IP ACL Rule

About Access Control Lists

Packet filtering allows you to limit network traffic and restrict network use by certain users or devices. Access control list (ACL), filters traffic as it passes through a switch and permit or deny packets crossing specified interfaces. An ACL is a sequential collection of permit and deny conditions that apply to packets. When a packet is received on an interface, the switch compares the fields in the packet against any applied ACLs to verify that the packet has the required permissions to be forwarded.

You can use ACLs to protect networks and specific hosts from unnecessary or unwanted traffic. For example, you could use ACLs to disallow HTTP traffic from a high-security network to the Internet. You could also use ACLs to allow HTTP traffic but only to specific sites, using the IP address of the site to identify it in an IP ACL.

In Cisco UCS Director, you can configure ACLs on the following Cisco network devices:

- Cisco Nexus 9300 and 9500 Series switches firewall

- Cisco IOS Devices

In Cisco UCS Director, you can configure context ACLs on the following Cisco network devices:

- Cisco ASA 5500 Series firewall

- Cisco Adaptive Security Virtual Appliance (ASAv)

Creating an ACL

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, choose the pod.

Step 3

Select the device for which you want to create an ACL.

Step 4

Choose Create ACL Entry from the drop-arrow icon.

Step 5

In the Create ACL Entry dialog box, complete the following fields:

Name

Description

ACL Name field

The name of the ACL.

Type drop-down list

Choose one of the following as the ACL type:

- IP

- MAC

- IPV6

Description field

The description of the ACL.

Per ACL Entry stats collection check box

Check the check box to collect the statistics details of the ACL entry.

Apply ACL to Interface check box

Check the check box to apply the ACL to an interface. The Interface Name field appears. Click Select and choose an interface to which you want to apply the ACL.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 6

Click Submit.

Configuring Context ACL

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the device for which you want to configure context ACL.

Step 4

Click the ACL tab.

Step 5

Select the ACL that needs to be configured.

Step 6

Click Configure Context ACL.

Step 7

In the Configure Context ACL dialog box, complete the following fields:

Name

Description

ACL Name field

The name of the context ACL.

Interface Name drop-down list

Choose the interface name on which you want to configure the context ACL.

Permit check box

Check the check box to forward the packets.

InBound Traffic check box

Check the check box to apply the ACL to inbound packets on an interface.

Protocol drop-down list

Choose one of the following to filter by Application layer protocol:

- ip

- tcp

- udp

- icmp

Source IP Address/IPv6 Prefix field

The IP address of the source host name that you want to apply to the ACL so that the packets from host are permitted or denied as per ACL.

Source Net Mask field

The subnet mask of a source network that you want to apply to the ACL so that the packets from the network are permitted or denied as per ACL.

Source Port Range field

The range of ports that you want to apply to the ACL so that the packets from the port range are permitted or denied as per ACL.

Destination IP Address/IPv6 Prefix field

The IP address of the destination host name that you want to apply to the ACL so that the packets to the destination host are forwarded or denied as per ACL.

Destination Net Mask field

The subnet mask of a destination network that you want to apply to the ACL so that the packets to the network are permitted or denied as per ACL.

Destination Port Range field

The range of ports that you want to apply to the ACL so that the packets to the port range are permitted or denied as per ACL.

Step 8

Click Submit.

Adding a MAC ACL Rule or an IP ACL Rule

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, choose the pod.

Step 3

Select the Cisco Nexus 1000 Series switch for HyperV.

Step 4

Click the ACL tab.

Step 5

Choose the ACL entry for which you want to add a MAC or an IP ACL rule.
The actions appear according to the type of the ACL. When you choose MAC type ACL, the Add MAC ACL Rule and Delete MAC ACL Rule actions appear. When you choose IP type ACL, the Add IP ACL Rule and Delete IP ACL Rule actions appear.

Step 6

To add a MAC ACL rule, click Add MAC ACL Rule and complete the following fields:

Name

Description

ACL Name drop-down list

Displays the name of the ACL.

Action drop-down list

Choose permit or deny as the action for the MAC ACL rule.

Source Type field

Choose one of the following as the source type:

- any—To permit or deny any source host or network.

- source MAC address—To permit or deny packets from a specific source MAC address. In the Source MAC address and Source Wildcard bits fields, enter the MAC address and wildcard bits to specify the source host.

Destination Type field

Choose one of the following as the destination type:

- any—To permit or deny any destination host or network.

- Destination MAC address—To permit or deny packets to a specific destination MAC address. In the Destination MAC address and Destination Wildcard bits fields, enter the MAC address and wildcard bits to specify the destination host.

VLAN ID drop-down list

Choose a VLAN ID to which you to need to apply the ACL entry.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 7

To add an IP ACL rule, click Add IP ACL Rule and complete the following fields:

Name

Description

ACL Name drop-down list

Displays the name of the ACL.

Action drop-down list

Choose permit or deny as the action for the IP ACL rule.

Protocol drop-down list

Choose a protocol for communication.

Source Type field

Choose one of the following as the source type:

- any—To permit or deny any source host or network.

- network prefix—To specify the source network prefix. In the Source Network Prefix field, enter the source network prefix.

- network address—To permit or deny packets from a specific source network address. In the Source Network address and Source Wildcard Bits fields, enter the source network address and wildcard bits to specify the source network address range.

- host—To specify the source network prefix. In the Source Host Address field, enter the source host address.

Destination Type field

Choose one of the following as the destination type:

- any—To permit or deny any source host or network.

- network prefix—To specify the source network prefix. In the Destination Network Prefix field, enter the source network prefix.

- network address—To permit or deny packets from a specific source network address. In the Destination Network address and Destination Wildcard Bits fields, enter the source network address and wildcard bits to specify the destination network address range.

- host—To specify the source network prefix. In the Destination Host Address field, enter the destination host address.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 8

Click Submit.

Chapter 16. Configuring Network Address Translation

This chapter contains the following sections:

- About NAT

- Configuring NAT

- Configuring Context NAT

About NAT

Network Address Translation (NAT) enables private IP internetworks that use non-registered IP addresses to connect to the Internet. NAT operates on a router, usually connecting two networks, and translates the private (not globally unique) addresses in the internal network into legal addresses before packets are forwarded onto another network. NAT can be configured to advertise only one address for the entire network to the outside world. This ability provides additional security by effectively hiding the entire internal network behind that one address.

In Cisco UCS Director, you can configure NAT on the following Cisco network devices:

- Cisco ASA 5500 Series firewall

- Cisco Adaptive Security Virtual Appliance (ASAv)

Configuring NAT

Before You Begin

Ensure that the real source and destination IP addresses and mapped source and destination IP addresses are preconfigured on the device.

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.
The summary of the device is displayed.

Step 4

Click Configure NAT.

Step 5

In the Configure NAT dialog box, complete the following fields:

Name

Description

Real Source field

Click Select and choose an object as real source address.

Mapped Source field

Click Select and choose an object as mapped source address.

Real Destination field

Click Select and choose an object as real destination address.

Mapped Destination field

Click Select and choose an object as mapped address.

Step 6

Click Submit.

Configuring Context NAT

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.
The summary of the device is displayed.

Step 4

Click Configure Context NAT.

Step 5

In the Configure Context NAT dialog box, complete the following fields:

Name

Description

Protocol drop-down

Choose TCP or UDP from the list.

Mapped Interface Name drop-down list

Choose an interface name to be mapped for NAT.

Mapped IP Address Destination field

The IP address to be mapped for NAT.

Mapped Port field

The port to be mapped for NAT.

Real Interface Name drop-down

Choose a real interface name for NAT.

Real IP Address field

The real IP address for NAT.

Real Port field

The port for NAT.

Step 6

Click Submit.

Chapter 17. Configuring Quality of Services

This chapter contains the following sections:

- About Quality of Service Policies

- Configuring a QoS Policy

- Deleting a QoS Policy

About Quality of Service Policies

You use the quality of service (QoS) feature to provide the most desirable flow of traffic through a network. QoS allows you to classify the network traffic and prioritize the traffic flow, which helps to avoid traffic congestion in a network. The control of traffic is based on the fields in the packets that flow through the system.

In Cisco UCS Director, you can configure QoS policy on the Cisco Nexus 9300 and 9500 Series switches.

Configuring a QoS Policy

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the down-arrow icon, and choose Configure N9K QOS.

Step 5

In the N9k QOS Configuration dialog box, complete the following fields:

Name

Description

Integrate with UCS QOS Policy check box

Check the check box to integrate the QoS policy that is defined for the Cisco UCS account with the device.

When you are checking this check box, the UCS Account Name drop-down field appears. Choose the QoS policy of the UCS account that you want to integrate with the device.

Configure Platinum Class check box

Check the check box to configure the parameters for the Platinum class and apply the class to the device.

To configure the parameters for the Platinum class, complete the following fields:

- Platinum Class ACL Name drop-down list—Choose the access control list (ACL) name to match packets against when you are configuring a traffic class.

- Platinum Class QOS Group drop-down list—(Optional) Choose the QoS group value to match packets against when you are configuring a traffic class. Values are from 0 to 3.

- Platinum Class COS drop-down list—(Optional) Choose the class of service (CoS) value to match packets against when you are classifying packets into this class. Values are from 0 to 7.

- Platinum Class MTU field—The maximum transmission unit (MTU) value for the class.

Configure Gold Class check box

Check the check box to configure the parameters for the Gold class and apply the class to the device.

To configure the parameters for the Gold class, complete the following fields:

- Gold Class ACL Name drop-down list—Choose the ACL name to match packets against when you are configuring a traffic class.

- Gold Class QOS Group drop-down list—(Optional) Choose the QoS group value to match packets against when you are configuring a traffic class. Values are from 0 to 3.

- Gold Class BW Percentage drop-down list—Choose the guaranteed percentage of interface bandwidth that is allocated to this class.

- Gold Class COS drop-down list—(Optional) Choose the CoS value to match packets against when you are classifying packets into this class. Values are from 0 to 7.

- Gold Class MTU field—The MTU value for the class.

Configure Silver Class check box

Check the check box to configure the parameters for the Silver class and apply the class to the device.

To configure the parameters for the Silver class, complete the following fields:

- Silver Class ACL Name drop-down list—Choose the ACL name to match packets against when you are configuring a traffic class.

- Silver Class QOS Group drop-down list—(Optional) Choose the QoS group value to match packets against when you are configuring a traffic class. Values are from 0 to 3.

- Silver Class BW Percentage drop-down list—Choose the guaranteed percentage of interface bandwidth allocated to this class.

- Silver Class COS drop-down list—(Optional) Choose the CoS value to match packets against when you are classifying packets into this class. Values are from 0 to 7.

- Silver Class MTU field—The MTU value for the class.

Configure Default Class check box

Check the check box to configure the parameters for the Default class and apply the class to the device.

To configure the parameters for the Default class, complete the following field:

- Default Class BW Percentage drop-down list—Choose the guaranteed percentage of interface bandwidth that is allocated to this class.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Request Approval check box

Check the check box to request for approval to deliver commands to the device.

Step 6

Click Submit.

Deleting a QoS Policy

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the down-arrow icon, and choose Delete N9K QOS.

Step 5

In the N9k QOS Deletion dialog box, uncheck the check box to remove the corresponding class configuration from the QoS policy.

Step 6

Uncheck the Copy Running configuration to Startup configuration check box to avoid copying the running configuration to the startup configuration.

Step 7

Uncheck the Request Approval check box to deliver commands to the device without approval.

Step 8

Click Submit.

Chapter 18. Managing Service Policies

This chapter contains the following sections:

- About Service Policies

- Updating a Service Policy

About Service Policies

A service policy is defined to apply multiple actions to an interface. The service policy provides the following two policy-map configuration modes:

- qos—Classification mode. This is the default mode. The input QoS policy is applied to incoming traffic on an Ethernet interface for classification.

- queuing—Queuing mode. The output policy is applied to all outgoing traffic that matches the specified class.

In Cisco UCS Director, you can configure service policies on the following Cisco network devices:

- Cisco Nexus 1000 Series switches

- Cisco Nexus 3000 Series switches

- Cisco Nexus 9300 and 9500 Series switches

Updating a Service Policy

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Choose the network device to be configured.

Step 4

Click the QOS Policy Maps tab.

Step 5

Select the service policy map to be updated.

Step 6

Click Update Service Policy.

Step 7

In the Update Service Policy dialog box, complete the following fields:

Name

Description

Select Interface field

Click Select and choose the interface to which you want to apply the service policy.

Service Policy type drop-down list

Choose one of the following as the policy type:

- qos

- queuing

Service Policy direction field

The direction in which the service policy is applied based on the selected policy type:

- input—Appears when qos is selected as the policy type. The input keyword specifies that this policy map must be applied to traffic received on an interface.

- output—Appears when queuing is selected as the policy type. The output keyword specifies that this policy map should be applied to traffic transmitted from an interface.

Select Policy Map field

The policy map to be updated.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 8

Click Submit.

Chapter 19. Managing Trunks

This chapter contains the following sections:

- About Trunks

- Configuring a Trunk

- Updating a Trunk

About Trunks

VLAN trunks reduce networking costs by reducing the need for expensive physical connections and conserving the number of ports used on switches. The trunk connection can be passed between two switches or between a switch and a computer. Ethernet interfaces can be configured either as access ports or a trunk port, as follows:

- An access port can have only one VLAN configured on the interface; it can carry traffic for only one VLAN.

- A trunk port can have two or more VLANs configured on the interface; it can carry traffic for several VLANs simultaneously.

In Cisco UCS Director, you can manage trunks on the following Cisco network devices:

- Cisco Nexus 1000 and 1110 Series switches

- Cisco Nexus 3000 Series switches

- Cisco Nexus 5000, 5500, and 5672 Series switches

- Cisco Nexus 6000 Series switches

- Cisco Nexus 7000 Series switches

- Cisco Nexus 9300 and 9500 Series switches

- Cisco MDS 9100 Series switches

- Cisco MDS 9500 Series switches

- Cisco MDS 9700 Series switches

- Cisco IOS Devices

Note

For more detailed information about managing trunks and configuration guidelines for managing trunks, see the Cisco NX-OS Software Configuration Guides.

Configuring a Trunk

You can configure an Ethernet port as a trunk port; a trunk port transmits untagged packets for the native VLAN plus encapsulated, tagged packets for multiple VLANs.

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the Interfaces tab.

Step 5

Click Configure Trunk.
Choose the interface on which the trunk needs to be configured.

Step 6

In the Configure Trunk dialog box, complete the following fields:

Name

Description

Port Name field

The name of port on which the trunk needs to be configured.

Description

Optionally enter a description for the trunk configuration.

Native VLAN ID drop-down list

Choose the native VLAN ID to use. The default native VLAN ID is default [1].

Allowed VLANs field

Click Select. In the Select Items dialog box, check the VLAN(s) that are allowed on this trunk port.

STP Port Type drop-down list

Choose one of the following: Edge trunk, Network, or Normal.

Note:
The STP Port Type field does not appear when you choose:

- a Cisco Nexus 1000V device

- a Cisco Nexus 7000 Series switch for storage virtual device context (VDC)

- a Cisco MDS 9100, 9500, or 9700 Series switch

Port Channel

Optionally, choose the channel group to which the port has to be assigned. The default channel group mode is active.

MTU

Optionally, type the MTU range. The MTU range can be between 1500 to 9216.

Copy Running configuration to Startup configuration check box

Check the box to copy the running trunk configuration to the startup configuration.

Step 7

Click Submit.

Updating a Trunk

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the Interfaces tab.
Select the port on which the trunk needs to be updated.

Step 5

Click Update Trunk.

Step 6

In the Trunk Configuration dialog box, complete the following fields:

Name

Description

Port Name button

The name of port on which the trunk needs to be updated is displayed.

Action drop-down list

Choose the relevant action (Add, or Remove).

Select VLANs field

Click Select. In the Select Items dialog box, choose the appropriate VLANs. Click Select.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running trunk configuration to the startup configuration.

Step 7

Click Submit.

Chapter 20. Managing Virtual Fibre Channels

This chapter contains the following sections:

- About VFCs

- Creating a VFC

- Associating a VFC

About VFCs

Fibre Channel over Ethernet (FCoE) allows Fibre Channel and Ethernet traffic to be carried on the same physical Ethernet connection between the switch and the servers.

The Fibre Channel portion of FCoE is configured as a virtual Fibre Channel (VFC) interface. Logical Fibre Channel features (such as interface mode) can be configured on VFC interfaces.

Before you can use a VFC interface, it must be bound to a physical Ethernet interface that is directly connected to a converged network adapter (CNA). The CNA makes the connection to the Fibre Channel Forwarder (FCF) over a virtual port channel (vPC).

The following switch port modes are used to bind the VFC interface:

- Virtual fabric (VF) port—Connects to a peripheral device (host or disk) operating as an N port. A VF port can be attached to only one N port.

- Virtual expansion (VE) port—Acts as an expansion port in an FCoE network. VE ports can connect multiple FCoE switches in the network. You can bind a VE port to a physical Ethernet port or a port channel.

In Cisco UCS Director, VFC configuration is supported on the following Cisco network devices:

- Cisco Nexus 3000 Series switches

- Cisco Nexus 5000, 5500, and 5672 Series switches

- Cisco Nexus 7000 Series switches

- Cisco MDS 9100 Series switches

- Cisco MDS 9500 Series switches

- Cisco MDS 9700 Series switches

Note

For more detailed information about VFCs and configuration guidelines for VFCs, see the Cisco NX-OS Software Configuration Guides.

Creating a VFC

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, choose the pod.

Step 3

Click the Managed Network Elements tab.

Step 4

Select the network device to be configured.

Step 5

Click the down-arrow icon, and choose Create VFC.
Alternately, choose the device from the expanded pod and click Create VFC on the Summary tab.

Step 6

In the Create Vfc dialog box, complete the following fields:

Name

Description

VFC ID field

The VFC ID within the valid range from 1 to 8192. The VFC ID creates a VFC interface.

Select Port Select button

Click Select. In the Select dialog box, choose the port for this VFC and click Select.

Switch Port Mode drop-down list

Choose the switch port mode (E or F). E is for virtual expansion (VE) port. F is for virtual fabric (VF) port. The default is F mode.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 7

Click Submit.

Associating a VFC

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, choose the pod.

Step 3

Click the Managed Network Elements tab.

Step 4

Select the network device to be configured.

Step 5

Click the down-arrow icon, and choose Associate VFC.
Alternately, choose the device from the expanded pod and click Associate VFC on the Summary tab.

Step 6

In the Associate Vfc dialog box, complete the following fields:

Name

Description

VFC Id Select button

Click Select. In the Select dialog box, choose the VFC ID and click Select.

VSAN Id Select button

Click Select to choose the VSAN ID that is associated with this VFC.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running VLAN configuration to the startup configuration.

Step 7

Click Submit.

Chapter 21. Managing VLANs

This chapter contains the following sections:

- About VLANs

- Creating a VLAN

- Assigning a VLAN to a User Group

- Unassigning a VLAN from a User Group

- Configuring a Private VLAN Port

- Creating a Private Primary and Secondary VLAN

- Associating a Private Primary and Secondary VLAN

- Disassociating a Private VLAN

- Removing a Private VLAN Port

- Deleting a Private VLAN

- Deleting a VLAN

About VLANs

A VLAN is a group of devices on one or more LANs that are configured so that they can communicate as if they were attached to the same wire, when they are located on a number of different LAN segments. Because VLANs are based on logical instead of physical connections, they are flexible.

In Cisco UCS Director, you can configure VLANs on the following Cisco network devices:

- Cisco Nexus 1000 and 1110 Series switches

- Cisco Nexus 3000 Series switches

- Cisco Nexus 5000, 5500, and 5672 Series switches

- Cisco Nexus 6000 Series switches

- Cisco Nexus 7000 Series switches

- Cisco Nexus 9300 and 9500 Series switches

Note

For more detailed information about VLANs and configuration guidelines for VLANs, see the Cisco NX-OS Software Configuration Guides.

Creating a VLAN

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the VLANs tab.

Step 5

Click Create VLAN.

Step 6

In the Vlan Parameters dialog box, complete the following fields:

Name

Description

VLAN ID field

The VLAN ID within the valid range.

VLAN Name field

The VLAN name.

No Shutdown check box

Check this box to make sure that the ports associated to the VLAN are not shut down when the VLAN is deleted.

Copy Running configuration to Startup configuration check box

Check this box to copy the running VLAN configuration to the startup configuration.

Step 7

Click Submit.

Assigning a VLAN to a User Group

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the VLANs tab.

Step 5

Select the VLAN to be assigned to a user group.

Step 6

Click Assign Group.

Step 7

In the Select Group dialog box, complete the following fields:

Name

Description

Assign To Users check box

Check the check box to assign the VLAN to users in a group.

Group drop-down list

Choose the group from the list.

Label field

The label for the VLAN that is assigned to a user group.

Step 8

Click Submit.

Unassigning a VLAN from a User Group

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the VLANs tab.

Step 5

Select the VLAN that you need to unassign from a user group.

Step 6

Click UnAssign Group.

Step 7

In the UnAssign VLAN from Group dialog box, complete the following fields:

Name

Description

VLAN ID field

The ID of the VLAN that you need to unassign from the group.

Comment field

The comment for unsigning the VLAN from the user group.

Step 8

Click Submit.

Configuring a Private VLAN Port

You can associate a private VLAN ID as primary and another private VLAN ID as secondary.

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the Private VLANs tab.

Step 5

Click Configure Private VLAN Port.

Step 6

In the Configure Private VLAN Port dialog box, complete the following fields:

Name

Description

Select Port drop-down list

Choose a port on which the VLAN needs to be configured.

Type field

Choose one of the following as the port type for VLAN:

- host

- promiscuous

Primary VLAN ID drop-down list

Choose the primary VLAN ID number.

Secondary VLAN ID field

Choose the VLAN ID number to associate as a secondary VLAN.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration. Uncheck the check box if you do not want to copy the running configuration.

Step 7

Click Submit.

Creating a Private Primary and Secondary VLAN

A private VLAN domain has only one primary VLAN. Each port in a private VLAN domain is a member of the primary VLAN; the primary VLAN is the entire private VLAN domain. Secondary VLANs provide isolation between ports within the same private VLAN domain. The two types of secondary VLANs within a primary VLAN are as follows:

- Isolated VLANs—Ports within an isolated VLAN that cannot communicate directly with each other at the Layer 2 level.

- Community VLANs—Ports within a community VLAN that can communicate with each other but cannot communicate with ports in other community VLANs or in any isolated VLANs at the Layer 2 level.

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the Private VLANs tab.

Step 5

Click Create Private VLAN.

Step 6

In the Create Private VLAN dialog box, complete the following fields:

Name

Description

VLAN ID field

The VLAN ID number that you choose within the valid range for the private VLAN.

Private VLAN Type drop-down list

Choose Primary to make this VLAN the primary VLAN.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 7

Click Submit to create a private VLAN.

Step 8

In the Private VLANs tab, click Create Private VLAN.

Step 9

In the Create Private VLAN dialog box, complete the following fields:

Name

Description

VLAN ID field

The VLAN ID number that you choose within the valid range for the private VLAN.

Private VLAN Type drop-down list

Choose either the Community or Isolated option to make this private VLAN the secondary VLAN within the same private VLAN domain.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 10

Click Submit.

Associating a Private Primary and Secondary VLAN

You can associate a private VLAN ID as primary and another private VLAN ID as secondary.

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the Private VLANs tab.

Step 5

Click Associate Private VLAN.

Step 6

In the Associate Private VLAN dialog box, complete the following fields:

Name

Description

Primary VLAN ID field

The primary VLAN ID number.

Action drop-down list

Choose add to create the association to the primary VLAN or remove to cancel an existing association to the primary VLAN.

Secondary VLAN ID drop-down list

Choose the VLAN ID number to associate as a secondary VLAN.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running port profile configuration to the startup configuration. Uncheck the check box if you do not want to copy the running configuration.

Step 7

Click Submit.

Disassociating a Private VLAN

You can remove the association of primary VLAN from the secondary VLAN.

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the Private VLANs tab.

Step 5

Choose a private VLAN from the Private VLANs table.

Step 6

From the drop-down icon at the top right of the table, choose Delete Associate Private VLAN.

Step 7

In the Delete Associate Private VLAN dialog box, check the Copy Running configuration to Startup configuration check box to copy the running configuration to the startup configuration. Uncheck the check box if you do not want to copy the running configuration.

Step 8

Click Submit.

Removing a Private VLAN Port

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the Private VLANs tab.

Step 5

From the drop-down icon at the top right of the table, choose Remove Private VLAN Port.

Step 6

In the Remove Private VLAN Port dialog box, complete the following fields:

Name

Description

Select Port drop-down list

Choose a port from which the private VLAN needs to be removed.

Type field

Choose one of the following as the port type for VLAN:

- host

- promiscuous

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration. Uncheck the check box if you do not want to copy the running configuration.

Step 7

Click Submit.

Deleting a Private VLAN

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the Private VLANs tab.

Step 5

Choose a private VLAN from the Private VLANs table.

Step 6

From the drop-down icon at the top right of the table, choose Delete Private VLAN.

Step 7

In the Delete Private VLAN dialog box, choose Primary or Secondary as the VLAN type.

Step 8

Check the Copy Running configuration to Startup configuration check box to copy the running configuration to the startup configuration. Uncheck the check box if you do not want to copy the running configuration.

Step 9

Click Submit.

Deleting a VLAN

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device for which the VLAN needs to be deleted.

Step 4

Click the VLANs tab.

Step 5

Select the VLAN to be deleted.

Step 6

Click Delete VLAN.
The Delete VLAN dialog box appears to confirm deletion of VLAN.

Step 7

Check the Copy Running configuration to Startup configuration check box to copy the VLAN configuration to the startup configuration.

Step 8

Click Delete.

Chapter 22. Managing Virtual Port Channels

This chapter contains the following sections:

- About vPCs

- Configuring a vPC Domain

- Configuring a vPC Port Channel

- Removing a vPC

About vPCs

A virtual port channel (vPC) allows links that are physically connected to two different Cisco network devices to appear as a single port channel to a third device, such as a Fabric Extender, a switch, server, or any other networking device. A vPC can provide Layer 2 multipathing, which allows you to create redundancy by increasing bandwidth, enabling multiple parallel paths between nodes and load-balancing traffic where alternative paths exist.

In Cisco UCS Director, you can manage vPCs on the following Cisco network devices:

- Cisco Nexus 3000 Series switches

- Cisco Nexus 5000, 5500, and 5672 Series switches

- Cisco Nexus 9300 and 9500 Series switches

Note

For more detailed information about vPCs and configuration guidelines for vPCs, see the Cisco NX-OS Software Configuration Guides.

Configuring a vPC Domain

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the VPC Info tab.

Step 5

Click Configure VPC Domain.

Step 6

In the Configure vPC Domain dialog box, complete the following fields:

Name

Description

Domain ID field

The virtual port channel (vPC) domain ID used to create a vPC domain.

Source Management IP Address field

The IP address for source management.

Destination Management IP Address field

The IP address for destination management.

Role Priority field

The role priority within the valid range for this vPC switch. The default value is 32667. The switch with a lower priority is elected as the vPC primary switch. If the peer link fails, vPC peer detects whether the peer switch is alive through the vPC peer keepalive link. If the vPC primary switch is alive, the vPC secondary switch suspends its vPC member ports to prevent potential looping while the vPC primary switch keeps all its vPC member ports active.

System Priority field

The system priority within the valid range for the specified vPC domain. The default value is 32667. You should manually configure the vPC system priority when you are running the Link Aggregation Control Protocol (LACP) to help ensure that the vPC peer devices are the primary devices on LACP. When you manually configure the system priority, make sure that you configure the same priority value on both vPC peer devices. If these values do not match, then the vPC is not activated.

Delay Restore field

Specify the time (in number of seconds) to delay bringing up the restored vPC peer device. The range is from 1 to 3600.

Peer Gateway check box

Check this box to enable Layer 3 forwarding for packets destined to the gateway MAC address of the virtual Port Channel (vPC).

Auto Recovery check box

Check this box to enable virtual PortChannel (vPC) auto-recovery feature on the network device.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 7

Click Submit.

Configuring a vPC Port Channel

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the VPC Info tab.

Step 5

Click the down-arrow icon, and choose Configure VPC PortChannel.

Step 6

In the Configure vPC PortChannel dialog box, complete the following fields:

Name

Description

Select Port Channel Name field

Click Select. In the Select dialog box, choose the port channel and click Select.

VPC Peer Link check box

Check the check box if you want to configure the port channel as a vPC peer link for this device.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 7

Click Submit.

Removing a vPC

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the VPC Info tab.

Step 5

Click Remove VPC PortChannel.

Step 6

In the Remove VPC PortChannel dialog box, complete the following fields:

Name

Description

Select Port Channel Name field

Click Select. In the Select dialog box, choose the virtual Port Channel (vPC) and click Select.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 7

Click Submit.

Chapter 23. Managing SAN Zones and SAN Zonesets

This chapter contains the following sections:

- About SAN Zone and Zonesets

- About Smart Zoning

- Creating a SAN Zone

- Enabling Smart Zoning

- Adding a Member to a SAN Zone

- Deleting a SAN Zone

- Creating a SAN Zoneset

- Adding a Member to a SAN Zoneset

- Deleting a SAN Zoneset

About SAN Zone and Zonesets

A zone is a collection of ports that can communicate between them over the SAN. We recommend defining a zone per initiator and target, and deploy multiple small zones, rather than having larger zones defined as they consume more resources. A Zoneset is a collection of zones that define the zoning configuration applied to a VSAN. There can be only one active zoneset per VSAN, but there can be multiple zonesets configured in a switch.

Zoning configuration is based on the following characteristics:

- Enhanced Zoning is enabled for automatic full zoneset distribution and synchronization, and preventing multiple administrators from modifying a VSAN zoneset at the same time. We recommend using enhanced zoning for all configured VSANs in the SAN.

- Device-aliases are used to configure zoning, as they are independent of the zoning database and can provide naming resolution to applications beyond the zone server.

In Cisco UCS Director, you can configure SAN Zone and Zonesets on the following Cisco network devices:

- Cisco Nexus 5000, 5500, and 5672 Series switches

- Cisco Nexus 7000 Series switches

- Cisco MDS 9100 Series switches

- Cisco MDS 9500 Series switches

- Cisco MDS 9700 Series switches

About Smart Zoning

Smart zoning is supported on network devices that run Cisco NX-OS. Smart zoning, when enabled on the device, allows you to add device types as labels to members. This labeling helps to reduce the volume of Ternary Content-Addressable Memory (TCAM) entries that are created for Access Control List (ACL). The keywords or device type values to be used are init, target, or both. Smart zoning programs TCAMs with entries that connect the initiator and the target. You need not manually edit all zones with the keywords. The conversion utility of smart zoning uses the Fibre Channel Name Server (FCNS) data to add these keywords to the members. For more information on smart zoning, refer to Smart Zoning.

In Cisco UCS Director, you can enable smart zoning on the following Cisco network devices.

- Cisco Nexus 5000 Series switches

- Cisco Nexus 7000 Series switches

- Cisco MDS 9100 Series switches

- Cisco MDS 9500 Series switches

- Cisco MDS 9700 Series switches

Creating a SAN Zone

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the SAN Zones tab.

Step 5

Click Create SAN Zone.

Step 6

In the Create SAN Zone dialog box, complete the following fields:

Name

Description

Zone Name field

The name of the zone.

VSAN Id field

Click Select. In the Select dialog box, choose a VSAN ID.

Commit San Zone check box

Check this check box to enable the enhanced zoning.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 7

Click Submit.

Enabling Smart Zoning

Smart zone is enabled at VSAN level. You can choose to disable the smart zoning at zone level. However, you cannot have smart zone at zone level without enabling the smart zone at VSAN level.

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the required device for which you want to enable smart zoning.
Ensure that the selected device runs NX-OS. To find the OS type of the device, click the Summary tab. Look for the OS Type value in the Overview box.

Step 4

Click the VSAN tab.

Step 5

From the VSAN list, click the VSAN that you want to enable smart zoning for.

Step 6

Click Enable SmartZone. This button appears only for devices that run Cisco NX-OS.

Step 7

In the Enable SmartZone dialog box, check the Copy Running configuration to Startup configuration check box to copy the running configuration to the startup configuration.

Step 8

Click Submit. The smart zoning is enabled on the VSAN.

Adding a Member to a SAN Zone

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the SAN Zones tab.

Step 5

Select the SAN zone to which you want to add a member.

Step 6

Click Add SAN Zone Member.

Step 7

In the Add Member to SAN Zone dialog box, complete the following fields:

Name

Description

SAN Zone field

The name of the zone.

Type drop-down list

Choose one of the following as the member type: pWWN,FCALIAS, or DeviceAlias.

Device Type drop-down list.

Note:
This field appears only when the smart zoning is enabled for the zone.

Choose one of the following as device type: initiator, target, or both.
Note:
This field disappears on selection of FCALIAS as the member type.

Member field

This field appears on selection of pWWN as the member type. The member that you want to add to the SAN zone.

FCALIAS field

This field appears on selection of FCALIAS as the member type. Click Select and choose one or more FC Aliases.

Device Alias Name field

This field appears on selection of DeviceAlias as the member type. Click Select and choose one or more Device Aliases.

Leverage Smart Zoning check box

Check this check box to use the smart zoning feature on the device. Ensure that smart zoning is supported for the device and is enabled in the VSAN. For more information on enabling smartzone, refer Enabling Smart Zoning. This field does not appear if the member type is FCALIAS.

Commit San Zone check box

Check this check box to enable the enhanced zoning.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 8

Click Submit.

Deleting a SAN Zone

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the SAN Zones tab.

Step 5

Select the SAN zone that you want to delete.

Step 6

Click Delete SAN Zone.

Step 7

In the Delete SAN Zone dialog box, complete the following fields:

Name

Description

Zone Name field

The name of the zone.

Commit San Zone check box

Check this check box to enable the enhanced zoning.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 8

Click Submit.

Creating a SAN Zoneset

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the SAN Zonesets tab.

Step 5

Click Create SAN Zone Set.

Step 6

In the Create SAN Zone Set dialog box, complete the following fields:

Name

Description

Zone Set Name field

The name of the SAN zoneset.

VSAN Id field

Click Select. In the Select dialog box, choose a VSAN ID.

Commit San Zone check box

Check this check box to enable the enhanced zoning.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 7

Click Submit.

Note

During the execution of the activate SAN zoneset workflow, if the Activate check box of the zoneset is enabled, the zoneset is deactivated during rollback and removed from the Active list. Once the zoneset is removed, the device restarts the zone merge process.

If the Disable Rollback check box is enabled, the task is not listed or allowed to roll back the activated zoneset.

Adding a Member to a SAN Zoneset

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the SAN Zonesets tab.

Step 5

Select the SAN zoneset to which you want to add a member.

Step 6

Click Add SAN Zone Set Member.

Step 7

In the Add SAN Zone to Set dialog box, complete the following fields:

Name

Description

SAN Zone Set field

The name of the SAN zoneset.

SAN Zone field

Click Select and choose the zone members.

Commit San Zone check box

Check this check box to enable the enhanced zoning.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 8

Click Submit.

Deleting a SAN Zoneset

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the SAN Zonesets tab.

Step 5

Select the SAN zoneset that you want to delete.

Step 6

Click Delete SAN Zone Set.

Step 7

In the Delete SAN Zone Set dialog box, complete the following fields:

Name

Description

SAN Zone Set field

The name of the SAN zoneset.

Commit San Zone check box

Check this check box to enable the enhanced zoning.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 8

Click Submit.

Chapter 24. Managing Virtual Storage Area Networks

This chapter contains the following sections:

- About VSANs

- Creating a VSAN

- Deleting a VSAN

About VSANs

A virtual storage area network (VSAN) is a dedicated virtual network that interconnects hosts and storage devices primarily to exchange SCSI traffic. Physical links in storage are networks (SANs) are used to make these interconnections. A set of protocols run over the SAN to handle routing, naming, and zoning. You can design multiple SANs with different topologies.

With VSANs, you can build a single topology that contains switches, links, and one or more VSANs. Each VSAN in this topology has the same behavior and property of a SAN.

In Cisco UCS Director, you can configure VSANs on the following Cisco network devices:

- Cisco Nexus 3000 Series switches

- Cisco Nexus 5000, 5500, and 5672 Series switches

- Cisco Nexus 7000 Series switches

- Cisco Nexus 9300 and 9500 Series switches

- Cisco MDS 9100 Series switches

- Cisco MDS 9500 Series switches

- Cisco MDS 9700 Series switches

Note

For more detailed information about VSANs and configuration guidelines for VSANs, see the Cisco NX-OS Software Configuration Guides.

Creating a VSAN

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the VSANs tab.

Step 5

Click Create VSAN.

Step 6

In the Create VSAN dialog box, complete the following fields:

Name

Description

VSAN ID field

The virtual storage area network (VSAN) ID number within the valid range for this device.

VSAN Name field

The VSAN name.

Enhance check box

Check the check box to enable Enhanced Zoning to perform all configurations using a single configuration session. Enhanced zone enforces and exchanges the default zone setting throughout the fabric.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running VSAN configuration to the startup configuration.

Step 7

Click Submit.

Deleting a VSAN

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the VSANs tab.

Step 5

Select the VSAN to be deleted.

Step 6

Click Delete VSAN.

Step 7

In the Delete VSAN dialog box, complete the following fields:

Name

Description

VSAN ID drop-down list

The virtual storage area network (VSAN) ID that you selected for deletion.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running VSAN configuration to the startup configuration.

Step 8

Click Submit.

Chapter 25. Managing Virtual Extensible LANs

This chapter contains the following sections:

- About VXLANs

- Creating a VXLAN

- Encapsulating a VXLAN

- Assigning a VXLAN to a Port Profile

- Unassigning a VXLAN from a Port Profile

- Removing a VXLAN

About VXLANs

A virtual extensible LAN (VXLAN) defines a 24-bit LAN segment identifier to provide segmentation at cloud scale and an architecture that expands cloud deployments with repeatable pods in different Layer 2 (L2) domains. A VXLAN can also enable the migration of virtual machines (VMs) between servers across Layer 3 networks.

A VXLAN creates LAN segments by overlaying the original MAC (L2) frame in IP encapsulation from the VM within the Virtual Ethernet Module (VEM).

Each VEM is assigned an IP address, which is used as the source IP address when MAC frames are encapsulated and sent over the network. You can have multiple VMkernel NICs (also referred to as virtual network adapters or vmknics) per VEM that are used as sources for this encapsulated traffic. The encapsulation carries the 24-bit VXLAN identifier that scopes the MAC address of the payload frame.

Note

VMkernel NICs are used to manage physical NICs (pNICs) on a host server to connect the virtual network to the physical network.

The connected VXLAN is indicated within the port profile configuration of the virtual network interface card (vNIC) and is applied when the VM connects. Each VXLAN uses an assigned IP multicast group to carry broadcast traffic within the VXLAN segment.

In Cisco UCS Director, you can configure VXLANs on the Cisco Nexus 1000 switch.

Note

For more detailed information about VXLANs and configuration guidelines for VXLANs, see the Cisco NX-OS Software Configuration Guides.

Creating a VXLAN

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the VXLAN Table tab.

Step 5

Click Create VXLAN.
Alternately, you can choose the command from the drop-down icon.

Step 6

In the Create VXLAN dialog box, complete the following fields:

Name

Description

Bridge Name field

The bridge domain name for the virtual extensible LAN (VXLAN).

VXLAN Id field

The VXLAN ID number within the valid range.

Mode Unicast check box

Check the check box to enable a unicast-only VXLAN.

With a unicast-only VXLAN, the Virtual Supervisor Module (VSM) knows which VEMs have Virtual Machines (VMs) attached to a particular VXLAN segment and distributes that information to all Virtual Ethernet Modules (VEMs). Each VEM receives a per-VXLAN list of destination IP addresses to use for flooding purposes.

Distribution learning MAC check box

Check the check box to distribution learning for MAC addressing.

MAC learning enables the distribution of the MAC addresses learned on one line card to the other line cards.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running VXLAN configuration to the startup configuration.

Step 7

Click Submit.

Encapsulating a VXLAN

You can configure VMkernel NICs (vmknics) for virtual extensible LAN (VXLAN) encapsulation by running the following procedure.

Note

Identify a VLAN to be used for transporting VXLAN encapsulated traffic and ensure that it is configured on the uplink port profile for all VEMs on which the VXLAN can be configured.

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the VXLAN Table tab.

Step 5

Select the VXLAN domain to be encapsulated.

Step 6

Click Encapsulate VXLAN.
Alternately, you can choose the command from the drop-down icon.

Step 7

In the Encapsulate VXLAN dialog box, complete the following fields:

Name

Description

Select Port Profile drop-down list

Choose the port profile that you want to use for the VXLAN.

VLAN ID Select button

Click Select. In the Select dialog box, check the check box for the VLAN ID that you want encapsulated and click Select.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running VXLAN configuration to the startup configuration.

Step 8

Click Submit.

Assigning a VXLAN to a Port Profile

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the VXLAN Table tab.

Step 5

Select the VXLAN domain to be assigned to a port profile.

Step 6

Click Assign VXLAN to a Port Profile.
Alternately, you can choose the command from the drop-down icon.

Step 7

In the Assign VXLAN dialog box, complete the following fields:

Name

Description

Select Port Profile drop-down list

Choose the port profile name for the VXLAN assignment.
Note:
Ensure that the access VLAN is enabled for a VXLAN capability in the port profile that you are using for the VXLAN. For more information, see Creating a Port Profile.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running VXLAN configuration to the startup configuration.

Step 8

Click Submit.

Unassigning a VXLAN from a Port Profile

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the VXLAN Table tab.

Step 5

Select the VXLAN domain to be unassigned from a port profile.

Step 6

Click Unassign VXLAN from Port Profile.
Alternatively, you can choose the command from the drop-down icon.

Step 7

In the Unassign VXLAN dialog box, complete the following fields:

Name

Description

Select Port Profile drop-down list

Choose the port profile from which you need to unassign the VXLAN.

Copy Running configuration to Startup configuration check box

Check the check box to copy the running VXLAN configuration to the startup configuration.

Step 8

Click Submit.

Removing a VXLAN

Note

Executing this procedure moves the ports to the default VLAN.

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Select the network device to be configured.

Step 4

Click the VXLAN Table tab.

Step 5

Select the VXLAN to be removed.

Step 6

Click Remove VXLAN.

Step 7

In the Remove VXLAN dialog box, complete the following fields:

Name

Description

Copy Running configuration to Startup configuration check box

Check the check box to copy the running VLAN configuration to the startup configuration.

Step 8

Click Submit.

Chapter 26. Configuring ASA Context

This chapter contains the following sections:

- About ASA Context

- Creating an ASA Context

About ASA Context

You can partition a single ASA into multiple virtual devices, known as security contexts. Each context acts as an independent device, with its own security policy, interfaces, and administrators. Multiple contexts are similar to having multiple standalone devices.

In Cisco UCS Director, ASA context configuration is supported on the following Cisco network device:

- Cisco ASA 5500 Series firewall

Creating an ASA Context

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, expand the pod.

Step 3

Choose the network device to be configured.

Step 4

Click the ASA Context tab.

Step 5

Click Create Asa Context.

Step 6

In the Create Asa Context dialog box, complete the following fields:

Name

Description

Context Name field

The name of the security context.

Context Description field

The description of the security context.

File Name field

The name of the security context configuration.

OutSide Interface Name drop-down list

Choose the outside interface name for the security context.

Inside Interfaces field

Click Select and choose the inside interfaces for the security context.

Mode drop-down list

Choose one of the following as the firewall mode for context:

- Routed

- Transparent

Copy Running configuration to Startup configuration check box

Check the check box to copy the running configuration to the startup configuration.

Step 7

Click Submit.

Chapter 27. Configuring the Cisco Nexus 1000V Switch for Microsoft Hyper-V

This chapter contains the following sections:

- About Microsoft System Center Virtual Machine Manager

- About the Cisco Nexus 1000V Switch for the Microsoft Hyper-V Configuration

- Configuring the Cisco Nexus 1000V Switch for Microsoft Hyper-V

- Managing Logical Networks

- Managing Network Segment Pools

- Managing IP Pool Templates

- Managing Network Segments

- Managing Network Uplinks

- Managing VXLAN Range

- Managing Tenant VRF

About Microsoft System Center Virtual Machine Manager

Microsoft System Center Virtual Machine Manager (SCVMM) 2012 SP1 is a comprehensive IT infrastructure, virtualization, and cloud management platform. With this platform, you can manage your applications and services across multiple hypervisors and across public, hosted, and private cloud infrastructures to deliver flexible and cost-effective IT services. Microsoft SCVMM allows you, as the administrator, to configure and manage the servers, the network, and the storage resources.

Microsoft SCVMM 2012 SP1 introduces the following constructs to model and configure the networks on the Hyper-V servers:

- Logical network

- Network site

- VM network

- VM subnet

- IP pool

- Uplink profile

- Port classification

- Logical switch

About the Cisco Nexus 1000V Switch for the Microsoft Hyper-V Configuration

Microsoft SCVMM SP1 models the physical networks as a fabric. The Cisco Nexus 1000V has introduced a capability to configure and edit the following new objects based on Microsoft SCVMM SP1 network object model:

- Logical networks

- Network segment pools (results in the creation of network sites on virtual machine manager [VMM])

- Network segments (results in the creation of a virtual machine [VM] network and VM subnet)

- IP pools

- Network uplink

Logical Networks and Network Segment Pools

A logical network (for example, Internet or intranet) is a connectivity abstraction that models separate networks managed by an enterprise. A logical network is composed of one or more network segment pools, and each network segment pool is a group of VLANs, IP subnets, or VLAN/IP subnet pairs. The logical network hides the VLANs and IP subnets that make the network from all the users (the VM network administrators, the tenant administrators, and the server administrators) other than the fabric administrator managing the physical fabric.

Network Segments

A network segment is associated with a unique broadcast domain. A network segment facilitates the availability of the network resources to a virtual machine. Microsoft SCVMM uses the VM networks and the VM subnets to provide the isolated virtual machine networks. When the Cisco Nexus 1000V switch is used to manage the virtual network, the VMM administrator creates the VM networks that use external isolation.

As a network administrator, you can create network segment on the Cisco Nexus 1000V switch to provide external isolation. You can provide the isolated networks using the VLANs and the private VLANs.

Note

In the Cisco Nexus 1000V for Microsoft Hyper-V, a VLAN is not created to define a bridge domain. Instead, a network segment is created on a Virtual Supervisor Module (VSM). The VSM provides the switch control and management plane for the Cisco Nexus 1000V switch. Creating a network segment triggers VLANs to be created automatically.

IP Pools

You can assign a range of IP addresses to the hosts and to the virtual machines that are running inside the Microsoft SCVMM-managed environment using an IP pool template. The IP pool template is the address template that is applied to the network segments. When you create an IP pool template for a VM network, you can define a range of IP addresses that are used by the VMs managed by Microsoft SCVMM.

Network Uplink

The uplink network is a combination of an Ethernet port profile and one or more network segment pools. When applied to the physical adapter on a server, the uplink network defines the policy and the VLANs that are allowed on the physical adapter. Each uplink network configured on the VSM is available as an uplink port profile to the Microsoft SCVMM administrator.

Configuring the Cisco Nexus 1000V Switch for Microsoft Hyper-V

Step 1

Create a logical network. For more information about how to create a logical network, see Creating a Logical Network.

Step 2

Create a network segment pool and associate the network segment pool to the logical network. For more information about how to create a network segment pool, see Creating a Network Segment Pool.

Step 3

Create an IP pool template. For more information about how to create an IP pool template, see Creating an IP Pool Template.

Step 4

Create a network segment. For more information about how to create a network segment, see Creating a Network Segment.

Step 5

Create a port profile. For more information about how to create a port profile, see Creating a Port Profile.

Step 6

Create an uplink network. For more information about how to create an uplink network, see Creating an Uplink Network.

Managing Logical Networks

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, choose the pod.

Step 3

In the Managed Network Elements tab, choose the Cisco Nexus 1000V switch to be configured.

Step 4

Click View Details.

Step 5

Click the Logical Network tab. The logical networks created in the Cisco Nexus 1000V switch are displayed. The Logical Network tab provides the following actions:

Action

Description

Refresh

Refreshes the current page.

Favorite

Adds this page to the Favorites tab which displays the page that you go to most often.

Create Logical Network

Creates a logical network in the Cisco Nexus 1000V switch.

When you choose a logical network, the following action appears:

Action

Description

Delete Logical Network

Deletes a logical network.

- Creating a Logical Network

Creating a Logical Network

Step 1

Navigate to the Logical Network tab.
For the procedure to navigate to the Logical Network tab, see Managing Logical Networks.

Step 2

Click Create Logical Network.

Step 3

In the Create Logical Network dialog box, complete the following fields:

Name

Description

Logical Network Name field

The name of the logical network.

Logical Network Description field

The description of the logical network.

No Mode Isolation check box

Check this check box to configure Hyper-V Network Virtualization (HNV) logical network. HNV provides virtual networks (called VM networks) to virtual machines, similar to how server virtualization (a hypervisor) provides virtual machines to the operating system.
Note:
This feature is supported in Nexus 1000v HyperV 5.2(1) SM3(1.1) and later releases.

Copy Running configuration to Startup configuration check box

Check this check box to copy the running configuration to the startup configuration.

Step 4

Click Submit.

Managing Network Segment Pools

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, choose the pod.

Step 3

In the Managed Network Elements tab, choose the Cisco Nexus 1000V switch to be configured.

Step 4

Click View Details.

Step 5

Click the Network Segment Pool tab. The network segment pools available in the Cisco Nexus 1000V switch are displayed. The globally unique identifier (GUID) of the network segment is displayed. The Network Segment Pool tab provides the following actions:

Action

Description

Refresh

Refreshes the current page.

Favorite

Adds this page to the Favorites tab which displays the page that you go to most often.

Create Network Segment Pool

Creates a network segment pool for the Cisco Nexus 1000V switch.

When you choose a network segment pool, the following actions appear:

Action

Description

Delete Network Segment Pool

Deletes a network segment pool.

Update Network Segment Pool

Updates a network segment pool.

- Creating a Network Segment Pool

Creating a Network Segment Pool

Step 1

Navigate to the Network Segment Pool tab.
For more information about how to navigate to the Network Segment Pool tab, see Managing Network Segment Pools.

Step 2

Click Create Network Segment Pool.

Step 3

In the Create Network Segment Pool dialog box, complete the following fields:

Name

Description

Network Segment Pool field

The name of the network segment pool.

Logical Network Name field

Click Select and choose a logical network to which you want to associate the network segment pool.

Segment Type drop-down list

Choose VLAN, VXLAN, or HNV as the segment type to accordingly configure the network segment pool.

Multicast IP field

This field appears when you choose VXLAN as the segment type. The multicast IP address that needs to be assigned to the network segment pool.

Intra Port Communication check box

Check this check box to enable the intra port communication.

Copy Running configuration to Startup configuration check box

Check this check box to copy the running configuration to the startup configuration.

Step 4

Click Submit.

Managing IP Pool Templates

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, choose the pod.

Step 3

In the Managed Network Elements tab, choose the Cisco Nexus 1000V switch to be configured.

Step 4

Click View Details.

Step 5

Click the IP Pool Template tab. The IP pool templates available in the Cisco Nexus 1000V switch are displayed. The IP Pool Template tab provides the following actions:

Action

Description

Refresh

Refreshes the current page.

Favorite

Adds this page to the Favorites tab which displays the page that you go to most often.

Create IP Pool Template

Creates an IP pool template that defines the IP-pool range to be used when virtual machines are deployed on a VLAN-based virtual machine network.

When you choose an IP pool template, the following actions appear:

Action

Description

Delete IP Pool Template

Deletes an IP pool template.

Update IP Pool Template

Updates the IP pool template.

- Creating an IP Pool Template

Creating an IP Pool Template

Step 1

Navigate to the IP Pool Template tab.
For more information about how to navigate to the IP Pool Template tab, see Managing IP Pool Templates.

Step 2

Click Create IP Pool Template.

Step 3

In the Create IP Pool Template dialog box, complete the following fields:

Name

Description

IP Pool Template Name field

The name of the IP pool template.

Description field

The description of the IP pool template.

IP Address From Range field

The first IP address of the IP pool.

IP Address To Range field

The last IP address of the IP pool.

Network Address field

The network address range of the IP pool template.

Network Subnet Mask field

The subnet mask address of the IP pool template.

Default Router field

The gateway IP address of the IP pool template.

DNS Server field

The DNS server IP address of the IP pool template.

DNS Suffix field

The DNS suffix of the IP pool template.

Netbios Name Server field

The IP address of the NetBIOS name server for the IP pool template.

Netbios drop-down list

Choose disabled or enabled.

Copy Running configuration to Startup configuration check box

Check this check box to copy the running configuration to the startup configuration.

Step 4

Click Submit.

Managing Network Segments

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, choose the pod.

Step 3

In the Managed Network Elements tab, choose the Cisco Nexus 1000V switch to be configured.

Step 4

Click View Details.

Step 5

Click the Network Segment tab. The network segments available in the Cisco Nexus 1000V switch are displayed. The Network Segment tab provides the following actions:

Action

Description

Refresh

Refreshes the current page.

Favorite

Adds this page to the Favorites tab which displays the page that you go to most often.

Create Network Segment

Creates a network segment on the Cisco Nexus 1000V switch.

When you choose a network segment, the following actions appear:

Action

Description

Delete Network Segment

Deletes a network segment.

Update Network Segment

Updates a network segment.

Publish Network Segment

Publishes the network segment to SCVMM.

- Creating a Network Segment

Creating a Network Segment

Step 1

Navigate to the Network Segment tab.
For procedure to navigate to the Network Segment tab, see Managing Network Segments.

Step 2

Click Create Network Segment.

Step 3

In the Create Network Segment dialog box, complete the following fields:

Name

Description

Network Segment Name field

The name of the network segment.

Network Segment Description field

The description of the network segment.

Network Segment Type drop-down list

Choose Ethernet or vethernet as the network segment type.

IP Subnet field

The subnet IP address of the network segment.
Note:
This feature is supported in Nexus 1000v HyperV 5.2(1) SM3(1.1) and later releases.

IP Pool Template Name field

Click Select and choose an IP pool template for the network segment.

Network Segment Pool field

Click Select and choose a network segment pool for the network segment.

Tenant VRF field

Click Select and choose a tenant Virtual Routing and Forwarding (VRF) for the network segment. For more information about the tenant VRF, see t_Managing_Tenant_VRF_d261.html.

System Network Segment check box

Check this check box to configure the segment as a system segment.

Type drop-down list

Choose VLAN, PVLAN, or VXLAN as the type for network segment.

VLAN field

This field appears when you choose the type as VLAN in the Type field. The valid VLAN ID of the network segment.

Publish Network Segment check box

Check this check box to publish the network segment to SCVMM.

Publish Network Segment Name field

This field appears when you check the Publish Network Segment check box. The default published name is the same name as the segment name. If you want to publish the segment with a different name, enter the name.

Copy Running configuration to Startup configuration check box

Check this check box to copy the running configuration to the startup configuration.

The following fields appear when you choose the type as PVLAN in the Type field.

Private VLAN Type field

By default, Primary is displayed. Choose Primary or Secondary as the type of private VLAN.

Primary VLAN field

The valid primary VLAN ID of the network segment.

The following fields appear when you choose the private VLAN type as Secondary in the Private VLAN Type field.

Secondary VLAN Type field

Choose Host or Promiscuous as the mode of secondary VLAN.

Host Type drop-down list

This field appears when you choose Host as the type of secondary VLAN. Choose Community or Isolated as the type of host.

Primary VLAN field

The valid primary VLAN ID of the network segment.

Secondary VLAN field

The valid secondary VLAN ID of the network segment.

The following field appears when you choose the type as VXLAN in the Type field.

Bridge Domain ID field

The bridge domain ID of the network segment. The valid bridge domain ID range is from 4097 to 16777215.

Step 4

Click Submit.

Managing Network Uplinks

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, choose the pod.

Step 3

In the Managed Network Elements tab, choose the Cisco Nexus 1000V switch to be configured.

Step 4

Click View Details.

Step 5

Click the Network Uplink tab. The uplink networks available in the Cisco Nexus 1000V switch are displayed. The Network Uplink tab provides the following actions:

Action

Description

Refresh

Refreshes the current page.

Favorite

Adds this page to the Favorites tab which displays the page that you go to most often.

Create Uplink Network

Creates an uplink network.

When you choose an uplink network, the following actions appear:

Action

Description

Inherit Port Profile

Imports the Ethernet port profile that gives the policy for the uplink.

In the Inherit Port Profile Configuration dialog box, complete the following fields:

- Network Uplink—Displays the network uplink.

- Port Profile—Click Select to choose a port profile from which you want to inherit the configuration.

- Copy Running configuration to Startup configuration—Check this check box to copy the running configuration to the startup configuration.

Delete Inherit Port Profile

Removes the inherited policies from a port profile.

Publish Network Uplink

Publishes the network uplink to Microsoft SCVMM.

Delete Uplink Network

Deletes an uplink network.

Update Uplink Network

Updates the uplink network.

- Creating an Uplink Network

Creating an Uplink Network

Step 1

Navigate to the Network Uplink tab.
For more information about how to navigate to the Network Uplink tab, see Managing Network Uplinks.

Step 2

Click Create Uplink Network.

Step 3

In the Create Uplink Network dialog box, complete the following fields:

Name

Description

Network Uplink field

The name of the network segment.

Network Segment Pool field

Click Select and choose a network segment pool.

Port Profile field

Click Select and choose a port profile.

Network Segment field

Click Select and choose a network segment.

System Network Uplink check box

Check this check box to configure the uplink as a system network uplink.

Publish Network Uplink check box

Check this check box to publish the network uplink to SCVMM.

Copy Running configuration to Startup configuration check box

Check this check box to copy the running configuration to the startup configuration.

Step 4

Click Submit.

Managing VXLAN Range

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, choose the pod.

Step 3

In the Managed Network Elements tab, choose the Cisco Nexus 1000V switch to be configured.

Step 4

Click View Details.

Step 5

Click the VXLAN Range tab. The VXLAN ranges available in the Cisco Nexus 1000V switch are displayed. The VXLAN Range tab provides the following actions:

Action

Description

Refresh

Refreshes the current page.

Favorite

Adds this page to the Favorites tab which displays the page that you go to most often.

Configure VXLAN Range

Configures the VXLAN range for the Cisco Nexus 1000V switch.

In the VXLAN Configuration dialog box, complete the following fields:

- Select Device field—Displays the selected device.

- Configure VXLAN check box—Check this check box to configure the VXLAN range.
Note:
Uncheck this check box and execute the Configure VXLAN Range action to unconfigure the VXLAN in the device.

- VXLAN ID field—The VXLAN ID number within the valid range.

- Copy Running configuration to Startup configuration check box—Check this check box to copy the running configuration to the startup configuration.

Managing Tenant VRF

Virtual Routing and Forwarding (VRF) implemented at core and aggregation layers provides per tenant isolation at Layer 3, with separate dedicated per-tenant routing and forwarding tables insuring that no inter-tenant (server to server) traffic within the data center will be allowed, unless explicitly configured.

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, choose the pod.

Step 3

In the Managed Network Elements tab, choose the Cisco Nexus 1000V switch to be configured.

Step 4

Click View Details.

Step 5

Click the Tenant VRF tab. The tenant VRFs available in the Cisco Nexus 1000V switch are displayed. The Tenant VRF tab provides the following actions:

Action

Description

Refresh

Refreshes the current page.

Favorite

Adds this page to the Favorites tab which displays the page that you go to most often.

Create Tenant VRF

Creates a tenant VRF for the Cisco Nexus 1000V switch.

In the Create Tenant VRF dialog box, complete the following fields:

- Tenant VRF Name field—The name of the tenant VRF.

- Description field—The description of the tenant VRF.

- Logical Network Name field—Click Select and choose a logical network.

- Copy Running configuration to Startup configuration check box—Check this check box to copy the running configuration to the startup configuration.

When you choose a tenant VRF, the following action appears:

Action

Description

Delete Tenant VRF

Deletes the tenant VRF.

Chapter 28. Monitoring and Reporting

This chapter contains the following sections:

- About General Reports

- About Detail Reports

- About Cisco ISE

- About the Service Request Details Report

- Exporting an Inventory Report

About General Reports

General reports are available for each network device.

Each report has its own tab, and the tabs are visible when you choose the pod with the network device you want to view or monitor.

You can monitor specific components, including the following:

- VTP status

- Private VLANs

- Layer 2 Neighbors

- Port Profiles

- VM network details

- Host network details

- Virtual Storage Area Networks (VSANs)

- VLANs

Note

You can also see detailed reports for Layer 2 neighbors and private VLANs, which display additional information.

About Detail Reports

Cisco UCS Director displays detail reports for the network devices when you click a pod on the Managed Network Elements tab.

Each report has its own tab, and the tabs are visible when you select a pod with the switch, and click View Details on the Managed Network Elements tab.

Cisco Nexus 1000V Switch

You can view reports for Cisco Nexus 1000V switch components, including the license information and summary status. In addition, you can monitor components, such as the following:

- Configurations

- Modules

- Layer 2 Neighbors

- VXLAN Table

- Interfaces

- Port capabilities

- VLANs

- Private VLANs

- Port profiles

- Port profile encapsulation

- SXP Connection Peers

- Features

- MAC address table

- MAC address table configuration

- QoS class maps

- QoS policy maps

- Service request details

The following tabs appear when you choose a Cisco Nexus 1000V switch that is configured with HyperV:

- ACL

- Logical Network

- Network Segment

- Network Segment Pool

- VXLAN Range

- Tenant VRF

- IP Pool Template

- Network Uplink

Cisco Nexus 5000 and 5500 Series Switches

You can view reports for Cisco Nexus 5000 and 5500 Series components, including the license information and summary status. In addition, you can monitor components, such as the following:

- Configurations

- Modules

- Layer 2 neighbors

- Interfaces

- Port capabilities

- VLANs

- Private VLANs

- Port profiles

- SXP Connection Peers

- HSRP

- VPC information

- VTP status

- Features

- MAC address tables

- MAC address table configuration

- SAN zones

Note

For the VSAN with smart zoning enabled, the data in the Zone Members column is affixed with the device type, within parenthesis. The device type is defined while adding the zone member. The device type could be init, target, both, or blank.

- SAN zonesets

- Fabric login

- FCNS database

- Device alias

- FCAlias

- VSANs

Note

The Smart Zoning column displays whether the VSAN is enabled with smart zoning. If smart zoning for the device is disabled at the zone level, the status is Not Applicable. If smart zoning is disabled at the VSAN level, the status is Disabled.

- QoS class maps

- QoS policy maps

- Service request details

Cisco Nexus 7000 Series Switches

You can view reports for Cisco Nexus 7000 Series components, including the license information and summary status. In addition, you can monitor components, such as the following:

- Configurations

- Modules

- Layer 2 neighbors

- Interfaces

- Port capabilities

- VLANs

- Private VLANs

- Port profiles

- VDC

- SXP Connection Peers

- HSRP

- FCAlias

Note

More reports are available for individual VDCs when they are expanded using the View Details button.

For a storage VDC, the following smart zoning information can be viewed:

- SAN Zones

Note

For the VSAN with smart zoning enabled, the data in the Zone Members column is affixed with the device type, within parenthesis. The device type is defined while adding the zone member. The device type could be init, target, both, or blank.

- VSANs

Note

The Smart Zoning column displays whether the VSAN is enabled with smart zoning. If smart zoning for the device is disabled at the zone level, the status is Not Applicable. If smart zoning is disabled at the VSAN level, the status is Disabled.

- VDC detail

- VDC interfaces

- VPC information

- VTP status

- Features

- MAC address table

- MAC address table configuration

- QoS policy maps

- QoS class maps

- Service request details

Cisco Nexus 9300 and 9500 Series Switches

You can view reports for Cisco Nexus 9300 and 9500 Series switches switch components, including the license information and summary status. In addition, you can monitor components, such as the following:

- Configurations

- Modules

- Layer 2 neighbors

- Interfaces

- Port Capabilities

- VLANs

- Private VLANs

- Port profiles

- VPC information

- VTP Status

- Features

- MAC address table

- MAC address table configuration

- QoS class maps

- QoS policy maps

- Service request details

Cisco MDS 9100, 9500, and 9700 Series Switches

You can view reports for Cisco MDS 9100, 9500, and 9700 Series switch components, including the license information and summary status. In addition, you can monitor the following components:

- Configurations

- Modules

- L2 Neighbors

- Interfaces

- Port Capabilities

- VLANs

- Features

- SAN Zones

Note

For the VSAN with smart zoning enabled, the data in the Zone Members column is affixed with the device type, within parenthesis. The device type is defined while adding the zone member. The device type could be init, target, both, or blank.

- SAN Zonesets

- FCNS

- Fabric Login

- Device Alias

- FCAlias

- VSANs

Note

The Smart Zoning column displays whether the VSAN is enabled with smart zoning. If smart zoning for the device is disabled at the zone level, the status is Not Applicable. If smart zoning is disabled at the VSAN level, the status is Disabled.

- QOS Class Maps

- QOS Policy Maps

- Service Request Details

About Cisco ISE

Cisco Identity Services Engine (Cisco ISE) is a next-generation identity and access control policy platform that enables enterprises to enforce compliance, enhance infrastructure security, and streamline their service operations. The Cisco Security Group Access (SGA) solution establishes clouds of trusted network devices to build secure networks. Each device in the Cisco SGA cloud is authenticated by its neighbors (peers). Communication between the devices in the SGA cloud is secured with a combination of encryption, message integrity checks, and data-path replay protection mechanisms.

The SGA solution uses the device and user identity information that it obtains during authentication to classify, or color, the packets as they enter the network. This packet classification is maintained by tagging packets when they enter the SGA network so that they can be properly identified by applying security and other policy criteria along the data path. The tag, also called the security group tag (SGT), allows Cisco ISE to enforce access control policies by enabling the endpoint device to act upon the SGT to filter traffic.

To view the SGT entry of all devices that are managed in Cisco UCS Director, in the network pane, expand the pod and click the Cisco ISE device. The Security Group Tag Entry tab displays the name, ID, and description of the SGT entry of devices.

About the Service Request Details Report

You can view the service requests that have changed the state of a selected network device or component. The Service Request ID and the change description appear under the component's Service Request Details tab. Device or component configurations, additions, modifications, and deletions are all tracked under each component on this tab.

Any network device or component that has been part of a task in an executed workflow is tracked based on the ID of the service request that modified it.

Exporting an Inventory Report

You can export an inventory report in PDF, CSV, or XLS format.

Step 1

On the menu bar, choose Physical > Network.

Step 2

In the Network pane, choose the pod.

Step 3

Click a report that you want to export.

Step 4

On the right side of the report, click the Export Report button.

Step 5

In the Export Report dialog box, choose the desired report format from the Select Report Format drop-down list and then click Generate Report.

Step 6

After the report has been generated, click Download.

Step 7

After you have downloaded the report, click Close.

Chapter 29. Troubleshooting

This chapter contains the following sections:

- Troubleshooting Cisco UCS Director Connectivity

- Troubleshooting Cisco UCS Director Bare Metal Agent Connectivity

Troubleshooting Cisco UCS Director Connectivity

Step 1

Ensure Cisco UCS Director services are active.

Check

Do the following:

Cisco UCS Director Virtual Machine (VM)

Ensure that there is sufficient resource reservation. For more information, see the System Requirements section.

Cisco UCS Director appliance

Access the appliance using Secure Shell (SSH) and the shelladmin user. Ensure that all the services are running (including the database). If services are not running, restart the services and wait a few minutes before accessing Cisco UCS Director through the web interface.

Step 2

Ensure that the IP address of Cisco UCS Director can be pinged over the network.

Check

Do the following:

Cisco UCS Director network configuration

Log into vCenter and check the network configuration of the Cisco UCS Director virtual appliance and its connectivity.

Port group and management network

Ping the port group and management network.

Cisco UCS Director VM

Ensure that the Connect check box is checked in the VM.

Step 3

Ensure that Cisco UCS Director can be accessed through a web browser. If you cannot access Cisco UCS Director, do the following:
Note:   Wait for the Cisco UCS Director appliance and services to become available before connecting to Cisco UCS Director. This may take a few minutes.

Check

Do the following:

Web browser cache

Clear the web browser cache before accessing Cisco UCS Director through the web.

Web browser version

Use the recommended browser version and flash version.

Step 4

Ensure that Cisco UCS Director is able to reach all of the hardware and software.

Step 5

Ensure that Cisco UCS Director is on the same interface as Cisco UCS Director Bare Metal Agent.

Troubleshooting Cisco UCS Director Bare Metal Agent Connectivity

Step 1

Ensure that the DHCP service (daemon) is active.

Check

Do the following:

DHCP server

Use the following command:

/etc/init.d/dhcp status

Note:   If the status is down, restart the DHCP server.

Step 2

Ensure that the status of Cisco UCS Director Bare Metal Agent network services is active.

Check

Do the following:

Cisco UCS Director Bare Metal Agent

Use the following command:

ps -ef | grep java

Note:
Entering the above command should have three Java processes display. If not, restart the services and recheck to make sure all of them are active.

/opt/infra/stopInfraAll.sh

/opt/infra/startInfraAll.sh

Step 3

Ensure Cisco UCS Director Bare Metal Agent can ping the Cisco UCS Director Bare Metal Agent IP address. If not, check the connectivity through the network configuration of the Cisco UCS Director Bare Metal Agent appliance using vCenter.

Step 4

Ensure that Cisco UCS Director Bare Metal Agent can ping the management and blade server network.

Check

Do the following:

DHCP server

Ensure that the DHCP server that is running on the Cisco UCS Director Bare Metal Agent provides DHCP functionality for bare metal provisioning. The Cisco UCS Director Bare Metal Agent should be on the same network or interface as the manager so that it can provide Preboot Execution Environment (PXE) functionality without problems.

Ensure there are no DHCP servers available in the same network as the Cisco UCS Director Bare Metal Agent.

Preface

- Audience

- Conventions

- Related Documentation

- Documentation Feedback

- Obtaining Documentation and Submitting a Service Request

Audience

This guide is intended primarily for data center administrators who use Cisco UCS Director and who have responsibilities and expertise in one or more of the following:

- Server administration

- Storage administration

- Network administration

- Network security

- Virtualization and virtual machines

Conventions

Text Type

Indication

GUI elements

GUI elements such as tab titles, area names, and field labels appear in this font.

Main titles such as window, dialog box, and wizard titles appear in this font.

Document titles

Document titles appear in this font.

TUI elements

In a Text-based User Interface, text the system displays appears in this font.

System output

Terminal sessions and information that the system displays appear in this font.

CLI commands

CLI command keywords appear in this font.

Variables in a CLI command appear in this font.

[ ]

Elements in square brackets are optional.

{x | y | z}

Required alternative keywords are grouped in braces and separated by vertical bars.

[x | y | z]

Optional alternative keywords are grouped in brackets and separated by vertical bars.

string

A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks.

< >

Nonprinting characters such as passwords are in angle brackets.

[ ]

Default responses to system prompts are in square brackets.

!, #

An exclamation point (!) or a pound sign (#) at the beginning of a line of code indicates a comment line.

Note

Means reader take note. Notes contain helpful suggestions or references to material not covered in the document.

Caution

Means reader be careful. In this situation, you might perform an action that could result in equipment damage or loss of data.

Tip

Means the following information will help you solve a problem. The tips information might not be troubleshooting or even an action, but could be useful information, similar to a Timesaver.

Timesaver

Means the described action saves time. You can save time by performing the action described in the paragraph.

Warning

IMPORTANT SAFETY INSTRUCTIONS

This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. Use the statement number provided at the end of each warning to locate its translation in the translated safety warnings that accompanied this device.

SAVE THESE INSTRUCTIONS

Related Documentation

Cisco UCS Director Documentation Roadmap

For a complete list of Cisco UCS Director documentation, see the Cisco UCS Director Documentation Roadmap available at the following URL: Click Here .

Cisco UCS Documentation Roadmaps

For a complete list of all B-Series documentation, see the Cisco UCS B-Series Servers Documentation Roadmap available at the following URL: Click Here .

For a complete list of all C-Series documentation, see the Cisco UCS C-Series Servers Documentation Roadmap available at the following URL: Click Here .

Note

The Cisco UCS B-Series Servers Documentation Roadmap includes links to documentation for Cisco UCS Manager and Cisco UCS Central. The Cisco UCS C-Series Servers Documentation Roadmap includes links to documentation for Cisco Integrated Management Controller.

Documentation Feedback

To provide technical feedback on this document, or to report an error or omission, please send your comments to ucs-director-docfeedback@cisco.com. We appreciate your feedback.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation.

To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What's New in Cisco Product Documentation RSS feed. RSS feeds are a free service.

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: Click Here . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)