OID / LDAP configuration steps

Similar Questions

• GC installation fails on the WHO with NodeManager Configuration step

  I try to install OEM Grid Control and I'm having some trouble to make it past step in the installation of the Configuration of the WHO. I'm not very familiar with Oracle products. I finished all the configuration steps listed in the documentation, and in order to solve a problem earlier, I deleted the Keynectis and Telesec certificates since the cacerts file java keystore. NodeManager is run as a service, even if I think that the Setup process starts a new instance because it cannot connect to the service. I was also unable to connect to the service through the nmConnect WLST function, if it is possible my settings are incorrect. If the only problem is that GCDomain is not saved in the file nodemanager.domains, I'm not sure what I'm doing wrong, because I put it in the nodemanager.domains file located at C:\Oracle\Middleware\wlserver_10.3\common\nodemanager:
  
  ---
  #Domains and directories created by the Configuration Wizard
  #Fri 22 April 15:23:16 EDT 2011
  wl_server=C\:\\Oracle\\Middleware\\wlserver_10.3\\samples\\domains\\wl_server
  MEDREC-Spring=C\:\\Oracle\\Middleware\\wlserver_10.3\\samples\\domains\\medrec-Spring
  GCDomain = C\:\\Oracle\\gc_inst\\user_projects\\domains\\GCDomain
  MEDREC=C\:\\Oracle\\Middleware\\wlserver_10.3\\samples\\domains\\medrec
  ---
  Note: the file paths are correct and using escaped slashes, as appropriate, but this message board system turns the last double backslash in a line break. I can't find any html solution that works, so just take my word for it
  
  I restarted NodeManager after making the change as well. Any help would be appreciated. Thank you.
  
  Details:
  Machine - Windows Server 2008 x 64
  DB - 11 GR 2
  WLS - 10.3.2
  GC - 11.1.0.1
  
  Install the Log:
  ...
  FINE: Connection to the node Manager... April 22, 2011 15:23:19 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: April 22, 2011 21:23:19 CEST > < opinion > < security > < BEA-090898 > < without taking account of the approved CA 'CN = AC KEYNECTIS ROOT, OU = ROOT, O is KEYNECTIS, C = EN ". Loading certificate trust list triggered a certificate of analysis exception PKIX: OID not supported in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11. > April 22, 2011 15:23:19 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: April 22, 2011 21:23:19 CEST > < opinion > < security > < BEA-090898 > < without taking account of the approved CA ' CN = T-TeleSec GlobalRoot class 3, OU = T - Systems Trust Center, O = T - Systems Enterprise Services GmbH, C = OF. Loading certificate trust list triggered a certificate of analysis exception PKIX: OID not supported in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11. > April 22, 2011 15:23:19 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: April 22, 2011 21:23:19 CEST > < opinion > < security > < BEA-090898 > < without taking account of the approved CA ' CN = T-TeleSec GlobalRoot class 2, OR = T - Systems Trust Center, O = T - Systems Enterprise Services GmbH, C = OF. Loading certificate trust list triggered a certificate of analysis exception PKIX: OID not supported in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11. > April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: This Exception occurred at Fri Apr 22 15:23:20 EDT 2011. April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: weblogic.nodemanager.NMConnectException: Connection refused: connect. Cannot connect to NodeManager. Check that they are running to win2008x64-2:7, 401. April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: java.net.PlainSocketImpl.socketConnect(Native Method) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: java.net.Socket.connect(Socket.java:525) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: weblogic.nodemanager.client.SSLClient.createSocket(SSLClient.java:38) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.java:227) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:199) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:205) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.java:52) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: weblogic.management.scripting.NodeManagerService.verifyConnection(NodeManagerService.java:175) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: weblogic.management.scripting.NodeManagerService.nmConnect(NodeManagerService.java:168) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: java.lang.reflect.Method.invoke(Method.java:597) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: org.python.core.PyReflectedFunction.__call__(Unknown Source) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: org.python.core.PyMethod.__call__(Unknown Source) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: org.python.core.PyObject.__call__(Unknown Source) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: org.python.core.PyObject.invoke(Unknown Source) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: to $3 org.python.pycode._pyx2.nmConnect (< iostream >: 118) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: to org.python.pycode._pyx2.call_function (< iostream >) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: org.python.core.PyTableCode.call(Unknown Source) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: org.python.core.PyTableCode.call(Unknown Source) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: org.python.core.PyFunction.__call__(Unknown Source) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: org.python.core.PyObject.__call__(Unknown Source) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: to org.python.pycode._pyx41.startNM$1(C:\Oracle\Middleware\oms11g\sysman\omsca\scripts\wls\start_server.py:20) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: to org.python.pycode._pyx41.call_function(C:\Oracle\Middleware\oms11g\sysman\omsca\scripts\wls\start_server.py) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: org.python.core.PyTableCode.call(Unknown Source) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: org.python.core.PyTableCode.call(Unknown Source) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: org.python.core.PyFunction.__call__(Unknown Source) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: to org.python.pycode._pyx39.f$0(C:\Oracle\Middleware\oms11g\sysman\omsca\scripts\wls\create_em_infra.py:74) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: to org.python.pycode._pyx39.call_function(C:\Oracle\Middleware\oms11g\sysman\omsca\scripts\wls\create_em_infra.py) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: org.python.core.PyTableCode.call(Unknown Source) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: org.python.core.PyCode.call(Unknown Source) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: org.python.core.Py.runCode(Unknown Source) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: org.python.util.PythonInterpreter.execfile(Unknown Source) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: weblogic.management.scripting.WLST.main(WLST.java:131) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: java.lang.reflect.Method.invoke(Method.java:597) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run.
  FINE: in weblogic. Run WLST.main(WLST.java:29) April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader
  FINE: Wed Apr 22 15:23:20 EDT 2011 Apr 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: Node Manager down from this April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader works
  FINE: Not connected to the Node Manager Apr 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: Launch NodeManager...
  April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: Properties: {ListenAddress=win2008x64-2,ListenPort=7401,NodeManagerHome=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239,StartScriptEnabled=true,StartScriptName=startEMServer.cmd}.
  April 22, 2011 15:23:20 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: Command: C:\Oracle\MIDDLE~1\JROCKI~1.5-3\jre\bin\javaw.exe - classpath "C:\Oracle\MIDDLE~1\JROCKI~1.5-3\jre\lib\rt.jar; C:\Oracle\MIDDLE~1\JROCKI~1.5-3\jre\lib\i18n.jar; C:\Oracle\MIDDLE~1\patch_wls1032\profiles\default\sys_manifest_classpath\weblogic_patch.jar; C:\Oracle\MIDDLE~1\patch_oepe1032\profiles\default\sys_manifest_classpath\weblogic_patch.jar; C:\Oracle\MIDDLE~1\JROCKI~1.5-3\lib\tools.jar; C:\Oracle\MIDDLE~1\utils\config\10.3\config-launch.jar; C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar; C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar; C:\Oracle\MIDDLE~1\modules\features\weblogic. Server.modules_10.3.2.0.jar; C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar; C:\Oracle\MIDDLE~1\modules\ORGAPA~1.0\lib\ant-all.jar; C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1\lib\ant-contrib.jar; C:\Oracle\Middleware\oms11g\sysman\jlib\emConfig.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf-API.jar; C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\jrf-WLST.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.odl_11.1.1\ojdl.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.odl_11.1.1\ojdl2.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.dms_11.1.1\dms.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.dConfig-infra_11.1.1.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.fabriccommon_11.1.1\fabric-common.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.xdk_11.1.0\xmlparserv2.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.xdk_11.1.0\xml.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.WSM.common_11.1.1\wsm-pmlib.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.WSM.common_11.1.1\wsm-policy-core.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.WSM.common_11.1.1\wsm-secpol.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.WSM.common_11.1.1\wsm-dependencies.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle. WSM.policies_11.1.1\wsm-Seed-Policies.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.webservices_11.1.1\orawsdl.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.webservices_11.1.1\mdds.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.webservices_11.1.1\ws_confmbeans.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\org.Apache.Commons.digester_1.7.jar; C:\Oracle\MIDDLE~1\ORACLE~1\... \modules\javax. XML.bind_2.1.1.jar; C:\Oracle\MIDDLE~1\ORACLE~1\... \modules\javax.activation_1.1.jar. C:\Oracle\MIDDLE~1\ORACLE~1\... \modules\javax. XML.stream_1.1.1.0.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.http_client_11.1.1.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jmx_11.1.1\jmxframework.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jmx_11.1.1\jmxspi.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle. ADF.dconfigbeans_11.1.1.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle. ADF.share.CA_11.1.1\adf-share-base.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle. ADF.share.CA_11.1.1\adf-share-ca.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle. ADF.share_11.1.1\adflogginghandler.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle. ADF.share_11.1.1\adfsharembean.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle. ADF.share_11.1.1\commons-El.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle. ADF.share_11.1.1\jsp-El-API.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle. ADF.share_11.1.1\oracle-El.jar; C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\auditwlst.jar; C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\sslconfigwlst.jar; C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\oamap_help.jar; C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\ossoiap_help.jar; C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\resources\jps-WLST.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.auditprovider_11.1.1\jps-WLS-auditprovider.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jps_11.1.1\jps-manifest.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jps_11.1.1\jps-MBeans.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jps_11.1.1\jps-upgrade.jar; C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jps_11.1.1\jps-patching.jar; C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\lib\ADF-sh~1.jar; C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\lib\mdswlst.jar; C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\AUDITW~1.jar; C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\jps-WLST.jar; C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\jrf-WLST.jar; C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OAMAP_~1.jar; C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OAMAUT~1.jar; C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\ossoiap.jar; C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\OSSOIA~1.jar; C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\SSLCON~1.jar; C:\Oracle\MIDDLE~1\ORACLE~1\common\wlst\RESOUR~1\wsm-WLST.jar; C:\Oracle\MIDDLE~1\WLSERV~1.3\common\eval\pointbase\lib\pbembedded57.jar; C:\Oracle\MIDDLE~1\WLSERV~1.3\common\eval\pointbase\lib\pbclient57.jar; C:\Oracle\MIDDLE~1\WLSERV~1.3\common\eval\pointbase\lib\pbtools57.jar"weblogic. NodeManager '-v '.
  April 22, 2011 15:23:21 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: April 22, 2011 15:23:21 > < INFO > < domains file: C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.domains > 22 April 2011 15:23:21 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: April 22, 2011 15:23:21 weblogic.nodemanager.server.NMServerConfig initDomainsMap 22 April 2011 15:23:21 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: INFO: loading areas file: C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.domains April 22, 2011 15:23:21 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: April 22, 2011 15:23:21 > < WARNING > < domains file not found: C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.domains > 22 April 2011 15:23:21 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: April 22, 2011 15:23:21 weblogic.nodemanager.server.NMServerConfig initDomainsMap 22 April 2011 15:23:21 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: WARNING: areas file not found: C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.domains April 22, 2011 15:23:22 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: April 22, 2011 15:23:22 > < INFO > < store loading identity keys: FileName=C:/Oracle/MIDDLE~1/WLSERV~1.3/server\lib\DemoIdentity.jks, Type = jks, PassPhraseUsed = true > 22 April 2011 15:23:22 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: April 22, 2011 15:23:22 weblogic.nodemanager.server.SSLConfig loadKeyStoreConfig April 22, 2011 15:23:22 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: INFO: loading storage identity key: FileName=C:/Oracle/MIDDLE~1/WLSERV~1.3/server\lib\DemoIdentity.jks, Type = jks, PassPhraseUsed = true April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: April 22, 2011 15:23:23 > < WARNING > < folder properties for configuration manager node 'C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.properties' not found. Using the default settings. > April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: April 22, 2011 15:23:23 weblogic.nodemanager.server.NMServer < init > 22 April 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: WARNING: configuration properties manager node of the file 'C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.properties' not found. Using the default settings. April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: April 22, 2011 15:23:23 > < INFO > < Saving configuration properties node manager 'C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.properties' > 22 April 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: April 22, 2011 15:23:23 weblogic.nodemanager.server.NMServer < init > 22 April 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: INFO: save the configuration properties node manager 'C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.properties' April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: node Manager v10.3 April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: Configuration settings: April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: NodeManagerHome=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239 April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: ListenAddress = win2008x64-2, April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: ListenPort = 7401 April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: ListenBacklog = 50 22 April 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: SecureListener = true April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: AuthenticationEnabled = true April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: NativeVersionEnabled = true April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: CrashRecoveryEnabled = false April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: JavaHome=C:\Oracle\MIDDLE~1\JROCKI~1.5-3\jre April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: StartScriptEnabled = true April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: StopScriptEnabled = false April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: StartScriptName = startEMServer.cmd April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: StopScriptName = April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: LogFile=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.log April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: LogLevel = INFO April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: LogLimit = 0, April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: LogCount = 1 April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: LogAppend = true April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: LogToStderr = true April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: LogFormatter = weblogic.nodemanager.server.LogFormatter April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: DomainsFile=C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239\nodemanager.domains April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: DomainsFileEnabled = true April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: StateCheckInterval = 500 22 April 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: QuitEnabled = true April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: Interface = April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: NetMask = April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: UseMACBroadcast = false April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: DomainRegistrationEnabled = false April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: mappings of domain names: April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: April 22, 2011 15:23:23 > < INFO > < Secure socket listener started on 7 401, host WIN2008x64-2/192.168.182.135 port > April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: April 22, 2011 15:23:23 weblogic.nodemanager.server.SSLListener run April 22, 2011 15:23:23 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: INFO: Secure socket listener started on port 7 401, host WIN2008x64-2/192.168.182.135 April 22, 2011 15:23:30 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: Successfully launched the Node Manager. April 22, 2011 15:23:30 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: The Node Manager process runs independent of the WLST process. April 22, 2011 15:23:30 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: Exit WLST won't stop the Node Manager process. Please see April 22, 2011 15:23:30 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: to the Node Manager records for more information. April 22, 2011 15:23:30 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: Node Manager logs will be under C:\Oracle\MIDDLE~1\WLSERV~1.3\common\emnodemanager20110422152239 April 22, 2011 15:23:30 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: Connection to the node Manager... April 22, 2011 15:23:41 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: April 22, 2011 15:23:41 > < WARNING > < directory domain read when Configuration Error > April 22, 2011 15:23:41 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: weblogic.nodemanager.common.ConfigException: the field 'GCDomain' to 'C:\Oracle\gc_inst\user_projects\domains\GCDomain' was not saved in the file nodemanager.domains and dynamic domain registration is not supported. Please register the domain in the file nodemanager.domains. April 22, 2011 15:23:41 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: to weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:257) April 22, 2011 15:23:41 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: to weblogic.nodemanager.server.Handler.handleDomain(Handler.java:224) April 22, 2011 15:23:41 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: to weblogic.nodemanager.server.Handler.handleCommand(Handler.java:108) April 22, 2011 15:23:41 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: to weblogic.nodemanager.server.Handler.run(Handler.java:70) April 22, 2011 15:23:41 oracle.sysman.omsca.util.ProcessOutputReader run
  FINE: NMProcess: at java.lang.Thread.run(Thread.java:619) April 22, 2011 15:23:41 oracle.sysman.omsca.util.ProcessOutputReader run
  ...

  Vijay,

  Your correct. Even with regard to the OEMGC 10 g Oracle still doesn't have a Windows 64 bit for OEMGC 11 g version.
  It sometimes means that are all companies except 1, the GC server 64-bit Windows servers.

  Eric

