1 EMAS Part RNC EMAS started towards the RNC 1.1 Manually perform the HealthCheck 1.1.1 Open the HealthCheck view - Select “Equipment” View - Select Equipment=1 in “MO Tree” - Click on “MO Properties” tab . - Select “Actions” tab by clicking on it - Select “startHealthCheck” from “Actions” list
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
1 EMAS PartRNC EMAS started towards the RNC
1.1 Manually perform the HealthCheck
1.1.1 Open the HealthCheck view
- Select “Equipment” View
- Select Equipment=1 in “MO Tree”
- Click on “MO Properties” tab .
- Select “Actions” tab by clicking on it
- Select “startHealthCheck” from “Actions” list
- Click the button “Execute” to perform HealthCheck
1.1.2 HealthCheck Started
From the “Result”, check the HealthCheck is started
1.1.3 View the result of HealthCheck
- Select “Attributes” tab by clicking on it under “MO Properties”
- Expand the attribute “healthCheckResult”
- Check the HealthCheck result
- If the HealthCheck is not ok
- One or all of the below alarms will raise on AL
File System Diagnostic Error
Configuration Version Corrupt
Upgrade Package Corrupt
1.2 Schedule the HealthCheck
1.2.1 Open the schedule view
- Select “Equipment” View
- Select Equipment=1 in “MO Tree” panel on the left side
- Click on “MO Properties” tab on the right side
- Select “Attributes” tab by clicking on it
- Click on “+” under the attribute “healthCheckSchedule”
- Input the time (UTC, Format: hh:mm) and select the weekday (you can select one of them from Monday to Sunday)
- Click on “Apply”, then RNC will automatically perform the HealthCheck on the schedule time
- If the HealthCheck is not ok
- One or all of the below alarms will raise on AL
o File System Diagnostic Error
o Configuration Version Corrupt
o Upgrade Package Corrupt
1.2.2 Add another schedule
- Click on “+” under the attribute “healthCheckSchedule”
- You will add another schedule for HealthCheck
Totally 14 schedules are available
2 AMOS PartOpen AMOS from OSS server
2.1 Manually perform the HealthCheck
- Run “lt root” in AMOS
- Run “acc ManagedElement=1$ startHealthCheck”
- Run “get ManagedElement=1$ healthCheckResult” to check the result
- If the result is not OK, the corresponding alams will raise.
o File System Diagnostic Error
o Configuration Version Corrupt
o Upgrade Package Corrupt
2.2 Schedule the HealthCheck
- Run “set ManagedElement=1$ healthCheckSchedule time=02:00,weekday=1” to set the schedule
- Time format (UTC, Format: hh:mm) and weekday format (you can choose from 1 to 7 )
o 1 SUNDAY
o 2 MONDAY
o 3 TUESDAY
o 4 WEDNESDAY
o 5 THURSDAY
o 6 FRIDAY
o 7 SATURDAY
- To add more schedules, you have to set moreschedules at once with “;”
o E.g. “set ManagedElement=1$ healthCheckSchedule time=02:00,weekday=1; time=03:00,weekday=5”
- To delete all schedules, just run “set ManagedElement=1$ healthCheckSchedule”
- Totally 14 schedules are available
3 Notes:- Normally HealthCheck costs less than 10
minutes for configure F RNC
- Can not make/delete any CV during HealthCheck running
- Can not verify upgrade during HealthCheck running
- Can not upgrade the next software package during HealthCheck running.
4 Reference for alarms:[1] File System Diagnostic Error (134/1543-CRX901 49/1)
[2] Configuration Version Corrupt (133/1543-CRX 901 49/1)