Backup server with two network interfaces.

Backup server with two network interfaces.

Post by Soojin K » Fri, 19 Jul 2002 19:16:33



Hi all,
During the client installation, I configure so that all the clients
are running the daemon "/usr/sbin/nsr/nsrexecd -s backup -s backup2".
The backup server has two network interfaces called backup and
backup2.
The usage of the second interface is hardly any.
# netstat -ni
Name  Mtu  Net/Dest      Address        Ipkts     Ierrs  Opkts  
Oerrs Collis Queue
lo0   8232 127.0.0.0     127.0.0.1      3001477    0     3001477   0  
  0      0
hme0  1500 192.168.1.0   192.168.1.80   601802621  4     261315655 0  
  0      0
hme1  1500 192.168.1.0   192.168.1.81   383168     0     323       0  
  0      0
I think it is because of the same MAC address of the two interfaces.
If I give a different MAC address on the second interface would the
backup clients send data through it?

I had a look at IP multipathing it only does the outbound load
balancing.(right?)

Thank you in advance.

 
 
 

Backup server with two network interfaces.

Post by Darren Dunha » Sat, 20 Jul 2002 02:05:32



> Hi all,
> During the client installation, I configure so that all the clients
> are running the daemon "/usr/sbin/nsr/nsrexecd -s backup -s backup2".

The hosts mentioned there are hosts which are allowed to begin backups.
It's an authorization control, not a backup interface setting.

Quote:> The backup server has two network interfaces called backup and
> backup2.
> The usage of the second interface is hardly any.
> # netstat -ni
> Name  Mtu  Net/Dest      Address        Ipkts     Ierrs  Opkts  
> Oerrs Collis Queue
> lo0   8232 127.0.0.0     127.0.0.1      3001477    0     3001477   0  
>   0      0
> hme0  1500 192.168.1.0   192.168.1.80   601802621  4     261315655 0  
>   0      0
> hme1  1500 192.168.1.0   192.168.1.81   383168     0     323       0  
>   0      0
> I think it is because of the same MAC address of the two interfaces.
> If I give a different MAC address on the second interface would the
> backup clients send data through it?

No.  You have to tell them to use it.

Since I see 'nsr' commands, you're using Solstice Backup or Legato
Networker.

Go into the client settings for a client.  One of the fields is "server
network interface" (I think it may be a hidden field).  Set that to the
interface you want the client to use on the server.  I'm guessing that
would be 'backup2' in your case.  Without that field set, it uses the
name of the server itself.

--

Unix System Administrator                    Taos - The SysAdmin Company
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

 
 
 

Backup server with two network interfaces.

Post by Soojin K » Sat, 20 Jul 2002 11:06:28




> > Hi all,
> > During the client installation, I configure so that all the clients
> > are running the daemon "/usr/sbin/nsr/nsrexecd -s backup -s backup2".

> The hosts mentioned there are hosts which are allowed to begin backups.
> It's an authorization control, not a backup interface setting.

I see.

Quote:> > The backup server has two network interfaces called backup and
> > backup2.
> > The usage of the second interface is hardly any.
> > # netstat -ni
> > Name  Mtu  Net/Dest      Address        Ipkts     Ierrs  Opkts  
> > Oerrs Collis Queue
> > lo0   8232 127.0.0.0     127.0.0.1      3001477    0     3001477   0  
> >   0      0
> > hme0  1500 192.168.1.0   192.168.1.80   601802621  4     261315655 0  
> >   0      0
> > hme1  1500 192.168.1.0   192.168.1.81   383168     0     323       0  
> >   0      0
> > I think it is because of the same MAC address of the two interfaces.
> > If I give a different MAC address on the second interface would the
> > backup clients send data through it?

> No.  You have to tell them to use it.

> Since I see 'nsr' commands, you're using Solstice Backup or Legato
> Networker.

Yes.
> Go into the client settings for a client.  One of the fields is "server
> network interface" (I think it may be a hidden field).  Set that to the
> interface you want the client to use on the server.  I'm guessing that
> would be 'backup2' in your case.  Without that field set, it uses the
> name of the server itself.