• The configuration step of the calendar after the call to DAQm angular encoder, takes a lot of time vey even to 1000 samples per second. No idea why?

  I use an encoder in quadrature with DAQmx 6259, the call to read the outputs of the meter is slow, much slower than the sampling rate? No idea why?
  Thank you

  Hello Roxanne,

  In the title of this thread, you mention that the calendar configuration step takes a long time.  Is now called node configuration several times in your code?  You may find that your code runs faster if the channel configurations and the task doesn't occur once.

  Our example of the expedition, ' counting digital Events.vi ' may be of interest to you.

  Can be found by browsing our example search tool:

  'Help' examples

  Once opened, the example Finder you can find this example by browsing:
  "" material input and output"DAQmx" counter measures "County Digital Events.vi

  Best regards.

• Updates to configuration - step 3 of 3 (over and over again)

  After windows vista update I get this message that I reboot: "updates of configuration - step 3 of 3-0%" (translated from Danish: o). After awhile, it restarts and I get the same message again. " Can someone help me, please?

  Marianne2010
  See if you are able to boot mode safe mode with networking (one of the boot advanced options).  If this isn't the case then start with your Vista support and select the option to repair your computer.  Then do a system restore to a date prior to the update.  Once you are able to start and access the internet, then install this update: KB937287.  Once it is installed, and then run Windows Update. Mike - Engineer Support Microsoft Answers
  Visit our Microsoft answers feedback Forum and let us know what you think.

