brocade 05400a yangguide

7/27/2019 Brocade 05400a YangGuide

1/112

53-1002548-02

25 September 2012

53-1002548-02

Brocade MLX Series andBrocade NetIron Family

YANG Guide

Supporting Brocade R05.4.00a


2/112

Copyright 2012 Brocade Communications Systems, Inc. All Rights Reserved.

Brocade, Brocade Assurance, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, MLX, NetIron, SAN Health, ServerIron,

TurboIron, VCS, and VDX are registered trademarks, and AnyIO, Brocade One, CloudPlex, Effortless Networking, ICX, NET Health,

OpenScript, and The Effortless Network are trademarks of Brocade Communications Systems, Inc., in the United States and/or in

other countries. Other brands, products, or service names mentioned may be trademarks of their respective owners.

Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning

any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to

this document at any time, without notice, and assumes no responsibility for its use. This informational document describesfeatures that may not be currently available. Contact a Brocade sales office for information on feature and product availability.

Export of technical data contained in this document may require an export license from the United States government.

The authors and Brocade Communications Systems, Inc. shall have no liability or responsibility to any person or entity with

respect to any loss, cost, liability, or damages arising from the information contained in this book or the computer programs that

accompany it.

The product described by this document may contain open source software covered by the GNU General Public License or other

open source license agreements. To find out which open source software is included in Brocade products, view the licensing

terms applicable to the open source software, and obtain a copy of the programming source code, please visit

http://www.brocade.com/support/oscd.

Brocade Communications Systems, Incorporated

Document History

Corporate and Latin American Headquarters

Brocade Communications Systems, Inc.130 Holger way,

San Jose, CA 95134

Tel: 1-408-333-8000

Fax: 1-408-333-8101

E-mail: [email protected]

Asia-Pacific Headquarters

Brocade Communications Systems China HK, Ltd.No. 1 Guanghua Road

Chao Yang District

Units 2718 and 2818

Beijing 100020, China

Tel: +8610 6588 8888

Fax: +8610 6588 9999


European Headquarters

Brocade Communications Switzerland Srl

Centre Swissair

Tour B - 4me tage

29, Route de l'Aroport

Case Postale 105

CH-1215 Genve 15Switzerland

Tel: +41 22 799 5640

Fax: +41 22 799 5641


Asia-Pacific Headquarters

Brocade Communications Systems Co., Ltd. (Shenzhen WFOE)

Citic Plaza

No. 233 Tian He Road North

Unit 1308 13th Floor

Guangzhou, China

Tel: +8620 3891 2000Fax: +8620 3891 2111


Title Publication number Summary of changes Date

Brocade MLX Series and Brocade

NetIron Family YANG Guide

53-1002548-02 Release 05.3.00a

document updated with

enhancements in Release

05.4.00.

25 September

2012


3/112

Brocade MLX Series and NetIron Family YANG Guide iii

Publication Number 53-000xxxx-0x

Contents

About This DocumentIn this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Document conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Notes, cautions, and danger notices . . . . . . . . . . . . . . . . . . . . . viii

Related publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Getting technical help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Chapter 1 Overview

Introduction to YANG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 2 Common Definitions and Headers

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Common definition and header elements. . . . . . . . . . . . . . . . . . . . . . 3

NetIron configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

NetIron state data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Device version state data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

RPC delete operation example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 3 Interface Configuration

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19


4/112

iv Brocade MLX Series and NetIron Family YANG Guide


Interface configuration elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Interface identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Alarm monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Admin status choice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Gig default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Layer 2 switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Drop precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Loop detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Load interval. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Source guard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Speed duplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

IPv4 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

IPv6 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Interface state elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Full examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

operation examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

operation example. . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 4 MPLS Configuration

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

MPLS configuration elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

MPLS priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

MPLS traffic engineering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

MPLS path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

MPLS LSP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

MPLS RSVP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Router MPLS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

MPLS state elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Full examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

operation examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

operation example. . . . . . . . . . . . . . . . . . . . . . . . . 88

Chapter 5 VLAN Configuration

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91

VLAN configuration elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

VLAN identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91VLAN name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Tagged ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Untagged ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Uplink ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Router interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

Loop detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

VLAN accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

VLAN CPU protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94


5/112

Brocade MLX Series and NetIron Family YANG Guide v


VLAN state elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Full examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97


6/112

vi Brocade MLX Series and NetIron Family YANG Guide



7/112

Brocade MLX Series and NetIron Family YANG Guide vii


About This Document

In this chapter

Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiSupported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiDocument conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiRelated publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiGetting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Audience

This document is designed for system administrators with a working knowledge of Layer 2 and

Layer 3 switching and routing.

Supported hardware and software

This guide describes the YANG models supported in this software release of the NetIron devices.

The following hardware platforms support the YANG models described in this guide: Brocade NetIron CER Brocade NetIron CES Brocade NetIron XMR Brocade MLX series

Document conventions

This section describes text formatting conventions and important notice formats used in this

document.


8/112

viii Brocade MLX Series and NetIron Family YANG Guide


In this chapter

Text formatting

The narrative-text formatting conventions that are used are as follows:

For readability, command names in the narrative portions of this guide are presented in bold; for

example, show version.Notes, cautions, and danger notices

The following notices and statements are used in this manual. They are listed below in order of

increasing severity of potential hazards.

NOTEA note provides a tip, guidance or advice, emphasizes important information, or provides a reference

to related information.

CAUTIONA Caution statement alerts you to situations that can be potentially hazardous to you or causedamage to hardware, firmware, software, or data.

DANGERA Danger statement indicates conditions or situations that can be potentially lethal or extremelyhazardous to you. Safety labels are also attached directly to products to warn of these conditionsor situations.

Related publications

The Brocade MLX Series and Brocade NetIron Family Configuration Guide supplements the

information in this guide.

bold text Identifies command namesIdentifies the names of user-manipulated GUI elements

Identifies keywords

Identifies text to enter at the GUI or CLI

italic text Provides emphasis

Identifies variables

Identifies document titles

code text Identifies CLI output


9/112

Brocade MLX Series and NetIron Family YANG Guide ix


In this chapter

NOTEFor the latest edition of this document, which contains the most up-to-date information, see Product

Manuals at brocade.com.

Getting technical help

To contact Technical Support, go to http://www.brocade.com/services-support/index.page for the

latest e-mail and telephone contact information.


10/112

x Brocade MLX Series and NetIron Family YANG Guide


In this chapter


11/112

Brocade MLX Series and NetIron Family YANG Guide 1


Chapter

1Overview

Introduction to YANG

YANG is a data modeling language. The language is used to model the supported configuration and

state data manipulated by the Network Configuration (NETCONF) protocol and NETCONF remote

procedure calls (RPCs). For more information on NETCONF, refer to the Brocade MLX Series and

Brocade NetIron Family Configuration Guide.

Each block of YANG data is encapsulated as a module containing a header information, linkage

statements, meta information, revision history, and module definitions. Modules can contain one

or more submodules with the same structure. The following code example shows the structure of a

header statement, along with linkage and meta information (which typically contains contactinformation and a high-level description of the module).

modul e common- def s{

namespace "htt p: / / br ocade. com/ ns/ net conf / conf i g/ net i r on- conf i g/ ";pref i x " common" ;

or gani zat i on"Br ocade Communi cat i ons I nc. " ;

cont act"Techni cal Suppor t Center "+"130 Hol ger Way, "+"San J ose, CA 95134"+

"Emai l : i psupport @brocade. com"+"Phone: 1- 800- 752- 8061"+"URL: www. br ocade. com";

descr i pti on "Thi s modul e def i nes t he common def i ni t i ons. VERSI ON: " ;

r evi si on 2011- 04- 20{

descr i pt i on " I ni t i al revi s i on" ;}

}

NOTEThe YANG model does not perform data allocation or NETCONF protocol operations. Refer to theBrocade MLX Series and Brocade NetIron Family Configuration Guide for more information on these

topics.

For the most recent YANG models, visit http://my.brocade.com.
http://my.brocade.com/http://my.brocade.com/


12/112

2 Brocade MLX Series and NetIron Family YANG Guide


Introduction to YANG


13/112



Chapter

2Common Definitions and Headers

In this chapter

