BS EN IEC 61158-4-2:2023
$215.11
Industrial communication networks. Fieldbus specifications – Data-link layer protocol specification. Type 2 elements
Published By | Publication Date | Number of Pages |
BSI | 2023 | 408 |
IEC 61158-4-2:2023 is one of a series produced to facilitate the interconnection of automation system components. It is related to other standards in the set as defined by the “three-layer” fieldbus reference model described in IEC 61158‑1. The data-link protocol provides the data-link service by making use of the services available from the physical layer. The primary aim of this document is to provide a set of rules for communication expressed in terms of the procedures to be carried out by peer data-link entities (DLEs) at the time of communication. These rules for communication are intended to provide a sound basis for development in order to serve a variety of purposes: – as a guide for implementers and designers; – for use in the testing and procurement of equipment; – as part of an agreement for the admittance of systems into the open systems environment; – as a refinement to the understanding of time-critical communications within OSI.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | undefined |
5 | Annex ZA (normative)Normative references to international publicationswith their corresponding European publications |
8 | Blank Page |
9 | CONTENTS |
23 | FOREWORD |
25 | INTRODUCTION |
26 | 1 Scope 1.1 General 1.2 Specifications 1.3 Procedures |
27 | 1.4 Applicability 1.5 Conformance 2 Normative references |
29 | 3 Terms, definitions, symbols, abbreviated terms and conventions 3.1 Reference model terms and definitions |
31 | 3.2 Service convention terms and definitions 3.3 Common terms and definitions |
32 | 3.4 Additional Type 2 definitions |
40 | 3.5 Type 2 symbols and abbreviated terms |
41 | 3.6 Conventions for station management objects Tables Table 1 – Format of attribute tables |
42 | 4 Overview of the data-link protocol 4.1 General 4.1.1 DLL architecture |
43 | Figures Figure 1 – Data-link layer internal architecture Table 2 – Data-link layer components |
44 | 4.1.2 Access control machine (ACM) and scheduling support functions 4.1.3 Connection-mode, connectionless-mode data transfer and DL service 4.2 Services provided by the DL 4.2.1 Overview |
45 | 4.2.2 QoS 4.3 Structure and definition of DLaddresses 4.3.1 General |
46 | 4.3.2 MAC ID address Figure 2 – Relationships of DLSAPs, DLSAPaddresses, and group DLaddresses Figure 3 – Basic structure of a MAC ID address |
47 | 4.3.3 Generic tag address 4.3.4 Fixed tag address Figure 4 – Basic structure of a generic tag address Figure 5 – Basic structure of a fixed tag address Table 3 – MAC ID addresses allocation Table 4 – Fixed tag service definitions |
48 | 4.4 Services assumed from the PhL 4.4.1 General requirements 4.4.2 Data encoding rules |
49 | 4.4.3 DLL to PhL interface Figure 6 – M_symbols and Manchester encoding at 5 MHz Table 5 – Data encoding rules |
50 | Table 6 – M Data symbols Table 7 – Truth table for ph_status_indication |
51 | 4.5 Functional classes 5 General structure and encoding of PhIDUs and DLPDUs and related elements of procedure 5.1 Overview 5.2 Media access procedure |
52 | Figure 7 – NUT structure |
53 | Figure 8 – Media access during scheduled time |
54 | Figure 9 – Media access during unscheduled time |
55 | 5.3 DLPDU structure and encoding 5.3.1 General 5.3.2 DLPDU components 5.3.3 Preamble 5.3.4 Start and end delimiters 5.3.5 DLPDU octets and ordering Figure 10 – DLPDU format |
56 | 5.3.6 Source MAC ID 5.3.7 Lpackets field 5.3.8 Frame check sequence (FCS) Table 8 – FCS length, polynomials and constants |
59 | 5.3.9 Null DLPDU 5.3.10 Abort DLPDU 5.4 Lpacket components 5.4.1 General Lpacket structure Figure 11 – Aborting a DLPDU during transmission |
60 | 5.4.2 Size 5.4.3 Control 5.4.4 Generic tag Lpackets Figure 12 – Lpacket format |
61 | 5.4.5 Fixed tag Lpackets 5.5 DLPDU procedures 5.5.1 General Figure 13 – Generic tag Lpacket format Figure 14 – Fixed tag Lpacket format |
62 | 5.5.2 Sending scheduled DLPDUs 5.5.3 Sending unscheduled DLPDUs 5.5.4 Receiving DLPDUs |
63 | 5.6 Summary of DLL support services and objects Table 9 – DLL support services and objects |
64 | 6 Specific DLPDU structure, encoding and procedures 6.1 Modeling language 6.1.1 State machine description |
65 | 6.1.2 Use of DLL- prefix 6.1.3 Data types |
66 | 6.2 DLS user services 6.2.1 General Table 10 – Elementary data types |
67 | 6.2.2 Connected mode and connectionless mode transfer service |
68 | 6.2.3 Queue maintenance service 6.2.4 Tag filter service |
69 | 6.2.5 Link synchronization service 6.2.6 Synchronized parameter change service |
70 | 6.2.7 Event reports service Table 11 – DLL events |
71 | 6.2.8 Bad FCS service 6.2.9 Current moderator service 6.2.10 Power up and online services |
72 | 6.2.11 Enable moderator service 6.2.12 Listen only service 6.3 Generic tag Lpacket 6.3.1 General 6.3.2 Structure of the generic-tag Lpacket |
73 | 6.3.3 Sending and receiving the generic-tag Lpacket 6.4 Moderator Lpacket 6.4.1 General 6.4.2 Structure of the moderator Lpacket 6.4.3 Sending and receiving the moderator Lpacket |
74 | 6.5 Time distribution Lpacket 6.5.1 General 6.5.2 Structure of the time distribution Lpacket |
75 | Figure 15 – Goodness parameter of TimeDist_Lpacket |
76 | 6.5.3 Sending and receiving the time distribution Lpacket Table 12 – Time distribution priority |
77 | 6.6 UCMM Lpacket 6.6.1 General 6.6.2 Structure of the UCMM Lpacket 6.6.3 Sending and receiving the UCMM Lpacket 6.7 Keeper UCMM Lpacket 6.7.1 General 6.7.2 Structure of the Keeper UCMM Lpacket 6.7.3 Sending and receiving the Keeper UCMM Lpacket |
78 | 6.8 TUI Lpacket 6.8.1 General 6.8.2 Structure of the TUI Lpacket Table 13 – Format of the TUI Lpacket |
79 | 6.8.3 Sending and receiving the TUI Lpacket 6.9 Link parameters Lpacket and tMinus Lpacket 6.9.1 General 6.9.2 Structure of link parameters and tMinus Lpackets |
80 | 6.9.3 Sending and receiving the tMinus and Link parameters Lpackets 6.10 I’m-alive Lpacket 6.10.1 General 6.10.2 Structure or the I’m-alive Lpacket |
81 | 6.10.3 Sending and receiving I’m Alive 6.10.4 I’m alive state processing |
82 | 6.11 Ping Lpackets 6.11.1 General Figure 16 – Example I’m alive processing algorithm |
83 | 6.11.2 Structure of the ping Lpackets 6.11.3 Sending and receiving the ping Lpackets 6.12 WAMI Lpacket 6.12.1 General |
84 | 6.12.2 Structure of the WAMI Lpacket 6.12.3 Sending and receiving the WAMI Lpacket 6.13 Debug Lpacket |
85 | 6.14 IP Lpacket 6.15 Ethernet Lpacket 7 Objects for station management 7.1 General |
87 | 7.2 ControlNet™ object 7.2.1 Overview 7.2.2 Class attributes 7.2.3 Instance attributes Table 14 – ControlNet object class attributes |
88 | Table 15 – ControlNet object instance attributes |
93 | Table 16 – TUI status flag bits |
94 | Table 17 – Mac_ver bits Table 18 – Channel state bits |
96 | 7.2.4 Common services Table 19 – ControlNet object common services |
97 | 7.2.5 Class specific services Table 20 – ControlNet object class specific services |
98 | 7.2.6 Behavior 7.2.7 Module status indicator |
99 | 7.3 Keeper object 7.3.1 Overview 7.3.2 Revision history 7.3.3 Class attributes 7.3.4 Instance attributes Table 21 – Keeper object revision history Table 22 – Keeper object class attributes |
100 | Table 23 – Keeper object instance attributes |
104 | Table 24 – Keeper operating state definitions Table 25 – Port status flag bit definitions |
105 | Table 26 – TUI status flag bits |
106 | Figure 17 – Keeper CRC algorithm |
108 | 7.3.5 Common services Table 27 – Keeper attributes Table 28 – Memory requirements (in octets) for the Keeper attributes |
109 | 7.3.6 Class specific services Table 29 – Keeper object common services Table 30 – Keeper object class specific services |
110 | Table 31 – Service error codes |
114 | Table 32 – Wire order format of the TUI Lpacket |
115 | 7.3.7 Service error codes 7.3.8 Behavior Table 33 – Service error codes |
116 | 7.3.9 Miscellaneous notes Table 34 – Keeper object operating states |
117 | 7.3.10 Keeper power up sequence |
118 | Figure 18 – Keeper object power-up state diagram |
119 | Figure 19 – Keeper object operating state diagram |
120 | Table 35 – Keeper object state event matrix |
122 | 7.4 Scheduling object 7.4.1 Overview Figure 20 – Synchronized network change processing |
123 | 7.4.2 Class attributes 7.4.3 Instance attributes Table 36 – Scheduling object class attributes |
124 | 7.4.4 Common services Table 37 – Scheduling object instance attributes Table 38 – Scheduling object common services |
125 | Table 39 – Status error descriptions for Create |
126 | 7.4.5 Class specific services Table 40 – Status error descriptions for Delete and Kick_Timer Table 41 – Scheduling object class specific services |
128 | Table 42 – Status error descriptions for Read |
129 | Table 43 – Status error descriptions for Conditional_Write Table 44 – Status error descriptions for Forced_Write |
130 | Table 45 – Status error descriptions for Change_Start |
131 | Table 46 – Status error descriptions for Break_Connections Table 47 – Status error descriptions for Change_Complete |
132 | 7.4.6 Typical scheduling session Table 48 – Status error descriptions for Restart_Connections |
133 | 7.5 TCP/IP Interface object 7.5.1 Overview 7.5.2 Revision history 7.5.3 Class attributes Table 49 – Revision history |
134 | 7.5.4 Instance attributes Table 50 – TCP/IP Interface object class attributes Table 51 – TCP/IP Interface object instance attributes |
139 | Table 52 – Status bits |
140 | Table 53 – Configuration capability bits |
141 | Table 54 – Configuration control bits |
142 | Table 55 – Example path |
143 | Table 56 – Interface configuration components |
145 | Table 57 – Alloc control values |
146 | Table 58 – AcdActivity values Table 59 – ArpPdu – ARP Response PDU in binary format |
147 | Table 60 – Admin Capability member bit definitions |
148 | Table 61 – Admin Capability member bit definitions |
149 | 7.5.5 Diagnostic connection points 7.5.6 Common services Table 62 – TCP/IP Interface connection point 1, Standard Network Diagnostics |
150 | Table 63 – TCP/IP Interface object common services |
151 | Table 64 – Get_Attributes_All response format |
152 | 7.5.7 Class specific services Table 65 – Set_Attributes_All request format Table 66 – TCP/IP Interface object class specific services |
153 | Table 67 – Set_Port_Admin_State service request parameters Table 68 – Set_Protocol_Admin_State service request parameters |
154 | 7.5.8 Behavior Figure 21 – State transition diagram for TCP/IP Interface object Table 69 – Class specific error codes |
155 | 7.5.9 Address Conflict Detection (ACD) Figure 22 – State transition diagram for TCP/IP Interface object |
157 | Figure 23 – ACD Behavior |
161 | 7.6 Ethernet Link object 7.6.1 Overview 7.6.2 Revision history 7.6.3 Class attributes Table 70 – Ethernet link object revision history |
162 | 7.6.4 Instance attributes Table 71 – Ethernet link object class attributes Table 72 – Ethernet link object instance attributes |
167 | Table 73 – Interface flags bits |
169 | Table 74 – Control bits |
170 | Table 75 – Interface type Table 76 – Interface state Table 77 – Admin state |
171 | Table 78 – Capability Bits |
172 | 7.6.5 Diagnostic connection points Table 79 – Ethernet Link connection point 1, Standard Network Diagnostics |
173 | 7.6.6 Common services Table 80 – Ethernet Link object common services |
174 | 7.6.7 Class specific services Table 81 – Get_Attributes_All response format |
175 | 7.6.8 Behavior Table 82 – Ethernet Link object class specific services |
176 | 7.7 DeviceNet™ object 7.7.1 Overview Figure 24 – State transition diagram for Ethernet Link object |
177 | 7.7.2 Revision history 7.7.3 Class attributes 7.7.4 Instance attributes Table 83 – DeviceNet object revision history Table 84 – DeviceNet object class attributes Table 85 – DeviceNet object instance attributes |
180 | Table 86 – Bit rate attribute values Table 87 – BOI attribute values |
183 | Table 88 – Diagnostic counters bit description |
184 | 7.7.5 Common services Table 89 – DeviceNet object common services Table 90 – Reset service parameter Table 91 – Reset service parameter values |
185 | 7.7.6 Class specific services Table 92 – DeviceNet object class specific services |
186 | 7.8 Connection Configuration object (CCO) 7.8.1 Overview 7.8.2 Revision history 7.8.3 Class attributes Table 93 – Connection Configuration object revision history Table 94 – Connection Configuration object class attributes |
188 | 7.8.4 Instance attributes Table 95 – Format number values Table 96 – Connection Configuration object instance attributes |
192 | Table 97 – Originator connection status values Table 98 – Target connection status values |
193 | Table 99 – Connection flags |
195 | Table 100 – I/O mapping formats |
197 | 7.8.5 Connection Configuration object change control 7.8.6 Common services Table 101 – Services valid during a change operation Table 102 – Connection Configuration object common services |
198 | Table 103 – Get_Attributes_All Response – class level Table 104 – Get_Attributes_All response – instance level |
200 | Table 105 – Set_Attributes_All error codes Table 106 – Set_Attributes_All request |
202 | Table 107 – Create request parameters Table 108 – Create error codes Table 109 – Delete error codes |
203 | 7.8.7 Class specific services Table 110 – Restore error codes Table 111 – Connection Configuration object class specific services |
204 | Table 112 – Change_Start error codes |
205 | Table 113 – Get_Status service parameter Table 114 – Get_Status service response Table 115 – Get_Status service error codes |
206 | Table 116 – Change_Complete service parameter Table 117 – Change_Complete service error codes Table 118 – Audit_Changes service parameter Table 119 – Audit_Changes service error codes |
207 | 7.8.8 Behavior 7.9 DLR object 7.9.1 Overview Figure 25 – Connection Configuration object edit flowchart |
208 | 7.9.2 Revision history 7.9.3 Class attributes 7.9.4 Instance attributes Table 120 – Revision history Table 121 – DLR object class attributes |
209 | Table 122 – DLR object instance attributes |
213 | Table 123 – Network Status values Table 124 – Ring Supervisor Status values |
217 | Table 125 – Capability flags |
219 | Table 126 – Redundant Gateway Status values |
220 | 7.9.5 Diagnostic connection points 7.9.6 Common services Table 127 – DLR connection point 1, Standard Network Diagnostics Table 128 – DLR connection point 2, Standard Network Diagnostics |
221 | Table 129 – DLR object common services Table 130 – Get_Attributes_All Response – Object Revision 1, non supervisor device |
222 | Table 131 – Get_Attributes_All Response – Object Revision 1, supervisor-capable device Table 132 – Get_Attributes_All Response – Object Revision 2, non supervisor device |
223 | Table 133 – Get_Attributes_All Response – All other cases |
224 | 7.9.7 Class specific services Table 134 – DLR object class specific services |
225 | 7.10 QoS object 7.10.1 Overview 7.10.2 Revision History 7.10.3 Class attributes Table 135 – QoS object revision history |
226 | 7.10.4 Instance Attributes Table 136 – QoS object class attributes Table 137 – QoS object instance attributes |
227 | 7.10.5 Common services Table 138 – Default DCSP values and usages |
228 | 7.11 Port object 7.11.1 Overview 7.11.2 Revision History Table 139 – QoS object common services |
229 | 7.11.3 Class attributes 7.11.4 Instance attributes Table 140 – Port object revision history Table 141 – Port object class attributes |
230 | Table 142 – Port object instance attributes |
232 | Table 143 – Port Type and associated Logical Link Object classes and Port Type Name values |
235 | Table 144 – Port Routing Capabilities attribute bit definitions |
236 | 7.11.5 Common services Figure 26 – Communication objects diagram for example device Table 145 – Contents of Associated Communication objects attribute 11 for the two Port object instances of the example device |
237 | Table 146 – Port object common services Table 147 – Get_Attributes_All response– class level Table 148 – Get_Attributes_All response– instance level |
238 | 7.12 PRP/HSR Protocol object 7.12.1 Overview 7.12.2 Revision history 7.12.3 Class attributes 7.12.4 Instance attributes Table 149 – Revision history Table 150 – Class attributes |
239 | Table 151 – Instance attributes |
242 | Table 152 – Node Type |
243 | Table 153 – Switching Node |
244 | Table 154 – HSR Mode |
245 | Table 155 – RedBox ID |
246 | 7.12.5 Diagnostic connection points 7.12.6 Common Services Table 156 – PRP/HSR Protocol connection point 1, Standard Network Diagnostics |
247 | Table 157 – PRP/HSR Protocol object common services Table 158 – Get_Attributes_All response |
248 | 7.13 PRP/HSR Nodes Table object 7.13.1 Overview 7.13.2 Revision history |
249 | 7.13.3 Class attributes 7.13.4 Instance attributes Table 159 – Revision history Table 160 – Class attributes Table 161 – Instance attributes |
251 | 7.13.5 Common services Table 162 – Remote Node Type |
252 | 7.14 LLDP Management object 7.14.1 Overview 7.14.2 Revision history Table 163 – PRP/HSR Nodes Tables object common services Table 164 – Get_Attributes_All response Table 165 – Revision history |
253 | 7.14.3 Class attributes 7.14.4 Instance attributes Table 166 – Class attributes Table 167 – Instance attributes |
254 | 7.14.5 Common services Table 168 – Bit Definitions of the LLDP Enable Array |
255 | 7.15 LLDP Data Table object 7.15.1 Overview Table 169 – LLDP Management object common services Table 170 – Get_Attributes_All response |
256 | 7.15.2 Revision history 7.15.3 Class attributes 7.15.4 Instance attributes Table 171 – Revision history Table 172 – Class attributes Table 173 – Instance attributes |
260 | 7.15.5 Common services Table 174 – Bitmaps of supported capabilities & enabled capabilities Table 175 – LLDP Management object common services |
261 | 8 Other DLE elements of procedure 8.1 Network attachment monitor (NAM) 8.1.1 General Table 176 – Get_Attributes_All response |
262 | Table 177 – NAM states |
263 | 8.1.2 Default parameters 8.1.3 Auto-addressing Figure 27 – NAM state machine Table 178 – Default link parameters |
264 | 8.1.4 Valid MAC IDs 8.1.5 State machine description |
270 | 8.2 Calculating link parameters 8.2.1 Link parameters 8.2.2 Conditions affecting link parameters 8.2.3 Moderator change |
271 | 8.2.4 NUT timing Table 179 – PhL timing characteristics |
272 | 8.2.5 Slot timing |
273 | 8.2.6 Blanking 8.2.7 Example implementation |
278 | 9 Detailed specification of DL components 9.1 General 9.2 Access control machine (ACM) |
297 | 9.3 TxLLC |
302 | 9.4 RxLLC |
305 | 9.5 Transmit machine (TxM) |
309 | 9.6 Receive machine (RxM) |
315 | 9.7 Serializer |
317 | 9.8 Deserializer 9.8.1 Octet construction |
318 | 9.8.2 FCS checking 9.8.3 End of DLPDU processing 9.9 DLL management |
320 | 10 Device Level Ring (DLR) protocol 10.1 General |
321 | 10.2 Support for Multiple DLR Ring Pairs Figure 28 – Devices with Multiple DLR Ring Pairs |
322 | 10.3 Supported topologies Figure 29 – DLR rings connected to switches |
323 | 10.4 Overview of DLR operation 10.4.1 Normal operation Figure 30 – Normal operation of a DLR network Figure 31 – Beacon and Announce frames |
324 | 10.4.2 Link failures Figure 32 – Link failure |
325 | 10.5 Classes of DLR implementation Figure 33 – Network reconfiguration after link failure |
326 | 10.6 DLR behavior 10.6.1 DLR variables 10.6.2 Ring supervisor Table 180 – DLR variables |
329 | 10.6.3 Ring node |
330 | 10.6.4 Sign on process |
331 | 10.6.5 Neighbor check process 10.7 Implementation requirements 10.7.1 Embedded switch requirements and recommendations Figure 34 – Neighbor Check process |
332 | 10.7.2 DLR implementation requirements Table 181 – DLR Link speed and duplex requirements |
333 | 10.7.3 IEC 61588 and Type 2 Ethernet considerations 10.7.4 IEEE Std 802.1Q-2018 STP/RSTP/MSTP considerations 10.8 Using non-DLR nodes in the ring network 10.8.1 General considerations |
334 | 10.8.2 Non-DLR end devices 10.8.3 Non-DLR switches |
335 | Figure 35 – Unsupported topology – example 1 Figure 36 – Unsupported topology – example 2 |
336 | 10.9 Redundant gateway devices on DLR network 10.9.1 General |
337 | 10.9.2 Supported topologies 10.9.3 Redundant gateway capable device Figure 37 – DLR ring connected to switches through redundant gateways |
338 | 10.9.4 Redundant gateway device behavior Figure 38 – DLR redundant gateway capable device |
339 | Table 182 – Redundant gateway variables |
340 | Figure 39 – Advertise frame |
341 | 10.10 DLR messages 10.10.1 General |
342 | 10.10.2 Common frame header Table 183 – MAC addresses for DLR messages Table 184 – IEEE Std 802.1Q-2018 common frame header format Table 185 –DLR message payload fields |
343 | 10.10.3 Beacon frame 10.10.4 Neighbor_Check request Table 186 – DLR frame types Table 187 – Format of the Beacon frame Table 188 – Ring State values |
344 | 10.10.5 Neighbor_Check_response 10.10.6 Link_Status/Neighbor_Status Table 189 – Format of the Neighbor_Check request Table 190 – Format of the Neighbor_Check response Table 191 – Format of the Link_Status/Neighbor_Status frame |
345 | 10.10.7 Locate_Fault 10.10.8 Announce 10.10.9 Sign_On Table 192 – Link/Neighbor status values Table 193 – Format of the Locate_Fault frame Table 194 – Format of the Announce frame |
346 | 10.10.10 Advertise 10.10.11 Flush_Tables Table 195 – Format of the Sign_On frame Table 196 – Format of the Advertise frame Table 197 – Gateway state values |
347 | 10.10.12 Learning_Update 10.11 State diagrams and state-event-action matrices 10.11.1 Beacon-based ring node Table 198 – Format of the Flush_Tables frame Table 199 – Format of the Learning_Update frame |
348 | Figure 40 – State transition diagram for Beacon frame based non-supervisor ring node Table 200 – Parameter values for Beacon frame based non-supervisor ring node |
349 | Table 201 – LastBcnRcvPort bit definitions Table 202 – State-event-action matrix for Beacon frame based non-supervisor ring node |
354 | 10.11.2 Announce-based ring node Figure 41 – State transition diagram for Announce frame basednon-supervisor ring node |
355 | Table 203 – Parameter values for Announce frame based non-supervisor ring node Table 204 – State-event-action matrix for Announce frame basednon-supervisor ring node |
358 | 10.11.3 Ring supervisor Figure 42 – State transition diagram for ring supervisor |
359 | Table 205 – Parameter values for ring supervisor node |
360 | Table 206 – LastBcnRcvPort bit definitions Table 207 – State-event-action matrix for ring supervisor node |
373 | 10.11.4 Redundant gateway Figure 43 – State transition diagram for redundant gateway Table 208 – Parameter values for redundant gateway node |
374 | Table 209 – State-event-action matrix for redundant gateway node |
376 | 10.12 Performance analysis 10.12.1 General |
377 | Table 210 – Parameters/assumptions for example performance calculations |
380 | 10.12.2 Redundant gateway switchover performance Table 211 – Example ring configuration parameters and performance |
381 | Table 212 – Variables for performance analysis |
382 | 11 PRP and HSR redundancy protocols 11.1 General 11.2 PRP overview 11.2.1 General |
383 | 11.2.2 Address Conflict Detection (ACD) Figure 44 – PRP network |
384 | 11.3 HSR overview Figure 45 – Directly Attached SANs Figure 46 – Virtual DANs |
385 | 12 LLDP protocol 12.1 General Figure 47 – HSR network |
386 | 12.2 LLDP overview 12.3 Type 2 LLDP Transmission Requirements 12.3.1 General Figure 48 – IEEE LLDP PDU Format (source IEEE Std 802.1AB-2016) Table 213 – LLDP support requirements |
387 | 12.3.2 Chassis ID TLV (TLV Type = 1) 12.3.3 Port ID TLV (TLV Type = 2) Figure 49 – Type 2 LLDP PDU Format Table 214 – LLDP TLV Type Values |
388 | 12.3.4 System Capabilities TLV (TLV Type = 7) 12.3.5 Management Address (TLV Type = 8) 12.3.6 Type 2 Identification TLV (TLV Type = 127) 12.3.7 Type 2 MAC Address TLV (TLV Type = 127) 12.3.8 Type 2 Interface Label TLV (TLV Type = 127) Figure 50 – Type 2 Identification TLV Format Figure 51 – Type 2 MAC Address TLV Format |
389 | 12.3.9 Additional Ethernet Capabilities TLV (TLV Type = 127) 12.4 Type 2 LLDP Reception Requirements 12.5 Type 2 LLDP Reporting Requirements 12.6 EtherNet/IP LLDP Link State Transition Requirements Figure 52 – Type 2 Interface Label TLV Format |
390 | Annex A (normative)Indicators and switches A.1 Purpose A.2 Indicators A.2.1 General indicator requirements A.2.2 Common indicator requirements |
391 | Table A.1 – Module status indicator |
392 | A.2.3 Fieldbus specific indicator requirements – option 1 Table A.2 – Time Sync status indication |
394 | Table A.3 – Network status indicators |
396 | A.2.4 Fieldbus specific indicator requirements – option 2 Figure A.1 – Non redundant network status indicator labeling Figure A.2 – Redundant network status indicator labeling |
398 | Table A.4 – Network status indicator |
399 | Figure A.3 – Network status indicator state diagram Figure A.4 – Examples of multiple network status indicators |
400 | A.2.5 Fieldbus specific indicator requirements – option 3 Table A.5 – Combined Module/Network status indicator |
402 | Table A.6 – Network status indicator |
403 | Table A.7 – Combined module/network status indicator |
404 | Table A.8 – I/O status indicator |
405 | A.3 Switches A.3.1 Common switch requirements A.3.2 Fieldbus specific switch requirements – option 1 A.3.3 Fieldbus specific switch requirements – option 2 |
406 | A.3.4 Fieldbus specific switch requirements – option 3 Table A.9 – Bit rate switch encoding |
407 | Bibliography |