I have a task to connect 2 servers using a cross-over cable (but with
a twist).


                SWITCH
                     |
                     |
 Server-A -  [NIC-A1 , NIC-A2]
                                    /
                                   /
                             x-over cable
                                /
                               /
      Server-B -    [NIC-B1 , NIC-B2]



NIC-A1 is the only interface connected to a switch. I need to connect
Server-B to the same switch but have no more switch ports.

My idea (may be silly) is to run a x-over cable from NIC-A2 to NIC-B1
and thus be on the same VLAN as NIC-A1.
For this, I need to somehow internally bridge NIC-A1 and NIC-A2 so
when I run the x-over cable, NIC-B1 will be part of the same segment.
Then I can assign IP to NIC-B1 and have my L2 connection via Server-A.
Is this at all doable???

Thanks
Ron

On 2/29/2012 5:44 PM, unix wrote:
> I have a task to connect 2 servers using a cross-over cable (but with
> a twist).
>
>
>                  SWITCH
>                       |
>                       |
>   Server-A -  [NIC-A1 , NIC-A2]
>                                      /
>                                     /
>                               x-over cable
>                                  /
>                                 /
>        Server-B -    [NIC-B1 , NIC-B2]
>
>
>
> NIC-A1 is the only interface connected to a switch. I need to connect
> Server-B to the same switch but have no more switch ports.
>
> My idea (may be silly) is to run a x-over cable from NIC-A2 to NIC-B1
> and thus be on the same VLAN as NIC-A1.
> For this, I need to somehow internally bridge NIC-A1 and NIC-A2 so
> when I run the x-over cable, NIC-B1 will be part of the same segment.
> Then I can assign IP to NIC-B1 and have my L2 connection via Server-A.
> Is this at all doable???
>
> Thanks
> Ron

Hi Ron,

i don't think it will work that way. i'm not aware of any 
switching/bridging function within solaris. however, you may connect 
server-b the very same way as you have described but use a different 
network address on the nic-a2 and nic-b2. that way you can simply use 
server-a as a router/default-gateway for server-b. keep in mind to have 
a route back to this network.

   switch (route 10.1.2.0/24 via 10.1.1.20)
     |
     |
10.1.1.20/24
  [nic-a1   |    nic-a2]    Server-A
               10.1.2.1/24
                   |
                   |
               10.1.2.2/24
  [nic-a1   |    nic-a2]    Server-A


i don't think it's a good idea to route traffic that way and make one 
machine depend on another one. you should somehow get a free switch 
port. either by replacing the existing switch with one that offers more 
ports or by adding a second one. i guess that getting a 5-port netgear 
switch in place would be much easier.

regards
markus

ct,
-- 
Das Abspringen einer Begrenzungsmauer dient nicht dem direkten 
Zur�cklegen des Arbeitsweges.
http://www.rz-amper.de

unix <unixzip@yahoo.com> writes:
>My idea (may be silly) is to run a x-over cable from NIC-A2 to NIC-B1
>and thus be on the same VLAN as NIC-A1.
>For this, I need to somehow internally bridge NIC-A1 and NIC-A2 ..

Solaris doesn't include any sort of L2 bridging daemon.

Linux has one, but it chows CPU in order to do its function. You could
take a big hit on server 1, if server 2 burps a lot of data. 

The best way to deal with it would be to throw in a cheap desktop
switch until you can get more infrastructure ports for your server stuff.
Even the 5-port dumb GigE switches are small and cheap.