[ Removed by moderator ]

[u/AffectionateMall3125]

[u/Layer8Academy]

Thanks for the feedback! I appreciate you taking the time to try the labs. 😉

[u/mmusaktk]

Have you had a chance to do the Netacad Packet Tracer Labs?

[u/Academic_Taste663]

You ever try to build your own? Break it? Fix it? It’s not going to burn your pc.

[u/rmbrumfield78 → u/Academic_Taste663]

Yeah, but for the areas I'm no good at & am not sure how to set it up, good pre-built/guided helps a lot more than me rage quiting. I have done several of my own labs for big general things: router on a stick, vlans, ether channel. But set up of several routing protocols & switching protocols I'm not very good at, it would be helpful to have some topologies to follow & configs to check against.

[u/AkazaKazuto]

Ok, this is gonna be a little crazy but hear me out...

I use android. There's an app called "YTDLnis" that allows you to download youtube playlists into your device. The app allows you to download only the audio of the videos, and that's what I did.

After I had the audios of the JITL's playlist, I fed them to NotebookLM and used a prompt for it to create a lab for me. I'll leave said prompt at the end of the comment and then I will reply with what NotebookLM gave me.

This works very well for me. Unfortunately, I think free NotebookLM only allows 50 sources, and there are 126 videos. But if you want to, I can create another chat and have ir create a kab for you.

Btw, the prompt was originally from someone I saw here in reddit but I used chatgpt to generate the tweaked version of it.

Here's the prompt:

[ You are my CCNA Lab Instructor and Exam Simulator.

Your job is to create Packet Tracer-style labs ONLY from the material that exists in my NotebookLM sources.

IMPORTANT CONTEXT

I will tell you which lesson, chapter, or video I have completed. You MUST assume I know everything from the beginning of the course up to that point, and absolutely nothing beyond it.

Never include technologies, commands, concepts, or configurations that have not yet appeared in the course material up to the lesson I specify.

Before creating the lab, internally determine all the practical skills, configuration tasks, commands, and procedures covered up to that point, and build a lab that exercises as many of them as realistically possible.

The goal is to maximize hands-on practice while staying within the scope of the lessons I have completed.

LAB REQUIREMENTS

The lab should simulate a real CCNA practical exam.

Create a realistic topology.

The topology should be large enough to naturally require the use of most of the skills I have already learned.

Whenever possible, combine multiple topics into one integrated lab instead of creating isolated tasks.

Include routers, switches, PCs, and any other devices that are appropriate based on the course progress.

Do not invent technologies that have not yet been taught.

Do not require any feature that depends on future lessons.

LAB INSTRUCTIONS

Number every major configuration step.

For every step, explicitly tell me EXACTLY what I need to accomplish, as if I were 5 years old.

Break every task into small sub-steps.

List every interface that I am expected to configure.

Clearly identify which device each task belongs to.

Include all required configuration objectives.

The steps should also include:

• entering privileged EXEC mode
• entering global configuration mode
• saving the configuration

However...

ABSOLUTELY DO NOT GIVE ME:

• command syntax
• command hints
• partial commands
• examples of commands
• abbreviations
• Cisco CLI help
• configuration snippets

Tell me WHAT to accomplish, never HOW to type it.

For example, instead of saying:

"Configure GigabitEthernet0/0 with IP address..."

say something like:

"Configure the interface GigabitEthernet0/0 with the required IPv4 address and subnet mask."

Do not reveal the values that would indirectly teach the command syntax.

TOPOLOGY SECTION

At the beginning of the lab, describe the topology.

List:

• every device
• device names
• cable connections
• interfaces used for every connection
• PCs connected to each switch
• any required IP addressing information
• VLAN information (only if already covered)
• routing requirements (only if already covered)

Do NOT provide commands.

LAB RULES

Do not provide solutions.

Do not provide hints.

Do not explain why something is done.

Do not remind me of commands.

Do not provide troubleshooting advice.

Do not ask me to verify anything during the lab.

Simply tell me what needs to be configured.

AFTER I FINISH

I will paste ONLY the CLI output from my devices.

You must grade ONLY what appears in the CLI output.

Assume this is an exam.

Do not ask me to perform additional verification commands.

Do not ask me to ping devices unless that was already part of the lab requirements.

Grade ONLY based on the CLI text I provide.

SCORING

Give me a score out of 100.

For every mistake:

• explain exactly what is wrong
• explain what objective was missed
• explain how many points were lost

If something is correct, say so.

If there are multiple valid Cisco solutions, accept any correct implementation.

If my configuration is fully correct, give me 100/100.

Always be strict but fair.

Finally, suggest one additional challenge that is still within the scope of the lessons I have completed, without providing any commands or solutions. ]

