[comp.dcom.sys.cisco] Adding static routes

leinwand@cisco.com (Allan Leinwand) (09/27/90)

>Perhaps a picture would help:
>
>                                                  \
>            \      -------             -------     |    
>             |    |       | #1        |       |    |
>134.40.64.0  |----| cisco |-----------| cisco |----| 134.38.192.0
>             |    |   A   |           |   B   |    |
>             \     -------             -------     \
>                  #2 |                    |
>                     |   /                |   /
>                   ------               ------   
>                  /    |               /    |
>                       |                    |     \
>            \      -------             -------     |
>             |    |       |           |       |    |
>134.40.32.0  |----| cisco |-----------| cisco |----| 134.38.128.0
>             |    |   C   |           |   D   |    |
>             \     -------             -------     \
>                                
>
>I have two IP networks, using class B addresses and a subnet mask of
>255.255.255.192.  Can I tell cisco A to route traffic from a host on
>134.40.64.0 to a host on 134.38.192.0 using interface #1 and to route
>traffic from a host on 134.40.64.0 to a host on 134.38.128.0 using 
>interface #2, (i.e., through cisco C rather than cisco B)?

First, assuming that the link from A --> B is not significantly lower
than all the other links in the picture, you will automatically route
from A --> B using interface #1.  If you want to be assured that this is
the primary path taken, lower the 'bandwidth' on this link to something
a little greater than the minimum bandwidth on C --> D.

By looking at your picture, it seems to me that you do not want any
traffic to traverse the link between cisco B and cisco D.  Thus, set the
'bandwidth' metric on the interfaces on B and D (which go to the common
link) to something lower than normal.  Thus, the A --> C --> D route
would have a lower metric.  This scheme also has the advantage of not
using static routes.  Thus, if you link from C --> D fails, you can
always use the A --> B --> D link as backup.

Maybe something like this:
          
    
                    64
           A  --------------- B
         56|                  |32
           |                  |
           C ---------------- D
                    56

Even if your real bandwidth does not match these 'bandiwdth' settings, this 
should produce the desired routing.

Thanks,

Allan Leinwand
cisco Systems

allan@frisbee.cisco.com (Allan Leinwand) (09/28/90)

>Perhaps a picture would help:
>
>                                                  \
>            \      -------             -------     |    
>             |    |       | #1        |       |    |
>134.40.64.0  |----| cisco |-----------| cisco |----| 134.38.192.0
>             |    |   A   |           |   B   |    |
>             \     -------             -------     \
>                  #2 |                    |
>                     |   /                |   /
>                   ------               ------   
>                  /    |               /    |
>                       |                    |     \
>            \      -------             -------     |
>             |    |       |           |       |    |
>134.40.32.0  |----| cisco |-----------| cisco |----| 134.38.128.0
>             |    |   C   |           |   D   |    |
>             \     -------             -------     \
>                                
>
>I have two IP networks, using class B addresses and a subnet mask of
>255.255.255.192.  Can I tell cisco A to route traffic from a host on
>134.40.64.0 to a host on 134.38.192.0 using interface #1 and to route
>traffic from a host on 134.40.64.0 to a host on 134.38.128.0 using 
>interface #2, (i.e., through cisco C rather than cisco B)?

First, assuming that the link from A --> B is not significantly lower
than all the other links in the picture, you will automatically route
from A --> B using interface #1.  If you want to be assured that this is
the primary path taken, lower the 'bandwidth' on this link to something
a little greater than the minimum bandwidth on C --> D.

By looking at your picture, it seems to me that you do not want any
traffic to traverse the link between cisco B and cisco D.  Thus, set the
'bandwidth' metric on the interfaces on B and D (which go to the common
link) to something lower than normal.  Thus, the A --> C --> D route
would have a lower metric.  This scheme also has the advantage of not
using static routes.  Thus, if you link from C --> D fails, you can
always use the A --> B --> D link as backup.

Maybe something like this:
          
    
                    64
           A  --------------- B
         56|                  |32
           |                  |
           C ---------------- D
                    56

Even if your real bandwidth does not match these 'bandwidth' settings, this 
should produce the desired routing.

Thanks,

Allan Leinwand
cisco Systems