1-- 2-- CDDL HEADER START 3-- 4-- The contents of this file are subject to the terms of the 5-- Common Development and Distribution License, Version 1.0 only 6-- (the "License"). You may not use this file except in compliance 7-- with the License. 8-- 9-- You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE 10-- or http://www.opensolaris.org/os/licensing. 11-- See the License for the specific language governing permissions 12-- and limitations under the License. 13-- 14-- When distributing Covered Code, include this CDDL HEADER in each 15-- file and include the License file at usr/src/OPENSOLARIS.LICENSE. 16-- If applicable, add the following below this CDDL HEADER, with the 17-- fields enclosed by brackets "[]" replaced with your own identifying 18-- information: Portions Copyright [yyyy] [name of copyright owner] 19-- 20-- CDDL HEADER END 21-- 22-- Copyright 1996 Sun Microsystems, Inc. All Rights Reserved. 23-- Use is subject to license terms. 24-- 25-- #ident "%Z%%M% %I% %E% SMI" 26-- 27 28 CORE-MIB DEFINITIONS ::= BEGIN 29 30 31 IMPORTS ; 32 33 34-------------- 35-- from SMI -- 36-------------- 37 38 -- the path to the root 39 40 internet OBJECT IDENTIFIER ::= { iso(1) org(3) dod(6) 1 } 41 42 directory OBJECT IDENTIFIER ::= { internet 1 } 43 44 mgmt OBJECT IDENTIFIER ::= { internet 2 } 45 46 experimental OBJECT IDENTIFIER ::= { internet 3 } 47 48 private OBJECT IDENTIFIER ::= { internet 4 } 49 enterprises OBJECT IDENTIFIER ::= { private 1 } 50 51 security OBJECT IDENTIFIER ::= { internet 5 } 52 53 snmpV2 OBJECT IDENTIFIER ::= { internet 6 } 54 55 -- transport domains 56 snmpDomains OBJECT IDENTIFIER ::= { snmpV2 1 } 57 58 -- transport proxies 59 snmpProxys OBJECT IDENTIFIER ::= { snmpV2 2 } 60 61 -- module identities 62 snmpModules OBJECT IDENTIFIER ::= { snmpV2 3 } 63 64 65----------------- 66-- from MIB-II -- 67----------------- 68 69 70 mib-2 OBJECT IDENTIFIER ::= { mgmt 1 } 71 72 -- textual conventions 73 74 DisplayString ::= 75 OCTET STRING 76 -- This data type is used to model textual information taken 77 -- from the NVT ASCII character set. By convention, objects 78 -- with this syntax are declared as having 79 -- 80 -- SIZE (0..255) 81 82 PhysAddress ::= 83 OCTET STRING 84 -- This data type is used to model media addresses. For many 85 -- types of media, this will be in a binary representation. 86 -- For example, an ethernet address would be represented as 87 -- a string of 6 octets. 88 89 90------------------- 91-- from RFC 1271 -- 92------------------- 93 94 EntryStatus ::= INTEGER 95 { valid(1), 96 createRequest(2), 97 underCreation(3), 98 invalid(4) 99 } 100 101 -- The status of a table entry. 102 -- 103 -- Setting this object to the value invalid(4) has the 104 -- effect of invalidating the corresponding entry. 105 -- That is, it effectively disassociates the mapping 106 -- identified with said entry. 107 -- It is an implementation-specific matter as to whether 108 -- the agent removes an invalidated entry from the table. 109 -- Accordingly, management stations must be prepared to 110 -- receive tabular information from agents that corresponds 111 -- to entries currently not in use. Proper 112 -- interpretation of such entries requires examination 113 -- of the relevant EntryStatus object. 114 -- 115 -- An existing instance of this object cannot be set to 116 -- createRequest(2). This object may only be set to 117 -- createRequest(2) when this instance is created. When 118 -- this object is created, the agent may wish to create 119 -- supplemental object instances to complete a conceptual 120 -- row in this table. Immediately after completing the 121 -- create operation, the agent must set this object to 122 -- underCreation(3). 123 -- 124 -- Entries shall exist in the underCreation(3) state until 125 -- the management station is finished configuring the 126 -- entry and sets this object to valid(1) or aborts, 127 -- setting this object to invalid(4). If the agent 128 -- determines that an entry has been in the 129 -- underCreation(3) state for an abnormally long time, 130 -- it may decide that the management station has 131 -- crashed. If the agent makes this decision, 132 -- it may set this object to invalid(4) to reclaim the 133 -- entry. A prudent agent will understand that the 134 -- management station may need to wait for human input 135 -- and will allow for that possibility in its 136 -- determination of this abnormally long period. 137 138 139------------------- 140-- from RFC 1316 -- 141------------------- 142 143 InstancePointer ::= OBJECT IDENTIFIER 144 145 -- The object identifier is a pointer to a specific instance 146 -- of a MIB object in this agent's implemented MIB. By 147 -- convention, it is the first object in the conceptual row 148 -- for the instance. 149 150 151------------------- 152-- from RFC 1443 -- 153------------------- 154 155 156 TimeStamp ::= TEXTUAL-CONVENTION 157 STATUS current 158 DESCRIPTION 159 "The value of MIB-II's sysUpTime object at which a 1133 160 specific occurrence happened. The specific 161 occurrence must be defined in the description of 162 any object defined using this type." 163 SYNTAX TimeTicks 164 165 TimeInterval ::= TEXTUAL-CONVENTION 166 STATUS current 167 DESCRIPTION 168 "A period of time, measured in units of 0.01 169 seconds." 170 SYNTAX INTEGER (0..2147483647) 171 172 173------------------------ 174-- from RFC 1065/1442 -- 175------------------------ 176 177 Gauge32 ::= Gauge 178 179 Counter32 ::= Counter 180 181 182----------------- 183-- entreprises -- 184----------------- 185 186 sun OBJECT IDENTIFIER ::= { enterprises 42 } 187 messaging OBJECT IDENTIFIER ::= { sun products(2) 8 } 188 189 agents OBJECT IDENTIFIER ::= { messaging 1 } 190 private-mibs OBJECT IDENTIFIER ::= { messaging 2 } 191 192 snmpx400d OBJECT IDENTIFIER ::= { agents 1 } 193 snmpxapiad OBJECT IDENTIFIER ::= { agents 2 } 194 snmpx500d OBJECT IDENTIFIER ::= { agents 3 } 195 196 197END 198 199