iSCSI - dedicated VLAN vs traffic switch

Similar Questions

• 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.

• What configuration of VLAN requires a switch connectivity defined as an access port?

  What configuration of VLAN requires a switch connectivity defined as an access port?

  By external switch tagging

• The VLAN on a Switch Standard

  I am currently creating a new environment and we have a number of VLANS trunked together, I created a Standard switch for our virtual machine-to-machine network and the DMZ network, have each VLAN resources shared.

  What is the best way to do it?

  That I should...

  Create a vss and create groups of ports of individual virtual machine for each VLAN IDS? (for example, a switch for virtual machine VLANS and a switch to DMZ with groups of individual ports?)

  Or should I create just a switch for each with all 4095 active?

  Hey, as previously stated, the large traps with it would be the single points of failure, but since you're ok with it, I'm going to shut up

  Configuring VMware site seems ok, if you do not touch the vSwitches default security settings.

  Regarding the loss of connectivity, I am looking for the reason outside of VMware (VLAN not on two physical switch ports, bad IP/gateway settings within the operating system prompted, etc..)

• Vlan trunk between switches traffic encryption

  Hello

  Can someone guide me to some documents and other resources on how to encrypt the traffic between 2 switches. The switchces will be connected with fiber and use the marking dot-1 q. And I wan't to encrypt all traffic to shared resources.

  I was thinking about L2TP, but I have not found a good description on how to implement this. I have two 3750 switches, I thought I could use.

  Thank you for any input,

  Kind regards

  Paul Mathiesen

  mnemonic

  Norway

  Hello

  Thanks for the reply. I had a look at effect and it seems good. I would have liked to use something P2P but also limit the amount of MAC addresses on the "wire". But let me first give you an understanding of the task:

  We have two sites, linked by fiber, and we want to create a trunk VLAN everywhere and to expand the broadcast domains to you another site.

  The carrier FOOL, has a limitation on the number of MAC addresses, they allow the service to fiber, 100.

  We also encrypt the datatraversing this connectivity.

  MACsec wuold work 100% exept the source and dstination MAC addresses are still sent (at least according to https://docs.google.com/viewer?a=v&q=cache:LEf2qOmYZyYJ:www.ieee802.org/1/files/public/docs2011/bn-hutchison-macsec-sample-packets-0511.pdf+&hl=en&gl=za&pid=bl&srcid=ADGEESgmAHXpDOY0RBAE-Rv1HDpu_C_gkeSPN4cv6NGgyP0M1aXVu0UqzCfxo8t_P41ep6J37k4OLKnjfp1M9hoTDHxY22WGz2h7yB7YRLyPvRUbGS8TICzvEMlG92xqbhy6RWFugmnj&sig=AHIEtbTfu0LQIJejdYidE6yzq4lpPifxjQ
  )

  And who tempt me to eat in the limit of MAC 100.

  Ridiculous I know, but we are looking for an out-of-the-norm plan...

  Thank you

• Routing between two VLANs on a switch in series SG300

  I've seen a lot of messages from people with problems of traffic between the two routing VLANS with some complex examples.  Can someone show a simple example for a SG300 switch (in layer 3 mode) to set up the two VLAN and send the traffic between VLANS without an external router?

  VLAN1 10.10.10.0

  VLAN2 10.10.20.0

  I tried to do through the UI and can't seem to make it work.  It seems that it must be very simple, so maybe I'm missing something in the GUI.

  Hi Chris,

  I did 5 minutes of recording that showed how I configured the two VLAN on my SG300 switch and layer 3-switched between the VLANS.

  You have no trouble getting to the GUI, so you will have no difficulty to setup in a few minutes...

  • Be sure to use the latest version of the SG300 package, with a bearable CLI.
  • to save your changes to the configuration at the end of the process.
  • the IP addresses that you create will be the address of default gateway for PC hosts on VLANs specified.
  • Recording can be interrupted at any time to perform configuration operations.

  Recording is now available on the website of the WebEx service. Click on the link below to read:

  https://Cisco.WebEx.com/ciscosales/LSR.php?at=PB&SP=MC&rID=55688352&RKEY=05e1fc5fff0d05da

  Configuration of VLAN

  Monday, October 24, 2011 11:02 New York time

  5 minutes

  Have fun

  Best regards, Dave

