Supervise a router/switch

Sensu Classic (EOL)
1

Hi everyone !

I would like supervise a router/switch (cisco and juniper).

But I can not install a sensu-client on router/switch…

So, how to supervise router and switch ?

You have an idea ?

Best regards,
Halysan

2

You can setup any normal check on a normal server with sensu-client,
just set the "source" to be the name of your switch:
https://sensuapp.org/docs/0.19/checks (see the "source" parameter)

You just have to have some sort of monitoring server setup to provide
this function.

···

On Tue, Jun 16, 2015 at 12:52 AM, Haly San <halysan06@gmail.com> wrote:

Hi everyone !

I would like supervise a router/switch (cisco and juniper).

But I can not install a sensu-client on router/switch..

So, how to supervise router and switch ?

You have an idea ?

Best regards,
Halysan

3

That is not correct. The sensu client only monitors itself and runs
checks for stuff.
The address field represents the address upon which to bind.
https://sensuapp.org/docs/0.19/clients#definition-attributes

To monitor a switch you would add a new check. (check_ping,
check_snmp, etc) with a "source" setting,
https://sensuapp.org/docs/0.19/checks#definition-attributes (see source)
to make it appear that it comes from the switch, creating a jit-client.
https://sensuapp.org/docs/0.19/clients#jit-clients

···

On Mon, Jun 29, 2015 at 12:28 AM, Haly San <halysan06@gmail.com> wrote:

Hey Kyle,

I've install sensu-client on the server.

The file of configuration is /etc/sensu/conf.d/client.json

Example:
The switch name is "sw01"
My file /etc/sensu/conf.d/client.json

{
  "client": {
    "name": "sw01",
    "address": "IP-SW01",
    "subscriptions": [
      "test"
    ]
  }
}

It's correct?
But, I can add multiple switch on client.json?

Best regards,

2015-06-18 4:47 GMT+02:00 Kyle Anderson <kyle@xkyle.com>:

You can setup any normal check on a normal server with sensu-client,
just set the "source" to be the name of your switch:
https://sensuapp.org/docs/0.19/checks (see the "source" parameter)

You just have to have some sort of monitoring server setup to provide
this function.

On Tue, Jun 16, 2015 at 12:52 AM, Haly San <halysan06@gmail.com> wrote:
> Hi everyone !
>
> I would like supervise a router/switch (cisco and juniper).
>
> But I can not install a sensu-client on router/switch..
>
> So, how to supervise router and switch ?
>
> You have an idea ?
>
> Best regards,
> Halysan
>

4

There is no file for a JIT client. They are created automatically by
the server just in time
https://sensuapp.org/docs/0.19/clients#jit-clients

All you have to do to monitor a switch is to create a check that
monitors the switch
and setting the "source" setting:
https://sensuapp.org/docs/0.19/checks#definition-attributes (see "source")

Here is an example check definition with a source attribute:

{
  "checks": {
    "check_ping": {
      "command": "/usr/lib/nagios_plugins/check_ping my-swtich,
      "interval": 60,
      "source": "my-switch"
    }
  }
}

···

On Mon, Jun 29, 2015 at 7:48 AM, Haly San <halysan06@gmail.com> wrote:

Ok, the file /etc/sensu/client.json:

{
  "client": {
    "name": "localhost",
    "address": "127.0.0.1",
    "subscriptions": [
      "test"
    ]
  }
}

And I create a file for JIT..?

Where is the file? .. in client.json?

{
  "name": "sw01",
  "address": "IP-sw01",
  "subscriptions": ,
  "keepalives": false
}

it's complicated...
Thanks

2015-06-29 16:26 GMT+02:00 Kyle Anderson <kyle@xkyle.com>:

That is not correct. The sensu client only monitors itself and runs
checks for stuff.
The address field represents the address upon which to bind.
https://sensuapp.org/docs/0.19/clients#definition-attributes

To monitor a switch you would add a new check. (check_ping,
check_snmp, etc) with a "source" setting,
https://sensuapp.org/docs/0.19/checks#definition-attributes (see source)
to make it appear that it comes from the switch, creating a jit-client.
https://sensuapp.org/docs/0.19/clients#jit-clients

