VSC6816-4.1 SMBStaXww1.microchip.com/downloads/en/DeviceDoc/VSC6816_SMBStaX_S… · VSC6816 SMBStaX Software Product Specification Product Overview The SMBStaX turnkey software package

VSC6816 SMBStaX Software Product Specification

Product Overview

The SMBStaX turnkey software package is a fully managed L2 switch application for the small and medium-sizedenterprise (SME). This software package can be customized to support different port configurations. The SMBStaXsoftware supports the following major capabilities.

• RedBoot bootloader• U-boot bootloader• Web or XMODEM update

Management is done using a web graphical user interface (GUI), command line interface (CLI), Simple NetworkManagement Protocol (SNMP), or JavaScript Object Notation-Remote Procedure Call (JSON- RPC) running on theinternal MIPS24Kec CPU. SMBStaX is highly integrated with switch features such as QoS control lists (QCLs),access control lists (ACLs), and super priority management queue.

This document provides an overview of the switch and software features of the SMBStaX software and lays the basisfor further specifications. The supported configuration details including parameters and limitations are beyond thescope of this document. The module specific requirement specifications and configuration guides may be referred tofor obtaining these details.

Supported Switch PlatformsThis software is supported on a series of Microchip switches with 12, 26, or 57 ports with Power over Ethernet (PoE)/non-PoE capabilities. The following table shows the supported switches.

Table 1. Supported Switches

Switch Description

VSC7410 6-port SGMII Gigabit Ethernet Switch with VeriTime™ and Gigabit Ethernet PHYs

VSC7414 11-port layer 2 SGMII Gigabit Ethernet Enterprise Switch with VeriTime™

VSC7415 6-Port SGMII Gigabit Ethernet Switch with VeriTime™, Integrated DPLL, and Gigabit EthernetPHYs

VSC7416 6-port Carrier Ethernet Switch Engine with ViSAA™, VeriTime™, and MPLS/MPLS-TP


VSC7423 7-port, layer 2 Gigabit Ethernet Switch with VeriTime™, 5 Integrated Copper PHYs, andEmbedded 32-bit CPU

VSC7424 10-port layer 2 Gigabit Ethernet Switch with 8 Fully Integrated Copper PHYs and Embedded416-MHz CPU


© 2020 Microchip Technology Inc. Product Specification DS30010226A-page 1

...........continuedSwitch Description



VSC7428 11-port Carrier Ethernet Switch Engine with ViSAA™, VeriTime™, and PHYs

VSC7429 26-port Carrier Ethernet Switch with ViSAA™, VeriTime™, and 12 Fully Integrated Copper PHYs

VSC7430 6-port Carrier Ethernet Switch with ViSAA™, VeriTime™, and Gigabit Ethernet PHYs

VSC7435 6-port Carrier Ethernet Switch with ViSAA™, VeriTime™, and Integrated DPLLs and GigabitEthernet PHYs

VSC7436 10-port Carrier Ethernet Switch with ViSAA™, VeriTime™, and Integrated Gigabit Ethernet PHYs

VSC7437 8-port Carrier Ethernet Switch with ViSAA™, VeriTime™, and Integrated DPLLs and GigabitEthernet PHYs

VSC7438 14-port Carrier Ethernet Switch with ViSAA™, VeriTime™, MPLS-TP, and L3 Routing

VSC7440 10-port L2/L3 Enterprise Gigabit Ethernet Switch with 10 Gbps Links

VSC7442 52-port L2/L3 Enterprise and Industrial Ethernet Switch



VSC7449 6-port SGMII Gigabit Ethernet Switch with VeriTime™ and Gigabit Ethernet PHYs

VSC7464 11-port layer 2 SGMII Gigabit Ethernet Enterprise Switch with VeriTime™


VSC7513 8-port L2 Gigabit Ethernet Switch

VSC7514 10-port L2 Gigabit Ethernet Switch

VSC7546 29-port L2/L3 Industrial Gigabit Ethernet Switches





VSC7546TSN 29-port L2/L3 Industrial Gigabit Ethernet Switches





The following table lists the supported 1G PHYs.

VSC6816


Table 2. Supported 1G PHYs

PHY Description

VSC8211 Single-port 10/100/1000BASE-T PHY and 1000BASE-X PHY with SGMII, SerDes, GMII, MII, TBI,RGMII/RTBI MAC Interfaces

VSC8221 Single-port 10/100/1000BASE-T PHY with 1.25 Gbps SerDes/SGMII for SFPs/GBICs

VSC8501 Single-port GbE Copper PHY with Synchronous Ethernet and RGMII/GMII Interface

VSC8502 Dual-port GbE Copper PHY with Synchronous Ethernet and RGMII/GMII Interface

VSC8504 Quad-port 10/100/1000BASE-T PHY with Synchronous Ethernet and QSGMII/SGMII MAC

VSC8512 12-port 10/100/1000BASE-T PHY with SGMII and QSGMII MAC Interface

VSC8514 Quad-port Gigabit Copper EEE PHY with QSGMII MAC-to-PHY Interface

VSC8522 12-port 10/100/1000BASE-T PHY with QSGMII MAC Interface

VSC8552 Dual-port RGMII/SGMII/QSGMII Dual Media PHY with EEE Support

VSC8562 Dual-port 10/100/1000BASE-T PHY with Synchronous Ethernet, Intellisec™, and QSGMII/SGMII MAC

VSC8564 Dual-port 10/100/1000BASE-T PHY with Synchronous Ethernet, MACsec, and QSGMII/SGMII MAC

VSC8572 Dual-port 10/100/1000BASE-T PHY with VeriTime™, Synchronous Ethernet, and RGMII/SGMII MAC

VSC8574 Quad-port Dual Media QSGMII/SGMII GbE PHY with VeriTime™

VSC8575 Quad-port 10/100/1000BASE-T PHY with Synchronous Ethernet, VeriTime™, and QSGMII/SGMIIMAC

VSC8582 Dual-port Dual Media QSGMII/SGMII GbE PHY with Intellisec™ and VeriTime™

VSC8584 Quad-port Dual Media QSGMII/SGMII GbE PHY with Intellisec™ and VeriTime™

The following table lists the supported 10G PHYs.

Table 3. Supported 10G PHYs

PHY Description

VSC8254 Dual Channel 1G/10GBASE-KR to SFI Ethernet LAN/WAN PHY with VeriTime™ and Intellisec™

VSC8256 Quad Channel 1G/10GBASE-KR to SFI Ethernet Repeater

VSC8257 Quad Channel 1G/10GBASE-KR to SFI Ethernet WIS PHY with VeriTime™ and Intellisec™

VSC8258 Quad Channel 1G/10GBASE-KR to SFI Ethernet WIS PHY with VeriTime™ and Intellisec™

VSC8489 Dual-port WAN/LAN/Backplane RXAUI/XAUI to SFP+/KR 10 GbE PHY

VSC8490 Dual-port WAN/LAN/Backplane RXAUI/XAUI to SFP+/KR 10 GbE PHY with Intellisec™ andVeriTime™

VSC8491 WAN/LAN/Backplane RXAUI/XAUI to SFP+/KR 10 GbE PHY with Intellisec™ and VeriTime™

Software ArchitectureThe SMBStaX software provides support for standalone switches. It consists of the following components.

VSC6816


• Operating system (Linux) for access to the hardware.• Application programming interface (API) for a function library to control switches and PHYs.• Control modules, such as port control, MSTP, and Virtual LAN (VLAN)—to implement product features and

protocols. These modules may include threads and provide a management API for configuration and monitoring.• Management modules, such as CLI, web, JSON-RPC, and SNMP—for interfaces to the system based on the

management API of the control modules.

