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

88 Network OS NETCONF Operations Guide
53-1003231-02
Fabric interface configuration management
8
<running/>
</target>
<config>
<interface xmlns="urn:brocade.com:mgmt:brocade-interface">
<tengigabitethernet>
<name>1/0/2</name>
<fabric xmlns=”urn:brocade.com:mgmt:brocade-fcoe”>
<fabric-isl>
<fabric-isl-enable/>
</fabric-isl>
</fabric>
</tengigabitethernet>
</interface>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="1202" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
NOTE
After you repair any segmented or disabled ISL ports, toggle the fabric ISL in order to propagate the
changes.
NOTE
A <shutdown> node on an operating ISL interface not only brings down the physical link but also its
FSPF adjacency. The main difference between a <shutdown> node and disabling fabric ISL is that
the link stays up after disabling fabric ISL, while the link stays down after a shutdown.
NOTE
Upon fabric reconvergence due to topology change involving the ECMP fabric-ISL path, there may be
sub-second flooding of known unicast traffic.
NOTE
Using an XGIG analyzer between switches in a Brocade VCS Fabric may cause a signal detection
timeout, causing the fabric ISL link to fail.
Enabling a fabric trunk
Fabric trunking is enabled on fabric ISLs by default. If trunking has been disabled, you can
re-enable it with the following steps.
1. Issue the <edit-config> RPC to configure the <interface> node in the
urn:brocade.com:mgmt:brocade-interface namespace.
2. Under the <interface> node, include the <gigabitethernet>, <tengigabitethernet>,
<fortygigabitethernet>, or <hundredgigabitethernet> node element.
3. Under the <gigabitethernet>, <tengigabitethernet>, <fortygigabitethernet>, or
<hundredgigabitethernet> node element, include the <name> leaf element and specify the
name of the interface on which you want to enable fabric trunking. Specify the name in
[rbridge-id/]slot/port format.