IBM, Infineon Develop Most Advanced MRAM Technology to Date

Lycos - Business Wire ^ | 10 Jun 2003, 12:00am ET | My Luu - IBM Reiner Schonrock - Infineon

[Ernest_at_the_Beach]

Cool this:

[Ramius]

Just damn. Saw that when I was browsing around over there. Nifty site.

Just damn. So what does that do to my per-processor licensing? Ouch. Oh well, that's a lousy way to write licenses anyway. The bastiches.

[Ernest_at_the_Beach]

What are you running?

[Ramius]

I run lots of different stuff. For the most part my company is a MS shop at the user end. But some other things where they make sense, or where I can't get rid of what's there yet. Lots of NT4/2K, Some Linux, Some OSX Server, some [sigh] VMS on an aging Alpha.

I'm the IT Dir for a company of about 700. 25 locations in a nifty new VPN-based WAN. We're doing some really neat stuff on the WAN front. I'm loving it.

Picture this: two low-cost SDSL or broadband wireless connects to different providers in every location. Use Cisco HSRP to auto-failover between providers. Use IPSec tunnels to mesh tunnels fully between all offices.

Freekin' bulletproof, that. :-)

[Ernest_at_the_Beach]

Picture this: two low-cost SDSL or broadband wireless connects to different providers in every location. Use Cisco HSRP to auto-failover between providers. Use IPSec tunnels to mesh tunnels fully between all offices.

I know nothing about that stuff!

But I can see you have an exciting life!

[Ramius]

hehehe... roger that.

It's like this: We're trying to move beyond traditional "disaster recovery" and into "failure resiliency". I want a network that can take hits, even serious hits, and nobody knows it even happened.

The big thing now for me is "virtualization" of storage. Everybody touches the same data all over the net, but the data isn't necessarily where they think it is. Nothing should ever exist in only one place, but must be everywhere. That way, whatever is still standing looks like all the other places too.

It's big, big fun. I love this stuff.

[Ernest_at_the_Beach]

OK -- found this:

________________________________________

General Functionality of HSRP

The Cisco innovation Hot Standby Router Protocol (HSRP) was introduced in IOS 10.0. HSRP brings fast re-routing technology to the desktop. HSRP enables a set of routers to work together to present the appearance of a single virtual router or default gateway to the hosts on a LAN. HSRP is particularly useful in environments where critical applications are running and fault-tolerant networks have been designed. By sharing an IP address and a MAC address two or more routers acting as one virtual router are able to seamlessly assume the routing responsibility in the case of a defined event or the unexpected failure. This enables hosts on a LAN to continue to forward IP packets to a consistent IP and MAC address enabling the changeover of devices doing the routing to be transparent to them and their sessions.

HSRP works by allowing an administrator to configure Hot Standby Groups to share responsibility for an IP address. Each router can be given a priority to enable an administrator to weight the prioritization of routers for active router selection. One of the routers in each group will be elected to be the active forwarder and one the stand-by router to stand ready to take over this functionality. This is done according to the router's configured priorities. The router with the highest priority wins and, in the case of a tie in priority, the greater value of their configured IP addresses will break the tie. Other routers in this group will monitor the active and stand-by routers' status to enable further fault tolerance. All HSRP routers participating in a standby group will watch for hello packets from the active and the standby routers. From the active router in the group they will all learn the hello and dead timer as well as the standby IP address to be shared, if these parameters are not explicitly configured on each individual router. If the active router becomes unavailable due to scheduled maintenance, power failure, or other reasons the stand-by can assume this functionality transparently within a few seconds. This will occur if the dead timer is reached, by missing three successive hello packets, and the standby router will promptly take over the virtual addresses, identity and responsibility.

[Ernest_at_the_Beach]

And this

Linux Advanced Routing & Traffic Control HOWTO

Interesting!