IEEE 802.1Qcx-2020：TSN协议的连接故障管理YANG数据模型

版权申诉

5星 · 超过95%的资源 136 浏览量更新于2024-07-04 收藏 1.19MB PDF 举报

"IEEE 802.1Qcx-2020标准是关于局域网和城域网中桥接和桥接网络的修正案，特别是针对连接性故障管理的YANG数据模型。该标准由IEEE计算机学会的LAN/MAN标准委员会开发，是对2018年IEEE 802.1Q标准以及后续修正案802.1Qcp、802.1Qcc和802.1Qcy的进一步扩展。" 在工业自动化、物联网(IoT)和时间敏感网络(TSN)领域，IEEE 802.1Qcx-2020标准扮演着关键角色。TSN（Time-Sensitive Networking）协议族是为了解决网络中对实时性和确定性有高要求的应用而设计的，如在汽车制造、航空航天、音频视频流传输等场景。它确保了数据包在网络中的传输具有极低的延迟和高度的一致性。 IEEE 802.1Qcx标准是TSN协议的一部分，专注于连接性故障管理。这个标准引入了一种名为YANG的数据模型，这是一种用于配置、管理和监控网络设备的接口语言。YANG使得网络设备之间的通信更加标准化，简化了网络运维，并增强了网络的可编程性。通过使用YANG，网络管理员可以更有效地检测、诊断和恢复网络中的连接性故障，提高了网络的可靠性和可用性。在802.1Qcx中，连接性故障管理涉及了桥接设备的监控和故障检测，例如，它可以检测到链路中断、帧丢失或重复等问题，并迅速采取行动来恢复服务。此外，该标准还可能包括故障预防机制，通过预测潜在问题并提前进行调整来避免故障的发生。此标准的实施对于构建高效、可靠和安全的TSN网络至关重要。结合其他IEEE 802.1Q系列标准，如流量控制（802.1Qbb）、时间同步（802.1AS）和调度（802.1Qbv），TSN能够提供一个统一的框架，使得不同厂商的设备能够在同一网络中协同工作，实现精确的时间同步和数据传输。 IEEE 802.1Qcx-2020是TSN技术的重要组成部分，它提供了连接性故障管理的标准化方法，有助于创建更加健壮和适应性强的工业网络环境。通过使用YANG数据模型，网络管理者可以更加智能化地管理和维护其网络基础设施，确保关键应用的性能和稳定性。

IEEE Std 802.1Qcx-2020

IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks

Amendment 33: YANG Data Model for Connectivity Fault Management

48. YANG Data Model

Change the introductory text of Clause 48 (as introduced in IEEE Std 802.1Qcp-2018) as follows:

This clause specifies YANG data models that provide control and status monitoring of bridges

IEEE 802.1Q

Bridges. Specifically,

a) Two-Port MAC Relays,

b) Customer VLAN bridges Bridges, and

c) Provider bridges Bridges.

The YANG bridge data management models are derived from UML models specified in 48.3. The UML

models are based on Clause 12.

This clause also specifies YANG data models for CFM protocol suite control and monitoring when applied

on the aforementioned bridges

Bridges.

NOTE 1—OMB UML 2.5 [B78] conventions together with C++ language constructs are used in this clause as a

representation to convey model structure and relationships.

NOTE 2—The MIB modules specified in Clause 17 were also derived from Clause 12. Consequently, the capabilities

and structure of the YANG data models align closely with

should closely aligned with that represented by the MIBs.

However the YANG data model has not been derived from the MIB, and there has been no attempt to include data or

modeling constructs that might appear in the MIB but not in the information model.

48.1 YANG Framework

Replace Figure 48-2 with the following figure:

Figure 48-2—YANG root hierarchy with IEEE 802.1Q YANG modules

IETF System

Management

IETF Interface

Management

IETF Routing 802.1Q Bridge

PAE

Sys tem

...

IS-IS

OSP F

...

PAE

Bridge

Port

TPMR

Customer

VLAN Bridge

Provider

Bridge

CFM

Maintenance

Domain

Maintenance

Association

CFM Stack

Default MD

Level

Maintenance

Group

MEP

Authorized licensed use limited to: Carleton University. Downloaded on November 03,2020 at 17:05:39 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 802.1Qcx-2020

IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks

Amendment 33: YANG Data Model for Connectivity Fault Management

48.3 802.1Q YANG model

Insert the following subclause (48.3.3, including Figure 48-11 through Figure 48-14) after 48.3.2.3:

