Sg300 DHCP vlan

Similar Questions

• Having the problem with the function on SG300 Dhcp / 500?

  Having the problem with the function on SG300 Dhcp / 500? now I can use the dhcp server on the two model, but have a problem.

  My problem is when I create

  VLAN 1: 192.168.0.1/24 dhcp pool 192.168.0.10 - 250

  VLAN 10: 192.168.10.10 - 250 192.168.10.1/24 dhcp pool

  case 1

  I plug the pc to vlan 1 can I get ip 192.168.0.11. But when I change this pc to a new port in vlan 2 I always get the same ip address. why I can not get IP of vlan2.

  case 1

  I plug the pc to vlan 2 I can get ip 192.168.10.11. But when I change this pc to a new port in the vlan 1 I always get the same ip address. why I can not get IP of vlan1.

  but when I have access to the switch and remove the link after that that i will get correct IP.

  I think this is the bug of this firmware. Could you help this case.

  This is a known bug that is the setting of Cisco

  Sent by Cisco Support technique iPad App

• SG300 DHCP DNS server secondary Allocation

  I'm not sure that this is possible, but is the DHCP server to assign a secondary DNS server.

  It seems to be an option to place a single DNS entry in.

  I have DHCP configuration to allocate an internet base DNS (DNS Google on 8.8.8.8) so my workstations can access the internet, but I want to allocate a secondary dns for my workstations are aware able to connect to my internal servers through host names.

  Is it possible on the SG300-20 for this

  Thank you

  Paul

  Weird, I'm trying to remember what I did today.  Here is my order show proving that it worked:

  switch706852(config-DHCP) #do sh ip dhcp pool network test

  Address name mask rental range.

  ------------------- --------------------------- ------------- -----------

  test 10.10.10.1 - 10.10.10.6 255.255.255.2 1 d: 0 h: 0 m

  48

  Statistics:

  All-range available free prealloue allocated expired declined

  ----------- ----------- ------ --------------- ----------- ---------- ----------

  6           6        6           0             0          0          0

  DNS server: 4.2.2.2; 8.8.8.8

  Ah ha, history buffer shows no comma, but the space!

  switch706852(config-DHCP) # 4.2.2.2 dns server 8.8.8.8

  -Please do not forget to rate and Marc answered useful posts.

• Changes in the incoming packets to address SG300 inter - VLAN routing and MAC

  Hello

  I SG300-20 operates in Layer 3 mode

  Vlan1 is not used

  Gateway Internet is VLAN211

  Customers are in other VLANs

  Switch is the default gateway for clients and itself has internet gateway as default route.

  The switch MAC address is XX:XX:XX:XX:XX:63

  When the client sends traffic destined for Internet MAC address in outgoing packets is XX:XX:XX:XX:XX:63

  But in incoming packets the source MAC address is XX:XX:XX:XX:XX:69

  Why change? And how can I set the switch to use MAC XX:XX:XX:XX:XX:63 address?

  I finished the event and found that it does not change as expected. When you use the switch to Layer 3, routing, with or without him as your default gateway, it will happen.

  I tested two different VLAN in two different ways, and every time that I ping via the switch to a different subnet, the MAC source on the return package was different on the last two. This is due to the fact that the return traffic through a different interface on the switch.

  Currently, there is no option to change this.

• RV220W second problem of DHCP vlan

  Hi all

  I have a router Cisco RV220W (the 1.0.4.17 firmware version).

  I would like to have two separate networks with the following characteristics:

  Netwrork1: network address range is 192.168.0.1 - 254. All devices should be able to reach eachother within this network and connect you to the internet via Wifi or LAN. This network, I was also able to reach the device on the router management page. Also the devices should get the throgh of DHCP ip addresses.

  Network2: network address range is 192.168.5.1 - 254. All devices within this network should not be able to reach devices in Network1. All devices on this network should reach internet through Wifi only. Device management page should not be available on this network.

  I have configured the router as described in the attached screenshots, but the problem is that in Network2, devices get IPs of the range 192.168.0.1 - 254 and not from 192.168.5.1 beach - 254. Also, there is no internet on these either.

  Any help would be greatly appreciated.

  Mate, honestly I don't think that there is an explanation here. It doesn't seem to work as it should. I personally default from Router 2 ssid, 2 VLANs and test from there before you make additional configurations.

  -Tom
  Please mark replied messages useful

