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

eSight V300R009C00 Single-Node System Software Installation Guide (SUSE Linux) 09

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).
Network Bandwidth Requirements

Network Bandwidth Requirements

To ensure the normal running of the eSight system, ensure that network bandwidths meet the basic network bandwidth requirements.

Table 2-2 Network bandwidth requirements

Item

Bandwidth Requirements

Bandwidth between the eSight server and devices

Total bandwidth between eSight and devices = Device management bandwidth + Additional bandwidth for terminal upgrade + Additional bandwidth for network traffic + Additional bandwidth for deploying the operating system for servers

  • Device management bandwidth (X indicates the total number of devices, including terminals and other box devices):
    • X < 2000, required bandwidth: 2 Mbit/s
    • X > 2000, required bandwidth: 2 Mbit/s + (X – 2000) x 0.8 kbit/s
  • Additional bandwidth for terminal (IP phones and CPEs) upgrade (Y indicates the number of terminals):

    (Y/10) x 256 kbit/s

    NOTE:

    The planned bandwidth for each terminal upgrade is 256 kbit/s. In the formula, Y/10 indicates that 10% terminals are concurrently upgraded. eSight allows users to upgrade 100 terminals at the same time, requiring 25.6 Mbit/s.

  • Additional bandwidth for network traffic:

    N x 400 bit/s

    NOTE:
    • In the formula, N indicates the number of flows and its unit is flow/s.
    • The bandwidth for a flow is calculated as follows: (1500/30) x 8 bit/s = 400 bit/s. Here, 1500 indicates that the average size of a NetStream packet is 1500 bytes, and 30 indicates that a NetStream packet has about 30 flows.
    • Reference: The number of flows varies according to the service. In a scenario where a bandwidth of 50 Gbit/s is required for monitoring, a bandwidth of 3.8 Mbit/s to 10 Mbit/s is required for 10,000 to 30,000 flows (sampling ratio: 1000:1).
  • Additional bandwidth for deploying the operating system for servers:

    15 Mbit/s

    NOTE:

    eSight allows users to load and deploy the operating system image through ServiceCD. Deploying the operating system for each server requires 1.5 Mbit/s. eSight allows users to deploy the operating system for a maximum of 10 servers at the same time, requiring 15 Mbit/s.

Bandwidth between the eSight server and web clients

Total bandwidth between the eSight server and clients = Bandwidth between the eSight server and a single eSight client x Number of eSight clients

The bandwidth between the eSight server and a single eSight client must be at least 2 Mbit/s, and 10 Mbit/s or above is recommended.

NOTE:

eSight requires that the network delay is no more than 3 milliseconds and packet loss no more than 0.1% on normal networks.

Bandwidth between the eSight server and OSS

100 Mbit/s or above

Bandwidth between the eSight upper-layer server and lower-layer server

10 Mbit/s or above

Bandwidth between active and standby servers in the HA system

50 Mbit/s or above

NOTE:

Network between the active and standby servers in the HA system: delay < 60 ms, packet loss < 0.1%

Download
Updated: 2019-05-17

Document ID: EDOC1100011860

Views: 92517

Downloads: 138

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