2.7.2 Packet Tracer - Configure Single-Area OSPFv2 - Physical Mode Answers
Topology
Addressing Table
| Device | Interface | IP Address | Subnet Mask | Default Gateway |
|---|---|---|---|---|
| R1 | G0/0/1 | 10.53.0.1 | 255.255.255.0 | n/a |
| G0/0/0 | 172.16.1.1 | 255.255.255.0 | n/a | |
| R2 | G0/0/1 | 10.53.0.2 | 255.255.255.0 | n/a |
| G0/0/0 | 192.168.1.1 | 255.255.255.0 | n/a | |
| Web Server | F0 | 172.16.1.10 | 255.255.255.0 | 172.16.1.1 |
| Laptop | F0 | 192.168.1.10 | 255.255.255.0 | 192.168.1.1 |
Objectives
- Part 1: Build the Network and Configure Basic Device Settings
- Part 2: Configure and Verify Single-Area OSPFv2 for Basic Operation
- Part 3: Optimize and Verify the Single-Area OSPFv2 Configuration
Background / Scenario
You have been tasked with configuring a small company’s network using OSPFv2. R1 will share the default route information to R2. After the initial configuration, the organization has asked for the configuration to be optimized to reduce protocol traffic and ensure that R1 remains in control of routing.
Note: The equipment required for this activity is located in the wiring closet on the utility shelf.
Instructions
Part 1: Build the Network and Configure Basic Device Settings
Step 1: Cable the network as shown in the topology.
Place the required devices on the rack and the table. Power on the PCs and cable the devices according to the topology. To select the correct port on a switch, right click and select Inspect Front. Use the Zoom tool, if necessary. Float your mouse over the ports to see the port numbers. Packet Tracer will score the correct cable and port connections.
a. There are several switches, routers, and other devices on the Shelf. Click and drag the routers R1 and R2 and the switches S1 and S2 to the Rack. Click and drag the Web Server to the Rack. Click and drag the Laptop to the Table.
b. Power on the routers and the laptop.
c. On the Cable Pegboard, click a Copper Straight-Through cable. Click the GigabitEthernet0/1 port on S1 and then click the GigabitEthernet0/0/1 port on R1 to connect them.
d. On the Cable Pegboard, click a Copper Straight-Through cable. Click the GigabitEthernet0/1 port on S2 and then click the GigabitEthernet0/0/1 port on R2 to connect them.
e. On the Cable Pegboard, click a Copper Cross-Over cable. Click the GigabitEthernet0/2 port on S1 and then click the GigabitEthernet0/2 port on S2 to connect them. You should see the cable connecting the two ports.
f. On the Cable Pegboard, click a Copper Straight-Through cable. Click the GigabitEthernet0/0/0 port on R1 and then click the FastEthernet0 port on the Web Server to connect them.
g. On the Cable Pegboard, click a Copper Straight-Through cable. Click the GigabitEthernet0/0/0 port on R2 and then click the FastEthernet0 port on the Laptop to connect them.
Visually inspect network connections. Initially, when you connect devices to a switch port, the link lights will be amber. After a minute or so, the link lights will turn green.
Step 2: Configure basic settings for the two routers and two switches.
a. On the Cable Pegboard, click a Console cable.
b. Connect the console cable between the device and the Laptop. For the switches, Inspect Rear to locate the Console port.
c. Assign a name to the device according to the Topology.
Router(config)# hostname R1
d. Disable DNS lookup to prevent the router from attempting to translate incorrectly entered commands as though they were host names.
R1(config)# no ip domain–lookup
e. Assign class as the privileged EXEC encrypted password.
R1(config)# enable secret class
f. Assign cisco as the console password and enable login.
R1(config)# line console 0 R1(config-line)# password cisco R1(config-line)# login
g. Assign cisco as the vty password and enable login.
R1(config)# line vty 0 4 R1(config-line)# password cisco R1(config-line)# login
h. Encrypt the plaintext passwords.
R1(config)# service password-encryption
i. Create a banner that warns anyone accessing the device that unauthorized access is prohibited.
R1(config)# banner motd $ Authorized Users Only! $
j. Save the running configuration to the startup configuration file.
R1# copy running-config startup-config
k. Click one end of the Console cable and drag it back to the Cable Pegboard.
l. Repeat Step 2 for each device until R2, S1, and S2 are also each configured with basic settings.
Step 3: Configure settings for the server and the laptop.
Configure static IP address information on the Web Server and Laptop according to the Addressing Table.
a. Click Web Server > Desktop > IP Configuration. Enter the IPv4 address, subnet mask, and default gateway information for the Web Server according to the Addressing Table.
b. Close or minimize the Web Server window.
c. Repeat the previous steps to assign the IPv4 address information for the Laptop, as listed in the Addressing Table.
Part 2: Configure and Verify Single-Area OSPFv2 for Basic Operation
Step 1: Configure interface addresses and basic OSPFv2 on each router.
a. Connect a Console cable between R1 and the Laptop.
b. Configure interface addresses on each router as shown in the Addressing Table.
R1(config)# interface g0/0/1 R1(config-if)# ip address 10.53.0.1 255.255.255.0 R1(config-if)# no shut R1(config-if)# exit R1(config)# interface g0/0/0 R1(config-if)# ip address 172.16.1.1 255.255.255.0 R1(config-if)# no shut R1(config-if)# exit R2(config)# interface g0/0/1 R2(config-if)# ip address 10.53.0.2 255.255.255.0 R2(config-if)# no shut R2(config-if)# exit R2(config)# interface g0/0/0 R2(config-if)# ip address 192.168.1.1 255.255.255.0 R2(config-if)# no shut R2(config-if)# exit
c. Enter OSPF router configuration mode using process ID 56.
R1(config)# router ospf 56 R2(config)# router ospf 56
d. Configure a static router ID for each router (1.1.1.1 for R1, 2.2.2.2 for R2).
R1(config-router)# router-id 1.1.1.1 R2(config-router)# router-id 2.2.2.2
e. Configure a network statement for the network between R1 and R2, placing it in area 0.
R1(config-router)# network 10.53.0.0 0.0.0.255 area 0 R2(config-router)# network 10.53.0.0 0.0.0.255 area 0
f. Configure a network statement for the other networks connected to R1 and R2 and place them in area 0. Note that the network command for the LAN connected to R1 will not be graded as this network is removed later in the activity.
R1(config-router)# network 172.16.1.0 0.0.0.255 area 0 R2(config-router)# network 192.168.1.0 0.0.0.255 area 0
g. Switch the console cable to R2 and repeat substeps b through f for R2. After configuring R1 and R2, you can simply use Telnet between them, if you wish, instead of moving the console cable each time.
h. Verify that OSPFv2 is operational between the routers. Issue the command to verify that R1 and R2 have formed an adjacency.
R1# show ip ospf neighbor Neighbor IDPriStateDead TimeAddressInterface 2.2.2.21FULL/DR00:00:3310.53.0.2GigabitEthernet0/0/1 R2# show ip ospf neighbor Neighbor IDPriStateDead TimeAddressInterface 1.1.1.11FULL/BDR00:00:3710.53.0.1GigabitEthernet0/0/1
Which router is identified as the DR? Which is the BDR? What was the selection criteria?
Answers will vary. In this example R1 was configured first and was speaking OSPF before R2. So during the OSPF election only R1 was configured for OSPF and became the DR. After R2 was configured for OSPF it became the BDR on the Gigabit segment. The router with the highest router ID is used in the selection of DR and BDR.
i. On R1, issue the show ip route ospf command to verify that the R2 G0/0/0 network is present in the routing table.
R1# show ip route ospf <output omitted> Gateway of last resort is not set 192.168.1.0/32 is subnetted, 1 subnets O 192.168.1.0 [110/2] via 10.53.0.2, 00:20:26, GigabitEthernet0/0/1
j. Click Laptop > Command Prompt, and then ping the Web Server at 172.16.1.10. After one or two timeouts, the ping should be successful. If not, troubleshoot your physical connections and configurations.
Packet Tracer PC Command Line 1.0 C:\> ping 172.16.1.10 Pinging 172.16.1.10 with 32 bytes of data: Request timed out. Reply from 172.16.1.10: bytes=32 time<1ms TTL=126 Reply from 172.16.1.10: bytes=32 time<1ms TTL=126 Reply from 172.16.1.10: bytes=32 time<1ms TTL=126 Ping statistics for 172.16.1.10: Packets: Sent = 4, Received = 3, Lost = 1 (25% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>
Part 3: Optimize the Single-Area OSPFv2 Configuration
Step 1: Implement various optimizations on each router.
a. On R1, configure the interface G0/0/1 OSPF priority to 50 to ensure that R1 is the Designated Router.
R1(config)# interface g0/0/1 R1(config-if)# ip ospf priority 50
b. Configure the OSPF timers on interface G0/0/1 of each router for a hello timer of 30 seconds and a dead timer of 120 seconds.
R1(config)# interface g0/0/1 R1(config-if)# ip ospf hello-interval 30 R1(config-if)# ip ospf dead-interval 120 R2(config)# interface g0/0/1 R2(config-if)# ip ospf hello-interval 30 R2(config-if)# ip ospf dead-interval 120
c. On R1, remove the OSPF network command for 172.16.1.0, and then configure a default static route that uses interface G0/0/0 as the exit interface. Finally, propagate the default route into OSPF. Note the console message after setting the default route.
R1(config)# router ospf 56 R1(config-router)# no network 172.16.1.0 0.0.0.255 area 0 R1(config-router)# exit R1(config)# ip route 0.0.0.0 0.0.0.0 g0/0/0 %Default route without gateway, if not a point-to-point interface, may impact performance R1(config)# router ospf 56 R1(config-router)# default-information originate
d. Change the reference bandwidth on each router to 1Gbs. After this configuration, restart OSPF using the clear ip ospf process command. Note the console message after setting the new reference bandwidth.
R1(config)# router ospf 56 R1(config-router)# auto-cost reference-bandwidth 1000 %OSPF: Reference bandwidth is changed. Please ensure reference bandwidth is consistent across all routers. R1(config-router)# end R1# clear ip ospf process Reset ALL OSPF processes? [no]: yes R2(config)# router ospf 56 R2(config-router)# auto-cost reference-bandwidth 1000 %OSPF: Reference bandwidth is changed. Please ensure reference bandwidth is consistent across all routers. R2(config-router)# end R2# clear ip ospf process Reset ALL OSPF processes? [no]: yes
Step 2: Verify OSPFv2 optimizations are in place.
a. Issue the show ip ospf interface g0/0/1 command on R1 and verify that the interface priority has been set to 50 and that the time intervals are Hello 30, Dead 120, and the default Network Type is Broadcast.
R1# show ip ospf interface g0/0/1 GigabitEthernet0/0/1 is up, line protocol is up Internet address is 10.53.0.1/24, Area 0 Process ID 56, Router ID 1.1.1.1, Network Type BROADCAST, Cost: 1 Transmit Delay is 1 sec, State DR, Priority 50 Designated Router (ID) 1.1.1.1, Interface address 10.53.0.1 Backup Designated Router (ID) 2.2.2.2, Interface address 10.53.0.2 Timer intervals configured, Hello 30, Dead 120, Wait 120, Retransmit 5 Hello due in 00:00:19 Index 1/1, flood queue length 0 Next 0x0(0)/0x0(0) Last flood scan length is 1, maximum is 1 Last flood scan time is 0 msec, maximum is 0 msec Neighbor Count is 1, Adjacent neighbor count is 1 Adjacent with neighbor 2.2.2.2(Backup Designated Router) Suppress hello for 0 neighbor(s)
b. On R1, issue the show ip route ospf command to verify that the R2 G0/0/0 network is present in the routing table. Note the difference in the metric between this output and the previous output.
R1# show ip route ospf O 192.168.1.0 [110/11] via 10.53.0.2, 00:04:50, GigabitEthernet0/0/1
c. On R2, issue the show ip route ospf command. The only OSPF route information should be the default route that R1 is propagating.
R2# show ip route ospf O*E2 0.0.0.0/0 [110/1] via 10.53.0.1, 00:01:58, GigabitEthernet0/0/1
d. From the Laptop, ping the Web Server again. The ping should be successful.
C:\> ping 172.16.1.10 Pinging 172.16.1.10 with 32 bytes of data: Reply from 172.16.1.10: bytes=32 time<1ms TTL=126 Reply from 172.16.1.10: bytes=32 time<1ms TTL=126 Reply from 172.16.1.10: bytes=32 time<1ms TTL=126 Reply from 172.16.1.10: bytes=32 time<1ms TTL=126 Ping statistics for 172.16.1.10: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\>
e. Compare the following two routes:
From R1:
O 192.168.1.0/24 [110/11] via 10.53.0.2, 00:04:28, GigabitEthernet0/0/1
From R2:
O*E2 0.0.0.0/0 [110/1] via 10.53.0.1, 00:00:08, GigabitEthernet0/0/1
Why is the OSPF cost for the default route different than the OSPF cost at R1 for the 192.168.1.0/24 network?
A default static route imported into OSPF is given the metric type of “E2” or External Type 2 by default. An “E2” by default, keeps the same OSPF cost across the entire OSPF network. In this case, the metric for the default route was 1, so it has a metric of 1 everywhere within the OSPF 56 network. The 192.168.1.0 /24 network is an internal OSPF route with a metric that is cumulative.
Device Configs - Final
ROUTER R1
! ==============================================================
!--- 2.7.2 Packet Tracer - Configure Single-Area OSPFv2 - Physical Mode
!--- ANSWER SCRIPT FOR ROUTER R1
!--- Usage: after cabling R1 per the topology (G0/0/1 <-> S1 G0/1, G0/0/0 <-> Web Server F0)
!--- and powering it on, connect a console cable from R1 to the Laptop, enter privileged
!--- EXEC mode with "enable", then paste this whole file. Every line beginning with "!" is a
!--- comment; IOS ignores it, so pasting a comment by accident is harmless.
!--- Physical cabling itself (Copper Straight-Through / Cross-Over on the Cable Pegboard) is
!--- a drag-and-drop action in Packet Tracer, not an IOS command, so it is not included here.
! ==============================================================
enable
configure terminal
! --------------------------------------------------------------
!--- Part 1, Step 2: Basic device settings
! --------------------------------------------------------------
hostname R1
no ip domain-lookup
enable secret class
line console 0
password cisco
login
exit
line vty 0 4
password cisco
login
exit
service password-encryption
banner motd $ Authorized Users Only! $
! --------------------------------------------------------------
!--- Part 2, Step 1b: Configure interface addresses
! --------------------------------------------------------------
interface GigabitEthernet0/0/1
ip address 10.53.0.1 255.255.255.0
no shutdown
exit
interface GigabitEthernet0/0/0
ip address 172.16.1.1 255.255.255.0
no shutdown
exit
! --------------------------------------------------------------
!--- Part 2, Step 1c-f: Basic OSPFv2 - process 56, static router ID, and network
!--- statements for both the R1<->R2 WAN link and R1's own LAN. The LAN network
!--- statement below is graded as "not graded" by the lab itself, since Part 3
!--- removes it again - kept here to follow the lab's own step order faithfully.
! --------------------------------------------------------------
router ospf 56
router-id 1.1.1.1
network 10.53.0.0 0.0.0.255 area 0
!--- NOTE: the lab's printed command is missing the trailing "0" ("...area" instead of
!--- "...area 0") - harmless typo in the document; the working command needs the area number.
network 172.16.1.0 0.0.0.255 area 0
end
! --------------------------------------------------------------
!--- Operational habit (not explicitly required by this lab): save to NVRAM.
! --------------------------------------------------------------
copy running-config startup-config
! ==============================================================
!--- Part 2 verification (from R1, after R2's matching config is also in place):
!--- R1# show ip ospf neighbor -> 2.2.2.2, priority 1, FULL/DR (R1 came up first and became
!--- DR before R2 joined; R2 becomes BDR on arrival - roles don't flip once set)
!--- R1# show ip route ospf -> O 192.168.1.0 [110/2] via 10.53.0.2, GigabitEthernet0/0/1
!--- Laptop> ping 172.16.1.10 -> succeeds after 1-2 timeouts (ARP resolving)
! ==============================================================
configure terminal
! --------------------------------------------------------------
!--- Part 3, Step 1a: Set G0/0/1 priority to 50 so R1 keeps control of the DR role
!--- (existing DR/BDR won't be preempted immediately, but this takes effect once the
!--- OSPF process is reset in Step 1d below).
! --------------------------------------------------------------
interface GigabitEthernet0/0/1
ip ospf priority 50
! --------------------------------------------------------------
!--- Part 3, Step 1b: Hello/dead timers on the R1<->R2 link, doubled from the broadcast
!--- network defaults (hello=10/dead=40) to hello=30/dead=120 - must match on R2 too.
! --------------------------------------------------------------
ip ospf hello-interval 30
ip ospf dead-interval 120
exit
! --------------------------------------------------------------
!--- Part 3, Step 1c: Stop advertising R1's own LAN via OSPF network statement; instead
!--- give R1 a default route out its LAN interface toward the "wider network" and inject
!--- that as an OSPF default route so R2 (and any other router) can still reach it.
!--- IOS will warn about a non-point-to-point exit interface with no next-hop - expected,
!--- since G0/0/0 is a LAN (broadcast) interface, not point-to-point; harmless for this lab.
! --------------------------------------------------------------
router ospf 56
no network 172.16.1.0 0.0.0.255 area 0
exit
ip route 0.0.0.0 0.0.0.0 GigabitEthernet0/0/0
router ospf 56
default-information originate
! --------------------------------------------------------------
!--- Part 3, Step 1d: Change reference bandwidth to 1 Gb/s (1000) so cost accurately
!--- reflects Gigabit links (cost = reference-bandwidth / interface-bandwidth = 1000/1000 = 1;
!--- both R1 and R2 are all-Gigabit in this topology, so this value needs no further tuning).
!--- Must be set identically on every router - IOS reminds you of this via the console message.
! --------------------------------------------------------------
auto-cost reference-bandwidth 1000
end
! --------------------------------------------------------------
!--- Force a fresh election/recalculation now that priority, timers, and cost have
!--- all changed. Answer "yes" (or press Enter, PT defaults to yes) at the confirmation.
! --------------------------------------------------------------
clear ip ospf process
! --------------------------------------------------------------
!--- Operational habit (not explicitly required by this lab): save to NVRAM.
! --------------------------------------------------------------
copy running-config startup-config
! ==============================================================
!--- Part 3 verification (from R1):
!--- R1# show ip ospf interface g0/0/1 -> Cost: 1, State DR, Priority 50, Hello 30, Dead 120
!--- R1# show ip route ospf -> O 192.168.1.0 [110/11] via 10.53.0.2 (up from [110/2] before
!--- the reference-bandwidth change - see the lab's own note at the end comparing this internal
!--- OSPF cost to the flat E2 cost of the default route R2 receives)
!--- Laptop> ping 172.16.1.10 -> succeeds with 0% loss (no more ARP-timeout drops)
! ==============================================================
ROUTER R2
! ============================================================== !--- 2.7.2 Packet Tracer - Configure Single-Area OSPFv2 - Physical Mode !--- ANSWER SCRIPT FOR ROUTER R2 !--- Usage: after cabling R2 per the topology (G0/0/1 <-> S2 G0/1, G0/0/0 <-> Laptop F0) !--- and powering it on, connect a console cable from R2 to the Laptop (or Telnet from R1 !--- once both routers are reachable), enter privileged EXEC mode with "enable", then paste !--- this whole file. Every line beginning with "!" is a comment; IOS ignores it. !--- Physical cabling itself (Copper Straight-Through on the Cable Pegboard) is a drag-and-drop !--- action in Packet Tracer, not an IOS command, so it is not included here. ! ============================================================== enable configure terminal ! -------------------------------------------------------------- !--- Part 1, Step 2: Basic device settings ! -------------------------------------------------------------- hostname R2 no ip domain-lookup enable secret class line console 0 password cisco login exit line vty 0 4 password cisco login exit service password-encryption banner motd $ Authorized Users Only! $ ! -------------------------------------------------------------- !--- Part 2, Step 1b: Configure interface addresses ! -------------------------------------------------------------- interface GigabitEthernet0/0/1 ip address 10.53.0.2 255.255.255.0 no shutdown exit interface GigabitEthernet0/0/0 ip address 192.168.1.1 255.255.255.0 no shutdown exit ! -------------------------------------------------------------- !--- Part 2, Step 1c-f: Basic OSPFv2 - process 56, static router ID, and network !--- statements for the R1<->R2 WAN link and R2's own LAN (unlike R1's LAN network !--- statement, R2's stays in place for the whole lab - it is never removed). ! -------------------------------------------------------------- router ospf 56 router-id 2.2.2.2 network 10.53.0.0 0.0.0.255 area 0 network 192.168.1.0 0.0.0.255 area 0 end ! -------------------------------------------------------------- !--- Operational habit (not explicitly required by this lab): save to NVRAM. ! -------------------------------------------------------------- copy running-config startup-config ! ============================================================== !--- Part 2 verification (from R2, after R1's matching config is also in place): !--- R2# show ip ospf neighbor -> 1.1.1.1, priority 1, FULL/BDR (R1 was configured/speaking !--- OSPF first and had already become DR; R2 joins afterward and becomes BDR - the router !--- with the highest router ID is only the tiebreaker when routers come up simultaneously) ! ============================================================== configure terminal ! -------------------------------------------------------------- !--- Part 3, Step 1b: Hello/dead timers on the R1<->R2 link must match R1's new values !--- exactly (hello=30/dead=120) or the adjacency will drop once the dead timer expires. ! -------------------------------------------------------------- interface GigabitEthernet0/0/1 ip ospf hello-interval 30 ip ospf dead-interval 120 exit ! -------------------------------------------------------------- !--- Part 3, Step 1d: Reference bandwidth must be identical across every OSPF router in !--- the area, so R2 gets the same 1000 (1 Gb/s) value as R1. ! -------------------------------------------------------------- router ospf 56 auto-cost reference-bandwidth 1000 end ! -------------------------------------------------------------- !--- Force a fresh election/recalculation now that R1's priority took effect and the !--- timers/cost changed. Answer "yes" (or press Enter, PT defaults to yes) at the prompt. ! -------------------------------------------------------------- clear ip ospf process ! -------------------------------------------------------------- !--- Operational habit (not explicitly required by this lab): save to NVRAM. ! -------------------------------------------------------------- copy running-config startup-config ! ============================================================== !--- Part 3 verification (from R2): !--- R2# show ip route ospf -> O*E2 0.0.0.0/0 [110/1] via 10.53.0.1 (the only OSPF route now !--- present - R1's specific 172.16.1.0/24 network statement was removed, so this default !--- route, injected by "default-information originate" on R1, is what gets R2 to the Web Server) !--- Laptop> ping 172.16.1.10 -> succeeds with 0% loss !--- Why is this default route's cost (1) flat while R1's internal 192.168.1.0/24 cost is 11? !--- A default route imported via default-information originate is an OSPF External Type 2 !--- (E2) route by default - E2 keeps the metric of the point where it was injected (1 here) !--- unchanged across the whole OSPF domain, unlike a normal internal route's cost, which !--- accumulates hop-by-hop along the path. ! ==============================================================
SWITCH S1
! ============================================================== !--- 2.7.2 Packet Tracer - Configure Single-Area OSPFv2 - Physical Mode !--- ANSWER SCRIPT FOR SWITCH S1 !--- Usage: after cabling S1 per the topology and powering it on, connect a console cable !--- from S1's rear Console port to the Laptop, enter privileged EXEC mode with "enable", !--- then paste this whole file. Every line beginning with "!" is a comment; IOS ignores it. !--- S1 is a pure Layer 2 switch in this topology - it only needs the basic device settings !--- from Part 1, Step 2; it plays no part in OSPF and needs no interface/routing configuration. ! ============================================================== enable configure terminal hostname S1 no ip domain-lookup enable secret class line console 0 password cisco login exit line vty 0 4 password cisco login exit service password-encryption banner motd $ Authorized Users Only! $ end ! -------------------------------------------------------------- !--- Operational habit (not explicitly required by this lab): save to NVRAM. ! -------------------------------------------------------------- copy running-config startup-config ! ============================================================== !--- Verification: !--- S1# show running-config -> confirms hostname S1, encrypted passwords (service !--- password-encryption), console/vty login enabled, and the banner text !--- Link lights on both G0/1 (to the attached router) and G0/2 (to the other switch) !--- should be green once STP has converged (initially amber for ~50s, or use Fast Forward Time) ! ==============================================================
SWITCH S2
! ============================================================== !--- 2.7.2 Packet Tracer - Configure Single-Area OSPFv2 - Physical Mode !--- ANSWER SCRIPT FOR SWITCH S2 !--- Usage: after cabling S2 per the topology and powering it on, connect a console cable !--- from S2's rear Console port to the Laptop, enter privileged EXEC mode with "enable", !--- then paste this whole file. Every line beginning with "!" is a comment; IOS ignores it. !--- S2 is a pure Layer 2 switch in this topology - it only needs the basic device settings !--- from Part 1, Step 2; it plays no part in OSPF and needs no interface/routing configuration. ! ============================================================== enable configure terminal hostname S2 no ip domain-lookup enable secret class line console 0 password cisco login exit line vty 0 4 password cisco login exit service password-encryption banner motd $ Authorized Users Only! $ end ! -------------------------------------------------------------- !--- Operational habit (not explicitly required by this lab): save to NVRAM. ! -------------------------------------------------------------- copy running-config startup-config ! ============================================================== !--- Verification: !--- S2# show running-config -> confirms hostname S2, encrypted passwords (service !--- password-encryption), console/vty login enabled, and the banner text !--- Link lights on both G0/1 (to the attached router) and G0/2 (to the other switch) !--- should be green once STP has converged (initially amber for ~50s, or use Fast Forward Time) ! ==============================================================
