SG and lan-0

[Co van Berkel]

Hey,

We have a question.
We run on two rp4440-8 servers, HP-UX 11.11 and SG a.11.6 in one cluster.

These servers are connected to the network:
- lan-0 (core i/o, 10/100/1000 BT) - Heartbeat
- lan-1 (A5838A, PCI 2x 10/100 BT + 2x SCSI) - Data lan
- lan-2 (A5838A, PCI 2x 10/100 BT + 2x SCSI) - nvt
- lan-3 (A5838A, PCI 2x 10/100 BT + 2x SCSI) - Standby for lan-1
- lan-4 (A5838A, PCI 2x 10/100 BT + 2x SCSI) - nvt

Now we have the following question:
- Can we use the lan-0 (10/100/1000 BT) for the primary lan instead of lan-1 (10/100 BT)?
- Than use the lan-1 for the heartbeat?
- And use lan-4 for standby of lan-1 (HB)?
- How to configure this?

This becose of some network issues while running our backup (legato) over the data network. The 10/100 BT card is fully occupide making the backup.

Regards,
CvB.

[Steven E. Protter · Accepted solution]

Shalom,

Advice, do not configure the lan card doing the backups as part of the cluster, especially heartbeat.

Best practice for heartbeat is to have a private lan JUST for that.

To improve the backup speed and congestion the 1000 BaseT card should be reconfigured and connected to the network on the network that does the backups. That will require downtime and you should manually edit /etc/rc.config.d/netconf

Heartbeat will live quiet nicely on a private 100 BaseT lan, no problem, just change the cluster configuration file on both nodes and do the standard cmquerycl,cmcheckconf,cmapplycolnf

A mistake will bring down the node.

SEP

[Co van Berkel]

Hey Shalom,

I want to check of I understand you.

What I want to do is to set the heartbeat lan on lan-1 (is now lan-0) and the primary data lan on lan-0 (is now lan-1).
So then for the heartbeat there will be still a private lan (lan-0 --> lan-1) just for that.
Is this ok?

Is it possible to recongigure this without bringing down the cluster?

And a other question:
Can I configure two primary data lan connections, one 1000BT and one 100BT, in one package?
Then I need two I.P.-addresses and DNS-names?

Regards,
CvB

[melvyn burnard]

A best practice for Sg is to put the heartebat on ALL available confiugerd LAN's in the cluster.
To make a LAN available to be a standby lan, there must be connectivity between the standby LAN and it's primary.
using cmquerycl will check this an dshow it in the ascii file or the stdout report.
You can also use linkloop to check this

[Co van Berkel]

Hey Melvyn,

Hereby the current configuration:
NODE_NAME node-1
NETWORK_INTERFACE lan0
HEARTBEAT_IP x1.x1.x1.x1
NETWORK_INTERFACE lan1
HEARTBEAT_IP x2.x2.x2.x2
NETWORK_INTERFACE lan3
# Possible standby Network Interfaces for lan1: lan3.
# Warning: There are no standby network interfaces for lan0.

NODE_NAME node-2
NETWORK_INTERFACE lan0
HEARTBEAT_IP y1.y1.y1.y1
NETWORK_INTERFACE lan1
HEARTBEAT_IP y2.y2.y2.y2
NETWORK_INTERFACE lan3
# Possible standby Network Interfaces for lan1: lan3.
# Warning: There are no standby network interfaces for lan0.

How to configure a "standby network interface" for lan0?

We don't use lan2 and lan4 in the current situation. lan1 and lan2 are on one PCI-card
as lan3 and lan4.

Regards,
CvB.

[melvyn burnard]

you need to cabl ein one of the "free" LAN's sothat there is physical connectivity (you can test this with linkloop) between the :AN's you wish to be associated as a primary/standby pair.
Once this is done, using cmquerycl you shoul dthen see that this lan will have a comment that it could be used as a standby lan

[Co van Berkel]

Hey,

More info:
# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/1/2/0 0x00306EF44D01 0 UP lan0 snap0 1 ETHER Yes 119
0/2/1/0/6/0 0x00306E5E2B18 1 UP lan1 snap1 2 ETHER Yes 11
9
0/2/1/0/7/0 0x00306E5E2B19 2 UP lan2 snap2 3 ETHER Yes 11
9
0/6/1/0/6/0 0x00306E5E1BCC 3 UP lan3 snap3 4 ETHER Yes 11
9
0/6/1/0/7/0 0x00306E5E1BCD 4 UP lan4 snap4 5 ETHER Yes 11
9

# ifconfig lan0
lan0: flags=1843
inet x1.x1.x1.x1 netmask ffffffff broadcast x11.x11.x11.x11
# ifconfig lan1
lan1: flags=843
inet x2.x2.x2.x2 netmask ffffffff broadcast x22.x22.x22.x22
# ifconfig lan2
ifconfig: no such interface
# ifconfig lan3
lan3: flags=842
inet 0.0.0.0 netmask 0
# ifconfig lan4
ifconfig: no such interface

Regards,
Cvb.

[Co van Berkel]

Hey Melvyn,

We use a cross cable between the current lan-0 cards (heartbeat) of the nodes.
When we want a extra "standby network interface" for the current lan0 this will be a problem I think?
Because to act lan4 as a standby interface all interfaces, lan0 and lan4 on both nodes, should be able to connect to each other (linkloop)?

Right?

Regards,
CvB.

[melvyn burnard]

correct, to have a standby for lan0 you must remove the xover cable an dconnect it via a switch

[Co van Berkel]

Hey Melvin,

Thanks for your reactions.


Hey Steven, (Shalom)

Your advice was:
â Do not configure the lan card doing the backups as part of the cluster, especially heartbeat.â

But how can we backup data of a MC/SG package not using the package I.P. / DNS-name?
Or is it possible to use more than one I.P. and DNS-name to connect to one package?
When it is possible to use more than one I.P. and DNS-name than we can use a private lan and network interface for the backup?
Right?

Regards,
CvB.

[Co van Berkel]

Thanks for all info.
All is clear now.

Regards,
CvB