No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Configuration Guide - System Monitor 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Configuration Guide - System Monitor
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Limitations for NQA-NE05E

Limitations for NQA-NE05E

Restrictions

Guidelines

Impact

When the lossy mode and the outward-facing 802,1ag function are both configured for an interface, the outward-facing 802,1ag function fails.

Do not configure the lossy mode and the outward-facing 802,1ag function for the same interface.

When the lossy mode and the outward-facing 802,1ag function are both configured for an interface, the outward-facing 802,1ag function fails.

If the client end supports hardware-based packet sending, the board that sends packets must support 1588v2 clock synchronization.

Select a board that supports 1588v2 clock synchronization for packet sending.

Hardware-based packet sending measurement results obtained during a jitter test are inaccurate.

If a destination IP address is configured for the client end, the outbound interface of a route cannot be any management interface.

Do not deploy any test instance for which the outbound interface of a route is a management interface.

Hardware-based packet sending measurement results obtained during a jitter test are inaccurate.

If the server end supports hardware-based packet reply, the board that replies packets must support 1588v2 clock synchronization.

Select a board that supports 1588v2 clock synchronization for packet reply.

Hardware-based packet sending measurement results obtained during a jitter test are inaccurate.

The MTU of the tested link cannot be less than 64,

Configure the MTU of the tested link to be no less than 64,

Jitter measurement results are inaccurate.

One-way delay measurement requires the deployment of 1588v2 clock synchronization.

To measure one-way delay, deploy 1588v2 clock synchronization.

Hardware-based packet sending measurement results obtained during a jitter test are inaccurate.

The server and client of an ICMP jitter, UDP jitter, or TCP test instance must be VRP-based devices. The test result depends on the board hardware capability.

None

The test fails or is inaccurate.

Only one VXLAN segment can be detected. End-to-end detection is not supported in scenarios where multi VXLAN segments are combined.

None

Only one VXLAN segment can be detected.

If a static route is associated with NQA and the path tested by NQA also depends on the static route, only direct connection is supported.

None

The static route fails to be restored.

In a cross-domain or private L3VPN detection scenario where a P node does not have any return route but supports MPLS forwarding, when the tracert ipv4 command is run to test an MPLS tunnel, the display of cross-domain P node information depends on whether the associated board supports tracert fast reply.

None

When the tracert ipv4 command is run to test an MPLS tunnel in a cross-domain scenario, information about cross-domain P nodes fails to be displayed if the associated board does not support tracert fast reply.

When the tracert lsp command is run to test an LSP , cross-domain P nodes are not supported.

None

After the tracert lsp command is run, timeout is displayed for cross-domain P nodes.

The tracert test skips cross-domain P nodes.

L2VPN PW ping/tracert can test a PW with only one segment, not a PW with multiple segments.

None

L2VPN PW ping/tracert can test a PW with only one segment, not a PW with multiple segments.

When testing VPLS or VLL PWs with tunnel overlapping, L2VPN PW ping/tracert can test only the outer backup plane.

None

When testing VPLS or VLL PWs with tunnel overlapping, L2VPN PW ping/tracert can test only the outer backup plane.

When the ping or tracert detection is delivered through Schema, the number of historical records is limited as follows:

1. A maximum of 128 historical records can be cached.

2. If the number of records exceeds the limit, the earliest historical records are overwritten circularly.

When the ping or tracert detection is delivered through Schema, the number of historical records is limited as follows:

1. A maximum of 128 historical records can be cached.

2. If the number of records exceeds the limit, the earliest historical records are overwritten circularly.

None

P2MP tunnel detection supports single-segment tunnel detection, not E2E detection in multi-segment splicing scenarios.

In multi-segment splicing scenarios, only the first-segment P2MP tunnel starting from the local root node can be detected.

Plan a proper configuration.

None

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058924

Views: 6931

Downloads: 24

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next