College Lab - Issues & Updates

Started by dipenshah, March 09, 2016, 07:24:12 PM

Previous topic - Next topic

routerdork

#15
Make sure you "no shut" the VLAN 1 interface.

Edit: I forgot to read step 4. In step 4 you need to use an Ethernet cable to connect like you have in the picture.
"The thing about quotes on the internet is that you cannot confirm their validity." -Abraham Lincoln

dipenshah

#16
Quote from: routerdork on March 24, 2016, 03:20:24 PM
Make sure you "no shut" the VLAN 1 interface.

Edit: I forgot to read step 4. In step 4 you need to use an Ethernet cable to connect like you have in the picture.

I made sure that my VLAN1 interface was "no shut". I follow it more as a rule whenever I try to configure :) Also, I verified by typing "show ip int brief" it shows everything is up for VLAN1 interface.

For 4th step am I supposed to connect my PC to switch ports on "Port 1" or my VLAN considers any port as port 1? What I mean is, if I have 24 physical ports, do I need to define which physical port is going to be my virtual port or it is handled by the switch.


I configured my switch and then disconnected it from the PC on which I was configuring. Taking same PC into consideration I connected it to switch port 1 via Ethernet and then tried to telnet it.

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
One more detail which is bugging me: I have routers connected to each other and I have router(console) connected to my PC via patch panel. But, it should somehow be connected to internet as well right? How is my router going to be on a network if I remove connection between my PC and router and likewise my switch as well. So, if my switch is connected to a router but not to a network, I don't think I will be able to telnet or SSH it?

I am attaching a picture to show how internet is connected to patch panel(one at top) and how 2 patch panels are interconnected (one at top and one at bottom). The internet connected patch panel is connected to switches and routers connected patch panel(one at bottom). 

1st red box is internet.
2nd small red box is connected to switch (and they are my 2 lab PCs - 16 & 17).
3rd red box is connected to 1st.

icecream-guy

the light blue Cisco cables are console cables. ment to directly connect a PC or Laptop to the console port of the device via either a RJ45/DB9 Console cable or a RJ45/RJ45 Console cable wiht a DB-9/RJ45 converter.  the cable pin outs are different on console cables than a typical network cable.

not sure why you have the console cable connected to the patch panel.

:professorcat:

My Moral Fibers have been cut.

dipenshah

The light blue Cisco cables are connected to patch panels which are connected to Lab PCs. Instead of connecting directly from switch to lab PC I connect it via patch panel and configure it.

Update: Today I was able to access switch(port not console) from my laptop via Ethernet cable. Also, I was able to telnet it!

I configured my switch in college's network subnet from console connected to lab PC (as mentioned above) for ex: if my lab pc has x.y.z.ab/24, I gave my switch IP address as x.y.z.ae - vlan1 which acts on all ports (verified using) "show vlan brief".

I guess I will soon be able to configure router on a stick configuration :)

Lessons learnt:
1. Patch panel broadcasts data.
2. I can access my switch via ports as well.
3. I wanted to assign random IP address to my switch and access it from Internet which I realized is not possible may be due to access limitations.

Please let me know if any of the points don't make sense I will try to elaborate and explain[emoji3]

Best,
Dipen



Sent from my iPhone using Tapatalk

dipenshah

I am trying out various configurations on Cisco 2950 switch and 1760 router.

Today I'm going to try standard and extended ACLs using a router, 2 switches and 3 laptops.

I want some suggestions on what all concepts (topologies) I can apply or practice using a simple router and a switch combination (1 router & 1 switch).

I looked into gns3 vault labs and many of them require 2-3 router, switches, etc.

Dipen

icecream-guy

Quote from: dipenshah on April 07, 2016, 10:36:41 AM
I am trying out various configurations on Cisco 2950 switch and 1760 router.

Today I'm going to try standard and extended ACLs using a router, 2 switches and 3 laptops.

I want some suggestions on what all concepts (topologies) I can apply or practice using a simple router and a switch combination (1 router & 1 switch).

I looked into gns3 vault labs and many of them require 2-3 router, switches, etc.

Dipen

how many interface does the 1760 have.

simplest would be

pc - switch - router - switch - pc
ACL on router to block ICMP, try to ping from one to other
:professorcat:

My Moral Fibers have been cut.

dipenshah

Apologies for late reply. The 1760 routers have just one interface. But, I guess I can use InterVlan concept here and divide my router interface into 2 sub-interfaces and try to ping from one end to another :)

icecream-guy

Quote from: dipenshah on April 11, 2016, 02:13:17 PM
Apologies for late reply. The 1760 routers have just one interface. But, I guess I can use InterVlan concept here and divide my router interface into 2 sub-interfaces and try to ping from one end to another :)
Router on a stick is a bit more complex, but will do the job.
:professorcat:

My Moral Fibers have been cut.

dipenshah

@ristau why did you say it is a complex job? On 04/09 I tried router-on-a-stick with 2 laptops one router and one switch. I did everything right. My configuration was working on Packet tracer as well.

I was able to ping from one laptop (network a) to another laptop's(network b) default gateway and from another laptop (network b) to my default gateway (network a). But, I was unable to ping from one laptop to another on real hardware. I assigned sub-interfaces to router, divided my switch into Vlans and connected laptops to respective Vlans as well.

I tried router on a stick 2 weeks back it was working fine. I am not sure what went wrong :(

Please suggest me what can go wrong in such a scenario.
-------------------------------------------------------

Now I will try to use a wireless router (as network b instead of another laptop) and will try configure this wireless router. Connect my phone via Wifi to that network and see if my packet flows from laptop (network a) to mobile (network b)?  :rolleyes:


dipenshah

Hah!! I got my answer!!  :partay:

Firewall was preventing the packets! I was getting a response from network b's default gateway but not from Laptop. I turned off the Firewall and voila they are able to ping each other  :XD:

deanwebb

Firewall? Like Windows firewall?

Because you can also permit traffic through the firewall. Just create the rule for it. That is why I always say...

:notthefirewall:
Take a baseball bat and trash all the routers, shout out "IT'S A NETWORK PROBLEM NOW, SUCKERS!" and then peel out of the parking lot in your Ferrari.
"The world could perish if people only worked on things that were easy to handle." -- Vladimir Savchenko
Вопросы есть? Вопросов нет! | BCEB: Belkin Certified Expert Baffler | "Plan B is Plan A with an element of panic." -- John Clarke
Accounting is architecture, remember that!
Air gaps are high-latency Internet connections.

dipenshah

Yes, Windows firewall.

I will keep that in mind :) Thanks [emoji4]


Sent from my iPhone using Tapatalk