summaryrefslogtreecommitdiff
path: root/MIBS/ATM-DXI-MIB
blob: 6d4593224c3ccc72618537f35f690ad117cfc7b5 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
ATM-DXI-MIB DEFINITIONS ::= BEGIN

	IMPORTS
	enterprises
	FROM RFC1155-SMI
	OBJECT-TYPE
	FROM RFC-1212;

	atmForum	OBJECT IDENTIFIER ::= { enterprises 353 }
	atmUniDxi	OBJECT IDENTIFIER ::= { atmForum 3 }

    -- This MIB is intended to be used in either of two scenarios.
    -- In the first scenario, the DTE acts as a proxy for the DCE(s),
    -- while, in the second scenario, the DCE contains an independent
    -- SNMP agent and responds to SNMP requests directly.
    --
    -- In both these scenarios, specific DXI interfaces are identified
    -- by a single integer-valued index.  In the first scenario, the
    -- DXI interfaces that connect directly to the DTE are identified
    -- by the DTE's corresponding value of ifIndex.  The DXI interfaces
    -- that connect to the DCE are assigned interface numbers.
    -- For example, see the figure below.
    -- In this example, the numbers 4 and 5 are assigned to those
    -- DXI interfaces that are connected to the DCE(s).  The assignment
    -- of numbers to these interfaces is implementation dependent.
    -- An SNMP management station will see these as interfaces of a
    -- special type (assigned by the IETF).
    -- In the second scenario, all the DXI interfaces correspond
    -- directly to DCE interfaces.  In this case, all corresponding
    -- instances are identified by IfIndices assigned by the DCE.

