Lab 2

Configuring Virtual Routers

and Bridged 1483

Overview

Description
In this lab, we will add an additional ATM PVC using Bridged 1483
encapsulation. To emulate the client environment, we will configure
virtual routers. One virtual router will provide the BRAS Server
functionality, one virtual router will emulate the Bridged 1483 Client. We
will configure an ATM PVC between the Bridged 1483 client and the BRAS
server.

Objectives
After completing this lab, you will be able to do the following:
• Create a virtual router
• Configure a T3/E3 Controller
• Configure a ATM interface with Bridged 1483 encapsulation
unnumbered IP
• Configure a static route to provide IP connectivity
• Use the show commands to troubleshoot and verify the configuration

Rev. 3.2 2-1

Configuring Virtual Routers
and Bridged 1483 Lab 2

Logical Network Map

ERX1 / ERX3 ERX2 / ERX4

ERX5 / ERX7 ERX6 / ERX8 “Internet”
U
IP U 30.30.0.0
Bridged 1483 Loopback 3
Client ATM Server

Client Network
Internet IP 10.10.0.0
Default Default
50.50.0.0 (Server) (Client) Loopback 2
ATM
Loopback 3

Client Network
IP IP
20.20.0.0
Loopback 3

2-2 Rev. 3.2 ERX B-RAS Configuration Basics

Lab 2 Bridged 1483 Configuration

Physical Network Map – Tear this page out!

ERX1/ERX3/ERX5/ERX7 ERX2/ERX4/ERX6/ERX8
UT3 or UT3 or
UE3 UE3
Client Slot ___ Slot ___ Server
0 0 Loopback 1= 182.10.1.1/24
Loopback 2= 30.30.30.30/24
182.10.1.2/24 1 1 Unnumbered IP
Loopback 1
ATM Subinterface 34
2 2
PVC 34 0 34

default (Server) PVC 33 0 33

default (Client)
ATM Subinterface 33
Unnumbered IP 172.10.1.2/24
Loopback 1
Loopback 1=192.168.1.1/24 Loopback1=192.168.16.1/24
Loopback 2 = 172.10.1.1/24 Loopback2 = 10.10.10.10/24
Loopback 3= 50.50.50.50/24 Loopback3 = 20.20.20.20/24
10.13.7.11, 13, 15, 17/24 10.13.7.12, 14, 16, 18/24

SRP SRP
Slot ___
0 0 Slot ___

For Training Purposes Only Rev. 3.2 2-3

Configuring Virtual Routers
and Bridged 1483 Lab 2

Logical Network Map – Tear this page out!

ERX1 / ERX3 ERX2 / ERX4

ERX5 / ERX7 ERX6 / ERX8 “Internet”
U
IP U 30.30.0.0
Bridged 1483 Loopback 3
Client ATM Server

Client Network
Internet IP 10.10.0.0
Default Default
50.50.0.0 (Server) (Client) Loopback 2
ATM
Loopback 3

Client Network
IP IP
20.20.0.0
Loopback 3

2-4 Rev. 3.2 ERX B-RAS Configuration Basics

Lab 2 Bridged 1483 Configuration

Physical Network Map

ERX1/ERX3/ERX5/ERX7 ERX2/ERX4/ERX6/ERX8
UT3 or UT3 or
UE3 UE3
Client Slot ___ Slot ___ Server
0 0 Loopback 1= 182.10.1.1/24
Loopback 2= 30.30.30.30/24
182.10.1.2/24 1 1 Unnumbered IP
Loopback 1
ATM Subinterface 34
2 2
PVC 34 0 34

default (Server) PVC 33 0 33

default (Client)
ATM Subinterface 33
Unnumbered IP 172.10.1.2/24
Loopback 1
Loopback 1=192.168.1.1/24 Loopback1=192.168.16.1/24
Loopback 2 = 172.10.1.1/24 Loopback2 = 10.10.10.10/24
Loopback 3= 50.50.50.50/24 Loopback3 = 20.20.20.20/24
10.13.7.11, 13, 15, 17/24 10.13.7.12, 14, 16, 18/24

