SA520 with 3 vlans, onboard DHCP is intermittent

Hello,
I have a setup with 1 SA520w and 3 AP541n's in a residential network. I have setup 3 VLANs wired and 3 wireless VLANs. they are 1, 10, 20. I am using the SA520 as the DHCP server for all 3 subnets, "192.168.13.0"-"192.168.26.0"-"192.168.39.0", Initially the DHCP would not pass through to wireless clients but after upgrading the firmware it does. initially at boot up the AP's clients connecting to the AP's get an address for the any of the networks but fail every so often through out the day. The wired network seem to have no problem although I could not get the DHCP to work with a Netgear switch in vlan mode. Has anyone had similar problems with the SA520's DHCP and what did you do about it.

Hello,
I have a setup with 1 SA520w and 3 AP541n's in a residential network. I have setup 3 VLANs wired and 3 wireless VLANs. they are 1, 10, 20. I am using the SA520 as the DHCP server for all 3 subnets, "192.168.13.0"-"192.168.26.0"-"192.168.39.0", Initially the DHCP would not pass through to wireless clients but after upgrading the firmware it does. initially at boot up the AP's clients connecting to the AP's get an address for the any of the networks but fail every so often through out the day. The wired network seem to have no problem although I could not get the DHCP to work with a Netgear switch in vlan mode. Has anyone had similar problems with the SA520's DHCP and what did you do about it.

