Connecting two 6224 separate batteries best practices LAG?

Similar Questions

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

• 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

• Best practices with two natachasery

  Hello

  I'll put up a small environment Vi3 with two HP DL380 G5 machines ESX and NFS on NetApp for storage. This must be installed in a field of laboratory and serve as both a learning platform Vi3, we, the admins and a test environment for some of our customers run their own virtual machines with the test software and others. For this purpose, safety is a higher priority than redundancy, roughly equal performance. What is a decent way to implement the two natachasery for this configuration?

  vSwitch0 and pNIC1:

  -VMkernel (vMotion and NFS)

  -Console service

  vSwitch1 and pNIC2:

  -VM network

  This would obviously no redundancy (not counting the vMotion between hosts) but separate VM and non - VM traffic. Is there anything else I should be concerned?

  Thanks in advance,

  Daniel

  Hi Daniel,.

  Available seems very well, simply create a trade.

  (Depends on the load, you might want to consider making another Nic dual or quad). I have 2 natachasery for virtual machines and 2 for NFS...

  Here is a great link to the blog created by Texiwill: (best practices for up to 8 NIC explained)

  It was useful for me (thanks Texiwill..!)

  http://www.astroarch.com/wiki/index.php/Blog_Roll#Cisco_Subnet_-_Blue_Gears_-_Virtual_Networking

  Alex

• best way to connect two PC 2748 s?

  I just upgraded our office in two PC 2748 s (while still also using one of our PC 2324 devices) and I would like to know the best way to connect these three switches.

  At the present time, I have a cord Ethernet connecting each of the 2748 s via the 49 port and then another cord ethernet connecting the 2324 to the 50 of my first 2748 port (which has our main file server and the outgoing Internet connection on it, among other things).

  Should I also connect the 2324 to SECOND 2748 or is asking for disaster? Also, is there an advantage to invest in GBIC modules for the two 2748 s so that I can connect this way or this advantage of flow occurs only when connecting a 2748 to another device (i.e. There is no speed advantage when only connecting two 2748 s together)?

  Thanks in advance for your clarification...

  
  

• Best practices deployment CD to the internet non-connected PC

  Hello

  Are there things or best practices to be careful during the deployment of CD player on the internet non-connected PC? We currently use drive X, which we are patching regularly via a field startup script. Specifically, I want to know:

  (1) CD player can be deployed in the same way that we currently do for Reader X (i.e. first install the base of the file through msiexec.exe /i package in a startup script, and then install the latest hotfix files using msiexec /p also using a startup script)

  (2) CD player does require authentication via internet, or can that be disabled via Adobe Customization Wizard or group policy?

  (3) can I disable all related and all features which requires an internet connection via Adobe Customization Wizard or group policy for clouds?

  (4) at - it nothing another important to know?

  Thank you.

  Here are answers to your questions:

  (1) CD player can be deployed the same way we do it currently for Reader X (i.e. first install the basic package of the file through msiexec.exe /i in a startup script, and then install the latest hotfix using msiexec /p also using a startup script) - Yes, CD player can be deployed in the same way as the X drive. There is no difference.

  (2) CD player does require authentication via internet, or can that be disabled via Adobe Customization Wizard or group policy?  -No, only DC Acrobat requires it. However, CD player, is free and requires no all identifications.

  (3) can I disable all related and all features which requires an internet connection via Adobe Customization Wizard or group policy for clouds? -Yes, you can disable all cloud related features through the Customization Wizard or group policy

  Ben above mentioned, you must always keep your reader to update to the latest version which has the latest security related bugs.

  I hope that I have answered all your questions, and it helps. If you have any question, please report.

  Thank you

  Vinod

• Best practices for client internal connectivity with Horizon view 6

  Hi all

  I saw configuration with a server connection and security.  Internal clients connect directly on the connection to the authentication server, while the external clients through the Security server.  Recently, one of my friends and I had to discuss our configurations.  It has all of its traffic to the Security server.  Its installer seems to be supported by the latest diagrams in the view documentation 6.  What is the best practice?

  Thank you!

  I can certainly see how this diagram is confusing, but it is intended to show the internal clients through directly load balancing to servers connection. If you look at the architecture guide and white papers, they are all show internal clients without going through the security servers.

