cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Bookmark
|
Subscribe
|
809
Views
0
Helpful
3
Replies

Cisco Packet Tracert - IP assignement process

LetMePass
Spotlight

Hello Cisco Community,

I am posting this thread because I am trying to get more experience by using Cisco Packet Tracert. I am building a simple VLAN network.

My project is available below:

https://we.tl/t-ZXbONQgpEY

When I browse on YouTube, it appears like everyone uses static IP addresses for everything: PC, Switch, and Router, which appears to be inconvenient. In practice, most IP addresses will be assigned using DHCP, therefore I activate it.

Now I have red triangles between my Switch 2960 and Router 2811. No configuration has been done yet.

Before getting into the VLAN, what am I supposed to type in the router so it gets an IP address?

For the switch I read some of them requires IP and others not? Aside the VLAN, should we type any command?

I am unable to find a clear answer on the web.  

Best Regards,

Chris

3 Replies 3

Hello,

Typically people who set up labs in PT assign static IP addresses for a couple reasons. 

1. It's convenient for several reasons - you would have to configure a DHCP server on your lab and create pools for all the networks you need an IP for. Then you would need some kind of routing (depending on how big your topology is) for all the networks to reach the DHCP server and vice-versa

2. If you configure static IPs you can make interface IPs exactly what you want. This helps in troubleshooting because if you see IP you recognize you know what its supposed to belong to. For example in my network if I have R1 connected to R2 I will put an IP that represents that connection such as 192.168.12.X. The 12 is for the link R1<->R2, remove the Rs and you have the third octet. Then the last octet is the Router #. R1 connection to R2 is 192.168.12.1 and R2 connection to R1 has the IP 192.168.12.2. That way when I see that IP or network on my Lab I know what to look for if there are any issues.

3. I see most people don't set up some kind of DHCP server in their lab unless they are specifically practicing DHCP. If you want to implement this then I suggest gearing your YouTube searches towards setting up DHCP stuff on a router and as a separate server in Packet Tracer.

 

-David

At David already notes, it can be difficult to reach a DHCP device if the network devices don't have already have an IP.  Plus depending on how you're doing routing, one router may want, or even really need, to know what the other side's IP will be.  With most DHCP hosts, they are not the target of other hosts, beyond replying to them.

In the real-world, for years, Cisco network devices didn't support DHCP on their own interfaces, and now that some do, it's often only used for dynamic connections to an ISP, where the whole site, behind it, only expects external hosts to respond to its hosts, not be the target of initial requests.

For "ordinary" hosts, in a lab, again as David notes, as there's often so few, using DHCP it's generally much more work to make it work, than just placing an IP on a few hosts.

Laugh, in the real-world of networks, I was the crazy guy who wanted most servers to use DHCP, as they too, unlike client hosts, even though they too, are "targets" of other hosts.

(Generally, not an ideal liked by server folk, but for most servers, they cannot show a reason not to do it.  However, great grandpapa, grandpapa and papa, all hard coded IPs on server hosts, and, by Jimmy Cricket, if it was good enough for them . . .  [Laugh, to be fair, there are network engineers who believe you must hard code speed and duplex on infrastructure copper links for about the same reason.  {Personally, I don't automatically think great grandpapa, et al, were stupid.  They may have very well had a fantastic reason for what they did.  But, what's the reason, and does it still apply?  Possible true story - which goes - current person cooking a turkey in oven - cuts it in half, and cooks each half separately.  Significant other asks, why?  Person responds, that's how I learned it should be done from my forebear person.  Later, forebear person, who's still living, is at person's house, and sees person cutting turkey in half.  They also ask, why?  Person responds, but that's how you always did it.  Foreperson says, well yes I did, but that's because my oven was too small to contain a full sized turkey.}])

Hi David,

Thank you, that indeed makes sense. The IP assignment for R1<->R2 is clever. I buy it!

Cheers,

Chris