PROJECT REPORT

Simulation of Partial Mesh Topology using Packet Tracer 5.0

Submitted To: Dr. Ghalib A. Shah

Submitted By: Muhammad Saad Roll No. 2011-MS-EE-61

Contents Chapter No. 1 Introduction of Computer Networks Chapter No. 2 Mesh Networks Chapter No. 3 Virtual LAN Chapter No.4 Introduction to Packet Tracer Chapter No.5 Simulation of Topology in Packet Tracer

Abstract
The project is based on simulation of partial Mesh Topology in Cisco Packet Tracer 5.0.The main task in this project is to create VLAN in a switch which is used to isolate data for different departments in industry. Moreover each switch and Host is configured so that they will communicate with each other. Different routing protocols are available for routing purpose but in this project I use RIP protocol for routers. Moreover the circuit have flexibility and scalability options to enhance optimization.

Chapter No. 1Introduction To Computer Networks

Basic of Networking
A computer network consists of a collection of computers, printers and other equipment that is connected together so that they can communicate with each other. Fig 1 gives an example of a network in a school comprising of a local area network or LAN connecting computers with each other, the internet, and various servers.

Access to: Internet content & learning resources, Scoilnet etc Email communication

File and Print Server CD or Multimedia Servers Printers , Scanners etc

Users computers

Cache, Proxy, Filtering, Firewall Server

Modem or Router

School Local Area Network (LAN)

Other users, computers

Fig 1: Representation of Network in a school. Broadly speaking, there are two types of network configuration, peer-to-peer networks and client/server networks. Peer-to-peer networks are more commonly implemented where less then ten computers are involved and where strict security is not necessary. All computers have the same status, hence the term 'peer', and they communicate with each other on an equal footing. Files, such as word processing or spreadsheet documents, can be shared across the network and all the computers on the network can share devices, such as printers or scanners, which are connected to any one computer.

Peer to Peer Network

Fig 2: Peer to Peer Networking Client/server networks are more suitable for larger networks. A central computer, or 'server', acts as the storage location for files and applications shared on the network. Usually the server is a higher than average performance computer. The server also controls the network access of the other computers which are

referred to as the 'client' computers. Typically, teachers and students in a school will use the client computers for their work and only the network administrator (usually a designated staff member) will have access rights to the server.

File Server

Other equipment

Fig 3: Client - Server Networking

Table 1 provides a summary comparison between Peer-to-Peer and Client/Server Networks.

Peer-to-Peer Networks vs Client/Server Networks

Peer-to-Peer Networks Easy to set up Less expensive to install Can be implemented on a wide range of operating systems More time consuming to maintain the software being used (as computers must be managed individually) Very low levels of security supported or none at all. These can be very cumbersome to set up, depending on the operating system being used Ideal for networks with less than 10 computers Does not require a server Demands a moderate level of skill to administer the network Client/Server Networks More difficult to set up More expensive to install A variety of operating systems can be supported on the client computers, but the server needs to run an operating system that supports networking Less time consuming to maintain the software being used (as most of the maintenance is managed from the server) High levels of security are supported, all of which are controlled from the server. Such measures prevent the deletion of essential system files or the changing of settings No limit to the number of computers that can be supported by the network Requires a server running a server operating system Demands that the network administrator has a high level of IT skills with a good working knowledge of a server operating system

Table 1: Peer-to-Peer Networks vs Client/Server Networks

Components of a Network A computer network comprises the following components: A minimum of at least 2 computers Cables that connect the computers to each other, although wireless communication is becoming more common (see Advice Sheet 20 for more information) A network interface device on each computer (this is called a network interface card or NIC) A Switch used to switch the data from one point to another. Hubs are outdated and are little used for new installations. Network operating system software Structured Cabling The two most popular types of structured network cabling are twisted-pair (also known as 10BaseT) and thin coax (also known as 10Base2). 10BaseT cabling looks like ordinary telephone wire, except that it has 8 wires inside instead of 4. Thin coax looks like the copper coaxial cabling that's often used to connect a Video Recorder to a TV. 10BaseT Cabling When 10BaseT cabling is used, a strand of cabling is inserted between each computer and a hub. If you have 5 computers, you'll need 5 cables. Each cable cannot exceed 325 feet in length. Because the cables from all of the PCs converge at a common point, a 10BaseT network forms a star configuration. Fig 4a shows a Cat5e cable, with a standard connector, known as an RJ-45 connector. Fig 4b shows a standard Cat5e Wall Outlet socket which the cables are connected to. Fig 4c shows a standard Cat5e Patch Panel Wall Outlet socket which is used to terminate the cables from various points in the school bank to a central point. Fig 4d shows a wall mounted cabinet used to house and protect patch panel cables and connectors.

Fig 4a: Cat5e Cable and a close up of RJ-45 connector

Fig 4b: Cat5e Wall Outlets

Fig 4c: Cat5e Patch Panel

Fig4d: Wall Mounted Cabinet

10BaseT cabling is available in different grades or categories. Some grades, or "cats", are required for Fast Ethernet networks, while others are perfectly acceptable for standard 10Mbps networks--and less expensive, too. All new networks use a minimum of standard unshielded twisted-pair (UTP) Category 5e 10BaseT cabling because it offers a performance advantage over lower grades. Network Interface Card (NIC) A NIC (pronounced 'nick') is also known as a network card. It connects the computer to the cabling, which in turn links all of the computers on the network together. Each computer on a network must have a network card. Most modern network cards are 10/100 NICs and can operate at either 10Mbps or 100Mbps. Only NICs supporting a minimum of 100Mbps should be used in new installations schools. Computers with a wireless connection to a network also use a network card (see Advice Sheet 20 for more information on wireless networking).

Fig 5: Network Interface Cards (NICs) Hub and Switch A hub is a device used to connect a PC to the network. The function of a hub is to direct information around the network, facilitating communication between all connected devices. However in new installations switches should be used instead of hubs as they are more effective and provide better performance. A switch, which is often termed a 'smart hub'. Switches and hubs are technologies or boxes to which computers, printers, and other networking devices are connected. Switches are the more recent technology and the accepted way of building today's networks. With switching, each connection gets "dedicated bandwidth" and can operate at full speed. In contrast, a hub shares bandwidth across multiple connections such that activity from one PC or server can slow down the effective speed of other connections on the hub.

Now more affordable than ever, Dual-speed 10/100 autosensing switches are recommended for all school networks. Schools may want to consider upgrading any hub based networks with switches to improve network performance ie speed of data on the network.

Fig 6a: An 8 port Hub

Fig 6b: 2 Examples of 24 port Switches

Wireless Networks The term 'wireless network' refers to two or more computers communicating using standard network rules or protocols, but without the use of cabling to connect the computers together. Instead, the computers use wireless radio signals to send information from one to the other. A wireless local area network (WLAN) consists of two key components: an access point (also called a base station) and a wireless card. Information can be transmitted between these two components as long as they are fairly close together (up to 100 metres indoors or 350 metres outdoors).

Fig 7a: Wireless Access point or Wireless Basestation Suppliers would need to visit the schools and conduct a site survey. This will determine the number of base stations you need and the best place(s) to locate them. A site survey will also enable each supplier to provide you with a detailed quote. It is important to contact a number of different suppliers as prices, equipment and opinions may vary. When the term 'wireless network' is used today, it usually refers to a wireless local area network or WLAN. A WLAN can be installed as the sole network in a school or building. However, it can also be used to extend an existing wired network to areas where wiring would be too difficult or too expensive to implement, or to areas located away from the main network or main building. Wireless networks can be configured to provide the same network functionality as wired networks, ranging from simple peer-to-peer configurations to large-scale networks accommodating hundreds of users.

Fig 7b: Desktop PC Wireless LAN card

Fig 7c: Laptop PC Wireless LAN card

What are the advantages and disadvantages of a Wireless LAN? Wireless LANs have advantages and disadvantages when compared with wired LANs. A wireless LAN will make it simple to add or move workstations, and to install access points to provide connectivity in

areas where it is difficult to lay cable. Temporary or semi-permanent buildings that are in range of an access point can be wirelessly connected to a LAN to give these buildings connectivity. Where computer labs are used in schools, the computers (laptops) could be put on a mobile cart and wheeled from classroom to classroom, providing they are in range of access points. Wired network points would be needed for each of the access points. A WLAN has some specific advantages: It is easier to add or move workstations It is easier to provide connectivity in areas where it is difficult to lay cable Installation can be fast and easy and can eliminate the need to pull cable through walls and ceilings Access to the network can be from anywhere in the school within range of an access point Portable or semi-permanent buildings can be connected using a wireless LAN Where laptops are used, the computer suite can be moved from classroom to classroom on mobile carts While the initial investment required for wireless LAN hardware can be similar to the cost of wired LAN hardware, installation expenses can be significantly lower Where a school is located on more than one site (such as on two sides of a road), it is possible with directional antennae, to avoid digging trenches under roads to connect the sites In historic buildings where traditional cabling would compromise the faade, a wireless LAN can avoid drilling holes in walls Long-term cost benefits can be found in dynamic environments requiring frequent moves and changes They allows the possibility of individual pupil allocation of wireless devices that move around the school with the pupil. WLANs also have some disadvantages: As the number of computers using the network increases, the data transfer rate to each computer will decrease accordingly As standards change, it may be necessary to replace wireless cards and/or access points Lower wireless bandwidth means some applications such as video streaming will be more effective on a wired LAN Security is more difficult to guarantee, and requires configuration Devices will only operate at a limited distance from an access point, with the distance determined by the standard used and buildings and other obstacles between the access point and the user A wired LAN is most likely to be required to provide a backbone to the wireless LAN; a wireless LAN should be a supplement to a wired LAN and not a complete solution Long-term cost benefits are harder to achieve in static environments that require few moves and changes It is easier to make a wired network future proof for high data transfer.

