enterprise network

59
Summer Internship Program 2014 Company Name: Hewlett Packard Branch: HPES Topic: Advanced Concept of Networking Address : HP Summer Training Nodal Centre, DN-14

Upload: santanu-mukherjee

Post on 11-Aug-2015

407 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: Enterprise network

Summer Internship Program 2014

Company Name: Hewlett Packard

Branch: HPES

Topic: Advanced Concept of Networking

Address:

HP Summer Training Nodal Centre,

DN-14

Salt Lake, Kolkata

West Bengal

Page 2: Enterprise network

Amity Institute of Telecom Engineering

And Management

Project Title: Enterprise Network End to End Solution

Faculty Guide: Neha Arora

Industry Guide: Amit Jaiswal

Submitted By:

Santanu Mukhopadhyay

B-Tech (E&T) (2011-15)

SEC A, En. No.-A1607111013

AMITY UNIVERSITY

Page 3: Enterprise network

Abstract

The sole purpose to study Enterprise Network is to create business simplicity across

worldwide. The side arms of successful networking are scalability, robustness, fault

identification, communication, modularity, security and maintaining privacy. The key

for making a network is to provide the essential tools and techniques that will offer

the quality of a private/public network.

As I discussed earlier the key purpose is to create business simplicity that means

creating IT/Infrastructure simplicity across the cities where an Enterprise Network is

connected. Obtaining success in failure/break-down conditions is the main purpose of

a network. So to achieve that requirement network designing involves certain

topologies, protocols, bandwidth allocation. Topology requirement can be described

as maintaining two adjacent networks against any failure in a single link or node.

Protocol requirement can be described as using dynamic/static routing protocol to

provide routes must be congestion free in a network. Bandwidth allocation is needed

to actively allocate extra bandwidth just to maintain the working condition in a

network. Design and Modification criteria is all over handed to a person called

Network Administrator, who maintains and solely responsible for anything(wanted or

unwanted) happens in a network.

(iii)

Page 4: Enterprise network

Acknowledgements

A Summer Internship Project is a golden opportunity for learning industrial skills and

self-development of practical knowledge. I do consider myself very privileged to have

so many wonderful people lead me through in completion of my project.

 

I would like to express my humbled gratitude and special thanks to Mr. Amit

Jaiswal, Lead Trainer, HPES, Salt Lake, Kolkata (WB) who in spite of being busy

with his duties and daily schedules took time out to guide and allowing me to carry

out my industrial project work at his esteemed organization .I can’t think where I

would have been without his sincere guidance. 

A Sincere thanks to you Sir.

I would like to express my sincere thanks to my faculty Neha Arora, Faculty,

AITEM, Amity University, Noida (UP) for her guidance and support throughout my

training period in my organization. She supported me by showing different method of

information collection about the company. She showed me the right direction toward

completion of my summer internship project in stipulated time period (42 days).

A Sincere thanks to you Madam.

Place: NoidaDate: 15/07/2014 Santanu Mukhopadhyay En.No.-A1607111013 B-Tech (E&T) (2011-15) AITEM AMITY UNIVERSITY

(iv)

Page 5: Enterprise network

Declaration

I, Santanu Mukhopadhyay, hereby affirm that My Project Titled “Enterprise

Network End to End Solution” is an original piece of project work(6 weeks

duration) carried out by me under the expert guidance of Amit Jaiswal (Lead Trainer,

HPES) and Neha Arora (Faculty, AITEM).

Place: NoidaDate: 15/07/14

Signature

(V)

Page 6: Enterprise network

Table of Contents

ABSTRACT III

ACKNOWLEDGEMENT IV

DECLARATION V

LIST OF FIGURES X

CHAPTER 1

INTRODUCTION

1.1 What is an Enterprise Network 1

1.2 Overview 1

1.3 What is End to End Solution 2

1.4 Different Architecture 3-4

(vi)

Page 7: Enterprise network

1.5 Study of Enterprise Network 5

1.6 Where the money is being spent 6