Similar Messages

  • SA520 Multiple VLAN Subnet Question

    I am trying to configure my SA520 with 4 VLANS
    VLAN-1 is configured as the default with 192.168.75.1/255.255.255.0 and DHCP Range of 192.168.75.100-254
    I thought I could create VLAN 2,3, and 4 with the pattern of 192.168.x.1 and DHCP of 192.168.x.100-254 where x=the VLAN ID
    When I do this, strange things seem to occur with connected DHCP clients on those VLANS, and I can not "see" DHCP leased clients in the config screen
    The system happily accepted the above config.  So after reading the docs -- I noted that VLANS need to exist in the same DHCP scope.
    I tried changing VLAN 2,3 and 4 to match the following pattern
    VLAN IP = 192.168.75.x/255.255.255.0 with DHCP of 192.168.75.1x0->1x9
    I get an error for the VLAN IP address stating that "IP in the same subnet is already configured"
    Thoughts?
    Firmware .39

    Hi Jason,
    Before the 1.0.39 firmware, the VLANs required the same subnet.  In 1.0.39, you can create your own subnets and DHCP scopes for each VLAN, which in fact is required in 1.0.39.  I am not sure if they will show up in the DHCP clients page, but I can look into this.

  • Wrvs4400n vlans/ssid/dhcp issue

    Hi all,
    it will be great if someone will help me with my problem.
    the problem is : our wrvs4400n  wifi router configuration.
    network description: we need 2 separated wifi networks one for guests and one for internal access, and i configured them on router, and also configured each one of them to different vlan, guests to vlan 200 and internal use default vlan 1.
    vlan 1 configured as dhcp relay and its working pritty well.
    vlan 200 configured as dhcp and the problem begins here.
    somehow  on vlan 200 i get dhcp from our externam dhcp server,
    wrvs4400n conected  as follow> lan port1/vlan 200 connected to firewall port(configured as vlan 200) and lan port 4/vlan1 conected to our main switch wich connected to firewall also.
    i guess that my knowlege in networking its not so good......
    how can i prevent from our internal dhcp to comunicate with vlan 200 ,
    any help will be very appreciated.

    Hi Rich,
    You cannot have different L3 VLANs sharing the same subnet.
    Each VLAN must have it's own subnet and then you have a routing device routing between both VLANs.
    You should have a DHCP pool also for VLAN 111 configured on the DHCP server.
    Even if you have ip helper address configured and this should be done on the VLAN111 interface of the switch, you still need a DHCP pool for VLAN 111 because the DHCP discovery is coming on VLAN 111.
    Please take a look into this document:
    http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a0080665ceb.shtml.
    Here it explains how to configure 2 ssids on 2 vlans and dhcp pool (on the switch itself) for each vlan.
    HTH,
    Tiago
    If  this helps you and/or answers your question please mark the question as  "answered" and/or rate it, so other users can easily find it.

  • SG-300 28P switches problem with VLAN Data and Voice, working all the time as Voice VLAN

    Hi Everyone,
    Thank you very much for your help in advance. I’m pulling my hair to fix the problem.
    I  just got the new SG-300 28P switches. My Bios ordered for me. I did not  know how it runs until now... not an IOS based. I really do not know  how to configure it.
    I have 2 VLAN are Data and Voice.
    -          Data VLAN ID is 2 IP 192.168.2.X/255.255.255.0
    -          Voice VLAN ID is 200 IP 192.168.22.X/255.255.255.0
    -          I created two vlans, in switch, Data and Voice.
    -          On the port number 28, it is trunk by default, so I add Data vlan ID 2 tagged.
    -          On the port number 26, it is trunk by default, so I add Voice vlan ID 200 tagged.
    -          On the port number 27, I add Data vlan ID 2 tagged for Data vlan out.
    -          Port settings No.1
    I set it up as Trunk with Data vlan 2 untagged, and  200  Tagged (voice vlan). I plugged in a phone with a pc attached. But the  PC will get to the vlan 200 to get the DHCP address, but no from vlan 2.  The Phone works with correct vlan ip.
    -          Port settings No.2
    Trunk with vlan 1UP, 2T, and 200T. The phone is even worse. Would never pick up any IP from DHCP.
    -          Port settings No.3
    Access  with 200U...of course the phone will work... and the PC could not get  to its own vlan. Instead, the PC got an ip from the voice vlan. Not from  VLAN 2.
    I have Linksys phone I’m not sure if this help.
    For more information I setup in switch,
                - enable voice vlan
    - set the port on auto voice vlan
    - enable LLDP-MED globally
    - create a network policy to assign VLAN 200
    - assign this network policy to the port the phone is connected to.
    I  hope this information help to help me to setup Data and Voice vlans, to  plug the phone to work with vlan Voice 200 (IP rang 192.168.22.X), from  phone to Pc and pc work as Data vlan 2 (IP rang 192.168.2.X).

    I just got done setting up voice VLANs on an SF 300-24P and verified working.  This was working with Cisco 7900 series phones connected to a Cisco UC setup.
    Here's my sample config.
    Note that I edited this by hand before posting, so doing a flat out tftp restore probably won't work.  However, this should give you a clue.  Also, don't take this as 100% accurate or correct.  I've only been working with these things for about a week, though I've worked with the older Linksys SRW switches for a couple of years.  I'm a CCNP/CCDP.
    VLAN 199 is my management VLAN and is the native VLAN on 802.1q trunks.
    VLAN 149 is the data/computer VLAN here.
    VLAN 111 is the voice/phone VLAN here.
    VLAN 107 does nothing.
    interface range ethernet e(1-24)
    port storm-control broadcast enable
    exit
    interface ethernet e1
    port storm-control include-multicast
    exit
    interface ethernet e2
    port storm-control include-multicast
    exit
    interface ethernet e3
    port storm-control include-multicast
    exit
    interface ethernet e4
    port storm-control include-multicast
    exit
    interface ethernet e5
    port storm-control include-multicast
    exit
    interface ethernet e6
    port storm-control include-multicast
    exit
    interface ethernet e7
    port storm-control include-multicast
    exit
    interface ethernet e8
    port storm-control include-multicast
    exit
    interface ethernet e9
    port storm-control include-multicast
    exit
    interface ethernet e10
    port storm-control include-multicast
    exit
    interface ethernet e11
    port storm-control include-multicast
    exit
    interface ethernet e12
    port storm-control include-multicast
    exit
    interface ethernet e13
    port storm-control include-multicast
    exit
    interface ethernet e14
    port storm-control include-multicast
    exit
    interface ethernet e15
    port storm-control include-multicast
    exit
    interface ethernet e16
    port storm-control include-multicast
    exit
    interface ethernet e17
    port storm-control include-multicast
    exit
    interface ethernet e18
    port storm-control include-multicast
    exit
    interface ethernet e19
    port storm-control include-multicast
    exit
    interface ethernet e20
    port storm-control include-multicast
    exit
    interface ethernet e21
    port storm-control include-multicast
    exit
    interface ethernet e22
    port storm-control include-multicast
    exit
    interface ethernet e23
    port storm-control include-multicast
    exit
    interface ethernet e24
    port storm-control include-multicast
    exit
    interface range ethernet g(1-4)
    description "Uplink trunk"
    exit
    interface range ethernet g(1-4)
    switchport default-vlan tagged
    exit
    interface range ethernet e(21-24)
    switchport mode access
    exit
    vlan database
    vlan 107,111,149,199
    exit
    interface range ethernet g(1-4)
    switchport trunk allowed vlan add 107
    exit
    interface range ethernet e(21-24)
    switchport access vlan 111
    exit
    interface range ethernet g(1-4)
    switchport trunk allowed vlan add 111
    exit
    interface range ethernet e(1-20)
    switchport trunk native vlan 149
    exit
    interface range ethernet g(1-4)
    switchport trunk allowed vlan add 149
    exit
    interface range ethernet g(1-4)
    switchport trunk native vlan 199
    exit
    voice vlan aging-timeout 5
    voice vlan oui-table add 0001e3 Siemens_AG_phone________
    voice vlan oui-table add 00036b Cisco_phone_____________
    voice vlan oui-table add 00096e Avaya___________________
    voice vlan oui-table add 000fe2 H3C_Aolynk______________
    voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone
    voice vlan oui-table add 00d01e Pingtel_phone___________
    voice vlan oui-table add 00e075 Polycom/Veritel_phone___
    voice vlan oui-table add 00e0bb 3Com_phone______________
    voice vlan oui-table add 108ccf MyCiscoIPPhones1
    voice vlan oui-table add 40f4ec MyCiscoIPPhones2
    voice vlan oui-table add 8cb64f MyCiscoIPPhones3
    voice vlan id 111
    voice vlan cos 6 remark
    interface ethernet e1
    voice vlan enable
    exit
    interface ethernet e1
    voice vlan cos mode all
    exit
    interface ethernet e2
    voice vlan enable
    exit
    interface ethernet e2
    voice vlan cos mode all
    exit
    interface ethernet e3
    voice vlan enable
    exit
    interface ethernet e3
    voice vlan cos mode all
    exit
    interface ethernet e4
    voice vlan enable
    exit
    interface ethernet e4
    voice vlan cos mode all
    exit
    interface ethernet e5
    voice vlan enable
    exit
    interface ethernet e5
    voice vlan cos mode all
    exit
    interface ethernet e6
    voice vlan enable
    exit
    interface ethernet e6
    voice vlan cos mode all
    exit
    interface ethernet e7
    voice vlan enable
    exit
    interface ethernet e7
    voice vlan cos mode all
    exit
    interface ethernet e8
    voice vlan enable
    exit
    interface ethernet e8
    voice vlan cos mode all
    exit
    interface ethernet e9
    voice vlan enable
    exit
    interface ethernet e9
    voice vlan cos mode all
    exit
    interface ethernet e10
    voice vlan enable
    exit
    interface ethernet e10
    voice vlan cos mode all
    exit
    interface ethernet e11
    voice vlan enable
    exit
    interface ethernet e11
    voice vlan cos mode all
    exit
    interface ethernet e12
    voice vlan enable
    exit
    interface ethernet e12
    voice vlan cos mode all
    exit
    interface ethernet e13
    voice vlan enable
    exit
    interface ethernet e13
    voice vlan cos mode all
    exit
    interface ethernet e14
    voice vlan enable
    exit
    interface ethernet e14
    voice vlan cos mode all
    exit
    interface ethernet e15
    voice vlan enable
    exit
    interface ethernet e15
    voice vlan cos mode all
    exit
    interface ethernet e16
    voice vlan enable
    exit
    interface ethernet e16
    voice vlan cos mode all
    exit
    interface ethernet e17
    voice vlan enable
    exit
    interface ethernet e17
    voice vlan cos mode all
    exit
    interface ethernet e18
    voice vlan enable
    exit
    interface ethernet e18
    voice vlan cos mode all
    exit
    interface ethernet e19
    voice vlan enable
    exit
    interface ethernet e19
    voice vlan cos mode all
    exit
    interface ethernet e20
    voice vlan enable
    exit
    interface ethernet e20
    voice vlan cos mode all
    exit
    interface ethernet e1
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e2
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e3
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e4
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e5
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e6
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e7
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e8
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e9
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e10
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e11
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e12
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e13
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e14
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e15
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e16
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e17
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e18
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e19
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e20
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e21
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e22
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e23
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e24
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet g1
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet g2
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet g3
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet g4
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e1
    lldp med notifications topology-change enable
    exit
    interface ethernet e2
    lldp med notifications topology-change enable
    exit
    interface ethernet e3
    lldp med notifications topology-change enable
    exit
    interface ethernet e4
    lldp med notifications topology-change enable
    exit
    interface ethernet e5
    lldp med notifications topology-change enable
    exit
    interface ethernet e6
    lldp med notifications topology-change enable
    exit
    interface ethernet e7
    lldp med notifications topology-change enable
    exit
    interface ethernet e8
    lldp med notifications topology-change enable
    exit
    interface ethernet e9
    lldp med notifications topology-change enable
    exit
    interface ethernet e10
    lldp med notifications topology-change enable
    exit
    interface ethernet e11
    lldp med notifications topology-change enable
    exit
    interface ethernet e12
    lldp med notifications topology-change enable
    exit
    interface ethernet e13
    lldp med notifications topology-change enable
    exit
    interface ethernet e14
    lldp med notifications topology-change enable
    exit
    interface ethernet e15
    lldp med notifications topology-change enable
    exit
    interface ethernet e16
    lldp med notifications topology-change enable
    exit
    interface ethernet e17
    lldp med notifications topology-change enable
    exit
    interface ethernet e18
    lldp med notifications topology-change enable
    exit
    interface ethernet e19
    lldp med notifications topology-change enable
    exit
    interface ethernet e20
    lldp med notifications topology-change enable
    exit
    interface ethernet e21
    lldp med notifications topology-change enable
    exit
    interface ethernet e22
    lldp med notifications topology-change enable
    exit
    interface ethernet e1
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e2
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e3
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e4
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e5
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e6
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e7
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e8
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e9
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e10
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e11
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e12
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e13
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e14
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e15
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e16
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e17
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e18
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e19
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e20
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e21
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e22
    lldp med enable network-policy poe-pse
    exit
    lldp med network-policy 1 voice vlan 111 vlan-type tagged
    interface range ethernet e(1-22)
    lldp med network-policy add 1
    exit
    interface vlan 199
    ip address 199.16.30.77 255.255.255.0
    exit
    ip default-gateway 199.16.30.3
    interface vlan 1
    no ip address dhcp
    exit
    no bonjour enable
    bonjour service enable csco-sb
    bonjour service enable http  
    bonjour service enable https 
    bonjour service enable ssh   
    bonjour service enable telnet
    hostname psw1
    line console
    exec-timeout 30
    exit
    line ssh
    exec-timeout 30
    exit
    line telnet
    exec-timeout 30
    exit
    management access-list Management1
    permit ip-source 10.22.5.5 mask 255.255.255.0
    exit
    logging 199.16.31.33 severity debugging description mysysloghost
    aaa authentication enable Console local
    aaa authentication enable SSH tacacs local
    aaa authentication enable Telnet local
    ip http authentication tacacs local
    ip https authentication tacacs local
    aaa authentication login Console local
    aaa authentication login SSH tacacs local
    aaa authentication login Telnet local
    line telnet
    login authentication Telnet
    enable authentication Telnet
    password admin
    exit
    line ssh
    login authentication SSH
    enable authentication SSH
    password admin
    exit
    line console
    login authentication Console
    enable authentication Console
    password admin
    exit
    username admin password admin level 15
    power inline usage-threshold 90
    power inline traps enable
    ip ssh server
    snmp-server location in-the-closet
    snmp-server contact [email protected]
    ip http exec-timeout 30
    ip https server
    ip https exec-timeout 30
    tacacs-server host 1.2.3.4 key spaceballz  timeout 3  priority 10
    clock timezone -7
    clock source sntp
    sntp unicast client enable
    sntp unicast client poll
    sntp server 199.16.30.1
    sntp server 199.16.30.2
    ip domain-name mydomain.com
    ip name-server  199.16.5.12 199.16.5.13
    ip telnet server

  • Need basic Help - SG300 with vlan and routing

    Hi,
    i need some basic help with configuring vlan/routing.
    Situation:
    DSL Router - Cisco 300 - XenServer
    192.168.1.253 - 192.168.1.19 - 192.168.1.10 (mgmt ip)
    goal is, to reach from inside xenserver vms the internet.
    vms = 192.168.2.x
    gateway ip = 192.168.2.1
    what i did:
    - configured vlan 102, tagged, with the xenserver port
    - configured on xenserver a network with vlan id 102, attached to the vm
    - this network is conntected to an external bond
    - configured ipva4 interface: vlan102 - Static - IP 192.168.2.1 (this is the gateway ip of the vms)
    - automatic configured IPv4 Route: 192.168.2.0/24 next hop 0.0.0.0, Directly connected
    So at the moment i cant ping from inside a vm to the DSL Router (192.168.2.2 to 192.168.1.253)
    any ideas what i misconfigured or whats wrong?
    cheers,
    -Marco

    Hi Tom,
    ok, that make sense. I can ping the router now inside vms from 192.168.2.x network.
    But i cant ping external adresses, error: Destination net unreachable.
    My other problem i have, i cant reach any server from outside over router portforwarding.
    How do i have to configure the upload port to the dsl router? Is it a access port or a trunk
    port with all vlans (tagged or untagged?) At the moment ive a tagged Trunkport with all vlans.
    IPv4 Interface Table
    Interface
    IP Address Type
    IP Address
    Mask
    Status
    VLAN 1
    Static
    192.168.1.19
    255.255.255.0
    Valid
    Should the VLAN1 ip adress not the router ip adress ? Do i need an additional vlan for
    the router ? At the end i like to change the switch ip from dhcp to static (change automaticly
    when switching to layer 3 mode), but ive to look for the ios commands first.
    What else do i missing ?
    Thanks a lot,
    Marcus

  • Two srw switches with vlans and pfsense gatway

    Hi,
    I've got a bit of a problem that a can't seem to get a handle of things.
    I've got two srw 48 port switches that I would like to link together  and then on to the pfsense box.
    First I'd like to connect the two switches to see if everything works and then on connect the pfsense box.
    Now I would be very great full if someone with a bit more experience with VLANs would be so kind to walk me trough the procedure of creating VLANs, configuring them to ports on the switch and connecting the whole thing to another switch.
    This is what I've done so fare.
    1. I created 3 VLANs on both switches (VLAN2-office,VLAN3-WiFi, VLAN5-VoIP). I've created these VLANs with the same tags on all the devices.
    2. I configured the ports that connect the switches as trunk. (I can't seem to be able to configure anything else on this port. Is there something else I should configure on these ports?)
    Now as fare as I understand the documentation the VLANs on each switch should now see each other.
    I'm still not sure on how to configure a physical port to one VLAN. After creating the VLANs on both switches and connecting them trough the trunk port I set ports 10-20 to VLAN2 by going to VLAN Management -> Ports to VLAN I selected VLAN2 and marked ports general and untagged and saved the settings. I repeated the procedure on the other switch. Now if I stuck my network cable into one of this ports I didn't get an IP anymore form the DHCP witch means that they were on a different VLAN than the other ports so I setup another router to act as a test DHCP with a different IP range as the main DHCPto see if it works. Now when I connectedthe test router to one of the ports in VLAN2 and my PC to the same VLAN2 port I got the test IP no problem. But when I connected the PC to the other switch VLAN2 port nothing happened until I connected the test DHCP to one of the VLAN2 ports. So clearly the switch VLANs are not communicating.
    Now I don't know did I forget something, made a mistake with some setting or I just don't know what I'm doing because I think I need to get the VLANs between switches working before tackling the pfsense connection.
    I would be really great full if someone explains to me how to set these VLANs up so that they would work between switches.
    Thank you for your help.

    Hi,
    I was successful and I did exactly that. I put all VLANs on trunk ports and the switch to switch to pfSense started to work.
    The only thing that gave me some problems was the end port(port connecting to the device pc, phone, printer) configuration. I was under the impression that the port was supposed to be in general mode and tagged. But I figured out that the port is supposed to be in access mode and untagged and only a member of one VLAN(the one I wanted it to connect to).
    Anyway all is working now and I've figured out all the kinks. 
    So thanks guys for the help.
    Nice day to all.
    Bye

  • SA520W Vlan's & DHCP and wireless LAN

    Hi just started to configure my new firewall and ran into some problems:
    1     I setup 3 VLAN's but cannot assign different subnets trough DHCP or manually.
           VLAN 's are working fine but they all get an ip from the same DHCP pool.
    2    I setup one WLAN for each VLAN but there is no option to assign an SSID to a VLAN.
          No WLAN can access the LAN, can that be done?
    Any help would be appreciated.
    Thank you.

    Just got my question answered by a SBSC Nework Engineer (Richard):
    The SA520 only has one DHCP scope, as you mentioned.   As a result, the
    VLAN's are all port based VLAN's.
    The steps you want to take to add your wireless SSID's to your vlan's is as follows:
    1)   Under Wireless - Profiles - Create your SSID's.
    2)   Under  Networking -  VLAN - Port VLAN  - You should see your
    wireless SSID's listed here under your wired VLAN's.  
    3)    Under Port VLAN,  Select the SSID that you want to add to VLAN's
    and select EDIT.   -   Add VLAN's to that SSID.   In order to select
    multiple VLAN's for a given SSID, you must set it to either General or Trunk port.
    Tested by me and it works perfect.
    Robert

  • V570 problem with Intel onboard driver on Windows 7 Pro 64 bit

    Hello Everyone, 
    I recently installed Windows 7 Pro 64 bit on my Lenovo v570. I downloaded the drivers from the support page and I have a strange problem with the onboard graphics driver "Intel Onboard Graphics Driver for Microsoft Windows 7 (64-bit) - Lenovo B470, B570, V370, V470, V570" in the drivers section.
    Installation seems fine, but after restart, the system fails to boot and goes into boot recovery mode, where I get a message saying that booting failed due to a bad driver and the only actual option I have to boot up is to go back to a previous restore point. I tried installing the Nvidia driver for Windows 7, but it says that I need to install an Intel driver first, which is the one that gives me the blue screen when booting. I have also tried installing both drivers without a restart between both installations, but that didn't help.
    I am wondering if anyone in the community has seen something similar. Any advice, information or assistance will be highly appreciated. Thank you very much in advance for your time.
    Best regards,
    Moe.
    Solved!
    Go to Solution.

    Welcome to the Lenovo Community !
    Check out the link I have posted below for video driver installation problems on your model.  The suggestions offered have worked for others.
    http://forums.lenovo.com/t5/Lenovo-C-E-K-M-N-and-V-Series/V570-video-drivers-don-t-work-with-Windows...
    Owner & Operator of the following:
    ● Lenovo Ideapad Z570 w/ Win 7 & Win 8.1 Dual Boot ● Lenovo Yoga 3 Pro w/ Windows 8.1 ● Toshiba A75-S206 w/ Win 7
    ● IBM Thinkpad T-23 w/ Win XP ● IBM Thinkpad T-22 w/ Win XP • As well as multiple desktops dual/triple booting XP, Vista and Win 7.
    ★ Find a post helpful? Thank that member by clicking on the ☆Star☆ to the left awarding them a Kudo.
    ★ Posting a problem and a reply is helpful and it answers your question, please mark it as an "Accepted Solution"
    ★ I'm not a Lenovo employee, just a volunteer geek who likes to help folks. Enjoy your time here, pay it forward by helping others !
    ★ Sorry, I don't answer questions via Private Messages. Posting in the appropriate forum is the best way to get assistance.

  • 802.1x with VLAN assignment on Catalyst 2950T-48-SI

    I will really appreciate if you can confirm me if the C2950T-48-SI will support the following features.
    - IEEE 802.1x with VLAN assignment
    - SSHv2
    - SNMPv3
    The data sheet for the Cisco Catalyst 2950 Series Switches with Standard Image mentions all the above and more features for the 2950T-48-SI, but at the same time the power point presentation, (Cisco Catalyst 2950 Series Switches, and the tool Sofware advisor say that those features are only supported with the Enhanced Image.
    If your those feature are supported by the Standard Image, would you please also inform the last IOS version supported.
    Thanks a lot.

    SSH isn't available on the SI version of the 2950 as you require the Crypto features and these are not available for the SI (the documentation is a little vague here but trust me I have upgraded one and it doesn't like it...). The documentation says 'Switches that support only the SI cannot run the cryptographic image.'
    802.1x with VLAN assignment is available only in the latest IOS - or at least since 12.1(22).
    SNMPv3 is supported.
    HTH
    Andy

  • 871 802.1x with vlan assignment aka dynamic vlan

    you can do vlan assignment on 871W wireless using the local radius server but unfort only LEAP which is N.G.
    I have been pounding on wired 802.1x PEAP (which works) trying to get vlan re-assignment. Have tried with IAS which I am using to do vlan reassignment with the WLC so I have the idea of how it works with IAS. With 871, no go. Have also tried ACS for radius with same results: can't escape the switchport's vlan. With debug radius local you can see the tunnel attributes for reassignment plainly but with debug radius with IAS or ACS, nada.
    Using 12.4(6)T advanced IP.
    I have just seen that 12.4(4)CX2 has "802.1x with vlan reassignment" but the download is MIA. Wonder what's up with that?
    Has anybody got this to work? Any info much appreciated
    Greg Turner

    SSH isn't available on the SI version of the 2950 as you require the Crypto features and these are not available for the SI (the documentation is a little vague here but trust me I have upgraded one and it doesn't like it...). The documentation says 'Switches that support only the SI cannot run the cryptographic image.'
    802.1x with VLAN assignment is available only in the latest IOS - or at least since 12.1(22).
    SNMPv3 is supported.
    HTH
    Andy

  • How to resolve A VMWare portgroup with VLAN ID 0 cannot be founf on virtual switch vSwitch0.

    Hi All,
    I have deployed Microsoft private cloud using SCVMM, SCOM, SCCM, SCSM, SCO and SCSM Portal...
    Also, i am using cloud service process pack runbooks and offerings for my vm provisioning in VM Ware platform...
    After submitted the request vm got created but it is throwing an error in SCVMM jobs:
    A VMWare portgroup with VLAN ID 0 cannot be found on virtual switch vSwitch0...
    VLAN ID of the existing virtual switch vSwitch is 48 and that we cannot change...also we cannot create a new vswitch in DC...
    How can i resolve this error...
    Thanks in advance for your help...
    Regards,
    Sudheesh M A

    Hi Alexander,
    Thank for answering. I asked custumer to send some config file from the switch. I don´t how complete is this, but, regarding "mls cos" entries, we have:
    no aaa new-model
    switch 1 provision ws-c2960x-48ts-l
    ip domain-name ecs.local
    login on-failure trap
    login on-success log
    vtp mode transparent
    mls qos
    crypto pki trustpoint TP-self-signed-1837850112
     enrollment selfsigned
     subject-name cn=IOS-Self-Signed-Certificate-1837850112
     revocation-check none
     rsakeypair TP-self-signed-1837850112
    interface GigabitEthernet1/0/1
     switchport access vlan 235
     switchport mode access
     srr-queue bandwidth share 1 70 25 5
     priority-queue out
     mls qos trust dscp
     service-policy input ACCESS_INGRESS
    interface GigabitEthernet1/0/2
     switchport access vlan 235
     switchport mode access
     srr-queue bandwidth share 1 70 25 5
     priority-queue out
     mls qos trust dscp
     service-policy input ACCESS_INGRESS
    interface GigabitEthernet1/0/48
     switchport access vlan 235
     srr-queue bandwidth share 1 70 25 5
     priority-queue out
     mls qos trust dscp
     service-policy input ACCESS_INGRESS
    Is these entries make any sense for the behavior we are facing?
    Thanks

  • What is it with the onboard devices on Neo2 Plat.

    What is it with the onboard devices on the Neo2 Plat. The sound really really sucks. Bass is like not there at all, other sounds is of LOW quality - Even with the Nforce driver the sound sucks, infact this is the WORST onboard sound I have ever tried.
    The wireless module is also a tragic "thing". Keeps reseting ur conection every 15 mins or so (I have 3 computers with wireless, the Neo 2 Plat is the only haveing this problem).  When the wireless is working (until the next reset in 15 mins) the Package loss is like 40%???? What is that.
    I thought I had a "DOA" MOBO device, GOT ANOTHER ONE. SAME SHITE.
    Even tried the Win64 RC edition, guess what, same problems.
    If I am wrong about this let me know (find it hard to belive since I have tested 2 Neo2 Plat, with the same problems).

    take a look at the new apple wireless keyboard... they use the same layout.

  • PXE with IP Helpers/DHCP Relay

    I'm a Sysadmin and I have a question about what is best practice in regards to PXE servers. We are currently using DHCP Options for PXE clients (options 66,67). This works for most clients but is not the recommended method from either of the vendors we have used (Microsoft or Symantec). They recommend using IP Helpers / DHCP relay to forward the DHCP discover request to the PXE servers so that the PXE server is getting the actual request. This is more of an issue now with UEFI-based machines where the boot file would be different based on if the client is UEFI.
    My Network team is against using IP Helpers and thinks it can cause issues. This doesn't seem to make much sense to me, as from what I understand, all that happens is both the DHCP server and the PXE servers get the DHCP discover and respond with their relevant info. Can someone clarify what, if any, issues there are using multiple IP helpers/DHCP relay with PXE Servers like SCCM & Altiris? Is this not standard practice?

    It's very common to use DHCP relays (IP helpers) in order to centralize DHCP infrastructure. Larger organizations will frequently use this approach in order to avoid having to manually edit DHCP configurations at the router or switch level. Having a few servers with a central DHCP configuration for all segments is a good management proposition.
    In most environments, there isn't a problem with doing this, but it is a major architectural consideration and not something you just turn on without consideration. This is largely because DHCP works on a broadcast principle. The clients are going to broadcast for the first DHCP server that answers with an acceptable offer, which they will take. If you have a mixture of local DHCP servers and relays, the local servers will respond faster and may not provide the configuration you want to deploy... at best. At worst, you will have a mix of acceptable responses and a lot of potential for conflicting addresses. On any network segment where you're using DHCP relays, the local server needs to be disabled.
    It might be worthwhile going back to your network team and asking what sorts of "issues" that they feel the implementation of DHCP relays would cause. There may be something unique to your environment that makes them reluctant to pursue this approach.

  • How to set all new vm with VLAN ID as a default settings and alose set the avaiablity high .

    How to set all new vm with VLAN ID as a default settings and alose set the avaiablity high .

    Hi Ramy,
    As a work around , you can create a VM without installing OS and  configure the Vlan of VNic , then export it .
    The new VM will be with Vlan ID when you import the "export file".(note : you need to select "copy the virtual machine " in the tab "choose import type" during importing ) .
    Hope this helps
    Best Regards
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • ISP with vlan id , cannot dialup

    I use cisco 1921 k9 , made a pppoe setting, here the problem , my ISP come with a vlan ID :620, where should i input this vaule?

    HI,
    Create Sub-interface  with VLAN tag where the IPS modem/Device is connected  and then configure the Dialer interface with PPPOE setting.
    Example:
    Interface Gig 0/0 or 0/1
    no ip address
     duplex auto
     speed auto
    interface Gig0/0.620
     encapsulation dot1Q 620
     pppoe enable group global
     pppoe-client dial-pool-number 1
    end
    interface Dialer0
    ip address  xxxxxxxxxxxx
     ip mtu 1492
     ip nat enable
     encapsulation ppp
     ip tcp adjust-mss 1452
     dialer pool 1
     dialer-group 1
     ppp authentication pap chap callin
     ppp chap hostname  ( Username)
     ppp chap password ( password)
     ppp pap sent-username ( Username) password 7 (Password)
    end

