7.6.1 Packet Tracer - Wan Concepts

Introduction to WAN Concepts in Cisco Packet Tracer 7.6.1

Cisco Packet Tracer 7.6.1 is more than just a network‑simulation tool for CCNA labs; it also offers a realistic environment to explore Wide Area Network (WAN) concepts. Still, understanding how WAN technologies operate—such as PPP, HDLC, Frame Relay, and MPLS—helps students and professionals design resilient, scalable networks that span cities, countries, or even continents. But this article walks through the essential WAN components available in Packet Tracer 7. In real terms, 6. 1, demonstrates step‑by‑step configuration of common WAN links, explains the underlying protocols, and answers frequent questions that arise when working with simulated WAN topologies.

Why Simulate WANs in Packet Tracer?

• Cost‑effective learning – No physical serial cards or leased lines are required.
• Rapid prototyping – Switch between technologies (e.g., PPP ↔ Frame Relay) with a few clicks.
• Immediate feedback – Real‑time packet tracing and console output reveal protocol behavior.
• Exam preparation – The tool mirrors the command set and output of Cisco IOS, making it ideal for CCNA, CCNP, and even entry‑level CCIE labs.

Core WAN Devices Available in 7.6.1

Setting Up a Basic WAN Link (Serial PPP)

Step 1 – Create the Topology

1. Drag two ISR 2911 routers onto the workspace.
2. Add a Cloud object and name it ISP.
3. Connect Router A’s Serial0/0/0 to the cloud using a Serial DCE cable.
4. Connect Router B’s Serial0/0/0 to the same cloud with a Serial DTE cable.

Step 2 – Configure Serial Interfaces

RouterA> enable
RouterA# configure terminal
RouterA(config)# interface serial0/0/0
RouterA(config-if)# ip address 10.0.0.1 255.255.255.252
RouterA(config-if)# encapsulation ppp
RouterA(config-if)# clock rate 64000   ! DCE side only
RouterA(config-if)# no shutdown
RouterA(config-if)# exit
RouterA(config)# exit
RouterA# write memory

RouterB> enable
RouterB# configure terminal
RouterB(config)# interface serial0/0/0
RouterB(config-if)# ip address 10.0.0.2 255.255.255.252
RouterB(config-if)# encapsulation ppp
RouterB(config-if)# no shutdown
RouterB(config-if)# exit
RouterB(config)# exit
RouterB# write memory

Step 3 – Verify Connectivity

RouterA# ping 10.0.0.2

A successful reply confirms that PPP encapsulation and the clock rate are correctly set.

What PPP Provides

• Authentication (CHAP, PAP) – optional but useful for securing WAN links.
• Multilink support – aggregates multiple physical circuits into a single logical link.
• Compression – reduces bandwidth consumption for low‑speed links.

Configuring HDLC vs. PPP

By default, Cisco routers use HDLC on serial interfaces. Switching to PPP is a single command (encapsulation ppp). The choice depends on:

• Compatibility – If both ends are Cisco, HDLC works; for multi‑vendor environments, PPP is required.
• Security – PPP can enforce CHAP/PAP; HDLC has none.
• Feature set – PPP supports multilink, while HDLC does not.

Quick Comparison

Frame Relay in Packet Tracer

Frame Relay remains a popular WAN technology for teaching because it introduces virtual circuits (PVCs) and Data Link Connection Identifiers (DLCIs) without the complexity of MPLS Small thing, real impact. Still holds up..

Building a Frame Relay Network

1. Place a WAN Emulation Server (named FR‑Provider) in the center And that's really what it comes down to..

2. Connect Router A and Router B to the server using Serial DCE cables.

3. On the server, create two PVCs:

   • PVC 1: DLCI 100 from Router A to Router B
   • PVC 2: DLCI 200 from Router B to Router A

4. Assign IP addresses on sub‑interfaces:

RouterA(config)# interface serial0/0/0.100
RouterA(config-subif)# encapsulation frame‑relay
RouterA(config-subif)# frame‑relay interface‑demand
RouterA(config-subif)# ip address 172.16.0.1 255.255.255.252
RouterA(config-subif)# exit

RouterB(config)# interface serial0/0/0.200
RouterB(config-subif)# encapsulation frame‑relay
RouterB(config-subif)# frame‑relay interface‑demand
RouterB(config-subif)# ip address 172.16.0.2 255.255.255.252
RouterB(config-subif)# exit

5. Verify the PVCs with show frame‑relay pvc.

Key Frame Relay Concepts

• Committed Information Rate (CIR) – the guaranteed bandwidth; Packet Tracer simulates it via QoS settings.
• Burst‑size – allows temporary traffic spikes above CIR.
• LMI (Local Management Interface) – maintains PVC status; three standards exist (Cisco, ANSI, ITU).

MPLS Basics in Packet Tracer

Although Packet Tracer’s MPLS implementation is simplified, it still demonstrates label switching, LDP (Label Distribution Protocol), and VRF (Virtual Routing and Forwarding).

Simple MPLS Lab

1. Deploy three routers: PE1, PE2, and P‑Core.
2. Connect PE1 ↔ P‑Core ↔ PE2 with GigabitEthernet links.
3. Enable MPLS on core interfaces:

