Cisco ASA and Firepower Threat Defense Reimage Guide
Step 9
To troubleshoot network connectivity, see the following examples.
Example:
View the network interface configuration:
firepower-boot>show interface
eth0 Link encap:Ethernet HWaddr 00:a0:c9:00:00:00
inet addr:10.123.123.123 Bcast:10.123.123.255 Mask:255.255.255.0
inet6 addr: fe80::2a0:c9ff:fe00:0/64 Scope:Link
inet6 addr: 2001:420:270d:1310:2a0:c9ff:fe00:0/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:522369 errors:0 dropped:0 overruns:0 frame:0
TX packets:2473 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:42120849 (40.1 MiB) TX bytes:170295 (166.3 KiB)
...
Ping a server:
firepower-boot>ping www.example.com
PING www.example.com (10.125.29.106) 56(84) bytes of data.
64 bytes from qg-in-f106.1e100.net (74.125.29.106): icmp_seq=1 ttl=42 time=28.8 ms
64 bytes from qg-in-f106.1e100.net (74.125.29.106): icmp_seq=2 ttl=42 time=28.1 ms
64 bytes from qg-in-f106.1e100.net (74.125.29.106): icmp_seq=3 ttl=42 time=28.1 ms
64 bytes from qg-in-f106.1e100.net (74.125.29.106): icmp_seq=4 ttl=42 time=29.0 ms
^C
--- www.example.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 28.159/28.549/29.022/0.437 ms
firepower-boot>
Traceroute to test network connectivity:
firepower-boot>traceroute -n 10.100.100.1
traceroute to 10.100.100.1 (10.100.100.1), 30 hops max, 60 byte packets
1 10.123.123.1 0.937 ms 1.078 ms 1.154 ms^C
firepower-boot>
Step 10
To troubleshoot installation failures, see the following examples.
Example:
"Timed out" error
At the downloading stage, if the file server is not reachable, it will fail due to a time out.
...
Erasing disk0 ...
Verifying
timed out
Upgrade aborted
firepower-boot>
In this case, make sure the file server is reachable from the ASA. You can verify by pinging the file server.
"Package not found" error
Reimage the Firepower Threat Defense Device
Cisco ASA and Firepower Threat Defense Reimage Guide
29
Sayfayı Yazdır