ExamGecko
Question list
Search
Search

Question 6 - 156-836 discussion

Report
Export

What cannot be a reason for 'Failed to get remote orchestrator interfaces' error message, when clicking on 'Orchestrator' in WebUI

A.
Remote orchestrator has no empty interfaces
Answers
A.
Remote orchestrator has no empty interfaces
B.
Single orchestrator environment, but configured Orchestrator amount is 2
Answers
B.
Single orchestrator environment, but configured Orchestrator amount is 2
C.
One orchestrator only, but Orchestrator amount is 2 or no Sync in between orchestrators
Answers
C.
One orchestrator only, but Orchestrator amount is 2 or no Sync in between orchestrators
D.
No Sync between orchestrators
Answers
D.
No Sync between orchestrators
Suggested answer: A

Explanation:

One of the possible reasons for the ''Failed to get remote orchestrator interfaces'' error message, when clicking on ''Orchestrator'' in WebUI, is that the remote orchestrator has no empty interfaces that can be assigned to a security group. This can happen if all the interfaces on the remote orchestrator are already part of configured security groups, or if the remote orchestrator has no physical interfaces at all. In this case, the WebUI cannot display the unassigned interfaces of the remote orchestrator, and shows the error message.

Reference

* Not able to see unassigned interfaces on checkpoint Orchestrator

* Maestro 140 not detecting Interfaces

* Maestro Expert (CCME) Course - Check Point Software, page

asked 16/09/2024
Jess Kendrick Gamboa
35 questions
User
Your answer:
0 comments
Sorted by

Leave a comment first