The Alpha Corp - Case Study Example

MINI CASE Name Grade Tutor Date Alpha Corp case. The typical requirements for Alpha Corp include 1000 emails an hour each of size 1500 bytes which is equivalent to (1500 X 8 ) bits = 12000 bits. The network also handles 3000 web pages per hour each having a file size of 40000 bytes which is equivalent to (40000 X 8) bits = 320000 bits. Therefore, the recommended range of operating capacity suitable for the network at Alpha Corp will be between 12000000 and 960000000 bits per hour. In terms of bits per second, we have the following ((12000000)/ (60X60)) bits per second for the lower limit and ((960000000)/ (60X60)) bits per second for the upper limit. = (12000000)/3600 and (960000000)/3600 = 3333 and 266666 bits per second, which is 3Kbps and 266Kbps. Therefore, an internet connection with the speed range of between 3Kbps and 266Kbps will be suitable for Alpha Corp requirements for email and web page services. Due to the possibility of errors occurring during transmission and because the receiver of the data needs to regulate the rate at which they receive the data, synchronization is necessary though not sufficient in itself. Flow control and error detection should also be included in this process for it to be successful. This is handled at the data link layer using the available protocols at this layer. Flow control ensures data flow regulation between the sender to the receiver. The data link control focuses on a number of issues like frame synchronization, managing the link, controlling the data on the same link, flow, and error control. High-level data link control (HLDC) is an example of a data link control protocol. This protocol is important since it serves as a baseline from which other important data link control protocols can be derived and therefore it is widely accepted as the standard. HLDC is a bit oriented synchronous data link layer protocol by ISO covering multipoint links, full and half-duplex as well as point-to-point communication. This protocol presumes three station types and makes use of three modes of communication. Since Alpha Corp is relying on HLDC the typical configuration would be that which includes a frame with a maximum address size of 32 bits and a maximum control size of 16 bits and a frame check sequence of 16 bits resulting in a frame overhead of 64 bits. Eventually the frame configuration may have up to 24 bytes with such an overhead. In order to increase their capacity based on synchronous data link control, Alpha Corp may in future opt for the point-to-point protocol which is a variant of the HLDC allowing the transfer of bit as well as byte oriented methods while still maintaining the necessary data transparency. The flag for this frame setup would have a maximum of one octet, the address part would consist of between two, and four octets, the frame sequence check would have a maximum of two octets with a variable length for the data being transmitted. It is assumed that at present the frame relay setup is what Alpha Corp are using at a current capacity of 56 Kbps to 1.544 Mbps. Alpha Corp may also consider investing in the fractional T1 with a capacity of between 64Kbps and 1.544 Mbps on cable which is much cheaper than full T1. Furthermore, fractional T1 setup will be able to take care of the high bandwidth demands especially for the webpage processes that include many graphics. Connectus case. Increasingly business processes are embracing today’s technology savvy setups that centralize the computer. Therefore, the computer continues to play an important role even where convenience has advanced to another level including and depending on computer interconnectivity. However, the achievement of computer-dependant business processes that are working optimally depends on rules and formats that govern the interconnection process. These rules are stipulated by the open system interconnectivity (OSI). This organization has defined the various interconnectivity levels also called layers using standards that aim at ensuring seamless interconnection between systems manufactured by different vendors. Among the formats or standards of interconnectivity used are the open shortest path first (OSPF) and routing information protocol (RIP). These standards are concerned with routing process on the network of computers. Routing information protocol (RIP) This is s a routing format currently used in autonomous systems. The RIP has its base in the ‘routed’ computer program found within UNIX. This routing procedure utilizes the Bellman Ford algorithm. This protocol consists of a routing database that stores information about the shortest path between two nodes on the network. Some of the information like the gateway identity and route change flag are stored within this database. Assuming that the network has two nodes X and Y which may be routers and suppose D(x, y) represents the best route from X to Y and d(x, y) is the actual distance between the routers. Therefore, the best distance between X and Y can be defined as D(x, x) equals zero for all X. D(x, y) equals min (d (x, K) + D (K, y) for X< > over K. Open shortest path first (OSPF) This also is a routing protocol in its own capacity. This protocol ensures that routing information is dispersed among the routers supporting the network autonomously. Under this protocol, the routers on the network will each generate details about their interlinks with others on the computer network. Each time a link fails, each of these routers regenerates their updated routing information tables to include the change. There are a number of considerations for choosing RIP over OSPF when establishing a routing protocol for the network. RIP is easier to configure unlike OSPF which is much more complex requiring network design and planning knowledge. RIP can operate passively in end system interfaces. However, OSPF does not support this kind of mode. On the other hand, OSPF quickly adjusts to severed links between nodes on a network unlike RIP which adjusts much slowly. The traffic generated by an OSPF network is lower as compared to that supporting RIP. This is because of the periodical retransmission of the routing table information in the case of RIP whereas for the OSPF a node transmits only information about its links and not the whole routing table. OSPF favours large networks and has a higher scalability than RIP because for the latter, the packet size increases in proportion to the network size. OSPF is recommended for this case study based on the advantage of scalability as well as lower network traffic that will result in optimal network operation. Therefore, Connectus should move to OSPF. Read More