In addition, anyone seen a situation where DDM support depends on IOS
image version? For example I have one ProLabs X2-10GB-LR-C
transceiver, which outputs DDM information in case of
cat4500-ipbasek9-mz.122-54.SG.bin, but displays nothing in show
interfaces transceiver output when IOS image is
Mack McBride writes:
It could be the specific match string.
Right, especially if there are many dots in the regexp.
What match is timing out?
If there are dots, try to escape them (e.g. | include 192\.0\.2\.).
But the output volume of show ip cache flow is probably also
significantly larger
Hi Martin,
In addition, anyone seen a situation where DDM support depends on IOS
image version? For example I have one ProLabs X2-10GB-LR-C
Take a look at the DOM Support column:
http://www.cisco.com/en/US/docs/interfaces_modules/transceiver_modules/compatibility/matrix/OL_6974.html#wp55804
On 30.09.2011 01:39, Martin T wrote:
Jason,
I agree that preferring Cisco branded SFP's gives a sort of quality
guarantee. According to a friend of mine, those SFP's were bought from
a electronics market in Moscow:
http://img.nag.ru/images/18388/101019342.gif
It used to be true that AnyConnect was only SSL.
One of the features introduced in AnyConnect 3.0
was support for IPSec.
HTH
Rick
On 11/3/2011 3:46 PM, Leonardo Gama Souza wrote:
No, it only supports SSL VPN.
-Mensagem original-
De: cisco-nsp-boun...@puck.nether.net
Last but not least, any ideas why do different switch models display
transceiver EEPROM information(show idprom interface X) differently?
Because Cisco has lots of different Business Units and they don't have
any reason to coordinate the display format?
Steinar Haug, Nethelp consulting,
On 09/11/2011 12:20, sth...@nethelp.no wrote:
Because Cisco has lots of different Business Units and they don't have
any reason to coordinate the display format?
My favourite is showing DOM values on 7600s. If you have a LAN card, you use:
(Router)# show interfaces TenGigabitEthernet x/y
See below
Jared Mauch
On Nov 9, 2011, at 6:20 AM, Garry g...@gmx.de wrote:
Interesting side note: in a customer Nexus 5548 we've recently put some
20+ SFPs in (1 and 10G) - along with four copper 10G links for NX2248.
Interestingly, the OEM SFP/SFP+ were recognized as original (no
warning,
Thanks
I tried using the escape but this did not help.
Its faster to export the whole netflow table to text via show ip cache flow |
tee url then run a grep in that file than to run it on the ASR direct.
I suspect it's software related, seems like a visit to TAC is in order...
On 09 Nov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Cisco TelePresence System Integrator C Series and Cisco TelePresence EX Series
Device Default Root Account Manufacturing Error
Advisory ID: cisco-sa-2009-telepresence-c-ex-series
Revision 1.0
For Public Release 2011 November 9 16:00 UTC
Hello,
Does anyone have any experience with the Sup720 and multicast? Looking to
find out how many IGMP groups the 720 will support and if we would need the
3BXL or if the 3B would be sufficient. The application is heavy video
streaming.
Cisco says Nexus but would prefer to stick with my trusty
On Wed, 9 Nov 2011, Ronen Isaac wrote:
Hello,
Does anyone have any experience with the Sup720 and multicast? Looking to
find out how many IGMP groups the 720 will support and if we would need the
3BXL or if the 3B would be sufficient. The application is heavy video
streaming.
Cisco says
I made a following setup:
http://img828.imageshack.us/img828/5736/interfacestrafficcounte.png
..and executed iperf -s -u -fm in ubuntu machine and iperf -c
10.10.11.2 -fm -u -d -b 10m -t600 in PE860 machine. Before the test
I cleared all interface counters. Iperf results were following:
Good evening list,
Cisco has claimed that the following optics are compatible:
SFP-GE-S=
1000BASE-SX SFP transceiver module for MMF, 850-nm wavelength, extended
operating temperature range and DOM support, dual LC/PC connector
GLC-SX-MM=
1000BASE-SX SFP transceiver module for
ASR only supports the 100m-fx GLC. The rest need to be SFP to work at all.
Jared Mauch
On Nov 9, 2011, at 6:59 PM, cisco...@secureobscure.com wrote:
Good evening list,
Cisco has claimed that the following optics are compatible:
SFP-GE-S=
1000BASE-SX SFP transceiver module
We just figured it out, the asr9k in 4.1.1 has this:
Full-duplex, 1000Mb/s, SXFD, link type is force-up
Adding negotiation auto under every fiber SFP interface having the issue has
resolved it:
Full-duplex, 1000Mb/s, SXFD, link type is autonegotiation
Thanks!
-Original Message-
From:
Hi,
Most likely this is because of 802.1Q tag (4 bytes) added to the counter
on a switch interface (and obviously you don't see this tag on a router
interface). For example, interfaces Fa3/0 and Fa0/24:
773476480 - 771435576 = 2040904
2040904 / 510226 = 4
HTH
Martin T wrote:
I made a
17 matches
Mail list logo
