CIS505 3rd Assignment 5thweek Elastic and Inelastic Traffic By Jyothirmai Nagabhairava

ELASTIC AND INELASTIC TRAFFIC
BY
Jyothirmai Nagabhairava
Student ID: SU200183298
Professor: Dr. Jodine Burchell
CIS505: Communication Technologies
Date: 02-20-2015.

Abstract
The purpose of this paper is to outline a plan for the development of an addressing and naming model for ten departments in a 1,000-employee organization and design a modern efficient network solution that will benefit the Company’s global enterprise operations.
Introduction
Names are assigned to many types of devices in today’s modern networks or internetworks, workstations, printers, servers, switches, and routers. A well-designed naming model should allow users to access these devices by name. The name of a resource indicates what we seek; an address indicates where it is. Most network protocols require a device to have a network address, and the end user’s system must map this address to a name. The methods used to map the network address to a network name can vary from static host files to Dynamic DNS. Dynamic methods of name resolution usually are the best solution.
To maximize usability, names should be short, meaningful, unambiguous, and distinct. A user should easily recognize which names go with which devices. These names give information about the type of device and the device location. A good practice is to include in a name some sort of indication of the device's type. For example, you can prefix or suffix router names with the characters rtr, switches with sw, servers with svr, and so on. Using meaningful prefixes or suffixes decreases ambiguity for end users, and helps managers more easily extract device names from network management tools.

Plan for the development of an addressing and naming model for ten departments
The company consists of ten departments having 1,000-employee. For 10 departments we have to design ten LANs with equal geography separation. Each LAN can contain more than 50 computers. The IT department of Corporation outlines a plan for the development of an addressing and naming model in an environment of the ten departments in a 1,000-employee organization. Each can access each department through these address name from Internet connection. This organization is using a common data center of twenty backend enterprise servers. It has one primary data center operation.
Names can also include a location code. Our network designers use location codes in naming models. For example, all names in San Francisco start with SFO, all names in Oakland start with OAK, and so on. The location code could be a number instead, but most people remember letters better than numbers. If a device has more than one interface and more than one address, you should map all the addresses to one common name. For example, on a multiport router with multiple IP addresses, assign the same name to all the router's IP addresses. This way network management software does not assume that a multiport device is actually more than one device.
For example, for a router located at a branch office in Louisville, KY, consider using something like sdfbranchrtr. In this example, sdf is Louisville’s airport code, branch describes the location, and rtr tells you that this device is a router.
A central authority can assign blocks of addresses and names in a hierarchical fashion to departments and branch offices. A topology map of the network is also useful, because it helps you see the hierarchy in the network and recognize where address boundaries exist. Network layer addresses should be planned, managed, and documented. The addressing and naming of the top-down network design process falls here in the methodology. The addressing and naming step precedes selecting routing and switching protocols. Although an end system can learn its address dynamically, no mechanisms exist for assigning network or subnet numbers dynamically. These numbers must be planned and administered.
Depending on the organizational structure of the enterprise, network managers within each region or branch office can further divide the subnets. IP addresses are either public or private. Public addresses are globally unique and are registered with a numbering authority. Private addresses are never routed on the global Internet and are assigned from a special range; The term provider-independent address space refers to addresses that are assigned directly by one of the regional registries. In practice, most enterprises do not use addresses from the provider-independent address space. Therefore, most enterprises work with an Internet service provider (ISP) to obtain public addresses, in which case their addresses are part of the provider-assigned address space. The enterprise uses these addresses for as long as it remains a subscriber of the provider. Naming in an IP environment is accomplished by configuring hosts files, DNS servers, or Network Information Service (NIS) servers. DNS is used on the Internet and has also gained widespread popularity for managing names in enterprise networks. It is the recommended naming system for modern networks. Using AppleTalk we have assigned cable range for each network segment e.g., building number/floor number. Network layer stations address consists of a 16-bit network number and an 8-bit node ID. Once network-layer address is chosen it is saved in battery-backed-up RAM so it doesn’t have to get new address each time it boots. AppleTalk station communicates with a router to determine the cable range for its network segment. A network manage configures routers and servers on a NetWare network with the 4 byte network number for a network segments
Example:
Network is 172.16.0.0. We have 10 LANs, each of which will be its own subnet. We want to divide the network into subnets. We will allow 100 nodes per subnet. What address would this node use to send to all devices on its subnet?
Functional Problems
Sending packets by clients to any department might take a lot of time. This plan might support caching of one name by all the servers in the organization. Some of the limitations of this plan might include; insufficient funds in organization to support the whole plan thus implementing would be difficult because it is some of the devices for networking are very costly.
The number of the workers in the organization is too many that is 1000, which may make it difficult to have all the names in the system. The implementation process of the plan might be time consuming thus it might take a lot of time entering all the names of the employees in the system. Implementation of new policies about the system might be difficult to become effective because it is difficult for many employees to catch up with new policies.
DNS In Our Plan
Domain Name System (DNS) converts user-defined domain names into IP addresses. The Domain Name System is one of the most important components of Internet infrastructure. If DNS is unavailable, you’ll have difficulty finding resources on the Internet and, likewise, others will be unable to find you. That’s because DNS is the phone book that translates names such as www.alpha.com to Internet protocol (IP) addresses such as 199.239.136.245, and vice versa. (Ambler, S. W. 1988). The Domain Name System distributes the responsibility of assigning domain names and mapping those names to IP addresses by designating authoritative name servers for each domain (Oppenheimer, 2005). Without proper name resolution, users cannot locate resources on the network. It is critical that the design of the DNS namespace be created with Active Directory in mind and that the namespace that exists on the Internet not conflict with an organization's internal namespace (Silverston, L., & Agnew, P. 2011).
Each computer can have its DNS names configured using one of two possible methods: A primary DNS domain name, which applies as the default fully qualified DNS name for the computer and all of its configured network connections. A connection-specific DNS domain can be configured as an alternate DNS domain name that applies only for a single network adapter installed and configured on the computer.
Use different internal and external namespaces. Different locations can be named with different sub domains. Separate internal and external names on separate servers. External servers should include only those names that you want to be visible to the Internet. Internal servers should contain names that are for internal use. You can set your internal DNS servers to forward requests that they cannot resolve to external servers for resolution. Different types of clients require different kinds of name resolution. Web proxy clients, for example, do not require external name resolution because the proxy server does this on their behalf (Silverston, L., & Agnew, P. 2011).
Our company has 10 departments; it’s likely to have ten domains. Here are a few alternate domain structures you might want to consider for company. The best way to show how all of these concepts come together is by walking through an example. The network shows how DNS servers might be deployed and configured for a company having anywhere from two to 1,000 employees. For every wide area network (WAN) link between offices, there should be a corresponding site link within Active Directory. Furthermore, the computers that reside within a physical office should be placed within a common Active Directory site. Ideally, each location should make use of a dedicated subnet because a single subnet can’t span multiple Active Directory sites (Napier, R. & Mugunth K. (2012)).
As shown in the following figure, a multi-homed server computer named "host-A" can be named according to both its primary and connection-specific DNS domain names.

