VLAN Basics

Similar Questions

• Reference Dell 6200 Voice Vlan

  Hello

  Could someone show the config complete for the vlan voice with a VLAN for data on the same port it please?

  I currently have all the switchports in one vlan 10 normal data, the phone system and phones are also in this vlan. However, I now want to put phones on one vlan separate voice sharing the same port.

  My current Config is:

  Configure

  database of VLAN

  VLAN 10

  interface vlan 10

  name of 'NETWORK '.

  Routing

  IP 192.168.10.1 255.255.255.0

  interface ethernet 1/g1

  spanning tree portfast

  switchport access vlan 10

  output

  In my understanding, I have to do the following:

  Configure

  database of VLAN

  VLAN 20

  interface vlan 20

  name of the "voice."

  Routing

  address 192.168.20.1 255.255.255.0

  interface ethernet1/g1

  spanning tree portfast

  switchport mode general

  pvid switchport General 10

  VLAN 20 voices

  output

  Thanks for any help you can give, it's urgent fairy we should have had this work tonight :(

  Here is an example of a configuration of VLAN basic votes for a port to have a phone and workstation on this subject, with each device traffic, separated from each other.

  Example:

  VLAN 100 is set up for voice *.

  VLAN 10 is set up for data. ****

  Console (config) # vlan VoIP

  Console (config) # interface ethernet 1/g20-1/g24

  Mode console # switchport general

  Console # switchport General allowed vlan add 100 tag

  Console # switchport General allowed vlan add 10 untagged

  Console # pvid general switchport 10

  Console # switchport general allowed vlan remove 1

  Console # vlan 100 VoIP

  Console # end

  There is also this white paper with some good info in there.

  www.Dell.com/.../pwcnt_voice_VLAN_support.pdf

  Hope this helps some.

  See you soon

• Selection extended DHCP and several VLANs

  I have a switch that has 2 VLANS: vlan 2 and vlan 3 - and both computers are connected to the switch where each PC is a member of one of VLAN.

  PC2 = VLAN2

  PC3 = VLAN3

  The switch is connected to a router that acts as a DHCP server with several 3 DHCP scopes for each of VLAN, basically a simple configuration "router on a stick".  This question has been confusing me for some time: How does the router knows what dhcp scope to assign an IP address to a particular computer?

  Let's say PC2 is now trying to get an IP address from the DHCP server, I know initially that he will send a DHCP DISCOVER broadcast to the router message and I assume that the router will know the VLAN demand coming as well based on the information contained in the package. But how the router discerns what scope to assign IP address to PC2 especially if I need PC2 to have an IP address in the subnet 192.168.2.0 and NOT 192.168.3.0 or vice versa?  The controls of such a choice?

  IP dhcp pool vlan1

  DHCP excluded-address IP 192.168.2.1 192.168.2.10

  DHCP excluded-address IP 192.168.3.1 192.168.3.10

  !
  IP dhcp pool vlan2
  network 192.168.2.0 255.255.255.0
  test.com domain name
  Server DNS 192.168.2.1
  default router 192.168.2.1

  !

  IP dhcp pool vlan3
  network 192.168.3.0 255.255.255.0
  test.com domain name
  Server DNS 192.168.2.1
  default router 192.168.3.1

  THX sc.

  Hi Sherwin,

  It's will be very simple. I guess that on the router configuration stick will have something like below.

  FAS int 0/0.2

  encapsulation dot1q 2

  IP 192.168.2.1 255.255.255.0

  FAS int 0/0.3

  encapsulation dot1q 3

  address 192.168.3.1 IP 255.255.255.0

  Now when a PC that is connected to the VLAN 2 send a DHCP broadcast this program is received by the interface that belongs to the same broadcast domain (VLAN 2). This broadcast is received by the Fas 0/0.2 and this has encapsulation dot1q sub interface 2 and so it will be part of the same broadcast domain (VLAN 2). If the router will search if there is no DHCP scope configured for the ip range on the interface sub Fas 0/0, 2. Now, router knows the 192.168.2.0 extended DHCP and assign the IP range of this scope to any PC in the VLAN2.

  I hope this helps.

  Concerning

  Najaf

  Please rate when there is place or useful!