SRP SRP
Slot ___
0 0 Slot ___

For Training Purposes Only Rev. 3.2 2-5

Configuring Virtual Routers
and Bridged 1483 Lab 2

Bridged 1483 Configuration

Getting Started
1. Power on the ERX.
2. Verify that all default router IP interfaces are operational from Lab 1.
3. Determine which virtual routers are currently configured using the
show virtual-router command.

Configuring a New Virtual Router

Using the network map as a reference, create a new virtual router, Client
or Server. Remember that layer 1 and layer 2 configuration information
is box-wide, but layer 3 information (IP Interfaces, IP routing tables, etc.)
is specific to a virtual router. In this lab while we are still learning, we will
configure all layers in the specific virtual router.
1. Enter configuration terminal mode.
2. Create the new virtual router. Remember that virtual router names
can not be abbreviated and are case sensitive.

♦ What happened to the prompt?_________________________________

_____________________________________________________________

♦ Which virtual router are you configuring at this point in time?

_____________________________________________________________

3. Exit configuration mode. Notice that you remain in the new virtual
router. Any privileged user commands performed now are for this new
virtual router.
4. Determine which virtual routers are currently configured using the
show virtual-router command.

♦ Are there any IP interfaces configured in the new virtual router?

_____________________________________________________________

♦ Are there any ATM VCs configured in the new virtual router?

_____________________________________________________________

Remember that Layer 1 and Layer 2 are box-wide and Layer 3 is

specific to the virtual router. Therefore, there should be 1 IP

2-6 Rev. 3.2 ERX B-RAS Configuration Basics

Lab 2 Bridged 1483 Configuration

Interface created (the NULL interface) and 1 ATM PVC, which was
configured in the previous lab exercise.

Initial Configuration on the SERVER Virtual Router

1. Enter configuration terminal mode.

2. On the SERVER virtual router:

a. Configure the Loopback 1 interface in the new virtual router using
the IP addresses and subnet masks found on the network map.
b. Configure a description for the Loopback 1 interface. For example,
configure the description Ref Unnumbered ATM Intf.
c. Configure the Loopback 2 address. This address will represent a
remote network in the Internet.
d. Configure a description for the Loopback 2 interface. For example,
configure the description Remote Net in Internet.

Configuring the UT3A/UE3A for ATM and IP

1. Configure the ATM subinterface using the subinterface number found
on the network map.
2. Configure the ATM PVC using the VCD, VPI and VCI found on the
network map. Specify aal5snap encapsulation.
3. Configure the ATM PVC for Bridged 1483 encapsulation.
4. On the CLIENT virtual router, assign the IP address and subnet mask
to the PVC found on the network map. Configure a description,
specifying the name of the ERX at the other end of the PVC, such as
SERVER ERX2.
5. On the SERVER virtual router, configure an unnumbered IP Interface
referencing the loopback 1 interface. Configure a description,
specifying the name of the ERX at the other end of the PVC, such as
CLIENT ERX1.
6. Exit out of configuration mode.

For Training Purposes Only Rev. 3.2 2-7

Configuring Virtual Routers
and Bridged 1483 Lab 2

Verifying the ATM PVC

Please work closely with your peer router during the next few
sections of the lab.

1. Examine the IP interfaces in the new virtual router using the show ip
interface brief command.

♦ Which IP Interfaces are listed in the new virtual router?

_____________________________________________________________

♦ Which IP interfaces are NOT listed in the new virtual router?

_____________________________________________________________

♦ Can you ping the IP addresses in the original Client/Server

configuration, for example 172.10.1.1 or 172.10.1.2?

_____________________________________________________________

♦ Which ATM PVCs are configured?

_____________________________________________________________

2. Switch to the default virtual router.

♦ Which IP Interfaces are listed in the default virtual router?

_____________________________________________________________

♦ Which IP interfaces are NOT listed in the default virtual router?

