Home » TP-Link Manuals » Hubs & Switches » TP-Link T1700G-28TQ » Manual Viewer

TP-Link T1700G-28TQ T1700G-28TQ V1 User Guide - Page 60

Stack Maintenance

View all TP-Link T1700G-28TQ manuals

Add to My Manuals
Save this manual to your list of manuals

Page 60 highlights

the interfaces associated with the switch that is not currently a member of the stack. The configuration you create on the stack is defined as the provisioned configuration. The switch that associated with the provisioned configuration is called the provisioned member. Provisioned Configuration: The unit number, switch type and interface information which are defined for switches not in the stack. The information of the provisioned member is manually created, or created/updated by the switch member when it joins the stack. The provisioned configuration retains in the stack when the stack member leaves the stack. You can delete the associated provisioned configuration manually. One of the benefits of provisioning mechanism is that: if a stack member fails and you replace it with an identical model, the replacement switch will function with exactly the same configuration as the failed switch, assuming that the new switch is using the same member number as the replaced switch. When you add a switch to the switch stack, the stack will allocate a unit ID to the new switch as rules described in Unit Number, and then the new switch will apply either the provisioned configuration or the default configuration. Table 5-1 lists the events that occur when the switch stack compares the provisioned configuration with the new switch member. Scenario Event The unit number and the device type match The switch stack applies the provisioned configuration to the new switch. The unit number matches but the device The switch stack applies the default type doesn't match configuration to the new switch. The provisioned configuration is updated to the configuration of the new switch. The unit number is not found in the The switch stack applies the default provisioned configuration configuration to the new switch. The provisioned configuration is created as the configuration of the new switch. Table 5-1 Scenario of a New Member Joins the Stack • Stack Maintenance Stack maintenance mainly functions to monitor the join and leave of member devices, collect the new topology at any times and maintain the current topology. When the stack is operating normally, packets are transmitted constantly between stack members. The switch can quickly judge the link status of the stack port via monitoring the response of the packets. When the switch detects the link status changes, it will recollect system topology and update topology database to ensure the normal operation of the stack. The events that will change the link status of the stack port which thus affecting the system topology include: stack member failure or leave, new member's coming, link failure or failure recovery, etc. When the master switch fails, the stack system elects a new master from the remaining members to succeed the previous master. 50

