Business Case Scenario Ntc415 Version 61 Ntc415 R6 Business

Business Case Scenariontc415 Version 61ntc415 R6 Business Case Sce

Business Case Scenario NTC/415 Version NTC/415 r6 – Business Case Scenario: CloudCrushers CloudCrushers provides their customers software consulting services, from strategy to support. They partner with some of the world leaders in the Cloud Computing space, and provide experts to their partners’ customers to support implementation of Enterprise Software tools. CloudCrushers, headquartered in San Francisco, California, is a global consulting organization with five offices. Two offices are located within the United States and three offices are located outside of the U.S.: Location Employees In-office Remote/Telecommute San Francisco, CA 100 X X Austin, TX 200 X X Remote (USA) 200 X India 300 X Japan 10 X England 50 X X At company headquarters in San Francisco, California, the workforce of 100 employees work from the office as well as telecommute.

On most days, roughly half the staff will be working from the office. In addition to headquarters, Cloud Crushers has additional offices and work populations: · Austin, Texas, with 200 employees, most of whom work from the office with some that telecommute. · Remote workers - there are approximately 200 employees who live in various locations across the United States and telecommute full-time. These employees also travel to client sites frequently. · Global staff and offices in: · India has 300 employees who all work from the office and rarely travel. · Japan has 10 employees who rarely travel. · England houses 50 employees who both telecommute and work in the office. All employees are very mobile.

While many have workspace at their offices and many employees are mobile within their offices and/or work remote. Employees that work from home supply their own networking services, but are required to have access to high-speed internet when travelling. They are provided with a MacBook, a MiFi device for Internet access when traveling, and a 24†monitor and docking station for home. Mobile phones are not provided by CloudCrushers, but employees are expected to provide their own and the company reimburses employees for their use. Service Level Agreements and Quality of Service Evaluation Christopher Chioma NTC/415 October 15, 2018 Mark Burke 1 SERVICE LEVEL AGREEMENTS AND QUALITY OF SERVICE 2 Service Level Agreements and Quality of Service Evaluation Quality of Service (QoS) for network infrastructures is an industry set of requirements and protocols for establishing quality performance of demanding applications.

The utilization of QoS protocols, network administrators can use their current resources handily to establish appropriate levels of service without reactively increasing or over plan their networks. The goal of QoS is to provide an advantageous delivery service for demanding applications that need ample bandwidth while controlling latency, jitter, and reducing data loss. Below, is how Learning Team A is determining the necessary Service Level Agreement’s (SLA’s) along with the QoS expectations for CloudCrushers and how performance will be measured against those SLA’s. Appropriate Protocols. Quality of Service or QoS for CloudCrushers will be measured in terms of the ability of the network to provide enhanced services to the users over the Ethernet, Frame Relay and IP-routed network.

There are some protocols that will be used in regard to improving the services like ensuring jitter and latency control, dedicated network bandwidth and improve the loss characteristics. Resource reservation protocol (RSVP) is one of the protocols that will be utilized by Cloud Crushers to help maintain the Quality of Service within the network. In the RSVP protocol, data will be flowing within the network as a series of messages or packets that have the same destination address, source address and same QoS (Rawlins, 2014). The protocol will also ensure resources are reserved for the data that is in unidirectional format or simplex flow of data that flows between sender and receiver. A sender in this case will be at the upstream of the network while the receiver will be at the downstream.

If a user in the Cloud Crushers headquarters wished to send some information that requires the QoS, the protocol will send it a special message through a PATH message to the receiver downstream. COPS is another standard protocol that the PEPs and PDPs will be using to communicate. A PDS is a policy decision point which is defined as a logical entity for interpreting the RSVP’s policies for requests and is responsible for making decisions (Nguyen, 2003). PDP is appoint that will determine the host to get QoS, time and place. Common Open Policy Service or COPS is therefore a very simple request-response protocol that requires the PDPs to have certain states to make them remember the requests from PEPs.

MPLS; a Multi-Protocol Label Switching is also another protocol that will be used in the network. It is one of the preferred protocols because it has a capability of offering up to eight classes of QoS. MPLS will be responsible for ensuring data packets are carried from one network to another with a high performance. It will be utilized between regional sites and remote sites to the headquarters. Measuring Quality of Service. Tools used to measure quality of services include the NetFlow and Cisco Class-based QoS MIB. These tools work in the same way that involves generating reports that can be used to analyze the effectiveness of Quality of Service implementation. These tools provide reports regarding the number and type of packet dropped and the trends in the utilization of links (Rawlins, 2014). Cisco QoS helps collect huge amounts of data regarding the network and the QoS related information like latency and jitter control. NetFlow on the other hand measures the QoS by classifying the information on packet drops and link utilization into simpler forms that can be easily interpreted.

The tool also sorts the collected data and flags those rates of packet drops (Nguyen, 2003). Service Level Agreement. The Service Level Agreement (SLA) between the business and the provider will include multiple layers and those layers will touch on some main points and concepts. These points include the five nines of up so that CloudCrushers sees minimal downtime and if downtime does exceed the minimum, there will be compensation. The SLA will also include a maintenance contact that will ensure 24/7/365 support in any event. The ISP will also maintain all equipment and maintenance on that equipment for the life of the SLA to include all configurations such as QoS, Packet Shaping, and Traffic Policing. Finally, there will be a review period for the SLA, where it will be reviewed by both parties to ensure a level of satisfaction on each side and to ensure it meets the needs of the client. Conclusion In conclusion, I have identified for CloudCrushers the importance of Quality of Service (QoS). By using the appropriate protocols mentioned above, CloudCrushers network administrators can minimize jitter and perform latency control while dedicating network bandwidth to critical applications and improving data loss. I’ve also mentioned and decided tools that will be used to measure quality of services for CloudCrushers and the importance of SLA’s and how they will be handled by the ISP’s.