On Mon, Jun 29, 2015 at 12:28 AM, Haly San <halysan06@gmail.com> wrote:
> Hey Kyle,
>
> I've install sensu-client on the server.
>
> The file of configuration is /etc/sensu/conf.d/client.json
>
> Example:
> The switch name is "sw01"
> My file /etc/sensu/conf.d/client.json
>
> {
> "client": {
> "name": "sw01",
> "address": "IP-SW01",
> "subscriptions": [
> "test"
> ]
> }
> }
>
> It's correct?
> But, I can add multiple switch on client.json?
>
>
> Best regards,
>
> 2015-06-18 4:47 GMT+02:00 Kyle Anderson <kyle@xkyle.com>:
>>
>> You can setup any normal check on a normal server with sensu-client,
>> just set the "source" to be the name of your switch:
>> https://sensuapp.org/docs/0.19/checks (see the "source" parameter)
>>
>> You just have to have some sort of monitoring server setup to provide
>> this function.
>>
>> On Tue, Jun 16, 2015 at 12:52 AM, Haly San <halysan06@gmail.com> wrote:
>> > Hi everyone !
>> >
>> > I would like supervise a router/switch (cisco and juniper).
>> >
>> > But I can not install a sensu-client on router/switch..
>> >
>> > So, how to supervise router and switch ?
>> >
>> > You have an idea ?
>> >
>> > Best regards,
>> > Halysan
>> >
>
>

5

Hi Kyle,

I have tried simply adding the following “source” check to my config.json

{

…

“checks”: {

"check-ping": {

  "command": "/usr/local/nagios/libexec/check_ping -H 10.0.20.20 -w 5,10% -c 10,20% -p 5",

  "interval": 60,

  "source": "switch-test" 

}

}

}

but then I get this in my sensu-server.log when starting the sensu-server service

{“timestamp”:“2015-09-08T17:27:06.080525+1000”,“level”:“fatal”,“message”:“invalid settings”}

{“timestamp”:“2015-09-08T17:27:06.080919+1000”,“level”:“fatal”,“message”:“check subscribers must be an array”,“object”:{“command”:“/usr/local/nagios/libexec/check_ping -H 10.0.20.20 -w 5,10% -c 10,20% -p 5”,“interval”:60,“source”:“switch-test”,“name”:“check-ping-”}}

even when I tried adding and empty subscribers: array it returned the same error.

Is there something I’m missing?

Thanks,

James

···

On Wednesday, 1 July 2015 01:00:29 UTC+10, Kyle Anderson wrote:

There is no file for a JIT client. They are created automatically by
the server just in time
https://sensuapp.org/docs/0.19/clients#jit-clients

All you have to do to monitor a switch is to create a check that
monitors the switch
and setting the “source” setting:
https://sensuapp.org/docs/0.19/checks#definition-attributes (see “source”)

Here is an example check definition with a source attribute:

{
“checks”: {
“check_ping”: {
“command”: "/usr/lib/nagios_plugins/check_ping my-swtich,
“interval”: 60,
“source”: “my-switch”
}
}
}

On Mon, Jun 29, 2015 at 7:48 AM, Haly San haly...@gmail.com wrote:

Ok, the file /etc/sensu/client.json:

{
“client”: {
“name”: “localhost”,
“address”: “127.0.0.1”,
“subscriptions”: [
“test”
]
}
}

And I create a file for JIT…?

Where is the file? … in client.json?

{
“name”: “sw01”,
“address”: “IP-sw01”,
“subscriptions”: ,
“keepalives”: false
}

it’s complicated…
Thanks

2015-06-29 16:26 GMT+02:00 Kyle Anderson ky...@xkyle.com:

That is not correct. The sensu client only monitors itself and runs
checks for stuff.
The address field represents the address upon which to bind.
https://sensuapp.org/docs/0.19/clients#definition-attributes

To monitor a switch you would add a new check. (check_ping,
check_snmp, etc) with a “source” setting,
https://sensuapp.org/docs/0.19/checks#definition-attributes (see source)
to make it appear that it comes from the switch, creating a jit-client.
https://sensuapp.org/docs/0.19/clients#jit-clients

