IEEE 802.1Q YANG Interface Framework in support of Link Aggregation (802.1AX), Security (802.1X), and CFM (802.1ag)

Size: px

Start display at page:

Download "IEEE 802.1Q YANG Interface Framework in support of Link Aggregation (802.1AX), Security (802.1X), and CFM (802.1ag)"

Quentin Casey
6 years ago
Views:

1 IEEE 80.1Q YANG Interface Framework in support of Link Aggregation (80.1AX), Security (80.1X), and CFM (80.1ag) Marc Holness Version 1.3 5July 016

2 IETF Interface Management Model IETF Interface Management Model can be represented as shown below UML-ized depiction of YANG model specified in RFC 73 Interface stack leaf nodes Marc Holness -

3 Interface Stack Diagram Representation 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 OBJECT Interface {1} INTERFACE REFERENCE Pointer or Index SHIM LAYER (e.g., Protocol Entity) SERVICE ACCESS POINT (SAP) YANG Interface definition 1 Shim/Service 1 Shim/Service {1} {} INTERFACE HIGHER & LOWER LAYER TABLE Marc Holness (mholness@ciena.com) - 3

4 Interface Stack LAG 0 {} {1,} 0 LAG 1 Member 1 Member 1 {0} {} MAC 1 MAC {0} {} Marc Holness (mholness@ciena.com) - 4

5 IEEE 80.1 Objects Within YANG Object Hierarchy IETF System Management IETF Interface Management IETF Routing 80.1Q Bridge... PAE System PAE IS-IS TPMR... IP Bridge Port... OSPF... Customer VLAN Provider Bridge Marc Holness - 5

6 Introducing the [Generic] Bridge YANG Model * bridge string name; // (1.4) r-w macaddress address; // (1.4) r-w enum type; // r-w int ports; // (1.4) r counter3 up-time; // (1.4) r int components; // r name component string name; // r-w int id; // (1.3) r-w enum type; // (1.3) r-w macaddress address; // (8.13.8, 13.4) r-w bool traffic-class-enabled; // ( ) r-w bool mmrp-enabled-status; // ( )r-w int ports; // ( ) r if-ref *bridge-port // r struct capabilities // ( ) r * The list of Bridge Ports filtering-database int aging-time; // (1.7, 8.8.3) r-w int size; // (1.7) r int static-entries; // (1.7, 8.8.1) r int dynamic-entries; // (1.7, 8.8.1) r int static-vlan-registration-entries; // (1.7, 8.8.) r int dynamic-vlan-registration-entries; // (1.7, 8.8.5) r int mac-address-registration-entries; // (1.7, 8.8.4) r * database-id, vid vlan-registration-entries int database-id; // (1.7.7) r-w int vid; // (1.7.7) r-w enum entry-type; // (1.7.7) r-w database-id, address, vid * filtering-entries int database-id; // (1.7.7) r-w macaddress address; // (1.7.7) r-w int vid; // (1.7.7) r-w enum entry-type; // (1.7.7) r-w enum status; // r port-number * port-number port-number * port-map if-ref port-number; // (8.8.1) r-w struct map; // (8.8.1) r-w * port-map if-ref port-number; // (8.8.1) r-w struct map; // (8.8.1) r-w permanent-database int size; // (1.7.6) r int static-entries; // (1.7.6) r int static-vlan-registration-entries;// (1.7.6) r database-id, address, vid * filtering-entries int database-id; // (1.7.7) r-w macaddress address; // (1.7.7) r-w int vid; // (1.7.7) r-w enum status; // r port-map if-ref port-number; // (8.8.1) r-w struct map; // (8.8.1) r-w bridge-vlan int version; // ( ) r int max-vids; // ( ) r bool override-default-pvid; // ( ) r stuct protocol-template; // ( ) r int max-msti; // ( ) r vids * vid * protocol-group-database string frame-format-type; // ( ) r-w struct frame-format; // ( ) r-w int protocol-group-id; // (6.1.) r-w vid-to-fid-allocation int *vids; // (1.10.3) r-w int fid; // (1.10.3) r-w enum allocation-type; // (1.10.3) r vlan-id int vid; // (1.10.) r-w string name; // (1.10.) r-w if-ref *untagged-ports; // (8.8., ) r if-ref *egress-ports; // (8.8.10, ) r Marc Holness (mholness@ciena.com) - 6