Maybe you are looking for

  • How big a deal is the shared memory for video editing

    Hi, It looks like the portable Mac I have been waiting for has been released. The one thing that I am wondering about is the shared video? memory. How big a deal is it? It looks like it should not be an issue with iMovie. How about FCE? With the Macb

  • I was delete iPhoto and i can't reinstall again!

    i was delete iPhoto and i can't reinstall again and i appstore when i press accept it say: "These apps cannot be accepted on this computer." "Future updates of these apps can be found through Software Update." ... whats prob ? and how i can solve it?

  • Trying to delete a course

    I have seen MANY people ask the same question.  We are also having the same issue in that we are not able to delete courses from our Public Site.  The Delete and Refresh buttons are greyed out.  Has anyone found a resolution?

  • Unable to create a new server

    I am running Jrun 4.0 Update 6 on windows 2003 R2 The server has been running fine for years, but just today when I went to Create a New Server in the JMC I get the follow error- Webpage error details User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Wi

  • I cannot to configure a Gmail account in my ipad 3. I enabled the IMAP settings in gmail configuration

    I cannot to configure a Gmail account in my ipad 3. I enabled the IMAP settings in gmail configuration. Using the mail configuration  manager one of the choices is GMAIL, Using this way I did not. I use an other way using MICROSOFT EXCHANGE opcion us