Topic On Terminal System of Switch: Huawei Technologies Co, LTD
Topic On Terminal System of Switch: Huawei Technologies Co, LTD
Topic On Terminal System of Switch: Huawei Technologies Co, LTD
Revision Records
Date Revised version Description Author
Contents
Keyword:
Terminal System, DAO, MCP, FTP, BAM
Summary:
This document collect some frequent asked questions on terminal system of overseas switch.
They are: ‘Set BAM Automatically Logging’, ‘Set NT Log Space’, ‘Set Virtual Memory of BAM’, ‘Set
Virtual Memory of SQL Server on BAM’, ‘Changing BAM server’s name’, ‘How to modify
connection number of SQL Server7’, ‘DAO Installation on Win2000’, ‘C805MCP Installation on
Win2000’, ‘Database Operation Errors after BAM Upgrade’, ‘Perfmon Process Exceptional on
Win2000’, ‘Cautions on Installing the FTP Service’, ‘Interruptions between WS and BAM’,
‘Dataman process of 128BAM Running Abnormally’.
Abbreviation list:
Reference list:
Set User and password correctly, select Automatic login, and Click OK.
Restart BAM to check whether BAM can automatically logging or not.
Set Maximum Size as 256, click Set, and set Maximum Registry Size as 64. After
setting, click OK.
System will prompt to restart computer, restart it.
Click SQL Server Group, click server name, here is PPS (Windows NT), right-click
mouse to select Properties.
Select page Memory, Select Use a Fixed Size Memory (MB), move Scroll Bar to half
position of max size, here is 64MB. It should be not less than 40 percent of max size.
System will not install SQL Server or any components, but only refresh setting of SQL
Server about BAM computer name.
After system refresh, click Finish to restart BAM.
After restarting BAM, run C&C08 Switch Alarm Panel to configure office information,
then it should be OK to run C&C08 client and maintenance.
Click SQL Server Group, click server name, here is Y25124 (Windows NT), right-click
mouse to select Properties.
Select page Connections, Set Maximum concurrent user connections.
见附件:《Msconfig》
Unload the current MCP card as shown in the above figure. The system will prompt
you to restart the computer. After the computer restarts, the system will prompt that a
new piece of hardware is discovered, follow the installation guide to install the MCP
card. When it comes to the step of searching for the driver, select the installation
directory of the BAM server—D:\cc08\services\mcp (default installation directory)
where the driver is saved. Follow the installation guide to complete the installation.
Cause of the problem: At the final step of BAM installation, the system will prompt you
to determine whether to restart the system right away or not. In most cases, the
system is allowed to restart immediately to update and activate the corresponding
services. After the Windows restarts, BAM will automatically restart. At this time, the
value of tbl_Log_Identity is null. MML will automatically insert a value 0 as the initial
record. The database is then upgraded. During the upgrade, the tbl_Log and
tbl_Log_Identity data of the old database will be upgraded to the new one. BAM can
then be normally restarted.
After the upgrade, the identity value in MML is still 0. If you start using the database
immediately after the upgrade (using the MML command), the first log record will use
0 as its identity and the first tbl_Log_Identity to change via the trigger will also be 0,
resulting in a data inconsistency between tbl_Log and tbl_Log_Identity. This trouble
will persist even after BAM restarts,
Because the latest identity value in the database is updated to MML through the
trigger mechanism rather than MML submits a query to the database each time it
needs to assign a new identity.
Solution 1: If it is necessary to update the database, do not restart the system at the
final step of the BAM installation, but start upgrading the data immediately. After the
upgrade, restart the system manually.
Solution 2: After the data upgrade, restart the BAM right away without running any
MML command. This is to ensure that no MML commands are run at any terminal
before the BAM restarts.
If the problem already exists after the Bam upgrade, launch SQL Analyze, select the
BAM database and run the following commands to shoot the trouble.
use Bam
declare @iDenty int
select @iDenty= max(iIdenty) from tbl_Log
update tbl_Log_Identity set iIdentity = @iDenty where tbl_Log_Identity.iFlag = 2
Solution: Open the 128BAM.INI file, change the statement Start=2 under
system\perfmon to Start=3, that is, change the start mode to manual start. And then
all the things left to do are to stop the process manually in Bam Manager.
If not or if it is started but then stopped after some time, the WINNT system may have
been infected by some virus. If this is the case, the recommended solution is to
re-install the WINNT server.
The case with the overseas office has been proved to be the result of abnormal RPC
behavior caused by virus infection. And the final solution is to reinstall the Windows
NT system. Similar problems have also occurred with domestic offices.
If the RPC service is running normally, and therefore, is not the cause of the problem,
proceed with the next step for troubleshooting:
z Has the pack provided by Microsoft against the Worm.Blaster virus been
installed on the server? Overseas Fiexed Network TSD has once issued a
technical notice, addressing specially the installation of this pack . Please follow
the Operation Guide to install the pack.
Note:
If the server is already infected by the virus, the installation of the anti-virus pack will take no effects. The
only way to shoot the trouble is as described in Step 1).
Verify if the system is indeed infected by virus. Overseas Fixed Network TSD has
once issued a technical notice, addressing specially the way to perform virus check.
Please follow the Operation Guide to perform the check.
Caution: Never try to kill the virus blindly by directly running a piece of anti-virus
software, for this may damage the NT/C&C08 system.
Please send back alarm database to [email protected] for further
analysis.