7 IEEE 80.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 80.1AX) case where there are many physical Ports for one Bridge Port Marc Holness (mholness@ciena.com) - 7

8 IEEE 80.1Q Bridge Port The MAC Relay Entity handles the media access methodindependent 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 Marc Holness (mholness@ciena.com) - 8

9 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 Marc Holness (mholness@ciena.com) - 9

10 Introducing the Bridge Port Interface Model type = bridge (09) interfaces string name; // r-w string description; // r-w if-type type; // r-w bool enabled; // r-w enum link-up-down-trap-enable; // r-w bridge-port * name ietf-interfaces string component-name; // r-w if-ref service-if // r-w int pvid; // (1.10.1) r-w int default-priority; // (1.6.) r-w struct priority-regeneration-table; // (1.6., 6.9.4) r-w enum pcp-selection; // (1.6., 6.9.3) r-w struct pcp-decoding-table; // (1.6.) r-w struct pcp-encoding-table; // (1.6.) r-w bool use-dei; // (1.6., 6.9.3) r-w bool drop-encoding; // (1.6., 8.6.6) r-w enum service-access-priority-selection; // (1.6., 6.13) r-w struct service-access-priority; // (1.6., ) r-w struct traffic-class-table; // (1.6.3, 8.6.6) r-w enum acceptable-frame; // ( , 6.9) r-w bool enable-ingress-filtering; // ( , 8.6.) r-w bool restricted-vlan-registration; // ( , ) r-w bool vid-translation-table; // ( , 6.9) r-w bool egress-vid-translation-table; // ( , 6.9) r-w int protocol-group-id; // (6.1.) r-w struct protocol-group-database-contents; // ( ) r-w int admin-point-to-point; // (6.8., 1.4.) r-w Interface Stack of Bridge Port * name interfaces-state string name; // r if-type type; // r enum admin-status; // r enum oper-status; // r date-time last-change; // r int3 if-index; // r address phys-address; // r if-ref * higher-layer-if; // r if-ref * lower-layer-if; // r guage64 speed; // r bridge-port bool protocol-based-vlan-classification;// (5.4.1.) r int max-vid-set-entries; // ( ) r int port-number; // (13.5, 1.4.) r enum port-type; // (1.4..1) r macaddress address; // (1.4.) r int capabilities; // (1.4., ) r int type-capabilities; // (1.4.) r bool external; // (1.4.) r bool oper-point-to-point; // (1.4.) r * * vid-translations int local-vid; // ( , 6.9) r-w int relay-vid; // ( , 6.9) r-w relay-vid local-vid egress-vid-translations int relay-vid; // ( , 6.9) r-w int local-vid; // ( , 6.9) r-w statistics date-time discontinuity-time; // r counter64 in-octets, in-unicast-pkts, in-broadcast-pkts, in-multicast-pkts; // r counter64 in-discards, in-errors, in-unknown-protos, ; // r counter64 out-octets, out-unicast-pkts, out-broadcast-pkts, out-multicast-pkts; // r counter64 out-discards, out-errors; // r bridge-port-statistics counter64 delay-exceeded-discards, mtu-exceeded-discards; // ( ) r counter64 frame-rx, octets-rx, frame-tx, octets-tx; // ( ) r counter64 discard-inbound, forward-outbound, discard-lack-of-buffers; // ( ) r counter64 discard-transit-delay-exceeded, discard-on-error; // ( ) r counter64 discard-on-ingress-filtering, discard-ttl-expired; // ( ) r Marc Holness (mholness@ciena.com) - 10