1.7 Theme 7

1.8 Organization 7

CHAPTER 2

MATERIALS & METHODS

2.1 Basic Setup 8-10

2.2 Methods 11

2.3 Basic Configuration 12-18

2.4 Basic Config. Commands 19

2.4.1 Router 19

2.4.2 RIP V2 Routing 20

2.4.3 IP DHCP Server Pool 20

(vii)

Page 8: Enterprise network

2.4.4 Access List 21

2.4.5 Network Address Translation 21-22

2.4.5.1 Static 21

2.4.5.2 Dynamic 21-22

2.4.6 Port Address Translation 22

2.4.7 TELNET & VLAN Database 23

CHAPTER 3

RESULTS & DISCUSSIONS 24

CHAPTER 4

CONCLUSIONs & RECOMMENDATIONs 25-26

(viii)

Page 9: Enterprise network

CHAPTER 5

IMPLICATION FOR FUTURE RESEARCH 27

CHAPTER 6

APPENDIX 28

CHAPTER 7

REFERENCES 29

(ix)

Page 10: Enterprise network

List of Figures

1. Figure 1-Enterprise Network Structure 42. Figure 2-Enterprise IT Spending 63. Figure 3-Model (.pkt) 84. Figure 4-DHCP Server Pool 205. Figure 5-VLAN Database 236. Figure 6-Basic Routing 247. Figure 7-VLAN Configuration 258. Figure 8-RIPV2 in USA Router 259. Figure 9-Ping Noida Router 2610. Figure 10-Making Delhi as DHCP 2611. Figure 11-All DNS Servers 27

(x)

Page 11: Enterprise network

CHAPTER 1______________________________

Introduction

1.1 What is Enterprise Network?

An enterprise network is a communication backbone that helps connect computers and related devices (smartphones) across various departments in an organization. An enterprise network helps to minimize the complexity through simplification of various communication protocols, improving system as well as internal and external enterprise data management.Enterprise Networks simplifies IT operations and creates new possible business opportunities with a flexible end and programmable purpose to networking.

1.2 Overview

1. Networking and Applications2. Connectivity and Services3. Maintenance4. Fault tolerance5. Load balancing6. Integration across systems7. Security

(1)

Page 12: Enterprise network

1.3 What is End to End solution?

At first we have to know what is the basic need for end to end solution in case of an

Enterprise network? So from a basic human common sense we can think what is the

reason for simplifying?

The answer comes to our mind which is

1. Simplifying (through modification) networking operations done in a private or

public network.

2. Increase in financial output of a government or private organization.

Rapid increase in smartphone user computer devices and has created huge traffic

congestion in network and complexity. Useful applications are experiencing an 80

percent increase rate in usage. Networks are failing to keep compatibility with rapid

changes in compute operations, which often produce problem in end-to-end delivery.

From the figure 1 we can see that an enterprise network is created amongst different

locations where the routers are connected through different vast locations like

Punjab, Haryana, Noida, Canada, USA, Dehradun, Greater Noida, Gurgaon, Delhi

and 24 port 3560 multilayer switches are connected with the routers and the servers

are used for creating server pools across the network. I used switches for creating

connectivity through router from private pcs.so if the user from USA wants to connect

with the user of Noida, traffic congestion arises ass it covers a vast distance along

with network congestion. So here to simplify the networking path, End to End

Enterprise Network Solution is needed.

(2)

Page 13: Enterprise network

1.4 Architecture

1. Nano level architecture (A Single PC in an Organization)

(Issue- Application related) (EX- A student in AMITY)(A single machine and a

router)

2. Micro level architecture (A Single Subnet in an Organization)

(Issue-Resource sharing)(Ex-A lab in AMITY)(Approximately 10’s of machines, 1-2

switches, 1000m cabling)

3. Mili level architecture (A Single Entity in large Office)

(Issue-Management and deployment)(Ex-AITEM in AMITY)(Approximately 100’s

of machines, 10-20’s switches, 3-5 Routers, 5 servers)