• On SG300 DHCP server configuration error

  Firmware 1.3 introduced a DHCP server.

  It seems that I can add a pool for any subnet except for the 192.168.1.1/24. I've successfully added a pool for 192.168.0.1/24, 172.16.16.1/24, etc. But when I use the same commands to add a pool 192.168.1.1/24, I get:

  SW (config) #ip dhcp pool perimeter network

  SW(config-DHCP) low #address 192.168.1.20 192.168.1.250 high 255.255.255.0

  Illegal IP address range, or subnet configuration tries to configure a pool of network on the default IP interface

  VLAN 1 IP went from 192.168.1.254 to 192.168.0.1 static default.

  Any ideas?

  Hi Frank,.

  Looks like you are experiening, bug CQ145102. There is currently no work around: Sx300 1.3.0 FW Release Notes.

  Problem: You cannot configure IP address 192.168.1.0/24 subnet as an address
  pool, other subnets are allowed. (CQ145102)
  Solution: There is no workaround.
  

  I open a case with Cisco Small Business Support, have your degenerate case and see if you can get the beta FW. The only alternative would be to review your network in order to eliminate the 192.168.1.0/24 subnet.

  Kind regards

  -David (formerly khaledammad)

• Problem with DNS SG300 for VLAN

  Hi all

  This week, I tried to implement a new SG300-52 L3 switch for switching and Vlan. The problem is that VLAN on the switch can't them get their DNS resolved. Probably a stupid thing that I can't see, but I think it's a given simple solution easy is not my expertise.

  So my configuration:

  -Router Wan ISP: LAN ip 10.0.0.1, DMZ: 10.0.0.2-> I use this router for support of the ISP. But it suckes, that's why we use own firewall router, forwarding port etc.

  -Nice router: WAN: 10.0.0.2, LAN: 192.168.1.1

  -Dip-switch SG300 L3:

  VLAN 1 (the default) ip 192.168.1.10/24

  IP VLAN 5 (for back-end servers) 10.1.1.1 / 24

  Added static routes:

  0000 / 0000-> 192.168.1.1 (so just send it to the router of Nice)

  This method works. I can ping switch, nice router, router ISP and ip of google to VLAN 5.

  But I can't ping google by using the host name.

  Leave in SG300 I can. So he has something to do with SG300 does not do DNS.

  My Client on VLAN 5 has 10.1.1.5 ip / 24, default gateway and dns pointing to switch: 10.1.1.1.

  I put an entry in the DNS of SG300 servers: 192.168.1.1 active (pointing to Nice router). Does not help.

  Work around:

  The default authorization pointing gateway to move customer. But put DNS server: 192.168.1.1 == Nice router.

  Now I can ping google.com. But this isn't what I want. Just a nasty workaround solution.

  Any help appreciated,

  Thank you

  Atam

  .

  I understand that you do not want to use the switch as your primary DNS, however the switch does not all DNS features which can manage DNS queries.

  DNS traffic must be addressed to a DNS server or a DNS proxy. The switch is unable to answer DNS queries. Simply thanks to the switch as your gateway by default, you route already traffic from the computer to the switch and then to the router.

  To give an example. If you send traffic telnet to the switch, you would get a telnet connection. If you send DNS traffic to the switch, you will not get a response that the switch does not know what to do with the request.

  I hope this information helps.

• SG300 voice vlan problem with UC520

  Salvation of the Forumers

  My problem statement:

  -Secretary referred to topology.png, this is how my network like structure look

  -the IP phone after startup can not connect, so it cannot download the XML of UC520 configuration file. problem switching suspects.

  -my configuration illustrated in topology.png and my config show vlan as the voice setting.png voice vlan

  -My requirement is switch SG300 unique switchport to carry data VLANs and vlan voice.

  -What is the mode of connection for voice siwth VLAN an IP phone + data must be set up? is it switchport voice vlan vvid switchport voice vlan dot1p, switchport voice vlan unidentified or vlan switchport voice no further action over requirement?

  Thank you

  Noel

  Christmas morning,

  Sorry for the late reply, things have been very hectic in here lately

  1. Why use trunk? the UC520 don't have voice vlan (vlan 20)

  Do you mean that data THAT VLAN is handled by another device? Again I would like to leave as a trunk in order to manage the CPU through the data VLAN. (Except for security or other reasons you would choose differently of course)

  2. the UC520 got CUE (voicemail), how should I design the uplink service for the main switch module?

  Nothing in particular needs to be done for this, CUE is processed and routed inside the UC520, the vlan (default ID = 90) CUE is used if you have another LANDMARK in the network

  1. I guess I did: swithcport the tag vlan vlan unlabelled 20, 10. is it ok for this setting?

  If the Vlan on the switch and the UC520 voice has been defined as VLAN 20 (default value = VLAN 100) it's perfect. Check if the CPU and the switch, the voice VLAN ID is set to 20.

  1 so if I have just the phone to vlan 20 (vlan voice), create the policy of network LLDP?

  If you are ready to configure the VLANS manually on the phone, you don't need politics LLDP, thats right.

  Politics LLDP is used to having phones automatically choose the VLAN you set, so you do not need to set it manually.

  I hope that answers your questions?

  Best regards

  Nico glacier

  Senior Network Engineer - CCNA