Wireless Network Components There are certain parallels between the equipment used to build a WLAN and that used in a traditional wired LAN. Both networks require network interface cards or network adapter cards. A wireless LAN PC card, which contains an in-built antenna, is used to connect notebook computers to a wireless network. Usually, this is inserted into the relevant slot in the side of the notebook, but some may be internal to the notebook. Desktop computers can also connect to a wireless network if a wireless network card is inserted into one of its internal PCI slots. In a wireless network, an 'access point' has a similar function to the hub in wired networks. It broadcasts and receives signals to and from the surrounding computers via their adapter card. It is also the point where a wireless network can be connected into an existing wired network.

The most obvious difference between wireless and wired networks, however, is that the latter uses some form of cable to connect computers together. A wireless network does not need cable to form a physical connection between computers. Wireless Network Configurations Wireless networks can be configured in an ad hoc/peer-to-peer arrangement or as a local area network. Ad Hoc/Peer-to-Peer Configuration This is the most basic wireless network configuration. It relies on the wireless network adapters installed in the computers that are communicating with each other. A computer within range of the transmitting computer can connect to it. However, if a number of computers are networked in this way, they must remain within range of each other. Even though this configuration has no real administration overhead, it should only be a consideration for very small installations. Benefits and Educational Uses The installation of cables is time consuming and expensive. The advantages of not doing so are apparent: the amount of work required and the time taken to complete it are significantly reduced the network is accessible in places where wiring would have been difficult or impossible with no cables linking computers together, cable-related faults and network downtime are minimised Where a wireless network is in place, teachers or students can have continuous access to the network, even as they move with their equipment from class to class. The space over which a wireless network operates is not planar but spherical. Therefore, in a multi-level site, network access is available in rooms above or below the access point, without the need for additional infrastructure. In a location within a school where network access is required occasionally, desktop computers fitted with wireless network cards can be placed on trolleys and moved from location to location. They can also be located in areas where group work is taking place. As they are connected to the network, documents and files can be shared, and access to the Internet is available, enhancing group project work. As the range of the wireless network extends outside the building, students and teachers can use wireless devices to gather and record data outside, e.g., as part of a science experiment or individual performance data as part of a PE class. Technical and Purchasing Considerations Network interface cards for wireless networks are more expensive than their wired counterparts. The cost of the access points has also to be considered. Wireless networks work at up top 54Mbps, whereas wired networks normally work at 100Mbps (Fast Ethernet). This data transmission rate is dependant on the number of users, the distance from the access point and the fabric of the building (metal structures in walls may have an impact). A wireless network will be noticeably slow when a group of users are transferring large files. This should be considered if multimedia applications are to be delivered over the network to a significant number of users. As the range of the network may extend beyond the walls of the building, it can be accessed from outside. Consideration should be given to what security features the equipment provides to ensure that only valid users have access to the network and that data is protected.

1.1. Advantages of Networking schools

Speed. Networks provide a very rapid method for sharing and transferring files. Without a network, files are shared by copying them to floppy disks, then carrying or sending the disks from one computer to another. This method of transferring files in this manner is very time-consuming. Cost. The network version of most software programs are available at considerable savings when compared to buying individually licensed copies. Besides monetary savings, sharing a program on a network allows for easier

upgrading of the program. The changes have to be done only once, on the file server, instead of on all the individual workstations. Centralized Software Management. One of the greatest benefits of installing a network at a school is the fact that all of the software can be loaded on one computer (the file server). This eliminates that need to spend time and energy installing updates and tracking files on independent computers throughout the building. Resource Sharing. Sharing resources is another area in which a network exceeds stand-alone computers. Most schools cannot afford enough laser printers, fax machines, modems, scanners, and CD-ROM players for each computer. However, if these or similar peripherals are added to a network, they can be shared by many users. Flexible Access. School networks allow students to access their files from computers throughout the school. Students can begin an assignment in their classroom, save part of it on a public access area of the network, then go to the media center after school to finish their work. Students can also work cooperatively through the network. Security. Files and programs on a network can be designated as "copy inhibit," so that you do not have to worry about illegal copying of programs. Also, passwords can be established for specific directories to restrict access to authorized users. Main challenges of installing a School Network Costs Although a network will generally save money over time, the initial costs can be substantial, and the installation may require the services of a technician. Requires Administrative Time. Proper maintenance of a network requires considerable time and expertise. Many schools have installed a network, only to find that they did not budget for the necessary administrative support. File Server May Fail. Although a file server is no more susceptible to failure than any other computer, when the files server "goes down," the entire network may come to a halt. When this happens, the entire school may lose access to necessary programs and files.

1.2.

Networking Models: Towards a Networked School

This model shows a diagram of a networked school indicating the various types of networking models used. These include computer rooms, networked classrooms, networked specialist rooms for specific subjects. Mobile solutions are shown in the Resource room, the General Purpose room and Building # 2. Note: To improve readability only network points are shown, rather than cabling itself. Refer to Fig 8.

Main School Building

School Admin Office Principals Office Staff Room

Technology Room Post Primary

Science Labs Post Primary

Resource Room

Standard Classroom

General Purpose Room

Standar d Classro Standard oms Classroom

Standard Classroom ICT Server & Equipment Room

Standard Classroom Store Room

Standard Classroom

Standard Classroom

Standard Classroom

Specialist Room Post Primary

Standard Classroom

Computer room with 15-30 computers Wireless link to Building 2

Specialist Room Post Primary

Building 2 Temporary Pre-Fab - Wireless Network

Building 3

Fig 8: Representation of a Whole School Network Model

Junior Infants # of computers

Senior Infants # of computers

1st Class # of computers

2nd Class # of computers

Resource room # of computers

Principal/Office Staffroom # of computers

3rd Class # of computers File & Print Server Access to: Internet content & learning resources, Scoilnet etc Email communication Cache, Proxy, Filtering, Firewall Server

4th Class # of computers

School Local Area Network (LAN)

Modem or Router

5th Class # of computers

6th Class # of computers

Fig 9: Typical Network Model for a Primary or Special school.

Figure 9 shows a model for a Primary or Special school. This includes connectivity to all classrooms back to a central network. The network connects to a File and Print Server. Internet access is handled via a modem or router, while internet Filtering , Proxy and Web Caching are all handled via a dedicated server.

standard classroom # of computers

computer room # of computers

Staff room # of computers

Principal/Office # of computers

Library # of computers

science lab # of computers File & Print Server Access to: Internet content & learning resources, Scoilnet etc Email communication

technology lab # of computers

Cache/Proxy, Filtering/Firewall Server

School Local Area Network (LAN)

resource room # of computers

Modem or Router

specialist room # of computers

Fig 10: Typical Network Model for a Post Primary school. Figure 10 shows a model for a Post Primary school. This includes connectivity to all classrooms back to a central network. The network connects to a File and Print Server. Internet access is handled via a modem or router, while internet Filtering , Proxy and Web Caching are all handled via a dedicated server.

File & Print Server

Printer

Multimedia or CD Server Access to: Internet content & learning resources, Scoilnet etc Email communication Cache/Proxy, Filtering/Firewall Server

Scanner

Main Servers & Internet Access

Modem or Router

Network

Fig 11: Server Functionality Model Server Functionality

The network connects to a File and Print Server, Fig 11. The File server stores common files, The Print Server manages the different requests for printing. A Multimedia or CD server is used to store and distribute Multimedia - Sound, Video, Text , applications etc . Internet access is handled via a modem or router, while internet Filtering , Proxy and Web Caching are all handled via a dedicated server.

Example network configurations:

Models for Networking First lets review some simple models where no networking exits and computers are used in standalone or ad-hoc mode. The following represent some simple models representing classrooms. Model 1a: One computer in a classroom with its own private printer. It is recommended that schools with computers in this situation would network the classrooms in question as shown. Networking will more effectively make use of commonly shared resources such as file servers and school printers, internet , email etc. When a mobile PC or PC with projector is require in a room the network points are already present. In this scenario, there could be a single LAN-connected point for the teacher and an additional LAN connection to allow for a portable switch. Refer to diagram 12a Model 1a

Fig 12a: From single PC to networked LAN Points

Model 1b: This scenario is similar to Model 1a, but where other equipment such as printers, scanners are used in ad-hoc and inefficient configuration. It is recommended that schools with computers in this situation would network the classrooms in question . Networking will more effectively make use of commonly shared resources such as scanners, printers, internet , email etc. In this scenario there may be a single LAN-connected point for the teacher and a limited number of LAN connection points throughout the room to allow students access to the school LAN. The connection points may be situated as required around the room depending upon class learning requirements and the availability of existing power outlets. Refer to diagram 12b Model 1b:

Fig 12b: Networking other commonly used equipment Networked Computer Room Model 1c: A non networked computer room or resource area with an ad-hoc and inefficient use of printers, scanners etc. Networking computer rooms is essential so that all PCs can access printers, the internet, email etc. This scenario represents a school computing room which can be timetabled for classes, and with each computer networked to the LAN. There may be a single LAN-connected presentation point for the teacher and LAN-connected computers throughout the classroom. Traditionally, ICT in Irish secondary schools has been concentrated in dedicated computer rooms. Primary schools have more varied deployment. From an administrative point of view, this setup is attractive. An entire class can be timetabled, avoiding problems of extra teachers for split classes. Refer to diagram 12c Model 1c:

Fig 12c: Networked computer lab.

Media Bays (Ref Fig 13a) Media bays, or data suites are clusters of perhaps four desktop computers, a scanner and a printer. Though self-sufficient in terms of peripherals, they would be connected to the main school network and have Internet access. This is one reason why they would be best sited in public areas around the school. These suites would be used by students in small groups or individually and could accommodate taskoriented activities and self-directed learning. Advantages are easy access to staff and students alike, Utilise areas of school without losing classrooms Public supervision Disadvantages are Open access means security issues must be addressed .

Fig 13a: Movable or mobile Media Bays