4. Typical level architecture (A Single Organization)

(Issues- Different resource monitoring)(Ex-AMITY)(Approximately 10’s locations,

1000’s of machines, 100’s of switches, 10’s of routers)

5. Kilo level architecture (National Network)

(Issue- Scalability) (Ex-LIC)(Approximately 100’s of locations, 10000’s of machines,

1000’s of switches, 100’s of routers)

6. Mega level architecture (Wide Network for a single organization)

(Issue-Robustness)(Ex-INTEL)(Approximately 10’s of countries, 1000s of locations)

7. Giga level architecture (Wireless Access)

(Issue-Control operations)(100’s of organizations, 100’s of countries, billions of devices)

(3)

Page 14: Enterprise network

FIG 1 Enterprise Network (Structure)

So as we can say in the image that an ENTERPRISE NETWORK supports thousands

of users across the wide geographical range of a company including thousands of

servers in each of the cities, each system is linked with each other in the network so

here complexity arises.

1. It is large as it can include 100000’s edge devices and 10000’s network devices.

2. It is Geographically Distributed amongst multiple countries.

3. The Network Administrator has the supreme priority over the entire network.

(4)

Page 15: Enterprise network

1.5 Why we should study Enterprise Network?

1.5.1 Money/Fund

Enterprise IT industries are spending lots of funds to improve, which is expected to increase steadily. In India rapid growth of IT Services as well as IT related business complexity is the main sole reason for investing in Enterprise IT applications and its infrastructure to minimize the level of complexity. Right now it’s about 200 million dollar spent.

1.5.2 Challenging Problems

1. Resource Management.

2. Network security and privacy management.

3. Capacity of a private or public network.

1.5.3 Others

1. Increasing gadgets (smartphones, tablets and laptops) and broadband access-

technologies demand for new services and applications worldwide.

(5)

Page 16: Enterprise network

1.6 Where the money is being spent??

1. Increasing connectivity requirements including VPN solutions.

2. Maintaining corporate information and resources.

3. Wide range of services including mobile devices.

4. IT applications for health purpose, financial purposes.

5. Security solutions for multinational corporate offices.

FIG 2 Enterprise IT Spending (2013 Budget)

(6)

Page 17: Enterprise network

1.7 Theme

Enterprise Network is the basic solution with respect to business and financial view of

an organization. It simply offers great value by creating End to End solution and as

the whole control of this network can be handled over the priority of a Network

Administrator so it can be integrated and improved in future if we need it.

1.8 Organization

Hewlett-Packard Company or HP is an American multinational information

technology corporation headquartered in Palo Alto, California, United States. It

provides hardware, software and services to consumers, small and medium-sized

businesses (SMBs) and large enterprises, including customers in the government,

health and education sectors.

The company was founded in a one-car garage in Palo Alto by William Bill

Redington Hewlett and Dave Packard. HP is the world's leading PC manufacturer and

has been since 2007, fending off a challenge by Chinese manufacturer Lenovo,

according to Gartner. It specializes in developing and manufacturing computing, data

storage, and networking hardware, designing software and delivering services. Major

product lines include personal computing devices, enterprise and industry standard

servers, related storage devices, networking products, software and a diverse range of

printers and other imaging products. HP markets its products to households, small- to

medium-sized businesses and enterprises directly as well as via online distribution,

consumer-electronics and office-supply retailers, software partners and major

technology vendors. HP also has services and consulting business around its products

and partner products. In 2013 it was the world's second-largest PC vendor by unit

sales.

(7)

Page 18: Enterprise network

CHAPTER 2______________________________

Materials & Methods

2.1 Basic Setup

Software Required-CISCO Packet Tracer (6.0.1)

FIG 3 Model (.pkt)

Enterprise Network is meant for creating business simplicity with simplifies

networking approach. Maintaining this similarity I made an Enterprise Network

covering these cities and countries and State of India.

1. Canada

(8)

Page 19: Enterprise network

2. Greater Noida

3. Gurgaon4. Delhi