• Best practices installation CARS in two areas of data center?

  Data Center has two distinct areas.
  In each area, we have a storage system and a rac node.
  
  We will install RAC 11 GR 2 ASM.
  
  For data, we want to use diskgroup + DATA, normal redundancy mirrored on two storage systems.
  
  CRS + vote, we want to use diskgroup + CRS, normal redundancy.
  But for diskgroup CRS + vote with normal redundancy, there are 3 LUNS and we have only 2 storage systems.
  In my view, that the third logical unit number is necessary to avoid situations of split brain.
  
  If we put two LUNS to storage lun #1 and the other for storage #2, what will happen when storage faills #1 - it means that two of the three disks for diskgroup + CRS are inaccessible?
  What will happen when all the material in the #1 box fails?
  Is the human intervention: at the time of the failure, which #1 area rises again?
  
  Is there a best practice for configuration 2-zone 2-storage cars?
  
  Joachim

  Hello

  With regard to the vote of the files are concerned, that a node must be able to access more than half of the files with the right to vote at any time (simple majority). In order to be able to tolerate failure of n files in vote, need at least 2n + 1 configured. (n = number of files with voting rights) for the cluster.
  The problem in a stretch cluster configuration, is that most of the facilities use only two storage systems (one on each site), which means that the site that hosts the majority of voting records is a potential single point of failure for the entire cluster. If the storage or the site where the files of n + 1 vote is configured fails, the entire cluster will go down, because Oracle Clusterware will lose the majority of the files.
  To avoid a complete cluster failure, Oracle will support a third vote file on a cheap lowend, standard NFS mounted device somewhere in the network. Oracle recommends the file NFS vote on a dedicated server, which belongs to a production environment.

  The white paper below allows you to accomplish:
  http://www.Oracle.com/technetwork/database/Clusterware/overview/grid-infra-thirdvoteonnfs-131158.PDF

  Also with regard to the configuration of the vote and OCR (11.2), when you use ASM. How they should be stored?
  I recommend that you read:
  {message: id = 10028550}

  Kind regards
  Levi Pereira

