LPM and multiple vSwitches
We are running HMC V8 R8.6.0.1 and have discovered an issue with LPM's when you use the vswitch_mappings option with multiple desitnation vswitch names. Using the LPM command as shown below, we found that the desitination HMC does not process the vswitch_mappings option correctly and places all the desination VLANs in the first vSwitch specficied. E.g. All the vSwitch names in the LPAR profile and the LPARs running profile would be set to Switch1 in the example below.
A software defect has been raised for this by the HMC Development team: SW389542
migrlpar -o v -m Server1 -t Server1 -p LPAR11 --ip 1.2.3.4 -u hscroot -i
'dest_lpar_id=5,"virtual_scsi_mappings=1/vio1//50,2/vion2//51",
"virtual_fc_mappings=3/vion1//52,4/vio1//53,5/vio2//54,6/vio2//55",
"vswitch_mappings=123/ETHERNET0/Switch1,246/ETHERNET0/Switch2,345/ETHERNET0/Switch2",
shared_proc_pool_name=pool,source_msp_name=vioa,>source_msp_ipaddr=1.2.3.8,dest_msp_name=vio2,dest_msp_ipaddr=1.2.3.9'
1 comment
Comment from: Gagandeep Visitor
Use following : \" \" within virtual_scwitch_mappings
migrlpar -o v -m Server1 -t Server1 -p LPAR11 --ip 1.2.3.4 -u hscroot -i 'dest_lpar_id=5,"virtual_scsi_mappings=1/vio1//50,2/vion2//51",
"virtual_fc_mappings=3/vion1//52,4/vio1//53,5/vio2//54,6/vio2//55", "vswitch_mappings=\"123/ETHERNET0/Switch1,246/ETHERNET0/Switch2,345/ETHERNET0/Switch2\"", shared_proc_pool_name=pool,source_msp_name=vioa,>source_msp_ipaddr=1.2.3.8,dest_msp_name=vio2,dest_msp_ipaddr=1.2.3.9'