On Mon, Jun 29, 2015 at 12:28 AM, Haly San haly...@gmail.com wrote:

Hey Kyle,

I’ve install sensu-client on the server.

The file of configuration is /etc/sensu/conf.d/client.json

Example:
The switch name is “sw01”
My file /etc/sensu/conf.d/client.json

{
“client”: {
“name”: “sw01”,
“address”: “IP-SW01”,
“subscriptions”: [
“test”
]
}
}

It’s correct?
But, I can add multiple switch on client.json?

Best regards,

2015-06-18 4:47 GMT+02:00 Kyle Anderson ky...@xkyle.com:

You can setup any normal check on a normal server with sensu-client,
just set the “source” to be the name of your switch:
https://sensuapp.org/docs/0.19/checks (see the “source” parameter)

You just have to have some sort of monitoring server setup to provide
this function.

On Tue, Jun 16, 2015 at 12:52 AM, Haly San haly...@gmail.com wrote:

Hi everyone !

I would like supervise a router/switch (cisco and juniper).

But I can not install a sensu-client on router/switch…

So, how to supervise router and switch ?

You have an idea ?

Best regards,
Halysan

6

Yes, in the docs:
https://sensuapp.org/docs/latest/checks

You can see that “subscriptions” must be an array, but it is not required if standalone: true

You probably want this to be a standalone check. (I like standalone checks for this sort of thing)

···

On Tue, Sep 8, 2015 at 12:47 AM, James Davis james.davis@danebank.nsw.edu.au wrote:

Hi Kyle,

I have tried simply adding the following “source” check to my config.json

{

…

“checks”: {

"check-ping": {

  "command": "/usr/local/nagios/libexec/check_ping -H 10.0.20.20 -w 5,10% -c 10,20% -p 5",

  "interval": 60,

  "source": "switch-test" 

}

}

}

but then I get this in my sensu-server.log when starting the sensu-server service

{“timestamp”:“2015-09-08T17:27:06.080525+1000”,“level”:“fatal”,“message”:“invalid settings”}

{“timestamp”:“2015-09-08T17:27:06.080919+1000”,“level”:“fatal”,“message”:“check subscribers must be an array”,“object”:{“command”:“/usr/local/nagios/libexec/check_ping -H 10.0.20.20 -w 5,10% -c 10,20% -p 5”,“interval”:60,“source”:“switch-test”,“name”:“check-ping-”}}

even when I tried adding and empty subscribers: array it returned the same error.

Is there something I’m missing?

Thanks,

James

On Wednesday, 1 July 2015 01:00:29 UTC+10, Kyle Anderson wrote:

There is no file for a JIT client. They are created automatically by
the server just in time
https://sensuapp.org/docs/0.19/clients#jit-clients

All you have to do to monitor a switch is to create a check that
monitors the switch
and setting the “source” setting:
https://sensuapp.org/docs/0.19/checks#definition-attributes (see “source”)

Here is an example check definition with a source attribute:

{
“checks”: {
“check_ping”: {
“command”: "/usr/lib/nagios_plugins/check_ping my-swtich,
“interval”: 60,
“source”: “my-switch”
}
}
}

On Mon, Jun 29, 2015 at 7:48 AM, Haly San haly...@gmail.com wrote:

Ok, the file /etc/sensu/client.json:

{
“client”: {
“name”: “localhost”,
“address”: “127.0.0.1”,
“subscriptions”: [
“test”
]
}
}

And I create a file for JIT…?

Where is the file? … in client.json?

{
“name”: “sw01”,
“address”: “IP-sw01”,
“subscriptions”: ,
“keepalives”: false
}

it’s complicated…
Thanks

2015-06-29 16:26 GMT+02:00 Kyle Anderson ky...@xkyle.com:

That is not correct. The sensu client only monitors itself and runs
checks for stuff.
The address field represents the address upon which to bind.
https://sensuapp.org/docs/0.19/clients#definition-attributes

