best practices v-switch

Similar Questions

• Best Practice Guide for stacked N3024 switches

  Is there a guide to BP for the configuration of the 2 N3024s stacked for the connections to the server, or is the same eql iscsi configuration guide.

  I'm trying to:

  1) reduce to a single point of failure for rack.

  (2) make good use of LACP for 2 and 4 nic server connections

  (3) use a 5224 with it's 1 lacp-> n3024s for devices of unique connection point (ie: internet router)

  TIA

  Jim...

  Barrett pointed out many of the common practices suggested for stacking. The best practice is to use a loop for stacking and distributing your LAG on multiple switches in the stack, are not specific to any brand or model of the switch. The steps described in the guides of the user or the white papers generally what is the recommended configuration.
  http://Dell.to/20sLnnc

  Many of the best practices scenarios will change of network-to-network based around what is currently plugged into the switch, and the independent networks needs / requirements of business. This has created a scenario where the default settings on a switch are pre-programmed for what is optimal for a fresh switch. Then recommended are described in detail in white papers for specific and not centralized scenarios in a single document of best practices that attempts to cover all scenarios.

  Express.ypH N-series switches are:
  -RSTP is enabled by default.
  -Green eee-mode is disabled by default.
  -Frother is enabled by default.
  -Storm control is disabled by default.

  Then these things can change based on the towed gear and needs/desires of the whole of society.

  For example, Equallogic has several guides that recommendations of configuration detail to different switches.
  http://Dell.to/1ICQhFX

  Then on the side server, you would like to look more like the OS/server role. For example a whitepaper VMware that has some network settings proposed when running VMware in an iSCSI environment.
  http://bit.LY/2ach2I7

  I suggest making a list of the technology/hardware/software, which is used on the network. Then use this list to acquire white papers for specific areas. Then use these white papers best practices in order to ensure the switch configuration is optimal for the task required by the network.

• Best practices for the firmware update 40 + switches

  Hello.

  I need for firmware (and boot code) updated over 40 switches PowerConnect (mainly 5324).

  What is the best practice on that?

  I tried to download and install Dell OpenManage Network Manager, but it seems like an application of 'disorder' for someone who doesn't know. I threw a look at the demo of Dell for the application, but the quality is very bad and it is a version different than the one I downloaded (V3.0.1.15) you cannot use the guides directly.

  Are there other options that manual session opening, then TFTP the new firmware and boot code? Or can someone a link to a valid demo or documentation that can help me with the work?

  Thanks in advance.

  
  

• Code/sequence TestStand sharing best practices?

  I am the architect for a project that uses TestStand, Switch Executive and LabVIEW code modules to control automated on a certain number of USE that we do.

  It's my first time using TestStand and I want to adopt the best practices of software allowing sharing between my other software engineers who each will be responsible to create scripts of TestStand for one of the DUT single a lot of code.  I've identified some 'functions' which will be common across all UUT like connecting two points on our switching matrix and then take a measure of tension with our EMS to check if it meets the limits.

  The gist of my question is which is the version of TestStand to a LabVIEW library for sequence calls?

  Right now what I did is to create these sequences Commons/generic settings and placed in their own sequence called "Functions.seq" common file as a pseduo library.   This "Common Functions.seq" file is never intended to be run as a script itself, rather the sequences inside are put in by another top-level sequence that is unique to one of our DUT.

  Is this a good practice or is there a better way to compartmentalize the calls of common sequence?

  It seems that you are doing it correctly.  I always remove MainSequence out there too, it will trigger an error if they try to run it with a model.  You can also access the properties of file sequence and disassociate from any model.

  I always equate a sequence on a vi and a sequence for a lvlib file.  In this case, a step is a node in the diagram and local variables are son.

  They just need to include this library of sequence files in their construction (and all of its dependencies).

  Hope this helps,

