Section 1: Bridging and Switching (18 Points) | CCIE Routing and Switching Practice Labs

Section 1.1: Frame Relay Configuration (2 Points)

Configure the Frame Relay portion of the network as shown in Figure 6-8 and ensure that only the PVCs illustrated in Figure 6-8 will be used. Use of dynamic PVCs is not permitted.

The question clearly states that you must use only the PVCs as shown in Figure 6-8. You must, therefore, disable inverse ARP on the routers. It is good practice to ensure that all routers do not rely on inverse ARP, so you should have configured no frame-relay inverse-arp under R1, R2, R3, R4, and R5 on their serial interfaces.

If you configured this correctly in Example 6-1, you have scored 2 points.

You must use subinterfaces on R2 interface s0/1.
Do not configure subinterfaces on any other routers.
You must be able to ping across the Frame Relay cloud.

R2 will be connecting to R1, R4, and R5. Notice that a different subnet address exists on either side of the connection between R2 and R4. You should be able to ping across the Frame Relay cloud. Also notice that you "must" configure subinterfaces on R2.

If you configured this correctly as shown in Example 6-1 through Example 6-5, you have scored 3 points.

Example 6-6 through Example 6-10 show how to verify if your configuration is working properly.

NOTE

When configuring the Frame Relay serial interfaces, it is a very good idea for you to shut down the interfaces while you are configuring. This procedure will ensure you do not have unexpected behavior because of dynamic maps, and so on. Although you have configured no frame-relay inverse-arp, another useful command to use is clear frame-relay inarp interface, which clears your inverse ARP entries from the map table. Sometimes, you might also need to reload the router to remove dynamic maps.

Example 6-1. R1 Initial Frame Relay Solution Configuration

 R1#show run int s0/1 Building configuration... Current configuration : 285 bytes ! interface Serial0/1  ip address 160.10.37.1 255.255.255.0  encapsulation frame-relay  frame-relay map ip 160.10.37.2 112 broadcast  frame-relay map ip 160.10.37.5 112 broadcast  no frame-relay inverse-arp  frame-relay lmi-type ansi end R1#

Example 6-2. R2 Initial Frame Relay Solution Configuration

 R2#show run int s0/0 Building configuration... Current configuration : 193 bytes ! interface Serial0/0  ip address 160.10.32.2 255.255.255.252  encapsulation frame-relay  frame-relay map ip 160.10.32.1 203 broadcast  no frame-relay inverse-arp  frame-relay lmi-type ansi end R2# R2#show run int s0/1 Building configuration... Current configuration : 285 bytes ! interface Serial0/1  no ip address  encapsulation frame-relay  no frame-relay inverse-arp  frame-relay lmi-type ansi end ! interface Serial0/1.1 multipoint  ip address 160.10.37.2 255.255.255.0  frame-relay map ip 160.10.37.1 211 broadcast  frame-relay map ip 160.10.37.5 215 broadcast  end ! R2#sh run int s0/1.2 Building configuration... Current configuration : 117 bytes ! interface Serial0/1.2 point-to-point  ip address 160.10.38.2 255.255.255.0  frame-relay interface-dlci 214 end R2#

Example 6-3. R3 Initial Frame Relay Solution Configuration

 R3#show run int s0/0 Building configuration... Current configuration : 193 bytes ! interface Serial0/0  ip address 160.10.32.1 255.255.255.252  encapsulation frame-relay  frame-relay map ip 160.10.32.2 302 broadcast  no frame-relay inverse-arp  frame-relay lmi-type ansi end R3#

Example 6-4. R4 Initial Frame Relay Solution Configuration

 R4#show run int s0/1 Building configuration... Current configuration : 285 bytes ! interface Serial0/1  ip address 160.10.38.4 255.255.255.0  encapsulation frame-relay  frame-relay map ip 160.10.38.2 412 broadcast  no frame-relay inverse-arp  frame-relay lmi-type ansi end R4#

Example 6-5. R5 Initial Frame Relay Solution Configuration

 R5#show run int s0/1 Building configuration... Current configuration : 285 bytes ! interface Serial0/1  ip address 160.10.37.5 255.255.255.0  encapsulation frame-relay  frame-relay map ip 160.10.37.1 512 broadcast  frame-relay map ip 160.10.37.2 512 broadcast  no frame-relay inverse-arp  frame-relay lmi-type ansi end R5#

Example 6-6. R1 show Commands and Pings to Verify Functionality

 R1#show fram map Serial0/1 (up): ip 160.10.37.2 dlci 112(0x70,0x1C00), static,               broadcast,               CISCO, status defined, active Serial0/1 (up): ip 160.10.37.5 dlci 112(0x70,0x1C00), static,               broadcast,               CISCO, status defined, active R1# R1#ping 160.10.37.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 160.10.37.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms R1#ping 160.10.37.5 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 160.10.37.5, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 4/5/8 ms R1#

