Re: [c-nsp] 2921 Fan noise

Hi I've had the same issues before with other routers. This was a 3845 and at the time we couldn't find any way to reduce the noise, but found that if we installed small cooling fans into the small cabinet they were in, we could reduce the amount of time, (if not eliminate) that the router was

Re: [c-nsp] MPLS - MP-BPG with multiple OSPF areas

On Tuesday, October 25, 2011 08:37:39 AM Livio Zanol Puppim wrote: > Searching the Internet about this topic, I've found a > draft that seems to be a near future solution for some > major MPLS networks, called "seamless MPLS". As written > in the laymann draft ( > http://tools.ietf.org/id/draft-i

Re: [c-nsp] MPLS - MP-BPG with multiple OSPF areas

Thank you very much for your answer. Searching the Internet about this topic, I've found a draft that seems to be a near future solution for some major MPLS networks, called "seamless MPLS". As written in the laymann draft ( http://tools.ietf.org/id/draft-ietf-mpls-seamless-mpls-00.txt), the imple

Re: [c-nsp] Change hostname on ASA

If you are ssh'ing to the box, you should zeroize your keys and recreate them. Not sure if this affects your particular OS, but better to be on the safe side. Mike -- Michael K. Smith - CISSP, GSEC, GISP Chief Technical Officer - Adhost Internet LLC mksm...@adhost.com w: +1 (206) 404-9500 f: +1

Re: [c-nsp] Bad TCP Hdr ASA syslog message

Because the TCP header check occurs before the L3 interface ACL. You can verify this by taking a packet capture from this source with the 'trace' option. Once the problem packet is captured, view the packet-tracer information on it to see the actions taken on the packet. Sincerely, David. Scot

[c-nsp] Bad TCP Hdr ASA syslog message

I'm getting syslogs from my ASA: 10/24/2011 11:01 AM : %ASA-5-53: Bad TCP hdr length (hdrlen=24, pktlen=58) from 110.75.27.14/80 to x.y.z.a/23597, flags: SYN ACK , on interface Outside Since I have this Block from China as my first deny statement, Why do I still get these Syslogs? Thanks

Re: [c-nsp] re-advertising eBGP learned prefixes

Hi, On 10/24/2011 12:40, Michael Chomicz wrote: > hi andrey - not sure if you've resolved your issue - you showed 2 BGP paths > in 2 different routers right? (both are called 'spring' and are in AS 65036??) Yes, there are 2 different routers in AS 65036, one receives these prefixes, the other

Re: [c-nsp] Sup720 - flows processed by MSFC3

Hi, Jiri Prochazka wrote: Hi to everyone, we use netflow for traffic accounting and recently I've found weird issue on some flows exported from one of our 6500(SXI) equipped with VS-S720-10G-3CXL supervisor and a few WS-X6708-3CXL cards. Even if a global mask for IPv4 is set to 'interface

Re: [c-nsp] re-advertising eBGP learned prefixes

hi andrey - not sure if you've resolved your issue - you showed 2 BGP paths in 2 different routers right? (both are called 'spring' and are in AS 65036??) route that works (from the OTHER router): > spring#sh ip bgp 10.36.72.32 > BGP routing table entry for 10.36.72.32/27, version 603507 > Paths:

Re: [c-nsp] BGP traffic engineering

Then, how to manage a link failure? you mean create templates? then those prefixes are divided to customers and those customers are usually upgrading there subscriptions.  Waseem From: Mark Tinka To: cisco-nsp@puck.nether.net; Waseem Sent: Sunday, October