Just as the commands in the ASA, the catalyst will show you now the number of Port Channel, port channel status and the physical Interfaces which are applied to this Port Channel group. There are no specific requirements for this document. An administrator might notice errors reported in the show interface command output on the Adaptive Security Appliance (ASA).
SHOW INTERFACE ERRORS CISCO ASA HOW TO
+-+-+-+-Ġ 00 Gi1/ 0/ 45 Active 0 0 00 Gi1/ 0/ 46 Active 0 0 00 Gi1/ 0/ 47 Active 0 0 00 Gi1/ 0/ 48 Active 0 This document describes the 'overrun' error counter and how to investigate performance issues or packet loss problems on the network. Port state = Port-channel Ag-Inuse Protocol = LACP Logical slot/port = 5/1 Number of ports = 4 OK, first of all you have the configure the Port Channel on the Catalyst it is very simple something like that:Īge of the Port-channel = 761d:02h:50m:21s Here you can see the Port Channel configuration on an ASA 5540 and a Catalyst 2960. The Port Channel’s configuration is not really tricky but it is a little bit complex and it will be best if you keep the history of what you have changed to not lose overview of what and why you actually configured. If you run the Port Channel on the ASA then you are permitted to make up to 200 VLANs. The ASA distributes the traffics to all Interfaces, which means you have the functioning Load balancing, furthermore if you lost one or two Interface the whole traffics will be distribute to the Interfaces which are available. Yesterday, out of the blue I lost communications to a brand new Cisco router we installed. I have an ASA5510 that I setup that sends logs to me via email for all my Cisco routers. The benefit of Ether Channel or Port Channel is that you are able to configure redundancy and load balancing in the same time all four ASA Interfaces will be bundle to a link in the Layer 2 then you assign all VLANs directly to the Port Channel and so they applied to all Interfaces of ASA. Solution: But yes doing a Sh Int shows interface issues and errors.
This was a standard solution to this problem, however since ASA version 8.4.2 you are able to use Ether Channel to solve this problem. To overcome this limitation you can configure some VLANs and trunk them to an Interfaces. Generally Cisco ASA has one Management interface and four Gigabit Interfaces, but in modern systems and scalable Infrastructures you will need more than four Interfaces.