serviceguard and trunking

[THEUNISSEN, J]

Dear all,

I've a question from one of our customers about trunking different VLANs in a high availabiltiy environment. We now have a Serviceguard solution with a heartbeat lan (VLAN1), an active and standby lan (VLAN2). The packages we defined in the VLAN2 as well. The customer however wants to have a VLAN3 for the active and standby lan and the packages remain in VLAN2. I think this is not possible in MC/Serviceguard, am I right? Or is trunking possible on the same lan card (different VLANs on the same lan card is supported?). The servers are HP Integrity rx4640 servers running HP-UX 11.23. The lan cards are:

# ioscan -fnC lan
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
lan 0 0/1/2/0 iether CLAIMED INTERFACE HP AB352-60001 PCI/PCI-X
1000Base-T Dual-port Core
lan 1 0/1/2/1 iether CLAIMED INTERFACE HP AB352-60001 PCI/PCI-X
1000Base-T Dual-port Core
lan 2 0/5/1/0 igelan CLAIMED INTERFACE HP A6825-60101 PCI 1000Ba
se-T Adapter

where lan 0 will be heartbeat lan, lan 1 will be active lan, lan 2 will be standby lan.

[Calandrello]

sorry friend, nao I understood very wellâ ¦ could explain better?

[Rita C Workman]

Well, I may be having a blonde moment, but if I understand you ... your customer wants to introduce another VLAN into the package, while not putting the packages into the new VLAN.
....problem I see is subnet. Wouldn't the new VLAN have a seperate subnet ? That could be a problem for local automated failover.

Now I'm not saying you can't do this, as having packages fail to different subnets can be done. But it becomes a manual intervention. In other words, your package will NOT failover until you reset your hostfile and DNS (if you use that) to resolve the package name to the new IP/subnet.

So....if the customers intent is to stop automatic failover, then do it. But if the customer expects to see automated local failover....then you might want to explain this fact to them.

..ps....we do this, but only for DR-remote site failover. I do not recommend this for local.

Kindest regards,
Rita

[THEUNISSEN, J]

The customer wants two VLAN's on the same lan interface (one VLAN containing the host ip address and one VLAN containing the package ip address) and I wonder if this can be done.

[Heironimus]

Putting one interface on multiple VLANs should be possible with the HP-UX VLAN software. Your network hardware will need to be configured to use tagged VLANs on those ports, which might make your network people unhappy.

That being said, I don't know if you can do what you want with the SG packages. And I don't know if it would be a good idea even if it does work.

[Bill Costigan]

You might have to give the SG nodes addresses in both VLANs, even if you never send traffic to one set of addresses.

Let's assume VLAN1 is 10.10.10.x
and VLAN2 is 10.20.20.x (package VLAN)

If the node doesn't have an address on the 10.20.20.x then there is no subnet 10.20.20.0 defined.

The package configuration file needs to specify the subnet 10.20.20.0 and the package IP address within that subset. But you don't define the rest of the parameters necessary to do the ifconfig. (e.g. LAN#, subnet mask etc.)

The package assumes the subnet was already configured.