_____________________________________________________________

♦ Can you ping the IP addresses in the new Client/Server

configuration, for example 182.10.1.1 or 182.10.1.2?

_____________________________________________________________

♦ Which ATM PVCs are configured?

_____________________________________________________________

2-8 Rev. 3.2 ERX B-RAS Configuration Basics

Lab 2 Bridged 1483 Configuration

3. Switch back to the new CLIENT or SERVER virtual router.

4. On the SERVER, ping the IP address of the client.

♦ Is the ping successful? ________________________________________

_____________________________________________________________

♦ Were any ATM cells transmitted or received? Use the show atm
vc atm slot/port vcd command.

_____________________________________________________________

♦ Were any IP packets transmitted and received on the IP interface?

Use the show ip interface atm slot/port.subinterface command.

_____________________________________________________________

5. On the CLIENT, ping the Server.

♦ Which IP address should be used? _____________________________

_____________________________________________________________

♦ Can you ping the server’s loopback interface that resides in the
same subnet as your ATM interface?

_____________________________________________________________

♦ Were any ATM cells transmitted or received? Use the show atm
vc atm slot/port vcd command.

_____________________________________________________________

♦ Were any IP packets transmitted and received on the IP interface?

Use the show ip interface atm slot/port.subinterface command.

_____________________________________________________________

For Training Purposes Only Rev. 3.2 2-9

Configuring Virtual Routers
and Bridged 1483 Lab 2

6. On both the SERVER and the CLIENT, examine the IP routing table.

♦ On the SERVER, is there a route to IP address you were trying to

ping?

_____________________________________________________________

♦ What is the next hop?

_____________________________________________________________

At this point, the Server is unable to ping the Client. The Server
does not have a specific route to the Client’s IP address. At this
point, the Server has a route to the entire network, but the next hop
address is the Server’s Loopback Interface. The Server does not
know where to send the IP packets destined for the Client.
Therefore, ATM cells and IP packets are not transmitted or
received.

♦ On the CLIENT, is there a route to IP address you were trying to

ping?

_____________________________________________________________

♦ What is the next hop?

_____________________________________________________________

At this point, the Client is unable to ping the Server, but for a very
different reason. The Client does have a route to the Server’s
Loopback IP address and the next hop is the appropriate ATM
interface. The Client transmits the ping packets out the
appropriate ATM interface. When the Server attempts to reply to
the pings, the Server does not know where to send the IP packets
destined for the Client. Therefore, on the Client, ATM cells and IP
packets are transmitted but not received.

2-10 Rev. 3.2 ERX B-RAS Configuration Basics

Lab 2 Bridged 1483 Configuration

7. On the CLIENT, ping the Server’s ‘remote’ network (30.30.30.30).

♦ Is the ping successful? ________________________________________

_____________________________________________________________

♦ Were any ATM cells transmitted or received? Remember to use the

baseline int commands.

_____________________________________________________________

♦ Were any IP packets transmitted and received on the IP interface?

Remember to use the clear ip interface commands.

_____________________________________________________________

♦ Do you have a route to this network in your routing table?

_____________________________________________________________

♦ Does the SERVER router have a route back to you?

_____________________________________________________________

Since the Client does not have a route to the network, the Client
does not know where to transmit the IP packets. Therefore, ATM
cells and IP packets are not transmitted or received.

For Training Purposes Only Rev. 3.2 2-11

Configuring Virtual Routers
and Bridged 1483 Lab 2

Configuring and Testing Static Routes

1. On the CLIENT, DO NOT CONTINUE until the SERVER has

completed the following step!

2. On the SERVER, configure an IP static host route to the client’s host

address, specifying the appropriate ATM interface as the next hop.

♦ Can the Server ping the client’s host address now?

_____________________________________________________________

♦ Can the Client ping the server’s loopback 1 address now?

_____________________________________________________________

♦ Were any ATM cells transmitted or received? Remember to take

advantage of the baseline int commands.

_____________________________________________________________

