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
Section titled “Diagram”Classes
Section titled “Classes”policies (compute.intersight.organizations)
Section titled “policies (compute.intersight.organizations)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| san_connectivity | List | [san_connectivity] | No |
san_connectivity (compute.intersight.organizations.policies)
Section titled “san_connectivity (compute.intersight.organizations.policies)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Regex: ^[a-zA-Z0-9_.:-]{1,64}$ | Yes | |
| description | String | No | ||
| managed | Boolean | true, false | No | true |
| tags | List | [tags] | No | |
| target_platform | Choice | FIAttached, Standalone, UnifiedEdgeServer | No | FIAttached |
| vhba_placement_mode | Choice | auto, custom | No | custom |
| wwnn_pool | String | No | ||
| vhbas | List | [vhbas] | No |
tags (compute.intersight.organizations.policies.san_connectivity)
Section titled “tags (compute.intersight.organizations.policies.san_connectivity)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| key | String | Yes | ||
| value | String | Yes |
vhbas (compute.intersight.organizations.policies.san_connectivity)
Section titled “vhbas (compute.intersight.organizations.policies.san_connectivity)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Regex: ^[a-zA-Z0-9_.:-]{1,64}$ | Yes | |
| order | Integer | min: 0, max: 255 | No | 0 |
| fabric | Choice | A, B, None | No | A |
| slot | String | No | ||
| pci_link | Integer | min: 0, max: 1 | No | |
| uplink | Integer | min: 0 | No | |
| auto_pci_link | Boolean | true, false | No | |
| auto_slot_id | Boolean | true, false | No | |
| persistent_lun_bindings | Boolean | true, false | No | |
| vhba_type | Choice | fc-initiator, fc-nvme-initiator, fc-nvme-target, fc-target | No | fc-initiator |
| wwpn_pool | String | No | ||
| fibre_channel_adapter_policy | String | No | ||
| fibre_channel_network_policy | String | No | ||
| fibre_channel_qos_policy | String | No |
Examples
Section titled “Examples”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: prodExample-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