Chapter 4 Es documents and troubleshooting

I. es network configuration table
The es network configuration table is a list of ES hardware and software components. Elasticsearch network configuration usually includes the following items:
Hierarchical Project
Miscellaneous information system name, system vendor/model, CPU rate, Ram, memory, System Function
1st layer 2 media type, interface speed, VLAN, Mac, and network connection
Layer-3 IP address, default gateway, subnet mask, wins, DNS,
Layer-3 operating systems (versions), network-based applications, high-bandwidth applications, low-latency applications, and specific considerations

Ii. es network topology
Typical es network topology projects include: system name, network connection, physical location, system target, VLAN, IP address, subnet mask, operating system, and network application
Most elasticsearch network topologies are created in the network topology. You can also add a subset of elasticsearch network configuration table data.

3. Collect es network configuration information
Common commands:
1) Ping host/IP-address to send and receive ICMP responses and verify network connectivity
2) ARP-A; view the MAC-IP ing table for modifying ES (same subnet)
3) Telnet host/IP-address; log on to elasticsearch or a specific TCP port.
Windows platform commands
1) ipconfig/All; view the IP address of elasticsearch (applicable to all Windows platforms)
2) winipcfg; view the IP address information of elasticsearch (applicable only to Win9x)
3) tracert host/IP-address; Verify the connection to the host and display the IP address of the device in the path
4) Route print; displays the IP route table of the current device.
5) netstat; displays the current network connection
UNIX, Linux, and Mac OS commands
1) ifconfig-A; view IP information of UNIX and Mac hosts
2) traceroute host/IP;
3) Route-N;
4) CAT/etc/resolv. conf; view DNS Server Information

Iv. General troubleshooting Process
1. General troubleshooting process:
L collect symptoms: Collect network, user, es symptoms
1) analyze existing symptoms
2) determine the ownership
3) narrow scope
4) identify symptoms
5) record symptoms
L separation problems
1) Bottom-up troubleshooting
Troubleshoot from the physical layer to the application layer. It is often used to suspect that a problem occurs at the physical layer or to handle complex network problems.
2) Top-Down troubleshooting
Troubleshoot from the application layer to the software section.
3) divide-and-conquer troubleshooting
Select a specific layer (data link layer, network layer, and transmission layer) of the OSI model to start troubleshooting. Suitable for experienced users.
Common traceroute commands are used to check the next layer (from the physical layer to the application layer ).
L correct the problem
2. Es troubleshooting command
1) Ping
Continuous Ping: Ping-T 192.168.0.1; windows
Ping-s 192.168.0.1; Unix environment
Record Route: Ping-r 192.168.0.1; windows
Ping-S-nrv 192.168.0.1; Unix
2) trace route
Tracert 10.0.0.1; windows
Tracerout 10.0.0.1; Unix
Ping records the router's outbound interface, while traceroute records the incoming interface.
3) ARP
Display the ing table for Layer 2 and layer 2nd addresses: ARP-A; Windows/Unix
4) Route
Display route table: Route print; windows
Route-N; Unix
5) netstat
Display the current connection and port to ES: netstat-N; windowx & Unix
6) ipconfig & ifconfig
Show elasticsearch IP configuration: ipconfig/All; windows
Ifconfig-A; Unix
7) NBTSTAT
Display the current name resolution cache: NBTSTAT-C;
Clear the current name resolution cache: NBTSTAT-R;

# Network Technology