Brocade Network OS NETCONF Operations Guide v4.1.1 - Manual (Page 305)

Network OS NETCONF Operations Guide 273
53-1003231-02
Configuring FCoE interfaces
20
<fcoeport-map>default</fcoeport-map>
</fcoeport>
</tengigabitethernet>
</interface>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="1800" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
5. Confirm the changes to the interface using the <get-config> RPC with a subtree filter to return
only the <fcoeport> node information of the 1/0/1 interface.
The output returns the FCoE mapping association for the interface.
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="1801" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-config>
<source>
<running/>
</source>
<filter type="subtree">
<interface xmlns="urn:brocade.com:mgmt:brocade-interface">
<tengigabitethernet>
<name>1/0/1</name>
<fcoeport xmlns="urn:brocade.com:mgmt:brocade-fcoe"/>
</tengigabitethernet>
</interface>
</filter>
</get-config>
</rpc>
<rpc-reply message-id="1801" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<interface xmlns="urn:brocade.com:mgmt:brocade-interface">
<tengigabitethernet>
<name>1/0/1</name>
<fcoe:fcoeport>
<fcoe:fcoeport-map>default<fcoe:fcoeport-map>
</fcoe:fcoeport>
</tengigabitethernet>
</interface>
</rpc-reply>
6. Repeat this procedure for any additional interfaces.
Assigning an FCoE map onto a LAG member
You can assign an FCoE map to a LAG that connects an FCoE Forwarder (FCF) to a Data Center
Bridging (DCB) switch or a FIP Snooping Bridge (FSB) switch. After applying the FCoE map, all
member ports of the LAG carry FCoE traffic.
NOTE
You cannot assign an FCoE map to a vLAG or to redundant LAGs connecting different FCFs from
different VCS Fabrics.