• Lost of acceso del cluster Datastore iSCSI cuando uno los back switches caer al vSphere

  Hola,

  Estoy serve a vSphere en alta availability, conectado al por iSCSI storage environment. Detallo el entorno:

  Back switches Procurve 2920 connected between por ellos a trunk con back cables from FC con una VLAN para iSCSI.

  An experience past 1 G an iSCSI, cada uno conectado a uno los con servidores Proliant DL360 Gen9 red back of back ports. Con el por iSCSI initiator software from VMware.

  Storage formed por back nodos HP 4330 en cluster, cada con UN nodo StoreVitual-dependent back red puertos y cada puerto a one of the switches

  The config as he hecho Los nodos vSphere ha sido a vSwitch, con VMKernel back in the same red y las back vmnic, each of ellas activa en UN vmkernel y unnused in el otro, las following past of vmware. The balanceo politica're RR.

  TODO works correctamente, except in el momento in el as el switch Procurve 1 cae. Cuando esto happens to pierde el acceso a los data warehouses in los nodos ESX, voy al vCenter until back y en the config-> storage, the doy pestana a Rescan All, momento in el than vuelven a appear.

  ¿alguien could help me a saber porque esto happens y como lo puedo did?

  Gracias,.

  Ya hemos sown el problema, y the respond.

  Esta spend las premium MAC por un switch del puerto y por el trunk al momento apagar el local switch, esas MAC duplicadas corresponden a los vmk of vMotion. Para el trafico vMotion tenemos breakfast back redes independientes as no switch should dirty cada don't con lo than no hace falta that vean between switches. Hemos quitado esa vlan trunk del there is no tenemos el problema!

  Saludos!

• VLAN function 6248 switch IP address

  We have a nice and simple class C private address space private on 4 x Dell 6248 switches. We are running out of IP addresses. We could change the netmask (add more bits), but who is to reach each node and potentially finding devices that do not work with anything other than 24. We have a lot of old material that we must keep functioning. In addition, we want to limit emissions, since here we have projects that do a lot of UDP broadcasts. If each project in one VLAN, the load on the switches would be less. Hosts on VLANS must get to the common servers well.

  So I did some reading and thought we would use of VLANS, routing and others to have several C class spaces. We turn the material around the office at an alarming rate so I thought that an IP based VLAN would be an excellent solution. I have problems with the documentation and configuration to make it work.

  We have 2 x 2716 Dell and 2 x Dell 2724 switches in the mix as well. They are connected to the 6248 s switches dumb and all seems to work now.

  I created 2 VLAN and reports the following:

  Curetes #show ip interface vlan 2

  State of the Routing Interface... Down
  Primary IP address... 192.168.3.1/255.255.255.0
  Routing mode... Enable
  Administrative mode... Enable
  NET before realized emissions... Disable
  Proxy ARP...................................... Enable
  Local Proxy ARP... Disable
  Statement of assets... Inactive
  MAC address... 0019.B998. E71E
  Type of encapsulation... Ethernet
  IP MTU......................................... 1500
  Bandwidth...................................... 10000 Kbps
  Destination unreachable... Activated
  ICMP redirects... Activated

  I am running firmware V3.3.3.3. I have improved the switches on the weekend of 2.2.0.3 I read that VLAN does work well with this version.

  I can't find in the documentation "Setup Guide" or "CLI_EN.pdf" how to get the "Routing Interface status" that up to.

  My config running is pretty simple:

  ! Current configuration:
  ! Description of the system "PowerConnect 6248, 3.3.3.3, VxWorks 6.5.
  ! 3.3.3.3 system software version
  ! Passage mode is configured as disabled
  !
  Configure
  database of VLAN
  VLAN 2-3, 10-11
  VLAN 2 1 routing
  VLAN 3 2 routing
  subnet of VLAN association 192.168.3.0 255.255.255.0 2
  output
  hostname "curetes.
  Select the SNTP client distribution
  192.139.238.68 SNTP server
  battery
  1 2 Member
  2 2 Member
  3 2 Member
  4 2 Member
  output

  IP 192.139.238.79 255.255.255.0
  default IP gateway - 192.139.238.27
  IP routing
  interface vlan 2
  name '192-168-3-x-address. "
  Routing
  address 192.168.3.1 IP 255.255.255.0
  output
  interface vlan 3
  Routing
  output
  level XXXXXXXXXXXXXXXXXXX username 'admin' password encrypted 15
  output

  Question (in order of importance):

  What is the best way to go to solve my problem (limit/exhaustion of Ip address space broadcast domain)?

  How to make "Routing Interface Status" on VLAN 2 upward? Do I need it upward?

  How to configure a VLAN to do what I want?

  Thanks in advance.

  Don

  Yes, that's my suggestion.