Common definition and header elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3NetIron configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Device version state data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9RPC delete operation example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Common definition and header elementsThe following YANG model contains the common type definitions and the common objects used by

the other YANG models.

NOTEFor the most recent YANG models, visit http://my.brocade.com.

modul e common- def s{

namespace "htt p: / / br ocade. com/ ns/ net conf / conf i g/ net i r on- conf i g/ ";pref i x " common" ;

or gani zat i on

"Br ocade Communi cat i ons I nc. " ;

cont act"Techni cal Suppor t Center "+"130 Hol ger Way, "+"San J ose, CA 95134"+"Emai l : i psupport @brocade. com"+"Phone: 1- 800- 752- 8061"+"URL: www. br ocade. com";

descr i pti on "Thi s modul e def i nes t he common def i ni t i ons. VERSI ON: " ;

r evi si on 2011- 04- 20{


t ypedef i nt erf ace- al l - t ypes{

t ype str i ng{

pat t er n"et her net\ s+\ d{1, 2}/ \ d{1, 2}| "+"et her net\ s+\ d{1, 2}/ \ d{1, 2}\ s+t o\ d{1, 2}/ \ d{1, 2}| "+"pos\ s+\ d{1, 2}/ \ d{1, 2}| "+


14/112



Common definition and header elements

"pos\ s+\ d{1, 2}/ \ d{1, 2}\ s+t o\ d{1, 2}/ \ d{1, 2}| "+"ve\ s+\ d| "+"l oopback\ s+\ d| "+"management \ s+\ d| "+"t unnel \ s+\ d";

l engt h "4. . 100";}descri pt i on

"Si ngl e or r ange of i nt er f aces "+"Format i s et her enet SLOT/ PORT or "+"et her ent SLOT/ PORT t o SLOT/ PORT "+"pos SLOT/ PORT "+"pos SLOT/ PORT t o SLOT/ PORT "+"ve ve_i d "+"l oopback l oopback_i d (1 t o 64) "+"management mgmt _i d (1 or 2) "+"t unnel r unnel _i d";

}

t ypedef i nt er f ace- et h- pos- ve- mul t i pl e{t ype str i ng{

pat t er n"et her net\ s+\ d{1, 2}/ \ d{1, 2}| "+"et her net\ s+\ d{1, 2}/ \ d{1, 2}\ s+t o\ d{1, 2}/ \ d{1, 2}| "+"pos\ s+\ d{1, 2}/ \ d{1, 2}| "+"pos\ s+\ d{1, 2}/ \ d{1, 2}\ s+t o\ d{1, 2}/ \ d{1, 2}| "+"ve\ s+\ d";

l engt h "4. . 100";

}descri pt i on

"Si ngl e or r ange of i nt er f aces "+

"Format i s et her enet SLOT/ PORT or "+"et her ent SLOT/ PORT t o SLOT/ PORT "+"pos SLOT/ PORT "+"pos SLOT/ PORT t o SLOT/ PORT "+"ve ve_i d";

}

t ypedef i nt erf ace- et h- pos- ve- si ngl e{

t ype str i ng{

pat t er n"et her net\ s+\ d{1, 2}/ \ d{1, 2}| "+"pos\ s+\ d{1, 2}/ \ d{1, 2}| "+

"ve\ s+\ d";l engt h "4. . 100";

}descri pt i on

"Si ngl e or r ange of i nt er f aces "+"Format i s et her enet SLOT/ PORT or "+"pos SLOT/ PORT "+"ve ve_i d";

}


15/112



Common definition and header elements 2t ypedef et hernet - i nt f - si ngl e{

t ype str i ng{

patt er n "et hernet \ s+\ d{1, 2}/ \ d{1, 2}";l engt h "11. . 20";

}descri pt i on "Si ngl e et her net i nt er f ace";

}

t ypedef et hernet - pos- i nt f - si ngl e{

t ype str i ng{

pat t er n"et hernet \ s+\ d{1, 2}/ \ d{1, 2}| "+"pos\ s+\ d{1, 2}/ \ d{1, 2}";

l engt h "11. . 20";}descri pt i on "Si ngl e et her net or pos i nt er f ace";

}

t ypedef ve- i nt f - s i ngl e{

t ype str i ng{

patt er n "ve\ s+\ d";l engt h "4. . 20";

}descri pt i on "VE i nt er f ace";

}

t ypedef et hernet - i nt f - mul t i pl e{

t ype str i ng

{pat t er n

"et her net\ s+\ d{1, 2}/ \ d{1, 2}| "+"et her net\ s+\ d{1, 2}/ \ d{1, 2}\ s+t o\ d{1, 2}/ \ d{1, 2}";

l engt h "11. . 50";}descri pt i on "Mul t i pl e et her net i nt er f aces";

}

t ypedef et hernet - pos- i nt f - mul t i pl e{

t ype str i ng{

pat t er n

"et her net\ s+\ d{1, 2}/ \ d{1, 2}| "+"et her net\ s+\ d{1, 2}/ \ d{1, 2}\ s+t o\ d{1, 2}/ \ d{1, 2}| "+"pos\ s+\ d{1, 2}/ \ d{1, 2}| "+"pos\ s+\ d{1, 2}/ \ d{1, 2}\ s+t o\ d{1, 2}/ \ d{1, 2}";

l engt h "7. . 50";}descri pt i on "Mul t i pl e et her net or pos i nt er f aces";

}

t ypedef vl an- i dent i f i er{


16/112



Common definition and header elements

t ype ui nt 32{

r ange "1. . 4090";}descri pt i on "VLAN I dent i f i er" ;

}

t ypedef i pv4_addr ess{

t ype str i ng{

l engt h "7. . 15";}descr i pt i on "I Pv4 Addr ess" ;

}

t ypedef i pv6_addr ess{

t ype str i ng{

l engt h "3. . 39";}descr i pt i on "I Pv6 Addr ess" ;

}

t ypedef i pv4_address_mask{

t ype str i ng{

l engt h "9. . 19";}descr i pt i on "I Pv4 Addr ess/ mask";

}

t ypedef i pv6_address_mask

{t ype str i ng{

l engt h "6. . 43";}descr i pt i on "I Pv6 Addr ess/ mask";

}

t ypedef mac_address{

t ype str i ng{

l engt h "1. . 21";

}descr i pt i on "Et hernet MAC address" ;}t ypedef pri ori t y- val ue{

t ype ui nt 32{

r ange "0. . 7";}descri pt i on "Pri or i t y Val ue";

}


17/112



NetIron configuration file 2

gr oupi ng pr i or i t y-groupi ng{

descri pt i on "Pr i or i t y";cont ai ner pr i or i t y{

descri pt i on "Pr i or i t y";l eaf val ue{

t ype pr i or i t y- val ue;descri pt i on "Pr i or i ty val ue";

}l eaf f orce{

t ype empt y;descri pt i on "Pr i or i ty f orce";

}}

}

}

NetIron configuration file

The following YANG model defines the header information, linkage statements, meta information,

and the revision history for the NetIron configuration group.


modul e neti r on- conf i g{

namespace "htt p: / / br ocade. com/ ns/ net conf / conf i g/ net i r on- conf i g/ ";pref i x "br cd";

i ncl ude common- def s;i ncl ude vl an- conf i g;i ncl ude i nt erf ace- conf i g;i ncl ude mpl s- conf i g;




descri pt i on"Net I r on Conf i g modul e. VERSI ON: " ;

r evi si on 2011- 04- 20{descr i pt i on " I ni t i al revi s i on" ;


18/112



NetIron state data

}gr oupi ng net i r on- conf i g{

descri pt i on "Net I r on conf i gur at i on gr oup";cont ai ner net i r on- conf i g{

descri pt i on "Net I r on conf i gur at i on";uses vl an- conf i g- gr oupi ng;uses i nt er f ace- conf i g- gr oupi ng;uses mpl s- conf i g- gr oupi ng;

}}

}

NetIron state data

The following YANG model contains the state data for the NetIron device.


modul e neti r on- st atedata{

namespace "htt p: / / br ocade. com/ ns/ net conf / conf i g/ net i r on- conf i g/ ";pref i x "st at edat a";

i ncl ude vl an- st at edat a;i ncl ude i nt er f ace- st at edat a;i ncl ude mpl s- st at edat a;



descri pt i on"NetI r on devi ce st ate dat a modul e. VERSI ON: " ;

r evi si on 2011- 04- 20{descr i pt i on " I ni t i al revi s i on" ;

}

gr oupi ng net i r on- st at edata{

descr i pt i on "NetI r on devi ce st at e data gr oup";cont ai ner net i r on- st at edat a{

descri pt i on "Net I r on devi ce state dat a";conf i g f al se;

uses vl an- st atedat a- gr oupi ng;


19/112



Device version state data 2uses i nt er f ace- st at edat a- gr oupi ng;uses mpl s- st atedata- groupi ng;

}}

}

Device version state data

The following YANG model contains the state data for the device version.


submodul e ver si on- st atedat a{

bel ongs- t o net i r on- st at edat a{

pref i x "st at edat a";

}

i mport common- def s{

pref i x " common" ;}




descr i pt i on "Thi s modul e def i nes t he devi ce ver si on st ate dat a. VERSI ON: ";

r evi si on 2011- 04- 20{


gr oupi ng devi ce- i d- gr oupi ng{

l eaf ser i al{

t ype st ri ng{

l engt h 1. . 20;}descr i pt i on "devi ce seri al number" ;

}

l eaf par t{

t ype st ri ng


20/112




{l engt h 1. . 20;

}descri pti on "devi ce par t number" ;

}}

gr oupi ng sof t ware- ver si on- gr oupi ng{

l eaf versi on{

t ype st ri ng{

l engt h 1. . 63;}descri pt i on "I mage ver si on. ";

}

l eaf compi l ed- on{

t ype st ri ng{l engt h 1. . 127;

}descri pti on "The i mage compi l ati on date and t i me. ";

}

l eaf l abel{

t ype st ri ng{

l engt h 1. . 15;}descri pt i on "The i mage l abel . . ";

}

l eaf l engt h{

t ype ui nt 32{

r ange " 0. . 4294967295" ;}descr i pt i on "The i mage l engt h. ";

}

l eaf sour ce{

t ype st ri ng{

l engt h 1. . 63;}descr i pt i on "The boot sour ce";

}}

gr oupi ng f l ash- gr oupi ng{

l eaf f l ash- s i ze{

t ype ui nt 32


21/112



Device version state data 2{

r ange " 0. . 4294967295" ;}descri pt i on "The f l ash si ze. ";

}

l eaf f l ash- name{

t ype st ri ng{

l engt h "1. . 31";}descr i pt i on "The f l ash name. ";

}}

gr oupi ng l i cense- gr oupi ng{

descri pt i on "Sof t war e Li cense I d";l eaf sof t ware- packagi ng- t ype

{ t ype st ri ng{

l engt h 1. . 31;}descri pti on "Sof t ware Packagi ng Type" ;

}l eaf l i cense- i d{

t ype st ri ng{

l engt h 1. . 11;}descri pt i on "devi ce l i cense i dent i f i er" ;

}

}

gr oupi ng ver si on- st at edata- gr oupi ng{

descri pt i on "devi ce ver si on state dat a";cont ai ner ver si on- st at edat a{

l eaf system{

t ype str i ng{

l engt h 1. . 127;}descr i pt i on "Syst em model / pr oduct / chassi s t ype";

}

l eaf chassi s- mode{

t ype str i ng{

l engt h 1. . 16;}descr i pt i on "Chassi s mode (XMR/ MLX) " ;

}


22/112




cont ai ner s yst em- i d{

descri pt i on "SystemI denti f i er" ;uses devi ce- i d- gr oupi ng;

}

cont ai ner f actory-i d{

descri pt i on "Syst em Factory I dent i f i er ";uses devi ce- i d- gr oupi ng;

}

cont ai ner l i cense{

descri pt i on "Sof t war e Li cense I d";uses l i cense-gr oupi ng;

}

l eaf cpl d- versi on{

t ype ui nt 8{r ange "0. . 255";

}descr i pt i on "The CPLD Versi on. ";

}

l eaf mi cro- contr ol l er- versi on{

t ype ui nt 8{

r ange "0. . 255";}descri pt i on "The Mi cro Cont r ol l er Ver si on. ";

}

l eaf pbi f - vers i on{

t ype ui nt 8{

r ange "0. . 255";}descr i pt i on "The PBI F Versi on ( 0 = not r eady). ";

}

cont ai ner daught er - boar d- i d{

descr i pti on "Daught er Boar d" ;uses devi ce- i d- gr oupi ng;

}

l i st modul e{

key "modul e- name";descr i pt i on "The modul e name (CER has onl y 1 modul e) . " ;l eaf modul e- name{

t ype str i ng{

l engt h 1. . 256;


23/112



Device version state data 2}descr i pt i on "Modul e name";

}

l eaf modul e- st at e{

t ype str i ng{

l engt h 1. . 16;}descri pt i on "Modul e stat e ( i f down) ";

}

cont ai ner modul e- i d{

descri pt i on "Modul e I dent i f i er" ;uses devi ce- i d- gr oupi ng;

}

l i st f e

{ key "f e- i d";descr i pt i on "The FE";l eaf f e- i d{

t ype ui nt 8{

r ange 1. . 16;}descri pt i on "FE i d";

}l eaf f e- type{

t ype ui nt 32{

r ange 1. . 1048575;}descri pt i on "FE t ype";

}

l eaf f e- ver{

t ype ui nt 8{

r ange 1. . 16;}descri pt i on "FE ver si on";

}}

cont ai ner modul e- l i cense{

descri pt i on "Sof t war e Li cense I d";uses l i cense- gr oupi ng;

}

cont ai ner sof t war e- ver si on{

descr i pt i on "Sof t war e Versi ons";cont ai ner boot


24/112




{descr i pt i on "Boot I mage Sof t ware Vers i ons" ;uses sof t ware- ver si on- gr oupi ng;

}cont ai ner moni t or{

descr i pt i on "Moni t or I mage Sof t ware Versi ons" ;uses sof t ware- ver si on- gr oupi ng;

}cont ai ner i r onwar e{

descr i pt i on " I r onware I mage Sof t ware Vers i ons" ;uses sof t ware- ver si on- gr oupi ng;

}}

l eaf f pga- versi ons{

t ype ui nt 8{

r ange "0. . 255";}descr i pt i on "The FPGA Versi on. ";

}

cont ai ner mac- st r i ng- cont ai ner{

descr i pt i on "MAC st r i ng cont ai ner" ;l eaf - l i s t mac-s t r i ng- l i s t{

descr i pt i on "The MAC st r i ng. ";t ype str i ng{

l engt h "1. . 15";}

}}

cont ai ner pr ocessor{

l eaf processor- speed{

t ype ui nt 32{

r ange " 0. . 4294967295" ;}descr i pt i on "The Pr ocessor Speed (MHz) " ;

}

l eaf pr ocessor - t ype{t ype str i ng{

l engt h "1. . 5";}descr i pt i on "Pr ocessor Type";

}

l eaf processor- revi si on{


25/112



Device version state data 2t ype ui nt 32{

r ange " 0. . 4294967295" ;}descri pt i on "Processor r evi si on";

}

l eaf bus- speed{

t ype ui nt 32{

r ange " 0. . 4294967295" ;}descr i pt i on "The Bus Speed ( MHz) " ;

}}

cont ai ner boot - f l ash{

descri pt i on "Boot Fl ash";

uses f l ash- gr oupi ng;}

cont ai ner code- f l ash{

descr i pt i on "Code Fl ash";uses f l ash- gr oupi ng;

}

l eaf dr am- si ze{

t ype ui nt 32{

r ange " 0. . 4294967295" ;}

descri pt i on "The DRAM si ze. ";}

l eaf sram- si ze{

t ype ui nt 32{

r ange " 0. . 4294967295" ;}descri pt i on "The SRAM si ze. ";

}

l eaf br am- si ze{

t ype ui nt 32{r ange " 0. . 4294967295" ;

}descri pt i on "The BRAM si ze. ";

}

cont ai ner dma- cont ai ner{

descr i pt i on "DMA i nf or mati on cont ai ner . ";l i s t dma- l i s t


26/112



RPC delete operation example

{key "ppcr- i d";descr i pt i on "The DMA i nf ormati on cont ai ner. ";l eaf ppcr - i d{

t ype ui nt 32

{r ange "0. . 4294967295";

}descr i pt i on "The PPCR I d. ";

}l eaf cam- si ze{

t ype ui nt 32{

r ange "0. . 4294967295";}descri pt i on "The CAM si ze ( K ent r i es) ";

}l eaf pr am- si ze

{ t ype ui nt 32{

r ange "0. . 4294967295";}descri pt i on "The PRAM si ze ( K ent r i es) ";

}l eaf age- r am- si ze{

t ype ui nt 32{

r ange "0. . 4294967295";}descr i pt i on "The AGE RAM si ze ( K ent r i es) ";

}

}}

l eaf syst em- upti me{

t ype str i ng{

l engt h "1. . 63";}descr i pt i on "System Upt i me";

}}

}}

}


The following example shows the RPC request and response for a delete operation.


27/112



RPC delete operation example 2

et her net 1/ 1]] >] ] >

]] >] ] >


