ADIN3310BBCZ datasheet(64/86 Pages) AD

64 / 86 page

Data Sheet

ADIN3310/ADIN6310

REDUNDANCY

analog.com

Rev. A | 64 of 86

HSR STATISTICS

The switch captures a number of HSR-related statistics and error

counters associated with each HSR port. The statistics also return

how many nodes are in the network. The following HSR statistics

are captured:

►

Rx Count reflects the number of frames received by Port A or

Port B that have HSR tag added.

►

Tx Count reflects the number of frames transmitted by Port A or

Port B that have HSR tag added.

►

Error Count specifies the number of frames with errors received

on the link redundancy entity (LRE) Port A or Port B.

►

Duplicate Count specifies the number of entries in the duplicate

detection mechanism on Port A or Port B for which one single

duplicate was received.

►

Multi Count specifies the number of entries in the duplicate

detection mechanism on Port A or Port B for which more than

one duplicate was received.

►

Unique Count specifies the number of entries in the duplicate

detection mechanism on Port A or Port B for which no duplicate

was received.

►

Node Count returns the number of nodes detected in the sys-

tem.

Node Table

The switch maintains a node table to track DANHs and SANs in

the HSR network. The node table is populated based on incoming

traffic and HSR supervision frames observed on HSR ports. The

packet assist engine automatically inserts or deletes entries based

on the node table logic. The node table records duplicate discard

or duplicate accept based upon received HSR supervision frames

for a node. This table records the last time a frame was received

from a particular node, and it refreshes the node table every 60

seconds. If no frames have been received after this time, the node

entry is removed. The user can interrogate the node table through

the SES_GetLreNodesEntry() API, which is available as part of

the software drivers on the ADIN6310 product page. The node table

can accommodate 1024 entries maximum.

Proxy Node Table

The proxy node table is a list of the detected SANs that are

connected to the RedBox, and the last time they were seen. The

proxy node table learns the SAN and virtual DANH MAC based on

ingressing traffic on an interlink port. The user can interrogate the

proxy node table using the SES_GetLreProxyNodeEntry() API,

which is available as part of the software drivers on the ADIN6310

product page. Like the node table, the proxy node table keeps its

table refreshed based on incoming frames and ages out entries

after 60 seconds. The maximum size of the proxy node table for

HSR RedBox is 8.

PARALLEL REDUNDANCY PROTOCOL (PRP)

Like HSR, PRP is used in redundant applications to increase

reliability of a communication channel by providing duplicate frames

traveling across separate networks and thus provide lossless com-

munications in the event of a single network failure. PRP places no

extra requirements on the other switches in the network,; however,

it does require usage of a duplicate network.

PRP implements redundancy through the use of doubly attached

nodes obeying PRP (DANP).

Again, only one instance of PRP can be configured in the 6-port

ADIN6310 switch, the selection of ports that are part of the PRP

network is flexible and can be defined by the user during initial

configuration.

A DANP is attached to two independent LANs of similar topology,

named LAN A and LAN B, which operate in parallel. A source

DANP takes the nonPRP frame from a SAN and duplicates the

frame for egress from the two ports connected to LAN A and LAN

B. These frames have a PRP redundancy control trailer (RCT or

PRP tag) attached at the end of the frame. These duplicate frames

are identical, except for the PRP tag (LAN ID) and FCS. A destina-

tion DANP receives the duplicate frames from both LANs, within a

certain time, consumes the first frame to arrive, and discards the

duplicate. The DANP can also remove the PRP tag upon egress.

Figure 48. Simplified PRP Network

Any switches in the LAN path do not care about the PRP tag

because it simply looks like part of the payload. All traffic from a

DANP to a DANP is accomplished with PRP; traffic from a DANP to

a SAN does not require PRP.

The two LANs are identical in protocol at the MAC-LLC level, but

they can differ in performance and topology. Transmission delays

may also be different. The two LANs have no connection between

them and are assumed to be fail independent.

The switch provides a hardware-based approach for PRP aligned

with the IEC standard and supports operation as a DANP where the

hardware manages the duplication of frames, insertion of the PRP

tag, consumption of the first frame, discard of the duplicate frame,

and removal of the PRP tag.

Because the PRP trailer is at the end of the frame, just before the

FCS, PRP operates in store and forward mode in the DANP and

RedBox but switches in the network can be in cut-through mode.

ADIN3310BBCZ bảng dữ liệu(PDF) 64 Page - Analog Devices

ADIN3310BBCZ bảng dữ liệu(HTML) 64 Page - Analog Devices

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86

bảng dữ liệu tải về

Link URL