Network Availability Flashcards
Availability
Concerned with being up & operational
Reliability
Concerned with not dropping packets
MTTR
Mean Time to Repair
Measures the average time it takes to repair a network device when it breaks
MTBF
Mean Time Between Failures
Measures the average time between failures of a device
Redundant Networks w/Single Point of Failure
Link Redundancy:
Internal Hardware Redundancy
(PSUs & NICs)
Redundant Networks w/No Single Points of Failure
Link Redundancy:
Redundancy of Components
(Switches & Routers)
Hardware Redundancy
(Takes many forms)
Devices with two NICs, HDDs/SSDs, or internal PSUs
Often found in strategic network devices
(Routers/Switches/Firewalls/Servers)
Usually not found in clients due to cost
Hardware Redundancy: Active-Active
Multiple NICs are active at the same time
NICs have their own MAC addresses
Makes troubleshooting more complex
Hardware Redundancy: Active-Standby
One NIC is active at a time
Client appears to have a single MAC address
Layer 3 Redundancy
Clients are configured with a default gateway (router)
If default gateway goes down, they cannot leave subnet
Layer 3 redundancy creates virtual gateways to avoid this issue
HSRP
Hot Standby Router Protocol:
Proprietary first-hop redundancy by Cisco
Allows for active router and standby router
Creates virtual router as the default gateway
CARP
Common Address Redundancy Protocol:
Open-standard variant of HSRP
Allows for active & standby router
Creates virtual router as default gateway
VRRP
Virtual Router Redundancy Protocol:
IETP open-standard variant of HSRP
Allows for active & standby router
Creates virtual router as default gateway
GLBP
Gateway Load Balancing Protocol:
Proprietary first-hop redundancy by Cisco
Focuses on load balancing over redundancy
Allows for active & standby router
Creates virtual router as default gateway
LACP
Ling Aggregation Control Protocol:
Achieves redundancy by having multiple links between devices
Load balancing occurs over multiple links
Multiple links appear as a single logical link
Availability Best Practices
Examine technical goals
Identify budget to fund high avail features
Categorize business apps into profiles
(Each requires certain level of availability)
Establish performance standards
Define how to manage & measure the solution
(Need metrics to quantify success)
Recovery Sites: Cold Sites
Building is available, but no hardware/software configured
Need to buy resources (or ship them in) and the configure network
Slow & time consuming recovery
Recovery Sites: Warm Sites
Building & equipment available
Software may not be installed & latest data unavailable
Recovery is fairly quick, but not everything from original site is available to employees