UNSOLVED

jeffdeford

updated

20 years ago

J

jeffdeford

13 Posts

0

28168

January 19th, 2007 19:00

Routed VLANs and campus wireless questions

All:
 
I have some questions on how to proceed with a wireless network deployment in my current network.
The current network has several IDCs (each defined as a unique VLAN with a corresponding IP Subnet) that are connected to a PowerConnect 6024F as the CORE.
The following VLANS and IP Subnets are currently in production:
VLAN1 192.168.1.0/24
VLAN3 192.168.3.0/24
VLAN5 192.168.5.0/24
VLAN7 192.168.7.0/24
VLAN11 192.168.11.0/24
 
A graphical depiction ( Click to enlarge) of the network is shown below (note: PLANNED wireless devices are shaded in PINK):
 

The current configuration has the interfaces on the CORE defined as members of the IDC / VLAN that each interface supports (e.g. – port g3 is assigned to VLANs 3 &1 with PVID=3, port g5 is assigned to VLANs 5 & 1 with PVID=5, etc…) The CORE has IP addresses assigned to each of the VLAN interfaces in the form of 192.168.x.254/24 where x=VLAN ID.  At the present, each port is set to operate in general mode and untagged.
Out at the edge in the IDC, switches are set so that all ports are members of the IDC VLAN (e.g. switches in the IDC that has been defined as VLAN 3 have all ports assigned to VLAN3 & 1, PVID=1 with a management IP address assigned to the VLAN1 interface that falls in the VLAN3 address pool such as 192.168.3.252). All ports on the IDC switches are set to general mode and are untagged.
This configuration has served well, as network clients in each VLAN / Subnet all receive the correct IP addresses from the DHCP server that the CORE switch has been configured to relay DHCP requests for. The LAN services both regular PC/printer and VOIP clients.
 
Now on to “the rub”…
All of the items depicted in PINK are part of the wireless deployment. The wireless deployment needs to be on new VLANs and IP subnets.  The wireless APs will be deployed on existing switches as well as new switches that will be cascaded off of the existing switches.
The new VLANS and IP subnets to be used for the wireless deployment are as follows:
VLAN2 192.168.2.0/24 wireless management (used for wireless controllers, APs, etc.)
VLAN4 192.168.4.0/24 wireless data
VLAN6 192.168.6.0/24 wireless voice
VLAN8 192.168.8.0/24 wireless guest users
 
How do I extend connectivity to the IDCs for these new VLANs and IP Address scopes so that the Wireless APs get their IP addresses from the DHCP server ?
Do I need to trunk ALL inter-switch links?
What do I need to do to my existing switches?
All of the VLANs *EXCEPT* VLAN 8 need to be able to access the network just as the wired devices that are in use now.  That being said, the wireless devices will need to get their IP addresses based on SSID and VLAN assignments (I think), so I assume that these new VLANS need to get pushed out to all of the switches?  But at what level? All ports or just trunks?
How do I configure my NEW switches? Do they need to be set up as access ports?  What about port VLAN assignments?  I am getting stuck on where and what needs trunking and where I need to use tagging.  I guess that sums it up...
 
I have lots of questions. Hopefully this will start a dialogue for some fruitful discussion.  I apologize for the long-winded post, however I thought more information is better than not enough. That being said, I will post configs as well tonight.
 
Many, many thanks in advance,
-=jeff

Message Edited by jeffdeford on 01-19-200704:09 PM

Message Edited by jeffdeford on 01-19-200711:01 PM

