Operating System - HP-UX
1832681 Members
3043 Online
110043 Solutions
New Discussion

Configuration in A.11.19.00

 
SOLVED
Go to solution
Carme Torca
Super Advisor

Configuration in A.11.19.00

Hi,

How I could apply one new configuration in the cluster. I could do it online, without stop?

Thanks a lot of,
Carmen.
Users are not too bad ;-)
8 REPLIES 8
Prasanth V Aravind
Trusted Contributor

Re: Configuration in A.11.19.00

Hi,

What configuration you want to apply ?? cluster conf or pbg conf ??


There are the modifications you can done in cluster..

Cluster Modifications

Change to Cluster Configuration Required Cluster State
Add a new node. All cluster nodes must be running.
Delete an existing node. A node can be deleted even if it is down or unreachable.
Change maximum configure packages. Cluster must not be running.
Change timing parameters. Cluster must not be running.
Change cluster lock configuration. Cluster must not be running.
Change serial heartbeat configuration. Cluster must not be running.
Change IP address for heartbeats. Cluster must not be running.
Change addresses of monitored subnets. Cluster must not be running.


Package Modifications

Change to Package Configuration Required Package State
Add a new package. Other packages can be running.
Remove a package. Package must be halted. Cluster can be running.
Add a new node. Package(s) may be running.
Remove a node. Package(s) may be running on different nodes.
Add/remove a new service process. Package must be halted.
Add/remove a new subnet. Package must be halted.

Cluster may need halting if subnet is new to the cluster.
Add/remove a new EMS resource. Package must be halted.

Cluster may need halting if EMS resource is new to the cluster.
Changes to the run/halt script contents Recommended that package be halted to avoid any timing problems while running the script.
Script timeouts Package may be running.
Service timeouts Package must be halted.
Failfast parameters Package must be halted.
Auto_Run Package may be running.
Local LAN failover Package may be running.
Change node adoption order. Package may be running.


Gudluclk
Prasanth
S-M-S
Valued Contributor

Re: Configuration in A.11.19.00

Hi Carme Torca,

What is the configuration you want to do in cluser?

Are you using MC Service guard ?

What is the version ?
S-M-S
Valued Contributor

Re: Configuration in A.11.19.00

Sorry , I gnore my last two question as its thre in the subject :-)
Carme Torca
Super Advisor

Re: Configuration in A.11.19.00

I need to add one new lvol in one package.
Users are not too bad ;-)
Prasanth V Aravind
Trusted Contributor

Re: Configuration in A.11.19.00

Yes .. its very simple & you can do it online.

GUdluck
Prasanth
Prasanth V Aravind
Trusted Contributor
Solution

Re: Configuration in A.11.19.00

these are the steps you need to follw.

Scan new disks (ioscan + insf)
Create new vgs & lvs
Export vg to map file
Import vg in all failover nodes
Deactivate vg (vgchange â a n vgname)
Make vg cluster aware (vgchange â c y vgname )
Active vg exclusively (vgchange â a e vgname )
Mount new new lvs manually with mount command
Take copy of /etc/cmcluster/pkg/pkg.cntl file
Edit /etc/cmcluster/pkg/pkg.cntl & add new vg, lv details
Copy pkg control files to all failover nodes

GUdluck
Prasanth
rariasn
Honored Contributor

Re: Configuration in A.11.19.00

Hi,

> I need to add one new lvol in one package

No problem.

- Create new lvol
- Update vgconfiguration in standby node (vgexport, vgimport)
- Modifiy control script in both nodes
- Mount FS in prymary node

rgs,
atul2701
Frequent Advisor

Re: Configuration in A.11.19.00

Following steps need to perform on your active node (where currently pkg is running).
-----------------------------------------
Check whether do you have enough space in VG or not, if not please add more disk in the VG.
Create new LV.
Create mount point.
Mount the file system.
Update pkg control script.
Create the map file for VG
Vgexport -p -s -m
Copy map file to all adoptive nodes.
Copy your pkg control script to all adoptive node (under /etc/cmcluster/ dir)
Note down the minor number of your VG.
Following steps need to perform on all adoptive nodes.
-------------------------------------------
Remove the vg using vgexport command.
Mkdir /dev/vgname
Mknod /dev/vgname/group c 64
Vgimport -s -m
Atul Gupta