Example 6-7. R2 show Commands and Pings to Verify Functionality

 R2#show fram map Serial0/0 (up): ip 160.10.32.1 dlci 203(0xCB,0x30B0), static,               broadcast,               CISCO, status defined, active Serial0/1.1 (up): ip 160.10.37.1 dlci 211(0xD3,0x3430), static,               broadcast,               CISCO, status defined, active Serial0/1.1 (up): ip 160.10.37.5 dlci 215(0xD7,0x3470), static,               broadcast,               CISCO, status defined, active Serial0/1.2 (up): point-to-point dlci, dlci 214(0xD6,0x3460), broadcast           status defined, active R2# R2# R2#ping 160.10.32.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 160.10.32.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/3/4 ms R2#ping 160.10.37.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 160.10.37.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/3/4 ms R2#ping 160.10.37.5 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 160.10.37.5, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms R2# R2#ping 160.10.38.4 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 160.10.38.4, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/3/4 ms

Example 6-8. R3 show Commands and Pings to Verify Functionality

 R3#show fram map Serial0/0 (up): ip 160.10.32.2 dlci 302(0x12E,0x48E0), static,               broadcast,               CISCO, status defined, active R3#ping 160.10.32.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 160.10.32.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/3/4 ms R3#

Example 6-9. R4 show Commands and Pings to Verify Functionality

 R4#show fram map Serial0/1 (up): ip 160.10.38.2 dlci 412(0x19C,0x64C0), static,               broadcast,               CISCO, status defined, active R4# R4#ping 160.10.38.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 160.10.38.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 4/6/8 ms R4#

Example 6-10. R5 show Commands and Pings to Verify Functionality

 R5#show fram map R5#sh fram map Serial0/1 (up): ip 160.10.37.1 dlci 512(0x200,0x8000), static,               broadcast,               CISCO, status defined, active Serial0/1 (up): ip 160.10.37.2 dlci 512(0x200,0x8000), static,               broadcast,               CISCO, status defined, active R5# R5#ping 160.10.37.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 160.10.37.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 4/6/8 ms R5#ping 160.10.37.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 160.10.37.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/3/4 ms R5#

Section 1.2: 3550 LAN Switch Configuration (12 Points)

Sw1 and Sw2 are connected via a crossover cable using ports fa0/15 and fa0/17. Configure a Dot1q (801.1Q) trunk between Sw1 and Sw2.

If you configured this correctly as shown in Example 6-11 and Example 6-12, you have scored 1 point. Both show a basic trunk configuration. Example 6-13 verifies the configuration for both switches.

Example 6-11. 3550 Sw1 Initial Trunk Configuration

 Sw1#show run int fa0/15 Building configuration... Current configuration : 108 bytes ! interface FastEthernet0/15  switchport trunk encapsulation dot1q  switchport mode trunk  no ip address end Sw1# Sw1#show run int fa0/17 Building configuration... Current configuration : 108 bytes ! interface FastEthernet0/17  switchport trunk encapsulation dot1q  switchport mode trunk  no ip address end Sw1#

Example 6-12. 3550 Sw2 Initial Trunk Configuration

 Sw2#show run int fa0/15 Building configuration... Current configuration : 108 bytes ! interface FastEthernet0/15  switchport trunk encapsulation dot1q  switchport mode trunk  no ip address end Sw2# Sw2#show run int fa0/17 Building configuration... Current configuration : 108 bytes ! interface FastEthernet0/17  switchport trunk encapsulation dot1q  switchport mode trunk  no ip address end Sw2#

Example 6-13. 3550 Sw1 and Sw2 show Command Output to Verify Configuration and Functionality

 Sw1#show int trunk Port        Mode         Encapsulation  Status        Native vlan Fa0/15      on           802.1q         trunking      1 Fa0/17      on           802.1q         trunking      1 Port      Vlans allowed on trunk Fa0/15      1-4094 Fa0/17      1-4094 Port        Vlans allowed and active in management domain Fa0/15      1 Fa0/17      1 Port        Vlans in spanning tree forwarding state and not pruned Fa0/15      1 Fa0/17      1 Sw1# ________________________________________________________________ Sw2#show int trunk Port        Mode         Encapsulation  Status        Native vlan Fa0/15      on           802.1q         trunking      1 Fa0/17      on           802.1q         trunking      1 Port      Vlans allowed on trunk Fa0/15      1-4094 Fa0/17      1-4094 Port        Vlans allowed and active in management domain Fa0/15      1 Fa0/17      1 Port        Vlans in spanning tree forwarding state and not pruned Fa0/15      1 Fa0/17      none Sw2#

