LAN card isolated.

[Francesco_17]

Hi,

after configured the second package on node 2 the package activate fails cause incorrect lan communication.
Scenario: one cluster, two nodes (9000/800 L1000 servers model), one package actually configured up and running on node 1, B.11.00 os installed, three lan card each node installed (0 for earthbeat, 1 ip address associated, 2 standby). The cables is correct connected on nodes and cisco catalyst 5505. The lan2 (standby) of first node comunicate just with catalyst and itself not else. Probably this trouble cause the incorrect lan communication and the second package activation failure.
There is a way to force the package activation or it's impossible due lan incorrect communication?

Tanks.
Regards.
Francesco

[melvyn burnard]

If I understand you corectly, you apppear to have one of hte networks not talking to the others as it is supposed to.
You need to fix this for the package/cluster to work as expected.
Without the network operating correctly you will have problems, this is a basic requirement for serviceguard.

[Michael Steele_2]

Can you run cmscancl and attach the report? Note the lan to lan configuration status will be provided as well as the heartbeat and data status.

This doesn't sound right:

"...The lan2 (standby) of first node comunicate just with catalyst and itself not else..."

You can make a one node cluster to force the package up. Node1 one sounds like this.

Are you trying to bring the second package up on node1 or node2?

[Francesco_17]

Hi Frederick,

in attachment the scancl.out file as you requested.
I'm trying to bring up the second package on node2 (pebfra02).

Thank you.
Regards.
Francesco

[melvyn burnard]

Well your networking is a mess!
according to hte binary, you should have lan2 backing up lan1 on both nodes.
But the linkloops show:
node fra01

lan1->lan0 WRONG
lan1->lan2 NO
lan2->lan1 NO


So htis is all wrong

and on hte ohter node:
lan2->lan1 OK
lan2->lan0 WRONG!
lan1->lan2 OK
lan1->lan0 Wrong

So you have majr networking issues. You MUST get these fixed for SG to work correcty

[Michael Steele_2]

"pebfra01" has some cable and configuration problems.

------ lan0 to lan1 ------
PPA 0 link test to 0x001083F744F6 (NO CONNECTION)

------ lan0 to lan2 ------
PPA 0 link test to 0x001083F7448E (NO CONNECTION)

------ lan1 to lan0 ------
PPA 1 link test to 0x00306E033AE6 -- OK

------ lan1 to lan2 ------
PPA 1 link test to 0x001083F7448E (NO CONNECTION)

------ lan2 to lan0 ------
PPA 2 link test to 0x00306E033AE6 (NO CONNECTION)

------ lan2 to lan1 ------
PPA 2 link test to 0x001083F744F6 (NO CONNECTION)


Here's what (pebfra02) looks like:

------ lan0 to lan1 ------
PPA 0 link test to 0x001083F744E2 (NO CONNECTION)

------ lan0 to lan2 ------
PPA 0 link test to 0x001083F734FF (NO CONNECTION)

------ lan1 to lan0 ------
PPA 1 link test to 0x00306E06669D -- OK

------ lan1 to lan2 ------
PPA 1 link test to 0x001083F734FF -- OK

------ lan2 to lan0 ------
PPA 2 link test to 0x00306E06669D -- OK

------ lan2 to lan1 ------
PPA 2 link test to 0x001083F744E2 -- OK

[Francesco_17]

Ok I'll try to fix it. Now I need to know wich is the correct lan configuration in my case.

Thanks.
Francesco

[melvyn burnard]

well it is your configuration, so you should know what it needs to be.
The best way is to look at what the binary for SG has, and that is in the cmcscancl output file.
namely:
lan1 and lan2 need to be connected to each other on both nodes, and to each other on the other node.
lan0 talks to lan0 on the other node.

[Michael Steele_2]

Here is the scheme from pebfra02 to follow to begin with:

(pebfra02)


------ lan0 to lan1 ------
PPA 0 link test to 0x001083F744E2 (NO CONNECTION)

------ lan0 to lan2 ------
PPA 0 link test to 0x001083F734FF (NO CONNECTION)

------ lan1 to lan0 ------
PPA 1 link test to 0x00306E06669D -- OK

------ lan1 to lan2 ------
PPA 1 link test to 0x001083F734FF -- OK

------ lan2 to lan0 ------
PPA 2 link test to 0x00306E06669D -- OK

------ lan2 to lan1 ------
PPA 2 link test to 0x001083F744E2 -- OK

[melvyn burnard]

As the post previous to this one shows, you have lans talking to lans they should not, and lans talking in one direction only.