28/112





29/112



Chapter

3Interface Configuration

In this chapter

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Interface configuration elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Interface state elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Full examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

OverviewThis chapter describes the interface components that provide support for configuring the network

interfaces, both link-level (including VLAN-tagged interfaces) and IP addresses (IPv4 and IPv6).


Interface configuration elements

Each element of the interface corresponds to the following:

A YANG model description An XML description A CLI descriptionThe following subsections compare a specific example for each interface configuration element.

Interface identifier

The interface identifier is a restricted integer type that behaves as a unique identifier for single or a

group of interfaces. This element is an edit request for an Ethernet interface and a VE interface and

disables each port.

TABLE 1 Interface identifierYANG model XML CLI

leaf interface-id

{

type interface-all-types;

description "Single or group of

interfaces";

}

ethernet 1/1

ve 2

interface ethernet/


30/112




Alarm monitoring

This data element indicates whether or not alarm monitoring is enabled. This data element only

applies to 10 GbE interfaces previously configured in the WAN PHY mode.

Admin status choice

This data element is used to enable or disable the interface.

TABLE 2 Alarm monitoringYANG model XML CLI

leaf alarm-monitoring

{

type empty;

description "Enable alarm monitoring";

}

[no] alarm-monitoring

TABLE 3 Admin status choiceYANG model XML CLI

