Symptoms

SC Service Name and Smartconnect zone name (including zone name alias) must not match as they can cause unexpected failures. During initial configuration of the Isilon cluster, sometimes the subnet and SC Service Name are created first. If the cluster is configured with more than one subnet, the SC Service Name is also created before pool zone names have been configured. This can lead to configuration mistakes whereby one or more SC Service Names and Smartconnect Zone names may have matching strings. When attempting to change the SC Service Name after it matches the zone name, an error will occur indicating the name cannot be changed.For example, the following subnets SC Service Name and pool Zone Name are identical. clr8120-1# isi network subnets view groupnet0.SYNCIQ_SUBNET ID: groupnet0.SYNCIQ_SUBNET Name: SYNCIQ_SUBNET Groupnet: groupnet0 Pools: SYNCIQ_POOL Addr Family: ipv4 Base Addr: 10.100.16.0 CIDR: 10.100.16.0/23 Description: - Dsr Addrs: - Gateway: 10.100.16.1 Gateway Priority: 20 MTU: 1500 Prefixlen: 23 Netmask: 255.255.254.0 Sc Service Addr: 10.100.16.209 Sc Service Name: test1.isilon.local VLAN Enabled: True VLAN ID: 160 clr8120-1# isi network pools view groupnet0.SYNCIQ_SUBNET.SYNCIQ_POOL ID: groupnet0.SYNCIQ_SUBNET.SYNCIQ_POOL Groupnet: groupnet0 Subnet: SYNCIQ_SUBNET Name: SYNCIQ_POOL Rules: - Access Zone: System Allocation Method: dynamic Aggregation Mode: lacp SC Suspended Nodes: - Description: - Ifaces: 1:ext-1, 2:ext-1, 3:ext-1 IP Ranges: 10.100.16.210-10.100.16.221 Rebalance Policy: auto SC Auto Unsuspend Delay: 0 SC Connect Policy: round_robin SC Zone: test1.isilon.local SC DNS Zone Aliases: ig-test1.isilon.local SC Failover Policy: round_robin SC Subnet: subnet0 SC TTL: 0 Static Routes: - clr8120-1# isi network subnets view groupnet0.VLAN100_subnet ID: groupnet0.VLAN100_subnet Name: VLAN100_subnet Groupnet: groupnet0 Pools: VLAN100_pool Addr Family: ipv4 Base Addr: 10.100.10.0 CIDR: 10.100.10.0/23 Description: - Dsr Addrs: - Gateway: 10.100.10.1 Gateway Priority: 30 MTU: 1500 Prefixlen: 23 Netmask: 255.255.254.0 Sc Service Addr: 10.100.10.10 Sc Service Name: test2.isilon.local VLAN Enabled: True VLAN ID: 100 clr8120-1# isi network pools view groupnet0.VLAN100_subnet.VLAN100_pool ID: groupnet0.VLAN100_subnet.VLAN100_pool Groupnet: groupnet0 Subnet: VLAN100_subnet Name: VLAN100_pool Rules: - Access Zone: System Allocation Method: dynamic Aggregation Mode: lacp SC Suspended Nodes: - Description: - Ifaces: 1:ext-1, 2:ext-1, 3:ext-1 IP Ranges: 10.100.11.31-10.100.11.50 Rebalance Policy: auto SC Auto Unsuspend Delay: 0 SC Connect Policy: round_robin SC Zone: test2.isilon.local SC DNS Zone Aliases: ig-test2.isilon.local SC Failover Policy: round_robin SC Subnet: subnet0 SC TTL: 0 Static Routes: 10.20.30.0/24-10.100.11.1 Yet, the service name is not able to change indicating the name already exists (through CLI and UI). Nor can you add an SC Service Name to another subnet (error below). clr8120-1# isi network subnets modify groupnet0.subnet0 --sc-service-name=test1-sip.isilon.local Error in field(s): sc_service_name More than one IPv4 subnet/pool in groupnet0 has the name 'test1.isilon.local'

Cause

OneFS does not accurately validate the SC Service Name string when duplicates occur for both the service name and zone name.

Resolution

All SC Service Names must be unique to all other service names, zone names, and zone aliases. If you receive the above error, then all SC Service Name strings (that contain duplicates) must be changed to an empty string value. # isi network subnets modify . --sc-service-name="" For example, to change the above SC Service Name values, both groupnet0.SYNCIQ_SUBNET and groupnet0.VLAN100_subnet must be reset to an empty string. # isi network subnets modify groupnet0.SYNCIQ_SUBNET --sc-service-name="" ... AND # isi network subnets modify groupnet0.VLAN100_subnet --sc-service-name="" Once all duplicate service names have been changed to empty strings, they can now be modified to an appropriate unique value.

Support Cases