Robust : Ability to remain functional under extreme conditions caused by either physical damage or heavy traffic. When you send a packet, does it get there intact? Efficient : Allows timely transmission of data packets as well as timely delivery. How long do I wait to transmit or receive? Simple : Is there a lot of overhead in setting up or expanding the network? Scalable : Does the performance take a big hit as the number of nodes increases?
Machine address conflict in normal MPI. New MPI release will include the changes done at UK. Dynamic Solution still pending. Channel bonding in Linux Kernel to be modified.
Give Disclaimer! The following segment is (mainly) for entertainment purposes.
Network book p305.
Terminology A home link is the link on which a specific node should be located; that is the link, which has been assigned the same network-prefix as the node’s IP address A foreign link is any link other than a node’s home link – that is, any link whose network-prefix differs from that of the node’s IP address Host-specific route is a routing-table with Prefix-Length of 32 bits, it will provide a match for exactly one IP Destination Address; namely, the address specified in the Target field Mobility is the ability of a node to change its point of attachment from one link to another while maintaining all existing communications and using the same IP address at its new link
The International Standards Organization (ISO) Open Systems Interconnect (OSI) is a standard set of rules describing the transfer of data between each layer in a network operating system. Each layer has a specific function. For example, the physical layer deals with the electrical and cable specifications.
The OSI Model clearly defines the interfaces between each layer. This allows different network operating systems and protocols to work together by having each manufacturer adhere to the standard interfaces. The application of the ISO OSI model has allowed the modern multiprotocol networks that exist today.
The OSI model provides the basic rules that allow multi protocol networks to operate. Understanding the OSI model is instrumental in understanding how the many different protocols fit into the networking jigsaw puzzle.
The Big Picture can be broken up according to its protocols into the following four areas:
Cable m odems are not part of the local loop but do fall into the category of the last mile, or how high speed digital communication gets to the premises (home). It would incredibly expensive to replace the existing cabling structure. And because this cabling was designed for voice communications rather than digital, all of these protocols are needed to overcome the existing cabling limitations in the local loop and provide high speed digital data transmission.
A Local Area Network is a system of computers that share resources such as disk drives, printers, data, CPU power, fax/modem, applications, etc. They usually have distributed processing, which means that there are many desktop computers distributed around the network and that there is no central processor machine (mainframe).
A Metropolitan Area Network is a system of LANs connected throughout a city or metropolitan area. MANs have the requirement of using telecommunication media such as voice channels or data channels. Branch offices are connected to head offices through MANs. Examples of organizations that use MANs are universities and colleges, grocery chains, and banks.
The main criterion for a MAN is that the connection between LANs is through a local exchange carrier (the local phone company). The protocols that are used for MANs are quite different from those used for LANs (except for ATM, which can be used for both under certain conditions).
In the past, it has been standard to come up with a topology first, and then adapt it to certain tasks. Modern design philosophy has changed this practice. Now a subset of problems or needs gives rise to special task network designs. One such design has been conceived right here at UK.
This example shows how one could construct a FNN for 6 PCs using just two NICs/PC and three 4-port switches. Note that every PC has at least one single-switch latency path to every other PC; some PC pairs have more than one such path.
Multiple small, interleaved subnets link each machine by a number of one-switch latency paths. Any machine can belong to as many subnets as it has network cards onboard. Sounds simple, but several problems arise from the design.
The wiring scheme and subnets can now be designed by a piece of software developed in the KAOS lab. This problem appears to be NP Complete (Very Bad) and must be solved using a genetic search algorithm. A simplified version allows you to design your own FNN on the web.