To monitor a switch you would add a new check. (check_ping,
check_snmp, etc) with a “source” setting,
https://sensuapp.org/docs/0.19/checks#definition-attributes (see source)
to make it appear that it comes from the switch, creating a jit-client.
https://sensuapp.org/docs/0.19/clients#jit-clients

On Mon, Jun 29, 2015 at 12:28 AM, Haly San haly...@gmail.com wrote:

Hey Kyle,

I’ve install sensu-client on the server.

The file of configuration is /etc/sensu/conf.d/client.json

Example:
The switch name is “sw01”
My file /etc/sensu/conf.d/client.json

{
“client”: {
“name”: “sw01”,
“address”: “IP-SW01”,
“subscriptions”: [
“test”
]
}
}

It’s correct?
But, I can add multiple switch on client.json?

Best regards,

2015-06-18 4:47 GMT+02:00 Kyle Anderson ky...@xkyle.com:

You can setup any normal check on a normal server with sensu-client,
just set the “source” to be the name of your switch:
https://sensuapp.org/docs/0.19/checks (see the “source” parameter)

You just have to have some sort of monitoring server setup to provide
this function.

On Tue, Jun 16, 2015 at 12:52 AM, Haly San haly...@gmail.com wrote:

Hi everyone !

I would like supervise a router/switch (cisco and juniper).

But I can not install a sensu-client on router/switch…

So, how to supervise router and switch ?

You have an idea ?

Best regards,
Halysan

Apply Online | denise.viskovic@danebank.nsw.edu.au

Applications close 17th October 2015

This email (and any attachments) may contain confidential and/or privileged information which is intended only to be read by the addressee. If you are not the addressee or you have received this email by mistake you must not disclose copy or distribute it or use the information contained in it (or any attachments) in any way. If you have received this message in error please notify Danebank Anglican School by return email or phone us on (02) 9580 1415 and then delete this message and any copies of it. Please also contact us if you have any doubts about the authenticity of this email. Unless explicitly attributed this email does not necessarily represent the official view of Sydney Anglican Schools Corporation.

7

sweet, that did the trick!

thanks

···

On Wednesday, 9 September 2015 01:05:34 UTC+10, Kyle Anderson wrote:

Yes, in the docs:
https://sensuapp.org/docs/latest/checks

You can see that “subscriptions” must be an array, but it is not required if standalone: true

You probably want this to be a standalone check. (I like standalone checks for this sort of thing)

On Tue, Sep 8, 2015 at 12:47 AM, James Davis james...@danebank.nsw.edu.au wrote:

Hi Kyle,

I have tried simply adding the following “source” check to my config.json

{

…

“checks”: {

"check-ping": {

  "command": "/usr/local/nagios/libexec/check_ping -H 10.0.20.20 -w 5,10% -c 10,20% -p 5",

  "interval": 60,

  "source": "switch-test" 

}

}

}

but then I get this in my sensu-server.log when starting the sensu-server service

{“timestamp”:“2015-09-08T17:27:06.080525+1000”,“level”:“fatal”,“message”:“invalid settings”}

{“timestamp”:“2015-09-08T17:27:06.080919+1000”,“level”:“fatal”,“message”:“check subscribers must be an array”,“object”:{“command”:“/usr/local/nagios/libexec/check_ping -H 10.0.20.20 -w 5,10% -c 10,20% -p 5”,“interval”:60,“source”:“switch-test”,“name”:“check-ping-”}}

even when I tried adding and empty subscribers: array it returned the same error.

Is there something I’m missing?

Thanks,

James

On Wednesday, 1 July 2015 01:00:29 UTC+10, Kyle Anderson wrote:

There is no file for a JIT client. They are created automatically by
the server just in time
https://sensuapp.org/docs/0.19/clients#jit-clients

All you have to do to monitor a switch is to create a check that
monitors the switch
and setting the “source” setting:
https://sensuapp.org/docs/0.19/checks#definition-attributes (see “source”)

Here is an example check definition with a source attribute:

{
“checks”: {
“check_ping”: {
“command”: "/usr/lib/nagios_plugins/check_ping my-swtich,
“interval”: 60,
“source”: “my-switch”
}
}
}