I can't find the file to set the interface.
I was thinking because of the same MAC address it will use the same
interface (hme0).
When I ping the hme1 interface and do snoop on the hme0 interface.
# snoop -d hme0 | grep backup2
Using device /dev/hme (promiscuous mode)
     server1 -> backup2      ICMP Echo request (ID: 10447 Sequence
number: 0)
     backup2 -> server1      ICMP Echo reply (ID: 10447 Sequence
number: 0)
     server1 -> backup2      ICMP Echo request (ID: 10447 Sequence
number: 2)
     backup2 -> server1      ICMP Echo reply (ID: 10447 Sequence
number: 2)
     server1 -> backup2      ICMP Echo request (ID: 10447 Sequence
number: 5)
     backup2 -> server1      ICMP Echo reply (ID: 10447 Sequence
number: 5)
     server1 -> backup2      ICMP Echo request (ID: 10447 Sequence
number: 6)
     backup2 -> server1      ICMP Echo reply (ID: 10447 Sequence
number: 6)
     server1 -> backup2      ICMP Echo request (ID: 10447 Sequence
number: 7)
     backup2 -> server1      ICMP Echo reply (ID: 10447 Sequence
number: 7)

Thank you.

 
 
 

Backup server with two network interfaces.

Post by Darren Dunha » Sun, 21 Jul 2002 00:28:33



>> Go into the client settings for a client.  One of the fields is "server
>> network interface" (I think it may be a hidden field).  Set that to the
>> interface you want the client to use on the server.  I'm guessing that
>> would be 'backup2' in your case.  Without that field set, it uses the
>> name of the server itself.
> I can't find the file to set the interface.

