Hi,
On Tue, Aug 27, 2019 at 04:29:14PM +0200, Brian Turnbow wrote:
> And to see the script
> show event manager policy available detailed
> Mandatory.dualrate_eem_policy.tcl
Interesting. In my version (16.06.05) it's called slightly different,
but your command to see it works...
#show event
Hi,
> > I'm not sure I wanted to know in the first place, and now I do not
> > know if
> I'm
> > scared or morbidly fascinated.
> >
> Isn't it possible to disable/delete all these EEM scripts?
>
It is a registered policy even on ASR-920-24SZ-M with no dual rate
ports
ASR920_JN1#sh event
> -Original Message-
> Gert Doering
> Sent: Monday, August 26, 2019 9:25 PM
> Hi,
>
> On Mon, Aug 26, 2019 at 02:46:19PM +0200, Gert Doering wrote:
> > does anyone know what "EEM:Mandatory.dualrate_eem.tcl" is?
>
> So, now I know - thanks to all who answered.
>
> I'm not sure I
On Mon, Aug 26, 2019, at 22:25, Gert Doering wrote:
> So, if I need EoMPLS/VPLS capability (12-24 1G ports, 2-4 10G ports,
> plain point-to-point pseudowires, or pseudowires with a local switching
> instance - VPLS or EVPN), what other vendors build such a box and do
> not hide madness inside?
At $old_job we had issues with the 920 failing to switch between the 1G and
10G shaping internally after the SFP swap. It would report that everything
went well and negotiate to 10G to only shape the actual line rate at 1G.
Fun times.
On Mon, Aug 26, 2019, 4:25 PM Gert Doering wrote:
> Hi,
>
>
Hi,
On Mon, Aug 26, 2019 at 02:46:19PM +0200, Gert Doering wrote:
> does anyone know what "EEM:Mandatory.dualrate_eem.tcl" is?
So, now I know - thanks to all who answered.
I'm not sure I wanted to know in the first place, and now I do not
know if I'm scared or morbidly fascinated.
The hacker
Bug CSCvm57265 has happened to me. The ASR920 in question had its
OSPF/MPLS Router-ID on Lo0 (only loopback configured) and the TCL script
changed it into the MGMT VRF (from the GRT) when inserting a 10G optic
for the first time after enabling the license. Needless to say it took
the site
Lukas Tribus wrote on 26/08/2019 17:28:
You better put that Loopback40 in your templates ;)
But wait! It's only Severity: 4 Minor. No need to be alarmed that this
might accidentally kill your entire network.
Nick
___
cisco-nsp mailing list
Hello Gert,
On Mon, 26 Aug 2019 at 14:47, Gert Doering wrote:
>
> Hi,
>
> does anyone know what "EEM:Mandatory.dualrate_eem.tcl" is?
>
> We have an ASR920 that grew an unexpected config change upon insertion
> of a DAC cable into port ten0/0/12, and "unexpected config change" always
> triggers
-port.html
Brian
-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of
Jared Mauch
Sent: lunedì 26 agosto 2019 15:10
To: Aaron
Cc: Gert Doering; cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] ASR920 and EEM:Mandatory.dualrate_eem.tcl
I’ll say this in public
..@puck.nether.net] On Behalf Of
> > Jared Mauch
> > Sent: lunedì 26 agosto 2019 15:10
> > To: Aaron
> > Cc: Gert Doering; cisco-nsp@puck.nether.net
> > Subject: Re: [c-nsp] ASR920 and EEM:Mandatory.dualrate_eem.tcl
> >
> > I’ll say this in public (n
-port.html
Brian
> -Original Message-
> From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of
> Jared Mauch
> Sent: lunedì 26 agosto 2019 15:10
> To: Aaron
> Cc: Gert Doering; cisco-nsp@puck.nether.net
> Subject: Re: [c-nsp] ASR920 and EEM:Manda
I’ll say this in public (now) - Changing the security posture on the VTYs is a
great reason to not use this product at the moment. I’ve seen many people not
monitor their devices for these types of changes, and this is a great case to
study.
Time for some retraining of people.
- Jared
> On
Any unexpected config change should be an automatic tac case.
Totally unexpected. Reminds me of the days when swapping a flash card on a
gsr could crash it.
This is a new one .
On Monday, August 26, 2019, Gert Doering wrote:
> Hi,
>
> does anyone know what "EEM:Mandatory.dualrate_eem.tcl" is?
>
Hi,
does anyone know what "EEM:Mandatory.dualrate_eem.tcl" is?
We have an ASR920 that grew an unexpected config change upon insertion
of a DAC cable into port ten0/0/12, and "unexpected config change" always
triggers an investigation here (who, why, what). One part of it was
somewhat related
15 matches
Mail list logo
