ATA187 Port unused 2 - best practices?

Similar Questions

• Best practices of ESXi.

  I'm trying to find out if I implement best practices correctly on ESXi 4.1 U1. Our facility has two on-board NICs and a quad card NETWORK to use for data and management networks. We have fiber for the side storage. If I understand the latest practices should I trunk 6-port then use port groups to manage traffic VLAN where going.

  My question is this does not put excessive pressure on the network card that is used for the traffic of vmotion/vmkernel? If I put the switchport in one VLAN specific datagrams wouldn't get inspected and abandoned by the switch asics as opposed to the ESXi host to have to deal with them? I don't know if traffic would have a significant impact, so be it, but wanted to check before the implementation...

  Thank you
  Froggy

  I guess that you are concerned about air on the ESXi host performance, because it must deal with VLAN tags.

  Don't worry about this. The overhead is minimal and modern NICS also have material unloading of functions for VLAN that will be used by ESX in many cases of handling.

  However, remember that you have no safe the uplinks on the physical switch! Just create a virtual switch and add all the rising physical their. ESXi them then use all function of the active/standby/unused attribute that you can set by group of virtual ports.

  Andreas

  - Blog of experience front of VMware

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

• Best practices for vsphere 5.1

  where can I find the doc more up-to-date about berries EQL configuration / best practices with vmware vsphere 5.1

  Hello

  Here is a link to a PDF file that covers best practices for ESXi and EQL.

  Best EqualLogic practices ESX

  en.Community.Dell.com/.../20434601.aspx

  This doc mentions specifically that the storage Heartbeat VMKernel port is no longer necessary with ESXi v5.1.  VMware has corrected the problem that made it necessary.

  If you add it to a 5.1 system it will not hurt.  It will take an IP address for each node.

  If you upgrade 5.0 to 5.1, you can delete it later.

  Here is a link to VMware which addresses this issue and has links to other Dell documents which confirm also that it is fixed in 5.1.

  KB.VMware.com/.../Search.do

  Kind regards

• 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

• A listener by server or a listener instance?  What is the best practice?

  I joined a company owner and new oracle DBA uses a listener and a port (by default) by server.  We have 7 instances of oracle on a server database using the same listener.  I always created a new listener. / netca or make entries manually by database instance. / dbca

  What is the best practice?  My argument for the creation of a separate listener is to be able to restrict connections and accelerator by database using the parameters and the params of the listener.  With a listener, it seems impossible to use several listener settings or settings since all the dB to use it only a listener.  Also if the listener does not have any new connection for all the dB to use it on the server.

  What is the best practice?

  The best practice is what works best for you in your particular environment

  Personally I have found don't have much need to adjust the configuration of the listener for each separate instance so in my environment of each server has 1 single earphone that is shared by several bodies. I can see your points about the benefits of having separated from listeners, but also additional administration required for the best answer is the one that is right for you. Some of the servers I maintain may have up to 20 instances (development) so having 20 listeners is probably a little more work I want keep.

• Best practices for building an infrastructure of APEX for 12 c

  Hi all

  Have we not the docs on best practices for building an infrastructure of APEX?

  Which means, for the production, it is acceptable to use Embedded PL as the listener, or we stick with the Listenr tested on Weblogic?

  Thank you

  Hi JCGO,.

  JCGO wrote:

  Hi all

  Have we not the docs on best practices for building an infrastructure of APEX?

  Which means, for the production, it is acceptable to use Embedded PL as the listener, or we stick with the Listenr tested on Weblogic?

  Thank you

  I agree with Scott's response '' it depends. '' It starts with the appropriate choice of a web listening port.

  You should discourage use EPG facility based in Production environments in accordance with the recommendation of the Oracle.

  Reference: See security considerations when you use the Embedded PL/SQL Gateway section.

  ADR (APEX Listener) + Oracle Weblogic Server sounds good, if you already have tried and have appropriate expertise to manage it.

  Also, you might consider what other facilities ADR based ADR + Apache Tomcat with Apache HTTP Server reverse proxy as described here:

  Dimitri Gielis Blog (Oracle Application Express - APEX): Prepare the architecture for the APEX 5.0 upgrade

  But it depends on Apache skills, you have within your organization.

  I hope this helps!

  Kind regards

  Kiran

• Best practices for network configuration of vSphere with two subnets?

  Well, then I'll set up 3 ESXi hosts connected to storage shared with two different subnets. I configured the iSCSI initiator and the iSCSI with his own default gateway - 192.168.1.1 - targets through a Cisco router and did the same with the hosts configured with its own default gateway - 192.168.2.2. I don't know if I should have a router in the middle to route traffic between two subnets since I use iSCSI ports linking and grouping of NETWORK cards. If I shouldn't use a physical router, how do I route the traffic between different subnets and use iSCSI ports binding at the same time. What are the best practices for the implementation of a network with two subnets vSphere (ESX host network: iSCSI network)? Thank you in advance.

  Install the most common iSCSI would be traffic between hosts and

  the storage is not being routed, because a router it could reduce performance.

  If you have VLAN 10(192.168.1.0/24) iSCSI, VLAN 20 (192.168.2.0/24) ESX

  MGMT and VLAN 30 (192.168.3.0/24) comments VMs and VLAN 40 (192.168.4.0/24)

  vMotion a deployment scenario might be something like:

  NIC1 - vSwitch 0 - active VMK (192.168.1.10) MGMT, vMotion VMK (192.168.4.10)

  standby

  NIC2 - vSwitch 1 - current (VLAN30) guest virtual machine port group

  NIC3 - vSwitch 2 - active VMK1 (192.168.1.10) iSCSI

  NIC4 - vSwitch 2 - active VMK2 (192.168.1.11) iSCSI

  NIC5 - vSwitch 1 - current (VLAN30) guest virtual machine port group

  NIC6 - vSwitch 0 - MGMT VMK (192.168.2.10) standby, vMotion

  VMK (192.168.4.10) active

  You would place you on VLAN 10 storage with an IP address of something like target

  192.168.1.8 and iSCSI traffic would remain on this VLAN. The default value

  gateway configured in ESXi would be the router the VLAN 20 with an ip address of

  something like 192.168.2.1. I hope that scenario help set some options.

  Tuesday, June 24, 2014 19:16, vctl [email protected]>

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

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

