Chapter3 : Lab 3.5.2 Creating an Overall Project Goal

Tinggalkan komentar

Step 1: Gather information about the company goals that this network upgrade will facilitate

Consider what FilmCompany sees as benefits that the upgraded network will provide to their business in

terms of their new stadium contract. These business benefits will not be the direct technical improvements

that networking technicians and engineers may see. A business manager does not necessarily see the

network in terms of bandwidth, latency, efficient protocols, or device operation. They are more likely to

consider issues of profitability, flexibility, customer service, and reliability.

As a network designer, you take into account all the information obtained through interviewing the company managers and key members of the staff.

a. Draft informal notes of what you consider to be the business benefits in this case.

b. Use word processing software to create a Project Goal document based on these notes.

c. Organize or group your informal notes and save these in your Project Goal document.

General headings could include:

  • • Financial goals
  • • Job management goals
  • • Customer communication goals

Step 2: Summarize important goals in a list

a. Examine the general goals recorded and summarize these as three or four key points.

1)

2)

Begin each point with a verb, such as Provide, Increase, Improve, or equivalent word. Try to include a measurable achievement if possible.

For example:

Provide the stadium with a broadcast-quality, 30-minute highlight video package within 3 hours of the conclusion of an event.

b. Save the list of important goals in your Project Goal document.

Step 3: Develop an overall project goal statement

a. Write a single statement that introduces the summarized important goals.

The proposed network upgrade will enable FilmCompany to increase its share of

the sports event video market through:

  • • Improved response times to customer requests
  • • Improved processing and delivery of video content across the network
  • • Improved communications access to customer facilities
  • • Ability for improved flexibility in meeting customer needs

b. Add this statement to your Project Goal document.

Step 4: Obtain agreement from the company on the project goal statement

FilmCompany has to agree with your assessment of the Project Goal before you proceed further with the

design. If this is agreement is not obtained, the network you design may not meet the FilmCompany overall business requirements. An agreement provides clarification and acknowledgement of why the upgrade is to occur and what it is to achieve.

a. Discuss your Project Goal document with another student and arrive at an agreed-upon Project Goal.

It may be necessary to amend the statement and important goals before agreement is reached.

b. Save your Project Goal document and retain it for the next stages of this network design case study.

Step 5: Reflection

Consider the issue of communication between the network designer and a manager of the company

considering an upgrade of the business network. The network designer is trained in network operation and performance and how to optimize network resources and technologies to best provide network services. To the manager, the network is only one of a number of business tools that the company may use. The business manager probably wants to improve profitability and sees an enhanced network as a tool to help achieve that goal. A business manager is not likely to relate to a goal that is expressed solely in technical terms, such as an upgraded LAN with higher bandwidth, less latency, and maximized server utilization. Although most designers may want to talk about network capabilities, the lifecycle approach is about customer requirements and enabling the business process.

Discuss some strategies that will enable clear communication between a network designer and a business manager so that the resulting Project Goal document represents business needs that ultimately can be met by a network design.

Mahasiswa yang tertarik untuk jaringan, termasuk komputer, sistem TI, dan teknologi, mungkin cenderung terlalu fokus pada aspek teknis desain jaringan. Pada tahap awal siklus desain, penting bagi siswa mengembangkan kesadaran tentang keharusan usaha yang akan meng-upgrade drive jaringan dari alam.

Iklan

Chapter3 : Lab 3.5.3 Creating a Scope Statement

Tinggalkan komentar

Step 1: Consider how meeting the project goals will impact the existing network

a. As the network designer, look at the existing network topology and the services that it provides.

Consider how much of the network is affected or changed as a result of the project.

b. Record what areas of the existing network will have to change or will in some way be affected by

meeting the project goals.

Draft informal descriptive notes of these possible changes. Organize these notes under headings

such as:

  • • Access Layer
  • • Distribution Layer
  • • Core Layer
  • • Data Center
  • • Network Services
  • • WAN Access

c. Use word processing software to create a Project Scope document based on these notes.

Step 2: Refine and record the proposed changes to the existing network

a. Distinguish between possible upgrades to existing network resources, such as additional servers or

VLANs, and completely new additional resources, such as QoS and WAN links.

b. Record which areas and users will be affected by these changes.

c. Include these network changes in your Project Scope document.

Step 3: Define the areas of the existing network not covered by the project

It is important to note the parts of the existing network that are not within the areas covered by the project.