choice admin-status-choice

{

description "Enable/Disable the Interface";

case enable

{

leaf enable

{

type empty;

description "Enable the Interface";

}

}

enable

case disable

{

leaf disable

{

type empty;

description "Disable the Interface";

}

}

}

disable


31/112



Interface configuration elements 3Gig default

This data element indicates the Gigabit negotiation modes.

TABLE 4 Gig defaultYANG model XML CLI

container gig-default

{

description "Global Gig port default options";

choice gig-default-option

{

description "Gig default type";

case auto-gig

{

leaf auto-gig

{

type empty;

description "Autonegotiation";

}

}

case neg-off

{

leaf neg-off

{

type empty;

description "Non-Autonegotiation";

}

}

case auto-full

{

leaf auto-full

{type empty;

description " Full Autonegotiation";

}

}

case neg-full-auto

{

leaf neg-full-auto

{

type empty;

description "Autonegotiation first, "+

"if failed try non-autonegotiation";

}

}}

}

[no] gig-default auto-gig | neg-off |auto-full | neg-full-auto


32/112




Layer 2 switching

This data element indicates whether or not Layer 2 switching is enabled.

Drop precedence

This data element indicates the Quality of Service (QoS) drop precedence value.

TABLE 5 Layer 2 switchingYANG model XML CLI

leaf route-only

{

type empty;

description "Enable Layer 2 switching";

}

[no] route-only

TABLE 6 Drop precedenceYANG model XML CLI

container drop-precedence

{

description "QOS drop precedence";

leaf value

{

type uint32

{

range "0..3";

}

description "Drop precedence value";

}

leaf force{

type empty;

description "Drop precedence force";

}

}

0

[no] drop-precedence

[no] drop-precedence force


33/112



Interface configuration elements 3Loop detection

This data element indicates whether or not loop detection is enabled.

Load interval

This data element indicates the time of the load interval during which the average byte and packetrates are calculated. The time can be configured in multiples of 30 seconds in the range from 30

through 300 seconds. The default value of the load interval is 300 seconds.

TABLE 7 Loop detectionYANG model XML CLI

container loop-detection

{

description "Shutdown this port if receiving "+

"packets originated from this port";

leaf vlan

{

type vlan-identifier;

description "Loop detection for this vlan";

}

leaf shutdown-disable

{

type empty;

description "Disable shutdown by "+

"loop detection";

}

leaf shutdown-sending-port

{

type empty;

description "Shutdown the sending port";

}

}

2

[no] loop-detection [vlan]

loop-detectionshutdown-disable

[no] loop-detectionshutdown-sending-port

TABLE 8 Load intervalYANG model XML CLI

leaf load-interval

{

type uint32

{

range "30..300";

}

units "Seconds";

description "Load interval, multiple of 30";

}

30 [no] load-interval


34/112




Source guard

This data element indicates whether or not the port is set as an IP source guarded port.

NOTEThis data element is supported only on Brocade MLX series and Brocade NetIron XMR platforms.

.

Flow control

This data element indicates the flow control status on full-duplex ports on a system.

Speed duplex

This data element sets the port speed of an interface.

TABLE 9 Source guardYANG model XML CLI

leaf source-guard

{

type empty;

description "Enable/ IP source guard";

}

[no] source-guard

TABLE 10 Flow controlYANG model XML CLI

leaf flow-control

{

type empty;

description "Enable 802.3 flow control "+

"on full duplex port";

}

[no] flow-control

TABLE 11 Speed duplexYANG model XML CLI

leaf speed-duplex

{

type interface_speed_duplex;

description "Speed duplex for this interface";

}

auto

1000-master

1000-slave

1000-full

1000-half

100-full

100-half10-full

10-half

[no] speed-duplex


35/112



Interface configuration elements 3IPv4 configuration

This data element indicates the IPv4 address of an interface.

IPv6 configurationThis data element indicates if IPv6 is enabled on this interface and the IPv6 address of the

interface.

TABLE 12 IPv4 configurationYANG model XML CLI

container ip

{

description "Interface IPv4 configuration";

leaf address

{

type ipv4_address_mask;

description "IPv4 address";

}

}

1.1.1.1/24

[no] ip address/

TABLE 13 IPv6 configurationYANG model XML CLI

container ipv6

{

description "Interface IPv6 configuration";

leaf address

{

type ipv6_address_mask;

description "IPv6 address";}

leaf enable

{

type empty;

description "Enable IPv6 on this interface";

}

}

::1/32

[no] ipv6 address /

[no] ipv6 enable


36/112



Interface state elements


The following is the YANG model for the Interface state data elements.


