3rd. ES documentation and fault handling
One, ES network configuration table
The ES Network configuration table is a list of the hardware and software components of ES. The ES network configuration often includes the following items:
Grading items
Miscellaneous information System name, system manufacturer/model, CPU rate, RAM, memory, system functions
1th, 2 layer media type, interface rate, VLAN, MAC, network connector
Layer 3rd IP Address, default gateway, subnet mask, WINS, DNS,
7th-tier operating systems (versions), Web-based applications, high-bandwidth applications, low-latency applications, specific considerations
Second, ES network topology diagram
Typical projects of the ES network topology map are: System name, network connection, physical location, system target, VLAN, IP address, subnet mask, operating system, network application
Most ES network topology diagrams are based on network topology diagrams, which can also include subsets of the ES Network configuration table data.
Iii. Collecting ES network configuration information
General Command:
1) ping host/ip-address; send and receive ICMP response, verify network connectivity
2) arp-a; View the MAC-IP mapping table for modifying ES (same subnet)
3) Telnet host/ip-address; log in to remote ES or a specific TCP port
Windows platform Commands
1) ipconfig/all; see modify IP information for es (for all Windows platforms)
2) winipcfg; see modify IP information for es (Win9x platform only)
3) tracert host/ip-address; Verify the connection to the host and display the device IP on the path
4) route print; Display the contents of the IP routing table for this device
5) netstat; show current network connection
Unix, Linux, and Mac OS system commands
1) ifconfig-a; View IP information for UNIX and Mac hosts
2) traceroute HOST/IP;
3) route n;
4) cat/etc/resolv.conf; View DNS server information
Iv. General fault-handling process
1, the General fault processing process:
L Collect symptoms: Collect network, user, ES symptoms
1) Analysis of existing symptoms
2) determine the owning
3) Narrow Range
4) Judging Symptoms
5) Record Symptoms
L Separation problem
1) bottom-up Troubleshooting
From the physical layer, go up to the application layer. Often used to suspect that a problem occurs at the physical layer, or when dealing with complex network problems.
2) Top-down Troubleshooting
Start down troubleshooting from the application layer to suspect that the problem occurred in the software section.
3) Divide-and-conquer Troubleshooting
Select the specific layer of the OSI model (data link layer, network layer, transport layer) to begin troubleshooting to determine whether the problem is at that level, or upper or lower layer. Suitable for use by people with extensive experience.
Common traceroute Commands Check the next 4 layers (from the physical layer to the application layer).
L CORRECT the problem
2. ES Fault handling command
1) Ping
Continuous ping:ping t 192.168.0.1; Windows system
ping s 192.168.0.1; UNIX environment
Record routing: Ping r 192.168.0.1; Windows
Ping s? nRv 192.168.0.1; Unix
2) Trace Route
Tracert 10.0.0.1; Windows system
Tracerout 10.0.0.1; Unix
Ping records the outbound interface of the router, and traceroute usually records the incoming interface.
3) ARP
Mapping table showing 2nd and 3rd addresses: Arp? A; Windows/unix
4) Route
Show routing table: route print; Windows system
Route N; Unix
5) Netstat
Displays the current connection and port to es: netstat? n; windowx & Unix
6) Ipconfig&ifconfig
Displays the IP configuration of es: Ipconfig/all; windows
Ifconfig? A; Unix
7) Nbtstat
Show current name resolution cache: Nbtstat? c;
Clears the current name resolution cache: Nbtstat R;
From for notes (Wiz)
3rd. ES documentation and fault handling
