Ping target RT

Similar Questions

• Command chain vmkping all script and return results in a txt file

  Hi guys, hope you all are doing it very well?

  Does anyone know if there is a way I can put this together?

  What I'm trying to do here is to circumvent the tedious process of ping every IP configured for my target iSCSI through each VMK of each host.

  So basically I want some advice from you guys for what I can basically get this in a script.

  vmkping - I vmk1 10.0.0.10

  vmkping - I vmk2 10.0.0.10

  vmkping - I vmk3 10.0.0.10

  vmkping - I vmk4 10.0.0.10

  vmkping - I vmk5 10.0.0.10

  vmkping - I vmk6 10.0.0.10

  vmkping - I vmk7 10.0.0.10

  vmkping - I vmk8 10.0.0.10

  vmkping - I vmk9 10.0.0.10

  vmkping - I vmk1 10.0.0.11

  vmkping - I vmk2 10.0.0.11

  vmkping - I vmk3 10.0.0.11

  vmkping - I vmk4 10.0.0.11

  vmkping - I vmk5 10.0.0.11

  vmkping - I vmk6 10.0.0.11

  vmkping - I vmk7 10.0.0.11

  vmkping - I vmk8 10.0.0.11

  vmkping - I vmk9 10.0.0.11

  vmkping - I vmk1 10.0.0.12

  vmkping - I vmk2 10.0.0.12

  vmkping - I vmk3 10.0.0.12

  vmkping - I vmk4 10.0.0.12

  vmkping - I vmk5 10.0.0.12

  vmkping - I vmk6 10.0.0.12

  vmkping - I vmk7 10.0.0.12

  vmkping - I vmk8 10.0.0.12

  vmkping - I vmk9 10.0.0.12

  etc... etc...

  Do this on all hosts is to take more time than I'd like to take. Because we are busy of troubleshooting an issue on our switches where some of the ports VMK are unable to communicate to the target. Is there anyway that we can this script?

  Please guys, I'm desperate here.

  Kind regards

  Johan

  You can do it from a bash script.

  This is a working script that gets a list of all the vmkernel ports then each IP provided in a file list.txt on each vmkernel port pings. The results are printed to the screen but to get the results to just the output of the line pipe.

  Here is an example:

  "sh vmkping.sh > / tmp/vmkpingResults.log".

  #! / bin/bash

  # Name of the program: vmkpingall.sh

  # Store a file list.txt with each target IP storage on a separate line

  #---EXEMPLE list.txt-

  #172.16.191.50

  #172.16.192.50

  #-----------------------------

  #Print the date and host name

  Date

  host name

  #get a list of all the ports of vmk on the host

  for vmknum $ (esxcli network ip interface list | grep vmk | grep - v name :))

  do

  White space #Trim

  vmkCompare = "${vmknum # * ()}" "

  #Trim trailing whitespace

  vmkCompare = "${vmkCompare % * ()}" "

  # Exclude vmk0, because we do not use our management traffic vmotion vmkernel port so pings are supposed to do not on vmk0

  If ["$vmkCompare"! = "vmk0"]; then

  Cat /path-to-script/list.txt |  while reading output

  do

  #use vmkping port command selected vmk '-I ' ping target IP addresses

  vmkping - I "$vmknum" - ch. 1 "$output" >/dev/null

  If [$?-eq 0]; then

  echo 'node $output's place on $vmknum

  on the other

  echo "$output node is down on $vmknum.

  FI

  fact

  FI

  fact

