Diagram 2

Frame Relay Setup

R6
S3/0

R3
S3/3

Frame Relay
(R8 is FR Switch)

S3/1 L0 L1
R1

S3/2

R2
NETWORK DIAGRAM
Make a network diagram that includes all addresses, frame relay DLCI’s and other pertinent information.
This diagram will be useful, as a reference, during trouble shooting.

TERMINAL SERVER
Setup the terminal server so that all routers can be accessed via reverse telnet. The asynchronous lines are
connected as follows:

R1 – line 2001
R2 – line 2002
R3 – line 2003
R4 – line 2004
Catalyst – 2005
R6 – 2006

IP ADDRESSING
Use the class B network address 138.10.0.0 throughout the network, except on
the backbone interfaces. Use the subnet masks shown on diagram 1. If a subnet
mask is not given for an interface, use /24. For Backbone 1 use the address
160.200.1.1 /24. For Backbone 2 use the address 160.100.2.1 /24.

FRAME RELAY
Configure frame relay between R1, R2, R3 and R6. Refer to diagram 2 for the DLCI routing setup on the
frame switch.

• The PVC between R1 and R2 should be on its own subnet.

• The PVC’s between R2, R3 and R6 should be on a single subnet.
• For the PVC between R2 and R1, let the average and peak rates for transmission be 32Kbps and
64Kbps respectively.

X.25
Configure back to back X.25 for the connection between R4 and R6.

VLANS
Configure the switch so that R6 and R3’s ethernet interfaces are in VLAN 2.

• Set the switch’s VTP domain to WSU.

• Configure the switch so that you can ping any device on VLAN 2’s subnet.
• Ensure that if another switch were added to VLAN 2 your switch would be the root switch.

OSPF
Configure OSPF for the frame relay links between R2, R3 and R6, for VLAN 2 and for Ring 2.
• The frame relay network should be in area 0.
• VLAN 2 should be in area 2.
• Ring 2 should be in area 5.
• Configure MD5 authentication in area 2.
• The 160.100.2.0 network should not be seen by the rest of the network.

IGRP & EIGRP

Configure IGRP on R1 and the frame relay link between R1 and R2.
Configure EIGRP on R4 and over the X.25 link.

REDISTRIBUTION
Redistribute so that all routes, except the backbone networks, are visible on all routers.

ISDN
Configure the ISDN link between R2 and R3 as a backup for the frame relay network.

• R2 should call R3.

• Should the frame network go down all routes should still be visible on both R2 and R3.
• The link should come up for any network topology changes .

BGP
Configure BGP on R2.

• R2 should be in AS 2.
• There is a BGP router on Backbone 1. Its AS is 20 and its IP address is 160.100.2.20. R2 should
establish an EBGP session with this router.
• Filter on R2 so that the only routes accepted from R2 are routes that originated in AS 20.

Configure IBGP on R6 and R4.

• Both routers should be in AS 2.

• BGP should be synchronized.
• R6 should be peered with both R2 and R4.
• R4 should be peered only with R6. R2 should be peered only with R6 and the external router.
• R4 should see the routes from AS 20.
• Configure R2 so that it advertises the aggregate route 177.0.0.0 to the other routers in AS 2.

NTP
Configure Network Timing Protocol (NTP) on all routers and the Catalyst switch. The UNIX NTP server is
at 160.100.1.25, and its clock is synchronized for GMT. All clocks should read Central Standard Time
(CST).

HSRP
Configure HSRP for VLAN 25. If the switched ethernet connection to R3 goes down R6 should pick up the
connection and visa versa. Test your configuration by configuring the terminal server as a host, and
including its ethernet port in VLAN 25.
LAT
Configure a password protected LAT service called WSUSERV on R5.
• This service should display statistics for the X.25 serial interface on R5.
• Configure R6 so that it can use WSUSERV.
• LAT should be directly transported over X.25

FIREWALL
Configure R6 as a firewall between R4 and the rest of the network. Apply all access lists in on R6’s X.25
interface.

• All routing traffic should be permitted.

• NTP should still work through the firewall.
• The rest of the network should be able to ping R4.
• After it authenticates, with a password at R6, R4 should be able to trace-route and ping any router in
the network.
• All other IP traffic from R4 should be denied.

DLSW+
Configure DLSW+ between ring 1 and Back Bone 2.
• R1 should not have a remote peer statement.
• The connection should use TCP for transport. Make any changes necessary on the firewall.
• Configure DLSW+ for R6’s ethernet.
• R3 should have a peer connection to R4.
• If the LLC2 connection between R4 and R3 should go down R4 should setup a peer connection with
R6 so that bridging is no disrupted. When the connection between R3 and R4 is again established the
connection to R3 should be dropped.
• There are two Netbios hosts on Backbone 1, MOZART and BEETHOVEN. Filter so that R3 and R1
only see MOZART.

IPX
Configure IPX on each of the routers.

• Use RIP/SAP routing on all of R4’s interfaces, on the X.25 link, over the ISDN link and on Backbone
2.
• Use EIGRP on all other interfaces.
• All routes should be visible on all routers.
• The ISDN link should only come up periodically for routing updates.
• There are SAPs being advertised on Backbone 1, only allow IPXSERV1 to be seen by the rest of the
network.
• There is a router advertising routes on Backbone 2, allow only the network 0xECE to be seen by the
rest of the network.
• Novell hosts on Backbone 2 should not be able to learn about IPXSERV1, but any routers on Back
Bone 2 should still receive advertisements for IPXSERV1.
APPLETALK
Configure AppleTalk on all routers.

• Wherever possible use EIGRP as the routing protocol.

• Configure Ring 1 and Ring 2 in the same zone.
• Filter on R6, such that R4 sees the cable-ranges for Ring 1 and 2 but does not see their zone.