Picos 2.1.0 l2 l3 Configuration Guide
Picos 2.1.0 l2 l3 Configuration Guide
This guide provides the configuration commands of L2/L3 for PicOS 2.1.0.
Pica8, Inc. makes no warranty of any kind with regard to this material, including, but not limited to, the
implied warranties of merchantability and fitness for a particular purpose. The information is provided “as
is” without warranty of any kind, and is subject to change without notice.
Table of Contents
TABLE OF CONTENTS ............................................................................................................ 3
PREFACE .................................................................................................................................. 6
Intended Audience ................................................................................................................................................................6
PicOS Documents .................................................................................................................................................................6
Organization .........................................................................................................................................................................6
Preface
Intended Audience
This guide is intended for data center administrators, system administrators, and customer service staffs
responsible for monitoring or configuring PicOS L2/L3.
PicOS Documents
The PicOS documents are available on our Pica8 website:
http://www.pica8.com/portal/
Organization
This configuration guide is organized as follows:
Chapter Description
Chapter 1. Overview
This chapter provides an overview of PicOS L2/L3 features, including Layer2 switching and
Layer3 routing.
L2/L3Features List
PicOS L2/L3 supports Layer2 switching (STP, RSTP, MSTP, MAC learning, Q-in-Q) and Layer3 routing
(static routing, RIPv2, OSPF, IGMP, PIM-SM, IPv6):
Support for configuration versioning and rollback; compares the two configurations for
differences
Device
Configuration, Ability to import/export configuration files, device software, and logs from a file on a remote server
Software,& File (tftp/scp as possible options)
Management
Ping tool and Traceroute tool from CLI
SSH tool and telnet tool from CLI
Ability to view and configure MAC/ARP table information
Support for LLDP protocols for detecting devices on a link
Support for LACP protocol andhashing of traffic using Src/Dst MAC address, Src/Dst IP
address, and Layer4 port information and mlag
Support for 802.1q trunked interfaces, for both single and LAG interfaces
Support for 802.1q tagged/untagged interfaces and native tags
Support for Q-in-Q
Layer2 Forwarding Support for Jumbo Frame
and Protocol
Support for 802.1d Spanning Tree Protocol (STP)
Support for 802.1w rapid STP (RSTP)and Per-VLAN Spanning Tree(PVST)
Support for 802.1s Multiple Spanning Tree protocol (MSTP)
Support for functionality of BPDU Guard / Filter/UDLD etc.
Support for storm-control for unicast, multicast, broadcast
Support foringress/egress port mirroring
Note: You can modify the baud rate of the switch. For that, enter the U-Boot and configure the baud rate (or other
parameters).
Eaxmple:
U-Boot 1.3.0 (Sep 8 2010 - 17:20:00)
Clock Configuration:
CPU: 825 MHz, CCB: 330 MHz,
DDR: 165 MHz, LBC: 41 MHz
L1: D-cache 32 kB enabled
I-cache 32 kB enabled
I2C: ready
DRAM: Initializing
DDR: 512 MB
FLASH: 32 MB
L2 cache 256KB: enabled
Set ethaddr MAC address = c8:0a:a9:04:49:1a
Set eth1addr MAC address = c8:0a:a9:04:49:1b
In: serial
Out: serial
Err: serial
Net: TSEC0, TSEC1
IDE: Bus 0: OK
Device 0: Model: CF Card Firm: Ver2.35 Ser#: 7DF70707030700224009
Type: Hard Disk
Capacity: 1923.9 MB = 1.8 GB (3940272 x 512)
Hit any key to stop autoboot: 0
You should not interupt the default boot process unless you want to upgrade, fix the file system or change the console
port settings (see documentation about upgrading or downgrading a Pica8 Switch).
The system has 2 default users: root and admin. The default password to both of them is “pica8”. If you login as root,
system will drop into Linux shell and you have the Linux root prilege. Yochange the switch mode (L2/L3 or OVS). Using
admin will bring the switch into the L2/L3 mode by default.
If you want to change the PicOS boot mode (from L2/L3 to OVS for example), you have to log as root user and use
the command “picos_boot”. The switch will display the software menu as follows:
XorPlus login: root
Password:
root@XorPlus#picos_boot
Please configure the default system start-up options:
(Press other key if no change)
[1] PicOS L2/L3
[2] PicOS Open vSwitch/OpenFlow
[3] No start-up options * default
Enter your choice (1,2,3):
Option 1,PicOS l2/l3 is Xorplus.when you choose option1, after a reboot PicOS will load Xorplus.
Option 2, OpenvSwitch (OVS), is an open source project ported to PicOS (refer to PicOS OVS
Configuration Guide for details) when you choose option2, after a reboot PicOS will load
OpenvSwitch.
This configuration guide is describing the behavior of PicOS in L2/L3 Mode (Option 1).
In L2/L3 mode, the login session should look like the following:
Synchronizing configuration...OK.
Pica8 PicOS Version 2.1
Welcome to PicOS L2/L3 on XorPlus
XorPlus>
XorPlus> configure
Entering configuration mode.
There are no other users in configuration mode.
[edit]
XorPlus#
Switch to the execution mode from the configuration mode without any uncommitted configurations.
XorPlus# exit
XorPlus>
[edit]
XorPlus#
(2)Configure DHCP snooping binding file and timeout
XorPlus# set protocols dhcp snooping binding file /tmp/run/dhcp_bind //sync the dhcp snooping
table to disk
[edit]
XorPlus# set protocols dhcp snooping binding timeout 8
[edit]
XorPlus# com
Merging the configuration.
Commit OK.
Save done.
[edit]
(3) Configure DHCP snooping trust port
XorPlus# set protocols dhcp snooping port ge-1/1/2 trust true //(DHCP reply is trusted),
usually, the port connect to
DHCP server should be enable
this.
[edit]
XorPlus# commit
Merging the configuration.
Commit OK.
Save done.
[edit]
ConfiguringAAA (Authentication/Authorization/Accounting)
PicOSL2/L3 supports AAA (Authentication/Authorization/Accounting). A user who is authenticated by the AAA
server (referred to as “admin” in our guide) may configure the switch. PicOSL2/L3 supports TACACS+ and
RAIUS protocols.Radius protocols only support two levels: read-only and super-user.
}
}
accounting {
disable: false
server-ip 10.10.50.41 {
shared-key: "testing123"
}
}
[edit]
XorPlus#
key = pica8
# Accounting File
accounting file = /var/tmp/acctfile
default authentication = file /etc/passwd
user = admin {
member = admins
}
group = admins {
global = cleartext "password"
service = exec {
default attribute = permit
}
}
user = operator {
global = cleartext "operator"
service = exec {
default attribute = permit
}
}
user = ychen {
global = cleartext "ychen"
member = admins
service = exec {
default attribute = permit
}
}
Users should add “/usr/share/freeradius/dictionary.pica8” to radius server before the configuration.
Radius server configuration:
Framed-MTU = 1500,
Framed-Compression = Van-Jacobsen-TCP-IP,
Class = "super-user"
Following theconfiguration above, the admin or operator can access the switch viatelnet or SSH.
Any validCLI commands executed by the admin or operator will be recordedto the specified accounting
file. In our example above,the accounting file is/var/tmp/acctfile.
In theconfiguration above, you cannot log in to the switch with a local account.
Configuring IPFIX
(1) ConfiguringIPFIX parameters
By default, IPFIX is disabled. You can enable IPFIX and configure its parameters as shown below. Make
sure the switch can connect to the IPFIX collector server correctly.
[edit]
XorPlus# set protocols ipfix interfaces ingress ge-1/1/1
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
ConfiguringsFlow
(1) Globally enabling sFlow
By default, sFlow is disabled. You can enable sFlow and configure itsparameters.Check that the switch
can connect to thesFlow collector server correctly, and be sure to configure the sFlow agent-idand
source-addressat the same time that you enable sFlow, as shown below:
In the current version, sFlow samples only the ingress traffic of each interface. You can monitor the traffic
with sFlowTrendas follows:
Figure 2-1.sFlowTrendtools.
Configuring SNMP
(1) ConfiguringSNMP parameters
By default, SNMP is disabled. You can enable SNMP and configure its parameters (e.g. community,
contact, location)as shown below:
In the example below, the system will log messages for Info, Warning, Error, and Fatal, since the system
syslog level is set to Info.
You can display the log messageson theconsole screen by entering the following command:
XorPlus# exit
XorPlus> syslog monitor on
If the switch’s sysloglevel is Trace, the traceoptions of the modules should be turned on, as shown below.
You can also turn on the OSPF traceoptions for debugging.
XorPlus#
Oct 17 15:22:42 XorPlus local0.warn : admin logined the switch
Oct 17 15:22:50 XorPlus local0.warn pica_sh: Tacacs send acct body send failed: wrote -1 of 127:
Connection refused
Revision ID : 10863
The image will be placed under the local installation directory (/cftmp). The system will decompress
pica.tar.gzautomatically when rebooted,updating only the PicOS Software.
The image will be placed under the local installation directory (/cftmp). The system will
decompressrootfs.tar.gz automatically when rebooted, updating both the PicOS Platform and PicOS
Software.
port-destination {
disable: false
}
}
}
XorPlus# run show system rollback list
-rw-rw-r-- 1 root xorp 23478 Jul 7 22:55 /pica/config/pica.conf
-rw-rw-r-- 1 root xorp 23595 Jul 7 22:28 /pica/config/pica.conf.01
-rw-rw-r-- 1 admin xorp 23595 Jul 7 22:27 /pica/config/pica.conf.02
-rw-rw-r-- 1 root xorp 23595 Jul 7 22:26 /pica/config/pica.conf.03
Technical Support
Execute the diagnosis CLI, and receive technical support by sending the diagnosis result report to Pica8.
Installing Software
You can install software that you’d like to have inyour Debian system(e.g.make, python, g++) as shown below:
ecmp {
max-path: 4
hash-mapping {
field {
ingress-interface {
disable: false
}
vlan {
disable: false
}
ip-protocol {
disable: false
}
ip-source {
disable: false
}
ip-destination {
disable: false
}
port-source {
disable: false
}
port-destination {
disable: false
}
}
}
}
XorPlus# show
Waiting for building configuration.
interface {
gigabit-ethernet "ge-1/1/1" {
ether-options {
}
}
gigabit-ethernet "ge-1/1/2" {
ether-options {
}
}
gigabit-ethernet "ge-1/1/3" {
ether-options {
}
family {
ethernet-switching {
native-vlan-id: 2
}
}
}
gigabit-ethernet "ge-1/1/4" {
ether-options {
}
family {
ethernet-switching {
native-vlan-id: 3
}
}
}
gigabit-ethernet "ge-1/1/5" {
ether-options {
}
}
……….
XorPlus#
XorPlus# show all
Waiting for building configuration.
interface {
ecmp_path_max: 4
gigabit-ethernet "ge-1/1/1" {
mtu: 1514
disable: false
ether-options {
flow-control: true
}
}
gigabit-ethernet "ge-1/1/2" {
mtu: 1514
disable: false
ether-options {
flow-control: true
}
}
gigabit-ethernet "ge-1/1/3" {
mtu: 1514
disable: false
ether-options {
flow-control: true
}
family {
ethernet-switching {
native-vlan-id: 2
port-mode: "access"
}
}
}
● The maximum rollback file is limited to 50. The current configuration is located in pica.conf.
XorPlus# rollback 1
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
}
XorPlus>
commit
● An LLDP PDU includes 4 basic TLVs and several optional TLVs. Basic TLVs include the Chassis ID, Port
ID,TTL, and End TLVs.
● Both static and LACP LAGs can support the hashing of traffic using the Src/Dst MAC address, the Src/Dst IP
address, and Layer 4 port information.
● If all member ports of a LAN are link-down, the LAG will be link-down. The LAG will become link-up when at
least one member port is link-up.
●The logical function and configuration of LAGs are same as those of a physical port.
● The LACPDU includes the LACP system priority, the system’s MAC, the port priority and I.D. The port,
included in the LACP LAG, will transmit the LACPDU to its neighbors.
● The configuration of the LACP LAG is similar to that of the static LAG.
● min-selected-port denotes that the LAG is up only when no fewer than the defined number of ports are up.
Below, our defined number is 4.
Description:
Link-level type: Ethernet, MTU: 1514, Speed: Auto, Duplex: Auto
Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled
Interface flags: Hardware-Down SNMP-Traps Internal: 0x0
Current address: 60:eb:69:d2:9c:d7, Hardware address: 60:eb:69:d2:9c:d7
Traffic statistics:
5 sec input rate 0 bits/sec, 0 packets/sec
5 sec output rate 0 bits/sec, 0 packets/sec
Input Packets............................0
Output Packets...........................0
Input Octets.............................0
Output Octets............................0
Aggregated link protocol: LACP
Minimum number of selected ports: 4
Members Status Port Speed
--------- ---------- ----------
ge-1/1/1 up(active) Auto
ge-1/1/2 up(active) Auto
ge-1/1/3 up(active) Auto
ge-1/1/4 up(active) Auto
SwitchA SwitchB
Link C
Link A Link B
LAG
SwitchC
There are two issues in the MLAG: Mac entry synchronization and broadcast traffic control. Mac entry synchronization
means the Mac entry which learned by the interface should be synchronized by the peer switch. In current version, we
only support 2 nodes in a MLAG and use L2 traffic to communicate between the nodes.
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
LAG3
Te-1/1/50 Te-1/1/50
LAG1 LAG2
Ge-1/1/1 NIC 2
Ge-1/1/2 NIC /2
SwitchC ServerA
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
XorPlus#
Configuring Mirroring
You can configure one (1) mirror to analyze traffic.Configure the source/destination port (also called the
input/output port).
The output port does not belong to any VLAN, and will not participate in Layer2 or Layer3 forwarding.
●Access ports belongtonative VLANs, whiletrunk ports can belong to more than one VLAN ( including the
native VLAN.)
Te-1/1/49 Te-1/1/49
Switch A Switch B
ge-1/1/3 ge-1/1/4
ge-1/1/3 ge-1/1/4
Vlan.3 Vlan.3
Vlan.3 Vlan.3
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/2 family ethernet-switching native-vlan-id 2
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/3 family ethernet-switching port-mode access
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/3 family ethernet-switching native-vlan-id 3
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/4 family ethernet-switching port-mode access
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/4 family ethernet-switching native-vlan-id 3
[edit]
XorPlus#set interface gigabit-ethernet te-1/1/49 family ethernet-switching port-mode trunk
[edit]
XorPlus#set interface gigabit-ethernet te-1/1/49 family ethernet-switching vlan members 2
[edit]
XorPlus#set interface gigabit-ethernet te-1/1/49 family ethernet-switching vlan members 3
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
XorPlus# run show vlans
VlanID Tag Interfaces
------ -------- ------------------------------------------------------
1 tagged
untagged ge-1/1/5, ge-1/1/6, ge-1/1/7, ge-1/1/8, ge-1/1/9,
ge-1/1/10, ge-1/1/11, ge-1/1/12, ge-1/1/13, ge-1/1/14,
ge-1/1/15, ge-1/1/16, ge-1/1/17, ge-1/1/18, ge-1/1/19,
ge-1/1/20, ge-1/1/21, ge-1/1/22, ge-1/1/23, ge-1/1/24,
ge-1/1/25, ge-1/1/26, ge-1/1/27, ge-1/1/28, ge-1/1/29,
ge-1/1/30, ge-1/1/31, ge-1/1/32, ge-1/1/33, ge-1/1/34,
ge-1/1/35, ge-1/1/36, ge-1/1/37, ge-1/1/38, ge-1/1/39,
ge-1/1/40, ge-1/1/41, ge-1/1/42, ge-1/1/43, ge-1/1/44,
ge-1/1/45, ge-1/1/46, ge-1/1/47, ge-1/1/48, te-1/1/49,
te-1/1/50, te-1/1/51, te-1/1/52,
2 tagged te-1/1/49,
untagged ge-1/1/1, ge-1/1/2,
3 tagged te-1/1/49,
untagged ge-1/1/3, ge-1/1/4,
●Q-in-Q tunneling is useful when customers have overlapping VLAN IDs, because the customer’s 802.1Q VLAN
tags are prependedby the service VLAN tag. The L2/L3implementation of Q-in-Q tunneling supports the IEEE
802.1ad standard.
●The Q-in-Q tunneling external mode belongs to basic Q-in-Q, while the Q-in-Q tunneling internal mode belongs
to selective Q-in-Q.
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
Ingress: t2
Untagged-type Enabled: false
One-tagged-type Customer Vlan: 20
Double-tagged-type Service Vlan: 0
New Service Vlan: 200
New Customer Vlan: 0
Ingress: t3
Untagged-type Enabled: false
One-tagged-type Customer Vlan: 30
Double-tagged-type Service Vlan: 0
New Service Vlan: 300
New Customer Vlan: 0
XorPlus#
[edit]
XorPlus#
XorPlus# run show interface gigabit-ethernet ge-1/1/1 dot1q-tunneling
Dot1q Tunneling Mode: internal, Ether Type: 0x8100
Egress: t1
Service Vlan: 100
Customer Vlan: 10
Action: Strip both tags
Egress: t2
Service Vlan: 200
Customer Vlan: 20
Action: Retain the customer vlan tag
Egress: t3
Service Vlan: 300
Customer Vlan: 30
Action: Retain the customer vlan tag
XorPlus#
Customer A Customer B
Ge-1/1/1 Ge-1/1/1
Ge-1/1/2 Ge-1/1/2
Customer C Customer D
VLAN 20 VLAN 20
untaged untaged
● Configure the untagged frames received by the port with the customer VLAN tag30 and service VLAN
Tag 100.
● Configure the customer VLAN tag 10 frames received by the port with the service VLAN Tag 100.
[edit]
● Configure VLAN 200 as the default VLAN of GigabitEthernet ge-1/1/2, and enable the Q-in-Q
tunneling internal mode on GigabitEthernet ge-1/1/2.
● Configure the untagged frames received by the port with the customer VLAN tag30 and service VLAN
Tag 200.
● Configure the customer VLAN tag20frames received by the port with the service VLAN Tag 200.
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# run show interface gigabit-ethernet ge-1/1/2 dot1q-tunneling
Dot1q Tunneling Mode: internal, Ether Type: 0x8100
Ingress: t5
Untagged-type Enabled: true
One-tagged-type Customer Vlan:
Double-tagged-type Service Vlan: 0
New Service Vlan: 200
New Customer Vlan: 30
Ingress: t6
Untagged-type Enabled: false
One-tagged-type Customer Vlan: 20
Double-tagged-type Service Vlan: 0
New Service Vlan: 200
New Customer Vlan: 0
Egress: t7
Service Vlan: 200
Customer Vlan: 20
Action: Retain the customer vlan tag
Egress: t8
Service Vlan: 200
Customer Vlan: 30
Action: Strip both tags
XorPlus#
Configure VLAN 100/200 as the trunk port of GigabitEthernet te-1/1/49, and enable the Q-in-Q tunneling
internal mode.
● Configure the untagged frames received by the port with the customer VLAN tag30 and service VLAN
Tag 100.
● Configure the customer VLAN tag 10 frames received by the port with the service VLAN Tag 100.
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# run show interface gigabit-ethernet ge-1/1/1 dot1q-tunneling
Dot1q Tunneling Mode: internal, Ether Type: 0x8100
Ingress: t1
Untagged-type Enabled: true
One-tagged-type Customer Vlan:
Double-tagged-type Service Vlan: 0
New Service Vlan: 100
New Customer Vlan: 30
Ingress: t2
Untagged-type Enabled: false
One-tagged-type Customer Vlan: 10
Double-tagged-type Service Vlan: 0
New Service Vlan: 100
New Customer Vlan: 0
Egress: t3
Service Vlan: 100
Customer Vlan: 10
Action: Retain the customer vlan tag
Egress: t4
Service Vlan: 100
Customer Vlan: 30
Action: Strip both tags
XorPlus#
●Configure VLAN 200 as the default VLAN of Gigabit Ethernet ge-1/1/2, and enable the Q-in-Q tunneling
internal mode on Gigabit Ethernet 1/1/2.
● Configure the untagged frames received by the port with the customer VLAN tag 30 and service VLAN
Tag 200.
● Configure the customer VLAN tag 20 frames received by the port with the service VLAN Tag 200.
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# run show interface gigabit-ethernet ge-1/1/2 dot1q-tunneling
Dot1q Tunneling Mode: internal, Ether Type: 0x8100
Ingress: t5
Untagged-type Enabled: true
One-tagged-type Customer Vlan:
Double-tagged-type Service Vlan: 0
New Service Vlan: 200
New Customer Vlan: 30
Ingress: t6
Untagged-type Enabled: false
One-tagged-type Customer Vlan: 20
Double-tagged-type Service Vlan: 0
New Service Vlan: 200
New Customer Vlan: 0
Egress: t7
Service Vlan: 200
Customer Vlan: 20
Action: Retain the customer vlan tag
Egress: t8
Service Vlan: 200
Customer Vlan: 30
Action: Strip both tags
XorPlus#
Configure VLAN 100/200 as the trunk port of Gigabit Ethernet te-1/1/49, and enable the Q-in-Q tunneling
internal mode.
MSTP Configuration
802.1D, 802.1w, and 802.1s are spanning tree protocols that can avoid the loop in Layer2. You can configure the
parameters of MSTP,including bridge-priority, forward-delay, max-age, and hello-time interval.
[edit]
XorPlus# set vlans vlan-id 400
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# set protocols spanning-tree mstp msti 1
[edit]
XorPlus# set protocols spanning-tree mstp msti 2
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# set protocols spanning-tree mstp msti 1 vlan 100
[edit]
XorPlus# set protocols spanning-tree mstp msti 1 vlan 200
[edit]
XorPlus# set protocols spanning-tree mstp msti 2 vlan 300
[edit]
XorPlus# set protocols spanning-tree mstp msti 2 vlan 400
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
XorPlus# run show spanning-tree mstp bridge
Bridge Spanning Tree Parameters
Enabled Protocol: MSTP
Root ID: 4096.08:9e:01:39:1a:fe
External Root Path Cost: 0
CIST Regional Root ID: 4096.08:9e:01:39:1a:fe
Root Port:
CIST Internal Root Path Cost: 0
Hello Time: 2
Maximum Age: 20
Forward Delay: 20
Remaining Hops: 8
Bridge Configuration Name: test1
Bridge Configuration Digest: 8b5d98ca042bad0d7fa5f18744f4755d
Msti 1 Member VLANs:
100, 200,
Msti 2 Member VLANs:
300, 400,
Number of Topology Changes: 14
Time Since Last Topology Change: 0 days 00:02:49
Local Parameters
Bridge ID: 4096.08:9e:01:39:1a:fe
Hello Time: 2
Maximum Age: 20
Forward Delay: 20
Remaining Hops: 8
XorPlus#
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
PVST Configuration
802.1D, 802.1w, and 802.1s are spanning tree protocols thatcan avoid the loop in Layer2. You can configure the
parameters of PVST, including bridge-priority, forward-delay, max-age, and hello-time interval.
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
XorPlus# run show spanning-tree pvst bridge vlan 2
PVST Bridge Parameters for VLAN 2
Root Bridge: 32769.08:9e:01:61:65:71
Root Cost: 0
Root Port:
Hello Time: 2
Max Age: 20
Forward Delay: 15
Time Since Last Topology Change: 15804 days 23:00:11
Local Parameters
Bridge ID: 32769.08:9e:01:61:65:71
Hello Time: 2
Maximum Age: 20
Forward Delay: 15
XorPlus# set protocols spanning-tree pvst vlan 2 enable true
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
XorPlus# run show spanning-tree pvst bridge vlan 2
PVST Bridge Parameters for VLAN 2
Root Bridge: 4098.08:9e:01:61:65:71
Root Cost: 0
Root Port:
Hello Time: 4
Max Age: 30
Forward Delay: 20
Time Since Last Topology Change: 0 days 00:00:21
Local Parameters
Bridge ID: 4098.08:9e:01:61:65:71
Hello Time: 4
Maximum Age: 30
Forward Delay: 20
XorPlus#
Commit OK.
Save done.
[edit]
XorPlus# set protocols spanning-tree enable false
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
● In order to achieve load balancing, VLAN 100 should be in MSTI-1 (Fig. 4-4), and VLAN 200 should be in MSTI-
2 (Fig. 4-5).
Switch A Switch B
Ge-1/1/3
Ge-1/1/1 Ge-1/1/1 Ge-1/1/3
Ge-1/1/2 Ge-1/1/2
VLAN VLAN
VLAN 100,200 VLAN
100,200 100,200 100,200
Ge-1/1/1 Ge-1/1/2
Ge-1/1/1 Ge-1/1/2
Ge-1/1/2 Ge-1/1/1
Regional Root
Switch A Switch B
Ge-1/1/3
Ge-1/1/1 Ge-1/1/1 Ge-1/1/3
Ge-1/1/2 Ge-1/1/2
VLAN 100
VLAN 100
VLAN 100 VLAN 100
Ge-1/1/1 Ge-1/1/2
Ge-1/1/1 Ge-1/1/2
Ge-1/1/2 Ge-1/1/1
Regional Root
Switch A Switch B
Ge-1/1/3
Ge-1/1/1 Ge-1/1/1 Ge-1/1/3
Ge-1/1/2 Ge-1/1/2
VLAN 200
VLAN 200
VLAN 200 VLAN 200
Ge-1/1/1 Ge-1/1/2
Ge-1/1/1 Ge-1/1/2
Ge-1/1/2 Ge-1/1/1
[edit]
XorPlus#
To make sure that Switch A is the root of the network and the regional root of MSTI-1, configure it as the
higher priority.
To make sure that Switch B is the regional root of MSTI-2, and that ge-1/1/2 and ge-1/1/3 are in blocking
statusin MSTI-1, you should configure a higher MSTI-2 priority, and a largevalue for internal-path-cost in
MSTI-1.
● To set ge-1/1/1 and ge-1/1/2 in forwarding statusin MSTI-1, configure a lower value for internal-path-
cost.
● To set ge-1/1/1 in blocking status in MSTI-2, configure a higher value for internal-path-cost.
XorPlus# set protocols spanning-tree mstp msti 1 interface ge-1/1/1 cost 1000
[edit]
XorPlus# set protocols spanning-tree mstp msti 1 interface ge-1/1/2 cost 1000
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# set protocols spanning-tree mstp msti 2 interface ge-1/1/1 cost 100000
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
To set ge-1/1/1 in blocking statusin MSTI-2 and ge-1/1/2 in blocking status in MSTI-1, configure a large
value for internal-path-cost.
XorPlus# set protocols spanning-tree mstp msti 2 interface ge-1/1/1 cost 10000000
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# set protocols spanning-tree mstp msti 1 interface ge-1/1/2 cost 10000000
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
● To set ge-1/1/1 and ge-1/1/2 in forwarding status in MSTI-2, configure a lower value for internal-path-
cost.
● To set ge-1/1/2 in blocking status in MSTI-1, configure a large value for internal-path-cost.
XorPlus# set protocols spanning-tree mstp msti 2 interface ge-1/1/1 cost 1000
[edit]
XorPlus# set protocols spanning-tree mstp msti 2 interface ge-1/1/2 cost 1000
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# set protocols spanning-tree mstp msti 1 interface ge-1/1/2 cost 10000000
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
● Inour second example, there are two regions. In region 1, VLAN 100 is mapped to MSTI-1, VLAN 200 is
mapped to MSTI-2, and VLAN 300 is mapped to MSTI-3. In region 2, VLAN 200 is mapped to MSTI-2, and
VLAN 400 is mapped to MSTI-4. Switch A is the root of the entire network.
● The topologies of the VLANs are presented in Fig. 4-6 through 4-10.
Switch A ROOT
Ge-1/1/1 Ge-1/1/2
Ge-1/1/1 Ge-1/1/1
Switch B Switch C
Ge-1/1/2 Ge-1/1/2
Ge-1/1/3 Ge-1/1/3
Region 1
Ge-1/1/1 Ge-1/1/1
Ge-1/1/3 Ge-1/1/3
Region 2
Ge-1/1/1 Ge-1/1/2
Switch B Switch C
Ge-1/1/2 Ge-1/1/2
Ge-1/1/3 Ge-1/1/3
Region 1
VLAN 100
Ge-1/1/1 Ge-1/1/1
VLAN 100
Switch D Ge-1/1/2 Ge-1/1/2 Switch E
Switch A
Ge-1/1/1 Ge-1/1/2
VLAN 200
Ge-1/1/1 Ge-1/1/1
Regional Root
Switch B VLAN 200 Switch C
Ge-1/1/2 Ge-1/1/2
Ge-1/1/3 Ge-1/1/3
Region 1
VLAN 200
Ge-1/1/1 Ge-1/1/1
VLAN 200
Switch D Ge-1/1/2 Ge-1/1/2 Switch E
Switch A
Ge-1/1/1 Ge-1/1/2
VLAN 300
Ge-1/1/1 Ge-1/1/1 Regional
Root
Switch B VLAN 300 Switch C
Ge-1/1/2 Ge-1/1/2
Ge-1/1/3 Ge-1/1/3
Region 1
VLAN 300
Ge-1/1/1 Ge-1/1/1
VLAN 300
Switch D Ge-1/1/2 Ge-1/1/2 Switch E
Ge-1/1/1 Ge-1/1/2
Switch B Switch C
Ge-1/1/2 Ge-1/1/2
Ge-1/1/3 Ge-1/1/3
Region 1
VLAN 400
Ge-1/1/1 Ge-1/1/1
VLAN 400
Switch D Ge-1/1/2 Ge-1/1/2 Switch E
To make sure that Switch A is the root of the network and the regional root of MSTI-1, configure it as the
higher priority.
Configure ge-1/1/1~ge-1/1/3 as trunk ports, and as members of VLAN 100, VLAN 200, VLAN 300, and
VLAN 400.
To make sure that Switch B is the regional root of MSTI-2, and that ge-1/1/1 is in blocking status in MSTI-
3, configure a higher MSTI-2 priority, and a large value for internal-path-cost in MSTI-3.
[edit]
XorPlus# set protocols spanning-tree mstp msti 2 vlan 200
[edit]
XorPlus# set protocols spanning-tree mstp msti 3 vlan 300
[edit]
XorPlus# set protocols spanning-tree mstp configuration-name region1
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
To make sure that Switch C is the regional root of MSTI-3, ge-1/1/1 is in blocking status in MSTI-2, and
that ge-1/1/2 is in blocking status in MSTI-1, you should configure a higher MSTI-3 priority, and large
values for internal-path-costs of ge-1/1/1 in MSTI-2 and ge-1/1/2 in MSTI-1.
XorPlus# set interface gigabit-ethernet ge-1/1/2 family ethernet-switching vlan members 300
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/2 family ethernet-switching vlan members 400
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/3 family ethernet-switching port-mode trunk
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/3 family ethernet-switching vlan members 100
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/3 family ethernet-switching vlan members 200
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/3 family ethernet-switching vlan members 300
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/3 family ethernet-switching vlan members 400
[edit]
XorPlus#
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
XorPlus# set protocols spanning-tree mstp msti 2 vlan 200
[edit]
XorPlus# set protocols spanning-tree mstp msti 4 vlan 400
[edit]
XorPlus# set protocols spanning-tree mstp configuration-name region2
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
To make sure that Switch D is the regional root of MSTI-2 andthe root of CIST, configure a higher MSTI-2
priority and bridge priority.
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/1 family ethernet-switching vlan members 100
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/1 family ethernet-switching vlan members 200
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/1 family ethernet-switching vlan members 300
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/1 family ethernet-switching vlan members 400
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/2 family ethernet-switching port-mode trunk
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/2 family ethernet-switching vlan members 100
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/2 family ethernet-switching vlan members 200
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/2 family ethernet-switching vlan members 300
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/2 family ethernet-switching vlan members 400
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/3 family ethernet-switching port-mode trunk
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/3 family ethernet-switching vlan members 100
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/3 family ethernet-switching vlan members 200
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/3 family ethernet-switching vlan members 300
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/3 family ethernet-switching vlan members 400
[edit]
XorPlus#
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
XorPlus# set protocols spanning-tree mstp msti 2 vlan 200
[edit]
XorPlus# set protocols spanning-tree mstp msti 4 vlan 400
[edit]
XorPlus# set protocols spanning-tree mstp configuration-name region2
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
To make sure that Switch E is the regional root of MSTI-4, configure a higher MSTI-4 priority.
Switch A Switch B
Ge-1/1/1 Ge-1/1/1
Ge-1/1/3 Permit: all VLAN Ge-1/1/3
Ge-1/1/2 Ge-1/1/2
Ge-1/1/1 Ge-1/1/1
Permit: VLAN 200, 400
Switch C Switch D
XorPlus#
XorPlus# set protocols spanning-tree force-version 4
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
To make sure that Switch A is the root bridge of VLANs 100 and 200, configure VLANs 100 and 200 as
the higher priority.
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
To make sure that Switch B is the root bridge of VLAN 300, configure VLAN 300 as the higher priority.
To make sure that Switch C is the root bridge of VLAN 400, configure VLAN 400 as the higher priority.
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
●In general, you do not need to configure parameters for“cell” and “packet,” because the switch contains their
default parameters.
● You can configure the switch to be inburstmode for burst traffic, which will dynamically allocate the “cell” and
“packet” for each port and queue.
Commit OK.
Save done.
[edit]
XorPlus#
STP1 STP1
Customer A Customer B
Ge-1/1/1 Ge-1/1/1
Ge-1/1/2 Ge-1/1/2
Customer C Customer D
STP2 STP2
Configure VLAN 200 as the default VLAN of GigabitEthernet ge-1/1/2, and enable BPDUtunneling on
GigabitEthernet ge-1/1/2.
Configure VLAN 100 as the default VLAN of GigabitEthernet ge-1/1/1, and enable BPDUtunneling on
GigabitEthernet ge-1/1/1.
Configure VLAN 200 as the default VLAN of GigabitEthernet ge-1/1/2, and enable BPDUtunneling on
GigabitEthernet ge-1/1/2.
Interface ge-1/1/2
----------------------------------------
Udld enabled, aggressive mode
Current bidirectional state: undetermined
Current phase: linkdown
Message interval: 7s
Timeout interval: 5s
Interface ge-1/1/3
----------------------------------------
Udld enabled, aggressive mode
Current bidirectional state: undetermined
Current phase: linkdown
Message interval: 7s
Timeout interval: 5s
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# set protocols neighbour ra-guard 2 prefix 2001:1:1:1::/64
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# set protocols neighbour ra-guard 3 source-mac-addr 22:22:22:22:22:22
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
(2) Configuring“trusted-port”
You can apply the RA guard to physical interfaces, LAGs, or VLANs; no more than one RA guard can be
applied to one interface. The RAs will be forwarded only if allconditions are matched, but if “trusted-port”
has been configured for the RA guard, then RAs will be forwarded on the trusted port regardless.
When the switch receives aningress RA message, it will attempt to match the message via the RA guard.
If the ingress port hasthe RA guard applied but is not a trusted port, the applied VLAN ID will be matched
first. If the RA tag is matched with the VLAN ID, the RA guard will continue matching conditions to
determine whether to forward or drop the RA message. If the RA tag is not matched with the VLAN ID,
the applied interfacewill be matched (followed by the subsequent conditions).
Raguard: 2
vlan : 3
packet dropped: 0
packet total : 0
trusted port:
ge-1/1/1
XorPlus#
● You can configure the IP address and prefix length for the VLAN interface.
● When all the member ports in the VLAN are link-down, the VLAN interface will be link-down. The VLAN
interface will be link-up when at least one of the member ports are link-up.
XorPlus#
ARP Configuration
(1) Configuring ARP aging time
In the default setting, the ARP aging time is 1200 seconds.
XorPlus# set protocols arp aging-time 600
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
In a typical network configuration, you configure all switch ports connected to host ports as untrusted and
configure all switch ports connected to switches as trusted. With this configuration, all ARP packets
entering the network from a given switch bypass the security check. No other validation is needed at any
other place in the VLAN or in the network.
When configuring DAI, follow these guidelines and restrictions:
• DAI is an ingress security feature; it does not perform any egress checking.
• DAI is not effective for hosts connected to switches that do not support DAI or that do not have this
feature enabled. Because man-in-the-middle attacks are limited to a single Layer 2 broadcast domain,
separate the domain with DAI checks from the one with no checking. This action secures the ARP caches
of hosts in the domain enabled for DAI.
• DAI depends on the entries in the DHCP snooping binding database to verify IP-to-MAC address
bindings in incoming ARP requests and ARP responses. Make sure to enable DHCP snooping to permit
ARP packets that have dynamically assigned IP addresses.,
• DAI is supported on access ports, trunk ports.lag ports.
Te-1/1/50
Switch
Te-1/1/52
Host
Figure-DAI
(1). Step 1:Eable DHCP snooping on Switch
You can enable dhcp snooping on the egress port ,the port connected to DHCP Server
Enable dhcp snooping
XorPlus# set protocols dhcp snooping disable false
[edit]
XorPlus# commit
Commit OK.
Save done.
[edit]
XorPlus#
Set the interface to trust mode
XorPlus# set protocols dhcp snooping port te-1/1/50 trust true
[edit]
XorPlus# commit
Commit OK.
Save done.
[edit]
XorPlus#
(2). Step 2:enable DAI
You can enable DAI on the port connect to the host
XorPlus# set protocols arp interface vlan-900 inspection disable false
[edit]
XorPlus# commit
Merging the configuration.
Commit OK.
Save done.
[edit]
XorPlus#
(3). Step 3:Check arp inspection table
When the host got an ip address from the DHCP server and the switch have enabled dhcp snooping, it
will created a table, IP-MAC-port binded table , the entry in this table was trusted ,all other ARP packet
will be discarded not in this table(The arp packet must be according with the arp inspection
table,interface .ip address .Mac address must be identified )
XorPlus# run show arp inspection
Total count : 1
Interface DAI Address HW Address
--------- -------- --------------- -----------------
vlan-900 Enabled 192.168.9.5 0:1e:c9:bb:d3:35
● Traffic that can be routed will have a route entry in the RIB and the ARP of the next hop; the outgoing
interface should be link-up. The traffic will then be soft-routed (i.e., routed by the switch’s CPU).
● When the switch learns the MAC address of the nexthop, the switch will forward the traffic with the ASIC chip.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 100
Layer 3 Routing Configuration
With the show route forward-route ipv4 all command, all the route entries in the ASIC chip will be
displayed. Following the show route table ipv4 unicast final command, all routes in the RIB of the
kernel will be displayed.
●Host A and Host B should be able to communicate with the gateway (e.g., access Internet).
Gateway
10.10.5.1/24
ge-1/1/3 10.10.5.2/24
10.10.3.2/24 10.10.4.2/24
ge-1/1/1 ge-1/1/2
Switch C
10.10.6.1/24 10.10.6.2/24
10.10.1.1/24 10.10.2.1/24
Host A ge-1/1/3 ge-1/1/3 Host B
ge-1/1/1 Switch A Switch B ge-1/1/1
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 101
Layer 3 Routing Configuration
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 102
Layer 3 Routing Configuration
[edit]
XorPlus# set vlans vlan-id 3 l3-interface vlan-3
[edit]
XorPlus# set vlans vlan-id 4 l3-interface vlan-4
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# set vlan-interface interface vlan-2 vif vlan-2 address 10.10.2.1 prefix-length 24
[edit]
XorPlus# set vlan-interface interface vlan-3 vif vlan-2 address 10.10.4.1 prefix-length 24
[edit]
XorPlus# set vlan-interface interface vlan-4vif vlan-2 address 10.10.6.1 prefix-length 24
[edit]
XorPlus# set protocols static route 10.10.1.0/24 next-hop 10.10.6.1
[edit]
XorPlus# set protocols static route 0.0.0.0/0 next-hop 10.10.4.2
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 103
Layer 3 Routing Configuration
Commit OK.
Save done.
[edit]
XorPlus# set vlan-interface interface vlan-2vif vlan-2 address 10.10.3.2 prefix-length 24
[edit]
XorPlus# set vlan-interface interface vlan-3vif vlan-3 address 10.10.4.2 prefix-length 24
[edit]
XorPlus# set vlan-interface interface vlan-4vif vlan-4 address 10.10.5.2 prefix-length 24
[edit]
XorPlus# set protocols static route 10.10.1.0/24 next-hop 10.10.3.1
[edit]
XorPlus# set protocols static route 10.10.2.0/24 next-hop 10.10.4.1
[edit]
XorPlus# set protocols static route 10.10.6.0/24 next-hop 10.10.3.1
[edit]
XorPlus# set protocols static route 0.0.0.0/0 next-hop 10.10.5.1
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
● A policy statement is used to specify which route entry will be distributed. For example, you can
distribute the static route or the connected route to a neighbor. You can also specify the distributed
route metric.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 104
Layer 3 Routing Configuration
Commit OK.
Save done.
[edit]
XorPlus# set vlans vlan-id 3
[edit]
XorPlus# set vlans vlan-id 3 l3-interface vlan-3
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/2 family ethernet-switching native-vlan-id 3
[edit]
XorPlus# set vlan-interface interface vlan-3vif vlan-3 address 192.168.2.1 prefix-length 24
[edit]
XorPlus# set protocols static route 9.9.9.0/24 next-hop 192.168.2.2
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# set policy policy-statement connected-to-rip term export from protocol connected
[edit]
XorPlus# set policy policy-statement connected-to-rip term export then metric 0
[edit]
XorPlus# set policy policy-statement static-to-rip term export from protocol static
[edit]
XorPlus# set policy policy-statement static-to-rip term export then metric 1
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# set protocols rip interface vlan-2vif vlan-2 address 192.168.1.1
[edit]
XorPlus# set protocols rip export "connected-to-rip,static-to-rip"
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
Counter Value
-------------------------------- ----------------
Requests Sent 7
Updates Sent 6
Triggered Updates Sent 1
Non-RIP Updates Sent 0
Total Packets Received 0
Request Packets Received 0
Update Packets Received 0
Bad Packets Received 0
Authentication Failures 0
Bad Routes Received 0
Non-RIP Requests Received 0
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 105
Layer 3 Routing Configuration
● Host A and Host B should be able to communicate with each other with anRIP route.
● Host A and Host B should be able to communicate with the gateway (e.g., access Internet)with RIP.
Gateway
10.10.5.1/24
ge-1/1/3 10.10.5.2/24
10.10.3.2/24 10.10.4.2/24
ge-1/1/1 ge-1/1/2
Switch C
10.10.1.1/24 10.10.2.1/24
Host A Host B
ge-1/1/1 Switch A Switch B ge-1/1/1
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 106
Layer 3 Routing Configuration
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 107
Layer 3 Routing Configuration
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 108
Layer 3 Routing Configuration
●XorPlus supports normal areas, stub areas, and not-so-stubby areas (NSSAs)in OSPF.
The router ID is a string similar to the IP address, and should be unique in the OSPF domain. You should
not change the router IDafter completing the configuration.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 109
Layer 3 Routing Configuration
[edit]
XorPlus# set vlan-interface interface vlan-2vif vlan-2 address 10.10.60.10 prefix-length 24
[edit]
XorPlus# set vlan-interface interface vlan-3vif vlan-3 address 10.10.61.10 prefix-length 24
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/1 family ethernet-switching native-vlan-id 2
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/2 family ethernet-switching native-vlan-id 3
[edit]
XorPlus# set protocols ospf4 area 0.0.0.0 interface vlan-2vif vlan-2 address 10.10.60.10
[edit]
XorPlus# set protocols ospf4 area 0.0.0.0 interface vlan-3vif vlan-3 address 10.10.61.10
[edit]
XorPlus# set protocols ospf4 router-id 1.1.1.1
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
XorPlus# run show ospf4 interface
Interface State Area DR ID BDR ID Nbrs
--------- -------- --------------- --------------- --------------- ----
vlan-2 DR 0.0.0.0 1.1.1.1 0.0.0.0 0
vlan-3 DR 0.0.0.0 1.1.1.1 0.0.0.0 0
XorPlus# set protocols ospf4 area 0.0.0.0 interface vlan-2vif vlan-2 address 10.10.60.10hello-
interval 5
[edit]
XorPlus# set protocols ospf4 area 0.0.0.0 interface vlan-2vif vlan-2 address
10.10.60.10interface-cost 8
[edit]
XorPlus# set protocols ospf4 area 0.0.0.0 interface vlan-2vif vlan-2 address 10.10.60.10transmit-
delay 2
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
XorPlus# run show ospf4 interface detail
Interface vlan-2/vlan-2, State DR, Area 0.0.0.0
DR ID 1.1.1.1, BDR ID 0.0.0.0, Nbrs 0
Network Type BROADCAST, Address 10.10.60.10, Mask 255.255.255.0, Cost 8
DR addr 10.10.60.10, BDR addr 0.0.0.0, Priority 128
Hello 10, Dead 40, ReXmit 5, NORMAL
● Switch D will obtain the routes of networks 10.10.1.0/24, 10.10.3.0/24, and 10.10.9.0/24,through the
LSAs sent from its neighbors. Switch C will obtain the routes of networks 10.10.1.0/24, 10.10.2.0/24, and
10.10.8.0/24, according toLSAs sent from its neighbors.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 110
Layer 3 Routing Configuration
Ge-1/1/1 Ge-1/1/1
10.10.1.1/24 10.10.1.2/24 Switch B
Switch A Area
0.0.0.0
Ge-1/1/2 Ge-1/1/2
10.10.2.1/24 10.10.3.1/24
Area Area
0.0.0.1 0.0.0.2
Ge-1/1/1 Ge-1/1/1
10.10.2.2/24 10.10.3.2/24
Switch D Switch C
Ge-1/1/2 Ge-1/1/2
10.10.8.1/24 Host A Host B 10.10.9.1/24
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 111
Layer 3 Routing Configuration
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 112
Layer 3 Routing Configuration
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
Below, switch A has two OSPF neighbor interfaces, 10.10.1.2 and 10.10.2.2.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 113
Layer 3 Routing Configuration
10.10.3.0/24 [ospf(110)/2]
> to 10.10.1.2 via vlan-2/vlan-2
● Switch D will obtain the routes of networks 10.10.1.0/24, 10.10.3.0/24, and 10.10.9.0/24, according to the
LSAs receivedfrom itsneighbors. Switch C will obtain the routes of networks 10.10.1.0/24, 10.10.2.0/24,
and10.10.8.0/24, according to the LSAs received from itsneighbors.
Ge-1/1/1 Ge-1/1/1
10.10.1.1/24 10.10.1.2/24 Switch B
Switch A Area
0.0.0.0
Ge-1/1/2 Ge-1/1/2
10.10.2.1/24 10.10.3.1/24
Stub
Area NSSA
Area
0.0.0.1 Internet 0.0.0.2
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 114
Layer 3 Routing Configuration
For switch A, configure 2 VLANinterfaces for networks 10.10.1.1/24 and 10.10.2.1/24. Youshould also
configure area 0.0.0.0,which includes network 10.10.1.1/24,and area 0.0.0.1,which includes network
10.10.2.1/24.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 115
Layer 3 Routing Configuration
[edit]
XorPlus# set protocols ospf4 area 0.0.0.0 interface vlan-2vif vlan-2 address 10.10.1.2
[edit]
XorPlus# set protocols ospf4 area 0.0.0.2 interface vlan-3vif vlan-3 address 10.10.3.1
[edit]
XorPlus# set protocols ospf4 area 0.0.0.2area-type stub
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 116
Layer 3 Routing Configuration
[edit]
XorPlus# set vlan-interface interface vlan-2vif vlan-2 address 10.10.2.2 prefix-length 24
[edit]
XorPlus# set vlan-interface interface vlan-3vif vlan-3 address 10.10.8.1 prefix-length 24
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# set policy policy-statement rip-ospf term rip from protocol rip
[edit]
XorPlus# set policy policy-statement rip-ospf term rip then external-type 2
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# set protocols ospf4 router-id 4.4.4.4
[edit]
XorPlus# set protocols ospf4 area 0.0.0.1 interface vlan-2vif vlan-2 address 10.10.2.2
[edit]
XorPlus# set protocols ospf4 area 0.0.0.1 area-type nssa
[edit]
XorPlus# set protocols ospf4 export rip-ospf
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 117
Layer 3 Routing Configuration
XorPlus# commit
[edit]
Waiting for merging configuration.
Commit OK.
Save Done.
[edit]
XorPlus#
● The two endpoints of a virtual link are Area Border Routers (ARBs). The virtual link must be configured in both
routers. The configuration information in each router consists of the other virtual endpoint (the other ARB), and
the non-backbone area that the two routers have in common (called the transit area). Virtual links cannot be
configured through stub areas.
● Enable OSPF on Switchs A, B, C, and D at the beginning. There is no route entry from the backbone area
(0.0.0.0) to area 2.2.2.2.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 118
Layer 3 Routing Configuration
XorPlus# set vlan-interface interface vlan-400 vif vlan-400 address 172.25.150.250 prefix-length
30
[edit]
XorPlus# set vlans vlan-id 500 l3-interface vlan-500
[edit]
XorPlus# set vlan-interface interface vlan-500 vif vlan-500 address 192.168.1.1 prefix-length 30
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/48 family ethernet-switching native-vlan-id 500
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/2 family ethernet-switching native-vlan-id 400
[edit]
XorPlus# set protocols ospf4 router-id 4.4.4.4
[edit]
XorPlus# set protocols ospf4 area 0.0.0.0 interface vlan-500 vif vlan-500 address 192.168.1.1
[edit]
XorPlus# set protocols ospf4 area 1.1.1.1 interface vlan-400 vif vlan-400 address 172.25.150.250
[edit]
XorPlus#commit
[edit]
Waiting for merging configuration.
Commit OK.
Save Done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 119
Layer 3 Routing Configuration
XorPlus# set protocols ospf4 area 2.2.2.2 interface vlan-300 vif vlan-300 address 172.25.150.245
[edit]
XorPlus#commit
[edit]
Waiting for merging configuration.
Commit OK.
Save Done.
[edit]
XorPlus#
Enable virtual links on the Area Border Routers (Switch B and Switch C).After this step, there will be
aroute entry from the backbone area, 0.0.0.0, to area 2.2.2.2.
XorPlus# set protocols ospf6 area 0.0.0.0 virtual-link 3.3.3.3 transmit-area 1.1.1.1
XorPlus#commit
[edit]
Waiting for merging configuration.
Commit OK.
Save Done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 120
Layer 3 Routing Configuration
[edit]
XorPlus# set protocols ospf4 area 0.0.0.0 interface vlan-400 vif vlan-400 address 172.25.150.250
[edit]
XorPlus#commit
[edit]
Waiting for merging configuration.
Commit OK.
Save Done.
[edit]
XorPlus#
XorPlus# set protocols ospf4 area 1.1.1.1 area-type <normal | stub | nssa>
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
# Check route table on DUT3,there will be route entry to backbone area 192.168.1.0/30
XorPlus# run show route forward-route ipv4 all
Destination NetMask NextHopMac Port
--------------- --------------- ----------------- ---------
172.25.150.248 255.255.255.252 08:9E:01:62:D5:61 connected
192.168.1.0 255.255.255. 252 60:EB:69:9B:BE:31 te-1/1/51
Total route count:2
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 121
Layer 3 Routing Configuration
● You can use the “advertisedisable” parameter to restrain ABR route aggregation. The ABR will generate route
aggregation by default after you configure area-range, and the packet is routed to the best (the longest or
most specific)match.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 122
Layer 3 Routing Configuration
[edit]
XorPlus# set vlan-interface interface vlan-500 vif vlan-500 address 192.168.1.1 prefix-length 30
[edit]
XorPlus# set interface gigabit-ethernet te-1/1/49 family ethernet-switching native-vlan-id 500
[edit]
XorPlus# set protocols ospf4 router-id 4.4.4.4
[edit]
XorPlus# set protocols ospf4 area 0.0.0.0 interface vlan-100 vif vlan-500 address 192.168.1.1
[edit]
XorPlus# set vlans vlan-id 400 l3-interface vlan-400
[edit]
XorPlus# set vlan-interface interface vlan-400 vif vlan-400 address 172.25.150.250 prefix-length
30
[edit]
XorPlus# set interface gigabit-ethernet te-1/1/49 family ethernet-switching native-vlan-id 400
[edit]
XorPlus# set protocols ospf4 area 0.0.0.0 interface vlan-400 vif vlan-400 address 172.25.150.250
[edit]
XorPlus#commit
[edit]
Waiting for merging configuration.
Commit OK.
Save Done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 123
Layer 3 Routing Configuration
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 124
Layer 3 Routing Configuration
XorPlus#commit
[edit]
Waiting for merging configuration.
Commit OK.
Save Done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 125
Layer 3 Routing Configuration
[edit]
XorPlus#
# Check route table on Switch A , there will be route entry 192.168.6.0/24
XorPlus# run show route forward-route ipv4 all
Destination NetMask NextHopMac Port
--------------- --------------- ----------------- ---------
192.168.1.0 255.255.255.252 C8:0A:A9:AE:0A:66 connected
172.25.150.248 255.255.255.252 60:EB:69:9B:BE:31 te-1/1/47
192.168.6.0 255.255.255.0 60:EB:69:9B:BE:31 te-1/1/47
Total route count:3
The BFD will send protocol messages initiatively in active mode, and passively in passive mode.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 126
Layer 3 Routing Configuration
XorPlus# set protocols ospf4 area 1.1.1.1 interface vlan-25 vif vlan-25 address 125.125.25.6 bfd
disable false
[edit]
XorPlus# commit
Merging the configuration.
Commit OK.
Save done.
[edit]
XorPlus#
XorPlus# set protocols ospf6 area 1.1.1.1 interface vlan-23 vif vlan-23 bfd disable false
[edit]
XorPlus# commit
Merging the configuration.
Commit OK.
Save done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 127
Layer 3 Routing Configuration
Switch A Switch B
123.123.10.1/24 123.123.10.6/24
Area
0.0.0.0
Ge-1/1/1 Ge-1/1/1
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 128
Layer 3 Routing Configuration
XorPlus# commit
Merging the configuration.
Commit OK.
Save done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 129
Layer 3 Routing Configuration
Switch A Switch B
123.123.10.1/24 123.123.10.6/24
Ge-1/1/1 Ge-1/1/1
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 130
Layer 3 Routing Configuration
XorPlus# commit
Merging the configuration.
Commit OK.
Save done.
[edit]
XorPlus# set protocols static route 178.178.10.0/24 next-hop 123.123.10.1
[edit]
XorPlus# set protocols static route 178.178.10.0/24 bfd true
[edit]
XorPlus# commit
Merging the configuration.
Commit OK.
Save done.
[edit]
XorPlus# set protocols bfd interface vlan-10 disable false
[edit]
XorPlus# commit
Merging the configuration.
Commit OK.
Save done.
[edit]
XorPlus#
The AS_Path attribute records all the AS’s that a route passes through from the source to the
destination,following the order of vectors.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 131
Layer 3 Routing Configuration
Commit OK.
Save done.
[edit]
XorPlus#
To establish point-to-point connections between peer autonomous systems, configure a BGP session on
each interface of a point-to-point link. Generally,such sessions are made at network exit points with
neighboring hosts outside the AS.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 132
Layer 3 Routing Configuration
● To enable the IBGP peer to use this route to guide traffic forwarding, configure the ASBR to set its IP
address as the next hop of the route when the ASBR forwards this route to the IBGP peer. After the
IBGP peer receives this route from the ASBR, it finds the next hop of the route reachable, sets the
route to active,and uses this route to guide traffic forwarding.
● When a BGP route changes, BGP needs to iterate the indirect next hop of the route again. If no
restriction is imposed on the iterated route, BGP may iterate the next hop to an incorrect forwarding
path, causing traffic loss. Configure routing policy-based route iteration to prevent traffic loss.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 133
Layer 3 Routing Configuration
Save done.
[edit]
XorPlus#
● A cluster ID can help prevent routing loops between multiple RRs within a cluster, and between
clusters. When a cluster has multiple RRs, the same cluster ID must be configured for all RRs within
the cluster.
● If full-mesh IBGP connections are established between clients of multiple RRs, route reflection
between clients is not required and wastes bandwidth resources. In this case, prohibit route reflection
between clients to reduce the network burden.
● Within an AS, an RR transmits routing information and forwards traffic. When an RR connects to a
large number of clients and non-clients, many CPU resources are consumed if the RR transmits
routing information and forwards traffic simultaneously. This also reduces route transmission efficiency.
To improve route transmission efficiency, prohibit BGP from adding preferred routes to IP routing
tables on the RR, enabling the RR to only transmit routing information.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 134
Layer 3 Routing Configuration
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 135
Layer 3 Routing Configuration
BGP supports automatic route summarization and manual route summarization. Manual route
summarization takes precedence over automatic route summarization.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 136
Layer 3 Routing Configuration
BGP will not load balance across multiple paths by default. This is acceptable if youare multihomed to a
single AS, but what if you are multihomed to different AS path? In that case,you cannot load balance
across theoretically equal paths. Enter the BGP multipath path-relaxcommand:
Ge-1/1/3 Vlan30
192.168.30.1/24 Ge-1/1/5 Vlan50
Ge-1/1/2 Vlan20 192.168.50.1/24
192.168.20.2/24
Ge-1/1/2 Vlan20
192.168.20.1/24
SwitchA SwitchB
Ge-1/1/4 Vlan40 Ge-1/1/5 Vlan50
192.168.40.1/24 192.168.50.2/24
Ge-1/1/4 Vlan40
192.168.40.2/24
SwitchC
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 137
Layer 3 Routing Configuration
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 138
Layer 3 Routing Configuration
Commit OK.
Save done.
[edit]
XorPlus#
XorPlus# set interface gigabit-ethernet ge-1/1/2 family ethernet-switching native-vlan-id 20
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/3 family ethernet-switching native-vlan-id 30
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/4 family ethernet-switching native-vlan-id 40
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 139
Layer 3 Routing Configuration
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 140
Layer 3 Routing Configuration
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 141
Layer 3 Routing Configuration
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 142
Layer 3 Routing Configuration
The preceding command output display that the route to destination 192.168.10.0/24 becomes invalid
because the nexthop address of this route is unreachable.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 143
Layer 3 Routing Configuration
●Configure SwitchB, SwitchC, and SwitchD to haveIBGP connections. Between SwitchA and SwitchB should be
an EBGP connection.
SwitchD
Ge-1/1/1 Vlan10
192.168.10.1/24
Ge-1/1/5 Vlan50
Ge-1/1/2 Vlan20 192.168.50.1/24
192.168.20.2/24
Ge-1/1/2 Vlan20
192.168.20.1/24
SwitchA SwitchB
Ge-1/1/4 Vlan40 Ge-1/1/5 Vlan50
192.168.40.1/24 192.168.50.2/24
Ge-1/1/4 Vlan40
192.168.40.2/24
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 144
Layer 3 Routing Configuration
Save done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 145
Layer 3 Routing Configuration
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 146
Layer 3 Routing Configuration
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 147
Layer 3 Routing Configuration
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/3 family ethernet-switching native-vlan-id 30
[edit]
XorPlus# set interface gigabit-ethernet ge-1/1/5 family ethernet-switching native-vlan-id 50
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 148
Layer 3 Routing Configuration
●Configure BGP confederation membersSwitchA, Switch B, Switch C, and SwitchD. Between SwitchA
andSwitchD is an EBGP connection within AS 200.
AS200
AS65011
SwitchD
Ge-1/1/6 Vlan60
192.168.60.1/24 Ge-1/0/3 Vlan30
192.168.30.1/24 Ge-1/1/5 Vlan50
192.168.50.1/24
Ge-1/1/2 Vlan20
192.168.20.2/24
Ge-1/1/2 Vlan20
192.168.20.1/24
SwitchE SwitchA
Ge-1/1/4 Vlan40 Ge-1/1/5 Vlan50
192.168.40.1/24 192.168.50.2/24
Ge-1/1/4 Vlan40
192.168.40.2/24
SwitchB AS65010
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 149
Layer 3 Routing Configuration
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 150
Layer 3 Routing Configuration
[edit]
XorPlus# set protocols bgp peer 192.168.40.2 local-ip 192.168.40.1
[edit]
XorPlus# set protocols bgp peer 192.168.40.2 next-hop-self true
[edit]
XorPlus# set protocols bgp peer 192.168.40.2 confederation-member true
[edit]
XorPlus# set protocols bgp peer 192.168.60.2 as 65011
[edit]
XorPlus# set protocols bgp peer 192.168.60.2 local-ip 192.168.60.1
[edit]
XorPlus# set protocols bgp peer 192.168.60.2 next-hop-self true
[edit]
XorPlus# set protocols bgp peer 192.168.60.2 confederation-member true
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 151
Layer 3 Routing Configuration
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 152
Layer 3 Routing Configuration
[edit]
XorPlus# set vlan-interface interface 50 vif 50 address 192.168.50.1 prefix-length 24
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 153
Layer 3 Routing Configuration
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 154
Layer 3 Routing Configuration
XorPlus#
ConfigureanEBGP connection.
● Configure EBGP connections between SwitchB and SwitchA, andbetween SwitchB and SwitchD.
● Configure EBGP connections between SwitchC and SwitchA, and between SwitchC and SwitchD.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 155
Layer 3 Routing Configuration
SwitchB
Ge-1/1/1 Vlan30 Ge-1/1/2 Vlan20
192.168.30.2/24 192.168.20.2/24
Ge-1/1/1 Vlan30
192.168.30.1/24 Ge-1/1/2 Vlan20
AS200 192.168.20.1/24
AS100
AS400
Ge-1/1/1 Vlan10
192.168.10.1/24
SwitchA SwitchD
Ge-1/1/2 Vlan40 AS300 Ge-1/1/3 Vlan30
192.168.40.1/24 192.168.50.1/24
SwitchC
XorPlus# set vlan-interface interface vlan30 vif vlan30 address 192.168.30.1 prefix-length 24
[edit]
XorPlus# set vlan-interface interface vlan40 vif vlan40 address 192.168.40.1 prefix-length 24
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 156
Layer 3 Routing Configuration
XorPlus# set vlan-interface interface vlan20 vif vlan20 address 192.168.20.2 prefix-length 24
[edit]
XorPlus# set vlan-interface interface vlan30 vif vlan30 address 192.168.30.2 prefix-length 24
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 157
Layer 3 Routing Configuration
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
XorPlus# set vlan-interface interface vlan40 vif vlan40 address 192.168.40.2 prefix-length 24
[edit]
XorPlus# set vlan-interface interface vlan50 vif vlan50 address 192.168.50.2 prefix-length 24
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 158
Layer 3 Routing Configuration
XorPlus# set vlan-interface interface vlan10 vif vlan10 address 192.168.10.1 prefix-length 24
[edit]
XorPlus# set vlan-interface interface vlan20 vif vlan20 address 192.168.20.1 prefix-length 24
[edit]
XorPlus# set vlan-interface interface vlan50 vif vlan50 address 192.168.50.1 prefix-length 24
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
ConfigureanEBGP connection.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 159
Layer 3 Routing Configuration
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 160
Layer 3 Routing Configuration
As expected, SwitchA is not load balancing because it does notviewthe paths as “equal,” but as different
AS paths.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 161
Layer 3 Routing Configuration
[edit]
XorPlus#
● After configuring the ECMP equal-cost path maximum, save the configuration file and rebootthe switch to
make it available.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 162
Layer 3 Routing Configuration
I2C: ready
DRAM: Initializing
You can check the static ECMP route for 10.10.51.0/24 in the RIB.
XorPlus# run show route table ipv4 unicast final
10.10.51.0/24 [static(1)/1]
> to 10.10.61.20 via vlan-3/vlan-3
10.10.51.0/24 [static(1)/1]
> to 10.10.62.20 via vlan-4/vlan-4
10.10.60.0/24 [connected(0)/0]
> via vlan-2/vlan-2
10.10.61.0/24 [connected(0)/0]
> via vlan-3/vlan-3
10.10.62.0/24 [connected(0)/0]
> via vlan-4/vlan-4
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 163
Layer 3 Routing Configuration
[edit]
XorPlus# set interface ecmp hash-mapping field ip-protocol disable false
[edit]
XorPlus# set interface ecmp hash-mapping field ip-source disable false
[edit]
XorPlus# set interface ecmp hash-mapping field port-destination disable false
[edit]
XorPlus# set interface ecmp hash-mapping field port-source disable false
[edit]
XorPlus# set interface ecmp hash-mapping field vlan disable false
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 164
Layer 3 Routing Configuration
Interface vlan-2
Vif vlan-2
VRID 1
State master
Master IP 192.168.1.1
XorPlus#
●In P-3290 and P-3780, you should configure the link-local IPv6 address,otherwise all the IPv6 interfaces will
share the same link-local address. This problem will be fixed in afuture version.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 165
Layer 3 Routing Configuration
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 166
Layer 3 Routing Configuration
Save done.
[edit]
XorPlus# set protocols ospf6 area 0.0.0.0 interface vlan-2 vif vlan-2 hello-interval 10
[edit]
XorPlus# set protocols ospf6 area 0.0.0.0 interface vlan-2 vif vlan-2 interface-cost 8
[edit]
XorPlus# set protocols ospf6 area 0.0.0.0 interface vlan-2 vif vlan-2 transmit-delay 2
[edit]
XorPlus# commit
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 167
Layer 3 Routing Configuration
● TCP flags are also supported. These ACLs can be applied to physical ports, LAG ports, and VLAN interfaces.
One ACL can be applied tomultiple ports (the propertiesof the ports can be same or different), but only one
port can be matched to one ACL.
XorPlus# set firewall filter bad-net sequence bad-1 from source-address-ipv4 1.1.1.0/24
[edit]
XorPlus# set firewall filter bad-net sequence bad-1 then action discard
[edit]
XorPlus# set firewall filter bad-net sequence bad-2 from source-address-ipv4 1.1.2.0/24
[edit]
XorPlus# set firewall filter bad-net sequence bad-2 then action discard
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
XorPlus# set firewall filter bad-net input interface ge-1/1/1
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# set firewall filter bad-net input interface ae1
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
When the switch receives a packet in ingress and egress, it will attemptto match ACLs by sequence
number, with smaller values representing higher priorities.If the matched ACL’s action is “forward” or
“discard,” the switchwill forward or discard the packet and will not match the remaining ACLs. If there is
no matching ACL, the packet will be dropped.
XorPlus# set firewall filter bad-net sequence bad-1 from source-address-ipv4 1.1.1.0/24
[edit]
XorPlus# set firewall filter bad-net sequence bad-1 then action discard
[edit]
XorPlus# set firewall filter bad-net sequence bad-2 from source-address-ipv4 1.1.2.0/24
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 168
Layer 3 Routing Configuration
[edit]
XorPlus# set firewall filter bad-net sequencebad-2 then action discard
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
XorPlus# set firewall filter bad-netinput vlan-interface vlan-2
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
XorPlus# set firewall filter bad-net sequence bad-1 then action discard
[edit]
XorPlus# set firewall filter bad-net sequence bad-1 from protocol tcp flags ack true
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# set firewall filter bad-net output interface ge-1/1/1
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 169
Layer 3 Routing Configuration
XorPlus#
XorPlus# run syslog monitor on
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 170
MulticastConfiguration
XorPlus#
XorPlus#
IGMP Configuration
In XorPlus, IGMPv1/v2/v3 is supported.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 172
Multicast Configuration
If you send a Ieaving message for the above group, the specified group will be removed.
PIM-SM Configuration
In L2/L3, PIM-SM is supported.
● You can then configure a candidate-RP and a candidate-BSR. For configuring the candidate-BSR, “scope-
zone”denotes the zone of the multicast group, which is included in the multicast domain.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 173
Multicast Configuration
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 174
Multicast Configuration
●In this example, the static route in the RIB will be used by PIM-SM.
Ge-1/1/1 Ge-1/1/1
10.10.1.1/24 C-RP BSR 10.10.2.1/24
Ge-1/1/2 Ge-1/1/2
10.10.3.1/24 10.10.4.1/24
Host A Host B
Destination Multicast Source
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 175
Multicast Configuration
[edit]
XorPlus# set protocols pimsm4 interface vlan-2vif vlan-2 disable false
[edit]
XorPlus# set protocols pimsm4 interface vlan-3vif vlan-3 disable false
[edit]
XorPlus# set protocols pimsm4 interface register_vif disable false
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#set protocols static route 10.10.2.0/24 next-hop 10.10.1.2
[edit]
XorPlus#set protocols static route 10.10.4.0/24 next-hop 10.10.1.2
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# run show pim interface
Interface State Mode V PIMstate Priority DRaddr Neighbors
---------- -------- ------ - -------- -------- --------------- ---------
vlan-2 UP Sparse 2 DR 1 10.10.1.1 0
vlan-3 UP Sparse 2 DR 1 10.10.3.1 0
register_vif UP Sparse 2 DR 1 10.10.1.1 0
XorPlus#
XorPlus# run show igmp interface
Interface State Querier Timeout Version Groups
------------ -------- --------------- --------- --------- --------
vlan-2 DISABLED 10.10.1.1 None 2 0
vlan-3 UP 10.10.3.1 None 2 3
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 176
Multicast Configuration
[edit]
XorPlus# set protocols pimsm4 interface vlan-3vif vlan-3 disable false
[edit]
XorPlus# set protocols pimsm4 interfaceregister_vif disable false
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# set protocols pimsm4 bootstrap cand-bsr scope-zone 224.0.0.0/4 cand-bsr-by-vif-name
vlan-3
[edit]
XorPlus# set protocols pimsm4 bootstrap cand-rp group-prefix 238.0.0.0/8 cand-rp-by-vif-name
vlan-2
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#set protocols static route 10.10.3.0/24 next-hop 10.10.1.1
[edit]
XorPlus#set protocols static route 10.10.4.0/24 next-hop 10.10.2.1
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# run show pim bootstrap
Active zones:
BSR Pri LocalAddress Pri State Timeout SZTimeout
10.10.2.2 1 10.10.2.2 1 Elected 19 -1
Expiring zones:
BSR Pri LocalAddress Pri State Timeout SZTimeout
XorPlus#
XorPlus# run show pim rps
RP Type Pri Holdtime Timeout ActiveGroups GroupPrefix
------------- ------- --- -------- ------- ------------ ----------------
10.10.1.2 bootstrap 192 150 -1 0 238.0.0.0/8
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 177
Multicast Configuration
[edit]
XorPlus# set multicast-interface interface register_vif disable false
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# set protocols pimsm4 interface vlan-2vif vlan-2 disable false
[edit]
XorPlus# set protocols pimsm4 interface vlan-3vif vlan-3 disable false
[edit]
XorPlus# set protocols pimsm4 interface register_vif disable false
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# set protocols static route 10.10.1.0/24 next-hop 10.10.2.2
[edit]
XorPlus# set protocols static route 10.10.3.0/24 next-hop 10.10.2.2
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
XorPlus# run show pim interface
Interface State Mode V PIMstate Priority DRaddr Neighbors
---------- -------- ------ - -------- -------- --------------- ---------
vlan-2 UP Sparse 2 DR 1 10.10.2.1 0
vlan-3 UP Sparse 2 DR 1 10.10.4.1 0
register_vif UP Sparse 2 DR 1 10.10.2.1 0
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 178
QoS Configuration
Configuring QoS
● In L2/L3, 802.1p, DSCP, and COS QoS are supported.
● You should first create forwarding classes, which determine the queue number of the specifiedtraffic type.
●Define your QoS classifiers (by specifying the associated forwarding class) and include the trust-mode.Map the
code-point in the forwardingclass.
XorPlus
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 180
OpenFlow Configuration
OpenFlow Introduction
● In L2/L3, OpenFlow v1.0, OFv1.1, OFv1.2, and OFv1.3 are all supported. You can configure any supported
version in the CLI.
● All ports in the switch are either legacy or crossflow ports. In a crossflow port, you can enable or disable local-
control, regarding local processing of protocol packets.
● You can configure specified ports in crossflow mode, and enable/disable the local control in a crossflow port. If
you enable local control in a crossflow port, the protocol packet (containing the BPDU, LLDP, and OSPF PDU)
will be processed in the local protocol stack. In the mean time, the MAC learning and flood domain will also be
enabled in this crossflow port. Without local control, the protocol packet, MAC learning, and flood domain will
not be enabled in crossflow mode.
Crossflow Crossflow
Legacy port
L2/L3 mode, LC- L2/L3 mode, LC+
● In TCAM mode, traffic can be forwarded between the OpenFlow domain and the Legacy network domain
(e.g.,you can send traffic from acrossflow port toa legacy port, as shown in the following figures).
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 182
OpenFlow Configuration
Traffic Traffic
Traffic Traffic
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 183
OpenFlow Configuration
OpenFlowBasic Configuration
You can enable OpenFlow and configure a specifiedport as a crossflow port.
TheOpenFlow module needs resources in the ASIC to install flows. For example, you can allocate a specified
TCAM entry and L3 routing table entry for OpenFlow, as shown below. Allocate the resources before
enabling OpenFlow, or the configuration will not be successful.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 184
OpenFlow Configuration
Commit OK.
Save done.
[edit]
XorPlus#
(5) Configuringstaticflowmatchfields
You can create a static flow with the following matched fields: destination-port, ethernet-destination-
address, ethernet-destination-mask, ethernet-source-address, ethernet-source-mask,ethernet-type, ,
ingress-port, ip-destination-address, ip-dst-addr-mask, ip-protocol, ip-source-address, ip-src-addr-
mask,ip-tos, ipv6-destination-address, ipv6-source-address, source-port, vlan-id, and vlan-priority.
XorPlus# set open-flow flow f1 match-field ethernet-destination-address 22:22:22:22:22:22
[edit]
XorPlus# set open-flow flow f1 match-field ethernet-destination-mask fe:ff:ff:ff:ff:ff
[edit]
XorPlus# set open-flow flow f1 match-field vlan-id 100
[edit]
XorPlus# set open-flow flow f1 match-field ip-destination-address 192.168.1.0/24
[edit]
XorPlus# set open-flow flow f1 match-field ip-dst-addr-mask 255.255.255.0
[edit
XorPlus# set open-flow flow f1 match-field ethernet-type 2048
[edit]
XorPlus# set open-flow flow f1 action output interface ge-1/1/1
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# run show open-flow flow-table
cookie=0x0, duration=7.929s, table=0, n_packets=0, n_bytes=0,
ip,dl_vlan=100,dl_dst=22:22:22:22:22:22/fe:ff:ff:ff:ff:ff,nw_dst=192.168.1.0/24 actions=output:1
XorPlus#
You can also add “virtual-interface” as the output port (e.g. “all,” “drop” ,“local”), and configure “controller”
as the output port of a flow.
XorPlus# set open-flow flow f1 match-field ethernet-destination-address 22:22:22:22:22:22
[edit]
XorPlus# set open-flow flow f1 match-field vlan-id 100
[edit]
XorPlus# set open-flow flow f1 action output interface ge-1/1/1
[edit]
XorPlus# set open-flow flow f1 action output controller
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 185
OpenFlow Configuration
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus#
If you want add “local” as the output port, (e.g. arp flow) you can configure as following.
XorPlus# set open-flow flow f1 match-field ethernet-type 2054
[edit]
XorPlus# set open-flow flow f1 action output virtual-interface local
[edit]
XorPlus# set open-flow flow f1 action output virtual-interface all
[edit]
XorPlus# commit
Merging the configuration.
Commit OK.
Save done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 186
OpenFlow Configuration
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 187
OpenFlow Configuration
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
XorPlus# run show open-flow flow-table layer-3
FlowID Destination NetMask NextHopMac Output
------ --------------- --------------- ----------------- ---------
1 4.4.4.0 255.255.255.0 08:9e:01:39:1a:11 te-1/1/2
1 4.4.4.0 255.255.255.0 08:9e:01:39:1a:22 te-1/1/3
XorPlus#
You can configure multiple controllers for the OpenFlow bridge (only one of them will be the active
controller).
XorPlus# set open-flow controller contr-serv address 192.168.1.100
[edit]
XorPlus# set open-flow controller contr-serv port 6633
[edit]
XorPlus# set open-flow controller contr-serv protocol tcp
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
[edit]
user can create a group table and a flow whose action is a group table.
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 188
OpenFlow Configuration
[edit]
XorPlus# set open-flow groups group-id 1 bucket-id 1 action output-interface ge-1/1/2
[edit]
XorPlus# commit
Merging the configuration.
Commit OK.
Save done.
[edit]
XorPlus#
XorPlus# set open-flow flow f1 match-field ethernet-destination-address 22:00:00:00:00:00
[edit]
XorPlus# set open-flow flow f1 action group 1
[edit]
XorPlus# commit
Merging the configuration.
Commit OK.
Save done.
[edit]
XorPlus#
XorPlus#
XorPlus# run show open-flow groups
OFPST_GROUP_DESC reply (OF1.3) (xid=0x2):
group-id=1, type=all
bucket 1:
weight=NONE,watch_port=NONE,watch_group=NONE
actions=mod_dl_dst:22:22:22:22:22:22,output:2
XorPlus#
XorPlus# run show open-flow flow-table
cookie=0x0, duration=4.001s, table=0, n_packets=0, n_bytes=0, dl_dst=22:00:00:00:00:00
actions=group:1
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 189
OpenFlow Configuration
XorPlus#
OK
[edit]
XorPlus# commit
Merging the configuration.
Commit OK.
Save done.
[edit]
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 190
OpenFlow Configuration
XorPlus#
● Servers should not be able to communicate witheach other, which means traffic from a server can
onlybe forwarded in the upstream direction.
●The network should be scalable, and the configuration of the switch should be simple (e.g.,isolating the
traffic between serversby ACLs or VLANs is too complex of a configuration).
172.16.4.x OSPF/BGP
Gateway
172.16.1.1 172.16.3.1
V
P-3920
172.16.2.1
X X X X
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 191
OpenFlow Configuration
If youdo not wishto manually configure the above flows with the CLI, you can configure a controller to
perform those tasks:
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 192
OpenFlow Configuration
Commit OK.
Save done.
[edit]
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 193
OpenFlow Configuration
Commit OK.
Save done.
[edit]
XorPlus# set open-flow working-mode tcam-mode
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
XorPlus# set open-flow flow net-1-upstream match-field ingress-port te-1/1/1
[edit]
XorPlus# set open-flow flow net-1-upstream action output interface qe-1/1/49
[edit]
XorPlus# set open-flow flow net-1-upstream action modify ethernet-destination-address
22:22:22:22:22:22
[edit]
XorPlus# set open-flow flow net-2-upstream match-field ingress-port te-1/1/2
[edit]
XorPlus# set open-flow flow net-2-upstream action output interface qe-1/1/49
[edit]
XorPlus# set open-flow flow net-2-upstream action modify ethernet-destination-address
22:22:22:22:22:22
[edit]
XorPlus# set open-flow flow net-3-upstream match-field ingress-port te-1/1/3
[edit]
XorPlus# set open-flow flow net-3-upstream action output interface qe-1/1/49
[edit]
XorPlus# set open-flow flow net-3-upstream action modify ethernet-destination-address
22:22:22:22:22:22
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
XorPlus#
Be sure to configure the OSPF interface to work with the OSPF Layer 3 network.
XorPlus# set protocols ospf4 area 0.0.0.0 interface vlan400 vif vlan400 address 172.16.4.1
[edit]
XorPlus# set protocols ospf4 router-id 1.1.1.1
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
XorPlus# set policy policy-statement static-to-ospf term t1 from protocol connected
[edit]
XorPlus# set protocols ospf4 export static-to-ospf
[edit]
XorPlus# commit
Waiting for merging configuration.
Commit OK.
Save done.
XorPlus#
© 2013 Pica8 Inc. All Rights Reserved. L2/L3 Configuration Guide P a g e | 194