Message Edited by jeffdeford on 01-19-200711:03 PM

  • jeffdeford

    13 Posts

    651

    0

    Posted January 20th, 2007 02:00

    Core Config:
     

    interface range ethernet g(3,5,7,9,11)
    speed 1000
    exit
    interface range ethernet g(3,5,7,9,11)
    duplex full
    exit
    bridge multicast filtering
    interface range ethernet g(3,5,7,9,11)
    switchport mode general
    exit
    vlan database
    vlan 3,5,7,9,11
    exit
    interface ethernet g3
    switchport general pvid 3
    exit
    interface ethernet g5
    switchport general pvid 5
    exit
    interface ethernet g7
    switchport general pvid 7
    exit
    interface ethernet g9
    switchport general pvid 9
    exit
    interface ethernet g11
    switchport general pvid 11
    exit
    interface ethernet g3
    switchport general allowed vlan add 3 untagged
    exit
    interface ethernet g5
    switchport general allowed vlan add 5 untagged
    exit
    interface ethernet g7
    switchport general allowed vlan add 7 untagged
    exit
    interface ethernet g9
    switchport general allowed vlan add 9 untagged
    exit
    interface ethernet g11
    switchport general allowed vlan add 11 untagged
    exit
    interface range ethernet g(3,5,7,9,11)
    switchport general ingress-filtering disable
    exit
    gvrp enable
    ip igmp snooping
    interface vlan 1
    ip igmp snooping
    exit
    interface vlan 1
    ip address 192.168.1.254 255.255.255.0
    exit
    interface vlan 3
    ip address 192.168.3.254 255.255.255.0
    exit
    interface vlan 5
    ip address 192.168.5.254 255.255.255.0
    exit
    interface vlan 7
    ip address 192.168.7.254 255.255.255.0
    exit
    interface vlan 9
    ip address 192.168.9.254 255.255.255.0
    exit
    interface vlan 11
    ip address 192.168.11.254 255.255.255.0
    exit
    ip route 0.0.0.0 0.0.0.0 192.168.1.1
    ip dhcp relay address 192.168.1.19
    ip dhcp relay enable
    ip multicast-routing
    hostname Core
    logging 192.168.1.19
    logging buffered size 400
    aaa authentication login default local
    username **** password **** level 15 encrypted
    snmp-server community public ro type router

    Message Edited by jeffdeford on 01-19-200711:13 PM

  • jeffdeford

    13 Posts

    651

    0

    Posted January 20th, 2007 03:00

    IDC Switch Config:

    interface range ethernet all
    switchport mode general
    exit
    vlan database
    vlan 7
    exit
    interface range ethernet all
    switchport general allowed vlan add 7 untagged
    exit
    interface vlan 1
    ip address 192.168.7.180 255.255.255.0
    exit
    ip default-gateway 192.168.7.254
    username **** password **** level 15 encrypted
    snmp-server community Dell_Network_Manager rw view DefaultSuper
  • 651

    0

    Posted January 22nd, 2007 07:00

    Setting up the switches to deliver the new VLANs to the ports connected to the APs isn't a problem.
     
    You intend to run 4 VLANs over the wireless domain - will this be either a)  one VLAN per AP, or b ) will all four VLANs present on all APs?
     
    If b), do the APs support 802.1q, and will the client applications be able to 802.1q tag traffic before sending for at least three of the four VLANs?
  • jeffdeford

    13 Posts

    651

    0

    Posted January 22nd, 2007 10:00

    This is where it gets cloudy for me as I am only responible for the LAN portion of this deployment. However, from what I understand, the APs are not dot1q capable.

    Of the 4 new VLANs, only 3 are intended to be used for actual wireless clients. One of the VLAN domains is set aside for the controllers and APs.

    From what I have gathered, the APs will setablish a tunnel to the controllers and that is where the distiction will be made as to what VLAN/subnet a given client will use. I assume that the controllers will associate an SSID with a virtual interface on the controller and that is how the tunnels will be managed. I have no issues stating that I am way out of my element here with this wireless stuff, so feel free to correct me if I am wrong.

    If this is the case, then where do I need to trunk since the switches are cascaded at the IDC? Where do I need to tag? Like I said, it gets real cloudy to me...

    Thanks,
    Jeff
  • 651

    0

    Posted January 22nd, 2007 12:00

    Whose APs / controllers are you using?
     
    They appear to be thin access points; so user authentication is carried out by the controller, which then allows the user access to the WLAN - but this will authenticate the user ( by MAC address or UID/password or...) , which still won't get you separation between the different VLANs.
     
    Depending on the APs and controllers, its quite possible that the authentication will allow you to be placed into different VLANs depending on the user credentials...but that means the APs/controllers must support 802.1q VLANs.
     
    I still can't see how this can be made to work the way you want it, but who knows......we might find a way...:-)
  • jeffdeford

    13 Posts

    651

    0

    Posted January 22nd, 2007 12:00

    The controllers are Cisco 4402's if that helps. Per Cisco they suppport dot1q. I don't know what APs are being used, but I will find out ASAP.
     
    As for the controllers, I could trunk their interfaces attches to the CORE and then they will see all the VLANs I assigned to the trunk. Do I need to build trunks all the way out to the edge too?  What about tagging?  My present config is not tagged, so I am very concerned about making changes to the existing infrastructure given the fact that it is a live network.
     
    Thanks,
    Jeff

     

    Message Edited by jeffdeford on 01-22-200708:59 AM

  • StarLog

    2 Intern

    •

    203 Posts

    651

    0

    Posted January 25th, 2007 00:00

    jeffdeford, can you explain what you mean by IDC, is that an internal data closet.?
     
    Thanks
  • jeffdeford

    13 Posts

    651

    0

    Posted January 25th, 2007 15:00

    Close enough!:smileywink:
    IDC = Intermediate Data Closet.
     
    -=jeff
  • StarLog

    2 Intern

    •

    203 Posts

    651

    0

    Posted February 1st, 2007 00:00

    Jeff,
     
    I would like to hear from you on how this is going, as I just received our first 6224 switch. We have about 14 5324 switches that will be below it. Also, will need to push the DHCP scopes to the seperate vlans from one server. We are currently using 4 vlans, with the 5324's.
     
    Tom


    Message Edited by StarLog on 01-31-2007 08:01 PM
  • jeffdeford

    13 Posts

    175

    0

    Posted February 1st, 2007 17:00

    Tom:
     
    This portion is working (as you described it), it is just the WLAN that I am concerned about.  However the WLAN vendor has assured me that the controllers will handle the configuration of all WLAN clients.
     
    If you need to know how I configured the 6224 and all the 5324's then shoot me a PM.
     
    -=jeff