Section	Page
Package Contents	11
Chapter 1 About this Guide	12
1.1 Intended Readers	12
1.2 Conventions	12
1.3 Overview of This Guide	12
Chapter 2 Introduction	16
2.1 Overview of the Switch	16
2.2 Appearance Description	16
2.2.1 Front Panel	16
2.2.2 Rear Panel	17
Chapter 3 Login to the Switch	19
3.1 Login	19
3.2 Configuration	20
Chapter 4 System	21
4.1 System Info	21
4.1.1 System Summary	21
4.1.2 Device Description	24
4.1.3 System Time	24
4.1.4 Daylight Saving Time	25
4.1.5 System IPv6	26
4.2 User Management	35
4.2.1 User Table	35
4.2.2 User Config	35
4.3 System Tools	36
4.3.1 Boot Config	37
4.3.2 Config Restore	38
4.3.3 Config Backup	38
4.3.4 Firmware Upgrade	39
4.3.5 System Reboot	39
4.3.6 System Reset	40
4.4 Access Security	40
4.4.1 Access Control	40
4.4.2 HTTP Config	42
4.4.3 HTTPS Config	42
4.4.4 SSH Config	45
4.4.5 Telnet Config	52
4.5 SDM Template	52
4.5.1 SDM Template Config	52
Chapter 5 Stack	54
5.1 Stack Management	61
5.1.1 Stack Info	61
5.1.2 Stack Config	62
5.2 Application Example for Stack	64
Chapter 6 Switching	65
6.1 Port	65
6.1.1 Port Config	65
6.1.2 Port Mirror	66
6.1.3 Port Security	68
6.1.4 Port Isolation	70
6.1.5 Loopback Detection	71
6.2 LAG	73
6.2.1 LAG Table	74
6.2.2 Static LAG	75
6.2.3 LACP Config	76
6.3 Traffic Monitor	78
6.3.1 Traffic Summary	78
6.3.2 Traffic Statistics	79
6.4 MAC Address	81
6.4.1 Address Table	82
6.4.2 Static Address	83
6.4.3 Dynamic Address	84
6.4.4 Filtering Address	86
Chapter 7 VLAN	88
7.1 802.1Q VLAN	89
7.1.1 VLAN Config	90
7.1.2 Port Config	91
7.2 Application Example for 802.1Q VLAN	93
7.3 MAC VLAN	94
7.3.1 MAC VLAN	95
7.3.2 Port Enable	95
7.4 Application Example for MAC VLAN	96
7.5 Protocol VLAN	98
7.5.1 Protocol Group Table	99
7.5.2 Protocol Group	99
7.5.3 Protocol Template	100
7.6 Application Example for Protocol VLAN	102
Chapter 8 Spanning Tree	104
8.1 STP Config	109
8.1.1 STP Config	109
8.1.2 STP Summary	111
8.2 Port Config	112
8.3 MSTP Instance	113
8.3.1 Region Config	114
8.3.2 Instance Config	114
8.3.3 Instance Port Config	115
8.4 STP Security	117
8.4.1 Port Protect	117
8.4.2 TC Protect	120
8.5 Application Example for STP Function	120
Chapter 9 Multicast	125
9.1 IGMP Snooping	129
9.1.1 Snooping Config	131
9.1.2 Port Config	133
9.1.3 VLAN Config	134
9.1.4 Multicast VLAN	135
9.1.5 Querier Config	138
9.1.6 Profile Config	140
9.1.7 Profile Binding	141
9.1.8 Packet Statistics	143
9.2 MLD Snooping	144
9.2.1 Snooping Config	146
9.2.2 Port Config	148
9.2.3 VLAN Config	149
9.2.4 Multicast VLAN	150
9.2.5 Querier Config	151
9.2.6 Profile Config	153
9.2.7 Profile Binding	154
9.2.8 Packet Statistics	156
9.3 Multicast Table	157
9.3.1 IPv4 Multicast Table	157
9.3.2 Static IPv4 Multicast Table	158
9.3.3 IPv6 Multicast Table	159
9.3.4 Static IPv6 Multicast Table	160
Chapter 10 Routing	162
10.1 Interface	162
10.2 Routing Table	165
10.3 Static Routing	166
10.4 ARP	167
10.4.1 ARP Table	167
10.4.2 Static ARP	167
Chapter 11 QoS	169
11.1 DiffServ	172
11.1.1 Port Priority	172
11.1.2 Schedule Mode	173
11.1.3 802.1P Priority	174
11.1.4 DSCP Priority	175
11.2 Bandwidth Control	177
11.2.1 Rate Limit	177
11.2.2 Storm Control	178
11.3 Voice VLAN	179
11.3.1 Global Config	181
11.3.2 Port Config	182
11.3.3 OUI Config	183
Chapter 12 ACL	185
12.1 Time-Range	185
12.1.1 Time-Range Summary	185
12.1.2 Time-Range Create	186
12.1.3 Holiday Config	187
12.2 ACL Config	187
12.2.1 ACL Summary	187
12.2.2 ACL Create	188
12.2.3 MAC ACL	188
12.2.4 Standard-IP ACL	189
12.2.5 Extend-IP ACL	190
12.3 Policy Config	191
12.3.1 Policy Summary	191
12.3.2 Policy Create	191
12.3.3 Action Create	192
12.4 ACL Binding	192
12.4.1 Binding Table	193
12.4.2 Port Binding	194
12.4.3 VLAN Binding	195
12.5 Policy Binding	195
12.5.1 Binding Table	196
12.5.2 Port Binding	197
12.5.3 VLAN Binding	198
12.6 Application Example for ACL	198
Chapter 13 Network Security	201
13.1 IP-MAC Binding	201
13.1.1 Binding Table	201
13.1.2 Manual Binding	202
13.1.3 ARP Scanning	204
13.2 DHCP Snooping	206
13.2.1 Global Config	209
13.2.2 Port Config	210
13.3 ARP Inspection	211
13.3.1 ARP Detect	215
13.3.2 ARP Defend	216
13.3.3 ARP Statistics	217
13.4 DoS Defend	218
13.4.1 DoS Defend	220
13.5 802.1X	220
13.5.1 Global Config	224
13.5.2 Port Config	225
13.5.3 RADIUS Config	227
Chapter 14 SNMP	229
14.1 SNMP Config	231
14.1.1 Global Config	231
14.1.2 SNMP View	232
14.1.3 SNMP Group	233
14.1.4 SNMP User	234
14.1.5 SNMP Community	236
14.2 Notification	238
14.3 RMON	240
14.3.1 Statistics	241
14.3.2 History	242
14.3.3 Event	243
14.3.4 Alarm Config	244
Chapter 15 Maintenance	246
15.1 System Monitor	246
15.1.1 CPU Monitor	246
15.1.2 Memory Monitor	247
15.2 Log	247
15.2.1 Log Table	248
15.2.2 Local Log	249
15.2.3 Remote Log	250
15.2.4 Backup Log	250
15.3 Device Diagnostics	251
15.3.1 Cable Test	251
15.4 Network Diagnostics	252
15.4.1 Ping	253
15.4.2 Tracert	253
Appendix A: Specifications	255

