How to Remove a VLAN or Change a Network in PowerFlex Manager

The first step is to add the network or VLAN that will be used -

1. On the menu bar, click Settings and then click Networking.

2. Click Networks. The Networks page opens.

3. Click Define. The Define Network page opens.

4. In the Name field, enter the name of the network. Optionally, in the Description field, enter a description for the network.

5. From the Network Type drop-down list, select one of the following network types:

• General Purpose LAN
• Hypervisor Management
• Hypervisor Migration
• PowerFlex Data
• PowerFlex Data (Client Traffic Only)
• PowerFlex Data (Server Traffic Only
• PowerFlex Replication
• NAS File Management
• NAS File Data
• PowerFlex Management

For a PowerFlex configuration that uses a hyperconverged architecture with two data networks, you typically have two networks that are defined with the PowerFlex data network type. The PowerFlex data network type supports both client and server communications. The PowerFlex data network type is used with hyperconverged resource groups. 

For a PowerFlex configuration that uses a two-layer architecture with four dedicated data networks, you typically have two PowerFlex (client traffic only) VLANs and two PowerFlex data (server traffic only) VLANs. These network types are used with storage-only and compute-only resource groups.

6. In the VLAN ID field, enter a VLAN ID between 1 and 4094.
NOTE: PowerFlex Manager uses the VLAN ID to configure I/O modules that enable network traffic to flow from the node to configured networks during deployment.

7. Optionally, select the Configure Static IP Address Ranges check box, and then do the following:
NOTE: The Configure Static IP Address Ranges check box is not available for all network types. For example, you cannot configure a static IP address range for the operating system installation network type. You cannot select or clear this check box to configure static IP address pools after a network is created.

1.  In the Subnet box, enter the IP address for the subnet. The subnet is used to support static routes for data and replication networks.
2. In the Subnet Mask box, enter the subnet mask.
3. In the Gateway box, enter the default gateway IP address for routing network traffic.
4. Optionally, in the Primary DNS and Secondary DNS fields, enter the IP addresses of primary DNS and secondary DNS.
5. Optionally, in the Primary DNS and Secondary DNS fields, enter the IP addresses of primary DNS and secondary DNS.
6. To add an IP address range, click Add IP Address Range. In the row, indicate the role in PowerFlex nodes for the IP address range and then specify a starting and ending IP address for the range. For the Role, select either:
   1. Server or Client: Range is assigned to the server and client roles.
   2. Client Only: Range is assigned to the client role on PowerFlex hyperconverged nodes and PowerFlex compute-only nodes.
   3. Server Only: Range is assigned to the server role on PowerFlex hyperconverged nodes and PowerFlex storage-only nodes. Repeat this step to add IP address ranges based on the requirement. For example, you can use one range for SDC and another for SDS. NOTE: IP address ranges cannot overlap. For example, you cannot create an IP address range of 10.10.10.1– 10.10.10.100 and another range of 10.10.10.50–10.10.10.150.

8. Click Save. 

The next step is to remove the Resource Groups (Ensure to keep them as managed) that are attached to the VLANs that are still using the services. Ensure you remove and do not delete.

1. On the menu bar, click Lifecycle > Resource Groups. 

2. Select a resource group from which you want to delete resources.

3. In the right pane, click View Details.

4. On the Resource Group Details page, in the right pane, under More Actions, click Remove Resource.

5. In the Remove Resource dialog box, select the node that you want to remove and click Next.

6. Select the Resource removal type:

• Delete Resource makes configuration changes to the nodes, switch ports, virtual machine managers, and PowerFlex to unconfigure those components, and returns the components to the available inventory.
• Remove Resource removes deployment information, but does not make any configuration changes to the nodes, switch ports, virtual machine managers, and PowerFlex, and returns the components to the available inventory.

7. If you choose Remove Resource, perform the following steps: 

1. To keep the node in the inventory, select Leave resource in PowerFlex Manager inventory and set state to and select the state:
   1. Managed
   2. Unmanaged
   3. Reserved
2. To remove the node, select Remove resource from the PowerFlex Manager inventory.
3. Click Remove

8. If you choose Delete Resource, perform the following steps:

1. If you are certain that you want to proceed, type DELETE RESOURCE.
2. Click Delete.

If a template is using the VLAN/Network configuration then the template will need the networks removed as well.

1. On the menu bar, click Templates.

2. Select the template that you want to delete. Click More Actions > Delete Template in the right pane.

3. Click Yes to confirm the deletion.

After the Resource Groups/Templates are removed then the VLAN/Network can be modified or removed -

1. On the menu bar, click Settings and then click Networking.

2. Click Networks. The Networks page opens.

3. Select the network that you want to edit and click Modify. The Modify Network page opens.

4. Edit the information in any of the following fields: Name, VLAN ID, IP Address Range. For a PowerFlex data or replication network, you can specify a Subnet IP address for a static route configuration. The subnet is used to support static routes for data and replication networks.

5. Click Save.

You can also view details for a network or export the network details by selecting the network, then clicking View Details or Export Network Details.

After old Networks/VLANs are removed, then the Resource Group can be added back

1. On the menu bar, click Lifecycle > Resource Groups and then click + Add Existing Resource Group.

2. On the Add Existing Resource Group page, enter a resource group name in the Name field.

3. Enter a description in the Description field.

4. Select the Type for the resource group.
The choices are Hyperconverged, Compute Only, Storage Only, and PowerFlex File. For compute only types, only the VMware compute only resource groups can be added to an existing resource group. Linux compute only resources groups cannot be added to existing resource groups. PowerFlex Manager checks to see whether there are any vCLS VMs on local storage. If it finds any, it puts the resource group in life cycle mode and lets you migrate these VMs to shared storage.

5. To specify the compliance version to use for compliance, select the version from the Firmware and Software Compliance list or select Use PowerFlex Manager appliance default catalog.
You cannot specify a minimal compliance version when you add an existing resource group, since it only includes server firmware updates. The compliance version for an existing resource group must include the full set of compliance update capabilities. PowerFlex Manager does not show any minimal compliance versions in the Firmware and Software Compliance list.
NOTE: Changing the compliance version might update the firmware level on nodes for this resource group. Firmware on shared devices is maintained by the global default firmware repository.

6. Specify the resource group permissions under Who should have access to the resource group deployed from this template? by performing one of the following actions:

•  To restrict access to super users, select Only PowerFlex SuperUser.
• To grant access to super users and some specific lifecycle administrators and drive replacers, select the PowerFlex SuperUser and specific LifecycleAdmin and DriveReplacer option, and perform the following steps:
  1. Click Add User(s) to add one or more LifecycleAdmin or DriveReplacer users to the list.
  2. Select which users will have access to this resource group.
  3. To delete a user from the list, select the user and click Remove User(s).
  4. After adding the users, select or clear the check box next to the users to grant or block access.

● To grant access to super users and all lifecycle administrators and drive replacers, select PowerFlex SuperUser and all LifecycleAdmin and DriveReplacer. 

7. Click Next.

8. Choose one of the following network automation types:

• Full Network Automation
• Partial Network Automation

When you choose Partial Network Automation, PowerFlex Manager skips the switch configuration step, which is normally performed for a resource group with Full Network Automation. Partial network automation allows you to work with unsupported switches. However, it also requires more manual configuration before a deployment can proceed successfully. If you choose to use partial network automation, you give up the error handling and network automation features that are available with a full network configuration that includes supported switches.
In the Number of Instances box, provide the number of component instances that you want to include in the template.

9. On the Cluster Information page, enter a name for the cluster component in the Component Name field.

10. Select values for the cluster settings: For a hyperconverged or compute-only resource group, select values for these cluster settings:

1. Target Virtual Machine Manager—Select the vCenter name where the cluster is available.
2. Data Center Name—Select the data center name where the cluster is available. NOTE: Ensure that the selected vCenter has unique names for clusters in case there are multiple clusters in the vCenter.
3. Cluster Name—Select the name of the cluster you want to discover.
4. OS Image—Select the image or choose Use Compliance File ESXi image if you want to use the image provided with the target compliance version. PowerFlex Manager filters the operating system image choices to show only ESXi images for a hyperconverged or compute-only resource group.

For a storage-only resource group, select values for these cluster settings: 

1. Target PowerFlex Gateway—Select the gateway where the cluster is available.
2. Protection Domain—Select the name of the protection domain in PowerFlex.
3. OS Image—Select the image or choose Use Compliance File Linux image if you want to use the image provided with the target compliance version. PowerFlex Manager filters the operating system image choices to show only Linux images for a storage-only resource group.
   a. Target PowerFlex Gateway—Select the gateway where the cluster is available.
   b. Protection Domain—Select the name of the protection domain in PowerFlex.
   c. OS Image—Select the image or choose Use Compliance File Linux image if you want to use the image provided with the target compliance version. PowerFlex Manager filters the operating system image choices to show only Linux images for a storage-only resource group.

For a PowerFlex file resource group, select values for these cluster settings: 

1. Target PowerFlex Gateway—Select the gateway where the cluster is available.
2. OS Image—Choose Use Compliance File Linux image for a PowerFlex file resource group.

11. Click Next.

12. On OS Credentials page, select the operating system credential that you want to use for each node, SVM, and MVM.
You can select one credential for all nodes, SVMs or MVMs, or choose credentials for each item separately. You can create the operating system credentials on the Credentials Management page under Settings.
PowerFlex Manager validates the credentials before it creates the resource group. This validation makes it possible for PowerFlex Manager to run a full inventory on all nodes, SVMs, and MVMs before creating the resource group. PowerFlex Manager runs the inventory on all nodes, SVMs, and MVMs for which the credentials are valid. The resource group uses any nodes, SVMs, and MVMs for which it has a successful inventory. For example, if you have four nodes, and one node has an invalid operating system password, PowerFlex Manager adds the three nodes for which the credentials are valid and ignores the one with an invalid password.

13. Click Next. The list of resources available in the cluster is displayed on the Inventory Summary page.

14. Review the inventory on the Inventory Summary page.
The summary shows all nodes that are available. If a node is not available, it might be because this node does not match the Type you selected for the resource group (Hyper-converged, Compute only, Storage only, or PowerFlex File).
Depending on how the node is configured, the summary might show additional inventory information. For example, for a node that has NVDIMM compression, the summary shows additional information about the acceleration pool and compression settings.
If the resources are discovered and in an available state, the Available Inventory displays the components as Yes. An unavailable PowerFlex gateway is shown as No.
If the credentials are invalid for a node or SVM, or if you have a network connectivity problem, PowerFlex Manager displays No in the Available Inventory column for the node, and displays an error message to notify you about the problem.
PowerFlex Manager cannot update firmware and software versions for PowerFlex clusters that do not have available PowerFlex Gateways. If expected PowerFlex Gateways are not shown as available, you can discover the gateways and run the wizard again.
NOTE: PowerFlex Manager retrieves the hostname value from iDRAC and not the operating system. If the hostname field is not updated in iDRAC, an incorrect value can be displayed in PowerFlex Manager. Certain operating systems require extra packages that are installed for iDRAC to update the correct hostname.

15. Click Next.

16. On the Network Mapping page, review the networks that are mapped to port groups and make any required edits.
PowerFlex Manager attempts to select the correct network based on the VLAN ID, subnet, or IP ranges entered in PowerFlex Manager. If PowerFlex Manager finds only one network for a given network type, it selects the network automatically. If it finds more than one, you must select the network from the Network drop-down list. The operating system Installation network does not get a VLAN ID.
NOTE: If the operating system install VLAN is not already configured in your environment, add it. This network is required to perform node expansions. This network is typically added during PowerFlex Manager configuration.
If there are any port groups for which you do not want PowerFlex Manager to manage access, leave those port groups cleared. If no network is selected for a particular port group, PowerFlex Manager leaves it out of the deployment data and does not add it to the nodes.  

17. To import many general-purpose VLANs from vCenter, perform these steps:

1.  Click Import Networks on the Network Mapping page. PowerFlex Manager displays the Import Networks wizard. In the Import Networks wizard, PowerFlex Manager lists the port groups that are defined on the vCenter as Available Networks. You can see the port groups and the VLAN IDs.
2. ptionally, search for a VLAN name or VLAN ID. PowerFlex Manager filters the list of available networks to include only those networks that match your search.
3. Click each network that you want to add under Available Networks. If you want to add all the available networks, click the check box to the left of the Name column.
4. Click the double arrow (>>) to move the networks you chose to Selected Networks. PowerFlex Manager updates the Selected Networks to show the ones that you have chosen.
5. Click Save.

18. Click Next.

19. Review the Summary page and click Finish when you are ready to add the resource group.

PowerFlex Manager displays a message indicating that a new job is being created for this resource group. The process of adding an existing resource group causes no disruption to the underlying hardware resources. It does not shut down any of the nodes or the vCenter. For an existing resource group, the Reference Template field shows Generated Existing Resource Group Template on the Resource Group Details page. You can distinguish existing resource groups from new resource groups that were deployed with PowerFlex Manager. When PowerFlex Manager must put a resource group in lifecycle mode, the Summary page for the Add Existing Resource Group wizard displays a warning message indicating the reason. In some situations, an imported configuration might not meet the minimal requirements for lifecycle mode. In this case, PowerFlex Manager does not allow you to add the resource group