Re: win2k3 - persistent route not persisting !

1. I've never seen anyone specify an Interface using a Hex Number. Use the
IP#.

2. When a Route is created the Interface that is used normally cannot have
another interface with an IP# in the same subnet. If it does the Interface
with the highest binding order will take over and be the one that actually
is used. The NLB Interface has the binding order priority so that is the
one used as the Source Interface for the Route.

3.You may have to look at the differnce in behavor between unicast mode and
multicast mode and how they behave differently and if that might be a
solution. Sorry,..I have no links or documentation. I would have to
"google" for them the same as you.

4. You may have to change what your "needs" are so that they don't conflict
with the impossible.

I could be wrong,...I am by no means an expert on NLB,...but those are my
thoughts on it


--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------


"andreww" <> wrote in message
news:2b220516-d734-4a6d-8700-...
On 21 Sep, 16:17, andreww <andy...@gmail.com> wrote:
> Argh !
>
> I have a problem with a couple of servers that are network load
> balanced. We need the non-NLB interface to maintain a persistent route
> to a particular gateway, but when I make the route and test it it's
> fine. And then I reload the server, and it changes to the OTHER
> interface when it comes back. Which won't work for what I need it to
> do (firewall, management interfaces etc).
>
> Here's how it should look:
> IPv4 Route Table
> ================================================== =========================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x2 ...02 bf c0 a8 01 ae ...... Intel(R) PRO/1000 MT Network
> Connection - Networ
> k Load Balancing Filter Device
> 0x10004 ...00 13 72 53 61 2e ...... Intel(R) PRO/1000 MT Network
> Connection #2
> ================================================== =========================
> ================================================== =========================
> Active Routes:
> Network Destination Netmask Gateway Interface
> Metric
> 0.0.0.0 0.0.0.0 192.168.1.252
> 192.168.1.160 1
> 10.40.0.0 255.255.0.0 192.168.1.200
> 192.168.1.160 1
> 127.0.0.0 255.0.0.0 127.0.0.1
> 127.0.0.1 1
> 192.168.1.0 255.255.255.0 192.168.1.160
> 192.168.1.160 1
> 192.168.1.0 255.255.255.0 192.168.1.170
> 192.168.1.170 10
> 192.168.1.160 255.255.255.255 127.0.0.1
> 127.0.0.1 1
> 192.168.1.170 255.255.255.255 127.0.0.1
> 127.0.0.1 10
> 192.168.1.174 255.255.255.255 127.0.0.1
> 127.0.0.1 10
> 192.168.1.255 255.255.255.255 192.168.1.160
> 192.168.1.160 1
> 192.168.1.255 255.255.255.255 192.168.1.170
> 192.168.1.170 10
> 224.0.0.0 240.0.0.0 192.168.1.160
> 192.168.1.160 1
> 224.0.0.0 240.0.0.0 192.168.1.170
> 192.168.1.170 10
> 255.255.255.255 255.255.255.255 192.168.1.160
> 192.168.1.160 1
> 255.255.255.255 255.255.255.255 192.168.1.170
> 192.168.1.170 1
> Default Gateway: 192.168.1.252
> ================================================== =========================
> Persistent Routes:
> Network Address Netmask Gateway Address Metric
> 10.40.0.0 255.255.0.0 192.168.1.200 1
>
> And when I reboot it, the interface for 10.40.0.0 changes:
> IPv4 Route Table
> ================================================== =========================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x2 ...02 bf c0 a8 01 ae ...... Intel(R) PRO/1000 MT Network
> Connection - Networ
> k Load Balancing Filter Device
> 0x10004 ...00 13 72 53 61 2e ...... Intel(R) PRO/1000 MT Network
> Connection #2
> ================================================== =========================
> ================================================== =========================
> Active Routes:
> Network Destination Netmask Gateway Interface
> Metric
> <snip>
> 10.40.0.0 255.255.0.0 192.168.1.200
> 192.168.1.170 1
> <snip>
> Default Gateway: 192.168.1.252
> ================================================== =========================
> Persistent Routes:
> Network Address Netmask Gateway Address Metric
> 10.40.0.0 255.255.0.0 192.168.1.200 1
>
> Command I'm using to add the persistent route is
>
> route -p add 10.40.0.0 mask 255.255.0.0 192.168.1.200 IF 0x10004
>
> Tried various combinations of metrics and such like, no dice. Not sure
> what the localhosts gateways are about on this machine (I didn't build
> it), but anyone know what's causing the persistent route to change
> interface after reload ?? 0x10004 is definitely the .160 address, no
> question about that.
>
> C:\>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : xxxxx
> Primary Dns Suffix . . . . . . . : xxxxxx
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : xxxxxx
>
> Ethernet adapter NLB:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
> Connection
> Physical Address. . . . . . . . . : 02-BF-C0-A8-01-AE
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.174
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> IP Address. . . . . . . . . . . . : 192.168.1.170
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . :
> DNS Servers . . . . . . . . . . . : 192.168.1.250
> 192.168.1.251
>
> Ethernet adapter LAN:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
> Connection #
> 2
> Physical Address. . . . . . . . . : 00-13-72-53-61-2E
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.160
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.252
> DNS Servers . . . . . . . . . . . : 192.168.1.250
> 192.168.1.251
>
> Driving me mad - little help anyone ?
>
> A

anyone ?

"andreww" <> wrote in message
news:f709afc6-21fa-4916-830c-...

>Couple of quick points - I can't specify the interface by anything
>other than hex, get errors.

That could be a hint that something you are doing is wrong.

>Tried by IP, and got this. Looks a bit odd...
>route -p add 10.40.2.0 mask 255.255.255.0 192.168.1.200 IF
>192.168.1.160

Nothing looks odd to me.

> At the moment, I've just scheduled a startup script to recreate the
> route each time. If things were bound incorrectly, then I could
> understand that they didn't work. However, they do work - it's a
> reboot that causes it to fall out which I find more perplexing...

The machine is probably smarter than we are here. If it keeps trying to
change what you are doing then the machine is probably right.

The NLB concept probably intends to only allow the Virtual IP# to be used
for anything and prevent the original local IP from being used,..hence the
Routing Table keeps over-riding you and jumping back to what it is
*supposed* to be. The MultiCast -vs- the UniCast stuff can effect this
directly,...you need to investigate and get the details on that.

Thinking back to my background in ISA Server:......
ISA Server uses NLB when it creates its Firewall Arrays,...they have to use
a third nic in each member so the members can communicate with each other
because they can't do it through the original IP# any longer (similar to
what you are seeing here). This third Nic with its accompanying new subnet
is called the Intra-Array Network. After some updates the ISA can work
without the Intra-Array Network but it *completely* depends on the
MultiCast -vs- the UniCast situation. So you really need to investigate
that.

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

Ok, good luck with it.
I wish I could give a more specific answer.

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------


"andreww" <> wrote in message
news:aa96ac2e-6890-4cf2-a83a-...
On 30 Sep, 20:30, "Phillip Windell" <philwind...@hotmail.com> wrote:

Thanks Phil

The "looks odd" referred to the error message returned, not the
command

I'll change the system so that the traffic I need to return can come
via the NLB interface instead, I suppose it's not such a big deal.

More of a curiosity than anything else. Thanks for the advice/
thoughts.

A