Refer to the exhibit.
How do improperly set Telnet/SSH parameters effect the configuration of a controller with Cisco
WCS?
A.
The CLI and GUI management of the controller both fail because Cisco WCS checks these
credentials before opening a session.
B.
The Telnet/SSH username must have sufficient privileges to execute commands in CLI
templates.
C.
The GUI management of the controller fails because the Cisco WCS uses the Telnet/SSH
parameters to login to the controller.
D.
The controller remains configured in the Cisco WCS, but no management is possible through
GUI from other client browsers.
Enter the Telnet credentials information for the controller. If you chose the File option and added
multiple controllers, the information will apply to all specified controllers. If you added controllers
from a CSV file, the username and password information is obtained from the CSV file.
Note: The Telnet/SSH username must have sufficient privileges to execute commands in CLI
templates.
0
0
sufficient – privileg
0
0
telnet ssh
0
0
MUST
0
0
Privilege
0
0