I wondering if discovering analog voice interfaces is intended on Cisco platform or this is just bug? Currently discovery will add interfaces with media type - voiceOverIp, voiceFXO, voiceEncap, these interfaces doesn't provide any statistic over snmp, except UP/DOWN state. So I see no reason to draw graphs for them. Even better I'll be glad to get rid of them from regular IP ports, maybe move to different group, or just have option to ignore state/don't poll them?
On 09/03/2011 11:25, Nikolay Shopik wrote:
I wondering if discovering analog voice interfaces is intended on Cisco platform or this is just bug? Currently discovery will add interfaces with media type - voiceOverIp, voiceFXO, voiceEncap, these interfaces doesn't provide any statistic over snmp, except UP/DOWN state. So I see no reason to draw graphs for them. Even better I'll be glad to get rid of them from regular IP ports, maybe move to different group, or just have option to ignore state/don't poll them?
Polling is usually done via snmpwalk, which means we don't selectively poll per-port.
They can be set to be ignored in the config. It's almost impossible for us to know every type of port to be ignored :)
adam.
On Wed, 2011-03-09 at 11:27 +0000, Adam Armstrong wrote:
Polling is usually done via snmpwalk, which means we don't selectively poll per-port.
They can be set to be ignored in the config. It's almost impossible for us to know every type of port to be ignored :)
You can also add them to the $config['bad_if'] array so they will be ignored automatically.
Adam, does that sound like something we want to do in the default configuration?
Tom
On 09/03/2011 12:07, Tom Laermans wrote:
On Wed, 2011-03-09 at 11:27 +0000, Adam Armstrong wrote:
Polling is usually done via snmpwalk, which means we don't selectively poll per-port.
They can be set to be ignored in the config. It's almost impossible for us to know every type of port to be ignored :)
You can also add them to the $config['bad_if'] array so they will be ignored automatically.
Adam, does that sound like something we want to do in the default configuration?
Yes. We should slowly populate the default bad interfaces.
I was thinking of moving it to the database, so we can update it with database-update.php and users can add/remove.
adam.
On Wed, 2011-03-09 at 12:23 +0000, Adam Armstrong wrote:
Adam, does that sound like something we want to do in the default configuration?
Yes. We should slowly populate the default bad interfaces.
I was thinking of moving it to the database, so we can update it with database-update.php and users can add/remove.
I don't know if adding it under the user's nose on a schema/db update is a good thing... might suddenly remove interfaces they were indeed wanting to look at. I think as long as they are OK with what they see, they can add a new bad_if whenever they see something popping up that needs to go.
Setting stuff in the database is always good, but don't forget to write the html frontend for it :D
Tom
On Wed, 2011-03-09 at 13:26 +0100, Tom Laermans wrote:
I don't know if adding it under the user's nose on a schema/db update is a good thing... might suddenly remove interfaces they were indeed wanting to look at. I think as long as they are OK with what they see, they can add a new bad_if whenever they see something popping up that needs to go.
Just realized if the setting is only in defaults.inc.php, and we update that, the interfaces will still disappear from their view... Oops ;-)
Tom
On 09/03/2011 12:26, Tom Laermans wrote:
On Wed, 2011-03-09 at 12:23 +0000, Adam Armstrong wrote:
Adam, does that sound like something we want to do in the default configuration?
Yes. We should slowly populate the default bad interfaces.
I was thinking of moving it to the database, so we can update it with database-update.php and users can add/remove.
I don't know if adding it under the user's nose on a schema/db update is a good thing... might suddenly remove interfaces they were indeed wanting to look at. I think as long as they are OK with what they see, they can add a new bad_if whenever they see something popping up that needs to go.
Setting stuff in the database is always good, but don't forget to write the html frontend for it :D
Initial change would build it from *their* bad_if.
adam.
On Wed, 2011-03-09 at 12:28 +0000, Adam Armstrong wrote:
I don't know if adding it under the user's nose on a schema/db update is a good thing... might suddenly remove interfaces they were indeed wanting to look at. I think as long as they are OK with what they see, they can add a new bad_if whenever they see something popping up that needs to go.
Initial change would build it from *their* bad_if.
Yeah, but adding a new one into the db later on *could* suddenly remove interfaces for them. That's what I meant.
Tom
On 09/03/2011 12:32, Tom Laermans wrote:
On Wed, 2011-03-09 at 12:28 +0000, Adam Armstrong wrote:
I don't know if adding it under the user's nose on a schema/db update is a good thing... might suddenly remove interfaces they were indeed wanting to look at. I think as long as they are OK with what they see, they can add a new bad_if whenever they see something popping up that needs to go.
Initial change would build it from *their* bad_if.
Yeah, but adding a new one into the db later on *could* suddenly remove interfaces for them. That's what I meant.
A solution I do not have. Other than the fact that we only really ignore interfaces that are all the suck!
adam.
On 09/03/11 15:07, Tom Laermans wrote:
On Wed, 2011-03-09 at 11:27 +0000, Adam Armstrong wrote:
Polling is usually done via snmpwalk, which means we don't selectively poll per-port.
They can be set to be ignored in the config. It's almost impossible for us to know every type of port to be ignored :)
You can also add them to the $config['bad_if'] array so they will be ignored automatically.
Adam, does that sound like something we want to do in the default configuration?
Tom
Thanks Tom,
But what if we could actually use information from these interfaces? I'll be glad to have stats on voice interfaces, regardless type (ISDN, PSTN, voip). I suppose this require to poll different OID and some changes in discovery.
Nikolay,
On 11/03/2011 8:51, Nikolay Shopik wrote:
You can also add them to the $config['bad_if'] array so they will be ignored automatically.
Thanks Tom,
But what if we could actually use information from these interfaces? I'll be glad to have stats on voice interfaces, regardless type (ISDN, PSTN, voip). I suppose this require to poll different OID and some changes in discovery.
That might also be possible but will require some changes in the code indeed. I don't know what could be polled for those nor do I have such a device, so I 'll gladly accept any tested patches... ;-)
Tom
participants (3)
-
Adam Armstrong -
Nikolay Shopik -
Tom Laermans