IEEE 802.1Q YANG Interface Framework in support of Link ......IEEE 802.1Q Bridge Port • The MAC...

IEEE 802.1Q YANG Interface Framework in support of Link

Aggregation (802.1AX), Security (802.1X), and CFM (802.1ag)

Marc HolnessVersion 1.325July 2016

Marc Holness (mholness@ciena.com) - 225 July 2016 cp-mholness-YANG-Link-Aggregation-Model-Summary-0716-v13

IETF Interface Management Model

• IETF Interface Management Model can be represented as shown below– UML-ized depiction of YANG model specified in RFC 7223

• Interface stack leaf nodes

Interface Stack Diagram Representation

Shim/Service‐1

OBJECT

Interface

Higher Layer

Lower Layer

{1} {}Shim/Service‐2

INTERFACE HIGHER & LOWERLAYER TABLE

INTERFACE REFERENCE• Pointer or Index

SHIM LAYER(e.g., Protocol Entity)

SERVICE ACCESS POINT (SAP)• YANG Interface definition

• A SAP is an abstraction and does not necessarily correspond to any concrete realization within a system

• The entities that support a particular SAP compose an interface stack

• Each YANG Interface definition contains an interface stack table

Interface Stack LAG

Member‐1 Member‐2Higher Layer

Lower Layer

{0} {} MAC‐1 MAC‐2

Higher Layer

Lower Layer

{0} {}

Higher Layer

Lower Layer

{} {1,2}

IEEE 802.1 Objects Within YANG Object Hierarchy

IETF System Management

IETF Interface Management IETF Routing 802.1Q Bridge

PAE System

Bridge Port

Customer VLAN

Provider Bridge

Introducing the [Generic] Bridge YANG Model

* bridgestring name; // (12.4) r-wmacAddress address; // (12.4) r-wenum type; // r-wint ports; // (12.4) rcounter32 up-time; // (12.4) rint components; // r

componentstring name; // r-wint id; // (12.3) r-wenum type; // (12.3) r-wmacAddress address; // (8.13.8, 13.24) r-wbool traffic-class-enabled; // (12.4.1.5.1) r-wbool mmrp-enabled-status; // (12.4.1.5.1)r-wint ports; // (12.4.1.1.3) rif-ref *bridge-port // rstruct capabilities // (12.4.1.5.2) r

filtering-databaseint aging-time; // (12.7, 8.8.3) r-wint size; // (12.7) rint static-entries; // (12.7, 8.8.1) rint dynamic-entries; // (12.7, 8.8.1) rint static-vlan-registration-entries; // (12.7, 8.8.2) rint dynamic-vlan-registration-entries; // (12.7, 8.8.5) rint mac-address-registration-entries; // (12.7, 8.8.4) r

database-id, address, vid*database-id, vid*

permanent-databaseint size; // (12.7.6) rint static-entries; // (12.7.6) rint static-vlan-registration-entries; // (12.7.6) r

database-id, address, vid*

bridge-vlanint version; // (12.10.1.3) rint max-vids; // (12.10.1.3) rbool override-default-pvid; // (12.10.1.3) rstuct protocol-template; // (12.10.1.7) rint max-msti; // (12.10.1.7) r

vlan-idint vid; // (12.10.2) r-wstring name; // (12.10.2) r-wif-ref *untagged-ports; // (8.8.2, 12.10.2.1.3) rif-ref *egress-ports; // (8.8.10, 12.10.2.1.3) r

protocol-group-databasestring frame-format-type; // (12.10.1.7) r-wstruct frame-format; // (12.10.1.7) r-wint protocol-group-id; // (6.12.2) r-w

vid*vids*

vid-to-fid-allocationint *vids; // (12.10.3) r-wint fid; // (12.10.3) r-wenum allocation-type; // (12.10.3) r

0 .. 1

vlan-registration-entriesint database-id; // (12.7.7) r-wint vid; // (12.7.7) r-wenum entry-type; // (12.7.7) r-w

filtering-entriesint database-id; // (12.7.7) r-wmacAddress address; // (12.7.7) r-wint vid; // (12.7.7) r-wenum entry-type; // (12.7.7) r-wenum status; // r

filtering-entriesint database-id; // (12.7.7) r-wmacAddress address; // (12.7.7) r-wint vid; // (12.7.7) r-wenum status; // r

port-mapif-ref port-number; // (8.8.1) r-wstruct map; // (8.8.1) r-w

port-number* port-number*port-number*

The list of Bridge Ports

