The Secret Diary of Han, Aged 0x29

twitter.com/h4n

Archive for June 2006

Configuring the new SNMP poller

The configuration files of the new SNMP poller can be found in /apps/poller16/conf. After any configuration change, just HUP the poller process. It will analyze the configuration and make the necessary adjustments. The most common operation is the addition of new nodes. For this, just add a line like the following to the nodes.conf file:

ip.ad.dr.ess : {profiles: [server]}

There can be more than one profile between the square brackets, as a comma separated list.

When migrating from the old to the new poller, the data collector has to be instructed to get the data from the new poller instead of the old. This is done by changing the pollgroup of the datastreams for the components to be migrated. The new pollers serve  a different pollgroup compared to the old pollers.

Run SQL like the following in enterprise manager or SQL analyzer to update the datastreams:

update DataStream set PollGroup='pollgroup_name' where ComponentId in (Select id from Components where Address in ('ip.add.dre.ss1', 'ip.add.dre.ss2'))

Subsequently, increment the UpdateCount field in the CollGroup records to force them to load the changes. Currently, there are only two CollGroups, “collgroup1″ and “collgroup2″. Obviously only the old pollgroup needs an UpdateCount change. Finally, make sure the poller is configured before switching over the data collector in order not to lose any collected data.

Written by Han

June 23, 2006 at 12:27

Posted in Uncategorized

New poller in production

Yesterday I installed the new poller on impact1 and poller1  in production. The poller is installed in parallel to the existing poller. Here is the current setup:

/apps/poller ==> old SNMP poller (SnmpPoller.pl)

/apps/poller16 ==> new SNMP poller (poller.pl)

All existing servers will gradually be migrated to the new poller. Once this process is complete the old poller can be removed.

Written by Han

June 23, 2006 at 12:17

Posted in Uncategorized

Winsock reset

Ruby GEM did not work on my laptop until I ran:

netsh winsock reset

This however, kills the SSLVPN client, as it removes all winsock Layered Service Providers, allthough the xclient still show up using netsh winsock show catalog. Not sure if I need a reboot or an SSLVPN client reinstall to revive it. The only way to get it up and working again is a reinstall.

Written by Han

June 20, 2006 at 18:20

Posted in Uncategorized