1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Cisco 2950 VLAN setup

Discussion in 'Networking (Hardware & Software)' started by Timsmith23, 2006/02/09.

  1. 2006/02/09
    Timsmith23

    Timsmith23 Inactive Thread Starter

    Joined:
    2006/02/06
    Messages:
    19
    Likes Received:
    0
    I am very new to cisco networking and need some help. A customer needs me to setup a Cisco 2950 and setup VLANs to separate several companies in the building. Can someone please help me or point me in the right direction. I have googled the subject, but have not found a clear cut step-by-step guide.

    Thanks

    Tim
     
  2. 2006/02/10
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    If you've not bought the switch yet, buy yourself seperate switches for each company. If you use HP Procurves (2124s for 24 port switches, or 408 for 8 port), you get better hardware, for less price. If you can afford it HP Procurve 2524, and 2512 switches are well worth the investment.

    If you have bought the hardware already, use that switch for the largest company, and then buy an HP procurve switch for each of the others.

    Call me a cynic, but all you get from Cisco kit is an inflated price and a headache supporting and/or selling it. (Please save me from ever again having to track down which cisco upgrade I need to purchase to get a feature I want.) 3com and netgear kit is good too, if you don't fancy the HP.

    I've never really understood the love some network designers have for VLAN. It is usually cheaper, easier, and less likely to cause errors if you seperate the hardware. The days when switches cost thousands of pounds and you needed to squeeze every last ounce out of each one are over. Also layer 3 switches are so cheap that if you need to break up a broadcast domian, its better to use one of those and do it at layer 3.
     

  3. to hide this advert.

  4. 2006/02/10
    Paul Westhead

    Paul Westhead Inactive

    Joined:
    2006/01/24
    Messages:
    39
    Likes Received:
    0
    How many VLANs do you need?

    Do you require routing between the VLANs ?
     
  5. 2006/02/10
    Timsmith23

    Timsmith23 Inactive Thread Starter

    Joined:
    2006/02/06
    Messages:
    19
    Likes Received:
    0
    No
     
  6. 2006/02/10
    Paul Westhead

    Paul Westhead Inactive

    Joined:
    2006/01/24
    Messages:
    39
    Likes Received:
    0
    FIrstly you will need to create the VLAN.

    This is done using the following

    from enable mode type "vlan database "

    The create the VLAN using the "vlan <number>" command bearing in mind that VLAN 1 is the management VLAN so do not use this one.

    Then go into each interface adn issue the following command:

    switchport access vlan <vlan number>

    This will only allow communication within its own VLAN and it is also assuming that you are only using one switch.
     
  7. 2006/02/12
    Timsmith23

    Timsmith23 Inactive Thread Starter

    Joined:
    2006/02/06
    Messages:
    19
    Likes Received:
    0
    Thanks a lot

    So once I have the vlans setup is there a way to designate which ports on the switch go to each vlan or is that something that is done in windows?
     
  8. 2006/02/12
    Paul Westhead

    Paul Westhead Inactive

    Joined:
    2006/01/24
    Messages:
    39
    Likes Received:
    0
    Appologies Tim,

    The following is what you need to do:

    From hte priveleged commadn prompt type:

    "Vlan Database "

    Then type Vlan <VLAN Number> bearing in mind that each company will require there own VLAN to keep them seperate.

    Next is the part that puts each port into the appropiate VLAN.

    After exiting from the VLAN database you will then need to type:

    configure terminal

    interface Fastethernet <number here> <-- This gives you the appropiate interface for configuration-->

    Switchport access Vlan <Vlan Number> <--This then says port XX you now belong to VLAN XX>

    Hope this makes things a little clearer.
     
    Last edited: 2006/02/12
  9. 2006/02/12
    Timsmith23

    Timsmith23 Inactive Thread Starter

    Joined:
    2006/02/06
    Messages:
    19
    Likes Received:
    0
    Thanks Paul

    This should do it.

    I assume that when you say "interface Fastethernet <number here> " you are refering to port numbers on the switch.
     
  10. 2006/02/12
    Paul Westhead

    Paul Westhead Inactive

    Joined:
    2006/01/24
    Messages:
    39
    Likes Received:
    0
    Yes,

    Exactly what is the setup as I am confused as towards why you require this VLAN seperation?
     
  11. 2006/02/12
    Timsmith23

    Timsmith23 Inactive Thread Starter

    Joined:
    2006/02/06
    Messages:
    19
    Likes Received:
    0
    I boss and the company we are working with want VLANs so I will give them vlans.
     
  12. 2006/02/12
    Paul Westhead

    Paul Westhead Inactive

    Joined:
    2006/01/24
    Messages:
    39
    Likes Received:
    0
    It all depends upon what you want doing with the VLANS though. If you are working with more than one switch there is more to it that what is above. Also if you require a port in a communal VLAN then this will also need more configuration.
     
  13. 2006/02/12
    Timsmith23

    Timsmith23 Inactive Thread Starter

    Joined:
    2006/02/06
    Messages:
    19
    Likes Received:
    0
    Its only one Cisco 2950
     
  14. 2006/02/12
    Paul Westhead

    Paul Westhead Inactive

    Joined:
    2006/01/24
    Messages:
    39
    Likes Received:
    0
    Alright are you going to be sharing the same routing for things such as internet traffic?
     
  15. 2006/02/12
    Timsmith23

    Timsmith23 Inactive Thread Starter

    Joined:
    2006/02/06
    Messages:
    19
    Likes Received:
    0
    Yes we have a single T1 connection
     
  16. 2006/02/12
    Paul Westhead

    Paul Westhead Inactive

    Joined:
    2006/01/24
    Messages:
    39
    Likes Received:
    0
    This now throws a spanner into the works.
     
  17. 2006/02/12
    Timsmith23

    Timsmith23 Inactive Thread Starter

    Joined:
    2006/02/06
    Messages:
    19
    Likes Received:
    0
    ?
     
  18. 2006/02/12
    Paul Westhead

    Paul Westhead Inactive

    Joined:
    2006/01/24
    Messages:
    39
    Likes Received:
    0
    The reason being is that by the nature of VLANS you can not communicate across them. This setup will require the port that the T1 is linked too will have to be a member of more than one VLAN at once but if you try this it is not possible. There is away round it but that'll now start costing you money :p :rolleyes:
     
  19. 2006/02/12
    Timsmith23

    Timsmith23 Inactive Thread Starter

    Joined:
    2006/02/06
    Messages:
    19
    Likes Received:
    0
    ?
     
  20. 2006/02/12
    Paul Westhead

    Paul Westhead Inactive

    Joined:
    2006/01/24
    Messages:
    39
    Likes Received:
    0
    The switch that the router will plug into will not support configuration of more than one VLAN per interface.
     
  21. 2006/02/12
    Timsmith23

    Timsmith23 Inactive Thread Starter

    Joined:
    2006/02/06
    Messages:
    19
    Likes Received:
    0
    what do you recommend?
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.