@Daniel-Espinal
Technically both situations were 'off-site'. We initially setup the Sonicwall in our office, but the connectivity was always to the client's data center. We ran into the issue during initial setup, which magically fixed itself, and then re-occurred at the client's site but never worked properly there. In both cases, outside of a different IP address (which we obviously changed in the configs once it moved), everything else was identical. Even the carrier.
It's not an EIGRP issue because we weren't using EIGRP at the new site (since it's Sonicwall). While they are using EIGRP internally between the other sites, it wasn't really necessary since it's a simple hub and spoke topology with no redundant routes or connectivity.
I'm pretty sure that the underlying issue is with the Cisco router in the hub. I say this because, even though the VPN tunnel is up to the new site, and even though it routes traffic to/from those subnets without issue, the new site's subnets aren't showing up in the routing table and , as a result, aren't being distributed out via EIGRP.
Under normal circumstances, I would look into rebooting the hub router since the uptime was something crazy and it might just be a hang up. It's also running an older IOS, but they don't have a smartnet contract on it. But since this was a one-off project for a non-managed client, with a T&M rate, eventually we just did static routes on the other sites back to the hub and everything worked fine with that.
But it's one of those things that still bothers me and I would eventually like to figure out why it didn't work properly all the time. My assumption is just a glitch in something.

@damian-tobin

Look into cisco's VIRL. They have virtual switches you can practice with. There is a slight learning curve but it's well worth it.

http://virl.cisco.com/

Otherwise the best option is to hop on ebay and grab at least 1 3560 catalyst and 2 cheap Layer 2 only switches. This is the best option since even the virtual switches have limited features when compared to real switches.

@Daniel-Espinal

Thanks! That sucks about the close pass. I definitely plan on taking it seriously though I think for me, compared to the ROUTE, it will be easier to use prior knowledge to help in preparing. I've done exponentially more work on things like VLANS, STP, Etherchannel, etc. than I have configuring EIGRP or BGP in production environments. Though I imagine since it's a more common technology that Cisco may make the questions even harder to compensate.

I'm about 2/3s of the way through the videos and hope to sit for the exam in two weeks. A lot less videos than the route series.

The one I'm most apprehensive about is the TSHOOT.

@Ponciana S Pajela,

I'm having a little problem visualizing your topology:

On R1, Try something like this:

R1(config)#int fa0/1 R1(config-if)# int fa0/1.10 #default gateway for vlan 10 R1(config-if)# encapsulation dot1q vlan 10 R1(config-if)# ip address 192.168.10.1 255.255.255.0 R1(config-if)# int fa0/1.20 #default gateway for vlan 10 R1(config-if)# encapsulation dot1q vlan 20 R1(config-if)# ip address 192.168.20.1 255.255.255.0 R1(config-if)# int fa0/1.30 #default gateway for vlan 10 R1(config-if)# encapsulation dot1q vlan 30 R1(config-if)# ip address 192.168.30.1 255.255.255.0 R1(config-if)# int fa0/1 R1(config-if)# no shutdown

ON SW1

SW1(config)# int fa0/1 SW1(config-if)# switchport mode trunk SW1(config-if)# switchport nonegotiate SW1(config-if)# exit SW1(config)# vtp domain itprotv SW1(config)# vtp password itprotv SW1(config)# interface range fa0/2 - 3 SW1(config-if-range)# switchport mode trunk SW1(config-if-range)# switchport nonegotiate SW1(config-if-range)# interface vlan 1 SW1(config-if)# ip address 192.168.10.2 255.255.255.0 SW1(config-if)# no shutdown

ON SW2 trunk to fa0/2 on SW1 and trunk to fa0/3 on SW3

SW2(config)# int fa0/1 SW2(config-if)# switchport mode trunk SW2(config-if)# switchport nonegotiate SW2(config-if)# exit SW2(config)# vtp domain itprotv SW2(config)# vtp password itprotv SW2(config)# vtp mode client SW2(config)# interface fa0/3 SW2(config-if)# switchport mode trunk SW2(config-if)# switchport nonegotiate SW2(config-if)# interface vlan 1 SW2(config-if)# ip address 192.168.20.2 255.255.255.0

ON SW3 trunk fa0/2 to fa0/2 on SW2, trunk fa0/1 to SW3 on SW1 fa0/3

SW3(config)# int fa0/1 SW3(config-if)# switchport mode trunk SW3(config-if)# switchport nonegotiate SW3(config-if)# exit SW3(config)# vtp domain itprotv SW3(config)# vtp password itprotv SW3(config)# vtp mode client SW3(config)# interface fa0/2 SW3(config-if)# switchport mode trunk SW3(config-if)# switchport nonegotiate SW3(config-if)# interface vlan 1 SW3(config-if)# ip address 192.168.30.2 255.255.255.0

ON SW1, create VLAN 10,20,30 and verify on SW2 and SW3 that the vlans appear. If they do, verify you can ping from the router to each vlan interface IP address.
Then on SW3, plug a PC into fa0/10 and put that port into vlan 30, verify you can ping the default gateway for vlan 30, then vlan 20.

If not troubleshoot, cabling connections are correct, and configurations are correct.

Learning to do these in your head is the key and isn't hard with practice.

If you can multiply by 2, you can write down a quick table to show you each segment.
I know that each octet is 8 bits. So, I write down an 8 bit decimal equivalent:

128 64 32 16 8 4 2 1

Now, when I see a /19, I know that there are all 1's in the first 2 octets (16 places), and all 0's in the last octet (places 25 through 32). The third octet is where I need to find the network number, and I do that by deciding how many bits to use, starting from the left (19 minus 16). That leaves me 3 bits for the third octet, which is 128 + 64 + 32 = 224. So, my decimal mask is 255.255.224.0 if I need that to answer an exam question. If I'm given the decimal mask instead of the network mask bitcount, I just convert it to binary as usual.

The subnet you gave, 10.100.48.27/19 uses the first 3 bits of the third octet as a mask. 48 is (0 0 1) (1 0 0 0 0) - you should already know how to convert a decimal number to binary using the decimal representation of 8 bits above. Just using those first 3 bits, I have a beginning network address of 32. The rest of the bits are assumed to be zero in the network address. 10.100.32.0/19 is the network. To find the end of that network segment, set the remaining 5 bits to 1 and add them to the beginning of the network address: 16 + 8 + 4 + 2 + 1 = 31 (I know this without adding because it will be 1 less than the next higher binary place (32)). I add 32 (the network octet) and 31 (the all 1's for the host addresses) and I get 63 (again, one less than the next higher binary place, so you can do this in your head without adding). The last possible address in the network (broadcast address) is 10.100.63.255/19 (all 1's after the last network bit, so the fourth octet is 255).

This shows you one process for finding the network and broadcast addresses. It's how I do it in my head. The host addresses are simply all addresses except the first and last within this range. As long as you can do a quick decimal to binary conversion using the power of 2 table: 128 64 32 16 8 4 2 1, then you're all set and can do each of these in mere seconds. Keep in mind the binary math trick that adding all bits to the right of any place in binary is equal to the next higher place minus 1 and you'll never have to add together the least significant bits of a binary number to convert it back to decimal.

I was able to figure the issue out with your help. Ronnie was correct as I needed to setup NAT from the new network I created to the IP which connected to my Arris router. It had been a while since I setup NAT so I forgot the "ip nat inside" and "ip nat outside" commands on the interfaces of the router. Statically assigning the interface that connected to the Arris worked pretty much the same way as using "ip address DHCP" command because the issue was actually NAT. I will leave my Arris first inline because it has a firewall and the Cisco is just my lab equipment. I have saved that config just in case I forgot.

It's funny because I got frustrated with it and had moved on to watching the CCNA videos. I did not realize my mistake until I was watching Don and Ronnie compare config files that were backed up to the tftp server. I paused it and had a "duh" moment.

Sorry but this was the first chance I had really got to sit down and play with the equipment in a long time. This is now resolved. Thanks guys

@enki That is an amazing score. Congrats

@teddi009x I also have a terminal server. Mine is an ioLAN brand but it's basically the same concept.

First thing I did was the cabling. You have to make sure you get the correct pinout. I see from google that your server has RJ45 ports so more than likely you are going to have to make your own cables. I was lucky because my box has the rs232 pinouts printed on it.

So for the cisco side of the cable, that info is all over the internet.
Alt text

Now what you have to do is find out how your terminal box is pined.
According to the pdf I found
digi cable guide

This is what you need to do

Alt text

Now it's time for the configuration. I didn't really have time to look over the user guide in depth but basically look at chapter 5, this tells you how to set up baudrate and whatnot. These settings need to match the cisco standards for connecting which are :

9600 baud
8 data bits
1 stop bit
No parity

here is the userguide I found
http://www.bb-elec.com/products/manuals/70001734_Config_Admin_Guide.aspx

hope this helps. Post back with any progress you've made. When I was setting up my terminal server it was quite a journey. Check out my struggles at the cisco forums

https://learningnetwork.cisco.com/thread/71822?start=0&tstart=0

@Daniel-Espinal,

With PAP, it's a client-server model authentication. I don't think we showed it because we've probably, between Don and me, in our experience haven't ever used it. I do see it' requires one side to act as a client and the other side the server.

Alt text
Congrats

@enki @Daniel-Espinosa

You're correct in the fact that it does prefer the secret over the regular password. At the same time remember it doesn't mean that the enable password isn't in effect. It is as you've stated in a later post,still in effect just not being used and if you remove the enable secret that the enable password is still there.

For the exam, though if both are configured, remember that the enable secret will be preferred if deciding between which one will be used.

Cisco is has consistently insisted on commands being deprecated (e.g. do wr for copy run start) yet both commands continue to find their home in the IOS. This isn't uncommon since there are so many piece of Cisco's old equipment that is still being used out there.

The increased difficulty has been a hot button topic over on the official cisco forums. All those people failing scared me away from taking the test. I've turned my efforts towards ccnp route since a lot of the topics cross over into ccna security anyway.

With that said, your score is an amazing accomplishment. Congrats :) .

