Got it

ECC Network Division Principle

Latest reply: Nov 5, 2018 01:34:27 1924 15 12 0 1

Hello, everyone!

The HW ECC solution establishes ECC routes using the shortest path first algorithm. "Shortest path" means that the path contains the least number of NEs compared with other paths. It does not mean that the physical reach is the shortest. The following describes how an NE establishes an ECC route:


a.  The physical layer of the NE maintains the status information for the DCC channel corresponding to a line port.

b.  The MAC layer of the NE establishes the MAC connections leading to the adjacent NEs.

  • The NE periodically broadcasts the connection request frame (MAC_REQ) to the adjacent NEs.

  • When receiving the MAC_REQ frame, the adjacent NEs send back a response frame (MAC_RSP).

  • The NE establishes the MAC connection between itself and either adjacent NE when receiving the MAC_RSP frame within the specified time.

c.  The network layer of the NE creates its network-layer routing table.

  • The NE creates an initial network-layer routing table based on the established MAC connections.

  • The NE periodically broadcasts its routing table to the adjacent NEs through the routing response message.

  • When receiving the routing response message, the adjacent NEs update their own network-layer routing tables based on the shortest path policy.

At the next routing broadcast time point, the NE broadcasts the current network-layer routing table.

ECC Network Division Principle

ECC Network Division Solution:

a.  The suggested scale of an ECC subnet is within 50 NEs and the maximum scale is 100 NEs.   

b.  If the NEs on an ECC network exceed 50, it is suggested that gateways be added to divide the network into multiple subnets.

c.  DCC channels are prohibited between ECC subnets.

d.  When an ECC network is divided, an external DCN must be planned.

e.  The ECC route protection function cannot be affected in the ECC network division.

Principle for the Extended ECC Plan:

a.  The NE supporting the extended ECC feature is used and IP addresses must be in the same network segment.

b.  A loop is not allowed when an extended ECC network is formed using hubs and serial ports of NEs.

c.  When a hub is used in the extended ECC networking, it cannot be connected to other devices.

d.  The NEs (including servers and clients) on an extended ECC network cannot exceed eight; otherwise, the NEs will be reset. If the scale is no more than four, the ECC can be extended automatically. If the scale is more than four, the ECC must be extended manually.  

e.  Extending ECC manually is recommended, because the manual mode can reduce negotiations between NEs, and fewer resources are occupied.

f.  When connected to the NMS using a hub, the gateway NE cannot automatically extend the ECC.

g.  When the ECC is extended manually, the NE near to the NMS is recommended as the server for TCP connections and other NEs as clients. The port number ranges from 1601 to 1699.

That's all, thanks!

The HW ECC solution establishes ECC routes using the shortest path first algorithm. "Shortest path" means that the path contains the least number of NEs compared with other paths. It does not mean that the physical reach is the shortest.

sorry can I ask a question about this, can you explain more about the details about ECC ?  what is the usage about this ?ECC Network Division Principle-2787331-1
This post was last edited by Torrent at 2018-10-31 06:21.
View more
  • x
  • convention:

Thanks for your sharing ,which is a wonderful guidance, i really interested in this article, which is useful for us and improvement product technology and become to a professional engineer .
I hope that you can insist post new kownlege and skills, i will alawys keep an eye on your sharing.
View more
  • x
  • convention:

very helpful for:
The suggested scale of an ECC subnet is within 50 NEs and the maximum scale is 100 NEs. b. If the NEs on an ECC network exceed 50, it is suggested that gateways be added to divide the network into multiple subnets.


c. DCC channels are prohibited between ECC subnets.


d. When an ECC network is divided, an external DCN must be planned.


e. The ECC route protection function cannot be affected in the ECC network division.
View more
  • x
  • convention:

Thanks for you share about this which is very useful for my daily work.
And now i can easy to check the ISSUE if i face any issue about this.before this i aways do not know how to deal with them,and wasted a lot of time to serch this.Thanks agin for you selfless Sharing, Hope you can aways work like this.:):):)
View more
  • x
  • convention:

a.   The suggested scale of an ECC subnet is within 50 NEs and the maximum scale is 100 NEs.   b.    If the NEs on an ECC network exceed 50, it is suggested that gateways be added to divide the network into multiple subnets.

  c.    DCC channels are prohibited between ECC subnets.

  d.    When an ECC network is divided, an external DCN must be planned.

 

can you explain more about ECC and DCC ?

This post was last edited by Finn92 at 2018-10-31 08:57.
View more
  • x
  • convention:

Thanks for your sharing , about this part , it help me to solve one live issue .
The NEs (including servers and clients) on an extended ECC network cannot exceed eight; otherwise, the NEs will be reset. If the scale is no more than four, the ECC can be extended automatically. If the scale is more than four, the ECC must be extended manually.
View more
  • x
  • convention:

facing one issue with N2510 and configure using the ECC mode , now I can understand the details about the ECC mode .

This post was last edited by GongXiaochuan at 2018-10-30 06:41.
View more
  • x
  • convention:

Regarding the ECC Network Division Principle, I think this is a key to the suggested scale of an ECC subnet is within 50 NEs and the maximum scale is 100 NEs. b. If the NEs on an ECC network exceed 50, it is suggested that gateways Be added to divide the network into multiple subnets. Through this we can understand this problem very well. This post was last edited by Mark.hu at 2018-10-31 05:47.
View more
  • x
  • convention:

Simplified configuration and management: You can log in to a stack from any member switch to manage and configure all the member switches. After switches set up a stack, complicated Layer 2 loop-prevention protocols (such as MSTP) or Layer 3 protection switching protocols (such as VRRP) do not need to be configured, simplifying the network configuration. This post was last edited by littlestone at 2018-10-31 05:40.
View more
  • x
  • convention:

12
Back to list

Comment

You need to log in to comment to the post Login | Register
Comment

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " User Agreement."

My Followers

Login and enjoy all the member benefits

Login

Block
Are you sure to block this user?
Users on your blacklist cannot comment on your post,cannot mention you, cannot send you private messages.
Reminder
Please bind your phone number to obtain invitation bonus.