The authorized user may engage in three conversations through two command-line interfaces. Conversations with the first two entities are common. Conversations of the third kind are infrequent and typically undertaken by NSX Advanced Load Balancer Customer Support personnel for troubleshooting purposes.

In conversation

Your commands address

With this frequency

1

NSX Advanced Load Balancer Controller's Linux OS using Bash

Frequently Used

2

NSX Advanced Load Balancer processes running on Controller using the NSX Advanced Load Balancer shell

Frequently Used

3

The SE’s Linux operating system

Rarely

Accessing NSX Advanced Load Balancer Controller using Linux Shell

  • Access the NSX Advanced Load Balancer Controller’s OS through the bash Linux CLI.

  • Either SSH (Secure Shell) to the Controller or access it through the console from an orchestrator such as vCenter.

  • Example: If the Controller’s address is 10.144.130.195, type the ssh command: ssh admin@10.144.130.195, and when prompted, supply the password for the admin user.

NSX Advanced Load Balancer Controller CLI is used to analyze various logs in the /opt/avi/log and /var/log/upstart directories.

Accessing NSX Advanced Load Balancer Controller using NSX Advanced Load Balancer Shell

  • Start with conversation 1.

  • To enter NSX Advanced Load Balancer-specific commands, type the shell command and furnish credentials.

  • For example: show virtualservice <name-of-virtual-service>

Accessing NSX Advanced Load Balancer Controller using NSX Advanced Load Balancer Service Engines

  • SSH to an NSX Advanced Load Balancer SE or execute the attached service engine <name-of-service-engine> command from the NSX Advanced Load Balancer shell to enter the SE’s Linux CLI.

  • Use it to look into SE-specific logs in various directories, such as /opt/avi/log.

Shell prompt access is not available for NSX Advanced Load Balancer Service Engines. NSX Advanced Load Balancer SE’s Linux CLI does not provide the option to run show commands.

For more information, see CLI Guide.