SSH into Linux Server become slow after change to ASA from PIX
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2009 11:58 PM - edited 03-11-2019 08:59 AM
Hi Guys,
Need assistant here,after change from PIX to ASA when remote ssh into the linux server behind the ASA become extremely slow compare to using PIX. Is it a hardware issue or configuration issue. Need help asap.
- Labels:
-
NGFW Firewalls
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2009 08:11 AM
Hi,
maybe it's just a speed or duplex mismatch between ASA and switch or linux box if it's direct attached.
Check the interface counters (errors and collisions) on the ASA
CLI:
sh interface xxx

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2009 10:38 AM
Hi,
Originally all my speed and duplex between ASA and Switch or linux box is been configure to different speed and duplex. But since then I had set to the same across all the devices to speed 100 Full duplex. But the problem still persist. Strange is that when I check the ASA interface counters there is zero errors and zero collisions.
Please advice
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2009 10:10 AM
Also you need to indicate if it's slow to connect and then normal speed once connected, or if it's slow transfer speed once connected...

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2009 10:34 AM
Hi cmcbride,
Can you explain me if it's slow to connect and then normal speed once connected.
Can you explain to me if it's slow transfer speed once connected.
Solution to the above scenarios.
Appreciate a reply.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2009 06:29 PM
service resetinbound (or resetoutbound)
service resetoutside
see if those commands help. it's probably an IDENTD issue.
