Configuring a port-profile-port – Brocade Network OS NETCONF Operations Guide v4.1.1 User Manual
Page 296

264
Network OS NETCONF Operations Guide
53-1003231-02
Configuring a port-profile-port
19
</last-recevied-interface-info>
</get-port-profile-for-intf>
</rpc>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1732">
<interface xmlns="urn:brocade.com:mgmt:brocade-port-profile-ext">
<interface-type>tengigabitethernet</interface-type>
<interface-name>9/0/54</interface-name>
<port-profile>
<name>auto-for_iscsi</name>
</port-profile>
</interface>
<has-more>false</has-more>
</rpc-reply>
Configuring a port-profile-port
This section describes the tasks for configuring a port-profile-port on a physical interface.
Configure the port-profile-port on the physical interface.
To configure a port-profile-port assignment on an interface, issue the <edit-config> RPC to
configure the <interface> node in the urn:brocade.com:mgmt:brocade-interface namespace and
specify the following elements.
1. Under the <interface> node, specify the <gigabitethernet>, <tengigabitethernet>,
<fortygigabitethernet>, <hundredgigabitethernet>, or <port-channel> element, depending on
the type of interface you want to work on.
2. Under the <gigabitethernet>, <tengigabitethernet>, <fortygigabitethernet>,
<hundredgigabitethernet>, or <port-channel> element, use the <name> element to specify
the interface for which you want to add the association with a port-profile.
3. Under the <gigabitethernet>, <tengigabitethernet>, <fortygigabitethernet>,
<hundredgigabitethernet>, or <port-channel> element, specify the <port-profile-port> element
tag.
The following example configures the port-profile assignment from interface 1/0/1.
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="1720" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config>
<interface xmlns="urn:brocade.com:mgmt:brocade-interface">
<tengigabitethernet>
<name>1/0/1</name>
<port-profile-port/>
</tengigabitethernet>
</interface>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="1720" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">