• How can I assign some VLAN in Virtual switch?

  I have ESX 4.0 installed on two IBM Blade hosts that are in a HA cluster to enable vMotion.  I have a virtual switch created on each host.  Virtual machine connect to the same switch.  I added a new virtual machine to on one VLAN separated.  I have a few "How to"... questions:

  1. How can I put the new virtual machine in an assignment of VLAN different from other virtual machines?  (I think it's through groups of ports but I always read)

  2. can I put several VLANS on the whole virtual switch? (If Yes, what is the snytax? "43; 40 "or"43, 40' or "43-40")

  3. What is the best practice for this kind of Setup?

  Thank you

  Stuart

  Hello and welcome to the forums.

  1. How can I put the new virtual machine in an assignment of VLAN different from other virtual machines?  (I think it's through groups of ports but I always read)

  Port groups - you're right.  Create a port group, and then assign the virtual machine this connection.

  2. can I put several VLANS on the whole virtual switch? (If Yes, what is the snytax? "43; 40 "or"43, 40' or "43-40")

  Yes, you want to create a new port group for each VIRTUAL LAN required in the vSwitch.

  3. What is the best practice for this kind of Setup?

  There is a lot of information around this in the Guide de Configuration ESX.

  Good luck!

• VLANS and virtual switch

  Looking for advice.

  Currently, I have our Vmware 4.0 servers configured with 4 NICs.   vSwitch0 (2 network cards) and vSwitch 1 (2 network cards). Switch 0 to several groups of ports for each vlan I have (on 8 VLAN) switch 1 a the VmKernel for NFS.  It works very well, I have a new server on order and I thought that I have would consider this configuration to make sure that I am maximimzing my performance.

  I get a little confused, it seems that I could create multiple vSwitch with the same NIC 2 and have a group of ports under each of them for the Vlan vs 1 vSwitch and several groups of ports.  If this is incorrect, please correct me.

  Benefits or drawbacks to this?

  If you had 4 network cards and several VLANs using NFS for storage, which would be the best config for performance and failover?

  What happens if I had 6 network interface cards (new server comes up with 6)?

  Thank you

  Take a look on:

  Best practices for the design of cards and vSwitches NIC

  Note: a NETWORK adapter can be connect only to a vSwitch, not for many.

  André

• iSCSI multipath with Distributed Virtual Switch error

  Ive followed the iSCSI SAN guide and have iSCSI multipathing works well with a regular virtual switch. Ive cancelled all configurations and have begun to see if I can get this working with a dVSwitch.

  I get the error "Add Nic failed in IMA"

  Someone at - it ideas?

  I recently worked on a case of iSCSI with VMware support and they mentioned a known issue with iSCSI and dVS, this is also described in the release notes, but may still have a problem. You can contact the technical support for confirmation.

  • ESX/ESXi 4.0 4.0 does not support the compatible ports with DVS binding configuration VMkernel network interface cards

  If you configure compatible with vNetwork Distributed Switch port binding NICs VMkernel, the operation fails if you enter esxcli swiscsi nic adds - n vmkx d vmhbaxx and vmkiscsi-tool - V - a vmkx vmhbaxx orders through the service console or the vSphere CLI.

  Workaround: Use only inherited vSwitch VMkernel NIC for port binding.

  =========================================================================

  William Lam

  VMware vExpert 2009

  Scripts for VMware ESX/ESXi and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

  repository scripts vGhetto

  VMware Code Central - Scripts/code samples for developers and administrators

  http://Twitter.com/lamw

  If you find this information useful, please give points to "correct" or "useful".

• Trunk Vlan 1 on switch Dell 3524

  Hi all...

  Need help please!

  I want to configure the VLAN 1 on dell 3524 because VLAN 1 has IP DHCP from the Mikrotik,

  the default VLAN 1 trunk mode configuration?

  Thanks :)

  By default, VLAN 1 is the VLAN native to an interface configured in mode switchport Trunk/general. If you want 1 VLAN tag, you need to change the VLAN native to something other than 1 and then tag VLAN 1.

  Example:

  Console (config) # interface ethernet 1/e16

  Console switchport mode trunk #.

  Console # switchport trunk vlan 99 native

  Switchport trunk console # permit vlan add 1

  You can also use the general mode.

  Example:

  Console (config) # interface ethernet 1/e16

  Mode console # switchport general

  Console # pvid general switchport 99

  Console # switchport General allowed vlan add 1 tag

• NIC physical or virtual dedicated & vlan for vCenter Heartbeat?

  I am writing a paper on the recommendations and requirements of vCenter Heartbeat 1...

  It seems unclear to me if the functionality of pulsations of vCenter need dedicated physical NIC when VC is running in a virtual machine?

  VC goes. Heart rate requires dedicated physical NIC or only vNIC & lt;-& gt; dedicated vSwitch is required?

  Thanks in advance

  : o).

  I guess that your VC is running in a virtual machine? VC with Heartbeat requires a minimum of two vNIC with every heartbeat (each vNIC, but the first) vNIC on a dedicated vSwitch. Since a physical NETWORK card can only below a unique vSwitch, this configuration requires at least two cards physical network. Basically, this means that you need at least two network adapters for and two physical network adapters to configure the heartbeat in a VC run in a virtual machine. For redundancy reasons, it makes sense to have multiple physical network cards in a vSwitch for grouping of NETWORK cards. Therefore, you should really have at least four physical NICs (two by vSwitch) in a production environment.

• Question about VMKernel iSCSI traffic and VLANS

  Hello

  This is a very fundamental question that I'm sure I know the answer too, but I want to ask him anyway just to reassure myself.  As a precursor to my question, the configuration of my ESX infrastructure is best described here: http://www.delltechcenter.com/page/VMware+ESX+4.0+and+PowerVault+MD3000i.  Or more precisely, we have two controllers MD3000i.  Each controller has two ports and each port is configured on two different subnets, with every subnet connected to the different switch.  ESX host are connected to two switches.  The only difference for the guide, is we have two MD3000i configured the same, connection to the same switches.  Each MD ports is configured on the same subnet, but different IP addresses.

  At present, we are in the process of upgrading our two iSCSI switches of humble Dlink DGS - 1224T to Cisco 2960 T of.  The switches have been and continue to be dedicated to iSCSI traffic, however, I'm trying to set up VLAN s on the side of the switch.  Originally, we used the default VLANS on switches, however, after you have added an another MD3000i, noted the Support Dell best practices is to separate each on its own subnet and VLAN MD3000i iSCSI traffic. This would result in iSCSI 4 VLANS, two on each switch and two for each MD3000i.  Firstly, is this in fact of good practices?

  Second, if I migrate preceding 4 iSCSI VLANS, as each switch port will actually be an access port, will there need to complete the VLAN ID field in the VMKernel configuration page? Presumably, this field is used when the tagging VLAN is used, but as our switches do not need any other rocking trunk (as they are dedicated to iSCSI traffic), there should be no need to fill?  I guess it would be prudent to keep the two existing subnets, create two new subnets and make changes to an MD3000i and connection of the ESX host.  Provided the switch and switch ports has been appropriate configured with VLAN on the right, the rest should be transparent and he wouldn't be Intel VLAN in all ESX hosts?

  Would be nice to get answers and thank you in advance!

  Gene

  (1) Yes, it is best practice for ESX iscsi, having an independent network and vlan for iscsi traffic.

  (2) No, there is no need to mention anything in the area of vlan, if you use an access port. Its a mandatory thing than a choice. If you supply the id vland with access port, it loses connectivity.

  Please explain a bit why you need to create two different virtual local networks for each MD3000i. You are going to use several on the same ESX box iscsi storage? Alternatively, you use only a single iscsi and use these 4 ports for the same single VMkernel interface?

  NUTZ

  VCP 3.5

  (Preparation for VCP 4)

• Cannot connect the switch Cisco Cisco SG300 - 28 p spend and traffic through VLANS

  Try to connect the Cisco SG300 - 28 p switch to another switch and proceed 2 VLANS between them.  Not doing any circuit.  If I connect a computer to the port on the SG300 - 28 p I can access the VLAN 2 and take a DHCP address. However, when I connect to another switch on the port and connect it to a port on another switch secondary I am unable to access VLAN 2 and pull an IP address.  I checked that the works of secondary switch (WS-C3560G-48PS-S) connected to the other 3500 s, but not this latest SG300 - 28 p.  Here's the configuration for both, I'm leaving areas that shouldn't matter and add if necessary.  Try to connect the SG300 - 28 p Port 26-WS-C3560 Port 1 port.  Once again, if I connect a computer to port 26 on the SG300 - 28 p I access the VLAN 2 as expected, but not when I connect to channel 2 on the secondary switch.

  Cisco SG300 - 28 p

  !
  interface vlan 1
  Internet name
  !
  interface vlan 2
  LAN name
  IP 172.20.5.11 255.255.0.0
  no ip address dhcp (this is the VLAN I'm moving)
  !
  interface vlan 3
  private name
  !
  interface vlan 4
  name of Nortel
  !
  interface vlan 101
  name Video_Project
  !
  interface gigabitethernet26
  Description VLAN2-ACCESS-CISCO3500
  switchport mode access
  switchport access vlan 2 (this goes to port 1 on the other Cisco 3500 switch to provide access 2 VLAN)

  Cisco 3500

  !
  interface Vlan1
  NATCO Internet description
  no ip address
  no ip route cache
  no ip mroute-cache
  !
  interface Vlan2
  NATCO LAN description
  IP 172.20.5.13 255.255.0.0
  no ip route cache
  no ip mroute-cache (this is the VLAN I'm moving)

  !
  interface Vlan3
  Description LHPrivate
  no ip address
  no ip route cache
  no ip mroute-cache
  !
  interface GigabitEthernet0/1
  switchport access vlan 2 (this is the port that I connect to the SG300 - 28 p)

  !
  interface GigabitEthernet0/2
  switchport access vlan 2 (this is the port I hang my computer to and trying to access VLAN 2 other switch)

  Hello

  Yes, STP is the problem here. As you can see on your release of the Cisco 3500 switch, port Gi0/1 is BKN (The FEW is a shortened form of "Broken").

  This is caused by an incompatibility of versions PLEASE used between the two switches. Small businesses (including series SG300) switches are use legacy STP or Rapid STP (your case), but uses templates to business (such as catalyst 3500) PVST + (each VLAN spanning tree version of STP).

  Two versions between group of switches are compatible only under certain conditions. Important condition is that the two switchports needs to use a VLAN 1, vlan access/native and not any other number VLAN.

  It is to make your communication work, you must:

  • disable the STP at least 3500 Cisco switch:
    • on overall global (Switch (config) # no vlan spanning tree 2)
    • or by the base interface (switch(config-if) # no vlan spanning tree 2)
  • change the configuration of your connection between two switches by following the path:
    • change the switchport trunk (trunk switchport mode) mode
    • do 1 VLAN as native vlan (vlan switchport trunk native 1)
    • Towing VLAN 2 as vlan tagged on that Stump (switchport trunk allow vlan add 2)