All Ethernet ports are pre-cabled as per Table 6-4. Note that not all ports will be used on this lab.
Configure the VLANs as follows:
- VLAN_11: Connected to R1-e0/0 (VLAN_11)

- VLAN_22: Connected to R3-fa0/0, R5-fa0/0, and R6-e0/0 (VLAN_22)

- VLAN_25: Connected to R1-e0/1 and R5-fa0/1 (VLAN_25)

- VLAN_33: Connected to R3-fa0/1 (VLAN_33)

- VLAN_100: Connected to R2-fa0/0 and BB1_Router-e2/0 (VLAN_100)

- VLAN_200: Connected to R4-e0/0 and BB2_Router-e2/4 (VLAN_200)

If you configured this correctly as shown in Example 6-14, you have scored 2 points.

Configure Sw1 to be the VTP server for the domain. Sw2 is a VTP client. Be sure that Sw2 can see the VLAN configuration from Sw1. The VTP domain name is "CISCO."

It is important to notice how VTP domains work. All VLAN configuration must be done on the VTP Server switch (Sw1) and then all information will be propagated to the VTP Client switch (Sw2), even though you do have some VLANs that will be only connected on Sw2. Notice the VTP domain name "CISCO" is a requirement and is case sensitive, so "CISCO" will be different than "CiSCO" and it will not work.

If you configured this correctly as shown in Example 6-14, you have scored 2 points.

NOTE

The VLAN configuration is completed under Vlan database.

Example 6-14. 3550 Sw1 and Sw2 VLAN and VTP Configuration

 Sw1#show vlan brief VLAN Name                             Status    Ports ---- -------------------------------- --------- ------------------------------- 1    default                          active    Fa0/7, Fa0/8, Fa0/9, Fa0/10                                                 Fa0/11, Fa0/12, Fa0/14, Fa0/16                                                 Fa0/17, Fa0/18, Fa0/19, Fa0/20                                                 Fa0/21, Fa0/22, Fa0/23, Fa0/24                                                 Gi0/1, Gi0/2 11   VLAN_11                          active    Fa0/1 22   VLAN_22                          active    Fa0/3, Fa0/5, Fa0/6 25   VLAN_25                          active 33   VLAN_33                          active 100  VLAN_100                         active    Fa0/2, Fa0/13 200  VLAN_200                         active    Fa0/4 1002 fddi-default                     active 1003 token-ring-default               active 1004 fddinet-default                  active 1005 trnet-default                    active Sw1# ________________________________________________________________ Sw2#show vlan brief VLAN Name                             Status    Ports ---- -------------------------------- --------- ------------------------------- 1    default                          active    Fa0/2, Fa0/4, Fa0/6, Fa0/7                                                 Fa0/8, Fa0/9, Fa0/10, Fa0/11                                                 Fa0/12, Fa0/14, Fa0/16, Fa0/17                                                 Fa0/18, Fa0/19, Fa0/20, Fa0/21                                                 Fa0/22, Fa0/23, Fa0/24, Gi0/1                                                 Gi0/2 11   VLAN_11                          active 22   VLAN_22                          active 25   VLAN_25                          active    Fa0/1, Fa0/5 33   VLAN_33                          active    Fa0/3 100  VLAN_100                         active 200  VLAN_200                         active    Fa0/13 1002 fddi-default                     active 1003 token-ring-default               active 1004 fddinet-default                  active 1005 trnet-default                    active Sw2# ________________________________________________________________ Sw1# Sw1#show vtp stat VTP Version                     : 2 Configuration Revision          : 1 Maximum VLANs supported locally : 1005 Number of existing VLANs        : 11 VTP Operating Mode              : Server VTP Domain Name                 : CISCO VTP Pruning Mode                : Disabled VTP V2 Mode                     : Disabled VTP Traps Generation            : Disabled MD5 digest                      : 0x36 0xC9 0xB9 0x93 0x5C 0xE6 0x7B 0x1D Configuration last modified by 160.10.7.7 at 3-19-93 04:55:23 Local updater ID is 160.10.11.10 on interface Vl11 (lowest numbered VLAN interface found) Sw1# ________________________________________________________________ Sw2#show vtp stat VTP Version                     : 2 Configuration Revision          : 1 Maximum VLANs supported locally : 1005 Number of existing VLANs        : 11 VTP Operating Mode              : Client VTP Domain Name                 : CISCO VTP Pruning Mode                : Disabled VTP V2 Mode                     : Disabled VTP Traps Generation            : Disabled MD5 digest                      : 0x36 0xC9 0xB9 0x93 0x5C 0xE6 0x7B 0x1D Configuration last modified by 160.10.7.7 at 3-19-93 04:55:23 Sw2#

