6-1 Assignment: Network Management Architecture

6-1 Assignment: Network Management Architecture IT-345 SNHU Cameron Thistle Interview: During the reality finding cycle and meetings with key organization engineers at OilMan, Inc., we have laid out the accompanying things for update: 1. 2. 3. 4. Operation Functions Responsibilities and Key Roles Business Layout Goals for the future Operation Functions: OilMan, Inc. is a medium-sized oil and gas company that focuses solely on oil exploration and drilling in the continental United States. There are four significant workplaces in Fort Worth and Houston, Texas; Pennsylvania's Pittsburgh and Colorado's Denver. The corporate base camp is the Post Worth area of the Business. Responsibilities and Key Roles: We have been provided with the following roles and responsibilities for each location: 1. The environment and network infrastructure are utilizing slow and out-ofdate legacy equipment. Every office has a 10-base neighborhood (LAN) with three 24-port daisy banded center points that are then associated with an outside confronting switch. Using bonded 4 x T1 lines, the company has WAN connectivity between all four offices in a ring topology, providing a total bandwidth of 6 Mbps between each location. 2. The datacenter for the association is situated in the Stronghold Worth office. Data replication and backups to the Fort Worth office must be maintained by the East and West offices, and Houston must provide a secondary copy for disaster recovery. The information aggregates have been growing by 10% every year and will proceed with this development for the following three years. 3. The Fort Worth office has internet access (10 Mbps Ethernet) for primary 4. 5. 6. 7. 8. surfing, and the Houston office has internet access (5 Mbps Ethernet), which serves as both primary for that office and backup for the remaining three locations. The web association comprises of a solitary 128 Kbps ISDN line. Video conference equipment can communicate both internally and externally in all locations. The central command envelops all the organization leaders, HR, training, accounting, and designing/development offices. The Stronghold Worth area is the essential office for all correspondences until the end of the organization. Email, SharePoint, IP telephony, and geographic information systems are just a few of the essential business applications it supports. All personnel from the West region's legal, finance, and IT departments, as well as personnel from the drilling department, are kept in the Denver office. The Pittsburgh office comprises of the designing/development division, IT work force, legitimate, and staff connected with the penetrating division in the East locale. The engineering department, IT staff, human resources, and safety are all located in the Houston office, which also serves as the disaster recovery center for the entire business. Business Layout: We have mapped out the following building's network layout using the information gleaned from interviews and other sources. Goals of the future: OilMan, Inc.'s management anticipates 15% growth in the industry, both internally (employee growth) and externally (creation of drilling sites). As a result, the current network, which has not been updated in at least ten years, requires not only an upgrade but also an overhaul to guarantee increased speed and data capacity for the four existing sites as well as any additional sites that might be required in the future. Applications: I've discovered the following critical servers and applications: 1. Microsoft office 365 2. Legal and Financial systems 3. VOIP 4. Geographic info. Systems 5. SharePoint 6. HR Apps These frameworks are required for OilMan to proceed with day-to-day activities and it's to the best of my knowledge that these frameworks just exist uniquely beyond the common records put away in SharePoint. Thusly, there are no excess servers or administrations for these basic applications in the even that a site, like Fort Worth, were to be disconnected under any condition. Also, we don't know what kind of firewall is currently in use, but we do know that each location has at least one. User Requirements: We anticipate that with a 15 percent increase in users, there will also be a 15 percent increase in data usage. As a result, the company's current network and design will not suffice. According to interviews with users, things are already very slow, and the limitations of the network make it take at least twice as long to do things that should take 10 minutes. Significant cycles like reinforcements are done quicker by sponsorship up the information locally, then sending the actual media to Houston for capacity instead of ignoring that reinforcement information the wire. Otherwise, backups are beginning to creep into operational hours, and the bandwidth of 6 Mbps is insufficient to handle both normal user traffic and backup operations simultaneously. Due to the rising usage and number of users, bandwidth-intensive applications like GIS and video conferencing systems are also showing signs of bandwidth limitations. Data Flow The Fort Worth internet connection, which is a 128 Kbps ISDN connection, currently handles all internet traffic for Fort Worth, Denver, and Pittsburgh. Houston has its own committed 128Kbps connection. Reinforcements are put away at the Houston area, however these occur over the joined 4 x T1 association, so they're being passed at the pace of 6 Mbps. However, there is simply not enough time to back up all the data at the remaining three sites within a reasonable amount of time due to the volume of data at each site. Additionally, considering that the three remaining sites will only have 2 Mbps of bandwidth to backup, which will triple the amount of time required, doing the backups simultaneously is not a viable option. All emails pass through the Fort Worth site because that's where the primary datacenter is currently located, as are the SharePoint file server and VoIP systems. There appears to be no redundancy of servers or load balancing. Network Architecture The following network architecture is what we believe to be the best solution for OilMan, Inc. to replace the company's current topology and accommodate future expansion. User Base and Asset Addressing The four parts of OilMan will relate to the following Internet Protocol Addressing to allow for expansion in the future: 1. The corporate network will use a Class B IP address of 172.16.16.0/20. This means that the subnet mask will be 255.255.240.0, which makes it possible to set up Classless Inter Domain Routing (CIDR) with 4,096 subnets and an IP address range of 172.16.16.0 - 172.16.31.255, or 4,094 connected devices all at once. This will permit all current gadgets to be associated with the organization, as well as future gadgets if OilMan decides to begin utilizing cell phones, for example, a Present to Your Own Gadget program. A user could have a desktop and a mobile device at the same time, necessitating two IP addresses per user. 2. For the IP address range of 172.16.17.1 to 172.16.17.254, the Denver location will use 172.16.17.0/24. 3. For the IP address range of 172.16.16.1 to 172.16.16.254, the Fort Worth location will use 172.16.16.0/24. 4. The Houston office will utilize 172.16.19.0/24 for IP address range 172.16.19.1 to 172.16.19.254. 5. For the IP address range of 172.16.18.1 to 172.16.18.254, the Pittsburg office will use 172.16.18.0/24. 6. This indicates that 12 additional subnets can be utilized between 172.16.20.0 and 172.16.31.0. These can be used to add new offices or locations to the OilMan business, create VPN access tunnels for remote devices, or separate Wi-Fi access for security reasons. Routing Logic Most of the routing will remain the same because the Fort Worth location will continue to handle all internet traffic, with failover and load balancing going through the Houston location. This will take into consideration overt repetitiveness to forestall full frameworks to be down, as well as give simplicity of blockage during times of high utilization. Reinforcement administrations will in any case be given by and directed to the Houston area. Because it requires a company to duplicate all its data and store it in two distinct offsite locations, redundant backup operations can be difficult and complex. This will double the costs of backup operations. This is a process that we seldom see utilized. An extra corporate Voice over Web Convention server for telephone utilities will be introduced in the Houston area to consider failover administration if the essential server in Stronghold Worth goes down. Performance Components All areas will be moved up to 45 Mbps Metro Ethernet administrations with the essential web connect being in Stronghold Worth, as recently expressed. A VPN association will be arrangement between the four existing areas to guarantee that all information for the organization is directed through one of two firewalls (Fort Worth and Houston). Reinforcement internet providers will be given by a Verizon FIOS association at 50 Mbps. If the Metro Ethernet connection fails for any reason, this will allow for redundancy. A similar innovation ought to never be utilized for overt repetitiveness since it puts every one of your eggs into one bushel, as it were. Security Mechanisms The primary thing that we might want to address is the association between the four destinations. As of now, the four reinforced T1 lines are not adequate, however the VPN is fine. With the move up to the WAN association utilizing 45 Mbps we will keep on utilizing the Webpage to-Webpage VPN using the Layer 2 Burrowing Convention (L2TP) and Web Convention Security (IPsec). The L2TP protocol will thus establish a secure connection between the four locations and IPsec will encrypt the transmitted data [VPN16]. A user can connect to the OilMan private network using a Remote Access VPN to remotely access resources and services. Laptop and tablet users in the field may benefit from this. The internet is used to establish a secure and private connection between the user and the private network. IP Services for Internet Access and WAN For a company of Oilman’s size, the current internet access services at 128 Kbps are far below any reasonable standard. As a result, this crucial link will be upgraded to a 45 Mbps Metro Ethernet connection so that it can fully accommodate both the current requirements and the anticipated expansion of internet access requirements in the future. A secondary internet connection with a speed of 50 Mbps that acts as a failover and can provide load balancing when the primary connection is under heavy use will be set up to guarantee uptime. These essential and optional administrations will completely supplant the 128 Kbps ISDN and 4 reinforced T1 associations. Topological Model The ongoing geography of the OilMan network is a ring organization. The new design will use a mesh topology for it. This considers Pittsburgh to be straightforwardly associated with Stronghold Worth and any remaining locales as displayed underneath. The Mesh architecture was chosen to improve connectivity and reduce network load when data is sent to a particular site. By doing this, other locations will still be able to connect even if one location goes completely offline for whatever reason. While properly implemented, it allows the network to withstand high traffic and allows for network expansion without disrupting other nodes on the network, it does increase costs and administration. Critical and Key Assets Oilman, Inc. has several key and critical assets that need to be maintained to ensure that essential resources are available to avoid service interruptions and downtime. Corporate VoIP systems and security systems (firewalls, routers, switches, etc.) are the critical assets we've identified. and safety mechanisms. Email services aren't on this list because, according to the Time to Live (TTL) settings in the MX record, they can be down for a few hours, so emails won't be lost in a short-term failure. We've included email servers, legal systems, and financial systems as key systems. These frameworks are pivotal to the everyday tasks of the organization however they're not so basic in that a blackout of these frameworks ought to negligibly affect the association in general. Notifications of Events and Monitoring One of the observing apparatuses that we propose to utilize is Nagios for organization and traffic checking as well as organization investigation. Nagios is open source so in-house professionals can adjust the code to suite the exceptional requirements of any business. Open-source code and closed source code are equally secure from a security standpoint. Nagios will permit Oilman the capacity to screen and advise network occasions with the goal that professionals can resolve issues quickly, even before the assistance work area is called. It will be possible to provide a low-cost solution to an old problem by utilizing a monitoring system. How does Oilman manage to keep up with network events without spending money or resources? Utilizing network monitoring tools that will enable notifications of the desired network events is the solution to this question. Additionally, application monitoring is supported by Nagios. System administrators can use this method to determine whether an application is offline while the machine is still running or whether the machine is down. This makes it possible to identify causes with greater precision and speed up the resolution process. Fault Management Nagios, as well as other organization checking instruments, offer a wide cluster of observing and ready choices. This can be accomplished in several ways, including sending emails and text messages and setting off audible alarms. The best way to figure out what the needs are is to have more conversations with the Oilman network staff to find out what works best for their needs and understanding levels. Other tasks can be automated as well. For instance, on the off chance that the email server goes down an optional email server can take over naturally or even be brought web-based by the observing programming. The setup choices to have the option to do just restricted by the requirements of the association are as well. Further, if an entire site goes disconnected an optional Nagios server can be housed at another area that naturally empowers the missing capabilities so no free time for different areas is seen. It may be able to lessen the impact of the outage by doing this. Governance of Performance It is possible to enable load balancing by utilizing network monitoring and analysis. This means that a specific site that is experiencing an increase in traffic can have services routed to another location to reduce the network load on a single location. Using secondary internet access that is already set up at a different organization site or a combination of the two is one way to accomplish this. This can assist in lowering the overall load on the network and avoiding potential network disasters. Management of Configurations The ring topology of the current network makes it possible for one site to fail, cutting off access to other sites. A mesh network is the setup we recommend. While network networks are harder to have an arrangement, they're more issue lenient than a ring geography since they consider a solitary area to be disconnected the leftover locales approach any remaining destinations. Further, the consider increment scaling without effect on existing locales, hence a site or two doesn't need to go disconnected when a totally new site is added to the corporate organization. Security Operations Security observing can be precarious because in-house checking devices will be unable to distinguish an assault, and contingent upon the ability level of the aggressors. In this way, we recommend observing of safety frameworks to be done both inside and beyond the corporate organization. By utilizing outsiders to screen outer access we can screen exactly what pariahs see. In addition, it permits monitoring if a network port is opened without the system administrators' knowledge. Interior checking may not be enough since assailants might have the option to cover their tracks while outer instruments that are obscure to aggressors may be able to see ports opened from an external perspective, empowering the Oilman network group to make the required moves. Additionally, ensuring that all computer, switch, router, and other component operating systems are always up to date with the most recent security patches can help close device vulnerabilities and prevent their exploitation. References Cooney, M. Cooney, M. (2023). Cisco issues critical warning after CIA WikiLeaks dump bares IOS security weakness. Retrieved 30 May 2023, from https://www.networkworld.com/article/3182871/cisco-issues-critical-warningafter-cia-wikileaks-dump-bares-ios-security-weakness.html StackPath StackPath. (2023). Retrieved 30 May 2023, from https://www.smartindustry.com/home/blog/11306695/oil-and-gas-data-flowsecurity-requires-both-protection-and-detection Types of VPN and types of VPN Protocols Types of VPN and types of VPN Protocols. (2023). Retrieved 30 May 2023, from https://www.vpnoneclick.com/types-of-vpn-and-types-of-vpn-protocols/ Labs, L. Labs, L. (2016). Mesh Topology Advantages for M2M Communication | Link Labs. Retrieved 30 May 2023, from https://www.link-labs.com/blog/mesh-networktopology-advantages-disadvantages Nagios - The Industry Standard in IT Infrastructure Monitoring Nagios - The Industry Standard in IT Infrastructure Monitoring. (2023). Retrieved 30 May 2023, from https://www.nagios.org/ Six open-source security myths debunked - and eight real challenges to consider Six open-source security myths debunked - and eight real challenges to consider. (2023). Retrieved 30 May 2023, from https://www.zdnet.com/article/six-opensource-security-myths-debunked-and-eight-real-challenges-to-consider/