11 YANG Bridge Port Model Except augment "/ifinterfaces/ifinterface" { when "/iftype = 'ianaifbridge'{ description "Applies when a Bridge interface"; } description "Augment the interface model with the Bridge Port"; container bridge-port { leaf component-name { type dot1qtypescomponent-ref; description Used to reference configured Component nodes. ; } leaf service-if { type interface-ref; description Reference to interfaces pointed to by the Bridge Port ; } } } Marc Holness (mholness@ciena.com) - 11

Port {} 1 Bridge Port 1 {} {} MAC {1} {}

12 Interface Stack Bridge Port 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 COMPONENT Bridge Port {1} Bridge Port {} 1 Bridge Port 1 {} {} MAC {1} {} MAC {1} {} Marc Holness (mholness@ciena.com) - 1

13 Interface Stack Bridge Ports and Internal LAN BRIDGE COMPONENT BRIDGE COMPONENT Bridge Port {1} Bridge Port {} 1 {} {3} 1 Bridge Port 3 I LAN Bridge Port {} {3} 3 {1,} {} Marc Holness (mholness@ciena.com) - 13

14 Interface Stack Bridge Ports and Internal LAN BRIDGE COMPONENT Bridge Port {1} BRIDGE COMPONENT Bridge Port {} 1 {} {} 1 Bridge Port Bridge Port {} {} Marc Holness (mholness@ciena.com) - 14

15 Interface Stack Bridge Port (LAG) BRIDGE COMPONENT Bridge Port {1} 1 Bridge Port 1 {} {} LAG {1} {3,4} 3 4 {} {} 3 4 Member 1 Member {} {} MAC 1 MAC Marc Holness (mholness@ciena.com) - 15

16 Interface Stack Bridge Port (LAG) BRIDGE COMPONENT Bridge Port {} LAG {} {3,4} 3 4 {} {} 3 4 Member 1 Member {} {} MAC 1 MAC Marc Holness (mholness@ciena.com) - 16

17 Interface Stack Bridge Port with MACSec BRIDGE COMPONENT Bridge Port {1} 1 {} {} 1 Bridge Port Controlled PAE SecY {1} {3} Common 3 MAC 3 {} {} Marc Holness (mholness@ciena.com) - 17

18 Interface Stack Bridge Port with MACSec BRIDGE COMPONENT Bridge Port {} Controlled PAE SecY {} {3} Common 3 MAC 3 {} {} Marc Holness (mholness@ciena.com) - 18

19 Interface Stack Bridge Port (LAG) with MACSec BRIDGE COMPONENT Bridge Port {1} 1 {} {} 1 Bridge Port {1} {3,4} LAG Controlled Controlled 3 {} {5} PAE SecY 3 4 SecY PAE 4 {} {6} 5 {3} {} Common Common 5 6 MAC 1 MAC 6 {4} {} Marc Holness (mholness@ciena.com) - 19

20 Interface Stack Bridge Port (LAG) with MACSec BRIDGE COMPONENT Bridge Port LAG {} {1} {3,4} Controlled Controlled 3 {} {5} PAE SecY 3 4 SecY PAE 4 {} {6} 5 {3} {} Common Common 5 6 MAC 1 MAC 6 {4} {} Marc Holness (mholness@ciena.com) - 0

21 Interface Stack Bridge Port (LAG) without MACSec BRIDGE COMPONENT Bridge Port {1} 1 {} {} 1 Bridge Port {1} {3,4} LAG Controlled Controlled 3 {} {5} PAE PAC 3 4 PAC PAE 4 {} {6} 5 {3} {} Common Common 5 6 MAC 1 MAC 6 {4} {} Marc Holness (mholness@ciena.com) - 1

22 Interface Stack Bridge Port (LAG) without MACSec BRIDGE COMPONENT Bridge Port {} {1} {3,4} LAG Controlled Controlled 3 {} {5} PAE PAC 3 4 PAC PAE 4 {} {6} 5 {3} {} Common Common 5 6 MAC 1 MAC 6 {4} {} Marc Holness (mholness@ciena.com) -

23 NETCONF and YANG Example Configuration Bridge Port

24 Bridge Port <rpc message-id= 101 xmlns= urnietfparamsxmlnsyangietf-interfaces > <edit-config> <target> <running/> </target> <config> <top xmlns="http//example.com/schema/1./config"> <interface xcoperation= create > <name>if-1</name> <type>bridge</type> <interface xcoperation= create > <name>if-</name> <type>ethernetcsmacd</type> </top> </config> </edit-config> </rpc> Interface specific configuration items Marc Holness - 4

Bridge Port <rpc message-id= 101 xmlns= urnieeeparamsxmlnsyangieee-dot1q-bridge > <edit-config> <target> <running/> </target> <config> <top xmlns="http//example.com/schema/1.

25 Bridge Port <rpc message-id= 101 xmlns= urnieeeparamsxmlnsyangieee-dot1q-bridge > <edit-config> <target> <running/> </target> <config> <top xmlns="http//example.com/schema/1./config"> <bridges xcoperation= create > <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-</service-if> </bridge-port> </top> </config> </edit-config> </rpc> Interface stack tables associated with each Interface gets updated by the system Marc Holness - 5

26 NETCONF and YANG Example Configuration Bridge Port (with member LAG)

27 Bridge Port (with LAG) <rpc message-id= 101 xmlns= urnietfparamsxmlnsyangietf-interfaces > <edit-config> <target> <running/> </target> <config> <top xmlns="http//example.com/schema/1./config"> <interface xcoperation= create > <name>if-1</name> <type>bridge</type> <interface xcoperation= create > <name>if-</name> <type>ieee803adlag</type> <interface xcoperation= create > <name>if-3</name> <type>ethernetcsmacd</type> <interface xcoperation= create > <name>if-4</name> <type>ethernetcsmacd</type> </top> </config> </edit-config> </rpc> Marc Holness - 7

28 Bridge Port (with LAG) <rpc message-id= 101 xmlns= urnieeeparamsxmlnsyangieee-dot1ax > <edit-config> <target> <running/> </target> <config> <top xmlns="http//example.com/schema/1./config"> <interface> <name>if-3</name> <interface> <name>if-4</name> <interface> <name>if-</name> <members> <member>if-3</member> <member>if-4</member> </members> </top> </config> </edit-config> </rpc> LAG member specific configuration items Link Aggregation Group specific configuration items Marc Holness - 8

Bridge Port (with LAG) <rpc message-id= 101 xmlns= urnieeeparamsxmlnsyangieee-dot1q-bridge > <edit-config> <target> <running/> </target> <config> <top xmlns="http//example.com/schema/1.

29 Bridge Port (with LAG) <rpc message-id= 101 xmlns= urnieeeparamsxmlnsyangieee-dot1q-bridge > <edit-config> <target> <running/> </target> <config> <top xmlns="http//example.com/schema/1./config"> <bridges xcoperation= create > <bridge> <name>my-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-</service-if> </bridge-port> </top> </config> </edit-config> </rpc> Interface stack tables associated with each Interface gets updated by the system Marc Holness - 9

30 NETCONF and YANG Example Configuration Bridge Port (with MACSec)

31 Bridge Port (with MACSec) <rpc message-id= 101 xmlns= urnietfparamsxmlnsyangietf-interfaces > <edit-config> <target> <running/> </target> <config> <top xmlns="http//example.com/schema/1./config"> <interface xcoperation= create > <name>if-1</name> <type>bridge</type> <interface xcoperation= create > <name>if-</name> <type>macseccontrolledif</type> <interface xcoperation= create > <name>if-3</name> <type>ethernetcsmacd</type> </top> </config> </edit-config> </rpc> Marc Holness - 31

32 Bridge Port (with MACSec) <rpc message-id= 101 xmlns= urnieeeparamsxmlnsyangieee-dot1x > <edit-config> <target> <running/> </target> <config> <top xmlns="http//example.com/schema/1./config"> <system> <pae-system> <name>my-pae-system</name> </pae-system> </system> <interface> <name>if-</name> <pae-system>my-pae-system</pae-system> </top> </config> </edit-config> </rpc> PAE System specific configuration items PAE specific configuration items Marc Holness - 3

Bridge Port (with MACSec) <rpc message-id= 101 xmlns= urnieeeparamsxmlnsyangieee-dot1q-bridge > <edit-config> <target> <running/> </target> <config> <top xmlns="http//example.com/schema/1.

33 Bridge Port (with MACSec) <rpc message-id= 101 xmlns= urnieeeparamsxmlnsyangieee-dot1q-bridge > <edit-config> <target> <running/> </target> <config> <top xmlns="http//example.com/schema/1./config"> <bridges xcoperation= create > <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-</service-if> </bridge-port> </top> </config> </edit-config> </rpc> Interface stack tables associated with each Interface gets updated by the system Marc Holness - 33

34 NETCONF and YANG Example Configuration Bridge Port (with member LAG and MACSec)

35 Bridge Port (with LAG plus MACSec) <rpc message-id= 101 xmlns= urnietfparamsxmlnsyangietf-interfaces > <edit-config> <target> <running/> </target> <config> <top xmlns="http//example.com/schema/1./config"> <interface xcoperation= create > <name>if-1</name> <type>bridge</type> <interface xcoperation= create > <name>if-</name> <type>ieee803adlag</type> <interface xcoperation= create > <name>if-3</name> <type>macseccontrolledif</type> <interface xcoperation= create > <name>if-4</name> <type>macseccontrolledif</type> Marc Holness - 35

36 Bridge Port (with LAG plus MACSec) <interface xcoperation= create > <name>if-5</name> <type>ethernetcsmacd</type> <interface xcoperation= create > <name>if-6</name> <type>ieee803adlag</type> </top> </config> </edit-config> </rpc> Marc Holness - 36

37 Bridge Port (with LAG plus MACSec) <rpc message-id= 101 xmlns= urnieeeparamsxmlnsyangieee-dot1ax > <edit-config> <target> <running/> </target> <config> <top xmlns="http//example.com/schema/1./config"> <interface> <name>if-3</name> <interface> <name>if-4</name> <interface> <name>if-</name> <members> <member>if-3</member> <member>if-4</member> </members> </top> </config> </edit-config> </rpc> LAG member specific configuration items Link Aggregation Group specific configuration items Marc Holness - 37

38 Bridge Port (with LAG plus MACSec) <rpc message-id= 101 xmlns= urnieeeparamsxmlnsyangieee-dot1x > <edit-config> <target> <running/> </target> <config> <top xmlns="http//example.com/schema/1./config"> <system> <pae-system> <name>my-pae-system</name> </pae-system> </system> <interface> <name>if-3</name> <pae-system>my-pae-system</pae-system> <interface> <name>if-4</name> <pae-system>my-pae-system</pae-system> </top> </config> </edit-config> </rpc> PAE System specific configuration items PAE specific configuration items Marc Holness - 38

Bridge Port (with LAG plus MACSec) <rpc message-id= 101 xmlns= urnieeeparamsxmlnsyangieee-dot1q-bridge > <edit-config> <target> <running/> </target> <config> <top xmlns="http//example.com/schema/1.

39 Bridge Port (with LAG plus MACSec) <rpc message-id= 101 xmlns= urnieeeparamsxmlnsyangieee-dot1q-bridge > <edit-config> <target> <running/> </target> <config> <top xmlns="http//example.com/schema/1./config"> <bridges xcoperation= create > <bridge> <name>my-bridge</name> <component> <name>the-component</name> </component> </bridge> </bridges> <interface> <name>if-1</name> <bridge-port> Interface stack tables associated with each Interface gets <component-name>the-component</component-name> updated by the system <service-if>if-</service-if> </bridge-port> </top> </config> </edit-config> </rpc> Marc Holness - 39

IEEE 802.1Q YANG Interface Framework in support of Link Aggregation (802.1AX), Security (802.1X), and CFM (802.1ag)

IEEE 802.1Q YANG Interface Framework in support of Link Aggregation (802.1AX), Security (802.1X), and CFM (802.1ag) Marc Holness Version 1.4 26 July 2016 IEEE 802.1Q Bridge Port Each Bridge Port is associated