Skip to main content

Redundant Topologies / Redundancy

Redundancy
7.1.1 This page will explain how redundancy can improve network reliability and performance.
Many companies and organizations increasingly rely on computer networks for their operations. Access to file servers, databases, the Internet, intranets, and extranets is critical for successful businesses. If the network is down, productivity and customer satisfaction decline.
Increasingly, companies require continuous network availability, or uptime. 100 percent uptime is perhaps impossible, but many organizations try to achieve 99.999 percent, or five nines, uptime. Extremely reliable networks are required to achieve this goal. This is interpreted to mean one hour of downtime, on average, for every 4,000 days, or approximately 5.25 minutes of downtime per year. To achieve such a goal requires extremely reliable networks.
Network reliability is achieved through reliable equipment and network designs that are tolerant to failures and faults. Networks should be designed to reconverge rapidly so that the fault is bypassed.
Figure illustrates redundancy. Assume that a car must be used to get to work. If the car has a fault that makes it unusable, it is impossible to use the car to go to work until it is repaired.
On average, if the car is unuseable due to failure one day out of ten, the car has ninety percent usage. Therefore, reliability is also 90 percent.
A second car will improve matters. There is no need for two cars just to get to work. However, it does provide redundancy, or backup, in case the primary vehicle fails. The ability to get to work is no longer dependent on a single car.
Both cars may become unusable simultaneously, one day in every 100. The second car raises reliability to 99 percent. 
The next page will discuss redundant topologies

Comments

Popular posts from this blog

OSI layers / Peer-to-peer communications / TCP/IP model

OSI layers 2.3.4 This page discusses the seven layers of the OSI model. The OSI reference model is a framework that is used to understand how information travels throughout a network. The OSI reference model explains how packets travel through the various layers to another device on a network, even if the sender and destination have different types of network media. In the OSI reference model, there are seven numbered layers, each of which illustrates a particular network function. - Dividing the network into seven layers provides the following advantages: • It breaks network communication into smaller, more manageable parts. • It standardizes network components to allow multiple vendor development and support. • It allows different types of network hardware and software to communicate with each other. • It prevents changes in one layer from affecting other layers. • It divides network communication into smaller parts to make learning it easier to understand. In the foll...

Advantages and disadvantages of link-state routing

Advantages and disadvantages of link-state routing 2.1.5  This page lists the advantages and disadvantages of link-state routing protocols. The following are advantages of link-state routing protocols:  Link-state protocols use cost metrics to choose paths through the network. The cost metric reflects the capacity of the links on those paths. Link-state protocols use triggered updates and LSA floods to immediately report changes in the network topology to all routers in the network. This leads to fast convergence times. Each router has a complete and synchronized picture of the network. Therefore, it is very difficult for routing loops to occur. Routers use the latest information to make the best routing decisions. The link-state database sizes can be minimized with careful network design. This leads to smaller Dijkstra calculations and faster convergence. Every router, at the very least, maps the topology of it...

Ports for services

Ports for services 10.2.2  Services running on hosts must have a port number assigned to them so communication can occur. A remote host attempting to connect to a service expects that service to use specific transport layer protocols and ports. Some ports, which are defined in RFC 1700, are known as the well-known ports. These ports are reserved in both TCP and UDP.  These well-known ports define applications that run above the transport layer protocols. For example, a server that runs FTP will use ports 20 and 21 to forward TCP connections from clients to its FTP application. This allows the server to determine which service a client requests. TCP and UDP use port numbers to determine the correct service to which requests are forwarded. The next page will discuss ports in greater detail.