• LDAP configuration with vFoglight 6.5

  Im trying to configure LDAP services within our domain for use with vFoglight. My goal is to have a group operator and administrator group that uses our AD accounts instead of "local." I'm not sure if I have properly configure all LDAP settings. Can someone check my settings and let me know where can be the problem?

  Also under Administration > users & security management > user management > groups; The LDAP group button is grayed out. If the LDAP settings are correct this button will become live?

  Here are our settings:
  Account is anonymous. fake Unique name of the service account. Contoso . com\svc_acct password | **** LDAP query prefix | CN= Query LDAP suffix. OU = site, DC = corp, DC = contoso, DC = com The scopes to search for groups | UO = site, DC = corp, DC = contoso, DC = com The second space of group names. UO = site, DC = corp, DC = contoso, DC = com The third namespace group | "in white" The LDAP context for the user's search. UO = site, DC = corp, DC = contoso, DC = com Role attribute ID | name Is Role DN attribute | fake ID of user alias attribute | sAMAccountName ID of the attribute to search for groups | members Match the DN of the user. true JAAS LoginModule name | Security for JACQUES com.quest.nitro.service.security.auth.spi.NitroExtendedLdapLoginModule name field. FGL-web-console Group ID parent attribute | memberOf Attribute of the group to search for nested groups. members Maximum level of group nesting. 15 LDAP search time (milliseconds). 10 000 mode of research group | direct

  I hope that your problem has been resolved but support. You can also check our free training site: http://svgtraining.quest.com/ which has a video on the LDAP configuration.