♦ Were any IP packets transmitted and received on the IP interface?

Remember to take advantage of the clear ip interface commands.

_____________________________________________________________

At this point, the Server should be able to ping the Client. The
Server should have a specific route to the Client’s IP address and
the Client has a route to the server. On both the Server and the
Client, ATM cells and IP packets should be transmitted and
received.

2-12 Rev. 3.2 ERX B-RAS Configuration Basics

Lab 2 Bridged 1483 Configuration

♦ Can the Client ping the “remote” network (30.30.30.30)?

_____________________________________________________________

♦ Were any ATM cells transmitted or received? ___________________

_____________________________________________________________

♦ Were any IP packets transmitted and received on the IP interface?

_____________________________________________________________

♦ Do you have a route to these networks in your routing table?

_____________________________________________________________

The Client does not have a route to any ‘remote’ networks.

Therefore, the client does not know where to transmit the IP
packets. Therefore, ATM cells and IP packets are not transmitted
or received.

3. On the CLIENT, configure a default route using Server’s Loopback 1

IP address as the next hop.

4. Verify that all networks are reachable.

5. Save the running configuration as br1483.cnf.

For Training Purposes Only Rev. 3.2 2-13

Configuring Virtual Routers
and Bridged 1483 Lab 2

Sample Configuration Steps – Server

erx2#show vir
Virtual Router : default
erx2#config t
Enter configuration commands, one per line. End with CNTL/Z.
erx2(config)#virtual-router server
Proceed with new virtual-router creation? [confirm]

erx2:server(config)#
erx2:server(config)#exit
erx2:server#show vir
Virtual Router : default
Virtual Router : server
erx2:server#show ip int bri
Interface IP-Address Status Protocol Description
null0 255.255.255.255/32 up up
erx2:server#show atm vc
Interface VCD VPI VCI Type Encap Peak Avg Burst InArp Status
---------- --- --- --- ---- --------- ---- --- ----- ----- ------
ATM 5/2.33 33 0 33 PVC AAL5-SNAP 0 0 0 No UP

erx2:server#config t
Enter configuration commands, one per line. End with CNTL/Z.
erx2:server(config)#interface loop 1
erx2:server(config-if)#ip add 182.10.1.1 255.255.255.0
erx2:server(config-if)#description ref unnumbered int
erx2:server(config-if)#interface loopback 2
erx2:server(config-if)#ip address 30.30.30.30 255.255.255.0
erx2:server(config-if)#desc remote internet network
erx2:server(config-if)#exit
erx2:server(config)#int atm 5/2.34
erx2:server(config-subif)#atm pvc 34 0 34 aal5snap
erx2:server(config-subif)#encapsulation ?
bridge1483 Specify bridge1483 encapsulation
hdlc Specify Cisco-HDLC encapsulation
ppp Specify PPP encapsulation
pppoe Use PPPoe interface encapsulation
vlan Specify VLAN encapsulation

erx2:server(config-subif)#encapsulation bridge1483
erx2:server(config-subif)#ip unnumbered loopback 1
erx2:server(config-subif)#description Client ERX1
erx2:server(config-subif)#exit
erx2:server(config)#exi
erx2:server#
erx2:server#show ip int bri
Interface IP-Address Status Protocol Description
null0 255.255.255.255/32 up up
loopback1 182.10.1.1/24 up up ref unnumbered int
loopback2 30.30.30.30/24 up up remote internet
netw...
2-14 Rev. 3.2 ERX B-RAS Configuration Basics
Lab 2 Sample Configuration Steps – Server

atm5/2.34 Unnumbered up up Client ERX1

erx2:server#ping 172.10.1.1
Sending 5 ICMP echos to 172.10.1.1, timeout = 2 sec.
.....
Success rate = 0% (0/5), round-trip min/avg/max = 0/0/0 ms
erx2:server#show atm vc
Interface VCD VPI VCI Type Encap Peak Avg Burst InArp Status
---------- --- --- --- ---- --------- ---- --- ----- ----- ------
ATM 5/2.33 33 0 33 PVC AAL5-SNAP 0 0 0 No UP
ATM 5/2.34 34 0 34 PVC AAL5-SNAP 0 0 0 No UP

