Sponsored Content
Operating Systems Solaris Agent missing in zone after patching Post 302985419 by Rockyc3400 on Wednesday 9th of November 2016 10:10:11 AM
Old 11-09-2016
Hi,

The agent is "Autosys". It was installed in a Sparse root zone with a separate mount point created for it.
Yes it is a third party agent.

Regards,
Rocky
 

9 More Discussions You Might Find Interesting

1. Solaris

Patching zone

Hi everyone, I have a container which includes 5 zones. I would like to patch only 2 of them with the latest recommended patch bundle. 1) Could it be done by installing Recommended Patch Cluster on those 2 zones? And after rebooting them? 2) May patching only those 2 zones affect the... (6 Replies)
Discussion started by: royalliege
6 Replies

2. Solaris

Zone failes to boot due to mount issue, dir exists in zone.

I have two physical servers, with zones that mount local storage. We were using "raw device" in the zonecfg to point to a metadevice on the global zone (it was not mounted in the global zone at any point). It failed to mount on every boot because the directory existed in the zone. I... (6 Replies)
Discussion started by: BG_JrAdmin
6 Replies

3. Solaris

patching a zone.

what are prerequisites or precautions we take before we install a patch in a zone.what if zone fails to boot after patching.How to recover form this situation.? Thanks in advance..:) (1 Reply)
Discussion started by: ravijanjanam12
1 Replies

4. Solaris

Help needed for patching on zone cluster

Hi All, Below is the configuration of my sun cluster. root@glob-one # clzc status === Zone Clusters === --- Zone Cluster Status --- Name Node Name Zone HostName Status Zone Status ---- --------- ------------- ------ ----------- data ... (0 Replies)
Discussion started by: milindphanse604
0 Replies

5. Solaris

showing 2 different time zones in global zone and nonglobal zone

can some one help me out as it is showing 2 different time zones in global zone and nonglobal zone .In global zone it is showing in GMT while in nonglobal zone i it showing as PDT. System in running with solaris 10 (3 Replies)
Discussion started by: ravijanjanam12
3 Replies

6. UNIX for Advanced & Expert Users

Solaris 10: I forgot to detach a zone before zpool export. Uninstall zone?

Dear all, recently, I migrated a solaris zone from one host to another. The zone was inside of a zpool. The zpool cotains two volumes. I did the following: host1: $ zlogin zone1 shutdown -y -g0 -i0 #Zone status changes from running to installed $ zpool export zone1 host2: $ zpool... (2 Replies)
Discussion started by: custos
2 Replies

7. Solaris

Patching Procedure in Solaris 10 with sun cluster having Solaris zone

Hi Gurus I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow. Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Discussion started by: nick101
1 Replies

8. Solaris

Solaris 11 Global zone patching having Solaris 10 branded zone

I am planning to do solaris 11 global zone patching having solaris 10 branded zone. I have a doubts on step 8 specially Can someone clear my step 8 doubts or if anything wrong between step 1 to step 9 please correct that also as I have pretty good idea about Step 10 mean patching in solaris 10... (2 Replies)
Discussion started by: amity
2 Replies

9. Solaris

Solaris 11 zone has no external network access (except to Global Zone)

Hi, hoping someone can help, its been a while since I used Solaris. After creating a NGZ (non global zone), the NGZ can access the GZ (Global Zone) and the GZ can access the NGZ (using ssh, zlogin) However, the NGZ cannot access any other netwqork devices, it can't even see the default router ... (2 Replies)
Discussion started by: GazinLincoln
2 Replies
naaagt(1M)																naaagt(1M)

