O&M information reporting
This section describes the configuration model for O&M information reporting, and provides examples of configured XML packets.
Data Model
The configuration model file matching O&M information reporting is huawei-sea.yang. The configuration model file for reporting logs of a module to the NMS is huawei-log-control.yang.
Object |
Description |
Value |
Remarks |
|---|---|---|---|
/huawei-sea:sea/sea-enable |
Indicates whether to enable the SEA function for users and applications and enter the SEA view. |
The value is of the Boolean type:
|
Ensure that eMDI is enabled before enabling the SEA function. |
/huawei-sea:sea/monitor-type-audio |
Indicates whether to set the type of media streams to be monitored to audio. |
The value is of the Boolean type:
|
N/A |
/huawei-sea:sea/monitor-type-video |
Indicates whether to set the type of media streams to be monitored to video. |
The value is of the Boolean type:
|
N/A |
/huawei-sea:sea/monitor-period |
Indicates the monitoring period of media streams. |
The value is of the enumerated type:
The default value is second-10s. |
N/A |
Object |
Description |
Value |
Remarks |
|---|---|---|---|
/huawei-log-control:log-control/module-list/module |
Specifies a module ID. |
The value is a string of 1 to 32 characters. |
N/A |
Configuring a Switch to Report Video Data to iMaster NCE-CampusInsight
Before configuring this function, use the huawei-system-performance.yang file or run the server ip-address ip-address [ port port-number ] command in the SMI view to configure the switch to interconnect with iMaster NCE-CampusInsight.
Operation |
XPATH |
|---|---|
edit-config:config |
/huawei-sea:sea/sea-enable /huawei-sea:sea/monitor-type-video /huawei-sea:sea/monitor-period |
Data Requirement 1
Item |
Data |
Description |
|---|---|---|
Whether to enable the SEA function |
true |
Enable the SEA function and display the SEA view. |
Type of media streams to be monitored |
true |
Set the type of media streams to be monitored to video. |
Monitoring period of media streams |
second-60s |
Set the monitoring period of media streams to 60 seconds. |
Request Example
<?xml version='1.0' encoding='UTF-8'?>
<rpc message-id="0" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config>
<sea:sea xmlns:sea="urn:huawei:yang:huawei-sea">
<sea:enabled>true</sea:enabled>
<sea:monitor-type-video>true</sea:monitor-type-video>
<sea:monitor-period>second-60s</sea:monitor-period>
</sea:sea>
</config>
</edit-config>
</rpc>
Response Example
# Sample of successful response.
<?xml version='1.0' encoding='UTF-8'?> <rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="0"> <ok/> </rpc-reply>
# Sample of failed response.
<?xml version='1.0' encoding='UTF-8'?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="0">
<rpc-error>
<error-type>application</error-type>
<error-tag>operation-failed</error-tag>
<error-severity>error</error-severity>
<error-path>/</error-path>
<error-message>parse rpc config error.(Unknown element "interfaces".).</error-message>
</rpc-error>
</rpc-reply>
Data Requirement 2
Item |
Data |
Description |
|---|---|---|
Whether to enable the SEA function |
true |
Delete the SEA configuration. |
Type of media streams to be monitored |
true |
Delete the configured type of media streams (video) to be monitored. |
Monitoring period of media streams |
second-60s |
Delete the configured monitoring period (60s) of media streams. |
Deletion Example
<?xml version='1.0' encoding='UTF-8'?>
<rpc message-id="3" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config>
<sea:sea xmlns:sea="urn:huawei:yang:huawei-sea" xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0" xc:operation="delete">
<sea:enabled>true</sea:enabled>
<sea:monitor-type-video>true</sea:monitor-type-video>
<sea:monitor-period>second-60s</sea:monitor-period>
</sea:sea>
</config>
</edit-config>
</rpc>
Response Example
# Sample of successful response.
<?xml version='1.0' encoding='UTF-8'?> <rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="2"> <ok/> </rpc-reply>
# Sample of failed response.
<?xml version='1.0' encoding='UTF-8'?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="2">
<rpc-error>
<error-type>application</error-type>
<error-tag>operation-failed</error-tag>
<error-severity>error</error-severity>
<error-path>/</error-path>
<error-message>parse rpc config error.(Unknown element "interfaces".).</error-message>
</rpc-error>
</rpc-reply>
Reporting Logs of a Module to the NMS
This section provides a sample of reporting logs of a module to the NMS using the edit-config method.
Operation |
XPATH |
|---|---|
edit-config:replace |
/huawei-log-control:log-control/module-list/module |
Data Requirement
Item |
Data |
Description |
|---|---|---|
Module ID |
ff4f0000 |
Set the ID of the module whose logs need to be reported to the NMS. |
Request Example
<?xml version="1.0" encoding="UTF-8"?>
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="15">
<edit-config>
<target>
<running />
</target>
<config>
<log-control xmlns:ns0="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns="urn:huawei:yang:huawei-log-control" ns0:operation="replace">
<module-list>
<module>ff4f0000</module>
</module-list>
</log-control>
</config>
</edit-config>
</rpc>
Response Example
# Sample of successful response.
<?xml version="1.0" encoding="UTF-8"?> <rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="15"> <ok /> </rpc-reply>
# Sample of failed response.
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="15">
<rpc-error>
<error-type>application</error-type>
<error-tag>operation-failed</error-tag>
<error-severity>error</error-severity>
<error-path>/huawei-log-control:log-control/module-list[module='ff4f0000000000000000000000000000000000000000']/module</error-path>
<error-message>parse rpc config error. (Value "ff4f0000000000000000000000000000000000000000" does not satisfy the constraint "1..32" (range, length, or pattern).).</error-message>
</rpc-error>
</rpc-reply>