• to use the help of a friend (distance) the configuration steps should I take?

  Hello

  use the help of a friend remotely, configuration steps I have to take?

  1. I see nothing in the services to enable

  2. I don't see anything in the windows firewall so that it

  3. what one thing I see in the computer properties in the Advanced section, I can help vink (enable) of distance.     Wil only be this option enough to get help from a friend or remotely?

  My second question is

  I know there are third party software to make contact with the client computer (remote assistance).

  are there any simple quiet easy to use for customers and third party free software, if so wat is the name of it?

  Thank you

  Johan

  Hi Johan

  You can use built-in Windows 7 Remote Assistance.

  What is Windows Remote Assistance? :

  http://Windows.Microsoft.com/en-us/Windows/what-is-Windows-remote-assistance#1TC=Windows-7

  There are also third-party products.

  Access, manage and support computers remotely:

  https://secure.LogMeIn.com/

  TeamViewer:

  http://www.TeamViewer.com/en/index.aspx

  Concerning

• OIM11g R2 PS2 Installation - problem to the IOM configuration step

  Hello

  I install OIM11gR2 PS2 to computer virtual RHEL5.4 installation. And I followed the steps of fixation with success. And now the configuration step IOM after making the field WL creation and facts Admin Server and running upward.

  In Assistant de Configuration IOM, step 4: screen of the WebLogic Admin Server.

  I have entered the following values:

  URL of the WebLogic Admin Server: t3: / / < xxxx >: 7001

  Username: weblogic

  Password: xxxxxx

  After you click Next, it is not further.and of the Forum got stuck at step 4 for more than an hour. I tried several times but the same problem persists.

  Could someone please help me out here.

  Enjoy a quick help.

  Thank you

  Maryse

  I think that your SOA server is not upward. Early SOA server and then click Next. Make sure that before you run the Configure Server Admin and SOA are rising.

  Kind regards

  ARI

