D-Link DGS-3426P Product Manual - Page 97

xStack® DGS-3400 Series Layer 2 Gigabit Ethernet Managed Switch VID (1-4094) Mirror Group ID (1-4) Target Port Source Ports Action RX Source Ports TX Source Ports modify the RSPAN Entries. This is the VLAN ID that, along with the VLAN Name, identifies the VLAN which will to modify the RSPAN Entries. Tick the check box and enter a group ID which mirror session is used for RSPAN source function. The target port that receives the packets duplicated at the source port. Use the pull-down menu to select add, or delete a source port. Select Source to display the source port only. The goal of RX source ports is to monitor as much as possible all the packets received by the source interface or VLAN before any modification or processing is performed by the switch. A copy of each packet received by the source is sent to the destination port for that RSPAN session. The goal of TX source ports is to monitor as much as possible all the packets sent by the source interface after all modification and processing is performed by the switch. DNS Relay Computer users usually prefer to use text names for computers for which they may want to open a connection. Computers themselves, require 32 bit IP addresses. Somewhere, a database of network devices' text names and their corresponding IP addresses must be maintained. The Domain Name System (DNS) is used to map names to IP addresses throughout the Internet and has been adapted for use within intranets. For two DNS servers to communicate across different subnets, the DNS Relay of the Switch must be used. The DNS servers are identified by IP addresses. Mapping Domain Names to Addresses Name-to-address translation is performed by a program called a Name server. The client program is called a Name resolver. A Name resolver may need to contact several Name servers to translate a name to an address. The Domain Name System (DNS) servers are organized in a somewhat hierarchical fashion. A single server often holds names for a single network, which is connected to a root DNS server - usually maintained by an ISP. Domain Name Resolution The domain name system can be used by contacting the name servers one at a time, or by asking the domain name system to do the complete name translation. The client makes a query containing the name, the type of answer required, and a code specifying whether the domain name system should do the entire name translation, or simply return the address of the next DNS server if the server receiving the query cannot resolve the name. When a DNS server receives a query, it checks to see if the name is in its sub domain. If it is, the server translates the name and appends the answer to the query, and sends it back to the client. If the DNS server cannot translate the name, it determines what type of name resolution the client requested. A complete translation is called recursive resolution and requires the server to contact other DNS servers until the name is resolved. Iterative resolution specifies that if the DNS server cannot supply an answer, it returns the address of the next DNS server the client should contact. Each client must be able to contact at least one DNS server, and each DNS server must be able to contact at least one root server. The address of the machine that supplies domain name service is often supplied by a DHCP or BOOTP server, or can be entered manually and configured into the operating system at startup. 88