• SG300-10 - DHCP server did not update DNS (bind9) records

  Hello community,

  My SG300 is configured in Mode L3 in my Homelab, and the DHCP server is enabled.

  The switch runs on the Version of the Firmware 1.4.1.3.

  I have configured by a Pool of network VLAN.

  The default router IP address (Option 3), the IP of the DNS (Option 6) and the domain name (Option15) are also configured.

  DHCP works fine without problems.

  Customers get their inclusive information of router, DNS, and domain IP Configuration name.

  As a DNS server, I configured a server bind9 under winded raspbian.

  The bind9 is configured to allow dynamic updates and DNS works as expected.

  Manually using NSUPDATE I can make dynamic updates to bind9 DHCP clients areas.

  But this isn't what I want.

  I want to make the SG300 DHCP server dynamic updates to the DNS zones.

  Would be the Option DHCP 81 (Client FQDN) useful?

  Any idea is welcome. :-)

  Looking forward to hear from you because it drives me crazy.

  Best regards

  Rainer.

  Sorry for the delay in reply Rainer.  I tried to set this up in my lab and became GUI of entry of unexpected results that did not affect the packages at all.  Checked with my contacts and they advised me that it is not supported on this switch option 81.  Given that the client sends to the server on how to update DNS records, the switch does not support this dynamic configuration.

  Referring to the data sheet for the SG300, these are supported options listed:

  DHCP (12, 66, 67, 82, 129 and 150 Options)

  Here is the link to the datasheet.

  http://www.Cisco.com/c/en/us/products/collateral/switches/small-business-smart-switches/data_sheet_c78-610061.html

  Sorry about the information, but is not a supported option.

  James

• VLAN in environment ESXi5 Switch Cisco SG300 and gateway RV220W

  Hi, I'm having a few problems getting VLANing to work properly.  I was hoping that someone would be able to point me in the right direction.  I spend a RV220W which has 2 VLANS on VLAN1 with a 192.168.1.x and VLAN 104 subnet with a subnet of 192.168.104.x.  Port 4 of the goes to port the SG300 Switch 20.  Port 20 switch SG300 has VLAN 1 as non-marked and labeled as VLAN104.  It also has the port configured in the same way 15 and 16.

  In my ESXi host NIC2 is in the 16 port and NIC3 is in port 15.  I created a Standard vSwitch1 and created two groups of ports.  192.168.104.x group has a vlan id of the 104 and group vmware with no id vlan.  I guess that when I put a virtual machine in vmware port group I would get the IP 192.168.1.x what I do.

  When I put a virtual machine in port 192.168.104.x I guess I should get an IP of 192.168.104.x, but I have not, I get a return address of loop group.

  Any ideas what I am doing wrong?  I'm assuming that by creating the port group 192.168.104.x with id VLAN 104 that is the vlan native untagged for this option, which would then send the traffic through the port 15 or 16 depending on the tag VLAN104.  That would be so only send traffic out port 20 to port 4 of the RV220W which should serve as a DHCP server for the this response as 192.168.104.1.

  Just at the moment where I think I have a handle on the VLAN, I'm wrong.

  Thank you

  I would recommend this:

  Configure an access port on SG300, with no trunking

  Configure it to VLAN 104

  Place your desktop on this VLAN

  Configure your desktop and virtual computer with a static IP address

  Test if they have connectivity

  This excludes the configuration of VMware and confirm that your trunk to the SG300 is operational.

• DHCP fails with two subnets and RV325 and SG300 - 28 p

  DHCP fails to issue addresses in double subnet environment.  Please see attached.

  Hello

  Mr. Ezzell, after reviewing all the screenshots and have a look at your configuration and you are not able to change the arrangement for VIRTUAL LANs, you can try this:

  As a work-around to use the router as DHCP VLAN 2 server, you can enable the DHCP server on the router for the VLAN 1, leave 2 IP addresses available, lets say 192.168.1.253 to 192.168.1.254 then go to static DHCP under network and the local network and hire two false addresses to these two IP addresses, so they will not be assigned to all devices. This way you will always be able to use your DHCP server without having to disable the DHCP server on the router

  Thank you for pointing out the firmware version very low on your switch, you actually run the firmware that came out of the unit.

  Here is a link to the firmware download page:

  https://software.Cisco.com/download/release.html?mdfid=283019669&flowid=...

  Please upgrade to the following firmware versions:

  1.2.9.44
  1.3.0.62
  1.3.5.58
  1.4.0.88

  Keep in mind that on the 1.3.5.58 version, you must also upgrade the bootcode using TFTP software.

  Once you are done with the upgrade of the connection check and see if it works.

• SG300 + SG500 = intervlan headaches

  OK, so I'm pulling my hair out with this one and now it's time to ask the people with experience.  Basically I have a stack of sg500 running a router-on-a-stick Setup.  I ran out of virtual ports on the sonicwall and now trying to get internet to route between VLANS by taking them out of the equation the sonicwall.  I had NO chance and ner access to any vlan other than 50 see internet.  So here goes.

  Main SG500

  -Vlan 50 contains a direct connection of the trunk to the sonicwall on IG 13

  -Vlan 50 contains a direct connection from trunk to sg300 on IM 42

  -14-41 are in vlan 50 as access ports (internet is ok)

  -Vlan 50 is set for an IP 192.168.50.1

  -Sonicwall ip is 192.168.50.254

  Remote SG300

  VLAN - 51 is access ports 1-5 IP 192.168.51.1

  VLAN - 52 is access ports 6-9 IP address 192.168.52.1

  VLAN - 53 is 10-11 ports access 192.168.53.1 ip address

  VLAN - 50 is trunk port ip 20 address 192.168.50.2

  -dhcp is configured on each interface as well

  I'm not even sure it's possible, but I need to get the 192.168.51.1 to 192.168.50.254 somehow while he can get online.  However no matter what I try in the routing table I constantly make me stuck behind the bridge vlan.  So, if im on 192.168.52.10 and I trace route on 192.168.50.1 or 192.168.50.2 or 192.168.50.254 it stops ALWAYS at 192.168.52.1.  Any idea?  Suggestions?  I'm about to give up on it and just throw it all together.  I spent far to on it for a long time already.

  Just to give you an idea what it is, because there are 3 rental offices that all three need internet but should not be able to talk to eachother.  The private ports would work, but these offices have several ethernet ports and if they connect a printer and PC will not able to talk.  Any idea would be greatly appreciated

  Hi Matt, looks like you're missing a route on the sonicwall to point to the gateway of the switch.

  If a VLAN is working and the rest are not, it is because the sonicwall is not supported/configure for VLANs or is not a routing table for the subnet.

  -Tom
  Please mark replied messages useful