• After the LDAP configuration cannot connect - ERROR: failed to connect vcloud use meter 3.2

  LDAP configuration page settings are as below: -.

  Host:-domain name

  port - 636

  Use SSL - verified

  username - DN [email protected]

  Password-*.

  Base DN of the user - OU = test, DC = test, DC = com

  User object class-

  User name attribute - sAMAccountName

  When I try to open a session using

  test. com\testuser or [email protected] it says ERROR: failed to connect

  and

  Cat /var/log/usgmtr/um.log--spectacles suite error -.

  Excerpt of ERROR [http-bio-8443-exec-1]. Authenticator: org.apache.directory.shared.ldap.model.exception.LdapInvalidDnException: ERR_04202 a value is missing on some RDN

  can anyone suggest what could be the problem

  Indicated user name is a UPN or Email address... not a DN.  DN resemble CN = test, OU = test, DC = test, DC = com.

  Please post the exact value of the DN using LDP or a similar LDAP tool against the LDAP provider to check the attribute for the metering login account.

  LdapInvalidDnException

• LDAP Configuration problem - BEEP in a deployment of OBIEE

  All,
  I have an OBIEE 11 g (11.1.1.6.0), including environmental BI Publisher put in place. I have successfully completed the integration of OBIEE with LDAP and LDAP ID user can connect you with the Group/privilege information is applied as announced. BI Publisher, however, is not so cooperative. Here's what I have:
  
  As part of the LDAP configuration, I replaced the BISystemUser id with a user based on LDAP, ADBISystemUser id. However, whenever someone tries to connect, they get the error message * "[53012]" user authentication failed: adbisystemuser "*." The BIP newspaper shows this same message, preceded by the message * "[nQSError: 43113] Message returned by OBIS." * I know with certainty that this user id is configured correctly - OBIEE users are able to connect, and my LDAP browser is able to connect using these credentials.
  
  At RANDOM, I have the Administration-> Security page configured as follows:
  
  Local superuser: enabled (this is the only way I can connect now)
  
  Authentication: authentication UNIQUE not selected; Use LDAP selected and the correct LDAP, id, password etc entered configuration settings.
  
  Authorization: security model = BI Server and the correct settings for this entry (entry in the installation, no change)
  
  
  I searched nQSError 43113 and 53012 and validated different suggestions I've seen without success. I can't tell you how many times I rebooted services. I have reset the GUID, verified passwords/accounts are locked out, tested and retested in BEEP passwords match those of LDAP. The only thing that worked (sort of), was when I jumped LDAP protocol for authentication and set up LDAP for authorization (3rd section on the Administration-> Security Page). When it is configured for LDAP, the BEEP was able to bind to LDAP and users could connect. Unfortunately, given that we were not BI server authorization, users could not see the folders, or they would avoid data sources or report objects. What do we have this test was to confirm that BEEP pourrait LDAP access. It is not the way I need to do.
  
  The last thing I tried was to adbisystemuser id in LDAP so that it lay in the same "folder" as all my users instead of a folder, separate service accounts. Even this was not useful. I implemented the XMLP * groups, even though I do not expect that these are referenced. The id adbisystemuser is a member of XMLP_ADMIN, and users have been added to the XMLP_DEVELOPER group, for what it's worth.
  
  Suggestions or recommendations on how to get the BEEP if authenticate to LDAP would be really appreciated!
  
  Thank you!
  Eric

  Eric,

  In my setup, I use Fusion Middleware as a model of security and everything seems to work.

  In the documentation model Oracle BI Server is Legacy only:

  5.2 integration with Oracle BI Server Security
  The security option Oracle BI Server is for customers who want to use the authentication of the legacy of 10g. This section does not apply if you set up Oracle Fusion Middleware security.

  Michael