48.3.3 CFM model

The CFM UML data model is composed of the following set of major objects:

— The Maintenance Domain object is associated with a device (e.g., Bridge). It contains information

used to identify the maintenance domain used to bind/contain Maintenance Association objects.

— The Maintenance Association objects are contained within a Maintenance Domain object. They

contain maintenance point information related to the service instance being monitored.

— The Maintenance Group objects provide a convenient binding of a Maintenance Association object

with a Maintenance Domain object.

— The Maintenance association Endpoint (MEP) object is associated with an Interface (e.g., Bridge

port) and a Maintenance Association Group object. It contains all information to manage a CFM

entity, associated with a specific DoSAP of a service instance, which can generate and receive CFM

PDUs and track any responses.

— The Maintenance domain Intermediate Point (MIP) object is associated with an Interface (e.g.,

Bridge port) and a service (e.g., VID) to allow the explicit creation of an MHF.

— The CFM Stack object is associated with a device (e.g., Bridge). It contains information about

maintenance points on a particular device Interface (e.g., Bridge port or Aggregation Port).

— The Default MD Level object is associated with a device (e.g., Bridge) component. It contains MHF

information needed for the creation of these functions on the services (e.g., VIDs) that are not

attached to any Maintenance Association.

— The Configuration Error List is associated with a device (e.g., Bridge). It contains configuration

error information that is identifiable on a per-Interface (e.g., Bridge port) and per-service (e.g., VID)

basis.

Authorized licensed use limited to: Carleton University. Downloaded on November 03,2020 at 17:05:39 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 802.1Qcx-2020

IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks

Amendment 33: YANG Data Model for Connectivity Fault Management

The UML model representing the relationship between relevant Bridge objects to CFM objects is illustrated

in Figure 48-11.

Figure 48-11—Bridge to CFM YANG model

* bridge

string name; // (1 2.4) r-w

macAddress address; // (12.4) r-w

enum type; // r-w

int por ts; // (1 2.4) r

cou nt er32 up-time; // (1 2.4) r

int com p one nt s; // r

name

ma-id

maint enance-gro up

string maintenance-gro up-id // r-w

string md-id; // r-w

string ma-id; // r-w

struct service-id; // (12.1 4.5.3.2) r-w

ref bri dge-id; // r-w

ref component-name // r-w

de fa ult-m d-leve l

int bridge-i d; // r-w

int com p one nt - i d; // r-w

str uct primary-service-id; // (12.1 4. 3.1 .2) r-w

struct asso ciated-service-ids; // (12.14. 3.1 .3) r-w

bool md-sta tus; // (1 2.1 4. 3.1.3) r-w

int md-leve l; // (12.1 4. 3.1.3) r-w

enum mhf-creation; // (12.1 4. 3.1.3) r-w

enum id-permission; // (12.1 4. 3.1 .3) r-w

config-err or

if-r ef po r t; // r-w

str uct service-id; // (1 2.14. 4.1 .2) r-w

en um er ror - typ e; // (1 2.1 4. 4.1 .3) r

cfm-stack

if-ref por t; // r-w

int md-level; // (12.14. 2.1.2) r-w

enum direct ion; // (12.14. 4.1 .2) r-w

struct service-id; // r-w

string maint enance-gro up-id; // r

int mep-id; // (1 2.14. 2.1 .3) r

int md-id; // r

int ma-id; // r

address mac-address; // (12.1 4. 2.1.3) r

enum maint enance -po int; // (1 2.14. 2.1.3) r

compone nt

str ing nam e; // r-w

int id; // (1 2.3) r-w

enum typ e; // (1 2.3) r-w

macAddress address; // (8 .13.8 , 13.24) r-w

bo ol tr af f i c-class-en ab l ed; // (1 2.4 .1 .5.1 ) r-w

int ports; // (12.4.1.1.3) r

if-ref *bridge-port // r

struct capabilities // (12.4.1.5.2) r

mep

mep-id

maint ena nce-domain

string md-id; // r-w

choice md-name; // (21.6.5.3) r-w

int md-level; // (1 2.14. 5.1 .3) r-w

enum mhf-crea ti on; // (1 2.14. 5.1 .3) r-w

enum id-per missi on; // (12.14. 5.1 .3) r-w

address fault-alarm-transmission; // (12.14.5.1.3) r-w

maint ena nce-associatio n

string ma-id; // r-w

choice ma-name; // (21.6.5.4) r-w