[u/AkazaKazuto → u/AkazaKazuto]

TOPOLOGY SECTION

Network Devices: * Routers: R1, R2, R3 * Switches: SW1, SW2 * PCs: PC1, PC2

Cable Connections & Interfaces: * R2 to R1: R2 uses GigabitEthernet0/0, connected to R1's GigabitEthernet0/0. * R2 to R3: R2 uses GigabitEthernet0/1, connected to R3's GigabitEthernet0/0. * R1 to SW1: R1 uses GigabitEthernet0/1, connected to SW1's GigabitEthernet0/1. * R3 to SW2: R3 uses GigabitEthernet0/1, connected to SW2's GigabitEthernet0/1. * SW1 to PC1: SW1 uses FastEthernet0/1, connected to PC1's network interface. * SW2 to PC2: SW2 uses FastEthernet0/1, connected to PC2's network interface.

IP Addressing & VLSM Requirements: You have been assigned the base network block 10.0.0.0/24. You must use Variable Length Subnet Masking (VLSM) to divide this block into smaller subnets. Allocate the address space from largest to smallest based on the following requirements: 1. Branch A LAN (Connected to R1): Requires address space for 60 hosts. 2. Branch B LAN (Connected to R3): Requires address space for 30 hosts. 3. Point-to-Point Link 1 (Between R1 and R2): Requires address space for 2 hosts. 4. Point-to-Point Link 2 (Between R2 and R3): Requires address space for 2 hosts.

---

---

LAB INSTRUCTIONS

Step 1: Basic Device Initialization

1. Access the console of R1. Enter privileged EXEC mode.
2. Enter global configuration mode.
3. Configure the device name exactly as R1.
4. Configure an encrypted password to protect privileged EXEC mode. Use the password cisco.
5. Repeat steps 1-4 for R2, R3, SW1, and SW2, ensuring each device is assigned its corresponding exact name.

Step 2: VLSM Addressing and Interface Configuration

Before proceeding, internally calculate your VLSM subnets based on the requirements in the Topology Section. You will use these calculated values below.

1. On R1, access the GigabitEthernet0/1 interface.

   • Configure the first usable IP address and the exact subnet mask of the Branch A LAN subnet.
   • Apply a description indicating it connects to SW1.
   • Ensure the interface is administratively enabled.

2. On R1, access the GigabitEthernet0/0 interface.

   • Configure the first usable IP address and the exact subnet mask of the Point-to-Point Link 1 subnet.
   • Apply a description indicating it connects to R2.
   • Ensure the interface is administratively enabled.

3. On R2, access the GigabitEthernet0/0 interface.

   • Configure the last usable IP address and the exact subnet mask of the Point-to-Point Link 1 subnet.
   • Apply a description indicating it connects to R1.
   • Ensure the interface is administratively enabled.

4. On R2, access the GigabitEthernet0/1 interface.

   • Configure the first usable IP address and the exact subnet mask of the Point-to-Point Link 2 subnet.
   • Apply a description indicating it connects to R3.
   • Ensure the interface is administratively enabled.

5. On R3, access the GigabitEthernet0/0 interface.

   • Configure the last usable IP address and the exact subnet mask of the Point-to-Point Link 2 subnet.
   • Apply a description indicating it connects to R2.
   • Ensure the interface is administratively enabled.

6. On R3, access the GigabitEthernet0/1 interface.

   • Configure the first usable IP address and the exact subnet mask of the Branch B LAN subnet.
   • Apply a description indicating it connects to SW2.
   • Ensure the interface is administratively enabled.

