爱立信CUDB日常维护指令

1.1

登陆操作

CUDB

节点中有三类板卡，

分别是

GEP3

板，

SCXB(DMX)

板和

NWI-E

板。

我们需要登录这些板子收集相应的日志，可以用

SecureCRT

，

terminal

者其他

SSH

客户软件 登录这些板卡。

有两种方式可以登陆到

CUDB

：

1

）

C

onsole

直连

Console

直连的方式在日常操作维护中不推荐使用。通过

Console

直连的

操作一般为对于硬件的操作，如更换板 卡。

CUDB

系统

< br>Console

连接配置表。

硬件名称

SCXB

波特率

115200

数据位

8

奇偶校验

None

停止位

1

流控

None

GEP3

NWI-E

115200

9600

8

8

None

None

1

1

None

None

2

）

通

过网管网络连接

CUDB

。

在对于

CUDB

的日常操作维护时，推 荐通过网管网络连接

从

OSS

登陆

SC

板卡和

DMX

板卡使用

SSH

协议，

登陆

使用

TELNET

协议。

CUDB

系统网管登陆信息表

登陆节点

CUDB GEP3

DMX

NWI

登陆方式

端口

SSH

SSH

Telnet

用户名

密码

rootroot

expert

登陆命令

ssh

root

22

root

2024

expert

23

admin

ssh expert@ -p 2024

telnet

1.2

CUDB

系统检查

通常情况下以下检查应该包括在每日健康检查中。

1.2.1

CUDB

总体系统检查

验证整个系统状态。在

CUDB

某块

SC

板卡上执行这些指令。

执行指令

:

# cudbSystemStatus

命令描述

:

这条命令自动执行下面的系统状态检查。

预期结果

:

Execution date: Tue Mar 25 11:29:36 CST 2014

CUDB Software Version:

!- CUDB DESIGN DISTRIBUTION: CUDB13B CXP9020214/6 R1K

Checking BC clusters:

[Site 1]

SM leader: Node 1 OAM2

Node 10.173.0.2

BC server in SC_2_1 ......... running

BC server in SC_2_2 ......... running (Leader)

BC server in PL_2_5 ......... running

[Site 2]

NoLeader

Node 10.173.0.34

BC server in SC_2_1 ......... running

BC server in SC_2_2 ......... running

BC server in PL_2_5 ......... running

Checking System Monitor BC status in local node:

SM-BC in OAM1 ......... running

SM-BC in OAM2 ......... running

Checking Clusters status:

Node 1:

PL Cluster (2%) ..............................OK

DSG1 Cluster (1%) ............................OK

DSG2 Cluster (1%) ............................OK

DSG3 Cluster (1%) ............................OK

DSG4 Cluster (1%) ............................OK

DSG5 Cluster (1%) ............................OK

DSG6 Cluster (1%) ............................OK

DSG7 Cluster (1%) ............................OK

DSG8 Cluster (1%) ............................OK

DSG9 Cluster (1%) ............................OK

DSG10 Cluster (1%) ...........................OK

DSG11 Cluster (1%) ...........................OK

DSG12 Cluster (1%) ...........................OK

DSG13 Cluster (1%) ...........................OK

Node 2:

PL Cluster (2%) ..............................OK

DSG1 Cluster (1%) ............................OK

DSG2 Cluster (1%) ............................OK

DSG3 Cluster (1%) ............................OK

DSG4 Cluster (1%) ............................OK

DSG5 Cluster (1%) ............................OK

DSG6 Cluster (1%) ............................OK

DSG7 Cluster (1%) ............................OK

DSG8 Cluster (1%) ............................OK

DSG9 Cluster (1%) ............................OK

DSG10 Cluster (1%) ...........................OK

DSG11 Cluster (1%) ...........................OK

DSG12 Cluster (1%) ...........................OK

DSG13 Cluster (1%) ...........................OK

Checking NDB status:

PL NDB's (6/6) ...............................OK

DS1 NDB's (2/2) ..............................OK

DS2 NDB's (2/2) ..............................OK

DS3 NDB's (2/2) ..............................OK

DS4 NDB's (2/2) ..............................OK

DS5 NDB's (2/2) ..............................OK

DS6 NDB's (2/2) ..............................OK

DS7 NDB's (2/2) ..............................OK

DS8 NDB's (2/2) ..............................OK

DS9 NDB's (2/2) ..............................OK

DS10 NDB's (2/2) .............................OK