• LDAP configuration problems

  Dear all,

  This is my first interaction with VCeneter Orchestrator and I am facing a problem in the configuration of the LDAP configuration. He expects the Strait for me but he said Dungeon "configuration Ldap registered successfully, but the configuration is wrong.»

  Connection error: LDAP successful but no users found. Check LDAP paths.

  Group Admin not found error

  I don't know what I did so wrong if someone could guide me to set this configuration in the right way.

  I entered the name of the domain controller and test the connectivity by using Telnet and everything was fine. Only the root using unique name format exported from Active directory using the DSQuery command.

  the resource used was VM_ Orc. configuration guide.

  Your accesnance is much appreciated.

  Thank you.

  Ahmed Salah

  For example, assuming that a field of acme.corp with all users in the default location and the groups in the default location, you configure the paths as follows. This example uses a group named 'vcoadmins' with the 'administrator' account a member of this group:

  Root: dc = acme, dc = corp

  User name: [email protected]

  User search base: cn = users, dc = acme, dc = corp

  Group search base: cn = users, dc = acme, dc = corp

  vCO Admin group: cn = vcoadmins, cn = users, dc = acme, dc = corp

  This help at all?

• the weblogic 10.3 OID/ldap error

  Hello:
  
  We are migrating our application of OC4J to weblogic 10.3. The application has some problem to access the OID/LDAP. Here is the error when the application attempts to connect to LDAP:
  
  Exception in thread "Thread-13" java.lang.ArrayIndexOutOfBoundsException: 10
  to weblogic.rjvm.RJVMFinder. < init > (RJVMFinder.java:98)
  at weblogic.rjvm.ServerURL.getFinder(ServerURL.java:181)
  at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
  to weblogic.jndi.WLInitialContextFactoryDelegate$ 1.run(WLInitialContextFactoryDelegate.java:344)
  at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
  at weblogic.security.service.SecurityManager.runAs (unknown Source)
  at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:339)
  at weblogic.jndi.Environment.getContext(Environment.java:315)
  at weblogic.jndi.Environment.getContext(Environment.java:285)
  at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
  at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
  at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
  at javax.naming.InitialContext.init(InitialContext.java:223)
  to javax.naming.ldap.InitialLdapContext. < init > (InitialLdapContext.java:134)
  at oracle.ldap.util.jndi.ConnectionThread.run(ConnectionThread.java:61)
  log4j:error no file or output stream is defined for the appender named "null".
  
  
  Us did not change any code and everything works find on our OC4J application server. It stops working on weblogic 10.3. Does anyone have a similar experience?
  
  Thank you
  
  Jack

  Hello

  It seems that the ConnectionUtil class is not supported with WLS. I managed to do work by creating the initial Ldap context manually:

  replace

  InitialLdapConetxt ldapCtx = ConnectionUtil.getDefaultDirCtx(ldapServerName, ldapServerPort, ldapUserDN, ldapUserPass);
  RootOracleContext roc = new RootOracleContext(ldapCtx);
  

  by

  Hashtable env = new Hashtable();
  env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.ldap.LdapCtxFactory");
  env.put(Context.SECURITY_AUTHENTICATION, "simple");
  env.put(Context.SECURITY_PRINCIPAL, ldapUserDN);
  env.put(Context.SECURITY_CREDENTIALS, ldapUserPass);
  env.put(Context.PROVIDER_URL, "ldap://" + ldapServerName+ ":" + ldapServerPort + "/");
  env.put(Context.REFERRAL, "follow");
  
  InitialLdapConetxt ldapCtx = new InitialLdapContext(env, null);
  RootOracleContext roc = new RootOracleContext(ldapCtx);
  

  I hope this helps.

  Kind regards
  Friedrich