• Dell MD3620i connect to vmware - best practices

  Hello community,

  I bought a Dell MD3620i with 2 x ports Ethernet 10Gbase-T on each controller (2 x controllers).
  My vmware environment consists of 2 x ESXi hosts (each with 2ports x 1Gbase-T) and a HP Lefthand (also 1Gbase-T) storage. The switches I have are the Cisco3750 who have only 1Gbase-T Ethernet.
  I'll replace this HP storage with DELL storage.
  As I have never worked with stores of DELL, I need your help in answering my questions:

  1. What is the best practices to connect to vmware at the Dell MD3620i hosts?
  2. What is the process to create a LUN?
  3. can I create more LUNS on a single disk group? or is the best practice to create a LUN on a group?
  4. how to configure iSCSI 10GBase-T working on the 1 Gbit/s switch ports?
  5 is the best practice to connect the Dell MD3620i directly to vmware without switch hosts?
  6. the old iscsi on HP storage is in another network, I can do vmotion to move all the VMS in an iSCSI network to another, and then change the IP addresses iSCSI on vmware virtual machines uninterrupted hosts?
  7. can I combine the two iSCSI ports to an interface of 2 Gbps to conenct to the switch? I use two switches, so I want to connect each controller to each switch limit their interfaces to 2 Gbps. My Question is, would be controller switched to another controller if the Ethernet link is located on the switch? (in which case a single reboot switch)

  Tahnks in advanse!

  Basics of TCP/IP: a computer cannot connect to 2 different networks (isolated) (e.g. 2 directly attached the cables between the server and an iSCSI port SAN) who share the same subnet.

  The corruption of data is very likely if you share the same vlan for iSCSI, however, performance and overall reliability would be affected.

  With a MD3620i, here are some configuration scenarios using the factory default subnets (and for DAS configurations I have added 4 additional subnets):

  Single switch (not recommended because the switch becomes your single point of failure):

  Controller 0:

  iSCSI port 0: 192.168.130.101

  iSCSI port 1: 192.168.131.101

  iSCSI port 2: 192.168.132.101

  iSCSI port 4: 192.168.133.101

  Controller 1:

  iSCSI port 0: 192.168.130.102

  iSCSI port 1: 192.168.131.102

  iSCSI port 2: 192.168.132.102

  iSCSI port 4: 192.168.133.102

  Server 1:

  iSCSI NIC 0: 192.168.130.110

  iSCSI NIC 1: 192.168.131.110

  iSCSI NIC 2: 192.168.132.110

  iSCSI NIC 3: 192.168.133.110

  Server 2:

  All ports plug 1 switch (obviously).

  If you only want to use the 2 NICs for iSCSI, have new server 1 Server subnet 130 and 131 and the use of the server 2 132 and 133, 3 then uses 130 and 131. This distributes the load of the e/s between the ports of iSCSI on the SAN.

  Two switches (a VLAN for all iSCSI ports on this switch if):

  NOTE: Do NOT link switches together. This avoids problems that occur on a switch does not affect the other switch.

  Controller 0:

  iSCSI port 0: 192.168.130.101-> for switch 1

  iSCSI port 1: 192.168.131.101-> to switch 2

  iSCSI port 2: 192.168.132.101-> for switch 1

  iSCSI port 4: 192.168.133.101-> to switch 2

  Controller 1:

  iSCSI port 0: 192.168.130.102-> for switch 1

  iSCSI port 1: 192.168.131.102-> to switch 2

  iSCSI port 2: 192.168.132.102-> for switch 1

  iSCSI port 4: 192.168.133.102-> to switch 2

  Server 1:

  iSCSI NIC 0: 192.168.130.110-> for switch 1

  iSCSI NIC 1: 192.168.131.110-> to switch 2

  iSCSI NIC 2: 192.168.132.110-> for switch 1

  iSCSI NIC 3: 192.168.133.110-> to switch 2

  Server 2:

  Same note on the use of only 2 cards per server for iSCSI. In this configuration each server will always use two switches so that a failure of the switch should not take down your server iSCSI connectivity.

  Quad switches (or 2 VLAN on each of the 2 switches above):

  iSCSI port 0: 192.168.130.101-> for switch 1

  iSCSI port 1: 192.168.131.101-> to switch 2

  iSCSI port 2: 192.168.132.101-> switch 3

  iSCSI port 4: 192.168.133.101-> at 4 switch

  Controller 1:

  iSCSI port 0: 192.168.130.102-> for switch 1

  iSCSI port 1: 192.168.131.102-> to switch 2

  iSCSI port 2: 192.168.132.102-> switch 3

  iSCSI port 4: 192.168.133.102-> at 4 switch

  Server 1:

  iSCSI NIC 0: 192.168.130.110-> for switch 1

  iSCSI NIC 1: 192.168.131.110-> to switch 2

  iSCSI NIC 2: 192.168.132.110-> switch 3

  iSCSI NIC 3: 192.168.133.110-> at 4 switch

  Server 2:

  In this case using 2 NICs per server is the first server uses the first 2 switches and the second server uses the second series of switches.

  Join directly:

  iSCSI port 0: 192.168.130.101-> server iSCSI NIC 1 (on an example of 192.168.130.110 IP)

  iSCSI port 1: 192.168.131.101-> server iSCSI NIC 2 (on an example of 192.168.131.110 IP)

  iSCSI port 2: 192.168.132.101-> server iSCSI NIC 3 (on an example of 192.168.132.110 IP)

  iSCSI port 4: 192.168.133.101-> server iSCSI NIC 4 (on an example of 192.168.133.110 IP)

  Controller 1:

  iSCSI port 0: 192.168.134.102-> server iSCSI NIC 5 (on an example of 192.168.134.110 IP)

  iSCSI port 1: 192.168.135.102-> server iSCSI NIC 6 (on an example of 192.168.135.110 IP)

  iSCSI port 2: 192.168.136.102-> server iSCSI NIC 7 (on an example of 192.168.136.110 IP)

  iSCSI port 4: 192.168.137.102-> server iSCSI NIC 8 (on an example of 192.168.137.110 IP)

  I left just 4 subnets controller 1 on the '102' IPs for more easy changing future.

