09.12.2012 Views

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ehave this way by default. With IP, it is a little more difficult, because some<br />

end-node configuration is needed. However, most major operating systems provide<br />

support for RIP <strong>to</strong> operate in a "snooping" mode <strong>to</strong> build a local dynamic routing<br />

table (some also support OSPF in this mode). Unfortunately, <strong>the</strong> feasibility of having<br />

every IP host run a routing pro<strong>to</strong>col is quite limited, because of <strong>the</strong> technical support<br />

required, additional processing overhead, and peripheral support availability<br />

needed <strong>to</strong> implement and manage such processes.<br />

There is really no efficient alternative for providing IP gateway assignments, so<br />

statically assigned gateways continue <strong>to</strong> be <strong>the</strong> most common method of providing<br />

a default gateway for external <strong>network</strong> access. They are often preferred over <strong>the</strong><br />

possibility of running a dynamic pro<strong>to</strong>col on an end-station. The static default is<br />

universally supported, easy <strong>to</strong> maintain, and has no possibility of failing—unless, of<br />

course, <strong>the</strong> router goes down. Regardless of how much redundancy you build in<strong>to</strong><br />

your <strong>network</strong> infrastructure, when <strong>the</strong> router fails <strong>the</strong> end-stations are stranded and<br />

cut off from <strong>the</strong> rest of <strong>the</strong> <strong>network</strong> until <strong>the</strong> router is recovered.<br />

Gateway failures are perhaps <strong>the</strong> largest single point of failure for any enterprise<br />

<strong>network</strong>. Cisco and o<strong>the</strong>r vendors have developed router redundancy pro<strong>to</strong>cols <strong>to</strong><br />

address this problem. The idea behind router redundancy pro<strong>to</strong>cols is simple. Two<br />

or more gateway routers collectively share a virtual IP and MAC address, which is<br />

set as <strong>the</strong> default gateway for <strong>the</strong> <strong>network</strong> segment. The routers sharing <strong>the</strong> IP<br />

address use an election pro<strong>to</strong>col <strong>to</strong> determine who is <strong>the</strong> gateway and who, in effect,<br />

stands by <strong>to</strong> take over when a failure occurs. There are three such pro<strong>to</strong>cols used <strong>to</strong><br />

perform this service:<br />

• Cisco Systems' Hot Standby Router Pro<strong>to</strong>col (HSRP)<br />

• Digital Equipment Corporation's IP Standby Pro<strong>to</strong>col (IPSTB)<br />

• A new open standard called Virtual Router Redundancy Pro<strong>to</strong>col (VIRP)<br />

IPSTB and VIRP are not supported currently in <strong>the</strong> Cisco IOS, so we will only focus<br />

on HSRP. IPSTB and VIRP are supported by o<strong>the</strong>r router vendors, so you should at<br />

least be aware of <strong>the</strong>ir existence. IPSTB and VIRP are not compatible with Cisco's<br />

HSRP, and Cisco has no plans <strong>to</strong> support VIRP (<strong>the</strong> newer and open standard) in <strong>the</strong><br />

future. More information on IPSTB and VIRP is available in RFC 2338.<br />

HSRP<br />

HSRP works by sharing a virtual IP address between two routers, where one is <strong>the</strong><br />

primary and <strong>the</strong> o<strong>the</strong>r <strong>the</strong> standby. When HSRP is active, all traffic and operational<br />

activity (ping responses, VTY sessions, and so on) is handled by <strong>the</strong> primary router.<br />

HSRP is activated using <strong>the</strong> <br />

interface configuration subcommand. In situations where only one HSRP instance is<br />

in use on a router, <strong>the</strong> group identifier is unnecessary. If more than one HSRP group

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!