enum ccm-interval; // (1 2.14. 6.1.3) r-w

address fault-alarm-transmission; // (12.14.5.1.3) r-w

enum mhf-crea ti on; // (1 2.14. 5.1 .3) r-w

enum id-per missi on; // (12.14. 3.1 .3) r-w

mep-id

maint enance-associatio n-mep

int mep-id; //(12.14.6.1. 3) r-w

Authorized licensed use limited to: Carleton University. Downloaded on November 03,2020 at 17:05:39 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 802.1Qcx-2020

IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks

Amendment 33: YANG Data Model for Connectivity Fault Management

The CFM objects (e.g., cfm-stack, configuration-error-list, default-md-level, maintenance-domain)

reference the device (i.e., Bridge and/or Bridge Component) to which they belong. This reference allows

CFM objects to be associated with other types of devices (e.g., non-Bridges, end stations) where

appropriate.

The Maintenance Group is modeled as a list that contains a convenient reference to a Maintenance

Association object and its corresponding Maintenance Domain object. The identification of this collection

of objects allows other CFM objects to more easily attach to a maintenance group and, in turn, simplifies

configuration and operation retrieval procedures supported by the data model.

As illustrated in Figure 48-12, MEP objects reference an Interface and are associated with a Maintenance

Group. The interface relationship allows a MEP to be associated with a Bridge port, as specified by this

standard. This model also allows MEPs to be associated with other Interface types (for other devices).

Figure 48-12—CFM MEP model relationships

ietf-interfaces

na m e

interfaces

str i ng na me; // r-w

string description; // r-w

if-type type; // r-w

bo ol en ab led; // r-w

enum link-up-down-trap-en able; // r-w

enum admin-status; // r

enum oper-status; // r

date-time last-change; // r

int3 2 if-index; // r

address phys-address; // r

if-ref * h igher-laye r-if; // r

if-ref * lower-layer-if; // r

guage6 4 speed; // r

bridge-port

str i ng com p one nt- na m e; // r-w

int pvid; // (12.10.1) r-w

int default-priority; // (12.6.2) r-w

struct priority-regeneration-ta ble; // (12.6 .2 , 6.9.4 ) r-w

enum pcp-selection ; // (1 2.6.2 , 6. 9.3 ) r-w

struct pcp-decoding-table; // (12.6.2) r-w

struct pcp-encoding-table; // (12.6.2) r-w

bool use-dei; // (1 2.6.2 , 6.9.3 ) r-w

bo ol dr op-en cod ing; // (1 2.6 .2 , 8. 6.6 ) r-w

enum service-acce ss-priority-selection ; // (1 2.6.2 , 6.13 ) r-w

struct service-access-priori ty; // (1 2.6.2 , 6.13 .1) r-w

struct traf fi c-class; // (12.6 .3 , 8.6.6 ) r-w

en um acce pt able -fr am e; // (1 2.1 0. 1.3 , 6 .9) r -w

bool enable-ingress-filtering; // (1 2.10. 1.4, 8 .6.2) r-w

bool enable-restricted-vlan-regist ra tion; // (1 2.10. 1.6, 1 1.2.3. 2.3) r-w

bo ol en ab le-v i d-tr an sl ation -ta ble; // (1 2.1 0. 1.8 , 6 .9) r -w

bool enable-egress-vid-translation-table; // (1 2.10. 1.9 , 6 .9) r-w

struct protocol-group-vid-set; // (12.10.1.7) r-w

int ad min-po i nt-to- po int; // (6 .8. 2, 12. 4.2 ) r-w

bool protoco l-ba sed-vlan-classificat ion; // (5 .4. 1.2 ) r

int max-vid-set -entries; // (1 2.10.1.1.3) r

int port-number; // (1 3.25, 12 .4. 2, 1 2. 3.i) r

enum port-type; // (1 2.4.2 .1) r

m acAd dr ess ad dress; // (1 2.4 .2 ) r

bits capabilities; // (12.4.2, 12.10.1.1.3) r

bits typ e-capabilitie s; // (1 2.4.2 ) r

bool ext ernal; // (12.4 .2 ) r

bool oper-point-to-point; // (1 2.4.2 ) r

po rt

mep

mep-id

maint ena nce -gr o up

str ing maint enance-gro up-id; // r-w

string md-id; // r-w

string ma-id; // r-w

str uct service-id; // (12.1 4. 5.3.2) r-w

ref bridge-id; // r-w

ref component-name // r-w

