Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2342
  • Last Modified:

How to debug errors for packet loss on CIsco PIX 506e

I am in process of setting up a site-to-site VPN between a Juniper SSG-140 firewall and Cisco PIX 506e.   From the Juniper side, it completes Phase 1, but doesn't seem to be able to get through Phase 2 and can't Ping anything on Cisco side.  On the Cisco side, I can ping and connect to all devices on the Juniper side.

basic info:

Juniper -
    private IP = 10.10.7.2
    public IP = x.x.32.98

Cisco -
    private IP = 10.10.12.2
    public IP = x.x.3.42

I was told by Juniper support to run debug on the PIX to check for packet loss.
How does this get done, and how do I view the results?



0
WPC479
Asked:
WPC479
1 Solution
 
batry_boyCommented:
If you issue the command "show interface" from the PIX CLI, you'll get output similar to the following:

pixfirewall# sh int
interface ethernet0 "outside" is up, line protocol is down
  Hardware is i82559 ethernet, address is 000d.28d3.3275
  MTU 1500 bytes, BW 10000 Kbit half duplex
        0 packets input, 0 bytes, 0 no buffer
        Received 0 broadcasts, 0 runts, 0 giants
        0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
        9 packets output, 5310 bytes, 0 underruns
        0 output errors, 0 collisions, 0 interface resets
        0 babbles, 0 late collisions, 0 deferred
        9 lost carrier, 0 no carrier
        input queue (curr/max blocks): hardware (128/128) software (0/0)
        output queue (curr/max blocks): hardware (0/1) software (0/1)

The output above shows the Ethernet0 interface on a PIX 501 which doesn't have anything connected to it, hence the protocol down state.  If you look in the middle of the output, you'll see several lines related to input/output errors, CRC errors, frame errors, etc...I would look at those and see what you get.  You should see all those values at "0" if everything is working OK.  If you see a high amount of any of those errors, then you could report those values back to Juniper and see what they say.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improved Protection from Phishing Attacks

WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now