• LDAP configuration

  Hi, I am trying configure LDAP authentication service.
  The domain name for the user name I know is correct (it came from Softerra LDAP browser).
  The part I'm not too sure of is the query LDAP prefix and suffix.
  If the right prefix be CN =?
  All I want to do is add a couple of ad groups in AD 1 ORGANIZATIONAL unit.
  Pointers would be useful.
  Thank you

  Hello mrvirtual,
  The first step
  You will notice that the LDAP query prefix is set to CN =
  Change of CN = to be sAMAccount =
  It behave like the same transverse and the tree OR AD NTLM authentication
  Two step
  Change the suffix, LDAP query to reflect only the parameters of DC
  EXAMPLE: DC = example, DC = com
  Step three
  Change the LDAP context for the user the same search as the previous step, but without the leading comma
  EXAMPLE: DC = example, DC = com
  The fourth step
  Change the scopes to search groups pointing toward an ORGANIZATIONAL unit that contains the group that users are memberof
  Create an internal group in vFoglight by exactly the same name (as in the previous step ad group) and assign roles to the group. That when a user logs in using their credentials to the AD, it will be automatically added to this group and get corresponding roles.
  That's the gist of it. If you still encounter any errors then best option would be to open a pension deal because at that time, we will have to review the settings.
  Concerning

• W520 WiDi configuration steps

  Hello

  I just got a helping hand me down w520 and I was wondering how to set up the widi with my new LED TV LG 47LM7600 which has a WiDi built into the TV set. Can someone show me please step by step to configure the w520 widi? What software do I need? How to use the software for my TV? ect...

  Thank you.

  
  