erx2:server#vir default
erx2#show ip int bri
Interface IP-Address Status Protocol Description
null0 255.255.255.255/32 up up
fastEthernet0/0 10.13.7.12/24 up up mgmtEnet
loopback1 192.168.16.1/24 up up
loopback2 10.10.10.10/24 up up
loopback3 20.20.20.20/24 up up
atm5/2.33 172.10.1.2/24 up up
erx2#ping 192.10.1.2
Sending 5 ICMP echos to 192.10.1.2, timeout = 2 sec.
NNNNN
Success rate = 0% (0/5), round-trip min/avg/max = 0/0/2 ms
erx2#show atm vc
Interface VCD VPI VCI Type Encap Peak Avg Burst InArp Status
---------- --- --- --- ---- --------- ---- --- ----- ----- ------
ATM 5/2.33 33 0 33 PVC AAL5-SNAP 0 0 0 No UP
ATM 5/2.34 34 0 34 PVC AAL5-SNAP 0 0 0 No UP

erx2#vir server
erx2:server#ping 182.10.1.2
Sending 5 ICMP echos to 182.10.1.2, timeout = 2 sec.
.....
Success rate = 0% (0/5), round-trip min/avg/max = 0/0/0 ms
erx2:server#show atm vc atm 5/2 33
ATM 5/2.33: VCD: 33, VPI: 0, VCI: 33, Encap: AAL5-SNAP
Service Type: Ubr
Inverse ARP enable: No
InPackets: 44
InBytes: 5624
InCells: 128
OutPackets: 49
OutBytes: 6664
OutCells: 15
InErrors: 1
OutErrors: 0
InPacketDiscards: 0
InByteDiscards: 0
CrcErrors: 0
SAR time-outs: 0
Over-sized SDUs: 0

For Training Purposes Only Rev. 3.2 2-15

Configuring Virtual Routers
and Bridged 1483 Lab 2

OAM VC verification: disabled

OAM VC status: not managed
InOamF5Cells: 0
InOamCellDiscards: 0
InF5EndLoopCells: 0
InF5SegLoopCells: 0
InF5AisCells: 0
InF5RdiCells: 0
OutOamF5Cells: 0
OutF5EndLoopCells: 0
OutF5SegLoopCells: 0
OutF5RdiCells: 0
Circuit is UP, time since last change: 00:24:18
erx2:server#show ip route
Protocol/Route type codes:
I1- ISIS level 1, I2- ISIS level2,
I- route type intra, IA- route type inter, E- route type external,
i- metric type internal, e- metric type external,
O- OSPF, E1- external type 1, E2- external type2,
N1- NSSA external type1, N2- NSSA external type2

Prefix/Length Type Next Hop Dist/Met Intf

------------------ ------- --------------- -------------- -----------------
---
30.30.30.0/24 Connect 30.30.30.30 0/1 loopback2
182.10.1.0/24 Connect 182.10.1.1 0/1 loopback1

erx2:server#show atm vc 5/2 34

^
% Invalid input detected at '^' marker.
erx2:server#show atm vc atm 5/2 34
ATM 5/2.34: VCD: 34, VPI: 0, VCI: 34, Encap: AAL5-SNAP
Service Type: Ubr
Inverse ARP enable: No
InPackets: 0
InBytes: 0
InCells: 0
OutPackets: 0
OutBytes: 0
OutCells: 0
InErrors: 0
OutErrors: 0
InPacketDiscards: 0
InByteDiscards: 0
CrcErrors: 0
SAR time-outs: 0
Over-sized SDUs: 0
OAM VC verification: disabled
OAM VC status: not managed
InOamF5Cells: 0
InOamCellDiscards: 0
InF5EndLoopCells: 0

