User manual

SM User Manual January 2004
Software Release 4.1
Procedure 5: Auto-updating SMs
To upgrade SMs to a later release, the operator performs the following steps:
1. FTP the file SMboot.bin, FPGA, and the action list to AP, as shown in Figure 24.
< ls
062403_D40.jbc APASboot.bin BH10boot.bin
SMboot.bin
41actionlist.txt APboot.bin BH20boot.bin
> ftp 172.16.1.1
Connected to 172.16.1.1.
220 FTP server ready
Name (172.16.1.1:user):
331 Guest login ok
Password:
230 Guest login ok, access restrictions apply.
Remote system type is Type:.
ftp> binary
200 Type set to I.
ftp> put SMboot.bin
local: SMboot.bin remote: SMboot.bin
500 'EPSV': command not understood.
227 Entering Passive Mode (172,16,1,1,4,1)
150 Opening BINARY mode data connection for SMboot.bin
100% |*************************************| 712 KB 229.55
KB/s 00:00 ETA
226 Transfer complete.
729668 bytes sent in 00:03 (209.57 KB/s)
ftp> put 062403_D40.jbc
local: 062403_D40.jbc remote: 062403_D40.jbc
227 Entering Passive Mode (172,16,1,1,4,2)
150 Opening BINARY mode data connection for 062403_D40.jbc
100% |*************************************| 156 KB 219.48
KB/s 00:00 ETA
226 Transfer complete.
159859 bytes sent in 00:00 (156.18 KB/s)
ftp> put 41actionlist
local: 41actionlist remote: 41actionlist
ftp: local: 41actionlist: No such file or directory
ftp> put 41actionlist.txt
local: 41actionlist.txt remote: 41actionlist.txt
227 Entering Passive Mode (172,16,1,1,4,3)
150 Opening BINARY mode data connection for 41actionlist.txt
100% |*************************************| 53 58.81
KB/s 00:00 ETA
226 Transfer complete.
53 bytes sent in 00:00 (0.25 KB/s)
ftp> exit
221 Goodbye.
Figure 24: FTP to AP for SM auto-update
2. Update the SMs in a telnet session to the AP, as shown in Figure 25.
Issue 5 Page 57 of 119