Skip to main content

CCNA Recap: Hot Standby Routing Protocol (HSRP)






https://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/5_x/nx-os/unicast/configuration/guide/l3_cli_nxos/l3_hsrp.html

Redundance | Load Balancing 
for ipv4
hosts

default priority for standby routers are 100

Virtual Router Redundancy Protocol is the non cisco proprietary version of HSRP
—————  HSRP ——————


Cisco proprietary
Group # 0 - 255, int. signif only.
  • v. 2 expands to 4095 groups
  • v . 2 uses 224.0.0.102 multicast ipv4
    • ipv6 multicast is FF02::66

224.0.0.2 is multicast address for v. 1

standby preempt to force a new election


last eight bits of the Virtual Mac = standby group
priority range 0 - 255, default 100
hello timer def. 3 sec, holddown, 10 sec.
preempt is not enabled by default
‘cisco’ for default auth
u can use MD5 ( - v.2)
active router election; Highest priority wins, highest IP if a tie
  • v.2 mac range 0000.0C9F.F000 to 0000.0C9F.FFFF (Ipv4)
  • v2. mac range 0005.73A0. 0000 -  0005.73A0.0FFF for ipv6 
Fasted router to boot becomes the active one, irregardless of config. priority, if there is no preempt configured
——— hot standby ————————

Virtual Router: “I’m not in active or standby, I’m just listening and knowing infnormation.” 

In standby, you’re a candidate to be the active router


  • Spanning tree priority = lower = better
  • HSRP priority = higher = better

Consider legacy routing protocols

————— Configuration ————
First Router 
int ____
ip add [add][mask]
standby version 2 

standby [group #] ip [default gateway / virtual router IP]
must match on each router involved.

standby [group #] priority [up to 250 I believe? Higher = better]
standby [group #] preempt forcing election 
no shut

Second Router 

int ____
ip add [add][mask]
standby version 2 

standby [group #] ip [default gateway / virtual router IP] 
must match on each router involved.

no shut


EMPLOYERS: This shows that I review material I have tested and passed to refresh myself.
Labels:

Comments

Post a Comment

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

 If you're seeing this post, I'm helping you, and you probably have LI presence: React and share this post to help me in return.   In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an
Post a Comment
Read more

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.
Post a Comment
Read more

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory
Post a Comment
Read more