2-16 Rev. 3.2 ERX B-RAS Configuration Basics

Lab 2 Sample Configuration Steps – Server

InF5SegLoopCells: 0
InF5AisCells: 0
InF5RdiCells: 0
OutOamF5Cells: 0
OutF5EndLoopCells: 0
OutF5SegLoopCells: 0
OutF5RdiCells: 0
Circuit is UP, time since last change: 00:03:47
erx2:server#show atm vc atm 5/2 34
ATM 5/2.34: VCD: 34, VPI: 0, VCI: 34, Encap: AAL5-SNAP
Service Type: Ubr
Inverse ARP enable: No
InPackets: 2
InBytes: 140
InCells: 4
OutPackets: 0
OutBytes: 0
OutCells: 0
InErrors: 0
OutErrors: 0
InPacketDiscards: 0
InByteDiscards: 0
CrcErrors: 0
SAR time-outs: 0
Over-sized SDUs: 0
OAM VC verification: disabled
OAM VC status: not managed
InOamF5Cells: 0
InOamCellDiscards: 0
InF5EndLoopCells: 0
InF5SegLoopCells: 0
InF5AisCells: 0
InF5RdiCells: 0
OutOamF5Cells: 0
OutF5EndLoopCells: 0
OutF5SegLoopCells: 0
OutF5RdiCells: 0
Circuit is UP, time since last change: 00:04:02
erx2:server#show ip route
Protocol/Route type codes:
I1- ISIS level 1, I2- ISIS level2,
I- route type intra, IA- route type inter, E- route type external,
i- metric type internal, e- metric type external,
O- OSPF, E1- external type 1, E2- external type2,
N1- NSSA external type1, N2- NSSA external type2

Prefix/Length Type Next Hop Dist/Met Intf

------------------ ------- --------------- -------------- -----------------
---
30.30.30.0/24 Connect 30.30.30.30 0/1 loopback2
182.10.1.0/24 Connect 182.10.1.1 0/1 loopback1

For Training Purposes Only Rev. 3.2 2-17

Configuring Virtual Routers
and Bridged 1483 Lab 2

erx2:server#config t
Enter configuration commands, one per line. End with CNTL/Z.
erx2:server(config)#ip route 182.10.1.2 255.255.255.255 atm 5/2.34
erx2:server(config)#^Z
erx2:server#ping 182.10.1.2
Sending 5 ICMP echos to 182.10.1.2, timeout = 2 sec.
.!!!!
Success rate = 80% (4/5), round-trip min/avg/max = 2/2/3 ms
erx2:server#show ip route
Protocol/Route type codes:
I1- ISIS level 1, I2- ISIS level2,
I- route type intra, IA- route type inter, E- route type external,
i- metric type internal, e- metric type external,
O- OSPF, E1- external type 1, E2- external type2,
N1- NSSA external type1, N2- NSSA external type2

Prefix/Length Type Next Hop Dist/Met Intf

------------------ ------- --------------- -------------- -----------------
---
30.30.30.0/24 Connect 30.30.30.30 0/1 loopback2
182.10.1.0/24 Connect 182.10.1.1 0/1 loopback1
182.10.1.2/32 Static 0.0.0.0 1/0 atm5/2.34

erx2:server#show atm vc atm 5/2 34

ATM 5/2.34: VCD: 34, VPI: 0, VCI: 34, Encap: AAL5-SNAP
Service Type: Ubr
Inverse ARP enable: No
InPackets: 11
InBytes: 1098
InCells: 30
OutPackets: 5
OutBytes: 678
OutCells: 18
InErrors: 0
OutErrors: 0
InPacketDiscards: 0
InByteDiscards: 0
CrcErrors: 0
SAR time-outs: 0
Over-sized SDUs: 0
OAM VC verification: disabled
OAM VC status: not managed
InOamF5Cells: 0
InOamCellDiscards: 0
InF5EndLoopCells: 0
InF5SegLoopCells: 0
InF5AisCells: 0
InF5RdiCells: 0
OutOamF5Cells: 0
OutF5EndLoopCells: 0
OutF5SegLoopCells: 0
OutF5RdiCells: 0

