Hi

I remember reading a while ago that it is supported to connect two ISIS 5000 System Directors in the same network.

Hoe can that be done?

We have two System Directors with live data on them, and we would like to connect both in the same network without backing up the data to an extranl storage, turning one of them to an expension and to add it to the primary system director.

I remember it is possible to connect both of them via 10gbe to the switch, and then the ISIS client will see two ISIS's in the Client Manager and will be able to choose into which one to connect.

I know i won't be able to mount workspaces from both of them at the same time. that is ok.

I just want to understand what is needed to configure it.

Thanks

two ISIS System directors in the same subnet (network) is NOT supported.  They have to be in different networks, or Subnets, else the storage managers can get confused as to which system director they belong to.

they CAN be cabled to the same switch, but the switch has to be segmented into different networks, and have routing enabled between the two networks, so that the clients connected to the switch can route to both System Directors.

Thanks

We have 2 system directors, 2 expension engines, 2 switches - each system is build from a system director, an expension engine and a switch

from what you are saying, i understand that these are my options:

1. Stuck/cascade the two switches, connect all system director and expension engines to the switchs, configure each system (system director+expension engine) as a diffrent network/subnet, configure routing so the clients will be able to see both networks, and configure a "Remote Host" on the clients.

2. Create two seperate systems with two different (not stucked) switches. - each system will be configure as a diffrent network/subnet.

each system (System= system director+expension engine+switch) will work seperatly as a stand alone system.

depending on the switch i will connect the clients to  - they will have accses to the first system or to the second system.

if these are the options, the first one seems better.

Thanks!

In addition to that workflow, can anyone explain how do i configure routing on the switchs?

We have 2 x system directors, 2 x expension engines, each system is build from a system director and an expension engine.

All engines (total of 4) connect to two s25n switches (stucked)

Each switch got an 10Gbe module (and a stuck moudle)

So - all clients+ two engines (system director +expension)  are connected to the main LAN - 192.168.1.x (using two stucked switches)

The two extra engines (system director + expnesion) are configured as static IP's with in a diffrent LAN - 192.168.2.x and connected via 10Gbe to the second switch.

How do i configure the 192.168.1.x network to see the 192.168.2.x netwrok and vica versa?

This is done via switch config? 

Thanks!