With HSRP on our network, there is a good deal of network reliability for end users. As the network engineer, this means when a link fails, end users rarely notice it. The backup link simply handles the load and business continues as usual. Just the way I want it. While my monitoring system does provide an alert to the link down condition, I like to handle these situations as a higher priority, since it has become a single point of failure.
Here are a few tips to actively managing your HSRP implementation:
1. Map out each pair – know when a primary route goes out, what path has been designated as the alternate (if you have many HSRP routes you can combine them onto a single map. The pre-created map makes it easy to find the paired item).
2. Create custom alerts for HSRP interfaces that indicate which path is a primary or secondary HSRP link. The HSRP interfaces need to be treated differently than a switch port to a user workstation due to their critical nature.
3. After service has been restored, review the interface load of the secondary link and evaluate how well it handled the traffic. Use this information to ensure your backup pipes have adequate capacity. This will improve your disaster recovery planning for any future events.
Here are some monitoring screenshots that show my HSRP map and an active alarm.
Figure 1. HSRP MAP (Primary is solid line, Secondary is dashed line)
Figure 2. HSRP Active Alarm – (identifies HSRP link route impacted)
Form and manner of display of registration marks on the motor vehicles as per Central Motor Vehicles rulesAccording to sub-section (6) of section 41,on or after commencement of this rule, the registration mark referred to shall be displayed both at the front, rear and windshield of all vehicles clearly and legibly in the form of security license plate of the following specifications, namely.
ReplyDelete