Difference between revisions of "HowTo Setup AlphaCom NetworkDisk"
From Zenitel Wiki
(→Preparing the shares for AlphaCom support) |
(→Preparing the NetworkDisk shares) |
||
| Line 59: | Line 59: | ||
Disk sucsessfully mounted on /mnt/mini/log | Disk sucsessfully mounted on /mnt/mini/log | ||
Disk sucsessfully mounted on /mnt/mini/mysql | Disk sucsessfully mounted on /mnt/mini/mysql | ||
| − | + | ||
--------------------------------------------------------- | --------------------------------------------------------- | ||
Free space on shares: | Free space on shares: | ||
| Line 68: | Line 68: | ||
465G 178M 465G 1% /mnt/mini/local | 465G 178M 465G 1% /mnt/mini/local | ||
//10.5.2.165/alphadb 465G 178M 465G 1% /mnt/mini/mysql | //10.5.2.165/alphadb 465G 178M 465G 1% /mnt/mini/mysql | ||
| − | + | ||
--------------------------------------------------------- | --------------------------------------------------------- | ||
Used Space on shares: | Used Space on shares: | ||
| Line 74: | Line 74: | ||
AlphaCom MySQL Database : 21M /mnt/mini/mysql | AlphaCom MySQL Database : 21M /mnt/mini/mysql | ||
AlphaCom NetDisk logging : 0 /mnt/mini/log | AlphaCom NetDisk logging : 0 /mnt/mini/log | ||
| − | + | ||
--------------------------------------------------------- | --------------------------------------------------------- | ||
Testing for a valid Extended Application share | Testing for a valid Extended Application share | ||
| Line 82: | Line 82: | ||
AlphaCom MySQL DB folder found | AlphaCom MySQL DB folder found | ||
Use this script with option 'initdb' to re-initialiaze to an empty DB | Use this script with option 'initdb' to re-initialiaze to an empty DB | ||
| − | + | ||
------------------- END --------------------------------- | ------------------- END --------------------------------- | ||
Revision as of 11:40, 30 March 2008
The following services is supported on NetworkDisk:
- Extended Aphache/PHP/Mysql support
- Mysql Database storage
- Log storage
Contents
The only requirement for the sharing device is that is supports the SAMBA/CIFS protocol, and it has sufficient disk space.
On the sharing device tree separate shares needs to be setup:
| Share Name | Description |
|---|---|
| local | The AlphaCom Extended Application packages. Mounted locally on /usr/local/ |
| mysql | Storage space for the AlphaCom MySQL databases. Mounted locally on /var/mysql/ |
| log | Storage space for AlphaCom system log. Mouned locally on /var/log/ |
Default:
user = ace passswd = alphacom
If other user/passwd is to be used the mounting scripts described below needs to be updated.
Required tools for setting up AlphaCom NetworkDisk
The setup procedure requires some manual steps using a ssh terminal and sftp file transfer.
Recommended tools to use:
SSH terminal: PuTTY (http://www.chiark.greenend.org.uk/~sgtatham/putty/) sftp client: WinSCP (http://winscp.net/eng/index.php)
Open a SSH terminal to the AlphaCom target and su to root (use "su -"):
-bash-3.1$ su -
Password: {root password}
-bash-3.1# ./netdiskprepare.sh mount
------------------- START -------------------------------
Trying to mount netdisk shares
Disk sucsessfully mounted on /mnt/mini/local
Disk sucsessfully mounted on /mnt/mini/log
Disk sucsessfully mounted on /mnt/mini/mysql
---------------------------------------------------------
Free space on shares:
Filesystem Size Used Avail Use% Mounted on
//10.5.2.165/alphalog
465G 178M 465G 1% /mnt/mini/log
//10.5.2.165/alphalocal
465G 178M 465G 1% /mnt/mini/local
//10.5.2.165/alphadb 465G 178M 465G 1% /mnt/mini/mysql
---------------------------------------------------------
Used Space on shares:
AlphaCom Extended Applications : 153M /mnt/mini/local
AlphaCom MySQL Database : 21M /mnt/mini/mysql
AlphaCom NetDisk logging : 0 /mnt/mini/log
---------------------------------------------------------
Testing for a valid Extended Application share
!! No AlphaCom Extended Applications found !!
Use sftp to transfer and install a new packages to this mount
Testing for a valid alphacom MySQL DB (simple test)
AlphaCom MySQL DB folder found
Use this script with option 'initdb' to re-initialiaze to an empty DB
------------------- END ---------------------------------