5. Punjab

6. Haryana

Now Branch networks are

1. USA connected with Greater Noida router.

2. Dehradun connected with Gurgaon router.

3. Noida connected with Delhi router.

4. UP connected with Punjab router.

And hereby they are branch networks are connected with the main network.

I used Generic routers in this network.

Here I used two Multilayer switch (3560 series, 24 ports) (Layer 3), first one is

connected with Canada router and second one is connected with UP router.

Here I used three Generic Domain Name System Servers (www.yahoo.com(Delhi

router), www.dit.com(Haryana router), www.hpes.com (Noida router)), first one is

connected with Delhi router, second one with Noida router and third one with

Haryana router via 2950T 24 Switch (Delhi-Switch 12, Noida-Switch 24, Haryana-

Switch 23).

Branch router Dehradun (Connected via Gurgaon router to the main network) is

connected with two 2950T 24ps switch(Switch 30 & switch 20), first switch is

connected with two private pc’s(pc 28 pc 29) and second one with three pc’s(pc-

30,31,51)

(9)

Page 20: Enterprise network

Branch router USA (Connected via Greater Noida router to the main network) is

connected with two 2950T-24 switch (Switch 21 & Switch 22). First switch is

connected with two private pc’s (pc-32, 33) and second one with two pc’s (pc-49, 50).

Canada router is connected with a 3560-24ps Multilayer Switch 6, which is connected

with three 2960-24TT switches(Switch-13,14,15), and all three switches are

connected with two private pc’s each(Switch 13-pc 46 & pc 48),(Switch 14-pc 43 &

pc 47),(Switch 15-pc 44 & pc 13).

Branch router UP (Connected with the main network via Punjab Router) is connected

with a 3560-24ps Multilayer Switch5, which is connected with three 2960-24TT

switches(Switch-16,17,18), and all three switches are connected with three private

pc’s each(Switch 16-pc 34,35,36)(Switch 17-pc 37,38,39)(Switch 18-pc 40,41,42).

All routers has two serial ports

1. Serial 2/0

2. Serial 3/0

Two Fast Ethernet port

1. Fast Ethernet 0/0

2. Fast Ethernet 0/1

VLAN Admin-192.168.5.0/24 VLAN Finance-192.168.6.0/24

VLAN Students-192.168.1.0/24 VLAN Faculty-192.168.2.0/24 VLAN HP-

192.168.3.0/24

(10)

Page 21: Enterprise network

2.2 Methods

1. Basic Configuration (VLAN, VTP, Inter-VLAN)

2. RIP V2 Routing.

3. VLAN finance should not communicate with anyone in the network.

4. Noida Router can ping any pc but none can ping it but can access www.hpes.com

5. Make Delhi Server DHCP to provide the IP’s to all leaving multilayer switch

network.

6. Apply PAT on USA.

7. PC 28 should not communicate with PC 33.

8. Apply Static NAT on the server of Haryana.

9. All 3 DNS Server should be accessible by all pc’s.

(11)

Page 22: Enterprise network

2.3 Basic Configuration

Starting from the Canada Router

(“Se.-Po.2/0”) (UP) [“IP address 10.0.0.98/27 (SM)”]

(“Se.-Po.3/0”) (Down) {NOT SET}

(“Fa.-Eth. 0/0”) (UP) [“IP Address-10.0.1.33/27 (SM)”]

(“Fa.-Eth. 1/0”) (DOWN) {NOT SET}

Dehradun Router

(“Fa.-Eth. 1/0”) (UP) [“IP-192.168.1.1/24 (Sub Ma.)”]

(“PC-PT PC 28”) [((“IP-192.168.1.6”) (“SM”) (“DG-192.168.1.1”) (“DNS-

192.168.7.2))”]

(“PC-PT PC 29”) [((“IP-192.168.1.5”) (“SM”) (“DG-192.168.1.1”) (“DNS-

192.168.7.2))”]

(“Fa.-Eth. 0/0 IP”) (UP) [(“192.168.2.1/24”) (“SM”)]