submodul e i nt erf ace- st atedat a{

bel ongs- t o net i r on- st at edat a{

pref i x "st at edat a";}





descr i pt i on "Thi s modul e def i nes t he devi ce i nt erf ace stat e data. VERSI ON: ";

r evi si on 2011- 04- 20{

descr i pt i on " I ni t i al revi s i on" ;}gr oupi ng i nt er f ace- st at edat a- gr oupi ng{

descri pt i on "devi ce i nt er f ace state dat a gr oup";cont ai ner i nt er f ace- st at edat a{

descri pt i on "Li st of i nt er f ace conf i gur ed on the syst em";

l i st i nt er f ace{

key i nt er f ace- i d;descri pt i on "devi ce i nt er f ace st at e dat a";

l eaf i nter f ace- i d{

t ype common: i nt er f ace- al l - t ypes;descri pt i on "The i nt er f ace i dent i f i er i ncl udi ng chassi s sl ot

and port number" ;}

choi ce l i nk- stat e{

descri pt i on "The stat e of t he l i nk";


37/112



Interface state elements 3

case up{

l eaf up{

t ype empt y;

descri pt i on "The l i nk i s up";}

}case down{

l eaf down{

t ype empt y;descri pt i on "The l i nk i s down";

}}

}

choi ce l 2- state

{ descri pt i on "The L2 st at e f or t he por t ";

case di sabl ed{

l eaf di sabl ed{

t ype empt y;descri pt i on "The L2 st at e i s di sabl ed";

}}case bl ocked{

l eaf bl ocked{

t ype empt y;descri pt i on "The L2 st at e i s bl ocked";

}}case l i steni ng{

l eaf l i s teni ng{

t ype empt y;descri pt i on "The L2 state i s l i steni ng";

}}case l earni ng{

l eaf l earni ng{t ype empt y;descri pt i on "The L2 st at e i s l ear ni ng";

}}case pref orwardi ng{

l eaf pr ef or war di ng{

t ype empt y;


38/112




descr i pt i on "The L2 st ate i s pr ef or wardi ng";}

}case f orward{

l eaf f or war d

{t ype empt y;descri pt i on "The L2 state i s f or war d";

}}case none{

l eaf none{

t ype empt y;descr i pt i on "The L2 st ate i s none";

}}case l k-di sabl e

{ l eaf l k- di sabl e{

t ype empt y;descr i pt i on "The L2 st ate i s LK- DI SABLE";

}}case oam- di sabl e{

l eaf oam- di sabl e{

t ype empt y;descr i pti on "The L2 state i s OAM- DI SABLE";

}}

case dot1x- bl ocked{

l eaf dot 1x-bl ocked{

t ype empt y;descr i pt i on "The L2 st at e i s DOT1X- BLOCKED" ;

}}case l acp- bl ocked{

l eaf l acp- bl ocked{

t ype empt y;descr i pti on "The L2 st ate i s LACP- BLOCKED";

}}case chdl c- down{

l eaf chdl c- down{

t ype empt y;descr i pt i on "The L2 st at e i s cHDLC- DOWN";

}}case ppp- down


39/112



Interface state elements 3{

l eaf ppp- down{

t ype empt y;descr i pti on "The L2 st ate i s PPP- DOWN";

}

}case i nacti ve{

l eaf i nact i ve{

t ype empt y;descri pt i on "The L2 st at e i s i nacti ve";

}}

}

choi ce dupl ex{

descr i pt i on "The dupl ex mode of t he i nter f ace" ;

case hal f{

l eaf hal f {

t ype empt y;descri pt i on "Hal f Dupl ex";

}}case f ul l{

l eaf f ul l{

t ype empt y;descri pt i on "Ful l Dupl ex";

}}case none{

l eaf none{

t ype empt y;descr i pt i on "None";

}}

}

l eaf speed{

t ype str i ng{l engt h "1. . 6";

}descr i pt i on "The bandwi dt h of t he i nt erf ace";

}

l eaf t r unk- i d{

t ype str i ng{


40/112




l engt h "1. . 6";}descri pt i on "The t r unk- i d";

}

choi ce tag-mode

{descr i pt i on "The t ag mode of t he i nt er f ace";

case yes{

l eaf yes{

t ype empt y;descri pt i on "Yes";

}}case no{

l eaf no

{ t ype empt y;descri pt i on "No";

}}case na{

l eaf na{

t ype empt y;descri pt i on "N/ A";

}}

}

choi ce pr i or i t y- l evel{

descri pt i on "The pri or i t y l evel ";

case l evel 0{

l eaf l evel 0{

t ype empt y;descri pt i on "Level 0";

}}case l evel 1{

l eaf l evel 1{t ype empt y;descri pt i on "Level 1";

}}case l evel 2{

l eaf l evel 2{

t ype empt y;


41/112



Interface state elements 3descri pt i on "Level 2";

}}case l evel 3{

l eaf l evel 3

{t ype empt y;descri pt i on "Level 3";

}}case l evel 4{

l eaf l evel 4{


}}case l evel 5

{ l eaf l evel 5{


}}case l evel 6{

l eaf l evel 6{


}}

case l evel 7{

l eaf l evel 7{


}}

}

l eaf mac- address{

t ype common: mac_address ;descr i pt i on "The MAC address of t he i ntef ace" ;

}

l eaf name{

t ype str i ng{

l engt h "1. . 256";}descri pt i on "The f ul l por t name of t he i nt er f ace";

}


42/112



Full examples

}

}

}

}

Full examples

The following shows the complete YANG model for interface configuration, as well as example RPC

requests and responses.


submodul e i nt erf ace- conf i g{

bel ongs- t o net i ron- conf i g{

pref i x brcd;}



or gani zat i on



descr i pt i on "Thi s modul e def i nes t he I nt erf ace conf i gur at i on. VERSI ON: ";

r evi si on 2011- 04- 20{


t ypedef i nter f ace_speed_dupl ex{

t ype enumerat i on{

enumaut o{

val ue "0";descri pt i on "Aut onegot i at i on";

}enum 10- f ul l


43/112



Full examples 3{

val ue "1";descri pt i on "10M, f ul l dupl ex";

}enum 10- hal f{

val ue "2";descr i pt i on "10M, hal f dupl ex";

}enum 100- f ul l{

val ue "3";descri pt i on "100M, f ul l dupl ex";

}enum 100- hal f{

val ue "4";descr i pt i on "100M, hal f dupl ex";

}enum 1000- f ul l

{ val ue "5";descri pt i on "1G, f ul l dupl ex";

}enum1000- hal f{

val ue "6";descri pt i on "1G, hal f dupl ex";

}enum 1000- mast er{

val ue "7";descr i pt i on "1G, master ";

}enum1000- sl ave

{val ue "9";descr i pt i on "1G, sl ave. The 1000- sl ave speed dupl ex i s"

+ " appl i cabl e onl y f or CES/ CER devi ses";}

}descr i pt i on "Speed dupl ex";

}

gr oupi ng i nt er f ace- conf i g- gr oupi ng{

descri pt i on "I nt er f ace conf i gur at i on gr oup";cont ai ner i nt er f ace- conf i g

{descri pt i on "I nt er f ace conf i gurati on";l i st i nt er f ace{

key i nt er f ace- i d;descri pt i on "Li st of I nt er f aces conf i gur ed "+

"on t he syst em";l eaf i nter f ace- i d{

t ype i nt er f ace- al l - t ypes;descri pt i on "Si ngl e or group of i nt er f aces";


44/112



Full examples

}

l eaf al ar m- moni t or i ng{

t ype empt y;descri pt i on "Enabl e al ar m moni t or i ng";

}

choi ce admi n- st atus- choi ce{

descr i pt i on "Enabl e/ Tear down t he LSP";

case enabl e{

l eaf enabl e{

t ype empt y;descr i pt i on "Enabl e the LSP";

}}

case di sabl e{l eaf di sabl e{

t ype empt y;descr i pti on "Tear down the LSP";

}}

}

cont ai ner gi g- def aul t{

descri pt i on "Gl obal Gi g por t def aul t opt i ons";choi ce gi g- def aul t - opt i on{

descri pt i on "Gi g def aul t t ype";case aut o-gi g{

l eaf auto-gi g{

t ype empt y;descri pt i on "Aut onegot i at i on";

}}case neg- of f{

l eaf neg- of f{

t ype empt y;

descr i pt i on "Non- Aut onegot i at i on";}}case aut o- f ul l{

l eaf auto-f ul l{

t ype empt y;descri pt i on " Ful l Aut onegot i at i on";

}}


45/112


46/112


47/112



Full examples 3

}

}

}

The following example shows the RPC request and response of an operation.

2ether net 1/ 6 t o 1/ 8
ve 2

et her net 1/ 1
1. 1. 1. 1/ 242000: 0: 0: 1: : 1/ 64

300

et her net 1/ 2
1. 1. 12. 1/ 242000: 0: 0: 12: : 1/ 64

300


48/112


49/112



Full examples 3

ve 2

1. 1. 2. 1/ 242000: 0: 0: 2: : 1/ 64]] >] ] >


50/112


51/112


52/112


53/112


54/112


55/112


56/112


57/112


58/112



Full examples

748e. f 811. 8190

et her net 1/ 17

748e. f 811. 8191

et her net 1/ 18

748e. f 811. 8192

et her net 1/ 19


59/112



Full examples 3

748e. f 811. 8193

et her net 1/ 20

748e. f 811. 8194

et her net 1/ 21

748e. f 811. 8195

et her net 1/ 22


60/112


61/112



Full examples 3

748e. f 811. 81b1

et her net 2/ 2

748e. f 811. 81b2

l oopback 1

N/ A

]] >] ] >


62/112



Full examples

