Unsolved
This post is more than 5 years old
2 Posts
0
5962
February 13th, 2006 14:00
VLAN on 5224
If we do not configure separate VLANs in our network, is there any reason why we have to call our "main" network VLAN 1? Unfortunately, we have the Optiview Integrated Network Analyzer and for us to be able to discover all VLAN agents and what switch port they are plugged into, we would have to purchase the VLAN addition to their software. Does every interface on the network have to be part of a VLAN? Thanks in advance for any response.
No Events found!


DELL-Cuong N.
1K Posts
0
February 13th, 2006 14:00
nvhusker
2 Posts
0
February 15th, 2006 04:00
DELL-Cuong N.
1K Posts
0
February 15th, 2006 12:00
I'm not sure I understand your questions so I don't think I can properly answer them. My point is this - if you don't configure your switches to use VLAN then there is no VLAN information in any of the packets passing through your network so in fact your entire network topology is flat and is essentially a very traditional LAN with no VLAN information at all. I'm not sure what you mean by "...switches look like one large VLAN to the Fluke...". If you don't define VLAN then the entire network looks like one large LAN with no VLAN information. None of the packets will have VLAN tagging so the Fluke would see Ethernet frame with NO VLAN information in it. I am not sure what the Fluke equipment does so it's hard for me to make it clearer.
Also, I'm not sure what you are asking when you asked - "can we name the interface without VLAN"? You do not need to add an interface to a VLAN for the switch to work. By default if you don't do anything at all the switch operates as a normal L2 switch without requiring any VLAN information. All traffic are passed without VLAN tagging unless you specify otherwise.
Cuong.