• Connecting two 6224 separate batteries best practices LAG?

  Hello

  I wonder how I should configure LAG between two powerconnect 6224 batteries (2 x powerconnect 6224 by battery) for iSCSI against 4 members EQL traffic, I intend to use the 4 ports of each stack (stack cross-possible LAG on 6224?) and equallogic documentation leaves me in two minds when it wants to run LACP or not?

  I wonder what reviewed best practices in this scenario?

  Cross-stack, LACP and no PLEASE or am I better of without LACP?

  Thanks in advance

  Cree

  The ports connecting the two piles together will be configured differently than the ports of connection of the battery to the EQL appliance. During the connection of the control unit switch EQL is when you might want to disable STP on that specific port.

  «Do not use of Spanning Tree (STP) on switch ports that connect to the terminal nodes (iSCSI initiators or storage array network interfaces).» However, if you want to use STP or Rapid STP (preferable to STP), you must enable port settings available on some switches that allow the port immediately transition to PLEASE State reference to link up. This feature can reduce network interruptions that occur when devices to restart, and should only be enabled on switch ports that connect the nodes. "

  With the network cards on the EQL devices according to me, there is only one active port, and the other is pending. So on the switch ports that are plug on the EQL will be in access mode for your iSCSI VLANS. Maybe someone more about EQL can chime to confirm.

  Here are some good white pages.

  www.dell.com/.../Dell_EqualLogic_%20iSCSI_Optimization_for_Dell_Power_onnect_%20Switches.pdf

  docs.danielkassner.com/.../ISCSI_optimization_EQL.pdf

  www.Dell.com/.../EQL-8024f-4-Switch.pdf

