Hard Disk full BCM200 4.0

[SS67]

Anyone know how to clear up disk space on a BCM 200 with about 15 users on it? Voice Mail reports indicate the disk is not being used by messages. I am wondeing if CDR has fill up the disk.

 

[Hewcrew5]

This is instructions for removing files from the e: drive. If you have CDR active and saving to the hard drive, it will definitely fill up.

Unable to Load a Patch Due to Insufficient Space on Drive E of the BCM


• Initiate a telnet session to the BCM
o From a command prompt on a computer that is on the same network as the BCM type telnet followed by the IP of the BCM. If the IP was 10.10.11.1 it would look like the following – telnet 10.10.11.1 - and press enter.
o Type the login for the BCM and press enter
o Type the password for the BCM and press enter
o You are now at the main menu

• Navigate directory structure and delete unnecessary log files
o Select option 7 for Command Line
o Type E: and press enter
o Type cd nortel networks and press enter
o Type dir and press enter to see a list of the directories
o Type cd logs and press enter
o Type dir/p and press enter to see a list of the directories one page at a time
o You can delete the contents of any one of these directories, start with MTT logs
o Type cd MTT logs and press enter
o Type del *.* and press enter they y to confirm and press enter
o This will empty the contents of the folder, re-attempt to install the patch to see if this cleared enough space. If not try deleting another directory. Another one to try is the voice solution directory.

 

[SS67]

This works for a BCM 4.0 Linux system??? I realize I left that part out in my original question.

 

[pkellow]

No it does not. This might help (this was an old solution for root full), at least you can use this to determine which partition (for linux) is full...

solution 5653538
/ root partition is full causing 11201 alarms and patches to fail
________________________________________
Problem Description
The / root partition is 97% full. The system shows alarm 11201 - file system /is at or near or its capacity. As a result, you cannot apply new patches.
Problem Resolution
Perform the following steps:

1. Retrieve a full set of logs from BCM to your PC and rename logs as <appropriate_name>.tar.

2. Use a third party utility (e.g. winzip) to extract the logs.

3. Use a third party utility to extract systemInformation.tar.gz.

4. Open \tmp folder.

5. Double click to open "df.txt" (e.g. using notepad) - this will indicate the filestore usage.

6. Double click to open "DirectoryContents.txt".

7. Within the "DirectoryContents.txt" file, select Edit, select Find, Find What "plltest_gbg". Look for /tmp/pll/gbgX, each of which is 1MB in size.

For example:
334851 994 -rw-r--r-- 1 root root 1017450 Jan 1 2007 /tmp/pll/gbg1/plltest_gbg1_20
334856 994 -rw-r--r-- 1 root root 1017450 Jan 1 2007 /tmp/pll/gbg1/plltest_gbg1_21
334858 994 -rw-r--r-- 1 root root 1017450 Jan 1 2007 /tmp/pll/gbg1/plltest_gbg1_22
334860 994 -rw-r--r-- 1 root root 1017450 Jan 1 2007 /tmp/pll/gbg1/plltest_gbg1_23
334863 994 -rw-r--r-- 1 root root 1017450 Jan 1 2007 /tmp/pll/gbg1/plltest_gbg1_24
334867 994 -rw-r--r-- 1 root root 1017450 Jan 1 2007 /tmp/pll/gbg1/plltest_gbg1_25

These files perform no useful function, and should not be there. There is a test tool called PLLTest that was developed by BCM development purely for the purposes of stress-testing the BCM. It will grab all the CPU cycles it can, and it will fill the HD to capacity. It could potentially cause the above files. The test tool is not a part of the GA software image, so it is not known how these files exist - this problem is seen in extremely rare circumstances.

To resolve, do one of the following:

1. Putty into BCM and log in with account nnsupport, using the appropriate password. Delete these files:

rm -rf /tmp/pll/*

or

2. Connect to the BCM using winscp and log in with account nnsupport, using the appropriate password. Delete these files from the right hand pane (assuming Norton Commander style interface).

General Advice on resolving space problems:

When investigating low freespace on the 4.0 hard disk, there are a handful of things to look for:
- Early versions of callpilotdesktopmessaging and callpilotdesktopmessagingijsg were wrapped with too many languages, and were each about 40MB larger than they should have been. This can be fixed by applying a later version of the Desktop Smart Update (004 and later).
- CallHistory* log files can grow quickly. The known cause is having configured IVR data but lacking an IVR keycode. Apply patch: BCM.R400.201-CTI-1.8-1.0 or later version.
- this PLLTest problem, observed very rarely.

Also, we have seen the /var/log partition filling up on some occasions, do to uncontrolled logging, or (old problem) log files being managed by more than one technique - DiaLogger and Syslog/Logrotate. Apply patch BCM.R400.080-SCD or later.

Refer to solutions database for other current possible fixes (e.g. solution 6719939 , 668237, 7365320, others).

 

[SS67]

Thats is the exact problem I am having with the alarm. Got to be honest and say I have never used putty on the 4.0 so I don't have the password. Is that something you can help me with offline?

 

[DBrewsky]

Putty requires a "password of the day" which is generated by Avaya Support. It is based upon the MSCID (system ID) and the date. They use an algorithm that is pretty secure. Hell, wish I had that generator, I would never need manufacturer support again.

--DB

http://support.csctech.us

Remote Support Specialist

 

[SS67]

I knew it required the password of the day. Was hoping someone other than Avaya/Nortel had the generator. I absolutely dread calling tech support these days. As a business partner they should treat us better than they do.

Thanks to all for the valuable infomation as usual

 

[pkellow]

Although putty access is required, you can still pull the Directorycontents.txt file and this may give you an indication of what is using the space.