--

    -- In the UNI ATM Cell Header, the VPI/VCI fields together
    -- comprise a 24-bit field.  The eight most significant bits
    -- constitute the VPI subfield, and the least significant
    -- sixteen bits constitute the VCI subfield.  All zeros is an
    -- invalid value and on ATM interfaces is used to designate a
    -- null (or empty or unassigned) cell.  Thus the valid VPI/VCI
    -- values are in the range 1 thru 2**24-1 inclusive.  These
    -- values are used for indexing certain tables in the ATM
    -- MIB(s).

    -- The ATM Data Exchange Interface (DXI) object reflects
    -- information about an ATM DXI between an ATM DCE (e.g., a DSU)
    -- and a DTE (e.g., a Router/Host).  In particular, it contains both
    -- configuration and performance information specific to the
    -- DXI. Each DXI instance typically corresponds to several DFAs.
    -- With a 24-bit DFA, the range of valid DFA index values is
    -- 1 thru 2**24 inclusive.  Note that the 24-bit binary DFA
    -- field (with values 0 thru 2**24-1) from the DXI
    -- header must be incremented by one to yield the DFA index
    -- for accessing the tables in the MIB.  The DFA consisting of
    -- all zeros (with corresponding MIB index value of 1) is
    -- reserved for the DXI Local Management Interface (LMI) with
    -- the ATM DTE.

	Dfa ::= INTEGER (1..16777215)
    -- *** For the DCEs, the mapping between the DXI
    -- *** DFA and the ATM VPI/VCI is fixed.  The LMI DFA has no
    -- *** corresponding VPI/VCI. (Refer to Annex A for the bit mapping.)

	atmDxi	OBJECT IDENTIFIER ::= { atmUniDxi 2 }

        ---
        --- This table is mandatory if supporting ATM DXI.
        ---

	atmDxiConfTable   OBJECT-TYPE
	SYNTAX  SEQUENCE OF AtmDxiConfEntry
	ACCESS  not-accessible
	STATUS  mandatory
	DESCRIPTION
	"This table contains
	ATM DXI configuration information
	including information on the mode supported
	across the DXI."
	::= { atmDxi 2 }

	atmDxiConfEntry  OBJECT-TYPE
	SYNTAX    AtmDxiConfEntry
	ACCESS    not-accessible
	STATUS    mandatory
	DESCRIPTION
	"This list contains ATM DXI configuration information."
	INDEX    { atmDxiConfIfIndex }
	::= { atmDxiConfTable 1 }

	AtmDxiConfEntry  ::=
	SEQUENCE {
	atmDxiConfIfIndex
	INTEGER,
	atmDxiConfMode
	INTEGER
	}

	atmDxiConfIfIndex  OBJECT-TYPE
	SYNTAX    INTEGER
	ACCESS    read-only
	STATUS    mandatory
	DESCRIPTION
	"The value of this object identifies, for SNMP, the ATM DXI
	interface for which this entry contains management information.
	This is the same value as used to identify the IfEntry describing
	the DCE interface.  Management uses and expects this value.  In
	the proxy mode of operation, the DCE always treats this as 0, but
	preserves it in its response to the DTE.  0, the DXI value, means
	the interface over which the DXI LMI request was received."
	::= { atmDxiConfEntry 2 }

	atmDxiConfMode OBJECT-TYPE
	SYNTAX    INTEGER {
	mode1a  (1),
	mode1b  (2),
	mode2   (3)
	}
	ACCESS  read-write
	STATUS  mandatory
	DESCRIPTION
	"This object identifies the dxi mode being
	used at the atm dxi port."
	::= { atmDxiConfEntry 3 }

	atmDxiDFAConfTable  OBJECT-TYPE
	SYNTAX  SEQUENCE OF AtmDxiDFAConfEntry
	ACCESS  not-accessible
	STATUS  mandatory
	DESCRIPTION
	"This table contains configuration information about
	a particular DFA."
	::= { atmDxi 3 }

	atmDxiDFAConfEntry  OBJECT-TYPE
	SYNTAX    AtmDxiDFAConfEntry
	ACCESS    not-accessible
	STATUS    mandatory
	DESCRIPTION
	"This list contains ATM DXI DFA configuration
	information."
	INDEX    { atmDxiDFAConfIfIndex, atmDxiDFAConfDfaIndex }
	::= { atmDxiDFAConfTable 1 }

	AtmDxiDFAConfEntry  ::=
	SEQUENCE {
	atmDxiDFAConfIfIndex
	INTEGER,
	atmDxiDFAConfDfaIndex
	Dfa,
	atmDxiDFAConfAALType
	INTEGER
	}

	atmDxiDFAConfIfIndex   OBJECT-TYPE
	SYNTAX    INTEGER
	ACCESS    read-only
	STATUS    mandatory
	DESCRIPTION
	"The value of this object identifies, for SNMP, the ATM DXI
	interface for which this entry contains management information.
	This is the same value as used to identify the IfEntry describing
	the DCE interface.  Management uses and expects this value.  In
	the proxy mode of operation, the DCE always treats this as 0, but
	preserves it in its response to the DTE.  0, the DXI value, means
	the interface over which the DXI LMI request was received."
	::= { atmDxiDFAConfEntry 1 }

	atmDxiDFAConfDfaIndex   OBJECT-TYPE
	SYNTAX  Dfa
	ACCESS  read-only
	STATUS  mandatory
	DESCRIPTION
	"This object identifies the DFA instance on the DXI
	identified by atmDxiDFAConfIfIndex."
	::= { atmDxiDFAConfEntry 2 }

	atmDxiDFAConfAALType OBJECT-TYPE
	SYNTAX    INTEGER {
	unknown (1),
	none    (2),
	aal34   (3),
	aal5    (4)
	}
	ACCESS  read-write
	STATUS  mandatory
	DESCRIPTION
	"This object identifies the AAL type supported at this DFA.
	Note, if mode 2 is supported on the DXI identified by the
	corresponding instance of atmDxiDFAConfIfIndex and that
	instance of atmDxiDFAConfIfIndex identifies the DCE side
	of the DXI, then this object contains the AAL Type being
	run on the corresponding VPI/VCI on the corresponding ATM UNI
	interface."
	::= { atmDxiDFAConfEntry 3 }

	--  The following definition is for use only in Trap PDUs

	atmDxiEnterprise  OBJECT-TYPE
	SYNTAX  OBJECT IDENTIFIER
	ACCESS  not-accessible
	STATUS  mandatory
	DESCRIPTION
	"This object is included as the first ID-Value pair
	in a Trap PDU for which the Generic Trap Type field
	has the value 'enterpriseSpecific'.  The value of the
	object identifies the enterprise under whose authority
	the value of the Enterprise Trap Type field is defined."
	::= { atmDxi 4 }


	-- End of definitions for ATM DXI-MIB
 END