These out-of-scope areas are defined so that there is no misunderstanding between the NetworkingCompany and FilmCompany management.

In this case study, for example, providing IP telephony services may be a future consideration, but it is not

within the scope of this project.

Clearly state these out-of-scope areas in your Project Scope document.

Step 4: Compile and present the project scope document

FilmCompany has to agree with your assessment of the Project Scope before you proceed further with the design. An agreement ensures that there is a common understanding about what is included in the network upgrade project and what is not included.

a. Discuss your Project Scope with another student to ensure that the issues you present are clear.

b. Save your Project Scope document and retain it for the next stages of this network design case study.

Step 5: Reflection

It is important that a project have clearly defined boundaries so that all parties know what is included and

what is not. Consider the issues of ensuring that customer business and network needs are satisfied before the scope is broadened beyond what is feasible and required.

What strategies could be used to ensure that a project scope is developed that is clear and appropriate?

Pastikan bahwa setiap layanan jaringan baru dan teknologi yang tidak termasuk dalam ruang lingkup semata-mata karena mereka dapat, pastikan mereka selaras dengan kebutuhan perusahaan dan tujuan.
• Apakah orang yang berbeda, baik dari perusahaan desain jaringan dan bisnis, meninjau lingkup
proyek dan memberikan interpretasi mereka untuk memastikan bahwa itu berarti hal yang sama untuk semua orang.

Chapter3: Lab 3.5.4 Developing Network Requirements

Tinggalkan komentar

Step 1: Record the company business goals and constraints that will influence the network design

As the network designer, you need to identify and prioritize the business goals of FilmCompany as defined in the Project Goals document. Develop your understanding of what these goals are from the FilmCompany case study information.

a. List these goals in order of priority.

b. Expand and consider the details of how these goals can be achieved using the network as a platform.

c. Note any constraints that these expanded goals may impose on the network design, such as retaining

the current number of IT and network support staff.

d. Use word processing software to create a Network Requirements document.

e. Clearly state the business goals and constraints in the document.

Step 2: Record the technical requirements that will influence the network design

a. Evaluate each of the business goals and determine the technical requirements to meet the goals.

List these technical requirements under the headings of:

  • • Scalability
  • • Availability and Performance
  • • Security
  • • Manageability

b. Initially, list all technologies that may be able to meet these technical requirements.

c. Include these requirements in your Network Requirements document.

Step 3: Record the user requirements that will influence the network design

a. Consider the types of users that will influence the network design. These users may be onsite, in the

office, in the video editing room, offsite (at the stadium), or mobile. Which types of users generate the heaviest amount of network traffic? Which types generate the lightest traffic?

How might different types of users be grouped for Access Layer purposes?

b. Include these requirements in your Network Requirements document.

Step 4: Record the application requirements that will influence the network design

a. Consider the type of applications that will influence the network design.

What applications are essentially device-based, with minimal network requirements?

Which applications are network-intensive?

Which applications and services are delivered onsite, in the offices, and which may need to be delivered offsite over the WAN or to mobile users?

b. Include these requirements in your Network Requirements document.

Step 5: Develop the network requirements

a. Refine the technical requirements of the network to match user and application requirements.

What compromises may have to be made to ensure that the project remains within the business

constraints?

b. Finalize the technical requirements of the network that will meet the project goals.

c. Discuss and review your Technical Requirements document with another student to ensure it addresses all the business, user, and application requirements within the Project Scope and does not unnecessarily address out-of-scope requirements. Modify the document as necessary.

d. Save and retain your Technical Requirements document for the next stage of this network design

case study.

Step 6: Reflection

Developing the technical requirements of a network that meets the project goals, while remaining within

scope, requires knowledge of the available and appropriate technologies and services.

Discuss strategies that will ensure that a network design team is up-to-date with networking technologies and their applications.

 

Berlangganan ke jurnal teknis dan industri (baik hardcopy dan online)
• Menghadiri pe
luncuran dan demonstrasi produk
• Menghadiri seminar pelatihan dan kursus
• M
enyusun dan melaksanakan rencana pengembangan diri profesional
• Memelihara industri saat ini dan sertifikasi vendor

Chapter3 : Lab 3.5.5 Analyzing an Existing Network

Tinggalkan komentar

Step 1: Document and confirm existing network topology, addressing, and naming schemes

a. Examine the existing network topology diagram.

1)

2)

Record the current addressing scheme in a table.

Associate device names with addresses on the table.

b. Highlight any inconsistencies in the naming and addressing schemes.

For example:

  • • Naming some devices by location and others by function
  • • Inconsistent or confusing use of abbreviations
  • • Some gateway addresses as the first address of a subnet, others as the last address

c. Use word processing software to create a Current Network document.

Step 2: Identify those parts of the existing network that currently meet the project technical requirements

a. Examine the network topology and specifications.

Record which current features meet the technical requirements of the proposed network upgrade.

  • • Capacity (bandwidth, address ranges, VLANs)
  • • Redundant links
  • • Router and switch interfaces and ports
  • • Router and switch feature sets, memory, and processing capability
  • • WAN
  • • Wireless
  • • QoS

b. Include these strengths and capabilities in your Current Network document.

Potential strengths may include:

  • • New wiring and adequate communications closets
  • • Adequate space for a new data center
  • • Servers and PCs are current models and will not need replacement
  • • Some existing network switches and routers can be used in the new design

Step 3: Identify those parts of the existing network that can be scaled to meet the project

technical requirements

a. Examine the network topology and specifications.

Record which current features do not meet the technical requirements of the proposed network

upgrade but can be scaled within the capacity of the network to do so.

  • • Capacity (bandwidth, address ranges, VLANs)
  • • Redundant links
  • • Router and switch interfaces and ports
  • • Router and switch feature sets, memory, and processing capability
  • • WAN
  • • Wireless
  • • QoS

b. Include these scalable features and capabilities in your Current Network document.

Step 4: Identify those parts of the existing network that do not to meet the project technical requirements

a. Examine the network topology and specifications.

Record which current features do not meet the technical requirements of the proposed network

upgrade and what additional networking resources are required.

  • • Capacity (bandwidth, address ranges, VLANs)
  • • Redundant links
  • • Router and switch interfaces and ports
  • • Router and switch feature sets, memory, and processing capability
  • • WAN
  • • Wireless
  • • QoS

b. Include these weaknesses and shortfalls in your Current Network document.

Possible weaknesses include:

  • • Flat network design
  • • Insufficient bandwidth at Distribution Layer, no true Core Layer
  • • Servers poorly located
  • • Multiple networks, difficult to maintain
  • • Poor IP addressing structure
  • • No dedicated bandwidth for WAN connectivity
  • • Limited wireless implementation
  • • Limited security implementations

Step 5: Obtain agreement and authorization from the company to continue with the network upgrade design

a. Finalize the Current Network document so that the strengths and shortfalls are clearly and precisely

presented.

b. Discuss and review your Current Network document with another student to ensure that it clearly

states which parts of the network meet the technical requirements of the upgrade project and which

parts do not. Amend the document as necessary to clarify any areas that could be misunderstood. At

this stage of the network design process, a meeting with the FilmCompany management would be

held to obtain their agreement and authorization to continue with the design of the upgrade.

c. Save and retain your Current Network document so that it can be incorporated with the previous

documents to complete this network design case study.

Step 6: Reflection

Consider the resources and information that will facilitate the task of analyzing a current network.

  • • Having up-to-date documentation showing such information as addressing, device names,

VLAN allocations, switch port assignments

  • • Systematic and consistent host names, descriptions, and addressing schemes
  • • Software tools that record data flows and device identification
  • • Efficient and accurate fault and incidence reporting and clearance documentation to highlight

and record problems

sistematis dan nama host yang konsisten, deskripsi, dan skema pengalamatan
• Software tools yang merekam aliran
data dan identifikasi perangkat

Chapter4 : Lab 4.1.2 Characterizing Network Applications

Tinggalkan komentar

Step 1: Cable and configure the current network

a. Connect and configure the devices in accordance with the topology and configuration given.

For this lab, a PC workstation can substitute for a Discovery Server.

b. Ping between Host 1 and Discovery Server to confirm network connectivity.

Troubleshoot and establish connectivity if the pings fail.

Step 2: Configure NetFlow on the interfaces

NetFlow is configured to monitor data flows in or out of specific router interfaces. Ingress captures traffic that

is being received by the interface. Egress captures traffic that is being transmitted by the interface. In this lab,

the traffic will be monitored on both router interfaces and in both directions from within the console session.

a. From the global configuration mode, issue the following commands:

FC-CPE-1(config)#interface fastethernet 0/0

FC-CPE-1(config-if)#ip flow ?

Note the two options available:

egress Enable outbound NetFlow

ingress Enable inbound NetFlow

Which option captures traffic that is being received by the interface? ingress

Which option captures traffic that is being transmitted by the interface? egress

b. Complete the NetFlow configuration.

FC-CPE-1(config-if)#ip flow egress

FC-CPE-1(config-if)#ip flow ingress

FC-CPE-1(config-if)#interface fastethernet 0/1

FC-CPE-1(config-if)#ip flow ingress

FC-CPE-1(config-if)#ip flow egress

FC-CPE-1(config-if)#exit

FC-CPE-1(config)#end

Step 3: Verify the NetFlow configuration

a. From the privileged EXEC mode, issue the show running-configuration command.

For each FastEthernet interface, what statement from the running-configuration denotes that NetFlow

is configured?

interface FastEthernet0/0:

ip flow ingress

ip flow egress

interface FastEthernet0/1:

ip flow ingress

ip flow egress

b. From the privileged EXEC mode, issue the command:

FC-CPE-1#show ip flow ?

Note the three options available:

export Display export

Statistics

interface Display flow

configuration on Interfaces

top-talkers Display top talkers

FC-CPE-1#show ip flow interface

FastEthernet0/0

ip flow ingress

ip flow egress

FastEthernet0/1

ip flow ingress

ip flow egress

Confirm that the output shown above is displayed. Troubleshoot your configuration if this output is not

displayed.

Step 4: Create network data traffic

a. The captured data flow can be examined using the show ip cache flow command issued from

the privileged EXEC mode.

FC-CPE-1#show ip cache flow

Issuing this command before any data traffic has flowed should produce output similar to the example

shown here.

IP packet size distribution (0 total packets):

1-32 64 96 128 160 192 224 256 288 320 352 384 416 448 480

.000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000

512 544 576 1024 1536 2048 2560 3072 3584 4096 4608

.000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000

IP Flow Switching Cache, 0 bytes

0 active, 0 inactive, 0 added

0 ager polls, 0 flow alloc failures

Active flows timeout in 30 minutes

Inactive flows timeout in 15 seconds

last clearing of statistics never

Protocol Total Flows Packets Bytes Packets Active(Sec)

Idle(Sec)

——– Flows /Sec /Flow /Pkt /Sec /Flow /Flow

SrcIf SrcIPaddress DstIf DstIPaddress Pr SrcP DstP

Pkts

b. List the seven highlighted column headings and consider what use this information may be in

characterizing the network.

Protocol

Total Flows

Flows per Second

Packets per Flow

Bytes per Packet

Packets per Second

Seconds of active flow

Seconds of no flow (idle)

c. To ensure that flow cache statistics are reset, from privileged EXEC mode issue the command:

FC-CPE-1# clear ip flow stats

d. Ping the Business Server from Host 1 to generate a data flow.

From the command line of Host 1, issue the command ping 172.17.1.1 -n 200

Step 5: View the data flows

a. At the conclusion of the data flow, the details of the flow can be viewed. From privileged EXEC mode,

issue the command:

FC-CPE-1#show ip cache flow

Output similar to that shown below will be displayed. Some values and details may be different in

your lab.

IP packet size distribution (464 total packets):

1-32 64 96 128 160 192 224 256 288 320 352 384 416 448 480

.000 .900 .096 .000 .000 .000 .000 .002 .000 .000 .000 .000 .000 .000 .000

512 544 576 1024 1536 2048 2560 3072 3584 4096 4608

.000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000

IP Flow Switching Cache, 278544 bytes

5 active, 4091 inactive, 48 added

1168 ager polls, 0 flow alloc failures

Active flows timeout in 30 minutes

Inactive flows timeout in 15 seconds

IP Sub Flow Cache, 17416 bytes

0 active, 1024 inactive, 0 added, 0 added to flow

0 alloc failures, 0 force free

1 chunk, 1 chunk added

last clearing of statistics never

Protocol Total Flows Packets Bytes Packets Active(Sec)

Idle(Sec)

——– Flows /Sec /Flow /Pkt /Sec /Flow

/Flow

UDP-DNS 31 0.0 1 72 0.0 0.0

15.5

UDP-other 10 0.0 2 76 0.0 4.1

15.2

ICMP 2 0.0 200 60 0.3 198.9

15.3

Total: 43 0.0 10 61 0.3 10.2

15.5

SrcIf SrcIPaddress DstIf DstIPaddress Pr SrcP DstP

Pkts

< output omitted >

b. Examine your output and list details that indicate data flow.

Protocol

Total Flows

Flows per Second

Packets per Flow

Bytes per Packet

Packets per Second

Seconds of active flow

Seconds of no flow (idle)

 

Step 6: Stop the NetFlow capture

a. To deactivate NetFlow capture, issue the no ip flow command at the interface configuration

prompt.

FC-CPE-1(config)#interface fastethernet 0/0

FC-CPE-1(config-if)#no ip flow ingress

FC-CPE-1(config-if)#no ip flow egress

FC-CPE-1(config)#interface fastethernet 0/1

FC-CPE-1(config-if)#no ip flow ingress

FC-CPE-1(config-if)#no ip flow egress

b. To verify that NetFlow is deactivated, issue the show ip flow interface command from the

privileged EXEC mode.

FC-CPE-1#show ip flow interface

FC-CPE-1#

No output is displayed if NetFlow is off.

 

Step 7: Clean up

Erase the configurations and reload the routers and switches. Disconnect and store the cabling. For PC hosts

that are normally connected to other networks (such as the school LAN or to the Internet), reconnect the

appropriate cabling and restore the TCP/IP settings.

Step 8: Reflection

Consider the possible range of data flow types across a network and how a tool like NetFlow could be

implemented to assist in analyzing those flows.

List of data flow categories and types: Client to Client, Client to Server, Server to Client, and Server to Server

Email, intranet web, database flows, document file flows

Number of separate flows of each type, size (bytes) of each flow, time each flow is on the network

Daftar kategori dan jenis aliran data: Client untuk Klien, Klien ke Server, Server untuk Client, dan Server ke Server
Email, web intranet, aliran database, file dokumen arus
Jumlah arus yang terpisah masing-masing jenis, ukuran (bytes) dari setiap aliran, waktu setiap aliran pada jaringan

 

Final Configurations

Router 1

version 12.4

service timestamps debug datetime msec

service timestamps log datetime msec

no service password-encryption

!

hostname FC-CPE-1

!

boot-start-marker

boot-end-marker

!

enable password cisco

!

no aaa new-model

ip cef

!

!

!

interface FastEthernet0/0

ip address 10.0.0.1 255.255.255.0

ip flow ingress

ip flow egress

duplex auto

speed auto

!

interface FastEthernet0/1

ip address 172.17.0.1 255.255.0.0

ip flow ingress

ip flow egress

duplex auto

speed auto

!

interface Serial0/1/0

no ip address

shutdown

no fair-queue

clock rate 2000000

!

interface Serial0/1/1

no ip address

shutdown

clock rate 2000000

!

!

ip http server

no ip http secure-server

!

!

!

control-plane

!

!

!

line con 0

password cisco

login

line aux 0

line vty 0 4

password cisco

login

!

scheduler allocate 20000 1000

end

Chapter4 : Lab 4.2.3 Analyzing Network Traffic

Tinggalkan komentar

Task 1: Design Network Access to FTP and Email Services

Step 1: FTP network considerations

File transfer traffic can put high-volume traffic onto the network. This traffic can have a greater effect on

throughput than interactive end-to-end connections. Although file transfers are throughput-intensive, they

typically have low response-time requirements. As part of the initial characterization of the network, it is important to identify the level of FTP traffic that will be generated. From this information, the network designers can decide on throughput and redundancy requirements.

a. List possible file transfer applications that would generate traffic on the FilmCompany network.

Document sharing

Video production file transfer

b. List these applications by priority based on response time.

1. Video production file transfer

2. Document sharing

c. List these applications by priority based on bandwidth requirements.

1. Video production file transfer

2. Document sharing

 

Step 2: Email network considerations

Although customers expect immediate access to their emails, they usually do not expect emails to have

network priority over files that they are sharing or updating. Emails are expected to be delivered reliably and accurately. Generally, emails are not throughput-intensive, except when there are enterprise-wide mail-outs or there is a denial of service attack.

List some email policies that could control the volume of email data and the bandwidth used.

Membatasi ukuran lampiran email

Membatasi nomor penerima pesan email

Memastikan spam terfilter sebelum menjangkau LAN

Step 3: Configure and connect the host PCs

a. Set the IP addresses for PC1 and PC2 as shown in the configuration table.

b. Establish a terminal session to router R1 from one of the PCs, and configure the interfaces and

hostname as shown in the configuration table.

 

Task 2: Configure NBAR to Examine Network Traffic

Step 1: Enable NBAR Protocol Discovery

NBAR can determine which protocols and applications are currently running on a network. NBAR includes the

Protocol Discovery feature, which identifies the application protocols operating on an interface so that

appropriate QoS policies can be developed and applied. To enable Protocol Discovery to monitor selected

protocols on a router interface, issue the following commands from the global configuration mode:

FC-CPE-1(config)#interface fastethernet 0/0

FC-CPE-1(config-if)#ip nbar protocol-discovery

Step 2: Confirm that Protocol Discovery is configured

From the privileged EXEC mode, issue the show running-config command and confirm that the following

output appears under interface FastEthernet 0/0:

interface FastEthernet0/0

ip address 10.0.0.1 255.255.255.0

ip nbar protocol-discovery

If protocol-discovery is not confirmed, reissue the configuration commands for interface FastEthernet

0/0.

 

Task 3: Generate and Identify Network Traffic

Step 1: Generate FTP traffic

The Mozilla Thunderbird email client program will be downloaded from Discovery Server as an example of FTP.

a. On PC1, launch a web browser and enter the URL ftp://server.discovery.ccna,

Alternatively, from the command line, enter ftp server.discovery.ccna. If DNS is not

configured the IP address 172.17.1.1 must be used instead of the domain name.

b. Locate the file thunderbird_setup.exe in the pub directory, download the file, and save it on PC1.

Repeat this step for PC2.

Step 2: Generate Email traffic

If the Thunderbird email client has been installed and email accounts set up on both PC1 and PC2, proceed

to Step 2d. Otherwise, install and set up the email client on PC1 and PC2 as described in Steps 2a through 2c.

a. Install the Thunderbird email client on PC1 and PC2 by double-clicking the downloaded

thunderbird_setup.exe file and accepting the default settings.

b. When the installation has completed, launch the program.

c. Configure email account settings as shown in this table.

1) On the Tools menu, click Account Settings.

2)

3)

Complete the required Thunderbird Account Settings.

In the left pane of the Account Settings screen, click Server Settings and complete the

necessary details.

4) In the left pane, click Outgoing Server (SMTP) and complete the proper configuration for the

Outgoing Server (SMTP).

d. Send and receive two emails between accounts on each PC.

Step 3: Display the NBAR results

With Protocol Discovery enabled, any protocol traffic supported by NBAR, as well as the statistics associated

with that protocol, can be discovered.

a. To display the traffic identified by NBAR, issue the show ip nbar protocol-discovery

command from the privileged EXEC mode.

FC-CPE-1#show ip nbar protocol-discovery

b. List each protocol identified and the Input and Output information.

Output:

ftp 18 16

1295 1288

0 0

0 0

c. Although the data traffic in this lab may not be sufficient to generate values for the 5min Bit rate

(bps) and 5min Max Bit Rate (bps) fields, consider and discuss how these values would be applied

to designing an FTP and email network.

_____________________________________________________________________________

Dapat membantu menentukan rata-rata dan puncak kebutuhan bandwidth jaringan.

Step 4: Use NBAR to monitor other data traffic

NBAR can identify and monitor a range of network application traffic protocols.

From the privileged EXEC mode of the router, issue the command show ip nbar port-map and note the output displayed.

FC-CPE-1#show ip nbar port-map

List some protocols that you consider should be monitored and policies applied to.

Output

port-map bgp udp 179

port-map bgp tcp 179

port-map bittorrent tcp 6881 6882 6883 6884 6885 6886

6887 6888 6889

port-map citrix udp 1604

port-map citrix tcp 1494

port-map cuseeme udp 7648 7649 24032

port-map cuseeme tcp 7648 7649

port-map dhcp udp 67 68

port-map directconnect tcp 411 412 413

port-map dns udp 53

port-map dns tcp 53

port-map edonkey tcp 4662

port-map exchange tcp 135

port-map fasttrack tcp 1214

port-map finger tcp 79

port-map ftp tcp 21

port-map gnutella udp 6346 6347 6348

port-map gnutella tcp 6346 6347 6348 6349 6355 5634

port-map gopher udp 70

port-map gopher tcp 70

port-map h323 udp 1300 1718 1719 1720 11720