IEEE 802.1Q Bridge Port

• Each Bridge Port is associated with one Interface, and in most situations, each Bridge Port is associated with a different interface

• However, there are situations in which multiple Bridge Ports are associated with the same interface

– For example, several Bridge Ports can each correspond one-to-one with several Ethernet private lines (or SDH virtual circuits) but all on the same Interface

– Or multiple Bridge Ports can each correspond to a single internal LAN (I-LAN) port

• Alternatively, there is the Link Aggregation (IEEE Std 802.1AX) case where there are many physical Ports for one Bridge Port

IEEE 802.1Q Bridge Port• The MAC Relay Entity handles the media access method-

independent functions of relaying frames among Bridge Ports. It uses the EISS (6.8, 6.9) provided by each Bridge Port

• Each Bridge Port also functions as an end station and shall provide the MAC Service to an LLC Entity that operates LLC Type 1 procedures to support protocol identification, multiplexing, and demultiplexing, for PDU transmission and reception by the Spanning Tree Protocol Entity and other higher layer entities

CFM Maintenance Point Placement

• CFM entities are specified as shims that make use of and provide the ISS or EISSS at SAPs within the network

• The relationships among MPs, and between the MPs and the other entities in a Bridge, are configurable

Introducing the Bridge Port Interface Modelietf-interfaces

statisticsdate-time discontinuity-time; // rcounter64 in-octets, in-unicast-pkts, in-broadcast-pkts, in-multicast-pkts; // rcounter64 in-discards, in-errors, in-unknown-protos, ; // rcounter64 out-octets, out-unicast-pkts, out-broadcast-pkts, out-multicast-pkts; // rcounter64 out-discards, out-errors; // r

interfacesstring name; // r-wstring description; // r-wif-type type; // r-wbool enabled; // r-wenum link-up-down-trap-enable; // r-w

interfaces-statestring name; // rif-type type; // renum admin-status; // renum oper-status; // rdate-time last-change; // rint32 if-index; // raddress phys-address; // rif-ref * higher-layer-if; // rif-ref * lower-layer-if; // rguage64 speed; // r

* namename*

bridge-portstring component-name; // r-wif-ref service-if // r-wint pvid; // (12.10.1) r-wint default-priority; // (12.6.2) r-wstruct priority-regeneration-table; // (12.6.2, 6.9.4) r-wenum pcp-selection; // (12.6.2, 6.9.3) r-wstruct pcp-decoding-table; // (12.6.2) r-wstruct pcp-encoding-table; // (12.6.2) r-wbool use-dei; // (12.6.2, 6.9.3) r-wbool drop-encoding; // (12.6.2, 8.6.6) r-wenum service-access-priority-selection; // (12.6.2, 6.13) r-wstruct service-access-priority; // (12.6.2, 6.13.1) r-wstruct traffic-class-table; // (12.6.3, 8.6.6) r-wenum acceptable-frame; // (12.10.1.3, 6.9) r-wbool enable-ingress-filtering; // (12.10.1.4, 8.6.2) r-wbool restricted-vlan-registration; // (12.10.1.6, 11.2.3.2.3) r-wbool vid-translation-table; // (12.10.1.8, 6.9) r-wbool egress-vid-translation-table; // (12.10.1.9, 6.9) r-wint protocol-group-id; // (6.12.2) r-wstruct protocol-group-database-contents; // (12.10.1.7) r-wint admin-point-to-point; // (6.8.2, 12.4.2) r-w

vid-translationsint local-vid; // (12.10.1.8, 6.9) r-wint relay-vid; // (12.10.1.8, 6.9) r-w

egress-vid-translationsint relay-vid; // (12.10.1.9, 6.9) r-wint local-vid; // (12.10.1.9, 6.9) r-w

relay-vid*

bridge-portbool protocol-based-vlan-classification;// (5.4.1.2) rint max-vid-set-entries; // (12.10.1.1.3) rint port-number; // (13.25, 12.4.2) renum port-type; // (12.4.2.1) rmacAddress address; // (12.4.2) rint capabilities; // (12.4.2, 12.10.1.1.3) rint type-capabilities; // (12.4.2) rbool external; // (12.4.2) rbool oper-point-to-point; // (12.4.2) r

bridge-port-statisticscounter64 delay-exceeded-discards, mtu-exceeded-discards; // (12.6.1.1.3) rcounter64 frame-rx, octets-rx, frame-tx, octets-tx; // (12.6.1.1.3) rcounter64 discard-inbound, forward-outbound, discard-lack-of-buffers; // (12.6.1.1.3) rcounter64 discard-transit-delay-exceeded, discard-on-error; // (12.6.1.1.3) rcounter64 discard-on-ingress-filtering, discard-ttl-expired; // (12.6.1.1.3) r

local-vid*

type = bridge (209)

Interface Stack of Bridge Port

YANG Bridge Port Model Except

augment "/if:interfaces/if:interface" {when "/if:type = 'ianaif:bridge'{

description"Applies when a Bridge interface";

}description

"Augment the interface model with the Bridge Port";container bridge-port {

leaf component-name {type dot1qtypes:component-ref;description

“Used to reference configured Component nodes.”;}:leaf service-if {

type interface-ref;description

“Reference to interfaces pointed to by the Bridge Port”;}:

Bridge Port

BRIDGE COMPONENT

Interface Stack Bridge Port

Bridge Port

Higher Layer

Lower Layer

{} {2}

Higher Layer

Lower Layer

{1} {}

• The Bridge Port interface provides a pointer to a service interface• The placement of CFM maintenance points (relative to other services)

would suggest that a separate SAP between the Bridge Ports and actual interface is required

BRIDGE COMPONENT

Bridge Port

Higher Layer

Lower Layer

{1} {}

Interface Stack Bridge Ports and Internal LAN

Bridge Port

BRIDGE COMPONENT

Bridge Port

BRIDGE COMPONENT

Bridge Port

I‐LAN

Higher Layer

Lower Layer

{} {3}

1Higher Layer

Lower Layer

{} {3}

Higher Layer

Lower Layer

{1,2} {}

Interface Stack Bridge Ports and Internal LAN

Bridge Port

BRIDGE COMPONENT

Bridge Port

BRIDGE COMPONENT

Bridge Port

Higher Layer

Lower Layer

1Higher Layer

Lower Layer

Member‐1 Member‐2

Interface Stack Bridge Port (LAG)

MAC‐1 MAC‐2

Higher Layer

Lower Layer

{1} {3,4}

Bridge Port

Higher Layer

Lower Layer

{2} {}

Higher Layer

Lower Layer

{2} {}

Higher Layer

Lower Layer

{} {2}

BRIDGE COMPONENT

Bridge Port

Member‐1 Member‐2

Interface Stack Bridge Port (LAG)

MAC‐1 MAC‐2

Higher Layer

Lower Layer

{} {3,4}

Higher Layer

Lower Layer

{2} {}

Higher Layer

Lower Layer

{2} {}

BRIDGE COMPONENT

Bridge Port

Interface Stack Bridge Port with MACSec

BRIDGE COMPONENT

Higher Layer

Lower Layer

{2} {}

Bridge Port

Controlled

Common

Higher Layer

Lower Layer

{1} {3}

Higher Layer

Lower Layer

{} {2}

Interface Stack Bridge Port with MACSec

BRIDGE COMPONENT

Higher Layer

Lower Layer

{2} {}

Bridge Port

Controlled

Common

Higher Layer

Lower Layer

{} {3}

MAC‐1 MAC‐2

Controlled Controlled

Interface Stack – Bridge Port (LAG) with MACSec

Common Common

Bridge PortHigher Layer

Lower Layer

{} {2}Higher Layer

Lower Layer

{1} {3,4}

Higher Layer

Lower Layer

{2} {6}

Higher Layer

Lower Layer

{2} {5}

5 6 Higher Layer

Lower Layer

{4} {}

BRIDGE COMPONENT

Bridge Port

Higher Layer

Lower Layer

{3} {}

MAC‐1 MAC‐2

Interface Stack – Bridge Port (LAG) with MACSec

Common Common

Higher Layer

Lower Layer

{1} {3,4}

Higher Layer

Lower Layer

{2} {6}

Higher Layer

Lower Layer

{2} {5}

5 6 Higher Layer

Lower Layer

{4} {}

BRIDGE COMPONENT

Bridge Port

Higher Layer

Lower Layer

{3} {}

MAC‐1 MAC‐2

Interface Stack – Bridge Port (LAG) without MACSec

Common Common

Bridge PortHigher Layer

Lower Layer

{} {2}Higher Layer

Lower Layer

{1} {3,4}

Higher Layer

Lower Layer

{2} {6}

Higher Layer

Lower Layer

{2} {5}

5 6 Higher Layer

Lower Layer

{4} {}

BRIDGE COMPONENT

Bridge Port

Higher Layer

Lower Layer

{3} {}

MAC‐1 MAC‐2

Interface Stack – Bridge Port (LAG) without MACSec

Common Common

Higher Layer

Lower Layer

{1} {3,4}

Higher Layer

Lower Layer

{2} {6}

Higher Layer

Lower Layer

{2} {5}

5 6 Higher Layer

Lower Layer

{4} {}

BRIDGE COMPONENT

Bridge Port

Higher Layer

Lower Layer

{3} {}

NETCONF and YANG Example Configuration

Bridge Port

Bridge Port<rpc message-id=”101” xmlns=”urn:ietf:params:xml:ns:yang:ietf-interfaces”>

<edit-config><target>

<name>if-1</name><type>bridge</type>

:</interface><interface xc:operation=“create”>

<name>if-2</name><type>ethernetCsmacd</type>

:</interface>

</top></config>

</edit-config></rpc>

• Interface specific configuration items

Bridge Port<rpc message-id=”101” xmlns=”urn:ieee:params:xml:ns:yang:ieee-dot1q-bridge”>

<bridge><name>the-bridge</name>

:<component>

<name>the-component</name>:

</component></bridge>:

</bridges><interface>

<name>if-1</name>:

<bridge-port><component-name>the-component</component-name><service-if>if-2</service-if>:

</bridge-port>:

</interface></top>

</config></edit-config>

</rpc>

Interface stack tables associated with each Interface gets updated by the system

Bridge Port (with 2 member LAG)

Bridge Port (with LAG)<rpc message-id=”101” xmlns=”urn:ietf:params:xml:ns:yang:ietf-interfaces”>

<name>if-2</name><type>ieee8023adLag</type>

:</interface>

</top></config>

Bridge Port (with LAG)<rpc message-id=”101” xmlns=”urn:ieee:params:xml:ns:yang:ieee-dot1ax”>

<name>if-3</name>:

</interface><interface>

<name>if-4</name>:

</members>:

</interface></top>

</rpc>

• LAG member specific configuration items

• Link Aggregation Group specific configuration items

Bridge Port (with LAG)<rpc message-id=”101” xmlns=”urn:ieee:params:xml:ns:yang:ieee-dot1q-bridge”>

<bridge><name>my-bridge</name>

:<component>

<name>if-1</name>:

</bridge-port>:

</interface></top>

</rpc>

Bridge Port (with MACSec)

Bridge Port (with MACSec)<rpc message-id=”101” xmlns=”urn:ietf:params:xml:ns:yang:ietf-interfaces”>

<name>if-2</name><type>macSecControlledIF</type>

:</interface>

</top></config>

Bridge Port (with MACSec)<rpc message-id=”101” xmlns=”urn:ieee:params:xml:ns:yang:ieee-dot1x”>

<pae-system><name>my-pae-system</name>:

</pae-system>:

</system><interface>

<name>if-2</name><pae-system>my-pae-system</pae-system>:

</interface></top>

</rpc>

• PAE System specific configuration items

• PAE specific configuration items

Bridge Port (with MACSec)<rpc message-id=”101” xmlns=”urn:ieee:params:xml:ns:yang:ieee-dot1q-bridge”>

<bridge><name>the-bridge</name>

:<component>

<name>if-1</name>:

</bridge-port>:

</interface></top>

</rpc>

Bridge Port (with 2 member LAG and MACSec)

Bridge Port (with LAG plus MACSec)<rpc message-id=”101” xmlns=”urn:ietf:params:xml:ns:yang:ietf-interfaces”>

:</interface>

Bridge Port (with LAG plus MACSec)<interface xc:operation=“create”>

:</interface>

</top></config>

Bridge Port (with LAG plus MACSec)<rpc message-id=”101” xmlns=”urn:ieee:params:xml:ns:yang:ieee-dot1ax”>

<name>if-3</name>:

<name>if-4</name>:

</members>:

</interface></top>

</rpc>

• LAG member specific configuration items

• Link Aggregation Group specific configuration items

Bridge Port (with LAG plus MACSec)<rpc message-id=”101” xmlns=”urn:ieee:params:xml:ns:yang:ieee-dot1x”>

<pae-system><name>my-pae-system</name>:

</pae-system>:

</system><interface>

</interface></top>

</rpc>

• PAE System specific configuration items

• PAE specific configuration items

Bridge Port (with LAG plus MACSec)<rpc message-id=”101” xmlns=”urn:ieee:params:xml:ns:yang:ieee-dot1q-bridge”>

<bridge><name>my-bridge</name>

:<component>

<name>if-1</name>:

</bridge-port>:

</interface></top>

</rpc>

IEEE 802.1Q YANG Interface Framework in support of Link ......IEEE 802.1Q Bridge Port • The MAC...

Documents

Transcript of IEEE 802.1Q YANG Interface Framework in support of Link ......IEEE 802.1Q Bridge Port • The MAC...

Reddees Inaláámmbricas de Área R Local y Personal …conatel.gob.ve/files/ceditel/Cursos_II_2010/Contenidos_cursos_2do... · Interfaces Vlan IEEE 802.1Q y Bridge IEEE 802.1D Gestión

ADAPTER CARDS - Login · ETHERNET – IEEE 802.3ae 10 Gigabit Ethernet – IEEE 802.3ad Link Aggregation and Failover – IEEE 802.1Q, .1p VLAN tags and priority – IEEE P802.1au

FTTH Active Ethernet - CTC U · • GbE IAD Gateway with IEEE 802.11ac WiFi • Per port based NAT/bridge hybrid mode • IEEE 802.1Q tagged VLAN • IEEE 802.1p / DSCP QoS • IGMP

This is a preview - click here to buy the full publication … · 2020. 8. 24. · IEEE Std 802.1Q™-2018 (Revision of IEEE Std 802.1Q-2014) IEEE Standard for Local and Metropolitan

Ethernet (IEEE 802.3) · IEEE 802.1Q, or VLAN Tagging, is an IEEE standard allowing multiple bridged networks to transparently share the same physical network link without leakage.

IEEE 802.1Q –Ethernet-cfm (IEEE 802.1ag)grouper.ieee.org/groups/802/1/files/public/docs2020/new... · 2020. 6. 29. · • AS per IEEE Std 802.1Q-2018 -An entry in the CCM Database

IEEE 802 · IETF 86 – Tutorial IEEE 802.1Q Media Access Control Bridges and Virtual Bridged Local Area Networks Patricia Thaler, Norman Finn, Don Fedyk,

On the Outage Probability of MIMO Full-Duplex Relaying ... · Relaying : Impact of Antenna Correlation and Imperfect CSI Ahmed Almradi, Student Member, IEEE, and Khairi Ashour Hamdi,

IPS-G803SMIEEE 802.1d STP (Spanning Tree Protocol) IEEE 802.1w RSTP (Rapid Spanning Tree Protocol) IEEE 802.1s MSTP (Multiple Spanning Tree Protocol) IEEE 802.1Q for VLAN Tagging IEEE

Working Group I21, Relaying Practices Subcommittee IEEE ......2016/05/09 · 1 Working Group I21, Relaying Practices Subcommittee IEEE PES Power System Relaying Committee Analysis

IEEE 802.1Q YANG Bridge Port Interface Model in Support · PDF fileIEEE 802.1Q YANG Bridge Port Interface Model in Support of 802 ... with several Ethernet ... frame-tx, octets-tx;

Configuring IEEE 802.1Q Tunneling, VLAN Mapping, 802.1ad ......14-3 Cisco ME 3400E Ethernet Access Switch Software Configuration Guide OL-16485-05 Chapter 14 Configuring IEEE 802.1Q

Fundamentals of Modern Protective Relaying - IEEE

IEEE Std 802.1Q -2001, -2002) 802.1QTM EEE Standards IEEE ...w3.tmit.bme.hu/courses/onlab/library/standards/802-1Q-2003.pdf · IEEE Std 802.1Q™, 2003 Edition (Incorporates IEEE

IEEE 802.1Q Bridging and Connectivity Fault Management ... · IEEE 802.1Q Bridging and Connectivity Fault Management YANG Data Model Introduction Marc Holness (mholness@ciena.com),

IEEE Std 802.1Q -2001, -2002) 802.1QTM EEE Standards IEEE ... · IEEE Std 802.1Q™, 2003 Edition (Incorporates IEEE Std 802.1Q-1998, IEEE Std 802.1u™-2001, IEEE Std 802.1v™-2001,

1 Distributed Association and Relaying with Fairness in ... · 1 Distributed Association and Relaying with Fairness in Millimeter Wave Networks Yuzhe Xu, Student Member, IEEE, Hossein

Regenerative Multi-Group Multi-Way Relaying...Regenerative Multi-Group Multi-Way Relaying Aditya Umbu Tana Amah, Student Member, IEEE, and Anja Klein, Member, IEEE Abstract—We consider

Relaying for IEEE 802.11p at Road Intersection Using a ...

IEEE 802.1Q