(“PC-PT PC 30”) [((“IP-192.168.2.7”) (“SM”) (“DG-192.168.2.1”) (“DNS-

192.168.7.2”))]

(“PC-PT PC 31”) [((“IP-192.168.2.6”) (“SM”) (“DG-192.168.2.1”) (“DNS-

192.168.7.2”))]

(“Se.-Po.2/0”) (UP) [(“IP address -10.0.0.1/27”) (“SM”)]

(“Se.-Po.3/0”) (DOWN) {NOT SET}

(12)

Page 23: Enterprise network

USA Router

(“Fa.-Eth. 0/0”) (UP) [(“IP Address -192.168.3.1/24”) (“SM”)]

(“PC-PT PC 32”) [((“IP-192.168.3.5”) (“SM”) (“DG-192.168.3.1”) (“DNS-

192.168.7.2”))]

(“PC-PT PC 33”) [((“IP-192.168.3.6”) (“SM”) (“DG-192.168.3.1”) (“DNS-

192.168.7.2”))]

(“Fa.-Eth. 1/0”) (UP) [(“IP Address -192.168.4.1/24”) (“SM”)]

(“PC-PT PC 49”) [((“IP-192.168.4.5”) (“SM”) (“DG-192.168.4.1”) (“DNS-

192.168.7.2”))]

(“PC-PT PC 50”) [((“IP-192.168.4.6”) (“SM”) (“DG-192.168.4.1”) (“DNS-

192.168.7.2”))]

(“Se.-Po.2/0”) (UP) [(“IP address -10.0.0.66/27”) (“SM”)]

(“Se.-Po.3/0”) (DOWN) {NOT SET}

Gurgaon Router

(“Se.-Po.2/0”) (UP) [(“IP address 10.0.0.2/27”) (“SM)”]

(“Se.-Po.3/0”) (UP) [(“IP address 10.0.0.33/27”) (“SM”)]

(“Se.-Po.6/0”) (UP) [(“IP address 10.0.0.129/27”) (“SM”)]

(“Fa-Eth. 0/0”) (DOWN) {NOT SET}

(“Fa.-Eth. 1/0”) (DOWN) {NOT SET}

(13)

Page 24: Enterprise network

Greater Noida Router

(“Se.-Po.2/0 “) (UP) [(“IP address 10.0.0.34/27”) (“SM”)]

(“Se.-Po.3/0”) (UP) [(“IP address 10.0.0.65/27”) (“SM”)]

(“Se.-Po.6/0”) (UP) [(“IP address 10.0.0.97/27”) (“SM”)]

(“Fa.-Eth. 0/0”) (DOWN) {NOT SET}

(“Fa.-Eth. 1/0”) (DOWN) {NOT SET}

Delhi Router

(“Se.-Po.2/0”) (UP) [(“IP address 10.0.0.130/27”) (“SM”)]

(“Se.-Po.3/0”) (UP) [(“IP address 10.0.0.193/27”) (“SM”)”]

(“Se.-Po.6/0”) (UP) [(“IP address 10.0.0.161/27”) (“SM”)]

(“Fa.-Eth. 0/0”) (UP) [(“IP Address”) (“SM”)]

(“Fa.-Eth. 1/0”) (DOWN) {NOT SET}

Noida Router

(“Se.-Po.2/0”) (UP) [(“IP address 10.0.0.162/27”) (“SM”)]

(“Se.-Po.3/0”) (DOWN) {NOT SET}

(“Fa.-Eth. 0/0”) (UP) [(“IP Address 192.168.8.1/24”) (“SM”)]

(“Fa.-Eth. 1/0”) (DOWN) {NOT SET}

(14)

Page 25: Enterprise network

Punjab Router

(“Se.-Po.2/0”) (UP) [(“IP address 10.0.0.194/27”) (“SM”)]

(“Se.-Po.3/0”) (UP) [(“IP address 10.0.0.225/27”) (“SM”)]

