Find the answer to your Linux question:
Results 1 to 3 of 3
Hello everyone I have 2 application servers and they are directly connected to a SAN without a switch. The SAN server has dual network card Code: APP1 APP2 172.16.16.10 172.16.16.20 ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Aug 2009
    Location
    Toronto
    Posts
    34

    Need help with routing


    Hello everyone


    I have 2 application servers and they are directly connected to a SAN without a switch.

    The SAN server has dual network card

    Code:
                          APP1                              APP2
                         172.16.16.10                   172.16.16.20
                              |                                |
                              |                                |
                       172.16.16.1 --[ SAN DUAL NIC ] -- 172.16.16.2

    APP1 is able to ping SAN on 172.16.16.1, however I'm not able to reach SAN from APP2.


    I'm not really sure why its not working, but if I change the subnet to be as the following


    Code:
                          APP1                              APP2
                         172.16.16.10                   192.168.1.20
                              |                                |
                              |                                |
                       172.16.16.1 --[ SAN DUAL NIC ] -- 192.168.1.2
    Both servers are able to talk to SAN box.

    My question will be how can I enable route between APP1 APP2? right now they work, but they can't talk to each other since they are on different subnet.

    Your help is highly appreciated.

    Thank you

  2. #2
    Linux Engineer Kloschüssel's Avatar
    Join Date
    Oct 2005
    Location
    Italy
    Posts
    773
    You probably want to:

    * let APP1 be in the subnet1 172.16.16.0/24
    * let APP2 be in the subnet2 172.16.17.0/24
    * route packets from subnet1 into subnet2 and vice-versa; normally this is done with the route command, i.e. something like:
    ~@ route add -net 172.16.16.0 netmask 255.255.255.0 dev nic1
    ~@ route add -net 172.16.17.0 netmask 255.255.255.0 dev nic2

    Cheers

  3. #3
    Just Joined!
    Join Date
    Aug 2009
    Location
    Toronto
    Posts
    34

  4. $spacer_open
    $spacer_close

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •