Solved

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

Posted on 2007-11-27
1
2,328 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 500 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

Secure Your Active Directory - April 20, 2017

Active Directory plays a critical role in your company’s IT infrastructure and keeping it secure in today’s hacker-infested world is a must.
Microsoft published 300+ pages of guidance, but who has the time, money, and resources to implement? Register now to find an easier way.

Question has a verified solution.

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

Suggested Solutions

From Cisco ASA version 8.3, the Network Address Translation (NAT) configuration has been completely redesigned and it may be helpful to have the syntax configuration for both at a glance. You may as well want to read official Cisco published AS…
Concerto Cloud Services, a provider of fully managed private, public and hybrid cloud solutions, announced today it was named to the 20 Coolest Cloud Infrastructure Vendors Of The 2017 Cloud  (http://www.concertocloud.com/about/in-the-news/2017/02/0…
As a trusted technology advisor to your customers you are likely getting the daily question of, ‘should I put this in the cloud?’ As customer demands for cloud services increases, companies will see a shift from traditional buying patterns to new…
Both in life and business – not all partnerships are created equal. Spend 30 short minutes with us to learn:   • Key questions to ask when considering a partnership to accelerate your business into the cloud • Pitfalls and mistakes other partners…

749 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