• Best practices with streams WCCP of WAAS

  Hello

  I have a module WAAS SRE 910 in 2911 router that intercepts packets this router with WCCP.

  All packets are received by the external interface (gi 0/2, connected to a switch with port configured in vlan WCCP) and are sent back to the router via the internal interface (IG 1/0 connected directly to the router):

  WAAS # sh interface IG 1/0

  Internet address: 10.0.1.1

  Subnet mask: 255.255.255.0

  State of the admin: to the top

  Operating status: running

  Maximum transfer unit size: 1500

  Entry errors: 0

  Entry packets dropped: 0

  Packets received: 20631

  Output errors: 0

  Output packets dropped: 0

  Load interval: 30

  Input rate: 239 bps, 0 packets/s

  Output: 3270892 bps, 592 packets/s

  Packets sent: 110062

  Auto-negotiation: on

  Full Duplex: Yes

  Speed: 1000 Mbit/s

  WAAS # sh interface 2/0 gi

  Internet address: 10.0.2.1

  Subnet mask: 255.255.255.0

  State of the admin: to the top

  Operating status: running

  Maximum transfer unit size: 1500

  Entry errors: 0

  Entry packets dropped: 0

  Packets received: 86558

  Output errors: 0

  Output packets dropped: 0

  Load interval: 30

  Input rate: 2519130 bps, 579 packets/s

  Output rate: 3431 bps, 2 packets/sec

  Packets sent: 1580

  Auto-negotiation: on

  Full Duplex: Yes

  Speed: 100 Mbps

  The default route configured in module WAAS is 0.0.0.0/0 to 10.0.1.254 (interface of the router).

  It would be better that the packets leave module WAAS of the external interface (instead of the internal interface)?

  Is there a best practice recommended by Cisco on this?

  Thank you.

  Stéphane

  Hi Stephane,

  That's right, internal interface means SM1/0.

  The best way is to have traffic at the start of the internal interface module so that we are sure, it hits the redirect exclude statement and that we do not have the crest of the loops because WCCP.

  Kind regards

  Nicolas

