Build a three-site hospital network (West, Central, East) in Cisco Packet Tracer with:

• Separate VLANs for Clinic and Admin at each site
• Multilayer Switch (MLS) routing between VLANs (Inter-VLAN Routing)
• Edge switches for PC connections
• Successful pings between Clinic and Admin PCs inside each site

Each hospital site contains:

• 1 Multilayer Switch (3560-24PS)
• 2 Edge Switches (2960-24TT)
• 2 PCs (Clinic and Admin)

Connections:

• Each Edge Switch uplinks to its site’s MLS
• Each PC connects to its local Edge Switch
• No direct links between Edge Switches

PC IPs:
*Clinic PCs use .10 in their subnet (ex: 192.168.10.10)
*Admin PCs use .10 in their subnet (ex: 192.168.11.10)

enable
configure terminal
hostname West-MLS
ip routing

vlan 100
 name West-Clinic
vlan 110
 name West-Admin

interface vlan 100
 ip address 192.168.10.1 255.255.255.0
 no shutdown
interface vlan 110
 ip address 192.168.11.1 255.255.255.0
 no shutdown

interface fastEthernet0/1
 switchport mode trunk
 no shutdown
interface fastEthernet0/2
 switchport mode trunk
 no shutdown

end
copy running-config startup-config

(Central-MLS and East-MLS use their own VLAN numbers and IP networks.)

enable
configure terminal
hostname North-West-Wing-SW

vlan 100
 name West-Clinic
vlan 110
 name West-Admin

interface fastEthernet0/2
 switchport mode access
 switchport access vlan 100
 no shutdown
interface fastEthernet0/3
 switchport mode access
 switchport access vlan 110
 no shutdown

interface fastEthernet0/1
 switchport mode trunk
 no shutdown

end
copy running-config startup-config

(Repeat similar commands for all edge switches with their site-specific VLAN numbers.)

hostname <name>                      # set device name
vlan <id>                             # create VLAN
name <vlan-name>                      # name the VLAN
interface vlan <id>                   # create SVI (gateway)
ip address <ip> <mask>                # assign IP to SVI
no shutdown                           # enable interface
ip routing                             # enable L3 routing on MLS
interface fastEthernet0/x             # select a port
switchport mode access/trunk          # set port mode
switchport access vlan <id>           # assign access VLAN
copy running-config startup-config    # save configuration
show vlan brief                        # view VLAN/port assignments
show interface trunk                   # verify trunk status
show ip interface brief                # verify SVI status

• Ping fails but own gateway works → PC plugged into wrong VLAN (moved cable or reconfigured port).
  Example: Central Admin PC initially connected to a port in VLAN 200 instead of 210.
• Invalid input detected → switchport commands entered before entering interface mode.
• No inter-VLAN routing → ip routing missing on MLS.

For each site, confirm:

From Clinic PC

ping <own gateway>      # e.g. 192.168.10.1
ping <other gateway>    # e.g. 192.168.11.1
ping <Admin PC>         # e.g. 192.168.11.10

From Admin PC

ping <own gateway>
ping <other gateway>
ping <Clinic PC>

All pings should succeed inside each site.

Take and save the following for your report:

1. Topology Diagram – full network view with all three sites and connections.
2. PC IP Configs – each PC showing correct IP, mask, and gateway.
3. Successful Ping Windows –
   • Clinic → Admin PC inside each site
   • Clinic → Other VLAN gateway inside each site
4. Switch CLI outputs –
   • show vlan brief from one edge switch per site (ports clearly in correct VLANs)
   • show interface trunk from one MLS (trunks carrying the right VLANs)
5. MLS Routing Proof – show ip interface brief showing all VLAN SVIs up/up and IPs assigned.

All three hospital sites now provide:

• Proper VLAN separation between Clinic and Admin networks
• Inter-VLAN routing within each site using Multilayer Switches
• Verified connectivity with successful ping tests

This meets the Alternative Assignment Lab 4-1 requirements.

##Screenshots