• SGE2000p QoS for VoIP

  I am trying to increase our quality of telephone problems. Things like backup tapes, download heavy etc. are originally phones get all cracked. I don't know where to start. Everyone says of VLANS, but I don't know if this is the best choice. I don't know anything about QoS in the SGE2000P switches. I keep reading, but he gets no more clear. I need a little help direction. I see things on the VLAN, basic QoS, QoS advanced and do not know which route to go.

  I have 3 batteries of the total of 8 switches switches network segment all the same SGE2000P. The main chimney is connected to smaller piles by a fibre optic cable. Some computers are connected to the voip phones due to the absence of inside wiring of the building, but a lot of phones have a line dedicated to the switches.

  Consider phones like three switches of ports (because that's what they are).  A port is the phone, going to a single port and a port goes to a PC.  A switch when you set a port as a trunk you can tag the traffic for VLANs, create separate virtual local networks on a single physical link.  Similarly, on the side of the phone when you configure an IP to use phone a VLAN you say the switch to have a trunk port to your switch and the telephone to communicate on this VLAN tagged.

  The VLAN native is the VLAN untagged.  Computers don't understand VLAN and just send the traffic untagged so when you connect the PC to the back of the phone it will operate the same as it does now.  the difference will be that the phone will be on a different subnet and VLAN.

  Taking example of VLAN 100 for voice, you need to change the IP address of your IP PBX for something in a new subnet as 192.168.100.1/24 and create a port on a switch, a put in VLAN 100.  Connect to your firewall for routing inter - vlan.  Then find a way to get the phones IP address in the subnet and configs updated to use VLAN 100 and enter 192.168.100.1.  If you configure inter - vlan routing properly advance, you should be able to have a reboot of the phone, coming up on the data VLAN, get a new configuration that specifies the use of VLAN 100, reset again and this time come on VLAN 100 with the new address and function properly.

• For access to the VLAN specific after VPN

  Hello

  I have a SRX5308 and have set up a PPTP VPN server. I have four VLANS configured, say:

  10.0.A.0/24

  10.0.B.0/24

  10.0.C.0/24

  10.0.D.0/24

  and setting up the PPTP server is giving VPN clients

  10.0.F.20 - 29

  I am able to connect to the server and surf as "from the network. But how can I set up a road (?) so I'm able to access (or logically be attached to) devices on 10.0.A.0/24 my VPN client network?

  I have searched high and low for this but didn't find clear instructions on how to do it.

  Any help would be appreciated.

  Thank you

  Joakim

  Ah yes, that would explain

  IPSec is very easy to set up, don't be scared by the many parameters - you won't really do much with then. In regard to the full domain name, you will define in the client, you connect since so little matter where.

  With the Netgear IPSec client, it is really easy and the support team can help you make it work... There is a 30 day free trial so you can test it.

  There is also a free third-party client called Shrewsoft, it is quite easy to set up too, but some features seem to be difficult to make it work, I would recommend the official client to Netgear, but if you want to give shrew a go, I've written a small guide just in time for a very basic client-to-box installation with it.
  http://www.hexnet.se/srx5308-IPSec-VPN-with-shrew-soft/

  I think that there were some problems with the Shrew and certain firmware even if, at some point given, you couldn't perform mode config (i.e. what shrew own manual shows) but I can't work with the latest firmware of the srx5308... But I didn't spend too much time on this, I'm sure that it can be understood.

• SFE2000 and VLAN

  Before we begin, I want to say that I saw "' responses to my question, but never exactly what I'm looking for, so I create a new post.  I'm not a network engineer, so please forgive my ignorance.

  We are a public library.  We have a network that includes a number of branches, through the central site of the main library.  We show an ASA firewall. We have a Cisco3825 for local and a series of Cisco2800 Internet connection.  We use a system of 192.168.xx.xx, using DHCP network.  We have a number of PCs that are on the network access to the public and they are locked by using various software that prevent people to do much except get Internet.

  What we want to do is to put the public pc in their own network, always using our Internet connection, but not allowing them to see or access one of our 192. addresses.

  We bought a Linksys SFE2000 and it is my understanding that if I use it as a layer 3 switch, we can do what I suggested above.  However, I get so far and I reached my level of incompetence!  We want that all the public pc to come through the SFE2000 and although about allowing the public to use a wireless connection (but that is located).

  Can anyone offer suggestions or point me to a site that will help me?  Thanks in advance and again, sorry for my ignorance.  I look forward to hearing from anyone.

  Well, the router must have at least one interface. If the interface is used otherwise you can simply run it through the router as well.

  If you want to use the features of the ESF L3 basically configure you the VLAN as I've mentioned before. You enable L3 on the ESF, then you configure filtering on the ESF for the VLAN 'public '. Drop everything that goes in your charge of private VLAN.

  The problem is the connection to the router. We must define a new IP subnet for routing between the CPE and the Cisco. So, basically you will need a 3rd VLAN to connect with the Cisco. You can use a very small for this IP subnet if you wish. For example, add VLAN3 with IP address 192.168.99.101/255.255.255.252. The port on the Cisco configure IP address 192.168.99.102/255.255.255.252. On the ESF, set the default gateway 192.168.99.102. Who should route all internet traffic to the Cisco.

• Several VLANs on Cisco SRW2016

  I have recently bought me a SRW2016 to secure my network with VLAN. But my problem is, I have about 0 experience on how to set up.

  I painted a picture of how I wan't the network to look like.

  What I want is:
  VLAN2 = workstations, etc..
  vlan3 = wifi, xbox, etc.
  vlan4 = development

  Gateway is also running bind9/dns and the DHCP server on the network
  Gateway supports 802. 1 q on two NICS

  Picture of the way I wan't it: http://bildr.no/view/563844

  It's a basic configuration.

  You dedicate each port on the SRW one VLAN specific. You configure this port access mode and make it member of this VLAN specific. All traffic on this port will be up next to this VLAN.

  The port for the 802. 1 q, gateway is configured in trunk mode. Member of all do your VLAN. All the VLAN except the default VLAN will be 802. 1 q tagged. The default VLAN will remain untagged. Configure your gateway in the same way.

  That should do it. Make sure that your gateway is running a DHCP server for each of your VLANs, if you want to use the DHCP protocol and make sure that each VLAN contains a single IP subnet.

• SGE2000 / questions SRW208G VLAN

  So we have a little SGE2000P and several SRW208G more, and it was decided to use a GSM7312 for basic L3 functionality (price was among the main issues to be considered, we have found nothing else suited our needs of features in this range). We have just received the GSM7312, seized of the whole of the network was flat

  We have several VLANs that need to communicate with some shared resources on a particular VIRTUAL local network. A VLAN mentioned individual will, among other things, the domain controller (make DNS/DHCP) and our RAS in a box that does also all web content filtering, RAS area is directly connected to our line of T-carrier.

  right now, everything is in 1 VLAN pointing to the RAS area as its front door. currently all EMS/SRW switches are also directed towards the RAS area as a gateway.

  So now we have L3 functionality in place and can affect the IPs to VLAN, am I right to say that all the SEMs and SRWs must point to as default gateway GSM, while GSM only points to the RAS area as its entrance door?

  What about pushing DHCP from the domain controller in 1 VLAN to all others? I see that both the EMS and GSM support DHCP relay - what do I have to use? Something doesn't seem right about this... for example. Let's say I have the ms in the VLAN 200 (192.168.2.0/24) and VLAN 300 (192.168.3.0/24) and 400 (192.168.4.0/24) customers. If the switch transmits a broadcast DHCP request to the domain controller, the domain controller is going to know what scope/pool to give the address of? The server would be blind to the fact that the request was relayed to all, and even less should it been relayed from a knot of VLAN 400.

  There are a few resolutions in my mind to this problem, but I don't know that I'm barking all the good trees.

  One thought would be to establish special reserves for DHCP leases by MAC address in DHCP server pools (assuming that the destination MAC is not changed when the switch relay... I would even consider that at all until I typed all this).

  Another idea would be to multihome server and place it in each VLAN unique just to serve DHCP addresses

  Another idea would be to buy an 802. 1 q capable NETWORK card for the server and the trunk all the VLAN to it.

  These two little seems to defeat some of the purpose of VLAN'ing because network that I placed once more at least 1 server in each area of dissemination of layer 2.

  Someone please tell me what single thing I'm on

  1. your box of RAS is already a router. This is your default gateway to the internet. The routes on the RAS area are to tell her at what router it traffic for what IP subnet. For example, the traffic of 10.10.71.0/255.255.255.0 must go the GSM. So:

  2. you must add 3 routes on the RAS server. And on the domain controller to route traffic directly to the correct gateway, you must add the same routes. Otherwise the DC would always send the traffic to the RAS hence it is send to the mobile PHONE, even if it was possible for the domain controller to send it directly to the GSM. A route tells a computer where to send a specific IP traffic. You need the transatlantic lines to suite of destinations on the AR and the domain controller:

  10.10.71.0/255.255.255.0
  10.10.30.0/255.255.255.0
  10.10.40.0/255.255.255.0

  The gateway to all these three subnets is GSM not the RAS. Let's not the 10.0.2.3 that you have suggested. The correct IP address is 10.0.1.230, which is the IP address of the GSM (the next router on the path to these destinations). These roads should be persisted. You can add at the command prompt, or I think you can also add them to RRAS.

  3. you're merging doesn't have anything by doing this. The GSM and the RAS will be routers and therefore only to route traffic between subnets. In so doing, they provide connectivity. But it is not fusion. You would merge networks if you put in a bridge instead of a router or switch.

  4. the Handset will always carry the traffic according to its routing table. By default, the routing table contains all subnets to which it is directly connected. The routing of the GSM table has entries of routing for all four IP subnets to which it is connected: 10.0.0.0/255.255.0.0, 10.10.71.0/24, 10.10.30.0/24 and 10.10.40.0/24. If the mobile PHONE receives a packet for any of these IP subnets it will forward it to the destination in the VLAN respective. If the IP address is not in these four subnets it passes the packet to the gateway by default unless you define a static route. For your configuration, you don't have to add the routes to the mobile PHONE. He already knows what he has to know.

  5. the change of IP address you want is not possible: you cannot configure a VLAN 10.10.0.0/255.255.0.0. It is not possible. The 10.10.0.0/16 VLAN consists of all the IPS 10.10. *. *. If you have a VIRTUAL LAN that you cannot have another VLAN with IP address 10.10.30.0/24. Any IP subnet that is connected to a router must be different. If the mobile PHONE has two VLAN connected 10.10.0.0/16 and 10.10.30.0/24 he wouldn't know where to send the traffic to 10.10.30. * because this IP address is routable two different VLANs. You can only move servers to a subnet as 10.10.1.0/24 or similar. It would be unique in your configuration.

  6. There is no "L3 VLAN. A VLAN is always a VLAN. It's always layer 2. You can consider each VLAN as a completely separate physical unmanaged ethernet LAN switching. VLAN is simply a technique to have several LAN separated on a single device (p. ex. 1 managed switch with 4 VLANS instead of 4 switches unmanaged separated). An L3 switch is just another word for a VIRTUAL local network router. It's a L2 switch with a built-in router. There's still that L2 VLAN. But it can also route between different IP subnets in the connected VLANs.

• Question put in basic network

  May switches service nets under different?

  I work with a company that uses a kit EZXS16W switch 16-port workgroup to which all nodes are connected.

  I put in a server in a company where I want to isolate 6 of 16 employees who are connected to this switch and make the members area of my server.

  The company has a T1 connected to a box which is apparently managing DHCP and IP numbers. It's using the standard 192.168.1.x subnet.

  I don't think I can I achieve what I want by hanging just switch server as just another node and then create a different subnet for him and six users, because that would take them on the net under Internet happens.

  The EZXS16W is apparently not managed, so I can't set up a VLAN.

  But the server has two network cards and is set to be a controller of domain, NAT, Firewall and DHCP server. So I ask myself, can I connect the two network adapters on the server to the switch so that a network adapter is the sending/receipt of Internet traffic on the main (192.168.1.x) subnet with the other configured manually to a different subnet (10.0.2.x) network adapter, and then manually configure the 6 users to use 10.0.2.1 gateway by default so I have basically two networks operated by the same switch?

  OR I need to connect my server to the main switch with a nic, buy another switch to connect to my second nic and do six users will connect to the second switch?

  It may be possible that if you want to communicate, if you want to have access to internet at the 6 users with 10.0.2.x network, it won't work...

  Even if you connect your server to the main switch with a nic, buy another switch for you to connect to my second nic and do six users will connect to the second switch, it does not connect to the internet...

• VLAN will not work on Interswitch link SLM2008 SRW2008MP

  I have a SLM2008 (SW01) and a SRW2008MP (SW02), these are inter connected both on port g1. G8 SW01 port is connected to the HDSL modem my ISP (off-grid). Connected G2is inside an ASA5505, offering my inside of network port. G7 and g8 SW02 port is connected outside 2 servers. I created a VLAN 2 on both switches. SW01 has 2 PVID on port 8, Acceptable frame types = All and enabled the capture filter. All other ports has same config except PVID on these are 1.
  On SW02 I tried several setting of VLAN on ports 1, 7 and 8. NO CHANCE!
  In general, I tried g1 as trunk, joined the untagged VLAN1, VLAN2 tagged, Acceptable frame types = All, PVID = 1, penetration fltering on. Ports g7 and g8, I tried with the access mode both in general mode, with several combinations of tag/untagged etc etc.
  I am not able to pass all traffic to the outside.

  Anyone? Help.

  Thanks in advance

  HKL

  Basically, what I want to achieve is; using a vlan between the 2 switches create a topology as if I had 4 physical switches, connected 2 and 2. No traffic should pass between the 2 pairs. No servers or other resources should be informed (or care) if they are on the physical pair 1 (VLAN1) or physical to pair 2 (VLAN2).

  As I see, or understand, the only difference between 4 physical switches and 2 physical (using the VIRTUAL local area network), it is that we need two trunk VLAN through, instead of having 2 physical connections intercommutation

  All outside routing is handled by the ASA (from vlan1) to VLAN2, the server will be directly using public IP address.

  In a concern for information inside subnet is 192.168.1.x, NAT by ASA at the public address 62.89.36.34/24 outside VLAN2 will be directly connected and use the servers 62.89.36.45 and 62.89.36.46

  GW = 62.89.36.33

  Hope this will make sence?

  BR

  JK.

• HP Procurve vlan voice with trunks

  Hi all

  I am a trained guy cisco, so I try to transfer my knowledge to the HP Procurve switches but it takes a little help to obtain VLAN etc set up.

  What I have is 4 switches, 3 at the access layer to the and 1 to the base and distribution.

  I want that switches to a trunk of the base and distribution layer 2 interfaces access layer allows to increase the speed of 2 instead of 1 gigabit uplink. Also, I want is that 2 VLANS is set up for separate voice and data. I want that all ports to be able to take in charge a PC or a VOIP phone. I put the phones to automatically tag the tag of vlan for the vlan voice, but I want all traffic to forward the link to resources shared at the base and distribution layer.

  From what I understand, so I need to:

  Configure a network interface on the access and use of basic/distribution layer switches: b1 - b2 trk1 lacp trunk

  Add VLAN for voice and data and assign vlan voice.

  The problem I have is the tag-no identified parameters.

  I tag vlan trk1 voice and set the priority of the qos to 6 and then comes to create the vlan data not marked on trk1?

  the config I've written so far is:

  b1 - b2 trk1 lacp trunk
  show trunks
  spanning tree
  spanning tree force version rstp operation
  voice VLAN 100 name
  voice
  Tagged trk1
  QoS priority 6
  data name VLAN 200
  not tagged trk1

  is this correct or am I missing something here?

  Thanks in advance!

  Hello:

  You can also copy and paste your message into the HP Business Support Forum - section Procurve switches.

  http://h30499.www3.HP.com/T5/ProCurve-provision-based/BD-p/switching-e-series-Forum

• Unable to see 'add a trunk switchport allowed vlan' lines in the running-config

  Hello!

  I use a configuration on a bunch of N3000 and N4000 switches (with firmware 6.3.x.x). I try to create the VLAN on the links and I am facing some problems (maybe).

  In the configuration of the interface if I send the command 'trunk switchport allowed vlan add [vlan]' and check the running configuration I can't see the line.

  The command show vlan shows VLAN seems them ok.

  I have a few configuration files archive and in these cases him vlan said add visible function. What could be the cause of this difference?

  Hi Adam,.

  OS6 is sometimes unpredictible :) Basically, you must use Add or remove the commands when you have got all the restrictions on the configured trunk.

  switchport mode trunk add all the VLANS on trunk (including for example VLAN1) port. At this point, you can delete only the VLAN of the trunk. This is the reason why you don't see the configuration changes to the example runn.

  Initially limit the VLAN allowed on trunk port starting with:

  switchport trunk allowed vlan "vlan numers '

  (eg. trunk allowed vlan switchport 10 with allowed vlan 10-25 range or after coma allowed vlan 10,11,15)

   

  After that you can use Add or remove commands you want :)

  Best regards

  GB

