@Jorge-Sosa said in ip default-gateway:

Hello,
I was trying to set up a default-gateway on a network comprised of pc -> router1 -> router2 -> server, and figured that the Pc can reach the Server when using in Router1 "ip route 0.0.0.0 0.0.0.0 router2", yet when trying to the same with the command "ip default-gateway router2", it wouldn't work. Hence I was wondering when would we use "ip default-gateway". I read online that usually only in switches and/or when ip routing is disabled, but I couldn't figure an scenario where that might apply. Can you please give me some insight?
Thanks

Okay. I think I'm understanding your question.... when to use:
ip route 0.0.0.0 0.0.0.0 <ip address> vs. ip default-gateway <ip address>

Respectively, you use the first one when: You have a stub network, only one path in and one path out of your network through the only router connecting to outside networks. The other is when you set a "catch all" route. You this just incase there are routes that you didn't account for within your static routes or routing protocols.

You use the second one on devices (switches generally) within your LAN that you need to access for remote management. Let's say you setup SSH access to a LAN switch. This works fine as long as you're on the same LAN but if you're going to be accessing that switch from another subnet, then you'll configure it on your internal devices so that the SSH connection can send the data back through the default gateway.

@Daniel-Espinal,

I hate to say it outside of the realm of cisco certification and hiring mangers who want make candidates squirm, manually subnetting is considered an arcane witchery anyhow. Most network admins uses subnetting calculators instead and don't even try to learn subnetting anymore. I could be more crotchety and say, everyone should know it but the reality is that IPv6 is coming and subnetting will then truly be a lost art...like driving a manual gear shift vehicle. Great to know how but not many will know.

Great! maybe you guys should have like a maillist where you can let us know what's new , what's coming so we don't annoy you with questions like this. Thanks

Thanks so much for your prompt answer @Ronnie-Wong !

@John-Croes,

We've also got on our schedule, I believe toward the end of June where Don and I will be reshooting our CCENT and CCNA R+S for the new objectives. This will be done more along the lines of the way we previously did our shows.

The great thing is that Todd Lammle said pretty much there's not been too much of a change for the CCENT but the percentages have changes and a couple of things they have made a little easier but the time demands from the exam are still stringent!

@Jorge-Sosa said in IP on routing-on-stick interface (CCENT):

Hello!,

In the CCENT intro to OSPF episode, when configuring router in a stick, I didn't get quite well the following:
In the router interface that we are going to subdivide, what is the IP that we need to configure?

You have some options with router on stick configuration when working with native vlans. If you want, you can configure an IP address on the physical interface (not a subinterface) and normally because you're not tagging traffic for the native vlan, it works fine. Then all of your other vlans you will need to communicate between would become sub interfaces configured with their vlan-id tags.
You could, instead not configure the physical interface and create a sub interface even for your native vlan instead.

You mentioned something about the native vlan, the one that is untagged... do you mean use an IP in the same range as VLAN1 in the switch>?

Normally, this is what we do. We put the interface vlan1 into the management vlan, which we normally also call our native vlan. So that IP address of the switch is on the same subnet as what you've configured for the router interface.

@Jorge-Sosa,

The definition does apply to any route that gets into the routing table. They key difference though is this. With multiple routing protocols, they learn routes and if multiple routing protocols learn about the best path to the destination which one get's entered into the routing table? The initial decision maker technically is the protocol's administrative distance--the lower the better.

With a static route this is not a learned route. It is an administratively entered route which by default is 1. The only better one is a connected route with an AD of ZERO. This is because the route is considered most trustworthy is the one that the administrator has typed in himself. If you chooses to enter a different administrative distance that's perfectly fine--technically what we call a floating-static route. But this is normally done as a backup routing method in case the routing protocol we implement fails and cannot find a route to the destination.

Between static routes to the same destination...as in your class case, the AD wouldn't necessarily be the tie breaker but the metric unless you are manipulating the AD as in the floating-static route.

@Jorge-Sosa,

There's a couple of reason to do so.

Let's say the the cost from the ISP is just about the same to run a Fiber Line to your business or a copper line. Fiber can easily expand capacity over copper. You would pick a fiber line run to the building then internally you would use a media converter to convert your copper network to connect to your ISP over fiber. Usually, this is how you see it happening. Here at ITProTV we have a 80Mbps connection to the ISP but internally we only run 100 Mbps to every port. Fiber is the future.