The following illustration shows the architecture of the Microchip managed application software and a few control andmanagement modules.

Figure 1. Application Architecture

VSC6816


Table of Contents

Product Overview...........................................................................................................................................1

1. Supported Switch Platforms.........................................................................................................12. Software Architecture...................................................................................................................3

1. Supported Features................................................................................................................................ 8

1.1. BSP and API................................................................................................................................ 81.2. Port Control.................................................................................................................................. 81.3. Quality of Service (QoS).............................................................................................................101.4. L2 Switching...............................................................................................................................101.5. L3 Switching...............................................................................................................................131.6. Synchronization..........................................................................................................................141.7. Security...................................................................................................................................... 151.8. Robustness and Power Savings................................................................................................ 161.9. Customization Framework..........................................................................................................171.10. Management.............................................................................................................................. 181.11. SNMP MIBs................................................................................................................................21

2. Features and Platform Capacity............................................................................................................23

3. System Requirements...........................................................................................................................26

4. Port and System Capabilities................................................................................................................ 28

4.1. Port Capability............................................................................................................................284.2. System Capability.......................................................................................................................28

5. Firmware Upgrade................................................................................................................................ 29

6. Port Control........................................................................................................................................... 30

6.1. NPI Port......................................................................................................................................306.2. PCIe........................................................................................................................................... 306.3. SFP Detection............................................................................................................................ 306.4. VeriPHY Support........................................................................................................................ 306.5. PoE/PoE+ Support..................................................................................................................... 306.6. POE/POE+ with LLDP................................................................................................................30

7. Quality of Services (QoS)......................................................................................................................31

7.1. Port Policers...............................................................................................................................317.2. Scheduling and Shaping............................................................................................................ 317.3. QoS Control List (QCL) Configuration........................................................................................317.4. Weighted Random Early Detection (WRED)..............................................................................317.5. Tag Remarking........................................................................................................................... 317.6. Ingress Port Classification..........................................................................................................327.7. Queue Policers...........................................................................................................................327.8. DiffServ (RFC2474) Remarking................................................................................................. 32

8. L2 Switching..........................................................................................................................................33

8.1. Virtual LAN................................................................................................................................. 338.2. Voice VLAN................................................................................................................................ 33

VSC6816


8.3. Generic VLAN Registration Protocol (GVRP)............................................................................ 348.4. Industrial Private VLANs............................................................................................................ 348.5. Multiple Registration Protocol (MRP)......................................................................................... 358.6. Multiple VLAN Registration Protocol (MVRP)............................................................................ 358.7. IEEE 802.3ad Link Aggregation................................................................................................. 358.8. Bridge Protocol Data Unit (BPDU) Guard, Restricted Role, and Error Disable Recovery..........368.9. Error Disable Recovery.............................................................................................................. 368.10. IGMP and Multicast Listener Discovery (MLD).......................................................................... 368.11. Filtering (IGMP Snooping and MLD Snooping)..........................................................................368.12. DHCP Snooping.........................................................................................................................368.13. Multicast VLAN Registration (MVR)........................................................................................... 368.14. MAC Table Configuration........................................................................................................... 378.15. Mirroring (SPAN/VSPAN and RSPAN)....................................................................................... 378.16. RMirror....................................................................................................................................... 378.17. Flow Mirroring for AC................................................................................................................. 378.18. Spanning Tree............................................................................................................................378.19. Loop Guard................................................................................................................................ 38

9. L3 Switching..........................................................................................................................................39

9.1. DHCP Relay...............................................................................................................................399.2. Universal Plug and Play (UPnP)................................................................................................ 399.3. L3 Routing..................................................................................................................................39

10. Synchronization.....................................................................................................................................40

10.1. Network Time Protocol (NTP).....................................................................................................40

11. Security................................................................................................................................................. 41

11.1. 802.1X and MAC-Based Authentication.....................................................................................4111.2. Port Security...............................................................................................................................4211.3. Authentication, Authorization, and Accounting (AAA)................................................................ 4211.4. Secure Access........................................................................................................................... 4211.5. Users and Privilege Levels.........................................................................................................4311.6. Authentication and Authorization Methods.................................................................................4311.7. Access Control List (ACLs)........................................................................................................ 4411.8. ARP Inspection/IP and IPv6 Source Guard................................................................................45

12. Robustness and Power Savings........................................................................................................... 46

12.1. Robustness................................................................................................................................ 4612.2. Power Savings........................................................................................................................... 46

13. Management......................................................................................................................................... 48

13.1. JSON-RPC.................................................................................................................................4813.2. Management Services................................................................................................................4813.3. SNMP.........................................................................................................................................5113.4. RMON Statistics.........................................................................................................................5113.5. Internet Control Message Protocol.............................................................................................5113.6. SysLog....................................................................................................................................... 5213.7. LLDP-MED................................................................................................................................. 5213.8. 802.1AB LLDP and CDP Aware.................................................................................................53

VSC6816


13.9. IP Management, DNS, and DHCPv4/v6.....................................................................................5413.10. IPv6 Ready Logo Phase2.......................................................................................................... 5513.11. DHCP Server..............................................................................................................................5513.12. Console......................................................................................................................................5513.13. System Management................................................................................................................. 5513.14. Crash File Support..................................................................................................................... 5513.15. Management Access Filtering....................................................................................................5513.16. sFlow..........................................................................................................................................5613.17. Default Configuration................................................................................................................. 5613.18. Configuration Upload/Download................................................................................................ 5613.19. Port Statistics............................................................................................................................. 5613.20. Loop Detection Restore to Default.............................................................................................56

14. SNMP MIBs...........................................................................................................................................57

15. Revision History.................................................................................................................................... 58

The Microchip Website.................................................................................................................................63

Product Change Notification Service............................................................................................................63

Customer Support........................................................................................................................................ 63

Microchip Devices Code Protection Feature................................................................................................ 63

Legal Notice................................................................................................................................................. 63

Trademarks.................................................................................................................................................. 64

Quality Management System....................................................................................................................... 64

Worldwide Sales and Service.......................................................................................................................65

VSC6816


1. Supported FeaturesThe following sections describe the features of each module in the SMBStaX software.

1.1 BSP and APIThe following table lists the features supported by the Board Support Package (BSP) and API module.

Table 1-1. BSP and API: Supported Features

Feature Luton26

VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

Serval-1

VSC7414

VSC7416

VSC7418

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7438

VSC7464

VSC7468

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5

VSC7546VSC7549VSC7552VSC7556VSC7558

Internal CPU • • • • • •

External CPU — — — — — •

64-bit CPU Architecture — — — — — •

API and application split • • • • • •

MESA layer • • • • • •

MEBA layer • • • • • •

U-Boot • • • • • •

U-Boot network support • • • • • •

32MB NOR FLASH onlyoption

• • • • • —

64MB NOR FLASH onlyoption

• • • • • —

1.2 Port ControlThe following table lists the features supported by the port control module. For more information, see 6. Port Control.

VSC6816Supported Features


Table 1-2. Port Control: Supported Features

Feature Luton26

VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

Serval-1

VSC7414

VSC7416

VSC7418

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7438

VSC7464

VSC7468

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5


Port speed/duplex mode/flowcontrol

• • • • • •

Aquantia 2.5G PHY Gen2 • • • • • •

Aquantia 2.5G PHY Gen3 • • • • • •

Aquantia 5G PHY Gen3 — — • — — —

Aquantia 10G PHY Gen2 — — • • — •

802.1Qbb per priority flowcontrol

— • • • • •

Port frame size (jumbo frames) • • • • • •

Port state (administrativestatus)

• • • • • •

Port status (link monitoring) • • • • • •

Port statistics (MIB counters) • • • • • •