• Net M4110x - Net management and iSCSI. Clarification of the configuration steps. The documentation is at best ambiguous.

  Hi guys,.

  I'm having a lot of trouble to translate what I know PS6000 table to the new M4100x.  Here's what I'm building:

  

  I want my iSCSI traffic that is completely isolated from all other traffic, and I want to use the CMC network to run the Board.  It must be a simple configuration, but Dell documentation for which is worse than useless.  It confuses and everyone who's read it confuses.  Why is this?

  It seems that I should be able to assign the IP addresses of management using the MCC according to DELL:

  Step 1.  Initialize the storage

  * Once in the CMC right-click on storage open storage gui initialization.

  * Member name: MY_SAN01
  * Member, IP: 192.168.101.10
  * Member gateway: 192.168.101.254
  Group name: MY_SAN
  Group IP address: 192.168.101.11
  Group of Memebersip password: groupadmin
  * Password Admin group: groupadmin

  It sounds simple enough, and when I apply this I guess I will be disconnected my M4110x simply because it currently resides on a separate network (net 2 in the image above).  Now how to set up the IP address of my CMC (net0 in the picture above) network management?

  Step 2.  Set ip management port

  According to the documentation of Dell, I have:

  To set the management port:

  * Open a telnet (ssh) session on a computer or console that has access to the PS-M4110 range. The array must be configured beforehand.
   
  * Connect the PS-M4110 modules using the following racadm command: racadm Server 15 connect
   
  * Connect to the PS-M4110 array as grpadmin

  Once I am in:

  Activate the management controller ports using the following commands in the CLI:
  0 > member select MY_SAN01
  1. (array1) > eth select 1
  2. (array1 eth_1) > 10.10.10.17 ipaddress netmask 255.255.255.0
  3. (array1 eth_1) > upward
  4. (array1 eth_1) > exit
  5. (array1) > grpparams
  6. (array1 (grpparams)) > network management-ipaddress 10.10.10.17

  (array1 (grpparams)) > exit

  My interpretation is correct?  Now my questions:

  1. in step 2. SubStep 1 - How can I know what ethernet interface to use?  Step 1 automatically assume eth0?

  2. am I correct in using the same IP address for both step 2 - substep 2 and substep 6?  Or do I have to assign a different IP address for these?  10.10.10.18 maybe.

  3. step 2 - substep 6, it doesn't seem to be that a network mask is that correct?

  4. comparison of the ps6000e - I set up an IP address for each controller (so 2) and then assigned an IP address for the group.  It's 3 IP addresses.  For this M4110, it seems that I have only one controller.  Is this correct?  The specifications make a point that there are 2 controllers.  What happened to the IP address of the controller of the 2nd?

  CLOSE-UPS

  I intend on building a VMware cluster using the algorithm of multiple paths of DELL and I built it to the DSC, but a technician Dell put in place the table initially and have not set up a dedicated management port.  Required configuration routing traffic on the net iSCSI management.  It is not recommended, and I don't want to set up this way.

  Currently, he is a blocking problemand I need to go beyond this ASAP.  I work with a large system integrator in Texas and plan on the order that these systems built this way on their part.  This means that I must be able to explain to them how to proceed.  This issue is standing in the way of progress, and I really hope I can get a satisfactory response from this forum.  Thanks for any helpful answers.

  I think I have the answers to my own questions:

  1. YES.  Step 1 automatically assume eth0.  There are TWO Ethernet interfaces and eth1 is disabled by default, and unless you use step 2 to set the management port this second Ethernet interface is never used.

  2. No. I can't use the same IP address for both lines.  In lower level 6 I need to use a different IP address on the same network 10.10.10.18 would work fine.

  3. YES.  It is correct.  Lower level 6 assumes the network mask that I have included in the point 2.

  4. it's tricky.  There is NO WAY to configure Active/active on these tables.  There are 2 controllers, but one "still asleep," unless the other fails.  Actually, the IP address is assigned to an Abstraction Layer, it maintains.  When fails another controller "awakens" and just starting to accept traffic and it doesn't care what its IP address.

  Another point.  Now that my table is initialized and my interfaces are configured, I need to know what IP address to point my ESXi hosts for their storage.  Use the IP address of the group assigned in step 1.  It is 192.168.101.11 (there is typo in the original post).

• BEA WebLogic Server 8.1 IS an external LDAP Configuration supported?

  Hi all

  We have server BEA Weblogic 8.1, and we intend to add the external LDAP authentication to the web application deployed on weblogic.

  Is BEA Weblogic server 8.1 support external LDAP OmniPass?

  Please help me.

  Thank you

  Ankit Patel

  Hi Pierre,.

  Yes, we can include external services Ldab here.

  http://docs.Oracle.com/CD/E13222_01/WLS/docs81/secmanage/providers.html#1109511

  • Configure a new iPlanet authenticator...
  • Configure a new authenticator realm adapter...
  • Configure a new Active Directory authenticator...
  • Set up a new default authenticator...
  • Set up a new default identity Asserter...
  • Configure a new authenticator OpenLDAP...
  • Configure a new authenticator of Novell...

  Kind regards

  Kal