Releasing a port from a pod set – Brocade Network OS NETCONF Operations Guide v4.1.1 User Manual

Page 102

Advertising

Network OS NETCONF Operations Guide

53-1003231-02

Overriding Dynamic POD assignments

4. Issue the <get-config> RPC to retrieve the DPOD configuration for the ports you reserved in

step 1

to verify that the ports are reserved.

?xml version="1.0" encoding="UTF-8"?>

<get-config>

</target>

<port-id>

<port-id>5/0/10</port-id>

<port-id>5/0/11</port-id>

</port-id>

</dpod>

</filter>

</get-config>

</rpc>

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="719">

<port-id>

<port-id>5/0/10</port-id>

<operation>reserve</operation>

</port-id>

<port-id>

<port-id>5/0/11</port-id>

<operation>reserve</operation>

</port-id>

</dpod>

</rpc-reply>

Releasing a port from a POD set

Once a port has been assigned to a Dynamic POD license port set, it remains licensed (or
“reserved”) until you remove the port from the port set. You remove a port from the port set by
editing the DPOD configuration with the <edit-config> RPC. Releasing a port removes it from the
Dynamic POD license port set; the port appears as unassigned until it comes back online.

To prevent a port from coming back online and taking a POD assignment, disable the port and save
the running configuration. This action will disable the port persistently.

A port POD assignment can only be released if the port is currently offline. Shut the port down to
disable the port or disable the switch if you plan to release multiple ports.

1. Issue the <edit-config> RPC to configure the <interface> node in the

urn:brocade.com:mgmt:brocade-interface namespace to shut down the interface.

The following example shuts down interface 1/0/10.

<?xml version="1.0" encoding="UTF-8"?>

<edit-config>

</target>

Advertising