Clustering Problem

ashkan · #1 (**permalink**) 06-28-2009, 11:05 AM

Dear All,
I have two ASG 525 appliances.
I want to cluster these two appliances.
So, I bought valid license for this issue.(2 nodes Cluster).
I configured the appliance that license issued for it as master(Device Node ID:1 and eth1 for cluster).
Then I configured the another appliance as slave(Device Node ID:2 and eth1 for cluster).
I linked these two appliance via straight CAT6 patch cord.

On web management of master appliance I can see the two appliance but the status of slave appliance is UNLINKED!!why?

Can anybody help me?

Thank you.
Best regards.
Ashkan.

BAlfson · #2 (**permalink**) 06-28-2009, 01:18 PM

Is this a cross-over cable?

dilandau · #3 (**permalink**) 06-28-2009, 10:36 PM

From my experience when you have UNLINKED status it means that an interface(s) on the slave device are not connected in the same manner as the master. Both devices need to be cabled exactly the same.

This is a description of UNLINKED from the help file:

"UNLINKED: One ore more interface links are down"

ashkan · #4 (**permalink**) 06-29-2009, 05:24 AM

Quote:

Originally Posted by BAlfson

Is this a cross-over cable?

Yes.It's a crossover cable.
Although it;s not so important, because of ASG-525 support MDIX on their interfaces.

ashkan · #5 (**permalink**) 06-29-2009, 05:28 AM

Quote:

Originally Posted by dilandau

From my experience when you have UNLINKED status it means that an interface(s) on the slave device are not connected in the same manner as the master. Both devices need to be cabled exactly the same.

This is a description of UNLINKED from the help file:

"UNLINKED: One ore more interface links are down"

thanks for your reply.
You means that i have to connect slave unit like master unit to my network exactly?
But, I read that I just connect master unit to my network and connect slave unit to master unit with a crossover cable.I have been confused.

tkaufi · #6 (**permalink**) 06-29-2009, 01:13 PM

hi,

i´ve a ASG 220 Cluster and i´ve found the best cabeling way for the cluster is to

eth0 to WAN
eth1 to LAN
eth3 for link between the two ASGs. (direct cable, no cross-over, even that does´nt matter)

for both of the machines

This prevents a total failure of Internet Access if one of the ASG went gone.

CU
Thomas

BAlfson · #7 (**permalink**) 06-29-2009, 01:26 PM

It sounds like you should read the documentation again. There's a new clustering article, # 305479, on the KnowledgeBase.

I suggest you rethink your interface assignments. In all of the documentation, the "default" connection for High Availabilty is Eth3. It will work with the way you'rve done it, but you will present a non-standard configuration to anyone who wannts to help you.

Good luck - Bob