User Manual
Table Of Contents
- 8-Port or 16-Port Gigabit Smart Managed Pro Switch with PoE+ and 2 SFP Ports
- Contents
- 1 Get Started
- Available publications
- Switch management and discovery overview
- Change the default IP address of the switch
- Discover or change the switch IP address
- About the user interfaces
- Access the local browser interface
- Change the language of the local browser interface
- Use the Device View of the local browser interface
- Interface naming conventions
- Configure interface settings
- Context–sensitive help and access to the support website
- Access the user manual online
- Register your product
- 2 Configure System Information
- View or define system information
- Configure the IP network settings for management access
- Configure the time settings
- Configure denial of service settings
- Configure the DNS settings
- Configure green Ethernet settings
- Use the Device View
- Configure Power over Ethernet
- Configure SNMP
- Configure LLDP
- Configure a DHCP L2 relay, DHCP snooping, and dynamic ARP inspection
- Set up PoE timer schedules
- 3 Configure Switching
- Configure the port settings
- Configure link aggregation groups
- Configure VLANs
- Configure a voice VLAN
- Configure Auto-VoIP
- Configure Spanning Tree Protocol
- Configure multicast
- Manage IGMP snooping
- Configure IGMP snooping
- Configure IGMP snooping for interfaces
- View, search, or clear the IGMP snooping table
- Configure IGMP snooping for VLANs
- Modify IGMP snooping settings for a VLAN
- Disable IGMP snooping on a VLAN and remove it from the table
- Configure one or more IGMP multicast router interfaces
- Configure an IGMP multicast router VLAN
- IGMP snooping querier overview
- Configure an IGMP snooping querier
- Configure an IGMP snooping querier for a VLAN
- Display the status of the IGMP snooping querier for VLANs
- Manage MLD snooping
- Enable MLD snooping
- Configure MLD snooping for interfaces
- Configure the MLD VLAN settings
- Modify the MLD snooping settings for a VLAN
- Remove MLD snooping from a VLAN
- Configure one or more MLD multicast router interfaces
- Configure an MLD multicast router VLAN
- Configure an MLD snooping querier
- Configure the MLD snooping querier VLAN settings
- Configure multicast VLAN registration
- View, search, and manage the MAC address table
- Configure Layer 2 loop protection
- 4 Configure Routing
- 5 Configure Quality of Service
- 6 Manage Device Security
- Change the device password for the local browser interface
- Manage the RADIUS settings
- Configure the TACACS+ settings
- Configure authentication lists
- Manage the Smart Control Center Utility
- Configure management access
- Control access with profiles and rules
- Configure port authentication
- Set up traffic control
- Configure access control lists
- Use the ACL Wizard to create a simple ACL
- Configure a MAC ACL
- Configure MAC ACL rules
- Configure MAC bindings
- View or delete MAC ACL bindings in the MAC binding table
- Configure a basic or extended IPv4 ACL
- Configure rules for a basic IPv4 ACL
- Configure rules for an extended IPv4 ACL
- Configure an IPv6 ACL
- Configure rules for an IPv6 ACL
- Configure IP ACL interface bindings
- View or delete IP ACL bindings in the IP ACL binding table
- Configure VLAN ACL bindings
- 7 Monitor the Switch and the Traffic
- 8 Maintain or Troubleshoot the Switch
- A Configuration Examples
- B Specifications and Default Settings
8-Port or 16-Port Gigabit Smart Managed Pro Switch Model GS418TPP, GS510TLP, and GS510TPP
Configure Routing User Manual233
Received Datagrams Discarded
Due To Header Errors
The number of input datagrams discarded due to errors in their IPv6
headers, including version number mismatch, other format errors, hop
count exceeded, errors discovered in processing their IPv6 options, and
so on.
Received Datagrams Discarded
Due T
o
MTU
The number of input datagrams that could not be forwarded because their
size exceeded the link MTU of outgoing interface.
Received Datagrams Discarded
Due T
o No Route
The number of input datagrams discarded because no route could be
found to transmit them to their destination.
Received Datagrams With Unknown
Protocol
The number of locally addressed datagrams received successfully but
discarded because of an unknown or unsupported protocol. This counter
is incremented at the interface to which these datagrams were addressed,
which might not be the input interface for some of the datagrams.
Received Datagrams Discarded
Due T
o
Invalid Address
The number of input datagrams discarded because the IPv6 address in
their IPv6 header's destination field was not a valid address to be received
at this entity. This count includes invalid addresses (for example, ::0) and
unsupported addresses (such as addresses with unallocated prefixes).
For entities that are not IPv6 routers and therefore do not forward
datagrams, this counter includes datagrams discarded because the
destination address was not a local address.
Received Datagrams Discarded Dut
T
o T
runcated Data
The number of input datagrams discarded because datagram frame didn't
carry enough data.
Received Datagrams Discarded
Other
The number of input IPv6 datagrams for which no problems were
encountered to prevent their continued processing, but that were
discarded for reasons such as lack of buffer space.
This counter does not
include any datagrams discarded while awaiting reassembly.
Received Datagrams Reassembly
Required
The number of IPv6 fragments received that needed to be reassembled at
this interface.
This counter is incremented at the interface to which these
fragments were addressed, which might not be the input interface for
some of the fragments.
Datagrams Successfully
Reassembled
The number of IPv6 datagrams successfully reassembled.
This counter is
incremented at the interface to which these datagrams were addressed,
which might not be necessarily the input interface for some of the
fragments.
Datagrams Failed To Reassemble The number of failures detected by the IPv6 reassembly algorithm (for
whatever reason: timed out, errors, and so on).
This is not necessarily a
count of discarded IPv6 fragments since some algorithms (notably the
algorithm in RFC 815) can lose track of the number of fragments by
combining them as they are received.
This counter is incremented at the
interface to which these fragments were addressed, which might not be
the input interface for some of the fragments.
Datagrams Forwarded The number of output datagrams that this entity received and forwarded to
their final destinations. In entities that do not act as IPv6 routers, this
counter includes only those packets that were source-routed through this
entity
, and the source-route processing was successful. For a successfully
forwarded datagram the counter of the outgoing interface is incremented.
Table 61. IPv6 Statistics information (continued)
Field Description










