Cisco Packet Tracer 7.x tutorials

Packet Tracer 7.2.1 - IP telephony devices

Details

Last Updated: Monday, 12 August 2019 19:18

Published: Saturday, 25 September 2010 12:04

Written by PacketTracerNetwork

Supported devices in Packet Tracer 7.2.1

Cisco Packet Tracer 7.2.1 supports three telephony devices :

• Cisco 7960 IP Phone
• Home VOIP device for analog phone connection to an IP network.
• Cisco IP Communicator software on desktop or laptop PC

Cisco 7960 IP Phone

Power up the phone

Two options are available in Packet Tracer for powering up the 7960 IP Phone :

• External power adapter
• PoE (only with 3560 multilayer switch)

If you choose to use the external power adapter, go to the physical tab and drag and drop the "IP_PHONE_POWER_ADAPTER" to the bottom left connector of the 7960 IP Phone.

If you want to use the PoE functionnality of the Cisco 3560 switch, apply the following configuration to the switch interface connected to the phone :

Switch(config)#int fastEthernet 0/1
Switch(config-if)#power inline auto

Place calls with 7960 IP Phone

The 7960 IP Phone emulated in Packet Tracer 7.2.1does not have any configurable options. It receives it's IP address through DHCP and it's line number from the Call Manager Express server.

 In the GUI tab, you can place a call, answer a call, and send Do, Re, and Mi notes to the recipient phone. To place a call enter the recipient's line number first using the keypad and then click on the handset to dial out.

To answer a phone call on the analog phone, click on the handset when the phone is ringing. While the line is connected, you can send Do, Re, or Mi to the recipient by pressing the respective buttons. In order to hear the sounds, be sure Sound is enabled in Preferences. To end a call, click on the handset.

Home VOIP device

The Home VoIP only has a "Server Address" configuration in which you have to place the Call Manager Express IP address.

Cisco IP Communicator software

The IP Communicator software is installed on desktop or laptop end devices. Configure the computer for DHCP address assignment and use the "Desktop" tab to access the IP Communicator software. The software will receive it's phone line number from the Cisco Call Manager Express server.

To place a phone call, enter the number of the recipient phone using the keypad and then click the Dial button. Once the recipient has answered the call, the status message will indicate that the Cisco IP Communicator is connected and a green light will show. While the call is still active, click on the Do, Re, or Mi buttons to send the respective sounds to the recipient. To end the call, click the EndCall button. For the best possible experience while making calls, be sure that Sound is enabled in Preferences.

If you want configure the Cisco IP Communicator to use a different TFTP server from the default TFTP server, follow these steps. On the upper right-hand corner of the Cisco IP Communicator GUI, there are four buttons above the words "Cisco IP Phone." Click on the first button from the left to open a context menu and then select Preferences. Select the option Use these TFTP Servers: and then enter the IP address of the TFTP server that you wish to use.

Packet Tracer 7.2.1 - Frame Relay configuration

Details

Last Updated: Monday, 12 August 2019 19:09

Published: Friday, 06 May 2011 11:55

Written by PacketTracerNetwork

Introduction

Frame Relay is a protocol standard for WAN internetworking which provides a fast and efficient method of transmitting packets through the network. Frame Relay offers an attractive alternative to both dedicated lines and X.25 networks for WAN links. The success of the Frame Relay protocol is based on the following two factors:

• Virtual circuits consume bandwidth only when they transport data. Consequently, many virtual circuits can exist across a given transmission line, which is an improvement compared to dedicated leased lines. In addition, each device can use more than the allowed bandwidth as necessary, and thus operate at higher speeds.
• The increased error-handling sophistication at end stations and the improved reliability of communication lines allows the Frame Relay protocol to discard bad frames and thus eliminate time-consuming error-handling processing.

Cisco Packet Tracer 7.2.1 includes a "Cloud-PT" device for WAN emulation. This device can be configured as a Frame Relay switch.  Router are connected to the Frame Relay switch using serial connections. Virtual circuits, LMI types, and DLCI are configured using the Serial and Frame Relay tabs of the "Cloud-PT" device.

Network topology used in this tutorial

A hub and sopke sample network topology is created in Cisco Packet Tracer 7.2.2 :

• R0 router is the spoke router
• R1 and R2 routers are frame-relay spokes
• All frame relay routers are interconnected through a Cisco Packet Tracer Cloud device which emulates frame relay circuits.

Frame Relay configuration - WAN cloud

Configure the LMI type and DLCI of virtual circuits on each serial interface of the cloud used for Frame Relay operation.

Create the virtual circuits one the "Frame Relay" tab. DLCI's need to be configured on the "Serial" tabs before creating virtual circuits.

Frame Relay configuration - ISR router configuration

Frame relay hub router configuration (R0)

The hub router is configured with two sub-interfaces to create a virtual circuit with each spoke. Each frame relay sub-interface is mapped with the DLCI number of the corresponding circuit configured in the Packet Tracer WAN emulation Cloud. The DLCI number defines a single virtual connection through the WAN and are the Frame Relay equivalent to a hardware address. 

The encapsulation frame-relay command is mandatory on the main serial interface before configuring frame-relay sub interfaces.

The clock rate defines the speed on the serial interface

interface Serial0/0/0
 no ip address
 encapsulation frame-relay
!
interface Serial0/0/0.101 point-to-point
 ip address 192.168.101.1 255.255.255.252
 frame-relay interface-dlci 101
 clock rate 2000000
!
interface Serial0/0/0.102 point-to-point
 ip address 192.168.102.1 255.255.255.252
 frame-relay interface-dlci 102
 clock rate 2000000

