Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

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

Posted on 2007-11-27
1
Medium Priority
?
2,337 Views
Last Modified: 2008-02-05
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
Comment
Question by:WPC479
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 28

Accepted Solution

by:
batry_boy earned 1500 total points
ID: 20359990
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

Featured Post

Looking for the Wi-Fi vendor that's right for you?

We know how difficult it can be to evaluate Wi-Fi vendors, so we created this helpful Wi-Fi Buyer's Guide to help you find the Wi-Fi vendor that's right for your business! Download the guide and get started on our checklist today!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

On Feb. 28, Amazon’s Simple Storage Service (S3) went down after an employee issued the wrong command during a debugging exercise. Among those affected were big names like Netflix, Spotify and Expedia.
Will you be ready when the clock on GDPR compliance runs out? Is GDPR even something you need to worry about? Find out more about the upcoming regulation changes and download our comprehensive GDPR checklist today !
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
Both in life and business – not all partnerships are created equal. As the demand for cloud services increases, so do the number of self-proclaimed cloud partners. Asking the right questions up front in the partnership, will enable both parties …

636 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question