• Having trouble getting the voice VLAN on the switch X1052P to work at all

  Can someone help me understand how to set up the voice VLAN X1052P? I spent several hours trying to get this working and it does not work. I spent about 4 hours on the phone with a Dell technician that night and he couldn't get it to work and finally gave up. He told me that I had to spend my warranty to ProSupport because he did not know how to solve the problem. What group of *. It's a simple configuration of VLAN. What must be so picky about? In any case...

  Setting up the VIRTUAL LAN must be fairly simple, but apparently on this switch is not. The user guide page 406 is not very useful except explaining what the different options. I must admit I am not an expert VLAN so I dunno I've misconfigured something. But remember, Dell technology could not operate either.

  Here's my situation... I have VoIP phones on my network connected to a network wall jack. Connected to phones are my computers of users. The computer of the user and its respective VoIP phone, both share the same data cable. Before replacing Cisco managed Internet service provider spend all it worked well. The problem is that they had direct access to our network so I removed the switch and installed the X1052P in its place. I talked to the ISP to let them know what I'm doing and they said everything I had to do was setup VLAN ID: 15 for the voice VLAN because this is the VLAN ID that the router uses to route telephone traffic. Router PSI is also the server DHCP VLAN 15 and issues IP for phones using 172.27.0.0/24 with a DHCP 172.27.0.50 range - 150.

  I tried to configure the switch using parameters of VLAN static and settings VLAN voice and neither one also seems to do what I want it to do.

  Network administration > VLAN > VLAN static

  Network administration > VLAN > Voice VLAN

  I activated the profile 'phone' on ports I want to added to the voice VLAN and it does not work. Moreover, 47 the switch port is connected directly to the ISP router and is configured as a trunk with the default port VLAN 1 unidentified and tag VLAN 15. For other ports I tried the general implementation, access and trunk of the parameters on each port to see if I could get something going and still nothing happens. When I set up the ports as General ports VLAN, I made adding VLAN VLAN 1 and VLAN 15 as a VLAN tagged not marked. It still does not.

  This is the short story from where I am now. Any help is greatly appreciated.

  FYI, as a follow up I finally solved the problem. I hope this information helps someone else that can encounter the same problem.

  After buying the ProSupport warranty upgrade ($121 out-of-Pocket mind you) and addressing a total of 4 technicians ProSupport expert technician a 3rd another level (only available via chat message between one of the ProSupport phone technicians and the 3rd Tier expert tech - i.e. I couldn't talk or chat with this person me) the consensus was that the material must be bad. When I bought the X1052P I bought two of them, so the best way to know if it was a bad switch was simply configure the other switch and see if the behavior occurs on this one, too. Well, this switch also restarted each time I assigned the profile 'phone' to more than 13 or 14 ports in the switch. It seems that it was not a hardware problem after all.

  I went back to the switch original and tried new things hoping that I could fall on a solution and it turns out that the solution was NOT to use the voice VLAN on the switch. It does not work!

  SOLUTION: I set the VLAN ID: 15 manually and no has not assigned any phone profiles to one of the ports. This is how I solved the problem.

  So he has bad software on the switch. I tried to see if there are updates of the firmware on the Dell support site, but there is none. Configure manually the phone VLAN was the solution. What a freaking nightmare which turned out to be. Maybe someone in Dell could note this problem and test in-house. And, if you want to compensate me for the 20 + hours I spent working on this problem, which has be great, too.

• VLAN does not not as expected

  Current configuration:

  Firewall and route point for two networks (personal and guest).  A port (port 1) for personnel and port (port 2) separate for the guest.    Port 1 (staff) on the FW goes to a Dell connect 2724 with default config managed.   All staff resources are on the dell connect.  Also on the dell connect is a point of wireless access for staff.  Port 2 (comments) plugs directly into a guest wifi AP (separate from the staff).  Everything works.

  State:

  The wireless access point that we use is the Engenius EAP350 and it has the ability to have the SSID 8 each in their own VIRTUAL local area network.  I'm looking to move the two networks wireless on a single access point.

  To do this I moved the FW 2 port to a port of the printer dell connect (port 9) and put it in 2 PVID and changed the dell connect the port connected to the existing personal wifi AP (port 7) a trunk (tag 2) port.  all other parameters are always default.  Personal wifi is the vlan 1 and wifi of comments is vlan 2 and labeled on the AP.  My hypothesis is that them VLAN are marked with the AP, authorized by the dell connect port port trunk and then requests DHCP for VLANs we then go to the FW through port a and dhcp vlan 2 go to the fw on port 9.  It did not work.  So to remove the AP of the equation all together, I've done 10 on the dell port connect a PVID in vlan 2 also and plugged in my laptop.  Since the port 9 and 10 are the two access ports in vlan 2, all dhcp requests should be met by the FW on the correct subnet.  However, it did not work.  any ideas or examples that can be sent on the configuration of the access and trunk.  I am very well versed on them with cisco, but dell connect do it a little different.

  the AP can send some unidentified VLAN 1? If you are not correct, you will need to establish another VIRTUAL local network you can send Tags images for, for example, VLAN 3. And not use VLAN 1.

• DHCP and groups AP assignments

  I'm having a problem where I have AP groups works perfectly fine, but when a customer moves from one building to the other assignment DHCP from the 'first' AP group is preserved when the user accesses AP assigned to another group of AP.

  For example, Laptop1 has an 10.2.1.110 address in AP Group1. When the user moves to an AP in Group 2, the Laptop1 retains the 10.2.1.110 rather than get a new address of Group2.

  Traffic still works perfectly, but I need them to inherit the regimes of intellectual property of the AP group they moved (conditions of the application).

  Our configuration is very similar to this document: http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008073c723.shtml#configs

  We have a controller 4402 with 37 1131 AP all AP is assigned to a group AP in their respective buildings and DHCP VLAN and traffic works perfectly well in each.

  DHCP is offered by a Windows 2003 server as clients wired and wireless must be in the same subnet for the purposes of the application.

  The controller and the AP is in native VLAN 10.

  I'd appreciate any help to determine why the controller or the DHCP server is not recognize the change of the client subnet.

  It is a normal behavior as long as the customer can place an AP on Group1 AP to ap on AP Group2. If you want the device to re-associate one building to another, you need to place the ap on a different WLC with a different mobility group name. If all of the ap is on the same mobility group, then you will have the seamless roaming like what you see.