ATS: Difference between revisions
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
# try to browse to the ATS: [https://ats1.johncompanies.com https://ats1.johncompanies.com] If you get a response: | # try to browse to the ATS: [https://ats1.johncompanies.com https://ats1.johncompanies.com] If you get a response: | ||
## Navigate to Settings -> Network and click 'Save Settings'. This will trigger the ATS to reboot | ## Navigate to Settings -> Network and click 'Save Settings'. This will trigger the ATS to reboot | ||
# If you get no response: | # If you get no response via browser: | ||
## Go to backup3 | ## Go to backup3. ping the ATS (see [https://secure.johncompanies.com/mgmt/cabinetmap.html https://secure.johncompanies.com/mgmt/cabinetmap.html] for the private IP). If it responds, re-upload the driver and config. On backup3, go to /root/055_files OR /root/047_files , find the dir which contains the config for the ATS in question and ftp 2 driver files and config to ATS: | ||
go to /root/055_files OR /root/047_files | |||
<pre> | <pre> | ||
[root@backup3 ~/047_files]# ftp 10.1.2.71 | [root@backup3 ~/047_files]# ftp 10.1.2.71 | ||
| Line 48: | Line 43: | ||
</pre> | </pre> | ||
after which the ATS will auto-reboot upon ftp disconnect and should come back up ok. | |||
## No response: have DC pull and reseat the ATS card | ## No response: have DC pull and reseat the ATS card | ||
## No response to pull: | ## No response to pull: | ||
### Go to DC. Connect to card via serial cable. In advanced settings instruct to wipe memory then follow ftp instructions to reupload driver and config. | ### Go to DC. Connect to card via serial cable. In advanced settings instruct to wipe memory then follow ftp instructions to reupload driver and config. | ||
Revision as of 15:07, 10 October 2012
Rebooting and Recovering
- confirm the ATS is actually offline. https://secure.johncompanies.com/mgmt/ats.html
- you should see 16 ports listed with green or red icons for each indicating status (green=up, red=down) and the customer # who's on that port. If you see no info, the ATS is down.
- try to browse to the ATS: https://ats1.johncompanies.com If you get a response:
- Navigate to Settings -> Network and click 'Save Settings'. This will trigger the ATS to reboot
- If you get no response via browser:
- Go to backup3. ping the ATS (see https://secure.johncompanies.com/mgmt/cabinetmap.html for the private IP). If it responds, re-upload the driver and config. On backup3, go to /root/055_files OR /root/047_files , find the dir which contains the config for the ATS in question and ftp 2 driver files and config to ATS:
[root@backup3 ~/047_files]# ftp 10.1.2.71 Connected to 10.1.2.71. 220 NET+ARM FTP Server 1.0 ready. Name (10.1.2.71:root): admin 331 User admin OK, send password. Password: 230 Password OK. Remote system type is NET+ARM. ftp> bin 200 Type set to I. ftp> put pwralert.dat local: pwralert.dat remote: pwralert.dat 200 PORT command Ok. 150 About to open data connection. 226 Transfer complete 679080 bytes sent in 0.92 secs (717.1 kB/s) ftp> put rom.bin local: rom.bin remote: rom.bin 200 PORT command Ok. 150 About to open data connection. put ats1paconfig.ini paconfig.ini 226 Transfer complete 2109474 bytes sent in 2.63 secs (782.0 kB/s) ftp> ascii 200 Type set to I. ftp> put ats1.paconfig.ini paconfig.ini local: ats1.paconfig.ini remote: paconfig.ini 200 PORT command Ok. 150 About to open data connection. 226 Transfer complete 4174 bytes sent in 0.02 secs (213.9 kB/s) ftp> bye 221 Goodbye.
after which the ATS will auto-reboot upon ftp disconnect and should come back up ok.
- No response: have DC pull and reseat the ATS card
- No response to pull:
- Go to DC. Connect to card via serial cable. In advanced settings instruct to wipe memory then follow ftp instructions to reupload driver and config.