53-1003041-02 9 December, 2013 Multi-Service IronWare YANG Configuration Guide Supporting Multi-Service IronWare R05.6.
Copyright © 2013 Brocade Communications Systems, Inc. All Rights Reserved. ADX, AnyIO, Brocade, Brocade Assurance, the B-wing symbol, DCX, Fabric OS, ICX, MLX, MyBrocade, OpenScript, VCS, VDX, and Vyatta are registered trademarks, and HyperEdge, The Effortless Network, and The On-Demand Data Center 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.
Contents About This Document Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . . v Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Notes, cautions, and danger notices . . . . . . . . . . . . . . . . . . . . . .
Interface state elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Full examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 operation examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 operation example . . . . . . . . . . . . . . . . . . . . . . . . . 53 Chapter 4 MPLS Configuration In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About This Document 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 on the software release R05.6.00 of the NetIron devices.
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. NOTE A note provides a tip, guidance or advice, emphasizes important information, or provides a reference to related information.
Getting technical help • Brocade NetIron CES 2000 Series and Brocade NetIron CER 2000 Series Hardware Installation Guide 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.
Getting technical help viii Multi-Service IronWare YANG Configuration Guide 53-1003038-02
Chapter 1 Overview Introduction to YANG NOTE Brocade maintains limited support only for this feature. 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 Multi-Service IronWare Administration Configuration Guide.
1 2 Introduction to YANG Multi-Service IronWare YANG Configuration Guide 53-1003038-02
Chapter Common Definitions and Headers 2 In this chapter • Common definition and header elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 • NetIron configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 • Device version state data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 • RPC delete operation example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 Common definition and header elements "pos\s+\d{1,2}/\d{1,2}\s+to\d{1,2}/\d{1,2}|"+ "ve\s+\d|"+ "loopback\s+\d|"+ "management\s+\d|"+ "tunnel\s+\d"; length "4..
Common definition and header elements 2 typedef ethernet-intf-single { type string { pattern "ethernet\s+\d{1,2}/\d{1,2}"; length "11..20"; } description "Single ethernet interface"; } typedef ethernet-pos-intf-single { type string { pattern "ethernet\s+\d{1,2}/\d{1,2}|"+ "pos\s+\d{1,2}/\d{1,2}"; length "11..20"; } description "Single ethernet or pos interface"; } typedef ve-intf-single { type string { pattern "ve\s+\d"; length "4..
2 Common definition and header elements type uint32 { range "1..4090"; } description "VLAN Identifier"; } typedef ipv4_address { type string { length "7..15"; } description "IPv4 Address"; } typedef ipv6_address { type string { length "3..39"; } description "IPv6 Address"; } typedef ipv4_address_mask { type string { length "9..19"; } description "IPv4 Address/mask"; } typedef ipv6_address_mask { type string { length "6..
NetIron configuration file 2 grouping priority-grouping { description "Priority"; container priority { description "Priority"; leaf value { type priority-value; description "Priority value"; } leaf force { type empty; description "Priority force"; } } } } NetIron configuration file The following YANG model defines the header information, linkage statements, meta information, and the revision history for the NetIron configuration group. NOTE For the most recent YANG models, visit http://my.brocade.com.
2 NetIron state data } grouping netiron-config { description "NetIron configuration group"; container netiron-config { description "NetIron configuration"; uses vlan-config-grouping; uses interface-config-grouping; uses mpls-config-grouping; } } } NetIron state data The following YANG model contains the state data for the NetIron device. NOTE For the most recent YANG models, visit http://my.brocade.com. module netiron-statedata { namespace "http://brocade.
Device version state data 2 uses interface-statedata-grouping; uses mpls-statedata-grouping; } } } Device version state data The following YANG model contains the state data for the device version. NOTE For the most recent YANG models, visit http://my.brocade.com. submodule version-statedata { belongs-to netiron-statedata { prefix "statedata"; } import common-defs { prefix "common"; } organization "Brocade Communications Inc.
2 Device version state data { length 1..20; } description "device part number"; } } grouping software-version-grouping { leaf version { type string { length 1..63; } description "Image version."; } leaf compiled-on { type string { length 1..127; } description "The image compilation date and time."; } leaf label { type string { length 1..15; } description "The image label.."; } leaf length { type uint32 { range "0..4294967295"; } description "The image length."; } leaf source { type string { length 1..
Device version state data 2 { range "0..4294967295"; } description "The flash size."; } leaf flash-name { type string { length "1..31"; } description "The flash name."; } } grouping license-grouping { description "Software License Id"; leaf software-packaging-type { type string { length 1..31; } description "Software Packaging Type"; } leaf license-id { type string { length 1..
2 Device version state data container system-id { description "System Identifier"; uses device-id-grouping; } container factory-id { description "System Factory Identifier"; uses device-id-grouping; } container license { description "Software License Id"; uses license-grouping; } leaf cpld-version { type uint8 { range "0..255"; } description "The CPLD Version."; } leaf micro-controller-version { type uint8 { range "0..255"; } description "The Micro Controller Version.
Device version state data 2 } description "Module name"; } leaf module-state { type string { length 1..16; } description "Module state (if down)"; } container module-id { description "Module Identifier"; uses device-id-grouping; } list fe { key "fe-id"; description "The FE"; leaf fe-id { type uint8 { range 1..16; } description "FE id"; } leaf fe-type { type uint32 { range 1..1048575; } description "FE type"; } leaf fe-ver { type uint8 { range 1..
2 Device version state data { description "Boot Image Software Versions"; uses software-version-grouping; } container monitor { description "Monitor Image Software Versions"; uses software-version-grouping; } container ironware { description "Ironware Image Software Versions"; uses software-version-grouping; } } leaf fpga-versions { type uint8 { range "0..255"; } description "The FPGA Version.
Device version state data 2 type uint32 { range "0..4294967295"; } description "Processor revision"; } leaf bus-speed { type uint32 { range "0..4294967295"; } description "The Bus Speed (MHz)"; } } container boot-flash { description "Boot Flash"; uses flash-grouping; } container code-flash { description "Code Flash"; uses flash-grouping; } leaf dram-size { type uint32 { range "0..4294967295"; } description "The DRAM size."; } leaf sram-size { type uint32 { range "0..
2 RPC delete operation example { key "ppcr-id"; description "The DMA information container."; leaf ppcr-id { type uint32 { range "0..4294967295"; } description "The PPCR Id."; } leaf cam-size { type uint32 { range "0..4294967295"; } description "The CAM size (K entries)"; } leaf pram-size { type uint32 { range "0..4294967295"; } description "The PRAM size (K entries)"; } leaf age-ram-size { type uint32 { range "0..
RPC delete operation example 2 ethernet 1/1 ]]>]]> PAGE 262 18 RPC delete operation example Multi-Service IronWare YANG Configuration Guide 53-1003038-02
Chapter 3 Interface Configuration In this chapter • Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Interface configuration elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Interface state elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Full examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 Interface configuration elements 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. TABLE 2 Alarm monitoring YANG model XML CLI leaf alarm-monitoring { type empty; description "Enable alarm monitoring"; } [no] alarm-monitoring Admin status choice This data element is used to enable or disable the interface.
Interface configuration elements 3 Gig default This data element indicates the Gigabit negotiation modes.
3 Interface configuration elements Layer 2 switching This data element indicates whether or not Layer 2 switching is enabled. TABLE 5 Layer 2 switching YANG model XML CLI leaf route-only { type empty; description "Enable Layer 2 switching"; } [no] route-only Drop precedence This data element indicates the Quality of Service (QoS) drop precedence value.
Interface configuration elements 3 Loop detection This data element indicates whether or not loop detection is enabled.
3 Interface configuration elements Source guard This data element indicates whether or not the port is set as an IP source guarded port. NOTE This data element is supported only on Brocade MLX series and Brocade NetIron XMR platforms. TABLE 9 .
Interface configuration elements 3 IPv4 configuration This data element indicates the IPv4 address of an interface. TABLE 12 IPv4 configuration YANG model XML CLI container ip { description "Interface IPv4 configuration"; leaf address { type ipv4_address_mask; description "IPv4 address"; } } 1.1.1.
3 Interface state elements Interface state elements The following is the YANG model for the Interface state data elements. NOTE For the most recent YANG models, visit http://my.brocade.com. submodule interface-statedata { belongs-to netiron-statedata { prefix "statedata"; } import common-defs { prefix "common"; } organization "Brocade Communications Inc."; contact "Technical Support Center"+ "130 Holger Way,"+ "San Jose, CA 95134"+ "Email: ipsupport@brocade.com"+ "Phone: 1-800-752-8061"+ "URL: www.
Interface state elements 3 case up { leaf up { type empty; description "The link is up"; } } case down { leaf down { type empty; description "The link is down"; } } } choice l2-state { description "The L2 state for the port"; case disabled { leaf disabled { type empty; description "The } } case blocked { leaf blocked { type empty; description "The } } case listening { leaf listening { type empty; description "The } } case learning { leaf learning { type empty; description "The } } case preforwarding { lea
3 Interface state elements description "The L2 state is preforwarding"; } } case forward { leaf forward { type empty; description "The } } case none { leaf none { type empty; description "The } } case lk-disable { leaf lk-disable { type empty; description "The } } case oam-disable { leaf oam-disable { type empty; description "The } } case dot1x-blocked { leaf dot1x-blocked { type empty; description "The } } case lacp-blocked { leaf lacp-blocked { type empty; description "The } } case chdlc-down { leaf chd
Interface state elements 3 { leaf ppp-down { type empty; description "The L2 state is PPP-DOWN"; } } case inactive { leaf inactive { type empty; description "The L2 state is inactive"; } } } choice duplex { description "The duplex mode of the interface"; case half { leaf half { type empty; description "Half Duplex"; } } case full { leaf full { type empty; description "Full Duplex"; } } case none { leaf none { type empty; description "None"; } } } leaf speed { type string { length "1..
3 Interface state elements length "1..
Interface state elements 3 description "Level 2"; } } case level3 { leaf level3 { type empty; description } } case level4 { leaf level4 { type empty; description } } case level5 { leaf level5 { type empty; description } } case level6 { leaf level6 { type empty; description } } case level7 { leaf level7 { type empty; description } } "Level 3"; "Level 4"; "Level 5"; "Level 6"; "Level 7"; } leaf mac-address { type common:mac_address; description "The MAC address of the inteface"; } leaf name { type str
3 Full examples } } } } Full examples The following shows the complete YANG model for interface configuration, as well as example RPC requests and responses. NOTE For the most recent YANG models, visit http://my.brocade.com. submodule interface-config { belongs-to netiron-config { prefix brcd; } import common-defs { prefix "common"; } organization "Brocade Communications Inc."; contact "Technical Support Center"+ "130 Holger Way,"+ "San Jose, CA 95134"+ "Email: ipsupport@brocade.
Full examples 3 { value "1"; description "10M, full duplex"; } enum 10-half { value "2"; description "10M, half duplex"; } enum 100-full { value "3"; description "100M, full duplex"; } enum 100-half { value "4"; description "100M, half duplex"; } enum 1000-full { value "5"; description "1G, full duplex"; } enum 1000-half { value "6"; description "1G, half duplex"; } enum 1000-master { value "7"; description "1G, master"; } enum 1000-slave { value "9"; description "1G, slave.
3 Full examples } leaf alarm-monitoring { type empty; description "Enable alarm monitoring"; } choice admin-status-choice { description "Enable/Tear down the LSP"; case enable { leaf enable { type empty; description "Enable the LSP"; } } case disable { leaf disable { type empty; description "Tear down the LSP"; } } } 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 "Aut
Full examples 3 case neg-full-auto { leaf neg-full-auto { type empty; description "Autonegotiation first, "+ "if failed try non-autonegotiation"; } } } } leaf route-only { type empty; description "Enable Layer 2 switching"; } container drop-precedence { description "QOS drop precedence"; leaf value { type uint32 { range "0..
3 Full examples } } leaf load-interval { type uint32 { range "30..300"; } units "Seconds"; description "Load interval, multiple of 30"; } leaf source-guard { type empty; description "Enable/ IP source guard"; } leaf flow-control { type empty; description "Enable 802.
Full examples 3 } } } The following example shows the RPC request and response of an operation. PAGE 463 Full examples ethernet 1/3 1.1.3.
Full examples 3 ve 2 1.1.2.
3 Full examples The following example shows the complete CLI for an interface configuration. Brocade# show run Current configuration: ! ver V5.2.
Full examples 3 ipv6 address 2001::10:20:99:187/64 ip address 10.20.99.187/20 enable ! interface ethernet 1/1 enable load-interval 30 route-only ip address 1.1.1.1/24 ipv6 address 2000:0:0:1::1/64 ipv6 enable ! interface ethernet 1/2 enable load-interval 30 route-only ip address 1.1.12.1/24 ipv6 address 2000:0:0:12::1/64 ipv6 enable ! interface ethernet 1/3 load-interval 30 route-only ip address 1.1.3.
3 Full examples ! ! ! ! end operation examples The following example shows the RPC request and response of a operation with filter for interface statedata. PAGE 51Full examples 3 748e.f811.
3 Full examples 748e.f811.
Full examples 3 748e.f811.
3 Full examples 748e.f811.
Full examples 3 748e.f811.
3 Full examples 748e.f811.
Full examples 3 748e.f811.
3 Full examples 748e.f811.
Full examples 3 748e.f811.
3 Full examples The following example shows the RPC request and response of a operation with filter for interface statedata and specific interfaces. PAGE 61Full examples 3 748e.f811.8186 ]]>]]> operation example The following example shows the RPC request and response of a operation. PAGE 623 Full examples ethernet 1/2 auto ethernet 1/3
Full examples 3 ethernet 1/8 auto ethernet 1/9
3 Full examples ethernet 1/14 auto ethernet 1/15
Full examples 3 ethernet 1/20 auto ethernet 1/21
3 Full examples ethernet 2/2 loopback 1 172.13.32.
Chapter 4 MPLS Configuration In this chapter • Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • MPLS configuration elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • MPLS state elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Full examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 MPLS configuration elements MPLS priority This data element specifies the setup priority and the hold priority. TABLE 14 MPLS priority YANG model XML CLI leaf setup-priority { type uint32 { range "0..7"; } mandatory "true"; description "Setup priority"; } 7 [no] priority leaf hold-priority { type uint32 { range "0..
MPLS configuration elements 4 MPLS traffic engineering The following data element specifies the traffic engineering parameters. TABLE 15 MPLS traffic engineering YANG model XML CLI 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..
4 MPLS configuration elements MPLS path The following data element creates a path and inserts nodes into the path. TABLE 16 MPLS path YANG model XML CLI 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.
MPLS configuration elements TABLE 16 4 MPLS path (Continued) YANG model XML CLI [no] insert loose before 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.
4 MPLS configuration elements TABLE 17 MPLS LSP (Continued) YANG model XML CLI leaf commit { type empty; description "Apply the parameter modifications to LSP"; } [no] commit [no] enable [no] disable leaf from { type ipv4_address; description "Ingress router of the LSP"; } 5.5.5.5 from leaf to { type ipv4_address; description "Egress router of the LSP"; } 6.6.
MPLS configuration elements TABLE 17 4 MPLS LSP (Continued) YANG model XML CLI 1526 [no] ipmtu [no] ldp-tunneling leaf metric { type uint32 { range "1..
4 MPLS configuration elements TABLE 17 MPLS LSP (Continued) YANG model leaf revert-timer { type uint32; { range "1..
MPLS configuration elements 4 MPLS RSVP configuration The following data element configures the Resource ReSerVation Protocol (RSVP) parameters. TABLE 18 MPLS RSVP configuration YANG model XML CLI 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..
4 MPLS state elements TABLE 19 Router MPLS configuration YANG model XML CLI grouping mpls-config-grouping { description "Router MPLS configuration group"; container mpls-config { description "Router MPLS configuration"; uses mpls-path-grouping; uses mpls-lsp-grouping; uses mpls-rsvp-grouping; } } [no] router mpls MPLS state elements The following is the YANG model for the MPLS state data elements. NOTE For the most recent YANG models, visit http://my.
MPLS state elements 4 description "Bandwidth(kbps) per priority (0-7)"; list priority-bandwidth { key "priority"; description "Bandwidth(kbps) for a priority"; leaf priority { type common:priority-value; description "Priority value"; } leaf bandwidth { type uint32 { range "0..
4 MPLS state elements } } case down { leaf down { type empty; description "Down"; } } } choice oper-state { description "The operational state of the LSP"; case up { leaf up { type empty; description "Up"; } } case up-star { leaf up-star { type empty; description "Up*"; } } case down { leaf down { type empty; description "Down"; } } } leaf tunnel-intf { type string { length "1..16"; } description "The tunnel interface"; } leaf up-dn-times { type uint16 { range "0..
MPLS state elements 4 } leaf retry-no { type uint16 { range "0..65535"; } description "The number of attempts the ingress LER has"+ " made to connect to the egress LER"; } leaf active-path { type string { length "1..64"; } description "The path currently in use for this LSP.
4 MPLS state elements { type empty; description "Down"; } } } choice oper-state { description "The operational state of the interface"; case up { leaf up { type empty; description "Up"; } } case down { leaf down { type empty; description "Down"; } } } leaf maximum-bw { type uint32 { range "0..4294967295"; } description "The maximum outbound bandwidth that can"+ " be used on the interface."; } leaf maximum-reservable-bw { type uint32 { range "0..
MPLS state elements 4 { description "The amount of bandwidth not yet reserved on" +"the interface per priority (0 to 7)"; uses per-priority-bandwidth-grouping; } container per-priority-last-sent-reservable-bw { description "The values in the Unreserved Bandwidth TLV" +" sent in the most recent OSPF-TE LSA."; uses per-priority-bandwidth-grouping; } container protecting-bypass-lsp { description "The name of any bypass LSPs that are" +"protecting this interface."; leaf-list lsp { type string { length "1..
4 Full examples Full examples The following shows the complete YANG model for MPLS configuration, as well as example RPC requests and responses. NOTE For the most recent YANG models, visit http://my.brocade.com. submodule mpls-config { belongs-to netiron-config { prefix brcd; } import common-defs { prefix "common"; } organization "Brocade Communications Inc."; contact "Technical Support Center"+ "130 Holger Way,"+ "San Jose, CA 95134"+ "Email: ipsupport@brocade.com"+ "Phone: 1-800-752-8061"+ "URL: www.
Full examples 4 { type string { length "1..64"; } description "Path Name"; } 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..
4 Full examples range "0..2147483647"; } units "Kilobits per second"; description "Maximum traffic rate"; } leaf mean-rate { type uint32 { range "0..
Full examples 4 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"; } } } } 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..
4 Full examples } } case disable { leaf disable { type empty; description "Tear down the LSP"; } } } leaf from { type ipv4_address; description "Ingress router of the LSP"; } leaf to { type ipv4_address; description "Egress router of the LSP"; } leaf hop-limit { type hop-limit-type; description "Limit of hops the LSP can traverse"; } leaf ipmtu { type uint32; description "IP Packet MTU size"; } leaf ldp-tunneling { type empty; description " Enable LDP over RSVP tunneling"; } leaf metric { type uint32 { ra
Full examples 4 { type empty; description "Enable recording path routes"; } leaf reoptimize-timer { type uint32 { range "300..
4 Full examples type uint32 { range "1..255"; } description "Num of unresponded path " + "or resv before time out"; } } } grouping mpls-config-grouping { description "Router MPLS configuration group"; container mpls-config { description "Router MPLS configuration"; uses mpls-path-grouping; uses mpls-lsp-grouping; uses mpls-rsvp-grouping; } } } The following example shows the RPC request and response of an operation. PAGE 89Full examples 4 5.5.5.5 6.6.6.
4 Full examples aaa authorization exec default tacacs+ radius aaa accounting commands 0 default start-stop radius aaa accounting exec default start-stop radius aaa accounting system default start-stop radius radius-server host 10.20.99.135 auth-port 1812 acct-port 1813 default key 0 rxperf tacacs-server host 10.20.99.135 auth-port 49 default key 2 $VUNTblVH sntp server 10.20.99.135 4 sntp server 10.20.99.130 4 enable snmp config-radius enable aaa console console timeout 5 logging host 10.20.99.
Full examples 4 isis point-to-point ! interface ethernet 2/1 enable ! interface ethernet 2/2 enable ! ! ! router mpls policy traffic-eng isis level-2 retry-time 300 no rapid-retry rsvp refresh-interval 360 refresh-multiple 255 mpls-interface e1/3 rsvp-reliable-messaging rapid-retrans-interval 2000 rsvp-refresh-reduction bundle-messages rsvp-refresh-reduction summary-refresh reservable-bandwidth percentage 80 rapid-retry-limit 5 path example strict 1.1.1.1 strict 3.3.3.3 loose 4.4.4.4 loose 2.2.2.
4 Full examples ! ! ! ! ! end operation examples The following example shows the RPC request and response of a operation for a single LSP. PAGE 93Full examples 4 ]]>]]> ]]>]]> PAGE 944 Full examples 1 0 2 0 3 0 4 0
Full examples 4 7 0 ]]>]]> Multi-Service IronWare YANG Configuration Guide 53-1003038-02 87
4 Full examples operation example The following example shows the RPC request and response of a operation. PAGE 97Full examples 4 Sec_to_mlx4_2 1.99.143.1 1.99.141.1 1.99.142.1 Sec_to_mlx4_3 1.99.144.1 1.99.143.1 Sec_to_mlx4_4 1.99.143.1 1.99.144.
4 Full examples 1.99.30.1 1.99.141.1 Ter_to_u40 1.99.30.1 Ter_to_u41 1.99.40.1 scriptlsp1008 161.0.0.113 81.0.0.
Chapter 5 VLAN Configuration In this chapter • Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • VLAN configuration elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • VLAN state elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Full examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 VLAN configuration elements VLAN name The VLAN name is a unique string that describes a specific VLAN. TABLE 21 VLAN name YANG model XML CLI leaf vlan-name { type string { length "1..31"; } description "VLAN Name"; } example [no] vlan name Tagged ports This data element indicates that a specific port is a tagged member of the VLAN.
VLAN configuration elements 5 Uplink ports This data element indicates which ports in the VLAN are connected to outside resources. TABLE 24 Uplink ports YANG model XML CLI leaf-list uplink-switch { type ethernet-pos-intf-multiple; description "List of Uplink ports to enable "+ "uplink switching on this VLAN.
5 VLAN state elements TABLE 27 VLAN accounting YANG model XML CLI leaf vlan-accounting { type empty; description "Enable VLAN accounting on the VLAN"; } [no] vlan-accounting VLAN CPU protection This data element indicates whether or not CPU protection is enabled.
VLAN state elements "URL: 5 www.brocade.com"; description "This module defines the device VLAN state data.
5 VLAN state elements list port { key port-id; description "VLAN port list"; leaf port-id { type common:interface-all-types; description "VLAN port"; } leaf tag-mode { type string { pattern "(untagged)"+ "|(tagged)"+ "|(broken)"; } description "Tag mode of port"; } leaf state { type string { length "1..19"; } description "Current state of the port."; } } leaf bytes-received { type string { length "1..
Full examples 5 description "All the ports that are configured as dual-mode ports in all the VLANs on the device"; } leaf default-vlan-id { type common:vlan-identifier; description "Default VLAN identifier"; } leaf control-vlan-id { type common:vlan-identifier; description "Control VLAN identifier"; } leaf maximum-port-vlan-entries { type uint32 { range "1..
5 Full examples "Technical Support Center"+ "130 Holger Way,"+ "San Jose, CA 95134"+ "Email: ipsupport@brocade.com"+ "Phone: 1-800-752-8061"+ "URL: www.brocade.com"; description "This module defines the VLAN configuration.
Full examples 5 uses priority-grouping; leaf router-interface { type ve-intf-single; description "router VE inteface"; } leaf loop-detection { type empty; description "Enable loop detection on the VLAN"; } leaf vlan-accounting { type empty; description "Enable VLAN Accounting on the VLAN"; } leaf vlan-cpu-protection { type empty; description "Enables Vlan CPU protection for "+ "unknown unicast and multicast packets"; } } leaf default-vlan-id { type vlan-identifier; description "Default VLAN identifier"; }
5 Full examples ethernet 1/10 ethernet 1/12 to 1/17 ethernet 1/4 to 1/5 ethernet 1/8 to 1/9 ethernet 1/11 ethernet 1/18 ethernet 1/12 to 1/16 ve 10
Full examples 5 vlan-accounting vlan-cpu-protection priority 6 priority force vlan 35 name Test35 tagged ethernet 2/2 to 2/3 tagged ethernet 2/6 to 2/7 tagged ethernet 2/10 tagged ethernet 2/12 to 2/17 untagged ethernet 2/4 to 2/5 untagged ethernet 2/8 to 2/9 untagged ethernet 2/11 untagged ethernet 2/18 uplink-switch ethernet 2/12 to 2/16 router-interface ve 20 loop-detection vlan-accounting vlan-cpu-protection priority 3 priority force Multi-Service IronWare YANG Configuration Guide 53-1003038-02 101
5 102 Full examples Multi-Service IronWare YANG Configuration Guide 53-1003038-02
