Deployment Architecture

How to categorize all AIX servers via serverclass.conf machineTypes for deployment manager

chicodeme
Communicator

I'm on splunk-4.1.3-80534

I have deployment manager setup and it works for sunos and linux.. but how would I match for aix?

maybe like this? machineTypes=linux-i686, linux-x86_64, sunos-sun4u, sunos-sun4v, aix-*

xxxxxx:/opt/splunk/var/log/splunk# grep "System info" splunkd.log 08-03-2010 18:48:03.484 INFO loader - System info: AIX, xxxxxxx, 3, 5, 000BF23C4C00. 08-03-2010 18:48:57.479 INFO loader - System info: AIX, xxxxxxx, 3, 5, 000BF23C4C00. xxxxxx:/opt/splunk/var/log/splunk# uname -a AIX xxxxxxx 3 5 000BF23C4C00

./splunk list deploy-clients shows Deployment client: ip=x.x.x.x, dns=xxxxxxx.com, hostname=xxxxxxx, mgmt=9089, build=80534, name=deploymentClient, id=connection_x.x.x.x_9089_xxxxxxxxxx.com_xxxxxxx_deploymentClient, utsname=aix-000bf23c4c00

Obviously I could use machineTypes=linux-i686, linux-x86_64, sunos-sun4u, sunos-sun4v, aix-000bf23c4c00 but then what about all the other AIX servers.. i have to list them all?

from "man uname" on aix *

The uname command writes to standard output the name of the operating system that you are using. The machine ID number contains 12 characters in the following digit format: xxyyyyyymmss. The xx positions indicate the system and is always 00. The yyyyyy positions contain the unique ID number for the entire system. The mm position represents the model ID. The ss position is the submodel number and is always 00. The model ID describes the ID of the CPU Planar, not the model of the System as a whole. Most machines share a common model ID of 4C. The machine identifier value returned by the uname command may change when new operating system software levels are installed. This change affects applications using this value to access licensed programs. To view this identifier, enter the uname -m command.

*

I get the feeling I need to do some type of workaround within serverclass using a whitelist.. which means I make a hardcoded serverlist or utsname list.. 😞

I don't see anything about wildcard matches for machineTypes: http://www.splunk.com/base/Documentation/4.1.4/Admin/Definedeploymentclasses http://www.splunk.com/base/Documentation/4.1.4/Admin/Serverclassconf

Tags (1)
0 Karma
2 Solutions

gkanapathy
Splunk Employee
Splunk Employee

I haven't used Deployment Server with AIX, but I think that this should be considered a bug. I would try out wildcarding the machineType/utsname to see if it works in the short term.

View solution in original post

mzax
Splunk Employee
Splunk Employee

Starting with 4.1.6, a machineTypes value can contain wildcards; For example: linux-* or aix-*

View solution in original post

mzax
Splunk Employee
Splunk Employee

Starting with 4.1.6, a machineTypes value can contain wildcards; For example: linux-* or aix-*

chicodeme
Communicator

sunos-* works as well..

0 Karma

gkanapathy
Splunk Employee
Splunk Employee

I haven't used Deployment Server with AIX, but I think that this should be considered a bug. I would try out wildcarding the machineType/utsname to see if it works in the short term.

chicodeme
Communicator

tried the wildcard.. didn't work.. let it sit on deployment manager for 3hours.. restarted both client and deployment server... even though i did the 'reload deploy-server'...

Then did this in serverclass.conf:
machineTypes=aix-000bf23c4c00

and it worked after a 'reload deploy-server'...

0 Karma
Get Updates on the Splunk Community!

Splunk Observability Cloud | Unified Identity - Now Available for Existing Splunk ...

Raise your hand if you’ve already forgotten your username or password when logging into an account. (We can’t ...

Index This | How many sides does a circle have?

February 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

Registration for Splunk University is Now Open!

Are you ready for an adventure in learning?   Brace yourselves because Splunk University is back, and it's ...