- Preface
- Overview of Cisco Unified Computing System
- Overview of Cisco UCS Manager
- Overview of Cisco UCS Manager CLI
- Configuring the Fabric Interconnects
- Configuring Ports and Port Channels
- Configuring Communication Services
- Configuring Authentication
- Configuring Organizations
- Configuring Role-Based Access Control
- Configuring DNS Servers
- Configuring System-Related Policies
- Managing Licenses
- Managing Virtual Interfaces
- Registering Cisco UCS Domains with Cisco UCS Central
- VLANs
- Configuring LAN Pin Groups
- Configuring MAC Pools
- Configuring Quality of Service
- Configuring Network-Related Policies
- Configuring Upstream Disjoint Layer-2 Networks
- Configuring Named VSANs
- Configuring SAN Pin Groups
- Configuring WWN Pools
- Configuring Storage-Related Policies
- Configuring Fibre Channel Zoning
- Configuring Server-Related Pools
- Setting the Management IP Address
- Configuring Server-Related Policies
- Configuring Server Boot
- Deferring Deployment of Service Profile Updates
- Service Profiles
- Configuring Storage Profiles
- Managing Power in Cisco UCS
- Managing Time Zones
- Managing the Chassis
- Managing Blade Servers
- Managing Rack-Mount Servers
- CIMC Session Management
- Managing the I/O Modules
- Backing Up and Restoring the Configuration
- Recovering a Lost Password
Configuring SAN Pin Groups
This chapter includes the following sections:
SAN Pin Groups
Note | In Fibre Channel switch mode, SAN pin groups are irrelevant. Any existing SAN pin groups will be ignored. |
To configure pinning for a server, you must include the SAN pin group in a vHBA policy. The vHBA policy is then included in the service profile assigned to that server. All traffic from the vHBA will travel through the I/O module to the specified uplink Fibre Channel port.
You can assign the same pin group to multiple vHBA policies. As a result, you do not need to manually pin the traffic for each vHBA.
Changing the target interface for an existing SAN pin group disrupts traffic for all vHBAs which use that pin group. The fabric interconnect performs a log in and log out for the Fibre Channel protocols to re-pin the traffic.
Configuring a SAN Pin Group
In a system with two fabric interconnects, you can associate the pin group with only one fabric interconnect or with both fabric interconnects.
The following example creates a SAN pin group named fcpingroup12, provides a description for the pin group, sets the pin group target to slot 2, port 1, and commits the transaction:
UCS-A# scope fc-uplink UCS-A /fc-uplink # create pin-group fcpingroup12 UCS-A /fc-uplink/pin-group* # set descr "This is my pin group #12" UCS-A /fc-uplink/pin-group* # set target a port 2/1 UCS-A /fc-uplink/pin-group* # commit-buffer UCS-A /fc-uplink/pin-group #
Include the pin group in a vHBA template.
Configuring a FCoE Pin Group
You can create a FCoE pin group, and specify the FCoE uplink port as the pin group target.
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# scope fc-uplink |
Enters FC uplink mode. |
Step 2 | UCS-A /fc-uplink # create pin-group fcoepingroup |
Creates a FCoE pin group with the specified name, and enters FCoE uplink pin group mode. |
Step 3 | UCS-A /fc-uplink/pin-group # set target a fcoe-port 1/8 |
Sets FCoE port 1/8 as the target port for this pin group. |
Step 4 | UCS-A /fc-uplink/pin-group # commit-buffer |
Commits the transaction to the system configuration. |
UCS-A# scope fc-uplink UCS-A /fc-uplink # create pin-group fcoepingroup UCS-A /fc-uplink/pin-group* #set target a fcoe-port 1/8 UCS-A /fc-uplink/pin-group* # commit-buffer UCS-A /fc-uplink/pin-group #