(“Se.-Po.6/0”) (UP) [(“IP address 10.0.1.1/27”) (“SM”)]

(“Fa.-Eth. 0/0”) (DOWN) {NOT SET}

(“Fa.-Eth. 1/0”) (DOWN) {NOT SET}

Haryana Router

(“Se.-Po.2/0”) (UP) [(“IP Address 10.0.1.2/27”) (“SM”)]

(“Se.-Po.3/0”) (D0wn) {NOT SET}

(“Fa.-Eth. 0/0”) (UP) [(“IP Address 192.168.9.1/24”) (“SM”)]

(“Fa.-Eth. 1/0”) (DOWN) {NOT SET}

UP Router

(“Se.-Po.2/0”) (UP) [(“IP address 10.0.0.226/27”) (“SM”)]

(“Se.-Po.3/0”) (D0WN) {NOT SET}

(“Fa.-Eth. 0/0”) (UP) [(“IP Address 10.0.1.66/24”) (“SM”)]

(“Fa.-Eth. 1/0”) (DOWN) {NOT SET}

(15)

Page 26: Enterprise network

For server (www.yahoo.com)

(“IP Address”) [“192.168.7.2/24”]

(“SM”) [“255.255.255.0”]

(“DG”) [“192.168.7.1”]

(“DNS”) [“192.168.7.2”]

(“Fa.-Eth. 0/0”) (UP) [“192.168.7.2”]

For Server (www.dit.com)

(“IP Address”) [“192.168.9.5/24”]

(“SM”) [“255.255.255.0”]

(“DG”) [“192.168.8.1”]

(“DNS”) [“192.168.7.2”]

(“Fa.-Eth. 0/0”) (UP) [“192.168.7.2”]

(16)

Page 27: Enterprise network

Multilayer Switch 6

(“VLAN 1”) (DOWN) {NOT SET}

(“VLAN 2”) (UP) IP [(“192.168.5.1/24”)]

(“VLAN 3”) (UP) IP [(“192.168.6.1/24”)]

(“Fast Ethernet 0/4”) (UP) IP [“10.0.1.34/27 (SM)”]

(“PC-PT PC 46”) [((“IP-192.168.6.2”) (“SM”) (“DG-192.168.6.1”) (DNS-

192.168.7.2”))]

(“PC-PT PC 48”) [((“IP-192.168.5.2”) (“SM”) (“DG-192.168.5”) (“DNS-

192.168.7.2”))]

(“PC-PT PC 13”) [((“IP-192.168.5.4”) (“SM”) (“DG-192.168.5.1”) (“DNS-

192.168.7.2”))]

(“PC-PT PC 44”) [((“IP-192.168.6.4”) (“SM”) (“DG-192.168.6.1”) (“DNS-

192.168.7.2”))]

(“PC-PT PC 47”) [((“IP-192.168.6.3”) (“SM”) (“DG-192.168.6.1”) (“DNS-

192.168.7.2”))]

(“PC-PT PC 43”) [((“IP-192.168.5.3”) (“SM”) (“DG-192.168.5.1”) (“DNS-

192.168.7.2”))]

Multilayer Switch 5

(“VLAN 1”) (DOWN) {NOT SET}

(“VLAN 2”) (UP) [(“IP 193.168.1.1/24”))]

(17)

Page 28: Enterprise network

(“VLAN 3”) (UP) [(“IP 193.168.2.1/24”)]

(“VLAN 4”) (UP) [(“IP 193.168.3.1/24”)]

(“Fa.-Eth. 0/1”) (UP) IP [(“10.0.1.65/27 (SM)”))]

(“PC-PT PC 34”) [((“IP-192.168.1.4”) (“SM”) (“DG-192.168.1.1”) (“DNS-

192.168.7.2”))]

(“PC-PT PC 35”) [((“IP-192.168.2.4”) (“SM”) (“DG-192.168.2.1”) (“DNS-

192.168.7.2”))]