• Sliders - best practices

  Hi all

  This question is based on the thread: Re: best practices with the sliders with curls

  Here I've created the same script with different methods.

  1 CURSOR

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

  DECLARE

  CURSOR table_count

  IS

  SELECT table_name

  From user_tables

  ORDER BY 1;

  sqlstr VARCHAR2 (1000);

  numrow NUMBER;

  BEGIN

  Dbms_output.put_line ('Start time' | to_char (sysdate,' dd-mon-yyyy hh24:mi:ss'));))

  I'm IN table_count

  LOOP

  sqlstr: = 'SELECT COUNT (*) FROM "| i.table_name;

  EXECUTE IMMEDIATE sqlstr INTO numrow;

  If numrow > 0 then

  Dbms_output.put_line (RPAD (i.table_name, 30, '.') |) ' = ' || numrow);

  end if;

  END LOOP;

  Dbms_output.put_line ('End time' | to_char (sysdate,' dd-mon-yyyy hh24:mi:ss'));))

  END;

  My understanding:

  He's going to line-by-line treatment generally slow performance

  2. BULK COLLECT

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

  DECLARE

  sqlstr VARCHAR2 (1000);

  numrow NUMBER;

  Table-name TYPE is table of the varchar2 (30);

  tNom table_name;

  BEGIN

  Dbms_output.put_line ('Start time' | to_char (sysdate,' dd-mon-yyyy hh24:mi:ss'));))

  SELECT table_name

  TNom LOOSE COLLECTION

  From user_tables

  ORDER BY 1;

  BECAUSE me IN tNom. FIRST... tNom. COUNTY

  LOOP

  sqlstr: = 'SELECT COUNT (*) FROM "| tname (i);

  EXECUTE IMMEDIATE sqlstr INTO numrow;

  If numrow > 0 then

  Dbms_output.put_line (RPAD (tname (i), 30, '.') |) ' = ' || numrow);

  end if;

  END LOOP;

  Dbms_output.put_line ('End time' | to_char (sysdate,' dd-mon-yyyy hh24:mi:ss'));))

  END;

  My understanding:

  1 avoid context switching

  2 uses more PGA

  3. THE CURSOR AND IN BULK AT COST VIRES

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

  DECLARE

  CURSOR table_count

  IS

  SELECT table_name

  From user_tables

  ORDER BY 1;

  sqlstr VARCHAR2 (1000);

  numrow NUMBER;

  Table-name TYPE is table of the varchar2 (30);

  tNom table_name;

  BEGIN

  OPEN table_count;

  Pick up the LOOSE COLLECT tNom table_count;

  Dbms_output.put_line ('Start time' | to_char (sysdate,' dd-mon-yyyy hh24:mi:ss'));))

  BECAUSE me IN tNom. FIRST... tNom. COUNTY

  LOOP

  sqlstr: = 'SELECT COUNT (*) FROM "| tname (i);

  EXECUTE IMMEDIATE sqlstr INTO numrow;

  If numrow > 0 then

  Dbms_output.put_line (RPAD (tname (i), 30, '.') |) ' = ' || numrow);

  end if;

  END LOOP;

  Dbms_output.put_line ('End time' | to_char (sysdate,' dd-mon-yyyy hh24:mi:ss'));))

  END;

  My understanding:

  I really don't understand why some people prefer this method is to have the two SLIDER and COLLECT in BULK

  4. IMPLICIT CURSOR

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

  DECLARE

  sqlstr VARCHAR2 (1000);

  numrow NUMBER;

  BEGIN

  Dbms_output.put_line ('Start time' | to_char (sysdate,' dd-mon-yyyy hh24:mi:ss'));))

  FOR I IN (SELECT table_name

  From user_tables

  ORDER BY 1)

  LOOP

  sqlstr: = 'SELECT COUNT (*) FROM "| i.table_name;

  EXECUTE IMMEDIATE sqlstr INTO numrow;

  If numrow > 0 then

  Dbms_output.put_line (RPAD (i.table_name, 30, '.') |) ' = ' || numrow);

  end if;

  END LOOP;

  Dbms_output.put_line ('End time' | to_char (sysdate,' dd-mon-yyyy hh24:mi:ss'));))

  END;

  My understanding:

  It will also gives better performance compare that loops of CURSOR

  Given that the 4 methods above do the same work, please explain how to choose the correct methods for different scenarios. That is what we have to consider before choosing a method.

  I asked this question on asktom a few years ago Tom Kyte. He recommended that the implicit cursors:

  • they have a size of 100 (not 500) extraction;
  • PL/SQL manages the opening and closing of the cursor automatically.

  He mentioned one important exception: If you need to change data and not just read it, you need in "bulk" so much read as write operations - and that is to use the FORALL.

  To use FORALL for writing, you must use the COLLECTION in BULK for reads - and you should almost always use LIMIT with the COLLECTION in BULK.

  So, to make it "in bulk the Scriptures ', use FORALL. For the ' readings in bulk "preparing the ' written in bulk ', use BULK COLLECT with LIMIT. For the ' readings in bulk "when you change all the data, implicit cursors are more simple.

  Best regards, stew Ashton