Port VeriPHY (cablediagnostics)

• • • • • •

PoE/PoE+ with PD69208support

• • • • • —

PoE/PoE+ with Link LayerDiscovery Protocol (LLDP)

• • • • • —

PoE IEEE802.3bt w/o LLDP • • • • • —

NPI port • • • • • •

PCIe — • • • • •

On-the-fly SFP detection • • • • • •

DDMI • • • • • •

Unidirectional Link Detection(UDLD)

• • • • • •



1.3 Quality of Service (QoS)The following table lists the features supported by the QoS module. For more information, see 7. Quality of Services(QoS).Table 1-3. QoS: Supported Features

Feature Luton26

VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

Serval-1

VSC7414

VSC7416

VSC7418

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7438

VSC7464

VSC7468

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5


Traffic classes (8 activepriorities)

• • • • • •

Port default priority • • • • • •

User priority • • • • • •

Input priority mapping • • • • • •

QoS control list (QCL mode) • • • • • •

Global storm control for UC,MC, and BC

• • • • • •

Random early discard (RED) — • • • • •

Port policers • • • • • •

Queue policers • • • • • •

Global/VCAP (ACL) policers • • • • • •

Port egress shaper • • • • • •

Queue egress shapers • • • • • •

DiffServ (RFC2474) remarking • • • • • •

Tag remarking • • • • • •

Scheduler mode • • • • • •

1.4 L2 SwitchingThe following table lists the features supported by the L2 Switching module. For more information, see 8. L2Switching.



Table 1-4. L2 Switching: Supported Features

Feature Luton26

VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

Serval-1

VSC7414

VSC7416

VSC7418

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7438

VSC7464

VSC7468

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5


IEEE 802.1D Bridge

Auto MAC address learning/aging

• • • • • •

MAC addresses—static • • • • • •

IEEE 802.1Q

Virtual LAN • • • • • •

Bidirectional VLAN translation • • • • • •

Unidirectional VLANtranslation (ingress/egress)

• • • • • •

Private VLAN—static • • • • • •

Port isolation—static • • • • • •

MAC-based VLAN • • • • • •

Protocol-based VLAN • • • • • •

IP subnet-based VLAN • • • • • •

VLAN trunking • • • • • •

iPVLAN trunking — • • • • •

GARP VLAN RegistrationProtocol (GVRP)

• • • • • •

Multiple Registration Protocol(MRP)

• • • • • •

Multiple VLAN RegistrationProtocol (MVRP)

• • • • • •

IEEE 802.1ad provider bridge(native or translated VLAN)

• • • • • •

Multiple Spanning TreeProtocol (MSTP)

• • • • • •



...........continuedFeature Luton26

VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

Serval-1

VSC7414

VSC7416

VSC7418

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7438

VSC7464

VSC7468

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5


Rapid spanning tree protocol(RSTP) and STP

• • • • • •

Loop guard • • • • • •

IEEE 802.3ad

Link aggregation—static • • • • • •

Link aggregation—LinkAggregation Control Protocol(LACP)

• • • • • •

AGGR/LACP user interfacealignment with industrystandard

• • • • • •

UNI LAG (LACP) 1:1 active/standby

• • • • • •

LACP revertive/non-revertive • • • • • •

LACP loop free operation • • • • • •

Bridge Protocol Data Unit(BPDU) guard and restrictedrole

• • • • • •

Error disable recovery • • • • • •

IGMPv2 snooping • • • • • •

IGMPv3 snooping • • • • • •

MLDv1 snooping • • • • • •

MLDv2 snooping • — • • — •

Internet Group ManagementProtocol (IGMP) filteringprofile

• • • • • •

IP Multicast (IPMC) throttling,filtering, leave proxy

• • • • • •




VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

Serval-1

VSC7414

VSC7416

VSC7418

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7438

VSC7464

VSC7468

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5


Multicast VLAN Registration(MVR)

• • • • • •

MVR profile • • • • • •

Voice VLAN • • • • • •

DHCP snooping • • • • • •

ARP inspection • • • • • •

Port mirroring • • • • • •

Flow mirroring • • • • • •

Rmirror • • • • • •

1.5 L3 SwitchingThe following table lists the features supported by the L3 switching module. For more information, see 9. L3Switching.Table 1-5. L3 Switching: Supported Features

Feature Luton26

VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

Serval-1

VSC7414

VSC7416

VSC7418

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7438

VSC7464

VSC7468

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5


DHCP option 82 relay • • • • • •

Universal Plug and Play (UPnP) • • • • • •




VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

Serval-1

VSC7414

VSC7416

VSC7418

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7438

VSC7464

VSC7468

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5


Software-based IPv4 L3 staticrouting with Linux Kernelintegration

• • — — • —

Hardware-based IPv4 L3 staticrouting with Linux Kernelintegration

— — • • — •

RFC2992 (ECMP) support forHW based L3 static routing

— — • • — •

RFC 2453 RIPv2 dynamicrouting

— — • • — •

RFC 2328 OSPFv2 Dynamicrouting

— — • • — •

RFC 3101 The OSPF Not-So-Stubby Area (NSSA) Option

— — • • — •

RFC 3137 OSPF Stub RouterAdvertisement

— — • • — •

Software-based IPv6 L3 staticrouting

• • — — • —

Hardware-based IPv6 L3 staticrouting

— — • • — •

RFC-1812 L3 checking(version, IHL, checksum, and soon)

• • • • • •

1.6 SynchronizationThe following table lists the features supported by the synchronization module. For more information, see 10. Synchronization.



Table 1-6. Synchronization: Supported Features

Feature Luton26

VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

Serval-1

VSC7414

VSC7416

VSC7418

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7438

VSC7464

VSC7468

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5


NTPv4 client • • • • • •

1.7 SecurityThe following table lists the features supported by the security module. For more information, see 11. Security.Table 1-7. Security: Supported Features

Feature Luton26

VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

Serval-1

VSC7414

VSC7416

VSC7418

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7438

VSC7464

VSC7468

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5


Network Access Server (NAS)

Port-based 802.1X • • • • • •

Single 802.1X • • • • • •

Multiple 802.1X • • • • • •

MAC-based authentication • • • • • •

VLAN assignment • • • • • •

QoS assignment • • • • • •

Guest VLAN • • • • • •

Remote authentication dial Inuser service (RADIUS)authentication and authorization

• • • • • •

RADIUS accounting • • • • • •




VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

Serval-1

VSC7414

VSC7416

VSC7418

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7438

VSC7464

VSC7468

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5


MAC address limit • • • • • •

Persistent MAC learning • • • • • •

IP MAC binding • • • • • •

IP/MAC binding dynamic tostatic

• • • • • •

TACACS+ authentication andauthorization

• • • • • •

TACACS+ commandauthorization

• • • • • •

TACACS+ accounting • • • • • •

Web and CLI authentication • • • • • •

Authorization (15 user levels) • • • • • •

ACLs for filtering/policing/portcopy

• • • • • •

IP source guard • • • • • •

Secure FTP client • • • • • •

1.8 Robustness and Power SavingsThe following table lists the features supported by the robustness and power savings module. For more information,see 12. Robustness and Power Savings.



Table 1-8. Robustness and Power Savings: Supported Features

Feature Luton26

VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

Serval-1

VSC7414

VSC7416

VSC7418

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7438

VSC7464

VSC7468

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5


Cold start • • • • • •

Cool start • • • • • •

ActiPHY • • • • • •

PerfectReach • • • • • •

Energy-Efficient Ethernet(EEE) power management

• • • • • •

LED power management • • • — — •

Thermal protection • • • • • •

Adaptive fan control • • • • — —