• What is the best practice for the double management interfaces?

  Hello community!

  I'm upgrading to a few host ESX to ESXi 4.1U1 4.0 in the coming weeks. My question is about how to configure the management networks. Obviously in ESX 4.0 Classic I have a Service Console port (on vSwitch0) group and a group of ports VMkernel (also on vSwitch0) which provides my host with SC and vmotion capabilities, as we all know. Note: my vSwitch0 has two vmnic attached to it, is pending and is active. That's just how we have our double installation of switches, so it must be active / standby.

  I got to thinking (book the great from HA and DRS deepdive Duncap Epping and Frank Denneman), that I should consider carefully when my network mangement I improve these hosts to ESXi 4.1 - which of course done away with the Service Console and use the vmkernel instead.

  The question is, in which best practices and account with my setup: I have two vmkernel ports? If so, how should I configure each for traffic management and vmotion vmkernel?

  I think it will be a good discussion to have.

  Thank you all,

  Matt

  The NIC vSwitch0 value active/active, the vswif (and future vmkernel management) team of NIC Active vmnic6 and vmnic1 ensures and leaves the vMotion vmkernel NIC team as is.

  This will allow you to use two physical network interface cards at the same time while having a failover plan and keep your physically separate management and vMotion traffic.

  In the end:

  vSwitch: vmnic1 vmnic6 active, active.

  VMK (Mgt): active eve of vmnic1 vmnic6.

  VMK (vMotion): active standby, vmnic6 vmnic1.

• 10 GB NIC redundancy-Best Practice

  Hi all

  I have now deployed successfully to the 5 different poles of vSphere using 4 x 1 GB network adapters on all servers to ESX/ESXi hosts. I used 2 active/passive NIC in vSwitch0 vMotion and network management traffic (or Service Console for ESX) and used 2 active/active NIC in vSwitch1 for VM traffic as shown below. The uplinks are using 802. 1 q trunks in redundant Cisco switches.

  We are now moving to 10 GB networks. I have the opportunity to use this same design of map NETWORK 4 (using the HP Flex 10 vNIC or cards Cisco Palo) or go with a simpler model of map NETWORK 2. What is the recommended best practice to separate VMkernel Port and port VM group traffic among the physical network interface cards? Any suggestions or links to published documents would be greatly appreciated of VMware.

  Thank you!

  

  Take a look at my post here.  https://www.myciscocommunity.com/message/63033#63033

  Can help you with your design questions.  There is also a generic 'best practice' guide for 10G networks & VMware environments.

  As Cisco I obviously partial to the Palo adapter.  Unlike the Flex-10 option you set up not a bandwidth 'max' virtual NETWORK card, rather, you set a guarantee min. for each virtual host NIC given that you can create multiple network cards virtual with Palo, you can create one for VMotion, VM data, IP storage, etc. and define your QoS guarantees quickly & easily while offering redundancy with the recovery of host-transparent fabric.

  Let us know if you have specific questions about a deployment.

  Kind regards

  Robert

• Best practices for the installation of 10 GbE

  I have a new HP DL380G7 who has 4 cards on 1 G and 2 10 network interface cards.

  This will run VSphere 4.1 esxi

  I'm looking for some advice on what would be a good network for this server configuration.

  The storage will be NFS goes to a NAS Server

  I tried to create 2 vswitch one with one of the NICs embedded for the service console and the other switch was a team of the 10G env.

  Support Vmware told me that in this configuration, I had to make sure that the service console was on a different subnet from the kernel NFS or NFS traffic will try to go on the service console port.

  I tried this config but as soon as I add a Vkernel to the 2nd switch I am not out ping.

  So I thought I'd post here with what would be a best practice configuration for this server.

  In the first configuration, it is difficult to say which interface will be used for NFS traffic.  Therefore, it is not a recommended configuration.

  The second configuration must be correct.

• Separate management / VMotion Best Practice?

  We're heading to 4.0 ESX ESXi 4.1.  Our servers have 4 physical Gigabit NIC.

  On ESX 4.0, we lack 2 vSwitches:

  vSwitch0

  Service Console - Active vmnic0 - vmnic3 watch

  VMkernel - Active vmnic3 - vmnic0 eve

  (Unique network interface cards / IPs by function)

  vSwitch1

  Port VM - vmnic1 and vmnic2 active groups

  (Several VLANS to resources shared)

  With the changes in ESXi, is recommended to separate the management of VMotion as we did with ESX?  Notice that we use the same subnet for these two functions.

  Personally, I would prefer combining Management and VMotion.  VMotion will not only benefit an additional NIC usage, especially with the multiple simultaneous VMotions?  At the same time, it seems not that management traffic would be impeded to the point of needing to separation, as we use the same subnet.  In addition, security should not be a problem, since the new, we use the same subnet for management and VMotion.

  Your configuration is consistent with "best practices". I prefer separate management taffic VMkernel myself, even if it will cost me some performances of vMotion.

  ---

  MCITP: SA + WILL, VMware vExpert, VCP 3/4

  http://blog.vadmin.ru