S
S
Sergey2015-06-04 15:15:24
Cisco
Sergey, 2015-06-04 15:15:24

Cisco ASA how to defeat the brakes on the network?

Good afternoon colleagues.
The old gateway (FreeBSD) was recently replaced with a new one (Cisco ASA 5510).
The network is divided into VLANs. We have a Windows based domain.

interface Port-channel1.90
 description SERVERS
 vlan 90
 nameif servers
 security-level 80
 ip address 192.168.90.1 255.255.255.0
!
interface Port-channel1.92
 description PRINTERS
 vlan 92
 nameif printers
 security-level 60
 ip address 192.168.92.1 255.255.255.0
!
interface Port-channel1.100
 description USERS
 vlan 100
 nameif users
 security-level 100
 ip address 192.168.100.1 255.255.255.0

All servers are in VLAN90. Users - VLAN100, printers - in VLAN92
Problem in the following. There were terrible brakes when printing documents. They can be queued and processed for several minutes, or even more.
Give advice where to look? I tried troubleshooting, but to be honest, after FreeBSD it is very unusual for me, can you tell me how and where to look?

Answer the question

In order to leave comments, you need to log in

3 answer(s)
S
Sergey, 2015-08-11
@bk0011m

Colleagues, the issue was resolved in an unexpected way.
The redesign of the network and the replacement of the gateway coincided with the simultaneous failure of two printers.
One was replaced, the other was repaired.
So it wasn't the ASA that was the problem. Just a coincidence.
Thanks to all!

M
morgan, 2015-06-04
@morgane

Monsieur knows a lot about perversions.
The Cisco ASA does not have the fastest throughput in the world, so your printed documents form a plug.
Can you put printers on the same network with computers, or if you need a separate vlan, implement it with the help of an additional router and switch on which to define computers and printers to one foot of the aces, and servers to the other?

T
throughtheether, 2015-06-04
@throughtheether

The problem is the following. There were terrible brakes when printing documents. They can be queued and processed for several minutes, or even more.
Check with wireshark which protocols (including TCP / UDP port numbers) are used when printing and correlate this data with the configured inspection rules, maybe this is the case.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question