Laptop and data-projector (Ref Fig 13b) A combination of laptop and data-projector is a highly effective teaching model where a teacher wants to provide the whole class with visual or multimedia content . It can be used in conjunction with an existing LAN point in the room for best effect.

Fig 13b: Movable or mobile Laptop PC with Digital Projector

Wireless LAN (Ref Fig 13c) This scenario has the capability to connect multiple computers to the school LAN without providing direct LAN connections. No LAN cabling is required for the classroom; instead all computers are radio linked to the LAN. Wireless LAN technology is relatively new and generally more expensive and more limited than cabled LANs. There is the potential, however, to save on extensive cabling work with this option. Wireless connections allow a region to be connected to a network by radiowaves, which link a wireless card in the computer to a wireless access point. One should remember that the access point itself must be connected by cable to the main network. Advantages

Flexibility of machines - usually laptops - linked even if students break into small workgroups in different parts of room. Wireless networking means that large common areas such as canteens or libraries can be easily connected to the network. Less unplugging of cables into sockets reduces wear and tear

Disadvantages Wireless networking may prove much more expensive if wiring large numbers of machines close together. Wireless hubs data rates (typically 11Mbps) are considerably less at present than their cable equivalent. Thus is unsuitable for high data volumes such as multimedia access by large numbers of machines. Manufacturers stated ranges of 100 - 300 metres is wildly optimistic. Ranges of less than 18 metres are not uncommon, Data rates drop off as distance increases.

While it is unlikely that wireless will replace data cables in the near future they do provide a flexibility that can be harnessed creatively.

Fig 13c: Wireless LAN (WLAN)

Chapter No. 2 Mesh Networks

Mesh networking (topology) is a type of networking where each node must not only capture and disseminate its own data, but also serve as a relay for other nodes, that is, it must collaborate to propagate the data in the network. A mesh network can be designed using a flooding technique or a routing technique. When using a routing technique, the message is propagated along a path, by hopping from node to node until the destination is reached. To ensure all its paths' availability, a routing network must allow for continuous connections and reconfiguration around broken or blocked paths, using self-healing algorithms. A mesh network whose nodes are all connected to each other is a fully connected network. Mesh networks can be seen as one type of ad hoc network. Mobile ad hoc networks (MANET) and mesh networks are therefore closely related, but MANET also have to deal with the problems introduced by the mobility of the nodes. The self-healing capability enables a routing based network to operate when one node breaks down or a connection goes bad. As a result, the network is typically quite reliable, as there is often more than one path between a source and a destination in the network. Although mostly used in wireless situations, this concept is also applicable to wired networks and software interaction.

Fig Full Mesh Network Advantages

Point-to-point line configuration makes identification and isolation of faults easy. Messages travel through a dedicated line, directly to the intended recipient; privacy and security are thus enhanced.

Should a fault occur in a given link, only those communications between that specific pair of devices sharing the link will be affected. Dedicated links ensure that each connection carries its own data load, thereby preventing the sort of traffic problems that may arise in shared-link architectures.

Disadvantage The more extensive the network, in terms of scope or of physical area, the greater the investment necessary to build it will be, due, among other considerations, to the amount of cabling and the number of hardware ports it will require. For this reason, such networks are uncommon. Partial Mesh Networks Mesh topologies involve the concept of routes. Unlike each of the previous topologies, messages sent on a mesh network can take any of several possible paths from source to destination. (Recall that even in a ring, although two cable paths exist, messages can only travel in one direction.) Some WANs, most notably the Internet, employ mesh routing. A mesh network in which every device connects to every other is called a full mesh. As shown in the illustration below, partial mesh networks also exist in which some devices connect only indirectly to others.

Fig Partial Mesh

Chapter No. 3 Virtual LAN

INTRODUCTION Virtual LANs (VLANs) have recently developed into an integral feature of switched LAN solutions from every major LAN equipment vendor. Although end-user enthusiasm for VLAN implementation has yet to take off, most organizations have begun to look for vendors that have a well-articulated VLAN strategy, as well as VLAN functionality built into products today. One of the reasons for the attention placed on VLAN functionality now is the rapid deployment of LAN switching that began in 1994/1995. The shift toward LAN switching as a replacement for local/departmental routers-- and now even shared media devices (hubs)-- will only accelerate in the future. With the rapid decrease in Ethernet and Token Ring switch prices on a per-port basis, many more ambitious organizations are moving quickly toward networks featuring private port (single user/port) LAN switching architectures. Such a desktop switching architecture is ideally suited to VLAN implementation. To understand why private port LAN switching is so well suited to VLAN implementation, it is useful to review the evolution of segmentation and broadcast containment in the network over the past several years. In the early 1990s, organizations began to replace two-port bridges with multiport, collapsed backbone routers in order to segment their networks at layer 3 and thus also contain broadcast traffic. In a network using only routers for segmentation, segments and broadcast domains correspond on a one-to-one basis. Each segment typically contained between 30 and 100 users. With the introduction of switching, organizations were able to divide the network into smaller, layer 2defined segments, enabling increased bandwidth per segment. Routers could now focus on providing broadcast containment, and broadcast domains could now span multiple switched segments, easily supporting 500 or more users per broadcast domain. However, the continued deployment of switches, dividing the network into more and more segments (with fewer and fewer users per segment) does not reduce the need for broadcast containment. Using routers, broadcast domains typically remain in the 100 to 500 user range. VLANs represent an alternative solution to routers for broadcast containment, since VLANs allow switches to also contain broadcast traffic. With the implementation of switches in conjunction with VLANs, each network segment can contain as few as one user (approaching private port LAN switching), while broadcast domains can be as large as 1,000 users or perhaps even more. In addition, if implemented properly, VLANs can track workstation movements to new locations without requiring manual reconfiguration of IP addresses. Why haven't more organizations deployed VLANs? For the vast majority of end-user organizations, switches have yet to be implemented on a large enough scale to necessitate VLANs. That situation will

soon change. There are, however, other reasons for the lukewarm reception that VLANs have received from network users up to now:

VLANs have been, and are still, proprietary, single-vendor solutions. As the networking industry has shown, proprietary solutions are anathema to the multivendor/open systems policies that have developed in the migration to local area networks and the client server model. Despite the frequently quoted numbers illuminating the hidden costs of networking, such as administration and moves/adds/ changes, customers realize that VLANs have their own administrative costs, both straight-forward and hidden. Although many analysts have suggested that VLANs enhance the ability to deploy centralized servers, customers may look at enterprise-wide VLAN implementation and see difficulties in enabling full, high-performance access to centralized servers.