In this example, the server computer host-A attaches to two separate subnets -- Subnet 1 and Subnet 2 -- which are also linked at redundant points using two routers for additional paths between each subnet. Given this configuration, host-A provides access as follows through its separately named local area network (LAN) connections: The name "host-A.public.example.alpha.com" provides access using LAN connection 1 over Subnet 1, a lower-speed (10 megabit) Ethernet LAN, for normal access to users who have typical file and print service needs. The name "host-a.backup.example.alpha.com" provides access using LAN connection 2 over Subnet 2, a higher-speed (100 megabit) Ethernet LAN, for reserved access by server applications and administrators who have special needs, such as troubleshooting server networking problems, performing network-based backup or replicating zone data between servers. This represents the root of the hierarchy that a name server traverses when looking up an address. A DNS server always knows where to find the root servers that can tell it the locations of servers that understand top-level domains (such as com, net, and org). Because DNS is distributed and hierarchical, looking up a domain name can take the query around the world to servers knowing answers to the query. The master authoritative name server has at least one slave in each physical location. The slave is a caching, recursive name server that acts as the primary name server for all non-Windows systems and indirectly for Windows workstations. It is placed topologically close to its clients, preferably on the same subnet. If the caching name server fails, the internal authoritative name server is the backup, at the cost of queries having to traverse the firewall, adding some latency to each request. Depending on the size of the organization, the locations of its subnets, and the importance of performance, and slave authoritative servers might be provided.
Executive Summary The purpose of this report is to design a modern efficient network solution that will benefit the Company’s global enterprise operations. The company consists of ten departments having 1,000-employee. The IT department of Corporation is looking at designing and creating a cost efficient network internally that will extend to 10 geographic locations. We have outlined a plan for the development of an addressing and naming model in an environment of the ten departments in a 1,000-employee organization. We can access each department through these address name from Internet connection. This organization is using a common data center of twenty backend enterprise servers. It has one primary data center operation. Network design uses a common data center of twenty (20) backend enterprise servers. The company wishes to upgrade its network and correct any security flaws in its infrastructure as part of this move.
Employees and customers can get information about the company’s product and services through this networking facility. The IT department of Corporation is looking at designing and creating a cost efficient network internally that will extend throughout the country. The system will provide to the company a system point-of-sale invoicing, sales management, revenue reporting, commission tracking for sales representatives, inventory management. As internal staff within the company, we are familiar with the current networking and have management onsite to reduce preliminary work. This report presents recommendations that allow Alpha Corporation to remain successful for years to come.
Conclusion
Without proper name resolution, users cannot locate resources on the network. The Domain Name System distributes the responsibility of assigning domain names and mapping those names to IP addresses by designating authoritative name servers for each domain. It is critical that the design of the DNS namespace be created with Active Directory that the namespace that exists on the Internet not conflict with an organization's internal namespace.

References
Stallings, W. (2009). Standards. (6th Ed.). Business Data Communications. Upper Saddle River, New Jersey: Prentice Hall.
Oppenheimer, P. (2005). Top-Down Network Design, Second Edition. Cisco Press.
Silverston, L., & Agnew, P. (2011). The Data Model Resource Book: Volume 3: Universal Patterns for Data Modeling. Chichester: Indianapolis: John Wiley & Sons.
Curtis, V. (2014). Creating A Business Plan For Dummies (e-book). Hoboken: Wiley. Accessed February 8, 2015.
Ambler, S. W. (1988). Building Object Applications That Work: Your Step-by-Step Handbook for Developing Robust Systems with Object Technology. Cambridge: Cambridge University Press.
Lachev, T. (2006). Applied Microsoft Analysis Services 2005 and Microsoft Business Intelligence Platform. Chicago, Illinois: Prologika Press.
Napier, R. & Mugunth K. (2012). Pushing the Limits with Ios 5 Programming: Advanced Application Development for Apple Iphone, Ipad and Ipod Touch. Chichester, West Sussex: Wiley.