The following example shows the RPC request and response of a operation with filter for

interface statedata and specific interfaces.

et her net 1/ 1

et her net 1/ 6]] >] ] >

et her net 1/ 1

748e. f 811. 8181

et her net 1/ 6


63/112


64/112



Full examples

et her net 1/ 2

aut o

et her net 1/ 3

aut o

et her net 1/ 4

aut o

et her net 1/ 5

aut o

et her net 1/ 6

aut o

et her net 1/ 7

aut o


65/112



Full examples 3

et her net 1/ 8

aut o

et her net 1/ 9

aut o

et her net 1/ 10

aut o

et her net 1/ 11

aut o

et her net 1/ 12

aut o

et her net 1/ 13

aut o


66/112



Full examples

et her net 1/ 14

aut o

et her net 1/ 15

aut o

et her net 1/ 16

aut o

et her net 1/ 17

aut o

et her net 1/ 18

aut o

et her net 1/ 19

aut o


67/112



Full examples 3

et her net 1/ 20

aut o

et her net 1/ 21

aut o

et her net 1/ 22

aut o

et her net 1/ 23

aut o

et her net 1/ 24

aut o

et her net 2/ 1


68/112



Full examples

et her net 2/ 2

l oopback 1
172. 13. 32. 1/ 32

]] >] ] >


69/112



Chapter

4MPLS Configuration

In this chapter

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59MPLS configuration elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59MPLS state elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Full examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

OverviewThis chapter describes how to configure Multiprotocol Label Switching (MPLS) using the YANG

model, and illustrates the equivalent XML and CLI.


MPLS configuration elements

Each element of the MPLS corresponds to the following:

A YANG model description An XML description A CLI descriptionThe following subsections compare a specific example for each MPLS configuration element.


70/112




MPLS priority

This data element specifies the setup priority and the hold priority.

TABLE 14 MPLS priorityYANG model XML CLI

grouping mpls-priority-grouping

{

description "MPLS Setup and hold priority group";

container mpls-priority

{

description "Setup and hold priority";

leaf setup-priority

{

type uint32

{

range "0..7";

}

mandatory "true";

description "Setup priority";

}

leaf hold-priority

{

type uint32

{

range "0..7";

}

mandatory "true";

description "Hold priority";

}}

}

7

7

[no] priority

[no] priority


71/112



MPLS configuration elements 4MPLS traffic engineering

The following data element specifies the traffic engineering parameters.

TABLE 15 MPLS traffic engineeringYANG model XML CLI

grouping mpls-traffic-eng-grouping

{

description "MPLS Traffic Engineering parameters

group";

container mpls-traffic-eng

{

description "MPLS Traffic Engineering

parameters";

leaf max-burst

{

type uint32

{

range "0..2147483647";

}

units "Bytes";

description "Maximum burst";

}

214748364

[no] traffic-eng max-burst

leaf max-rate

{

type uint32

{

range "0..2147483647";

}

units "Kilobits per second";description "Maximum traffic rate";

}

214748364

[no] traffic-eng max-rate

leaf mean-rate

{

type uint32

{

range "0..2147483647";

}

units "Kilobits per seconds";

description "Mean traffic rate";

}

}

}

4500

[no] traffic-eng mean-rate


72/112




MPLS path

The following data element creates a path and inserts nodes into the path.

TABLE 16 MPLS pathYANG model XML CLI

grouping mpls-path-grouping

{

description "MPLS Explicit Path configuration group";

list path

{

key "name";

description "Explicit route path";

leaf name

{

type mpls-path-type;

description "Path Name";

}

example

[no] path

leaf-list strict

{

type ipv4_address;

description "Strict node";

}

1.1.1.1 [no] strict

leaf-list loose

{

type ipv4_address;

description "Loose node";

}

2.2.2.2 [no] loose

list insert-strict

{key "addr before";

description "Insert Strict nodes";

leaf addr

{

type ipv4_address;

description "Strict node";

}

leaf before

{

type ipv4_address;

description "Insert before this node";

}

}

3.3.3.3

2.2.2.2

[no] insert strict before


73/112



MPLS configuration elements 4

MPLS LSP configuration

The following data element configures the Label Switch Path (LSP).

list insert-loose

{

key "addr before";description "Insert Loose nodes";

leaf addr

{

type ipv4_address;

description "Loose node";

}

leaf before

{

type ipv4_address;

description "Insert before this node";

}

}

}

}

4.4.4.4

1.1.1.1

[no] insert loosebefore

TABLE 16 MPLS path (Continued)YANG model XML CLI

TABLE 17 MPLS LSPYANG model XML CLI

grouping mpls-lsp-grouping

{

description "MPLS LSP configuration group";

list lsp{

key "name";

description "MPLS Signaled label switched

"+"path configuration";

leaf name

{

type string

{

length "1..64";

}

description "LSP name";

}

example

[no] lsp

leaf adaptive

{

type empty;

description "Enable LSP to be modified

on fly";

}

[no] adaptive


74/112


75/112



MPLS configuration elements 4

leaf ipmtu

{

type uint32;{

range "576..9194";

}

description "IP Packet MTU size";

}

NOTE: The maximum value varies depending on thedefault max-frame-size configured on the device.

1526 [no] ipmtu

leaf ldp-tunneling

{

type empty;

description " Enable LDP over RSVP

tunneling";

}

[no] ldp-tunneling

leaf metric

{

type uint32

{

range "1..65535";

}

description "LSP metric";

}

600 [no] metric

leaf primary-path

{


description "LSP Primary explicit path";

}

example

[no] primary-path

uses mpls-priority-grouping;

leaf record

{

type empty;

description "Enable recording path

routes";

}

[no] record

leaf reoptimize-timer

{

type uint32

{range "300..65535";

}

units "seconds";

description "Reoptimize timer value";

}

3600

[no] reoptimize_timer

TABLE 17 MPLS LSP (Continued)YANG model XML CLI


76/112




leaf revert-timer

{

type uint32;{

range "1..65535";

}

units "seconds";

description "LSP revert timer";

}

2999 [no] revert-time

uses mpls-traffic-eng-grouping;

list secondary-path

{

key "name";

description "Secondary Path

configuration";leaf name

{


description "Name of the Secondary

Path";

}

}

}

}

example2

[no] secondary-path

TABLE 17 MPLS LSP (Continued)YANG model XML CLI


77/112



MPLS configuration elements 4MPLS RSVP configuration

The following data element configures the Resource ReSerVation Protocol (RSVP) parameters.

TABLE 18 MPLS RSVP configurationYANG model XML CLI

grouping mpls-rsvp-grouping

{

description "MPLS RSVP configuration group";

container rsvp

{

description "MPLS RSVP configuration";

leaf refresh-interval

{

type uint32

{

range "1..360";

}units "seconds";

description "Avg. interval between " + "refresh

path and resv msgs";

}

360

[no] refresh-interval

leaf refresh-multiple

{

type uint32

{

range "1..255";

}

description "Num of unresponded path " + "or

resv before time out";

}

}

}

255

[no] refresh-multiple


78/112


79/112



MPLS state elements 4}

gr oupi ng per - pr i or i t y- bandwi dt h- gr oupi ng{

descri pt i on "Bandwi dt h( kbps) per pri or i t y ( 0- 7) ";l i st pr i or i ty- bandwi dt h

{key "pri or i ty";descri pt i on "Bandwi dt h( kbps) f or a pr i or i t y";l eaf pr i or i t y{

t ype common: pr i ori t y- val ue;descri pt i on "Pr i or i ty val ue";

}l eaf bandwi dt h{

t ype ui nt 32{

r ange "0. . 4294967295";}

descr i pt i on "Bandwi dt h( kbps) ";}}

}

gr oupi ng mpl s- l sp- st atedat a- gr oupi ng{

descr i pt i on "Rout er MPLS LSP st atedat a gr oupi ng" ;cont ai ner mpl s- l sp- st at edat a{

descri pti on "Rout er MPLS LSP st atedata" ;l i st l sp{

key " name" ;

descr i pt i on "MPLS Si gnal ed l abel swi t ched "+"pat h conf i gur at i on";

l eaf name{

t ype str i ng{

l engt h "1. . 64";}descr i pt i on "LSP name";

}

l eaf to{

t ype common: i pv4_address;descr i pt i on "Egr ess LER f or t he LSP";}

choi ce admi n-st ate{

descr i pt i on "The admi ni st r ati ve st at e of t he LSP";

case up{


80/112



MPLS state elements

l eaf up{

t ype empt y;descri pt i on "Up";

}}

case down{

l eaf down{

t ype empt y;descr i pti on "Down";

}}

}

choi ce oper - st at e{

descr i pt i on "The operati onal st ate of t he LSP";

case up{l eaf up{


}}case up- st ar{

l eaf up- star{

t ype empt y;descri pt i on "Up*";

}

}case down{

l eaf down{


}}

}

l eaf t unnel - i ntf {

t ype str i ng

{ l engt h "1. . 16";}descri pt i on "The t unnel i nt er f ace";

}

l eaf up- dn- t i mes{

t ype ui nt 16{

r ange "0. . 65535" ;


81/112



MPLS state elements 4}descr i pt i on "The number of t i mes t he oper at i onal st ate"+" of t he LSP' s pri mary pat h has t r ansi t i oned f r omDOWN"+" t o UP";

}

l eaf r etr y- no{

t ype ui nt 16{

r ange "0. . 65535" ;}descr i pt i on "The number of at t empts t he i ngr ess LER has" +

" made to connect t o the egress LER" ;}

l eaf act i ve- pat h{

t ype str i ng{

l engt h "1. . 64";}descri pt i on "The pat h cur r ent l y i n use f or t hi s LSP. ";

}

}

}

}

gr oupi ng mpl s- i nt er f ace- st at edata- gr oupi ng{

descr i pt i on "Rout er MPLS i nt erf ace st at edat a gr oupi ng";cont ai ner mpl s- i nt er f ace- st at edat a

{descr i pt i on "Rout er MPLS i nt er f ace stat e dat a";l i st i nt er f ace{

key i nt er f ace- i d;descri pt i on "Li st of MPLS- enabl ed i nt er f aces - - st at e dat a";

l eaf i nter f ace- i d{

t ype common: i nt er f ace- al l - t ypes;descri pt i on "The i nt er f ace i dent i f i er i ncl udi ng chassi s sl ot

and port number" ;}

choi ce admi n-st ate{descri pt i on "The admi ni st r at i ve st at e of t he i nt er f ace";

case up{

l eaf up{


}


82/112



MPLS state elements

}case down{

l eaf down{

t ype empt y;

descr i pti on "Down";}

}}

choi ce oper - st at e{

descri pt i on "The oper at i onal st at e of t he i nt er f ace";

case up{

l eaf up{

t ype empt y;

descri pt i on "Up";}}case down{

l eaf down{


}}

}

l eaf maxi mum- bw{

t ype ui nt 32{

r ange " 0. . 4294967295" ;}descr i pt i on "The maxi mumout bound bandwi dth t hat can"+" be used on the i nt er f ace. ";

}

l eaf maxi mum- r eservabl e- bw{

t ype ui nt 32{

r ange " 0. . 4294967295" ;}

descr i pt i on "The maxi mumbandwi dth that can be"+" r eser ved on the i nt er f ace. ";}

l eaf admi n-groups- bi t map{

t ype ui nt 32{

r ange " 0. . 4294967295" ;}descri pt i on "The bi t f i el d i ndi cat i ng t he"+


83/112



MPLS state elements 4" admi ni st r at i ve gr oups t o whi ch t hi s i nt er f ace bel ongs. ";

}

cont ai ner per- pr i or i t y-r eser vabl e- bw{

descr i pt i on "The amount of bandwi dth not yet r eserved on"

+"t he i nt erf ace per pr i or i t y (0 to 7) ";uses per - pr i ori t y- bandwi dt h- gr oupi ng;

}

cont ai ner per- pr i or i t y-l ast- sent - reser vabl e- bw{

descr i pt i on "The val ues i n t he Unr eser ved Bandwi dt h TLV"+" sent i n the most r ecent OSPF- TE LSA. " ;uses per - pr i ori t y- bandwi dt h- gr oupi ng;

}

cont ai ner pr ot ect i ng- bypass- l sp{

descr i pt i on "The name of any bypass LSPs t hat are"

+"protect i ng t hi s i nt erf ace. ";l eaf - l i st l sp{

t ype str i ng{

l engt h "1. . 64";}descr i pt i on "bypass LSP name";

}}

}

}

}

groupi ng mpl s- st atedat a- gr oupi ng{

descr i pt i on "Rout er MPLS st ate dat a gr oup";cont ai ner mpl s- st atedata{

descri pti on "Rout er MPLS st ate data" ;uses mpl s- l sp- st at edata- gr oupi ng;uses mpl s- i nt erf ace- st atedat a- gr oupi ng;

}

}

}


84/112



Full examples

Full examples

The following shows the complete YANG model for MPLS configuration, as well as example RPC

requests and responses.


submodul e mpl s- conf i g{

bel ongs- t o net i ron- conf i g{

pref i x brcd;}



or gani zat i on



descr i pti on "Thi s modul e def i nes the Rout er MPLS conf i gur ati on. VERSI ON: " ;

r evi si on 2011- 04- 20{


t ypedef hop- l i mi t - t ype{

t ype ui nt 32{

r ange "0. . 255";}descri pt i on "Type f or Li mi t of hops";

}

t ypedef hop- l i mi t - t ype{

t ype ui nt 32{

r ange "0. . 255";}descri pt i on "Type f or Li mi t of hops";

}

t ypedef mpl s- pat h- t ype


85/112



Full examples 4{

t ype str i ng{

l engt h "1. . 64";}descr i pt i on "Pat h Name";

}

gr oupi ng mpl s- pr i or i t y-groupi ng{

descr i pt i on "MPLS Setup and hol d pr i ori t y gr oup";cont ai ner mpl s- pr i or i t y{

descri pt i on "Set up and hol d pr i or i t y";

l eaf setup- pr i or i ty{

t ype ui nt 32{

r ange "0. . 7";

}mandat ory " t r ue" ;descri pt i on "Set up pr i or i t y";

}

l eaf hol d- pr i or i ty{

t ype ui nt 32{

r ange "0. . 7";}mandat ory " t r ue" ;descri pt i on "Hol d pri ori t y";

}}

}

gr oupi ng mpl s- t r af f i c- eng- gr oupi ng{

descr i pt i on "MPLS Traf f i c Engi neer i ng par ameters gr oup";

cont ai ner mpl s- t r af f i c-eng{

descr i pt i on "MPLS Tr af f i c Engi neer i ng parameter s";

l eaf max- burst{

t ype ui nt 32

{ r ange "0. . 2147483647";}uni t s "Bytes";descr i pt i on "Maxi mum bur st ";

}

l eaf max- r ate{

t ype ui nt 32{


86/112



Full examples

r ange "0. . 2147483647";}uni t s "Ki l obi t s per second";descri pt i on "Maxi mum t r af f i c r at e";

}

l eaf mean- r at e{

t ype ui nt 32{

r ange "0. . 2147483647";}uni t s "Ki l obi t s per seconds";descri pt i on "Mean tr af f i c r at e";

}

}

}

groupi ng mpl s- pat h- gr oupi ng{descri pt i on "MPLS Expl i ci t Pat h conf i gur at i on gr oup";l i s t pat h{

key "name";descri pt i on "Expl i ci t r out e pat h";l eaf name{

t ype mpl s- path- t ype;descr i pt i on "Pat h Name";

}l eaf - l i st st r i ct{

t ype i pv4_addr ess;

descri pt i on "St r i ct node";}

l eaf - l i st l oos e{

t ype i pv4_addr ess;descr i pti on "Loose node";

}

l i st i nser t - s t r i ct{

key "addr bef ore" ;descri pt i on "I nsert St ri ct nodes";l eaf addr

{ t ype i pv4_address;descri pt i on "St ri ct node";

}l eaf bef or e{

t ype i pv4_address;descri pt i on "I nser t bef or e t hi s node";

}}


87/112


88/112


89/112



Full examples 4{

t ype empt y;descr i pt i on "Enabl e r ecordi ng pat h r out es";

}

l eaf r eopt i mi ze- t i mer

{t ype ui nt 32{

r ange "300. . 65535";}uni t s " seconds";descr i pt i on "Reopt i mi ze t i mer val ue";

}

l eaf r evert - t i mer{

t ype ui nt 32;uni t s " seconds";descri pt i on "LSP rever t t i mer ";

}

uses mpl s- t r af f i c- eng- gr oupi ng;

l i st secondar y-pat h{

key " name" ;descr i pt i on "Secondar y Pat h conf i gur at i on";l eaf name{

t ype mpl s- path- t ype;descr i pt i on "Name of t he Secondar y Pat h";

}}

}

}

groupi ng mpl s- r svp- gr oupi ng{

descr i pt i on "MPLS RSVP conf i gur ati on gr oup" ;cont ai ner r svp{

descri pti on "MPLS RSVP conf i gurat i on" ;

l eaf refr esh- i nt erval{

t ype ui nt 32{r ange "1. . 360";

}uni t s " seconds";descr i pt i on "Avg. i nt erval between " +

" r ef r esh pat h and r esv msgs" ;}

l eaf refr esh- mul t i pl e{


90/112



Full examples

t ype ui nt 32{

r ange "1. . 255";}descr i pti on "Num of unr esponded path " +

"or r esv bef or e ti me out ";

}

}

}

gr oupi ng mpl s- conf i g- gr oupi ng{

descr i pt i on "Rout er MPLS conf i gur ati on gr oup";cont ai ner mpl s- conf i g{

descr i pt i on "Rout er MPLS conf i gur at i on";uses mpl s- pat h-groupi ng;uses mpl s- l sp- gr oupi ng;

uses mpl s- r svp- groupi ng;

}

}

}

The following example shows the RPC request and response of an operation.

exampl e1. 1. 1. 12. 2. 2. 23. 3. 3. 32. 2. 2. 2
4. 4. 4. 4

1. 1. 1. 1
exampl e2
10. 10. 10. 10

exampl e


91/112



Full examples 45. 5. 5. 56. 6. 6. 6exampl e
201526

6003600
2999
exampl e2

6
6
214748364214748364

4500
360
255]] >] ] >

