Shulou(Shulou.com)06/01 Report--

When I made a recent network change, I found that SSG140 could not be accessed through web/telnet/ssh, but snmp monitoring and ping were normal, all kinds of internal Internet applications were normal, and only the management page could not be accessed. The fault was dealt with today.

1. Various management methods fail, try to connect to ssg140 with console

two。 After a successful login, back up the configuration file first

Get config > tftp 192.168.1.1 ssg140cfg.txt

3. Check management configuration information

Get admin get admin manage-ip get int eth0/0

Check that the web/telnet/ssh configuration is correct, the port settings are normal, and access source address control is not enabled.

4. Try to grab the bag

a. Set the packet capture filter to record only the required data set ffilter src-ip 192.168.1.1

b. Clear cache record clear db

c. Enable the following debugging features separately

Debug web all / debug admin all / debug flow all

d. Open the Firewall web Administration page on the management host

e. Record capture package output get db str > tftp 192.168.1.1 web.log

5. Analysis of packet capture records

Debug_admin_all (no valid information)

Debug_flow_all (no valid information)

So far, the cause of the failure has not been found, so we have no choice but to turn to the network (pulling off google is really better than rowing, many problems cannot be found in boating, and google will not be disappointed). The search found the following connection:

Http://www.juniperforum.com/index.php?topic=7884.0

The buddy in the article also encountered the same situation, but his version is V6.0.R1, my version here is V6.1R2, according to the follow-up approach to deal with, the fault is still the same.

This is the third time I have encountered this problem. I think it is caused by the OS version and should belong to the fixed bug. Check the next version of release note and expect to have the answer. I'm too lazy to check. Because I was in a hurry to make a change, I backed up the configuration file again, and then manually restart the firewall command as follows:

Reset save-config yes

PS: the reboot of the firewall is still very fast. It will restart and load the configuration file in about 1 minute. Like it.

Attach the official steps to deal with this problem.

Reference link: http://kb.juniper.net/InfoCenter/index?page=content&id=KB11363

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.