• How VLANs ' IP subnet ing works with based port of VLAN (series N2000 and N3000)

  Hi all

  I have a small pile of x N3024 2 acting as my heart L3 with a lag of 2 x 10 g down to a stack of x N2048 5 acting as L2 switch for my PC workstations.

  Workstations are that all on the port assigned VLAN 10 (switchport access vlan 10). I have a bunch of developers who want to access without restrictions more or less to assign random IP addresses for their VM (Virtualbox and VMware) Workstation.  As you can imagine, I would like some control over this situation.  the powerconnect guide I described features of subnet IP VLAN but does not seem to enter in how it works and interacts with the port actually function vlan assignments.

  What I currently have is the VLAN 10 assigned to a segment that support the subnet 172.100.x.x which dates back to our base of L3 for routing to other segments. What I want to do is to configure the VLAN based on IP and then load the dev is to config their VM with another IP range, say 10.10.x.x.

  Theory here is, I set the L3 core with say 20 VLAN and an IP to register in L3 path between subnets and then configure the battery switch L2 workstation with IP - based VLAN to recognize 10.10.x.x and separate on VLAN 20.

  However, I think the simplified here question is if I have a nail up to 10 ports VLAN, will the than basic work IP subnet VLANS as I want only it? Or, I need to create a subnet IP VIRTUAL local area network for the two IP ranges? I have to remove the assignenment VLAN per port and are based entirely on the treatment of subnet IP VLAN?

  If there is a better RTFM on this topic you can tell me I would appreciate it

  Thank you!

  I ended up calling specialists... great Dell technical support here.

  In fact, the IP based VLAN works very close to what I want to achieve. Missing from the user guide is that the port needs to be in the mode. Ports using switch port mode and bound to a VLAN just didn't work... probably because the vlan IP based did not differ from the port binding. Dell support has suggested to use the trunk mode, but my answer is finished using the general mode; any traffic not referenced, PVID located my usual LAN vlan ID and acceptance of port traffic of new vlan based on IP. In this way, I'm able to have a physical host DHCP on the corporate LAN and a virtual machine on that host to bind to a different subnet which is then isolated in the new NAV based on IP.

