Hello,
I want to add a Failover feature in my Ndis Miniport lowest layer driver. So
far I have implemented the Failover feature of LBFO using BundleId as
described in DDK.
But the problem with Bundle ID is that both Primary and Secondary adapter
have their own individual network addresses(IP address). When the failover
happens and secondary is promoted to the primary, the machine have the IP
address of secondary (which is primary now) adapter.
This is not exactly a Failover as the IPaddress of machine has changed and
all the application has to restart due to this change in IP address.
I need to implement a TRUE failover in which if one adapter goes down, the
secondary takes over without any need to restart the application.
Any help or pointers in this direction would be highly appreciated. May be
there is a way in Miniport driver to assign the specific IP address to its
interface, in that case the driver can assign the old IP address to the new
adapter and hence the application keep on continuing as it is.
Thanks
Stop worrying about overloading your inbox - get MSN Hotmail Extra Storage!
http://join.msn.click-url.com/go/onm00200362ave/direct/01/
You need to write an intermediate driver that virtualizes a lowest layer and
handles the failover to the real network drivers. There are commercial
examples (e.g. intel proset.)
=====================
Mark Roddy
-----Original Message-----
From: Bill Wells [mailto:xxxxx@hotmail.com]
Sent: Sunday, May 23, 2004 3:11 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Failover in NDIS driver
Hello,
I want to add a Failover feature in my Ndis Miniport lowest
layer driver. So far I have implemented the Failover feature
of LBFO using BundleId as described in DDK.
But the problem with Bundle ID is that both Primary and
Secondary adapter have their own individual network
addresses(IP address). When the failover happens and
secondary is promoted to the primary, the machine have the IP
address of secondary (which is primary now) adapter.
This is not exactly a Failover as the IPaddress of machine
has changed and all the application has to restart due to
this change in IP address.
I need to implement a TRUE failover in which if one adapter
goes down, the secondary takes over without any need to
restart the application.
Any help or pointers in this direction would be highly
appreciated. May be there is a way in Miniport driver to
assign the specific IP address to its interface, in that case
the driver can assign the old IP address to the new adapter
and hence the application keep on continuing as it is.
Thanks
Stop worrying about overloading your inbox - get MSN Hotmail
Extra Storage!
http://join.msn.click-url.com/go/onm00200362ave/direct/01/
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as:
xxxxx@stratus.com To unsubscribe send a blank email to
xxxxx@lists.osr.com
Can you create two instances of your miniport adapter, one with state
connected and the other one with state disconnected until Failover ?
If so, try to Bridge the two instances.
Guy
“Bill Wells” wrote in message
news:xxxxx@ntdev…
> Hello,
>
> I want to add a Failover feature in my Ndis Miniport lowest layer driver.
So
> far I have implemented the Failover feature of LBFO using BundleId as
> described in DDK.
>
> But the problem with Bundle ID is that both Primary and Secondary adapter
> have their own individual network addresses(IP address). When the failover
> happens and secondary is promoted to the primary, the machine have the IP
> address of secondary (which is primary now) adapter.
>
> This is not exactly a Failover as the IPaddress of machine has changed and
> all the application has to restart due to this change in IP address.
>
> I need to implement a TRUE failover in which if one adapter goes down, the
> secondary takes over without any need to restart the application.
>
> Any help or pointers in this direction would be highly appreciated. May be
> there is a way in Miniport driver to assign the specific IP address to its
> interface, in that case the driver can assign the old IP address to the
new
> adapter and hence the application keep on continuing as it is.
>
> Thanks
> - Bill
>
> _________________________________________________________________
> Stop worrying about overloading your inbox - get MSN Hotmail Extra
Storage!
> http://join.msn.click-url.com/go/onm00200362ave/direct/01/
>
>