Here is a sample zone down trap about a local zone named smk-210 going
down. The trap is from the SunMC agent that is running in the global
zone. The trap is directly from a SunMC agent whom was told to send
traps to a secondary traphost in addition to it's SunMC server tier.
# /opt/SUNWsymo
Yes, that is what I thought. I think it is too esoteric. An importance
of a zone states in an SNMP monitoring environment is it is either
"running" or not. States such as "ready", or "installed" mean the zone
is not running. If a zone is a server, there is an SNMP process that
can be easily im
Mike,
To get it to link, I needed to create a symbolic link at
/usr/lib/libzonecfg.so -> libzonecfg.so.1. Time to go searching for
linker options that I haven't needed before... I haven't looked into
it, but for some reason I seem to get some useless events. Consider
the following reboot:
#
Paul Kraus wrote:
> On 10/27/06, Mike Gerdts <[EMAIL PROTECTED]> wrote:
>
>> What if "zoneadm monitor -a" (all zones) had the ability to spit
>> syslog entries and/or SNMP traps? Perhaps if the SNMP route is taken,
>> a subagent to snmpd(1M) would be the right approach.
>
>Speaking as an
On 10/27/06, Mike Gerdts <[EMAIL PROTECTED]> wrote:
What if "zoneadm monitor -a" (all zones) had the ability to spit
syslog entries and/or SNMP traps? Perhaps if the SNMP route is taken,
a subagent to snmpd(1M) would be the right approach.
Speaking as an admin and customer and not a de
On Fri 27 Oct 2006 at 10:49PM, Matty wrote:
> This is definitely useful, and I can see it being useful for postmortem
> debugging and event tracking. Are there any plans to allow admins to
> log zone console output to a logfile? That would be extremely useful!!
Thanks.
Yes, console logging is o
On Sat 28 Oct 2006 at 10:10AM, Mike Gerdts wrote:
> On 10/28/06, Menno Lageman <[EMAIL PROTECTED]> wrote:
> >How about something like the DHCP eventhook mechanism (see
> >dhcpagent(1M))? This would allow people to get notifications of zone
> >state changes in a well defined *and* simple way without
On 10/28/06, Menno Lageman <[EMAIL PROTECTED]> wrote:
How about something like the DHCP eventhook mechanism (see
dhcpagent(1M))? This would allow people to get notifications of zone
state changes in a well defined *and* simple way without the need
scraping logs for unstable messages.
zoneadmd ju
Dan Price wrote:
On Fri 27 Oct 2006 at 09:11PM, Peter Memishian wrote:
> So here are my questions:
>
> - Do you think this is useful?
>
> - Do you think the log level (Info) is right? daemon.info is
> *not* logged by default, whereas notice is. (So basically: do
>
On Fri, 27 Oct 2006, Mike Gerdts wrote:
On 10/27/06, Dan Price <[EMAIL PROTECTED]> wrote:
As for GPEC, that's what our existing C api is based upon. Take a look at
zonecfg_notify_*() in libzonecfg. It's a real horror show but it does
solve the "get the state and then subscribe to future chan
On Fri, 27 Oct 2006, Dan Price wrote:
A (large) customer recently asked me to implement a feature whereby they
could monitor zone activity via syslog. The motivation is that for this
customer, any zone state change not during maintenance windows is a cause
for alarm.
I prototyped this featur
On 10/27/06, Dan Price <[EMAIL PROTECTED]> wrote:
As for GPEC, that's what our existing C api is based upon. Take a look at
zonecfg_notify_*() in libzonecfg. It's a real horror show but it does
solve the "get the state and then subscribe to future changes and don't
miss anything in between" pro
> I think that some minimal syslogging is warranted (I've tried to keep it
> simple here) because we do know that customers have a degree of comfort
> with syslog, and because it fits readily into various existing 3rd party
> monitoring packages.
But it falls apart in the long run since the o
On Fri 27 Oct 2006 at 06:21PM, Dan Price wrote:
> >
> > Encouraging programmatic use of syslog seems a step in the wrong direction
> > to me. Surely we can provide a better mechanism to notify them of state
> > changes?
>
> Such as?
I guess my larger point is that I haven't seen us take steps i
> Such as?
No strong preference, but it should be something that can be versioned,
extensible, parsed unambiguously and easily, and unaffected by locale.
Maybe general purpose event channels?
--
meem
___
zones-discuss mailing list
zones-discuss@open
On Fri 27 Oct 2006 at 09:11PM, Peter Memishian wrote:
>
> > So here are my questions:
> >
> > - Do you think this is useful?
> >
> > - Do you think the log level (Info) is right? daemon.info is
> > *not* logged by default, whereas notice is. (So basically: do
> > yo
On 10/27/06, Dan Price <[EMAIL PROTECTED]> wrote:
A (large) customer recently asked me to implement a feature whereby they
could monitor zone activity via syslog. The motivation is that for this
customer, any zone state change not during maintenance windows is a cause
for alarm.
I've had a si
> So here are my questions:
>
> - Do you think this is useful?
>
> - Do you think the log level (Info) is right? daemon.info is
> *not* logged by default, whereas notice is. (So basically: do
> you want these messages in /var/adm/messages by default, or not?)
>
>
18 matches
Mail list logo