port-map h323 tcp 1300 1718 1719 1720 11000 – 11999

port-map http tcp 80

port-map imap udp 143 220

port-map imap tcp 143 220

port-map irc udp 194

port-map irc tcp 194

port-map kerberos udp 88 749

port-map kerberos tcp 88 749

port-map l2tp udp 1701

port-map ldap udp 389

port-map ldap tcp 389

port-map mgcp udp 2427 2727

port-map mgcp tcp 2427 2428 2727

port-map netbios udp 137 138

port-map netbios tcp 137 139

port-map netshow tcp 1755

port-map nfs udp 2049

port-map nfs tcp 2049

port-map nntp udp 119

port-map nntp tcp 119

port-map notes udp 1352

port-map notes tcp 1352

port-map novadigm udp 3460 3461 3462 3463 3464 3465

port-map novadigm tcp 3460 3461 3462 3463 3464 3465

port-map ntp udp 123

port-map ntp tcp 123

port-map pcanywhere udp 22 5632

port-map pcanywhere tcp 65301 5631

port-map pop3 udp 110

port-map pop3 tcp 110

port-map pptp tcp 1723

port-map printer udp 515

port-map printer tcp 515

port-map rcmd tcp 512 513 514

port-map rip udp 520

port-map rsvp udp 1698 1699

port-map rtsp tcp 554

port-map secure-ftp tcp 990

port-map secure-http tcp 443

port-map secure-imap udp 585 993

port-map secure-imap tcp 585 993

port-map secure-irc udp 994

port-map secure-irc tcp 994

port-map secure-ldap udp 636

port-map secure-ldap tcp 636

port-map secure-nntp udp 563

port-map secure-nntp tcp 563

port-map secure-pop3 udp 995

port-map secure-pop3 tcp 995

port-map secure-telnet tcp 992

port-map sip udp 5060

port-map sip tcp 5060

port-map skinny tcp 2000 2001 2002

port-map smtp tcp 25

port-map snmp udp 161 162

port-map snmp tcp 161 162

port-map socks tcp 1080

port-map sqlnet tcp 1521

port-map sqlserver tcp 1433

port-map ssh tcp 22

port-map streamwork udp 1558

port-map sunrpc udp 111

port-map sunrpc tcp 111

port-map syslog udp 514

port-map telnet tcp 23

port-map tftp udp 69

port-map vdolive tcp 7000

port-map winmx tcp 6699

port-map xwindows tcp 6000 6001 6002 6003

Step 5: Clean up

Erase the configurations and reload the routers and switches. Disconnect and store the cabling. For PC hosts that are normally connected to other networks (such as the school LAN or to the Internet), reconnect the appropriate cabling and restore the TCP/IP settings

Challenge

This lab considered only the volume of FTP and email data traffic and its impact on network design. Reliable

access to servers is also important. In the space below, sketch a revised topology for this lab that would

provide redundancy for these services.

Chapter 4 : Lab 4.3.3 Prioritizing Traffic

Tinggalkan komentar

Step 1: Gather the data traffic information

a. Read through the StadiumCompany case study curriculum.

List the current types of data traffic carried by the StadiumCompany network as well as the types

planned for the future.

b. Refer to the topology diagram and the stadium network diagram information.

List the possible data sources and destinations on the StadiumCompany network. For example, there

is likely to be data communications between the stadium management and the vendor management,

but not between Team A and Team B.

Step 2: Prioritize the data traffic

  1. List the source, destination, and traffic type that will be assigned the High priority queue.
  2. List the source, destination, and traffic type that will be assigned the Medium priority queue.
  3. List the source, destination, and traffic type that will be assigned the Normal priority queue
  4. List the source, destination, and traffic type that will be assigned the Low priority queue.

Step 3: Finalize the Data Priorities

a. Discuss and review your data priority assignments with another student to ensure that it addresses allnpossible data. Modify your priorities as necessary.

b. Highlight on the StadiumCompany topology diagram the device or devices where data traffic priority policies are likely to be configured.

Step 4: Reflection

Ideally, it may seem that all data traffic should be given a priority and queued accordingly. Consider and

discuss the potential for network performance to be negatively affected if this policy were implemented

everywhere on the network.

Delay data sensitif akan melihat prioritas yang sama sebagai non-delay data sensitif. Suara, video, diberi prioritas yang sama sebagai lalu lintas lainnya, dll

Older Entries