TP-LINK Omada TL-SG2008P - Switch

Omada TL-SG2008P - Switch TP-LINK - Free user manual and instructions

Find the device manual for free Omada TL-SG2008P TP-LINK in PDF.

📄 999 pages English EN Download 💬 AI Question
Notice TP-LINK Omada TL-SG2008P - page 33
Pick your language and provide your email: we'll send you a specifically translated version.

User questions about Omada TL-SG2008P TP-LINK

0 question about this device. Answer the ones you know or ask your own.

Ask a new question about this device

The email remains private: it is only used to notify you if someone responds to your question.

No questions yet. Be the first to ask one.

Download the instructions for your Switch in PDF format for free! Find your manual Omada TL-SG2008P - TP-LINK and take your electronic device back in hand. On this page are published all the documents necessary for the use of your device. Omada TL-SG2008P by TP-LINK.

USER MANUAL Omada TL-SG2008P TP-LINK

Accessing the Switch

Determine the Management Method ....4

Web Interface Access....5

Login....5

Save the Configuration File....6

Disable the Web Server 7

Configure the Switch's IP Address and Default Gateway 8

Command Line Interface Access 10

Console Login (only for switch with console port)....10

Telnet Login 12

SSH Login....13

Disable Telnet login....17

Disable SSH login 18

Copy running-config startup-config....18

Change the Switch's IP Address and Default Gateway....19

Managing System

System 21

Overview....21

Supported Features....21

System Info Configurations 23

Using the GUI 23

Viewing the System Summary....23

Configuring the Device Description....27

Configuring the System Time 27

Configuring the Daylight Saving Time....28

Configuring LED (Only for Certain Devices)....29

Using the CLI 30

Viewing the System Summary....30

Configuring the Device Description....31

Configuring the System Time 32

Configuring the Daylight Saving Time....35

Configuring LED (Only for Certain Devices) 37

User Management Configurations.... 38

Using the GUI 38

Creating Accounts 38

Configuring Enable Password....39

Using the CLI 40

Creating Accounts 40

Configuring Enable Password....41

System Tools Configurations 44

Using the GUI 44

Configuring the Boot File 44

Restoring the Configuration of the Switch 46

Backing up the Configuration File....46

Upgrading the Firmware....47

Configuring DHCP Auto Install (Only for Certain Devices)....47

Rebooting the switch....49

Reseting the Switch....50

Using the CLI....50

Configuring the Boot File....50

Restoring the Configuration of the Switch 52

Backing up the Configuration File....52

Upgrading the Firmware....53

Configuring DHCP Auto Install (Only for Certain Devices) 53

Rebooting the Switch 55

Reseting the Switch....57

EEE Configuration.... 58

Using the CLI....58

PoE Configurations (Only for Certain Devices) 60

Using the GUI 61

Configuring the PoE Parameters Manually....61

Configuring the PoE Parameters Using the Profile....64

Using the CLI....67

Configuring the PoE Parameters Manually....67

Configuring the PoE Parameters Using the Profile....69

SDM Template Configuration....72

Using the GUI 72

Using the CLI....73

Time Range Configuration....75

Using the GUI 75

Adding Time Range Entries....75

Configuring Holiday 77

Using the CLI....78

Adding Time Range Entries....78

Configuring Holiday 79

Controller Settings (Only for Certain Devices) 81

Using the GUI 81

Enabling Cloud-Based Controller Management....81

Configuring Controller Inform URL....82

Using the CLI....82

Enabling Cloud-Based Controller Management....82

Configuring Controller Inform URL....82

Example for PoE Configurations....84

Network Requirements....84

Configuring Scheme....84

Using the GUI 84

Using the CLI 87

Appendix: Default Parameters....89

Managing Physical Interfaces

Physical Interface 93

Overview....93

Supported Features....93

Basic Parameters Configurations....94

Using the GUI 94

Using the CLI 95

Port Isolation Configurations....98

Using the GUI....98

Using the CLI....99

Loopback Detection Configuration....101

Using the GUI 101

Using the CLI....103

Configuration Examples....105

Example for Port Isolation....105

Network Requirements....105

Configuration Scheme....105

Using the GUI....105

Using the CLI 107

Example for Loopback Detection....108

Network Requirements....108

Configuration Scheme....108

Using the GUI....109

Using the CLI 110

Appendix: Default Parameters....111

Configuring LAG

LAG....113

Overview....113

Supported Features....113

LAG Configuration....114

Using the GUI 115

Configuring Load-balancing Algorithm....115

Configuring Static LAG or LACP....116

Using the CLI 118

Configuring Load-balancing Algorithm....118

Configuring Static LAG or LACP....119

Configuration Examples....123

Example for Static LAG 123

Network Requirements....123

Configuration Scheme....123

Using the GUI....123

Using the CLI 124

Example for LACP 125

Network Requirements....125

Configuration Scheme....125

Using the GUI....126

Using the CLI 127

Appendix: Default Parameters....130

Configuring DDM (Only for Certain Devices)

Overview 132

DDM Configuration....133

Using the GUI 133

Configuring DDM Globally....133

Configuring the Threshold....134

Viewing DDM Status....139

Using the CLI....139

Configuring DDM Globally....139

Configuring DDM Shutdown....140

Configuring the Threshold....141

Viewing DDM Configuration....147

Viewing DDM Status....148

Appendix: Default Parameters....149

Managing MAC Address Table

MAC Address Table....151

Overview....151

Supported Features....151

MAC Address Configurations 153

Using the GUI 153

Adding Static MAC Address Entries 153

Modifying the Aging Time of Dynamic Address Entries....155

Adding MAC Filtering Address Entries....156

Viewing Address Table Entries....156

Using the CLI....157

Adding Static MAC Address Entries 157

Modifying the Aging Time of Dynamic Address Entries....158

Adding MAC Filtering Address Entries....159

Security Configurations 161

Using the GUI....162

Configuring MAC Notification Traps 162

Limiting the Number of MAC Addresses Learned in VLANs....163

Using the CLI 165

Configuring MAC Notification Traps 165

Limiting the Number of MAC Addresses in VLANs 167

Example for Security Configurations 169

Network Requirements....169

Configuration Scheme 169

Using the GUI 170

Using the CLI 171

Appendix: Default Parameters....172

Configuring 802.1Q VLAN

Overview 174

802.1Q VLAN Configuration....175

Using the GUI 176

Configuring the VLAN....176

Configuring Port Parameters for 802.1Q VLAN 177

Using the CLI....178

Creating a VLAN 178

Adding the Port to the Specified VLAN....179

Configuring the Port....180

Configuration Example 182

Network Requirements....182

Configuration Scheme 182

Network Topology....183

Using the GUI 183

Using the CLI....186

Appendix: Default Parameters ....189

Configuring MAC VLAN

Overview 191

MAC VLAN Configuration....192

Using the GUI 192

Configuring 802.1Q VLAN 192

Binding the MAC Address to the VLAN....192

Enabling MAC VLAN for the Port....193

Using the CLI....194

Configuring 802.1Q VLAN....194

Binding the MAC Address to the VLAN....194

Enabling MAC VLAN for the Port....195

Configuration Example 196

Network Requirements....196

Configuration Scheme 196

Using the GUI 197

Using the CLI 202

Appendix: Default Parameters....206

Configuring Protocol VLAN

Overview 208

Protocol VLAN Configuration....209

Using the GUI 209

Configuring 802.1Q VLAN 209

Creating Protocol Template 210

Configuring Protocol VLAN....211

Using the CLI 212

Configuring 802.1Q VLAN 212

Creating a Protocol Template....212

Configuring Protocol VLAN....213

Configuration Example 216

Network Requirements....216

Configuration Scheme 216

Using the GUI 218

Using the CLI 224

Appendix: Default Parameters....228

Configuring VLAN-VPN (Only for Certain Devices)

VLAN-VPN 230

Overview....230

Supported Features....231

Basic VLAN-VPN Configuration 232

Using the GUI 232

Configuring 802.1Q VLAN 232

Configuring Basic VLAN-VPN 233

Using the CLI 234

Configuring 802.1Q VLAN 234

Configuring Basic VLAN-VPN 234

Flexible VLAN-VPN Configuration....237

Using the GUI 237

Using the CLI 238

Configuration Examples....240

Example for Basic VLAN VPN 240

Network Requirements....240

Configuration Scheme....240

Using the GUI....241

Using the CLI 247

Example for Flexible VLAN VPN 251

Network Requirements....251

Configuration Scheme....251

Using the GUI....252

Using the CLI 259

Appendix: Default Parameters....262

Configuring GVRP

Overview 264

GVRP Configuration....265

Using the GUI 266

Using the CLI 267

Configuration Example 270

Network Requirements....270

Configuration Scheme 270

Using the GUI 271

Using the CLI 275

Appendix: Default Parameters....279

Configuring Private VLAN (Only for Certain Devices)

Overview 281

Private VLAN Configurations 283

Using the GUI 283

Using the CLI 284

Creating Private VLAN....284

Configuring the Up-link Port 286

Configuring the Down-link Port....288

Configuration Example 290

Network Requirements....290

Configuration Scheme 290

Network Topology....290

Using the GUI 291

Using the CLI 295

Appendix: Default Parameters....299

Configuring Layer 2 Multicast

Layer 2 Multicast....301

Overview 301

Supported Features....303

IGMP Snooping Configuration 304

Using the GUI 304

Configuring IGMP Snooping Globally 304

Configuring IGMP Snooping for VLANs 305

Configuring IGMP Snooping for Ports....309

Configuring Hosts to Statically Join a Group....309

Configuring IGMP Accounting and Authentication Features....310

Using the CLI 312

Configuring IGMP Snooping Globally 312

Configuring IGMP Snooping for VLANs 313

Configuring IGMP Snooping for Ports....318

Configuring Hosts to Statically Join a Group....319

Configuring IGMP Accounting and Authentication Features....320

MLD Snooping Configuration....324

Using the GUI 324

Configuring MLD Snooping Globally....324

Configuring MLD Snooping for VLANs....325

Configuring MLD Snooping for Ports 328

Configuring Hosts to Statically Join a Group 328

Using the CLI 329

Configuring MLD Snooping Globally....329

Configuring MLD Snooping for VLANs....330

Configuring MLD Snooping for Ports 335

Configuring Hosts to Statically Join a Group....336

MVR Configuration 338

Using the GUI 338

Configuring 802.1Q VLANs....338

Configuring MVR Globally....339

Adding Multicast Groups to MVR....340

Configuring MVR for the Port....341

(Optional) Adding Ports to MVR Groups Statically 342

Using the CLI 343

Configuring 802.1Q VLANs....343

Configuring MVR Globally....343

Configuring MVR for the Ports 345

Multicast Filtering Configuration....348

Using the GUI 348

Creating the Multicast Profile....348

Configure Multicast Filtering for Ports 350

Using the CLI 351

Creating the Multicast Profile....351

Binding the Profile to Ports....354

Viewing Multicast Snooping Information....358

Using the GUI 358

Viewing IPv4 Multicast Table 358

Viewing IPv4 Multicast Statistics on Each Port 359

Viewing IPv6 Multicast Table....360

Viewing IPv6 Multicast Statistics on Each Port....361

Using the CLI 362

Viewing IPv4 Multicast Snooping Information....362

Viewing IPv6 Multicast Snooping Configurations....363

Configuration Examples....364

Example for Configuring Basic IGMP Snooping....364

Network Requirements....364

Configuration Scheme....364

Using the GUI....365

Using the CLI 367

Example for Configuring MVR 369

Network Requirements 369

Network Topology....369

Configuration Scheme....370

Using the GUI....370

Using the CLI 373

Example for Configuring Unknown Multicast and Fast Leave....376

Network Requirement....376

Configuration Scheme....377

Using the GUI....377

Using the CLI 379

Example for Configuring Multicast Filtering....380

Network Requirements....380

Configuration Scheme....380

Network Topology....381

Using the GUI....381

Using the CLI 385

Appendix: Default Parameters ....388

Default Parameters for IGMP Snooping 388

Default Parameters for MLD Snooping....389

Default Parameters for MVR....390

Default Parameters for Multicast Filtering....390

Configuring Spanning Tree

Spanning Tree....392

Overview....392

Basic Concepts 392

STP/RSTP Concepts....392

MSTP Concepts 396

STP Security 397

STP/RSTP Configurations 400

Using the GUI 400

Configuring STP/RSTP Parameters on Ports....400

Configuring STP/RSTP Globally....402

Verifying the STP/RSTP Configurations....404

Using the CLI 406

Configuring STP/RSTP Parameters on Ports....406

Configuring Global STP/RSTP Parameters 408

Enabling STP/RSTP Globally....410

MSTP Configurations 412

Using the GUI 412

Configuring Parameters on Ports in CIST 412

Configuring the MSTP Region 415

Configuring MSTP Globally....419

Verifying the MSTP Configurations 421

Using the CLI 422

Configuring Parameters on Ports in CIST 422

Configuring the MSTP Region 425

Configuring Global MSTP Parameters....428

Enabling Spanning Tree Globally....430

STP Security Configurations....432

Using the GUI 432

Using the CLI 433

Configuring the STP Security....433

Configuration Example for MSTP 436

Network Requirements....436

Configuration Scheme 436

Using the GUI 437

Using the CLI 443

Appendix: Default Parameters....450

Configuring LLDP

LLDP 453

Overview 453

Supported Features....453

LLDP Configurations 454

Using the GUI 454

Configuring LLDP Globally 454

Configuring LLDP For the Port 456

Using the CLI 457

Global Config....457

Port Config....459

LLDP-MED Configurations....462

Using the GUI 462

Configuring LLDP Globally 462

Configuring LLDP-MED Globally 462

Configuring LLDP-MED for Ports....463

Using the CLI 465

Global Config....465

Port Config....466

Viewing LLDP Settings....469

Using GUI....469

Viewing LLDP Device Info 469

Viewing LLDP Statistics 473

Using CLI 474

Viewing LLDP-MED Settings 475

Using GUI....475

Using CLI 478

Configuration Example 479

Configuration Example for LLDP 479

Network Requirements......479

Network Topology....479

Configuration Scheme....479

Using the GUI....479

Using CLI....480

Example for LLDP-MED 486

Network Requirements....486

Configuration Scheme....486

Using the GUI....486

Using CLI....489

Appendix: Default Parameters....492

Configuring L2PT (Only for Certain Devices)

Overview 494

L2PT Configuration....496

Using the GUI 496

Using the CLI 497

Configuration Example 501

Network Requirements....501

Configuration Scheme 501

Using the GUI 501

Using the CLI....502

Appendix: Default Parameters....504

Configuring PPPoE ID Insertion (Only for Certain Devices)

Overview 506

PPPoE ID Insertion Configuration....507

Using the GUI 507

Using the CLI....508

Appendix: Default Parameters....511

Configuring Layer 3 Interfaces

Overview 513

Layer 3 Interface Configurations....514

Using the GUI 514

Creating an Layer 3 Interface....514

Configuring IPv4 Parameters of the Interface 516

Configuring IPv6 Parameters of the Interface 517

Viewing Detail Information of the Interface....520

Using the CLI 521

Creating an Layer 3 Interface....521

Configuring IPv4 Parameters of the Interface 523

Configuring IPv6 Parameters of the Interface 524

Configuration Example 527

Network Requirement 527

Configuration Scheme 527

Using the GUI 527

Using the CLI 528

Appendix: Default Parameters....530

Configuring Routing

Overview 532

IPv4 Static Routing Configuration....533

Using the GUI 533

Using the CLI 534

IPv6 Static Routing Configuration 535

Using the GUI 535

Using the CLI 535

Viewing Routing Table 537

Using the GUI 537

Viewing IPv4 Routing Table....537

Viewing IPv6 Routing Table....538

Using the CLI....538

Viewing IPv4 Routing Table....538

Viewing IPv6 Routing Table....539

Example for Static Routing....540

Network Requirements....540

Configuration Scheme 540

Using the GUI 540

Using the CLI 542

Configuring DHCP Service

DHCP 546

Overview....546

Supported Features....546

DHCP Server Configuration....551

Using the GUI 551

Enabling DHCP Server 551

Configuring DHCP Server Pool 553

Configuring Manual Binding....554

Using the CLI 555

Enabling DHCP Server 555

Configuring DHCP Server Pool 558

Configuring Manual Binding....561

DHCP Relay Configuration 564

Using the GUI 564

Enabling DHCP Relay and Configuring Option 82....564

Configuring DHCP Interface Relay 566

Configuring DHCP VLAN Relay 566

Using the CLI 568

Enabling DHCP Relay 568

(Optional) Configuring Option 82 ....569

Configuring DHCP Interface Relay 571

Configuring DHCP VLAN Relay 572

DHCP L2 Relay Configuration 575

Using the GUI 575

Enabling DHCP L2 Relay 575

Configuring Option 82 for Ports....576

Using the CLI 577

Enabling DHCP L2 Relay 577

Configuring Option 82 for Ports ....578

Configuration Examples....581

Example for DHCP Server....581

Network Requirements....581

Configuration Scheme....581

Using the GUI....581

Using the CLI 583

Example for DHCP Interface Relay 583

Network Requirements....583

Configuration Scheme....584

Using the GUI....585

Using the CLI 591

Example for DHCP VLAN Relay 593

Network Requirements....593

Configuration Scheme....594

Using the GUI....595

Using the CLI 598

Example for Option 82 in DHCP Relay....600

Network Requirements....600

Configuration Scheme....601

Configuring the DHCP Relay Switch....602

Configuring the DHCP Server 604

Example for DHCP L2 Relay 606

Network Requirements....606

Configuration Scheme....606

Configuring the DHCP Relay Switch....607

Configuring the DHCP Server 610

Appendix: Default Parameters....612

Configuring ARP

Overview 616

Supported Features....616

ARP Configurations....618

Using the GUI 618

Viewing the ARP Entries....618

Adding Static ARP Entries Manually....619

Configuring Gratuitous ARP 619

Configuring Proxy ARP 620

Configuring Local Proxy ARP 621

Using the CLI....622

Configuring the ARP Entry 622

Configuring the Gratuitous ARP 624

Configuring Proxy ARP 626

Appendix: Default Parameters....629

Configuring QoS

QoS....631

Overview....631

Supported Features....631

Class of Service Configuration....633

Using the GUI 634

Configuring Port Priority....634

Configuring 802.1p Priority 636

Configuring DSCP Priority....639

Specifying the Scheduler Settings 643

Using CLI 645

Configuring Port Priority....645

Configuring 802.1p Priority 648

Configuring DSCP Priority....651

Specifying the Scheduler Settings 657

Bandwidth Control Configuration....661

Using the GUI 661

Configuring Rate Limit....661

Configuring Storm Control 662

Using the CLI....664

Configuring Rate Limit....664

Configuring Storm Control 665

Voice VLAN Configuration 668

Using the GUI 668

Configuring OUI Addresses 668

Configuring Voice VLAN Globally 669

Adding Ports to Voice VLAN 670

Using the CLI 671

Auto VoIP Configuration 674

Using the GUI 674

Using the CLI 675

Configuration Examples....679

Example for Class of Service 679

Network Requirements....679

Configuration Scheme....679

Using the GUI....680

Using the CLI 682

Example for Voice VLAN 684

Network Requirements......684

Configuration Scheme....685

Using the GUI....685

Using the CLI 689

Example for Auto VoIP 692

Network Requirements....692

Configuration Scheme....693

Using the GUI....693

Using the CLI 698

Appendix: Default Parameters....703

Configuring Access Security

Access Security 708

Overview....708

Supported Features....708

Access Security Configurations....709

Using the GUI....709

Configuring the Access Control Feature....709

Configuring the HTTP Function 712

Configuring the HTTPS Function....714

Configuring the SSH Feature 717

Configuring the Telnet Function....718

Configuring the Serial Port Parameters....719

Using the CLI....719

Configuring the Access Control Feature....719

Configuring the HTTP Function 721

Configuring the HTTPS Function....723

Configuring the SSH Feature 726

Configuring the Telnet Function....728

Configuring the Serial Port Parameters....729

Appendix: Default Parameters....730

Configuring AAA

Overview 733

AAA Configuration....734

Using the GUI 735

Adding Servers....735

Configuring Server Groups....737

Configuring the Method List....738

Configuring the AAA Application List....739

Configuring Login Account and Enable Password 740

Using the CLI....741

Adding Servers....741

Configuring Server Groups....743

Configuring the Method List....744

Configuring the AAA Application List 745

Configuring Login Account and Enable Password 750

Configuration Example 752

Network Requirements....752

Configuration Scheme 752

Using the GUI 753

Using the CLI 755

Appendix: Default Parameters....758

Configuring 802.1x

Overview 761

802.1x Configuration....762

Using the GUI 762

Configuring the RADIUS Server 762

Configuring 802.1x Globally....765

Configuring 802.1x on Ports....766

View the Authenticator State 768

Using the CLI....769

Configuring the RADIUS Server....769

Configuring 802.1x Globally....771

Configuring 802.1x on Ports....773

Viewing Authenticator State....775

Configuration Example 777

Network Requirements....777

Configuration Scheme 777

Network Topology....777

Using the GUI 778

Using the CLI 780

Appendix: Default Parameters....783

Configuring Port Security

Overview 785

Port Security Configuration....786

Using the GUI 786

Using the CLI 787

Appendix: Default Parameters....790

Configuring ACL

Overview 792

ACL Configuration....793

Using the GUI 793

Configuring Time Range 793

Creating an ACL....793

Configuring ACL Rules....794

Configuring MAC ACL Rule....794

Configuring IP ACL Rule....798

Configuring Combined ACL Rule....802

Configuring the IPv6 ACL Rule....807

Configuring the Packet Content ACL Rule 812

Configuring ACL Binding....816

Using the CLI 818

Configuring Time Range 818

Configuring ACL 818

Configuring Policy....828

Configuring ACL Binding....830

Viewing ACL Counting 831

Configuration Example for ACL....832

Configuration Example for MAC ACL....832

Network Requirements 832

Configuration Scheme....832

Using the GUI....833

Using the CLI 839

Configuration Example for IP ACL....840

Network Requirements 840

Configuration Scheme....841

Using the GUI....841

Using the CLI 847

Configuration Example for Combined ACL....849

Network Requirements 849

Configuration Scheme....849

Using the GUI....850

Using the CLI 855

Appendix: Default Parameters....857

Configuring IPv4 IMPB

IPv4 IMPB 860

Overview 860

Supported Features 860

IP-MAC Binding Configuration....861

Using the GUI 861

Binding Entries Manually 861

Binding Entries via ARP Scanning....863

Binding Entries via DHCP Snooping....864

Viewing the Binding Entries 866

Using the CLI 867

Binding Entries Manually 867

Binding Entries via DHCP Snooping....869

Viewing Binding Entries 870

ARP Detection Configuration....871

Using the GUI 871

Adding IP-MAC Binding Entries 871

Enabling ARP Detection 871

Configuring ARP Detection on Ports 872

Viewing ARP Statistics....873

Using the CLI 874

Adding IP-MAC Binding Entries 874

Enabling ARP Detection 874

Configuring ARP Detection on Ports 875

Viewing ARP Statistics....877

IPv4 Source Guard Configuration....878

Using the GUI 878

Adding IP-MAC Binding Entries 878

Configuring IPv4 Source Guard 878

Using the CLI 879

Adding IP-MAC Binding Entries 879

Configuring IPv4 Source Guard 879

Configuration Examples....881

Example for ARP Detection 881

Network Requirements....881

Configuration Scheme....881

Using the GUI....882

Using the CLI 884

Example for IP Source Guard....886

Network Requirements 886

Configuration Scheme....886

Using the GUI....886

Using the CLI 888

Appendix: Default Parameters....890

Configuring IPv6 IMPB

IPv6 IMPB 893

Overview 893

Supported Features 893

IPv6-MAC Binding Configuration....895

Using the GUI 895

Binding Entries Manually 895

Binding Entries via ND Snooping....897

Binding Entries via DHCPv6 Snooping....898

Viewing the Binding Entries....900

Using the CLI....901

Binding Entries Manually....901

Binding Entries via ND Snooping....903

Binding Entries via DHCPv6 Snooping....904

Viewing Binding Entries 905

ND Detection Configuration 906

Using the GUI 906

Adding IPv6-MAC Binding Entries....906

Enabling ND Detection....906

Configuring ND Detection on Ports....907

Viewing ND Statistics....907

Using the CLI....908

Adding IPv6-MAC Binding Entries....908

Enabling ND Detection....908

Configuring ND Detection on Ports....909

Viewing ND Statistics....910

IPv6 Source Guard Configuration....911

Using the GUI 911

Adding IPv6-MAC Binding Entries....911

Configuring IPv6 Source Guard 911

Using the CLI 912

Adding IPv6-MAC Binding Entries....912

Configuring IPv6 Source Guard 912

Configuration Examples....914

Example for ND Detection....914

Network Requirements......914

Configuration Scheme....914

Using the GUI....915

Using the CLI 917

Example for IPv6 Source Guard 918

Network Requirements....918

Configuration Scheme....919

Using the GUI....919

Using the CLI 921

Appendix: Default Parameters....922

Configuring DHCP Filter

DHCP Filter 925

Overview....925

Supported Features....925

DHCPv4 Filter Configuration....927

Using the GUI 927

Configuring the Basic DHCPv4 Filter Parameters....927

Configuring Legal DHCPv4 Servers 929

Using the CLI 929

Configuring the Basic DHCPv4 Filter Parameters....929

Configuring Legal DHCPv4 Servers....931

DHCPv6 Filter Configuration....933

Using the GUI 933

Configuring the Basic DHCPv6 Filter Parameters....933

Configuring Legal DHCPv6 Servers....934

Using the CLI 935

Configuring the Basic DHCPv6 Filter Parameters....935

Configuring Legal DHCPv6 Servers....936

Configuration Examples....938

Example for DHCPv4 Filter 938

Network Requirements....938

Configuration Scheme....938

Using the GUI....939

Using the CLI 940

Example for DHCPv6 Filter 941

Network Requirements....941

Configuration Scheme....942

Using the GUI....942

Using the CLI 944

Appendix: Default Parameters....946

Configuring DoS Defend

Overview 948

DoS Defend Configuration....949

Using the GUI 949

Using the CLI 950

Appendix: Default Parameters....953

Monitoring the System

Overview 955

Monitoring the CPU 956

Using the GUI 956

Using the CLI 956

Monitoring the Memory 958

Using the GUI 958

Using the CLI 958

Monitoring Traffic

Traffic Monitor 961

Using the GUI 961

Using the CLI 965

Appendix: Default Parameters....966

Mirroring Traffic

Mirroring....968

Using the GUI 968

Using the CLI 970

Configuration Examples....972

Network Requirements....972

Configuration Scheme 972

Using the GUI 972

Using the CLI 973

Appendix: Default Parameters....975

Configuring sFlow (Only for Certain Devices)

Overview 977

sFlow Configuration....978

Using the GUI 978

Configuring the sFlow Agent....978

Configuring the sFlow Collector 979

Configuring the sFlow Sampler 979

Using the CLI....981

Configuration Example 984

Network Requirements....984

Configuration Scheme 984

Using the GUI 984

Using the CLI....985

Appendix: Default Parameters....987

Configuring OAM (Only for Certain Devices)

Ethernet OAM....989

Overview....989

Supported Features....990

Ethernet OAM Configurations....993

Using the GUI 993

Enabling OAM and Configuring OAM Mode 993

Configuring Link Monitoring....994

Configuring RFI....996

Configuring Remote Loopback....997

Viewing OAM Status....998

Using the CLI 1000

Enabling OAM and Configuring OAM Mode 1000

Configuring Link Monitoring....1001

Configuring Remote Failure Indication....1007

Configuring Remote Loopback....1008

Verifying OAM Connection....1009

Viewing OAM Statistics....1012

Using the GUI 1012

Viewing OAMPDUs....1012

Viewing Event Logs....1014

Using the CLI....1015

Viewing OAMPDUs....1015

Viewing Event Logs....1017

Configuration Example 1019

Network Requirements....1019

Configuration Scheme....1019

Using the GUI....1019

Using the CLI 1023

Appendix: Default Parameters....1027

Configuring DLDP

Overview 1029

DLDP Configuration....1030

Using the GUI 1030

Using the CLI....1032

Appendix: Default Parameters....1034

Configuring SNMP & RMON

SNMP 1036

Overview....1036

Basic Concepts....1036

SNMP Configurations....1040

Using the GUI 1040

Enabling SNMP 1040

Creating an SNMP View....1041

Creating SNMP Communities (For SNMP v1/v2c) 1042

Creating an SNMP Group (For SNMP v3)....1043

Creating SNMP Users (For SNMP v3)....1044

Using the CLI 1045

Enabling SNMP 1045

Creating an SNMP View....1047

Creating SNMP Communities (For SNMP v1/v2c) 1048

Creating an SNMP Group (For SNMPv3)....1049

Creating SNMP Users (For SNMPv3)....1051

Notification Configurations....1053

Using the GUI 1053

Configuring the Information of NMS Hosts....1053

Enabling SNMP Traps....1055

Using the CLI 1058

Configuring the NMS Host....1058

Enabling SNMP Traps....1060

RMON 1068

RMON Configurations....1069

Using the GUI 1069

Configuring the Statistics Group....1069

Configuring History Group....1070

Configuring Event Group 1071

Configuring Alarm Group....1072

Using the CLI 1074

Configuring Statistics....1074

Configuring History....1076

Configuring Event 1077

Configuring Alarm....1078

Configuration Example 1081

Network Requirements....1081

Configuration Scheme 1082

Using the GUI 1082

Using the CLI 1087

Appendix: Default Parameters....1093

Diagnosing the Device & Network

Diagnosing the Device....1098

Using the GUI 1098

Using the CLI....1099

Diagnosing the Network....1100

Using the GUI 1100

Troubleshooting with Ping Testing....1100

Troubleshooting with Tracert Testing....1101

Using the CLI 1102

Configuring the Ping Test....1102

Configuring the Tracert Test....1103

Appendix: Default Parameters....1104

Configuring System Logs

Overview 1106

System Logs Configurations....1107

Using the GUI 1108

Configuring the Local Logs....1108

Configuring the Remote Logs....1108

Backing up the Logs 1109

Viewing the Log Table....1110

Using the CLI 1111

Configuring the Local Logs....1111

Configuring the Remote Logs....1112

Configuration Example 1114

Network Requirements....1114

Configuration Scheme 1114

Using the GUI 1114

Using the CLI 1115

Appendix: Default Parameters....1116

About This Guide

This User Guide provides information for managing JetStream Switches. Please read this guide carefully before operation.

Intended Readers

This Guide is intended for network managers familiar with IT concepts and network terminologies.

Conventions

When using this guide, notice that features available in Jetstream Switches may vary by model and software version. Availability of Jetstream Switches may also vary by region or ISP. All images, steps, and descriptions in this guide are only examples and may not reflect your actual experience.

Some models featured in this guide may be unavailable in your country or region. For local sales information, visit https://www.tp-link.com.

The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied. Users must take full responsibility for their application of any products.

In this Guide, the following conventions are used:

PoE budget calculations are based on laboratory testing. Actual PoE power budget is not guaranteed and will vary as a result of client limitations and environmental factors.

The symbol stands for Note. Notes contains suggestions or references that helps you make better use of your device.

For GUI:

Menu Name > Submenu Name > Tab page indicates the menu structure. System > System Info > System Summary means the System Summary page under the System Info menu option that is located under the System menu.

Bold font indicates a button, a toolbar icon, menu or menu item.

For CLI:

Bold Font An unalterable keyword.

For example: show logging

Normal Font A constant (several options are enumerated and only one can be selected).For example: no bandwidth {all | ingress | egress}
{} Items in braces {} are required.
[] Items in square brackets [] are optional.
| Alternative items are grouped in braces and separated by vertical bars |.For example: speed {10 | 100 | 1000}
Italic Font A variable (an actual value must be assigned).For example: bridge aging-time aging-time

Common combination:

{[]][[]} A least one item in the square brackets must be selected.

For example: bandwidth {[ingress ingress-rate] [egress egress-rate]}

This command can be used on three occasions:

bandwidth ingress ingress-rate is used to restrict ingress bandwidth.

bandwidth egress egress-rate is used to restrict egress bandwidth.

bandwidth ingress ingress-rate egress egress-rate is used to restrict ingress and egress bandwidth.

More Information

■ The latest software and documentations can be found at Download Center at https://www.tp-link.com/support.
■ The Installation Guide (IG) can be found where you find this guide or inside the package of the switch.
■ The authentication information can be found where you find this guide.
■ Specifications can be found on the product page at https://www.tp-link.com.
■ To ask questions, find answers, and communicate with TP-Link users or engineers, please visit https://community.tp-link.com to join TP-Link Community.
■ Our Technical Support contact information can be found at the Contact Technical Support page at https://www.tp-link.com/support.

Part 1

Accessing the Switch

CHAPTERS

  1. Determine the Management Method
  2. Web Interface Access
  3. Command Line Interface Access

1 Determine the Management Method

Before building your network, choose a proper method to manage your switch based on your actual network situation. The switch supports two configuration options: Standalone Mode or Controller Mode.

TP-LINK Omada TL-SG2008P - Determine the Management Method - 1

Note:

Controller Mode is only available on certain devices. To check whether your device supports this feature, refer to the actual web interface. If Controller Mode is available, there is SYSTEM > Controller Settings in the menu structure.

■ Controller Mode

If you want to configure and manage a large-scale network centrally, which consists of mass devices such as access points, switches, and gateways, Controller Mode is recommended. In Controller Mode, the switch can be centrally configured and monitored via Omada SDN Controller.

To prepare the switch for Omada SDN Controller Management, refer to Controller Settings (Only for Certain Devices). For detailed instructions about the network topology in such situations and how to use Omada SDN Controller, refer to the User Guide of Omada SDN Controller. The guide can be found on the download center of our official website: https://www.tp-link.com/support/download/

■ Standalone Mode

If you have a relatively small-sized network and only one or just a small number of devices need to be managed, Standalone Mode is recommended. In Standalone Mode, the switch can be singly configured and monitored via the GUI (Graphical User Interface, also called web interface in this text) or via the CLI (Command Line Interface). There are equivalent functions in the web interface and the command line interface, while web configuration is easier and more visual than the CLI configuration. You can choose the method according to their available applications and preference.

This User Guide introduces how to configure and monitor the switch in Standalone Mode.

TP-LINK Omada TL-SG2008P - ■ Standalone Mode - 1

Note:

- The GUI and CLI is inaccessible while the switch is managed by a controller. To turn the switch back to Standalone Mode and access its GUI and CLI, you can forget the switch on the controller or reset the switch.

• The first time you log in, change the password to better protect your network and devices.

2 Web Interface Access

You can access the switch's web interface through the web-based authentication. The switch uses two built-in web servers, HTTP server and HTTPS server, for user authentication.

The following example shows how to login via the HTTP server.

2.1 Login

To manage your switch through a web browser in the host PC:

1) Make sure that the route between the host PC and the switch is available.
2) Launch a web browser. The supported web browsers include, but are not limited to, the following types:

■ IE 8.0, 9.0, 10.0, 11.0
■ Firefox 26.0, 27.0
■ Chrome 32.0, 33.0

3) Enter the switch's IP address in the web browser's address bar. The switch's default IP address is 192.168.0.1.

Figure 2-1 Enter the Switch's IP Address in the Browser
TP-LINK Omada TL-SG2008P - Login - 1

text_image 192.168.0.1

4) Enter the username and password (both admin by default) in the pop-up login window.

Figure 2-2 Login Authentication
TP-LINK Omada TL-SG2008P - Login - 2

text_image Username admin Password ...... Remember Me Log In

TP-LINK Omada TL-SG2008P - Login - 3

Note:

The first time you log in, change the password to better protect your network and devices.

5) The typical web interface displays below. You can view the switch's running status and configure the switch on this interface.

Figure 2-3 Web Interface
TP-LINK Omada TL-SG2008P - Note: - 1

text_image tp-link SYSTEM L2 FEATURES L3 FEATURES QuS SECURITY MAINTENANCE Save Log Out System Info System Summary Device Description System Time Daylight Saving Time User Management System Tools EEE SDM Template Time Range Port Status UNIT1 2 4 6 8 10 12 14 16 18 20 22 24 1 3 5 7 9 11 13 15 17 19 21 23 25 26 27 28 System Info UNIT1 System Description: JetStream 24-Port Gigabit Smart Switch with 4 SFP Slots Device Name: T1600G-28TS Device Location: SHENZHEN Contact Information: www.tp-link.com Hardware Version: T1600G-28TS 3.0 Firmware Version: 3.0.0 Build 2017/11/20 Rel.52008(s) Boot Loader Version: TP-LINK BOOTUTIL(v1.0.0) MAC Address: 00-0A-EB-13-A2-24 System Time: 2006-01-04 07:33:02 Running Time: 2 day - 23 hour - 33 min - 24 sec Serial Number: Jumbo Frame: Disabled Settings SNTP: Enabled Settings IGMP Snooping: Disabled Settings SNMP: Disabled Settings Spanning Tree: Disabled Settings DHCP Relay: Disabled Settings 802.1X: Disabled Settings HTTP Server: Enabled Settings

2.2 Save the Configuration File

The switch's configuration files fall into two types: the running configuration file and the start-up configuration file.

After you perform configurations on the sub-interfaces and click Apply, the modifications will be saved in the running configuration file. The configurations will be lost when the switch reboots.

If you need to keep the configurations after the switch reboots, please click save main interface to save the configurations in the start-up configuration file.

Figure 2-4 Save the Configuration
TP-LINK Omada TL-SG2008P - Save the Configuration File - 1

text_image SYSTEM L2 FEATURES L3 FEATURES QoS SECURITY MAINTENANCE Save Log Out Port Status Save the configuration file? No Yes 25° 26° 27° 28°

2.3 Disable the Web Server

You can shut down the HTTP server and HTTPS server to block any access to the web interface.

Go to SECURITY > Access Security > HTTP Config, disable the HTTP server and click Apply.

Figure 2-5 Shut Down HTTP Server
TP-LINK Omada TL-SG2008P - Disable the Web Server - 1

text_image Global Config HTTP: Enable Port: 80 (1-65535) Apply

Go to SECURITY > Access Security > HTTPS Config, disable the HTTPS server and click Apply.

Figure 2-6 Disbale the HTTPS Server
TP-LINK Omada TL-SG2008P - Disable the Web Server - 2

text_image Global Config HTTPS: Enable SSL Version 3: Enable TLS Version 1: Enable Port: 443 (1-65535) Apply

2.4 Configure the Switch's IP Address and Default Gateway

If you want to access the switch via a specified port (hereafter referred to as the access port), you can configure the port as a routed port and specify its IP address, or configure the IP address of the VLAN which the access port belongs to.

■ Change the IP Address

By default, all the ports belong to VLAN 1 with the VLAN interface IP 192.168.0.1.

The following example shows how to change the switch's default access IP address 192.168.0.1.

1) Go to L3 FEATURES > Interface. The default access IP address in VLAN 1 in the Interface List. Click Edit IPv4 to modify VLAN1's IP address.

Figure 2-7 Change VLAN1's IP Address
TP-LINK Omada TL-SG2008P - ■ Change the IP Address - 1

text_image Routing Config IPv4 Routing: ✓ Enable IPv6 Routing: □ Enable Apply Interface List + Add - Delete □ Interface ID IP Address Mode IP Address Subnet Mask Interface Name Status Operation □ VLAN1 Static 192.168.0.100 255.255.255.0 Up Edit IPv4 Edit IPv6 Detail Total: 1

2) Choose the IP Address Mode as Static. Enter the new access address in the IP Address field and click Apply. Make sure that the route between the host PC and the switch's new IP address is available.

Figure 2-8 Specify the IP Address
TP-LINK Omada TL-SG2008P - ■ Change the IP Address - 2

text_image Modify IPv4 Interface Interface ID: VLAN1 Admin Status: Enable Interface Name: (Optional, 1-16 characters) IP Address Mode: None Static DHCP BOOTP IP Address: 192.168.0.100 (Format: 192.168.0.1) Subnet Mask: 255.255.255.0 (Format: 255.255.255.0) Apply

3) Enter the new IP address in the web browser to access the switch.

4) Click to save the settings.

■ Configure the Default Gateway

The following example shows how to configure the switch's gateway. By default, the switch has no default gateway.

1) Go to page L3 FEATURES > Static Routing > IPv4 Static Routing Config. Click to Add load the following page and configure the parameters related to the switch's gateway. Then click Create.

Figure 2-9 Configure the Default Gateway
TP-LINK Omada TL-SG2008P - ■ Change the IP Address - 3

text_image IPv4 Static Routing Destination: 0.0.0.0 (Format: 10.10.10.0) Subnet Mask: 0.0.0.0 (Format: 255.255.255.0) Next Hop: 192.168.0.100 (Format: 192.168.0.2) Distance: 1 (Optional. range: 1-255) Cancel Create

Destination Specify the destination as 0.0.0.0.

Subnet Mask Specify the subnet mask as 0.0.0.0.

Next Hop Configure your desired default gateway as the next hop's IP address.

Distance Specify the distance as 1.

2) Click to save the settings.

3) Check the routing table to verify the default gateway you configured. The entry marked in red box displays the valid default gateway.

Figure 2-10 View the Default Gateway

IPv4 Routing Information Summary
Refresh
ProtocolDestination NetworkNext HopDistanceMetricInterface Name
Static0.0.0.0/24192.168.0.10010VLAN1
Connected192.168.0.0/24192.168.0.10001VLAN1
Total: 2

3 Command Line Interface Access

Users can access the switch's command line interface through the console (only for switch with console port), Telnet or SSH connection, and manage the switch with the command lines.

Console connection requires the host PC connecting to the switch's console port directly, while Telnet and SSH connection support both local and remote access.

The following table shows the typical applications used in the CLI access.

Table 3-1 Method list

Method Using Port Typical Applications
Console Console port (connected directly)Hyper Terminal
Telnet RJ-45 port CMD
SSH RJ-45 port Putty

3.1 Console Login (only for switch with console port)

Follow these steps to log in to the switch via the Console port:

1) Connect the PC or terminal to the Console port on the switch with the serial cable.
2) Start the terminal emulation program (such as the Hyper Terminal) on the PC and configure the terminal emulation program as follows:

■ Baud Rate: 38400bps
■ Data Bits: 8
■ Parity: None
■ Stop Bits: 1
■ Flow Control: None

3) Type the User name and Password in the Hyper Terminal window. The default value for both of them is admin. Press Enter in the main window and Switch> will appear, which

indicates that you have successfully logged in to the switch and you can use the CLI now.

Figure 3-1 CLI Main Window
TP-LINK Omada TL-SG2008P - Console Login (only for switch with console port) - 1

text_image User admin Password: Switch>

TP-LINK Omada TL-SG2008P - Console Login (only for switch with console port) - 2

Note:

The first time you log in, change the password to better protect your network and devices.

4) Enter enable to enter the User EXEC Mode to further configure the switch.

Figure 3-2 User EXEC Mode
TP-LINK Omada TL-SG2008P - Note: - 1

text_image User admin Password. Switch>enable SwitchH_

TP-LINK Omada TL-SG2008P - Note: - 2

Note:

In Windows XP, go to Start > All Programs > Accessories > Communications > Hyper Terminal to open the Hyper Terminal and configure the above settings to log in to the switch.

3.2 Telnet Login

The switch supports Login Local Mode for authentication by default.

Login Local Mode: Username and password are required, which are both admin by default.

The following steps show how to manage the switch via the Login Local Mode:

1) Make sure the switch and the PC are in the same LAN (Local Area Network). Click Start and type in cmd in the Search bar and press Enter.

Figure 3-3 Open the CMD Window
TP-LINK Omada TL-SG2008P - Telnet Login - 1

text_image cmd Shut down

2) Type in telnet 192.168.0.1 in the CMD window and press Enter.

Figure 3-4 Log In to the Switch
TP-LINK Omada TL-SG2008P - Telnet Login - 2

text_image Microsoft Windows [Version 6.1.7500] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\admin.WIN7-PC\telnet 192.168.0.1

3) Type in the login username and password (both admin by default). Press Enter and you will enter User EXEC Mode.

Figure 3-5 Enter User EXEC Mode
TP-LINK Omada TL-SG2008P - Telnet Login - 3

text_image User:admin Password: Switch>%2006-01-01 08:02:54,[User]/3/Login the CLI by admin on vty0 (192.168.0.200). Switch>

TP-LINK Omada TL-SG2008P - Telnet Login - 4

Note:

The first time you log in, change the password to better protect your network and devices.

4) Type in enable command and you will enter Privileged EXEC Mode. By default no password is needed. Later you can set a password for users who want to access the Privileged EXEC Mode.

Figure 3-6 Enter Privileged EXEC Mode
TP-LINK Omada TL-SG2008P - Note: - 1

text_image User Access Login User:admin Password: Switch)#2006-01-01 00:21:11,[User]/3/login the CLI by admin on vty8 (192.168.0.200). Switch>enable Switch#_

Now you can manage your switch with CLI commands through Telnet connection.

3.3 SSH Login

SSH login supports the following two modes: Password Authentication Mode and Key Authentication Mode. You can choose one according to your needs:

■ Password Authentication Mode: Username and password are required, which are both admin by default.
■ Key Authentication Mode (Recommended): A public key for the switch and a private key for the client software (PuTTY) are required. You can generate the public key and the private key through the PuTTY Key Generator.

Before logging in via SSH, follow the steps below to enable SSH on the terminal emulation program:

Figure 3-7 Enable SSH
TP-LINK Omada TL-SG2008P - SSH Login - 1

text_image User Access Login ***** User:admin Password: Switch>#2006-01-01 08:10:29,[User]/3/Login the CLI by admin on vty0 (192.168.0.200). Switch>enable Switch#config Switch(config)#ip ssh server Switch#_ Enable SSH function

Password Authentication Mode

1) Open PuTTY and go to the Session page. Enter the IP address of the switch in the Host Name field and keep the default value 22 in the Port field; select SSH as the Connection type. Click Open.

Figure 3-8 Configurations in PuTTY
TP-LINK Omada TL-SG2008P - Password Authentication Mode - 1

text_image PuTTY Configuration Category: Session Logging Terminal Keyboard Bell Features Window Appearance Behaviour Translation Selection Colours Connection Data Proxy Telnet Rlogin SSH Serial Basic options for your PuTTY session Specify the destination you want to connect to Host Name (or IP address) Port 192.168.0.1 22 Connection type: Raw Telnet Rlogin SSH Serial Load, save or delete a stored session Saved Sessions Default Settings Load Save Delete Close window on exit: Always Never Only on clean exit About Open Cancel

2) Enter the login username and password to log in to the switch, and you can continue to configure the switch.

Figure 3-9 Log In to the Switch
TP-LINK Omada TL-SG2008P - Password Authentication Mode - 2

text_image login as: admin Further authentication required Authenticating with public key "rsa-key-20150122" T1700X-16TS3>

TP-LINK Omada TL-SG2008P - Password Authentication Mode - 3

Note:

The first time you log in, change the password to better protect your network and devices.

Key Authentication Mode

1) Open the PuTTY Key Generator. In the Parameters section, select the key type and enter the key length. In the Actions section, click Generate to generate a public/private key pair. In the following figure, an SSH-2 RSA key pair is generated, and the length of each key is 1024 bits.

Figure 3-10 Generate a Public/Private Key Pair
TP-LINK Omada TL-SG2008P - Key Authentication Mode - 1

text_image PuTTY Key Generator File Key Conversions Help Key No key. Actions Generate a public/private key pair Generate a key Generate Load an existing private key file Load Save the generated key Save public key Save private key Parameters Type of key to generate: SSH-1 (RSA) SSH-2 RSA SSH-2 DSA Key type Number of bits in a generated key: Key length 2048

TP-LINK Omada TL-SG2008P - Key Authentication Mode - 2

Note:

• The key length should be between 512 and 3072 bits.
- You can accelerate the key generation process by moving the mouse quickly and randomly in the Key section.

2) After the keys are successfully generated, click Save public key to save the public key to a TFTP server; click Save private key to save the private key to the host PC.

Figure 3-11 Save the Generated Keys
TP-LINK Omada TL-SG2008P - Note: - 1

text_image PuTTY Key Generator File Key Conversions Help Key Public key for pasting into OpenSSH authorized_keys file: ssh-rsa AAAAB3NzaC1yc2EAAAABJQAAAQEAg4R3LBYbN7SDbFjn3MuoHr4LHF7Jv8WNBCf 7xoJzrlwndlbpC7Dkxd8m0zlJo6SR +sUVK8EaTWROqOpfBxohu7QPLIBM40cMz0mDCZk3bhfg6g0rVf0MmSmGNoEYtiD qhXLbFU3rDxTjn5nlUCrvG0oRUKIvaYR8qSqKHwpsGbZKQlZtS/Bgp1/2Pn0fzzSSZD Key fingerprint: ssh-rsa 2048 cf:11.bc:4b:40:55:50:ef:8a:e4:9d:c5:b9:ca:30:13 Key comment: rsa-key-20150122 Key passphrase: Confirm passphrase: Actions Generate a public/private key pair Generate Load an existing private key file Load Save the generated key Save public key Save private key Parameters Type of key to generate: SSH-1 (RSA) SSH-2 RSA SSH-2 DSA Number of bits in a generated key: 2048

3) On Hyper Terminal, download the public key file from the TFTP server to the switch as shown in the following figure:

Figure 3-12 Download the Public Key to the Switch
TP-LINK Omada TL-SG2008P - Note: - 2

text_image Telnet 192.168.0.1 ***************** User Access Login ****************** User:admin Password: #2006-01-27 08:06:01.[User]/5/Login the CLI by admin on vty0 (192.168.0.200). Switch>enable Switch#configure Switch(config)#ip ssh download v2 public ip-address 192.168.0.100 Start to download SSH key file...... Download SSH key file OK. Switch(config> the filename of the public key the ip address of the TFTP server

TP-LINK Omada TL-SG2008P - Note: - 3

Note:

  • The key type should accord with the type of the key file. In the above CLI, v1 corresponds to SSH-1 (RSA), and v2 corresponds to SSH-2 RSA and SSH-2 DSA.
    • The key downloading process cannot be interrupted.

4) After the public key is downloaded, open PuTTY and go to the Session page. Enter the IP address of the switch and select SSH as the Connection type (keep the default value in the Port field).

Figure 3-13 Configure the Host Name and Connection Type
TP-LINK Omada TL-SG2008P - Note: - 1

text_image PuTTY Configuration Category: Session Logging Terminal Keyboard Bell Features Window Appearance Behaviour Translation Selection Colours Connection Data Proxy Telnet Rlogin SSH Serial Basic options for your PuTTY session Specify the destination you want to connect to Host Name (or IP address) Port 192.168.0.1 22 Connection type: Raw Telnet Rlogin SSH Serial Load, save or delete a stored session Saved Sessions Default Settings Load Save Delete Close window on exit: Always Never Only on clean exit About Open Cancel

5) Go to Connection > SSH > Auth. Click Browse to download the private key file to PuTTY. Click Open to start the connection and negotiation.

Figure 3-14 Download the Private Key to PuTTY
TP-LINK Omada TL-SG2008P - Note: - 2

text_image PuTTY Configuration Category: Session Logging Terminal Keyboard Bell Features Window Appearance Behaviour Translation Selection Colours Connection Data Proxy Telnet Rlogin SSH Kex Auth TTY X11 About Options controlling SSH authentication Bypass authentication entirely (SSH-2 only) Authentication methods Attempt authentication using Pageant Attempt TIS or CryptoCard auth (SSH-1) Attempt "keyboard-interactive" auth (SSH-2) Authentication parameters Allow agent forwarding Allow attempted changes of username in SSH-2 Private key file for authentication: D:\Program files\private.ppk Browse... Open Cancel

6) After negotiation is completed, enter the username to log in. If you can log in without entering the password, the key authentication completed successfully.

Figure 3-15 Log In to the Switch
TP-LINK Omada TL-SG2008P - Note: - 3

text_image login as: admin Further authentication required Authenciating with public key "zsa-key-20150122" T1700X-16TS>

TP-LINK Omada TL-SG2008P - Note: - 4

Note:

The first time you log in, change the password to better protect your network and devices.

3.4 Disable Telnet login

You can shut down the Telnet function to block any Telnet access to the CLI interface.

■ Using the GUI:

Go to SECURITY > Access Security > Telnet Config, disable the Telnet function and click Apply.

Figure 3-16 Disable Telnet login
TP-LINK Omada TL-SG2008P - Disable Telnet login - 1

text_image Telnet Config Telnet: Enable Port: 23 (1-65535) Apply

■ Using the CLI:

Switch#configure

Switch(config)#telnet disable

3.5 Disable SSH login

You can shut down the SSH server to block any SSH access to the CLI interface.

■ Using the GUI:

Go to SECURITY > Access Security > SSH Config, disable the SSH server and click Apply.

Figure 3-17 Shut down SSH server
TP-LINK Omada TL-SG2008P - Disable SSH login - 1

text_image Global Config SSH: Enable Protocol V1: Enable Protocol V2: Enable Idle Timeout: 120 seconds (1-120) Maximum Connections: 5 (1-5) Port: 22 (1-65535) Apply

■ Using the CLI:

Switch#configure

Switch(config)#no ip ssh server

3.6 Copy running-config startup-config

The switch's configuration files fall into two types: the running configuration file and the start-up configuration file.

After you enter each command line, the modifications will be saved in the running configuration file. The configurations will be lost when the switch reboots.

If you need to keep the configurations after the switch reboots, please use the command copy running-config startup-config to save the configurations in the start-up configuration file.

Switch(config)#end

Switch#copy running-config startup-config

3.7 Change the Switch's IP Address and Default Gateway

If you want to access the switch via a specified port (hereafter referred to as the access port), you can configure the port as a routed port and specify its IP address, or configure the IP address of the VLAN which the access port belongs to.

■ Change the IP Address

By default, all the ports belong to VLAN 1 with the VLAN interface IP 192.168.0.1/24. In the following example, we will show how to replace the switch's default access IP address 192.168.0.1/24 with 192.168.0.10/24.

Switch#configure

Switch(config)#interface vlan 1

Switch(config-if)#ip address 192.168.0.10 255.255.255.0

The connection will be interrupted and you should telnet to the switch's new IP address 192.168.0.10.

C:\Users\Administrator>telnet 192.168.0.10

User:admin

Password:tplink

Switch>enable

Switch#copy running-config startup-config

■ Configure the Default Gateway

In the following example, we will show how to configure the switch's gateway as 192.168.0.100. By default, the switch has no default gateway.

Switch#configure

Switch(config)#ip route 0.0.0.0 0.0.0.0 192.168.0.100 1

Switch(config)#end

Switch#copy running-config startup-config

Part 2

Managing System

CHAPTERS

  1. System
  2. System Info Configurations
  3. User Management Configurations
  4. System Tools Configurations
  5. EEE Configuration
  6. PoE Configurations (Only for Certain Devices)
  7. SDM Template Configuration
  8. Time Range Configuration
  9. Controller Settings (Only for Certain Devices)
  10. Example for PoE Configurations
  11. Appendix: Default Parameters

1 System

1.1 Overview

In System module, you can view the system information and configure the system parameters and features of the switch.

1.2 Supported Features

System Info

You can view the switch's port status and system information, and configure the device description, system time, and daylight saving time.

User Management

You can manage the user accounts for login to the switch. There are multiple user types which have different access levels, and you can create different user accounts according to your need.

System Tools

You can configure the boot file of the switch, backup and restore the configurations, update the firmware, reset the switch, and reboot the switch.

EEE

EEE (Energy Efficient Ethernet) is used to save power consumption of the switch during periods of low data activity. You can simply enable this feature on ports to allow power reduction.

PoE

TP-LINK Omada TL-SG2008P - PoE - 1

Note:

PoE configuration is only available on certain devices. To check whether your device supports this feature, refer to the actual web interface. If PoE configuration is available, there is SYSTEM > PoE in the menu structure.

Power over Ethernet (PoE) is a remote power supply function. With this function, the switch can supply power to the connected devices over twisted-pair cable.

Some devices such as IP phones, access points (APs) and cameras may be located far away from the AC power source in actual use. PoE can provide power for these devices without requiring to deploy power cables. This allows a single cable to provide both data connection and electric power to devices.

IEEE 802.3af and 802.3at are both PoE standards. The standard process of PoE power supply contains powered-device discovery, power administration, disconnect detection and optional power-device power classification.

PSE

Power sourcing equipment (PSE) is a device that provides power for PDs on the Ethernet, for example, the PoE switch. PSE can detect the PDs and determine the device power requirements.

PD

Powered device (PD) is a device receiving power from the PSE, for example, IP phones and access points. According to whether PDs comply with IEEE standard, they can be classified into standard PDs and non-standard PDs. Only standard PDs can be powered via TP-Link PoE switches.

SDM Template

SDM (Switch Database Management) Template is used to prioritize hardware resources for certain features. The switch provides three templates which allocate different hardware resources for different usage, and you can choose one according to your need.

Time Range

With this feature, you can configure a time range. You can use the time range when you configure other features like ACL.

Controller Settings

TP-LINK Omada TL-SG2008P - Controller Settings - 1

Note:

Controller Settings is only available on certain devices. To check whether your device supports this feature, refer to the actual web interface. If Controller Settings is available, there is SYSTEM >Controller Settings in the menu structure.

With this feature, you can configure your switch to be discovered by Omada SDN Controller on this page, then it can be managed centrally via Omada SDN Controller.

2 System Info Configurations

With system information configurations, you can:

■ View the System Summary
■ Configure the Device Description
■ Configure the System Time
■ Configure the Daylight Saving Time
■ Configuring LED (Only for Certain Devices)

2.1 Using the GUI

2.1.1 Viewing the System Summary

Choose the menu SYSTEM > System Info > System Summary to load the System Summary page. You can view the port status and system information of the switch.

Viewing the Port Status

In the Port Status section, you can view the status and bandwidth utilization of each port.

Figure 2-1 Viewing the System Summary
TP-LINK Omada TL-SG2008P - Viewing the Port Status - 1

text_image Port Status UNIT 1 2 4 6 8 10 12 14 16 18 20 22 24 1 3 5 7 9 11 13 15 17 19 21 23 25 26 27 28

The following table introduces the meaning of each port status:

Port Status Indication
Indicates the Ethernet port is not connected to a device.
Indicates the Ethernet port is transmitting and receiving data at the highest speed.
Indicates the Ethernet port is transmitting and receiving data, but not at the highest speed.
Indicates the SFP port is not connected to a device.
Indicates the SFP port is transmitting and receiving data at the highest speed.

TP-LINK Omada TL-SG2008P - Viewing the Port Status - 2

Indicates the SFP port is transmitting and receiving data, but not at the highest speed.

You can move your cursor to a port to view the detailed information of the port.

Figure 2-2 Port Information
TP-LINK Omada TL-SG2008P - Viewing the Port Status - 3

text_image Port:1/0/4 Type: Auto RJ45 Speed: 1000M, Full Duplex Status: Link Up

Port Information Indication

Port Displays the port number.

Type Displays the type of the port.

Speed Displays the maximum transmission rate and duplex mode of the port.

Status Displays the connection status of the port.

You can click a port to view the bandwidth utilization on this port.

Figure 2-3 Bnadwidth Utilization
TP-LINK Omada TL-SG2008P - Viewing the Port Status - 4

bar Bandwidth Utilization (Port: 1/0/18) | Port | Bandwidth Utilization (%) | |---|---| | 1 | 100 | | 2 | 100 | | 3 | 100 | | 4 | 100 | | 5 | 100 | | 6 | 100 | | 7 | 100 | | 8 | 100 | | 9 | 100 | | 10 | 100 | | 11 | 100 | | 12 | 100 | | 13 | 100 | | 14 | 100 | | 15 | 100 | | 16 | 100 | | 17 | 100 | | 18 | 100 | | 19 | 100 | | 20 | 100 | | 21 | 100 | | 22 | 100 | | 23 | 100 | | 24 | 100 | | 25 | 100 | | 26 | 100 | | 27 | 100 | | 28 | 100 | Legend: RX = RX, TX = TX Current Utilization: RX = RX, TX = TX %Utilization: RX = RX, TX = TX

RX Displays the bandwidth utilization of receiving packets on this port.

TX Displays the bandwidth utilization of sending packets on this port.

Viewing the System Information

In the System Info section, you can view the system information of the switch.

Figure 2-4 System Information

System Info
UNIT1
System Description:JetStream 24-Port Gigabit Smart Switch with 4 SFP Slots
Device Name:T1600G-28TS
Device Location:SHENZHEN
Contact Information:www.tp-link.com
Hardware Version:T1600G-28TS 3.0
Firmware Version:3.0.0 Build 20171011 Rel.72184(s)
Boot Loader VersionTP-LINK BOOTUTIL(v1.0.0)
MAC Address:00-0A-EB-13-A2-24
System Time:2006-01-02 10:20:02
Running Time:1 day - 2 hour - 20 min - 24 sec
Serial Number:
Jumbo Frame:DisabledSettings
SNTP:EnabledSettings
IGMP Snooping:DisabledSettings
SNMP:DisabledSettings
Spanning Tree:DisabledSettings
DHCP Relay:DisabledSettings
802.1X:DisabledSettings
HTTP Server:EnabledSettings
Telnet:EnabledSettings
SSH:DisabledSettings

System Description Displays the system description of the switch.

Device Name Displays the name of the switch. You can edit it on the Device Description page.

Device LocationDisplays the location of the switch. You can edit it on the Device Description page.
Contact InformationDisplays the contact information of the switch. You can edit it on the Device Description page.
Hardware VersionDisplays the hardware version of the switch.
Firmware VersionDisplays the firmware version of the switch.
Boot Loader VersionDisplays the boot loader version of the switch.
MAC Address Displays the MAC address of the switch.
System Time Displays the system time of the switch.
Running Time Displays the running time of the switch.
Serial Number Displays the serial number of the switch.
Jumbo FrameDisplays whether Jumbo Frame is enabled. You can click Settings to jump to the Jumbo Frame configuration page.
SNTPDisplays whether the switch gets system time from NTP Server. You can click Settings to jump to the System Time configuration page.
IGMP SnoopingDisplays whether IGMP Snooping is enabled. You can click Settings to jump to the IGMP Snooping configuration page.
SNMPDisplays whether SNMP is enabled. You can click Settings to jump to the SNMP configuration page.
Spanning TreeDisplays whether Spanning Tree is enabled. You can click Settings to jump to the Spanning Tree configuration page.
DHCP RelayDisplays whether DHCP Relay is enabled. You can click Settings to jump to the DHCP Relay configuration page.
802.1xDisplays whether 802.1x is enabled. You can click Settings to jump to the 802.1x configuration page.
HTTP ServerDisplays whether HTTP server is enabled. You can click Settings to jump to the HTTP configuration page.
TelnetDisplays whether Telnet is enabled. You can click Settings to jump to the Telnet configuration page.
SSHDisplays whether SSH is enabled. You can click Settings to jump to the SSH configuration page.

2.1.2 Configuring the Device Description

Choose the menu SYSTEM > System Info > Device Description to load the following page.

Figure 2-5 Configuring the Device Description
TP-LINK Omada TL-SG2008P - Configuring the Device Description - 1

text_image Device Description Device Name: T1600G-28TS (1-32 characters) Device Location: SHENZHEN (1-32 characters) System Contact: www.tp-link.com (1-32 characters) Apply

1) In the Device Description section, configure the following parameters.

Device Name Specify a name for the switch.

Device Location Enter the location of the switch.

System Contact Enter the contact information.

2) Click Apply.

2.1.3 Configuring the System Time

Choose the menu SYSTEM > System Info > System Time to load the following page.

Figure 2-6 Configuring the System Time
TP-LINK Omada TL-SG2008P - Configuring the System Time - 1

text_image Time Info Current System Time: Monday, January 2, 2006 05:21:47 Current Time Source: Manual Time Config ○ Manual ● Get Time from NTP Server ○ Synchronize with PC's Clock Time Zone: (GMT+08:00) Beijing, Urumqi, Hong Kong, Taipei ▼ Primary NTP Server: 133.100.9.2 (Format: 192.168.0.1 or 2001::1) Secondary NTP Server: 139.78.100.163 (Format: 192.168.0.1 or 2001::1) Update Rate: 12 hours (1-24) Apply

In the Time Info section, you can view the current time information of the switch.

Current System TimeDisplays the current date and time of the switch.
Current Time SourceDisplays how the switch gets the current time.

In the Time Config section, follow these steps to configure the system time:

1) Choose one method to set the system time and specify the related parameters.

Manual Set the system time manually.
Date: Specify the date of the system.
Time: Specify the time of the system.
Get Time from NTP ServerGet the system time from an NTP server. Make sure the NTP server is accessible on your network. If the NTP server is on the internet, connect the switch to the internet first.Time Zone: Select your local time zone.Primary Server: Enter the IP Address of the primary NTP server.Secondary Server: Enter the IP Address of the secondary NTP server. Once the primary NTP server is down, the EAP can get the system time from the secondary NTP server.Update Rate: Specify the interval the switch fetching time from NTP server, which ranges from 1 to 24 hours.
Synchronize with PC's ClockSynchronize the system time with the clock of your currently logged-in host.

2) Click Apply.

2.1.4 Configuring the Daylight Saving Time

Choose the menu SYSTEM > System Info > Daylight Saving Time to load the following page.

Figure 2-7 Configuring the Daylight Saving Time
TP-LINK Omada TL-SG2008P - Configuring the Daylight Saving Time - 1

text_image DST Config DST Status: ✓ Enable Mode: Predefined Mode ○ Recurring Mode ○ Date Mode Predefined Profile: USA Apply

Follow these steps to configure Daylight Saving Time:

1) In the DST Config section, enable the Daylight Saving Time function.

2) Choose one method to set the Daylight Saving Time and specify the related parameters.

Predefined ModeIf you select Predefined Mode, choose a predefined DST schedule for the switch.USA: Select the Daylight Saving Time of the USA. It is from 2:00 a.m. on the Second Sunday in March to 2:00 a.m. on the First Sunday in November.Australia: Select the Daylight Saving Time of Australia. It is from 2:00 a.m. on the First Sunday in October to 3:00 a.m. on the First Sunday in April.Europe: Select the Daylight Saving Time of Europe. It is from 1:00 a.m. on the Last Sunday in March to 1:00 a.m. on the Last Sunday in October.New Zealand: Select the Daylight Saving Time of New Zealand. It is from 2:00 a.m. on the Last Sunday in September to 3:00 a.m. on the First Sunday in April.
Recurring ModeIf you select Recurring Mode, specify a cycle time range for the Daylight Saving Time of the switch. This configuration will be used every year.Offset: Specify the time to set the clock forward by.Start Time: Specify the start time of Daylight Saving Time. The interval between start time and end time should be more than 1 day and less than 1 year(365 days).End Time: Specify the end time of Daylight Saving Time. The interval between start time and end time should be more than 1 day and less than 1 year (365 days).
Date ModeIf you select Date Mode, specify an absolute time range for the Daylight Saving Time of the switch. This configuration will be used only one time.Offset: Specify the time to set the clock forward by.Start Time: Specify the start time of Daylight Saving Time. The interval between start time and end time should be more than 1 day and less than 1 year(365 days).End Time: Specify the end time of Daylight Saving Time. The interval between start time and end time should be more than 1 day and less than 1 year (365 days).

3) Click Apply.

2.1.5 Configuring LED (Only for Certain Devices)

TP-LINK Omada TL-SG2008P - Configuring LED (Only for Certain Devices) - 1

Note:

Configuring LED is only available on certain devices. To check whether your device supports this feature, refer to the actual web interface. If configuring LED is available, there is SYSTEM > LED On/Off in the menu structure.

Choose the menu System > LED On/Off to load the following page. Choose the LED status and click Apply.

Figure 2-8 Configuring LED On/Off
TP-LINK Omada TL-SG2008P - Note: - 1

text_image LED On/Off Config LED: On Off Apply

2.2 Using the CLI

2.2.1 Viewing the System Summary

On privileged EXEC mode or any other configuration mode, you can use the following commands to view the system information of the switch:

show interface status [ fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port ]

View status of the interface.

port: Enter the number of the Ethernet port.

show system-info

View the system information including System Description, Device Name, Device Location, System Contact, Hardware Version, Firmware Version, System Time, Run Time and so on.

The following example shows how to view the interface status and the system information of the switch.

Switch#show interface status

PortStatusSpeedDuplexFlowCtrlJumboActive-Medium
Gi1/0/1LinkDownN/AN/AN/ADisableCopper
Gi1/0/2LinkDownN/AN/AN/ADisableCopper
Gi1/0/3LinkUp1000MFullDisableDisableCopper

...

Switch#show system-info

System Description - JetStream 48-Port Gigabit Smart Switch with 4 SFP Slots

System Name - T1600G-52TS

System Location - SHENZHEN

Contact Information - www.tp-link.com

Hardware Version - T1600G-52TS 3.0

Software Version - 3.0.0 Build 20171129 Rel.38400(s)

Bootloader Version - TP-LINK BOOTUTIL(v1.0.0)

Mac Address - 00-0A-EB-13-23-A0

Serial Number -

System Time - 2017-12-12 10:10:37

Running Time - 1 day - 2 hour - 11 min - 30 sec

2.2.2 Configuring the Device Description

Follow these steps to configure the device description:

Step 1 configure

Enter global configuration mode.

Step 2 hostname [ hostname ]

Specify the system name of the switch.

hostname: Enter the device name. The length of the name ranges from 1 to 32 characters. By default, it is the model name of the switch.

Step 3 location [ location ]

Specify the system location of the switch.

location: Enter the device location. It should consist of no more than 32 characters. By default, it is "SHENZHEN".

Step 4 contact-info [ contact-info ]

Specify the system contact Information.

contact-info: Enter the contact information. It should consist of no more than 32 characters. By default, it is "www.tp-link.com".

Step 5 show system-info

Verify the system information including system Description, Device Name, Device Location, System Contact, Hardware Version, Firmware Version, System Time, Run Time and so on.

Step 6 end

Return to privileged EXEC mode.

Step 7 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to set the device name as Switch_A, set the location as BEIJING and set the contact information as https://www.tp-link.com.

Switch#configure

Switch(config)#hostname Switch_A

Switch(config)#location BEIJING

Switch(config)#contact-info https://www.tp-link.com

Switch(config)#show system-info

System Description - JetStream 24-Port Gigabit Smart Switch with 4 SFP Slots

System Name - Switch_A

System Location - BEIJING

Contact Information - https://www.tp-link.com

...

Switch(config)#end

Switch#copy running-config startup-config

2.2.3 Configuring the System Time

Follow these steps to configure the system time:

TP-LINK Omada TL-SG2008P - Configuring the System Time - 1

Note:

The mode of Synchronize with PC's Clock does not support CLI command.

Step 1 configure

Enter global configuration mode.

Step 2 Use the following command to set the system time manually:

system-time manual time

Configure the system time manually.

time: Specify the date and time manually in the format of MM/DD/YYYY-HH:MM:SS. The valid value of the year ranges from 2000 to 2037.

Use the following command to set the system time by getting time from the NTP server. Ensure the NTP server is accessible. If the NTP server is on the internet, connect the switch to the internet first.

system-time ntp { timezone } { ntp-server } { backup-ntp-server } { fetching-rate }

timezone: Enter your local time-zone, which ranges from UTC-12:00 to UTC+13:00.

The detailed information of each time-zone are displayed as follows:

UTC-12:00 — TimeZone for International Date Line West.

UTC-11:00 — TimeZone for Coordinated Universal Time-11.

UTC-10:00 — TimeZone for Hawaii.

UTC-09:00 — TimeZone for Alaska.

UTC-08:00 — TimeZone for Pacific Time (US Canada).

UTC-07:00 — TimeZone for Mountain Time (US Canada).

UTC-06:00 — TimeZone for Central Time (US Canada).

UTC-05:00 — TimeZone for Eastern Time (US Canada).

UTC-04:30 —— TimeZone for Caracas.

UTC-04:00 — TimeZone for Atlantic Time (Canada).

UTC-03:30 — TimeZone for Newfoundland.

UTC-03:00 — TimeZone for Buenos Aires, Salvador, Brasilia.

UTC-02:00 — TimeZone for Mid-Atlantic.

UTC-01:00 — TimeZone for Azores, Cape Verde Is.

UTC — TimeZone for Dublin, Edinburgh, Lisbon, London.

UTC+01:00 —— TimeZone for Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna.

UTC+02:00 —— TimeZone for Cairo, Athens, Bucharest, Amman, Beirut, Jerusalem.

UTC+03:00 — TimeZone for Kuwait, Riyadh, Baghdad.

UTC+03:30 — TimeZone for Tehran.

UTC+04:00 —— TimeZone for Moscow, St.Petersburg, Volgograd, Tbilisi, Port Louis.

UTC+04:30 — TimeZone for Kabul.

UTC+05:00 — TimeZone for Islamabad, Karachi, Tashkent.

UTC+05:30 — TimeZone for Chennai, Kolkata, Mumbai, New Delhi.

UTC+05:45 —— TimeZone for Kathmandu.

UTC+06:00 — TimeZone for Dhaka, Astana, Ekaterinburg.

UTC+06:30 — TimeZone for Yangon (Rangoon).

UTC+07:00 — TimeZone for Novosibrisk, Bangkok, Hanoi, Jakarta.

UTC+08:00 —— TimeZone for Beijing, Chongqing, Hong Kong, Urumqi, Singapore.

UTC+09:00 —— TimeZone for Seoul, Irkutsk, Osaka, Sapporo, Tokyo.

UTC+09:30 — TimeZone for Darwin, Adelaide.

UTC+10:00 —— TimeZone for Canberra, Melbourne, Sydney, Brisbane.

UTC+11:00 —— TimeZone for Solomon Is., New Caledonia, Vladivostok.

UTC+12:00 —— TimeZone for Fiji, Magadan, Auckland, Wellington.

UTC+13:00 — TimeZone for Nuku'alofa, Samoa.

ntp-server: Specify the IP address of the primary NTP server.

backup-ntp-server: Specify the IP address of the backup NTP server.

fetching-rate: Specify the interval fetching time from the NTP server.

Step 3 Use the following command to verify the system time information.

show system-time

Verify the system time information.

Use the following command to verify the NTP mode configuration information.

show system-time ntp

Verify the system time information of NTP mode.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to set the system time by Get Time from NTP Server and set the time zone as UTC+08:00, set the NTP server as 133.100.9.2, set the backup NTP server as 139.78.100.163 and set the update rate as 11.

Switch#configure

Switch(config)#system-time ntp UTC+08:00 133.100.9.2 139.78.100.163 11

Switch(config)#show system-time ntp

Backup NTP server: 139.78.100.163

Last successful NTP server: 133.100.9.2

Update Rate: 11 hour(s)

Switch(config)#end

Switch#copy running-config startup-config

2.2.4 Configuring the Daylight Saving Time

Follow these steps to configure the Daylight Saving Time:

Step 1 configure

Enter global configuration mode.

Step 2 Use the following command to select a predefined Daylight Saving Time configuration:

system-time dst predefined [USA | Australia | Europe | New-Zealand]

Specify the Daylight Saving Time using a predefined schedule.

USA | Australia | Europe | New-Zealand: Select one mode of Daylight Saving Time.

USA: 02:00 a.m. on the Second Sunday in March \~ 02:00 a.m. on the First Sunday in November.

Australia: 02:00 a.m. on the First Sunday in October \~ 03:00 a.m. on the First Sunday in April.

Europe: 01:00 a.m. on the Last Sunday in March \~ 01:00 a.m. on the Last Sunday in October.

New Zealand: 02:00 a.m. on the Last Sunday in September \~ 03:00 a.m. on the First Sunday in April.

Use the following command to set the Daylight Saving Time in recurring mode:

system-time dst recurring {sweek}{sday}{smonth}{stime}{eweek}{eday}{emonth}{etime}[offset]

Specify the Daylight Saving Time in Recuring mode.

sweek: Enter the start week of Daylight Saving Time. There are 5 values showing as follows: first, second, third, fourth, last.

sday. Enter the start day of Daylight Saving Time. There are 7 values showing as follows: Sun, Mon, Tue, Wed, Thu, Fri, Sat.

smonth: Enter the start month of Daylight Saving Time. There are 12 values showing as follows: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec.

stime: Enter the start time of Daylight Saving Time, in the format of HH:MM.

eweek: Enter the end week of Daylight Saving Time. There are 5 values showing as follows: first, second, third, fourth, last.

eday. Enter the end day of Daylight Saving Time. There are 7 values showing as follows: Sun, Mon, Tue, Wed, Thu, Fri, Sat.

emonth: Enter the end month of Daylight Saving Time. There are 12 values showing as follows: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec.

etime: Enter the end time of Daylight Saving Time, in the format of HH:MM.

offset: Enter the offset of Daylight Saving Time. The default value is 60.

Use the following command to set the Daylight Saving Time in date mode:

system-time dst date {smonth } {sday } {stime } {syear } {emonth } {eday } {etime } {eyear } [ offset]

Specify the Daylight Saving Time in Date mode.

smonth: Enter the start month of Daylight Saving Time. There are 12 values showing as follows: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec.

sday: Enter the start day of Daylight Saving Time, which ranges from 1 to 31.

stime: Enter the start time of Daylight Saving Time, in the format of HH:MM.

syear: Enter the start year of Daylight Saving Time.

emonth: Enter the end month of Daylight Saving Time. There are 12 values showing as follows: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec.

eday: Enter the end day of Daylight Saving Time, which ranges from 1 to 31.

etime: Enter the end time of Daylight Saving Time, in the format of HH:MM.

eyear: Enter the end year of Daylight Saving Time.

offset: Enter the offset of Daylight Saving Time. The default value is 60.

Step 3 show system-time dst

Verify the DST information of the switch.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to set the Daylight Saving Time by Date Mode. Set the start time as 01:00 August 1st, 2017, set the end time as 01:00 September 1st, 2017 and set the offset as 50.

Switch#configure

Switch(config)#system-time dst date Aug 1 01:00 2017 Sep 1 01:00 2017 50

Switch(config)#show system-time dst

DST starts at 01:00:00 on Aug 1 2017

DST ends at 01:00:00 on Sep 1 2017

DST offset is 50 minutes

DST configuration is one-off

Switch(config)#end

Switch#copy running-config startup-config

2.2.5 Configuring LED (Only for Certain Devices)

TP-LINK Omada TL-SG2008P - Configuring LED (Only for Certain Devices) - 1

Note:

LED configuration is only available on certain devices. To check whether your device supports this feature, refer to the actual web interface. If LED configuration is available, there is SYSTEM > LED On/Off in the menu structure.

Follow these steps to configure the LED status:

Step 1 configure

Enter global configuration mode.

Step 2 led {on | off}

Configure the LED status. By default, the LEDs are on.

on | off: Turn on or turn off the LEDs.

3 User Management Configurations

With User Management, you can create and manage the user accounts for login to the switch.

3.1 Using the GUI

There are four types of user accounts with different access levels: Admin, Operator, Power User and User.

■ There is a default Admin account which cannot be deleted. The default username and password of this account are both admin. You can also create more Admin accounts.

If you create Operator, Power User or User accounts, you need go to the AAA section to create an Enable Password. If needed, these types of users can use the Enable Password to change their access level to Admin.

3.1.1 Creating Accounts

Choose the menu SYSTEM > User Management > User Config to load the following page.

Figure 3-1 User Config Page
TP-LINK Omada TL-SG2008P - Creating Accounts - 1

text_image User Config User ID Username Access Level Operation 1 admin Admin Total: 1

By default, there is a default Admin account in the table. You can click to edit this Admin account but you cannot delete it.

You can create new user accounts. Click and the following window will pop up.

Figure 3-2 Adding Account
TP-LINK Omada TL-SG2008P - Creating Accounts - 2

text_image User Username: (1-16 characters) Access Level: User Password: (6-31 characters) Confirm Password: (6-31 characters) Cancel Create

Follow these steps to create a new user account.

1) Configure the following parameters:

Username Specify a username for the account. It contains 16 characters at most, composed of digits, English letters and symbols. No spaces, question marks and double quotation marks are allowed.

Access Level Select the access level. There are four options provided:

Admin: Admin can edit, modify and view all the settings of different functions.

Operator: Operator can edit, modify and view most of the settings of different functions.

Power User: Power User can edit, modify and view some of the settings of different functions.

User: User can only view the settings without the right to edit or modify.

Password Specify a password for the account. It contains 6–31 alphanumeric characters (case-sensitive) and symbols. No spaces are allowed.

Confirm Retype the password. Password

2) Click Create.

3.1.2 Configuring Enable Password

Choose the menu SECURITY > AAA > Global Config to load the following page.

Figure 3-3 Configure Enable Password
TP-LINK Omada TL-SG2008P - Configuring Enable Password - 1

text_image Enable Admin Enable Admin: ○ Clear Password ● Set Password Password: (1-31 characters) Apply

Follow these steps to configure Enable Password:

1) Select Set Password and specify the enable password in the Password field. It should be a string with 31 characters at most, which can contain only English letters (case-sensitive), digits and 17 kinds of special characters. The special characters are !\$%'()*,-./[]_{!}.

2) Click Apply.

Tips:

The logged-in users can enter the Enable Password on this page to get the administrative privileges.

3.2 Using the CLI

There are four types of user accounts with different access levels: Admin, Operator, Power User and User.

■ There is a default Admin account which cannot be deleted. The default username and password of this account are both admin. You can also create more Admin accounts.
If you create Operator, Power User or User accounts, you need go to the AAA section to create an Enable Password. If needed, these types of users can use the Enable Password to change their access level to Admin.

3.2.1 Creating Accounts

Follow these steps to create an account:

Step 1 configure

Enter global configuration mode.

Step 2 Use the following command to create an account unencrypted or symmetric encrypted.

user name name { privilege admin | operator | power_user | user } password { [0] password | 7 encrypted-password }

name: Enter a user name for users' login. It contains 16 characters at most, composed of digits, English letters and symbols. No spaces, question marks and double quotation marks are allowed.

admin | operator | power_user | user: Specify the access level for the user. Admin can edit, modify and view all the settings of different functions. Operator can edit, modify and view mostly the settings of different functions. Power User can edit, modify and view some of the settings of different functions. User can only view the settings without the right to edit and modify.

0: Specify the encryption type. 0 indicates that the password you entered is unencrypted, and the password is saved to the configuration file unencrypted. By default, the encryption type is 0.

password: Enter a password for users' login. It contains 6–31 alphanumeric characters (case-sensitive) and symbols. No spaces are allowed.

7: Specify the encryption type. 7 indicates that the password you entered is symmetric encrypted, and the password is saved to the configuration file symmetric encrypted.

encrypted-password: Enter a symmetric encrypted password with fixed length, which you can copy from another switch's configuration file. After the encrypted password is configured, you should use the corresponding unencrypted password to reenter this mode.

Use the following command to create an account MD5 encrypted.

user name name { privilege admin | operator | power_user | user } secret { [0] password | 5 encrypted-password }

Create an account whose access level is Admin.

name: Enter a user name for users' login. It contains 16 characters at most, composed of digits, English letters and symbols. No spaces, question marks and double quotation marks are allowed.

admin | operator | power_user | user: Specify the access level for the user. Admin can edit, modify and view all the settings of different functions. Operator can edit, modify and view mostly the settings of different functions. Power User can edit, modify and view some of the settings of different functions. User can only view the settings without the right to edit and modify.

0: Specify the encryption type. 0 indicates that the password you entered is unencrypted, but the password is saved to the configuration file MD5 encrypted. By default, the encryption type is 0.

password: Enter a password for users' login. It contains 6–31 alphanumeric characters (case-sensitive) and symbols. No spaces are allowed.

5: Specify the encryption type. 5 indicates that the password you entered is MD5 encrypted, and the password is saved to the configuration file MD5 encrypted.

encrypted-password: Enter a MD5 encrypted password with fixed length, which you can copy from another switch's configuration file.

Step 3 show user account-list

Verify the information of the current users.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

3.2.2 Configuring Enable Password

Follow these steps to create an account of other type:

Step 1 configure

Enter global configuration mode.

Step 2 Use the following command to create an enable password unencrypted or symmetric encrypted.

enable admin password { [0]password | 7 encrypted-password }

Create an Enable Password. It can change the users' access level to Admin. By default, it is empty.

0: Specify the encryption type. 0 indicates that the password you entered is unencrypted, and the password is saved to the configuration file unencrypted. By default, the encryption type is 0.

password: Enter an enable password. It is a string with 31 characters at most, which can contain only English letters (case-sensitive), digits and 17 kinds of special characters. The special characters are !\$%{}*,-./[]_{}.

7: Specify the encryption type. 7 indicates that the password you entered is symmetric encrypted, and the password is saved to the configuration file symmetric encrypted.

encrypted-password: Enter a symmetric encrypted password with fixed length, which you can copy from another switch's configuration file. After the encrypted password is configured, you should use the corresponding unencrypted password to reenter this mode.

Use the following command to create an enable password unencrypted or MD5 encrypted.

enable admin secret { [0] password | 5 encrypted-password }

Create an Enable Password. It can change the users' access level to Admin. By default, it is empty.

0: Specify the encryption type. 0 indicates that the password you entered is unencrypted, but the password is saved to the configuration file MD5 encrypted. By default, the encryption type is 0.

password: Enter an enable password. It is a string with 31 characters at most, which can contain only English letters (case-sensitive), digits and 17 kinds of special characters. The special characters are !\$%{}*,-./[]_{}.

5: Specify the encryption type. 5 indicates that the password you entered is MD5 encrypted, and the password is saved to the configuration file MD5 encrypted.

encrypted-password: Enter a MD5 encrypted password with fixed length, which you can copy from another switch's configuration file. After the encrypted password is configured, you should use the corresponding unencrypted password to reenter this mode.

Step 3 show user account-list

Verify the information of the current users.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

Tips:

The logged-in users can enter the enable-admin command and the Enable Password to get the administrative privileges.

The following example shows how to create a uesr with the access level of Operator, set the username as user1 and password as 123, and set the enable password as abc123.

Switch#configure

Switch(config)#user name user1 privilege operator password 123

Switch(config)#enable admin password abc123

Switch(config)#show user account-list

IndexUser-NameUser-Type
------------
1user1Operator
2adminAdmin

Switch(config)#end

Switch#copy running-config startup-config

4 System Tools Configurations

With System Tools, you can:

■ Configure the boot file
■ Restore the configuration of the switch
■ Back up the configuration file
■ Upgrade the firmware
■ Configure DHCP Auto Install
■ Reboot the switch
■ Reset the switch

4.1 Using the GUI

4.1.1 Configuring the Boot File

Choose the menu SYSTEM > System Tools > Boot Config to load the following page.

Figure 4-1 Configuring the Boot File
TP-LINK Omada TL-SG2008P - Configuring the Boot File - 1

text_image Boot Table ✓ Unit Current Startup Image Next Startup Image Backup Image Current Startup Config Next Startup Config Backup Config ✓ 1 Image_1.bin Image_1.bin Image_2.bin config1.cfg Config_1.cfg Config_2.cfg Total: 1 1 entry selected. Cancel Apply Restore Image Table UNIT1 ✓ Current Startup Image Image Name: image1.bin Software Version: 3.0.0 Flash Version: 1.3.0 ✓ Next Startup Image Image Name: image1.bin Software Version: 3.0.0 Flash Version: 1.3.0 ✓ Backup Image Image Name: image2.bin Software Version: 3.0.0 Flash Version: 1.3.0

Follow these steps to configure the boot file:

1) In the Boot Table section, select one or more units and configure the relevant parameters.

Unit Displays the number of the unit.
Current Startup ImageDisplays the current startup image.
Next Startup ImageSelect the next startup image. When the switch is powered on, it will try to start up with the next startup image. The next startup image and backup image should not be the same.
Backup ImageSelect the backup image. When the switch fails to start up with the next startup image, it will try to start up with the backup image. The next startup and backup image should not be the same.
Current Startup ConfigDisplays the current startup configuration.
Next Startup ConfigSpecify the next startup configuration. When the switch is powered on, it will try to start up with the next startup configuration. The next startup configuration and backup configuration should not be the same.
Backup ConfigSpecify the backup configuration. When the switch fails to start up with the next startup configuration, it will try to start up with the backup configuration. The next startup and backup configuration should not be the same.

2) Click Apply.

In the Image Table, you can view the information of the current startup image, next startup image and backup image. The displayed information is as follows:

Image Name Displays the name of the image.
Software VersionDisplays the software version of the image.
Flash Version Displays the flash version of the image.

4.1.2 Restoring the Configuration of the Switch

Choose the menu SYSTEM > System Tools > Restore Config to load the following page.

Figure 4-2 Restoring the Configuration of the Switch
TP-LINK Omada TL-SG2008P - Restoring the Configuration of the Switch - 1

text_image Restore Config Restore the configurations using a saved configuration file. Target Unit: UNIT1 Configuration File: Browse □ Reboot the switch to validate the configuration after the restore is complete. Import

Follow these steps to restore the current configuration of the switch:

1) In the Restore Config section, select the unit to be restored.
2) Click Browse and select the desired configuration file to be imported.
3) Choose whether to reboot the switch after restoring is completed. Only after the switch is rebooted will the imported configuration take effect.
4) Click Import to import the configuration file.

TP-LINK Omada TL-SG2008P - Restoring the Configuration of the Switch - 2

Note:

It will take some time to restore the configuration. Please wait without any operation.

4.1.3 Backing up the Configuration File

Choose the menu SYSTEM > System Tools > Backup Config to load the following page.

Figure 4-3 Backing up the Configuration File
TP-LINK Omada TL-SG2008P - Backing up the Configuration File - 1

text_image Backup Config Back up the current startup configuration file. Target Unit: UNIT1 Export

In the Config Backup section, select one unit and click Export to export the configuration file.

TP-LINK Omada TL-SG2008P - Backing up the Configuration File - 2

Note:

It will take some time to export the configuration. Please wait without any operation.

4.1.4 Upgrading the Firmware

Choose the menu SYSTEM > System Tools > Firmware Upgrade to load the following page.

Figure 4-4 Upgrading the Firmware
TP-LINK Omada TL-SG2008P - Upgrading the Firmware - 1

text_image Firmware Upgrade You can upgrade the firmware of the switch using the new upgrade file. Firmware Version: 3.0.0 Build 20171011 Rel.72184(s) Hardware Version: T1600G-28TS 3.0 Image Name: Backup Image Firmware File: Browse □ Reboot the switch using the backup image after upgrading is completed. Upgrade

You can view the current firmware information on this page:

Firmware Version Displays the current firmware version of the system.

Hardware Version Displays the current hardware version of the system.

Image Name Displays the image to upgrade. The operation will only affect the image displayed here.

Follow these steps to upgrade the firmware of the switch:

1) Click Browse and select the proper firmware upgrade file.

2) Choose whether to reboot the switch after upgrading is completed. Only after the switch is rebooted will the new firmware take effect.

3) Click Upgrade to upgrade the system.

TP-LINK Omada TL-SG2008P - Upgrading the Firmware - 2

Note:

• It will take some time to upgrade the switch. Please wait without any operation.
• It is recommended to backup your configuration before upgrading.

4.1.5 Configuring DHCP Auto Install (Only for Certain Devices)

TP-LINK Omada TL-SG2008P - Configuring DHCP Auto Install (Only for Certain Devices) - 1

Note:

DHCP Auto Install is only available on certain devices. To check whether your device supports this feature, refer to the actual web interface. If DHCP Auto Install is available, there is SYSTEM > System Tools > DHCP Auto Install in the menu structure.

This feature is used to download configuration files and images from the TFTP server automatically. It requires a TFTP server and a DHCP server that supports option 67, 125 and 150 on your network. When Auto Install function starts, the switch tries to get

configuration file name, image file path and TFTP server IP address from the DHCP server, and then downloads the new image and configuration file form the TFTP server.

Choose the menu SYSTEM > System Tools > DHCP Auto Install to load the following page.

Figure 4-5 Configuring DHCP Auto Install
TP-LINK Omada TL-SG2008P - Note: - 1

text_image DHCP Auto Install DHCP Auto Install: Enable Auto Install Persistent Mode: Enable Auto Save Mode: Enable Auto Reboot Mode: Enable Auto Install Retry Count: 1 (1-3) Auto Install State: Stopped Apply

Configure the following parameters and click Apply:

DHCP Auto Install Enable or disable DHCP Auto Install.
Auto InstallPersistent ModeEnable or disable Auto Install Persistent Mode. With this mode enabled, the switch will start Auto Install progress once the switch is rebooted.
Auto Save Mode Enable or disable Save Mode. With this mode enabled, the downloaded configuration file will be saved as the startup configuration file, which means that the downloaded configuration will take effect after the next reboot.
Auto Reboot ModeEnable or disable Auto Reboot Mode. With this mode enabled, the switch will reboot automatically once the auto install process is completed.
Auto Install Retry CountSpecify how many times the switch can try to get the configuration file or image file from the TFTP server in one cycle. If the number of tries has reached this limit, the switch will wait for 10 minutes and start to try to get the files again. This process will be repeated until the switch succeeds in getting any of the image file or configuration file, or unless you stop Auto Install manually.
Auto Install State Displays the status of Auto Install process.

For configuration example and detailed instructions, refer to FAQ.

TP-LINK Omada TL-SG2008P - For configuration example and detailed instructions, refer to FAQ. - 1

Note:

  • The switch will obtain a new IP address from the DHCP server during the process of Auto Install. If you want to access to the switch, you should check the new IP address on the DHCP server.
  • If the Auto Install process fails, the switch will restart the process every 10 minutes. You can stop the process manually.

4.1.6 Rebooting the switch

There are two methods to reboot the switch: manually reboot the switch and configure reboot schedule to automatically reboot the switch.

Manually Rebooting the Switch

Choose the menu SYSTEM > System Tools > System Reboot > System Reboot to load the following page.

Figure 4-6 Manually Rebooting the Switch
TP-LINK Omada TL-SG2008P - Manually Rebooting the Switch - 1

text_image System Reboot Target Unit: All Unit Save the current configuration before reboot Reboot

Follow these steps to reboot the switch:

1) In the System Reboot section, select the desired unit.
2) Choose whether to save the current configuration before reboot.
3) Click Reboot.

Configuring Reboot Schedule

Choose the menu SYSTEM > System Tools > System Reboot > Reboot Schedule to load the following page.

Figure 4-7 Configuring the Reboot Schedule
TP-LINK Omada TL-SG2008P - Configuring Reboot Schedule - 1

text_image Reboot Schedule Config Reboot Schedule: Enable Time Interval: 360 minutes (1-43200) Special Time: Month Day Year Time (HH:MM) January 1 2000 Save the current configuration before reboot Apply

Follow these steps to configure the reboot schedule:

1) Enable Reboot Schedule, and select one time schedule for the switch to reboot.

Time Interval

Specify a period of time. The switch will reboot after this period. Valid values are from 1 to 43200 minutes.

To make this schedule recur, you need to click save current configuration or enable the option Save the current configuration before reboot.

Special Time Specify the date and time for the switch to reboot.

Month/Day/Year: Specify the date for the switch to reboot.

Time (HH:MM): Specify the time for the switch to reboot, in the format of HH:MM.

2) Choose whether to save the current configuration before the reboot.
3) Click Apply.

Tips:

To delete the reboot schedule configurations, you can click Delete and the configurations will be empty.

4.1.7 Reseting the Switch

Choose the menu SYSTEM > System Tools > System Reset to load the following page.

Figure 4-8 Reseting the Switch
TP-LINK Omada TL-SG2008P - Reseting the Switch - 1

text_image System Reset Target Unit: All Unit □ Maintain the IP Address Reset

Follow these steps to reset the switch:

1) In the System Reset section, select the desired unit.
2) Choose whether to maintain the IP address of selected unit when resetting.
3) Click Reset.

After reset, all configurations of the switch will be reset to the factory defaults.

4.2 Using the CLI

4.2.1 Configuring the Boot File

Follow these steps to configure the boot file:

Step 1 configure

Enter global configuration mode.

Step 2boot application filename { image1 | image2 } { startup | backup }Specify the configuration of the boot file. By default, image1.bin is the startup image and image2.bin is the backup image.image1 | image2: Select the image file to be configured.startup | backup: Select the property of the image file.
Step 3boot config filename { config1 | config2 } { startup | backup }Specify the configuration of the boot file. By default, config1.cfg is the startup configuration file and config2.cfg is the backup configuration file.config1 | config2: Select the configuration file to be configured.startup | backup: Specify the property of the configuration file.
Step 4 show bootVerify the boot configuration of the system.
Step 5 endReturn to privileged EXEC mode.
Step 6 copy running-config startup-configSave the settings in the configuration file.

The following example shows how to set the next startup image as image1, the backup image as image2, the next startup configuration file as config1 and the backup configuration file as config2.

Switch#configure

Switch(config)#boot application filename image1 startup

Switch(config)#boot application filename image2 backup

Switch(config)#boot config filename config1 startup

Switch(config)#boot config filename config2 backup

Switch(config)#show boot

Boot config:

Current Startup Image - image2.bin

Next Startup Image - image1.bin

Backup Image - image2.bin

Current Startup Config - config2.cfg

Next Startup Config - config1.cfg

Backup Config - config2.cfg

Switch(config)#end

Switch#copy running-config startup-config

4.2.2 Restoring the Configuration of the Switch

Follow these steps to restore the configuration of the switch:

Step 1 enable

Enter privileged mode.

Step 2 copy tftp startup-config ip-address

ip-addr filename name

Download the configuration file to the switch from TFTP server.

ip-addr: Specify the IP address of the TFTP server. Both IPv4 and IPv6 addresses are supported.

name: Specify the name of the configuration file to be downloaded.

TP-LINK Omada TL-SG2008P - Restoring the Configuration of the Switch - 1

Note:

It will take some time to restore the configuration. Please wait without any operation.

The following example shows how to restore the configuration file named file1 from the TFTP server with IP address 192.168.0.100.

Switch>enable

Switch#copy tftp startup-config ip-address 192.168.0.100 filename file1

Start to load user config file...

Operation OK! Now rebooting system...

4.2.3 Backing up the Configuration File

Follow these steps to back up the current configuration of the switch in a file:

Step 1 enable

Enter privileged mode.

Step 2 copy startup-config tftp ip-address

ip-addr filename name

Back up the configuration file to TFTP server.

ip-addr: Specify the IP address of the TFTP server. Both IPv4 and IPv6 addresses are supported.

name: Specify the name of the configuration file to be saved.

The following example shows how to backup the configuration file named file2 to TFTP server with IP address 192.168.0.100.

Switch>enable

Switch#copy startup-config tftp ip-address 192.168.0.100 filename file2

Start to backup user config file...

Backup user config file OK.

4.2.4 Upgrading the Firmware

Follow these steps to upgrade the firmware:

Step 1 enable

Enter privileged mode.

Step 2 firmware upgrade tftp ip-address

ip-addr filename name

Upgrade the switch's backup image via TFTP server. To boot up with the new firmware, you need to choose to reboot the switch with the backup image.

ip-addr: Specify the IP address of the TFTP server. Both IPv4 and IPv6 addresses are supported.

name: Specify the name of the desired firmware file.

Step 3 Enter Y to continue and then enter Y to reboot the switch with the backup image.

The following example shows how to upgrade the firmware using the configuration file named file3.bin. The TFTP server is 190.168.0.100.

Switch>enable

Switch#firmware upgrade tftp ip-address 192.168.0.100 filename file3.bin

It will only upgrade the backup image. Continue? (Y/N):Y

Operation OK!

Reboot with the backup image? (Y/N): Y

4.2.5 Configuring DHCP Auto Install (Only for Certain Devices)

TP-LINK Omada TL-SG2008P - Configuring DHCP Auto Install (Only for Certain Devices) - 1

Note:

DHCP Auto Install is only available on certain devices. To check whether your device supports this feature, refer to the actual web interface. If DHCP Auto Install is available, there is SYSTEM > System Tools > DHCP Auto Install in the menu structure.

This feature is used to download configuration files and images from the TFTP server automatically. It requires a TFTP server and a DHCP server that supports option 67, 125 and 150 on your network. When Auto Install function starts, the switch tries to get

configuration file name, image file path and TFTP server IP address from the DHCP server, and then downloads the new image and configuration file form the TFTP server.

Follow these steps to configure the DHCP Auto Install.

Step 1 configure

Enter global configuration mode.

Step 2 boot autoinstall persistent-mode

Enable the auto install persistent mode. After saving configuration, the switch will start the Auto Install function automatically during next reboot process.

Step 3 boot autoinstall auto-save

Enable the auto save mode and the switch will save the configuration file downloaded as startup configuration file automatically.

Step 4 boot autoinstall auto-reboot

Enable the auto reboot mode and the switch will reboot automatically after the auto install process is completed successfully.

Step 5 boot autoinstall retry-count

count

Specify the auto install retry count which ranges from 1 to 3. The default value is 1.

Step 6 boot autoinstall start

Start the Auto Install process and the switch will download the configuration file and the backup image automatically.

Step 7 end

Return to privileged EXEC mode.

Step 8 copy running-config startup-config

Save the settings in the configuration file.

TP-LINK Omada TL-SG2008P - Step 8 copy running-config startup-config - 1

Note:

  • The switch will obtain a new IP address from the DHCP server during the process of Auto Install. If you want to access to the switch, you should check the new IP address on the DHCP server.
  • If the Auto Install process fails, the switch will restart the process every 10 minutes. You can stop the process manually.

The following example shows how to configure the Auto Install function.

Switch#configure

Switch(config)#boot autoinstall persistent-mode

Switch(config)#boot autoinstall auto-save

Switch(config)#boot autoinstall auto-reboot

Switch(config)#boot autoinstall retry-count 2

Switch(config)#show boot autoinstall

Auto Insatll Mode......Stop

Auto Insatll Persistent Mode......Enabled

Auto Save Mode......Enabled

Auto Reboot Mode......Enabled

Auto Insatll Retry Count......2

Auto Insatll sate......Stopped

4.2.6 Rebooting the Switch

Manually Rebooting the Switch

Follow these steps to reboot the switch:

Step 1 enable

Enter privileged mode.

Step 2 reboot

Reboot the switch.

Configuring Reboot Schedule

Follow these steps to configure the reboot schedule:

Step 1 configure

Enter global configuration mode.

Step 2 Use the following command to set the interval of reboot:

reboot-schedule in interval [ save_before_reboot ]

(Optional) Specify the reboot schedule.

interval: Specify a period of time. The switch will reboot after this period. The valid values are from 1 to 43200 minutes.

save_before_reboot: Save the configuration file before the switch reboots. To make this schedule recur, you can add this part to the command.

Use the following command to set the special time of reboot:

reboot-schedule at time [date] [save_before_reboot]

(Optional) Specify the reboot schedule.

time: Specify the time for the switch to reboot, in the format of HH:MM.

date: Specify the date for the switch to reboot, in the format of DD/MM/YYYY. The date should be within 30 days.

save_before_reboot: Save the configuration file before the switch reboots.

If no date is specified, the switch will reboot according to the time you have set. If the time you set is later than the time that this command is executed, the switch will reboot later the same day; otherwise the switch will reboot the next day.

Step 3 end

Return to privileged EXEC mode.

Step 4 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to set the switch to reboot at 12:00 on 15/08/2017.

Switch#configure

Switch(config)#reboot-schedule at 12:00 15/08/2017 save_before_reboot

Reboot system at 15/08/2017 12:00. Continue? (Y/N): Y

Reboot Schedule Settings

Reboot schedule at 2017-08-15 12:00 (in 25582 minutes)

Save before reboot: Yes

Switch(config)#end

Switch#copy running-config startup-config

4.2.7 Reseting the Switch

Follow these steps to reset the switch:

Step 1 enable

Enter privileged mode.

Step 2 reset [except-ip]

Reset the switch, and all configurations of the switch will be reset to the factory defaults.

except-ip: To maintain the IP address when resetting the switch, add this part to the command.

Follow these steps to disable the reset function of console port or reset button:

Step 1 configure

Enter global configuration mode.

Step 2 service reset-disable

Disable the reset function of console port or reset button. By default, the reset function is enabled.

Note: use the no service reset-disable command to enable the reset function of console port.

5 EEE Configuration

Choose the menu SYSTEM > EEE to load the following page.

Figure 5-1 Configuring EEE
TP-LINK Omada TL-SG2008P - EEE Configuration - 1

text_image EEE Config UNIT1 LAGS Port Status ✓ 1/0/1 Disabled □ 1/0/2 Disabled □ 1/0/3 Disabled □ 1/0/4 Disabled □ 1/0/5 Disabled □ 1/0/6 Disabled □ 1/0/7 Disabled □ 1/0/8 Disabled □ 1/0/9 Disabled □ 1/0/10 Disabled Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure EEE:

1) In the EEE Config section, select one or more ports to be configured.
2) Enable or disable EEE on the selected port(s).
3) Click Apply.

5.1 Using the CLI

Follow these steps to configure EEE:

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list } Enter interface configuration mode.

Step 3 eee

Enable EEE on the port.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable the EEE feature on port 1/0/1.

Switch#config

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#eee

Switch(config-if)#show interface eee

Port EEE status

Gi1/0/1 Enable

Gi1/0/2 Disable

...

Switch(config-if)#end

Switch#copy running-config startup-config

6 PoE Configurations (Only for Certain Devices)

TP-LINK Omada TL-SG2008P - PoE Configurations (Only for Certain Devices) - 1

Note:

PoE configuration is only available on certain devices. To check whether your device supports this feature, refer to the actual web interface. If PoE configuration is available, there is SYSTEM > PoE in the menu structure.

With the PoE feature, you can:

■ Configure the PoE parameters manually
■ Configure the PoE parameters using the profile

You can configure the PoE parameters one by one via configuring the PoE parameters manually. You can also set a profile with the desired parameters and bind the profile to the corresponding ports to quickly configure the PoE parameters.

6.1 Using the GUI

6.1.1 Configuring the PoE Parameters Manually

Choose the menu SYSTEM > PoE > PoE Config to load the following page.

Figure 6-1 Configuring PoE Parameters Manually
TP-LINK Omada TL-SG2008P - Configuring the PoE Parameters Manually - 1

text_image PoE Config Unit System Power Limit (W) System Power Consumption (W) System Power Remain (W)Operation Unit1 384.0 0.0 384.0 Total: 1 Port Config UNIT1 □ Port PoE Status PoE Priority Power Limit Power Limit Value (0.1-30.0 W) Time Range PoE Profile Power (W) Curre ✓ 1 Enabled Low Class4 30 No Limit None 0 □ 2 Enabled Low Class4 30 No Limit None 0 □ 3 Enabled Low Class4 30 No Limit None 0 □ 4 Enabled Low Class4 30 No Limit None 0 □ 5 Enabled Low Class4 30 No Limit None 0 □ 6 Enabled Low Class4 30 No Limit None 0 □ 7 Enabled Low Class4 30 No Limit None 0 □ 8 Enabled Low Class4 30 No Limit None 0 □ 9 Enabled Low Class4 30 No Limit None 0 □ 10 Enabled Low Class4 30 No Limit None 0 Total: 24 1 entry selected. Cancel Apply

Follow these steps to configure the basic PoE parameters:

1) In the PoE Config section, you can view the current PoE parameters.

System Power Limit (W)Displays the maximum power the PoE switch can supply.
System Power Consumption (W)Displays the real-time system power consumption of the PoE switch.
System Power Remain (W)Displays the real-time system remaining power of the PoE switch.

In addition, you can click and configure the System Power Limit. Click Apply.

Figure 6-2 Configuring System Power Limit
TP-LINK Omada TL-SG2008P - Configuring the PoE Parameters Manually - 2

text_image PoE Config Unit: 1 System Power Limit: 384 W (1-384) Cancel Save

Unit Displays the unit number.

System Power Limit Specify the maximum power the PoE switch can supply.

2) In the Port Config section, select the port you want to configure and specify the parameters. Click Apply.

PoE Status Enable or disable the PoE function for the corresponding port. The port can supply power to the PD when its status is enable.
PoE PrioritySelect the priority level for the corresponding port. When the supply power exceeds the system power limit, the switch will power off PDs on low-priority ports to ensure stable running of other PDs.
Power Limit Specify the maximum power the corresponding port can supply. The following options are provided:
Auto: The switch will allocate a value as the maximum power that the port can supply automatically.
Class1: The maximum power that the port can supply is 4 W.
Class2: The maximum power that the port can supply is 7 W.
Class3: The maximum power that the port can supply is 15.4 W.
Class4: The maximum power that the port can supply is 30 W.
Manual: You can enter a value manually.
Power Limit Value (0.1–30.0 W)If you select Manual as Power Limit mode, specify a maximum power supply value in this field.
If you select Class1 to Class4 as Power Limit mode, you can view the maximum power supply value in this field.
Time RangeSelect a time range, then the port will supply power only during the time range. For how to create a time range, refer to Time Range Configuration.
PoE ProfileA quick configuration method for the corresponding ports. If one profile is selected, you will not be able to modify PoE status, PoE priority or power limit manually. For how to create a profile, refer to Configuring the PoE Parameters Using the Profile.
Power (W) Displays the port's real-time power supply.
Current (mA) Displays the port's real-time current.
Voltage (V) Displays the port's real-time voltage.
PD Class Displays the class the linked PD belongs to.
Power Status Displays the port's real-time power status.

6.1.2 Configuring the PoE Parameters Using the Profile

■ Creating a PoE Profile

Choose the menu SYSTEM > PoE > PoE Profile and click + Add to load the following page.

Figure 6-3 Creating a PoE Profile
TP-LINK Omada TL-SG2008P - Configuring the PoE Parameters Using the Profile - 1

text_image PoE Profile Config Profile Name: (1-31 characters) PoE Status: Enable Disable PoE Priority: Low Power Limit: Auto Cancel Create

Follow these steps to create a PoE profile:

1) In the Create PoE Profile section, specify the desired configurations of the profile.

Profile Name Specify a name for the PoE profile.
PoE Status Specify the PoE status for the PoE profile.
PoE PrioritySpecify the priority level for the PoE profile. The following options are provided:High, Middle and Low. When the supply power exceeds the system power limit, the switch will power off PDs on low-priority ports to ensure stable running of other PDs.
Power LimitSpecify the maximum power the port can supply for the PoE profile. The following options are provided:Auto: The switch will allocate a value as the maximum power that the port can supply automatically.Class1 (4 W): The maximum power that the port can supply is 4 W.Class2 (7 W): The maximum power that the port can supply is 7 W.Class3 (15.4 W): The maximum power that the port can supply is 15.4 W.Class4 (30 W): The maximum power that the port can supply is 30 W.Manual: Enter a value manually.

2) Click Create.

■ Binding the Profile to the Corresponding Ports

Choose the menu SYSTEM > PoE > PoE Config to load the following page.

Figure 6-4 Binding the Profile to the Corresponding Ports
TP-LINK Omada TL-SG2008P - ■ Binding the Profile to the Corresponding Ports - 1

text_image PoE Config Unit System Power Limit (W) System Power Consumption (W) System Power Remain (W)Operation Unit1 384.0 0.0 384.0 Total: 1 Port Config UNIT1 □ Port PoE Status PoE Priority Power Limit Power Limit Value (0.1-30.0 W) Time Range PoE Profile Power (W) Curre ✓ 1 Enabled Low Class4 30 No Limit None 0 □ 2 Enabled Low Class4 30 No Limit None 0 □ 3 Enabled Low.Class4 30 No Limit None 0 □ 4 Enabled Low.Class4 30 No Limit None 0 □ 5 Enabled Low.Class4 30 No Limit None 0 □ 6 Enabled Low.Class4 30 No Limit None 0 □ 7 Enabled Low.Class4 30 No Limit None 0 □ 8 Enabled Low.Class4 30 No Limit None 0 □ 9 Enabled Low.Class4 30 No Limit None 0 □ 10 Enabled Low.Class4 30 No Limit None 0 Total: 24 1 entry selected. Cancel Apply

Follow these steps to bind the profile to the corresponding ports:

1) In the PoE Config section, you can view the current PoE parameters.

System Power Limit (W)Displays the maximum power the PoE switch can supply.
System Power Consumption (W)Displays the real-time system power consumption of the PoE switch.
System Power Remain (W)Displays the real-time system remaining power of the PoE switch.

In addition, you can click and configure the System Power Limit. Click Apply.

Figure 6-5 Configuring System Power Limit
TP-LINK Omada TL-SG2008P - ■ Binding the Profile to the Corresponding Ports - 2

text_image PoE Config Unit: 1 System Power Limit: 384 W (1-384) Cancel Save

Unit Displays the unit number.

System Power Limit Specify the maximum power the PoE switch can supply.

2) In the Port Config section, select one or more ports and configure the following two parameters: Time Range and PoE Profile. Click Apply and the PoE parameters of the selected PoE Profile, such as PoE Status and PoE Priority, will be displayed in the table.

PoE Status Displays the PoE function for the corresponding port. The port can supply power to the PD when its status is enable.
PoE PriorityDisplays the priority level for the corresponding port. When the supply power exceeds the system power limit, the switch will power off PDs on low-priority ports to ensure stable running of other PDs.
Power Limit Displays the maximum power the corresponding port can supply.
Power Limit Value (0.1–30.0 W)Displays the power limit value.
Time RangeSelect a time range, then the port will supply power only during the time range. For how to create a time range, refer to Time Range Configuration.
PoE ProfileSelect the PoE profile for the desired port. If one profile is selected, you will not be able to modify PoE status, PoE priority or power limit manually.
Power (W) Displays the port's real-time power supply.
Current (mA) Displays the port's real-time current.
Voltage (V) Displays the port's real-time voltage.
PD Class Displays the class the linked PD belongs to.
Power Status Displays the port's real-time power status.

6.2 Using the CLI

6.2.1 Configuring the PoE Parameters Manually

Follow these steps to configure the basic PoE parameters:

Step 1 configureEnter global configuration mode.
Step 2 power inline consumption power-limitSpecify the maximum power the PoE switch can supply globally.power-limit: Specify the maximum power the PoE switch can supply.
Step 3 interface { fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list }Enter Interface Configuration mode.port: Specify the Ethernet port number, for example 1/0/1.port-list: Specify the list of Ethernet ports, for example 1/0/1-3, 1/0/5.
Step 4 power inline supply { enable | disable }Specify the PoE status for the corresponding port.enable | disable: Enable or disable the PoE function. By default, it is enable.
Step 5 power inline priority { low | middle | high }Specify the PoE priority for the corresponding port.low | middle | high: Select the priority level for the corresponding port. When the supply power exceeds the system power limit, the switch will power off PDs on low-priority ports to ensure stable running of other PDs. The default setting is low.
Step 6 power inline consumption { power-limit | auto | class1 | class2 | class3 | class4 }Specify the maximum power the corresponding port can supply.power-limit | auto | class1 | class2 | class3 | class4: Select or enter the maximum power the corresponding port can supply. The following options are provided: Auto represents that the switch will allocate the maximum power that the port can supply automatically. Class1 represents 4 W, Class2 represents 7W, Class3 represents 15.4 W and Class4 represents 30 W, or you can enter a value manually. The value ranges from 1 to 300. It is in the unit of 0.1 watt. For instance, if you want to configure the maximum power as 5 W, you should enter 50. By default, it is Class4.
Step 7 power inline time-rangenameSpecify a time range for the port. Then the port will supply power only during the time range.For how to create a time range, refer to Time Range Configuration.name: Specify the name of the time range.
Step 8 show power inlineVerify the global PoE information of the system.
Step 9 show power inline configuration interface [ fastEthernet { port | port-list } | gigabitEthernet { port | port-list } | ten-gigabitEthernet { port | port-list }]Verify the PoE configuration of the corresponding port.port: Specify the Ethernet port number, for example 1/0/1.port-list: Specify the list of Ethernet ports, in the format of 1/0/1-3, 1/0/5.
Step 10 show power inline information interface [ fastEthernet { port | port-list } | gigabitEthernet { port | port-list } | ten-gigabitEthernet { port | port-list } ]Verify the real-time PoE status of the corresponding port.port: Specify the Ethernet port number, for example 1/0/1.port-list: Specify the list of Ethernet ports, in the format of 1/0/1-3, 1/0/5.

Step 11 end

Return to privileged EXEC mode.

Step 12 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to set the system power limit as 160 W. Set the priority as middle and set the power limit as class3 for the port 1/0/5.

Switch#configure

Switch(config)#power inline consumption 160

Switch(config)#interface gigabitEthernet 1/0/5

Switch(config-if)#power inline supply enable

Switch(config-if)#power inline priority middle

Switch(config-if)#power inline consumption class3

Switch(config-if)#show power inline

System Power Limit: 160.0w

System Power Consumption: 0.0w

System Power Remain: 160.0w

Switch(config-if)#show power inline configuration interface gigabitEthernet 1/0/5

InterfacePoE-StatusPoE-PrioPower-Limit(w)Time-RangePoE-Profile
Gi1/0/5EnableMiddleClass3No LimitNone

Switch(config-if)#show power inline information interface gigabitEthernet 1/0/5

InterfacePower(w)Current(mA)Voltage(v)PD-ClassPower-Status
Gi1/0/51.32653.5Class 2ON

Switch(config-if)#end

Switch#copy running-config startup-config

6.2.2 Configuring the PoE Parameters Using the Profile

Follow these steps to configure the PoE profile:

Step 1 configure

Enter global configuration mode.

Step 2 power inline consumption power-limit

Specify the maximum power the PoE switch can supply globally.

power-limit: Specify the maximum power the PoE switch can supply.

Step 3 power profile name [supply { enable | disable } [priority { low | middle | high } [consumption { power-limit | auto | class1 | class2 | class3 | class4}]]]

Create a PoE profile for the switch. In a profile, the PoE status, PoE priority and power limit are configured. You can bind a profile to the corresponding port to quickly configure the PoE function.

name: Specify a name for the PoE profile. It ranges from 1 to 16 characters. If the name contains spaces, enclose the name in double quotes.

enable | disable: Specify the PoE status for the profile. By default, it is enable.

low | middle | high: Select the priority level for the profile. When the supply power exceeds the system power limit, the switch will power off PDs on low-priority ports to ensure stable running of other PDs.

power-limit | auto | class1 | class2 | class3 | class4: Select or enter the maximum power the corresponding port can supply. The following options are provided: Auto represents that the switch will assign a value of maximum power automatically. Class1 represents 4W, Class2 represents 7W, Class3 represents 15.4W and Class4 represents 30W or you can enter a value manually. The value ranges from 1 to 300. It is in the unit of 0.1 watt. For instance, if you want to configure the maximum power as 5W, you should enter 50.

Step 4 interface { fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list }

Enter Interface Configuration mode.

port: Specify the Ethernet port number, for example 1/0/1.

port-list: Specify the list of Ethernet ports, for example 1/0/1-3, 1/0/5.

Step 5 power inline profile name
Bind a PoE profile to the desired port. If one profile is selected, you will not be able to modify PoE status, PoE priority or power limit manually.
name: Specify the name of the PoE profile. If the name contains spaces, enclose the name in double quotes.
Step 6 power inline time-range name
Specify a time range for the port. Then the port will supply power only during the time range. For how to create a time range, refer to Time Range Configuration.
name: Specify the name of the time range.
Step 7 show power profile
Verify the defined PoE profile.
Step 8 show power inline configuration interface [ fastEthernet { port | port-list } | gigabitEthernet { port | port-list }]
Verify the PoE configuration of the corresponding port.
port: Specify the Ethernet port number, for example 1/0/1.
port-list: Specify the list of Ethernet ports, in the format of 1/0/1-3, 1/0/5.
Step 9 show power inline information interface [ fastEthernet { port | port-list } | gigabitEthernet { port | port-list }]
Verify the real-time PoE status of the corresponding port.
port: Specify the Ethernet port number, for example 1/0/1.
port-list: Specify the list of Ethernet ports, in the format of 1/0/1-3, 1/0/5.
Step 10 end
Return to privileged EXEC mode.
Step 11 copy running-config startup-config
Save the settings in the configuration file.

The following example shows how to create a profile named profile1 and bind the profile to the port 1/0/6.

Switch#configure

Switch(config)#power profile profile1 supply enable priority middle consumption class2

Switch(config)#show power profile

Index Name Status Priority Power-Limit(w)

1 profile1 Enable Middle Class2

Switch(config)#interface gigabitEthernet 1/0/6

Switch(config-if)#power inline profile profile1

Switch(config-if)#show power inline configuration interface gigabitEthernet 1/0/6

InterfacePoE-StatusPoE-PrioPower-Limit(w)Time-RangePoE-Profile
Gi1/0/6EnableMiddleClass2No Limitprofile1

Switch(config-if)#end

Switch#copy running-config startup-config

7

SDM Template Configuration

7.1 Using the GUI

Choose the menu SYSTEM > SDM Template to load the following page.

Figure 7-1 Configuring SDM Template
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image iDM Template Config Current Template: Default Next Template: Default Select Next Template: Default Apply SDM Template Table SDM Template IP ACL Rules MAC ACL Rules Combined ACL Rules IPv6 ACL Rules IPv4 Source Guard Entries IPv6 Source Guard Entries Default 100 80 50 0 253 0 EnterpriseV4 120 84 50 0 253 0 EnterpriseV6 32 32 0 120 0 183 Total: 3

In SDM Template Config section, select one template and click Apply. The setting will be effective after the switch is rebooted.

Current Template Displays the template currently in effect.
Next Template Displays the template that will be effective after the reboot.
Select Next TemplateSelect the template that will be effective after the next reboot.Default: Select the template of default. It gives balance to the IP ACL rules and MAC ACL rules.EnterpriseV4: Select the template of enterpriseV4. It maximizes system resources for IP ACL rules and MAC ACL rules.EnterpriseV6: Select the template of enterpriseV6. It allocates resources to IPv6 ACL rules.

The Template Table displays the resources allocation of each template.

SDM Template Displays the name of the templates.
IP ACL RulesDisplays the number of IP ACL Rules including Layer 3 ACL Rules and Layer 4 ACL Rules.
MAC ACL Rules Displays the number of Layer 2 ACL Rules.
Combined ACL RulesDisplays the number of combined ACL rules.
IPv6 ACL Rules Displays the number of IPv6 ACL rules.
IPv4 Source Guard EntriesDisplays the number of IPv4 source guard entries.
IPv6 Source Guard EntriesDisplays the number of IPv6 source guard entries.
Packet Content ACL RulesDisplays the number of packet content ACL rules.Note: Packet Content ACL Rules is only available for certain devices.

7.2 Using the CLI

Follow these steps to configure the SDM template:

Step 1 configure
Enter global configuration mode.
Step 2show sdm prefer { used | default | enterpriseV4 | enterpriseV6 }View the template table. It will help you determine which template is suitable for your network.used: Displays the resource allocation of the current template.default: Displays the resource allocation of the default template.enterpriseV4: Displays the resource allocation of the enterpriseV4 template.enterpriseV6: Displays the resource allocation of the enterpriseV6 template.
Step 3 sdm prefer { default | enterpriseV4 | enterpriseV6 }Select the template that will be effective after the switch is rebooted.default: Select the template of default. It gives balance to the IP ACL rules, MAC ACL rules and ARP detection entries.enterpriseV4: Select the template of enterpriseV4. It maximizes system resources for IP ACL rules and MAC ACL rules.enterpriseV6: Select the template of enterpriseV4. It allocates resources to IPv6 ACL rules.
Step 4 endReturn to privileged EXEC mode.
Step 5 copy running-config startup-configSave the settings in the configuration file.

The following example shows how to set the SDM template as enterpriseV4.

Switch#config

Switch(config)#show sdm prefer enterpriseV4

"enterpriseV4" template:

number of IP ACL Rules : 120

number of MAC ACL Rules : 84

number of IPV6 ACL Rules : 0

number of IPV4 Source Guard Entries : 253

number of IPV6 Source Guard Entries : 0

Switch(config)#sdm prefer enterpriseV4

Switch to "enterpriseV4" tempale.

Changes to the running SDM preferences have been stored, but cannot take effect until reboot the switch.

Switch(config)#end

Switch#copy running-config startup-config

8

Time Range Configuration

To complete Time Range configuration, follow these steps:

1) Add time range entries.
2) Configure Holiday time range.

8.1 Using the GUI

8.1.1 Adding Time Range Entries

Choose the menu SYSTEM > Time Range > Time Range Config and click + Add to load the following page.

Figure 8-1 Configuring Time Range
TP-LINK Omada TL-SG2008P - Adding Time Range Entries - 1

text_image Time-Range Config Name: (1-16 characters) Holiday: Exclude Include Period Time Config ID Date Day Time Operation No entries in this table. Total: 0 Discard Create

Follow these steps to add time range entries:

1) In the Time-Range Config section, specify a name for the entry and select the Holiday mode.

Name Specify a name for the entry.

Holiday Select to include or exclude the holiday in the time range.

Exclude: The time range will not take effect on holiday.

Include: The time range will not be affected by holiday.

To configure Holiday, refer to Configuring Holiday.

2) In the Period Time Config section, click and the following window will pop up.

Figure 8-2 Adding Period Time
TP-LINK Omada TL-SG2008P - Adding Time Range Entries - 2

text_image Period Time Config Date From Month: Day: Year: January 1 2000 To Month: Day: Year: January 1 2000 Time From: (Format: HH:MM) To: (Format: HH:MM) Day of Week Mon Tue Wed Thu Fri Sat Sun Cancel Create

Configure the following parameters and click Create:

Date Specify the start date and end date of this time range.

Time Specify the start time and end time of a day.

Day of Week Select days of a week as the period of this time range.

3) Similarly, you can add more entries of period time according to your needs. The final period time is the sum of all the periods in the table. Click Create.

Figure 8-3 View Configuration Result
TP-LINK Omada TL-SG2008P - Adding Time Range Entries - 3

text_image Time-Range Config Name: work_time (1-16 characters) Holiday: Exclude Include Period Time Config ID Date Day Time Operation 1 January 1, 2017 - November 1, 2017 Mon,Tue,Wed,Thu,Fri 08:00 - 20:00 Total: 1 Discard Create

8.1.2 Configuring Holiday

Choose the menu SYSTEM > Time Range > Holiday Config and click + Add to load the following page.

Figure 8-1 Configuring Holiday
TP-LINK Omada TL-SG2008P - Configuring Holiday - 1

text_image Holiday Config Holiday Name: (1-31 characters) Start Date Month Day January 01 End Date Month Day January 01 Cancel Create

Configure the following parameters and click Create to add a Holiday entry.

Holiday Name Specify a name for the entry.

Start Date Specify the start date of the Holiday time range.

End Date Specify the end date of the Holiday time range.

Similarly, you can add more Holiday entries. The final Holiday time range is the sum of all the entries.

8.2 Using the CLI

8.2.1 Adding Time Range Entries

Follow these steps to add time range entries:

Step 1 configure

Enter global configuration mode.

Step 2 time-range

name

Create a time-range entry.

name: Specify a name for the entry.

Step 3 holiday { exclude | include }

Include or exclude the holiday in the time range.

exclude: The time range will not take effect on holiday.

include: The time range will not be affected by holiday.

To configure Holiday, refer to Configuring Holiday.

Step 4 absolute from

start-date to end-date

Specify the start date and end date of this time range.

start-date: Specify the start date in the format MM/DD/YYYY.

end-date: Specify the end date in the format MM/DD/YYYY.

Step 5 periodic start

start-time end end-time day-of-the-week week-day

Specify days of a week as the period of this time range.

start-time: Specify the start end time of a day in the format HH:MM.

end-time: Specify the end time and end time of a day in the format HH:MM.

week-day: Specify the days of week in the format of 1-3, 7. The numbers 1-7 respectively represent Monday, Tuesday, Wednesday, Thursday, Friday, Saturday and Sunday.

Step 6 show time-range

View the configuration of Time Range.

Step 7 end

Return to privileged EXEC mode.

Step 8 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to create a time range entry and set the name as time1, holiday mode as exclude, absolute time as 10/01/2017 to 10/31/2017 and periodic time as 8:00 to 20:00 on every Monday and Tuesday:

Switch#config

Switch(config)#time-range time1

Switch(config-time-range)#holiday exclude

Switch(config-time-range)#absolute from 10/01/2017 to 10/31/2017

Switch(config-time-range)#periodic start 08:00 end 20:00 day-of-the-week 1,2

Switch(config-time-range)#show time-range

Time-range entry: 12 (Inactive)

Time-range entry: time1 (Inactive)

holiday: exclude

number of time slice: 1

01 - 10/01/2017 to 10/31/2017

- 08:00 to 20:00 on 1,2

Switch(config-time-range)#end

Switch#copy running-config startup-config

8.2.2 Configuring Holiday

Follow these steps to configure Holiday time range:

Step 1 configure

Enter global configuration mode.

Step 2 holiday name start-date start-date end-date end-date

Create a holiday entry.

name: Specify a name for the entry.

start-date : Specify the start date in the format MM/DD.

end-date: Specify the end date in the format MM/DD.

Step 3 show holiday

View the configuration of Holiday.

Step 4 end

Return to privileged EXEC mode.

Step 8 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to create a holiday entry and set the entry name as holiday1 and set start date and end date as 07/01 and 09/01:

Switch#config

Switch(config)#holiday holiday1 start-date 07/01 end-date 09/01

Switch(config)#show holiday

Index Holiday Name Start-End

1 holiday1 07.01-09.01

Switch(config)#end

Switch#copy running-config startup-config

9

Controller Settings (Only for Certain Devices)

TP-LINK Omada TL-SG2008P - Controller Settings (Only for Certain Devices) - 1

Note:

Controller Settings is only available on certain devices. To check whether your device supports this feature, refer to the actual web interface. If Controller Settings is available, there is SYSTEM >Controller Settings in the menu structure.

This feature prepares the switch for Omada SDN Controller Management in either of the following scenarios:

If you are using Omada Cloud-Based Controller, enable Cloud-Based Controller Management on this page, then you can further add your devices to your Omada Cloud-Based Controller.
If your switch and Omada SDN Controller are located on the same subnet, the controller can discover and manage the switch without any controller settings. Otherwise, you need to inform the switch of the controller's URL/IP address.

9.1 Using the GUI

9.1.1 Enabling Cloud-Based Controller Management

Choose the menu SYSTEM > Controller Settings to load the following page. In the Cloud-Based Controller Management section, enable Cloud-Based Controller Management and click Apply. After you add the switch to your Omada Cloud-Based Controller, you can check the connection status on this page.

Figure 9-1 Enabling Cloud-Based Controller Management
TP-LINK Omada TL-SG2008P - Enabling Cloud-Based Controller Management - 1

text_image Cloud-Based Controller Management Connection Status: Disabled Cloud-Based Controller Management: Enable Notes: To enjoy centralized management on Omada Cloud-Based Controller, enable Cloud-Based Controller Management and add the device to the controller via its serial number. You can disable this feature if you do not need to manage the device with the Omada Cloud-Based Controller. Controller Inform URL Inform URL/IP Address: Notes: Enter the inform URL or IP address of your controller to tell the device where to discover the controller. This feature is commonly used for the device to be managed by the controller in Layer 3 deployments. Apply

9.1.2 Configuring Controller Inform URL

Choose the menu SYSTEM > Controller Settings to load the following page. In the Controller Inform URL section, inform the switch of the controller's URL/IP address, and click Apply.

Figure 9-1 Configuring Controller Inform URL
TP-LINK Omada TL-SG2008P - Configuring Controller Inform URL - 1

text_image Cloud-Based Controller Management Connection Status: Disabled Cloud-Based Controller Management: Enable Notes: To enjoy centralized management on Omada Cloud-Based Controller, enable Cloud-Based Controller Management and add the device to the controller via its serial number. You can disable this feature if you do not need to manage the device with the Omada Cloud-Based Controller. Controller Inform URL Inform URL/IP Address: Notes: Enter the inform URL or IP address of your controller to tell the device where to discover the controller. This feature is commonly used for the device to be managed by the controller in Layer 3 deployments. Apply

9.2 Using the CLI

9.2.1 Enabling Cloud-Based Controller Management

Follow these steps to enable cloud-based controller management:

Step 1 configure

Enter global configuration mode.

Step 2 controller cloud-based

Enable cloud-based controller management.

Step 3 show controller

View the controller settings and status.

9.2.2 Configuring Controller Inform URL

Follow these steps to configure controller inform URL:

Step 1 configure

Enter global configuration mode.

Step 2 controller inform-url [ controller-url | controller-ip ]

Inform the switch of the controller's URL/IP address.

Step 3 show controller

View the controller settings and status.

The following example shows how to inform the switch of the controller whose IP address is 192.168.1.1:

Switch#config

Switch(config)#controller inform-url 192.168.1.1

Switch(config)#show controller

Cloud-Based Controller Management : Disabled

Connection Status : Disabled

inform URL/IP Address : 192.168.1.1:29810

10 Example for PoE Configurations

10.1 Network Requirements

The network topology of a company is shown as below. Camera1 and Camera2 work for the security of the company and cannot be power off all the time. AP1 and AP2 provide the internet service and only work in the office time.

Figure 10-1 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["Switch A"] -->|Gi1/0/1| B["Base Device"]
    A -->|Gi1/0/2 Gi1/0/3| C["Base Device"]
    A -->|Gi1/0/4| D["Base Device"]
    A -->|Gi1/0/4| E["End"]

Camera1 Camera2 AP1 AP2

10.2 Configuring Scheme

To implement this requirement, you can set a PoE time-range as the office time, for example, from 08:30 to 18:00 on work days. Then apply the settings to port 1/0/3 and 1/0/4. Port 1/0/1 and port 1/0/2 need to supply power all the time, so the time range configurations can be left as the default settings here.

10.3 Using the GUI

The configurations of port 1/0/4 is similar with the configurations of port 1/0/3. Here we take port 1/0/3 for example.

1) Choose the menu SYSTEM > Time Range > Time Range Create and click + Add to load the following page.

Figure 10-2 Creating Time Range
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Time-Range Config Name: (1-16 characters) Holiday: Exclude Include Period Time Config Add Delete ID Date Day Time Operation No entries in this table. Total: 0 Discard Create

2) Click + Add and the following window will pop up. Set Date, Time and Day of Week as the following figure shows. Click Create.

Figure 10-3 Creating a Periodic Time
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image Period Time Config Date From Month: January ▼ Day: 1 ▼ Year: 2017 ▼ To Month: January ▼ Day: 1 ▼ Year: 2018 ▼ Time From: 08:30 (Format: HH:MM) To: 18:00 (Format: HH:MM) Day of Week ✓ Mon ✓ Tue ✓ Wed ✓ Thu ✓ Fri □ Sat □ Sun Cancel Create

3) Specify a name for the time range. Click Create.

Figure 10-4 Configuring Time Range
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image Time-Range Config Name: OfficeTime (1-16 characters) Holiday: Exclude Include Period Time Config ID Date Day Time Operation 0 January 1, 2017 - January 1, 20 18 Mon,Tue,Wed,Thu,Fri 08:30 - 18:00 Total: 0 Discard Create

4) Choose the menu SYSTEM > PoE > PoE Config to load the following page. Select port 1/0/3 and set the Time Range as OfficeTime. Click Apply.

Figure 10-5 Configure the Port
TP-LINK Omada TL-SG2008P - Using the GUI - 4

text_image PoE Config Unit System Power Limit (W) System Power Consumption (W) System Power Remain (W) Operation Unit1 192.0 0.0 192.0 Total: 1 Port Config UNIT1 □ Port PoE Status PoE Priority Power Limit Power Limit Value (0.1-30.0 W) Time Range PoE Profile Power (W) Curre OfficeTime □ 1 Enabled Low Class4 30 No Limit None 0 □ 2 Enabled Low Class4 30 No Limit None 0 ✓ 3 Enabled Low Class4 30 OfficeTime None 0 □ 4 Enabled Low Class4 30 No Limit None 0 □ 5 Enabled Low Class4 30 No Limit None 0 □ 6 Enabled Low Class4 30 No Limit None 0 □ 7 Enabled Low Class4 30 No Limit None 0 □ 8 Enabled Low Class4 30 No Limit None 0 □ 9 Enabled Low Class4 30 No Limit None 0 □ 10 Enabled Low Class4 30 No Limit None 0 Total: 24 1 entry selected. Cancel Apply

5) Click Save the settings.

10.4 Using the CLI

The configurations of Port1/0/4 is similar with the configuration of port 1/0/3. Here we take port 1/0/3 for example.

1) Create a time-range.

Switch_A#config

Switch_A(config)#time-range office-time

Switch_A(config-time-range)#holiday exclude

Switch_A(config-time-range)#absolute from 01/01/2017 to 01/01/2018

Switch_A(config-time-range)#periodic start 08:30 end 18:00 day-of-the-week 1-5

Switch_A(config-time-range)#exit

2) Enable the PoE function on the port 1/0/3. Specify the basic parameters for the port 1/0/3 and bind the time-range office-time to the port.

Switch_A(config)#interface gigabitEthernet 1/0/3

Switch_A(config-if)#power inline supply enable

Switch_A(config-if)#power inline time-range office-time

Switch_A(config-if)#end

Switch_A#copy running-config startup-config

Verify the Configuration

Verify the configuration of the time-range:

Switch_A#show time-range

Time-range entry: office-time (Active)

holiday: exclude

number of time slice: 1

01 - 01/01/2017 to 01/01/2018

- 08:00 to 18:00 on 1,2,3,4,5

Verify the configuration of the PoE basic parameters:

Switch_A#show power inline configuration interface gigabitEthernet 1/0/3

InterfacePoE-StatusPoE-PrioPower-Limit(w)Time-RangePoE-Profile
Gi1/0/3EnableLowClass4office-timeNone

11 Appendix: Default Parameters

Default settings of System Info are listed in the following tables.

Table 11-1 Default Settings of Device Description Configuration

Parameter Default Setting
Device Name The model nameof the switch.
Device Location SHENZHEN
System Contact www.tp-link.com

Table 11-2 Default Settings of System Time Configuration

Parameter Default Setting
Time Source Manual

Table 11-3 Default Settings of Daylight Saving Time Configuration

Parameter Default Setting
DST status Disabled

Default settings of User Management are listed in the following table.

Table 11-4 Default Settings of User Configuration

Parameter Default Setting
User Name admin
Password admin
Access Level Admin

Default settings of System Tools are listed in the following table.

Table 11-5 Default Settings of Boot Configuration

Parameter Default Setting
Current Startup Image image1.bin
Next Startup Image image1.bin
Backup Image image2.bin
Current Startup Config config1.cfg
Next Startup Configconfig1.cfg
Backup Config config2.cfg

Default setting of EEE is listed in the following table.

Table 11-6 Default Settings of EEE Configuration

Parameter Default Setting
Status Disabled

(Only for certain devices) Default settings of PoE is listed in the following table.

Table 11-7 Default Settings of PoE Configuration

Parameter Default Setting
PoE Config
System Power Limit (Refer to the actual web interface)
Port Config
PoE Status Enabled
PoE Priority Low
Power Limit (0.1w-30.0w) Class 4
Time Range No Limit
PoE Profile None
Profile Config
Profile Name None
PoE Status Enabled
PoE Priority Low
Power Limit Auto

Default settings of SDM Template are listed in the following table.

Table 11-8 Default Settings of SDM Template Configuration

Parameter Default Setting
Current Template IDDefault
Next Template ID Default

Default settings of Time Range are listed in the following table.

Table 11-9 Default Settings of Time Range Configuration

Parameter Default Setting
Holiday Include

Part 3

Managing Physical Interfaces

CHAPTERS

  1. Physical Interface
  2. Basic Parameters Configurations
  3. Port Isolation Configurations
  4. Loopback Detection Configuration
  5. Configuration Examples
  6. Appendix: Default Parameters

1 Physical Interface

1.1 Overview

Interfaces are used to exchange data and interact with interfaces of other network devices. Interfaces are classified into physical interfaces and layer 3 interfaces.

■ Physical interfaces are the ports on the switch panel. They forward packets based on MAC address table.
■ Layer 3 interfaces are used to forward IPv4 and IPv6 packets using static or dynamic routing protocols. You can use Layer 3 interfaces for IP routing and inter-VLAN routing.

This chapter introduces the configurations for physical interfaces.

1.2 Supported Features

The switch supports the following features about physical interfaces:

Basic Parameters

You can configure port status, speed mode, duplex mode, flow control and other basic parameters for ports.

Port Isolation

You can use this feature to restrict a specific port to send packets to only the ports in the forwarding port list that you configure.

Loopback Detection

This function allows the switch to detect loops in the network. When a loop is detected on a port or VLAN, the switch will display an alert on the management interface and block the corresponding port or VLAN according to your configurations.

2 Basic Parameters Configurations

2.1 Using the GUI

Choose the menu L2 FEATURES > Switching > Port > Port Config to load the following page.

Figure 2-1 Configuring Basic Parameters
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Port Config Jumbo: 1518 bytes (1518-9216) Apply UNIT1 LAGS Port Type Description Status Speed Duplex Flow Control LAG ✓ 1/0/1 Copper Enabled Auto Auto Disabled -- □ 1/0/2 Copper Enabled Auto Auto Disabled -- □ 1/0/3 Copper Enabled Auto Auto Disabled -- □ 1/0/4 Copper Enabled Auto Auto Disabled -- □ 1/0/5 Copper Enabled Auto Auto Disabled -- □ 1/0/6 Copper Enabled Auto Auto Disabled -- □ 1/0/7 Copper Enabled Auto Auto Disabled -- □ 1/0/8 Copper Enabled Auto Auto Disabled -- □ 1/0/9 Copper Enabled Auto Auto Disabled -- □ 1/0/10 Copper Enabled Auto Auto Disabled -- Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure basic parameters for the ports:

1) Configure the MTU size of jumbo frames for all the ports, then click Apply.

Jumbo Configure the size of jumbo frames. By default, it is 1518 bytes.

Generally, the MTU (Maximum Transmission Unit) size of a normal frame is 1518 bytes. If you want the switch supports to transmit frames of which the MTU size is greater than 1518 bytes, you can configure the MTU size manually here.

2) Select one or more ports to configure the basic parameters. Then click Apply.

UNIT/LAGSClick the UNIT number to configure physical ports. Click LAGS to configure LAGs.
TypeDisplays the port type. Copper indicates an Ethernet port, and Fiber indicates an SFP port.
Description (Optional) Enter a description for the port.
Status With this option enabled, the port forwards packets normally. Otherwise, the port cannot work. By default, it is enabled.
SpeedSelect the appropriate speed mode for the port. WhenAutois selected, the port automatically negotiates speed mode with the neighbor device. The default setting isAuto.It is recommended to selectAutoif both ends of the link support auto-negotiation.
DuplexSelect the appropriate duplex mode for the port. There are three options:Half, Full and Auto.The default setting isAuto.Half:The port can send and receive packets, but only one-way at a time.Full:The port can send and receive packets simultaneously.Auto:The port automatically negotiates duplex mode with the peer device.
Flow ControlWith this option enabled, when a device gets overloaded it will send a PAUSE frame to notify the peer device to stop sending data for a specified period of time, thus avoiding the packet loss caused by congestion. By default, it is disabled.

TP-LINK Omada TL-SG2008P - Using the GUI - 2

Note:

We recommend that you set the ports on both ends of a link as the same speed and duplex mode.

2.2 Using the CLI

Follow these steps to set basic parameters for the ports.

Step 1 configure

Enter global configuration mode.

Step 2 jumbo-size

size

Change the MTU (Maximum Transmission Unit) size to support jumbo frames. The default MTU size for frames received and sent on all ports is 1518 bytes. To transmit jumbo frames, you can manually configure MTU size of frames up to 9216 bytes.

size: Configure the MTU size of jumbo frames. The value ranges from 1518 to 9216 bytes.

Step 3 interface {fastEthernet

port | range fastEthernet port-list | gigabitEthernet port | range

gigabitEthernet port-list | ten-gigabitEthernet port | ten-range gigabitEthernet port-list | port-channel port-channel | range port-channel port-channel-list |

Enter interface configuration mode.

Step 4 Configure basic parameters for the port:

description string

Give a port description for identification.

string: Content of a port description, ranging from 1 to 16 characters.

shutdown

no shutdown

Use shutdown to disable the port, and use no shutdown to enable the port. When the status is enabled, the port can forward packets normally, otherwise it will discard the received packets. By default, all ports are enabled.

speed {10 | 100 | 1000 | 10000 | auto}

Set the appropriate speed mode for the port.

10 | 100 | 1000 | 10000 | auto: Speed mode of the port. The options are subject to your actual product. The device connected to the port should be in the same speed and duplex mode with the port. When auto is selected, the speed mode will be determined by auto-negotiation.

duplex { auto | full | half }

Set the appropriate duplex mode for the port.

auto | full | half: Duplex mode of the port. The device connected to the port should be in the same speed and duplex mode with the port. When auto is selected, the duplex mode will be determined by auto-negotiation.

flow-control

Enable the switch to synchronize the data transmission speed with the peer device, avoiding the packet loss caused by congestion. By default, it is disabled.

Step 5 show interface configuration [fastEthernet

port | gigabitEthernet port || ten-

gigabitEthernet port | port-channel port-channel-id ]

Verify the configuration of the port or LAG.

Step 6 end

Return to privileged EXEC mode.

Step 7 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to implement the basic configurations of port1/0/1, including setting a description for the port, configuring the jumbo frame, making the port automatically negotiate speed and duplex with the neighboring port, and enabling the flow-control:

Switch#configure

Switch#jumbo-size 9216

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#no shutdown

Switch(config-if)#description router connection

Switch(config-if)#speed auto

Switch(config-if)#duplex auto

Switch(config-if)#flow-control

Switch(config-if)#show interface configuration gigabitEthernet 1/0/1

Port State Speed Duplex FlowCtrl Description

Gi1/0/1 Enable Auto Auto Enable router connection

Switch(config-if)#show jumbo-size

Global jumbo size : 9216

Switch(config-if)#end

Switch#copy running-config startup-config

3 Port Isolation Configurations

3.1 Using the GUI

Port Isolation is used to limit the data transmitted by a port. The isolated port can only send packets to the ports specified in its Forwarding Port List.

Choose the menu L2 FEATURES > Switching > Port > Port Isolation to load the following page.

Figure 3-1 Port Isolation List

Port Isolation List
UNIT1
PortLAGForwarding Port List
1/0/1-28,LAG1-141/0/1-28,LAG1-14
1/0/2-1/0/1-28,LAG1-141/0/1-28,LAG1-14
1/0/3-1/0/1-28,LAG1-141/0/1-28,LAG1-14
1/0/4-1/0/1-28,LAG1-141/0/1-28,LAG1-14
1/0/5-1/0/1-28,LAG1-141/0/1-28,LAG1-14
1/0/6-1/0/1-28,LAG1-141/0/1-28,LAG1-14
1/0/7-1/0/1-28,LAG1-141/0/1-28,LAG1-14
1/0/8-1/0/1-28,LAG1-141/0/1-28,LAG1-14
1/0/9-1/0/1-28,LAG1-141/0/1-28,LAG1-14
1/0/10-1/0/1-28,LAG1-141/0/1-28,LAG1-14
Total: 28

The above page displays the port isolation list. Click to configure Port Isolation on the following page.

Figure 3-2 Port Isolation
TP-LINK Omada TL-SG2008P - Using the GUI - 1

Follow these steps to configure Port Isolation:

1) In the Port section, select one or multiple ports to be isolated.
2) In the Forwarding Port List section, select the forwarding ports or LAGs which the isolated ports can only communicate with. It is multi-optional.
3) Click Apply.

3.2 Using the CLI

Follow these steps to configure Port Isolation:

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet

port | range fastEthernet port-list | gigabitEthernet port | range

gigabitEthernet port-list | ten-gigabitEthernet port | ten-range gigabitEthernet port-list | port-channel port-channel | range port-channel port-channel-list |}

Specify the port to be isolated and enter interface configuration mode.

Step 3 port isolation { [fa-forward-list fa-forward-list] [gi-forward-list gi-forward-list] [te-forward-list te-forward-list] [ po-forward-list po-forward-list ] }Add ports or LAGs to the forwarding port list of the isolated port. It is multi-optional. fa-forward-list / gi-forward-list / te-forward-list Specify the forwarding Ethernet ports. po-forward-list: Specify the forwarding LAGs.
Step 4 show port isolation interface { fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel port-channel }Verify the Port Isolation configuration of the specified port.
Step 5 endReturn to privileged EXEC mode.
Step 6 copy running-config startup-configSave the settings in the configuration file.

The following example shows how to add ports 1/0/1-3 and LAG 4 to the forwarding list of port 1/0/5:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/5

Switch(config-if)#port isolation gi-forward-list 1/0/1-3 po-forward-list 4

Switch(config-if)#show port isolation interface gigabitEthernet 1/0/5

Port LAG Forward-List

Gi1/0/5 N/A Gi1/0/1-3, Po4

Switch(config-if)#end

Switch#copy running-config startup-config

4 Loopback Detection Configuration

4.1 Using the GUI

To avoid broadcast storm, we recommend that you enable storm control before loopback detection is enabled. For detailed introductions about storm control, refer to Configuring QoS.

Choose the menu L2 FEATURES > Switching > Port > Loopback Detection to load the following page.

Figure 4-1 Configuring Loopback Detection
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Loopback Detection Loopback Detection Status: ☐ Enable Detection Interval: 30 seconds (1-1000) Auto-recovery Time: 90 seconds (2-100,000) Web Refresh Status: ☐ Enable Web Refresh Interval: 6 seconds (3-100) Apply Port Config UNIT1 LAGS Recovery ☐ Port Status Operation Mode Recovery Mode Loop Status Block Status Block VLAN LAG ✓ 1/0/1 Disabled Alert Auto --- --- --- -- ☐ 1/0/2 Disabled Alert Auto --- --- --- -- ☐ 1/0/3 Disabled Alert Auto --- --- --- -- ☐ 1/0/4 Disabled Alert Auto --- --- --- -- ☐ 1/0/5 Disabled Alert Auto --- --- --- -- ☐ 1/0/6 Disabled Alert Auto --- --- --- -- ☐ 1/0/7 Disabled Alert Auto --- --- --- -- ☐ 1/0/8 Disabled Alert Auto --- --- --- -- ☐ 1/0/9 Disabled Alert Auto --- --- --- -- ☐ 1/0/10 Disabled Alert Auto --- --- --- -- Total: 28 1 entry selected. Cancel Apply Cancel

Follow these steps to configure loopback detection:

1) In the Loopback Detection section, enable loopback detection and configure the global parameters. Then click Apply.

Loopback Detection StatusEnable loopback detection globally.
Detection IntervalSet the interval of sending loopback detection packets in seconds.The valid value ranges from 1 to 1000 and the default value is 30.
Auto-recovery TimeSet the recovery time globally. The blocked port in Auto Recovery mode will automatically be recovered to normal status after the Auto-recovery Time expires. The value ranges from 2 to 100,000 in seconds, and the default value is 90.
Web Refresh StatusWith this option enabled, the switch will refresh the web timely. By default, it is disabled.
Web Refresh IntervalIf you enabled web refresh status, set the refresh interval in seconds between 3 and 100. The default value is 6.

2) In the Port Config section, select one or more ports to configure the loopback detection parameters. Then click Apply.

Status Enable loopback detection for the port.
Operation Mode Select the operation mode when a loopback is detected on the port:Alert: The Loop Status will display whether there is a loop detected on the corresponding port. It is the default setting.Port Based: In addition to displaying alerts, the switch will block the port on which the loop is detected.VLAN-Based: If a loop is detected in a VLAN on that port, in addition to displaying alerts, the switch will block that VLAN. The traffic of the other VLANs can still be normally forwarded by the port.
Recovery ModeIf you select Port Based or VLAN-Based as the operation mode, you also need to configure the recovery mode for the blocked port:Auto: The blocked port will automatically be recovered to normal status after the automatic recovery time expires. It is the default setting.Manual: You need to manually release the blocked port. Click Recovery to release the selected port.

3) (Optional) View the loopback detection information.

Loop Status Displays whether a loop is detected on the port.

Block Status Displays whether the port is blocked.

Block VLAN Displays the blocked VLANs.

4.2 Using the CLI

Follow these steps to configure loopback detection:

Step 1 configure

Enter global configuration mode.

Step 2 loopback-detection

Enable the loopback detection feature globally. By default, it is disabled.

Step 3 loopback-detection interval

interval-time

Set the interval of sending loopback detection packets which is used to detect the loops in the network.

interval-time: The interval of sending loopback detection packets. The valid values are from 1 to 1000 seconds. By default, the value is 30 seconds.

Step 4 loopback-detection recovery-time

recovery-time

Set the auto-recovery time, after which the blocked port in Auto Recovery mode can automatically be recovered to normal status.

recovery-time: Specify the detection interval, ranging from 2 to 100,000 seconds. The default value is 90.

Step 5 interface {fastEthernet

port | range fastEthernet port-list | gigabitEthernet port | range

gigabitEthernet port-list | ten-gigabitEthernet port | ten-range gigabitEthernet port-list | port-channel port-channel | range port-channel port-channel-list |

Enter interface configuration mode.

Step 6 loopback-detection

Enable loopback detection for the port. By default, it is disabled.

Step 7

loopback-detection config process-mode { alert | port-based | vlan-based } recovery-mode { auto | manual }

Set the process mode when a loopback is detected on the port. There are three modes:

alert: The switch will only display alerts when a loopback is detected. It is the default setting.

port-based: In addition to displaying alerts, the switch will block the port on which the loop is detected.

vlan-based: In addition to displaying alerts, the switch will block the VLAN of the port in which the loop is detected.

Set the recovery mode for the blocked port. There are two modes:

auto: After the recovery time expires, the blocked port will automatically recover to normal status and restart to detect loops in the network.

manual: The blocked port can only be released manually. You can use the command 'loopback-detection recover' to recover the blocked port to normal status.

Step 9 show loopback-detection global

Verify the global configuration of Loopback Detection.

Step 10 show loopback-detection interface { fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel port-channel}Verify the Loopback Detection configuration of the specified port.

Step 11 end

Return to privileged EXEC mode.

Step 12 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable loopback detection globally (keep the default parameters):

Switch#configure

Switch(config)#loopback-detection

Switch(config)#show loopback-detection global

Loopback detection global status : enable

Loopback detection interval : 30s

Loopback detection recovery time : 3 intervals

Switch(config-if)#end

Switch#copy running-config startup-config

The following example shows how to enable loopback detection of port 1/0/3 and set the process mode as alert and recovery mode as auto:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/3

Switch(config-if)#loopback-detection

Switch(config-if)#loopback-detection config process-mode alert recovery-mode auto

Switch(config-if)#show loopback-detection interface gigabitEthernet 1/0/3

PortEnableProcess ModeRecovery ModeLoopbackBlockLAG
----------------------------
Gi1/0/3enablealertautoN/AN/AN/A

Switch(config-if)#end

Switch#copy running-config startup-config

5 Configuration Examples

5.1 Example for Port Isolation

5.1.1 Network Requirements

As shown below, three hosts and a server are connected to the switch and all belong to VLAN 10. Without changing the VLAN configuration, Host A is not allowed to communicate with the other hosts except the server, even if the MAC address or IP address of Host A is changed.

Figure 5-1 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    Switch["Switch"] -->|Gi1/0/1| HostA["Host A"]
    Switch -->|Gi1/0/2| HostB["Host B"]
    Switch -->|Gi1/0/3| HostC["Host C Server"]
    Switch -->|Gi1/0/4| HostD["Host D"]
    HostA --> VLAN10["VLAN 10"]
    HostB --> VLAN10
    HostC --> VLAN10
    HostD --> VLAN10

5.1.2 Configuration Scheme

You can configure port isolation to implement the requirement. Set port 1/0/4 as the only forwarding port for port 1/0/1, thus forbidding Host A to forward packets to the other hosts.

Since communications are bidirectional, if you want Host A and the server to communicate normally, you also need to add port 1/0/1 as the forwarding port for port 1/0/4.

Demonstrated with T1600G-28TS, the following sections provide configuration procedure in two ways: using the GUI and using the CLI.

5.1.3 Using the GUI

1) Choose the menu L2 FEATURES > Switching > Port > Port Isolation to load the following page. It displays the port isolation list.

Figure 5-2 Port Isolation List

2) Click Edit on the above page to load the following page. Select port 1/0/1 as the port to be isolated, and select port 1/0/4 as the forwarding port. Click Apply.

Figure 5-3 Port Isolation Configuration
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Port Isolation List Port UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Forwarding Port List Select All 2 4 UNIT1 LAGS 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available

3) Select port 1/0/4 as the port to be isolated, and select port 1/0/1 as the forwarding port. Click Apply.

Figure 5-4 Port Isolation Configuration
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image Port Isolation List Port UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Forwarding Port List UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available

4) Click Save the settings.

5.1.4 Using the CLI

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#port isolation gi-forward-list 1/0/4

Switch(config-if)#exit

Switch(config)#interface gigabitEthernet 1/0/4

Switch(config-if)#port isolation gi-forward-list 1/0/1

Switch(config-if)#end

Switch#copy running-config startup-config

Verify the Configuration

Switch#show port isolation interface

Port LAG Forward-List

Gi1/0/1 N/A Gi1/0/4

Gi1/0/2 N/A Gi1/0/1-28, Po1-14

Gi1/0/3 N/A Gi1/0/1-28, Po1-14

Gi1/0/4 N/A Gi1/0/1

...

5.2 Example for Loopback Detection

5.2.1 Network Requirements

As shown below, Switch A is a convergence-layer switch connecting to several access-layer switches. Loops can be easily caused in case of misoperation on the access-layer switches. If there is a loop on an access-layer switch, broadcast storms will occur on Switch A or even in the entire network, creating excessive traffic and degrading the network performance.

To reduce the impacts of broadcast storms, users need to detect loops in the network via Switch A and timely block the port on which a loop is detected.

Figure 5-5 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["Switch A"] -->|Gi1/0/1| B["Access-layer Switches"]
    A -->|Gi1/0/2| C["Access-layer Switches"]
    A -->|Gi1/0/3| D["Management Host"]
    B --> E["Loop"]
    C --> E
    D --> E

5.2.2 Configuration Scheme

Enable loopback detection on ports 1/0/1-3 and configure SNMP to receive the trap notifications. For detailed instructions about SNMP, refer to Configuring SNMP & RMON. Here we introduce how to configure loopback detection and monitor the detection result on the management interface of the switch.

Demonstrated with T1600G-52TS, the following sections provide configuration procedure in two ways: using the GUI and using the CLI.

5.2.3 Using the GUI

1) Choose the menu L2 FEATURES > Switching > Port > Loopback Detection to load the configuration page.
2) In the Loopback Detection section, enable loopback detection and web refresh globally. Keep the other parameters as default values and click Apply.

Figure 5-6 Global Configuration
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Loopback Detection Loopback Detection Status: ✓ Enable Detection Interval: 20 seconds (1-1000) Auto-recovery Time: 90 seconds (2-100,000) Web Refresh Status: ✓ Enable Web Refresh Interval: 6 seconds (3-100) Apply

3) In the Port Config section, enable ports 1/0/1-3, select the operation mode as Port-Based so that the port will be blocked when a loop is detected, and keep the recovery mode as Auto so that the port will automatically be recovered to normal status after the auto-recovery time. Click Apply.

Figure 5-7 Port Configuration
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image Port Config UNIT1 LAGS Recovery Port Status Operation Mode Recovery Mode Loop Status Block Status Block VLAN LAG Enable Port Based Auto ✓ 1/0/1 Enabled Port Based Auto -- -- -- -- ✓ 1/0/2 Enabled Port Based Auto -- -- -- -- ✓ 1/0/3 Enabled Port Based Auto -- -- -- -- □ 1/0/4 Disabled Alert Auto -- -- -- -- □ 1/0/5 Disabled Alert Auto -- -- -- -- □ 1/0/6 Disabled Alert Auto -- -- -- -- □ 1/0/7 Disabled Alert Auto -- -- -- -- □ 1/0/8 Disabled Alert Auto -- -- -- -- □ 1/0/9 Disabled Alert Auto -- -- -- -- □ 1/0/10 Disabled Alert Auto -- -- -- -- Total: 28 3 entries selected. Cancel Apply

4) Monitor the detection result on the above page. The Loop status and Block status are displayed on the right side of ports.

5.2.4 Using the CLI

1) Enable loopback detection globally and configure the detection interval and recovery time.

Switch#configure

Switch(config)#loopback-detection

Switch(config)#loopback-detection interval 30

Switch(config)#loopback-detection recovery-time 3

2) Enable loopback detection on ports 1/0/1-3 and set the process mode and recovery mode.

Switch(config)#interface range gigabitEthernet 1/0/1-3

Switch(config-if-range)#loopback-detection

Switch(config-if-range)#loopback-detection config process-mode port-based recovery-mode auto

Switch(config-if-range)#end

Switch#copy running-config startup-config

Verify the Configuration

Verify the global configuration:

Switch#show loopback-detection global

Loopback detection global status : enable

Loopback detection interval: 30 s

Loopback detection recovery time : 90 s

Verify the loopback detection configuration on ports:

Switch#show loopback-detection interface

PortEnableProcess ModeRecovery ModeLoopbackBlockLAG
----------------------------
Gi1/0/1enableport-basedautoN/AN/AN/A
Gi1/0/2enableport-basedautoN/AN/AN/A
Gi1/0/3enableport-basedautoN/AN/AN/A

6

Appendix: Default Parameters

Default settings of Switching are listed in th following tables.

Table 6-1 Configurations for Ports

Parameter Default Setting
Port Config
Jumbo 1518 bytes
TypeCopper (For RJ45 Ports)Fiber (For SFP Ports)
Status Enabled
SpeedAuto (For RJ45 Ports)1000M (For SFP Ports)
DuplexAuto (For RJ45 Ports)Full (For SFP Ports)
Flow Control Disabled
Loopback Detection
Loopback Detection Status Disabled
Detection Interval 30 seconds
Auto-recovery Time 90 seconds
Web Refresh Status Disabled
Web Refresh Interval 6 seconds
Port Status Disabled
Operation modeAlert
Recovery modeAuto

Part 4

Configuring LAG

CHAPTERS

  1. LAG
  2. LAG Configuration
  3. Configuration Examples
  4. Appendix: Default Parameters

1 LAG

1.1 Overview

With LAG (Link Aggregation Group) function, you can aggregate multiple physical ports into a logical interface, increasing link bandwidth and providing backup ports to enhance the connection reliability.

1.2 Supported Features

You can configure LAG in two ways: static LAG and LACP (Link Aggregation Control Protocol).

Static LAG

The member ports are manually added to the LAG.

LACP

The switch uses LACP to implement dynamic link aggregation and disaggregation by exchanging LACP packets with its peer device. LACP extends the flexibility of the LAG configuration.

2 LAG Configuration

To complete LAG configuration, follow these steps:

1) Configure the global load-balancing algorithm.
2) Configure Static LAG or LACP.

Configuration Guidelines

■ Ensure that both ends of the aggregation link work in the same LAG mode. For example, if the local end works in LACP mode, the peer end should also be set as LACP mode.
■ Ensure that devices on both ends of the aggregation link use the same number of physical ports with the same speed, duplex, jumbo and flow control mode.

■ A port cannot be added to more than one LAG at the same time.
■ LACP does not support half-duplex links.

■ One static LAG supports up to eight member ports. All the member ports share the bandwidth evenly. If an active link fails, the other active links share the bandwidth evenly.

■ One LACP LAG supports multiple member ports, but at most eight of them can work simultaneously, and the other member ports are backups. Using LACP protocol, the switches negotiate parameters and determine the working ports. When a working port fails, the backup port with the highest priority will replace the faulty port and start to forward data.

For the functions like IGMP Snooping, 802.1Q VLAN, MAC VLAN, Protocol VLAN, VLAN-VPN, GVRP, Voice VLAN, STP, QoS, DHCP Snooping and Flow Control, the member pot of an LAG follows the configuration of the LAG but not its own. The configurations of the port can take effect only after it leaves the LAG.

■ The port enabled with Port Security, Port Mirror, MAC Address Filtering or 802.1X cannot be added to an LAG, and the member port of an LAG cannot be enabled with these functions.

2.1 Using the GUI

2.1.1 Configuring Load-balancing Algorithm

Choose the menu L2 FEATURES > Switching > LAG > LAG Table to load the following page.

Figure 2-1 Global Config
TP-LINK Omada TL-SG2008P - Configuring Load-balancing Algorithm - 1

text_image Global Config Hash Algorithm: SRC MAC+DST MAC LAG Table Apply Delete Group ID Description Members Operation 1 Active LACP -- Total: 1

In the Global Config section, select the load-balancing algorithm (Hash Algorithm), then click Apply.

Hash Algorithm

Select the Hash Algorithm, based on which the switch can choose the port to forward the received packets. In this way, different data flows are forwarded on different physical links to implement load balancing. There are six options:

SRC MAC: The computation is based on the source MAC addresses of the packets.

DST MAC: The computation is based on the destination MAC addresses of the packets.

SRC MAC+DST MAC: The computation is based on the source and destination MAC addresses of the packets.

SRC IP: The computation is based on the source IP addresses of the packets.

DST IP: The computation is based on the destination IP addresses of the packets.

SRC IP+DST IP: The computation is based on the source and destination IP addresses of the packets.

Tips:

  • Load-balancing algorithm is effective only for outgoing traffic. If the data stream is not well shared by each link, you can change the algorithm of the outgoing interface.
    ■ Please properly choose the load-balancing algorithm to avoid data stream transferring only on one physical link. For example, Switch A receives packets from several hosts and forwards them to the Server with the fixed MAC address, you can set the algorithm

as "SRC MAC" to allow Switch A to determine the forwarding port based on the source MAC addresses of the received packets.

Figure 2-2 Hash Algorithm Configuration
TP-LINK Omada TL-SG2008P - Tips: - 1

flowchart
graph LR
    A["Laptop 1"] --> B["Switch A"]
    C["Laptop 2"] --> B
    D["Laptop 3"] --> B
    B --> E["Server"]
    style A fill:#cce5ff,stroke:#333
    style C fill:#cce5ff,stroke:#333
    style D fill:#cce5ff,stroke:#333
    style E fill:#cce5ff,stroke:#333

Hosts Server

2.1.2 Configuring Static LAG or LACP

For one port, you can choose only one LAG mode: Static LAG or LACP. And make sure both ends of a link use the same LAG mode.

- Configuring Static LAG

Choose the menu L2 FEATURES > Switching > LAG > Static LAG to load the following page.

Figure 2-3 Static LAG
TP-LINK Omada TL-SG2008P - - Configuring Static LAG - 1

text_image LAG Config Group ID: LAG2 Description: -- Port: (Format:1/0/1, input or choose below) UNIT1 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Apply

Follow these steps to configure the static LAG:

1) Select an LAG for configuration.

Group ID Select an LAG for static LAG configuration.

Description Displays the LAG mode.

2) Select the member ports for the LAG. It is multi-optional.

3) Click Apply.

TP-LINK Omada TL-SG2008P - 3) Click Apply. - 1

Note:

Clearing all member ports will delete the LAG.

- Configuring LACP

Choose the menu L2 FEATURES > Switching > LAG > LACP to load the following page.

Figure 2-4 LACP Config
TP-LINK Omada TL-SG2008P - - Configuring LACP - 1

text_image Global Config System Priority: 32768 (0-65535) Apply LACP Table UNIT1 Port Status Group ID Port Priority Mode LAG ✓ 1/0/1 Disabled 0 32768 Passive --- □ 1/0/2 Disabled 0 32768 Passive --- □ 1/0/3 Disabled 0 32768 Passive --- □ 1/0/4 Disabled 0 32768 Passive --- □ 1/0/5 Disabled 0 32768 Passive --- □ 1/0/6 Disabled 0 32768 Passive --- □ 1/0/7 Disabled 0 32768 Passive --- □ 1/0/8 Disabled 0 32768 Passive --- □ 1/0/9 Disabled 0 32768 Passive --- □ 1/0/10 Disabled 0 32768 Passive --- Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure LACP:

1) Specify the system priority for the switch and click Apply.

System Priority

Specify the system priority for the switch. A smaller value means a higher priority.

To keep active ports consistent at both ends, you can set the system priority of one device to be higher than that of the other device. The device with higher priority will determine its active ports, and the other device can select its active ports according to the selection result of the device with higher priority. If the two ends have the same system priority value, the device with a smaller MAC address has the higher priority.

2) Select member ports for the LAG and configure the related parameters. Click Apply.

Group ID Specify the group ID of the LAG. Note that the group ID of other static LAGs cannot be set as this value.The valid value of the Group ID is determined by the maximum number of LAGs supported by your switch. For example, if your switch supports up to 14 LAGs, the valid value ranges from 1 to 14.
Port Priority(0-65535)Specify the Port Priority. A smaller value means a higher port priority.The port with higher priority in an LAG will be selected as the working port to forward data, and at most eight ports can work simultaneously. If two ports have the same priority value, the port with a smaller port number has the higher priority.
Mode Select the LACP mode for the port.In LACP, the switch uses LACPDU (Link Aggregation Control Protocol Data Unit) to negotiate the parameters with the peer end. In this way, the two ends select active ports and form the aggregation link. The LACP mode determines whether the port will take the initiative to send the LACPDU. There are two modes:Passive:The port will not send LACPDU before receiving the LACPDU from the peer end.Active:The port will take the initiative to send LACPDU.

Status Enable the LACP function of the port. By default, it is disabled.

2.2 Using the CLI

2.2.1 Configuring Load-balancing Algorithm

Follow these steps to configure the load-balancing algorithm:

Step 1 configure

Enter global configuration mode.

Step 2port-channel load-balance {src-mac | dst-mac | src-dst-mac | src-ip | dst-ip | src-dst-ip}Select the Hash Algorithm. The switch will choose the ports to transfer the packets based on the Hash Algorithm. In this way, different data flows are forwarded on different physical links to implement load balancing.src-mac: The computation is based on the source MAC addresses of the packets.dst-mac: The computation is based on the destination MAC addresses of the packets.src-dst-mac: The computation is based on the source and destination MAC addresses of the packets.src-ip: The computation is based on the source IP addresses of the packets.dst-ip: The computation is based on the destination IP addresses of the packets.src-dst-ip: The computation is based on the source and destination IP addresses of the packets.

Step 3 show etherchannel load-balance

Verify the configuration of load-balancing algorithm.
Step 4 end
Step 5 copy running-config startup-config

The following example shows how to set the global load-balancing mode as src-dst-mac:

Switch#configure

Switch(config)#port-channel load-balance src-dst-mac

Switch(config)#show etherchannel load-balance

EtherChannel Load-Balancing Configuration: src-dst-mac

EtherChannel Load-Balancing Addresses Used Per-Protocol:

Non-IP: Source XOR Destination MAC address

IPv4: Source XOR Destination MAC address

IPv6: Source XOR Destination MAC address

Switch(config)#end

Switch#copy running-config startup-config

2.2.2 Configuring Static LAG or LACP

You can choose only one LAG mode for a port: Static LAG or LACP. And make sure both ends of a link use the same LAG mode.

■ Configuring Static LAG

Follow these steps to configure static LAG:

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list ] Enter interface configuration mode.

Step 3 channel-group num mode on

Add the port to a static LAG.

num: The group ID of the LAG.

Step 4 show etherchannel num summary

Verify the configuration of the static LAG.

num: The group ID of the LAG.

Step 5 end

Return to privileged EXEC mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to add ports1/0/5-8 to LAG 2 and set the mode as static LAG:

Switch#configure

Switch(config)#interface range gigabitEthernet 1/0/5-8

Switch(config-if-range)#channel-group 2 mode on

Switch(config-if-range)#show etherchannel 2 summary

Flags: D - down P - bundled in port-channel U - in use

I - stand-alone H - hot-standby(LACP only) s - suspended

R - layer3 S - layer2 f - failed to allocate aggregator

u - unsuitable for bundling w - waiting to be aggregated d - default port

Group Port-channel Protocol Ports

2 Po2(S) - Gi1/0/5(D) Gi1/0/6(D) Gi1/0/7(D) Gi1/0/8(D)

Switch(config-if-range)#end

Switch#copy running-config startup-config

- Configuring LACP

Follow these steps to configure LACP:

Step 1 configure

Enter global configuration mode.

Step 2 lacp system-priority

pri

Specify the system priority for the switch.

To keep active ports consistent at both ends, you can set the priority of one device to be higher than that of the other device. The device with higher priority will determine its active ports, and the other device can select its active ports according to the selection result of the device with higher priority. If the two ends have the same system priority value, the end with a smaller MAC address has the higher priority.

pri: System priority. The valid values are from 0 to 65535, and the default value is 32768. A smaller value means a higher device priority.

Step 3 interface {fastEthernet

port | range fastEthernet port-list | gigabitEthernet port | range

gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list ]

Enter interface configuration mode.

Step 4 channel-group

num mode {active | passive}

Add the port to an LAG and set the mode as LACP.

num: The group ID of the LAG.

mode: LAG mode. Here you need to select LACP mode: active or passive.

In LACP, the switch uses LACPDU (Link Aggregation Control Protocol Data Unit) to negotiate the parameters with the peer end. In this way, the two ends select active ports and form the aggregation link. The LACP mode determines whether the port will take the initiative to send the LACPDU.

passive: The port will not send LACPDU before receiving the LACPDU from the peer end.

active: The port will take the initiative to send LACPDU.

Step 5 lacp port-priority

pri

Specify the Port Priority. The port with higher priority in an LAG will be selected as the working port. If two ports have the same priority value, the port with a smaller port number has the higher priority.

pri: Port priority. The valid values are from 0 to 65535, and the default value is 32768. A smaller value means a higher port priority.

Step 6 show lacp sys-id

Verify the global system priority.

Step 7 show lacp internal

Verify the LACP configuration of the local switch.

Step 8 end

Return to privileged EXEC mode.

Step 9 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to specify the system priority of the switch as 2:

Switch#configure

Switch(config)#lacp system-priority 2

Switch(config)#show lacp sys-id

2,000a.eb13.2397

Switch(config)#end

Switch#copy running-config startup-config

The following example shows how to add ports 1/0/1-4 to LAG 6, set the mode as LACP, and select the LACPDU sending mode as active:

Switch#configure

Switch(config)#interface range gigabitEthernet 1/0/1-4

Switch(config-if-range)#channel-group 6 mode active

Switch(config-if-range)#show lacp internal

Flags: S - Device is requesting Slow LACPDUs

F - Device is requesting Fast LACPDUs

A - Device is in active mode

P - Device is in passive mode

Channel group 6

PortFlagsStateLACP Port PriorityAdmin KeyOper KeyPort NumberPort State
Gi1/0/1SAUp327680x60x4b10x10x7d
Gi1/0/2SADown327680x600x20x45
Gi1/0/3SADown327680x600x30x45
Gi1/0/4SADown327680x600x40x45

Switch(config-if-range)#end

Switch#copy running-config startup-config

3 Configuration Examples

3.1 Example for Static LAG

3.1.1 Network Requirements

As shown below, hosts and servers are connected to switch A and switch B, and heavy traffic is transmitted between the two switches. To achieve high speed and reliability of data transmission, users need to improve the bandwidth and redundancy of the link between the two switches.

Figure 3-1 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph LR
    A["Hosts"] -->|Gi1/0/1 Gi1/0/1| B["Switch A Switch B"]
    B -->|Gi1/0/8 Gi1/0/8| C["Servers"]

3.1.2 Configuration Scheme

LAG function can bundle multiple physical ports into one logical interface to increase bandwidth and improve reliability. In this case we can configure static LAG to meet the requirement.

The overview of the configuration is as follows:

1) Considering there are multiple devices on each end, configure the load-balancing algorithm as 'SRC MAC+DST MAC'.
2) Add ports 1/0/1-8 to a static LAG.

Demonstrated with T1600G-28TS, the following sections provide configuration procedure in two ways: using the GUI and using the CLI.

3.1.3 Using the GUI

The configurations of switch A and switch B are similar. The following introductions take switch A as an example.

1) Choose the menu L2 FEATURES > Switching > LAG > LAG Table to load the following page. Select the hash algorithm as 'SRC MAC+DST MAC'.

Figure 3-2 Global Configuration
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Global Config Hash Algorithm: SRC MAC+DST MAC Apply

2) Choose the menu L2 FEATURES > Switching > LAG > Static LAG to load the following page. Select LAG 1 and add ports 1/0/1-8 to LAG 1.

Figure 3-3 System Priority Configuration
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image LAG Config Group ID: LAG1 Description: -- Port: 1/0/1-8 (Format: 1/0/1, input or choose below) UNIT1 2 4 5 8 1 3 5 7 Selected Unselected Not Available Apply

3) Click Save the settings.

3.1.4 Using the CLI

The configurations of switch A and switch B are similar. The following introductions take switch A as an example.

1) Configure the load-balancing algorithm as "src-dst-mac".

Switch#configure

Switch(config)#port-channel load-balance src-dst-mac

2) Add ports 1/0/1-8 to static LAG 1.

Switch(config)#interface range gigabitEthernet 1/0/1-8

Switch(config-if-range)#channel-group 1 mode on

Switch(config-if)#end

Switch#copy running-config startup-config

Verify the Configuration

Switch#show etherchannel 1 summary

Flags: D - down

P - bundled in port-channel

U - in use

I - stand-alone

H - hot-standby(LACP only)

s - suspended

R - layer3S - layer2f - failed to allocate aggregator
u - unsuitable for bundlingw - waiting to be aggregated d - default port
GroupPort-channelProtocolPorts
----------------
1Po2(S)-Gi1/0/1(D) Gi1/0/2(D) Gi1/0/3(D) Gi1/0/4(D)
Gi1/0/5(D) Gi1/0/6(D) Gi1/0/7(D) Gi1/0/8(D)

3.2 Example for LACP

3.2.1 Network Requirements

As shown below, hosts and servers are connected to Switch A and Switch B, and heavy traffic is transmitted between the two switches. To achieve high speed and reliability of data transmission, users need to improve the bandwidth and redundancy of the link between the two switches.

3.2.2 Configuration Scheme

LAG function can bundle multiple physical ports into one logical interface to increase bandwidth and improve reliability. In this case, we take LACP as an example.

As shown below, you can bundle up to eight physical ports into one logical aggregation group to transmit data between the two switches, and respectively connect the ports of the groups. In addition, another two redundant links can be set as the backup. To avoid traffic bottleneck between the servers and Switch B, you also need to configure LAG on them to increase link bandwidth. Here we mainly introduce the LAG configuration between the two switches.

Figure 3-1 Network Topology
TP-LINK Omada TL-SG2008P - Configuration Scheme - 1

flowchart
graph LR
    A["Hosts"] -->|Gi1/0/1 Gi1/0/1| B["Switch A Switch B"]
    B -->|Gi1/0/10 Gi1/0/10| C["Servers"]

The overview of the configuration is as follows:

1) Considering there are multiple devices on each end, configure the load-balancing algorithm as 'SRC MAC+DST MAC'.
2) Specify the system priority for the switches. Here we choose Switch A as the dominate device and specify a higher system priority for it.
3) Add ports 1/0/1-10 to the LAG and set the mode as LACP.

4) Specify a lower port priority for ports 1/0/9-10 to set them as the backup ports. When any of ports 1/0/1-8 is down, the backup ports will automatically be enabled to transmit data.

Demonstrated with T1600G-52TS, the following sections provide configuration procedure in two ways: using the GUI and using the CLI.

3.2.3 Using the GUI

The configurations of Switch A and Switch B are similar. The following introductions take Switch A as an example.

1) Choose the menu L2 FEATURES > Switching > LAG > LAG Table to load the following page. Select the hash algorithm as 'SRC MAC+DST MAC'.

Figure 3-2 Global Configuration
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Global Config Hash Algorithm: SRC MAC+DST MAC Apply

2) Choose the menu L2 FEATURES > Switching > LAG > LACP Config to load the following page. In the Global Config section, specify the system priority of Switch A as 0 and Click Apply. Remember to ensure that the system priority value of Switch B is bigger than 0.

Figure 3-3 System Priority Configuration
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image Global Config System Priority: 0 (0-65535) Apply

3) In the LACP Table section, select ports 1/0/1-10, and respectively set the status, group ID, port priority and mode for each port as follows.

Figure 3-4 LACP Configuration
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image LACP Table UNIT1 Port Status Group ID Port Priority Mode LAG 1/0/1 Enabled 1 0 Active --- 1/0/2 Enabled 1 0 Active --- 1/0/3 Enabled 1 0 Active --- 1/0/4 Enabled 1 0 Active --- 1/0/5 Enabled 1 0 Active --- 1/0/6 Enabled 1 0 Active --- 1/0/7 Enabled 1 0 Active --- 1/0/8 Enabled 1 0 Active --- 1/0/9 Enabled 1 1 Active --- 1/0/10 Enabled 1 2 Active --- Total: 28

4) Click Save the settings.

3.2.4 Using the CLI

The configurations of Switch A and Switch B are similar. The following introductions take Switch A as an example.

1) Configure the load-balancing algorithm as "src-dst-mac".

Switch#configure

Switch(config)#port-channel load-balance src-dst-mac

2) Specify the system priority of Switch A as 0. Remember to ensure that the system priority value of Switch B is bigger than 0.

Switch(config)#lacp system-priority 0

3) Add ports 1/0/1-8 to LAG 1 and set the mode as LACP. Then specify the port priority as 0 to make them active.

Switch(config)#interface range gigabitEthernet 1/0/1-8

Switch(config-if-range)#channel-group 1 mode active

Switch(config-if-range)#lacp port-priority 0

Switch(config-if-range)#exit

4) Add port 1/0/9 to LAG 1 and set the mode as LACP. Then specify the port priority as 1 to set it as a backup port. When any of the active ports is down, this port will be preferentially selected to work as an active port.

Switch(config)#interface gigabitEthernet 1/0/9

Switch(config-if)#channel-group 1 mode active

Switch(config-if)#lacp port-priority 1

Switch(config-if)#exit

5) Add port 1/0/10 to LAG 1 and set the mode as LACP. Then specify the port priority as 2 to set it as a backup port. The priority of this port is lower than port 1/0/9.

Switch(config)#interface gigabitEthernet 1/0/10

Switch(config-if)#channel-group 1 mode active

Switch(config-if)#lacp port-priority 2

Switch(config-if)#end

Switch#copy running-config startup-config

Verify the Configuration

Verify the system priority:

Switch#show lacp sys-id

0,000a.eb13.2397

Verify the LACP configuration:

Switch#show lacp internal

Flags: S - Device is requesting Slow LACPDUs

F - Device is requesting Fast LACPDUs

A - Device is in active mode

P - Device is in passive mode

Channel group 1

PortFlagsStateLACPPort PriorityAdmin KeyOper KeyPort NumberPort State
Gi1/0/1SADown00x100x10x45
Gi1/0/2SADown00x100x20x45
Gi1/0/3SADown00x100x30x45
Gi1/0/4SADown00x100x40x45
Gi1/0/5SADown00x100x50x45
Gi1/0/6SADown00x100x60x45
Gi1/0/7SADown00x100x70x45
Gi1/0/8SADown00x100x80x45
Gi1/0/9 SADown10x100x90x45
Gi1/0/10 SADown20x100xa0x45

4 Appendix: Default Parameters

Default settings of Switching are listed in the following tables.

Table 4-1 Default Settings of LAG

Parameter Default Setting
LAG Table
Hash Algorithm SRC MAC+DST MAC
LACP Config
System Priority 32768
Admin Key 0
Port Priority 32768
Mode Passive
Status Disabled

Part 5

Configuring DDM

(Only for Certain Devices)

CHAPTERS

  1. Overview
  2. DDM Configuration
  3. Appendix: Default Parameters

1 Overview

TP-LINK Omada TL-SG2008P - Overview - 1

Note:

DDM is only available on certain devices. To check whether your device supports this feature, refer to the actual web interface. If DDM is available, there is L2 FEATURES > Switching > DDM in the menu structure.

The DDM (Digital Diagnostic Monitoring) function is used to monitor the status of the SFP modules inserted into the SFP ports on the switch. The user can choose to shut down the monitored SFP port automatically when the specified parameter exceeds the alarm threshold or warning threshold. The monitored parameters include: Temperature, Voltage, Bias Current, Tx Power and Rx Power.

2 DDM Configuration

To complete DDM configuration, follow these steps:

1) Enable DDM on the SFP port and configure the shutdown condition.
2) Configure the specified value for warning or alarm threshold.

2.1 Using the GUI

2.1.1 Configuring DDM Globally

Choose the menu L2 FEATURES > Switching > DDM > DDM Config and select the desired SFP port to load the following page.

Figure 2-1 Configure DDM Globally
TP-LINK Omada TL-SG2008P - Configuring DDM Globally - 1

text_image Port Config Port DDM Status Shutdown LAG ✓ 1/0/25 Enabled None -- □ 1/0/26 Enabled None -- □ 1/0/27 Enabled None -- □ 1/0/28 Enabled None -- Total: 4 1 entry selected. Cancel Apply

Follow these steps to configure the DDM parameters on SFP ports:

1) In the Port Config section, select one or multiple SFP ports to configure DDM parameters.

DDM Status Enable or disable DDM feature on the SFP port.

Shutdown Specify whether to shut down the port when the alarm threshold or warning threshold is exceeded.

Alarm: Shut down the port when the alarm threshold is exceeded.

Warning: Shut down the port when the warning threshold is exceeded.

None: The port will not be shut down even if the alarm threshold or warning threshold is exceeded. This is the default option.

LAG Displays the LAG number which the port belongs to.

2) Click Apply.

2.1.2 Configuring the Threshold

TP-LINK Omada TL-SG2008P - Configuring the Threshold - 1

Note:

The value of threshold parameters should conform to the following rule: High Alarm ≥ High Warning ≥ Low Warning ≥ Low Alarm.

Choose the menu L2 FEATURES > Switching > DDM > Threshold Config to load the following page.

■ Configuring the Temperature Threshold

Figure 2-2 Configure Temperature Threshold
TP-LINK Omada TL-SG2008P - Note: - 1

text_image Temperature Port High Alarm Low Alarm High Warning Low Warning LAG (-128-127.996 °C) (-128-127.996 °C) (-128-127.996 °C) (-128-127.996 °C) 1/0/25 -- -- -- -- 1/0/26 -- -- -- -- 1/0/27 -- -- -- -- 1/0/28 -- -- -- -- Total: 4 1 entry selected. Cancel Apply Cancel Apply

Follow these steps to configure DDM's temperature threshold:

1) In the Temperature table, select one or more SFP ports to configure temperature threshold of the SFP ports.

High Alarm Specify the high temperature threshold for the alarm. When the operating parameter rises above this value, action associated with the alarm will be taken. The valid values are from -128 to 127.996.
Low Alarm Specify the low temperature threshold for the alarm. When the operating parameter falls below this value, action associated with the alarm will be taken. The valid values are from -128 to 127.996.
High WarningSpecify the high temperature threshold for the warning. When the operating parameter rises above this value, action associated with the warning will be taken. The valid values are from -128 to 127.996.
Low Warning Specify the low temperature threshold for the warning. When the operating parameter falls below this value, action associated with the warning will be taken. The valid values are from -128 to 127.996.
LAG Displays the LAG number which the port belongs to.

2) Click Apply.

■ Configuring the Voltage Threshold

Figure 2-3 Configure Voltage Threshold
TP-LINK Omada TL-SG2008P - ■ Configuring the Voltage Threshold - 1

text_image Voltage Port High Alarm Low Alarm High Warning Low Warning LAG (0-6.5535 V) (0-6.5535 V) (0-6.5535 V) (0-6.5535 V) 1/0/25 --- --- --- -- 1/0/26 --- --- --- -- 1/0/27 --- --- --- -- 1/0/28 --- --- --- -- Total: 4 1 entry selected Cancel Apply

Follow these steps to configure DDM's voltage threshold:

1) In the Voltage table, select one or more SFP ports to configure voltage threshold on the SFP ports.

High AlarmSpecify the high voltage threshold for the alarm. When the operating parameter rises above this value, action associated with the alarm will be taken. The valid values are from 0 to 6.5535.
Low AlarmSpecify the low voltage threshold for the alarm. When the operating parameter falls below this value, action associated with the alarm will be taken. The valid values are from 0 to 6.5535.
High WarningSpecify the high voltage threshold for the warning. When the operating parameter rises above this value, action associated with the warning will be taken. The valid values are from 0 to 6.5535.
Low WarningSpecify the low voltage threshold for the warning. When the operating parameter falls below this value, action associated with the warning will be taken. The valid values are from 0 to 6.5535.

LAG Displays the LAG number which the port belongs to.

2) Click Apply.

■ Configuring the Bias Current Threshold

Figure 2-4 Configure Bias Current Threshold
TP-LINK Omada TL-SG2008P - ■ Configuring the Bias Current Threshold - 1

text_image Bias Current Port High Alarm Low Alarm High Warning Low Warning LAG (0-131 mA) (0-131 mA) (0-131 mA) (0-131 mA) 1/0/25 --- --- --- -- 1/0/26 --- --- --- -- 1/0/27 --- --- --- -- 1/0/28 --- --- --- -- Total: 4 1 entry selected. Cancel Apply

Follow these steps to configure DDM's bias current threshold:

1) In the Bias Current table, select one or more SFP ports to configure bias current threshold on the SFP ports.

High Alarm Specify the high bias current threshold for the alarm. When the operating parameter rises above this value, action associated with the alarm will be taken. The valid values are from 0 to 131.
Low Alarm Specify the low bias current threshold for the alarm. When the operating parameter falls below this value, action associated with the alarm will be taken. The valid values are from 0 to 131.
High WarningSpecify the high bias current threshold for the warning. When the operating parameter rises above this value, action associated with the warning will be taken. The valid values are from 0 to 131.
Low Warning Specify the low bias current threshold for the warning. When the operating parameter falls below this value, action associated with the warning will be taken. The valid values are from 0 to 131.
LAG Displays the LAG number which the port belongs to.

2) Click Apply.

■ Configuring the Rx Power Threshold

Figure 2-5 Configure Rx Power Threshold
TP-LINK Omada TL-SG2008P - ■ Configuring the Rx Power Threshold - 1

text_image RX Power Port High Alarm Low Alarm High Warning Low Warning LAG (0-6.5535 mW) (0-6.5535 mW) (0-6.5535 mW) (0-6.5535 mW) 1/0/25 --- --- --- -- 1/0/26 --- --- --- -- 1/0/27 --- --- --- -- 1/0/28 --- --- --- -- Total: 4 1 entry selected Cancel Apply

Follow these steps to configure DDM's Rx power threshold:

1) In the RX Power table, select one or more SFP ports to configure Rx power threshold on the SFP ports.

High Alarm Specify the high Rx power threshold for the alarm. When the operating parameter rises above this value, action associated with the alarm will be taken. The valid values are from 0 to 6.5535.
Low Alarm Specify the low Rx power threshold for the alarm. When the operating parameter falls below this value, action associated with the alarm will be taken. The valid values are from 0 to 6.5535.
High Warning Specify the high Rx power threshold for the warning. When the operating parameter rises above this value, action associated with the warning will be taken. The valid values are from 0 to 6.5535.
Low Warning Specify the low Rx power threshold for the warning. When the operating parameter falls below this value, action associated with the warning will be taken. The valid values are from 0 to 6.5535.
LAG Displays the LAG number which the port belongs to.

2) Click Apply.

■ Configuring the Tx Power Threshold

Figure 2-6 Configure Tx Power Threshold
TP-LINK Omada TL-SG2008P - ■ Configuring the Tx Power Threshold - 1

text_image TX Power Port High Alarm Low Alarm High Warning Low Warning LAG (0-6.5535 mW) (0-6.5535 mW) (0-6.5535 mW) (0-6.5535 mW) 1/0/25 --- --- --- -- 1/0/26 --- --- --- -- 1/0/27 --- --- --- -- 1/0/28 --- --- --- -- Total: 4 1 entry selected. Cancel Apply

Follow these steps to configure DDM's Tx power threshold:

1) In the TX Power table, select one or more SFP ports to configure Tx power threshold on the SFP ports.

High Alarm Specify the high Tx power threshold for the alarm. When the operating parameter rises above this value, action associated with the alarm will be taken. The valid values are from 0 to 6.5535.
Low Alarm Specify the low Tx power threshold for the alarm. When the operating parameter falls below this value, action associated with the alarm will be taken. The valid values are from 0 to 6.5535.
High Warning Specify the high Tx power threshold for the warning. When the operating parameter rises above this value, action associated with the warning will be taken. The valid values are from 0 to 6.5535.
Low Warning Specify the low Tx power threshold for the warning. When the operating parameter falls below this value, action associated with the warning will be taken. The valid values are from 0 to 6.5535.
LAG Displays the LAG number which the port belongs to.

2) Click Apply.

2.1.3 Viewing DDM Status

Choose the menu L2 FEATURES > Switching > DDM > DDM Status to load the following page.

Figure 2-7 View DDM Status

DDM Status
PortTemperature (°C)Voltage (V)Bias Current (mA)TX Power (mW)RX Power (mW)Transmit FaultLoss of SignalData Ready
1/0/25----------------
1/0/26----------------
1/0/27----------------
1/0/28----------------
Total: 4

In the Port Config table, view the current operating parameters for the SFP modules inserted into the SFP ports.

Temperature The current temperature of the SFP module inserted into this port.

Voltage The current voltage of the SFP module inserted into this port.

Bias Current The current bias current of the SFP module inserted into this port.

Tx Power The current Tx power of the SFP module inserted into this port.

Rx Power The current Rx power of the SFP module inserted into this port.

Data Ready Indicates whether SFP module is operational. The values are True and False.

Loss of Signal Reports local SFP module signal loss. The values are True and False.

Transmit Fault Reports remote SFP module signal loss. The values are True, False and No Signal.

2.2 Using the CLI

2.2.1 Configuring DDM Globally

Follow these steps to enable DDM on specified SFP ports:

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet

port | range fastEthernet port-list | gigabitEthernet port | range

gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list }

Enter interface configuration mode.

Step 3 ddm state enable

Enable DDM on this SFP port.

Step 4 show ddm configuration state

Display the DDM state of the SFP ports.

Step 5 end

Return to Privileged EXEC Mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable DDM status on SFP port 1/0/25:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/25

Switch(config-if)#ddm state enable

Switch(config-if)#show ddm configuration state

DDM Status Shutdown

Gi1/0/25 Enable None

...

Switch(config-if)#end

Switch#copy running-config startup-config

2.2.2 Configuring DDM Shutdown

Follow these steps to configure settings for shutting down SFP ports when the alarm threshold or warning threshold is exceeded:

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet

port | range fastEthernet port-list | gigabitEthernet port | range

gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list }

Enter interface configuration mode.

Step 3 ddm shutdown {none | warning | alarm}

none: The port will not be shut down if the alarm threshold or warning threshold is exceeded.

warning: Shut down the port when the warning threshold is exceeded.

alarm: Shut down the port when the alarm threshold is exceeded.

Step 4 show ddm configuration state

Display the DDM state of the SFP ports.

Step 5 end

Return to Privileged EXEC Mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to set SFP port 1/0/25 to shut down when the warning threshold is exceeded.

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/25

Switch(config-if)#ddm shutdown warning

Switch(config-if)#show ddm configuration state

DDM Status Shutdown

Gi1/0/25 Enable Warning

...

Switch(config-if)#end

Switch#copy running-config startup-config

2.2.3 Configuring the Threshold

■ Configuring Temperature Threshold

Follow these steps to configure the threshold of the DDM temperature on the specified SFP port.

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet

port | range fastEthernet port-list | gigabitEthernet port | range

gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list }

Enter interface configuration mode.

Step 3ddm temperature_threshold { high_alarm | high_warning | low_alarm | low_warning } valuehigh_alarm: Specify the high threshold for the alarm. When the operating parameter rises above this value, action associated with the alarm will be taken.high_warning: Specify the high threshold for the warning. When the operating parameter rises above this value, action associated with the warning will be taken.low_alarm: Specify the low threshold for the alarm. When the operating parameter falls below this value, action associated with the alarm will be taken.low_warning: Specify the low threshold for the warning. When the operating parameter falls below this value, action associated with the warning will be taken.value: Enter the threshold value in Celsius. The valid values are from -128 to 127.996.
Step 4show ddm configuration temperatureDisplay the DDM temperature threshold on the SFP ports.
Step 5endReturn to Privileged EXEC Mode.
Step 6copy running-config startup-configSave the settings in the configuration file.

The following example shows how to set SFP port 1/0/27's high alarm temperature threshold as 110 Celsius.

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/27

Switch(config-if)#ddm temperature_threshold high_alarm 110

Switch(config-if)#show ddm configuration temperature

Temperature Threshold(Celsius):

High Alarm Low Alarm High Warning Low Warning

Gi1/0/27 110.000000 -- -- --

...

Switch(config-if)#end

Switch#copy running-config startup-config

■ Configuring Voltage Threshold

Follow these steps to configure the threshold of the DDM voltage on the specified SFP port.

Step 1 configure
Enter global configuration mode.

Step 2 interface { fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list }Enter interface configuration mode.
Step 3ddm voltage_threshold { high_alarm | high_warning | low_alarm | low_warning } valuehigh_alarm: Specify the high threshold for the alarm. When the operating parameter rises above this value, action associated with the alarm will be taken.high_warning: Specify the high threshold for the warning. When the operating parameter rises above this value, action associated with the warning will be taken.low_alarm: Specify the low threshold for the alarm. When the operating parameter falls below this value, action associated with the alarm will be taken.low_warning: Specify the low threshold for the warning. When the operating parameter falls below this value, action associated with the warning will be taken.value: Enter the threshold value in V. The valid values are from 0 to 6.5535.

Step 4 show ddm configuration voltage

Display the DDM voltage threshold of the SFP ports.

Step 5 end
Return to Privileged EXEC Mode.
Step 6 copy running-config startup-config
Save the settings in the configuration file.

The following example shows how to set SFP port 1/0/27's high alarm threshold voltage as 5 V.

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/27

Switch(config-if)#ddm vlotage_threshold high_alarm 5

Switch(config-if)#show ddm configuration voltage

Voltage Threshold(V):

High Alarm Low Alarm High Warning Low Warning

Gi1/0/27

5.000000

--

--

--

...

Switch(config-if)#end

Switch#copy running-config startup-config

■ Configuring Bias Current Threshold

Follow these steps to configure the threshold of the DDM bias current on the specified SFP port.

Step 1 configure
Enter global configuration mode.

Step 2 interface { fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list }Enter interface configuration mode.
Step 3ddm bias_current_threshold { high_alarm | high_warning | low_alarm | low_warning } valuehigh_alarm: Specify the high threshold for the alarm. When the operating parameter rises above this value, action associated with the alarm will be taken.high_warning: Specify the high threshold for the warning. When the operating parameter rises above this value, action associated with the warning will be taken.low_alarm: Specify the low threshold for the alarm. When the operating parameter falls below this value, action associated with the alarm will be taken.low_warning: Specify the low threshold for the warning. When the operating parameter falls below this value, action associated with the warning will be taken.value: Enter the threshold value in mA. The valid values are from 0 to 131.

Step 4 show ddm configuration bias_current
Display the DDM bias current threshold of the SFP ports.
Step 5 end
Return to Privileged EXEC Mode.
Step 6 copy running-config startup-config
Save the settings in the configuration file.

The following example shows how to set SFP port 1/0/27's high alarm threshold bias current as 120 mA.

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/17

Switch(config-if)#ddm vlotage_threshold high_alarm 120

Switch(config-if)#show ddm configuration bias_current

Voltage Threshold(V):

High Alarm Low Alarm High Warning Low Warning

Gi1/0/27

120.000000

--

--

--

...

Switch(config-if)#end

Switch#copy running-config startup-config

■ Configuring Rx Power Threshold

Follow these steps to configure the threshold of the DDM Rx power on the specified SFP port.

Step 1 configure
Enter global configuration mode.

Step 2 interface { fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list }Enter interface configuration mode.
Step 3ddm rx_power_threshold { high_alarm | high_warning | low_alarm | low_warning } valuehigh_alarm: Specify the high threshold for the alarm. When the operating parameter rises above this value, action associated with the alarm will be taken.high_warning: Specify the high threshold for the warning. When the operating parameter rises above this value, action associated with the warning will be taken.low_alarm: Specify the low threshold for the alarm. When the operating parameter falls below this value, action associated with the alarm will be taken.low_warning: Specify the low threshold for the warning. When the operating parameter falls below this value, action associated with the warning will be taken.value: Enter the threshold value in mW. The valid values are from 0 to 6.5535.

Step 4 show ddm configuration rx_power
Display the DDM rx power threshold on the SFP ports.
Step 5 end
Return to Privileged EXEC Mode.
Step 6 copy running-config startup-config
Save the settings in the configuration file.

The following example shows how to set SFP port 1/0/27's high alarm threshold Rx power as 6 mW.

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/27

Switch(config-if)#ddm rx_power_threshold high_alarm 6

Switch(config-if)#show ddm configuration rx_power

Rx Power Threshold(mW):

High Alarm Low Alarm High Warning Low Warning

Gi1/0/27

6.000000

--

--

--

...

Switch(config-if)#end

Switch#copy running-config startup-config

■ Configuring Tx Power Threshold

Follow these steps to configure the threshold of the DDM Tx power on the specified SFP port.

Step 1 configure
Enter global configuration mode.

Step 2 interface { fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list }Enter interface configuration mode.
Step 3ddm tx_power_threshold { high_alarm | high_warning | low_alarm | low_warning } valuehigh_alarm: Specify the high threshold for the alarm. When the operating parameter rises above this value, action associated with the alarm will be taken.high_warning: Specify the high threshold for the warning. When the operating parameter rises above this value, action associated with the warning will be taken.low_alarm: Specify the low threshold for the alarm. When the operating parameter falls below this value, action associated with the alarm will be taken.low_warning: Specify the low threshold for the warning. When the operating parameter falls below this value, action associated with the warning will be taken.value: Enter the threshold value in mW. The valid values are from 0 to 6.5535.

Step 4 show ddm configuration tx_power

Display the DDM tx power threshold on the SFP ports.

Step 5 end
Return to Privileged EXEC Mode.
Step 6 copy running-config startup-config
Save the settings in the configuration file.

The following example shows how to set SFP port 1/0/27's high alarm threshold Tx power as 6 mW.

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/27

Switch(config-if)#ddm tx_power_threshold high_alarm 6

Switch(config-if)#show ddm configuration tx_power

Tx Power Threshold(mW) :

High Alarm Low Alarm High Warning Low Warning

Gi1/0/27 6.000000 -- -- --

...

Switch(config-if)#end

Switch#copy running-config startup-config

2.2.4 Viewing DDM Configuration

Follow these steps to view the DDM configuration.

Step 1 configure
Enter global configuration mode.

Step 2show ddm configuration { state | temperature | voltage | bias_current | tx_power | rx_power}state: Displays the DDM configuration state.temperature: Displays the threshold of the DDM temperature value.voltage: Displays the threshold of the DDM voltage value.bias_current: Displays the threshold of the DDM bias current value.tx_power: Displays the threshold of the DDM Tx Power value.rx_power: Displays the threshold of the DDM Rx Power value.

Step 3 end
Return to Privileged EXEC Mode.
Step 4 copy running-config startup-config
Save the settings in the configuration file.

The following example shows how to view SFP ports' Rx power threshold.

Switch#configure

Switch(config)#show ddm configuration rx_power

Rx Power Threshold(mW) :

High Alarm Low Alarm High Warning Low Warning

Gi1/0/27 6.000000 -- -- --

Gi1/0/28 -- -- -- --

Switch(config)#end

2.2.5 Viewing DDM Status

Follow these steps to view the DDM status, which is the digital diagnostic monitoring status of SFP modules inserted into the switch's SFP ports.

Step 1 configure

Enter global configuration mode.

Step 2 show ddm status

Displays all the monitoring status of SFP modules.

Step 3 end

Return to Privileged EXEC Mode.

The following example shows how to view SFP ports' DDM status.

Switch#configure

Switch(config)#show ddm status

Temperature(C)Rx Power(mW)Voltage(V)Data ReadyBias Current(mA)Rx LosTx Power(mW)Tx Fault
Gi1/0/27--------
--------
Gi1/0/28--------
--------

Switch(config)#end

3 Appendix: Default Parameters

Default settings of DDM are listed in the following table.

Table 3-1 Default Settings of DDM

Parameter Default Setting
DDM Status Enabled. All the SFP ports are being monitored.
ShutdownNone. The port will not be shut down even if the alarm or warning threshold is exceeded.

Part 6

Managing MAC Address Table

CHAPTERS

  1. MAC Address Table
  2. MAC Address Configurations
  3. Security Configurations
  4. Example for Security Configurations
  5. Appendix: Default Parameters

1 MAC Address Table

1.1 Overview

The MAC address table contains address information that the switch uses to forward packets. As shown below, the table lists map entries of MAC addresses, VLAN IDs and ports. These entries can be manually added or automatically learned by the switch. Based on the MAC-address-to-port mapping in the table, the switch can forward packets only to the associated port.

Table 1-1 The MAC Address Table

MAC Address VLAN ID Port Type Aging Status
00:00:00:00:00:011 1 DynamicAging
00:00:00:00:00:02 12 Static No-Aging
...

1.2 Supported Features

The address table of the switch contains dynamic addresses, static addresses and filtering addresses. For devices which support security configurations, you can configure notification traps and limit the number of MAC addresses in a VLAN for traffic safety.

Address Configurations

■ Dynamic address

Dynamic addresses are addresses learned by the switch automatically, and the switch regularly ages out those that are not in use. That is, the switch removes the MAC address entries related to a network device if no packet is received from the device within the aging time. And you can specify the aging time if needed.

■ Static address

Static addresses are manually added to the address table and do not age. For some relatively fixed connection, for example, frequently visited server, you can manually set the MAC address of the server as a static entry to enhance the forwarding efficiency of the switch.

■ Filtering address

Filtering addresses are manually added and determine the packets with specific source or destination MAC addresses that will should dropped by the switch.

Security Configurations

TP-LINK Omada TL-SG2008P - Security Configurations - 1

Note:

Security Configurations are only available on certain devices. To check whether your device supports this feature, refer to the actual web interface. If Security Configurations are available, there are L2 FEATURES > Switching > MAC Address > MAC Notifications and L2 FEATURES > Switching > MAC Address > MAC VLAN Security in the menu structure.

■ Configuring MAC Notification Traps

You can configure traps and SNMP (Simple Network Management Protocol) to monitor and receive notifications of the usage of the MAC address table and the MAC address change activity. For example, you can configure the switch to send notifications when a new MAC address is learned, so the administrator knows a new users accesses the network.

■ Limiting the Number of MAC Addresses in VLANs

You can configure VLAN Security to limit the number of MAC addresses that can be learned in specified VLANs. The switch will not learn addresses when the number of learned addresses has reached the limit, preventing the address table from being used up by broadcasting packets of MAC address attacks.

2

MAC Address Configurations

With MAC address table, you can:

■ Add static MAC address entries
■ Change the MAC address aging time
■ Add filtering address entries
■ View address table entries

2.1 Using the GUI

2.1.1 Adding Static MAC Address Entries

You can add static MAC address entries by manually specifying the desired MAC address or binding dynamic MAC address entries.

■ Adding MAC Addresses Manually

Choose the menu L2 FEATURES > Switching > MAC Address > Static Address and click

TP-LINK Omada TL-SG2008P - Adding Static MAC Address Entries - 1

Add

to load the following page.

Figure 2-1 Adding MAC Addresses Manually
TP-LINK Omada TL-SG2008P - Adding Static MAC Address Entries - 2

text_image Static Address MAC Address: (Format: 00-00-00-00-00-01) VLAN ID: (1-4094) Port: (Format: 1/0/1, input or choose below) UNIT1 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

Follow these steps to add a static MAC address entry:

1) Enter the MAC address, VLAN ID and select a port to bind them together as an address entry.

MAC Address Enter the static MAC address to be added to the static MAC address entry.

VLAN ID Specify an existing VLAN in which packets with the specific MAC address are received.

Port Specify a port to which packets with the specific MAC address are forwarded. The port must belong to the specified VLAN.

After you have added the static MAC address, if the corresponding port number of the MAC address is not correct, or the connected port (or the device) has been changed, the switch cannot forward the packets correctly. Please reset the static address entry appropriately.

2) Click Create.

■ Binding Dynamic Address Entries

If some dynamic address entries are frequently used, you can bind these entries as static entries.

Choose the menu L2 FEATURES > Switching > MAC Address > Dynamic Address to load the following page.

Figure 2-2 Binding Dynamic MAC Address Entries
TP-LINK Omada TL-SG2008P - Adding Static MAC Address Entries - 3

text_image Aging Config Auto Aging: ✓ Enable Aging Time: 300 seconds (10-630) Apply Dynamic Address Table All UNIT1 MAC Address VLAN ID Port Type Aging Status ✓ 30-B5-C2-BD-04-6E 1 1/0/22 Dynamic Aging □ 00-0A-EB-13-23-97 1 1/0/22 Dynamic Aging □ 00-0A-EB-13-23-7B 1 1/0/22 Dynamic Aging □ C4-6E-1F-BF-72-51 1 1/0/22 Dynamic Aging □ 00-19-66-35-E1-B0 1 1/0/22 Dynamic Aging Total: 5 1 entry selected.

Follow these steps to bind dynamic MAC address entries:

1) In the Dynamic Address Table section, Select your desired MAC address entries.
2) Click Bind, and then the selected entries will become static MAC address entries.

TP-LINK Omada TL-SG2008P - Adding Static MAC Address Entries - 4

Note:

  • In the same VLAN, once an address is configured as a static address, it cannot be set as a filtering address, and vice versa.
    • Multicast or broadcast addresses cannot be set as static addresses.
  • Ports in LAGs (Link Aggregation Group) are not supported for static address configuration.

2.1.2 Modifying the Aging Time of Dynamic Address Entries

Choose the menu L2 FEATURES > Switching > MAC Address > Dynamic Address to load the following page.

Figure 2-3 Modifying the Aging Time of Dynamic Address Entries
TP-LINK Omada TL-SG2008P - Modifying the Aging Time of Dynamic Address Entries - 1

text_image Aging Config Auto Aging: ✓ Enable Aging Time: 300 seconds (10-630) Apply

Follow these steps to modify the aging time of dynamic address entries:

1) In the Aging Config section, enable Auto Aging, and enter your desired length of time.

Auto AgingEnable Auto Aging, then the switch automatically updates the dynamic address table with the aging mechanism. By default, it is enabled.
Aging TimeSet the length of time that a dynamic entry remains in the MAC address table after the entry is used or updated. The valid values are from 10 to 630 seconds, and the default value is 300.A short aging time is applicable to networks where network topology changes frequently, and a long aging time is applicable to stable networks. We recommend that you keep the default value if you are unsure about settings in your case.

2) Click Apply.

2.1.3 Adding MAC Filtering Address Entries

Choose the menu L2 FEATURES > Switching > MAC Address > Filtering Address and click to load the following page.

Figure 2-4 Adding MAC Filtering Address Entries
TP-LINK Omada TL-SG2008P - Adding MAC Filtering Address Entries - 1

text_image Filtering Address MAC Address: (Format: 00-00-00-00-00-01) VLAN ID: (1-4094) Cancel Create

Follow these steps to add MAC filtering address entries:

1) Enter the MAC Address and VLAN ID.

MAC Address Specify the MAC address to be used by the switch to filter the received packets.

VLAN ID Specify an existing VLAN in which packets with the specific MAC address are dropped.

2) Click Create.

TP-LINK Omada TL-SG2008P - Adding MAC Filtering Address Entries - 2

Note:

  • In the same VLAN, once an address is configured as a filtering address, it cannot be set as a static address, and vice versa.
    • Multicast or broadcast addresses cannot be set as filtering addresses.

2.1.4 Viewing Address Table Entries

You can view entries in MAC address table to check your former operations and address information.

Choose the menu L2 FEATURES > Switching > MAC Address > Address Table and click

TP-LINK Omada TL-SG2008P - Viewing Address Table Entries - 1

Search to load the following page.

Figure 2-5 Viewing Address Table Entries
TP-LINK Omada TL-SG2008P - Viewing Address Table Entries - 2

text_image Address Table MAC Address VLAN ID Type Dynamic Static Filter Port (Format: 00-00-00-00-00-01) (1-4094) Clear Search 30-B5-C2-BD-20-CC 1 1/0/8 Dynamic Aging 00-0A-EB-13-23-97 1 1/0/8 Dynamic Aging 00-0A-EB-13-23-7B 1 1/0/8 Dynamic Aging 30-B5-C2-BD-20-5C 1 1/0/8 Dynamic Aging 00-0A-EB-13-A2-02 1 1/0/8 Dynamic Aging C4-6E-1F-BF-72-51 1 1/0/8 Dynamic Aging 00-19-66-35-E1-B0 1 1/0/8 Dynamic Aging Total: 7

2.2 Using the CLI

2.2.1 Adding Static MAC Address Entries

Follow these steps to add static MAC address entries:

Step 1 configure

Enter global configuration mode.

Step 2 mac address-table static mac-addr vid vid interface {fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port }

Bind the MAC address, VLAN and port together to add a static address to the VLAN.

mac-addr: Enter the MAC address, and packets with this destination address received in the specified VLAN are forwarded to the specified port. The format is xx:xx:xx:xx:xx:xx, for example, 00:00:00:00:00:01.

vid: Specify an existing VLAN in which packets with the specific MAC address are received.

port: Specify a port to which packets with the specific MAC address are forwarded. The port must belong to the specified VLAN.

Step 3 end

Return to privileged EXEC mode.

Step 4 copy running-config startup-config

Save the settings in the configuration file.

TP-LINK Omada TL-SG2008P - Adding Static MAC Address Entries - 1

Note:

  • In the same VLAN, once an address is configured as a static address, it cannot be set as a filtering address, and vice versa.
    • Multicast or broadcast addresses cannot be set as static addresses.
  • Ports in LAGs (Link Aggregation Group) are not supported for static address configuration.

The following example shows how to add a static MAC address entry with MAC address 00:02:58:4f:6c:23, VLAN 10 and port 1. When a packet is received in VLAN 10 with this address as its destination, the packet will be forwarded only to port 1/0/1.

Switch#configure

Switch(config)# mac address-table static 00:02:58:4f:6c:23 vid 10 interface gigabitEthernet 1/0/1

Switch(config)#show mac address-table static

MAC Address Table

MACVLANPortTypeAging
00:02:58:4f:6c:2310Gi1/0/1config staticno-aging

Total MAC Addresses for this criterion: 1

Switch(config)#end

Switch#copy running-config startup-config

2.2.2 Modifying the Aging Time of Dynamic Address Entries

Follow these steps to modify the aging time of dynamic address entries:

Step 1 configure

Enter global configuration mode.

Step 2 mac address-table aging-time

aging-time

Set your desired length of address aging time for dynamic address entries.

aging-time: Set the length of time that a dynamic entry remains in the MAC address table after the entry is used or updated. The valid values are from 10 to 630. Value 0 means the Auto Aging function is disabled. The default value is 300 and we recommend you keep the default value if you are unsure.

Step 3 end

Return to privileged EXEC mode.

Step 4 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to modify the aging time to 500 seconds. A dynamic entry remains in the MAC address table for 500 seconds after the entry is used or updated.

Switch#configure

Switch(config)# mac address-table aging-time 500

Switch(config)#show mac address-table aging-time

Aging time is 500 sec.

Switch(config)#end

Switch#copy running-config startup-config

2.2.3 Adding MAC Filtering Address Entries

Follow these steps to add MAC filtering address entries:

Step 1 configure

Enter global configuration mode.

Step 2 mac address-table filtering

mac-addr vid vid

Add the filtering address to the VLAN.

mac-addr: Specify a MAC address to be used by the switch to filter the received packets. The switch will drop packets of which the source address or destination address is the specified MAC address. The format is xx:xx:xx:xx:xx:xx, for example, 00:00:00:00:00:01.

vid: Specify an existing VLAN in which packets with the specific MAC address will be dropped.

Step 3 end

Return to privileged EXEC mode.

Step 4 copy running-config startup-config

Save the settings in the configuration file.

TP-LINK Omada TL-SG2008P - Step 4 copy running-config startup-config - 1

Note:

  • In the same VLAN, once an address is configured as a filtering address, it cannot be set as a static address, and vice versa.
    • Multicast or broadcast addresses cannot be set as filtering addresses.

The following example shows how to add the MAC filtering address 00:1e:4b:04:01:5d to VLAN 10. Then the switch will drop the packet that is received in VLAN 10 with this address as its source or destination.

Switch#configure

Switch(config)# mac address-table filtering 00:1e:4b:04:01:5d vid 10

Switch(config)#show mac address-table filtering

MAC Address Table

MACVLANPortTypeAging
-------------------
00:1e:4b:04:01:5d10filterno-aging

Total MAC Addresses for this criterion: 1

Switch(config)#end

Switch#copy running-config startup-config

3 Security Configurations

TP-LINK Omada TL-SG2008P - Security Configurations - 1

Note:

Security Configurations are only available on certain devices. To check whether your device supports this feature, refer to the actual web interface. If Security Configurations are available, there are L2 FEATURES > Switching > MAC Address > MAC Notifications and L2 FEATURES > Switching > MAC Address > MAC VLAN Security in the menu structure.

With security configurations of the MAC address table, you can:

■ Configure MAC notification traps
■ Limit the number of MAC addresses in VLANs

3.1 Using the GUI

3.1.1 Configuring MAC Notification Traps

Choose the menu L2 FEATURES > Switching > MAC Address > MAC Notification to load the following page.

Figure 3-1 Configuring MAC Notification Traps
TP-LINK Omada TL-SG2008P - Configuring MAC Notification Traps - 1

text_image MAC Notification Global Config Global Status: Enable Table Full Notification: Enable Notification Interval: 1 seconds(1-1000) Apply MAC Notification Port Config UNIT1 Port Learned Mode Change New MAC Learned ✓ 1/0/1 Disabled Disabled □ 1/0/2 Disabled Disabled □ 1/0/3 Disabled Disabled □ 1/0/4 Disabled Disabled □ 1/0/5 Disabled Disabled □ 1/0/6 Disabled Disabled □ 1/0/7 Disabled Disabled □ 1/0/8 Disabled Disabled □ 1/0/9 Disabled Disabled □ 1/0/10 Disabled Disabled Total: 28 1 entry selected Cancel Apply

Follow these steps to configure MAC notification traps:

1) In the MAC Notification Global Config section, enable this feature, configure the relevant options, and click Apply.

Global Status Enable MAC notification feature globally.

Table Full NotificationEnable Table Full Notification, and when address table is full, a notification will be generated and sent to the management host.
Notification IntervalSpecify the time value of Notification Interval. Notification Interval is the interval at which the New MAC Learned notifications are continuously sent.

2) In the MAC Notification Port Config section, select one or more ports to configure the notification status. Click Apply.

Learned Mode ChangeEnable Learned Mode Change, and when the learned mode of the specified port is changed, a notification will be generated and sent to the management host.
New MAC LearnedEnable New MAC Learned, and when the specified port learns a new MAC address, a notification will be generated and sent to the management host.

3) Configure SNMP and set a management host. For detailed SNMP configurations, please refer to Configuring SNMP & RMON.

3.1.2 Limiting the Number of MAC Addresses Learned in VLANs

■ For Certain Devices

Choose the menu L2 FEATURES > Switching > MAC Address > MAC VLAN Security to load the following page.

Figure 3-2 Configuring the MAC VLAN Security Mode

MAC VLAN Security Config

MAC VLAN Security Mode:

TP-LINK Omada TL-SG2008P - ■ For Certain Devices - 1

Drop

TP-LINK Omada TL-SG2008P - ■ For Certain Devices - 2

Forward

Apply

MAC VLAN Security Table

TP-LINK Omada TL-SG2008P - ■ For Certain Devices - 3

Add

TP-LINK Omada TL-SG2008P - ■ For Certain Devices - 4

Delete

VLAN IDMax Learned NumberCurrent Learned NumberOperation
No entries in this table.
Total: 0

Follow these steps to limit the number of MAC addresses in VLANs:

1) In the MAC VLAN Security Config section, select the security mode for all VLANs.

Drop Packets with new source MAC addresses in the VLAN will be dropped when the maximum number of MAC addresses is exceeded.

Forward Packets of new source MAC addresses will be forwarded but the addresses will not be learned when the maximum number of MAC addresses is exceeded.

2) In the MAC VLAN Security Table section, click Add to load the following page. Enter the VLAN ID and the Max Learned Number to limit the number of MAC addresses that can be learned in the specified VLAN.

Figure 3-3 Limiting the Number of MAC Addresses in VLANs
TP-LINK Omada TL-SG2008P - ■ For Certain Devices - 5

text_image VLAN Security Config VLAN ID: (1-4094) Max Learned Number: (0-16383) Cancel Create

VLAN ID Specify an existing VLAN in which you want to limit the number of MAC addresses.

Max Learned NumberSet the maximum number of MAC addresses in the specific VLAN. It ranges from 0 to 16383.
You can control the available address table space by setting maximum learned MAC number for VLANs. However, an improper maximum number can cause unnecessary floods in the network or a waste of address table space. Therefore, before you set the number limit, please be sure you are familiar with the network topology and the switch system configuration.

3) Click Create.

■ For Certain Devices

Choose the menu L2 FEATURES > Switching > MAC Address > MAC VLAN Security and click Add to load the following page.

Figure 3-4 Limiting the Number of MAC Addresses in VLANs
TP-LINK Omada TL-SG2008P - ■ For Certain Devices - 1

text_image VLAN Security Config VLAN ID: (1-4094) Max Learned Number: (0-16383) Mode: Drop Cancel Create

Follow these steps to limit the number of MAC addresses in VLANs:

1) Enter the VLAN ID to limit the number of MAC addresses that can be learned in the specified VLAN.

VLAN ID Specify an existing VLAN in which you want to limit the number of MAC addresses.

2) Enter your desired value in Max Learned Number to set a threshold.

Max Learned NumberSet the maximum number of MAC addresses in the specific VLAN. It ranges from 0 to 16383.You can control the available address table space by setting maximum learned MAC number for VLANs. However, an improper maximum number can cause unnecessary floods in the network or a waste of address table space. Therefore, before you set the number limit, please be sure you are familiar with the network topology and the switch system configuration.

3) Choose the mode that the switch adopts when the maximum number of MAC addresses in the specified VLAN is exceeded.

Drop Packets with new source MAC addresses in the VLAN will be dropped when the maximum number of MAC addresses in the specified VLAN is exceeded.

Forward Packets of new source MAC addresses will be forwarded but the addresses will not be learned when the maximum number of MAC addresses in the specified VLAN is exceeded.

4) Click Create.

3.2 Using the CLI

3.2.1 Configuring MAC Notification Traps

Follow these steps to configure MAC notification traps:

Step 1 configure
Enter global configuration mode.
Step 2mac address-table notification global-status {enable | disable}Enable MAC Notification globally.enable | disable: Enable or disable MAC Notification globally.
Step 3mac address-table notification table-full-status [enable | disable](Optional) Enable Table Full Notification.enable | disable: With Table Full Notification enabled, when address table is full, a notification will be generated and sent to the management host.
Step 4mac address-table notification interval timeSpecify the time value of Notification Interval. Notification Interval is the interval at which the New MAC Learned notifications are continuously sent.time: Specify the Notification Interval in seconds between 1 to 1000. By default, it is 1 second.
Step 5interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | ten-range gigabitEthernet port-list }Configure notification traps on the specified port.port/ port-list: The number or the list of the Ethernet port that you want to configure notification traps.
Step 6 mac address-table notification {[learn-mode-change enable | disable] [new-mac-learned enable | disable]}
Enable learn-mode-change, exceed-max-learned, or new-MAC-learned notification traps on the specified port.
enable | disable:Enable or disable learn-mode-change, exceed-max-learned, or new-MAC-learned notification traps on the specified port.
learn-mode-change: With learn-mode-change enabled, when the learned mode of the specified port is changed, a notification will be generated and sent to the management host.
new-mac-learned: With new-mac-learned enabled, when the specified port learns a new MAC address, a notification will be generated and sent to the management host.

Step 7 end

Return to privileged EXEC mode.

Step 8 copy running-config startup-config

Save the settings in the configuration file.

Now you have configured MAC notification traps. To receive notifications, you need to further enable SNMP and set a management host. For detailed SNMP configurations, please refer to Configuring SNMP & RMON.

The following example shows how to enable new-MAC-learned trap on port 1, and set the interval time as 10 seconds. After you have further configured SNMP, the switch will bundle notifications of new addresses in every 10 seconds and send to the management host.

Switch#configure

Switch(config)#mac address-table notification global-status enable

Switch(config)#mac address-table notification interval 10

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#mac address-table notification new-mac-learned enable

Switch(config-if)#show mac address-table notification interface gigabitEthernet 1/0/1

Mac Notification Global Config

Notification Global Status : enable

Table Full Notification Status: disable

Notification Interval : 10

Port LrnMode Change New Mac Learned

Gi1/0/1 disable enable

Switch(config-if)#end

Switch#copy running-config startup-config

3.2.2 Limiting the Number of MAC Addresses in VLANs

■ For Certain Devices

Follow these steps to limit the number of MAC addresses in VLANs:

Step 1 configure

Enter global configuration mode.

Step 2 mac address-table vlan-security mode {drop | forward}

Specify the VLAN security mode for all the VLANs.

drop | forward: The mode that the switch adopts when the maximum number of MAC addresses in the specified VLAN is exceeded.

drop: Packets of new source MAC addresses in the VLAN will be dropped when the maximum number of MAC addresses in the specified VLAN is exceeded.

forward: Packets of new source MAC addresses will be forwarded but the addresses not learned when the maximum number of MAC addresses in the specified VLAN is exceeded.

Step 3 mac address-table vlan-security vid

vid max-learn num

Configure the maximum number of MAC addresses in the specified VLAN and select a mode for the switch to adopt when the maximum number is exceeded.

vid: Specify an existing VLAN in which you want to limit the number of MAC addresses.

num: Set the maximum number of MAC addresses in the specific VLAN. It ranges from 0 to 16383.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to limit the number of MAC addresses to 100 in VLAN 10, and configure the switch to drop packets of new source MAC addresses when the limit is exceeded.

Switch#configure

Switch(config)#mac address-table vlan-security mode drop

Switch(config)#mac address-table vlan-security vid 10 max-learn 100

Switch(config)#show mac address-table vlan-security vid 10

VlanIdMax-learnCurrent-learnStatus
----------------
101000Drop

Switch(config)#end

Switch#copy running-config startup-config

■ For Certain Devices

Follow these steps to limit the number of MAC addresses in VLANs:

Step 1 configure

Enter global configuration mode.

Step 2 mac address-table security vid

vid max-learn num {drop | forward}

Configure the maximum number of MAC addresses in the specified VLAN and select a mode for the switch to adopt when the maximum number is exceeded.

vid: Specify an existing VLAN in which you want to limit the number of MAC addresses.

num: Set the maximum number of MAC addresses in the specific VLAN. It ranges from 0 to 16383.

drop | forward: The mode that the switch adopts when the maximum number of MAC addresses in the specified VLAN is exceeded.

drop: Packets of new source MAC addresses in the VLAN will be dropped when the maximum number of MAC addresses in the specified VLAN is exceeded.

forward: Packets of new source MAC addresses will be forwarded but the addresses not learned when the maximum number of MAC addresses in the specified VLAN is exceeded.

Step 3 end

Return to privileged EXEC mode.

Step 4 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to limit the number of MAC addresses to 100 in VLAN 10, and configure the switch to drop packets of new source MAC addresses when the limit is exceeded.

Switch#configure

Switch(config)#mac address-table security vid 10 max-learn 100 drop

Switch(config)#show mac address-table security vid 10

VlanIdMax-learnCurrent-learnStatus
----------------
101000Drop

Switch(config)#end

Switch#copy running-config startup-config

4 Example for Security Configurations

4.1 Network Requirements

Several departments are connected to the company network as shown in Figure 4-1. Now the Marketing Department that is in VLAN 10 has network requirements as follows:

■ Free the network system from illegal accesses and MAC address attacks by limiting the number of access users in this department to 100.
■ Assist the network manager supervising the network with notifications of any new access users.

Figure 4-1 The Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["Internet"] --> B["Switch"]
    B --> C["Gi1/0/1"]
    B --> D["Gi1/0/2"]
    B --> E["Gi1/0/3"]
    C --> F["Marketing Department VLAN 10"]
    C --> G["R&D Department VLAN 30"]
    D --> H["..."]

4.2 Configuration Scheme

VLAN Security can be configured to limit the number of access users and in this way to prevent illegal accesses and MAC address attacks.

MAC Notification and SNMP can be configured to monitor the interface which is used by the Marketing Department. Enable the new-MAC-learned notification and the SNMP, then the network manager can get notifications when new users access the network.

Demonstrated with T2600G-28TS, this chapter provides configuration procedures in two ways: using the GUI and using the CLI.

4.3 Using the GUI

1) Choose the menu L2 FEATURES > Switching > MAC Address > MAC VLAN Security and click Add to load the following page. Set the maximum number of MAC address in VLAN 10 as 100, choose drop mode and click Create.

Figure 4-2 Configuring VLAN Security
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image VLAN Security Config VLAN ID: 10 (1-4094) Max Leamed Number: 100 (0-16383) Mode: Drop Cancel Create

2) Choose the menu L2 FEATURES > Switching > MAC Address > MAC Notification to load the following page. Enable Global Status, set notification interval as 10 seconds, and click Apply. Then, enable new-mac-learned trap on port 1/0/2 and click Apply.

Figure 4-3 Configuring New-MAC-learned Traps
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image MAC Notification Global Config Global Status: ✓ Enable Table Full Notification: ☐ Enable Notification Interval: 10 seconds (1-1000) Apply MAC Notification Port Config UNIT1 Port Learned Mode Change New MAC Learned Enable ✓ 1/0/1 Disabled Disabled ✓ 1/0/2 Disabled Enabled 1/0/3 Disabled Disabled 1/0/4 Disabled Disabled 1/0/5 Disabled Disabled 1/0/6 Disabled Disabled 1/0/7 Disabled Disabled 1/0/8 Disabled Disabled 1/0/9 Disabled Disabled 1/0/10 Disabled Disabled Total: 28 1 entry selected. Cancel Apply

3) Click Save the settings.
4) Enable SNMP and set a management host. For detailed SNMP configurations, please refer to Configuring SNMP & RMON.

4.4 Using the CLI

1) Set the maximum number of MAC address in VLAN 10 as 100, and choose drop mode.
Switch#configure
Switch(config)#mac address-table security vid 10 max-learn 100 drop
2) Configure the new-MAC-learned trap on port 1/0/2 and set notification interval as 10 seconds.
Switch(config)#mac address-table notification global-status enable
Switch(config)#mac address-table notification interval 10
Switch(config)#interface gigabitEthernet 1/0/2
Switch(config-if)#mac address-table notification new-mac-learned enable
Switch(config-if)#end
Switch#copy running-config startup-config

3) Configure SNMP and set a management host. For detailed SNMP configurations, please refer to Configuring SNMP & RMON.

Verify the Configurations

Verify the configuration of VLAN Security.

Switch#show mac address-table security vid 10

VlanIdMax-learnCurrent-learnStatus
----------------
101000Drop

Verify the configuration of MAC Notification on port 1/0/2.

Switch#show mac address-table notification interface gigabitEthernet 1/0/2

Port LrnMode Change New Mac Learned

Gi1/0/2 disable enable

5 Appendix: Default Parameters

Default settings of the MAC Address Table are listed in the following tables.

Table 5-1 Entries in the MAC Address Table

Parameter Default Setting
Static Address Entries None
Dynamic Address Entries Auto-learning
Filtering Address Entries None

Table 5-2 Default Settings of Dynamic Address Table

Parameter Default Setting
Auto Aging Enabled
Aging Time 300 seconds

Table 5-3 Default Settings of MAC Notification

Parameter Default Setting
Global Status Disabled
Table Full Notification Disabled
Notification Interval 1 Second
Learned Mode Change NotificationDisabled
Exceed Max Learned NotificationDisabled
New MAC Learned NotificationDisabled

Part 7

Configuring

802.1Q VLAN

CHAPTERS

  1. Overview
  2. 802.1Q VLAN Configuration
  3. Configuration Example
  4. Appendix: Default Parameters

1 Overview

VLAN (Virtual Local Area Network) is a network technique that solves broadcasting issues in local area networks. It is usually applied in the following occasions:

■ To restrict broadcast domain: VLAN technique divides a big local area network into several VLANs, and all VLAN traffic remains within its VLAN. It reduces the influence of broadcast traffic in Layer 2 network to the whole network.
■ To enhance network security: Devices from different VLANs cannot achieve Layer 2 communication, and thus users can group and isolate devices to enhance network security.
■ For easier management: VLANs group devices logically instead of physically, so devices in the same VLAN need not be located in the same place. It eases the management of devices in the same work group but located in different places.

2 802.1Q VLAN Configuration

To complete 802.1Q VLAN configuration, follow these steps:

1) Configure the VLAN, including creating a VLAN and adding the desired ports to the VLAN.
2) Configure port parameters for 802.1Q VLAN.

2.1 Using the GUI

2.1.1 Configuring the VLAN

Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > VLAN Config and click to load the following page.

Figure 2-1 Configuring VLAN
TP-LINK Omada TL-SG2008P - Configuring the VLAN - 1

text_image VLAN Config VLAN ID: (2-4094, format: 2,4-5,8) VLAN Name: (1-16 characters) Untagged Ports Port: (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Tagged Ports Port: (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 Selected Unselected Not Available Cancel Create

Follow these steps to configure VLAN:

1) Enter a VLAN ID and a description for identification to create a VLAN.

VLAN ID Enter a VLAN ID for identification with the values between 2 and 4094.

VLAN Name Give a VLAN description for identification with up to 16 characters.

2) Select the untagged port(s) and the tagged port(s) respectively to add to the created VLAN based on the network topology.

Untagged port The selected ports will forward untagged packets in the target VLAN.

Tagged port The selected ports will forward tagged packets in the target VLAN.

3) Click Apply.

2.1.2 Configuring Port Parameters for 802.1Q VLAN

Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > Port Config to load the following page.

Figure 2-2 Configuring the Port
TP-LINK Omada TL-SG2008P - Configuring Port Parameters for 802.1Q VLAN - 1

text_image Port Config UNIT1 LAGS Port PVID Ingress Checking Acceptable Frame Types LAG Details ✓ 1/0/1 1 Enabled Admit All --- Details □ 1/0/2 1 Enabled Admit All --- Details □ 1/0/3 1 Enabled Admit All --- Details □ 1/0/4 1 Enabled Admit All --- Details □ 1/0/5 1 Enabled Admit All --- Details □ 1/0/6 1 Enabled Admit All --- Details □ 1/0/7 1 Enabled Admit All --- Details □ 1/0/8 1 Enabled Admit All --- Details □ 1/0/9 1 Enabled Admit All --- Details □ 1/0/10 1 Enabled Admit All --- Details Total: 28 1 entry selected. Cancel Apply

Select a port and configure the parameters. Click Apply.

PVID Set the default VLAN ID of the port. Valid values are from 1 to 4094. It is used mainly in the following two ways:
When the port receives an untagged packet, the switch inserts a VLAN tag to the packet based on the PVID.
Ingress CheckingEnable or disable Ingress Checking. With this function enabled, the port will accept the packet of which the VLAN ID is in the port's VLAN list and discard others. With this function disabled, the port will forward the packet directly.
Acceptable Frame TypesSelect the acceptable frame type for the port and the port will perform this operation before Ingress Checking.
Admit All: The port will accept both the tagged packets and the untagged packets.
Tagged Only: The port will accept the tagged packets only.

LAG Displays the LAG (Link Aggregation Group) which the port belongs to.

Details Click the Details button to view the VLANs to which the port belongs.

2.2 Using the CLI

2.2.1 Creating a VLAN

Follow these steps to create a VLAN:

Step 1 configure
Enter global configuration mode.

Step 2 vlanvlan-listWhen you enter a new VLAN ID, the switch creates a new VLAN and enters VLAN configuration mode; when you enter an existing VLAN ID, the switch directly enters VLAN configuration mode.vlan-list: Specify the ID or the ID list of the VLAN(s) for configuration. Valid values are from 2 to 4094, for example, 2-3,5.
Step 3 namedescript(Optional) Specify a VLAN description for identification.descript: The length of the description should be 1 to 16 characters.
Step 4 show vlan [ idvlan-list ]Show the global information of the specified VLAN(s). When no VLAN is specified, this command shows global information of all 802.1Q VLANs.vlan-list: Specify the ID or the ID list of the VLAN(s) to show information. Valid values are from 1 to 4094.
Step 5 endReturn to privileged EXEC mode.
Step 6 copy running-config startup-configSave the settings in the configuration file.

The following example shows how to create VLAN 2 and name it as RD:

Switch#configure

Switch(config)#vlan 2

Switch(config-vlan)#name RD

Switch(config-vlan)#show vlan id 2

VLANNameStatusPorts
----------------
2RDactive

Switch(config-vlan)#end

Switch#copy running-config startup-config

2.2.2 Adding the Port to the Specified VLAN

Follow these steps to add the port to the specified VLAN:

Step 1 configure
Enter global configuration mode.
Step 2 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}
Enter interface configuration mode.
Step 3 switchport general allowed vlanvlan-list { tagged | untagged }
Add ports to the specified VLAN.
vlan-list: Specify the ID or ID list of the VLAN(s) that the port will be added to. The ID ranges from 1 to 4094.
tagged | untagged: Select the egress rule for the port.
Step 4show interface switchport [fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel lag-id]
Verify the information of the port.
Step 5 end
Return to privileged EXEC mode.
Step 6 copy running-config startup-config
Save the settings in the configuration file.

The following example shows how to add the port 1/0/5 to VLAN 2, and specify its egress rule as tagged:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/5

Switch(config-if)#switchport general allowed vlan 2 tagged

Switch(config-if)#show interface switchport gigabitEthernet 1/0/5

Port Gi1/0/5:

PVID: 2

Acceptable frame type: All

Ingress Checking: Enable

Member in LAG: N/A

Link Type: General

Member in VLAN:

Vlan Name Egress-rule

1 System-VLAN Untagged

2 RD Tagged

Switch(config-if)#end

Switch#copy running-config startup-config

2.2.3 Configuring the Port

Follow these steps to configure the port:

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet

port | range fastEthernet port-list | gigabitEthernet port | range

gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}

Enter interface configuration mode.

Step 3 switchport pvid

vlan-id

Configure the PVID of the port(s). By default, it is 1.

vlan-id: The default VLAN ID of the port with the values between 1 and 4094.

Step 4 switchport check ingress

Enable or disable Ingress Checking. With this function enabled, the port will accept the packet of which the VLAN ID is in the port's VLAN list and discard others. With this function disabled, the port will forward the packet directly.

Step 5

switchport acceptable frame {all | tagged}

Select the acceptable frame type for the port and the port will perform this operation before Ingress Checking.

all: The port will accept both the tagged packets and the untagged packets.

tagged: The port will accept the tagged packets only.

Step 6 end

Return to privileged EXEC mode.

Step 7 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to configure the PVID of port 1/0/5 as 2, enable the ingress checking and set the acceptable frame type as all:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/5

Switch(config-if)#switchport pvid 2

Switch(config-if)#switchport check ingress

Switch(config-if)#switchport acceptable frame all

Switch(config-if)#show interface switchport gigabitEthernet 1/0/5

Port Gi1/0/5:

PVID: 2

Acceptable frame type: All

Ingress Checking: Enable

Member in LAG: N/A

Link Type: General

Member in VLAN:

Vlan Name Egress-rule


1 System-VLAN Untagged

Switch(config-if)#end

Switch#copy running-config startup-config

3 Configuration Example

3.1 Network Requirements

■ Offices of Department A and Department B in the company are located in different places, and some computers in different offices connect to the same switch.
It is required that computers can communicate with each other in the same department but not with computers in the other department.

3.2 Configuration Scheme

■ Divide computers in Department A and Department B into two VLANs respectively so that computers can communicate with each other in the same department but not with computers in the other department.
■ Terminal devices like computers usually do not support VLAN tags. Add untagged ports to the corresponding VLANs and specify the PVID.
■ The intermediate link between two switches carries traffic from two VLANs simultaneously. Add the tagged ports to both VLANs.

3.3 Network Topology

The figure below shows the network topology. Host A1 and Host A2 are in Department A, while Host B1 and Host B2 are in Department B. Switch 1 and Switch 2 are located in two different places. Host A1 and Host B1 are connected to port 1/0/2 and port 1/0/3 on Switch 1 respectively, while Host A2 and Host B2 are connected to port 1/0/6 and port 1/0/7 on Switch 2 respectively. Port 1/0/4 on Switch 1 is connected to port 1/0/8 on Switch 2.

Figure 3-1 Network Topology
TP-LINK Omada TL-SG2008P - Network Topology - 1

flowchart
graph TD
    subgraph VLAN 10
        HostA1["Host A1"] -->|Gi1/0/2| Switch1["Switch 1"]
        HostA2["Host A2"] -->|Gi1/0/2| Switch1
        Switch1 -->|Gi1/0/4| Switch2["Switch 2"]
        Switch2 -->|Gi1/0/6| HostB1["Host B1"]
        Switch2 -->|Gi1/0/7| HostB2["Host B2"]
        Switch1 -->|Gi1/0/8| Switch2
    end
    subgraph VLAN 20
        Switch1 -->|Gi1/0/3| Switch1
        Switch1 -->|Gi1/0/4| Switch2
        Switch2 -->|Gi1/0/7| HostB2
        Switch2 -->|Gi1/0/8| HostB1
        Switch2 --> HostB2
    end

Demonstrated with T1600G-28TS, the following sections provide configuration procedure in two ways: using the GUI and using the CLI.

3.4 Using the GUI

The configurations of Switch 1 and Switch 2 are similar. The following introductions take Switch 1 as an example.

1) Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > VLAN Config and click to load the following page. Create VLAN 10 with the description of Department_A. Add port 1/0/2 as an untagged port and port 1/0/4 as a tagged port to VLAN 10. Click Create.

Figure 3-2 Creating VLAN 10 for Department A
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image VLAN Config VLAN ID: 10 (2-4094, format: 2,4-5,8) VLAN Name: Department_A (1-16 characters) Untagged Ports Port: 1/0/2 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Tagged Ports Port: 1/0/4 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

2) Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > VLAN Config and click to load the following page. Create VLAN 20 with the description of Department_B. Add port 1/0/3 as an untagged port and port 1/0/4 as a tagged port to VLAN 20. Click Create.

Figure 3-3 Creating VLAN 20 for Department B
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image VLAN Config VLAN ID: 20 (2-4094, format: 2.4-5.8) VLAN Name: Department_B (1-16 characters) Untagged Ports Port: 1/0/3 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Tagged Ports Port: 1/0/4 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

3) Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > Port Config to load the following page. Set the PVID of port 1/0/2 as 10 and click Apply. Set the PVID of port 1/0/3 as 20 and click Apply.

Figure 3-4 Specifying the PVID for the Ports
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image Port Config UNIT1 LAGS Port PVID Ingress Checking Acceptable Frame Types LAG Details 20 ▼ ▼ 1/0/1 1 Enabled Admit All --- Details 1/0/2 10 Enabled Admit All --- Details ✓ 1/0/3 20 Enabled Admit All --- Details 1/0/4 1 Enabled Admit All --- Details 1/0/5 1 Enabled Admit All --- Details 1/0/6 1 Enabled Admit All --- Details 1/0/7 1 Enabled Admit All --- Details 1/0/8 1 Enabled Admit All --- Details 1/0/9 1 Enabled Admit All --- Details 1/0/10 1 Enabled Admit All --- Details Total: 28 1 entry selected. Cancel Apply

4) Click save the settings.

3.5 Using the CLI

The configurations of Switch 1 and Switch 2 are similar. The following introductions take Switch 1 as an example.

1) Create VLAN 10 for Department A, and configure the description as Department-A. Similarly, create VLAN 20 for Department B, and configure the description as Department-B.

Switch_1#configure

Switch_1(config)#vlan 10

Switch_1(config-vlan)#name Department-A

Switch_1(config-vlan)#exit

Switch_1(config)#vlan 20

Switch_1(config-vlan)#name Department-B

Switch_1(config-vlan)#exit

2) Add untagged port 1/0/2 and tagged port 1/0/4 to VLAN 10. Add untagged port 1/0/3 and tagged port 1/0/4 to VLAN 20.

Switch_1(config)#interface gigabitEthernet 1/0/2

Switch_1(config-if)#switchport general allowed vlan 10 untagged

Switch_1(config-if)#exit

Switch_1(config)#interface gigabitEthernet 1/0/3

Switch_1(config-if)#switchport general allowed vlan 20 untagged

Switch_1(config-if)#exit

Switch_1(config)#interface gigabitEthernet 1/0/4

Switch_1(config-if)#switchport general allowed vlan 10 tagged

Switch_1(config-if)#switchport general allowed vlan 20 tagged

Switch_1(config-if)#exit

3) Set the PVID of port 1/0/2 as 10, and set the PVID of port 1/0/3 as 20.

Switch_1(config)#interface gigabitEthernet 1/0/2

Switch_1(config-if)#switchport pvid 10

Switch_1(config-if)#exit

Switch_1(config)#interface gigabitEthernet 1/0/3

Switch_1(config-if)#switchport pvid 20

Switch_1(config-if)#end

Switch_1#copy running-config startup-config

Verify the Configurations

Verify the VLAN configuration:

Switch_1#show vlan

VLANNameStatusPorts
1System-VLANactiveGi1/0/1, Gi1/0/2, Gi1/0/3, Gi1/0/4,Gi1/0/5, Gi1/0/6, Gi1/0/7, Gi1/0/8,Gi1/0/9, Gi1/0/10, Gi1/0/11, Gi1/0/12,Gi1/0/13, Gi1/0/14, Gi1/0/15, Gi1/0/16,Gi1/0/17, Gi1/0/18, Gi1/0/19, Gi1/0/20,Gi1/0/21, Gi1/0/22, Gi1/0/23, Gi1/0/24,Gi1/0/25, Gi1/0/26, Gi1/0/27, Gi1/0/28
10Department-AactiveGi1/0/2, Gi1/0/4
20Department-BactiveGi1/0/3, Gi1/0/4

Primary Secondary Type Ports

Verify the VLAN configuration:

Switch_1(config)#show interface switchport

PortLAGTypePVIDAcceptable frame typeIngress Checking
-----------------------
Gi1/0/1N/AGeneral1AllEnable
Gi1/0/2N/AGeneral10AllEnable
Gi1/0/3N/AGeneral20AllEnable
Gi1/0/4N/AGeneral1AllEnable
Gi1/0/5N/AGeneral1AllEnable

...

4 Appendix: Default Parameters

Default settings of 802.1Q VLAN are listed in the following table.

Table 4-1 Default Settings of 802.1Q VLAN

Parameter Default Setting
VLAN ID 1
PVID 1
Ingress Checking Enabled
Acceptable Frame Types Admit All

Part 8

Configuring MAC VLAN

CHAPTERS

  1. Overview
  2. MAC VLAN Configuration
  3. Configuration Example
  4. Appendix: Default Parameters

1 Overview

VLAN is generally divided by ports. It is a common way of division but isn't suitable for those networks that require frequent topology changes. With the popularity of mobile office, at different times a terminal device may access the network via different ports. For example, a terminal device that accessed the switch via port 1 last time may change to port 2 this time. If port 1 and port 2 belong to different VLANs, the user has to re-configure the switch to access the original VLAN. Using MAC VLAN can free the user from such a problem. It divides VLANs based on the MAC addresses of terminal devices. In this way, terminal devices always belong to their MAC VLANs even when their access ports change.

The figure below shows a common application scenario of MAC VLAN.

Figure 1-1 Common Application Scenario of MAC VLAN
TP-LINK Omada TL-SG2008P - Overview - 1

flowchart
graph TD
    ServerA["Server A VLAN 10"] --> Switch3["Switch 3"]
    ServerB["Server B VLAN 20"] --> Switch3
    Switch1["Switch 1 Switch 2"] --> Switch3
    Switch1 --> MeetingRoom1["Meeting Room 1"]
    Switch1 --> LaptopA["Laptop A"]
    Switch1 --> LaptopB["Laptop B"]
    Switch3 --> Switch1
    Switch3 --> Switch2["Switch 2"]
    Switch3 --> Switch3

Two departments share all the meeting rooms in the company, but use different servers and laptops. Department A uses Server A and Laptop A, while Department B uses Server B and Laptop B. Server A is in VLAN 10 while Server B is in VLAN 20. It is required that Laptop A can only access Server A and Laptop B can only access Server B, no matter which meeting room the laptops are being used in. To meet this requirement, simply bind the MAC addresses of the laptops to the corresponding VLANs respectively. In this way, the MAC address determines the VLAN each laptop joins. Each laptop can access only the server in the VLAN it joins.

2 MAC VLAN Configuration

To complete MAC VLAN configuration, follow these steps:

1) Configure 802.1Q VLAN.
2) Bind the MAC address to the VLAN.
3) Enable MAC VLAN for the port.

Configuration Guidelines

When a port in a MAC VLAN receives an untagged data packet, the switch will first check whether the source MAC address of the data packet has been bound to the MAC VLAN. If yes, the switch will insert the corresponding tag to the data packet and forward it within the VLAN. If no, the switch will continue to match the data packet with the matching rules of other VLANs (such as the protocol VLAN). If there is a match, the switch will forward the data packet. Otherwise, the switch will process the data packet according to the processing rule of the 802.1 Q VLAN. When the port receives a tagged data packet, the switch will directly process the data packet according to the processing rule of the 802.1 Q VLAN.

2.1 Using the GUI

2.1.1 Configuring 802.1Q VLAN

Before configuring MAC VLAN, create an 802.1Q VLAN and set the port type according to network requirements. For details, refer to Configuring 802.1Q VLAN.

2.1.2 Binding the MAC Address to the VLAN

Choose the menu L2 FEATURES > VLAN > MAC VLAN and click to load the following page.

Figure 2-1 Creating MAC VLAN
TP-LINK Omada TL-SG2008P - Binding the MAC Address to the VLAN - 1

text_image MAC VLAN Config MAC Address: (Format: 00-00-00-00-00-01) Description: (1-8 characters) VLAN: ID Name (1-4094) Cancel Create

Follow these steps to bind the MAC address to the 802.1Q VLAN:

1) Enter the MAC address of the device, give it a description, and enter the VLAN ID to bind it to the VLAN.

MAC Address Enter the MAC address of the device in the format of 00-00-00-00-00-01.

Description Give a MAC address description for identification with up to 8 characters.

VLAN ID/Name Enter the ID number or name of the 802.1Q VLAN that will be bound to the MAC VLAN..

2) Click Create.

TP-LINK Omada TL-SG2008P - Binding the MAC Address to the VLAN - 2

Note:

One MAC address can be bound to only one VLAN.

2.1.3 Enabling MAC VLAN for the Port

By default, MAC VLAN is disabled on all ports. You need to enable MAC VLAN for your desired ports manually.

Choose the menu L2 FEATURES > VLAN > MAC VLAN to load the following page.

Figure 2-2 Enabling MAC VLAN for the Port
TP-LINK Omada TL-SG2008P - Enabling MAC VLAN for the Port - 1

text_image Port Enable UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Apply MAC VLAN Config ID MAC Address Description VLAN ID VLAN Name Operation No entries in this table. Total: 0

In the Port Enable section, select the desired ports to enable MAC VLAN, and click Apply.

TP-LINK Omada TL-SG2008P - Enabling MAC VLAN for the Port - 2

Note:

The member port of an LAG (Link Aggregation Group) follows the configuration of the LAG and not its own. The configurations of the port can take effect only after it leaves the LAG.

2.2 Using the CLI

2.2.1 Configuring 802.1Q VLAN

Before configuring MAC VLAN, create an 802.1Q VLAN and set the port type according to network requirements. For details, refer to Configuring 802.1Q VLAN.

2.2.2 Binding the MAC Address to the VLAN

Follow these steps to bind the MAC address to the VLAN:

Step 1 configure

Enter global configuration mode.

Step 2 mac-vlan mac-address

mac-addr vlan vlan-id [description descript]

Bind the MAC address to the VLAN.

mac-addr: Specify the MAC address of the device in the format of xx:xx:xx:xx:xx:xx.

vlan-id: Enter the ID number of the 802.1Q VLAN that will be bound to the MAC VLAN.

descript: Specify the MAC address description for identification, with up to 8 characters.

Step 3 show mac-vlan { all | mac-address

mac-addr | vlan vlan-id }

Verify the configuration of MAC VLAN.

vid: Specify the MAC VLAN to be displayed.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to bind the MAC address 00:19:56:8A:4C:71 to VLAN 10, with the address description as Dept.A.

Switch#configure

Switch(config)#mac-vlan mac-address 00:19:56:8a:4c:71 vlan 10 description Dept.A

Switch(config)#show mac-vlan vlan 10

MAC-Addr

Name

VLAN-ID

00:19:56:8A:4C:71

Dept.A

10

Switch(config)#end

Switch#copy running-config startup-config

2.2.3 Enabling MAC VLAN for the Port

Follow these steps to enable MAC VLAN for the port:

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}Enter interface configuration mode.

Step 3 mac-vlan

Enable MAC VLAN for the port.

Step 4 show mac-vlan interface

Verify the configuration of MAC VLAN on each interface.

Step 5 end

Return to privileged EXEC mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable MAC VLAN for port 1/0/1.

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#mac-vlan

Switch(config-if)#show mac-vlan interface

Port STATUS

Gi1/0/1 Enable

Gi1/0/2 Disable

...

Switch(config-if)#end

Switch#copy running-config startup-config

3 Configuration Example

3.1 Network Requirements

Two departments share all the meeting rooms in the company, but use different servers and laptops. Department A uses Server A and Laptop A, while Department B uses Server B and Laptop B. Server A is in VLAN 10 while Server B is in VLAN 20. It is required that Laptop A can only access Server A and Laptop B can only access Server B, no matter which meeting room the laptops are being used in. The figure below shows the network topology.

Figure 3-1 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    ServerA["Server A VLAN 10"] --> Switch1["Switch 1 Switch 2"]
    ServerB["Server B VLAN 20"] --> Switch1
    Switch1 -->|Gi1/0/2 Gi1/0/2| Switch3["Switch 3 Gi1/0/3Gi1/0/2"]
    Switch3 -->|Gi1/0/5Gi1/0/4| Switch1
    Switch1 -->|Gi1/0/3Gi1/0/2| Switch3
    Switch1 -->|Gi1/0/1Gi1/0/1| MeetingRoom1["Meeting Room 1"]
    Switch1 -->|Gi1/0/2 Gi1/0/2| MeetingRoom2["Meeting Room 2"]
    Switch1 -->|Gi1/0/1Gi1/0/1| LaptopA["Laptop A 00-19-56-8A-4C-71"]
    Switch1 -->|Gi1/0/2 Gi1/0/2| LaptopB["Laptop B 00-19-56-82-3B-70"]

3.2 Configuration Scheme

You can configure MAC VLAN to meet this requirement. On Switch 1 and Switch 2, bind the MAC addresses of the laptops to the corresponding VLANs respectively. In this way, each laptop can access only the server in the VLAN it joins, no matter which meeting room the laptops are being used in. The overview of the configuration is as follows:

1) Create VLAN 10 and VLAN 20 on each of the three switches and add the ports to the VLANs based on the network topology. For the ports connecting the laptops, set the

egress rule as Untagged; for the ports connecting to other switch, set the egress rule as Tagged.

2) On Switch 1 and Switch 2, bind the MAC addresses of the laptops to their corresponding VLANs, and enable MAC VLAN for the ports.

Demonstrated with T1600G-28TS, the following sections provide configuration procedure in two ways: using the GUI and using the CLI.

3.3 Using the GUI

■ Configurations for Switch 1 and Switch 2

The configurations of Switch 1 and Switch 2 are similar. The following introductions take Switch 1 as an example.

1) Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > VLAN Config and click Add to load the following page. Create VLAN 10, and add untagged port 1/0/1 and tagged port 1/0/2 to VLAN 10. Click Create.

Figure 3-2 Creating VLAN 10
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch 1 and Switch 2 - 1

text_image VLAN Config VLAN ID: 10 (2-4094, format: 2,4-5,8) VLAN Name: Department_A (1-16 characters) Untagged Ports Port: 1/0/1 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Tagged Ports Port: 1/0/2 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

2) Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > VLAN Config and click Add to load the following page. Create VLAN 20, and add untagged port 1/0/1 and tagged port 1/0/2 to VLAN 20. Click Create.

Figure 3-3 Creating VLAN 20
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch 1 and Switch 2 - 2

text_image VLAN Config VLAN ID: 20 (2-4094, format: 2,4-5,8) VLAN Name: Department_B (1-16 characters) Untagged Ports Port: 1/0/1 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Tagged Ports Port: 1/0/2 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

3) Choose the menu L2 FEATURES > VLAN > MAC VLAN and click Add to load the following page. Specify the corresponding parameters and click Create to bind the MAC address of Laptop A to VLAN 10 and bind the MAC address of Laptop B to VLAN 20.

Figure 3-4 Creating MAC VLAN
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch 1 and Switch 2 - 3

text_image MAC VLAN Config MAC Address: 00-19-56-8A-4C-71 (Format: 00-00-00-00-01) Description: PCA (1-8 characters) VLAN: ID Name (1-4094) 10 Cancel Create

4) Choose the menu L2 FEATURES > VLAN > MAC VLAN to load the following page. In the Port Enable section select port 1/0/1 and click Apply to enable MAC VLAN.

Figure 3-5 Enabling MAC VLAN for the Port
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch 1 and Switch 2 - 4

text_image Port Enable UNIT1 LAGS Select All 2 4 5 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Apply MAC VLAN Config ID MAC Address Description VLAN ID VLAN Name Operation 1 00-19-56-8a-4c-71 PCA 10 Department-A 2 00-19-56-82-3b-70 PCB 20 Department-B Total: 2

5) Click Save the settings.

■ Configurations for Switch 3

1) Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > VLAN Config and click

Add to load the following page. Create VLAN 10, and add untagged port 1/0/4 and tagged ports 1/0/2-3 to VLAN 10. Click Create.

Figure 3-6 Creating VLAN 10
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch 1 and Switch 2 - 5

text_image VLAN Config VLAN ID: 10 (2-4094, format: 2,4-5,8) VLAN Name: Department_A (1-16 characters) Untagged Ports Port: 1/0/4 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Tagged Ports Port: 1/0/2-3 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

2) Click Create to load the following page. Create VLAN 20, and add untagged port 1/0/5 and tagged ports 1/0/2-3 to VLAN 20. Click Create.

Figure 3-7 Creating VLAN 20
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch 1 and Switch 2 - 6

text_image VLAN Config VLAN ID: 20 (2-4094, format: 2,4-5,8) VLAN Name: Department_B (1-16 characters) Untagged Ports Port: 1/0/5 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Tagged Ports Port: 1/0/2-3 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

3) Click Save the settings.

3.4 Using the CLI

■ Configurations for Switch 1 and Switch 2

The configurations of Switch 1 and Switch 2 are the same. The following introductions take Switch 1 as an example.

1) Create VLAN 10 for Department A and create VLAN 20 for Department B.

Switch_1#configure

Switch_1(config)#vlan 10

Switch_1(config-vlan)#name deptA

Switch_1(config-vlan)#exit

Switch_1(config)#vlan 20

Switch_1(config-vlan)#name deptB

Switch_1(config-vlan)#exit

2) Add tagged port 1/0/2 and untagged port 1/0/1 to both VLAN 10 and VLAN 20. Then enable MAC VLAN on port 1/0/1.

Switch_1(config)#interface gigabitEthernet 1/0/2

Switch_1(config-if)#switchport general allowed vlan 10,20 tagged

Switch_1(config-if)#exit

Switch_1(config)#interface gigabitEthernet 1/0/1

Switch_1(config-if)#switchport general allowed vlan 10,20 untagged

Switch_1(config-if)#mac-vlan

Switch_1(config-if)#exit

3) Bind the MAC address of Laptop A to VLAN 10 and bind the MAC address of Laptop B to VLAN 20.

Switch_1(config)#mac-vlan mac-address 00:19:56:8A:4C:71 vlan 10 description PCA

Switch_1(config)#mac-vlan mac-address 00:19:56:82:3B:70 vlan 20 description PCB

Switch_1(config)#end

Switch_1#copy running-config startup-config

■ Configurations for Switch 3

1) Create VLAN 10 for Department A and create VLAN 20 for Department B.

Switch_3#configure

Switch_3(config)#vlan 10

Switch_3(config-vlan)#name deptA

Switch_3(config-vlan)#exit

Switch_3(config)#vlan 20

Switch_3(config-vlan)#name deptB

Switch_3(config-vlan)#exit

2) Add tagged port 1/0/2 and port 1/0/3 to both VLAN 10 and VLAN 20.

Switch_3(config)#interface gigabitEthernet 1/0/2

Switch_3(config-if)#switchport general allowed vlan 10,20 tagged

Switch_3(config-if)#exit

Switch_3(config)#interface gigabitEthernet 1/0/3

Switch_3(config-if)#switchport general allowed vlan 10,20 tagged

Switch_3(config-if)#exit

3) Add untagged port 1/0/4 to VLAN 10 and untagged port 1/0/5 to VLAN 20.

Switch_3(config)#interface gigabitEthernet 1/0/4

Switch_3(config-if)#switchport general allowed vlan 10 untagged

Switch_3(config-if)#exit

Switch_3(config)#interface gigabitEthernet 1/0/5

Switch_3(config-if)#switchport general allowed vlan 20 untagged

Switch_3(config-if)#end

Switch_3#copy running-config startup-config

Verify the Configurations

Switch 1

Switch_1#show mac-vlan all

MAC AddNameVLAN-ID
------------------------

00:19:56:8A:4C:71 PCA 10

00:19:56:82:3B:70 PCB 20

Switch 2

Switch_2#show mac-vlan all

MAC AddressDescriptionVLAN
------------------------

00:19:56:8A:4C:71 PCA 10

00:19:56:82:3B:70 PCB 20

Switch 3

Switch_3#show vlan

VLANNameStatusPorts
1System-VLANactiveGi1/0/1, Gi1/0/2, Gi1/0/3, Gi1/0/4, Gi1/0/5, Gi1/0/6, Gi1/0/7, Gi1/0/8 ...
10DeptAactiveGi1/0/2, Gi1/0/3, Gi1/0/4
20DeptBactiveGi1/0/2, Gi1/0/3, Gi1/0/5

4 Appendix: Default Parameters

Default settings of MAC VLAN are listed in the following table.

Table 4-1 Default Settings of MAC VLAN

Parameter Default Setting
MAC Address None
Description None
VLAN ID None
Port Enable Disabled

Part 9

Configuring Protocol VLAN

CHAPTERS

  1. Overview
  2. Protocol VLAN Configuration
  3. Configuration Example
  4. Appendix: Default Parameters

1 Overview

Protocol VLAN is a technology that divides VLANs based on the network layer protocol. With the protocol VLAN rule configured on the basis of the existing 802.1Q VLAN, the switch can analyze specific fields of received packets, encapsulate the packets in specific formats, and forward the packets with different protocols to the corresponding VLANs. Since different applications and services use different protocols, network administrators can use protocol VLAN to manage the network based on specific applications and services.

The figure below shows a common application scenario of protocol VLAN. With protocol VLAN configured, Switch 2 can forward IPv4 and IPv6 packets from different VLANs to the IPv4 and IPv6 networks respectively.

Figure 1-1 Common Application Scenario of Protocol VLAN
TP-LINK Omada TL-SG2008P - Overview - 1

flowchart
graph TD
    A["IPv4 Internet"] --> B["Switch 1"]
    C["IPv6 Internet"] --> D["Switch 2"]
    E["RouterRouter"] --> D
    B --> F["VLAN 20VLAN 10"]
    D --> G["VLAN 20VLAN 10"]
    F --> H["IPv4 Hosts VLAN 10"]
    G --> I["IPv6 Hosts VLAN 20"]

2 Protocol VLAN Configuration

To complete protocol VLAN configuration, follow these steps:

1) Configure 802.1Q VLAN.
2) Create protocol template.
3) Configure Protocol VLAN.

Configuration Guidelines

■ You can use the IP, ARP, RARP, and other protocol templates provided by TP-Link switches, or create new protocol templates.
In a protocol VLAN, when a port receives an untagged data packet, the switch will first search for the protocol VLAN matching the protocol type value of the packet. If there is a match, the switch will insert the corresponding VLAN tag to the data packet and forward it within the VLAN. Otherwise, the switch will forward the data packet to the default VLAN based on the PVID (Port VLAN ID) of the receiving port. (If MAC VLAN is also configured, the switch will first process Protocol VLAN, then MAC VLAN.) When the port receives a tagged data packet, the switch will directly process the data packet according to the processing rule of the 802.1 Q VLAN.

2.1 Using the GUI

2.1.1 Configuring 802.1Q VLAN

Before configuring protocol VLAN, create an 802.1Q VLAN and set the port type according to network requirements. For details, refer to Configuring 802.1Q VLAN.

2.1.2 Creating Protocol Template

Choose the menu L2 FEATURES > VLAN > Protocol VLAN > Protocol Template to load the following page.

Figure 2-1 Check the Protocol Template

Protocol Template Config
+ Add Delete
IDTemplate NameProtocol Type
1IPEthernet II 0800
2ARPEthernet II 0806
3RARPEthernet II 8035
4IPXSNAP
5ATSNAP
Total: 5

Follow these steps to create a protocol template:

1) Check whether your desired template already exists in the Protocol Template Config section. If not, click to create a new template.

Figure 2-2 Creating a Protocol Template
TP-LINK Omada TL-SG2008P - Creating Protocol Template - 1

text_image Protocol Template Config Template Name: Frame Type: Ethernet II SNAP LLC Ether Type: (1-8 characters) (4 hexadecimal integers, 0600-FFFF) Cancel Create

Template Name Give a protocol name to identify the protocol template.

Frame Type Select the frame type of the new protocol template.

Ethernet II: A common Ethernet frame format. Select to specify the Frame Type by entering the Ether Type.

SNAP: An Ethernet 802.3 frame format based on IEEE 802.3 and IEEE 802.2 SNAP. Select to specify the Frame Type by entering the Ether Type.

LLC: An Ethernet 802.3 frame format based on IEEE 802.3 and IEEE 802.2 LLC. Select to specify the Frame Type by entering the DSAP and SSAP.

Ether Type Enter the Ethernet protocol type value for the protocol template. It is available when Ethernet II and SNAP is selected. It is the Ether Type field in the frame and is used to identify the data type of the frame.

DSAPEnter the DSAP value for the protocol template. It is available when LLC is selected. It is the DSAP field in the frame and is used to identify the data type of the frame.
SSAPEnter the SSAP value for the protocol template. It is available when LLC is selected. It is the SSAP field in the frame and is used to identify the data type of the frame.

2) Click Create.

TP-LINK Omada TL-SG2008P - 2) Click Create. - 1

Note:

A protocol template that is bound to a VLAN cannot be deleted.

2.1.3 Configuring Protocol VLAN

Choose the menu L2 FEATURES > VLAN > Protocol VLAN > Protocol VLAN Group and click to load the following page.

Figure 2-3 Configure the Protocol VLAN Group
TP-LINK Omada TL-SG2008P - Configuring Protocol VLAN - 1

text_image Protocol VLAN Group Config Template Name: VLAN: VLAN ID VLAN Name VLAN ID: (1-4094) 802.1p Priority: 0 Port: (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

Follow these steps to configure the protocol group:

1) In the Protocol Group Config section, specify the following parameters.

Template Name Select the previously defined protocol template.

VLAN ID/Name Enter the ID number or name of the 802.1Q VLAN that will be bound to the Protocol VLAN.

802.1p Priority

Specify the 802.1p priority for the packets that belong to the protocol VLAN. The switch will determine the forwarding sequence according this value. The packets with larger value of 802.1p priority have the higher priority.

2) Select the desired ports. Click Create.

TP-LINK Omada TL-SG2008P - 2) Select the desired ports. Click Create. - 1

Note:

The member port of an LAG (Link Aggregation Group) follows the configuration of the LAG and not its own. The configurations of the port can take effect only after it leaves the LAG.

2.2 Using the CLI

2.2.1 Configuring 802.1Q VLAN

Before configuring protocol VLAN, create an 802.1Q VLAN and set the port type according to network requirements. For details, refer to Configuring 802.1Q VLAN.

2.2.2 Creating a Protocol Template

Follow these steps to create a protocol template:

Step 1 configure

Enter global configuration mode.

Step 2 protocol-vlan template name

protocol-name frame { ether_2 ether-type type | snap

ether-type type | llc dsap dsap_type ssap ssap_type}

Create a protocol template.

protocol-name: Specify the protocol name with 1 to 8 characters.

type: Enter4 hexadecimal numbers as the Ethernet protocol type for the protocol template. It is the Ether Type field in the frame and is used to identify the data type of the frame.

dsap_type: Enter 2 hexadecimal numbers as the DSAP value for the protocol template. It is the DSAP field in the frame and is used to identify the data type of the frame.

ssap_type: Enter 2 hexadecimal numbers as the SSAP value for the protocol template. It is the SSAP field in the frame and is used to identify the data type of the frame.

Step 3 show protocol-vlan template

Verify the protocol templates.

Step 4 end

Return to Privileged EXEC Mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to create an IPv6 protocol template:

Switch#configure

Switch(config)#protocol-vlan template name IPv6 frame ether_2 ether-type 86dd

Switch(config)#show protocol-vlan template

IndexProtocol NameProtocol Type
1IPEthernetll ether-type 0800
2ARPEthernetll ether-type 0806
3RARPEthernetll ether-type 8035
4IPXSNAP ether-type 8137
5ATSNAP ether-type 809B
6IPv6Ethernetll ether-type 86DD

Switch(config)#end

Switch#copy running-config startup-config

2.2.3 Configuring Protocol VLAN

Follow these steps to configure protocol VLAN:

Step 1 configure

Enter global configuration mode.

Step 2 show protocol-vlan template

Check the index of each protocol template.

Step 3 protocol-vlan vlan

vid priority priority template index

Bind the protocol template to the VLAN.

vid : Enter the ID number of the 802.1Q VLAN that will be bound to the Protocol VLAN.

priority: Specify the 802.1p priority for the packets that belong to the protocol VLAN. The switch will determine the forwarding sequence according this value. The packets with larger value of 802.1p priority have the higher priority.

index : Specify the protocol template index.

Step 4 show protocol-vlan vlan

Check the protocol VLAN index (entry-id) of each protocol group.

Step 5 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}Enter interface configuration mode.
Step 6 protocol-vlan group entry-idAdd the specified port to the protocol group.entry-id: Protocol VLAN index.
Step 7 endReturn to Privileged EXEC Mode.
Step 8 copy running-config startup-configSave the settings in the configuration file.

The following example shows how to bind the IPv6 protocol template to VLAN 10 and add port 1/0/2 to protocol VLAN:

Switch#configure

Switch(config)#show protocol-vlan template

IndexProtocol NameProtocol Type
1IPEthernetll ether-type 0800
2ARPEthernetll ether-type 0806
3RARPEthernetll ether-type 8035
4IPXSNAP ether-type 8137
5ATSNAP ether-type 809B
6IPv6Ethernetll ether-type 86DD

Switch(config)#protocol-vlan vlan 10 priority 5 template 6

Switch(config)#show protocol-vlan vlan

IndexProtocol-NameVIDPriorityMember
1IPv6100

Switch(config)#interface gigabitEthernet 1/0/2

Switch(config-if)#protocol-vlan group 1

Switch(config-if)#show protocol-vlan vlan

IndexProtocol-NameVIDPriorityMember
1IPv6105Gi1/0/2

Switch(config-if)#end

Switch#copy running-config startup-config

3 Configuration Example

3.1 Network Requirements

A company uses both IPv4 and IPv6 hosts, and these hosts access the IPv4 network and IPv6 network respectively via different routers. It is required that IPv4 packets are forwarded to the IPv4 network, IPv6 packets are forwarded to the IPv6 network, and other packets are dropped.

The figure below shows the network topology. The IPv4 host belongs to VLAN 10, the IPv6 host belongs to VLAN 20, and these hosts access the network via Switch 1. Switch 2 is connected to two routers to access the IPv4 network and IPv6 network respectively. The routers belong to VLAN 10 and VLAN 20 respectively.

Figure 3-1 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["IPv4 Internet"] --> B["Router 2Router 1"]
    B --> C["Switch 2"]
    C --> D["IPv4 Host IPv6 Host"]
    A --> E["Router 2Router 1"]
    E --> F["Switch 1"]
    F --> G["IPv4 Host IPv6 Host"]
    C --> H["Gi1/0/1 VLAN 10"]
    C --> I["Gi1/0/3 VLAN 20"]
    C --> J["Gi1/0/2 VLAN 20"]

3.2 Configuration Scheme

You can configure protocol VLAN on port 1/0/1 of Switch 2 to meet this requirement. When this port receives packets, Switch 2 will forward them to the corresponding VLANs according to their protocol types. The overview of the configuration on Switch 2 is as follows:

1) Create VLAN 10 and VLAN 20 and add each port to the corresponding VLAN.
2) Use the IPv4 protocol template provided by the switch, and create the IPv6 protocol template.
3) Bind the protocol templates to the corresponding VLANs to form protocol groups, and add port 1/0/1 to the groups.

For Switch 1, configure 802.1Q VLAN according to the network topology.

Demonstrated with T1600G-28TS, this chapter provides configuration procedures in two ways: using the GUI and using the CLI.

3.3 Using the GUI

■ Configurations for Switch 1

1) Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > VLAN Config and click

TP-LINK Omada TL-SG2008P - Using the GUI - 1

Add to load the following page. Create VLAN 10, and add untagged port 1/0/1 and gged port 1/0/3 to VLAN 10. Click Create.

Figure 3-2 Create VLAN 10
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image VLAN Config VLAN ID: 10 (2-4094, format: 2,4-5,8) VLAN Name: IPv4 (1-16 characters) Untagged Ports Port: 1/0/1,1/0/3 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Tagged Ports Port: (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

2) Click + Add to load the following page. Create VLAN 20, and add untagged ports 1/0/2-3 to VLAN 20. Click Create.

Figure 3-3 Create VLAN 20
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image VLAN Config VLAN ID: 20 (2-4094, format: 2,4-5,8) VLAN Name: IPv6 (1-16 characters) Untagged Ports Port: 1/0/2-3 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Tagged Ports Port: (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

3) Click Save the settings.

■ Configurations for Switch 2

1) Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > VLAN Config and click Add to load the following page. Create VLAN 10, and add tagged port 1/0/1 and untagged port 1/0/2 to VLAN 10. Click Create.

Figure 3-4 Create VLAN 10
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch 2 - 1

text_image VLAN Config VLAN ID: 10 (2-4094, format: 2,4-5,8) VLAN Name: IPv4 (1-16 characters) Untagged Ports Port: 1/0/2 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Tagged Ports Port: 1/0/1 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

2) Click + Add to load the following page. Create VLAN 20, and add tagged port 1/0/1 and untagged port 1/0/3 to VLAN 20. Click Create.

Figure 3-5 Create VLAN 20
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch 2 - 2

text_image VLAN Config VLAN ID: 20 (2-4094, format: 2,4-5,8) VLAN Name: IPv6 (1-16 characters) Untagged Ports Port: 1/0/3 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Tagged Ports Port: 1/0/1 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

3) Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > Port Config to load the following page. Set the PVID of port 1/0/2 and port 1/0/3 as 10 and 20 respectively. Click Apply.

Figure 3-6 Port Configuration
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch 2 - 3

text_image Port Config UNIT1 LAGS Port PVID Ingress Checking Acceptable Frame Types LAG Details 20 ▼ ▼ 1/0/1 1 Enabled Admit All --- Details 1/0/2 10 Enabled Admit All --- Details ✓ 1/0/3 20 Enabled Admit All --- Details 1/0/4 1 Enabled Admit All --- Details 1/0/5 1 Enabled Admit All --- Details 1/0/6 1 Enabled Admit All --- Details 1/0/7 1 Enabled Admit All --- Details 1/0/8 1 Enabled Admit All --- Details 1/0/9 1 Enabled Admit All --- Details 1/0/10 1 Enabled Admit All --- Details Total: 28 1 entry selected. Cancel Apply

4) Choose the menu L2 FEATURES > VLAN > Protocol VLAN > Protocol Template and click + Add to load the following page. Enter IPv6 in the protocol name, select the Ethernet II frame type, enter 86DD in the Ether Type field, and click Create to create the IPv6 protocol template.

Tips: The IPv4 protocol template is already provided by the switch. You only need to create the IPv6 protocol template.

Figure 3-7 Create the IPv6 Protocol Template
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch 2 - 4

text_image Protocol Template Config Template Name: IPv6 (1-8 characters) Frame Type: Ethernet II ○ SNAP ○ LLC Ether Type: 86DD (4 hexadecimal integers, 0600-FFFF) Cancel Create

5) Choose the menu L2 FEATURES > VLAN > Protocol VLAN > Protocol VLAN Group and click to load the following page. Select the IP protocol name (that is the IPv4 protocol template), enter VLAN ID 10, select port 1, and click Create. Select the IPv6 protocol name, enter VLAN ID 20, select port 1, and click Create.

Figure 3-8 Configure the IPv4 Protocol Group
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch 2 - 5

text_image Protocol VLAN Group Config Template Name: IP VLAN: ○ VLAN ID ○ VLAN Name VLAN ID: 10 (1-4094) 802.1p Priority: 0 Port: 1/0/1 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

Figure 3-9 Configure the IPv6 Protocol Group
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch 2 - 6

text_image Protocol VLAN Group Config Template Name: IPv6 VLAN: VLAN ID VLAN Name VLAN ID: 20 (1-4094) 802.1p Priority: 0 Port: 1/0/1 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

6) Click Save the settings.

3.4 Using the CLI

■ Configurations for Switch 1

1) Create VLAN 10 and VLAN 20.

Switch_1#configure

Switch_1(config)#vlan 10

Switch_1(config-vlan)#name IPv4

Switch_1(config-vlan)#exit

Switch_1(config)#vlan 20

Switch_1(config-vlan)#name IPv6

Switch_1(config-vlan)#exit

2) Add untagged port 1/0/1 to VLAN 10. Add untagged port 1/0/2 to VLAN 20. Add untagged port 1/0/3 to both VLAN10 and VLAN 20.

Switch_1(config)#interface gigabitEthernet 1/0/1

Switch_1(config-if)#switchport general allowed vlan 10 untagged

Switch_1(config-if)#exit

Switch_1(config)#interface gigabitEthernet 1/0/2

Switch_1(config-if)#switchport general allowed vlan 20 untagged

Switch_1(config-if)#exit

Switch_1(config)#interface gigabitEthernet 1/0/3

Switch_1(config-if)#switchport general allowed vlan 10,20 untagged

Switch_1(config-if)#end

Switch_1#copy running-config startup-config

■ Configurations for Switch 2

1) Create VLAN 10 and VLAN 20.

Switch_2#configure

Switch_2(config)#vlan 10

Switch_2(config-vlan)#name IPv4

Switch_2(config-vlan)#exit

Switch_2(config)#vlan 20

Switch_2(config-vlan)#name IPv6

Switch_2(config-vlan)#exit

2) Add tagged port 1/0/1 to both VLAN 10 and VLAN 20. Specify the PVID of untagged port 1/0/2 as 10 and add it to VLAN 10. Specify the PVID of untagged port 1/0/3 as 20 and add it to VLAN 20.

Switch_2(config)#interface gigabitEthernet 1/0/1

Switch_2(config-if)#switchport general allowed vlan 10,20 tagged

Switch_2(config-if)#exit

Switch_2(config)#interface gigabitEthernet 1/0/2

Switch_2(config-if)#switchport pvid 10

Switch_2(config-if)#switchport general allowed vlan 10 untagged

Switch_2(config-if)#exit

Switch_2(config)#interface gigabitEthernet 1/0/3

Switch_2(config-if)#switchport mode general

Switch_2(config-if)#switchport pvid 20

Switch_2(config-if)#switchport general allowed vlan 20 untagged

Switch_2(config-if)#exit

3) Create the IPv6 protocol template.

Switch_2(config)#protocol-vlan template name IPv6 frame ether_2 ether-type 86dd

Switch_2(config)#show protocol-vlan template

IndexProtocol NameProtocol Type
-----------
1IPEthernetll ether-type 0800
2ARPEthernetll ether-type 0806
3RARPEthernetll ether-type 8035
4IPXSNAP ether-type 8137
5ATSNAP ether-type 809b
6IPv6Ethernet ll ether-type 86dd

4) Configure the protocol groups.

Switch_2(config)#protocol-vlan vlan 10 priority 0 template 1

Switch_2(config)#protocol-vlan vlan 20 priority 0 template 6

5) Add port 1/0/1 to the protocol groups.

Switch_2(config)#show protocol-vlan vlan

IndexProtocol-NameVIDMember
---------------
1IP10
2IPv620

Switch_2(config)#interface gigabitEthernet 1/0/1

Switch_2(config-if)#protocol-vlan group 1

Switch_2(config-if)#protocol-vlan group 2

Switch_2(config-if)#exit

Switch_2(config)#end

Switch_2#copy running-config startup-config

Verify the Configurations

Switch 1

Verify 802.1Q VLAN configuration:

Switch_1#show vlan

VLANNameStatusPorts
1System-VLANactiveGi1/0/1, Gi1/0/2, Gi1/0/3, Gi1/0/4...Gi1/0/25, Gi1/0/26, Gi1/0/27, Gi1/0/28
10IPv4activeGi1/0/1, Gi1/0/3
20IPv6activeGi1/0/2, Gi1/0/3

Switch 2

Verify 802.1Q VLAN configuration:

Switch_2#show vlan

VLANNameStatusPorts
1System-VLANactiveGi1/0/1, Gi1/0/2, Gi1/0/3, Gi1/0/4...Gi1/0/25, Gi1/0/26, Gi1/0/27, Gi1/0/28
10IPv4activeGi1/0/1, Gi1/0/2
20IPv6activeGi1/0/1, Gi1/0/3

Verify protocol group configuration:

Switch_2#show protocol-vlan vlan

IndexProtocol-NameVIDPriorityMember
1IP100Gi1/0/1
2IPv6200Gi1/0/1

4 Appendix: Default Parameters

Default settings of Protocol VLAN are listed in the following table.

Table 4-1 Default Settings of Protocol VLAN

Parameter Default Setting
Protocol Template Table1 IP Ethernet II ether-type 08002 ARP Ethernet II ether-type 08063 RARP Ethernet II ether-type 80354 IPX SNAP ether-type 81375 AT SNAP ether-type 809B

Part 10

Configuring VLAN-VPN

(Only for Certain Devices)

CHAPTERS

  1. VLAN-VPN
  2. Basic VLAN-VPN Configuration
  3. Flexible VLAN-VPN Configuration
  4. Configuration Examples
  5. Appendix: Default Parameters

1 VLAN-VPN

1.1 Overview

TP-LINK Omada TL-SG2008P - Overview - 1

Note:

VLAN VPN is only available on certain devices. To check whether your device supports this feature, refer to the actual web interface. If VLAN VPN is available, there is L2 FEATURES > VLAN > VLAN VPN in the menu structure.

VLAN-VPN (Virtual Private Network) is an easy-to-implement layer 2 VLAN technology, and it is usually deployed at the edge of the ISP (Internet Service Provider) network.

With VLAN-VPN, when forwarding packets from the customer network to the ISP network, the switch adds an outer tag to the packets with outer VLAN ID. Thus, packets can be transmitted through ISP networks with double VLAN tags. In the ISP network, packets are forwarded according to the outer VLAN tag (VLAN tag of the ISP network), while the inner VLAN tag is treated as part of the payload. When forwarding packets from the ISP network to the customer network, the switch remove the outer VLAN tag of the packets. Thus, packets are forwarded according to the inner VLAN tag (VLAN tag of the customer network) in the customer network.

The following figure shows the typical application scenario of VLAN-VPN. To realize the communication between two customer VLANs across the ISP network, you can configure VLAN-VPN at the ISP edge switches to allow packets from customer VLAN 100 and VLAN 200 to be forwarded through the ISP network with the outer tag of VLAN 1050.

Figure 1-1 Application Scenario of VLAN-VPN
TP-LINK Omada TL-SG2008P - Note: - 1

flowchart
graph LR
    A["VLAN 100"] --> B["Device"]
    C["VLAN 200"] --> B
    B --> D["VLAN 1050"]
    D --> E["VLAN 100"]
    E --> F["Device"]
    G["VLAN 200"] --> F
    F --> H["Device"]

1.2 Supported Features

The VLAN-VPN function includes: basic VLAN-VPN and flexible VLAN-VPN (VLAN mapping).

Basic VLAN-VPN

All packets from customer VLANs are encapsulated with the same VLAN tag of the ISP network, and sent to the ISP network. Additionally, you can set the TPID (Tag Protocol Identifier) for compatibility with devices in the ISP network.

Flexible VLAN-VPN

You can configure different VLANs in the customer network to map to different VLANs in the ISP network.

When the switch receives a packet with the customer network tag, the switch will check the VLAN Mapping List. If a match is found, the switch encapsulates the packet with the corresponding VLAN tag of the ISP network, and forwards it to the corresponding port. If no match is found, the switch process the packet in rules of MAC VLAN, Protocol VLAN and 802.1Q VLAN. For untagged packets, the switch directly processes them in rules of MAC VLAN, Protocol VLAN and 802.1Q VLAN.

2 Basic VLAN-VPN Configuration

To complete the basic VLAN-VPN configuration, follow these steps:

1) Configure 802.1Q VLAN.
2) Configure NNI ports and UNI ports.
3) Enable VLAN-VPN globally.

Configuration Guidelines

■ The TPID preset by the switch is 0x8100. If the devices in the ISP network do not support this value, you should change it to ensure VLAN-VPN packets sent to the ISP network can be recognized and forwarded by devices of other manufacturers.
- You can go to 802.1Q VLAN section to specify the Ingress Checking feature according to your needs. If the Ingress Checking is enabled, the port will perform this operation first then process the packets based on the VLAN-VPN configuration. If Ingress Checking is disabled, the port will process the packets directly based on the VLAN-VPN configuration.

2.1 Using the GUI

2.1.1 Configuring 802.1Q VLAN

Before configuring VLAN-VPN, create 802.1Q VLAN add ports to corresponding VLANs and configure Ingress Checking on ports according to your needs. For details, refer to Configuring 802.1Q VLAN.

2.1.2 Configuring Basic VLAN-VPN

Choose the menu L2 FEATURES > VLAN > VLAN VPN > VPN Config to load the following page.

Figure 2-1 Basic VPN Configuration
TP-LINK Omada TL-SG2008P - Configuring Basic VLAN-VPN - 1

text_image Global Config VLAN VPN: ☐ Enable Apply Port Config UNIT1 LAGS ☐ Port Port Role TPID Missdrop Use Inner Priority ✓ 1/0/1 -- 8100 Disabled Disabled ☐ 1/0/2 -- 8100 Disabled Disabled ☐ 1/0/3 -- 8100 Disabled Disabled ☐ 1/0/4 -- 8100 Disabled Disabled ☐ 1/0/5 -- 8100 Disabled Disabled ☐ 1/0/6 -- 8100 Disabled Disabled ☐ 1/0/7 -- 8100 Disabled Disabled ☐ 1/0/8 -- 8100 Disabled Disabled ☐ 1/0/9 -- 8100 Disabled Disabled ☐ 1/0/10 -- 8100 Disabled Disabled Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure the basic VLAN-VPN parameters:

1) In the Global Config section, enable VLAN VPN globally, and click Apply.

VLAN VPN Enable the VLAN VPN function globally.

2) In the VPN Port Config section, select on or more ports and configure the corresponding parameters. Click Apply.

Port Role Select the port role that will take effect in the VLAN-VPN function.

NNI: NNI ports are usually connected to the ISP network, and the packets forwarded by these port have outer VLAN tags.

UNI: UNI ports are usually connected to the customer network. The outer VLAN tags will be added or removed when the packets are forwarded by the UNI port.

Note:

The direct shift between ports modes UNI and NNI is not supported. To switch from the current mode to another mode, you can change the port role to “--” first.

TPID Specify the value of TPID. TPID is a field of VLAN tag and is modified to make the double tagged packets identifiable to devices from different vendors.
Missdrop Enable the Missdrop feature. This option only can take effect on tagged packets.With Missdrop enabled, the tagged packets that don't match the VLAN Mapping entries will be dropped.Note:For T2600G-28TS/T2600G-28MPS/T2600G-28SQ/T2600G-52TS, Missdrop can only be enabled on UNI ports.For T2600G-18TS, Missdrop can only be enabled on NNI ports.
Use Inner PriorityEnable this function and the switch will determine the forwarding sequence of the packets according to the 802.1p priority of the inner VLAN tag.It is available only when the port role is UNI.

TP-LINK Omada TL-SG2008P - Configuring Basic VLAN-VPN - 2

Note:

• The PVID of the UNI port should be specified as the VLAN ID of the ISP VLAN.
- The member port of an LAG (Link Aggregation Group) follows the configuration of the LAG and not its own. The configurations of the port can take effect only after it leaves the LAG.

2.2 Using the CLI

2.2.1 Configuring 802.1Q VLAN

Before configuring VLAN-VPN, create 802.1Q VLAN, add ports to corresponding VLANs and configure Ingress Checking on ports according to your needs. For details, refer to Configuring 802.1Q VLAN.

2.2.1 Configuring Basic VLAN-VPN

Follow these steps to configure basic VLAN-VPN:

Step 1 configure

Enter global configuration mode.

Step 2 dot1q-tunnel

Enable the VLAN-VPN feature globally.

Step 3 interface {fastEthernet

port | range fastEthernet port-list | gigabitEthernet port | range

gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}

Enter interface configuration mode.

Step 4 switchport dot1q-tunnel mode { nni | uni }

Select the port role that will take effect in the VLAN-VPN function.

nni: NNI ports are usually connected to the ISP network, and the packets forwarded by these port have outer VLAN tags.

uni: UNI ports are usually connected to the customer network. The outer VLAN tags will be added or removed when the packets are forwarded by the UNI port.

Note:

The direct shift between ports modes uni and nni is not supported. To switch from the current mode to another mode, you can use no switchport dot1q-tunnel mode to disable the current mode.

Step 5 switchport dot1q-tunnel tpid

tpid

Specify the value of TPID. TPID is a field of VLAN tag and is modified to make the double tagged packets identifiable to devices from different vendors.

tpid: Enter the IPID for the port. It must be 4 Hex integers. By default, it is 8100.

Step 6 switchport dot1q-tunnel missdrop

Enable the Missdrop feature. This option only can take effect on tagged packets. With Missdrop enabled, the tagged packets that don't match the VLAN Mapping entries will be dropped. By default, it is disabled.

Note:

For T2600G-28TS/T2600G-28MPS/T2600G-28SQ/T2600G-52TS, Missdrop can only be enabled on UNI ports.

For T2600G-18TS, Missdrop can only be enabled on NNI ports.

Step 7 switchport dot1q-tunnel use\_inner\_priority

Enable this function and the switch will determine the forwarding sequence of the packets according to the 802.1p priority of the inner VLAN tag. By default, it is disabled.

It is available only when the port mode is UNI.

Step 8 show dot1q-tunnel

Verify the global configuration of VLAN-VPN.

Step 9 show dot1q-tunnel interface

Verify the interface configuration of basic VLAN-VPN.

Step 10 end

Return to privileged EXEC mode.

Step 11 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable the VLAN-VPN feature globally, set port 1/0/1 of switch as the UNI port and 1/0/2 as the NNI port:

Switch#configure

Switch(config)#dot1q-tunnel

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#switchport dot1q-tunnel mode uni

Switch(config-if)#exit

Switch(config)#interface gigabitEthernet 1/0/2

Switch(config-if)#switchport dot1q-tunnel mode nni

Switch(config-if)#show dot1q-tunnel

VLAN-VPN Mode: Enabled

Mapping Mode: Disabled

Switch(config-if)#show dot1q-tunnel interface

PortTypeTpidUse Inner PriorityLAG
Gi1/0/1UNI0x8100DisableN/A
Gi1/0/2NNI0x8100EnableN/A

Switch(config-if)#end

Switch#copy running-config startup-config

3 Flexible VLAN-VPN Configuration

To complete the flexible VLAN-VPN configuration, follow these steps:

1) Configure 802.1Q VLAN and basic VLAN-VPN.
2) Configure VLAN mapping.

Configuration Guidelines

■ Before you start, configure 802.1Q VLAN and the basic VLAN-VPN.

- You can specify the PVID of the UNI port according to your needs. The untagged packets and the tagged packets that don't the VLAN mapping entry may be added the outer VLAN tag with this PVID according to your configuration.

3.1 Using the GUI

Choose the menu L2 FEATURES > VLAN > VLAN VPN > VLAN Mapping to load the following page.

Figure 3-1 Enable Flexible VLAN-VPN
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Global Config VLAN Mapping: Enable Apply VLAN Mapping Config Index Port C VLAN ID C VLAN Name SP VLAN ID SP VLAN Name Description Operation No entries in this table. Total: 0

Follow these steps to configure flexible VLAN-VPN:

1) In the Global Config section, enable VLAN mapping globally and click Apply.
2) In the VLAN Mapping Config section, click + Add to load the following page. Configure the following parameters.

Figure 3-2 Create VLAN Mapping Entry
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image VLAN Mapping Config Port: C VLAN: SP VLAN: Description: Choose (Format: 1/0/1) ID Name (1-4094) ID Name (1-4094) (Optional. 1-16 characters) Cancel Create

Port For some devices, choose a UNI port to enable VLAN mapping. For other devices, choose a NNI port to enable VLAN mapping.

C VLAN Specify the customer VLAN of the UNI port by entering the VLAN ID or VLAN Name.

SP VLAN Specify the ISP VLAN of the UNI port by entering the VLAN ID or VLAN Name.

Description Give a description to identify the VLAN Mapping.

3) Click Create.

3.2 Using the CLI

Follow these steps to configure flexible VLAN-VPN:

Step 1 configure

Enter global configuration mode.

Step 2 dot1q-tunnel mapping

Enable VLAN mapping globally.

Step 3 interface {fastEthernet

port | range fastEthernet port-list | gigabitEthernet port | range

gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}

For some devices, choose a UNI port to enable VLAN mapping. For other devices, choose a NNI port to enable VLAN mapping.

Step 4 switchport dot1q-tunnel mapping

c-vlan sp-vlan [descript]

Set VLAN mapping entries for the specified port.

c vlan: Enter VLAN ID of the customer network.

sp vlan: Enter VLAN ID of the ISP network.

descript: Give a description to identify the VLAN Mapping.

Step 5 end

Return to privileged EXEC mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable VLAN mapping and set a VLAN mapping entry named mapping1 on port 1/0/3 to map customer network VLAN 15 to ISP network VLAN 1040:

Switch#configure

Switch(config)#dot1q-tunnel mapping

Switch(config)#show dot1q-tunnel

VLAN-VPN Mode: Enabled

Mapping Mode: Enabled

Switch(config)#interface gigabitEthernet 1/0/3

Switch(config-if)#switchport dot1q-tunnel mapping 15 1040 mapping1

Switch(config-if)#show dot1q-tunnel mapping

PortC-VLANSP-VLANName
Gi1/0/3151040mapping1

Switch(config-if)#end

Switch#copy running-config startup-config

4 Configuration Examples

4.1 Example for Basic VLAN VPN

4.1.1 Network Requirements

A company has two stations, and the computers belong to VLAN 100 and VLAN 200 respectively. The ISP VLAN is VLAN 1050 and the TPID adopted by the ISP network is 0x9100.

The two stations need to communicate with each other through the ISP network. And it is required that the traffic from VLAN 100 and VLAN 200 should be transmitted in VLAN 1050.

Figure 4-1 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["TPID=0x9100 VLAN1050"] --> B["Switch 1"]
    A --> C["Switch 2"]
    B --> D["Gi1/0/1"]
    B --> E["GI1/0/2 UNI Port"]
    C --> F["Gi1/0/2 UNI Port"]
    C --> G["Gi1/0/3"]
    D --> H["VLAN 200"]
    E --> I["VLAN 100"]
    F --> J["VLAN 200"]
    G --> K["VLAN 100"]
    H --> L["VLAN 200"]
    I --> M["VLAN 100"]
    J --> N["VLAN 200"]
    K --> O["VLAN 100"]
    style A fill:#f9f,stroke:#333
    style B fill:#ccf,stroke:#333
    style C fill:#ccf,stroke:#333
    style D fill:#cfc,stroke:#333
    style E fill:#cfc,stroke:#333
    style F fill:#cfc,stroke:#333
    style G fill:#cfc,stroke:#333
    style H fill:#fcc,stroke:#333
    style I fill:#fcc,stroke:#333
    style J fill:#fcc,stroke:#333
    style K fill:#fcc,stroke:#333
    style L fill:#cff,stroke:#333
    style M fill:#cff,stroke:#333

4.1.2 Configuration Scheme

To meet the requirement that all the traffic from VLAN 100 and VLAN 200 should be transmitted through VLAN 1050, users can configure basic VLAN VPN on Switch 1 and Switch 2 to allow packets sent with double VLAN tags, and thus ensure the communication between them. The general configuration procedure is as follows:

Here we only introduce the configuration schemes on switch 1 and switch 3, for the configurations on switch 2 are the same as those on switch 1, and the configurations on switch 4 are the same as those on switch 3.

1) Configure 802.1Q VLAN on switch 1. The parameters are shown below:

VLAN 100 VLAN 200 VLAN 1050 PVID
Port 1/0/1 -- Tagged Keep thedefault value
Port 1/0/2 Tagged Tagged Untagged 1050

2) Configure 802.1Q VLAN on switch 3. The parameters are shown below:

VLAN 100 VLAN 200 PVID
Port 1/0/1 Untagged - 100
Port 1/0/2 - Untagged 200
Port 1/0/3 Tagged Tagged Keep the default value

3) Configure VLAN VPN on switch 1. Set port 1/0/1 as NNI port and port 1/0/2 as UNI port; configure the TPID as 0x9100.

Demonstrated with T2600G-28TS, this chapter provides configuration procedures in two ways: using the GUI and using the CLI.

4.1.3 Using the GUI

■ Configuring Switch 1:

1) Go to L2 FEATURES > VLAN > 802.1Q VLAN to create VLAN 100, VLAN 200 and VLAN 1050. Configure the egress rule of port 1/0/2 in VLAN 100 and VLAN 200 as Tagged, and in VLAN 1050 as Untagged; Configure the egress rule of port 1/0/1 in VLAN 1050 as Tagged.

Figure 4-2 Create VLAN 100
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image VLAN Config VLAN ID: 100 (2-4094, format: 2,4-5,8) VLAN Name: C_VLAN100 (1-16 characters) Untagged Ports Port: (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available Tagged Ports Port: 1/0/2 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Cancel Create

Figure 4-3 Create VLAN 200
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image VLAN Config VLAN ID: 200 (2-4094, format: 2,4-5,8) VLAN Name: C_VLAN200 (1-16 characters) Untagged Ports Port: (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available Tagged Ports Port: 1/0/2 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Cancel Create

Figure 4-4 Create VLAN 1050
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image VLAN Config VLAN ID: 1050 (2-4094, format: 2.4-5.8) VLAN Name: SP_VLAN1050 (1-16 characters) Untagged Ports Port: 1/0/2 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available Tagged Ports Port: 1/0/1 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Cancel Create

2) Go to L2 FEATURES > VLAN > Port Config to set the PVID as 1050 for port 1/0/2 and leave the default vaule 1 for port 1/0/1.

Figure 4-5 Configuring PVID
TP-LINK Omada TL-SG2008P - Using the GUI - 4

text_image Port Config UNIT1 LAGS Port PVID Ingress Checking Acceptable Frame Types LAG Details 1050 ▼ ▼ 1/0/1 1 Enabled Admit All — Details ✓ 1/0/2 1050 Enabled Admit All — Details

3) Go to L2 FEATURES > VLAN > VLAN VPN > VPN Config, enable VLAN VPN globally; set port 1/0/1 as NNI port and port /1/0/2 as UNI port. Specify the TPID of port 1/0/1 as 9100.

Figure 4-6 Enabling VLAN VPN Globally and Configuring the Ports
TP-LINK Omada TL-SG2008P - Using the GUI - 5

text_image Global Config VLAN VPN: ✓ Enable Port Config UNIT1 LAGS Port Port Role TPID Missdrop Use Inner Priority 1/0/1 NNI 9100 Disabled Disabled 1/0/2 UNI 8100 Disabled Disabled 1/0/3 -- 8100 Disabled Disabled

4) Click Save the settings.

- Configuring Switch 3:

1) Go to L2 FEATURES > VLAN > 802.1Q VLAN to create VLAN 100 and VLAN 200. Configure the egress rules of port 1/0/1 in VLAN 100 as Untagged; egress rules of port 1/0/2 in VLAN 200 as Untagged; egress rule of port 1/0/3 in VLAN 100 and VLAN 200 as Tagged.

Figure 4-7 Creating VLAN 100
TP-LINK Omada TL-SG2008P - Using the GUI - 6

text_image VLAN Config VLAN ID: 100 (2-4004, format: 2.4-5.8) VLAN Name: C_VLAN100 (1-16 characters) Untagged Ports Port: 1/0/1 (Format: 1/0/1, input or choose below) UNIT I LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available Tagged Ports Port: 1/0/3 (Format: 1/0/1, input or choose below) UNIT I LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Cancel Create

Figure 4-8 Creating VLAN 200
TP-LINK Omada TL-SG2008P - Using the GUI - 7

text_image VLAN Config VLAN ID: 200 (2-4094, format: 2.4-5.0) VLAN Name: C_VLAN200 (1-16 characters) Untagged Ports Port: 1/0/2 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available Tagged Ports Port: 1/0/3 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Cancel Create

2) Go to L2 FEATURES > VLAN > Port Config to set the PVID as 100 for port 1/0/1 and 200 for port 1/0/2.

Figure 4-9 Configuring PVID
TP-LINK Omada TL-SG2008P - Using the GUI - 8

text_image Port Config UNIT1 LAGS Port PVID Ingress Checking Acceptable Frame Types LAG Details 1/0/1 100 Enabled Admit All — Details 1/0/2 200 Enabled Admit All — Details 1/0/3 1 Enabled Admit All — Details

3) Click save the settings.

4.1.4 Using the CLI

The configurations of Switch 1 and Switch 2 are similar. The following introductions take Switch 1 as an example.

1) Create VLAN 1050, VLAN 100 and VLAN 200.

Switch_1#configure

Switch_1(config)#vlan 1050
Switch_1(config-vlan)#name SP_VLAN
Switch_1(config-vlan)#exit
Switch_1(config)#vlan 100
Switch_1(config-vlan)#name C_VLAN100
Switch_1(config-vlan)#exit
Switch_1(config)#vlan 200
Switch_1(config-vlan)#name C_VLAN200
Switch_1(config-vlan)#exit 
2) Add port 1/0/1 to VLAN 1050 as tagged port, modify PVID as 1050, set the port as NNI port and specify the TPID as 9100.
Switch_1(config)#interface gigabitEthernet 1/0/1
Switch_1(config-if)#switchport general allowed vlan 1050 tagged
Switch_1(config-if)#switchport pvid1050
Switch_1(config-if)#switchport dot1q-tunnel mode nni
Switch_1(config-if)#switchport dot1q-tunnel tpid 9100
Switch_1(config-if)#exit 
3) Add port 1/0/2 to VLAN 1050 as untagged port, and add it to VLAN 100 and VLAN 200 as tagged port. Modify PVID of the port as 1050. Set the port as the UNI port.
Switch_1(config)#interface gigabitEthernet 1/0/2
Switch_1(config-if)#switchport general allowed vlan 1050 untagged
Switch_1(config-if)#switchport general allowed vlan 100,200 tagged
Switch_1(config-if)#switchport pvid 1050
Switch_1(config-if)#switchport dot1q-tunnel mode uni
Switch_1(config-if)#exit 
4) Enable VLAN VPN globally
Switch_1(config)#dot1q-tunnel
Switch_1(config)#end
Switch_1#copy running-config startup-config 

■ Configuring Switch 3

1) Create VLAN 100 and VLAN 200.

Switch_3#configure

Switch_3(config)#vlan 100

Switch_3(config-vlan)#name C_VLAN100

Switch_3(config-vlan)#exit

Switch_3(config)#vlan 200

Switch_3(config-vlan)#name C_VLAN200

Switch_3(config-vlan)#exit

2) Add port 1/0/1 to VLAN 100 and port 1/0/2 to VLAN 200 as untagged ports; add port 1/0/3 to VLAN 100 and VLAN 200 as tagged ports. Configure the PVID as 100 for port 1/0/1 and 200 for port 1/0/2.

Switch_3(config)#interface gigabitEthernet 1/0/1

Switch_3(config-if)#switchport general allowed vlan 100 untagged

Switch_3(config-if)#switchport pvid 100

Switch_3(config-if)#exit

Switch_3(config)#interface gigabitEthernet 1/0/2

Switch_3(config-if)#switchport general allowed vlan 200 untagged

Switch_3(config-if)#switchport pvid 200

Switch_3(config-if)#exit

Switch_3(config)#interface gigabitEthernet 1/0/3

Switch_3(config-if)#switchport general allowed vlan 100,200 tagged

Switch_3(config-if)#end

Switch_3#copy running-config startup-config

Verify the VLAN VPN Configurations on Switch 1

Verify the configurations of global VLAN VPN:

Switch_3#show dot1q-tunnel

VLAN VPN Mode: Enabled

Mapping Mode: Disabled

Verify the configurations of VPN up-link port and VPN port:

Switch_3#show dot1q-tunnel interface

PortTypeTpidUse Inner PriorityLAG
-------------------
Gi1/0/1NNI0x9100DisableN/A
Gi1/0/2UNI0x8100EnableN/A
Gi1/0/3NONE0x8100DisableN/A
Gi1/0/4NONE0x8100DisableN/A

...

Verify the port configuration:

Switch_3#show interface switchport gigabitEthernet 1/0/1

Port Gi1/0/1:

PVID: 1050

Acceptable frame type: All

Ingress Checking: Enable

Member in LAG: N/A

Link Type: General

Member in VLAN:

Vlan Name Egress-rule

1 System-VLAN Untagged

1050 SP_VLAN Tagged

Switch_3#show interface switchport gigabitEthernet 1/0/2

Port Gi1/0/2:

PVID: 1050

Acceptable frame type: All

Ingress Checking: Enable

Member in LAG: N/A

Link Type: General

Member in VLAN:

VlanNameEgress-rule
------------
1System-VLANUntagged
100C_VLAN100Tagged
200C_VLAN200Tagged
1050SP_VLANUntagged

4.2 Example for Flexible VLAN VPN

4.2.1 Network Requirements

A company has two stations, and the computers belong to VLAN 100 and VLAN 200 respectively. The ISP VLAN is VLAN 1050 and VLAN 1060, and the TPID adopted by the ISP network is 0x9100.

The two stations need to communicate with each other through the ISP network. And it is required that the traffic from VLAN 100 should be transmitted in VLAN 1050, while the traffic from VLAN 200 should be transmitted in VLAN 1060.

Figure 4-10 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["TPID=0x9100\nVLAN1050\nVLAN1050"] --> B["Switch 1"]
    A --> C["Switch 2"]
    B --> D["Gi1/0/1\nGi1/0/2 UNI Port"]
    C --> E["Gi1/0/2\nGi1/0/2 UNI Port"]
    D --> F["Switch 3"]
    E --> G["Switch 4"]
    F --> H["VLAN 200"]
    F --> I["VLAN 100"]
    G --> J["VLAN 200"]
    G --> K["VLAN 100"]

4.2.2 Configuration Scheme

To meet the requirement that all the traffic from VLAN 100 and VLAN 200 need to be transmitted through different ISP VLANs, users can configure flexible VLAN VPN on Switch 1 and Switch 2 to map VLAN 100 to VLAN 1050 and VLAN 200 to VLAN 1060, so packets

from VLAN 100 and VLAN 200 will be transmitted through VLAN 1050 and VLAN 1060 respectively.

Here we only introduce the configuration scheme on Switch 1 and Switch 3, for the configurations on Switch 2 are the same as that on Switch 1, and the configurations on Switch 4 are the same as that on Switch 3.

1) Configure 802.1Q VLAN on Switch 1. The parameters are shown below:

VLAN 100 VLAN 200 VLAN 1050 VLAN 1060
Port 1/0/1 -- Tagged Tagged
Port 1/0/2 Tagged Tagged Untagged Untagged

2) Configure 802.1Q VLAN on Switch 3. The parameters are shown below:

VLAN 100 VLAN 200 PVID
Port 1/0/1 Untagged - 100
Port 1/0/2 - Untagged 200
Port 1/0/3 Tagged Tagged Keep thedefault value

3) Configure VLAN VPN on Switch 1. Set port 1/0/1 as NNI port and port 1/0/2 as UNI port; configure the TPID as 0x9100; map VLAN 100 to VLAN 1050 and VLAN 200 to VLAN 1060.

Demonstrated with T2600G-28TS, this chapter provides configuration procedures in two ways: using the GUI and using the CLI.

4.2.3 Using the GUI

■ Configuring Switch 1:

1) Go to L2 FEATURES > VLAN > 802.1Q VLAN to create VLAN 100, VLAN 200, VLAN 1050 and VLAN 1060. Configure the egress rule of port 1/0/2 in VLAN 100 and VLAN 200 as Tagged, and Untagged in VLAN 1050 and VLAN 1060; Configure the egress rule of port 1/0/1 in VLAN 1050 and VLAN 1060 as Tagged.

Figure 4-11 Create VLAN 100
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image VLAN Config VLAN ID: 100 (2-4094, format: 2,4-5,8) VLAN Name: C_VLAN100 (1-16 characters) Untagged Ports Port: (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available Tagged Ports Port: 1/0/2 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Cancel Create

Figure 4-12 Create VLAN 200
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image VLAN Config VLAN ID: 200 (2-4094, format: 2,4-5,8) VLAN Name: C_VLAN200 (1-16 characters) Untagged Ports Port: (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available Tagged Ports Port: 1/0/2 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Cancel Create

Figure 4-13 Create VLAN 1050
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image VLAN Config VLAN ID: 1050 (2-4094, format: 2.4-5.8) VLAN Name: SP_VLAN1050 (1-16 characters) Untagged Ports Port: 1/0/2 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available Tagged Ports Port: 1/0/1 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Cancel Create

Figure 4-14 Create VLAN 1060
TP-LINK Omada TL-SG2008P - Using the GUI - 4

text_image VLAN Config VLAN ID: 1060 (2-4094, format: 2,4-5,8) VLAN Name: SP_VLAN1060 (1-16 characters) Untagged Ports Port: 1/0/2 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available Tagged Ports Port: 1/0/1 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Cancel Create

2) Go to L2 FEATURES > VLAN > VLAN VPN > VPN Config, enable VLAN VPN globally; set port 1/0/1 as NNI port and port /1/0/2 as UNI port. Specify the TPID of port 1/0/1 as 9100.

Figure 4-15 Enabling VLAN VPN Globally and Configuring the Ports
TP-LINK Omada TL-SG2008P - Using the GUI - 5

text_image Global Config VLAN VPN: ✓ Enable Port Config UNIT1 LAGS Port Port Role TPID Missdrop Use Inner Priority 1/0/1 NNI 9100 Disabled Disabled 1/0/2 UNI 8100 Disabled Disabled 1/0/3 - 8100 Disabled Disabled

3) Go to L2 FEATURES > VLAN > VLAN VPN > VLAN Mapping, enable VLAN Mapping globally. Then configure VLAN mapping for the UNI port 1/0/2.

Figure 4-16 Mapping VLAN 100 to VLAN 1050
TP-LINK Omada TL-SG2008P - Using the GUI - 6

text_image VLAN Mapping Config Port: 1/0/2 Choose (Format: 1/0/1) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 C VLAN: ID Name 100 (1-4094) SP VLAN: ID Name 1050 (1-4094) Description: (Optional. 1-16 characters) Cancel Create

Figure 4-17 Mapping VLAN 200 to VLAN 1060
TP-LINK Omada TL-SG2008P - Using the GUI - 7

text_image VLAN Mapping Config Port: 1/0/2 Choose (Format: 1/0/1) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 C VLAN: ID Name 200 (1-4094) SP VLAN: ID Name 1060 (1-4094) Description: (Optional. 1-16 characters) Cancel Create

4) Click to save the settings.

■ Configuring Switch 3:

1) Go to L2 FEATURES > VLAN > 802.1Q VLAN to create VLAN 100 and VLAN 200. Configure the egress rules of port 1/0/1 in VLAN 100 as Untagged; egress rules of port 1/0/2 in VLAN 200 as Untagged; egress rule of port 1/0/3 in VLAN 100 and VLAN 200 as Tagged.

Figure 4-18 Creating VLAN 100
TP-LINK Omada TL-SG2008P - Using the GUI - 8

text_image VLAN Config VLAN ID: 100 (2-4004, format: 2.4-5.8) VLAN Name: C_VLAN100 (1-16 characters) Untagged Ports Port: 1/0/1 (Format: 1/0/1, input or choose below) UNIT I LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available Tagged Ports Port: 1/0/3 (Format: 1/0/1, input or choose below) UNIT I LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Cancel Create

Figure 4-19 Creating VLAN 200
TP-LINK Omada TL-SG2008P - Using the GUI - 9

text_image VLAN Config VLAN ID: 200 (2-4094, format: 2.4-5.0) VLAN Name: C_VLAN200 (1-16 characters) Untagged Ports Port: 1/0/2 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available Tagged Ports Port: 1/0/3 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Cancel Create

2) Go to L2 FEATURES > VLAN > Port Config to set the PVID as 100 for port 1/0/1 and 200 for port 1/0/2.

Figure 4-20 Configuring PVID
TP-LINK Omada TL-SG2008P - Using the GUI - 10

text_image Port Config UNIT1 LAGS Port PVID Ingress Checking Acceptable Frame Types LAG Details 1/0/1 100 Enabled Admit All — Details 1/0/2 200 Enabled Admit All — Details 1/0/3 1 Enabled Admit All — Details

3) Click save the settings.

4.2.4 Using the CLI

- Configuring Switch 1

1) Create VLAN 100, VLAN 200, VLAN 1050 and VLAN 1060.

Switch_1#configure

Switch_1(config)#vlan 1050
Switch_1(config-vlan)#name SP_VLAN1050
Switch_1(config-vlan)#exit
Switch_1(config)#vlan 1060
Switch_1(config-vlan)#name SP_VLAN1060
Switch_1(config-vlan)#exit
Switch_1(config)#vlan 100
Switch_1(config-vlan)#name C_VLAN100
Switch_1(config-vlan)#exit
Switch_1(config)#vlan 200
Switch_1(config-vlan)#name C_VLAN200
Switch_1(config-vlan)#exit 

2) Add port 1/0/1 to VLAN 1050 and VLAN 1060 as tagged port, set the port as NNI port and specify the TPID as 9100.

Switch_1(config)#interface gigabitEthernet 1/0/1
Switch_1(config-if)#switchport general allowed vlan 1050,1060 tagged
Switch_1(config-if)#switchport dot1q-tunnel mode nni
Switch_1(config-if)#switchport dot1q-tunnel tpid 9100
Switch_1(config-if)#exit 

3) Add port 1/0/2 to VLAN 1050 and VLAN 1060 as untagged port, and add it to VLAN 100 and VLAN 200 as tagged port. Set the port as the UNI port.

Switch_1(config)#interface gigabitEthernet 1/0/2
Switch_1(config-if)#switchport general allowed vlan 1050,1060 untagged
Switch_1(config-if)#switchport general allowed vlan 100,200 tagged
Switch_1(config-if)#switchport dot1q-tunnel mode uni
Switch_1(config-if)#exit 

4) Enable VLAN mapping. Map VLAN 100 to VLAN 1050 and VLAN 200 to VLAN 1060 for port 1/0/2.

Switch_1(config)#dot1q-tunnel mapping
Switch_1(config)#interface gigabitEthernet 1/0/2
Switch_1(config-if)#switchport dot1q-tunnel mapping 100 1050 mapping
Switch_1(config-if)#switchport dot1q-tunnel mapping 200 1060 mapping 

Switch_1(config-if)#exit

5) Enable VLAN VPN globally

Switch_1(config)#dot1q-tunnel

Switch_1(config)#end

Switch_1#copy running-config startup-config

■ Configuring Switch 3

1) Create VLAN 100 and VLAN 200.

Switch_3#configure

Switch_3(config)#vlan 100

Switch_3(config-vlan)#name C_VLAN100

Switch_3(config-vlan)#exit

Switch_3(config)#vlan 200

Switch_3(config-vlan)#name C_VLAN200

Switch_3(config-vlan)#exit

2) Add port 1/0/1 to VLAN 100 and port 1/0/2 to VLAN 200 as untagged ports; add port 1/0/3 to VLAN 100 and VLAN 200 as tagged ports. Configure the PVID as 100 for port 1/0/1 and 200 for port 1/0/2.

Switch_3(config)#interface gigabitEthernet 1/0/1

Switch_3(config-if)#switchport general allowed vlan 100 untagged

Switch_3(config-if)#switchport pvid 100

Switch_3(config-if)#exit

Switch_3(config)#interface gigabitEthernet 1/0/2

Switch_3(config-if)#switchport general allowed vlan 200 untagged

Switch_3(config-if)#switchport pvid 200

Switch_3(config-if)#exit

Switch_3(config)#interface gigabitEthernet 1/0/3

Switch_3(config-if)#switchport general allowed vlan 100,200 tagged

Switch_3(config-if)#end

Switch_3#copy running-config startup-config

5 Appendix: Default Parameters

Default settings of VLAN VPN are listed in the following table.

Table 5-1 Default Settings of VLAN VPN

Parameter Default Setting
Global VLAN VPN Disabled
Port Role None
Global TPID 0x8100
Missdrop Disabled
Use Inner Priority Disabled
VLAN Mapping Disabled

Part 11

Configuring GVRP

CHAPTERS

  1. Overview
  2. GVRP Configuration
  3. Configuration Example
  4. Appendix: Default Parameters

1 Overview

GVRP (GARP VLAN Registration Protocol) is a GARP (Generic Attribute Registration Protocol) application that allows registration and deregistration of VLAN attribute values and dynamic VLAN creation.

Without GVRP operating, configuring the same VLAN on a network would require manual configuration on each device. As shown in Figure 1-1, Switch A, B and C are connected through trunk ports. VLAN 10 is configured on Switch A, and VLAN 1 is configured on Switch B and Switch C. Switch C can receive messages sent from Switch A in VLAN 10 only when the network administrator has manually created VLAN 10 on Switch B and Switch C.

Figure 1-1 VLAN Topology

Switch B

VLAN 10

Switch A

Switch C

The configuration may seem easy in this situation. However, for a larger or more complex network, such manual configuration would be time-consuming and fallible. GVRP can be used to implement dynamic VLAN configuration. With GVRP, the switch can exchange VLAN configuration information with the adjacent GVRP switches and dynamically create and manage the VLANs. This reduces VLAN configuration workload and ensures correct VLAN configuration.

Figure 1-2 GVRP Topology

Switch 3 Switch n

... ...

VLAN 10-20 VLAN 10-20

Switch 1

Switch 2

2 GVRP Configuration

To complete GVRP configuration, follow these steps:

1) Create a VLAN.
2) Enable GVRP globally.
3) Enable GVRP on each port and configure the corresponding parameters.

Configuration Guidelines

To dynamically create a VLAN on all ports in a network link, you must configure the same static VLAN on both ends of the link.

We call manually configured 802.1Q VLAN as static VLAN and VLAN created through GVRP as dynamic VLAN. Ports in a static VLAN can initiate the sending of GVRP registration message to other ports. And a port registers VLANs only when it receives GVRP messages. As the messages can only be sent from one GVRP participant to another, two-way registration is required to configure a VLAN on all ports in a link. To implement two-way registration, you need to manually configure the same static VLAN on both ends of the link.

As shown in the figure below, VLAN registration from Switch A to Switch C adds Port 2 to VLAN 2. And VLAN registration from Switch C to Switch A adds Port 3 to VLAN 2.

Figure 2-1
TP-LINK Omada TL-SG2008P - Configuration Guidelines - 1

flowchart
graph TD
    A["Switch A"] -->|Port 1 Port 4| B["Switch B"]
    B -->|Port 2| A
    B -->|Port 3| C["Switch C"]
    C -->|Port 4| A
    style A fill:#cce5ff,stroke:#333
    style B fill:#cce5ff,stroke:#333
    style C fill:#cce5ff,stroke:#333
    note right of B: "Dynamic VLAN 2"
    note right of C: "Static VLAN 2 Static VLAN 2"

Similarly, if you want to delete a VLAN from the link, two-way deregistration is required. You need to manually delete the static VLAN on both ends of the link.

2.1 Using the GUI

Choose the menu L2 FEATURES > VLAN > GVRP > GVRP Config to load the following page.

Figure 2-1 GVRP Config
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image GVRP GVRP: Enable Apply Port Config UNIT1 LAGS ID Port Status Registration Mode LeaveAll Timer (1000-30000 centiseconds) Join Timer (20-1000 centiseconds) Leave Timer (60-3000 centiseconds) LAG ✓ 1 1/0/1 Disabled Normal 1000 20 60 --- □ 2 1/0/2 Disabled Normal 1000 20 60 --- □ 3 1/0/3 Disabled Normal 1000 20 60 --- □ 4 1/0/4 Disabled Normal 1000 20 60 --- □ 5 1/0/5 Disabled Normal 1000 20 60 --- □ 6 1/0/6 Disabled Normal 1000 20 60 --- □ 7 1/0/7 Disabled Normal 1000 20 60 --- □ 8 1/0/8 Disabled Normal 1000 20 60 --- □ 9 1/0/9 Disabled Normal 1000 20 60 --- □ 10 1/0/10 Disabled Normal 1000 20 60 --- Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure GVRP:

1) In the GVRP section, enable GVRP globally, then click Apply.
2) In the Port Config section, select one or more ports, set the status as Enable and configure the related parameters according to your needs.

Port Select the desired port for GVRP configuration. It is multi-optional.

Status Enable or disable GVRP on the port. By default, it is disabled.

Registration Mode

Select the GVRP registration mode for the port.

Normal: In this mode, the port can dynamically register and deregister VLANs, and transmit both dynamic and static VLAN registration information.

Fixed: In this mode, the port is unable to dynamically register and deregister VLANs, and can transmit only the static VLAN registration information.

Forbidden: In this mode, the port is unable to dynamically register and deregister VLANs, and can transmit only the information of VLAN 1.

LeaveAll Timer (centisecond)When a GARP participant is enabled, the LeaveAll timer will be started. When the LeaveAll timer expires, the GARP participant will send LeaveAll messages to request other GARP participants to re-register all its attributes. After that, the participant restarts the LeaveAll timer.The timer ranges from 1000 to 30000 centiseconds and should be an integral multiple of 5. The default value is 1000 centiseconds.
Join Timer (centisecond)Join timer controls the sending of Join messages. A GVRP participant starts the Join timer after sending the first Join message. If the participant does not receive any response, it will send the second Join message when the Join timer expires to ensures that the Join message can be sent to other participants.The timer ranges from 20 to 1000 centiseconds and should be an integral multiple of 5. The default value is 20 centiseconds.
Leave Timer (centisecond)The Leave timer controls attribute deregistration. A participant will send a Leave message if it wants other participants to deregister some of its attributes. The participant receiving the message starts the Leave timer. If the participant does not receive any Join message of the corresponding attribute before the Leave timer expires, the participant deregisters the attribute.The timer ranges from 60 to 3000 centiseconds and should be an integral multiple of 5. The default value is 60 centiseconds.

LAG Displays the LAG the port is in.

3) Click Apply.

TP-LINK Omada TL-SG2008P - 3) Click Apply. - 1

Note:

  • The member port of an LAG follows the configuration of the LAG and not its own. The configurations of the port can take effect only after it leaves the LAG.
    • The egress rule of the ports that are dynamically added to the VLAN is tagged.
    • The egress rule of the fixed ports should be tagged.
  • When setting the timer values, make sure that the values are within the required range. The configuration value for LeaveAll timer should be greater than or equal to ten times the Leave timer value. The value for Leave timer should be greater than or equal to two times the Join timer value.

2.2 Using the CLI

Step 1 configure

Enter Global Configuration Mode.

Step 2 gvrp

Enable GVRP globally.

Step 3 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}Enter interface configuration mode.
Step 4 gvrpEnable GVRP on the port.
Step 5 gvrp registration {normal | fixed | forbidden}Configure the GVRP registration mode for the port. By default, it is normal.normal: In this mode, the port can dynamically register and deregister VLANs, and transmit both dynamic and static VLAN registration information.fixed: n this mode, the port is unable to dynamically register and deregister VLANs, and can transmit only the static VLAN registration information.forbidden: In this mode, the port is unable to dynamically register and deregister VLANs, and can transmit only information of VLAN 1.
Step 6 gvrp timer {leaveall | join | leave} valueSet the GARP timers according to your needs.leaveall: When a GARP participant is enabled, the LeaveAll timer will be started. When the LeaveAll timer expires, the GARP participant will send LeaveAll messages to request other GARP participants to re-register all its attributes. After that, the participant restarts the LeaveAll timer.join: Join timer controls the sending of Join messages. A GVRP participant starts the Join timer after sending the first Join message. If the participant does not receive any response, it will send the second Join message when the Join timer expires to ensures that the Join message can be sent to other participants.leave: The Leave timer controls attribute deregistration. A participant will send a Leave message if it wants other participants to deregister some of its attributes. The participant receiving the message starts the Leave timer. If the participant does not receive any Join message of the corresponding attribute before the Leave timer expires, the participant deregisters the attribute.value: Set a value for the timer. It should be an integral multiple of 5. For LeaveAll timer, the valid values are from 1000 to 30000 centiseconds and the default value is 1000 centiseconds. For Join timer, the valid values are from 20 to 1000 centiseconds and the default value is 20 centiseconds. For Leave timer, the valid values are from 60 to 3000 centiseconds and the default value is 60 centiseconds.

Step 7 show gvrp global

Verify the global configurations of GVRP.

Step 8 show gvrp interface [ fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel port-channel-id ]

Verify the GVRP configuration of the specified port or LAG.

Step 9 end

Return to privileged EXEC mode.

Step 10 copy running-config startup-config

Save the settings in the configuration file.

TP-LINK Omada TL-SG2008P - Step 2 gvrp - 1

Note:

  • The member port of an LAG follows the configuration of the LAG and not its own. The configurations of the port can take effect only after it leaves the LAG.
    • The egress rule of the ports dynamically added to the VLAN is tagged.
    • The egress rule of the fixed port should be tagged.
  • When setting the timer values, make sure that the values are within the required range. The configuration value for LeaveAll timer should be greater than or equal to ten times the Leave timer value. The value for Leave timer should be greater than or equal to two times the Join timer value.

The following example shows how to enable GVRP globally and on port 1/0/1, configure the GVRP registration mode as fixed and keep the values of timers as default:

Switch#configure

Switch(config)#gvrp

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#gvrp

Switch(config-if)#gvrp registration fixed

Switch(config-if)#show gvrp global

GVRP Global Status

Enabled

Switch(config-if)# show gvrp interface gigabitEthernet 1/0/1

PortStatusReg-ModeLeaveAllJoinInLeaveLAG
---------------------------
Gi1/0/1EnabledFixed10002060N/A

Switch(config-if)#end

Switch#copy running-config startup-config

3 Configuration Example

3.1 Network Requirements

Department A and Department B of a company are connected using switches. Offices of one department are distributed on different floors. As shown in Figure 3-1, the network topology is complicated. Configuration of the same VLAN on different switches is required so that computers in the same department can communicate with each other.

Figure 3-1 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["Dept. A: VLAN 10"] --> B["Switch 1"]
    B --> C["Switch 5 Switch 6"]
    C --> D["..."]
    D --> E["Switch 3"]
    E --> F["Dept. A: VLAN 10"]
    F --> G["Switch 4"]
    G --> H["Dept. B: VLAN 20"]
    C --> I["Dept. B: VLAN 20"]
    C --> J["Dept. A: VLAN 10"]
    C --> K["Dept. A: VLAN 20"]

3.2 Configuration Scheme

To reduce manual configuration and maintenance workload, GVRP can be enabled to implement dynamic VLAN registration and update on the switches.

When configuring GVRP, please note the following:

■ The two departments are in separate VLANs. To make sure the switches only dynamically create the VLAN of their own department, you need to set the registration mode for ports on Switch 1-4 as Fixed to prevents dynamic registration and deregistration of VLANs and allow the port to transmit only the static VLAN registration information.
■ To configure dynamic VLAN creation on the other switches, set the registration mode of the corresponding ports as Normal to allow dynamic registration and deregistration of VLANs.

Demonstrated with T1600G-28TS, the following sections provide configuration procedure in two ways: using the GUI and using the CLI.

3.3 Using the GUI

GVRP configurations for Switch 3 are the same as Switch 1, and Switch 4 are the same as Switch 2. Other switches share similar configurations.

The following configuration procedures take Switch 1, Switch 2 and Switch 5 as examples.

■ Configurations for Switch 1

1) Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > VLAN Config and click Add to load the following page. Create VLAN 10 and add tagged port 1/0/1 to it. Click Create.

Figure 3-2 Create VLAN 10
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch 1 - 1

text_image VLAN Config VLAN ID: 10 (2-4094, format: 2,4-5,8) VLAN Name: Department_A (1-16 characters) Untagged Ports Port: (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Tagged Ports Port: 1/0/1 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

2) Choose the menu L2 FEATURES > VLAN > GVRP to load the following page. Enable GVRP globally, then click Apply. Select port 1/0/1, set Status as Enable, and set Registration Mode as Fixed. Keep the values of the timers as default. Click Apply.

Figure 3-3 GVRP Configuration
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch 1 - 2

text_image GVRP GVRP: ✓ Enable Apply Port Config UNIT1 LAGS ID Port Status Registration Mode LeaveAll Timer (1000-30000 centiseconds) Join Timer (20-1000 centiseconds) Leave Timer (60-3000 centiseconds) LAG Enable ✓ Fixed ✓ 1 1/0/1 Enabled Fixed 1000 20 60 --- □ 2 1/0/2 Disabled Normal 1000 20 60 --- □ 3 1/0/3 Disabled Normal 1000 20 60 --- □ 4 1/0/4 Disabled Normal 1000 20 60 --- □ 5 1/0/5 Disabled Normal 1000 20 60 --- □ 6 1/0/6 Disabled Normal 1000 20 60 --- □ 7 1/0/7 Disabled Normal 1000 20 60 --- □ 8 1/0/8 Disabled Normal 1000 20 60 --- □ 9 1/0/9 Disabled Normal 1000 20 60 --- □ 10 1/0/10 Disabled Normal 1000 20 60 --- Total: 28 1 entry selected Cancel Apply

3) Click Save the settings.

■ Configurations for Switch 2

1) Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > VLAN Config and click Add to load the following page. Create VLAN 20 and add tagged port 1/0/1 to it. Click Create.

Figure 3-4 Create VLAN 20
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch 1 - 3

text_image VLAN Config VLAN ID: 20 (2-4094, format: 2,4-5,8) VLAN Name: Department_B (1-16 characters) Untagged Ports Port: (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Tagged Ports Port: 1/0/1 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

2) Choose the menu L2 FEATURES > VLAN > GVRP to load the following page. Enable GVRP globally, then click Apply. Select port 1/0/1, set Status as Enable, and set Registration Mode as Fixed. Keep the values of the timers as default. Click Apply.

Figure 3-5 GVRP Configuration
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch 1 - 4

text_image GVRP GVRP: ✓ Enable Apply Port Config UNIT1 LAGS ID Port Status Registration Mode LeaveAll Timer (1000-30000 centiseconds) Join Timer (20-1000 centiseconds) Leave Timer (60-3000 centiseconds) LAG Enable ✓ Fixed ✓ 1 1/0/1 Enabled Fixed 1000 20 60 --- □ 2 1/0/2 Disabled Normal 1000 20 60 --- □ 3 1/0/3 Disabled Normal 1000 20 60 --- □ 4 1/0/4 Disabled Normal 1000 20 60 --- □ 5 1/0/5 Disabled Normal 1000 20 60 --- □ 6 1/0/6 Disabled Normal 1000 20 60 --- □ 7 1/0/7 Disabled Normal 1000 20 60 --- □ 8 1/0/8 Disabled Normal 1000 20 60 --- □ 9 1/0/9 Disabled Normal 1000 20 60 --- □ 10 1/0/10 Disabled Normal 1000 20 60 --- Total: 28 1 entry selected Cancel Apply

3) Click Save the settings.

■ Configurations for Switch 5

1) Choose the menu L2 FEATURES > VLAN > GVRP to load the following page. Enable GVRP globally, then click Apply. Select ports 1/0/1-3, set Status as Enable, and keep the Registration Mode and the values of the timers as default. Click Apply.

Figure 3-6 GVRP Configuration
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch 1 - 5

text_image GVRP GVRP: ✓ Enable Apply Port Config UNIT1 LAGS ID Port Status Registration Mode LeaveAll Timer (1000-30000 centiseconds) Join Timer (20-1000 centiseconds) Leave Timer (60-3000 centiseconds) LAG Enable ✓ 1 1/0/1 Enabled Normal 1000 20 60 --- ✓ 2 1/0/2 Enabled Normal 1000 20 60 --- ✓ 3 1/0/3 Enabled Normal 1000 20 60 --- □ 4 1/0/4 Disabled Normal 1000 20 60 --- □ 5 1/0/5 Disabled Normal 1000 20 60 --- □ 6 1/0/6 Disabled Normal 1000 20 60 --- □ 7 1/0/7 Disabled Normal 1000 20 60 --- □ 8 1/0/8 Disabled Normal 1000 20 60 --- □ 9 1/0/9 Disabled Normal 1000 20 60 --- □ 10 1/0/10 Disabled Normal 1000 20 60 --- Total: 28 3 entries selected. Cancel Apply

2) Click Save the settings.

3.4 Using the CLI

GVRP configuration for Switch 3 is the same as Switch 1, and Switch 4 is the same as Switch 2. Other switches share similar configurations.

The following configuration procedures take Switch 1, Switch 2 and Switch 5 as examples.

■ Configurations for Switch 1

1) Enable GVRP globally.

Switch_1#configure

Switch_1(config)#gvrp

2) Create VLAN 10.

Switch_1(config)#vlan 10

Switch_1(config-vlan)#name Department_A

Switch_1(config-vlan)#exit

3) Add tagged port 1/0/1 to VLAN 10. Enable GVRP on the port and set the registration mode as Fixed.

Switch_1(config)#interface gigabitEthernet 1/0/1
Switch_1(config-if)#switchport general allowed vlan 10 tagged
Switch_1(config-if)#gvrp
Switch_1(config-if)#gvrp registration fixed
Switch_1(config-if)#end
Switch_1#copy running-config startup-config 

■ Configurations for Switch 2

1) Enable GVRP globally.

Switch_2#configure
Switch_2(config)#gvrp 

2) Create VLAN 20.

Switch_2(config)#vlan 20
Switch_2(config-vlan)#name Department_B
Switch_2(config-vlan)#exit 

3) Add tagged port 1/0/1 to VLAN 20. Enable GVRP on the port and set the registration mode as Fixed.

Switch_2(config)#interface gigabitEthernet 1/0/1
Switch_2(config-if)#switchport general allowed vlan 20 tagged
Switch_2(config-if)#gvrp
Switch_2(config-if)#gvrp registration fixed
Switch_2(config-if)#end
Switch_2#copy running-config startup-config 

■ Configurations for Switch 5

1) Enable GVRP globally.

Switch_5#configure
Switch_5(config)#gvrp 

2) Enable GVRP on ports 1/0/1-3.

Switch_5(config)#interface range gigabitEthernet 1/0/1-3
Switch_5(config-if-range)#gvrp
Switch_5(config-if-range)#end 

Switch_5#copy running-config startup-config

Verify the Configuration

Switch 1

Verify the global GVRP configuration:

Switch_1#show gvrp global

GVRP Global Status

Enabled

Verify GVRP configuration for port 1/0/1:

Switch_1#show gvrp interface

PortStatusReg-ModeLeaveAllJoinInLeaveLAG
---------------------------
Gi1/0/1EnabledFixed10002060N/A
Gi1/0/2DisabledNormal10002060N/A
...

Switch 2

Verify the global GVRP configuration:

Switch_2#show gvrp global

GVRP Global Status

Enabled

Verify GVRP configuration for port 1/0/1:

Switch_2#show gvrp interface

PortStatusReg-ModeLeaveAllJoinInLeaveLAG
---------------------------
Gi1/0/1EnabledFixed10002060N/A

Gi1/0/2 Disabled Normal 1000 20 60 N/A

...

Switch 5

Verify global GVRP configuration:

GVRP Global Status

Enabled

Verify GVRP configuration for ports 1/0/1-3:

Switch_5#show gvrp interface

PortStatusReg-ModeLeaveAllJoinInLeaveLAG
---------------------------
Gi1/0/1EnabledNormal10002060N/A
Gi1/0/2EnabledNormal10002060N/A
Gi1/0/3EnabledNormal10002060N/A
Gi1/0/4DisabledNormal10002060N/A

...

4 Appendix: Default Parameters

Default settings of GVRP are listed in the following tables.

Table 4-1 Default Settings of GVRP

Parameter Default Setting
Global Config
GVRP Disabled
Port Config
Status Disabled
Registration Mode Normal
LeaveAll Timer 1000 centiseconds
Join Timer 20 centiseconds
Leave Timer 60 centiseconds

Part 12

Configuring Private VLAN

(Only for Certain Devices)

CHAPTERS

  1. Overview
  2. Private VLAN Configurations
  3. Configuration Example
  4. Appendix: Default Parameters

1 Overview

TP-LINK Omada TL-SG2008P - Overview - 1

Note:

Private VLAN is only available on certain devices. To check whether your device supports this feature, refer to the actual web interface. If Private VLAN is available, there is L2 FEATURES > VLAN > Private VLAN in the menu structure.

Common large networks such as ISP networks generally isolate users by VLANs. However, with the increasing number of users, upper-layer devices have to create large amount of VLANs to manage all the users. According to IEEE 802.1Q protocol, each upper-layer device can create no more than 4094 VLANs, which means upper-layer devices in backbone networks will face shortage of VLANs. By creating primary VLAN and secondary VLAN, private VLAN is an effective solution to this problem.

Based on 802.1Q VLAN, private VLAN pairs a secondary VLAN with a primary VLAN. A primary VLAN can pair with more than one secondary VLANs to compose several private VLANs. In a private VLAN, Layer 2 isolation can be achieved between end users with secondary VLANs, while upper-layer devices only need to recognize primary VLANs, which solves the problem of VLAN shortage. Meanwhile, private VLAN resolves the conflicts triggered when users' need of VLANs is different from what the ISP can provide.

The network models of traditional VLAN and private VLAN are shown in Figure 1-1 and Figure 1-2 respectively. In the network model of traditional VLAN, isolation between users is achieved by creating VLAN2, VLAN3 and VLAN4. In this case, the upper-layer device, Switch A, needs to recognize 3 VLANs including VLAN2, VLAN3 and VLAN4.

Figure 1-1 Topology of Traditional VLAN
TP-LINK Omada TL-SG2008P - Note: - 1

flowchart
graph TD
    A["Switch A"] --> B["Switch B"]
    B --> C["VLAN2"]
    B --> D["VLAN3"]
    B --> E["VLAN4"]

If private VLAN is configured on Switch B, Switch A only needs to recognize primary VLAN, VLAN5; and end users can be isolated by secondary VLANs, VLAN2, VLAN3 and VLAN4, saving VLAN resources for Switch A.

Figure 1-2 Topology of Private VLAN
TP-LINK Omada TL-SG2008P - Note: - 2

flowchart
graph TD
    SwitchA["Switch A"] --> SwitchB["Switch B"]
    SwitchB --> VLAN5["VLAN5"]
    SwitchB --> VLAN2["VLAN2"]
    SwitchB --> VLAN3["VLAN3"]
    SwitchB --> VLAN4["VLAN4"]
    SwitchB --> VLAN5b["VLAN5"]
    SwitchB --> VLAN3b["VLAN3"]
    SwitchB --> VLAN4b["VLAN4"]

2 Private VLAN Configurations

2.1 Using the GUI

TP-LINK Omada TL-SG2008P - Using the GUI - 1

Note:

If you need to create a private VLAN with existing VLANs, delete all member ports of the existing VLANs before creating the private VLAN.

Choose the menu L2 FEATURES > VLAN > Private VLAN and click + Add to load the following page.

Figure 2-1 Configuring Private VLAN
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image Private VLAN Config Primary VLAN: (2-4094) Secondary VLAN: (2-4094, format: 2,4-5,8) Secondary VLAN Type: Community Isolated Promiscuous Ports Port: (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available Host Ports Port: (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 Selected Unselected Not Available Cancel Create

1) Enter the IDs of Primary VLAN and Secondary VLAN, and select Secondary VLAN Type.

Primary VLAN Enter an ID for Primary VLAN. A primary VLAN can pair with more than one secondary VLANs to compose several private VLANs.
Secondary VLANEnter an ID or an ID list for Secondary VLAN. A secondary VLAN can pair with only one primary VLAN to compose one private VLAN. To avoid long response time of the switch, you are recommended to create less than 10 secondary VLANs at a time.
Secondary VLAN TypeSelect the Secondary VLAN Type.Isolated: Select this option and users in the same isolated VLAN cannot communicate with each other.Community: Select this option and users in the same community VLAN can communicate with each other.

2) Select promiscuous ports and host ports to be added to the private VLAN.

Promiscuous PortsSelect promiscuous ports to be added to the VLAN. The port type of up-link port in a primary VLAN must be Promiscuous. This type of port is used to connect upper-layer devices or connect the switch with other switches. The PVID of this port is its primary VLAN ID and the egress rule is untagged.
Host PortsSelect host ports to be added to the VLAN. The port type of down-link port in a secondary VLAN must be Host. This type of port is used to connect to end users and shield information from upper-layer devices. The PVID of this port is its secondary VLAN ID and the egress rule is untagged.

3) Click Create.

TP-LINK Omada TL-SG2008P - Using the GUI - 3

Note:

When configuring the up-link port, you only need to add the port to one private VLAN and set the port type as Promiscuous. The switch will automatically add the port to private VLANs with the same primary VLAN.

2.2 Using the CLI

2.2.1 Creating Private VLAN

TP-LINK Omada TL-SG2008P - Creating Private VLAN - 1

Note:

If you need to create a private VLAN with existing VLANs, delete all member ports of the existing VLANs before creating the private VLAN.

Follow these steps to create Private VLAN:

Step 1 configure

Enter global configuration mode.

Step 2 vlanvlan-listSpecify Primary VLAN ID, and enter VLAN configuration mode.vlan-list: Specify the ID or the ID list of the VLAN(s) for configuration. The ID ranges from 2 to 4094, for example, 2-3,5.
Step 3 private-vlan primarySpecify the VLAN to be the primary VLAN.
Step 4 exitExit VLAN configuration mode.
Step 5 vlanvlan-listSpecify Primary VLAN ID, and enter VLAN configuration mode.vlan-list: Specify the ID or the ID list of the VLAN(s) for configuration. The ID ranges from 2 to 4094, for example, 2-3,5.
Step 6private-vlan { community | isolated }Specify the VLAN to be the secondary VLAN, and configure the secondary VLAN type.community: Set the secondary VLAN type as Community. Users in the same isolated VLAN cannot communicate with each other.isolated: Set the secondary VLAN type as Isolated. Users in the same community VLAN can communicate with each other.
Step 7 exitExit VLAN configuration mode.
Step 8 vlanvlan-idSpecify the primary VLAN ID, and enter VLAN configuration mode.
Step 9 private-vlan associationvlan-listSpecify the ID or the ID list of the secondary VLAN(s) to pair with this primary VLAN. To avoid long response time of the switch, you are recommended to pair less than 10 secondary VLANs with the primary VLAN at a time.vlan-list: Specify the ID or the ID list of the secondary VLAN(s).
Step 10 show vlan private-vlanVerify configurations of private VLAN.
Step 11 endReturn to Privileged EXEC Mode.
Step 12 copy running-config startup-configSave the settings in the configuration file.

The following example shows how to create primary VLAN 6 and secondary VLAN 5, set the secondary VLAN type as community, and pair primary VLAN 6 with secondary VLAN 5 as a private VLAN.

Switch#configure

Switch(config)#vlan 6

Switch(config-vlan)#private-vlan primary

Switch(config-vlan)#exit

Switch(config)#vlan 5

Switch(config-vlan)#private-vlan community

Switch(config-vlan)#exit

Switch(config)#vlan 6

Switch(config-vlan)#private-vlan association 5

Switch(config-vlan)#exit

Switch(config)#show vlan private-vlan

Primary Secondary Type Ports

6 5 Community

Switch(config)#end

Switch#copy running-config startup-config

Follow these steps to add up-link ports to Private VLAN:

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}

Enter interface configuration mode.

Step 3 switchport private-vlan promiscuous

Configure the port type as Promiscuous. The port type of up-link port in a primary VLAN must be Promiscuous. This type of port is used to connect upper-layer devices or connect the switch with other switches. The PVID of this port is its primary VLAN ID.

Step 4 switchport private-vlan mapping

primary-vlan-id secondary-vlan-id

Add the specified port(s) to the private VLAN.

primary-vlan-id: Specify the ID of the primary VLAN. The ID ranges from 2 to 4094.

secondary-vlan-id: Specify the ID of the secondary VLAN. The ID ranges from 2 to 4094.

Step 5 show vlan private-vlan

Verify configurations of private VLAN.

Step 6 show vlan private-vlan interface [fastEthernet

port | gigabitEthernet port | ten-

gigabitEthernet port | port-channel lag-id]

Verify private VLAN configurations of ports.

port: Specify the ID of the port to show information.

lag-id: Specify the ID of the LAG to show information.

Step 7 end

Return to Privileged EXEC Mode.

Step 8 copy running-config startup-config

Save the settings in the configuration file.

TP-LINK Omada TL-SG2008P - Step 8 copy running-config startup-config - 1

Note:

When configuring the up-link port, you only need to add the port to one private VLAN and set the port type as Promiscuous. The switch will automatically add the port to private VLANs with the same primary VLAN.

The following example shows how to configure the port type of port 1/0/2 as Promiscuous, and add it to the private VLAN composed of primary VLAN 6 and secondary VLAN 5.

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/2

Switch(config-if)#switchport private-vlan promiscuous

Swtich(config-if)#switchport private-vlan mapping 6 5

Switch(config-if)#exit

Switch(config)#show vlan private-vlan

Primary

Secondary

Type

Ports

6

5

Community

Gi1/0/2

Switch(config)#show vlan private-vlan interface gigabitEthernet 1/0/2

Port

type

Gi1/0/2 Promiscuous

Switch(config)#end

Switch#copy running-config startup-config

Follow these steps to add down-link ports to Private VLAN:

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet

port | range fastEthernet port-list | gigabitEthernet port | range

gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}

Enter interface configuration mode.

Step 3 switchport private-vlan host

Configure the port type as host. The port type of down-link port in a secondary VLAN must be Host. This type of port is used to connect to end users and shield information from upper-layer devices. The PVID of this port is its secondary VLAN ID.

Step 4 switchport private-vlan host-association

primary-vlan-id secondary-vlan-id vlantype

Add the specified port(s) to the private VLAN.

primary-vlan-id: Specify the ID of the primary VLAN. The ID ranges from 2 to 4094.

secondary-vlan-id: Specify the ID of the secondary VLAN. The ID ranges from 2 to 4094.

vlantype: Specify the secondary VLAN type, either community or isolated.

Step 5 show vlan private-vlan

Verify configurations of private VLAN.

Step 6 show vlan private-vlan interface [fastEthernet

port | gigabitEthernet port | ten-

gigabitEthernet port | port-channel lag-id]

Verify private VLAN configurations of ports.

port: Specify the ID of the port to show information.

lag-id: Specify the ID of the LAG to show information.

Step 7 end

Return to Privileged EXEC Mode.

Step 8 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to configure the port type of port 1/0/3 as Host, and add it to the private VLAN composed of primary VLAN 6 and secondary VLAN 5.

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/3

Switch(config-if)#switchport private-vlan host

Swtich(config-if)#switchport private-vlan host-association 6 5 community

Switch(config-if)#exit

Switch(config)#show vlan private-vlan

Primary Secondary Type Ports

6 5 Community Gi1/0/3

Switch(config)#show vlan private-vlan interface gigabitEthernet 1/0/3

Port type

Gi1/0/3 Host

Switch(config)#end

Switch#copy running-config startup-config

3 Configuration Example

3.1 Network Requirements

Usually, an ISP divides its network into subnets to differentiate different areas by using VLAN. Company A belongs to Area VI which is marked as VLAN 6 by the ISP. It is required that departments in Company A can achieve Layer 2 isolation by using VLAN and users in the same department can communicate with each other.

3.2 Configuration Scheme

You can create primary VLAN and secondary VLAN and pair them into private VLAN. This allows upper-layer switch to recognize only the primary VLAN instead of all the secondary VLANs. Also, Company A can achieve Layer 2 isolation by using secondary VLAN.

Since it is required that users in the same department can communicate with each other, secondary VLAN type should be configured as Community.

3.3 Network Topology

As shown in the following figure, Switch C is the ISP's central switch, and Switch A is in Company A. To meet the requirement, configure private VLAN on Switch A. This chapter provides configuration procedures in two ways: using the GUI and using the CLI.

Demonstrated with T2600G-28TS, this chapter provides configuration procedures in two ways: using the GUI and using the CLI.

Figure 3-1 Network Topology
TP-LINK Omada TL-SG2008P - Network Topology - 1

flowchart
graph TD
    A["Switch C\nGi1/0/3"] --> B["Company A\nSwitch A\nGi1/0/2"]
    A --> C["..."]
    B --> D["VLAN6\nGi1/0/10 Gi1/0/11"]
    B --> E["VLAN7\n...<br>...<br>"]
    C --> F["..."]

3.4 Using the GUI

■ Configurations for Switch A

1) Choose the menu L2 FEATURES > VLAN > Private VLAN and click Add to load the following page. Create primary VLAN 6 and secondary VLAN 5, select Community as the Secondary VLAN Type. Add promiscuous port 1/0/2 and host port 1/0/10 to private VLAN.

Figure 3-2 Creating Primary VLAN 6 and Secondary VLAN 5
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch A - 1

text_image Private VLAN Config Primary VLAN: 6 (2-4094) Secondary VLAN: 5 (2-4094, format: 2,4-5,8) Secondary VLAN Type: Community Isolated Promiscuous Ports Port: 1/0/2 (Format: 1/0/1, input or choose below) UNIT 1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available Host Ports Port: 1/0/10 (Format: 1/0/1, input or choose below) UNIT 1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28

2) Choose the menu L2 FEATURES > VLAN > Private VLAN and click Add to load the following page. Create primary VLAN 6 and secondary VLAN 7, select Community as the Secondary VLAN Type. Add promiscuous port 1/0/2 and host port 1/0/11 to private VLAN.

Figure 3-3 Creating Primary VLAN 6 and Secondary VLAN 7
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch A - 2

text_image Private VLAN Config Primary VLAN: 6 (2-4094) Secondary VLAN: 7 (2-4094, format: 2,4-5,8) Secondary VLAN Type: Community Isolated Promiscuous Ports Port: 1/0/2 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Z 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available Host Ports Port: 1/0/11 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available Cancel Create

3) Click Save the settings.

■ Configurations for Switch C

1) Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > VLAN Config and click Add to load the following page. Create VLAN 6 and add untagged port 1/0/3 to VLAN 6. Click Create.

Figure 3-4 Creating VLAN 6
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch A - 3

text_image VLAN Config VLAN ID: 6 (2-4094, format: 2,4-5,8) VLAN Name: vlan6 (1-16 characters) Untagged Ports Port: 1/0/3 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available Tagged Ports Port: (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available Cancel Create

2) Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > Port Config to load the following page. Set the PVID of port 1/0/3 as 6. Click Apply.

Figure 3-5 Cpecifying the PVID
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch A - 4

text_image Port Config UNIT1 LAGS Port PVID Ingress Checking Acceptable Frame Types LAG Details 6 ▼ ▼ 1/0/1 1 Enabled Admit All --- Details 1/0/2 1 Enabled Admit All --- Details ✓ 1/0/3 6 Enabled Admit All --- Details 1/0/4 1 Enabled Admit All --- Details 1/0/5 1 Enabled Admit All --- Details 1/0/6 1 Enabled Admit All --- Details 1/0/7 1 Enabled Admit All --- Details 1/0/8 1 Enabled Admit All --- Details 1/0/9 1 Enabled Admit All --- Details 1/0/10 1 Enabled Admit All --- Details Total: 28 1 entry selected. Cancel Apply

3) Click save the settings.

3.5 Using the CLI

■ Configurations for Switch A

1) Enter global configuration mode.

Switch_A>enable

Switch_A#configure

2) Create primary VLAN 6 and secondary VLAN 5, and pair them into a private VLAN.

Switch_A(config)#vlan 6

Switch_A(config-vlan)#private-vlan primary

Switch_A(config-vlan)#exit

Switch_A(config)#vlan 5

Switch_A(config-vlan)#private-vlan community

Switch_A(config-vlan)#exit

Switch_A(config)#vlan 6

Switch_A(config-vlan)#private-vlan association 5

Switch_A(config-vlan)#exit

3) Create secondary VLAN 7, and pair it with primary VLAN 6 into a private VLAN.

Switch_A(config)#vlan 7

Switch_A(config-vlan)#private-vlan community

Switch_A(config-vlan)#exit

Switch_A(config)#vlan 6

Switch_A(config-vlan)#private-vlan association 7

Switch_A(config-vlan)#exit

4) Add up-link port to the corresponding private VLAN and configure the port type as Promiscuous.

Switch_A(config)#interface gigabitEthernet 1/0/2

Switch_A(config-if)#switchport private-vlan promiscuous

Switch_A(config-if)#switchport private-vlan mapping 6 5

Switch_A(config-if)#exit

5) Add down-link port to the corresponding private VLAN and configure the port type as Host.

Switch_A(config)#interface gigabitEthernet 1/0/10

Switch_A(config-if)#switchport private-vlan host

Switch_A(config-if)#switchport private-vlan host-association 6 5 community

Switch_A(config-if)#exit

Switch_A(config)#interface gigabitEthernet 1/0/11

Switch_A(config-if)#switchport private-vlan host

Switch_A(config-if)#switchport private-vlan host-association 6 7 community

Switch_A(config-if)#end

Switch_A#copy running-config startup-config

■ Configurations for Switch C

1) Enter global configuration mode.

Switch_C>enable

Switch_C#configure

2) Create VLAN 6, add port 1/0/3 to VLAN 6 and set the PVID of port 1/0/3 as 6.

Switch_C(config)#vlan 6

Switch_C(config-vlan)#name vlan6

Switch_C(config-vlan)#exit

Switch_C(config)#interface gigabitEthernet 1/0/3

Switch_C(config-if)#switchport pvid 6

Switch_C(config-if)#switchport general allowed vlan 6 untagged

Switch_C(config-if)#end

Switch_C#copy running-config startup-config

Verify the Configurations

Switch A

Verify the configuration of private VLAN:

Switch_A#show vlan private-vlan

PrimarySecondaryTypePorts
65CommunityGi1/0/2,1/0/10
67CommunityGi1/0/2,1/0/11

Verify the configuration of ports:

Swtich_A#show vlan private-vlan interface

Port type

Gi1/0/1 Normal

Gi1/0/2 Promiscuous

Gi1/0/3 Normal

Gi1/0/4 Normal

Gi1/0/5 Normal

Gi1/0/6 Normal

Gi1/0/7 Normal

Gi1/0/8 Normal

Gi1/0/9 Normal

Gi1/0/10 Host

Gi1/0/11 Host

Gi1/0/12 Normal

...

Switch C

Verify the configuration of 802.1Q VLAN:

Switch_C#show vlan

VLANNameStatusPorts
1System-VLANactiveGi1/0/1, Gi1/0/2, Gi1/0/3, Gi1/0/4, Gi1/0/5, Gi1/0/6, Gi1/0/7, Gi1/0/8, Gi1/0/9, Gi1/0/10, Gi1/0/11, Gi1/0/12, Gi1/0/13, Gi1/0/14, Gi1/0/15, Gi1/0/16, Gi1/0/17, Gi1/0/18, Gi1/0/19, Gi1/0/20, Gi1/0/21, Gi1/0/22, Gi1/0/23, Gi1/0/24, Gi1/0/25, Gi1/0/26, Gi1/0/27, Gi1/0/28
6vlan6activeGi1/0/3
PrimarySecondaryTypePorts
----------------

4 Appendix: Default Parameters

Default settings of Private VLAN are listed in the following tables.

Table 4-1 Default Settings of Private VLAN

Parameter Default Setting
Primary VLAN None
Secondary VLAN None
Secondary VLAN Type Community

Part 13

Configuring Layer 2 Multicast

CHAPTERS

  1. Layer 2 Multicast
  2. IGMP Snooping Configuration
  3. MLD Snooping Configuration
  4. MVR Configuration
  5. Multicast Filtering Configuration
  6. Viewing Multicast Snooping Information
  7. Configuration Examples
  8. Appendix: Default Parameters

1 Layer 2 Multicast

1.1 Overview

In a point-to-multipoint network, packets can be sent in three ways: unicast, broadcast and multicast. With unicast, many copies of the same information will be sent to all the receivers, occupying a large bandwidth.

With broadcast, information will be sent to all users in the network no matter they need it or not, wasting network resources and impacting information security.

Multicast, however, solves all the problems caused by unicast and broadcast. With multicast, the source only need to send one piece of information, and all and only the users who need the information will receive copies of the information. In a point-to-multipoint network, multicast technology not only transmits data with high efficiency, but also saves a large bandwidth and reduces network load.

In practical applications, Internet information provider can provide value-added services such as Online Live, IPTV, Distance Education, Telemedicine, Internet Radio and Real-time Video Conferences more conveniently using multicast.

Layer 2 Multicast allows Layer 2 switches to listen for IGMP (Internet Group Management Protocol) packets between IGMP Querier and user hosts to establish multicast forwarding table and to manage and control transmission of packets.

Take IGMP Snooping as an example. When IGMP Snooping is disabled on the Layer 2 device, multicast packets will be broadcast in the Layer 2 network; when IGMP Snooping is enabled on the Layer 2 device, multicast data from a known multicast group will be transmitted to the designated receivers instead of being broadcast in the Layer 2 network.

Demonstrated as below:

Figure 1-1 IGMP Snooping
TP-LINK Omada TL-SG2008P - Demonstrated as below: - 1

flowchart
graph TD
    A["Source"] --> B["IGMP Querier"]
    B --> C["Non-Snooping Switch"]
    C --> D["Host A Host B Host C"]
    C --> E["Host A Host B Host C"]
    C --> F["Host A Host B Host C"]
    C --> G["Host A Host B Host C"]
    style A fill:#99ccff,stroke:#333
    style B fill:#99ccff,stroke:#333
    style C fill:#66ccff,stroke:#333
    style D fill:#99ccff,stroke:#333
    style E fill:#99ccff,stroke:#333
    style F fill:#99ccff,stroke:#333
    style G fill:#99ccff,stroke:#333
    note1["Multicast packets transmission without IGMP Snooping"]
    note2["Multicast packets"]

TP-LINK Omada TL-SG2008P - Demonstrated as below: - 2

flowchart
graph TD
    A["Source"] --> B["IGMP Querier"]
    B --> C["Router Port"]
    C --> D["Snooping Switch"]
    D --> E["Member Port"]
    D --> F["Host A Host B Host C"]
    D --> G["Member Port"]
    style A fill:#333,stroke:#fff,color:#fff
    style B fill:#999,stroke:#000,color:#fff
    style C fill:#999,stroke:#000,color:#fff
    style D fill:#999,stroke:#000,color:#fff
    style E fill:#666,stroke:#000,color:#fff
    style F fill:#666,stroke:#000,color:#fff
    style G fill:#666,stroke:#000,color:#fff
    note1["Multicast packets transmission with IGMP Snooping"]

The following basic concepts of IGMP Snooping will be introduced: IGMP querier, snooping switch, router port and member port.

IGMP Querier

An IGMP querier is a multicast router (a router or a Layer 3 switch) that sends query messages to maintain a list of multicast group memberships for each attached network, and a timer for each membership.

Normally only one device acts as querier per physical network. If there are more than one multicast router in the network, a querier election process will be implemented to determine which one acts as the querier.

Snooping Switch

A snooping switch indicates a switch with IGMP Snooping enabled. The switch maintains a multicast forwarding table by snooping on the IGMP transmissions between the host and the querier. With the multicast forwarding table, the switch can forward multicast data only to the ports that are in the corresponding multicast group, so as to constrain the flooding of multicast data in the Layer 2 network.

Router Port

A router port is a port on snooping switch that is connecting to the IGMP querier.

Member Port

A member port is a port on snooping switch that is connecting to the host.

1.2 Supported Features

Layer 2 Multicast protocol for IPv4: IGMP Snooping

On the Layer 2 device, IGMP Snooping transmits data on demand on data link layer by analyzing IGMP packets between the IGMP querier and the users, to build and maintain Layer 2 multicast forwarding table.

Layer 2 Multicast protocol for IPv6: MLD Snooping

On the Layer 2 device, MLD Snooping (Multicast Listener Discovery Snooping) transmits data on demand on data link layer by analyzing MLD packets between the MLD querier and the users, to build and maintain Layer 2 multicast forwarding table.

Multicast VLAN Registration (MVR)

MVR allows a single multicast VLAN to be shared for multicast member ports in different VLANs in IPv4 network. In IGMP Snooping, if member ports are in different VLANs, a copy of the multicast streams is sent to each VLAN that has member ports. While MVR provides a dedicated multicast VLAN to forward multicast traffic over the Layer 2 network, to avoid duplication of multicast streams for clients in different VLANs. Clients can dynamically join or leave the multicast VLAN without interfering with their relationships in other VLANs.

There are two types of MVR modes:

■ Compatible Mode

In compatible mode, the MVR switch does not forward report or leave messages from the hosts to the IGMP querier. So the IGMP querier cannot learn the multicast groups membership information from the MVR switch. You have to statically configure the IGMP querier to transmit all the required multicast streams to the MVR switch via the multicast VLAN.

■ Dynamic Mode

In dynamic mode, after receiving report or leave messages from the hosts, the MVR switch will forward them to the IGMP querier via the multicast VLAN (with appropriate translation of the VLAN ID). So the IGMP querier can learn the multicast groups membership information through the report and leave messages, and transmit the multicast streams to the MVR switch via the multicast VLAN according to the multicast forwarding table.

Multicast Filtering

Multicast Filtering allows you to control the set of multicast groups to which a host can belong. You can filter multicast joins on a per-port basis by configuring IP multicast profiles (IGMP profiles or MLD profiles) and associating them with individual switch ports.

2 IGMP Snooping Configuration

To complete IGMP Snooping configuration, follow these steps:

1) Enable IGMP Snooping globally and configure the global parameters.
2) Configure IGMP Snooping for VLANs.
3) Configure IGMP Snooping for ports.
4) (Optional) Configure hosts to statically join a group.

TP-LINK Omada TL-SG2008P - IGMP Snooping Configuration - 1

Note:

IGMP Snooping takes effect only when it is enabled globally, in the corresponding VLAN and port at the same time.

2.1 Using the GUI

2.1.1 Configuring IGMP Snooping Globally

Choose the menu L2 FEATURES > Multicast > IGMP Snooping > Global Config to load the following page.

Figure 2-1 Configure IGMP Snooping Globally
TP-LINK Omada TL-SG2008P - Configuring IGMP Snooping Globally - 1

text_image Global Config IGMP Snooping: Enable IGMP Version: v1 v2 v3 Unknown Multicast Groups: Forward Discard Header Validation: Enable Apply

Follow these steps to configure IGMP Snooping globally:

1) In the Global Config section, enable IGMP Snooping globally and configure the global parameters.

IGMP Snooping Enable or disable IGMP Snooping globally.

IGMP Version Specify the IGMP version.

v1: The switch works as an IGMPv1 Snooping switch. It can only process IGMPv1 messages from the host. Messages of other versions are ignored.

v2: The switch works as an IGMPv2 Snooping switch. It can process both IGMPv1 and IGMPv2 messages from the host. IGMPv3 messages are ignored.

v3: The switch works as an IGMPv3 Snooping switch. It can process IGMPv1, IGMPv2 and IGMPv3 messages from the host.

Unknown

Multicast Groups

Set the way in which the switch processes data that are sent to unknown multicast groups as Forward or Discard. By default, it is Forward.

Unknown multicast groups are multicast groups that do not match any of the groups announced in earlier IGMP membership reports, and thus cannot be found in the multicast forwarding table of the switch.

Note: IGMP Snooping and MLD Snooping share the setting of Unknown Multicast Groups, so you have to enable MLD Snooping globally on the L2 FEATURES > Multicast > MLD Snooping > Global Config page at the same time.

Header Validation Enable or disable Header Validation. By default, it is disabled.

Generally, for IGMP packets, the TTL value should be 1, ToS field should be 0xC0, and Router Alert option should be 0x94040000. The fields to be validated depend on the IGMP version being used. IGMPv1 only checks the TTL field. IGMPv2 checks the TTL field and the Router Alert option. IGMPv3 checks TTL field, ToS field and Router Alert option. Packets that fail the validation process will be dropped.

2) Click Apply.

2.1.2 Configuring IGMP Snooping for VLANs

Before configuring IGMP Snooping for VLANs, set up the VLANs that the router ports and the member ports are in. For details, please refer to Configuring 802.1Q VLAN.

The switch supports configuring IGMP Snooping on a per-VLAN basis. After IGMP Snooping is enabled globally, you also need to enable IGMP Snooping and configure the corresponding parameters for the VLANs that the router ports and the member ports are in.

Choose the menu L2 FEATURES > Multicast > IGMP Snooping > Global Config, and click in your desired VLAN entry in the IGMP VLAN Config section to load the following page.

Figure 2-2 Configure IGMP Snooping for VLAN
TP-LINK Omada TL-SG2008P - Configuring IGMP Snooping for VLANs - 1

text_image Configure IGMP Snooping for VLAN VLAN ID: 1 IGMP Snooping Status: Enable Fast Leave: Enable Report Suppression: Enable Member Port Aging Time: 260 seconds (60-600) Router Port Aging Time: 300 seconds (60-600) Leave Time: 1 seconds (1-30) IGMP Snooping Querier: Enable Static Router Ports UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Cancel Save

Follow these steps to configure IGMP Snooping for a specific VLAN:

1) Enable IGMP Snooping for the VLAN, and configure the corresponding parameters.

VLAN ID Displays the VLAN ID.

IGMP Snooping Status

Enable or disable IGMP Snooping for the VLAN.

Fast Leave Enable or disable Fast Leave for the VLAN. IGMPv1 does not support Fast Leave.
Without Fast Leave, after a receiver sends an IGMP leave message to leave a multicast group, the switch will forward the leave message to the Layer 3 device (the querier).
From the point of view of the querier, the port connecting to the switch is a member port of the corresponding multicast group. After receiving the leave message from the switch, the querier will send out a configured number (Last Member Query Count) of group-specific queries on that port with a configured interval (Last Member Query Interval), and wait for IGMP group membership reports. If there are other receivers connecting to the switch, they will response to the queries before the Last Member Query Interval expires. If no reports are received after the response time of the last query expires, the querier will remove the port from the forwarding list of the corresponding multicast group.
That is, if there are other receivers connecting to the switch, the one sent leave message have to wait until the port ages out from the switch's forwarding list of the corresponding multicast group (the maximum waiting time is decided by the Member Port Aging Time).
With Fast Leave enabled on a VLAN, the switch will remove the (Multicast Group, Port, VLAN) entry from the multicast forwarding table before forwarding the leave message to the querier. This helps to reduce bandwidth waste since the switch no longer sends the corresponding multicast streams to the VLAN of the port as soon as the port receives a leave message from the VLAN.
Report SuppressionEnable or disable Report Suppression for the VLAN.
When enabled, the switch will only forward the first IGMP report message for each multicast group to the IGMP querier and suppress subsequent IGMP report messages for the same multicast group during one query interval. This feature prevents duplicate report messages from being sent to the IGMP querier.
Member Port Aging TimeSpecify the aging time of the member ports in the VLAN.
Once the switch receives an IGMP membership report message from a port, the switch adds this port to the member port list of the corresponding multicast group. Member ports that are learned in this way are called dynamic member ports.
If the switch does not receive any IGMP membership report messages for a specific multicast group from a dynamic member port, it will no longer consider this port as a member port of this multicast group and delete it from the multicast forwarding table.
Router Port Aging TimeSpecify the aging time of the router ports in the VLAN.
Once the switch receives an IGMP general query message from a port, the switch adds this port to the router port list. Router ports that are learned in this way are called dynamic router ports.
If the switch does not receive any IGMP general query message from a dynamic router port within the router port aging time, the switch will no longer consider this port as a router port and delete it from the router port list.
Leave Time Specify the leave time for the VLAN.
When the switch receives a leave message from a port to leave a multicast group, it will wait for a leave time before removing the port from the multicast group. During the period, if the switch receives any report messages from the port, the port will not be removed from the multicast group. Exceptions are as follows:If the member port ages out before the Leave Time ends and no report messages are received, the port will be removed from the multicast group once its Member Port Aging Time ends.The Leave Time mechanism will not take effect when Fast Leave takes effect.A proper leave time value can avoid other hosts connecting to the same port of the switch being mistakenly removed from the multicast group when only some of them want to leave.
IGMP Snooping QuerierEnable or disable the IGMP Snooping Querier for the VLAN.When enabled, the switch acts as an IGMP Snooping Querier for the hosts in this VLAN. A querier periodically sends a general query on the network to solicit membership information, and sends group-specific queries when it receives leave messages from hosts.
Query IntervalWith IGMP Snooping Querier enabled, specify the interval between general query messages sent by the switch.
Maximum Response TimeWith IGMP Snooping Querier enabled, specify the host's maximum response time to general query messages.
Last Member Query IntervalWith IGMP Snooping Querier enabled, when the switch receives an IGMP leave message, it obtains the address of the multicast group that the host wants to leave from the message. Then the switch sends out group-specific queries to this multicast group through the port receiving the leave message. This parameter determines the interval between group-specific queries.
Last Member Query CountWith IGMP Snooping Querier enabled, specify the number of group-specific queries to be sent. If specified count of group-specific queries are sent and no report message is received, the switch will delete the multicast address from the multicast forwarding table.
General Query Source IPWith IGMP Snooping Querier enabled, specify the source IP address of the general query messages sent by the switch. It should be a unicast address.
Static Router PortsSelect one or more ports to be the static router ports in the VLAN. Static router ports do not age.Multicast streams and IGMP packets to all groups in this VLAN will be forwarded through the static router ports. Multicast streams and IGMP packets to the groups that have dynamic router ports will be also forwarded through the corresponding dynamic router ports.
Forbidden Router PortsSelect ports to forbid them from being router ports in the VLAN.

2) Click Save.

2.1.3 Configuring IGMP Snooping for Ports

Choose the menu L2 FEATURES > Multicast > IGMP Snooping > Port Config to load the following page.

Figure 2-3 Configure IGMP Snooping for Ports
TP-LINK Omada TL-SG2008P - Configuring IGMP Snooping for Ports - 1

text_image Port Config UNIT1 LAGS Port IGMP Snooping Fast Leave LAG ✓ 1/0/1 Enabled Disabled -- □ 1/0/2 Enabled Disabled -- □ 1/0/3 Enabled Disabled -- □ 1/0/4 Enabled Disabled -- □ 1/0/5 Enabled Disabled -- □ 1/0/6 Enabled Disabled -- □ 1/0/7 Enabled Disabled -- □ 1/0/8 Enabled Disabled -- □ 1/0/9 Enabled Disabled -- □ 1/0/10 Enabled Disabled -- Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure IGMP Snooping for ports:

1) Enable IGMP Snooping for the port and enable Fast Leave if there is only one receiver connected to the port.

IGMP Snooping Enable or disable IGMP Snooping for the port.

Fast Leave Enable or disable Fast Leave for the port. IGMPv1 does not support fast leave.

Fast Leave can be enabled on a per-port basis or per-VLAN basis. When enabled on a per-port basis, the switch will remove the port from the corresponding multicast group of all VLANs before forwarding the leave message to the querier.

You should only use Fast Leave for a port when there is a single receiver connected to the port. For more details about Fast Leave, see 2.1.2 Configuring IGMP Snooping for VLANs.

LAG Displays the LAG the port belongs to.

2) Click Apply.

2.1.4 Configuring Hosts to Statically Join a Group

Hosts or Layer 2 ports normally join multicast groups dynamically, but you can also configure hosts to statically join a group.

Choose the menu L2 FEATURES > Multicast > IGMP Snooping > Static Group Config and click + Add to load the following page.

Figure 2-4 Configure Hosts to Statically Join a Group
TP-LINK Omada TL-SG2008P - Configuring Hosts to Statically Join a Group - 1

text_image Create Static Multicast Group Multicast IP: (Format: 235.0.0.1) VLAN ID: (1-4094) Member Ports: UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

Follow these steps to configure hosts to statically join a group:

1) Specify the multicast IP address, VLAN ID. Select the ports to be the static member ports of the multicast group.

Multicast IP Specify the address of the multicast group that the hosts need to join.

VLAN ID Specify the VLAN that the hosts are in.

Member Ports Select the ports that the hosts are connected to. These ports will become the static member ports of the multicast group and will never age.

2) Click Create.

2.1.5 Configuring IGMP Accounting and Authentication Features

TP-LINK Omada TL-SG2008P - Configuring IGMP Accounting and Authentication Features - 1

Note:

IGMP Accounting and Authentication is only available on certain devices. To check whether your device supports this feature, refer to the actual web interface.

You can enable IGMP accounting and authentication according to your need. IGMP accounting is configured globally, and IGMP authentication can be enabled on a per-port basis.

To use these features, you should also set up a RADIUS server and go to SECURITY > AAA > RADIUS Config to configure RADIUS server for the switch.

Choose the menu L2 FEATURES > Multicast > IGMP Snooping > IGMP Authentication to load the following page.

Figure 2-5 Configure IGMP Accounting and Authentication
TP-LINK Omada TL-SG2008P - Note: - 1

text_image Global Config Accounting: ☐ Enable Apply Port Config UNIT1 LAGS ID Port IGMP Authentication LAG ✓ 1 1/0/1 Disabled --- ☐ 2 1/0/2 Disabled --- ☐ 3 1/0/3 Disabled --- ☐ 4 1/0/4 Disabled --- ☐ 5 1/0/5 Disabled --- ☐ 6 1/0/6 Disabled --- ☐ 7 1/0/7 Disabled --- ☐ 8 1/0/8 Disabled --- ☐ 9 1/0/9 Disabled --- ☐ 10 1/0/10 Disabled --- Total: 28 1 entry selected. Cancel Apply

Follow these steps to enable IGMP accounting:

1) In the Global Config section, enable IGMP Accounting globally.

Accounting Enable or disable IGMP Accounting.

2) Click Apply.

Follow these steps to configure IGMP Authentication on ports:

1) In the Port Config section, select the ports and enable IGMP Authentication.

IGMP

Enable or disable IGMP Authentication for the port.

Authentication

2) Click Apply.

2.2 Using the CLI

2.2.1 Configuring IGMP Snooping Globally

Follow these steps to configure IGMP Snooping globally:

Step 1 configure

Enter global configuration mode.

Step 2 ip igmp snooping

Enable IGMP Snooping Globally.

Step 3 ip igmp snooping version {v1 | v2 | v3}

Configure the IGMP version.

v1:The switch works as an IGMPv1 Snooping switch. It can only process IGMPv1 report messages from the host. Report messages of other versions are ignored.
v2: The switch works as an IGMPv2 Snooping switch. It can process both IGMPv1 and IGMPv2 report messages from the host. IGMPv3 report messages are ignored.
v3: The switch works as an IGMPv3 Snooping switch. It can process IGMPv1, IGMPv2 and IGMPv3 report messages from the host.

Step 4 ip igmp snooping drop-unknown

(Optional) Configure the way how the switch processes multicast streams that are sent to unknown multicast groups as Discard. By default, it is Forward.

Unknown multicast groups are multicast groups that do not match any of the groups announced in earlier IGMP membership reports, and thus cannot be found in the multicast forwarding table of the switch.

Note: IGMP Snooping and MLD Snooping share the setting of Unknown Multicast Groups, you need to ensure MLD Snooping is enabled globally. To enable MLD Snooping globally, use the ipv6 mld snooping command in global configuration mode.

Step 5 ip igmp snooping header-validation

(Optional) Enable header validation.

Generally, for IGMP packets, the TTL value should be 1, ToS field should be 0xC0, and Router Alert option should be 0x94040000. The fields validated depend on the IGMP version being used. IGMPv1 only checks the TTL field. IGMPv2 checks the TTL field and the Router Alert option. IGMPv3 checks TTL field, ToS field and Router Alert option. Packets that fail the validation process will be dropped.

Step 6 show ip igmp snooping

Show the basic IGMP Snooping configuration.

Step 7 end

Return to privileged EXEC mode.

Step 8 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable IGMP Snooping and header validation globally, and specify the IGMP Snooping version as IGMPv3, the way how the switch processes multicast streams that are sent to unknown multicast groups as discard.

Switch#configure

Switch(config)#ip igmp snooping

Switch(config)#ip igmp snooping version v3

Switch(config)#ipv6 mld snooping

Switch(config)#ip igmp snooping drop-unknown

Switch(config)#ip igmp snooping header-validation

Switch(config)#show ip igmp snooping

IGMPSnooping:Enable
IGMPVersion:V3
UnknownMulticast:Discard
HeaderValidation:Enable
...

Switch(config)#end

Switch#copy running-config startup-config

2.2.2 Configuring IGMP Snooping for VLANs

Before configuring IGMP Snooping for VLANs, set up the VLANs that the router ports and the member ports are in. For details, please refer to Configuring 802.1Q VLAN.

The switch supports configuring IGMP Snooping on a per-VLAN basis. After IGMP Snooping is enabled globally, you also need to enable IGMP Snooping and configure the corresponding parameters for the VLANs that the router ports and the member ports are in.

Follow these steps to configure IGMP Snooping for VLANs:

Step 1 configure

Enter global configuration mode.

Step 2 ip igmp snooping vlan-config

vlan-id-list mtime member-time

Enable IGMP Snooping for the specified VLANs, and specify the member port aging time for the VLANs.

vlan-id-list: Specify the ID or the ID list of the VLAN(s).

member-time: Specify the aging time of the member ports in the specified VLANs. Valid values are from 60 to 600 seconds. By default, it is 260 seconds.

Once the switch receives an IGMP membership report message from a port, the switch adds this port to the member port list of the corresponding multicast group. Member ports that are learned in this way are called dynamic member ports.

If the switch does not receive any IGMP membership report message for a specific multicast group from a dynamic member port, it will no longer consider this port as a member port of this multicast group and delete it from the multicast forwarding table.

Step 3 ip igmp snooping vlan-config

vlan-id-list rtime router-time

Specify the router port aging time for the VLANs.

vlan-id-list: Specify the ID or the ID list of the VLAN(s).

router-time: Specify the aging time of the router ports in the specified VLANs. Valid values are from 60 to 600 seconds. By default, it is 300 seconds.

Once the switch receives an IGMP general query message from a port, the switch adds this port to the router port list. Router ports that are learned in this way are called dynamic router ports.

If the switch does not receive any IGMP general query message from a dynamic router port within the router port aging time, the switch will no longer consider this port as a router port and delete it from the router port list.

Step 4 ip igmp snooping vlan-config

vlan-id-list ltime leave-time

Specify the router port aging time for the VLANs.

vlan-id-list: Specify the ID or the ID list of the VLAN(s).

leave-time: Specify the leave time for the VLAN(s). Valid values are from 1 to 30 in seconds, and the default value is 1 second.

When the switch receives a leave message from a port to leave a multicast group, it will wait for a leave time before removing the port from the multicast group. During the period, if the switch receives any report messages from the port, the port will not be removed from the multicast group. Exceptions are as follows:

- If the member port ages out before the Leave Time ends and no report messages are received, the port will be removed from the multicast group once its Member Port Aging Time ends.

• The Leave Time mechanism will not take effect when Fast Leave takes effect.

A proper leave time value can avoid other hosts connecting to the same port of the switch being mistakenly removed from the multicast group when only some of them want to leave.

Step 5 ip igmp snooping vlan-config

vlan-id-list report-suppression

(Optional) Enable the Report Suppression for the VLANs. By default, it is disabled.

When enabled, the switch will only forward the first IGMP report message for each multicast group to the IGMP querier and suppress subsequent IGMP report messages for the same multicast group during one query interval. This feature prevents duplicate report messages from being sent to the IGMP querier.

vlan-id-list: Specify the ID or the ID list of the VLAN(s).

Step 6 ip igmp snooping vlan-config

vlan-id-list immediate-leave

(Optional) Enable the Fast Leave for the VLANs. By default, it is disabled. IGMPv1 does not support fast leave.

Without Fast Leave, after a receiver sends an IGMP leave message to leave a multicast group, the switch will forward the leave message to the Layer 3 device (the querier).

From the point of view of the querier, the port connecting to the switch is a member port of the corresponding multicast group. After receiving the leave message from the switch, the querier will send out a configured number (Last Member Query Count) of group-specific queries on that port with a configured interval (Last Member Query Interval), and wait for IGMP group membership reports. If there are other receivers connecting to the switch, they will response to the queries before the Last Member Query Interval expires. If no reports are received after the response time of the last query expires, the querier will remove the port from the forwarding list of the corresponding multicast group.

That is, if there are other receivers connecting to the switch, the one sent leave message have to wait until the port ages out from the switch's forwarding list of the corresponding multicast group (the maximum waiting time is decided by the Member Port Aging Time).

With Fast Leave enabled on a VLAN, the switch will remove the (Multicast Group, Port, VLAN) entry from the multicast forwarding table before forwarding the leave message to the querier. This helps to reduce bandwidth waste since the switch no longer sends the corresponding multicast streams to the VLAN of the port as soon as the port receives a leave message from the VLAN.

You should only enable Fast Leave for a VLAN when there is a single receiver belongs to this VLAN on every port of the VLAN.

vlan-id-list: Specify the ID or the ID list of the VLAN(s).

Step 7 ip igmp snooping vlan-config

vlan-id-list rport interface { fastEthernet port-list |

gigabitEthernet port-list | ten-gigabitEthernet port-list | port-channel lag-list}

(Optional) Specify the static router ports for the VLANs. Static router ports do not age.

vlan-id-list: Specify the ID or the ID list of the VLAN(s).

port-list: The number or the list of the Ethernet port that need to be configured as static router ports.

lag-list: The ID or the list of the LAG that need to be configured as static router ports.

Step 8 ip igmp snooping vlan-config vlan-id-list router-ports-forbidden interface {fastEthernet port-list | gigabitEthernet port-list | ten-gigabitEthernet port-list | port-channel lag-list}

(Optional) Specify the ports to forbid them from being router ports in the VLANs.

vlan-id-list: Specify the ID or the ID list of the VLAN(s).

port-list: The number or the list of the Ethernet port that need to be forbidden from being router ports.

lag-list: The ID or the list of the LAG that need to be forbidden from being router ports.

Step 9 ip igmp snooping vlan-config vlan-id-list querier

(Optional) Enable the IGMP Snooping Querier for the VLAN. By default, it is disabled.

When enabled, the switch acts as an IGMP Snooping Querier for the hosts in this VLAN. A querier periodically sends a general query on the network to solicit membership information, and sends group-specific queries when it receives leave messages from hosts.

vlan-id-list: Specify the ID or the ID list of the VLAN(s).

After enabling IGMP Snooping Querier feature, you need to specify the corresponding parameters including the Last Member Query Count, Last Member Query Interval, Maximum Response Time, Query Interval and General Query Source IP. Use the command below in global configuration mode to configure the parameters:

ip igmp snooping vlan-config vlan-id-list querier { max-response-time response-time | query-interval interval | general-query source-ip ip-addr | last-member-query-count num | last-member-query-interval interval }

vlan-id-list: Specify the ID or the ID list of the VLAN(s).

response-time: Specify the host's maximum response time to general query messages. Valid values are from 1 to 25 seconds, and the default value is 10 seconds.

query-interval interval: Specify the interval between general query messages sent by the switch. Valid values are from 10 to 300 seconds, and the default value is 60 seconds.

ip-addr: Specify the source IP address of the general query messages sent by the switch. It should be a unicast address. By default, it is 0.0.0.0.

num: Specify the number of group-specific queries to be sent. With IGMP Snooping Querier enabled, when the switch receives an IGMP leave message, it obtains the address of the multicast group that the host wants to leave from the message. Then the switch sends out group-specific queries to this multicast group through the port receiving the leave message. If specified count of group-specific queries are sent and no report message is received, the switch will delete the multicast address from the multicast forwarding table. Valid values are from 1 to 5, and the default value is 2.

last-member-query-interval interval: Specify the interval between group-specific queries. Valid values are from 1 to 5 seconds, and the default value is 1 second.

Step 10 show ip igmp snooping vlan vlan-id

Show the basic IGMP Snooping configuration in the specified VLAN.

Step 11 end

Return to privileged EXEC mode.

Step 12 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable IGMP Snooping for VLAN 1, and configure the member port aging time as 300 seconds, the router port aging time as 320 seconds, and then enable Fast Leave and Report Suppression for the VLAN:

Switch#configure

Switch(config)#ip igmp snooping vlan-config 1 mtime 300

Switch(config)#ip igmp snooping vlan-config 1 rtime 320

Switch(config)#ip igmp snooping vlan-config 1 immediate-leave

Switch(config)#ip igmp snooping vlan-config 1 report-suppression

Switch(config)#show ip igmp snooping vlan 1

Vlan Id: 1

Vlan IGMP Snooping Status: Enable

Fast Leave: Enable

Report Suppression: Enable

Router Time:320

Member Time: 300

Querier: Disable

...

Switch(config)#end

Switch#copy running-config startup-config

The following example shows how to enable IGMP Snooping querier for VLAN 1, and configure the query interval as 100 seconds, the maximum response time as 15 seconds, the last member query interval as 2 seconds, the last member query count as 3, and the general query source IP as 192.168.0.5:

Switch#configure

Switch(config)#ip igmp snooping vlan-config 1 querier

Switch(config)#ip igmp snooping vlan-config 1 querier query-interval 100

Switch(config)#ip igmp snooping vlan-config 1 querier max-response-time 15

Switch(config)#ip igmp snooping vlan-config 1 querier last-member-query-interval 2

Switch(config)#ip igmp snooping vlan-config 1 querier last-member-query-count 3

Switch(config)#ip igmp snooping vlan-config 1 querier general-query source-ip192.168.0.5

Switch(config)#show ip igmp snooping vlan 1

Vlan Id: 1

...

Querier:

Maximum Response Time: 15

Query Interval: 100

Last Member Query Interval: 2

Last Member Query Count: 3

General Query Source IP: 192.168.0.5

...

Switch(config)#end

Switch#copy running-config startup-config

2.2.3 Configuring IGMP Snooping for Ports

Follow these steps to configure IGMP Snooping for ports:

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet

port | range fastEthernet port-list | gigabitEthernet port | range

gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list|

port-channel port-channel-id | range port-channel port-channel-list}

Enter interface configuration mode.

Step 3 ip igmp snooping

Enable IGMP Snooping for the port. By default, it is enabled.

Step 4 ip igmp snooping immediate-leave

(Optional) Enable Fast Leave on the specified port.

Fast Leave can be enabled on a per-port basis or per-VLAN basis. When enabled on a per-port basis, the switch will remove the port from the corresponding multicast group of all VLANs before forwarding the leave message to the querier.

You should only use Fast Leave for a port when there is a single receiver connected to the port. For more details about Fast Leave, see 2.2.2 Configuring IGMP Snooping for VLANs.

Step 5 show ip igmp snooping interface [fastEthernet]

port-list] | gigabitEthernet [port-list] | ten-

gigabitEthernet [ port-list ] | port-channel [port-channel-list ] basic-config

Show the basic IGMP Snooping configuration on the specified port(s) or of all the ports.

Step 6 end

Return to privileged EXEC mode.

Step 7 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable IGMP Snooping and fast leave for port 1/0/1-3:

Switch#configure

Switch(config)#interface range gigabitEhternet 1/0/1-3

Switch(config-if-range)#ip igmp snooping

Switch(config-if-range)#ip igmp snooping immediate-leave

Switch(config-if-range)#show ip igmp snooping interface gigabitEthernet 1/0/1-3

PortIGMP-SnoopingFast-Leave
Gi1/0/1enableenable
Gi1/0/2enableenable
Gi1/0/3enableenable

Switch(config-if-range)#end

Switch#copy running-config startup-config

2.2.4 Configuring Hosts to Statically Join a Group

Hosts or Layer 2 ports normally join multicast groups dynamically, but you can also configure hosts to statically join a group.

Follow these steps to configure hosts to statically join a group:

Step 1 configure

Enter global configuration mode.

Step 2 ip igmp snooping vlan-config vlan-id-list static ip interface { fastEthernet port-list |

gigabitEthernet port-list | ten-gigabitEthernet port-list | port-channel lag-list}

vlan-id-list: Specify the ID or the ID list of the VLAN(s).

ip: Specify the IP address of the multicast group that the hosts want to join.

port-list / lag-list: Specify the ports that is connected to the hosts. These ports will become static member ports of the group.

Step 3 show ip igmp snooping groups static

Show the static MLD Snooping configuration.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to configure port 1/0/1-3 in VLAN 2 to statically join the multicast group 239.1.2.3:

Switch#configure

Switch(config)#ip igmp snooping vlan-config 2 static 239.1.2.3 interface gigabitEthernet 1/0/1-3

Switch(config)#show ip igmp snooping groups static

Multicast-ipVLAN-idAddr-typeSwitch-port
239.1.2.32staticGi1/0/1-3

Switch(config)#end

Switch#copy running-config startup-config

2.2.5 Configuring IGMP Accounting and Authentication Features

TP-LINK Omada TL-SG2008P - Configuring IGMP Accounting and Authentication Features - 1

Note:

IGMP Accounting and Authentication is only available on certain devices. To check whether your device supports this feature, refer to the actual web interface.

You can enable IGMP accounting and authentication according to your need. IGMP accounting is configured globally, and IGMP authentication can be enabled on a per-port basis.

To use these features, you need to set up a RADIUS server and configure add the RADIUS server for the switch.

Follow these steps to add the RADIUS server and enable IGMP accounting globally:

Step 1 configure

Enter global configuration mode.

Step 2 radius-server host ip-address [auth-port port-id] [acct-port port-id] [timeout time] [retransmit number] [nas-id nas-id] key { [0] string | 7 encrypted-string}

Add the RADIUS server and configure the related parameters as needed.

host ip-address: Enter the IP address of the server running the RADIUS protocol.

auth-port port-id: Specify the UDP destination port on the RADIUS server for authentication requests. The default setting is 1812.

acct-port port-id: Specify the UDP destination port on the RADIUS server for accounting requests. The default setting is 1813. Usually, it is used in the 802.1X feature.

timeout time: Specify the time interval that the switch waits for the server to reply before resending. The valid values are from 1 to 9 seconds and the default setting is 5 seconds.

retransmit number: Specify the number of times a request is resent to the server if the server does not respond. The valid values are from 1 to 3 and the default setting is 2.

nas-id nas-id: Specify the name of the NAS (Network Access Server) to be contained in RADIUS packets for identification. It ranges from 1 to 31 characters. The default value is the MAC address of the switch. Generally, the NAS indicates the switch itself.

key { [0]string|7 encrypted-string}: Specify the shared key. 0 and 7 represent the encryption type. 0 indicates that an unencrypted key will follow. 7 indicates that a symmetric encrypted key with a fixed length will follow. By default, the encryption type is 0. string is the shared key for the switch and the server, which contains 31 characters at most. encrypted-string is a symmetric encrypted key with a fixed length, which you can copy from the configuration file of another switch. The key or encrypted-key you configure here will be displayed in the encrypted form.

Step 3 ip igmp snooping accouting

Enable IGMP accounting globally.

Step 4 show ip igmp snooping

Show the basic IGMP Snooping configuration.

Step 5 end

Return to privileged EXEC mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

Follow these steps to enable IGMP authentication for ports:

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}

Enter interface configuration mode.

Step 3 ip igmp snooping authentication

Enable IGMP Snooping authentication for the port. By default, it is enabled.

Step 4 show ip igmp snooping interface [fastEthernet [ port-list] | gigabitEthernet [port-list] | ten-gigabitEthernet [port-list] | port-channel [port-channel-list] ] authentication

Show the basic IGMP Snooping configuration on the specified port(s) or of all the ports.

Step 5 end

Return to privileged EXEC mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable IGMP accounting globally:

Switch#configure

Switch(config)#ip igmp snooping accounting

Switch(config)#show ip igmp snooping

...

Global Authentication Accounting: Enable

Enable Port: Gi1/0/1-28, Po1-14

Enable VLAN:

Switch(config)#end

Switch#copy running-config startup-config

The following example shows how to enable IGMP authentication on port 1/0/1-3:

Switch#configure

Switch(config)#interface range gigabitEhternet 1/0/1-3

Switch(config-if-range)#ip igmp snooping authentication

Switch(config-if-range)#show ip igmp snooping interface gigabitEthernet 1/0/1-3 authentication

PortIGMP-Authentication
Gi1/0/1enable
Gi1/0/2enable
Gi1/0/3enable

Switch(config)#end

Switch#copy running-config startup-config

3

MLD Snooping Configuration

To complete MLD Snooping configuration, follow these steps:

1) Enable MLD Snooping globally and configure the global parameters.
2) Configure MLD Snooping for VLANs.
3) Configure MLD Snooping for ports.
4) (Optional) Configure hosts to statically join a group.

TP-LINK Omada TL-SG2008P - MLD Snooping Configuration - 1

Note:

MLD Snooping takes effect only when it is enabled globally, in the corresponding VLAN and port at the same time.

3.1 Using the GUI

3.1.1 Configuring MLD Snooping Globally

Choose the menu L2 FEATURES > Multicast > MLD Snooping > Global Config to load the following page.

Figure 3-1 Configure MLD Snooping Globally
TP-LINK Omada TL-SG2008P - Configuring MLD Snooping Globally - 1

text_image Global Config MLD Snooping: Enable Unknown Multicast Groups: Forward Discard Apply

Follow these steps to configure MLD Snooping globally:

1) In the Global Config section, enable MLD Snooping and configure the Unknown Multicast Groups feature globally.

MLD Snooping Enable or disable MLD Snooping globally.

Unknown

Multicast Groups

Configure the way in which the switch processes data that are sent to unknown multicast groups as Forward or Discard. By default, it is Forward.

Unknown multicast groups are multicast groups that do not match any of the groups announced in earlier IGMP membership reports, and thus cannot be found in the multicast forwarding table of the switch.

Note: IGMP Snooping and MLD Snooping share the setting of Unknown Multicast Groups, so you have to enable IGMP Snooping globally on the L2 FEATURES > Multicast > IGMP Snooping > Global Config page at the same time.

2) Click Apply.

3.1.2 Configuring MLD Snooping for VLANs

Before configuring MLD Snooping for VLANs, set up the VLANs that the router ports and the member ports are in. For details, please refer to Configuring 802.1Q VLAN.

The switch supports configuring MLD Snooping on a per-VLAN basis. After MLD Snooping is enabled globally, you also need to enable MLD Snooping and configure the corresponding parameters for the VLANs that the router ports and the member ports are in.

Choose the menu L2 FEATURES > Multicast > MLD Snooping > Global Config, and click in your desired VLAN entry in the MLD VLAN Config section to load the following page.

Figure 3-2 Configure MLD Snooping for VLAN
TP-LINK Omada TL-SG2008P - Configuring MLD Snooping for VLANs - 1

text_image Configure MLD Snooping for VLAN VLAN ID: 1 MLD Snooping Status: Enable Fast Leave: Enable Report Suppression: Forward Discard Member Port Aging Time: 260 seconds (60-600) Router Port Aging Time: 300 seconds (60-600) Leave Time: 1 seconds (1-30) MLD Snooping Querier: Enable Static Router Ports UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Cancel Save

Follow these steps to configure MLD Snooping for a specific VLAN:

1) Enable MLD Snooping for the VLAN, and configure the corresponding parameters.

VLAN ID Displays the VLAN ID.

MLD Snooping Status Enable or disable MLD Snooping for the VLAN.

Fast Leave Enable or disable Fast Leave for the VLAN.

Without Fast Leave, after a receiver sends an MLD done message (equivalent to an IGMP leave message) to leave a multicast group, the switch will forward the done message to the Layer 3 device (the querier).From the point of view of the querier, the port connecting to the switch is a member port of the corresponding multicast group. After receiving the done message from the switch, the querier will send out a configured number (Last Listener Query Count) of Multicast-Address-Specific Queries (MASQs) on that port with a configured interval (Last Listener Query Interval), and wait for MLD reports. If there are other receivers connecting to the switch, they will response to the MASQs before the Last Listener Query Interval expires. If no reports are received after the response time of the last query expires, the querier will remove the port from the forwarding list of the corresponding multicast group.That is, if there are other receivers connecting to the switch, the one sent done message have to wait until the port ages out from the switch's forwarding list of the corresponding multicast group (the maximum waiting time is decided by the Member Port Aging Time).With Fast Leave enabled on a VLAN, the switch will remove the (Multicast Group, Port, VLAN) entry from the multicast forwarding table before forwarding the done message to the querier. This helps to reduce bandwidth waste since the switch no longer sends the corresponding multicast streams to the VLAN of the port as soon as the port receives a done message from the VLAN.
Report SuppressionEnable or disable Report Suppression for the VLAN.When enabled, the switch will only forward the first MLD report message for each multicast group to the MLD querier and suppress subsequent MLD report messages for the same multicast group during one query interval. This feature prevents duplicate report messages from being sent to the MLD querier.
Member Port Aging TimeSpecify the aging time of the member ports in the VLAN.Once the switch receives an MLD report message from a port, the switch adds this port to the member port list of the corresponding multicast group. Member ports that are learned in this way are called dynamic member ports.If the switch does not receive any MLD report messages for a specific multicast group from a dynamic member port, it will no longer consider this port as a member port of this multicast group and delete it from the multicast forwarding table.
Router Port Aging TimeSpecify the aging time of the router ports in the VLAN.Once the switch receives an MLD general query message from a port, the switch adds this port to the router port list. Router ports that are learned in this way are called dynamic router ports.If the switch does not receive any MLD general query messages from a dynamic router port within the router port aging time, the switch will no longer consider this port as a router port and delete it from the router port list.
Leave Time Specify the leave time for the VLAN.
When the switch receives a leave message from a port to leave a multicast group, it will wait for a leave time before removing the port from the multicast group. During the period, if the switch receives any report messages from the port, the port will not be removed from the multicast group. Exceptions are as follows:If the member port ages out before the Leave Time ends and no report messages are received, the port will be removed from the multicast group once its Member Port Aging Time ends.The Leave Time mechanism will not take effect when Fast Leave takes effect.A proper leave time value can avoid other hosts connecting to the same port of the switch being mistakenly removed from the multicast group when only some of them want to leave.
MLD Snooping QuerierEnable or disable the MLD Snooping Querier for the VLAN.When enabled, the switch acts as an MLD Snooping Querier for the hosts in this VLAN. A querier periodically sends a general query on the network to solicit membership information, and sends MASQs when it receives done messages from hosts.
Query IntervalWith MLD Snooping Querier enabled, specify the interval between general query messages sent by the switch.
Maximum Response TimeWith MLD Snooping Querier enabled, specify the host's maximum response time to general query messages.
Last Listener Query IntervalWith MLD Snooping Querier enabled, when the switch receives a done message, it obtains the address of the multicast group that the host wants to leave from the message. Then the switch sends out MASQs to this multicast group through the port receiving the done message. This parameter determines the interval between MASQs.
Last Listener Query CountWith MLD Snooping Querier enabled, specify the number of MASQs to be sent. If specified count of MASQs are sent and no report message is received, the switch will delete the multicast address from the multicast forwarding table.
General Query Source IPWith MLD Snooping Querier enabled, specify the source IPv6 address of the general query messages sent by the switch. It should be a unicast address.
Static Router PortsSelect one or more ports to be the static router ports in the VLAN. Static router ports do not age.Multicast streams and MLD packets to all groups in this VLAN will be forwarded through the static router ports. Multicast streams and MLD packets to the groups that have dynamic router ports will be also forwarded through the corresponding dynamic router ports.
Forbidden Router PortsSelect the ports to forbid them from being router ports in the VLAN.

2) Click Save.

3.1.3 Configuring MLD Snooping for Ports

Choose the menu L2 FEATURES > Multicast > MLD Snooping > Port Config to load the following page.

Figure 3-3 Configure MLD Snooping for Ports
TP-LINK Omada TL-SG2008P - Configuring MLD Snooping for Ports - 1

text_image Port Config UNIT1 LAGS Port MLD Snooping Fast Leave LAG ✓ 1/0/1 Enabled Disabled --- □ 1/0/2 Enabled Disabled --- □ 1/0/3 Enabled Disabled --- □ 1/0/4 Enabled Disabled --- □ 1/0/5 Enabled Disabled --- □ 1/0/6 Enabled Disabled --- □ 1/0/7 Enabled Disabled --- □ 1/0/8 Enabled Disabled --- □ 1/0/9 Enabled Disabled --- □ 1/0/10 Enabled Disabled --- Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure MLD Snooping for ports:

1) Enable MLD Snooping for the port and enable Fast Leave if there is only one receiver connected to the port.

MLD Snooping Enable or disable MLD Snooping for the port.

Fast Leave Enable or disable Fast Leave for the port.

Fast Leave can be enabled on a per-port basis or per-VLAN basis. When enabled on a per-port basis, the switch will remove the port from the corresponding multicast group of all VLANs before forwarding the done message to the querier.

You should only use Fast Leave for a port when there is a single receiver connected to the port. For more details about Fast Leave, see 3.1.2 Configuring MLD Snooping for VLANs.

LAG Displays the LAG the port belongs to.

2) Click Apply.

3.1.4 Configuring Hosts to Statically Join a Group

Hosts or Layer 2 ports normally join multicast groups dynamically, but you can also configure hosts to statically join a group.

Choose the menu L2 FEATURES > Multicast > MLD Snooping > Static Group Config and click + Add to load the following page.

Figure 3-4 Configure Hosts to Statically Join a Group
TP-LINK Omada TL-SG2008P - Configuring Hosts to Statically Join a Group - 1

text_image Create Static Multicast Group Multicast IP: (Format: FF80::1234:01) VLAN ID: (1-4094) Member Ports: UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

Follow these steps to configure hosts to statically join a group:

1) Specify the multicast IP address, VLAN ID. Select the ports to be the static member ports of the multicast group.

Multicast IP Specify the IPv6 address of the multicast group that the hosts need to join.
VLAN ID Specify the VLAN that the hosts are in.
Member PortsSelect the ports that the hosts are connected to. These ports will become the static member ports of the multicast group and will never age.

2) Click Create.

3.2 Using the CLI

3.2.1 Configuring MLD Snooping Globally

Follow these steps to configure MLD Snooping globally:

Step 1 configure

Enter global configuration mode.

Step 2 ipv6 mld snooping

Enable MLD Snooping Globally.

Step 3 ipv6 mld snooping drop-unknown

(Optional) Configure the way how the switch processes multicast streams that are sent to unknown multicast groups as Discard. By default, it is Forward.

Unknown multicast groups are multicast groups that do not match any of the groups announced in earlier IGMP membership reports, and thus cannot be found in the multicast forwarding table of the switch.

Note: IGMP Snooping and MLD Snooping share the setting of Unknown Multicast Groups, you need to ensure IGMP Snooping is enabled globally. To enable IGMP Snooping globally, use the ip igmp snooping command in global configuration mode.

Step 4 show ipv6 mld snooping

Show the basic IGMP Snooping configuration.

Step 5 end

Return to privileged EXEC mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable MLD Snooping globally, and the way how the switch processes multicast streams that are sent to unknown multicast groups as discard.

Switch#configure

Switch(config)#ipv6 mld snooping

Switch(config)#ipv6 mld snooping

Switch(config)#ipv6 mld snooping drop-unknown

Switch(config)#show ipv6 mld snooping

MLD

Snooping

:Enable

Unknown

Multicast

:Discard

...

Switch(config)#end

Switch#copy running-config startup-config

3.2.2 Configuring MLD Snooping for VLANs

Before configuring MLD Snooping for VLANs, set up the VLANs that the router ports and the member ports are in. For details, please refer to Configuring 802.1Q VLAN.

The switch supports configuring MLD Snooping on a per-VLAN basis. After MLD Snooping is enabled globally, you also need to enable MLD Snooping and configure the corresponding parameters for the VLANs that the router ports and the member ports are in.

Follow these steps to configure MLD Snooping for VLANs:

Step 1 configure

Enter global configuration mode.

Step 2 ipv6 mld snooping vlan-config

vlan-id-list mtime member-time

Enable MLD Snooping for the specified VLANs, and specify the member port aging time for the VLANs.

vlan-id-list: Specify the ID or the ID list of the VLAN(s).

member-time: Specify the aging time of the member ports in the specified VLANs. Valid values are from 60 to 600 seconds. By default, it is 260 seconds.

Once the switch receives an MLD report message from a port, the switch adds this port to the member port list of the corresponding multicast group. Member ports that are learned in this way are called dynamic member ports.

If the switch does not receive any MLD report message for a specific multicast group from a dynamic member port, it will no longer consider this port as a member port of this multicast group and delete it from the multicast forwarding table.

Step 3 ipv6 mld snooping vlan-config

vlan-id-list rtime router-time

Specify the router port aging time for the VLANs.

vlan-id-list: Specify the ID or the ID list of the VLAN(s).

router-time: Specify the aging time of the router ports in the specified VLANs. Valid values are from 60 to 600 seconds. By default, it is 300 seconds.

Once the switch receives an MLD general query message from a port, the switch adds this port to the router port list. Router ports that are learned in this way are called dynamic router ports.

If the switch does not receive any MLD general query message from a dynamic router port within the router port aging time, the switch will no longer consider this port as a router port and delete it from the router port list.

Step 4 ipv6 mld snooping vlan-config

vlan-id-list ltimeleave-time

Specify the router port aging time for the VLANs.

vlan-id-list: Specify the ID or the ID list of the VLAN(s).

leave-time: Specify the leave time for the VLAN(s). Valid values are from 1 to 30 in seconds, and the default value is 1 second.

When the switch receives a leave message from a port to leave a multicast group, it will wait for a leave time before removing the port from the multicast group. During the period, if the switch receives any report messages from the port, the port will not be removed from the multicast group. Exceptions are as follows:

  • If the member port ages out before the Leave Time ends and no report messages are received, the port will be removed from the multicast group once its Member Port Aging Time ends.
    • The Leave Time mechanism will not take effect when Fast Leave takes effect.

A proper leave time value can avoid other hosts connecting to the same port of the switch being mistakenly removed from the multicast group when only some of them want to leave.

Step 5 ipv6 mld snooping vlan-config vlan-id-list report-suppression

(Optional) Enable Report Suppression for the VLANs. By default, it is disabled.

When enabled, the switch will only forward the first MLD report message for each multicast group to the MLD querier and suppress subsequent MLD report messages for the same multicast group during one query interval. This feature prevents duplicate report messages from being sent to the MLD querier.

vlan-id-list: Specify the ID or the ID list of the VLAN(s).

Step 6 ipv6 mld snooping vlan-config vlan-id-list immediate-leave

(Optional) Enable Fast Leave for the VLANs. By default, it is disabled.

Without Fast Leave, after a receiver sends an MLD done message (equivalent to an IGMP leave message) to leave a multicast group, the switch will forward the done message to the Layer 3 device (the querier).

From the point of view of the querier, the port connecting to the switch is a member port of the corresponding multicast group. After receiving the done message from the switch, the querier will send out a configured number (Last Listener Query Count) of Multicast-Address-Specific Queries (MASQs) on that port with a configured interval (Last Listener Query Interval), and wait for MLD reports. If there are other receivers connecting to the switch, they will response to the MASQs before the Last Listener Query Interval expires. If no reports are received after the response time of the last query expires, the querier will remove the port from the forwarding list of the corresponding multicast group.

That is, if there are other receivers connecting to the switch, the one sent done message have to wait until the port ages out from the switch's forwarding list of the corresponding multicast group (the maximum waiting time is decided by the Member Port Aging Time).

With Fast Leave enabled on a VLAN, the switch will remove the (Multicast Group, Port, VLAN) entry from the multicast forwarding table before forwarding the done message to the querier. This helps to reduce bandwidth waste since the switch no longer sends the corresponding multicast streams to the VLAN of the port as soon as the port receives a done message from the VLAN.

vlan-id-list: Specify the ID or the ID list of the VLAN(s).

Step 7 ipv6 mld snooping vlan-config vlan-id-list rport interface { fastEthernet port-list | gigabitEthernet port-list | ten-gigabitEthernet port-list | port-channel lag-list }

(Optional) Specify the static router ports for the VLANs. Static router ports do not age.

vlan-id-list: Specify the ID or the ID list of the VLAN(s).

port-list: The number or the list of the Ethernet port that need to be configured as static router ports.

lag-list: The ID or the list of the LAG that need to be configured as static router ports.

Step 8 ipv6 mld snooping vlan-config vlan-id-list router-ports-forbidden interface { fastEthernet port-list | gigabitEthernet port-list | ten-gigabitEthernet port-list | port-channel lag-list }

(Optional) Specify the ports to forbid them from being router ports in the VLANs.

vlan-id-list: Specify the ID or the ID list of the VLAN(s).

port-list: The number or the list of the Ethernet port that need to be forbidden from being router ports.

lag-list: The ID or the list of the LAG that need to be forbidden from being router ports.

Step 9 ipv6 mld snooping vlan-config

vlan-id-list querier

(Optional) Enable MLD Snooping Querier for the VLAN. By default, it is disabled.

When enabled, the switch acts as an MLD Snooping Querier for the hosts in this VLAN. A querier periodically sends a general query on the network to solicit membership information, and sends group-specific queries when it receives done messages from hosts.

vlan-id-list: Specify the ID or the ID list of the VLAN(s).

After enabling MLD Snooping Querier feature, you need to specify the corresponding parameters including the Last Member Query Count, Last Member Query Interval, Maximum Response Time, Query Interval and General Query Source IP. Use the command below in global configuration mode to configure the parameters:

ipv6 mld snooping vlan-config vlan-id-list querier { max-response-time response-time | query-interval interval | general-query source-ip ip-addr | last-listener-query-count num | last-listener-query-interval interval }

vlan-id-list: Specify the ID or the ID list of the VLAN(s).

response-time: Specify the host's maximum response time to general query messages.

query-interval interval: Specify the interval between general query messages sent by the switch.

ip-addr: Specify the source IP address of the general query messages sent by the switch. It should be a unicast address.

num: Specify the number of group-specific queries to be sent. With MLD Snooping Querier enabled, when the switch receives a done message, it obtains the address of the multicast group that the host wants to leave from the message. Then the switch sends out MASQs to this multicast group through the port receiving the done message. If specified count of MASQs are sent and no report message is received, the switch will delete the multicast address from the multicast forwarding table.

last-listener-query-interval interval: Specify the interval between MASQs.

Step 10 show ipv6 mld snooping vlan

vlan-id

Show the basic MLD snooping configuration in the specified VLAN.

Step 11 end

Return to privileged EXEC mode.

Step 12 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable MLD Snooping for VLAN 1, and configure the member port aging time as 300 seconds, the router port aging time as 320 seconds, and then enable Fast Leave and Report Suppression for the VLAN:

Switch#configure

Switch(config)#ipv6 mld snooping vlan-config 1 mtime 300

Switch(config)#ipv6 mld snooping vlan-config 1 rtime 320

Switch(config)#ipv6 mld snooping vlan-config 1 immediate-leave

Switch(config)#ipv6 mld snooping vlan-config 1 report-suppression

Switch(config)#show ipv6 mld snooping vlan 1

Vlan Id: 1

Vlan MLD Snooping Status: Enable

Fast Leave: Enable

Report Suppression: Enable

Router Time: Enable

Member Time: Enable

Querier: Disable

...

Switch(config)#end

Switch#copy running-config startup-config

The following example shows how to enable MLD Snooping querier for VLAN 1, and configure the query interval as 100 seconds, the maximum response time as 15 seconds, the last listener query interval as 2 seconds, the last listener query count as 3, and the general query source IP as 2000::1:2345:6789:ABCD:

Switch#configure

Switch(config)#ipv6 mld snooping vlan-config 1 querier

Switch(config)#ipv6 mld snooping vlan-config 1 querier query-interval 100

Switch(config)#ipv6 mld snooping vlan-config 1 querier max-response-time 15

Switch(config)#ipv6 mld snooping vlan-config 1 querier last-listener-query-interval 2

Switch(config)#ipv6 mld snooping vlan-config 1 querier last-listener-query-count 3

Switch(config)#ipv6 mld snooping vlan-config 1 querier general-query source-ip 2000::1:2345:6789:ABCD

Switch(config)#show ipv6 mld snooping vlan 1

Vlan Id: 1

...

Querier:

Enable

Maximum Response Time: 15

Query Interval: 100

Last Member Query Interval: 2

Last Member Query Count: 3

General Query Source IP: 2000::1:2345:6789:abcd

...

Switch(config)#end

Switch#copy running-config startup-config

3.2.3 Configuring MLD Snooping for Ports

Follow these steps to configure MLD Snooping for ports:

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}

Enter interface configuration mode.

Step 3 ipv6 mld snooping

Enable MLD Snooping for the port. By default, it is enabled.

Step 4 ipv6 mld snooping immediate-leave

(Optional) Enable Fast Leave on the specified port.

Fast Leave can be enabled on a per-port basis or per-VLAN basis. When enabled on a per-port basis, the switch will remove the port from the corresponding multicast group of all VLANs before forwarding the done message to the querier.

You should only use Fast Leave for a port when there is a single receiver connected to the port. For more details about Fast Leave, see 3.2.2 Configuring MLD Snooping for VLANs.

Step 5 show ipv6 mld snooping interface [fastEthernet [ port-list] | gigabitEthernet [ port-list] | ten-gigabitEthernet [ port-list] | port-channel [port-channel-list]] basic-config

Show the basic MLD Snooping configuration on the specified port(s) or of all the ports.

Step 6 end

Return to privileged EXEC mode.

Step 7 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable MLD Snooping and fast leave for port 1/0/1-3:

Switch#configure

Switch(config)#interface range gigabitEhternet 1/0/1-3

Switch(config-if-range)#ipv6 mld snooping

Switch(config-if-range)#ipv6 mld snooping immediate-leave

Switch(config-if-range)#show ipv6 mld snooping interface gigabitEthernet 1/0/1-3

PortMLD-SnoopingFast-Leave
Gi1/0/1enableenable
Gi1/0/2enableenable
Gi1/0/3enableenable

Switch(config-if-range)#end

Switch#copy running-config startup-config

3.2.4 Configuring Hosts to Statically Join a Group

Hosts or Layer 2 ports normally join multicast groups dynamically, but you can also configure hosts to statically join a group.

Follow these steps to configure hosts to statically join a group:

Step 1 configure

Enter global configuration mode.

Step 2 ipv6 mld snooping vlan-config vlan-id-list static ip interface {fastEthernet port-list | gigabitEthernet port-list | ten-gigabitEthernet port-list | port-channel lag-list}

vlan-id-list: Specify the ID or the ID list of the VLAN(s).

ip: Specify the IP address of the multicast group that the hosts want to join.

port-list / lag-list: Specify the ports that is connected to the hosts. These ports will become static member ports of the group.

Step 3 show ipv6 mld snooping groups static

Show the static MLD Snooping configuration.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to configure port 1/0/1-3 in VLAN 2 to statically join the multicast group ff80::1234:1:

Switch#configure

Switch(config)#ipv6 mld snooping vlan-config 2 static ff80::1234:1 interface gigabitEthernet 1/0/1-3

Switch(config)#show ipv6 mld snooping groups static

Multicast-ipVLAN-idAddr-typeSwitch-port
----------------
ff80::1234:12staticGi1/0/1-3

Switch(config)#end

Switch#copy running-config startup-config

4 MVR Configuration

To complete MVR configuration, follow these steps:

1) Configure 802.1Q VLANs.
2) Configure MVR globally.
3) Add multicast groups to MVR.
4) Configure MVR for the ports.
5) (Optional) Statically add ports to MVR groups.

Configuration Guidelines

■ MVR does not support IGMPv3 messages.
■ Do not configure MVR on private VLAN ports, otherwise MVR cannot take effect.
■ MVR operates on the underlying mechanism of IGMP Snooping, but the two features operate independently of each other. Both protocols can be enabled on a port at the same time. When both are enabled, MVR listens to the report and leave messages only for the multicast groups configured in MVR. All other multicast groups are managed by IGMP Snooping.

4.1 Using the GUI

4.1.1 Configuring 802.1Q VLANs

Before configuring MVR, create an 802.1Q VLAN as the multicast VLAN. Add all source ports (uplink ports that receive multicast data from the router) to the multicast VLAN as tagged ports. Configure 802.1Q VLANs for the receiver ports (ports that are connecting to the hosts) according to network requirements. Note that receiver ports can only belong to one VLAN and cannot be added to the multicast VLAN. For details, refer to Configuring 802.1Q VLAN.

4.1.2 Configuring MVR Globally

Choose the menu L2 FEATURES > Multicast > MVR > MVR Config to load the following page.

Figure 4-1 Configure MVR Globally
TP-LINK Omada TL-SG2008P - Configuring MVR Globally - 1

text_image MVR Config MVR: Enable MVR Mode: Compatible Dynamic Multicast VLAN ID: 1 (1-4094) Query Response Time: 5 tenths of a second (1-100) Maximum Multicast Groups: 511 Current Multicast Groups: 0 Apply

Follow these steps to configure MVR globally:

1) Enable MVR globally and configure the global parameters.

MVR Enable or disable MVR globally.

MVR Mode Specify the MVR mode as compatible or dynamic.

Compatible: In this mode, the switch does not forward report or leave messages from the hosts to the IGMP querier. This means IGMP querier cannot learn the multicast groups' membership information from the switch. The IGMP querier must be statically configured to transmit all the required multicast streams to the switch via the multicast VLAN.

Dynamic: In this mode, after receiving report or leave messages from the hosts, the switch will forward them to the IGMP querier via the multicast VLAN (with appropriate translation of the VLAN ID). The IGMP querier can learn the multicast groups' membership information through the report and leave messages, and transmit the multicast streams to the switch via the multicast VLAN according to the multicast forwarding table.

Multicast VLAN ID Specify an existing 802.1Q VLAN as the multicast VLAN.

Query Response TimeSpecify the maximum time to wait for IGMP report on a receiver port before removing the port from multicast group membership.
Maximum Multicast GroupsDisplays the maximum number of multicast groups that can be configured on the switch.
Current Multicast GroupsDisplays the current number of multicast groups that have been configured on the switch.

2) Click Apply.

4.1.3 Adding Multicast Groups to MVR

You need to manually add multicast groups to the MVR. Choose the menu L2 FEATURES > Multicast > MVR > MVR Group Config and click + Add to load the following page.

Figure 4-2 Add Multicast Groups to MVR
TP-LINK Omada TL-SG2008P - Adding Multicast Groups to MVR - 1

text_image MVR Group IP MVR Group IP: (Format: 235.0.0.1) MVR Group Count: (1-256) Cancel Create

Follow these steps to add multicast groups to MVR:

1) Specify the IP address of the multicast groups.

MVR Group IP / MVR Group Count

Specify the start IP address and the number of contiguous series of multicast groups.

Multicast data sent to the address specified here will be sent to all source ports on the switch and all receiver ports that have requested to receive data from that multicast address.

2) Click Create.

Then the added multicast groups will appear in the MVR group table, as the following figure shows:

Figure 4-3 MVR Group Table

MVR Group Table
+ Add - Delete
IndexMVR Group IPStatusMembersOperation
1239.1.2.3Inactive
2239.1.2.4Inactive
Total: 2

MVR Group IP Displays the IP address of multicast group.

Status Displays the status of the MVR group. In compatible mode, all the MVR groups are added manually, so the status is always active. In dynamic mode, there are two status:

Inactive: The MVR group is added successfully, but the source port has not received any query messages from this multicast group.

Active: The MVR group is added successfully and the source port has received query messages from this multicast group.

Member Displays the member ports in this MVR group.

4.1.4 Configuring MVR for the Port

Choose the menu L2 FEATURES > Multicast > MVR > Port Config to load the following page.

Figure 4-4 Configure MVR for the Port
TP-LINK Omada TL-SG2008P - Configuring MVR for the Port - 1

text_image Port Config UNIT1 Port Mode Type Status Fast Leave ✓ 1/0/1 Disable None INACTIVE/InVLAN Disable □ 1/0/2 Disable None ACTIVE/InVLAN Disable □ 1/0/3 Disable None INACTIVE/InVLAN Disable □ 1/0/4 Disable None INACTIVE/InVLAN Disable □ 1/0/5 Disable None INACTIVE/InVLAN Disable □ 1/0/6 Disable None INACTIVE/InVLAN Disable □ 1/0/7 Disable None INACTIVE/InVLAN Disable □ 1/0/8 Disable None INACTIVE/InVLAN Disable □ 1/0/9 Disable None INACTIVE/InVLAN Disable □ 1/0/10 Disable None INACTIVE/InVLAN Disable Total: 28 1 entry selected. Cancel Apply

Follow these steps to add multicast groups to MVR:

1) Select one or more ports to configure.
2) Enable MVR, and configure the port type and Fast Leave feature for the port.

Mode Enable or disable MVR for the selected ports.

Type Configure the port type.

None: The port is a non-MVR port. If you attempt to configure a non-MVR port with MVR characteristics, the operation will be unsuccessful.

Source: Configure the uplink ports that receive and send multicast data on the multicast VLAN as source ports. Source ports should belong to the multicast VLAN. In compatible mode, source ports will be automatically added to all multicast groups, while in dynamic mode, you need to manually add them to the corresponding multicast groups.

Receiver: Configure the ports that are connecting to the hosts as receiver ports. A receiver port can only belong to one VLAN, and cannot belong to the multicast VLAN. In both modes, the switch will add or remove the receiver ports to the corresponding multicast groups by snooping the report and leave messages from the hosts.

Status Displays the port's status.

Active/InVLAN: The port is physically up and in one or more VLANs.

Active/NotInVLAN: The port is physically up and not in any VLAN.

Inactive/InVLAN: The port is physically down and in one or more VLANs.

Inactive/NotInVLAN: The port is physically down and not in any VLAN.

Fast Leave

Enable or disable Fast Leave for the selected ports. Only receiver ports support Fast Leave. Before enabling Fast Leave for a port, make sure there is only a single receiver device connecting to the port.

3) Click Apply.

4.1.5 (Optional) Adding Ports to MVR Groups Statically

You can add only receiver ports to MVR groups statically. The switch adds or removes receiver ports to the corresponding multicast groups by snooping the report and leave messages from the hosts. You can also statically add a receiver port to an MVR group.

Choose the menu L2 FEATURES > Multicast > MVR > Static Group Members, and click in your desired MVR group entry to load the following page.

Figure 4-5 Configure Hosts to Statically Join an MVR group
TP-LINK Omada TL-SG2008P - (Optional) Adding Ports to MVR Groups Statically - 1

text_image Static Group Member MVR Group IP: 239.1.2.4 Static Member Ports: UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Save

Follow these steps to statically add ports to an MVR group:

1) Select the ports to add them to the MVR group.
2) Click Save.

4.2 Using the CLI

4.2.1 Configuring 802.1Q VLANs

Before configuring MVR, create an 802.1Q VLAN as the multicast VLAN. Add the all source ports to the multicast VLAN as tagged ports. Configure 802.1Q VLANs for the receiver ports according to network requirements. Note that receiver ports can only belong to one VLAN and cannot be added to the multicast VLAN. For details, refer to Configuring 802.1Q VLAN.

4.2.2 Configuring MVR Globally

Follow these steps to configure MVR globally:

Step 1 configure

Enter global configuration mode.

Step 2 mvr

Enable MVR Globally.

Step 3 mvr mode { compatible | dynamic }

Configure the MVR mode as compatible or dynamic.

compatible: In this mode, the switch does not forward report or leave messages from the hosts to the IGMP querier. So the IGMP querier cannot learn the multicast groups membership information from the switch. You have to statically configure the IGMP querier to transmit all the required multicast streams to the switch via the multicast VLAN.

dynamic: In this mode, after receiving report or leave messages from the hosts, the switch will forward them to the IGMP querier via the multicast VLAN (with appropriate translation of the VLAN ID). So the IGMP querier can learn the multicast groups membership information through the report and leave messages, and transmit the multicast streams to the switch via the multicast VLAN according to the multicast forwarding table.

Step 4 mvr vlan

vlan-id

Specify the multicast VLAN.

vlan-id: Specify the ID of the multicast VLAN. Valid values are from 1 to 4094.

Step 5 mvr querytime

time

Specify the maximum time to wait for IGMP report on a receiver port before removing the port from multicast group membership.

time: Specify the maximum response time. Valid values are from 1 to 100 tenths of a second, and the default value is 5 tenths of a second.

Step 6 mvr group ip-addr count

Add multicast groups to the MVR.

ip-addr: Specify the start IP address of the contiguous series of multicast groups.

count: Specify the number of the multicast groups to be added to the MVR. The range is 1 to 511.

Step 7 show mvr

Show the global MVR configuration.

show mvr members

Show the existing MVR groups.

Step 8 end

Return to privileged EXEC mode.

Step 9 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable MVR globally, and configure the MVR mode as compatible, the multicast VLAN as VLAN 2 and the query response time as 5 tenths of a second. Then add 239.1.2.3-239.1.2.5 to MVR group.

Switch#configure

Switch(config)#mvr mode compatible

Switch(config)#mvr vlan 2

Switch(config)#mvr querytime 5

Switch(config)#mvr group 239.1.2.3 3

Switch(config)#show mvr

MVR :Enable

MVR Multicast Vlan :2

MVR Max Multicast Groups :511

MVR Current Multicast Groups :3

MVR Global Query Response Time :5 (tenths of sec)

MVR Mode Type :Compatible

Switch(config)#show mvr members

MVR Group IP status Members

239.1.2.3active
239.1.2.4active
239.1.2.5active

Switch(config)#end

Switch#copy running-config startup-config

4.2.3 Configuring MVR for the Ports

Follow these steps to configure MVR for the ports:

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list}

Enter interface configuration mode.

Step 3 mvr

Enable MVR for the port.

Step 4 mvr type { source | receiver }

Configure the MVR port type as receiver or source. By default, the port is a non-MVR port. If you attempt to configure a non-MVR port with MVR characteristics, the operation fails.

source: Configure the uplink ports that receive and send multicast data on the multicast VLAN as source ports. Source ports should belong to the multicast VLAN.

receiver: Configure the ports that are connecting to the hosts as receiver ports. A receiver port can only belong to one VLAN, and cannot belong to the multicast VLAN.

Step 5 mvr immediate

(Optional) Enable the Fast Leave feature of MVR for the port. Only receiver ports support Fast Leave. Before enabling Fast Leave for a port, make sure there is only a single receiver device connecting to the port.

Step 6 mvr vlan vlan-id group ip-addr

(Optional) Statically add the port to an MVR group. Then the port can receive multicast traffic sent to the IP multicast address via the multicast VLAN.

This command applies to only receiver ports. The switch adds or removes the receiver ports to the corresponding multicast groups by snooping the report and leave messages from the hosts. You can also statically add a receiver port to an MVR group.

vlan-id: Enter the multicast VLAN ID.

ip-addr: Specify the IP address of the multicast group.

Step 7 show mvr interface {fastEthernet [port-list] | gigabitEthernet [port-list] | ten-gigabitEthernet [port-list]}

Show the MVR configuration of the specified interface(s).

show mvr members

Show the membership information of all MVR groups.

Step 8 end

Return to privileged EXEC mode.

Step 9 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to configure port 1/0/7 as source port, and port 1/0/1-3 as receiver ports. Then statically add port 1/0/1-3 to group 239.1.2.3 and enable MVR Fast Leave for these ports. The multicast VLAN is VLAN 2.

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/7

Switch(config-if)#mvr

Switch(config-if)#mvr type source

Switch(config-if)#exit

Switch(config)#interface range gigabitEthernet 1/0/1-3

Switch(config-if-range)#mvr

Switch(config-if-range)#mvr type receiver

Switch(config-if-range)#mvr immediate

Switch(config-if-range)#mvr vlan 2 group 239.1.2.3

Switch(config-if-range)#show mvr interface gigabitEthernet 1/0/1-3,1/0/7

PortModeTypeStatusImmediate
----------------------------------------

Gi1/0/1 Enable Receiver INACTIVE/InVLAN Enable

Gi1/0/2 Enable Receiver INACTIVE/InVLAN Enable

Gi1/0/3 Enable Receiver INACTIVE/InVLAN Enable

Gi1/0/7 Enable Source INACTIVE/InVLAN Disable

Switch(config-if-range)#show mvr members

MVR Group IP status Members

239.1.2.3

active

Gi1/0/1-3,

1/0/7

Switch(config)#end

Switch#copy running-config startup-config

5 Multicast Filtering Configuration

To complete multicast filtering configuration, follow these steps:

1) Create the IGMP profile or MLD profile.
2) Configure multicast groups a port can join and the overflow action.

5.1 Using the GUI

5.1.1 Creating the Multicast Profile

You can create multicast profiles for both IPv4 and IPv6 network. With multicast profile, the switch can define a blacklist or whitelist of multicast groups so as to filter multicast sources.

The process for creating multicast profiles for IPv4 and IPv6 are similar. The following introductions take creating an IPv4 profile as an example.

Choose the menu L2 FEATURES > Multicast > Multicast Filtering > IPv4 Profile, and click

+ Add to load the following page.

TP-LINK Omada TL-SG2008P - Creating the Multicast Profile - 1

Note:

To create a multicast profile for IPv6, choose the menu L2 FEATURES > Multicast > Multicast Filtering > IPv6 Profile.

Figure 5-1 Create IPv4 Profile
TP-LINK Omada TL-SG2008P - Creating the Multicast Profile - 2

text_image Back General Config Profile ID: (1-999) Mode: Permit Deny IP-Range Index Start IP Address End IP Address Operation No entries in this table. Total: 0 Bind Ports UNIT1 LAGS 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Discard Save

Follow these steps to create a profile.

1) In the General Config section, specify the Profile ID and Mode.

Profile ID Enter a profile ID between 1 and 999.
ModeSelect Permit or Deny as the filtering mode.
Permit: Acts as a whitelist and only allows specific member ports to join specified multicast groups.
Deny: Acts as a blacklist and prevents specific member ports from joining specific multicast groups.

2) In the IP-Range section, click + Add to load the following page. Configure the start IP address and end IP address of the multicast groups to be filtered, and click Create.

Figure 5-2 Configure Multicast Groups to Be Filtered
TP-LINK Omada TL-SG2008P - Creating the Multicast Profile - 3

text_image IP-Range Start IP Address: (Format: 235.0.0.1) End IP Address: (Format: 235.0.0.1) Cancel Create

3) In the Bind Ports section, select your desired ports to be bound with the profile.
4) Click Save.

5.1.2 Configure Multicast Filtering for Ports

You can modify the mapping relation between ports and profiles in batches, and configure the number of multicast groups a port can join and the overflow action.

The process for configuring multicast filtering for ports in IPv4 and IPv6 are similar. The following introductions take configuring multicast filtering for ports in IPv4 as an example.

Choose the menu L2 FEATURES > Multicast > Multicast Filtering > IPv4 Port Binding to load the following page.

TP-LINK Omada TL-SG2008P - Configure Multicast Filtering for Ports - 1

Note:

For IPv6, choose the menu L2 FEATURES > Multicast > Multicast Filtering > IPv6 Port Binding.

Figure 5-3 Configure Multicast Filtering for Ports
TP-LINK Omada TL-SG2008P - Configure Multicast Filtering for Ports - 2

text_image Binding Table UNIT1 LAGS Port Profile ID Maximum Groups Overflow Action LAG Operation ✓ 1/0/1 1000 Drop --- Clear Profile □ 1/0/2 1000 Drop --- Clear Profile □ 1/0/3 1000 Drop --- Clear Profile □ 1/0/4 1000 Drop --- Clear Profile □ 1/0/5 1000 Drop --- Clear Profile □ 1/0/6 1000 Drop --- Clear Profile □ 1/0/7 1000 Drop --- Clear Profile □ 1/0/8 1000 Drop --- Clear Profile □ 1/0/9 1000 Drop --- Clear Profile □ 1/0/10 1000 Drop --- Clear Profile Total: 28 1 entry selected. Cancel Apply

Follow these steps to bind the profile to ports and configure the corresponding parameters for the ports:

1) Select one or more ports to configure.
2) Specify the profile to be bound, and configure the maximum groups the port can join and the overflow action.

Profile IDSpecify the ID of an existing profile to bind the profile to the selected ports. One port can only be bound to one profile.
Maximum GroupsEnter the number of multicast groups the port can join. Valid values are from 0 to 1000.
Overflow ActionSelect the action the switch will take with the new multicast member groups when the number of multicast groups the port has joined exceeds the maximum.Drop: Drop all subsequent membership report messages to prevent the port joining a new multicast groups.Replace: Replace the existing multicast group that has the lowest multicast MAC address with the new multicast group.
LAG Displays the LAG the port belongs to.
OperationClick Clear Profile to clear the binding between the profile and the port.

3) Click Apply.

5.2 Using the CLI

5.2.1 Creating the Multicast Profile

You can create multicast profiles for both IPv4 and IPv6 network. With multicast profile, the switch can define a blacklist or whitelist of multicast groups so as to filter multicast sources.

Creating IGMP Profile (Multicast Profile for IPv4)

Step 1 configureEnter global configuration mode.
Step 2 ip igmp profile idCreate a new profile and enter profile configuration mode.

Step 3 Permit

Configure the profile's filtering mode as permit. Then the profile acts as a whitelist and only allows specific member ports to join specified multicast groups.

deny

Configure the profile's filtering mode as deny. Then the profile acts as a blacklist and prevents specific member ports from joining specific multicast groups.

Step 4 range start-ip end-ip

Configure the range of multicast IP addresses to be filtered.

start-ip / end-ip: Specify the start IP address and end IP address of the IP range.

Step 5 show ip igmp profile [ id]

Show the detailed IGMP profile configuration.

Step 6 end

Return to privileged EXEC mode.

Step 7 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to configure Profile 1 so that the switch filters multicast streams sent to 226.0.0.5-226.0.0.10:

Switch#configure

Switch(config)#ip igmp snooping

Switch(config)#ip igmp profile 1

Switch(config-igmp-profile)#deny

Switch(config-igmp-profile)#range 226.0.0.5 226.0.0.10

Switch(config-igmp-profile)#show ip igmp profile

IGMP Profile 1

deny

range 226.0.0.5 226.0.0.10

Switch(config)#end

Switch#copy running-config startup-config

Creating MLD Profile (Multicast Profile for IPv6)

Step 1 configure

Enter global configuration mode.

Step 2 ipv6 mld profile id

Create a new profile and enter profile configuration mode.

Step 3 Permit

Configure the profile's filtering mode as permit. It is similar to a whitelist, indicating that the switch only allows specific member ports to join specific multicast groups.

deny

Configure the profile's filtering mode as deny. It is similar to a blacklist, indicating that the switch disallow specific member ports to join specific multicast groups.

Step 4 range start-ip end-ip

Configure the range of multicast IP addresses to be filtered.

start-ip / end-ip: Specify the start IP address and end IP address of the IP range.

Step 5 show ipv6 mld profile [ id]

Show the detailed MLD profile configuration.

Step 6 end

Return to privileged EXEC mode.

Step 7 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to configure Profile 1 so that the switch filters multicast streams sent to ff01::1234:5-ff01::1234:8:

Switch#configure

Switch(config)#ipv6 mld snooping

Switch(config)#ipv6 mld profile 1

Switch(config-mld-profile)#deny

Switch(config-mld-profile)#range ff01::1234:5 ff01::1234:8

Switch(config-mld-profile)#show ipv6 mld profile

MLD Profile 1

deny

range ff01::1234:5 ff01::1234:8

Switch(config)#end

Switch#copy running-config startup-config

5.2.2 Binding the Profile to Ports

You can bind the created IGMP profile or MLD profile to ports, and configure the number of multicast groups a port can join and the overflow action.

Binding the IGMP Profile to Ports

Step 1 configureEnter global configuration mode.
Step 2 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}Enter interface configuration mode.
Step 3 ip igmp filter profile-idBind the IGMP profile to the specified ports.profile-id: Specify the ID of the profile to be bound. It should be an existing profile.
Step 4 ip igmp snooping max-groups maxgroupConfigure the maximum number of multicast groups the port can join.maxgroup: Specify the maximum number of multicast groups the port can join. The range is 0 to 1000.
Step 5 ip igmp snooping max-groups action {drop | replace}Specify the action towards the new multicast group when the number of multicast groups the port joined exceeds the limit.drop: Drop all subsequent membership report messages, and the port join no more new multicast groups.replace: Replace the existing multicast group owning the lowest multicast MAC address with the new multicast group.
Step 6 show ip igmp profile [ id]Show the detailed IGMP profile configurations.show ip igmp snooping interface [fastEthernet [port-list ] | gigabitEthernet [port-list ] | ten-gigabitEthernet [port-list ] | port-channel [port-channel-list ] ] max-groupsShow the multicast group limitation on the specified port(s) or of all the ports.
Step 7 endReturn to privileged EXEC mode.
Step 8 copy running-config startup-configSave the settings in the configuration file.

The following example shows how to bind the existing Profile 1 to port 1/0/2, and specify the maximum number of multicast groups that port 1/0/2 can join as 50 and the Overflow Action as Drop:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/2

Switch(config-if)#ip igmp snooping

Switch(config-if)#ip igmp filter 1

Switch(config-if)#ip igmp snooping max-groups 50

Switch(config-if)#ip igmp snooping max-groups action drop

Switch(config-if)#show ip igmp profile

IGMP Profile 1

...

Binding Port(s)

Gi1/0/2

Switch(config-if)#show ip igmp snooping interface gigabitEthernet 1/0/2 max-groups

PortMax-GroupsOverflow-Action
Gi1/0/250Drops

Switch(config)#end

Switch#copy running-config startup-config

Binding the MLD Profile to Ports

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}

Enter interface configuration mode.

Step 3 ipv6 mld filter profile-id

Bind the MLD profile to the specified ports.

profile-id: Specify the ID of the profile to be bound. It should be an existing profile.

Step 4 ipv6 mld snooping max-groups maxgroupConfigure the maximum number of multicast groups the port can join.maxgroup: Specify the maximum number of multicast groups the port can join. The range is 0 to 1000.
Step 5 ipv6 mld snooping max-groups action {drop | replace}Specify the action towards the new multicast group when the number of multicast groups the port joined exceeds max group.drop: Drop all subsequent membership report messages, and the port join no more new multicast groups.replace: Replace the existing multicast group owning the lowest multicast MAC address with the new multicast group.
Step 6 show ipv6 mld profile [ id]Show the detailed MLD profile configuration.show ipv6 mld snooping interface [fastEthernet [port-list ] | gigabitEthernet [port-list ] | ten-gigabitEthernet [port-list ] | port-channel [port-channel-list ] ] max-groupsShow the multicast group limitation on the specified port(s) or of all the ports.
Step 7 endReturn to privileged EXEC mode.
Step 8 copy running-config startup-configSave the settings in the configuration file.

The following example shows how to bind the existing Profile 1 to port 1/0/2, and specify the maximum number of multicast groups that port 1/0/2 can join as 50 and the Overflow Action as Drop:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/2

Switch(config-if)#ipv6 mld snooping

Switch(config-if)#ipv6 mld filter 1

Switch(config-if)#ipv6 mld snooping max-groups 50

Switch(config-if)#ipv6 mld snooping max-groups action drop

Switch(config-if)#show ipv6 mld profile

MLD Profile 1

...

Binding Port(s)

Gi1/0/2

Switch(config-if)#show ipv6 mld snooping interface gigabitEthernet 1/0/2 max-groups

PortMax-GroupsOverflow-Action
Gi1/0/250Drops

Switch(config)#end

Switch#copy running-config startup-config

6 Viewing Multicast Snooping Information

You can view the following multicast snooping information:

■ View IPv4 multicast table.
■ View IPv4 multicast statistics on each port.
■ View IPv6 multicast table.
■ View IPv6 multicast statistics on each port.

6.1 Using the GUI

6.1.1 Viewing IPv4 Multicast Table

Choose the menu L2 FEATURES > Multicast > Multicast Info > IPv4 Multicast Table to load the following page:

Figure 6-1 IPv4 Multicast Table
TP-LINK Omada TL-SG2008P - Viewing IPv4 Multicast Table - 1

text_image Multicast IP Address Table All Refresh Index Multicast IP VLAN ID Source Type Forward Ports No entries in this table. Total: 0

The multicast IP address table shows all valid Multicast IP-VLAN-Port entries:

Multicast IP Displays the multicast source IP address.

VLAN ID Displays the ID of the VLAN the multicast group belongs to.

Source Displays the source of the multicast entry.

IGMP Snooping: The multicast entry is learned by IGMP Snooping.

MVR: The multicast entry is learned by MVR.

Type Displays how the multicast entry is generated.

Dynamic: The entry is dynamically learned. All the member ports are dynamically added to the multicast group.

Static: The entry is manually added. All the member ports are manually added to the multicast group.

Mix: The entry is dynamically learned (manually learned), and some of the member ports are manually added (dynamically added) to the multicast group.

Forward Ports All ports in the multicast group, including router ports and member ports.

6.1.2 Viewing IPv4 Multicast Statistics on Each Port

Choose the menu L2 FEATURES > Multicast > Multicast Info > IPv4 Multicast Statistics to load the following page:

Figure 6-2 IPv4 Multicast Statistics
TP-LINK Omada TL-SG2008P - Viewing IPv4 Multicast Statistics on Each Port - 1

text_image Auto Refresh Auto Refresh: ✓ Refresh Interval: 300 seconds (3-300) Apply Port Statistics UNIT1 LAGS Refresh ID Port Query Packets Report Packets Report Packets Leave Packets Error Packets 1 1/0/1 0 0 0 0 0 0 2 1/0/2 0 0 0 0 0 0 3 1/0/3 0 0 0 0 0 0 4 1/0/4 0 0 0 0 0 0 5 1/0/5 0 0 0 0 0 0 6 1/0/6 0 0 0 0 0 0 7 1/0/7 0 0 0 0 0 0 8 1/0/8 0 0 0 0 0 0 9 1/0/9 0 0 0 0 0 0 10 1/0/10 0 0 0 0 0 0 Total: 28

Follow these steps to view IPv4 multicast statistics on each port:

1) To get the real-time multicast statistics, enable Auto Refresh, or click Refresh.

Auto Refresh

Enable or disable Auto Refresh. When enabled, the switch will automatically refresh the multicast statistics.

Refresh IntervalAfter Auto Refresh is enabled, specify the time interval for the switch to refresh the multicast statistics.

2) In the Port Statistics section, view IPv4 multicast statistics on each port.

Query Packets Displays the number of query packets received by the port.
Report Packets (v1)Displays the number of IGMPv1 report packets received by the port.
Report Packets (v2)Displays the number of IGMPv2 report packets received by the port.
Report Packets (v3)Displays the number of IGMPv3 report packets received by the port.
Leave Packets Displays the number of leave packets received by the port.
Error Packets Displays the number of error packets received by the port.

6.1.3 Viewing IPv6 Multicast Table

Choose the menu L2 FEATURES > Multicast > Multicast Info > IPv6 Multicast Table to load the following page:

Figure 6-3 IPv6 Multicast Table
TP-LINK Omada TL-SG2008P - Viewing IPv6 Multicast Table - 1

text_image Multicast IP Address Table All Refresh Index Multicast IP VLAN ID Source Type Forward Ports No entries in this table. Total: 0

The multicast IP address table shows all valid Multicast IP-VLAN-Port entries:

Multicast IP Displays the multicast source IP address.

VLAN ID Displays the ID of the VLAN the multicast group belongs to.

Source Displays the source of the multicast entry.

MLD Snooping: The multicast entry is learned by MLD Snooping.

Type Displays how the multicast entry is generated.

Dynamic: The entry is dynamically learned. All the member ports are dynamically added to the multicast group.

Static: The entry is manually added. All the member ports are manually added to the multicast group.

Mix: The entry is dynamically learned (manually learned), and some of the member ports are manually added (dynamically added) to the multicast group.

Forward Port All ports in the multicast group, including router ports and member ports.

6.1.4 Viewing IPv6 Multicast Statistics on Each Port

Choose the menu L2 FEATURES > Multicast > Multicast Info > IPv6 Multicast Statistics to load the following page:

Figure 6-4 IPv6 Multicast Statistics
TP-LINK Omada TL-SG2008P - Viewing IPv6 Multicast Statistics on Each Port - 1

text_image Auto Refresh Auto Refresh: ✓ Refresh Interval: 300 seconds (3-300) Apply Port Statistics UNIT1 LAGS Refresh ID Port Query Packets Report Packets (v1) Report Packets (v2) Done Packets Error Packets 1 1/0/1 0 0 0 0 0 2 1/0/2 0 0 0 0 0 3 1/0/3 0 0 0 0 0 4 1/0/4 0 0 0 0 0 5 1/0/5 0 0 0 0 0 6 1/0/6 0 0 0 0 0 7 1/0/7 0 0 0 0 0 8 1/0/8 0 0 0 0 0 9 1/0/9 0 0 0 0 0 10 1/0/10 0 0 0 0 0 Total: 28

Follow these steps to view IPv6 multicast statistics on each port:

1) To get the real-time IPv6 multicast statistics, enable Auto Refresh, or click Refresh.

Auto Refresh

Enable or disable Auto Refresh. When enabled, the switch will automatically refresh the multicast statistics.

Refresh IntervalAfter Auto Refresh is enabled, specify the time interval for the switch to refresh the multicast statistics.
2) In the Port Statistics section, view IPv6 multicast statistics on each port.
Query Packets Displays the number of query packets received by the port.
Report Packets (v1)Displays the number of MLDv1 packets received by the port.
Report Packets (v2)Displays the number of MLDv2 packets received by the port.
Done Packets Displays the number of done packets received by the port.
Error Packets Displays the number of error packets received by the port.

6.2 Using the CLI

6.2.1 Viewing IPv4 Multicast Snooping Information

show ip igmp snooping groups [vlan vlan-id] [count | dynamic | dynamic count | static | static count]

Displays information of specific multicast group in all VLANs or in the specific VLAN.

count: Displays the number of multicast groups.

dynamic: Displays information of all dynamic multicast groups.

dynamic count: Displays the number of dynamic multicast groups.

static: Displays information of all static multicast groups.

static count: Displays the number of static multicast groups.

show ip igmp snooping interface [fastEthernet [port-list] | gigabitEthernet [port-list] | ten-gigabitEthernet [port-list] ] packet-stat

Displays the packet statistics on specified ports or all ports.

clear ip igmp snooping statistics

Clear all statistics of all IGMP packets.

6.2.2 Viewing IPv6 Multicast Snooping Configurations

show ipv6 mld snooping groups [vlan vlan-id] [count | dynamic | dynamic count | static | static count]

Displays information of specific multicast group in all VLANs or in the specific VLAN.

count displays the number of multicast groups.

dynamic displays information of all dynamic multicast groups.

dynamic count displays the number of dynamic multicast groups.

static displays information of all static multicast groups.

static count displays the number of static multicast groups.

show ipv6 mld snooping interface [fastEthernet [port-list] | gigabitEthernet [port-list] | ten-gigabitEthernet [port-list] ] packet-stat

Displays the packet statistics on specified ports or all ports.

clear ipv6 mld snooping statistics

Clear all statistics of all MLD packets.

7 Configuration Examples

7.1 Example for Configuring Basic IGMP Snooping

7.1.1 Network Requirements

Host B, Host C and Host D are in the same VLAN of the switch. All of them want to receive multicast streams sent to multicast group 225.1.1.1.

As shown in the following topology, Host B, Host C and Host D are connected to port 1/0/1, port 1/0/2 and port 1/0/3 respectively. Port 1/0/4 is the router port connected to the multicast querier.

Figure 7-1 Network Topology for Basic IGMP Snooping
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["Source"] --> B["Internet"]
    B --> C["Querier"]
    C --> D["Gi1/0/4"]
    C --> E["Gi1/0/3"]
    D --> F["Host B Receiver"]
    D --> G["Host C Receiver"]
    D --> H["Host D Receiver"]
    E --> I["Gi1/0/2"]
    E --> J["Gi1/0/1"]
    style A fill:#6699CC,stroke:#333
    style B fill:#99CCFF,stroke:#333
    style C fill:#99CCFF,stroke:#333
    style D fill:#99CCFF,stroke:#333
    style E fill:#99CCFF,stroke:#333
    style F fill:#99CCFF,stroke:#333
    style G fill:#99CCFF,stroke:#333
    style H fill:#99CCFF,stroke:#333
    style I fill:#99CCFF,stroke:#333
    style J fill:#99CCFF,stroke:#333

7.1.2 Configuration Scheme

■ Add the three member ports and the router port to a VLAN and configure their PVIDs.
■ Enable IGMP Snooping globally and in the VLAN.

■ Enable IGMP Snooping on the ports.

Demonstrated with T1600G-28TS, this section provides configuration procedures in two ways: using the GUI and using the CLI.

7.1.3 Using the GUI

1) Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > VLAN Config and click

Add to load the following page. Create VLAN 10 and add Untagged port 1/0/1-3 and Tagged port 1/0/4 to VLAN 10.

Figure 7-2 Create VLAN 10
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image VLAN Config VLAN ID: 10 (2-4094, format: 2,4-5,8) VLAN Name: VLAN10 (1-16 characters) Untagged Ports Port: 1/0/1-3 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Tagged Ports Port: 1/0/4 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

2) Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > Port Config to load the following page. Configure the PVID of port 1/0/1-4 as 10.

Figure 7-3 Configure PVID for the Ports
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image Port Config UNIT1 LAGS Port PVID Ingress Checking Acceptable Frame Types LAG Detail 10 ✓ 1/0/1 10 Enabled Admit All --- Detail ✓ 1/0/2 10 Enabled Admit All --- Detail ✓ 1/0/3 10 Enabled Admit All --- Detail ✓ 1/0/4 10 Enabled Admit All --- Detail □ 1/0/5 1 Enabled Admit All --- Detail □ 1/0/6 1 Enabled Admit All --- Detail □ 1/0/7 3 Enabled Admit All --- Detail □ 1/0/8 3 Enabled Admit All --- Detail □ 1/0/9 1 Enabled Admit All --- Detail □ 1/0/10 1 Enabled Admit All --- Detail Total: 28 4 entries selected. Cancel Apply

3) Choose the menu L2 FEATURES > Multicast > IGMP Snooping > Global Config to load the following page. In the Global Config section, enable IGMP Snooping globally. Configure the IGMP version as v3 so that the switch can process IGMP messages of all versions. Then click Apply.

Figure 7-4 Configure IGMP Snooping Globally
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image Global Config IGMP Snooping: ✓ Enable IGMP Version: ○ v1 ○ v2 ● v3 Unknown Multicast Groups: ○ Forward ○ Discard Header Validation: □ Enable Apply IGMP VLAN Config VLAN ID VLAN ID IGMP Snooping Status Fast Leave Report Suppression IGMP Snooping Querier Dynamic Router Ports Static Router Ports Forbidden Router Ports Operation 1 Disabled Disabled Disabled Disabled 10 Disabled Disabled Disabled Disabled Total: 2

4) In the IGMP VLAN Config section, click √ in VLAN 10 to load the following page. Enable IGMP Snooping for VLAN 10.

Figure 7-5 Enable IGMP Snooping for VLAN 10
TP-LINK Omada TL-SG2008P - Using the GUI - 4

text_image Configure IGMP Snooping for VLAN VLAN ID: 10 IGMP Snooping Status: ✓ Enable Fast Leave: □ Enable Report Suppression: □ Enable Member Port Aging Time: 260 seconds (60-600) Router Port Aging Time: 300 seconds (60-600) IGMP Snooping Querier: □ Enable Static Router Ports

5) Choose the menu L2 FEATURES > Multicast > IGMP Snooping > Port Config to load the following page. Enable IGMP Snooping for ports 1/0/1-4.

Figure 7-6 Enable IGMP Snooping for the Ports
TP-LINK Omada TL-SG2008P - Using the GUI - 5

text_image Port Config UNIT1 LAGS Port IGMP Snooping Fast Leave LAG ✓ 1/0/1 Enabled Disabled --- ✓ 1/0/2 Enabled Disabled --- ✓ 1/0/3 Enabled Disabled --- ✓ 1/0/4 Enabled Disabled --- □ 1/0/5 Enabled Disabled --- □ 1/0/6 Enabled Disabled --- □ 1/0/7 Enabled Disabled LAG1 □ 1/0/8 Enabled Disabled LAG1 □ 1/0/9 Enabled Disabled --- □ 1/0/10 Enabled Disabled --- Total: 28 4 entries selected. Cancel Apply

6) Click Save the settings.

7.1.4 Using the CLI

1) Create VLAN 10.

Switch#configure

Switch(config)#vlan 10

Switch(config-vlan)#name vlan10

Switch(config-vlan)#exit

2) Add port 1/0/1-3 to VLAN 10 and set the link type as untagged. Add port 1/0/4 to VLAN 10 and set the link type as tagged.

Switch(config)#interface range gigabitEthernet 1/0/1-3

Switch(config-if-range)#switchport general allowed vlan 10 untagged

Switch(config-if-range)#exit

Switch(config)#interface gigabitEthernet 1/0/4

Switch(config-if)#switchport general allowed vlan 10 tagged

Switch(config-if)#exit

3) Set the PVID of port 1/0/1-4 as 10.

Switch(config)#interface range gigabitEthernet 1/0/1-4

Switch(config-if-range)#switchport pvid 10

Switch(config-if-range)#exit

4) Enable IGMP Snooping globally.

Switch(config)#ip igmp snooping

5) Enable IGMP Snooping in VLAN 10.

Switch(config)#ip igmp snooping vlan-config 10

6) Enable IGMP Snooping on port 1/0/1-4.

Switch(config)#interface range gigabitEthernet 1/0/1-4

Switch(config-if-range)#ip igmp snooping

Switch(config-if-range)#exit

7) Save the settings.

Switch(config)#end

Switch#copy running-config startup-config

Verify the Configurations

Show members in the VLAN:

Switch(config)#show vlan brief

VLAN

Name

Status

Ports

Show status of IGMP Snooping globally, on the ports and in the VLAN:

Switch(config)#show ip igmp snooping

IGMP Snooping :Enable

IGMP Version :V3

Header Validation :Disable

Global Authentication Accounting : Disable

Enable Port : Gi1/0/1-4

Enable VLAN:10

7.2 Example for Configuring MVR

7.2.1 Network Requirements

Host B, Host C and Host D are in three different VLANs of the switch. All of them want to receive multicast streams sent to multicast group 225.1.1.1.

7.2.2 Network Topology

As shown in the following network topology, Host B, Host C and Host D are connected to port 1/0/1, port 1/0/2 and port 1/0/3 respectively. Port 1/0/1, port 1/0/2 and port 1/0/3 belong to VLAN 10, VLAN 20 and VLAN 30 respectively. Port 1/0/4 is connected to the multicast network in the upper layer network.

Figure 7-7 Network Topology for Multicast VLAN
TP-LINK Omada TL-SG2008P - Network Topology - 1

flowchart
graph TD
    A["Source"] --> B["Internet"]
    B --> C["Querier"]
    C --> D["G1/0/4"]
    C --> E["G1/0/3"]
    D --> F["Host B Receiver"]
    D --> G["Host C Receiver"]
    D --> H["Host D Receiver"]
    E --> I["Host B Receiver"]
    E --> J["Host C Receiver"]
    E --> K["Host D Receiver"]

7.2.3 Configuration Scheme

As the hosts are in different VLANs, in IGMP Snooping, the Querier need to duplicate multicast streams for hosts in each VLAN. To avoid duplication of multicast streams being sent between Querier and the switch, you can configure MVR on the switch.

The switch can work in either MVR compatible mode or MVR dynamic mode. When in compatible mode, remember to statically configure the Querier to transmit the streams of multicast group 225.1.1.1 to the switch via the multicast VLAN. Here we take the MVR dynamic mode as an example.

Demonstrated with T1600G-28TS, this section provides configuration procedures in two ways: using the GUI and using the CLI.

7.2.4 Using the GUI

1) Add port 1/0/1-3 to VLAN 10, VLAN 20 and VLAN 30 as Untagged ports respectively, and configure the PVID of port 1/0/1 as 10, port 1/0/2 as 20, port 1/0/3 as 30. Make sure port1/0/1-3 only belong to VLAN 10, VLAN 20 and VLAN 30 respectively. For details, refer to Configuring 802.1Q VLAN.

Figure 7-8 VLAN Configurations for Port 1/0/1-3
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image VLAN Config VLAN ID VLAN Name Members Operation 1 System-VLAN 1/0/4-28 10 VLAN10 1/0/1 20 VLAN20 1/0/2 30 VLAN30 1/0/3 Total: 4

Figure 7-9 PVID for Port 1/0/1-3

TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image Port Config UNIT1 LAGS Port PVID Ingress Checking Acceptable Frame Types LAG Detail 1/0/1 10 Enabled Admit All --- Detail 1/0/2 20 Enabled Admit All --- Detail 1/0/3 30 Enabled Admit All --- Detail 1/0/4 1 Enabled Admit All --- Detail 1/0/5 1 Enabled Admit All --- Detail 1/0/6 1 Enabled Admit All --- Detail 1/0/7 1 Enabled Admit All --- Detail 1/0/8 1 Enabled Admit All --- Detail 1/0/9 1 Enabled Admit All --- Detail 1/0/10 1 Enabled Admit All --- Detail Total: 28

2) Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > VLAN Config and click Add to load the following page. Create VLAN 40 and add port 1/0/4 to the VLAN as Tagged port.

Figure 7-10 Create Multicast VLAN
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image VLAN Config VLAN ID: 40 (2-4094, format: 2,4-5,8) VLAN Name: Multicast_VLAN (1-16 characters) Untagged Ports Port: (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Tagged Ports Port: 1/0/4 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 SelectedUnselectedNot Available Cancel Create

3) Choose the menu L2 FEATURES > Multicast > MVR > MVR Config to load the following page. Enable MVR globally, and configure the MVR mode as Dynamic, multicast VLAN ID as 40.

Figure 7-11 Configure MVR Globally
TP-LINK Omada TL-SG2008P - Using the GUI - 4

text_image MVR Config MVR: Enable MVR Mode: Compatible Dynamic Multicast VLAN ID: 40 (1-4094) Query Response Time: 5 tenths of a second (1-100) Maximum Multicast Groups: 511 Current Multicast Groups: 0 Apply

4) Choose the menu L2 FEATURES > Multicast > MVR > MVR Group Config and click

Add to load the following page. Add multicast group 225.1.1.1 to MVR.

Figure 7-12 Add Multicast Group to MVR
TP-LINK Omada TL-SG2008P - Using the GUI - 5

text_image MVR Group IP MVR Group IP: 225.1.1.1 (Format: 235.0.0.1) MVR Group Count: 1 (1-250) Cancel Create

5) Choose the menu L2 FEATURES > Multicast > MVR > Port Config to load the following page. Enable MVR for port 1/0/1-4. Configure port 1/0/1-3 as Receiver ports and port 1/0/4 as Source port.

Figure 7-13 Configure MVR for the Ports
TP-LINK Omada TL-SG2008P - Using the GUI - 6

text_image Port Config UNIT1 Port Mode Type Status Immediate Leave 1/0/1 Enable Receiver Inactive/inVLAN Disable 1/0/2 Enable Receiver Inactive/inVLAN Disable 1/0/3 Enable Receiver Inactive/inVLAN Disable 1/0/4 Enable Source Inactive/inVLAN Disable 1/0/5 Disable None Inactive/inVLAN Disable 1/0/6 Disable None Inactive/inVLAN Disable 1/0/7 Disable None Inactive/inVLAN Disable 1/0/8 Disable None Inactive/inVLAN Disable 1/0/9 Disable None Inactive/inVLAN Disable 1/0/10 Disable None Inactive/inVLAN Disable Total: 28

6) Click to save the settings.

7.2.5 Using the CLI

1) Create VLAN 10, VLAN 20, VLAN 30 and VLAN 40.

Switch#configure

Switch(config)#vlan 10,20,30,40

Switch(config-vlan)#exit

2) Add port 1/0/1-3 to VLAN 10, VLAN 20 and VLAN 30 as untagged ports respectively, and configure the PVID of port 1/0/1 as 10, port 1/0/2 as 20, port 1/0/3 as 30. Add port 1/0/4 to VLAN 40 as tagged port and configure the PVID as of port 1/0/4 as 40.

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#switchport general allowed vlan 10 untagged

Switch(config-if)#switchport pvid 10

Switch(config-if)#exit

Switch(config)#interface gigabitEthernet 1/0/2

Switch(config-if)#switchport general allowed vlan 20 untagged

Switch(config-if)#switchport pvid 20

Switch(config-if)#exit

Switch(config)#interface gigabitEthernet 1/0/3

Switch(config-if)#switchport general allowed vlan 30 untagged

Switch(config-if)#switchport pvid 30

Switch(config-if)#exit

Switch(config)#interface gigabitEthernet 1/0/4

Switch(config-if)#switchport general allowed vlan 40 tagged

Switch(config-if)#switchport pvid 40

Switch(config-if)#exit

3) Check whether port1/0/1-3 only belong to VLAN 10, VLAN 20 and VLAN 30 respectively. If not, delete them from the other VLANs. By default, all ports are in VLAN 1, so you need to delete them from VLAN 1.

Switch(config)#show vlan brief

VLAN

Name

Status

Ports

4) Enable MVR globally, and configure the MVR mode as Dynamic, multicast VLAN ID as 40. Add multicast group 225.1.1.1 to MVR.

Switch(config)#mvr

Switch(config)#mvr mode dynamic

Switch(config)#mvr vlan 40

Switch(config)#mvr group 225.1.1.1

5) Enable MVR for port 1/0/1-4. Configure port 1/0/1-3 as Receiver ports and port 1/0/4 as Source port.

Switch(config)#interface range gigabitEthernet 1/0/1-3

Switch(config-if-range)#mvr

Switch(config-if-range)#mvr type receiver

Switch(config-if-range)#exit

Switch(config)#interface gigabitEthernet 1/0/4

Switch(config-if)#mvr

Switch(config-if)#mvr type source

Switch(config-if)#exit

6) Save the settings.

Switch(config)#end

Switch#copy running-config startup-config

Verify the Configurations

Show the brief information of all VLANs:

Switch(config)#show vlan brief

VLAN

Name

Status

Ports

1 System-VLAN active Gi1/0/4, Gi1/0/5, Gi1/0/6, Gi1/0/7,

...

10

VLAN10

active

Gi1/0/1

20

VLAN20

active

Gi1/0/2

30

VLAN30

active

Gi1/0/3

40

VLAN40

active

Gi1/0/4

Show the brief information of MVR:

Switch(config)#show mvr

MVR

:Enable

MVR

Multicast

Vlan

:40

MVR Max Multicast Groups :511

MVR Current Multicast Groups :1

MVR Global Query Response Time :5 (tenths of sec)

MVR

Mode

Type

:Dynamic

Show the membership of MVR groups:

Switch(config)#show mvr members

MVR

Group

IP

Status

Members

225.1.1.1

active

Gi1/0/4

7.3 Example for Configuring Unknown Multicast and Fast Leave

7.3.1 Network Requirement

A user experiences lag when he is changing channel on his IPTV. He wants solutions to this problem. As shown in the following network topology, port 1/0/4 on the switch is connected to the upper layer network, and port 1/0/2 is connected to Host B.

Figure 7-14 Network Topology for Unknow Multicast and Fast Leave
TP-LINK Omada TL-SG2008P - Network Requirement - 1

flowchart
graph TD
    A["Source"] --> B["Internet"]
    B --> C["Querier"]
    C --> D["VLAN 10"]
    D --> E["Host B Receiver"]
    D --> F["Gi1/0/4 VLAN 10"]
    D --> G["Gi1/0/2"]

7.3.2 Configuration Scheme

After the channel is changed, the client (Host B) still receives irrelevant multicast data, the data from the previous channel and possibly other unknown multicast data, which increases the network load and results in network congestion.

To avoid Host B from receiving irrelevant multicast data, you can enable Fast Leave on port 1/0/2 and configure the switch to discard unknown multicast data. To change channel, Host B sends a leave message about leaving the previous channel. With Fast Leave enabled on port 1/0/2, the switch will then drop multicast data from the previous channel, which ensures that Host B only receives multicast data from the new channel and that the multicast network is unimpeded.

Demonstrated with T1600G-52TS, this section provides configuration procedures in two ways: using the GUI and using the CLI.

7.3.3 Using the GUI

1) Create VLAN 10. Add port 1/0/2 to the VLAN as untagged port and port 1/0/4 as tagged port. Configure the PVID of the two ports as 10. For details, refer to Configuring 802.1Q VLAN.

2) Choose the menu L2 FEATURES > Multicast > IGMP Snooping > Global Config to load the following page. In the Global Config section, enable IGMP Snooping globally and configure Unknown Multicast Groups as Discard.

Figure 7-15 Configure IGMP Snooping Globally
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Global Config IGMP Snooping: ✓ Enable IGMP Version: ○ v1 ○ v2 ● v3 Unknown Multicast Groups: ○ Forward ● Discard Header Validation: □ Enable Apply IGMP VLAN Config VLAN ID VLAN ID IGMP Snooping Status Fast Leave Report Suppression IGMP Snooping Querier Dynamic Router Ports Static Router Ports Forbidden Router Ports Operation 1 Disabled Disabled Disabled Disabled 10 Disabled Disabled Disabled Disabled Total: 2

TP-LINK Omada TL-SG2008P - Using the GUI - 2

Note:

IGMP Snooping and MLD Snooping share the setting of Unknown Multicast, so you have to enable MLD Snooping globally on the L2 FEATURES > Multicast > MLD Snooping > Global Config page at the same time.

3) In the IGMP VLAN Config section, click ☑ in VLAN 10 to load the following page. Enable IGMP Snooping for VLAN 10.

Figure 7-16 Enable IGMP Snooping for VLAN 10
TP-LINK Omada TL-SG2008P - Note: - 1

text_image Configure IGMP Snooping for VLAN VLAN ID: 10 IGMP Snooping Status: ✓ Enable Fast Leave: □ Enable Report Suppression: □ Enable Member Port Aging Time: 260 seconds (00-000) Router Port Aging Time: 300 seconds (60-600) IGMP Snooping Querier: □ Enable Static Router Ports

4) Choose the menu L2 FEATURES > Multicast > IGMP Snooping > Port Config to load the following page. Enable IGMP Snooping on port 1/0/2 and port 1/0/4 and enable Fast Leave on port 1/0/2.

Figure 7-17 Configure IGMP Snooping on Ports
TP-LINK Omada TL-SG2008P - Note: - 2

text_image Port Config UNIT1 LAGS Port IGMP Snooping Fast Leave LAG 1/0/1 Enabled Disabled --- ✓ 1/0/2 Enabled Enabled --- □ 1/0/3 Enabled Disabled --- □ 1/0/4 Enabled Disabled --- □ 1/0/5 Enabled Disabled --- □ 1/0/6 Enabled Disabled --- □ 1/0/7 Enabled Disabled --- □ 1/0/8 Enabled Disabled --- □ 1/0/9 Enabled Disabled --- □ 1/0/10 Enabled Disabled --- Total: 28 1 entry selected. Cancel Apply

5) Click save the settings.

7.3.4 Using the CLI

1) Enable IGMP Snooping and MLD Snooping globally.

Switch#configure

Switch(config)#ip igmp snooping

Switch(config)#ipv6 mld snooping

2) Configure Unknown Multicast Groups as Discard globally.

Switch(config)#ip igmp snooping drop-unknown

3) Enable IGMP Snooping on port 1/0/2 and enable Fast Leave. On port 1/0/4, enable IGMP Snooping.

Switch(config)#interface gigabitEthernet 1/0/2

Switch(config-if)#ip igmp snooping

Switch(config-if)#ip igmp snooping immediate-leave

Switch(config-if)#exit

Switch(config)#interface gigabitEthernet 1/0/4

Switch(config-if)#ip igmp snooping

Switch(config-if)#exit

4) Enable IGMP Snooping in VLAN 10.

Switch(config)#ip igmp snooping vlan-config 10

5) Save the settings.

Switch(config)#end

Switch#copy running-config startup-config

Verify the Configurations

Show global settings of IGMP Snooping:

Switch(config)#show ip igmp snooping

IGMP Snooping :Enable

IGMP Version :V3

Unknown Multicast :Discard

...

Enable Port: Gi1/0/1-28

Enable VLAN:10

Show settings of IGMP Snooping on port 1/0/2:

Switch(config)#show ip igmp snooping interface gigabitEthernet 1/0/2 basic-config

Port IGMP-Snooping Fast-Leave

Gi1/0/2 enable enable

7.4 Example for Configuring Multicast Filtering

7.4.1 Network Requirements

Host B, Host C and Host D are in the same subnet. Host C and Host D only receive multicast data sent to 225.0.0.1, while Host B receives all multicast data except the one sent from 225.0.0.2.

7.4.2 Configuration Scheme

With the functions for managing multicast groups, whitelist and blacklist mechanism (profile binding), the switch can only allow specific member ports to join specific multicast groups or disallow specific member ports to join specific multicast groups. You can achieve this filtering function by creating a profile and binding it to the corresponding member port.

7.4.3 Network Topology

As shown in the following network topology, Host B is connected to port 1/0/1, Host C is connected to port 1/0/2 and Host D is connected to port 1/0/3. They are all in VLAN 10.

Figure 7-18 Network Topology for Multicast Filtering
TP-LINK Omada TL-SG2008P - Network Topology - 1

flowchart
graph TD
    A["Source"] --> B["Internet"]
    B --> C["Querier"]
    C --> D["Gi1/0/1"]
    C --> E["Gi1/0/2"]
    C --> F["Gi1/0/3"]
    D --> G["VLAN 10"]
    E --> H["Host B Receiver"]
    E --> I["Host C Receiver"]
    E --> J["Host D Receiver"]

Demonstrated with T1600G-28TS, this section provides configuration procedures in two ways: using the GUI and using the CLI.

7.4.4 Using the GUI

1) Create VLAN 10. Add port 1/0/1-3 to the VLAN as untagged port and port 1/0/4 as tagged port. Configure the PVID of the four ports as 10. For details, refer to Configuring 802.1Q VLAN.
2) Choose the menu L2 FEATURES > Multicast > IGMP Snooping > Global Config to load the following page. In the Global Config section, enable IGMP Snooping globally.

Figure 7-19 Enable IGMP Snooping Globally
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Global Config IGMP Snooping: ✓ Enable IGMP Version: ○ v1 ○ v2 ● v3 Unknown Multicast Groups: ● Forward ○ Discard Header Validation: □ Enable Apply IGMP VLAN Config VLAN ID VLAN ID IGMP Snooping Status Fast Leave Report Suppression IGMP Snooping Querier Dynamic Router Ports Static Router Ports Forbidden Router Ports Operation 1 Disabled Disabled Disabled Disabled 10 Disabled Disabled Disabled Disabled Total: 2

3) In the IGMP VLAN Config section, click √ in VLAN 10 to load the following page. Enable IGMP Snooping for VLAN 10.

Figure 7-20 Enable IGMP Snooping for VLAN 10
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image Configure IGMP Snooping for VLAN VLAN ID: 10 IGMP Snooping Status: ✓ Enable Fast Leave: □ Enable Report Suppression: □ Enable Member Port Aging Time: 260 seconds (60-600) Router Port Aging Time: 300 seconds (60-600) IGMP Snooping Quener: □ Enable Static Router Ports

4) Choose the menu L2 FEATURES > Multicast > IGMP Snooping > Port Config to load the following page.

Figure 7-21 Enable IGMP Snooping on the Port
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image Port Config UNIT1 LAGS Port IGMP Snooping Fast Leave LAG ✓ 1/0/1 Enabled Disabled --- ✓ 1/0/2 Enabled Disabled --- ✓ 1/0/3 Enabled Disabled --- ✓ 1/0/4 Enabled Disabled --- □ 1/0/5 Enabled Disabled --- □ 1/0/6 Enabled Disabled --- □ 1/0/7 Enabled Disabled LAG1 □ 1/0/8 Enabled Disabled LAG1 □ 1/0/9 Enabled Disabled --- □ 1/0/10 Enabled Disabled --- Total: 28 4 entries selected. Cancel Apply

5) Choose the menu L2 FEATURES > Multicast > Multicast Filtering > IPv4 Profile and click to load the following page. Create Profile 1, specify the mode as Permit, bind the profile to port 1/0/2-3, and specify the filtering multicast IP address as 225.0.0.1. Then click Back to return to the IPv4 Profile Table page.

Figure 7-22 Configure Filtering Profile for Host C and Host D
TP-LINK Omada TL-SG2008P - Using the GUI - 4

text_image Back General Config Profile ID: 1 (1-999) Mode: Permit Deny IP-Range Index Start IP Address End IP Address Operation 1 225.0.0.1 225.0.0.1 Total: 1 Bind Ports UNIT1 LAGS 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Discard Save

6) Click + Add again to load the following page. Create Profile 2, specify the mode as Deny, bind the profile to port 1/0/1, and specify the filtering multicast IP address as 225.0.0.2.

Figure 7-23 Configure Filtering Profile for Host B
TP-LINK Omada TL-SG2008P - Using the GUI - 5

text_image Back General Config Profile ID: 2 (1-999) Mode: Permit Deny IP-Range Index Start IP Address End IP Address Operation 1 225.0.0.2 225.0.0.2 Total: 1 Bind Ports UNIT1 LAGS 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Discard Save

7) Click Save the settings.

7.4.5 Using the CLI

1) Create VLAN 10.

Switch#configure

Switch(config)#vlan 10

Switch(config-vlan)#name vlan10

Switch(config-vlan)#exit

2) Add port 1/0/1-3 to VLAN 10 and set the link type as untagged. Add port 1/0/4 to VLAN 10 and set the link type as tagged.

Switch(config)#interface range gigabitEthernet 1/0/1-3

Switch(config-if-range)#switchport general allowed vlan 10 untagged

Switch(config-if-range)#exit

Switch(config)#interface gigabitEthernet 1/0/4

Switch(config-if)#switchport general allowed vlan 10 tagged

Switch(config-if)#exit

3) Set the PVID of port 1/0/1-4 as 10.

Switch(config)#interface range gigabitEthernet 1/0/1-4

Switch(config-if-range)#switchport pvid 10

Switch(config-if-range)#exit

4) Enable IGMP Snooping Globally.

Switch(config)#ip igmp snooping

5) Enable IGMP Snooping in VLAN 10.

Switch(config)#ip igmp snooping vlan-config 10

6) Enable IGMP Snooping on port 1/0/1-4.

Switch(config)#interface range gigabitEthernet 1/0/1-4

Switch(config-if-range)#ip igmp snooping

Switch(config-if-range)#exit

7) Create Profile 1, configure the mode as permit, and add an IP range with both start IP and end IP being 225.0.0.1.

Switch(config)#ip igmp profile 1

Switch(config-igmp-profile)#permit

Switch(config-igmp-profile)#range 225.0.0.1 225.0.0.1

Switch(config-igmp-profile)#exit

8) Bind Profile 1 to Port 1/0/2 and Port 1/10/3.

Switch(config)#interface range gigabitEthernet 1/0/2-3

Switch(config-if-range)#ip igmp filter 1

Switch(config-if-range)#exit

9) Create Profile 2, configure the mode as deny, and add an IP range with both start IP and end IP being 225.0.0.2.

Switch(config)#ip igmp profile 2

Switch(config-igmp-profile)#deny

Switch(config-igmp-profile)#range 225.0.0.2 225.0.0.2

Switch(config-igmp-profile)#exit

10) Bind Profile 2 to Port 1/0/1.

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#ip igmp filter 2

Switch(config-if)#exit

11) Save the settings.

Switch(config)#end

Switch#copy running-config startup-config

Verify the Configurations

Show global settings of IGMP Snooping:

Switch(config)#show ip igmp snooping

IGMP

Snooping

:Enable

IGMP

Version

:V3

...

Enable Port:Gi1/0/1-4

Enable VLAN:10

Show all profile bindings:

Switch(config)#show ip igmp profile

IGMP Profile 1

permit

range 225.0.0.1 225.0.0.1

Binding Port(s)

Gi1/0/2-3

IGMP Profile 2

deny

range 225.0.0.2 225.0.0.2

Binding Port(s)

Gi1/0/1

8 Appendix: Default Parameters

8.1 Default Parameters for IGMP Snooping

Table 8-1 Default Parameters of IGMP Snooping

Function Parameter Default Setting
Global Settings of IGMP SnoopingIGMP Snooping Disabled
IGMP Version v3
Unknown Multicast Groups Forward
Header Validation Disabled
IGMP Snooping Settings in the VLANIGMP Snooping Disabled
Fast Leave Disabled
Report Suppression Disabled
Member Port Aging Time 260 seconds
Router Port Aging Time300 seconds
Leave Time1 second
IGMP Snooping QuerierDisabled
Query Interval60 seconds
Maximum Response Time10 seconds
Last Member Query Interval1 second
Last Member Query Count2
General Query Source IP0.0.0.0
Static Router PortsNone
Forbidden Router PortsNone
IGMP Snooping Settings on the Port and LAGIGMP Snooping Enabled
Fast Leave Disabled
Static Multicast Group SettingsStatic Multicast Group EntriesNone
IGMP Accounting and AuthenticationIGMP Accounting Disabled
IGMP Authentication Disabled

8.2 Default Parameters for MLD Snooping

Table 8-2 Default Parameters of MLD Snooping

Function Parameter Default Setting
Global Settings of IGMP SnoopingMLD Snooping Disabled
Unknown Multicast Groups Forward
MLD Snooping Settings in the VLANMLD Snooping Disabled
Fast Leave Disabled
Report Suppression Disabled
Member Port Aging Time 260 seconds
Router Port Aging Time300 seconds
Leave Time1 second
MLD Snooping QuerierDisabled
Query Interval60 seconds
Maximum Response Time10 seconds
Last Listener Query Interval1 second
Last Listener Query Count2
General Query Source IP::
Static Router PortsNone
Forbidden Router PortsNone
MLD Snooping Settings on the Port and LAGMLD Snooping Enabled
Fast Leave Disabled
Static Multicast Group SettingsStatic Multicast Group EntriesNone

8.3 Default Parameters for MVR

Table 8-3 Default Parameters of MVR

Function Parameter Default Setting
Global Settings of MVRMVR Disabled
MVR Mode Compatible
Multicast VLAN ID 1
Query Response Time 5 tenths of a second
Maximum Multicast Groups 511
MVR Group Settings MVR Group Entries None
MVR Settings on the PortMVR Mode Disabled
MVR Port Type None
Fast Leave Disabled
MVR Static Group MembersMVR Static Group Member EntriesNone

8.4 Default Parameters for Multicast Filtering

Table 8-4 Default Parameters of Multicast Filtering

FunctionParameter Default Setting
Profile SettingsIPv4 Profile and IPv6 Profile EntriesNone
Multicast Filtering Settings on the Port and LAGBound ProfileNone
Maximum Groups1000
Overflow ActionDrop

Part 14

Configuring

Spanning Tree

CHAPTERS

  1. Spanning Tree
  2. STP/RSTP Configurations
  3. MSTP Configurations
  4. STP Security Configurations
  5. Configuration Example for MSTP
  6. Appendix: Default Parameters

1 Spanning Tree

1.1 Overview

STP

STP (Spanning Tree Protocol) is a layer 2 Protocol that prevents loops in the network. As is shown in Figure 1-1, STP helps to:

■ Block specific ports of the switches to build a loop-free topology.
■ Detect topology changes and automatically generate a new loop-free topology.

Figure 1-1 STP Function
TP-LINK Omada TL-SG2008P - STP - 1

RSTP (Rapid Spanning Tree Protocol) provides the same features as STP. Besides, RSTP can provide much faster spanning tree convergence.

MSTP

MSTP (Multiple Spanning Tree Protocol) also provides the fast spanning tree convergence as RSTP. In addition, MSTP enables VLANs to be mapped to different spanning trees (MST instances), and traffic in different VLANs will be transmitted along their respective paths, implementing load balancing.

1.2 Basic Concepts

1.2.1 STP/RSTP Concepts

Based on the networking topology below, this section will introduce some basic concepts in STP/RSTP.

Figure 1-2 STP/RSTP Topology
TP-LINK Omada TL-SG2008P - STP/RSTP Concepts - 1

flowchart
graph TD
    A["Root bridge"] -->|Designated port| B["Root port"]
    A -->|Designated port| C["Root port"]
    B -->|Designated port| D["Root port"]
    C -->|Designated port| E["Root port"]
    D -->|Backup port| F["Alternate port"]
    E -->|Backup port| F

Root Bridge

The root bridge is the root of a spanning tree. The switch with te lowest bridge ID will be the root bridge, and there is only one root bridge in a spanning tree.

Bridge ID

Bridge ID is used to select the root bridge. It is composed of a 2-byte priority and a 6-byte MAC address. The priority is allowed to be configured manually on the switch, and the switch with the lowest priority value will be elected as the root bridge. If the priority of the switches are the same, the switch with the smallest MAC address will be selected as the root bridge.

Port Role

■ Root Port

The root port is selected on non-root bridge that can provide the lowest root path cost. There is only one root port in each non-root bridge.

■ Designated Port

The designated port is selected in each LAN segment that can provide the lowest root path cost from that LAN segment to the root bridge.

Alternate Port

If a port is not selected as the designated port for it receives better BPDUs from another switch, it will become an alternate port.

In RSTP/MSTP, the alternate port is the backup for the root port. It is blocked when the root port works normally. Once the root port fails, the alternate port will become the new root port.

In STP, the alternate port is always blocked.

■ Backup Port

If a port is not selected as the designated port for it receives better BPDUs from the switch it belongs to, it will become an backup port.

In RSTP/MSTP, the backup port is the backup for the designated port. It is blocked when the designated port works normally. Once the root port fails, the backup port will become the new designated port.

In STP, the backup port is always blocked.

■ Disable Port

The disconnected port with spanning tree function enabled.

Port Status

Generally, in STP, the port status includes: Blocking, Listening, Learning, Forwarding and Disabled.

■ Blocking

In this status, the port receives and sends BPDUs. The other packets are dropped.

■ Listening

In this status, the port receives and sends BPDUs. The other packets are dropped.

■ Learning

In this status, the port receives and sends BPDUs. It also receives the other user packets to update its MAC address table, but doesn't forward them.

Forwarding

In this status, the port receives and sends BPDUs. It also receives the other user packets to update its MAC address table, and forwards them.

■ Disabled

In this status, the port is not participating in the spanning tree, and drops all the packets it receives.

In RSTP/MSTP, the port status includes: Discarding, Learning and Forwarding. The Discarding status is the grouping of STP's Blocking, Listening and Disabled, and the

Learning and Forwarding status correspond exactly to the Learning and Forwarding status specified in STP.

In TP-Link switches, the port status includes: Blocking, Learning, Forwarding and Disconnected.

■ Blocking

In this status, the port receives and sends BPDUs. The other packets are dropped.

■ Learning

In this status, the port receives and sends BPDUs. It also receives the other user packets to update its MAC address table, but doesn't forward them.

Forwarding

In this status, the port receives and sends BPDUs. It also receives the other user packets to update its MAC address table, and forwards them.

■ Disconnected

In this status, the port is enabled with spanning tree function but not connected to any device.

Path Cost

The path cost reflects the link speed of the port. The smaller the value, the higher link speed the port has.

The path cost can be manually configured on each port. If not, the path cost values are automatically calculated according to the link speed as shown below:

Table 1-1 The Default Path Cost Value

Link Speed Path Cost Value
10Mb/s 2,000,000
100Mb/s 200,000
1Gb/s 20,000
10Gb/s 2,000

Root Path Cost

The root path cost is the accumulated path costs from the root bridge to the other switches. When root bridge sends its BPDU, the root path cost value is 0. When a switch receives this BPDU, the root path cost will be increased according to the path cost of the receive port. Then it create a new BPDU with the new root file cost and forwards it to the

downstream switch. The value of the accumulated root path cost increases as the BPDU spreads further.

BPDU

BPDU is a kind of packet that is used to generate and maintain the spanning tree. The BPDUs (Bridge Protocol Data Unit) contain a lot of information, like bridge ID, root path cost, port priority and so on. Switches share these information to help determine the spanning tree topology.

1.2.2 MSTP Concepts

MSTP, compatible with STP and RSTP, has the same basic elements used in STP and RSTP. Based on the networking topology, this section will introduce some concepts only used in MSTP.

Figure 1-3 MSTP Topology
TP-LINK Omada TL-SG2008P - MSTP Concepts - 1

flowchart
graph TD
    subgraph Region 1
        A["region 1"] --> B["region 2"]
        B --> C["region 3"]
        C --> D["region 4"]
        D --> E["region 4"]
        style A fill:#f9f,stroke:#333
        style B fill:#bbf,stroke:#333
        style C fill:#bbf,stroke:#333
        style D fill:#bbf,stroke:#333
        style E fill:#bbf,stroke:#333
    end
    Note: Red 'x' marks the blocked port on Region 1 and Region 4.

MST Region

An MST region consists of multiple interconnected switches. The switches with the same following characteristics are considered as in the same region:

■ Same region name
■ Same revision level
■ Same VLAN-Instance mapping

MST Instance

The MST instance is a spanning tree running in the MST region. Multiple MST instances can be established in one MST region and they are independent of each other. As is shown in Figure 1-4, there are three instances in a region, and each instance has its own root bridge.

Figure 1-4 MST Region
TP-LINK Omada TL-SG2008P - MST Instance - 1

flowchart
graph TD
    A["Node A"] -->|Instance 1 (root bridge: A) VLAN 3| B["Node B"]
    A -->|Instance 2 (root bridge: B) VLAN 4-5| C["Node C"]
    B -->|Other VLANs| C
    C -->|ST| A
    style A fill:#99ccff,stroke:#333
    style B fill:#99ccff,stroke:#333
    style C fill:#99ccff,stroke:#333
    note right of A: Red 'X' marks blocked port; node right of C: Other VLANs; node left of A: Instance 1; node right of C: Instance 2; node right of C: Other VLANs; note right of A: Blocked port; note right of C: Other VLANs; note right of C: Other VLANs; note right of A: Other VLANs; note right of C: Other VLANs; note right of B: Blocked port; note right of C: Other VLANs; note right of A: Other VLANs; note right of C: Other VLANs; note right of B: Blocked port; note right of C: Other VLANs; note right of A: Other VLANs; note right of C: Other VLANs; note right of B: Blocked port; note right of C: Other VLANs; note right of A: Other VLANs; note right of C: Other VLANs; note left of A: Other VLANs; note left of C: Other VLANs; note right of B: Blocked port; note right of C: Other VLANs; note right of A: Other VLANs; note right of C: Other VLANs; note right of B: Blocked port; note right of C: Other VLANs; note right of A: Other VLANs; note right of C: Other VLANs; note right of B: Blocked port; note right of C: Other VLANs; note right of A: Unknown Port; note right of C: Unknown Port

VLAN-Instance Mapping

VLAN-Instance Mapping describes the mapping relationship between VLANs and instances. Multiple VLANs can be mapped to a same instance, but one VLAN can be mapped to only one instance. As Figure 1-4 shows, VLAN 3 is mapped to instance 1, VLAN 4 and VLAN 5 are mapped to instance 2, the other VLANs are mapped to the IST.

IST

The Internal Spanning Tree (IST), which is a special MST instance with an instance ID 0. By default, all the VLANs are mapped to IST.

CST

The Common Spanning Tree (CST), that is the spanning tree connecting all MST regions. As is shown in Figure 1-3, region1-region 4 are connected by the CST.

CIST

The Common and Internal Spanning Tree (CIST), comprising IST and CST. CIST is the spanning tree that connects all the switches in the network.

1.3 STP Security

STP Security prevents the loops caused by wrong configurations or BPDU attacks. It contains Loop Protect, Root Protect, BPDU Protect, BPDU Filter and TC Protect functions.

» Loop Protect

Loop Protect function is used to prevent loops caused by link congestions or link failures. It is recommended to enable this function on root ports and alternate ports.

If the switch cannot receive BPDUs because of link congestions or link failures, the root port will become a designated port and the alternate port will transit to forwarding status, so loops will occur.

With Loop Protect function enabled, the port will temporarily transit to blocking state when the port does not receive BPDUs. After the link restores to normal, the port will transit to its normal state, so loops can be prevented.

» Root Protect

Root Protect function is used to ensure that the desired root bridge will not lose its position. It is recommended to enable this function on the designated ports of the root bridge.

Generally, the root bridge will lose its position once receiving higher-priority BPDUs caused by wrong configurations or malicious attacks. In this case, the spanning tree will be regenerated, and traffic needed to be forwarded along high-speed links may be lead to low-speed links.

With root protect function enabled, when the port receives higher-priority BDPUs, it will temporarily transit to blocking state. After two times of forward delay, if the port does not receive any higher-priority BDPUs, it will transit to its normal state.

» BPDU Protect

BPDU Protect function is used to prevent the port from receiving BPUDs. It is recommended to enable this function on edge ports.

Normally edge ports do not receive BPDUs, but if a user maliciously attacks the switch by sending BPDUs, the system automatically configures these ports as non-edge ports and regenerates the spanning tree.

With BPDU protect function enabled, the edge port will be shutdown when it receives BPDUs, and reports these cases to the administrator. Only the administrator can restore it.

» BPDU Filter

BPDU filter function is to prevent BPDU flooding in the network. It is recommended to enable this function on edge ports.

If a switch receives malicious BPDUs, it forwards these BPDUs to the other switches in the network, and the spanning tree will be continuously regenerated. In this case, the switch occupies too much CPU or the protocol status of BPDUs is wrong.

With the BPDU Filter function enabled, the port does not forward BPDUs from the other switches.

» TC Protect

TC Protect function is used to prevent the switch from frequently removing MAC address entries. It is recommended to enable this function on the ports of non-root switches.

A switch removes MAC address entries upon receiving TC-BPDUs (the packets used to announce changes in the network topology). If a user maliciously sends a large number of TC-BPDUs to a switch in a short period, the switch will be busy with removing MAC address entries, which may decrease the performance and stability of the network.

With TC protect function enabled, if the number of the received TC-BPDUs exceeds the maximum number you set in the TC threshold, the switch will not remove MAC address entries in the TC protect cycle.

2 STP/RSTP Configurations

To complete the STP/RSTP configuration, follow these steps:

1) Configure STP/RSTP parameters on ports.
2) Configure STP/RSTP globally.
3) Verify the STP/RSTP configurations.

Configuration Guidelines

■ Before configuring the spanning tree, it's necessary to make clear the role that each switch plays in a spanning tree.
■ To avoid any possible network flapping caused by STP/RSTP parameter changes, it is recommended to enable STP/RSTP function globally after configuring the relevant parameters.

2.1 Using the GUI

2.1.1 Configuring STP/RSTP Parameters on Ports

Choose the menu L2 FEATURES > Spanning Tree > Port Config to load the following page.

Figure 2-1 Configuring STP/RSTP Parameters on Ports

Follow these steps to configure STP/RSTP parameters on ports:

1) In the Port Config section, configure STP/RSTP parameters on ports.

UNIT Select the desired unit or LAGs.
Status Enable or disable spanning tree function on the desired port.
Priority Specify the Priority for the desired port. The value should be an integral multiple of 16, ranging from 0 to 240.The port with lower value has the higher priority. When the root path of the port is the same as other ports', the switch will compare the port priorities between these port and select a root port with the highest priority.
Ext-Path CostEnter the value of the external path cost. The valid values are from 0 to 2000000. The default setting is Auto, which means the port calculates the external path cost automatically according to the port's link speed.For STP/RSTP, external path cost indicates the path cost of the port in spanning tree. The port with the lowest root path cost will be elected as the root port of the switch.For MSTP, external path cost indicates the path cost of the port in CST.
Int-Path CostEnter the value of the internal path cost. The default setting is Auto, which means the port calculates the internal path cost automatically according to the port's link speed. This parameter is only used in MSTP and you need not to configure it if the spanning tree mode is STP/RSTP.For MSTP, internal path cost is used to calculate the path cost in IST. The port with the lowest root path cost will be elected as the root port of the switch in IST.
Edge Port Select Enable to set the port as an edge port.When the topology is changed, the edge port can transit its state from blocking to forwarding directly. For the quick generation of the spanning tree, it is recommended to set the ports that are connected to the end devices as edge ports.
P2P Link Select the status of the P2P (Point-to-Point) link to which the ports are connected. During the regeneration of the spanning tree, if the port of P2P link is elected as the root port or the designated port, it can transit its state to forwarding directly.Three options are supported: Auto, Open(Force) and Closed(Force). By default, it is Auto.Auto:The switch automatically checks if the port is connected to a P2P link, then sets the status as Open or Closed.Open(Force): A port is set as the one that is connected to a P2P link. You should check the link first.Close(Force): A port is set as the one that is not connected to a P2P link. You should check the link first.

MCheck Select whether to perform MCheck operations on the port. If a port on an

RSTP-enabled/MSTP-enabled device is connected to an STP-enabled device, the port will switch to STP compatible mode and send packets in STP format. MCheck is used to switch the mode of the port back to RSTP/MSTP after the port is disconnected from the STP-enabled device. The MCheck configuration can take effect only once, after that the MCheck status of the port will switch to Disabled.

Port Mode Displays the spanning tree mode of the port.

STP: The spanning tree mode of the port is STP.

RSTP: The spanning tree mode of the port is RSTP.

MSTP: The spanning tree mode of the port is MSTP.

Port Role Displays the role that the port plays in the spanning tree.

Root Port: Indicates that the port is the root port in the spanning tree. It has the lowest path cost from the root bridge to this switch and is used to communicate with the root bridge.

Designated Port: Indicates that the port is the designated port in the spanning tree. It has the lowest path cost from the root bridge to this physical network segment and is used to forward data for the corresponding network segment.

Alternate Port: Indicates that the port is the alternate port in the spanning tree. It is the backup of the root port or master port.

Backup Port: Indicates that the port is the backup port in the spanning tree. It is the backup of the designated port.

Disabled: Indicates that the port is not participating in the spanning tree.

Port Status Displays the port status.

Forwarding: The port receives and sends BPDUs, and forwards user data.

Learning: The port receives and sends BPDUs. It also receives user traffic, but doesn't forward the traffic.

Blocking: The port only receives and sends BPDUs.

Disconnected: The port has the spanning tree function enabled but is not connected to any device.

LAG Displays the LAG the port belongs to.

2) Click Apply.

2.1.2 Configuring STP/RSTP Globally

Choose the menu L2 FEATURES > Spanning Tree > STP Config > STP Config to load the following page.

Figure 2-2 Configuring STP/RSTP Globally
TP-LINK Omada TL-SG2008P - Configuring STP/RSTP Globally - 1

text_image Global Config Spanning Tree: ✓ Enable Mode: STP Parameters Config CIST Priority: 32768 (0-61440, in increments of 4096) Hello Time: 2 seconds (1-10) Max Age: 20 seconds (5-40) Forward Delay: 15 seconds (4-30) Tx Hold Count: 5 pps (1-20) Max Hops: 20 hop (1-40) Apply Apply

Follow these steps to configure STP/RSTP globally:

1) In the Parameters Config section, configure the global parameters of STP/RSTP and click Apply.

CIST PrioritySpecify the CIST priority for the switch. CIST priority is a parameter used to determine the root bridge for spanning tree. The switch with the lower value has the higher priority.In STP/RSTP, CIST priority is the priority of the switch in spanning tree. The switch with the highest priority will be elected as the root bridge.In MSTP, CISP priority is the priority of the switch in CIST. The switch with the higher priority will be elected as the root bridge in CIST.
Hello Time Specify the interval between BPDUs' sending. The default value is 2.The root bridge sends configuration BPDUs at an interval of Hello Time. It works with the MAX Age to test the link failures and maintain the spanning tree.
Max Age Specify the maximum time that the switch can wait without receiving a BPDU before attempting to regenerate a new spanning tree. The default value is 2.
Forward Delay Specify the interval between the port state transition from listening to learning. The default value is 15. It is used to prevent the network from causing temporary loops during the regeneration of spanning tree. The interval between the port state transition from learning to forwarding is also the Forward Delay.
Tx Hold Count Specify the maximum number of BPDU that can be sent in a second. The default value is 5.

Max Hops Specify the maximum BPDU counts that can be forwarded in a MST region.

The default value is 20. A switch receives BPDU, then decrements the hop count by one and generates BPDUs with the new value. When the hop reaches zero, the switch will discard the BPDU. This value can control the scale of the spanning tree in the MST region.

Note: Max Hops is a parameter configured in MSTP. You need not configure it if the spanning tree mode is STP/RSTP.

TP-LINK Omada TL-SG2008P - Configuring STP/RSTP Globally - 2

Note:

To prevent frequent network flapping, make sure that Hello Time, Forward Delay, and Max Age conform to the following formulas:

• 2*(Hello Time + 1) <= Max Age
• 2*(Forward Delay - 1) >= Max Age

2) In the Global Config section, enable spanning tree function, choose the STP mode as STP/RSTP, and click Apply.

Spanning Tree Check the box to enable the spanning tree function globally.

Mode Select the desired spanning tree mode as STP/RSTP on the switch. By default, it's STP.

STP: Specify the spanning tree mode as STP.

RSTP: Specify the spanning tree mode as RSTP.

MSTP: Specify the spanning tree mode as MSTP.

2.1.3 Verifying the STP/RSTP Configurations

Verify the STP/RSTP information of your switch after all the configurations are finished.

Choose the menu L2 FEATURES > Spanning Tree > STP Config > STP Summary to load the following page.

Figure 2-3 Verifying the STP/RSTP Configurations
TP-LINK Omada TL-SG2008P - Verifying the STP/RSTP Configurations - 1

text_image STP Summary Spanning Tree: Enable Spanning Tree Mode: STP Local Bridge: 32768---00-0a-eb-13-a2-02 Root Bridge: 32768---00-0a-eb-13-a2-02 External Path Cost: 0 Regional Root Bridge: --- Internal Path Cost: --- Designated Bridge: 32768---00-0a-eb-13-a2-02 Root Port: --- Latest TC Time: 2006-01-01 08:00:45 TC Count: 0 MSTP Instance Summary Instance ID: Instance Status: Disable Local Bridge: --- Regional Root Bridge: --- Internal Path Cost: --- Designated Bridge: --- Root Port: --- Latest TC Time: --- TC Count: ---

The STP Summary section shows the summary information of spanning tree :

Spanning Tree Displays the status of the spanning tree function.
Spanning Tree Mode Displays the spanning tree mode.
Local BridgeDisplays the bridge ID of the local bridge. The local bridge is the current switch.
Root Bridge Displays the bridge ID of the root bridge.
External Path Cost Displays the root path cost from the switch to the root bridge.
Regional Root BridgeIt is the root bridge of IST. It is not displayed when you choose the spanning tree mode as STP/RSTP.
Internal Path CostThe internal path cost is the root path cost from the switch to the root bridge of IST. It is not displayed when you choose the spanning tree mode as STP/RSTP.
Designated BridgeDisplays the bridge ID of the designated bridge. The designated bridge is the switch that has designated ports.
Root Port Displays the root port of the current switch.
Latest TC Time Displays the latest time when the topology is changed.
TC Count Displays how many times the topology has changed.

2.2 Using the CLI

2.2.1 Configuring STP/RSTP Parameters on Ports

Follow these steps to configure STP/RSTP parameters on ports:

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}

Enter interface configuration mode.

Step 3 spanning-tree

Enable spanning tree function for desired ports.

Step 4 spanning-tree common-config [ port-priority pri ] [ ext-cost ext-cost ] [ portfast { enable | disable }] [ point-to-point { auto | open | close }]

Configure STP/RSTP parameters on the desired port.

pri: Specify the Priority for the desired port. The value should be an integral multiple of 16, ranging from 0 to 240. The default value is 128. Ports with lower values have higher priority. When the root path of the port is the same as other ports', the switch will compare the port priorities and select a root port with the highest priority.

ext-cost: Specify the value of the external path cost. The valid values are from 0 to 2000000 and the default setting is Auto, which means the port calculates the external path cost automatically according to the port's link speed.

For STP/RSTP, external path cost indicates the path cost of the port in spanning tree. The Port with the lowest root path cost will be elected as the root port of the switch.

For MSTP, external path cost indicates the path cost of the port in CST.

portfast { enable | disable }: Enable to set the port as an edge port. By default, it is disabled. When the topology is changed, the edge port can transit its state from blocking to forwarding directly. For the quick generation of the spanning tree, it is recommended to set the ports that are connected to the end devices as edge ports.

point-to-point { auto | open | close }: Select the status of the P2P (Point-to-Point) link to which the ports are connected. During the regeneration of the spanning tree, if the port of P2P link is elected as the root port or the designated port, it can transit its state to forwarding directly. Auto indicates that the switch automatically checks if the port is connected to a P2P link, then sets the status as Open or Closed. Open is used to set the port as the one that is connected to a P2P link. Close is used to set the port as the one that is not connected to a P2P link.

Step 5 spanning-tree mcheck

(Optional) Perform MCheck operations on the port.

If a port on an RSTP-enabled/MSTP-enabled device is connected to an STP-enabled device, the port will switch to STP compatible mode and send packets in STP format. MCheck is used to switch the mode of the port back to RSTP/MSTP after the port is disconnected from the STP-enabled device. The MCheck configuration can take effect only once, after that the MCheck status of the port will switch to Disabled.

Step 6 show spanning-tree interface [fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel lagid] [edge | ext-cost | int-cost | mode | p2p | priority | role | state | status]

(Optional) View the information of all ports or a specified port.

port: Specify the port number.

lagid: Specify the ID of the LAG.

ext-cost | int-cost | mode | p2p | priority | role | state | status: Display the specified information.

Step 7 end

Return to privileged EXEC mode.

Step 8 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable spanning tree function on port 1/0/3 and configure the port priority as 32 :

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/3

Switch(config-if)#spanning-tree

Switch(config-if)#spanning-tree common-config port-priority 32

Switch(config-if)#show spanning-tree interface gigabitEthernet 1/0/3

InterfaceStatePrioExt-CostInt-CostEdgeP2pMode
Gi1/0/3Enable32AutoAutoNoNo(auto)N/A
RoleStatusLAG
N/ALnkDwnN/A

Switch(config-if)#end

Switch#copy running-config startup-config

2.2.2 Configuring Global STP/RSTP Parameters

Follow these steps to configure global STP/RSTP parameters of the switch:

Step 1 configure

Enter global configuration mode.

Step 2 spanning-tree priority pri

Configure the priority of the switch.

pri: Specify the priority for the switch. The valid value is from 0 to 61440, which are divisible by 4096. The priority is a parameter used to determine the root bridge for spanning tree. The switch with the lower value has the higher priority.

In STP/RSTP, the value is the priority of the switch in spanning tree. The switch with the highest priority will be elected as the root bridge.

In MSTP, the value is the priority of the switch in CIST. The switch with the higher priority will be elected as the root bridge in CIST.

Step 3 spanning-tree timer {[ forward-time forward-time] [hello-time hello-time] [max-age max-age]}

(Optional) Configure the Forward Delay, Hello Time and Max Age.

forward-time: Specify the value of Forward Delay. It is the interval between the port state transition from listening to learning. The valid values are from 4 to 30 in seconds, and the default value is 15. Forward Delay is used to prevent the network from causing temporary loops during the regeneration of spanning tree. The interval between the port state transition from learning to forwarding is also the Forward Delay.

hello-time: Specify the value of Hello Time. It is the interval between BPDUs' sending. The valid values are from 1 to 10 in seconds, and the default value is 2. The root bridge sends configuration BPDUs at an interval of Hello Time. It works with the MAX Age to test the link failures and maintain the spanning tree.

max-age: Specify the value of Max Age. It is the maximum time that the switch can wait without receiving a BPDU before attempting to regenerate a new spanning tree. The valid values are from 6 to 40 in seconds, and the default value is 20.

Step 4 spanning-tree hold-count value

Specify the maximum number of BPDU that can be sent in a second.

value: Specify the maximum number of BPDU packets that can be sent in a second. The valid values are from 1 to 20 pps, and the default value is 5.

Step 5 show spanning-tree bridge

(Optional) View the global STP/RSTP parameters of the switch.

Step 6 end

Return to privileged EXEC mode.

Step 7 copy running-config startup-config

Save the settings in the configuration file.

TP-LINK Omada TL-SG2008P - Step 2 spanning-tree priority pri - 1

Note:

To prevent frequent network flapping, make sure that Hello Time, Forward Delay, and Max Age conform to the following formulas:

• 2*(Hello Time + 1) <= Max Age
• 2*(Forward Delay - 1) >= Max Age

This example shows how to configure the priority of the switch as 36864, the Forward Delay as 12 seconds:

Switch#configure

Switch(config)#spanning-tree priority 36864

Switch(config)#spanning-tree timer forward-time 12

Switch(config)#show spanning-tree bridge

StateModePriorityHello-TimeFwd-TimeMax-AgeHold-CountMax-Hops
--------------------------------
EnableRstp3686421220520

Switch(config)#end

Switch#copy running-config startup-config

2.2.3 Enabling STP/RSTP Globally

Follow these steps to configure the spanning tree mode as STP/RSTP, and enable spanning tree function globally:

Step 1 configure

Enter global configuration mode.

Step 2 spanning-tree mode {stp | rstp}

Configure the spanning tree mode as STP/RSTP.

stp: Specify the spanning tree mode as STP.

rstp: Specify the spanning tree mode as RSTP.

Step 3 spanning-tree

Enable spanning tree function globally.

Step 4 show spanning-tree active

(Optional) View the active information of STP/RSTP.

Step 5 end

Return to privileged EXEC mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

This example shows how to enable spanning tree function, configure the spanning tree mode as RSTP and verify the configurations:

Switch#configure

Switch(config)#spanning-tree mode rstp

Switch(config)#spanning-tree

Switch(config)#show spanning-tree active

Spanning tree is enabled

Spanning-tree's mode: RSTP (802.1w Rapid Spanning Tree Protocol)

Latest topology change time: 2006-01-02 10:04:02

Root Bridge

Priority : 32768

Address :00-0a-eb-13-12-ba

Local bridge is the root bridge

Designated Bridge

Priority : 32768

Address :00-0a-eb-13-12-ba

Local Bridge

Priority : 32768

Address :00-0a-eb-13-12-ba

InterfaceStatePrioExt-CostInt-CostEdgeP2pMode
Gi1/0/16Enable128200000200000NoYes(auto)Rstp
Gi1/0/18Enable128200000200000NoYes(auto)Rstp
Gi1/0/20Enable128200000200000NoYes(auto)Rstp

Role Status LAG

Desg Fwd N/A

Desg Fwd N/A

Desg Fwd N/A

Switch(config)#end

Switch#copy running-config startup-config

3 MSTP Configurations

To complete the MSTP configuration, follow these steps:

1) Configure parameters on ports in CIST.
2) Configure the MSTP region.
3) Configure the MSTP globally.
4) Verify the MSTP configurations.

Configuration Guidelines

■ Before configuring the spanning tree, it's necessary to make clear the role that each switch plays in a spanning tree.
■ To avoid any possible network flapping caused by MSTP parameter changes, it is recommended to enable MSTP function globally after configuring the relevant parameter.

3.1 Using the GUI

3.1.1 Configuring Parameters on Ports in CIST

Choose the menu L2 FEATURES > Spanning Tree > Port Config to load the following page.

Figure 3-1 Configuring the Parameters of the Ports
TP-LINK Omada TL-SG2008P - Configuring Parameters on Ports in CIST - 1

text_image Port Config UNIT1 LAGS Port Status Priority Ext-Path Cost Int-Path Cost Edge Port P2P Link MCheck Port Mode Port I ✓ 1/0/1 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/2 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/3 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/4 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/5 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/6 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/7 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/8 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/9 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/10 Disabled 128 Auto Auto Disabled Auto -- -- - Total: 28 1 entry selected. Cancel Aply

Follow these steps to configure parameters on ports in CIST:

1) In the Port Config section, configure the parameters on ports.

UNIT Select the desired unit or LAGs.
Status Enable or disable spanning tree function on the desired port.
Priority Specify the Priority for the desired port. The value should be an integral multiple of 16, ranging from 0 to 240.The port with lower value has the higher priority. When the root path of the port is the same as other ports', the switch will compare the port priorities between these port and select a root port with the highest priority.
Ext-Path CostEnter the value of the external path cost. The default setting is Auto, which means the port calculates the external path cost automatically according to the port's link speed.For STP/RSTP, external path cost indicates the path cost of the port in spanning tree. The port with the lowest root path cost will be elected as the root port of the switch.For MSTP, external path cost indicates the path cost of the port in CST.
Int-Path CostEnter the value of the internal path cost. The valid values are from 0 to 2000000. The default setting is Auto, which means the port calculates the internal path cost automatically according to the port's link speed. This parameter is only used in MSTP and you need not to configure it if the spanning tree mode is STP/RSTP.For MSTP, internal path cost is used to calculate the path cost in IST. The port with the lowest root path cost will be elected as the root port of the switch in IST.
Edge Port Select Enable to set the port as an edge port.When the topology is changed, the edge port can transit its state from blocking to forwarding directly. For the quick generation of the spanning tree, it is recommended to set the ports that are connected to the end devices as edge ports.

P2P Link Select the status of the P2P (Point-to-Point) link to which the ports are

connected. During the regeneration of the spanning tree, if the port of P2P link is elected as the root port or the designated port, it can transit its state to forwarding directly.

Three options are supported: Auto, Open(Force) and Closed(Force). By default, it is Auto.

Auto: The switch automatically checks if the port is connected to a P2P link, then sets the status as Open or Closed.

Open(Force): A port is set as the one that is connected to a P2P link. You should check the link first.

Close(Force): A port is set as the one that is not connected to a P2P link. You should check the link first.

MCheck Select whether to perform MCheck operations on the port. If a port on an

RSTP-enabled/MSTP-enabled device is connected to an STP-enabled device, the port will switch to STP compatible mode and send packets in STP format. MCheck is used to switch the mode of the port back to RSTP/MSTP after the port is disconnected from the STP-enabled device. The MCheck configuration can take effect only once, after that the MCheck status of the port will switch to Disabled.

Port Mode Displays the spanning tree mode of the port.

STP: The spanning tree mode of the port is STP.

RSTP: The spanning tree mode of the port is RSTP.

MSTP: The spanning tree mode of the port is MSTP.

Port Role Displays the role that the port plays in the spanning tree.

Root Port: Indicates that the port is the root port in the spanning tree. It has the lowest path cost from the root bridge to this switch and is used to communicate with the root bridge.

Designated Port: Indicates that the port is the designated port in the spanning tree. It has the lowest path cost from the root bridge to this physical network segment and is used to forward data for the corresponding network segment.

Master Port: Indicates the port provides the lowest root path cost from the region to the root bridge in CIST. In CIST, each region is regarded as a switch, and the master port is the root port of the corresponding region.

Alternate Port: Indicates that the port is the alternate port in the spanning tree. It is the backup of the root port or master port.

Backup Port: Indicates that the port is the backup port in the spanning tree. It is the backup of the designated port.

Disabled: Indicates that the port is not participating in the spanning tree.

Port Status Displays the port status.

Forwarding: The port receives and sends BPDUs, and forwards user data.

Learning: The port receives and sends BPDUs. It also receives user traffic, but doesn't forward the traffic.

Blocking: The port only receives and sends BPDUs.

Disconnected: The port has the spanning tree function enabled but is not connected to any device.

LAG Displays the LAG the port belongs to.

2) Click Apply.

3.1.2 Configuring the MSTP Region

Configure the region name, revision level, VLAN-Instance mapping of the switch. The switches with the same region name, the same revision level and the same VLAN-Instance mapping are considered as in the same region.

Besides, configure the priority of the switch, the priority and path cost of ports in the desired instance.

■ Configuring the Region Name and Revision Level

Choose the menu L2 FEATURES > Spanning Tree > MSTP Instance > Region Config to load the following page.

Figure 3-2 Configuring the Region
TP-LINK Omada TL-SG2008P - Configuring the MSTP Region - 1

text_image Region Config Region Name: 00-0a-eb-13-a2-02 Revision: 0 (0-65535) Apply

Follow these steps to create an MST region:

1) In the Region Config section, set the name and revision level to specify an MSTP region.

Region Name Configure the name for an MST region using up to 32 characters. By default, it is the MAC address of the switch.

Revision Enter the revision level. By default, it is 0.

2) Click Apply.

■ Configuring the VLAN-Instance Mapping and Switch Priority

Choose the menu L2 FEATURES > Spanning Tree > MSTP Instance > Instance Config to load the following page.

Figure 3-3 Configuring the VLAN-Instance Mapping

Instance Config
+ Add - Delete
Instance IDPriorityVLAN IDOperation
CIST368641-4094,
Total: 1

Follow these steps to map VLANs to the corresponding instance, and configure the priority of the switch in the desired instance:

1) In the Instance Config section, click Add and enter the instance ID, Priority and corresponding VLAN ID.

Figure 3-4 Configuring the Instance
TP-LINK Omada TL-SG2008P - Configuring the MSTP Region - 2

text_image Instance Config Instance ID: (1-8) Priority: (0-61440, in increments of 4096) VLAN ID: Add Delete (1-4094, format:1,3,4-7,11-30) Cancel Create

Instance ID Enter the corresponding instance ID.

Priority Specify the priority for the switch in the corresponding instance. The value should be an integral multiple of 4096, ranging from 0 to 61440. It is used to determine the root bridge for the instance. Switches with a lower value have higher priority, and the switch with the highest priority will be elected as the root bridge in the corresponding instance.

VLAN ID Enter the VLAN ID to map the VLAN to the desired instance or unbind the VLAN-instance mapping.

2) Click Create.

■ Configuring Parameters on Ports in the Instance

Choose the menu L2 FEATURES > Spanning Tree > MSTP Instance > Instance Port Config to load the following page.

Figure 3-5 Configuring Port Parameters in the Instance
TP-LINK Omada TL-SG2008P - ■ Configuring Parameters on Ports in the Instance - 1

text_image Instance Port Config Instance ID: 1 UNIT1 LAGS Port Priority Path Cost Port Role Port Status LAG ✓ 1/0/1 128 Auto -- -- --- □ 1/0/2 128 Auto -- -- --- □ 1/0/3 128 Auto -- -- --- □ 1/0/4 128 Auto -- -- --- □ 1/0/5 128 Auto -- -- --- □ 1/0/6 128 Auto -- -- --- □ 1/0/7 128 Auto -- -- --- □ 1/0/8 128 Auto -- -- --- □ 1/0/9 128 Auto -- -- --- □ 1/0/10 128 Auto -- -- --- Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure port parameters in the instance:

1) In the Instance Port Config section, select the desired instance ID.

Instance ID Select the ID number of the instance that you want to configure.

2) Configure port parameters in the desired instance.

UNIT Select the desired unit or LAGs for configuration.

Priority Specify the Priority for the port in the corresponding instance. The value should be an integral multiple of 16, ranging from 0 to 240.

The port with lower value has the higher priority. When the root path of the port is the same as other ports', the switch will compare the port priorities between these ports and select a root port with the highest priority.

Path Cost Enter the value of the path cost in the corresponding instance. The valid values are from 0 to 2000000. The default setting is Auto, which means the port calculates the external path cost automatically according to the port's link speed. The port with the lowest root path cost will be elected as the root port of the switch.

Port Role Displays the role that the port plays in the desired instance.

Root Port: Indicates that the port is the root port in the desired instance. It has the lowest path cost from the root bridge to this switch and is used to communicate with the root bridge.

Designated Port: Indicates that the port is the designated port in the desired instance. It has the lowest path cost from the root bridge to this physical network segment and is used to forward data for the corresponding network segment.

Alternate Port: Indicates that the port is the alternate port in the desired instance. It is the backup of the root port or master port.

Backup Port: Indicates that the port is the backup port in the desired instance. It is the backup of the designated port.

Master Port: Indicates the port provides the lowest root path cost from the region to the root bridge in CIST. In CIST, each region is regarded as a switch, and the master port is the root port of the corresponding region.

Disabled: Indicates that the port is not participating in the spanning tree.

Port Status Displays the port status.

Forwarding: The port receives and sends BPDUs, and forwards user traffic.

Learning: The port receives and sends BPDUs. It also receives user traffic, but doesn't forward the traffic.

Blocking: The port only receives and sends BPDUs.

Disconnected: The port has the spanning tree function enabled but is not connected to any device.

LAG Displays the LAG which the port belongs to.

3.1.3 Configuring MSTP Globally

Choose the menu L2 FEATURES > Spanning Tree > STP Config > STP Config to load the following page.

Figure 3-6 Configure MSTP Function Globally
TP-LINK Omada TL-SG2008P - Configuring MSTP Globally - 1

text_image Global Config Spanning Tree: ✓ Enable Mode: MSTP Parameters Config CIST Priority: 36864 (0-61440, in increments of 4096) Hello Time: 2 seconds (1-10) Max Age: 20 seconds (6-40) Forward Delay: 12 seconds (4-30) Tx Hold Count: 5 pps (1-20) Max Hops: 20 hop (1-40) Apply Apply

Follow these steps to configure MSTP globally:

1) In the Parameters Config section, Configure the global parameters of MSTP and click Apply.

CIST PrioritySpecify the CIST priority for the switch. CIST priority is a parameter used to determine the root bridge for spanning tree. The switch with the lower value has the higher priority.In STP/RSTP, CIST priority is the priority of the switch in spanning tree. The switch with the highest priority will be elected as the root bridge.In MSTP, CISP priority is the priority of the switch in CIST. The switch with the higher priority will be elected as the root bridge in CIST.
Hello Time Specify the interval between BPDUs' sending. The default value is 2. The root bridge sends configuration BPDUs at an interval of Hello Time. It works with the MAX Age to test the link failures and maintain the spanning tree.
Max Age Specify the maximum time that the switch can wait without receiving a BPDU before attempting to regenerate a new spanning tree. The default calue is 20.

Forward Delay Specify the interval between the port state transition from listening to

learning. The default value is 15. It is used to prevent the network from causing temporary loops during the regeneration of spanning tree. The interval between the port state transition from learning to forwarding is also the Forward Delay.

Tx Hold Count Specify the maximum number of BPDU that can be sent in a second. The

default value is 5.

Max Hops Specify the maximum BPDU hop counts that can be forwarded in a MST

region. The default value is 20. A switch receives BPDU, then decrements the hop count by one and generates BPDUs with the new value. When the hop reaches zero, the switch will discard the BPDU. This value can control the scale of the spanning tree in the MST region.

Note: Max Hops is a parameter configured in MSTP. You need not configure

it if the spanning tree mode is STP/RSTP.

TP-LINK Omada TL-SG2008P - Configuring MSTP Globally - 2

Note:

To prevent frequent network flapping, make sure that Hello Time, Forward Delay, and Max Age conform to the following formulas:

• 2*(Hello Time + 1) <= Max Age
• 2*(Forward Delay - 1) >= Max Age

2) In the Global Config section, enable Spanning-Tree function and choose the STP mode as MSTP and click Apply.

Spanning-Tree Check the box to enable the spanning tree function globally.

Mode Select the desired spanning tree mode as STP/RSTP on the switch. By default, it's STP.

STP: Specify the spanning tree mode as STP.

RSTP: Specify the spanning tree mode as RSTP.

MSTP: Specify the spanning tree mode as MSTP.

3.1.4 Verifying the MSTP Configurations

Choose the menu Spanning Tree > STP Config > STP Summary to load the following page.

Figure 3-7 Verifying the MSTP Configurations

STP Summary
Spanning Tree:Enable
Spanning Tree Mode:MSTP
Local Bridge:36864---00-0a-eb-13-a2-02
Root Bridge:36864---00-0a-eb-13-a2-02
External Path Cost:0
Regional Root Bridge:36864---00-0a-eb-13-a2-02
Internal Path Cost:0
Designated Bridge:36864---00-0a-eb-13-a2-02
Root Port:---
Latest TC Time:2006-01-01 08:00.45
TC Count:0
MSTP Instance Summary
Instance ID:
Instance Status:Disable
Local Bridge:---
Regional Root Bridge:---
Internal Path Cost:---
Designated Bridge:---
Root Port:---
Latest TC Time:---
TC Count:---

The STP Summary section shows the summary information of CIST:

Spanning Tree Displays the status of the spanning tree function.
Spanning-Tree Mode Displays the spanning tree mode.
Local BridgeDisplays the bridge ID of the local switch. The local bridge is the current switch.
Root Bridge Displays the bridge ID of the root bridge in CIST.
External Path CostDisplays the external path cost. It is the root path cost from the switch to the root bridge in CIST.
Regional Root Bridge Displays the bridge ID of the root bridge in IST.
Internal Path CostDisplays the internal path cost. It is the root path cost from the current switch to the root bridge in IST.
Designated Bridge Displays the bridge ID of the designated bridge in CIST.
Root Port Displays the root port of in CIST.
Latest TC Time Displays the latest time when the topology is changed.
TC Count Displays how many times the topology has changed.
The MSTP Instance Summary section shows the information in MST instances:
Instance ID Select the desired instance.
Instance Status Displays the status of the desired instance.
Local BridgeDisplays the bridge ID of the local switch. The local bridge is the current switch.
Regional Root Bridge Displays the bridge ID of the root bridge in the desired instance.
Internal Path CostDisplays the internal path cost. It is the root path cost from the current switch to the regional root bridge.
Designated Bridge Displays the bridge ID of the designated bridge in the desired instance.
Root Port Displays the root port of the desired instance.
Latest TC Time Displays the latest time when the topology is changed.
TC Count Displays how many times the topology has changed.

3.2 Using the CLI

3.2.1 Configuring Parameters on Ports in CIST

Follow these steps to configure the parameters of the port in CIST:

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}

Enter interface configuration mode.

Step 3 spanning-tree

Enable spanning tree function for the desired port.

Step 4 spanning-tree common-config [ port-priority pri ] [ ext-cost ext-cost ] [ int-cost int-cost ][ portfast { enable | disable } ] [ point-to-point { auto | open | close } ]

Configure the parameters on ports in CIST.

pri: Specify the Priority for the desired port. The value should be an integral multiple of 16, ranging from 0 to 240. The default value is 128. Ports with lower values have higher priority. When the root path of the port is the same as other ports', the switch will compare the port priorities and select a root port with the highest priority.

ext-cost: Specify the value of the external path cost. The valid values are from 0 to 2000000 and the default setting is Auto, which means the port calculates the external path cost automatically according to the port's link speed.

For STP/RSTP, external path cost indicates the path cost of the port in spanning tree. The Port with the lowest root path cost will be elected as the root port of the switch.

For MSTP, external path cost indicates the path cost of the port in CST.

int-cost: Specify the value of the internal path cost. The valid values are from 0 to 2000000. The default setting is Auto, which means the port calculates the internal path cost automatically according to the port's link speed. This parameter is only used in MSTP.

For MSTP, internal path cost is used to calculate the path cost in IST. The port with the lowest root path cost will be elected as the root port of the switch in IST.

portfast { enable | disable }: Enable to set the port as an edge port. By default, it is disabled. When the topology is changed, the edge port can transit its state from blocking to forwarding directly. For the quick generation of the spanning tree, it is recommended to set the ports that are connected to the end devices as edge ports.

point-to-point { auto | open | close }: Select the status of the P2P (Point-to-Point) link to which the ports are connected. During the regeneration of the spanning tree, if the port of P2P link is elected as the root port or the designated port, it can transit its state to forwarding directly. Auto indicates that the switch automatically checks if the port is connected to a P2P link, then sets the status as Open or Closed. Open is used to set the port as the one that is connected to a P2P link. Close is used to set the port as the one that is not connected to a P2P link.

Step 5 spanning-tree mcheck

(Optional) Perform MCheck operations on the port.

If a port on an RSTP-enabled/MSTP-enabled device is connected to an STP-enabled device, the port will switch to STP compatible mode and send packets in STP format. MCheck is used to switch the mode of the port back to RSTP/MSTP after the port is disconnected from the STP-enabled device. The MCheck configuration can take effect only once, after that the MCheck status of the port will switch to Disabled.

Step 6show spanning-tree interface [ fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel lagid ] [ edge | ext-cost | int-cost | mode | p2p | priority | role | state | status ](Optional) View the information of all ports or a specified port.port: Specify the port number.lagid: Specify the ID of the LAG.ext-cost | int-cost | mode | p2p | priority | role | state | status: Display the specified information.
Step 7 endReturn to privileged EXEC mode.
Step 8 copy running-config startup-configSave the settings in the configuration file.

This example shows how to enable spanning tree function for port 1/0/3 and configure the port priority as 32 :

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/3

Switch(config-if)#spanning-tree

Switch(config-if)#spanning-tree common-config port-priority 32

Switch(config-if)#show spanning-tree interface gigabitEthernet 1/0/3

MST-Instance 0 (CIST)

InterfaceStatePrioExt-CostInt-CostEdgeP2pModeRoleStatus
Gi1/0/3Enable32AutoAutoNoNo(auto)N/AN/ALnkDwn

MST-Instance 5

InterfacePrio CostRoleStatus
Gi1/0/3144 200N/ALnkDwn

Switch(config-if)#end

Switch#copy running-config startup-config

3.2.2 Configuring the MSTP Region

■ Configuring the MST Region

Follow these steps to configure the MST region and the priority of the switch in the instance:

Step 1 configure

Enter global configuration mode.

Step 2 spanning-tree mst instance

instance-id priority pri

Configure the priority of the switch in the instance.

instance-id: Specify the instance ID, the valid values ranges from 1 to 8.

pri: Specify the priority for the switch in the corresponding instance. The value should be an integral multiple of 4096, ranging from 0 to 61440. The default value is 32768. It is used to determine the root bridge for the instance. Switches with a lower value have higher priority, and the switch with the highest priority will be elected as the root bridge in the corresponding instance.

Step 3 spanning-tree mst configuration

Enter MST configuration mode, as to configure the VLAN-Instance mapping, region name and revision level.

Step 4 name

name

Configure the region name of the region.

name: Specify the region name, used to identify an MST region. The valid values are from 1 to 32 characters.

Step 5 revision

revision

Configure the revision level of the region.

revision: Specify the revision level of the region. The valid values are from 0 to 65535.

Step 6 instance

instance-id vlan vlan-id

Configure the VLAN-Instance mapping.

instance-id: Specify the Instance ID. The valid values are from 1 to 8.

vlan-id: Specify the VLAN mapped to the corresponding instance.

Step 7

show spanning-tree mst { configuration [digest] | instance instance-id [interface [ fastEthernet port | gigabitEthernet port | port-channel lagid | ten-gigabitEthernet port] ] }

(Optional) View the related information of MSTP Instance.

digest: Specify to display the digest calculated by instance-vlan map.

instance-id: Specify the Instance ID desired to view, ranging from 1 to 8.

port: Specify the port number.

lagid: Specify the ID of the LAG.

Step 8 end

Return to privileged EXEC mode.

Step 9 copy running-config startup-config

Save the settings in the configuration file.

This example shows how to create an MST region, of which the region name is R1, the revision level is 100 and VLAN 2-VLAN 6 are mapped to instance 5:

Switch#configure

Switch(config)#spanning-tree mst configuration

Switch(config-mst)#name R1

Switch(config-mst)#revision 100

Switch(config-mst)#instance 5 vlan 2-6

Switch(config-mst)#show spanning-tree mst configuration

Region-Name: R1

Revision : 100

MST-Instance Vlans-Mapped

0 1,7-4094

5 2-6,

Switch(config-mst)#end

Switch#copy running-config startup-config

■ Configuring the Parameters on Ports in Instance

Follow these steps to configure the priority and path cost of ports in the specified instance:

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}

Enter interface configuration mode.

Step 3 spanning-tree mst instanceinstance-id { [ port-priority pri ] | [ cost cost] }Configure the priority and path cost of ports in the specified instance.
instance-id: Specify the instance ID, the valid values ranges from 1 to 8.
pri: Specify the Priority for the port in the corresponding instance. The value should be an integral multiple of 16, ranging from 0 to 240. The default valueis 128. The port with lower value has the higher priority. When the root path of the port is the same as other ports', the switch will compare the port priorities between these ports and select a root port with the highest priority.
cost: Enter the value of the path cost in the corresponding instance. The valid values are from 0 to 2000000. The default setting is Auto, which means the port calculates the external path cost automatically according to the port's link speed. The port with the lowest root path cost will be elected as the root port of the switch.
Step 4show spanning-tree mst { configuration [ digest ] | instance instance-id [ interface [ fastEthernet port | gigabitEthernet port | port-channel lagid | ten-gigabitEthernet port ]]} (Optional) View the related information of MSTP Instance.
digest: Specify to display the digest calculated by instance-vlan map.
instance-id: Specify the Instance ID desired to view, ranging from 1 to 8.
port: Specify the port number.
lagid: Specify the ID of the LAG.
Step 5 endReturn to privileged EXEC mode.
Step 6 copy running-config startup-config

This example shows how to configure the priority as 144, the path cost as 200 of port 1/0/3 in instance 5:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/3

Switch(config-if)#spanning-tree mst instance 5 port-priority 144 cost 200

Switch(config-if)#show spanning-tree interface gigabitEthernet 1/0/3

MST-Instance 0 (CIST)

InterfaceStatePrioExt-CostInt-CostEdgeP2pModeRoleStatusLAG
Gi1/0/3Enable32AutoAutoNoNo(auto)N/AN/ALnkDwnN/A
MST-Instance 5
InterfacePrioCostRoleStatusLAG
Gi1/0/3144200N/ALnkDwnN/A

Switch(config-if)#end

Switch#copy running-config startup-config

3.2.3 Configuring Global MSTP Parameters

Follow these steps to configure the global MSTP parameters of the switch:

Step 1 configure

Enter global configuration mode.

Step 2 spanning-tree priority pri

Configure the priority of the switch for comparison in CIST.

pri: Specify the priority for the switch. The valid value is from 0 to 61440, which are divisible by 4096. The priority is a parameter used to determine the root bridge for spanning tree. The switch with the lower value has the higher priority.

In STP/RSTP, the value is the priority of the switch in spanning tree. The switch with the highest priority will be elected as the root bridge.

In MSTP, the value is the priority of the switch in CIST. The switch with the higher priority will be elected as the root bridge in CIST.

Step 3 spanning-tree timer {[ forward-time forward-time ] [ hello-time hello-time ] [ max-age max-age }}

(Optional) Configure the Forward Delay, Hello Time and Max Age.

forward-time: Specify the value of Forward Delay. It is the interval between the port state transition from listening to learning. The valid values are from 4 to 30 in seconds, and the default value is 15. Forward Delay is used to prevent the network from causing temporary loops during the regeneration of spanning tree. The interval between the port state transition from learning to forwarding is also the Forward Delay.

hello-time: Specify the value of Hello Time. It is the interval between BPDUs' sending. The valid values are from 1 to 10 in seconds, and the default value is 2. The root bridge sends configuration BPDUs at an interval of Hello Time. It works with the MAX Age to test the link failures and maintain the spanning tree.

max-age: Specify the value of Max Age. It is the maximum time that the switch can wait without receiving a BPDU before attempting to regenerate a new spanning tree. The valid values are from 6 to 40 in seconds, and the default value is 20.

Step 4 spanning-tree hold-count value

(Optional) Specify the maximum number of BPDU that can be sent in a second.

value: Specify the maximum number of BPDU packets that can be sent in a second. The valid values are from 1 to 20 pps, and the default value is 5.

Step 5 spanning-tree max-hops value

(Optional) Specify the maximum BPDU hop counts that can be forwarded in a MST region. A switch receives BPDU, then decrements the hop count by one and generates BPDUs with the new value. When the hop reaches zero, the switch will discard the BPDU. This value can control the scale of the spanning tree in the MST region.

value: Specify the maximum number of hops that occur in a specific region before the BPDU is discarded. The valid values are from 1 to 40 in hop, and the default value is 20.

Step 6 show spanning-tree bridge

(Optional) View the global parameters of the switch.

Step 7 end

Return to privileged EXEC mode.

Step 8 copy running-config startup-config

Save the settings in the configuration file.

TP-LINK Omada TL-SG2008P - Step 4 spanning-tree hold-count value - 1

Note:

To prevent frequent network flapping, make sure that Hello Time, Forward Delay, and Max Age conform to the following formulas:

• 2*(Hello Time + 1) <= Max Age
• 2*(Forward Delay - 1) >= Max Age

This example shows how to configure the CIST priority as 36864, the Forward Delay as 12 seconds, the Hold Count as 8 and the Max Hop as 25:

Switch#configure

Switch(config)#spanning-tree priority 36864

Switch(config-if)#spanning-tree timer forward-time 12

Switch(config-if)#spanning-tree hold-count 8

Switch(config-if)#spanning-tree max-hops 25

Switch(config-if)#show spanning-tree bridge

StateModePriorityHello-TimeFwd-TimeMax-AgeHold-CountMax-Hops
--------------------------------
EnableMstp3686421220825

Switch(config-if)#end

Switch#copy running-config startup-config

3.2.4 Enabling Spanning Tree Globally

Follow these steps to configure the spanning tree mode as MSTP and enable spanning tree function globally:

Step 1 configure

Enter global configuration mode.

Step 2 spanning-tree mode mstp

Configure the spanning tree mode as MSTP.

mstp: Specify the spanning tree mode as MSTP.

Step 3 spanning-tree

Enable spanning tree function globally.

Step 4 show spanning-tree active

(Optional) View the active information of MSTP.

Step 5 end

Return to privileged EXEC mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

This example shows how to configure the spanning tree mode as MSTP and enable spanning tree function globally:

Switch#configure

Switch(config)#spanning-tree mode mstp

Switch(config)#spanning-tree

Switch(config)#show spanning-tree active

Spanning tree is enabled

Spanning-tree's mode: MSTP (802.1s Multiple Spanning Tree Protocol)

Latest topology change time: 2006-01-04 10:47:42

MST-Instance 0 (CIST)

Root Bridge

Priority : 32768

Address : 00-0a-eb-13-23-97

External Cost: 200000

Root Port : Gi/0/20

Designated Bridge

Priority : 32768

Address : 00-0a-eb-13-23-97

Regional Root Bridge

Priority : 36864

Address :00-0a-eb-13-12-ba

Local bridge is the regional root bridge

Local Bridge

Priority : 36864

Address : 00-0a-eb-13-12-ba

InterfaceStatePrioExt-CostInt-CostEdgeP2pModeRoleStatus
Gi/0/16Enable128200000200000NoYes(auto)MstpAltnBlk
Gi/0/20Enable128200000200000NoYes(auto)MstpRootFwd

MST-Instance 1

Root Bridge

Priority : 32768

Address : 00-0a-eb-13-12-ba

Local bridge is the root bridge

Designated Bridge

Priority : 32768

Address :00-0a-eb-13-12-ba

Local Bridge

Priority : 32768

Address :00-0a-eb-13-12-ba

Interface Prio Cost Role Status

Gi/0/16 128 200000 Altn Blk

Gi/0/20 128 200000 Mstr Fwd

Switch(config)#end

Switch#copy running-config startup-config

4 STP Security Configurations

4.1 Using the GUI

Choose the menu L2 FEATURES > Spanning Tree > STP Security to load the following page.

Figure 4-1 Configuring the Port Protect
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Port Protect UNIT1 LAGS Port Loop Protect Root Protect TC Guard BPDU Protect BPDU Filter BPDU Forward LAG ✓ 1/0/1 Disabled Disabled Disabled Disabled Disabled Enabled --- □ 1/0/2 Disabled Disabled Disabled Disabled Disabled Enabled --- □ 1/0/3 Disabled Disabled Disabled Disabled Disabled Enabled --- □ 1/0/4 Disabled Disabled Disabled Disabled Disabled Enabled --- □ 1/0/5 Disabled Disabled Disabled Disabled Disabled Enabled --- □ 1/0/6 Disabled Disabled Disabled Disabled Disabled Enabled --- □ 1/0/7 Disabled Disabled Disabled Disabled Disabled Enabled --- □ 1/0/8 Disabled Disabled Disabled Disabled Disabled Enabled --- □ 1/0/9 Disabled Disabled Disabled Disabled Disabled Enabled --- □ 1/0/10 Disabled Disabled Disabled Disabled Disabled Enabled --- Total: 28 1 entry selected. Cancel Apply

Configure the Port Protect features for the selected ports, and click Apply.

UNIT Select the desired unit or LAGs for configuration.

Loop Protect

Enable or disable Loop Protect. It is recommended to enable this function on root ports and alternate ports.

When there are link congestions or link failures in the network, the switch will not receive BPDUs from the upstream device in time. Loop Protect is used to avoid loop caused by the recalculation in this situation. With Loop Protect function enabled, the port will temporarily transit to a blocking state after it does not receive BPDUs in time.

Root ProtectEnable or disable Root Protect. It is recommended to enable this function on the designated ports of the root bridge.Switches with faulty configurations may produce a higher-priority BPDUs than the root bridge's, and this situation will cause recalculation of the spanning tree. Root Protect is used to ensure that the desired root bridge will not lose its position in the scenario above. With root protect enabled, the port will temporarily transit to blocking state when it receives higher-priority BDPUs. After two forward delays, if the port does not receive any other higher-priority BDPUs, it will transit to its normal state.
TC Guard Enable or disable the TC Guard function. It is recommended to enable this function on the ports of non-root switches.TC Guard function is used to prevent the switch from frequently changing the MAC address table. With TC Guard function enabled, when the switch receives TC-BPDUs, it will not process the TC-BPDUs at once. The switch will wait for a fixed time and process the TC-BPDUs together after receiving the first TC-BPDU, then it will restart timing.
BPDU ProtectEnable or disable the BPDU Protect function. It is recommended to enable this function on edge ports.Edge ports in spanning tree are used to connect to the end devices and it doesn't receive BPDUs in the normal situation. If edge ports receive BPDUs, it may be an attack. BPDU Protect is used to protect the switch from the attack talked above. With BPDU protect function enabled, the edge ports will be shutdown when they receives BPDUs, and will report these cases to the administrator. Only the administrator can restore the state of the ports.
BPDU FilterEnable or disable BPDU Filter. It is recommended to enable this function on edge ports.With the BPDU Filter function enabled, the port does not forward BPDUs from the other switches.
BPDU Forward Enable or disable BPDU Forward. This function only takes effect when the spanning tree function is disabled globally.With BPDU forward enabled, the port can still forward spanning tree BPDUs when the spanning tree function is disabled.

4.2 Using the CLI

4.2.1 Configuring the STP Security

Follow these steps to configure the Root protect feature, BPDU protect feature and BPDU filter feature for ports:

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}

Enter interface configuration mode.

Step 3 spanning-tree guard loop

(Optional) Enable Loop Protect. It is recommended to enable this function on root ports and alternate ports.

When there are link congestions or link failures in the network, the switch will not receive BPDUs from the upstream device in time. Loop Protect is used to avoid loop caused by the recalculation in this situation. With Loop Protect function enabled, the port will temporarily transit to a blocking state after it does not receive BPDUs in time.

Step 4 spanning-tree guard root

(Optional) Enable Root Protect. It is recommended to enable this function on the designated ports of the root bridge.

Switches with faulty configurations may produce a higher-priority BPDUs than the root bridge's, and this situation will cause recalculation of the spanning tree. Root Protect is used to ensure that the desired root bridge will not lose its position in the scenario above. With root protect enabled, the port will temporarily transit to blocking state when it receives higher-priority BDPUs. After two forward delays, if the port does not receive any other higher-priority BDPUs, it will transit to its normal state.

Step 5 spanning-tree guard tc

(Optional) Enable the TC Guard function. It is recommended to enable this function on the ports of non-root switches.

TC Guard function is used to prevent the switch from frequently changing the MAC address table. With TC Guard function enabled, when the switch receives TC-BPDUs, it will not process the TC-BPDUs at once. The switch will wait for a fixed time and process the TC-BPDUs together after receiving the first TC-BPDU, then it will restart timing.

Step 6 spanning-tree bpduguard

(Optional) Enable the BPDU Protect function. It is recommended to enable this function on edge ports.

Edge ports in spanning tree are used to connect to the end devices and it doesn't receive BPDUs in the normal situation. If edge ports receive BPDUs, it may be an attack. BPDU Protect is used to protect the switch from the attack talked above. With BPDU protect function enabled, the edge ports will be shutdown when they receive BPDUs, and will report these cases to the administrator. Only the administrator can restore the state of the ports.

Step 7 spanning-tree bpdufilter

(Optional) Enable or disable BPDU Filter. It is recommended to enable this function on edge ports.

With the BPDU Filter function enabled, the port does not forward BPDUs from the other switches.

Step 8 spanning-tree bpduflood(Optional) Enable BPDU Forward. This function only takes effect when the spanning tree function is disabled globally. By default, it is enabled.With BPDU forward enabled, the port can still forward spanning tree BPDUs when the spanning tree function is disabled.
Step 9show spanning-tree interface-security [ fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel port-channel-id ] [ bpdufilter | bpduguard | bpduflood | loop | root | tc ](Optional) View the protect information of ports.port: Specify the port number.lagid: Specify the ID of the LAG.
Step 10 endReturn to privileged EXEC mode.
Step 11 copy running-config startup-configSave the settings in the configuration file.

This example shows how to enable Loop Protect, Root Protect, BPDU Filter and BPDU Protect functions on port 1/0/3:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/3

Switch(config-if)#spanning-tree guard loop

Switch(config-if)#spanning-tree guard root

Switch(config-if)#spanning-tree bpdufilter

Switch(config-if)#spanning-tree bpduguard

Switch(config-if)#show spanning-tree interface-security gigabitEthernet 1/0/3

5 Configuration Example for MSTP

MSTP, backwards-compatible with STP and RSTP, can map VLANs to instances to implement load-balancing, thus providing a more flexible method in network management. Here we take the MSTP configuration as an example.

5.1 Network Requirements

As shown in figure 5-1, the network consists of three switches. Traffic in VLAN 101-VLAN 106 is transmitted in this network. The link speed between the switches is 100Mb/s (the default path cost of the port is 200000).

It is required that traffic in VLAN 101 - VLAN 103 and traffic in VLAN 104 - VLAN 106 should be transmitted along different paths.

Figure 5-1 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["Switch A\nMAC: 00-0A-EB-13-23-97"] -->|200000 Gi1/0/1| B["Switch B\nMAC: 00-0A-EB-13-12-97"]
    A -->|200000 Gi1/0/2| C["Switch C\nMAC: 3C-46-D8-9D-88-F7"]
    B -->|200000 Gi1/0/2| C

5.2 Configuration Scheme

To meet this requirement, you are suggested to configure MSTP function on the switches. Map the VLANs to different instances to ensure traffic can be transmitted along the respective instance.

Here we configure two instances to meet the requirement, as is shown below:

Figure 5-2 VLAN-Instance Mapping
TP-LINK Omada TL-SG2008P - Configuration Scheme - 1

flowchart
graph TD
    SwitchA["Switch A"] -->|Gi1/0/1| SwitchB["Switch B"]
    SwitchA -->|Gi1/0/2| SwitchC["Switch C"]
    SwitchB -->|Gi1/0/1 Gi1/0/1| SwitchA
    SwitchB -->|Gi1/0/2 Gi1/0/2| SwitchC
    SwitchA -.->|Instance 1: VLAN 101 -VLAN 103| SwitchB
    SwitchA -.->|Instance 2: VLAN 104 -VLAN 106| SwitchC
    SwitchA -.->|Blocked Port| SwitchA

The overview of configuration is as follows:

1) Enable MSTP function globally in all the switches.
2) Enable Spanning Tree function on the ports in each switch.
3) Configure Switch A, Switch B and Switch C in the same region. Configure the region name as 1, and the revision level as 100. Map VLAN 101 - VLAN 103 to instance 1 and VLAN 104 - VLAN 106 to instance 2.
4) Configure the priority of Switch B as 0 to set it as the root bridge in instance 1; configure the priority of Switch C as 0 to set it as the root bridge in instance 2.
5) Configure the path cost to block the specified ports. For instance 1, set the path cost of port 1/0/1 of Switch A to be greater than the default path cost (200000); for instance 2, set the path cost of port 1/0/2 of Switch B to be greater than the default path cost (200000). After this configuration, port 1/0/2 of Switch A in instance 1 and port 1/0/1 of Switch B in instance 2 will be blocked for they cannot be neither root port nor designated port.

TP-LINK Omada TL-SG2008P - Configuration Scheme - 2

Note:

Please configure MSTP for each switch first and then connect them together to avoid broadcast storm.

5.3 Using the GUI

■ Configurations for Switch A

1) Choose the menu L2 FEATURES > Spanning Tree > STP Config > STP Config to load the following page. Enable MSTP function globally, here we leave the values of the other global parameters as default settings. Click Apply.

Figure 5-3 Configure the Global MSTP Parameters of the Switch
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch A - 1

text_image Global Config Spanning Tree: ✓ Enable Mode: MSTP Apply Parameters Config CIST Priority: 32768 (0-61440, in increments of 4096) Hello Time: 2 seconds (1-10) Max Age: 20 seconds (5-40) Forward Delay: 15 seconds (4-30) Tx Hold Count: 5 pps (1-20) Max Hops: 20 (1-40) Apply

2) Choose the menu L2 FEATURES > Spanning Tree > STP Config > Port Config to load the following page. Enable spanning tree function on port 1/0/1 and port 1/0/2. Here we leave the values of the other parameters as default settings. Click Apply.

Figure 5-4 Enable Spanning Tree Function on Ports
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch A - 2

text_image Port Config UNIT1 LAGS Port Status Priority Ext-Path Cost Int-Path Cost Edge Port P2P Link MCheck Port Mode Port I Enable ▼ ✓ 1/0/1 Enabled 128 Auto Auto Disabled Auto -- -- - ✓ 1/0/2 Enabled 126 Auto Auto Disabled Auto -- -- - □ 1/0/3 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/4 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/5 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/6 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/7 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/8 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/9 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/10 Disabled 128 Auto Auto Disabled Auto -- -- - Total: 28 2 entries selected. Cancel Apply

3) Choose the menu L2 FEATURES > Spanning Tree > MSTP Instance > Region Config to load the following page. Set the region name as 1 and the revision level as 100. Click Apply.

Figure 5-5 Configuring the MST Region
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch A - 3

text_image Region Config Region Name: 1 Revision: 100 (0-65535) Apply

4) Choose the menu L2 FEATURES > Spanning Tree > MSTP Instance > Instance Config. Click Add, map VLAN101-VLAN103 to instance 1 and set the priority as 32768; map VLAN104-VLAN106 to instance 2 and set the priority as 32768. Click Create.

Figure 5-6 Configuring the VLAN-Instance Mapping
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch A - 4

text_image Instance Config + Add - Delete Instance ID Priority VLAN ID Operation CIST 32768 1-100,107-4094, 1 32768 101-103, 2 32768 104-106, Total: 3

5) Choose the menu L2 FEATURES > Spanning Tree > MSTP Instance > Instance Port Config to load the following page. Set the path cost of port 1/0/1 in instance 1 as 300000 so that port 1/0/1 of switch C can be selected as the designated port.

Figure 5-7 Configure the Path Cost of Port 1/0/1 In Instance 1
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch A - 5

text_image Instance Port Config Instance ID: 1 UNIT1 LAGS Port Priority Path Cost Port Role Port Status LAG 128 300000 ✓ 1/0/1 126 Auto -- - --- □ 1/0/2 126 Auto -- - --- □ 1/0/3 126 Auto -- - --- □ 1/0/4 126 Auto -- - --- □ 1/0/5 126 Auto -- - --- □ 1/0/6 126 Auto -- - --- □ 1/0/7 126 Auto -- - --- □ 1/0/8 126 Auto -- - --- □ 1/0/9 126 Auto -- - --- □ 1/0/10 126 Auto -- - --- Total: 28 1 entry selected. Cancel Apply

6) Click Save the settings.

■ Configurations for Switch B

1) Choose the menu L2 FEATURES > Spanning Tree > STP Config > STP Config to load the following page. Enable MSTP function globally, here we leave the values of the other global parameters as default settings. Click Apply.

Figure 5-8 Configure the Global MSTP Parameters of the Switch
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch B - 1

text_image Global Config Spanning Tree: ✓ Enable Mode: MSTP Apply Parameters Config CIST Priority: 32768 (0-61440, in increments of 4096) Hello Time: 2 seconds (1-10) Max Ago: 20 seconds (6-40) Forward Delay: 15 seconds (4-30) Tx Hold Count: 5 pps (1-20) Max Hops: 20 (1-40) Apply

2) Choose the menu L2 FEATURES > Spanning Tree > STP Config > Port Config to load the following page. Enable the spanning tree function on port 1/0/1 and port 1/0/2. Here we leave the values of the other parameters as default settings. Click Apply.

Figure 5-9 Enable Spanning Tree Function on Ports
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch B - 2

text_image Port Config UNIT1 LAGS Port Status Priority Ext-Path Cost Int-Path Cost Edge Port P2P Link MCheck Port Mode Port I Enabl▼ ✓ 1/0/1 Enabled 128 Auto Auto Disabled Auto -- -- - ✓ 1/0/2 Enabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/3 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/4 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/5 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/6 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/7 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/8 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/9 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/10 Disabled 128 Auto Auto Disabled Auto -- -- - Total: 20 2 entries selected. Cancel Apply

3) Choose the menu L2 FEATURES > Spanning Tree > MSTP Instance > Region Config to load the following page. Set the region name as 1 and the revision level as 100. Click Apply.

Figure 5-10 Configuring the Region
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch B - 3

text_image Region Config Region Name: 1 Revision: 100 (0-65535) Apply

4) Choose the menu L2 FEATURES > Spanning Tree > MSTP Instance > Instance Config. Map VLAN101-VLAN103 to instance 1 and set the Priority as 0; map VLAN104-VLAN106 to instance 2 and set the priority as 32768. Click Create.

Figure 5-11 Configuring the VLAN-Instance Mapping
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch B - 4

text_image Instance Config + Add Delete Instance ID Priority VLAN ID Operation CIST 32768 1-100,107-4094, 1 0 101-103, 2 32768 104-106. Total: 3

5) Choose the menu L2 FEATURES > Spanning Tree > MSTP Instance > Instance Port Config to load the following page. Set the path cost of port 1/0/2 in instance 2 as 300000 so that port 1/0/1 of switch A can be selected as the designated port.

Figure 5-12 Configure the Path Cost of Port 1/0/2 in Instance 2
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch B - 5

text_image Instance Port Config Instance ID: 2 UNIT1 LAGS Port Priority Path Cost Port Role Port Status LAG 300000 1/0/1 128 Auto -- -- -- ✓ 1/0/2 128 Auto -- -- -- 1/0/3 128 Auto -- -- -- 1/0/4 128 Auto -- -- -- 1/0/5 128 Auto -- -- -- 1/0/6 128 Auto -- -- -- 1/0/7 128 Auto -- -- -- 1/0/8 128 Auto -- -- -- 1/0/9 128 Auto -- -- -- 1/0/10 128 Auto -- -- Total: 16 1 entry selected. Cancel Apply

6) Click Save the settings.

■ Configurations for Switch C

1) Choose the menu L2 FEATURES > Spanning Tree > STP Config > STP Config to load the following page. Enable MSTP function globally, here we leave the values of the other global parameters as default settings. Click Apply.

Figure 5-13 Configure the Global MSTP Parameters of the Switch
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch C - 1

text_image Global Config Spanning Tree: ✓ Enable Mode: MSTP Apply Parameters Config CIST Priority: 32768 (0-61440, in increments of 4096) Hello Time: 2 seconds (1-10) Max Ago: 20 seconds (6-40) Forward Delay: 15 seconds (4-30) Tx Hold Count: 5 pps (1-20) Max Hops: 20 (1-40) Apply

2) Choose the menu L2 FEATURES > Spanning Tree > STP Config > Port Config to load the following page. Enable the spanning tree function on port 1/0/1 and port 1/0/2. Here we leave the values of the other parameters as default settings. Click Apply.

Figure 5-14 Enable Spanning Tree Function on Ports
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch C - 2

text_image Port Config UNIT1 LAGS Port Status Priority Ext-Path Cost Int-Path Cost Edge Port P2P Link MCheck Port Mode Port I Enabl▼ ✓ 1/0/1 Enabled 128 Auto Auto Disabled Auto -- -- - ✓ 1/0/2 Enabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/3 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/4 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/5 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/6 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/7 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/8 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/9 Disabled 128 Auto Auto Disabled Auto -- -- - □ 1/0/10 Disabled 128 Auto Auto Disabled Auto -- -- - Total: 20 2 entries selected. Cancel Apply

3) Choose the menu Spanning Tree > MSTP Instance > Region Config to load the following page. Set the region name as 1 and the revision level as 100. Click Apply.

Figure 5-15 Configuring the Region
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch C - 3

text_image Region Config Region Name: 1 Revision: 100 (0-65535) Apply

4) Choose the menu L2 FEATURES > Spanning Tree > MSTP Instance > Instance Config. Click Add, map VLAN101-VLAN103 to instance 1 and set the priority as 32768; map VLAN104-VLAN106 to instance 2 and set the priority as 0. Click Create.

Figure 5-16 Configuring the VLAN-Instance Mapping
TP-LINK Omada TL-SG2008P - ■ Configurations for Switch C - 4

text_image Instance Config Instance ID Priority VLAN ID Operation CIST 32768 1-100,107-4094, 1 32768 101-103, 2 0 104-106, Total: 3

5) Click Save the settings.

5.4 Using the CLI

■ Configurations for Switch A

1) Configure the spanning tree mode as MSTP, then enable spanning tree function globally.

Switch#configure

Switch(config)#spanning-tree mode mstp

Switch(config)#spanning-tree

2) Enable the spanning tree function on port 1/0/1 and port 1/0/2, and specify the path cost of port 1/0/1 in instance 1 as 300000.

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#spanning-tree

Switch(config-if)#spanning-tree mst instance 1 cost 300000

Switch(config-if)#exit

Switch(config)#interface gigabitEthernet 1/0/2

Switch(config-if)#spanning-tree

Switch(config-if)#exit

3) Configure the region name as 1, the revision number as 100; map VLAN101-VLAN103 to instance 1; map VLAN104-VLAN106 to instance 2:

Switch(config)#spanning-tree mst configuration

Switch(config-mst)#name 1

Switch(config-mst)#revision 100

Switch(config-mst)#instance 1 vlan 101-103

Switch(config-mst)#instance 2 vlan 104-106

Switch(config-mst)#end

Switch#copy running-config startup-config

■ Configurations for Switch B

1) Configure the spanning tree mode as MSTP, then enable spanning tree function globally.

Switch#configure

Switch(config)#spanning-tree mode mstp

Switch(config)#spanning-tree

2) Enable the spanning tree function on port 1/0/1 and port 1/0/2, and specify the path cost of port 1/0/2 in instance 2 as 300000.

Switch(config)#interface gigabitEthernet 1/0/2

Switch(config-if)#spanning-tree

Switch(config-if)#spanning-tree mst instance 2 cost 300000

Switch(config-if)#exit

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#spanning-tree

Switch(config-if)#exit

3) Configure the region name as 1, the revision number as 100; map VLAN101-VLAN103 to instance 1; map VLAN104-VLAN106 to instance 2; configure the priority of Switch B in instance 1 as 0 to set it as the root bridge in instance 1:

Switch(config)#spanning-tree mst configuration

Switch(config-mst)#name 1

Switch(config-mst)#revision 100

Switch(config-mst)#instance 1 vlan 101-103

Switch(config-mst)#instance 2 vlan 104-106

Switch(config-mst)#exit

Switch(config)#spanning-tree mst instance 1 priority 0

Switch(config)#end

Switch#copy running-config startup-config

■ Configurations for Switch C

1) Configure the spanning tree mode as MSTP, then enable spanning tree function globally.

Switch#configure

Switch(config)#spanning-tree mode mstp

Switch(config)#spanning-tree

2) Enable the spanning tree function on port 1/0/1 and port 1/0/2.

Switch(config)#interface range gigabitEthernet 1/0/1-2

Switch(config-if-range)#spanning-tree

Switch(config-if-range)#exit

3) Configure the region name as 1, the revision number as 100; map VLAN101-VLAN103 to instance 1; map VLAN104-VLAN106 to instance 2; configure the priority of Switch C in instance 2 as 0 to set it as the root bridge in instance 2:

Switch(config)#spanning-tree mst configuration

Switch(config-mst)#name 1

Switch(config-mst)#revision 100

Switch(config-mst)#instance 1 vlan 101-103

Switch(config-mst)#instance 2 vlan 104-106

Switch(config-mst)#exit

Switch(config)#spanning-tree mst instance 2 priority 0

Switch(config)#end

Switch#copy running-config startup-config

Verify the Configurations

Switch A

Verify the configurations of Switch A in instance 1:

Switch(config)#show spanning-tree mst instance 1

MST-Instance 1

Root Bridge

Priority : 0

Address : 00-0a-eb-13-12-ba

Internal Cost : 400000

Root Port : 1

Designated Bridge

Priority : 0

Address : 00-0a-eb-13-12-ba

Local Bridge

Priority : 32768

Address :00-0a-eb-13-23-97

InterfacePrioCostRoleStatusLAG
------------------------
Gi1/0/1128300000RootFwdN/A
Gi1/0/2128200000AltnBlkN/A

Verify the configurations of Switch A in instance 2:

Switch(config)#show spanning-tree mst instance 2

MST-Instance 2

Root Bridge

Priority : 0

Address : 3c-46-d8-9d-88-f7

Internal Cost : 200000

Root Port : 2

Designated Bridge

Priority : 0

Address : 3c-46-d8-9d-88-f7

Local Bridge

Priority : 32768

Address : 00-0a-eb-13-23-97

Interface Prio Cost Role Status LAG


Gi1/0/1 128 200000 Desg Fwd N/A

Gi1/0/2 128 200000 Root Fwd N/A

Switch B

Verify the configurations of Switch B in instance 1:

Switch(config)#show spanning-tree mst instance 1

MST-Instance 1

Root Bridge

Priority : 0

Address : 00-0a-eb-13-12-ba

Local bridge is the root bridge

Designated Bridge

Priority : 0

Address :00-0a-eb-13-12-ba

Local Bridge

Priority : 0

Address : 00-0a-eb-13-12-ba

Interface Prio Cost Role Status

Gi1/0/1 128 200000 Desg Fwd

Gi1/0/2 128 200000 Desg Fwd

Verify the configurations of Switch B in instance 2:

Switch(config)#show spanning-tree mst instance 2

MST-Instance 2

Root Bridge

Priority : 0

Address : 3c-46-d8-9d-88-f7

Internal Cost : 400000

Root Port : 2

Designated Bridge

Priority : 0

Address : 3c-46-d8-9d-88-f7

Local Bridge

Priority : 32768

Address : 00-0a-eb-13-12-ba

Interface Prio Cost Role Status

Gi1/0/1 128 200000 Altn Blk

Gi1/0/2 128 300000 Root Fwd

Switch C

Verify the configurations of Switch C in instance 1:

Switch(config)#show spanning-tree mst instance 1

MST-Instance 1

Root Bridge

Priority : 0

Address :00-0a-eb-13-12-ba

Internal Cost : 200000

Root Port : 2

Designated Bridge

Priority : 0

Address : 00-0a-eb-13-12-ba

Local Bridge

Priority : 32768

Address : 3c-46-d8-9d-88-f7

Interface Prio Cost Role Status

Gi1/0/1 128 200000 Desg Fwd

Gi1/0/2 128 200000 Root Fwd

Verify the configurations of Switch C in instance 2:

Switch(config)#show spanning-tree mst instance 2

MST-Instance 2

Root Bridge

Priority : 0

Address : 3c-46-d8-9d-88-f7

Local bridge is the root bridge

Designated Bridge

Priority : 0

Address : 3c-46-d8-9d-88-f7

Local Bridge

Priority : 0

Address : 3c-46-d8-9d-88-f7

Interface Prio Cost Role Status

Gi1/0/1 128 200000 Desg Fwd

Gi1/0/2 128 200000 Desg Fwd

6

Appendix: Default Parameters

Default settings of the Spanning Tree feature are listed in the following table.

Table 6-1 Default Settings of the Global Parameters

Parameter Default Setting
Spanning-tree Disabled
Mode STP
CIST Priority 32768
Hello Time 2 seconds
Max Age 20 seconds
Forward Delay 15 seconds
Tx Hold Count 5 pps
Max Hops 20 hops

Table 6-2 Default Settings of the Port Parameters

Parameter Default Setting
Status Disabled
Priority 128
Ext-Path Cost Auto
In-Path Cost Auto
Edge Port Disabled
P2P Link Auto
MCheck----

Table 6-3 Default Settings of the MSTP Instance

Parameter Default Setting
Status Disabled
Revision Level 0
Priority 32768
Port Priority 128
Path Cost Auto

Table 6-4 Default Settings of the STP Security

Parameter Default Setting
Loop Protect Disabled
Root Protect Disabled
TC Guard Disabled
BPDU Protect Disabled
BPDU Filter Disabled
BPDU Forward Enabled

Part 15

Configuring LLDP

CHAPTERS

  1. LLDP
  2. LLDP Configurations
  3. LLDP-MED Configurations
  4. Viewing LLDP Settings
  5. Viewing LLDP-MED Settings
  6. Configuration Example
  7. Appendix: Default Parameters

1 LLDP

1.1 Overview

LLDP (Link Layer Discovery Protocol) is a neighbor discovery protocol that is used for network devices to advertise information about themselves to other devices on the network. This protocol is a standard IEEE 802.1ab defined protocol and runs over the Layer 2 (the data-link layer), which allows for interoperability between network devices of different vendors.

With LLDP enabled, the switch can get its neighbors' information, and network administrators can use the NMS (Network Management System) to gather these information, helping them to know about the network topology, examine the network connectivity and troubleshoot the network faults.

LLDP-MED (LLDP for Media Endpoint Discovery) is an extension of LLDP and is used to advertise information between network devices and media endpoints. It is specially used together with Auto VoIP (Voice over Internet Protocol) to allow VoIP device to access the network. VoIP devices can use LLDP-MED for auto-configuration to minimize the configuration effort.

1.2 Supported Features

The switch supports LLDP and LLDP-MED.

LLDP allows the local device to encapsulate its management address, device ID, interface ID and other information into a LLDPDU (Link Layer Discovery Protocol Data Unit) and periodically advertise this LLDPDU to its neighbor devices. The neighbors store the received LLDPDU in a standard MIB (Management Information Base), making it possible for the information to be accessed by a NMS (Network Management System) using a management protocol such as the SNMP (Simple Network Management Protocol).

LLDP-MED allows the network device to send its information including Auto VoIP information, PoE (Power over Ethernet) capacity and more to the media endpoint devices (for example, IP phones) for auto-configuration. The media endpoint devices receive the Auto VoIP information and finish the auto-configuration, then send the voice traffic with the desired configuration, which can provide preferential treatment to the voice traffic.

2 LLDP Configurations

T configure LLDP function, follow the steps:

1) Configure the LLDP feature globally.
2) Configure the LLDP feature for the port.

2.1 Using the GUI

2.1.1 Configuring LLDP Globally

Choose the L2 FEATURES > LLDP > LLDP Config > Global Config to load the following page.

Figure 2-1 Global Config
TP-LINK Omada TL-SG2008P - Configuring LLDP Globally - 1

text_image Global Config LLDP: □ Enable LLDP Forwarding: □ Enable Parameter Config Apply Transmit Interval: 30 seconds (5-32768) Hold Multiplier: 4 (2-10) Transmit Delay: 2 seconds (1-8192) Reinitialization Delay: 2 seconds (1-10) Notification Interval: 5 seconds (5-3600) Fast Start Repeat Count: 3 (1-10) Apply

Follow these steps to configure the LLDP feature globally.

1) In the Global Config section, enable LLDP. You can also enable the switch to forward LLDP messages when LLDP function is disabled. Click Apply.

LLDP Enable LLDP function globally.

LLDP (Optional) Enable the switch to forward LLDP messages when LLDP function is forwarding disabled.

3) In the Parameter Config section, configure the LLDP parameters. Click Apply.

Transmit IntervalEnter the interval between successive LLDP packets that are periodically sent from the local device to its neighbors. The default is 30 seconds.
Hold MultiplierThis parameter is a multiplier on the Transmit Interval that determines the actual TTL (Time To Live) value used in an LLDP packet. TTL is the duration that the neighbor device should hold the received LLDP packet before discarding it. The default value is 4.TTL= Hold Multiplier * Transmit Interval.
Transmit DelaySpecify the amount of delay from when Admin Status of ports becomes “Disable” until reinitialization will be attempted. The default value is 2 seconds.
Reinitialization DelaySpecify the amount of delay from when Admin Status of ports becomes “Disable” until reinitialization will be attempted. The default value is 2 seconds.
Notification IntervalEnter the interval between successive in seconds Trap messages that are periodically sent from the local device to the NMS. The default value is 5.
Fast Start Repeat CountSpecify the number of LLDP packets that the local port sends when its Admin Status changes from Disable (or Rx_Only) to Tx&RX (or Tx_Only). The default value is 3.In this case, the local device will shorten the Transmit Interval of LLDP packets to 1 second to make it quickly discovered by its neighbors. After the specified number of LLDP packets are sent, the Transmit Interval will be restored to the specified value.

2.1.2 Configuring LLDP For the Port

Choose th menu L2 FEATURES > LLDP > LLDP Config > Port Config to load the following page.

Figure 2-2 Port Config
Port Config
TP-LINK Omada TL-SG2008P - Configuring LLDP For the Port - 1

text_image UNIT1 Port Admin Status Notification Mode Management Address Included TLVs ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ 1/0/1 Tx & Rx Disabled PD SC SD SN SA PVVP VA LA PS F5 PW 1/0/2 Tx & Rx Disabled PD SC SD SN SA PVVP VA LA PS F5 PW 1/0/3 Tx & Rx Disabled PD SC SD SN SA PVVP VA LA PS F5 PW 1/0/4 Tx & Rx Disabled PD SC SD SN SA PVVP VA LA PS F5 PW 1/0/5 Tx & Rx Disabled PD SC SD SN SA PVVP VA LA PS F5 PW 1/0/6 Tx & Rx Disabled PD SC SD SN SA PVVP VA LA PS F5 PW 1/0/7 Tx & Rx Disabled PD SC SD SN SA PVVP VA LA PS F5 PW 1/0/8 Tx & Rx Disabled PD SC SD SN SA PVVP VA LA PS F5 PW 1/0/9 Tx & Rx Disabled PD SC SD SN SA PVVP VA LA PS F5 PW 1/0/10 Tx & Rx Disabled PD SC SD SN SA PVVP VA LA PS F5 PW Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure the LLDP feature for the interface.

1) Select one or more ports to configure.
2) Configure the Admin Status and Notification Mode for the port.

Admin Status Set Admin Status for the port to deal with LLDP packets.

Tx&Rx: The port transmits LLDP packets and receives LLDP packets.

Rx_Only: The port only receives LLDP packets.

Tx_Only: The port only transmits LLDP packets.

Disable: The port will not transmit LLDP packets or drop the received LLDP packets.

Notification Mode(Optional) Enable the switch to send trap messages to the NMS when the information of the neighbor device connected to this port changes.
Management AddressSpecify the Management IP address of the port to be notified to the neighbor. Value 0.0.0.0 means the port will notify its default management address to the neighbor.

3) Select the TLVs (Type/Length/Value) included in the LLDP packets according to your needs.

Included TLVs Configure the TLVs included in the outgoing LLDP packets.

The switch supports the following TLVs:

PD: Used to advertise the port description defined by the IEEE 802 LAN station.

SC: Used to advertise the supported functions and whether or not these functions are enabled.

SD: Used to advertise the system's description including the full name and version identification of the system's hardware type, software operating system, and networking software.

SN: Used to advertise the system name.

SA: Used to advertise the local device's management address to make it possible to be managed by SNMP.

PV: Used to advertise the 802.1Q VLAN ID of the port.

VP: Used to advertise the protocol VLAN ID of the port.

VA: Used to advertise the name of the VLAN which the port is in.

LA: Used to advertise whether the link is capable of being aggregated, whether the link is currently in an aggregation, and the port ID when it is in an aggregation.

PS: Used to advertise the port's attributes including the duplex and bit-rate capability of the sending IEEE 802.3 LAN node that is connected to the physical medium, the current duplex and bit-rate settings of the sending IEEE 802.3 LAN node and whether these settings are the result of auto-negotiation during link initiation or of manual set override action.

FS: Used to advertise the maximum frame size capability of the implemented MAC and PHY.

PW: Used to advertise the port's PoE (Power over Ethernet) support capabilities.

4) Click Apply.

2.2 Using the CLI

2.2.1 Global Config

Enable the LLDP feature on the switch and configure the LLDP parameters.

Step 1 configure

Enter global configuration mode.

Step 2 lldp

Enable the LLDP feature on the switch.

Step 3 lldp forward\_message

(Optional) Enable the switch to forward LLDP messages when LLDP function is disabled.

Step 4 lldp hold-multiplier multiplier

(Optional) Specify the amount of time the neighbor device should hold the received information before discarding it. This parameter is a multiplier on the Transmit Interval that determines the actual TTL (Time To Live) value used in an LLDP packet. TTL is the duration that the neighbor device should hold the received LLDP packet before discarding it.

TTL= Hold Multiplier * Transmit Interval.

multiplier: Specify the hold-multiplier. The valid value ranges from 2 to 10, and the default value is 4.

Step 5 lldp timer { tx-interval tx-interval | tx-delay tx-delay | reinit-delay reinit-delay | notify-interval notify-interval | fast-count fast-count }

(Optional) Configure the timers for LLDP packet forwarding.

tx-interval: Enter the interval between successive LLDP packets that are periodically sent from the local device to its neighbors.

tx-delay: Specify the amount of time that the local device waits before sending another LLDP packet to its neighbors. The default is 2 seconds.

reinit-delay: Specify the amount of time that the local device waits before sending another LLDP packet to its neighbors. The default is 2 seconds.

notify-interval: Enter the interval between successive Trap messages that are periodically sent from the local device to the NMS. The default is 5 seconds.

fast-count: Specify the number of packets that the local port sends when its Admin Status changes. The default is 3.

Step 6 show lldp

Display the LLDP information.

Step 7 end

Return to Privileged EXEC Mode.

Step 8 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to configure the following parameters, lldp timer=4, tx-interval=30 seconds, tx-delay=2 seconds, reinit-delay=3 seconds, notify-ilinterval=5 seconds, fast-count=3.

Switch#configure

Switch(config)#lldp

Switch(config)#lldp hold-multiplier 4

Switch(config)#lldp timer tx-interval 30 tx-delay 2 reinit-delay 3 notify-interval 5 fast-count 3

Switch(config)#show lldp

LLDP Status: Enabled

LLDP Forward Message: Disabled

Tx Interval: 30 seconds

TTL Multiplier: 4

Tx Delay: 2 seconds

Initialization Delay: 2 seconds

Trap Notification Interval: 5 seconds

Fast-packet Count: 3

LLDP-MED Fast Start Repeat Count: 4

Switch(config)#end

Switch#copy running-config startup-config

2.2.2 Port Config

Select the desired port and set its Admin Status, Notification Mode and the TLVs included in the LLDP packets.

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet

port | range fastEthernet port-list | gigabitEthernet port | range

gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list ]

Enter interface configuration mode.

Step 3 lldp receive

(Optional) Set the mode for the port to receive LLDP packets. It is enabled by default.

Step 4 lldp transmit

(Optional) Set the mode for the port to send LLDP packets. It is enabled by default.

Step 5 lldp snmp-trap

(Optional) Enable the Notification Mode feature on the port. If it is enabled, the local device will send trap messages to the NMS when neighbor information changed. It is disabled by default.

Step 6 lldp tlv-select

(Optional) Configure the TLVs included in the outgoing LLDP packets. By default, the outgoing LLDP packets include all TLVs.

Step 7 show lldp interface { fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port }Display LLDP configuration of the corresponding port.
Step 8 endReturn to Privileged EXEC Mode.
Step 9 copy running-config startup-configSave the settings in the configuration file.

The following example shows how to configure the port 1/0/1. The port can receive and transmit LLDP packets, its notification mode is enabled and the outgoing LLDP packets include all TLVs.

Switch#configure

Switch(config)#lldp

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#lldp receive

Switch(config-if)#lldp transmit

Switch(config-if)#lldp snmp-trap

Switch(config-if)#lldp tlv-select all

Switch(config-if)#show lldp interface gigabitEthernet 1/0/1

LLDP interface config:

gigabitEthernet 1/0/1:

Admin Status: TxRx

SNMP Trap: Enabled

TLV Status

Port-Description Yes

System-Capability Yes

System-Description Yes

System-Name Yes

Management-Address Yes

Port-VLAN-ID Yes

Protocol-VLAN-ID Yes

VLAN-Name Yes

Link-Aggregation Yes

MAC-Physic Yes

Max-Frame-Size Yes

Power Yes

Switch(config-if)#end

Switch#copy running-config startup-config

3 LLDP-MED Configurations

To configure LLDP-MED function, follow the steps:

1) Enable LLDP feature globally and configure the LLDP parametres for the ports.
2) Configuring LLDP-MED fast repeat count globally.
3) Enable and configure the LLDP-MED feature on the port.

Configuration Guidelines

LLDP-MED is used together with Auto VoIP to implement VoIP access. Besides the configuration of LLDP-MED feature, you also need configure the Auto VoIP feature. Refer to Configuring QoS for detailed instructions.

3.1 Using the GUI

3.1.1 Configuring LLDP Globally

Enable LLDP globally and configure the LLDP parametres for the ports. For the details of LLDP configuration, refer to LLDP Configuration.

3.1.1 Configuring LLDP-MED Globally

Choose the menu L2 FEATURES > LLDP Config > LLDP-MED Config > Global Config to load the following page.

Figure 3-1 LLDP-MED Parameters Config
TP-LINK Omada TL-SG2008P - Configuring LLDP-MED Globally - 1

text_image LLDP-MED Parameters Config Fast Start Repeat Count: 4 (1-10) Device Class: Network Connectivity Apply

Configure the Fast Start Count and view the current device class. Click Apply.

Fast Start Repeat CountSpecify the number of successive LLDP-MED packets that the switch sends when it receives the LLDP-MED packets from the neighbor endpoints. The default is 4.
If the switch receives LLDP-MED packets from the neighbor endpoints for the first time, it will send the specified number of LLDP-MED packets carrying LLDP-MED information. After that, the transmit interval will be restored to the specified value.

Device Class Display the current device class.

LLDP-MED defines two device classes, Network Connectivity Device and Endpoint Device. The switch is a Network Connectivity device.

3.1.2 Configuring LLDP-MED for Ports

Choose the menu L2 FEATURES > LLDP > LLDP-MED Config > Port Config to load the following page.

Figure 3-2 LLDP-MED Port Config
TP-LINK Omada TL-SG2008P - Configuring LLDP-MED for Ports - 1

text_image Port Config UNIT1 Port LLDP-MED Status Included TLVs ✓ 1/0/1 Disabled Detail □ 1/0/2 Disabled Detail □ 1/0/3 Disabled Detail □ 1/0/4 Disabled Detail □ 1/0/5 Disabled Detail □ 1/0/6 Disabled Detail □ 1/0/7 Disabled Detail □ 1/0/8 Disabled Detail □ 1/0/9 Disabled Detail □ 1/0/10 Disabled Detail Total: 28 1 entry selected. Cancel Apply

Follow these steps to enable LLDP-MED:

1) Select the desired port and enable LLDP-MED. Click Apply.
2) Click Detail to enter the following page. Configure the TLVs included in the outgoing LLDP packets. If Location Identification is selected, you need configure the Emergency Number or select Civic Address to configure the details. Click Apply.

Figure 3-3 LLDP-MED Port Config-Detail
TP-LINK Omada TL-SG2008P - Configuring LLDP-MED for Ports - 2

text_image Included TLVs Detail(Port:1/0/1) Included TLVs ✓ All ✓ Network Policy ✓ Location Identification ✓ Extended Power-Via-MDI ✓ Inventory Location Identification Parameters ○ Emergency Number ○ Civic Address (Parameters in total should not exceed 230 characters in length) What: Switch Country Code: CN China(Default) Language: Province/State: City/Township: County/Parish/District: Street: House Number: Name: Postal/Zip Code: Room Number: Cancel Save
Network PolicyUsed to advertise VLAN configuration and the associated Layer 2 and Layer 3 attributes of the port to the endpoint devices.
Location IdentificationUsed to assign the location identifier information to the Endpoint devices.If this option is selected, you can configure the emergency number and the detailed address of the endpoint device in the Location Identification Parameters section.
Extended Power-Via-MDIUsed to advertise the detailed PoE information including power supply priority and supply status between LLDP-MED Endpoint devices and Network Connectivity devices.
Inventory Used to advertise the inventory information. The Inventory TLV set contains seven basic Inventory management TLVs, that is, Hardware Revision TLV, Firmware Revision TLV, Software Revision TLV, Serial Number TLV, Manufacturer Name TLV, Model Name TLV and Asset ID TLV.
Emergency NumberConfigure the emergency number to call CAMA or PSAP. The number should contain 10-25 characters.

Civic Address Configure the address of the audio device in the IETF defined address format.

What: Specify the role type of the local device, DHCP Server, Switch or LLDP-MED Endpoint.

Country Code: Enter the country code defined by ISO 3166, for example, CN, US.

Language, Province/State etc.: Enter the regular details.

3.2 Using the CLI

3.2.1 Global Config

Step 1 configure

Enter global configuration mode.

Step 2 lldp

Enable the LLDP feature on the switch.

Step 3 lldp med-fast-count

count

(Optional) Specify the number of successive LLDP-MED frames that the local device sends when fast start mechanism is activated. When the fast start mechanism is activated, the local device will send the specified number of LLDP packets carrying LLDP-MED information.

count: The valid value are from 1 to 10. The default is 4.

Step 4 show lldp

Display the LLDP information.

Step 5 end

Return to Privileged EXEC Mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to configure LLDP-MED fast count as 4:

Switch#configure

Switch(config)#lldp

Switch(config)#lldp med-fast-count 4

Switch(config)#show lldp

LLDP Status:

Enabled

Tx Interval:

30 seconds

TTL Multiplier: 4

Tx Delay: 2 seconds

Initialization Delay: 2 seconds

Trap Notification Interval: 5 seconds

Fast-packet Count: 3

LLDP-MED Fast Start Repeat Count: 4

Switch(config)#end

Switch#copy running-config startup-config

3.2.2 Port Config

Select the desired port, enable LLDP-MED and select the TLVs (Type/Length/Value) included in the outgoing LLDP packets according to your needs.

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list ] Enter interface configuration mode.

Step 3 lldp med-status

(Optional) Enable the LLDP-MED on the port. It is disabled by default.

Step 4 lldp med-tlv-select { [inventory-management] [location] [network-policy] [power-management] [all] }

(Optional) Configure the LLDP-MED TLVs included in the outgoing LLDP packets. By default, the outgoing LLDP packets include all TLVs.

If LLDP-MED Location TLV is selected, configure the parameters as follows:

lldp med-location {emergency-number identifier | civic-address [language language | province-state province-state | lci-county-name county | lci-city city | street street | house-number house-number | name name | postal-zipcode postal-zipcode | room-number room-number | post-office-box post-office-box | additional additional | country-code country-code | what { dhcp-server | endpoint | switch }}

Configure the LLDP-MED Location TLV included in the outgoing LLDP packets. Used to assign the location identifier information to the Endpoint devices.

identifier: Configure the emergency number to call CAMA or PSAP. The number should contain 10-25 characters.

language, province-state, county.etc: Configure the address in the IETF defined address format.

Step 5 show lldp interface { fastEthernet

port | gigabitEthernet port | ten-gigabitEthernet port }

Display LLDP configuration of the corresponding port.

Step 6 end

Return to Privileged EXEC Mode.

Step 7 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable LLDP-MED on port 1/0/1, configure the LLDP-MED TLVs included in the outgoing LLDP packets.

Switch(config)#lldp

Switch(config)#lldp med-fast-count 4

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#lldp med-status

Switch(config-if)#lldp med-tlv-select all

Switch(config-if)#show lldp interface gigabitEthernet 1/0/1

LLDP interface config:

gigabitEthernet 1/0/1:

Admin Status: TxRx

SNMP Trap: Enabled

TLV Status

Port-Description Yes

System-Capability Yes

System-Description Yes

System-Name Yes

Management-Address Yes

Port-VLAN-ID Yes

Protocol-VLAN-ID Yes

VLAN-Name Yes

Link-Aggregation Yes

MAC-Physic Yes

Max-Frame-Size Yes

Power Yes

LLDP-MED Status: Enabled

TLV Status


Network Policy Yes

Location Identification Yes

Extended Power Via MDI Yes

Inventory Management Yes

Switch(config)#end

Switch#copy running-config startup-config

4 Viewing LLDP Settings

This chapter introduces how to view the LLDP settings on the local device.

4.1 Using GUI

4.1.1 Viewing LLDP Device Info

■ Viewing the Local Info

Choose the menu L2 FEATURES > LLDP > LLDP Config > Local Info to load the following page.

Figure 4-1 Local Info
TP-LINK Omada TL-SG2008P - Viewing LLDP Device Info - 1

Follow these steps to view the local information:

1) In the Auto Refresh section, enable the Auto Refresh feature and set the Refresh Rate according to your needs. Click Apply.
2) In the Local Info section, select the desired port and view its associated local device information.

Local Interface Displays the local port ID.

Chassis ID Subtype Displays the Chassis ID type.

Chassis ID Displays the value of the Chassis ID.

Port ID Subtype Displays the Port ID type.

Port ID Displays the value of the Port ID.

TTL Specify the amount of time in seconds the neighbor device should hold the received information before discarding it.

Port Description Displays the description of the local port.

System Name Displays the system name of the local device.

System Description Displays the system description of the local device.

System Capabilities Displays the supported capabilities of the local system. Supported

System Capabilities Enabled Displays the primary functions of the local device.

Management Address Type Displays the management IP address type of the local device.

Management Address Displays the management IP address of the local device.

Management Displays the interface numbering type that is used to define the interface ID. Address Interface Type

Management Address Interface ID Displays the interface ID that is used to identify the specific interface associated with the MAC address of the local device.

Management Address OID Displays the OID (Object Identifier) of the local device. A value of 0 means that the OID is not provided.

Port VLAN ID(PVID) Displays the PVID of the local port.

Port And Protocol Displays the PPVID of the local port. VLAN ID(PPVID)

Port And Protocol SupportedDisplays whether the local device supports port and protocol VLAN feature.
Port And Protocol VLAN EnabledDisplays the status of the port and protocol VLAN feature.
VLAN Name of VLAN 1Displays the VLAN name of VLAN 1 for the local device.
Protocol Identify Displays the particular protocol that the local device wants to advise.
Auto-negotiation SupportedDisplays whether the local device supports auto-negotiation.
Auto-Negotiation EnableDisplays the status of auto-negotiation for the local device.
OperMau Displays the OperMau (Optional Mau) field of the TLV configured by the local device.
Link Aggregation SupportedDisplays whether the local device supports link aggregation.
Link Aggregation EnabledDisplays the status of link aggregation fot the local device.
Aggregation Port ID Displays the aggregation port ID of the local device.
Power Port Class Displays the power port class of the local device.
PSE Power SupportedDisplays whether the local device supports PSE power.
PSE Power Enabled Displays the status of PSE power for the local device.
PSE Pairs Control AbilityDisplays whether the PSE pairs can be controlled for the local device.
Maximum Frame SizeDisplays the maximum frame size supported by the local device.

■ Viewing the Neighbor Info

Choose the menu L2 FEATURES > LLDP > LLDP Config > Neighbor Info to load the following page.

Figure 4-2 Neighbor Info
TP-LINK Omada TL-SG2008P - ■ Viewing the Neighbor Info - 1

text_image Auto Refresh Auto Refresh: Enable Neighbor Info UNIT1 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Port 1/0/7 System Name Chassic ID System Description Neighbor Port Information No Entries in this table.

Follow these steps to view the neighbor information:

1) In the Auto Refresh section, enable the Auto Refresh feature and set the Refresh Rate according to your needs. Click Apply.
2) In the Neighbor Info section, select the desired port and view its associated neighbor device information.

System Name Displays the system name of the neighbor device.

Chassis ID Displays the Chassis ID of the neighbor device.

System

Displays the system description of the neighbor device.

Description

Neighbor Port Displays the port ID of the neighbor device which is connected to the local port.

Information Click to view the details of the neighbor device.

4.1.2 Viewing LLDP Statistics

Choose the menu L2 FEATURES > LLDP > LLDP Config > Statistics Info to load the following page.

Figure 4-3 Static Info
TP-LINK Omada TL-SG2008P - Viewing LLDP Statistics - 1

text_image Auto Refresh Auto Refresh: □ Enable Apply Global Statistics Last Update Total Inserts Total Deletes Total Drops Total Ageouts 2 days 03h.41m.16s 0 0 0 0 Neighbors Statistics UNIT1 Port Transmit Total Receive Total Discards Errors Ageouts Discarded TLVs Unknown TLVs 1/0/19 0 0 0 0 0 0 0 1/0/20 0 0 0 0 0 0 0 1/0/21 0 0 0 0 0 0 0 1/0/22 0 0 0 0 0 0 0 1/0/23 0 0 0 0 0 0 0 1/0/24 0 0 0 0 0 0 0 1/0/25 0 0 0 0 0 0 0 1/0/26 0 0 0 0 0 0 0 1/0/27 0 0 0 0 0 0 0 1/0/28 0 0 0 0 0 0 0 Total: 28

Follow these steps to view LLDP statistics:

1) In the Auto Refresh section, enable the Auto Refresh feature and set the Refresh Rate according to your needs. Click Apply.
2) In the Global Statistics section, view the global statistics of the local device.

Last Update Displays the time when the statistics updated.

Total Inserts Displays the total number of neighbors during latest update time.

Total DeletesDisplays the number of neighbors deleted by the local device. The port will delet neighbors when the port is disabled or the TTL of the LLDP packets sent by the neighbor is 0.
Total DropsDisplays the number of neighbors dropped by the local device. Each port can learn a maximum of 80 neighbor device, and the subsequent neighbors will be dropped when the limit is exceeded.

Total Ageouts Displays the latest number of neighbors that have aged out on the local device.

3) In the Neighbors Statistics section, view the statistics of the corresponding port.

Transmit Total Displays the total number of the LLDP packets sent via the port.

Receive Total Displays the total number of the LLDP packets received via the port.

Discards Displays the total number of the LLDP packets discarded by the port.

Errors Displays the total number of the error LLDP packets received via the port.

Ageouts Displays the number of the aged out neighbors that are connected to the port.

TLV Discards Displays the total number of the TLVs discarded by the port when receiving LLDP packets.

TLV Unknowns Displays the total number of the unknown TLVs included in the received LLDP packets.

4.2 Using CLI

■ Viewing the Local Info

show lldp local-information interface { fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port }

View the LLDP details of a specific port or all the ports on the local device.

■ Viewing the Neighbor Info

show lldp neighbor-information interface { fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port }

Display the information of the neighbor device which is connected to the port.

■ Viewing LLDP Statistics

show lldp traffic interface { fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port }

View the statistics of the corresponding port on the local device.

5 Viewing LLDP-MED Settings

5.1 Using GUI

Choose the menu L2 FEATURES > LLDP > LLDP-MED Config > Local Info to load the following page.

■ Viewing the Local Info

Figure 5-1 LLDP-MED Local Info
TP-LINK Omada TL-SG2008P - Using GUI - 1

text_image Auto Refresh Auto Refresh: ☐ Enable Local Info UNIT1 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Port 1/0/8 Local Interface: 1/0/8 Device Type: Network Connectivity Application Type: Reserved Unknown Policy Flag: Yes VLAN tagged: 0 Media Policy VLAN ID: 0 Media Policy Layer 2 Priority: 0 Media Policy DSCP: 0 Location Data Format: Civic Address LCI What: Switch Country Code: CN China(Default) Power Type: PSE Device Power Source: Primary Power Priority: Low

Follow these steps to view LLDP-MED local information:

1) In the Auto Refresh section, enable the Auto Refresh feature and set the Refresh Rate according to your needs. Click Apply.
2) In the LLDP-MED Local Info section, select the desired port and view the LLDP-MED settings.

Local Interface Displays the local port ID.

Device Type Displays the local device type defined by LLDP-MED.LLDP-MED.

Application Type

Displays the supported applications of the local device.

Unknown Policy Flag

Displays the unknown location settings included in the network policy TLV.

VLAN tagged Displays the VLAN Tag type of the applications, tagged or untagged.

Media Policy VLAN ID

Displays the 802.1Q VLAN ID of the port.

Media Policy Layer 2 Priority

Displays the Layer 2 priority used in the specific application.

Media Policy DSCP

Displays the DSCP value used in the specific application.

Location Data Format

Displays the Location ID data format of the local device.

What Displays the type of the local device.

Country Code Displays the country code of the local device.

Power Type Displays the whether the local device is a PSE device or PD device.

Power Source Displays the power source of the local device.

Power Priority

Displays the power priority of the local device, which represents the priority of power that is received by the PD devices, or the priority of power that the PSE devices supply.

Power Value Displays the power required by the PD device or supplied by the PSE device.

Hardware Revision

Displays the hardware revision of the local device.

Firmware Revision

Displays the firmware revision of the local device.

Software Revision

Displays the software revision of the local device.

Serial Number Displays the serial number of the local device.

Manufacturer

Displays the manufacturer name of the local device.

Name

Model Name Displays the model name of the local device.

Asset ID Displays the asset ID of the local device.

■ Viewing the Neighbor Info

Choose the menu L2 FEATURES > LLDP > LLDP-MED Config > Neighbor Info to load the following page.

Figure 5-2 LLDP-MED Neighbor Info
TP-LINK Omada TL-SG2008P - ■ Viewing the Neighbor Info - 1

text_image Auto Refresh Auto Refresh: Enable Apply Neighbor Info UNIT1 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Port 1/0/1 Device Type Application Type Location Data Format Power Type Information No Entries in this table.

Follow these steps to view LLDP-MED neighbor information:

1) In the Auto Refresh section, enable the Auto Refresh feature and set the Refresh Rate according to your needs. Click Apply.
2) In the Neighbor Info section, select the desired port and view the LLDP-MED settings.

Device Type Displays the LLDP-MED device type of the neighbor device.

Application

Displays the application type of the neighbor device.

Type

Location Data

Displays the location type of the neighbor device.

Format

Power Type Displays the power type of the neighbor device.

Information View more LLDP-MED details of the neighbor device.

5.2 Using CLI

■ Viewing the Local Info

show lldp local-information interface { fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port }

View the LLDP details of a specific port or all the ports on the local device.

■ Viewing the Neighbor Info

show lldp neighbor-information interface {fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port }

Display the information of the neighbor device which is connected to the port.

■ Viewing LLDP Statistics

show lldp traffic interface { fastEthernet port | gigabitEthernet port | tengigabitEthernet port }

View the statistics of the corresponding port.

6 Configuration Example

6.1 Configuration Example for LLDP

6.1.1 Network Requirements

The network administrator needs view the information of the devices in the company network to know about the link situation and network topology so that he can troubleshoot the potential network faults in advance.

6.1.2 Network Topology

Exampled with the following situation:

Port Gi1/0/1 on Switch A is directly connected to port Gi1/0/2 on Switch B. Switch B is directly connected to the PC. The administrator can view the device information using the NMS.

Figure 6-1 LLDP Network Topology
TP-LINK Omada TL-SG2008P - Network Topology - 1

flowchart
graph LR
    A["Switch A"] -->|Gi1/0/1| B["Switch B"]
    B -->|Gi1/0/2| A
    B --> C["PC"]

6.1.3 Configuration Scheme

LLDP can meet the network requirements. Enable the LLDP feature globally on Switch A and Switch B. Configure the related LLDP parameters on the corresponding ports.

Configuring Switch A and Switch B:

The configurations of Switch A and Switch B are similar. The following introductions take Switch A as an example. Demonstrated with T1600G-52TS, this chapter provides configuration procedures in two ways: using the GUI and using the CLI.

6.1.4 Using the GUI

1) Choose the menu L2 FEATURES > LLDP > LLDP Config > Global Config to load the following page. Enable LLDP globally and configure the related parameters. Here we take the default settings as an example.

Figure 6-2 LLDP Global Config
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Global Config LLDP: ✓ Enable LLDP Forwarding: ☐ Enable Parameter Config Apply Transmit Interval: 30 seconds (5-32768) Hold Multiplier: 4 (2-10) Transmit Delay: 2 seconds (1-8192) Reinitialization Delay: 2 seconds (1-10) Notification Interval: 5 seconds (5-3600) Fast Start Repeat Count: 3 (1-10) Apply

2) Choose the menu L2 FEATURES > LLDP > LLDP Config > Port Config to load the following page. Set the Admin Status of port Gi1/0/1 as Tx&Rx, enable Notification Mode and configure all the TLVs included in the outgoing LLDP packets.

Figure 6-3 LLDP Port Config
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image Port Config UNIT1 Port Admin Notification Included TLVs Tx & Rx Enable ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ 1/0/1 Tx & Rx Enabled PD SC SD SN SA PV VP VA LA PS FS PW □ 1/0/2 Tx & Rx Disabled PD SC SD SN SA PV VP VA LA PS FS PW □ 1/0/3 Tx & Rx Disabled PD SC SD SN SA PV VP VA LA PS FS PW □ 1/0/4 Tx & Rx Disabled PD SC SD SN SA PV VP VA LA PS FS PW □ 1/0/5 Tx & Rx Disabled PD SC SD SN SA PV VP VA LA PS FS PW □ 1/0/6 Tx & Rx Disabled PD SC SD SN SA PV VP VA LA PS FS PW □ 1/0/7 Tx & Rx Disabled PD SC SD SN SA PV VP VA LA PS FS PW □ 1/0/9 Tx & Rx Disabled PD SC SD SN SA PV VP VA LA PS FS PW □ 1/0/9 Tx & Rx Disabled PD SC SD SN SA PV VP VA LA PS FS PW □ 1/0/10 Tx & Rx Disabled PD SC SD SN SA PV VP VA LA PS FS PW Total: 28 1 entry selected. Cancel Apply

6.1.5 Using CLI

1) Enable LLDP globally and configure the corresponding parameters.

Switch_A#configure

Switch_A(config)#Ildp

Switch_A(config)#lldp hold-multiplier 4

Switch_A(config)#lldp timer tx-interval 30 tx-delay 2 reinit-delay 3 notify-interval 5 fast-count 3

2) Set the Admin Status of port Gi1/0/1 to Tx&Rx, enable Notification Mode and configure all the TLVs included in the outgoing LLDP packets.

Switch_A#configure

Switch_A(config)#interface gigabitEthernet 1/0/1

Switch_A(config-if)#lldp receive

Switch_A(config-if)#lldp transmit

Switch_A(config-if)#lldp snmp-trap

Switch_A(config-if)#lldp tlv-select all

Switch_A(config-if)#end

Switch_A#copy running-config startup-config

Verify the Configurations

View LLDP settings globally

Switch_A#show lldp

LLDP Status: Enabled

LLDP Forward Message: Disabled

Tx Interval: 30 seconds

TTL Multiplier: 4

Tx Delay: 2 seconds

Initialization Delay: 2 seconds

Trap Notification Interval: 5 seconds

Fast-packet Count: 3

LLDP-MED Fast Start Repeat Count: 4

View LLDP settings on each port

Switch_A#show lldp interface gigabitEthernet 1/0/1

LLDP interface config:

gigabitEthernet 1/0/1:

Admin Status: TxRx

SNMP Trap: Enabled

TLVStatus
-------
Port-DescriptionYes
System-CapabilityYes
System-DescriptionYes
System-NameYes
Management-AddressYes
Port-VLAN-IDYes
Protocol-VLAN-IDYes
VLAN-NameYes
Link-AggregationYes
MAC-PhysicYes
Max-Frame-SizeYes
PowerYes
LLDP-MED Status:Disabled
TLVStatus
-------
Network PolicyYes
Location IdentificationYes
Extended Power Via MDIYes
Inventory ManagementYes

View the Local Info

Switch_A#show lldp local-information interface gigabitEthernet 1/0/1

LLDP local Information:

gigabitEthernet 1/0/1:

Chassis type:MAC address
Chassis ID:00:0A:EB:13:23:97
Port ID type:Interface name
Port ID:GigabitEthernet1/0/1
Port description:GigabitEthernet1/0/1 Interface

TTL: 120

System name: T1600G-52TS

System description: JetStream 24-Port Gigabit L2 Managed Switch with 4 SFP Slots

System capabilities supported: Bridge Router

System capabilities enabled: Bridge Router

Management address type: ipv4

Management address: 192.168.0.226

Management address interface type: IfIndex

Management address interface ID: 1

Management address OID: 0

Port VLAN ID(PVID): 1

Port and protocol VLAN ID(PPVID): 0

Port and protocol VLAN supported: Yes

Port and protocol VLAN enabled: No

VLAN name of VLAN 1: System-VLAN

Protocol identity:

Auto-negotiation supported: Yes

Auto-negotiation enabled: Yes

OperMau: speed(1000)/duplex(Full)

Link aggregation supported: Yes

Link aggregation enabled: No

Aggregation port ID: 0

Power port class: PD

PSE power supported: No

PSE power enabled: No

PSE pairs control ability: No

Maximum frame size: 1518

LLDP-MED Capabilities: Capabilities

Network Policy

Location Identification

Inventory

Device Type: Network Connectivity

Application type: Reserved

Unknown policy: Yes

Tagged: No

VLAN ID: 0

Layer 2 Priority: 0

DSCP: 0

Location Data Format: Civic Address LCI

- What: Switch

- Country Code: CN

Hardware Revision: T1600G-52TS 3.0

Firmware Revision: Reserved

Software Revision: 3.0.0 Build 20170918 Rel.71414(s)

Serial Number: Reserved

Manufacturer Name: TP-Link

Model Name: T1600G-52TS 3.0

Asset ID: unknown

View the Neighbor Info

Switch_A#show lldp neighbor-information interface gigabitEthernet 1/0/1

LLDP Neighbor Information:

gigabitEthernet 1/0/1:

Neighbor index 1:

Chassis type: MAC address

Chassis ID: 00:0A:EB:13:18:2D

Port ID type: Interface name

Port ID: GigabitEthernet1/0/2

Port description: GigabitEthernet1/0/2 Interface

TTL: 120

System name:T1600G-52PS
System description:JetStream 48-Port Gigabit Smart PoE Switch with 4 SFP Slots
System capabilities supported:Bridge Router
System capabilities enabled:Bridge Router
Management address type:ipv4
Management address:192.168.0.1
Management address interface type:IfIndex
Management address interface ID:1
Management address OID:0
Port VLAN ID(PVID):1
Port and protocol VLAN ID(PPVID):0
Port and protocol VLAN supported:Yes
Port and protocol VLAN enabled:No
VLAN name of VLAN 1:System-VLAN
Protocol identity:
Auto-negotiation supported:Yes
Auto-negotiation enabled:Yes
OperMau:speed(1000)/duplex(Full)
Link aggregation supported:Yes
Link aggregation enabled:No
Aggregation port ID:0
Power port class:PSE
PSE power supported:Yes
PSE power enabled:Yes
PSE pairs control ability:No

6.2 Example for LLDP-MED

6.2.1 Network Requirements

As the following figure shows, an IP phone and a PC are both connected to port 1/0/1 of the switch. It is required that the voice data stream is sent to VLAN2 and other untagged data stream is sent to the default VLAN1.

Figure 6-1 LLDP-MED Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph LR
    PC["PC"] --> IPPhone["IP Phone"]
    IPPhone --> Switch["Switch"]
    Switch -->|Gi1/0/1| IPPhone

6.2.2 Configuration Scheme

LLDP-MED allows the switch to send its Auto VoIP information to the IP phones for auto-configuration. In this example, you can configure Auto VoIP and LLDP-MED to meet the network requirements.

The configuration overview is as follows:

1) Create VLAN2 for the voice data and keep the PVID of port 1/0/1 as the default value 1. In this way, all the untagged packets from the PC are sent to VLAN1; all the packets with VLAN Tag 2 from the IP phone are sent to VLAN2.
2) Configure Auto VoIP on port 1/0/1.
3) Enable LLDP globally.
4) Configure LLDP-MED on port 1/0/1.

Demonstrated with T1600G-28TS, this chapter provides configuration procedures in two ways: using the GUI and using the CLI.

6.2.3 Using the GUI

1) Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > VLAN Config and click Add to load the following page. Specify VLAN ID as 2, give a VLAN name, and select port 1/0/1 as untagged member port. Click Create.

Figure 6-2 VLAN Config
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image VLAN Config VLAN ID: 2 (2-4094, format: 2,4-5,8) VLAN Name: voice_vlan (1-16 characters) Untagged Ports Port: 1/0/1 (Format: 1/0/1, input or choose below) UNIT 1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Tagged Ports Port: (Format: 1/0/1, input or choose below) UNIT 1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27) Cancel Create

2) Choose the menu QoS > Auto VoIP to load the following page. Select port 1/0/1, configure the interface mode as VLAN ID and set the VLAN ID value as 2. Click Apply.

Figure 6-3 Auto VoIP Config
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image Global Config Auto VoIP: ✓ Enable Apply Port Config UNIT1 Port Interface Mode Value CoS Override Mode Operational Status DSCP Value VLAN ID 2 ✓ 1/0/1 VLAN ID 2 Disabled Disabled 0 □ 1/0/2 Disable 0 Disabled Disabled 0 □ 1/0/3 Disable 0 Disabled Disabled 0 □ 1/0/4 Disable 0 Disabled Disabled 0 □ 1/0/5 Disable 0 Disabled Disabled 0 □ 1/0/6 Disable 0 Disabled Disabled 0 □ 1/0/7 Disable 0 Disabled Disabled 0 □ 1/0/8 Disable 0 Disabled Disabled 0 □ 1/0/9 Disable 0 Disabled Disabled 0 □ 1/0/10 Disable 0 Disabled Disabled 0 Total: 28 1 entry selected. Cancel Apply

3) Choose the menu L2 FEATURES > LLDP > LLDP Config > Global Config to load the following page. Enable LLDP globally and click Apply.

Figure 6-4 LLDP Global Config
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image Global Config LLDP: ✓ Enable LLDP Forwarding: □ Enable Apply

4) Choose the menu L2 FEATURES > LLDP > LLDP Config > Global Config > Port Config to load the following page. Enable LLDP-MED on port 1/0/1 and click Apply.

Figure 6-5 LLDP-MED Config
TP-LINK Omada TL-SG2008P - Using the GUI - 4

text_image Port Config UNIT1 Port LLDP-MED Status Included TLVs Enable ✓ 1/0/1 Enabled Detail □ 1/0/2 Disabled Detail □ 1/0/3 Disabled Detail □ 1/0/4 Disabled Detail □ 1/0/5 Disabled Detail □ 1/0/6 Disabled Detail □ 1/0/7 Disabled Detail □ 1/0/8 Disabled Detail □ 1/0/9 Disabled Detail □ 1/0/10 Disabled Detail Total: 28 1 entry selected. Cancel Apply

5) Click Save the settings.

6.2.4 Using CLI

1) Create VLAN2 and add untagged port 1/0/1 to VLAN2.

Switch#configure

Switch(config)#vlan 2

Switch(config-vlan)#name voice_vlan

Switch(config-vlan)#exit

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#switch general allowed vlan 2 untagged

Switch(config-if)#exit

2) Enable Auto VoIP globally.

Switch(config)#auto-voip

3) Configure Auto VoIP. On port 1/0/1, configure the interface mode as VLAN ID and set the VLAN ID value as 2.

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#auto-voip 2

Switch(config-if)#exit

4) Enable LLDP globally.

Switch(config)#lldp

5) Enable LLDP-MED on port 1/0/1.

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#lldp med-status

Switch(config-if)#end

Switch#copy running-config startup-config

Verify the Configurations

View VLAN settings:

Switch#show vlan

VLAN NameStatusPorts
------------
1System-VLANactiveGi1/0/1, Gi1/0/2, Gi1/0/3, Gi1/0/4,
Gi1/0/5, Gi1/0/6, Gi1/0/7, Gi1/0/8,
Gi1/0/9, Gi1/0/10, Gi1/0/11, Gi1/0/12,
Gi1/0/13, Gi1/0/14, Gi1/0/15, Gi1/0/16,
Gi1/0/17, Gi1/0/18, Gi1/0/19, Gi1/0/20,
Gi1/0/21, Gi1/0/22, Gi1/0/23, Gi1/0/24,
Gi1/0/25, Gi1/0/26, Gi1/0/27, Gi1/0/28
2voice_vlanactiveGi1/0/1

View VoIP settings:

Switch#show auto-voip interface

Interface.Gi1/0/1

Auto-VoIP Interface Mode. Enabled

Auto-VoIP VLAN ID. 2

Auto-VoIP COS Override. False

Auto-VoIP DSCP Value. 0

Auto-VolP Port Status. Enabled

...

View global LLDP settings:

Switch_A#show lldp

LLDP Status: Enabled

LLDP Forward Message: Disabled

...

View LLDP-MED settings on port 1/0/1:

Switch_A#show lldp interface gigabitEthernet 1/0/1

LLDP interface config:

gigabitEthernet 1/0/1:

...

LLDP-MED Status: Enabled

TLV Status


Network Policy Yes

Location Identification Yes

Extended Power Via MDI Yes

Inventory Management Yes

7

Appendix: Default Parameters

Default settings of LLDP are listed in the following tables.

Default LLDP Settings

Table 7-1 Default LLDP Settings

Parameter Default Setting
LLDP Disabled
LLDP Forward Message Disabled
Transmit Interval 30 seconds
Hold Multiplier 4
Transmit Delay 2 seconds
Reinitialization Delay 2 seconds
Notification Interval 5 seconds
Fast Start Repeat Count 3

Table 7-2 Default LLDP Settings on the Port

Parameter Default Setting
Admin StatusTx&Rx
Notification ModeDisabled
Included TLVsAll

Default LLDP-MED Settings

Table 7-3 Default LLDP-MED Settings

Parameter Default Setting
Fast Start Repeat Count 4
LLDP-MED Status (port) Disabled
Included TLVsAll

Part 16

Configuring L2PT

(Only for Certain Devices)

CHAPTERS

  1. Overview
  2. L2PT Configuration
  3. Configuration Example
  4. Appendix: Default Parameters

1 Overview

TP-LINK Omada TL-SG2008P - Overview - 1

Note:

L2PT is only available on certain devices. To check whether your device supports this feature, refer to the actual web interface. If L2PT is available, there is L2 FEATURES > L2PT in the menu structure.

L2PT (Layer 2 Protocol Tunneling) is a feature for service providers to transparently transmit Layer 2 protocol data units (PDUs) between customer networks at different locations through a public ISP network. Some terminology that is used in this section is defined as follows:

■ Edge Switch: The switch that is connected to the customer network and placed on the boundary of the ISP network.
■ UNI: User Network Interface, a port configured on the edge switch which is connected to the customer network.
■ NNI: Network Network Interface, a port configured on the edge switch which is connected to the ISP network.

As shown in Figure 1-1, a customer has two local networks which are connected through the ISP network. When the two customer networks run the same Layer 2 protocol, the Layer 2 PDUs between them must be transmitted through the ISP network to perform Layer 2 protocol calculation (for example, calculating a spanning tree). Generally, the PDUs of the same Layer 2 protocol use the same destination MAC address. Therefore, when a Layer 2 PDU from a customer network reaches a edge switch in the ISP network, the switch cannot identify whether the PDU comes from a customer network or the ISP network and then the PDU will be discarded. As a result, the Layer 2 PDUs cannot be transmitted through the ISP network to the other side.

Figure 1-1 L2PT Application
TP-LINK Omada TL-SG2008P - Note: - 1

flowchart
graph TD
    CE1["CE1"] -->|UNI| PE1["PE1"]
    CE1 -->|UNI| NEINNI["NNINNI"]
    NEINNI -->|UNI| PE2["PE2"]
    NEINNI -->|UNI| CE2["CE2"]
    CE2 -->|UNI| NEINNI
    style NEINNI fill:#f9f,stroke:#333
    style_SP1["ISP Network"] fill:#bbf,stroke:#333
    style NEINNI fill:#bbf,stroke:#333
    style CE1 fill:#bfb,stroke:#333
    style SP1 fill:#bfb,stroke:#333
    style NEINNI fill:#bbf,stroke:#333

To resolve this problem, the ISP network should transparently transmit the Layer 2 PDUs between the two customer networks. In this case, L2PT feature can be configured on the edge switches (PE1 and PE2) to allow the Layer 2 PDUs to be tunneled through the network.

The following describes the PDUs transmission procedure through the ISP network from one customer network to the other side:

1) Upon receiving a Layer 2 PDU from CE1 via the UNI port, PE1 replaces the destination MAC address of the PDU with a special multicast MAC address (01:00:0c:cd:cd: d0) and then sends the PDU to the ISP network via the NNI port.
2) The ISP network identifies the PDU and directly forwards it to the other end.
3) PE2 receives the PDU via its NNI port and restores the destination MAC address of the PDU to its original destination MAC address.

With L2PT feature configured accordingly, the switch can transparently transmit the PDUs of the following Layer 2 protocols: STP (Spanning Tree Protocol), GVRP (GARP VLAN Registration Protocol), LACP (Link Aggregation Control Protocol), CDP (Cisco Discovery Protocol), VTP (VLAN Trunking Protocol), PAgP (Port Aggregation Protocol), UDLD (UniDirectional Link Detection) and PVST+(Per VLAN Spanning Tree Plus).

2 L2PT Configuration

2.1 Using the GUI

Choose the menu L2 FEATURES > L2PT to load the following page.

Figure 2-1 Configuring L2PT
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image L2PT Config Layer 2 Protocol Tunneling: Enable Apply Port Config UNIT1 LAGS Port Type Protocol Threshold LAG ✓ 1/0/1 None ---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/--- □ 1/0/2 None ---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/--- □ 1/0/3 None ---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/--- □ 1/0/4 None ---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/--- □ 1/0/5 None ---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/---/-----/ □ 1/0/6 None ---/---/---/----/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/--/----. □ 1/0/7 None ---//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//------/ □ 1/08 None ---//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//-----//------/ ☐ 109 None ---//-----//-----//-----//-----//----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- //----- /--- ☐ 110 None ---//-------//-------//-------//-------//-------//-------//-------//-------//-------//-------//-------//-------//-------//-------//-------//-------//-------//-------//-------//-------//-------//-------//-------//-------//-------//-------//-------//-------//-------//-------//-------//------- Total: 28 1 entry selected Cancel Apply

Follow these steps to configure L2PT:

1) In the L2PT Config section, enable L2PT globally and click Apply.
2) In the Port Config section, configure the port that is connected to the customer network as a UNI port and specify your desired protocols on the port. In addition, you can also set the threshold for packets-per-second to be processed on the UNI port.

Port Displays the port number.

Type

Select UNI as the port type for the selected port. Usually, the UNI port is connected to the customer network.

The default setting is None which indicates that L2PT is disabled on this port.

Protocol Specify the Layer 2 protocol types of the packets that can be transparently transmitted on the selected port:

STP: Enable protocol tunneling for the STP packets.

GVRP: Enable protocol tunneling for the GVRP packets.

01000CCCCCC: Enable protocol tunneling for the packets with their destination MAC address as 01000CCCCCC, which includes CDP, VTP, PAgP and UDLD.

01000CCCCCCD: Enable protocol tunneling for the PVST+ packets with the destination MAC address as 01000CCCCCCD.

LACP: Enable protocol tunneling for the LACP packets.

All: All the above Layer 2 protocols are supported for tunneling.

Threshold Specify the maximum number of packets to be processed for the specified protocol on the port in one second. When the threshold is exceeded, the port drops the specified Layer 2 protocol packets.

This value ranges from 1 to 1000 (packets per second). 0 indicates that the threshold feature is disabled.

LAG Displays the LAG that the port is in.

3) In the Port Config section, configure the port that is connected to the ISP network as an NNI port. Note that the protocols and threshold cannot be configured on the NNI port.

Port Displays the port number.

Type Select NNI as the port type for the selected port. Usually, NNI port is connected to the ISP network.

The default setting is None, which indicates that L2PT is disabled on this port.

LAG Displays the LAG that the port is in.

4) Click Apply.

TP-LINK Omada TL-SG2008P - Using the GUI - 2

Note:

The member port of an LAG (Link Aggregation Group) follows the configuration of the LAG and not its own. The configurations of the port can take effect only after it leaves the LAG.

2.2 Using the CLI

Follow these steps to configure L2PT feature.

Step 1 configure

Enter global configuration mode.

Step 2 l2protocol-tunnelEnable the L2PT feature globally.
Step 3 interface { fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-id-list }Enter interface configuration mode.
Step 4l2protocol-tunnel type uni {01000ccccc | 01000ccccc | gvrp | stp | lacp | all } [threshold threshold]Configure the port as a UNI port, specify the Layer 2 protocol types of the packets that can be transparently transmitted on the port, and set the threshold for packets-per-second accepted for encapsulation on the UNI port.01000ccccc: Enable protocol tunneling for the packets with their destination MAC address as 01000CCCCCCC, which includes CDP, VTP, PAgP and UDLD.01000ccccc: Enable protocol tunneling for the PVST+ packets with the destination MAC address as 01000CCCCC.D.gvrp: Enable protocol tunneling for the GVRP packets.stp: Enable protocol tunneling for the STP packets.lacp: Enable protocol tunneling for the LACP packets.all: All the above Layer 2 protocols are supported for tunneling.threshold: Set a threshold which determines the maximum number of packets to be processed for the specified protocol on the port in one second. When the threshold is exceeded, the port drops the specified Layer 2 protocol packets. The valid values are from 1 to 1000 (packets/second). 0 indicates that the threshold feature is disabled.
Step 5 exitReturn to global configuration mode.
Step 6 interface { fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-id-list }Enter interface configuration mode.
Step 7 l2protocol-tunnel type nniConfigure the port as an NNI port.
Step 8 show l2protocol-tunnel globalVerify the global L2PT configuration.
Step 9 show l2protocol-tunnel interface [ fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel port-channel-id ]Verify the L2PT configuration of the port or LAG.

Step 10 end

Return to privileged EXEC mode.

Step 11 copy running-config startup-config

Save the settings in the configuration file.

TP-LINK Omada TL-SG2008P - Using the CLI - 1

Note:

The member port of an LAG (Link Aggregation Group) follows the configuration of the LAG and not its own. The configurations of the port can take effect only after it leaves the LAG.

This example shows how to enable L2PT globally:

Switch#configure

Switch(config)#l2protocol-tunnel

Switch(config)#show l2protocol-tunnel global

I2protocol-tunnel State: Enable

Switch(config)#end

Switch#copy running-config startup-config

This example shows how to configure port 1/0/1 as a UNI port for the Layer 2 protocol GVRP and set the threshold as 1000:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#l2protocol-tunnel type uni gvrp threshold 1000

Switch(config-if)#show l2protocol-tunnel interface gigabitEthernet 1/0/1

InterfaceTypeProtocolThresholdLAG
--------------------
Gi1/0/1unigvrp,--,--,--1000,--,--,--N/A

Switch(config-if)#end

Switch#copy running-config startup-config

This example shows how to configure port 1/0/5 as an NNI port.

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/5

Switch(config-if)#l2protocol-tunnel type nni
Switch(config-if)#show l2protocol-tunnel interface gigabitEthernet 1/0/5

InterfaceTypeProtocolThresholdLAG
--------------------
Gi1/0/5nni--,--,--,----,--,--,--N/A

Switch(config-if)#end

Switch#copy running-config startup-config

3 Configuration Example

3.1 Network Requirements

As shown below, the two branches of a company are connected through the ISP network, and they want to achieve spanning tree calculation by exchanging Layer 2 STP packets with each other. To meet this requirement, the ISP network needs to transparently transmit the STP packets between the two customer networks.

Figure 3-1 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["Switch A"] -->|1/0/2| B["ISP Network"]
    B -->|1/0/11/0/1| C["Switch B"]
    C -->|1/0/2| D["Customer Network Customer Network"]
    D -->|1/0/2| A

3.2 Configuration Scheme

The service provider can configure L2PT on the two edge switches (Switch A and Switch B). With the L2PT feature, the STP packets can be encapsulated as normal data packets and sent to the other side without being processed by the devices in the ISP network.

The overview of configuration is as follows:

1) Enable the L2PT feature globally.
2) Specify port 1/0/1 which is connected to the ISP network as an NNI port.
3) Specify port 1/0/2 which is connected to the customer network as a UNI port for the STP. In addition, configure the threshold as 1000 to limit the number of packets to be processed on the port in one second.

Demonstrated with T2600G-28TS, the following sections provide configuration procedure in two ways: using the GUI and using the CLI.

3.3 Using the GUI

The configurations of Switch A and Switch B are similar. The following introductions take Switch A as an example.

1) Choose the menu L2 FEATURES > L2PT to load the following page. Enable the L2PT feature globally and click Apply.
2) Specify port 1/0/1 as an NNI port and click Apply. Specify port 1/0/2 as a UNI port for the STP and set the threshold as 1000. Then click Apply. The configuration result is as follows:

Figure 3-2 Global Config
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image L2PT Config Layer 2 Protocol Tunneling: ✓ Enable Port Config UNIT1 LAGS Port Type Protocol Threshold LAG UNI STP 1000 1/0/1 NNI ----/----/----/ ----/----/----/ -- ✓ 1/0/2 UNI STP 1000 -- 1/0/3 None ----/----/----/ ----/----/----/ -- 1/0/4 None ----/----/----/ ----/----/----/ -- 1/0/5 None ----/----/----/ ----/----/----/ -- 1/0/6 None ----/----/----/ ----/----/----/ -- 1/0/7 None ----/----/----/ ----/----/----/ -- 1/0/8 None ----/----/----/ ----/----/----/ -- 1/0/9 None ----/----/----/ ----/----/----/ -- 1/0/10 None ----/----/----/ ----/----/----/ -- Total: 28 1 entry selected. Cancel Apply

3) Click Save the settings.

3.4 Using the CLI

The configurations of Switch A and Switch B are similar. The following introductions take Switch A as an example.

Switch_A#configure

Switch_A(config)#l2protocol-tunnel

Switch_A(config)#interface gigabitEthernet 1/0/1

Switch_A(config-if)#l2protocol-tunnel type nni

Switch_A(config-if)#exit

Switch_A(config)#interface gigabitEthernet 1/0/2

Switch_A(config-if)#l2protocol-tunnel type uni stp 1000

Switch_A(config-if)#end

Switch_A#copy running-config startup-config

Verify the Configuration

Verify the global configuration:

Switch_A#show l2protocol-tunnel global

I2protocol-tunnel State: Enable

Verify the configuration on port 1/0/1:

Switch_A#show l2protocol-tunnel interface gigabitEthernet 1/0/1

InterfaceTypeProtocolThresholdLAG
--------------------
Gi1/0/1nni--,--,--,----,--,--,--N/A

Verify the configuration on port 1/0/2:

Switch_A#show l2protocol-tunnel interface gigabitEthernet 1/0/2

InterfaceTypeProtocolThresholdLAG
--------------------
Gi1/0/2unistp,--,--,--,1000,--,--,--,N/A

4 Appendix: Default Parameters

Default settings of L2PT are listed in the following table.

Table 4-1 Default Settings of L2PT

Parameter Default Setting
L2PT Config
Layer 2 Protocol Tunneling Disable
Port Config
Type None
Protocol None
Threshold None

Part 17

Configuring PPPoE ID Insertion

(Only for Certain Devices)

CHAPTERS

  1. Overview
  2. PPPoE ID Insertion Configuration
  3. Appendix: Default Parameters

1 Overview

TP-LINK Omada TL-SG2008P - Overview - 1

Note:

PPPoE ID Insertion is only available on certain devices. To check whether your device supports this feature, refer to the actual web interface. If PPPoE ID Insertion is available, there is L2 FEATURES > PPPoE in the menu structure.

In common PPPoE dialup mode, when users dial up through PPPoE, they can access the network as long as their accounts are authenticated successfully on the RADIUS server. As a result, the illegal users can embezzle the accounts to access the Internet.

PPPoE ID Insertion provides a way to resolve this problem. With this feature enabled, the switch attaches a tag to the PPPoE Active Discovery packets received from the client, and sends it to the BRAS (Broadband Remote Access Server). The tag records the client information, such as the connected port number and the MAC address of the client. The BRAS uses the tag as a NAS-Port-ID attribute in the RADIUS packet and send it to the RADIUS server for PPP (Point-to-Point Protocol) authentication. If the tag information is different from the configured one, the authentication will fail. In this way, the illegal users cannot embezzle the accounts of legal users to access the Internet.

Additionally, after receiving the PPPoE Active Discovery Offer packet or Session-confirmation packet from the BRAS, the switch will remove the tag in the packet and send it to the client.

Figure 1-1 Network Topology of PPPoE ID-Insertion
TP-LINK Omada TL-SG2008P - Note: - 1

flowchart
graph LR
    A["Client"] --> B["Switch"]
    B --> C["BRAS PPPoE Server"]
    C --> D["RADIUS Server"]

2 PPPoE ID Insertion Configuration

2.1 Using the GUI

Choose the menu L2 FEATURES > PPPoE to load the following page.

Figure 2-1 Configuring PPPoE ID Insertion
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image PPPoE ID Insertion PPPoE ID Insertion: ☐ Enable Apply Port Config UNIT1 LAGS Port Circuit-ID Circuit-ID Type UDF Value Remote-ID Remote-ID Value ✓ 1/0/1 Disabled IP -- Disabled -- ☐ 1/0/2 Disabled IP -- Disabled -- ☐ 1/0/3 Disabled IP -- Disabled -- ☐ 1/0/4 Disabled IP -- Disabled -- ☐ 1/0/5 Disabled IP -- Disabled -- ☐ 1/0/6 Disabled IP -- Disabled -- ☐ 1/0/7 Disabled IP -- Disabled -- ☐ 1/0/8 Disabled IP -- Disabled -- ☐ 1/0/9 Disabled IP -- Disabled -- ☐ 1/0/10 Disabled IP -- Disabled -- Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure PPPoE ID-Insertion:

1) In the PPPoE ID Insertion section, enable PPPoE ID Insertion and click Apply.
2) In the Port Config section, select one or more ports, and configure the relevant parameters. Then click Apply.

Circuit-ID Enable or disable the Circuit-ID Insertion feature. With this option enabled, the switch will insert a Circuit ID to the received PPPoE Discovery packet on this port.

Circuit-ID Type Select the type of the Circuit ID. The following options are provided:

IP: The circuit ID includes the following three parts: the source MAC address of the received packet, the IP address of the switch and the port number. This is the default value.

MAC: The circuit ID includes the following three parts: the source MAC address of the packet, the MAC address of the switch and the port number.

UDF: The circuit ID includes the following three parts: the source MAC address of the packet, the user-specified string and the port number.

UDF Only: Only the user specified string will be used to encode the Circuit-ID option.

UDF Value If UDF or UDF Only is selected, specify a string with at most 40 characters to encode the Circuit-ID option.

Remote-ID Enable or disable the Remote-ID Insertion feature. With this option enabled, the switch will insert a Remote ID to the received PPPoE Discovery packet on this port.

Remote-ID Value Specify a string with at most 40 characters to encode the Remote-ilD option.

TP-LINK Omada TL-SG2008P - Using the GUI - 2

Note:

The member port of an LAG (Link Aggregation Group) follows the configuration of the LAG and not its own. The configurations of the port can take effect only after it leaves the LAG.

2.2 Using the CLI

Follow these steps to configure PPPoE ID Insertion:

Step 1 configure

Enter global configuration mode.

Step 2 pppoe id-insertion

Globally enable the PPPoE ID Insertion feature.

Step 3 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list}

Enter interface configuration mode.

Step 4 pppoe circuit-id

Enable Circuit-ID Insertion feature, and the switch will insert a Circuit ID to the received PPPoE Discovery packet on this port.

Step 5 pppoe circuit-id type { mac | ip | udf [

Value] | udf-only [Value] }

Specify the type of the Circuit ID. The following options are provided:

mac: The source MAC address of the packet, the MAC address of the switch and the port number will be used to encode the Circuit-ID option.

ip: The circuit ID includes the following three parts: the source MAC address of the received packet, the IP address of the switch and the port number. This is the default value.

udf [Value]: Specify a string with at most 40 characters. The circuit ID includes the following three parts: the source MAC address of the packet, the user-specified string and the port number.

udf-only [Value]: Specify a string with at most of 40 characters. Only the specified string will be used to encode the Circuit-ID option.

Step 6 pppoe remote-id [ Value]

Enable Remote-ID Insertion feature and specify the Remote ID.

Value Specify a string with at most 40 characters. The source MAC address of the packet and the specified string will be used to encode the Remote-ID option.

Step 7 show pppoe id-insertion global

Verify the global configuration of PPPoE ID Insertion.

Step 8 show pppoe id-insertion interface { fastEthernet gigabitEthernet port}

port | gigabitEthernet port | ten-

Verify the configuration of PPPoE ID Insertion on the port.

Step 9 end

Return to privileged EXEC mode.

Step 10 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable PPPoE ID Insertion globally and on port 1/0/1, and configure the Circuit-ID as 123 without other information and Remote-ID as host1.

Switch#configure

Switch(config)#pppoe id-insertion

Switch(config-if)#interface gigabitEthernet 1/0/1

Switch(config-if)#pppoe circuit-id

Switch(config-if)#pppoe circuit-id type udf-only 123

Switch(config-if)#pppoe remote-id host1

Switch(config-if)#show pppoe id-insertion global

PPPoE ID Insertion State: Enabled

Switch(config-if)#show pppoe id-insertion interface gigabitEthernet 1/0/1

The member port of an LAG (Link Aggregation Group) follows the configuration of the LAG and not its own. The configurations of the port can take effect only after it leaves the LAG.

3 Appendix: Default Parameters

Default settings of L2PT are listed in the following table.

Table 3-1 PPPoE ID Insertion

Parameter Default Setting
Global Config
PPPoE ID Insertion Disabled
Port Config
Circuit-ID Disabled
Circuit-ID Type IP
UDF Value None
Remote-ID Disabled
Remote-ID Value None

Part 18

Configuring Layer 3 Interfaces

CHAPTERS

  1. Overview
  2. Layer 3 Interface Configurations
  3. Configuration Example
  4. Appendix: Default Parameters

1 Overview

Interfaces are used to exchange data and interact with interfaces of other network devices. Interfaces are classified into Layer 2 interfaces and Layer 3 interfaces.

■ Layer 2 interfaces are the physical ports on the switch panel. They forward packets based on MAC address table.
■ Layer 3 interfaces are used to forward IPv4 and IPv6 packets using static or dynamic routing protocols. You can use Layer 3 interfaces for IP routing and inter-VLAN routing.

This chapter introduces the configurations for Layer 3 interfaces. The supported types of Layer 3 interfaces are shown as below:

Table 1-1 Supported Types of Layer 3 interfaces

Type Description
VLAN InterfaceA Layer 3 interface with which acts as the default gateway of all the hosts in the corresponding VLAN.
Loopback Interface An interface of which the status is always up.
Routed Port A physical port configured as an Layer 3 port.
Port-channel InterfaceSeveral routed ports are bound together and configured as an Layer 3 interface.

2 Layer 3 Interface Configurations

To complete IPv4 interface configuration, follow these steps:

1) Create an Layer 3 interface
2) Configure IPv4 parameters of the created interface
3) View detailed information of the created interface

To complete IPv6 interface configuration, follow these steps:

1) Create an Layer 3 interface
2) Configure IPv6 parameters of the created interface
3) View detailed information of the created interface

2.1 Using the GUI

2.1.1 Creating an Layer 3 Interface

Choose the menu L3 FEATURES> Interface to load the following page.

Figure 2-1 Creating an Layer 3 Interface
TP-LINK Omada TL-SG2008P - Creating an Layer 3 Interface - 1

text_image Routing Config IPv4 Routing: ✓ Enable IPv6 Routing: □ Enable Apply Interface List + Add - Delete □ Interface ID IP Address Mode IP Address Subnet Mask Interface Name Status Operation □ Loopback3 None - - Down Edit IPv4 Detail □ VLAN1 Static 192.168.0.26 255.255.255.0 Up Edit IPv4 Detail □ Gi1/0/18 None - - Down Edit IPv4 Detail Total: 3

Follow these steps to create an Layer 3 interface.

1) In the Routing Config section, enable IPv4 routing or IPv6 routing. Then click Apply.

IPv4 Routing

Enable IPv4 routing function globally for all Layer 3 interfaces. It is enabled by default.

IPv6 Routing

(Optional) Enable IPv6 routing function globally for all Layer 3 interfaces. It is disabled by default.

2) In the Interface List section, click + Add to load the following page, and configure the corresponding parameters for the Layer 3 interface. Then click Create.

Interface

Interface ID:

VLAN

TP-LINK Omada TL-SG2008P - Interface - 1

(1-4094)

IP Address Mode:

TP-LINK Omada TL-SG2008P - Interface - 2

None

TP-LINK Omada TL-SG2008P - Interface - 3

Static

TP-LINK Omada TL-SG2008P - Interface - 4

DHCP

TP-LINK Omada TL-SG2008P - Interface - 5

BOOTP

Admin Status:

TP-LINK Omada TL-SG2008P - Interface - 6

Enable

Interface Name:

(Optional. 1-16 characters)

Cancel

Create

Interface ID Select an interface type and enter the ID of the interface.

IP Address Mode Specify the IP address assignment mode of the interface.

None: No IP address will be assigned to the interface.

Static: Assign an IP address to the interface manually.

DHCP: Assign an IP address to the interface through the DHCP server.

BOOTP: Assign an IP address to the interface through the BOOTP server.

DHCP Option 12 If you select DHCP as the IP Address Mode, configure the Option 12 here.

DHCP Option 12 is used to specify the client's name.

IP Address

Specify the IP address of the interface if you choose "Static" as the IP address assignment mode.

Subnet Mask Specify the subnet mask of the interface's IP address.

Admin Status Enable or disable the interface's Layer 3 capabilities.

Interface Name (Optional) Enter a name for the interface.

TP-LINK Omada TL-SG2008P - Interface - 7

Note:

The created interface is an IPv4 interface. To configure the IPv6 features, please click "Edit IPv6" after the interface is created.

2.1.2 Configuring IPv4 Parameters of the Interface

In Figure 2-1 you can view the corresponding interface you have created in the Interface List section. On the corresponding interface entry, click Edit IPv4 to load the following page and edit the IPv4 parameters of the interface.

Figure 2-2 Configuring the IPv4 Parameters
TP-LINK Omada TL-SG2008P - Configuring IPv4 Parameters of the Interface - 1

text_image Modify IPv4 Interface Interface ID: VLAN1 Admin Status: Enable Interface Name: (Optional. 1-16 characters) IP Address Mode: None Static DHCP BOOTP IP Address: 192.168.0.28 (Format: 192.168.0.1) Subnet Mask: 255.255.255.0 (Format: 255.255.255.0) Apply Secondary IP List ID IP Address Subnet Mask No Entries in this table. Total: 0

1) In the Modify IPv4 Interface section, configure relevant parameters for the interface according to your actual needs. Then click Apply.

Interface ID Displays the interface ID.
Admin Status Enable the Layer 3 capabilities for the interface.
Interface Name (Optional) Enter a name for the interface.
IP Address Mode Specify the IP address assignment mode of the interface.
None: No IP address will be assigned.
Static: Assign an IP address manually.
DHCP: Obtain an IP address through DHCP.
BOOTP: Obtain an IP address through BOOTP.
IP AddressSpecify the IP address of the interface if you choose "Static" as the IP address assignment mode.
Subnet Mask Specify the subnet mask of the interface's IP address.

DHCP Option 12 If you select DHCP as the IP Address Mode, configure the Option 12 here.

DHCP Option 12 is used to specify the client's name.

2) In the Secondary IP List section, click + Add to add a secondary IP for the specified interface which allows you to have two logical subnets. Then click Create.

TP-LINK Omada TL-SG2008P - Configuring IPv4 Parameters of the Interface - 2

text_image Secondary IP IP Address: (Format: 192.168.0.1) Subnet Mask: (Format: 255.255.255.0) Cancel Create

IP Address Specify the secondary IP address of the interface.

Subnet Mask Specify the subnet mask of the secondary IP address.

3) (Optional) In the Secondary IP List section, you can view the corresponding secondary IP entry you have created.

2.1.3 Configuring IPv6 Parameters of the Interface

In Figure 2-1, you can view the corresponding interface entry you have created in the Interface List section. On the corresponding interface entry, click Edit IPv6 to load the following page and configure the IPv6 parameters of the interface.

Figure 2-3 Configuring the IPv6 Parameters
TP-LINK Omada TL-SG2008P - Configuring IPv6 Parameters of the Interface - 1

text_image Modify IPv6 Interface Interface ID: VLAN1 Admin Status: Enable IPv6 Enable: Enable Link-local Address Mode: Manual Auto Link-local Address: fe80:c66e:1fff.febf.7251 (Format:3001:1) Status: Normal Enable global address auto configuration via RA message Enable global address auto configuration via DHCPv6 Server Apply Global Address Table Add Delete ID Global Address Prefix Length Type Preferred Lifetime Valid Lifetime Status No Entries in this table. Total: 0

1) In the Modify IPv6 Interface section, enable IPv6 feature for the interface and configure the corresponding parameters. Then click Apply.

Interface ID Displays the interface ID.
Admin Status Enable the Layer 3 capabilities for the interface.
IPv6 Enable Enable the IPv6 feature of the interface.
Link-local Address ModeSelect the link-local address configuration mode.Manual:With this option selected, you can assign a link-local address manually.Auto:With this option selected, the switch generates a link-local address automatically.
Link-local AddressEnter a link-local address if you choose “Manual” as the Link-Local Address Mode.
Status Displays the status of the link-local address. An IPv6 address cannot be used before pass the DAD (Duplicate Address Detection), which is used to detect the address conflicts. In the DAD process, the IPv6 address may in three different status:Normal: Indicates that the link-local address passes the DAD and can be used normally.Try: Indicates that the link-local address is in the progress of DAD and cannot be used right now.Repeat: Indicates that the link-local address is duplicated, this address is already used by another node and cannot be used by the interface.

2) Configure IPv6 global address of the interface via following three ways:

Via RA Message:

Enable global address auto configuration via RA messageWith this option enabled, the interface automatically generates a global address and other information according to the address prefix and other configuration parameters from the received RA (Router Advertisement) message.

Via DHCPv6 Server:

Enable global address auto configuration via DHCPv6 ServerWith this option enabled, the switch will try to obtain the global address from the DHCPv6 Server.

Manually:

In the Global Address Table section, click + Add to manually assign an IPv6 global address to the interface.

Global Address

Address Format:

TP-LINK Omada TL-SG2008P - Global Address - 1

EUI-64

TP-LINK Omada TL-SG2008P - Global Address - 2

Not EUI-64

Global Address:

TP-LINK Omada TL-SG2008P - Global Address - 3

(Format:3001::1)

Prefix Length:

TP-LINK Omada TL-SG2008P - Global Address - 4

(1-64)

Cancel

Create

Address Format Select the global address format according to your needs.

EUI-64: Indicates that you only need to specify an address prefix, then the system will create a global address automatically.

Not EUI-64: Indicates that you have to specify an intact global address.

Global Address

When EUI-64 is selected, please input the address prefix here, otherwise, please input an intact IPv6 address here.

Prefix Length Configure the prefix length of the global address.

3) View the global address entry in the Global Address Table.

Global Address View or modify the global address.
Prefix Length View or modify the prefix length of the global address.
Type Displays the configuration mode of the global address.
Manual: Indicates that the corresponding address is configured manually.
Auto: Indicates that the corresponding address is created automatically using the RA message or obtained from the DHCPv6 Server.
Preferred LifetimeDisplays the preferred lifetime of the global address.
Preferred lifetime is the length of time that a valid IPv6 address is preferred. When the preferred time expires, the address becomes deprecated but still can be used, and you need to switch to another address.
Valid Lifetime Displays the valid lifetime of the global address.
Valid lifetime is the length of time that an IPv6 address is in the valid state. When the valid lifetime expires, the address become invalid and can be no longer usable.
Status Displays the status of the link-local address. An IPv6 address cannot be used before pass the DAD (Duplicate Address Detection), which is used to detect the address conflicts. In the DAD process, the IPv6 address may in three different status:
Normal: Indicates that the global address passes the DAD and can be normally used.
Try: Indicates that the global address is in the progress of DAD and cannot be used right now.
Repeat: Indicates that the global address is duplicated, this address is already used by another node. This address cannot be used by the interface.

2.1.4 Viewing Detail Information of the Interface

In Figure 2-1 you can view the corresponding interface entry you have created in the Interface List section. On the corresponding interface entry, click Detail to load the following page and view the detail information of the interface.

Figure 2-4 Viewing the detail information of the interface

Interface ID:VLAN1
Detail InformationInterface Setting Detail Information
Interface ID:1MTU is 1500 byte
IP Address Mode:StaticDirected broadcast forwarding is Disabled
IP Address:192.168.0.1ICMP redirects are never sent
Subnet Mask:255.255.255.0ICMP unreachables are never sent
Admin Status:EnabledICMP mask replies are never sent
Interface Status:Up
Line Protocol Status:Up
Secondary IP:
IPv6 Address Mode:EnabledMTU is 1500 byte
Link-Local Address:fe80::20a:ebff:fe13:a23aND DAD is Enabled
Admin Status:EnabledND retrans timer is 1000 ms
IPv6 Interface Status:UpND reachable time is 30000 ms
Line Protocol Status:UpGlobal address auto configuration via RA message is Enabled
IPv6 Address:Global address auto configuration via DHCPv6 Server is Disabled

2.2 Using the CLI

2.2.1 Creating an Layer 3 Interface

Follow these steps to create an Layer 3 interface. You can create a VLAN interface, a loopback interface, a routed port or a port-channel interface according to your needs.

Step 1 configure

Enter global configuration mode.

Step 2 Create a VLAN interface:

interface vlan vlan-id

vlan-id: Specify an IEEE 802.1Q VLAN ID that already exists, ranging from 1 to 4094.

Create a loopback interface:

interface loopback {id}

id: Specify the ID of the loopback interface, ranging from 1 to 64.

Create a routed port:

interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list}

Enter interface configuration mode.

port: Specify the Ethernet port number, for example 1/0/1.

port-list: Specify the list of Ethernet ports, for example 1/0/1-3, 1/0/5.

no switchport

Switch the Layer 2 port into the Layer 3 routed port.

Create a port-channel interface:

interface { port-cahnel port-channel| range port-channel port-channel-list }

Enter interface configuration mode.

port-channel: Specify the port channel, the valid value ranges from 1 to 14.

port-channel-list: Specify the list of the port-channel interface, for example 1-3, 5.

no switchport

Switch the port channel to an Layer 3 port channel interface.

Step 3 description

string

Specify a description for the Layer 3 interface.

string: The description of the Layer 3 interface, ranging from 1 to 32 characters.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to create a VLAN interface with a description of VLAN-2.

Switch#configure

Switch(config)#interface vlan 2

Switch(config-if)#description VLAN-2

Switch(config-if)#end

Switch#copy running-config startup-config

2.2.2 Configuring IPv4 Parameters of the Interface

Follow these steps to configure the IPv4 parameters of the interface.

Step 1 configure
Enter global configuration mode.

Step 2interface {interface-type}{interface-id}Enter Layer 3 interface configuration mode.interface-type: Type of the Layer 3 interface, including fastEthernet, gigabitEthernet, ten-gigabitEthernet, loopback and VLAN.interface-id: The interface ID.
Step 3 Automatically assign an IP Address for the interface via DHCP or BOOTP:ip address-alloc{dhcp | bootp}Specify the IP Address assignment mode of the interface.dhcp: Specify the Layer 3 interface to obtain an IPv4 address from the DHCP Server.bootp: Specify the Layer 3 interface to obtain an IPv4 address from the BOOTP Server.Manually assign an IP Address for the interface:ip address{ip-addr}{mask}[secondary]Configure the IP address and subnet mask for the specified interface manually.ip-addr. Specify these IP address of the Layer 3 interface.mask: Specify the subnet mask of the Layer 3 interface.secondary: Specify the interface's secondary IP address which allows you to have two logical subnets. If this parameter is omitted here, the configured IP address is the interface's primary address.
Step 4 show ip interface briefVerify the summary information of the Layer 3 interfaces.
Step 5 endReturn to privileged EXEC mode.
Step 6 copy running-config startup-configSave the settings in the configuration file.

The following example shows how to configure the IPv4 parameters of a routed port, including setting a static IP address for the port and enabling the Layer 3 capabilities:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#no switchport

Switch(config-if)#ip address 192.168.0.100 255.255.255.0

Switch(config-if)#show ip interface brief

InterfaceIP-AddressMethodStatusProtocolShutdown
Gi1/0/1192.168.0.100/24StaticUpUpno

Switch(config-if)#end

Switch#copy running-config startup-config

2.2.3 Configuring IPv6 Parameters of the Interface

Follow these steps to configure the IPv6 parameters of the interface.

Step 1 configure
Enter global configuration mode.

Step 2 interface {interface-type}{interface-id}
Enter Layer 3 interface configuration mode.
interface-type: Type of the Layer 3 interface, including fastEthernet, gigabitEthernet, ten-gigabitEthernet, loopback and VLAN.
interface-id: The interface ID.

Step 3 ipv6 enable
Enable the IPv6 feature on the specified Layer 3 interface. By default, it is enabled on VLAN interface 1. IPv6 function can only be enabled on one Layer 3 interface at a time.
Step 4 Configure the IPv6 link-local address for the specified interface:
Manually configure the ipv6 link-local address for the specified interface: ipv6 address ipv6-addr link-local ipv6-addr: Specify the link-local address of the interface. It should be a standardized IPv6 address with the prefix fe80::/10, otherwise this command will be invalid.
Automatically configure the ipv6 link-local address for the specified interface: ipv6 address autoconfig

Step 5 Configure the IPv6 global address for the specified interface:

Automatically configure the interface's global IPv6 address via RA message: ipv6 address ra

Configure the interface's global IPv6 address according to the address prefix and other configuration parameters from its received RA (Router Advertisement) message.

Automatically configure the interface's global IPv6 address via DHCPv6 server: ipv6 address dhcp

Enable the DHCPv6 Client function. When this function is enabled, the Layer 3 interface will try to obtain the IPv6 address from DHCPv6 server.

Manually configure the interface's global IPv6 address:

ipv6 address ipv6-addr

ipv6-addr: The Global IPv6 address with network prefix, for example 3ffe::1/64. ipv6 address ipv6-addr eui-64

Specify a global IPv6 address with an extended unique identifier (EUI) in the low-order 64 bits of the IPv6 address. Specify only the network prefix; the last 64 bits are automatically computed from the switch MAC address. This enables IPv6 processing on the interface.

Step 6 show ipv6 interface

Verify the configured ipv6 information of the interface.

Step 7 end

Return to privileged EXEC mode.

Step 8 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable the IPv6 function and configure the IPv6 parameters of a VLAN interface:

Switch#configure

Switch(config)#interface vlan 2

Switch(config-if)#ipv6 enable

Switch(config-if)#ipv6 address autoconfig

Switch(config-if)#ipv6 address dhcp

Switch(config-if)#show ipv6 interface

Vlan2 is up, line protocol is up

IPv6 is enable, Link-Local Address: fe80::20a:ebff:fe13:237b[NOR]

Global Address RA: Disable

Global Address DHCPv6: Enable

Global unicast address(es): ff02::1:ff13:237b

Joined group address(es): ff02::1

ICMP error messages limited to one every 1000 milliseconds

ICMP redirects are enable

MTU is 1500 bytes

ND DAD is enable, number of DAD attempts: 1

ND retrans timer is 1000 milliseconds

ND reachable time is 30000 milliseconds

Switch(config-if)#end

Switch#copy running-config startup-config

3 Configuration Example

3.1 Network Requirement

The administrator need to allow the hosts in VLANs can access the internet. The topology is shown as below.

Figure 3-1 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirement - 1

flowchart
graph TD
    A["Internet"] --> B["Router"]
    B --> C["Switch"]
    C --> D["VLAN 2"]
    C --> E["VLAN 10"]
    C --> F["..."]

3.2 Configuration Scheme

For the hosts in VLANs are seperated at layer 2. To make it possible for these host to access the internet, we need to configure a VLAN interface on the switch for each VLAN. The VLAN interface can be considered as the default gateway for the hosts in the VLAN. All the requests to internet are sent to the VLAN interface first, then the VLAN interface will forward the packets to the internet according to the routing table.

Demonstrated with T1600G-28TS, this chapter provides configuration procedures in two ways: using the GUI and using the CLI.

3.3 Using the GUI

For the configurations for all the VLANs are similar, here we only take the configuration of VLAN interface for VLAN 2 as an example.

1) Go to L2 FEATURES > VLAN > 802.1Q VLAN to create VLAN 2. Add port 1/0/2 to VLAN 2 with its egress rule as Untagged.

Table 3-2 Create VLAN 2
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image VLAN Config VLAN ID: 2 (2-4094, format: 2,4-5.8) VLAN Name: (1-16 characters) Untagged Ports Port 1/0/2 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Tagged Ports Port (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Cancel Create

2) Go to L3 FEATURES > Interface to enable IPv4 routing (enabled by default), then click Add to create VLAN interface 2. Here we choose the IP address mode as Static and manually assign an IP address 192.168.2.1 to the interface.

Table 3-3 Create VLAN Interface 2
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image Interface Config Interface ID: VLAN 2 (1-4094) IP Address Mode: None Static DHCP BOOTP IP Address: 192.168.2.1 (Format: 192.168.0.1) Subnet Mask: 255.255.255.0 (Format: 255.255.255.0) Admin Status: Enable Interface Name: (Optional: 1-16 characters) Cancel Create

3) Click save the settings.

3.4 Using the CLI

1) Create VLAN 2 and add port 1/0/2 to VLAN 2 with its egress rule as Untagged.

Switch#configure

Switch(config)#vlan 2

Switch(config-vlan)#exit

Switch(config)#interface gigabitEthernet 1/0/2

Switch(config-if)#switchport general allowed vlan 2 untagged

Switch(config-if)#exit

2) Create VLAN interface 2 for VLAN 2. Configure the IP address of VLAN interface 2 as 192.168.2.1.

Switch(config)#interface vlan 2

Switch(config-if)#ip address 192.168.2.1 255.255.255.0

Switch(config-if)#end

Switch#copy running-config startup-config

Verify the VLAN Interface Configurations

Verify the configurations of VLAN interface 2.

Switch#show interface vlan 2

VLAN2 is down, line protocol is down

Hardware is CPU Interface, address is 00:0a:eb:13:a2:98

ip is 192.168.2.1/24

4 Appendix: Default Parameters

Default settings of interface are listed in the following tables.

Table 4-1 Default Settings of Routing Config

Parameter Default Setting
IPv4 Routing Enabled
IPv6 Routing Disabled

Table 4-2 Configuring the IPv4 Parameters of the Interface

Parameter Default Setting
Interface ID VLAN
IP Address Mode None
Admin Status Enabled

Table 4-3 Configuring the IPv6 Parameters of the Interface

Parameter Default Setting
Admin Status Enabled
IPv6 Enable Enabled
Link-local Address Mode Auto
Enable global address auto configuration via RA messageEnabled
Enable global address auto configuration via DHCPv6 ServerDisabled

Part 19

Configuring Routing

CHAPTERS

  1. Overview
  2. IPv4 Static Routing Configuration
  3. IPv6 Static Routing Configuration
  4. Viewing Routing Table
  5. Example for Static Routing

1 Overview

Routing table is used for a Layer 3 device (in this configuration guide, it means the switch) to forward packets to the correct destination. When the switch receives packets of which the source IP address and destination IP address are in different subnets, it will check the routing table, find the correct outgoing interface then forward the packets.

The routing table mainly contains two types of routing entries: dynamic routing entries and static routing entries.

Dynamic routing entries are automatically generated by the switch. The switch use dynamic routing protocols to automatically calculate the best route to forward packets.

Static routing entries are manually added none-aging routing entries. In a simple network with a small number of devices, you only need to configure static routes to ensure that the devices from different subnets can communicate with each other. On a complex large-scale network, static routes ensure stable connectivity for important applications because the static routes remain unchanged even when the topology changes.

The switch supports IPv4 static routing and IPv6 static routing configuration.

2 IPv4 Static Routing Configuration

2.1 Using the GUI

Choose the menu L3 FEATURES > Static Routing > IPv4 Static Routing and click to load the following page.

Figure 2-1 Configuring the IPv4 Static Routing
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image IPv4 Static Routing Destination: (Format: 10.10.10.0) Subnet Mask: (Format: 255.255.255.0) Next Hop: (Format: 192.168.0.2) Distance: (Optional. range: 1-255) Cancel Create

Configure the corresponding parameters to add an IPv4 static routing entry. Then click Create.

Destination Specify the destination IPv4 address of the packets.
Subnet Mask Specify the subnet mask of the destination IPv4 address.
Next Hop Specify the IPv4 gateway address to which the packet should be sent next.
DistanceSpecify the administrative distance, which is the trust rating of a routing entry. A higher value means a lower trust rating. Among the routes to the same destination, the route with the lowest distance value will be recorded in the IPv4 routing table.The valid value ranges from 1 to 255 and the default value is 1.

2.2 Using the CLI

Follow these steps to create an IPv4 static route.

Step 1 configure

Enter global configuration mode.

Step 2 ip route {

dest-address}{mask}{next-hop-address}[distance]

Add an IPv4 static route.

dest-address: Specify the destination IPv4 address of the packets.

mask: Specify the subnet mask of the destination IPv4 address.

next-hop-address: Specify the IPv4 gateway address to which the packet should be sent next.

distance: Specify the administrative distance, which is a rating of the trustworthiness of the routing information. A higher value means a lower trust rating. When more than one routing protocols have routes to the same destination, only the route that has the shortest distance will be recorded in the IP routing table. The valid values are from 1 to 255 and the default value is 1.

Step 3 show ip route [static | connected]

Verify the IPv4 route entries of the specified type.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to create an IPv4 static route with the destination IP address as 192.168.2.0, the subnet mask as 255.255.255.0 and the next-hop address as 192.168.0.2:

Switch#configure

Switch(config)#ip route 192.168.2.0 255.255.255.0 192.168.0.2

Switch(config)#show ip route

Codes: C - connected, S - static

* - candidate default

C 192.168.0.0/24 is directly connected, Vlan1

S 192.168.2.0/24 [1/0] via 192.168.0.2, Vlan1

Switch(config)#end

Switch#copy running-config startup-config

3 IPv6 Static Routing Configuration

3.1 Using the GUI

Choose the menu L3 FEATURES > Static Routing > IPv6 Static Routing > IPv6 Static Routing Table and click to load the following page.

Figure 3-1 Configuring the IPv6 Static Routing
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image IPv6 Static Routing IPv6 Address: (Format: 2001::) Prefix Length: (Format: 64. range: 0-128) Next Hop: (Format: 3001::2) Distance: (Optional. range: 1-255) Cancel Create

Configure the corresponding parameters to add an IPv6 static routing entry. Then click Create.

IPv6 Address Specify the destination IPv6 address of the packets.
Prefix Length Specify the prefix length of the IPv6 address.
Next Hop Specify the IPv6 gateway address to which the packet should be sent next.
DistanceSpecify the administrative distance, which is the trust rating of a routing entry. A higher value means a lower trust rating. Among the routes to the same destination, the route with the lowest distance value will be recorded in the IPv6 routing table.The valid value ranges from 1 to 255 and the default value is 1

3.2 Using the CLI

Follow these steps to enable IPv6 routing function and create an IPv6 static route.

Step 1 configure

Enter global configuration mode.

Step 2 ipv6 routing

Enable the IPv6 routing function on the specified Layer 3 interface.

Step 3 ipv6 route {

ipv6-dest-address} { next-hop-address } [distance ]

Add an IPv6 static route.

ipv6-dest-address: Specify the destination IPv6 address of the packets, in the format of X:X:X:X::X/<0-128>.

next-hop-address: Specify the IPv6 gateway address to which the packet should be sent next.

distance: Specify the administrative distance, which is a rating of the trustworthiness of the routing information. A higher value means a lower trust rating. When more than one routing protocols have routes to the same destination, only the route that has the shortest distance will be recorded in the IP routing table. The valid values are from 1 to 255 and the default value is 1.

Step 4 show ipv6 route [static | connected]

Verify the IPv6 route entries of the specified type.

Step 5 end

Return to privileged EXEC mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to create an IPv6 static route with the destination IP address as 3200::/64 and the next-hop address as 3100::1234:

Switch#configure

Switch(config)#ipv6 route 3200::/64 3100::1234

Switch(config)#show ipv6 route static

Codes: C - connected, S - static

* - candidate default

C 3000::/64 is directly connected, Vlan1

S 3200::/64 [1/0] via 3100::1234, Vlan2

Switch(config)#end

Switch#copy running-config startup-config

4 Viewing Routing Table

You can view the routing tables to learn about the network topology. The switch supports IPv4 routing table and IPv6 routing table.

4.1 Using the GUI

4.1.1 Viewing IPv4 Routing Table

Choose the menu L3 FEATURES > Routing Table > IPv4 Routing Table > IPv4 Routing Information Summary to load the following page.

Figure 4-1 Viewing IPv4 Routing Table

ProtocolDestination NetworkNext HopDistanceMetricInterface Name
Connected192.168.0.0/24192.168.0.2601
Static192.168.30.0/24192.168.0.3650
Total: 2

View the IPv4 routing entries.

Protocol Displays the type of the routing entry.

Connected: The destination network is directed connected to the switch.

Static: The routing entry is a manually added static routing entry.

Destination NetworkDisplays the destination IP address and subnet mask.
Next Hop Displays the IPv4 gateway address to which the packet should be sent next.
DistanceDisplays the administrative distance, which is the trust rating of a routing entry. A higher value means a lower trust rating. Among the routes to the same destination, the route with the lowest distance value will be recorded in the IPv6 routing table.
Metric Displays the metric to reach the destination IP address.
Interface Name Displays the name of the gateway interface.

4.1.2 Viewing IPv6 Routing Table

Choose the menu L3 FEATURES> Routing Table > IPv6 Routing Table > IPv6 Routing Information Summary to load the following page.

Figure 4-2 Viewing IPv6 Routing Table

Protocol Destination Network Next Hop Distance Metric Interface Name
No Entries in this table.
Total: 0

View the IPv6 routing entries.

Protocol Displays the type of the routing entry.
Connected: The destination network is directed connected to the switch.
Static: The routing entry is a manually added static routing entry.
Destination NetworkDisplays the destination IPv6 address and subnet mask.
Next Hop Displays the IPv6 gateway address to which the packet should be sent next.
DistanceDisplays the administrative distance, which is the trust rating of a route higher value means a lower trust rating. Among the routes to the same the route with the lowest distance value will be recorded in the IPv6 routine.
Metric Displays the metric to reach the destination IPv6 address.
Interface Name Displays the name of the gateway interface.

4.2 Using the CLI

4.2.1 Viewing IPv4 Routing Table

On privileged EXEC mode or any other configuration mode, you can use the following command to view IPv4 routing table:

show ip route [static | connected]

View the IPv4 route entries of the specified type. If not specified, all types of route entries will be displayed.

static: View the static routes.

connected: View the connected routes.

4.2.2 Viewing IPv6 Routing Table

On privileged EXEC mode or any other configuration mode, you can use the following command to view IPv6 routing table:

show ipv6 route [static | connected]

View the IPv6 route entries of the specified type. If not specified, all types of route entries will be displayed.

static: View the static IPv6 routes.

connected: View the connected IPv6 routes.

5 Example for Static Routing

5.1 Network Requirements

As shown below, Host A and Host B are on different network segments. To meet business needs, Host A and Host B need to establish a connection without using dynamic routing protocols to ensure stable connectivity.

Figure 5-1 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph LR
    A["Host A\n10.1.1.100/24"] -->|Gi1/0/1\n10.1.1.1/24| B["Switch A Switch B"]
    B -->|Gi1/0/2\n10.1.10.1/24| C["Switch B"]
    C -->|Gi1/0/1\n10.1.10.2/24| D["Switch B"]
    D -->|Gi1/0/2\n10.1.2.1/24| E["Host B\n10.1.2.100/24"]

5.2 Configuration Scheme

To implement this requirement, you can configure the default gateway of host A as 10.1.1.1/24, the default gateway of host B as 10.1.2.1/24, and configure IPv4 static routes on Switch A and Switch B so that hosts on different network segments can communicate with each other.

Demonstrated with T1600G-28TS, the following sections provide configuration procedure in two ways: using the GUI and using the CLI.

5.3 Using the GUI

The configurations of Switch A and Switch B are similar. The following introductions take Switch A as an example.

1) Choose the menu L3 FEATURES > Interface to create a routed port Gi1/0/1 with the mode as static, the IP address as 10.1.1.1, the mask as 255.255.255.0 and the admin status as Enable. Create a routed port Gi1/0/2 with the mode as static, the IP address as 10.1.10.1, the mask as 255.255.255.0 and the admin status as Enable.

Figure 5-2 Create a Routed Port Gi1/0/1 for Switch A
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Interface Interface ID: Routed Port 1/0/1 (Format: 1/0/1) UNIT1 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 IP Address Mode: None Static DHCP BOOTP IP Address: 10.1.1.1 (Format: 192.168.0.1) Subnet Mask: 255.255.255.0 (Format: 255.255.255.0) Admin Status: Enable Interface Name: (Optional. 1-16 characters) Cancel Create

Figure 5-3 Create a Routed Port Gi1/0/2 for Switch A

TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image Interface Interface ID: Routed Port 1/0/2 (Format: 1/0/1) UNIT1 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 IP Address Mode: None Static DHCP BOOTP IP Address: 10.1.10.1 (Format: 192.168.0.1) Subnet Mask: 255.255.255.0 (Format: 255.255.255.0) Admin Status: Enable Interface Name: (Optional. 1-16 characters) Cancel Create

2) Choose the menu L3 FEATURES > Static Routing > IPv4 Static Routing to load the following page. Add a static routing entry with the destination as 10.1.2.0, the subnet

mask as 255.255.255.0 and the next hop as 10.1.10.2. For switch B, add a static route entry with the destination as 10.1.1.0, the subnet mask as 255.255.255.0 and the next hop as 10.1.10.1.

Figure 5-4 Add a Static Route for Switch A
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image IPv4 Static Routing Destination: 10.1.2.0 (Format: 10.10.10.0) Subnet Mask: 255.255.255.0 (Format: 255.255.255.0) Next Hop: 10.1.10.2 (Format: 192.168.0.2) Distance: (Optional range: 1-255) Cancel Create

5.4 Using the CLI

The configurations of Switch A and Switch B are similar. The following introductions take Switch A as an example.

1) Create a routed port Gi1/0/1 with the mode as static, the IP address as 10.1.1.1, the mask as 255.255.255.0 and the admin status as Enable. Create a routed port Gi1/0/2 with the mode as static, the IP address as 10.1.10.1, the mask as 255.255.255.0 and the admin status as Enable.

Switch_A#configure

Switch_A(config)#interface gigabitEthernet 1/0/1

Switch_A(config-if)#no switchport

Switch_A(config-if)#ip address 10.1.1.1 255.255.255.0

Switch_A(config-if)#exit

Switch_A(config)#interface gigabitEthernet 1/0/2

Switch_A(config-if)#no switchport

Switch_A(config-if)#ip address 10.1.10.1 255.255.255.0

2) Add a static route entry with the destination as 10.1.2.0, the subnet mask as 255.255.255.0 and the next hop as 10.1.10.2. For switch B, add a static route entry with the destination as 10.1.1.0, the subnet mask as 255.255.255.0 and the next hop as 10.1.10.1.

Switch_A#configure

Switch_A(config)#ip route 10.1.2.0 255.255.255.0 10.1.10.2

Switch_A(config)#end

Switch_A#copy running-config startup-config

Verify the Configurations

Switch A

Verify the static routing configuration:

Switch_A#show ip route

Codes: C - connected, S - static

* - candidate default

C 10.1.1.0/24 is directly connected, Vlan10

C 10.1.10.0/24 is directly connected, Vlan20

S 10.1.2.0/24 [1/0] via 10.1.10.2, Vlan20

Switch B

Verify the static routing configuration:

Switch_B#show ip route

Codes: C - connected, S - static

* - candidate default

C 10.1.2.0/24 is directly connected, Vlan30

C 10.1.10.0/24 is directly connected, Vlan20

S 10.1.1.0/24 [1/0] via 10.1.10.1, Vlan20

■ Connectivity Between Switch A and Switch B

Run the ping command on switch A to verify the connectivity:

Switch_A#ping 10.1.2.1

Pinging 10.1.2.1 with 64 bytes of data :

Reply from 10.1.2.1 : bytes=64 time<16ms TTL=64

Reply from 10.1.2.1 : bytes=64 time<16ms TTL=64

Reply from 10.1.2.1 : bytes=64 time<16ms TTL=64

Reply from 10.1.2.1 : bytes=64 time<16ms TTL=64

Ping statistics for 10.1.2.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)

Approximate round trip times in milli-seconds:

Minimum = 1ms, Maximum = 3ms, Average = 1ms

Part 20

Configuring DHCP Service

CHAPTERS

  1. DHCP
  2. DHCP Server Configuration
  3. DHCP Relay Configuration
  4. DHCP L2 Relay Configuration
  5. Configuration Examples
  6. Appendix: Default Parameters

1 DHCP

1.1 Overview

DHCP (Dynamic Host Configuration Protocol) is widely used to automatically assign IP addresses and other network configuration parameters to network devices, enhancing the utilization of IP address.

1.2 Supported Features

The supported DHCP features of the switch include DHCP Server, DHCP Relay and DHCP L2 Relay.

DHCP Server

DHCP Server is used to dynamically assign IP addresses, default gateway and other parameters to DHCP clients. As the following figure shows, the switch acts as a DHCP server and assigns IP addresses to the clients.

Figure 1-1 Application Scenario of DHCP Server
TP-LINK Omada TL-SG2008P - DHCP Server - 1

flowchart
graph LR
    A["Switch DHCP Server"] --> B["DHCPC clients"]
    B --> C["Client 1"]
    B --> D["Client 2"]
    B --> E["Client 3"]

DHCP Relay

DHCP Relay is used to process and forward DHCP packets between different subnets or VLANs.

DHCP clients broadcast DHCP request packets to require for IP addresses. Without this function, clients cannot obtain IP addresses from a DHCP server in the different LAN because the broadcast packets can be transmitted only in the same LAN. To equip each LAN with a DHCP server can solve this problem, but the costs of network construction will be increased and the management of central network will become inconvenient.

A device with DHCP Relay function is a better choice. It acts as a relay agent and can forward DHCP packets between DHCP clients and DHCP servers in different LANs. Therefore, DHCP clients in different LANs can share one DHCP server.

DHCP Relay includes three features: Option 82, DHCP Interface Relay and DHCP VLAN Relay.

Option 82

Option 82 is called the DHCP Relay Agent Information Option. It provides additional security and a more flexible way to allocate network addresses compared with the traditional DHCP.

When enabled, the DHCP relay agent can inform the DHCP server of some specified information of clients by inserting an Option 82 payload to DHCP request packets before forwarding them to the DHCP server, so that the DHCP server can distribute the IP addresses or other parameters to clients based on the payload. In this way, Option 82 prevents DHCP client requests from untrusted sources. Besides, it allows the DHCP server to assign IP addresses of different address pools to clients in different groups.

An Option 82 has two sub-options, namely, the Agent Circuit ID and Agent Remote ID. The information that the two sub-options carry depends on the settings of the DHCP relay agent, and are different among devices from different vendors. To allocate network addresses using Option 82, you need to define the two sub-options on the DHCP relay agent, and create a DHCP class on the DHCP server to identify the Option 82 payload.

TP-Link switches preset a default circuit ID and remote ID in TLV (Type, Length, and Value) format. You can also configure the format to include Value only and customize the Value.

Table 1-1 and Table 1-2 show the packet formats of the Agent Circuit ID and Agent Remote ID, respectively.

Table 1-1 Packet Formats of the Agent Circuit ID with Different Option 82 Settings

Option 82 Settings*Type (Hex)*Length (Hex) *Value
*FormatCircuit ID Customization
Normal (TLV)Disabled 00 04 Default circuit ID
Enabled 01 Length of the customized circuit ID Customized circuit ID
Private (Only the value)Disabled - - Default circuit ID
Enabled - - Customized circuit ID

Table 1-2 Packet Formats of the Agent Remote ID with Different Option 82 Settings

Option 82 Settings*Type (Hex)*Length (Hex) *Value
*FormatRemote ID Customization
Normal (TLV)Disabled 00 06Default remote ID
Enabled 01 Length of the customized remote IDCustomized remote ID
Private (Only the value)Disabled --Default remote ID
Enabled --Customized remote ID

\*Format

Indicates the packet format of the sub-option field. Two options are available:

■ Normal: Indicates the field consists of three parts: Type, Length, and Value (TLV).
■ Private: Indicates the field consists of the value only.

\*Type

A one-byte field indicating whether the Value field is customized or not. 00 in hexadecimal means the Value field is not customized (uses the default circuit/remote ID) while 01 in hexadecimal means it is customized.

\*Length

A one-byte field indicating the length of the Value field. The length of the default circuit ID is 4 bytes and that of default remote ID is 6 bytes. For the customized circuit ID and remote ID, the length is variable, ranging from 1 to 64 bytes.

\*Value

Indicates the value of the sub-option. The switch has preset a default circuit ID and remoter ID. You can also customize them with Circuit ID Customization and Remote ID Customization enabled.

■ Default circuit ID: A 4-byte value which consists of 2-byte VLAN ID and 2-byte Port ID. The VLAN ID indicates which VLAN the DHCP client belongs to, and the Port ID indicates which port the DHCP client is connected to.
For example, if the DHCP client is connected to port 1/0/1 in VLAN 2, this field is 00:02:00:01 in hexadecimal.
■ Default remote ID: A 6-byte value which indicates the MAC address of the DHCP relay agent.
- Customized circuit/remote ID: You can configure a string using up to 64 characters. The switch encodes the string using ASCII. When configuring your DHCP server to identify the string, use the correct notation that is used by your DHCP server to represent ASCII strings, or convert it into hexadecimal format if necessary.

Tips:

As shown in Table 1-1 and Table 1-2, by default, the circuit ID records the ports of the DHCP relay agent that are connected to the clients and the VLANs that the clients belong to, and the remote ID records the MAC address of the DHCP relay agent. That is, the two sub-options together record the location of the clients. To record the accruate location of clients, configure Option 82 on the switch which is closest to the clients.

DHCP Interface Relay

DHCP Interface Relay allows clients to obtain IP addresses from a DHCP server in a different LAN. In DHCP Interface Relay, you can specify a DHCP server for the Layer 3 interface that the clients are connected to. When receiving DHCP packets from clients, the switch fills the corresponding interface's IP address in the Relay Agent IP Address field of the DHCP packets, and forwards the packets to the DHCP server. Then the DHCP server

can assign IP addresses that are in the same subnet with the Relay Agent IP Address to the clients.

The switch supports specifying a DHCP server for multiple Layer 3 interfaces, which makes it possible to assign IP addresses to clients in different subnets from the same DHCP server.

As the following figure shows, the IP address of VLAN 20 is 192.168.2.1/24 and that of the routed port Gi1/0/1 is 192.168.3.1/24. With DHCP Interface VLAN configured, the switch fills in the Relay Agent IP Address field of the DHCP packets with the IP address of VLAN 20 (192.168.2.1/24) when applying for IP addresses for clients in VLAN 20, and fills with the IP address of Gi1/0/1 (192.168.3.1/24) when applying for an IP address for PC 1. As a result, the DHCP server will assign IP addresses in Pool A (the same subnet with the IP address of VLAN 20) to clients in VLAN 20, and assign an IP address in Pool B (the same subnet with the Gi1/0/1) to PC 1.

Figure 1-2 Application Scenario of DHCP Interface Relay
TP-LINK Omada TL-SG2008P - DHCP Interface Relay - 1

flowchart
graph LR
    A["DHCP Clients\nVLAN 20\n192.168.2.0/24"] -->|VLAN 20\n192.168.2.1/24| B["Switch\nDHCP Relay"]
    C["PC 1\nDHCP Client\n192.168.3.2/24"] -->|Gi1/0/1\nRouted Port\n192.168.3.1/24| B
    D["DHCP Server\nPool A:192.168.2.0/24\nPool B:192.168.3.0/24"] --> B

DHCP VLAN Relay

DHCP VLAN Relay allows clients in different VLANs to obtain IP addresses from the DHCP server using the IP address of a single agent interface.

In DHCP Interface Relay, to achieve this goal, you need to create a Layer 3 interface for each VLAN to ensure the reachability.

In DHCP VLAN Relay, you can simply specify a Layer 3 interface as the default agent interface for all VLANs. The switch fills this default agent interface's IP address in the Relay Agent IP Address field of the DHCP packets from all VLANs.

As the following figure shows, no IP addresses are assigned to VLAN 10 and VLAN 20, but a default relay agent interface is configured with the IP address 192.168.2.1/24. The switch fills in the Relay Agent IP Address field of the DHCP packets with the IP address of the default agent interface (192.168.2.1/24) when applying for IP addresses for clients in both VLAN 10 and VLAN 20. As a result, the DHCP server will assign IP addresses on 192.168.2.0/24 (the same subnet with the IP address of the default agent interface) to clients in both VLAN 10 and VLAN 20.

Figure 1-3 Application Scenario of DHCP VLAN Relay
TP-LINK Omada TL-SG2008P - DHCP VLAN Relay - 1

flowchart
graph TD
    A["DHCP Server"] --> B["DHCP Relay"]
    B --> C["DHCP Clients VLAN 10 192.168.2.0/24"]
    B --> D["DHCP Clients VLAN 20 192.168.2.0/24"]
    B --> E["Default Agent Interface: 192.168.2.1/24"]

TP-LINK Omada TL-SG2008P - DHCP VLAN Relay - 2

Note:

  • If the VLAN already has an IP address, the switch will use the IP address of the VLAN as the relay agent IP address. The default relay agent IP address will not take effect.
  • DHCP VLAN Relay will not work on routed ports or port channel interfaces, because they are not associated with any particular VLAN.

DHCP L2 Relay

Unlike DHCP relay, DHCP L2 Relay is used in the situation that the DHCP server and clients are in the same VLAN. In DHCP L2 Relay, in addition to normally assigning IP addresses to clients from the DHCP server, the switch can inform the DHCP server of some specified information, such as the location information, of clients by inserting an Option 82 payload to DHCP request packets before forwarding them to the DHCP server. This allows the DHCP server which supports Option 82 can set the distribution policy of IP addresses and other parameters, providing a more flexible way to distribute IP addresses.

Figure 1-4 Application Scenario of DHCP L2 Relay
TP-LINK Omada TL-SG2008P - DHCP L2 Relay - 1

flowchart
graph TD
    A["DHCP Server"] --> B["VLAN 1"]
    B --> C["Switch DHCP L2 Relay"]
    C --> D["DHCP Clients"]
    B --> E["DHCP Clients"]

2

DHCP Server Configuration

To complete DHCP server configuration, follow these steps:

1) Enable the DHCP Server feature on the switch.
2) Configure DHCP Server Pool.
3) (Optional) Manually assign static IP addresses for some clients.

2.1 Using the GUI

2.1.1 Enabling DHCP Server

Choose the menu L3 FEATURES > DHCP Service > DHCP Server > DHCP Server to load the following page.

Figure 2-1 Configure DHCP Server
TP-LINK Omada TL-SG2008P - Enabling DHCP Server - 1

text_image DHCP Server Pool Setting Manual Binding DHCP Client List Packet Statistics Global Config DHCP Server: Enable Option 60: (Optional. 1-64 characters) Option 138: (Optional. Format:192.168.0.1) Ping Time Config Ping Packets: 1 (0-10 packets, 0 for disabling ping) Ping Timeout: 100 (100-10000 milliseconds) Apply Apply Excluded IP Address Config Index Starting IP Address Ending IP Address No entries in this table. Total: 0

Follow these steps to configure DHCP Server:

1) In the Global Config section, enable DHCP Server. Click Apply.

DHCP Server Enable DHCP Server.

Option 60(Optional) Specify the Option 60 for device identification. Mostly it is used for the scenarios that the APs (Access Points) apply for different IP addresses from different servers according to the needs.If an AP requests Option 60, the server will respond a packet containing the Option 60 configured here. And then the AP will compare the received Option 60 with its own. If they are the same, the AP will accept the IP address assigned by the server. Otherwise, the assigned IP address will not be accepted.
Option 138 (Optional)Specify the Option 138, which should be configured as the management IP address of an AC (Access Control) device. If the APs in the local network request this option, the server will respond a packet containing this option to inform the APs of the AC's IP address.

2) In the Ping Time Config section, configure Ping Packets and Ping Timeout for ping tests. Click Apply.

Ping PacketsEnter the number of ping packets the server can broadcast to test whether the IP address is occupied. The valid values are from 1 to 10, and the default is 1.When the switch is configured as a DHCP server to dynamically assign IP addresses to clients, the switch will deploy ping tests to avoid IP address conflicts resulted from assigning IP addresses repeatedly.
Ping TimeoutSpecify the timeout period for ping tests in milliseconds. It ranges from 100 to 10000 ms, and the default is 100 ms.The DHCP server broadcasts an ICMP Echo Request (ping packet) to test whether an IP address is occupied or not. If there is no response within the timeout period, the server will broadcast the ping packet again. If the number of ping packets reaches the specified number without response, the server will assign the IP address. Otherwise, the server will record the IP address as a conflicted one and assign another IP address to the client.

3) In the Excluded IP Address Config section, click + Add to load the following page to specify the IP addresses that should not be assigned to the clients.

Figure 2-2 Configure Excluded IP Address
TP-LINK Omada TL-SG2008P - Enabling DHCP Server - 2

text_image Excluded IP Address Starting IP Address: (Format: 192.168.0.10) Ending IP Address: (Format: 192.168.0.10) Cancel Create

Enter the Starting IP Address and Ending IP Address to specify the range of reserved IP addresses. Click Create.

Starting IP

Address/ Ending IP Address

Specify the starting IP address and ending IP address of the excluded IP address range. If the starting IP address and ending IP address are the same, the server excludes only one IP address.

When configuring DHCP Server, you need to reserve certain IP addresses for each subnet, such as the default gateway address, broadcast address and DNS server address.

2.1.2 Configuring DHCP Server Pool

DHCP Server Pool defines the parameters that will be assigned to DHCP clients.

Choose the menu L3 FEATURES > DHCP Service > DHCP Server > Pool Setting and click

TP-LINK Omada TL-SG2008P - Configuring DHCP Server Pool - 1

TP-LINK Omada TL-SG2008P - Configuring DHCP Server Pool - 2

TP-LINK Omada TL-SG2008P - Configuring DHCP Server Pool - 3

TP-LINK Omada TL-SG2008P - Configuring DHCP Server Pool - 4

TP-LINK Omada TL-SG2008P - Configuring DHCP Server Pool - 5

TP-LINK Omada TL-SG2008P - Configuring DHCP Server Pool - 6

TP-LINK Omada TL-SG2008P - Configuring DHCP Server Pool - 7
Figure 2-3 Pool Setting

DHCP Server Pool

Pool Name:

Network Address:

Subnet Mask:

Lease Time:

Default Gateway:

DNS Server:

NetBIOS Server:

NetBIOS Node Type:

Next Server Address:

Domain Name:

Bootfile:

TP-LINK Omada TL-SG2008P - DHCP Server Pool - 1

(8 characters maximum)

(Format: 192.168.0.0)

(Format: 255.255.255.0)

(Optional. 1-2880 min, Default: 120)

(Optional, Format: 192.168.0.1)

(Optional. Format: 192.168.0.1)

(Optional. Format: 192.168.0.1)

(Optional, b/p/m/h/none)

(Optional. Format: 192.168.0.1)

(0 to 200 characters)

(0 to 128 characters)

TP-LINK Omada TL-SG2008P - DHCP Server Pool - 2

Configure the parameters for DHCP Server Pool. Then click Create.

Pool Name Specify a pool name for identification.
Network Address / Subnet MaskConfigure the network address and subnet mask of the DHCP server pool.The network address and subnet mask decide the range of the DHCP server pool.On the same subnet, all addresses can be assigned except the excluded addresses and addresses for special uses.
Lease TimeSpecify how long the client can use the IP address assigned from this address pool.It ranges from 1 to 2880 minutes, and the default is 120 minutes.
Default Gateway(Optional) Configure the default gateway of the DHCP server pool. You can create up to 8 default gateways for each DHCP server pool. If you leave this field blank, the DHCP server will not assign this parameter to clients.In general, you can configure the IP address of the VLAN interface as the default gateway address.
DNS Server(Optional) Specify the DNS server of the DHCP server pool. You can specify up to 8 DNS servers for each DHCP server pool. If you leave this field blank, the DHCP server will not assign this parameter to clients.In general, you can configure the IP address of the VLAN interface as the DNS server address.
NetBIOS Server(Optional) Specify the NetBIOS name server. You can specify up to 8 NetBIOS servers for each DHCP server pool. If you leave this field blank, the DHCP server will not assign this parameter to clients.When a DHCP client uses the Network NetBIOS (Basic Input Output System) protocol for communication, the host name must be mapped to IP address. NetBIOS name server can resolve host names to IP addresses.
NetBIOS Node Type(Optional) Specify the NetBIOS type for clients, which is the way of inquiring IP address resolution. If you leave this field blank, the DHCP server will not assign this parameter to clients.The following options are provided:b-node Broadcast: The client sends query messages via broadcast.p-node Peer-to-Peer: The client sends query messages via unicast.m-node Mixed: The client sends query messages via broadcast first. If it fails, the client will try again via unicast.h-node Hybrid: The client sends query messages via unicast first. If it fails, the client will try again via broadcast.
Next Server Address(Optional) Specify the IP address of a TFTP server for clients. If needed, clients can get the configuration file from the TFTP server for auto installation. If you leave this field blank, the DHCP server will not assign this parameter to clients.
Domain Name(Optional) Specify the domain name that clients should use when resolving host names via DNS. If you leave this field blank, the DHCP server will not assign this parameter to clients.
Bootfile(Optional) Specify the name of the bootfile. If needed, clients can get the bootfile from the TFTP server for auto installation. If you leave this field blank, the DHCP server will not assign this parameter to clients.

2.1.3 Configuring Manual Binding

Some devices like web servers require static IP addresses. To meet this requirement, you can manually bind the MAC address or client ID of the device to an IP address, and the DHCP server will reserve the bound IP address to this device at all times.

Choose the menu L3 FEATURES > DHCP Service > DHCP Server > Manual Binding and click to load the following page.

Figure 2-4 Manual Binding
TP-LINK Omada TL-SG2008P - Configuring Manual Binding - 1

text_image Manual Binding Pool Name: IP Address: Binding Mode: Client ID Client ID: (Format: 192.168.0.1) (Even number of characters, 4-200 length, in Hexadecimal) Cancel Create

Select a pool name and enter the IP address to be bound. Select a binding mode and finish the configuration accordingly. Click Create.

Pool Name Select a DHCP server pool from the drop-down list.

IP Address Enter the IP address to be bound to the client.

Binding Mode Select the binding mode:

Client ID: Bind the IP address to the client ID of the client.

Client ID in ASCII: Bind the IP address to the client ID in ASCII format.

Hardware Address: Bind the IP address to the MAC address of the client.

Client ID If you select Client ID as the binding mode, enter the client ID in this field.

Hardware Address If you select Hardware Address as the binding mode, enter the MAC address in this field.

Hardware Type If you select Hardware Address as the binding mode, select a hardware type. The hardware type includes Ethernet and IEEE802.

2.2 Using the CLI

2.2.1 Enabling DHCP Server

Follow these steps to enable DHCP Server and to configure ping packets and ping timeout.

Step 1 configure

Enter Global Configuration Mode.

Step 2 service dhcp server

Enable DHCP Server.

Step 3 ip dhcp server extend-option vendor-class-id vendor

(Optional) Specify the Option 60 for server identification. If a client requests Option 60, the server will respond a packet containing the Option 60 configured here. And then the client will compare the received Option 60 with its own. If they are the same, the client will accept the IP address assigned by the server. Otherwise, the assigned IP address will not be accepted.

vendor: Specify the Option 60 with 1 to 64 characters.

Step 4 ip dhcp server extend-option capwap-ac-ip ip-address

(Optional) Specify the Option 138, which should be configured as the management IP address of an AC (Access Control) device. If the APs (Access Points) in the local network request this option, the server will respond a packet containing this option to inform the APs of the AC's IP address.

ip-address: Specify the IP address of the AC device that controls the APs.

Step 5 ip dhcp server ping timeout value

Specify the timeout period for ping tests. The DHCP server broadcasts an ICMP Echo Request (ping packet) to test whether an IP address is occupied or not. If there is no response within the timeout period, the server will broadcast the ping packet again. If the number of ping packets reaches the specified number without response, the server will assign the IP address. Otherwise, the server will record the IP address as a conflicted IP address and assign another IP address to the client.

value: Specify the timeout period for ping tests in milliseconds. It ranges from 100 to 10000 ms, and the default is 100 ms.

Step 6 ip dhcp server ping packets num

Specify the number of ping packets the server can broadcast to test whether the IP address is occupied. When the switch is configured as a DHCP server to dynamically assign IP addresses to clients, the switch will deploy ping tests to avoid IP address conflicts resulted from assigning IP addresses repeatedly.

num: Enter the number of ping packets. The valid values are from 1 to 10, and the default is 1.

Step 7 ip dhcp server exclude-address start-ip-address end-ip-address

Specify the starting IP address and ending IP address of the excluded IP address range. If the starting IP address and the ending IP address are the same, the server excludes only one IP address.

When configuring DHCP Server, you need to reserve certain IP addresses for each subnet, such as default gateway address, broadcast address and DNS server address.

start-ip-address/end-ip-address: Specify the starting IP address and ending IP address.

Step 8 show ip dhcp server status

Verify the DHCP status, including whether it is enabled and the configuration of ping packet number and ping packet timeout.

Step 9 show ip dhcp server extend-option

Verify the configuration of the extended options.

Step 10 show ip dhcp server excluded-address

Verify the configuration of the excluded IP address.

Step 11 end

Return to Privileged EXEC Mode.

Step 12 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable DHCP Server globally on the switch, configure the number of ping packets as 2 and configure the timeout period for ping tests as 200 ms:

Switch#configure

Switch(config)#service dhcp server

Switch(config)#ip dhcp server ping packets 2

Switch(config)#ip dhcp server ping timeout 200

Switch(config)#show ip dhcp server status

DHCP server is enable.

Ping packet number: 2.

Ping packet timeout: 200 milliseconds.

Switch(config)#end

Switch#copy running-config startup-config

The following example shows how to configure the Option 60 as abc and Option 138 as 192.168.0.155:

Switch#configure

Switch(config)#ip dhcp server extend-option vendor-class-id abc

Switch(config)#ip dhcp server extend-option capwap-ac-ip 192.168.0.155

Switch(config)#show ip dhcp server extend-option

Option 60: abc

Option 138: 192.168.0.155

Switch(config)#end

Switch#copy running-config startup-config

The following example shows how to configure the 192.168.1.1 as the default gateway address and excluded IP address:

Switch#configure

Switch(config)#ip dhcp server excluded-address 192.168.1.1 192.168.1.1

Switch(config)#show ip dhcp server excluded-address

No. Start IP Address End IP Address


1 192.168.1.1 192.168.1.1

Switch(config)#end

Switch#copy running-config startup-config

2.2.2 Configuring DHCP Server Pool

Follow these steps to configure DHCP server pool:

Step 1 configure

Enter Global Configuration Mode.

Step 2 ip dhcp server pool

pool-name

Configure a name for the DHCP server pool for identification.

pool-name: Specify a pool name with 1 to 8 characters.

Step 3 network

network-address subnet-mask

Configure the network address and subnet mask of the DHCP server pool.

The network address and subnet mask decide the range of the DHCP server pool. On the same subnet, all addresses can be assigned except the excluded addresses and addresses for special uses.

network-address: Configure the network address of the DHCP server pool.

subnet-mask: Configure the subnet mask of the DHCP server pool.

Step 4 lease

lease-time

Specify how long the client can use the IP address assigned from this address pool.

lease-time: Enter the value of lease-time. It ranges from 1 to 2880 minutes, and the default is 120 minutes.

Step 5 default-gateway

gateway-list

(Optional) Configure the default gateway of the DHCP server pool. In general, you can configure the IP address of the VLAN interface as the default gateway address.

gateway-list: Specify the IP address of the default gateway. You can create up to 8 default gateways for each DHCP server pool.

Step 6 dns-serverdns-server-list(Optional) Specify the DNS server of the DHCP server pool. In general, you can configure the IP address of the VLAN interface as the DNS server address.dns-server-list: Specify the IP address of the DNS server. You can specify up to 8 DNS servers for each DHCP server pool.
Step 7 netbios-name-serverNBNS-list(Optional) Specify the NetBIOS name server. You can specify up to 8 NetBIOS servers for each DHCP server pool.When a DHCP client uses the Network NetBIOS (Basic Input Output System) protocol for communication, the host name must be mapped to IP address. NetBIOS name server can resolve host names to IP addresses.NBNS-list: Specify the IP address of the NetBIOS server. You can specify up to 8 NetBIOS servers for each DHCP server pool.
Step 8 netbios-node-typetype(Optional) Specify the NetBIOS type for the clients, which is the way of inquiring IP address resolution.type: Specify the NetBIOS type. The following options are provided:b-node: The client sends query messages via broadcast.p-node: The client sends query messages via unicast.m-node: The client sends query messages via broadcast first. If it fails, the client will try again via unicast.h-node: The client sends query messages via unicast first. If it fails, the client will try again via broadcast.
Step 9 next-serverip-address(Optional) Specify the IP address of a TFTP server for the clients. If needed, the clients can get the configuration file from the TFTP server for auto installation.ip-address: Specify the IP address of the TFTP server.
Step 10 domain-namedomainname(Optional) Specify the domain name that the clients should use when resolving host names via DNS.domainname: Specify the domain name with up to 200 characters.
Step 11 bootfilefile-name(Optional) Specify the name of the bootfile. If needed, the clients can get the bootfile from the TFTP server for auto installation.file-name: Specify the bootfile name with up to 128 characters.
Step 12 show ip dhcp server pool
Step 13 end
Return to Privileged EXEC Mode.

Step 14 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to create a DHCP server pool with the parameters shown in Table 2-1.

Table 2-1 Parameters for the DHCP Server Pool

Parameter Value
Pool Name pool 1
Network Address 192.168.1.0
Subnet Mask 255.255.255.0
Lease Time 180 minutes
Default Gateway 192.168.1.1
DNS Server 192.168.1.4
NetBIOS Server 192.168.1.19
NetBIOS Node Type B-node (Broadcast)
TFTP server192.168.1.30
Domain Namecom
Bootfilebootfile

Switch#configure

Switch(config)#ip dhcp server pool pool1

Switch(dhcp-config)#network 192.168.1.0 255.255.255.0

Switch(dhcp-config)#lease 180

Switch(dhcp-config)#default-gateway 192.168.1.1

Switch(dhcp-config)#dns-server 192.168.1.4

Switch(dhcp-config)#netbios-name-server 192.168.1.19

Switch(dhcp-config)#netbios-node-type b-node

Switch(dhcp-config)#next server 192.168.1.30

Switch(dhcp-config)#domain-name com

Switch(dhcp-config)#bootfile bootfile

Switch(dhcp-config)#show ip dhcp server pool

Pool Name: pool1

Network Address: 192.168.1.0

Subenet Mask: 255.255.255.0

Lease Time: 180

Default Gateway: 192.168.1.1

DNS Server: 192.168.1.4

Netbios Server: 192.168.1.19

Netbios Node Type: b-node

Next Server Address: 192.168.1.30

Domain Name: com

Bootfile Name: bootfile

Switch(dhcp-config)#end

Switch#copy running-config startup-config

2.2.3 Configuring Manual Binding

Some hosts, WWW server for example, requires a static IP address. To satisfy this requirement, you can manually bind the MAC address or client ID of the host to an IP address, and the DHCP server will reserve the bound IP address to this host at all times.

Follow these steps to configure Manual Binding:

Step 1 configure

Enter Global Configuration Mode.

Step 2 ip dhcp server pool

name

Create a DHCP server pool and enter DHCP Configuration Mode.

Step 3 Bind an IP address to a client:

address ip-address client-identifier client-id

Bind the specified IP address to the client with a specific hexadecimal client ID.

ip-address: Specify the IP address to be bound.

client-id: Specify the client ID in hexadecimal format.

address ip-address client-identifier client-id ascii

Bind the specified IP address to the client with a specific ASCII client ID.

ip-address: Specify the IP address to be bound.

client-id: Specify the client ID with ASCII characters.

address ip-address hardware-address hardware-address hardware-type { ethernet | ieee802 }

Bind the specified IP address to the client with a specific MAC address.

ip-address: Specify the IP address to be bound.

hardware-address: Enter the MAC address of the client.

ethernet | ieee802: Specify a hardware type for the client, either Ethernet or IEEE802.

Step 4 show ip dhcp server manual-binding

Verify the manual binding configuration.

Step 5 end

Return to Privileged EXEC Mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to bind the IP address 192.168.1.33 in pool1 (on the subnet of 192.168.1.0) to the host with the MAC address 74:D4:68:22:3F:34:

Switch#configure

Switch(config)#ip dhcp server pool pool1

Switch(dhcp-config)#address 192.168.1.33 hardware-address 74:d4:68:22:3f:34 hardware-type ethernet

Switch(dhcp-config)#show ip dhcp server manual-binding

Pool NameClient Id/Hardware AddressIP AddressHardware TypeBind Mode
----------------------------------------
pool174:d4:68:22:3f:34192.168.1.33EthernetMAC Address

Switch(dhcp-config)#end

Switch#copy running-config startup-config

3 DHCP Relay Configuration

To complete DHCP Relay configuration, follow these steps:

1) Enable DHCP Relay. Configure Option 82 if needed.
2) Specify DHCP server for the Interface or VLAN.

3.1 Using the GUI

3.1.1 Enabling DHCP Relay and Configuring Option 82

Choose the menu L3 FEATURES > DHCP Service > DHCP Relay > DHCP Relay Config to load the following page.

Figure 3-1 Enable DHCP Relay and Configure Option 82
TP-LINK Omada TL-SG2008P - Enabling DHCP Relay and Configuring Option 82 - 1

text_image DHCP Relay Config DHCP Interface Relay DHCP VLAN Relay Global Config DHCP Relay: Enable DHCP Relay Hops: 4 (1-10) DHCP Relay Time Threshold: 0 seconds (0-65535) Apply Option 82 Config UNIT1 LAGS Port Option 82 Support Option 82 Policy Format Circuit ID Customization Circuit ID Remote ID Customization Remote ID LAG 1/0/1 Disabled Keep Normal Disabled Disabled --- 1/0/2 Disabled Keep Normal Disabled Disabled --- 1/0/3 Disabled Keep Normal Disabled Disabled --- 1/0/4 Disabled Keep Normal Disabled Disabled --- 1/0/5 Disabled Keep Normal Disabled Disabled --- 1/0/6 Disabled Keep Normal Disabled Disabled --- 1/0/7 Disabled Keep Normal Disabled Disabled --- 1/0/8 Disabled Keep Normal Disabled Disabled --- 1/0/9 Disabled Keep Normal Disabled Disabled --- 1/0/10 Disabled Keep Normal Disabled Disabled --- Total: 28

Follow these steps to enable DHCP Relay and configure Option 82:

1) In the Global Config section, enable DHCP Relay globally and configure the relay hops and time threshold. Click Apply.

DHCP Relay Enable DHCP Relay globally.
DHCP Relay HopsSpecify the DHCP relay hops.DHCP Relay Hops defines the maximum number of hops (DHCP Relay agent) that the DHCP packets can be relayed. If a packet's hop count is more than the value you set here, the packet will be dropped.
DHCP Relay Time ThresholdSpecify the threshold of the DHCP relay time. The valid values are from 0 to 65535 seconds.DHCP relay time is the time elapsed since the client began address acquisition or renewal process. There is a field in DHCP packets which specially records this time, and the switch will drop the packets if the value of this field is greater than the threshold. Value 0 means the switch will not examine this field of the DHCP packets.

2) (Optional) In the Option 82 Config section, configure Option 82.

Option 82 SupportSelect whether to enable Option 82 or not. Enable it if you want to prevent DHCP client requests from untrusted sources, or assign different IP addresses to clients in different groups from the same DHCP server.
Option 82 PolicySelect the operation for the switch to take when receiving DHCP packets that include the Option 82 field. Keep: The switch keeps the Option 82 field of the packets. Replace: The switch replaces the Option 82 field of the packets with a new one. The switch presets a default circuit ID and remote ID in TLV (Type, Length, and Value) format. You can also configure the format to include Value only and customize the Value. Drop: The switch discards the packets that include the Option 82 field.
Format Specify the packet format for the sub-option fields of Option 82.
Normal: Indicates the fields consist of three parts: Type, Length, and Value (TLV).
Private: Indicates the fields consist of the value only.
Circuit ID CustomizationEnable or disable Circuit ID Customization. Enable it if you want to manually configure the circuit ID. Otherwise, the switch uses the default one when inserting Option 82 to DHCP packets.The default circuit ID is a 4-byte value which consists of 2-byte VLAN ID and 2-byte Port ID. The VLAN ID indicates which VLAN the DHCP client belongs to, and the Port ID indicates which port the DHCP client is connected to. For example, if the DHCP client is connected to port 1/0/1 in VLAN 2, this field is 00:02:00:01 in hexadecimal.
Circuit ID Enter the customized circuit ID with up to 64 characters. The circuit ID configurations of the switch and the DHCP server should be compatible with each other.
Remote ID CustomizationEnable or disable Remote ID Customization. Enable it if you want to manually configure the remote ID. Otherwise, the switch uses its own MAC address as the remote ID.
Remote ID Enter the customized remote ID with up to 64 characters. The remote ID configurations of the switch and the DHCP server should be compatible with each other.

3) Click Apply.

3.1.2 Configuring DHCP Interface Relay

DHCP Interface Relay allows clients to obtain IP addresses from a DHCP server in a different subnet.

Choose the menu L3 FEATURES > DHCP Service > DHCP Relay > DHCP Interface Relay and click to load the following page.

Figure 3-2 Configuring DHCP Interface Relay
TP-LINK Omada TL-SG2008P - Configuring DHCP Interface Relay - 1

text_image DHCP Interface Relay Interface ID: VLAN (1-4094) Server Address: (Format: 192.168.0.1) Cancel Create

Select the interface type and enter the interface ID, then enter the IP address of the DHCP server. Click Create.

Interface ID Specify the type and ID of the interface. It is the Layer 3 interface which is connecting to the DHCP clients.

The interface should be an existing Layer 3 interface.

Server Address Enter the IP address of the DHCP server.

3.1.3 Configuring DHCP VLAN Relay

DHCP VLAN Relay allows clients in different VLANs to obtain IP addresses from a DHCP server using the IP address of a single agent interface. It is often used when the relay switch does not support configuring multiple Layer 3 interfaces.

Choose the menu L3 FEATURES > DHCP Service > DHCP Relay > DHCP VLAN Relay to load the following page.

Figure 3-3 Configure DHCP VLAN Relay
TP-LINK Omada TL-SG2008P - Configuring DHCP VLAN Relay - 1

text_image Default Relay Agent Interface Interface ID: VLAN (1-4094) IP Address: Apply DHCP VLAN Relay Config Index VLAN ID Server Address No entries in this table. Total: 0

Follow these steps to specify DHCP Server for the specific VLAN:

1) In the Default Relay Agent Interface section, specify a Layer 3 interface as the default relay agent interface. Then click Apply.

Interface ID

Specify the type and ID of the interface that needs to be configured as the default relay agent interface.

You can configure any existing Layer 3 interface as the default relay-agent interface. The DHCP server will assign IP addresses in the same subnet with this relay agent interface to the clients who use this relay-agent interface to apply for IP addresses.

IP Address Displays the IP address of this interface.

TP-LINK Omada TL-SG2008P - Configuring DHCP VLAN Relay - 2

Note:

  • If the VLAN the clients belong to already has an IP address, the switch will use the client's own VLAN interface as the relay-agent interface. The manually specified default relay agent will not take effect.
  • DHCP VLAN Relay will not work on routed ports or port channel interfaces, because they are not associated with any particular VLAN.

2) In the DHCP VLAN Relay Config section, click + Add to load the configuration page.

Figure 3-4 Specify a DHCP server for the VLAN
TP-LINK Omada TL-SG2008P - Note: - 1

text_image DHCP VLAN Relay VLAN ID: (1-4094) Server Address: (Format: 192.168.0.1) Cancel Create

Specify the VLAN the clients belong to and the server address. Click Create.

VLAN ID Specify the VLAN in which the clients can get IP addresses from the DHCP server.

Server Address Enter the IP address of the DHCP server.

3.2 Using the CLI

3.2.1 Enabling DHCP Relay

Follow these steps to enable DHCP Relay and configure the corresponding parameters:

Step 1 configure

Enter Global Configuration Mode.

Step 2 service dhcp relay

Enable DHCP Relay.

Step 3 ip dhcp relay hops

hops

Specify the maximum hops (DHCP relay agent) that the DHCP packets can be relayed. If a packet's hop count is more than the value you set here, the packet will be dropped.

hops: Specify the maximum hops for DHCP packets. Valid values are from the 1 to 16, and the default value is 4.

Step 4 ip dhcp relay time

time

Specify the threshold for the DHCP relay time.

DHCP relay time is the time elapsed since the client began address acquisition or renewal process. There is a field in DHCP packets which specially records this time, and the switch will drop the packets if the value of this field is greater than the threshold. Value 0 means the switch will not examine this field of the DHCP packets.

time: Specify the threshold for the DHCP relay time. Valid values are from 1 to 65535. By default, the value is 0, which means the switch will not examine this field of the DHCP packets.

Step 5 show ip dhcp relay

Verify the configuration of DHCP Relay.

Step 6 end

Return to Privileged EXEC Mode.

Step 7 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable DHCP Relay, configure the relay hops as 5 and configure the relay time as 10 seconds :

Switch#configure

Switch(config)#service dhcp relay

Switch(config)#show ip dhcp relay

Switch(config)#ip dhcp relay hops 5

Switch(config)#ip dhcp relay time 10

DHCP relay state: enabled

DHCP relay hops: 5

DHCP relay Time Threshold: 10 seconds

...

Switch(config)#end

Switch#copy running-config startup-config

3.2.2 (Optional) Configuring Option 82

Follow these steps to configure Option 82:

Step 1 configure

Enter Global Configuration Mode.

Step 2 interface { fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list }

Enter Interface Configuration Mode.

Step 3 ip dhcp relay information option

Enable the Option 82 feature on the port.

Step 4 ip dhcp relay information strategy { keep | replace | drop }

Specify the operation for the switch to take when receiving DHCP packets that include the Option 82 field.

keep: The switch keeps the Option 82 field of the packets.

replace: The switch replaces the Option 82 field of the packets with a new one. The switch presets a default circuit ID and remote ID in TLV (Type, Length, and Value) format. You can also configure the format to include Value only and customize the Value.

drop: The switch discards the packets that include the Option 82 field.

Step 5 ip dhcp relay information format {normal | private}

Specify the packet format for the sub-option fields of Option 82.

normal: Indicates the fields consist of three parts: Type, Length, and Value (TLV).

private: Indicates the fields consist of the value only.

Step 6 ip dhcp relay information circuit-idstring
(Optional) A default circuit ID is preset on the switch, and you can also run this command to customize the circuit ID. The circuit ID configurations of the switch and the DHCP server should be compatible with each other.
The default circuit ID is a 4-byte value which consists of 2-byte VLAN ID and 2-byte Port ID. The VLAN ID indicates which VLAN the DHCP client belongs to, and the Port ID indicates which port the DHCP client is connected to. For example, if the DHCP client is connected to port 1/0/1 in VLAN 2, this field is 00:02:00:01 in hexadecimal.
string: Enter the customized circuit ID with up to 64 characters.
Step 7 ip dhcp relay information remote-idstring
(Optional) The switch uses its own MAC address as the default remote ID, and you can also run this command to customize the remote ID. The remote ID configurations of the switch and the DHCP server should be compatible with each other.
string: Enter the remote ID with up to 64 characters.
Step 8 show ip dhcp relay information interface { fastEthernet gigabitEthernet port | port-channel port-channel-id }port | gigabitEthernet port | ten-
Verify the Option 82 configurations of the port.
Step 9 end
Return to Privileged EXEC Mode.
Step 10 copy running-config startup-config
Save the settings in the configuration file.

The following example shows how to enable Option 82 on port 1/0/7 and configure the strategy as replace, the format as normal, the circuit-id as VLAN20 and the remote-id as Host1:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/7

Switch(config-if)#ip dhcp relay information option

Switch(config-if)#ip dhcp relay information strategy replace

Switch(config-if)#ip dhcp relay information format normal

Switch(config-if)#ip dhcp relay information circuit-id VLAN20

Switch(config-if)#ip dhcp relay information remote-id Host1

Switch(config-if)#show ip dhcp relay information interface gigabitEthernet 1/0/7

InterfaceOption 82 StatusOperation StrategyFormatCircuit IDRemote IDLAG
Gi1/0/7EnableReplaceNormalVLAN20Host1N/A

Switch(config-if)#end

Switch#copy running-config startup-config

3.2.3 Configuring DHCP Interface Relay

You can specify a DHCP server for a Layer 3 interface or for a VLAN. The following introduces how to configure DHCP Interface Relay and DHCP VLAN Relay, respectively.

Follow these steps to DHCP Interface Relay:

Step 1 configure

Enter Global Configuration Mode.

Step 2 Enter Layer 3 Interface Configuration Mode:

Enter VLAN Interface Configuration Mode:

interface vlan vlan-id

vlan-id: Specify an IEEE 802.1Q VLAN ID that already exists, ranging from 1 to 4094.

Enter Routed Port Configuration Mode:

interface { fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port }

Enter Interface Configuration Mode.

port: Specify the Ethernet port number, for example, 1/0/1.

no switchport

Switch the Layer 2 port into the Layer 3 routed port.

Enter Port-channel Interface Configuration Mode:

interface { port-cahnnel port-channel }

Enter Interface Configuration Mode.

port-channel: Specify the port channel. Valid values are from 1 to 14.

no switchport

Switch the port channel to a Layer 3 port channel interface.

Step 3 ip helper-address

ip-addr

Specify DHCP server for the Layer 3 interface.

ip-addr: Enter the IP address of the DHCP server.

Step 4 show ip dhcp relay

Verify the configuration of DHCP Relay.

Step 5 end

Return to Privileged EXEC Mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to configure the DHCP server address as 192.168.1.7 on VLAN interface 66:

Switch#configure

Switch(config)#interface vlan 66

Switch(config-if)#ip helper-address 192.168.1.7

Switch(config-if)#show ip dhcp relay

...

DHCP relay helper address is configured on the following interfaces:

Interface Helper address

VLAN 66 192.168.1.7

Switch(config-if)#end

Switch#copy running-config startup-config

3.2.4 Configuring DHCP VLAN Relay

Follow these steps to configure DHCP VLAN Relay:

Step 1 configure

Enter Global Configuration Mode.

Step 2 Enter Layer 3 Interface Configuration Mode:

Enter VLAN Interface Configuration Mode:

interface vlan vlan-id

vlan-id: Specify an IEEE 802.1Q VLAN ID that already exists, ranging from 1 to 4094.

Enter Routed Port Configuration Mode:

interface { fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port }

Enter Interface Configuration Mode.

port: Specify the Ethernet port number, for example, 1/0/1.

no switchport

Switch the Layer 2 port into the Layer 3 routed port.

Enter Port-channel Interface Configuration Mode:

interface { port-cahnnel port-channel }

Enter Interface Configuration Mode.

port-channel: Specify the port channel. Valid values are from 1 to 14.

no switchport

Switch the port channel to a Layer 3 port channel interface.

Step 3 ip dhcp relay default-interface

Set the interface as the default relay-agent interface. If the VLAN that the clients belong to does not have an IP address, the switch will use the IP address of this interface to fill in the Relay Agent IP Address field of DHCP packets from the DHCP clients.

Step 4 exit

Return to Global Configuration Mode.

Step 5 ip dhcp relay vlan

vid helper-address ip-address

Specify the VLAN ID and the DHCP server.

vid: Enter the ID of the VLAN, in which the hosts can dynamically get the IP addresses from the DHCP server.

ip-address: Enter the IP address of the DHCP server.

Step 6 show ip dhcp relay

Verify the configuration of DHCP Relay.

Step 7 end

Return to Privileged EXEC Mode.

Step 8 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to set the routed port 1/0/2 as the default relay agent interface and configure the DHCP server address as 192.168.1.8 on VLAN 10:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/2

Switch(config-if)#no switchport

Switch(config-if)# ip dhcp relay default-interface

Switch(config-if)#exit

Switch(config)#ip dhcp relay vlan 10 helper-address 192.168.1.8

Switch(config)#show ip dhcp relay

...

DHCP VLAN relay helper address is configured on the following vlan:

vlan Helper address

VLAN 10 192.168.1.8

Switch(config)#end

Switch#copy running-config startup-config

4 DHCP L2 Relay Configuration

To complete DHCP L2 Relay configuration, follow these steps:

1) Enable DHCP L2 Relay.
2) Configure Option 82 for ports.

4.1 Using the GUI

4.1.1 Enabling DHCP L2 Relay

Choose the menu L3 FEATURES > DHCP Service > DHCP L2 Relay > Global Config to load the following page.

Figure 4-1 Enable DHCP L2 Relay
TP-LINK Omada TL-SG2008P - Enabling DHCP L2 Relay - 1

text_image Global Config DHCP L2 Relay: Enable VLAN Config Filter by VLAN: From To Apply VLAN Status 1 Disabled 8 Disabled Total: 2 1 entry selected. Cancel Apply

Follow these steps to enable DHCP L2 Relay globally for the specified VLAN:

1) In the Global Config section, enable DHCP L2 Relay globally. Click Apply.

DHCP L2 Relay Enable DHCP Relay globally.

2) In the VLAN Config section, enable DHCP L2 Relay for the specified VLAN. Click Apply.

VLAN Displays the VLAN ID.

Status Enable DHCP L2 Relay for the specified VLAN.

4.1.2 Configuring Option 82 for Ports

Choose the menu L3 FEATURES > DHCP Service > DHCP L2 Relay > Port Config to load the following page.

Figure 4-2 Configure Option 82 for Ports
TP-LINK Omada TL-SG2008P - Configuring Option 82 for Ports - 1

text_image Port Config UNIT1 LAGS Port Option 82 Support Option 82 Policy Format Circuit ID Customizaton Circuit ID Remote ID Customizaton Remote ID LAG ✓ 1/0/1 Disabled Keep Normal Disabled Disabled --- □ 1/0/2 Disabled Keep Normal Disabled Disabled --- □ 1/0/3 Disabled Keep Normal Disabled Disabled --- □ 1/0/4 Disabled Keep Normal Disabled Disabled --- □ 1/0/5 Disabled Keep Normal Disabled Disabled --- □ 1/0/6 Disabled Keep Normal Disabled Disabled --- □ 1/0/7 Disabled Keep Normal Disabled Disabled --- □ 1/0/8 Disabled Keep Normal Disabled Disabled --- □ 1/0/9 Disabled Keep Normal Disabled Disabled --- □ 1/0/10 Disabled Keep Normal Disabled Disabled --- Total: 28 1 entry selected. Cancel Apply

Follow these steps to enable DHCP Relay and configure Option 82:

1) Select one or more ports to configure Option 82.

Option 82 SupportSelect whether to enable Option 82 or not. Enable it if you want to prevent DHCP client requests from untrusted sources, or assign different IP addresses to clients in different groups from the same DHCP server.
Option 82 PolicySelect the operation for the switch to take when receiving DHCP packets that include the Option 82 field. Keep: The switch keeps the Option 82 field of the packets. Replace: The switch replaces the Option 82 field of the packets with a new one. The switch presets a default circuit ID and remote ID in TLV (Type, Length, and Value) format. You can also configure the format to include Value only and customize the Value. Drop: The switch discards the packets that include the Option 82 field.
Format Specify the packet format for the sub-option fields of Option 82.
Normal: Indicates the fields consist of three parts: Type, Length, and Value (TLV).
Private: Indicates the fields consist of the value only.
Circuit ID CustomizationEnable or disable Circuit ID Customization. Enable it if you want to manually configure the circuit ID. Otherwise, the switch uses the default one when inserting Option 82 to DHCP packets.The default circuit ID is a 4-byte value which consists of 2-byte VLAN ID and 2-byte Port ID. The VLAN ID indicates which VLAN the DHCP client belongs to, and the Port ID indicates which port the DHCP client is connected to. For example, if the DHCP client is connected to port 1/0/1 in VLAN 2, this field is 00:02:00:01 in hexadecimal.
Circuit ID Enter the customized circuit ID with up to 64 characters. The circuit ID configurations of the switch and the DHCP server should be compatible with each other.
Remote ID CustomizationEnable or disable Remote ID Customization. Enable it if you want to manually configure the remote ID. Otherwise, the switch uses its own MAC address as the remote ID.
Remote ID Enter the customized remote ID with up to 64 characters. The remote ID configurations of the switch and the DHCP server should be compatible with each other.

2) Click Apply.

4.2 Using the CLI

4.2.1 Enabling DHCP L2 Relay

Follow these steps to enable DHCP L2 Relay:

Step 1 configureEnter Global Configuration Mode.
Step 2 ip dhcp l2relayEnable DHCP L2 Relay.
Step 3 ip dhcp l2relay vlan vlan-listEnable DHCP L2 Relay for specified VLANs.vlan-list: Specify the vlan to be enabled with DHCP L2 relay.
Step 5 show ip dhcp l2relayVerify the configuration of DHCP Relay.

Step 6 end

Return to Privileged EXEC Mode.

Step 7 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable DHCP L2 Relay globally and for VLAN 2:

Switch#configure

Switch(config)#ip dhcp l2relay

Switch(config)#ip dhcp l2relay vlan 2

Switch(config)#show ip dhcp l2relay

Global Status: Enable

VLAN ID: 2

Switch(config)#end

Switch#copy running-config startup-config

4.2.2 Configuring Option 82 for Ports

Follow these steps to configure Option 82:

Step 1 configure

Enter Global Configuration Mode.

Step 2 interface { fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list } Enter Interface Configuration Mode.

Step 3 ip dhcp I2relay information option

Enable the Option 82 feature on the port.

Step 4 ip dhcp I2relay information strategy { keep | replace | drop }

Specify the operation for the switch to take when receiving DHCP packets that include the Option 82 field.

keep: The switch keeps the Option 82 field of the packets.

replace: The switch replaces the Option 82 field of the packets with a new one. The switch presets a default circuit ID and remote ID in TLV (Type, Length, and Value) format. You can also configure the format to include Value only and customize the Value.

drop: The switch discards the packets that include the Option 82 field.

Step 5ip dhcp l2relay information format {normal | private}Specify the packet format for the sub-option fields of Option 82.
normal: Indicates the fields consist of three parts: Type, Length, and Value (TLV).
private: Indicates the fields consist of the value only.
Step 6 ip dhcp l2relay information circuit-id string(Optional) A default circuit ID is preset on the switch, and you can also run this command to customize the circuit ID. The circuit ID configurations of the switch and the DHCP server should be compatible with each other.The default circuit ID is a 4-byte value which consists of 2-byte VLAN ID and 2-byte Port ID. The VLAN ID indicates which VLAN the DHCP client belongs to, and the Port ID indicates which port the DHCP client is connected to. For example, if the DHCP client is connected to port 1/0/1 in VLAN 2, this field is 00:02:00:01 in hexadecimal.
string: Enter the customized circuit ID with up to 64 characters.
Step 7 ip dhcp l2relay information remote-id string(Optional) The switch uses its own MAC address as the default remote ID, and you can also run this command to customize the remote ID. The remote ID configurations of the switch and the DHCP server should be compatible with each other.
string: Enter the remote ID with up to 64 characters.
Step 8 show ip dhcp l2relay information interface {fastEthernet port-channel port-channel-id}Verify the Option 82 configuration of the port.port | gigabitEthernet port |
Step 9 endReturn to Privileged EXEC Mode.
Step 10 copy running-config startup-configSave the settings in the configuration file.

The following example shows how to enable Option 82 on port 1/0/7 and configure the strategy as replace, the format as normal, the circuit-id as VLAN20 and the remote-id as Host1:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/7

Switch(config-if)#ip dhcp I2relay information option

Switch(config-if)#ip dhcp l2relay information strategy replace

Switch(config-if)#ip dhcp l2relay information format normal

Switch(config-if)#ip dhcp I2relay information circuit-id VLAN20

Switch(config-if)#ip dhcp I2relay information remote-id Host1

Switch(config-if)#show ip dhcp l2relay information interface gigabitEthernet 1/0/7

InterfaceOption 82 StatusOperation StrategyFormatCircuit IDRemote IDLAG
Gi1/0/7EnableReplaceNormalVLAN20Host1N/A

Switch(config-if)#end

Switch#copy running-config startup-config

5 Configuration Examples

5.1 Example for DHCP Server

5.1.1 Network Requirements

As the network topology shows, the administrator uses the switch as the DHCP server to assign IP addresses to all the connected devices. The office computers need to obtain IP addresses dynamically, while the FTP server needs a fixed IP address.

Figure 5-1 Network Topology for DHCP Server
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph LR
    A["FTP Server"] -->|Gi1/0/2| B["Switch DHCP Server 192.168.0.28/24"]
    B -->|Gi1/0/6| C["Office Computer"]

5.1.2 Configuration Scheme

You can enable the DHCP Server service on the switch and create a DHCP IP pool for all the connected devices. Then manually bind the MAC address of the FTP server to an IP address specified for the FTP server.

Demonstrated with T1600G-28TS, the following sections provide configuration procedures in two ways: using the GUI and using the CLI.

5.1.3 Using the GUI

1) Choose the menu L3 FEATURES > DHCP Service > DHCP Server > DHCP Server to load the following page. In the Global Config section, enable DHCP Server and click Apply.

Figure 5-2 Configuring DHCP Server
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Global Config DHCP Server: ✓ Enable Option 60: (Optional. 1-64 characters) Option 138: (Optional. Format 192.168.0.1) Apply

2) Choose the menu L3 FEATURES > DHCP Service > DHCP Server > Pool Setting and click to load the following page. Specify the Pool Name, Network Address,

Subnet Mask, Lease Time, Default Gateway and DNS Server as shown below. Click Create.

Figure 5-3 Configuring DHCP Server Pool
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image DHCP Server Pool Pool Name: pool (8 characters maximum) Network Address: 192.168.0.0 (Format: 192.168.0.0) Subnet Mask: 255.255.255.0 (Format: 255.255.255.0) Lease Time: 120 (Optional: 1-2880 min, Default: 120) ► Default Gateway: (Optional: Format: 192.168.0.1) ► DNS Server: (Optional: Format: 192.168.0.1) ► NetBIOS Server: (Optional: Format: 192.168.0.1) NetBIOS Node Type: ▼ (Optional, b/p/m/h/none) Next Server Address: (Optional: Format: 192.168.0.1) Domain Name: (0 to 200 characters) Bootfile: (0 to 128 characters) Cancel Create

3) Choose the menu L3 FEATURES > DHCP Service > DHCP Server > Manual Binding and click to load the following page. Select the DHCP server pool you just created, and enter the IP address of the FTP server in the IP Address field. Select Hardware Address as the binding mode, and enter the MAC address of the FTP server in the Hardware Address field. Select Ethernet as the Hardware Type. Click Create.

Figure 5-4 Configuring Manual Binding
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image Manual Binding Pool Name: pool IP Address: 192.168.0.8 (Format: 192.168.0.1) Binding Mode: Hardware Address Hardware Address: FC-AA-14-59-E9-4A (Format: 00-11-22-33-44-55) Hardware Type: Ethernet Cancel Create

4) Click Save the settings.

5.1.4 Using the CLI

1) Enable DHCP Server.

Switch#configure

Switch(config)#service dhcp server

2) Specify the Pool Name, Network Address, Subnet Mask and Lease Time.

Switch(config)#ip dhcp server pool pool

Switch(dhcp-config)#network 192.168.0.0 255.255.255.0

Switch(dhcp-config)#lease 120

Switch(dhcp-config)#exit

3) Bind the specified IP address to the MAC address of the FTP server.

Switch(config)# ip dhcp server pool pool

Switch(dhcp-config)# address 192.168.0.8 hardware-address FC-AA-14-59-E9-4A hardware-type ethernet

Switch(dhcp-config)#end

Switch#copy running-config startup-config

Verify the Configuration

Switch#show ip dhcp server binding

IP Address Client id/Hardware Address Type Lease Time Left

[EMPTY]

192.168.0.2 01-d43d-7ebf-615f Automatic 01:57:27

192.168.0.8 01-fcaa-1459-e94a Manual Infinite

5.2 Example for DHCP Interface Relay

5.2.1 Network Requirements

The administrator deploys one DHCP server on the network, and wants the server to assign IP addresses to the computers in the Marketing department and the R&D department. It is required that computers in the same department should be on the same subnet, while computers in different departments should be on different subnets.

After adding the DHCP server, the network topology will be as shown in Figure 5-5. The Marketing department and the R&D department belong to VLAN 10 and VLAN 20, respectively. The IP address of VLAN interface 10 is 192.168.2.1/24, and the IP address of VLAN interface 20 is 192.168.3.1/24. The DHCP server is connected to the routed port of

the switch. The Marketing department is connected to port 1/0/1 of the relay agent, and the R&D department is connected to port 1/0/2 of the relay agent.

Figure 5-5 Network Topology for DHCP Interface Relay
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["DHCP Server 192.168.0.59/24"] --> B["Switch DHCP Relay Agent"]
    C["VLAN 10 192.168.2.1/24"] --> B
    D["Marketing Dept. 192.168.2.0/24"] --> B
    E["Routed Port (Gi1/0/5) 192.168.0.1"] --> B
    F["Gi1/0/1"] --> B
    G["Gi1/0/2"] --> B
    H["VLAN 20 192.168.3.1/24"] --> B
    I["R&D Dept. 192.168.3.0/24"] --> B

5.2.2 Configuration Scheme

In the given situation, the DHCP server and the computers are isolated in different network segments, so the DHCP requests from the clients cannot be directly forwarded to the DHCP server. To assign IP addresses in two different subnets to two departments respectively, we recommend you to configure DHCP Interface Relay to satisfy the requirement.

The overview of the configurations are as follows:

1) Before configuring DHCP Interface Relay, create two DHCP IP pools on the DHCP server for the two departments, respectively. Then create static routes or enable dynamic routing protocol like RIP on the DHCP server to make sure the DHCP server can reach the clients in the two VLANs.
2) Configure 802.1Q VLAN on the DHCP relay agent. Add all computers in the marketing department to VLAN 10, and add all computers in the R&D department to VLAN 20.
3) Create VLAN interfaces for VLAN 10 and VLAN 20 on the DHCP relay agent.
4) Configure DHCP Interface Relay on the DHCP relay agent. Enable DHCP Relay globally, and specify the DHCP server address for each VLAN.

In this example, the DHCP server is demonstrated with T1600G-52TS and the DHCP relay agent is demonstrated with T1600G-28TS. This section provides configuration procedures in two ways: using the GUI and using the CLI.

5.2.3 Using the GUI

■ Configuring the DHCP Server

1) Choose the menu L3 FEATURES > DHCP Service > DHCP Server > DHCP Server to load the following page. In the Global Config section, enable DHCP Server globally.

Figure 5-6 Configuring DHCP Server
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Global Config DHCP Server: ✓ Enable Option 60: (Optional. 1-64 characters) Option 138: (Optional. Format 192.168.0.1) Apply

2) Choose the menu L3 FEATURES > DHCP Service > DHCP Server > Pool Setting and click to load the following page. Create pool 1 for VLAN 10 and pool 2 for VLAN 20. Configure the corresponding parameters as the following pictures show.

Figure 5-7 Configuring DHCP Pool 1 for VLAN 10
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image DHCP Server Pool Pool Name: pool1 (8 characters maximum) Network Address: 192.168.2.0 (Format: 192.168.0.0) Subnet Mask: 255.255.255.0 (Format: 255.255.255.0) Lease Time: 120 (Optional: 1-2880 min, Default: 120) ► Default Gateway: 192.168.2.1 (Optional: Format: 192.168.0.1) ► DNS Server: (Optional: Format: 192.168.0.1) ► NetBIOS Server: (Optional: Format: 192.168.0.1) NetBIOS Node Type: ▼ (Optional, b/p/m/h/none) Next Server Address: (Optional: Format: 192.168.0.1) Domain Name: (0 to 200 characters) Bootfile: (0 to 128 characters) Cancel Create

Figure 5-8 Configuring DHCP Pool 2 for VLAN 20
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image DHCP Server Pool Pool Name: pool2 (8 characters maximum) Network Address: 192.168.3.0 (Format: 192.168.0.0) Subnet Mask: 255.255.255.0 (Format: 255.255.255.0) Lease Time: 120 (Optional: 1-2880 min, Default: 120) ► Default Gateway: 192.168.3.1 (Optional. Format: 192.168.0.1) ► DNS Server: ► NetBIOS Server: NetBIOS Node Type: ▼ (Optional, b/p/m/h/none) Next Server Address: Domain Name: Bootfile: (0 to 200 characters) (0 to 128 characters) Cancel Create

3) Choose the menu L3 FEATURES > Static Routing > IPv4 Static Routing and click Add to load the following page. Create two static routing entries for the DHCP server to make sure that the DHCP server can reach the clients in the two VLANs.

Figure 5-9 Creating the Static Routing Entry for VLAN 10
TP-LINK Omada TL-SG2008P - Using the GUI - 4

text_image IPv4 Static Routing Destination: 192.168.2.0 (Format: 10.10.10.0) Subnet Mask: 255.255.255.0 (Format: 255.255.255.0) Next Hop: 192.168.0.1 (Format: 192.168.0.2) Distance: (Optional range: 1-255) Cancel Create

Figure 5-10 Creating the Static Routing Entry for VLAN 20
TP-LINK Omada TL-SG2008P - Using the GUI - 5

text_image IPv4 Static Routing Destination: 192.168.3.0 (Format: 10.10.10.0) Subnet Mask: 255.255.255.0 (Format: 255.255.255.0) Next Hop: 192.168.0.1 (Format: 192.168.0.2) Distance: (Optional. range: 1-255) Cancel Create

■ Configuring the VLANs on the Relay Agent

1) Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > VLAN Config and click

TP-LINK Omada TL-SG2008P - ■ Configuring the VLANs on the Relay Agent - 1

Add to load the following page. Create VLAN 10 for the Marketing department and port 1/0/1 as an untagged port to the VLAN.

Figure 5-11 Creating VLAN 10
TP-LINK Omada TL-SG2008P - ■ Configuring the VLANs on the Relay Agent - 2

text_image VLAN Config VLAN ID: 10 (2-4094, format: 2,4-5,8) VLAN Name: Marketing (1-16 characters) Untagged Ports Port: 1/0/1 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available Tagged Ports Port: (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Cancel Create

2) On the same page, click again to create VLAN 20 for the R&D department and add port 1/0/2 as an untagged port to the VLAN.

Figure 5-12 Creating VLAN 20
TP-LINK Omada TL-SG2008P - ■ Configuring the VLANs on the Relay Agent - 3

text_image VLAN Config VLAN ID: 20 (2-4094, format: 2,4-5,8) VLAN Name: RD (1-16 characters) Untagged Ports Port: 1/0/2 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available Tagged Ports Port: (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Cancel Create

■ Configuring the VLAN Interface and Routed Port on the Relay Agent

1) Choose the menu L3 FEATURES > Interface and click + Add to load the following page. Create VLAN interface 10 and VLAN interface 20. Configure port 1/0/5 as the routed port.

Figure 5-13 Creating VLAN Interface 10
TP-LINK Omada TL-SG2008P - ■ Configuring the VLANs on the Relay Agent - 4

text_image Interface Interface ID: VLAN 10 (1-4094) IP Address Mode: None Static DHCP BOOTP IP Address: 192.168.2.1 (Format: 192.168.0.1) Subnet Mask: 255.255.255.0 (Format: 255.255.255.0) Admin Status: Enable Interface Name: (Optional. 1-16 characters) Cancel Create

Figure 5-14 Creating VLAN Interface 20

TP-LINK Omada TL-SG2008P - ■ Configuring the VLANs on the Relay Agent - 5

text_image Interface Interface ID: VLAN 20 (1-4094) IP Address Mode: None Static DHCP BOOTP IP Address: 192.168.3.1 (Format: 192.168.0.1) Subnet Mask: 255.255.255.0 (Format: 255.255.255.0) Admin Status: Enable Interface Name: (Optional. 1-16 characters) Cancel Create

2) On the same page, click again to configure port 1/0/5 as the routed port.

Figure 5-15 Configuring the Routed Port
TP-LINK Omada TL-SG2008P - ■ Configuring the VLANs on the Relay Agent - 6

text_image Interface Interface ID: Routed Port 1/0/5 (Format: 1/0/1) UNIT1 IP Address Mode: None Static DHCP BOOTP IP Address: 192.168.0.1 (Format: 192.168.0.1) Subnet Mask: 255.255.255.0 (Format: 255.255.255.0) Admin Status: Enable Interface Name: (Optional: 1-16 characters) Cancel Create

■ Configuring DHCP Interface Relay on the Relay Agent

1) Choose the menu L3 FEATURES > DHCP Service > DHCP Relay > DHCP Relay Config to load the following page. In the Global Config section, enable DHCP Relay, and click Apply.

Figure 5-16 Enable DHCP Relay
TP-LINK Omada TL-SG2008P - ■ Configuring the VLANs on the Relay Agent - 7

text_image Global Config DHCP Relay: ✓ Enable DHCP Relay Hops: 4 (1-16) DHCP Relay Time Threshold: 0 seconds (0-65535) Apply

2) Choose the menu L3 FEATURES > DHCP Service > DHCP Relay > DHCP Interface Relay and click to load the following page. Specify the DHCP server for the clients in VLAN 10 and VLAN 20.

Figure 5-17 Specify DHCP Server for Interface VLAN 10
TP-LINK Omada TL-SG2008P - ■ Configuring the VLANs on the Relay Agent - 8

text_image DHCP Interface Relay Interface ID: VLAN 10 (1-4094) Server Address: 192.168.0.59 (Format: 192.168.0.1) Cancel Create

Figure 5-18 Specify DHCP Server for Interface VLAN 20
TP-LINK Omada TL-SG2008P - ■ Configuring the VLANs on the Relay Agent - 9

text_image DHCP Interface Relay Interface ID: VLAN 20 (1-4094) Server Address: 192.168.0.59 (Format: 192.168.0.1) Cancel Create

3) Click Save the settings.

5.2.4 Using the CLI

■ Configurting the DHCP Server

1) Enable DHCP service globally.

Switch#configure

Switch(config)#service dhcp server

2) Create DHCP pool 1 and configure its network address as 192.168.2.0, subnet mask as 255.255.255.0, lease time as 120 minutes, default gateway as 192.168.2.1; Create DHCP pool 2 and configure its network address as 192.168.3.0, subnet mask as 255.255.255.0, lease time as 120 minutes, default gateway as 192.168.3.1.

Switch(config)#ip dhcp server pool pool1

Switch(dhcp-config)#network 192.168.2.0 255.255.255.0

Switch(dhcp-config)#lease 120

Switch(dhcp-config)#default-gateway 192.168.2.1

Switch(dhcp-config)#exit

Switch(config)#ip dhcp server pool pool2

Switch(dhcp-config)#network 192.168.2.0 255.255.255.0

Switch(dhcp-config)#lease 120

Switch(dhcp-config)#default-gateway 192.168.3.1

Switch(dhcp-config)#exit

3) Create two static routing entries to make sure that the DHCP server can reach the clients in the two VLANs.

Switch(config)# ip route 192.168.2.0 255.255.255.0 192.168.0.1

Switch(config)# ip route 192.168.3.0 255.255.255.0 192.168.0.1

Switch(config)#end

Switch#copy running-config startup-config

■ Configuring the VLAN on the Relay Agent

Switch(config)# vlan 10

Switch(config-vlan)#name Marketing

Switch(config-vlan)#exit

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#switchport general allowed vlan 10 untagged

Switch(config-if)#exit

Switch(config)# vlan 20

Switch(config-vlan)#name RD

Switch(config-vlan)#exit

Switch(config)#interface gigabitEthernet 1/0/2

Switch(config-if)#switchport general allowed vlan 20 untagged

Switch(config-if)#exit

■ Configuring the VLAN Interfaces Routed Port on the Relay Agent

Switch(config)#interface vlan 10

Switch(config-if)#ip address 192.168.2.1 255.255.255.0

Switch(config-if)#exit

Switch(config)#interface vlan 20

Switch(config-if)#ip address 192.168.3.1 255.255.255.0

Switch(config-if)#exit

Switch(config)#interface gigabitEthernet 1/0/5

Switch(config-if)#ip address 192.168.0.1 255.255.255.0

Switch(config-if)#exit

■ Configuring DHCP Interface Relay on the Relay Agent

1) Enable DHCP Relay.

Switch#configure

Switch(config)#service dhcp relay

2) Specify the DHCP server for the interface VLAN 10.

Switch(config)#interface vlan 10

Switch(config-if)#ip helper-address 192.168.0.59

Switch(config-if)#exit

3) Specify the DHCP server for interface VLAN 20

Switch(config)#interface vlan 20

Switch(config-if)#ip helper-address 192.168.0.59

Switch(config-if)#end

Switch#copy running-config startup-config

Verify the Configurations of the DHCP Relay Agent

Switch#show ip dhcp relay

DHCP relay is enabled

...

DHCP relay helper address is configured on the following interfaces:

Interface Helper address

VLAN10 192.168.0.59

VLAN20 192.168.0.59

...

5.3 Example for DHCP VLAN Relay

5.3.1 Network Requirements

The administrator needs to deploy the office network for the Marketing department and the R&D department. The detailed requirements are listed below:

■ The Marketing department and the R&D department belong to VLAN 10 and VLAN 20, respectively. Both of the VLANs have no Layer 3 gateways.
■ Computers in the two departments need to obtain IP addresses from the same DHCP server.

The network topology designed by the administrator is shown below.

Figure 5-19 Network Topology for DHCP VLAN Relay
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["DHCP Server 192.168.0.59/24"] --> B["DHCP Relay Agent 192.168.0.1"]
    C["Marketing Dept. R&D Dept."] -->|Gi1/0/1| B
    D["VLAN 20VLAN 10"] -->|Gi1/0/2| B

5.3.2 Configuration Scheme

In the given situation, the DHCP server and the computers are isolated by VLANs, so the DHCP request from the clients cannot be directly forwarded to the DHCP server. Considering that the two VLANs have no Layer 3 gateways, we recommend you to configure DHCP VLAN Relay to satisfy the requirement.

The overview of the configurations are as follows:

1) Create one DHCP IP pool on the DHCP server, which is on 192.168.0.0/24 network segment.
2) Configure 802.1Q VLAN on the DHCP relay agent. Add all computers in the marketing department to VLAN 10, and add all computers in the R&D department to VLAN 20.
3) Configure DHCP VLAN Relay on the DHCP relay agent. Enable DHCP Relay globally, choose the VLAN interface 1 (the default management VLAN interface) as the default relay agent interface, and specify the DHCP server address for VLAN 10 and VLAN 20.

In this example, the DHCP server is demonstrated with T1600G-52TS and the DHCP relay agent is demonstrated with T1600G-28TS. The following sections provide configuration procedures in two ways: using the GUI and using the CLI.

5.3.3 Using the GUI

■ Configuring the DHCP Server

1) Choose the menu L3 FEATURES > DHCP Service > DHCP Server > DHCP Server to load the following page. In the Global Config section, enable DHCP Server globally.

Figure 5-20 Configuring DHCP Server
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Global Config DHCP Server: ✓ Enable Option 60: (Optional. 1-64 characters) Option 138: (Optional. Format 192.168.0.1) Apply

2) Choose the menu L3 FEATURES > DHCP Service > DHCP Server > Pool Setting and click to load the following page. Create a DHCP pool for the clients. Configure the corresponding parameters as the following picture shows.

Figure 5-21 Configuring DHCP Pool 1 for VLAN 10
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image DHCP Server Pool Pool Name: pool (8 characters maximum) Network Address: 192.168.0.0 (Format: 192.168.0.0) Subnet Mask: 255.255.255.0 (Format: 255.255.255.0) Lease Time: 120 (Optional: 1-2880 min, Default: 120) ► Default Gateway: (Optional. Format: 192.168.0.1) ► DNS Server: (Optional. Format: 192.168.0.1) ► NetBIOS Server: (Optional. Format: 192.168.0.1) NetBIOS Node Type: ▼ (Optional, b/p/m/h/none) Next Server Address: (Optional. Format: 192.168.0.1) Domain Name: (0 to 200 characters) Bootfile: (0 to 128 characters) Cancel Create

■ Configuring the VLANs on the Relay Agent

1) Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > VLAN Config and click Add to load the following page. Create VLAN 10 for the Marketing department and add port 1/0/1 as untagged port to the VLAN.

Figure 5-22 Creating VLAN 10
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image VLAN Config VLAN ID: 10 (2-4094, format: 2,4-5,8) VLAN Name: Marketing (1-16 characters) Untagged Ports Port: 1/0/1 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available Tagged Ports Port: (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Cancel Create

2) On the same page, click again to create VLAN 20 for the R&D department and add port 1/0/2 as untagged port to the VLAN.

Figure 5-23 Creating VLAN 20
TP-LINK Omada TL-SG2008P - Using the GUI - 4

text_image VLAN Config VLAN ID: 20 (2-4094, format: 2,4-5,8) VLAN Name: RD (1-16 characters) Untagged Ports Port: 1/0/2 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available Tagged Ports Port: (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Cancel Create

■ Configuring DHCP VLAN Relay on the Relay Agent

1) Choose the menu L3 FEATURES > DHCP Service > DHCP Relay > DHCP Relay Config to load the following page. In the Global Config section, enable DHCP Relay, and click Apply.

Figure 5-24 Enable DHCP Relay
TP-LINK Omada TL-SG2008P - Using the GUI - 5

text_image Global Config DHCP Relay: ✓ Enable DHCP Relay Hops: 4 (1-16) DHCP Relay Time Threshold: 0 seconds (0-65535) Apply

2) Choose the menu L3 FEATURES > DHCP Service > DHCP Relay > DHCP VLAN Relay to load the following page. In the Default Relay Agent Interface section, specify

VLAN interface 1 (the default management VLAN interface) as the default relay-agent interface. Click Apply.

Figure 5-25 Specify the Default Relay Agent Interface
TP-LINK Omada TL-SG2008P - Using the GUI - 6

text_image Default Relay Agent Interface Interface ID: VLAN 1 (1-4094) IP Address: 192.168.0.1 Apply

3) Choose the menu L3 FEATURES > DHCP Service > DHCP Relay > DHCP VLAN Relay and click to load the following page. Specify the DHCP server address for the clients in VLAN 10 and VLAN 20.

Figure 5-26 Specify DHCP Server for Interface VLAN 10
TP-LINK Omada TL-SG2008P - Using the GUI - 7

text_image DHCP VLAN Relay VLAN ID: 10 (1-4094) Server Address: 192.168.0.59 (Format: 192.168.0.1) Cancel Create

Figure 5-27 Specify DHCP Server for Interface VLAN 20
TP-LINK Omada TL-SG2008P - Using the GUI - 8

text_image DHCP VLAN Relay VLAN ID: 20 (1-4094) Server Address: 192.168.0.59 (Format: 192.168.0.1) Cancel Create

4) Click Save the settings.

5.3.4 Using the CLI

■ Configurting the DHCP Server

1) Enable DHCP service globally.

Switch#configure

Switch(config)#service dhcp server

2) Create a DHCP pool and name it as "pool" and configure its network address as 192.168.0.0, subnet mask as 255.255.255.0, lease time as 120 minutes, default gateway as 192.168.0.1.

Switch(config)#ip dhcp server pool pool

Switch(dhcp-config)#network 192.168.0.0 255.255.255.0

Switch(dhcp-config)#lease 120

Switch(dhcp-config)#default-gateway 192.168.0.1

Switch(dhcp-config)#dns-server 192.168.0.2

Switch(dhcp-config)#end

Switch#copy running-config startup-config

■ Configuring the VLAN on the Relay Agent

Switch#configure

Switch(config)# vlan 10

Switch(config-vlan)#name Marketing

Switch(config-vlan)#exit

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#switchport general allowed vlan 10 untagged

Switch(config-if)#exit

Switch(config)# vlan 20

Switch(config-vlan)#name RD

Switch(config-vlan)#exit

Switch(config)#interface gigabitEthernet 1/0/2

Switch(config-if)#switchport general allowed vlan 20 untagged

Switch(config-if)#exit

■ Configuring DHCP VLAN Relay on the Relay Agent

1) Enable DHCP Relay.

Switch(config)#service dhcp relay

2) Specify the routed port 1/0/5 as the default relay agent interface.

Switch(config)#interface vlan 1

Switch(config-if)#ip dhcp relay default-interface

Switch(config-if)#exit

3) Specify the DHCP server for VLAN 10 and VLAN 20

Switch(config)#ip dhcp relay vlan 10 helper-address 192.168.0.59

Switch(config)#ip dhcp relay vlan 20 helper-address 192.168.0.59

Switch(config)#exit

Verify the Configurations of the DHCP Relay Agent

Switch#show ip dhcp relay

Switch#show ip dhcp relay

DHCP relay state: enabled

...

DHCP relay default relay agent interface:

Interface: VLAN 1

IP address: 192.168.0.1

DHCP vlan relay helper address is configured on the following vlan:

vlan Helper address

VLAN 10 192.168.0.59

VLAN 20 192.168.0.59

5.4 Example for Option 82 in DHCP Relay

5.4.1 Network Requirements

As the following figure shows, there are two groups of computers. Group 1 is connected to Switch A via port 1/0/1, and Group 2 is connected via port 1/0/2. All computers are in the same VLAN, but the computers and the DHCP server are in different subnets. For management convenience, the administrator wants to allocate separate address spaces for the two groups of computers.

Figure 5-28 Network Topology for Option 82 in DHCP Relay
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["DHCP Server\n192.168.0.59/24"] --> B["Switch A\nGi1/0/2Gi1/0/1"]
    B --> C["VLAN 2\n192.168.2.1/24"]
    B --> D["VLAN 2\n192.168.2.1/24"]
    B --> E["Group 1\nPC\nGroup 1\n192.168.2.50-192.168.2.100"]
    B --> F["Group 2\nPC\nGroup 2\nPC\nGroup 2\n192.168.2.150-192.168.2.200"]

5.4.2 Configuration Scheme

To meet the requirements, you can configure Option 82 in DHCP Relay on Switch A. With DHCP Relay enabled, the switch can forward DHCP requests and replies between clients and the server. With Option 82 enabled, Switch A informs the DHCP server of the group information of each computer, so that the DHCP server can assign IP addresses of different address pools to the computers in different groups.

The overview of the configurations are as follows:

1) Configuring Switch A

a. Configure 802.1Q VLAN. Add all computers to VLAN 2. For details, refer to Configuring 802.1Q VLAN.

b. Configure the interface address of VLAN 2. For details, refer to Configuring Layer 3 Interfaces.

c. Configure DHCP relay and enable Option 82 in DHCP Relay. In this example, both DHCP Interface Relay and DHCP VLAN Relay can implement the requirements. Demonstrated with T1600G-28TS, 5.4.3 Configuring the DHCP Relay Switch provides configuration procedures to configure DHCP Interface Relay in two ways: using the GUI and using the CLI.

2) Configuring the DHCP Server

The detailed configurations on the DHCP server may be different among different devices. You can refer to the related document that is for the DHCP server you use. Demonstrated with a Linux ISC DHCP Server, 5.4.4 Configuring the DHCP Server provides information about how to set its DHCP configuration file.

5.4.3 Configuring the DHCP Relay Switch

Using the GUI

Follow these steps to configure DHCP relay and enable Option 82 in DHCP Relay on Switch A:

1) Choose the menu L3 FEATURES > DHCP Service > DHCP Relay > DHCP Relay Config to load the following page. In the Global Config section, enable DHCP Relay, and click Apply.

Figure 5-29 Enable DHCP Relay
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Global Config DHCP Relay: ✓ Enable DHCP Relay Hops: 4 (1-16) DHCP Relay Time Threshold: 0 seconds (0-65535) Apply

2) In the Option 82 Config section, select port 1/0/1 and port 1/0/2, enable Option 82 Support and set Option 82 Policy as Replace. You can configure other parameters according to your needs. In this example, the Format is set as Normal, and Circuit ID Customization and Remote ID Customization as Disabled. Click Apply.

Figure 5-30 Configure Option 82
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image Option 82 Config UNIT1 LAGS Port Option 82 Option 82 Support Policy Format Circuit ID Circuit ID Remote ID Remote ID LAG Enable Replace ▼ ▼ ▼ ▼ ✓ 1/0/1 Enabled Replace Normal Disabled Disabled -- ✓ 1/0/2 Enabled Replace Normal Disabled Disabled -- □ 1/0/3 Disabled Keep Normal Disabled Disabled -- □ 1/0/4 Disabled Keep Normal Disabled Disabled -- □ 1/0/5 Disabled Keep Normal Disabled Disabled -- □ 1/0/6 Disabled Keep Normal Disabled Disabled -- □ 1/0/7 Disabled Keep Normal Disabled Disabled -- □ 1/0/8 Disabled Keep Normal Disabled Disabled -- □ 1/0/9 Disabled Keep Normal Disabled Disabled -- □ 1/0/10 Disabled Keep Normal Disabled Disabled -- Total: 28 2 entries selected. Cancel Apply

3) Choose the menu L3 FEATURES > DHCP Service > DHCP Relay > DHCP Interface

Relay and click to load the following page. Specify the DHCP server address to assign IP addresses for clients in VLAN 2. Click Create.

Figure 5-31 Specify DHCP Server for Interface VLAN 2
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image DHCP Interface Relay Interface ID: VLAN 2 (1-4094) Server Address: 192.168.0.59 (Format: 192.168.0.1) Cancel Create

4) Click Save the settings.

Using the CLI

Follow these steps to configure DHCP relay and enable Option 82 in DHCP Relay on Switch A:

1) Enable DHCP Relay.

Switch#configure

Switch(config)#service dhcp relay

2) Enable Option 82 for port 1/0/1 and port 1/0/2. Set Option 82 policy as Replace. You can configure other parameters according to your needs. In this example, the Format is set as Normal, and Circuit ID Customization and Remote ID Customization as Disabled.

Switch#(config)#interface range gigabitEthernet 1/0/1-2

Switch(config-if)#ip dhcp relay information option

Switch(config-if)#ip dhcp relay information strategy replace

Switch(config-if)#ip dhcp relay information format normal

Switch(config-if)#exit

3) Specify the DHCP server for the interface VLAN 2.

Switch(config)#interface vlan 2

Switch(config-if)#ip helper-address 192.168.0.59

Switch(config-if)#end

Switch#copy running-config startup-config

4) Verify the Configurations

View global settings:

Switch#show ip dhcp relay

DHCP relay state: enabled

...

DHCP relay helper address is configured on the following interfaces:

Interface Helper address

VLAN2 192.168.0.59

...

View port settings:

Switch#show ip dhcp relay information interface

Interface Option 82 Status Operation Strategy Format Circuit ID ...

Gi1/0/1 Enable Replace Normal Default:VLAN-PORT ...

Gi1/0/2 Enable Replace Normal Default:VLAN-PORT ...

...

5.4.4 Configuring the DHCP Server

TP-LINK Omada TL-SG2008P - Configuring the DHCP Server - 1

Note:

• Make sure the DHCP server supports Option 82 and more than one DHCP address pool.
- To make sure the DHCP server can reach the computers, you can create static routes or enable dynamic routing protocol like RIP on the DHCP server.
- In this section, we use different notations to distinguish ASCII strings from hexadecimal numbers. An ASCII string is enclosed with quotation marks, such as "123", while a hexadecimal number is divided by colon into parts of two digits, such as 31:32:33.

On the DHCP server, you need to create two DHCP classes to identify the Option 82 payloads of DHCP request packets from Group 1 and Group 2, respectively.

In this example, the DHCP relay agent uses the default circuit ID and remote ID in TLV format. According to packet formats described in Table 1-1 and Table 1-2, the sub-options of the two groups are as shown in the following table.

Table 5-1 Sub-options of Group1 and Group 2

Group Sub-option Type (Hex) Length (Hex) Value (Hex)
1Circuit ID 00 04 00:02:00:01
Remote ID00 06 00:00:FF:FF:27:12
2Circuit ID 00 04 00:02:00:02
Remote ID 00 06 00:00:FF:FF:27:12

The configuration file /etc/dhcpd.conf of the Linux ISC DHCP Server is:

ddns-update-style interim; ignore client-updates;

<h1 id="create-two-classes-to-match-the-pattern-of-option-82-in-dhcp-request-packets-from">Create two classes to match the pattern of Option 82 in DHCP request packets from</h1>
<h1 id="group-1-and-group-2-respectively">Group 1 and Group 2, respectively.</h1>
<h1 id="the-agent-circuit-id-inserted-by-the-dhcp-relay-switch-is-6-bytes-long-in-tlv-format-one">The agent circuit ID inserted by the DHCP relay switch is 6 bytes long in TLV format, one</h1>
<h1 id="byte-for-type-one-byte-for-length-and-4-bytes-for-value-therefore-the-offset-is-2-and-the">byte for Type, one byte for Length, and 4 bytes for Value. Therefore, the offset is 2 and the</h1>
length is 4.
<h1 id="similarly-the-offset-of-the-agent-remote-id-is-2-and-the-length-is-6">Similarly, the offset of the agent remote ID is 2 and the length is 6.</h1>
class "VLAN2Port1" {
    match if substring (option agent.circuit-id, 2, 4) = 00:02:00:01
    and substring (option agent.remote-id, 2, 6) = 00:00:ff:ff:27:12;
}

class "VLAN2Port2" {
    match if substring (option agent.circuit-id, 2, 4) = 00:02:00:02
    and substring (option agent.remote-id, 2, 6) = 00:00:ff:ff:27:12;
}

<h1 id="create-two-ip-address-pools-in-the-same-subnet">Create two IP Address pools in the same subnet.</h1>
<h1 id="assign-different-ip-addresses-to-the-dhcp-clients-in-different-groups">Assign different IP addresses to the DHCP clients in different groups.</h1>
subnet 192.168.2.0 netmask 255.255.255.0 {
    option routers 192.168.2.1;
    option subnet-mask 255.255.255.0;
    option domain-name-servers 192.168.0.59;
    option domain-name "example.com";
    default-lease-time 600;
    max-lease-time 7200;
    authoritative;

pool {
    range 192.168.2.50 192.168.2.100;
    allow members of "VLAN2Port1";
}

pool {
    range 192.168.2.150 192.168.2.200;
    allow members of "VLAN2Port2";
} 

5.5 Example for DHCP L2 Relay

5.5.1 Network Requirements

As the following figure shows, two groups of computers are connected to Switch A, and Switch A is connected to the DHCP server. All devices on the network are in the default VLAN 1. All computers get dynamic IP addresses from the DHCP server. For management convenience, the administrator wants to allocate separate address spaces for the two groups of computers.

Figure 5-32 Network Topology for DHCP L2 Relay
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["DHCP Server"] -->|192.168.10.1/24| B["Switch A DHCP Relay"]
    B --> C["Group 1 Group 2"]
    B --> D["Group 2"]
    B --> E["PC PCPC PC"]
    B --> F["Diode"]
    B --> G["Diode"]

192.168.10.100-192.168.10.150 192.168.10.151-192.168.10.200

5.5.2 Configuration Scheme

To meet the requirements, you can configure DHCP L2 Relay on Switch A to inform the DHCP server of the group information of each PC, so that the DHCP server can assign IP addresses of different address pools to the PCs in different groups.

The overview of the configurations are as follows:

1) Configuring Switch A

a. Enable DHCP L2 Relay globally and on VLAN 1.
b. Configure Option 82 on ports 1/0/1 and 1/0/2.

Demonstrated with T1600G-28TS, 5.5.3 Configuring the DHCP Relay Switch provides configuration procedures in two ways: using the GUI and using the CLI.

2) Configuring the DHCP Server

The detailed configurations on the DHCP server may be different among different devices. You can refer to the related document that is for the DHCP server you use. Demonstrated with a Linux ISC DHCP Server, 5.5.4 Configuring the DHCP Server provides information about how to set its DHCP configuration file.

5.5.3 Configuring the DHCP Relay Switch

Using the GUI

1) Choose the menu L3 FEATURES > DHCP Service > DHCP L2 Relay > Global Config to load the following page. In the Global Config section, enable DHCP L2 Relay globally and click Apply. Enable DHCP L2 Relay on VLAN 1 and click Apply.

Figure 5-33 Enabling DHCP L2 Relay
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Global Config DHCP L2 Relay: ✓ Enable VLAN Config Filter by VLAN: From To Apply ✓ VLAN Status Enable ✓ 1 Enabled Total: 1 entry selected Cancel Apply

2) Choose the menu L3 FEATURES > DHCP Service > DHCP L2 Relay > Port Config to load the following page. Select port 1/0/1, enable Option 82 Support and select Option 82 Policy as Replace. You can configure other parameters according to your needs. In this example, keep Format as Normal and Remote ID Customization as Disabled. Enable Circuit ID Customization and specify the Circuit ID as Group1. Click Apply.

Figure 5-34 Configuring Port 1/0/1
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image UNIT1 Port LAGS Option 82 Option 82 Support Policy Format Circuit ID Circuit ID Remote ID Remote ID LAG Enable Replace Enable Group1 ✓ 1/0/1 Enabled Replace Normal Enabled Group1 Disabled -- □ 1/0/2 Disabled Keep Normal Disabled Disabled □ 1/0/3 Disabled Keep Normal Disabled Disabled □ 1/0/4 Disabled Keep Normal Disabled Disabled □ 1/0/5 Disabled Keep Normal Disabled Disabled □ 1/0/6 Disabled Keep Normal Disabled Disabled □ 1/0/7 Disabled Keep Normal Disabled Disabled □ 1/0/8 Disabled Keep Normal Disabled Disabled Disabled □ 1/0/9 Disabled Keep Normal Disabled Disabled Disabled □ 1/0/10 Disabled Keep Normal Disabled Disabled Total. 28 1 entry selected. Cancel Apply Cancel

3) On the same page, select port 1/0/2, enable Option 82 Support and select Option 82 Policy as Replace. You can configure other parameters according to your needs. In this example, keep Format as Normal and Remote ID Customization as Disabled. Enable Circuit ID Customization and specify the Circuit ID as Group2. Click Apply.

Figure 5-35 Configuring Port 1/0/2
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image UNIT1 Port LAGS Option 82 Support Option 82 Policy Formal Circuit ID Customization Circuit ID Enable Group2 Remote ID Customization Remote ID LAG Enable Group2 1/0/1 Enabled Replace Normal Enabled Group1 Disabled — ✓ 1/0/2 Enabled Replace Normal Enabled Group2 Disabled — 1/0/3 Disabled Keep Normal Disabled Disabled Disabled — 1/0/4 Disabled Keep Normal Disabled Disabled Disabled — 1/0/5 Disabled Keep Normal Disabled Disabled Disabled — 1/0/6 Disabled Keep Normal Disabled Disabled Disabled — 1/0/7 Disabled Keep Normal Disabled Disabled Disabled — 1/0/8 Disabled Keep Normal Disabled Disabled Disabled — 1/0/9 Disabled Keep Normal Disabled Disabled Disabled — 1/0/10 Disabled Keep Normal Disabled Disabled Cancel Apply

4) Click Save the settings.

Using the CLI

1) Enable DHCP L2 Relay globally and on VLAN1.

Switch#configure

Switch(config)#ip dhcp I2relay

Switch(config)#ip dhcp I2relay vlan 1

2) On port 1/0/1, enable Option 82 and select Option 82 Policy as Replace. You can configure other parameters according to your needs. In this example, keep Format as Normal and Remote ID Customization as Disabled. Enable Circuit ID Customization and specify the Circuit ID as Group1.

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#ip dhcp l2relay information option

Switch(config-if)#ip dhcp I2relay information strategy replace

Switch(config-if)#ip dhcp I2relay information circuit-id Group1

Switch(config-if)#exit

3) On port 1/0/2, enable Option 82 and select Option 82 Policy as Replace. You can configure other parameters according to your needs. In this example, keep Format as Normal and Remote ID Customization as Disabled. Enable Circuit ID Customization and specify the Circuit ID as Group2.

Switch(config)#interface gigabitEthernet 1/0/2

Switch(config-if)#ip dhcp l2relay information

Switch(config-if)#ip dhcp l2relay information strategy replace

Switch(config-if)#ip dhcp I2relay information circuit-id Group2

Switch(config-if)#end

Switch#copy running-config startup-config

Verify the Configurations

View global settings:

Switch#show ip dhcp l2relay

Global Status: Enable

VLAN ID: 1

View port settings:

Switch#show ip dhcp l2relay information interface gigabitEthernet 1/0/1

Interface Option 82 Status Operation Strategy Format Circuit ID ...

Gi1/0/1 Enable Replace Normal Group1 ...

Switch#show ip dhcp I2relay information interface gigabitEthernet 1/0/1

Interface Option 82 Status Operation Strategy Format Circuit ID ...

• Make sure the DHCP server supports Option 82 and more than one DHCP address pool.
- To make sure the DHCP server can reach the computers, you can create static routes or enable dynamic routing protocol like RIP on the DHCP server.
- In this section, we use different notations to distinguish ASCII strings from hexadecimal numbers. An ASCII string is enclosed with quotation marks, such as "123", while a hexadecimal number is divided by colon into parts of two digits, such as 31:32:33.

On the DHCP server, you need to create two DHCP classes to identify the Option 82 payloads of DHCP request packets from Group 1 and Group 2, respectively.

In this example, the DHCP relay agent uses the customized circuit ID and default remote ID in TLV format. According to packet format described in Table 1-1 and Table 1-2, the sub-options of the two groups are as shown in the following table.

Table 5-2 Sub-options of Group1 and Group 2

Group Sub-option Type (Hex) Length (Hex) Value
1Circuit ID 00 06“Group1” as an ASCII string (or 47:72:6F:75:70:31 in hexadecimal)
Remote ID 00 0600:00:FF:FF:27:12
2Circuit ID 00 06“Group2” as an ASCII string (or 47:72:6F:75:70:32 in hexadecimal)
Remote ID 00 0600:00:FF:FF:27:12

The configuration file /etc/dhcpd.conf of the Linux ISC DHCP Server is:

ddns-update-style interim;

ignore client-updates;

# Create two classes to match the pattern of Option 82 in DHCP request packets from

# Group 1 and Group 2, respectively.

# The agent circuit ID inserted by the DHCP relay switch is 8 byte long in TLV format, one

# byte for Type, one byte for Length, and 6 bytes for Value. Therefore, the offset is 2 and the length is 6.

# Similarly, the offset of the agent remote ID is 2 and the length is 6.

class "Group1" {
    match if substring (option agent.circuit-id, 2, 6) = "Group1"
    and substring (option agent.remote-id, 2, 6) = 00:00:ff:ff:27:12;
}

class "Group2" {
    match if substring (option agent.circuit-id, 2, 6) = "Group2"
    and substring (option agent.remote-id, 2, 6) = 00:00:ff:ff:27:12;
}

<h1 id="create-two-ip-address-pools-in-the-same-subnet-2">Create two IP Address pools in the same subnet.</h1>
<h1 id="assign-different-ip-addresses-to-the-dhcp-clients-in-different-groups-2">Assign different IP addresses to the DHCP clients in different groups.</h1>
subnet 192.168.10.0 netmask 255.255.255.0 {
    option routers 192.168.10.1;
    option subnet-mask 255.255.255.0;
    option domain-name-servers 192.168.10.1;
    option domain-name "example.com";
    default-lease-time 600;
    max-lease-time 7200;
    authoritative;

pool {
    range 192.168.10.100 192.168.10.150;
    allow members of "Group1";
}

pool {
    range 192.168.10.151 192.168.10.200;
    allow members of "Group2";
} 

6

Appendix: Default Parameters

Default settings of DHCP Server are listed in the following table.

Table 6-1 Default Settings of DHCP Server

Parameter Default Setting
Global Config
DHCP Server Disabled
Option 60 None
Option 138 None
Ping Time Config
Ping Packets 1
Ping Timeout 100 ms
Excluded IP Address
Start IP Address None
End IP Address None
Pool Setting
Pool Name None
Network Address None
Subnet Mask None
Lease Time 120 min
Default GatewayNone
DNS ServerNone
NetBIOS ServerNone
NetBIOS Node TypeNone
Next Server AddressNone
Domain NameNone
BootfileNone
Manual Binding
Pool Name None
IP Address None
Binding Mode Client ID
Client Id None
Hardware Address None
Hardware Type Ethernet

Default settings of DHCP Relay are listed in the following table.

Table 6-2 Default Settings of DHCP Relay

Parameter Default Setting
DHCP Relay
DHCP Relay Disabled
DHCP Relay Hops 4
DHCP Relay Time Threshold 0
Option 82 Configuration
Option 82 Support Disabled
Option 82 Policy Keep
FormatNormal
Circuit ID CustomizationDisabled
Circuit IDNone
Remote ID CustomizationDisabled
Remote ID None
DHCP Interface Relay
Interface IDNone
Server AddressNone
DHCP VLAN Relay
Interface ID None
VLAN ID None
Server Address None

Default settings of DHCP L2 Relay are listed in the following table.

Table 6-3 Default Settings of DHCP L2 Relay

Parameter Default Setting
Global Config
DHCP Relay Disabled
VLAN Status Disabled
Port Config
Option 82 Support Disabled
Option 82 Policy Keep
Format Normal
Circuit ID Customization Disabled
Circuit ID None
Remote ID CustomizationDisabled
Remote ID None

Part 21

Configuring ARP

CHAPTERS

  1. Overview
  2. ARP Configurations
  3. Appendix: Default Parameters

1 Overview

ARP (Address Resolution Protocol) is used to map IP addresses to MAC addresses. Taking an IP address as input, ARP learns the associated MAC address, and stores the IP-MAC address association in an ARP entry for rapid retrieval.

1.1 Supported Features

ARP Table

The ARP table displays all the ARP entries, including dynamic entries and static entries.

Dynamic Entry: Automatically learned and will be deleted after aging time.

Static Entry: Added manually and will be remained unless modified or deleted manually.

Static ARP

You can manually add ARP entries by specifying the IP addresses and MAC addresses.

Gratuitous ARP

Gratuitous ARP is a special kind of ARP. Both the source and destination addresses of the gratuitous ARP packet are the sender its own IP address. It is used to detect duplicate IP address. If an interface sends a gratuitous ARP packet and no replies are received, then the sender knows its IP address is not used by other devices.

Proxy ARP

Normally, the ARP packets can only be transmitted in one broadcast domain, which means if two devices in the same network segment are connected to different Layer 3 interfaces, they cannot communicate with each other because they cannot learn each other's MAC address using ARP packets.

Proxy ARP solves this problem. As shown below, when a host sends an ARP request to another device that is not in the same broadcast domain but on the same network segment, the Layer 3 interface with Proxy ARP enabled will respond the ARP request with its own MAC address if the destination IP is reachable. After that, the ARP request sender sends packets to the switch, and the switch forwards the packets to the intended device.

Figure 1-1 Proxy ARP Application
TP-LINK Omada TL-SG2008P - Proxy ARP - 1

flowchart
graph LR
    A["Computer 1"] -->|VLAN Interface 2 192.168.2.1/24| B["Switch"]
    B -->|VLAN Interface 3 192.168.3.1/24| C["Computer 2"]
    A -->|192.168.2.10/16 192.168.3.20/16| A

Local Proxy ARP

Local Proxy ARP is similar with Proxy ARP. As shown below, two hosts are in the same VLAN and connected to VLAN interface 1, but port 1/0/1 and port 1/0/2 are isolated on Layer 2. In this case, both of the hosts cannot receive each other's ARP request. So they cannot communicate with each other because they cannot learn each other's MAC address using ARP packets.

To solve this problem, you can enable Local Proxy ARP on the Layer 3 interface and the interface will respond the ARP request sender with its own MAC address. After that, the ARP request sender sends packets to the Layer 3 interface, and the interface forwards the packets to the intended device.

Figure 1-2 Local Proxy ARP Application
TP-LINK Omada TL-SG2008P - Local Proxy ARP - 1

flowchart
graph TD
    A["VLAN Interface 1\nIP: 192.168.0.1/24"] --> B["Port 1/0/1 Port 1/0/2"]
    B --> C["VLAN 1"]
    C --> D["Computer 1"]
    C --> E["Computer 2"]

2 ARP Configurations

With ARP configurations, you can:

■ View dynamic and static ARP entries.
■ Add or delete static ARP entries.

To configure the Gratuitous ARP feature:

■ Configure the Gratuitous ARP globally and set the Gratuitous ARP sending interval

To configure the Proxy ARP feature:

■ Enable Proxy function for VLAN interfaces or routed ports.

To configure the Local Proxy ARP feature:

■ Enable Local Proxy function for VLAN interfaces or routed ports.

2.1 Using the GUI

2.1.1 Viewing the ARP Entries

The ARP table consists of two kinds of ARP entries: dynamic and static.

■ Dynamic Entry: Automatically learned and will be deleted after aging time.
■ Static Entry: Added manually and will be remained unless modified or deleted manually.

Choose the menu L3 FEATURES > ARP > ARP Table > ARP Table to load the following page.

Figure 2-1 Viewing the ARP Entries

ARP Table
Refresh
InterfaceIP AddressMAC AddressType
VLAN1192.168.0.5200-0a-eb-13-23-7bDynamic
VLAN1192.168.0.22600-0a-eb-13-23-97Dynamic
VLAN1192.168.0.20000-19-66-35-e1-b0Dynamic
Total: 3

Interface Displays the network interface of an ARP entry.

IP Address Displays the IP address of an ARP entry.

MAC Address Displays the MAC address of an ARP entry.

Type Displays the type of an ARP entry.

Static: The entry is added manually and will always remain the same.

Dynamic: The entry that will be deleted after the aging time leased. The default aging time value is 600 seconds. If you want to change the aging time, you can use the CLI to configure it.

2.1.2 Adding Static ARP Entries Manually

You can add desired static ARP entries by manually specifying the IP addresses and MAC addresses.

Choose the menu L3 FEATURES > ARP > Static ARP and click + Add to load the following page.

Figure 2-2 Adding Static ARP Entries
TP-LINK Omada TL-SG2008P - Adding Static ARP Entries Manually - 1

text_image Static ARP IP Address: (Format: 192.168.0.10) MAC Address: (Format: 00-00-00-00-00-01) Cancel Create

Enter the IP address and MAC address, then click Create.

IP address Specify the IP address of the static ARP entry.

MAC address Specify the MAC address.of the static ARP entry.

2.1.3 Configuring Gratuitous ARP

Choose the menu L3 FEATURES > ARP > Gratuitous ARP to load the following page.

Figure 2-3 Configuring Gratuitous ARP
TP-LINK Omada TL-SG2008P - Configuring Gratuitous ARP - 1

text_image Gratuitous ARP Global Settings Send on IP Interface Status Up: ✓ Enable Send on Duplicate IP Detected: □ Enable Gratuitous ARP Learning: □ Enable Apply Gratuitous ARP Table Interface Name Gratuitous ARP Periodical Send Interval Gi1/0/18 0 VLAN1 0 Total: 2 1 entry selected. Cancel Apply

Follow these steps to configure the Gratuitous feature for the interface.

1) In the Gratuitous ARP Global Settings section, configure the global parameters for gratuitous ARP. Then click Apply.

Send on IP Interface Status UpWith this option enabled, the interface will send gratuitous ARP request packets when its status becomes up. This is used to announce the interface's IP address to the other hosts. It is enabled by default.
Send on Duplicate IP DetectedWith this option enabled, the interface will send gratuitous ARP request packets when a gratuitous ARP request packet is received for which the IP address is the same as the interface's. In this case, the switch knows that another host is using the same IP address as its own. To claim the IP address for the correct owner, the interface sends gratuitous ARP packets. It is disabled by default.
Gratuitous ARP LearningNormally, the switch only updates the MAC address table by learning from the ARP reply packet or normal ARP request packet. With this option enabled, the switch will also update the MAC address table by learning from the received gratuitous ARP packets. It is disabled by default.

2) In the Gratuitous ARP Table section, configure the interval of sending gratuitous ARP request packets for the interface. Then click Apply.

Interface Name Displays the Interface ID of the Layer 3 interface.
Gratuitous ARP Periodical Send IntervalEnter the interval of sending gratuitous ARP request packets for the interface.A value of 0 means the interface will not send gratuitous ARP request packets periodically.

2.1.4 Configuring Proxy ARP

Proxy ARP is used in the situation that two devices are in the same network segment but connected to different Layer 3 interfaces.

Choose the menu L3 FEATURES> ARP > Proxy ARP > Proxy ARP to load the following page.

Figure 2-4 Configuring Proxy ARP
TP-LINK Omada TL-SG2008P - Configuring Proxy ARP - 1

text_image Proxy ARP Information ✓ ID IP Address Subnet Mask Interface Status ✓ 1 192.168.0.100 255.255.255.0 VLAN1 Enabled Total: 1 1 entry selected. Cancel Apply

Select the desired interface and enable proxy ARP. Then click Apply.

IP Address Displays the IP address of the Layer 3 interface

Subnet Mask Displays the subnet mask of the IP address.

Status Enable proxy ARP feature on the interface. The interface will respond the ARP request sender with its own MAC address.

2.1.5 Configuring Local Proxy ARP

Local Proxy ARP is used in the situation that two devices are in the same VLAN but isolated on the layer 2 ports.

Choose the menu L3 FEATURES > ARP > Proxy ARP > Local Proxy ARP to load the following page.

Figure 2-5 Configuring Local Proxy ARP
Local Proxy ARP Information
TP-LINK Omada TL-SG2008P - Configuring Local Proxy ARP - 1

text_image ID IP Address Subnet Mask Interface Status ✓ 1 192.168.0.100 255.255.255.0 VLAN1 Disabled Total: 1 1 entry selected. Cancel Apply

Select the desired interface and enable local proxy ARP. Then click Apply.

IP Address Displays the IP address of the Layer 3 interface

Subnet Mask Displays the subnet mask of the IP address.

Status Enable local proxy ARP feature on the interface. The interface will respond the ARP request sender with its own MAC address.

2.2 Using the CLI

2.2.1 Configuring the ARP Entry

■ Adding Static ARP Entries

Follow these steps to add static ARP entries:

Step 1 configure

Enter global configuration mode.

Step 2 arp

ip mac type

Add a static ARP entry.

ip: Enter the IP address of the static ARP entry.

mac: Enter the MAC address of the static ARP entry.

type:Enter the ARP type. Configure it as 'arpa'.

Step 3 show arp [ip] [mac]

ip: Specify the IP address of your desired ARP entry.

mac: Specify the MAC address of your desired ARP entry.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

This example shows how to create a static ARP entry with the IP as 192.168.0.1 and the MAC as 00:11:22:33:44:55:

Switch#configure

Switch(config)#arp 192.168.0.1 00:11:22:33:44:55 arpa

Switch(config)#show arp 192.168.0.1

Interface

Address

Hardware Addr

Type

Vlan1

192.168.0.1

00:11:22:33:44:55

STATIC

Switch(config)#end

Switch#copy running-config startup-config

■ Configuring the Aging Time of Dynamic ARP Entries

Follow these steps to configure the aging time of dynamic ARP entries:

Step 1 configure

Enter global configuration mode.

Step 2 arp timeout

timeout

Configure the ARP aging time of the VLAN interface or routed port.

timeout: Specify the value of aging time, which ranges from 1 to 3000 in seconds. The default value is 1200 seconds.

Step 3 end

Return to privileged EXEC mode.

Step 4 copy running-config startup-config

Save the settings in the configuration file.

This example shows how to configure the aging time of dynamic ARP entries as 1000 seconds:

Switch#configure

Switch(config)#arp timeout 1000

Switch(config)#end

Switch#copy running-config startup-config

■ Clearing Dynamic Entries

Step 1 configure

Enter global configuration mode.

Step 2 clear arp-cache

Clear all the dynamic ARP entries.

Step 3 copy running-config startup-config

Save the settings in the configuration file.

■ Renewing Dynamic ARP Entries Automatically

Step 1 configure

Enter global configuration mode.

Step 2 arp dunamicrenew

Enable the switch to automatically renew dynamic ARP entries. By default, it is enabled..

Step 3 copy running-config startup-config

Save the settings in the configuration file.

■ Viewing ARP Entries

On privileged EXEC mode or any other configuration mode, you can use the following command to view ARP entries:

show arp [ip] [mac]

ip: Specify the IP address of your desired ARP entry.

mac: Specify the MAC address of your desired ARP entry.

show ip arp { fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel lagid | vlan vid }

Verify the active ARP entries associated with a Layer 3 interface.

port: Specify the number of the routed port.

lagid: Specify the ID of the LAG.

vid: Specify the VLAN interface ID.

2.2.2 Configuring the Gratuitous ARP

■ Configuring Gratuitous ARP Globally

Follow these steps to add static ARP entries:

Step 1 configure

Enter global configuration mode.

Step 2 gratuitous-arp intf-status-up enable

Enable the Layer 3 interface to send a gratuitous ARP packet to detect if its IP address is used by other devices. It is enabled by default

Step 3 gratuitous-arp dup-ip-detected enable

(Optional) Enable the Layer 3 interface to send a gratuitous packet when the interface received a gratuitous ARP packet with the same IP address with its own. It is disabled by default.

Step 4 gratuitous-arp learning enable

(Optional) Enable the switch to learn MAC address entries from gratuitous ARP packets. Generally, the switch only learns MAC address entries form normal ARP packets. With this option enabled, the switch will also learn MAC address entries from gratuitous ARP packets. By default, it is disabled.

Step 5 show gratuitous-arp

Show the gratuitous ARP configuration.

Step 6 end

Return to privileged EXEC mode.

Step 7 copy running-config startup-config

Save the settings in the configuration file.

This example shows how to enable Send on IP Interface Status Up, Send on Duplicate IP Detected and Gratuitous ARP Learning features:

Switch#configure

Switch(config)#gratuitous-arp dup-ip-detected enable

Switch(config)#gratuitous-arp intf-status-up enable

Switch(config)#gratuitous-arp learning enable

Switch(config)#show gratuitous-arp

Send on IP interface Status up : Enabled

Send on Duplicate IP Detected : Enabled

Gratuitous ARP Learning : Enabled

Interface Gratuitous ARP Periodical Send Interval

Gi1/0/18 0

VLAN1 0

Switch(config)#end

Switch#copy running-config startup-config

■ Configuring Interval of Sending Gratuitous ARP Packets

Follow these steps to configure gratuitous ARP packets for Layer 3 interfaces:

Step 1 configure

Enter global configuration mode.
Step 2There are three types of Layer 3 interface that are able to send gratuitous ARP packets: routed port, port-channel and VLAN interface.interface { fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | ten-range gigabitEthernet port-list | port-channel port-channel | range port-channel port-channel-list |}no switch portEnter interface configuration mode and change the port or port-channel to be a Layer 3 interface.
Interface vlan vlan-idEnter the vlan interface configuration mode.vlan-id: Enter the interface VLAN ID.
Step 3 gratuitous-arp send-interval interval

Step 4 show gratuitous-arp

Show the gratuitous ARP configuration.

Step 5 end

Return to privileged EXEC mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

This example shows how to configure the interval of sending gratuitous ARP packets for VLAN interface 1 as 10 seconds:

Switch#configure

Switch(config)#interface vlan 1

Switch(config-if)#gratuitous-arp send-interval 10

Switch(config-if)#show gratuitous-arp

...

Interface Gratuitous ARP Periodical Send Interval

VLAN1 10

Switch(config-if)#end

Switch#copy running-config startup-config

2.2.3 Configuring Proxy ARP

You can configure proxy ARP and local proxy ARP.

■ Configuring Proxy ARP

Follow these steps to Proxy ARP on the VLAN interface, routed port or port channel.

Step 1 configure

Enter global configuration mode.

Step 2There are three types of Layer 3 interface can be enabled with Proxy ARP: routed port, port-channel and VLAN interface.
interface { fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | ten-range gigabitEthernet port-list | port-channel port-channel | range port-channel port-channel-list }
no switch port
Enter interface configuration mode and change the port or port-channel to be a Layer 3 interface.
Interface vlan vlan-id
Enter the vlan interface configuration mode.
vlan-id: Enter the interface VLAN ID.
Step 3 ip proxy-arp
Step 4 show ip proxy-arp
Step 5 end
Step 6 copy running-config startup-config
Save the settings in the configuration file.

This example shows how to enable Proxy ARP function for VLAN interface 1:

Switch#configure

Switch(config)#interface vlan 1

Switch(config-if)#ip proxy-arp

Switch(config-if)#show ip proxy-arp

InterfaceIP AddressIP MaskStatus
vlan 1192.168.0.1255.255.255.0Enabled

Switch(config-if)#end

Switch#copy running-config startup-config

■ Configuring Local Proxy ARP

Follow these steps to Local Proxy ARP on the VLAN interface, routed port or port channel.

Step 1 configure

Enter global configuration mode.

Step 2There are three types of Layer 3 interface can be enabled with Local Proxy ARP: routed port, port-channel and VLAN interface.interface { fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | ten-range gigabitEthernet port-list | port-channel port-channel | range port-channel port-channel-list }no switch portEnter interface configuration mode and change the port or port-channel to be a Layer 3 interface.
Interface vlan vlan-idEnter the vlan interface configuration mode.vlan-id: Enter the interface VLAN ID.
Step 3 ip local-proxy-arpEnable Local Proxy ARP function on the specified Layer 3 interface..
Step 4 show ip local-proxy-arpShow the Local Proxy ARP configuration..
Step 5 endReturn to privileged EXEC mode.
Step 6 copy running-config startup-configSave the settings in the configuration file.

This example shows how to enable Local Proxy ARP function for VLAN interface 1:

Switch#configure

Switch(config)#interface vlan 1

Switch(config-if)#ip local-proxy-arp

Switch(config-if)#show ip local-proxy-arp

InterfaceIP AddressIP MaskStatus
vlan 1192.168.0.1255.255.255.0Enabled

Switch(config-if)#end

Switch#copy running-config startup-config

3 Appendix: Default Parameters

Default ARP settings are listed in the following tables.

Table 3-1 Default Gratuitous Settings

Parameter Default Setting
Send on IP Interface Status Up Enabled
Send on Duplicate IP Detected Disabled
Gratuitous ARP Learning Disabled
Gratuitous ARP Periodical Send Interval 0 second

Part 22

Configuring QoS

CHAPTERS

  1. QoS
  2. Class of Service Configuration
  3. Bandwidth Control Configuration
  4. Voice VLAN Configuration
  5. Auto VoIP Configuration
  6. Configuration Examples
  7. Appendix: Default Parameters

1 QoS

1.1 Overview

With network scale expanding and applications developing, internet traffic is dramatically increased, thus resulting in network congestion, packet drops and long transmission delay. Typically, networks treat all traffic equally on FIFO (First In First Out) delivery basis, but nowadays many special applications like VoD, video conferences, VoIP, etc, require more bandwidth or shorter transmission delay to guarantee the performance.

With QoS (Quality of Service) technology, you can classify and prioritize network traffic to provide differentiated services to certain types of traffic.

1.2 Supported Features

You can configure the class of service, bandwidth control, Voice VLAN and Auto VoIP features on the switch to maximize the network performance and bandwidth utilization.

Class of Service

The switch classifies the ingress packets, maps the packets to different priority queues and then forwards the packets according to specified scheduler settings to implement QoS function.

■ Priority Mode: Three modes are supported, Port Priority, 802.1p Priority and DSCP Priority.
■ Scheduler Mode: Two scheduler types are supported, Strict and Weighted.

Bandwidth Control

Bandwidth Control functions to control the traffic rate and traffic threshold on each port to ensure network performance.

■ Rate limit functions to limit the ingress/egress traffic rate on each port. In this way, the network bandwidth can be reasonably distributed and utilized.
■ Storm Control function allows the switch to monitor broadcast packets, multicast packets and UL-frames (Unknown unicast frames) in the network. If the transmission rate of the packets exceeds the set rate, the packets will be automatically discarded to avoid network broadcast storm.

Voice VLAN and Auto VoIP

The voice VLAN and Auto VoIP features are used to prioritize the transmission of voice traffic. Voice traffic is typically more time-sensitive than data traffic, and the voice quality

can deteriorate a lot because of packet loss and delay. To ensure the high voice quality, you can configure Voice VLAN or Auto VoIP.

These two features can be enabled on the ports that transmit voice traffic only or transmit both voice traffic and data traffic. Voice VLAN can change the voice packets' 802.1p priority and transmit the packets in desired VLAN. Auto VoIP can inform the voice devices of send the packets with specific configuration by working with the LLDP-MED feature.

2 Class of Service Configuration

With class of service configurations, you can:

■ Configure port priority
■ Configure 802.1p priority
■ Configure DSCP priority
■ Specify the scheduler settings

Configuration Guidelines

■ Select the priority mode that the ports trust according to your network requirements.

A port can use only one priority to classify the ingress packets. Three priority modes are supported on the switch: Port Priority, 802.1P Priority and DSCP Priority.

■ Port Priority

In this mode, the switch prioritizes packets according to their ingress ports, regardless of the packet field or type.

■ 802.1P Priority

802.1P defines the first three bits in 802.1Q Tag as PRI field. The PRI values are from 0 to 7.802.1P priority determines the priority of packets based on the PRI value.

In this mode, the switch only prioritizes packets with VLAN tag, regardless of the IP header of the packets.

■ DSCP Priority

DSCP priority determines the priority of packets based on the ToS (Type of Service) field in their IP header. RFC2474 re-defines the ToS field in the IP packet header as DS field. The first six bits (bit 0-bit 5) of the DS field is used to represent DSCP priority. The DSCP values are from 0 to 63.

In this mode, the switch only prioritizes IP packets.

■ Specify the 802.1p to queue mapping according to your needs.

For 802.1p Priority, the packets will be forwarded according to the 802.1p to queue mapping directly.

For Port Priority and DSCP Priority, the port priority and DSCP priority will first be mapped to the 802.1p priority, and then mapped to the queue according to the 802.1p to queue mapping.

2.1 Using the GUI

2.1.1 Configuring Port Priority

■ Configuring the Trust Mode and Port to 802.1p Mapping

Choose the menu QoS > Class of Service > Port Priority to load the following page.

Figure 2-1 Configuring the Trust Mode and Port to 802.1p Mapping
TP-LINK Omada TL-SG2008P - Configuring Port Priority - 1

text_image Port Priority Config UNIT1 LAGS Port 802.1p Priority Trust Mode LAG ✓ 1/0/1 0 Untrusted -- □ 1/0/2 0 Untrusted -- □ 1/0/3 0 Untrusted -- □ 1/0/4 0 Untrusted -- □ 1/0/5 0 Untrusted -- □ 1/0/6 0 Untrusted -- □ 1/0/7 0 Untrusted -- □ 1/0/8 0 Untrusted -- □ 1/0/9 0 Untrusted -- □ 1/0/10 0 Untrusted -- Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure the parameters of the port priority:

1) Select the desired ports, specify the 802.1p priority and set the trust mode as Untrusted.

802.1p Priority Specify the port to 802.1p mapping for the desired port. The ingress packets from one port are first mapped to 802.1p priority based on the port to 802.1p mapping, then to TC queues based on the 802.1p to queue mapping. The untagged packets from one port will be added an 802.1p priority value according to the port to 802.1p priority mapping.

Trust Mode Select the Trust mode as Untrusted. In this mode, the packets will be processed according to the port priority configuration.

2) Click Apply.

■ Configuring the 802.1p to Queue Mapping

Choose the menu QoS > Class of Service > 802.1p Priority to load the following page.

Figure 2-2 Configuring the 802.1p to Queue Mapping
TP-LINK Omada TL-SG2008P - Configuring Port Priority - 2

text_image 802.1p to Queue Mapping 802.1p Priority Queue 0: TC-1 1: TC-0 2: TC-2 3: TC-3 4: TC-4 5: TC-5 6: TC-6 7: TC-7 802.1p Remap 802.1p Priority Remap 0: 0 1: 1 2: 2 3: 3 4: 4 5: 5 6: 6 7: 7 Apply Apply

In the 802.1p to Queue Mapping section, configure the mappings and click Apply.

802.1p PriorityDisplays the number of 802.1p priority. In QoS, 802.1p priority is used to represent class of service.
Queue Select the TC queue for the desired 802.1p priority. The packets with the desired 802.1p priority will be put in the corresponding queue.

2.1.2 Configuring 802.1p Priority

■ Configuring the Trust Mode

Choose the menu QoS > Class of Service > Port Priority to load the following page.

Figure 2-3 Configuring the Trust Mode
TP-LINK Omada TL-SG2008P - Configuring 802.1p Priority - 1

text_image Port Priority Config UNIT1 LAGS Port 802.1p Priority Trust Mode LAG ✓ 1/0/1 0 Untrusted -- □ 1/0/2 0 Untrusted -- □ 1/0/3 0 Untrusted -- □ 1/0/4 0 Untrusted -- □ 1/0/5 0 Untrusted -- □ 1/0/6 0 Untrusted -- □ 1/0/7 0 Untrusted -- □ 1/0/8 0 Untrusted -- □ 1/0/9 0 Untrusted -- □ 1/0/10 0 Untrusted -- Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure the trust mode:

1) Select the desired ports and set the trust mode as Trust 802.1p.

Trust ModeSelect the Trust mode as Trust 802.1p. In this mode, the tagged packets will be processed according to the 802.1p priority configuration and the untagged packets will be processed according to the port priority configuration.

2) Click Apply.

■ Configuring the 802.1p to Queue Mapping and 802.1p Remap

For Certain Devices:

Choose the menu QoS > Class of Service > 802.1p Priority to load the following page.

Figure 2-4 Configuring the 802.1p to Queue Mapping and 802.1p Remap
TP-LINK Omada TL-SG2008P - For Certain Devices: - 1

text_image 802.1p to Queue Mapping 802.1p Priority Queue 0: TC-0 1: TC-1 2: TC-2 3: TC-3 4: TC-4 5: TC-5 6: TC-6 7: TC-7 802.1p Remap UNIT1 LAGS Port 0 1 2 3 4 5 6 7 LAG ✓ 1/0/1 0 1 2 3 4 5 6 7 -- □ 1/0/2 0 1 2 3 4 5 6 7 -- □ 1/0/3 0 1 2 3 4 5 6 7 -- □ 1/0/4 0 1 2 3 4 5 6 7 -- □ 1/0/5 0 1 2 3 4 5 6 7 -- □ 1/0/6 0 1 2 3 4 5 6 7 -- □ 1/0/7 0 1 2 3 4 5 6 7 -- □ 1/0/8 0 1 2 3 4 5 6 7 -- □ 1/0/9 0 1 2 3 4 5 6 7 -- □ 1/0/10 0 1 2 3 4 5 6 7 -- Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure the parameters of the 802.1p priority:

1) In the 802.1p to Queue Mapping section, configure the mappings and click Apply.

802.1p Priority

Displays the number of 802.1p priority. In QoS, 802.1p priority is used to represent class of service. IEEE 802.1p standard defines three bits in 802.1Q tag as PRI filed. The PRI values are called 802.1p priority and used to represent the priority of the layer 2 packets. This function requires packets with VLAN tags.

Queue Select the TC queue for the desired 802.1p priority. The packets with the desired 802.1p priority will be put in the corresponding queue.

2) (Optional) In the 802.1p Remap section, configure the 802.1p to 802.1p mappings for ports and click Apply.

0 - 7

Select the number of 802.1p priority to which the desired 802.1p priority will be remapped. 802.1p Remap is used to modify the 802.1p priority of the ingress packets. When the switch detects the packets with desired 802.1p priority, it will modify the value of 802.1p priority according to the map.

For Certain Devices:

Choose the menu QoS > Class of Service > 802.1p Priority to load the following page.

Figure 2-5 Configuring the 802.1p to Queue Mapping and 802.1p Remap
TP-LINK Omada TL-SG2008P - For Certain Devices: - 1

text_image 802.1p to Queue Mapping 802.1p Priority Queue 0: TC-1 1: TC-0 2: TC-2 3: TC-3 4: TC-4 5: TC-5 6: TC-6 7: TC-7 802.1p Remap 802.1p Priority Remap 0: 0 1: 1 2: 2 3: 3 4: 4 5: 5 6: 6 7: 7 Apply Apply

Follow these steps to configure the parameters of the 802.1p priority:

1) In the 802.1p to Queue Mapping section, configure the mappings and click Apply.

802.1p Priority

Displays the number of 802.1p priority. In QoS, 802.1p priority is used to represent class of service. IEEE 802.1p standard defines three bits in 802.1Q tag as PRI filed. The PRI values are called 802.1p priority and used to represent the priority of the layer 2 packets. This function requires packets with VLAN tags.

Queue Select the TC queue for the desired 802.1p priority. The packets with the desired 802.1p priority will be put in the corresponding queue.

2) (Optional) In the 802.1p Remap section, configure the 802.1p to 802.1p mappings and click Apply.

802.1p PriorityDisplays the number of 802.1p priority. In QoS, 802.1p priority is used to represent class of service. IEEE 802.1p standard defines three bits in 802.1Q tag as PRI filed. The PRI values are called 802.1p priority and used to represent the priority of the layer 2 packets. This function requires packets with VLAN tags.
RemapSelect the number of 802.1p priority to which the original 802.1p priority will be remapped. 802.1p Remap is used to modify the 802.1p priority of the ingress packets. When the switch detects the packets with desired 802.1p priority, it will modify the value of 802.1p priority according to the map.

TP-LINK Omada TL-SG2008P - For Certain Devices: - 2

Note:

In Trust 802.1p mode, the untagged packets will be added an 802.1p priority based on the port to 802.1p mapping and will be forwarded according to the 802.1p to queue mapping.

2.1.3 Configuring DSCP Priority

■ Configuring the Trust Mode

Choose the menu QoS > Class of Service > Port Priority to load the following page.

Figure 2-6 Configuring the Trust Mode
TP-LINK Omada TL-SG2008P - ■ Configuring the Trust Mode - 1

text_image Port Priority Config UNIT1 LAGS Port 802.1p Priority Trust Mode LAG ✓ 1/0/1 0 Untrusted -- □ 1/0/2 0 Untrusted -- □ 1/0/3 0 Untrusted -- □ 1/0/4 0 Untrusted -- □ 1/0/5 0 Untrusted -- □ 1/0/6 0 Untrusted -- □ 1/0/7 0 Untrusted -- □ 1/0/8 0 Untrusted -- □ 1/0/9 0 Untrusted -- □ 1/0/10 0 Untrusted -- Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure the trust mode:

1) Select the desired ports and set the trust mode as Trust DSCP.

Trust Mode Select the Trust mode as Trust DSCP. In this mode, the IP packets will be processed according to the DSCP priority configuration and the non-IP packets will be processed according to the port priority configuration.

2) Click Apply.

■ Configuring the 802.1p to Queue Mapping

Choose the menu QoS > Class of Service > 802.1p Priority to load the following page.

Figure 2-7 Configuring the 802.1p to Queue Mapping

802.1p to Queue Mapping
802.1p PriorityQueue
0:TC-1 ▼
1:TC-0 ▼
2:TC-2 ▼
3:TC-3 ▼
4:TC-4 ▼
5:TC-5 ▼
6:TC-6 ▼
7:TC-7 ▼
802.1p Remap
802.1p PriorityRemap
0:0 ▼
1:1 ▼
2:2 ▼
3:3 ▼
4:4 ▼
5:5 ▼
6:6 ▼
7:7 ▼

In the 802.1p to Queue Mapping section, configure the mappings and click Apply.

802.1p Priority

Displays the number of 802.1p priority. In QoS, 802.1p priority is used to represent class of service.

Queue Select the TC queue for the desired 802.1p priority. The packets with the desired 802.1p priority will be put in the corresponding queue.

■ Configuring the DSCP to 802.1p Mapping and the DSCP Remap

For Certain Devices:

Choose the menu QoS > Class of Service >DSCP Priority to load the following page.

Figure 2-8 Configuring the DSCP to 802.1p Mapping and the DSCP Remap
TP-LINK Omada TL-SG2008P - For Certain Devices: - 1

other DSCP Priority Config | Port | DSCP Priority | 802.1p Priority | DSCP Remap | | :--- | :--- | :--- | :--- | | 1 | 0 | 0 | 0 be (000000) | | 2 | 1 | 0 | 1 | | 3 | 2 | 0 | 2 | | 4 | 3 | 0 | 3 | | 5 | 4 | 0 | 4 | | 6 | 5 | 0 | 5 | | 7 | 6 | 0 | 6 | | 8 | 7 | 0 | 7 | | 9 | 8 | 1 | 8 cs1 (001000) | | Total: 64 | 1 entry selected. | Cancel | Apply |

Follow these steps to configure the DSCP Priority:

1) Select the desired port, configure the DSCP to 802.1p mapping and the DSCP remap.

DSCP PriorityDisplays the number of DSCP priority. DSCP Priority is used to classify the packets based on the value of DSCP, and map them to different queues. ToS (Type of Service) is a part of IP header, and DSCP uses the first six bits of ToS to represent the priority of IP packets. The DSCP values range from 0 to 63.
802.1p PrioritySpecify the DSCP to 802.1p mapping for the desired port. The ingress packets are first mapped to 802.1p priority, then to TC queues according to the 802.1p to queue mappings.
DSCP Remap(Optional) Select the DSCP priority to which the desired DSCP priority will be remapped for the port. When the switch detects the packets with desired DSCP value, it will modify the packets' DSCP value according to the map.

2) Click Apply.

For Certain Devices:

Choose the menu QoS > Class of Service >DSCP Priority to load the following page.

Figure 2-9 Configuring the DSCP to 802.1p Mapping and the DSCP Remap
TP-LINK Omada TL-SG2008P - For Certain Devices: - 1

text_image DSCP Priority Config DSCP Priority 802.1p Priority DSCP Remap 0 0 0 be (000000) 1 0 1 2 0 2 3 0 3 4 0 4 5 0 5 6 0 6 7 0 7 8 1 8 cs1 (001000) 9 1 9 Total: 64 1 entry selected. Cancel Apply

Follow these steps to configure the DSCP Priority:

1) In the DSCP Priority Config section, configure the DSCP to 802.1p mapping and the DSCP remap.

DSCP PriorityDisplays the number of DSCP priority. DSCP Priority is used to classify the packets based on the value of DSCP, and map them to different queues. ToS (Type of Service) is a part of IP header, and DSCP uses the first six bits of ToS to represent the priority of IP packets. The DSCP values range from 0 to 63.
802.1p PrioritySpecify the DSCP to 802.1p mapping. The ingress packets are first mapped to 802.1p priority based on the DSCP to 802.1p mappings, then to TC queues according to the 802.1p to queue mappings. The untagged IP packets with the desired DSCP value will be added an 802.1p priority value according to the DSCP to 802.1p mapping.
DSCP Remap(Optional) Select the DSCP priority to which the original DSCP priority will be remapped. When the switch detects the packets with desired DSCP value, it will modify the packets' DSCP value according to the map.

2) Click Apply.

TP-LINK Omada TL-SG2008P - 2) Click Apply. - 1

Note:

In Trust DSCP mode, non-IP packets will be added an 802.1p priority based on the port to 802.1p mapping and will be forwarded according to the 802.1p to queue mapping.

2.1.4 Specifying the Scheduler Settings

Specify the scheduler settings to control the forwarding sequence of different TC queues when congestion occurs.

For Certain Devices:

Choose the menu QoS > Class of Service > Scheduler Settings to load the following page.

Figure 2-10 Specifying the Scheduler Settings
TP-LINK Omada TL-SG2008P - For Certain Devices: - 1

other | Queue TC-id | Syncled Type | Taildrop | | ----------- | ------------ | -------- | | 0 | Weighted | 1 | | 1 | Weighted | 1 | | 2 | Weighted | 1 | | 3 | Weighted | 1 | | 4 | Weighted | 1 | | 5 | Weighted | 1 | | 6 | Weighted | 1 | | 7 | Weighted | 1 |

Follow these steps to configure the schedule mode:

1) In the Scheduler Config section, select the desired port.
2) Select the desired queue and configure the parameters.

Queue TC-id Displays the ID number of priority Queue.

Scheduler TypeSelect the type of scheduling used for corresponding queue. When the network congestion occurs, the egress queue will determine the forwarding sequence of the packets according to the type.Strict: In this mode, the egress queue will use SP (Strict Priority) to process the traffic in different queues. When congestion occurs, the traffic will be transmitted according to its queue priority strictly. The queue with higher priority occupies the whole bandwidth. Packets in the queue with lower priority are sent only when the queue with higher priority is empty.Weighted: In this mode, the egress queue will use WRR (Weighted Round Robin) to process the traffic in different queues. When congestion occurs, all the traffic will be transmitted, but the bandwidth that each traffic queue occupies will be allocated based on the queue weight.
Queue WeightSpecify the queue weight for the desired queue. This value can be set only in the Weighted mode. The valid values are from 1 to 127.
Minimum BandwidthSpecify the minimum guaranteed bandwidth for the desired queue. The valid values are from 0 to 100 and 0 means Minimum Bandwidth is disabled. If the queue bandwidth calculated according to the weight is smaller than the minimum bandwidth, the switch will be forced to allocated the minimum bandwidth to the queue, and the other queue will share the rest bandwidth based on the weight.Note: Minimum Bandwidth is only available on certain devices.
Management TypeDisplays the Management Type for the queues. The switch supports Taildrop mode. When the traffic exceeds the limit, the additional traffic will be dropped.

3) Click Apply.

For Certain Devices:

Choose the menu QoS > Class of Service > Scheduler Settings to load the following page.

Figure 2-11 Specifying the Scheduler Settings

Scheduler Config
Queue TC-idScheduler TypeQueue WeightManagement Type
0Weighted1Taildrop
1Weighted1Taildrop
2Weighted1Taildrop
3Weighted1Taildrop
4Weighted1Taildrop
5Weighted1Taildrop
6Weighted1Taildrop
7Weighted1Taildrop
Total: 8

Follow these steps to configure the schedule mode:

1) In the Scheduler Config section, select the desired queue and configure the parameters.

Queue TC-id Displays the ID number of priority Queue.
Scheduler TypeSelect the type of scheduling used for corresponding queue. When the network congestion occurs, the egress queue will determine the forwarding sequence of the packets according to the type.Strict: In this mode, the egress queue will use SP (Strict Priority) to process the traffic in different queues. When congestion occurs, the traffic will be transmitted according to its queue priority strictly. The queue with higher priority occupies the whole bandwidth. Packets in the queue with lower priority are sent only when the queue with higher priority is empty.Weighted: In this mode, the egress queue will use WRR (Weighted Round Robin) to process the traffic in different queues. When congestion occurs, all the traffic will be transmitted, but the bandwidth that each traffic queue occupies will be allocated based on the queue weight.
Queue WeightSpecify the queue weight for the desired queue. This value can be set only in the Weighted mode. The valid values are from 1 to 127.
Minimum BandwidthSpecify the minimum guaranteed bandwidth for the desired queue. The valid values are from 0 to 100 and 0 means Minimum Bandwidth is disabled. If the queue bandwidth calculated according to the weight is smaller than the minimum bandwidth, the switch will be forced to allocated the minimum bandwidth to the queue, and the other queue will share the rest bandwidth based on the weight.Note: Minimum Bandwidth is only available on certain devices.
Management TypeDisplays the Management Type for the queues. The switch supports Taildrop mode. When the traffic exceeds the limit, the additional traffic will be dropped.

2) Click Apply.

TP-LINK Omada TL-SG2008P - For Certain Devices: - 1

Note:

With ACL Redirect feature, the switch maps all the packets that meet the configured ACL rules to the new TC queue, regardless of the mapping relations configured in this section.

2.2 Using CLI

2.2.1 Configuring Port Priority

■ Configuring the Trust Mode and the port to 802.1p Mapping

Follow these steps to configure the trust mode and the port to 802.1p mapping:

Step 1 configureEnter global configuration mode
Step 2 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}Enter interface configuration mode.
Step 3 qos trust mode { untrust | dot1p | dscp}Select the trust mode for the port. By default, it is untrust. Here we set the trust mode as untrust.untrust: Specify the ports' trust mode as untrust. In this mode, the packets will be processed according to the port priority configuration.
Step 4 qos port-priority { dot1p-priority}Specify the port to 802.1p priority mapping for the desired port. The ingress packets from one port are first mapped to 802.1p priority based on the port to 802.1p mapping, then to TC queues based on the 802.1p to queue mapping. The untagged packets from one port will be added an 802.1p priority value according to the port to 802.1p mapping.dot1p-priority: Specify the 802.1p priority ranging from 0 to 7. The default value is 0.
Step 5 show qos trust interface [fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel port-channel-id]Verify the trust mode of the ports.
Step 6 show qos port-priority interface [fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel port-channel-id]Verify the port to 802.1p mappings.
Step 7 endReturn to privileged EXEC mode.
Step 8 copy running-config startup-configSave the settings in the configuration file.
■ Configuring the 802.1p to Queue MappingFollow these steps to configure the 802.1p to queue mapping:
Step 1 configureEnter global configuration mode

Step 2 qos cos-map { dot1p-priority } {tc-queue}

Specify the 802.1p to queue mapping. The packets with the desired 802.1p priority will be put in the corresponding queues. By default, the 802.1p priority 0 to 7 is respectively mapped to TC-1, TC-0, TC-2, TC-3, TC-4, TC-5, TC-6, TC-7.

dot1p-priority: Specify the 802.1p priority. The valid values are from 0 to 7.

tc-queue: Specify the ID number of the TC queue. The valid values are from 0 to 7.

Step 3 show qos cos-map

Verify the 802.1p to queue mappings.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to configure the trust mode of port 1/0/1 as untrust, map the port 1/0/1 to 802.1p priority 1 and map 802.1p priority 1 to TC3:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#qos trust mode untrust

Switch(config-if)#qos port-priority 1

Switch(config-if)#exit

Switch(config)#qos cos-map 1 3

Switch(config)#show qos trust interface gigabitEthernet 1/0/1

Port Trust Mode LAG

Gi1/0/1 untrust N/A

Switch(config)#show qos port-priority interface gigabitEthernet 1/0/1

Port CoS Value LAG

Gi1/0/1 CoS 1 N/A

Switch(config)#show qos cos-map

Dot1p Value |0 |1 |2 |3 |4 |5 |6 |7

TC |TC0 |TC3 |TC2 |TC3 |TC4 |TC5 |TC6 |TC7

Switch(config)#end

Switch#copy running-config startup-config

2.2.2 Configuring 802.1p Priority

■ Configuring the Trust Mode

Follow these steps to configure the trust mode:

Step 1 configure

Enter global configuration mode

Step 2 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}Enter interface configuration mode.
Step 3 qos trust mode { untrust | dot1p | dscp}Select the trust mode for the port. By default, it is untrust. Here we set the trust mode as dot1p.dot1p: Specify the ports' trust mode as dot1p. In this mode, the tagged packets will be processed according to the 802.1p priority configuration and the untagged packets will be processed according to the port priority configuration.
Step 4 show qos trust interface [fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel port-channel-id]Verify the trust mode of the ports.
Step 5 endReturn to privileged EXEC mode.
Step 6 copy running-config startup-configSave the settings in the configuration file.

■ Configuring the 802.1p to Queue Mapping and 802.1p Remap

Follow these steps to configure the 802.1p to queue mapping and 802.1p remap:

Step 1 configure

Enter global configuration mode

Step 2 qos cos-map { dot1p-priority } {tc-queue}

Specify the 802.1p to queue mapping. The packets with the desired 802.1p priority will be put in the corresponding queues. By default, the 802.1p priority 0 to 7 is respectively mapped to TC-1, TC-0, TC-2, TC-3, TC-4, TC-5, TC-6, TC-7.

dot1p-priority: Specify the 802.1p priority. The valid values are from 0 to 7.

tc-queue: Specify the ID number of the TC queue. The valid values are from 0 to 7.

Step 3 For Certain Devices:

interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}

Enter interface configuration mode.

qos dot1p-remap {dot1p-priority} {new-dot1p-priority}

(Optional) Specify the 802.1p to 802.1p mappings for the desired port. 802.1p Remap is used to modify the 802.1p priority of the ingress packets. When the switch detects the packets with desired 802.1p priority, it will modify the value of 802.1p priority according to the map. By default, the original 802.1p priority 0 is mapped to the 802.1p priority 0, the original 802.1p priority 1 is mapped to the 802.1p priority 1 and so on.

dot1p-priority: Specify the original 802.1p priority. The valid values are from 0 to 7.

new-dot1p-priority: Specify the new 802.1p priority. The valid values are from 0 to 7.

For Certain Devices:

qos dot1p-remap {dot1p-priority} {new-dot1p-priority}

(Optional) Specify the 802.1p to 802.1p mappings. 802.1p Remap is used to modify the 802.1p priority of the ingress packets. When the switch detects the packets with desired 802.1p priority, it will modify the value of 802.1p priority according to the map. By default, the original 802.1p priority 0 is mapped to the 802.1p priority 0, the original 802.1p priority 1 is mapped to the 802.1p priority 1 and so on.

dot1p-priority: Specify the original 802.1p priority. The valid values are from 0 to 7.

new-dot1p-priority: Specify the new 802.1p priority. The valid values are from 0 to 7.

Step 4 show qos cos-map

Verify the 802.1p to queue mappings.

Step 5 For Certain Devices:

show qos dot1p-remap interface [fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel port-channel-id]

Verify the 802.1p to 802.1p mappings of the ports.

For Certain Devices:

show qos dot1p-remap

Verify the 802.1p to 802.1p mappings globally.

Step 6 end

Return to privileged EXEC mode.

Step 7 copy running-config startup-config

Save the settings in the configuration file.

TP-LINK Omada TL-SG2008P - Step 7 copy running-config startup-config - 1

Note:

In Trust 802.1p mode, the untagged packets will be added an 802.1p priority based on the port to 802.1p mapping and will be forwarded according to the 802.1p to queue mapping.

The following example shows how to configure the trust mode of port 1/0/1 as dot1p, map 802.1p priority 3 to TC4, and configure to map the original 802.1p 1 to 802.1p priority 3:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#qos trust mode dot1p

Switch(config-if)#exit

Switch(config)#qos cos-map 3 4

Switch(config)#qos dot1p-remap 1 3

Switch(config)#show qos trust interface gigabitEthernet 1/0/1

PortTrust ModeLAG
------------
Gi1/0/1trust 802.1PN/A

Switch(config)#show qos cos-map

+---+---+---+---+---+---+---

Dot1p Value |0 |1 |2 |3 |4 |5 |6 |7

+---+---+---+---+---+---+---

TC |TC0 |TC1 |TC2 |TC4 |TC4 |TC5 |TC6 |TC7

+---+---+---+---+---+---+---+

Switch(config)#show qos dot1p-remap

Dot1p Value 0 1 2 3 4 5 6 7 LAG


Dot1p Remap 0 3 2 3 4 5 6 7 N/A

Switch(config)#end

Switch#copy running-config startup-config

2.2.3 Configuring DSCP Priority

■ Configuring the Trust Mode

Follow these steps to configure the trust mode:

Step 1 configureEnter global configuration mode
Step 2 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}Enter interface configuration mode.
Step 3 qos trust mode {untrust | dot1p | dscp}Select the trust mode for the port. By default, it is untrust. Here we set the trust mode as dscp.dscp: Specify the ports' trust mode as dscp. In this mode, the IP packets will be processed according to the DSCP priority configuration and the non-IP packets will be processed according to the port priority configuration.
Step 4 show qos trust interface [fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel port-channel-id]Verify the trust mode of the ports.
Step 5 endReturn to privileged EXEC mode.
Step 6 copy running-config startup-configSave the settings in the configuration file.

■ Configuring the 802.1p to Queue Mapping

Follow these steps to configure the 802.1p to queue mapping:

Step 1 configureEnter global configuration mode
Step 2 qos cos-map { dot1p-priority} {tc-queue}Specify the 802.1p to queue mapping. The packets with the desired 802.1p priority will be put in the corresponding queues. By default, the 802.1p priority 0 to 7 is respectively mapped to TC-1, TC-0, TC-2, TC-3, TC-4, TC-5, TC-6, TC-7.dot1p-priority: Specify the 802.1p priority. The valid values are from 0 to 7.tc-queue: Specify the ID number of the TC queue. The valid values are from 0 to 7.
Step 3 show qos cos-mapVerify the 802.1p to queue mappings.
Step 4 endReturn to privileged EXEC mode.
Step 5 copy running-config startup-configSave the settings in the configuration file.

■ Configuring the DSCP to 802.1p Mapping and DSCP Remp

Follow these steps to configure the DSCP to 802.1p mapping and DSCP remap:

Step 1 configure

Enter global configuration mode

Step 2 For Certain Devices:

interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}

Enter interface configuration mode.

qos dscp-map {dscp-value-list} {dot1p-priority}

Specify the DSCP to 802.1p mapping for the desired port. The ingress packets with the desired DSCP priority are first mapped to 802.1p priority based on the DSCP to 802.1p mapping, then to TC queues based on the 802.1p to queue mapping. By default, the DSCP priorities 0-7 are mapped to the 802.1p priority 0, the DSCP priorities 8-15 are mapped to the 802.1p priority 1 and so on.

dscp-value-list: Specify the DSCP value list in the format of "1-3,5,7". The valid values are from 0 to 63.

dot1p-priority: Specify the 802.1p priority. The valid values are from 0 to 7.

For Certain Devices:

qos dscp-map {dscp-value-list} {dot1p-priority}

Specify the DSCP to 802.1p mapping. The ingress packets with the desired DSCP priority are first mapped to 802.1p priority based on the DSCP to 802.1p mapping, then to TC queues based on the 802.1p to queue mapping. The untagged packets with the desired DSCP priority will be added an 802.1p priority value according to the DSCP to 802.1p mapping. by default, the DSCP priorities 0-7 are mapped to the 802.1p priority 0, the DSCP priorities 8-15 are mapped to the 802.1p priority 1 and so on.

dscp-value-list: Specify the DSCP value list in the format of "1-3,5,7". The valid values are from 0 to 63.

dot1p-priority: Specify the 802.1p priority. The valid values are from 0 to 7.

Step 3 qos dscp-remap { dscp-value-list } {dscp-remap-value}

(Optional) Specify the DSCP to DSCP mappings. DSCP Remap is used to modify the DSCP priority of the ingress packets. When the switch detects the packets with the desired DSCP priority, it will modify the value of DSCP priority according to the map. By default, the original DSCP priority 0 is mapped to the DSCP priority 0, the original DSCP priority 1 is mapped to the DSCP priority 1 and so on.

dscp-value-list: Specify the original DSCP priority list in the format of "1-3,5,7". The valid values are from 0 to 63.

dscp-remap-value: Specify the new DSCP priority. The valid values are from 0 to 63.

Step 4 For Certain Devices:

show qos dscp-map interface [fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel port-channel-id]

Verify the DSCP to queue mappings of ports.

For Certain Devices:

show qos dscp-map

Verify the DSCP to queue mappings globally.

Step 5 For Certain Devices:

show qos dscp-remap interface [fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel port-channel-id]

Verify the DSCP to DSCP mappings of the ports.

For Certain Devices:

show qos dscp-remap

Verify the DSCP to DSCP mappings globally.

Step 6 end

Return to privileged EXEC mode.

Step 7 copy running-config startup-config

Save the settings in the configuration file.

TP-LINK Omada TL-SG2008P - Step 3 qos dscp-remap { dscp-value-list } {dscp-remap-value} - 1

Note:

In Trust DSCP mode, non-IP packets will be added an 802.1p priority based on the port to 802.1p mapping and will be forwarded according to the 802.1p to queue mapping.

The following example shows how to configure the trust mode of port 1/0/1 as dscp, map 802.1p priority 3 to TC4, map DSCP priority 1-3,5,7 to 802.1p priority 3, and configure to map the original DSCP priority 9 to DSCP priority 5:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#qos trust mode dscp

Switch(config-if)#exit

Switch(config)#qos cos-map 3 4

Switch(config)#qos dscp-map 1-3,5,7 3

Switch(config)#qos dscp-remap 9 5

Switch(config)#show qos trust interface gigabitEthernet 1/0/1

PortTrust ModeLAG
------------
Gi1/0/1trust DSCPN/A

Switch(config)#show qos cos-map

Dot1p Value01234567
TC|TC0|TC1|TC2|TC4|TC4|TC5|TC6|TC7

Switch(config)#show qos dscp-map

DSCP:01234567
DSCP to 802.1P03330303
--------------------------------
DSCP:89101112131415
DSCP to 802.1P11111111
--------------------------------
DSCP:1617181920212223
DSCP to 802.1P22222222
--------------------------------
DSCP:2425262728293031
DSCP to 802.1P33333333
--------------------------------
DSCP:3233343536373839
DSCP to 802.1P44444444
--------------------------------
DSCP:4041424344454647
DSCP to 802.1P55555555
--------------------------------
DSCP:4849505152535455
DSCP to 802.1P66666666
--------------------------------
DSCP:5657585960616263
DSCP to 802.1P77777777
--------------------------------

Switch(config)#show qos dscp-remap

DSCP:01234567
DSCP remap value01234567
--------------------------------
DSCP:89101112131415
DSCP remap value85101112131415
--------------------------------
DSCP:1617181920212223
DSCP remap value1617181920212223
--------------------------------
DSCP:2425262728293031
DSCP remap value2425262728293031
--------------------------------
DSCP:3233343536373839
DSCP remap value3233343536373839
--------------------------------
DSCP:4041424344454647
DSCP remap value4041424344454647
--------------------------------
DSCP:4849505152535455
DSCP remap value4849505152535455
--------------------------------
DSCP:5657585960616263
DSCP remap value5657585960616263
--------------------------------

Switch(config-if)#end

Switch#copy running-config startup-config

2.2.4 Specifying the Scheduler Settings

Follow these steps to specify the scheduler settings to control the forwarding sequence of different TC queues when congestion occurs.

Step 1 configure

Enter global configuration mode.

Step 2 For Certain Devices:

interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}

Enter interface configuration mode.

qos queue tc-queue mode {sp | wrr} [weight weight]

Specify the type of scheduling used for corresponding queue. When the network congestion occurs, the egress queue will determine the forwarding sequence of the packets according to the type. By default, it is wrr mode and the all the queue weights are 1.

tc-queue: Specify the ID number of TC queue. The valid values are from 0 to 7.

sp: In sp mode, the egress queue will use SP (Strict Priority) to process the traffic in different queues. When congestion occurs, the traffic will be transmitted according to its queue priority strictly. The queue with higher priority occupies the whole bandwidth. Packets in the queue with lower priority are sent only when the queue with higher priority is empty.

wrr: In wrr mode, the egress queue will use WRR (Weighted Round Robin) to process the traffic in different queues. When congestion occurs, all the traffic will be transmitted, but the bandwidth that each traffic queue occupies will be allocated based on the queue weight.

weight: Specify the queue weight for the desired queue. This value can be set only in the wrr mode. The valid values are from 1 to 127.

For Certain Devices:

qos queue tc-queue mode {sp | wrr} [weight weight]

Specify the type of scheduling used for corresponding queue. When the network congestion occurs, the egress queue will determine the forwarding sequence of the packets according to the type. By default, it is wrr mode and the all the queue weights are 1.

tc-queue: Specify the ID number of TC queue. The valid values are from 0 to 7.

sp: In sp mode, the egress queue will use SP (Strict Priority) to process the traffic in different queues. When congestion occurs, the traffic will be transmitted according to its queue priority strictly. The queue with higher priority occupies the whole bandwidth. Packets in the queue with lower priority are sent only when the queue with higher priority is empty.

wrr: In wrr mode, the egress queue will use WRR (Weighted Round Robin) to process the traffic in different queues. When congestion occurs, all the traffic will be transmitted, but the bandwidth that each traffic queue occupies will be allocated based on the queue weight.

weight: Specify the queue weight for the desired queue. This value can be set only in the wrr mode. The valid values are from 1 to 127.

Step 3 qos queue tc-queue bandwidth rate

Specify the minimum guaranteed bandwidth for the desired queue. If the queue bandwidth calculated according to the weight is smaller than the minimum bandwidth, the switch will be forced to allocated the minimum bandwidth to the queue, and the other queue will share the rest bandwidth based on the weight.

tc-queue: Specify the ID number of the TC queue. The valid values are from 0 to 7.

rate: Specify the rate for the desired TC queue. The valid values are from 1 to 100. The default value is 0.

Note: Minimum Bandwidth is only available on certain devices.

Step 4 show qos queue interface [fastEthernet

port | port-channel port-channel-id]

Verify the scheduler settings..

port | gigabitEthernet port | ten-gigabitEthernet

Step 5 end

Return to privileged EXEC mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

TP-LINK Omada TL-SG2008P - For Certain Devices: - 1

Note:

With ACL Redirect feature, the switch maps all the packets that meet the configured ACL rules to the new TC queue, regardless of the mapping relations configured in this section.

The following example shows how to specify the scheduler settings for port 1/0/1. Set the scheduler mode of TC1 as sp mode, set the scheduler mode of TC4 as wrr mode and set the queue weight as 5.

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#qos queue 1 mode sp

Switch(config-if)#qos queue 4 mode wrr weight 5

Switch(config-if)#show qos queue interface gigabitEthernet 1/0/1

Gi1/0/1----LAG: N/A

Queue Schedule Mode Weight

TC0 WRR 1

TC1 Strict N/A

TC2 WRR 1

TC3 WRR 1

TC4WRR5
TC5WRR1
TC6WRR1
TC7WRR1

Switch(config-if)#end

Switch#copy running-config startup-config

3 Bandwidth Control Configuration

With bandwidth control configurations, you can:

■ Configure rate limit
■ Configure storm control

3.1 Using the GUI

3.1.1 Configuring Rate Limit

Choose the menu QoS > Bandwidth Control > Rate Limit to load the following page.

Figure 3-1 Configuring Rate Limit
TP-LINK Omada TL-SG2008P - Configuring Rate Limit - 1

text_image Rate Limit Config UNIT1 LAGS Port Ingress Rate (0-1,000,000Kbps) Egress Rate (0-1,000,000Kbps) LAG ✓ 1/0/1 0 0 --- □ 1/0/2 0 0 --- □ 1/0/3 0 0 --- □ 1/0/4 0 0 --- □ 1/0/5 0 0 --- □ 1/0/6 0 0 --- □ 1/0/7 0 0 --- □ 1/0/8 0 0 --- □ 1/0/9 0 0 --- □ 1/0/10 0 0 --- Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure the Rate Limit function:

1) Select the desired port and configure the upper rate limit to receive and send packets.

Ingress Rate (0-1,000,000Kbps)

Specify the upper rate limit for receiving packets on the port.

The rate ranges from 1 to 1000000 kbps for the gigaport and 1 to 100000 kbps for the fast port, and is rounded off to the nearest multiple of 64.0 means the ingress rate limit is disabled.

Egress Rate (0-1,000,000Kbps)

Specify the upper rate limit for sending packets on the port.

The rate ranges from 1 to 1000000 kbps for the gigaport and 1 to 100000 kbps for the fast port, and is rounded off to the nearest multiple of 64.0 means the egress rate limit is disabled.

2) Click Apply.

3.1.2 Configuring Storm Control

Choose the menu QoS > Bandwidth Control > Storm Control to load the following page.

Figure 3-2 Configuring Storm Control
TP-LINK Omada TL-SG2008P - Configuring Storm Control - 1

text_image Storm Control Config UNIT1 LAGS Recover Port Rate Mode Broadcast Threshold (0- 1,000,000) Multicast Threshold (0- 1,000,000) UL-Frame Threshold (0- 1,000,000) Action Recover Time LAG kbps ✓ 1/0/1-kbps 0 0 0 Drop 0 --- 1/0/2-kbps 0 0 0 Drop 0 --- 1/0/3-kbps 0 0 0 Drop 0 --- 1/0/4-kbps 0 0 0 Drop 0 --- 1/0/5-kbps 0 0 0 Drop 0 --- 1/0/6-kbps 0 0 0 Drop 0 --- 1/0/7-kbps 0 0 0 Drop 0 --- 1/0/8-kbps 0 0 0 Drop 0 --- 1/0/9-kbps 0 0 0 Drop 0 --- 1/0/10-kbps 0 0 0 Drop 0 --- Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure the Storm Control function:

1) Select the desired port and configure the upper rate limit for forwarding broadcast packets, multicast packets and UL-frames (Unknown unicast frames).

Rate Mode

Specify the Rate Mode for the broadcast threshold, multicast threshold and UL-Frame threshold on the desired port.

kbps: The switch will limit the maximum speed of the specific kinds of traffic in kilo-bits per second.

ratio: The switch will limit the percentage of bandwidth utilization for specific kinds of traffic.

pps: The switch will limit the maximum number of packets per second for specific kinds of traffic.

Note: pps is only available on certain devices.

Broadcast Threshold (0-1,000,000)Specify the upper rate limit for receiving broadcast packets.The valid values differ among different rate modes. For kbps, the rate ranges from 1 to 1000000 kbps, and is rounded off to the nearest multiple of 64. For ratio, the rate ranges from 1 to 100 percent. For pps, the rate ranges from 1 to 1488000 packets per second. The value 0 means the broadcast threshold is disabled.The broadcast traffic exceeding the limit will be processed according to the Action configurations.
Multicast Threshold (0-1,000,000)Specify the upper rate limit for receiving multicast packets.The valid values differ among different rate modes. For kbps, the rate ranges from 1 to 1000000 kbps, and is rounded off to the nearest multiple of 64. For ratio, the rate ranges from 1 to 100 percent. For pps, the rate ranges from 1 to 1488000 packets per second. The value 0 means the multicast threshold is disabled.The multicast traffic exceeding the limit will be processed according to the Action configurations.
UL-Frame Threshold (0-1,000,000)Specify the upper rate limit for receiving unknown unicast frames.The valid values differ among different rate modes. For kbps, the rate ranges from 1 to 1000000 kbps, and is rounded off to the nearest multiple of 64. For ratio, the rate ranges from 1 to 100 percent. For pps, the rate ranges from 1 to 1488000 packets per second. The value 0 means the unknown unicast threshold is disabled.The traffic exceeding the limit will be processed according to the Action configurations.
Action Select the action that the switch will take when the traffic exceeds its corresponding limit.Drop:Set the Action as Drop. The port will drop the subsequent packets when the traffic exceeds the limit.Shutdown:Set the Action as Shutdown. The port will be shutdown when the traffic exceeds the limit.
Recover TimeSpecify the recover time for the port. It takes effect only when the action is set as shutdown. The valid values are from 0 to 3600 seconds. When the port is shutdown, it can recover to its normal state after the recover time passed. If the recover time is specified as 0, which means the port will not recover to its normal state automatically and you can recover the port manually.

2) Click Apply.

TP-LINK Omada TL-SG2008P - 2) Click Apply. - 1

Note:

The member port of an LAG (Link Aggregation Group) follows the configuration of the LAG and not its own. The configurations of the port can take effect only after it leaves the LAG.

3.2 Using the CLI

3.2.1 Configuring Rate Limit

Follow these steps to configure the upper rate limit for the port to receive and send packets:

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}

Enter interface configuration mode.

Step 3 bandwidth {ingress ingress-rate | egress egress-rate}

Configure the upper rate limit for the port to receive and send packets.

ingress-rate: Specify the upper rate limit for receiving packets on the port. The rate ranges from 1 to 1000000 kbps for the gigaport and 1 to 100000 kbps for the fast port, and is rounded off to the nearest multiple of 64.

egress-rate: Specify the upper rate limit for sending packets on the port. The rate ranges from 1 to 1000000 kbps for the gigaport and 1 to 100000 kbps for the fast port, and is rounded off to the nearest multiple of 64.

Step 4 show bandwidth interface [fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel port-channel-id]

Verify the ingress/egress rate limit for forwarding packets on the port or LAG. If no port or LAG is specified, it displays the upper ingress/egress rate limit for all ports or LAGs.

Step 5 end

Return to privileged EXEC mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to configure the ingress-rate as 5120 Kbps and egress-rate as 1024 Kbps for port 1/0/5:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/5

Switch(config-if)#bandwidth ingress 5120 egress 1024

Switch(config-if)#show bandwidth interface gigabitEthernet 1/0/5

Port IngressRate(Kbps) EgressRate(Kbps) LAG

Gi1/0/5

5120

1024

N/A

Switch(config-if)#end

Switch#copy running-config startup-config

3.2.2 Configuring Storm Control

Follow these steps to configure the upper rate limit on the port for forwarding broadcast packets, multicast packets and unknown unicast frames:

Step 1 configure

Enter global configuration mode

Step 2 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}

Enter interface configuration mode.

Step 3 storm-control rate-mode {kbps | ratio | pps}

Specify the Rate Mode for the broadcast threshold, multicast threshold and UL-Frame threshold on the desired port.

kbps: The switch will limit the maximum speed of the specific kinds of traffic in kilo-bits per second.

ratio: The switch will limit the percentage of bandwidth utilization for specific kinds of traffic.

pps: The switch will limit the maximum number of packets per second for specific kinds of traffic.

Note: pps is only available on certain devices.

Step 4 storm-control broadcast rate

Specify the upper rate limit for receiving broadcast packets. The broadcast traffic exceeding the limit will be processed according to the Action configurations.

rate: Specify the upper rate limit for receiving broadcast packets. The valid values differ among different rate modes. For kbps, the rate ranges from 1 to 1000000 kbps, and is rounded off to the nearest multiple of 64. For ratio, the rate ranges from 1 to 100 percent. For pps, the rate ranges from 1 to 1488000 packets per second.

Step 5 storm-control multicast rate

Specify the upper rate limit for receiving multicast packets. The multicast traffic exceeding the limit will be processed according to the Action configurations.

rate: Specify the upper rate limit for receiving multicast packets. The valid values differ among different rate modes. For kbps, the rate ranges from 1 to 1000000 kbps, and is rounded off to the nearest multiple of 64. For ratio, the rate ranges from 1 to 100 percent. For pps, the rate ranges from 1 to 1488000 packets per second.

Step6 storm-control unicast rate
Specify the upper rate limit for receiving unknown unicast frames. The traffic exceeding the limit will be processed according to the Action configurations.
rate: Specify the upper rate limit for receiving unknown unicast frames. The valid values differ among different rate modes. For kbps, the rate ranges from 1 to 1000000 kbps, and is rounded off to the nearest multiple of 64. For ratio, the rate ranges from 1 to 100 percent. For pps, the rate ranges from 1 to 1488000 packets per second.
Step 7storm-control exceed {drop | shutdown} [recover-time time]
Specify the action and the recover time. The switch will perform the action when the traffic exceeds its corresponding limit. By default, it is drop.
drop: Set the Action as Drop. The port will drop the subsequent packets when the traffic exceeds the limit.
shutdown: Set the Action as Shutdown. The port will be shutdown when the traffic exceeds the limit.
time: Specify the recover time for the port. It takes effect only when the action is set as shutdown. The valid values are from 0 to 3600 and the default value is 0. When the port is shutdown, it can recover to its normal state after the recover time passed. If the recover time is specified as 0, which means the port will not recover to its normal state automatically and you can recover the port manually.
Step 8 storm-control recover(Optional) Recover the port manually. When the recover time is specified as 0, the port will not recover to its normal state automatically. In this condition, you need to use this command to recover the port manually.
Step 9 show storm-control interface [fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel port-channel-id]Verify the storm control configurations of the port or LAG. If no port or LAG is specified, it displays the storm control configuration for all ports or LAGs.
Step 10 endReturn to privileged EXEC mode.
Step 11 copy running-config startup-configSave the settings in the configuration file.

The following example shows how to configure the upper rate limit of broadcast packets as 1024 kbps, Specify the action as shutdown and set the recover time as 10 for port 1/0/5:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/5

Switch(config-if)#storm-control rate-mode kbps

Switch(config-if)#storm-control broadcast 1024

Switch(config-if)#storm-control exceed shutdown recover-time 10

Switch(config-if)#show storm-control interface gigabitEthernet 1/0/5

PortRate ModeBcRateMcRateUIRateExceedRecover TimeLAG
Gi1/0/5kbps102400shutdown10N/A

Switch(config-if)#end

Switch#copy running-config startup-config

4 Voice VLAN Configuration

To complete the voice VLAN configurations, follow these steps:

1) Create a 802.1Q VLAN
2) Configure OUI addresses
3) Configure Voice VLAN globally
4) Add ports to Voice VLAN

Configuration Guidelines

■ Before configuring voice VLAN, you need to create a 802.1Q VLAN for voice traffic. For details about 802.1Q VLAN Configuration, please refer to Configuring 802.1Q VLAN.
■ VLAN 1 is a default VLAN and cannot be configured as the voice VLAN.
■ Only one VLAN can be set as the voice VLAN on the switch.

4.1 Using the GUI

4.1.1 Configuring OUI Addresses

The OUI address is assigned as a unique identifier by IEEE (Institute of Electrical and Electronics Engineers) to a device vendor. It is used by the switch to determine whether a packet is a voice packet.

If the OUI address of your voice device is not in the OUI table, you need to add the OUI address to the table.

Choose the menu QoS > Voice VLAN > OUI Config to load the following page.

Figure 4-1 Configuring OUI Addresses
TP-LINK Omada TL-SG2008P - Configuring OUI Addresses - 1

text_image OUI Config UNIT1 OUI Status Description 00:01:E3 Default SIEMENS 00:03:6B Default CISCO1 00:12:43 Default CISCO2 00:0F:E2 Default H3C 00:60:B9 Default NITSUKO 00:D0:1E Default PINTEL 00:E0:75 Default VERILINK 00:E0:BB Default 3COM 00:04:0D Default AVAYA1 00:18:4F Default AVAYA2 Total: 11

Follow these steps to configure the OUI addresses:

1) Click to load the following page.

Figure 4-2 Creating an OUI Entry
TP-LINK Omada TL-SG2008P - Configuring OUI Addresses - 2

text_image OUI OUI: (Format: 00:00:00) Description: (1-16 characters) Cancel Create

2) Specify the OUI and the Description.

OUI Enter the OUI address of your voice devices. The OUI address is used by the switch to determine whether a packet is a voice packet. An OUI address is the first 24 bits of a MAC address, and is assigned as a unique identifier by IEEE (Institute of Electrical and Electronics Engineers) to a device vendor. If the source MAC address of a packet matches the OUI addresses in the OUI list, the switch identifies the packet as a voice packet and prioritizes it in transmission.

Description Give an OUI address description for identification.

3) Click Create.

4.1.1 Configuring Voice VLAN Globally

Choose the menu QoS > Voice VLAN > Global Config to load the following page.

Figure 4-3 Configuring Voice VLAN Globally
TP-LINK Omada TL-SG2008P - Configuring Voice VLAN Globally - 1

text_image Global Config Voice VLAN: Enable VLAN ID: 0 (2-4094) Priority: 7 Apply

Follow these steps to configure voice VLAN globally:

1) Enable the voice VLAN feature and specify the parameters.

VLAN ID Specify the 802.1Q VLAN ID to set the 802.1Q VLAN as the voice VLAN.

Priority

Select the priority that will be assigned to voice packets. A bigger value means a higher priority. This is an IEEE 802.1p priority, and you can further configure its scheduler mode in Class of Service if needed.

2) Click Apply.

4.1.1 Adding Ports to Voice VLAN

Choose the menu QoS > Voice VLAN > Port Config to load the following page.

Figure 4-4 Adding Ports to Voice VLAN
TP-LINK Omada TL-SG2008P - Adding Ports to Voice VLAN - 1

text_image Port Config UNIT1 LAGS Port Voice VLAN Operational Status ✓ 1/0/1 Disabled Inactive □ 1/0/2 Disabled Inactive □ 1/0/3 Disabled Inactive □ 1/0/4 Disabled Inactive □ 1/0/5 Disabled Inactive □ 1/0/6 Disabled Inactive □ 1/0/7 Disabled Inactive □ 1/0/8 Disabled Inactive □ 1/0/9 Disabled Inactive □ 1/0/10 Disabled Inactive Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure voice VLAN globally:

1) Select the desired ports and choose Enable in Voice VLAN filed.

Voice VLAN Select Enable to enable the voice VLAN feature on ports and add the desired ports to Voice VLAN.

Optional Status Displays the state of the Voice VLAN on the corresponding port.

Active: Indicates that Voive VLAN function is enabled on the port.

Inactive: Indicates that Voive VLAN function is disabled on the port.

2) Click Apply.

4.2 Using the CLI

Follow these steps to configure voice VLAN:

Step 1 configure

Enter global configuration mode.

Step 2 show voice vlan oui-table

Check whether the OUI address of your voice device is in the OUI table.

The OUI address is used by the switch to determine whether a packet is a voice packet. An OUI address is the first 24 bits of a MAC address, and is assigned as a unique identifier by IEEE (Institute of Electrical and Electronics Engineers) to a device vendor. If the source MAC address of a packet matches the OUI addresses in the OUI list, the switch identifies the packet as a voice packet and prioritizes it in transmission.

Step 3 voice vlan oui oui-prefix oui-desc string

If the OUI address of your voice device is not in the OUI table, add the OUI address to the table.

oui-prefix: Enter the OUI address for your voice device in the format of XX:XX:XX.

string: Give an OUI address description for identification. It contains 16 characters at most.

Enable the voice VLAN feature and specify an existing 802.1Q VLAN as the voice VLAN.

vid: Enter the 802.1Q VLAN ID to set the 802.1Q VLAN as the voice VLAN.

Step 5 voice vlan priority pri

Specify the priority that will be assigned to voice packets.

pri: Enter the priority that will be assigned to voice packets. A bigger value means a higher priority. The valid values are from 0 to 7 and the default value is 7. This is an IEEE 802.1p priority, and you can further configure its scheduler mode in Class of Service if needed.

Step 6 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}

Enter interface configuration mode.

Step 7 voice vlan

Enable the voice VLAN feature on ports and add the desired ports to voice VLAN.

Step 8 show voice vlan interface

Verify the voice VLAN configuration information.

Step 8 end

Return to privileged EXEC mode.

Step 9 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to show the OUI table, set VLAN 8 as voice VLAN, set the priority as 6 and enable voice VLAN feature on port 1/0/3:

Switch#configure

Switch(config)#show voice vlan oui-table

00:01:E3DefaultSIEMENS
00:03:6BDefaultCISCO1
00:12:43DefaultCISCO2
00:0F:E2DefaultH3C
00:60:B9DefaultNITSUKO
00:D0:1EDefaultPINTEL
00:E0:75DefaultVERILINK
00:E0:BBDefault3COM
00:04:0DDefaultAVAYA1
00:1B:4FDefaultAVAYA2
00:04:13DefaultSNOM

Switch(config)#voice vlan 8

Switch(config)#voice vlan priority 6

Switch(config)#interface gigabitEthernet 1/0/3

Switch(config-if)#voice vlan

Switch(config-if)#show voice vlan interface

Voice VLAN ID8
Priority6
InterfaceVoice VLAN ModeOperational StatusLAG
---------------
Gi1/0/1disabledDownN/A
Gi1/0/2disabledDownN/A

Gi1/0/3 enabled Up N/A

Gi1/0/4 disabled Down N/A

Gi1/0/5 disabled Down N/A

...

Switch(config-if)#end

Switch#copy running-config startup-config

5 Auto VoIP Configuration

Configuration Guidelines

■ Before configuring Auto VoIP, you need to enable LLDP-MED on ports and configure the relevant parameters. For details about LLDP-MED configuration, please refer to Configuring LLDP.
■ Auto VoIP provide flexible solutions for optimizing the voice traffic. It can work with other features such as VLAN and Class of Service to process the voice packets with specific fields. You can choose and configure Auto VoIP and other features according to your needs.

5.1 Using the GUI

Choose the menu QoS > Auto VoIP to load the following page.

Figure 5-1 Configuring Auto VoIP
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Global Config Auto VoIP: Enable Apply Port Config UNIT1 Port Interface Mode Value CoS Override Mode Operational Status DSCP Value ✓ 1/0/1 Disable 0 Disabled Disabled 0 □ 1/0/2 Disable 0 Disabled Disabled 0 □ 1/0/3 Disable 0 Disabled Disabled 0 □ 1/0/4 Disable 0 Disabled Disabled 0 □ 1/0/5 Disable 0 Disabled Disabled 0 □ 1/0/6 Disable 0 Disabled Disabled 0 □ 1/0/7 Disable 0 Disabled Disabled 0 □ 1/0/8 Disable 0 Disabled Disabled 0 □ 1/0/9 Disable 0 Disabled Disabled 0 □ 1/0/10 Disable 0 Disabled Disabled 0 Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure the OUI addresses:

1) In the Global Config section, enable the Auto VoIP function gloably.
2) In the Port Config section, select the desired and configure the parameters.

Interface Mode Select the interface mode for the port.

Disable: Disable the Auto VoIP function on the corresponding port.

None: Allow the voice devices to use its own configuration to send voice traffic.

VLAN ID: The voice devices will send voice packets with desired VLAN tag. If this mode is selected, it is necessary to specify the VLAN ID in the Value field.

In addition, you need to configure the 802.1Q VLAN to ensure the corresponding ports can forward the packets normally.

Dot1p: The voice devices will send voice packets with desired 802.1p priority. If this mode is selected, it is necessary to specify 802.1p priority in the Value field.

In addition, you can configure the Class of Service to make the switch process the packets according to the 802.1p priority.

Untagged: The voice devices will send untagged voice packets.

Value Enter the value of VLAN ID or 802.1p priority for the port according to the Interface Mode configurations.

CoS Override Enable or disable the Class of Service override mode. Mode

Enabled: Enable CoS override. The switch will ignore Class of Service settings and put the packets in TC-5 directly.

Disabled: Disable CoS override. The switch will then put the voice packets in the corresponding TC queue according to Class of Service settings.

Operational Status Displays the operating status of the Voice VLAN feature on the interface. To make it enabled, you must enable the Voice VLAN both globally and on the interface.

DSCP Value Enter the value of DSCP priority. The voice device will send the packets with the corresponding DSCP value.

In addition, you can configure the Class of Service to make the switch process the packets according to the DSCP priority.

3) Click Apply.

5.2 Using the CLI

Follow these steps to configure Auto VoIP:

Step 1 configure

Enter global configuration mode.

Step 2 auto-voip

Enable Auto VoIP globally.

Step 3 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | port-channel port-channel-id | range port-channel port-channel-list}

Enter interface configuration mode.

Step 4 Select the interface mode for the port.

no auto-voip

Specify the interface mode as disabled, which means the Auto VoIP function is disabled on the corresponding port.

auto-voip none

Specify the interface mode as none. In this mode, the switch allows the voice devices to use its own configuration to send voice traffic.

auto-voip vlan-id

Specify the interface mode as VLAN ID. In this mode, the voice devices will send voice packets with desired VLAN tag. If this mode is selected, it is necessary to specify the 802.1Q VLAN ID. The valid values are from 1 to 4093.

In addition, you need to configure the 802.1Q VLAN to ensure the corresponding ports can forward the packets normally.

auto-voip dot1p dot1p

Specify the interface mode as dot1p. In this mode, the voice devices will send voice packets with desired 802.1p priority. If this mode is selected, it is necessary to specify 802.1p priority. The valid values are from 0 to 7.

In addition, you can configure the Class of Service to make the switch process the packets according to the 802.1p priority.

auto-voip untagged

Specify the interface mode as untagged. In this mode, the voice devices will send untagged voice packets.

Step 5 auto-voip data priority {trust | untrust}

Enable or disable the Class of Service override mode. By default, it is trust, which means the Class of Service override mode is disabled.

trust: In this mode, The switch will then put the voice packets in the corresponding TC queue according to Class of Service settings.

untrust: In this mode, The switch will ignore Class of Service settings and put the packets in TC-5 directly.

Step 6 auto-voip dscp value

Specify the value of DSCP priority. The voice device will send the packets with the corresponding DSCP value.

In addition, you can configure the Class of Service to make the switch process the packets according to the DSCP priority.

value: Enter the value of DSCP priority. The valid values are from 0 to 63 and the default value is 0.

Step 7 show auto-voip

Verify the global state of Auto VoIP.

Step 8 show auto-voip interface

Verify the Auto VoIP configuration information of ports.

Step 8 end

Return to privileged EXEC mode.

Step 9 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to set the interface mode as dot1p, specify the 802.1p priority as 4, specify the DSCP priority as 10 and enable the CoS override mode for port 1/0/3:

Switch#configure

Switch(config)#auto-voip

Switch(config)#interface gigabitEthernet 1/0/3

Switch(config-if)#auto-voip dot1p 4

Switch(config-if)#auto-voip dscp 10

Switch(config-if)#auto-voip data priority untrust

Switch(config-if)#show auto-voip

Administrative Mode: Enabled

Switch(config-if)#show auto-voip interface

Interface.Gi1/0/1

Auto-VolP Interface Mode. Disabled

Auto-VoIP COS Override. False

Auto-VoIP DSCP Value. 0

Auto-VolP Port Status. Disabled

Interface.Gi1/0/2

Auto-VolP Interface Mode. Disabled

Auto-VoIP COS Override. False

Auto-VoIP DSCP Value. 0

Auto-VolP Port Status. Disabled

Interface.Gi1/0/3

Auto-VolP Interface Mode. Enabled

Auto-VoIP Priority. 4

Auto-VoIP COS Override. True

Auto-VoIP DSCP Value. 10

Auto-VoIP Port Status. Enabled

...

Switch(config-if)#end

Switch#copy running-config startup-config

6 Configuration Examples

6.1 Example for Class of Service

6.1.1 Network Requirements

As shown below, both RD department and Marketing department can access the internet. When congestion occurs, the traffic from two departments can both be forwarded and the traffic from the Marketing department should take precedence.

Figure 6-1 QoS Application Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["Internet"] --> B["Router"]
    B --> C["Switch A"]
    C --> D["RD Dept. Marketing Dept."]
    C --> E["Gi1/0/1"]
    C --> F["Gi1/0/2"]
    C --> G["Gi1/0/3"]

6.1.2 Configuration Scheme

To implement this requirement, you can configure Port Priority to put the packets from the Marketing department into the queue with the higher priority than the packets from the RD department.

1) Configure the trust mode of port 1/0/1 and port 1/0/2 as untrusted and map the ports to different queues.

2) Set the scheduler type of the queues as weighted for port 1/0/3 and specify the queue weight to make the traffic from the Marketing department take precedence.

Demonstrated with T1600G-28TS, the following sections provide configuration procedure in two ways: using the GUI and using the CLI.

6.1.3 Using the GUI

1) Choose the menu QoS > Class of Service > Port Priority to load the following page. Set the trust mode of port 1/0/1 and 1/0/2 as untrusted. Specify the 802.1p priority of port 1/0/1 as 1 and specify the 802.1p priority of port 1/0/2 as 0. Click Apply.

Figure 6-2 Configuring Port Priority
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Port Priority Config UNIT1 LAGS Port 802.1p Priority Trust Mode LAG 1 Untrusted ✓ 1/0/1 1 Untrusted -- 1/0/2 0 Untrusted -- 1/0/3 0 Untrusted -- 1/0/4 0 Untrusted -- 1/0/5 0 Untrusted -- 1/0/6 0 Untrusted -- 1/0/7 0 Untrusted -- 1/0/8 0 Untrusted -- 1/0/9 0 Untrusted -- 1/0/10 0 Untrusted -- Total: 28 1 entry selected. Cancel Apply

2) Choose the menu QoS > Class of Service > 802.1p Priority to load the following page. Map the 802.1p priority 0 to TC-1 and map the 802.1p priority 1 to TC-0. Click Apply.

Figure 6-3 Configuring the 802.1p to Queue Mappings
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image 802.1p to Queue Mapping 802.1p Priority Queue 0: TC-1 1: TC-0 2: TC-2 3: TC-3 4: TC-4 5: TC-5 6: TC-6 7: TC-7 802.1p Remap 802.1p Priority Remap 0: 0 1: 1 2: 2 3: 3 4: 4 5: 5 6: 6 7: 7 Apply Apply

3) Choose the menu QoS > Class of Service > Scheduler Settings to load the following page. Select the port 1/0/3 and set the scheduler type of TC-0 and TC-1 as Weighted. Specify the queue weight of TC-0 as 1 and specify the queue weight of TC-1 as 5. Click Apply.

Figure 6-4 Configuring the Egress Queue
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image Scheduler Config UNIT1 LAGS 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Port 1/0/3 Queue TC-Id Scheduler Type Queue Weight Management Type Weighted 5 0 Weighted 1 Taildrop ✓ 1 Weighted 5 Taildrop 2 Weighted 1 Taildrop 3 Weighted 1 Taildrop 4 Weighted 1 Taildrop 5 Weighted 1 Taildrop 6 Weighted 1 Taildrop 7 Weighted 1 Taildrop Total: 8 1 entry selected. Cancel Apply

4) Click Save the settings.

6.1.4 Using the CLI

1) Set the trust mode of port 1/0/1 as untrusted and specify the 802.1p priority as 1.

Switch_A#configure

Switch_A(config)#interface gigabitEthernet 1/0/1

Switch_A(config-if)#qos trust mode untrust

Switch_A(config-if)#qos port-priority 1

Switch_A(config-if)#exit

2) Set the trust mode of port 1/0/2 as untrusted and specify the 802.1p priority as 0.

Switch_A(config)#interface gigabitEthernet 1/0/2

Switch_A(config-if)#qos trust mode untrust

Switch_A(config-if)#qos port-priority 0

Switch_A(config-if)#exit

3) Map the 802.1p priority 0 to TC-1 and map the 802.1p priority 1 to TC-0.

Switch_A(config)#qos cos-map 0 1

Switch_A(config)#qos cos-map 10

4) Set the scheduler type of TC-0 and TC-1 as Weighted for egress port 1/0/3. Specify the queue weight of TC-0 as 1 and specify the queue weight of TC-1 as 5.

Switch_A(config)#interface gigabitEthernet 1/0/3

Switch_A(config-if)#qos queue 0 mode wrr weight 1

Switch_A(config-if)#qos queue 1 mode wrr weight 5

Switch_A(config-if)#end

Switch_A#copy running-config startup-config

Verify the configurations

Verify the trust mode of the port:

Switch_A#show qos trust interface

Port Trust Mode LAG


Gi1/0/1 untrust N/A

Gi1/0/2 untrust N/A

Gi1/0/3 untrust N/A

Gi1/0/4 untrust N/A

...

Verify the port to 802.1p mappings:

Switch_A#show qos port-priority interface

Port CoS Value LAG

Gi1/0/1 CoS 1 N/A

Gi1/0/2 CoS 0 N/A

Gi1/0/3 CoS 0 N/A

Gi1/0/4 CoS 0 N/A

...

Verify the 802.1p to queue mappings:

Switch_A#show qos cos-map
Dot1p Value01234567
TC|TC1|TC0|TC2|TC4|TC4|TC5|TC6|TC7

Verify the scheduler mode of the egress port:

Switch _A#show qos queue interface gigabitEthernet 1/0/3

Gi1/0/3----LAG: N/A

Queue Schedule Mode Weight

TC0WRR1
TC1WRR5
TC2WRR1
TC3WRR1
TC4WRR1
TC5WRR1
TC6WRR1
TC7WRR1

6.2 Example for Voice VLAN

6.2.1 Network Requirements

As shown below, the company plans to install IP phones in the office area. To ensure the good voice quality, IP phones and the computers will be connected to the different ports of the switch, and the voice traffic requires a higher priority than the data traffic.

Figure 6-5 Voice VLAN Application Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["Internet"] --> B["Switch B"]
    B --> C["Switch A"]
    C --> D["VLAN 2 VLAN 3"]
    C --> E["IP Phone 1 IP Phone 2"]
    C --> F["PC 3"]
    C --> G["Gi1/0/1"]
    C --> H["Gi1/0/2"]
    C --> I["Gi1/0/3"]
    B --> J["Switch B"]
    style B fill:#666,stroke:#333
    style C fill:#999,stroke:#333
    style D fill:#ccc,stroke:#333
    style E fill:#ccc,stroke:#333
    style F fill:#ccc,stroke:#333
    style G fill:#ccc,stroke:#333
    style H fill:#ccc,stroke:#333
    style I fill:#ccc,stroke:#333

6.2.2 Configuration Scheme

To implement this requirement, you can configure Voice VLAN to ensure that the voice traffic can be transmitted in the same VLAN and the data traffic is transmitted in another VLAN. In addition, specify the priority to make the voice traffic can take precedence when the congestion occurs.

1) Configure 802.1Q VLAN for port 1/0/1, port 1/0/2, port 1/0/3 and port 1/0/4.
2) Configure Voice VLAN feature on port 1/0/1 and port 1/0/2.

Demonstrated with T1600G-28TS, the following sections provide configuration procedure in two ways: using the GUI and using the CLI.

6.2.3 Using the GUI

1) Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > VLAN Config and click

TP-LINK Omada TL-SG2008P - Using the GUI - 1

Add

to load the following page. Create VLAN 2 and add untagged port 1/0/1, port

1/0/2 and port 1/0/4 to VLAN 2. Click Create.

Figure 6-6 Configuring VLAN 2
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image VLAN Config VLAN ID: 2 (2-4094, format: 2,4-5,8) VLAN Name: Voice_VLAN (1-16 characters) Untagged Ports Port: 1/0/1-2,1/0/4 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Tagged Ports Port: (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

2) Click to load the following page. Create VLAN 3 and add untagged port 1/0/3 and port 1/0/4 to VLAN 3. Click Create.

Figure 6-7 Configuring VLAN 3
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image VLAN Config VLAN ID: 3 (2-4094, format: 2,4-5,8) VLAN Name: VLAN3 (1-16 characters) Untagged Ports Port: 1/0/3-4 (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Tagged Ports Port: (Format: 1/0/1, input or choose below) UNIT1 LAGS Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

3) Choose the menu L2 FEATURES > VLAN > 802.1Q VLAN > Port Config to load the following page. Disable the Ingress Checking feature on port 1/0/1 and port 1/0/2 and specify the PVID as 2. Click Apply.

Figure 6-8 Specifying the Parameters of the Ports
TP-LINK Omada TL-SG2008P - Using the GUI - 4

text_image Port Config UNIT1 LAGS Port PVID Ingress Checking Acceptable Frame Types LAG Details 2 Disable ✓ 1/0/1 2 Disabled Admit All --- Details ✓ 1/0/2 2 Disabled Admit All --- Details □ 1/0/3 1 Enabled Admit All --- Details □ 1/0/4 1 Enabled Admit All --- Details □ 1/0/5 1 Enabled Admit All --- Details □ 1/0/6 1 Enabled Admit All --- Details □ 1/0/7 1 Enabled Admit All --- Details □ 1/0/8 1 Enabled Admit All --- Details □ 1/0/9 1 Enabled Admit All --- Details □ 1/0/10 1 Enabled Admit All --- Details Total: 28 2 entries selected. Cancel Apply

4) Choose the menu QoS > Voice VLAN > OUI Config to load the following page. Check the OUI table.

Figure 6-9 Checking the OUI Table
TP-LINK Omada TL-SG2008P - Using the GUI - 5

text_image OUI Config UNIT1 OUI Status Description 00:01:E3 Default SIEMENS 00:03:68 Default CISCO1 00:12:43 Default CISCO2 00:0F:E2 Default H3C 00:60:B9 Default NITSUKO 00:D0:1E Default PINTEL 00:E0:75 Default VERILINK 00:E0:BB Default 3COM 00:04:0D Default AVAYA1 00:1B:4F Default AVAYA2 Total: 11

5) Choose the menu QoS > Voice VLAN > Global Config to load the following page. Enable Voice VLAN globally. Specify the VLAN ID as 2 and set the priority as 7. Click Apply.

Figure 6-10 Configuring Voice VLAN Globally
TP-LINK Omada TL-SG2008P - Using the GUI - 6

text_image Global Config Voice VLAN: ✓ Enable VLAN ID: 2 (2-4094) Priority: 7 Apply

6) Choose the menu QoS > Voice VLAN > Port Config to load the following page. Enable Voice VLAN on port 1/0/1 and port 1/0/2. Click Apply.

Figure 6-11 Enabling Voice VLAN on Ports
TP-LINK Omada TL-SG2008P - Using the GUI - 7

text_image Port Config UNIT1 LAGS Port Voice VLAN Operational Status Enable ✓ 1/0/1 Enabled Inactive ✓ 1/0/2 Enabled Inactive □ 1/0/3 Disabled Inactive □ 1/0/4 Disabled Inactive □ 1/0/5 Disabled Inactive □ 1/0/6 Disabled Inactive □ 1/0/7 Disabled Inactive □ 1/0/8 Disabled Inactive □ 1/0/9 Disabled Inactive □ 1/0/10 Disabled Inactive Total: 28 2 entries selected. Cancel Apply

7) Click Save the settings.

6.2.4 Using the CLI

1) Create VLAN 2 and add untagged port 1/0/1, port 1/0/2 and port 1/0/4 to VLAN 2.

Switch_A#configure

Switch_A(config)#vlan 2

Switch_A(config-vlan)#name VoiceVLAN

Switch_A(config-vlan)#exit

Switch_A(config)#interface gigabitEthernet 1/0/1

Switch_A(config-if)#switchport general allowed vlan 2 untagged

Switch_A(config-if)#exit

Switch_A(config)#interface gigabitEthernet 1/0/2

Switch_A(config-if)#switchport general allowed vlan 2 untagged
Switch_A(config-if)#exit
Switch_A(config)#interface gigabitEthernet 1/0/4
Switch_A(config-if)#switchport general allowed vlan 2 untagged
Switch_A(config-if)#exit 

2) Create VLAN 3 and add untagged port 1/0/3 and port 1/0/4 to VLAN 3.

Switch_A(config)#vlan 3
Switch_A(config-vlan)#name VLAN3
Switch_A(config-vlan)#exit
Switch_A(config)#interface gigabitEthernet 1/0/3
Switch_A(config-if)#switchport general allowed vlan 3 untagged
Switch_A(config-if)#exit
Switch_A(config)#interface gigabitEthernet 1/0/4
Switch_A(config-if)#switchport general allowed vlan 3 untagged
Switch_A(config-if)#exit 

3) Disable the Ingress Checking feature on port 1/0/1 and port 1/0/2 and specify the PVID as 2.

Switch_A(config)#interface gigabitEthernet 1/0/1
Switch_A(config-if)#no switchport check ingress
Switch_A(config-if)#switchport pvid 2
Switch_A(config-if)#exit
Switch_A(config)#interface gigabitEthernet 1/0/2
Switch_A(config-if)#no switchport check ingress
Switch_A(config-if)#switchport pvid 2
Switch_A(config-if)#exit 

4) Check the OUI table.

Switch(config)#show voice vlan oui

00:01:E3 Default SIEMENS
00:03:6B Default CISCO1
00:12:43 Default CISCO2
00:0F:E2 Default H3C 
00:60:B9DefaultNITSUKO
00:D0:1EDefaultPINTEL
00:E0:75DefaultVERILINK
00:E0:BBDefault3COM
00:04:0DDefaultAVAYA1
00:1B:4FDefaultAVAYA2
00:04:13DefaultSNOM

5) Enable Voice VLAN globally. Specify the VLAN ID as 2 and set the priority as 7.

Switch_A(config)#voice vlan 2

Switch_A(config)#voice vlan priority 7

6) Enable Voice VLAN on port 1/0/1 and port 1/0/2.

Switch_A(config)#interface gigabitEthernet 1/0/1

Switch_A(config-if)#voice vlan

Switch_A(config-if)#exit

Switch_A(config)#interface gigabitEthernet 1/0/2

Switch_A(config-if)#voice vlan

Switch_A(config-if)#end

Switch_A#copy running-config startup-config

Verify the configurations

Verify the basic VLAN configuration:

Switch_A(config)#show vlan brief

VLAN Name Status Ports

Gi1/0/25, Gi1/0/26, Gi1/0/27, Gi1/0/28

6.3 Example for Auto VoIP

6.3.1 Network Requirements

As shown below, the company plans to install IP phones in the office area. IP phones share switch ports used by computers, because no more ports are available for IP phones. To ensure the good voice quality, the voice traffic requires a higher priority than the data traffic.

Figure 6-12 Auto VoIP Application Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["Internet"] --> B["Switch B"]
    B --> C["Switch A"]
    D["PC 10"] --> E["IP Phone 10"]
    F["..."] --> G["..."]
    E -->|Gi1/0/1| C
    C -->|Gi1/0/2| B

6.3.2 Configuration Scheme

To optimize voice traffic, configure Auto VoIP and LLDP-MED to instruct IP Phones to send traffic with desired DSCP priority. Voice traffic is put in the desired queue and data traffic is put in other queues according to the Class of Service configurations. Make sure that the voice traffic can take precedence when congestion occurs.

1) Enable the Auto VoIP feature and configure the DSCP value of ports.
2) Configure Class of Service.
3) Enable LLDP-MED and configure the corresponding parameters.

Demonstrated with T1600G-28TS, the following sections provide configuration procedure in two ways: using the GUI and using the CLI.

6.3.3 Using the GUI

Auto VoIP configurations for port1/0/1 and other ports connected to the IP phone are the same, the following configuration procedures take port 1/0/1 as example.

1) Choose the menu QoS > Auto VoIP to load the following page. Enable Auto VoIP globally and specify the DSCP value of port 1/0/1 as 63. Click Apply.

Figure 6-13 Configuring Auto VoIP
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Global Config Auto VoIP: ✓ Enable Apply Port Config UNIT1 Port Interface Mode Value CoS Override Mode Operational Status DSCP Value 63 ✓ 1/0/1 Disable 0 Disabled Disabled 63 □ 1/0/2 Disable 0 Disabled Disabled 0 □ 1/0/3 Disable 0 Disabled Disabled 0 □ 1/0/4 Disable 0 Disabled Disabled 0 □ 1/0/5 Disable 0 Disabled Disabled 0 □ 1/0/6 Disable 0 Disabled Disabled 0 □ 1/0/7 Disable 0 Disabled Disabled 0 □ 1/0/8 Disable 0 Disabled Disabled 0 □ 1/0/9 Disable 0 Disabled Disabled 0 □ 1/0/10 Disable 0 Disabled Disabled 0 Total: 28 1 entry selected. Cancel Apply

2) Choose the menu QoS > Class of Service > Port Priority to load the following page. Set the trust mode of port 1/0/1 as trust DSCP. Click Apply.

Figure 6-14 Configuring Port Priority
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image Port Priority Config UNIT1 LAGS Port 802.1p Priority Trust Mode LAG Trust DSCP ✓ 1/0/1 0 Trust DSCP -- □ 1/0/2 0 Untrusted -- □ 1/0/3 0 Untrusted -- □ 1/0/4 0 Untrusted -- □ 1/0/5 0 Untrusted -- □ 1/0/6 0 Untrusted -- □ 1/0/7 0 Untrusted -- □ 1/0/8 0 Untrusted -- □ 1/0/9 0 Untrusted -- □ 1/0/10 0 Untrusted -- Total: 28 1 entry selected. Cancel Apply

3) Choose the menu QoS > Class of Service > DSCP Priority to load the following page. Specify the 802.1p priority as 7 for DSCP priority 63. Click Apply.

Figure 6-15 Specifying the 802.1p priority for DSCP priority 63
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image DSCP Priority Config □ DSCP Priority 802.1p Priority DSCP Remap 7 □ 54 6 54 □ 55 6 55 □ 56 7 56 cs7 (111000) □ 57 7 57 □ 58 7 58 □ 59 7 59 □ 60 7 60 □ 61 7 61 □ 62 7 62 ✓ 63 7 63 Total 64 1 entry selected. Cancel Apply

4) Specify the 802.1p priority as 5 for other DSCP priorities. Click Apply.

Figure 6-16 Specifying the 802.1p priority for Other DSCP priorities
TP-LINK Omada TL-SG2008P - Using the GUI - 4

text_image DSCP Priority Config DSCP Priority 802.1p Priority DSCP Remap 5 ✓ 54 5 54 ✓ 55 5 55 ✓ 56 5 56 cs7 (111000) ✓ 57 5 57 ✓ 58 5 58 ✓ 59 5 59 ✓ 60 5 60 ✓ 61 5 61 ✓ 62 5 62 ✓ 63 7 63 Total: 64 63 entries selected. Cancel Apply

5) Choose the menu QoS > Class of Service > Scheduler Settings to load the following page. Select port 1/0/2. Set the scheduler mode as weighted and specify the queue weight as 1 for TC-5. Click Apply.

Figure 6-17 Configuring the TC-5 for the Port
TP-LINK Omada TL-SG2008P - Using the GUI - 5

text_image Scheduler Config UNIT1 LAGS 2 4 5 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Port 1/0/2 Queue TC-id Scheduler Type Queue Weight Management Type Weighted 1 0 Weighted 1 Taildrop 1 Weighted 1 Taildrop 2 Weighted 1 Taildrop 3 Weighted 1 Taildrop 4 Weighted 1 Taildrop 5 Weighted 1 Taildrop 6 Weighted 1 Taildrop 7 Weighted 1 Taildrop Total: 8 1 entry selected. Cancel Apply

6) Select port 1/0/2. Set the scheduler mode as weighted and specify the queue weight as 10 for TC-7. Click Apply.

Figure 6-18 Configuring the TC-7 for the Port
TP-LINK Omada TL-SG2008P - Using the GUI - 6

text_image Scheduler Config UNIT 1 LAGS 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Port 1/0/2 Queue TC-id Scheduler Type Queue Weight Management Type Weighted 10 0 Weighted 1 Taidrop 1 Weighted 1 Taidrop 2 Weighted 1 Taidrop 3 Weighted 1 Taidrop 4 Weighted 1 Taidrop 5 Weighted 1 Taidrop 6 Weighted 1 Taidrop 7 Weighted 10 Taidrop Total: 8 1 entry selected. Cancel Apply

7) Choose the menu L2 FEATURES > LLDP > LLDP-MED Config > Port Config click Detail to of port1/0/1 to load the following page. Check the boxes of all the TLVs. Click Save.

Figure 6-19 Configuring the TLVs
TP-LINK Omada TL-SG2008P - Using the GUI - 7

text_image Included TLVs Detail(Port:1/0/1) Included TLVs ✓ All ✓ Network Policy ✓ Location Identification ✓ Extended Power-Via-MDI ✓ Inventory Location Identification Parameters Emergency Number ✓ Civic Address What: Switch Country Code: CN China(Default) Language: Chars. (0-255) Province/State: Chars. (0-255) City/Township: Chars. (0-255) County/Parish/District: Chars. (0-255) Street: Chars. (0-255) House Number: Chars. (0-255) Name: Chars. (0-255) Postal/Zip Code: Chars. (0-255) Room Number: Chars. (0-255) Cancel Save

8) Choose the menu L2 FEATURES > LLDP > LLDP-MED Config > Port Config to load the following page. Enable LLDP-MED on port 1/0/1. Click Apply.

Figure 6-20 Enabling LLDP-MED on the Port
TP-LINK Omada TL-SG2008P - Using the GUI - 8

text_image Port Config UNIT1 Port LLDP-MED Status Included TLVs Enable ✓ 1/0/1 Enabled Detail □ 1/0/2 Disabled Detail □ 1/0/3 Disabled Detail □ 1/0/4 Disabled Detail □ 1/0/5 Disabled Detail □ 1/0/6 Disabled Detail □ 1/0/7 Disabled Detail □ 1/0/8 Disabled Detail □ 1/0/9 Disabled Detail □ 1/0/10 Disabled Detail Total: 28 1 entry selected. Cancel Apply

9) Click Save the settings.

6.3.4 Using the CLI

1) Enable Auto VoIP globally and specify the DSCP value of port 1/0/1 as 63.

Switch_A#configure

Switch_A(config)#auto-voip

Switch_A(config)#interface gigabitEthernet 1/0/1

Switch_A(config-if)#auto-voip dscp 63

Switch_A(config-if)#exit

2) Set the trust mode of port 1/0/1 as trust DSCP. Specify the 802.1p priority as 7 for DSCP priority 63 and specify 802.1p priority as 5 for other DSCP priorities.

Switch_A(config)#interface gigabitEthernet 1/0/1

Switch_A(config-if)#qos trust mode dscp

Switch_A(config-if)#exit

Switch_A(config)#qos dscp-map 63 7

Switch_A(config)#qos dscp-map 0-62 5

3) On port 1/0/1, set the scheduler mode as weighted and specify the queue weight as 1 for TC-5. Set the scheduler mode as weighted and specify the queue weight as 10 for TC-7.

Switch_A(config)#interface gigabitEthernet 1/0/1

Switch_A(config-if)#qos queue 5 mode wrr weight 1

Switch_A(config-if)#qos queue 7 mode wrr weight 10

Switch_A(config-if)#exit

4) Enable LLDP-MED on port 1/0/1 and select all the TLVs to be included in outgoing LLDPDU.

Switch_A(config)#interface gigabitEthernet 1/0/1

Switch_A(config-if)#lldp med-status

Switch_A(config-if)#lldp med-tlv-select all

Switch_A(config-if)#end

Switch_A#copy running-config startup-config

Verify the configurations

Verify the configuration of Auto VoIP:

Switch_A(config)#show auto-voip

Administrative Mode: Enabled

Verify the Auto VoIP configuration of ports:

Switch_A(config)#show auto-voip interface

Interface.Gi1/0/1

Auto-VolP Interface Mode. Disabled

Auto-VoIP COS Override. False

Auto-VoIP DSCP Value. 63

Auto-VoIP Port Status. Disabled

Interface.Gi1/0/2

Auto-VolP Interface Mode. Disabled

Auto-VoIP COS Override. False

Auto-VoIP DSCP Value. 0

Auto-VolP Port Status. Disabled

Interface.Gi1/0/3

Auto-VolP Interface Mode. Disabled

Auto-VoIP COS Override. False

Auto-VoIP DSCP Value. 0

Auto-VolP Port Status. Disabled

...

Verify the configuration of Class of Service:

Switch_A(config)#show qos trust interface gigabitEthernet 1/0/1

Port Trust Mode LAG

Gi1/0/1 trust DSCP N/A

Switch_A(config)#show qos cos-map

+---+---+---+---+---+---+---

Dot1p Value |0 |1 |2 |3 |4 |5 |6 |7

+ + + + + + + +

TC |TC1 |TC0 |TC2 |TC3 |TC4 |TC5 |TC6 |TC7

+---+---+---+---+---+---+---

Switch_A(config)#show qos dscp-map

DSCP: 0 1 2 3 4 5 6 7

DSCP to 802.1P 5 5 5 5 5 5 5 5

DSCP: 8 9 10 11 12 13 14 15

DSCP to 802.1P 5 5 5 5 5 5 5 5

DSCP: 16 17 18 19 20 21 22 23

DSCP to 802.1P 5 5 5 5 5 5 5 5

DSCP: 24 25 26 27 28 29 30 31

DSCP to 802.1P 5 5 5 5 5 5 5 5

DSCP: 32 33 34 35 36 37 38 39

DSCP to 802.1P 5 5 5 5 5 5 5 5

DSCP: 40 41 42 43 44 45 46 47

DSCP to 802.1P 5 5 5 5 5 5 5 5

DSCP: 48 49 50 51 52 53 54 55

DSCP to 802.1P 5 5 5 5 5 5 5 5

DSCP: 56 57 58 59 60 61 62 63

DSCP to 802.1P 5 5 5 5 5 5 5 7

Verify the configuration of LLDP-MED:

Switch_A(config)#show lldp interface

LLDP interface config:

gigabitEthernet 1/0/1:

Admin Status:TxRx
SNMP Trap:Disabled
TLVStatus
-------
Port-DescriptionYes
System-CapabilityYes
System-DescriptionYes
System-NameYes
Management-AddressYes
Port-VLAN-IDYes
Protocol-VLAN-IDYes
VLAN-NameYes
Link-AggregationYes
MAC-PhysicYes
Max-Frame-SizeYes
PowerYes
LLDP-MED Status:Enabled
TLVStatus
-------
Network PolicyYes

Location Identification Yes

Extended Power Via MDI Yes

Inventory Management Yes

...

7

Appendix: Default Parameters

Default settings of Class of Service are listed in the following tables.

Table 7-1 Default Settings of Port Priority Configuration

Parameter Default Setting
802.1P Priority 0
Trust Mode Untrusted

Table 7-2 Default Settings of 802.1p to Queue Mapping

802.1p Priority Queues (8)
0 TC1
1 TC0
2 TC2
3 TC3
4 TC4
5 TC5
6 TC6
7 TC7

Table 7-3 Default Settings of 802.1p Remap Configuration

Original 802.1pPriorityNew 802.1pPriority
00
11
22
33
44
55
66
77

Table 7-4 Default Settings of DSCP to 802.1p Mapping

DSCP 802.1p Priority
0 to 7 0
8 to 15 1
16 to 23 2
24 to 31 3
32 to 39 4
40 to 47 5
48 to 55 6
56 to 63 7

Table 7-5 Default Settings of DSCP Remap Configuration

Original DSCPNew DSCP Original DSCPNew DSCP Original DSCPNew DSCP
0 0 be (000000)22 22 af23 (010110)44 44
1 1 23 23 45 45
2 2 24 24 cs3 (011000)46 46 ef (101110)
3 3 25 25 47 47
4 4 26 26 af31 (011010)48 48 cs6 (110000)
5 5 27 27 49 49
6 6 28 28 af32 (011100)50 50
7 7 29 29 51 51
8 8 cs1 (001000)30 30 af33 (011110)52 52
9 9 31 31 53 53
10 10 af11 (001010)32 32 cs4 (100000)54 54
11 11 33 33 55 55
12 12 af12 (001100)34 34 af41 (100010)56 56 cs7 (111000)
13 13 35 35 57 57
14 14 af13 (001110)36 36 af42 (100100)58 58
15 15 37 37 59 59
16 16 cs2 (010000)38 38 af43 (100110)60 60
17 17 39 39 61 61
18 18 af21 (010010)40 40 cs5 (101000)62 62
19 19 41 41 63 63
20 20 af22 (010100)42 42
21 21 43 43

Table 7-6 Default Settings of Scheduler Settings Configuration

Parameter Default Setting
Scheduler Type Weighted
Queue Weight 1
Management TypeTaildrop

Default settings of Class of Service are listed in the following tables.

Table 7-7 Default Settings of Bandwidth Control

Parameter Default Setting
Ingress Rate (0-1,000,000Kbps)0
Egress Rate (0-1,000,000Kbps)0

Table 7-8 Default Settings of Storm Control

Parameter Default Setting
Rate Mode kbps
Broadcast Threshold (0-1,000,000)0
Multicast Threshold (0-1,000,000)0
UL-Frame Threshold (0-1,000,000)0
Action Drop
Recover Time 0

Default settings of Voice VLAN are listed in the following tables.

Table 7-9 Default Settings of Global Configuration

Parameter Default Setting
Voice VLAN Disabled
VLAN ID None
Priority 7

Table 7-10 Default Settings of Port Configuration

Parameter Default Setting
Voice VLAN Disabled

Table 7-11 Default Settings of OUI Table

OUI Status Description
00:01:E3 Default SIEMENS
00:03:6B Default CISCO1
00:12:43 Default CISCO2
00:0F:E2 Default H3C
00:60:B9 Default NITSUKO
00:D0:1E Default PINTEL
00:E0:75 Default VERILINK
00:E0:BB Default 3COM
00:04:0D Default AVAYA1
00:1B:4F Default AVAYA2
00:04:13 Default SNOM

Default settings of Auto VoIP are listed in the following tables.

Table 7-12 Default Settings of Auto VoIP

Parameter Default Setting
Interface ModeDisabled
ValueNone
Cos Override ModeDisabled
DSCP Value0

Part 23

Configuring Access Security

CHAPTERS

  1. Access Security
  2. Access Security Configurations
  3. Appendix: Default Parameters

1 Access Security

1.1 Overview

Access Security provides different security measures for accessing the switch remotely so as to enhance the configuration management security.

1.2 Supported Features

Access Control

This function is used to control the users' access to the switch based on IP address, MAC address or port.

HTTP

This function is based on the HTTP protocol. It can allow or deny users to access the switch via a web browser.

HTTPS

This function is based on the SSL or TLS protocol working in transport layer. It supports a security access via a web browser.

SSH

This function is based on the SSH protocol, a security protocol established on application and transport layers. The function with SSH is similar to a telnet connection, but SSH can provide information security and powerful authentication.

Telnet

This function is based on the Telnet protocol subjected to TCP/IP protocol. Through Telnet, users can log on to the switch remotely.

Serial Port

TP-LINK Omada TL-SG2008P - Serial Port - 1

Note:

Serial Port is only available on certain devices. To check whether your device supports this feature, refer to the actual web interface. If Serial Port is available, there is SECURITY > Access Security > Serial Port Config in the menu structure.

You can configure the serial port parameters.

2 Access Security Configurations

With access security configurations, you can:

■ Configure the Access Control feature
■ Configure the HTTP feature
■ Configure the HTTPS feature
■ Configure the SSH feature
■ Configure the Telnet function
■ Configure the Serial Port parameters

2.1 Using the GUI

2.1.1 Configuring the Access Control Feature

Choose the menu SECURITY > Access Security > Access Control to load the following page.

Figure 2-1 Configuring the Access Control
TP-LINK Omada TL-SG2008P - Configuring the Access Control Feature - 1

text_image Global Config Access Control: ✓ Enable Control Mode: IP-based Entry Table Add Delete ID Port/IP/MAC Access Interface Operation No Entries in this table. Total: 0

1) In the Global Config section, enable Access Control, select one control mode and click Apply.

Control Mode Choose how to control the users' access.

IP-based: Only the users within a certain IP-range can access the switch via the specified interfaces

MAC-based: Only the users with a certain MAC address can access the switch via the specified interfaces.

Port-based: Only the users who are connected to certain ports can access the switch via the specified interfaces.

2) In the Entry Table section, click to add an Access Control entry.

■ When the IP-based mode is selected, the following window will pop up.

Figure 2-2 Configuring Access Control Based on IP Range
TP-LINK Omada TL-SG2008P - Configuring the Access Control Feature - 2

text_image IP-based Access Interface: IP Address: (Format: 192.168.0.1) Mask: (Format: 255.255.255.0) Cancel Create

Access Interface

Select the interfaces where to apply the Access Control rule. If an interface is unselected, all users can access the switch via it.

SNMP: A function to manage the network devices via NMS.

Telnet: A connection type for users to remote login.

SSH: A connection type based on SSH protocol.

HTTP: A connection type based on HTTP protocol.

HTTPS: A connection type based on SSL protocol.

Ping: A communication protocol to test the connection of the network.

IP Address/Mask

Enter the IP address and mask to specify an IP range. Only the users within this IP range can access the switch via the specified interfaces.

■ When the MAC-based mode is selected, the following window will pop up.

Figure 2-3 Configuring Access Control Entry Based on MAC Address
TP-LINK Omada TL-SG2008P - Configuring the Access Control Feature - 3

text_image MAC-based Access Interface: MAC Address: (Format: #-##-##-##-##) Cancel Create

Access Interface

Select the interfaces where to apply the Access Control rule. If an interface is unselected, all users can access the switch via it.

SNMP: A function to manage the network devices via NMS.

Telnet: A connection type for users to remote login.

SSH: A connection type based on SSH protocol.

HTTP: A connection type based on HTTP protocol.

HTTPS: A connection type based on SSL protocol.

Ping: A communication protocol to test the connection of the network.

MAC Address Enter the MAC address. Only the users with this MAC address can access the switch via the specified interfaces.

■ When the Port-based mode is selected, the following window will pop up.

Figure 2-4 Configuring Access Control Entry Based on Port
TP-LINK Omada TL-SG2008P - Configuring the Access Control Feature - 4

text_image Port-based Access Interface: Port: (Format 1/0/1) UNIT1 Select All 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create
Access InterfaceSelect the interfaces where to apply the Access Control rule. If an interface is unselected, all users can access the switch via it.
SNMP: A function to manage the network devices via NMS.
Telnet: A connection type for users to remote login.
SSH: A connection type based on SSH protocol.
HTTP: A connection type based on HTTP protocol.
HTTPS: A connection type based on SSL protocol.
Ping: A communication protocol to test the connection of the network.
Port Select one or more ports. Only the users who are connected to these ports can access the switch via the specified interfaces.

3) Click Create. Then you can view the created entries in the table.

2.1.2 Configuring the HTTP Function

Choose the menu SECURITY > Access Security > HTTP Config to load the following page.

Figure 2-5 Configuring the HTTP Function
TP-LINK Omada TL-SG2008P - Configuring the HTTP Function - 1

text_image Global Config HTTP: ✓ Enable Port: 80 (1-65535) Apply Session Config Session Timeout: 10 minutes (5-30) Apply Number of Access Users Number Control: □ Enable Number of Admins: 1 (1-16) Number of Operators: 0 (0-15) Number of Power Users: 0 (0-15) Number of Users: 0 (0-15) Apply

1) In the Global Control section, enable HTTP function, specify the port using for HTTP, and click Apply to enable the HTTP function.

HTTP HTTP function is based on the HTTP protocol. It allows users to manage the switch through a web browser.

Port Specify the port number for HTTP service.

2) In the Session Config section, specify the Session Timeout and click Apply.

Session The system will log out automatically if users do nothing within the Session Timeout Timeout time.

3) In the Number of Access Users section, enable Number Control function, specify the following parameters and click Apply.

Number Control Enable or disable Number Control. With this option enabled, you can control the number of the users logging on to the web management page at the same time. The total number of users should be no more than 16.

Number of Admins Specify the maximum number of users whose access level is Admin.

Number of Operators Specify the maximum number of users whose access level is Operator.

Number of Power Users Specify the maximum number of users whose access level is Power User.

Number of Users Specify the maximum number of users whose access level is User.

2.1.3 Configuring the HTTPS Function

Choose the menu SECURITY > Access Security > HTTPS Config to load the following page.

Figure 2-6 Configuring the HTTPS Function
TP-LINK Omada TL-SG2008P - Configuring the HTTPS Function - 1

text_image Global Config HTTPS: ✓ Enable Protocol Version: ALL ▼ Port: 443 (1-65535) Apply Cipher Suite Config RSA_WITH_RC4_128_MD5: ✓ Enable RSA_WITH_RC4_128_SHA: ✓ Enable RSA_WITH_DES_CBC_SHA: ✓ Enable RSA_WITH_3DES_EDE_CBC_SHA: ✓ Enable ECDHE_WITH_AES_128_GCM_SHA256: ✓ Enable ECDHE_WITH_AES_256_GCM_SHA384: ✓ Enable Apply Session Config Session Timeout: 10 minutes (5-30) Apply Number of Access Users Number Control: ☐ Enable Number of Admins: 1 (1-16) Number of Operators: 0 (0-15) Number of Power Users: 0 (0-15) Number of Users: 0 (0-15) Apply Load Certificate Certificate File: Browse Load Load Key Key File: Browse Load

1) In the Global Config section, enable HTTPS function, select the protocol version that the switch supports and specify the port using for HTTPS. Click Apply.

HTTPS Enable or disable the HTTPS function.

HTTPS function is based on the SSL or TLS protocol. It provides a secure connection between the client and the switch.
Protocol VersionSelect the protocol version for HTTPS. Make sure the protocol in use is compatible with that on your HTTPS client.
SSL is a transport protocol. It can provide server authentication, encryption and message integrity to allow secure HTTP connection.
TLS is a transport protocol upgraded from SSL. It can support a more secure connection than SSL. TLS and SSL are not compatible with each other.
SSL Version 3.0: Select SSL Version 3.0 as the protocol for HTTPS.
TLS Version 1.0: Select TLS Version 1.0 as the protocol for HTTPS.
TLS Version 1.1: Select TLS Version 1.1 as the protocol for HTTPS.
TLS Version 1.2: Select TLS Version 1.2 as the protocol for HTTPS.
All: Enable all the above protocols for HTTPS. The HTTPS server and client will negotiate the protocol each time.

Port Specify the port number for HTTPS service.

2) In the CipherSuite Config section, select the algorithm to be enabled and click Apply.

RSA_WITH_RC4_128_MD5128-bit RC4 encryption with MD5 message authentication and RSA key exchange.
RSA_WITH_RC4_128_SHA128-bit RC4 encryption with SHA-1 message authentication and RSA key exchange.
RSA_WITH_DES_CBC_SHA56-bit DES encryption with SHA-1 message authentication and RSA key exchange.
RSA_WITH_3DES_EDE_CBC_SHA168-bit Triple DES encryption with SHA-1 message authentication and RSA key exchange.
ECDHE_WITH_AES_128_GCM_SHA256128-bit AES in Galois Counter Mode encryption with SHA-256 message authentication and elliptic curve Diffie-Hellman key exchange signed with an RSA certificate or ECDSA certificate.
ECDHE_WITH_AES_256_GCM_SHA384256-bit AES in Galois Counter Mode encryption with SHA-384 message authentication and elliptic curve Diffie-Hellman key exchange signed with an RSA certificate or ECDSA certificate.

3) In the Session Config section, specify the Session Timeout and click Apply.

SessionTimeoutThe system will log out automatically if users do nothing within the SessionTimeout time.

4) In the Number of Access Users section, enable Number Control function, specify the following parameters and click Apply.

Number ControlEnable or disable Number Control. With this option enabled, you can control the number of the users logging on to the web management page at the same time. The total number of users should be no more than 16.
Number of AdminsSpecify the maximum number of users whose access level is Admin.
Number of OperatorsSpecify the maximum number of users whose access level is Operator.
Number of Power UsersSpecify the maximum number of users whose access level is Power User.
Number of UsersSpecify the maximum number of users whose access level is User.

5) In the Load Certificate and Load Key section, download the certificate and key.

Certificate FileSelect the desired certificate to download to the switch. The certificate must be BASE64 encoded. The SSL certificate and key downloaded must match each other, otherwise the HTTPS connection will not work.
Key File Select the desired Key to download to the switch. The key must be BASE64 encoded. The SSL certificate and key downloaded must match each other, otherwise the HTTPS connection will not work.

2.1.4 Configuring the SSH Feature

Choose the menu SECURITY > Access Security > SSH Config to load the following page.

Figure 2-7 Configuring the SSH Feature
TP-LINK Omada TL-SG2008P - Configuring the SSH Feature - 1

text_image Global Config SSH: Enable Protocol V1: Enable Protocol V2: Enable Idle Timeout: 120 seconds(1-120) Maximum Connections: 5 (1-5) Port: 22 (1-65535) Apply Encryption Algorithm AES128-CBC: Enable AES192-CBC: Enable AES256-CBC: Enable Blowfish-CBC: Enable CAST128-CBC: Enable 3DES-CBC: Enable Apply Data Integrity Algorithm HMAC-SHA1: Enable HMAC-MD5: Enable Apply Load Key Choose the SSH public key file to download into the switch. Key Type: SSH-2 RSA/DSA Key File: Browse Load

1) In the Global Config section, select Enable to enable SSH function and specify following parameters.

SSH Select Enable to enable the SSH function.

SSH is a protocol working in application layer and transport layer. It can provide a secure, remote connection to a device. It is more secure than Telnet protocol as it provides strong encryption.

Protocol V1 Select Enable to enable SSH version 1.
Protocol V2 Select Enable to enable SSH version 2.
Idle Timeout Specify the idle timeout time. The system will automatically release the connection when the time is up.
Maximum ConnectionsSpecify the maximum number of the connections to the SSH server. New connection will not be established when the number of the connections reaches the maximum number you set.
Port Specify the port using for SSH.

2) In the Encryption Algorithm section, enable the encryption algorithm you want the switch to support and click Apply.
3) In Data Integrity Algorithm section, enable the integrity algorithm you want the switch to support and click Apply.
4) In Import Key File section, select key type from the drop-down list and click Browse to download the desired key file.

Key Type Select the key type. The algorithm of the corresponding type is used for both key generation and authentication.
Key FileSelect the desired public key to download to the switch. The key length of the downloaded file ranges of 512 to 3072 bits.

TP-LINK Omada TL-SG2008P - Configuring the SSH Feature - 2

Note:

It will take a long time to download the key file. Please wait without any operation.

2.1.5 Configuring the Telnet Function

Choose the menu SECURITY > Access Security > Telnet Config to load the following page.

Figure 2-8 Configuring the Telnet Function
TP-LINK Omada TL-SG2008P - Configuring the Telnet Function - 1

text_image Telnet Config Telnet: ✓ Enable Port: 23 (1-65535) Apply

Enable Telnet and click Apply.

TelnetSelect Enable to make the Telnet function effective. Telnet function is based on the Telnet protocol subjected to TCP/IP protocol. It allows users to log on to the switch remotely.
Port Specify the port using for Telnet.

2.1.6 Configuring the Serial Port Parameters

TP-LINK Omada TL-SG2008P - Configuring the Serial Port Parameters - 1

Note:

Serial Port is only available on certain devices. To check whether your device supports this feature, refer to the actual web interface. If Serial Port is available, there is SECURITY > Access Security > Serial Port Config in the menu structure.

Choose the menu SECURITY > Access Security > Serial Port Config to load the following page.

Figure 2-9 Configuring the Serial Port Parameters
TP-LINK Omada TL-SG2008P - Note: - 1

text_image Serial Port Settings Baud Rate: 38400 Data Bits: 8 Parity Bits: none Stop Bits: 1 Apply

Configure the Baud Rate and click Apply.

Baud Rate Configure the baud rate of the console connection. The default value is 38400 bps.

Data Bits Displays the data bits.

Parity Bits Displays the parity bits.

Stop Bits Displays the stop bits.

2.2 Using the CLI

2.2.1 Configuring the Access Control Feature

Follow these steps to configure the access control:

Step 1 configure

Enter global configuration mode.

Step 2

■ Use the following command to control the users' access by limiting the IP address:

user access-control ip-based enable

Configure the control mode as IP-based.

user access-control ip-based {ip-addr ip-mask} [snmp] [telnet] [ssh] [http] [https] [ping] [all]

Only the users within a certain IP-range can access the switch via the specified interfaces.

ip-addr: Specify the IP address of the user.

ip-mask: Specify the subnet mask of the user.

【snmp】【telnet】【ssh】【http】【https】【ping】【all】: Select the interfaces where to apply the Access Control rule. If an interface is unselected, all users can access the switch via it. By default, all the interfaces are selected.

■ Use the following command to control the users' access by limiting the MAC address:

user access-control mac-based enable

Configure the control mode as MAC-based.

user access-control mac-based {mac-addr} [snmp] [telnet] [ssh] [http] [https] [ping] [all]

Only the users with a certain MAC address can access the switch via the specified interfaces.

mac-addr: Specify the MAC address of the user.

【snmp】【telnet】【ssh】【http】【https】【ping】【all】: Select the interfaces where to apply the Access Control rule. If an interface is unselected, all users can access the switch via it. By default, all the interfaces are selected.

- Use the following command to control the users' access by limiting the ports connected to the users:

user access-control port-based enable

Configure the control mode as Port-based.

user access-control port-based interface { fastEthernet port-list | gigabitEthernet port-list | ten-gigabitEthernet port-list } [ snmp ] [ telnet ] [ ssh ] [ http ] [ https ] [ ping ] [ all ]

Only the users who are connected to certain ports can access the switch via the specified interfaces.

port-list: Specify the list of Ethernet port, in the format of 1/0/1-4. You can appoint 5 ports at most.

【snmp】[telnet][ssh][http][https][ping][all]: Select the interfaces where to apply the Access Control rule. If an interface is unselected, all users can access the switch via it. By default, all the interfaces are selected.

Step 3 show user configuration

Verify the security configuration information of the user authentication information and the access interface.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to set the type of access control as IP-based. Set the IP address as 192.168.0.100, set the subnet mask as 255.255.255.0, and select snmp, telnet, http and https to apply the Access Control rule.

Switch#configure

Switch(config)#user access-control ip-based enable

Switch(config)#user access-control ip-based 192.168.0.100 255.255.255.255 snmp telnet http https

Switch(config)#show user configuration

User authentication mode: IP based

IndexIP AddressAccess Interface
1192.168.0.100/24SNMP Telnet HTTP HTTPS

Switch(config)#end

Switch#copy running-config startup-config

2.2.2 Configuring the HTTP Function

Follow these steps to configure the HTTP function:

Step 1 configure

Enter global configuration mode.

Step 2 ip http server

Enable the HTTP function. By default, it is enabled.

Step 3 ip http session timeout minutes

Specify the Session Timeout time. The system will log out automatically if users do nothing within the Session Timeout time.

minutes: Specify the timeout time, which ranges from 5 to 30 minutes. The default value is 10.

Step 4 ip http max-users admin-num operator-num poweruser-num user-num

Specify the maximum number of users that are allowed to connect to the HTTP server. The total number of users should be no more than 16.

admin-num: Enter the maximum number of users whose access level is Admin. The valid values are from 1 to 16.

operator-num: Enter the maximum number of users whose access level is Operator. The valid values are from 0 to 15.

poweruser-num: Enter the maximum number of users whose access level is Power User. The valid values are from 0 to 15.

user-num: Enter the maximum number of users whose access level is User. The valid values are from 0 to 15.

Step 5 show ip http configuration

Verify the configuration information of the HTTP server, including status, session timeout, access-control, max-user number and the idle-timeout, etc.

Step 6 end

Return to privileged EXEC mode.

Step 7 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to set the session timeout as 9, set the maximum admin number as 6, and set the maximum operator number as 2, the maximum power user number as 2, the maximum user number as 2.

Switch#configure

Switch(config)#ip http server

Switch(config)#ip http session timeout 9

Switch(config)#ip http max-user 6222

Switch(config)#show ip http configuration

HTTP Status: Enabled

HTTP Port: 80

HTTP Session Timeout: 9

HTTP User Limitation: Enabled

HTTP Max Users as Admin: 6

HTTP Max Users as Operator: 2

HTTP Max Users as Power User: 2

HTTP Max Users as User: 2

Switch(config)#end

Switch#copy running-config startup-config

2.2.3 Configuring the HTTPS Function

Follow these steps to configure the HTTPS function:

Step 1 configure

Enter global configuration mode.

Step 2 ip http secure-server

Enable the HTTPS function. By default, it is enabled.

Step 3 ip http secure-protocol { ssl3 | tls1 | tls11 | tls12 | all }

Select the protocol version for HTTPS. Make sure the protocol in use is compatible with that on your HTTPS client.

SSL is a transport protocol. It can provide server authentication, encryption and message integrity to allow secure HTTP connection.

TLS is a transport protocol upgraded from SSL. It can support a more secure connection than SSL. TLS and SSL are not compatible with each other.

ssl3: Select SSL Version 3.0 as the protocol for HTTPS.

tls1: Select TLS Version 1.0 as the protocol for HTTPS.

tls11: Select TLS Version 1.1 as the protocol for HTTPS.

tls12: Select TLS Version 1.2 as the protocol for HTTPS.

all: Enable all the above protocols for HTTPS. The HTTPS server and client will negotiate the protocol each time.

Step 4 ip http secure-ciphersuite { [rc4-128-md5] [rc4-128-sha] [des-cbc-sha] [3des-ede-cbc-sha] [ecdhe-a128-g-s256] [ecdhe-a256-g-s384]}

Enable the corresponding ciphersuite. By default, these types are all enabled.

rc4-128-md5: 128-bit RC4 encryption with MD5 message authentication and RSA key exchange.

rc4-128-sha: 128-bit RC4 encryption with SHA-1 message authentication and RSA key exchange.

des-cbc-sha: 56-bit DES encryption with SHA-1 message authentication and RSA key exchange.

3des-ede-cbc-sha: 168-bit Triple DES encryption with SHA-1 message authentication and RSA key exchange.

ecdhe-a128-g-s256: 128-bit AES in Galois Counter Mode encryption with SHA-256 message authentication and elliptic curve Diffie-Hellman key exchange signed with an RSA certificate or ECDSA certificate.

ecdhe-a256-g-s384: 256-bit AES in Galois Counter Mode encryption with SHA-384 message authentication and elliptic curve Diffie-Hellman key exchange signed with an RSA certificate or ECDSA certificate.

Step 5 ip http secure-session timeout minutes

Specify the Session Timeout time. The system will log out automatically if users do nothing within the Session Timeout time.

minutes: Specify the timeout time, which ranges from 5 to 30 minutes. The default value is 10.

Step 6 ip http secure-max-users admin-num operator-num poweruser-num user-num

Specify the maximum number of users that are allowed to connect to the HTTPS server. The total number of users should be no more than 16.

admin-num: Enter the maximum number of users whose access level is Admin. The valid values are from 1 to 16.

operator-num: Enter the maximum number of users whose access level is Operator. The valid values are from 0 to 15.

poweruser-num: Enter the maximum number of users whose access level is Power User. The valid values are from 0 to 15.

user-num: Enter the maximum number of users whose access level is User. The valid values are from 0 to 15.

Step 7 ip http secure-server download certificate ssl-cert ip-address ip-addr

Download the desired certificate to the switch from TFTP server.

ssl-cert. Specify the name of the SSL certificate, which ranges from 1 to 25 characters. The certificate must be BASE64 encoded. The SSL certificate and key downloaded must match each other.

ip-addr: Specify the IP address of the TFTP server. Both IPv4 and IPv6 addresses are supported.

Step 8 ip http secure-server download key ssl-key ip-address ip-addr

Download the desired key to the switch from TFTP server.

ssl-key: Specify the name of the key file saved in TFTP server. The key must be BASE64 encoded.

ip-addr: Specify the IP address of the TFTP server. Both IPv4 and IPv6 addresses are supported.

Step 9 show ip http secure-server

Verify the global configuration of HTTPS.

Step 10 end

Return to privileged EXEC mode.

Step 11 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to configure the HTTPS function. Enable all the protocol versions, including SSL 3.0, TLS 1.0, TLS 1.1 and TLS1.2. Enable the ciphersuite of 3desede-cbc-sha. Set the session timeout time as 15, the maximum admin number as 2, the maximum operator number as 2, the maximum power user number as 2, the maximum user

number as 2. Download the certificate named ca.crt and the key named ca.key from the TFTP server with the IP address 192.168.0.100.

Switch#configure

Switch(config)#ip http secure-server

Switch(config)#ip http secure-protocol all

Switch(config)#ip http secure-ciphersuite 3des-ede-cbc-sha

Switch(config)#ip http secure-session timeout 15

Switch(config)#ip http secure-max-users 2 2 2 2

Switch(config)#ip http secure-server download certificate ca.crt ip-address 192.168.0.100

Start to download SSL certificate...

Download SSL certificate OK.

Switch(config)#ip http secure-server download key ca.key ip-address 192.168.0.100

Start to download SSL key...

Download SSL key OK.

Switch(config)#show ip http secure-server

HTTPS Status: Enabled

HTTPS

Port:

443

SSL Protocol Level(s): all

SSL CipherSuite: 3des-ede-cbc-sha

HTTPS Session Timeout: 15

HTTPS User Limitation: Enabled

HTTPS Max Users as Admin: 2

HTTPS Max Users as Operator: 2

HTTPS Max Users as Power User: 2

HTTPS Max Users as User: 2

Switch(config)#end

Switch#copy running-config startup-config

2.2.4 Configuring the SSH Feature

Follow these steps to configure the SSH function:

Step 1 configure

Enter global configuration mode.

Step 2 ip ssh server

Enable the SSH function. By default, it is disabled.

Step 3 ip ssh version {v1 | v2}

Configure to make the switch support the corresponding protocol. By default, the switch supports SSHv1 and SSHv3.

v1 | v2: Select to enable the corresponding protocol.

Step 4 ip ssh timeout value

Specify the idle timeout time. The system will automatically release the connection when the time is up.

value: Enter the value of the timeout time, which ranges from 1 to 120 seconds. The default value is 120 seconds.

Step 5 ip ssh max-client num

Specify the maximum number of the connections to the SSH server. New connection will not be established when the number of the connections reaches the maximum number you set.

num: Enter the number of the connections, which ranges from 1 to 5. The default value is 5.

Step 6 ip ssh algorithm { AES128-CBC | AES192-CBC | AES256-CBC | Blowfish-CBC | Cast128-CBC | 3DES-CBC | HMAC-SHA1 | HMAC-MD5 }

Enable the corresponding algorithm. By default, these types are all enabled.

AES128-CBC | AES192-CBC | AES256-CBC | Blowfish-CBC | Cast128-CBC | 3DES-CBC:

Specify the encryption algorithm you want the switch supports.

HMAC-SHA1 | HMAC-MD5: Specify the data integrity algorithm you want the switch supports.

Step 7 ip ssh download {v1 | v2} key-file ip-address ip-addr

Select the type of the key file and download the desired file to the switch from TFTP server.

v1 | v2: Select the key type. The algorithm of the corresponding type is used for both key generation and authentication.

key-file: Specify the name of the key file saved in TFTP server. Ensure the key length of the downloaded file is in the range of 512 to 3072 bits.

ip-addr: Specify the IP address of the TFTP server. Both IPv4 and IPv6 addresses are supported.

Step 8 show ip ssh

Verify the global configuration of SSH.

Step 9 end

Return to privileged EXEC mode.

Step 10 copy running-config startup-config

Save the settings in the configuration file.

TP-LINK Omada TL-SG2008P - Step 8 show ip ssh - 1

Note:

It will take a long time to download the key file. Please wait without any operation.

The following example shows how to configure the SSH function. Set the version as SSH V1 and SSH V2. Enable the AES128-CBC and Cast128-CBC encryption algorithm. Enable the HMAC-MD5 data integrity algorithm. Choose the key type as SSH-2 RSA/DSA.

Switch(config)#ip ssh server

Switch(config)#ip ssh version v1

Switch(config)#ip ssh version v2

Switch(config)#ip ssh timeout 100

Switch(config)#ip ssh max-client 4

Switch(config)#ip ssh algorithm AES128-CBC

Switch(config)#ip ssh algorithm Cast128-CBC

Switch(config)#ip ssh algorithm HMAC-MD5

Switch(config)#ip ssh download v2 publickey ip-address 192.168.0.100

Start to download SSH key file...

Download SSH key file OK.

Switch(config)#show ip ssh

Global Config:

SSH Server: Enabled

Protocol V1: Enabled

Protocol V2: Enabled

Idle Timeout: 100

MAX Clients: 4

Port: 22

Encryption Algorithm:

AES128-CBC: Enabled

AES192-CBC: Disabled

AES256-CBC: Disabled

Blowfish-CBC: Disabled

Cast128-CBC: Enabled

3DES-CBC: Disabled

Data Integrity Algorithm:

HMAC-SHA1: Disabled

HMAC-MD5: Enabled

Key Type: SSH-2 RSA/DSA

Key File:

---- BEGIN SSH2 PUBLIC KEY ----

Comment: "dsa-key-20160711"

Switch(config)#end

Switch#copy running-config startup-config

2.2.5 Configuring the Telnet Function

Follow these steps enable the Telnet function:

Step 1 configure

Enter global configuration mode.

Step 2 telnet enable

Enable the telnet function. By default, it is enabled.

Step 3 telnet port port

Specify the port using for Telnet. It ranges from 1 to 65535.

Step 4 end

Return to privileged EXEC mode.

Step 4 copy running-config startup-config

Save the settings in the configuration file.

2.2.6 Configuring the Serial Port Parameters

TP-LINK Omada TL-SG2008P - Configuring the Serial Port Parameters - 1

Note:

Serial Port is only available on certain devices. To check whether your device supports this feature, refer to the actual web interface. If Serial Port is available, there is SECURITY > Access Security > Serial Port Config in the menu structure.

Follow these steps enable the serial port parameters:

Step 1 configure

Enter global configuration mode.

Step 2 serial_port baud_rate {9600|19200|38400|57600|115200}

Specify the baud rate of the console connection.

9600 | 19200 | 38400 | 57600 | 115200: Specify the communication baud rate on the console port. The default value is 38400 bps.

Step 3 end

Return to privileged EXEC mode.

Step 4 copy running-config startup-config

Save the settings in the configuration file.

3

Appendix: Default Parameters

Default settings of Access Security are listed in the following tables.

Table 3-1 Default Settings of Access Control Configuration

Parameter Default Setting
Access Control Disabled

Table 3-2 Default Settings of HTTP Configuration

Parameter Default Setting
HTTP Enabled
Port 80
Session Timeout 10 minutes
Number Control Disabled

Table 3-3 Default Settings of HTTPS Configuration

Parameter Default Setting
HTTPS Enabled
Protocol Version All
Port 443
RSA_WITH_RC4_128_MD5 Enabled
RSA_WITH_RC4_128_SHA Enabled
RSA_WITH_DES_CBC_SHA Enabled
RSA_WITH_3DES_EDE_CBC_SHAEnabled
ECDHE_WITH_AES_128_GCM_SHA256Enabled
ECDHE_WITH_AES_256_GCM_SHA384Enabled
Session Timeout10 minutes
Number Control Disabled

Table 3-4 Default Settings of SSH Configuration

Parameter Default Setting
SSHDisabled
Protocol V1Enabled
Protocol V2Enabled
Idle Timeout 120 seconds
Maximum Connections 5
Port 22
AES128-CBC Enabled
AES192-CBC Enabled
AES256-CBC Enabled
Blowfish-CBC Enabled
Cast128-CBC Enabled
3DES-CBC Enabled
HMAC-SHA1 Enabled
HMAC-MD5 Enabled
Key Type: SSH-2 RSA/DSA

Table 3-5 Default Settings of Telnet Configuration

Parameter Default Setting
TelnetEnabled
Port 23

Table 3-6 Default Settings of Serial Port

Parameter Default Setting
Baud Rate38400 bps

Part 24

Configuring AAA

CHAPTERS

  1. Overview
  2. AAA Configuration
  3. Configuration Example
  4. Appendix: Default Parameters

1 Overview

AAA stands for authentication, authorization and accounting. On TP-Link switches, this feature is mainly used to authenticate the users trying to log in to the switch or get administrative privileges. The administrator can create guest accounts and an Enable password for other users. The guests do not have administrative privileges without the Enable password provided.

AAA provides a safe and efficient authentication method. The authentication can be processed locally on the switch or centrally on the RADIUS/TACACS+ server(s). As the following figure shows, the network administrator can centrally configure the management accounts of the switches on the RADIUS server and use this server to authenticate the users trying to access the switch or get administrative privileges.

Figure 1-1 Network Topology of AAA
TP-LINK Omada TL-SG2008P - Overview - 1

flowchart
graph TD
    A["User Switch"] --> B["Switch"]
    C["User Switch"] --> D["Switch"]
    E["User Switch"] --> F["Switch"]
    B --> G["RADIUS Server"]
    D --> G
    F --> G

2 AAA Configuration

In the AAA feature, the authentication can be processed locally on the switch or centrally on the RADIUS/TACACS+ server(s). To ensure the stability of the authentication system, you can configure multiple servers and authentication methods at the same time. This chapter introduces how to configure this kind of comprehensive authentication in AAA.

To complete the configuration, follow these steps:

1) Add the servers.
2) Configure the server groups.
3) Configure the method list.
4) Configure the AAA application list.
5) Configure the login account and the Enable password.

Configuration Guidelines

The basic concepts and working mechanism of AAA are as follows:

■ AAA Default Setting

By default, the AAA feature is enabled and cannot be disabled.

■ Server Group

Multiple servers running the same protocol can be added to a server group, and the servers in the group will authenticate the users in the order they are added. The server that is first added to the group has the highest priority, and is responsible for authentication under normal circumstances. If the first one breaks down or doesn't respond to the authentication request for some reason, the second sever will start working for authentication, and so on.

■ Method List

A server group is regarded as a method, and the local authentication is another method. Several methods can be configured to form a method list. The switch uses the first method in the method list to authenticate the user, and if that method fails to respond, the switch selects the next method. This process continues until the user has a successful communication with a method or until all defined methods are exhausted. If the authentication succeeds or the secure server or the local switch denies the user's access, the authentication process stops and no other methods are attempted.

Two types of method list are provided: Login method list for users of all types to access the switch, and Enable method list for guests to get administrative privileges.

■ AAA Application List

The switch supports the following access applications: Telnet, SSH and HTTP. You can select the configured authentication method lists for each application.

2.1 Using the GUI

2.1.1 Adding Servers

You can add one or more RADIUS/TACACS+ servers on the switch for authentication. If multiple servers are added, the server that is first added to the group has the highest priority and authenticates the users trying to access the switch. The others act as backup servers in case the first one breaks down.

■ Adding RADIUS Server

Choose the menu SECURITY > AAA > RADIUS Config and click to load the following page.

Figure 2-1 RADIUS Server Configuration
TP-LINK Omada TL-SG2008P - ■ Adding RADIUS Server - 1

text_image RADIUS Server Server IP: (Format:192.168.0.1) Shared Key: 1-32 characters. Only numbers, letters and the following symbols are allowed: - . / : @ _ . Authentication Port: 1812 (1-65535) Accounting Port: 1813 (1-65535) Retransmit: 2 (1-3) Timeout: 5 seconds (1-9) NAS Identifier: (Optional) Cancel Create

Follow these steps to add a RADIUS server:

1) Configure the following parameters.

Server IP Enter the IP address of the server running the RADIUS secure protocol.

Shared Key Enter the shared key between the RADIUS server and the switch. The RADIUS server and the switch use the key string to encrypt passwords and exchange responses.

Authentication Port Specify the UDP destination port on the RADIUS server for authentication requests. The default setting is 1812.

Accounting PortSpecify the UDP destination port on the RADIUS server for accounting requests. The default setting is 1813. Usually, it is used in the 802.1x feature.
RetransmitSpecify the number of times a request is resent to the server if the server does not respond. The default setting is 2.
Timeout Specify the time interval that the switch waits for the server to reply before resending. The default setting is 5 seconds.
NAS IdentifierSpecify the name of the NAS (Network Access Server) to be contained in RADIUS packets for identification. It ranges from 1 to 31 characters. The default value is the MAC address of the switch. Generally, the NAS indicates the switch itself.

2) Click Create to add the RADIUS server on the switch.

■ Adding TACACS+ Server

Choose the menu SECURITY > AAA > TACACS+ Config and click to load the following page.

Figure 2-2 TACACS+ Server Configuration
TP-LINK Omada TL-SG2008P - ■ Adding RADIUS Server - 2

text_image TACACS+ Server Server IP: (Format:192.168.0.1) Timeout: 5 seconds (1-9) Shared Key: 1-32 characters. Only numbers, letters and the following symbols are allowed: - . / : @ _ . Server Port: 49 (1-65535) Cancel Create

Follow these steps to add a TACACS+ server:

1) Configure the following parameters.

Server IP Enter the IP address of the server running the TACACS+ secure protocol.
Timeout Specify the time interval that the switch waits for the server to reply before resending. The default setting is 5 seconds.
Shared Key Enter the shared key between the TACACS+ server and the switch. The TACACS+ server and the switch use the key string to encrypt passwords and exchange responses.
Server PortSpecify the TCP port used on the TACACS+ server for AAA. The default setting is 49.

2) Click Create to add the TACACS+ server on the switch.

2.1.2 Configuring Server Groups

The switch has two built-in server groups, one for RADIUS servers and the other for TACACS+ servers. The servers running the same protocol are automatically added to the default server group. You can add new server groups as needed.

Choose the menu SECURITY > AAA > Server Group to load the following page.

Figure 2-3 Add New Server Group
TP-LINK Omada TL-SG2008P - Configuring Server Groups - 1

text_image Server Group List ID Server Group Server Type Server IP Operation 1 radius RADIUS 2 tacacs TACACS+ Total: 2

There are two default server groups in the list. You can edit the default server groups or follow these steps to configure a new server group:

1) Click and the following window will pop up.

Figure 2-4 Add Server Group
TP-LINK Omada TL-SG2008P - Configuring Server Groups - 2

text_image Server Group Server Group: (1-15 characters) Server Type: RADIUS Server IP: 192.168.0.99 Cancel Create

Configure the following parameters:

Server Group Specify a name for the server group.

Server Type Select the server type for the group. The following options are provided: RADIUS and TACACS+.

Server IP Select the IP address of the server which will be added to the server group.

2) Click Create.

2.1.3 Configuring the Method List

A method list describes the authentication methods and their sequence to authenticate the users. The switch supports Login Method List for users of all types to gain access to the switch, and Enable Method List for guests to get administrative privileges.

Choose the menu SECURITY > AAA > Method List to load the following page.

Figure 2-5 Method List
TP-LINK Omada TL-SG2008P - Configuring the Method List - 1

text_image Authentication Login Method List ID Name Pri1 Pri2 Pri3 Pri4 Operation 1 default local -- -- Total: 1 Authentication Enable Method List ID Name Pri1 Pri2 Pri3 Pri4 Operation 1 default none -- -- Total: 1

There are two default methods respectively for the Login authentication and the Enable authentication.

You can edit the default methods or follow these steps to add a new method:

1) Click + Add in the Authentication Login Method List section or Authentication Enable Method List section to add corresponding type of method list. The following window will pop up.

Figure 2-6 Add New Method
TP-LINK Omada TL-SG2008P - Configuring the Method List - 2

text_image Authentication Login Method Method List Name: (1-15 characters) Pri1: -- Pri2: -- Pri3: -- Pri4: -- Cancel Create

Configure the parameters for the method to be added.

Method List Name Specify a name for the method.

Pri1- Pri4 Specify the authentication methods in order. The method with priority 1 authenticates a user first, the method with priority 2 is tried if the previous method does not respond, and so on.

local: Use the local database in the switch for authentication.

none: No authentication is used.

radius: Use the remote RADIUS server/server groups for authentication.

tacacs: Use the remote TACACS+ server/server groups for authentication.

Other user-defined server groups: Use the user-defined server groups for authentication.

2) Click Create to add the new method.

2.1.4 Configuring the AAA Application List

Choose the menu SECURITY > AAA > Global Config to load the following page.

Figure 2-7 Configure Application List
TP-LINK Omada TL-SG2008P - Configuring the AAA Application List - 1

text_image AAA Application List Index Module Login List Enable List 1 telnet defaultITCHEN 2 ssh default default 3 ultimately default Total: 3 1 entry selected. Cancel Apply

Follow these steps to configure the AAA application list.

1) In the AAA Application List section, select an access application and configure the Login list and Enable list.

Module Displays the configurable applications on the switch: console, telnet, ssh and http.

Note: Console is only available on certain devices.

Login List Select a previously configured Login method list. This method list will authenticate the users trying to log in to the switch.

Enable List Select a previously configured Enable method list. This method list will authenticate the users trying to get administrative privileges.

2) Click Apply.

2.1.5 Configuring Login Account and Enable Password

The login account and Enable password can be configured locally on the switch or centrally on the RADIUS/TACACS+ server(s).

On the Switch

The local username and password for login can be configured in the User Management feature. For details, refer to Managing System.

To configure the local Enable password for getting administrative privileges, choose the menu SECURITY > AAA > Global Config to load the following page.

Figure 2-8 Configure Enable Password
TP-LINK Omada TL-SG2008P - On the Switch - 1

text_image Enable Admin Enable Admin: ○ Clear Password ● Set Password Password: (1-31 characters) Apply

There are two options: Clear Password and Set Password. You can choose whether the local Enable password is required when the guests try to get administrative privileges. Click Apply.

Tips: The logged-in guests can enter the local Enable password on this page to get administrative privileges.

On the Server

The accounts created by the RADIUS/TACACS+ server can only view the configurations and some network information without the Enable password.

Some configuration principles on the server are as follows:

■ For Login authentication configuration, more than one login account can be created on the server. Besides, both the user name and password can be customized.

■ For Enable password configuration:

On RADIUS server, the user name should be set as \enable\, and the Enable password is customizable. All the users trying to get administrative privileges share this Enable password.

On TACACS+ server, configure the value of "enable 15" as the Enable password in the configuration file. All the users trying to get administrative privileges share this Enable password.

2.2 Using the CLI

2.2.1 Adding Servers

You can add one or more RADIUS/TACACS+ servers on the switch for authentication. If multiple servers are added, the server with the highest priority authenticates the users trying to access the switch, and the others act as backup servers in case the first one breaks down.

■ Adding RADIUS Server

Follow these steps to add RADIUS server on the switch:

Step 1 configure

Enter global configuration mode.

Step 2 radius-server host ip-address [auth-port port-id] [acct-port port-id] [timeout time] [retransmit number] [nas-id nas-id] key { [0] string | 7 encrypted-string }

Add the RADIUS server and configure the related parameters as needed.

host ip-address: Enter the IP address of the server running the RADIUS protocol.

auth-port port-id: Specify the UDP destination port on the RADIUS server for authentication requests. The default setting is 1812.

acct-port port-id: Specify the UDP destination port on the RADIUS server for accounting requests. The default setting is 1813. Usually, it is used in the 802.1X feature.

timeout time: Specify the time interval that the switch waits for the server to reply before resending. The valid values are from 1 to 9 seconds and the default setting is 5 seconds.

retransmit number. Specify the number of times a request is resent to the server if the server does not respond. The valid values are from 1 to 3 and the default setting is 2.

nas-id nas-id: Specify the name of the NAS (Network Access Server) to be contained in RADIUS packets for identification. It ranges from 1 to 31 characters. The default value is the MAC address of the switch. Generally, the NAS indicates the switch itself.

key { [0] string | 7 encrypted-string }: Specify the shared key. 0 and 7 represent the encryption type. 0 indicates that an unencrypted key will follow. 7 indicates that a symmetric encrypted key with a fixed length will follow. By default, the encryption type is 0. string is the shared key for the switch and the server. encrypted-string is a symmetric encrypted key with a fixed length, which you can copy from the configuration file of another switch. The key or encrypted-key you configure here will be displayed in the encrypted form.

Step 3 show radius-server

Verify the configuration of RADIUS server.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to add a RADIUS server on the switch. Set the IP address of the server as 192.168.0.10, the authentication port as 1812, the shared key as 123456, the timeout as 8 seconds and the retransmit number as 3.

Switch#configure

Switch(config)#radius-server host 192.168.0.10 auth-port 1812 timeout 8 retransmit 3 key 123456

Switch(config)#show radius-server

Server IpAuth PortAcct PortTimeoutRetransmitNAS IdentifierShared key
192.168.0.101812181352000AEB132397123456

Switch(config)#end

Switch#copy running-config startup-config

■ Adding TACACS+ Server

Follow these steps to add TACACS+ server on the switch:

Step 1 configure

Enter global configuration mode.

Step 2 tacacs-server host ip-address [port port-id] [timeout time] [key { [0] string | 7 encrypted-string}]

Add the RADIUS server and configure the related parameters as needed.

hostip-address: Enter the IP address of the server running the TACACS+ protocol.

port port-id: Specify the TCP destination port on the TACACS+ server for authentication requests. The default setting is 49.

timeout time: Specify the time interval that the switch waits for the server to reply before resending. The valid values are from 1 to 9 seconds and the default setting is 5 seconds.

key { [0] string | 7 encrypted-string }: Specify the shared key. 0 and 7 represent the encryption type. 0 indicates that an unencrypted key will follow. 7 indicates that a symmetric encrypted key with a fixed length will follow. By default, the encryption type is 0. string is the shared key for the switch and the server. encrypted-string is a symmetric encrypted key with a fixed length, which you can copy from the configuration file of another switch. The key or encrypted-key you configured here will be displayed in the encrypted form.

Step 3 show tacacs-server

Verify the configuration of TACACS+ server.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to add a TACACS+server on the switch. Set the IP address of the server as 192.168.0.20, the authentication port as 49, the shared key as 123456, and the timeout as 8 seconds.

Switch#configure

Switch(config)#tacacs-server host 192.168.0.20 auth-port 49 timeout 8 key 123456

Switch(config)#show tacacs-server

Server IpPortTimeoutShared key
192.168.0.20498123456

Switch(config)#end

Switch#copy running-config startup-config

2.2.2 Configuring Server Groups

The switch has two built-in server groups, one for RADIUS and the other for TACACS+. The servers running the same protocol are automatically added to the default server group. You can add new server groups as needed.

The two default server groups cannot be deleted or edited. Follow these steps to add a server group:

Step 1 configure
Enter global configuration mode.

Step 2 aaa group { radius | tacacs } group-nameCreate a server group.radius | tacacs: Specify the group type.group-name: Specify a name for the group.
Step 3 server ip-addressAdd the existing servers to the server group.ip-address: Specify IP address of the server to be added to the group.
Step 4 show aaa group [ group-name ]Verify the configuration of server group.
Step 5 endReturn to privileged EXEC mode.
Step 6 copy running-config startup-configSave the settings in the configuration file.

The following example shows how to create a RADIUS server group named RADIUS1 and add the existing two RADIUS servers whose IP address is 192.168.0.10 and 192.168.0.20 to the group.

Switch#configure

Switch(config)#aaa group radius RADIUS1

Switch(aaa-group)#server 192.168.0.10

Switch(aaa-group)#server 192.168.0.20

Switch(aaa-group)#show aaa group RADIUS1

192.168.0.10

192.168.0.20

Switch(aaa-group)#end

Switch#copy running-config startup-config

2.2.3 Configuring the Method List

A method list describes the authentication methods and their sequence to authenticate the users. The switch supports Login Method List for users of all types to gain access to the switch, and Enable Method List for guests to get administrative privileges.

Follow these steps to configure the method list:

Step 1 configure

Enter global configuration mode.

Step 2 aaa authentication login {

method-list } { method1 } [ method2 ] [ method3 ] [ method4 ]

Configure a login method list.

method-list: Specify a name for the method list.

method1/method2/method3/method4: Specify the authentication methods in order. The first method authenticates a user first, the second method is tried if the previous method does not respond, and so on. The default methods include radius, tacacs, local and none. None means no authentication is used for login.

Step 3 aaa authentication enable {

method-list } {method1 } [method2 ] [method3 ] [method4 ]

Configure an Enable password method list.

method-list: Specify a name for the method list.

method1/method2/method3/method4: Specify the authentication methods in order. The default methods include radius, tacacs, local and none. None means no authentication is used for getting administrative privileges.

Step 4 show aaa authentication [ login | enable ]

Verify the configuration method list.

Step 5 end

Return to privileged EXEC mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to create a Login method list named Login1, and configure the method 1 as the default radius server group and the method 2 as local.

Switch#configure

Switch(config)##aaa authentication login Login1 radius local

Switch(config)#show aaa authentication login

Methodlistpri1pri2pri3pri4
defaultlocal------
Login1radiuslocal----

Switch(config)#end

Switch#copy running-config startup-config

The following example shows how to create an Enable method list named Enable1, and configure the method 1 as the default radius server group and the method 2 as local.

Switch#configure

Switch(config)##aaa authentication enable Enable1 radius local

Switch(config)#show aaa authentication enable

Methodlistpri1pri2pri3pri4
defaultlocal------
Enable1radiuslocal----

Switch(config)#end

Switch#copy running-config startup-config

2.2.4 Configuring the AAA Application List

You can configure authentication method lists on the following access applications: Console, Telnet, SSH and HTTP.

Console

TP-LINK Omada TL-SG2008P - Configuring the AAA Application List - 1

Note:

Console is only available on certain devices.

Follow these steps to apply the Login and Enable method lists for the application Console:

Step 1 configure

Enter global configuration mode.

Step 2 line console

linenum

Enter line configuration mode.

linenum: Enter the number of users allowed to login through console port. Its value is 0 in general, for the reason that console input is only active on one console port at a time.

Step 3 login authentication {

method-list }

Apply the Login method list for the application Console.

method-list: Specify the name of the Login method list.

Step 4 enable authentication {

method-list}

Apply the Enable method list for the application Console.

method-list: Specify the name of the Enable method list.

Step 5 show aaa global

Verify the configuration of application list.

Step 6 end

Return to privileged EXEC mode.

Step 7 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to apply the existing Login method list named Login1 and Enable method list named Enable1 for the application Console.

Switch#configure

Switch(config)#line console 0

Switch(config-line)#login authentication Login1

Switch(config-line)#enable authentication Enable1

Switch(config-line)#show aaa global

Module

Login List

Enable List

Console

Login1

Enable1

Telnetdefaultdefault
Sshdefaultdefault
Httpdefaultdefault

Switch(config-line)#end

Switch#copy running-config startup-config

Telnet

Follow these steps to apply the Login and Enable method lists for the application Telnet:

Step 1 configure

Enter global configuration mode.

Step 2 line telnet

Enter line configuration mode.

Step 3 login authentication {

method-list }

Apply the Login method list for the application Telnet.

method-list: Specify the name of the Login method list.

Step 4 enable authentication {

method-list}

Apply the Enable method list for the application Telnet.

method-list: Specify the name of the Enable method list.

Step 5 show aaa global

Verify the configuration of application list.

Step 6 end

Return to privileged EXEC mode.

Step 7 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to apply the existing Login method list named Login1 and Enable method list named Enable1 for the application Telnet.

Switch#configure

Switch(config)#line telnet

Switch(config-line)#login authentication Login1

Switch(config-line)#enable authentication Enable1

Switch(config-line)#show aaa global

Module

Login List

Enable List

TelnetLogin1Enable1
Sshdefaultdefault
Httpdefaultdefault

Switch(config-line)#end

Switch#copy running-config startup-config

■ SSH

Follow these steps to apply the Login and Enable method lists for the application SSH:

Step 1 configure

Enter global configuration mode.

Step 2 line ssh

Enter line configuration mode.

Step 3 login authentication {

method-list }

Apply the Login method list for the application SSH.

method-list: Specify the name of the Login method list.

Step 4 enable authentication {

method-list}

Apply the Enable method list for the application SSH.

method-list: Specify the name of the Enable method list.

Step 5 show aaa global

Verify the configuration of application list.

Step 6 end

Return to privileged EXEC mode.

Step 7 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to apply the existing Login method list named Login1 and Enable method list named Enable1 for the application SSH.

Switch#configure

Switch(config)#line ssh

Switch(config-line)#login authentication Login1

Switch(config-line)#enable authentication Enable1

Switch(config-line)#show aaa global

Module

Login List

Enable List

Telnetdefaultdefault
SshLogin1Enable1
Httpdefaultdefault

Switch(config-line)#end

Switch#copy running-config startup-config

HTTP

Follow these steps to apply the Login and Enable method lists for the application HTTP:

Step 1 configure

Enter global configuration mode.

Step 2 ip http login authentication {

method-list }

Apply the Login method list for the application HTTP.

method-list: Specify the name of the Login method list.

Step 3 ip http enable authentication {

method-list}

Apply the Enable method list for the application HTTP.

method-list: Specify the name of the Enable method list.

Step 4 show aaa global

Verify the configuration of application list.

Step 5 end

Return to privileged EXEC mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to apply the existing Login method list named Login1 and Enable method list named Enable1 for the application HTTP:

Switch#configure

Switch(config)#ip http login authentication Login1

Switch(config)#ip http enable authentication Enable1

Switch(config)#show aaa global

ModuleLogin ListEnable List
Telnetdefaultdefault
Sshdefaultdefault
HttpLogin1Enable1

Switch(config)#end

Switch#copy running-config startup-config

2.2.5 Configuring Login Account and Enable Password

The login account and Enable password can be configured locally on the switch or centrally on the RADIUS/TACACS+ server(s).

On the Switch

The local username and password for login can be configured in the User Management feature. For details, refer to Managing System.

To configure the local Enable password for getting administrative privileges, follow these steps:

Step 1 configure

Enter global configuration mode.

Step 2 Use the following command to create an enable password unencrypted or symmetric encrypted.

enable admin password { [0]password | 7 encrypted-password }

0 indicates that an unencrypted key will follow.

password is a string with 31 characters at most, which can contain only English letters (case-sensitive), digits and 17 kinds of special characters. The special characters are !\$%'()*,-./[]_{}.

7 indicates that a symmetric encrypted key with a fixed length will follow. By default, the encryption type is 0.

encrypted-password is a symmetric encrypted key with a fixed length, which you can copy from the configuration file of another switch. The key or encrypted-key you configured here will be displayed in the encrypted form.

Use the following command to create an enable password unencrypted or MD5 encrypted.

enable admin secret { [0] password | 5 encrypted-password }

0 indicates that an unencrypted key will follow.

password is a string with 31 characters at most, which can contain only English letters (case-sensitive), digits and 17 kinds of special characters. The special characters are !\$%'()*,-./□_{}.

5 indicates that an MD5 encrypted password with fixed length will follow. By default, the encryption type is 0.

encrypted-password is an MD5 encrypted password with fixed length, which you can copy from another switch's configuration file.

Step 3 end

Return to privileged EXEC mode.

Step 4 copy running-config startup-config

Save the settings in the configuration file.

On the Server

The accounts created by the RADIUS/TACACS+ server can only view the configurations and some network information without the Enable password.

Some configuration principles on the server are as follows:

■ For Login authentication configuration, more than one login account can be created on the server. Besides, both the user name and password can be customized.

■ For Enable password configuration:

On RADIUS server, the user name should be set as \enable\, and the Enable password is customizable. All the users trying to get administrative privileges share this Enable password.

On TACACS+ server, configure the value of "enable 15" as the Enable password in the configuration file. All the users trying to get administrative privileges share this Enable password.

Tips: The logged-in guests can get administrative privileges by using the command enable-admin and providing the Enable password.

3 Configuration Example

3.1 Network Requirements

As shown below, the switch needs to be managed remotely via Telnet. In addition, the senior administrator of the company wants to create an account for the less senior administrators, who can only view the configurations and some network information without the Enable password provided.

Two RADIUS servers are deployed in the network to provide a safer authenticate method for the administrators trying to log in or get administrative privileges. If RADIUS Server 1 breaks down and doesn't respond to the authentication request, RADIUS Server 2 will work, so as to ensure the stability of the authentication system.

Figure 3-1 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph LR
    A["Computer"] --> B["Management Network"]
    B --> C["Switch Administrator"]
    C --> D["RADIUS Server 1\n192.168.0.10/24\nAuth Port:1812"]
    C --> E["RADIUS Server 2\n192.168.0.20/24\nAuth Port:1812"]

3.2 Configuration Scheme

To implement this requirement, the senior administrator can create the login account and the Enable password on the two RADIUS servers, and configure the AAA feature on the switch. The IP addresses of the two RADIUS servers are 192.168.0.10/24 and 192.168.0.20/24; the authentication port number is 1812; the shared key is 123456.

The overview of configuration on the switch is as follows:

1) Add the two RADIUS servers on the switch.
2) Create a new RADIUS server group and add the two servers to the group. Make sure that RADIUS Server 1 is the first server for authentication.
3) Configure the method list.
4) Configure the AAA application list.

Demonstrated with T1600G-52TS, the following sections provide configuration procedure in two ways: using the GUI and using the CLI.

3.3 Using the GUI

1) Choose the menu SECURITY > AAA > RADIUS Config and click Add to load the following page. Configure the Server IP as 192.168.0.10, the Shared Key as 123456, the Authentication Port as 1812, and keep the other parameters as default. Click Create to add RADIUS Server 1 on the switch.

Figure 3-2 Add RADIUS Server 1

RADIUS Server

Server IP:

192.168.0.10

Shared Key:

123456

Authentication Port:

1812

Accounting Port:

1813

Retransmit:

2

Timeout:

5

NAS Identifier:

(Format:192.168.0.1)

1-32 characters. Only numbers, letters and the following symbols are allowed: - . / : @ _.

(1-65535)

(1-65535)

(1-3)

seconds (1-9)

(Optional)

Cancel

Create

2) On the same page, click Add to load the following page. Configure the Server IP as 192.168.0.20, the Shared Key as 123456, the Auth Port as 1812, and keep the other parameters as default. Click Create to add RADIUS Server 2 on the switch

Figure 3-3 Add RADIUS Server 2

RADIUS Server

Server IP:

192.168.0.20

Shared Key:

123456

Authentication Port:

1812

Accounting Port:

1813

Retransmit:

2

Timeout:

5

NAS Identifier:

(Format:192.168.0.1)

1-32 characters. Only numbers, letters and the following symbols are allowed: - . / : @ _.

(1-65535)

(1-65535)

(1-3)

seconds (1-9)

(Optional)

Cancel

Create

3) Choose the menu SECURITY > AAA > Server Group to load the following page. Click Add. Specify the group name as RADIUS1 and the server type as RADIUS. Select 192.168.0.10 and 192.168.0.20 to from the drop-down list. Click Create to create the server group.

Figure 3-4 Create Server Group
TP-LINK Omada TL-SG2008P - RADIUS Server - 1

text_image Server Group Server Group: RADIUS1 (1-15 characters) Server Type: RADIUS Server IP: 192.168.0.10,192.168.0. Cancel Create

4) Choose the menu SECURITY > AAA > Method List and click Add in the Authentication Login Method List section. Specify the Method List Name as MethodLogin and select the Pri1 as RADIUS1. Click Create to set the method list for the Login authentication.

Figure 3-5 Configure Login Method List
TP-LINK Omada TL-SG2008P - RADIUS Server - 2

text_image Authentication Login Method Method List Name: MethodLogin (1-15 characters) Pri1: RADIUS1 Pri2: -- Pri3: -- Pri4: -- Cancel Create

5) On the same page, click + Add in the Authentication Eanble Method List section. Specify the Method List Name as MethodEnable and select the Pri1 as RADIUS1. Click Create to set the method list for the Enable password authentication.

Figure 3-6 Configure Enable Method List
TP-LINK Omada TL-SG2008P - RADIUS Server - 3

text_image Authentication Enable Method Method List Name: MethodEnable (1-15 characters) Pri1: RADIUS1 Pri2: -- Pri3: -- Pri4: -- Cancel Create

6) Choose the menu SECURITY > AAA > Global Config to load the following page. In the AAA Application List section, select telnet and configure the Login List as Method-Login and Enable List as Method-Enable. Then click Apply.

Figure 3-7 Configure AAA Application List
TP-LINK Omada TL-SG2008P - RADIUS Server - 4

text_image AAA Application List Index Module Login List Enable List MethodLogin MethodEnable ✓ 1 telnet Default Protein 2 ssh Water default default 3 http default default Total: 3 1 entry selected. Cancel Apply

7) Click Save the settings.

3.4 Using the CLI

1) Add RADIUS Server 1 and RADIUS Server 2 on the switch.

Switch(config)#radius-server host 192.168.0.10 auth-port 1812 key 123456

Switch(config)#radius-server host 192.168.0.20 auth-port 1812 key 123456

2) Create a new server group named RADIUS1 and add the two RADIUS servers to the server group.

Switch(config)#aaa group radius RADIUS1

Switch(aaa-group)#server 192.168.0.10

Switch(aaa-group)#server 192.168.0.20

Switch(aaa-group)#exit

3) Create two method lists: Method-Login and Method-Enable, and configure the server group RADIUS1 as the authentication method for the two method lists.

Switch(config)#aaa authentication login Method-Login RADIUS1

Switch(config)#aaa authentication enable Method-Enable RADIUS1

4) Configure Method-Login and Method-Enable as the authentication method for the Telnet application.

Switch(config)#line telnet

Switch(config-line)#login authentication Method-Login

Switch(config-line)#enable authentication Method-Enable

Switch(config-line)#end

Switch#copy running-config startup-config

Verify the Configuration

Verify the configuration of the RADIUS servers:

Switch#show radius-server

Server IpAuth PortAcct PortTimeoutRetransmitNAS IdentifierShared key
192.168.0.101812181352000AEB132397123456
192.168.0.201812181352000AEB132397123456

Verify the configuration of server group RADIUS1:

Switch#show aaa group RADIUS1

192.168.0.10

192.168.0.20

Verify the configuration of the method lists:

Switch#show aaa authentication

Authentication Login Methodist:

Methodlistpri1pri2pri3pri4
defaultlocal------
Method-LoginRADIUS1------

Authentication Enable Methodist:

Methodlistpri1pri2pri3pri4

default none -- -- --

Method-Enable RADIUS1 -- -- --

...

Verify the status of the AAA feature and the configuration of the AAA application list:

Switch#show aaa global

Module Login List Enable List

Telnet Method-Login Method-Enable

SSH default default

Http default default

4 Appendix: Default Parameters

Default settings of AAA are listed in the following tables.

Table 4-1 AAA

Parameter Default Setting
Global Config
AAA Feature Enabled
RADIUS Config
Server IP None
Shared Key None
Auth Port 1812
Acct Port 1813
Retransmit 2
Timeout 5 seconds
NAS Identifier The MAC address of the switch.
TACACS+ Config
Server IP None
Timeout 5 seconds
Shared Key None
Port 49
Server Group: There are two default server groups: radius and tacacs.
Method List
Authentication Login Method ListList name: defaultPri1: local
Authentication Enable Method ListList name: defaultPri1: none
AAA Application List
consoleLogin List: defaultEnable List: default
telnetLogin List: defaultEnable List: default
sshLogin List: defaultEnable List: default
httpLogin List: defaultEnable List: default

Part 25

Configuring 802.1x

CHAPTERS

  1. Overview
  2. 802.1x Configuration
  3. Configuration Example
  4. Appendix: Default Parameters

1 Overview

802.1x protocol is a protocol for port-based Network Access Control. It is used to authenticate and control access from devices connected to the ports. If the device connected to the port is authenticated by the authentication server successfully, its request to access the LAN will be accepted; if not, its request will be denied.
802.1x authentication uses client-server model which contains three device roles: client/supplicant, authenticator and authentication server. This is described in the figure below:

Figure 1-1 802.1x Authentication Model
TP-LINK Omada TL-SG2008P - Overview - 1

flowchart
graph LR
    A["Clients"] --> B["Switch Authenticator"]
    B --> C["Authentication Server"]

■ Client

A client, usually a computer, is connected to the authenticator via a physical port. We recommend that you install TP-Link 802.1x authentication client software on the client hosts, enabling them to request 802.1x authentication to access the LAN.

- Authenticator

An authenticator is usually a network device that supports 802.1x protocol. As the above figure shows, the switch is an authenticator.

The authenticator acts as an intermediate proxy between the client and the authentication server. The authenticator requests user information from the client and sends it to the authentication server; also, the authenticator obtains responses from the authentication server and send them to the client. The authenticator allows authenticated clients to access the LAN through the connected ports but denies the unauthenticated clients.

■ Authentication Server

The authentication server is usually the host running the RADIUS server program. It stores information of clients, confirms whether a client is legal and informs the authenticator whether a client is authenticated.

2 802.1x Configuration

To complete the 802.1x configuration, follow these steps:

1) Configure the RADIUS server.
2) Configure 802.1x globally.
3) Configure 802.1x on ports.

In addition, you can view the authenticator state.

Configuration Guidelines

802.1x authentication and Port Security cannot be enabled at the same time. Before enabling 802.1x authentication, make sure that Port Security is disabled.

2.1 Using the GUI

2.1.1 Configuring the RADIUS Server

Configure the parameters of RADIUS sever and configure the RADIUS server group.

■ Adding the RADIUS Server

Choose the menu SECURITY > AAA > RADIUS Config and click + Add to load the following page.

Figure 2-1 Adding RADIUS Server
TP-LINK Omada TL-SG2008P - Configuring the RADIUS Server - 1

text_image RADIUS Server Server IP: (Format:192.168.0.1) Shared Key: 1-32 characters. Only numbers, letters and the following symbols are allowed: - . / : @ _ . Authentication Port: 1812 (1-65535) Accounting Port: 1813 (1-65535) Retransmit: 2 (1-3) Timeout: 5 seconds (1-9) NAS Identifier: (Optional) Cancel Create

Follow these steps to add a RADIUS server:

1) Configure the parameters of the RADIUS server.

Server IP Enter the IP address of the server running the RADIUS secure protocol.
Shared Key Enter the shared key between the RADIUS server and the switch. The RADIUS server and the switch use the key string to encrypt passwords and exchange responses.
Authentication PortSpecify the UDP destination port on the RADIUS server for authentication requests. The default setting is 1812.
Accounting PortSpecify the UDP destination port on the RADIUS server for accounting requests. The default setting is 1813.
RetransmitSpecify the number of times a request is resent to the server if the server does not respond. The default setting is 2.
Timeout Specify the time interval that the switch waits for the server to reply before resending. The default setting is 5 seconds.
NAS IdentifierSpecify the name of the NAS (Network Access Server) to be contained in RADIUS packets for identification. It ranges from 1 to 31 characters. The default value is the MAC address of the switch. Generally, the NAS indicates the switch itself.

2) Click Apply.

■ Configuring the RADIUS Server Group

Choose the menu SECURITY > AAA > Server Group to load the following page.

Figure 2-2 Adding a Server Group
TP-LINK Omada TL-SG2008P - ■ Configuring the RADIUS Server Group - 1

text_image Server Group List ID Server Group Server Type Server IP Operation 1 radius RADIUS ✓ ✓ ✓ 2 tacacs TACACS+ Total: 2

Follow these steps to add the RADIUS server to a server group:

1) Click ☑ to edit the default radius server group or click + Add to add a new server group.

If you click √, the following window will pop up. Select a RADIUS server and click Save.

Figure 2-3 Editing Server Group
TP-LINK Omada TL-SG2008P - ■ Configuring the RADIUS Server Group - 2

text_image Server Group Server Group: radius Server Type: RADIUS Server IP: 192 168.0.99 Cancel Save

If you click , the following window will pop up. Specify a name for the server group, select the server type as RADIUS and select the IP address of the RADIUS server. Click Save.

Figure 2-4 Adding Server Group
TP-LINK Omada TL-SG2008P - ■ Configuring the RADIUS Server Group - 3

text_image Server Group Server Group: (1-15 characters) Server Type: RADIUS Server IP: 192.168.0.99 Cancel Create

■ Configuring the Dot1x List

Choose the menu SECURITY > AAA > Dot1x List to load the following page.

Figure 2-5 Configuring the Dot1x List
TP-LINK Omada TL-SG2008P - ■ Configuring the RADIUS Server Group - 4

text_image Authentication Dot1x Method Method List: default Pri1: radius Accounting Dot1x Method Method List: default Pri1: radius Apply Apply

Follow these steps to configure RADIUS server groups for 802.1x authentication and accounting:

1) In the Authentication Dot1x Method section, select an existing RADIUS server group for authentication from the Pri1 drop-down list and click Apply.

2) In the Accounting Dot1x Method section, select an existing RADIUS server group for accounting from the Pri1 drop-down list and click Apply.

2.1.2 Configuring 802.1x Globally

Choose the menu SECURITY > 802.1x > Global Config to load the following page.

Figure 2-6 Global Config
TP-LINK Omada TL-SG2008P - Configuring 802.1x Globally - 1

text_image Global Config 802.1x: Enable Authentication EAP Protocol: Accounting: Enable Handshake: Enable VLAN Assignment: Enable Apply

Follow these steps to configure 802.1x global parameters:

1) In the Global Config section, configure the following parameters.

802.1x Enable or disable 802.1x globally.

Auth Protocol Select the 802.1x authentication protocol.

PAP: The 802.1x authentication system uses EAP packets to exchange information between the switch and the client. The transmission of EAP (Extensible Authentication Protocol) packets is terminated at the switch and the EAP packets are converted to other protocol (such as RADIUS) packets, and transmitted to the authentication server.

EAP: The 802.1x authentication system uses EAP packets to exchange information between the switch and the client. The EAP packets with authentication data are encapsulated in the advanced protocol (such as RADIUS) packets, and transmitted to the authentication server.

Accounting Enable or disable 802.1x accounting feature.

Handshake Enable or disable the Handshake feature. The Handshake feature is used to detect the connection status between the TP-Link 802.1x Client and the switch. Please disable Handshake feature if you are using other client softwares instead of TP-Link 802.1x Client.

VLANAssignmentEnable or disable the 802.1x VLAN assignment feature. 802.1x VLAN assignment is a technology allowing the RADIUS server to send the VLAN assignment to the port when the port is authenticated.If the assigned VLAN does not exist on the switch, the switch will create the related VLAN automatically, add the authenticated port to the VLAN and change the PVID based on the assigned VLAN.If the assigned VLAN exists on the switch, the switch will directly add the authenticated port to the related VLAN and change the PVID instead of creating a new VLAN.If no VLAN is supplied by the RADIUS server or if 802.1x authentication is disabled, the port will be in its original VLAN after successful authentication.

2) Click Apply.

2.1.3 Configuring 802.1x on Ports

Choose the menu SECURITY > 802.1x > Port Config to load the following page.

Figure 2-7 Port Config

Port Config
UNIT1
PortStatusMABGuest VLAN (0-4094)Port ControlPort MethodMaximum Request (1-9)Quiet Period (0-999)Supplicant Timeout (1-60)
1/0/1DisableDisable0AutoMAC Based31030
1/0/2DisableDisable0AutoMAC Based31030
1/0/3DisableDisable0AutoMAC Based31030
1/0/4DisableDisable0AutoMAC Based31030
1/0/5DisableDisable0AutoMAC Based31030
1/0/6DisableDisable0AutoMAC Based31030
1/0/7DisableDisable0AutoMAC Based31030
1/0/8DisableDisable0AutoMAC Based31030
1/0/9DisableDisable0AutoMAC Based31030
1/0/10DisableDisable0AutoMAC Based31030

Follow these steps to configure 802.1x authentication on the desired port:

1) Select one or more ports and configure the following parameters:

Status Enable 802.1x authentication on the port.

MAB Select whether to enable the MAB (MAC-Based Authentication Bypass) feature for the port.
With MAB feature enabled, the switch automatically sends the authentication server a RADIUS access request frame with the client's MAC address as the username and password. It is also necessary to configure the RADIUS server with the client's information for authentication. You can enable this feature on IEEE 802.1x ports connected to devices without 802.1x capability. For example, most printers, IP phones and fax machines do not have 802.1x capability.
Note: MAB cannot work if Guest VLAN is enabled.
Guest VLANSpecify a Guest VLAN ID. 0 means that Guest VLAN is disabled. The configured VLAN must be an existing 802.1Q VLAN.
With Guest VLAN enabled, a port can access resources in the guest VLAN even though the port is not yet authenticated; if guest VLAN is disabled and the port is not authenticated, the port cannot visit any resource in the LAN.
Port Control Select the control mode for the port. By default, it is Auto.
Auto: If this option is selected, the port can access the network only when it is authenticated.
Force-Authorized: If this option is selected, the port can access the network without authentication.
Force-Unauthorized: If this option is selected, the port can never be authenticated.
Port Method Select the port method. By default, it is MAC Based.
MAC Based: All clients connected to the port need to be authenticated.
Port Based: If a client connected to the port is authenticated, other clients can access the LAN without authentication.
Maximum Request (1-9)Specify the maximum number of attempts to send the authentication packet. It ranges from 1 to 9 times and the default is 3 times.
Quiet Period (1-999)Specify the Quiet Period. It ranges from 1 to 999 seconds and the default time is 10 seconds.
The quiet period starts after the authentication fails. During the quiet period, the switch does not process authentication requests from the same client.
Supplicant Timeout (1-60)Specify the maximum time which the switch waits for a response from the client. It ranges from 1 to 60 seconds and the default time is 30 seconds.
If the switch does not receive any reply from the client within the specified time, it will resend the request.
Authorized Displays whether the port is authorized or not.
LAG Displays the LAG the port belongs to.

2) Click Apply.

TP-LINK Omada TL-SG2008P - Configuring 802.1x on Ports - 1

Note:

If a port is in an LAG, its 802.1x authentication function cannot be enabled. Also, a port with 802.1x authentication enabled cannot be added to any LAG.

2.1.4 View the Authenticator State

Choose the menu SECURITY > 802.1x > Authenticator State to load the following page.

Figure 2-8 View Authenticator State
TP-LINK Omada TL-SG2008P - View the Authenticator State - 1

text_image Authenticator State Port: Search UNIT1 ID Port MAC Address PAE State Backend State Status VID ✓ 1 1/0/1 N/A Disconnected IDle Unauthorized 1 □ 2 1/0/2 N/A Disconnected(Idle Unauthorized 1 □ 3 1/0/3 N/A Disconnected(Idle Unauthorized 1 □ 4 1/0/4 N/A Disconnected(Idle Unauthorized 1 □ 5 1/0/5 N/A Disconnected(Idle Unauthorized 1 □ 6 1/0/6 N/A Disconnected(Idle Unauthorized 1 □ 7 1/0/7 N/A Disconnected(Idle Unauthorized 1 □ 8 1/0/8 N/A Disconnected(Idle Unauthorized 1 □ 9 1/0/9 N/A Disconnected(Idle Unauthorized 1 □ 10 1/0/10 N/A Disconnected(Idle Unauthorized 1 Total: 28 1 entry selected.

On this page, you can view the authentication status of each port:

Port Displays the port number.

MAC AddressDisplays the MAC address of the authenticated device. When the port method is Port Based, the MAC address of the first authenticated device wil be displayed with a suffix "p".
PAE StateDisplays the current state of the authenticator PAE state machine. Possible values are: Initialize, Disconnected, Connecting, Authenticating, Authenticated, Aborting, Held, ForceAuthorized and ForceUnauthorized.
Backend StateDisplays the current state of the backend authentication state machine. Possible values are: Request, Response, Success, Fail, Timeout, Initialize and Idle.
Status Displays whether the port is authorized or not.
VID Displays the VLAN ID assigned by the authenticator to the supplicant device when the related port is authorized. If the related port is unauthorized and there is a Guest VLAN ID, the Guest VLAN ID will be displayed.

2.2 Using the CLI

2.2.1 Configuring the RADIUS Server

Follow these steps to configure RADIUS:

Step 1 configure

Enter global configuration mode.

Step 2 radius-server host

ip-address [auth-port port-id] [acct-port port-id] [timeout time] [

retransmit number ] [nas-id nas-id] key { [0] string | 7 encrypted-string }

Add the RADIUS server and configure the related parameters as needed.

hostip-address: Enter the IP address of the server running the RADIUS protocol.

auth-port port-id: Specify the UDP destination port on the RADIUS server for authentication requests. The default setting is 1812.

acct-port port-id: Specify the UDP destination port on the RADIUS server for accounting requests. The default setting is 1813. Generally, the accounting feature is not used in the authentication account management.

timeout time: Specify the time interval that the switch waits for the server to reply before resending. The valid values are from 1 to 9 seconds and the default setting is 5 seconds.

retransmit number. Specify the number of times a request is resent to the server if the server does not respond. The valid values are from 1 to 3 and the default setting is 2.

nas-id nas-id: Specify the name of the NAS (Network Access Server) to be contained in RADIUS packets for identification. It ranges from 1 to 31 characters. The default value is the MAC address of the switch. Generally, the NAS indicates the switch itself.

key { [0] string | 7 encrypted-string }: Specify the shared key. 0 and 7 prevent the encryption type. 0 indicates that an unencrypted key will follow. 7 indicates that a symmetric encrypted key with a fixed length will follow. By default, the encryption type is 0. string is the shared key for the switch and the server. encrypted-string is a symmetric encrypted key with a fixed length, which you can copy from the configuration file of another switch. The key or encrypted-key you configured here will be displayed in the encrypted form.

Step 3 aaa group radius

group-name

Create a RADIUS server group.

radius: Specify the group type as radius.

group-name: Specify a name for the group.

Step 4 server

ip-address

Add the existing servers to the server group.

ip-address: Specify IP address of the server to be added to the group.

Step 5 exit

Return to global configuration mode.

Step 6 aaa authentication dot1x default { method}Select the RADIUS group for 802.1x authentication.method: Specify the RADIUS group for 802.1x authentication.aaa accounting dot1x default { method}Select the RADIUS group for 802.1x accounting.method: Specify the RADIUS group for 802.1x accounting.Note: If multiple RADIUS servers are available, you are suggested to add them to different server groups respectively for authentication and accounting.
Step 7 show radius-server(Optional) Verify the configuration of RADIUS server.
Step 8 show aaa group [ group-name ](Optional) Verify the configuration of server group.
Step 9 show aaa authentication dot1x(Optional) Verify the authentication method list.
Step 10 show aaa accounting dot1x(Optional) Verify the accounting method list.
Step 11 endReturn to privileged EXEC mode.
Step 12 copy running-config startup-configSave the settings in the configuration file.

The following example shows how to enable AAA, add a RADIUS server to the server group named radius1, and apply this server group to the 802.1x authentication. The IP address of the RADIUS server is 192.168.0.100; the shared key is 123456; the authentication port is 1812; the accounting port is 1813.

Switch#configure

Switch(config)#radius-server host 192.168.0.100 auth-port 1812 acct-port 1813 key 123456

Switch(config)#aaa group radius radius1

Switch(aaa-group)#server 192.168.0.100

Switch(aaa-group)#exit

Switch(config)#aaa authentication dot1x default radius1

Switch(config)#aaa accounting dot1x default radius1

Switch(config)#show radius-server

Server IpAuth PortAcct PortTimeoutRetransmitNAS IdentifierShared key
192.168.0.1001812181352000AEB132397123456

Switch(config)#show aaa group radius1

192.168.0.100

Switch(config)#show aaa authentication dot1x

Methodlistpri1pri2pri3pri4
defaultradius1------

Switch(config)#show aaa accounting dot1x

Methodlistpri1pri2pri3pri4
defaultradius1------

Switch(config)#end

Switch#copy running-config startup-config

2.2.2 Configuring 802.1x Globally

Follow these steps to configure 802.1x globally:

Step 1 configure

Enter global configuration mode.

Step 2 dot1x system-auth-control

Enable 802.1x authentication globally.

Step 3 dot1x auth-protocol {pap | eap}

Configure the 802.1x authentication protocol.

pap: Specify the authentication protocol as PAP. If this option is selected, the 802.1x authentication system uses EAP (Extensible Authentication Protocol) packets to exchange information between the switch and the client. The transmission of EAP packets is terminated at the switch and the EAP packets are converted to other protocol (such as RADIUS) packets, and transmitted to the authentication server.

eap: Specify the authentication protocol as EAP. If this option is selected, the 802.1x authentication system uses EAP packets to exchange information between the switch and the client. The EAP packets with authentication data are encapsulated in the advanced protocol (such as RADIUS) packets, and transmitted to the authentication server.

Step 4 dot1x accounting

(Optional) Enable the accounting feature.

Step 5 dot1x handshake

(Optional) Enable the Handshake feature. The Handshake feature is used to detect the connection status between the TP-Link 802.1x Client and the switch. Please disable Handshake feature if you are using other client softwares instead of TP-Link 802.1x Client.

Step 6 dot1x vlan-assignment

(Optional) Enable or disable the 802.1x VLAN assignment feature. 802.1x VLAN assignment is a technology allowing the RADIUS server to send the VLAN assignment to the port when the port is authenticated.

If the assigned VLAN does not exist on the switch, the switch will create the related VLAN automatically, add the authenticated port to the VLAN and change the PVID based on the assigned VLAN.

If the assigned VLAN exists on the switch, the switch will directly add the authenticated port to the related VLAN and change the PVID instead of creating a new VLAN.

If no VLAN is supplied by the RADIUS server or if 802.1x authentication is disabled, the port will be in its original VLAN after successful authentication.

Step 7 show dot1x global

(Optional) Verify global configurations of 802.1x.

Step 8 end

Return to privileged EXEC mode.

Step 9 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable 802.1x authentication, configure PAP as the authentication method and keep other parameters as default:

Switch#configure

Switch(config)#dot1x system-auth-control

Switch(config)#dot1x auth-protocol pap

Switch(config)#show dot1x global

802.1X State: Enabled

Authentication Protocol: PAP

Handshake State: Enabled

802.1X Accounting State: Disabled

802.1X VLAN Assignment State: Disabled

Switch(config)#end

Switch#copy running-config startup-config

2.2.3 Configuring 802.1x on Ports

Follow these steps to configure the port:

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet

port | range fastEthernet port-list | gigabitEthernet port | range

gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list }

Enter interface configuration mode.

port: Enter the ID of the port to be configured.

Step 3 dot1x

Enable 802.1x authentication for the port.

Step 4 dot1x mab

Enable the MAB (MAC-Based Authentication Bypass) feature for the port.

With MAB feature enabled, the switch automatically sends the authentication server a RADIUS access request frame with the client's MAC address as the username and password. It is also necessary to configure the RADIUS server with the client's information for authentication. You can enable this feature on IEEE 802.1x ports connected to devices without 802.1x capability. For example, most printers, IP phones and fax machines do not have 802.1x capability.

Note: MAB cannot work if Guest VLAN is enabled.

Step 5 dot1x guest-vlanvid(Optional) Configure guest VLAN on the port.
vid: Specify the ID of the VLAN to be configured as the guest VLAN. The valid values are from 0 to 4094. 0 means that Guest VLAN is disabled on the port. The configured VLAN must be an existing 802.1Q VLAN. Clients in the guest VLAN can only access resources from specific VLANs.
Note: To use Guest VLAN, the control type of the port should be configured as port-based.
Step 6dot1x port-control { auto | authorized-force | unauthorized-force }Configure the control mode for the port. By default, it is auto.auto: If this option is selected, the port can access the network only when it is authenticated.authorized-force: If this option is selected, the port can access the network without authentication.unauthorized-force: If this option is selected, the port can never be authenticated.
Step 7 dot1x port-method { mac-based | port-based }Configure the control type for the port. By default, it is mac-based.mac-based: All clients connected to the port need to be authenticated.port-based: If a client connected to the port is authenticated, other clients can access the LAN without authentication.
Step 8 dot1x max-reqtimesSpecify the maximum number of attempts to send the authentication packet for the client.times: The maximum attempts for the client to send the authentication packet. It ranges from 1 to 9 and the default is 3.
Step 9 dot1x quiet-period [time](Optional) Enable the quiet feature for 802.1x authentication and configure the quiet period.time: Set a value between 1 and 999 seconds for the quiet period. It is 10 seconds by default. The quiet period starts after the authentication fails. During the quiet period, the switch does not process authentication requests from the same client.
Step 10 dot1x timeout supp-timeouttimeConfigure the supplicant timeout period.time: Specify the maximum time for which the switch waits for response from the client. It ranges from 1 to 60 seconds and the default time is 30 seconds. If the switch does not receive any reply from the client within the specified time, it will resend the request.
Step 11 show dot1x interface [fastEthernet port |gigabitEthernet port | ten-gigabitEthernet port](Optional) Verify the configurations of 802.1x authentication on the port.port: Enter the ID of the port to be configured. If no specific port is entered, the switch will show configurations of all ports.

Step 12 end

Return to privileged EXEC mode.

Step 13 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable 802.1x authentication on port 1/0/2, configure the control type as port-based, and keep other parameters as default:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/2

Switch(config-if)#dot1x

Switch(config-if)#dot1x port-method port-based

Switch(config-if)#show dot1x interface gigabitEthernet 1/0/2

PortStateMAB StateGuestVLANPortControlPortMethod
------------------------
Gi1/0/2disableddisabled0autoport-based
MaxReqQuietPeriodSuppTimeoutAuthorizedLAG
-------------------
31030unauthorizedN/A

Switch(config-if)#end

Switch#copy running-config startup-config

2.2.4 Viewing Authenticator State

You can view the authenticator state. If needed, you can also initialize or reauthenticate the specific client:

Step 1 show dot1x auth-state interface [fastEthernet gigabitEthernet port] port | gigabitEthernet port | ten-

Displays the authenticator state.

Step 2 configure

Enter global configuration mode.

Step 3 interface {fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list}

Enter interface configuration mode.

port: Enter the ID of the port to be configured.

Step 4 dot1x auth-init [ mac mac-address ]

Initialize the specific client. To access the network, the client needs to provide the correct information to pass the authentication again.

mac-address: Enter the MAC address of the client that will be unauthorized.

Step 5 dot1x auth-reauth [ mac mac-address ]

Reauthenticate the specific client.

mac-address: Enter the MAC address of the client that will be reauthenticated.

Step 6 end

Return to privileged EXEC mode.

Step 7 copy running-config startup-config

Save the settings in the configuration file.

3 Configuration Example

3.1 Network Requirements

The network administrator wants to control access from the end users (clients) in the company. It is required that all clients need to be authenticated separately and only the authenticated clients can access the internet.

3.2 Configuration Scheme

■ To authenticate clients separately, enable 802.1x authentication, configure the control mode as auto, and set the control type as MAC based.
■ Enable 802.1x authentication on the ports connected to clients.
- Keep 802.1x authentication disabled on ports connected to the authentication server and the internet, which ensures unrestricted connections between the switch and the authentication server or the internet.

3.3 Network Topology

As shown in the following figure, Switch A acts as the authenticator. Port 1/0/1 is connected to the client, port 1/0/2 is connected to the RADIUS server, and port 1/0/3 is connected to the internet.

Figure 3-1 Network Topology
TP-LINK Omada TL-SG2008P - Network Topology - 1

flowchart
graph TD
    A["Internet"] --> B["Switch A Authenticator"]
    B --> C["RADIUS Server 192.168.0.10/24\nAuth Port:1812"]
    B --> D["Client Client"]
    B --> E["Client"]
    B --> F["Client"]
    B --> G["Client"]
    B --> H["Client"]
    B --> I["Client"]
    B --> J["Client"]
    B --> K["Client"]
    B --> L["Client"]
    B --> M["Client"]
    B --> N["Client"]
    B --> O["Client"]
    B --> P["Client"]
    B --> Q["Client"]
    B --> R["Client"]
    B --> S["Client"]
    B --> T["Client"]
    B --> U["Client"]
    B --> V["Client"]
    B --> W["Client"]
    B --> X["Client"]
    B --> Y["Client"]
    B --> Z["Client"]
    B --> AA["Client"]
    B --> AB["Client"]
    B --> AC["Client"]
    B --> AD["Client"]
    B --> AE["Client"]
    B --> AF["Client"]
    B --> AG["Client"]
    B --> AH["Client"]
    B --> AI["Client"]
    B --> AJ["Client"]
    B --> AK["Client"]
    B --> AL["Client"]
    B --> AM["Client"]
    B --> AN["Client"]
    B --> AO["Client"]
    B --> AP["Client"]
    B --> AQ["Client"]
    B --> AR["Client"]

Demonstrated with T1600G-52TS acting as the authenticator, the following sections provide configuration procedure in two ways: using the GUI and using the CLI.

3.4 Using the GUI

1) Choose the menu SECURITY > AAA > RADIUS Config and click + Add to load the following page. Configure the parameters of the RADIUS server and click Create.

Figure 3-2 Adding RADIUS Server
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image RADIUS Server Server IP: 192.168.0.10 (Format:192.168.0.1) Shared Key: 123456 1-32 characters. Only numbers, letters and the following symbols are allowed: - . / : @ _ . Authentication Port: 1812 (1-65535) Accounting Port: 1813 (1-65535) Retransmit: 2 (1-3) Timeout: 5 seconds (1-9) NAS Identifier: (Optional) Cancel Create

2) Choose the menu SECURITY > AAA > Server Group and click + Add to load the following page. Specify the group name as RADIUS1, select the server type as RADIUS and server IP as 192.168.0.10. Click Create.

Figure 3-3 Creating Server Group
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image Server Group Server Group: RADIUS1 (1-15 characters) Server Type: RADIUS Server IP: 192.168.0.10 Cancel Create

3) Choose the menu SECURITY > AAA > Dot1x List to load the following page. In the Authentication Dot1x Method section, select RADIUS1 as the RADIUS server group for authentication, and click Apply.

Figure 3-4 Configuring Authentication RADIUS Server
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image Authentication Dot1x Method Method List: default Pri1: RADIUS1 Apply

4) Choose the menu SECURITY > 802.1x > Global Config to load the following page. Enable 802.1x authentication and configure the Authentication Method as EAP. Keep the default authentication settings. Click Apply.

Figure 3-5 Configuring Global Settings
TP-LINK Omada TL-SG2008P - Using the GUI - 4

text_image Global Config 802.1x: ✓ Enable Authentication Protocol: EAP Accounting: □ Enable Handshake: ✓ Enable VLAN Assignment: □ Enable Apply

5) Choose the menu SECURITY > 802.1x > Port Config to load the following page. For port 1/0/1, enable 802.1x authentication, set the Control Mode as auto and set the Control Type as MAC Based; For port 1/0/2 and port 1/0/3, disable 802.1x authentication.

Figure 3-6 Configuring Port
TP-LINK Omada TL-SG2008P - Using the GUI - 5

text_image Port Config UNIT1 ID Port Status MAB Guest VLAN (0-4094) Port Control Port Method Maximum Request (1-9) Quiet Period (1-999) Suppl Time (1- Enabl ✓ 1 1/0/1 Enable Disable 0 Auto MAC Based 3 10 3 □ 2 1/0/2 Disable Disable 0 Auto MAC Based 3 10 3 □ 3 1/0/3 Disable Disable 0 Auto MAC Based 3 10 3 □ 4 1/0/4 Disable Disable 0 Auto MAC Based 3 10 3 □ 5 1/0/5 Disable Disable 0 Auto MAC Based 3 10 3 □ 6 1/0/6 Disable Disable 0 Auto MAC Based 3 10 3 □ 7 1/0/7 Disable Disable 0 Auto MAC Based 3 10 3 □ 8 1/0/8 Disable Disable 0 Auto MAC Based 3 10 3 □ 9 1/0/9 Disable Disable 0 Auto MAC Based 3 10 3 □ 10 1/0/10 Disable Disable 0 Auto MAC Based 3 10 3 Total: 28 1 entry selected. Cancel Apply

6) Click Save the settings.

3.5 Using the CLI

1) Configure the RADIUS parameters.

Switch_A(config)#radius-server host 192.168.0.10 auth-port 1812 key 123456

Switch_A(config)#aaa group radius RADIUS1

Switch_A(aaa-group)#server 192.168.0.10

Switch_A(aaa-group)#exit

Switch_A(config)#aaa authentication dot1x default RADIUS1

2) Globally enable 802.1x authentication and set the authentication protocol.

Switch_A(config)#dot1x system-auth-control

Switch_A(config)#dot1x auth-protocol eap

3) Disable 802.1x authentication on port 1/0/2 and port 1/0/3. Enable 802.1x authentication on port 1/0/1, set the control mode as auto, and set the control type as MAC based.

Switch_A(config)#interface gigabitEthernet 1/0/2

Switch_A(config-if)#no dot1x

Switch_A(config-if)#exit

Switch_A(config)#interface gigabitEthernet 1/0/3

Switch_A(config-if)#no dot1x

Switch_A(config-if)#exit

Switch_A(config)#interface gigabitEthernet 1/0/1

Switch_A(config-if)#dot1x

Switch_A(config-if)#dot1x port-method mac-based

Switch_A(config-if)#dot1x port-control auto

Switch_A(config-if)#exit

Verify the Configurations

Verify the global configurations of 802.1x authentication:

Switch_A#show dot1x global

802.1X State: Enabled

Authentication Protocol: EAP

Handshake State: Enabled

802.1X Accounting State: Disabled

802.1X VLAN Assignment State: Disabled

Verify the configurations of 802.1x authentication on the port:

Switch_A#show dot1x interface

PortStateMAB StateGuestVLANPortControlPortMethod
------------------------
Gi1/0/1enableddisabled0automac-based
Gi1/0/2disableddisabled0automac-based
Gi1/0/3disableddisabled0automac-based
MaxReqQuietPeriodSuppTimeoutAuthorizedLAG
-------------------
31030unauthorizedN/A
31030unauthorizedN/A

3 10 30 unauthorized N/A

...

Verify the configurations of RADIUS :

Switch_A#show aaa global

ModuleLogin ListEnable List
Telnetdefaultdefault
Sshdefaultdefault
Httpdefaultdefault

Switch_A#show aaa authentication dot1x

Methodlist pri1 pri2 pri3 pri4 default RADIUS1 -- -- --

Switch_A#show aaa group RADIUS1

192.168.0.10

4 Appendix: Default Parameters

Default settings of 802.1x are listed in the following table.

Table 4-1 Default Settings of 802.1x

Parameter Default Setting
Global Config
802.1x Authentication Disabled
Authentication Method EAP
Handshake Enabled
Accounting Disabled
VLAN Assignment Disabled
Port Config
802.1x Status Disabled
MAB Disabled
Guest VLAN Disabled
Port Control Auto
Guest VLAN 0
Maximum Request3
Quiet Period10 seconds
Supplicant Timeout30 seconds
Port MethodMAC Based
Dot1X List
Authentication Dot1x Method ListList Name: defaultPri1: radius
Accounting Dot1x Method ListList Name: defaultPri1: radius

Part 26

Configuring Port Security

CHAPTERS

  1. Overview
  2. Port Security Configuration
  3. Appendix: Default Parameters

1 Overview

You can use the Port Security feature to limit the number of MAC addresses that can be learned on each port, thus preventing the MAC address table from being exhausted by the attack packets. In addition, the switch can send a notification if the number of learned MAC addresses on the port exceeds the limit.

2 Port Security Configuration

2.1 Using the GUI

Choose the menu SECURITY > Port Security to load the following page.

Figure 2-1 Port Security
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Port Security Config UNIT1 Port Max Learned Current Learned Exceed Max Learned Trap Learn Address Mode Status Number of MAC Number ✓ 1/0/1 64 0 Disable Delete on Timeout Disable □ 1/0/2 64 0 Disable Delete on Timeout Disable □ 1/0/3 64 0 Disable Delete on Timeout Disable □ 1/0/4 64 0 Disable Delete on Timeout Disable □ 1/0/5 64 0 Disable Delete on Timeout Disable □ 1/0/6 64 0 Disable Delete on Timeout Disable □ 1/0/7 64 0 Disable Delete on Timeout Disable □ 1/0/8 64 0 Disable Delete on Timeout Disable □ 1/0/9 64 0 Disable Delete on Timeout Disable □ 1/0/10 64 0 Disable Delete on Timeout Disable Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure Port Security:

1) Select one or more ports and configure the following parameters.

Port Displays the port number.
Max Learned Number of MACSpecify the maximum number of MAC addresses that can be learned on the port. When the learned MAC address number reaches the limit, the port will stop learning. It ranges from 0 to 64. The default value is 64.
Current Learned MACDisplays the current number of MAC addresses that have been learned on the port.
Exceed Max Learned TrapEnable Exceed Max Learned, and when the maximum number of learned MAC addresses on the specified port is exceeded, a notification will be generated and sent to the management host.
Learn Address ModeSelect the learn mode of the MAC addresses on the port. Three modes are provided:Delete on Timeout:The switch will delete the MAC addresses that are not used or updated within the aging time. It is the default setting.Delete on Reboot:The learned MAC addresses are out of the influence of the aging time and can only be deleted manually. The learned entries will be cleared after the switch is rebooted.Permanent:The learned MAC addresses are out of the influence of the aging time and can only be deleted manually. The learned entries will be saved even the switch is rebooted.
Status Select the status of Port Security. Three kinds of status can be selected:Drop:When the number of learned MAC addresses reaches the limit, the port will stop learning and discard the packets with the MAC addresses that have not been learned.Forward:When the number of learned MAC addresses reaches the limit, the port will stop learning but send the packets with the MAC addresses that have not been learned.Disable:The number limit on the port is not effective, and the switch follows the original forwarding rules. It is the default setting.

2) Click Apply.

TP-LINK Omada TL-SG2008P - 2) Click Apply. - 1

Note:

  • Port Security cannot be enabled on the member ports of a LAG, and the port with Port Security enabled cannot be added to a LAG.
  • On one port, Port Security and 802.1x cannot be enabled at the same time.

2.2 Using the CLI

Follow these steps to configure Port Security:

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet

port | range fastEthernet port-list | gigabitEthernet port | range

gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list}

Enter interface configuration mode.

Step 3 mac address-table max-mac-count { [max-number num] [exceed-max-learned

enable | disable] [mode { dynamic | static | permanent} ] [status { forward | drop | disable} ]

Enable the port security feature of the port and configure the related parameters.

num: The maximum number of MAC addresses that can be learned on the port. The valid values are from 0 to 64. The default value is 64.

exceed-max-learned: With exceed-max-learned enabled, when the maximum number of MAC addresses on the specified port is exceeded, a notification will be generated and sent to the management host.

enable: Enable exceed-max-learned.

disable: Disable exceed-max-learned.

mode: Learn mode of the MAC address. There are three modes:

dynamic: The switch will delete the MAC addresses that are not used or updated within the aging time.

static: The learned MAC addresses are out of the influence of the aging time and can only be deleted manually. The learned entries will be cleared after the switch is rebooted.

permanent: The learned MAC address is out of the influence of the aging time and can only be deleted manually. The learned entries will be saved even the switch is rebooted.

status: Status of port security feature. By default, it is disabled.

drop: When the number of learned MAC addresses reaches the limit, the port will stop learning and discard the packets with the MAC addresses that have not been learned.

forward: When the number of learned MAC addresses reaches the limit, the port will stop learning but send the packets with the MAC addresses that have not been learned.

disable: The number limit on the port is not effective, and the switch follows the original forwarding rules. It is the default setting.

Step 4 show mac address-table max-mac-count interface { fastEthernet port | gigabitEthernet port | ten-gigabitEthernetport}

Verify the Port Security configuration and the current learned MAC addresses of the port.

Step 5 end

Return to privileged EXEC mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

TP-LINK Omada TL-SG2008P - Step 6 copy running-config startup-config - 1

Note:

  • Port Security cannot be enabled on the member port of a LAG, and the port with Port Security enabled cannot be added to a LAG.
  • On one port, Port Security and 802.1x cannot be enabled at the same time.

The following example shows how to set the maximum number of MAC addresses that can be learned on port 1/0/1 as 30, enable exceed-max-leaned feature and configure the mode as permanent and the status as drop:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#mac address-table max-mac-count max-number 30 exceed-max-learned enable mode permanent status drop

Switch(config-if)#show mac address-table max-mac-count interface gigabitEthernet 1/0/1

PortMax-learnCurrent-learnExceed Max LimitModeStatus
------------------------
Gi1/0/1300disablepermanentdrop

Switch(config-if)#end

Switch#copy running-config startup-config

3 Appendix: Default Parameters

Default settings of Port Security are listed in the following table.

Table 3-1 Default Parameters of Port Security

Parameter Default Setting
Max Learned Number of MAC64
Current Learned Number 0
Exceed Max Learned Trap Disabled
Learn Address Mode Delete on Timeout
Status Disabled

Part 27

Configuring ACL

CHAPTERS

  1. Overview
  2. ACL Configuration
  3. Configuration Example for ACL
  4. Appendix: Default Parameters

1 Overview

ACL (Access Control List) filters traffic as it passes through a switch, and permits or denies packets crossing specified interfaces or VLANs. It accurately identifies and processes the packets based on the ACL rules. In this way, ACL helps to limit network traffic, manage network access behaviors, forward packets to specified ports and more.

To configure ACL, follow these steps:

1) Configure a time range during which the ACL is in effect.
2) Create an ACL and configure the rules to filter different packets.
3) Bind the ACL to a port or VLAN to make it effective.

Configuration Guidelines

A packet "matches" an ACL rule when it meets the rule's matching criteria. The resulting action will be either to "permit" or "deny" the packet that matches the rule.
If no ACL rule is configured, the packets will be forwarded without being processed by the ACL. If there is configured ACL rules and no matching rule is found, the packets will be dropped.

2 ACL Configuration

2.1 Using the GUI

2.1.1 Configuring Time Range

Some ACL-based services or features may need to be limited to take effect only during a specified time period. In this case, you can configure a time range for the ACL. For details about Time Range configuration, please refer to Managing System

2.1.2 Creating an ACL

You can create different types of ACL and define the rules based on source MAC or IP address, destination MAC or IP address, protocol type, port number and so on.

MAC ACL: MAC ACL uses source and destination MAC address for matching operations.

IP ACL: IP ACL uses source and destination IP address, IP protocols and so on for matching operations.

Combined ACL: Combined ACL uses source and destination MAC address, and source and destination IP address for matching operations.

IPv6 ACL: IPv6 ACL uses source and destination IPv6 address for matching operations.

Packet Content ACL: Packet Content ACL analyzes and processes data packets based on 4 chunk match conditions, each chunk can specify a user-defined 4-byte segment carried in the packet's first 128 bytes.

TP-LINK Omada TL-SG2008P - Creating an ACL - 1

Note:

Packet Content ACL is only available on certain devices.

Choose the menu SECURITY > ACL > ACL Config and click + Add to load the following page.

Figure 2-1 Creating an ACL
TP-LINK Omada TL-SG2008P - Creating an ACL - 2

text_image ACL ACL Type: MAC ACL ACL ID: (0-499) ACL Name: (Optional) Cancel Create

Follow these steps to create an ACL:

1) Choose one ACL type and enter a number to identify the ACL.
2) (Optional) Assign a name to the ACL.
3) Click Create.

TP-LINK Omada TL-SG2008P - Creating an ACL - 3

Note:

The supported ACL type and ID range varies on different switch models. Please refer to the on-screen information.

2.1.3 Configuring ACL Rules

TP-LINK Omada TL-SG2008P - Configuring ACL Rules - 1

Note:

Every ACL has an implicit deny all rule at the end of an ACL rule list. That is, if an ACL is applied to a packet and none of the explicit rules match, then the final implicit deny all rule takes effect and the packet is dropped.

The created ACL will be displayed on the SECURITY > ACL > ACL Config page.

Figure 2-2 Editing ACL

ACL Config
+ Add - Delete
ACL TypeACL IDACL NameRulesOperation
IP ACL500ACL1NoneEdit ACL
Total: 1

Click Edit ACL in the Operation column. Then you can configure rules for this ACL.

The following sections introduce how to configure MAC ACL, IP ACL, Combined ACL and IPv6 ACL.

Configuring MAC ACL Rule

Click Edit ACL for a MAC ACL entry to load the following page.

Figure 2-3 Configuring the MAC ACL Rule
TP-LINK Omada TL-SG2008P - Configuring MAC ACL Rule - 1

text_image ACL Details ACL Type: MAC ACL ACL ID: 1 ACL Name: ACL2 ACL Rules Table 1 Resequence Add Delete Refresh ID Rule ID S-MAC D-MAC Action Total Matched Counter Operation No entries in this table. Total: 0

In ACL Rules Table section, click + Add and the following page will appear.

Figure 2-4 Configuring the MAC ACL Rule
TP-LINK Omada TL-SG2008P - Configuring MAC ACL Rule - 2

text_image MAC ACL Rule ACL ID: 1 ACL Name: ACL2 Rule ID: Auto Assign Operation: Permit □ S-MAC: (Format: FF-FF-FF-FF-FF-FF) Mask: (Format: FF-FF-FF-FF-FF-FF) □ D-MAC: (Format: FF-FF-FF-FF-FF-FF) Mask: (Format: FF-FF-FF-FF-FF-FF) □ VLAN ID: (1-4094) □ EtherType: (4-hex number) User Priority: Default Time Range: (Optional) Logging: Disable Policy □ Mirroring □ Redirect □ Rate Limit □ QoS Remark Discard Apply

Follow these steps to configure the MAC ACL rule:

1) In the MAC ACL Rule section, configure the following parameters:

Rule ID Enter an ID number to identify the rule.
It should not be the same as any current rule ID in the same ACL. For the convenience of inserting new rules to an ACL, you should set the appropriate interval between rule IDs.
If you selectAuto Assign, the rule ID will be assigned automatically by the system and the default increment between neighboring rule IDs is 5.
Operation Select an action to be taken when a packet matches the rule.
Permit: To forward the matched packets.
Deny: To discard the matched packets.
S-MAC/MaskEnter the source MAC address with a mask. A value of 1 in the mask indicates that the corresponding bit in the address will be matched.
D-MAC/MaskEnter the destination MAC address with a mask. A value of 1 in the mask indicates that the corresponding bit in the address will be matched.
VLAN ID Enter the ID number of the VLAN with which packets will match. The valid range is 1-4094. If the ACL is bound to a VLAN, the system requires the VLAN ID of a packet to match the ID of the VLAN instead of the ID listed here.
EtherType Specify the EtherType to be matched using 4 hexadecimal numbers.
User Priority Specify the User Priority to be matched.
Time RangeSelect a time range during which the rule will take effect. The default value is No Limit, which means the rule is always in effect. The Time Range referenced here can be created on the SYSTEM > Time Range page.
Logging Enable Logging function for the ACL rule. Then the times that the rule is matched will be logged every 5 minutes and a related trap will be generated. You can refer to Total Matched Counter in the ACL Rules Table to view the matching times.

2) In the Policy section, enable or disable the Mirroring feature for the matched packets. With this option enabled, choose a destination port to which the packets will be mirrored.

Figure 2-5 Configuring Mirroring
TP-LINK Omada TL-SG2008P - Configuring MAC ACL Rule - 3

text_image Mirroring Port (Format: 1/0/1, input or choose below) UNIT1 2 4 6 8 10 12 14 15 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available

3) In the Policy section, enable or disable the Redirect feature for the matched packets. With this option enabled, choose a destination port to which the packets will be redirected.

Figure 2-6 Configuring Redirect
TP-LINK Omada TL-SG2008P - Configuring MAC ACL Rule - 4

text_image Redirect Destination Port: (Format:1/0/1, input or choose below) UNIT1 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available

TP-LINK Omada TL-SG2008P - Configuring MAC ACL Rule - 5

Note:

In the Mirroring feature, the matched packets will be copied to the destination port and the original forwarding will not be affected. While in the Redirect feature, the matched packets will be forwarded only on the destination port.

4) In the Policy section, enable or disable the Rate Limit feature for the matched packets. With this option enabled, configure the related parameters.

Figure 2-7 Configuring Rate Limit
TP-LINK Omada TL-SG2008P - Note: - 1

text_image Rate Limit Rate: Kbps (1-10000000) Burst Size: KB (1-128) Out of Band:

Rate Specify the transmission rate for the matched packets.

Burst Size Specify the maximum number of bytes allowed in one second.

Out of Band Select the action for the packets whose rate is beyond the specified rate.

None: The packets will be forwarded normally.

Drop: The packets will be discarded.

Remark DSCP: You can specify a DSCP value, and the DSCP field of the packets will be changed to the specified one.

Note: Remark DSCP is only available on certain devices.

5) In the Policy section, enable or disable the QoS Remark feature for the matched packets. With this option enabled, configure the related parameters, and the remarked values will take effect in the QoS processing on the switch.

Figure 2-8 Configuring QoS Remark
TP-LINK Omada TL-SG2008P - Note: - 2

text_image QoS Remark DSCP: Default Local Priority: Default 802.1p Priority: Default

DSCP Specify the DSCP field for the matched packets. The DSCP field of the packets will be changed to the specified one.

Local PrioritySpecify the local priority for the matched packets. The local priority of the packets will be changed to the specified one.
802.1p PrioritySpecify the 802.1p priority for the matched packets. The 802.1p priority of the packets will be changed to the specified one.

6) Click Apply.

Configuring IP ACL Rule

Click Edit ACL for an IP ACL entry to load the following page.

Figure 2-9 Configuring the IP ACL Rule
TP-LINK Omada TL-SG2008P - Configuring IP ACL Rule - 1

text_image ACL Details ACL Type: IP ACL ACL ID: 500 ACL Name: ACL1 ACL Rules Table Resequence Add Delete Refresh ID Rule ID S-IP D-IP IP Protocol Action Total Matched Counter Operation No entries in this table. Total: 0

In ACL Rules Table section, click + Add and the following page will appear.

Figure 2-10 Configuring the IP ACL Rule
TP-LINK Omada TL-SG2008P - Configuring IP ACL Rule - 2

text_image IP ACL Rule ACL ID: 500 ACL Name: ACL1 Rule ID: Auto Assign Operation: Permit S-IP: (Format: 192.168.0.1) Mask: (Format: 255.255.255.0) D-IP: (Format: 192.168.0.1) Mask: (Format: 255.255.255.0) IP Protocol: No Limit DSCP: No Limit IP ToS: (Optional, 0-15) IP Pre: (Optional, 0-7) Time Range: (Optional) Logging: Disable Policy Mirroring Redirect Rate Limit QoS Remark Discard Apply

Follow these steps to configure the IP ACL rule:

1) In the IP ACL Rule section, configure the following parameters:

Rule ID Enter an ID number to identify the rule.

It should not be the same as any current rule ID in the same ACL. For the convenience of inserting new rules to an ACL, you should set the appropriate interval between rule IDs.

If you select Auto Assign, the rule ID will be assigned automatically by the system and the default increment between neighboring rule IDs is 5

Operation Select an action to be taken when a packet matches the rule.

Permit: To forward the matched packets.

Deny: To discard the matched packets.

FragmentWith this option selected, the rule will be applied to all fragment packets except for the last fragment packet in the fragment packet group.Note: Fragment is only available on certain devices.
S-IP/Mask Enter the source IP address with a mask. A value of 1 in the mask indicates that the corresponding bit in the address will be matched.
D-IP/MaskEnter the destination IP address with a mask. A value of 1 in the mask indicates that the corresponding bit in the address will be matched.
IP ProtocolSelect a protocol type from the drop-down list. The default is No Limit, which indicates that packets of all protocols will be matched. You can also select User-defined to customize the IP protocol.
TCP FlagIf TCP protocol is selected, you can configure the TCP Flag to be used for the rule's matching operations. There are six flags and each has three options, which are *, 0 and 1. The default is *, which indicates that the flag is not used for matching operations.URG: Urgent flag.ACK: Acknowledge flag.PSH: Push flag.RST: Reset flag.SYN: Synchronize flag.FIN: Finish flag.
S-Port / D-PortIf TCP/UDP is selected as the IP protocol, specify the source and destination port number with a mask.Value: Specify the port number.Mask: Specify the port mask with 4 hexadecimal numbers.
DSCP Specify a DSCP value to be matched between 0 and 63. The default is No Limit.
IP ToS Specify an IP ToS value to be matched between 0 and 15. The default is No Limit.
IP Pre Specify an IP Precedence value to be matched to be matched between 0 and 7. The default is No Limit.
Time RangeSelect a time range during which the rule will take effect. The default value is No Limit, which means the rule is always in effect. The Time Range referenced here can be created on the SYSTEM > Time Range page.
Logging Enable Logging function for the ACL rule. Then the times that the rule is matched will be logged every 5 minutes and a related trap will be generated. You can refer to Total Matched Counter in the ACL Rules Table to view the matching times.

2) In the Policy section, enable or disable the Mirroring feature for the matched packets. With this option enabled, choose a destination port to which the packets will be mirrored.

Figure 2-11 Configuring Mirroring
TP-LINK Omada TL-SG2008P - Configuring IP ACL Rule - 3

text_image Mirroring Port (Format: 1/0/1, input or choose below) UNIT1 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available

3) In the Policy section, enable or disable the Redirect feature for the matched packets. With this option enabled, choose a destination port to which the packets will be redirected.

Figure 2-12 Configuring Redirect
TP-LINK Omada TL-SG2008P - Configuring IP ACL Rule - 4

text_image Redirect Destination Port: (Format: 1/0/1, input or choose below) UNIT1 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available

TP-LINK Omada TL-SG2008P - Configuring IP ACL Rule - 5

Note:

In the Mirroring feature, the matched packets will be copied to the destination port and the original forwarding will not be affected. While in the Redirect feature, the matched packets will be forwarded only on the destination port.

4) In the Policy section, enable or disable the Rate Limit feature for the matched packets. With this option enabled, configure the related parameters.

Figure 2-13 Configuring Rate Limit
TP-LINK Omada TL-SG2008P - Note: - 1

text_image Rate Limit Rate: Kbps (1-10000000) Burst Size: KB (1-128) Out of Band:

Rate Specify the transmission rate for the matched packets.

Burst Size Specify the maximum number of bytes allowed in one second.

Out of Band Select the action for the packets whose rate is beyond the specified rate.

None: The packets will be forwarded normally.

Drop: The packets will be discarded.

Remark DSCP: You can specify a DSCP value, and the DSCP field of the packets will be changed to the specified one.

Note: Remark DSCP is only available on certain devices.

5) In the Policy section, enable or disable the QoS Remark feature for the matched packets. With this option enabled, configure the related parameters, and the remarked values will take effect in the QoS processing on the switch.

Figure 2-14 Configuring QoS Remark

QoS Remark

DSCP:

Default

TP-LINK Omada TL-SG2008P - Note: - 2

Local Priority:

Default

TP-LINK Omada TL-SG2008P - Note: - 3

802.1p Priority:

Default

TP-LINK Omada TL-SG2008P - Note: - 4

DSCP Specify the DSCP field for the matched packets. The DSCP field of the packets will be changed to the specified one.

Local Priority

Specify the local priority for the matched packets. The local priority of the packets will be changed to the specified one.

802.1p Priority

Specify the 802.1p priority for the matched packets. The 802.1p priority of the packets will be changed to the specified one.

6) Click Apply.

Configuring Combined ACL Rule

Click Edit ACL for a Combined ACL entry to load the following page.

Figure 2-15 Configuring the Combined ACL Rule
TP-LINK Omada TL-SG2008P - Configuring Combined ACL Rule - 1

text_image ACL Details ACL Type: Combined ACL ACL ID: 1000 ACL Name: ACL_1000 ACL Rules Table Resequence Add Delete Refresh ID Rule ID S-MAC D-MAC S-IP D-IP VID Action Total Matched Operation Counter No entries in this table. Total: 0

In ACL Rules Table section, click + Add and the following page will appear.

Figure 2-16 Configuring the Combined ACL Rule
TP-LINK Omada TL-SG2008P - Configuring Combined ACL Rule - 2

text_image Combined ACL Rule ACL ID: 1000 ACL Name: ACL_1000 Rule ID: Auto Assign Operation: Permit S-MAC: (Format: FF-FF-FF-FF-FF-FF) Mask: (Format: FF-FF-FF-FF-FF-FF) D-MAC: (Format: FF-FF-FF-FF-FF-FF) Mask: (Format: FF-FF-FF-FF-FF-FF) VLAN ID: (1-4094) EtherType: (4-hex number) S-IP: (Format: 192.168.0.1) Mask: (Format: 255.255.255.0) D-IP: (Format: 192.168.0.1) Mask: (Format: 255.255.255.0) IP Protocol: No Limit DSCP: No Limit IP ToS: (Optional, 0-15) IP Pre: (Optional, 0-7) User Priority: Default Time Range: (Optional) Logging: Disable Policy Mirroring Redirect Rate Limit QoS Remark Discard Apply

Follow these steps to configure the Combined ACL rule:

1) In the Combined ACL Rule section, configure the following parameters:

Rule ID Enter an ID number to identify the rule.

It should not be the same as any current rule ID in the same ACL. For the convenience of inserting new rules to an ACL, you should set the appropriate interval between rule IDs.

If you select Auto Assign, the rule ID will be assigned automatically by the system and the default increment between neighboring rule IDs is 5

Operation Select an action to be taken when a packet matches the rule.
Permit: To forward the matched packets.
Deny: To discard the matched packets.
S-MAC/MaskEnter the source MAC address with a mask. A value of 1 in the mask indicates that the corresponding bit in the address will be matched.
D-MAC/MaskEnter the destination IP address with a mask. A value of 1 in the mask indicates that the corresponding bit in the address will be matched.
VLAN ID Enter the ID number of the VLAN with which packets will match. The valid range is 1-4094. If the ACL is bound to a VLAN, the system requires the VLAN ID of a packet to match the ID of the VLAN instead of the ID listed here.
EtherType Specify the EtherType to be matched using 4 hexadecimal numbers.
S-IP/Mask Enter the source IP address with a mask. A value of 1 in the mask indicates that the corresponding bit in the address will be matched.
D-IP/MaskEnter the destination IP address with a mask. A value of 1 in the mask indicates that the corresponding bit in the address will be matched.
IP ProtocolSelect a protocol type from the drop-down list. The default is No Limit, which indicates that packets of all protocols will be matched. You can also select User-defined to customize the IP protocol.
TCP FlagIf TCP protocol is selected, you can configure the TCP Flag to be used for the rule's matching operations. There are six flags and each has three options, which are *, 0 and 1. The default is *, which indicates that the flag is not used for matching operations.URG: Urgent flag.ACK: Acknowledge flag.PSH: Push flag.RST: Reset flag.SYN: Synchronize flag.FIN: Finish flag.
S-Port / D-PortIf TCP/UDP is selected as the IP protocol, specify the source and destination port number with a mask.Value: Specify the port number.Mask: Specify the port mask with 4 hexadecimal numbers.
DSCP Specify a DSCP value to be matched between 0 and 63. The default is No Limit.
IP ToS Specify an IP ToS value to be matched between 0 and 15. The default is No Limit.

IP Pre Specify an IP Precedence value to be matched to be matched between 0 and 7. The default is No Limit.

User Priority Specify the User Priority to be matched.

Time Range

Select a time range during which the rule will take effect. The default value is No Limit, which means the rule is always in effect. The Time Range referenced here can be created on the SYSTEM > Time Range page.

Logging Enable Logging function for the ACL rule. Then the times that the rule is matched will be logged every 5 minutes and a related trap will be generated. You can refer to Total Matched Counter in the ACL Rules Table to view the matching times.

2) In the Policy section, enable or disable the Mirroring feature for the matched packets. With this option enabled, choose a destination port to which the packets will be mirrored.

Figure 2-17 Configuring Mirroring
TP-LINK Omada TL-SG2008P - Configuring Combined ACL Rule - 3

text_image Mirroring Port (Format: 1/0/1, input or choose below) UNIT1 2 4 6 8 10 12 14 15 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available

3) In the Policy section, enable or disable the Redirect feature for the matched packets. With this option enabled, choose a destination port to which the packets will be redirected.

Figure 2-18 Configuring Redirect
TP-LINK Omada TL-SG2008P - Configuring Combined ACL Rule - 4

text_image Redirect Destination Port: (Format: 1/0/1, input or choose below) UNIT1 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available

TP-LINK Omada TL-SG2008P - Configuring Combined ACL Rule - 5

Note:

In the Mirroring feature, the matched packets will be copied to the destination port and the original forwarding will not be affected. While in the Redirect feature, the matched packets will be forwarded only on the destination port.

4) In the Policy section, enable or disable the Rate Limit feature for the matched packets. With this option enabled, configure the related parameters.

Figure 2-19 Configuring Rate Limit
TP-LINK Omada TL-SG2008P - Note: - 1

text_image Rate Limit Rate: Kbps (1-10000000) Burst Size: KB (1-128) Out of Band:

Rate Specify the transmission rate for the matched packets.

Burst Size Specify the maximum number of bytes allowed in one second.

Out of Band Select the action for the packets whose rate is beyond the specified rate.

None: The packets will be forwarded normally.

Drop: The packets will be discarded.

Remark DSCP: You can specify a DSCP value, and the DSCP field of the packets will be changed to the specified one.

Note: Remark DSCP is only available on certain devices.

5) In the Policy section, enable or disable the QoS Remark feature for the matched packets. With this option enabled, configure the related parameters, and the remarked values will take effect in the QoS processing on the switch.

Figure 2-20 Configuring QoS Remark
TP-LINK Omada TL-SG2008P - Note: - 2

text_image QoS Remark DSCP: Default Local Priority: Default 802.1p Priority: Default

DSCP Specify the DSCP field for the matched packets. The DSCP field of the packets will be changed to the specified one.

Local PrioritySpecify the local priority for the matched packets. The local priority of the packets will be changed to the specified one.
802.1p PrioritySpecify the 802.1p priority for the matched packets. The 802.1p priority of the packets will be changed to the specified one.

6) Click Apply.

Configuring the IPv6 ACL Rule

Click Edit ACL for an IPv6 ACL entry to load the following page.

Figure 2-21 Configuring the IPv6 ACL Rule
TP-LINK Omada TL-SG2008P - Note: - 3

text_image ACL Details ACL Type: IPv6 ACL ACL ID: 1500 ACL Name: ACL_1500 ACL Rules Table Resequence Add Delete Refresh ID Rule ID IPv6 Source IP IPv6 Destination IP Action Total Matched Counter Operation No entries in this table. Total: 0

In ACL Rules Table section, click + Add and the following page will appear.

Figure 2-22 Configuring the IPv6 ACL Rule
TP-LINK Omada TL-SG2008P - Note: - 4

text_image IPv6 ACL Rule ACL ID: 1500 ACL Name: ACL_1500 Rule ID: Auto Assign Operation: Permit □ IPv6 Class: (0-63) □ Flow Label: (5-hex number: 0x00000-0xFFFF) □ IPv6 Source IP: (Format: 2001::) Mask: (Format: FFFF:FFFF:FFFF:FFFF) □ IPv6 Destination IP: (Format: 2001::) Mask: (Format: FFFF:FFFF:FFFF:FFFF) IP Protocol: No Limit Time Range: (Optional) Policy □ Mirroring □ Redirect □ Rate Limit □ QoS Remark Discard Apply

Follow these steps to configure the IPv6 ACL rule:

1) In the IPv6 ACL Rule section, configure the following parameters:

Rule ID Enter an ID number to identify the rule.
It should not be the same as any current rule ID in the same ACL. For the convenience of inserting new rules to an ACL, you should set the appropriate interval between rule IDs.
If you selectAuto Assign, the rule ID will be assigned automatically by the system and the default increment between neighboring rule IDs is 5
Operation Select an action to be taken when a packet matches the rule.
Permit: To forward the matched packets.
Deny: To discard the matched packets.
IPv6 ClassSpecify an IPv6 class value to be matched. The switch will check the class field of the IPv6 header.
Flow Label Specify a Flow Label value to be matched.
IPv6 Source IPEnter the source IPv6 address to be matched. All types of IPv6 address will be checked. You may enter a complete 128-bit IPv6 address but only the first 64 bits will be valid.
Mask The mask is required if the source IPv6 address is entered. Enter the mask in complete format (for example, FFFF:FFFF:0000:FFFF).
The IP address mask specifies which bits in the source IPv6 address to match the rule. A value of 1 in the mask indicates that the corresponding bit in the address will be matched.
IPv6 Destination IPEnter the destination IPv6 address to be matched. All types of IPv6 address will be checked. You may enter a complete 128-bit IPv6 address but only the first 64 bits will be valid.
Mask The mask is required if the destination IPv6 address is entered. Enter the complete mask (for example, FFFF:FFFF:0000:FFFF).
The IP address mask specifies which bits in the source IP address to match the rule. A value of 1 in the mask indicates that the corresponding bit in the address will be matched.
IP Protocol Select a protocol type from the drop-down list.
No Limit: Packets of all protocols will be matched.
UDP: Specify the source port and destination port for the UDP packet to be matched.
TCP: Specify the source port and destination port for the TCP packet to be matched.
User-defined: You can customize an IP protocol.
S-Port / D-PortIf TCP/UDP is selected as the IP protocol, specify the source and destination port numbers.

Time Range

Select a time range during which the rule will take effect. The default value is No Limit, which means the rule is always in effect. The Time Range referenced here can be created on the SYSTEM > Time Range page.

2) In the Policy section, enable or disable the Mirroring feature for the matched packets. With this option enabled, choose a destination port to which the packets will be mirrored.

Figure 2-23 Configuring Mirroring
TP-LINK Omada TL-SG2008P - Note: - 5

text_image Mirroring Port (Format: 1/0/1, input or choose below) UNIT1 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available

3) In the Policy section, enable or disable the Redirect feature for the matched packets. With this option enabled, choose a destination port to which the packets will be redirected.

Figure 2-24 Configuring Redirect
TP-LINK Omada TL-SG2008P - Note: - 6

text_image Redirect Destination Port: (Format:1/0/1, input or choose below) UNIT1 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available

TP-LINK Omada TL-SG2008P - Note: - 7

Note:

In the Mirroring feature, the matched packets will be copied to the destination port and the original forwarding will not be affected. While in the Redirect feature, the matched packets will be forwarded only on the destination port.

4) In the Policy section, enable or disable the Rate Limit feature for the matched packets. With this option enabled, configure the related parameters.

Figure 2-25 Configuring Rate Limit
TP-LINK Omada TL-SG2008P - Note: - 1

text_image Rate Limit Rate: Kbps (1-10000000) Burst Size: KB (1-128) Out of Band:

Rate Specify the transmission rate for the matched packets.

Burst Size Specify the maximum number of bytes allowed in one second.

Out of Band Select the action for the packets whose rate is beyond the specified rate.

None: The packets will be forwarded normally.

Drop: The packets will be discarded.

Remark DSCP: You can specify a DSCP value, and the DSCP field of the packets will be changed to the specified one.

Note: Remark DSCP is only available on certain devices.

5) In the Policy section, enable or disable the QoS Remark feature for the matched packets. With this option enabled, configure the related parameters, and the remarked values will take effect in the QoS processing on the switch.

Figure 2-26 Configuring QoS Remark

QoS Remark

DSCP:

Default

TP-LINK Omada TL-SG2008P - Note: - 2

Local Priority:

Default

TP-LINK Omada TL-SG2008P - Note: - 3

802.1p Priority:

Default

TP-LINK Omada TL-SG2008P - Note: - 4

DSCP Specify the DSCP field for the matched packets. The DSCP field of the packets will be changed to the specified one.

Local Priority

Specify the local priority for the matched packets. The local priority of the packets will be changed to the specified one.

802.1p Priority

Specify the 802.1p priority for the matched packets. The 802.1p priority of the packets will be changed to the specified one.

6) Click Apply.

Configuring the Packet Content ACL Rule

TP-LINK Omada TL-SG2008P - Configuring the Packet Content ACL Rule - 1

Note:

Packet Content ACL is only available on certain devices.

Click Edit ACL for a Packet Content ACL entry to load the following page.

Figure 2-27 Configuring the Packet Content ACL Rule
TP-LINK Omada TL-SG2008P - Note: - 1

text_image Packet Content Offset Profile Global Config Chunk0 Offset: (0-31) Chunk1 Offset: (0-31) Chunk2 Offset: (0-31) Chunk3 Offset: (0-31) Apply ACL Details ACL Type: Packet Content ACL ACL ID: 2000 ACL Name: ACL_2000 ACL Rules Table Resequence Add Delete Refresh ID Rule ID Enabled Chunk Action Total Matched Counter Operation No entries in this table. Total: 0

In the Packet Content Offset Profile Global Config section, configure the Chunk Offset. Click Apply.

Chunk0 Offset/
Chunk1 Offset/
Chunk2 Offset/
Chunk3 Offset

Enter the offset of a chunk. Packet Content ACL analyzes and processes data packets based on 4 chunk match conditions, and each chunk can specify a user-defined 4-byte segment carried in the packet's first 128 bytes. Offset 31 matches the 127, 128, 1, 2 bytes of the packet, offset 0 matches the 3,4,5,6 bytes of the packet, and so on, for the rest of the offset value.

Note: All 4 chunks must be set at the same time.

In ACL Rules Table section, click + Add and the following page will appear.

Figure 2-28 Configuring the Packet Content ACL Rule
TP-LINK Omada TL-SG2008P - Note: - 2

text_image Packet Content Rule ACL ID: 2000 ACL Name: ACL_2000 Rule ID: Auto Assign Operation Deny Chunk0 Chunk Value: (8-hex number) Chunk Mask: (8-hex number, like '0000ffff') Chunk1 Chunk Value: (8-hex number) Chunk Mask: (8-hex number, like '0000ffff') Chunk2 Chunk Value: (8-hex number) Chunk Mask: (8-hex number, like '0000ffff') Chunk3 Chunk Value: (8-hex number) Chunk Mask: (8-hex number, like '0000ffff') Time Range: (Optional) Policy Mirroring Redirect Rate Limit QoS Remark Discard Apply

Follow these steps to configure the Packet Content ACL rule:

1) In the Packet Content Rule section, configure the following parameters:

Rule ID Enter an ID number to identify the rule.
It should not be the same as any current rule ID in the same ACL. If you select Auto Assign, the rule ID will be assigned automatically and the interval between rule IDs is 5.
Operation Select an action to be taken when a packet matches the rule.
Permit: To forward the matched packets.
Deny: To discard the matched packets.
Chunk0-Chunk3 Specify the EtherType to be matched using 4 hexadecimal numbers.
Chunk ValueEnter the 4-byte value in hexadecimal for the desired chunk, like '0000ffff'. The Packet Content ACL will check this chunk of packets to examine if the packets match the rule or not.
Chunk Mask Enter the 4-byte mask in hexadecimal for the desired chunk. The mask must be written completely in 4-byte hex mode, like '0000ffff'. The mask specifies which bits to match the rule.
Time Range Select a time range during which the rule will take effect. The default value is No Limit, which means the rule is always in effect. The Time Range referenced here can be created on the SYSTEM > Time Range page.
Logging Enable Logging function for the ACL rule. Then the times that the rule is matched will be logged every 5 minutes and a related trap will be generated. You can refer to Total Matched Counter in the ACL Rules Table to view the matching times.

2) In the Policy section, enable or disable the Mirroring feature for the matched packets. With this option enabled, choose a destination port to which the packets will be mirrored.

Figure 2-29 Configuring Mirroring
TP-LINK Omada TL-SG2008P - Note: - 3

text_image Mirroring Port (Format:1/0/1, input or choose below) UNIT1 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available

3) In the Policy section, enable or disable the Redirect feature for the matched packets. With this option enabled, choose a destination port to which the packets will be redirected.

Figure 2-30 Configuring Redirect
TP-LINK Omada TL-SG2008P - Note: - 4

text_image Redirect Destination Port: (Format:1/0/1, input or choose below) UNIT1 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Selected Unselected Not Available

TP-LINK Omada TL-SG2008P - Note: - 5

Note:

In the Mirroring feature, the matched packets will be copied to the destination port and the original forwarding will not be affected. While in the Redirect feature, the matched packets will be forwarded only on the destination port.

4) In the Policy section, enable or disable the Rate Limit feature for the matched packets. With this option enabled, configure the related parameters.

Figure 2-31 Configuring Rate Limit
TP-LINK Omada TL-SG2008P - Note: - 1

text_image Rate Limit Rate: Kbps (1-10000000) Burst Size: KB (1-128) Out of Band:

Rate Specify the transmission rate for the matched packets.

Burst Size Specify the maximum number of bytes allowed in one second.

Out of Band Select the action for the packets whose rate is beyond the specified rate.

None: The packets will be forwarded normally.

Drop: The packets will be discarded.

Remark DSCP: You can specify a DSCP value, and the DSCP field of the packets will be changed to the specified one.

Note: Remark DSCP is only available on certain devices.

5) In the Policy section, enable or disable the QoS Remark feature for the matched packets. With this option enabled, configure the related parameters, and the remarked values will take effect in the QoS processing on the switch.

Figure 2-32 Configuring QoS Remark
TP-LINK Omada TL-SG2008P - Note: - 2

text_image QoS Remark DSCP: Default Local Priority: Default 802.1p Priority: Default
DSCP Specify the DSCP field for the matched packets. The DSCP field of the packets will be changed to the specified one.
Local PrioritySpecify the local priority for the matched packets. The local priority of the packets will be changed to the specified one.
802.1p PrioritySpecify the 802.1p priority for the matched packets. The 802.1p priority of the packets will be changed to the specified one.

6) Click Apply.

Viewing the ACL Rules

The rules in an ACL are listed in ascending order of their rule IDs. The switch matches a received packet with the rules in order. When a packet matches a rule, the switch stops the match process and performs the action defined in the rule.

Click Edit ACL for an entry you have created and you can view the rule table. We take IP ACL rules table for example.

Figure 2-33 Viewing ACL Rules Table

☐ IDRule IDS-IPD-IPIP ProtocolActionTotal Matched CounterOperation
☐ 11192.168.1.0192.168.5.0Permit0
☐ 23192.168.7.0Permit0
☐ 35192.168.0.0Deny0
Total: 3

Here you can view and edit the ACL rules. You can also click Resequence to resequence the rules by providing a Start Rule ID and Step value.

2.1.4 Configuring ACL Binding

You can bind the ACL to a port or a VLAN. The received packets on the port or in the VLAN will then be matched and processed according to the ACL rules. An ACL takes effect only after it is bound to a port or VLAN.

TP-LINK Omada TL-SG2008P - Configuring ACL Binding - 1

Note:

• Different types of ACLs cannot be bound to the same port or VLAN.
- Multiple ACLs of the same type can be bound to the same port or VLAN. The switch matches the received packets using the ACLs in order. The ACL that is bound earlier has a higher priority.

Binding the ACL to a Port

Choose the menu SECURITY > ACL > ACL Binding > Port Binding and click + Add to load the following page.

Figure 2-34 Binding the ACL to a Port
TP-LINK Omada TL-SG2008P - Binding the ACL to a Port - 1

text_image Port Binding Config ACL: ID Name 1000 Direction Ingress Port: (Format:1/0/1, input or choose below) UNIT1 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Cancel Create

Follow these steps to bind the ACL to a Port:

1) Choose ID or Name to be used for matching the ACL. Then select an ACL from the drop-down list.
2) Specify the port to be bound.
3) Click Create.

■ Binding the ACL to a VLAN

Choose the menu SECURITY > ACL > ACL Binding > VLAN Binding to load the following page.

Figure 2-35 Binding the ACL to a VLAN
TP-LINK Omada TL-SG2008P - Binding the ACL to a Port - 2

text_image VLAN Binding Config ACL: ID Name 1000 VLAN ID List: (Format: 1-3,5,7) Direction Ingress Cancel Create

Follow these steps to bind the ACL to a VLAN:

1) Choose ID or Name to be used for matching the ACL. Then select an ACL from the drop-down list.
2) Enter the ID of the VLAN to be bound.
3) Click Create.

2.2 Using the CLI

2.2.1 Configuring Time Range

Some ACL-based services or features may need to be limited to take effect only during a specified time period. In this case, you can configure a time range for the ACL. For details about Time Range Configuration, please refer to Managing System.

2.2.2 Configuring ACL

Follow the steps to create different types of ACL and configure the ACL rules.

You can define the rules based on source or destination IP address, source or destination MAC address, protocol type, port number and others.

MAC ACL

Follow these steps to configure MAC ACL:

Step 1 configure

Enter global configuration mode.

Step 2 access-list create

acl-id [name acl-name]

Create a MAC ACL.

acl-id: Enter an ACL ID. The ID ranges from 0 to 499.

acl-name: Enter a name to identify the ACL.

Step 3 access-list mac acl-id-or-name rule { auto | rule-id } { deny | permit } logging { enable | disable}

[smac source-mac smask source-mac-mask] [dmac destination-mac dmask destination-mac-mask] [type ether-type] [pri dot1p-priority] [vid vlan-id] [tseg time-range-name]

Add a MAC ACL Rule.

acl-id-or-name: Enter the ID or name of the ACL that you want to add a rule for.

auto: The rule ID will be assigned automatically and the interval between rule IDs is 5.

rule-id: Assign an ID to the rule.

deny | permit: Specify the action to be taken with the packets that match the rule. By default, it is set to permit. The packets will be discarded if "deny" is selected and forwarded if "permit" is selected.

logging {enable | disable}: Enable or disable Logging function for the ACL rule. If "enable" is selected, the times that the rule is matched will be logged every 5 minutes. With ACL Counter trap enabled, a related trap will be generated if the matching times changes.

source-mac: Enter the source MAC address. The format is FF:FF:FF:FF:FF:FF.

source-mac-mask: Enter the mask of the source MAC address. This is required if a source MAC address is entered. The format is FF:FF:FF:FF:FF:FF.

destination-mac: Enter the destination MAC address. The format is FF:FF:FF:FF:FF:FF.

destination-mac-mask: Enter the mask of the destination MAC address. This is required if a destination MAC address is entered. The format is FF:FF:FF:FF:FF:FF.

ether-type: Specify an Ethernet-type with 4 hexadecimal numbers.

dot1p-priority: The user priority ranges from 0 to 7. The default is No Limit.

vlan-id: The VLAN ID ranges from 1 to 4094.

time-range-name: The name of the time-range. The default is No Limit.

Step 4 exit

Return to global configuration mode.

Step 5 show access-list [ acl-id-or-name ]

Display the current ACL configuration.

acl-id-or-name: The ID number or name of the ACL.

Step 6 end

Return to privileged EXEC mode.

Step 7 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to create MAC ACL 50 and configure Rule 5 to permit packets with source MAC address 00:34:A2:D4:34:B5:

Switch#configure

Switch(config)#access-list create 50

Switch(config-mac-acl)#access-list mac 50 rule 5 permit logging disable smac

00:34:A2:D4:34:B5 smask FF:FF:FF:FF:FF:FF

Switch(config-mac-acl)#exit

Switch(config)#show access-list 50

MAC access list 50 name: ACL_50

rule 5 permit logging disable smac 00:34:a2:d4:34:b5 smask ff:ff:ff:ff:ff:ff

Switch(config)#end

Switch#copy running-config startup-config

IP ACL

Follow these steps to configure IP ACL:

Step 1 configure

Enter global configuration mode.

Step 2 access-list create

acl-id [name acl-name]

Create an IP ACL.

acl-id: Enter an ACL ID. The ID ranges from 500 to 999.

acl-name: Enter a name to identify the ACL.

Step 3 access-list ip acl-id-or-name rule {auto | rule-id } {deny | permit} logging {enable | disable} [sip sip-address sip-mask sip-address-mask ] [dipdip-address dip-mask dip-address-mask ] [dscp dscp-value] [tos tos-value] [pre pre-value] [frag {enable | disable}] [protocol protocol [s-port s-port-number s-port-mask s-port-mask] [d-port d-port-number d-port-mask d-port-mask] [tcpflag tcpflag]] [tseg time-range-name]

Add rules to the ACL.

acl-id-or-name: Enter the ID or name of the ACL that you want to add a rule for.

auto: The rule ID will be assigned automatically and the interval between rule IDs is 5.

rule-id: Assign an ID to the rule.

deny | permit: Specify the action to be taken with the packets that match the rule. Deny means to discard; permit means to forward. By default, it is set to permit.

logging {enable | disable}: Enable or disable Logging function for the ACL rule. If "enable" is selected, the times that the rule is matched will be logged every 5 minutes. With ACL Counter trap enabled, a related trap will be generated if the matching times changes.

sip-address: Enter the source IP address.

sip-address-mask: Enter the mask of the source IP address. This is required if a source IP address is entered.

dip-address: Enter the destination IP address.

dip-address-mask: Enter the mask of the destination IP address. This is required if a destination IP address is entered.

dscp-value: Specify the DSCP value between 0 and 63.

tos-value: Specify an IP ToS value to be matched between 0 and 15.

pre-value: Specify an IP Precedence value to be matched between 0 and 7.

frag {enable | disable}: Enable or disable matching of fragmented packets. The default is disable. When enabled, the rule will apply to all fragmented packets and always permit to forward the last fragment of a packet.

Note: frag {enable | disable} is only available on certain devices.

protocol: Specify a protocol number between 0 and 255.

s-port-number: With TCP or UDP configured as the protocol, specify the source port number.

s-port-mask: With TCP or UDP configured as the protocol, specify the source port mask with 4 hexadacimal numbers.

d-port-number: With TCP or UDP configured as the protocol, specify the destination port number.

d-port-mask: With TCP or UDP configured as the protocol, specify the destination port mask with 4 hexadacimal numbers.

tcpflag: With TCP configured as the protocol, specify the flag value using either binary numbers or * (for example, 01*010*). The default is *, which indicates that the flag will not be matched.

The flags are URG (Urgent flag), ACK (Acknowledge Flag), PSH (Push Flag), RST (Reset Flag), SYN (Synchronize Flag) and FIN (Finish Flag).

time-range-name: The name of the time-range. The default is No Limit.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to create IP ACL 600, and configure Rule 1 to permit packets with source IP address 192.168.1.100:

Switch#configure

Switch(config)#access-list create 600

Switch(config)#access-list ip 600 rule 1 permit logging disable sip 192.168.1.100 sip-mask 255.255.255.255

Switch(config)#show access-list 600

IP access list 600 name: ACL_600

rule 1 permit logging disable sip 192.168.1.100 smask 255.255.255.255

Switch(config)#end

Switch#copy running-config startup-config

Combined ACL

Follow these steps to configure Combined ACL:

Step 1 configure

Enter global configuration mode

Step 2 access-list create

acl-id [name acl-name]

Create a Combined ACL.

acl-id: Enter an ACL ID. The ID ranges from 1000 to 1499.

acl-name: Enter a name to identify the ACL.

Step 3 access-list combined

acl-id-or-name rule {auto | rule-id } {deny | permit} logging {enable |

disable} [smac source-mac-address smask source-mac-mask] [dmac dest-mac-address dmask dest-mac-mask] [vid vlan-id] [type ether-type] [pri priority] [sip sip-address sip-mask sip-address-mask] [dip dip-address dip-mask dip-address-mask] [dscp dscp-value] [tos tos-value] [pre pre-value] [protocol protocol [s-port s-port-number s-port-mask s-port-mask] [d-port d-port-number d-port-mask d-port-mask] [tcpflag tcpflag]] [tseg time-range-name]

Add rules to the ACL.

acl-id-or-name: Enter the ID or name of the ACL that you want to add a rule for.

auto: The rule ID will be assigned automatically and the interval between rule IDs is 5.

rule-id: Assign an ID to the rule.

deny | permit: Specify the action to be taken with the packets that match the rule. Deny means to discard; permit means to forward. By default, it is set to permit.

logging {enable | disable}: Enable or disable Logging function for the ACL rule. If "enable" is selected, the times that the rule is matched will be logged every 5 minutes. With ACL Counter trap enabled, a related trap will be generated if the matching times changes.

source-mac-address: Enter the source MAC address.

source-mac-mask: Enter the source MAC address mask.

dest-mac-address: Enter the destination MAC address.

dest-mac-mask: Enter the destination MAC address mask. This is required if a destination MAC address is entered.

vlan-id: The VLAN ID ranges from 1 to 4094.

ether-type: Specify the Ethernet-type with 4 hexadecimal numbers.

priority: The user priority ranges from 0 to 7. The default is No Limit.

sip-address: Enter the source IP address.

sip-address-mask: Enter the mask of the source IP address. It is required if source IP address is entered.

dip-address: This is required if a source IP address is entered.

dip-address-mask: Enter the destination IP address mask. This is required if a destination IP address is entered.

dscp-value: Specify the DSCP value between 0 and 63.

tos-value: Specify an IP ToS value to be matched between 0 and 15.

pre-value: Specify an IP Precedence value to be matched between 0 and 7.

protocol: Specify a protocol number between 0 and 255.

s-port-number: With TCP or UDP configured as the protocol, specify the source port number.

s-port-mask: With TCP or UDP configured as the protocol, specify the source port mask with 4 hexadacimal numbers.

d-port-number: With TCP or UDP configured as the protocol, specify the destination port number.

d-port-mask: With TCP or UDP configured as the protocol, specify the destination port mask with 4 hexadecimal numbers.

tcpflag: With TCP configured as the protocol, specify the flag value using either binary numbers or * (for example, 01*010*). The default is *, which indicates that the flag will not be matched.

The flags are URG (Urgent flag), ACK (Acknowledge Flag), PSH (Push Flag), RST (Reset Flag), SYN (Synchronize Flag), and FIN (Finish Flag).

time-range-name: The name of the time-range. The default is No Limit.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to create Combined ACL 1100 and configure Rule 1 to deny packets with source IP address 192.168.3.100 in VLAN 2:

Switch#configure

Switch(config)#access-list create 1100

Switch(config)#access-list combined 1100 logging disable rule 1 permit vid 2 sip 192.168.3.100 sip-mask 255.255.255.255

Switch(config)#show access-list 2600

Combined access list 2600 name: ACL_2600

rule 1 permit logging disable vid 2 sip 192.168.3.100 sip-mask 255.255.255.255

Switch(config)#end

Switch#copy running-config startup-config

IPv6 ACL

Follow these steps to configure IPv6 ACL:

Step 1 configure

Enter global configuration mode

Step 2 access-list create acl-id [name acl-name]

Create an IPv6 ACL.

acl-id: Enter an ACL ID. The ID ranges from 1500 to 1999.

acl-name: Enter a name to identify the ACL.

Step 3 access-list ipv6 acl-id-or-name rule {auto | rule-id } {deny | permit} logging {enable | disable}

[class class-value] [flow-label flow-label-value] [sip source-ip-address sip-mask source-ip-mask] [dip destination-ip-address dip-mask destination-ip-mask] [s-port source-port-number] [d-port destination-port-number] [tseg time-range-name]

Add rules to the ACL.

acl-id-or-name: Enter the ID or name of the ACL that you want to add a rule for.

auto: The rule ID will be assigned automatically and the interval between rule IDs is 5.

rule-id: Assign an ID to the rule.

deny | permit: Specify the action to be taken with the packets that match the rule. Deny means to discard; permit means to forward. By default, it is set to permit.

logging {enable | disable}: Enable or disable Logging function for the ACL rule. If "enable" is selected, the times that the rule is matched will be logged every 5 minutes. With ACL Counter trap enabled, a related trap will be generated if the matching times changes.

class-value: Specify a class value to be matched. It ranges from 0 to 63.

flow-label-value: Specify a Flow Label value to be matched.

source-ip-address: Enter the source IP address. Enter the destination IPv6 address to be matched. All types of IPv6 address will be checked. You may enter a complete 128-bit IPv6 address but only the first 64 bits will be valid.

source-ip-mask: Enter the source IP address mask. The mask is required if the source IPv6 address is entered. Enter the mask in complete format (for example, ffff:ffff:0000:ffff). The mask specifies which bits in the source IPv6 address to match the rule.

destination-ip-address: Enter the destination IPv6 address to be matched. All types of IPv6 address will be checked. You may enter a complete 128-bit IPv6 addresses but only the first 64 bits will be valid.

destination-ip-mask: Enter the source IP address mask. The mask is required if the source IPv6 address is entered. Enter the mask in complete format (for example, ffff:ffff:0000:ffff). The mask specifies which bits in the source IPv6 address to match the rule.

source-port-number: Enter the TCP/UDP source port if TCP/UDP protocol is selected.

destination-port-number: Enter the TCP/UDP destination port if TCP/UDP protocol is selected.

time-range-name: The name of the time-range. The default is No Limit.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to create IPv6 ACL 1600 and configure Rule 1 to deny packets with source IPv6 address CDCD:910A:2222:5498:8475:1111:3900:2020:

Switch#configure

Switch(config)#access-list create 1600

Switch(config)#access-list ipv6 1600 rule 1 deny logging disable sip

CDCD:910A:2222:5498:8475:1111:3900:2020 sip-mask ffff:ffff:ffff:ffff

Switch(config)#show access-list 1600

IPv6 access list 1600 name: ACL_1600

rule 1 deny logging disable sip cdcd:910a:2222:5498:8475:1111:3900:2020 sip-mask ffff:ff

ff:ffff:ffff

Switch(config)#end

Switch#copy running-config startup-config

Packet Content ACL

TP-LINK Omada TL-SG2008P - Packet Content ACL - 1

Note:

Packet Content ACL is only available on certain devices.

Step 1 configure

Enter global configuration mode

Step 2 access-list create

acl-id [name acl-name]

Create a Packet Content ACL.

acl-id:Enter an ACL ID. The ID ranges from 2000 to 2499.

acl-name: Enter a name to identify the ACL.

Step 3 access-list packet-content profile chunk-offset0

offset0 chunk-offset1 offset1

chunk-offset2 offset2 chunk-offset3 offset3

Specify the offset of each chunk, all the 4 chunks must be set at the same time.

offset0 -offset3: Specify the offset of each chunk, the value ranges from 0 to 31. When the offset is set as 31, it matches the first 127,128, 1, 2 bytes of the packet; when the offset is set as 0, it matches the 3, 4, 5, 6 bytes, and so on, for the rest of the offset value.

Step 4 access-list packet-content config acl-id-or-name rule {auto | rule-id } {deny | permit} logging { enable | disable } [chunk0 value mask0 mask] [chunk1 value mask1 mask] [chunk2 value mask2 mask] [chunk3 value mask3 mask] [tseg time-range-name]

Add rules to the ACL.

acl-id-or-name: Enter the ID or name of the ACL that you want to add a rule for.

auto: The rule ID will be assigned automatically and the interval between rule IDs is 5.

rule-id: Assign an ID to the rule.

deny | permit: Specify the action to be taken with the packets that match the rule. Deny means to discard; permit means to forward. By default, it is set to permit.

logging { enable | disable} : Enable or disable Logging function for the ACL rule. If "enable" is selected, the times that the rule is matched will be logged every 5 minutes. With ACL Counter trap enabled, a related trap will be generated if the matching times changes.

value: Enter the 4-byte value in hexadecimal for the desired chunk, like '0000ffff'. The Packet Content ACL will check this chunk of packets to examine if the packets match the rule or not.

mask: Enter the 4-byte mask in hexadecimal for the desired chunk. The mask must be written completely in 4-byte hex mode, like '0000ffff'. The mask specifies which bits to match the rule.

time-range-name: The name of the time-range. The default is No Limit.

Step 5 end

Return to privileged EXEC mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to create Packet Content ACL 2000, and deny the packets with the value of its chunk1 0x58:

Switch#configure

Switch(config)#access-list create 2000

Switch(config)#access-list packet-content profile chunk-offset0 offset0 chunk-offset1 offset1 chunk-offset2 offset2 chunk-offset3 offset3

Switch(config)#packet-content config 2000 rule 10 deny logging disable chunk1 58 mask1 fffffff

Switch(config)#show access-list 2000

Packet content access list 2000 name: ACL_2000

rule 10 deny logging disable chunk1 value 0x58 mask 0xffffff

Switch(config)#end

Switch#copy running-config startup-config

Resequencing Rules

TP-LINK Omada TL-SG2008P - Resequencing Rules - 1

Note:

Resequencing Rules is only available on certain devices.

You can resequence the rules by providing a Start Rule ID and Step value.

Step 1 configure

Enter global configuration mode.

Step 2 access-list resequence

acl-id-or-name start start-rule-id step rule-id-step-value

Resequence the rules of the specific ACL.

acl-id-or-name: Enter the ID or name of the ACL.

start-rule-id: Enter the start rule ID.

rule-id-step-value: Enter the Step value.

Step 3 end

Return to privileged EXEC mode.

Step 4 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to resequence the rules of MAC ACL 100: set the start rule ID as 1 and the step value as 10:

Switch#configure

Switch(config)#access-list resequence 100 start 1 step 10

Switch(config)#show access-list 100

MAC access list 100 name: "ACL_100"

rule 1 deny logging disable smac aa:bb:cc:dd:ee:ff smask ff:ff:ff:ff:ff:ff

rule 11 permit logging disable vid 18

rule 21 permit logging disable dmac aa:cc:ee:ff:dd:33 dmask ff:ff:ff:ff:ff:ff

Switch(config)#end

Switch#copy running-config startup-config

2.2.3 Configuring Policy

Policy allows you to further process the matched packets through operations such as mirroring, rate-limiting, redirecting, or changing priority.

Follow the steps below to configure the policy actions for an ACL rule.

Step 1 configure

Enter global configuration mode.

Step 2 access-list action

acl-id-or-name rule rule-id

Configure the policy actions for an ACL rule.

acl-id-or-name: Enter the ID or name of the ACL.

rule-id: Enter the ID of the ACL rule.

Step 3

redirect interface { fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port }

(Optional) Define the policy to redirect the matched packets to the desired port.

port: The destination port to which the packets will be redirected. The default is All.

s-mirror interface { fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port }

(Optional) Define the policy to mirror the matched packets to the desired port.

port: The destination port to which the packets will be mirrored.

s-condition rate rate burst burst-size osd { none | discard | remark dscp dscp }

(Optional) Define the policy to monitor the rate of the matched packets.

rate: Specify a rate from 1 to 1000000 kbps.

burst-size: Specify the number of bytes allowed in one second ranging from 1 to 128.

osd: Select either "none", "discard" or "remark dscp" as the action to be taken for the packets whose rate is beyond the specified rate. The default is None. When "remark dscp" is selected, you also need to specify the DSCP value for the matched packets. The DSCP value ranges from 0 to 63.

Note: Remark DSCP is only available on certain devices.

qos-remark [dscp dscp] [priority pri] [dot1p pri]

(Optional) Define the policy to remark priority for the matched packets.

dscp: Specify the DSCP region for the data packets. The value ranges from 0 to 63.

priority pri: Specify the local priority for the data packets. The value ranges from 0 to 7.

dot1p pri: Specify the 802.1p priority for the data packets. The value ranges from 0 to 7.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

Redirect the matched packets to port 1/0/4 for rule 1 of MAC ACL 10:

Switch#configure

Switch(config)#access-list action 10 rule 1

Switch(config-action)#redirect interface gigabitEthernet 1/0/4

Switch(config-action)#exit

Switch(config)#show access-list 10

MAC access list 10 name: ACL_10

rule 5 permit logging disable action redirect Gi1/0/4

Switch(config)#end

Switch#copy running-config startup-config

2.2.4 Configuring ACL Binding

You can bind the ACL to a port or a VLAN. The received packets on the port or in the VLAN will then be matched and processed according to the ACL rules. An ACL takes effect only after it is bound to a port or VLAN.

TP-LINK Omada TL-SG2008P - Configuring ACL Binding - 1

Note:

• Different types of ACLs cannot be bound to the same port or VLAN.
- Multiple ACLs of the same type can be bound to the same port or VLAN. The switch matches the received packets using the ACLs in order. The ACL that is bound earlier has a higher priority.

Follow the steps below to bind ACL to a port or a VLAN:

Step 1 configure

Enter global configuration mode

Step 2 access-list bind acl-id-or-name interface { [vlan vlan-list ] | [fastEthernet port-list ] | [gigabitEthernet port-list] | [ten-gigabitEthernet port-list ] }

Bind the ACL to a port or a VLAN.

acl-id-or-name: Enter the ID or name of the ACL that you want to add a rule for.

vlan-list: Specify the ID or the ID list of the VLAN(s) that you want to bind the ACL to. The valid values are from 1 to 4094, for example, 2-3,5.

port-list Specify the number or the list of the Ethernet port that you want to bind the ACL to.

Step 3 show access-list bind

View the ACL binding configuration.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to bind ACL 1 to port 3 and VLAN 4:

Switch#configure

Switch(config)#access-list bind 1 interface vlan 4 gigabitEthernet 1/0/3

SSwitch(config)#show access-list bind

ACL IDACL NAMEInterface/VIDDirectionType
--------------------
1ACL_1Gi1/0/3IngressPort
1ACL_14IngressVLAN

Switch(config)#end

Switch#copy running-config startup-config

2.2.5 Viewing ACL Counting

You can use the following command to view the number of matched packets of each ACL in the privileged EXEC mode and any other configuration mode:

show access-list acl-id-or-name counter

View the number of matched packets of the specific ACL.

acl-id-or-name: Specify the ID or name of the ACL to be viewed.

3 Configuration Example for ACL

3.1 Configuration Example for MAC ACL

3.1.1 Network Requirements

A company forbids the employees in the R&D department to visit the internal forum during work hours. While the manager of the R&D department can get access to the internal forum without limitation.

As shown below, the internal forum server is connected to the switch via port 1/0/1, and computers in the R&D department are connected to the switch via port 1/0/2.

Figure 3-1 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["Internal Forum Server\nMAC: 40-61-86-FC-71-56"] --> B["Gi1/0/1"]
    B --> C["Gi1/0/2"]
    C --> D["R&D Department"]
    D --> E["R&D manager's PC\nMAC: 8C-DC-D4-40-A1-79"]

3.1.2 Configuration Scheme

To meet the requirements above, you can set up packet filtering by creating an MAC ACL and configuring rules for it.

■ Time Range Configuration

Create a time range entry for the work hour of the company. Apply the time range to the ACL rule which blocks the access to internal forum server.

■ ACL Configuration

Create a MAC ACL and configure the following rules for it:

■ Binding Configuration

  • Configure a permit rule to match packets with source MAC address 8C-DC-D4-40-A1-79 and destination MAC address 40-61-86-FC-71-56. This rule allows the manager of R&D department to visit internal forum at any time.
  • Configure a deny rule to match packets with destination MAC address 40-61-86-FC-71-56 and apply the time range of work hours. This rule forbids the employees in the R&D department to visit the internal forum during work hours.
  • Configure a permit rule to match all the packets that do not match neither of the above rules.

Bind the MAC ACL to port 1/0/2 so that the ACL rules will be applied to the computer of the devices in the R&D department which are restricted to the internal forum during work hours.

Demonstrated with T1600G-28TS, the following sections explain the configuration procedure in two ways: using the GUI and using the CLI.

3.1.3 Using the GUI

1) Choose the menu SYSTEM > Time Range > Time Range Config and click Add to load the following page. Create a time range named Work_time.

Figure 3-2 Configuring Time Range
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Time-Range Config Name: Work_time (1-16 characters) Holiday: Exclude Include Period Time Config Index Date Day Time Operation No entries in this table. Total 0 Discard Create

2) In the Period Time Config section, click + Add and the following window will pop up. Add the work hour of the company in the Period Time and click Save.

Figure 3-3 Adding Period Time
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image Period Time Config Date From Month: January ▼ Day: 1 ▼ Year: 2018 ▼ To Month: January ▼ Day: 1 ▼ Year: 2019 ▼ Time From: 08:00 (Format: HH:MM) To: 18:00 (Format: HH:MM) Day of Week ✓ Mon ✓ Tue ✓ Wed ✓ Thu ✓ Fri □ Sat □ Sun Cancel Save

3) After adding the Period Time, click Create to save the time range entry.

Figure 3-4 Creating Time Range
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image Time-Range Config Name: Work_time (1-16 characters) Holiday: Exclude Include Period Time Config Index Date Day Time Operation 0 January 1, 2018 - January 1, 20 19 Mon,Tue,Wed,Thu,Fri 08:00 - 18:00 Total: 0 Discard Create

4) Choose the menu SECURITY > ACL > ACL Config and click + Add to load the following page. Then create a MAC ACL for the marketing department.

Figure 3-5 Creating a MAC ACL
TP-LINK Omada TL-SG2008P - Using the GUI - 4

text_image ACL ACL Type: MAC ACL ACL ID: 100 (0-499) ACL Name: Forum_Control (Optional) Cancel Create

5) Click Edit ACL in the Operation column.

Figure 3-6 Editing the MAC ACL
TP-LINK Omada TL-SG2008P - Using the GUI - 5

text_image ACL Config Add Delete ACL Type ACL ID ACL Name Rules Operation MAC ACL 100 Forum_Control None Edit ACL Total: 1

6) On the ACL configuration page, click . + Add

Figure 3-7 Editing the MAC ACL
TP-LINK Omada TL-SG2008P - Using the GUI - 6

text_image ACL Details ACL Type: MAC ACL ACL ID: 100 ACL Name: Forum_Control ACL Rules Config Resequence Index Rule ID S-MAC D-MAC Action Total Matched Counter Operation No entries in this table. Total: 0

7) Configure rule 5 to permit packets with the source MAC address 8C-DC-D4-40-A1-79 and destination MAC address 40-61-86-FC-71-56.

Figure 3-8 Configuring Rule 5
TP-LINK Omada TL-SG2008P - Using the GUI - 7

text_image MAC ACL Rule ACL ID: 100 ACL Name: Forum_Control Rule ID: 5 Auto Assign Operation: Permit ✓ S-MAC: 8C-DC-D4-40-A1-79 (Format FF-FF-FF-FF-FF-FF) Mask: FF-FF-FF-FF-FF (Format FF-FF-FF-FF-FF-FF) ✓ D-MAC: 40-61-86-FC-71-56 (Format FF-FF-FF-FF-FF-FF) Mask: FF-FF-FF-FF-FF (Format FF-FF-FF-FF-FF-FF) □ VLAN ID: (1-4094) □ EtherType: (4-hex number) User Priority: Default Time Range: (Optional) Logging: Disable Policy □ Mirroring □ Redirect □ Rate Limit □ QoS Remark Discard Apply

8) In the same way, configure rule 15 to deny packets with destination MAC address 40-61-86-FC-71-56 and apply the time range of work hours.

Figure 3-9 Configuring Rule 15
TP-LINK Omada TL-SG2008P - Using the GUI - 8

text_image MAC ACL Rule ACL ID: 100 ACL Name: Forum_Control Rule ID: 15 Auto Assign Operation: Deny S-MAC: (Format: FF-FF-FF-FF-FF) Mask: (Format: FF-FF-FF-FF-FF) D-MAC: 40-61-86-FC-71-56 (Format: FF-FF-FF-FF-FF) Mask: FF-FF-FF-FF-FF (Format: FF-FF-FF-FF-FF) VLAN ID: (1-4094) EtherType: (4-hex number) User Priority: Default Time Range: Work_time (Optional) Logging: Disable Policy Mirroring Redirect Rate Limit QoS Remark Discard Apply

9) Configure rule 25 to permit all the packets that do not match neither of the above rules.

Figure 3-10 Configuring Rule 25
TP-LINK Omada TL-SG2008P - Using the GUI - 9

text_image MAC ACL Rule ACL ID: 100 ACL Name: Forum_Control Rule ID: 25 Auto Assign Operation Permit □ S-MAC: (Format: FF-FF-FF-FF-FF-FF) Mask: (Format: FF-FF-FF-FF-FF-FF) □ D-MAC: (Format: FF-FF-FF-FF-FF-FF) Mask: (Format: FF-FF-FF-FF-FF-FF) □ VLAN ID: (1-4094) □ EtherType: (4-hex number) User Priority: Default Time Range: (Optional) Logging: Disable Policy □ Mirroring □ Redirect □ Rate Limit □ QoS Remark Discard Apply

10) Choose the menu SECURITY > ACL > ACL Binding and click + Add to load the following page. Bind ACL 100 to port 1/0/2 to make it take effect.

Figure 3-11 Binding the ACL to Port 1/0/2
TP-LINK Omada TL-SG2008P - Using the GUI - 10

text_image Port Binding Config ACL: ID Name 100 Direction Ingress Port: 1/0/2 (Format: 1/0/1, input or choose below) UNIT 1 Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 4 6 8 10 12 14 16 18 20 22 24 26 28 Cancel Create

11) Click Save the settings.

3.1.4 Using the CLI

1) Create a time range entry.

Switch#config

Switch(config)#time-range Work_time

Switch(config-time-range)#holiday include

Switch(config-time-range)#absolute from 01/01/2018 to 01/01/2019

Switch(config-time-range)#periodic start 08:00 end 18:00 day-of-the-week 1,2,3,4,5

Switch(config-time-range)#end

Switch#copy running-config startup-config

2) Create a MAC ACL.

Switch#configure

Switch(config)#access-list create 100 name Forum_Control

3) Configure rule 5 to permit packets with source MAC address 8C-DC-D4-40-A1-79 and destination MAC address 40-61-86-FC-71-56.

Switch(config)#access-list mac 100 rule 5 permit logging disable smac 8C:DC:D4:40:A1:79 smask FF: FF: FF: FF: FF: FF dmac 40:61:86:FC:71:56 dmask FF: FF: FF: FF: FF

4) Configure rule 15 to deny packets with destination MAC address 40-61-86-FC-71-56.

Switch(config)#access-list mac 100 rule 15 deny logging disable dmac 40:61:86:FC:71:56 dmask FF: FF: FF: FF: FF tseg Work_time

5) Configure rule 25 to permit all the packets. The rule makes sure that the traffic to other network resources will not be blocked by the switch.

Switch(config)#access-list mac 100 rule 25 permit logging disable

6) Bind ACL100 to port 1/0/2.

Switch(config)#access-list bind 100 interface gigabitEthernet 1/0/2

Switch(config)#end

Switch#copy running-config startup-config

Verify the Configurations

Verify the MAC ACL 100:

Switch#show access-list 100

MAC access list 100 name: "Forum_Control"

rule 5 permit logging disable smac 8c:dc:d4:40:a1:79 smask ff:ff:ff:ff:ff:ff dmac 40:61:86:fc:71:56 dmask ff:ff:ff:ff:ff

rule 15 deny logging disable dmac 40:61:86:fc:71:56 dmask ff:ff:ff:ff:ff tseg "Work_time"

rule 25 permit logging disable

Switch#show access-list bind

ACL IDACL NAMEInterface/VIDDirection Type
--------------------
100Forum_ControlGi1/0/2IngressPort

3.2 Configuration Example for IP ACL

3.2.1 Network Requirements

As shown below, a company's internal server group can provide different types of services. Computers in the Marketing department are connected to the switch via port 1/0/1, and the internal server group is connected to the switch via port 1/0/2.

Figure 3-12 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["Internet"] --> B["Router"]
    B --> C["Gi1/0/1"]
    C --> D["Server Group"]
    D --> E["Marketing"]
    style A fill:#fff,stroke:#333
    style B fill:#fff,stroke:#333
    style C fill:#fff,stroke:#333
    style D fill:#fff,stroke:#333
    style E fill:#fff,stroke:#333

It is required that:

■ The Marketing department can only access internal server group in the intranet.
■ The Marketing department can only visit http and https websites on the internet.

3.2.2 Configuration Scheme

To meet the requirements above, you can set up packet filtering by creating an IP ACL and configuring rules for it.

■ ACL Configuration

Create an IP ACL and configure the following rules for it:

  • Configure a permit rule to match packets with source IP address 10.10.70.0/24, and destination IP address 10.10.80.0/24. This rule allows the Marketing department to access internal network servers from intranet.
  • Configure four permit rules to match the packets with source IP address 10.10.70.0/24, and destination ports TCP 80, TCP 443 and TCP/UDP 53. These allow the Marketing department to visit http and https websites on the internet.

The switch matches the packets with the rules in order, starting with Rule 1. If a packet matches a rule, the switch stops the matching process and initiates the action defined in the rule.

■ Binding Configuration

Bind the IP ACL to port 1/0/1 so that the ACL rules will apply to the Marketing department only.

Demonstrated with T1600G-28TS, the following sections explain the configuration procedure in two ways: using the GUI and using the CLI.

3.2.3 Using the GUI

1) Choose the menu SECURITY > ACL > ACL Config and click + Add to load the following page. Then create an IP ACL for the marketing department.

Figure 3-13 Creating an IP ACL
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image ACL ACL Type: IP ACL ACL ID: 500 (500-999) ACL Name: marketing (Optional) Cancel Create

2) Click Edit ACL in the Operation column.

Figure 3-14 Editing IP ACL
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image ACL Config ACL Type ACL ID ACL Name Rules Operation IP ACL 500 marketing None Edit ACL Total: 1

3) On the ACL configuration page, click . + Add

Figure 3-15 Editing IP AC
TP-LINK Omada TL-SG2008P - 3) On the ACL configuration page, click . + Add - 1

text_image ACL Details ACL Type: IP ACL ACL ID: 500 ACL Name: marketing ACL Rules Table Resequence Add Delete Refresh ID Rule ID S-IP D-IP IP Protocol Action Total Matched Counter Operation No Entries in this table. Total: 0

4) Configure rule 1 to permit packets with the source IP address 10.10.70.0/24 and destination IP address 10.10.80.0/24.

Figure 3-16 Configuring Rule 1
TP-LINK Omada TL-SG2008P - 4) Configure rule 1 to permit packets with the source IP address 10.10.70.0/24 and destination IP address 10.10.80.0/24. - 1

text_image IP ACL Rule ACL ID: 500 ACL Name: marketing Rule ID: 1 Auto Assign Operation: Permit ✓ S-IP: 10.10.70.0 (Format: 192.168.0.1) Mask: 255.255.255.0 (Format: 255.255.255.0) ✓ D-IP: 10.10.80.0 (Format: 192.168.0.1) Mask: 255.255.255.0 (Format: 255.255.255.0) IP Protocol: No Limit DSCP: No Limit IP ToS: (Optional, 0-15) IP Pre: (Optional, 0-7)

5) In the same way, configure rule 2 and rule 3 to permit packets with source IP 10.10.70.0 and destination port TCP 80 (http service port) and TCP 443 (https service port).

Figure 3-17 Configuring Rule 2
TP-LINK Omada TL-SG2008P - 4) Configure rule 1 to permit packets with the source IP address 10.10.70.0/24 and destination IP address 10.10.80.0/24. - 2

text_image IP ACL Rule ACL ID: 500 ACL Name: marketing Rule ID: 2 Auto Assign Operation: Permit ✓ S-IP: 10.10.70.0 (Format: 192.168.0.1) Mask: 255.255.255.0 (Format: 255.255.255.0) ☐ D-IP: Mask: IP Protocol: TCP URG: * ▼ ACK: * ▼ PSH: * RST: * ▼ SYN: * ▼ FIN: * ☐ S-Port Value: (0-65535) ✓ D-Port Value: 80 (0-65535) Mask: ffff (0000-ffff) DSCP: No Limit IP ToS: (Optional, 0-15)

Figure 3-18 Configuring Rule 3
TP-LINK Omada TL-SG2008P - 4) Configure rule 1 to permit packets with the source IP address 10.10.70.0/24 and destination IP address 10.10.80.0/24. - 3

text_image IP ACL Rule ACL ID: 500 ACL Name: marketing Rule ID: 3 Auto Assign Operation: Permit ✓ S-IP: 10.10.70.0 (Format: 192.168.0.1) Mask: 255.255.255.0 (Format: 255.255.255.0) ☐ D-IP: (Format: 192.168.0.1) Mask: (Format: 255.255.255.0) IP Protocol: TCP URG: * ▼ ACK: * ▼ PSH: * RST: * ▼ SYN: * ▼ FIN: * ☐ S-Port Value: (0-65535) ✓ D-Port Value: 443 (0-65535) Mask: ffff (0000-ffff) DSCP: No Limit IP ToS: (Optional, 0-15)

6) In the same way, configure rule 4 and rule 5 to permit packets with source IP 10.10.70.0 and with destination port TCP 53 or UDP 53 (DNS service port).

Figure 3-19 Configuring Rule 4
TP-LINK Omada TL-SG2008P - 4) Configure rule 1 to permit packets with the source IP address 10.10.70.0/24 and destination IP address 10.10.80.0/24. - 4

text_image IP ACL Rule ACL ID: 500 ACL Name: marketing Rule ID: 4 Auto Assign Operation: Permit ✓ S-IP: 10.10.70.0 (Format: 192.168.0.1) Mask: 255.255.255.0 (Format: 255.255.255.0) ☐ D-IP: Mask: IP Protocol: TCP URG: * ACK: PSH: * RST: * SYN: FIN: * ☐ S-Port Value: (0-05535) ✓ D-Port Value: 53 (0-05535) Mask: m DSCP: No Limit IP ToS: (Optional, 0-15)

Figure 3-20 Configuring Rule 5
TP-LINK Omada TL-SG2008P - 4) Configure rule 1 to permit packets with the source IP address 10.10.70.0/24 and destination IP address 10.10.80.0/24. - 5

text_image IP ACL Rule ACL ID: 500 ACL Name: marketing Rule ID: 5 Auto Assign Operation: Permit ✓ S-IP: 10.10.70.0 (Format 192.168.0.1) Mask: 255.255.255.0 (Format 255.255.255.0) ☐ D-IP: (Format 192.168.0.1) Mask: (Format 255.255.255.0) IP Protocol: UDP ☐ S-Port ✓ D-Port Value: (0-65535) Value: 53 (0-65535) Mask: (0000-fff) Mask: ffff (0000-fff) DSCP: No Limit IP ToS: (Optional, 0-15)

7) In the same way, configure rule 6 to deny packets with source IP 10.10.70.0.

Figure 3-21 Configuring Rule 6
TP-LINK Omada TL-SG2008P - 4) Configure rule 1 to permit packets with the source IP address 10.10.70.0/24 and destination IP address 10.10.80.0/24. - 6

text_image IP ACL Rule ACL ID: 500 ACL Name: marketing Rule ID: 6 Auto Assign Operation: Deny ✓ S-IP: 10.10.70.0 (Format: 192.168.0.1) Mask: 255.255.255.0 (Format: 255.255.255.0) ☐ D-IP: (Format: 192.168.0.1) Mask: (Format: 255.255.255.0) IP Protocol: No Limit DSCP: No Limit IP ToS: (Optional: 0-15) IP Pre: (Optional: 0-7)

8) Choose the menu SECURITY > ACL > ACL Binding and click + Add to load the following page. Bind ACL Marketing to port 1/0/1 to make it take effect.

Figure 3-22 Binding the ACL to Port 1/0/1
TP-LINK Omada TL-SG2008P - 4) Configure rule 1 to permit packets with the source IP address 10.10.70.0/24 and destination IP address 10.10.80.0/24. - 7

text_image Port Binding Config ACL: ID Name 500 Direction Ingress Port: 1/0/1 (Format:1/0/1, input or choose below) UNIT1 Select All Cancel Create

9) Click save the settings.

3.2.4 Using the CLI

1) Create an IP ACL.

Switch#configure

Switch(config)#access-list create 500 name marketing

2) Configure rule 1 to permit packets with source IP 10.10.70.0/24 and destination IP 10.10.80.0/24.

Switch(config)#access-list ip 500 rule 1 permit logging disable sip 10.10.70.0 sip-mask 255.255.255.0 dip 10.10.80.0 dmask 255.255.255.0

3) Configure rule 2 and Rule 3 to permit packets with source IP 10.10.70.0/24, and destination port TCP 80 (http service port) or TCP 443 (https service port).

Switch(config)#access-list ip 500 rule 2 permit logging disable sip 10.10.70.0 sip-mask 255.255.255.0 protocol 6 d-port 80 d-port-mask ffff

Switch(config)#access-list ip 500 rule 3 permit logging disable sip 10.10.70.0 sip-mask 255.255.255.0 protocol 6 d-port 443 d-port-mask ffff

4) Configure rule 4 and rule 5 to permit packets with source IP 10.10.70.0/24, and destination port TCP53 or UDP 53.

Switch(config)#access-list ip 500 rule 4 permit logging disable sip 10.10.70.0 sip-mask 255.255.255.0 protocol 6 d-port 53 d-port-mask ffff

Switch(config)#access-list ip 500 rule 5 permit logging disable sip 10.10.70.0 sip-amask 255.255.255.0 protocol 17 d-port 53 d-port-mask ffff

5) Configure rule 6 to deny packets with source IP 10.10.70.0/24.

Switch(config)#access-list ip 500 rule 2 deny logging disable sip 10.10.70.0 sip-mask 255.255.255.0

6) Bind ACL500 to port 1.

Switch(config)#access-list bind 500 interface gigabitEthernet 1/0/1

Switch(config)#end

Switch#copy running-config startup-config

Verify the Configurations

Verify the IP ACL 500:

Switch#show access-list 500

rule 1 permit logging disable sip 10.10.70.0 smask 255.255.255.0 dip 10.10.80.0 dmask 255.255.255.0

rule 2 permit logging disable sip 10.10.70.0 smask 255.255.255.0 protocol 6 d-port 80

rule 3 permit logging disable sip 10.10.70.0 smask 255.255.255.0 protocol 6 d-port 443

rule 4 permit logging disable sip 10.10.70.0 smask 255.255.255.0 protocol 6 d-port 53

rule 5 permit logging disable sip 10.10.70.0 smask 255.255.255.0 protocol 17 d-port 53

rule 6 deny loggin disable sip 10.10.70.0 smask 255.255.255.0

Switch#show access-list bind

ACL IDACL NAMEInterface/VIDDirectionType
--------------------
500marketingGi1/0/1IngressPort

3.3 Configuration Example for Combined ACL

3.3.1 Network Requirements

To enhance network security, a company requires that only the network administrator can log in to the switch through Telnet connection. The computers are connected to the switch via port 1/0/2. The network topology is shown as below.

Figure 3-23 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["Internet"] --> B["Router"]
    B --> C["Gi1/0/1"]
    B --> D["Gi1/0/2"]
    D --> E["Mac: 6C-62-6D-F5-BA-48"]

3.3.2 Configuration Scheme

To meet the requirements above, you can set up packet filtering by creating a Combined ACL and configuring rules for it.

■ ACL Configuration

Create a Combined ACL and configure the following rules for it:

  • Configure a permit rule to match packets with source MAC address 6C-62-6D-F5-BA-48, and destination port TCP 23. This rule allows the computer of the network administrator to access the switch through Telnet connection.
  • Configure a deny rule to match all the packets except the packets with source MAC address 6C-62-6D-F5-BA-48 and destination port TCP 23. This rule blocks the Telnet connection to the switch of other computers.
  • Configure a permit rule to match all the packets. This rule allows that other devices are given the network services except Telnet connection.

The switch matches the packets with the rules in order, starting with Rule 1. If a packet matches a rule, the switch stops the matching process and initiates the action defined in the rule.

■ Binding Configuration

Bind the Combined ACL to port 1/0/2 so that the ACL rules will be applied to the computer of the network administrator and the devices which are restricted to Telnet connection.

Demonstrated with T1600G-28TS, the following sections explain the configuration procedure in two ways: using the GUI and using the CLI.

3.3.3 Using the GUI

1) Choose the menu SECURITY > ACL > ACL Config and click + Add to load the following page. Then create a Combined ACL for the marketing department.

Figure 3-24 Creating an Combined ACL
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image ACL ACL Type: Combined ACL ACL ID: 1000 (1000-1499) ACL Name: ACL_Telnet (Optional) Cancel Create

2) Click Edit ACL in the Operation column.

Figure 3-25 Editing Combined ACL
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image ACL Config Add Delete □ ACL Type ACL ID ACL Name Rules Operation □ Combined ACL 1000 ACL_Telnet None Edit ACL Total: 1

3) On the ACL configuration page, click . + Add

Figure 3-26 Editing Combined ACL
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image ACL Details ACL Type: Combined ACL ACL ID: 1000 ACL Name: ACL_Telnet ACL Rules Config Resequence Add Delete Refresh Index Rule ID S-MAC D-MAC S-IP D-IP VID Action Total Matched Counter Operation No entries in this table. Total: 0

4) Configure rule 5 to permit packets with the source MAC address 6C-62-6D-F5-BA-48 and destination port TCP 23 (Telnet service port).

Figure 3-27 Configuring Rule 5
TP-LINK Omada TL-SG2008P - Using the GUI - 4

text_image Combined ACL Rule ACL ID: 1000 ACL Name: ACL_Telnet Rule ID: 5 Operation: Permit ✓ S-MAC: 6C-62-6D-F5-BA-48 Mask: FF-FF-FF-FF-FF (Format: FF-FF-FF-FF-FF-FF) (Format: FF-FF-FF-FF-FF-FF) ✓ D-MAC: Mask: (1-4094) ✓ EtherType: 0800 (4-hex number) ✓ S-IP: Mask: (Format: 192.168.0.1) ✓ D-IP: Mask: (Format: 192.168.0.1) (Format: 255.255.255.0) IP Protocol: TCP URG: * ▼ ACK: * ▼ PSH: * ▼ RST: * ▼ SYN: * ▼ FIN: * ▼ ✓ D-Port Value: (0-65535) Value: 23 (0-65535) Mask: (0000-FFFF) FFFF (0000-FFFF) DSCP: No Limit IP ToS: (Optional, 0-15)

5) Configure rule 15 to deny all the packets except the packet with source MAC address 6C-62-6D-F5-BA-48, and destination port TCP 23 (Telnet service port).

Figure 3-28 Configuring Rule 15
TP-LINK Omada TL-SG2008P - Using the GUI - 5

text_image Combined ACL Rule ACL ID: 1000 ACL Name: ACL_Telnet Rule ID: 15 Operation: Deny S-MAC: (Format: FF-FF-FF-FF-FF-FF) Mask: (Format: FF-FF-FF-FF-FF-FF) D-MAC: (Format: FF-FF-FF-FF-FF-FF) Mask: (Format: FF-FF-FF-FF-FF-FF) VLAN ID: (1-4094) EtherType: 0800 (4-hex number) S-IP: (Format: 192.168.0.1) Mask: (Format: 255.255.255.0) D-IP: (Format: 192.168.0.1) Mask: (Format: 255.255.255.0) IP Protocol: TCP URG: * ACK: * PSH: * RST: * SYN: * FIN: * S-Port Value: (0-65535) D-Port Value: 23 (0-65535) Mask: (0000-FFFF) FFFF (0000-FFFF) DSCP: No Limit IP ToS: (Optional, 0-15)

6) In the same way, configure rule 25 to permit all the packets. The rule makes sure that all devices can get other network services normally.

Figure 3-29 Configuring Rule 25
TP-LINK Omada TL-SG2008P - Using the GUI - 6

text_image Combined ACL Rule ACL ID: 1000 ACL Name: ACL_Telnet Rule ID: 25 Operation: Permit □ S-MAC: (Format: FF-FF-FF-FF-FF-FF) Mask: (Format: FF-FF-FF-FF-FF-FF) □ D-MAC: (Format: FF-FF-FF-FF-FF-FF) Mask: (Format: FF-FF-FF-FF-FF-FF) □ VLAN ID: (1-4094) □ EtherType: (4-hex number) □ S-IP: (Format: 192.168.0.1) Mask: (Format: 255.255.255.0) □ D-IP: (Format: 192.168.0.1) Mask: (Format: 255.255.255.0) IP Protocol: No Limit DSCP: No Limit IP ToS: (Optional, 0-15) IP Pre: (Optional, 0-7) User Priority: Default Time Range: (Optional) Logging: Disable

7) Choose the menu SECURITY > ACL > ACL Binding and click + Add to load the following page. Bind the Policy ACL_Telnet to port 1/0/2 to make it take effect.

Figure 3-30 Binding the ACL to Port 1/0/2
TP-LINK Omada TL-SG2008P - Using the GUI - 7

text_image Port Binding Config ACL: ID Name 1000 Direction Ingress Port: 1/0/2 (Format:1/0/1, input or choose below) UNIT1 Select All 1 3 5 7 9 11 13 15 17 19 21 23 25 27 2 4 6 8 10 12 14 16 18 20 22 24 26 28 Cancel Create

8) Click Save the settings.

3.3.4 Using the CLI

1) Create a Combined ACL.

Switch#configure

Switch(config)#access-list create 1000 name ACL_Telnet

2) Configure rule 5 to permit packets with the source MAC address 6C-62-6D-F5-BA-48 and destination port TCP 23 (Telnet service port).

Switch(config)#access-list combined 1000 rule 5 permit logging disable smac 6C:62:6D:F5:BA: 48 smask FF: FF: FF: FF: FF type 0800 protocol 6 d-port 23 d-port-mask FFFF

3) Configure rule 15 to deny all the packets except the packet with source MAC address 6C-62-6D-F5-BA-48, and destination port TCP 23 (Telnet service port).

Switch(config)#access-list combined 1000 rule 15 deny logging disable type 0800 protocol 6 d-port 23 d-port-mask FFFF

4) Configure rule 25 to permit all the packets. The rule makes sure that all devices can get other network services normally.

Switch(config)#access-list combined 1000 rule 25 permit logging disable type 0800 protocol 6 d-port 23 d-port-mask FFFF

5) Bind ACL500 to port 1/0/2.

Switch(config)#access-list bind 500 interface gigabitEthernet 1/0/2

Switch(config)#end

Switch#copy running-config startup-config

Verify the Configurations

Verify the Combined ACL 1000:

Switch#show access-list 1000

Combined access list 1000 name: "ACL_Telnet"

rule 5 permit logging disable smac 6c:62:6d:f5:ba:48 smask ff:ff:ff:ff:ff type 0800 protocol 6 d-port 23

rule 15 deny logging disable type 0800 protocol 6 d-port 23

rule 25 permit logging disable

Switch#show access-list bind

ACL ID ACL NAME Interface/VID Direction Type

1000 ACL_Telnet Gi1/0/2 Ingress Port

4 Appendix: Default Parameters

The default settings of ACL are listed in the following tables:

Table 4-1 MAC ACL

Parameter Default Setting
Operation Permit
User Priority No Limit
Time-Range No Limit

Table 4-2 IP ACL

Parameter Default Setting
Operation Permit
IP Protocol All
DSCP No Limit
IP ToS No Limit
IP Pre No Limit
Time-Range No Limit

Table 4-3 IPv6 ACL

Parameter Default Setting
Operation Permit
Time-Range No Limit

Table 4-4 Combined ACL

Parameter Default Setting
Operation Permit
Time-Range No Limit

Table 4-5 Policy

Parameter Default Setting
Mirroring Disabled
Redirect Disabled
Rate Limit Disabled
QoS Remark Disabled

Part 28

Configuring IPv4 IMPB

CHAPTERS

  1. IPv4 IMPB
  2. IP-MAC Binding Configuration
  3. ARP Detection Configuration
  4. IPv4 Source Guard Configuration
  5. Configuration Examples
  6. Appendix: Default Parameters

1 IPv4 IMPB

1.1 Overview

IPv4 IMPB (IP-MAC-Port Binding) is used to bind the IP address, MAC address, VLAN ID and the connected port number of the specified host. Basing on the binding table, the switch can prevent the ARP cheating attacks with the ARP Detection feature and filter the packets that don't match the binding entries with the IP Source Guard feature.

1.2 Supported Features

IP-MAC Binding

This feature is used to add binding entries. The binding entries can be manually configured, or learned by ARP scanning or DHCP snooping. The features ARP Detection and IPv4 Source Guard are based on the IP-MAC Binding entries.

ARP Detection

In an actual complex network, there are high security risks during ARP implementation procedure. The cheating attacks against ARP, such as imitating gateway, cheating gateway, cheating terminal hosts and ARP flooding attack, frequently occur to the network. ARP Detection can prevent the network from these ARP attacks.

■ Prevent ARP Cheating Attacks

Based on the IP-MAC Binding entries, the ARP Detection can be configured to detect the ARP packets and filter the illegal ones so as to prevent the network from ARP cheating attacks.

■ Prevent ARP Flooding Attack

You can limit the receiving speed of the legal ARP packets on the port to avoid ARP flooding attack.

IPv4 Source Guard

IPv4 Source Guard is used to filter the IPv4 packets based on the IP-MAC Binding table. Only the packets that match the binding rules are forwarded.

2 IP-MAC Binding Configuration

You can add IP-MAC Binding entries in three ways:

■ Manual Binding
■ Via ARP Scanning
■ Via DHCP Snooping

Additionally, you can view, search and edit the entries in the Binding Table.

2.1 Using the GUI

2.1.1 Binding Entries Manually

You can manually bind the IP address, MAC address, VLAN ID and the Port number together on the condition that you have got the detailed information of the hosts.

Choose the menu SECURITY > IPv4 IMPB > IP-MAC Binding > Manual Binding and click

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 1

Add

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 2

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 3

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 4

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 5

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 6

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 7

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 8

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 9

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 10

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 11

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 12

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 13

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 14

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 15

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 16

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 17

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 18

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 19

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 20

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 21

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 22

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 23

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 24

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 25

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 26

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 27

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 28

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 29

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 30

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 31

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 32

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 33

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 34

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 35

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 36

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 37

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 38

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 39

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 40

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 41

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 42

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 43

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 44

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 45

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 46

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 47

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 48

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 49

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 50

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 51

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 52

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 53

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 54

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 55

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 56

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 57

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 58

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 59

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 60

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 61

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 62

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 63

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 64

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 65

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 66

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 67
Figure 2-1 Manual Binding

IPv4-MAC Binding

Host Name:

IP Address:

MAC Address:

VLAN ID:

Protect Type:

Port:

TP-LINK Omada TL-SG2008P - IPv4-MAC Binding - 1

text_image None

(20 characters maximum)

(Format: 192.168.0.1)

(Format: 00-00-00-00-00-01)

(1-4094)

(Format: 1/0/1, input or choose below)

UNIT1
TP-LINK Omada TL-SG2008P - IPv4-MAC Binding - 2

text_image 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27

TP-LINK Omada TL-SG2008P - IPv4-MAC Binding - 3
Selected

TP-LINK Omada TL-SG2008P - IPv4-MAC Binding - 4
Unselected

TP-LINK Omada TL-SG2008P - IPv4-MAC Binding - 5
Not Available

Cancel

Apply

Follow these steps to manually create an IP-MAC Binding entry:

1) Enter the following information to specify a host.

Host Name Enter the host name for identification.

IP Address Enter the IP address.

MAC Address Enter the MAC address.

VLAN ID Enter the VLAN ID.

2) Select protect type for the entry.

Protect Type

Select the protect type for the entry. The entry will be applied to the specific feature. The following options are provided:

None: This entry will not be applied to any feature.

ARP Detection: This entry will be applied to the ARP Detection feature.

IP Source Guard: This entry will be applied to the IPv4 Source Guard feature.

Both: This entry will be applied to both of the features.

3) Enter or select the port that is connected to this host.
4) Click Apply.

2.1.2 Binding Entries via ARP Scanning

With ARP Scanning, the switch sends the ARP request packets of the specified IP field to the hosts. Upon receiving the ARP reply packet, the switch can get the IP address, MAC address, VLAN ID and the connected port number of the host. You can bind these entries conveniently.

TP-LINK Omada TL-SG2008P - Binding Entries via ARP Scanning - 1

Note:

Before using this feature, make sure that your network is safe and the hosts are not suffering from ARP attacks at present; otherwise, you may obtain incorrect IP-MAC Binding entries. If your network is being attacked, it's recommended to bind the entries manually.

Choose the menu SECURITY > IPv4 IMPB > IP-MAC Binding > ARP Scanning to load the following page.

Figure 2-2 ARP Scanning
TP-LINK Omada TL-SG2008P - Note: - 1

text_image Scanning Option Starting IP Address: 192.168.0.1 (Format: 192.168.0.1) Ending IP Address: 192.168.0.254 (Format: 192.168.0.1) VLAN ID: 1 (1-4094) Scan Scanning Result Delete Host Name IP Address MAC Address VLAN ID Port Protect Type ✓ --- 192.168.0.28 c4-6e-1f-bf-72-51 1 1/0/20 None □ --- 192.168.0.52 00-0a-eb-13-23-7b 1 1/0/20 None □ --- 192.168.0.73 00-0a-eb-00-13-01 1 1/0/20 None □ --- 192.168.0.200 00-19-66-35-e1-b0 1 1/0/20 None □ --- 192.168.0.225 ea-23-51-06-22-52 1 1/0/20 None □ --- 192.168.0.226 00-0a-eb-13-23-97 1 1/0/20 None □ --- 192.168.0.253 14-cc-20-00-00-13 1 1/0/20 None 1 entry selected. Cancel Bind

Follow these steps to configure IP-MAC Binding via ARP scanning:

1) In the Scanning Option section, specify an IP address range and a VLAN ID. Then click Scan to scan the entries in the specified IP address range and VLAN.

Starting IP Specify an IP range by entering a start and end IP address. Address/Ending IP Address

VLAN ID Specify a VLAN ID.

2) In the Scanning Result section, select one or more entries and configure the relevant parameters. Then click Bind.

Host Name Enter a host name for identification.

IP Address Displays the IP address.

MAC Address Displays the MAC address.

VLAN ID Displays the VLAN ID.

Port Displays the port number.

Protect Type

Select the protect type for the entry. The entry will be applied to to the specific feature. The following options are provided:

None: This entry will not be applied to any feature.

ARP Detection: This entry will be applied to the ARP Detection feature.

IP Source Guard: This entry will be applied to the IP Source Guard feature.

Both This entry will be applied to both of the features.

2.1.3 Binding Entries via DHCP Snooping

With DHCP Snooping enabled, the switch can monitor the IP address obtaining process of the host, and record the IP address, MAC address, VLAN ID and the connected port number of the host.

Choose the menu SECURITY > IPv4 IMPB > IP-MAC Binding > DHCP Snooping to load the following page.

Figure 2-3 DHCP Snooping
TP-LINK Omada TL-SG2008P - Binding Entries via DHCP Snooping - 1

text_image Global Config DHCP Snooping: ☐ Enable Apply VLAN Config Filter by VLAN: From ☐ To ☐ Apply VLAN ID Status 1 Disabled Total: 1 1 entry selected. Cancel Apply Port Config UNIT1 LAGS Port Maximum Entries LAG 1/0/1 512 -- 1/0/2 512 -- 1/0/3 512 -- 1/0/4 512 -- 1/0/5 512 -- 1/0/6 512 -- 1/0/7 512 -- 1/0/8 512 -- 1/0/9 512 -- 1/0/10 512 -- Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure IP-MAC Binding via DHCP Snooping:

1) In the Global Config section, globally enable DHCP Snooping. Click Apply.
2) In the VLAN Config section, enable DHCP Snooping on a VLAN or range of VLANs. Click Apply.

VLAN ID Displays the VLAN ID.

Status Enable or disable DHCP Snooping on the VLAN.

3) In the Port Config section, configure the maximum number of binding entries a port can learn via DHCP snooping. Click Apply.

Port Displays the port number.

Maximum Entries Configure the maximum number of binding entries a port can learn via DHCP snooping

LAG Displays the LAG that the port is in.

4) The learned entries will be displayed in the Binding Table. You can go to SECURITY > IPv4 IMPB > IP-MAC Binding > Binding Table to view or edit the entries.

2.1.4 Viewing the Binding Entries

In the Binding Table, you can view, search and edit the specified binding entries.

Choose the menu SECURITY > IPv4 IMPB > IP-MAC Binding > Binding Table to load the following page.

Figure 2-4 Binding Table
TP-LINK Omada TL-SG2008P - Viewing the Binding Entries - 1

text_image Binding Table Source: All IP Address: (Format: 192.168.0.1) Search Delete Host Name IP Address MAC Address VLAN ID Port Protect Type Source --- 192.168.0.28 c4-6e-1f-bf-72-51 1 1/0/20 None ARP Scanning PC1 192.168.0.98 74-d4-35-76-a4-d8 1 1/0/6 None Manual Binding 1 entry selected. Cancel Apply

You can specify the search criteria to search your desired entries.

Source Select the source of the entry and click Search.

All: Displays the entries from all sources.

Manual Binding: Displays the manually bound entries.

ARP Scanning: Displays the binding entries learned from ARP Scanning.

DHCP Snooping: Displays the binding entries learned from DHCP Snooping.

IP Enter an IP address and click Search to search the specific entry.

Additionally, you select one or more entries to edit the host name and protect type and click Apply.

Host Name Enter a host name for identification.

IP Address Displays the IP address.

MAC Address Displays the MAC address.

VLAN ID Displays the VLAN ID.
Port Displays the port number.
Protect TypeSelect the protect type for the entry. The entry will be applied to to the specific feature. The following options are provided:None: This entry will not be applied to any feature.ARP Detection: This entry will be applied to the ARP Detection feature.IP Source Guard: This entry will be applied to the IP Source Guard feature.Both: This entry will be applied to both of the features.
Source Displays the source of the entry.

2.2 Using the CLI

Binding entries via ARP scanning is not supported by the CLI. The following sections introduce how to bind entries manually and via DHCP Snooping and view the binding entries.

2.2.1 Binding Entries Manually

You can manually bind the IP address, MAC address, VLAN ID and the Port number together on the condition that you have got the detailed information of the hosts.

Follow these steps to manually bind entries:

Step 1 configure

Enter global configuration mode.

Step 2 ip source bindinghostname ip-addr mac-addr vlan vlan-id interface { fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel port-channel-id } { none | arp-detection | ip-verify-source | both}
Manually bind the host name, IP address, MAC address, VLAN ID and port number of the host, and configure the protect type for the host.
hostname: Specify a name for the host. It contains 20 characters at most.
ip-addr: Enter the IP address of the host.
mac-addr: Enter the MAC address of the host, in the format of xx:xx:xx:xx:xx:xx.
vlan-id: Enter the VLAN ID of the host.
port: Enter the number of the port on which the host is connected.
none | arp-detection | ip-verify-source | both: Specify the protect type for the entry. None indicates this entry will not be applied to any feature; arp-detection indicates this entry will be applied to ARP Detection; ip-verify-source indicates this entry will be applied to IPv4 Source Guard.

Step 3 show ip source binding
Verify the binding entry.
Step 4 end
Return to privileged EXEC mode.
Step 5 copy running-config startup-config
Save the settings in the configuration file.

The following example shows how to bind an entry with the hostname host1, IP address 192.168.0.55, MAC address 74:d4:35:76:a4:d8, VLAN ID 10, port number 1/0/5, and enable this entry for the ARP detection feature.

Switch#configure

Switch(config)#ip source binding host1 192.168.0.55 74:d4:35:76:a4:d8 vlan 10 interface gigabitEthernet 1/0/5 arp-detection

Switch(config)#show ip source binding

UHostIP-AddrMAC-AddrVIDPortACLSOURCE
---------------------------
1host1192.168.0.5574:d4:35:76:a4:d810Gi1/0/5ARP-DManual

Notice:

  1. Here, 'ARP-D' for 'ARP-Detection', and 'IP-V-S' for 'IP-Verify-Source'.

Switch(config)#end

Switch#copy running-config startup-config

2.2.2 Binding Entries via DHCP Snooping

Follow these steps to bind entries via DHCP Snooping:

Step 1 configure

Enter global configuration mode.

Step 2 ip dhcp snooping

Globally enable DHCP Snooping.

Step 3 ip dhcp snooping vlan

vlan-range

Enable DHCP Snooping on the specified VLAN.

vlan-range: Enter the vlan range in the format of 1-3, 5.

Step 4 interface {

fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range

gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list |

interface port-channel port-channel-id | interface range port-channel port-channel-id-list

}

Enter interface configuration mode.

Step 5 ip dhcp snooping max-entries

value

Configure the maximum number of binding entries the port can learn via DHCP snooping.

value: Enter the value of maximum number of entries. The valid values are from 0 to 512.

Step 6 show ip dhcp snooping

Verify global configuration of DHCP Snooping.

Step 7 end

Return to privileged EXEC mode.

Step 8 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable DHCP Snooping globally and on VLAN 5, and set the maximum number of binding entries port 1/0/1 can learn via DHCP snooping as 100:

Switch#configure

Switch(config)#ip dhcp snooping

Switch(config)#ip dhcp snooping vlan 5

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#ip dhcp snooping max-entries 100

Switch(config-if)#show ip dhcp snooping

Global Status: Enable

VLAN ID: 5

Switch(config-if)#show ip dhcp snooping interface gigabitEthernet 1/0/1

Interface max-entries LAG


Gi1/0/1 100 N/A

Switch(config-if)#end

Switch#copy running-config startup-config

2.2.3 Viewing Binding Entries

On privileged EXEC mode or any other configuration mode, you can use the following command to view binding entries:

show ip source binding

View the information of binding entries, including the host name, IP address, MAC address, VLAN ID, port number and protect type.

3 ARP Detection Configuration

To complete ARP Detection configuration, follow these steps:

1) Add IP-MAC Binding entries.
2) Enable ARP Detection.
3) Configure ARP Detection on ports.
4) View ARP statistics.

3.1 Using the GUI

3.1.1 Adding IP-MAC Binding Entries

In ARP Detection, the switch detects the ARP packets based on the binding entries in the IP-MAC Binding Table. So before configuring ARP Detection, you need to complete IP-MAC Binding configuration. For details, refer to IP-MAC Binding Configuration.

3.1.2 Enabling ARP Detection

Choose the menu SECURITY > IPv4 IMPB > ARP Detection > Global Config to load the following page.

Figure 3-1 ARP Detection Global Config
TP-LINK Omada TL-SG2008P - Enabling ARP Detection - 1

text_image Global Config ARP Detect: □ Enable Validate Source MAC : □ Enable Validate Destination MAC: □ Enable Validate IP: □ Enable Apply VLAN Config ✓ VLAN ID Status Log Status ✓ 1 Disabled Disabled Total: 1 1 entry selected. Cancel Apply

Follow these steps to enable ARP Detection:

1) In the Global Config section, enable ARP Detection and configure the related parameters. Click Apply.

ARP Detect Enable or disable ARP Detection globally.
Validate Source MACEnable or disable the switch to check whether the source MAC address and the sender MAC address are the same when receiving an ARP packet. If not, the ARP packet will be discarded.
Validate Destination MACEnable or disable the switch to check whether the destination MAC address and the target MAC address are the same when receiving an ARP reply packet. If not, the ARP packet will be discarded.
Validate IPEnable or disable the switch to check whether the sender IP address of all ARP packets and the target IP address of ARP reply packets are legal. The illegal ARP packets will be discarded, including broadcast addresses, multicast addresses, Class E addresses, loopback addresses (127.0.0.0/8) and the following address: 0.0.0.0.

2) In the VLAN Config section, enable ARP Detection on the selected VLANs. Click Apply.

VLAN ID Displays the VLAN ID.
Status Enable or disable ARP Detection on the VLAN.
Log StatusEnable or disable Log feature on the VLAN. With this feature enabled, the switch generates a log when an illegal ARP packet is discarded.

3.1.3 Configuring ARP Detection on Ports

Choose the menu SECURITY > IPv4 IMPB > ARP Detection >Port Config to load the following page.

Figure 3-2 ARP Detection on Port
TP-LINK Omada TL-SG2008P - Configuring ARP Detection on Ports - 1

text_image Port Config UNIT1 LAGS Port Trust Status Limit Rate pps (0-300) Current Speed (pps) Burst Interval seconds (1-15) Status Operation LAG ✓ 1/0/1 Disabled 100 0 1 Normal --- --- □ 1/0/2 Disabled 100 0 1 Normal --- --- □ 1/0/3 Disabled 100 0 1 Normal --- --- □ 1/0/4 Disabled 100 0 1 Normal --- --- □ 1/0/5 Disabled 100 0 1 Normal --- --- □ 1/0/6 Disabled 100 0 1 Normal --- --- □ 1/0/7 Disabled 100 0 1 Normal --- --- □ 1/0/8 Disabled 100 0 1 Normal --- --- □ 1/0/9 Disabled 100 0 1 Normal --- --- □ 1/0/10 Disabled 100 0 1 Normal --- --- Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure ARP Detection on ports:

1) Select one or more ports and configure the parameters.

Trust StatusEnable or disable this port to be a trusted port. On a trusted port, the ARP packets are forwarded directly without checked. The specific ports, such as up-link ports and routing ports are suggested to be set as trusted.
Limit Rate Specify the maximum number of the ARP packets that can be received on the port per second.
Current Speed Displays the current speed of receiving the ARP packets on the port.
Burst IntervalSpecify a time range. If the speed of received ARP packets reaches the limit for this time range, the port will be shut down.
Status Displays the status of the ARP attack:Normal:The forwarding of ARP packets on the port is normal.Down:The transmission speed of the legal ARP packet exceeds the defined value. The port will be shut down for 300 seconds. You can also click the Recovery button to recover
OperationIf Status is changed to Down, there will be a Recover button. You can click the button to restore the port to the normal status.
LAG Displays the LAG that the port is in.

2) Click Apply.

3.1.4 Viewing ARP Statistics

You can view the number of the illegal ARP packets received on each port, which facilitates you to locate the network malfunction and take the related protection measures.

Choose the menu SECURITY > IPv4 IMPB > ARP Detection > ARP Statistics to load the following page.

Figure 3-3 View ARP Statistics
TP-LINK Omada TL-SG2008P - Viewing ARP Statistics - 1

text_image Auto Refresh Auto Refresh: ☐ Enable Apply Illegal ARP Packets VLAN ID Forwarded Dropped 1 0 0 Total: 1

In the Auto Refresh section, you can enable the auto refresh feature and specify the refresh interval, and thus the web page will be automatically refreshed.

In the Illegal ARP Packet section, you can view the number of illegal ARP packets in each VLAN.

VLAN ID Displays the VLAN ID.

Forwarded Displays the number of forwarded ARP packets in this VLAN.

Dropped Displays the number of dropped ARP packets in this VLAN.

3.2 Using the CLI

3.2.1 Adding IP-MAC Binding Entries

In ARP Detection, the switch detects the ARP packets based on the binding entries in the IP-MAC Binding Table. So before configuring ARP Detection, you need to complete IP-MAC Binding configuration. For details, refer to IP-MAC Binding Configuration.

3.2.2 Enabling ARP Detection

Follow these steps to enable ARP Detection:

Step 1 configure

Enter global configuration mode.

Step 2 ip arp inspection

Globally enable the ARP Detection feature.

Step 3 ip arp inspection validate { src-mac | dst-mac | ip }

Configure the switch to check the IP address or MAC address of the received packets.

src-mac: Enable the switch to check whether the source MAC address and the sender MAC address are the same when receiving an ARP packet. If not, the ARP packet will be discarded.

dst-mac: Enable the switch to check whether the sender IP address of all ARP packets and the target IP address of ARP reply packets are legal. The illegal packets will be discarded.

ip: Enable or disable the switch to check whether the sender IP address of all ARP packets and the target IP address of ARP reply packets are legal. The illegal ARP packets will be discarded, including broadcast addresses, multicast addresses, Class E addresses, loopback addresses (127.0.0.0/8) and the following address: 0.0.0.0.

Step 4 ip arp inspection vlan

vlan-list

Enable ARP Detection on one or more 802.1Q VLANs that already exist.

vlan-list: Enter the VLAN ID. The format is 1,5-9.

Step 5 ip arp inspection vlanvlan-list logging(Optional) Enable the Log feature to make the switch generate a log when an ARP packet is discarded.vlan-list; Enter the VLAN ID. The format is 1,5-9.
Step 6 show ip arp inspectionVerify the ARP Detection configuration.
Step 7 endReturn to privileged EXEC mode.
Step 8 copy running-config startup-configSave the settings in the configuration file.

The following example shows how to enable ARP Detection globally and on VLAN 2, and enable the switch to check whether the source MAC address and the sender MAC address are the same when receiving an ARP packet:

Switch#configure

Switch(config)#ip arp inspection

Switch(config)#ip arp inspection validate src-mac

Switch(config)#ip arp inspection vlan 2

Switch(config)#show ip arp inspection

Global Status: Enable

Verify SMAC: Enable

Verify DMAC: Disable

Verify IP: Disable

Switch(config)#show ip arp inspection vlan

VIDEnable statusLog Status
------------
1DisableDisable
2EnableDisable

Switch(config)#end

Switch#copy running-config startup-config

3.2.3 Configuring ARP Detection on Ports

Follow these steps to configure ARP Detection on ports:

Step 1 configureEnter global configuration mode.
Step 2 interface { fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list } Enter interface configuration mode.
Step 3 ip arp inspection trustConfigure the port as a trusted port, on which the ARP Detection function will not take effect. The specific ports, such as up-linked ports and routing ports are suggested to be set as trusted ports.
Step 4 ip arp inspection limit-rate valueSpecify the maximum number of the ARP packets can be received on the port per second.value: Specify the limit rate value. The valid values are from 0 to 300 pps (packets/second), and the default value is 100.
Step 5 ip arp inspection burst-interval valueSpecify a time range. If the speed of received ARP packets reaches the limit for this time range, the port will be shut down.value: Specify the time range. The valid values are from 1 to 15 seconds, and the default value is 1 second.
Step 6 show ip arp inspection interfaceView the configurations and status of the ports.
Step 7 show ip arp inspection vlanView the configurations and status of the VLANs.
Step 8 ip arp inspection recover(Optional) For ports on which the speed of receiving ARP packets has exceeded the limit, use this command to restore the port from Down status to Normal status.
Step 9 endReturn to privileged EXEC mode.
Step 10 copy running-config startup-configSave the settings in the configuration file.

The following example shows how to set port 1/02 as a trusted port, and set limit-rate as 20 pps and burst interval as 2 seconds on port 1/0/2:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/2

Switch(config-if)#ip arp inspection trust

Switch(config-if)#ip arp inspection limit-rate 20

Switch(config-if)#ip arp inspection burst-interval 2

Switch(config-if)#show ip arp inspection interface gigabitEthernet 1/0/2

InterfaceTrust statelimit Rate(pps)Current speed(pps)Burst IntervalStatusLAG
Gi1/0/2Enable2002---N/A

Switch(config-if)#end

Switch#copy running-config startup-config

The following example shows how to restore the port 1/0/1 that is in Down status to Normal status:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#ip arp inspection recover

Switch(config-if)#end

Switch#copy running-config startup-config

3.2.4 Viewing ARP Statistics

On privileged EXEC mode or any other configuration mode, you can use the following command to view ARP statistics:

show ip arp inspection statistics

View the ARP statistics on each port, including the number of forwarded ARP packets and the number of dropped ARP packets.

4 IPv4 Source Guard Configuration

To complete IPv4 Source Guard configuration, follow these steps:

1) Add IP-MAC Binding entries.
2) Configure IPv4 Source Guard.

4.1 Using the GUI

4.1.1 Adding IP-MAC Binding Entries

In IPv4 Source Guard, the switch filters the packets that do not match the rules of IPv4-MAC Binding Table. So before configuring ARP Detection, you need to complete IP-MAC Binding configuration. For details, refer to IP-MAC Binding Configuration.

4.1.2 Configuring IPv4 Source Guard

Choose the menu SECURITY > IPv4 IMPB > IPv4 Source Guard to load the following page.

Figure 4-1 IPv4 Source Guard Config
TP-LINK Omada TL-SG2008P - Configuring IPv4 Source Guard - 1

text_image Global Config IPv4 Source Guard Log: Enable Apply Port Config UNIT1 LAGS □ Port Security Type LAG ✓ 1/0/1 Disable -- □ 1/0/2 Disable -- □ 1/0/3 Disable -- □ 1/0/4 Disable -- □ 1/0/5 Disable -- □ 1/0/6 Disable -- □ 1/0/7 Disable -- □ 1/0/8 Disable -- □ 1/0/9 Disable -- □ 1/0/10 Disable -- Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure IPv4 Source Guard:

1) In the Global Config section, choose whether to enable the Log feature. Click Apply.

IPv4 Source Guard LogEnable or disable IPv4 Source Guard Log feature. With this feature enabled, the switch generates a log when illegal packets are received.

2) In the Port Config section, configure the protect type for ports and click Apply.

Port Displays the port number.

Security TypeSelect Security Type on the port for IPv4 packets. The following options are provided:

Disable: The IP Source Guard feature is disabled on the port.

SIP+MAC: Only the packet with its source IP address, source MAC address and port number matching the IPv4-MAC binding rules can be processed, otherwise the packet will be discarded.

SIP: Only the packet with its source IP address and port number matching the IPv4-MAC binding rules can be processed, otherwise the packet will be discarded.

Note: SIP is only available on certain devices.

LAG Displays the LAG that the port is in.

4.2 Using the CLI

4.2.1 Adding IP-MAC Binding Entries

In IPv4 Source Guard, the switch filters the packets that do not match the rules of IPv4-MAC Binding Table. So before configuring ARP Detection, you need to complete IP-MAC Binding configuration. For details, refer to IP-MAC Binding Configuration.

4.2.2 Configuring IPv4 Source Guard

Follow these steps to configure IPv4 Source Guard:

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet

port | range fastEthernet port-list | gigabitEthernet port | range

gigabitEthernet port-list| ten-gigabitEthernet port | range ten-gigabitEthernet port-list}

Enter interface configuration mode.

Step 3 ip verify source { sip+mac | sip }

Enable IP Source Guard for IPv4 packets.

sip+mac: Only the packet with its source IP address, source MAC address and port number matching the IP-MAC binding rules can be processed, otherwise the packet will be discarded.

sip: Only the packet with its source IP address and port number matching the IP-MAC binding rules can be processed, otherwise the packet will be discarded.

Note: SIP is only available on certain devices.

Step 4 show ip verify source [interface {fastEthernet

port | gigabitEthernet port | ten-

gigabitEthernet port | port-channel port-channel-id } ]

Verify the IP Source Guard configuration for IPv4 packets.

Step 5 end

Return to privileged EXEC mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable IPv4 Source Guard on port 1/0/1:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#ip verify source sip+mac

Switch(config-if)#show ip verify source interface gigabitEthernet 1/0/1

Port

Security-Type

LAG


[EMPTY]


Gi1/0/1

SIP+MAC

N/A

Switch(config-if)#end

Switch#copy running-config startup-config

5 Configuration Examples

5.1 Example for ARP Detection

5.1.1 Network Requirements

As shown below, User 1 and User 2 are legal users in the LAN and connected to port 1/0/1 and port 1/0/2. Both of them are in the default VLAN 1. The router has been configured with security feature to prevent attacks from the WAN. Now the network administrator wants to configure Switch A to prevent ARP attacks from the LAN.

Figure 5-1 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["Internet"] -->|WAN| B["Router"]
    B -->|LAN| C["Switch A"]
    C -->|Gi1/0/3| D["Attacker"]
    C -->|Gi1/0/1 Gi1/0/2| E["User 1"]
    C -->|Gi1/0/2| F["User 2"]
    C --> G["74-D3-45-32-B6-8D 192.168.0.31/24"]
    C --> H["88-A9-D4-54-FD-C3 192.168.0.33/24"]

5.1.2 Configuration Scheme

To meet the requirement, you can configure ARP Detection to prevent the network from ARP attacks in the LAN.

The overview of configurations on the switch is as follows:

1) Configure IP-MAC Binding. The binding entries for User 1 and User 2 should be manually bound.

2) Configure ARP Detection globally.

3) Configure ARP Detection on ports. Since port 1/0/3 is connected to the gateway router, set port 1/0/3 as trusted port. To prevent ARP flooding attacks, limit the speed of receiving the legal ARP packets on all ports.

Demonstrated with T1600G-28TS, the following sections provide configuration procedure in two ways: using the GUI and using the CLI.

5.1.3 Using the GUI

1) Choose the menu SECURITY > IPv4 IMBP > IP-MAC Binding > Manual Binding and click to load the following page. Enter the host name, IP address, MAC address and VLAN ID of User 1, select the protect type as ARP Detection, and select port 1/0/1 on the panel. Click Apply.

Figure 5-2 Binding Entry for User 1
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image IPv4-MAC Binding Host Name: User1 (20 characters maximum) IP Address: 192.168.0.31 (Format: 192.168.0.1) MAC Address: 74-D3-45-32-B6-8D (Format: 00-00-00-00-00-01) VLAN ID: 1 (1-4094) Protect Type: ARP Detection Port: 1/0/1 (Format: 1/0/1, input or choose below) UNIT 1 LAGS 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Apply

2) On the same page, add a binding entry for User 2. Enter the host name, IP address, MAC address and VLAN ID of User 2, select the protect type as ARP Detection, and select port 1/0/2 on the panel. Click Apply.

Figure 5-3 Binding Entry for User 2
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image IPv4-MAC Binding Host Name: User2 (20 characters maximum) IP Address: 192.168.0.33 (Format: 192.168.0.1) MAC Address: 88-A9-D4-54-FD-C3 (Format: 00-00-00-00-00-01) VLAN ID: 1 (1-4094) Protect Type: ARP Detection Port: 1/0/2 (Format: 1/0/1, input or choose below) UNIT1 LAGS 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Apply

3) Choose the menu SECURITY > IPv4 IMBP > ARP Detection > Global Config to load the following page. Enable APP Detect, Validate Source MAC, Validate Destination MAC and Validate IP, and click Apply. Select VLAN 1, change Status as Enabled and click Apply.

Figure 5-4 Enable ARP Detection
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image Global Config ARP Detect Enable Validate Source MAC : Enable Validate Destination MAC: Enable Validate IP: Enable Apply VLAN Config VLAN ID Status Log Status Enable 1 Enabled Disabled Total: 1 1 entry selected. Cancel Apply

4) Choose the menu SECURITY > IPv4 IMBP > ARP Detection > Port Config to load the following page. By default, all ports are enabled with ARP Detection and ARP flooding defend. Configure port 1/0/3 as trusted port and keep other defend parameters as default. Click Apply.

Figure 5-5 Port Config
TP-LINK Omada TL-SG2008P - Using the GUI - 4

text_image Port Config UNIT1 LAGS Port Trust Status Limit Rate pps (0-300) Current Speed (pps) Burst Interval seconds (1-15) Status Operation LAG Enable 1/0/1 Disabled 100 0 1 Normal --- --- 1/0/2 Disabled 100 0 1 Normal --- --- ✓ 1/0/3 Enabled 100 0 1 Normal --- --- 1/0/4 Disabled 100 0 1 Normal --- --- 1/0/5 Disabled 100 0 1 Normal --- --- 1/0/6 Disabled 100 0 1 Normal --- --- 1/0/7 Disabled 100 0 1 Normal --- --- 1/0/8 Disabled 100 0 1 Normal --- --- 1/0/9 Disabled 100 0 1 Normal --- --- 1/0/10 Disabled 100 0 1 Normal --- --- Total: 28 1 entry selected. Cancel Apply

5) Click Save the settings.

5.1.4 Using the CLI

1) Manually bind the entries for User 1 and User 2.

Switch_A#configure

Switch_A(config)#ip source binding User1 192.168.0.31 74:d3:45:32:b6:8d vlan 1 interface gigabitEthernet 1/0/1 arp-detection

Switch_A(config)#ip source binding User1 192.168.0.32 88:a9:d4:54:fd:c3 vlan 1 interface gigabitEthernet 1/0/2 arp-detection

2) Enable ARP Detection globally and on VLAN 1.

Switch_A(config)#ip arp inspection

Switch_A(config)#ip arp inspection vlan 1

3) Configure port 1/0/3 as trusted port.

Switch_A(config)#interface gigabitEthernet 1/0/3

Switch_A(config-if)#ip arp inspection trust

Switch_A(config-if)#end

Switch_A#copy running-config startup-config

Verify the Configuration

Verify the IP-MAC Binding entries:

Switch_A#show ip source binding

UHostIP-AddrMAC-AddrVIDPortACLSOURCE
---------------------------
1User1192.168.0.3174:d3:45:32:b6:8d1Gi1/0/1ARP-DManual
1User2192.168.0.3388:a9:d4:54:fd:c31Gi1/0/2ARP-DManual

Notice:

  1. Here, 'ARP-D' for 'ARP-Detection', and 'IP-V-S' for 'IP-Verify-Source'.

Verify the global configuration of ARP Detection:

Switch_A#show ip arp inspection

Global Status: Enable

Verify SMAC: Enable

Verify DMAC: Enable

Verify IP: Enable

Verify the ARP Detection configuration on VLAN:

Switch_A#show ip arp inspection vlan

VID Enable status Log Status

1 Enable Disable

Verify the ARP Detection configuration on ports:

Switch_A#show ip arp inspection interface

Interface Trust state limit Rate(pps) Current speed(pps) Burst Interval Status LAG

[Non-Text]

Gi1/0/1 Disable 100 0 1 --- N/A

Gi1/0/2 Disable 100 0 1 --- N/A

Gi1/0/3 Enable 100 0 1 --- N/A

...

5.2 Example for IP Source Guard

5.2.1 Network Requirements

As shown below, the legal host connects to the switch via port 1/0/1 and belongs to the default VLAN 1. It is required that only the legal host can access the network via port 1/0/1, and other unknown hosts will be blocked when trying to access the network via ports 1/0/1-3.

Figure 5-6 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["Computer 1"] -->|GI1/0/1| B["Switch"]
    C["Computer 2"] -->|GI1/0/2| B
    D["Computer 3"] -->|GI1/0/3| B
    E["Legal Host 192.168.0.100 74-D3-45-32-B5-6D"] --> B
    B -->|GI1/0/2| F["Unknown Host"]

5.2.2 Configuration Scheme

To implement this requirement, you can use IP-MAC Binding and IP Source Guard to filter out the packets received from the unknown hosts. The overview of configuration on the switch is as follows:

1) Bind the MAC address, IP address, connected port number and VLAN ID of the legal host with IP-MAC Binding.
2) Enable IP Source Guard on ports 1/0/1-3.

Demonstrated with T1600G-28TS, the following sections provide configuration procedure in two ways: using the GUI and using the CLI.

5.2.3 Using the GUI

1) Choose the menu SECURITY > IPv4 IMPB > IP-MAC Binding > Manual Binding and click to load the following page. Enter the host name, IP address, MAC address and VLAN ID of the legal host, select the protect type as , and select port 1/0/1 on the panel. Click Apply.

Figure 5-7 Manual Binding
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image IPv4-MAC Binding Host Name: LegalHost (20 characters maximum) IP Address: 192.168.0.100 (Format: 192.168.0.1) MAC Address: 74-D3-45-32-B5-6D (Format: 00-00-00-00-00-01) VLAN ID: 1 (1-4094) Protect Type: IP Source Guard Port: 1/0/1 (Format: 1/0/1, input or choose below) UNIT1 LAGS 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Apply

2) Choose the menu SECURITY > IPv4 IMPB > IPv4 Source Guard to load the following page. Enable IPv4 Source Guard Logging to make the switch generate logs when receiving illegal packets, and click Apply. Select ports 1/0/1-3, configure the Security Type as SIP+MAC, and click Apply.

Figure 5-8 IPv4 Source Guard
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image Global Config IPv4 Source Guard Logging: ✓ Enable Port Config UNIT1 LAGS Port Security Type LAG SIP+MAC ✓ 1/0/1 SIP+SMAC -- ✓ 1/0/2 SIP+SMAC -- ✓ 1/0/3 SIP+SMAC -- ✓ 1/0/4Disable -- ✓ 1/0/5Disable -- ✓ 1/0/6Disable -- ✓ 1/0/7Disable -- ✓ 1/0/8Disable -- ✓ 1/0/9Disable -- ✓ 1/0/10Disable -- Total: 28 3 entries selected Cancel Apply

3) Click Save the settings.

5.2.4 Using the CLI

1) Manually bind the IP address, MAC address, VLAN ID and connected port number of the legal host, and apply this entry to the IP Source Guard feature.

Switch#configure

Switch(config)#ip source binding legal-host 192.168.0.100 74:d3:45:32:b5:6d vlan 1 interface gigabitEthernet 1/0/1 ip-verify-source

2) Enable the log feature and IP Source Guard on ports 1/0/1-3.

Switch(config)# ip verify source logging

Switch(config)# interface range gigabitEthernet 1/0/1-3

Switch(config-if-range)#ip verify source sip+mac

Switch(config-if-range)#end

Switch#copy running-config startup-config

Verify the Configuration

Verify the binding entry:

Switch#show ip source binding

UHostIP-AddrMAC-AddrVIDPortACLSOURCE
---------------------------
1User1192.168.0.10074:d3:45:32:b5:6d1Gi1/0/1IP-V-SManual

Notice:
1. Here, 'ARP-D' for 'ARP-Detection', and 'IP-V-S' for 'IP-Verify-Source'.

Verify the configuration of IP Source Guard:

Switch#show ip verify source

IP Source Guard log: Enabled

Default settings of DHCP Snooping are listed in the following table:

Table 6-1 DHCP Snooping

Parameter Default Setting
Global Config
DHCP Snooping Disabled
VLAN Config
Status Disabled
Port Config
Maximum Entry 512

Default settings of ARP Detection are listed in the following table:

Table 6-2 ARP Detection

Parameter Default Setting
Global Config
ARP Detect Disabled
Validate Source MAC Disabled
Validate Destination MAC Disabled
Validate IP Disabled
VLAN Config
Status Disabled
Log Status Disabled
Port Config
Trust StatusDisabled
Limit Rate100 pps
Burst Interval 1 second
ARP Statistics
Auto Refresh Disabled
Refresh Interval 5 seconds

Default settings of IPv4 Source Guard are listed in the following table:

Table 6-3 ARP Detection

Parameter Default Setting
Global Config
IPv4 Source Guard Log: Disabled
Port Config
Security Type Disabled

Part 29

Configuring IPv6 IMPB

CHAPTERS

  1. IPv6 IMPB
  2. IPv6-MAC Binding Configuration
  3. ND Detection Configuration
  4. IPv6 Source Guard Configuration
  5. Configuration Examples
  6. Appendix: Default Parameters

1 IPv6 IMPB

1.1 Overview

IPv6 IMPB (IP-MAC-Port Binding) is used to bind the IPv6 address, MAC address, VLAN ID and the connected port number of the specified host. Basing on the binding table, the switch can prevent ND attacks with the ND Detection feature and filter the packets that don't match the binding entries with the IPv6 Source Guard feature.

1.2 Supported Features

IPv6-MAC Binding

This feature is used to add binding entries. The binding entries can be manually configured, or learned by ND Snooping or DHCPv6 snooping. The features ND Detection and IPv6 Source Guard are based on the IPv6-MAC Binding entries.

ND Detection

Because of the absence of security mechanism, IPv6 ND (Neighbor Discovery) protocol is easy to be exploited by attackers. ND detection feature uses the entries in the IPv6-MAC binding table to filter the forged ND packets and prevent the ND attacks.

The application topology of ND Detection is as the following figure shows. The port that is connected to the gateway should be configured as trusted port, and other ports should be configured as untrusted ports. The forwarding principles of ND packets are as follows:

■ All ND packets received on the trusted port will be forwarded without checked.
■ RS (Router Solicitation) and NS (Neighbor Solicitation) packets with their source IPv6 addresses unspecified, such as the RS packet for IPv6 address request and the NS packet for duplicate address detection, will not be checked on both kinds of ports.
■ RA (Router Advertisement) and RR (Router Redirect) packets received on the untrusted port will be discarded directly, and other ND packets will be checked: The switch will use the IPv6-MAC binding table to compare the IPv6 address, MAC address, VLAN ID and receiving port between the entry and the ND packet. If a match is found, the ND packet is considered legal and will be forwarded; if no match is found, the ND packet is considered illegal and will be discarded.

Figure 1-1 Network Topology of ND Detection
TP-LINK Omada TL-SG2008P - ND Detection - 1

flowchart
graph TD
    A["User A"] -->|Untrusted Port| B["Switch"]
    C["Attacker"] -->|Untrusted Port| B
    B -->|Trusted Port| D["Gateway"]
    D --> E["Internet"]

IPv6 Source Guard

IPv6 Source Guard is used to filter the IPv6 packets based on the IPv6-MAC Binding table. Only the packets that match the binding rules are forwarded.

2 IPv6-MAC Binding Configuration

You can add IPv6-MAC Binding entries in three ways:

■ Manual Binding
■ Via ND Snooping
■ Via DHCPv6 Snooping

Additionally, you can view, search and edit the entries in the Binding Table.

2.1 Using the GUI

2.1.1 Binding Entries Manually

You can manually bind the IPv6 address, MAC address, VLAN ID and the Port number together on the condition that you have got the detailed information of the hosts.

Choose the menu SECURITY > IPv6 IMPB > IPv6-MAC Binding > Manual Binding and click

TP-LINK Omada TL-SG2008P - Binding Entries Manually - 1

Add

to load the following page.

Figure 2-1 Manual Binding
TP-LINK Omada TL-SG2008P - Binding Entries Manually - 2

text_image IPv4-MAC Binding Host Name: (20 characters maximum) IPv6 Address: (Format: 2001::1) MAC Address: (Format: 00-00-00-00-00-01) VLAN ID: (1-4094) Protect Type: None Port: (Format:1/0/1, input or choose below) UNIT1 LAGS 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Bind

Follow these steps to manually create an IPv6-MAC Binding entry:

1) Enter the following information to specify a host.

Host Name Enter the host name for identification.

IPv6 Address Enter the IPv6 address.

MAC Address Enter the MAC address.

VLAN ID Enter the VLAN ID.

2) Select protect type for the entry.

Protect Type

Select the protect type for the entry. The entry will be applied to to the specific feature. The following options are provided:

None: This entry will not be applied to any feature.

ND Detection: This entry will be applied to the ND Detection feature.

IPv6 Source Guard: This entry will be applied to the IPv6 Source Guard feature.

Both: This entry will be applied to both of the features.

3) Enter or select the port that is connected to this host.
4) Click Apply.

2.1.2 Binding Entries via ND Snooping

With ND Snooping, the switch monitors the ND packets, and records the IPv6 addresses, MAC addresses, VLAN IDs and the connected port numbers of the IPv6 hosts. You can bind these entries conveniently.

TP-LINK Omada TL-SG2008P - Binding Entries via ND Snooping - 1

Note:

Before using this feature, make sure that your network is safe and the hosts are not suffering from ND attacks at present; otherwise, you may obtain incorrect IPv6-MAC Binding entries. If your network is being attacked, it's recommended to bind the entries manually.

Choose the menu SECURITY > IPv6 IMPB > IPv6-MAC Binding > ND Snooping to load the following page.

Figure 2-2 ND Snooping
TP-LINK Omada TL-SG2008P - Note: - 1

text_image ND Snooping ND Snooping: Enable Apply VLAN Config Filter by VLAN: From To Apply VLAN ID Status 1 Disabled 6 Disabled Total: 2 1 entry selected. Cancel Apply Port Config UNIT1 LAGS Port Maximum Entries LAG 1/0/1 512 -- 1/0/2 512 -- 1/0/3 512 -- 1/0/4 512 -- 1/0/5 512 -- 1/0/6 512 -- 1/0/7 512 -- 1/0/8 512 -- 1/0/9 512 -- 1/0/10 512 -- Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure IPv6-MAC Binding via ND Snooping:

1) In the ND Snooping section, enable ND Snooping and click Apply.

2) In the VLAN Config section, select one or more VLANs and enable ND Snooping. Click Apply.

VLAN ID Displays the VLAN ID.

Status Enable or disable ND Snooping on the VLAN.

3) In the Port Config section, configure the maximum number of entries a port can learn via ND snooping. Click Apply.

Port Displays the port number.

Maximum Entries Configure the maximum number of binding entries a port can learn via ND snooping.

LAG Displays the LAG that the port is in.

4) The learned entries will be displayed in the Binding Table. You can go to SECURITY > IPv6 IMPB > IPv6-MAC Binding > Binding Table to view or edit the entries.

2.1.3 Binding Entries via DHCPv6 Snooping

With DHCPv6 Snooping enabled, the switch can monitor the IP address obtaining process of the host, and record the IPv6 address, MAC address, VLAN ID and the connected port number of the host.

Choose the menu SECURITY > IPv6 IMPB > IPv6-MAC Binding > DHCPv6 Snooping to load the following page.

Figure 2-3 DHCPv6 Snooping
TP-LINK Omada TL-SG2008P - Binding Entries via DHCPv6 Snooping - 1

text_image Global Config DHCPv6 Snooping: Enable Apply VLAN Config Filter by VLAN: From To Apply VLAN ID Status 1 Disabled 6 Disabled Total: 2 1 entry selected. Cancel Apply Port Config UNIT1 LAGS Port Maximum Entries LAG 1/0/1 512 --- 1/0/2 512 --- 1/0/3 512 --- 1/0/4 512 --- 1/0/5 512 --- 1/0/6 512 --- 1/0/7 512 --- 1/0/8 512 --- 1/0/9 512 --- 1/0/10 512 --- Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure IPv6-MAC Binding via DHCPv6 Snooping:

1) In the Global Config section, globally enable DHCPv6 Snooping. Click Apply.
2) In the VLAN Config section, enable DHCPv6 Snooping on a VLAN or range of VLANs. Click Apply.

VLAN ID Displays the VLAN ID.

Status Enable or disable DHCPv6 Snooping on the VLAN.

3) In the Port Config section, configure the maximum number of binding entries a port can learn via DHCPv6 snooping. Click Apply.

Port Displays the port number.

Maximum Entries Configure the maximum number of binding entries a port can learn via DHCPv6 snooping.

LAG Displays the LAG that the port is in.

4) The learned entries will be displayed in the Binding Table. You can go to SECURITY > IPv6 IMPB > IPv6-MAC Binding > Binding Table to view or edit the entries.

2.1.4 Viewing the Binding Entries

In the Binding Table, you can view, search and edit the specified binding entries.

Choose the menu SECURITY > IPv6 IMPB > IPv6-MAC Binding > Binding Table to load the following page.

Figure 2-4 Binding Table
TP-LINK Omada TL-SG2008P - Viewing the Binding Entries - 1

text_image Binding Table Source: All IP Address: (Format: 192.168.0.1) Search Delete Host Name IP Address MAC Address VLAN ID Port Protect Type Source --- 192.168.0.20 c4-6e-1f-bf-72-51 1 1/0/20 None ARP Scanning PC1 192.168.0.98 74-d4-35-76-a4-d8 1 1/0/6 None Manual Binding 1 entry selected. Cancel Apply

You can specify the search criteria to search your desired entries.

Source Select the source of the entry and click Search.

All: Displays the entries from all sources.

Manual Binding: Displays the manually bound entries.

ND Snooping: Displays the binding entries learned from ND Snooping.

DHCPv6 Snooping: Displays the binding entries learned from DHCP Snooping.

IP Enter an IP address and click Search to search the specific entry.

Additionally, you select one or more entries to edit the host name and protect type and click Apply.

Host Name Enter a host name for identification.

IP Address Displays the IPv6 address.

MAC Address Displays the MAC address.

VLAN ID Displays the VLAN ID.
Port Displays the port number.
Protect TypeSelect the protect type for the entry. The entry will be applied to to the specific feature. The following options are provided:None: This entry will not be applied to any feature.ND Detection: This entry will be applied to the ND Detection feature.IPv6 Source Guard: This entry will be applied to the IP Source Guard feature.Both: This entry will be applied to both of the features.
Source Displays the source of the entry.

2.2 Using the CLI

The following sections introduce how to bind entries manually and via ND Snooping and DHCP Snooping, and how to view the binding entries.

2.2.1 Binding Entries Manually

You can manually bind the IPv6 address, MAC address, VLAN ID and the Port number together on the condition that you have got the detailed information of the hosts.

Follow these steps to manually bind entries:

Step 1 configure

Enter global configuration mode.

Step 2 ipv6 source binding hostname ipv6-addr mac-addr vlan vlan-id interface {fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel port-channel-id} {none | nd-detection | ipv6-verify-source | both}

Manually bind the host name, IP address, MAC address, VLAN ID and port number of the host, and configure the protect type for the host.

hostname: Specify a name for the host. It contains 20 characters at most.

ipv6-addr: Enter the IPv6 address of the host.

mac-addr: Enter the MAC address of the host, in the format of xx:xx:xx:xx:xx:xx.

vlan-id: Enter the VLAN ID of the host.

port: Enter the number of the port on which the host is connected.

none | nd-detection | ipv6-verify-source | both: Specify the protect type for the entry. None indicates this entry will not be applied to any feature; nd-detection indicates this entry will be applied to ND Detection; ipv6-verify-source indicates this entry will be applied to IP Source Guard; both indicates this entry will be applied to both ND Detection and IP Source Guard.

Step 3 show ip source binding

Verify the binding entry.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to bind an entry with the hostname host1, IPv6 address 2001:0:9d38:90d5::34, MAC address AA-BB-CC-DD-EE-FF, VLAN ID 10, port number 1/0/5, and enable this entry for ND Detection.

Switch#configure

Switch(config)#ipv6 source binding host1 2001:0:9d38:90d5::34 aa:bb:cc:dd:ee:ff vlan 10 interface gigabitEthernet 1/0/5 nd-detection

Switch(config)#show ipv6 source binding

UHostIP-AddrMAC-AddrVIDPortACLSource
---------------------------
1host12001:0:9d38:90d5::34aa:bb:cc:dd:ee:ff10Gi1/0/5ND-DManual

Switch(config)#end

Switch#copy running-config startup-config

2.2.2 Binding Entries via ND Snooping

Follow these steps to bind entries via ND Snooping:

Step 1 configure

Enter global configuration mode.

Step 2 ipv6 nd snooping

Globally enable ND Snooping.

Step 3 ipv6 nd snooping vlan

vlan-range

Enable ND Snooping on the specified VLAN.

vlan-range: Enter the vlan range in the format of 1-3, 5.

Step 4 interface {

fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range

gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list

Enter interface configuration mode.

Step 5 ipv6 nd snooping max-entries

value

Configure the maximum number of ND binding entries a port can learn via ND snooping.

value: Enter the maximum number of ND binding entries a port can learn via ND snooping.

The valid values are from 0 to 1024, and the default is 1024.

Step 6 show ipv6 nd snooping

Verify the global configuration of IPv6 ND Snooping

Step 7 show ipv6 nd snooping interface { gigabitEthernet port }

fastEthernet port | gigabitEthernet port | ten-

Verify the IPv6 ND Snooping configuration of the specific port.

Step 8 end

Return to privileged EXEC mode.

Step 9 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable ND Snooping globally and on VLAN 1.

Switch#configure

Switch(config)#ipv6 nd snooping

Switch(config)#ipv6 nd snooping vlan 1

Switch(config)#show ipv6 nd snooping

Global Status: Enable

VLAN ID: 1

Switch(config)#end

Switch#copy running-config startup-config

The following example shows how to configure the maximum number of entries that can be learned on port 1/0/1:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#ipv6 nd snooping max-entries 1000

Switch(config-if)#show ipv6 nd snooping interface gigabitEthernet 1/0/1

Interfacemax-entriesLAG
------------
Gi1/0/11000N/A

Switch(config-if)#end

Switch#copy running-config startup-config

2.2.3 Binding Entries via DHCPv6 Snooping

Follow these steps to bind entries via DHCP Snooping:

Step 1 configure

Enter global configuration mode.

Step 2 ipv6 dhcp snooping

Globally enable DHCPv6 Snooping.

Step 3 ipv6 dhcp snooping vlan

vlan-range

Enable DHCPv6 Snooping on the specified VLAN.

vlan-range: Enter the vlan range in the format of 1-3, 5.

Step 4 interface {

fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range

gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | interface port-channel port-channel-id | interface range port-channel port-channel-id-lis }

Enter interface configuration mode.

Step 5 ipv6 dhcp snooping max-entries

value

Configure the maximum number of binding entries the port can learn via DHCPv6 snooping.

value: Enter the value of maximum number of entries. The valid values are from 0 to 512.

Step 6 show ip dhcp snooping

Verify global configuration of DHCPv6 Snooping.

Step 7 end

Return to privileged EXEC mode.

Step 8 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable DHCPv6 Snooping globally and on VLAN 5, and set the maximum number of binding entries port 1/0/1 can learn via DHCPv6 snooping as 100:

Switch#configure

Switch(config)#ipv6 dhcp snooping

Switch(config)#ipv6 dhcp snooping vlan 5

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#ipv6 dhcp snooping max-entries 100

Switch(config-if)#show ipv6 dhcp snooping

Global Status: Enable

VLAN ID: 5

Switch(config-if)#show ipv6 dhcp snooping interface gigabitEthernet 1/0/1

Interface max-entries LAG

Gi1/0/1 100 N/A

Switch(config-if)#end

Switch#copy running-config startup-config

2.2.4 Viewing Binding Entries

On privileged EXEC mode or any other configuration mode, you can use the following command to view binding entries:

show ipv6 source binding

View the information of binding entries, including the host name, IP address, MAC address, VLAN ID, port number and protect type.

3 ND Detection Configuration

To complete ND Detection configuration, follow these steps:

1) Add IPv6-MAC Binding entries.
2) Enable ND Detection.
3) Configure ND Detection on ports.
4) View ND statistics.

3.1 Using the GUI

3.1.1 Adding IPv6-MAC Binding Entries

The ND Detection feature allows the switch to detect the ND packets based on the binding entries in the IPv6-MAC Binding Table and filter out the illegal ND packets. Before configuring ND Detection, complete IPv6-MAC Binding configuration. For details, refer to IPv6-MAC Binding Configuration.

3.1.2 Enabling ND Detection

Choose the menu SECURITY > IPv6 IMPB > ND Detection > Global Config to load the following page.

Figure 3-1 ND Detection Global Config
TP-LINK Omada TL-SG2008P - Enabling ND Detection - 1

text_image Global Config ND Detection: Enable Apply VLAN Config VLAN ID Status Log Status 1 Disabled Disabled 8 Disabled Disabled Total: 2 1 entry selected. Cancel Apply

Follow these steps to enable ND Detection:

1) In the Global Config section, enable ND Detection and configure the related parameters. Click Apply.

ND Detection Enable or disable ND Detection globally.

2) In the VLAN Config section, enable ND Detection on the selected VLANs. Click Apply.

VLAN ID Displays the VLAN ID.

Status Enable or disable ND Detection on the VLAN.

Log Status

Enable or disable Log feature on the VLAN. With this feature enabled, the switch generates a log when an illegal ND packet is discarded.

3.1.3 Configuring ND Detection on Ports

Choose the menu SECURITY > IPv6 IMPB > ND Detection > Port Config to load the following page.

Figure 3-2 ND Detection on Port
TP-LINK Omada TL-SG2008P - Configuring ND Detection on Ports - 1

text_image Port Config UNIT1 LAGS Port Trust Status LAG ✓ 1/0/1 Disabled --- □ 1/0/2 Disabled --- □ 1/0/3 Disabled --- □ 1/0/4 Disabled --- □ 1/0/5 Disabled --- □ 1/0/6 Disabled --- □ 1/0/7 Disabled --- □ 1/0/8 Disabled --- □ 1/0/9 Disabled --- □ 1/0/10 Disabled --- Total: 28 1 entry selected. Cancel Apply

Follow these steps to configure ND Detection on ports:

1) Select one or more ports and configure the parameters.

Port Displays the port number.

Trust Status

Enable or disable this port to be a trusted port. On a trusted port, the ND packets are forwarded directly without checked. The specific ports, such as up-link ports and routing ports are suggested to be set as trusted.

LAG Displays the LAG that the port is in.

2) Click Apply.

3.1.4 Viewing ND Statistics

You can view the number of the illegal ND packets received on each port, which facilitates you to locate the network malfunction and take the related protection measures.

Choose the menu SECURITY > IPv6 IMPB > ND Detection > ND Statistics to load the following page.

Figure 3-3 View ND Statistics
TP-LINK Omada TL-SG2008P - Viewing ND Statistics - 1

text_image Auto Refresh Auto Refresh: ☐ Enable Apply Illegal ND Packets VLAN ID Forwarded Dropped 1 0 0 8 0 0 Total: 2

In the Auto Refresh section, you can enable the auto refresh feature and specify the refresh interval, and thus the web page will be automatically refreshed.

In the Illegal ND Packet section, you can view the number of illegal ND packets in each VLAN.

VLAN ID Displays the VLAN ID.

Forwarded Displays the number of forwarded ND packets in this VLAN.

Dropped Displays the number of dropped ND packets in this VLAN.

3.2 Using the CLI

3.2.1 Adding IPv6-MAC Binding Entries

The ND Detection feature allows the switch to detect the ND packets based on the binding entries in the IPv6-MAC Binding Table and filter out the illegal ND packets. Before configuring ND Detection, complete IPv6-MAC Binding configuration. For details, refer to IPv6-MAC Binding Configuration.

3.2.2 Enabling ND Detection

Follow these steps to enable ND Detection:

Step 1 configure

Enter global configuration mode.

Step 2 ipv6 nd detection

Globally enable the ND Detection feature.

Step 3 ipv6 nd detection vlanvlan-range
Enable ND Detection on the specified VLAN.
vlan-range: Enter the vlan range in the format of 1-3, 5.
Step 4 ipv6 nd detection vlanvlan-range logging(Optional) Enable the Log feature to make the switch generate a log when an ND packet is discarded.vlan-range: Enter the vlan range in the format of 1-3, 5.
Step 5 show ipv6 nd detection
Verify the global ND Detection configuration.
Step 6 end
Return to privileged EXEC mode.
Step 7 copy running-config startup-config
Save the settings in the configuration file.

The following example shows how to enable ND Detection globally and on VLAN 1:

Switch#configure

Switch(config)#ipv6 nd detection

Switch(config)#ipv6 nd detection vlan 1

Switch(config)#show ipv6 nd detection

Global Status: Enable

Switch(config)#show ipv6 nd detection vlan

VID Enable status Log Status

1 Enable Disable

Switch(config)#end

Switch#copy running-config startup-config

3.2.3 Configuring ND Detection on Ports

Follow these steps to configure ND Detection on ports:

Step 1 configure

Enter global configuration mode.

Step 2 interface { fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list }Enter interface configuration mode.
Step 3 ipv6 nd detection trustConfigure the port as a trusted port, on which the ND packets will not be checked. The specific ports, such as up-linked ports and routing ports are suggested to be set as trusted ports.
Step 4 show ipv6 nd detection interface { fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel port-channel-id }Verify the global ND Detection configuration of the port.
Step 5 endReturn to privileged EXEC mode.
Step 6 copy running-config startup-configSave the settings in the configuration file.

The following example shows how to configure port 1/0/1 as trusted port:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#ipv6 nd detection trust

Switch(config-if)#show ipv6 nd detection interface gigabitEthernet 1/0/1

Interface Trusted LAG


Gi1/0/1 Enable N/A

Switch(config-if)#end

Switch#copy running-config startup-config

3.2.4 Viewing ND Statistics

On privileged EXEC mode or any other configuration mode, you can use the following command to view ND statistics:

show ipv6 nd detection statistics

View the ND statistics on each port, including the number of forwarded ND packets and the number of dropped ND packets.

4 IPv6 Source Guard Configuration

To complete IPv6 Source Guard configuration, follow these steps:

1) Add IP-MAC Binding entries.
2) Configure IPv6 Source Guard.

4.1 Using the GUI

4.1.1 Adding IPv6-MAC Binding Entries

The ND Detection feature allows the switch to detect the ND packets based on the binding entries in the IPv6-MAC Binding Table and filter out the illegal ND packets. Before configuring ND Detection, complete IPv6-MAC Binding configuration. For details, refer to IPv6-MAC Binding Configuration.

4.1.2 Configuring IPv6 Source Guard

Before configuring IPv6 Source Guard, you need to configure the SDM template as EnterpriseV6.

Choose the menu SECURITY > IPv6 IMPB > IPv6 Source Guard to load the following page.

Figure 4-1 IPv6 Source Guard Config
TP-LINK Omada TL-SG2008P - Configuring IPv6 Source Guard - 1

text_image IPv6 Source Guard Config UNIT1 LAGS Port Security Type LAG ✓ 1/0/1 Disable --- □ 1/0/2 Disable --- □ 1/0/3 Disable --- □ 1/0/4 Disable --- □ 1/0/5 Disable --- □ 1/0/6 Disable --- □ 1/0/7 Disable --- □ 1/0/8 Disable --- □ 1/0/9 Disable --- □ 1/0/10 Disable --- Total: 23 1 entry selected. Cancel Apply

Follow these steps to configure IPv6 Source Guard:

1) Select one or more ports and configure the protect type for ports.

Port Displays the port number.
Security TypeSelect Security Type on the port for IPv6 packets. The following options are provided:Disable:The IP Source Guard feature is disabled on the port.SIPv6+MAC:Only the packet with its source IPv6 address, source MAC address and port number matching the IPv6-MAC binding rules can be processed, otherwise the packet will be discarded.SIPv6:Only the packet with its source IPv6 address and port number matching the IPv6-MAC binding rules can be processed, otherwise the packet will be discarded.

LAG Displays the LAG that the port is in.

2) Click Apply.

4.2 Using the CLI

4.2.1 Adding IPv6-MAC Binding Entries

The ND Detection feature allows the switch to detect the ND packets based on the binding entries in the IPv6-MAC Binding Table and filter out the illegal ND packets. Before configuring ND Detection, complete IPv6-MAC Binding configuration. For details, refer to IPv6-MAC Binding Configuration.

4.2.2 Configuring IPv6 Source Guard

Before configuring IPv6 Source Guard, you need to configure the SDM template as EnterpriseV6.

Follow these steps to configure IPv6 Source Guard:

Step 1 configure

Enter global configuration mode.

Step 2 interface {fastEthernet

port | range fastEthernet port-list | gigabitEthernet port | range

gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list}

Enter interface configuration mode.

Step 3 ipv6 verify source {sipv6+mac | sipv6}

Enable IPv6 Source Guard for IPv6 packets.

sipv6+mac: Only the packet with its source IPv6 address, source MAC address and port number matching the IPv6-MAC binding rules can be processed, otherwise the packet will be discarded.

sipv6: Only the packet with its source IPv6 address and port number matching the IPv6-MAC binding rules can be processed, otherwise the packet will be discarded.

Step 4 show ipv6 verify source [interface {fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel port-channel-id}] Verify the IP Source Guard configuration for IPv6 packets.

Step 5 end

Return to privileged EXEC mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable IPv6 Source Guard on port 1/0/1:

Switch#configure

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#ipv6 verify source sipv6+mac

Switch(config-if)#show ipv6 verify source interface gigabitEthernet 1/0/1

5.1 Example for ND Detection

5.1.1 Network Requirements

As shown below, User 1 and User 2 are legal IPv6 users in the LAN and connected to port 1/0/1 and port 1/0/2. Both of them are in the default VLAN 1. The router has been configured with security feature to prevent attacks from the WAN. Now the network administrator wants to configure Switch A to prevent ND attacks from the LAN.

Figure 5-1 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["Internet"] -->|WAN| B["Router"]
    B -->|LAN| C["Switch A"]
    C -->|Gi1/0/3| D["Attacker"]
    C -->|Gi1/0/2| E["Computer 1 74-D3-45-32-B6-8D 2001::5"]
    C -->|Gi1/0/1| F["Computer 2 88-A9-D4-54-FD-C3 2001::6"]

5.1.2 Configuration Scheme

To meet the requirement, you can configure ND Detection to prevent the network from ND attacks in the LAN.

The overview of configurations on the switch is as follows:

1) Configure IPv6-MAC Binding. The binding entries for User 1 and User 2 should be manually bound.

2) Configure ND Detection globally.

3) Configure ND Detection on ports. Since port 1/0/3 is connected to the gateway router, set port 1/0/3 as trusted port.

Demonstrated with T1600G-28TS, the following sections provide configuration procedure in two ways: using the GUI and using the CLI.

5.1.3 Using the GUI

1) Choose the menu SECURITY > IPv6 IMBP > IPv6-MAC Binding > Manual Binding and click to load the following page. Enter the host name, IPv6 address, MAC address and VLAN ID of User 1, select the protect type as ND Detection, and select port 1/0/1 on the panel. Click Apply.

Figure 5-2 Binding Entry for User 1
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image IPv6-MAC Binding Host Name: User1 (20 characters maximum) IPv6 Address: 2001::5 (Format: 2001::1) MAC Address: 74-D3-45-32-B6-8D (Format: 00-00-00-00-00-01) VLAN ID: 1 (1-4094) Protect Type: ND Detection Port: 1/0/1 (Format:1/0/1, input or choose below) UNIT1 LAGS 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Apply

2) In the same way, add a binding entry for User 2. Enter the host name, IPv6 address, MAC address and VLAN ID of User 2, select the protect type as ND Detection, and select port 1/0/2 on the panel. Click Apply.

Figure 5-3 Binding Entry for User 2
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image IPv6-MAC Binding Host Name: User1 (20 characters maximum) IPv6 Address: 2001::6 (Format: 2001::1) MAC Address: 88-A9-D4-54-FD-C3 (Format: 00-00-00-00-00-01) VLAN ID: 1 (1-4094) Protect Type: ND Detection Port: 1/0/2 (Format: 1/0/1, input or choose below) UNIT 1 LAGS 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Apply

3) Choose the menu SECURITY > IPv6 IMBP > ND Detection > Global Config to load the following page. Enable ND Detection and click Apply. Select VLAN 1, change Status as Enabled and click Apply.

Figure 5-4 Enable ND Detection
TP-LINK Omada TL-SG2008P - Using the GUI - 3

text_image Global Config ND Detection: ✓ Enable VLAN Config ✓ VLAN ID Status Log Status Enable ✓ 1 Enabled Disabled Total: 1 1 entry selected. Cancel Apply Apply

4) Choose the menu SECURITY > IPv6 IMBP > ND Detection > Port Config to load the following page. By default, all ports are enabled with ND Detection. Since port 1/0/3 is connected to the gateway router, configure port 1/0/3 as trusted port. Click Apply.

Figure 5-5 Port Config
TP-LINK Omada TL-SG2008P - Using the GUI - 4

text_image Port Config UNIT1 LAGS Port Trust Status LAG Enable 1/0/1 Disabled -- 1/0/2 Disabled -- ✓ 1/0/3 Enabled -- 1/0/4 Disabled -- 1/0/5 Disabled -- 1/0/6 Disabled -- 1/0/7 Disabled -- 1/0/8 Disabled -- 1/0/9 Disabled -- 1/0/10 Disabled -- Total: 28 1 entry selected. Cancel Apply

5) Click Save the settings.

5.1.4 Using the CLI

1) Manually bind the entries for User 1 and User 2.

Switch_A#configure

Switch_A(config)#ipv6 source binding User1 2001::5 74:d3:45:32:b6:8d vlan 1 interface gigabitEthernet 1/0/1 nd-detection

Switch_A(config)#ip source binding User1 2001::6 88:a9:d4:54:fd:c3 vlan 1 interface gigabitEthernet 1/0/2 nd-detection

2) Enable ND Detection globally and on VLAN 1.

Switch_A(config)#ipv6 nd detection vlan 1

3) Configure port 1/0/3 as trusted port.

Switch_A(config)#interface gigabitEthernet 1/0/3

Switch_A(config-if)#ipv6 nd detection trust

Switch_A(config-if)#end

Switch_A#copy running-config startup-config

Verify the Configuration

Verify the IPv6-MAC Binding entries:

Switch_A#show ipv6 source binding

UHostIP-AddrMAC-AddrVIDPortACLSOURCE
---------------------------
1User12001::574:d3:45:32:b6:8d1Gi1/0/1ND-DManual
1User22001::688:a9:d4:54:fd:c31Gi1/0/2ND-DManual

Notice:
1. Here, 'ND-D' for 'ND-Detection', and 'IP-V-S' for 'IP-Verify-Source'.

Verify the global configuration of ND Detection:

Switch_A#show ipv6 nd detection

Global Status: Enable

Verify the ND Detection configuration on VLAN:

Switch_A#show ipv6 nd detection vlan

VID Enable status Log Status


1 Enable Disable

Verify the ND Detection configuration on ports:

Switch_A#show ipv6 nd detection interface

Interface Trusted LAG

Gi1/0/1 Disable N/A

Gi1/0/2 Disable N/A

Gi1/0/3 Enable N/A

...

5.2 Example for IPv6 Source Guard

5.2.1 Network Requirements

As shown below, the legal IPv6 host connects to the switch via port 1/0/1 and belongs to the default VLAN 1. It is required that only the legal host can access the network via port

1/0/1, and other unknown hosts will be blocked when trying to access the network via ports 1/0/1-3.

Figure 5-6 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["Computer 74-D3-45-32-B6-8D"] -->|GI1/0/1| B["Switch"]
    C["Computer 74-D3-45-32-B6-8D"] -->|GI1/0/2| B
    D["Computer 74-D3-45-32-B6-8D"] -->|GI1/0/3| B
    E["Unknown Host"] --> B

5.2.2 Configuration Scheme

To implement this requirement, you can use IPv6-MAC Binding and IPv6 Source Guard to filter out the packets received from the unknown hosts. The overview of configuration on the switch is as follows:

1) Bind the MAC address, IPv6 address, connected port number and VLAN ID of the legal host with IPv6-MAC Binding.
2) Enable IPv6 Source Guard on ports 1/0/1-3.

Demonstrated with T1600G-28TS, the following sections provide configuration procedure in two ways: using the GUI and using the CLI.

5.2.3 Using the GUI

1) Choose the menu SECURITY > IPv6 IMPB > IPv6-MAC Binding > Manual Binding and click to load the following page. Enter the host name, IPv6 address, MAC address and VLAN ID of the legal host, select the protect type as , and select port 1/0/1 on the panel. Click Apply.

Figure 5-7 Manual Binding
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image IPv6-MAC Binding Host Name: LegalHost (20 characters maximum) IPv6 Address: 2001::5 (Format: 2001::1) MAC Address: 74-D3-45-32-B6-8D (Format: 00-00-00-00-00-01) VLAN ID: 1 (1-4094) Protect Type: IPv6 Source Guard Port: 1/0/1 (Format: 1/0/1, input or choose below) UNIT1 LAGS 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Apply

2) Choose the menu SECURITY > IPv6 IMPB > IPv6 Source Guard to load the following page. Select ports 1/0/1-3, configure the Security Type as SIPv6+MAC, and click Apply.

Figure 5-8 IPv6 Source Guard
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image IPv6 Source Guard Config UNIT1 LAGS Port Security Type LAG SIPv6+MAC ✓ 1/0/1 SIPv6+SMAC -- ✓ 1/0/2 SIPv6+SMAC -- ✓ 1/0/3 SIPv6+SMAC -- ✓ 1/0/4Disable -- ✓ 1/0/5Disable -- ✓ 1/0/6Disable -- ✓ 1/0/7Disable -- ✓ 1/0/8Disable -- ✓ 1/0/9Disable -- ✓ 1/0/10Disable -- Total: 28 3 entries selected. Cancel Apply

3) Click Save the settings.

5.2.4 Using the CLI

1) Manually bind the IPv6 address, MAC address, VLAN ID and connected port number of the legal host, and apply this entry to the IPv6 Source Guard feature.

Switch#configure

Switch(config)#ipv6 source binding legal-host 2001::5 74:d3:45:32:b6:8d vlan 1 interface gigabitEthernet 1/0/1 ipv6-verify-source

2) Enable IPv6 Source Guard on ports 1/0/1-3.

Switch(config)# ipv6 verify source

Switch(config)# interface range gigabitEthernet 1/0/1-3

Switch(config-if-range)#ipv6 verify source sipv6+mac

Switch(config-if-range)#end

Switch#copy running-config startup-config

Verify the Configuration

Verify the binding entry:

Switch#show ip source binding

UHostIP-AddrMAC-AddrVIDPortACLSOURCE
---------------------------
1legal-host2001::574:d3:45:32:b6:8d1Gi1/0/1IP-V-SManual

Notice:

  1. Here, 'ND-D' for 'ND-Detection', and 'IP-V-S' for 'IP-Verify-Source'.

Verify the configuration of IPv6 Source Guard:

Switch#show ipv6 verify source

Default settings of DHCP Snooping are listed in the following table:

Table 6-1 DHCPv6 Snooping

Parameter Default Setting
Global Config
DHCPv6 Snooping Disabled
VLAN Config
Status Disabled
Port Config
Maximum Entry 512

Default settings of ND Detection are listed in the following table:

Table 6-2 ND Detection

Parameter Default Setting
Global Config
ND Detection Disabled
VLAN Config
Status Disabled
Log Status Disabled
Port Config
Trust Status Disabled
ND Statistics
Auto Refresh Disabled
Refresh Interval5 seconds

Default settings of IPv6 Source Guard are listed in the following table:

Table 6-3 ND Detection

Parameter Default Setting
Port Config
Security Type Disabled

Part 30

Configuring DHCP Filter

CHAPTERS

  1. DHCP Filter
  2. DHCPv4 Filter Configuration
  3. DHCPv6 Filter Configuration
  4. Configuration Examples
  5. Appendix: Default Parameters

1 DHCP Filter

1.1 Overview

During the working process of DHCP, generally there is no authentication mechanism between the DHCP server and the clients. If there are several DHCP servers on the network, security problems and network interference will happen. DHCP Filter resolves this problem.

With DHCP Filter configured, the switch can check whether the received DHCP packets are legal and discard the illegal ones. In this way, DHCP Filter ensures that users get IP addresses only from the legal DHCP server and enhances the network security.

As the following figure shows, there are both legal and illegal DHCP servers on the network. You can configure DHCP Server1 as a legal DHCP server by providing the IP address and port number of DHCP Server1. When receiving the DHCP respond packets, the switch will forward the packets from the legal DHCP server.

Figure 1-1 Network Topology
TP-LINK Omada TL-SG2008P - Overview - 1

flowchart
graph TD
    A["DHCP Server1 (Legal)"] --> B["Switch"]
    B --> C["Clients"]
    B --> D["Other DHCP Server (Illegal)"]

Additionally, you can limit the forwarding rate of DHCP packets on each port.

1.2 Supported Features

The switch supports DHCPv4 Filter and DHCPv6 Filter.

DHCPv4 Filter

DHCPv4 Filter is used for DHCPv4 servers and IPv4 clients.

DHCPv6 Filter

DHCPv6 Filter is used for DHCPv6 servers and IPv6 clients.

2 DHCPv4 Filter Configuration

To complete DHCPv4 Filter configuration, follow these steps:

1) Configure the basic DHCPv4 Filter parameters.
2) Configure legal DHCPv4 servers.

2.1 Using the GUI

2.1.1 Configuring the Basic DHCPv4 Filter Parameters

Choose the menu SECURITY > DHCP Filter > DHCPv4 Filter > Basic Config to load the following page.

Figure 2-1 DHCPv4 Filter Basic Config
TP-LINK Omada TL-SG2008P - Configuring the Basic DHCPv4 Filter Parameters - 1

text_image Global Config DHCPv4 Filter: Enable Apply Port Config UNIT1 LACS Port Status MAC Verify Rate Limit Decline Protect LAG ✓ 1/0/1 Disabled Disabled Disabled Disabled --- □ 1/0/2 Disabled Disabled Disabled Disabled --- □ 1/0/3 Disabled Disabled Disabled Disabled --- □ 1/0/4 Disabled Disabled Disabled Disabled --- □ 1/0/5 Disabled Disabled Disabled Disabled --- □ 1/0/6 Disabled Disabled Disabled Disabled --- □ 1/0/7 Disabled Disabled Disabled Disabled --- □ 1/0/8 Disabled Disabled Disabled Disabled --- □ 1/0/9 Disabled Disabled Disabled Disabled --- □ 1/0/10 Disabled Disabled Disabled Disabled --- Total: 28 1 entry selected. Cancel Apply

Follow these steps to complete the basic settings of DHCPv4 Filter:

1) In the Global Config section, enable DHCPv4 globally.
2) In the Port Config section, select one or more ports and configure the related parameters.

Port Displays the port number.
Status Enable or disable DHCPv4 Filter feature on the port.
MAC VerifyEnable or disable the MAC Verify feature. There are two fields in the DHCPv4 packet that contain the MAC address of the host. The MAC Verify feature compares the two fields of a DHCPv4 packet and discards the packet if the two fields are different.This prevents the IP address resource on the DHCPv4 server from being exhausted by forged MAC addresses.
Rate Limit Select to enable the rate limit feature and specify the maximum number of DHCPv4 packets that can be forwarded on the port per second. The excessive DHCPv4 packets will be discarded.
Decline ProtectSelect to enable the decline protect feature and specify the maximum number of Decline packets that can be forwarded on the port per second. The excessive Decline packets will be discarded.
LAG Displays the LAG that the port is in.

3) Click Apply.

TP-LINK Omada TL-SG2008P - 3) Click Apply. - 1

Note:

The member port of an LAG (Link Aggregation Group) follows the configuration of the LAG and not its own. The configurations of the port can take effect only after it leaves the LAG.

Choose the menu SECURITY > DHCP Filter > DHCPv4 Filter > Legal DHCPv4 Servers and click to load the following page.

Figure 2-2 Adding Legal DHCPv4 Server
TP-LINK Omada TL-SG2008P - Configuring Legal DHCPv4 Servers - 1

text_image Add Legal DHCPv4 Server Server IP Address: (Format: 192.168.0.1) Client MAC Address: (Format: 00-00-00-00-00-01) Server Port: Cancel (Format: 1/0/1, input or choose below) UNIT1 LAGS 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

Follow these steps to add a legal DHCPv4 server:

1) Configure the following parameters:

Server IP Address Specify the IP address of the legal DHCPv4 server.

Client MAC (Optional) Specify the MAC address of the DHCP Client. You can also keep this Address field empty, which represents for all DHCP clients.

Server Port Select the port that the legal DHCPv4 server is connected.

2) Click Create.

2.2 Using the CLI

2.2.1 Configuring the Basic DHCPv4 Filter Parameters

Follow these steps to complete the basic settings of DHCPv4 Filter:

Step 1 configure

Enter global configuration mode.

Step 2 ip dhcp filterEnable DHCPv4 Filter globally.
Step 3 interface { fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | interface port-channel port-channel-id | interface range port-channel port-channel-id-list }Enter interface configuration mode.
Step 4 ip dhcp filterEnable DHCPv4 Filter on the port.
Step 5 ip dhcp filter mac-verifyEnable the MAC Verify feature. There are two fields in the DHCP packet that contain the MAC address of the host. The MAC Verify feature compares the two fields of a DHCP packet and discards the packet if the two fields are different. This prevents the IP address resource on the DHCP server from being exhausted by forged MAC addresses.
Step 6 ip dhcp filter limit rate valueEnable the limit rate feature and specify the maximum number of DHCP messages that can be forwarded on the port per second. The excessive DHCP packets will be discarded.value: Specify the limit rate value. The following options are provided: 0, 5,10,15,20,25 and 30 (packets/second). The default value is 0, which indicates disabling limit rate.
Step 7 ip dhcp filter decline rate valueEnable the decline protect feature and specify the maximum number of Decline packets can be forwarded per second on the port. The excessive Decline packets will be discarded.value: Specify the limit rate value of Decline packets. The following options are provided: 0, 5,10,15,20,25 and 30 (packets/second). The default value is 0, which indicates disabling this feature.
Step 8 show ip dhcp filterVerify the global DHCPv4 Filter configuration.
Step 9 show ip dhcp filter interface [ fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel port-channel-id ]Verify the DHCPv4 Filter configuration of the port.
Step 10 endReturn to privileged EXEC mode.
Step 11 copy running-config startup-configSave the settings in the configuration file.

TP-LINK Omada TL-SG2008P - Configuring the Basic DHCPv4 Filter Parameters - 1

Note:

The member port of an LAG (Link Aggregation Group) follows the configuration of the LAG and not its own. The configurations of the port can take effect only after it leaves the LAG.

The following example shows how to enable DHCPv4 Filter globally and how to enable DHCPv4 Filter, enable the MAC verify feature, set the limit rate as 10 pps and set the decline rate as 20 pps on port 1/0/1:

Switch#configure

Switch(config)#ip dhcp filter

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#ip dhcp filter

Switch(config-if)#ip dhcp filter mac-verify

Switch(config-if)#ip dhcp filter limit rate 10

Switch(config-if)#ip dhcp filter decline rate 20

Switch(config-if)##show ip dhcp filter

Global Status: Enable

Switch(config-if)#show ip dhcp filter interface gigabitEthernet 1/0/1

InterfacestateMAC-VerifyLimit-RateDec-rateLAG
-----------------------
Gi1/0/1EnableEnable1020N/A

Switch(config-if)#end

Switch#copy running-config startup-config

Follow these steps configure legal DHCPv4 servers:

Step 1 configure

Enter global configuration mode.

Step 2 ip dhcp filter server permit-entry server-ip ipAddr client-mac macAddr interface { fastEthernet port-list | gigabitEthernet port-list | ten-gigabitEthernet port-list | port-channel port-channel-id}

Create an entry for the legal DHCPv4 server.

ipAddr: Specify the IP address of the legal DHCPv4 server.

macAddr : Specify the MAC address of the DHCP Client. The value "all" means all client mac addresses.

port-list | port-channel-id: Specify the port that the legal DHCPv4 server is connected to.

Step 3 show ip dhcp filter server permit-entry

Verify configured legal DHCPv4 server information.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to create an entry for the legal DHCPv4 server whose IP address is 192.168.0.100 and connected port number is 1/0/1 without client MAC address restricted:

Switch#configure

Switch(config)#ip dhcp filter server permit-entry server-ip 192.168.0.100 client-mac all interface gigabitEthernet 1/0/1

Switch(config)#show ip dhcp filter server permit-entry

Server IPClient MACInterface
192.168.0.100allGi1/0/1

Switch(config)#end

Switch#copy running-config startup-config

3 DHCPv6 Filter Configuration

To complete DHCPv6 Filter configuration, follow these steps:

1) Configure the basic DHCPv6 Filter parameters.
2) Configure legal DHCPv6 servers.

3.1 Using the GUI

3.1.1 Configuring the Basic DHCPv6 Filter Parameters

Choose the menu SECURITY > DHCP Filter > DHCPv6 Filter > Basic Config to load the following page.

Figure 3-1 DHCPv6 Filter Basic Config
TP-LINK Omada TL-SG2008P - Configuring the Basic DHCPv6 Filter Parameters - 1

text_image Global Config DHCPv6 Filter: Enable Apply Port Config UNIT1 LAGS Port Status Rate Limit Decline Protect LAG ✓ 1/0/1 Disabled Disabled Disabled --- □ 1/0/2 Disabled Disabled Disabled --- □ 1/0/3 Disabled Disabled Disabled --- □ 1/0/4 Disabled Disabled Disabled --- □ 1/0/5 Disabled Disabled Disabled --- □ 1/0/6 Disabled Disabled Disabled --- □ 1/0/7 Disabled Disabled Disabled --- □ 1/0/8 Disabled Disabled Disabled --- □ 1/0/9 Disabled Disabled Disabled --- □ 1/0/10 Disabled Disabled Disabled ---Total: 28 1 entry selected. Cancel Apply

Follow these steps to complete the basic settings of DHCPv6 Filter:

1) In the Global Config section, enable DHCPv6 globally.
2) In the Port Config section, select one or more ports and configure the related parameters.

Port Displays the port number.

Status Enable or disable DHCPv6 Filter feature on the port.

Rate Limit Select to enable the rate limit feature and specify the maximum number of DHCPv6 packets that can be forwarded on the port per second. The excessive DHCPv6 packets will be discarded.

Decline Protect Select to enable the decline protect feature and specify the maximum number of DHCPv6 Decline packets that can be forwarded on the port per second. The excessive DHCPv6 Decline packets will be discarded.

LAG Displays the LAG that the port is in.

3) Click Apply.

TP-LINK Omada TL-SG2008P - 3) Click Apply. - 1

Note:

The member port of an LAG (Link Aggregation Group) follows the configuration of the LAG and not its own. The configurations of the port can take effect only after it leaves the LAG.

Choose the menu SECURITY > DHCP Filter > DHCPv6 Filter > Legal DHCPv6 Servers and click to load the following page.

Figure 3-2 Adding Legal DHCPv6 Server

Server IPv6 Address:

Server Port:

TP-LINK Omada TL-SG2008P - Add Legal DHCPv6 Server - 1

(Format: 2001::1)

TP-LINK Omada TL-SG2008P - Add Legal DHCPv6 Server - 2

Cancel

(Format: 1/0/1, input or choose below)

UNIT1

TP-LINK Omada TL-SG2008P - Add Legal DHCPv6 Server - 3

text_image 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27

TP-LINK Omada TL-SG2008P - Add Legal DHCPv6 Server - 4

Selected

TP-LINK Omada TL-SG2008P - Add Legal DHCPv6 Server - 5

Unselected

TP-LINK Omada TL-SG2008P - Add Legal DHCPv6 Server - 6

Not Available

Cancel

Create

Follow these steps to add a legal DHCPv6 server:

1) Configure the following parameters:

Server IPv6 Address

Specify the IP address of the legal DHCPv6 server.

Server Port Select the port that the legal DHCPv6 server is connected.

2) Click Create.

3.2 Using the CLI

3.2.1 Configuring the Basic DHCPv6 Filter Parameters

Follow these steps to complete the basic settings of DHCPv6 Filter:

Step 1 configure

Enter global configuration mode.

Step 2 ipv6 dhcp filter

Enable DHCPv6 Filter globally.

Step 3 interface { fastEthernet port | range fastEthernet port-list | gigabitEthernet port | range gigabitEthernet port-list | ten-gigabitEthernet port | range ten-gigabitEthernet port-list | interface port-channel port-channel-id | interface range port-channel port-channel-id-list }

Enter interface configuration mode.

Step 4 ipv6 dhcp filter

Enable DHCPv6 Filter on the port.

Step 5 ipv6 dhcp filter limit rate

value

Enable the limit rate feature and specify the maximum number of DHCP messages that can be forwarded on the port per second. The excessive DHCP packets will be discarded.

value: Specify the limit rate value. The following options are provided: 0, 5, 10, 15, 20, 25 and 30 (packets/second). The default value is 0, which indicates disabling limit rate.

Step 6 ipv6 dhcp filter decline rate

value

Enable the decline protect feature and specify the maximum number of Decline packets can be forwarded per second on the port. The excessive Decline packets will be discarded.

value: Specify the limit rate value of Decline packets. The following options are provided: 0, 5, 10, 15, 20, 25 and 30 (packets/second). The default value is 0, which indicates disabling this feature.

Step 7 show ipv6 dhcp filter

Verify the global DHCPv6 Filter configuration.

Step 8 show ipv6 dhcp filter interface [fastEthernet

port | gigabitEthernet port | ten-

gigabitEthernet port | port-channel port-channel-id ]

Verify the DHCPv6 Filter configuration of the port.

Step 9 end

Return to privileged EXEC mode.

Step 10 copy running-config startup-config

Save the settings in the configuration file.

TP-LINK Omada TL-SG2008P - Configuring the Basic DHCPv6 Filter Parameters - 1

Note:

The member port of an LAG (Link Aggregation Group) follows the configuration of the LAG and not its own. The configurations of the port can take effect only after it leaves the LAG.

The following example shows how to enable DHCPv6 Filter globally and how to enable DHCPv6 Filter, set the limit rate as 10 pps and set the decline rate as 20 pps on port 1/0/1:

Switch#configure

Switch(config)#ipv6 dhcp filter

Switch(config)#interface gigabitEthernet 1/0/1

Switch(config-if)#ipv6 dhcp filter

Switch(config-if)#ipv6 dhcp filter limit rate 10

Switch(config-if)#ipv6 dhcp filter decline rate 20

Switch(config-if)##show ipv6 dhcp filter

Global Status: Enable

Switch(config-if)#show ip dhcp filter interface gigabitEthernet 1/0/1

InterfacestateLimit-RateDec-rateLAG
-------------------
Gi1/0/1Enable1020N/A

Switch(config-if)#end

Switch#copy running-config startup-config

Follow these steps configure legal DHCPv6 servers:

Step 1 configure

Enter global configuration mode.

Step 2 ipv6 dhcp filter server permit-entry server-ip ipAddr interface { fastEthernet port-list | gigabitEthernet port-list | ten-gigabitEthernet port-list | port-channel port-channel-id } Create an entry for the legal DHCPv6 server.

ipAddr: Specify the IPv6 address of the legal DHCPv6 server.

port-list | port-channel-id: Specify the port that the legal DHCPv6 server is connected to.

Step 3 show ip dhcp filter server permit-entry

Verify configured legal DHCPv6 server information.

Step 4 end

Return to privileged EXEC mode.

Step 5 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to create an entry for the legal DHCPv6 server whose IPv6 address is 2001::54 and connected port number is 1/0/1:

Switch#configure

Switch(config)#ipv6 dhcp filter server permit-entry server-ip 2001::54 interface gigabitEthernet 1/0/1

Switch(config)#show ipv6 dhcp filter server permit-entry

Server IP Interface

2001::54 Gi1/0/1

Switch(config)#end

Switch#copy running-config startup-config

4 Configuration Examples

4.1 Example for DHCPv4 Filter

4.1.1 Network Requirements

As shown below, all the DHCPv4 clients get IP addresses from the legal DHCPv4 server, and any other DHCPv4 server in the LAN is regarded as illegal. Now it is required that only the legal DHCPv4 server is allowed to assign IP addresses to the clients.

Figure 4-1 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["Switch A"] --> B["Gi1/0/1"]
    B --> C["Legal DHCPv4 Server 192.168.0.200"]
    B --> D["Illegal DHCPv4 Server"]
    B --> E["DHCPv4 Client"]
    B --> F["DHCPv4 ClientDHCPv4 Client"]

4.1.2 Configuration Scheme

To meet the requirements, you can configure DHCPv4 Filter to filter the DHCPv4 packets from the illegal DHCPv4 server.

The overview of configuration is as follows:

1) Enable DHCPv4 Filter globally and on all ports.
2) Create an entry for the legal DHCPv4 server.

Demonstrated with T1600G-28TS, the following sections provide configuration procedure in two ways: using the GUI and using the CLI.

4.1.3 Using the GUI

1) Choose the menu SECURITY > DHCP Filter > DHCPv4 Filter > Basic Config to load the following page. Enable DHCPv4 Filter globally and click Apply. Select all ports, change Status as Enable, and click Apply.

Figure 4-2 Basic Config
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Global Config DHCPv4 Filter: ✓ Enable Port Config UNIT1 LAGS ✓ Port Status MAC Verify Rate Limit Decline Protect LAG Enable ✓ 1/0/1 Enabled Disabled Disabled Disabled --- ✓ 1/0/2 Enabled Disabled Disabled Disabled --- ✓ 1/0/3 Enabled Disabled Disabled Disabled --- ✓ 1/0/4 Enabled Disabled Disabled Disabled --- ✓ 1/0/5 Enabled Disabled Disabled Disabled --- ✓ 1/0/6 Enabled Disabled Disabled Disabled --- ✓ 1/0/7 Enabled Disabled Disabled Disabled --- ✓ 1/0/8 Enabled Disabled Disabled Disabled --- ✓ 1/0/9 Enabled Disabled Disabled Disabled --- ✓ 1/0/10 Enabled Disabled Disabled Disabled --- Total: 28 28 entries selected. Cancel Apply

2) Choose the menu SECURITY > DHCP Filter > DHCPv4 Filter > Legal DHCPv4 Servers and click to load the following page. Specify the IP address and connected port number of the legal DHCPv4 server. Click Create.

Figure 4-3 Create Entry for Legal DHCPv4 Server
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image Add Legal DHCPv4 Server Server IP Address: 192.168.0.200 Client MAC Address: Server Port: 1/0/1 (Format: 192.168.0.1) (Format: 00-00-00-00-00-01) Cancel (Format: 1/0/1, input or choose below) UNIT1 LAGS 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

3) Click Save the settings.

4.1.4 Using the CLI

1) Enable DHCPv4 Filter globally and on all pots:

Switch_A#configure

Switch_A(config)#ip dhcp filter

Switch_A(config)#interface range gigabitEthernet 1/0/1-28

Switch_A(config-if-range)#ip dhcp filter

Switch_A(config-if-range)#exit

2) Create an entry for the legal DHCPv4 server:

Switch_A(config)#ip dhcp filter server permit-entry server-ip 192.168.0.200 client-mac all interface gigabitEthernet 1/0/1

Switch_A(config)#end

Switch_A#copy running-config startup-config

Verify the Configuration

Verify the global DHCPv4 Filter configuration:

Switch_A#show ip dhcp filter

Global Status: Enable

Verify the DHCPv4 Filter configuration on ports:

Switch_A#show ip dhcp filter interface

InterfacestateMAC-VerifyLimit-RateDec-rateLAG
-----------------------
Gi1/0/1EnableDisableDisableDisableN/A
Gi1/0/2EnableDisableDisableDisableN/A
Gi1/0/3EnableDisableDisableDisableN/A
Gi1/0/4EnableDisableDisableDisableN/A
...

Verify the legal DHCPv4 server configuration:

Switch_A#show ip dhcp filter server permit-entry

Server IP Client MAC Interface

192.168.0.200 all Gi1/0/1

4.2 Example for DHCPv6 Filter

4.2.1 Network Requirements

As shown below, all the DHCPv6 clients get IP addresses from the legal DHCPv6 server, and any other DHCPv6 server in the LAN is regarded as illegal. Now it is required that only the legal DHCPv6 server is allowed to assign IP addresses to the clients.

Figure 4-1 Network Topology
TP-LINK Omada TL-SG2008P - Network Requirements - 1

flowchart
graph TD
    A["Switch A"] --> B["Gi1/0/1"]
    B --> C["Legal DHCPv6 Server 2001::54"]
    B --> D["Illegal DHCPv6 Server"]
    A --> E["DHCPv6 Client"]
    A --> F["DHCPv6 ClientDHCPv6 Client"]

4.2.2 Configuration Scheme

To meet the requirements, you can configure DHCPv6 Filter to filter the DHCPv6 packets from the illegal DHCPv6 server.

The overview of configuration is as follows:

1) Enable DHCPv6 Filter globally and on all ports.
2) Create an entry for the legal DHCPv6 server.

Demonstrated with T1600G-28TS, the following sections provide configuration procedure in two ways: using the GUI and using the CLI.

4.2.3 Using the GUI

1) Choose the menu SECURITY > DHCP Filter > DHCPv6 Filter > Basic Config to load the following page. Enable DHCPv6 Filter globally and click Apply. Select all ports, change Status as Enable, and click Apply.

Figure 4-2 Basic Config
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Global Config DHCPv6 Filter: ✓ Enable Port Config UNIT1 LAGS ✓ Port Status MAC Verify Rate Limit Decline Protect LAG Enable ✓ 1/0/1 Enabled Disabled Disabled Disabled --- ✓ 1/0/2 Enabled Disabled Disabled Disabled --- ✓ 1/0/3 Enabled Disabled Disabled Disabled --- ✓ 1/0/4 Enabled Disabled Disabled Disabled --- ✓ 1/0/5 Enabled Disabled Disabled Disabled --- ✓ 1/0/6 Enabled Disabled Disabled Disabled --- ✓ 1/0/7 Enabled Disabled Disabled Disabled --- ✓ 1/0/8 Enabled Disabled Disabled Disabled --- ✓ 1/0/9 Enabled Disabled Disabled Disabled --- ✓ 1/0/10 Enabled Disabled Disabled Disabled --- Total: 28 28 entries selected. Cancel Apply

2) Choose the menu SECURITY > DHCP Filter > DHCPv6 Filter > Legal DHCPv6 Servers and click to load the following page. Specify the IP address and connected port number of the legal DHCPv6 server. Click Create.

Figure 4-3 Create Entry for Legal DHCPv6 Server
TP-LINK Omada TL-SG2008P - Using the GUI - 2

text_image Add Legal DHCPv6 Server Server IPv6 Address: 2001::54 (Format: 2001::1) Server Port: 1/0/1 Cancel (Format: 1/0/1, input or choose below) UNIT1 LAGS 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Selected Unselected Not Available Cancel Create

3) Click Save the settings.

4.2.4 Using the CLI

1) Enable DHCPv6 Filter globally and on all pots:

Switch_A#configure

Switch_A(config)#ipv6 dhcp filter

Switch_A(config)#interface range gigabitEthernet 1/0/1-28

Switch_A(config-if-range)#ipv6 dhcp filter

Switch_A(config-if-range)#exit

2) Create an entry for the legal DHCPv6 server:

Switch_A(config)#ipv6 dhcp filter server permit-entry server-ip 2001::54 interface gigabitEthernet 1/0/1

Switch_A(config)#end

Switch_A#copy running-config startup-config

Verify the Configuration

Verify the global DHCPv6 Filter configuration:

Switch_A#show ipv6 dhcp filter

Global Status: Enable

Verify the DHCPv6 Filter configuration on ports:

Switch_A#show ipv6 dhcp filter interface

InterfacestateLimit-RateDec-rateLAG
-------------------

Gi1/0/1 Enable Disable Disable N/A

Gi1/0/2 Enable Disable Disable N/A

Gi1/0/3 Enable Disable Disable N/A

Gi1/0/4 Enable Disable Disable N/A

...

Verify the legal DHCPv6 server configuration:

Switch_A#show ipv6 dhcp filter server permit-entry

Server IP Interface

2001::54 Gi1/0/1

5 Appendix: Default Parameters

Default settings of DHCPv4 Filter are listed in the following table:

Table 5-1 DHCPv4 Filter

Parameter Default Setting
Global Config
DHCPv4 Filter Disabled
Port Config
Status Disabled
MAC Verify Disabled
Rate Limit Disabled
Decline Protect Disabled

Table 5-2 DHCPv6 Filter

Parameter Default Setting
Global Config
DHCPv6 Filter Disabled
Port Config
Status Disabled
Rate Limit Disabled
Decline Protect Disabled

Part 31

Configuring DoS Defend

CHAPTERS

  1. Overview
  2. DoS Defend Configuration
  3. Appendix: Default Parameters

1 Overview

The DoS (Denial of Service) defend feature provides protection against DoS attacks. DoS attacks occupy the network bandwidth maliciously by sending numerous service requests to the hosts. It results in an abnormal service or breakdown of the network.

With DoS Defend feature, the switch can analyze the specific fields of the IP packets, distinguish the malicious DoS attack packets and discard them directly. Also, DoS Defend feature can limit the transmission rate of legal packets. When the number of legal packets exceeds the threshold value and may incur a breakdown of the network, the switch will discard the packets.

2 DoS Defend Configuration

2.1 Using the GUI

Choose the menu SECURITY > DoS Defend to load the following page.

Figure 2-1 DoS Defend
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image DoS Defend DoS Protection: □ Enable Apply DoS Defend Config Land Attack: □ Enable Scan SYNFIN: □ Enable Xmascan: □ Enable NULL Scan: □ Enable SYN sPort less 1024: □ Enable Blat Attack: □ Enable Ping Flooding: □ Enable SYN/SYN-ACK Flooding: □ Enable WinNuke Attack: □ Enable Ping Of Death: □ Enable Smurf Attack: □ Enable Apply

Follow these steps to configure DoS Defend:

1) In the DoS Defend section, enable DoS Protection and click Apply.
2) In the DoS Defend Config section, select one or more defend types according to your needs and click Apply. The following table introduces each type of DoS attack.

Land Attack The attacker sends a specific fake SYN (synchronous) packet to the destination host. Because both of the source IP address and the destination IP address of the SYN packet are set to be the IP address of the host, the host will be trapped in an endless circle of building the initial connection.
Scan SYNFINThe attacker sends the packet with its SYN field and the FIN field set to 1. The SYN field is used to request initial connection whereas the FIN field is used to request disconnection. Therefore, the packet of this type is illegal.
XmascanThe attacker sends the illegal packet with its TCP index, FIN, URG and PSH field set to 1.
NULL ScanThe attacker sends the illegal packet with its TCP index and all the control fields set to 0. During the TCP connection and data transmission, the packets with all control fields set to 0 are considered illegal.
SYN sPort less 1024The attacker sends the illegal packet with its TCP SYN field set to 1 and source port smaller than 1024.
Blat AttackThe attacker sends the illegal packet with the same source port and destination port on Layer 4 and with its URG field set to 1. Similar to the Land Attack, the system performance of the attacked host is reduced because the Host circularly attempts to build a connection with the attacker.
Ping Flooding The attacker floods the destination system with Ping packets, creating a broadcast storm that makes it impossible for the system to respond to legal communication.
SYN/SYN-ACK FloodingThe attacker uses a fake IP address to send TCP request packets to the server. Upon receiving the request packets, the server responds with SYN-ACK packets. Since the IP address is fake, no response will be returned. The server will keep on sending SYN-ACK packets. If the attacker sends overflowing fake request packets, the network resource will be occupied maliciously and the requests of the legal clients will be denied.
WinNuke Attack Because the Operation System with bugs cannot correctly process the URG (Urgent Pointer) of TCP packets, the attacker sends this type of packets to the TCP port139 (NetBIOS) of the host with the Operation System bugs, which will cause the host with a blue screen.
Ping of DeathPing of Death attack means that the attacker sends abnormal ping packets larger than 65535 bytes to cause system crash on the target computer.Note: Ping of Death is only available on certain devices.
Smurf AttackSmurf attack is a distributed denial-of-service attack in which large numbers of Internet Control Message Protocol (ICMP) packets with the intended victim's spoofed source IP are broadcast to a computer network using an IP broadcast address. Most devices on a network will, by default, respond to this by sending a reply to the source IP address. If the number of machines on the network that receive and respond to these packets is very large, the victim's computer will be flooded with traffic.Note: Smurf Attack is only available on certain devices.

3) Click Apply.

2.2 Using the CLI

Follow these steps to configure DoS Defend:

Step 1 configure

Enter global configuration mode.

Step 2 ip dos-prevent

Globally enable the DoS defend feature.

Step 3

ip dos-prevent type { land | scan-synfin | xma-scan | null-scan | port-less-1024 | blat | ping-flood | syn-flood | win-nuke | ping-of-death | smurf }

Configure one or more defend types according to your needs. The types of DoS attack are introduced as follows.

land: The attacker sends a specific fake SYN (synchronous) packet to the destination host. Because both the source IP address and the destination IP address of the SYN packet are set to be the IP address of the host, the host will be trapped in an endless circle of building the initial connection.

scan-synfin: The attacker sends the packet with its SYN field and the FIN field set to 1. The SYN field is used to request initial connection whereas the FIN field is used to request disconnection. Therefore, a packet of this type is illegal.

xma-scan: The attacker sends the illegal packet with its TCP index, FIN, URG and PSH field set to 1.

null-scan: The attacker sends the illegal packet with its TCP index and all the control fields set to 0. During the TCP connection and data transmission, the packets with all the control fields set to 0 are considered as the illegal packets.

port-less-1024: The attacker sends the illegal packet with its TCP SYN field set to 1 and source port smaller than 1024.

blat: The attacker sends the illegal packet with the same source port and destination port on Layer 4 and with its URG field set to 1. Similar to the Land Attack, the system performance of the attacked host is reduced because the Host circularly attempts to build a connection with the attacker.

ping-flood: The attacker floods the destination system with Ping packets, creating a broadcast storm that makes it impossible for system to respond to legal communication.

syn-flood: The attacker uses a fake IP address to send TCP request packets to the server. Upon receiving the request packets, the server responds with SYN-ACK packets. Since the IP address is fake, no response will be returned. The server will keep on sending SYN-ACK packets. If the attacker sends overflowing fake request packets, the network resource will be occupied maliciously and the requests of the legal clients will be denied.

win-nuke: An Operation System with bugs cannot process the URG (Urgent Pointer) of TCP packets. If the attacker sends TCP packets to port139 (NetBIOS) of the host with Operation System bugs, it will cause blue screen.

ping-of-death: Ping of Death attack means that the attacker sends abnormal ping packets larger than 65535 bytes to cause system crash on the target computer.

Note: Ping of Death is only available on certain devices.

smurf: Smurf attack is a distributed denial-of-service attack in which large numbers of Internet Control Message Protocol (ICMP) packets with the intended victim's spoofed source IP are broadcast to a computer network using an IP broadcast address. Most devices on a network will, by default, respond to this by sending a reply to the source IP address. If the number of machines on the network that receive and respond to these packets is very large, the victim's computer will be flooded with traffic.

Note: Smurf is only available on certain devices.

Step 4 show ip dos-prevent

Verify the DoS Defend configuration.

Step 5 end

Return to privileged EXEC mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to enable the DoS Defend type named land:

Switch#configure

Switch(config)#ip dos-prevent

Switch(config)#ip dos-prevent type land

Switch(config)#show ip dos-prevent

DoS Prevention State: Enabled

Type Status


Land Attack Enabled

Scan SYNFIN Disabled

Xmascan Disabled

NULL Scan Disabled

SYN sPort less 1024 Disabled

Blat Attack Disabled

Ping Flooding Disabled

SYN/SYN-ACK Flooding Disabled

WinNuke Attack Disabled

Smurf Attack Disabled

Ping Of Death Disabled

Switch(config)#end

Switch#copy running-config startup-config

3 Appendix: Default Parameters

Default settings of Network Security are listed in the following tables.

Table 3-1 DoS Defend

Parameter Default Setting
DoS Defend Disabled

Part 32

Monitoring the System

CHAPTERS

  1. Overview
  2. Monitoring the CPU
  3. Monitoring the Memory

1 Overview

With System Monitor function, you can:

■ Monitor the CPU utilization of the switch.
■ Monitor the memory utilization of the switch.

The CPU utilization should be always under 80%, and excessive use may result in switch malfunctions. For example, the switch fails to respond to management requests (ICMP ping, SNMP timeouts, slow Telnet or SSH sessions). You can monitor the system to verify a CPU utilization problem.

2 Monitoring the CPU

2.1 Using the GUI

Choose the menu MAINTENANCE > System Monitor > CPU Monitor to load the following page.

Figure 2-1 Monitoring the CPU
TP-LINK Omada TL-SG2008P - Using the GUI - 1

line | Statistic | Value | | ------------------- | ------- | | Current Utilization | 14.00% | | Average Utilization | 15.05% | | Maximum Utilization | 33.00% | | Minimum Utilization | 10.00% |

Click Monitor to enable the switch to monitor and display its CPU utilization rate every five seconds.

2.2 Using the CLI

On privileged EXEC mode or any other configuration mode, you can use the following command to view the CPU utilization:

show cpu-utilization

View the memory utilization of the switch in the last 5 seconds, 1 minute and 5 minutes.

The following example shows how to monitor the CPU:

Switch#show cpu-utilization

Unit | CPU Utilization

No. | Five-Seconds One-Minute Five-Minutes

1 | 13% 13% 13%

3 Monitoring the Memory

3.1 Using the GUI

Choose the menu MAINTENANCE > System Monitor > Memory Monitor to load the following page.

Figure 3-1 Monitoring the Memory
TP-LINK Omada TL-SG2008P - Using the GUI - 1

line | Metric | Value | | -------------------- | ------- | | Current Utilization | 79.00% | | Average Utilization | 76.21% | | Maximum Utilization | 79.00% | | Minimum Utilization | 75.00% |

Click Monitor to enable the switch to monitor and display its memory utilization rate every five seconds.

3.2 Using the CLI

On privileged EXEC mode or any other configuration mode, you can use the following command to view the memory utilization:

show memory-utilization

View the current memory utilization of the switch.

The following example shows how to monitor the memory:

Switch#show memory-utilization

Unit | Current Memory Utilization

1 | 74%

Part 33

Monitoring Traffic

CHAPTERS

  1. Traffic Monitor
  2. Appendix: Default Parameters

1 Traffic Monitor

With Traffic Monitor function, you can monitor each port's traffic information, including the traffic summary and traffic statistics in detail.

1.1 Using the GUI

Choose the menu MAINTENANCE > Traffic Monitor to load the following page.

Figure 1-1 Traffic Summary
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Traffic Summary Auto Refresh: ✓ Enable Refresh Interval: 10 seconds (3-300) Apply UNIT1 LAGS Port Packets Rx Packets Tx Octets Rx Octets Tx Statistics 1/0/1 0 0 0 0 Statistics 1/0/2 0 0 0 0 Statistics 1/0/3 0 0 0 0 Statistics 1/0/4 0 0 0 0 Statistics 1/0/5 0 0 0 0 Statistics 1/0/6 0 0 0 0 Statistics 1/0/7 0 0 0 0 Statistics 1/0/8 0 0 0 0 Statistics 1/0/9 0 0 0 0 Statistics 1/0/10 0 0 0 0 Statistics Total: 28

Follow these steps to view the traffic summary of each port:

1) To get the real-time traffic summary, enable Auto Refresh, or click Refresh.

Auto Refresh: With this option enabled, the switch will automatically refresh the traffic summary.

Refresh Interval: Specify the time interval for the switch to refresh the traffic summary.

2) In the Traffic Summary section, click UNIT1 to show the information of the physical ports, and click LAGS to show the information of the LAGs.

Packets Rx: Displays the number of packets received on the port. Error packets are not counted.

Packets Tx: Displays the number of packets transmitted on the port. Error packets are not counted.

Octets Rx: Displays the number of octets received on the port. Error octets are counted.

Octets Tx: Displays the number of octets transmitted on the port. Error octets are counted.

To view a port's traffic statistics in detail, click Statistics on the right side of the entry.

Figure 1-2 Traffic Statistics

Port1/0/12
ReceivedSent
Broadcast: 106Broadcast: 15
Multicast: 81Multicast: 7
Unicast: 14279Unicast: 15994
Jumbo: 0Jumbo: 0
Alignment Errors: 0Pkts: 16016
Undersize Packets: 0Bytes: 6838693
64-Octets Packets: 9606Collisions Errors: 0
65-to-127-Octects Packets: 2400
128-to-255-Octects Packets: 81
256-to-511-Octects Packets: 234
512-to-1023-Octects Packets: 2145
1023-to-1518-Octects Packets: 0
Pkts: 14466
Bytes: 2241191

Received: Displays the detailed information of received packets.

Broadcast: Displays the number of valid broadcast packets received on the port. Error frames are not counted.

Multicast: Displays the number of valid multicast packets received on the port. Error frames are not counted.

Unicast: Displays the number of valid unicast packets received on the port. Error frames are not counted.

Jumbo: Displays the number of valid jumbo packets received on the port. Error frames are not counted.

Alignment Errors: Displays the number of the received packets that have a Frame Check Sequence (FCS) with a non-integral octet (Alignment Error). The size of the packet is between 64 bytes and 1518 bytes.

Undersize Packets: Displays the number of the received packets (excluding error packets) that are less than 64 bytes long.

64-Octets Packets: Displays the number of the received packets (including error packets) that are 64 bytes long.

65-to-127-Octects Packets: Displays the number of the received packets (including error packets) that are between 65 and 127 bytes long.

128-to-255-Octects Packets: Displays the number of the received packets (including error packets) that are between 128 and 255 bytes long.

256-to-511-Octects Packets: Displays the number of the received packets (including error packets) that are between 256 and 511 bytes long.

512-to-1023-Octects Packets: Displays the number of the received packets (including error packets) that are between 512 and 1023 bytes long.

1023-to-1518-Octects Packets: Displays the number of the received packets (including error packets) that are between 512 and 1023 bytes long.

Pkts: Displays the number of packets received on the port. Error packets are not counted.

Bytes: Displays the number of bytes received on the port. Error packets are not counted.

Sent: Displays the detailed information of sent packets.

Broadcast: Displays the number of valid broadcast packets transmitted on the port. Error frames are not counted.

Multicast: Displays the number of valid multicast packets transmitted on the port. Error frames are not counted.

Unicast: Displays the number of valid unicast packets transmitted on the port. Error frames are not counted.

Pkts: Displays the number of packets transmitted on the port. Error packets are not counted.

Bytes: Displays the number of bytes transmitted on the port. Error packets are not counted.

Collisions: Displays the number of collisions experienced by a half-duplex port during packet transmissions.

1.2 Using the CLI

On privileged EXEC mode or any other configuration mode, you can use the following command to view the traffic information of each port or LAG:

show interface counters [ fastEthernet port | gigabitEthernet port | ten-gigabitEthernet port | port-channel port-channel-id ]

port: The port number.

port-channel-id : The group number of the LAG.

If you enter no port number or group number, the information of all ports and LAGs will be displayed.

The displaying information includes:

Tx Collisions: Displays the number of collisions experienced by a port during packet transmissions.

Tx Ucast / Tx Mcast / Tx Bcast / Tx Jumbo: Displays the number of valid unicast / multicast / broadcast / jumbo packets transmitted on the port. Error frames are not counted.

Tx Pkts: Displays the number of packets transmitted on the port. Error packets are not counted.

Tx Bytes: Displays the number of bytes transmitted on the port. Error packets are not counted.

Rx Ucast / Rx Mcast / Rx Bcast / Rx Jumbo: Displays the number of valid unicast / multicast / broadcast / jumbo packets received on the port. Error frames are not counted.

Rx Alignment: Displays the number of the received packets that have a Frame Check Sequence (FCS) with a non-integral octet (Alignment Error). The size of the packet is between 64 bytes and 1518 bytes.

Rx UnderSize: Displays the number of the received packets (excluding error packets) that are less than 64 bytes long.

Rx 64Pkts: Displays the number of the received packets (including error packets) that are 64 bytes long.

Rx 65-127Pkts: Displays the number of the received packets (including error packets) that are between 65 and 127 bytes long.

Rx 128-255Pkts: Displays the number of the received packets (including error packets) that are between 128 and 255 bytes long.

Rx 256-511Pkts: Displays the number of the received packets (including error packets) that are between 256 and 511 bytes long.

Rx 512-1023Pkts: Displays the number of the received packets (including error packets) that are between 512 and 1023 bytes long.

Rx 1024-1518Pkts: Displays the number of the received packets (including error packets) that are between 1024 and 1518 bytes long.

Rx Pkts: Displays the number of packets received on the port. Error packets are not counted.

Rx Bytes: Displays the number of bytes received on the port. Error packets are not counted.

2 Appendix: Default Parameters

Table 2-1 Traffic Statistics Monitoring

Parameter Default Setting
Traffic Summary
Auto Refresh Disabled
Refresh Rate 10 seconds

Part 34

Mirroring Traffic

CHAPTERS

  1. Mirroring
  2. Configuration Examples
  3. Appendix: Default Parameters

1 Mirroring

You can analyze network traffic and troubleshoot network problems using Mirroring. Mirroring allows the switch to send a copy of the traffic that passes through specified sources (ports, LAGs or the CPU) to a destination port. It does not affect the switching of network traffic on source ports, LAGs or the CPU.

1.1 Using the GUI

Choose the menu MAINTENANCE > Mirroring to load the following page.

Figure 1-1 Port Mirroring Session List

Session Destination Port Mode Source Interfaces Operation
1Ingress Only Egress Only BothEdit Clear
Total: 1

The above page displays a mirroring session, and no more session can be created. Click Edit to configure this mirroring session on the following page.

Figure 1-2 Configure the Mirroring Session
TP-LINK Omada TL-SG2008P - Using the GUI - 1

text_image Destination Port Config UNIT1 2 4 6 8 10 12 14 16 18 20 22 24 26 28 1 3 5 7 9 11 13 15 17 19 21 23 25 27 Apply Source Interfaces Config UNIT1 LAGS CPU Port Ingress Egress LAG 1/0/1 Disabled Disabled -- 1/0/2 Disabled Disabled -- 1/0/3 Disabled Disabled -- 1/0/4 Disabled Disabled -- 1/0/5 Disabled Disabled -- 1/0/6 Disabled Disabled -- 1/0/7 Disabled Disabled -- 1/0/8 Disabled Disabled -- 1/0/9 Disabled Disabled -- 1/0/10 Disabled Disabled -- Total: 28

Follow these steps to configure the mirroring session:

1) In the Destination Port Config section, specify a destination port for the mirroring session, and click Apply.
2) In the Source Interfaces Config section, specify the source interfaces and click Apply. Traffic passing through the source interfaces will be mirrored to the destination port. There are three source interface types: port, LAG, and CPU. Choose one or more types according to your need.

UNIT1 Select the desired ports as the source interfaces. The switch will send a copy of traffic passing through the port to the destination port.

LAGS Select the desired LAGs as the source interfaces. The switch will send a copy of traffic passing through the LAG members to the destination port.

CPU When selected, the switch will send a copy of traffic passing through the CPU to the destination port.

Ingress With this option enabled, the packets received by the corresponding interface (port, LAG or CPU) will be copied to the destination port. By default, it is disabled.

Egress With this option enabled, the packets sent by the corresponding interface (port, LAG or CPU) will be copied to the destination port. By default, it is disabled.

TP-LINK Omada TL-SG2008P - Using the GUI - 2

Note:

• The member ports of an LAG cannot be set as a destination port or source port.
• A port cannot be set as the destination port and source port at the same time.

1.2 Using the CLI

Follow these steps to configure Mirroring.

Step 1 configure

Enter global configuration mode.

Step 2 monitor session

session_num destination interface { fastEthernet port | gigabitEthernet tEthernet port}

Enable the port mirror function and set the destination port.

session_num: The monitor session number. It can only be specified as 1.

port: The destination port number. You can specify only one destination port for the mirror session.

Step 3 monitor session

session_num source { cpu cpu_numbr | interface { fastEthernet port-list

| gigabitEthernet port-list | ten-gigabitEthernet port-list | port-channel port-channel-id }} mode

Configure ports or LAGs as the monitored interfaces.

session_num: The monitor session number. It can only be specified as 1.

cpu_number: The CPU number. It can only be specified as 1.

port-list: List of source ports. It is multi-optional.

mode: The monitor mode. There are three options: rx, tx and both:

rx: The incoming packets of the source port will be copied to the destination port.

tx: The outgoing packets of the source port will be copied to the destination port.

both: Both of the incoming and outgoing packets on source port can be copied to the destination port.

Note:

You can configure one or more source interface types (ports, LAGs and the CPU) according to your needs.

Step 4 show monitor session

Verify the Port Mirror configuration.

Step 5 end

Return to privileged EXEC mode.

Step 6 copy running-config startup-config

Save the settings in the configuration file.

The following example shows how to copy the received and transmitted packets on port 1/0/1,2,3 and the CPU to port 1/0/10.

Switch#configure

Switch(config)#monitor session 1 destination interface gigabitEthernet 1/0/10

Table of contents Click a title to access it
Manual assistant
Powered by Anthropic
Waiting for your message
Product information

Brand : TP-LINK

Model : Omada TL-SG2008P

Category : Switch