vPar create file can't accept comments

[Kevin_31]

Hello experts, I've got vPars A.01.01.00 running on hpux11.11. I'd like to be able to enter comments into the file I feed to vparcreate to document which io card is network, etc.

I've tried creating a file like the one below with "#" and ";" but they aren't accepted.

root: more vparcreate.vpar1*
-p vpar1
-a cpu::1
-a cpu:::1:8
-a cpu:101
-a mem::1024
-a io:1/8/0/0.1.16.0.0.6.4:BOOT
-a io:1/8/0/0
-a io:1/12/0/0
-b /stand/vmunix
-B auto


Is there another one I should try? Anyone a comment character that is accepted?

cheers,
Kevin

[harry d brown jr]

Kevin,

I just make my vPar create a "script", and in a script you can place comments:

vparcreate -p vpart1 -a cpu:33 -a mem::1280 -a io:0/0 -a io:0/0/2/0.6.0:boot
vparcreate -p vpart2 -a cpu:37 -a mem::1280 -a io:0/10 -a io:0/10/0/0.8.0.255.0.0.0:boot -a io:1/0
vparcreate -p vpart3 -a cpu:41 -a mem::1280 -a io:0/2 -a io:0/2/0/0.8.0.255.0.0.0:boot -a io:1/8
# comments can go here
vparcreate -p vpart4 -a cpu:45 -a mem::1280 # BUT NOT HERE BECAUSE OF CONTINUATION!!!
-a io:1/10 -a io:1/10/0/0.8.0.255.0.3.0:boot -a io:1/2



The IMPORTANT thing is to have the vparcreate command WITHIN the "script".

Keith, I've been screwing around with vPars for two years now, and finally we have acceptance and have it in production!!! eventually to be on 28+ N-class servers, each with 4 partitions!!



live free or die
harry

[harry d brown jr · Accepted solution]

Kevin

SORRY about that, the STUPID "subit" screws the continuation character, let me try that again:

vparcreate -p vpart1 \\ -a cpu:33 \\ -a mem::1280 \\ -a io:0/0 \\ -a io:0/0/2/0.6.0:boot
# comments can go here
vparcreate -p vpart2 \\ -a cpu:37 \\ -a mem::1280 \\ -a io:0/10 \\ -a io:0/10/0/0.8.0.255.0.0.0:boot \\ -a io:1/0
vparcreate -p vpart3 \\ -a cpu:41 \\### BUT NO COMMENTS BETWEEN CONTINUATION's
-a mem::1280 \\ -a io:0/2 \\ -a io:0/2/0/0.8.0.255.0.0.0:boot \\ -a io:1/8

live free or die
harry

[harry d brown jr]

Kevin

ONE more time?

vparcreate -p vpart1 \ -a cpu:33 \ -a mem::1280 \ -a io:0/0 \ -a io:0/0/2/0.6.0:boot
# comments can go here
vparcreate -p vpart2 \ -a cpu:37 \ -a mem::1280 \ -a io:0/10 \ -a io:0/10/0/0.8.0.255.0.0.0:boot \ -a io:1/0
vparcreate -p vpart3 \ -a cpu:41 \### BUT NO COMMENTS BETWEEN CONTINUATION's
-a mem::1280 \ -a io:0/2 \ -a io:0/2/0/0.8.0.255.0.0.0:boot \ -a io:1/8

live free or die
harry

[Kevin_31]

It's alright Harry, I understand what you're trying in submit.

I'll modify my input files to make them scripts then comment them to my heart's content.

cheers,
points assigned.

p.s. (I knew it would be you who'd answer, you're the vPar MAN!).

p.p.s. I've got 4 vPars bought for two of our Ns and 3 for each of our 2 L3K's. So far we've got live applications rolled out on one, rolled out but still in test mode of another, and the rest are my pet project.

thanks again for all your help Harry.

[harry d brown jr]

Kevin,

That's great! I'm glad to hear it's working for ya! We found that we need to go to Release 2.0 because we are booting from an EMC SAN. Just an FYI for ya!

live free or die
harry

[Kevin_31]

Interesting. I didn't realize release 2 was out yet. We've had no problems booting our vPars over our SAN, but we use Brocade switches and HP disks instead of EMC.

[harry d brown jr]

Yeah, we are using the mcNasty, I mean mcdata switches. THe issue is booting all partitions at the same time. If you boot one after the other, there is no issue. It was a flow control/timing issue for the pdc.

live free or die
harry

[Ryan Green]

The latest version of the vPar s/w is A.02.01.00 for T1335AC. Just installed on our dome.

What boot problem is Harry reffering to? Is it related to McData (not our choice, slected for us)? PDC?