Professional Documents
Culture Documents
Nodeb MML Alarm Ver
Nodeb MML Alarm Ver
2)
3)
4)
5)
6)
7)
8)
9)
10)
11)
12)
PING - PING............................................................................................................................8
13)
14)
15)
- LST SOFTWARE
Use this command to list the information of NE software and patch, including version
number and whether it is available and active. The running version is circle in red as
shown below.
10)
Use this command to display the status of IP Path. IP paths are used for user plane
connection between RNC and NodeB.
12)
PING - PING
You can use PING to check the network connections and the network quality. The
system sends a PING request to the destination. If the connection to the destination
network is good, the host computer of the destination responses to the source host
computer upon receiving the PING request. The output of PING is the PING response
from the destination. If no response is received within the limit, the output is "Request
time out". Otherwise it outputs the message size in bytes, message number, TTL, and
response time. The final statistics include the number of sent messages, number of
received messages, percentage of the non-response messages, and the minimum,
maximum and average response time.
13)
Use this command to reset board. User need to specify subrack number and slot
number.
Note: Reset board may cause service interruption. Resetting WMPT board may cause
the NodeB to reset. To reset NodeB, use command RST NodeB
14)
Use this command to list data of all the remote OM channels. If there is no OM
channel configured yet, the return value is null. User can check the configured M2000
server IP address, as shown by figure below.
15)
User can query the configured routes on NodeB by using this command.
2)
1) Run command LST ALDPWRSW to make sure all power supply ports A are
turned on and B are off.
2) Reset RRU / WRFU by command RST BRD.
Note: Reset board will affect services for few minutes.
1) Refer to BCO.
Action:
1) Check whether there are other alarms associated with the link. Handle those
alarms accordingly.
2) If alarm still cannot be solved, refer to OMC
Action:
1) Query NTP server IP address with LST SNTPCLTPARA. Make sure it is
correct and valid. Run command SET SNTPCLTPARA to change the IP
address if the parameters are wrong.
2) If alarm still exists, refer to OMC.
Refer to BCO.
1) Refer to BCO.
Refer to OMC.
1) Refer to BCO.
1) Refer to BCO.
1) Refer to BCO.