same 5.1B?

[watermelonyu]

We have many Alpha servers. This was upgraded to 5.1B by HP CE. However, when we check as below, the output are different? Why? Is the same OS version? What's different?

---------

node05

------

# uname -a

OSF1 node05 P5.1 1017 alpha

# sizer -v

Compaq Tru64 UNIX P5.1B (Rev. 1017); Wed Jun 16 04:41:52 EDT 2004

-----

node01

-----

# uname -a

OSF1 node01 V5.1 2650 alpha

# sizer -v

Compaq Tru64 UNIX V5.1B (Rev. 2650); Sun Dec 5 04:19:00 CST 2004

[watermelonyu]

可以看看

#dupatch -track -type kit

的output 嗎

[watermelonyu]

Hello Eric:



What is the patch installed on each machine?



Is it a standalone machine or a member of TruCluster?



Please post the data for checking.



Best Regards

Danny Lin

[watermelonyu]

Hello Denny,



HP CE added some cards on node05.

After above, HP CE booted generic kernel on node05 in order to reduce downtime.

Normally, HP CE should do kernel after changing any H/W.



Therefore node05 is P5.1B now. Can you tell me what the difference between boot generic kernel and do kernel?



Thanks



Eric

[watermelonyu]

Hello Eric:



Yes, if you boot the system by using /genvmunix; then you will see the node5 has P5.1 displayed.



The /genvmunix is used by CE when he add some new H/Ws that are not included drivers in current /vmunix, after booting up he/she can build new kernel to include drivers for new H/Ws. and If you have TruCluster, and when you use "add_new_member" to create new member, then after running "add_new_member", the new node must boot from /genvmunix to build new kernel then it can be running with new kernel and join TruCluster successfully.



Best Regards

Danny Lin

[watermelonyu]

Hello:



I am very sorry that I made typing mistake, the "add_new_member" should be "clu_add_member"



Best Regards

Danny