(“PC-PT PC 36”) [((“IP-192.168.3.4”) (“SM”) (“DG-192.168.3.1”) (“DNS-

192.168.7.2”))]

(“PC-PT PC 37”) [((“IP-192.168.1.3”) (“SM”) (“DG-192.168.1.1”) (“DNS-

192.168.7.2”))]

(“PC-PT PC 38”) [((“IP-192.168.2.3”) (“SM”) (“DG-192.168.2.1”) (“DNS-

192.168.7.2”))]

(“PC-PT PC 39”) [((“IP-192.168.3.3”) (“SM”) (“DG-192.168.3.1”) (“DNS-

192.168.7.2”))]

(“PC-PT PC 40”) [((“IP-192.168.3.2”) (“SM”) (“DG-192.168.3.1”) (“DNS-

192.168.7.2”))]

(“PC-PT PC 41”) [((“IP-192.168.2.2”) (“SM”) (“DG-192.168.2.1”) (“DNS-

192.168.7.2”))]

(“PC-PT PC 42”) [((“IP-192.168.1.2”) (“SM”) (“DG-192.168.1.1”) (“DNS-

192.168.7.2”))]

(18)

Page 29: Enterprise network

2.4 Basic Configuration Command

2.4.1 Router

Router> Enable

Router# Configure terminal

Router(config) # int fa (0/0, 1/0)

Route (config-if)# ip address (ip address) (subnet mask)

Router(config-if)# no shutdown

Router(config-if)#exit

Router(config)#int serial 2/0

Router(config-if)# ip address (ip address) (subnet mask)

Router(config-if)# no shutdown

Router(config-if)# exit

Router(config)#int serial 3/0

Router(config-if)# ip address (ip address) (subnet mask)

Router(config-if)# no shutdown

Router(config-if)# exit

No Shutdown command is used to change the state of Interface from UP to DOWN or

from DOWN to UP.

(19)

Page 30: Enterprise network

2.4.2 RIP V2 Routing

Router(config)# router rip

Router(config)# version 2

Router(config-router)# (Connected Network1 address)

Router(config-router)# (connected Network2 address)

2.4.3 To make Delhi Server DHCP to provide the IP’s to all

leaving multilayer switch network

FIG 4 DHCP Server Pool

(20)

Page 31: Enterprise network

2.4.4 Access List

Router(config)# access list 1 deny host ip address

Router(config)# interface fastethernet 0/0

Router(config-if)# ip access-group 1 in

Router(config)# access-list 1 permit any

2.4.5 Network Address Translation

2.4.5.1 Static

Router(config)# interface fastethernet 0/0

Router(config-if)# ip nat inside

Router(config)#interface serial 0/0/0

Router(config-if)# ip nat outside

Router(config)# ip nat inside source static public ip address private ip address

2.4.5.2 Dynamic

Router(config)# interface fastethernet 0/0

Router(config-if)# ip nat inside

(21)

Page 32: Enterprise network

Router(config)#interface serial 0/0/0

Router(config-if)# ip nat outside

Router(config)# ip nat pool HPES (Global ip add.) (Avl. Ip add.) Subnetmask

Router(config)# ip nat inside source list 10 HPES

Router(config)# access-list 10 permit private ip add. Subnetmask

Port Address Translation

Router(config)# interface fastethernet 0/0

Router(config-if)# ip nat inside

Router(config)#interface serial 0/0/0

Router(config-if)# ip nat outside

Router(config)# ip nat inside source list 10 interface serial 0/0/0 overload

Router(config)# access-list 10 permit ip add. Subnetmask

(22)

Page 33: Enterprise network

Creating TELNET Password

Pat(Configure)#Line vty 0 4 (password)

Pat(Configure-Line)#Login

Pat(Configure-Line)#Password

Pat(Configure-Line)#Exit

VLAN Database

FIG 5 VLAN Database

(23)

Page 34: Enterprise network

CHAPTER 3_____________________________

Results & Discussion

1. Basic Configuration (VLAN, VTP, Inter VLAN) successful

FIG 6 Basic routing Successful

