Adding NIC card to a running vpar

[Vee_1]

Hello Everyone,
We have 5 vpars running in one of the npars.We are in demand of adding one more NIC card to the existing vpar(vpar1).We have to take the NIC card from the decommissioned vpar also in same npar.Please assist me how can i get the details to add this NIC from the availabe resources.Though am getting details from the vparstatus -A ,am not able to get resource details since its only giving the availabe resources.Not sure which one is the NIC card hardware path.Awaiting for all of your updates on this.

[Duncan Edmonstone]

You mean you don't have documentation telling you whcih card is in which slot on the server - tsk tsk ;o)

If you don't have an old ioscan from the decomissioned vPars or something like that, you'll have to go and eyeball the server manually armed with your vparstatus -A output... If you aren't sure what IO paths from vparstatus -A are associated with which IO slot, then post the output of:

model
vparstatus -A

here and we should be able to tell you...

If this is a Superdome we might need some parstatus outputs as well to figure put whcih IOX are connected to which cells.

HTH

Duncan

[Vee_1]

Dun, thanks for the update.Here are the details.Please post me how to check with this details.
Please see the attachment also.

MP:CM> cp

-------------------------------+
Cabinet | 0 | 1 |
-------------+--------+--------+
Slot |01234567|01234567|
-------------+--------+--------+
Partition 0 |XXXXXXX.|........|
Partition 1 |........|X.XX....|

[] MP:CM> io

--------------------------+
Cabinet | 0 | 1 |
--------+--------+--------+
Slot |01234567|01234567|
--------+--------+--------+
Cell |XXXXXXX.|X.XX....|
IO Cab |0.0.0.0.|1.1.....|
IO Bay |1.0.1.0.|1.0.....|
IO Chas |3.1.1.3.|3.1.....|

vparstatus -A
[Unbound CPUs (path)]: 4.16
4.17
5.10
5.11
5.12
5.13
5.14
5.15
5.16
5.17
6.10
6.11
6.12
6.13
6.14
6.15
6.16
6.17
[Available CPUs]: 18

[Available I/O devices (path)]: 0.0.8
2.0.0
2.0.8
2.0.14
4.0.3
4.0.6
4.0.8
4.0.9
4.0.11
6.0.0
6.0.6
6.0.8
6.0.9
6.0.11
6.0.12

[Unbound Memory (Base /Range)]: 0x10000000/512
(bytes) (MB) 0x48000000/896
0x3c5c000000/14400
0x4000000000/24448
[Available Memory (MB)]: 40256

[Vivek_Pendse]

You can run lanscan & vparstatus -v -p on each vpar & check the hw paths which are being used & are free.
vparstatus -A --> can you give you the free resources across npar of all vpars.

The downtime will be required to add new lan card. & even to remove lan card from running vpar.

Thanks,
Vivek

[Duncan Edmonstone · Accepted solution]

OK, so I guess this change is for a vPar in nPar 0, as all the available paths you list are for cells 0, 2, 4 and 6.

You are still going to have to physically eyebeall the system (or get someone to do it for you), but we can at least tell you where to look.

In terms of where the available slots are located - you need to look in the following slots:


0.0.8 - IO Chassis attached to cell board 1 : Cab 0, IO Bay 1, Chassis 3 - (rear of cabinet, right hand chassis) - Slot 11
2.0.0 - IO Chassis attached to cell board 2 : Cab 0, IO Bay 0, Chassis 1 - (front of cabinet, left hand chassis) - Slot 0
2.0.8 - IO Chassis attached to cell board 2 : Cab 0, IO Bay 0, Chassis 1 - (front of cabinet, left hand chassis) - Slot 11
2.0.14 - IO Chassis attached to cell board 2 : Cab 0, IO Bay 0, Chassis 1 - (front of cabinet, left hand chassis) - Slot 6
4.0.3 - IO Chassis attached to cell board 4 : Cab 0, IO Bay 1, Chassis 1 - (read of cabinet, left hand chassis) - Slot 3
4.0.6 - IO Chassis attached to cell board 4 : Cab 0, IO Bay 1, Chassis 1 - (read of cabinet, left hand chassis) - Slot 5
4.0.8 - IO Chassis attached to cell board 4 : Cab 0, IO Bay 1, Chassis 1 - (read of cabinet, left hand chassis) - Slot 11
4.0.9 - IO Chassis attached to cell board 4 : Cab 0, IO Bay 1, Chassis 1 - (read of cabinet, left hand chassis) - Slot 10
4.0.11 - IO Chassis attached to cell board 4 : Cab 0, IO Bay 1, Chassis 1 - (read of cabinet, left hand chassis) - Slot 8
6.0.0 - IO Chassis attached to cell board 6 : Cab 0, IO Bay 0, Chassis 3 - (front of cabinet, right hand chassis) - Slot 0
6.0.6 - IO Chassis attached to cell board 6 : Cab 0, IO Bay 0, Chassis 3 - (front of cabinet, right hand chassis) - Slot 5
6.0.8 - IO Chassis attached to cell board 6 : Cab 0, IO Bay 0, Chassis 3 - (front of cabinet, right hand chassis) - Slot 11
6.0.9 - IO Chassis attached to cell board 6 : Cab 0, IO Bay 0, Chassis 3 - (front of cabinet, right hand chassis) - Slot 10
6.0.11 - IO Chassis attached to cell board 6 : Cab 0, IO Bay 0, Chassis 3 - (front of cabinet, right hand chassis) - Slot 8
6.0.12 - IO Chassis attached to cell board 6 : Cab 0, IO Bay 0, Chassis 3 - (front of cabinet, right hand chassis) - Slot 7