NOTE

The VTP domain name must be called CISCO. It needs to be exactly as the question is asking for.

Configure Sw1, using VLAN_11 with the IP address 160.10.11.10/24. After you have finished all tasks related to the IGP section, all routers on your topology should be able to ping Sw1 VLAN_11 interface.

If you configured this correctly as shown in Example 6-15, you have scored 2 points.

Example 6-15. 3550 Sw1 Management Interface Configuration

 Sw1# Sw1#show run int vlan 11 Building configuration... Current configuration : 63 bytes ! interface Vlan11  ip address 160.10.11.10 255.255.255.0 ! !

NOTE

You are expected to have Sw1 reachable after you have your IGP routing section done. For example, R6 should be able to ping Sw1 interface VLAN_11.

Configure Sw2, using VLAN_33 with the IP address 160.10.33.10/24. After you have finished all tasks related to the IGP section, all routers on your topology should be able to ping Sw2 VLAN_33 interface. R3 also should be able to ping this interface.

If you configured this correctly as shown in Example 6-16, you have scored 2 points. Example 6-17 verifies the configuration.

NOTE

At this moment, Sw2 will be able to ping only R3-fa0/1, which is its default-gateway and is in the same VLAN_33. In fact, you are not required to reach the switches from other routers.

Example 6-16. 3550 Sw2 Management Interface Configuration

 Sw2# Sw2#sh run int vlan 33 Building configuration... Current configuration : 63 bytes ! interface Vlan33  ip address 160.10.33.10 255.255.255.0 end ! ! ip default-gateway 160.10.33.3 Sw2# !

Example 6-17. 3550 Sw2 Management Interface Output Verification (Sw2 Pinging R3-fa0/1)

 Sw2#ping 160.10.33.3 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 160.10.33.3, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms Sw2

Configure Sw1 and Sw2 such that you will have the traffic related to VLAN_100 pass primarily through fa0/15 trunk port and the traffic related to VLAN_200 pass primarily through fa0/17 trunk port. If one of the trunks should fail, the remaining trunk must carry all traffic.

The question is looking for a loading balance between the port trunks on Sw1 and Sw2 for VLAN_100 and VLAN_200. One possible solution is the use of spanning-tree vlan port-priority command, where you need to configure a smaller value on both sides (both trunks). You can also achieve the solution using the spanning-tree vlan cost command, where, in this case, the cost is to be changed to a smaller value on the "root" only. Pay attention to what is highlighted in the following example.

If you configured this correctly as shown in Example 6-18, you have scored 2 points.