(24)

Page 35: Enterprise network

FIG 7 VLAN configuration

2. RIPV2 routing successful.

FIG 8 RIPV2 in USA router

3. VLAN finance is not communicating with anyone in the network.

4. Noida Router can ping any pc but none can ping it but can access

www.hpes.com . That means configuring Access List on Noida router successful.

(25)

Page 36: Enterprise network

FIG 9 Pinging Noida Router Unsuccessful

5. Making Delhi Server DHCP to provide the IP’s to all leaving multilayer switch

network is successful.

FIG 10 Making Delhi server DHCP

6. Applying PAT on USA router successful.

7. PC 28 is not communicating with PC 33.

(26)

Page 37: Enterprise network

8. Apply Static NAT on the server of Haryana is successful.

9. All 3 DNS Servers are accessible by all Pc’s in the network.

FIG 11 All DNS are accessible (www.yahoo.com)

(27)

Page 38: Enterprise network

CHAPTER 4_____________________________

Conclusion

To conclude I would like to say that I have successfully completed the basic and soul

purpose of my project which is to create an Enterprise Network which offers End to

End Solution across multiple cities, Countries through which it is connected.

The Basic Fundamentals and aims I think I have successfully achieved and

implemented but as nothing can be perfect so as my project, it needs better

implications in future.

According to me I have completed my project still I am left with lots of improvements

and enhancements of this projected structure. I will try my level best to complete it in

my near future.

(28)

Page 39: Enterprise network

Recommendations

Although I have completed my project successfully but there can be made few

extensions

1. CISCO PACKET TRACER should be updated to next version, as it lags

sometimes.

2. Using different colors in the software makes it easy to understand the difficult

network architecture.

3. Try to make a network which is broader to understand, means there should be

sufficient gap between router switch and multilayer switches of different cities

(29)

Page 40: Enterprise network

CHAPTER 5_____________________________

Implications for Future Research

The Enterprise of the Future will need to be hungry for change and disruptive by

nature, innovative beyond customer imagination, global integrated, and genuine, not

simply generous in their corporate social responsibility efforts. Each of these issues

has clear implications for the workforce, and for the leaders of the Human Resources

function who are working to enhance organizational effectiveness.

Building the Enterprise of the Future: The

Workforce

Dimension

The Enterprise Network of the Future is globally integrated and designed – leveraging

the most appropriate talent and expertise regardless of its geographic location. To

make the most of a global workforce organizations need to develop an HR capability

that can deliver cost-effective services to a global population, provide an

infrastructure that enables individuals to work together regardless of their locations,

and develop leadership competencies that can deliver results and provide guidance to

a myriad of stakeholders. Lastly, corporate social responsibility is playing a larger

role in today’s enterprises. Engaging the workforce in these efforts can have a positive

impact on both employee attraction and retention, yet many companies have not

engaged the workforce around this topic.

.

(30)

Page 41: Enterprise network

CHAPTER 6 ___________________________

Appendix

Working in CISCO Packet Tracer Software is very interesting according to me. We

know our generation is fond of mobiles and their configuration (Android, IOS,

Symbian) Going through the CISCO Packet Tracer software I understood that it is

very similar because everything you are configuring is clearly visible as there is not

any virtual level, you can test your correctness of configuration while you are writing

the program, may be in routers, in switches or in servers(Command Line Interface or

in Global Configuration Mode).It was a nice experience of 6 weeks working in this

highly customizable Network Simulation Software.

(31)

Page 42: Enterprise network

CHAPTER 7 ____________________________

References

1. HP Internship Material.

2. Enterprise Network Convergence-Sridhar Iyer

3. CISCO Packet Tracer (v 6.0.1)

4. Implications for the Workforce-An IBM CEO Study

(32)

Page 43: Enterprise network

CHAPTER 8__________________________

PLAGIARISM CHECK RESULT

Source- Turn it in Software (Amity University)

(33)

Page 44: Enterprise network

THANK YOU

(34)

Page 45: Enterprise network