VLAN's and management

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

So I'm playing around with VLANs tonight and came across something where I'm not sure what to do. I think I know the answer but I want to make sure.

Scenario.

Hosts connected to my master 2950. All in VLAN 50. All accessible. No problems there. Ip of master switch is 192.168.2.200 . This is in the default VLAN 1 .. So the minute I put all my hosts in VLAN 50 I lost telnet to that switch due to it being in a different VLAN. That makes sense.

I'm consoled into my first breakout switch (192.168.2.201) so I can still get to it that way. But from a management perspective what is the correct way to do this?

If my VLAN 50 includes my main workstation and I would still like to be able to access all these from telnet then I must do inter vlan routing correct? I mean in a production environment having access to these switches is sort of a must and a console connection is not guaranteed. I'm going to make the assumption that in any production environment you rarely see VLAN's without inter VLAN routing...

I'm hoping that made sense.

Thanks
Bruce

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Yeah, Intervlan routing is the way forward.......

How To Configure InterVLAN Routing on Layer 3 Switches - Cisco Systems