P-Core# configure terminal
P-Core(config)# interface g0/0
P-Core(config-if)# mpls ip
P-Core(config-if)# exit
P-Core(config)# interface g0/1
P-Core(config-if)# mpls ip
P-Core(config-if)# exit

4. On PE routers, enable MPLS LDP on all interfaces that face the core:

PE1(config)# mpls label protocol ldp
PE1(config)# interface g0/0
PE1(config-if)# mpls ip

5. Create a VRF on each PE to separate customer traffic:

PE1(config)# ip vrf CUSTOMER_A
PE1(config-vrf)# rd 100:1
PE1(config-vrf)# route-target export 100:1
PE1(config-vrf)# route-target import 100:1
PE1(config-vrf)# exit
PE1(config)# interface g0/1
PE1(config-if)# ip vrf forwarding CUSTOMER_A
PE1(config-if)# ip address 192.168.10.1 255.255.255.0

6. Verify label bindings with show mpls forwarding-table.

Why MPLS Matters

• Scalability – Labels replace long IP lookups, speeding up forwarding.
• Traffic engineering – Allows explicit path selection (not covered in basic Packet Tracer).
• Service separation – VRFs enable multiple customers to share the same physical infrastructure securely.

WAN Optimization Techniques Simulated in Packet Tracer

Even though Packet Tracer does not model real‑world compression algorithms, you can emulate WAN optimization by configuring:

• IP QoS – Prioritize voice or critical data using class-map, policy-map, and service-policy.
• TCP MSS adjustment – Reduce segment size for low‑bandwidth links (ip tcp adjust-mss 1200).
• Static routes with bandwidth metrics – Influence path selection to favor higher‑capacity WAN links.

Example: Prioritizing VoIP over a Serial Link

RouterA(config)# class-map VOICE
RouterA(config-cmap)# match ip dscp ef
RouterA(config)# policy-map WAN-POLICY
RouterA(config-pmap)# class VOICE
RouterA(config-pmap-c)# priority percent 70
RouterA(config-pmap)# class class-default
RouterA(config-pmap-c)# fair-queue
RouterA(config)# interface serial0/0/0
RouterA(config-if)# service-policy output WAN-POLICY

Frequently Asked Questions (FAQ)

Q1: Can I simulate a PPPoE broadband connection in Packet Tracer?
A: Yes. Use a PPPoE Server (available under the “End Devices” menu) and configure the router’s Ethernet interface as a PPPoE client. The CLI mirrors real IOS commands (pppoe enable, pppoe-client dial-pool-number) Worth keeping that in mind. Practical, not theoretical..

Q2: How do I emulate a leased‑line bandwidth limit?
A: Apply the bandwidth command on the serial interface (e.g., bandwidth 1544 for a T1) and use QoS shaping (policy-map with shape average). Packet Tracer respects these values when calculating delay and jitter in the simulation.

Q3: Is it possible to test BGP over a WAN in Packet Tracer?
A: BGP is supported on routers with the appropriate IOS image. Create two routers, assign them AS numbers, and configure neighbor statements. The simulation will display BGP table updates, but advanced features like route‑reflectors are not fully implemented That's the whole idea..

Q4: Why does my Frame Relay PVC stay in the “inactive” state?
A: see to it that the DLCI numbers match on both ends and that the WAN Emulation Server has the PVC defined. Also verify that the router interfaces are not shut down.

Q5: Can I practice MPLS traffic engineering (RSVP‑TE) in Packet Tracer?
A: The current version (7.6.1) does not support RSVP‑TE. You can still explore basic label switching and VRF concepts.

Troubleshooting Common WAN Issues

1. Serial Interface Not Coming Up

   • Check the cable type (DCE vs. DTE). Only the DCE side can set clock rate.
   • Verify that both ends have compatible encapsulation (ppp vs. hdlc).

2. PPP Authentication Fails

   • Ensure the same authentication method (CHAP or PAP) is configured on both routers.
   • Verify the username/password strings are identical and case‑sensitive.

3. Frame Relay “In Use” but No Traffic

   • Confirm frame‑relay interface‑demand is not preventing traffic when the link is idle.
   • Use no frame‑relay interface‑demand for constant traffic flow.

4. MPLS Labels Not Distributed

   • Enable LDP on all core interfaces (mpls label protocol ldp).
   • Verify that the interfaces have IP addresses; LDP works only on IP‑enabled links.

5. High Latency in Simulated WAN

   • Adjust the link delay property in the connection’s settings (right‑click → “Properties”).
   • Remember that Packet Tracer adds a default delay based on the link type (e.g., 20 ms for serial).

Conclusion

Cisco Packet Tracer 7.6.1 provides a strong sandbox for mastering WAN concepts ranging from simple serial PPP links to sophisticated MPLS VRF deployments. Day to day, by following the step‑by‑step configurations outlined above, learners can visualize how data traverses wide‑area networks, troubleshoot common problems, and experiment with optimization techniques—all without the expense of physical hardware. Plus, consistent practice in this simulated environment builds the intuition required for real‑world WAN design and prepares candidates for certification exams. Embrace the flexibility of Packet Tracer, layer your knowledge from HDLC → PPP → Frame Relay → MPLS, and you’ll be ready to architect resilient, high‑performance wide area networks.