• Deploy the agent EM12C initialization of the phase error sending software agent

  During the deployment of EM12C in the initialization stage - software agent agent sent to the error of host target
  The file to the SGD/m02 / midd/WHO/sysman/agent / 12.1.0.2.0 AgentCore226. Zip is copied to the host/m01 ADATMP_2013 on 192.168.165.83 - 03-28 _11-01-33 - error failure AM message: PROV - 16011: Auth fail
  Exit code: 0
  (1) the user authentication is oracle
  (2) the target users oracle sudo ls-l/root this command
  (3) the em can SSH connection to the target host

  Why are you using "-ignorePrereqs" parameter? You should not use this parameter to this than recommended by Oracle support or running in some soaps question. It will ignore any pre - req check and it is not recommended to ignore any failure pre - req controls, that can cause more problems with agent later.

  one) from ping target machine omshost
  Ping
  (b) of the Agent machine, run the below

  wget http://:/empbs/genwallet
  or
  wget https://:/empbs/genwallet
  Someone at - he of the foregoing should be connected to the machine of the WHO.

  Above two work then try installing the agent with on the "-ignorePrereqs" parameter and look in the more detailed error log file: agent_home/cfgtoollogs/agentdeploy/*.*

• After that stright connected to iSCSI (initiator) Host cannot ping the server iSCSI (target), but the target can, why?

  After that host on vSHere 4.0 strightly connected to iSCSI (initiator) host cannot ping the server iSCSI (target), but target can.  And iSCSI works well. I mean I can create and use the iSCSI disk, why? It makes me confused.

  Thank you!

  Geoarge,

  iSCSI traffic uses a VMkernel port, instead of using the command 'ping', use 'vmkping '.

  André

• 'Find all Targets.vi' blocks 2009 development environment

  Hi people,

  This is a first for me - 2009 v9.0f3 running and have problems with the above vi (included as part of the example of "Replication of system"). I used this VI for a while now and never had this problem.

  The local NIC 10/100 the value by default, but if static DHCP DHCP not available (172.16.1.1/255.255.0.0).

  PSC-2010 is static to 172.16.1.2

  Link/ping find between the target and the computer host.

  Target is running RT v8.5.1, FP VI Manager 6.0.1 / PS drivers 6.0.0 and variable customer support for LV RT.

  Crashes when:

  -host to PSC-2010 PC connection is OK

  AND

  -' Find not only configured "bool terminal is set to (False)

  Won't crash if:

  -computer host is connected to the network 'coorperate' and a IP through DHCP (no target address). Or bool value.

  -host to PSC-2010 PC connection is OK

  AND

  -' Find not only configured "bool terminal is set to (true)

  Crash is difficult - no "program has stopped responding", all the windows just left LabVIEW.

  Recovery comes into play on the next launch of LV, but no error report.

  Any thoughts? Don't know where to start, another that * perhaps * an another PSC-2010.

  Kind regards

  Jamie

  After that I realized that it was actually a DevZone Toolbox, I re-uploaded, re-placed in the \user.lib folder, and everything's fine.

  Thank you

  Jamie

• Can ping but not connect to the system in real time

  Hi all

  I have a funny glitch that has arisen recently.  I have a PXI chassis running an RTOS that I am able to reach with LV and MAX when I sit on the local network.  I have the chassis in a DMZ, so she is directly exposed via the external IP network.  Recently, I had to reformat the hard drive and now, for some reason I can't access the system via MAX or external LV (I have before).  I ping the instrument, but it seems not respond with MAX or LV there is no error on the target and the target is not currently a start of VI.  Someone at - it ideas?

  Thanks, m

  NM - I don't know what was going on, but everything seems fine now... I had the wrong IP today.

  For those who are interested, this is a report of nmap on intellectual property will look like if you do a scan of 1-10 k on a PXI chassis located on a DMZ (I'm not pass all other ports, but some ports such as 80 react on the machines on the network):

  

  Thank you for your attention.  m

• can not see Add targets and devices in the Project Explorer

  Hello!

  I think I have a strange question. I have the evaluation version of Labview 2010. I am trying to add my cRIO 9004 to a project. I'm just trying to follow the instructions in the getting started with manual cRIO. It is said, add crio to the project by project root right clicking and selecting NEW > ADD TARGETS AND DEVICES. The problem is I can't see the link to the NEW, but once I click that I see not a link under "add new target or device" appear, instead, I see the dialog box to open a NEW FILE LABVIEW appear. everywhere in distress forum/basic knowledge/support of shooting and get started articles have mentioned project root right click > select NEW > select Add a target or peripheral >, as if she IS supposed TO APPEAR STANDARD in all new projects! But I'm not! I do not understand what Miss me. The version of software that I have are below:

  the cRio:

  OR VISA 5.0

  NEITHER RIO 3.0
  RT LV 8.6

  and he allied himself with what I installed on my host.

  I can communicate with the device of cRIO times using MAX as well as ping at the windows command prompt command.

  Any help would be great!

  Thank you!

  Rajesh

  After you have installed the evaluation version of LV 2010, you reinstall all of the other drivers, as for the cRIO?

• Remote Desktop connection failed but successful ping

  I am trying to connect via RDC (Remote Desktop Connection) of the SOURCE to the DESTINATION.

  I welcomed the remote connections on the DESTINATION and added couple of users who are allowed to connect remotely.
  I can ping DESTINATION SOURCE successfully.

  None of the responses failed to control below SOURCE
  C:\ > ping-l 512 f - n 100

  Strange thing is that I can remote login from DESTINATION to SOURCE, but not vice versa.

  I don't remember making any additional settings to other machines that are connected to remote. Only one machine (the DESTINATION) to the question.

  Any thoughts are appreciated.

  Thank you
  Biausse.

  On the target computer, make sure that Port 3389 is not blocked by a firewall.  If you use Windows Firewall, go to the control panel Windows Firewall, check that "Don't allow Exceptions" is not checked in the "Général" tab, then click the 'Exceptions' tab and make sure there is a check mark next to "Remote Desktop".

  You can also ensure that a program is to accept incoming remote desktop connections to raise a command prompt (start-> Run-> "cmd") and entering the following command:
  netstat - year |    find "3389.
  If all goes well, you should see the following line returned:
  TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING

  HTH,
  JW

• Connect two targets in real time via TCP/IP

  Hello everyone

  I need to connect two targets of RT on TCP/IP protocols

  I have two sbRIO Council related to a single host PC through an Ethernet router

  and I have two IP address of these two targets, how do I RT - RT ping using the TCP/IP protocol...

  Thank you

  Syed irfan

  irfan789 wrote:

  As I am with RT if the IP address of the two targets has a role to play in this communication via TCP/IP

  In order to open a TCP connection, you must provide the IP address of the remote computer. It does not matter what operating system, the remote computer is running. If that does not meet your question, so I don't understand what you're asking.

• Cannot open websites, error DNS when the ping command cannot resolve the name

  Cannot open all websites on a PC. (other computers on the network can access the sites without a problem)
  Error message is "Internet Explorer cannot display webpage."

  I can ping (internal and external) of the IP and gateway addresses.
  Ping translates:
  C:\>ping www.yahoo.com
  Ping request could not find host www.yahoo.com. Please check the name and try again.

  Nslookup translates:
  C:\>nslookup www.yahoo.com
  Can not find the name of the server for the address 192.168.0.1: non-existent domain
  Default servers are not available
  Server: unknown
  Address: 192.168.0.1

  Non-authoritative answer:
  Name: www-real.wa1.b.yahoo.com
  Address: 69.147.76.15
  Alias: www.yahoo.com, www.wa1.b.yahoo.com

  Pathping translates:
  C:\>Pathping www.yahoo.com
  Unable to resolve target system name www.yahoo.com.

  The problem occurs on a wired and wireless connection.
  Reset TCP/IP via netsh int ip reset c:\ressetlog.txt results in the following in the log file error message:

  discount Linkage\UpperBind for USB\VID_0B05 & PID_1723\5 & 2461925A & 0 & 5.  incorrect value was:
  REG_MULTI_SZ =
  SymIM

  Is there a total of 9 errors in the log similar to the one above.
  The host file has only 127.0.0.1 in there.
  Clearing the cache of the arg, flushing the DNS and do a repair on the network connection does not resolve the problem.
  Install a new network device does not resolve the problem.
  I also deleted all the antivirus software and security, including firewalls.
  The Windows Firewall is disabled.
  Boot in safe mode with Networking does not solve the problem.
  Running Winsockfix does not solve the problem.
  Internet Explorer 8 (reset web settings has been done)
  Windows XP Media Center with SP3
  Execution of the IE Diagnostics results in an error 12007 the server name or address cannot be resolved.

  Get the end of the line...

  Any other ideas?

  Thank you

  Larry

  Sorry for the late reply, but I did not have access to the MS Web site for a few months.

  I tried your suggestions, they do not work.

  The resolution is to do a repair of the operating system out of the CD.  Who cleared up the problem.

  Thank you

  Larry

• Cannot ping port host MD3000i on RC0

  Hello

  I have set up my iSCSI network, as suggested in this post:

  http://en.community.Dell.com/TechCenter/storage/w/wiki/MPIO-to-PowerVault-MD3000i-with-Microsoft-iSCSI-initiator.aspx

  I can only ping the ports of controller RAID 1 (two ports). All of my iSCSI traffic is drunk through the controller. Windows Server 2008R2 (R710/810), but also an ESXi 4.1 cluster (R610 and PE2950) access the dedicated iSCSI network. I contacted the support a few weeks ago, and they have replaced the MD3000i RAID controllers as well as the background. They are insistent that there is a configuration problem and would not assist any more beyond to send me links suggested configs. I went through the Setup on the R810 (Windows 2008R2) from scratch. This has not produced different results. Then I updated all drivers (BCM5709Cs) NETWORK card and software on all hosts, successfully restarted the MD3000i and the two MD1000s bike powered two switches HP Procurve 1400 and restarted all hosts. I can't always ping RC0. I Putty and captured RC0 boot logs, but it was not obvious to me. Here are the logs of boot:

  -=<###>=-
  Set the interface lo0... done

  Autonomous 9768 symbols added.
  Error
  03/26/13-16:44:29 (GMT) (tRootTask): NOTE: I2C transaction returned 0x0423fe00

  ATTENTION: Reset by spare controller

  Current date: 26/03/13 time: 09:26:15

  Send Change Service Interface rate or baud
  03/26/13-16: 44:46 (GMT) (NCDB): NOTE: sequence SOD is Normal, 0
  03/26/13-16: 44:46 (GMT) (NCDB): NOTE: SOD: removed host SAS from index 0
  03/26/13-16: 44:46 (GMT) (NCDB): NOTE: in iscsiIOQLIscsiInitDq.  iscsiIoFstrBase = 0 x 0
  03/26/13-16: 44:46 (GMT) (NCDB): NOTE: turn on seeing failure summary tray
  03/26/13-16: 44:48 (GMT) (NCDB): NOTE: SYMBOL: SYMbolAPI registered.
  esmc0: event LinkUp
  03/26/13-16: 44:50 (GMT) (tNetCfgInit): NOTE: the loan network
  03/26/13-16: 44:51 (GMT) (NCDB): NOTE: channel initiating Drive: ioc:0 bringup
  03/26/13-16: 44:54 (GMT) (NCDB): NOTE: the Firmware Version of the IOC: 00-24-63-00
  03/26/13-16: 45:17 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan: 0 phy:0 prevNumActivePhys:2 numActivePhys:2
  03/26/13-16: 45:17 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan: 0 phy:1 prevNumActivePhys:2 numActivePhys:2
  03/26/13-16: 45:17 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan: 1 phy:2 prevNumActivePhys:2 numActivePhys:2
  03/26/13-16:45:18 (GMT) (tSasEvtWkr): NOTE: sasIocPhyUp: chan: 1 phy:3 prevNumActivePhys:2 numActivePhys:2
  03/26/13-16:45:18 (GMT) (tSasCfg021): NOTE: path of the Alt up - chan: 0 phy:18 itn:1 controller
  03/26/13-16:45:18 (GMT) (tSasCfg022): NOTE: path of the Alt up - chan: 1 phy:16 itn:2 controller
  03/26/13-16:45:18 (GMT) (IOSched): NOTE: discoveredEncl: enclosure: 1, enclProp: x2c50104, trayId: slotCount 2:15
  03/26/13-16: 45:19 (GMT) (NCDB): NOTE: IonMgr: Drive Interface enabled
  03/26/13-16: 45:19 (GMT) (NCDB): NOTE: SOD: instantiation Phase complete
  03/26/13-16: 45:19 (GMT) (NCDB): NOTE: controller between open Communication channels
  03/26/13-16: 45:19 (GMT) (IOSched): NOTE: initiator of news: 1 - channel: 1, devHandle: x2c, SAS address: 590b11c41a9d8b00
  03/26/13-16: 45:19 (GMT) (tSasDiscCom): NOTE: complete a discovery SAS task created
  03/26/13-16: 45:19 (GMT) (NCDB): NOTE: LockMgr role is slave
  03/26/13-16: 45:19 (GMT) (IOSched): NOTE: discoveredEncl: enclosure: 1, enclProp: x2c9516c, trayId: slotCount 2:15
  03/26/13-16: 45:19 (GMT) (IOSched): NOTE: new initiator: 2 - channels: 0, devHandle: x1a, SAS address: 590b11c41a9d8b01
  03/26/13-16: 45:21 (GMT) (IOSched): NOTE: discoveredEncl: Speaker: 2, enclProp: x2c8f730, trayId: 1, slotCount: 15
  03/26/13-16: 45:21 (GMT) (sasCheckExpanderSet): NOTE: Expander Firmware Version: 0116-e05c
  03/26/13-16: 45:21 (GMT) (sasCheckExpanderSet): NOTE: address SAS Expander: salvation = Low = xf6ac8d10 x5848f694
  03/26/13-16: 45:21 (GMT) (tSasDiscCom): WARN: SAS: Initial full time of discovery: 33 seconds
  03/26/13-16: 45:21 (GMT) (IOSched): NOTE: discoveredEncl: Speaker: 2, enclProp: x2c66ad4, trayId: 1, slotCount: 15
  03/26/13-16: 45:22 (GMT) (NCDB): NOTE: spmEarlyData: from alternate data
  03/26/13-16: 45:22 (GMT) (NCDB): NOTE: WWN baseName (valid ==> SigMatch) 00040026-b95795de
  03/26/13-16: 45:23 (GMT) (NCDB): NOTE: ionEnableHostInterfaces is waiting for a channel lends itself
  03/26/13-16: 45:26 (GMT) (NCDB): NOTE: ionEnableHostInterfaces expected 3800ms for a channel lends itself
  03/26/13-16: 45:26 (GMT) (NCDB): NOTE: IonMgr: Host Interface enabled
  03/26/13-16: 45:26 (GMT) (NCDB): NOTE: SOD: pre to complete initialization Phase
  03/26/13-16: 45:47 (GMT) (NCDB): NOTE: ACS: autoCodeSync(): beginning of the process. Comm mode: 0, State: 1
  03/26/13-16: 45:47 (GMT) (NCDB): NOTE: SOD: complete Phase initialization Code synchronization
  03/26/13-16: 45:48 (GMT) (NvpsPersistentSyncM): NOTE: persistent storage NVSRAM updated successfully
  03/26/13-16: 45:48 (GMT) (NCDB): NOTE: initialization complete USM Mgr with 0 records.
  03/26/13-16: 45:49 (GMT) (NCDB): NOTE: BDU - received 1 small files
  03/26/13-16: 45:49 (GMT) (NCDB): NOTE: BDU - received 0 records of great
  03/26/13-16: 45:50 (GMT) (NCDB): NOTE: acquire 0.035 dry
  03/26/13-16: 45:53 (GMT) (NCDB): NOTE: QLStartFw: FW drive download image 03.00.01.47 033eab00 4c0c8 bytes, result 0
  03/26/13-16:45:55 (GMT) (tRAID): NOTE:  ********************************************************************************
  03/26/13-16:45:55 (GMT) (NCDB): NOTE: Application target QLogic, 2.01.08 Version 2005-06-13 (W2K)
  03/26/13-16:45:55 (GMT) (NCDB): NOTE: iSCSI Target Application
  03/26/13-16:45:55 (GMT) (tRAID): NOTE:   ********************************************************************************
  03/26/13-16: 45:56 (GMT) (NCDB): NOTE: QLInitializeFW: iSNS Server 0.0.0.0:3205
  03/26/13-16: 45:56 (GMT) (NCDB): NOTE: QLInitializeFW: ISNSServerIPv6Addr 00:00:00:00:00:00:00:00: 3205
  03/26/13-16: 45:56 (GMT) (NCDB): NOTE: QLInitializeFW: iSCSI name iqn.1984 - 05.com.dell:powervault.md3000i.60026b90005795de000000004b2ae7b6
  03/26/13-16: 45:56 (GMT) (NCDB): NOTE: QLInitializeFW: port = 0, turn on IPv4 = 1, turn on IPv6 = 0
  03/26/13-16: 45:56 (GMT) (NCDB): NOTE: QLInitializeFW: 10.182.233.250:3260 IP address
  03/26/13-16: 45:56 (GMT) (NCDB): NOTE: QLInitializeFW: Firmware waiting for DHCP lease.  State 18
  03/26/13-16: 45:56 (GMT) (NCDB): NOTE: QLInitializeFW: 18 FwState 000/010 of time
  03/26/13-16: 45:57 (GMT) (NCDB): NOTE: QLInitializeFW: 10/01/00 18 FwState of time
  03/26/13-16: 45:58 (GMT) (NCDB): NOTE: QLInitializeFW: 10/02/00 18 FwState of time
  03/26/13-16: 45:58 (GMT) (IOSched): NOTE: QLIsrDecodeMailbox: Port 0 bind upward.
  03/26/13-16: 45:59 (GMT) (NCDB): NOTE: QLInitializeFW: 10/03/00 FwState time 0
  03/26/13-16: 46:00 (GMT) (NCDB): NOTE: QLInitializeFW: port = 1, turn on IPv4 = 1, turn on IPv6 = 0
  03/26/13-16: 46:00 (GMT) (NCDB): NOTE: QLInitializeFW: 10.182.232.250:3260 IP address
  03/26/13-16: 46:00 (GMT) (NCDB): NOTE: QLInitializeFW: Firmware waiting for DHCP lease.  State 18
  03/26/13-16: 46:00 (GMT) (NCDB): NOTE: QLInitializeFW: 18 FwState 000/010 of time
  03/26/13-16: 46:01 (GMT) (NCDB): NOTE: QLInitializeFW: 10/01/00 18 FwState of time
  03/26/13-16: 46:02 (GMT) (NCDB): NOTE: QLInitializeFW: 10/02/00 18 FwState of time
  03/26/13-16: 46:03 (GMT) (NCDB): NOTE: QLInitializeFW: 10/03/00 FwState 18 time
  03/26/13-16: 46:03 (GMT) (IOSched): NOTE: QLIsrDecodeMailbox: Port 1 link up.
  03/26/13-16: 46:04 (GMT) (NCDB): NOTE: QLInitializeFW: 10/04/00 FwState time 0
  03/26/13-16: 46:05 (GMT) (NCDB): NOTE: PM - reading DB (record 1.0)
  03/26/13-16: 46:08 (GMT) (t1): NOTE: QLTA_HandleTeb: Connect ports 0
  03/26/13-16: 46:08 (GMT) (t3): NOTE: QLTA_HandleTeb: port 1 link up
  03/26/13-16: 46:09 (GMT) (t2): WARN: QLTA_Handleteb: 72 event Code.
  03/26/13-16: 46:09 (GMT) (t4): WARN: QLTA_Handleteb: 72 event Code.
  03/26/13-16: 46:09 (GMT) (NCDB): NOTE: CCM: sodMirrorCheckIn() waiting alt cache check in mirror...
  03/26/13-16: 46:10 (GMT) (NCDB): WARN: CCM: initMirrorAltChkIn() may not reflect
  03/26/13-16: 46:11 (GMT) (NCDB): NOTE: CCM: initialize(): cache configuration
  03/26/13-16: 46:11 (GMT) (NCDB): NOTE: from UWManager::initialize, 510, the invalid index - 1 entries
  03/26/13-16: 46:11 (GMT) (NCDB): NOTE: NVSRAM IW queue size is 0
  03/26/13-16: 46:16 (GMT) (NCDB): NOTE: RTR: IO released
  03/26/13-16: 46:17 (GMT) (NCDB): NOTE: SOD: initialization Phase complete
  ==============================================
  Title: Disk Array Controller
  Copyright 2005 - 2011 LSI Logic Corporation, all rights reserved.

  Name: RC
  Version: 07.35.39.64
  Date: 16/08/2011
  Time: 14:24:32 CDT
  Models: 1532
  Manager: devmgr.v1035api01.Manager
  ==============================================

  03/26/13-16: 46:17 (GMT) (NCDB): NOTE: sodMain of the sequence is complete, elapsed time = 90 seconds
  03/26/13-16: 46:17 (GMT) (NCDB): NOTE: complete sodMain
  03/26/13-16: 46:17 (GMT) (EventGateManager): WARN: GMOS: 8 events of creation for objects that already exist

  IPs I can ping: 10.182.232.251 and 10.182.233.251 (both on RC1). I can even ping all other iSCSI host initiator ports! I hope I gave enough information about me for some answers. Please advise!

  Thank you.

  What are the 4 IP addresses and subnets for the 4 the MD3000i iSCSI ports?

  ISCSI controller 0 port 0?: (guess 10.182.232.250/24)

  ISCSI 0 1 controller port?: (guess 10.182.233.250/24)

  Controller 1 iSCSI port 0: 10.182.232.251 24 (hypothesis on the mask)

  Port of iSCSI controller 1 1: 10.182.233.251 24 (hypothesis on the mask)

  Wiring must be:

  iSCSI 1 Switch / VLAN:

  ISCSI controller 0 port 0

  ISCSI controller 1 port 0

  Server 1 iSCSI port 0 (in the subnet 10.182.232.x 24)

  etc.

  iSCSI Switch 2 / VLAN:

  ISCSI 0 1 controller port

  ISCSI 1 1 controller port

  Server 1 iSCSI port 0 (in the subnet 10.182.233.x 24)

  etc.

  To test iSCSI on controller 0 port, take a cell phone with a Gbit ethernet port (any modern laptop should have it), connect the ethernet controller iSCSI 0 0, 10.182.232.100 port value IP from the laptop and try to ping 10.182.232.250 (assuming that it comes to the INVESTIGATION period on this port). If it works, change the IP of the laptop to 10.182.233.100 and move the cable to the iSCSI port 1 and try to ping 10.182.233.250 and see if you can ping the IP address.

  If these two are working, the first thing that comes to mind is that the port 0 and 1 have their swapped cables.

• iSCSI initiator error - cannot add target

  I am currently using a MD3000i in a test environment.

  The installation is very simple:

  The MD3000i is directly connected to a Windows Server 2003 (x 64 Enterprise edition).

  The management software is completely installed on this server. Only one controller is used to manage the PowerVault (partially managed)

  All default settings are used. I have configure the system according to the guide online "Board installation and configuring iSCSI" found on the installation CD.

  I get an error when configuring the Mirosoft iSCSI initiator. As soon as I try to add a port for iSCSI (iSCSI initiator properties panel-> discovery-> target portals tab), I get the following error message:

  "invalid sendtargets response text was detected.

  After accepting this error, the port is added to the list, but will not appear in the tab target, it is therefore impossible to connect to this port. The port of host iSCSI on the table and the address source on the server IP responds to ping without problem.

  At this point, I am only able to connect to the MD3000i with the out of band management and cannot access the storage in any way.

  Any help would be greatly appreciated

  Robert

  
  

• How to start the tunnels without the need of ping to a remote host

  That's the big question!

  How can you tunnels without need to ping to a remote host in the target network? Our clients get hung on a regular basis because of this problem. 10 points for the first answer!

  Hello

  You can configure KeepAlive on end VPN.

  For example

  On PIX

  ISAKMP keepalive 2 30

  On IOS

  ISAKMP crypto keepalive 10 periodicals

  If it does not solve that and you need some kind of traffic you can configure NTP on the link VPN (source of the private interface it is so interesting traffic for VPN).

  HTH

  Sangaré

• "PING [ARC2]: Heartbeat cannot connect to standby mode"

  Dear Experts,

  I have n/w connectivity between two servers.  IP is the ping requests.

  But primary alert log datbase shows PING [ARC2]: Heartbeat cannot connect to standby mode '

  This standby alert log database already mounted.

  SYS > select nom_dest, status, type, database_mode, recovery_mode, error, destination, synchronization_status from v$ archive_dest_status where type = 'PHYSICAL ';

  STATUS TYPE ERROR DESTINATION SYNCHRONIZATION_STATUS RECOVERY_MODE DATABASE_MODE NOM_DEST

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

  LOG_ARCHIVE_DEST_2 ERROR PHYSICS FORCE RESCUE IDLE ORA-16058: standby database instance is not mounted stby_crmsdb CHECK the CONFIGURATION

  Heartbeat PING [ARC2]: Unable to connect to the day before "stby_crmsdb". The error is 16058.

  Sam Oct 31 12:20:12 2015

  Errors in the /u01/app/oracle/diag/rdbms/crms/crms/trace/crms_arc2_32417.trc file:

  ORA-16058: standby database instance is not mounted

  Heartbeat PING [ARC2]: Unable to connect to the day before "stby_crmsdb". The error is 16058.

  Sam Oct 31 12:26:16 2015

  Errors in the /u01/app/oracle/diag/rdbms/crms/crms/trace/crms_arc2_32417.trc file:

  ORA-16058: standby database instance is not mounted

  Heartbeat PING [ARC2]: Unable to connect to the day before "stby_crmsdb". The error is 16058.

  Sam Oct 31 12:32:18 2015

  Errors in the /u01/app/oracle/diag/rdbms/crms/crms/trace/crms_arc2_32417.trc file:

  ORA-16058: standby database instance is not mounted

  Heartbeat PING [ARC2]: Unable to connect to the day before "stby_crmsdb". The error is 16058.

  Sam Oct 31 12:37:20 2015

  Errors in the /u01/app/oracle/diag/rdbms/crms/crms/trace/crms_arc2_32417.trc file:

  ORA-16058: standby database instance is not mounted

  Heartbeat PING [ARC2]: Unable to connect to the day before "stby_crmsdb". The error is 16058.

  Sam Oct 31 12:38:31 2015

  > > On standby server I delivered after a command.  Cloning process is running

  $ rman target sys/passwd@CRMSDB auxiliary sys/passwd@STBY_CRMSDB

  ...

  ....

  > > alert_log ensures msgs

  Sam Oct 31 12:07:17 2015

  Connections of RFS were rejected

  change the basis of mountain rescue

  Defined in the converted due to the incompatibility of db_unique_name control file

  Change di2dbun of MRC to stbycrms

  ARK: START OF THE ARCH PROCESS

  Sam Oct 31 12:07:21 2015

  Arc0 started with pid = 22, OS id = 7103

  Arc0: Started archiving

  ARCH: FROM PROCESS ARCH COMPLETE

  ARC0: FROM PROCESS ARCH

  Sam Oct 31 12:07:22 2015

  Mount of redo thread 1, with mount id 1596596917

  Physical Standby Database mounted.

  Lost write protect mode the "typical" value

  ..

  Sam Oct 31 12:07:22 2015

  Arc1 started with pid = 23, OS id = 7105

  Completed: alter database mount standby

  Sam Oct 31 12:07:22 2015

  ARC2 started with pid = 24, OS id = 7107

  Arc1: Started archiving

  ARC2: Started archiving

  Arc1: become the "no FAL' ARCH

  Sam Oct 31 12:07:22 2015

  ARC3 started with pid = 25, OS id = 7109

  ARC2: Become the heartbeat ARCH

  ARC3: Started archiving

  ARC0: FROM PROCESS ARCH COMPLETE

  Sam Oct 31 12:07:24 2015

  Using the default for the STANDBY_ARCHIVE_DEST as USE_DB_RECOVERY_FILE_DEST parameter value

  > On primary and Stanby (output is even only)

  SYS > select thread #, max(sequence#) from v$ archived_log group thread #;

  THREAD # MAX(SEQUENCE#)

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

  1 14452

  Your standby database health seems good and is in phase with the primary. Mistakes "hearbeat failed", you've seen, maybe during the RMAN duplication, Eve could have been returned a couple of times, who would have said these errors in the primary alert log file.

  -Jonathan Rolland

• BEA-000362 &lt; server failed. At least a migratable target is configured with automatic migration. Before the automatic migration of any type can be used, the MigrationBasis must be defined in the ClusterMBean. If the database is selected, then DataSourc

  My Weblogic 12 c StartWeblogic.cmd failed after that I configured the migration of the cluster to the database with the name of the table as none.  I can't even to the Server Admin page.

  Before that, I remove the. log.lck, process.id, process.lck files in the nodemanager directory

  Help, please! Thank you!

  Joe

  ****************************************************************************

  # < October 1, 2015 4:18:20 PM CDT > < Info > < security > < NAP1D692 > <>< Home > <><><>< 1443734300986 > < BEA-090905 > < disable provider JCE CryptoJ self-intégrité for better startup performance. To allow this control, enter - Dweblogic.security.allowCryptoJDefaultJCEVerification = true. >

  # < October 1, 2015 4:18:21 PM CDT > < Info > < security > < NAP1D692 > <>< Home > <><><>< 1443734301049 > < BEA-090906 > < change the default Random Number Generator in RSA CryptoJ of ECDRBG128 to FIPS186PRNG. To disable this change, specify - Dweblogic.security.allowCryptoJDefaultPRNG = true. >

  # < October 1, 2015 4:18:21 PM CDT > < opinion > < WebLogicServer > < NAP1D692 > <>< Home > <><><>< 1443734301064 > < BEA-000395 > < the following extensions added at the end of the classpath directory content:

  C:\oracle\Middleware\Oracle_Home\user_projects\domains\joe12c_domain\lib\log4j-1.2.15.jar; C:\oracle\Middleware\Oracle_Home\user_projects\domains\joe12c_domain\lib\wllog4j.jar. >

  # < October 1, 2015 4:18:21 PM CDT > < Info > < WebLogicServer > < NAP1D692 > <>< Thread-4 > <><><>< 1443734301361 > < BEA-000377 > < since Java hotspot 64-bit Server VM WebLogic Server Version 24.60 - b09 of Oracle Corporation. >

  # < October 1, 2015 4:18:21 PM CDT > < Info > < management > < NAP1D692 > <>< Thread-5 > <><><>< 1443734301610 > < BEA-141107 > < Version: WebLogic Server 12.1.3.0.0 Wed May 21 18:53:34 PDT 2014 1604337 >

  # < October 1, 2015 4:18:22 PM CDT > < opinion > < WebLogicServer > < NAP1D692 > <>< Thread-6 > <><><>< 1443734302702 > < BEA-000365 > < Server State has changed at the START. >

  # < October 1, 2015 4:18:22 PM CDT > < Info > < WorkManager > < NAP1D692 > <>< Thread-6 > <><><>< 1443734302702 > < BEA-002900 > < init > self-adjustable thread pool.

  # < October 1, 2015 4:18:22 PM CDT > < Info > < WorkManager > < NAP1D692 > <>< ExecuteThread [ASSET]: '0' for the queue: "(self-adjusting) weblogic.kernel.Default" > <><><>< 1443734302733 > < BEA-002942 > < CMM level memory becomes 0. Sleep thread pool to 256. >

  # < October 1, 2015 4:18:22 PM CDT > < Info > < WebLogicServer > < NAP1D692 > <>< Thread-6 > <><><>< 1443734302733 > < BEA-000214 > < WebLogic Server "AdminServer" version:

  WebLogic Server 12.1.3.0.0 Wed May 21 18:53:34 PDT 2014 1604337 Copyright (c) 1995,2014, Oracle and/or its affiliates. All rights reserved. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < Protocol 't3' is now configured. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < Protocol "t3s" is now configured. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < the 'http' Protocol is now configured. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < the "https" Protocol is now configured. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < Protocol "iiop" is now configured. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < Protocol 'iiops' is now configured. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < "ldap" Protocol is now configured. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < Protocol "ldaps" is now set up. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < Protocol "cluster" is now configured. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < Protocol 'clusters' is now configured. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < the "SNMP" is now configured. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002622 > < Protocol "admin" is now configured. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-6 > <><><>< 1443734303264 > < BEA-002624 > < administration Protocol is "t3s" and is now configured. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < RJVM > < NAP1D692 > <>< Thread-5 > <><><>< 1443734303264 > < BEA-000570 > < Network Configuration for channel "AdminServer.

  Listening address: 7001

  Address public n/a

  True active http

  Tunneling Enabled false

  Outgoing Enabled false

  Admin traffic enabled true fake license to ResolveDNSName >

  # < October 1, 2015 4:18:23 PM CDT > < Debug > < RJVM > < NAP1D692 > <>< Thread-5 > <><><>< 1443734303264 > < BEA-000571 > < retail network for channel "AdminServer.

  Weight of the channel 50

  Accept the rear 300

  Timeout 5000ms

  Message Max Size 10000000

  Timeout message 60 years

  Timeout of 65

  Tunneling Timeout 40 s

  Tunneling Ping 45 s >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < Server > < NAP1D692 > <>< Thread-5 > <><><>< 1443734303279 > < BEA-002609 > < channel Service initialized. >

  # < October 1, 2015 4:18:23 PM CDT > < opinion > < Log Management > < NAP1D692 > <>< ExecuteThread [pending]: '1' for the queue: "(self-adjusting) weblogic.kernel.Default" > <><><>< 1443734303357 > < BEA-170019 > < C:\oracle\Middleware\Oracle_Home\user_projects\domains\joe12c_domain\servers\AdminServer\logs\AdminServer.log server log file is opened. All events in the log server-side will be written to this file. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < Log Management > < NAP1D692 > <>< ExecuteThread [pending]: '1' for the queue: "(self-adjusting) weblogic.kernel.Default" > <><><>< 1443734303404 > < BEA-170023 > < logging of the server is initialized with the Java application logging API. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < IIOP > < NAP1D692 > <>< [STANDBY] ExecuteThread: '2' for the queue: "(self-adjusting) weblogic.kernel.Default" > <><><>< 1443734303404 > < BEA-002014 > < subsystem enabled IIOP. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < Log Management > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303404 > < BEA-170025 > < initialized Logging area. Events in the field log will be written to C:\oracle\Middleware\Oracle_Home\user_projects\domains\joe12c_domain\servers\AdminServer\logs/joe12c_domain.log. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < Diagnostics > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303451 > < BEA-320001 > < ServerDebug The service initialized successfully. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < Store > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303513 > < BEA-280008 > < open the persistent store of file 'WLS_DIAGNOSTICS' for recovery: directory = C:\oracle\Middleware\Oracle_Home\user_projects\domains\joe12c_domain\servers\AdminServer\data\store\diagnostics requestedWritePolicy = "Disabled" fileLockingEnabled = true driver = "wlfileio3." >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < Store > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303529 > < BEA-280103 > < storage of persistent files "WLS_DIAGNOSTICS" puts in cache in weblogic.store.io.file.direct.FileMapping [granularity = 65536 io mapped =]. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < management > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '2' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303529 > < BEA-141278 > < Java configuration entropy is: property system "java.security.egd = null; File JRE java.security "securerandom.source = file:/dev/urandom" property Blocking of the Config = false; Version of the JDK = 1.7.0_60; Operating system = Windows 7. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < management > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '2' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303545 > < BEA-141280 > < configuration detected NON-BLOCKING of entropy of java. This setting you will give the best performance on machines with limited sources of entropy, but is less secure than a blocking entropy configuration. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < management > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '2' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303545 > < BEA-141187 > < Java System properties are defined as follows:

  awt. Toolkit = sun.awt.windows.WToolkit

  leader. Encoding = Cp1252

  leader. Encoding.pkg = sun.io

  leader. Separator =.

  Java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment

  Java.awt.PrinterJob = sun.awt.windows.WPrinterJob

  Java.class.Path = C:\JDK17~1.0_6\lib\tools.jar; C:\oracle\MIDDLE~1\ORACLE~1\wlserver\server\lib\weblogic_sp.jar; C:\oracle\MIDDLE~1\ORACLE~1\wlserver\server\lib\weblogic.jar; C:\oracle\MIDDLE~1\ORACLE~1\oracle_common\modules\net. SF.antcontrib_1.1.0.0_1-0b3\lib\ant-contrib.jar; C:\oracle\MIDDLE~1\ORACLE~1\wlserver\modules\features\oracle.WLS.common.nodemanager_2.0.0.0.jar; C:\oracle\MIDDLE~1\ORACLE~1\oracle_common\modules\com. Oracle.Cie.config - WLS - online_8.1.0.0.jar; C:\oracle\MIDDLE~1\ORACLE~1\wlserver\common\derby\lib\derbyclient.jar; C:\oracle\MIDDLE~1\ORACLE~1\wlserver\common\derby\lib\derby.jar; C:\oracle\MIDDLE~1\ORACLE~1\wlserver\server\lib\xqrl.jar; C:\oracle\MIDDLE~1\ORACLE~1\wlserver\server\lib\weblogic.jar; C:\Progra~2\IBM\RATION~1\CLEARQ~1\cqjni.jar

  Java.class.version = 51.0

  Java.endorsed.dirs = C:\JDK17~1.0_6\jre\lib\endorsed; C:\oracle\MIDDLE~1\ORACLE~1\oracle_common\modules\endorsed

  Java.ext.dirs = C:\JDK17~1.0_6\jre\lib\ext; C:\Windows\Sun\Java\lib\ext

  Java.Home = C:\JDK17~1.0_6\jre

  Java.IO.TMPDIR =

  Java.Library.Path = C:\JDK17~1.0_6\bin; C:\Windows\Sun\Java\bin; C:\Windows\System32; C:\Windows; C:\oracle\MIDDLE~1\ORACLE~1\wlserver\server\native\win\x64; C:\oracle\MIDDLE~1\ORACLE~1\wlserver\server\bin; C:\oracle\MIDDLE~1\ORACLE~1\oracle_common\modules\org. Apache.ant_1.9.2\bin; C:\JDK17~1.0_6\jre\bin; C:\JDK17~1.0_6\bin; C:\Progra~2\IBM\RATION~1\common; C:\Progra~3\Oracle\Java\javapath; C:\oracle\product\102~1.0\client_1\BIN; C:\Progra~2\BUSINE~1\Common\3.5\bin\NOTES\; C:\Windows\System32; C:\Windows; C:\Windows\System32\wbem; C:\Windows\System32\WINDOW~1\v1.0\; C:\Progra~2\HEAT\;\\nap-lvip-047\scmref\bin; C:\JDK17~1.0_5;\\nap-lvip-047\maven\M3R1SW~N.9\bin; C:\Progra~2\CODECO~1;\\nap-lvip-047\scmref\bin; C:\Windows\System32; C:\Progra~2\IBM\gsk8\lib; C:\Progra~2\IBM\gsk8\bin; C:\Progra~2\IBM\RATION~1\CLEARC~1\Bin; C:\Progra~2\IBM\RATION~1\CLEARC~1\REMOTE~1\cteapis; C:\oracle\MIDDLE~1\ORACLE~1\wlserver\server\native\win\x64\oci920_8;.

  Java.naming.Factory.initial = weblogic.jndi.WLInitialContextFactory

  Java.naming.Factory.URL.pkgs = weblogic.jndi.factories:weblogic.corba.j2ee.naming.url:weblogic.jndi.factories:weblogic.corba.j2ee.naming.url

  Java.Runtime.Name = Java (TM) SE Runtime Environment

  Java.Runtime.version = 1.7.0_60 - b19

  Java.Security.Policy = C:\oracle\MIDDLE~1\ORACLE~1\wlserver\server\lib\weblogic.policy

  Java.Specification.Name = Java Platform API Specification

  Java.Specification.Vendor = Oracle Corporation

  Java.Specification.version = 1.7

  Java.Vendor = Oracle Corporation

  Java.vendor.URL = http://Java.Oracle.com/

  Java.vendor.URL.bug = http://bugreport.Sun.com/bugreport/

  Java.version = 1.7.0_60

  Java.VM.info = mixed mode

  Java.VM.Name = VM Server Java hotspot 64-Bit

  Java.VM.Specification.Name = specification of Machine Java virtual

  Java.VM.Specification.Vendor = Oracle Corporation

  Java.VM.Specification.version = 1.7

  Java.VM.Vendor = Oracle Corporation

  Java.VM.version = 24, 60 - b09

  javax. Management.Builder.initial = weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder

  javax.rmi.CORBA.PortableRemoteObjectClass = weblogic.iiop.PortableRemoteObjectDelegateImpl

  javax.rmi.CORBA.UtilClass = weblogic.iiop.UtilDelegateImpl

  org.omg.CORBA.ORBClass = weblogic.corba.orb.ORB

  org.omg.CORBA.ORBSingletonClass = weblogic.corba.orb.ORB

  OS. Arch = amd64

  OS. Name = Windows 7

  OS.version = 6.1

  Path.Separator =;

  Sun.Arch.Data.Model = 64

  Sun.Boot.class.Path = C:\oracle\MIDDLE~1\ORACLE~1\oracle_common\modules\endorsed\javax-xml-bind.jar; C:\oracle\MIDDLE~1\ORACLE~1\oracle_common\modules\endorsed\javax-XML-WS.jar; C:\oracle\MIDDLE~1\ORACLE~1\oracle_common\modules\endorsed\jsr250-API.jar; C:\JDK17~1.0_6\jre\lib\resources.jar; C:\JDK17~1.0_6\jre\lib\rt.jar; C:\JDK17~1.0_6\jre\lib\sunrsasign.jar; C:\JDK17~1.0_6\jre\lib\jsse.jar; C:\JDK17~1.0_6\jre\lib\jce.jar; C:\JDK17~1.0_6\jre\lib\charsets.jar; C:\JDK17~1.0_6\jre\lib\jfr.jar; C:\JDK17~1.0_6\jre\classes

  Sun.Boot.Library.Path = C:\JDK17~1.0_6\jre\bin

  Sun.CPU.endian = little

  Sun.CPU.isalist = amd64

  Sun.Desktop = windows

  Sun.IO.Unicode.Encoding = UnicodeLittle

  Sun.java.Command = weblogic. Server

  Sun.java.Launcher = SUN_STANDARD

  Sun.JNU.Encoding = Cp1252

  Sun.Management.Compiler = HotSpot 64 bits compilers Tiered

  Sun.OS.patch.Level = Service Pack 1

  User.country = en

  User.dir = C:\oracle\Middleware\Oracle_Home\user_projects\domains\joe12c_domain

  User.Home =

  User.language = en

  User.Name =

  User.TimeZone =

  VDE. Home = C:\oracle\Middleware\Oracle_Home\user_projects\domains\joe12c_domain\servers\AdminServer\data\ldap

  WebLogic. Name = AdminServer

  WebLogic.Home = C:\oracle\MIDDLE~1\ORACLE~1\wlserver\server

  WLS. Home = C:\oracle\MIDDLE~1\ORACLE~1\wlserver\server

  . >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < Store > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303545 > < BEA-280009 > < storing files persistent "WLS_DIAGNOSTICS" (75765a60-c009-403f-a7ed-c6a75a86e1c8) has been opened: blockSize = 512 actualWritePolicy = "Disabled(single-handle-non-direct)" explicitIOEnforced = false files = 25. " >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < XML > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303592 > < BEA-130036 > < XMLRegistry initialization >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < Socket > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '2' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303662 > < BEA-000436 > < allocate 4 player son. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < Socket > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '2' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303662 > < BEA-000446 > < active native to IO. >

  # < October 1, 2015 4:18:23 PM CDT > < Info > < security > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734303849 > < BEA-000000 > < OpenJPA starting 1.1.1 - SNAPSHOT >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < security > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304005 > < BEA-000000 > < StoreServiceImpl.initJDO - StoreService is initialized with Id = ldap_PyMqKeZifftJZ2SHXoWLnh4Ldn4 = >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < security > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304021 > < BEA-090516 > < authenticator provider has already given LDAP. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < security > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304114 > < BEA-090516 > < provider authorized person a pre-existing LDAP data. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < security > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304301 > < BEA-090516 > < CredentialMapper a pre-existing LDAP provider data. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < security > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304317 > < BEA-090516 > < RoleMapper a pre-existing LDAP provider data. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < security > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304379 > < BEA-090093 > < no pre - WLS 8.1 Keystore provider is configured for server security realm myrealm AdminServer. >

  # < October 1, 2015 4:18:24 PM CDT > < opinion > < security > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304379 > < BEA-090082 > < security initialization using security realm myrealm. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < connector > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304457 > < BEA-190000 > < J2EE Connector Service initialization. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < connector > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304457 > < BEA-190001 > < Service connector J2EE initialized successfully. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < Store > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304473 > < BEA-280008 > < opening persistent store file '_WLS_AdminServer' for recovery: directory = C:\oracle\Middleware\Oracle_Home\user_projects\domains\joe12c_domain\servers\AdminServer\data\store\default requestedWritePolicy = fileLockingEnabled 'Direct entry' = true driver = "wlfileio3." >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JMX > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '2' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304504 > < BEA-149512 > < JMX connector server started service: jmx:iiop://10.29.11.182:7001/jndi/weblogic.management.mbeanservers.runtime. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304535 > < BEA-040305 > < JMS service is initialized and standby mode. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304567 > < BEA-040090 > < 8 deployed by default connection factories. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304567 > < BEA-040407 > < connection factory default 'DefaultXAConnectionFactory2' with 'weblogic.jms.XAConnectionFactory2' JNDI name is started >.

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304567 > < BEA-040407 > < connection factory default 'MessageDrivenBeanConnectionFactory' with 'weblogic.jms.MessageDrivenBeanConnectionFactory' JNDI name is started >.

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304567 > < BEA-040407 > < connection factory default 'DefaultConnectionFactory' with 'weblogic.jms.ConnectionFactory' JNDI name is started >.

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304567 > < BEA-040407 > < connection factory default 'TopicConnectionFactory' with his "javax.jms.TopicConnectionFactory" JNDI name is started >.

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304567 > < BEA-040407 > < connection factory default 'DefaultXAConnectionFactory' with 'weblogic.jms.XAConnectionFactory' JNDI name is started >.

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304567 > < BEA-040407 > < connection factory default 'DefaultXAConnectionFactory0' with 'weblogic.jms.XAConnectionFactory0' JNDI name is started >.

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304567 > < BEA-040407 > < default connection factory is started 'Factory' with his "javax.jms.QueueConnectionFactory" JNDI name >.

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304567 > < BEA-040407 > < connection factory default 'DefaultXAConnectionFactory1' with 'weblogic.jms.XAConnectionFactory1' JNDI name is started >.

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304567 > < BEA-040306 > < JMS service is now active. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JMX > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304629 > < BEA-149512 > < JMX connector server started service: jmx:iiop://10.29.11.182:7001/jndi/weblogic.management.mbeanservers.domainruntime. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < Store > < NAP1D692 > < AdminServer > < ExecuteThread [ASSETS]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304676 > < BEA-280009 > < file persistent store "_WLS_AdminServer" (c54c7ab9-2eab-4095-ba3c-5abb38f06231) has been opened: blockSize = 512 actualWritePolicy = "Direct-Write(read-buffered)" explicitIOEnforced = false documents = 21. " >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JMX > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304691 > < BEA-149512 > < JMX connector server started service: jmx:iiop://10.29.11.182:7001/jndi/weblogic.management.mbeanservers.edit. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JDBC > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304769 > < BEA-001135 > < init > the JDBC service.

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JDBC > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304785 > < BEA-001137 > < full initialization >.

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JDBC > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304785 > < BEA-001138 > < Recovery > JDBC service.

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JDBC > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304785 > < BEA-001140 > < complete resume >.

  # < October 1, 2015 4:18:24 PM CDT > < Info > < messaging.interception > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304816 > < BEA-400000 > < initialization message interception service. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < Server > < NAP1D692 > < AdminServer > < ExecuteThread [pending]: '3' for queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304863 > < BEA-002622 > < Protocol "[https, t3, snmp, cluster-broadcast-secure, ldaps, cluster-broadcast, ldap, http, iiop, admin, t3s '. "[, iiops]" is now set up. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < HTTP > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304863 > < BEA-101128 > < HTTP initialization services. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < HTTP > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304894 > < BEA-101135 > < AdminServer is the default Web server. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < HTTP > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304894 > < BEA-101052 > < [HttpServer (defaultWebserver) name: AdminServer] Initialized >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < HTTP > < NAP1D692 > < AdminServer > < [pending] ExecuteThread: '1' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304894 > < BEA-101129 > < init > the container of the Web application.

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JMX > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304972 > < BEA-149513 > < JMX Connector Server stopped serving: jmx:iiop://10.29.11.182:7001/jndi/weblogic.management.mbeanservers.edit. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JDBC > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304988 > < BEA-001144 > < Force suspending the JDBC service. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JDBC > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304988 > < BEA-001146 > < Force suspend completed JDBC service >.

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JDBC > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304988 > < BEA-001147 > < JDBC service stop. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JDBC > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304988 > < BEA-001149 > < stopping the JDBC service performed. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JMX > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304988 > < BEA-149513 > < JMX Connector Server stopped serving: jmx:iiop://10.29.11.182:7001/jndi/weblogic.management.mbeanservers.domainruntime. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < MessagingBridge > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304988 > < BEA-200001 > < messaging bridge has shut down successfully. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304988 > < BEA-040308 > < service JMS suspends >.

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304988 > < BEA-040107 > < 8 cancelled by default connection factories. >

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JMS > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304988 > < BEA-040015 > < stop JMS is done >.

  # < October 1, 2015 4:18:24 PM CDT > < Info > < JMX > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734304988 > < BEA-149513 > < JMX Connector Server stopped serving: jmx:iiop://10.29.11.182:7001/jndi/weblogic.management.mbeanservers.runtime. >

  # < October 1, 2015 4:18:24 PM CDT > < critical > < WebLogicServer > < NAP1D692 > < AdminServer > < principal > < < WLS Kernel > > <><>< 1443734304988 > < BEA-000362 > <Server has failed. Reason: at least a migratable target is configured with automatic migration. Before the automatic migration of any type can be used, the MigrationBasis must be defined in the ClusterMBean. If database is chosen, must be set so DataSourceForAutomaticMigration. >

  # < October 1, 2015 4:18:25 PM CDT > < opinion > < WebLogicServer > < NAP1D692 > < AdminServer > < principal > < < WLS Kernel > > <><>< 1443734305003 > < BEA-000365 > < Server state changed to FAILED. >

  # < October 1, 2015 4:18:25 PM CDT > < error > < WebLogicServer > < NAP1D692 > < AdminServer > < principal > < < WLS Kernel > > <><>< 1443734305003 > < BEA-000383 > < is not an essential service. The server shuts itself down. >

  # < October 1, 2015 4:18:25 PM CDT > < opinion > < WebLogicServer > < NAP1D692 > < AdminServer > < principal > < < WLS Kernel > > <><>< 1443734305003 > < BEA-000365 > < Server state has changed to FORCE_SHUTTING_DOWN. >

  # < October 1, 2015 4:18:25 PM CDT > < Info > < WebLogicServer > < NAP1D692 > < AdminServer > < ExecuteThread [ASSET]: '0' for the queue: '(self-adjusting) weblogic.kernel.Default' > < < WLS Kernel > > <><>< 1443734305003 > < BEA-000236 > < stop run > discussions.

  # < October 1, 2015 4:18:25 PM CDT > < Info > < WebLogicServer > < NAP1D692 > < AdminServer > < principal > < < WLS Kernel > > <><>< 1443734305003 > < BEA-000238 > < judgment made. >

  It may sound crazy that I am answering my own post.  As he complains about MigrationBasis.  I tried to go to the config.xml file and changed

  Cluster-0

  unicast

  database

  TO

  Cluster-0

  unicast

  consensus

  And at least I was able to restart Server Admin and go to the Server Admin page. The Cluster-> Configuration-> Migration is always on view from database as the basis for Migration.

  Joe