Not sure I understand. You want to test 100mbps throughput on a switch
etherchannel without any devices to actually generate and/or receive traffic?
Iperf is fast, easy, and runs on both win and non-win systems very nicely. This
would be a poor test for real life traffic but will test raw bytes
Also check for stp related port blockings. Perhaps there is some sort of loop
or other weird issue the switch sees. Do a show int status and show span int
f0/1 for port blocking status.
Sent via BlackBerry from T-Mobile
-Original Message-
From: Peter Pauly ppa...@gmail.com
Sender:
No experience with the fw module but if you had an asa or any fw (single or
pair) you could run the outside interface(s) off the 6500 on one vlan, then one
or more physical inside interfaces back to the 6500 with one or more vlans per
customer.
Sent via BlackBerry from T-Mobile
-Original
With local user auth you can also define users to exclude them from access to
the vpn or to ssh on the asa itself.
Sent via BlackBerry from T-Mobile
-Original Message-
From: Ryan West rw...@zyedge.com
Sender: cisco-nsp-boun...@puck.nether.net
Date: Tue, 11 Jan 2011 12:34:54
To:
Free version of kiwi cattools supports 20 devices.
Sent via BlackBerry from T-Mobile
-Original Message-
From: GERGELY Antal sk...@skoal.name
Sender: cisco-nsp-boun...@puck.nether.net
Date: Fri, 26 Nov 2010 20:44:23
To: John Neibergerjneiber...@gmail.com
Cc: cisco-nsp@puck.nether.net
1) this really depends on what kind of device you are using, what version you
are on and what version you want to upgrade to. There are a large number of
variables that you'd need to provide before anyone could be very specific.
2) depending on the device and version there are different
The outside interface ip of the asa has no requirement to be on net with
anything having to do with your pi addresses whether you are nat'ing on the asa
or not. You could use rfc1918 addresses as suggested by others.
Sent via BlackBerry from T-Mobile
-Original Message-
From: Donald
The address on the asa does not control your source addresses of your protected
hosts. Couple of options, you use your pi space behind the asa exclusively and
not nat with static (inside,outside) pi pi netmask 255.255.255.0 or use pi on
the outside of asa and nat to inside private addresses.