1.9 Customization FrameworkThe following table lists the features supported by the customization framework module.Table 1-9. Customization Framework: Supported Features

Feature Luton26

VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

Serval-1

VSC7414

VSC7416

VSC7418

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7438

VSC7464

VSC7468

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5


Separate BSP and application • • • • • •

Append or change a binaryimage

• • • • • •

IPC JSON-RPC socket (withnotification support)

• • • • • •




VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

Serval-1

VSC7414

VSC7416

VSC7418

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7438

VSC7464

VSC7468

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5


Overwrite default startupconfiguration

• • • • • •

Boot and initialization of third-party daemons

• • • • • •

Configuration to disable certainbuilt-in features

• • • • • •

Microchip Ethernet board API(MEBA)

• • • • • •

1.10 ManagementThe following table lists the features supported by the management module. For more information, see 13. Management.Table 1-10. Management: Supported Features

Feature Luton26

VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

Serval-1

VSC7414

VSC7416

VSC7418

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7438

VSC7464

VSC7468

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5


JSON-RPC • • • • • •

JSON-RPC notifications • • • • • •

Dual CPU (application variantwith JSON

— • • • • •

RFC 2131 DHCP client • • • • • •

RFC 2131 DHCP server • • • • • •




VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

Serval-1

VSC7414

VSC7416

VSC7418

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7438

VSC7464

VSC7468

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5


DHCP server support forDHCP relay packets

• • • • • •

DHCP per port • • • • • •

RFC 3315 DHCPv6 client • • • • • •

RFC 3315 DHCPv6 relayagent

• • • • • •

RFC 7610 DHCPv6-shieldprotecting against rogueDHCPv6 servers

• • • • • •

RFC 1035 DNS client andrelay

• • • • • •

IPv4/IPv6 ping • • • • • •

IPv4/IPv6 traceroute • • • • • •

HTTP server • • • • • •

CLI—console port • • • • • •

CLI—Telnet • • • • • •

Industrial standard CLI • • • • • •

Industrial standardconfiguration

• • • • • •

Industrial standard CLI debugcommands

• • • • • •

Port description CLI • • • • • •

Management access filtering • • • • • •

HTTPS • • • • • •

SSHv2 • • • • • •

IPv6 management • • • • • •

IPv6 ready logo PHASE2 • • • • • •




VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

Serval-1

VSC7414

VSC7416

VSC7418

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7438

VSC7464

VSC7468

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5


RFC4884 (ICMPv6) • • • • • •

System syslog • • • • • •

Software upload through web • • • • • •

SNMP v1/v2c/v3 agent1 • • • • • •

RMON (group 1, 2, 3, and 9) • • • • • •

RMON alarm and event (CLIand web)

• • • • • •

Alarm module • • • • • •

IEEE 802.1AB-2005 link layerdiscovery—LLDP

• • • • • •

TIA 1057 LLDP—MED • • • • • •

Industry standard discoveryprotocol - ISDP

• • • • • •

sFlow • • • • • •

FTP client • • • • • •

Configuration download/upload— industrial standard

• • • • • •

Loop detection restore todefault

• • • • • •

Symbolic register access • • • • • •

Daylight saving • • • • • •

SD/MMC card slot support — • — — — —

Note: 1. No SNMPv1 trap support.



1.11 SNMP MIBsThe following table lists the features supported by the SNMP MIBs module. For more information, see 14. SNMPMIBs.Table 1-11. SNMP MIBs: Supported Features

Feature Luton26

VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

Serval-1

VSC7414

VSC7416

VSC7418

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7438

VSC7464

VSC7468

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5


RFC 2674 VLAN MIB • • • • • •

IEEE 802.1Q bridge MIB 2008 • • • • • •

RFC 2819 RMON (group 1, 2, 3,and 9)

• • • • • •

RFC 1213 MIB II • • • • • •

RFC 1215 TRAPS MIB • • • • • •

RFC 4188 bridge MIB • • • • • •

RFC 4292 IP forwarding table MIB • • • • • •

RFC 4293 managementinformation base for the Internetprotocol (IP)—IPv6

• • • • • •

RFC 5519 multicast groupmembership discovery MIB

• • • • • •

RFC 4668 RADIUS authenticationclient MIB

• • • • • •

RFC 4670 RADIUS accountingMIB

• • • • • •

RFC 3635 Ethernet-like MIB • • • • • •

RFC 2863 interface group MIBusing SMI v2

• • • • • •

RFC 3636 802.3 MAU MIB • • • • • •

RFC 4133 entity MIB version 3 • • • • • •

RFC 3411 SNMP managementframeworks

• • • • • •




VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

Serval-1

VSC7414

VSC7416

VSC7418

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7438

VSC7464

VSC7468

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5


RFC 3414 user-based securitymodel for SNMPv3

• • • • • •

RFC 3415 view-based accesscontrol model for SNMP

• • • • • •

RFC 2613 SMON VLAN statistics — — • • — —

RFC 2613 SMON—PortCopy • • • • • •

IEEE 802.1 MSTP MIB • • • • • •

IEEE 802.1AB LLDP-MIB (LLDPMIB included in a clause of theSTD)

• • • • • •

IEEE 802.3ad (LACP MIB includedin a clause of the STD)

• • • • • •

IEEE 802.1X (PAE MIB included ina clause of the STD)

• • • • • •

TIA 1057 LLDP-MED (MIB is partof the STD)

• • • • • •

RFC 3621 LLDP-MED power(PoE) (no specific MIB for PoE+exists)

• • • • • —

Private MIB framework • • • • • •



2. Features and Platform CapacityThe following table lists the features and platform capacity supported by the SMBStaX software. The capacitymentioned can be either software or hardware constrained, depending on the case.Table 2-1. Features and Platform Capacity

Feature SparX-III

and

Caracal

VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

SparX-IIIand

Serval-1

VSC7414

VSC7416

VSC7418

SparX-IV

and

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7464

VSC7468

SparX-IV

and

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5

VSC7546VSC7549

VSC7552

VSC7556

VSC7558

Resilience andAvailability

IEEE 802.1s MSTPinstances

8 8 8 8 8 8

IEEE 802.3ad LACP: MaxLAGs

5 LAGs 5 LAGs inVSC7414/18

3 LAGs inVSC7416

7 LAGs inVSC7438

26 LAGs inVSC7442/48/49/68

13 LAGs inVSC7444/64

3 LAGs inSC7410/15,VSC7430/35

5 LAGs inVSC7436,VSC7440

4 LAGs inVSC7437

4 LAGs inVSC7513

5 LAGs inVSC7514

35 LAGs inVSC7546

37 LAGs inVSC7549,VSC7552,VSC7556,VSC7558

Traffic Control

Port-based VLAN 4095 4095 4095 4095 4095 4095

Guest-VLAN 1 1 1 1 1 1

Private VLAN 11 11 inVSC7414/18

7 inVSC7416

14 inVSC7438

52 inVSC7442/48/49/68

26 inVSC7444/64

6 in VSC7410/15,VSC7430/35

10 in VSC7436,VSC7440 8 inVSC7437

8 inVSC7513

10 inVSC7514

9

Voice VLAN 1 1 1 1 1 1

VSC6816Features and Platform Capacity


...........continuedFeature SparX-III

and

Caracal

VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

SparX-IIIand

Serval-1

VSC7414

VSC7416

VSC7418

SparX-IV

and

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7464

VSC7468

SparX-IV

and

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5

VSC7546VSC7549

VSC7552

VSC7556

VSC7558

MAC table size 8K 8K 8K 32K 8K inVSC7410/15/30/35

16K inVSC7436/37/40

4K 32K

Storm control 1, 2, 4, 8,16, 32, 64,128, 256,512, 1000,2000,4000,8000,16000,32000,64000,128000,256000,512000, or1024000kpps(globalsetting forUnicast,Multicast,andBroadcast)

1, 2, 4, 8,16, 32, 64,128, 256,512, 1000,2000,4000,8000,16000,32000,64000,128000,256000,512000, or1024000kpps(globalsetting forUnicast,Multicast,andBroadcast)

25 kbps–10Gbps [per portfor Unicast(known/learned),Broadcast,and Unknown(floodedUnicast andMulticast)]

25 kbps–10 Gbps[per port forUnicast (known/learned),Broadcast, andUnknown (floodedUnicast andMulticast)]

25 kbps –10 Gbps[per port forUnicast(known/learned),Broadcast,andUnknown(floodedUnicastandMulticast)]

10kbps –13128mbps

Jumbo frames supported Up to10056

Up to10240

Up to 10240 Up to 10240 Up to10240

10240

Security

Port security aging 10 to10000000s

10 to10000000s

10 to10000000s

10 to 10000000s 10 to10000000s

10 to10000000s

MAC address limit 1024 1024 1024 1024 1024 1024

Static MAC entriessupported

64 64 64 64 64 64



...........continuedFeature SparX-III

and

Caracal

VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

SparX-IIIand

Serval-1

VSC7414

VSC7416

VSC7418

SparX-IV

and

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7464

VSC7468

SparX-IV

and

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5

VSC7546VSC7549

VSC7552

VSC7556

VSC7558

RADIUS authenticationservers

5 5 5 5 5 5

TACACS+ authenticationservers

5 5 5 5 5 5

RADIUS accountingservers

5 5 5 5 5 5

Telnet/SSH v2 4 4 4 4 4 4

Max ARP inspection 1K persystem

1K per system 1K per system 1K persystem

1K persystem

IPSG entries Up to 256 Up to 512 Up to 512 Up to 512 persystem

Up to 512per system

512

Policy-based securityfiltering

512 512 512 512 512 512

Password length 32 32 32 32 32 32

Authorization user levels 15 15 15 15 15 15

ACE 256 512 512 512 512 512

Number of logged inusers

20 20 20 20 20 20

IP Routing

Max static route entries 32 32 128 32 32 32

Max HW routing tableentries

No HWroutingtable

No HWroutingtable

4000 1000 No HWroutingtable

3072



3. System RequirementsThe following tables lists the port system requirements supported by the SMBStaX software.Table 3-1. Port System Requirements

Feature SparX-III

and

Caracal

VSC7423

VSC7424

VSC7425

VSC7426

VSC7427

VSC7428

VSC7429

SparX-III

and

Serval-1

VSC7414

VSC7416

VSC7418

SparX-IV

and

Jaguar-2

VSC7438

VSC7442

VSC7444

VSC7448

VSC7449

VSC7464

VSC7468

SparX-IV

and

Serval-T

VSC7410

VSC7415

VSC7430

VSC7435

VSC7436

VSC7437

VSC7440

Ocelot

VSC7513

VSC7514

SparX-5

VSC7546VSC7549

VSC7552

VSC7556

VSC7558

LEDs per port 1 1 1 1 1 1

SFP+/SFP SFP auto-detection

BothSFP/SFP+auto-detection

SFP auto-detection

BothSFP/SFP+supported

BothSFP/SFP+supported

Both SFP/SFP+ supported

Speed capability per10/100M and Gigabitport

Supported Supported Supported Supported Supported Supported

Duplex capability per10/100M

Half/full Half/full Half/full Half/full Half/full Half/full

Auto MDI/MDIX Supported Supported Supported Supported Supported Supported

Port packet forwardingrate

1488000 pps(1000 Mbpswith 64bytes)148800 pps(100 Mbps)14880 pps(10 Mbps)

14880000pps (10Gbps)1488000 pps(1000 Mbpswith 64bytes)148800 pps(100 Mbps)14880 pps(10 Mbps)

14880000pps (10Gbps)1488000 pps(1000 Mbpswith 64 bytes)148800 pps(100 Mbps)14880 pps(10 Mbps)

14880000pps (10Gbps)1488000 pps(1000 Mbpswith 64bytes)148800 pps(100 Mbps)14880 pps(10 Mbps)

14880000pps (10Gbps)1488000pps (1000Mbps with64 bytes)148800pps (100Mbps)14880pps (10Mbps)

14880000 pps(10 Gbps)1488000 pps(1000 Mbpswith 64 bytes)148800 pps(100 Mbps)14880 pps (10Mbps)

RJ45 connectors Supported Supported Supported Supported Supported Supported

Fiber slots Supported Supported Supported Supported Supported Supported

The following tables lists the hardware system requirements supported by the SMBStaX software.

VSC6816System Requirements


Table 3-2. Hardware System Requirements

Requirement Support

CPU memory type and size Supported by hardware

EMC/safety requirement Supported by hardware

Forwarding architecture Supported by hardware

MAC address aging Supported by hardware

MAC address entries Supported by hardware

MAC buffer memory type and size Supported by hardware

Management LED Supported by hardware

Performance requirement Supported by hardware

Power LED Supported by hardware

Reset button Supported by hardware

Switch fabric capacity Supported by hardware

System DDR SDRAM Supported by hardware

System LED Supported by hardware

VSC6816System Requirements


4. Port and System CapabilitiesThe following sections describe the port and system capabilities supported by the SMBStaX software.

4.1 Port CapabilityThe ports are equipped with the following capabilities.

• All copper ports can be configured as full-duplex or half-duplex.• Copper ports operating at 10/100 Mbps support auto-sensing and auto-negotiation.• Full-duplex, auto-sensing, and auto-negotiation are supported on 1000 Mbps ports.• Full-duplex flow control is supported according to the IEEE 802.3x standard.• Half-duplex flow control is supported using collision-based backpressure.• LEDs for all the ports are driven by the SGPIO and shift registers.• Different port-based configurations are supported on all available ports. For more information, see 1. Supported

Features.

4.2 System CapabilityThe 6- to 52-port turnkey switch platform model switches can be supported using the SMBStaX software with wirespeed layer 2 Gigabit/Fast Ethernet switches, with an option to additionally support the PoE functionality with partnervendors.

The turnkey switch software runs on Linux. The following system-wide operations are supported:

• Store-and-forward forwarding architecture.• Configurable MAC address aging support (300 seconds default timeout value).• Port packet-forwarding rates of 1488095 pps (1000 Mbps), 148810 pps (100 Mbps), and 14880 pps (10 Mbps).• 128-MB system DDR SDRAM is recommended for a typical 24- to 48-port switch.• 16-MB flash size is recommended for a typical 24- to 48-port switch.• NOR-only, flash-based hardware designs are supported. NOR flash size of 64 MB is supported.

VSC6816Port and System Capabilities


5. Firmware UpgradeThe SMBStaX firmware, which controls the switch, can be updated using one of the following methods. The turnkeyswitch software runs on Linux. The following system-wide operations are supported:

• Web, using the HTTP protocol• CLI, using the TFTP client on the switch

The software image selection information includes the following:• Image—the file name of the firmware image• Version—the version of the firmware image• Date—the date when the firmware was produced

After the software image is uploaded from the web interface, a web page announces that the firmware update isinitiated. After about a minute, the firmware is updated and the switch restarts. While the firmware is being updated,web access appears to be defunct. The front LED flashes green/off with a frequency of 10 Hz while the firmwareupdate is in progress.

Note: Do not restart or power off the device at this time or the switch may fail to function.

VSC6816Firmware Upgrade


6. Port ControlThe following sections describe the port control features supported by the SMBStaX software.

6.1 NPI PortThe SMBStaX software supports the NPI port to manage the switch core. Any front port can be configured as an NPIport through which frames can be injected from and extracted to an external CPU.

6.2 PCIeThe PCIe interface allows a back-to-back connection with an external CPU. The external CPU has read/write accessto device registers and can burst frame-data in (injection) and out (extraction) through memory-mapped injection/extraction registers.

6.3 SFP DetectionThe SMBStaX software detects SFP at run time.

6.4 VeriPHY SupportVeriPHY is supported on the SMBStaX software for running cable diagnostics to find cable shorts/opens and todetermine cable length.

6.5 PoE/PoE+ SupportThe SMBStaX software provides PoE/PoE+ support to comply with the IEEE 802.3at and IEEE 802.3af standards forenabling the supply of up to 30 W per port and up to the total power budget.

6.6 POE/POE+ with LLDPThe SMBStaX software allows automatic power configuration if the link partner supports PoE. When LLDP isenabled, the information about the power usage of the PD is available, and then the switch can comply with or ignorethis information.

VSC6816Port Control


7. Quality of Services (QoS)The following sections describe the rich QoS features supported by the SMBStaX software.

7.1 Port PolicersThe QoS ingress port policers are configurable per port and are disabled by default. The software allows disable/enable flow control on the port policer. Flow control is disabled by default. If flow control is enabled and the port is inflow control mode, then pause frames are sent instead of discarding frames.

7.2 Scheduling and ShapingEach egress port implements a scheduler that controls eight queues, one queue (priority) per QoS class. Thescheduler mode can be set to strict priority or weighted (modified-DWRR). Strict priority is selected by default. It ispossible to specify the weight for each of the queues (0–5).

Each egress port also implements a port shaper and a shaper per queue. The software allows disabling/enabling theport and queue shaper as part of egress shaping. The port shaper and queue shaper are disabled by default.

It is possible to specify the maximum bit rate in kbps or mbps The use of excess bandwidth for a queue isconfigurable and is disabled by default.

The software also has the QoS leaky bucket egress shapers support per queue (0–7) as well as per port.

7.3 QoS Control List (QCL) ConfigurationQoS classification based on basic classification can be overruled by an intelligent classifier called QCL.

The QCL consists of QCE entries where each entry is configured with keys and actions. The keys specify which partof the frames must be matched and the actions specify the applied classification parameters.

When a frame is received on a port, the list of QCEs is searched for a match. If the frame matches the configuredkeys, the actions are applied and the search is terminated.

The QCL configuration is a table of QCEs containing QoS control entries that classify to a specific QoS class onspecific traffic objects. A QoS class can be associated with a particular QCE ID.

7.4 Weighted Random Early Detection (WRED)While the random early detection (RED) settings are configurable for queues 0–5, WRED is configurable to eitherdisable/enable, and is disabled by default.

The minimum and maximum percentage of the queue fill level or drop probability can be configured before WREDstarts discarding frames.

By specifying a different RED configuration for the queues (QoS classes), it is possible to obtain the WRED operationbetween queues.

7.5 Tag RemarkingTag remarking determines how an egress frame is edited before transmission. This includes the remarking of PCPand DEI values in tagged frames.

When adding a VLAN tag, the software allows specifying a mode where the PCP and DEI values are taken fromClassified, Mapped, or Default. Classified is the default.

The QoS class DEI, DP Level to PCP, can also be mapped for QoS egress tag remarking per port when theclassification is set to Mapped.

VSC6816Quality of Services (QoS)


7.6 Ingress Port ClassificationClassification is the first step for implementing QoS. There is a one-to-one mapping between QoS class, queue, andpriority. The QoS class is represented by numbers; higher numbers correspond to higher priority.

The features supported are as follows:

• Port default priority (QoS class)• Port default priority (DP level)• Port default PCP• Port default DEI• DSCP mapping to QoS class and DP level• DSCP classification (DiffServ)• Advanced QoS classification

7.7 Queue PolicersThe queue policers are configurable per queue and are disabled by default.

7.8 DiffServ (RFC2474) RemarkingThe SMBStaX software allows disabling/enabling port DSCP remarking, which is disabled by default. Port DSCPremarking is possible for both IPv4 and IPv6.

In addition to the ingress DSCP remarking done by the analyzer, the rewriter supports egress DSCP remarking of IP(IPv4 and IPv6) frames where the actual change is made to the DSCP field in frame.

The remarking can be configured as enable/disable per egress port. It is also possible to enable/disable DSCPremapping on the egress port and to use the translated DSCP value for DSCP remarking.

DSCP remapping is disabled by default. If DSCP remarking is enabled, the new DSCP value in a transmitted frame iseither from the analyzer (basic classification or advanced classification based on TCAM), or from the DSCPremapped on egress. The following configuration options are available if DSCP remapping is enabled.

• Get the DSCP value from the analyzer (ingress classification) and always remap based on global remap table.This is done independently of the value of the drop precedence level.

• Get DSCP value from the analyzer and remap based on drop precedence level and remap table.

DSCP remarking is not possible for frames where PTP time stamps are also generated. It is automatically disabled insuch cases. It is possible to configure per DSCP (0–63) value for each QoS class and set the DPL. The per DSCPvalue parameters are configurable for DSCP translation. The software allows mapping QoS class and DPL to DSCPvalue on the SMBStaX software.

VSC6816Quality of Services (QoS)


8. L2 SwitchingThe following sections describe the rich L2 switching features supported by the SMBStaX software.

8.1 Virtual LANThe SMBStaX software supports the IEEE 802.1Q standard virtual LAN (VLAN). The default configuration is asfollows.

• All ports are VLAN-aware.• All ports are members of VLAN 1.• The switch management interface is on VLAN 1. All ports have a Port VLAN ID (PVID) of 1.• A port can be configured to one of the following three modes.

– Access– Trunk– Hybrid

• By default, all ports are in Access mode and are normally used to connect to end stations. Access ports havethe following characteristics:

– Member of exactly one VLAN, the Port VLAN (Access VLAN), which by default is 1.– Accepts untagged and C-tagged frames.– Discards all frames that are not classified to the Access VLAN.– On egress all frames classified to the Access VLAN are transmitted untagged. Others (dynamically added

VLANs) are transmitted tagged.• The PVID is set to 1 by default.• Ingress filtering is always enabled.

Trunk ports can carry traffic on multiple VLANs simultaneously, and are normally used to connect to other switches.Trunk ports have the following characteristics.

• By default, a trunk port is a member of all VLANs (1–4095). This may be limited by the use of allowed VLANs.• If frames are classified to a VLAN that the port is not a member of, they are discarded.• By default, all frames classified to the Port VLAN (also known as Native VLAN) get tagged on egress. Frames

classified to the Port VLAN do not get C-tagged on egress.• Egress tagging can be changed to tag all frames, in which case only tagged frames are accepted on ingress.

Hybrid ports resemble trunk ports in many ways, but provide the following additional port configuration features.

• Can be configured to be VLAN tag unaware, C-tag aware, S-tag aware, or S-custom-tag aware.• Ingress filtering can be controlled.• Ingress acceptance of frames and configuration of egress tagging can be configured independently.

8.2 Voice VLANVoice VLAN is configured specially for voice traffic. Adding the ports with voice devices attached to VLAN to performQoS-related configuration for voice data ensures the transmission priority of voice traffic and voice quality. Individualoptions allow the port to participate in a Voice VLAN using the port security feature. A configurable port discoveryprotocol will also be available to detect voice devices attached to port using the Port Discovery Protocol. Thisdiscovery can be done either based on an Organizationally Unique Identifier (OUI) or Link Layer Discovery Protocol(LLDP) or both.

8.2.1 Private VLAN, Port IsolationIn a private VLAN, communication between isolated ports in that private VLAN is not permitted.

Private VLANs are based on the source port mask, and there are no connections to VLANs. This means that VLANIDs and private VLAN IDs can be identical.

VSC6816L2 Switching


8.2.2 Auto MAC Address Learning/AgingLearning is done automatically as soon as a frame with unknown SMAC is received. Dynamic entries are removedfrom the MAC table after a configured aging time (in seconds), if frames with learned MAC address are not receivedwithin aging period.

8.2.3 MAC Addresses–StaticStatically-added MAC entries are not subjected to aging.

8.2.4 MAC-Based, Protocol-Based, and IP Subnet-Based VLANA MAC-based VLAN enables mapping a specific MAC address to a specific VLAN.

A protocol-based VLAN enables mapping to a VLAN whose frame type may be one of the following:

• Ethernet—valid values for etype ranges from 0x0600–0xffff.• SNAP—valid value in this case also is comprised of two sub-values.

• Organizationally Unique Identifier (OUI).

– Protocol ID (PID)—if the OUI is hexadecimal 000000, the PID is the Ethernet type (EtherType) field valuefor the protocol running on top of SNAP. If the OUI is an OUI for a particular organization, the PID is a valueassigned by that organization to the protocol running on top of SNAP.

• LLC—Valid value in this case is comprised of two sub-values:

– DSAP—1-byte long string (0x00–0xff)– SSAP—1-byte long string (0x00–0xff)

The precedence of these VLANs is that the MAC-based VLAN is preferred over the protocol-based VLAN, andprotocol-based VLAN is preferred over port-based VLAN.

8.3 Generic VLAN Registration Protocol (GVRP)GVRP is a registration method for VLANs. Though this has been superseded by MVRP as described in IEEE802.1Q-2011, it is still of interest due to legacy systems that can interoperate.

GVRP is a method of dynamically telling a bridge port that there are devices for a particular VLAN on that port. A hostcan announce (register) that it wants to be part of a particular VLAN. It can de-register when it does not want to bepart of a certain VLAN anymore. It then becomes the responsibility of GVRP to propagate this information in thenetwork, so that a given VLAN gets proper connectivity.

8.4 Industrial Private VLANsThis feature is widely known as private VLANs (PVLAN). VLANs limit broadcasts to specified users. PVLANs splitsthe broadcast domain into multiple isolated broadcast sub-domains and puts secondary VLANs inside a primaryVLAN.

PVLANs restrict traffic flows through their member switch ports (private ports) so that these ports communicate onlywith a specified uplink trunk port or with specified ports within the same VLAN. The uplink trunk port is usuallyconnected to a router, firewall, server, or provider network. Each PVLAN typically contains many private ports thatcommunicate only with a single uplink, thereby preventing the ports from communicating with each other.

The following terms are used to describe the Private VLAN feature.

• PVLAN domain—a VLAN domain partitioned into a number of sub-domains. Inside the domain, a number ofprimary and secondary VLANs are used. Only the primary VLANs are known outside the PVLAN domain.

• Primary VLAN—a VLAN used inside and outside a PVLAN domain. A primary VLAN carries traffic frompromiscuous ports to isolated ports, and from community ports to other promiscuous ports.

• Secondary VLAN—a VLAN used inside a PVLAN domain only.• Isolated VLAN—a secondary VLAN that carries traffic from isolated ports to promiscuous ports.• Community VLAN—a secondary VLAN that carries traffic from community ports to promiscuous ports and other

community ports.

VSC6816L2 Switching


• Isolated port—a port that receives untagged frames and classifies these to an isolated VLAN.• Community port—a port that receives untagged frames and classifies these to a community VLAN.• Promiscuous port—a port that receives frames in the primary VLAN.• Standard trunk port—a port that carries primary and secondary VLANs using tags.• Promiscuous PVLAN trunk port—a port that receives frames tagged with the primary VLAN ID. The port sends

frames from secondary VLANs, but translates these to the primary VLAN ID and pushes this into the tag.• Isolated PVLAN trunk port—a port, which receives frames tagged with the isolated VLAN ID. The port sends

frames from the isolated VLAN. The port also sends frames from the primary VLAN, but translates this into theisolated VLAN ID and pushes it into the tag.

8.5 Multiple Registration Protocol (MRP)The MRP, that replaced Generic Attribute Registration Protocol (GARP), is a generic registration framework definedby the IEEE 802.1ak amendment to the IEEE 802.1Q standard. MRP allows bridges, switches or other similardevices to be able to register and unregister attribute values, such as VLAN identifiers and multi-cast groupmembership across a large LAN.

8.6 Multiple VLAN Registration Protocol (MVRP)The MVRP, that replaced GVRP, is a standards-based layer 2 network protocol, for automatic configuration of VLANinformation on switches. It was defined in the IEEE 802.1ak amendment to 802.1Q- 2005.

8.7 IEEE 802.3ad Link AggregationA link aggregation is a collection of one or more full duplex (FDX) Ethernet links. These links when combinedtogether form a Link Aggregation Group (LAG), such that the networking device can treat it as if it were a single link.The traffic distribution is based on a hash calculation of fields in the frame:

• Source MAC address—can be used to calculate the destination port for the frame. By default, the source MACaddress is enabled.

• Destination MAC address—can be used to calculate the destination port for the frame. By default, thedestination MAC address is disabled.

• IP address—can be used to calculate the destination port for the frame. By default, the IP address is enabled.• TCP/UDP port number—can be used to calculate the destination port for the frame. By default, the TCP/UDP

port number is enabled.

An aggregation can be configured statically or dynamically through the Link Aggregation Control Protocol (LACP).

8.7.1 StaticStatic aggregations can be configured through the CLI or the web interface. A static LAG interface does not require apartner system to be able to aggregate its member ports. In Static mode, the member ports do not transmitLACPDUs.

8.7.2 Link Aggregation Control Protocol (LACP)The LACP exchanges LACPDUs with an LACP partner and forms an aggregation automatically. The LACP can beenabled or disabled on the switch port. The LACP will form an aggregation when two or more ports are connected tothe same partner.

The key value can be configured to a user-defined value or set to auto to calculate based on the link speed inaccordance with IEEE 802.3ad standard.

The role for the LACP port configuration can be selected as either active to transmit LACP packets each second, orpassive to wait for an LACP packet from a partner.

VSC6816L2 Switching


8.8 Bridge Protocol Data Unit (BPDU) Guard, Restricted Role, and Error DisableRecoveryThis is provided as part of the Spanning Tree Protocol (STP) configuration settings. The BPDU guard is a control thatspecifies whether a port explicitly configured as edge will disable itself upon reception of a BPDU. The port will enterthe error-disabled state, and will be removed from active topology.

The Common and Internal Spanning Tree (CIST) port setting for the BPDU guard is not subject to edge statusdependency. For a restricted role, CIST port setting may also be seen as a security measure.

8.8.1 BPDU FilteringBPDU filtering is a control that specifies whether a port explicitly configured as edge will transmit and receive BPDUs.This is also provided as part of the STP configuration settings.

8.9 Error Disable RecoveryThe error disable recovery comes under the BPDU guard, just change the heading as Bridge Protocol Data Unit(BPDU) Guard and error disable recovery.

8.10 IGMP and Multicast Listener Discovery (MLD)The IGMP snooping or MLD snooping mode can be configured system-wide including unregistered IPMC flooding,Source-Specific Multicast (SSM) range, proxy, and leave proxy. Per VLAN configuration is also supported forconfiguring IGMP snooping or MLD snooping. The maximum IGMP interfaces refer to the maximum number of IPinterfaces.

8.11 Filtering (IGMP Snooping and MLD Snooping)The IGMP snooping or MLD snooping filtering groups for a specific IPv4 or IPv6 multicast address can be createdand viewed per port.

8.12 DHCP SnoopingDHCP snooping is used to block intruders on the untrusted ports of the switch device when it tries to intervene byinjecting a bogus DHCP (for IPv4) reply packet to a legitimate conversation between the DHCP (IPv4) client andserver.

DHCP snooping is a series of techniques applied to ensure the security of an existing DHCP infrastructure. WhenDHCP servers allocate IP addresses to clients on the LAN, DHCP snooping can be configured on LAN switches toharden the security on the LAN to allow only clients with specific IP/MAC addresses to have access to the network.

DHCP snooping ensures IP integrity on a layer 2 switched domain by allowing only a white-list of IP addresses toaccess the network. The white-list is configured at the switch port level, and the DHCP server manages accesscontrol.

Only specific IP addresses with specific MAC addresses on specific ports may access the IP network.

DHCP snooping also stops attackers from adding their own DHCP servers to the network. An attacker—controlledDHCP server could cause malfunction of the network or even control it. The port role can be set as Trusted orUntrusted in order to protect it.

8.13 Multicast VLAN Registration (MVR)System-wide configuration parameters are available for configuring MVR. Up to four MVR VLANs can be created,each of which manages the channel by using an IPMC profile. The immediate leave configuration is configurable andviewable per port.

VSC6816L2 Switching


8.14 MAC Table ConfigurationMAC learning configuration can be configured per port.

• Auto—learning is done automatically as soon as a frame with unknown Static MAC (SMAC) is received.• Disable—no learning is done.• Secure—only SMAC entries are learned, all other frames are dropped.

The static entries can be configured in the MAC table for forwarding. The user can enable/disable MAC learning perVLAN. VLAN learning is enabled by default.

MAC aging is configurable to age out the learned entries.

MAC learning cannot be administered on each individual aggregation group.

8.15 Mirroring (SPAN/VSPAN and RSPAN)The SMBStaX software allows selected traffic to be copied, or mirrored, to a mirror port where a frame analyzer canbe attached to analyze the frame flow. By default, mirror monitors all traffic, including multicast and bridge PDUs.

The software will support many-to-one port mirroring. The destination port is located on the local switch in the case ofMirror. The switch can support VLAN-based mirroring.

Note: The mirroring session will have either ports or VLANs as sources, but not both.

8.16 RMirrorThe RMirror is an extension to mirror that allows for mirroring traffic from one switch to a port on another switch. TheRMirror is more flexible than Mirror. When a host wants to send traffic to a remote Host connected to a differentswitch, the first switch will copy the traffic to a dedicated RMirror VLAN, which will cause the traffic to be flooded toports that are members of that VLAN. The administrator can use a sniffer to analyze network traffic on remoteswitches.

The RMirror does not support BPDU monitoring, but rather supports IGMP packet monitoring when IGMP snooping isdisabled on the RMirror VLAN.

All hardware error packets are discarded at the source port, so they are not copied to the destination port.

8.17 Flow Mirroring for ACManagement can set and get ACE mirror function. When the function is enabled, the frame is mirrored if the ACE ishit. The default value is disabled.

8.18 Spanning TreeThe SMBStaX software supports the Spanning Tree versions IEEE 802.1 Spanning Tree Protocol (STP), 802.1wRapid STP (RSTP), and 802.1s MSTP. The desired version is configurable and the MSTP is selected by default.

The RSTP portion of the module conforms to IEEE 802.1D-2004 and the MSTP portion of the module conforms toIEEE 802.1Q-2005.

IEEE 802.1s supports 16 instances.

The STP MSTI and CIST port configurations are allowed per physical port or aggregated port, as also STP MSTIbridge instance mapping and priority configurations.

Port Error Recovery is supported to control whether a port in the error-disabled state automatically will be enabledafter a certain time.

VSC6816L2 Switching


8.19 Loop GuardLoops inside a network are very costly because they consume resources and lower network performance. Detectingloops manually can become cumbersome and tasking. Loop protection can be enabled or disabled on a port, orsystem-wide.

If loop protection is enabled, it sends packets to a reserved layer 2 multicast destination address on all the ports onwhich the feature is enabled. Transmission of the packet can be disabled on selected ports, even when loopprotection is on. If a packet is received by the switch with matching multicast destination address, the source MAC inthe packet is compared with its own MAC. If the MAC does not match, the packet is forwarded to all ports that aremember of the same VLAN, except to the port from which it came in, treating it similar to a data packet. If the featureis enabled and source MAC matches its own MAC, the port on which the packet is received will be shut down,logged, or both actions taken depending upon the action configured.

If the feature is disabled, the packet will be dropped silently. The following matching criteria are used.

• DA= determined on customer requirement, AND• SA= first 5 bytes of switch SA, AND• Ether Type= 9003, AND

Loop protection is disabled by default, with an option to either enable globally on all the ports or individually on eachport of the switch including the trunks (static only). Loop protection will co-exist with the (M)STP protocol beingenabled on the same physical ports. Loop protection will not affect the ports that (M)STP has put in non-forwardingstate.

The following sections describe the rich L3 switching features supported by the SMBStaX software.

VSC6816L2 Switching


9. L3 SwitchingThe following sections describe the rich L3 switching features supported by the SMBStaX software.

9.1 DHCP RelayThe following table lists the parameters available for configuring the DHCP relay.

Table 9-1. DHCP Relay Configuration Parameters

Parameter Allowed Range Default

Relay mode Enabled/disabled Disabled

Relay server address IP address None

Relay information mode Enabled/disabled Disabled

Relay information policy Replace

Keep

Drop

Keep

The relay information mode enables or disables the DHCP option 82 operation. When DHCP relay information modeoperation is enabled, the agent inserts specific information (option 82) into a DHCP message when forwarding toDHCP server and removes it from a DHCP message when transferring to DHCP client. The first four charactersrepresent the VLAN ID, the fifth and sixth characters are the module ID (in standalone device it always equals 0, instackable device it means switch ID), and the last two characters are the port number.

9.2 Universal Plug and Play (UPnP)The addressing, discovery, and description parts of UPnP-client protocol are implemented in the device. It is used tohelp the network administrator in managing the network. The purpose of UPnP in the device is similar to LLDP.However, UPnP is a layer 4 protocol that allows UPnP-clients to be located on a different subnet with UPnP-controlpoints.

In the implementation, the switch sends Simple Service Discovery Protocol (SSDP) messages periodically at theinterval one-half of the advertising duration minus 30 seconds.

When the UPnP mode is enabled, two ACEs are added automatically to trap UPnP related packets to CPU. TheACEs are automatically removed when the mode is disabled.

9.3 L3 RoutingL3 routing is to select path and forward traffic to the nexthop based on the routing table. L3 routing includes hardwarerouting and software routing. Software routing is supported by the SMBStaX software and hardware routing issupported by the VCAP LPM table. If the switch has no LPM table then it only uses software routing.

Only manually configured routing entries are supported, that is, static routes.

VSC6816L3 Switching


10. SynchronizationThe following section describes the synchronization feature supported by the SMBStaX software.

10.1 Network Time Protocol (NTP)NTP is widely used to synchronize system clocks among a set of distributed time servers and clients. NTP is disabledby default. The implemented NTP version is 4.

The NTP IPv4 or IPv6 address can be configured and a maximum of five servers are supported. Daylight saving timecan also be supported to automatically adjust the Time of

Documents

VSC6816-4.1 SMBStaXww1.microchip.com/downloads/en/DeviceDoc/VSC6816_SMBStaX_S… · VSC6816 SMBStaX Software Product Specification Product Overview The SMBStaX turnkey software package