• The ESXi 4.1.0 to 6.0 upgrade. -upgarde and best practices

  Hi guys,.

  We are a small business with a single physical server, ESXi 4.1.0 installed with approx. 8 VMs. We plan on buying Essential Kit 6.0 ESXi because that's all we need right now. However, as VMWare says that 4.1.0 to 6.0 upgrade is NOT supported (matrices of the interoperability of products VMware), how we improve our host and VMS?

  I guess the correct way will be upgraded from 4.0. 5.5 U3 first, then to 6.0. However, if we buy the 6.0 license essential Kit, that we will be able to always download and install and upgrade of the host and all VMs to U3 5.5, and 6.0. Essentials?

  In addition, what are the best practices to upgrade a single host with multiple virtual machines? What I did research, we should back up important files from virtual machine, all critical data, etc. All recommendations are welcome. My understanding is that the upgrade also virtual machines will be upgraded automatically, that's correct - methods of upgrade to ESXi 5.5 (2058352) | VMware KB

  Best regards

  D. Stanchev

  Hello

  As you said, you cannot upgrade host ESXi 4.x to 6.x, you must first upgrade 4.x to 5.x and then switch to 6.x

  Before moving to 5 or 6, make sure you ESXi host is compatible with ESXi 6.

  Check cheque and VMware hardware compatibility list if your server is listed.

  Although you'll have a 6 ESXi license kit, you can download ESXi 5.x and use it to upgrade process.

  Only if you need to use 5.x permanently, then you need to get your license keys downgraded to 5.x, otherwise once you upgrade host to 5.x, go ahead and level to ESXi 6.x

  Backup-

  Before you begin the upgrade, make sure that you have backup of all VMs critics.

  Either you can download/export all VMs as OVF, or you can use Veeam's free edition to make the backup of virtual machines

  -Update

  You can join the server ESXi ISO Installer and boot server form ISO and update.

  During the Installation process make sure to select ' PRESERVER VMFS and upgrade ESXi host '

  If you do not keep vmfs, all virtual machines will get deleted during the installation/upgrade process.

  Once you get ESXi Host upgrade to Upgrade VMFS 5.x version so that it can support 6.

  Then finally the ESXi host to 6.x upgrade, yet once make sure PRESERVE you VMFS during installation.

  If you have vCenter Update manager, use update reach the average upgrade easy it is to upgrade.

  Thank you

  Hentzien

• Fabric zoning best practices (new FC)

  I'm new to CF (we are an iSCSI store), but I'm learning to my DCD. I read on different blog posts on zoning, which on the whole I think logical. I came across this blog post and am a little confused by the diagram:

  http://vmfocus.com/2012/05/31/fabric-zoning-best-practices/

  If you look at the chart it is logical, but higher than that, look at the text:

  http://vmfocus.files.WordPress.com/2012/05/capture.PNG

  E1 to S1 via Fabric Switch 1

  E1 to S3 via Fabric Switch 2

  E2 to S2 switch fabric 1

  E2 to S4 via Fabric Switch 2

  Via Fabric Switch S1 E3 1

  E3 to S3 via Fabric Switch 2

  E4 in the S2 switch fabric 1

  E4 to S4 via Fabric Switch 2

  
  

  How can connect to the same physical port on the HBA to switch 2? Is the text in the wrong article? I presume to know more than any zoning CF topic but I do not see how E1 can be plugged in more than one switch.

  
  

  Totally confused...

  Steven
  

  Using my amazing art skills, I drew a diagram for you:
  http://i.imgur.com/WU6iGGv.PNG

  A high level view of fiber channel SAN would look like incredibly similar, if not identical to your iSCSI network. The text is just describing the logical connections, different server ports can do, such as ethernet. Let me know if it it clears, or I'll go into details with what you want.

