OC LACP
Configuring the LACP System Priority
Configuring the LACP System Priority
Request:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<lacp xmlns="http://openconfig.net/yang/lacp">
<config>
<system-priority>1</system-priority>
</config>
</lacp>
</config>
</edit-config>
</rpc>
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
lacp system-priority 1
Querying the State of the LACP System Priority (Global)
Querying the State of the LACP System Priority (Global)
Request:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<get-config>
<source>
<running/>
</source>
<filter>
<lacp xmlns="http://openconfig.net/yang/lacp">
<config>
<system-priority/>
</config>
</lacp>
</filter>
</get-config>
</rpc>
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
show lacp internal info global
Configuring the LACP Interval Rate on a Port Channel
Configuring the LACP Interval Rate on a Port Channel
Request:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<lacp xmlns="http://openconfig.net/yang/lacp">
<interfaces>
<interface>
<name>po1</name>
<config>
<interval>FAST</interval>
</config>
</interface>
</interfaces>
</lacp>
</config>
</edit-config>
</rpc>
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
interface eth1/1
lacp rate fast
Caveat: NX-API only allows configuring LACP interval rate on a port-channel member in shut state. In this example, assume eth1/1 is part of po1.
Querying the State of the LACP Interval Rate
Querying the State of the LACP Interval Rate
Request:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<get-config>
<source>
<running/>
</source>
<filter>
<lacp xmlns="http://openconfig.net/yang/lacp">
<interfaces>
<interface>
<name>po1</name>
<config>
<interval/>
</config>
</interface>
</interfaces>
</lacp>
</filter>
</get-config>
</rpc>
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
show running-config interface eth1/1
Caveat: NX-API only allows configuring LACP interval rate on a port-channel member in shut state. In this example, assume eth1/1 is part of po1.
Configuring LACP Mode
Configuring LACP Mode
Request:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<edit-config>
<target>
<running/>
</target>
<config>
<lacp xmlns="http://openconfig.net/yang/lacp">
<interfaces>
<interface>
<name>po1</name>
<config>
<lacp-mode>ACTIVE</lacp-mode>
</config>
</interface>
</interfaces>
</lacp>
</config>
</edit-config>
</rpc>
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
interface eth1/1
channel-group 1 mode active
Querying the State of the LACP Mode on the Interface
Querying the State of the LACP Mode on the Interface
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<get-config>
<source>
<running/>
</source>
<filter>
<lacp xmlns="http://openconfig.net/yang/lacp">
<interfaces>
<interface>
<name>po1</name>
<config>
<lacp-mode/>
</config>
</interface>
</interfaces>
</lacp>
</filter>
</get-config>
</rpc>
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
show running-config interface eth1/1
Querying the State of the LACP Member Data
Querying the State of the LACP Member Data
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<get>
<filter>
<lacp xmlns="http://openconfig.net/yang/lacp">
<interfaces>
<interface>
<members>
<member>
<interface>eth1/1</interface>
<state/>
</member>
</members>
</interface>
</interfaces>
</lacp>
</filter>
</get>
</rpc>
Note: Members must be in “admin up” state to query the LACP member state data.
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
show lacp interface ethernet1/1
Querying an LACP Interface
Querying an LACP Interface
Request:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<get>
<filter>
<lacp xmlns="http://openconfig.net/yang/lacp">
<interfaces>
<interface>
<name>po1</name>
<members>
<member>
<interface>eth1/10</interface>
<state/>
</member>
</members>
</interface>
</interfaces>
</lacp>
</filter>
</get>
</rpc
Response:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:6e502c5e-5ffa-48d6-8180-01b1fcb6b97d">
<data>
<lacp xmlns="http://openconfig.net/yang/lacp">
<interfaces>
<interface>
<name>po1</name>
<members>
<member>
<interface>eth1/10</interface>
<state>
<activity>ACTIVE</activity>
<aggregatable>true</aggregatable>
<collecting>true</collecting>
<distributing>true</distributing>
<interface>eth1/10</interface>
<oper-key>32768</oper-key>
<partner-id>88:F0:31:DC:BA:7D</partner-id>
<partner-key>32768</partner-key>
<partner-port-num>265</partner-port-num>
<port-num>293</port-num>
<synchronization>IN_SYNC</synchronization>
<timeout>LONG</timeout>
<counters>
<lacp-in-pkts>17</lacp-in-pkts>
<lacp-out-pkts>15</lacp-out-pkts>
<lacp-rx-errors>0</lacp-rx-errors>
</counters>
</state>
</member>
</members>
</interface>
</interfaces>
</lacp>
</data>
</rpc-reply>
Note: This example was added in Release 9.3(5).
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
show lacp interface e<>
Querying an LACP Ethernet Interface
Querying an LACP Ethernet Interface
Request:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<get>
<filter>
<lacp xmlns="http://openconfig.net/yang/lacp">
<interfaces>
<interface>
<name>po1</name>
<members/>
</interface>
</interfaces>
</lacp>
</filter>
</get>
</rpc>
Response:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="urn:uuid:cbc11386-3414-49bd-82df-52b354edd62e">
<data>
<lacp xmlns="http://openconfig.net/yang/lacp">
<interfaces>
<interface>
<name>po1</name>
<members>
<member>
<interface>eth1/12</interface>
<state>
<activity>ACTIVE</activity>
<aggregatable>true</aggregatable>
<collecting>true</collecting>
<distributing>true</distributing>
<interface>eth1/12</interface>
<oper-key>32768</oper-key>
<partner-id>88:F0:31:DC:BA:7D</partner-id>
<partner-key>32768</partner-key>
<partner-port-num>269</partner-port-num>
<port-num>301</port-num>
<synchronization>IN_SYNC</synchronization>
<timeout>LONG</timeout>
<counters>
<lacp-in-pkts>362</lacp-in-pkts>
<lacp-out-pkts>360</lacp-out-pkts>
<lacp-rx-errors>0</lacp-rx-errors>
</counters>
</state>
</member>
<member>
<interface>eth1/10</interface>
<state>
<activity>ACTIVE</activity>
<aggregatable>true</aggregatable>
<collecting>true</collecting>
<distributing>true</distributing>
<interface>eth1/10</interface>
<oper-key>32768</oper-key>
<partner-id>88:F0:31:DC:BA:7D</partner-id>
<partner-key>32768</partner-key>
<partner-port-num>265</partner-port-num>
<port-num>293</port-num>
<synchronization>IN_SYNC</synchronization>
<timeout>LONG</timeout>
<counters>
<lacp-in-pkts>364</lacp-in-pkts>
<lacp-out-pkts>362</lacp-out-pkts>
<lacp-rx-errors>0</lacp-rx-errors>
</counters>
</state>
</member>
</members>
</interface>
</interfaces>
</lacp>
</data>
</rpc-reply>
Note: This example was added in Release 9.3(5).