We do run fiber to our editing workstations though. This allows for each editor to work at 10Gbps to the shared storage without worrying. So in this sense We had to instead of using a media converter to connect to an existing switch, we put a 10 Gig blade in our switch with each port having dedicated 10Gbps for fast transfers to and from the editing stations.

Daniel is right it would be better if we had gig connections with non-blocking ports but the very fact is in most SMB you'll see that even the Gig ports are oversubscribed 4 to 1 or 8 to 1 or higher instead. Normally in the situation that Daniel is describing you also would have to consider things like how much internal bandwidth is there for the switch (backplane).

@Steve-Van,

Here Daniel is correct in his answer. If your Switch IOS supports it; it can do it. If it will not allow you to configure the DHCP commands then it will not.

@jason-kanjiravilyil said in TCP/IP or OSI Model:

What is on the Cisco CCENT/CCNA exam. The OSI or TCP/IP model.
The Cisco Book talks about the TCP/IP model and the CCENT video only mentions the OSI model.

You'll need to know both of them. The emphasis is on the OSI model for the details. The TCP/IP may still be referred to at times but it's not heavily emphasized for details.

@elasticskywalker,

We just rearranged the schedule, The 210-260 is back on the schedule and to begin on 5/31/2016...ironically since you asked about May specifically.

The CCNP Security is not rescheduled but will be back on our calendar probably before the end of the year. After we shot the first week, we decided the show didn't meet up to our expectations or hopes for a show we wanted for our members to have. It's of no disrespect to the expert. He was completely knowledgeable and a complete expert but wasn't ready for the ITProTV presentation style and format. So we had made a decision to not put on our site a show we were not proud to say we created.

@Will-McNair said in native vlan security:

If the native vlan is changed, is it a good security measure to remove it from the allowed list of vlans on a trunked port?

As Daniel said, for security sake, yes. He gave good reason to do so!

@andrew-dorey

Under the header "Enabling OSPF" I see it listing the subnet for NYWAN1: 172.88.0.0/30. From inspecting the diagram I cannot find that subnet.

If you look for NYWAN1 on the diagram. You'll see an interface for s0/0.
Your networks are attached here. The s0/0 interface was been configured as a sub-interface. This sub-interface is connected to the subnet 172.88.0.0/30 (only 2 valid IP addresses allowed) , it is directly connected. Also the sub-interface has an IP address 172.88.0.1/32 (32 indicating that single ip address on that sub-interface).

Let us know if you have any additional questions. We've got plenty of members who are really good at Cisco. So feel free to post questions here!

@shawn-banta,

Sorry about the delay in the response. We just got confirmation from the lab providers! The provider has confirmed they expect a JUNE/JULY release on the updated premium labs to go to 210-260.

@Maddog,

Please make a course request! If you click on Course Library
You may be asked to login again. then you can click on the link Course Request and add your request here.

This will allow you to make a request that is visible to everyone to vote it up or down. Because we are a content demand driven company, there is a chance that your requested content makes it because our members have the chance to vote it up or down.

@Ronnie-Wong Ok, this makes sense. Sorry, I didn't notice that he had switched to the other router. Thanks Ronnie!

Thanks Ronnie and Daniel,

I didn’t realize the premium labs gave access to the actual hardware. I may go that route.

@Mamadou-Cisse,

just glad it helped! :)

@Daniel-Espinal said:

@enki Congrats :+1:

What was your study strategy?

Thanks!

I definitely used the ITProTV SWITCH training videos. I also used some of the Cisco training resources and setup some home labs for practice. Since it was switching, GNS3 could only do so much, but I had a couple old Catalyst switches I was able to play with for other stuff. Most of the generic stuff I was able to rely on previous work experience. Even though we rarely use Cisco switches in our client's production networks, many other vendors have similar CLI environments. I've setup countless VLANs, trunks, LAGs, STP, etc. so have a strong fundamental understanding of those concepts. Even with that, there were a few questions I really just guessed at. Combined with the issues mentioned above in one of the lab questions, I really thought I might have failed. I was astonished when I got 1000. I did that on my CCNA, but felt very confident that I knew all the stuff (plus had been CCNA certified twice before hand since 2000). I spent a LOT more time studying for the route, since it was a weakness in terms of experience, and got 9-something. Hopefully my luck continues for the TSHOOT exam. I took Cisco's TSHOOT simulator, since the format is very different compares to other exams, and it looks kind of fun. I got 4/4 right, but I imagine those are just basic 'how-to' type questions. I'm going to begin studying for that tomorrow and hope to sit for it sometime next month.