EM13c: Exadata Cell targets, PDUs and Ethernet Switch shows down with this message error: em_error=ping response failed for IP address
(Doc ID 2360796.1)
Last updated on SEPTEMBER 27, 2021
Applies to:
Enterprise Manager for Exadata - Version 12.1.0.6.0 to 13.2.2.0.0 [Release 12.1 to 13c]Information in this document applies to any platform.
Symptoms
After bouncing the Exadata Machines, Cell storage servers , PDU's and Ethernet shows as down.
2018-02-12 14:12:47,079 INFO - Finished dynamic properties computation (total time 95 ms). Number of DP computed: 3. Number of DP with error: 1. Number of dynamic properties that were added: 2. Dynamic properties with changed value: [VersionCategory]. Dynamic properties that were loaded from the cache: []. Timeout=false
2018-02-12 14:12:47,086 INFO - Skipping scheduling upload of target dynamic properties as there was no change
2018-02-12 14:12:47,118 INFO - Initialize collections for target
2018-02-12 14:12:49,323 INFO - Ensuring collections for target started: startedCollections=15
2018-02-12 14:13:01,269 INFO - The target is being marked as in DOWN state
2018-02-12 14:13:01,269 INFO - The target is being marked as in DOWN state
2018-02-12 16:46:30,795 INFO - The target IS_MASTER status is being set to false (counter=0)
2018-02-12 16:46:30,812 INFO - Unschedule collections for target (exemptResponse=false, numOfCancelledCollections=15)
2018-02-12 16:46:30,817 INFO - Initialize collections for target
2018-02-12 16:46:30,818 INFO - Scheduling collections for target: 15
2018-02-12 16:46:31,826 INFO - Reschedule collections for target: Unscheduled=15, Scheduled=15
2018-02-12 16:46:33,541 INFO - Starting computation of the target dynamic properties
2018-02-12 16:46:33,602 INFO - Dynamic property execution error for [GetVersion], error: em_error=ping response failed for IP address xx.xx.xx.xx:
2018-02-12 14:12:47,086 INFO - Skipping scheduling upload of target dynamic properties as there was no change
2018-02-12 14:12:47,118 INFO - Initialize collections for target
2018-02-12 14:12:49,323 INFO - Ensuring collections for target started: startedCollections=15
2018-02-12 14:13:01,269 INFO - The target is being marked as in DOWN state
2018-02-12 14:13:01,269 INFO - The target is being marked as in DOWN state
2018-02-12 16:46:30,795 INFO - The target IS_MASTER status is being set to false (counter=0)
2018-02-12 16:46:30,812 INFO - Unschedule collections for target (exemptResponse=false, numOfCancelledCollections=15)
2018-02-12 16:46:30,817 INFO - Initialize collections for target
2018-02-12 16:46:30,818 INFO - Scheduling collections for target: 15
2018-02-12 16:46:31,826 INFO - Reschedule collections for target: Unscheduled=15, Scheduled=15
2018-02-12 16:46:33,541 INFO - Starting computation of the target dynamic properties
2018-02-12 16:46:33,602 INFO - Dynamic property execution error for [GetVersion], error: em_error=ping response failed for IP address xx.xx.xx.xx:
emagent_perl.trc
osresp.pl: 2018-02-11 05:11:04,795: WARN: getent failed for 10.100.0.192; status=2
oracle_exadata_response.pl: 2018-02-11 05:11:21,656: WARN: getent failed for xx.xx.xx.xx; status=2
NodeStatusCheck.pl: 2018-02-12 13:52:56,136: WARN: getent failed for xx.xx.xx.xx; status=2
NodeStatusCheck.pl: 2018-02-12 13:53:13,009: WARN: getent failed for xx.xx.xx.xx; status=2
osresp.pl: 2018-02-11 05:11:04,795: WARN: getent failed for 10.100.0.192; status=2
oracle_exadata_response.pl: 2018-02-11 05:11:21,656: WARN: getent failed for xx.xx.xx.xx; status=2
NodeStatusCheck.pl: 2018-02-12 13:52:56,136: WARN: getent failed for xx.xx.xx.xx; status=2
NodeStatusCheck.pl: 2018-02-12 13:53:13,009: WARN: getent failed for xx.xx.xx.xx; status=2
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |