There is no big mystery around the "management VLAN", it is just a regular VLAn that the Sup or similar device needs to made a part of to communicate with the outside world so that you can communicate and manage it. By default, the Sup modules are part of VLAN one, which you should use as you management VLAN and put all other traffic on another VLAN if you really want to make it easier for troubleshooting and a couple other reasons, but you don't have to do this if you don't want to. It just makes your network cleaner. If you only have one VLAN and a small network, just leave it that way. I make my management VLAN an rfc1918 network, ( IE 192.168.x.x, etc ) so that I am using IP addresses that are blocked from being routed, for security reasons and that I am not burning IP addresses that don't need to go outside my network, IE: accessing the internet for HTTP, FTP, etc. You can put what VLAN the Sup module attaches to, part of any VLAN so you could make a management VLAN, any VLAN number if you wish. However, the default management VLAN by default from Cisco and other vendors is VLAN 1. I would recommend though that VLAN 1 remain the management VLAN for 1 reason, if you add a new switch to the network, it is by default in VLAN 1 unless it is programmed before it is put on the network. Why take a chance of it being on the wrong VLAN? There have been cases where some switches just won't work very well in anything else but VLAN 1 for management. Just a bug in the code. Some switches won't even let you move management from working out of anything else than VLAN 1. Mostly the older switches though. If you have under 200 switches/devices on VLAN 1 that need to be managed and the router goes down or you start having router issues, all of your devices are already on the same VLAN, which doesn't require routing at this point since they are all on the same VLAN, then stick all everything else in another VLAN. I have had NICs go bad and cause some nasty broadcast storms but since they were on another VLAN, only that VLAN was really effected. You can have a port setup to be in VLAN 1 so you can attach a workstation to it to get to your devices in a pinch as you won't be routing at this point as you will be on the same subnet. ( Assuming you are not doing secondary addressing or subinterfaces on the router or running on the VLAN ) I even set aside port 1 on all the switches I manage so that when I am in a closet, I know I have a port to connect my laptop to, to manage the switches, routers with. I even host 5 addresses on this net from my DHCP server so that I don't even have to change my settings on my MAC Powerbook. Did I miss your question? Did this help? Scott > Hi, > > Just to point out to some that replyed to my message... > > Management VLAN is something different than a normal VLAN. The management > VLAN is mostly on every trunk port of a VLAN configuration. So if I have > about 6 different VLAN's on different trunk ports, the management VLAN would > also be on the trunkports of every VLAN. That's why I posted the question if > the management VLAN (configured on each VLAN domain) will let trough > broadcasts. > > > JT > > **NOTE: New CCNA/CCDA List has been formed. For more information go to > http://www.groupstudy.com/list/Associates.html > _________________________________ > UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html > FAQ, list archives, and subscription info: http://www.groupstudy.com > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] ---------------------------------------------------------- Scott Nelson - Network Engineer Wash DC +1202-270-8968 & +1202-352-6646 Los Angeles +1310-367-6646 mailto:[EMAIL PROTECTED] ---------------------------------------------------------- "The better the customer service, the sooner you get to speak with someone who can't help you." ---------------------------------------------- **NOTE: New CCNA/CCDA List has been formed. For more information go to http://www.groupstudy.com/list/Associates.html _________________________________ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