Match case Limit results 1 per page

the interfaces associated with the switch that is not currently a member of the stack. The

configuration you create on the stack is defined as the provisioned configuration. The

switch that associated with the provisioned configuration is called the provisioned member.

Provisioned Configuration: The unit number, switch type and interface information which

are defined for switches not in the stack.

The information of the provisioned member is manually created, or created/updated by the

switch member when it joins the stack. The provisioned configuration retains in the stack

when the stack member leaves the stack. You can delete the associated provisioned

configuration manually.

One of the benefits of provisioning mechanism is that: if a stack member fails and you

replace it with an identical model, the replacement switch will function with exactly the

same configuration as the failed switch, assuming that the new switch is using the same

member number as the replaced switch.

When you add a switch to the switch stack, the stack will allocate a unit ID to the new

switch as rules described in

Unit Number

, and then the new switch will apply either the

provisioned configuration or the default configuration. Table 5-1 lists the events that occur

when the switch stack compares the provisioned configuration with the new switch

member.

Scenario

Event

The unit number and the device type match

The switch stack applies the provisioned

configuration to the new switch.

The unit number matches but the device

type doesn’t match

The

switch

stack

applies

the

default

configuration to the new switch.

The provisioned configuration is updated to

the configuration of the new switch.

The unit number is not found in the

provisioned configuration

The

switch

stack

applies

the

default

configuration to the new switch.

The provisioned configuration is created as

the configuration of the new switch.

Table 5-1 Scenario of a New Member Joins the Stack

•

Stack Maintenance

Stack maintenance mainly functions to monitor the join and leave of member devices,

collect the new topology at any times and maintain the current topology.

When the stack is operating normally, packets are transmitted constantly between stack

members. The switch can quickly judge the link status of the stack port via monitoring the

response of the packets. When the switch detects the link status changes, it will recollect

system topology and update topology database to ensure the normal operation of the

stack.

The events that will change the link status of the stack port which thus affecting the system

topology include: stack member failure or leave, new member's coming, link failure or

failure recovery, etc.

When the master switch fails, the stack system elects a new master from the remaining

members to succeed the previous master.