• ADF Faces & BC: best practices for project implementation

  Season greetings my fellow JDevelopers!
  
  Our group of software works with ADF for about 5 years and over the years, we have accumulated a good amount of knowledge in collaboration with JDeveloper and ADF. A large part of our current structure of demand was resurrected in the early days of JDeveloper 10 where there are more codes samples floating around, then there was the 'best practices' documentation. I understand that this is a subjective question, and varies from one site to another, but in my view, there is a set of common practices, our group began to identify as essential to the rationalization of a development process (reusable decorated with user interface components, modular common biz logic, the development with svn, continuous integration/build team, etc...). One of our development objectives is to minimize the dependence between each engineer as everyone is responsible for the client and middle tier application without losing the consistency of coding. After speaking with a couple of the ACE to the last openworld, I understand a large part of our planned architectural requirements are filled with JDeveloper 11 (with the introduction of models, declarative elements, bordered of workflow, etc...) but lack of time on the results expected to come, we are still almost a year away before moving to this new version. Here's some of our group/application.
  
  JDeveloper version: 10.1.3.4
  Number of developers: 7
  Responsibilities of the developer: build both faces & collection bc
  
  We currently have two applications in our production environments.
  1.A flavor of the dynamic module from Steve Muench jdbc connection credentials
  2 core application ADF Faces & BC
  
  In our Core ADF Faces application, we get the following structure:
  
  OurApplication
  -OurApplicationLib (common framework files)
  -OurApplicationModel (project BC)
  src/org/ourapp/module1
  -src/org/ourapp/module 2
  …
  -OurApplicationView (project faces)
  OurApp/public_html/module1
  OurApp/public_html/module2
  …
  SRC/org/ourapp/support/module1
  SRC/org/ourapp/support/module 2
  …
  SRC/org/ourapp/pageDefs /.
  
  
  Total number of application Modules: 15 (including a RootApplicationModule that references the specific AMs module)
  Display of number objects total: 171
  Total number of entities: 58
  Total number of files BC: 1734
  Total number of JSP pages: 246
  Total number of pageDefs: 236
  Total number of cases of navigation in faces - config.xml: 127
  Total number of application files: 4183
  Application size total: 180megs
  
  Are there other ways to divide this application? IE: module specific projects with distinct faces-config files/databindings? If so, how can these files be "hooked" together? A couple of aces has recommended that we must separate all files of the entity in its own project that make sense. In addition, we look at maven builds that must remove the pesky model.jpr files that gets constantly "touched". I would love to hear how other groups organize their application and anything else, they would like to share as a best practice ADF.
  
  See you soon,.
  Wes

  After discussions in the summer/fall by members of the ADF methodology group, I have published a wiki page ADF Coding Standards that people may find useful:
  [http://wiki.oracle.com/page/ADF+Coding+Standards]

  It aims to ADF 11g and is intended to be a living document - if you have any comments or suggestions please post them to the ADF methodology ([http://groups.google.com/group/adf-methodology?hl=en]) google group.

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

• TDMS & Diadem best practices: what happens if my mark has breaks/cuts?

  I created a LV2011 datalogging application that stores a lot of data to TDMS files.  The basic architecture is like this:

  Each channel has these properties:

  To = start time

  DT = sampling interval

  Channel values:

  Table 1 d of the DBL values

  After the start of datalogging, I still just by adding the string values.  And if the size of the file the PDM goes beyond 1 GB, I create a new file and try again.  The application runs continuously for days/weeks, so I get a lot of TDMS files.

  It works very well.  But now I need to change my system to allow the acquisition of data for pause/resume.  In other words, there will be breaks in the signal (probably from 30 seconds to 10 minutes).  I had originally considered two values for each point of registration as a XY Chart (value & timestamp) data.  But I am opposed to this principal in because according to me, it fills your hard drive unnecessarily (twice us much disk footprint for the same data?).

  Also, I've never used a tiara, but I want to ensure that my data can be easily opened and analyzed using DIAdem.

  My question: are there some best practices for the storage of signals that break/break like that?  I would just start a new record with a new time of departure (To) and tiara somehow "bind" these signals... for example, I know that it is a continuation of the same signal.

  Of course, I should install Diadem and play with him.  But I thought I would ask the experts on best practices, first of all, as I have no knowledge of DIAdem.

  Hi josborne;

  Do you plan to create a new PDM file whenever the acquisition stops and starts, or you were missing fewer sections store multiple power the same TDMS file?  The best way to manage the shift of date / time is to store a waveform per channel per section of power and use the channel property who hails from waveform TDMS data - if you are wiring table of orange floating point or a waveform Brown to the TDMS Write.vi "wf_start_time".  Tiara 2011 has the ability to easily access the time offset when it is stored in this property of channel (assuming that it is stored as a date/time and not as a DBL or a string).  If you have only one section of power by PDM file, I would certainly also add a 'DateTime' property at the file level.  If you want to store several sections of power in a single file, PDM, I would recommend using a separate group for each section of power.  Make sure that you store the following properties of the string in the TDMS file if you want information to flow naturally to DIAdem:

  'wf_xname '.
  
  'wf_xunit_string '.
  
  'wf_start_time '.
  
  'wf_start_offset '.
  
  'wf_increment '.

  Brad Turpin

  Tiara Product Support Engineer

  National Instruments

• 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 restart of the nodes of the ISE?

  Hello community,

  I administer an ISE installation with two nodes (I'm not a specialist of the ISE, my job is simply to manage the user/mac-addresses... but now I have to move my ISE a VMWare Cluster nodes to another VMWare Cluster.

  (Both VMWare environments are connected to our network of the company, but are different environments. vMotion is not possible)

  I want to stop ISE02, move it to our new VMWare environment and start it again.

  That I could do this with our ISE01 node...

  Are there best practices to achieve this? (Stop request first, stopl replikation etc.) ?

  Can I really just reboot a node ISE - or I have consider something before I do this? After I did this?

  All tasks after reboot?

  Thanks for any answer!

  ISE01
  Administration, monitoring, Service policy
  PRI (A), DRY (M)

  ISE02
  Administration, monitoring, Service policy
  SEC (A), PRI (M)

  There is a lot to consider here.  If changing environments involves a change of IP address and IP extended, then your policies, profiles and DACL would also change among other things.  If this is the case, create a new VM ISE in the new environment in evaluation license using the and recreate the old environment deployment by using the address of the new environment scheme.  Then a new secondary node set rotation and enter it on the primary.  Once this is done, you can re - host license from your old environment on your new environment.  You can use this tool to re - host:

  https://Tools.Cisco.com/swift/LicensingUI/loadDemoLicensee?formid=3999

  If IP addressing is to stay the same, it becomes simpler.

  First and always, perform an operational backup and configuration.

  If the downtime is not a problem, or if you have a window of maintenance of an hour or so: just to close the two nodes.  Transfer to the new environment and light them, head node first, of course.

  If the downtime is a problem, stop the secondary node and transfer it to the new environment.  Start the secondary node and when he comes back, stop the main node.  Once that stopped services on the head node, promote the secondary node to the primary node.

  Transfer of the FORMER primary node to the new environment and turn it on.  She should play the role of secondary node.  If it is not the case, assign this role through the GUI.

  Remember, the proper way to shut down a node of ISE is:

  request stop ise

  Halt

  By using these commands, the risk of database corruption decreases by 90% (remember to always backup).

  Please rate useful messages and mark this question as answered if, in fact, does that answer your question.  Otherwise, feel free to post additional questions.

  Charles Moreton

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