Re: Use of Management VLAN

From: ALL From_NJ <all.from.nj_at_gmail.com>
Date: Wed, 15 Apr 2009 17:56:07 -0400

I wanted to find a link that would add to this discussion ... and had to
resort to google ;-( I am trying to become a doccd look up master ... I am
not there yet. I still need the practice.

http://www.cisco.com/en/US/docs/switches/lan/catalyst2900xl_3500xl/release12.0_5_wc_1_/swg/swgvlans.html#wp1031794

The reason I wanted to find a link is because I figured this topic could be
explained in pages of descriptions ... a bit to much to write ...

On this next link it has a short but nice write up of the why and how for
network management / management VLANs.

http://www.ciscopress.com/articles/article.asp?p=358549

Something these links to do not contain or go into with much depth is a bit
of the practical stuff.

Starting at the basics: When someone plugs their device (laptop, AP, Switch,
etc ...) into a switch, what is the default VLAN? What happens if this
default VLAN is also the same VLAN that your network devices listen to and
how you get net management statistics? Isn't network management important
and a foundation to any network? Sure it is ...

Using the default VLAN, kind of leaves you open if the users are on the same
network as your network devices. This does not mean that using an alternate
VLAN for management keeps you secrure, there is more needed ... such as
ACLs, control plane policing, etc ... it is still needed.

I think having a separate management VLAN is the first step. Makes life
easier when designing access, security, etc ... and helps to keep a barrier
between the users and network devices / management.

Sorry if this is too short, I hope this links help too. HTH,

Andrew Lee Lissitz

On Wed, Apr 15, 2009 at 12:05 PM, Mukom TAMON <mukom.tamon_at_gmail.com> wrote:

> Hello all,
> I know the theory of what a Management VLAN is but still trying to wrap
> my mind about how it works in practice. I understand it is a VLAN created
> to
> 'house' the management IP addreses of your nework devices right? But
> 1. We will have to make trunk this VLAN across the entire network
> rifht?
> 2. Do we need to maintain the 1:1 correspondence between vlans and IP
> subnet?
> Grateful for your insights
>
> M.A. TAMON
> B.Eng, CCNP, CCNA
> _________________________
> "A man owns nothing, not land or money, only his character, the loyalty &
> courage in his heart" - Commander Chakotay - StarTrek Voyager
> My BLOGs:
> [ICT Business Integration] - http://ibiztech.wordpress.com
> [Leadership Lessons from Movies] - http://thbs.wordpress.com
> [In Search of Excellence & Perfection] -
> http://perfexcellence.wordpress.com
> [Technical How-Tos & Stuff-at-a-Glance] - http://techowto.wordpress.com
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>

-- 
Andrew Lee Lissitz
all.from.nj_at_gmail.com
Blogs and organic groups at http://www.ccie.net
Received on Wed Apr 15 2009 - 17:56:07 ART

This archive was generated by hypermail 2.2.0 : Mon May 04 2009 - 07:39:12 ART