Troubleshooting Login Issues

Administration Portal IP Address Is Not Reachable

Problem

Solution

1. Check the CSO Administration Portal IP address reachability from your local machine, where you access the user interface (UI).
   [user-host:~]user% ping 192.0.2.1
2. Check the status of the CSO central microservices virtual machine.

   Log in to the server that is hosting the central microservices virtual machine. The URL is https://central-ms-vm-IP-Address. Log in as root at the shell prompt, and run the virsh list --all command.

   root@host:~# virsh list --all

   Check the status of all the virtual machines.

3. Log in to central microservices virtual machine using SSHv2. This is a prerequisite before starting the installation.

   • If you can log in using SSHv2 , then the /etc/network/interfaces is correct.

   • If you cannot log in to the CSO server hosting central microservices virtual machine, then execute the following commands:

     # virsh console centralmsvm

     # check file /etc/network/interfaces

     Check the gateway and try to ping the gateway from the virtual machine. If the gateway is correct and if you can ping the gateway, then the issue must be due to the lab switch.

4. Check the routes and firewall policies with the help of Network Administrator.
5. For further troubleshooting, collect the logs and output results and contact Juniper Networks Technical Support team.

Administration Portal User Interface Is Not Reachable

Problem

Solution

Check whether the firewall in the path is blocking port 443. Also, check whether the CSO Administration Portal performance-optimized data center (POD) and other PODs are running. You can check the PODs in the Icinga or in CSO central microservices virtual machine.

• To check whether the firewall in the path is blocking port 443:

  user@host-csp-build:~$ telnet 192.213.10.54 443

• To verify the POD status in Icinga:

  1. Log in to http://central-ms-vm-IP-Address:1947/icingaweb2.
  2. Enter the user name icinga and the password that is generated during CSO installation.
  3. Select Infrastructure > CSP Microservices > Central_Services > Central MS IP.

     The PODs are displayed along with their running status.

  4. Verify whether the Administration Portal POD status is running (indicated by green).

1. Log in to the CSO central microservices virtual machine, and execute the following command:
   root@centralmsvm:~# kubectl get pods –n central | grep admin-portal

   Verify whether the Administration Portal POD and the service is in running state, which is indicated by 1/1. In some cases, where the microservices are clubbed together in a POD, the running status is indicated by 2/2, or 3/3.

2. Execute kubectl get pods to get the status of all POD running in the central microservices virtual machine. For example:
   root@centralmsvm:~# kubectl get pods –n central
   root@centralmsvm:~# kubectl get pods –n central | grep admin-portal
3. Check if any other POD is not in running state or if the ready state is 0/1 instead of 1/1. Then check the corresponding POD log by executing the kubectl logs -f pod-name command.
   root@centralmsvm:~# kubectl logs -f csp.admin-portal-ui-2886357385-brtjg –n central
4. For further troubleshooting, collect the logs and output results and contact Juniper Networks Technical Support team.