Configuring physical interfaces – Brocade Network OS NETCONF Operations Guide v4.1.1 User Manual
Page 348
316
Network OS NETCONF Operations Guide
53-1003231-02
Virtual Fabric configuration with NETCONF overview
23
</interface-vlan>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="1104" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="1105" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config>
<interface-vlan xmlns="urn:brocade.com:mgmt:brocade-interface">
<interface>
<vlan>
<name>5000</name>
<private-vlan>
<association>
<sec-assoc-add>7000</sec-assoc-add>
</association>
</private-vlan>
</vlan>
</interface>
</interface-vlan>
</config>
</edit-config>
</rpc>
<rpc-reply message-id="1105" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
Configuring physical interfaces
The physical interfaces can be configured in the following five types:
•
Switchport-private-vlan-host mapped to isolated or community VLANs associated on the
access port.
•
Switchport-private-vlan-trunk-host mapped to isolated or community VLANs associated on the
trunk port.
•
Switchport-private-vlan-promiscuous mapped to primary VLANs associated on the access port.
•
Switchport-private-vlan-trunk-promiscuous mapped to primary VLANs associated on the trunk
port.
•
Switchport-private-vlan-trunk mapped to primary, isolated, community, or standard VLANs
associated on the trunk port.
The following task is one possible example of configuring the physical interface. For additional
examples, refer to
“Configuring a trunk Virtual Fabric with a range of C-TAGs”