Skip to content

SAN Connectivity Policy

A SAN Connectivity Policy groups one or more vHBAs and wires them to their associated Fibre Channel policies (adapter, network, QoS) and WWPN pools. It defines the complete Fibre Channel configuration for a server, including fabric placement and vHBA type. The policy is applied to servers via a Server Profile Template.

Location in Intersight GUI: Policies » SAN Connectivity

Diagram

policies (compute.intersight.organizations)

Section titled “policies (compute.intersight.organizations)”
NameTypeConstraintMandatoryDefault Value
san_connectivityList[san_connectivity]No

san_connectivity (compute.intersight.organizations.policies)

Section titled “san_connectivity (compute.intersight.organizations.policies)”
NameTypeConstraintMandatoryDefault Value
nameStringRegex: ^[a-zA-Z0-9_.:-]{1,64}$Yes
descriptionStringNo
managedBooleantrue, falseNotrue
tagsList[tags]No
target_platformChoiceFIAttached, Standalone, UnifiedEdgeServerNoFIAttached
vhba_placement_modeChoiceauto, customNocustom
wwnn_poolStringNo
vhbasList[vhbas]No

tags (compute.intersight.organizations.policies.san_connectivity)

Section titled “tags (compute.intersight.organizations.policies.san_connectivity)”
NameTypeConstraintMandatoryDefault Value
keyStringYes
valueStringYes

vhbas (compute.intersight.organizations.policies.san_connectivity)

Section titled “vhbas (compute.intersight.organizations.policies.san_connectivity)”
NameTypeConstraintMandatoryDefault Value
nameStringRegex: ^[a-zA-Z0-9_.:-]{1,64}$Yes
orderIntegermin: 0, max: 255No0
fabricChoiceA, B, NoneNoA
slotStringNo
pci_linkIntegermin: 0, max: 1No
uplinkIntegermin: 0No
auto_pci_linkBooleantrue, falseNo
auto_slot_idBooleantrue, falseNo
persistent_lun_bindingsBooleantrue, falseNo
vhba_typeChoicefc-initiator, fc-nvme-initiator, fc-nvme-target, fc-targetNofc-initiator
wwpn_poolStringNo
fibre_channel_adapter_policyStringNo
fibre_channel_network_policyStringNo
fibre_channel_qos_policyStringNo

Example-1: The example below demonstrates an FI-attached SAN connectivity policy with two FC initiator vHBAs placed on separate fabric paths for high availability.

compute:
intersight:
organizations:
- name: MyOrganization
policies:
san_connectivity:
- name: web-san
description: SAN connectivity for web servers
target_platform: FIAttached
wwnn_pool: web-wwnn
vhbas:
- name: vhba0
order: 2
fabric: A
vhba_type: fc-initiator
wwpn_pool: web-wwpn-a
fibre_channel_adapter_policy: web-fc-adapter
fibre_channel_network_policy: web-fc-network
fibre_channel_qos_policy: web-fc-qos
- name: vhba1
order: 3
fabric: B
vhba_type: fc-initiator
wwpn_pool: web-wwpn-b
fibre_channel_adapter_policy: web-fc-adapter
fibre_channel_network_policy: web-fc-network
fibre_channel_qos_policy: web-fc-qos
tags:
- key: env
value: prod

Example-2: The example below demonstrates explicit slot assignment for deployments where vHBA placement must be pinned to a specific adapter slot.

compute:
intersight:
organizations:
- name: MyOrganization
policies:
san_connectivity:
- name: web-san-pinned
description: SAN connectivity with pinned MLOM slot
target_platform: FIAttached
vhbas:
- name: vhba0
order: 2
fabric: A
slot: MLOM
pci_link: 0
wwpn_pool: web-wwpn-a
fibre_channel_adapter_policy: web-fc-adapter
fibre_channel_network_policy: web-fc-network
fibre_channel_qos_policy: web-fc-qos