LAN Traffic in SG

[joe_91]

Hi All:

We Currently have 1 package in HA (3 applications) in one node. We want to seperate one product out of the 3 and make it as a seperate package and also route that package thru a dedicated lan card. we have lan0 thru lan4. currently lan4 is backup for lan1. we are not doing any failover(since one node). given this scenario on N-class, 11.0, 64bit
the following would be my questions..
1. What do i require(hardware etc..) (my assumption would be one hard disk for the new package for the volume group..hope this is correct)
2.how would i route it thru a seperate LAN card?(lan0,lan2 and lan4 are free)
3. how well i can make use of the existing scripts?(since we are already doing all the three Applications as a single package, so we have the control, startup,shutdown, monitor scripts etc...)
4. Do i have to write some extra scripts?
5. Some sample scripts/tips etc...
Please Help Gurus.. I have to put in a Plan before i leave for the Long Weekend..

Thanks in Advance..
Joe.

[Steve Lewis]

I recommend that all Serviceguard changes are first tested on a test server, before rolling out the change to a live/production server. Be warned that it is easy to get things wrong with Serviceguard changes and testing is vital. HP consulting would take several days over this.

Your (documented) plan should address these things.

1. How about 2 disks (1 mirrored)? I recommend you put these into a new volume group, create any logical volumes and filesystems you need to.

2. Assign an IP to this lan card, not the package IP, but another IP that is on the same subnet, either using SAM or by editing your netconf file and hosts file and using ifconfig. This new subnet should be different to any other on your server. Then do the routing in your router. The clients connect to the package IP.

3. Create a new package within your cluster and check the max_configured_packages parameter is not exceeded. Use cmmakepkg. Include your new volume group, the subnet. You do not identify the network interface in MCSG as it knows how to route to it (netstat -r). MCSG will use any spare interface card in the cluster if it goes down.

4. Edit the new control script for the new package to add the package IP (cmmodnet) the volume group activation and any filesystems to be mounted. You will have to copy the existing package startup scripts and just use the relevent bits.

5. Re-configure your cluster to include the new package. Use cmcheckconf and only cmapplyconf if it is OK.

6. Test your configuration (cmmodpkg, reboot, lan failover tests etc).

Inform everybody about this new package IP, maybe update dns, nis, hosts files etc.

When you are happy with your testing implement your change on your production machine.

[joe_91]

Hi Steve:

Thank. Could explain the point no.2 please. I do not understand it at all. Please bear with me.

Thanks
Joe.

[Stephen Doud]

Hi Joe,

I placed an article for this topic in the ITRC technical database last fall.

Document ID: UMCSGKBRC00008178
"How to split a package into two packages"

I updated it today to make it more clear. The update should be available tomorrow. Of, if you want it today, email a request to hpcu@atl.hp.com using the Subject: "ITRC Forum request for Stephen Doud"

-s.

[Steve Lewis]

Hi joe,

The article mentioned above looks like a good place to explain it all. I forgot to talk about removing the application from your old package and haven't done it in quite a while so you are better off looking at that for more info.
What I meant in point 2 is this:
You are not supposed to have more than one interface card on each network, so if lan1 has for example 200.0.0.1 subnet ffffff00 then lan0/2/3/4 cannot also be assigned IPs in 200.0.0 You must make them something else, maybe 201.0.0.1 and then the package IP might be 201.0.0.2, for example.
You can check that the package IP has been added using ifconfig lanX:1 (or :2 :3 etc) where you have lots of IPs added to an interface. This means that if your clients connect through 200.0.0.X there will be some routing required to access IPs on 201.0.0