Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Netflow & IP SLA Sim
#1
Hi - not sure if its me, but I can't ping 10.12.1.2 from R1, thus obtaining the output.

R1#sh ip sla summary
IPSLAs Latest Operation Summary
Codes: * active, ^ inactive, ~ pending
All Stats are in milliseconds. Stats with u are in microseconds

ID          Type        Destination      Stats      Return      Last
                                                      Code        Run
-----------------------------------------------------------------------
*1          icmp-echo  10.12.1.2        -          Timeout    18 seconds ag
                                                                  o       
and

not 

R1# show ip sla summary
IPSLAs Latest Operation Summary
Codes: * active, ^ inactive, ~ pending
ID        Type        Destination    Stats    Return        Last
                                      (ms)      Code        Run
-----------------------------------------------------------------------
*1        icmp-echo  10.12.1.2      RTT=2        OK        4 seconds ago


as indicated via the notes for this lab.

Something appears to be missing here.
Reply
#2
Hey,

So there's a few reasons why its not working as intended I'll paste the configs below in case you want to apply the fix to get the result you want.

Step 1: 
Missing IP within PC1s subnet on R1 - PC1 is on subnet 10.12.1.0/24, R1 only has one interface which is in subnet 10.10.1.0/24.

Conf t
interface eth0/0.12     (creating the subinterface with .12 as the VLAN ID)
Encapsulation Dot1Q 12     (enabling dot1q on sub interface, with 12 as the value for VLAN ID)
Ip address 10.12.1.254    (Allocating IP within PC1s subnet to the sub interface)


Step2: (can be skipped, isn't necessary for the lab tasks as we don't need to route between subnets)
PC1 isn't configured with a default gateway, we can confirm this with " ip route show | grep default"

On PC1:
sudo ip route add default via 10.12.1.254 dev eth0 -- This is creating the default gateway for PC1 to use.

Verify:  ip route show | grep default

Step 3:
On SW1, E0/0 is not configured as a trunk.

On SW1:

conf t
interface eth0/0 
switchport trunk encapsulation dot1q
switchport mode trunk

Verify: show int trunk


Hope I didn't miss anything out,
Hopefully that helps.
Reply
#3
I completely understand the steps and fixes - much appreciated for the information.

I was under the impression that we didn't have to go this deep and only add, modify, fix what was asked in the questions via the tasks.
So I would assume all configs on the infrastructure would be accurate and working. 

I am hoping this is not how it is on the actual exam.

Please confirm.
Reply
#4
(5 hours ago)networman Wrote: I completely understand the steps and fixes - much appreciated for the information.

I was under the impression that we didn't have to go this deep and only add, modify, fix what was asked in the questions via the tasks.
So I would assume all configs on the infrastructure would be accurate and working. 

I am hoping this is not how it is on the actual exam.

Please confirm.

You're right,

My exam is actually tomorrow. From the research I've done, you won't be expected to go this "deep" unless specified in the task that you need to troubleshoot an issue.

That being said, there's no harm in doing a bit "extra". I'm just a user like you, so I don't have the ability to fix these labs and reupload them.

The labs aren't perfect, there's a few hiccups such as wrong ASN numbers for the BGP lab or the VRF lab which doesn't have end-to-end connectivity so the tunnel can't be established. But they do at the very least give you an idea and if you have a bit of extra time just re-write the short config needed to make ends meet.
Reply
#5
Thanks for this information.
It's very helpful to know this.

Good luck to you on your exam tomorrow.  
I have mine as well.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)