On Mon, Jun 29, 2015 at 7:48 AM, Haly San haly...@gmail.com wrote:

Ok, the file /etc/sensu/client.json:

{
“client”: {
“name”: “localhost”,
“address”: “127.0.0.1”,
“subscriptions”: [
“test”
]
}
}

And I create a file for JIT…?

Where is the file? … in client.json?

{
“name”: “sw01”,
“address”: “IP-sw01”,
“subscriptions”: ,
“keepalives”: false
}

it’s complicated…
Thanks

2015-06-29 16:26 GMT+02:00 Kyle Anderson ky...@xkyle.com:

That is not correct. The sensu client only monitors itself and runs
checks for stuff.
The address field represents the address upon which to bind.
https://sensuapp.org/docs/0.19/clients#definition-attributes

To monitor a switch you would add a new check. (check_ping,
check_snmp, etc) with a “source” setting,
https://sensuapp.org/docs/0.19/checks#definition-attributes (see source)
to make it appear that it comes from the switch, creating a jit-client.
https://sensuapp.org/docs/0.19/clients#jit-clients

On Mon, Jun 29, 2015 at 12:28 AM, Haly San haly...@gmail.com wrote:

Hey Kyle,

I’ve install sensu-client on the server.

The file of configuration is /etc/sensu/conf.d/client.json

Example:
The switch name is “sw01”
My file /etc/sensu/conf.d/client.json

{
“client”: {
“name”: “sw01”,
“address”: “IP-SW01”,
“subscriptions”: [
“test”
]
}
}

It’s correct?
But, I can add multiple switch on client.json?

Best regards,

2015-06-18 4:47 GMT+02:00 Kyle Anderson ky...@xkyle.com:

You can setup any normal check on a normal server with sensu-client,
just set the “source” to be the name of your switch:
https://sensuapp.org/docs/0.19/checks (see the “source” parameter)

You just have to have some sort of monitoring server setup to provide
this function.

On Tue, Jun 16, 2015 at 12:52 AM, Haly San haly...@gmail.com wrote:

Hi everyone !

I would like supervise a router/switch (cisco and juniper).

But I can not install a sensu-client on router/switch…

So, how to supervise router and switch ?

You have an idea ?

Best regards,
Halysan

Apply Online | denise…@danebank.nsw.edu.au

Applications close 17th October 2015

This email (and any attachments) may contain confidential and/or privileged information which is intended only to be read by the addressee. If you are not the addressee or you have received this email by mistake you must not disclose copy or distribute it or use the information contained in it (or any attachments) in any way. If you have received this message in error please notify Danebank Anglican School by return email or phone us on (02) 9580 1415 and then delete this message and any copies of it. Please also contact us if you have any doubts about the authenticity of this email. Unless explicitly attributed this email does not necessarily represent the official view of Sydney Anglican Schools Corporation.

8

Note, it seems in order for a proxy client to show up on the dashboard (uchiwa in my case) the check must be a standalone check.

Unlike James, an empty subscribers array did not return an error but the proxy client was not created; it appears a proxy client requires "standalone: true

Using version 0.24.0

···

On Tuesday, September 8, 2015 at 4:41:20 PM UTC-6, James Davis wrote:

sweet, that did the trick!

thanks

On Wednesday, 9 September 2015 01:05:34 UTC+10, Kyle Anderson wrote:

Yes, in the docs:
https://sensuapp.org/docs/latest/checks

You can see that “subscriptions” must be an array, but it is not required if standalone: true

You probably want this to be a standalone check. (I like standalone checks for this sort of thing)

On Tue, Sep 8, 2015 at 12:47 AM, James Davis james...@danebank.nsw.edu.au wrote:

Hi Kyle,

I have tried simply adding the following “source” check to my config.json

{

…

“checks”: {

"check-ping": {

  "command": "/usr/local/nagios/libexec/check_ping -H 10.0.20.20 -w 5,10% -c 10,20% -p 5",

  "interval": 60,

  "source": "switch-test" 

}

}

}

but then I get this in my sensu-server.log when starting the sensu-server service