Example 6-18. Sw1 and Sw2 spanning-tree vlan port-priority Configuration

 Sw1#sh run int fa0/15 Building configuration... Current configuration : 136 bytes ! interface FastEthernet0/15  switchport trunk encapsulation dot1q  switchport mode trunk  spanning-tree vlan 100 port-priority 16 end Sw1# Sw1#sh run int fa0/17 Building configuration... Current configuration : 136 bytes ! interface FastEthernet0/17  switchport trunk encapsulation dot1q  switchport mode trunk  spanning-tree vlan 200 port-priority 16 end ! Sw1#sh spanning-tree vlan 100 VLAN0100   Spanning tree enabled protocol ieee   Root ID    Priority    32868              Address     0009.e8ee.f200              Cost        19              Port        15 (FastEthernet0/15)              Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec   Bridge ID  Priority    32868  (priority 32768 sys-id-ext 100)              Address     0009.e8ef.1800              Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec              Aging Time 300 Interface        Role Sts Cost      Prio.Nbr Type ---------------- ---- --- --------- -------- -------------------------------- Fa0/2            Desg FWD 19        128.2    Shr Fa0/13           Desg FWD 100       128.13   Shr Fa0/15           Root FWD 19         16.15   P2p Fa0/17           Altn BLK 19        128.17   P2p Sw1# Sw1#sh spanning-tree vlan 200 VLAN0200   Spanning tree enabled protocol ieee   Root ID    Priority    32968              Address     0009.e8ee.f200              Cost        19              Port        17 (FastEthernet0/17)              Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec   Bridge ID  Priority    32968  (priority 32768 sys-id-ext 200)              Address     0009.e8ef.1800              Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec              Aging Time 300 Interface        Role Sts Cost      Prio.Nbr Type ---------------- ---- --- --------- -------- -------------------------------- Fa0/4            Desg FWD 100       128.4    Shr Fa0/15           Altn BLK 19        128.15   P2p Fa0/17           Root FWD 19         16.17   P2p Sw1# ! ! Sw2# Sw2#sh run int fa0/15 Building configuration... Current configuration : 136 bytes ! interface FastEthernet0/15  switchport trunk encapsulation dot1q  switchport mode trunk  spanning-tree vlan 100 port-priority 16 end Sw2# Sw2#sh run int fa0/17 Building configuration... Current configuration : 136 bytes ! interface FastEthernet0/17  switchport trunk encapsulation dot1q  switchport mode trunk  spanning-tree vlan 200 port-priority 16 end Sw2# Sw2#sh spanning-tree vlan 100 VLAN0100   Spanning tree enabled protocol ieee   Root ID    Priority    32868              Address     0009.e8ee.f200              This bridge is the root              Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec   Bridge ID  Priority    32868  (priority 32768 sys-id-ext 100)              Address     0009.e8ee.f200              Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec              Aging Time 300 Interface        Role Sts Cost      Prio.Nbr Type ---------------- ---- --- --------- -------- -------------------------------- Fa0/15           Desg FWD 19         16.15   P2p Fa0/17           Desg FWD 19        128.17   P2p Sw2# Sw2#sh spanning-tree vlan 200 VLAN0200   Spanning tree enabled protocol ieee   Root ID    Priority    32968              Address     0009.e8ee.f200              This bridge is the root              Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec   Bridge ID  Priority    32968  (priority 32768 sys-id-ext 200)              Address     0009.e8ee.f200              Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec              Aging Time 300 Interface        Role Sts Cost      Prio.Nbr Type ---------------- ---- --- --------- -------- -------------------------------- Fa0/13           Desg FWD 100       128.13   Shr Fa0/15           Desg FWD 19        128.15   P2p Fa0/17           Desg FWD 19         16.17   P2p Sw2#

You have high-priority traffic running on VLAN_22 between routers R3, R5, and R6. Configure Sw1 such that the ports connected to these routers will wait eight seconds before changing from learning state to forwarding state.

Configure the forward-delay feature so that you can change the wait delay time from learning to forward state. The default delay is 15 seconds. The use of the portfast feature does not apply here because you are still having the ports going through all states. The portfast feature will make a port go from blocking state to the forward state immediately, bypassing the listening and the learning states.

If you configured this correctly as shown in Example 6-19, you have scored 2 points.

Example 6-19. 3550 Sw1 forward-delay Configuration

 Sw1#sh run Building configuration... Current configuration : 2944 bytes ! version 12.1 no service pad ! hostname Sw1 ! spanning-tree vlan 22 forward-time 8 !

Section 1.3: ATM Configuration (4 Points)

Configure the ATM connection as shown in Figure 6-9.
A PVC is configured between R6 and the backbone router. Configure your router to communicate with the BB router. Do not configure subinterfaces.
Use explicit address mapping. Do not depend on the remoter backbone router for inverse ARP.
You must be able to ping the backbone router address 170.100.10.254.

If you configured this correctly as shown in Example 6-20, you have scored 2 points.

Example 6-20. R6 ATM Configuration, Map Verification, and Access to Backbone Router

 R6#show run int a3/0 Building configuration... Current configuration : 140 bytes ! interface ATM3/0  ip address 170.100.10.1 255.255.255.0  no atm ilmi-keepalive  pvc 0/100   protocol ip 170.100.10.254 broadcast  ! end R6#ping 170.100.10.254 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 170.100.10.254, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms R6#show atm vc            VCD /                                        Peak  Avg/Min Burst Interface  Name         VPI   VCI  Type   Encaps   SC   Kbps   Kbps   Cells  Sts 3/0        3              0   100  PVC    SNAP     UBR  155000                UP R6#

You have users on Backbone 3 using an application that requires a 512-kbps Input Peak Cell Rate. Configure your ATM interface to guarantee this requirement.

You have a UBR service on the ATM interface and you will need to create an ATM class to apply the PCR required. You need to define a VC Class and apply within the interface using the command class-int.

If you configured this correctly as shown in Example 6-21, you have scored 2 points.

Example 6-21. ATM Class for UBR Configuration

 R6#sh run ! ! hostname R6 ! ! vc-class atm UBR   ubr 155000 512 ! R6#sh run int a3/0 Building configuration... Current configuration : 155 bytes ! interface ATM3/0  ip address 170.100.10.1 255.255.255.0  class-int UBR  no atm ilmi-keepalive  pvc 0/100   protocol ip 170.100.10.254 broadcast  ! end R6#