I have been using Ostinato to generate some traffic. It gives you a very big
granularity on how to build the packet, how fast to send it, etc.
Catalin
From: Christian MacNevin cmacne...@linkedin.com
To: Cisco-nsp cisco-nsp@puck.nether.net
Sent: Thu, 17
Hi,
Does anyone know how is throughput tested for Cisco ASA applicances? Although,
does anyone have any documents where Cisco explains what firewall throughput
means?
Is it:
- the total packets per second the entire backplane can handle, so all the
traffic across all ports, inside and
Hi,
Does anyone know how to view the RAM that is currently installed on each
linecard in a VSS cluster 2x6509 running SXI2a? I could not find anything on
Cisco website, or I did not know where to look for that information.
Thank you
Catalin
Linecard RAM
On (2010-08-27 13:40 +), C and C Dominte wrote:
Does anyone know how to view the RAM that is currently installed on each
linecard in a VSS cluster 2x6509 running SXI2a? I could not find anything on
Cisco website, or I did not know where to look for that information.
You could
Hi everyone,
I recently got this messages logged in the 2x6509 VSS cluster:
May 30 07:56:18.498: %LTL-SW1_SP-2-LTL_PARITY_CHECK: LTL parity check request
for 0x53DC.
May 30 08:15:10.994: %LTL-SW1_SP-2-LTL_PARITY_CHECK: LTL parity check request
for 0xDBF4.
I tried to search for some
Hi,
Is there any chance of overlapping subnets configured on two different routers?
I saw similar issues caused by this, but traceroute and show ip route commands
should help diagnosing that.
Catalin
From: Lee ler...@gmail.com
To: Renelson Panosky
I recently configured two Catalyst 6509 switches in a VSS
cluster. When I am issuing the command “show mac-address-table dynamic”, I’m
getting the following output:
Legend: * - primary entry
age - seconds
since last seen
n/a - not
available
vlan mac address
type
Hi,
I recently configured two catalyst 6509 switches into a
VSS cluster. After I experimented issues with unknown unicast, the secondary
chassis reloaded itself with no apparent reason, .
The cluster is configured with two VSL 10G links, one
link is on the supervisor, and the secondary one
kl...@kl.net wrote:
C and C Dominte wrote:
Thank you for your advice, however, increasing the timers
did not work.
I powered down the active linecards from switch 2
yesterday to see if it stopped the unicast flood, which it did.
Today I increased the mac address syncronisation activity
1440 issues
To: Matthew Huff mh...@ox.com
Cc: C and C Dominte domintefam...@yahoo.co.uk, cisco-nsp@puck.nether.net
cisco-nsp@puck.nether.net
Date: Wednesday, 5 August, 2009, 9:06 PM
Take a look at this..
http://www.cisco.com/en/US/products/ps9336/products_tech_note09186a0080a7c837.shtml#oob_mac
Hi,
I recently clustered 2 Catalysts 6509's into a VSS 1440
Virtual switch.
Details about the cluster:
- Software version:
s72033_rp Software (s72033_rp-IPSERVICESK9_WAN-M), Version 12.2(33)SXI1,
RELEASE SOFTWARE (fc3)
- Supervisor:
VS-S720-10G with one 10G port
used as VSL
Hi all,
I am having a rather unusual issue, and I have no idea on
how or where to find any info about it.
Basically, a bgp session configured over an etherchannel
(2x10G ports) goes down, if one cable is removed. This should not happen under
normal circumstances, as the physical
Hi all,
I would like to cluster two 6509 catalysts into a VSS-1440 system, and I would
like to know if anyone else tried that, to see some opinions about it.
The configuration would be:
2x 6509
6x 6748 in each
1x 6708 in each
1x Sup in each
I am a little bit surprised that they have such
Try permitting based on IP address only, e.g.
access-list 199 permit ip x.x.x.x 0.0.0.255 host y.y.y.y
still the same result, all the ip's are blocked.
Well you are allowing TCP port 22 from x.x.x.x/24 to any destination, which
will be any IP address on the router. But that doesnt
Aaron Riemer [EMAIL PROTECTED] wrote: Hi,
I was under the impression that vty ACL's only filter by source addresses.
i.e. standard ACL's only.
At first I thought that since VTY lines are for SSH access, there is no need to
add an extended access-list, to allow ssh on those lines.
I found on
Aaron Daubman [EMAIL PROTECTED] wrote: Catalin,
...
Is this a normal behavior of the IOS, to block access to all the ip's,
including to the one that is supposed to be allowed?
While not explicitly called out, I believe the intent is to use a
'standard' access list with one's vty
Hi,
yes, but since the extended access-list range is 100 - 199, this means that
extended access lists are supported:
#access-class ?
1-199 IP access list
1300-2699 IP expanded access list
WORD Access-list name
Catalin
Tom Storey [EMAIL PROTECTED] wrote: Expanded access-lists
17 matches
Mail list logo