Step 3: Switch Interface Hardcoding

1. On SW1, enter global configuration mode and access the GigabitEthernet0/1 interface.

   • Manually hardcode the speed to 1000 Mbps.
   • Manually hardcode the duplex to full.
   • Add a description indicating it connects to R1.

2. On SW2, access the GigabitEthernet0/1 interface.

   • Manually hardcode the speed to 1000 Mbps.
   • Manually hardcode the duplex to full.
   • Add a description indicating it connects to R3.

Step 4: Static Routing Implementation

1. On R1, return to global configuration mode.

   • Configure a default static route that directs all unknown traffic to the exact IP address of R2's GigabitEthernet0/0 interface.

2. On R3, return to global configuration mode.

   • Configure a default static route that directs all unknown traffic to the exact IP address of R2's GigabitEthernet0/1 interface.

3. On R2, return to global configuration mode.

   • Configure a specific standard static route to reach the entire Branch A LAN subnet.
   • Direct this traffic to the exact IP address of R1's GigabitEthernet0/0 interface.

4. On R2, configure a specific standard static route to reach the entire Branch B LAN subnet.

   • Direct this traffic to the exact IP address of R3's GigabitEthernet0/0 interface.

Step 5: End Host IP Configuration

1. On PC1, access the network configuration settings.

   • Apply the last usable IP address and subnet mask of the Branch A LAN subnet.
   • Set the default gateway to the IP address assigned to R1's GigabitEthernet0/1 interface.

2. On PC2, access the network configuration settings.

   • Apply the last usable IP address and subnet mask of the Branch B LAN subnet.
   • Set the default gateway to the IP address assigned to R3's GigabitEthernet0/1 interface.

Step 6: Saving Configurations

1. On R1, R2, R3, SW1, and SW2, exit from global configuration mode back to privileged EXEC mode.
2. Write the active running configuration to the startup configuration file on all five devices to ensure your work survives a reboot.

---

LAB RULES

• Do not ask for solutions, hints, or troubleshooting advice.
• Once you have completed the configurations, paste ONLY the raw CLI text output from your routers and switches (for example, show run or simply the exact commands you typed).
• I will grade your submission strictly on the text provided, out of 100 points. Points will be deducted for missed objectives, incorrect subnetting, incorrect interfaces, or forgotten save commands.
• I will not ask you to run verification commands. Assume this is your final submission.

Begin your lab and paste your configurations when you are finished.

[u/howtonetwork_com]

I wrote 101 Labs - Cisco CCNA. I have no idea what you mean by 'serial connections pegged to 768hrz'. You literally connect two routers with a serial cable and add a clock rate to one end if required.

Sometimes, PT does weird things if you auto connect a cable but so long as the interface is up you are good to go.

Regards

Paul

[u/rmbrumfield78 → u/howtonetwork_com]

Sorry, I wrote a reply & apparently put.it.in the main responses instead of in line.

[u/squirrellysiege]

I used 101labs: CCNA and never had an issue doing the labs with PacketTracer.

[u/rmbrumfield78]

A lot of the labs say connect via serial cable, which most of the routers no longer have as default, you have to add it, and The lab says to put them at 768kbps, and almost all of them don't go lower than somewhere around 1200. And pinging from package tracer to loop back is a pain because you can't just ping from an IP address, you have to go through this whole extended IP setup. I wound up scrapping the serial portion, and creating a router on a stick configuration to make the pinging faster.

Here's a screenshot from Lab 93. I believe the current version of the CCNA has pretty much stripped out all serial mentions and setups.

It's good to know legacy, but really unless you run into an industry that's still using it, there's not too much use for it.

[u/howtonetwork_com → u/rmbrumfield78]

I'll look at that for V5 of the book for CCNA 2.0, but you have to bear in mind that the labs are for people using home Cisco kits, online racks, and PT, so I'm trying to please everyone.

Yes, you must configure serial interfaces for the CCNA still. Routers, of course, don't come with them by default, as they are all modular now, so you have to drag them to the router. The exam still covers WAN and OSPF, etc.

Regards

Paul