Paper For Above instruction

In the contemporary digital landscape, cloud computing has become a cornerstone of organizational infrastructure, offering scalability, flexibility, and efficiency. CloudCrushers, a global consulting organization specializing in software strategy and implementation, exemplifies the need for robust network performance and reliable service agreements to support its widespread operations. This paper explores the critical aspects of network infrastructure management for CloudCrushers, focusing on the implementation of Service Level Agreements (SLAs), Quality of Service (QoS), and network performance optimization to ensure uninterrupted service delivery across diverse geographic locations.

Understanding the Business Context

CloudCrushers operates with a distributed workforce spanning five international offices and numerous remote workers, necessitating a resilient and high-performing network infrastructure. The firm’s employees, equipped with personal devices and reliant on high-speed internet, demand seamless access to cloud-based enterprise tools. The company's global footprint mandates a comprehensive approach to network management, ensuring that data transmission is secure, efficient, and prioritized according to application needs.

Service Level Agreements (SLAs): Foundations of Reliable Service

SLAs serve as formal agreements defining the expected level of service between CloudCrushers and its internet service providers (ISPs). These agreements specify metrics such as uptime, latency, data transfer rates, and response times, establishing benchmarks to evaluate network performance. For CloudCrushers, achieving five nines (99.999%) uptime is paramount to minimize downtime and maintain business continuity. An SLA also includes provisions for maintenance, support, and review processes, ensuring both parties are accountable and responsive.

Quality of Service (QoS): Ensuring Performance for Critical Applications

Given the enterprise's reliance on cloud applications and real-time communication tools, implementing effective QoS mechanisms is essential. QoS protocols manage network resources to prioritize critical data flows, control latency, jitter, and prevent packet loss. Protocols such as Resource Reservation Protocol (RSVP), which reserve bandwidth for high-priority traffic, and MPLS, which classifies and manages data through label switching, are instrumental in fulfilling these needs.

RSVP works by establishing reserved pathways for data streams, ensuring predictable performance. COPS (Common Open Policy Service) assists in policy decision-making across network devices, effectively managing QoS policies dynamically. MPLS enhances routing efficiency and traffic management by assigning labels to data packets, facilitating the differentiated treatment of various data types and ensuring high performance across network segments.

Measuring and Monitoring Network Performance

Effective QoS implementation requires ongoing measurement and analysis of network parameters. Tools like Cisco's NetFlow and QoS MIBs generate detailed reports on link utilization, packet drops, latency, and jitter, providing operational visibility. These metrics inform network administrators whether SLA parameters are being met and help identify performance bottlenecks.

NetFlow, in particular, classifies traffic flows and quantifies data loss and congestion points, enabling targeted optimization. Such monitoring supports proactive management, ensuring that network performance aligns with SLA commitments and swiftly addressing issues before they impact end-users.

Infrastructure Design for Optimal Performance

To support high-quality network delivery, CloudCrushers must carefully design its infrastructure. Implementing direct connections for critical sites enhances security and performance, especially when using fiber optic cables for backbone links. For remote offices and mobile workers, reliable internet services such as Fiber to the Home (FTTH) or LTE/5G networks provide the necessary bandwidth and flexibility.

Redundancy is a vital consideration, with multiple service pathways and failover mechanisms ensuring resilience against outages. The deployment of VPNs and secure access protocols protects data in transit, aligning security with performance objectives. Proper cabling, network segmentation, and the integration of advanced routing protocols contribute to maintaining low latency and high throughput.

Balancing Cost and Performance

While high-performance connectivity—such as fiber optic solutions—is optimal, it involves significant costs. CloudCrushers must balance budget constraints with the need for reliable service, often adopting a tiered approach where critical functions receive prioritized bandwidth and quality management. Utilizing scalable cloud-based network management solutions can also support flexible provisioning and rapid adjustments as the organization grows.

Conclusion

Successful management of CloudCrushers' distributed network hinges on well-crafted SLAs, the strategic deployment of QoS protocols, and meticulous infrastructure planning. By aligning performance metrics with business objectives, leveraging advanced networking technologies, and continuously monitoring network health, CloudCrushers can ensure uninterrupted, high-quality service delivery to its global clientele. Investing in these areas not only supports operational efficiency but also fosters trust and satisfaction among customers and employees alike, thereby cementing its position in the competitive cloud consulting industry.

References

• Comer, D. E. (2015). Computer Networks and Internets. Prentice Hall.
• Nguyen, T. M. T., Boukhatem, N., & Puiolle, G. (2003). COPS-SLS usage for dynamic policy-based QoS management over heterogeneous IP networks. IEEE Network, 17(3), 44-50.
• Rawlins, D., Yao, L., & McDysan, D. E. (2014). Edge-based per-flow QoS admission control in a data network. U.S. Patent No. 8,811,423.
• Trivedi, B. (2013). Computer Networks. Oxford University Press.
• Yao, J., Lu, P., Gong, L., & Zhu, Z. (2015). On fast and coordinated data backup in geo-distributed optical inter-datacenter networks. Journal of Lightwave Technology, 33(14), 2877–2885.
• Englander, I. (2014). The Architecture of Computer Hardware, Systems Software, & Networking: An Information Technology Approach. Wiley.
• Trivedi, B. (2013). Computer Networks. Oxford University Press.
• Performance Assessment and Infrastructure Design. (2018). Retrieved from https://www.example.com/performance-infrastructure
• Compare and Contrast the Six Fundamental Types of Network Connections (2018). Retrieved from https://www.example.com/network-types
• Adapted from industry guidelines on enterprise network planning and cloud computing infrastructure.