Frame relay spoke routers configuration (R1 and R2)

The spoke routers have only one virtual circuit configured to reach the hub router. The DLCI configured on both spoke routers is the same as the DLCI is locally significant between the WAN Cloud and each customer.

Router R1 configuration

interface Serial0/0/0
 ip address 192.168.101.2 255.255.255.252
 encapsulation frame-relay
 frame-relay interface-dlci 100
!

Router R2 configuration

interface Serial0/0/0
 ip address 192.168.102.2 255.255.255.252
 encapsulation frame-relay
 frame-relay interface-dlci 100
!

Video

Packet Tracer 7.2 - ACL configuration

Details

Last Updated: Tuesday, 16 July 2019 21:12

Published: Saturday, 05 October 2013 14:00

Written by PacketTracerNetwork

Introduction

Access Control Lists (ACL) are used to filter network traffic on Cisco routers. In order to filter network traffic, ACLs control if routed packets have to be forwarded or blocked at the ingress or egress router interface. The router checks each packet to determine whether to forward or drop the packet based on the criteria specified in the ACL applied to the interface.

IP ACL types

Two types of IP ACL can be configured in Cisco Packet Tracer 7.2 :

• Standard ACLs : This is the oldest ACL type which can be configured on Cisco routers. Traffic is filtered based on the source IP address of IP packets. The access-list number can be any number from 1 to 99. This kind of ACL has to be placed near the destination to avoid blocking legitimate trafic from the source.

access-list 1 permit 10.2.25.0 0.0.0.255
access-list 1 deny any

• Extended ACLs : Introduced in IOS version 8.3, the extended ACLs are more complex and allow filtering of the IP traffic based on a combination of multiple criterias : source IP address, destination IP address, TCP or UDP port, protocol, .... In numbered ACLs, the access-list number can be any number from 100 to 199 or 2000 to 2699 (available in IOS versions >12.0.1). Such ACLs can also be named access lists in which the ACL number is replaced by a keyword. This kind of ACL has to be placed near the source as it allows fine grained control to ressources accessed. Placing the ACL near the destination will make the trafic travel through the network before beeing blocked, resulting in bandwidth waste.

access-list 1 permit ip 10.2.25.0 0.0.0.255 10.1.0.0 0.0.255.255
access-list 101 permit icmp any 10.1.0.0 0.0.255.255 echo
access-list 1 deny ip any any

Configuration on Cisco 2911 ISR Router

Restrict remote telnet or SSH access to the ISR router

Access lists can be used to restrict remote SSH or Telnet access to the ISR router management interface (VTY) from specific networks only. Only numbered access-lists are supported on the Virtual Terminal Line.

The access-class command is used to apply the access list on the Virtual Terminal Line. The following configuration deny administrative access to the router except for the 192.168.1.0/24 network hosting admin workstations. Note the wildcard mask used in the access-list configuration for the /24 network.

access-list 1 permit 192.168.1.0 0.0.0.255

line vty 0 4
 access-class 1 in
 login
line vty 5 15
 access-class 1 in
 login

Packet Tracer 7.1.1 - BGP configuration

Details

Last Updated: Tuesday, 16 July 2019 21:12

Published: Thursday, 20 October 2011 13:41

Written by PacketTracerNetwork

BGP in Packet Tracer

BGP (Border Gateway Protocol) is the core routing protocol of the Internet. It is described as a path vector protocol as BGP does not use traditional IGP (OSPF, EIGRP, RIP) metrics, but makes routing decisions based on path, network policies and/or rulesets. It maintains a table of IP networks or 'prefixes' which designate network reachability among autonomous systems (AS).

BGP protocol support has been added in Packet Tracer in the 5.3 version. This allows Cisco CCNP Route students to better understand this complex routing protocol and to be prepared for the simulation questions in the exam.

Internal BGP (iBGP) is currently not supported in Packet Tracer (see screenshot below). iBGP support has still not been added in the new Packet Tracer 7.1.1 version

IOS commands available in Packet Tracer 7.1.1

enable mode

• show ip bgpexit
• show ip bgp neighbors
• show ip bgp summary
• clear ip bgp *

router bgp mode

• bgp log-neighbor-changes
• bgp redistribute-internal
• bgp router-id A.B.C.D
• exit
• neighbor A.B.C.D next-hop-self
• neighbor A.B.C.D remote-as <1-65535>
• network A.B.C.D
• network A.B.C.D mask A.B.C.D
• redistribute connected / eigrp <1-65535> / ospf <1-65535> / static
• synchronization
• timers bgp <0-65535> <0-65535>

Sample BGP network

WAN1 router configuration  :

A simple eBGP peering with ISP1 router is configured in the WAN1 router.

interface Serial0/0/0
ip address 156.12.1.6 255.255.255.252
!
router bgp 65000
bgp log-neighbor-changes
no synchronization
neighbor 156.12.1.5 remote-as 10000

ISP1 router configuration :

Several loopback interfaces are configured in ISP1 router to simulate connected networks whose are advertised to WAN1 router through the BGP peering.

interface Loopback0
ip address 156.100.1.1 255.255.255.0
!
interface Loopback1
ip address 156.100.2.1 255.255.255.0
!
interface Loopback2
ip address 156.100.4.1 255.255.254.0
!
interface Serial0/0/0
ip address 156.12.1.5 255.255.255.252
clock rate 500000
!
router bgp 10000
bgp log-neighbor-changes
no synchronization
neighbor 156.12.1.6 remote-as 65000
network 156.100.4.0 mask 255.255.254.0
network 156.100.2.0 mask 255.255.255.0
network 156.100.1.0 mask 255.255.255.0
!