Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 
New Member

IBM x330 file missing ibmspc

Just installed callmanager 3.1 on IBMx330 box, the OS is looking for the above mentioned file (ibmspc) .

I have found 2 seperate versions of this file on the ibm cd that came with the server and browsed and installed the driver.If I look under winnt/system32/drivers I can see it though I dont know exactly what this file relates to a search of the registry suggests the scsi controller could have something to do with it.

There is also a problem with DC directory the service says starting but never starts the netstat command diplays nothing listening on port 102

Has anyone seen these issues with CM and x330 servers

after the install of all software it asks if you would like to reboot I said know as a windows installer package dc directory was still installing

this hung like this for more than 1/2 an hour.

This was the second time I have seen this behaviour ie the second install.

How i installed

1)put in the first disk that detects hardware

2)then prompted me for disk 3 with the x330 image

I put in the appropriate keys paswds etc

so 98% of the install works fine just the dc directory takes an eternity and doesnt appear to be doing anything under task manager.

Why does the it say setup is finished would u like to reboot if the windows package installer is still doing the dc directory bit ?

Any info on the ibmspc file would be good as well thanks.

Cisco Employee

Re: IBM x330 file missing ibmspc

You should talk to Cisco TAC about this. I know that there have been DC Directory problems relating to installation and they may be able to give you some pointers on that. As far as the ibmspc file they may be able to tell you something about that as well.

New Member

Re: IBM x330 file missing ibmspc

I did the guy was a good bloke but didnt have any info regarding the directory issue. See suggested fix below for the file missing

There is no fan failor on our box and Ibm site has nothing pertaining to the issue.

I would be suggesting that this is a cisco image problem.If you no of issues what are they ?

Dave the guy from the tac said the only issues he could see related to passwd and username ie :Directory Manager ciscicisco


- The ASMA (Advanced Systems Management Adapter) erroneously reports single fan failures.

- These false fan failures are written to the ASMA Event Log upon each instance.

- If the Automatic Dial-out Function of the ASMA is configured to dial-out to a pager or another Netfinity system in the

event of a fan failure, the false fan failures will be interpreted as real fan failures resulting in the Dial-out

function to be executed and send the alert.


All of the following must be true for this tip to apply:

- The system is a PC Server 325 Type 8639 model PT0, PBW, PB0, RB0 that is properly configured with a ASMA (Advanced

Systems Management Adapter) Option p/n94G7578 (FRU p/n12J4743) or Option p/n94G5570 (FRU p/n76H3234).

- The system is configured with any supported version of NT Server, OS/2, or NetWare.

- System diagnostics pass.

- The system experiences the described Symptoms when all cooling fans are functioning.

- The Advanced Management Adapter is presently at a RAM microcode level* 12 or below.

* The RAM microcode level may be viewed from the "Configuration Information" section of the "Netfinity Service

Processor" Utility located in Netfinity Manager (details may be found in step 4 under the FIX section of this document).


1- Prior to going onsite, download the "Advanced Systems Management Adapter Configuration Update Utility and Driver

Diskette ver 2.3" or higher from the IBM Website at the following URL:

- Select "Search"

- Type "Management Adapter 2.3" in the Keywords box

- Select the "Advanced Systems Management Adapter Configuration Update Utility and Driver Diskette ver 2.3" to download.

The file is a self-extracting executable file that creates a diskette.

2- Update the ASMA RAM Microcode in one of the following ways:

Local Update(At the Server)*************************************

1. Boot to the Advanced Systems Management Adapter Configuration Update Utility and Driver Diskette ver 2.3 or higher.

2. Select the 3rd option "Update Service Processor" then press .

3. Follow instructions on the screen, when complete press to exit. Be sure to cycle power OFF, then ON after


to ensure changes will take effect.

Remote Update(Dialed-in to the ASMA from another computer)*****

Refer to page 38 of "Service Processor Manager for Netfinity User's Guide" to execute the following 4 steps.

1. On the machine that used to dial into the Server, copy the $80C5102.BIN from the Advanced Systems Management Adapter

Configuration Update Utility and Driver Diskette ver 2.3 or higher to the NetWare directory.

2. Dial into the ASMA adapter and establish connection.

3. If the server to be updated is up and running, access the "System Power Control" and select "Power off with O/S

shutdown" (the system has to be OFF to apply the update).

4. Access "Configuration Information" and click on "Update Ram Microcode", follow the on-screen instructions.

Note: Completion of the Microcode Update will result in a disconnect of the remote connection to the server requiring

that a remote connection is re-established to remotely Power Up the Server.


It is recommended that the ASMA drivers are updated after upgrading the ASMA RAM Microcode (the ASMA Driver update may

be done locally or remotely).

Local Update (at the Server):

For NT:

1. Open a MS-DOS Prompt.

2. Rename the existing driver and .DLL by typing the following:

rename c:\winnt\system32\ibmspw.dll

rename c:\winnt\system32\drivers\ibmspw.sys ibmspw.bbb

3. Insert the "Advanced Systems Management Adapter Configuration Update Utility and Driver Diskette ver 2.3 or higher

into the Floppy Drive (A drive).

4. Install the new drivers by typing the following:

copy a:\nt\ibmspw.dll c:\winnt\system32\

copy a:\nt\ibmspw.sys c:\winnt\system32\drivers\

5. Shutdown and Restart the System.

6. Cleanup by deleting the and ibmspw.bbb that were created in step 2.

CreatePlease to create content