• Can not do anything on the VLAN ping on 6248

  Hello

  I've spent a day and a half trying to solve this problem, but I'm not getting anywhere. Here is a breakdown of the test configuration database.

  Port 1: Connected to the existing network (if I can get to the host ESXi from my PC)
  : 3 my ESXi host is connected to this
  Virtual machines are tag VLAN through port ESXi group properties.
  All VLANS have 1 VM except VLAN 10, which has 2.
  All the VLANS are IP address ending with 24 par.1 the subnet mask.
  All virtual machines have the corresponding default gateway pointing to the IP of the VLAN (XXX1)
  I am able to get the IP address of the DHCP server to different VLANS.

  Things that work:
  From a virtual machine, I can ping to IP of any VLAN (so MV in VLAN 10 can ping IP of the VLAN 20)
  The console, I can ping IP of any VLAN

  Things that DON'T work:
  The console, I cannot ping any computer virtual IP.
  From a virtual machine, I can not ping any address (including the virtual machines in the same VLAN)

  Here is my config running:

  ! Current configuration:
  ! Description of the system "PowerConnect 6248, 3.3.7.3, VxWorks 6.5.
  ! 3.3.7.3 system software version
  ! Passage mode is configured as disabled
  !
  Configure
  database of VLAN
  VLAN 10,20,30,40,50,300
  VLAN 10 1 routing
  VLAN 20 2 routing
  VLAN 30 3 routing
  VLAN routing 40 4
  VLAN 50 5 routing
  VLAN routing 300 6
  output
  unicast SNTP client enable
  customer survey SNTP 1024 timer
  SNTP server 0.north - america.pool.ntp.org
  clock timezone-7 minutes 0
  battery
  1 2 Member

  output
  IP 192.168.8.250 255.255.255.0
  default IP gateway - 192.168.8.230
  IP routing
  IP helper-address 10.80.10.10 dhcp
  interface vlan 10
  name 'server '.
  Routing
  IP 10.80.10.1 255.255.255.0
  output
  interface vlan 20
  name "printer - Switch."
  Routing
  IP 10.80.20.1 255.255.255.0
  IP helper 10.80.10.10
  output
  interface vlan 30
  name "Workstation".
  Routing
  IP 10.80.30.1 255.255.255.0
  IP helper 10.80.10.10
  output
  interface vlan 40
  name "phones".
  Routing
  IP 10.80.40.1 255.255.255.0
  IP helper 10.80.10.10
  output
  interface vlan 50
  name of the 'Camera '.
  Routing
  IP 10.80.50.1 255.255.255.0
  IP helper 10.80.10.10
  output
  interface vlan 300
  name "router".
  Routing
  IP address 192.168.1.250 255.255.255.0
  output
  user name 'root' password XXXXXXX level encrypted 15
  l2relay DHCP
  DHCP l2relay vlan 10,20,30,40,50
  !
  interface ethernet 1/g1
  switchport mode general
  output
  !
  interface ethernet 1/g2
  switchport mode general
  output
  !
  interface ethernet 1/g3
  spanning tree portfast
  switchport mode general
  switchport general allowed vlan add 10,20,30,40 tag
  output
  output

  Looking at the config on the switch, I can't predict whether the switch. The config is pretty basic, and the only way I guess whether the switch is if there were problems with the overall performance of the network. Love packages ignored, times of high ping, etc. Doing some research I found a few posts of blogs, KB and forum various with some things to look at what can help.

  http://msmvps.com/blogs/netman66/archive/2010/03/25/VMware-vSphere-4-client-slow-to-load-fixed.aspx

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1027836

  http://www.v-front.de/2011/07/improve-your-vSphere-clients.html

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1029665

  http://hardforum.com/showthread.php?t=1698368

  http://d1it.WordPress.com/2010/12/23/slow-vSphere-client/

  See you soon

• Priority of VLAN on a Trunk port

  What is the easiest way to give a single VLAN a higher priority than the other on a trunk port?  I have two VLANS, VLAN 10 and by default.  I want to VLAN 10 to have a 802 .1p priority 6 and I want the default VLAN priority of 2.  Is it possible in basic QOS mode, or do I need access to advanced mode?

  Thank you!

  This networking wiki has lots of good information and follow. Looking at what you have planned, everything looks good to me. Let us know how it goes with the implementation.