• Design by using NetApp's best practices

  I am preparing for my VCP5 and I read the new book by Scott Lowe. the book describes how the traffic should be isolated. your vMotion, vmkernal, etc., but in many organizations, I see the NetApp with some of data warehouses and a few LUNS to CIFS share LUNS. I guess you can have your vmMotion on a VLAN separated, but would not safer just configure a windows VM file server to host your files? In freenas and openfiler forums, they stress is not to run their software in virtual machines in a production environment.   Physical separation would be better then just a VLAN? I was inking and correct me if I'm wrong. I think the CIFS shares in a virtual hosting machine would SAN, vMotion, vmkernal, most reliable if you have redundant switches on both sides VMware hosts. So if your kernel switches drop your vmware environment will not drop.

  > traffic must be isolated.

  Yes, the network traffic must be split on networks separated for various reasons, including performance and safety.

  > NetApps with MON a few for data warehouses and a few LUNS to CIFS share.

  Yes, if you have a NetApp file server you can block-level storage server as FCP or iSCSI, CIFS or NFS file-level storage.

  > I guess you can have your vmMotion on a VLAN separated, but would not safer just configure a windows VM file server to host your files?

  OK, you lost me.  Yes, you must separate the vMotion traffic to enhance the performance and because the vMotion traffic is not encrypted.

  I don't see where you're going for vMotion to a Windows file server?

  However, if you are referring to, why don't you your NetApp instead of Windows CIFS Server:

  You don't need to patch and reboot the NetApp at least once a month.

  Performance is better

  You don't need to buy a Windows license and then maintain Windows

  Snapshots.  NetApp has the best shots in the business.  When your Windows I/O high, or just typing box because it of Tuesday and removes all of your VSS snapshots you really wish you had a NetApp.

  > In the forums of freenas and openfiler, they stress is not to run their software in virtual machines in a production environment.

  Note that there are a ton of storage there equipment running as VMs and server NFS for shared storage, including left and they have been stable for years.

  > Physical separation would be better then just a VLAN?

  Yes, if you have the infrastructure.  When it comes to the first time I've seen reference you VLAN?  Are you talking about now the NetApp as the series 2020 with two network cards where you need to carry all traffic (managent, CIFS and iSCSI) through them via VLAN?

  Like this: http://sostechblog.com/2012/01/08/netapp-fas2xxx-fas3xxx-2-nic-ethernet-scheme/

  > I was inking and correct me if I'm wrong. I think the CIFS shares in a virtual hosting machine would SAN, vMotion, vmkernal, most reliable

  CIFS is nothting to do with SAN, vMotion or VMkernel.  CIFS (SMB) is the protocol used mainly by Windows file sharing

  > If you have redundant switches on both sides of the VMware hosts. So if your kernel switches drop your vmware environment will not drop.

  You always want to redundant switches.  No single point of failure is the best practice.

• Best practices for a NFS data store

  I need to create a data store on a NAS and connect to some servers ESXi 5.0 as a NFS datastore.

  It will be used to host virtual machines less used.

  What are the best practices to create and connect a datastore NFS or networking and storage view bridges in order to get the best possible performance and decrease is not the overall performance of the network?

  Concerning

  Marius

  Create a new subnet of layer 2 for your NFS data warehouses and set it up on his own vSwitch with two uplinks in an active configuration / eve of reunification. Uplink should be variously patches in two distinct physical switches and the subnet must have the disabled bridge so that NFS traffic is not routable in other parts of your network. NFS export can be restricted to the IP address of storage host IP (address of the VM kernel port you created for NFS in the first step), or any address on that subnet. This configuration isolates traffic NFS for performance, ensures the security and redundancy. You should also consult your whitepapers of storage vendors for any specific recommendation of the seller.

  Data warehouses can be made available for the guests you wish and you can use Iometer to compare PAHO are / s and flow rate to see if it meets your expectations and requirements.

• Issue of best practice

  Hello

  I mounted the UN lab pour assess vSphere 5.

  I have a switch and 2 servers.

  Problem:

  vCenter is currently on a VM Server n ° 2. Resources are not sufficient and it is possible that I will reinstall.

  Question:

  More than the way of the East which simple / Secure / quick pour transfer this VM on the server # 1.

  Good evening

  Without the use of special features, you can also:

  -clone the virtual machine

  -migrate from the

  fishing - your vcenter server.

  -start the clone vcenter server.

  and:

  -Since the clone migrate the original stop the clone / delete it and restart the original.

  UO:

  -check that the ok to EST vcenter.

  -delete the original and keep the clone.

  After I know best practices, but in any case by causing, you Microsoft have almost no interruption of service and you have a backup available in 2 clicks.

  He must just ensure that the 2 vm (original and clone is not started at the same time, otherwise you will create a conflict of @ ip).

  Good luck.

