Summary: On an OptiX OSN 1500/2500/3500/3500 II/7500 V100R008C02SPH203 that houses active and standby system control boards, the standby system control board periodically performs file patrol and reports version information to the active system control board to synchronize patch files. The two operations conflict occasionally, resulting in patch file synchronization failure and the reporting of the PATCH_ERR alarm. The alarm is automatically cleared after patch file synchronization succeeds in the next period.
Product Line: Transport network product line Product Family: MSTP products
[Problem Description]
Trigger conditions:
The problem occurs when the following conditions are present:
The OptiX OSN 1500/2500/3500/3500 II/7500 runs the V100R008C02SPH203 patch.
The OptiX OSN 1500/2500/3500/3500 II/7500 houses active and standby system control boards, SSQ3CXLN, SSR1CXL, SSR2CXLN, SSN3GSCC, SSN3GSCC-B2, or SSN4GSCC.
Symptom:
The NE reports the PATCH_ERR alarm occasionally and the alarm persists for 10 to 20 minutes.
Identification method:
Run the following commands or query the version number on the NMS to check whether the involved NE is an OptiX OSN 1500/2500/3500/3500 II/7500 V100R008C02SPH203.
Run the following command to check whether the active and standby system control boards run properly.
Check historical alarms and find that the following alarm record or records are displayed and no current PATCH_ERR alarm exists.
[Root Cause]
The OptiX OSN 1500/2500/3500/3500 II/7500 runs the V100R008C02SPH203 patch. The standby system control board reports version information to the patch package on the active system control board every 23 or 60 minutes to request patch file synchronization. This operation occasionally conflicts with periodical file patrol (every 30 minutes by default) performed on the standby system control, causing synchronization.
failure and PATCH_ERR alarms. After the patch file synchronization succeeds in the next period, the alarm is automatically cleared.
[Impact and Risk]
The NE falsely reports the PATCH_ERR alarm occasionally whereas patches on the standby system control board are normal.
[Measures and Solutions]
Preventive measures:
The following three preventive measures are available:
Method 1:
Disable file patrol on the standby system control board. Enable file patrol one hour later. This method decreases the possibility that PATCH_ERR alarms are falsely reported.
Disable file patrol on the standby system control board by running the following command.
SlaveBid indicates the slot ID of the standby system control board.
File patrol is successfully disabled if the following results are queried and the file patrol state is displayed as USERSTOP.
Enable file patrol on the standby system control board one hour later.
File patrol is successfully enabled if the following results are queried and the file patrol state is displayed as START.
----End
Method 2:
Lower the severity of the PATCH_ERR alarm at corresponding sites.
Method 3:
Mask the PATCH_ERR alarm on the NMS at corresponding sites. Enable the alarm after the standby system control board is reseated or replaced.
Recovery measures:
The PATCH_ERR alarm is automatically cleared within 10 to 20 minutes after it is reported.
Solutions:
Upgrade the NE to V100R008C02SPH505 and modifies the file patrol period on the standby system control board to 24 hours.
Upgrade the NE to V100R010C03 which optimizes patch package synchronization and avoids conflicts with file patrol on the system control board.
Material handling after replacement:
N/A
[Inspector Applicable or Not]
N/A
[Rectification Scope and Time Requirements]
N/A
[Rectification Instructions]
N/A
[Attachments]
N/A
Ｍore blog:
No comments:
Post a Comment