Re: [rancid] Ciena Waveserver 1.6 - fluctuating power values + other improvement suggestions

2018-08-03 Thread heasley
Fri, Aug 03, 2018 at 11:29:03AM -0500, Chris Wopat:
> We recently upgraded some Ciena Waveservers to v1.6, Ciena added power draw
> info to the output of "show chassis". That value fluctuates a lot, causing
> diffs on most rancid-runs. looking to see the best method to filter it out.
> 
> Attached is a .txt file (or see
> https://falz.net/static/waveserver-1.6-chassis.txt)  with sample output
> from 1.5 and 1.6m where the power column was added as well as a new box
> displaying a total power value, which also fluctuates.
> 
> Is there a quick and easy way to filter out just the power values? If not,

does the patch below do it?  I no longer have any of these devices.

> a proposed solution would be to run these commands instead of 'chassis
> show':
> 
> chassis show capabilities
> chassis show mac
> 
> These would not show the power related info, but it would show the rest of
> whats normally in the 'chassis show command'.
> 
> While looking in to this issue, we also notice that the command 'software
> show' is run, but our diffs never show the output of it. If i run this via
> command line, it does show output.

what does the cmd output look like?  output from one of ours looked like:

! WS>  software show
! + ACTIVE RELEASE INFORMATION ---+
! | Parameter | Value |
! +---+---+
! | Version   | 1.0.1 |
! | Build | ae03  |
! | Build Date| 2015.12.16-13:36.17   |
! | Catalog Name  | 1.0.1-ae03_svrbuild_wvsrvr|
! +---+---+-+-+
! | Release Component | Version   | Build   | State   |
! +---+---+-+-+
! | Waveserver OS | 1.0.1 | ae03| Active  |
! | WS Control Datapath Firmware  | 1.0.1 | ae03| Active  |
! | WS Wavelogic Firmware | 1.0.1 | ae03| Active  |
! | WS Controller App | 1.0.1 | ae03| Active  |
! | WS Datapath App   | 1.0.1 | ae03| Active  |
! | WS Management App | 1.0.1 | ae03| Active  |
! | WS MIB| 01-00-00  | 00  | Active  |
! | WS YANG   | 01-00-00  | 00  | Active  |
! | WS HW-ID  | 003   | 00  | Active  |
! | WS SW-ID  | 01| 00  | Active  |
! +---+---+-+-+

> Lastly, there's a few other useful commands that I could see being added
> fairly painlessly that show some useful information. Some of these came
> from looking at what Juniper does already and some are unique to Fortigate
> (the service things).
> 
> alarm show
> blade show
> license client show
> license file list
> service-domain show
> service show map

you have to show me output of these.

Index: wavesvros.pm.in
===
--- wavesvros.pm.in (revision 3846)
+++ wavesvros.pm.in (working copy)
@@ -103,6 +103,7 @@
 # This routine parses "chassis show"
 sub ShowChassis {
 my($INPUT, $OUTPUT, $cmd) = @_;
+my($PSW) = 0;
 print STDERR "In ShowChassisClocks: $_" if ($debug);
 
 # include the command
@@ -113,8 +114,8 @@
last if (/^$prompt/);
/no matching entry found/ && return(-1);# unknown cmd
 
-   # skip fan status
-   if (/CFU FAN STATUS/) {
+   # skip fan status/chassis power draw
+   if (/(cfu fan status|chassis power summary)/i) {
while (<$INPUT>) {
tr/\015//d;
return(-1) if (/^$prompt/);
@@ -121,6 +122,20 @@
last if (/^\s*$/);
}
}
+   # filter PS wattage from power supply status
+   if (/(cfu fan status|chassis power summary)/i) {
+   while (<$INPUT>) {
+   tr/\015//d;
+   return(-1) if (/^$prompt/);
+   $PSW = 1 if (/power \(w\)/i);
+   if ($PSW && /^(|[^|]+){7,}|\s+([0-9.]+ |)/) {
+   ProcessHistory("","","","! $1|\n");
+   } else {
+   ProcessHistory("","","","! $_");
+   }
+   last if (/^\s*$/);
+   }
+   }
 
ProcessHistory("","","","! $_");
 }

___
Rancid-discuss mailing list
Rancid-discuss@shrubbery.net
http://www.shrubbery.net/mailman/listinfo/rancid-discuss


Re: [rancid] Fortigate additional tweaks and device filters

2018-08-03 Thread heasley
Fri, Aug 03, 2018 at 03:34:05PM +, Nick Nauwelaerts:
> i guess the fortinet module could use some polishing. it does a great job for 
> getting a complete running config backup. but other information could 
> certainly be welcome to.
> 
> perhaps i'll have a look at converting it to a library later on, then you can 
> just comment out the modules you have no interest in. but that will have to 
> wait until i get aerohive hiveos polished a bit.

i'll convert it, but someone needs to commit to testing it for me, since i
have none of these devices.

> // nick
> 
> 
> -Original Message-
> From: Rancid-discuss [mailto:rancid-discuss-boun...@shrubbery.net] On Behalf 
> Of heasley
> Sent: Friday, August 3, 2018 00:16
> To: Chris Wopat 
> Cc: rancid-discuss@shrubbery.net
> Subject: Re: [rancid] Fortigate additional tweaks and device filters
> 
> Thu, Aug 02, 2018 at 09:25:30AM -0500, Chris Wopat:
> > > Wed, Aug 01, 2018 at 08:37:03AM +, Nick Nauwelaerts:
> > >> hm,
> > >> i actually like to have those versions in the output. if something 
> > >> breaks my first reaction tends to be: "what changed?", and rancid is 
> > >> usually the first place i check.
> > >>
> > >> would it be an option to control this with FILTER_OSC , even though its 
> > >> not quite it's intended application?
> > > Could be; what are they?  version stamp of what exactly?
> > >
> >
> >
> > My additions to filter are based on the fact that there's already a
> > block of these being filtered, this is just 'more of the same' chatty
> > stuff that changes daily.
> >
> > I'd say go one way or another- add more similar filters (my suggestion)
> > or do none or have a toggle-able option. FILTER_OSC sounds more like
> > it's for security stuff, so that doesn't seem like the best fit to me.
> >
> > Has a new FILTER_CRUFT type of option been discussed in the past? Unsure
> > if this fits the category of any other previously discussed things.
> 
> it was intended for stuff that oscillated but is still desirable (by some).
> so, seems to fit the application, perhaps for the other similar filters.
> again, i dont know the platform, so I need input.
> 
> ___
> Rancid-discuss mailing list
> Rancid-discuss@shrubbery.net
> http://www.shrubbery.net/mailman/listinfo/rancid-discuss
> 
> 
> 
> Volg Aquafin op Facebook | 
> Twitter | 
> YouTube 
> | LinkedIN
> 
> In het kader van de uitoefening van onze taken verzamelen we bij Aquafin 
> persoonsgegevens. Hoe we omgaan met deze gegevens en wat de rechten van de 
> betrokkenen zijn, kan je nalezen in onze privacy 
> policy.
> 
> [https://www.aquafin.be/sites/aquafin/files/styles/paragraph_with_caption/public/2018-06/email_banner_web.jpg]
>   P Denk aan het milieu. Druk deze mail niet onnodig af.

___
Rancid-discuss mailing list
Rancid-discuss@shrubbery.net
http://www.shrubbery.net/mailman/listinfo/rancid-discuss


[rancid] Ciena Waveserver 1.6 - fluctuating power values + other improvement suggestions

2018-08-03 Thread Chris Wopat
We recently upgraded some Ciena Waveservers to v1.6, Ciena added power draw
info to the output of "show chassis". That value fluctuates a lot, causing
diffs on most rancid-runs. looking to see the best method to filter it out.

Attached is a .txt file (or see
https://falz.net/static/waveserver-1.6-chassis.txt)  with sample output
from 1.5 and 1.6m where the power column was added as well as a new box
displaying a total power value, which also fluctuates.

Is there a quick and easy way to filter out just the power values? If not,
a proposed solution would be to run these commands instead of 'chassis
show':

chassis show capabilities
chassis show mac

These would not show the power related info, but it would show the rest of
whats normally in the 'chassis show command'.

While looking in to this issue, we also notice that the command 'software
show' is run, but our diffs never show the output of it. If i run this via
command line, it does show output.

Lastly, there's a few other useful commands that I could see being added
fairly painlessly that show some useful information. Some of these came
from looking at what Juniper does already and some are unique to Fortigate
(the service things).

alarm show
blade show
license client show
license file list
service-domain show
service show map
!!
! saos 1.6

waveserver-v1.6# chassis show



! 
! +-- CHASSIS POWER SUMMARY --+
! | Parameter   | Value   |
! +-+-+
! | Total Power (W) |   564.0 |
! +-+-+
! 
! + POWER SUPPLY STATUS 
---+---+
! | Slot   | Admin| Oper   | Type| Model| Serial Number | 
Part Number / Rev| Power (W) |
! 
++--++-+--+---+--+---+
! | PSU-1  | Enabled  | Normal | DC  | WS DC PSU| blah  |   
 186-1501-900/AB   | 255.5 |
! 
++--++-+--+---+--+---+
! | PSU-2  | Enabled  | Normal | DC  | WS DC PSU| blah  |   
 186-1501-900/AB   | 308.5 |
! 
++--++-+--+---+--+---+


!!
! saos 1.5

waveserver-v1.5# chassis show



!
! + POWER SUPPLY STATUS 
---+
! | Slot   | Admin| Oper   | Type| Model| Serial Number | 
Part Number / Rev|
! 
++--++-+--+---+--+
! | PSU-1  | Enabled  | Normal | DC  | WS DC PSU| blah  |   
 186-1501-900/AB   |
! 
++--++-+--+---+--+
! | PSU-2  | Enabled  | Normal | DC  | WS DC PSU| blah  |   
 186-1501-900/AB   |
! 
++--++-+--+---+--+

___
Rancid-discuss mailing list
Rancid-discuss@shrubbery.net
http://www.shrubbery.net/mailman/listinfo/rancid-discuss


Re: [rancid] Fortigate additional tweaks and device filters

2018-08-03 Thread Nick Nauwelaerts
i guess the fortinet module could use some polishing. it does a great job for 
getting a complete running config backup. but other information could certainly 
be welcome to.

perhaps i'll have a look at converting it to a library later on, then you can 
just comment out the modules you have no interest in. but that will have to 
wait until i get aerohive hiveos polished a bit.

// nick


-Original Message-
From: Rancid-discuss [mailto:rancid-discuss-boun...@shrubbery.net] On Behalf Of 
heasley
Sent: Friday, August 3, 2018 00:16
To: Chris Wopat 
Cc: rancid-discuss@shrubbery.net
Subject: Re: [rancid] Fortigate additional tweaks and device filters

Thu, Aug 02, 2018 at 09:25:30AM -0500, Chris Wopat:
> > Wed, Aug 01, 2018 at 08:37:03AM +, Nick Nauwelaerts:
> >> hm,
> >> i actually like to have those versions in the output. if something breaks 
> >> my first reaction tends to be: "what changed?", and rancid is usually the 
> >> first place i check.
> >>
> >> would it be an option to control this with FILTER_OSC , even though its 
> >> not quite it's intended application?
> > Could be; what are they?  version stamp of what exactly?
> >
>
>
> My additions to filter are based on the fact that there's already a
> block of these being filtered, this is just 'more of the same' chatty
> stuff that changes daily.
>
> I'd say go one way or another- add more similar filters (my suggestion)
> or do none or have a toggle-able option. FILTER_OSC sounds more like
> it's for security stuff, so that doesn't seem like the best fit to me.
>
> Has a new FILTER_CRUFT type of option been discussed in the past? Unsure
> if this fits the category of any other previously discussed things.

it was intended for stuff that oscillated but is still desirable (by some).
so, seems to fit the application, perhaps for the other similar filters.
again, i dont know the platform, so I need input.

___
Rancid-discuss mailing list
Rancid-discuss@shrubbery.net
http://www.shrubbery.net/mailman/listinfo/rancid-discuss



Volg Aquafin op Facebook | 
Twitter | 
YouTube | 
LinkedIN

In het kader van de uitoefening van onze taken verzamelen we bij Aquafin 
persoonsgegevens. Hoe we omgaan met deze gegevens en wat de rechten van de 
betrokkenen zijn, kan je nalezen in onze privacy 
policy.

[https://www.aquafin.be/sites/aquafin/files/styles/paragraph_with_caption/public/2018-06/email_banner_web.jpg]
  P Denk aan het milieu. Druk deze mail niet onnodig af.

___
Rancid-discuss mailing list
Rancid-discuss@shrubbery.net
http://www.shrubbery.net/mailman/listinfo/rancid-discuss