Hi,
> On Wed, 2016-02-10 at 08:06 -0800, ps...@cisco.com wrote:
>> Cisco Security Advisory: Cisco ASA Software IKEv1 and IKEv2 Buffer
>> Overflow Vulnerability
>>
>> Advisory ID: cisco-sa-20160210-asa-ike
> Poor bastards stuck at 8.2 (like us) might be relieved to know that
> there actually is a
...on Mon, Feb 15, 2016 at 07:50:36PM +0100, Peter Rathlev wrote:
> On Wed, 2016-02-10 at 08:06 -0800, ps...@cisco.com wrote:
> > Advisory ID: cisco-sa-20160210-asa-ike
> Poor bastards stuck at 8.2 (like us) might be relieved to know that
> there actually is a 8.2(5)59 version with the fix.
Thank you
Upgraded )
From: vinny_abe...@dell.com [mailto:vinny_abe...@dell.com]
Sent: 15 February 2016 22:32
To: dwhit...@cisco.com; Nick Cutting; pe...@rathlev.dk;
cisco-nsp@puck.nether.net
Subject: RE: [c-nsp] Cisco Security Advisory: Cisco ASA Software IKEv1 and
IKEv2 Buffer Overflow
FWIW, I believe the ASA 5505, 5510, 5520, 5540, and 5550's have always been the
identical images, with the exception of the 5505's also supporting 9.2.x.
-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of David
White, Jr. (dwhitejr)
Sent: Monday,
The non -smp image is also posted (for the 5505). Look on the 5505
download page under:
All Releases
--> Interim
--> 8
--> 8.2.5 Interim
Sincerely,
David.
On 2/15/16 3:43 PM, Nick Cutting wrote:
This is best news I've heard all day. Was going to have to move 55 VPNs by
This is best news I've heard all day. Was going to have to move 55 VPNs by
hand..
I have this for the 5510 - I cannot see a release for the 5505 - will this also
be coming?
-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Peter
Rathlev
Sent:
On Wed, 2016-02-10 at 08:06 -0800, ps...@cisco.com wrote:
> Cisco Security Advisory: Cisco ASA Software IKEv1 and IKEv2 Buffer
> Overflow Vulnerability
>
> Advisory ID: cisco-sa-20160210-asa-ike
Poor bastards stuck at 8.2 (like us) might be relieved to know that
there actually is a 8.2(5)59
Hi,
> For some reason especially on 4500X 3.7 code we have also seen this message
> on ports which are left no shut, and they have an SFP in it. It was
> seriously polluting our logs so we wrote this:
+1
> logging discriminator LOGFILTER mnemonics drops
> SFF8472-5-THRESHOLD_VIOLATION
> logging
For some reason especially on 4500X 3.7 code we have also seen this message
on ports which are left no shut, and they have an SFP in it. It was
seriously polluting our logs so we wrote this:
logging discriminator LOGFILTER mnemonics drops
SFF8472-5-THRESHOLD_VIOLATION
logging host x.y.z.w
Hi,
The few I've had were fiber strand related, a poorly seated or dirty
patch cord connection.
best!
jim
On 2/15/2016 6:43 AM, Harry Hambi - Atos wrote:
Hi all,
Getting the following error Jan 27 04:06:25.811 GMT:
%SFF8472-5-THRESHOLD_VIOLATION: Te4/1: Tx power low alarm; Operating value:
I've seen it with a bad gbic / sfp as well. All you can really do is start
checking. Fiber, jumpers, etc.
On Mon, Feb 15, 2016 at 6:51 AM, Karsten Thomann
wrote:
> Usually it is caused by a broken fiber, but you will never know for sure
> until you checked it.
>
>
Usually it is caused by a broken fiber, but you will never know for sure until
you checked it.
Gesendet von meinem BlackBerry
Originalnachricht
Von: Harry Hambi - Atos
Gesendet: Montag, 15. Februar 2016 12:44
An: 'cisco-nsp@puck.nether.net'
Betreff: [c-nsp] TX low alarm warning
Hi all,
Hi all,
Getting the following error Jan 27 04:06:25.811 GMT:
%SFF8472-5-THRESHOLD_VIOLATION: Te4/1: Tx power low alarm; Operating value:
-40.0 dBm, Threshold value: -12.2 dBm. Does this point to a fibre or gbic
error?. Any suggestions appreciated. Other end of link not alarming.
Rgds
Harry
On 15 February 2016 at 04:24, Troy Boutso wrote:
> I understand I couldn't lodge cases to the TAC etc or get any support for
> anything operating within the confines of the RTU licensing but I am more
> intersted in this for LAB/Personal use to stress test equipment out of
14 matches
Mail list logo