NetXMS Support Forum

Yikes! Yes, that complicates things a bit

I've seen this topic come up a few times: Could you please make a way to 'put a node into maintenance mode'? Scheduled would be super-awesome, but I'll gladly take manual. I really don't want this thing to wake me up at 3 in the morning when somebody is doing maintenance

From browsing through the 1.1.7 source, it looks like you have quite a bit of it in place with the 'disabled' status for a node. Just suspend all polling while the node is in maintenance mode. No data collected. No events generated. Etc. Just a single event that the node has changed status (into maintenance mode) and one when it's come out of maintenance mode.

Please? Pretty please?

Peter

Not sure if this is already possible through some workaround or not. If it is, I can't figure out how

All my servers have some form of out-of-band management card or connection (Dell BMC, Dell DRAC, HP ILO, Generic IPMI, etc). This connection has a separate IP address that doesn't show up anywhere. I'd like to monitor some things from that connection and propagate it as part of the device status.

Optimally, I'd like to just add DCIs and select the IP address of the management card. Come to think of it, you'd need more than just the IP address: you'd need almost all the communication settings. Perhaps this is actually a device as a child of another device?

It might be very useful to be able to set properties on a container, and have those propagate hierarchically down the tree. I'm thinking of things like SNMP community strings, agent secrets, status calculation method, etc. Preferably with an option to override on a per sub-container or sub-node basis.

When starting up the java console (1.1.7) on a remote machine, an error occurs saying 'Load MIB file on startup' has encountered a problem. Cannot load MIB file from server: URI has an authority component.

This doesn't occur when you start the console on the server.

What gives?

Hello,
I'm trying to pull the total number of hits on a web site through an agent. I think I've tried just about every variation, but I just can't make it work! This seems so simple....

Shouldn't it just be:
1) Add a new DCI to my server
2) Pick "Agent" as the source
3) Select "PDH.CounterValue(*)" as the parameter
4) Enter "\Web Service(<instancename>)\Total Method Requests" as the parameter


I feel like I'm missing something really simple....
Help? Please?
Thanks!

Peter

I've created two nodes and a cluster object. How do I move the nodes under the cluster? Or is the only option to recreate the nodes?

The cluster option is actually elegant in the particular case of HSRP, as it models the real world. In general, though, there's not a one-to-one mapping between interfaces and IP addresses. They're two unrelated things where one just might be assigned to the other at different times. As we see in HSRP and other forms of clustering, IP address may not even be assigned to the same device at all times, so let alone to the same interface.

My suggestion would be to only detect real interfaces as interfaces. In SNMP, use ifIndex or name or description as the unique key (preferably selectable which one, since not all devices have persistent ifIndex values across reboots).

This way, you never get duplicate interfaces. Monitoring happens by the primary interface of the device anyway, so you can still get the values. Which leads me to the question: why care about the additional IP addresses at all? The additional address is normally not an integrated part of the device, but more a "service" that happens to be offered by that device at that time. You know?

I have a variety of switches but most are monitored in similar ways. For instance, for all ports I'd like an event to occur when inbound or outbound errors occur. Or when utilization is above X.

You can obviously set this up as device based templates and apply, but is there a way to create interface based templates?

If I use two switches with HSRP, netxms detects the virtual IP address as a separate interface and moves it from switch to switch when the configuration gets re-polled and the active switch happens to have changed. Is this behavior by design?

When you walk the ifTable, only one interface shows.

Example config:
(switch1)
interface Vlan99
description VL99
ip address 10.0.99.2 255.255.255.0
ip verify unicast source reachable-via any allow-default
no ip redirects
no ip unreachables
load-interval 30
standby 99 ip 10.0.99.1
standby 99 timers 1 3
standby 99 priority 105
standby 99 preempt delay minimum 10
standby 99 authentication 99_1
standby 99 track GigabitEthernet2/1
end

(switch2)
interface Vlan99
description VL99
ip address 10.0.99.3 255.255.255.0
ip verify unicast source reachable-via any allow-default
no ip redirects
no ip unreachables
load-interval 30
standby 99 ip 10.0.99.1
standby 99 timers 1 3
standby 99 priority 100
standby 99 preempt delay minimum 10
standby 99 authentication 99_1
standby 99 track GigabitEthernet2/1
end

When switch1 has the HSRP address, netxms shows:

(switch1)
- VL99 (ifIndex=147,ipaddress=10.0.99.1)
- VL99:0 (ifIndex=147,ipaddress=10.0.99.2)

(switch2)
- VL99 (ifIndex=147,ipaddress=10.0.99.3)

Which 'instance of the interface' gets the :0 depends on who happened to get detected first.
Help?

Thanks!

Peter

Cool,
thanks!

That impacts only the up/down status?

Is there a way to make unconnected (but "admin up") interfaces not show as critical?