Keywords

Browse Relevant Trails, disk array card cache, battery

Version Mapping

NMS	OS	Database	NE
-	-	-	-

Symptom

After a user opens the SDH Service Configuration window in the NE Explorer and right-clicks a cross-connection, the Relevant Discrete Service item is displayed in the shortcut menu. In practice, most cross-connections are occupied by trails. It takes a long time (may be more than 30 seconds) to display the Browse Relevant Trails item in the shortcut menu.

The association relationship between cross-connections and trails is not updated yet. The number of cross-connections that are not occupied by trails is consistent with the total number of cross-connections. At that moment, the shortcut menus of all cross-connections display only the Relevant Discrete Service item.

 

After a while, you can see that the number of cross-connections that are not occupied by trails becomes less. At that moment, the association relationship between cross-connections and trails has been updated. The shortcut menus of all cross-connections that are associated with trails display the Browse Relevant Trails item.

 

Problem Identification

The battery of the disk array card of the server runs out and therefore the normal read and write configurations are not retained. You need to replace the battery and set the read and write configurations again.

Cause Analysis

In normal conditions, the association relationship between cross-connections and trails can be queried within several seconds even if many cross-connections exist. On the live network, it takes at least 90 seconds to finish the query, which is appropriate.

The live-network logs show that the time required exceeds the normal value.

[14:53:01.549],Debug,[T13980],default temptable: TNTempTblKey Create temp table:  create table temp_keyNml_sdh6 (  cKey       int not null  )  !

[14:56:31.673],Error,[T13980],ErrorCode: 0x00000000, E2E sql: GetMoString_db17: SELECT t11631526.cID, t11631526.cName FROM tSDHTrail  t11631526 WHERE t11631526.cID IN  ( select cKey from temp_keyNml_sdh6 )

[14:56:35.921],Debug,[T13980],timelog efficiency analysis: Get TNSDH_TRAILMGR::OnGetNameInfo used time(ms):214439

This operation involves data insertion into the temporary database table. The scheduling operation is automatically performed by the database. In normal conditions, the operation consumes a short time.

In practice, a long time is consumed. The unique cause is that the write efficiency of the server deteriorates significantly.

Instruct frontline engineers to check whether the battery of the server disk array card cache runs out and whether the current write configurations are set properly.

Frontline engineers give feedback that the battery runs out and the write configurations are not set properly.

Solution

Replace the battery and ensure that Array Accelerator (Cache) Ratio (read and write configurations) in the Array Configuration Utility dialog box is set to 50%Read/50%Write.

Suggestions and Summary

None