1mibiisa(1M) System Administration Commands mibiisa(1M)
2
6 mibiisa - Sun SNMP Agent
7
9 mibiisa [-ar] [-c config-dir] [-d debug-level] [-p port]
10 [-t cache-timer]
11
14 The mibiisa utility is an RFC 1157-compliant SNMP agent. It supports
15 MIB-II as defined in RFC 1213, with Sun extensions under Sun's enter‐
16 prise number. The MIB (Management Information Base) is both readable
17 and writable. The mibiisa utility supports all SNMP protocol operations
18 including GET-REQUEST, GETNEXT-REQUEST, SET-REQUEST, GET-REPLY, and
19 TRAP.
20 The SMA (Systems Management Agent) is the default SNMP agent in
23 Solaris. MIB-II subagent mibiisa does not run by default. To enable
24 mibiisa, rename the configuration file from /etc/snmp/conf/mibi‐
25 isa.rsrc- to /etc/snmp/conf/mibiisa.rsrc. SMA has the capability to
26 handle any MIB-II requests.
27 The mibiisa utility supports the coldStart, linkUp, linkDown, and
30 authentication traps. The authentication trap may be disabled by a com‐
31 mand-line switch, which itself may be overridden by a management sta‐
32 tion writing to a MIB variable in the standard SNMP MIB group.
33 The mibiisa utility supports four distinct views of the MIB. The view
36 used for any request is determined by the community string contained in
37 that request.
38 To enhance security, mibiisa supports an option to block all writes to
41 the MIB. You can also limit the set of management stations from which
42 the agent will accept requests in the configuration file used when
43 starting the mibiisa. See the section for more information.
44 Unless overridden, mibiisa uses UDP port 161, the standard SNMP port.
47 The mibiisa utility issues traps through the same port on which it
48 receives SNMP requests.
49 The mibiisa utility must run with super-user privileges and is typi‐
52 cally started at system startup via /etc/rc3.d. mibiisa may not be
53 started using inetd(1M). When started, mibiisa detaches itself from the
54 keyboard, disables all signals except SIGKILL, SIGILL, SIGUSR1, and
55 SIGUSR2, and places itself in the background.
56
58 The following options are supported by mibiisa:
59 -a Disable the generation of authentication traps. How‐
61 ever, an SNMP manager may write a value into snmpEn‐
62 ableAuthenTraps to enable or disable authentication
63 traps.
64 -c config-dir Specify a directory where it expects snmpd.conf file,
67 on startup. The default directory is /etc/snmp/conf.
68 -d debug-level Debug. A value of 0 disables all debug and is the
71 default. Levels 1 through 3 represent increasing lev‐
72 els of debug output. When mibiisa receives the signal
73 SIGUSR1, it resets the debug-level to 0. When mibiisa
74 receives the signal SIGUSR2, it increments the debug-
75 level by one.
76 Debug output is sent to the standard output in effect
78 at the time mibiisa is started. No matter what debug
79 level is in effect, certain significant events are
80 logged in the system log.
81 -p port Define an alternative UDP port on which mibiisa lis‐
84 tens for incoming requests. The default is UDP port
85 161.
86 -r Place the MIB into read-only mode.
89 -t cache-timer By default, information fetched from the kernel is
92 considered to be valid for 45 seconds from the time
93 it is retrieved. This cache lifetime may be altered
94 with this parameter. You cannot set cache-timer to
95 any value less than 1.
96
99 The snmpd.conf file is used for configuration information. Each entry
100 in the file consists of a keyword followed by a parameter string. The
101 keyword must begin in the first position. Parameters are separated from
102 the keyword and from one another by white space. Case in keywords is
103 ignored. Each entry must be contained on a single line. All text fol‐
104 lowing (and including) a pound sign (#) is ignored. Keywords currently
105 supported are:
106 sysdescr
108 The value to be used to answer queries for sysDescr.
110 syscontact
113 The value to be used to answer queries for sysContact.
115 syslocation
118 The value to be used to answer queries for sysLocation.
120 trap
123 The parameter names one or more hosts to receive traps. Only five
125 hosts may be listed.
126 system-group-read-community
129 The community name to get read access to the system group and Sun's
131 extended system group.
132 system-group-write-community
135 The community name to get write access to the system group and
137 Sun's extended system group.
138 read-community
141 The community name to get read access to the entire MIB.
143 write-community
146 The community name to get write access to the entire MIB (implies
148 read access).
149 trap-community
152 The community name to be used in traps.
154 kernel-file
157 The name of the file to use for kernel symbols.
159 managers
162 The names of hosts that may send SNMP queries. Only five hosts may
164 be listed on any one line. This keyword may be repeated for a total
165 of 32 hosts.
166 newdevice
169 The additional devices which are not built in SNMPD. The format is
171 as follows: newdevice type speed name where newdevice is the key‐
172 word, type is an integer which has to match your schema file, speed
173 is the new device's speed, and name is this new device's name.
174 An example snmpd.conf file is shown below:
178 sysdescr Sun SNMP Agent, Sun Fire 4800, Company
180 Property Number 123456
181 syscontact Cliff Claven
182 sysLocation Room 1515, building 1
183 #
184 system-group-read-community public
185 system-group-write-community private
186 #
187 read-community all_public
188 write-community all_private
189 #
190 trap localhost
191 trap-community SNMP-trap
192 #
193 #kernel-file /vmunix
194 #
195 managers lvs golden
196 managers swap
197
201 The mibiisa utility and its configuration file, snmpd.conf, may be
202 placed in any directory. However for Solaris 2.4 and subseqent
203 releases, use /usr/lib/snmp for mibiisa itself and /etc/snmp/conf for
204 the configuration file. You can modify the configuration file as appro‐
205 priate. If you make any changes to snmpd.conf file keyword values, you
206 must kill and restart mibiisa for the changes to take effect.
207 Your /etc/services file (or NIS equivalent) should contain the follow‐
210 ing entries:
211 snmp 161/udp # Simple Network Mgmt Protocol
216 snmp-trap 162/udp snmptrap # SNMP trap (event) messages
217 The following is an example for Solaris 2.x and releases compatible
221 with Solaris 2.x, such as Solaris 9:
222 #
224 # Start the SNMP agent
225 #
226 if [ -f /etc/snmp/conf/snmpd.conf -a -x
227 /usr/lib/snmp/mibiisa ];
228 then
229 /opt/SUNWconn/snm/agents/snmpd
230 echo 'Starting SNMP-agent.'
231
235 SNMP, as presently defined, offers relatively little security. The
236 mibiisa utility accepts requests from other machines, which can have
237 the effect of disabling the network capabilities of your computer. To
238 limit the risk, the configuration file lets you specify a list of up to
239 32 manager stations from which mibiisa will accept requests. If you do
240 not specify any such manager stations, mibiisa accepts requests from
241 anywhere.
242 The mibiisa utility also allows you to mark the MIB as "read-only" by
245 using the -r option.
246 mibiisa supports four different community strings. These strings, how‐
249 ever, are visible in the configuration file and within the SNMP packets
250 as they flow on the network.
251 The configuration file should be owned by, and readable only by super-
254 user. In other words the mode should be:
255 −rw−−−−−−− 1 root 2090 Oct 17 15:04 /etc/snmp/conf/snmpd.conf
257 Managers can be restricted based on the community strings. This can be
262 configured by creating an optional secondary configuration file
263 /etc/snmp/conf/mibiisa.acl. To enable such a restriction, add the secu‐
264 rity line in the /etc/snmp/conf/mibiisa.rsrc file.
265 An example mibiisa.acl file is as follows:
268 acl = {
270 {
271 communities = public
272 access = read-only
273 managers = xyz
274 }
275 {
276 communities = private
277 access = read-write
278 managers = abc,pqrs
279 }
280 }
281 An example mibiisa.rsrc file is as follows:
285 resource =
287 {
288 {
289 registration_file = "/etc/snmp/conf/mibiisa.reg"
290 security = "/etc/snmp/conf/mibiisa.acl"
291 policy = "spawn"
292 type = "legacy"
293 command = "/usr/lib/snmp/mibiisa -r -p $PORT"
294 }
295 }
296
299 This section discusses some of the differences between the mibiisa MIB
300 and the standard MIB-II (as defined in RFC 1213).
301 The following variables are read-only in the mibiisa MIB:
304 sysName
306 atIfIndex
307 ipDefaultTTL
308 These variables are read-write in the standard MIB-II.
313 The mibiisa MIB Address Translation tables support limited write
316 access: only atPhysAddress may be written, either to change the physi‐
317 cal address of an existing entry or to delete an entire ARP table
318 entry.
319 The mibiisa MIB IP Net to Media table supports limited write access:
322 only ipNetToMediaPhysAddress and ipNetToMediaType may be written,
323 either to change the physical address of an existing entry or to delete
324 an entire ARP table entry.
325 The following variables are read-write in the mibiisa MIB; however,
328 these variables have fixed values. Any new values "set" to them are
329 accepted, but have no effect:
330 ipRoutIfIndex
332 ipRouteMetric1
333 ipRouteMetric2
334 ipRouteMetric3
335 ipRouteMetric4
336 ipRouteType
337 ipRouteAge
338 ipRouteMask
339 ipRouteMetric5
340 The following mibiisa MIB variable reflects the actual state of the
345 related table entry. "Sets" are accepted but have no effect:
346 tcpConnState
348 The following mibiisa MIB variables are readable, but return a fixed
353 value:
354 icmpInDestUnreachs Returns 1
359 icmpInTimeExcds Returns 1
360 icmpInParmProbs Returns 1
361 icmpInSrcQuenchs Returns 1
362 icmpInRedirects Returns 1
363 icmpInEchos Returns 1
364 icmpInEchoReps Returns 1
365 icmpInTimestamps Returns 1
366 icmpInTimestampReps Returns 1
367 icmpInAddrMasks Returns 1
368 icmpInAddrMaskReps Returns 1
369 icmpOutDestUnreachs Returns 1
370 icmpOutTimeExcds Returns 1
371 icmpOutParmProbs Returns 1
372 icmpOutSrcQuenchs Returns 1
373 icmpOutRedirects Returns 1
374 icmpOutEchos Returns 1
375 icmpOutEchoReps Returns 1
376 icmpOutTimestamps Returns 1
377 icmpOutTimestampReps Returns 1
378 icmpOutAddrMasks Returns 1
379 icmpOutAddrMaskReps Returns 1
380 ifInUnknownProtos Returns 0
381 ipAdEntBcastAddr Returns 1
382 ipAdEntReasmMaxSiz Returns 65535
383 ipRouteMetric1 Returns −1
384 ipRouteMetric2 Returns −1
385 ipRouteMetric3 Returns −1
386 ipRouteMetric4 Returns −1
387 ipRouteAge Returns 0
388 ipRouteMetric5 Returns −1
389 ipNetToMediaType [22mReturns (3) dynamic
390 ipRoutingDiscards Returns 0
391 The following variables return a fixed value of 0 for drivers not con‐
395 forming to the GLD framework (see gld(7D)), including the old LAN driv‐
396 ers on SPARC machines:
397 ifInOctets Returns 0
402 ifInNUcastPkts Returns 0
403 ifInDiscards Returns 0
404 ifOutOctets Returns 0
405 ifOutNUcastPkts Returns 0
406 ifOutDiscards Returns 0
407
410 The following describes the attributes in the group and table defini‐
411 tions in the /var/snmp/mib/sun.mib file.
412 system
414 The system group reports statistics about a particular system (for
415 example, a workstation or a printer).
416 sysDescr − A textual description of the entity. This value should
419 include the full name and version identification of the system's hard‐
420 ware type, software operating-system, and networking software. This
421 value must only contain printable ASCII characters. (string[255])
422 sysObjectID − The vendor's authoritative identification of the network
425 management subsystem contained in the entity. This value is allocated
426 within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy
427 and unambiguous means for determining what type of equipment is being
428 managed. For example, if vendor "Flintstones, Inc." was assigned the
429 subtree 1.3.6.1.4.1.4242, it could assign the identifier
430 1.3.6.1.4.1.4242.1.1 to its "Fred Router." (objectid)
431 sysUpTime − Time (in hundredths of a second) since the network manage‐
434 ment portion of the system was last reinitialized. (timeticks)
435 sysContact − The textual identification of the contact person for this
438 managed node, together with information on how to contact this person.
439 (string[255])
440 sysName − An administratively-assigned name for this managed node. By
443 convention, this is the node's fully-qualified domain name.
444 (string[255])
445 sysLocation − The physical location of this node (for example, "tele‐
448 phone closet, 3rd floor" (string[255]))
449 sysServices − A value indicating the set of services that this entity
452 primarily offers. (int) The value is a sum. This sum initially takes
453 the value zero. Then, for each layer L in the range 1 through 7 for
454 which this node performs transactions, 2 raised to (L - 1) is added to
455 the sum. For example, a node that performs primarily routing functions
456 would have a value of 4 (2**(3-1)). In contrast, a node that is a host
457 offering application services would have a value of 72 (2**(4-1) +
458 2**(7-1)). Note that in the context of the Internet suite of protocols,
459 values should be calculated accordingly:
460 Layer Functionality
465 1 physical (such as repeaters)
466 2 datalink/subnetwork (such as bridges)
467 3 internet (such as IP gateways)
468 4 end-to-end (such as IP hosts)
469 7 applications (such as mail relays)
470 For systems including OSI protocols, Layers 5 and 6 may also be
474 counted.
475 interfaces
477 The interfaces group reports the number of interfaces handled by the
478 agent.
479 ifNumber − The number of network interfaces, regardless of their cur‐
482 rent state, present on this system. (int)
483 ifTable
485 The ifTable is a table of interface entries. The number of entries is
486 given by the value of ifNumber.
487 ifIndex − A unique value for each interface. Its value ranges between 1
490 and the value of ifNumber. The value for each interface must remain
491 constant at least from one reinitialization of the entity's network
492 management system to the next reinitialization. (int)
493 ifDescr − A textual string containing information about the interface.
496 This string should include the name of the manufacturer, the product
497 name, and the version of the hardware interface. (string[255])
498 ifType − The type of interface, distinguished according to the physi‐
501 cal/link protocol(s) immediately below the network layer in the proto‐
502 col stack. (enum)
503 ifMtu − The size of the largest datagram that can be sent/received on
506 the interface, specified in octets. For interfaces used for transmit‐
507 ting network datagrams, this is the size of the largest network data‐
508 gram that can be sent on the interface. (int)
509 ifSpeed − An estimate of the interface's current bandwidth in bits-per-
512 second. For interfaces that do not vary in bandwidth, or for those
513 where no accurate estimation can be made, this object should contain
514 the nominal bandwidth. (gauge)
515 if1hysAddress − The interface's address at the protocol layer immedi‐
518 ately below the network layer in the protocol stack. For interfaces
519 without such an address (for example, a serial line), this object
520 should contain an octet string of zero length. (octet[128])
521 ifAdminStatus − The desired state of the interface. The testing(3)
524 state indicates that no operational packets can be passed. (enum)
525 if OperStatus − The current operational state of the interface. The
528 testing(3) state indicates that no operational packets can be passed.
529 (enum)
530 ifLastChange − The value of sysUpTime at the time the interface entered
533 its current operational state. If the current state was entered prior
534 to the last reinitialization of the local network management subsystem,
535 then this object contains a zero value. (timeticks)
536 ifInOctets − The total number of octets received on the interface,
539 including framing characters. (counter) Returns a fixed value of 0.
540 ifInUcastPkts − The number of subnetwork-unicast packets delivered to a
543 higher-layer protocol. (counter)
544 ifInNUcastPkts − The number of non-unicast (that is, subnetwork- broad‐
547 cast or subnetwork-multicast) packets delivered to a higher-layer pro‐
548 tocol. (counter) Returns a fixed value of 0.
549 ifInDiscards − The number of inbound packets chosen to be discarded,
552 even though no errors had been detected to prevent their being deliver‐
553 able to a higher-layer protocol. One possible reason for discarding
554 such a packet could be to free up buffer space. (counter) Returns a
555 fixed value of 0.
556 ifInErrors − The number of inbound packets that contained errors pre‐
559 venting them from being deliverable to a higher-layer protocol.
560 (counter)
561 ifInUnknownProtos − The number of packets received via the interface
564 that were discarded because of an unknown or unsupported protocol.
565 (counter) Returns a fixed value of 0.
566 ifOutOctets − The total number of octets transmitted out of the inter‐
569 face, including framing characters. (counter) Returns a fixed value of
570 0.
571 ifOutUcastPkts − The total number of packets that higher-level proto‐
574 cols requested be transmitted to a subnetwork-unicast address, includ‐
575 ing those that were discarded or not sent. (counter)
576 ifOutNUcastPkts − The total number of packets that higher-level proto‐
579 cols requested be transmitted to a non- unicast (that is, a subnetwork-
580 broadcast or subnetwork-multicast) address, including those that were
581 discarded or not sent. (counter) Returns a fixed value of 0.
582 ifOutDiscards − The number of outbound packets that were chosen to be
585 discarded even though no errors had been detected to prevent their
586 being transmitted. One possible reason for discarding such a packet
587 could be to free up buffer space. (counter) Returns a fixed value of 0.
588 ifOutErrors − The number of outbound packets that could not be trans‐
591 mitted because of errors. (counter)
592 ifOutQLen − The length of the output packet queue (in packets). (gauge)
595 ifSpecific − A reference to MIB definitions specific to the particular
598 media being used to realize the interface. For example, if the inter‐
599 face is realized by an Ethernet, then the value of this object refers
600 to a document defining objects specific to Ethernet. If this informa‐
601 tion is not present, its value should be set to the OBJECT IDENTIFIER {
602 0 0 }, which is a syntactically valid object identifier. Any conformant
603 implementation of ASN.1 and BER must be able to generate and recognize
604 this value. (objectid)
605 atTable
607 atTable Address Translation tables contain the NetworkAddress to physi‐
608 cal address equivalences. Some interfaces do not use translation tables
609 for determining address equivalences (for example, DDN-X.25 has an
610 algorithmic method). If all interfaces are of this type, then the
611 Address Translation table is empty, that is, has zero entries.
612 atIfIndex − The interface on which this entry's equivalence is effec‐
615 tive. The interface identified by a particular value of this index is
616 the same interface as identified by the same value of ifIndex. (int)
617 atPhysAddress − The media-dependent physical address. (octet[128]) Set‐
620 ting this object to a null string (one of zero length) has the effect
621 of invaliding the corresponding entry in the atTable object. That is,
622 it effectively dissociates the interface identified with said entry
623 from the mapping identified with said entry. It is an implementation-
624 specific matter as to whether the agent removes an invalidated entry
625 from the table. Accordingly, management stations must be prepared to
626 receive tabular information from agents that corresponds to entries not
627 currently in use. Proper interpretation of such entries requires exami‐
628 nation of the relevant atPhysAddress object.
629 atNetAddress − The NetworkAddress (that is, the IP address) correspond‐
632 ing to the media-dependent physical address. (netaddress)
633 ip
635 The ip group reports statistics about the Internet Protocol (IP) group.
636 ipForwarding − The indication of whether this entity is acting as an IP
639 gateway in respect to the forwarding of datagrams received by, but not
640 addressed to, this entity. IP gateways forward datagrams. IP hosts do
641 not— except those source-routed via the host. (enum)
642 Note that for some managed nodes, this object may take on only a subset
645 of the values possible. Accordingly, it is appropriate for an agent to
646 return a "badValue" response if a management station attempts to change
647 this object to an inappropriate value.
648 ipDefaultTTL − The default value inserted into the Time-To-Live field
651 of the IP header of datagrams originated at this entity, whenever a TTL
652 value is not supplied by the transport layer protocol. (int)
653 ipInReceives − The total number of input datagrams received from inter‐
656 faces, including those received in error. (counter)
657 ipInHdrErrors − The number of input datagrams discarded due to errors
660 in their IP headers, including bad checksums, version number mismatch,
661 other format errors, time-to-live exceeded, errors discovered in pro‐
662 cessing their IP options, and so on. (counter)
663 ipInAddrErrors − The number of input datagrams discarded because the IP
666 address in their IP header's destination field was not a valid address
667 to be received at this entity. This count includes invalid addresses
668 (for example, 0.0.0.0) and addresses of unsupported Classes (for exam‐
669 ple, Class E). For entities that are not IP Gateways and therefore do
670 not forward datagrams, this counter includes datagrams discarded
671 because the destination address was not a local address. (counter)
672 ipForwDatagrams − The number of input datagrams for which this entity
675 was not their final IP destination, as a result of which an attempt was
676 made to find a route to forward them to that final destination. In
677 entities that do not act as IP Gateways, this counter will include only
678 those packets that were Source-Routed via this entity, and the Source-
679 Route option processing was successful. (counter)
680 ipInUnknownProtos − The number of locally-addressed datagrams received
683 successfully but discarded because of an unknown or unsupported proto‐
684 col. (counter)
685 ipInDiscards − The number of input IP datagrams for which no problems
688 were encountered to prevent their continued processing, but which were
689 discarded, for example, for lack of buffer space. Note that this
690 counter does not include any datagrams discarded while awaiting
691 reassembly. (counter)
692 ipInDelivers − The total number of input datagrams successfully deliv‐
695 ered to IP user-protocols (including ICMP). (counter)
696 ipOutRequests − The total number of IP datagrams that local IP user-
699 protocols (including ICMP) supplied to IP in requests for transmission.
700 Note that this counter does not include any datagrams counted in ipFor‐
701 wDatagrams. (counter)
702 ipOutDiscards − The number of output IP datagrams for which no problem
705 was encountered to prevent their transmission to their destination, but
706 which were discarded (for example, for lack of buffer space). Note that
707 this counter would include datagrams counted in ipForwDatagrams if any
708 such packets met this (discretionary) discard criterion. (counter)
709 ipOutNoRoutes − The number of IP datagrams discarded because no route
712 could be found to transmit them to their destination. Note that this
713 counter includes any packets counted in ipForwDatagrams which meet this
714 "no-route" criterion. Note that this includes any datagrams that a host
715 cannot route because all its default gateways are down. (counter)
716 ipReasmTimeout − The maximum number of seconds that received fragments
719 are held while they are awaiting reassembly at this entity. (int)
720 ipReasmReqds − The number of IP fragments received that needed to be
723 reassembled at this entity. (counter)
724 ipReasmOKs − The number of IP datagrams successfully reassembled.
727 (counter)
728 ipReasmFails − The number of failures detected by the IP reassembly
731 algorithm, for whatever reason: timed out, errors, and the like. Note
732 that this is not necessarily a count of discarded IP fragments since
733 some algorithms (notably the algorithm in RFC 815) can lose track of
734 the number of fragments by combining them as they are received.
735 (counter)
736 ipFragOKs − The number of IP datagrams that have been successfully
739 fragmented at this entity. (counter)
740 ipFragFails − The number of IP datagrams that have been discarded
743 because they needed to be fragmented at this entity but could not be,
744 for example, because their "Don't Fragment" flag was set. (counter)
745 ipFragCreates − The number of IP datagram fragments that have been gen‐
748 erated as a result of fragmentation at this entity. (counter)
749 ipRoutingDiscards − The number of routing entries that were chosen to
752 be discarded even though they were valid. One possible reason for dis‐
753 carding such an entry could be to free-up buffer space for other rout‐
754 ing entries. (counter) Returns a fixed value of 0.
755 ipAddrTable
757 ipAddrTable is a table of addressing information relevant to this
758 entity's IP addresses.
759 ipAdEntAddr − The IP address to which this entry's addressing informa‐
762 tion pertains. (netaddress)
763 ipAdEntIfIndex − The index value that uniquely identifies the interface
766 to which this entry is applicable. The interface identified by a par‐
767 ticular value of this index is the same interface as identified by the
768 same value of ifIndex. (int)
769 ipAdEntNetMask − The subnet mask associated with the IP address of this
772 entry. The value of the mask is an IP address with all the network bits
773 set to 1, and all the hosts bits set to 0. (netaddress)
774 ipAdEntBcastAddr − The value of the least-significant bit in the IP
777 broadcast address used for sending datagrams on the (logical) interface
778 associated with the IP address of this entry. For example, when the
779 Internet standard all-ones broadcast address is used, the value will be
780 1. This value applies to both the subnet and network broadcasts
781 addresses used by the entity on this (logical) interface. (int) Returns
782 a fixed value of 1.
783 ipAdEntReasmMaxSize − The size of the largest IP datagram that this
786 entity can reassemble from incoming IP fragmented datagrams received on
787 this interface. (int) Returns a fixed value of 65535.
788 ipRouteTable
790 The ipRouteTable is this entity's IP Routing table.
791 ipRouteDest − The destination IP address of this route. An entry with a
794 value of 0.0.0.0 is considered a default route. Multiple routes to a
795 single destination can appear in the table, but access to such multiple
796 entries is dependent on the table- access mechanisms defined by the
797 network management protocol in use. (netaddress)
798 ipRouteIfIndex − The index value that uniquely identifies the local
801 interface through which the next hop of this route should be reached.
802 The interface identified by a particular value of this index is the
803 same interface as identified by the same value of ifIndex. (int)
804 ipRouteMetric1 − The primary routing metric for this route. The seman‐
807 tics of this metric are determined by the routing-protocol specified in
808 the route's ipRouteProto value. If this metric is not used, its value
809 should be set to −1. (int) Returns a fixed value of −1.
810 ipRouteMetric2 − An alternate routing metric for this route. The seman‐
813 tics of this metric are determined by the routing-protocol specified in
814 the route's ipRouteProto value. If this metric is not used, its value
815 should be set to −1. (int) Returns a fixed value of −1.
816 ipRouteMetric3 − An alternate routing metric for this route. The seman‐
819 tics of this metric are determined by the routing-protocol specified in
820 the route's ipRouteProto value. If this metric is not used, its value
821 should be set to −1. (int) Returns a fixed value of −1.
822 ipRouteMetric4 − An alternate routing metric for this route. The seman‐
825 tics of this metric are determined by the routing-protocol specified in
826 the route's ipRouteProto value. If this metric is not used, its value
827 should be set to −1. (int) Returns a fixed value of −1.
828 ipRouteNextHop − The IP address of the next hop of this route. (In the
831 case of a route bound to an interface that is realized via a broadcast
832 media, the value of this field is the agent's IP address on that inter‐
833 face.) (netaddress)
834 ipRouteType − The type of route. Note that the values direct (3) and
837 indirect (4) refer to the notion of direct and indirect routing in the
838 IP architecture. (enum)
839 Setting this object to the value invalid (2) has the effect of invali‐
842 dating the corresponding entry in the ipRouteTable object. That is, it
843 effectively dissociates the destination identified with said entry from
844 the route identified with said entry. It is an implementation-specific
845 matter as to whether the agent removes an invalidated entry from the
846 table. Accordingly, management stations must be prepared to receive
847 tabular information from agents that corresponds to entries not cur‐
848 rently in use. Proper interpretation of such entries requires examina‐
849 tion of the relevant ipRouteType object.
850 ipRouteProto − The routing mechanism through which this route was
853 learned. Inclusion of values for gateway routing protocols is not
854 intended to imply that hosts should support those protocols. (enum)
855 ipRouteAge − The number of seconds since this route was last updated or
858 otherwise determined to be correct. Note that no semantics of "too old"
859 can be implied except through knowledge of the routing protocol by
860 which the route was learned. (int) Returns a fixed value of 0.
861 ipRouteMask − Indicate the mask to be logical-ANDed with the destina‐
864 tion address before being compared to the value in the ipRouteDest
865 field. For those systems that do not support arbitrary subnet masks, an
866 agent constructs the value of the ipRouteMask by determining whether
867 the value of the correspondent ipRouteDest field belongs to a class-A,
868 B, or C network, and then using one of:
869 Mask Network
874 255.0.0.0 class-A
875 255.255.0.0 class-B
876 255.255.255.0 class-C
877 If the value of the ipRouteDest is 0.0.0.0 (a default route), then the
881 mask value is also 0.0.0.0. It should be noted that all IP routing sub‐
882 systems implicitly use this mechanism. (netaddress)
883 ipRouteMetric5 − An alternate routing metric for this route. The seman‐
886 tics of this metric are determined by the routing-protocol specified in
887 the route's ipRouteProto value. If this metric is not used, its value
888 should be set to −1. (int) Returns a fixed value of −1.
889 ipRouteInfo − A reference to MIB definitions specific to the particular
892 routing protocol responsible for this route, as determined by the value
893 specified in the route's ipRouteProto value. If this information is not
894 present, its value should be set to the OBJECT IDENTIFIER { 0 0 },
895 which is a syntactically valid object identifier. Any conformant imple‐
896 mentation of ASN.1 and BER must be able to generate and recognize this
897 value. (objectid)
898 ipNetToMediaTable
900 The ipNetToMediaTable is the IP Address Translation table used for map‐
901 ping from IP addresses to physical addresses.
902 ipNetToMediaIfIndex − The interface on which this entry's equivalence
905 is effective. The interface identified by a particular value of this
906 index is the same interface as identified by the same value of ifIndex.
907 (int)
908 ipNetToMediaPhysAddress − The media-dependent physical address.
911 (octet[128])
912 ipNetToMediaNetAddress − The IpAddress corresponding to the media-
915 dependent physical address. (netaddress)
916 ipNetToMediaType − The type of mapping. (enum) Returns a fixed value of
919 (3)dynamic. Setting this object to the value invalid(2) has the effect
920 of invalidating the corresponding entry in the ipNetToMediaTable. That
921 is, it effectively dissociates the interface identified with said entry
922 from the mapping identified with said entry. It is an implementation-
923 specific matter as to whether the agent removes an invalidated entry
924 from the table. Accordingly, management stations must be prepared to
925 receive tabular information from agents that corresponds to entries not
926 currently in use. Proper interpretation of such entries requires exami‐
927 nation of the relevant ipNetToMediaType object.
928 icmp
930 The icmp group reports statistics about the ICMP group.
931 icmpInMsgs − The total number of ICMP messages that the entity
934 received. Note that this counter includes all those counted by icmpIn‐
935 Errors. (counter)
936 icmpInErrors − The number of ICMP messages that the entity received but
939 determined as having ICMP-specific errors (bad ICMP checksums, bad
940 length, and the like.). (counter)
941 icmpInDestUnreachs − The number of ICMP Destination Unreachable mes‐
944 sages received. (counter)
945 icmpInTimeExcds − The number of ICMP Time Exceeded messages received.
948 (counter)
949 icmpInParmProbs − The number of ICMP Parameter Problem messages
952 received. (counter)
953 icmpInSrcQuenchs − The number of ICMP Source Quench messages received.
956 (counter)
957 icmpInRedirects − The number of ICMP Redirect messages received.
960 (counter)
961 icmpInEchos − The number of ICMP Echo (request) messages received.
964 (counter)
965 icmpInEchoReps − The number of ICMP Echo Reply messages received.
968 (counter)
969 icmpInTimestamps − The number of ICMP Timestamp (request) messages
972 received. (counter)
973 icmpInTimestampReps − The number of ICMP Timestamp Reply messages
976 received. (counter)
977 icmpInAddrMasks − The number of ICMP Address Mask Request messages
980 received. (counter)
981 icmpInAddrMaskReps − The number of ICMP Address Mask Reply messages
984 received. (counter)
985 icmpOutMsgs − The total number of ICMP messages that this entity
988 attempted to send. Note that this counter includes all those counted by
989 icmpOutErrors. (counter)
990 icmpOutErrors − The number of ICMP messages that this entity did not
993 send due to problems discovered within ICMP, such as a lack of buffers.
994 This value should not include errors discovered outside the ICMP layer,
995 such as the inability of IP to route the resultant datagram. In some
996 implementations there may be no types of errors that contribute to this
997 counter's value. (counter)
998 icmpOutDestUnreachs − The number of ICMP Destination Unreachable mes‐
1001 sages sent. (counter)
1002 icmpOutTimeExcds − The number of ICMP Time Exceeded messages sent.
1005 (counter)
1006 icmpOutParmProbs − The number of ICMP Parameter Problem messages sent.
1009 (counter)
1010 icmpOutSrcQuenchs − The number of ICMP Source Quench messages sent.
1013 (counter)
1014 icmpOutRedirects − The number of ICMP Redirect messages sent. For a
1017 host, this object will always be zero, since hosts do not send redi‐
1018 rects. (counter)
1019 icmpOutEchos − The number of ICMP Echo (request) messages sent.
1022 (counter)
1023 icmpOutEchoReps − The number of ICMP Echo Reply messages sent.
1026 (counter)
1027 icmpOutTimestamps − The number of ICMP Timestamp (request) messages
1030 sent. (counter)
1031 icmpOutTimestampReps − The number of ICMP Timestamp Reply messages
1034 sent. (counter)
1035 icmpOutAddrMasks − The number of ICMP Address Mask Request messages
1038 sent. (counter)
1039 icmpOutAddrMaskReps − The number of ICMP Address Mask Reply messages
1042 sent. (counter)
1043 tcp
1045 The tcp group reports statistics about the TCP group.
1046 tcpRtoAlgorithm − The algorithm used to determine the timeout value
1049 used for retransmitting unacknowledged octets. (enum)
1050 tcpRtoMin − The minimum value permitted by a TCP implementation for the
1053 retransmission timeout, measured in milliseconds. More refined seman‐
1054 tics for objects of this type depend upon the algorithm used to deter‐
1055 mine the retransmission timeout. In particular, when the timeout algo‐
1056 rithm is rsre(3), an object of this type has the semantics of the
1057 LBOUND quantity described in RFC 793. (int)
1058 tcpRtoMax − The maximum value permitted by a TCP implementation for the
1061 retransmission timeout, measured in milliseconds. More refined seman‐
1062 tics for objects of this type depend upon the algorithm used to deter‐
1063 mine the retransmission timeout. In particular, when the timeout algo‐
1064 rithm is rsre(3), an object of this type has the semantics of the
1065 UBOUND quantity described in RFC 793. (int)
1066 tcpMaxConn − The limit on the total number of TCP connections that the
1069 entity can support. In entities where the maximum number of connections
1070 is dynamic, this object should contain the value -1. (int)
1071 tcpActiveOpens − The number of times that TCP connections have made a
1074 direct transition to the SYN-SENT state from the CLOSED state.
1075 (counter)
1076 tcpPassiveOpens − The number of times that TCP connections have made a
1079 direct transition to the SYN-RCVD state from the LISTEN state.
1080 (counter)
1081 tcpAttemptFails − The number of times that TCP connections have made a
1084 direct transition to the CLOSED state from either the SYN-SENT state or
1085 the SYN-RCVD state, plus the number of times TCP connections have made
1086 a direct transition to the LISTEN state from the SYN-RCVD state.
1087 (counter)
1088 tcpEstabResets − The number of times TCP connections have made a direct
1091 transition to the CLOSED state from either the ESTABLISHED state or the
1092 CLOSE-WAIT state. (counter)
1093 tcpCurrEstab − The number of TCP connections for which the current
1096 state is either ESTABLISHED or CLOSE-WAIT. (gauge)
1097 tcpInSegs − The total number of segments received, including those
1100 received in error. This count includes segments received on currently
1101 established connections. (counter)
1102 tcpOutSegs − The total number of segments sent, including those on cur‐
1105 rent connections but excluding those containing only retransmitted
1106 octets. (counter)
1107 tcpRetransSegs − The total number of segments retransmitted - that is,
1110 the number of TCP segments transmitted containing one or more previ‐
1111 ously transmitted octets. (counter)
1112 tcpInErrs − The total number of segments received in error (for exam‐
1115 ple, bad TCP checksums). (counter)
1116 tcpOutRsts − The number of TCP segments sent containing the RST flag.
1119 (counter)
1120 tcpConnTable
1122 The tcpConnTable is a table containing TCP connection-specific informa‐
1123 tion.
1124 tcpConnState − The state of this TCP connection. (enum)
1127 The only value that may be set by a management station is
1130 deleteTCB(12). Accordingly, it is appropriate for an agent to return a
1131 "badValue" response if a management station attempts to set this object
1132 to any other value.
1133 If a management station sets this object to the value deleteTCB(12),
1136 then this has the effect of deleting the TCB (as defined in RFC 793) of
1137 the corresponding connection on the managed node. This results in imme‐
1138 diate termination of the connection.
1139 As an implementation-specific option, an RST segment may be sent from
1142 the managed node to the other TCP endpoint. (Note, however, that RST
1143 segments are not sent reliably.)
1144 tcpConnLocalAddress − The local IP address for this TCP connection. For
1147 a connection in the listen state that is willing to accept connections
1148 for any IP interface associated with the node, the value 0.0.0.0 is
1149 used. (netaddress)
1150 tcpConnLocalPort − The local port number for this TCP connection. (int)
1153 tcpConnRemAddress − The remote IP address for this TCP connection.
1156 (netaddress)
1157 tcpConnRemPort − The remote port number for this TCP connection. (int)
1160 upd
1162 The udp group reports statistics about the UDP group.
1163 udpInDatagrams − The total number of UDP datagrams delivered to UDP
1166 users. (counter) Returns a fixed value of 0.
1167 udpNoPorts − The total number of received UDP datagrams for which there
1170 was no application at the destination port. (counter) Returns a fixed
1171 value of 0.
1172 udpInErrors − The number of received UDP datagrams that could not be
1175 delivered for reasons other than the lack of an application at the des‐
1176 tination port. (counter)
1177 udpOutDatagrams − The total number of UDP datagrams sent from this
1180 entity. (counter) Returns a fixed value of 0.
1181 udpTable
1183 The udpTable is a table containing UDP listener information.
1184 udpLocalAddress − The local IP address for this UDP listener. For a UDP
1187 listener that is willing to accept datagrams for any IP interface asso‐
1188 ciated with the node, the value 0.0.0.0 is used. (netaddress)
1189 udpLocalPort − The local port number for this UDP listener. (int)
1192 snmp
1194 The snmp group reports statistics about the SNMP group.
1195 snmpInPkts − The total number of Messages delivered to the SNMP entity
1198 from the transport service. (counter)
1199 snmpOutPkts − The total number of SNMP Messages passed from the SNMP
1202 protocol entity to the transport service. (counter)
1203 snmpInBadVersions − The total number of SNMP Messages delivered to the
1206 SNMP protocol entity that were for an unsupported SNMP version.
1207 (counter)
1208 snmpInBadCommunityNames − The total number of SNMP Messages delivered
1211 to the SNMP protocol entity that used a SNMP community name not known
1212 to said entity. (counter)
1213 snmpInBadCommunityUses − The total number of SNMP Messages delivered to
1216 the SNMP protocol entity, which represented an SNMP operation not
1217 allowed by the SNMP community named in the Message. (counter)
1218 snmpInASNParseErrs − The total number of ASN.1 or BER errors encoun‐
1221 tered by the SNMP protocol entity when decoding received SNMP Messages.
1222 (counter)
1223 snmpInTooBigs − The total number of SNMP PDUs delivered to the SNMP
1226 protocol entity for which the value of the error-status field is
1227 "tooBig." (counter)
1228 snmpInNoSuchNames − The total number of SNMP PDUs delivered to the SNMP
1231 protocol entity for which the value of the error-status field is
1232 "noSuchName." (counter)
1233 snmpInBadValues − The total number of SNMP PDUs delivered to the SNMP
1236 protocol entity for which the value of the error-status field is "bad‐
1237 Value." (counter)
1238 snmpInReadOnlys − The total number valid SNMP PDUs delivered to the
1241 SNMP protocol entity for which the value of the error-status field is
1242 "readOnly." It should be noted that it is a protocol error to generate
1243 an SNMP PDU that contains the value "readOnly" in the error-status
1244 field. This object is provided as a means of detecting incorrect imple‐
1245 mentations of the SNMP. (counter)
1246 snmpInGenErrs − The total number of SNMP PDUs delivered to the SNMP
1249 protocol entity for which the value of the error-status field is "gen‐
1250 Err." (counter)
1251 snmpInTotalReqVars − The total number of MIB objects successfully
1254 retrieved by the SNMP protocol entity as the result of receiving valid
1255 SNMP Get-Request and Get-Next PDUs. (counter)
1256 snmpInTotalSetVars − The total number of MIB objects successfully
1259 altered by the SNMP protocol entity as the result of receiving valid
1260 SNMP Set-Request PDUs. (counter)
1261 snmpInGetRequests − The total number of SNMP Get-Request PDUs accepted
1264 and processed by the SNMP protocol entity. (counter)
1265 snmpInGetNexts − The total number of SNMP Get-Next PDUs accepted and
1268 processed by the SNMP protocol entity. (counter)
1269 snmpInSetRequests − The total number of SNMP Set-Request PDUs accepted
1272 and processed by the SNMP protocol entity. (counter)
1273 snmpInGetResponses − The total number of SNMP Get-Response PDUs
1276 accepted and processed by the SNMP protocol entity. (counter)
1277 snmpInTraps − The total number of SNMP Trap PDUs accepted and processed
1280 by the SNMP protocol entity. (counter)
1281 snmpOutTooBigs − The total number of SNMP PDUs generated by the SNMP
1284 protocol entity for which the value of the error-status field is
1285 "tooBig." (counter)
1286 snmpOutNoSuchNames − The total number of SNMP PDUs generated by the
1289 SNMP protocol entity for which the value of the error-status is
1290 "noSuchName." (counter)
1291 snmpOutBadValues − The total number of SNMP PDUs generated by the SNMP
1294 protocol entity for which the value of the error-status field is "bad‐
1295 Value." (counter)
1296 snmpOutGenErrs − The total number of SNMP PDUs generated by the SNMP
1299 protocol entity for which the value of the error-status field is "gen‐
1300 Err." (counter)
1301 snmpOutGetRequests − The total number of SNMP Get-Request PDUs which
1304 have been generated by the SNMP protocol entity. (counter)
1305 snmpOutGetNexts − The total number of SNMP Get-Next PDUs generated by
1308 the SNMP protocol entity. (counter)
1309 snmpOutSetRequests − The total number of SNMP Set-Request PDUs gener‐
1312 ated by the SNMP protocol entity. (counter)
1313 snmpOutGetResponses − The total number of SNMP Get-Response PDUs gener‐
1316 ated by the SNMP protocol entity. (counter)
1317 snmpOutTraps − The total number of SNMP Trap PDUs generated by the SNMP
1320 protocol entity. (counter)
1321 snmpEnableAuthenTraps − Indicates whether the SNMP agent process is
1324 permitted to generate authentication-failure traps. The value of this
1325 object overrides any configuration information. As such, it provides a
1326 means whereby all authentication-failure traps may be disabled. (enum)
1327 Note that this object must be stored in non-volatile memory, so that it
1330 remains constant between reinitializations of the network management
1331 system.
1332 The following are Sun-specific group and table definitions.
1335 sunSystem
1337 The sunSystem group reports general system information.
1338 agentDescr − The SNMP agent's description of itself. (string[255])
1341 hostID − The unique Sun hardware identifier. The value returned is four
1344 byte binary string. (octet[4])
1345 motd − The first line of /etc/motd. (string[255])
1348 unixTime − The UNIX system time. Measured in seconds since January 1,
1351 1970 GMT. (counter)
1352 sunProcessTable
1354 The sunProcessTable table reports UNIX process table information.
1355 psProcessID − The process identifier for this process. (int)
1358 psParentProcessID − The process identifier of this process's parent.
1361 (int)
1362 psProcessSize − The combined size of the data and stack segments (in
1365 kilobytes.) (int)
1366 psProcessCpuTime − The CPU time (including both user and system time)
1369 consumed so far. (int)
1370 psProcessState − The run-state of the process. (octet[4])
1373 R Runnable
1378 T Stopped
1379 P In page wait
1380 D Non-interruptable wait
1381 S Sleeping (less than 20 seconds)
1382 I Idle (more than 20 seconds)
1383 Z Zombie
1384 psProcessWaitChannel − Reason process is waiting. (octet[16])
1388 psProcessTTY − Terminal, if any, controlling this process. (octet[16])
1391 psProcessUserName − Name of the user associated with this process.
1394 (octet[16])
1395 psProcessUserID − Numeric form of the name of the user associated with
1398 this process. (int)
1399 psProcessName − Command name used to invoke this process. (octet[64])
1402 psProcessStatus − Setting this variable will cause a signal of the set
1405 value to be sent to the process. (int)
1406 sunHostPerf
1408 The sunHostPerf group reports hostperf information.
1409 rsUserProcessTime − Total number of timeticks used by user processes
1412 since the last system boot. (counter)
1413 rsNiceModeTime − Total number of timeticks used by "nice" mode since
1416 the last system boot. (counter)
1417 rsSystemProcessTime − Total number of timeticks used by system pro‐
1420 cesses since the last system boot. (counter)
1421 rsIdleModeTime − Total number of timeticks in idle mode since the last
1424 system boot. (counter)
1425 rsDiskXfer1 − Total number of disk transfers since the last boot for
1428 the first of four configured disks. (counter)
1429 rsDiskXfer2 − Total number of disk transfers since the last boot for
1432 the second of four configured disks. (counter)
1433 rsDiskXfer3 − Total number of disk transfers since the last boot for
1436 the third of four configured disks. (counter)
1437 rsDiskXfer4 − Total number of disk transfers since the last boot for
1440 the fourth of four configured disks. (counter)
1441 rsVPagesIn − Number of pages read in from disk. (counter)
1444 rsVPagesOut − Number of pages written to disk. (counter)
1447 rsVSwapIn − Number of pages swapped in. (counter)
1450 rsVSwapOut − Number of pages swapped out. (counter)
1453 rsVIntr − Number of device interrupts. (counter)
1456 rsIfInPackets − Number of input packets. (counter)
1459 rsIfOutPackets − Number of output packets. (counter)
1462 rsIfInErrors − Number of input errors. (counter)
1465 rsIfOutErrors − Number of output errors. (counter)
1468 rsIfCollisions − Number of output collisions. (counter)
1471
1473 /etc/snmp/conf/snmpd.conf configuration information
1474 /etc/snmp/conf/mibiisa.acl access control file
1477 /var/snmp/mib/sun.mib standard SNMP MIBII file
1480
1483 See attributes(5) for descriptions of the following attributes:
1484 ┌─────────────────────────────┬─────────────────────────────┐
1489 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
1490 ├─────────────────────────────┼─────────────────────────────┤
1491 │Availability │SUNWmibii │
1492 ├─────────────────────────────┼─────────────────────────────┤
1493 │Interface Stability │Obsolete │
1494 └─────────────────────────────┴─────────────────────────────┘
1495
1497 inetd(1M), select(3C), recvfrom(3SOCKET), sendto(3SOCKET),
1498 attributes(5), gld(7D)
1499
1501 cannot dispatch request
1502 The proxy cannot dispatch the request. The rest of the message
1504 indicates the cause of the failure.
1505 select(3C) failed
1508 A select(3C) call failed. The rest of the message indicates the
1510 cause of the failure.
1511 sendto(3SOCKET) failed
1514 A sendto(3SOCKET) call failed. The rest of the message indicates
1516 the cause of the failure.
1517 recvfrom(3SOCKET) failed
1520 A recvfrom(3SOCKET) call failed. The rest of the message indicates
1522 the cause of the failure.
1523 no response from system
1526 The SNMP agent on the target system does not respond to SNMP
1528 requests. This error might indicate that the SNMP agent is not run‐
1529 ning on the target system, the target system is down, or the net‐
1530 work containing the target system is unreachable.
1531 response too big
1534 The agent could not fit the results of an operation into a single
1536 SNMP message. Split large groups or tables into smaller entities.
1537 missing attribute
1540 An attribute is missing from the requested group.
1542 bad attribute type
1545 An object attribute type received from the SNMP agent that does not
1547 match the attribute type specified by the proxy agent schema. The
1548 rest of the message indicates the expected type and received type.
1549 cannot get sysUpTime
1552 The proxy agent cannot get the variable sysUpTime from the SNMP
1554 agent.
1555 sysUpTime type bad
1558 The variable sysUpTime received from the SNMP agent has the wrong
1560 data type.
1561 unknown SNMP error
1564 An unknown SNMP error was received.
1566 bad variable value
1569 The requested specified an incorrect syntax or value for a set
1571 operation.
1572 variable is read only
1575 The SNMP agent did not perform the set request because a variable
1577 to set may not be written.
1578 general error
1581 A general error was received.
1583 cannot make request PDU
1586 An error occurred building a request PDU.
1588 cannot make request varbind list
1591 An error occurred building a request variable binding list.
1593 cannot parse response PDU
1596 An error occurred parsing a response PDU.
1598 request ID - response ID mismatch
1601 The response ID does not match the request ID.
1603 string contains non-displayable characters
1606 A displayable string contains non-displayable characters.
1608 cannot open schema file
1611 An error occurred opening the proxy agent schema file.
1613 cannot parse schema file
1616 The proxy agent couldn't parse the proxy agent schema file.
1618 cannot open host file
1621 An error occurred opening the file associated with the
1623 na.snmp.hostfile keyword in /etc/snmp/conf/snmpd.conf
1624 cannot parse host file
1627 The proxy agent was unable to parse the file associated with the
1629 na.snmp.hostfile keyword in /etc/snmp/conf/snm.conf.
1630 attribute unavailable for set operations
1633 The set could not be completed because the attribute was not avail‐
1635 able for set operations.
1636
1639 The mibiisa utility returns the wrong interface speed for the SBUS FDDI
1640 interface (for example, "bf0").
1641 The mibiisa utility does not return a MAC address for the SBUS FDDI
1644 interface (for example, "bf0").
1645 Process names retrieved from mibiisa contain a leading blank space.
1648 When you change attribute values in the system group with an SNMP set
1651 request, the change is effective only as long as mibiisa is running.
1652 mibiisa does not save the changes to /etc/snmp/conf/snmpd.conf.
1653SunOS 5.11 11 Dec 2003 mibiisa(1M)