Separate management / VMotion Best Practice?

Similar Questions

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

• Best practices of VMotion

  Summer of Googling, but impossible to find a "Best Practices" document on the configuration of VMotion?

  Regarding the configuration of the network it is not much - you need connectivity GB NIC - as has already been identified - I usually we vSwitch0 as my management vSwitch and assign 2 NIC's - this provides Actif\Passif NIC for the service console and vMotion then... You must also ensure that vSwitch names are the same if you use standard vSwitches.  You do not try vMotion between AMD and Intel CPU - if you have different generations of AMD and Intel CPU so watch using enhanced vMotion.

  Don't forget to leave some points for messages useful/correct.

• C++ Cache manages best practices

  Hello
  
  Extend the initial connection to the coherence via C++ client proxy is an expensive operation. To this end could someone offer me some clarity on the best practices in the following situations.
  
  1. currently I call CacheFactory::getCache (cache_name); and save this handle, I then use the handle for the duration of the application for gets later. I use a range of different caches and I keep all handles 'alive '. By doing this, I found only the cost of the socket connection once.
  
  2. given situation 1. What happens if multiple threads call 'get' on a mixer? Are queue operation? It is thread-safe?
  
  3. situation 2. Will there be a performance gain to have a cache to manage per-thread?
  
  
  Thank you
  Rich

  Hi rich,

  The CacheFactory puts cached internally NamedCache returned references, multiple calls to CacheFactory::getCache ("name") will return the same reference every time. When the application is done using the cache it can ask the factory to drop the reference and invalidating local stubs by calling CacheFactory::releaseCache, passing in the reference cache. The NamedCaches returned are also thread-safe, so that you can share them safely between threads in your application. Finally, given that the factory will return the same reference every time, you have not really a way to distribute the different references in different threads, if you really wanted to do that you would need to instantiate DefaultConfigurableCacheFactories separate for each thread, rather then making them share the CacheFactory singleton. Note these feature exist in the same form in our Java and .NET clients.

  Thank you

  Mark
  The Oracle coherence

• Request for advice: generally speaking, what is the best practice for managing a paid and a free application?

  Hi all

  I recently finished my first app of cascades, and now I want to inspire of having a more feature rich application that I can then sell for a reasonable price. However, my question is how to manage the code base for both applications. Any have any "best practices", I would like to know your opinion.

  You use a revision control system? This should be a prerequisite...

  How the different versions of the application will be?

  Generally if you have two versions that differ only in terms of having a handful of features disabled in the free version, you must use exactly the same code base. You could even just it for packaging (build command) was the only difference, for example by adding an environment variable in one of them that would be checked at startup to turn paid options.

• Best practices for the Manager of the Ucs to the smooth running of our environment

  Hi team

  We are remaining with data center with Cisco Ucs blades. I want the best practices guide Ucs Manager Manager of Ucs check all things configured correctly in accordance with the recommendation of Cisco and standard to the smooth running of the environment.
  A certain provide suggestions. Thank you

  Hey Mohan,.

  Take a look at the following links. They should provide an overview of the information you are looking for:

  http://www.Cisco.com/c/en/us/products/collateral/servers-unified-computi...

  http://www.Cisco.com/c/en/us/support/servers-unified-computing/UCS-manag...

  HTH,

  Wes