Authorized licensed use limited to: Carleton University. Downloaded on November 03,2020 at 17:05:39 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 802.1Qcx-2020

IEEE Standard for Local and Metropolitan Area Networks—Bridges and Bridged Networks

Amendment 33: YANG Data Model for Connectivity Fault Management

The MEP object has relationships with other MEP-related objects. As illustrated in Figure 48-13, the CFM

continuity check protocol suite-specific data needed to initiate protocol-specific sessions or maintain

protocol-specific state information are grouped together. In addition, the MEP object will also reference the

MEP CCM database and Stats objects.

Figure 48-13—CFM MEP model

stats

cou nter m ep-c cm-s eq ue nce- er ror s; // (1 2.1 4. 7.1 .3) r

counter mep-ccms-sent; // (12.14.7.1.3) r

counter mep-lbr-in; // (12.14.7.1.3) r

counter mep-lbr-in-out-of -order; // (12.14.7.1.3) r

counter mep-lbr-bad-msdu ; // (1 2.14. 7.1.3) r

counter mep-unexp ected-ltr-in; // (1 2.14. 7.1.3) r

counter m ep-lbr-out; // (1 2.14. 7.1 .3) r

rmep-id

continuity-check

bool ccm-enabled; // (12.14.7.1.3) r -w

enum fault-alarm-transmision ; // (12.14. 7.1.3) r -w

enum lowest-priority-defect; // (12.14. 7.1.3) r -w

time fng-ala rm-tim e; // (1 2.14. 7.1 .3) r -w

time fng-reset-tim e; // (1 2.14. 7.1 .3) r -w

enum hig he st-priority-de fect; // (1 2.14. 7.1 .3) r

struct defects; // (12.14. 7.1.3) r

string error-ccm-last-failure; // (12.14. 7.1.3) r

enum fng-sta te; // (12.14. 7.1.3) r

string xcon-ccm-last-fa ilu re // (1 2.14. 7.1.3) r

mep

int mep-id; // (12.14. 7) r -w

if-ref por t; // (1 2.14. 7.1.3) r -w

enum direct ion; // (12.1 4. 7.1 .3) r -w

int primary-vid; // (12.14.7.1.3) r -w

bool enabled; // (1 2.14. 7.1.3) r -w

int ccm-ltm-priority; // (12.14.7.1.3) r -w

ad dr ess m ac-ad dress; // (1 2.1 4. 7.1 .3) r

list inactive-remote-mep // (12.14. 7.1.3) r -w

mep-db

int rme p-i d; // (12.1 4. 7.6.2) r

enum r me p-sta te; // (12.1 4. 7.6.3) r

time rme p-fail e d-ok-ti me; // (12.1 4. 7.6 .3) r

address mac-ad dress; // (12.1 4. 7.6 .3) r

bool rdi; // (12.1 4. 7.6.3) r

enum por t-sta tus-tlv; // (12.1 4. 7.6 .3) r

enum inte rface-sta tus-tlv; // (12.1 4. 7.6.3) r

enum cha ssis-id-subtype; // (12.1 4. 7.6.3) r

enum cha ssis-id; // (12.1 4. 7.6.3) r

struct transport-service-domain; // (12.1 4. 7.6.3) r

struct manage ment-address; // (12.1 4. 7.6.3) r

bool rme p-i s-active; // (12.1 4. 7.1.3) r

Authorized licensed use limited to: Carleton University. Downloaded on November 03,2020 at 17:05:39 UTC from IEEE Xplore. Restrictions apply.

剩余122页未读，继续阅读

汽车通信技术

粉丝: 2w+
资源: 74

IEEE 802.1Qcx-2020：TSN协议的连接故障管理YANG数据模型

IEEE 802.1Qcr-2020.pdf

IEEE Std 802.1Qcx-2020 Local and Metropolitan Area Networks—Brid

IEEE 802.1Qcx-2020: YANG数据模型与网络连接故障管理

在实施IEEE 802.1Qcx-2020标准时，如何通过YANG数据模型进行局域网连接故障的诊断与管理？请结合实际案例说明。

如何使用IEEE 802.1Qcx-2020标准中的YANG数据模型来诊断和管理局域网中的连接故障？请提供一个具体的实施案例。

2018.1 IEEE 802.1 YANG Data Modeling Overview.pdf

IEEE 802.1 YANG数据建模简介

QCX-SSB:这是一个简单且实验性的修改，可将您的QCX转换为（E级驱动）SSB收发器

最新资源