The following example shows the complete CLI for an MLPS configuration.

Brocade# show r unCur r ent conf i gur at i on:!ver V5. 2. 0T183!!

no spanni ng- t r ee!!vl an 1 name DEFAULT- VLAN!

vl an 4089unt agged et he 2/ 1 to 2/ 2

!!sys t em- max vl an 4095syst em- max vi r t ual - i nt erf ace 4095!aaa aut hent i cat i on enabl e defaul t r adi us t acacs+ l ocalaaa aut hent i cat i on l ogi n def aul t l ocal r adi us t acacs+aaa aut hent i cat i on l ogi n pr i vi l ege- mode


92/112



Full examples

aaa aut hori zat i on exec def aul t t acacs+ r adi usaaa account i ng commands 0 def aul t st ar t - st op r adi usaaa account i ng exec def aul t st ar t - st op r adi usaaa account i ng systemdef aul t st ar t - st op r adi usr adi us- server host 10. 20. 99. 135 aut h- port 1812 acct- por t 1813 def aul t key 0 r xperft acacs- server host 10. 20. 99. 135 aut h- por t 49 def aul t key 2 $VUNTbl VH

sntp server 10. 20. 99. 135 4sntp server 10. 20. 99. 130 4enabl e snmp conf i g- r adi usenabl e aaa consol econsol e t i meout 5l oggi ng host 10. 20. 99. 136l oggi ng consol euser name br ocade password . . . . .username ncl ocal normal pr i vi l ege 5 passwor d . . . . .username ncl ocal super password . . . . .i p r out e 0. 0. 0. 0/ 0 10. 20. 96. 1!!!

!!snmp- ser versnmp- server communi t y . . . . . r of dp r un!netconf server!router i s i snet 56. 0000. 0001. 0209. 9187. 00i s - t ype l evel - 2addr ess- f ami l y i pv4 uni castmet r i c- st yl e wi de

exi t - address-f ami l y

addr ess- f ami l y i pv6 uni castno adj acency-check

exi t - address-f ami l y!!!!!!i nt erf ace l oopback 1i p addr ess 172. 13. 32. 1/ 32

!!

i nt er f ace management 1i pv6 address 2001: : 10: 20: 99: 187/ 64i p address 10. 20. 99. 187/ 20enabl e

!i nt er f ace et her net 1/ 3i p router i s i si p addr ess 1. 1. 3. 1/ 24i s i s ci r cui t - t ype l evel - 2i s i s hel l o- i nterval 1i si s met ri c 110


93/112



Full examples 4i s i s poi nt - to -poi nt

!i nt er f ace et her net 2/ 1enabl e

!i nt er f ace et her net 2/ 2

enabl e!!!r out er mpl spol i cyt r af f i c-eng i s i s l evel - 2r etr y- t i me 300no rapi d- r et ry

rsvpref resh- i nt erval 360r ef r esh- mul t i pl e 255

mpl s- i nt er f ace e1/ 3rsvp- rel i abl e- messagi ng r api d- retr ans- i nt erval 2000 rapi d- r et r y- l i mi t 5r svp- r ef r esh- r educt i on bundl e- messagesr svp- r ef r esh- r educt i on summary- r ef r eshr eservabl e- bandwi dth per cent age 80

path exampl es t r i ct 1. 1. 1. 1s t r i ct 3. 3. 3. 3l oose 4. 4. 4. 4l oose 2. 2. 2. 2

path exampl e2

s t r i ct 2. 2. 2. 2str i ct 10. 10. 10. 10

l sp exampl eto 6. 6. 6. 6f rom5. 5. 5. 5pr i mary exampl epr i or i ty 6 6t r af f i c- eng max- r at e 214748364 mean- r at e 4500 max- bur st 214748364met r i c 600hop- l i mi t 20adapt i vesecondar y exampl e2

r ever t - t i mer 2999l dp- t unnel i ngenabl e


94/112


95/112



Full examples 4] ] >] ] >

]] >] ] >

exampl el sp11. 99. 161. 1

t nl 1013

exampl el sp21. 99. 145. 1

t nl 20
0

ve 100

0
00

00


96/112



Full examples

10

20

30

40

50

60

70

00

10

20

30

4

0

50

60


97/112



Full examples 4
70

]] >] ] >


98/112



Full examples

operation example

The following example shows the RPC request and response of a operation.

]] >] ] >

Pr i _t o_ml x4_2
1. 99. 144. 1
1. 99. 142. 1

Pr i _t o_ml x4_3
1. 99. 143. 1

Pr i _t o_ml x4_4
1. 99. 144. 1

Pr i _t o_ml x4_5
1. 99. 145. 1

Pr i _t o_ml x8_1
1. 99. 143. 1
1. 99. 141. 1

Pr i _t o_u40

1. 99. 144. 1
1. 99. 142. 1
1. 99. 30. 1

Pr i _t o_u41
1. 99. 144. 1
1. 99. 142. 1
1. 99. 40. 1


99/112



Full examples 4
Sec_t o_ml x4_2
1. 99. 143. 1
1. 99. 141. 1
1. 99. 142. 1

Sec_t o_ml x4_3
1. 99. 144. 1
1. 99. 143. 1

Sec_t o_ml x4_4
1. 99. 143. 1
1. 99. 144. 1

Sec_t o_ml x4_5
1. 99. 143. 1
1. 99. 145. 1

Sec_t o_ml x8_1
1. 99. 144. 1
1. 99. 142. 1
1. 99. 141. 1

Sec_t o_u40
1. 99. 143. 1
1. 99. 141. 1
1. 99. 30. 1

Sec_t o_u41
1. 99. 143. 1

1. 99. 141. 1
1. 99. 40. 1

Ter _t o_ml x4_2
1. 99. 40. 1
1. 99. 142. 1

Ter _t o_ml x4_3
1. 99. 145. 1
1. 99. 143. 1

Ter _t o_ml x4_4
1. 99. 145. 1
1. 99. 144. 11

Ter _t o_ml x4_5
1. 99. 144. 1
1. 99. 145. 1

Ter _t o_ml x8_1


100/112



Full examples

1. 99. 30. 1
1. 99. 141. 1

Ter _t o_u40
1. 99. 30. 1

Ter _t o_u41
1. 99. 40. 1

scr i pt l

brocade 05400a yangguide

Documents