This paper discusses these and other issues in greater detail, and attempts to determine the strategic implications that VLANs, present and future, pose for enterprise networks. DEFINING VLANS What is a VLAN? With the multitude of vendor-specific VLAN solutions and implementation strategies, defining precisely what VLANs are has become a contentious issue. Nevertheless, most people would agree that a VLAN can be roughly equated to a broadcast domain. More specifically, VLANs can be seen as analogous to a group of end-stations, perhaps on multiple physical LAN segments, that are not constrained by their physical location and can communicate as if they were on a common LAN. However, at this point, issues such as the extent to which end-stations are not constrained by physical location, the way VLAN membership is defined, the relationship between VLANs and routing, and the relationship between VLANs and ATM have been left up to each vendor. To a certain extent these are tactical issues, but how they are resolved has important strategic implications. Because there are several ways in which VLAN membership can be defined, this paper divides VLAN solutions into four general types: port grouping, MAC-layer grouping, network-layer grouping, and IP multicast grouping. We will discuss the issue of manual vs. automatic VLAN configuration, and describe techniques by which VLANs may be extended across multiple switches in the network. Finally, the paper takes a look at the present state of VLAN standards. MEMBERSHIP BY PORT GROUP Many initial VLAN implementations defined VLAN membership by groups of switch ports (for example, ports 1, 2, 3, 7, and 8 on a switch make up VLAN A, while ports 4, 5, and 6 make up VLAN B). Furthermore, in most initial implementations, VLANs could only be supported on a single switch. Second-generation implementations support VLANs that span multiple switches (for example, ports 1 and 2 of switch #1 and ports 4, 5, 6, and 7 of switch #2 make up VLAN A; while ports 3, 4, 5, 6, 7, and 8 of switch #1 combined with ports 1, 2, 3, and 8 of switch #2 make up VLAN B). This scenario is depicted in Figure 1. Port grouping is still the most common method of defining VLAN membership, and configuration is fairly straightforward. Defining VLANs purely by port group does not allow multiple VLANs to include the same physical segment (or switch port). However, the primary limitation of defining VLANs by port is that the network manager must reconfigure VLAN membership when a user moves from one port to another.

Figure 1. VLANs Defined by Port Group

MEMBERSHIP BY MAC Address VLAN membership based on MAC-layer address has a different set of advantages and disadvantages. Since MAC-layer addresses are hard-wired into the workstation's network interface card (NIC), VLANs based on MAC addresses enable network managers to move a workstation to a different physical location on the network and have that work-station automatically retain its VLAN membership. In this way, a VLAN defined by MAC address can be thought of as a user-based VLAN.

One of the drawbacks of MAC address-based VLAN solutions is the requirement that all users must initially be configured to be in at least one VLAN. After that initial manual configuration, automatic tracking of users is possible, depending on the specific vendor solution. However, the disadvantage of having to initially configure VLANs becomes clear in very large networks where thousands of users must each be explicitly assigned to a particular VLAN. Some vendors have mitigated the onerous task of initially configuring MAC-based VLANs by using tools that create VLANs based on the current state of the network--that is, a MAC address-based VLAN is created for each subnet. MAC address-based VLANs that are implemented in shared media environments will run into serious performance degradation as members of different VLANs coexist on a single switch port. In addition, the primary method of communicating VLAN membership information between switches in a MAC addressdefined VLAN also runs into performance degradation with larger-scale implementations. This is explained in "Communicating VLAN Membership Information," later in this paper. Another, but minor, drawback to VLANs based only on MAC-layer addresses emerges in environments that use significant numbers of notebook PCs with some docking stations. The problem is that the docking station and integrated network adapter (with its hardwired MAC-layer address) usually remain on the desktop, while the notebook travels with the user. When the user moves to a new desk and docking station, the MAC-layer address changes, making VLAN membership impossible to track. In such an environment, VLAN membership must be updated constantly as users move around and use different docking stations. While this problem may not be particularly common, it does illustrate some of the limitations of MAC address-based VLANs. LAYER 3-BASED VLANS VLANs based on layer 3 information take into account protocol type (if multiple protocols are supported) or network-layer address (for example, subnet address for TCP/IP networks) in determining VLAN

membership. Although these VLANs are based on layer 3 information, this does not constitute a "routing" function and should not be confused with network-layer routing. Even though a switch inspects a packet's IP address to determine VLAN membership, no route calculation is undertaken, RIP or OSPF protocols are not employed, and frames traversing the switch are usually bridged according to implementation of the Spanning Tree Algorithm. Therefore, from the point of view of a switch employing layer 3-based VLANs, connectivity within any given VLAN is still seen as a flat, bridged topology. Having made the distinction between VLANs based on layer 3 information and routing, it should be noted that some vendors are incorporating varying amounts of layer 3 intelligence into their switches, enabling functions normally associated with routing. Furthermore, "layer 3 aware" or "multi-layer" switches often have the packet-forwarding function of routing built into ASIC chip sets, greatly improving performance over CPU-based routers. Nevertheless, a key point remains: no matter where it is located in a VLAN solution, routing is necessary to provide connectivity between distinct VLANs. There are several advantages to defining VLANs at layer 3. First, it enables partitioning by protocol type. This may be an attractive option for network managers who are dedicated to a service- or application-based VLAN strategy. Second, users can physically move their workstations without having to reconfigure each workstation's network address--a benefit primarily for TCP/IP users. Third, defining VLANs at layer 3 can eliminate the need for frame tagging in order to communicate VLAN membership between switches, reducing transport overhead. One of the disadvantages of defining VLANs at layer 3 (vs. MAC- or port-based VLANs) can be performance. Inspecting layer 3 addresses in packets is more time consuming than looking at MAC addresses in frames. For this reason, switches that use layer 3 information for VLAN definition are generally slower than those that use layer 2 information. It should be noted that this performance difference is true for most, but not all, vendor implementations. VLANs defined at layer 3 are particularly effective in dealing with TCP/IP, but less effective with protocols such as IPX(TM) , DECnet , or AppleTalk , which do not involve manual configuration at the desktop. Furthermore, layer 3-defined VLANs have particular difficulty in dealing with "unroutable" protocols such as NetBIOS. End-stations running unroutable protocols cannot be differentiated and thus cannot be defined as part of a network-layer VLAN. IP MULTICAST GROUPS AS VLANS IP multicast groups represent a somewhat different approach to VLAN definition, although the fundamental concept of VLANs as broadcast domains still applies. When an IP packet is sent via multicast, it is sent to an address that is a proxy for an explicitly defined group of IP addresses that is established dynamically. Each workstation is given the opportunity to join a particular IP multicast group by responding affirmatively to a broadcast notification, which signals that group's existence. All workstations that join an IP multicast group can be seen as members of the same virtual LAN. However, they are only members of a particular multicast group for a certain period of time. Therefore, the dynamic nature of VLANs defined by IP multicast groups enables a very high degree of flexibility and application sensitivity. In addition, VLANs defined by IP multicast groups would inherently be able to span routers and thus WAN connections. COMBINATION VLAN DEFINITIONS Due to the trade-offs between various types of VLANs, many vendors are planning to include multiple methods of VLAN definition. Such a flexible definition of VLAN membership enables network managers to configure their VLANs to best suit their particular network environment. For example, by using a combination of methods, an organization that utilizes both IP and NetBIOS protocols could define IP VLANs corresponding to preexisting IP subnets (convenient for smooth migration), and then define VLANs for NetBIOS end-stations by dividing them by groups of MAC-layer addresses.

AUTOMATION OF VLAN CONFIGURATION Another issue central to VLAN deployment is the degree to which VLAN configuration is automated. To a certain extent, this degree of automation is correlated to how VLANs are defined; but in the end, the specific vendor solution will determine this level of automation. There are three primary levels of automation in VLAN configuration: Manual. With purely manual VLAN configuration, both the initial setup and all subsequent moves and changes are controlled by the network administrator. Of course, purely manual configuration enables a high degree of control. However, in larger enterprise networks, manual configuration is often not practical. Furthermore, it defeats one of the primary benefits of VLANs: elimination of the time it takes to administer moves and changes--although moving users manually with VLANs may actually be easier than moving users across router subnets, depending on the specific vendor's VLAN management interface. Semiautomated. Semiautomated configuration refers to the option to automate either initial configuration, subsequent reconfigurations (moves/changes), or both. Initial configuration automation is normally accomplished with a set of tools that map VLANs to existing subnets or other criteria. Semi-automated configuration could also refer to situations where VLANs are initially configured manually, with all subsequent moves being tracked automatically. Combining both initial and subsequent configuration automation would still imply semi-automated configuration, because the network administrator always has the option of manual configuration. Fully Automatic. A system that fully automates VLAN configuration implies that workstations automatically and dynamically join VLANs depending on application, user ID, or other criteria or policies that are preset by the administrator. This type of VLAN configuration is discussed in greater detail toward the end of this paper.

COMMUNICATING VLAN MEMBERSHIP INFORMATION Switches must have a way of understanding VLAN membership (that is, which stations belong to which VLAN) when network traffic arrives from other switches; otherwise, VLANs would be limited to a single switch. In general, layer 2-based VLANs (defined by port or MAC address) must communicate VLAN membership explicitly, while VLAN membership in IP-based VLANs is implicitly communicated by the IP address. Depending on the particular vendor's solution, communication of VLAN membership may also be implicit in the case of layer 3-based VLANs in a multiprotocol environment. To date, outside of implementing an ATM backbone, three methods have been implemented for interswitch communication of VLAN information across a backbone: table maintenance via signaling, frame tagging, and time-division multiplexing (TDM). Table Maintenance via Signaling. This method operates as follows: When an end-station broadcasts its first frame, the switch resolves the end-station's MAC address or attached port with its VLAN membership in cached address tables. This information is then broadcast continuously to all other switches. As VLAN membership changes, these address tables are manually updated by a system administrator at a management console. As the network expands and switches are added, the constant signaling necessary to update the cached address tables of each switch can cause substantial congestion of the backbone. For this reason, this method does not scale particularly well. Frame Tagging. In the frame-tagging approach, a header is typically inserted into each frame on interswitch trunks to uniquely identify which VLAN a particular MAC-layer frame belongs to. Vendors differ in the way they solve the problem of occasionally exceeding the maximum length of MAC-layer frames as these headers are inserted. These headers also add overhead to network traffic. TDM. The third, and least utilized method, is time-division multiplexing. TDM works the same way on the interswitch backbone to support VLANs as it does in the WAN environment to support multiple traffic types-- here, channels are reserved for each VLAN. This approach cuts out some of the overhead problems inherent in signaling and frame tagging, but it also wastes bandwidth, because a time slot dedicated to one VLAN cannot be used by another VLAN, even if that channel is not carrying traffic.

Deploying an ATM backbone also enables the communication of VLAN information between switches, but it introduces a new set of issues with regard to LAN Emulation (LANE). ATM is discussed in detail in a separate section of this paper. However, for the time being, it should be remembered that with port groupdefined VLANs, the LANE standard provides for a nonproprietary method of communicating VLAN membership across a backbone. STANDARDS AND THE PROPRIETARY NATURE OF VLANS Given the variety of types of VLAN definitions and the variety of ways that switches can communicate VLAN information, it should not be surprising that each vendor has developed its own unique and proprietary VLAN solutions and products. The fact that switches from one vendor will not interoperate entirely with VLANs from other vendors may force customers to buy from a single vendor for VLAN deployment across the enterprise. An exception to this rule arises when VLANs are implemented in conjunction with an ATM backbone and LANE. This is discussed further in "VLANs and ATM," later in this paper. The fact that single-vendor VLAN solutions in the LAN backbone will be the rule for the foreseeable future contributes to the recommendation that VLANs should not be deployed indiscriminately throughout the enterprise. It also implies that purchase decisions should be more highly centralized or coordinated than they may traditionally have been. Thus, from both a procurement and a technological perspective, VLANs should be considered as elements of a strategic approach. The following two VLAN standards have been proposed: 802.10 "VLAN Standard." In 1995, Cisco Systems proposed the use of IEEE 802.10, which was originally established to address LAN security for VLANs. Cisco attempted to take the optional 802.10 frame header format and "reuse" it to convey VLAN frame tagging instead of security information. Although this can be made to work technically, most members of the 802 committee have been strongly opposed to using one standard for two discrete purposes. In addition, this solution would be based on variable-length fields, which make implementation of ASIC-based frame processing more difficult and thus slower and/or more expensive. 802.1 Internetworking Subcommittee. In March, 1996, the IEEE 802.1 Internet-working Subcommittee completed the initial phase of investigation for developing a VLAN standard, and passed resolutions concerning three issues: the architectural approach to VLANs; a standardized format for frame tagging to communicate VLAN membership information across multiple, multivendor devices; and the future direction of VLAN standardization. The standardized format for frame tagging, in particular, known as 802.1Q, represents a major milestone in enabling VLANs to be implemented using equipment from several vendors, and will be key in encouraging more rapid deployment of VLANs. Furthermore, establishment of a frame format specification will allow vendors to immediately begin incorporating this standard into their switches. All major switch vendors, including 3Com, Alantec/ FORE, Bay Networks, Cisco, and IBM voted in favor of this proposal. The dynamic nature of VLANs defined by IP multicast groups enables a very high degree of flexibility and application sensitivity.

However, due to the lag time necessary for some vendors to incorporate the frame format specification and the desire on the part of most organizations to have a unified VLAN management platform, VLANs will, in practice, continue to retain characteristics of a single-vendor solution for some time. This has significant ramifications for deployment and procurement of VLANs. Department-level procurement for LAN equipment, particularly in the backbone, is not practical for organizations deploying VLANs. Purchasing decisions and standardization on a particular vendor's solution throughout the enterprise will become the norm, and price-based product competition will decrease. The structure of the industry itself may also shift in favor of the larger networking vendors that can furnish a complete solution across a wide range of components.

VLAN IMPLEMENTATION BENEFITS Why are vendors paying so much attention to VLAN implementation? Will VLANs solve all of the network manager's problems with respect to moves, changes, broadcasts, and performance?

REDUCING THE COST OF MOVES AND CHANGES The reason most often given for VLAN implementation is a reduction in the cost of handling user moves and changes. Since these costs are quite substantial, this argument for VLAN implementation can be compelling. Many vendors are promising that VLAN implementation will result in a vastly increased ability to manage dynamic networks and realize substantial cost savings. This value proposition is most valid for IP networks. Normally, when a user moves to a different subnet, IP addresses must be manually updated in the workstation. This updating process can consume a substantial amount of time that could be used for more productive endeavors such as developing new network services. VLANs eliminate that hassle, because VLAN membership is not tied to a workstation's location in the network, allowing moved work-stations to retain their original IP addresses and subnet membership. It is certainly true that the phenomenon of increasingly dynamic networks absorbs a substantial portion of the budgets of most IS departments. However, not just any VLAN implementation will reduce these costs. VLANs themselves add another layer of virtual connectivity that must be managed in conjunction with physical connectivity. This is not to say that VLANs cannot reduce the costs of moves, and changes--if properly implemented, they will. However, organizations must be careful not to simply throw VLANs at the network, and they must make sure that the solution does not generate more network administration than it saves. VIRTUAL WORKGROUPS One of the more ambitious VLAN objectives is the establishment of the virtual workgroup model. The concept is that, with full VLAN implementation across the campus network environment, members of the same department or section can all appear to share the same "LAN," with most of the network traffic staying within the same VLAN broadcast domain. Someone moving to a new physical location but remaining in the same department could move without having workstations reconfigured. Conversely, a user would not have to change his or her physical location when changing departments--the network manager would simply change the user's VLAN membership. This functionality promises to enable a more dynamic organizational environment, enhancing the recent trend toward cross-functional teams. The logic of the virtual work-group model goes like this: teams formed on a temporary, project basis could be virtually connected to the same LAN without requiring people to physically move in order to minimize traffic across a collapsed backbone. Additionally, these workgroups would be dynamic: VLANs corresponding to these cross-functional project teams could be set up for the duration of the project and torn down when the project was completed, all the while allowing users to remain in the same physical locations. Although this scenario seems attractive, the reality is that VLANs alone cannot pave the way for full utilization of the virtual workgroup model. There are several managerial and architectural issues that, at this point, pose problems for the virtual workgroup model: Managing Virtual Workgroups. From a network management perspective, the transitory nature of these virtual workgroups may grow to the point where updating VLAN membership becomes as onerous as updating routing tables to keep up with adds, moves, and changes today (although it may save on the time and effort involved in physically moving the user's workstation). Moreover, there are still cultural hurdles to overcome in the virtual workgroup model: people usually move to be physically close to those with whom they work, rather than to reduce traffic across a collapsed backbone. Maintaining the 80/20 Rule. Virtual LAN support for virtual workgroups is often tied to support of the "80/20 rule," that is, 80 percent of the traffic is "local" to the workgroup while 20 percent is remote or outside of the workgroup. In theory, by properly configuring VLANs to match workgroups, only the 20 percent of the traffic that is nonlocal will need to pass through a router and out of the workgroup, improving performance for the 80 percent of the traffic that is within the workgroup. However, many believe that the applicability of the 80/20 rule is waning due to the deployment of servers and/or

network applications such as e-mail and Lotus Notes that users throughout the enterprise access on an equal basis. Access to Local Network Resources. The virtual workgroup concept may run into the simple problem that users must sometimes be physically close to certain resources such as printers. For example, a user is in the Accounting VLAN, but is physically located in an area populated by members of the Sales VLAN. The local network printer is also in the Sales VLAN. Every time this Accounting VLAN member prints to the local printer, his print file must traverse a router connecting the two VLANs. This problem can be avoided by making that printer a member of both VLANs. This clearly favors VLAN solutions that enable overlapping VLANs, discussed later. If overlapping VLANs are not possible, this scenario would require that routing functionality be built into the backbone switch. Then, the example print file would be routed by the switch rather than having to go through an external router. Centralized Server Farms. Server farms refer to the placement of departmental servers in a data center, where they can be provided with consolidated backup, uninterrupted power supply, and a proper operating environment. The trend toward server farm architecture has accelerated recently and is expected to continue in order to ease administrative costs. Centralized server farms raise problems for the virtual workgroup model when vendor solutions do not provide the ability for a server to belong to more than one VLAN simultaneously. If overlapping VLANs are not possible, traffic between a centralized server and clients not belonging to that server's VLAN must traverse a router. However, if the switch incorporates built-in routing and is able to route inter-VLAN packets at wire speed, there is no performance advantage for overlapping VLANs over routing between VLANs to allow universal access to a centralized server. Remember, only inter-VLAN packets would need to be routed-- not all packets. Several vendors support integrated routing as an alternative to over-lapping VLANs.

While workgroup VLANs may be extended to centralized server farms (for example, including a particular file server in a particular workgroup's VLAN), this is not always possible. In some networks, the MIS people who control the servers may want to place routers between the server farms and the rest of the network in order to create a separate administrative domain or to enhance network security via router access control lists. Depending on the vendor implementation, most switching products will not support VLANs that extend across routers (the exception to this would be "VLANs" that equate to IP multicast groups). It should be kept in mind that cordoning off servers with external routers conflicts with one of the reasons for utilizing switches and VLANs in the first place--to avoid the delay introduced by routers. REDUCTION OF ROUTING FOR BROADCAST CONTAINMENT Even the most router-centric networking vendors have come to embrace the philosophy of "switch when you can, route when you must." Although switches certainly provide substantial performance enhancements over layer 3 packet forwarding (routing), as users learned years ago with bridges, switches normally do not filter LAN broadcast traffic; in general, they replicate it on all ports. This not only can cause large switched LAN environments to become flooded with broadcasts, it is also wasteful of precious wide area network bandwidth. As a result, users have traditionally been forced to partition their networks with routers that act as broadcast "firewalls." Hence, simple switches alone do not allow users to phase out routers completely. One of the primary benefits of VLANs is that LAN switches supporting VLANs can be used to effectively control broadcast traffic, reducing the need for routing. Broadcast traffic from servers and end-stations in a particular VLAN is replicated only on those switch ports connected to end-stations belonging to that VLAN. Broadcast traffic is blocked from ports with no end-stations belonging to that VLAN, in effect creating the same type of broadcast firewall that a router provides. Only packets that are destined for addresses outside the VLAN need to proceed to a router for forwarding. There are multiple reasons for utilizing VLANs to reduce the need for routing in the network: Higher Performance and Reduced Latency. As the network expands, more and more routers are required to divide the network into broadcast domains. As the number of routers increase, latency begins to degrade network performance. A high degree of latency in the network is a problem now for many legacy applications, but it is particularly troublesome for newer applications that feature delaysensitive multimedia and interactivity. Switches that employ VLANs can accomplish the same division of the network into broadcast domains, but can do so at latencies much lower than those of routers. In

addition, performance, measured in packets per second, is usually much higher for switches than for traditional routers. However, it should be noted that there are some switches supporting network layerdefined VLANs that may not perform substantially faster than routers. Additionally, latency is also highly correlated to the number of hops a packet must traverse, no matter what internetworking device (switch or router) is located at each hop. Ease of Administration. Routers require much more complex configuration than switches; they are "administratively rich." Reducing the number of routers in the network saves time spent on network management. Cost. Router ports are more expensive than switch ports. Also, by utilizing cheaper switch ports, switching and VLANs allow networks to be segmented at a lower cost than would be the case if routers alone were used for segmentation.

In comparing VLANs with routing, VLANs have their disadvantages as well. The most significant weakness is that VLANs have been, to date, single-vendor solutions and therefore may lead to switch vendor lock-in. The primary benefits of VLANs over routing are the creation of broadcast domains without the disadvantages of routing and a reduction in the cost of moves and changes in the network. Therefore, if neither of these is a problem, then the user organization may want to forgo VLANs and continue deploying a multivendor network backbone, segmented by a mix of a few routers and a relatively large number of simple switches. Assuming a major implementation of VLANs, what is the role of routers in a network? Routers have two remaining responsibilities: to provide connectivity between VLANs, and to provide broadcast filtering capabilities for WAN links, where VLANs are generally not appropriate. Routing Between VLANs. VLANs can be used to establish broadcast domains within the network as routers do, but they cannot forward traffic from one VLAN to another. Routing is still required for interVLAN traffic. Optimal VLAN deployment is predicated on keeping as much traffic from traversing the router as possible. Minimizing this traffic reduces the chance of the router developing into a bottleneck. As a result, the corollary to "switch when you can, route when you must" in a VLAN environment becomes "routing is used only to connect VLANs." Having said this, however, keep in mind that in some cases routing may not prove to be much of a bottleneck. As mentioned earlier, integrating routing functionality into the backbone switch eliminates this bottleneck if this routing is accomplished at high speed for inter-VLAN packets. VLANs Over the WAN. Theoretically, VLANs can be extended across the WAN. However, this is generally not advised, since VLANs defined over the WAN will permit LAN broadcast traffic to consume expensive WAN bandwidth. Because routers filter broadcast traffic, they neatly solve this problem. However, if WAN bandwidth is free for a particular organization (for example, an electric utility with dark fiber installed in its right of way), then extending VLANs over a WAN can be considered. Finally, depending on how the they are constructed, IP multicast groups (functioning as "VLANs") can be effectively extended across the WAN, as well as the routers providing the WAN connections, without wasting WAN bandwidth. Security The ability of VLANs to create firewalls can also satisfy more stringent security requirements and thus replace much of the functionality of routers in this area. This is primarily true when VLANs are implemented in conjunction with private port switching. The only broadcast traffic on a single-user segment would be from that user's VLAN (that is, traffic intended for that user). Conversely, it would be impossible to "listen" to broadcast or unicast traffic not intended for that user (even by putting the workstation's network adapter in promiscuous mode), because such traffic does not physically traverse that segment. VLANs and ATM

While the concept of VLANs originated with LAN switches, their use may need to be extended to environments where ATM networks and ATM-attached devices are also present. Combining VLANs with ATM networks creates a new set of issues for network managers, such as relating VLANs to ATM emulated LANs (ELANs), and determining where to place the routing function. VLANs Transparent to ATM In a LAN backbone with VLANs spanning more than one LAN switch, switches determine where frames have originated by the techniques discussed earlier in "Communicating VLAN Membership Information" (VLAN tables, frame tagging, and TDM). In an environment where ATM exists only in the backbone (that is, there are no ATM-connected end-stations), ATM permanent virtual circuits (PVCs) may be set up in a logical mesh to carry intra-VLAN traffic between these multiple LAN switches. In this environment, any proprietary technique the vendor has employed is transparent to the ATM backbone. ATM switches do not have to be VLAN "aware." This means that ATM backbone switches could be from a different vendor than the LAN switches; ATM backbone switches could be selected without regard for VLAN functionality, allowing network managers to focus more on performance- related issues. As convenient as this situation sounds, it does not reflect reality for many network environments. Complexity Arising with ATM-Attached Devices Usually, organizations that implement ATM backbones would also like to connect workstations or, more likely, servers directly to those backbones. As soon as any logical end-station is connected via ATM, a new level of complexity arises. LAN Emulation must be introduced into the network to enable ATM-connected end-stations and non-ATM-connected end-stations to communicate. LAN EMULATION With the introduction of ATM-connected end-stations, the network becomes a truly "mixed" environment, with two types of networks operating under fundamentally different technologies: connectionless LANs (Ethernet, Token Ring, FDDI, etc.) and connection-oriented ATM. This environment puts the responsibility on the ATM side of the network to "emulate" the characteristics of broadcast LANs and provide MAC-toATM address resolution. The LAN Emulation (LANE) specification, standardized in 1995 by the ATM Forum, specifies how this emulation is accomplished in a multivendor environment. LANE specifies a LAN Emulation server (LES), which can be incorporated into one or more switches or a separate workstation to provide the MAC-toATM address resolution in conjunction with LAN Emulation clients (LECs), which are incorporated into ATM edge switches and ATM NICs.

Figure 2. Lan Emulation

Figure 2 briefly illustrates how LANE operates:

1.

2. 3. 4. 5.

The LAN switch receives a frame from an Ethernet-connected end-station. This frame is destined for another Ethernet end-station across the ATM backbone. The LEC (which in this situation resides in the LAN switch) sends a MAC-to-ATM address resolution request to the LES (which in this case resides in an ATM switch). The LES sends a multicast to all other LECs in the network. Only the LEC that has the destination (MAC) address in its tables responds to the LES. The LES then broadcasts this response to all other LECs. The original LEC recognizes this response, learns the ATM address of the destination switch, and sets up a switched virtual circuit (SVC) to transport the frame via ATM cells as per AAL5, which governs segmentation and reassembly.

In looking at the path of traffic between an Ethernet-attached client and an ATM-attached server, the section that is governed by LANE extends from the LEC in the ATM interface of the LAN switch to the LEC residing in the server's ATM NIC. From the standpoint of either MAC driver, frames pass directly between them just as if they were connected by a non-ATM backbone, with each LEC acting as a proxy MAC address. VLANs defined by port group would treat the ATM interface on the LAN switch as just another Ethernet port, and all ATM-attached devices would then be members of that VLAN. In this way, VLANs could be deployed without regard to whether the ATM switches in the backbone are from the same vendor (so long as they support LANE). However, from an administrative point of view, many organizations may not want to employ separate management software for the ATM backbone and may prefer to source both edge devices (LAN switches) and backbone devices (ATM switches) from the same vendor. LANE can also allow for multiple ELANs by establishing more than one LEC in the ATM interfaces of participating devices (as well as a separate LES for each ELAN). Each LEC in the ATM interface of the LAN switch is treated as a separate logical Ethernet port, and each LEC in a single ATM-attached device is seen as a separate Ethernet-attached end-station. Therefore, multiple LECs in a single ATM-attached device can be members of different VLANs, allowing these VLANs to overlap at ATM-attached devices. Since LANE supports only ATM-attached devices, while VLANs are defined for both ATM and non-ATM network devices, VLANs can be seen as supersets of ELANs (Figure 3).

Figure 3. VLANs as Supersets of ELANs

With this structure, an ATM backbone can enable all end-stations from multiple VLANs to access a centralized server or servers without passing through a router by establishing a separate ELAN for each VLAN. Since most traffic in a network is between client and server, establishing VLANs that overlap at ATM-attached servers greatly reduces the number of packets that must be routed between VLANs. Of course, there is still likely to be a small amount of inter-VLAN traffic remaining. Therefore, a router is still required for traffic to pass from one VLAN to another (and, therefore, from one ELAN to another). Figure 4 depicts this type of structure.

<Bild> Figure 4. Router Connecting Overlapping VLANs/ELANs

ROUTING BETWEEN EMULATED LANS AND/OR VLANS Since routing remains necessary in any mixed ATM/shared media environment to forward inter-VLAN traffic, network designers are faced with the question of where to locate the router functionality. The following are four architectural solutions to the problem of where to locate the routing functionality: edge routing, the "one-armed" router, the route server, and MPOA. Edge Routing. Basically, edge routing dictates that the routing function across the ATM backbone be incorporated into each LAN switch at the "edge" of the ATM backbone. Traffic within VLANs can be switched across the ATM backbone with minimal delay, while inter-VLAN packets are processed by the routing function built into the switch. In this way, an inter-VLAN packet does not have to make a special trip to an external router, eliminating a time-consuming extra hop. There are three other major advantages to this architecture. First, unlike solutions that have centralized routing, there is no single point of failure with edge routing architectures. Second, several solutions featuring edge routing are available today. Third, edge routing will function in multivendor environments if each vendor's equipment supports LAN Emulation. The primary disadvantage of edge routing is the difficulty of managing multiple physical devices relative to having centralized management of a consolidated router/routing function. Additionally, edge routing solutions may be more expensive than centralized routing solutions made up of a centralized router and multiple, less-expensive edge switches. The One-Armed Router. The concept of the so-called "one-armed router" has become particularly attractive because it removes the more processing-intensive, higher-latency routing function from the primary data path. A one-armed router sits off the side of an ATM backbone switch with a single ATM link, allowing packets that do not need to traverse the router to pass through the ATM backbone unimpeded. Another advantage of the one-armed router is that, relative to other configurations, it is less complex to configure and administer. The key to the one-armed router structure, shown in Figure 5, is to keep as much traffic as possible out of the one-armed router. By structuring VLANs to support the 80/20 rule (so that 80 percent of the traffic remains within each VLAN), the router is not required to handle most traffic. For this to work well, optimal configuration of VLANs to minimize inter-VLAN traffic (traffic passing through the one-armed router) is critical. There are several vendors presently shipping one-armed router solutions. One of the disadvantages of the one-armed router is that it represents a single point of failure in the network. For this reason, two or more redundant one-armed routers are generally preferred. However, perhaps the most significant drawback of the one-armed router is that its one arm can develop into a bottleneck if VLAN traffic does not support the 80/20 rule. This can occur particularly in networks with large amounts of peer-to-peer traffic.

Figure 5. One-Armed Router LAN switch

The Route Server. The route server model (see Figure 6) is physically similar to the one-armed router model, but logically very different in that it breaks up the routing function into distributed parts. In a onearmed router configuration, a packet from VLAN A heading to VLAN B is sent to the one-armed router, where it waits for address resolution, path calculation, establishment of a connection across the ATM backbone, and, finally, transmission. In a route server scheme, the same packet waits in the cache of the LAN switch at the edge of the ATM backbone before transmission. In this process, the packet itself never traverses a router. The only traffic to and from the route server is the signaling required to set up a connection between LAN switches across the ATM backbone. The advantage is that less routed traffic must be diverted to the route server, often reducing the number of hops required through the backbone. Also, overall traffic across the route server's one arm is reduced.

Figure 6. Route Server LAN switch There are, of course, disadvantages to the route server approach as well. First, initial vendor implementations are strictly proprietary and do not support standard routing protocols. Secondly, at this point available route servers only support IP. Of course, the route server shares one of the one-armed router's drawbacks in that it can be a single point of failure, but, as with the one-armed router, this problem can be mitigated through redundancy. Finally, because a route server architecture requires LAN switches to have a certain level of routing functionality, route server solutions tend to be more expensive and more complex to configure than the relatively simple LAN switches deployed in the one-armed router architecture. MPOA. There is at least one development that may eventually standardize the route server approach. The Multiprotocol over ATM (MPOA) standards working group of the ATM Forum is currently working out the details of an implementation model for MPOA service. While a variety of models have been proposed, MPOA is expected to provide direct virtual circuit connectivity between ATM-network-attached devices that may belong to different routing subnets. In other words, MPOA can let logical end-stations that are part of different ELANs communicate directly across an ATM network without requiring an intervening router. Since ELANs are subsets of VLANs, MPOA holds the promise of enabling an ATM backbone to connect VLANs without the need for an external router. MPOA can be considered an enhancement beyond LANE that integrates routing functionality into the LAN-ATM edge switch. All inter-VLAN traffic would be able to leverage this capability, and network latency would be reduced. An MPOA standard is not expected to be finalized until at least 1997, and the initial implementation will most likely support only TCP/IP. It should be noted that some of the disadvantages of the route server approach, such as cost and management complexity, would remain in MPOA solutions.

VLANS AND DHCP: OVERLAPPING SOLUTIONS With Microsoft's recent introduction of the Dynamic Host Configuration Protocol (DHCP), users now have another alternative for reducing the workload associated with administration of workstation IP address. Unfortunately, DHCP can actually conflict with VLAN implementation, especially with layer-3, IP-based VLANs. DHCP FUNCTIONALITY When considering the ability of VLANs to deal with ever-changing networks, it should be remembered that most of the difficulty in supporting adds, moves, and changes occurs in IP networks. In order to deal with the problem of reconfiguring IP addresses, Microsoft has developed DHCP, a TCP/IP-based solution incorporated into the Windows NT (TM) server and most Windows clients. Rather than establishing location-independent broadcast domains as VLANs do, DHCP dynamically allocates IP addresses to logical end-stations for fixed periods of time. When the DHCP server detects a workstation whose physical location no longer corresponds to its allocated IP address, it simply allocates that end-station a new address. By doing so, DHCP enables workstations to be moved from subnet to subnet without the network administrator having to manually configure the workstation's IP address or update host table information. The element of DHCP that equates most closely to VLAN functionality is the network administrator's ability to specify a range of IP addresses available for a particular logical workgroup. These logical groups are termed "scopes" in the Microsoft lexicon. However, scopes should not be equated with VLANs, because members of a single scope are still bound by their physical subnet, although there can be multiple scopes residing in each subnet. Consequently, DHCP implementation may reduce the labor-intensive administration of TCP/IP networks, but DHCP alone does not control network broadcasts in the same way that VLANs do. BEST USE FOR EACH In what types of network environments should VLANs be implemented, and in what types of network environments does DHCP make the most sense? Since DHCP is solely an IP-based solution, it has little appeal in environments where IP users are a minority, since all non-TCP/ IP clients would be excluded from scope membership. In particular, network environments where non-TCP/IP protocols are required for mission-critical applications may benefit more from VLAN implementation, since VLANs can be used to contain multi-protocol broadcast traffic. However, for smaller, purely TCP/IP network environments (under 500 nodes), DHCP alone may suffice. By simply having fewer total network nodes and fewer physical subnets, the need to establish fully location-independent logical groups is greatly reduced. Additionally, for medium-sized organizations that, for whatever reason, do not support location-independent work-groups, VLANs lose much of their appeal when compared to DHCP. There is one area in which VLANs and DHCP do not compete: reducing the necessity for routing in the network. Although DHCP servers dynamically maintain address tables, they lack routing functionality and cannot create broadcast domains. Therefore, DHCP has no impact on an organization's need for routing in the network. In environments where the containment of broadcast traffic without having to resort to routers is a major requirement, VLANs are a better solution. OVERLAP BETWEEN DHCP AND VLANS It what ways can DHCP and VLANs work together, and in what situations do they represent competitive solutions? DHCP and layer-3, IP-based VLANs clearly represent competitive solutions because of addressing problems that stem from implementing layer 3-based VLANs in conjunction with DHCP. If a client workstation physically moves to a new subnet, the DHCP server will allocate a new IP address for that workstation. Yet, this workstation's VLAN membership is based on the old IP address. Therefore, the network administrator would have to manually update the client's IP address in the switch's VLAN tables.

This would eliminate the primary benefit of DHCP and one of the primary benefits of IP-based VLANs. In summary, these two solutions represent an either/or proposition for most network environments. Implementing VLANs defined by MAC-layer address in conjunction with DHCP is a somewhat more plausible solution. However, DHCP together with MAC-based VLANs would create a two-tiered, redundant matrix of logical groups (MAC address-based VLANs and DHCP scopes). Having two tiers of logical groups would make otherwise easy-to-manage, "drag-and-drop" moves, adds, and changes unnecessarily difficult and might entail more labor-intensive network administration than if neither solution was implemented. Port group-based VLANs and DHCP can coexist, and their joint implementation can even be complementary. As stated earlier, when users in VLANs based purely on port groups move from one port group to another, their VLAN membership changes. In a non-DHCP environment where IP subnets correspond one-to-one with VLANs, users who move from one port group to another would still need to have their workstation reconfigured to reflect their new IP subnet. Implementing DHCP would make this reconfiguration automatic. The port group-based VLANs, of course, provide the broadcast containment that DHCP implementation alone does not. In this way, DHCP and port-group-based VLANs can work together to accomplish both broadcast containment and automation of moves and changes. Port group-based VLANs and DHCP, in conjunction with deployment of architectures that reduce the need for external routing of inter-VLAN traffic (such as multiple VLAN memberhip or integrating routing into the switch), represent a fairly complete short- to medium-term solution, which will alleviate the most pressing problems faced in many network environments. VLAN ARCHITECTURES GOING FORWARD Due to the trends toward server centralization, enterprise-wide e-mail, and collaborative applications, various network resources will need to be made available to users regardless of their VLAN membership. Ideally, this access should be provided without most user traffic having to traverse a router. Organizations that implement VLANs recognize the need for certain logical end-stations (for example, centralized servers) to communicate with multiple VLANs on a regular basis, either through overlapping VLANs (in which network-attached end-stations simultaneously belong to more than one VLAN) or via integrated routing that can process inter-VLAN packets at wire speed. From a strategic standpoint, these organizations have two ways to deploy VLANs: an "infrastructural" VLAN implementation or a "servicebased" VLAN implementation. The choice of approach will have a substantial impact on the overall network architecture, and may even affect the management structure and business model of the organization. INFRASTRUCTURAL VLANS An infrastructural approach to VLANs is based on the functional groups (that is, the departments, workgroups, sections, etc.) that make up the organization. Each functional group, such as accounting, sales, and engineering, is assigned to its own uniquely defined VLAN. Based on the 80/20 rule, the majority of network traffic is assumed to be within these functional groups, and thus within each VLAN. In this model, VLAN overlap occurs at network resources that must be shared by multiple workgroups. These resources are normally servers, but could also include printers, routers providing WAN access, workstations functioning as gateways, and so forth. The amount of VLAN overlap in the infrastructural model is minimal, involving only servers rather than user workstations-- making VLAN administration relatively straightforward. In general, this approach fits well in those organizations that maintain clean, discrete organizational boundaries. The infra-structural model is also the approach most easily enabled by presently available solutions and fits more easily with networks deployed today. Moreover, this approach does not require network administrators to alter how they view the network, and entails a lower cost of deployment. For these reasons, most organizations should begin with an infrastructural approach to VLAN implementation.

As can be seen in the example in Figure 7, the e-mail server is a member of all of the departments' VLANs, while the accounting database server is only a member of the accounting VLAN.

Figure 7. Infrastructural VLANs

SERVICE-BASED VLANS A service-based approach to VLAN implementation looks, not at organizational or functional groups, but at individual user access to servers and applications--that is, network resources. In this model, each VLAN corresponds to a server or service on the network. Servers do not belong to multiple VLANs-- groups of users do. In a typical organization, all users would belong to the e-mail server's VLAN, while only a specified group such as the accounting department plus top-level executives would be members of the accounting database server's VLAN. By its nature, the service-based approach creates a much more complex set of VLAN membership relationships to be managed. Given the level of most VLAN visualization tools presently available, a large number of overlapping VLANs using the service-based approach could generate incomprehensible multilevel network diagrams at a management console. Therefore, to be practical, service-based VLAN solutions must include a high level of automatic configuration features. However, in response to the types of applications organizations want to deploy in the future, as well as the shift away from traditional, more rigid organizational structures, the trend in VLAN implementation will be toward the service-based approach. Figure 8 depicts the service-based VLAN model.

Figure 8. Service-Based VLANs As bandwidth to the desktop increases and as vendor solutions become available to better manage greater VLAN overlap, the size of the groups that belong to a particular set of VLANs may become smaller and smaller. At the same time, the number of these groups becomes larger and larger, to the point where each individual could have a customized mix of services delivered to his or her workstation. Taking that concept a step further, control over what services are delivered at a given time could be left up to each individual user. At that point, the network structure begins to take on the multiple-channel characteristics of a cable TV (CATV) network. In fact, at this stage, this model finds the greatest degree of similarity in VLANs defined by IP multicast group--each workstation has the choice of which IP multicast or "channel" it wants to belong to. In such a future environment, VLANs lose the characteristics of static or semistatic broadcast domains defined by the network manager, and become channels to which users subscribe. Users simply sign up for the applications they need delivered to them at a particular time. Application use could be accounted for, enabling precise and automated chargeback for network services. Network managers could also retain control in order to block access to specific channels by certain users for security purposes. VLAN MIGRATION STRATEGIES As this paper has demonstrated, there are many factors to be considered in VLAN implementation: technological, architectural, and organizational. Given the effects of VLANs on network architecture, organizational structure, and even the business model of some organizations, it is difficult to deploy VLAN technology solely as a tactical solution, only where and when it is needed. However, this does not imply an all-or-nothing strategy in which the network architecture is transformed overnight from one based on physical subnets and router-based segmentation to one of service-based VLANs. What steps are necessary before applying VLANs to an enterprise network? Initially, VLANs should be seen as a solution to at least one of two problems: Containment of broadcast traffic to minimize dependence on routers Reduction in the cost of network moves and changes

An organization where broadcast traffic is not yet a problem, or where the cost of network moves and changes is tolerable, may want to forgo implementing VLANs for the time being. However, the majority of large enterprise networks are now experiencing one or both of these problems. In organizations that are rapidly replacing routers with switches and may soon face broadcast traffic containment issues, another element of the network architecture should be considered: the degree to which

the network has evolved toward a single user/port switched LAN architecture. If the majority of users are still on shared LAN segments, the ability of VLANs to contain broadcasts is greatly reduced. If multiple users belonged to different VLANs on the same shared LAN segment, that segment would receive broadcasts from each VLAN--defeating the goal of broadcast containment. Having determined that VLANs need to be a part of network planning in the immediate future, server access, server location, and application utilization must all be thoroughly analyzed to determine the nature of traffic flow in the network. This analysis should answer the remaining questions about where VLAN broadcast domains should be deployed, what role ATM needs to play, and where the routing function should to be placed. Because of the limitations of present VLAN technology, initial VLANs are likely to employ an infrastructural approach. However, as vendor solutions develop, many organizations will want to consider migration toward a more service-based model, which will more easily let users subscribe to various network services. This concept of user-controlled subscribership, as opposed to administrator-controlled membership, is augmented by NICs with built-in VLAN functionality operating in environments with a single user per switch port. In this scheme, the NIC driver dynamically tells the switch which multicast groups or VLANs it wants to belong to. Certainly, this type of distributed VLAN control leverages the increasing processing power of the desktop and enables a higher degree of other, related functionality such as automatic VLAN configuration and traffic monitoring. In addition, agents residing in each NIC will enable the workstation to collect and report information on specific application usage (rather than just simple layer 2 traffic statistics in the case of RMON1). This capability facilitates the automated chargeback for network services described earlier for service-based VLANs. If individual users control VLAN membership, what about security? Clearly, users cannot be allowed to simply subscribe to any network service they wish. The network administrator must be able to establish policies that define which users have access to what resources and what class of service each user is entitled to. One solution to the security problem may come in the form of an authentication server. These servers may well develop into the primary method by which the VLANs of the future are defined. Authentication servers define VLAN membership by user ID (password or other authentication device) rather than by MAC address or IP address. Defining VLANs in this way greatly increases flexibility and also implies a certain level of integration of VLANs with the network operating system, which typically asks the user for a password anyway to allow or deny access to network resources. One of the primary advantages of authentication servers is that they allow the user to take his or her VLAN anywhere, without regard to which workstation or protocol is being used. The analysis of network traffic, applications usage, server access, and so on that is necessary in the VLAN migration process, and which will be greatly furthered by the implementation of RMON2, may simply produce VLANs that correspond to functional teams or departments. On the other hand, if migration is undertaken with a holistic view of the capabilities of VLAN technology, and the network designers ask the question, "Who should talk to whom?" rather than "Who is talking to whom?," it may become apparent that fundamental process and organizational changes are needed. Many organizations are making such changes: trends such as flatter hierarchies, revamped workflows, and innovative business models are helping to fully leverage the possibilities of emerging applications.

Chapter No 4 Introduction to Packet Tracer

Cisco Packet Tracer is a powerful network simulation program that allows students to experiment with network behavior and ask what if questions. As an integral part of the Networking Academy comprehensive learning experience, Packet Tracer provides simulation, visualization, authoring, assessment, and collaboration capabilities and facilitates the teaching and learning of complex technology concepts. Packet Tracer is a protocol simulator developed by Dennis Frezzo and his team at Cisco Systems. Packet Tracer (PT) is a powerful and dynamic tool that displays the various protocols used in networking, in either Real Time or Simulation mode. This includes layer 2 protocols such as Ethernet and PPP, layer 3 protocols such as IP, ICMP, and ARP, and layer 4 protocols such as TCP and UDP. Routing protocols can also be traced.

Fig Pakcet Trace Version 5.0

Start Packet Tracer

Step 2: Choosing Devices and Connections We will begin building our network topology by selecting devices and the media in which to connect them. Several types of devices and network connections can be used. For this lab we will keep it simple by using End Devices, Switches, Hubs, and Connections.

Single click on each group of devices and connections to display the various choices. The devices you see may differ slightly.

Step 3: Building the Topology Adding Hosts Single click on the End Devices.

Single click on the Generic host.

Move the cursor into topology area. You will notice it turns into a plus + sign.

Single click in the topology area and it copies the device.

Add three more hosts.

Step 4: Building the Topology Connecting the Hosts to Hubs and Switches Adding a Hub Select a hub, by clicking once on Hubs and once on a Generic hub.

Add the hub by moving the plus sign + below PC0 and PC1 and click once.

Connect PC0 to Hub0 by first choosing Connections.

Click once on the Copper Straight-through cable.

Perform the following steps to connect PC0 to Hub0: 1. Click once on PC0 2. Choose FastEthernet 3. Drag the cursor to Hub0 4. Click once on Hub0 and choose Port 0 5. Notice the green link lights on both the PC0 Ethernet NIC and the Hub0 Port 0 showing that the link is active. 1 2 3 4 5

Repeat the steps above for PC1 connecting it to Port 1 on Hub0. (The actual hub port you choose does not matter.)

Adding a Switch Select a switch, by clicking once on Switches and once on a 2950-24 switch.

Add the switch by moving the plus sign + below PC2 and PC3 and click once.

Connect PC2 to Hub0 by first choosing Connections.

Click once on the Copper Straight-through cable.

Perform the following steps to connect PC2 to Switch0: 1. Click once on PC2 2. Choose FastEthernet 3. Drag the cursor to Switch0 4. Click once on Switch0 and choose FastEthernet0/1 5. Notice the green link lights on PC2 Ethernet NIC and amber light Switch0 FastEthernet0/1 port. The switch port is temporarily not forwarding frames, while it goes through the stages for the Spanning Tree Protocol (STP) process. 6. After a about 30 seconds the amber light will change to green indicating that the port has entered the forwarding stage. Frames can now forwarded out the switch port. Note: Spanning Tree Protocol (STP) is discussed later. 1 2 3 4 5 6

Repeat the steps above for PC3 connecting it to Port 3 on Switch0 on port FastEtherent0/2. (The actual switch port you choose does not matter.)

Move the cursor over the link light to view the port number. Fa means FastEthernet, 100 Mbps Ethernet.

Step 5: Configuring IP Addresses and Subnet Masks on the Hosts Before we can communicate between the hosts we need to configure IP Addresses and Subnet Masks on the devices. Click once on PC0.

Choose the Config tab and click on Settings. It is here that you can change the name of PC0. It is also here where you would enter a Gateway IP Address, also known as the default gateway and the DNS Server IP Address. We will discuss this later, but this would be the IP address of the local router. If you want, you can enter the Gateway IP Address 172.16.1.1 and DNS Server IP Address 172.16.1.100, although it will not be used in this lab.

Click on Interface and then FastEthernet. Although we have not yet discussed IP Addresses, add the IP Address to 172.16.1.10. Click once in the Subnet Mask field to enter the default Subnet Mask. You can leave this at 255.255.0.0. We will discuss this later.

Also, notice this is where you can change the Bandwidth (speed) and Duplex of the Ethernet NIC (Network Interface Card). The default is Auto (autonegotiation), which means the NIC will negotiate with the hub or switch. The bandwidth and/or duplex can be manually set by removing the check from the Auto box and choosing the specific option. Bandwidth - Auto If the host is connected to a hub or switch port which can do 100 Mbps, then the Ethernet NIC on the host will choose 100 Mbps (Fast Ethernet). Otherwise, if the hub or switch port can only do 10 Mbps, then the Ethernet NIC on the host will choose 10 Mbps (Ethernet). Duplex - Auto Hub: If the host is connected to a hub, then the Ethernet NIC on the host will choose Half Duplex. Switch: If the host is connected to a switch, and the switch port is configured as Full Duplex (or Autonegotiation), then the Ethernet NIC on the host will choose Full Duplex. If the switch port is configured as Half Duplex, then the Ethernet NIC on the host will choose Half Duplex. (Full Duplex is a much more efficient option.) The information is automatically saved when entered.

To close this dialog box, click the X in the upper right.

Repeat these steps for the other hosts. Use the information below for IP Addresses and Subnet Masks. Host PC0 PC1 PC2 PC3 IP Address 172.16.1.10 172.16.1.11 172.16.1.12 172.16.1.13 Subnet Mask 255.255.0.0 255.255.0.0 255.255.0.0 255.255.0.0

Verify the information To verify the information that you entered, move the Select tool (arrow) over each host.

Deleting a Device or Link To delete a device or link, choose the Delete tool and click on the item you wish to delete.

Step 6: Connecting Hub0 to Switch0 To connect like-devices, like a Hub and a Switch, we will use a Cross-over cable. Click once the Crossover Cable from the Connections options.

Move the Connections cursor over Hub0 and click once.

Select Port 5 (actual port does not matter).

Move the Connections cursor to Switch0.

Click once on Switch0 and choose FastEthernet0/4 (actual port does not matter).

The link light for switch port FastEthernet0/4 will begin as amber and eventually change to green as the Spanning Tree Protocol transitions the port to forwarding.

Step 7: Verifying Connectivity in Realtime Mode Be sure you are in Realtime mode.

Select the Add Simple PDU tool used to ping devices..

Click once on PC0, then once on PC3.

The PDU Last Status should show as Successful.

Resetting the Network At this point we will want to reset the network, Whenever you want to reset the network and begin the simulation again, perform the following tasks: Click Delete in the PDU area.

Now, Power Cycle Devices and confirm the action.

Chapter No 5. Simulation of Topology in Packet Tracer 5.0

Fig Represents Partial Mesh Topology

References: https://en.wikipedia.org/wiki/Mesh_networking

http://www.cisco.com/web/learning/netacad/course_catalog/PacketTracer.html

www.infoworld.com/article/ 05/07/20/HNmeshnetworks_1.html http://mesh.nowwireless.com http://www.oreillynet.com/pub/a/wireless/2004/01/22/wirelessmesh.html http://wireless.industrial-networking.com/articles/ articledisplay.asp?id=223 http://www.ncte.ie/documents/networking/Introduction_Computer_Networkin...%E2%80%8E