@Joe-Bedale,

Ironically, both! But when working with STP, the device's MAC address is the one that is used. You might ask why and how it does it.

Technically, every port on a switch is a NIC. (So every port has a MAC)

Also, the Switch has a MAC address too BUT this is represented by the LOWEST MAC address of all the ports on the switch.

So in STP, the lowest MAC address on the switch is the one that will be used when doing the STP Root Bridge Election

@Daniel-Espinal,

It would probably be the CCNA R+S shows. If you're talking about the DR and BDR election; it would be in CCNA show.

@brian-ventura ,

Some of the notes during that point in time may not actually be there. There was point where the notes were not centralized and that means it's possible that we may not have all them available. If they are available it will be with the episode. If not, you can make a request for us to search for a specific episode and we'll see if have show notes for those episode and we'll try and post them if we find them.

Cordially,
Ronnie Wong
Host, ITProTV

@Daniel-Espinal,

Great job and LOL. Don't forget the lesson you learned earlier though. Remember that if the Reported Distanced (AD) is higher than the Feasible Distance (FD) then regardless, it wont make it in even with the variance. That is a key take away as well. It's something you're likely to see again...somewhere in a more formalized context! ;)

Cordially,
Ronnie Wong
Edutainer, ITProTV

@Marc-Cram,

I don't normally have a day where I let things slip. Today though I did. I think ( I have to check) we did this in the CCNA R+S exam instead. Even though we mention in the CCENT, I think you'll find that demonstration in the CCNA R+S show.

http://www.unetlab.com/download/index.html

Is another one that I heard about. I've never tried it myself but it looks very interesting.

Got to watch your colons right? :laughing:

Thanks.