Configuring an interface port as a trunk interface – Brocade Network OS NETCONF Operations Guide v4.1.1 User Manual

Page 317

Advertising

Network OS NETCONF Operations Guide

285

53-1003231-02

VLAN configuration and management

6. Under the <gigabitethernet>, <tengigabitethernet>, <fortygigabitethernet>, or

<hundredgigabitethernet> element, include the following elements:

a. In the <name> element, specify the same port name you specified in

step 3

b. Include the <switchport>/<access> hierarchy of node elements.

7. Under the <access> node element, specify the <access-vlan> leaf element containing the

VLAN ID to configure a layer 2 switch port as an access interface.

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

<edit-config>

</target>

</access>

</switchport>

</tengigabitethernet>

</interface>

</config>

</edit-config>

</rpc>

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

<ok/>

</rpc-reply>

Configuring an interface port as a trunk interface

Each DCB interface port supports admission policies based on whether the frames are untagged or
tagged. Trunk mode admits only VLAN-tagged frames.

This procedure performs the following functions:

•

Enables the interface.

•

Specifies trunk mode.

•

Specifies whether one, all, or none of the VLAN interfaces are allowed to transmit and receive
through the DCB interface.

To configure the interface as a trunk interface requires two RPCs. The first RPC configures the port
as a Layer 2 interface; the second RPC configures the interface port as a trunk interface.

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

urn:brocade.com:mgmt:brocade-interface namespace.

2. Under the <interface> node, specify the interface type element (<gigabitethernet>,

<tengigabitethernet>, <fortygigabitethernet>, or <hundredgigabitethernet>).

3. Under the <gigabitethernet>, <tengigabitethernet>, <fortygigabitethernet>, or

<hundredgigabitethernet> element, include the following elements:

Advertising