NAME
naaagt - Native Agent Adapter (NAA) SYNOPSIS
priority] logMask] ... DESCRIPTION
The Native Agent Adapter allows third-party SNMP agents to work with the HP SNMP Master Agent The Native Agent Adapter runs as a subagent to the HP SNMP Master Agent. reads the file (see the environment variable, described below), and it registers each object identifier (OID) with See the section. After registration is complete, receives SNMP requests from and forwards them to a non-standard UDP port on the same system (see the envi- ronment variable, described below). also receives SNMP responses from the third-party SNMP agent, which is listening to the non-standard UDP port, and forwards the responses to The third-party SNMP agent must listen to the same non-standard UDP port that sends to not the standard SNMP port number(161). Refer to third-party documentation for instructions on how to accomplish this. The third-party SNMP agent can be started before or after starting Parameters Sets the registration priority. If two subagents register the same OIDs, requests are sent to the subagent with the highest priority or to the subagent with the same priority that was the last to register. The priority range is zero (high) to 255 (low). Default: zero. Causes the Native Agent Adapter to continue to run, even if the HP SNMP Master Agent terminates. When subsequently restarts, will re-establish communica- tion with and re-register its OIDs. This option is recommended if the procedure is used, described below. By default, ter- minates automatically when terminates. Troubleshooting Parameters Displays usage information. Sets the logging mask. may be one of the following names: or Multiple logging options can be specified by repeating the option. Logging data is written to the SNMP log file, Default: Causes to run in foreground. By default, runs in the background. Native Agent Adapter Start-up The Native Agent Adapter start-up procedure may be provided by the vendor of the third-party SNMP agent. Refer to third-party documenta- tion for instructions. The third-party SNMP agent and its Native Agent Adapter can be started and stopped automatically during system start-up and shutdown. This is accomplished by providing a start-up/shutdown script under the directory, with symbolic links to it under an appropriate directory. See the rc(1M) man page for details. See the section for procedures for starting The third-party SNMP agent and its Native Agent Adapter can be started using the command by providing start-up and shutdown scripts under Normally, those scripts are merely symbolic links to the automatic start-up/shutdown script under following the same naming conventions documented in the rc(1M) manual page. These scripts are executed by the command. See the section for procedures for starting The third-party SNMP agent and its Native Agent Adapter can be started by entering commands directly or by executing an arbitrary script. When this approach is used, the option should probably be used because the third-party agent and adapter will not be restarted by the com- mand. The following procedure should be used to start for each third-party agent. o Export which must be set to a unique port number. o Export which must be set to an absolute path name for a third-party-specific file. Create the file; refer to third-party docu- mentation for a list of the OIDs that are instrumented by the third-party SNMP agent. o Export which must be set to the community name to be used in SNMP requests forwarded from to the third-party SNMP agent. This environment variable is required only if the third-party agent is configured to use a community name other than the default ("public"). o Create a unique symbolic link to This makes it convenient to distinguish each Native Agent Adapter in output from the command. Execute the symbolic link to start o Start the third-party SNMP agent, following procedures in the third-party documentation. This can be done before or after start- ing naaCnf File Format The file consists of a list of numeric object identifiers (OIDs), one OID per line. Each OID is a subtree of MIB variables that are instrumented by the third-party SNMP agent. Refer to third-party documentation for the list of OIDs. Blank lines and lines beginning with "#" are treated as comments. Leading and trailing spaces on a line are ignored. The OID can start with an optional period. EXTERNAL INFLUENCES
Environment Variables The absolute path name for the file from which the Native Agent Adapter reads the OIDs to be registered for its third-party SNMP agent. Default (not recommended): The community name that the Native Agent Adapter uses in SNMP requests forwarded to the third-party SNMP agent. Note that this does not have to match any community names accepted by the SNMP Master Agent, which are defined in This environment variable is required only if the standard community name ("public") is not accepted by the third-party SNMP agent. Refer to third-party documenta- tion for instructions regarding SNMP community names. Default: public. The non-standard UDP port number to which the Native Agent Adapter forwards SNMP requests to the third-party SNMP agent. This must match the port number that the third-party agent listens to instead of the standard SNMP port(161). Each third-party SNMP agent must listen to a different non- standard UDP port number. Default: 8161. International Code Set Support Supports single-byte character code sets except where the SNMP protocol supports only 7-bit characters encoded in ASCII. WARNINGS
The Native Agent Adapter only supports SNMP read requests (for example, SNMP Get). SNMP Set requests must be sent directly to the third- party SNMP agent's non-standard UDP port If the value is not a valid port number, terminates without writing any error message either to the display or to If there are no valid OIDs in the file, terminates. It does not register a default OID. There may be unexpected results if the is outside the valid range. AUTHOR
was developed by SNMP Research and Hewlett-Packard Company. FILES
Default file. Not recommended. Directory for SNMP start-up and shutdown scripts. Native Agent Adapter command. HP SNMP Master Agent command. HP SNMP log file. SEE ALSO
rc(1M), snmpd(1M), snmpd.conf(4). naaagt(1M)
All times are GMT -4. The time now is 01:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy