vparmodify

[J Turner]

I have two vpars. vpar0 and vpar2.
On this npar there are two cell boards.
Class I H/W Path Driver S/W State H/W Type Description
cell 0 1 cell CLAIMED BUS_NEXUS
cell 1 2 cell CLAIMED BUS_NEXUS

I do an ioscan of vpar2 and select the ioscan -fn devices the vpar is not using.
ba 7 2/0/8 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
fc 4 2/0/8/1/0 fcd CLAIMED INTERFACE HP AB379-60101 4Gb Dual Port PCI/PCI-X Fibre Channel Adapter (FC Port 1)
/dev/fcd4
fc 5 2/0/8/1/1 fcd CLAIMED INTERFACE HP AB379-60101 4Gb Dual Port PCI/PCI-X Fibre Channel Adapter (FC Port 2)
/dev/fcd5

Then I run these commands and nothing is removed.
#vparmodify -p vpar2 -d io:2/0/8 -d io:2/0/8/1/0 -d io:2/0/8/1/1
vparmodify: Error: "-d io:2/0/8": The device at the specified path is not an I/O device.
# vparmodify -p vpar2 -d io:2/0/8/1/0 -d io:2/0/8/1/1
vparmodify: Error: "-d io:2/0/8/1/0": The device at the specified path is not an I/O device.
# vparmodify -p vpar2 -d io:0/8
vparmodify: Error: "-d io:0/8": The device at the specified path is not an I/O device.
# vparmodify -p vpar2 -d io:2.0.8
vparmodify: Error: "-d io:2.0.8": The device at the specified path is not an I/O device

Any Ideas?

Thanks

[Torsten.]

First look what is configured:

# vparstatus -v -p vpar2

[J Turner]

vparstatus -v -p vpar2
[Virtual Partition Details]
Name: vpar2
State: Up
Attributes: Dynamic,Autoboot,Nosearch
Kernel Path: /stand/vmunix
Boot Opts:

[CPU Details]
Min/Max: 1/16
User assigned [Path]:
Boot processor [Path]: 1.120
Monitor assigned [Path]: 1.123
1.124
1.125

Non-cell-specific:
User assigned [Count]: 0
Monitor assigned [Count]: 4
Cell-specific [Count]: Cell ID/Count


[IO Details]
2.0.0.2.0.6.0
2.0.0.3.0.6.0
2.0
2.0.0.2.0.6.0.0.0.0.0 BOOT
2.0.0.3.0.6.0.0.0.0.0,ALTBOOT

[Memory Details]
ILM, user-assigned [Base /Range]:
(bytes) (MB)
ILM, monitor-assigned [Base /Range]: 0x1e0000000/16384
(bytes) (MB)
ILM Total (MB): 16384

ILM Granularity (MB): 128

CLM, user-assigned [CellID Base /Range]:
(bytes) (MB)
CLM, monitor-assigned [CellID Base /Range]:
(bytes) (MB)
CLM (CellID MB):

CLM Granularity (MB): 128

[Torsten.]

Look,

[IO Details]
2.0.0.2.0.6.0
2.0.0.3.0.6.0
2.0
2.0.0.2.0.6.0.0.0.0.0 BOOT
2.0.0.3.0.6.0.0.0.0.0,ALTBOOT


this is not this good.
Resource 2.0 is assigned, so this means all below this system bus adapter.

If you want to remove 2.0.8, you need IMHO to remove "2.0" first and add all remaining needed LBAs.

[J Turner]

But the boot devices are below 2/0.
How would I go about the reconfiguration.
And what does IMHO stand for?

[Torsten.]

In My Humble/Honest Opinion

As long as the SBA 2.0 is assigned to this vpar, all LBAs are assigned.

I would record the configuration details and simply delete and re-create this vpar.

This does not harm the OS installation on the boot disk.

[J Turner]

This is a SG failover node on Itanium rx8640.
Would it seem reasonable to do a make_net_recovery, shutdown the vpar, delete it and recreate, with out using make_net_recovery?

[Torsten. · Accepted solution]

It is always a good idea to have a backup, but if you delete the vpar you won't change anything on the boot disks (except the vpdb in /stand - backup this file).

The current config does not look very well.

As mentioned earlier, assigning the whole SBA does not make so much sense.

These entries don't make any sense at all:

2.0.0.2.0.6.0
2.0.0.3.0.6.0

because they are already covered.

I would record the information from

# vparstatus -v -p vpar2
# vparstatus -v
# vparstatus
and
# ioscan -fn

think about what LBA's I would need in future, delete the vpar and re-create.



Finally think about what resources to assign to what vPar. IMHO it makes more sense to spread the assigned slots over the IO chassis, e.g. 1 FC card in IO bay 0, one card in IO bay 1 and so on ... but maybe the other IO chassis is allocated by vpar1 the same way.

[J Turner]

I did have to do this same thing to another vpar I inherited...
Thanks for all your advice, I will do this today and post the outcome