GPL-8000 - Switch Planet - Free user manual and instructions
Find the device manual for free GPL-8000 Planet in PDF.
| Product Type | 8-Port GPON Managed OLT |
| Dimensions (W x D x H) | 440 x 304 x 44 mm |
| Weight | 5,500 g |
| Power Supply | 100-240V AC, 1.5A max or 36-72V DC, 3A max; 60 watts |
| GPON Ports | 8 GPON SFP ports, up to 2.5Gbps downstream / 1.25Gbps upstream, 20km distance, split ratio up to 128 |
| Uplink Ports | 4x 10/100/1000BASE-T RJ45 (shared with SFP), 8x 100/1000BASE-X SFP, 4x 10GBASE-X SFP+ |
| Management Ports | 1x 10/100BASE-TX RJ45, 1x RJ45 Console (9600,8,N,1) |
| Switching Capacity | 176 Gbps |
| MAC Address Table | 64K entries |
| VLAN Support | IEEE 802.1Q, up to 4K VLAN groups, Q-in-Q, GVRP |
| Routing Protocols | Static routing, RIP, OSPF, IPv4/IPv6 |
| Security Features | 802.1x, RADIUS/TACACS+, ACL, DHCP Snooping, DAI, IP Source Guard |
| Management Interfaces | Web GUI, CLI (Telnet/Console), SNMP v1/v2c/v3, SSHv2, SSLv3 |
| Cooling | 3 fans |
| Operating Temperature | 0°C to 50°C |
| Storage Temperature | -10°C to 70°C |
| Humidity | 5% to 90% (non-condensing) |
| Regulatory Compliance | CE, FCC Class A, LVD |
| Package Contents | GPON OLT, Quick Installation Guide, Dust Caps (20), RJ45-to-DB9 Console Cable, Rack-mount Kit, AC Power Cord |
| Warranty | Standard limited warranty; refer to official terms |
Frequently Asked Questions - GPL-8000 Planet
User questions about GPL-8000 Planet
0 question about this device. Answer the ones you know or ask your own.
Ask a new question about this device
Download the instructions for your Switch in PDF format for free! Find your manual GPL-8000 - Planet and take your electronic device back in hand. On this page are published all the documents necessary for the use of your device. GPL-8000 by Planet.
USER MANUAL GPL-8000 Planet
natural_image
Front view of a network switch device with multiple ports and indicator lights (no visible text or labels)8-Port GPON Managed OLT
GPL-8000
natural_image
Interior view of a modern automated factory with rows of white robotic arms (no visible text or symbols)Trademarks
Copyright © PLANET Technology Corp. 2020.
Contents are subject to revision without prior notice.
PLANET is a registered trademark of PLANET Technology Corp. All other trademarks belong to their respective owners.
Disclaimer
PLANET Technology does not warrant that the hardware will work properly in all environments and applications, and makes no warranty and representation, either implied or expressed, with respect to the quality, performance, merchantability, or fitness for a particular purpose. PLANET has made every effort to ensure that this User's Manual is accurate; PLANET disclaims liability for any inaccuracies or omissions that may have occurred.
Information in this User's Manual is subject to change without notice and does not represent a commitment on the part of PLANET. PLANET assumes no responsibility for any inaccuracies that may be contained in this User's Manual. PLANET makes no commitment to update or keep current the information in this User's Manual, and reserves the right to make improvements to this User's Manual and/or to the products described in this User's Manual, at any time without notice.
If you find information in this manual that is incorrect, misleading, or incomplete, we would appreciate your comments and suggestions.
FCC Warning
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the Instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense.
CE Mark Warning
This is a Class A product. In a domestic environment, this product may cause radio interference, in which case the user may be required to take adequate measures.
Energy Saving Note of the Device
This power required device does not support Standby mode operation. For energy saving, please remove the power cable to disconnect the device from the power circuit. In view of saving the energy and reducing the unnecessary power consumption, it is strongly suggested to remove the power connection for the device if this device is not intended to be active.
WEEE Warning
To avoid the potential effects on the environment and human health as a result of the presence of hazardous substances in electrical and electronic equipment, end users of electrical and electronic equipment should understand the meaning of the crossed-out wheeled bin symbol. Do not dispose of WEEE as unsorted municipal waste and have to collect such WEEE separately.
Revision
PLANET GPL-8000 User's Manual
Model: GPL-8000
Revision: 1.0 (Jan. 2021)
Part No: EM-GPL-8000_v1.0
Contents
1. Introduction 19
1.1 Packet Contents....19
1.2 Product Description....20
1.4 How to Use This Manual 22
1.5 Product Features 22
1.6 Product Specifications 25
2. Hardware Installation 30
2.1 Hardware Description 30
2.1.1. OLT Front Panel....30
2.1.2. LED Indications....31
2.1.4. OLT Rear Panel 33
2.3 Installing the OLT 35
2.3.1. Rack Mounting....35
2.3.2. Installing the Uplink Port 36
3. Web-based Management 40
3.1 About Web-based Management 40
3.2 Logging on to the Switch....40
3.3 OLT Information 42
3.3.1. Device Information....42
3.3.2. Manage the Switch via SNMP Network Management Software 42
3.3.3. Help Function....44
3.3.4. Canceling a Command 44
3.3.5. Saving Configuration 44
4. Basic Configuration 45
4.1 System Management Configuration....45
4.1.1. File Management Configuration....45
4.1.1.1. Managing the file system....45
4.1.1.2. Commands for the file system 45
4.1.1.3. Starting up from a file manually 45
4.1.1.4. Updating software....46
4.1.1.5. Updating configuration....47
4.1.1.6. Using ftp to perform the update of software and configuration 48
4.1.2. Basic System Management Configuration....49
4.1.2.1. Configuring Ethernet IP address....49
4.1.2.2. Configuring default route 49
4.1.2.3. Using ping to test network connection state 50
4.1.3. HTTP Configuration 50
4.1.3.1. Configuring HTTP 50
4.1.3.2. Examples of http configuration 51
4.2 Terminal Configuration....52
4.2.1. VTY configuration introduction....52
4.2.2. Configuration tasks....52
4.2.2.1. Relationship between line and interface 52
4.2.3. Monitoring and maintenance ....52
4.2.4. Browsing Logs 52
4.2.5. VTY configuration example....53
4.3 Remote Monitoring....54
4.3.1. Configuring SNMP 54
4.3.1.1. Introduction....54
4.3.1.2. SNMP configuration tasks....55
4.3.1.3. Configuration example....59
4.3.2. RMON configuration 60
4.3.2.1. RMON configuration tasks....60
4.3.3. Configuring PDP 64
4.3.3.1. Introduction....64
4.3.3.2. PDP configuration tasks....64
4.3.3.3. PDP configuration examples....66
4.4 SSH Configuration commands....67
4.4.1. Introduction....67
4.4.1.1. SSH server 67
4.4.1.2. SSH client....67
4.4.1.3. Function 67
4.4.2. Configuration Tasks 67
4.4.2.1. Configuring the authentication method list....67
4.4.2.2. Configuring the access control list....67
4.4.2.3. Configuring the authentication timeout value....68
4.4.2.4. Configuring authentication....68
4.4.2.5. Enabling SSH server 68
4.4.3. SSH server configuration example 68
4.4.3.1. Access control list 68
4.4.3.2. Global configuration....68
5. Remote Monitoring 70
Chapter 5....70
5.1 Remote Monitoring....70
5.1.1 SNMP configuration....70
5.1.2 Overview....70
5.1.3 SNMP notification ....70
5.1.4 SNMP tasks....70
6. Security Configuration 71
Chapter 6....71
6.1 AAA Configuration 71
6.1.1 AAA Overview....71
6.1.2 AAA Configuration Process 73
6.1.3 AAA Authentication Configuration Task List....74
6.1.4 AAA Authentication Configuration Task....74
6.1.5 AAA Authentication Configuration Example....79
6.1.6 AAA Authorization Configuration Task List....79
6.1.7 AAA Authorization Configuration Task 79
6.1.8 AAA Authorization Example 81
6.1.9 AAA Accounting Configuration Task List....81
6.1.10 AA Accounting Configuration Task....81
6.2 Configuring RADIUS....83
6.2.1 Introduction 83
6.2.2 RADIUS Configuration Task List 85
6.2.3 RADIUS Configuration Task List....86
6.2.4 RADIUS Configuration Task....86
6.2.5 RADIUS Configuration Examples 88
6.3 Web Authentication Configuration....89
6.3.1 Overview 89
6.3.2 Configuring Web Authentication....92
6.3.3 Monitoring and Maintaining Web Authentication....94
6.3.4 Web Authentication Configuration Example....95
7. Web Configuration 97
Chapter 7....97
7.1 HTTP Switch Configuration....97
7.1.1 HTTP Configuration 97
7.1.2 HTTPS Configuration....98
7.2 Configuration Preparation....98
7.2.1 Accessing the Switch through HTTP 98
7.2.2 Accessing a Switch through Secure Links....100
7.2.3 Introduction of Web Interface....101
7.3 Basic Configuration....103
7.3.1 Hostname Configuration....104
7.3.2 Time Management....104
7.4 GPON Interface Config....105
7.4.1 GPON Global Config 105
7.4.2 ONU Bind Relationship Config 105
7.4.3 ONU Discovery Mode 106
7.4.4 ONU Authentication 107
7.5 ONU Config Profile 108
7.5.1 ONU T-Cont Config....108
7.5.2 ONU Rate Limit Config 109
7.5.3 ONU Virtual Port Config....110
7.5.4 T-Cont Virtual Port Bind Config....110
7.5.5 ONU VLAN Config....111
7.5.6 ONU Flow Mapping Config....112
7.6 ONU Interface Config....114
7.6.1 ONU Description....114
7.6.2 T-Cont Virtual Port Bind 114
7.6.3 Flow Mapping 115
7.6.4 VLAN Config....115
7.6.5 Virtual Port Bandwidth Config.... 115
7.6.6 Virtual Port GEM Port Bind 115
7.6.7 ONU Remote Controller....115
7.7 Advanced Config....117
7.7.1 Configuring Port Description.... 117
7.7.2 Configuring the Attributes of the Port....118
7.7.3 Rate control 118
7.7.4 Port mirroring....119
7.7.5 VLAN Settings 120
7.7.6 Configuring the VLAN Interface 122
7.7.7 LDP Configuration....123
7.7.8 STP Configuration....124
7.7.9 Port security....126
7.7.10 Storm control 128
7.7.11 IP Access Control List....130
7.7.12 MAC Access Control List 132
7.7.13 Link Aggregation Configuration....133
7.7.14 Ring Protection Configuration....134
7.7.15 DDM Configuration 135
7.7.16 MTU Config....135
7.8 Layer 3 Configuration....136
7.8.1 Setting the Static Route....137
7.9 Remote Monitor configuration....138
7.9.1 SNMP Configuration....138
7.9.2 RMON Config 139
7.10 System Management....142
7.10.1 User Management 142
7.10.2 Log Management....146
7.10.3 Diagnostic....146
7.10.4 Managing the Configuration Files....147
7.10.5 Software Management....149
7.10.6 Factory Settings....150
7.10.7 Rebooting the Device 150
7.10.8 About 150
- Interface Configuration 151
Chapter 8....151
8.1 Introduction 151
8.1.1 Supported Interface Types....151
8.1.2 Interface Configuration Introduction....152
8.2 Interface Configuration....153
8.2.1 Configuring Interface Common Attribute....153
8.2.2 Monitoring and Maintaining Interface....154
8.2.3 Configuring Logistical Interface 155
8.3 Interface Configuration Example....157
8.3.1 Configuring Public Attribute of Interface 157
- Interface Range Configuration 158
Chapter 9....158
9.1 Interface Range Configuration Task....158
9.1.1 Understanding Interface Range....158
9.1.2 Entering Interface Range Mode....158
9.1.3 Configuration Example 158
10. Port Physical Characteristics Configuration 158
Chapter 10....158
10.1 Configuring the Ethernet Interface....158
10.1.1 Selecting Ethernet Interface 159
10.1.2 Configuration Rate....159
10.1.3 Configuring Flow Control on the Interface 159
11. Additional Port Characteristics Configuration 159
Chapter 11....159
11.1 Configuring the Ethernet Interface 159
11.1.1 Configuring Flow Control for the Port 160
11.1.2 Comfiguring the Rate Unit for the Port....160
11.1.3 Configuring the Storm Control on the Port....161
11.2 Secure Port Configuration....161
11.2.1 Overview....161
11.2.2 Configuration Task of the Secure Port 161
11.3 Configuring the Secure Port.... 161
11.3.1 Configuring the Secure Port Mode 161
11.3.2 Configuring the Static MAC Address of the Secure Port 162
12. Configuring Port Mirroring 163
Chapter 12....163
12.1 Configuring Port Mirroring Task.... 163
12.1.1 Configuring Port Mirroring....163
12.1.2 Displaying Port Mirroring Information 163
13. Configuring MAC Address Attribute 163
Chapter 13....163
13.1 MAC Address Configuration Task List.... 163
13.2 MAC address Configuration Task....164
13.2.1 Configuring Static Mac Address....164
13.2.2 Configuring MAC Address Aging Time....164
13.2.3 Displaying MAC Address Table....164
13.2.4 Clearing Dynamic MAC Address 165
14. Configuring MAC List 165
Chapter 14....165
14.1 MAC List Configuration Task.... 165
14.1.1 Creating MAC List....165
14.1.2 Configuring Items of MAC List....165
14.1.3 Applying MAC List 166
15. Configuring 802.1x 167
Chapter 15....167
15.1 802.1x Configuration Task List....167
15.2 802.1x Configuration Task....167
15.2.1 Configuring 802.1x Port Authentication 167
15.2.2 Configuring 802.1x Multiple Port Authentication....169
15.2.3 Configuring Maximum Times for 802.1x ID Authentication....170
15.2.4 Configuring 802.1x Re-authentication .... 170
15.2.5 Configuring 802.1x Transmission Frequency ....170
15.2.6 Configuring 802.1x User Binding....170
15.2.7 Configuring Authentication Method for 802.1x Port 171
15.2.8 Selecting Authentication Type for 802.1x Port....171
15.2.9 Configuring 802.1x Accounting....171
15.2.10 Configuring 802.1x guest-vlan....172
15.2.11 Forbidding Supplicant with Multiple Network Cards 172
15.2.12 Resuming Default 802.1x Configuration....172
15.2.13 Monitoring 802.1x Authentication Configuration and State....173
15.3 802.1x Configuration Example....173
16. VLAN Configuration 174
Chapter 16....174
16.1 VLAN Introduction....174
16.2 VLAN Configuration Task List 174
16.3 VLAN Configuration Task....174
16.3.1 Adding/Deleting VLAN 174
16.3.2 Configuring Switch Port 175
16.3.3 Creating/Deleting VLAN Interface....176
16.3.4 Configuring Super VLAN Interface 176
16.3.5 Monitoring Configuration and State of VLAN....177
16.4 Configuration Examples....177
17. GVRP Configuration 178
Chapter 17.... 178
17.1 Configuring GVRP 178
17.2 Introduction....178
17.3 Configuring Task List....178
17.3.1 GVRP Configuration Task List 178
17.4 GVRP Configuration Task 178
17.4.1 Enabling/Disabling GVRP Globally 178
17.4.2 Enabling/Disabling GVRP on the Interface 178
17.4.3 Monitoring and Maintenance of GVRP 179
17.5 Configuration Example....179
18. Private VLAN Settings 181
Chapter 18....181
18.1 Private VLAN Settings 181
18.2 Overview of Private VLAN 181
18.3 Private VLAN Type and Port Type in Private VLAN 181
18.3.1 Having One Primary VLAN Type 181
18.3.2 Having Two Secondary VLAN Types....181
18.3.3 Port Types Under the Private VLAN Port.... 181
18.3.4 Modifying the Fields in VLAN TAG....182
18.4 Private VLAN Configuration Task List.... 182
18.5 Private VLAN Configuration Tasks....182
18.5.1 Configuring Private VLAN....182
18.5.2 Configuring the Association of Private VLAN Domains 182
18.5.3 Configuring the L2 Port of Private VLAN to Be the Host Port.... 183
18.5.4 Configuring the L2 Port of Private VLAN to Be the Promiscuous Port 183
18.5.5 Modifying Related Fields of Egress Packets in Private VLAN 183
18.5.6 Displaying the Configuration Information of Private VLAN 184
18.6 Configuration Example.... 184
19. STP Configuration 187
Chapter 19....187
19.1 Configuring STP.... 187
19.1.1 STP Introduction.... 187
19.1.2 SSTP Configuration Task List 188
19.1.3 SSTP Configuration Task....188
19.1.4 Configuring VLAN STP 191
19.1.5 RSTP Configuration Task List.... 192
19.1.6 RSTP Configuration Task.... 193
19.2 Configuring MTSP....195
19.2.1 MSTP Overview....195
19.2.2 MSTP Configuration Task List.... 203
19.2.3 MSTP Configuration Task....204
20. STP Optional Characteristic Configuration 215
Chapter 20....215
20.1 Configuring STP Optional Characteristic 215
20.1.1 STP Optional Characteristic Introduction....215
20.1.2 Configuring STP Optional Characteristic 221
21. Link Aggregation Configuration 226
Chapter 21....226
21.1 Configuring Port Aggregation....226
21.1.1 Overview....226
21.1.2 Port Aggregation Configuration Task List....226
21.1.3 Port Aggregation Configuration Task 226
22. PDP Configuration 228
Chapter 22....228
22.1 PDP Overview....228
22.1.1 Overview 228
22.1.2 PDP Configuration Tasks 229
22.1.3 PDP Configuration Example 230
23. LLDP Configuration 231
Chapter 23....231
23.1 LLDP 231
23.1.1 LLDP Introduction 231
23.1.2 LLDP Configuration Task List....231
23.1.3 LLDP Configuration Task 231
24. FlexLinkLite Configuration 235
Chapter 24....235
24.1 FlexLinkLite Configuration 235
24.1.1 FlexLinkLite Overview....235
24.1.2 FlexLinkLite Configuration 236
24.1.3 FlexLinkLite Configuration Example 237
25. BackupLink Configuration 239
Chapter 25....239
25.1 BackupLink Overview 239
25.1.1 Overview....239
25.1.2 Port Aggregation Configuration Task 239
26. EAPS Configuration 242
Chapter 26....242
26.1 Introduction of Fast Ethernet Ring Protection 242
26.1.1 Overview....242
26.1.2 Related Concepts of Fast Ether-Ring Protection....242
26.1.3 Types of EAPS Packets 245
26.1.4 Fast Ethernet Ring Protection Mechanism 245
26.2 Fast Ethernet Ring Protection Configuration 246
26.2.1 Default EAPS Settings....246
26.2.2 Requisites before Configuration 247
26.2.3 MEAPS Configuration Tasks....247
26.2.4 Fast Ethernet Ring Protection Configuration 247
26.2.5 MEAPS configuration....250
27. MEAPS Settings 252
Chapter 27....252
27.1 MEAPS Introduction....252
27.1.1 MEAPS Overview 252
27.1.2 Basic Concepts of MEAPS 253
27.1.3 Types of EAPS Packets....257
27.1.4 Fast Ethernet Ring Protection Mechanism 257
27.2 Fast Ethernet Ring Protection Configuration 264
27.2.1 Requisites before Configuration 264
27.2.2 MEAPS Configuration Tasks....265
27.2.3 Fast Ethernet Ring Protection Configuration 265
27.3 Appendix 269
27.3.1 Working Procedure of MEAPS....269
27.3.2 Complete state....269
27.3.3 MEAPS configuration....273
27.3.4 Unfinished Configurations (to be continued)....279
28. ELPS Configuration 280
Chapter 28....280
28.1 ELPS Overview 280
28.1.1 Overview....280
29. UDLD Configuration 285
Chapter 29....285
29.1 Unidirectional Link Detection (UDLD) 285
29.1.1 UDLD Overview....285
29.1.2 UDLD Configuration Task List....287
29.1.3 UDLD Configuration Tasks....287
29.1.4 Configuration Example 290
30. IGMP Snooping Configuration 293
Chapter 30....293
30.1 IGMP Snooping Configuration 293
30.1.1 IGMP Snooping Configuration Task....293
31. IGMP Proxy Configuration 300
Chapter 31....300
31.1 IGMP Proxy Configuration 300
32. MLD Snooping Configuration 303
Chapter 32....303
32.1 MLD Snooping Configuration....303
32.1.1 IPv6 Multicast Overview 303
32.1.2 MLD Snooping Multicast Configuration Tasks 303
33. OAM Configuration 309
Chapter 33....309
33.1 OAM Configuration 309
33.1.1 OAM Overview....309
33.1.2 OAM Configuration Task List 312
33.1.3 OAM Configuration Tasks 313
33.1.4 Configuration Example 318
34. CFM and Y1731 Configuration 322
Chapter 34....322
34.1 Overview 322
34.1.1 Stipulations 322
34.2 CFM Configuration....322
34.2.1 CFM Configuration Task List....322
34.2.2 CFM Maintenance Task List.... 322
34.2.3 CFM Configuration....322
34.2.4 CFM Maintenance 324
34.2.5 Configuration Example 324
34.3 Y1731 Configuration 324
34.3.1 Configuration Task List....324
35. DHCP Snooping Configuration 327
Chapter 35....327
35.1 DHCP Snooping Configuration 327
35.1.1 DHCP Snooping Configuration Tasks 327
36. MACFF Configuration 334
Chapter 36....334
36.1 MACFF Settings....334
36.1.1 Configuration Tasks 334
37. IEEE 1588 Transparent Clock Configuration 338
Chapter 37....338
37.1 Task List for IEEE1588 Transparent Clock Configuration 338
37.2 Tasks for IEEE1588 Transparent Clock Configuration....338
37.3 Enabling the Transparent Clock....338
37.3.1 Creating the Transparent Clock Port 339
37.3.2 Configuring the Link Delay Calculation Mode 339
37.3.3 Configuring the Forwarding Mode of Sync Packets....339
37.3.4 Configuring the Domain Filtration Function 340
37.3.5 Setting the Transmission Interval of Pdelay_Req Packets 340
37.4 PTP TC Configuration Example 341
38. Layer 2 Tunnel Protocol Configuration 342
Chapter 38....342
38.1 Configuring Layer 2 Protocol Tunnel....342
38.1.1 Introduction....342
38.1.2 Configuring Layer 2 Protocol Tunnel 342
38.1.3 Configuration Example of Layer 2 Protocol Tunnel 342
39. Loopback Detection Configuration 343
Chapter 39....343
39.1 Setting Loopback Detection 343
39.1.1 Introduction of Loopback Detection 343
39.1.2 Loopback Detection Configuration Tasks 344
39.1.3 Setting Loopback Detection 344
39.1.4 Configuration Example 347
40. QoS Configuration 349
Chapter 40....349
40.1 QoS Configuration 349
40.1.1 QoS Overview....349
40.1.2 QoS Configuration Task List 352
40.1.3 QoS Configuration Tasks 352
40.1.4 QoS Configuration Example 360
41. DoS Attack Prevention Configuration 361
Chapter 41....361
41.1 DoS Attack Prevention Configuration....361
41.1.1 DoS Attack Overview 361
41.1.2 DoS Attack Prevention Configuration Task List....362
41.1.3 DoS Attack Prevention Configuration Tasks 362
41.1.4 DoS Attack Prevention Configuration Example 363
42. Attack Prevention Configuration 364
Chapter 42....364
42.1 Attack Prevention Configuration 364
42.1.1 Overview 364
42.1.2 Attack Prevention Configuration Tasks 364
42.1.3 Attack Prevention Configuration 364
42.1.4 Attack Prevention Configuration Example 365
43. Network Protocol Configuration 366
Chapter 43....366
43.1 Configuring IP Addressing....366
43.1.1 IP Introduction....366
43.1.2 Configuring IP Address Task List 367
43.1.3 Configuring IP Address 368
43.2 Configuring NAT 374
43.2.1 Introduction....374
43.2.2 NAT Configuration Task List....376
43.2.3 NAT Configuration Task 376
43.2.4 NAT Configuration Example....385
43.3 Configuring DHCP 387
43.3.1 Introduction....387
43.3.2 Configuring DHCP Client 388
43.3.3 Configuring DHCP Server....390
43.4 IP Service Configuration 393
43.4.1 Configuring IP Service 393
43.4.2 Configuring Access List 398
43.4.3 Configuring IP Access List Based on Physical Port....402
44. IP ACL Application Configuration 405
Chapter 44....405
44.1 Applying the IP Access Control List 405
44.1.1 Applying ACL on Ports 405
45. Routing Configuration 406
Chapter 45....406
45.1 Configuring RIP 406
45.1.1 Overview 406
45.1.2 Configuring RIP Task List....406
45.1.3 Configuring RIP Tasks 407
45.1.4 RIP Configuration Example.... 411
45.2 Configuring BEIGRP 411
45.2.1 Overview 411
45.2.2 BEIGRP Configuration Task List....412
45.2.3 BEIGRP Configuration Task....413
45.2.4 BEIGRP Configuration Example 417
45.3 Configuring OSPF 417
45.3.1 Overview 417
45.3.2 OSPF Configuration Task List....418
45.3.3 OSPF Configuration Task 418
45.3.4 OSPF Configuration Example....424
45.4 Configuring BGP 430
45.4.1 Overview 430
45.4.2 BGP Configuration Task....432
45.4.3 Monitoring and Maintaining BGP 441
45.4.4 BGP Configuration Example 442
46. IP Hardware Subnet Routing Configuration 451
Chapter 46....451
46.1 IP Hardware Subnet Configuration Task....451
46.1.1 Overview 451
46.1.2 Configuring IP Hardware Subnet Routing....452
46.1.3 Checking the State of IP Hardware Subnet Routing....452
46.2 Configuration Example....452
47. IP-PBR Configuration 453
Chapter 47....453
47.1 IP-PBR Configuration....453
47.1.1 Enabling or Disabling IP-PBR Globally 454
47.1.2 ISIS Configuration Task List....455
47.1.3 Monitoring and Maintaining MVC....455
47.1.4 IP-PBR Configuration Example 457
48. Multi-VRF CE Configuration 457
Chapter 48....457
48.1 Multi-VRF CE Introduction 457
48.1.1 Overview 457
48.2 Multi-VRF CE Configuration....459
48.2.1 Default VRF Configuration....459
48.2.2 MCE Configuration Tasks 459
48.2.3 MCE Configuration 460
48.3 MCE Configuration Example....462
48.3.1 Configuring S11 462
48.3.2 Configuring MCE-S1....463
48.3.3 Configuring PE....465
48.3.4 Configuring MCE-S2....467
48.3.5 Setting S22 469
48.3.6 TestifyingVRF Connectivity 470
49. Reliability Configuration 471
Chapter 49....471
49.1 Configuring Port Backup....471
49.1.1 Overview 471
49.1.2 Backup Interface Configratin Task List....471
49.1.3 Backup Interface Configratin Task....471
49.1.4 Examples of Port Backup Configuration 473
49.2 Configuring HSRP protocol....474
49.2.1 Overview 474
49.2.2 HSRP Protocol Configuration Task List 474
49.2.3 HSRP Protocol Configuration Task....474
49.2.4 Example of Hot Standby Configuration....475
49.3 Configuring VRRP 476
49.3.1 VRRP Overview 476
49.3.2 VRRP Configuration Task List....478
49.3.3 VRRP Configuration Tasks 478
49.3.4 VRRP Configuration Example....479
50. Multicast Configuration 482
Chapter 50....482
50.1 Multicast Overview 482
50.1.1 Multicast Routing Realization 482
50.1.2 Multicast Routing Configuration Task List....483
50.2 Basic Multicast Routing Configuration 484
50.2.1 Starting up Multicast Routing....484
50.2.2 Starting up the Multicast Function on the Port....484
50.2.3 Configuring TTL Threshold 485
50.2.4 Cancelling Rapid Multicast Forwarding 485
50.2.5 Configuring Static Multicast Route....485
50.2.6 Configuring IP Multicast Boundary....486
50.2.7 Configuring IP Multicast Rate Control....486
50.2.8 Configuring IP Multicast Helper 487
50.2.9 Configuring Stub Multicast Route 488
50.2.10 Monitoring and Maintaining Multicast Route 489
50.3 IGMP Configuration....490
50.3.1 Overview....490
50.3.2 IGMP Configuration 490
50.3.3 IGMP Characteristic Configuration Example 494
50.4 PIM-DM Configuration 496
50.4.1 PIM-DM Introduction....496
50.4.2 Configuring PIM-DM 497
50.4.3 PIM-DM State-Refresh Configuration Example 499
50.5 Configuring PIM-SM....499
50.5.1 PIM-SM Introduction 499
50.5.2 Configuring PIM-SM 501
50.5.3 Configuration Example 502
51. IPv6 Configuration 504
Chapter 51....504
51.1 IPv6 Protocol's Configuration....504
51.2 Enabling IPv6....505
51.2.1 Setting the IPv6 Address 505
51.3 Setting the IPv6 Services....506
51.3.1 Setting the IPv6 Services....506
52. ND Configuration 508
Chapter 52....508
52.1 ND Overview....508
52.1.1 Address Resolution....509
52.1.2 ND Configuration 509
53. RIPNG Configuration 513
Chapter 53....513
53.1 Configuring RIPNG 513
53.1.1 Overview....513
53.1.2 Setting RIPng Configuration Task List 513
53.1.3 RIPng Configuration Tasks 514
53.1.4 RIPng Configuration Example 518
54. OSPFv3 Configuration 518
Chapter 54....518
54.1 Overview 518
54.2 OSPFv3 Configuration Task List....519
54.3 OSPFv3 Configuration Tasks....520
54.3.1 Enabling OSPFv3 520
54.3.2 Setting the Parameters of the OSPFv3 Interface 520
54.3.3 Setting OSPFv3 on Different Physical Networks 521
54.3.4 Setting the OSPF Network Type....521
54.3.5 Setting the Parameters of the OSPFv3 Domain 521
54.3.6 Setting the Route Summary in the OSPFv3 Domain....522
54.3.7 Setting the Summary of the Forwarded Routes....523
54.3.8 Generating a Default Route....523
54.3.9 Choosing the Route ID on the Loopback Interface....523
54.3.10 Setting the Management Distance of OSPFv3....524
54.3.11 Setting the Timer of Routing Algorithm 524
54.3.12 Monitoring and Maintaining OSPFv3 524
54.4 OSPFv3 Configuration Example....525
54.4.1 Example for OSPFv3 Route Learning Settings 525
55. BFD Configuration 533
Chapter 55....533
55.1 Overview 533
55.2 BFD Configuration Tasks 533
55.2.1 Activating Port BFD 533
55.2.2 Activating the Port BFD Query Mode....534
55.2.3 Activating Port BFD Echo 534
55.2.4 Enabling Port BFD Authentication 535
55.3 BFD Configuration Example 535
56. SNTP Configuration 536
Chapter 56....536
56.1 Overview 536
56.1.1 Stipulations....536
56.2 SNTP Configuration....536
56.2.1 Overview....536
56.2.2 SNTP Configuration Task List....537
56.2.3 SNTP Configuration....538
57. Cluster Management Configuration 538
Chapter 57....538
57.1 Overview 538
57.2 Cluster Management Configuration Task List 539
57.3 Cluster Management Configuration Task....539
57.3.1 Planning Cluster 539
57.3.2 Creating Cluster....539
57.3.3 Configuring Cluster 540
57.3.4 Monitoring the State of Standby Group 541
57.3.5 Using SNMP to Manage Cluster 541
57.3.6 Using Web to Manage Cluster 541
1. Introduction
Thank you for purchasing PLANET GPON OLT GPL-8000. The description of this model is as follows:
| Model GPON ports | 10/100/1000TRJ45 ports | 100/1000BASE-XSFP slots | 10G SFP slots |
| GPL-8000 8 4 | 8 4 |
1.1 Packet Contents
The box should contain the following items:
■ GPON OLT x 1
■ Quick Installation Guide x 1
■ Dust Cap (SFP) x 20
■ RJ45 to DB9 Console Cable x 1
■ Rack-mount Accessory Kit x 1
■ AC Power Cord x 1
If any of these are missing or damaged, please contact your dealer immediately; if possible, retain the carton including the original packing material, and use them again to repack the product in case there is a need to return it to us for repair.
1.2 Product Description
natural_image
Front view of a network switch device (CPU-8008) showing multiple Ethernet ports and I/O ports, no visible text or labels beyond branding.High-performance GPON for FTTx Applications
PLANET GPL-8000 GPON Optical Line Terminal (OLT) consists of eight GPON ports, four Gigabit TP/SFP combo ports, four Gigabit SFP ports, four 10G SFP+ ports and one management port. It complies with ITU-T G.984/G.988 and meets the requirements of GPON OLT's network access technology.
It is easy to install and maintain a GPON deployment of up to 1024 ONU and HGU devices, providing highly-effective GPON solutions and convenient management for fiber optic broadband network.
High-speed and Long-distance Coverage for Triple Play Services
The GPL-8000 provides a high bandwidth of up to 2.5Gbps for downstream and 1.25Gbps for upstream, long-distance coverage of up to 20km between equipment nodes, and flexibility for network deployment. It is a cost-effective access technology with reliable and scalable network for triple-play service applications such as HDTV, IPTV, voice-over-IP (VoIP) and multimedia.
High Split Ratio for a Cost-effective Network Solution
The GPL-8000 is an ideal solution for FTTx applications. It helps to minimize the investment cost for carriers by offering a high split ratio of 1:128 per port and supporting the usage of PLANET ONUs. The GPL-8000 provides strong functionalities for Ethernet features such as VLAN, Dynamic Bandwidth Allocation (DBA), Service Level Agreement (SLA) and Access Control List. GPON protocol allows a Gigabit Ethernet communications fiber to be shared by multiple end users using a passive optical splitter.
Flexible and Extendable 10Gb Ethernet Solution
The GPL-8000 has four 10G SFP+ uplink ports to deliver ultra-high speed networking over long distances to service providers. Each of the 10G SFP+ ports supports dual speed and 10GBASE-SR/LR or 1000BASE-SX/LX. With its 4 ports, 10G Ethernet link capability and additional 8-port 1G Ethernet link capability, the administrator now can flexibly choose the suitable SFP/SFP+ transceiver according to the transmission distance or the transmission speed required to extend the network efficiently. The GPL-8000 provides broad bandwidth and powerful processing capacity for FTTx applications for distribution data link.
Extractive Power Supply Design to Increase Flexibility
The GPL-8000 is equipped with one extractive 100\~240V AC power supply unit, so it is easy to replace the power for users. Besides, the GPL-8000 reserves another backup power slot on the rear panel and users can add the second AC or DC power to the redundant power supply installation. The AC power or DC power is optional. The redundant power system is specifically designed to handle the demands of high-tech facilities requiring the highest power integrity.
Layer 3 Routing Support
The GPL-8000 enables the administrator to conveniently boost network efficiency by configuring Layer 3 static routing manually, the RIP (Routing Information Protocol) or OSPF (Open Shortest Path First) settings automatically.
- The RIP can employ the hop count as a routing metric and prevent routing loops by implementing a limit on the number of hops allowed in a path from the source to a destination.
- The OSPF is an interior dynamic routing protocol for autonomous system based on link-state. The protocol creates a link-state database by exchanging link-states among Layer 3 switches, and then uses the Shortest Path First algorithm to generate a route table based on that database.
Robust Layer 2 Features
The GPL-8000 can be programmed for basic switch management functions such as port speed configuration, port aggregation, VLAN, Spanning Tree Protocol, WRR, bandwidth control and IGMP snooping. It also supports 802.1Q tagged VLAN, Q-in-Q and GVRP Protocol. In addition, the number of VLAN interfaces is 4K. By supporting port aggregation, the GPL-8000 allows the operation of a high-speed trunk combined with multiple ports. It enables up to 32 groups for trunking with a maximum of 8 ports for each group.
Efficient and Secure Management
For efficient management, the GPL-8000 is equipped with console, Web and SNMP management interfaces.
■ With the built-in Web-based management interface, the GPL-8000 offers an easy-to-use, platform-independent management and configuration facility.
■ For text-based management, it can be accessed via Telnet and the console port.
For standard-based monitor and management software, it offers SNMPv3 connection which encrypts the packet content at each session for secure remote management.
Moreover, the GPL-8000 offers secure remote management by supporting SSHv2, TLSv1.0 and SSLv3 connection which encrypts the packet content at each session.
1.4 How to Use This Manual
This User Manual is structured as follows:
Section 2, Hardware Installation
The section explains the functions of the Switch and how to physically install the GPON OLT.
Section 3, Web-based Management
The section explains how to manage the GPON OLT from Web UI.
Section 4, Switch Operation
The chapter explains how to do the switch operation of the GPON OLT.
Appendix A
The section contains cable information of the GPON OLT.
1.5 Product Features
GPON Ports
■ 8 GPON OLT SFP ports
■ Up to 2.5Gbps downstream and 1.25Gbps upstream
■ Maximum transfer distance of up to 20km
■ Each PON port supports up to 128 ONT/HGU
■ Compliant with G.984/G.988
Physical Ports
■ 4 10/100/1000BASE-T RJ45 copper ports
■ 8 100/1000BASE-X SFP ports
■ 4 10GBASE-SR/LR SFP+ ports
■ RJ45 to DB9 console interface for switch basic management and setup
■ One 10/100BASE-TX Management port
OLT Management
■ User-friendly GUI management
■ 2 control interfaces
- Out-of-Band IP – the management RJ45 port
- In-Band IP – the Gigabit TP, SFP and 10G SFP+ uplink ports
■ Supports ONT/HGU authentication; averts illegal ONT access to network
ONT/HGU Management
■ ONT/HGU port control
■ ONT/HGU VLAN mode
IP Routing Features
■ Supports dynamic routing protocol: RIP and OSPF
■ IPv4 static routing
■ Routing interface provides per VLAN routing mode
Layer 2 Features
■ Supports VLAN
- IEEE 802.1Q tag-based VLAN
- Provider Bridging (VLAN Q-in-Q, IEEE 802.1ad) supported
- GVRP for dynamic VLAN management
■ Supports Link Aggregation
- 802.3ad Link Aggregation Control Protocol (LACP)
- Cisco ether-channel (static trunk)
■ Supports Spanning Tree Protocol
- STP, IEEE 802.1D (Classic Spanning Tree Protocol)
- RSTP, IEEE 802.1w (Rapid Spanning Tree Protocol)
- MSTP, IEEE 802.1s (Multiple Spanning Tree Protocol, spanning tree by VLAN)
■ Port mirroring to monitor the incoming or outgoing traffic on a particular port (many to 1)
■ Supports G.8032 ERPS (Ethernet Ring Protection Switching)
■ Loop protection to avoid broadcast loops
■ Link Layer Discovery Protocol (LLDP)
Quality of Service
■ Ingress shaper and egress rate limit per port bandwidth control
■ 8 priority queues on all switch ports
- IEEE 802.1p CoS/DSCP/Precedence
- VLAN ID
- Policy-based ingress and egress QoS
Multicast
■ Supports IPv4 IGMP snooping v1, v2 and v3
■ Supports IPv6 MLD snooping v1 and v2
■ Querier mode support
■ MVR (Multicast VLAN Registration)
Security
■ Authentication
- IEEE 802.1x port-based network access authentication
- Built-in RADIUS client to cooperate with the RADIUS servers
- RADIUS/TACACS+ users access authentication
■ Access Control List
- IP-based Access Control List (ACL)
- MAC-based Access Control List (ACL)
- Time-based ACL
■ DHCP Snooping to filter distrusted DHCP messages
■ Dynamic ARP Inspection discards ARP packets with invalid MAC address to IP address binding
■ IP Source Guard prevents IP spoofing attacks
Management
■ IPv4 and IPv6 dual stack management
■ Switch Management Interfaces
- Console and Telnet Command Line Interface
- HTTP web switch management
- SNMP v1 and v2c switch management
- SSHv2, SSLv3, TLSv1.0 and SNMP v3 secure access
■ SNMP Management
- Four RMON groups (history, statistics, alarms, and events)
- SNMP trap for interface Link Up and Link Down notification
■ Built-in Trivial File Transfer Protocol (TFTP) client
■ BOOTP and DHCP for IP address assignment
■ System Maintenance
- Firmware upload/download via HTTP
- Reset button for system reboot or reset to factory default
- Dual images
■ DHCP Functions:
- DHCP Relay
- DHCP Option 82
- DHCP Server
■ User Privilege levels control
■ Network Time Protocol (NTP) and SNTP
■ Network Diagnostic
- SFP-DDM (Digital Diagnostic Monitor)
- ICMP remote IP ping
■ Syslog remote alarm
■ System Log
1.6 Product Specifications
| Product | GPL-8000 |
| Hardware Specifications | |
| GPON Ports | 8, supporting Class C+, Class C++ and Class B+ |
| 10/100/1000BASE-T RJ45 Ports | 4 TP/SFP combo interfaces, shared with Port-1 to Port-4 |
| 1000BASE-X SFP Slots | 8, supporting 1000BASE-SX/LX/BX SFP transceiverBackward compatible with 100BASE-FX SFP transceiver |
| 10GBASE-X SFP+ Slots | 4, supporting 10GBASE-SR/LR SFP+ transceiver |
| Management Port | One 10/100BASE-TX RJ45 port |
| Console | One RJ45-to-RS232 serial port (9600, 8, N, 1) |
| CPU | 600MHz |
| RAM | 512MB |
| Flash Memory | 32MB |
| Dimensions (W x D x H) | 440 x 304 x 44 mm |
| Weight | 5,500g |
| Power Consumption | 60 watts/204.73BTU |
| Power Requirements - AC | 100~240V AC, 1.5A max. |
| Power Requirements - DC | 36~72V DC, 3A max. |
| Fan | 3 |
| Switching | |
| Switch Architecture | Store-and-forward |
| Switch Fabric | 176Gbps |
| Address Table | 64K |
| ARP Table | 8K |
| ACL Table | 1K |
| Shared Data Buffer | 2MB |
| Jumbo Frame | 2KB |
| Flow Control | Back pressure for half duplexIEEE 802.3x pause frame for full duplex |
| GPON Specifications | |
| Transmission Speed | Downstream: 2.5GbpsUpstream: 1.25Gbps |
| Optical Split Ratio | Up to 128 |
| Transmission Distance | 20km |
| PON Module Wavelength | TX: 1490nm; RX: 1310nm |
| PON Fiber Type | 9/125um SMF (Single mode fiber optic) |
| Layer 3 Functions | |
| IP Interfaces | Max. 1K VLAN interfaces for IPv4Max. 256 VLAN interfaces for IPv6 |
| Routing Table | 32K for IPv48K for IPv6 |
| Routing Protocols | Static routingRIPOSPF |
| Layer 2 Functions | |
| Port Configuration | Port disable/enableAuto-negotiation 10/100/1000Mbps full and half duplex mode selectionFlow control disable/enableBandwidth control on each portPort loopback detect |
| Port Mirroring | TX/RX/BothMany to 1 |
| VLAN | IEEE 802.1Q tag-based VLAN, up to 4K VLAN groupsIEEE 802.1ad Q-in-Q VLAN stacking/tunnelingGVRP for VLAN management |
| Spanning Tree Protocol | IEEE 802.1D Spanning Tree Protocol (STP)IEEE 802.1w Rapid Spanning Tree Protocol (RSTP)IEEE 802.1s Multiple Spanning Tree Protocol (MSTP) |
| Multicast | IPv4 IGMP v1/v2/v3 snoopingIPv4 Querier mode supportIGMP Filtering and IGMP ThrottlingIGMP Proxy reportingIGMP multicast forwarding |
| IPv6 MLD v1/v2 snoopingMulticast VLAN Register (MVR)Up to 2K multicast groups | |
| Link Aggregation | IEEE 802.3ad Ling Aggregation Control Protocol (LACP)Static trunk link aggregationSupports 32 groups with 8 ports per trunk groupUp to 80Gbps bandwidth (full duplex mode)Load Balance Algorithm:- Source IP/destination IP/Source + destination IP- Source MAC/destination MAC/Source + destination MAC |
| Storm Control | Per 100pps1-14880 |
| Bandwidth Control | At least 64Kbps stream |
| QoS | PON interfaces:Dynamic Bandwidth Allocation (DBA)Service Level Agreement (SLA)Limiting the upstream/downstream rate based on each ONT/ONU/HGU |
| 8 priority queues on all switch portsScheduling for priority queues- Weighted Round Robin (WRR)- Strict priorityTraffic classification:- IEEE 802.1p CoS/DSCP/Precedence- VLAN ID- Policy-based ingress and egress QoS | |
| Ring | IGU-T G.8032 ERPS Ring |
| Security Functions | |
| Access Control List | Supports Standard and Expanded ACL- IP-based ACL- MAC-based ACL- Time-based ACLACL based on:- MAC Address- IPv4/IPv6 IP Address- Protocol-number- sport/dport- ToS/PrecedenceUp to 1k entries |
| Security | Transmission data encryption on the PON interfaceMAC limitationMAC stickyPort isolationDHCP snoopingDynamic ARP inspectionIP source guard |
| AAA | TACACS+ and IPv4/IPv6 over RADIUS |
| Network Access Control | IEEE 802.1x port-based network access control |
| Management Functions | |
| System Configuration | Console and TelnetWeb browserSNMP v1, v2c |
| Secure Management Interfaces | SSHv2, SSLv3Maximum 8 sessions for SSH and telnet connection |
| System Management | IPv4 and IPv6 dual stack managementSNMP MIB and TRAPSNMP RMON 1, 2, 3, 9 four groupsFirmware upgrade by HTTP/TFTP/FTP protocol through Ethernet networkConfiguration upload/download through HTTP/TFTP/FTP protocolSupports IEEE 802.1ab LLDP protocolNTP and SNTP clientRADIUS authentication for IPv4/IPv6 login user name and password |
| Event Management | Remote syslogSystem log |
| SNMP MIBs | RFC 1213 MIB-IIRFC 1215 Internet Engineering Task ForceRFC 1271 RMONRFC 1354 IP-Forwarding MIBRFC 1493 Bridge MIBRFC 1643 Ether-like MIBRFC 1907 SNMPv2RFC 2011 IP/ICMP MIBRFC 2012 TCP MIBRFC 2013 UDP MIBRFC 2096 IP forward MIBRFC 2233 if MIBRFC 2452 TCP6 MIBRFC 2454 UDP6 MIBRFC 2465 IPv6 MIBRFC 2466 ICMP6 MIBRFC 2573 SNMPv3 notificationRFC 2574 SNMPv3 VACMRFC 2674 Bridge MIB Extensions |
| Standard Conformance | |
| Regulatory Compliance | CE, FCC, LVD |
| Standards Compliance | IEEE 802.3z Gigabit 1000BASE-SX/LXIEEE 802.3ae 10Gb/s EthernetIEEE 802.3x flow control and back pressureIEEE 802.3ad port trunk with LACPIEEE 802.1D Spanning Tree ProtocolIEEE 802.1w Rapid Spanning Tree ProtocolIEEE 802.1s Multiple Spanning Tree ProtocolIEEE 802.1p Class of ServiceIEEE 802.1Q VLAN taggingIEEE 802.1X port authentication network controlIEEE 802.1ab LLDPRFC 768 UDPRFC 793 TFTP RFC 791 IPRFC 792 ICMPRFC 2068 HTTPRFC 1112 IGMP v1RFC 2236 IGMP v2RFC 3376 IGMP v3RFC 2710 MLD v1FRC 3810 MLD v2 |
| Environments | |
| Operating | Temperature: 0 ~ 50 degrees CRelative Humidity: 5 ~ 90% (non-condensing) |
| Storage | Temperature: -10 ~ 70 degrees CRelative Humidity: 5 ~ 90% (non-condensing) |
2. Hardware Installation
This section describes the hardware features and installation of the GPON OLT on the desktop or rack mount. For easier management and control of the GPON OLT, familiarize yourself with its display indicators and ports. Front panel illustrations in this chapter display the unit LED indicators. Before connecting any network device to the GPON OLT, please read this chapter completely.
2.1 Hardware Description
2.1.1. OLT Front Panel
The front panel of the unit provides a simple interface monitoring the OLT. Figure 2-1 shows the front panel of the GPON OLT.
Figure 2-1 GPL-8000 Front Panel
Gigabit SFP PON Ports
1000BASE-PX20 mini-GBIC slot, SFP (Small Form Factor Pluggable) transceiver module: Up to 20 kilometers (single-mode fiber).
1G/10G SFP+ Uplink Port
10G BASE-SR/LR SFP+ Port, compatible with 1000BASE-SX/LX/BX SFP transceiver.
Gigabit SFP Uplink Port
1000BASE-SX/LX mini-GBIC port, SFP (Small Form Factor Pluggable) transceiver module: From 550 meters (multi-mode fiber) to 10/30/50/70/120 kilometers (single-mode fiber).
Gigabit RJ45 Uplink Ports
100/1000BASE-T copper, RJ45 twisted-pair: Up to 100 meters
Management Port
10/100BASE-TX copper, RJ45 twisted-pair: Up to 100 meters
Gigabit SFP uplink ports support 1000Mbps Forced Mode only. The remote Gigabit switch or media converter's SFP port must support 1000Mbps Forced Mode as well.
2.1.2. LED Indications
The front panel LEDs indicates instant status of port links, data activity and system power, and help to monitor and troubleshoot when needed. Figure 2-4 shows the LED indications of GPL-8000.
GPL-8000 LED Indication
Figure 2-4 GPL-8000 LED Panel
System
| LED Color Function | |||
| PWR1 Green | Lights: | To indicate that the Switch is powered on. | |
| PWR2 Green | Lights: | To indicate that the Switch is powered on. | |
| ALM Red | Lights: | To indicate that AC or DC power has failed. | |
| SYS Green | Blinks: | The OLT is ready for management. | |
| Off: | The OLT is operating abnormally. | ||
1000BASE-PX20 SFP PON Interfaces
| LED Color Function | |||
| PON1-8 Green | Lights: | To indicate the link through that PON port is successfully established. | |
| Off: | To indicate that the PON port is link-down. | ||
| Blinks | To indicate that the switch is actively sending or receiving data over that port. | ||
1000BASE-T RJ45 Interfaces
LED Color Function
| Port G1-4 Green | Lights: | To indicate the link through that RJ45 port is successfully established. |
| Off: | To indicate that the RJ45 port is link-down. | |
| Blinks: | To indicate that the switch is actively sending or receiving data over that port. |
1G Shared SFP+ Interfaces
LED Color Function
| Port G1-8 | Green | Lights: | To indicate the link through that SFP+ port is successfully established. |
| Off: | To indicate that the SFP+ port is link-down. | ||
| Blinks: | To indicate that the switch is actively sending or receiving data over that port. |
10G SFP+ Interfaces (TG1 to TG4 Ports)
LED Color Function
| LINK Green | Lights: | To indicate the link through that SFP+ port is successfully established. | |
| Off: | To indicate that the SFP+ port is link-down. | ||
| ACT | Green | Blinks: | To indicate that the switch is actively sending or receiving data over that port. |
2.1.4. OLT Rear Panel
The rear panel of the GPON OLT indicates an AC inlet power socket, which accepts input power from 100 to 240V AC, 50-60Hz. Figure 2-5 shows the rear panel of this GPON OLT.
GPL-8000 Rear Panel
natural_image
Three black server rack units with ventilation fans and ports, shown from top to bottom (no visible text or labels)Figure 2-5 Rear Panel of GPL-8000
■ AC Power Receptacle
For compatibility with electric service in most areas of the world, the GPON OLT's power supply automatically adjusts to line power in the range of 100-240V AC and 50/60 Hz.
Plug the female end of the power cord firmly into the receptacle on the rear panel of the GPON OLT and the other end of the power cord into an electric outlet and then the power will be ready.
There is a power switch for AC power input use only, whereas DC power input has no power switch.
The device is a power-required device; if your networks should be active all the time, please consider using UPS (Uninterrupted Power Supply) for your device. It will prevent you from network data loss or network downtime.
In some areas, installing a surge suppression device may also help to protect your GPON OLT from being damaged by unregulated surge or current to the switch or the power adapter.
2.3 Installing the OLT
This section describes how to install your GPON OLT and make connections to the GPON OLT. Please read the following topics and perform the procedures in the order being presented. To install your GPON OLT on a shelf, simply complete the following steps.
2.3.1. Rack Mounting
To install the GPON OLT in a 19-inch standard rack, please follow the instructions described below:
Step 1: Place the GPON OLT on a hard flat surface, with the front panel positioned towards the front side.
Step 2: Attach the rack-mount bracket to each side of the GPON OLT with supplied screws attached to the package.
Figure 2-9 shows how to attach brackets to one side of the GPON OLT.
Figure 2-9 Attaching Brackets to the GPON OLT.
You must use the screws supplied with the mounting brackets. Damage caused to the parts by using incorrect screws would invalidate the warranty.
Step 3: Secure the brackets tightly.
Step 4: Follow the same steps to attach the second bracket to the opposite side.
Step 5: After the brackets are attached to the GPON OLT, use suitable screws to securely attach the brackets to the rack, as shown in Figure 2-10.
Figure 2-10 Mounting the GPON OLT on a Rack
2.3.2. Installing the Uplink Port
The sections describe how to insert an SFP transceiver into an SFP slot and UTP copper cable to RJ45 port. The SFP transceivers are hot-pluggable and hot-swappable. You can plug in and out the transceiver to/from any SFP port without having to power down the GPON OLT as Figure 2-11 shows.
Figure 2-11 Plugging in the SFP Transceiver
■Approved PLANET SFP Transceivers
PLANET GPON OLT supports both Single mode and Multi-mode SFP transceivers. The following list of approved PLANET SFP transceivers is correct at the time of publication:
1000BASE-X SFP modules:
Gigabit Ethernet Transceiver (1000BASE-X SFP)
| Model | Speed (Mbps) | Connector Interface | Fiber Mode | Distance | Wavelength (nm) | Operating Temp. |
| MGB-GT | 1000 | Copper | -- | 100m | -- | 0 ~ 60 °C |
| MGB-SX(V2) | 1000 | LC | Multi Mode | 550m | 850nm | 0 ~ 60 °C |
| MGB-SX2(V2) | 1000 | LC | Multi Mode | 2km | 1310nm | 0 ~ 60 °C |
| MGB-LX(V2) | 1000 | LC | Single Mode | 20km | 1310nm | 0 ~ 60°C |
| MGB-L40 | 1000 | LC | Single Mode | 40km | 1310nm | 0 ~ 60°C |
| MGB-L80 | 1000 | LC | Single Mode | 80km | 1550nm | 0 ~ 60°C |
| MGB-L120 | 1000 | LC | Single Mode | 120km | 1550nm | 0 ~ 60°C |
| MGB-TSX | 1000 | LC | Multi Mode | 550m | 850nm | -40 ~ 75°C |
| MGB-TSX2 | 1000 | LC | Multi Mode | 2km | 1310nm | -40 ~ 75°C |
| MGB-TLX(V2) | 1000 | LC | Single Mode | 20km | 1310nm | -40 ~ 75°C |
| MGB-TL40 | 1000 | LC | Single Mode | 40km | 1310nm | -40 ~ 75°C |
| MGB-TL80 | 1000 | LC | Single Mode | 80km | 1550nm | -40 ~ 75°C |
Gigabit Ethernet Transceiver (1000BASE-BX, Single Fiber Bi-directional SFP)
| Model | Speed (Mbps) | Connector Interface | Fiber Mode | Distance | Wavelength (TX) | Wavelength (RX) | Operating Temp. |
| MGB-LA10(V2) | 1000 | WDM(LC) | Single Mode | 10km | 1310nm | 1550nm | 0 ~ 60°C |
| MGB-LB10(V2) | 1000 | WDM(LC) | Single Mode | 10km | 1550nm | 1310nm | 0 ~ 60°C |
| MGB-LA20(V2) | 1000 | WDM(LC) | Single Mode | 20km | 1310nm | 1550nm | 0 ~ 60°C |
| MGB-LB20(V2) | 1000 | WDM(LC) | Single Mode | 20km | 1550nm | 1310nm | 0 ~ 60°C |
| MGB-LA40(V2) | 1000 | WDM(LC) | Single Mode | 40km | 1310nm | 1550nm | 0 ~ 60°C |
| MGB-LB40(V2) | 1000 | WDM(LC) | Single Mode | 40km | 1550nm | 1310nm | 0 ~ 60°C |
| MGB-LA80 | 1000 | WDM(LC) | Single Mode | 80km | 1490nm | 1550nm | 0 ~ 60°C |
| MGB-LB80 | 1000 | WDM(LC) | Single Mode | 80km | 1550nm | 1490nm | 0 ~ 60°C |
| MGB-TLA10(V2) | 1000 | WDM(LC) | Single Mode | 10km | 1310nm | 1550nm | -40 ~ 75°C |
| MGB-TLB10(V2) | 1000 | WDM(LC) | Single Mode | 10km | 1550nm | 1310nm | -40 ~ 75°C |
| MGB-TLA20 | 1000 | WDM(LC) | Single Mode | 20km | 1310nm | 1550nm | -40 ~ 75°C |
| MGB-TLB20 | 1000 | WDM(LC) | Single Mode | 20km | 1550nm | 1310nm | -40 ~ 75°C |
| MGB-TLA40 | 1000 | WDM(LC) | Single Mode | 40km | 1310nm | 1550nm | -40 ~ 75°C |
| MGB-TLB40 | 1000 | WDM(LC) | Single Mode | 40km | 1550nm | 1310nm | -40 ~ 75°C |
| MGB-TLA80 | 1000 | WDM(LC) | Single Mode | 80km | 1490nm | 1550nm | -40 ~ 75°C |
| MGB-TLB80 | 1000 | WDM(LC) | Single Mode | 80km | 1550nm | 1490nm | -40 ~ 75°C |
10Gigabit Ethernet Transceiver (10GBASE-X SFP+)
| Model Speed (Mbps) | Connector Interface | Fiber Mode | Distance | Wavelength (nm) | Operating Temp. | |
| MTB-SR | 10G | LC | Multi Mode | 300m | 850nm | 0 ~ 60°C |
| MTB-LR | 10G | LC | Single Mode | 10km | 1310nm | 0 ~ 60°C |
10Gigabit Ethernet Transceiver (10GBASE-BX, Single Fiber Bi-directional SFP+)
| Model | Speed (Mbps) | Connector Interface | Fiber Mode | Distance | Wavelength (TX) | Wavelength (RX) | Operating Temp. |
| MTB-LA20 | 1000 | WDM(LC) | Single Mode | 20km | 1270nm | 1330nm | 0 ~ 60°C |
| MTB-LB20 | 1000 | WDM(LC) | Single Mode | 20km | 1330nm | 1270nm | 0 ~ 60°C |
| MTB-LA40 | 1000 | WDM(LC) | Single Mode | 40km | 1270nm | 1330nm | 0 ~ 60°C |
| MTB-LB40 | 1000 | WDM(LC) | Single Mode | 40km | 1330nm | 1270nm | 0 ~ 60°C |
| MTB-LA60 | 1000 | WDM(LC) | Single Mode | 60km | 1270nm | 1330nm | 0 ~ 60°C |
| MTB-LB60 | 1000 | WDM(LC) | Single Mode | 60km | 1330nm | 1270nm | 0 ~ 60°C |
GPON OLT GPL-8000 SFP ports are configured in 1000Mbps Forced Mode. To make the connection successfully, the switch's SFP ports should also be in 1000Mbps Forced Mode. Otherwise, the connection might fail.
Before connecting the other GPON OLT, workstation or media converter,
- Make sure both sides of the SFP transceiver are with the same media type, for example, 1000BASE-SX to 1000BASE-SX, or 1000BASE-LX to 1000BASE-LX.
- Check whether the fiber-optic cable type matches the SFP transceiver model.
To connect to 1000BASE-SX SFP transceiver, use the multi-mode fiber cable, with one side being male duplex LC connector type.
To connect to 1000BASE-LX SFP transceiver, use the single-mode fiber cable, with one side being male duplex LC connector type.
■Connecting the fiber cable
- Insert the duplex LC connector on the network cable into the SFP transceiver.
- Connect the other end of the cable to a device – switches with SFP installed, fiber NIC on a workstation or a media converter.
- Check the LNK/ACT LED of the SFP port on the front of the GPON OLT. Ensure that the SFP transceiver is operating correctly.
- Check the Link mode of the SFP port if the link fails. It works well with some fiber-NICs or media converters. Set the Link mode to "1000 Force" if needed.
■Removing the transceiver module
- Make sure there is no network activity by consulting or checking with the network administrator. Or through the management interface of the switch/converter (if available), disable the port in advance.
- Remove the Fiber Optic Cable gently.
- Turn the handle of the MGB module to a horizontal position.
- Pull out the module gently through the handle.
Figure 2-12 Pulling Out the SFP Transceiver
Never pull out the module without pulling the handle or the push bolts on the module. Directly pulling out the module with force could damage the module and SFP module slot of the GPON OLT.
3. Web-based Management
This section introduces the configuration and functions of the Web-based management.
3.1 About Web-based Management
The GPL-8000 offers management features that allow users to manage the OLT from anywhere on the network through a standard browser such as Microsoft Internet Explorer. The Web-based Management supports Internet Explorer 8.0 above.
The GPL-8000 can be configured through an Ethernet connection, making sure the manager PC must be set to the same IP subnet address with the OLT.
For example, the IP address of the GPON OLT is configured with 192.168.1.1 on Management Port, then the manager PC should be set to 192.168.1.x (where x is a number between 2 and 253, except 1 or 254), and the default subnet mask is 255.255.255.0.
If you have changed the default IP address of the OLT to 192.168.0.1 with subnet mask 255.255.255.0 via console, then the manager PC should be set to 192.168.0.x (where x is a number between 2 and 254) to do the relative configuration on manager PC.
flowchart
graph LR
A["PC/Workstation with COM Port and Terminal Emulation Software"] --> B["DB9 to RJ45"]
B --> C["Serial Cable"]
C --> D["RJ45 Console"]
3.2 Logging on to the Switch
Use Internet Explorer 8.0 or above Web browser. Enter the factory-default IP address to access the Web interface. The default IP of Management port is as follows:
http://192.168.1.1
When the following login screen appears, please enter the default username "admin" with password "admin" (or the username/password you have changed via console) to log in the main screen of OLT. The login screen in Figure 3-1-1 appears.
Figure 3-1 Login Screen
Default User name: admin
Default Password: admin
After entering the username and password, the main screen appears as Figure 3-2.
Figure 3-2 Web Main Page
The OLT menu on the left of the Web page lets you access all the commands and statistics the OLT provides.
Now, you can use the Web management interface to continue the OLT management or manage the ONU by Web interface. The OLT menu on the left of the web page lets you access all the commands and statistics the ONU provides.
- It is recommended to use Internet Explore 8.0 or above to access OLT.
- The changed IP address takes effect immediately after clicking on the Submit button; you need to use the new IP address to access the Web interface.
- For security reason, please change and memorize the new password after this first setup.
3.3 OLT Information
3.3.1. Device Information
This page shows the OLT information such as system name, serial number, hardware version, firmware version, MAC address and system time. The system name can be modified if need.
Figure 3-3 Web Main Page
3.3.2. Manage the Switch via SNMP Network Management Software
The followings are required by SNMP network management software to manage switches:
1) IP addresses are configured on the switch;
2) The IP address of the client host and that of the VLAN interface on the switch it subordinates to should be in the same segment;
3) If 2) is not met, the client should be able to reach an IP address of the switch through devices like routers;
4) SNMP should be enabled.
The host with SNMP network management software should be able to ping the IP address of the switch, so that when running, SNMP network management software will be able to find it and implement read/write operation on it. Details about how to manage switches via SNMP network management software will not be covered in this manual; please refer to “Simple Network Management software user manual”.
CLI Interface
The switch provides three management interfaces for users: CLI (Command Line Interface) interface, Web interface and Simple Network Management software. The command line interfaces for the switch can be classified into several modes. Each command mode enables you to configure different groupware. The command that can be used currently is up to the command mode where you are. You can enter the question mark in different command modes to obtain the available command list. Common command modes are listed in the following table:
| Command Mode | Login Mode | Prompt | Exit Mode |
| System monitoring mode | Enter Ctrl-p after the power is on. | monitor# | Run quit. |
| User mode | Log in. | Switch> | Run exit or quit. |
| Management mode | Enter enter or enablein user mode. | Switch# | Run exit or quit. |
| Office configuration mode | Enter config in management mode. | Switch_config# | Run exit or quit or Ctrl-z to directly back to the management mode. |
| Port configuration mode | Enter the interface command in office configuration mode, such as interface f0/1. | Switch_config_f0/1# | Run exit or quit or Ctrl-z to directly back to the management mode. |
Each command mode is unsuitable to subsets of some commands. If problem occurs when you enter commands, check the prompt and enter the question mark to obtain the available command list. Problem may occur when you run in incorrect command mode or you misspelled the command.
Pay attention to the changes of the interface prompt and the relative command mode in the following case:
Switch> enter
Password:
Switch# config
Switch_config# interface f0/1
Switch_config_f0/1# quit
Switch_config# quit
Switch#
3.3.3. Help Function
Use the question mark (?) and the direction mark to help you enter commands:
● The currently available command list can be presented if you enter a question mark.
OLT> ?
- The currently available commands starting with the known characters in the list can be displayed if you enter the known characters and then a question mark (without space).
OLT>s?
- The parameter list of a command will be obtained if you enter the command, press "Space" and enter the question mark.
OLT> show ?
- The previously entered commands can be presented if you press the “up” arrow key. If you continue press the “up” arrow key, more commands can be shown. If you press the “up” arrow key and then the “down” arrow key, the next command line following the current one can be presented.
3.3.4. Canceling a Command
To cancel a command or resume its default properties, add the keyword "no" before most commands. An example is given as follows:
no ip routing
3.3.5. Saving Configuration
You may need to save the configuration changes, so that you can recover the original configuration in case of system restarted or power cuts. You can use write command to save configuration in the Administration Mode or Global Configuration Mode.
4. Basic Configuration
4.1 System Management Configuration
4.1.1. File Management Configuration
4.1.1.1.Managing the file system
The filename in flash is no more than 20 characters and filenames are case insensitive.
4.1.1.2. Commands for the file system
The boldfaces in all commands are keywords. Others are parameters. The content in the square brakcet “[ ]” is optional.
| Command Description | |
| format | Formats the file system and delete all data. |
| Differment [filename] | Displays files and directory names. The file name in the symbol “[]” means to display files starting with several letters. The file is displayed in the following format:Index numberfile namelength established time |
| delete filename | Deletes a file. The system will prompt if the file does not exist. |
| md dirname Creates a directory. | |
| rd dirname | Deletes a directory. The system will prompt if the directory is not existed. |
| more filename | Displays the content of a file. If the file content cannot be displayed by one page, it will be displayed by pages. |
| cd Changes the path of the current file system. | |
| pwd | Displays the current path. |
4.1.1.3.Starting up from a file manually
monitor#boot flash
The previous command is to start a OLT software in the flash, which may contain multiple switch software.
- Parameter description
| Parameter | Description |
| local_filename | A file name stored in the flash memoryUsers must enter the file name. |
- Example
monitor#boot flash switch.bin
4.1.1.4. Updating software
User can use this command to download OLT system software locally or remotely to obtain version update or the custom-made function version (like data encryption and so on).
There are two ways of software update in monitor mode.
a) Through TFTP
monitor#copy tftpflash [ip\_addr]
The previous command is to copy file from the tftp server to the flash in the system. After you enter the command, the system will prompt you to enter the remote server name and the remote filename.
● Parameter description
| Parameter Description | |
| ip_addr | IP address of the tftp serverIf there is no specified IP address, the system will prompt you to enter the IP address after thecopycommand is run. |
- Example
The following example shows a main.bin file is read from the server, written into the switch and changed into the name switch. Bin.
monitor#copy tftp flash
Prompt: Source file name[]?main.bin
Prompt: Remote-server ip address[] ?192.168.20.1
Prompt: Destination file name [main.bin]?switch.bin
please wait ...
##########
########
##########
#######
TFTP: successfully receive 3377 blocks,1728902 bytes
monitor#
b) Through serial port communication protocol - zmodem
Use the download command to update software. Enter download ? to obtain help.
monitor#download c0
This command is to copy the file to the flash of system through zmodem. The system will prompt you to enter the port rate after you enter the command.
- Parameter description
| Parameter Description | |
| local_filename | Filename stored in the flashUsers must enter the filename. |
- Example
The terminal program can be the Hyper Terminal program in WINDOWS 95, NT 4.0 or the terminal emulation program in WINDOWS 3.X.
monitor#download c0 switch.bin
Prompt: speed [9600]?115200
Then, modify the rate to 115200. After reconnection, select send file in the transfer menu of hyper terminal (terminal emulation). The send file dialog box appears as follows:
Figure 4-1 Send files
Enter the all-path of the switch software main.bin that our company provides in the filename input box, choose Zmodem as the protocol. Click send to send the file.
After the file is transferred, the following information appears:
ZMODEM: successfully receive 36 blocks ,18370 bytes
It indicates that the software update is completed, and then the baud rate of the hyper terminal should be reset to 9600.
4.1.1.5. Updating configuration
The switch configuration is saved as a file, the filename is startup-config. You can use commands similar to software update to update the configuration.
a) Through TFTP
monitor#copy tftp flash startup-config
b) Through serial port communication protocol—zmodem.
monitor#download c0 startup-config
4.1.1.6. Using ftp to perform the update of software and configuration
config #copy ftpflash [ip\_addr|option]
Use ftp to perform the update of software and configuration in formal program management. Use the copy command to download a file from ftp server to switch, also to upload a file from file system of the switch to ftp server. After you enter the command, the system will prompt you to enter the remote server name and remote filename.
copy{ftp: [[//login-name: [login-password]@]location]/directory]/filename}|flash: filename>}{flash<:filename>|ftp: [[//login-name: [login-password]@]location]/directory]/filename}
- Parameter description
| Parameter Description | |
| login-nam | Username of the ftp serverIf there is no specified username, the system will prompt you to enter the username after thecopycommand is run. |
| login-password | Password of the ftp serverIf there is no specified password, the system will prompt you to enter the password after thecopycommand is run. |
| ip_addr | IP address of the ftp serverIf there is no specified IP address, the system will prompt you to enter the IP address after executing thecopycommand. |
| active Means to connect the ftp server in active mode. | |
| passive Means to connect the ftp server in passive mode. | |
| type Set the data transmission mode (ascii or binary) | |
- Example
The following example shows a main.bin file is read from the server, written into the switch and changed into the name switch. Bin.
config#copy ftp flash
Prompt: ftp user name[anonymous]? login-nam
Prompt: ftp user password[anonymous]? login-password
Prompt: Source file name[]?main.bin
Prompt: Remote-server ip address[]?192.168.20.1
Prompt: Destination file name[main.bin]?switch.bin
or
config#copy ftp: //login-nam: login-password@192.168.20.1/main.bin flash: switch.bin
FTP: successfully receive 3377 blocks, 1728902 bytes
config#
-
When the ftp server is out of service, the wait time is long. If this problem is caused by the tcp timeout time (the default value is 75s), you can configure the global command ip tcp synwait-time to modify the tcp connection time. However, it is not recommended to use it.
-
When you use ftp in some networking conditions, the rate of data transmission might be relatively slow. You can properly adjust the size of the transmission block to obtain the best effect. The default size is 512 characters, which guarantee a relatively high operation rate in most of the networks.
4.1.2. Basic System Management Configuration
4.1.2.1.Configuring Ethernet IP address
monitor#ip address
This command is to configure the IPaddress of the Ethernet.,The default IP address is 192.168.1.1,and the network mask is255.255.255.0.
- Parameter description
| Parameter Description | |
| ip_addr | IP address of the Ethernet |
| net_mask | Mask of the Ethernet |
Example
monitor#ip address 192.168.0.1 255.255.255.0
4.1.2.2. Configuring default route
monitor#ip route default
This command is used to configure the default route. You can configure only one default route.
Parameter description
| Parameter Description | |
| ip_addr | IP address of the gateway |
- Example
monitor#ip route default 192.168.0.1
4.1.2.3. Using ping to test network connection state
monitor#ping
This command is to test network connection state.
- Parameter description
| Parameter Description | |
| ip_address | Destination IP address |
- Example
monitor#ping 192.168.20.100
PING 192.168.20.100: 56 data bytes
64 bytes from 192.168.20.100: icmp_seq=0. time=0. ms
64 bytes from 192.168.20.100: icmp_seq=1. time=0. ms
64 bytes from 192.168.20.100: icmp_seq=2. time=0. ms
64 bytes from 192.168.20.100: icmp_seq=3. time=0. ms
----192.168.20.100 PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0
4.1.3. HTTP Configuration
4.1.3.1. Configuring HTTP
● Enabling the http service
- Modifying the port number of the http service
- Configuring the access password of the http service
- Specifying the access control list for the http service
a) Enabling the http service
The http service is disabled by default.
The http service is enabled in the global configuration mode using the following command:
| Command Function | |
| Ip http server Enables the http service. |
b) Modifying the port number of the http service
The number of the listen port for the http service is 80.
The port number of the http service is modified in global configuration mode using the following command:
| Command Function | |
| Ip http port number | Modifies the port number of the http service. |
c) Configuring the access password of the http service
Http uses enable as the access password. You need to set the password enable if you want to perform authentication for http access. The password enable is set in global configuration mode using the following command:
| Command Function | |
| Enable password {0|7} line | Sets the password enable. |
d) Specifying the access control list for the http service
To control the host's access to http server, you can specify the access control list for http service. To specify an access control list, use the following command in global configuration mode:
| Command Function | |
| ip http access-class STRING | Specifies an access control list for the http service. |
4.1.3.2. Examples to http configuration
The following example uses default port (80) as the http service port, and the access address is limited to 192.168.20.0/24:
- ip acl configuration:
ip access-list standard http-acl
permit 192.168.20.0 255.255.255.0
- global configuration:
ip http access-class http-acl
ip http server
4.2 Terminal Configuration
4.2.1. VTY Configuration Introduction
The system uses the line command to configure terminal parameters. Through the command, you can configure the width and height that the terminal displays.
4.2.2. Configuration Task
The system has four types of lines: console, aid, asynchronous and virtual terminal. Different systems have different numbers of lines of these types. Refer to the following software and hardware configuration guide for the proper configuration.
| Line Type | Interface | Description | Numbering |
| CON (CTY) | Console | To log in to the system for configuration. | 0 |
| VTY | Virtual and asynchronous | To connect Telnet, X.25 PAD, HTTP and Rlogin of synchronous ports (such as Ethernet and serial port) on the system | 32 numbers starting from 1 |
4.2.2.1.Relationship between line and interface
a) Relationship between synchronous interface and VTY line
The virtual terminal line provides a synchronous interface to access to the system. When you connect to the system through VTY line, you actually connect to a virtual port on an interface. For each synchronous interface, there can be many virtual ports.
For example, if several Telnets are connecting to an interface (Ethernet or serial interface), you need to do the following steps for the VTY configuration:
(1) Log in to the line configuration mode.
(2) Configure the terminal parameters.
For VTY configuration, refer to Part 4.2.4 "VTY configuration example".
4.2.3. Monitoring and Maintenance
Run showline to check the VTY configuration.
4.2.4. Browsing Logs
By default, the system will export the logs to the console port. After the terminal monitor command is set on the telnet line, the logs will be exported to this line.
By default the logs will not be exported to the cache and cannot be browsed after you run show log. After you run logging buffer size to set the log cache, you can run show log to browse the log information.
4.2.5. VTY Configuration Example
It shows how to cancel the limit of the line number per screen for all VTYs without more prompt:
config#line vty 0 32
config_line#length 0
32 vty configuration timeout time
Switch_config#line vty 0 31
Switch_config_line#exec-timeout 10
Switch_config_line#exit
Switch_config#
4.3 Remote Monitoring
4.3.1. Configuring SNMP
The SNMP system includes the following parts:
• SNMP management side (NMS)
• SNMP agent (AGENT)
● Management information base (MIB)
SNMP is a protocol working on the application layer. It provides the packet format between SNMP management side and agent.
SNMP management side can be part of the network management system (NMS, like CiscoWorks). Agent and MIB are stored on the system. You need to define the relationship between network management side and agent before configuring SNMP on the system.
SNMP agent contains MIB variables. SNMP management side can check or modify value of these variables. The management side can get the variable value from agent or stores the variable value to agent. The agent collects data from MIB. MIB is the database of device parameter and network data. The agent also can respond to the loading of the management side or the request to configure data. SNMP agent can send trap to the management side. Trap sends alarm information to NMS indicating a certain condition of the network. Trap can point out improper user authentication, restart, link layer state(enable or disable), close of TCP connection, lose of the connection to adjacent systems or other important events.
a) SNMP notification
When some special events occur, the system will send 'inform' to SNMP management side. For example, when the agent system detects an abnormal condition, it will send information to the management side. SNMP notification can be treated as trap or inform request to send. Since the receiving side doesn't send any reply when receiving a trap, this leads to the receiving side cannot be sure that the trap has been received. Therefore the trap is not reliable. In comparison, SNMP management side that receives "inform request" uses PDU that SNMP echoes as the reply for this information. If no "inform request" is received on the management side, no echo will be sent. If the receiving side doesn't send any reply, then you can resend the "inform request". Then notifications can reach their destination.
Since inform requests are more reliable, they consume more resources of the system and network. The trap will be discarded when it is sent. The “inform request” has to be stored in the memory until the echo is received or the request timeouts. In addition, the trap is sent only once, while the “inform request” can be resent for many times. Resending "inform request" adds to network communications and causes more load on network. Therefore, trap and inform request provide balance between reliability and resource. If SNMP management side needs receiving every notification, then the “inform request” can be used. If you give priority to the communication amount of the network and there is no need to receive every notification, then trap can be used.
This switch only supports trap, but we provide the extension for "inform request".
b) SNMP version
System of our company supports the following SNMP versions:
- SNMPv1---simple network management protocol, a complete Internet standard, which is defined in RFC1157.
- SNMPv2C--- Group-based Management framework of SNMPv2, Internet test protocol, which is defined in RFC1901.
Layer 3 switch of our company also supports the following SNMP:
- SNMPv3--- a simple network management protocol version 3, which is defined in RFC3410.
SNMPv1 uses group-based security format. Use IP address access control list and password to define the management side group that can access to agent MIB.
SNMPv3 provides secure access to devices by a combination of authenticating and encrypting packets over the network.
The security features provided in SNMPv3 are:
- Message integrity—Ensuring that a packet has not been tampered with in-transit.
- Authentication—Determining the message is from a valid source.
- Encryption—Scrambling the contents of a packet prevent it from being seen by an unauthorized source. SNMPv3 provides for both security models and security levels. A security model is an authentication strategy that is set up for a user and the group in which the user resides. A security level is the permitted level of security within a security model. A combination of a security model and a security level will determine which security mechanism is employed when handling an SNMP packet. Three security models are available, that is, authentication and encryption, authentication and no encryption, no authentication.
You need to configure SNMP agent to the SNMP version that the management working station supports. The agent can communicate with many management sides.
c) Supported MIB
SNMP of our system supports all MIBII variables (which will be discussed in RFC 1213) and SNMP traps (which will be discussed in RFC 1215).
Our system provides its own MIB extension for each system.
4.3.1.2.SNMP Configuration Tasks
- Configuring SNMP view
- Creating or modifying the access control for SNMP community
-
Configuring the contact method of system administrator and the system's location
● Defining the maximum length of SNMP agent data packet
● Monitoring SNMP state -
Configuring SNMP trap
- Configuring SNMP binding source address
- Configuring NMPv3 group
- Configuring NMPv3 user
- Configuring NMPv3 EngineID
a) Configuring SNMP view
The SNMP view is to regulate the access rights (include or exclude) for MIB. Use the following command to configure the SNMP view.
| Command Description | |
| snmp-server view nameoid] [exclude | include] | Adds the subtree or table of OID-specified MIB to the name of the SNMP view, and specifies the access right of the object identifier in the name of the SNMB view.Exclude: decline to be accessedInclude: allow to be accessed |
The subsets that can be accessed in the SNMP view are the remaining objects that "include" MIB objects are divided by "exclude" objects. The objects that are not configured are not accessible by default.
After configuring the SNMP view, you can implement SNMP view to the configuration of the SNMP group name, limiting the subsets of the objects that the group name can access.
b) Creating or modifying the access control for SNMP community
You can use the SNMP community character string to define the relationship between SNMP management side and agent. The community character string is similar to the password that enables the access system to log in to the agent. You can specify one or multiple properties relevant with the community character string. These properties are optional:
Allowing to use the community character string to obtain the access list of the IP address at the SNMP management side
Defining MIB views of all MIB object subsets that can access the specified community
Specifying the community with the right to read and write the accessible MIB objects
Configure the community character string in global configuration mode using the following command:
| Command Function | |
| snmp-server communitystring[view view-name] [ro | rw] [word] | Defines the group access character string. |
You can configure one or multiple group character strings. Run no snmp-server community to remove the specified community character string.
For how to configure the community character string, refer to the part "SNMP Commands".
c) Configuring the contact method of system administrator and the system's location
SysContact and sysLocation are the management variables in the MIB's system group, respectively defining
the linkman's identifier and actual location of the controlled node. These information can be accessed through config. files. You can use the following commands in global configuration mode.
| Command Function | |
| snmp-server contacttext | Sets the character string for the linkman of the node. |
| snmp-server locationtext | Sets the character string for the node location. |
d) Defining the maximum length of SNMP agent data packet
When SNMP agent receives requests or sents responses, you can configure the maximum length of the data packet. Use the following command in global configuration mode:
| Command Function | |
| snmp-server packetsizebyte-count | Sets the maximum length of the data packet. |
e) Monitoring SNMP state
You can run the following command in global configuration mode to monitor SNMP output/input statistics, including illegal community character string items, number of mistakes and request variables.
| Command Function | |
| show snmp | Monitores the SNMP state. |
f) Configuring SNMP trap
Use the following command to configure the system to send the SNMP traps (the second task is optional):
- Configuring the system to send trap
Run the following commands in global configuration mode to configure the system to send trap to a host.
| Command Function | |
| snmp-server host host community-string[trap-type] | Specifies the receiver of the trap message. |
| snmp-server host host [traps|informs]{version {v1 | v2c | v3 {auth | noauth | priv }}}community-string [trap-type] | Specifies the receiver, version number and username of the trap message.Note: For the trap of SNMPv3, you must configure SNMP engine ID for the host before the host is configured to receive the trap message. |
When the system is started, the SNMP agent will automatically run. All types of traps are activated. You can use the command snmp-server host to specify which host will receive which kind of trap.
Some traps need to be controlled through other commands. For example, if you want SNMP link traps to be sent when an interface is opened or closed, you need to run snmp trap link-status in interface configuration mode to activate link traps. To close these traps, run the interface configuration command snmp trap link-stat.
You have to configure the command snmp-server host for the host to receive the traps.
- Modifying the running parameter of the trap
As an optional item, it can specify the source interface where traps originate, queue length of message or value of resending interval for each host.
To modify the running parameters of traps, you can run the following optional commands in global configuration mode.
| Command Function | |
| snmp-server trap-source interface | Specifies the source interface where traps originate and sets the source IP address for the message. |
| snmp-server queue-length length | Creates the queue length of the message for each host that has traps.Default value: 10 |
| snmp-server trap-timeoutseconds | Defines the frequency to resend traps in the resending queue.Default value: 30 seconds |
g) Configuring the SNMP binding source address
Run the following command in the global configuration mode to set the source address for the SNMP message.
| Command Function | |
| snmp source-addr ipaddress | Sets the source address for the SNMP message. |
h) Configuring SNMPv3 group
Run the following command to configure a group.
| Command Function | |
| snmp-server group [groupname {v1 | v2c |v3 [auth | noauth | priv]}][readreadview][writewriteview] [notifynotifyview] [accessaccess-list] | Configures a SNMPv3 group. You can only read all items in the subtree of the Internet by default. |
i) Configuring SNMPv3 user
You can run the following command to configure a local user. When an administrator logs in to a device, he has to user the username and password that are configured on the device. The security level of a user must be higher than or equals to that of the group which the user belongs to. Otherwise, the user cannot pass authentication.
| Command Function | |
| snmp-server user username groupname {v1 | v2c | v3 [encrypted] [auth {md5 | sha} auth-password]} [access access-list] | Configures a local SNMPv3 user. |
You can run the following command to configure a remote user. When a device requires to send traps to a remote control station, a remote user has to be configured if the control station performs ID authentication. Username and password of the remote user must be the same as those on the control station. Otherwise, the control station cannot receive traps.
| Command Function | |
| snmp-server user username groupname remote ip-address [udp-port port] {v1 | v2c | v3 [encrypted] [auth {md5 | sha} auth-password]} [access access-list] | Configures a remote SNMPv3 user. Note: A remote SNMP engine ID must be configured for the control station of the IP address before a remote user is configured. |
j) Configuring SNMPv3 Engine ID
The SNMP Engine ID is to identify an SNMP engine. Traditional SNMP manager and agent are part of the SNMP engine in the SNMPv3 frame.
| Command Function | |
| snmp-server engineID remoteip-address [udp-portport-number] engineid-string | Configures a remote SNMP engine. |
4.3.1.3. Configuration example
a) Example 1
snmp-server community public RO
snmp-server community private RW
snmp-server host 192.168.10.2 public
The above example shows:
- how to set the community string public that can only read all MIB variables.
- how to set the community string private that can read and write all MIB variables.
You can use the community string public to read MIB variables in the system. You can also use the community string private to read MIB variables and write writable MIB variables in the system.
The above command specifies the community string public to send traps to 192.168.10.2 when a system requires to send traps. For example, when a port of a system is in the down state, the system will send a linkdown trap information to 192.168.10.2.
b) Example 2
snmp-server engineID remote 90.0.0.3 80000523015a000003
snmp-server group getter v3 auth
snmp-server group setter v3 priv write v-write
snmp-server user get-user getter v3 auth sha 12345678
snmp-server user set-user setter v3 encrypted auth md5 12345678
snmp-server user notifier getter remote 90.0.0.3 v3 auth md5 abcdefghi
snmp-server host 90.0.0.3 informs version v3 auth notifier
snmp-server view v-write internet included
The above example shows how to use SNMPv3 to manage devices. Group getter can browse device information, while group setter can set devices. User get-user belongs to group getter while user set-user belongs to group setter.
For user get-user, its security level is authenticate but not encrypt, its password is 12345678, and it uses the sha arithmetic to summarize the password.
For user set-user, its security level is authenticate and encrypt, its password is 12345678, and it uses the md5 arithmetic to summarize the password.
When key events occur at a device, use username notifier to send inform messages to host 90.0.0.3 of the administrator.
4.3.2. RMON Configuration
4.3.2.1.RMON configuration task
RMON configuration tasks include:
- Configuring the rMon alarm function for the switch
- Configuring the rMon event function for the switch
- Configuring the rMon statistics function for the switch
- Configuring the rMon history function for the switch
● Displaying the rMon configuration of the switch
a) Configuring rMon alarm for switch
You can configure the rMon alarm function through the command line or SNMP NMS. If you configure
through SNMP NMS, you need to configure the SNMP of the switch. After the alarm function is configured, the device can monitor some statistic value in the system. The following table shows how to set the rMon alarm function:
| Command Function | |
| configure | Enter the global configuration mode. |
| rmon alarm indexvariableinterval{absolute | delta} rising-thresholdvalue[eventnumber] falling-thresholdvalue[eventnumber] [ownerstring] | Add a rMon alarm item.indexis the index of the alarm item. Its effective range is from 1 to 65535.variableis the object in the monitored MIB. It must be an effective MIB object in the system. Only obejects in the Integer, Counter, Gauge or TimeTicks type can be detected.intervalis the time section for sampling. Its unit is second. Its effective value is from 1 to 4294967295.absoluteis used to directly monitor the value of MIB object.deltais used to monitor the value change of the MIB objects between two sampling.valueis the threshold value when an alarm is generated.eventnumberis the index of an event that is generated when a threshold is reached.eventnumberis optional.owner stringis to describe the information about the alarm. |
| exit Enter the management mode again. | |
| write Save the configuration. |
After a rMon alarm item is configured, the device will obtain the value of variable-specified oid after an interval. The obtained value will be compared with the previous value according to the alarm type (absolute or delta). If the obtained value is bigger than the previous value and surpasses the threshold value specified by rising-threshold, an event whose index is eventnumber (If the value of eventnumber is 0 or the event whose index is eventnumber does not exist in the event table, the event will not occur). If the variable-specified oid cannot be obtained, the state of the alarm item in this line is set to invalid. If you run rmon alarm many times to configure alarm items with the same index, only the last configuration is effective. You can run no rmon alarm index to cancel alarm items whose indexes are index.
b) Configuring rMon event for switch
The steps to configure the rMon event are shown in the following table:
| Step | Command | Purpose |
| 1. | configure | Enter the global configuration mode. |
| 2. | rmon eventindex[descriptionstring][log] [ownerstring] [trap community] | Add an rMon event item.index means the index of the event item. Its effective range is from 1 to 65535.description means the information about the event.log means to add a piece of information to the log table when a event is triggered. trap means a trap message is generated when the event is triggered. community means the name of a community. owner string is to describe the information about the alarm. |
| 3. | exit | Enter the management mode again. |
| 4. | write | Save the configuration. |
After a rMon event is configured, you must set the domain eventLastTimeSent of the rMon event item to sysUpTime when a rMon alarm is triggered. If the log attribute is set to the rMon event, a message is added to the log table. If the trap attribute is set to the rMon event, a trap message is sent out in name of community. If you run rmon event many times to configure event items with the same index, only the last configuration is effective. You can run no rmon event index to cancel event items whose indexes are index.
c) Configuring rMon statistics for switch
The rMon statistics group is used to monitor the statistics information on every port of the device. The steps to configure the rMon statistics are as follows:
| Step | Command | Purpose |
| 1. | configure | Enter the global configuration mode. |
| 2. | interface iftype ifid | Enter the port mode.iftype means the type of the port.ifid means the ID of the interface. |
| 3. | rmon collectionstat index [ownerstring] | Enable the statistics function on the port.index means the index of the statistics.owner string is to describe the information about the statistics. |
| 4. | exit | Enter the global office mode. |
| 5. | exit | Enter the management mode again. |
| 6. | write | Save the configuration. |
If you run rmon collection stat many times to configure statistics items with the same index, only the last configuration is effective. You can run no rmon collection stats index to cancel statistics items whose indexes are index.
d) Configuring rMon history for switch
The rMon history group is used to collect statistics information of different time sections on a port in a device. The rMon statistics function is configured as follows:
| Step | Command | Purpose |
| 1. | configure | Enter the global configuration command. |
| 2. | interface iftype ifid | Enter the port mode.iftype means the type of the port.ifid means the ID of the interface. |
| 3. rmon collection history index [buckets bucket-number] [interval second] [owner owner-name] | Enable the history function on the port.index means the index of the history item.Among all data collected by history item, the latestbucket-number items need to be saved. You can browse the history item of the Ethernet to abtain these statistics values. The default value is 50 items.second means the interval to abtain the statistics data every other time. The default value is 1800 seconds.owner string is used to describe some information about the history item. | |
| 4. | exit | Enter the global office mode again. |
| 5. | exit | Enter the management mode again. |
| 6. | write | Save the configuration. |
After a rMon history item is added, the device will obtain statistics values from the specified port every second seconds. The statistics value will be added to the history item as a piece of information. If you run rmon collection history index many times to configure history items with the same index, only the last configuration is effective. You can run no rmon history index to cancel history items whose indexes are index.
Too many system sources will be occupied; in the case. the value of bucket-number is too big or the value of interval second is too small.
e) Displaying rMon configuration of switch
Run show to display the rMon configuration of the switch.
| Command Purpose | |
| show rmon [alarm] [event][statistics] [history] | Displays the rmon configuration information.alarm means to display the configuration of the alarm item.event means to show the configuration of the event item and to show the items that are generated by the occurrence of events and are contained in the log table.statistics means to display the configuration of the statistics item and statistics values that the device collects from the port.history means to display the configuration of the history item and statistics values that the device collects in the latest specified intervals from the port. |
4.3.3.Configuring PDP
4.3.3.1. Introduction
PDP is a two-layer protocol specially used to detect network devices. PDP is used in Network Management Service (NMS) to detect all neighboring devices of an already known device. Using PDP enable you to learn the SNMP agent address and the types of neighboring devices. After neighboring devices are detected through PDP, the NMS can require neighboring devices through SNMP to obtain the network topology. Our switches can detect neighboring devices through PDP, but cannot require neighboring devices through SNMP. Therefore, these switches have to be located at the verge of networks. Otherwise, the complete network topology cannot be obtained.
PDP on switches can be configured on all SANPs, such as Ethernet.
4.3.3.2. PDP configuration tasks
● Default PDP configuration of the switch
- Setting the PDP clock and information saving time
- Setting the PDP version
● Enabling the PDP on the switch
● Enabling the PDP on the port of the switch
● Monitoring and managing PDP
a) Default PDP configuration of the switch
| Function Default Setting | |
| PDP global configuration state Disabled | |
| PDP port configuration state Disabled | |
| PDP clock (frequency for sending messages) | 60 seconds |
| PDP information saving 180 seconds | |
| PDP version 2 |
b) Setting the PDP clock and information saving time
Run the following commands in global configuration mode to set the frequency for PDP to send messages and the PDP information saving time:
| Command Purpose | |
| pdp timer seconds | Sets the frequency for PDP to send messages. |
| pdp holdtimeseconds | Sets the PDP information saving time. |
c) Setting the PDP version
Run the following command in global configuration mode to set the PDP version:
| Command Purpose | |
| pdp version {1|2} | Sets the PDP version. |
d) Enabling PDP on the switch
PDP is not enabled in the default configuration. If you want to use PDP, run the following command in global configuration mode.
| Command Purpose | |
| pdp run | Enables the PDP on the switch. |
e) Enabling PDP on the port of the switch
PDP is not enabled in the default configuration. You can run the following command in interface configuration mode to enable PDP on the port after PDP is enabled on the switch.
| Command | Purpose |
| pdp enable | Enables PDP on the port of the switch. |
f) Monitoring and managing PDP
Run the following commands in management mode to monitor PDP:
| Command | Purpose |
| show pdp traffic | Displays the number of PDP messages that the switch receives and sends. |
| show pdp neighbor [detail] | Displays neighboring devices that the switch detects through PDP. |
4.3.3.3.PDP configuration examples
Example 1: Enabling PDP
config# pdp run
config# int f0/0
config_f0/0#pdp enable
Example 2: Setting the PDP clock and information saving time
config#pdp timer 30
config#pdp holdtime 90
Example 3: Setting the PDP version
config#pdp version 1
Example 4: Monitoring PDP information
config#show pdp neighbors
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge S - Switch, H -
Host, I - IGMP, r - Repeater
Device ID Local IntrfceHoldtmeCapabilityPlatform Port ID
joeEth 0 133 4500 Eth 0
samEth 0 152 R AS5200 Eth 0
4.4 SSH Configuration commands
4.4.1. Introduction
4.4.1.1. SSH server
A scure and encrypted communication connection can be created between SSH client and the device through SSH server. The connection has telnet-like functions. SSH server supports the encryption algorithms including des, 3des and blowfish.
4.4.1.2. SSH client
SSH client is an application running under the ssh protocol. SSH client can provide authentication and encryption, so SSH client guarantees secure communication between communication devices or devices supporting SSH server even if these devices run in unsafe network conditions. SSH client supports the encryption algorithms including des, 3des and blowfish.
4.4.1.3. Function
SSH server and SSH client supports version 1.5. Both of them only support the shell application.
4.4.2. Configuration Tasks
4.4.2.1.Configuring the authentication method list
SSH server adopts the login authentication mode. SSH server uses the default authentication method list by default.
Run the following command in global configuration command mode to configure the authentication method list:
| Command Purpose | |
| Ip sshd auth_method STRING | Configures the authentication method list. |
4.4.2.2.Configuring the access control list
To control the access to the device's SSH server, you need to configure the access control list for SSH server. Run the following command in global configuration mode to configure the access control list:
| Command Purpose | |
| Ip sshd access-class STRING | Configures the access control list. |
4.4.2.3.Configuring the authentication timeout value
After a connection is established between client and server, server cuts off the connection if authentication cannot be approved within the set time.
Run the following command in global configuration mode to configure the configuration timeout value:
| Command Purpose | |
| lp sshd timeout <60-65535> | Configures the authentication timeout value. |
4.4.2.4.Configuring the times of authentication retrying
If the times for failed authentications exceed the maximum times, SSH server will not allow you to retry authentication unless a new connection is established. The maximum times for retrying authentication is 3 by default.
Run the following command in global configuration mode to configure the maximum times for retrying authentication:
| Command Purpose | |
| Ip sshd auth-retries <0-65535> | Configures the maximum times for retrying authentication. |
4.4.2.5. Enabling SSH server
SSH server is disabled by default. When SSH server is enabled, the device will generate a rsa password pair, and then listen connection requests from the client. The process takes one or two minutes.
Run the following command in global configuration mode to enable SSH server:
| Command Purpose | |
| Ip sshd enable | Enables SSH server. The digit of the password is 1024. |
4.4.3.SSH server Configuration Example
The following configuration only allows the host whose IP address is 192.168.20.40 to access SSH server. The local user database is used to distinguish user ID.
4.4.3.1. Access control list
ip access-list standard ssh-acl
permit 192.168.20.40
4.4.3.2. Global configuration
aaa authentication login ssh-auth local
ip sshd auth-method ssh-auth
ip sshd access-class ssh-acl
ip sshd enable
5. Remote Monitoring
5.1 Remote Monitoring
5.1.1 SNMP Configuration
5.1.2 Overview
The SNMP system includes the following 3 parts:
• SNMP management server (NMS)
- SNMP agent (agent)
• MIB
SNMP is a protocol for the application layer. It provides the format for the packets which are transmitted between NMS and agent.
SNMP management server is a part of the network management system, such as CiscoWorks.
SNMP agent includes the MIB variable and the SNMP management server can be used to browse or change these variables' values. The management server can get the values from the agent or save these variables in the agent. The agent collects data from MIB. MIB is the database of equipment parameters and network data.
5.1.3 SNMP Notification
When a special event occurs, the system will send an inform to the SNMP management server. For example, when the agent system runs into a incorrect condition, it will send a message to the management server.
The SNMP notification can be sent as a trap or a inform request. Because the receiver receives a trap and does not send any response, the transmitter hence cannot confirm whether the trap is received. In this way, the trap is unreliable. Comparatively, the SNMP management server uses SNMP to respond PDU, which is acted as a response of this message. If the management server does not receive the inform request, it will not transmit a response. If the transmitter does not receive the response, it will transmit the inform request again. In this way, the inform has more chance to arrive the planned destination.
5.1.4 SNMP Tasks
- Configuring idle time value
- Configuring the time value of waiting for acknowledgement
- Configuring busy time value of remote end
- Configuring time value of Response
- Configuring the time of reject
- Configuring the redial times
- Configuring the size of window for resend
- Configuring the size of accumulated data packet
- Setting the acknowledgement time-delay
- Setting the maximum numbers of acknowledgement
• Showing LLC2 link information
● Debugging LLC2 link information
6. Security Configuration
6.1 AAAConfiguration
6.1.1 AAA Overview
Access control is the way to control access to the network and services. Authentication, authorization, and accounting (AAA) network security services provide the primary framework through which you set up access control on your router or access server.
6.1.1.1 AAA Security Service
AAA is an architectural framework for configuring a set of three independent security functions in a consistent manner. AAA provides a modular way of performing the following services:
- Authentication—Provides the method of identifying users, including login and password dialog, challenge and response, messaging support, and, depending on the security protocol you select, encryption.
Authentication is the way a user is identified prior to being allowed access to the network and network services. You configure AAA authentication by defining a named list of authentication methods, and then applying that list to various interfaces. The method list defines the types of authentication to be performed and the sequence in which they will be performed; it must be applied to a specific interface before any of the defined authentication methods will be performed. The only exception is the default method list (which is named "default"). The default method list is automatically applied to all interfaces if no other method list is defined. A defined method list overrides the default method list.
All authentication methods, except for local, line password, and enable authentication, must be defined through AAA. For information about configuring all authentication methods, including those implemented outside of the AAA security services, refer to the chapter "Configuring Authentication."
- Authorization—Provides the method for remote access control, including one-time authorization or authorization for each service, per-user account list and profile, user group support, and support of IP, IPX, ARA, and Telnet.
AAA authorization works by assembling a set of attributes that describe what the user is authorized to perform. These attributes are compared to the information contained in a database for a given user and the result is returned to AAA to determine the user's actual capabilities and restrictions. The database can be located locally on the access server or router or it can be hosted remotely on a RADIUS or TACACS+ security server. Remote security servers, such as RADIUS and TACACS+, authorize users for specific rights by associating attribute-value (AV) pairs, which define those rights with the appropriate user. All authorization methods must be defined through AAA.
As with authentication, you configure AAA authorization by defining a named list of authorization methods, and then applying that list to various interfaces. For information about configuring authorization using AAA, refer to the chapter "Configuring Authorization."
- Accounting—Provides the method for collecting and sending security server information used for billing, auditing, and reporting, such as user identities, start and stop times, executed commands (such as PPP), number of packets, and number of bytes.
Accounting enables you to track the services users are accessing as well as the amount of network resources they are consuming. When AAA accounting is activated, the network access server reports user activity to the RADIUS or TACACS+ security server (depending on which security method you have implemented) in the form of accounting records. Each accounting record is comprised of accounting AV pairs and is stored on the access control server. This data can then be analyzed for network management, client billing, and/or auditing. All accounting methods must be defined through AAA. As with authentication and authorization, you configure AAA accounting by defining a named list of accounting methods, and then applying that list to various interfaces. For information about configuring accounting using AAA, refer to the chapter "Configuring Accounting."
6.1.1.2 Benefits of Using AAA
AAA provides the following benefits:
- Increased flexibility and control of access configuration
- Scalability
- Standardized authentication methods, such as RADIUS, TACACS+, and Kerberos
● Multiple backup systems
6.1.1.3 AAA Principles
AAA is designed to enable you to dynamically configure the type of authentication and authorization you want on a per-line (per-user) or per-service (for example, IP, IPX, or VPDN) basis. You define the type of authentication and authorization you want by creating method lists, then applying those method lists to specific services or interfaces.
6.1.1.4 Method Lists
A method list is a sequential list that defines the authentication methods used to authenticate a user. Method lists enable you to designate one or more security protocols to be used for authentication, thus ensuring a backup system for authentication in case the initial method fails. Cisco IOS software uses the first method listed to authenticate users; if that method does not respond, Cisco IOS software selects the next authentication method in the method list. This process continues until there is successful communication with a listed authentication method or the authentication method list is exhausted, in which case authentication fails.
The software attempts authentication with the next listed authentication method only when there is no response from the previous method. If authentication fails at any point in this cycle—meaning that the security server or local username database responds by denying the user access—the authentication process stops and no other authentication methods are attempted. The following figures show a typical AAA network configuration that includes four security servers: R1 and R2 are RADIUS servers, and T1 and T2 are TACACS+ servers.
flowchart
graph LR
A["Remote PC"] --> B["NAS"]
B --> C["R1: RADIUS server"]
B --> D["R2: RADIUS server"]
B --> E["T1: TACACS+ server"]
B --> F["T2: TACACS+ server"]
B --> G["Workstation 96746"]
Figure 6-1 Typical AAA Network Configuration
Suppose the system administrator has defined a method list where R1 will be contacted first for authentication information, then R2, T1, T2, and finally the local username database on the access server itself. When a remote user attempts to dial in to the network, the network access server first queries R1 for authentication information. If R1 authenticates the user, it issues a PASS response to the network access server and the user is allowed to access the network. If R1 returns a FAIL response, the user is denied access and the session is terminated. If R1 does not respond, then the network access server processes that as an ERROR and queries R2 for authentication information. This pattern continues through the remaining designated methods until the user is either authenticated or rejected, or until the session is terminated. If all of the authentication methods return errors, the network access server will process the session as a failure, and the session will be terminated.
A FAIL response is significantly different from an ERROR. A FAIL means that the user has not met the criteria contained in the applicable authentication database to be successfully authenticated. Authentication ends with a FAIL response. An ERROR means that the security server has not responded to an authentication query. Because of this, no authentication has been attempted. Only when an ERROR is detected will AAA select the next authentication method defined in the authentication method list.
6.1.2 AAA Configuration Process
You must first decide what kind of security solution you want to implement. You need to assess the security risks in your particular network and decide on the appropriate means to prevent unauthorized entry and attack.
6.1.2.1 Overview of the AAA Configuration Process
Configuring AAA is relatively simple after you understand the basic process involved. To configure security on a Cisco router or access server using AAA, follow this process:
- If you decide to use a separate security server, configure security protocol parameters, such as RADIUS, TACACS+, or Kerberos.
- Define the method lists for authentication by using an AAA authentication command.
- Apply the method lists to a particular interface or line, if required.
- (Optional) Configure authorization using the AAA authorization command.
- (Optional) Configure accounting using the AAA accounting command.
6.1.3 AAA Authentication Configuration Task List
- Configuring Login Authentication Using AAA
- Configuring PPP Authentication Using AAA
● Enabling Password Protection at the Privileged Level - Configuring Message Banners for AAA Authentication
- AAA authentication username-prompt
- AAA authentication password-prompt
- Establishing Username Authentication
- Enabling Password
6.1.4 AAA Authentication Configuration Task
To configure AAA authentication, perform the following configuration processes:
- If you decide to use a separate security server, configure security protocol parameters, such as RADIUS, TACACS+, or Kerberos.
- Define the method lists for authentication by using an AAA authentication command.
- Apply the method lists to a particular interface or line, if required.
6.1.4.1 Configuring Login Authentication Using AAA
The AAA security services facilitate a variety of login authentication methods. Use the aaa authentication login command to enable AAA authentication no matter which of the supported login authentication methods you decide to use. With the aaa authentication login command, you create one or more lists of authentication methods that are tried at login. These lists are applied using the login authentication line configuration command.
To configure login authentication by using AAA, use the following commands beginning in global configuration mode:
| Command Purpose | |
| aaa authentication login {default | list-name}method1 [method2...] | Enables AAA globally. |
| line [ console | vty ] line-number [ending-line-number] | Enters line configuration mode for the lines to which you want to apply the authentication list. |
| login authentication {default | list-name} | Applies the authentication list to a line or set of lines. |
The list-name is a character string used to name the list you are creating. The method argument refers to the actual method the authentication algorithm tries. The additional methods of authentication are used only if the previous method returns an error, not if it fails. To specify that the authentication should succeed even if all methods return an error, specify none as the final method in the command line.
For example, to specify that authentication should succeed even if (in this example) the TACACS+ server returns an error, enter the following command:
aaa authentication login default group radius
Because the none keyword enables any user to log in for authentication, it should be used only as a backup method of authentication.
The following table lists the supported login authentication methods.:
| Keyword description | |
| enable | Uses the enable password for authentication. |
| group name | Uses named server group for authentication. |
| group radius | Uses the list of all RADIUS servers for authentication. |
| line Uses the line | password for authentication. |
| local | Uses the local username database for authentication. |
| local-case | Uses case-sensitive local username authentication. |
| none Uses no authentication. | |
(1) Login Authentication Using Enable Password
Use the aaa authentication login command with the enable method keyword to specify the enable password as the login authentication method. For example, to specify the enable password as the method of user authentication at login when no other method list has been defined, enter the following command: aaa authentication login default enable
(2) Login Authentication Using Line Password
Use the aaa authentication login command with the line method keyword to specify the line password as the login authentication method. For example, to specify the line password as the method of user authentication at login when no other method list has been defined, enter the following command:
aaa authentication login default line
Before you can use a line password as the login authentication method, you need to define a line password.
(3) Login Authentication Using Local Password
Use the aaa authentication login command with the local method keyword to specify that the Cisco router or access server will use the local username database for authentication. For example, to specify the local username database as the method of user authentication at login when no other method list has been defined, enter the following command:
aaa authentication login default local
For information about adding users into the local username database, refer to the section "Establishing Username Authentication" in this chapter.
(4) Login Authentication Using Group RADIUS
Use the aaa authentication login command with the group radius method to specify RADIUS as the login authentication method. For example, to specify RADIUS as the method of user authentication at login when no other method list has been defined, enter the following command:
aaa authentication login default group radius
Before you can use RADIUS as the login authentication method, you need to enable communication with the RADIUS security server. For more information about establishing communication with a RADIUS server, refer to the chapter "Configuring RADIUS."
6.1.4.2 Enabling Password Protection at the Privileged Level
Use the aaa authentication enable default command to create a series of authentication methods that are used to determine whether a user can access the privileged EXEC command level. You can specify up to four authentication methods. The additional methods of authentication are used only if the previous method returns an error, not if it fails. To specify that the authentication should succeed even if all methods return an error, specify none as the final method in the command line.
Use the following command in global configuration mode:
| Command Purpose | |
| aaa authentication enable defaultmethod1 [method2...] | Enables user ID and password checking for users requesting privileged EXEC level. |
The method argument refers to the actual list of methods the authentication algorithm tries, in the sequence entered.
The following table lists the supported enable authentication methods.
| Keyword Description | |
| enable | Uses the enable password for authentication. |
| group | Uses a subset of RADIUS or TACACS+ servers for authentication as defined by the aaa group server radius or aaa group server tacacs+ command. |
| group-name | |
| group radius | Uses the list of all RADIUS hosts for authentication. |
| line Uses the line password for authentication. | |
| none | Uses no authentication. |
6.1.4.3 Configuring Message Banners for AAA Authentication
AAA supports the use of configurable, personalized login and failed-login banners. You can configure message banners that will be displayed when a user logs in to the system to be authenticated using AAA and when, for whatever reason, authentication fails.
6.1.4.4 Configuring a Login Banner
To configure a banner that will be displayed whenever a user logs in (replacing the default message for login), use the following commands in global configuration mode: :
| Command Purpose | |
| aaa authentication bannerdelimiter text-string delimiter | Creates a personalized login banner. |
6.1.4.5 Configuring a Failed-Login Banner
To configure a message that will be displayed whenever a user fails login (replacing the default message for failed login), use the following commands in global configuration mode: :
| Command Purpose | |
| aaa authenticationfail-message delimiter text-string delimiter | Creates a message to be displayed when a user fails login. |
6.1.4.6 Instruction
To create a login banner, you need to configure a delimiting character, which notifies the system that the following text string is to be displayed as the banner, and then the text string itself. The delimiting character is repeated at the end of the text string to signify the end of the banner. The delimiting character can be any single character in the extended ASCII character set, but once defined as the delimiter, that character cannot be used in the text string making up the banner.
6.1.4.7 AAA authentication username-prompt
To change the text displayed when users are prompted to enter a username, use the aaa authentication username-prompt command in global configuration mode. To return to the default username prompt text, use the no form of this command. username:
The aaa authentication username-prompt command does not change any dialog that is supplied by a remote TACACS+ server. Use the following command to configure in global configuration mode:
| Command Purpose | |
| aaa authentication username-prompt text-string | String of text that will be displayed when the user is prompted to enter an username. |
6.1.4.8 AAA authentication password-prompt
To change the text displayed when users are prompted for a password, use the aaa authentication password-prompt command in global configuration mode. To return to the default password prompt text, use the no form of this command.
password:
The aaa authentication password-prompt command does not change any dialog that is supplied by a remote TACACS+ server. Use the following command to configure in global configuration mode:
| Command Purpose | |
| aaa authenticationpassword-prompttext-string | String of text that will be displayed when the user is prompted to enter a password. |
6.1.4.9 Establishing Username Authentication
You can create a username-based authentication system, which is useful in the following situations:
- To provide a TACACS-like username and encrypted password-authentication system for networks that cannot support TACACS
- To provide special-case logins: for example, access list verification, no password verification, autocommand execution at login, and "no escape" situations
To establish username authentication, use the following commands in global configuration mode as needed for your system configuration:
Use the no form of this command to delete a username.
username name {nopassword | passwordpassword | passwordencryption-type encrypted-password}
username name [autocomplete command]
username name [callback-dialstringtelephone-number]
username name [callback-rotary rotary-group-number]
username name [callback-line [tty | aux] line-number [ending-line-number]]
username name [noescape] [nohangup]
username name [privilege/level]
username name [user-maxlinksnumber]
no username name
6.1.4.10 Enabling password
To set a local password to control access to various privilege levels, use the enable password command in global configuration mode. To remove the password requirement, use the no form of this command.
enable password { [encryption-type] encrypted-password} [level level]
no enable password [level /evel]
6.1.5 AAA Authentication Configuration Example
6.1.5.1 RADIUS Authentication Example
This section provides one sample configuration using RADIUS.
The following example shows how to configure the switch to authenticate and authorize using RADIUS:
aaa authentication login radius-login group radius local
aaa authorization network radius-network radius
line vty
login authentication radius-login
The lines in this sample RADIUS authentication and authorization configuration are defined as follows: :
- The aaa authentication login radius-login radius local command configures the router to use RADIUS for authentication at the login prompt. If RADIUS returns an error, the user is authenticated using the local database.
- The aaa authentication ppp radius-ppp radius command configures the software to use PPP authentication using CHAP or PAP if the user has not already logged in. If the EXEC facility has authenticated the user, PPP authentication is not performed.
- The aaa authorization network radius-network radius command command queries RADIUS for network authorization, address assignment, and other access lists.
- The login authentication radius-login command enables the radius-login method list for line 3.
6.1.6 AAA Authorization Configuration Task List
- Configuring EXEC Authorization using AAA
6.1.7 AAA Authorization Configuration Task
To configure AAA authorization, perform the following configuration processes:
(1) If you decide to use a separate security server, configure security protocol parameters, such as RADIUS, TACACS+, or Kerberos.
(2) Define the method lists for authorization by using an AAA authorization command.
(3) Apply the method lists to a particular interface or line, if required.
6.1.7.1 Configuring EXEC Authorization Using AAA
Use the aaa authorization command to enable authorization
Use aaa authorization exec command to run authorization to determine if the user is allowed to run an EXEC shell. This facility might return user profile information such as autocommand information.
Use line configuration command login authorization to apply these lists. Use the following command in global configuration mode:
| Command Purpose | |
| aaa authorization exec {default | list-name}method1 [method2...] | Establishes global authorization list. |
| line [console | vty ] line-number [ending-line-number] | Enters the line configuration mode for the lines to which you want to apply the authorization method list. |
| login authorization {default | list-name} | Applies the authorization list to a line or set of lines(in line configuration mode). |
The keyword list-name is the character string used to name the list of authorization methods.
The keyword method specifies the actual method during authorization process. Method lists enable you to designate one or more security protocols to be used for authorization, thus ensuring a backup system in case the initial method fails. The system uses the first method listed to authorize users for specific network services; if that method fails to respond, the system selects the next method listed in the method list. This process continues until there is successful communication with a listed authorization method, or all methods defined are exhausted. If all specified methods fail to respond, and you still want the system to enter the EXEC shell, you should specify none as the last authorization method in command line.
Use default parameter to establish a default list, and the default list will apply to all interfaces automatically. For example, use the following command to specify radius as the default authorization method for exec: aaa authorization exec default group radius
If no method list is defined, the local authorization service will be unavailable and the authorization is allowed to pass.
The following table lists the currently supported EXEC authorization mode:
| Keyword Description | |
| group WORD | Uses a named server group for authorization. |
| group radius Uses radius authorization. | |
| local | Uses the local database for authorization. |
| if-authenticated | Allows the user to access the requested function if the user is authenticated. |
| none No authorization is performed. | |
6.1.8 AAA Authorization Example
EXEC local authorization example
aaa authentication login default local
aaa authorization exec default local
!
username exec1 password 0 abc privilege 15
username exec2 password 0 abc privilege 10
username exec3 nopassword
username exec4 password 0 abc user-maxlinks 10
username exec5 password 0 abc autocommand telnet 172.16.20.1
!
The lines in this sample RADIUS authorization configuration are defined as follows: :
- The aaa authentication login default local command defines the default method list of login authentication. This method list applies to all login authentication servers automatically.
- The aaa authorization exec default local command defines default method list of exec authorization. The method list automatically applies to all users that need to enter exec shell.
- Username is exec1, login password is abc, EXEC privileged level is 15(the highest level), that is, when user exec1 whose privileged level is 15 logs in exec shell, all commands can be checked and performed.
- Username is exec2, login password is abc, EXEC privileged level is 10, that is, when user exec2 whose privileged level is 10 logs in EXEC shell, commands with privileged level less than 10 can be checked and performed.
- Username is exec3, no password is needed for login.
- Username is exec4, login password is abc, the maximum links of the user is 10.
- Username is exec5, login password is abc, user performs telnet 172.16.20.1 immediately when logging in exec shell.
6.1.9 AAA Accounting Configuration Task List
- Configuring Connection Accounting using AAA
- Configuring Network Accounting using AAA
6.1.10 AA Accounting Configuration Task
To configure AAA accounting, perform the following configuration processes:
(1) If you decide to use a separate security server, configure security protocol parameters, such as RADIUS, TACACS+, or Kerberos.
(2) Define the method lists for accounting by using an AAA accounting command.
(3) Apply the method lists to a particular interface or line, if required.
6.1.10.1 Configuring Accounting Connection Using AAA
Use the aaa accounting command to enable AAA accounting.
To create a method list to provide accounting information about all outbound connections made from the network access server, use the aaa accounting connection command.
| Command Purpose | |
| aaa accounting connection {default | list-name} {start-stop | stop-only | none} group groupname | Establishes global accounting list. |
The keyword list-name is used to name any character string of the establishing list. The keyword method specifies the actual method adopted during accounting process.
The following table lists currently supported connection accounting methods:
| Keyword Description | |
| group WORD | Enables named server group for accounting. |
| group radius Enables radius accounting. | |
| none | Disables accounting services for the specified line or interface. |
| stop-only | Sends a "stop" record accounting notice at the end of the requested user process. |
| start-stop | RADIUS or TACACS+ sends a "start" accounting notice at the beginning of the requested process and a "stop" accounting notice at the end of the process. |
6.1.10.2 Configuring Network Accounting Using AAA
Use the aaa accounting command to enable AAA accounting.
To create a method list to provide accounting information for SLIP, PPP, NCPs, and ARAP sessions, use the aaa accounting network command in global configuration mode.
| Command Purpose | |
| aaa accounting network {default | list-name} {start-stop | stop-only | none} group groupname | Enables global accounting list. |
The keyword list-name is used to name any character string of the establishing list. The keyword method specifies the actual method adopted during accounting process.
The following table lists currently supported network accounting methods:
| Keyword Description | |
| group WORD | Enables named server group for accounting. |
| group radius Enables radius accounting. | |
| none | Disables accounting services for the specified line or interface. |
| stop-only | Sends a "stop" record accounting notice at the end of the requested user process. |
| start-stop | RADIUS or TACACS+ sends a "start" accounting notice at the beginning of the requested process and a "stop" accounting notice at the end of the process. |
6.1.10.3 AAA Accounting Update
To enable periodic interim accounting records to be sent to the accounting server, use the aaa accounting update command in global configuration mode. To disable interim accounting updates, use the no form of this command.
| Command Purpose | |
| aaa accounting update [newinfo][periodicnumber] | Enables AAA accounting update. |
If the newinfo keyword is used, interim accounting records will be sent to the accounting server every time there is new accounting information to report. An example of this would be when IP Control Protocol (IPCP) completes IP address negotiation with the remote peer. The interim accounting record will include the negotiated IP address used by the remote peer.
When used with the periodic keyword, interim accounting records are sent periodically as defined by the argument number. The interim accounting record contains all of the accounting information recorded for that user up to the time the accounting record is sent.
When using both the newinfo and periodic keywords, interim accounting records are sent to the accounting server every time there is new accounting information to report, and accounting records are sent to the accounting server periodically as defined by the argument number. For example, if you configure the aaa accounting update newinfo periodic number command, all users currently logged in will continue to generate periodic interim accounting records while new users will generate accounting records based on the newinfo algorithm.
6.1.10.4 AAA accounting suppress null-username
To prevent the AAA system from sending accounting records for users whose username string is NULL, use the aaa accounting suppress null-username command in global configuration mode. To allow sending records for users with a NULL username, use the no form of this command.
- aaa accounting suppress null-username
6.2 Configuring RADIUS
This chapter describes the Remote Authentication Dial-In User Service (RADIUS) security system, defines its operation, and identifies appropriate and inappropriate network environments for using RADIUS technology. The "RADIUS Configuration Task List" section describes how to configure RADIUS with the authentication, authorization, and accounting (AAA) command set.
6.2.1 Introduction
6.2.1.1 RADIUS Introduction
RADIUS is a distributed client/server system that secures networks against unauthorized access. In the implementation, RADIUS clients run on switches and send authentication requests to a central RADIUS server that contains all user authentication and network service access information.
RADIUS has been implemented in a variety of network environments that require high levels of security while
maintaining network access for remote users.
Use RADIUS in the following network environments that require access security: :
● Networks with multiple-vendor access servers, each supporting RADIUS. For example, access servers from several vendors use a single RADIUS server-based security database. In an IP-based network with multiple vendors' access servers, dial-in users are authenticated through a RADIUS server that has been customized to work with the Kerberos security system.
● Networks in which a user must only access a single service. Using RADIUS, you can control user access to a single host, to a single utility such as Telnet, or to a single protocol such as Point-to-Point Protocol (PPP). For example, when a user logs in, RADIUS identifies this user as having authorization to run PPP using IP address 10.2.3.4 and the defined access list is started.
● Networks that require resource accounting. You can use RADIUS accounting independent of RADIUS authentication or authorization. The RADIUS accounting functions allow data to be sent at the start and end of services, indicating the amount of resources (such as time, packets, bytes, and so on) used during the session. An Internet service provider (ISP) might use a freeware-based version of RADIUS access control and accounting software to meet special security and billing needs.
RADIUS is not suitable in the following network security situations:
- Multiprotocol access environments. RADIUS does not support the following protocols:
- AppleTalk Remote Access (ARA)
● NetBIOS Frame Control Protocol (NBFCP)
● NetWare Asynchronous Services Interface (NASI)
• X.25 PAD connections
- Switch-to-switch situations. RADIUS does not provide two-way authentication.
● Networks using a variety of services. RADIUS generally binds a user to one service model.
6.2.1.2 RADIUS Operation
When a user attempts to log in and authenticate to an access server using RADIUS, the following steps occur:
(1) The user is prompted for and enters a username and password.
(2) The username and encrypted password are sent over the network to theRADIUS server.
(3) The user receives one of the following responses from the RADIUS server:
a. ACCEPT—the user is authenticated.
b. REJECT—the user is not authenticated and is prompted to reenter the username and password, or access is denied
c. CHALLENGE—a challenge is issued by the RADIUS server. The challenge collects additional data from the user.
d. CHANGE PASSWORD—a request is issued by the RADIUS server, asking the user to select a new password.
The ACCEPT or REJECT response is bundled with additional data that is used for EXEC or network authorization. You must first complete RADIUS authentication before using RADIUS authorization. The additional data included with the ACCEPT or REJECT packets consists of the following:
Services that the user can access, including Telnet, rlogin, or local-area transport (LAT) connections, and PPP, Serial Line Internet Protocol (SLIP), or EXEC services.
Connection parameters, include the host or client IP address, access list, and user timeouts.
6.2.2 RADIUS Configuration Task List
To configure RADIUS on your switch or access server, you must perform the following tasks:
- Use the aaa authentication global configuration command to define method lists for RADIUS authentication. For more information about using the aaa authentication command, refer to the "Configuring Authentication" chapter.
- Use line and interface commands to enable the defined method lists to be used. For more information, refer to the "Configuring Authentication" chapter.
● The following configuration tasks are optional:
- You may use the aaa authorization global command to authorize specific user functions. For more information about using the aaa authorization command, refer to the chapter "Configuring Authorization."
- You may use the aaa accounting command to enable accounting for RADIUS connections. For more information about using the aaa accounting command, refer to the chapter "Configuring Accounting."
6.2.3 RADIUS Configuration Task List
- Configuring Switch to RADIUS Server Communication
- Configuring Switch to Use Vendor-Specific RADIUS Attributes
- Specifying RADIUS Authentication
- Specifying RADIUS Authorization
- Specifying RADIUS Accounting
6.2.4 RADIUS Configuration Task
6.2.4.1 Configuring Switch to RADIUS Server Communication
The RADIUS host is normally a multiuser system running RADIUS server software from Livingston, Merit, Microsoft, or another software provider.
A RADIUS server and a Cisco router use a shared secret text string to encrypt passwords and exchange responses.
To configure RADIUS to use the AAA security commands, you must specify the host running the RADIUS server daemon and a secret text (key) string that it shares with the router.
To configure per-server RADIUS server communication, use the following command in global configuration mode:
| Command Purpose | |
| radius-server hostip-address[auth-portport-number][acct-portportnumber] | Specifies the IP address or host name of the remote RADIUS server host and assign authentication and accounting destination port numbers. |
| radius-server keystring | Specifies the shared secret text string used between the router and a RADIUS server. |
To configure global communication settings between the router and a RADIUS server, use the following radius-server commands in global configuration mode:
| Command Purpose | |
| radius-server retransmitretries | Specifies how many times the switch transmits each RADIUS request to the server before giving up (the default is 2). |
| radius-server timeout seconds | Specifies for how many seconds a switch waits for a reply to a RADIUS request before retransmitting the request. |
| radius-server deadtime minutes | Specifies for how many minutes a RADIUS server that is not responding to authentication requests is passed over by requests for RADIUS authentication. |
6.2.4.2 Configuring Switch to Use Vendor-Specific RADIUS Attributes
The Internet Engineering Task Force (IETF) draft standard specifies a method for communicating vendor-specific information between the network access server and the RADIUS server by using the vendor-specific attribute (attribute 26).
Vendor-specific attributes (VSAs) allow vendors to support their own extended attributes not suitable for general use.
For more information about vendor-IDs and VSAs, refer to RFC 2138, Remote Authentication Dial-In User Service (RADIUS). To configure the network access server to recognize and use VSAs, use the following command in global configuration mode:
| Command Purpose | |
| radius-servervsasend [authentication] | Enables the network access server to recognize and use VSAs as defined by RADIUS IETF attribute 26. |
6.2.4.3 Specifying RADIUS Authentication
After you have identified the RADIUS server and defined the RADIUS authentication key, you must define method lists for RADIUS authentication. Because RADIUS authentication is facilitated through AAA, you must enter the aaa authentication command, specifying RADIUS as the authentication method. For more information, refer to the chapter "Configuring Authentication."
6.2.4.4 Specifying RADIUS Authorization
AAA authorization lets you set parameters that restrict a user's access to the network. Authorization using RADIUS provides one method for remote access control, including one-time authorization or authorization for each service, per-user account list and profile, user group support, and support of IP, IPX, ARA, and Telnet. Because RADIUS authorization is facilitated through AAA, you must issue the aaa authorization command, specifying RADIUS as the authorization method. For more information, refer to the chapter "Configuring Authorization."
6.2.4.5 Specifying RADIUS Accounting
The AAA accounting feature enables you to track the services users are accessing as well as the amount of network resources they are consuming. Because RADIUS accounting is facilitated through AAA, you must issue the aaa accounting command, specifying RADIUS as the accounting method. For more information, refer to the chapter "Configuring Accounting."
6.2.5 RADIUS Configuration Examples
6.2.5.1 RADIUS Authentication and Authorization Example
The following example shows how to configure the router to authenticate and authorize using RADIUS:
aaa authentication login use-radius group radius local
The lines in this sample RADIUS authentication and authorization configuration are defined as follows: : aaa authentication login use-radius radius local configures the router to use RADIUS for authentication at the login prompt. If RADIUS returns an error, the user is authenticated using the local database. In this example, use-radius is the name of the method list, which specifies RADIUS and then local authentication.
RADIUS Authentication, Authorization, and Accounting Example
The following example shows a general configuration using RADIUS with the AAA command set: radius-server host 1.2.3.4
radius-server key myRaDiUSpassWoRd
username root password AlongPassword
aaa authentication login admins radius local
line vty 1 16
login authentication admins
The lines in this example RADIUS authentication, authorization, and accounting configuration are defined as follows:
radius-server host command defines the IP address of the RADIUS server host. ;
radius-server key command defines the shared secret text string between the network access server and the RADIUS server host.
aaa authentication login admins group radius local command defines the authentication method list "dialins," which specifies that RADIUS authentication and then (if the RADIUS server does not respond) local authentication will be used on serial lines using PPP. ;
login authentication admins command applies the "admins" method list for login authentication.
6.2.5.2 RADIUS Application Example
The following example shows how to define the general configuration through the AAA command set: radius-server host 1.2.3.4
radius-server key myRaDiUSpassWoRd
username root password AlongPassword
aaa authentication login admins radius local
line vty 1 16
login authentication admins
In the example above, each command line has its own meaning. See the following content:
The command radius-server host defines the IP address of the RADIUS server.
The command radius-server key defines the shared pin between the network access server and the RADIUS server.
The command aaa authentication login admins radius local defines the authentication method list admins, which first specifies RADIUS as the authentication method and then uses the local authentication if the
RADIUS server does not respond.
The command login authentication admins specifies the method list admins as the login authentication method.
6.3 Web Authentication Configuration
The section describes the concept of Web authentication and configuration and usage of the Web authentication.
6.3.1 Overview
6.3.1.1 Web Authentication
The Web authentication of the switch is a connection control mode as PPPoE and 802.1x. When you use the Web authentication, the login and logout operations can be successfully performed through the interaction of the browser and the builtin portal server of the switch. During the operations of login and logout, no other client software need be installed.
1. Device role
The roles that the network devices take during the Web authentication are shown in Figure 6-2:
- Client: It is ausercomputer that accesses network through the switch. The user computer need be configured the network browser, the function of DHCP client and the function to originate DNS query.
● DHCP server: It is to distribute the IP address for users.
● AAA server: It is to save user right information and to charge users for their network access. - Switch: It is a switch having Web authentication. It is to control the access right of users and works as an agent between users and AAA server.
flowchart
graph TD
A["client"] --> C["switch"]
B["client"] --> C["switch"]
D["DHCP server"] --> C["switch"]
E["AAA server (RAD US)"] --> C["switch"]
Figure 6-2Web authentication network
2. Authentication flow
According to different configuration strategies, the Web authentication flow of the switch may relate to protocols such as DHCP and DNS. Its typical flow is shown in Figure 3-2. The Web authentication flow generally contains the following steps:
(1) The DHCP server sends a DHCP confirmation request to a user through the switch after the user originates the process of DHCP address distribution. The switch then identifies and records the user.
(2) The user accesses any Website through the browser (Write down the domain name, not the IP address, in the host part of the url column in the browser), which activates the DNS request of the user computer.
(3) The DNS server returns the user a request response. The switch captures the request response message and changes the resolved address to the address of the built-in portal server in the switch.
(4) The DHCP confirmation process continues after the browser captures DNS resolution. The switch returns the corresponding authentication page according to different authentication methods after the switch receives the request.
(5) The user submits the authentication request; the switch authenticates the user through the AAA server after the switch receives information submitted by the user; if the authentication succeeds, the AAA server will be notified to start charging; the switch gives the user the network access right and returns the user a page that the authentication is successful; meanwhile, the switch also returns a keep alive page, which periodically sends the user online notification to the switch.
(6) The user sends the logout request to the switch through the browser. The switch then notifies the AAA server to stop charging, and withdraws the network access right from the user.
(7) In the period between successful user authentication and logout, the switch periodically detects the user online notification. If the notification is not received in the preset time, the switch considers that the user abnormally logs off, notifies the AAA server to stop charging and withdraws the network access right from the user.
The above steps may vary a little with configuration strategies and user's operations. For example, if user directly accesses the portal server of the switch before the authentication is approved, DNS-related processes will not be enabled.
flowchart
graph TD
A["client"] -->|DHCP ACK| B["switch"]
B -->|DNS REQUERY| C["drop_ser.ver"]
C -->|DNS RESPONSE| D["DNS_ser.ver.AAA_ser.ver"]
D -->|http request| E["ht t pr equest"]
E -->|http request( ask user to login) | F["ht t pr equest( login)"]
F -->|aut hent i cat ion r equest| G["aut hent i cat ion r esul t"]
G -->|start t account i ng r equest| H["start t account i ng r esul t"]
H -->|start t account i ng r esul t| I["start t account i ng r esul t"]
I -->|aut hent i cat ion r esul t| J["aut hent i cat ion r esul t"]
J -->|http request( keepal i ve) | K["http request( keepal i ve response)"]
K -->|http request( logout ) stop accounting r equest| L["http request( logout)"]
L -->|http request( logout )| M["http request( logout)"]
Figure 6-3 web authentication flow
6.3.1.2 Planning Web Authentication
1. Planning the authentication mode
Two authentication modes are provided to control user's access:
Username/password authentication mode: In this mode, the switch identifies the user through the username and password, and notifies the AAA server to start charging according to username; user needs to enter the username and password through the browser.
VLAN ID authentication mode: In this mode, the switch identifies the user through the VLAN ID the user belongs to, and notifies the AAA server to start charging according to VLAN ID; user only requires to confirm corresponding operations on the Web page before accessing the network.
Different operation strategies adopt different authentication modes. The supported maximum number of users that simultaneously access the network varies with the authentication mode. For the username/password authentication mode, the switch supports simultaneously accessed users as many as its performance permits. For the VLAN ID authentication mode, the maximum number of simultaneously accessed users equals the number of VLAN that the switch supports.
2. Planning network topology
The switch takes the routing interface as a unit to set the authentication attribute. if the web authentication function is enabled on a routing interface, network accesses through the routing interface are all controlled by the web authentication. the dhcp server, dns server or aaa server should connect the switch through the interface with web authentication function disabled. figure 6-4 shows the relative typical network topology.
flowchart
graph TD
A["DNS server"] --> B["I 2swi t ch"]
C["DHP server"] --> B
D["AAA server"] --> B
E["user"] --> F["I 2swi t ch"]
G["user"] --> H["I 3swi t ch"]
I["user"] --> J["I 2swi t ch"]
K["user"] --> L["I 3swi t ch"]
M["user"] --> N["I 2swi t ch"]
O["i nt er net"] --> P["I 3swi t ch"]
B --> P
F --> P
H --> P
J --> P
L --> P
Figure 6-4 Typical network topology
6.3.2 Configuring Web Authentication
6.3.2.1 Global Configuration
1. Configuring the address of the portal server
Run the following command in global configuration mode to configure the address of the portal server:
| Run... To... | |
| web-auth portal-server A.B.C.D | Configure the IP address of the portal server. |
2. Configuring authentication duration
The parameter authtime determines the maximum time of user's authentication. If the authentication is not approved within the maximum time, the switch terminates the authentication procedure.
Run the following command in global configuration mode to configure the authentication duration (Unit: second):
| Run... To... | |
| web-auth authtime <60-65535> | Configure the authentication duration. |
3. Configuring the transmission period of the online notification
Through the online notification sent by the browser, the switch checks whether the user is online.
Run the following command in global configuration mode to configure the transmission period (unit: second):
| Run... To... | |
| web-auth keep-alive<60-65535> | Configure the transmission period for the online notification. |
4. Configuring the duration to detect the abnormal logout
When the switch does not receive the user online notification from the browser in the set duration, the switch considers that user logs out abnormally.
Run the following command in global configuration mode to configure the duration to detect the abnormal logout:
| Run... To... | |
| web-auth holdtime <60-65535> | Configure the duration to detect user's abnormal logout. |
5. Configuring password for the VLAN ID authentication
When the authentication mode is set to VLAN ID, the switch takes vlan n as the user name, n representing the corresponding VLAN serial number. All user names use the same password.
Run the following command in global configuration mode to configure the password for the VLAN ID authentication:
| Run... To... | |
| web-auth vlan-password | Configure the password for the VLAN ID authentication. |
6.3.2.2 Interface Configuration
1. Configuring authentication mode
The switch provides two authentication modes: username/password and VLAN ID.
Run the following command in interface configuration mode to configure the authentication mode:
| Run... To... | |
| web-auth mode user | vlan-id | Configure the authentication mode. |
2. Configuring authentication method list
Different authentication method lists can be applied on each interface. By default, the authentication method list named default is applied on each interface.
Run the following command in interface configuration mode to configure the authentication method list:
| Run... To... | |
| web-auth authentication WORD | Configure the authentication method list. |
3. Configuring the accounting method list
Different accounting method lists can be applied on each interface. By default, the accounting method list named default is applied on each interface.
Run the following command in interface configuration mode to configure the accounting method list:
| Run... To... | |
| web-auth accounting WORD | Configure the accounting method list. |
6.3.2.3 Enabling Web Authentication
If global configuration and interface configuration satisfy the requirements, you can enable the Web authentication on the designated routing switch.
Run the following command in interface configuration mode to enable the Web authentication:
| Run... To... | |
| web-auth enable | Enable the Web authentication. |
6.3.3 Monitoring and Maintaining Web Authentication
6.3.3.1 Checking the Global Configuration
Run the following command in privileged mode to check the global configuration:
| Run... To... | |
| show web-auth | Check the global configuration. |
6.3.3.2 Checking Interface Configuration
Run the following command in interface configuration mode to check the interface configuration:
| Run... To... | |
| show web-auth interface [vlan | SuperVlan] | Check the interface configuration. |
6.3.3.3 Checking User State
Run the following command in privileged mode to check the user state:
| Run... To... | |
| show web-auth user | Check the user state. |
6.3.3.4 Mandatorily Kicking Out Users
Run the following command in global configuration mode to mandatorily kick out a user.
| Run... To... | |
| web-auth kick-out user-IP | Mandatorily kick out a user. |
6.3.4 Web Authentication Configuration Example
Network topology
See Figure 6-5:
flowchart
graph TD
A["user 1"] --> B["F0/3"]
C["DNS server"] --> D["DHP server (192.168.20.1)"]
E["AAA server"] --> F["192.168.20.2"]
G["user 2"] --> H["I2switch"]
I["user 3"] --> J["I2switch"]
K["Internet"] --> L["F0/4"]
M["I3switch"] --> N["F0/2"]
O["i nter net"] --> P["F0/4"]
Figure 6-5 Network topology
Global configuration
aaa authentication login auth-weba radius
aaa accounting network acct-weba start-stop radius
!
radius-server host 192.168.20.2 auth-port 1812 acct-port 1813
radius-server key 405.10
!
ip dhcp enable
ip http server
!
vlan 1-4
!
web-auth portal-server 192.168.20.41
web-auth holdtime 3600
web-auth authtime 600
web-auth keep-alive 180
Configuration of the layer-2 interface
interface FastEthernet0/1
switchport pvid 1
!
interface FastEthernet0/2
switchport pvid 2
!
interface FastEthernet0/3
switchport pvid 3
!
interface FastEthernet0/4
switchport pvid 4
Configuration of the routing interface
interface VLAN1
no ip directed-broadcast
ip helper-address 192.168.20.1
web-auth accounting acct- weba
web-auth authentication auth- weba
web-auth mode vlan-id
web-auth enable
!
interface VLAN2
ip address 192.168.20.41 255.255.255.0
no ip directed-broadcast
!
interface VLAN3
no ip directed-broadcast
ip helper-address 192.168.20.1
web-auth accounting acct- weba
web-auth authentication auth- weba
web-auth mode user
web-auth enable
!
interface VLAN4
no ip directed-broadcast
!
7. Web Configuration
7.1 HTTP Switch Configuration
7.1.1 HTTP Configuration
Switch configuration can be conducted not only through command lines and SNMP but also through Web browser. The switches support the HTTP configuration, the abnormal packet timeout configuration, and so on.
7.1.1.1 Choosing the Prompt Language
Up to now, switches support two languages, that is, English and Chinese, and the two languages can be switched over through the following command.
| Command Purpose | |
| ip http language {chinese | english} | Sets the prompt language of Web configuration to Chinese or English. |
7.1.1.2 Setting the HTTP Port
Generally, the HTTP port is port 80 by default, and users can access a switch by entering the IP address directly; however, switches also support users to change the service port and after the service port is changed you have to use the IP address and the changed port to access switches. For example, if you set the IP address and the service port to 192.168.1.3 and 1234 respectively, the HTTP access address should be changed to http://192.168.1.3:1234. You'd better not use other common protocols' ports so that access collision should not happen. Because the ports used by a lot of protocols are hard to remember, you'd better use port IDs following port 1024.
| Command Purpose | |
| ip http port { portNumber } | Sets the HTTP port. |
7.1.1.3 Enabling the HTTP Service
Switches support to control the HTTP access. Only when the HTTP service is enabled can HTTP exchange happen between switch and PC and, when the HTTP service is closed, HTTP exchange stops.
| Command Purpose | |
| ip http server Enables the HTTP service. | |
| ip http {timeout} | Configures the timeout time of HTTP abnormal packets. |
7.1.1.4 Setting the HTTP Access Mode
You can access a switch through two access modes: HTTP access and HTTPS access, and you can use the following command to set the access mode to HTTP.
| Command Purpose | |
| ip http http-access enable | Sets the HTTP access mode. |
7.1.1.5 Setting the Maximum Number of VLAN Entries on Web Page
A switch supports at most 4094 VLANs and in most cases Web only displays parts of VLANs, that is, those VLANs users want to see. You can use the following command to set the maximum number of VLANs. The default maximum number of VLANs is 100.
| Command Purpose | |
| ip http web max-vlan {max-vlan} | Sets the maximum number of VLAN entries displayed in a web page. |
7.1.1.6 Setting the Maximum Number of Multicast Entries Displayed on a Web Page
A switch supports at most 100 multicast entries. You can run the following command to set the maximum number of multicast entries and Web then shows these multicast entries. The default maximum number of multicast entries is 15.
| Command Purpose | |
| ip http web igmp-groups{ igmp-groups } | Sets the maximum number of multicast entries displayed in a web page. |
7.1.2 HTTPS Configuration
In order to improve the security of communications, switches support not only the HTTP protocol but also the HTTPS protocol. HTTPS is a security-purposed HTTP channel and it is added to the SSL layer under HTTP.
7.1.2.1 Setting the HTTP Access Mode
You can run the following command to set the access mode to HTTPS.
| Command Purpose | |
| ip http ssl-access enable | Sets the HTTPS access mode. |
7.1.2.2 It is used to set the HTTPS port.
As the HTTP port, HTTPS has its default service port, port 443, and you also can run the following command to change its service port. It is recommended to use those ports following port 1024 so as to avoid collision with other protocols' ports.
| Parameter Remarks | |
| ip http secure-port {portNumber} | Sets the HTTPS port. |
7.2 Configuration Preparation
7.2.1 Accessing the Switch through HTTP
When accessing the switch through Web, please make sure that the applied browser complies with the following requirements:
- HTML of version 4.0
- HTTP of version 1.1
- JavaScript™ of version 1.5
What's more, please ensure that the main program file, running on a switch, supports Web access and your computer has already connected the network in which the switch is located.
7.2.1.1 Initially Accessing the Switch
When the switch is initially used, you can use the Web access without any extra settings:
- Modify the IP address of the network adapter and subnet mask of your computer to 192.168.1.x and 255.255.255.0 respectively.
- Open the Web browser and enter 192.168.1.1 in the address bar. It is noted that 192.168.1.1 is the default management address of the switch.
- If the Internet Explorer browser is used, you can see the dialog box in figure 1. Both the original username and the password are "admin", which is capital sensitive.
4.
Figure 1: ID checkup of WEB login
- After successful authentication, the systematic information about the switch will appear on the IE browser.
7.2.1.2 Upgrading to the Web-Supported Version
If your switch is upgraded to the Web-supported version during its operation and the switch has already stored its configuration files, the Web visit cannot be directly applied on the switch. Perform the following steps one by one to enable the Web visit on the switch:
- Connect the console port of the switch with the accessory cable, or telnet to the management address of the switch through the computer.
- Enter the global configuration mode of the switch through the command line, the DOS prompt of which is similar to "Switch config#".
- If the management address of the switch is not configured, please create the VLAN interface and configure the IP address.
- Enter the ip http server command in global configuration mode and start the Web service.
- Run username to set the username and password of the switch. For how to use this command, refer to the "Security Configuration" section in the user manual.
- After the above-mentioned steps are performed, you can enter the address of the switch in the Web browser to access the switch.
- Enter write to store the current configuration to the configuration file.
7.2.2 Accessing a Switch through Secure Links
The data between the WEB browser and the switch will not be encrypted if you access a switch through common HTTP. To encrypt these data, you can use the secure links, which are based on the secure sockets layer, to access the switch.
To do this, you should follow the following steps:
- Connect the console port of the switch with the accessory cable, or telnet to the management address of the switch through the computer.
- Enter the global configuration mode of the switch through the command line, the DOS prompt of which is similar to "Switch_config#".
-
If the management address of the switch is not configured, please create the VLAN interface and configure the IP address.
-
Enter the ip http server command in global configuration mode and start the Web service.
-
Run username to set the username and password of the switch. For how to use this command, refer to the "Security Configuration" section in the user manual.
-
- Run ip http ssl-access enable to enable the secure link access of the switch.
-
Run no ip http http-access enable to forbid to access the switch through insecure links.
-
Enter write to store the current configuration to the configuration file.
-
Open the WEB browser on the PC that the switch connects, enter https://192.168.1.1 on the address bar (192.168.1.1 stands for the management IP address of the OLT) and then press the Enter key. Then the switch can be accessed through the secure links.
7.2.3 Introduction of Web Interface
The Web homepage appears after login, as shown in figure 2:
Figure 2: Web homepage
The whole homepage consists of the top control bar, the navigation bar, the configuration area and the bottom control bar.
7.2.3.1 Top Control Bar
Save All | Logout
Figure 3: Top control bar
Save All Write the current settings to the configuration file of the device. It is equivalent to the execution of the write command. The configuration that is made through Web will not be promptly written to the configuration file after validation. If you click "Save All", the unsaved configuration will be lost after rebooting.
Logout Exit from the current login state.
After you click "logout", you have to enter the username and the password again if you want to continue the Web function.
After you configure the device, the result of the previous step will appear on the left side of the top control bar. If error occurs, please check your configuration and retry it later.
7.2.3.2 Navigation Bar
Device Status
Device Info
Interface State
Interface Flow
GPON Optical State
Mac Address Table
ONU Interface State
Reject ONU
Information
ONU Optic Module
Information
Log Query
Basic Config
GPON Interface
Config
ONU Config Profile
ONU Interface Config
Advanced Config
L3 Config
Remote Monitor
System Mgr
Figure 4 Navigation bar
The contents in the navigation bar are shown in a form of list and are classified according to types. By default, the list is located at "Runtime Info". If a certain item need be configured, please click the group name and then the sub-item. For example, to browse the flux of the current port, you have to click "Interface State" and then "Interface Flow".
The limited user can only browse the state of the device and cannot modify the configuration of the device. If you log on to the Web with limited user's permissions, only "Interface State" will appear.
7.2.3.3 Configuration Area
| Device Type | XGS-6350-12X8TR |
| BIOS Version | 0.4.3 |
| Firmware Version | 2.2.0B Build 48290 |
| Serial No. | 20014013899 |
| MAC Address | A8F7.E003.0001 |
| IP Address | 192.168.0.254 |
| Current Time | 1970-1-8 21:3:10 |
| Uptime | 7 Day -21 Hour -3 Minute -10 Second |
| CPU Usage | 2% |
| Memory Usage | 16% |
Figure 5 Configuration Area
The configuration display area shows the state and configuration of the device. The contents of this area can be modified by the clicking of the items in the navigation bar.
7.2.3.4 Configuration Area
The configuration area is to show the content that is selected in the navigation area. The configuration area always contains one or more buttons, and their functions are listed in the following table:
7.3 Basic Configuration
Device Status
Basic Config
Hostname
Clock Mgr
GPON Interface
Config
ONU Config Profile
ONU Interface Config
Advanced Config
L3 Config
Remote Monitor
System Mgr
Figure 1 A list of basic configuration
7.3.1 Hostname Configuration
If you click Basic Config -> Hostname Config in the navigation bar, the Hostname Configuration page appears, as shown in figure 2.
Figure 2 Hostname configuration
The hostname will be displayed in the login dialog box.
The default name of the device is "Switch". You can enter the new hostname in the text box shown in figure 8 and then click "Apply".
7.3.2 Time Management
If you click System Manage -> Time Manage, the Time Setting page appears.
Figure 3 Clock management
To refresh the clock of the displayed device, click "Refresh".
In the "Select Time-Zone" dropdown box select the time zone where the device is located. When you select "Set Time Manually", you can set the time of the device manually. When you select "Network Time Synchronization", you can designate 3 SNTP servers for the device and set the interval of time synchronization.
7.4 GPON Interface Config
Figure 1: GPON Interface Config list
7.4.1 GPON Global Config
On the left navigation bar, click "GPON Interface Config" -> "GPON Global Config", and the following interface appears.
Figure 2: Device Name Configuration
On this page, you can configure ONU authentication method to serial number, password and authentication. You can broadcast GEM Port and the value ranges from 385 to 4094. Click "Apply" and the operation will take effect on the OLT. Click "Reset" to return to the default setting.
7.4.2 ONU Bind Relationship Config
On the left navigation bar, click "GPON Interface Config" -> "ONU Bind Relationship Config" and the following page appears.
Figure 3: Interface ONU Bind Relationship Configuration
Click "Detail" to show the concrete ONU binding relationship of the concrete interface. Select an ONU and click "Delete" to remove the binding or click "Go Back" to return to the default setting.
Click "New" on the top left of the interface to create a new "Interface ONU Bind Relationship Config" and the corresponding interface will pop up:
Figure 4: Interface ONU Bind Relationship List GPON
You can "Reset" the binding relationship and fill in the password and ONU ID. Click "Apply" to apply the configuration; click "Reset" to reset the information; click "Go Back" after you complete the configuration.
Figure 5: Interface ONU Bind Relationship Config GPON
7.4.3 ONU Discover Mode
On the left navigation bar, click "GPON Interface Config" -> "ONU Discover Mode", and the following page appears.
Figure 6: ONU Discover Mode Interface Config
You can designate the discover mode for each PON port: Auto or Disable. Click "Apply" to save the configuration.
7.4.4 ONU Authentication
On the left navigation bar, click "GPON Interface Config" -> "ONU Authentication", and the following page appears.
Figure 7: ONU Authentication Interface Config
You can on OLT to enable the ONU detection mechanism at MPCP registration. After the ONU MAC detection mechanism is enabled, ONUs without static binding settings cannot be registered to OLT. One LLID port maps to only one ONU's MAC address.
By default, the ONU SN detection mechanism at MPCP registration is disabled; in this case all ONUs can be registered freely.
Once ONU passes through the authentication, or it is set not to base on the authentication and the registration is successful, the SN of ONU and the static binding entries of the ONU number will be automatically added; when this settings is saved and the system is restarted, this ONU will not be re-authenticated.
7.5 ONU Config Profile
Figure 1: ONU Config Profile list
7.5.1 ONU T-Cont Config
On the left navigation bar, click "ONU Config Profile" -> "ONU T-Cont Config", and the following page appears.
Figure 2 ONU T-Cont Profile List
On ONU T-Cont Profile List, select a to-be-deleted item, click "Delete" to delete the corresponding ONU profile. The default profile cannot be deleted.
Click "New" or "Edit" to edit the profile on the following page. On the page, you can edit
Profile Name or select Tcont type (1-5), peak bandwidth, committed bandwidth and assured bandwidth (one or multiple). After completing the configuration, click "Apply" to save the configuration.
Figure 3: ONU T-Cont Profile Config
7.5.2 ONU Rate Limit Config
On the left navigation bar, click "ONU Config Profile" -> "ONU Rate Limit Config", and the following page appears.
| Help |
| #Cannot delete the default profile. |
Figure 4: ONU T-Cont Profile List
On ONU T-Cont Profile List, select a to-be-deleted item, click "Delete" to delete the corresponding ONU profile. The default profile cannot be deleted.
Click "New" or "Edit" to edit the profile on the following page. On the page, you can edit Profile Name or set Peak Bandwidth and Committed Bandwidth. After the configuration is finished, click "Apply" to save the configuration.
Figure 5: ONU T-Cont Profile Config
7.5.3 ONU Virtual Port Config
On the left navigation bar, click "ONU Config Profile" -> "ONU Rate Virtual Port Config", and the following page appears.
Figure 6: ONU Virtual Port Profile List
On ONU Virtual Profile List, select a to-be-deleted item, click "Delete" to delete the corresponding ONU profile. The default profile cannot be deleted.
Click "New" or "Edit" to edit the profile on the following page. On the page, you can edit
Profile Name, Downstream Encryption, Upstream Queue, Upstream Rate Limit Profile and Downstream Queue. After the configuration is finished, click "Apply" to save the configuration.
Figure 7: ONU Virtual Port Profile Config
7.5.4 T-Cont Virtual Port Bind Config
On the left navigation bar, click "ONU Config Profile" -> "T-Cont Virtual Port Bind Config", and the following page appears.
Figure 8: ONU T-Cont Virtual Port Bind Profile List
Figure 9: ONU T-Cont Virtual Port Bind Profile tvbind-default
On ONU Virtual Profile List, select a to-be-deleted item, click "Delete" to delete the corresponding ONU profile. The default profile cannot be deleted.
Click "New" or "Edit" to edit the profile on the following page. On the page, you can edit Virtual Port ID, Virtual Port Profile, T-Cont ID and T-Cont Profile. After the configuration is finished, click "Apply" to save the configuration.
Figure 10: ONU T-Cont Virtual Port Bind Profile tvbind-default
7.5.5 ONU VLAN Config
On the left navigation bar, click "ONU Config Profile" -> "ONU VLAN Config", and the following page appears.
Figure 11: ONU VLAN Profile List
On ONU VLAN Profile List, select a to-be-deleted item, click "Delete" to delete the corresponding ONU profile.
Click "New" or "Edit" to edit the profile on the following page. On the page, you can edit Profile Name, VLAN Mode, Port PVID, VLAN Trunk Allowed, IPoE VLAN, PPPoE VLAN and ARP VLAN.
After the configuration is finished, click "Apply" to save the configuration.
Figure 12: ONU VLAN Profile Config
7.5.6 ONU Flow Mapping Config
On the left navigation bar, click "ONU Config Profile" -> "ONU Flow Mapping Configuration", and the following page appears.
Figure 13: ONU Flow Mapping Profile List
Figure 14: ONU Flow Mapping Profile flow-mapping-default
On ONU Flow Mapping Profile List, select a to-be-deleted item, click "Delete" to delete the corresponding ONU profile. The default profile cannot be deleted.
Click "New" or "Edit" to edit the profile on the following page. On the page, you can edit Entry ID, UNI Port Bitmap, VLAN ID, Class of Service and Virtual Port.
After the configuration is finished, click "Apply" to save the configuration.
ONU Flow Mapping Profile flow-mapping-default
Figure 15: Add ONU Flow Mapping Profile flow-mapping-default
7.6 ONU Interface Config
ONU Interface Config
ONU Description
T-Cont Virtual Port Bind
Flow Mapping
VLAN Config
Virtual Port Bandwidth Config
Virtual Port GEM Port Bind
ONU Remote Controller
Advanced Config
L3 Config
Remote Monitor
System Mgr
Figure 1: ONU Interface Config list
7.6.1 ONU Description
On the left navigation bar, click "ONU Interface Config" -> "ONU Description", and the following page appears.
Figure 2: ONU Description list
7.6.2 T-Cont Virtual Port Bind
On the left navigation bar, click "ONU Interface Config" -> "T-Cont Virtual Port Bind", and the following page appears.
Figure 3: T-Cont Virtual Port Bind
On the page of T-Cont Virtual Port Bind Interface Config, click "Apply" to save the setting or click "Reset" to return to the default setting.
7.6.3 Flow Mapping
On the left navigation bar, click "ONU Interface Config" -> "Flow Mapping", and the following page appears.
Figure 4: Flow Mapping Interface Configuration
On the page of Flow Mapping Interface Config, click "Apply" to save the setting or click "Reset" to return to the default setting.
7.6.4 VLAN Config
On the left navigation bar, click "ONU Interface Config" -> "VLAN Config", and the following page appears.
Figure 5: VLAN Interface Configuration
7.6.5 Virtual Port Bandwidth Config
On the left navigation bar, click "ONU Interface Config" -> "Virtual Port Bandwidth Config", and the following page appears.
Figure 6: Virtual Port Bandwidth Configuration
7.6.6 Virtual Port GEM Port Bind
On the left navigation bar, click "ONU Interface Config" -> "Virtual Port GEM Port Bind", and the following page appears.
Figure 7: Virtual Port GEM Port Bind Config
7.6.7 ONU Remote Controller
On the left navigation bar, click "ONU Interface Config" -> "ONU Remote Controller", and the following page appears.
Figure 8: ONU Remote Controller Config
7.7 Advanced Config
Advanced Config
Port Description
Port Config
Rate Limit
Port Mirror
VLAN Config
VLAN Interface
LLDP Config
STP Config
Static MAC Config
Port Security
Storm Control
IP Access List
MAC Access List
Port Channel
Ring Protection
DDM Config
MTU Config
Figure 1: Advanced Config list
7.7.1 Configuring Port Description
If you click Advanced Config -> Port description Config in the navigation bar, the Port description Configuration page appears, as shown in figure 2.
| Interface | Port Description |
| g0/1 | |
| g0/2 | |
| g0/3 | |
| g0/4 | |
| g0/5 | |
| g0/6 | |
| g0/7 | |
| g0/8 | |
| tg0/1 | |
| tg0/2 | |
| tg0/3 | |
| tg0/4 | |
| gpon0/1 | |
| gpon0/2 | |
| gpon0/3 | |
| gpon0/4 | |
| gpon0/5 | |
| gpon0/6 | |
| gpon0/7 | |
| gpon0/8 |
Figure 2: Port description configuration
You can modify the port description on this page and enter up to 120 characters. The description of the VLAN port cannot be set at present.
7.7.2 Configuring the Attributes of the Port
If you click Advanced Config -> Port attribute Config in the navigation bar, the Port Attribute Configuration page appears, as shown in figure 3.
| Interface | Status | Speed | Duplex | Flow Control | Medium | |||||
| g0/1 | Up | ✓ | Auto | ✓ | Auto | ✓ | Off | ✓ | Auto | ✓ |
| g0/2 | Up | ✓ | Auto | ✓ | Auto | ✓ | Off | ✓ | Auto | ✓ |
| g0/3 | Up | ✓ | Auto | ✓ | Auto | ✓ | Off | ✓ | Auto | ✓ |
| g0/4 | Up | ✓ | Auto | ✓ | Auto | ✓ | Off | ✓ | Auto | ✓ |
| g0/5 | Up | ✓ | 1000M | ✓ | Auto | ✓ | Off | ✓ | Auto | ✓ |
| g0/6 | Up | ✓ | 1000M | ✓ | Auto | ✓ | Off | ✓ | Auto | ✓ |
| g0/7 | Up | ✓ | 1000M | ✓ | Auto | ✓ | Off | ✓ | Auto | ✓ |
| g0/8 | Up | ✓ | 1000M | ✓ | Auto | ✓ | Off | ✓ | Auto | ✓ |
| tg0/1 | Up | ✓ | 10G | ✓ | Full | ✓ | Off | ✓ | Auto | ✓ |
| tg0/2 | Up | ✓ | 10G | ✓ | Full | ✓ | Off | ✓ | Auto | ✓ |
| tg0/3 | Up | ✓ | 10G | ✓ | Full | ✓ | Off | ✓ | Auto | ✓ |
| tg0/4 | Up | ✓ | 10G | |||||||
Figure 3: Configuring the port attributes
On this page you can modify the on/off status, rate, duplex mode, flow control status and medium type of a port.
1. The Web page does not support the speed and duplex mode of the fast-Ethernet port.
2. After the speed or duplex mode of a port is modified, the link state of the port may be switched over and the network communication may be impaired.
7.7.3 Rate control
If you click Advanced Config -> Port rate-limit Config in the navigation bar, the Port rate limit page appears, as shown in figure 4.
| Port | Receive Status | Receive Speed Unit | Receive Speed | Send Status | Send Speed Unit | Send Speed | ||
| g0/1 | Disable✓ | 64kbps ✓ | (1-15625) | Disable✓ | 64kbps ✓ | (1-15625) | ||
| g0/2 | Disable✓ | 64kbps ✓ | (1-15625) | Disable✓ | 64kbps ✓ | (1-15625) | ||
| g0/3 | Disable✓ | 64kbps ✓ | (1-15625) | Disable✓ | 64kbps ✓ | (1-15625) | ||
| g0/4 | Disable✓ | 64kbps ✓ | (1-15625) | Disable✓ | 64kbps ✓ | (1-15625) | ||
| g0/5 | Disable✓ | 64kbps ✓ | (1-15625) | Disable✓ | 64kbps ✓ | (1-15625) | ||
| g0/6 | Disable✓ | 64kbps ✓ | (1-15625) | Disable✓ | 64kbps ✓ | (1-15625) | ||
| g0/7 | Disable✓ | 64kbps ✓ | (1-15625) | Disable✓ | 64kbps ✓ | (1-15625) | ||
| g0/8 | Disable✓ | 64kbps ✓ | (1-15625) | Disable✓ | 64kbps ✓ | (1-15625) | ||
| tg0/1 | Disable✓ | 64kbps ✓ | (1-156250) | Disable✓ | 64kbps ✓ | (1-156250) | ||
| tg0/2 | Disable✓ | 64kbps ✓ | (1-156250) | Disable✓ | 64kbps ✓ | (1-156250) | ||
| tg0/3 | Disable✓ | 64kbps ✓ | (1-156250) | Disable✓ | 64kbps ✓ | (1-156250) | ||
| tg0/4 | Disable✓ | 64kbps ✓ | (1-156250) | Disable✓ | 64kbps ✓ | (1-156250) | ||
| gpon0/1 | Disable✓ | 64kbps ✓ | (1-19440) | Disable✓ | 64kbps ✓ | (1-38880) | ||
| gpon0/2 | Disable✓ | 64kbps ✓ | (1-19440) | Disable✓ | 64kbps ✓ | (1-38880) | ||
| gpon0/3 | Disable✓ | 64kbps ✓ | (1-19440) | Disable✓ | 64kbps ✓ | (1-38880) | ||
| gpon0/4 | Disable✓ | 64kbps ✓ | (1-19440) | Disable✓ | 64kbps ✓ | (1-38880) | ||
| gpon0/5 | Disable✓ | 64kbps ✓ | (1-19440) | Disable✓ | 64kbps ✓ | (1-38880) | ||
| gpon0/6 | Disable✓ | 64kbps ✓ | (1-19440) | Disable✓ | 64kbps ✓ | (1-38880) | ||
| gpon0/7 | Disable✓ | 64kbps ✓ | (1-19440) | Disable✓ | 64kbps ✓ | (1-38880) | ||
| gpon0/8 | Disable✓ | 64kbps ✓ | (1-19440) | Disable✓ | 64kbps ✓ | (1-38880) |
Figure 4: Port's rate limit
On this page you can set the reception speed and transmission speed of a port. By default, all ports have no speed limited.
7.7.4 Port mirroring
If you click Advanced Config -> Port Mirror in the navigation bar, the Port Mirror Config page appears, as shown in figure 5.
Figure 5: Port mirror configuration
Click the drop-down list on the right side of "Mirror Port" and select a port to be the destination port of mirror. Click a checkbox and select a source port of mirror, that is, a mirrored port.
RX The received packets will be mirrored to the destination port.
TX The transmitted packets will be mirrored to a destination port.
RX & TX The received and transmitted packets will be mirrored simultaneously.
7.7.5 VLAN Settings
7.7.5.1 VLAN List
If you click Advanced Config -> VLAN Config in the navigation bar, the VLAN Config page appears, as shown in figure 2.
| VLAN ID | VLAN Name | Operate | |
| 1 | Default | Edit |
Figure 2: VLAN configuration
The VLAN list will display VLAN items that exist in the current device according to the ascending order. In case of lots of items, you can look for the to-be-configured VLAN through the buttons like "Prev", "Next" and "Search".
You can click "New" to create a new VLAN.
You can also click "Edit" at the end of a VLAN item to modify the VLAN name and the port's attributes in the VLAN.
If you select the checkbox before a VLAN and then click "Delete", the selected VLAN will be deleted.
By default, a VLAN list can display up to 100 VLAN items. If you want to configure more VLANs through Web, please log on to the switch through the Console port or Telnet, enter the global configuration mode and then run the "ip http web max-vlan" command to modify the maximum number of VLANs that will be displayed.
7.7.5.2 VLAN Settings
If you click "New" or "Edit" in the VLAN list, the VLAN configuration page appears, on which new VLANs can be created or the attributes of an existent VLAN can be modified.
| VLAN ID 2 | |||||
| VLAN Name VLAN0002 | |||||
| Interface | Default VLAN | Mode | Untag or not | Allow or not | |
| g0/1 | 1 | <1-4094> | Trunk✓ | No✓ | Yes✓ |
| g0/2 | 1 | <1-4094> | Trunk✓ | No✓ | Yes✓ |
| g0/3 | 1 | <1-4094> | Trunk✓ | No✓ | Yes✓ |
| g0/4 | 1 | <1-4094> | Trunk✓ | No✓ | Yes✓ |
| g0/5 | 1 | <1-4094> | Trunk✓ | No✓ | Yes✓ |
| g0/6 | 1 | <1-4094> | Trunk✓ | No✓ | Yes✓ |
| g0/7 | 1 | <1-4094> | Trunk✓ | No✓ | Yes✓ |
| g0/8 | 1 | <1-4094> | Trunk✓ | No✓ | Yes✓ |
| tg0/1 | 1 | <1-4094> | Trunk✓ | No✓ | Yes✓ |
| tg0/2 | 1 | <1-4094> | Trunk✓ | No✓ | Yes✓ |
| tg0/3 | 1 | <1-4094> | Trunk✓ | No✓ | Yes✓ |
| tg0/4 | 1 | <1-4094> | Trunk✓ | No✓ | Yes✓ |
| gpon0/1 | 1 | <1-4094> | Access✓ | No✓ | Yes✓ |
| gpon0/2 | 1 | <1-4094> | Access✓ | No✓ | Yes✓ |
| gpon0/3 | 1 | <1-4094> | Access✓ | No✓ | Yes✓ |
| gpon0/4 | 1 | <1-4094> | Access✓ | No✓ | Yes✓ |
| gpon0/5 | 1 | <1-4094> | Access✓ | No✓ | Yes✓ |
| gpon0/6 | 1 | <1-4094> | Access✓ | No✓ | Yes✓ |
| gpon0/7 | 1 | <1-4094> | Access✓ | No✓ | Yes✓ |
| gpon0/8 | 1 | <1-4094> | Access✓ | No✓ | Yes✓ |
Figure 3: Revising VLAN configuration
If you want to create a new VLAN, enter a VLAN ID and a VLAN name; the VLAN name can be null.
Through the port list, you can set for each port the default VLAN, the VLAN mode (Trunk or Access), whether to allow the entrance of current VLAN packets and whether to execute the untagging of the current VLAN when the port works as the egress port.
When a port in Trunk mode serves as an egress port, it will untag the default VLAN by default.
7.7.6 Configuring the VLAN Interface
If you click Advanced Config -> VLAN interface, the Configuring the VLAN interface page appears.
Figure 2: Configuring the VLAN interface
Click New to add a new VLAN interface. Click Cancel to delete a VLAN interface. Click Modify to modify the settings of a corresponding VLAN interface.
When you click New, the name of the corresponding VLAN interface can be modified; but if you click Modify, the name of the corresponding VLAN interface cannot be modified.
The primary IP must be configured for the VLAN interface before the secondary IP is configured
Figure 3: VLAN interface configuration
Before the accessory IP of a VLAN interface is set, you have to set the main IP.
7.7.7 LDP Configuration
7.7.7.1 Configuring the Global Attributes of LLDP
If you click Advanced Config -> LLDP Config in the navigation bar, the Global LLDP Config page appears, as shown in figure 6.
HoldTime:Means the TTL(Time to live) of sending LLDP packets. Its default value is 120s.
Reinit:Means the delay of continuously sending LLDP packets. Its default value is 2s.
Figure 6: Configuring the global attributes of LLDP
You can choose to enable LLDP or disable it. When you choose to disable LLDP, you cannot configure LLDP. The "HoldTime" parameter means the ttl value of the packet that is transmitted by LLDP, whose default value is 120s.
The "Reinit" parameter means the delay of successive packet transmission of LLDP, whose default value is 2s.
7.7.7.2 Configuring the Attributes of the LLDP Port
If you click Advanced Config -> LLDPConfig-> LLDP port Config in the navigation bar, the Setting the attributes of the LLDP port page appears, as shown in figure 7.
| Interface | Receive LLDP Packet | Send LLDP Packet | |
| g0/1 | Enable | Enable | |
| g0/2 | Enable | Enable | |
| g0/3 | Enable | Enable | |
| g0/4 | Enable | Enable | |
| g0/5 | Enable | Enable | |
| g0/6 | Enable | Enable | |
| g0/7 | Enable | Enable | |
| g0/8 | Enable | Enable | |
| tg0/1 | Enable | Enable | |
| tg0/2 | Enable | Enable | |
| tg0/3 | Enable | Enable | |
| tg0/4 | Enable | Enable | |
| gpon0/1 | Enable | Enable | |
| gpon0/2 | Enable | Enable | |
| gpon0/3 | Enable | Enable | |
| gpon0/4 | Enable | Enable | |
| gpon0/5 | Enable | Enable | |
| gpon0/6 | Enable | Enable | |
| gpon0/7 | Enable | Enable | |
| gpon0/8 | Enable | Enable | |
Figure 7: Configuring the LLDP port
After the LLDP port is configured, you can enable or disable LLDP on this port.
7.7.8 STP Configuration
7.7.8.1 STP Status Information
If you click Advanced Config -> STP Config in the navigation bar, the STP Config page appears, as shown in figure 10.
Figure 10: Configuring the global attributes of STP
The root STP configuration information and the STP port's status are only-read.
On the local STP configuration page, you can modify the running STP mode by clicking the Protocol type drop-down box. The STP modes include STP, RSTP and disabled STP.
The priority and the time need to be configured for different modes.
The change of the STP mode may lead to the interruption of the network.
7.7.8.2 Configuring the Attributes of the STP Port
If you click the "Configure RSTP Port" option, the "Configure RSTP Port" page appears.
| Interface | Protocol Status | Priority(0~240) | Path-Cost(0~200000000) | Edge Port Property | |
| g0/1 | Enable | ✓ | 128 ✓ | 0 | Auto |
| g0/2 | Enable | ✓ | 128 ✓ | 0 | Auto |
| g0/3 | Enable | ✓ | 128 ✓ | 0 | Auto |
| g0/4 | Enable | ✓ | 128 ✓ | 0 | Auto |
| g0/5 | Enable | ✓ | 128 ✓ | 0 | Auto |
| g0/6 | Enable | ✓ | 128 ✓ | 0 | Auto |
| g0/7 | Enable | ✓ | 128 ✓ | 0 | Auto |
| g0/8 | Enable | ✓ | 128 ✓ | 0 | Auto |
| gpon0/1 | Enable | ✓ | 128 ✓ | 0 | Auto |
| gpon0/2 | Enable | ✓ | 128 ✓ | 0 | Auto |
| gpon0/3 | Enable | ✓ | 128 ✓ | 0 | Auto |
| gpon0/4 | Enable | ✓ | 128 ✓ | 0 | Auto |
| gpon0/5 | Enable | ✓ | 128 ✓ | 0 | Auto |
| gpon0/6 | Enable | ✓ | 128 ✓ | 0 | Auto |
| gpon0/7 | Enable | ✓ | 128 ✓ | 0 | Auto |
| gpon0/8 | Enable | ✓ | 128 ✓ | 0 | Auto |
| tg0/1 | Enable | ✓ | 128 ✓ | 0 | Auto |
| tg0/2 | Enable | ✓ | 128 ✓ | 0 | Auto |
| tg0/3 | Enable | ✓ | 128 ✓ | 0 | Auto |
| tg0/4 | Enable | ✓ | 128 ✓ | 0 | Auto |
Figure 11: Configuring the attributes of RSTP
The configuration of the attributes of the port is irrelative of the global STP mode. For example, if the protocol status is set to "Disable" and the STP mode is also changed, the port will not run the protocol in the new mode.
The default value of the path cost of the port is 0, meaning the path cost is automatically calculated according to the speed of the port. If you want to change the path cost, please enter another value.
7.7.9 Port security
7.7.9.1 IP Binding Configuration
If you click Advanced Config -> Port Security -> IP bind in the navigation bar, the Configure the IP-Binding Info page appears, as shown in figure 7.
| Interface | Detail |
| g0/1 | Detail |
Figure 7: IP binding configuration
Click "Detail" and then you can conduct the binding of the source IP address for each physical port. In this way, the IP address that is allowed to visit the port will be limited.
| Serial number | Address | Operate | |
| 1 | 192.168.0.2 | Edit | |
| 2 | 192.168.0.3 | Edit |
Figure 8: Setting the binding of the source IP addressMAC Binding Configuration
If you click Advanced Config -> Port Security -> MAC bind in the navigation bar, the Configure the MAC-Binding Info page appears, as shown in figure 9.
| Interface Name | Detail |
| g0/1 | Detail |
Figure 9: MAC binding configuration
Click "Detail" and then you can conduct the binding of the source MAC address for each physical port. In this way, the MAC address that is allowed to visit the port will be limited.
| Serial number | Address | Operate | |
| 1 | 1234.1234.1234 | Edit | |
| 2 | 1234.1234.1235 | Edit |
Figure 10: Setting the binding of the source MAC address
7.7.9.2 Setting the Static MAC Filtration Mode
If you click Advanced Config -> Port Security -> Static MAC filtration mode in the navigation bar, the Configure the static MAC filtration mode page appears, as shown in figure 11.
| Interface Name | Port Mode | Static MAC Filtration Mode |
| g0/1 | Trunk | Disable |
Figure 11: Setting the static MAC filtration mode
On this page you can set the static MAC filtration mode. By default, the static MAC filter is disabled. Also, the static MAC filter mode cannot be set on ports in trunk mode.
7.7.9.3 Static MAC Filtration Entry
If you click Advanced Config -> Port Security -> Static MAC filtration entry in the navigation bar, the Setting the static MAC filtration entries page appears.
| Interface Name | Detail |
| g0/1 | Detail |
Figure 12: Static MAC filtration entry list
If you click "Detail", you can conduct the binding of the source MAC address for each physical port. According to the configured static MAC filtration mode, the MAC address of a port can be limited, allowed or forbidden to visit.
| Serial number | Filtration Mode | MAC Address | Operate | |
| 1 | Disable | 0001.0002.0003 | Edit |
Figure 13: Setting static MAC filtration entries
7.7.9.4 Setting the Dynamic MAC Filtration Mode
If you click Advanced Config -> Port Security -> Dynamic MAC filtration mode in the navigation bar, the Configure the dynamic MAC filtration mode page appears, as shown in figure 14.
Figure 14: Setting the dynamic MAC filtration mode
You can set the dynamic MAC filtration mode and the allowable maximum number of addresses on this page. By default, the dynamic MAC filtration mode is disabled and the maximum number of addresses is 1.
7.7.10 Storm control
In the navigation bar, click Advanced Config -> Storm control. The system then enters the page, on which the broadcast/multicast/unknown unicast storm control can be set.
7.7.10.1 Broadcast Storm Control
| Interface | Status | Threshold | |
| g0/1 | Disable✓ | (1-14880) 100PPS | |
| g0/2 | Disable✓ | (1-14880) 100PPS | |
| g0/3 | Disable✓ | (1-14880) 100PPS | |
| g0/4 | Disable✓ | (1-14880) 100PPS | |
| g0/5 | Disable✓ | (1-14880) 100PPS | |
| g0/6 | Disable✓ | (1-14880) 100PPS | |
| g0/7 | Disable✓ | (1-14880) 100PPS | |
| g0/8 | Disable✓ | (1-14880) 100PPS | |
| tg0/1 | Disable✓ | (1-148809) 100PPS | |
| tg0/2 | Disable✓ | (1-148809) 100PPS | |
| tg0/3 | Disable✓ | (1-148809) 100PPS | |
| tg0/4 | Disable✓ | (1-148809) 100PPS | |
| gpon0/1 | Disable✓ | (1-37202) 100PPS | |
| gpon0/2 | Disable✓ | (1-37202) 100PPS | |
| gpon0/3 | Disable✓ | (1-37202) 100PPS | |
| gpon0/4 | Disable✓ | (1-37202) 100PPS | |
| gpon0/5 | Disable✓ | (1-37202) 100PPS | |
| gpon0/6 | Disable✓ | (1-37202) 100PPS | |
| gpon0/7 | Disable✓ | (1-37202) 100PPS | |
| gpon0/8 | Disable✓ | (1-37202) 100PPS |
Figure 15: Broadcast storm control
Through the drop-down boxes in the Status column, you can decide whether to enable broadcast storm control on a port. In the Threshold column you can enter the threshold of the broadcast packets. The legal threshold range for each port is given behind the threshold.
7.7.10.2 Multicast Storm Control
| Interface | Status | Threshold | |
| g0/1 | Disable✓ | (1-14880) 100PPS | |
| g0/2 | Disable✓ | (1-14880) 100PPS | |
| g0/3 | Disable✓ | (1-14880) 100PPS | |
| g0/4 | Disable✓ | (1-14880) 100PPS | |
| g0/5 | Disable✓ | (1-14880) 100PPS | |
| g0/6 | Disable✓ | (1-14880) 100PPS | |
| g0/7 | Disable✓ | (1-14880) 100PPS | |
| g0/8 | Disable✓ | (1-14880) 100PPS | |
| tg0/1 | Disable✓ | (1-148809) 100PPS | |
| tg0/2 | Disable✓ | (1-148809) 100PPS | |
| tg0/3 | Disable✓ | (1-148809) 100PPS | |
| tg0/4 | Disable✓ | (1-148809) 100PPS | |
| gpon0/1 | Disable✓ | (1-37202) 100PPS | |
| gpon0/2 | Disable✓ | (1-37202) 100PPS | |
| gpon0/3 | Disable✓ | (1-37202) 100PPS | |
| gpon0/4 | Disable✓ | (1-37202) 100PPS | |
| gpon0/5 | Disable✓ | (1-37202) 100PPS | |
| gpon0/6 | Disable✓ | (1-37202) 100PPS | |
| gpon0/7 | Disable✓ | (1-37202) 100PPS | |
| gpon0/8 | Disable✓ | (1-37202) 100PPS |
Figure 16: Setting the broadcast storm control
Through the drop-down boxes in the Status column, you can decide whether to enable multicast storm control on a port. In the Threshold column you can enter the threshold of the multicast packets. The legal
threshold range for each port is given behind the threshold.
7.7.10.3 Unknown Unicast Storm Control
| Interface | Status | Threshold | |
| g0/1 | Disable✓ | (1-14880) 100PPS | |
| g0/2 | Disable✓ | (1-14880) 100PPS | |
| g0/3 | Disable✓ | (1-14880) 100PPS | |
| g0/4 | Disable✓ | (1-14880) 100PPS | |
| g0/5 | Disable✓ | (1-14880) 100PPS | |
| g0/6 | Disable✓ | (1-14880) 100PPS | |
| g0/7 | Disable✓ | (1-14880) 100PPS | |
| g0/8 | Disable✓ | (1-14880) 100PPS | |
| tg0/1 | Disable✓ | (1-148809) 100PPS | |
| tg0/2 | Disable✓ | (1-148809) 100PPS | |
| tg0/3 | Disable✓ | (1-148809) 100PPS | |
| tg0/4 | Disable✓ | (1-148809) 100PPS | |
| gpon0/1 | Disable✓ | (1-37202) 100PPS | |
| gpon0/2 | Disable✓ | (1-37202) 100PPS | |
| gpon0/3 | Disable✓ | (1-37202) 100PPS | |
| gpon0/4 | Disable✓ | (1-37202) 100PPS | |
| gpon0/5 | Disable✓ | (1-37202) 100PPS | |
| gpon0/6 | Disable✓ | (1-37202) 100PPS | |
| gpon0/7 | Disable✓ | (1-37202) 100PPS | |
| gpon0/8 | Disable✓ | (1-37202) 100PPS |
Figure 17: Unknown unicast storm control
In the Threshold column you can enter the threshold of the broadcast packets. The legal threshold range for each port is given behind the threshold.
7.7.11 IP Access Control List
7.7.11.1 Setting the Name of the IP Access Control List
If you click Advanced Config -> IP access control list -> IP access control list Config, the IP ACL configuration page appears.
Figure 9: IP access control list configuration
Click New to add a name of the IP access control list. Click Cancel to delete an IP access control list.
Figure 10: Creating a name of the IP access control list
If you click Modify, the corresponding IP access control list appears and you can set the corresponding rules for the IP access control list.
7.7.11.2 Setting the Rules of the IP Access Control List
▶ Standard IP access control list
Figure 11: Standard IP access control list
Click New to add a rule of the IP access control list. Click Cancel to delete a rule of the IP access control list. If you click Modify, the corresponding IP access control list appears and you can set the corresponding rules for the IP access control list.
Figure 12: Setting the Rules of the standard IP access control list
▶ Extended IP access control list
Figure 13: Extended IP access control list
Click New to add a rule of the IP access control list. Click Cancel to delete a rule of the IP access control list. If you click Modify, the corresponding IP access control list appears and you can set the corresponding rules for the IP access control list.
Figure 14: Setting the Rules of the extended IP access control list
7.7.11.3 Applying the IP Access Control List
If you click Advanced Config -> IP access control list -> Applying the IP access control list, the Applying the IP access control list page appears.
| Port | Egress ACL | Ingress ACL |
| GO/1 | myacl | |
| GO/2 | acla | |
| GO/3 | ||
| GO/4 | ||
| GO/5 | ||
| GO/6 | ||
| GO/7 | ||
| GO/8 |
Figure 15: Applying the IP access control list
7.7.12 MAC Access Control List
7.7.12.1 Setting the Name of the MAC Access Control List
If you click Advanced Config -> MAC access control list -> MAC access control list Config, the MAC ACL configuration page appears.
Figure 4: MAC access control list configuration
Click New to add a name of the MAC access control list. Click Cancel to delete a MAC access control list.
Figure 5: Setting the name of MAC access control list
7.7.12.2 Setting the Rules of the MAC Access Control List
If you click Modify, the corresponding MAC access control list appears and you can set the corresponding rules for the MAC access control list.
Figure 6: Specific MAC access control list configuration
Click New to add a rule of the MAC access control list. Click Cancel to delete a rule of the MAC access control list.
Figure 7: Setting the Rules of the MAC Access Control List
7.7.12.3 Applying the MAC Access Control List
If you click Advanced Config -> MAC access control list -> Applying the MAC access control list, the Applying the MAC access control list page appears.
| Port | Egress ACL | Ingress ACL |
| G0/1 | ||
| G0/2 | ||
| G0/3 | ||
| G0/4 | ||
| G0/5 | ||
| G0/6 | ||
| G0/7 |
Figure 8: Applying the MAC access control list
7.7.13 Link Aggregation Configuration
If you click Advanced Config ->Port Channel in the navigation bar, the Port aggregation Config page appears, as shown in figure 8.
Figure 8: Port aggregation configuration
If you click New, an aggregation group can be created. Up to 32 aggregation groups can be configured through Web and up to 8 physical ports in each group can be aggregated. If you click Cancel, you can delete a selected aggregation group; if you click Modify, you can modify the member port and the aggregation mode.
Figure 9: Setting the member port of the aggregation group
An aggregation group is selectable when it is created but is not selectable when it is modified.
When a member port exists on the aggregation group, you can choose the aggregation mode to be static, LACP active or LACP passive.
You can click “>>” and “<<” to delete and add a member port in the aggregation group.
7.7.14 Ring Protection Configuration
7.7.14.1 EAPS Ring List
If you click Advanced Config -> EAPS Ring Config, the EAPS ring list page appears.
Figure 19: EAPS Ring List
In the list shows the currently configured EAPS ring, including the status of the ring, the forwarding status of the port and the status of the link.
Click "New" to create a new EAPS ring.
Click the "Operate" option to configure the "Time" parameter of the ring.
- The system can support 8 EAPS rings.
- After a ring is configured, its port, node type and control VLAN cannot be modified. If the port of the ring, the node type or the control VLAN needs to be adjusted, please delete the ring and then establish a new one.
7.7.14.2 EAPS Ring Configuration
If you click "New" on the EAPS ring list, or "Operate" on the right side of a ring item, the "Configure EAPS" page appears.
Figure 20: EAPS ring configuration
If you want to modify a ring, on this page the node type, the control VLAN, the primary port and the secondary port cannot be modified.
In the dropdown box on the right of "Ring ID", select an ID as a ring ID. The ring IDs of all devices on the same ring must be the same.
The dropdown box on the right of "Node Type" is used to select the type of the node. Please note that only one master node can be configured on a ring.
Enter a value between 1 and 4094 in the text box on the right of "Control VLAN" as the control VLAN ID. When a ring is established, the control VLAN will be automatically established too. Please note that if the designated control VLAN is 1 and the VLAN of the control device is also 1 the control device cannot access the control VLAN. Additionally, please do not enter a control VLAN ID that is same as that of another ring. In the text boxes of "Primary Port" and "Secondary Port", select a port as the ring port respectively. If "Node Type" is selected as "Transit-Node", the two ports will be automatically set to transit ports.
Click "Apply" to finish EAPS ring configuration, click "Reset" to resume the initial values of the configuration, or click "Return" to go back to the EAPS list page.
7.7.15 DDM Configuration
If you click Advanced Config -> DDM Config in the navigation bar, the DDM configuration page appears, as shown in figure 21.
Figure 21: DDM configuration
7.7.16 MTU Config
On the left navigation bar, click "Advanced Config" -> "MTU Config" and the following page appears.
Figure 20: MTU Config
You can set the size of MTU within a designated range.
7.8 Layer 3 Configuration
Figure 1: Layer 3 configuration list
Only Layer 3 switches have the Layer 3 configuration.
7.8.1 Setting the Static Route
If you click Layer 3 Config -> Static route Config, the Static route configuration page appears.
Figure 4: Displaying the static route
Click Create to add a static route.
If you click Edit, you can modify the current static route.
If you click Cancel, you can cancel the chosen static route.
Global:The next-hop address is in the global routing table.
Figure 5: Setting the static route
7.9 Remote Monitor configuration
Figure 1: Remote Monitor configuration list
7.9.1 SNMP Configuration
If you click Remote Monitor -> SNMP management in the navigation bar, the SNMP management page appears, as shown in figure 2.
7.9.1.1 SNMP Community Management
Figure 2: SNMP community management
On the SNMP community management page, you can know the related configuration information about SNMP community.
You can create, modify or cancel the SNMP community information, and if you click New or Edit, you can switch to the configuration page of SNMP community.
Figure 3: SNMP community management settings
On the SNMP community management page you can enter the SNMP community name, select the attributes of SNMP community, which include Read only and Read-Write.
7.9.1.2 SNMP Host Management
Figure 4: SNMP host management
On the SNMP community host page, you can know the related configuration information about SNMP host. You can create, modify or cancel the SNMP host information, and if you click New or Edit, you can switch to the configuration page of SNMP host.
Figure 5: SNMP host management settings
On the SNMP host configuration page, you can enter SNMP Host IP, SNMP Community, SNMP Message Type and SNMP Community Version. SNMP Message Type includes Traps and Informs, and as to version 1, SNMP Message Type does not support Informs.
7.9.2 RMON Config
7.9.2.1 RMON Statistic Information Configuration
If you click Remote Monitor -> RMON Config -> RMON Statistics -> New, the RMON Statistics page appears.
![Interface Statistics Config Interface:g0/1 Index:1[1-65535] Owner:demon Apply Go Back Help #It must be configured in Interface mode, which is used to enable the interface statistics *#The string you totally entered is less than or equal to 255 characters](/content/2026/05/900918/images/6b3fe4e7879ffc440dfd4a2c9961bff60dc6a89974e06305b79a0c15df4c6fe1.jpg)
Figure 6: Configuring the RMON statistic information
You need to set a physical port to be the reception terminal of the monitor data.
The index is used to identify a specific interface; if the index is same to that of the previous application interface, it will replace that of the previous application interface.
At present, the monitor statistic information can be obtained through the command line "show rmon statistics", but the Web does not support this function.
7.9.2.2 RMON History Information Configuration
If you click Remote Monitor -> RMON Config -> RMON history -> New, the RMON history page appears.
Figure 7: Configuring the RMON history information
You need to set a physical port to be the reception terminal of the monitor data.
The index is used to identify a specific interface; if the index is same to that of the previous application interface, it will replace that of the previous application interface.
The sampling number means the items that need be reserved, whose default value is 50.
The sampling interval means the time between two data collection, whose default value is 1800s.
At present, the monitor statistic information can be obtained through the command line "show rmon history", but the Web does not support this function.
7.9.2.3 RMON Alarm Information Configuration
If you click Remote Monitor -> RMON Config -> RMON Alarm -> New, the RMON Alarm page appears.
Figure 8: Configuring the RMON alarm information
The index is used to identify specific alarm information; if the index is same to the previously applied index, it will replace the previous one.
The MIB node corresponds to OID.
If the alarm type is absolute, the value of the MIB object will be directly minitored; if the alarm type is delta, the change of the value of the MIB object in two sampling will be monitored.
When the monitored MIB object reaches or exceeds the rising threshold, the event corresponding to the index of the rising event will be triggered.
When the monitored MIB object reaches or exceeds the falling threshold, the event corresponding to the
index of the falling event will be triggered.
7.9.2.4 RMON Event Configuration
If you click Remote Monitor -> RMON Config -> RMON Event -> New, the RMON event page appears.
Figure 9: RMON event configuration
The index corresponds to the rising event index and the falling event index that have already been configured on the RMON alarm config page.
The owner is used to describe the descriptive information of an event.
"Enable log" means to add an item of information in the log table when the event is triggered.
"Enable trap" means a trap will be generated if the event is triggered.
7.10 System Management
System Mgr
Figure 1: Navigation list of system management
7.10.1 User Management
7.10.1.1 User List
If you click System Manage -> User Manage, the User Management page appears.
Figure 2: User list
You can click "New" to create a new user.
To modify the permission or the login password, click "Edit" on the right of the user list.
- Please make sure that at least one system administrator exists in the system, so that you can manage the devices through Web.
- The limited user can only browse the status of the device.
7.10.1.2 Establishing a New User
If you click "New" on the User Management page, the Creating User page appears.
Figure 3: Creating new users
In the "User name" text box, enter a name, which contains letters, numbers and symbols except question, "", &#, "#" and the "Space".
In the "Password" textbox enter a login password, and in the "Confirming password" textbox enter this login password again.
In the "User permission" dropdown box set the user's permission. The "System administrator" user can browse the status of the device and conduct relevant settings, while the limited user can only browse the status of the device.
7.10.1.3 Group Mgrfiguration
On the left navigation bar, click "System Mgr" -> "User Mgr" -> "User Group Mgr" and the following page appears.
text_imagecommands in global configuration mode.
User Group Mgr.
New
No.0 Page/Total 0 Page First Prev Next Last Go No. Page Search: Current 0 Item/Total 0 Item
Serial Number Group Name Pass-Group Rule Authen-Group Rule Author-Group Rule Operate Detail
Select All/Select None Delete
If an interface is set to be a DHCP-trusting interface, the DHCP packets received from this interface will not be checked.
Run the following commands in physical interface configuration mode.
Figure 4: User Group Management
Click "New" on the top left of the interface to create a new user group.
Click "Delete" to delete the user group.
text_imagemand Purpose
User Group Config
User Group Name*
Pass-Group Name
Authen-Group Name
Author-Group Name
Apply Reset Go Back
Help
•The user group mustn't exist.
•Rule must exist.
After source IP address monitoring is enabled in a VLAN, IP packets received from all physical ports in the VLAN will be rejected if their source MAC addresses and source IP addresses do not match up with the configured MAC-to-IP binding relationship. The binding relationship on an interface can be dynamically bound by DHCP or configured manually. If no MAC addresses are bound to IP addresses on a physical interface, the switch rejects forwarding all IP packets received from the physical interface.
Run the following commands in global configuration mode.
Figure 5: User Group Config
The user group name cannot be created before. The Pass-Group Name, Authen-Group Name and Author-Group Name must be created before; otherwise, the new created user group cannot be succeeded. Set Pass-Group Name, Authen-Group Name, and Author-Group Name on the relevant tab pages.
7.10.1.4 Pass-Group Mgrd0790c94bba75ccead3356.jpg)
If the DHCP packet (also the IP packet) is received, it will be forwarded because global snooping is configured.
On the left navigation bar, click "System Mgr" -> "User Mgr" -> "Pass- Group Mgr" and the following page appears.
text_imagemand Purpose
Pass-Group Mgr.
New
No.0 Page/Total 0 Page First Prev Next Last Go No. Page Search: Current 0 Item/Total 0 Item
Serial Number Pass-Group Name Same as the username Min Length Validity Number Lower-letter Upper-letter Special-character Operate
Select All/Select None Delete
Run the following commands in global configuration mode.
Figure 6: Password Group Management
Click "New" to create a new Pass-Group Name.
Click "Delete" to delete the selected Pass-Group Name.
text_imageg-the-interval-for-checking-interface-binding-backup">
Pass-Group Config
Pass-Group Name*
Same as Username
Can
Contain Number
Must
Contain Lower-letter
Must
Contain Upper-letter
Must
Contain Special-character
Must
Min Length
(1-127)
Validity
0 d 0 h 0 m 0 s
Apply Reset Go Back
Help
•Config Pass-Group
The following command can be used to forward the DHCP packets to the designated DHCP server to realize DHCP relay. The negative form of this command can be used to shut down DHCP relay.
This command can only be used to enable DHCP relay on L2 switches, while on L3 switches, DHCP relay is realized by the DHCP server.
Run the following commands in global configuration mode.
Figure 7: Pass Group Configuration
Set some password rules including whether the password can be the same with the user name, whether the password must contain numbers, lowercase, uppercase, special characters, the minimum length and the period of validity.
When the rule is created and applied to the user management, the user password will show invalid if the set password is not complied with the password rule, vice versa.
7.10.1.5 Authen-Group Mgrip dhcp-relay agent
On the left navigation bar, click "System Mgr" -> "User Mgr" -> "Authen-Group Mgr" and the following page appears.
text_images the information about the DHCP snooping configuration:
switch#show ip dhcp-relay snooping
ip dhcp-relay snooping vlan 3
ip arp inspection vlan 3
DHCP Snooping trust interface:
FastEthernet0/1
ARP Inspect interface:
FastEthernet0/11
The following shows the binding information about dhcp-relay snooping:
switch#show ip dhcp-relay snooping binding
Hardware Address IP Address remainder time Type VLAN interface
a8-f7-e0-26-23-89 192.2.2.101 86400 DHCP\_SN 3 FastEthernet0/3
The following shows all binding information about dhcp-relay snooping:
switch#show ip dhcp-relay snooping binding all
Hardware Address IP Address remainder time Type VLAN interface
a8-f7-e0-32-1c-59 192.2.2.1 infinite MANUAL 1 FastEthernet0/2
a8-f7-e0-26-23-89 192.2.2.101 86400 DHCP\_SN 3 FastEthernet0/3
The following shows the information about dhcp-relay snooping.
switch#debug ip DHCP-snooping packet
DHCPR: receive I2 packet from vlan 3, diID: 3
DHCPR: DHCP packet len 277
DHCPR: add binding on interface FastEthernet0/3
DHCPR: send packet continue
DHCPR: receive I2 packet from vlan 3, diID: 1
DHCPR: DHCP packet len 300
DHCPR: send packet continue
DHCPR: receive I2 packet from vlan 3, diID: 3
DHCPR: DHCP packet len 289
DHCPR: send packet continue
DHCPR: receive I2 packet from vlan 3, diID: 1
DHCPR: DHCP packet len 300
DHCPR: update binding on interface FastEthernet0/3
DHCPR: IP address: 192.2.2.101, lease time 86400 seconds
DHCPR: send packet continue
Author-Group Mgr.
New
No.0 Page/Total 0 Page First Prev Next Last Go No. Page Search: Current 0 Item/Total 0 Item
Serial Number Authen-Group Name Max try times Duration for all tries Operate
Select All/Select None Delete
ip arp inspection vlan 3
DHCP Snooping trust interface:
FastEthernet0/1
ARP Inspect interface:
FastEthernet0/11
The following shows the binding information about dhcp-relay snooping:
switch#show ip dhcp-relay snooping binding
Hardware Address IP Address remainder time Type VLAN interface
a8-f7-e0-26-23-89 192.2.2.101 86400 DHCP\_SN 3 FastEthernet0/3
The following shows all binding information about dhcp-relay snooping:
switch#show ip dhcp-relay snooping binding all
Hardware Address IP Address remainder time Type VLAN interface
a8-f7-e0-32-1c-59 192.2.2.1 infinite MANUAL 1 FastEthernet0/2
a8-f7-e0-26-23-89 192.2.2.101 86400 DHCP\_SN 3 FastEthernet0/3
The following shows the information about dhcp-relay snooping.
switch#debug ip DHCP-snooping packet
DHCPR: receive I2 packet from vlan 3, diID: 3
DHCPR: DHCP packet len 277
DHCPR: add binding on interface FastEthernet0/3
DHCPR: send packet continue
DHCPR: receive I2 packet from vlan 3, diID: 1
DHCPR: DHCP packet len 300
DHCPR: send packet continue
DHCPR: receive I2 packet from vlan 3, diID: 3
DHCPR: DHCP packet len 289
DHCPR: send packet continue
DHCPR: receive I2 packet from vlan 3, diID: 1
DHCPR: DHCP packet len 300
DHCPR: update binding on interface FastEthernet0/3
DHCPR: IP address: 192.2.2.101, lease time 86400 seconds
DHCPR: send packet continue
Figure 8: Authorization Group Management
Click "New" to create a new authen-group name.
Click "Delete" to delete the authen-group name.
text_imagep-relay snooping binding
Hardware Address IP Address remainder time Type VLAN interface
a8-f7-e0-26-23-89 192.2.2.101 86400 DHCP\_SN 3 FastEthernet0/3
The following shows all binding information about dhcp-relay snooping:
switch#show ip dhcp-relay snooping binding all
Hardware Address IP Address remainder time Type VLAN interface
a8-f7-e0-32-1c-59 192.2.2.1 infinite MANUAL 1 FastEthernet0/2
a8-f7-e0-26-23-89 192.2.2.101 86400 DHCP\_SN 3 FastEthernet0/3
The following shows the information about dhcp-relay snooping.
switch#debug ip DHCP-snooping packet
DHCPR: receive I2 packet from vlan 3, diID: 3
DHCPR: DHCP packet len 277
DHCPR: add binding on interface FastEthernet0/3
DHCPR: send packet continue
DHCPR: receive I2 packet from vlan 3, diID: 1
DHCPR: DHCP packet len 300
DHCPR: send packet continue
DHCPR: receive I2 packet from vlan 3, diID: 3
DHCPR: DHCP packet len 289
DHCPR: send packet continue
DHCPR: receive I2 packet from vlan 3, diID: 1
DHCPR: DHCP packet len 300
DHCPR: update binding on interface FastEthernet0/3
DHCPR: IP address: 192.2.2.101, lease time 86400 seconds
DHCPR: send packet continue
Authen-Group Config
Authen-Group Name*
Max try times (1-9)
Duration for all tries 0 d 0 h 0 m 0 s
Apply Reset Go Back
Help
• Configure the Authen-Group
• 'Max Try Times' and 'Duration for all tries' must be entered at the same time
Hardware Address IP Address remainder time Type VLAN interface
a8-f7-e0-32-1c-59 192.2.2.1 infinite MANUAL 1 FastEthernet0/2
a8-f7-e0-26-23-89 192.2.2.101 86400 DHCP\_SN 3 FastEthernet0/3
The following shows the information about dhcp-relay snooping.
switch#debug ip DHCP-snooping packet
DHCPR: receive I2 packet from vlan 3, diID: 3
DHCPR: DHCP packet len 277
DHCPR: add binding on interface FastEthernet0/3
DHCPR: send packet continue
DHCPR: receive I2 packet from vlan 3, diID: 1
DHCPR: DHCP packet len 300
DHCPR: send packet continue
DHCPR: receive I2 packet from vlan 3, diID: 3
DHCPR: DHCP packet len 289
DHCPR: send packet continue
DHCPR: receive I2 packet from vlan 3, diID: 1
DHCPR: DHCP packet len 300
DHCPR: update binding on interface FastEthernet0/3
DHCPR: IP address: 192.2.2.101, lease time 86400 seconds
DHCPR: send packet continue
Figure 9: Authentication Group Configuration
On the above page, the Max try times and Duration for all tries must be configured simultaneously. Otherwise, the configuration cannot take effect.
7.10.1.6 Author-Group Mgroping.
switch#debug ip DHCP-snooping packet
DHCPR: receive I2 packet from vlan 3, diID: 3
DHCPR: DHCP packet len 277
DHCPR: add binding on interface FastEthernet0/3
DHCPR: send packet continue
DHCPR: receive I2 packet from vlan 3, diID: 1
DHCPR: DHCP packet len 300
DHCPR: send packet continue
DHCPR: receive I2 packet from vlan 3, diID: 3
DHCPR: DHCP packet len 289
DHCPR: send packet continue
DHCPR: receive I2 packet from vlan 3, diID: 1
DHCPR: DHCP packet len 300
DHCPR: update binding on interface FastEthernet0/3
DHCPR: IP address: 192.2.2.101, lease time 86400 seconds
DHCPR: send packet continue
On the left navigation bar, click "System Mgr" -> "User Mgr" -> "Author-Group Mgr" and the following page appears.
text_imagelen 277
DHCPR: add binding on interface FastEthernet0/3
DHCPR: send packet continue
DHCPR: receive I2 packet from vlan 3, diID: 1
DHCPR: DHCP packet len 300
DHCPR: send packet continue
DHCPR: receive I2 packet from vlan 3, diID: 3
DHCPR: DHCP packet len 289
DHCPR: send packet continue
DHCPR: receive I2 packet from vlan 3, diID: 1
DHCPR: DHCP packet len 300
DHCPR: update binding on interface FastEthernet0/3
DHCPR: IP address: 192.2.2.101, lease time 86400 seconds
DHCPR: send packet continue
Author-Group Mgr.
New
No.0 Page/Total 0 Page First Prev Next Last Go No. Page Search: Current 0 Item/Total 0 Item
Serial Number Author-Group Name Precedence Operate
Select All/Select None Delete
DHCPR: DHCP packet len 300
DHCPR: send packet continue
DHCPR: receive I2 packet from vlan 3, diID: 3
DHCPR: DHCP packet len 289
DHCPR: send packet continue
DHCPR: receive I2 packet from vlan 3, diID: 1
DHCPR: DHCP packet len 300
DHCPR: update binding on interface FastEthernet0/3
DHCPR: IP address: 192.2.2.101, lease time 86400 seconds
DHCPR: send packet continue
Figure 10: Authorization Group Management
Click "New" to create a new author-group name.
Click "Delete" to delete the author-group name.
text_imageacket from vlan 3, diID: 1
DHCPR: DHCP packet len 300
DHCPR: update binding on interface FastEthernet0/3
DHCPR: IP address: 192.2.2.101, lease time 86400 seconds
DHCPR: send packet continue
Author-Group Config
Author-Group Name*
Precedence System administrator
Apply Reset Go Back
Help
•Config Author-Group
DHCPR: send packet continue
Figure 11: Authorization Group Configuration
The authorization rule determines your permission of the administrator or the limited user. If you are the administrator, you have the administrator right. If you are the limited user, you can only but check the web.
7.10.2 Log Managementh1>
If you click System Manage -> Log Manage, the Log Management page appears.
text_imagemodes, the normal mode (default) and the aggressive mode. In normal mode, UDLD can detect the existence of a unidirectional link according to the unidirectional services of the link. In aggressive mode, UDLD can detect not only the existence of a unidirectional link as in the previous mode but also connection interruption which cannot be detected by L1 detection protocols.
In normal mode, if UDLD determines that the connection is gone, UDLD will set the state of the port to undetermined, not to down. In aggressive mode, if UDLD determines that the link is gone and the link cannot be reconnected, it is thought that interrupted communication is a severe network problem and UDLD will set the state of the protocol to linkdown and the port is in errdisable state. No matter in what mode, if UDLD maintains it is a bidirectional link, the port will be set to bidirectional.
In aggressive mode, UDLD can detect the following cases of the unidirectional link:
On the optical fiber or the twisted pair, an interface cannot receive or transmit services.
On the optical fiber or the twisted pair, the interface of one terminal is down and the interface of the other terminal is up.
One line in the optical cable is broken, and therefore the data can only be transmitted or only be received. In previous cases, UDLD will shut down the affected interface.
Log Management
System logs will be sent to the server when it is enabled
Enable the log server ✓
Address of the log server 192.168.1.77
Level of system logs (7-debugging) ✓
Enable the log buffer □
Size of the log buffer 4096 (Bytes)
Level of cache logs (7-debugging) ✓
Apply
Figure 12: Log management
If "Enabling the log server" is selected, the device will transmit the log information to the designated server. In this case, you need enter the address of the server in the "Address of the system log server" textbox and select the log's grade in the "Grade of the system log information" dropdown box.
If "Enabling the log buffer" is selected, the device will record the log information to the memory. By logging on to the device through the Console port or Telnet, you can run the command "show log" to browse the logs which are saved on the device. The log information which is saved in the memory will be lost after rebooting. Please enter the size of the buffer area in the "Size of the system log buffer" textbox and select the grade of the cached log in the "Grade of the cache log information" dropdown box.
7.10.3 Diagnosticll ports and, when a UDLD echo information is received on the ports, a detection phase and an authentication process are triggered. If all effective conditions are satisfied (port is connected in two directions and the cable is correctly connected), this port will be up. Otherwise, the port will be down.
Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 15 seconds.
7.10.3.1 Pingbeled as bidirectional, UDLD will transmit a probe/echo message every 15 seconds.
If you click Diagnostic -> Ping, the Ping page appears.
Ping may be in one of the following states:
Ping is a typical network tool, which is used to identify the states of some network functions. The states of network functions are the basis of regular network diagnosis. Ping is used to check whether the peer is reachable. If Ping transmits a packet to the host and receives a response from the peer, the peer is reachable.
PING test-->
Destination address*
Source IP address
Size of the PING packet
(An option which can be null)
(36-20000) (An option which can be null)
PING
Helpage Interval of the Aggressive Mode
- Restarting the Interface Shut Down by UDLD
- Displaying the UDLD State
The ping program can test whether a destination can be reached, or it can test the packet loss to reach a destination.
Destination address: Enter the to-be-tested destination address.
Source IP: Source IP.
4Packet's size: Designate the size of a packet when the packet is used to ping a destination. It is optional and cannot be configured.
Figure 13: Ping
Ping is used to test whether the switch connects other devices.
If a Ping test need be conducted, please enter an IP address in the "Destination address" textbox, such as the IP address of your PC, and then click the "PING" button. If the switch connects your entered address, the device can promptly return a test result to you; if not, the device will take a little more time to return the test result.
"Source IP address" is used to set the source IP address which is carried in the Ping packet.
"Size of the PING packet" is used to set the length of the Ping packet which is transmitted by the device.
7.10.4 Managing the Configuration FilesWhen UDLD is in aggressive mode and the port stops transmitting the UDLD packets, UDLD will try to establish a link with its neighbor again. If the times of tries exceed a certain number, the state of the port is changed into the Error-Disable state and the link of the port is down. When UDLD is running, the ports at both terminals should run in the same mode, or the expecting result cannot be obtained.
If you click System Manage -> Startup-config, the Configuration file page appears.
7.10.4.1 Exporting the Configuration Information
Export the current startup-config
Export the current startup-config
Export
Figure 14: Exporting the configuration file
The current configuration file can be exported, saved in the disk of PC or in the mobile storage device as the backup file.
To export the configuration file, please click the "Export" button and then select the "Save" option in the pop-up download dialog box.
The default name of the configuration file is "startup-config", but you are suggested to set it to an easily memorable name.
7.10.4.2 Importing the Configuration Informationerval of the aggressive mode.
text_imagemand Purpose
Import startup-config file
Import startup-config file
Reboot is required after importing startup-config!
Import
Figure 15: Importing the configuration files
You can import the configuration files from PC to the device and replace the configuration file that is currently being used. For example, by importing the backup configuration files, you can resume the device to its configuration of a previous moment.
- Please make sure that the imported configuration file has the legal format for the configuration file with illegal format cannot lead to the normal startup of the device.
- If error occurs during the process of importation, please try it later again, or click the "Save All" button to make the device re-establish the configuration file with the current configuration, avoiding the incomplete file and the abnormality of the device.
- After the configuration file is imported, if you want to use the imported configuration file immediately, do not click "Save All", but reboot the device directly.
7.10.5 Software Managementguration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 5
Entry 1
...
Expiration time: 42
Cache Device index: 1
Device ID: CAT0611Z0L9
Port ID: FastEthernet0/1
Neighbor echo 1 device: S35000202
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 5
UDLD Device name: Switch
Interface FastEthernet0/2
---
Port enable administrative configuration setting: Disabled
Port enable operational state: Disabled
Current bidirectional state: Unknown
Interface FastEthernet0/3
\-
Port enable administrative configuration setting: Disabled
Port enable operational state: Disabled
Current bidirectional state: Unknown
......
It is used to display the operational state of the UDLD module of the current interface.
Switch#show udld interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 5
Entry 1
---
Expiration time: 42
Cache Device index: 1
Device ID: CAT0611Z0L9
Port ID: FastEthernet0/1
Neighbor echo 1 device: S35000202
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 5
UDLD Device name: Switch
If you click System Manage -> IOS Software, the software managementpage appears.
7.10.5.1 Backing up the IOS Softwareonal
Current operational state: Advertisement
Message interval: 15
Time out interval: 5
Entry 1
...
Expiration time: 42
Cache Device index: 1
Device ID: CAT0611Z0L9
Port ID: FastEthernet0/1
Neighbor echo 1 device: S35000202
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 5
UDLD Device name: Switch
Interface FastEthernet0/2
---
Port enable administrative configuration setting: Disabled
Port enable operational state: Disabled
Current bidirectional state: Unknown
Interface FastEthernet0/3
\-
Port enable administrative configuration setting: Disabled
Port enable operational state: Disabled
Current bidirectional state: Unknown
......
It is used to display the operational state of the UDLD module of the current interface.
Switch#show udld interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 5
Entry 1
---
Expiration time: 42
Cache Device index: 1
Device ID: CAT0611Z0L9
Port ID: FastEthernet0/1
Neighbor echo 1 device: S35000202
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 5
UDLD Device name: Switch
Backup System
Current software version: switch.bin, 2.2.0B Build 48290 Build 48290, 2017-12-1 17:14:43 by SYS
File name on the server switch.bin
Backup System
Figure 16: Backing up IOS
On this page the currently running software version is displayed. If you want to backup IOS, please click "Backup IOS"; then on the browser the file download dialog box appears; click "Save" to store the IOS file to the disk of the PC, mobile storage device or other network location.
The default name of the IOS file is "Switch.bin", and it is recommended to change it to a name that is easy to identify and find when it is backed up.
7.10.5.2 Upgrading the IOS Software5000202
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 5
UDLD Device name: Switch
Interface FastEthernet0/2
---
Port enable administrative configuration setting: Disabled
Port enable operational state: Disabled
Current bidirectional state: Unknown
Interface FastEthernet0/3
\-
Port enable administrative configuration setting: Disabled
Port enable operational state: Disabled
Current bidirectional state: Unknown
......
It is used to display the operational state of the UDLD module of the current interface.
Switch#show udld interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 5
Entry 1
---
Expiration time: 42
Cache Device index: 1
Device ID: CAT0611Z0L9
Port ID: FastEthernet0/1
Neighbor echo 1 device: S35000202
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 5
UDLD Device name: Switch
- Please make sure that your upgraded IOS matches the device type, because the matchable IOS will not lead to the normal startup of the device.
- The upgrade of IOS probably takes one to two minutes; when the "updating" button is clicked, the IOS files will be uploaded to the device.
- If errors occur during upgrade, please do not restart the device or cut off the power of the device, or the device cannot be started. Please try the upgrade again.
- After the upgrade please save the configuration and then restart the device to run the new IOS.
Update System
Reboot is required after the update of System software!
☐ Reboot the device automatically after update
File name on the server switch.bin
Update System
瀏覽...
Upgrade
Figure 17: Upgrading the IOS software
The upgraded IOS is always used to solve the already known problems or to perfect a specific function. If you device run normally, do not upgrade your IOS software frequently.
If IOS need be upgraded, please first enter the complete path of the new IOS files in the textbox on the right of "Upgrading IOS", or click the "Browsing" button and select the new IOS files on your computer, and then click "Updating".
7.10.6 Factory Settings Disabled
Port enable operational state: Disabled
Current bidirectional state: Unknown
......
It is used to display the operational state of the UDLD module of the current interface.
Switch#show udld interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 5
Entry 1
---
Expiration time: 42
Cache Device index: 1
Device ID: CAT0611Z0L9
Port ID: FastEthernet0/1
Neighbor echo 1 device: S35000202
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 5
UDLD Device name: Switch
On the left navigation bar, click "System Mgr" -> "Factory Setting" and the following page appears.
text_imageal state: Unknown
......
It is used to display the operational state of the UDLD module of the current interface.
Switch#show udld interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 5
Entry 1
---
Expiration time: 42
Cache Device index: 1
Device ID: CAT0611Z0L9
Port ID: FastEthernet0/1
Neighbor echo 1 device: S35000202
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 5
UDLD Device name: Switch
Restore the original settings
Restore the original settings
Reboot is required
Restore
Switch#show udld interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 5
Entry 1
---
Expiration time: 42
Cache Device index: 1
Device ID: CAT0611Z0L9
Port ID: FastEthernet0/1
Neighbor echo 1 device: S35000202
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 5
UDLD Device name: Switch
Figure 18: Restore to the original settings
- If you click the "Resume" button, the current configuration will be replaced by the original configuration, which will take effect after rebooting.
- Before rebooting the device still works under the current configuration, and if you click "Save All" at the moment, the current configuration will replace the original configuration. The original configuration, therefore, cannot take effect after rebooting.
- After the rebooting is done and the original configuration takes effect, the Web access of the device will be automatically started. The address of Vlan 1 is 192.168.1.1/255.255.255.0, and the username and password are both "admin". To resume the original configuration, click "Resume" and then reboot the device.
7.10.7 Rebooting the Device
If you click System Manage -> Reboot Device, the Rebooting page appears.
text_imagetails>
Rebooting
Reboot
Reboot
Help
Figure 19: Rebooting the device
If the device need be rebooted, please first make sure that the modified configuration of the device has already been saved, and then click the "Reboot" button.
7.10.8 Aboutnaged switch B:
Switch\_config#udld enable
Switch\_config#
Entering the show command on managed switch A:
Switch\_config#show udld interface g0/1
Interface g0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Detection
Message interval: 15
Time out interval: 1
Entry 1
---
Expiration time: 44
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 1
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udld interface f0/1
Interface FastEthernet0/1
...
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
On the left navigation bar, click "System Mgr" -> "About" and the following page appears.
Copyright (c) 2020 PLANET Technology Corporation
Homepage: www.planet.com.tw
Telephone: +886-2-22199518
Figure 20: About
8. Interface Configurationn setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Detection
Message interval: 15
Time out interval: 1
Entry 1
---
Expiration time: 44
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 1
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udld interface f0/1
Interface FastEthernet0/1
...
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
8.1 Introductionation setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Detection
Message interval: 15
Time out interval: 1
Entry 1
---
Expiration time: 44
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 1
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udld interface f0/1
Interface FastEthernet0/1
...
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
This section helps user to learn various kinds of interface that our switch supports and consult configuration information about different interface types.
For detailed description of all interface commands used in this section, refer to Interface configuration command. For files of other commands appeared in this section, refer to other parts of the manual.
The introduction includes communication information that can be applied to all interface types.
8.1.1 Supported Interface Typesinterval: 1
Entry 1
---
Expiration time: 44
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 1
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udld interface f0/1
Interface FastEthernet0/1
...
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
For information about interface types, please refer to the following table.
Interface Type1
---
Expiration time: 44
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 1
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udld interface f0/1
Interface FastEthernet0/1
...
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
Taskation time: 44
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 1
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udld interface f0/1
Interface FastEthernet0/1
...
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
Referenceche Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 1
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udld interface f0/1
Interface FastEthernet0/1
...
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
evice index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 1
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udld interface f0/1
Interface FastEthernet0/1
...
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
Ethernet interface6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 1
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udld interface f0/1
Interface FastEthernet0/1
...
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
Configures Ethernet interface.Configures fast Ethernet interface.Configures gigabit Ethernet interface.et0/1
Message interval: 15
Time out interval: 1
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udld interface f0/1
Interface FastEthernet0/1
...
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
Configuring Ethernet Interfacenterval: 1
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udld interface f0/1
Interface FastEthernet0/1
...
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
al: 1
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udld interface f0/1
Interface FastEthernet0/1
...
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
Logical InterfaceSwitch\_config#
Switch\_config#show udld interface f0/1
Interface FastEthernet0/1
...
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
Loopback interfaceNull interfaceVLAN interface1
Interface FastEthernet0/1
...
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
Configuring Logistical InterfaceThe loopback interface and null interface are only configured on layer-3 switch. User can configure the VLAN interface on layer-2 switch.t operational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
rational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
Aggregation interfacesage interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
Configuring Logistical InterfaceEntry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
--
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
The two supported kinds of interface: Ethernet interface and logical interface. The Ethernet interface type depends on one device depends on the standard communication interface and the interface card or interfaced module installed on the switch. The logical interface is the interface without the corresponding physical device, which is established by user manually.
The supported Ethernet interfaces of our switch include:
- Ethernet interface
- Fast Ethernet interface
• Gigabit Ethernet interface
● The supported logical interface of our switch include:
- loopback interface
- null interface
- aggregation interface
- vlan interface
8.1.2 Interface Configuration Introductionrval: 15
Time out interval: 1
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udld interface f0/1
Interface FastEthernet0/1
...
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
The following description applies to the configuration process of all interfaces. Take the following steps to perform interface configuration in global configuration mode.
(1) Run the interface command to enter the interface configuration mode and start configuring interface. At this time, the switch prompt becomes 'config_' plus the shortened form of the interface to be configured. Use these interfaces in terms of their numbers. Numbers are assigned during installation(exworks) or when an interface card are added to the system. Run the show interface command to display these interfaces. Each interface that the device supports provides its own state as follows:
Switch#show interface
GigaEthernet1/1 is down, line protocol is down
Hardware is Fast Ethernet, Address is 0009.7cf7.7dc1
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Auto-duplex, Auto-speed
input flow-control is off, output flow-control is off
ARP type: ARPA, ARP Timeout 04: 00: 00
Last input never, output 17: 52: 52, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue : 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1 packets input, 64 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
1 packets output, 64 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out
To configure gigabit Ethernet interface g1/1, enter the following content:
interface GigaEthernet0/1
The switch prompts "config_g1/1".
There is no need to add blank between interface type and interface number. For example, in the above line, g 1/1 or g 1/1 is both rights.
(1) You can configure the interface configuration commands in interface
configuration mode. Various commands define protocols and application programs to be executed on the interface. These commands will stay until user exits the interface configuration mode or switches to another interface.
(2) Once the interface configuration has been completed, use the show command in the following chapter 'Monitoring and Maintaining Interface' to test the interface state.
8.2 Interface Configuratione ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
8.2.1 Configuring Interface Common Attributeet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
The following content describes the command that can be executed on an interface of any type and configures common attributes of interface. The common attributes of interface that can be configured include: interface description, bandwidth and delay and so on.
8.2.1.1 Adding Description FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
Adding description about the related interface helps to memorize content attached to the interface. This description only serves as the interface note to help identify uses of the interface and has no effect on any feature of the interface. This description will appear in the output of the following commands: show running-config and show interface. Use the following command in interface configuration mode if user wants to add a description to any interface.
Command Description echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
evice: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
description stringo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
Adds description to the currently-configured interface.al: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
5
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
LD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
For examples relevant to adding interface description, please refer to the following section 'Interface Description Example'.
8.2.1.2 Configuring Bandwidth out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
The upper protocol uses bandwidth information to perform operation decision. Use the following command to configure bandwidth for the interface:
Command Description name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
S-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
0-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
bandwidthkilobpsom the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
Configures bandwidth for the currently configured interface.tate which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
The bandwidth is just a routing parameter, which doesn't influence the communication rate of the actual physical interface.
8.2.1.3 Configuring Time Delay phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
The upper protocol uses time delay information to perform operation decision. Use the following command to configure time delay for the interface in the interface configuration mode.
Command Descriptione UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
ckets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
delaytensofmicroseconds
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
Configures time delay for the currently configured interface. eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
t seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
onds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
The configuration of time delay is just an information parameter. Use this command cannot adjust the actual time delay of an interface.
8.2.2 Monitoring and Maintaining Interfaceas bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
The following tasks can monitor and maintain interface:
- Checking interface state
- Initializing and deleting interface
● Shutting down and enabling interface
8.2.2.1 Checking Interface State and group address and to update simultaneously with the multicast changes, enabling layer-2 switches to forward data according to the topology structure of the multicast group.
The main functions of IGMP-snooping are shown as follows:
● Listening IGMP message;
- Maintaining the relationship table between VLAN and group address;
- Keeping the IGMP entity of host and the IGMP entity of router in the same state to prevent flooding from occurring.
Because igmp-snooping realizes the above functions by listening the query message and report message of igmp, igmp-snooping can function properly only
when it works on the multicast router, that is, the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
Our switch supports displaying several commands related to interface information, including version number of software and hardware, interface state. The following table lists a portion of interface monitor commands. For the description of these commands, please refer to 'Interface configuration command'.
Use the following commands:
Command Descriptionand the IGMP entity of router in the same state to prevent flooding from occurring.
Because igmp-snooping realizes the above functions by listening the query message and report message of igmp, igmp-snooping can function properly only
when it works on the multicast router, that is, the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
GMP entity of router in the same state to prevent flooding from occurring.
Because igmp-snooping realizes the above functions by listening the query message and report message of igmp, igmp-snooping can function properly only
when it works on the multicast router, that is, the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
ntity of router in the same state to prevent flooding from occurring.
Because igmp-snooping realizes the above functions by listening the query message and report message of igmp, igmp-snooping can function properly only
when it works on the multicast router, that is, the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
show interface [type [slot|port]]looding from occurring.
Because igmp-snooping realizes the above functions by listening the query message and report message of igmp, igmp-snooping can function properly only
when it works on the multicast router, that is, the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
Displays interface state.gmp-snooping realizes the above functions by listening the query message and report message of igmp, igmp-snooping can function properly only
when it works on the multicast router, that is, the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
nooping realizes the above functions by listening the query message and report message of igmp, igmp-snooping can function properly only
when it works on the multicast router, that is, the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
show running-configions by listening the query message and report message of igmp, igmp-snooping can function properly only
when it works on the multicast router, that is, the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
Displays current configuration.report message of igmp, igmp-snooping can function properly only
when it works on the multicast router, that is, the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
t message of igmp, igmp-snooping can function properly only
when it works on the multicast router, that is, the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
sage of igmp, igmp-snooping can function properly only
when it works on the multicast router, that is, the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
8.2.2.2 Initializing and Deleting Interfacemessage of igmp, igmp-snooping can function properly only
when it works on the multicast router, that is, the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
You can dynamically establish and delete logical interfaces. This also applies to the sub interface and channalized interface. Use the following command to initialize and delete interface in global configuration mode:
Command Descriptionter, that is, the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
is, the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
no interface type [slot/port]gmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
Initializes physical interface or deletes virtual interface.nooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
ng must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
st be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
8.2.2.3 Shutting down and Enabling InterfaceN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
When an interface is shut down, all features of this interface are disabled, and also this interface is marked as unavailable interface in all monitor command displays. This information can be transmitted to other switches via dynamic routing protocol.
Use the following command to shutdown or enable an interface in the interface configuration mode:
Command Description-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
shutdown Shuts down an interface. IGMP-snooping configuration example
oping configuration example
configuration example
no shutdownEnables an interface.g-igmp-snooping-of-vlan">p-snooping-of-vlan">oping-of-vlan">
You can use the show interface command and the show running-config command to check whether an interface has been shut down. An interface that has been shut down is displayed as 'administratively down' in the show interface command display. For more details, please refer to the following example in 'Interface Shutdown Example'.
8.2.3 Configuring Logistical InterfaceGMP-Snooping of VLAN
This section describes how to configure a logical interface. The contents are as follows:
- Configuring null interface
- Configuring loopback interface.
- Configuring aggregation interface
- Configuring VLAN interface
8.2.3.1 Configuring Null Interfacec4f18d51441398e7.jpg)
IGMP-snooping can run on up to 16 VLANs.
To enable IGMP-snooping on VLAN3, you must first run no ip IGMP-snooping to disable IGMP-snooping of all VLANs, then configure ipIGMP-snooping VLAN 3 and save configuration.
The whole system supports only one null interface. Its functions are similar to those of applied null devices on most operating systems. The null interface is always available, but it never sends or receives communication information. The interface configuration command no ip unreachable is the only one command available to the null interface. The null interface provides an optional method to filtrate communication. That is, the unwanted network communication can be routed to the null interface; the null interface can function as the access control list.
You can run the following command in global configuration mode to specify the null interface:
Command Descriptionyou must first run no ip IGMP-snooping to disable IGMP-snooping of all VLANs, then configure ipIGMP-snooping VLAN 3 and save configuration.
first run no ip IGMP-snooping to disable IGMP-snooping of all VLANs, then configure ipIGMP-snooping VLAN 3 and save configuration.
run no ip IGMP-snooping to disable IGMP-snooping of all VLANs, then configure ipIGMP-snooping VLAN 3 and save configuration.
interface null0disable IGMP-snooping of all VLANs, then configure ipIGMP-snooping VLAN 3 and save configuration.
Enters the null interface configuration state.MP-snooping VLAN 3 and save configuration.
ooping VLAN 3 and save configuration.
g VLAN 3 and save configuration.
The null interface can be applied in any command that takes the interface type as its parameter.
The following case shows how to configure a null interface for the routing of IP 192.168.20.0.
ip route 192.168.20.0 255.255.255.0 null 0
8.2.3.2 Configuring Loopback Interfacean_id staticA.B.C.D interfaceintf
The loopback interface is a logistical interface. It always functions and continues BGP session even in the case that the outward interface is shut down. The loopback interface can be used as the terminal address for BGP session. If other switches try to reach the loopback interface, a dynamic routing protocol should be configured to broadcast the routes with loopback interface address. Messages that are routed to the loopback interface can be re-routed to the switch and be handled locally. For messages that are routed to the loopback interface but whose destination is not the IP address of the loopback interface, they will be dropped. This means that the loopback interface functions as the null interface.
Run the following command in global configuration mode to specify a loopback interface and enter the interface configuration state:
Command Descriptionn in global configuration mode:
al configuration mode:
nfiguration mode:
interface loopbacknumbermand Description Enter the loopback interface configuration state.g vlan vlan_id immediate-leave n vlan_id immediate-leavelan_id$ immediate-leave
8.2.3.3 Configuring Aggregation Interface_id$ immediate-leave
The inadequate bandwidth of a single Ethernet interface gives rise to the birth of the aggregation interface. It can bind several full-duplex interfaces with the same rate together, greatly improving the bandwidth.
Run the following command to define the aggregation interface:
Command Descriptions to be found (DHL, the destination address is not registered in the switch chip through igmp-snooping), the default process method is to send message on all ports of VLAN. Through configuration, you can change the process method and all multicast messages whose destination addresses are not registered to any port will be dropped.
ound (DHL, the destination address is not registered in the switch chip through igmp-snooping), the default process method is to send message on all ports of VLAN. Through configuration, you can change the process method and all multicast messages whose destination addresses are not registered to any port will be dropped.
(DHL, the destination address is not registered in the switch chip through igmp-snooping), the default process method is to send message on all ports of VLAN. Through configuration, you can change the process method and all multicast messages whose destination addresses are not registered to any port will be dropped.
Interface port-aggregator numbered in the switch chip through igmp-snooping), the default process method is to send message on all ports of VLAN. Through configuration, you can change the process method and all multicast messages whose destination addresses are not registered to any port will be dropped.
Configures the aggregation interface the default process method is to send message on all ports of VLAN. Through configuration, you can change the process method and all multicast messages whose destination addresses are not registered to any port will be dropped.
default process method is to send message on all ports of VLAN. Through configuration, you can change the process method and all multicast messages whose destination addresses are not registered to any port will be dropped.
lt process method is to send message on all ports of VLAN. Through configuration, you can change the process method and all multicast messages whose destination addresses are not registered to any port will be dropped.
8.2.3.4 Configuring VLAN Interfacengdlf-framesfilter
V VLAN interface is the routing interface in switch. The VLAN command in global configuration mode only adds layer 2 VLAN to system without defining how to deal with the IP packet whose destination address is itself in the VLAN. If there is no VLAN interface, this kind of packets will be dropped.
Run the following command to define VLAN interface:
Command Descriptionage-timer-of-igmp-snooping"> -of-igmp-snooping">gmp-snooping"> Interface vlannumberg Router Age Timer of IGMP-snooping Configures VLAN interface.
The Router Age timer is used to monitor whether the IGMP inquirer exists. IGMP inquirers maintains multicast addresses by sending query message. IGMP-snooping works through communication between IGMP inquier and host.
Perform the following configuration in global configuration mode:
Router Age timer is used to monitor whether the IGMP inquirer exists. IGMP inquirers maintains multicast addresses by sending query message. IGMP-snooping works through communication between IGMP inquier and host.
Perform the following configuration in global configuration mode:
8.2.3.5 Configuring Super VLAN Interfacers maintains multicast addresses by sending query message. IGMP-snooping works through communication between IGMP inquier and host.
Perform the following configuration in global configuration mode:
The Super VLAN technology provides a mechanism: hosts in different VLANs of the same switch can be allocated in the same lpv4 subnet and use the same default gateway; lots of IP addresses are, therefore, saved. The Super VLAN technology puts different VLANs into a group where VLANs use the same management interface and hosts use the same IPv4 network section and gateway. VLAN belonging to Super VLAN is called as SubVLAN. No SubVLAN can possess the management interface by configuring IP address. You can configure a Super VLAN interface through a command line. The procedure of configuring a Super VLAN interface is shown as follows:
Command Descriptionn >> [no] interface supervlanindex-agetimer_value Enter the Super VLAN interface configuration mode. If the specified Super VLAN interface does not exist, the system will create a Super VLAN interface.index is the index of the Super VLAN interface. Its effective value ranges from 1 to 32.no means to delete Super VLAN interface.561.jpg)
For how to configure the timer, refer to the query period setup of IGMP inquirer. The timer cannot be set to be smaller than query period. It is recommended that the timer is set to three times of the query period.
The default value of Router Age of IGMP-snooping is 260 seconds.
pg)
For how to configure the timer, refer to the query period setup of IGMP inquirer. The timer cannot be set to be smaller than query period. It is recommended that the timer is set to three times of the query period.
The default value of Router Age of IGMP-snooping is 260 seconds.
[no] subvlan[setstr] [addaddstr][removeemstr]riod setup of IGMP inquirer. The timer cannot be set to be smaller than query period. It is recommended that the timer is set to three times of the query period.
The default value of Router Age of IGMP-snooping is 260 seconds.
Configure SubVLAN in Super VLAN. The added Sub VLAN cannot possess a management interface or cannot belong to other Super VLANs. In original state, Super VLAN does not contain any Sub VLAN. Only one sub command can only be used every time. setstr means to set the Sub VLAN list. For example, List 2,4-6 indicate VLAN 2, 4, 5 and 6. add means to add VLAN list in the original SubVLAN list. addstr means the character string whose format is the same as the above. remove means to delete VLAN list in the original SubVLAN list. remstr is the list's character string whose format is the same as the above. no means to delete all SubVLANs in SuperVLAN. The no command cannot be used with other sub commands.r>>ip igmp-snooping timerresponse-timetimer_value
After you configure the Super VLAN interface, you can configure the IP address for the Super VLAN interface.
The Super VLAN interface is also a routing port, which can be configured as other ports are.
8.3 Interface Configuration Example6-configuring-response-time-timer-of-igmp-snooping">
8.3.1 Configuring Public Attribute of Interfacemer of IGMP-Snooping
8.3.1.1 Interface Description Exampleast after IGMP inquirer sends the query message. If the report message is not received after the timer ages, the switch will delete the multicast address.
Perform the following configuration in global configuration mode:
The following example shows how to add description related to an interface. This description appears in the configuration file and interface command display.
interface vlan 1
ip address 192.168.1.23 255.255.255.0
8.3.1.2 Interface Shutdown Examplen will be unstable.
The value of Response Time of IGMP-snooping is set to ten seconds.
The following example shows how to shut down the Ethernet interface 0/1:
interface GigaEthernet0/1
shutdown
The following example shows how to enable the interface:
interface GigaEthernet0/1
no shutdown
9. Interface Range Configurationlticast router exists in VLAN; the function can be automatically activated when the multicast router times out.
9.1 Interface Range Configuration Tasktaining IGMP-Snooping
9.1.1 Understanding Interface RangeDescription
In the process of configuring interface tasks, there are cases when you have to configure the same attribute on ports of the same type. In order to avoid repeated configuration on each port, we provide the interface range configuration mode. You can configure ports of the same type and slot number with the same configuration parameters. This reduces the workload.
when entering the interface range mode, all interfaces included in this mode must have been established.
9.1.2 Entering Interface Range Mode
Run the following command to enter the interface range mode.
Stepspan="3"> Command Description-snooping groups groups ps1r> interface rangetypeslot/[,] Enters the range mode. All ports included in this mode accord to the following conditions:(1) The slot number is set to slot.(2) The port numbers before/after the hyphen must range between port1 and port2, or equal to port3.(3) Port 2 must be less than port 1(4) There must be space before/after the hyphen or the comma.
switch#show ip igmp-snooping statistics
vlan 1
v1_packets: 0 IGMP v1 packet number
v2_packets: 6 IGMP v2 packet number
v3_packets: 0 IGMP v3 packet number
general_query_packets: 5 General query of the packet number
special_query_packets: 0 Special query of the packet number
join_packets: 6 Number of report packets
leave_packets: 0 Number of Leave packets
send_query_packets: 0 Rserved statistics option
err_packets: 0 Number of incorrect packets
Debug the message timer of IGMP-snooping:
switch#debug ip igmp-snooping packet
rx: s_ip: 90.0.0.3, d_ip: 224.0.8.9 Source and destination IP addresses where packets are received
type: 16(V2-Report), max resp: 00, group address: 224.0.8.9 Type and content of packet
rx: s_ip: 90.0.0.90, d_ip: 224.0.0.1
type: 11(Query), max resp: 64, group address: 0.0.0.0
rx: s_ip: 90.0.0.3, d_ip: 224.0.8.9
type: 16(V2-Report), max resp: 00, group address: 224.0.8.9
rx: s_ip: 90.0.0.3, d_ip: 224.0.0.2
type: 17(V2-Leave), max resp: 00, group address: 224.0.8.9
rx: s_ip: 90.0.0.90, d_ip: 224.0.8.9
type: 11(Query), max resp: 0a, group address: 224.0.8.9
Debug the message timer of IGMP-snooping:
switch#debug ip igmp-snooping timer
tm: vlan 1 igmp router age expiry at port 2(F0/2)
tm: multicast item 0.0.0.0->224.0.8.9(0100.5e00.0809) response time expiry at port F0/4 Inquiring the response timer expiry
switch#show ip igmp-snooping statistics
vlan 1
v1_packets: 0 IGMP v1 packet number
v2_packets: 6 IGMP v2 packet number
v3_packets: 0 IGMP v3 packet number
general_query_packets: 5 General query of the packet number
special_query_packets: 0 Special query of the packet number
join_packets: 6 Number of report packets
leave_packets: 0 Number of Leave packets
send_query_packets: 0 Rserved statistics option
err_packets: 0 Number of incorrect packets
Debug the message timer of IGMP-snooping:
switch#debug ip igmp-snooping packet
rx: s_ip: 90.0.0.3, d_ip: 224.0.8.9 Source and destination IP addresses where packets are received
type: 16(V2-Report), max resp: 00, group address: 224.0.8.9 Type and content of packet
rx: s_ip: 90.0.0.90, d_ip: 224.0.0.1
type: 11(Query), max resp: 64, group address: 0.0.0.0
rx: s_ip: 90.0.0.3, d_ip: 224.0.8.9
type: 16(V2-Report), max resp: 00, group address: 224.0.8.9
rx: s_ip: 90.0.0.3, d_ip: 224.0.0.2
type: 17(V2-Leave), max resp: 00, group address: 224.0.8.9
rx: s_ip: 90.0.0.90, d_ip: 224.0.8.9
type: 11(Query), max resp: 0a, group address: 224.0.8.9
Debug the message timer of IGMP-snooping:
switch#debug ip igmp-snooping timer
tm: vlan 1 igmp router age expiry at port 2(F0/2)
tm: multicast item 0.0.0.0->224.0.8.9(0100.5e00.0809) response time expiry at port F0/4 Inquiring the response timer expiry
zdk:49
Debug the message timer of IGMP-snooping:
switch#debug ip igmp-snooping packet
rx: s_ip: 90.0.0.3, d_ip: 224.0.8.9 Source and destination IP addresses where packets are received
type: 16(V2-Report), max resp: 00, group address: 224.0.8.9 Type and content of packet
rx: s_ip: 90.0.0.90, d_ip: 224.0.0.1
type: 11(Query), max resp: 64, group address: 0.0.0.0
rx: s_ip: 90.0.0.3, d_ip: 224.0.8.9
type: 16(V2-Report), max resp: 00, group address: 224.0.8.9
rx: s_ip: 90.0.0.3, d_ip: 224.0.0.2
type: 17(V2-Leave), max resp: 00, group address: 224.0.8.9
rx: s_ip: 90.0.0.90, d_ip: 224.0.8.9
type: 11(Query), max resp: 0a, group address: 224.0.8.9
Debug the message timer of IGMP-snooping:
switch#debug ip igmp-snooping timer
tm: vlan 1 igmp router age expiry at port 2(F0/2)
tm: multicast item 0.0.0.0->224.0.8.9(0100.5e00.0809) response time expiry at port F0/4 Inquiring the response timer expiry
9.1.3 Configuration Examplemer:
Enter the interface configuration mode via the following commands, including slot 0 and fast Ethernet 1,2,3,6,8,10,11,12:
switch_config#interface range 1 - 3, 6, 8, 10 - 12
switch_config_if_range#
10. Port Physical Characteristics Configurationhzdk:50
Debug the message timer of IGMP-snooping:
switch#debug ip igmp-snooping timer
tm: vlan 1 igmp router age expiry at port 2(F0/2)
tm: multicast item 0.0.0.0->224.0.8.9(0100.5e00.0809) response time expiry at port F0/4 Inquiring the response timer expiry
10.1Configuring the Ethernet Interface message timer of IGMP-snooping:
switch#debug ip igmp-snooping timer
tm: vlan 1 igmp router age expiry at port 2(F0/2)
tm: multicast item 0.0.0.0->224.0.8.9(0100.5e00.0809) response time expiry at port F0/4 Inquiring the response timer expiry
The section describes how to configure the Ethernet interface. The switch supports the 10Mbps Ethernet and the 100Mbps fastEthernet. The detailed configuration is shown as follows. The step described in section 1.1.1
is mandatory. Steps described in other sections are optional.
10.1.1 Selecting Ethernet Interfacegmp-snooping-configuration-example">
Run the following command in global configuration mode to enter the Ethernet interface configuration mode:
Run... To...9-igmp-snooping-configuration-example"> ooping-configuration-example">g-configuration-example"> interface fastethernet [slot/port] Configuration Example Enter the fastEthernet interface configuration modeon of the example.
the example.
interface gigaethernet [slot/port]41a5ec8414f28353c6f653e79d216ac9c5d9aca9348ed.jpg)
Enter the gigabit Ethernet interface configuration mode.mmary>>chart
You can run the show interface fastethernet command to display the state of fastEthernet interface. You can run the show interface gigaethernet command to display the state of the gigabit Ethernet interface.
10.1.2 Configuring Rate
The Ethernet rate can be realized through auto-negotiation or configuration on the interface.
Run the following command to configure the Ethernet rate:
Run... To...
Configuring Switch
(1) Enable IGMP-snooping of VLAN 1 connecting Private Network A.
Switch\_config#ip igmp-snooping vlan 1
(2) Enable IGMP-snooping of VLAN 2 connecting Private Network B.
Switch\_config#ip igmp-snooping vlan 2
ing Switch
(1) Enable IGMP-snooping of VLAN 1 connecting Private Network A.
Switch\_config#ip igmp-snooping vlan 1
(2) Enable IGMP-snooping of VLAN 2 connecting Private Network B.
Switch\_config#ip igmp-snooping vlan 2
witch
(1) Enable IGMP-snooping of VLAN 1 connecting Private Network A.
Switch\_config#ip igmp-snooping vlan 1
(2) Enable IGMP-snooping of VLAN 2 connecting Private Network B.
Switch\_config#ip igmp-snooping vlan 2
Speed {10|100|1000|auto}AN 1 connecting Private Network A.
Switch\_config#ip igmp-snooping vlan 1
(2) Enable IGMP-snooping of VLAN 2 connecting Private Network B.
Switch\_config#ip igmp-snooping vlan 2
Set the rate of fast Ethernet to 10M, 100M, 1000M or auto-negotiation.2) Enable IGMP-snooping of VLAN 2 connecting Private Network B.
Switch\_config#ip igmp-snooping vlan 2
able IGMP-snooping of VLAN 2 connecting Private Network B.
Switch\_config#ip igmp-snooping vlan 2
No speed VLAN 2 connecting Private Network B.
Switch\_config#ip igmp-snooping vlan 2
Resume the default settings—auto-negotiation.ip igmp-snooping vlan 2
mp-snooping vlan 2
ooping vlan 2
The Ethernet rate can be realized through auto-negotiation or configuration on the interface.
Run the following command to configure the Ethernet rate:
Run... To...
Configuring Switch
(1) Enable IGMP-snooping of VLAN 1 connecting Private Network A.
Switch\_config#ip igmp-snooping vlan 1
(2) Enable IGMP-snooping of VLAN 2 connecting Private Network B.
Switch\_config#ip igmp-snooping vlan 2
ing Switch
(1) Enable IGMP-snooping of VLAN 1 connecting Private Network A.
Switch\_config#ip igmp-snooping vlan 1
(2) Enable IGMP-snooping of VLAN 2 connecting Private Network B.
Switch\_config#ip igmp-snooping vlan 2
witch
(1) Enable IGMP-snooping of VLAN 1 connecting Private Network A.
Switch\_config#ip igmp-snooping vlan 1
(2) Enable IGMP-snooping of VLAN 2 connecting Private Network B.
Switch\_config#ip igmp-snooping vlan 2
Speed {10|100|1000|auto}AN 1 connecting Private Network A.
Switch\_config#ip igmp-snooping vlan 1
(2) Enable IGMP-snooping of VLAN 2 connecting Private Network B.
Switch\_config#ip igmp-snooping vlan 2
Set the rate of fast Ethernet to 10M, 100M, 1000M or auto-negotiation.2) Enable IGMP-snooping of VLAN 2 connecting Private Network B.
Switch\_config#ip igmp-snooping vlan 2
able IGMP-snooping of VLAN 2 connecting Private Network B.
Switch\_config#ip igmp-snooping vlan 2
No speed VLAN 2 connecting Private Network B.
Switch\_config#ip igmp-snooping vlan 2
Resume the default settings—auto-negotiation.ip igmp-snooping vlan 2
mp-snooping vlan 2
ooping vlan 2 - 1](/content/2026/05/900918/images/1301a91cfe3776480c90a11672ac27e2ca955c6994088d9437bb5f3b5773a749.jpg)
The speed of the optical interface is fixed. For example, the rate of GBIC and GE-FX is 1000M; the rate of FE-FX is 100M. If the auto parameter is behind the speed command, it means that you can enable the auto-negotiation function on the optical interface. Otherwise, you cannot enable the auto-negotiation function on the optical interface.
10.1.3 Configuring Flow Control on the Interfacep igmp-snooping vlan 1
(2) Enable IGMP-snooping of VLAN 2 connecting Private Network B.
Switch\_config#ip igmp-snooping vlan 2
When the interface is in full-duplex mode, the flow control is achieved through the PAUSE frame defined by 802.3X. When the interface is in half-duplex mode, the flow control is achieved through back pressure.
Run... To...f VLAN 2 connecting Private Network B.
Switch\_config#ip igmp-snooping vlan 2
connecting Private Network B.
Switch\_config#ip igmp-snooping vlan 2
cting Private Network B.
Switch\_config#ip igmp-snooping vlan 2
flow-control on/off\_config#ip igmp-snooping vlan 2
Enable or disable the flow control on the interface.guration">ion"> no flow-controlation Resume the default settings.The default settings have no flow control.
id="31111-igmp-proxy-configuration-tasks">
11. Port Additional Characteristics Configuration/h1>
11.1 Configuring the Ethernet Interfacemp-proxy-configuration">
The switch supports the 10Mbps/100Mbps Ethernet interfaces. See the following content for detailed configuration. Among the configuration, the first step is mandatory while others are optional.
11.1.1 Configuring Flow Control for the Port IGMP Proxy allows the VLAN where the multicast user is located to receive the multicast source from other VLANs. The IGMP Proxy runs on layer 2 independently without other multicast routing protocols. IGMP proxy will be transmitted by the IGMP packets of the proxied VLAN to the proxying VLAN and maintain the hardware forward table of the multicast user of the agent VLAN according to these IGMP packets. IGMP proxy divides different VLANs into two kinds: proxied VLANs and proxying VLANs. The downstream multicast VLANs can be set to the proxied VLANs, while the upstream multicast VLANs can be set to the proxying VLANs.
Although IGMP proxy is based on IGMP snooping, two are independent in application; IGMP Snooping will not be affected when IGMP proxy is enabled or disabled, while IGMP proxy can run only when IGMP Snooping is enabled.
IGMP proxy cannot be used unless the following conditions are met:
(1) L3 switch
(2) Avoiding to enable IP multicast routing at the same time
(3) Preventing a vlan to act as downstream vlan and also upstream vlan
● Enabling/Disabling IGMP-Proxy
- Adding/deleting VLAN agent relationship
- Adding/deleting static multicast source entries
● Monitoring and Maintaining IGMP-Proxy
- Setting the Example of IGMP Proxy
You can control the flow rate on the incoming and outgoing ports through configuration.
Run the following commands in previliged mode to limit the flow rate of the port.
Each band is defaulted as 128 kbps.
Command Purpose to enable IP multicast routing at the same time
(3) Preventing a vlan to act as downstream vlan and also upstream vlan
● Enabling/Disabling IGMP-Proxy
- Adding/deleting VLAN agent relationship
- Adding/deleting static multicast source entries
● Monitoring and Maintaining IGMP-Proxy
- Setting the Example of IGMP Proxy
e IP multicast routing at the same time
(3) Preventing a vlan to act as downstream vlan and also upstream vlan
● Enabling/Disabling IGMP-Proxy
- Adding/deleting VLAN agent relationship
- Adding/deleting static multicast source entries
● Monitoring and Maintaining IGMP-Proxy
- Setting the Example of IGMP Proxy
multicast routing at the same time
(3) Preventing a vlan to act as downstream vlan and also upstream vlan
● Enabling/Disabling IGMP-Proxy
- Adding/deleting VLAN agent relationship
- Adding/deleting static multicast source entries
● Monitoring and Maintaining IGMP-Proxy
- Setting the Example of IGMP Proxy
configurehe same time
(3) Preventing a vlan to act as downstream vlan and also upstream vlan
● Enabling/Disabling IGMP-Proxy
- Adding/deleting VLAN agent relationship
- Adding/deleting static multicast source entries
● Monitoring and Maintaining IGMP-Proxy
- Setting the Example of IGMP Proxy
Enters the global configuration mode.s downstream vlan and also upstream vlan
● Enabling/Disabling IGMP-Proxy
- Adding/deleting VLAN agent relationship
- Adding/deleting static multicast source entries
● Monitoring and Maintaining IGMP-Proxy
- Setting the Example of IGMP Proxy
nstream vlan and also upstream vlan
● Enabling/Disabling IGMP-Proxy
- Adding/deleting VLAN agent relationship
- Adding/deleting static multicast source entries
● Monitoring and Maintaining IGMP-Proxy
- Setting the Example of IGMP Proxy
interface f1/0eam vlan
● Enabling/Disabling IGMP-Proxy
- Adding/deleting VLAN agent relationship
- Adding/deleting static multicast source entries
● Monitoring and Maintaining IGMP-Proxy
- Setting the Example of IGMP Proxy
Enters the to-be-configured port.
- Adding/deleting VLAN agent relationship
- Adding/deleting static multicast source entries
● Monitoring and Maintaining IGMP-Proxy
- Setting the Example of IGMP Proxy
Adding/deleting VLAN agent relationship
- Adding/deleting static multicast source entries
● Monitoring and Maintaining IGMP-Proxy
- Setting the Example of IGMP Proxy
Interface Type1
---
Expiration time: 44
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 1
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udld interface f0/1
Interface FastEthernet0/1
...
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
evice index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 1
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udld interface f0/1
Interface FastEthernet0/1
...
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
Ethernet interface6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 1
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udld interface f0/1
Interface FastEthernet0/1
...
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
|
al: 1
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udld interface f0/1
Interface FastEthernet0/1
...
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
Logical InterfaceSwitch\_config#
Switch\_config#show udld interface f0/1
Interface FastEthernet0/1
...
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
|
rational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
Aggregation interfacesage interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
|
1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
|
The two supported kinds of interface: Ethernet interface and logical interface. The Ethernet interface type depends on one device depends on the standard communication interface and the interface card or interfaced module installed on the switch. The logical interface is the interface without the corresponding physical device, which is established by user manually.
The supported Ethernet interfaces of our switch include:
- Ethernet interface
- Fast Ethernet interface
• Gigabit Ethernet interface
● The supported logical interface of our switch include: - loopback interface
- null interface
- aggregation interface
- vlan interface
8.1.2 Interface Configuration Introductionrval: 15
Time out interval: 1
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udld interface f0/1
Interface FastEthernet0/1
...
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Unknown
Current operational state: Advertisement
Message interval: 15
Time out interval: 7
Entry 1
---
Expiration time: 43
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 7
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
Switch\_config#show udd interface f0/1
Interface FastEthernet0/1
---
Port enable administrative configuration setting: Enabled
Port enable operational state: Enabled
Current bidirectional state: Bidirectional
Current operational state: Advertisement
Message interval: 15
Time out interval: 15
Entry 1
...
Expiration time: 36
Cache Device index: 1
Device ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
The following description applies to the configuration process of all interfaces. Take the following steps to perform interface configuration in global configuration mode.
(1) Run the interface command to enter the interface configuration mode and start configuring interface. At this time, the switch prompt becomes 'config_' plus the shortened form of the interface to be configured. Use these interfaces in terms of their numbers. Numbers are assigned during installation(exworks) or when an interface card are added to the system. Run the show interface command to display these interfaces. Each interface that the device supports provides its own state as follows:
Switch#show interface
GigaEthernet1/1 is down, line protocol is down
Hardware is Fast Ethernet, Address is 0009.7cf7.7dc1
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Auto-duplex, Auto-speed
input flow-control is off, output flow-control is off
ARP type: ARPA, ARP Timeout 04: 00: 00
Last input never, output 17: 52: 52, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue : 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1 packets input, 64 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
1 packets output, 64 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out
To configure gigabit Ethernet interface g1/1, enter the following content:
interface GigaEthernet0/1
The switch prompts "config_g1/1".
There is no need to add blank between interface type and interface number. For example, in the above line, g 1/1 or g 1/1 is both rights.
(1) You can configure the interface configuration commands in interface
configuration mode. Various commands define protocols and application programs to be executed on the interface. These commands will stay until user exits the interface configuration mode or switches to another interface.
(2) Once the interface configuration has been completed, use the show command in the following chapter 'Monitoring and Maintaining Interface' to test the interface state.
8.2 Interface Configuratione ID: XGS-6350-12X8TR
Port ID: FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
8.2.1 Configuring Interface Common Attributeet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
8.2.1 Configuring Interface Common Attributeet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
The following content describes the command that can be executed on an interface of any type and configures common attributes of interface. The common attributes of interface that can be configured include: interface description, bandwidth and delay and so on.
8.2.1.1 Adding Description FastEthernet0/1
Neighbor echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
Adding description about the related interface helps to memorize content attached to the interface. This description only serves as the interface note to help identify uses of the interface and has no effect on any feature of the interface. This description will appear in the output of the following commands: show running-config and show interface. Use the following command in interface configuration mode if user wants to add a description to any interface.
Command Description echo 1 device: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
: XGS-6350-12X8TR
Neighbor echo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
description stringo 1 port: FastEthernet0/1
Message interval: 15
Time out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
|
5
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
|
For examples relevant to adding interface description, please refer to the following section 'Interface Description Example'.
8.2.1.2 Configuring Bandwidth out interval: 15
UDLD Device name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
The upper protocol uses bandwidth information to perform operation decision. Use the following command to configure bandwidth for the interface:
Command Description name: XGS-6350-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
0-12X8TR
Switch\_config#
From the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
bandwidthkilobpsom the information above, you can find the three phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
|
which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
|
The bandwidth is just a routing parameter, which doesn't influence the communication rate of the actual physical interface.
8.2.1.3 Configuring Time Delay phases of the link state which UDLD detects:
Detection phase: In this phase, the UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
The upper protocol uses time delay information to perform operation decision. Use the following command to configure time delay for the interface in the interface configuration mode.
Command Descriptione UDLD packets are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
are transmitted every other second.
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
delaytensofmicroseconds
Unknown phase: In this phase, the UDLD packets are transmitted every eight seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
|
t seconds.
Known bidirectional/unidirectional connection phase: Once a link is established and labeled as bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
|
The configuration of time delay is just an information parameter. Use this command cannot adjust the actual time delay of an interface.
8.2.2 Monitoring and Maintaining Interfaceas bidirectional, UDLD will transmit a probe/echo message every 16 seconds.
The following tasks can monitor and maintain interface:
- Checking interface state
- Initializing and deleting interface
● Shutting down and enabling interface
8.2.2.1 Checking Interface State and group address and to update simultaneously with the multicast changes, enabling layer-2 switches to forward data according to the topology structure of the multicast group.
The main functions of IGMP-snooping are shown as follows:
● Listening IGMP message;
- Maintaining the relationship table between VLAN and group address;
- Keeping the IGMP entity of host and the IGMP entity of router in the same state to prevent flooding from occurring.
Because igmp-snooping realizes the above functions by listening the query message and report message of igmp, igmp-snooping can function properly only
when it works on the multicast router, that is, the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
Our switch supports displaying several commands related to interface information, including version number of software and hardware, interface state. The following table lists a portion of interface monitor commands. For the description of these commands, please refer to 'Interface configuration command'.
Use the following commands:
Command Descriptionand the IGMP entity of router in the same state to prevent flooding from occurring.
Because igmp-snooping realizes the above functions by listening the query message and report message of igmp, igmp-snooping can function properly only
when it works on the multicast router, that is, the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
ntity of router in the same state to prevent flooding from occurring.
Because igmp-snooping realizes the above functions by listening the query message and report message of igmp, igmp-snooping can function properly only
when it works on the multicast router, that is, the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
show interface [type [slot|port]]looding from occurring.
Because igmp-snooping realizes the above functions by listening the query message and report message of igmp, igmp-snooping can function properly only
when it works on the multicast router, that is, the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
|
nooping realizes the above functions by listening the query message and report message of igmp, igmp-snooping can function properly only
when it works on the multicast router, that is, the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
show running-configions by listening the query message and report message of igmp, igmp-snooping can function properly only
when it works on the multicast router, that is, the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
|
t message of igmp, igmp-snooping can function properly only
when it works on the multicast router, that is, the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
|
You can dynamically establish and delete logical interfaces. This also applies to the sub interface and channalized interface. Use the following command to initialize and delete interface in global configuration mode:
Command Descriptionter, that is, the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
the switch must periodically receive the igmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
no interface type [slot/port]gmp query information from the router. The router age timer of igmp-snooping must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
|
ng must be set to a time value that is bigger than the group query period of the multicast router connecting igmp-snooping. You can check the multicast router information in each VLAN by running show ip igmp-snooping.
● Enabling/Disabling IGMP-snooping of VLAN
- Adding/Deleting static multicast address of VLAN
- Configuring immediate-leave of VLAN
- Configuring the function to filter multicast message without registered destination address
- Configuring the Router Age timer of IGMP-snooping
- Configuring the Response Time timer of IGMP-snooping
- Configuring IGMP Querier of IGMP-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
|
When an interface is shut down, all features of this interface are disabled, and also this interface is marked as unavailable interface in all monitor command displays. This information can be transmitted to other switches via dynamic routing protocol.
Use the following command to shutdown or enable an interface in the interface configuration mode:
Command Description-snooping
● Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
Monitoring and maintaining IGMP-snooping
- IGMP-snooping configuration example
shutdown Shuts down an interface. IGMP-snooping configuration example
|
configuration example
no shutdown |
You can use the show interface command and the show running-config command to check whether an interface has been shut down. An interface that has been shut down is displayed as 'administratively down' in the show interface command display. For more details, please refer to the following example in 'Interface Shutdown Example'. 8.2.3 Configuring Logistical InterfaceGMP-Snooping of VLANThis section describes how to configure a logical interface. The contents are as follows:
8.2.3.1 Configuring Null Interfacec4f18d51441398e7.jpg)
IGMP-snooping can run on up to 16 VLANs.
To enable IGMP-snooping on VLAN3, you must first run no ip IGMP-snooping to disable IGMP-snooping of all VLANs, then configure ipIGMP-snooping VLAN 3 and save configuration.
The whole system supports only one null interface. Its functions are similar to those of applied null devices on most operating systems. The null interface is always available, but it never sends or receives communication information. The interface configuration command no ip unreachable is the only one command available to the null interface. The null interface provides an optional method to filtrate communication. That is, the unwanted network communication can be routed to the null interface; the null interface can function as the access control list. You can run the following command in global configuration mode to specify the null interface:
|
The null interface can be applied in any command that takes the interface type as its parameter.
The following case shows how to configure a null interface for the routing of IP 192.168.20.0.
ip route 192.168.20.0 255.255.255.0 null 0
8.2.3.2 Configuring Loopback Interfacean_id staticA.B.C.D interfaceintf
The loopback interface is a logistical interface. It always functions and continues BGP session even in the case that the outward interface is shut down. The loopback interface can be used as the terminal address for BGP session. If other switches try to reach the loopback interface, a dynamic routing protocol should be configured to broadcast the routes with loopback interface address. Messages that are routed to the loopback interface can be re-routed to the switch and be handled locally. For messages that are routed to the loopback interface but whose destination is not the IP address of the loopback interface, they will be dropped. This means that the loopback interface functions as the null interface.
Run the following command in global configuration mode to specify a loopback interface and enter the interface configuration state:
Command Descriptionn in global configuration mode:
|
The speed of the optical interface is fixed. For example, the rate of GBIC and GE-FX is 1000M; the rate of FE-FX is 100M. If the auto parameter is behind the speed command, it means that you can enable the auto-negotiation function on the optical interface. Otherwise, you cannot enable the auto-negotiation function on the optical interface.
10.1.3 Configuring Flow Control on the Interfacep igmp-snooping vlan 1
(2) Enable IGMP-snooping of VLAN 2 connecting Private Network B.
Switch\_config#ip igmp-snooping vlan 2
When the interface is in full-duplex mode, the flow control is achieved through the PAUSE frame defined by 802.3X. When the interface is in half-duplex mode, the flow control is achieved through back pressure.
Run... To...f VLAN 2 connecting Private Network B.
Switch\_config#ip igmp-snooping vlan 2
cting Private Network B.
Switch\_config#ip igmp-snooping vlan 2
flow-control on/off\_config#ip igmp-snooping vlan 2
|
|
id="31111-igmp-proxy-configuration-tasks">
11. Port Additional Characteristics Configuration/h1>
11.1 Configuring the Ethernet Interfacemp-proxy-configuration">
11.1 Configuring the Ethernet Interfacemp-proxy-configuration">
The switch supports the 10Mbps/100Mbps Ethernet interfaces. See the following content for detailed configuration. Among the configuration, the first step is mandatory while others are optional.
11.1.1 Configuring Flow Control for the Port IGMP Proxy allows the VLAN where the multicast user is located to receive the multicast source from other VLANs. The IGMP Proxy runs on layer 2 independently without other multicast routing protocols. IGMP proxy will be transmitted by the IGMP packets of the proxied VLAN to the proxying VLAN and maintain the hardware forward table of the multicast user of the agent VLAN according to these IGMP packets. IGMP proxy divides different VLANs into two kinds: proxied VLANs and proxying VLANs. The downstream multicast VLANs can be set to the proxied VLANs, while the upstream multicast VLANs can be set to the proxying VLANs.
Although IGMP proxy is based on IGMP snooping, two are independent in application; IGMP Snooping will not be affected when IGMP proxy is enabled or disabled, while IGMP proxy can run only when IGMP Snooping is enabled.
IGMP proxy cannot be used unless the following conditions are met:
(1) L3 switch
(2) Avoiding to enable IP multicast routing at the same time
(3) Preventing a vlan to act as downstream vlan and also upstream vlan
● Enabling/Disabling IGMP-Proxy
- Adding/deleting VLAN agent relationship
- Adding/deleting static multicast source entries
● Monitoring and Maintaining IGMP-Proxy
- Setting the Example of IGMP Proxy
You can control the flow rate on the incoming and outgoing ports through configuration.
Run the following commands in previliged mode to limit the flow rate of the port.
Each band is defaulted as 128 kbps.
Command Purpose to enable IP multicast routing at the same time
(3) Preventing a vlan to act as downstream vlan and also upstream vlan
● Enabling/Disabling IGMP-Proxy
- Adding/deleting VLAN agent relationship
- Adding/deleting static multicast source entries
● Monitoring and Maintaining IGMP-Proxy
- Setting the Example of IGMP Proxy
multicast routing at the same time
(3) Preventing a vlan to act as downstream vlan and also upstream vlan
● Enabling/Disabling IGMP-Proxy
- Adding/deleting VLAN agent relationship
- Adding/deleting static multicast source entries
● Monitoring and Maintaining IGMP-Proxy
- Setting the Example of IGMP Proxy
configurehe same time
(3) Preventing a vlan to act as downstream vlan and also upstream vlan
● Enabling/Disabling IGMP-Proxy
- Adding/deleting VLAN agent relationship
- Adding/deleting static multicast source entries
● Monitoring and Maintaining IGMP-Proxy
- Setting the Example of IGMP Proxy
|
nstream vlan and also upstream vlan
● Enabling/Disabling IGMP-Proxy
- Adding/deleting VLAN agent relationship
- Adding/deleting static multicast source entries
● Monitoring and Maintaining IGMP-Proxy
- Setting the Example of IGMP Proxy
interface f1/0eam vlan
● Enabling/Disabling IGMP-Proxy
- Adding/deleting VLAN agent relationship
- Adding/deleting static multicast source entries
● Monitoring and Maintaining IGMP-Proxy
- Setting the Example of IGMP Proxy
|
Adding/deleting VLAN agent relationship - Adding/deleting static multicast source entries ● Monitoring and Maintaining IGMP-Proxy - Setting the Example of IGMP Proxy |