White Papers
Abstract
Determine Correct Hardware Management Console (HMC) Command On Dual HMC To Move PVID/VLAN From vSwitchA On VIO Server (Virtual I/O) Source Frame To VswitchB On VIO Server Target Frame.
Content
VIOS Version 2.2.4
System Firmware Release 840
HMC Release 8 Version 8.4.0
- https://www.ibm.com/support/knowledgecenter/POWER8/p8hc3/p8hc3_hmcprepdiffvswitch.htm
- https://www.ibm.com/support/knowledgecenter/POWER8/p8hc3/p8hc3_hmcprepservers.htm
lssyscfg -r sys -m [Source_Managed_System] -F capabilities
lssyscfg -r sys -m [Target_Managed_System] -F capabilities
Listing Source_Managed_System and Destination Managed_System:
# lssyscfg -r sys -F name
Environment & Scenario:
1) Dual HMC with multiple vSwitches (vSwitchA, vSwitchB and vSwitchC)
2) Source and Destination frames with dual VIO servers hosting the client LPAR (Not configured with MSP)
- Source VIO servers: vio4a and vio4b on FrameA
- Destination VIO servers: vio11a and vio11b on FrameB
3) Mover Service Partition (MSP) VIO servers for network communication.
- viom04a and viom04b on FrameC
- viom011a and viom011b on FrameD
viom04a=source_msp_ipaddr=10.11.12.1
viom011a=dest_msp_ipaddr=10.11.12.2
4) Client LPAR (clientA)
* VEA ent0 PVID: 240 VIDs: SwitchID: vSwitchA
* VEA ent1 PVID: 473 VIDs: SwitchID: vSwitchB
In this scenario VLAN 240 is on vSwitchA and need to move it to VLAN 240 on VSwitchB.
How to locate source and target MSP pairs from HMC for moving client LPAR (clientA)
# lslparmigr -r msp -m [Source_Managed_System] -t [Destination_Managed_System] --ip [des_hmc_ip] -u hscroot --filter "lpar_names=clientA"
Executing validation command with single VLAN:
migrlpar -o v -m [Source_Managed_System] -t [Destination_Managed_System] -i "vswitch_mappings=240/vSwitchA/vSwitchB,source_msp_ipaddr=10.11.12.1,dest_msp_ipaddr=10.11.12.2" --ip [DES-HMC] --id 16 --vlanbridge 2 --vsi 2 -d 5
For single HMC remove --ip [DES-HMC]
Executing migration command with single VLAN:
migrlpar -o m -m [Source_Managed_System] -t [Destination_Managed_System] -i "vSwitch_mappings=240/vSwitchA/vSwitchB,source_msp_ipaddr=10.11.12.1,dest_msp_ipaddr=10.11.12.2" --ip [des_hmc_ip] --id 16 --vlanbridge 2 --vsi 2 -d 5
When using multiple VLAN, the CLI command for bash to work will need to be as below for validation and migration. Change -v to -m for migration.
migrlpar -o v -m DCW_DIS-02-850 -t DCW_DIS-01-850
-i "\"vswitch_mappings=240/vSwtichA/vSwtichB,250/vSwtichA/vSwtichB\", source_msp_ipaddr=10.11.12.1,dest_msp_ipaddr=10.11.12.2"
--ip 170.94.244.187 --id 7 --vlanbridge 2 --vsi 2 -d 5
Additional Comments:
After validation, check the output to make sure that any HLC* warnings are not for the MSP pair selected. All others should be ignored since during validation, the HMC will scan across all VIO servers and will report both MSP and non MSP information.
From the migrlpar command man page:
http://www.ibm.com/support/knowledgecenter/POWER8/p8edm/migrlpar.html
vswitch_mappings
Comma separated list of virtual switch mappings, with each mapping having the following format:
"vlan-id/source-vswitch-name/dest-vswitch-name"
For Example:
6/srcSwitch/dstSwitch specifies a mapping of VLAN ID 6 on virtual switch srcSwitch to the virtual switch dstSwitch on the destination managed system.
Rev 1: June 19, 2020: Added 2 links under minimum requirement and correct clarify [des_hmc_ip] when using dual HMC.
Rev2: Aug 31, 2020: updated command to include example with more than 1 VLAN.
Rev3: Sept 16 2022: updated the command syntax
Author: Rajendra D Patel (rajpat@us.ibm.com)
Related Information
Was this topic helpful?
Document Information
Modified date:
16 September 2022
UID
isg3T7000732