It's not a file (well, you don't edit it that way anyway).  It's the
networker client configuration.  You can edit it in the gui (I think
it's 'nwadmin') or via command line ('nsradmin').  You edit it the same
way you do other Networker configuration changes.

Quote:> I was thinking because of the same MAC address it will use the same
> interface (hme0).

No.  Unless the interfaces are on the same physical network, or unless
they're tied into the same piece of equipment that gets confused by the
MAC addresses, there should be no problem.

Quote:> When I ping the hme1 interface and do snoop on the hme0 interface.
> # snoop -d hme0 | grep backup2
> Using device /dev/hme (promiscuous mode)
>      server1 -> backup2      ICMP Echo request (ID: 10447 Sequence
> number: 0)
>      backup2 -> server1      ICMP Echo reply (ID: 10447 Sequence
> number: 0)

Do you see anything on the hme1 interface?

--

Unix System Administrator                    Taos - The SysAdmin Company
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

 
 
 

Backup server with two network interfaces.

Post by Soojin K » Tue, 23 Jul 2002 18:28:06


Thank you for your help.
I found the field called "Server network Interface". I add the host
name of the second interface. It first couldn't write to hme1 so I
gave a new MAC address to the hme1 and now the backup data goes
through the hme1.
I might be to do with the Cisco catalyse 4000 switch.
I was wondering if anyone knows whether it will do a load balancing if
I specify two network interfaces (hme0 and hme1) in the "Server
network Interface" field.

Thanks in advance.



> > > Hi all,
> > > During the client installation, I configure so that all the clients
> > > are running the daemon "/usr/sbin/nsr/nsrexecd -s backup -s backup2".

> > The hosts mentioned there are hosts which are allowed to begin backups.
> > It's an authorization control, not a backup interface setting.

> I see.

> > > The backup server has two network interfaces called backup and
> > > backup2.
> > > The usage of the second interface is hardly any.
> > > # netstat -ni
> > > Name  Mtu  Net/Dest      Address        Ipkts     Ierrs  Opkts  
> > > Oerrs Collis Queue
> > > lo0   8232 127.0.0.0     127.0.0.1      3001477    0     3001477   0  
> > >   0      0
> > > hme0  1500 192.168.1.0   192.168.1.80   601802621  4     261315655 0  
> > >   0      0
> > > hme1  1500 192.168.1.0   192.168.1.81   383168     0     323       0  
> > >   0      0
> > > I think it is because of the same MAC address of the two interfaces.
> > > If I give a different MAC address on the second interface would the
> > > backup clients send data through it?

> > No.  You have to tell them to use it.

> > Since I see 'nsr' commands, you're using Solstice Backup or Legato
> > Networker.

>  Yes.
> > Go into the client settings for a client.  One of the fields is "server
> > network interface" (I think it may be a hidden field).  Set that to the
> > interface you want the client to use on the server.  I'm guessing that
> > would be 'backup2' in your case.  Without that field set, it uses the
> > name of the server itself.
> I can't find the file to set the interface.
> I was thinking because of the same MAC address it will use the same
> interface (hme0).
> When I ping the hme1 interface and do snoop on the hme0 interface.
> # snoop -d hme0 | grep backup2
> Using device /dev/hme (promiscuous mode)
>      server1 -> backup2      ICMP Echo request (ID: 10447 Sequence
> number: 0)
>      backup2 -> server1      ICMP Echo reply (ID: 10447 Sequence
> number: 0)
>      server1 -> backup2      ICMP Echo request (ID: 10447 Sequence
> number: 2)
>      backup2 -> server1      ICMP Echo reply (ID: 10447 Sequence
> number: 2)
>      server1 -> backup2      ICMP Echo request (ID: 10447 Sequence
> number: 5)
>      backup2 -> server1      ICMP Echo reply (ID: 10447 Sequence
> number: 5)
>      server1 -> backup2      ICMP Echo request (ID: 10447 Sequence
> number: 6)
>      backup2 -> server1      ICMP Echo reply (ID: 10447 Sequence
> number: 6)
>      server1 -> backup2      ICMP Echo request (ID: 10447 Sequence
> number: 7)
>      backup2 -> server1      ICMP Echo reply (ID: 10447 Sequence
> number: 7)

> Thank you.

 
 
 

Backup server with two network interfaces.

Post by Darren Dunha » Wed, 24 Jul 2002 01:50:38



> Thank you for your help.
> I found the field called "Server network Interface". I add the host
> name of the second interface. It first couldn't write to hme1 so I
> gave a new MAC address to the hme1 and now the backup data goes
> through the hme1.
> I might be to do with the Cisco catalyse 4000 switch.
> I was wondering if anyone knows whether it will do a load balancing if
> I specify two network interfaces (hme0 and hme1) in the "Server
> network Interface" field.

I don't believe so.  That field is passed (via nsrexec) to the 'save'
process on the client.  The client tries to contact a 'nsrmmd' on the
interface specified.  Since this is a tcp connection, it has a single IP
address for the destination specified.

To "load balance", you'd need to use something between the sun and the
cisco (like SunTrunking).  You could put some clients on one interface
and some on another, but it wouldn't be dynamic.

 
 
 

1. One DHCP server - two interfaces - two subnets

Hi
        I run a DHCP server which supports wired internet in the internal LAN range
192.168.0.1/24. Now I wish to add a wireless internet LAN in the internal
LAN range 10.0.0.1/24. How do I accomplish this ?

/etc/dhcpd.conf :

option www-server       207.75.181.2,141.213.6.5,141.213.6.1;
ddns-update-style ad-hoc;

subnet 192.168.0.0 netmask 255.255.255.0
{
        range 192.168.0.3       192.168.0.10;

subnet 10.0.0.0 netmask 255.255.255.0
{
        range 10.0.0.3  10.0.0.10;

host clientwired
{
        hardware ethernet       wr:wr:wr:wr:wr:wr;
        fixed-address           192.168.0.2;

host clientwireless
{
        hardware ethernet       wl:wl:wl:wl:wl:wl;
        fixed-address           10.0.0.2;

where wr:wr:wr:wr:wr:wr and wl:wl:wl:wl:wl:wl are the obfuscated hardware
addresses for two clients - one wired and one wireless. How do I make sure
that the server listens on eth0 for the wired connections (192.168.0.1/24 -
as it already does) and wlan0 for wireless connections (10.0.0.1/24) ?

Thanks,

MS

2. Help with restricted user

3. Two Network interface with the same network

4. UNIX

5. two public ips from two networks on one server

6. trouble with LILO

7. two network cards, two(?) networks, one computer...

8. boot directly with floppies into unix without boot mngr?

9. Two network interface = 200 Mbps throughput?

10. How do masquerade and set up firewall on two network interfaces?

11. Two network interface = 200 Mbps throughput?

12. Two Network Interfaces on Same Subnet -- How-To?

13. Adding a second IP to network interface