OpenSwitch OPX Configuration Guide Release 2.1.
017 - 7 Rev.
Contents 1 Network configuration....................................................................................................................................4 2 Interfaces...................................................................................................................................................... 5 Physical ports.....................................................................................................................................................................
1 Network configuration OpenSwitch OPX supports the ability to model and configure various networking features in the network processing unit (NPU) using two methods—Linux commands and CPS APIs. This information describes how to program networking features using Linux commands and open source applications. See Programmability in the OpenSwitch OPX Developers Guide for a description of the CPS framework, and detailed information on using the CPS API for configuration.
2 Interfaces You can create and manage physical and virtual interfaces—physical port interfaces are ports on the NPU and do not include the Management port. Each physical port on the NPU maps to a data port on the front panel of the device. Applications access physical and virtual ports using mapped Linux interfaces. The software allocates an ifindex for each Linux interface, and the value is used in CPS APIs to refer to a Linux interface.
• Fan-out interfaces • Port-channel/bond interfaces • VLAN interfaces Physical ports Physical ports are administratively down by default. Each interface has a reserved MAC hardware address derived from the system MAC address. Use standard Linux commands to configure physical interface parameters.
base-port/physical/loopback = 0 base-port/physical/hardware-port-id = 45 base-port/physical/npu-id = 0 base-port/physical/fanout-mode = 4 base-port/physical/breakout-capabilities base-port/physical/port-id = 45 base-port/physical/slot-id = 0 Deleting.. e101-005-0 Completed... = 4,2 Creating interface e101-005-1 Creating interface e101-005-2 Creating interface e101-005-3 Creating interface e101-005-4 Successfully created interfaces...
See www.kernel.org for more information about how to use bond interfaces, and see Application examples in the OpenSwitch OPX Developers Guide for more information on programming a bond interface using the CPS API. VLAN interfaces Virtual LANs (VLANs) define broadcast domains in a Layer 2 network, and an NPU VLAN entity is modeled as a separate Linux bridge instance. NPU entities (VLANs) are mapped to Linux entities (bridges).
3 Layer 2 bridging OpenSwitch OPX supports Layer 2 bridging and includes VLAN bridging, spanning-tree provisioning (STP), link layer discovery protocol (LLDP), and media access control (MAC) address forwarding. OpenSwitch OPX provides a CPS data model for configuring and managing the MAC address forwarding database using the CPS API. You can configure Layer 2 MAC addresses and VLAN learning and forwarding properties in support of Layer 2 bridging.
1 Create a bridge instance for the VLAN—br100 is the name of the bridge instance used to model the VLAN, and OpenSwitch OPX does not derive the VLAN ID from the name. $ brctl addbr br100 2 Add a tagged port to the VLAN to ensure that the Linux interface mapped to the port being added does not have an IP address. $ ifconfig e101-001-0 e101-001-0 Link encap:Ethernet HWaddr 90:b1:1c:f4:9d:3c inet addr:1.1.1.1 Bcast:1.1.1.255 Mask:255.255.255.
Add a Linux bond interface to a VLAN domain—bond1 is a Linux interface that maps to a LAG port in the NPU. Use the command to add the LAG port to the VLAN associated with the bridge instance in the NPU. $ ip link add link bond1 name bond1.200 type vlan id 200 $ brctl addif br200 bond1.200 Remove VLAN member from VLAN $ brctl delif br200 e101-001-0.100 Delete VLAN $ brctl delbr br200 Link layer discovery protocol OpenSwitch OPX supports the link layer discovery protocol (LLDP) daemon on Linux interfaces.
NOTE: OpenSwitch OPX does not support RSTP, MSTP, and RPVST in a Linux bridge due to a Linux kernel limitation. STP is not supported on a bridge which has multiple member interfaces with different VLAN IDs. See YANG model reference in the OpenSwitch OPX Developers Guide for more information on the dell-open-stp.yang model for the supported STP parameters. Linux STP does not support the concept of spanning-tree groups. In Linux, you can enable spanning tree independently in each bridge instance.
4 Layer 3 routing OpenSwitch OPX supports unicast routing over Linux interfaces using routes in the Linux kernel routing table. Applications can also use the CPS API to configure routes. This information describes how to configure Layer 3 unicast routing to provision the NPU. The OpenSwitch OPX routing subsystem manages the forwarding information base (FIB). The routing subsystem programs routes with resolved next hops using ARP/Neighbor table entries received from the Linux kernel.
$ ip route show default dev eth0 scope link 3.3.3.0/24 dev e101-003-0 proto kernel scope link 11.10.10.0/24 dev e101-003-0 scope link src 3.3.3.1 Configure static route with next-hop $ ip route add 30.30.30.0/24 via 3.3.3.3 $ ip route show default dev eth0 scope link 3.3.3.0/24 dev e101-003-0 proto kernel 30.30.30.0/24 via 3.3.3.3 dev e101-003-0 scope link src 3.3.3.1 Delete static route $ ip route delete 11.10.10.0/24 $ ip route show default dev eth0 scope link 3.3.3.
Configure IPv6 address $ ifconfig e101-003-0 inet6 add 3::1/64 $ ifconfig e101-003-0 e101-003-0 Link encap:Ethernet HWaddr 90:b1:1c:f4:a8:ea inet addr:3.3.3.1 Bcast:3.3.3.255 Mask:255.255.255.0 inet6 addr: 3::1/64 Scope:Global inet6 addr: fe80::92b1:1cff:fef4:a8ea/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:532 errors:0 dropped:0 overruns:0 frame:0 TX packets:173 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:46451 (45.3 KiB) TX bytes:25650 (25.
Configure IP address on R2 $ ip addr add 10.1.1.2/24 dev e101-007-0 $ ip addr add 12.1.1.1/24 dev e101-001-0 Verify configuration on R1 $ ip addr show e101-007-0 16: e101-007-0: mtu 1500 qdisc mq state UP group default qlen 500 link/ether 74:e6:e2:f6:af:87 brd ff:ff:ff:ff:ff:ff inet 10.1.1.
1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.709/0.709/0.709/0.000 ms View ARP table on R1 $ arp -n Address 11.1.1.2 10.1.1.2 HWtype ether ether HWaddress 00:00:00:1d:9a:bd 74:e6:e2:f6:ba:87 Flags Mask C C Iface e101-001-0 e101-007-0 HWaddress 74:e6:e2:f6:af:87 00:00:00:1d:9a:be Flags Mask C C Iface e101-007-0 e101-001-0 View ARP table on R2 $ arp -n Address 10.1.1.1 12.1.1.
Quagga daemons and the debian.conf file are stored in the /etc/quagga directory. All routing protocol daemons installed with Quagga are disabled by default. You must enable the zebra daemon to install the routes in the kernel routing table. 1 Open the daemons file for editing and change the daemon status to yes. $ vim /etc/quagga/daemons zebra=yes bgpd=yes ospfd=no ospf6d=no ripd=no ripngd=no isisd=no babeld=no 2 Create the vtysh.conf and Quagga.conf configuration files.
See github.com/opensourcerouting/quagga for complete information. Routing using Quagga This use case describes how to configure BGP using Quagga in a spine/leaf network. See github.com/opensourcerouting/quagga for complete information. Link Network Link Nodes BGP AS Number Leaf1-to-Spine1 10.1.1.0/24 Leaf1 64501 Spine1 64555 Leaf1 64501 Spine2 64555 Leaf2 64502 Spine1 64555 Leaf2 64502 Spine2 64555 Leaf1-to-Spine2 Leaf2-to-Spine1 Leaf2-to-Spine2 20.1.1.0/24 40.1.1.0/24 30.1.1.
leaf2(conf-if-e101-001-0)# ip address 12.1.1.1/24 leaf2(conf-if-e101-001-0)# no shutdown 3 Configure the IP addresses to Leaf1 and Leaf2 from Spine1. spine1(config)# interface e101-027-1 spine1(conf-if-e101-027-1)# ip address 10.1.1.2/24 spine1(conf-if-e101-027-1)# no shutdown spine1(conf-if-e101-027-1)# exit spine1(config)# interface e101-010-1 spine1(conf-if-e101-010-1)# ip address 40.1.1.2/24 spine1(conf-if-e101-010-1)# no shutdown 4 Configure the IP addresses to Leaf1 and Leaf2 from Spine2.
20.1.1.2 4 64555 195 206 0 0 0 02:38:57 4 Total number of neighbors 2 leaf2# show ip bgp sum BGP router identifier 40.1.1.1, local AS number 64502 RIB entries 11, using 1232 bytes of memory Peers 2, using 9136 bytes of memory Neighbor 30.1.1.2 40.1.1.2 V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down 4 64555 196 197 0 0 0 02:39:45 4 4 64555 192 204 0 0 0 02:39:42 4 State/PfxRcd Total number of neighbors 2 2 Verify BGP neighbors from Spine1 and Spine 2. spine1# show ip bgp sum BGP router identifier 40.
* C>* C>* B>* B>* C>* via 20.1.1.2, e101-051-0, 02:44:45 13.1.1.0/24 is directly connected, e101-002-0 20.1.1.0/24 is directly connected, e101-051-0 30.1.1.0/24 [20/0] via 20.1.1.2, e101-051-0, 02:09:44 40.1.1.0/24 [20/0] via 10.1.1.2, e101-049-0, 02:11:50 127.0.0.0/8 is directly connected, lo leaf2# show ip route Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF, I - IS-IS, B - BGP, A - Babel, > - selected route, * - FIB route B>* B>* * C>* B>* C>* C>* C>* 5 10.1.1.
4098 4098 0 0 10.1.1.0/24 20.1.1.
5 Security OpenSwitch OPX secures your network using access control lists (ACLs) and quality of service (QoS). ACLs Access control lists are flexible, hardware-accelerated sets of rules that match packets using packet header criteria, and perform actions on selected packets. Configure an ACL on a physical port (NPU) only by using the CPS API.
6 Monitoring OpenSwitch OPX supports network monitoring features such as port mirroring and sFlow which monitor and capture network traffic in the system. It also provides tools to collect port and VLAN statistics, and port media information. Port mirroring Mirroring copies packets from a source port to a destination port. OpenSwitch OPX supports local and remote porting mirroring using CPS and Dell EMC-specific commands—not standard Linux commands.
• Disable packet sampling on a physical port • Set the sampling interval rate • Forward the sampled packet to an IP address/port See Application examples in the OpenSwitch OPX Developers Guide for more information on how to configure sFlow using the CPS API. Port statistics OpenSwitch OPX provides scripts to view statistical information about ports, VLANs, and installed transceivers. • Display port statistics for all or a specified Linux interface which maps to physical ports.
base-stats/interface/if/in-ucast-pkts = 0 base-stats/interface/ether-out/pkts-128-to-255-octets = 2281 base-stats/interface/ether-in/pkts-2048-to-4095-octets = 0 base-stats/interface/ether-tx-oversize-pkts = 0 base-stats/interface/ether/pkts-256-to-511-octets = 0 base-stats/interface/ether-multicast-pkts = 36295 base-stats/interface/ether-out/pkts-4096-to-9216-octets = 0 base-stats/interface/ether/pkts-128-to-255-octets = 2281 base-stats/interface/ether-in/pkts-128-to-255-octets = 0 base-stats/interface/tim
rx_65_to_127_byte_packets: 0 rx_128_to_255_byte_packets: 0 rx_256_to_511_byte_packets: 0 rx_512_to_1023_byte_packets: 0 rx_1024_to_1518_byte_packets: 0 rx_1519_to_2047_byte_packets: 0 rx_2048_to_4095_byte_packets: 0 rx_4096_to_9216_byte_packets: 0 tx_64_byte_packets: 0 tx_65_to_127_byte_packets: 33217 tx_128_to_255_byte_packets: 2228 tx_256_to_511_byte_packets: 0 tx_512_to_1023_byte_packets: 0 tx_1024_to_1518_byte_packets: 8967736 tx_1519_to_2047_byte_packets: 0 tx_2048_to_4095_byte_packets: 0 tx_4096_to_92
base-pas/media/rx-power-measurement-type = 0 base-pas/media/wavelength = 0 base-pas/media/cc_base = 54 base-pas/media/temp-low-alarm-threshold = base-pas/media/tx-power-low-warning-threshold = base-pas/media/insertion-timestamp = 0 base-pas/media/current-voltage = base-pas/media/bias-high-alarm-threshold = base-pas/media/high-power-mode = 1 base-pas/media/br-nominal = 0 base-pas/media/options = 0 base-pas/media/rx-power-high-warning-threshold = base-pas/media/date-code = 3131303632322000 base-pas/media/pres
7 Support resources The Dell Networking Support site provides a range of documents and tools to assist you with effectively using Dell Networking devices. Through the support site you can obtain technical information regarding Dell Networking products, access software upgrades and patches, download available management software, and manage your open cases. The Dell Networking support site provides integrated, secure access to these services. To access the Dell Networking Support site, go to www.dell.