{“timestamp”:“2015-09-08T17:27:06.080525+1000”,“level”:“fatal”,“message”:“invalid settings”}

{“timestamp”:“2015-09-08T17:27:06.080919+1000”,“level”:“fatal”,“message”:“check subscribers must be an array”,“object”:{“command”:“/usr/local/nagios/libexec/check_ping -H 10.0.20.20 -w 5,10% -c 10,20% -p 5”,“interval”:60,“source”:“switch-test”,“name”:“check-ping-”}}

even when I tried adding and empty subscribers: array it returned the same error.

Is there something I’m missing?

Thanks,

James

On Wednesday, 1 July 2015 01:00:29 UTC+10, Kyle Anderson wrote:

There is no file for a JIT client. They are created automatically by
the server just in time
https://sensuapp.org/docs/0.19/clients#jit-clients

All you have to do to monitor a switch is to create a check that
monitors the switch
and setting the “source” setting:
https://sensuapp.org/docs/0.19/checks#definition-attributes (see “source”)

Here is an example check definition with a source attribute:

{
“checks”: {
“check_ping”: {
“command”: "/usr/lib/nagios_plugins/check_ping my-swtich,
“interval”: 60,
“source”: “my-switch”
}
}
}

On Mon, Jun 29, 2015 at 7:48 AM, Haly San haly...@gmail.com wrote:

Ok, the file /etc/sensu/client.json:

{
“client”: {
“name”: “localhost”,
“address”: “127.0.0.1”,
“subscriptions”: [
“test”
]
}
}

And I create a file for JIT…?

Where is the file? … in client.json?

{
“name”: “sw01”,
“address”: “IP-sw01”,
“subscriptions”: ,
“keepalives”: false
}

it’s complicated…
Thanks

2015-06-29 16:26 GMT+02:00 Kyle Anderson ky...@xkyle.com:

That is not correct. The sensu client only monitors itself and runs
checks for stuff.
The address field represents the address upon which to bind.
https://sensuapp.org/docs/0.19/clients#definition-attributes

To monitor a switch you would add a new check. (check_ping,
check_snmp, etc) with a “source” setting,
https://sensuapp.org/docs/0.19/checks#definition-attributes (see source)
to make it appear that it comes from the switch, creating a jit-client.
https://sensuapp.org/docs/0.19/clients#jit-clients

On Mon, Jun 29, 2015 at 12:28 AM, Haly San haly...@gmail.com wrote:

Hey Kyle,

I’ve install sensu-client on the server.

The file of configuration is /etc/sensu/conf.d/client.json

Example:
The switch name is “sw01”
My file /etc/sensu/conf.d/client.json

{
“client”: {
“name”: “sw01”,
“address”: “IP-SW01”,
“subscriptions”: [
“test”
]
}
}

It’s correct?
But, I can add multiple switch on client.json?

Best regards,

2015-06-18 4:47 GMT+02:00 Kyle Anderson ky...@xkyle.com:

You can setup any normal check on a normal server with sensu-client,
just set the “source” to be the name of your switch:
https://sensuapp.org/docs/0.19/checks (see the “source” parameter)

You just have to have some sort of monitoring server setup to provide
this function.

On Tue, Jun 16, 2015 at 12:52 AM, Haly San haly...@gmail.com wrote:

Hi everyone !

I would like supervise a router/switch (cisco and juniper).

But I can not install a sensu-client on router/switch…

So, how to supervise router and switch ?

You have an idea ?

Best regards,
Halysan

Apply Online | denise…@danebank.nsw.edu.au

Applications close 17th October 2015

This email (and any attachments) may contain confidential and/or privileged information which is intended only to be read by the addressee. If you are not the addressee or you have received this email by mistake you must not disclose copy or distribute it or use the information contained in it (or any attachments) in any way. If you have received this message in error please notify Danebank Anglican School by return email or phone us on (02) 9580 1415 and then delete this message and any copies of it. Please also contact us if you have any doubts about the authenticity of this email. Unless explicitly attributed this email does not necessarily represent the official view of Sydney Anglican Schools Corporation.