• Best practices Networking ESXi 5

  Good afternoon.

  Hate me help, docks as best practices para uma infraestrutura of rede receber o Vmware (ESXi 5 + vCenter vConverter) autonomous.

  Switch, VLAN, NIC?

  Obrigado

  Olá amigo, good afternoon.

  Leave aqui um trecho do livro "Virtualização - Central Datacenter do Componente" em than comenta, sober os conceitos uma rede virtual cloud:

  An e VMware a Savvis sugerem some measures Segurança interesting than sao Speaker aqui operacionais:

  Lado provedor:

  • Manter as redes for sao to leave da infraestrutura virtualizada isoladas. Insulation pode ser feito com os rocking or utilizando segmentacao through VLAN. Outro Método PODES use uma want Kanada Doi methods e o conceito of virtual switch.
  • Manter as redes of members isoladas. Manter as redes of members e isoladas interfaces controlled devidamente.
  • Manter as redes used para verificaram maquinas e tolls IP isoladas em redes roteaveis nao. Estas redes precisam ser rapidas e ao mesmo tempo sao suscetiveis an attacks.
  • Manter as redes back clients isoladas. Estas redes should ser isoladas das redes e members should divertir firewall between as redes para avoid security problems.
  • Fornecer seguro aos recursos nuvem client access. Client OS usually precisam ter access has recursos dentro da e nuvem para isto e Chipre o provedor disponibilize um Portal com encriptacao para Segurança effect.
  • Backups to maintain E restores seguros e consistent. Provedor deve to maintain this appearance basico realize e recursos back to maintain backup um processo rapido restore.
  • Autenticacao strong mechanisms, auditoria e autorização. OS provedores should please has autenticacao segura, access so aos recursos waiting rooms recursos providenciar e.
  • Use models seguros e configuracao gold images do sistema operational e das management. Estas reduzem os problemas com configuracoes inadequadas measures. Also o provisionamento maquinas tolls deve obedecer an entrar em being Produção antes criteria preestabelecidos.
  • Members of recursos para avoid attacks do tipo back.

  Client side:

  • Practices of mercado Seguir para a Segurança sistemas operacionais back. OS administradores should seguir as mesmas rules used no ambiente interno relativas to back sistemas operacionais, como manter os last Segurança no patches of Segurança configuracao gold images.
  • Following to encrypt data. Dados follows sistemas important should mantidos encriptados forse ainda but os possíveis ataque para ser to rede.

  Espero ter helped.

• Best practices for vSphere 5 Networking

  Hi all

  Given the following environment:

  (1) 4 physical servers, each server has 16 (Gigabit) network interface cards will install vSphere 5 std.

  (2) 2 switches with SAN storage battery function

  (3) 2 Equallogic PS4000 SAN (two controllers)

  (4) 2 switches for the traffic of the virtual machine

  As for networking, I intend create some vSwitches on each physical server as follows

  1 vSwitch0 - used for iSCSI storage

  6 network adapters are associated with IP-hash, multitracks with iSCSI Storage consolidation policy. and storage load balancing is round Rodin (vmware)

  (vmware suggests to use 2 cards for 1 traget of IP storage, I'm not sure)

  2 vSwitch1 - used for the virtual machine

  6 Teamed network adapters for the traffic of the virtual machine, with the hash intellectual property policy

  3 vSwitch2 - management

  2 network cards are associated

  4 vSwitch3 - vMotion

  2 network cards are associated

  You would like to give me some suggestions?

  Alex, the standard set by the storage and VMware is used by dell for their servers and tested sound on their equipment and the publication of the document, it is recommended...

  This sound is the best practice for dell server with this model mentioned in the document to use.

  Hope that clarifies...