Professional Documents
Culture Documents
Group Members Name: Lingling Meng mit121563s Name: Name: Student ID: Student ID: Student ID:
Summary:
Contents
1.Project Background ................................................................................................................................5 2.Project Objectives...................................................................................................................................5 2.1 Business Goals.............................................................................................................................5 2.2 Technical Goals...........................................................................................................................6 3.Project Design and Solution....................................................................................................................6 3.1 Proposed Solution........................................................................................................................6 3.1.1 Network Modeling...........................................................................................................7 3.1.2 Network Architecture.......................................................................................................8 3.1.3 QoS on Network.............................................................................................................10 3.1.4 Network Convergence ..................................................................................................12 3.2 Network Application.................................................................................................................12 3.3 Network Device.........................................................................................................................13 3.4 Cabling.......................................................................................................................................13 3.5 Cost............................................................................................................................................15 4.Improvement and Future Expansion.....................................................................................................16 4.1 Project Monitoring Network Monitoring...............................................................................16 4.2 Future Development..................................................................................................................16 5.Conclusion............................................................................................................................................17
1. Project Background
2. Project Objectives
merged into a single network to reduce operating costs and increase ease of operation.
To set the priority of the traffic, we can separate three different traffic data: VoIP voice traffic, VoIP signaling traffic, best-effort IP data traffic. Routers connected to low-bandwidth interfaces must separate voice packets and voice signaling packets to minimize jitter that was introduced by the signaling packets to the voice packets. DiffServ is supported on the signaling server, Voice Gateway media cards, and the IP devices connected to the network.
And for the layer 4 QoS, all layer 4 devices can classify IP packets by using source/destination TCP/UDP port number, protocol ID. So we dont need to worry too much for that. As we have set the QoS for layer 3 and layer 4, there are still some more issues we need to consider. We need to apply the broadcast and multicast rate limiting at egress from the switch ports, or optionally configure all the switch ports to rate limit ingress broadcast and multicast traffic. We need to limit the broadcast traffic rate in layer 2 and layer 3 switch to 150 broadcast packets per second in order to save for bandwidth for the voice traffic. We need to limit the multicast traffic rate in later 2 and layer 3 switch to 150 broadcast packets per second. Also, we need to disable the Spanning tree option on the layer 2 switch ports that connect to the network interface in the system. When we select and assign the IP address, there are a number of factors
to consider when determining if the subnets in the enterprise network will use private (internal) IP addresses or public IP addresses. Private or internal IP addresses that are not routed over the Internet. They can routed between separate intranets, provided that there are no duplicated subnets in the private IP addresses. Three blocks of IP address can be used for private intranets: 10.0.0.0-10.255.255.255, 172.16.0.0172.31.255.255, 192.168.0.0-192.168.255.255. Some routers and firewalls provide a Network Address Translation (NAT) function that allows the customer to map a registered globally-unique public IP address to a private IP address without renumbering an existing private IP address autonomous domain. And private IP address can be accessed selectively over the Internet by NAT. Consume limit resources, public IP addresses can be bought and used from the local ISP (Internet Service Provider). As the number of employees in these two headquarters is large, we can buy more than one public IP address from the local ISP (Internet Service Provider) allocated for each buildings in each headquarter. By each building, we can assign different IP addresses for their VLANs. For example, there are three buildings in headquarter in Sydney. We can assign private IP addresses from 172.16.0.0-172.16.20.255 for building A, IP addresses from 172.16.50.0-172.16.70.255 for building B and IP addresses from 172.16.100.0-172.16.120.255 for building C. All the connections from these three buildings are connected with the server level which for the server level, equipments and machines are assigned with the IP addresses from 192.168.0.0-192.168.40.0. Same idea applied for another headquarter in Melbourne. So whenever there are communications between these two headquarters, traffic will go through the internal network to the external network, and IP address will be translated by the NAT server.
consists in the packet handling on a QoS-enabled network. First step is classification for the packets which includes voice packets, voice signaling packets and data traffic packets. Signaling server can classify its packet as signaling packets. Voice Gateway Media Card can classify its packets as voice packets or voice signaling packets. And IP devices can classify its packets as voice or signaling packets. Second step is marking on the packets which the network devices can recognize different packets and forward them in a proper way which queuing (same as forwarding) is the third step. All packets entering the IP network must be classified and marked. Then the packets are placed into transmission queues of a certain priority. Consider the bandwidth demand on a WAN enterprise network, one of the issues of VoIP is the ability to use an existing WAN data network. When VoIP calls are active, routers configured with QoS(which priority voice traffic over data traffic) reduce the data traffic throughput by the amount of bandwidth being used for the VoIP call. Adding VoIP to the existing WAN data network might require an increase in the WAN bandwidth. To minimize voice delay and jitter in the mixed voice/data IP network, fragment larger packets before they traverse limited-bandwidth (<1Mbps) connections. Two types of fragmentation are more universal and not limited to a specific link-layer technology such as ATM and Frame Relay. Those methods are PPP fragmentation and IP fragmentation. PPP fragmentation splits large packets into multiple smaller packets and encapsulates them into PPP frames before they are queued and transmitted. PPP fragmentation enables higher-priority VoIP packets to be transmitted ahead of the lower-priority data packets fragments that have already been queued. Interleaving is the result of voice packets having a higher priority than data packets. A data fragment can be transmitted first; however when a higher-priority voice packet arrive, the voice packet will be sent ahead of the data packets. IP fragmentation configures all IP packets to a size determined by the MTU (Maximum Transmission Unit). Most of the routers use a default maximum packet size of 1500 bytes which can considered the amount of time to transmit over a lowbandwidth connection. Over bandwidth-limited connection (<1 Mbps), if layer 2 fragmentation is not used, the router must be configured to transmit smaller packets by adjusting the MTU size for the IP packets. Traffic shaping is used to determine which packets are dropped due to congestion and which packets receive priority. Traffic shaping works by queuing excess traffic to lower the amount of bandwidth across a Frame Relay WAN to limit traffic to a predetermined level. CIR (Committed Information Rate) is negotiated with the service provider. If voice and data traffic share the same virtual circuit for transmission, its necessary to use priority queuing along with traffic shaping to ensure that voice packets are not discarded or queued for a long period of time. On a low bandwidth link (< 1 Mbps), fragmentation and interleaving may have to be used. For the
11
Ethernet QoS, VoIP packets can be classified by the Ethernet header. Source/Destination MAC address, VLAN ID and 802.1P user priority bits are used to determine the classification for VoIP packets. As mentioned, DiffServ and IP address classification are recommended for layer 3 QoS.
12
these problems, QoS mechanisms can be applied to support VoIP network with consistent, acceptable and predictable voice quality.
Cisco Catalyst 3750-E series (Access layer) Passport 8600 in the core network Business Policy Switch (BPS) connected to the core network Signaling servers (Placed at the data center which is at the server level) Voice Gateway Media Cards (Placed at the data center which is at the server level) IP devices (like smartphones or IP phones)
3.4 Cabling
When consider the cabling in the network, we have to consider the link speed firstly. Link speed is an important consideration when consider VoIP in a WAN environment, as speed under 1 Mbps result in the serialization delay of VoIP packets. When small VoIP packets travel over a network that typically has packet size up to 1500 bytes, these larger packets introduce variable delay in the network which will impact voice quality. In order to
13
address the delay issue on a WAN, we can implement protocol prioritization, traffic shaping, DiffServ, fragmentation and interleaving (larger packet sizes incur higher serialization delays and introduce jitter into the VoIP stream) to fix.
If we look at the large enterprise network model, the following cabling has been used. Building A Cables between Access layer and layer 2 switchs are straight through fast Ethernet with speeds up to 100Mbit/s (100BASE-TX). By using these cables you can establish connection between access layer and distribution layer. This Cable runs on UTP Data and also uses CSMA/CD methodology to detect collisions.
Cables between Layer 2 switch and Diff Serv Domain are cross over fast Ethernet. This cabling is used to establish connection between the two. If we compare this to the straight through cable the internal wiring of Ethernet crossover cables reverses the transmit and receive signals. The purpose of a crossover cable is to connect one device directly to another device, without a hub or switch in the middle. Usually, the hub/switch performs the crossover for you. Cables coming from Building A in to the Core layer and in to Diff Serv Domain are once again cross over Ethernet cables. The same reasoning and benefits as cabling in Building A between Layer 2 Switch and Diff Serv Domain. Cabling between switches (core layer) and Diff Serv Domain (Server Layer) are Ethernet Crossover cables. Server Layer Cabling between Diff Serv Domain and WAN switch are 10 gigabit Ethernet. This type of cabling has a speed of 10 gigabits per second and supports copper and fiber cabling. However, due to its higher bandwidth requirements, higher-grade copper cables are required: category 6a or Class F/Category 7 cables for links up to 100m. 10 gigabit Ethernet standard was developed for WAN connections. Cabling between Diff Serv Domain and switchs are once again cross over Ethernet cables. Cabling between switchs and Enterprise Data Servers are straight through fast Ethernet cables, this is similar to access layer where switchs are accessing information the servers. These are two complete unlike devices so a straight through Ethernet is the only option to establish connection. Call server to Media gateway uses PSTN connections and the cables used are fiber optic. This type of cable is made out of glass and susceptible to
14
electromagnetic or radio frequency interference. It has speeds up to 10 Gbps and for long distances fiber optic cables costs less than copper.
3.5 Cost
Approximate cost list for the equipment used in this project(Numbers may Vary) Device Switches Type Cisco Catalyst 6500 series Cisco Catalyst 4500 series Cisco Catalyst 3750-E series Passport 8600 Router Switch Business Policy Switch Signaling servers Voice Gateway Media Cards Cisco 5 line phones Price ($) 1215. 8 300 120 Quanti ty 4 4 4 Total 4863.2 1200 480 0 4426.24 699 794.94 1168.88 0 65697 0 3190 1500 0 0 210000 294019. 26
$553.2 8
8 1 2 1
IP devices
300
Cables
100 600
PC's
700
300
TOTAL
15
switches for each level in the building, assuming approximately 100 users for each level which makes 9 switches for each building ( number of users may vary) For future development if there is a development in the company may lead in hiring some more staff which will be covered with the help of the switches used in the building. This will in return save the cost of establishing new cabling work.
5. Conclusion
Reference:
4cabling.com.au Amazon.com.au
17
18