Skip to main content

NetApp wins prestigious Coveo Relevance Pinnacle Award. Learn more!

INSIGHT Japan :2023年 1月25日(水)ANAインターコンチネンタルホテル開催 へ参加・申込を行う

NetApp Knowledge Base

UM5 API (XML) fails with 'HTTP POST - failed, status code = 507'

Views:
54
Visibility:
Public
Votes:
0
Category:
oncommand-unified-manager-core-package
Specialty:
om
Last Updated:

Applies to

  • Unified Manager 5.2.5Px (UM5)
  • Operating in 7-mode 
  • Data ONTAP 8.2.5

Issue

UM5 reports communication problems
Errror XML ( http port 80) HTTP POST - failed, status code = 507
In host diag output we see xml failing with XML (http port 80)     Timeout. Could not read API response.
There is also no response when using ZAPI Explorer, means the problem is on the controller
API is failing without time pattern
 
Log
Feb 01 14:51:15 [DFMMonitor:DEBUG]: [3320:0xf078]: [7-mode Controller] (120251): fcp-adapter-list-info failed: HTTP POST - failed, status code = 507
Feb 01 14:51:25 [DFMMonitor:DEBUG]: [3320:0x14ca4]: [7-mode Controller] (120251): system-cli failed: HTTP POST - failed, status code = 507
Feb 01 14:51:25 [DFMMonitor:DEBUG]: [3320:0x14ca4]: [7-mode Controller] (120251): ipspace-list-info failed: HTTP POST - failed, status code = 507
 
and
Jan 28 22:19:56 [DFMMonitor:ERROR]: [3320:0x44c]: dfmon get_volume_list_info: Timeout. Could not read API response., [7-mode Controller]
Jan 28 22:21:10 [DFMMonitor:DEBUG]: [3320:0xe050]: [7-mode Controller] (120251): fcp-adapter-list-info failed: Timeout. Could not read API response.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device