​

Question:
Often, when troubleshooting a schoolview system, you will be asked to provided Telnet logs. Here are instructions for how to gather them. Here are a few recommendations that have the benefit of auto reconnect functions which is invaluable when troubleshooting because much of the bootup information needed by tech support is already gone before you can manually reconnect the software after a reboot. First,  ShadeBlue Indigo Terminal Emulator. This is not freeware or shareware, but you do get a 45 day trial period. Second is an offshoot of Putty called Kitty which adds the auto reconnect function.

Answer:

1. Create a new connection to all Schoolview masters so that you have one instance for every master, running at the same time.
1. Log into each master with the following default username and password. Username: administrator and Password: password. If your site has changed the username or password, obtain those from your administrator.​
   
2. Once logged in, enable debug messaging on each master with the following command.
1. msg on debug
2. Save telnet logs to a file.
1. Set Kitty to log all session output to a file of your own designation for name and location.
1. Click on the Logging tab
2. Under “Session logging" select “All session output"
3. Under “Log file name" choose an appropriate file name for your site. Please include the school name, master being logged, and date the logs were captured, as well as what event you were logging; such as Paging, bells, or system reboot in the filename. (Reference image on next page)
   
   
    
4. Click “Browse" and in the popup, choose a location to save the file.
   
   
3. Clicking “Save" means all logs will then automatically be saved to the filename and location specified once the session is terminated.
4. Set Kitty to auto-reconnect after reboot
1. Click on the “Connection" tab
2. Check the box for “Attempt to reconnect on connection failure (image reference on next page)
   
   
   
    
5. Click Open on the left to start the session.
6. Execute event to be troubleshot. (Paging, Bells, or System Reboot)
7. Once event is complete, close session and provide Tech Support with the log file for review.