Re: MSCS - arp cache/mac-address problems

Hi Johnny,

No the ARP cache should be updated once the virutal server fails over. If
should assume part of the phyical NIC MAC and part virtual. It should not
switch without a failover.

This is a strange problem, not one I have seen. What is the hardware for the
cluster nodes?

I will do some digging and see what I can find.
Regards

Craig.


"Johnny Lundgren" <JohnnyLundgren@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:FCBA215D-763C-4D7F-988F-E6950111D480@xxxxxxxxxxxxxxxx
Hello Craig,

Yes I have WINS in the environment but the problem I am having is residing
near the hardware layer not at O.S. level.
Normally, I shouldn´t have to worry about arp table updates, should I ?

Or am I wrong ?

/Johnny Lundgren

"Craig Wilson" wrote:

Hi Johnny,

One thing the comes to mind is WINS, do you have WINS in the envoriment?

Cheers

Craig.
"Johnny Lundgren" <JohnnyLundgren@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:C7FAAAD8-4742-41C7-A520-4EB4E68B010C@xxxxxxxxxxxxxxxx
Hello,

I have two cluster-nodes based on Win2k AS SP4 English.
Hardware is Compaq MSA1000 and two ML380 servers.

On some clients I get problems when I failover one group with Virtual
IP
and
Name resources.
When I ping the virtual IP it times out. Checking the ARP table on the
client shows that the macaddress belongs to the server that does not
own
the
IP resource.
I make a arp -d to clear the cache then I ping again. It works for a
while
and it is the correct mac-address when checking the arp cache (the
other
node´s public NIC that is).

Suddenly, still pinging, it times out again.
Checking the arp cache shows that it has reverted to the same
mac-address
as
before ! The other node´s mac-address that does not own the virtual IP.

The arp table updates should automatically take place. It is Ethernet
basics
so where should I start looking for a solution to the problem ?

Regards

Johnny Lundgren

Alla servers and clients are connected to several Cisco switches.





.

Relevant Pages

  • Re: NLB Cluster - Ping fails or long time to reply from outside local subnet - SOLVED
    ... Once again, ARP is an RFC standard, if you are having to make static entries in unicast mode, then your network device is not in compliance. ... Windows Server 2008 Readiness Team ... I was feeling nervous about our teaming-capable adapter as I read it might be sending out heartbeats, so I disabled it AND configured the cluster on a separate DLink card in multicast mode. ... I thought that the litmus test was that the router functions fine when no NLB is installed, but when it is, things start going screwy. ...
    (microsoft.public.windows.server.clustering)
  • Re: NLB Cluster - Ping fails or long time to reply from outside local subnet - SOLVED
    ... ARP is defined by RFC. ... Windows Server 2008 Readiness Team ... The servers are a couple of switches away from the router so I would have thought that any duplicate MAC info. or similar would have been come irrelavent/concealed at the router. ... If you run the command 'wlbs query' and the node it is run on says it is converged with all of your nodes in the cluster, that basically says the NLB configuration is correct and the nodes are talking to each other. ...
    (microsoft.public.windows.server.clustering)
  • RE: ARP Spoofing and Routing
    ... It sounds to me like you were only doing one way arp spoofing... ... requests sent out from that server. ... Up to 75% of cyber attacks are launched on shopping carts, ...
    (Pen-Test)
  • Re: Migrating from one server to another
    ... Oh heck no. M$ clients and HA boxen on the same subnet? ... Migrating from one server to another ... stuff to figure out where gratuitous ARP is yet...). ... We've also had a problem on some servers where there are lots of aliases ...
    (AIX-L)
  • Re: dhcprelay troubleshooting, where next?
    ... > It quite happily supplies addresses to everything on that subnet. ... The server has noted this in its dhcpd.leases file. ... > Listening on Socket/eth1 ... > plus lots of inaddr arp domain unreachable and PTR? ...
    (comp.os.linux.networking)