2-18 Rev. 3.2 ERX B-RAS Configuration Basics

Lab 2 Sample Configuration Steps – Server

Circuit is UP, time since last change: 00:06:02

erx2:server#baseline ?
aaa Set a baseline for AAA statistics
clns Set a baseline for CLNS statistics
dhcp Set DHCP related baseline
frame-relay Set a baseline for frame relay statistics
hdlc Set a baseline for Cisco-HDLC statistics
interface Specify a interface
ip Set a baseline for IP statistics
local Set a baseline for Local Address assignment
ppp Set a baseline for ppp statistics
pppoe Set a baseline for pppoe statistics
radius Set a baseline for RADIUS statistics
snmp Set a baseline for SNMP statistics

For Training Purposes Only Rev. 3.2 2-19

Configuring Virtual Routers
and Bridged 1483 Lab 2

Sample Configuration File – Server

erx2:server#show config
! Unisphere Edge Routing Switch ERX-700
! Version: 3.0.2 patch-2.0 (April 2, 2001 15:52)
! Copyright (c) 1999,2000 Unisphere Networks, Inc. All rights reserved.
!
! Configuration script generated on TUE MAY 29 2001 15:19:49 UTC
boot config running-configuration
boot system 3-0-2p2.rel
no boot backup
no boot subsystem
no boot backup subsystem
no boot force-backup
no boot slot
!
hostname erx2
exception protocol ftp anonymous null
!
controller t3 5/0
controller t3 5/1
controller t3 5/2
no shutdown
clock source internal chassis
!
controller t3 4/0
controller t3 4/1
controller t3 4/2
controller sonet 6/0
!
controller sonet 6/1
!
!
line console 0
line vty 0
no login
!
line vty 1
no login
!
line vty 2
no login
!
line vty 3
no login
!
line vty 4
no login
!
log engineering
log verbosity low
2-20 Rev. 3.2 ERX B-RAS Configuration Basics
Lab 2 Sample Configuration File – Server

no log engineering
log fields timestamp instance no-calling-task
!
timing source primary line t1:a
timing source secondary line t1:b
!
slot enable 0
slot enable 3
slot enable 4
slot enable 5
slot enable 6
!
profile default
virtual-router default
interface null 0
interface loopback 1
ip address 192.168.16.1 255.255.255.0
!
interface loopback 2
ip address 10.10.10.10 255.255.255.0
!
interface loopback 3
ip address 20.20.20.20 255.255.255.0
!
interface atm 5/2
no shutdown
atm clock internal chassis
!
interface atm 5/2.33 point-to-point
atm pvc 33 0 33 aal5snap 0 0 0
ip address 172.10.1.2 255.255.255.0
!
interface fastEthernet 0/0
description mgmtEnet
ip address 10.13.7.12 255.255.255.0
!
interface fastEthernet 3/0
!
interface fastEthernet 3/1
!
ip route 0.0.0.0 0.0.0.0 atm5/2.33
! Trap Source: <not configured>
! Note: SNMP server not running.
!
virtual-router server
interface null 0
interface loopback 1
description ref unnumbered int
ip address 182.10.1.1 255.255.255.0
!
interface loopback 2
description remote internet network

For Training Purposes Only Rev. 3.2 2-21

Configuring Virtual Routers
and Bridged 1483 Lab 2

ip address 30.30.30.30 255.255.255.0

!
interface atm 5/2.34 point-to-point
atm pvc 34 0 34 aal5snap 0 0 0
encapsulation bridge1483
description Client ERX1
ip unnumbered loopback 1
ip proxy-arp
!
ip route 182.10.1.2 255.255.255.255 atm5/2.34
ip bgp-community new-format
no ip source-route
! Trap Source: <not configured>
! Note: SNMP server not running.
!

2-22 Rev. 3.2 ERX B-RAS Configuration Basics