So go look at each of those slots and see what card you have in there - any 10BaseT / 100BaseT / 1000BaseT cards should have the usual RJ45 network port. The slot numbers hsould be labelled on the actual IO chassis.

If you are wondering how I figured out the IO slot numbers from the HW paths, see figure 37 on p282 of the vPars manual here:

http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c02732529/c02732529.pdf


If you have any choice over the cards to use, try and use a card that is attached to the same cell board as the majority of the bound CPUs for the vPar you are adding the card to.

HTH

Duncan

[Duncan Edmonstone]

Ach! typo made worse by cut & paste! Obviously I mean "rear" not "read" :

0.0.8 - IO Chassis attached to cell board 1 : Cab 0, IO Bay 1, Chassis 3 - (rear of cabinet, right hand chassis) - Slot 11
2.0.0 - IO Chassis attached to cell board 2 : Cab 0, IO Bay 0, Chassis 1 - (front of cabinet, left hand chassis) - Slot 0
2.0.8 - IO Chassis attached to cell board 2 : Cab 0, IO Bay 0, Chassis 1 - (front of cabinet, left hand chassis) - Slot 11
2.0.14 - IO Chassis attached to cell board 2 : Cab 0, IO Bay 0, Chassis 1 - (front of cabinet, left hand chassis) - Slot 6
4.0.3 - IO Chassis attached to cell board 4 : Cab 0, IO Bay 1, Chassis 1 - (rear of cabinet, left hand chassis) - Slot 3
4.0.6 - IO Chassis attached to cell board 4 : Cab 0, IO Bay 1, Chassis 1 - (rear of cabinet, left hand chassis) - Slot 5
4.0.8 - IO Chassis attached to cell board 4 : Cab 0, IO Bay 1, Chassis 1 - (rear of cabinet, left hand chassis) - Slot 11
4.0.9 - IO Chassis attached to cell board 4 : Cab 0, IO Bay 1, Chassis 1 - (rear of cabinet, left hand chassis) - Slot 10
4.0.11 - IO Chassis attached to cell board 4 : Cab 0, IO Bay 1, Chassis 1 - (rear of cabinet, left hand chassis) - Slot 8
6.0.0 - IO Chassis attached to cell board 6 : Cab 0, IO Bay 0, Chassis 3 - (front of cabinet, right hand chassis) - Slot 0
6.0.6 - IO Chassis attached to cell board 6 : Cab 0, IO Bay 0, Chassis 3 - (front of cabinet, right hand chassis) - Slot 5
6.0.8 - IO Chassis attached to cell board 6 : Cab 0, IO Bay 0, Chassis 3 - (front of cabinet, right hand chassis) - Slot 11
6.0.9 - IO Chassis attached to cell board 6 : Cab 0, IO Bay 0, Chassis 3 - (front of cabinet, right hand chassis) - Slot 10
6.0.11 - IO Chassis attached to cell board 6 : Cab 0, IO Bay 0, Chassis 3 - (front of cabinet, right hand chassis) - Slot 8
6.0.12 - IO Chassis attached to cell board 6 : Cab 0, IO Bay 0, Chassis 3 - (front of cabinet, right hand chassis) - Slot 7


HTH

Duncan

[Vee_1]

I found the NIC card which needs to be added to the existing vpar.May i know whether it need a reboot or not..?

[Torsten.]

If you could tell what your system model is (Superdome sx1000 vs. sx2000 // PCI-x I/O chassis vs. mixed PCI-e I/O chassis), the cell assignment (MP:CM> cp) and the slot of the NIC card, someone can tell you the h/w path to this card.


A previous saved ioscan would make this easier.


Then you need to shutdown the vPar, add the slot (command performed from another vPar) and finally start the vPar again - done.