Skip to main content

Hot Standby Router Protocol- HSRP



The Hot Standby Router Prtocol (HSRP) is a networking protocol that supports the non-disruptive failover of Internet Protocol (IP) traffic in special circumstances. HSRP also allows network hosts to look like they are using a single router and keep connected if the first hop router being used fails to respond. The protocol guards against the failure of the first hop router in a network infrastructure when the router’s IP address cannot be found dynamically. The HSRP normally joins several routers together to create a single virtual server that client machines and networks use. The protocol helps to ensure that only one of the virtual server’s routers is working at any given time.

How does the Hot Standby Router Protocol Work?

The router that forwards packets for the virtual router is referred to as the active router. There is also a designated standby router in the scheme in the event that the primary router fails. The protocol makes router assignments based on the IP address assignments for each device, and it runs on top of the UDP network protocol using port number 1985. The routers in the system use their true IP addresses in the protocol via the virtual router’s IP address so that they can be distinguished from each other. HSRP also allows interface tracking to be configured on the network. This prioritizes select events or machines on the network in order to prioritize network resources for the most important transactions on the network. The priority scheduling of resources is primarily done in a work or research setting.
Advantages of the Hot Standby Router Protocol

The HSRP supports configurable MAC addresses. This lets client computers and destination networks use HSRP as the first destination to start routing IP traffic. Peer-to-peer networking applications have significantly used the HSRP protocol, which also allows IP redundancy and maintains maximum redundancy.

Popular posts from this blog

HOW TO EDIT THE BCD REGISTRY FILE

The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N