Logical switch configuration guidelines

  • When Virtual Connect interconnects are connected to a logical switch, an uplink set cannot span multiple interconnects. This limitation is similar to FEX interconnects. However, multiple uplink sets are supported on a single Virtual Connect interconnect.

  • When you enable or disable a top-of-rack switch downlink port, the associated port on a Virtual Connect interconnect also displays the updated port status.

  • When retrieving MAC addresses for FEX interconnects, only the entries that are associated with the managed FEX interconnects are displayed.

  • If an FCoE network is assigned to an uplink set that is configured as dual-homed (an invalid configuration), that FCoE network is not provisioned on the switch. Deployment of any server profile connection with this FCoE network will fail.

  • When a logical switch is defined and configured with only a single physical switch, the uplink set associated with any FEX module connected to this logical switch is considered single-homed. Therefore, you can add an FCoE network to the uplink set even if the uplink set was initially created only with Ethernet networks. Deployment of any server profile connection with this FCoE network will succeed.

  • For server profiles created for server ports connected to FEX interconnects, Ethernet networks are only supported on physical function a, and FCoE networks are only supported on physical function b at the server port. When both physical functions have connections defined, traffic is split evenly across both ports.

  • If HPE OneView cannot log in to the switch, a critical alert is generated and the switch transitions to ConfigError state. You must reapply the logical switch configuration to its physical switches on the logical switch to recover.

  • If HPE OneView is unable to claim a member switch of the logical switch when the operational mode of the logical switch is Managed, the operating state of the switch transitions to Added with Error. In this case, the Message of the Day (MOTD) banner on the switch indicates that the switch is currently claimed by another HPE OneView appliance and the message “This switch is being controlled by OneView Domain, Appliance ID: {} ” displays. You should remove the logical switch from that HPE OneView appliance, and then refresh the logical switch from the current HPE OneView appliance to re-initiate the claim operation.

  • HPE OneView does not fully automate configuration of FCoE connectivity on the switch specified in the logical switch. For each FCoE network specified in the uplink set, HPE OneView only provisions the VLAN for that network on the switch. Network administrators must provision additional configuration for FCoE connectivity manually on the switch in addition to what HPE OneView provisions.

    • To deploy server profile connections to a FEX interconnect, HPE OneView provisions the virtual Fibre Channel interface (VFC), VFC binding to FEX downlink port, and VSAN interface assignment on the switch.

    • For the deployment of server profile connections for a Virtual Connect interconnect, the Network administrator must configure the virtual Fibre Channel interface (vFC), VFC binding to server port, and VSAN interface assignment binding manually.

  • When a Cisco Nexus switch expansion module is removed, a warning alert is generated unless the module is powered off.

  • HPE OneView can detect configuration changes that occur on the switches specified in the logical switch. Warning alerts are generated when the switch configuration no longer matches the configuration provisioned by HPE OneView.

    To recover, administrators can correct the configuration manually on the physical switch or reapply the configuration on the logical switch.