Automatic Auxiliary path?

[chk]

Hi there

Have a little problem with our two identical configured DSS V6 servers.

In both servers we have 3 active network cards:


eth0: 172.16.100.X (management interface)
eth3: 192.168.100.X (iSCSI virtual IP)
eth5: 192.168.10.X (replication)

The auxiliary paths are configured at eth3 and eth5

So, when we start our failover, it automatically configures eth0 as a third auxiliary path. But only on the secondary server.

I can't find any configuration mismatch on the servers.

In the failover screen, it says that the primary server uses eth3 and eht5 and the service is OK.
At the secound server it says eth3, eth5, and eth0 is used, with a failed connection on eth0 and a degraded failover service.

So, where is the problem?

Thanks

[To-M]

Can you send screen shots of both servers? Also is the Target names and SCSI IDs the same? You can also try submitting a support ticket with the log files so we can see what is going on, make sure to have the same versions as well.

[Gr-R]

It would be better to use the management IPs for the aux connection as these are routable.
Using the iscsi connection can be OK, but if that path is busy with IO, you will likely get messages the aux path is down on that link due to traffic and ping delays.
You can of course use all 3 if you want to.

[chk]

Can you send screen shots of both servers?

Hi

Which Screens do you want?
Also, where should i send the log file to?

Thanks

[To-M]

Send screens of the NICs from the Setup > Network and from the Volume Replication. Submitting a support ticket is done from our main website on the top where the User Portal login and password that you setup when you purchased the DSS V6.

[chk]

Here are some screens...

[chk]

Here are some screens....

Bild "dss03_net8wu0g.jpg" anzeigen.
Bild "dss04_net54utg.jpg" anzeigen.
Bild "dss03_rep30u9w.jpg" anzeigen.
Bild "dss04_repqtuzh.jpg" anzeigen.

[To-M]

Those look ok, now check that you take off any Unicast for the NICs in Failover, use the broadcast method. This document demonstrates the steps, most you know, just review the Failover steps. Also check that you can ping all and both ways.


http://www.open-e.com/service-and-su...-to-resources/
Open-E iSCSI and NFS Failover:
Open-E DSS V6 Synchronous Volume Replication with Failover over a LAN (broadcast)

[chk]

I tried to post some screens herer, but i get a message, that a moderator has to check my post first...

[To-M]

I did see your other screen shots posted, so not sure why. Can you send logs to support from your User Portal on the Open-E website, I am sure there is something that might in your connections causing the degraded mode.