This section will guide you through troubleshooting some common LinMin Snapshot Manager scenarios.

 

All command line interactions below assume you are logged is as root.

 

I can't access the LSM GUI

 

•Did you open your browser and enter the IP address of your LSM Server?

 

 

•Did you check to see if the LSM services are running?

 

# sh /home/LinMin/actions/LSM_StatusServices.sh

...

LSM server can access the Network

Action: Status

Active:

Inactive: DHCP/PXE/TFTP NFS HTTP

 

In the example above, the LSM services NOT are running.

Restart the LSM services (after making sure there are no Machines being serviced at that time):

 

# sh /home/LinMin/actions/LSM_RestartServices.sh

...

LSM server can access the Network

Action: Restart

Active: DHCP/PXE/TFTP NFS HTTP

Inactive:

 

 

•Do you get a browser message "Unable to connect"?

 

 

This error may occur after resuming a virtual Machine Snapshot running LSM and under other scenarios where the operating system's network services stopped.

 

To address this issue:

# systemctl restart network

Then click "Try Again" and you should be presented with the LSM GUI.

 

 

 

My Machine can't find the LSM Server upon PXE boot

 

My Machine's console presents the PXE "twirl", then times out and boots to its local storage device:

 

 

 

•Are the LSM services running? You may still have GUI access but the required DHCP/PXE/TFTP services may not be active...

 

# sh /home/LinMin/actions/LSM_StatusServices.sh

...

LSM server can access the Network

Action: Status

Active: NFS HTTP

Inactive: DHCP/PXE/TFTP  

 

In the example above, the LSM services required to service Machines are NOT running even though the User can access the LSM GUI.

 

Restart the LSM services (after making sure there are no Machines being serviced at that time):

# sh /home/LinMin/actions/LSM_RestartServices.sh

...

LSM server can access the Network

Action: Restart

Active: DHCP/PXE/TFTP NFS HTTP

Inactive:

 

•If the LSM services are running, is the Machine on the correct (LSM's) subnet, or if on a different subnet, is your PXE-forwarding done correctly?

oAre other Machines able to PXE boot to the LSM Server?

▪If yes, the Machine not PXE-booting may indeed be misconfigured

▪How is the network configuration/setup different between the Machine that can PXE boot and the Machine that cannot PXE boot?

oReview the Configure > Machine: Netboot Actions settings

▪Recommended setting changes would be to set the default to "Register only" or "Register and get Machine Profile"

•This default action will register any Machine "hitting" (connecting with) the LSM Server

▪If set to "Ignore and Continue booting", you may have missed the LSM splash screen that appears for only a few seconds, and booting to the local storage device is expected behavior:

 

 

 

 

 

 

 

- Errors during imaging events

 

 

 

Search keyword(s): network_issues