DS11 NDB's (2/2) .............................OK

DS12 NDB's (2/2) .............................OK

DS13 NDB's (2/2) .............................OK

Checking Replication Channels in the System:

Node

|

1

|

2

====================

PLDB ___|__M__|__S1_

DSG 1 __|__M__|__S1_

DSG 2 __|__M__|__S2_

DSG 3 __|__M__|__S1_

DSG 4 __|__M__|__S1_

DSG 5 __|__M__|__S2_

DSG 6 __|__M__|__S2_

DSG 7 __|__M__|__S1_

DSG 8 __|__M__|__S2_

DSG 9 __|__M__|__S1_

DSG 10 _|__M__|__S2_

DSG 11 _|__M__|__S2_

DSG 12 _|__M__|__S1_

DSG 13 _|__M__|__S2_

Printing Alarms...

[Mar 23 12:50:05]( Preventive Maintenance

Logchecker has found major error(s). )

Checking MySQL server connection:

MySQL Master Servers connection ..............OK

MySQL Slave Servers connection ...............OK

MySQL Access Servers connection ..............OK

Checking Process:

OAMs..................

Cluster Supervisor............................Running

System Monitor BC.............................Running

Reconciliation process........................Running in: OAM2

Smp- client....................................Running

Management Server Process (ndb_mgmd)..........Running

KeepAlive process.............................Running

ESA...................................... .....Running

LDAP counter..................................Running

Log Handler process...........................Running

< br>PLs............................................ ....

Storage Engine process (ndbd).................Running

LDAP FE.......................................Running

KeepAlive process.............................Running

MySQL server process (Master).................Running

MySQL server process (Slave)..................Running

MySQL server process (Access).................Running

CudbNotifications process.....................Running

LDAP FE Monitor process.......................Running

D Ss................................................ .................................................. .................................................. .....

.............................

Storage Engine process (ndbd).................Running

LDAP FE.......................................Running

KeepAlive process.............................Running

MySQL server process (Master).................Running

MySQL server process (Slave)..................Running

MySQL server process (Access).................Running

LDAP FE Monitor process.......................Running

1.2.2

HA

状态检查

在

CUDB Active OAM

板卡上验证所有

GEP3

板加入到

cl uster

中。

执行指令

:

#cudbHaState

预期结果

:

LOTC cluster uptime:

--------------------

Thu Mar 27 18:13:44 2014

LOTC cluster state:

-------------------

Node safNode=SC_2_1 joined cluster | Thu Mar 27 18:13:44 2014

Node safNode=SC_2_2 joined cluster | Thu Mar 27 18:14:23 2014

Node safNode=PL_2_3 joined cluster | Thu Mar 27 18:15:21 2014

Node safNode=PL_2_4 joined cluster | Thu Mar 27 18:15:25 2014

…..

AMF cluster state:

------------------

saAmfNode AdminState.

saAmfNodeOperState.

saAmfNodeAdminState.

saAmfNodeOperStat e.

saAmfNodeAdminState.

saAmfN odeOperState.

……

CoreMW HA state:

----------------

CoreMW is assigned as ACTIVE in controller SC-1

CoreMW is assigned as STANDBY in controller SC-2

COM state:

----------

COM is assigned as ACTIVE in controller SC-1

COM is assigned as STANDBY in controller SC-2

SI HA state:

------------

saAmfSISUHAState.

=2N-1

< br>saAmfSISUHAState.

1

saAmfSI SUHAState.

active(1)

saAmfSISUHAState.

active(1)

saAmfSISUHAState.

active(1)

saAmfSISUHAState.

active(1)

saAmfSISUHAState.

active(1)

saAmfSISUHAState.

active(1)

saAmfSISUHAState.

active(1)

saAmfSISUHAState.

active(1) < /p>

saAmfSISUHAState.

…..

SU States:

----------

Status OK

1.2.3

CMW

状态查询

在某块

SC

板卡上输出所有

CUD B servers (OAM, PL and DS)

的磁盘使用

率。

执行指令

:

# cmw-status app csiass comp node sg si siass su pm

命令描述

:

检查

CMW

状态。

1.2.4

检查磁盘使用率

在某块

SC

板卡上输出所有

CUDB servers (OAM, PL and DS)

的磁盘使用

率。

执行指令

:

for a in `awk '/^node/ { print $$4 }' /cluster/etc/`;do

echo $$a; ssh $$a df -h;

done;

命令描述

:

检查磁盘使用率。