• Best practices for managing exceptions and success messages.

  Hey people,

  These days I've been shooting packages to clean my application. And question came to my mind, ' should I treat my exceptions the right way?

  
  So I want to ask you met guys, what is the best practice for this? (I want to learn it until it's too late )

  Currently I have a function that returns "OK" if all goes well.

  
  

  return('OK');  

  Can I manage my exceptions like this

    EXCEPTION
      WHEN OTHERS THEN
        ROLLBACK;
        RETURN (SQLERRM);
  
  

  At THE SUMMIT, I have a process that calls the function and then checks if the function returned "OK".

       IF cRet not LIKE 'OK%' THEN
        RAISE_APPLICATION_ERROR(-20000,cRet);
       END IF;
  
  

  And in 'process Error Message' I put "#SQLERRM_TEXT #" so that I can see what error occurred.

  Question aside, how do you manage your messages of success?

  Currently in 'process success Message' put something along the lines "Action completed successfully". What to do about all the processes.

  Do you want to do differently?

  I really want to hear what you have to say since I'm tired of feeling like this is a terrible way to manage these things.

  Hi Para,

  Para wrote:

  I don't know of situations where my service throw exceptions like no_data_found.

  and I need to know that the process is not so I can get to see my # #SQLERRM_TEXT.

  I got this by increasing the error in the application (which I think is a bad way to go) if the return is anything other than 'OK '. I get my application error in the process of the apex, and not in my service.
  And I want to show the inline error in the notification. (Which I am currently with my approach).

  You can use APEX_ERROR. ADD_ERROR in your PL/SQL process to throw exceptions in Oracle APEX.

  Reference: Re: Re: error in the processing of the page management

  Kind regards

  Kiran

• I'm looking for help to share best practices to upgrade the Site Recovery Manager (SRM), if someone can summarize the preparatory tasks?

  I'm looking for help to share best practices to upgrade the Site Recovery Manager (SRM), if someone can summarize the preparatory tasks?

  Hello

  Please check the content below, you may find useful.

  Please refer to the URL: Documentation VMware Site Recovery Manager for more detailed instructions.

  Important

  Check that there is no cleanup operation pending on recovery plans and there is no problem of configuration for the virtual machines that protects the Site Recovery Manager.

  1 all the recovery plans are in ready state.

  2 the protection status of all protection groups is OK.

  3 the status of the protection of all the individual virtual machines in the protection groups is OK.

  4 the recovery of all groups of protection status is ready.

  5. If you have configured the advanced settings in the existing installation, note settings you configured before the upgrade.

  6 the vCenter local and remote server instances must be running when you upgrade the Site Recovery Manager.

  7 upgrade all components Server vCenter Site Recovery Manager on a site until you upgrade vCenter Server and Site Recovery Manager on the other site.

  8 download the setup of Site Recovery Manager file in a folder on the machines to be upgraded the Site Recovery Manager.

  9 make sure no other facilities-\no updates windows restarts done shoud

  Procedure:

  1. connect to the machine on the protected site on which you have installed the Site Recovery Manager.

  2. backup the database of Site Recovery Manager by using the tools that offers the database software.

  3. (optional) If you upgrade of Site Recovery Manager 5.0.x, create a 64-bit DSN.

  4 upgrade the instance of vCenter Site Recovery Manager server that connects to vCenter Server 5.5.

  If you upgrade a vCenter Server and Site Recovery Manager 4.1.x, you upgrade the instances of vCenter Server and Site Recovery Manager server in the correct sequence until you can upgrade to Site Recovery Manager 5.5.

  a upgrade vCenter Server 4.1.x to 5.0.x server.

  b Update Site Recovery Manager of 4.1.x to 5.0.x.

  c upgrade server vCenter Server 5.0.x to 5.5.

  Please let me know if it helped you or not.

  Thank you.

• Best practices for managing strategies of path

  Hello

  I get conflicting advice on best practices for managed paths.

  We are on version 4.0 of ESXi connection to a HP EVA8000. Best practices guide HP recommends setting the strategy of railways handle on Round Robin.

  This seems to give two active paths to the optimized controller. See: http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA1-2185ENW.pdf

  We used certain consultants and they say that the best practices of Vmware for this solution is to use the MRU policy which translates a single path to the optimized controller.

  So, any idea what good practice is best practice? Does make a difference?

  TIA

  Rob.

  Always go with the recommendation of the storage provider.  VMware recommendation is based on the characteristics of the generic array (controller, capable ALUA failover methods, etc.).  The storage provider's recommendation is based on their performance and compatibility testing.  You may want to review their recommendations carefully, however, to ensure that each point is what you want.

  With the 8000, I ran with Round-Robin.  This is the option of creating more robust paths available to you from a failover and performance point of view and can provide performance more even through the ports on the storage controller.

  While I did of the specific tests/validation, the last time that I looked at the docs, the configuration of HP recommends that you configure each IO to the ports in the switch configuration.  This adds the charge to the ESX host, the switch to other ports, but HP claims that their tests showed that it is the optimal configuration.  It was the only parameter I wondered in their recommendation.

  If you haven't done so already, be sure to download the HP doc on configuring ESX and EVA bays.  There are several parameters that you must configure the policy path, as well as a few scripts to help make the changes.

  Virtualization of happy!

  JP

  Please consider awarding points to useful or appropriate responses.

• Best practices VMotion network prod.

  Our team has looked at the requirements of network speed for the VMotion network on an ESX Server.  Details to our environment, we are looking at a cluster of 8 knots with each ESX Server running over 25 virtual machines.  Given this information, a network of 1 GB for the VMotion network connection seems sufficient, or should we be looking at more closely to the provision of a connection of 10 GB?

  Thank you very much in advance,

  Steve

  best practical vMotion is a network isolated from 1 GB - 10 GB would be a stretch the network is used when a vmotion event happens and if your environment is sized correctly I don't expect vmotion occurning more than a few times per hour - and based on your virtual machines per host, I would say that you will have a lot of extra capacity--

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• Best practices for the configuration of VMotion

  Hi guys,.

  I need to try VMware Vmotion. What are the steps to configure Setup for VMotion. Could someone help me with this?

  I had tried to do VMotion, but have not seen the result.

  I currently have two boxes of ESX (ESX 3.5 U3) with VI U4. Primary ESX with Guest OS WIN2K3 and WINXP.

  I am also wanting to know the best practices that can be followed for configuration of VMotion.

  Concerning

  MRM

  http://www.VMware.com/PDF/vi3_35/esx_3/R35/vi3_35_25_3_server_config.PDF

  The link above is a complete in pdf format on the configuration of ESX, including the VMkernel you need for VMotion.

  Duncan

  VMware communities user moderator

  -

• Update DB Manager best practices?

  It is advisable to give VUM it's own DB instance separated from the VC DB instance?   The best practice is documented somewhere?

  Thanks in advance,

  -geob

  That's probably what you are looking for: VMware Update Manager Performance and best practices

• 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 for the integration of the Master Data Management (MDM)

  I work on the integration of MDM with Eloqua and are looking for the best approach to sync data lead/Contact changes of Eloqua in our internal MDM Hub (output only). Ideally, we would like that integration practically in real time but my findings to date suggest that there is no option. Any integration will result in a kind of calendar.

  Here are the options that we had:

  1. "Exotic" CRM integration: using internal events to capture and queue in the queue changes internal (QIP) and allows access to the queue from outside Eloqua SOAP/REST API
  2. Data export: set up a Data Export that is "expected" to run on request and exteernally annex survey via the API SOAP/REST/in bulk
  3. API in bulk: changes in voting that has happened since the previous survey through the API in bulk from Eloqua outside (not sure how this is different from the previous option)

  Two other options which may not work at all and who are potentially antimodel:

  • Cloud connector: create a campaign questioning changes to schedule and configure a connector of cloud (if possible at all) to notify MDM endpoint to query contact/lead "record" of Eloqua.
  • "Native" integration CRM (crazy): fake of a native CRM endpoint (for example, Salesforce) and use internal events and external calls to Eloqua push data into our MDM

  Issues related to the:

  1. What is the best practice for this integration?
  2. Give us an option that would give us the close integration in real-time (technically asynchronous but always / event-based reminder)? (something like the outgoing in Salesforce e-mail)
  3. What limits should consider these options? (for example API daily call, size response SOAP/REST)

  If you can, I would try to talk to Informatica...

  To imitate the integrations of native type, you use the QIP and control what activities it validated by internal events as you would with a native integration.

  You will also use the cloud api connector to allow you to set up an integration CRM (or MDM) program.

  You have fields of identification is added objects contact and account in Eloqua for their respective IDs in the MDM system and keep track of the last update of MDM with a date field.

  A task scheduled outside of Eloqua would go to a certain interval and extract the QAP changes send to MDM and pull the contacts waiting to be sent in place of the cloud connector.

  It isn't really much of anything as outgoing unfortunately use Messaging.  You can send form data shall immediately submit data to Server (it would be a bit like from collections of rule of integration running of the steps in processing of forms).

  See you soon,.

  Ben

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