projects / openwrt.git / blob
? search:
summary | shortlog | log | commit | commitdiff | tree
history | raw | HEAD
add cpmac ipv6 patch from mache
[openwrt.git] / openwrt / package / net-snmp / patches / 500-debian-subset-5.1.2-6.1.patch
1 diff -ruN net-snmp-5.1.2-orig/EXAMPLE-trap.conf net-snmp-5.1.2-5/EXAMPLE-trap.conf
2 --- net-snmp-5.1.2-orig/EXAMPLE-trap.conf 1970-01-01 01:00:00.000000000 +0100
3 +++ net-snmp-5.1.2-5/EXAMPLE-trap.conf 2005-03-13 16:17:21.000000000 +0100
4 @@ -0,0 +1,18 @@
5 +###############################################################################
6 +#
7 +# EXAMPLE.conf:
8 +# An example configuration file for configuring the ucd-snmp snmptrapd agent.
9 +#
10 +###############################################################################
11 +#
12 +# This file is intended to only be an example. If, however, you want
13 +# to use it, it should be placed in /etc/snmp/snmptrapd.conf.
14 +# When the snmptrapd agent starts up, this is where it will look for it.
15 +#
16 +# All lines beginning with a '#' are comments and are intended for you
17 +# to read. All other lines are configuration commands for the agent.
18 +
19 +#
20 +# PLEASE: read the snmptrapd.conf(5) manual page as well!
21 +#
22 +
23 diff -ruN net-snmp-5.1.2-orig/EXAMPLE.conf.def net-snmp-5.1.2-5/EXAMPLE.conf.def
24 --- net-snmp-5.1.2-orig/EXAMPLE.conf.def 2003-02-25 15:04:06.000000000 +0100
25 +++ net-snmp-5.1.2-5/EXAMPLE.conf.def 2005-03-13 16:17:21.000000000 +0100
26 @@ -6,7 +6,7 @@
27 ###############################################################################
28 #
29 # This file is intended to only be an example. If, however, you want
30 -# to use it, it should be placed in SYSCONFDIR/share/snmp/snmpd.conf.
31 +# to use it, it should be placed in /etc/snmp/snmpd.conf.
32 # When the snmpd agent starts up, this is where it will look for it.
33 #
34 # You might be interested in generating your own snmpd.conf file using
35 @@ -58,31 +58,37 @@
36 # from):
37
38 # sec.name source community
39 -com2sec local localhost COMMUNITY
40 -com2sec mynetwork NETWORK/24 COMMUNITY
41 +com2sec paranoid default public
42 +#com2sec readonly default public
43 +#com2sec readwrite default private
44
45 ####
46 # Second, map the security names into group names:
47
48 # sec.model sec.name
49 -group MyRWGroup v1 local
50 -group MyRWGroup v2c local
51 -group MyRWGroup usm local
52 -group MyROGroup v1 mynetwork
53 -group MyROGroup v2c mynetwork
54 -group MyROGroup usm mynetwork
55 +group MyROSystem v1 paranoid
56 +group MyROSystem v2c paranoid
57 +group MyROSystem usm paranoid
58 +group MyROGroup v1 readonly
59 +group MyROGroup v2c readonly
60 +group MyROGroup usm readonly
61 +group MyRWGroup v1 readwrite
62 +group MyRWGroup v2c readwrite
63 +group MyRWGroup usm readwrite
64
65 ####
66 # Third, create a view for us to let the groups have rights to:
67
68 # incl/excl subtree mask
69 view all included .1 80
70 +view system included .iso.org.dod.internet.mgmt.mib-2.system
71
72 ####
73 # Finally, grant the 2 groups access to the 1 view with different
74 # write permissions:
75
76 # context sec.model sec.level match read write notif
77 +access MyROSystem "" any noauth exact system none none
78 access MyROGroup "" any noauth exact all none none
79 access MyRWGroup "" any noauth exact all all none
80
81 @@ -100,8 +106,8 @@
82 # value of an object whose value is given here will fail with an error
83 # status of notWritable.
84
85 -syslocation Right here, right now.
86 -syscontact Me <me@somewhere.org>
87 +syslocation Unknown (configure /etc/snmp/snmpd.local.conf)
88 +syscontact Root <root@localhost> (configure /etc/snmp/snmpd.local.conf)
89
90 # Example output of snmpwalk:
91 # % snmpwalk -v 1 -c public localhost system
92 @@ -135,13 +141,13 @@
93 #
94
95 # Make sure mountd is running
96 -proc mountd
97 +#proc mountd
98
99 # Make sure there are no more than 4 ntalkds running, but 0 is ok too.
100 -proc ntalkd 4
101 +#proc ntalkd 4
102
103 # Make sure at least one sendmail, but less than or equal to 10 are running.
104 -proc sendmail 10 1
105 +#proc sendmail 10 1
106
107 # A snmpwalk of the prTable would look something like this:
108 #
109 @@ -199,7 +205,7 @@
110 # ARGS: optional arguments to be passed to the program
111
112 # a simple hello world
113 -exec echotest /bin/echo hello world
114 +#exec echotest /bin/echo hello world
115
116 # Run a shell script containing:
117 #
118 @@ -250,7 +256,7 @@
119
120 # Check the / partition and make sure it contains at least 10 megs.
121
122 -disk / 10000
123 +#disk / 10000
124
125 # % snmpwalk -v 1 -c public localhost .EXTENSIBLEDOTMIB.DISKMIBNUM
126 # enterprises.ucdavis.diskTable.dskEntry.diskIndex.1 = 0
127 @@ -279,7 +285,7 @@
128 # 15MAX: Similar, but for 15 min average.
129
130 # Check for loads:
131 -load 12 14 14
132 +#load 12 14 14
133
134 # % snmpwalk -v 1 -c public localhost .EXTENSIBLEDOTMIB.LOADAVEMIBNUM
135 # enterprises.ucdavis.loadTable.laEntry.loadaveIndex.1 = 1
136 @@ -365,7 +371,7 @@
137 # (commented out here since it requires that you place the
138 # script in the right location. (its not installed by default))
139
140 -# pass .EXTENSIBLEDOTMIB.255 /bin/sh PREFIX/local/passtest
141 +# pass .EXTENSIBLEDOTMIB.255 /bin/sh /usr/local/passtest
142
143 # % snmpwalk -v 1 -c public localhost .EXTENSIBLEDOTMIB.255
144 # enterprises.ucdavis.255.1 = "life the universe and everything"
145 diff -ruN net-snmp-5.1.2-orig/FAQ net-snmp-5.1.2-5/FAQ
146 --- net-snmp-5.1.2-orig/FAQ 2004-08-07 10:02:45.000000000 +0200
147 +++ net-snmp-5.1.2-5/FAQ 2005-03-13 16:17:21.000000000 +0100
148 @@ -104,7 +104,7 @@
149 I don't understand the new access control stuff - what does it mean?
150 How do I configure SNMPv3 users?
151 The 'createUser' line disappears when I start the agent. Why?
152 - What's the difference between /var/ucd-snmp and /usr/local/share/snmp?
153 + What's the difference between /var/ucd-snmp and /usr/share/snmp?
154 My new agent is ignoring the old snmpd.conf file. Why?
155 Why am I getting "Connection refused"?
156 I'm getting errors about "bad security model" - why?
157 @@ -620,7 +620,7 @@
158
159 Firstly,
160
161 - cp MY-MIB.txt /usr/local/share/snmp/mibs
162 + cp MY-MIB.txt /usr/share/snmp/mibs
163
164 or
165
166 @@ -639,7 +639,7 @@
167 Note that you need *both* steps.
168 The first command copies the file defining the new MIB to a
169 expected location for MIB files. This defaults to
170 - /usr/local/share/snmp/mibs (or PREFIX/share/snmp/mibs if the the
171 + /usr/share/snmp/mibs (or PREFIX/share/snmp/mibs if the the
172 suite was installed into a different base location). Some
173 ready-packaged distributions (such as Linux RPM packages) may look
174 for MIB files in a different location, such as /etc/snmp/mibs - put
175 @@ -1111,7 +1111,7 @@
176 If this is the case, then you can specify this interpreter
177 explicitly as part of the trap handle directive:
178
179 - traphandle default /usr/bin/perl /usr/local/bin/log_it
180 + traphandle default /usr/bin/perl /usr/bin/log_it
181
182 Note that in this case, it's almost certain that you'll also
183 need to give the full path to the traphandle script (as shown)
184 @@ -1263,7 +1263,7 @@
185 (if appropriate) the community string to use.
186
187 Some of these (such as the MIB file location), might belong in a
188 - shared snmp.conf file (typically /usr/local/share/snmp/snmp.conf or
189 + shared snmp.conf file (typically /usr/share/snmp/snmp.conf or
190 /etc/snmp/snmp.conf) to apply to all users of the system. Others
191 (particularly the SNMPv3 security settings), are more likely to refer
192 to a particular user, and should go in a personal snmp.conf file
193 @@ -1522,7 +1522,7 @@
194
195
196 Alternatively, the tools may be looking in the wrong place.
197 - The default location for the mib files is /usr/local/share/snmp/mibs.
198 + The default location for the mib files is /usr/share/snmp/mibs.
199 Again, this is set when the suite is first configured and compiled.
200 This can be changed using the environmental variable 'MIBDIRS'
201 or the snmp.conf directive 'mibdirs'.
202 @@ -2507,11 +2507,11 @@
203
204
205
206 -What's the difference between /var/ucd-snmp and /usr/local/share/snmp?
207 +What's the difference between /var/ucd-snmp and /usr/share/snmp?
208 ---------------------------------------------------------------------
209
210 Most "static" agent configuration should go in the traditional location
211 - (typically /usr/local/share/snmp/snmpd.conf or /etc/snmp). The
212 + (typically /usr/share/snmp/snmpd.conf or /etc/snmp). The
213 /var/ucd-snmp (or /var/net-snmp) location is used for information set during
214 the running of the agent, which needs to be persistent between one run of
215 the agent and the next.
216 @@ -2531,7 +2531,7 @@
217 distribution), with the current release installed from the source.
218
219 The default location for this file with the basic distribution is
220 - /usr/local/share/snmp/snmpd.conf (or PREFIX/share/snmp/snmpd.conf).
221 + /usr/share/snmp/snmpd.conf (or PREFIX/share/snmp/snmpd.conf).
222 Ready-installed versions often look for the file as /etc/snmpd.conf,
223 or /etc/snmp/snmpd.conf. Try moving the old config file to the new
224 location, and restart the agent.
225 diff -ruN net-snmp-5.1.2-orig/Makefile.in net-snmp-5.1.2-5/Makefile.in
226 --- net-snmp-5.1.2-orig/Makefile.in 2004-08-04 14:48:14.000000000 +0200
227 +++ net-snmp-5.1.2-5/Makefile.in 2005-03-13 16:17:21.000000000 +0100
228 @@ -163,6 +163,11 @@
229 ( cd perl ; $(MAKE) clean ) ; \
230 fi
231
232 +perlrealclean:
233 + @if test -f perl/Makefile; then \
234 + ( cd perl ; $(MAKE) realclean ) ; \
235 + fi
236 +
237 #
238 # make distclean completely removes all traces of building including
239 # any files generated by configure itself.
240 diff -ruN net-snmp-5.1.2-orig/Makefile.rules net-snmp-5.1.2-5/Makefile.rules
241 --- net-snmp-5.1.2-orig/Makefile.rules 2004-02-13 23:42:28.000000000 +0100
242 +++ net-snmp-5.1.2-5/Makefile.rules 2005-03-13 16:17:21.000000000 +0100
243 @@ -301,7 +301,7 @@
244 # cleaning targets
245 #
246 clean: cleansubdirs $(OTHERCLEANTODOS)
247 - rm -f core ${OBJS} ${LOBJS} $(STANDARDCLEANTARGETS) $(OTHERCLEANTARGETS)
248 + rm -f -- core ${OBJS} ${LOBJS} $(STANDARDCLEANTARGETS) $(OTHERCLEANTARGETS)
249 rm -rf .libs
250
251 cleansubdirs:
252 diff -ruN net-snmp-5.1.2-orig/Makefile.top net-snmp-5.1.2-5/Makefile.top
253 --- net-snmp-5.1.2-orig/Makefile.top 2004-08-07 09:29:36.000000000 +0200
254 +++ net-snmp-5.1.2-5/Makefile.top 2005-03-13 16:17:21.000000000 +0100
255 @@ -27,6 +27,7 @@
256 snmplibdir = $(datadir)/snmp
257 mibdir = $(snmplibdir)/mibs
258 persistentdir = @PERSISTENT_DIRECTORY@
259 +sysconfdir = @sysconfdir@
260 INSTALL_PREFIX = @INSTALL_PREFIX@
261
262 #
263 diff -ruN net-snmp-5.1.2-orig/acconfig.h net-snmp-5.1.2-5/acconfig.h
264 --- net-snmp-5.1.2-orig/acconfig.h 2004-06-28 20:54:17.000000000 +0200
265 +++ net-snmp-5.1.2-5/acconfig.h 2005-03-13 16:17:21.000000000 +0100
266 @@ -560,6 +560,9 @@
267 /* define if you have getservbyname */
268 #undef HAVE_GETSERVBYNAME
269
270 +/* define if you have dlopen */
271 +#undef HAVE_DLOPEN
272 +
273 /* printing system */
274 #undef HAVE_LPSTAT
275 #undef LPSTAT_PATH
276 diff -ruN net-snmp-5.1.2-orig/acinclude.m4 net-snmp-5.1.2-5/acinclude.m4
277 --- net-snmp-5.1.2-orig/acinclude.m4 1970-01-01 01:00:00.000000000 +0100
278 +++ net-snmp-5.1.2-5/acinclude.m4 2005-03-13 16:17:21.000000000 +0100
279 @@ -0,0 +1,193 @@
280 +dnl @synopsis AC_PROMPT_USER_NO_DEFINE(VARIABLENAME,QUESTION,[DEFAULT])
281 +dnl
282 +dnl Asks a QUESTION and puts the results in VARIABLENAME with an optional
283 +dnl DEFAULT value if the user merely hits return.
284 +dnl
285 +dnl @version 1.15
286 +dnl @author Wes Hardaker <hardaker@users.sourceforge.net>
287 +dnl
288 +AC_DEFUN([AC_PROMPT_USER_NO_DEFINE],
289 +dnl changequote(<<, >>) dnl
290 +dnl <<
291 +[
292 +if test "x$defaults" = "xno"; then
293 +echo $ac_n "$2 ($3): $ac_c"
294 +read tmpinput
295 +if test "$tmpinput" = "" -a "$3" != ""; then
296 + tmpinput="$3"
297 +fi
298 +eval $1=\"$tmpinput\"
299 +else
300 +tmpinput="$3"
301 +eval $1=\"$tmpinput\"
302 +fi
303 +]
304 +dnl >>
305 +dnl changequote([, ])
306 +) dnl done AC_PROMPT_USER
307 +
308 +dnl @synopsis AC_PROMPT_USER(VARIABLENAME,QUESTION,[DEFAULT],QUOTED)
309 +dnl
310 +dnl Asks a QUESTION and puts the results in VARIABLENAME with an optional
311 +dnl DEFAULT value if the user merely hits return. Also calls
312 +dnl AC_DEFINE_UNQUOTED() on the VARIABLENAME for VARIABLENAMEs that should
313 +dnl be entered into the config.h file as well. If QUOTED is "quoted" then
314 +dnl the result will be defined within quotes.
315 +dnl
316 +dnl @version 1.15
317 +dnl @author Wes Hardaker <hardaker@users.sourceforge.net>
318 +dnl
319 +AC_DEFUN([AC_PROMPT_USER],
320 +[
321 +MSG_CHECK=`echo "$2" | tail -1`
322 +AC_CACHE_CHECK($MSG_CHECK, ac_cv_user_prompt_$1,
323 +[echo "" >&AC_FD_MSG
324 +AC_PROMPT_USER_NO_DEFINE($1,[$2],$3)
325 +eval ac_cv_user_prompt_$1=\$$1
326 +echo $ac_n "setting $MSG_CHECK to... $ac_c" >&AC_FD_MSG
327 +])
328 +if test "$ac_cv_user_prompt_$1" != "none"; then
329 + if test "x$4" = "xquoted" -o "x$4" = "xQUOTED"; then
330 + AC_DEFINE_UNQUOTED($1,"$ac_cv_user_prompt_$1")
331 + else
332 + AC_DEFINE_UNQUOTED($1,$ac_cv_user_prompt_$1)
333 + fi
334 +fi
335 +]) dnl
336 +
337 +dnl @synopsis AC_CHECK_STRUCT_FOR(INCLUDES,STRUCT,MEMBER,DEFINE,[no])
338 +dnl
339 +dnl Checks STRUCT for MEMBER and defines DEFINE if found.
340 +dnl
341 +dnl @version 1.15
342 +dnl @author Wes Hardaker <hardaker@users.sourceforge.net>
343 +dnl
344 +AC_DEFUN(AC_CHECK_STRUCT_FOR,[
345 +
346 +ac_safe_struct=`echo "$2" | sed 'y%./+-%__p_%'`
347 +ac_safe_member=`echo "$3" | sed 'y%./+-%__p_%'`
348 +ac_safe_all="ac_cv_struct_${ac_safe_struct}_has_${ac_safe_member}"
349 +changequote(, )dnl
350 + ac_uc_define=STRUCT_`echo "${ac_safe_struct}_HAS_${ac_safe_member}" | sed 'y%abcdefghijklmnopqrstuvwxyz./-%ABCDEFGHIJKLMNOPQRSTUVWXYZ___%'`
351 +changequote([, ])dnl
352 +
353 +AC_MSG_CHECKING([for $2.$3])
354 +AC_CACHE_VAL($ac_safe_all,
355 +[
356 +if test "x$4" = "x"; then
357 + defineit="= 0"
358 +elif test "x$4" = "xno"; then
359 + defineit=""
360 +else
361 + defineit="$4"
362 +fi
363 +AC_TRY_COMPILE([
364 +$1
365 +],[
366 +struct $2 testit;
367 +testit.$3 $defineit;
368 +], eval "${ac_safe_all}=yes", eval "${ac_safe_all}=no" )
369 +])
370 +
371 +if eval "test \"x$`echo ${ac_safe_all}`\" = \"xyes\""; then
372 + AC_MSG_RESULT(yes)
373 + AC_DEFINE_UNQUOTED($ac_uc_define)
374 +else
375 + AC_MSG_RESULT(no)
376 +fi
377 +
378 +])
379 +
380 +dnl AC_CHECK_IFNET_FOR(SUBSTRUCT,[no])
381 +AC_DEFUN(AC_CHECK_IFNET_FOR,[
382 +dnl check for $1 in struct ifnet
383 +AC_CHECK_STRUCT_FOR([
384 +#ifdef IFNET_NEEDS_KERNEL
385 +#define _KERNEL 1
386 +#endif
387 +#include <sys/types.h>
388 +#include <sys/socket.h>
389 +#ifdef HAVE_SYS_TIME_H
390 +#include <sys/time.h>
391 +#endif
392 +#include <net/if.h>
393 +#ifdef HAVE_NET_IF_VAR_H
394 +#include <net/if_var.h>
395 +#endif
396 +#ifdef HAVE_SYS_QUEUE_H
397 +#include <sys/queue.h>
398 +#endif
399 +#ifdef linux
400 +struct ifnet {
401 + char *if_name; /* name, e.g. "en" or "lo" */
402 + short if_unit; /* sub-unit for lower level driver */
403 + short if_mtu; /* maximum transmission unit */
404 + short if_flags; /* up/down, broadcast, etc. */
405 + int if_metric; /* routing metric (external only) */
406 + char if_hwaddr [6]; /* ethernet address */
407 + int if_type; /* interface type: 1=generic,
408 + 28=slip, ether=6, loopback=24 */
409 + int if_speed; /* interface speed: in bits/sec */
410 +
411 + struct sockaddr if_addr; /* interface's address */
412 + struct sockaddr ifu_broadaddr; /* broadcast address */
413 + struct sockaddr ia_subnetmask; /* interface's mask */
414 +
415 + struct ifqueue {
416 + int ifq_len;
417 + int ifq_drops;
418 + } if_snd; /* output queue */
419 + int if_ibytes; /* octets received on interface */
420 + int if_ipackets; /* packets received on interface */
421 + int if_ierrors; /* input errors on interface */
422 + int if_iqdrops; /* input queue overruns */
423 + int if_obytes; /* octets sent on interface */
424 + int if_opackets; /* packets sent on interface */
425 + int if_oerrors; /* output errors on interface */
426 + int if_collisions; /* collisions on csma interfaces */
427 +/* end statistics */
428 + struct ifnet *if_next;
429 +};
430 +#endif
431 +], ifnet, $1, $2)
432 +])
433 +
434 +dnl
435 +dnl Add a search path to the LIBS and CFLAGS variables
436 +dnl
437 +AC_DEFUN(AC_ADD_SEARCH_PATH,[
438 + if test "x$1" != x -a -d $1; then
439 + if test -d $1/lib; then
440 + LDFLAGS="-L$1/lib $LDFLAGS"
441 + fi
442 + if test -d $1/include; then
443 + CPPFLAGS="-I$1/include $CPPFLAGS"
444 + fi
445 + fi
446 +])
447 +
448 +dnl
449 +dnl Store information for displaying later.
450 +dnl
451 +AC_DEFUN(AC_MSG_CACHE_INIT,[
452 + rm -f configure-summary
453 +])
454 +
455 +AC_DEFUN(AC_MSG_CACHE_ADD,[
456 + cat >> configure-summary << EOF
457 + $1
458 +EOF
459 +])
460 +
461 +AC_DEFUN(AC_MSG_CACHE_DISPLAY,[
462 + echo ""
463 + echo "---------------------------------------------------------"
464 + echo " Net-SNMP configuration summary:"
465 + echo "---------------------------------------------------------"
466 + echo ""
467 + cat configure-summary
468 + echo ""
469 + echo "---------------------------------------------------------"
470 + echo ""
471 +])
472 +
473 diff -ruN net-snmp-5.1.2-orig/agent/Makefile.in net-snmp-5.1.2-5/agent/Makefile.in
474 --- net-snmp-5.1.2-orig/agent/Makefile.in 2003-10-14 15:30:48.000000000 +0200
475 +++ net-snmp-5.1.2-5/agent/Makefile.in 2005-03-13 16:17:21.000000000 +0100
476 @@ -82,7 +82,7 @@
477 # libnetsnmpagent objects
478 LIBAGENTOBJS=snmp_agent.o snmp_vars.o agent_read_config.o \
479 agent_registry.o agent_index.o agent_trap.o kernel.o \
480 - agent_handler.o @OTHERAGENTLIBOBJS@
481 + agent_handler.o @OTHERAGENTLIBOBJS@ @WRAPLIBS@
482 LLIBAGENTOBJS=snmp_agent.lo snmp_vars.lo agent_read_config.lo \
483 agent_registry.lo agent_index.lo agent_trap.lo kernel.lo \
484 agent_handler.lo @OTHERAGENTLIBLOBJS@
485 @@ -120,11 +120,11 @@
486
487
488 libnetsnmpagent.$(LIB_EXTENSION)$(LIB_VERSION): ${LLIBAGENTOBJS} libnetsnmpmibs.$(LIB_EXTENSION)$(LIB_VERSION)
489 - $(LIB_LD_CMD) libnetsnmpagent.$(LIB_EXTENSION)$(LIB_VERSION) ${LLIBAGENTOBJS} $(LIB_LD_LIBS)
490 + $(LIB_LD_CMD) libnetsnmpagent.$(LIB_EXTENSION)$(LIB_VERSION) ${LLIBAGENTOBJS} $(LIB_LD_LIBS) $(AGENT_RELINK_LIBS)
491 $(RANLIB) libnetsnmpagent.$(LIB_EXTENSION)$(LIB_VERSION)
492
493 libnetsnmpmibs.$(LIB_EXTENSION)$(LIB_VERSION): ${LMIBOBJS}
494 - $(LIB_LD_CMD) libnetsnmpmibs.$(LIB_EXTENSION)$(LIB_VERSION) ${LMIBOBJS} $(LIB_LD_LIBS)
495 + $(LIB_LD_CMD) libnetsnmpmibs.$(LIB_EXTENSION)$(LIB_VERSION) ${LMIBOBJS} $(LIB_LD_LIBS) $(MIBS_RELINK_LIBS) $(LIBSENSORS)
496 $(RANLIB) libnetsnmpmibs.$(LIB_EXTENSION)$(LIB_VERSION)
497
498 embedperlinstall:
499 diff -ruN net-snmp-5.1.2-orig/agent/helpers/Makefile.in net-snmp-5.1.2-5/agent/helpers/Makefile.in
500 --- net-snmp-5.1.2-orig/agent/helpers/Makefile.in 2004-03-01 06:26:12.000000000 +0100
501 +++ net-snmp-5.1.2-5/agent/helpers/Makefile.in 2005-03-13 16:17:21.000000000 +0100
502 @@ -68,5 +68,5 @@
503 all: standardall
504
505 libnetsnmphelpers.$(LIB_EXTENSION)$(LIB_VERSION): ${LOBJS}
506 - $(LIB_LD_CMD) libnetsnmphelpers.$(LIB_EXTENSION)$(LIB_VERSION) ${LOBJS} $(LIB_LD_LIBS)
507 + $(LIB_LD_CMD) libnetsnmphelpers.$(LIB_EXTENSION)$(LIB_VERSION) ${LOBJS} $(LIB_LD_LIBS) $(HELPERS_RELINK_LIBS)
508 $(RANLIB) libnetsnmphelpers.$(LIB_EXTENSION)$(LIB_VERSION)
509 diff -ruN net-snmp-5.1.2-orig/agent/mibgroup/agentx/protocol.h net-snmp-5.1.2-5/agent/mibgroup/agentx/protocol.h
510 --- net-snmp-5.1.2-orig/agent/mibgroup/agentx/protocol.h 2002-04-20 09:30:01.000000000 +0200
511 +++ net-snmp-5.1.2-5/agent/mibgroup/agentx/protocol.h 2005-03-13 16:17:21.000000000 +0100
512 @@ -10,7 +10,7 @@
513 */
514
515 #define AGENTX_PORT 705
516 -#define AGENTX_SOCKET "/var/agentx/master"
517 +#define AGENTX_SOCKET "/var/run/agentx"
518
519 /*
520 * AgentX versions
521 diff -ruN net-snmp-5.1.2-orig/agent/mibgroup/mibII/interfaces.c net-snmp-5.1.2-5/agent/mibgroup/mibII/interfaces.c
522 --- net-snmp-5.1.2-orig/agent/mibgroup/mibII/interfaces.c 2004-07-23 02:55:41.000000000 +0200
523 +++ net-snmp-5.1.2-5/agent/mibgroup/mibII/interfaces.c 2005-03-13 16:17:21.000000000 +0100
524 @@ -1512,14 +1512,28 @@
525 struct ifreq ifrq;
526 struct ifnet **ifnetaddr_ptr;
527 FILE *devin;
528 - unsigned long rec_pkt, rec_oct, rec_err, rec_drop;
529 - unsigned long snd_pkt, snd_oct, snd_err, snd_drop, coll;
530 int i, fd;
531 conf_if_list *if_ptr;
532 +#ifdef SCNuMAX
533 + uintmax_t rec_pkt, rec_oct, rec_err, rec_drop, rec_mcast;
534 + uintmax_t snd_pkt, snd_oct, snd_err, snd_drop, coll;
535 + const char *scan_line_2_2 =
536 + "%" SCNuMAX " %" SCNuMAX " %" SCNuMAX " %" SCNuMAX
537 + " %*" SCNuMAX " %*" SCNuMAX " %*" SCNuMAX " %*" SCNuMAX
538 + " %" SCNuMAX " %" SCNuMAX " %" SCNuMAX " %" SCNuMAX
539 + " %*" SCNuMAX " %" SCNuMAX;
540 + const char *scan_line_2_0 =
541 + "%" SCNuMAX " %" SCNuMAX " %*" SCNuMAX " %*" SCNuMAX
542 + " %*" SCNuMAX " %" SCNuMAX " %" SCNuMAX " %*" SCNuMAX
543 + " %*" SCNuMAX " %" SCNuMAX;
544 +#else
545 + unsigned long rec_pkt, rec_oct, rec_err, rec_drop;
546 + unsigned long snd_pkt, snd_oct, snd_err, snd_drop, coll;
547 const char *scan_line_2_2 =
548 "%lu %lu %lu %lu %*lu %*lu %*lu %*lu %lu %lu %lu %lu %*lu %lu";
549 const char *scan_line_2_0 =
550 "%lu %lu %*lu %*lu %*lu %lu %lu %*lu %*lu %lu";
551 +#endif
552 const char *scan_line_to_use;
553 struct timeval et; /* elapsed time */
554
555 @@ -1598,6 +1612,10 @@
556 struct ifnet *nnew;
557 char *stats, *ifstart = line;
558
559 + /* Ignore interfaces with no statistics. */
560 + if (strstr(line, "No statistics available."))
561 + continue;
562 +
563 if (line[strlen(line) - 1] == '\n')
564 line[strlen(line) - 1] = '\0';
565
566 @@ -1631,7 +1649,7 @@
567 &coll) != 5)) {
568 if ((scan_line_to_use == scan_line_2_2)
569 && !strstr(line, "No statistics available"))
570 - snmp_log(LOG_ERR,
571 + snmp_log(LOG_DEBUG,
572 "/proc/net/dev data format error, line ==|%s|",
573 line);
574 continue;
575 diff -ruN net-snmp-5.1.2-orig/agent/mibgroup/smux/smux.c net-snmp-5.1.2-5/agent/mibgroup/smux/smux.c
576 --- net-snmp-5.1.2-orig/agent/mibgroup/smux/smux.c 2004-02-04 12:25:20.000000000 +0100
577 +++ net-snmp-5.1.2-5/agent/mibgroup/smux/smux.c 2005-03-13 16:17:21.000000000 +0100
578 @@ -819,14 +819,14 @@
579 passwd[string_len] = '\0';
580 if (!smux_auth_peer(oid_name, oid_name_len, passwd, fd)) {
581 snmp_log(LOG_WARNING,
582 - "refused smux peer: oid %s, password %s, descr %s\n",
583 - oid_print, passwd, descr);
584 + "refused smux peer: oid %s, descr %s\n",
585 + oid_print, descr);
586 *fail = TRUE;
587 return ptr;
588 }
589 snmp_log(LOG_INFO,
590 - "accepted smux peer: oid %s, password %s, descr %s\n",
591 - oid_print, passwd, descr);
592 + "accepted smux peer: oid %s, descr %s\n",
593 + oid_print, descr);
594 *fail = FALSE;
595 return ptr;
596 }
597 diff -ruN net-snmp-5.1.2-orig/apps/Makefile.in net-snmp-5.1.2-5/apps/Makefile.in
598 --- net-snmp-5.1.2-orig/apps/Makefile.in 2004-03-09 16:51:28.000000000 +0100
599 +++ net-snmp-5.1.2-5/apps/Makefile.in 2005-03-13 16:17:21.000000000 +0100
600 @@ -129,7 +129,7 @@
601 $(LINK) -o $@ snmpdf.$(OSUFFIX) $(LOCAL_LIBS) ${LDFLAGS} ${LIBS}
602
603 libnetsnmptrapd.$(LIB_EXTENSION)$(LIB_VERSION): $(LLIBTRAPD_OBJS)
604 - $(LIB_LD_CMD) libnetsnmptrapd.$(LIB_EXTENSION)$(LIB_VERSION) ${LLIBTRAPD_OBJS} $(LIB_LD_LIBS)
605 + $(LIB_LD_CMD) libnetsnmptrapd.$(LIB_EXTENSION)$(LIB_VERSION) ${LLIBTRAPD_OBJS} $(LIB_LD_LIBS) $(TRAPD_RELINK_LIBS)
606 $(RANLIB) libnetsnmptrapd.$(LIB_EXTENSION)$(LIB_VERSION)
607
608 snmpinforminstall:
609 diff -ruN net-snmp-5.1.2-orig/apps/snmpnetstat/if.c net-snmp-5.1.2-5/apps/snmpnetstat/if.c
610 --- net-snmp-5.1.2-orig/apps/snmpnetstat/if.c 2002-04-20 09:30:10.000000000 +0200
611 +++ net-snmp-5.1.2-5/apps/snmpnetstat/if.c 2005-03-13 16:17:21.000000000 +0100
612 @@ -300,8 +300,9 @@
613 case IFINDEX:
614 ifindex = *var->val.integer;
615 for (cur_if = if_table;
616 - cur_if->ifindex != ifindex && cur_if->ifindex != 0;
617 - cur_if++);
618 + cur_if < (if_table + cfg_nnets) &&
619 + cur_if->ifindex != ifindex &&
620 + cur_if->ifindex != 0; cur_if++);
621 if (cur_if >= (if_table + cfg_nnets)) {
622 fprintf(stderr,
623 "Inconsistent reponse from server. Aborting\n");
624 @@ -492,8 +493,14 @@
625 case IPIFINDEX:
626 ifindex = *var->val.integer;
627 for (cur_if = if_table;
628 - cur_if->ifindex != ifindex && cur_if->ifindex != 0;
629 - cur_if++);
630 + cur_if < (if_table + cfg_nnets) &&
631 + cur_if->ifindex != ifindex &&
632 + cur_if->ifindex != 0; cur_if++);
633 + if (cur_if >= (if_table + cfg_nnets)) {
634 + fprintf(stderr,
635 + "Inconsistent reponse from server. Aborting.\n");
636 + exit(0);
637 + }
638 cur_if->ifindex = ifindex;
639 break;
640 case IPADDR:
641 @@ -567,8 +574,14 @@
642 case IFINDEX:
643 ifindex = *var->val.integer;
644 for (cur_if = if_table;
645 - cur_if->ifindex != ifindex && cur_if->ifindex != 0;
646 - cur_if++);
647 + cur_if < (if_table + cfg_nnets) &&
648 + cur_if->ifindex != ifindex &&
649 + cur_if->ifindex != 0; cur_if++);
650 + if (cur_if >= (if_table + cfg_nnets)) {
651 + fprintf(stderr,
652 + "Inconsistent reponse from server. Aborting.\n");
653 + exit(0);
654 + }
655 cur_if->ifindex = ifindex;
656 break;
657 case INOCTETS:
658 diff -ruN net-snmp-5.1.2-orig/configure.in net-snmp-5.1.2-5/configure.in
659 --- net-snmp-5.1.2-orig/configure.in 2004-06-23 00:06:40.000000000 +0200
660 +++ net-snmp-5.1.2-5/configure.in 2005-03-13 16:17:21.000000000 +0100
661 @@ -161,6 +161,9 @@
662 AC_DEFINE(SNMP_NO_DEBUGGING)
663 fi
664
665 +AC_ARG_WITH(rpm,
666 +[ --without-rpm Don't use RPM even if available.])
667 +
668 AC_ARG_WITH(dmalloc,
669 [ --with-dmalloc=PATH Use dmalloc library (www.dmalloc.com)],
670 if test "x$withval" = "xyes"; then
671 @@ -1539,12 +1542,13 @@
672 AC_CHECK_LIB(RSAglue, RSA_PKCS1_RSAref)
673 fi
674
675 - AC_CHECK_LIB(crypto, EVP_md5)
676 + AC_CHECK_LIB(crypto, EVP_md5, [CRYPTOLIBS=-lcrypto], , )
677 AC_CHECK_FUNCS(AES_cfb128_encrypt)
678 fi
679 elif test "x$askedpkcs" = "xyes"; then
680 AC_CHECK_LIB(pkcs11, C_Initialize)
681 fi
682 +AC_SUBST(CRYPTOLIBS)
683
684 # Check for libraries that the agent needs
685 # saving old libraries
686 @@ -1664,8 +1668,9 @@
687 # Replace `main' with a function in -lkvm:
688 AC_CHECK_LIB(kvm, kvm_read)
689 # DYNAMIC MODULE SUPPORT
690 -AC_CHECK_LIB(dl, dlopen)
691 -AC_CHECK_FUNCS(dlopen)
692 +AC_CHECK_FUNC(dlopen, AC_DEFINE(HAVE_DLOPEN),
693 + AC_CHECK_LIB(dl, dlopen, AC_DEFINE(HAVE_DLOPEN)
694 + LIBS="${LIBS} -ldl"))
695
696 AC_CHECK_FUNCS(kvm_openfiles nlist knlist kvm_getprocs)
697 echo "$with_mib_modules" | grep "ucd-snmp/diskio" >/dev/null
698 @@ -1979,7 +1984,7 @@
699
700 AC_MSG_RESULT([$ac_cv_type_ssize_t])
701 if test $ac_cv_type_ssize_t = yes; then
702 - AC_DEFINE(HAVE_SSIZE_T)
703 + AC_DEFINE(HAVE_SSIZE_T, 1, [Define if type ssize_t is available])
704 fi
705
706 # Check ps args
707 diff -ruN net-snmp-5.1.2-orig/debian/README.Debian net-snmp-5.1.2-5/debian/README.Debian
708 diff -ruN net-snmp-5.1.2-orig/debian/changelog net-snmp-5.1.2-5/debian/changelog
709 diff -ruN net-snmp-5.1.2-orig/debian/control net-snmp-5.1.2-5/debian/control
710 diff -ruN net-snmp-5.1.2-orig/debian/copyright net-snmp-5.1.2-5/debian/copyright
711 diff -ruN net-snmp-5.1.2-orig/debian/fixman net-snmp-5.1.2-5/debian/fixman
712 diff -ruN net-snmp-5.1.2-orig/debian/libsnmp-base.dirs net-snmp-5.1.2-5/debian/libsnmp-base.dirs
713 diff -ruN net-snmp-5.1.2-orig/debian/libsnmp-base.docs net-snmp-5.1.2-5/debian/libsnmp-base.docs
714 diff -ruN net-snmp-5.1.2-orig/debian/libsnmp-base.files net-snmp-5.1.2-5/debian/libsnmp-base.files
715 diff -ruN net-snmp-5.1.2-orig/debian/libsnmp-base.postrm net-snmp-5.1.2-5/debian/libsnmp-base.postrm
716 diff -ruN net-snmp-5.1.2-orig/debian/libsnmp-base.prerm net-snmp-5.1.2-5/debian/libsnmp-base.prerm
717 diff -ruN net-snmp-5.1.2-orig/debian/libsnmp-perl.docs net-snmp-5.1.2-5/debian/libsnmp-perl.docs
718 diff -ruN net-snmp-5.1.2-orig/debian/libsnmp-perl.files net-snmp-5.1.2-5/debian/libsnmp-perl.files
719 diff -ruN net-snmp-5.1.2-orig/debian/libsnmp5-dev.files net-snmp-5.1.2-5/debian/libsnmp5-dev.files
720 diff -ruN net-snmp-5.1.2-orig/debian/libsnmp5-dev.manpages net-snmp-5.1.2-5/debian/libsnmp5-dev.manpages
721 diff -ruN net-snmp-5.1.2-orig/debian/libsnmp5.dirs net-snmp-5.1.2-5/debian/libsnmp5.dirs
722 diff -ruN net-snmp-5.1.2-orig/debian/libsnmp5.docs net-snmp-5.1.2-5/debian/libsnmp5.docs
723 diff -ruN net-snmp-5.1.2-orig/debian/libsnmp5.files net-snmp-5.1.2-5/debian/libsnmp5.files
724 diff -ruN net-snmp-5.1.2-orig/debian/libsnmp5.postinst net-snmp-5.1.2-5/debian/libsnmp5.postinst
725 diff -ruN net-snmp-5.1.2-orig/debian/libsnmp5.prerm net-snmp-5.1.2-5/debian/libsnmp5.prerm
726 diff -ruN net-snmp-5.1.2-orig/debian/manpages/encode_keychange.1 net-snmp-5.1.2-5/debian/manpages/encode_keychange.1
727 diff -ruN net-snmp-5.1.2-orig/debian/manpages/net-snmp-config.1 net-snmp-5.1.2-5/debian/manpages/net-snmp-config.1
728 diff -ruN net-snmp-5.1.2-orig/debian/manpages/snmpvacm.1 net-snmp-5.1.2-5/debian/manpages/snmpvacm.1
729 diff -ruN net-snmp-5.1.2-orig/debian/manpages/tkmib.1 net-snmp-5.1.2-5/debian/manpages/tkmib.1
730 diff -ruN net-snmp-5.1.2-orig/debian/rules net-snmp-5.1.2-5/debian/rules
731 diff -ruN net-snmp-5.1.2-orig/debian/snmp.files net-snmp-5.1.2-5/debian/snmp.files
732 diff -ruN net-snmp-5.1.2-orig/debian/snmp.manpages net-snmp-5.1.2-5/debian/snmp.manpages
733 diff -ruN net-snmp-5.1.2-orig/debian/snmp.preinst net-snmp-5.1.2-5/debian/snmp.preinst
734 diff -ruN net-snmp-5.1.2-orig/debian/snmpd.default net-snmp-5.1.2-5/debian/snmpd.default
735 diff -ruN net-snmp-5.1.2-orig/debian/snmpd.files net-snmp-5.1.2-5/debian/snmpd.files
736 diff -ruN net-snmp-5.1.2-orig/debian/snmpd.init net-snmp-5.1.2-5/debian/snmpd.init
737 diff -ruN net-snmp-5.1.2-orig/debian/snmpd.postinst net-snmp-5.1.2-5/debian/snmpd.postinst
738 diff -ruN net-snmp-5.1.2-orig/debian/snmpd.postrm net-snmp-5.1.2-5/debian/snmpd.postrm
739 diff -ruN net-snmp-5.1.2-orig/debian/tkmib.docs net-snmp-5.1.2-5/debian/tkmib.docs
740 diff -ruN net-snmp-5.1.2-orig/debian/tkmib.files net-snmp-5.1.2-5/debian/tkmib.files
741 diff -ruN net-snmp-5.1.2-orig/debian/tkmib.manpages net-snmp-5.1.2-5/debian/tkmib.manpages
742 diff -ruN net-snmp-5.1.2-orig/debian/watch net-snmp-5.1.2-5/debian/watch
743 diff -ruN net-snmp-5.1.2-orig/ipkg/libsnmp/CONTROL/control net-snmp-5.1.2-5/ipkg/libsnmp/CONTROL/control
744 diff -ruN net-snmp-5.1.2-orig/ipkg/libsnmp-dev/CONTROL/control net-snmp-5.1.2-5/ipkg/libsnmp-dev/CONTROL/control
745 diff -ruN net-snmp-5.1.2-orig/ipkg/rules net-snmp-5.1.2-5/ipkg/rules
746 diff -ruN net-snmp-5.1.2-orig/ipkg/snmp-utils/CONTROL/control net-snmp-5.1.2-5/ipkg/snmp-utils/CONTROL/control
747 diff -ruN net-snmp-5.1.2-orig/ipkg/snmpd/CONTROL/conffiles net-snmp-5.1.2-5/ipkg/snmpd/CONTROL/conffiles
748 diff -ruN net-snmp-5.1.2-orig/ipkg/snmpd/CONTROL/control net-snmp-5.1.2-5/ipkg/snmpd/CONTROL/control
749 diff -ruN net-snmp-5.1.2-orig/ipkg/snmpd/etc/default/snmpd net-snmp-5.1.2-5/ipkg/snmpd/etc/default/snmpd
750 diff -ruN net-snmp-5.1.2-orig/ipkg/snmpd/etc/init.d/snmpd net-snmp-5.1.2-5/ipkg/snmpd/etc/init.d/snmpd
751 diff -ruN net-snmp-5.1.2-orig/ipkg/snmpd/etc/snmp/snmpd.conf net-snmp-5.1.2-5/ipkg/snmpd/etc/snmp/snmpd.conf
752 diff -ruN net-snmp-5.1.2-orig/ipkg/snmpd-static/CONTROL/control net-snmp-5.1.2-5/ipkg/snmpd-static/CONTROL/control
753 diff -ruN net-snmp-5.1.2-orig/ipkg/version net-snmp-5.1.2-5/ipkg/version
754 diff -ruN net-snmp-5.1.2-orig/local/Makefile.in net-snmp-5.1.2-5/local/Makefile.in
755 --- net-snmp-5.1.2-orig/local/Makefile.in 2003-12-20 05:38:17.000000000 +0100
756 +++ net-snmp-5.1.2-5/local/Makefile.in 2005-03-13 16:17:21.000000000 +0100
757 @@ -58,7 +58,7 @@
758
759 mib2c.made: $(srcdir)/mib2c
760 if test "x$(PERLPROG)" != "x" ; then \
761 - $(PERLPROG) -p -e 's%^#!.*/perl.*%#!$(PERLPROG)%;s#/usr/local/share/snmp#$(snmplibdir)#;' ${srcdir}/mib2c > mib2c.made; \
762 + $(PERLPROG) -p -e 's%^#!.*/perl.*%#!$(PERLPROG)%;s#/usr/local/share/snmp#$(snmplibdir)#;s#/usr/local/etc/snmp#$(SNMPCONFPATH)#;' ${srcdir}/mib2c > mib2c.made; \
763 else \
764 touch mib2c.made; \
765 fi
766 diff -ruN net-snmp-5.1.2-orig/local/mib2c net-snmp-5.1.2-5/local/mib2c
767 --- net-snmp-5.1.2-orig/local/mib2c 2004-06-15 16:26:37.000000000 +0200
768 +++ net-snmp-5.1.2-5/local/mib2c 2005-03-13 16:17:21.000000000 +0100
769 @@ -56,7 +56,8 @@
770 if($ENV{MIB2C_DIR}) {
771 push @def_search_dirs, $ENV{MIB2C_DIR};
772 }
773 -push @def_search_dirs, "/usr/local/share/snmp/";
774 +push @def_search_dirs, "/etc/snmp/";
775 +push @def_search_dirs, "/usr/share/snmp/";
776
777
778 sub usage {
779 diff -ruN net-snmp-5.1.2-orig/man/mib2c.1.def net-snmp-5.1.2-5/man/mib2c.1.def
780 --- net-snmp-5.1.2-orig/man/mib2c.1.def 2003-10-02 20:04:19.000000000 +0200
781 +++ net-snmp-5.1.2-5/man/mib2c.1.def 2005-03-13 16:17:21.000000000 +0100
782 @@ -72,8 +72,9 @@
783 .TP
784 .BI -c " CONFIGFILE"
785 Use CONFIGFILE when generating code. These files will be searched for
786 -first in the current directory and then in the DATADIR directory
787 -(which is where the default mib2c configuration files can be found).
788 +first in the current directory and then in /etc/snmp
789 +(which is where the default mib2c configuration files can be found)
790 +and finally in the DATADIR directory.
791 Running mib2c without the -c CONFIGFILE option will display
792 a description of the valid values for CONFIGFILE, that is,
793 the available config files, including new ones that you might
794 diff -ruN net-snmp-5.1.2-orig/man/mib_api.3.def net-snmp-5.1.2-5/man/mib_api.3.def
795 --- net-snmp-5.1.2-orig/man/mib_api.3.def 2004-04-15 00:41:32.000000000 +0200
796 +++ net-snmp-5.1.2-5/man/mib_api.3.def 2005-03-13 16:17:21.000000000 +0100
797 @@ -5,7 +5,7 @@
798 add_module_replacement,
799 read_module, read_mib, read_all_mibs,
800 read_objid, read_module_node,
801 -get_module_node, read_objid
802 +get_module_node
803 snmp_set_mib_warnings, snmp_set_save_descriptions,
804 shutdown_mib,
805 print_mib,
806 @@ -34,9 +34,9 @@
807 .PP
808 .BI "void print_mib(FILE *" "fp" );
809 .PP
810 -.BI "int read_objid(char *" "input" ", oid *" "output" ", int *" "out_len" );
811 +.BI "int read_objid(char *" "input" ", oid *" "output" ", size_t *" "out_len" );
812 .br
813 -.BI "int get_module_node(char *" "name" ", char *" "module" ", oid *" "objid" ", int *" "objidlen" );
814 +.BI "int get_module_node(char *" "name" ", char *" "module" ", oid *" "objid" ", size_t *" "objidlen" );
815 .PP
816 .BI "void print_variable(const oid *" "objid" ", size_t " "objidlen" ", struct variable_list *" "variable" );
817 .br
818 diff -ruN net-snmp-5.1.2-orig/man/snmp_config.5.def net-snmp-5.1.2-5/man/snmp_config.5.def
819 --- net-snmp-5.1.2-orig/man/snmp_config.5.def 2003-12-10 11:41:41.000000000 +0100
820 +++ net-snmp-5.1.2-5/man/snmp_config.5.def 2005-03-13 16:17:21.000000000 +0100
821 @@ -11,7 +11,7 @@
822 found and read from. By default, the applications look for
823 configuration files in the following 4 directories, in order:
824 SYSCONFDIR/snmp,
825 -DATADIR/snmp, LIBDIR/snmp, and $HOME/.snmp. In each of these
826 +/etc/snmp, LIBDIR/snmp, and $HOME/.snmp. In each of these
827 directories, it looks for files with the extension of both
828 .IR conf " and " local.conf
829 (reading the second ones last). In this manner, there are
830 diff -ruN net-snmp-5.1.2-orig/man/snmp_trap_api.3.def net-snmp-5.1.2-5/man/snmp_trap_api.3.def
831 --- net-snmp-5.1.2-orig/man/snmp_trap_api.3.def 2003-09-29 04:58:18.000000000 +0200
832 +++ net-snmp-5.1.2-5/man/snmp_trap_api.3.def 2005-03-13 16:17:21.000000000 +0100
833 @@ -1,8 +1,7 @@
834 .TH SNMP_TRAP_API 3 "7 Mar 2002" VVERSIONINFO "Net-SNMP"
835 .UC 5
836 .SH NAME
837 -send_easy_trap, send_trap_vars, send_v2trap - send TRAPs or INFORMs
838 -from a Net-SNMP MIB module
839 +send_easy_trap, send_trap_vars, send_v2trap - send TRAPs or INFORMs from a Net-SNMP MIB module
840 .SH SYNOPSIS
841 .B #include <net-snmp/agent/agent_trap.h>
842 .PP
843 diff -ruN net-snmp-5.1.2-orig/mibs/BGP4-MIB.txt net-snmp-5.1.2-5/mibs/BGP4-MIB.txt
844 --- net-snmp-5.1.2-orig/mibs/BGP4-MIB.txt 1970-01-01 01:00:00.000000000 +0100
845 +++ net-snmp-5.1.2-5/mibs/BGP4-MIB.txt 2005-03-13 16:17:21.000000000 +0100
846 @@ -0,0 +1,929 @@
847 + BGP4-MIB DEFINITIONS ::= BEGIN
848 +
849 + IMPORTS
850 + MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
851 + IpAddress, Integer32, Counter32, Gauge32, mib-2
852 + FROM SNMPv2-SMI
853 + MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
854 + FROM SNMPv2-CONF;
855 +
856 + bgp MODULE-IDENTITY
857 + LAST-UPDATED "9902100000Z"
858 + ORGANIZATION "IETF IDR Working Group"
859 + CONTACT-INFO "E-mail: idr@merit.net
860 +
861 + Susan Hares (Editor)
862 + Merit Network
863 + 4251 Plymouth Road
864 + Suite C
865 + Ann Arbor, MI 48105-2785
866 + Tel: +1 734 936 2095
867 + Fax: +1 734 647 3185
868 + E-mail: skh@merit.edu
869 +
870 + Jeff Johnson (Editor)
871 + RedBack Networks, Inc.
872 + 1389 Moffett Park Drive
873 + Sunnyvale, CA 94089-1134
874 + Tel: +1 408 548 3516
875 + Fax: +1 408 548 3599
876 + E-mail: jeff@redback.com"
877 + DESCRIPTION
878 + "The MIB module for BGP-4."
879 + REVISION "9902100000Z"
880 + DESCRIPTION
881 + "Corrected duplicate OBJECT IDENTIFIER
882 + assignment in the conformance information."
883 + REVISION "9601080000Z"
884 + DESCRIPTION
885 + "1) Fixed the definitions of the traps to
886 + make them equivalent to their initial
887 + definition in RFC 1269.
888 + 2) Added compliance and conformance info."
889 + ::= { mib-2 15 }
890 +
891 + bgpVersion OBJECT-TYPE
892 + SYNTAX OCTET STRING (SIZE (1..255))
893 + MAX-ACCESS read-only
894 + STATUS current
895 + DESCRIPTION
896 + "Vector of supported BGP protocol version
897 + numbers. Each peer negotiates the version
898 + from this vector. Versions are identified
899 + via the string of bits contained within this
900 + object. The first octet contains bits 0 to
901 + 7, the second octet contains bits 8 to 15,
902 + and so on, with the most significant bit
903 + referring to the lowest bit number in the
904 + octet (e.g., the MSB of the first octet
905 + refers to bit 0). If a bit, i, is present
906 + and set, then the version (i+1) of the BGP
907 + is supported."
908 + ::= { bgp 1 }
909 +
910 + bgpLocalAs OBJECT-TYPE
911 + SYNTAX INTEGER (0..65535)
912 + MAX-ACCESS read-only
913 + STATUS current
914 + DESCRIPTION
915 + "The local autonomous system number."
916 + ::= { bgp 2 }
917 +
918 +
919 +
920 + -- BGP Peer table. This table contains, one entry per BGP
921 + -- peer, information about the BGP peer.
922 +
923 + bgpPeerTable OBJECT-TYPE
924 + SYNTAX SEQUENCE OF BgpPeerEntry
925 + MAX-ACCESS not-accessible
926 + STATUS current
927 + DESCRIPTION
928 + "BGP peer table. This table contains,
929 + one entry per BGP peer, information about the
930 + connections with BGP peers."
931 + ::= { bgp 3 }
932 +
933 + bgpPeerEntry OBJECT-TYPE
934 + SYNTAX BgpPeerEntry
935 + MAX-ACCESS not-accessible
936 + STATUS current
937 + DESCRIPTION
938 + "Entry containing information about the
939 + connection with a BGP peer."
940 + INDEX { bgpPeerRemoteAddr }
941 + ::= { bgpPeerTable 1 }
942 +
943 + BgpPeerEntry ::= SEQUENCE {
944 + bgpPeerIdentifier
945 + IpAddress,
946 + bgpPeerState
947 + INTEGER,
948 + bgpPeerAdminStatus
949 + INTEGER,
950 + bgpPeerNegotiatedVersion
951 + Integer32,
952 + bgpPeerLocalAddr
953 + IpAddress,
954 + bgpPeerLocalPort
955 + INTEGER,
956 + bgpPeerRemoteAddr
957 + IpAddress,
958 + bgpPeerRemotePort
959 + INTEGER,
960 + bgpPeerRemoteAs
961 + INTEGER,
962 + bgpPeerInUpdates
963 + Counter32,
964 + bgpPeerOutUpdates
965 + Counter32,
966 + bgpPeerInTotalMessages
967 + Counter32,
968 + bgpPeerOutTotalMessages
969 + Counter32,
970 + bgpPeerLastError
971 + OCTET STRING,
972 + bgpPeerFsmEstablishedTransitions
973 + Counter32,
974 + bgpPeerFsmEstablishedTime
975 + Gauge32,
976 + bgpPeerConnectRetryInterval
977 + INTEGER,
978 + bgpPeerHoldTime
979 + INTEGER,
980 + bgpPeerKeepAlive
981 + INTEGER,
982 + bgpPeerHoldTimeConfigured
983 + INTEGER,
984 + bgpPeerKeepAliveConfigured
985 + INTEGER,
986 + bgpPeerMinASOriginationInterval
987 + INTEGER,
988 + bgpPeerMinRouteAdvertisementInterval
989 + INTEGER,
990 + bgpPeerInUpdateElapsedTime
991 + Gauge32
992 + }
993 +
994 + bgpPeerIdentifier OBJECT-TYPE
995 + SYNTAX IpAddress
996 + MAX-ACCESS read-only
997 + STATUS current
998 + DESCRIPTION
999 + "The BGP Identifier of this entry's BGP peer."
1000 + ::= { bgpPeerEntry 1 }
1001 +
1002 + bgpPeerState OBJECT-TYPE
1003 + SYNTAX INTEGER {
1004 + idle(1),
1005 + connect(2),
1006 + active(3),
1007 + opensent(4),
1008 + openconfirm(5),
1009 + established(6)
1010 + }
1011 + MAX-ACCESS read-only
1012 + STATUS current
1013 + DESCRIPTION
1014 + "The BGP peer connection state."
1015 + ::= { bgpPeerEntry 2 }
1016 +
1017 + bgpPeerAdminStatus OBJECT-TYPE
1018 + SYNTAX INTEGER {
1019 + stop(1),
1020 + start(2)
1021 + }
1022 + MAX-ACCESS read-write
1023 + STATUS current
1024 + DESCRIPTION
1025 + "The desired state of the BGP connection. A
1026 + transition from 'stop' to 'start' will cause
1027 + the BGP Start Event to be generated. A
1028 + transition from 'start' to 'stop' will cause
1029 + the BGP Stop Event to be generated. This
1030 + parameter can be used to restart BGP peer
1031 + connections. Care should be used in providing
1032 + write access to this object without adequate
1033 + authentication."
1034 + ::= { bgpPeerEntry 3 }
1035 +
1036 + bgpPeerNegotiatedVersion OBJECT-TYPE
1037 + SYNTAX Integer32
1038 + MAX-ACCESS read-only
1039 + STATUS current
1040 + DESCRIPTION
1041 + "The negotiated version of BGP running between
1042 + the two peers."
1043 + ::= { bgpPeerEntry 4 }
1044 +
1045 + bgpPeerLocalAddr OBJECT-TYPE
1046 + SYNTAX IpAddress
1047 + MAX-ACCESS read-only
1048 + STATUS current
1049 + DESCRIPTION
1050 + "The local IP address of this entry's BGP
1051 + connection."
1052 + ::= { bgpPeerEntry 5 }
1053 +
1054 + bgpPeerLocalPort OBJECT-TYPE
1055 + SYNTAX INTEGER (0..65535)
1056 + MAX-ACCESS read-only
1057 + STATUS current
1058 + DESCRIPTION
1059 + "The local port for the TCP connection between
1060 + the BGP peers."
1061 + ::= { bgpPeerEntry 6 }
1062 +
1063 + bgpPeerRemoteAddr OBJECT-TYPE
1064 + SYNTAX IpAddress
1065 + MAX-ACCESS read-only
1066 + STATUS current
1067 + DESCRIPTION
1068 + "The remote IP address of this entry's BGP
1069 + peer."
1070 + ::= { bgpPeerEntry 7 }
1071 +
1072 + bgpPeerRemotePort OBJECT-TYPE
1073 + SYNTAX INTEGER (0..65535)
1074 + MAX-ACCESS read-only
1075 + STATUS current
1076 + DESCRIPTION
1077 + "The remote port for the TCP connection between
1078 + the BGP peers. Note that the objects
1079 + bgpPeerLocalAddr, bgpPeerLocalPort,
1080 + bgpPeerRemoteAddr and bgpPeerRemotePort
1081 + provide the appropriate reference to the
1082 + standard MIB TCP connection table."
1083 + ::= { bgpPeerEntry 8 }
1084 +
1085 + bgpPeerRemoteAs OBJECT-TYPE
1086 + SYNTAX INTEGER (0..65535)
1087 + MAX-ACCESS read-only
1088 + STATUS current
1089 + DESCRIPTION
1090 + "The remote autonomous system number."
1091 + ::= { bgpPeerEntry 9 }
1092 +
1093 + bgpPeerInUpdates OBJECT-TYPE
1094 + SYNTAX Counter32
1095 + MAX-ACCESS read-only
1096 + STATUS current
1097 + DESCRIPTION
1098 + "The number of BGP UPDATE messages received on
1099 + this connection. This object should be
1100 + initialized to zero (0) when the connection is
1101 + established."
1102 + ::= { bgpPeerEntry 10 }
1103 +
1104 + bgpPeerOutUpdates OBJECT-TYPE
1105 + SYNTAX Counter32
1106 + MAX-ACCESS read-only
1107 + STATUS current
1108 + DESCRIPTION
1109 + "The number of BGP UPDATE messages transmitted
1110 + on this connection. This object should be
1111 + initialized to zero (0) when the connection is
1112 + established."
1113 + ::= { bgpPeerEntry 11 }
1114 +
1115 + bgpPeerInTotalMessages OBJECT-TYPE
1116 + SYNTAX Counter32
1117 + MAX-ACCESS read-only
1118 + STATUS current
1119 + DESCRIPTION
1120 + "The total number of messages received from the
1121 + remote peer on this connection. This object
1122 + should be initialized to zero when the
1123 + connection is established."
1124 + ::= { bgpPeerEntry 12 }
1125 +
1126 + bgpPeerOutTotalMessages OBJECT-TYPE
1127 + SYNTAX Counter32
1128 + MAX-ACCESS read-only
1129 + STATUS current
1130 + DESCRIPTION
1131 + "The total number of messages transmitted to
1132 + the remote peer on this connection. This object
1133 + should be initialized to zero when the
1134 + connection is established."
1135 + ::= { bgpPeerEntry 13 }
1136 +
1137 + bgpPeerLastError OBJECT-TYPE
1138 + SYNTAX OCTET STRING (SIZE (2))
1139 + MAX-ACCESS read-only
1140 + STATUS current
1141 + DESCRIPTION
1142 + "The last error code and subcode seen by this
1143 + peer on this connection. If no error has
1144 + occurred, this field is zero. Otherwise, the
1145 + first byte of this two byte OCTET STRING
1146 + contains the error code, and the second byte
1147 + contains the subcode."
1148 + ::= { bgpPeerEntry 14 }
1149 +
1150 + bgpPeerFsmEstablishedTransitions OBJECT-TYPE
1151 + SYNTAX Counter32
1152 + MAX-ACCESS read-only
1153 + STATUS current
1154 + DESCRIPTION
1155 + "The total number of times the BGP FSM
1156 + transitioned into the established state."
1157 + ::= { bgpPeerEntry 15 }
1158 +
1159 + bgpPeerFsmEstablishedTime OBJECT-TYPE
1160 + SYNTAX Gauge32
1161 + MAX-ACCESS read-only
1162 + STATUS current
1163 + DESCRIPTION
1164 + "This timer indicates how long (in seconds) this
1165 + peer has been in the Established state or how long
1166 + since this peer was last in the Established state.
1167 + It is set to zero when a new peer is configured or
1168 + the router is booted."
1169 + ::= { bgpPeerEntry 16 }
1170 +
1171 + bgpPeerConnectRetryInterval OBJECT-TYPE
1172 + SYNTAX INTEGER (1..65535)
1173 + MAX-ACCESS read-write
1174 + STATUS current
1175 + DESCRIPTION
1176 + "Time interval in seconds for the ConnectRetry
1177 + timer. The suggested value for this timer is
1178 + 120 seconds."
1179 + ::= { bgpPeerEntry 17 }
1180 +
1181 + bgpPeerHoldTime OBJECT-TYPE
1182 + SYNTAX INTEGER ( 0 | 3..65535 )
1183 + MAX-ACCESS read-only
1184 + STATUS current
1185 + DESCRIPTION
1186 + "Time interval in seconds for the Hold Timer
1187 + established with the peer. The value of this
1188 + object is calculated by this BGP speaker by
1189 + using the smaller of the value in
1190 + bgpPeerHoldTimeConfigured and the Hold Time
1191 + received in the OPEN message. This value
1192 + must be at lease three seconds if it is not
1193 + zero (0) in which case the Hold Timer has
1194 + not been established with the peer, or, the
1195 + value of bgpPeerHoldTimeConfigured is zero (0)."
1196 + ::= { bgpPeerEntry 18 }
1197 +
1198 + bgpPeerKeepAlive OBJECT-TYPE
1199 + SYNTAX INTEGER ( 0 | 1..21845 )
1200 + MAX-ACCESS read-only
1201 + STATUS current
1202 + DESCRIPTION
1203 + "Time interval in seconds for the KeepAlive
1204 + timer established with the peer. The value of
1205 + this object is calculated by this BGP speaker
1206 + such that, when compared with bgpPeerHoldTime,
1207 + it has the same proportion as what
1208 + bgpPeerKeepAliveConfigured has when compared
1209 + with bgpPeerHoldTimeConfigured. If the value
1210 + of this object is zero (0), it indicates that
1211 + the KeepAlive timer has not been established
1212 + with the peer, or, the value of
1213 + bgpPeerKeepAliveConfigured is zero (0)."
1214 + ::= { bgpPeerEntry 19 }
1215 +
1216 + bgpPeerHoldTimeConfigured OBJECT-TYPE
1217 + SYNTAX INTEGER ( 0 | 3..65535 )
1218 + MAX-ACCESS read-write
1219 + STATUS current
1220 + DESCRIPTION
1221 + "Time interval in seconds for the Hold Time
1222 + configured for this BGP speaker with this peer.
1223 + This value is placed in an OPEN message sent to
1224 + this peer by this BGP speaker, and is compared
1225 + with the Hold Time field in an OPEN message
1226 + received from the peer when determining the Hold
1227 + Time (bgpPeerHoldTime) with the peer. This value
1228 + must not be less than three seconds if it is not
1229 + zero (0) in which case the Hold Time is NOT to be
1230 + established with the peer. The suggested value for
1231 + this timer is 90 seconds."
1232 + ::= { bgpPeerEntry 20 }
1233 +
1234 + bgpPeerKeepAliveConfigured OBJECT-TYPE
1235 + SYNTAX INTEGER ( 0 | 1..21845 )
1236 + MAX-ACCESS read-write
1237 + STATUS current
1238 + DESCRIPTION
1239 + "Time interval in seconds for the KeepAlive timer
1240 + configured for this BGP speaker with this peer.
1241 + The value of this object will only determine the
1242 + KEEPALIVE messages' frequency relative to the value
1243 + specified in bgpPeerHoldTimeConfigured; the actual
1244 + time interval for the KEEPALIVE messages is
1245 + indicated by bgpPeerKeepAlive. A reasonable
1246 + maximum value for this timer would be configured to
1247 + be one third of that of bgpPeerHoldTimeConfigured.
1248 + If the value of this object is zero (0), no
1249 + periodical KEEPALIVE messages are sent to the peer
1250 + after the BGP connection has been established. The
1251 + suggested value for this timer is 30 seconds."
1252 + ::= { bgpPeerEntry 21 }
1253 +
1254 + bgpPeerMinASOriginationInterval OBJECT-TYPE
1255 + SYNTAX INTEGER (1..65535)
1256 + MAX-ACCESS read-write
1257 + STATUS current
1258 + DESCRIPTION
1259 + "Time interval in seconds for the
1260 + MinASOriginationInterval timer.
1261 + The suggested value for this timer is 15 seconds."
1262 + ::= { bgpPeerEntry 22 }
1263 +
1264 + bgpPeerMinRouteAdvertisementInterval OBJECT-TYPE
1265 + SYNTAX INTEGER (1..65535)
1266 + MAX-ACCESS read-write
1267 + STATUS current
1268 + DESCRIPTION
1269 + "Time interval in seconds for the
1270 + MinRouteAdvertisementInterval timer.
1271 + The suggested value for this timer is 30 seconds."
1272 + ::= { bgpPeerEntry 23 }
1273 +
1274 + bgpPeerInUpdateElapsedTime OBJECT-TYPE
1275 + SYNTAX Gauge32
1276 + MAX-ACCESS read-only
1277 + STATUS current
1278 + DESCRIPTION
1279 + "Elapsed time in seconds since the last BGP
1280 + UPDATE message was received from the peer.
1281 + Each time bgpPeerInUpdates is incremented,
1282 + the value of this object is set to zero (0)."
1283 + ::= { bgpPeerEntry 24 }
1284 +
1285 +
1286 +
1287 + bgpIdentifier OBJECT-TYPE
1288 + SYNTAX IpAddress
1289 + MAX-ACCESS read-only
1290 + STATUS current
1291 + DESCRIPTION
1292 + "The BGP Identifier of local system."
1293 + ::= { bgp 4 }
1294 +
1295 +
1296 +
1297 + -- Received Path Attribute Table. This table contains,
1298 + -- one entry per path to a network, path attributes
1299 + -- received from all peers running BGP version 3 or less.
1300 + -- This table is obsolete, having been replaced in
1301 + -- functionality with the bgp4PathAttrTable.
1302 +
1303 + bgpRcvdPathAttrTable OBJECT-TYPE
1304 + SYNTAX SEQUENCE OF BgpPathAttrEntry
1305 + MAX-ACCESS not-accessible
1306 + STATUS obsolete
1307 + DESCRIPTION
1308 + "The BGP Received Path Attribute Table contains
1309 + information about paths to destination networks
1310 + received from all peers running BGP version 3 or
1311 + less."
1312 + ::= { bgp 5 }
1313 +
1314 + bgpPathAttrEntry OBJECT-TYPE
1315 + SYNTAX BgpPathAttrEntry
1316 + MAX-ACCESS not-accessible
1317 + STATUS obsolete
1318 + DESCRIPTION
1319 + "Information about a path to a network."
1320 + INDEX { bgpPathAttrDestNetwork,
1321 + bgpPathAttrPeer }
1322 + ::= { bgpRcvdPathAttrTable 1 }
1323 +
1324 + BgpPathAttrEntry ::= SEQUENCE {
1325 + bgpPathAttrPeer
1326 + IpAddress,
1327 + bgpPathAttrDestNetwork
1328 + IpAddress,
1329 + bgpPathAttrOrigin
1330 + INTEGER,
1331 + bgpPathAttrASPath
1332 + OCTET STRING,
1333 + bgpPathAttrNextHop
1334 + IpAddress,
1335 + bgpPathAttrInterASMetric
1336 + Integer32
1337 + }
1338 +
1339 + bgpPathAttrPeer OBJECT-TYPE
1340 + SYNTAX IpAddress
1341 + MAX-ACCESS read-only
1342 + STATUS obsolete
1343 + DESCRIPTION
1344 + "The IP address of the peer where the path
1345 + information was learned."
1346 + ::= { bgpPathAttrEntry 1 }
1347 +
1348 + bgpPathAttrDestNetwork OBJECT-TYPE
1349 + SYNTAX IpAddress
1350 + MAX-ACCESS read-only
1351 + STATUS obsolete
1352 + DESCRIPTION
1353 + "The address of the destination network."
1354 + ::= { bgpPathAttrEntry 2 }
1355 +
1356 + bgpPathAttrOrigin OBJECT-TYPE
1357 + SYNTAX INTEGER {
1358 + igp(1),-- networks are interior
1359 + egp(2),-- networks learned via EGP
1360 + incomplete(3) -- undetermined
1361 + }
1362 + MAX-ACCESS read-only
1363 + STATUS obsolete
1364 + DESCRIPTION
1365 + "The ultimate origin of the path information."
1366 + ::= { bgpPathAttrEntry 3 }
1367 +
1368 + bgpPathAttrASPath OBJECT-TYPE
1369 + SYNTAX OCTET STRING (SIZE (2..255))
1370 + MAX-ACCESS read-only
1371 + STATUS obsolete
1372 + DESCRIPTION
1373 + "The set of ASs that must be traversed to reach
1374 + the network. This object is probably best
1375 + represented as SEQUENCE OF INTEGER. For SMI
1376 + compatibility, though, it is represented as
1377 + OCTET STRING. Each AS is represented as a pair
1378 + of octets according to the following algorithm:
1379 +
1380 + first-byte-of-pair = ASNumber / 256;
1381 + second-byte-of-pair = ASNumber & 255;"
1382 + ::= { bgpPathAttrEntry 4 }
1383 +
1384 + bgpPathAttrNextHop OBJECT-TYPE
1385 + SYNTAX IpAddress
1386 + MAX-ACCESS read-only
1387 + STATUS obsolete
1388 + DESCRIPTION
1389 + "The address of the border router that should
1390 + be used for the destination network."
1391 + ::= { bgpPathAttrEntry 5 }
1392 +
1393 + bgpPathAttrInterASMetric OBJECT-TYPE
1394 + SYNTAX Integer32
1395 + MAX-ACCESS read-only
1396 + STATUS obsolete
1397 + DESCRIPTION
1398 + "The optional inter-AS metric. If this
1399 + attribute has not been provided for this route,
1400 + the value for this object is 0."
1401 + ::= { bgpPathAttrEntry 6 }
1402 +
1403 +
1404 +
1405 + -- BGP-4 Received Path Attribute Table. This table contains,
1406 + -- one entry per path to a network, path attributes
1407 + -- received from all peers running BGP-4.
1408 +
1409 + bgp4PathAttrTable OBJECT-TYPE
1410 + SYNTAX SEQUENCE OF Bgp4PathAttrEntry
1411 + MAX-ACCESS not-accessible
1412 + STATUS current
1413 + DESCRIPTION
1414 + "The BGP-4 Received Path Attribute Table contains
1415 + information about paths to destination networks
1416 + received from all BGP4 peers."
1417 + ::= { bgp 6 }
1418 +
1419 + bgp4PathAttrEntry OBJECT-TYPE
1420 + SYNTAX Bgp4PathAttrEntry
1421 + MAX-ACCESS not-accessible
1422 + STATUS current
1423 + DESCRIPTION
1424 + "Information about a path to a network."
1425 + INDEX { bgp4PathAttrIpAddrPrefix,
1426 + bgp4PathAttrIpAddrPrefixLen,
1427 + bgp4PathAttrPeer }
1428 + ::= { bgp4PathAttrTable 1 }
1429 +
1430 + Bgp4PathAttrEntry ::= SEQUENCE {
1431 + bgp4PathAttrPeer
1432 + IpAddress,
1433 + bgp4PathAttrIpAddrPrefixLen
1434 + INTEGER,
1435 + bgp4PathAttrIpAddrPrefix
1436 + IpAddress,
1437 + bgp4PathAttrOrigin
1438 + INTEGER,
1439 + bgp4PathAttrASPathSegment
1440 + OCTET STRING,
1441 + bgp4PathAttrNextHop
1442 + IpAddress,
1443 + bgp4PathAttrMultiExitDisc
1444 + INTEGER,
1445 + bgp4PathAttrLocalPref
1446 + INTEGER,
1447 + bgp4PathAttrAtomicAggregate
1448 + INTEGER,
1449 + bgp4PathAttrAggregatorAS
1450 + INTEGER,
1451 + bgp4PathAttrAggregatorAddr
1452 + IpAddress,
1453 + bgp4PathAttrCalcLocalPref
1454 + INTEGER,
1455 + bgp4PathAttrBest
1456 + INTEGER,
1457 + bgp4PathAttrUnknown
1458 + OCTET STRING
1459 + }
1460 +
1461 + bgp4PathAttrPeer OBJECT-TYPE
1462 + SYNTAX IpAddress
1463 + MAX-ACCESS read-only
1464 + STATUS current
1465 + DESCRIPTION
1466 + "The IP address of the peer where the path
1467 + information was learned."
1468 + ::= { bgp4PathAttrEntry 1 }
1469 + bgp4PathAttrIpAddrPrefixLen OBJECT-TYPE
1470 + SYNTAX INTEGER (0..32)
1471 + MAX-ACCESS read-only
1472 + STATUS current
1473 + DESCRIPTION
1474 + "Length in bits of the IP address prefix in the
1475 + Network Layer Reachability Information field."
1476 + ::= { bgp4PathAttrEntry 2 }
1477 +
1478 + bgp4PathAttrIpAddrPrefix OBJECT-TYPE
1479 + SYNTAX IpAddress
1480 + MAX-ACCESS read-only
1481 + STATUS current
1482 + DESCRIPTION
1483 + "An IP address prefix in the Network Layer
1484 + Reachability Information field. This object
1485 + is an IP address containing the prefix with
1486 + length specified by bgp4PathAttrIpAddrPrefixLen.
1487 + Any bits beyond the length specified by
1488 + bgp4PathAttrIpAddrPrefixLen are zeroed."
1489 + ::= { bgp4PathAttrEntry 3 }
1490 +
1491 + bgp4PathAttrOrigin OBJECT-TYPE
1492 + SYNTAX INTEGER {
1493 + igp(1),-- networks are interior
1494 + egp(2),-- networks learned via EGP
1495 + incomplete(3) -- undetermined
1496 + }
1497 + MAX-ACCESS read-only
1498 + STATUS current
1499 + DESCRIPTION
1500 + "The ultimate origin of the path information."
1501 + ::= { bgp4PathAttrEntry 4 }
1502 +
1503 + bgp4PathAttrASPathSegment OBJECT-TYPE
1504 + SYNTAX OCTET STRING (SIZE (2..255))
1505 + MAX-ACCESS read-only
1506 + STATUS current
1507 + DESCRIPTION
1508 + "The sequence of AS path segments. Each AS
1509 + path segment is represented by a triple
1510 + <type, length, value>.
1511 +
1512 + The type is a 1-octet field which has two
1513 + possible values:
1514 + 1 AS_SET: unordered set of ASs a
1515 + route in the UPDATE message
1516 + has traversed
1517 + 2 AS_SEQUENCE: ordered set of ASs
1518 + a route in the UPDATE message
1519 + has traversed.
1520 +
1521 + The length is a 1-octet field containing the
1522 + number of ASs in the value field.
1523 +
1524 + The value field contains one or more AS
1525 + numbers, each AS is represented in the octet
1526 + string as a pair of octets according to the
1527 + following algorithm:
1528 +
1529 + first-byte-of-pair = ASNumber / 256;
1530 + second-byte-of-pair = ASNumber & 255;"
1531 + ::= { bgp4PathAttrEntry 5 }
1532 +
1533 + bgp4PathAttrNextHop OBJECT-TYPE
1534 + SYNTAX IpAddress
1535 + MAX-ACCESS read-only
1536 + STATUS current
1537 + DESCRIPTION
1538 + "The address of the border router that should
1539 + be used for the destination network."
1540 + ::= { bgp4PathAttrEntry 6 }
1541 +
1542 + bgp4PathAttrMultiExitDisc OBJECT-TYPE
1543 + SYNTAX INTEGER (-1..2147483647)
1544 + MAX-ACCESS read-only
1545 + STATUS current
1546 + DESCRIPTION
1547 + "This metric is used to discriminate between
1548 + multiple exit points to an adjacent autonomous
1549 + system. A value of -1 indicates the absence of
1550 + this attribute."
1551 + ::= { bgp4PathAttrEntry 7 }
1552 +
1553 + bgp4PathAttrLocalPref OBJECT-TYPE
1554 + SYNTAX INTEGER (-1..2147483647)
1555 + MAX-ACCESS read-only
1556 + STATUS current
1557 + DESCRIPTION
1558 + "The originating BGP4 speaker's degree of
1559 + preference for an advertised route. A value of
1560 + -1 indicates the absence of this attribute."
1561 + ::= { bgp4PathAttrEntry 8 }
1562 +
1563 + bgp4PathAttrAtomicAggregate OBJECT-TYPE
1564 + SYNTAX INTEGER {
1565 + lessSpecificRrouteNotSelected(1),
1566 + lessSpecificRouteSelected(2)
1567 + }
1568 + MAX-ACCESS read-only
1569 + STATUS current
1570 + DESCRIPTION
1571 + "Whether or not a system has selected
1572 + a less specific route without selecting a
1573 + more specific route."
1574 + ::= { bgp4PathAttrEntry 9 }
1575 +
1576 + bgp4PathAttrAggregatorAS OBJECT-TYPE
1577 + SYNTAX INTEGER (0..65535)
1578 + MAX-ACCESS read-only
1579 + STATUS current
1580 + DESCRIPTION
1581 + "The AS number of the last BGP4 speaker that
1582 + performed route aggregation. A value of zero (0)
1583 + indicates the absence of this attribute."
1584 + ::= { bgp4PathAttrEntry 10 }
1585 +
1586 + bgp4PathAttrAggregatorAddr OBJECT-TYPE
1587 + SYNTAX IpAddress
1588 + MAX-ACCESS read-only
1589 + STATUS current
1590 + DESCRIPTION
1591 + "The IP address of the last BGP4 speaker that
1592 + performed route aggregation. A value of
1593 + 0.0.0.0 indicates the absence of this attribute."
1594 + ::= { bgp4PathAttrEntry 11 }
1595 +
1596 + bgp4PathAttrCalcLocalPref OBJECT-TYPE
1597 + SYNTAX INTEGER (-1..2147483647)
1598 + MAX-ACCESS read-only
1599 + STATUS current
1600 + DESCRIPTION
1601 + "The degree of preference calculated by the
1602 + receiving BGP4 speaker for an advertised route.
1603 + A value of -1 indicates the absence of this
1604 + attribute."
1605 + ::= { bgp4PathAttrEntry 12 }
1606 +
1607 + bgp4PathAttrBest OBJECT-TYPE
1608 + SYNTAX INTEGER {
1609 + false(1),-- not chosen as best route
1610 + true(2) -- chosen as best route
1611 + }
1612 + MAX-ACCESS read-only
1613 + STATUS current
1614 + DESCRIPTION
1615 + "An indication of whether or not this route
1616 + was chosen as the best BGP4 route."
1617 + ::= { bgp4PathAttrEntry 13 }
1618 +
1619 + bgp4PathAttrUnknown OBJECT-TYPE
1620 + SYNTAX OCTET STRING (SIZE(0..255))
1621 + MAX-ACCESS read-only
1622 + STATUS current
1623 + DESCRIPTION
1624 + "One or more path attributes not understood
1625 + by this BGP4 speaker. Size zero (0) indicates
1626 + the absence of such attribute(s). Octets
1627 + beyond the maximum size, if any, are not
1628 + recorded by this object."
1629 + ::= { bgp4PathAttrEntry 14 }
1630 +
1631 +
1632 + -- Traps.
1633 +
1634 + -- note that in RFC 1657, bgpTraps was incorrectly
1635 + -- assigned a value of { bgp 7 }, and each of the
1636 + -- traps had the bgpPeerRemoteAddr object inappropriately
1637 + -- removed from their OBJECTS clause. The following
1638 + -- definitions restore the semantics of the traps as
1639 + -- they were initially defined in RFC 1269.
1640 +
1641 + -- { bgp 7 } is unused
1642 +
1643 + bgpTraps OBJECT IDENTIFIER ::= { bgp 0 }
1644 +
1645 + bgpEstablished NOTIFICATION-TYPE
1646 + OBJECTS { bgpPeerRemoteAddr,
1647 + bgpPeerLastError,
1648 + bgpPeerState }
1649 + STATUS current
1650 + DESCRIPTION
1651 + "The BGP Established event is generated when
1652 + the BGP FSM enters the ESTABLISHED state."
1653 + ::= { bgpTraps 1 }
1654 +
1655 + bgpBackwardTransition NOTIFICATION-TYPE
1656 + OBJECTS { bgpPeerRemoteAddr,
1657 + bgpPeerLastError,
1658 + bgpPeerState }
1659 + STATUS current
1660 + DESCRIPTION
1661 + "The BGPBackwardTransition Event is generated
1662 + when the BGP FSM moves from a higher numbered
1663 + state to a lower numbered state."
1664 + ::= { bgpTraps 2 }
1665 +
1666 + -- conformance information
1667 +
1668 + bgpMIBConformance OBJECT IDENTIFIER ::= { bgp 8 }
1669 + bgpMIBCompliances OBJECT IDENTIFIER ::= { bgpMIBConformance 1 }
1670 + bgpMIBGroups OBJECT IDENTIFIER ::= { bgpMIBConformance 2 }
1671 +
1672 + -- compliance statements
1673 +
1674 + bgpMIBCompliance MODULE-COMPLIANCE
1675 + STATUS current
1676 + DESCRIPTION
1677 + "The compliance statement for entities which
1678 + implement the BGP4 mib."
1679 + MODULE -- this module
1680 + MANDATORY-GROUPS { bgp4MIBGlobalsGroup,
1681 + bgp4MIBPeerGroup,
1682 + bgp4MIBPathAttrGroup,
1683 + bgp4MIBNotificationGroup }
1684 + ::= { bgpMIBCompliances 1 }
1685 +
1686 + -- units of conformance
1687 +
1688 + bgp4MIBGlobalsGroup OBJECT-GROUP
1689 + OBJECTS { bgpVersion,
1690 + bgpLocalAs,
1691 + bgpIdentifier }
1692 + STATUS current
1693 + DESCRIPTION
1694 + "A collection of objects providing information
1695 + on global BGP state."
1696 + ::= { bgpMIBGroups 1 }
1697 +
1698 + bgp4MIBPeerGroup OBJECT-GROUP
1699 + OBJECTS { bgpPeerIdentifier,
1700 + bgpPeerState,
1701 + bgpPeerAdminStatus,
1702 + bgpPeerNegotiatedVersion,
1703 + bgpPeerLocalAddr,
1704 + bgpPeerLocalPort,
1705 + bgpPeerRemoteAddr,
1706 + bgpPeerRemotePort,
1707 + bgpPeerRemoteAs,
1708 + bgpPeerInUpdates,
1709 + bgpPeerOutUpdates,
1710 + bgpPeerInTotalMessages,
1711 + bgpPeerOutTotalMessages,
1712 + bgpPeerLastError,
1713 + bgpPeerFsmEstablishedTransitions,
1714 + bgpPeerFsmEstablishedTime,
1715 + bgpPeerConnectRetryInterval,
1716 + bgpPeerHoldTime,
1717 + bgpPeerKeepAlive,
1718 + bgpPeerHoldTimeConfigured,
1719 + bgpPeerKeepAliveConfigured,
1720 + bgpPeerMinASOriginationInterval,
1721 + bgpPeerMinRouteAdvertisementInterval,
1722 + bgpPeerInUpdateElapsedTime }
1723 + STATUS current
1724 + DESCRIPTION
1725 + "A collection of objects for managing
1726 + BGP peers."
1727 + ::= { bgpMIBGroups 2 }
1728 +
1729 + bgp4MIBRcvdPathAttrGroup OBJECT-GROUP
1730 + OBJECTS { bgpPathAttrPeer,
1731 + bgpPathAttrDestNetwork,
1732 + bgpPathAttrOrigin,
1733 + bgpPathAttrASPath,
1734 + bgpPathAttrNextHop,
1735 + bgpPathAttrInterASMetric }
1736 + STATUS obsolete
1737 + DESCRIPTION
1738 + "A collection of objects for managing BGP
1739 + path entries.
1740 +
1741 + This conformance group is obsolete,
1742 + replaced by bgp4MIBPathAttrGroup."
1743 + ::= { bgpMIBGroups 3 }
1744 +
1745 + bgp4MIBPathAttrGroup OBJECT-GROUP
1746 + OBJECTS { bgp4PathAttrPeer,
1747 + bgp4PathAttrIpAddrPrefixLen,
1748 + bgp4PathAttrIpAddrPrefix,
1749 + bgp4PathAttrOrigin,
1750 + bgp4PathAttrASPathSegment,
1751 + bgp4PathAttrNextHop,
1752 + bgp4PathAttrMultiExitDisc,
1753 + bgp4PathAttrLocalPref,
1754 + bgp4PathAttrAtomicAggregate,
1755 + bgp4PathAttrAggregatorAS,
1756 + bgp4PathAttrAggregatorAddr,
1757 + bgp4PathAttrCalcLocalPref,
1758 + bgp4PathAttrBest,
1759 + bgp4PathAttrUnknown }
1760 + STATUS current
1761 + DESCRIPTION
1762 + "A collection of objects for managing
1763 + BGP path entries."
1764 + ::= { bgpMIBGroups 4 }
1765 +
1766 + bgp4MIBNotificationGroup NOTIFICATION-GROUP
1767 + NOTIFICATIONS { bgpEstablished,
1768 + bgpBackwardTransition }
1769 + STATUS current
1770 + DESCRIPTION
1771 + "A collection of notifications for signaling
1772 + changes in BGP peer relationships."
1773 + ::= { bgpMIBGroups 5 }
1774 +
1775 + END
1776 diff -ruN net-snmp-5.1.2-orig/mibs/BRIDGE-MIB.txt net-snmp-5.1.2-5/mibs/BRIDGE-MIB.txt
1777 --- net-snmp-5.1.2-orig/mibs/BRIDGE-MIB.txt 1970-01-01 01:00:00.000000000 +0100
1778 +++ net-snmp-5.1.2-5/mibs/BRIDGE-MIB.txt 2005-03-13 16:17:21.000000000 +0100
1779 @@ -0,0 +1,1075 @@
1780 +BRIDGE-MIB DEFINITIONS ::= BEGIN
1781 +
1782 +IMPORTS
1783 + Counter, TimeTicks
1784 + FROM RFC1155-SMI
1785 + mib-2
1786 + FROM RFC1213-MIB
1787 + OBJECT-TYPE
1788 + FROM RFC-1212
1789 + TRAP-TYPE
1790 + FROM RFC-1215;
1791 +
1792 +-- All representations of MAC addresses in this MIB Module
1793 +-- use, as a textual convention (i.e. this convention does
1794 +-- not affect their encoding), the data type:
1795 +MacAddress ::= OCTET STRING (SIZE (6)) -- a 6 octet address
1796 + -- in the
1797 + -- "canonical"
1798 + -- order
1799 +-- defined by IEEE 802.1a, i.e., as if it were transmitted
1800 +-- least significant bit first, even though 802.5 (in
1801 +-- contrast to other n802.x protocols) requires MAC
1802 +-- addresses to be transmitted most significant bit first.
1803 +--
1804 +-- 16-bit addresses, if needed, are represented by setting
1805 +-- their upper 4 octets to all 0's, i.e., AAFF would be
1806 +-- represented as 00000000AAFF.
1807 +
1808 +-- Similarly, all representations of Bridge-Id in this MIB
1809 +-- Module use, as a textual convention (i.e. this
1810 +-- convention does not affect their encoding), the data
1811 +-- type:
1812 +BridgeId ::= OCTET STRING (SIZE (8)) -- the
1813 + -- Bridge-Identifier
1814 + -- as used in the
1815 + -- Spanning Tree
1816 +-- Protocol to uniquely identify a bridge. Its first two
1817 +-- octets (in network byte order) contain a priority
1818 +-- value and its last 6 octets contain the MAC address
1819 +-- used to refer to a bridge in a unique fashion
1820 +-- (typically, the numerically smallest MAC address
1821 +-- of all ports on the bridge).
1822 +
1823 +-- Several objects in this MIB module represent values of
1824 +-- timers used by the Spanning Tree Protocol. In this
1825 +-- MIB, these timers have values in units of hundreths of
1826 +-- a second (i.e. 1/100 secs).
1827 +-- These timers, when stored in a Spanning Tree Protocol's
1828 +-- BPDU, are in units of 1/256 seconds. Note, however,
1829 +-- that 802.1D-1990 specifies a settable granularity of
1830 +-- no more than 1 second for these timers. To avoid
1831 +-- ambiguity, a data type is defined here as a textual
1832 +-- convention and all representation of these timers
1833 +-- in this MIB module are defined using this data type. An
1834 +-- algorithm is also defined for converting between the
1835 +-- different units, to ensure a timer's value is not
1836 +-- distorted by multiple conversions.
1837 +-- The data type is:
1838 +
1839 +Timeout ::= INTEGER -- a STP timer in units of 1/100 seconds
1840 +
1841 +-- To convert a Timeout value into a value in units of
1842 +-- 1/256 seconds, the following algorithm should be used:
1843 +--
1844 +-- b = floor( (n * 256) / 100)
1845 +--
1846 +-- where:
1847 +-- floor = quotient [ignore remainder]
1848 +-- n is the value in 1/100 second units
1849 +-- b is the value in 1/256 second units
1850 +--
1851 +-- To convert the value from 1/256 second units back to
1852 +-- 1/100 seconds, the following algorithm should be used:
1853 +--
1854 +-- n = ceiling( (b * 100) / 256)
1855 +--
1856 +-- where:
1857 +-- ceiling = quotient [if remainder is 0], or
1858 +-- quotient + 1 [if remainder is non-zero]
1859 +-- n is the value in 1/100 second units
1860 +-- b is the value in 1/256 second units
1861 +--
1862 +-- Note: it is important that the arithmetic operations are
1863 +-- done in the order specified (i.e., multiply first, divide
1864 +-- second).
1865 +
1866 + dot1dBridge OBJECT IDENTIFIER ::= { mib-2 17 }
1867 +
1868 +-- groups in the Bridge MIB
1869 +
1870 +dot1dBase OBJECT IDENTIFIER ::= { dot1dBridge 1 }
1871 +
1872 +dot1dStp OBJECT IDENTIFIER ::= { dot1dBridge 2 }
1873 +
1874 +dot1dSr OBJECT IDENTIFIER ::= { dot1dBridge 3 }
1875 +-- separately documented
1876 +
1877 +dot1dTp OBJECT IDENTIFIER ::= { dot1dBridge 4 }
1878 +
1879 +dot1dStatic OBJECT IDENTIFIER ::= { dot1dBridge 5 }
1880 +
1881 +-- the dot1dBase group
1882 +
1883 +-- Implementation of the dot1dBase group is mandatory for all
1884 +-- bridges.
1885 +
1886 +dot1dBaseBridgeAddress OBJECT-TYPE
1887 + SYNTAX MacAddress
1888 + ACCESS read-only
1889 + STATUS mandatory
1890 + DESCRIPTION
1891 + "The MAC address used by this bridge when it must
1892 + be referred to in a unique fashion. It is
1893 + recommended that this be the numerically smallest
1894 + MAC address of all ports that belong to this
1895 + bridge. However it is only required to be unique.
1896 + When concatenated with dot1dStpPriority a unique
1897 + BridgeIdentifier is formed which is used in the
1898 + Spanning Tree Protocol."
1899 + REFERENCE
1900 + "IEEE 802.1D-1990: Sections 6.4.1.1.3 and 3.12.5"
1901 + ::= { dot1dBase 1 }
1902 +
1903 +dot1dBaseNumPorts OBJECT-TYPE
1904 + SYNTAX INTEGER
1905 + ACCESS read-only
1906 + STATUS mandatory
1907 + DESCRIPTION
1908 + "The number of ports controlled by this bridging
1909 + entity."
1910 + REFERENCE
1911 + "IEEE 802.1D-1990: Section 6.4.1.1.3"
1912 + ::= { dot1dBase 2 }
1913 +
1914 +dot1dBaseType OBJECT-TYPE
1915 + SYNTAX INTEGER {
1916 + unknown(1),
1917 + transparent-only(2),
1918 + sourceroute-only(3),
1919 + srt(4)
1920 + }
1921 + ACCESS read-only
1922 + STATUS mandatory
1923 + DESCRIPTION
1924 + "Indicates what type of bridging this bridge can
1925 + perform. If a bridge is actually performing a
1926 + certain type of bridging this will be indicated by
1927 + entries in the port table for the given type."
1928 + ::= { dot1dBase 3 }
1929 +
1930 +-- The Generic Bridge Port Table
1931 +
1932 +dot1dBasePortTable OBJECT-TYPE
1933 + SYNTAX SEQUENCE OF Dot1dBasePortEntry
1934 + ACCESS not-accessible
1935 + STATUS mandatory
1936 + DESCRIPTION
1937 + "A table that contains generic information about
1938 + every port that is associated with this bridge.
1939 + Transparent, source-route, and srt ports are
1940 + included."
1941 + ::= { dot1dBase 4 }
1942 +
1943 +dot1dBasePortEntry OBJECT-TYPE
1944 + SYNTAX Dot1dBasePortEntry
1945 + ACCESS not-accessible
1946 + STATUS mandatory
1947 + DESCRIPTION
1948 + "A list of information for each port of the
1949 + bridge."
1950 + REFERENCE
1951 + "IEEE 802.1D-1990: Section 6.4.2, 6.6.1"
1952 + INDEX { dot1dBasePort }
1953 + ::= { dot1dBasePortTable 1 }
1954 +
1955 +Dot1dBasePortEntry ::=
1956 + SEQUENCE {
1957 + dot1dBasePort
1958 + INTEGER,
1959 + dot1dBasePortIfIndex
1960 + INTEGER,
1961 + dot1dBasePortCircuit
1962 +
1963 + OBJECT IDENTIFIER,
1964 + dot1dBasePortDelayExceededDiscards
1965 + Counter,
1966 + dot1dBasePortMtuExceededDiscards
1967 + Counter
1968 + }
1969 +
1970 +dot1dBasePort OBJECT-TYPE
1971 + SYNTAX INTEGER (1..65535)
1972 + ACCESS read-only
1973 + STATUS mandatory
1974 + DESCRIPTION
1975 + "The port number of the port for which this entry
1976 + contains bridge management information."
1977 + ::= { dot1dBasePortEntry 1 }
1978 +
1979 +dot1dBasePortIfIndex OBJECT-TYPE
1980 + SYNTAX INTEGER
1981 + ACCESS read-only
1982 + STATUS mandatory
1983 + DESCRIPTION
1984 + "The value of the instance of the ifIndex object,
1985 + defined in MIB-II, for the interface corresponding
1986 + to this port."
1987 + ::= { dot1dBasePortEntry 2 }
1988 +
1989 +dot1dBasePortCircuit OBJECT-TYPE
1990 + SYNTAX OBJECT IDENTIFIER
1991 + ACCESS read-only
1992 + STATUS mandatory
1993 + DESCRIPTION
1994 + "For a port which (potentially) has the same value
1995 + of dot1dBasePortIfIndex as another port on the
1996 + same bridge, this object contains the name of an
1997 + object instance unique to this port. For example,
1998 + in the case where multiple ports correspond one-
1999 + to-one with multiple X.25 virtual circuits, this
2000 + value might identify an (e.g., the first) object
2001 + instance associated with the X.25 virtual circuit
2002 + corresponding to this port.
2003 +
2004 + For a port which has a unique value of
2005 + dot1dBasePortIfIndex, this object can have the
2006 + value { 0 0 }."
2007 + ::= { dot1dBasePortEntry 3 }
2008 +
2009 +dot1dBasePortDelayExceededDiscards OBJECT-TYPE
2010 + SYNTAX Counter
2011 +
2012 + ACCESS read-only
2013 + STATUS mandatory
2014 + DESCRIPTION
2015 + "The number of frames discarded by this port due
2016 + to excessive transit delay through the bridge. It
2017 + is incremented by both transparent and source
2018 + route bridges."
2019 + REFERENCE
2020 + "IEEE 802.1D-1990: Section 6.6.1.1.3"
2021 + ::= { dot1dBasePortEntry 4 }
2022 +
2023 +dot1dBasePortMtuExceededDiscards OBJECT-TYPE
2024 + SYNTAX Counter
2025 + ACCESS read-only
2026 + STATUS mandatory
2027 + DESCRIPTION
2028 + "The number of frames discarded by this port due
2029 + to an excessive size. It is incremented by both
2030 + transparent and source route bridges."
2031 + REFERENCE
2032 + "IEEE 802.1D-1990: Section 6.6.1.1.3"
2033 + ::= { dot1dBasePortEntry 5 }
2034 +
2035 +-- the dot1dStp group
2036 +
2037 +-- Implementation of the dot1dStp group is optional. It is
2038 +-- implemented by those bridges that support the Spanning Tree
2039 +-- Protocol.
2040 +
2041 +dot1dStpProtocolSpecification OBJECT-TYPE
2042 + SYNTAX INTEGER {
2043 + unknown(1),
2044 + decLb100(2),
2045 + ieee8021d(3)
2046 + }
2047 + ACCESS read-only
2048 + STATUS mandatory
2049 + DESCRIPTION
2050 + "An indication of what version of the Spanning
2051 + Tree Protocol is being run. The value
2052 + 'decLb100(2)' indicates the DEC LANbridge 100
2053 + Spanning Tree protocol. IEEE 802.1d
2054 + implementations will return 'ieee8021d(3)'. If
2055 + future versions of the IEEE Spanning Tree Protocol
2056 + are released that are incompatible with the
2057 + current version a new value will be defined."
2058 +
2059 + ::= { dot1dStp 1 }
2060 +
2061 +dot1dStpPriority OBJECT-TYPE
2062 + SYNTAX INTEGER (0..65535)
2063 + ACCESS read-write
2064 + STATUS mandatory
2065 + DESCRIPTION
2066 + "The value of the write-able portion of the Bridge
2067 + ID, i.e., the first two octets of the (8 octet
2068 + long) Bridge ID. The other (last) 6 octets of the
2069 + Bridge ID are given by the value of
2070 + dot1dBaseBridgeAddress."
2071 + REFERENCE
2072 + "IEEE 802.1D-1990: Section 4.5.3.7"
2073 + ::= { dot1dStp 2 }
2074 +
2075 +dot1dStpTimeSinceTopologyChange OBJECT-TYPE
2076 + SYNTAX TimeTicks
2077 + ACCESS read-only
2078 + STATUS mandatory
2079 + DESCRIPTION
2080 + "The time (in hundredths of a second) since the
2081 + last time a topology change was detected by the
2082 + bridge entity."
2083 + REFERENCE
2084 + "IEEE 802.1D-1990: Section 6.8.1.1.3"
2085 + ::= { dot1dStp 3 }
2086 +
2087 +dot1dStpTopChanges OBJECT-TYPE
2088 + SYNTAX Counter
2089 + ACCESS read-only
2090 + STATUS mandatory
2091 + DESCRIPTION
2092 + "The total number of topology changes detected by
2093 + this bridge since the management entity was last
2094 + reset or initialized."
2095 + REFERENCE
2096 + "IEEE 802.1D-1990: Section 6.8.1.1.3"
2097 + ::= { dot1dStp 4 }
2098 +
2099 +dot1dStpDesignatedRoot OBJECT-TYPE
2100 + SYNTAX BridgeId
2101 + ACCESS read-only
2102 + STATUS mandatory
2103 + DESCRIPTION
2104 + "The bridge identifier of the root of the spanning
2105 + tree as determined by the Spanning Tree Protocol
2106 + as executed by this node. This value is used as
2107 +
2108 + the Root Identifier parameter in all Configuration
2109 + Bridge PDUs originated by this node."
2110 + REFERENCE
2111 + "IEEE 802.1D-1990: Section 4.5.3.1"
2112 + ::= { dot1dStp 5 }
2113 +
2114 +dot1dStpRootCost OBJECT-TYPE
2115 + SYNTAX INTEGER
2116 + ACCESS read-only
2117 + STATUS mandatory
2118 + DESCRIPTION
2119 + "The cost of the path to the root as seen from
2120 + this bridge."
2121 + REFERENCE
2122 + "IEEE 802.1D-1990: Section 4.5.3.2"
2123 + ::= { dot1dStp 6 }
2124 +
2125 +dot1dStpRootPort OBJECT-TYPE
2126 + SYNTAX INTEGER
2127 + ACCESS read-only
2128 + STATUS mandatory
2129 + DESCRIPTION
2130 + "The port number of the port which offers the
2131 + lowest cost path from this bridge to the root
2132 + bridge."
2133 + REFERENCE
2134 + "IEEE 802.1D-1990: Section 4.5.3.3"
2135 + ::= { dot1dStp 7 }
2136 +
2137 +dot1dStpMaxAge OBJECT-TYPE
2138 + SYNTAX Timeout
2139 + ACCESS read-only
2140 + STATUS mandatory
2141 + DESCRIPTION
2142 + "The maximum age of Spanning Tree Protocol
2143 + information learned from the network on any port
2144 + before it is discarded, in units of hundredths of
2145 + a second. This is the actual value that this
2146 + bridge is currently using."
2147 + REFERENCE
2148 + "IEEE 802.1D-1990: Section 4.5.3.4"
2149 + ::= { dot1dStp 8 }
2150 +
2151 +dot1dStpHelloTime OBJECT-TYPE
2152 + SYNTAX Timeout
2153 + ACCESS read-only
2154 + STATUS mandatory
2155 + DESCRIPTION
2156 +
2157 + "The amount of time between the transmission of
2158 + Configuration bridge PDUs by this node on any port
2159 + when it is the root of the spanning tree or trying
2160 + to become so, in units of hundredths of a second.
2161 + This is the actual value that this bridge is
2162 + currently using."
2163 + REFERENCE
2164 + "IEEE 802.1D-1990: Section 4.5.3.5"
2165 + ::= { dot1dStp 9 }
2166 +
2167 +dot1dStpHoldTime OBJECT-TYPE
2168 + SYNTAX INTEGER
2169 + ACCESS read-only
2170 + STATUS mandatory
2171 + DESCRIPTION
2172 + "This time value determines the interval length
2173 + during which no more than two Configuration bridge
2174 + PDUs shall be transmitted by this node, in units
2175 + of hundredths of a second."
2176 + REFERENCE
2177 + "IEEE 802.1D-1990: Section 4.5.3.14"
2178 + ::= { dot1dStp 10 }
2179 +
2180 +dot1dStpForwardDelay OBJECT-TYPE
2181 + SYNTAX Timeout
2182 + ACCESS read-only
2183 + STATUS mandatory
2184 + DESCRIPTION
2185 + "This time value, measured in units of hundredths
2186 + of a second, controls how fast a port changes its
2187 + spanning state when moving towards the Forwarding
2188 + state. The value determines how long the port
2189 + stays in each of the Listening and Learning
2190 + states, which precede the Forwarding state. This
2191 + value is also used, when a topology change has
2192 + been detected and is underway, to age all dynamic
2193 + entries in the Forwarding Database. [Note that
2194 + this value is the one that this bridge is
2195 + currently using, in contrast to
2196 + dot1dStpBridgeForwardDelay which is the value that
2197 + this bridge and all others would start using
2198 + if/when this bridge were to become the root.]"
2199 + REFERENCE
2200 + "IEEE 802.1D-1990: Section 4.5.3.6"
2201 + ::= { dot1dStp 11 }
2202 +
2203 +dot1dStpBridgeMaxAge OBJECT-TYPE
2204 + SYNTAX Timeout (600..4000)
2205 +
2206 + ACCESS read-write
2207 + STATUS mandatory
2208 + DESCRIPTION
2209 + "The value that all bridges use for MaxAge when
2210 + this bridge is acting as the root. Note that
2211 + 802.1D-1990 specifies that the range for this
2212 + parameter is related to the value of
2213 + dot1dStpBridgeHelloTime. The granularity of this
2214 + timer is specified by 802.1D-1990 to be 1 second.
2215 + An agent may return a badValue error if a set is
2216 + attempted to a value which is not a whole number
2217 + of seconds."
2218 + REFERENCE
2219 + "IEEE 802.1D-1990: Section 4.5.3.8"
2220 + ::= { dot1dStp 12 }
2221 +
2222 +dot1dStpBridgeHelloTime OBJECT-TYPE
2223 + SYNTAX Timeout (100..1000)
2224 + ACCESS read-write
2225 + STATUS mandatory
2226 + DESCRIPTION
2227 + "The value that all bridges use for HelloTime when
2228 + this bridge is acting as the root. The
2229 + granularity of this timer is specified by 802.1D-
2230 + 1990 to be 1 second. An agent may return a
2231 + badValue error if a set is attempted to a value
2232 + which is not a whole number of seconds."
2233 + REFERENCE
2234 + "IEEE 802.1D-1990: Section 4.5.3.9"
2235 + ::= { dot1dStp 13 }
2236 +
2237 +dot1dStpBridgeForwardDelay OBJECT-TYPE
2238 + SYNTAX Timeout (400..3000)
2239 + ACCESS read-write
2240 + STATUS mandatory
2241 + DESCRIPTION
2242 + "The value that all bridges use for ForwardDelay
2243 + when this bridge is acting as the root. Note that
2244 + 802.1D-1990 specifies that the range for this
2245 + parameter is related to the value of
2246 + dot1dStpBridgeMaxAge. The granularity of this
2247 + timer is specified by 802.1D-1990 to be 1 second.
2248 + An agent may return a badValue error if a set is
2249 + attempted to a value which is not a whole number
2250 + of seconds."
2251 + REFERENCE
2252 + "IEEE 802.1D-1990: Section 4.5.3.10"
2253 + ::= { dot1dStp 14 }
2254 +
2255 +-- The Spanning Tree Port Table
2256 +
2257 +dot1dStpPortTable OBJECT-TYPE
2258 + SYNTAX SEQUENCE OF Dot1dStpPortEntry
2259 + ACCESS not-accessible
2260 + STATUS mandatory
2261 + DESCRIPTION
2262 + "A table that contains port-specific information
2263 + for the Spanning Tree Protocol."
2264 + ::= { dot1dStp 15 }
2265 +
2266 +dot1dStpPortEntry OBJECT-TYPE
2267 + SYNTAX Dot1dStpPortEntry
2268 + ACCESS not-accessible
2269 + STATUS mandatory
2270 + DESCRIPTION
2271 + "A list of information maintained by every port
2272 + about the Spanning Tree Protocol state for that
2273 + port."
2274 + INDEX { dot1dStpPort }
2275 + ::= { dot1dStpPortTable 1 }
2276 +
2277 +Dot1dStpPortEntry ::=
2278 + SEQUENCE {
2279 + dot1dStpPort
2280 + INTEGER,
2281 + dot1dStpPortPriority
2282 + INTEGER,
2283 + dot1dStpPortState
2284 + INTEGER,
2285 + dot1dStpPortEnable
2286 + INTEGER,
2287 + dot1dStpPortPathCost
2288 + INTEGER,
2289 + dot1dStpPortDesignatedRoot
2290 + BridgeId,
2291 + dot1dStpPortDesignatedCost
2292 + INTEGER,
2293 + dot1dStpPortDesignatedBridge
2294 + BridgeId,
2295 + dot1dStpPortDesignatedPort
2296 + OCTET STRING,
2297 + dot1dStpPortForwardTransitions
2298 + Counter
2299 + }
2300 +
2301 +dot1dStpPort OBJECT-TYPE
2302 + SYNTAX INTEGER (1..65535)
2303 +
2304 + ACCESS read-only
2305 + STATUS mandatory
2306 + DESCRIPTION
2307 + "The port number of the port for which this entry
2308 + contains Spanning Tree Protocol management
2309 + information."
2310 + REFERENCE
2311 + "IEEE 802.1D-1990: Section 6.8.2.1.2"
2312 + ::= { dot1dStpPortEntry 1 }
2313 +
2314 +dot1dStpPortPriority OBJECT-TYPE
2315 + SYNTAX INTEGER (0..255)
2316 + ACCESS read-write
2317 + STATUS mandatory
2318 + DESCRIPTION
2319 + "The value of the priority field which is
2320 + contained in the first (in network byte order)
2321 + octet of the (2 octet long) Port ID. The other
2322 + octet of the Port ID is given by the value of
2323 + dot1dStpPort."
2324 + REFERENCE
2325 + "IEEE 802.1D-1990: Section 4.5.5.1"
2326 + ::= { dot1dStpPortEntry 2 }
2327 +
2328 +dot1dStpPortState OBJECT-TYPE
2329 + SYNTAX INTEGER {
2330 + disabled(1),
2331 + blocking(2),
2332 + listening(3),
2333 + learning(4),
2334 + forwarding(5),
2335 + broken(6)
2336 + }
2337 + ACCESS read-only
2338 + STATUS mandatory
2339 + DESCRIPTION
2340 + "The port's current state as defined by
2341 + application of the Spanning Tree Protocol. This
2342 + state controls what action a port takes on
2343 + reception of a frame. If the bridge has detected
2344 + a port that is malfunctioning it will place that
2345 + port into the broken(6) state. For ports which
2346 + are disabled (see dot1dStpPortEnable), this object
2347 + will have a value of disabled(1)."
2348 + REFERENCE
2349 + "IEEE 802.1D-1990: Section 4.5.5.2"
2350 + ::= { dot1dStpPortEntry 3 }
2351 +
2352 +dot1dStpPortEnable OBJECT-TYPE
2353 + SYNTAX INTEGER {
2354 + enabled(1),
2355 + disabled(2)
2356 + }
2357 + ACCESS read-write
2358 + STATUS mandatory
2359 + DESCRIPTION
2360 + "The enabled/disabled status of the port."
2361 + REFERENCE
2362 + "IEEE 802.1D-1990: Section 4.5.5.2"
2363 + ::= { dot1dStpPortEntry 4 }
2364 +
2365 +dot1dStpPortPathCost OBJECT-TYPE
2366 + SYNTAX INTEGER (1..65535)
2367 + ACCESS read-write
2368 + STATUS mandatory
2369 + DESCRIPTION
2370 + "The contribution of this port to the path cost of
2371 + paths towards the spanning tree root which include
2372 + this port. 802.1D-1990 recommends that the
2373 + default value of this parameter be in inverse
2374 + proportion to the speed of the attached LAN."
2375 + REFERENCE
2376 + "IEEE 802.1D-1990: Section 4.5.5.3"
2377 + ::= { dot1dStpPortEntry 5 }
2378 +
2379 +dot1dStpPortDesignatedRoot OBJECT-TYPE
2380 + SYNTAX BridgeId
2381 + ACCESS read-only
2382 + STATUS mandatory
2383 + DESCRIPTION
2384 + "The unique Bridge Identifier of the Bridge
2385 + recorded as the Root in the Configuration BPDUs
2386 + transmitted by the Designated Bridge for the
2387 + segment to which the port is attached."
2388 + REFERENCE
2389 + "IEEE 802.1D-1990: Section 4.5.5.4"
2390 + ::= { dot1dStpPortEntry 6 }
2391 +
2392 +dot1dStpPortDesignatedCost OBJECT-TYPE
2393 + SYNTAX INTEGER
2394 + ACCESS read-only
2395 + STATUS mandatory
2396 + DESCRIPTION
2397 + "The path cost of the Designated Port of the
2398 + segment connected to this port. This value is
2399 + compared to the Root Path Cost field in received
2400 +
2401 + bridge PDUs."
2402 + REFERENCE
2403 + "IEEE 802.1D-1990: Section 4.5.5.5"
2404 + ::= { dot1dStpPortEntry 7 }
2405 +
2406 +dot1dStpPortDesignatedBridge OBJECT-TYPE
2407 + SYNTAX BridgeId
2408 + ACCESS read-only
2409 + STATUS mandatory
2410 + DESCRIPTION
2411 + "The Bridge Identifier of the bridge which this
2412 + port considers to be the Designated Bridge for
2413 + this port's segment."
2414 + REFERENCE
2415 + "IEEE 802.1D-1990: Section 4.5.5.6"
2416 + ::= { dot1dStpPortEntry 8 }
2417 +
2418 +dot1dStpPortDesignatedPort OBJECT-TYPE
2419 + SYNTAX OCTET STRING (SIZE (2))
2420 + ACCESS read-only
2421 + STATUS mandatory
2422 + DESCRIPTION
2423 + "The Port Identifier of the port on the Designated
2424 + Bridge for this port's segment."
2425 + REFERENCE
2426 + "IEEE 802.1D-1990: Section 4.5.5.7"
2427 + ::= { dot1dStpPortEntry 9 }
2428 +
2429 +dot1dStpPortForwardTransitions OBJECT-TYPE
2430 + SYNTAX Counter
2431 + ACCESS read-only
2432 + STATUS mandatory
2433 + DESCRIPTION
2434 + "The number of times this port has transitioned
2435 + from the Learning state to the Forwarding state."
2436 + ::= { dot1dStpPortEntry 10 }
2437 +
2438 +-- the dot1dTp group
2439 +
2440 +-- Implementation of the dot1dTp group is optional. It is
2441 +-- implemented by those bridges that support the transparent
2442 +-- bridging mode. A transparent or SRT bridge will implement
2443 +-- this group.
2444 +
2445 +dot1dTpLearnedEntryDiscards OBJECT-TYPE
2446 + SYNTAX Counter
2447 +
2448 + ACCESS read-only
2449 + STATUS mandatory
2450 + DESCRIPTION
2451 + "The total number of Forwarding Database entries,
2452 + which have been or would have been learnt, but
2453 + have been discarded due to a lack of space to
2454 + store them in the Forwarding Database. If this
2455 + counter is increasing, it indicates that the
2456 + Forwarding Database is regularly becoming full (a
2457 + condition which has unpleasant performance effects
2458 + on the subnetwork). If this counter has a
2459 + significant value but is not presently increasing,
2460 + it indicates that the problem has been occurring
2461 + but is not persistent."
2462 + REFERENCE
2463 + "IEEE 802.1D-1990: Section 6.7.1.1.3"
2464 + ::= { dot1dTp 1 }
2465 +
2466 +dot1dTpAgingTime OBJECT-TYPE
2467 + SYNTAX INTEGER (10..1000000)
2468 + ACCESS read-write
2469 + STATUS mandatory
2470 + DESCRIPTION
2471 + "The timeout period in seconds for aging out
2472 + dynamically learned forwarding information.
2473 + 802.1D-1990 recommends a default of 300 seconds."
2474 + REFERENCE
2475 + "IEEE 802.1D-1990: Section 6.7.1.1.3"
2476 + ::= { dot1dTp 2 }
2477 +
2478 +-- The Forwarding Database for Transparent Bridges
2479 +
2480 +dot1dTpFdbTable OBJECT-TYPE
2481 + SYNTAX SEQUENCE OF Dot1dTpFdbEntry
2482 + ACCESS not-accessible
2483 + STATUS mandatory
2484 + DESCRIPTION
2485 + "A table that contains information about unicast
2486 + entries for which the bridge has forwarding and/or
2487 + filtering information. This information is used
2488 + by the transparent bridging function in
2489 + determining how to propagate a received frame."
2490 + ::= { dot1dTp 3 }
2491 +
2492 +dot1dTpFdbEntry OBJECT-TYPE
2493 + SYNTAX Dot1dTpFdbEntry
2494 + ACCESS not-accessible
2495 + STATUS mandatory
2496 + DESCRIPTION
2497 + "Information about a specific unicast MAC address
2498 + for which the bridge has some forwarding and/or
2499 + filtering information."
2500 + INDEX { dot1dTpFdbAddress }
2501 + ::= { dot1dTpFdbTable 1 }
2502 +
2503 +Dot1dTpFdbEntry ::=
2504 + SEQUENCE {
2505 + dot1dTpFdbAddress
2506 + MacAddress,
2507 + dot1dTpFdbPort
2508 + INTEGER,
2509 + dot1dTpFdbStatus
2510 + INTEGER
2511 + }
2512 +
2513 +dot1dTpFdbAddress OBJECT-TYPE
2514 + SYNTAX MacAddress
2515 + ACCESS read-only
2516 + STATUS mandatory
2517 + DESCRIPTION
2518 + "A unicast MAC address for which the bridge has
2519 + forwarding and/or filtering information."
2520 + REFERENCE
2521 + "IEEE 802.1D-1990: Section 3.9.1, 3.9.2"
2522 + ::= { dot1dTpFdbEntry 1 }
2523 +
2524 +dot1dTpFdbPort OBJECT-TYPE
2525 + SYNTAX INTEGER
2526 + ACCESS read-only
2527 + STATUS mandatory
2528 + DESCRIPTION
2529 + "Either the value '0', or the port number of the
2530 + port on which a frame having a source address
2531 + equal to the value of the corresponding instance
2532 + of dot1dTpFdbAddress has been seen. A value of
2533 + '0' indicates that the port number has not been
2534 + learned but that the bridge does have some
2535 + forwarding/filtering information about this
2536 + address (e.g. in the dot1dStaticTable).
2537 + Implementors are encouraged to assign the port
2538 + value to this object whenever it is learned even
2539 + for addresses for which the corresponding value of
2540 + dot1dTpFdbStatus is not learned(3)."
2541 + ::= { dot1dTpFdbEntry 2 }
2542 +
2543 +dot1dTpFdbStatus OBJECT-TYPE
2544 + SYNTAX INTEGER {
2545 + other(1),
2546 + invalid(2),
2547 + learned(3),
2548 + self(4),
2549 + mgmt(5)
2550 + }
2551 + ACCESS read-only
2552 + STATUS mandatory
2553 + DESCRIPTION
2554 + "The status of this entry. The meanings of the
2555 + values are:
2556 + other(1) : none of the following. This would
2557 + include the case where some other
2558 + MIB object (not the corresponding
2559 + instance of dot1dTpFdbPort, nor an
2560 + entry in the dot1dStaticTable) is
2561 + being used to determine if and how
2562 + frames addressed to the value of
2563 + the corresponding instance of
2564 + dot1dTpFdbAddress are being
2565 + forwarded.
2566 + invalid(2) : this entry is not longer valid
2567 + (e.g., it was learned but has since
2568 + aged-out), but has not yet been
2569 + flushed from the table.
2570 + learned(3) : the value of the corresponding
2571 + instance of dot1dTpFdbPort was
2572 + learned, and is being used.
2573 + self(4) : the value of the corresponding
2574 + instance of dot1dTpFdbAddress
2575 + represents one of the bridge's
2576 + addresses. The corresponding
2577 + instance of dot1dTpFdbPort
2578 + indicates which of the bridge's
2579 + ports has this address.
2580 + mgmt(5) : the value of the corresponding
2581 + instance of dot1dTpFdbAddress is
2582 + also the value of an existing
2583 + instance of dot1dStaticAddress."
2584 + ::= { dot1dTpFdbEntry 3 }
2585 +
2586 +-- Port Table for Transparent Bridges
2587 +
2588 +dot1dTpPortTable OBJECT-TYPE
2589 + SYNTAX SEQUENCE OF Dot1dTpPortEntry
2590 + ACCESS not-accessible
2591 + STATUS mandatory
2592 + DESCRIPTION
2593 + "A table that contains information about every
2594 + port that is associated with this transparent
2595 + bridge."
2596 + ::= { dot1dTp 4 }
2597 +
2598 +dot1dTpPortEntry OBJECT-TYPE
2599 + SYNTAX Dot1dTpPortEntry
2600 + ACCESS not-accessible
2601 + STATUS mandatory
2602 + DESCRIPTION
2603 + "A list of information for each port of a
2604 + transparent bridge."
2605 + INDEX { dot1dTpPort }
2606 + ::= { dot1dTpPortTable 1 }
2607 +
2608 +Dot1dTpPortEntry ::=
2609 + SEQUENCE {
2610 + dot1dTpPort
2611 + INTEGER,
2612 + dot1dTpPortMaxInfo
2613 + INTEGER,
2614 + dot1dTpPortInFrames
2615 + Counter,
2616 + dot1dTpPortOutFrames
2617 + Counter,
2618 + dot1dTpPortInDiscards
2619 + Counter
2620 + }
2621 +
2622 +dot1dTpPort OBJECT-TYPE
2623 + SYNTAX INTEGER (1..65535)
2624 + ACCESS read-only
2625 + STATUS mandatory
2626 + DESCRIPTION
2627 + "The port number of the port for which this entry
2628 + contains Transparent bridging management
2629 + information."
2630 + ::= { dot1dTpPortEntry 1 }
2631 +
2632 +-- It would be nice if we could use ifMtu as the size of the
2633 +-- largest INFO field, but we can't because ifMtu is defined
2634 +-- to be the size that the (inter-)network layer can use which
2635 +-- can differ from the MAC layer (especially if several layers
2636 +-- of encapsulation are used).
2637 +
2638 +dot1dTpPortMaxInfo OBJECT-TYPE
2639 + SYNTAX INTEGER
2640 + ACCESS read-only
2641 + STATUS mandatory
2642 + DESCRIPTION
2643 + "The maximum size of the INFO (non-MAC) field that
2644 + this port will receive or transmit."
2645 + ::= { dot1dTpPortEntry 2 }
2646 +
2647 +dot1dTpPortInFrames OBJECT-TYPE
2648 + SYNTAX Counter
2649 + ACCESS read-only
2650 + STATUS mandatory
2651 + DESCRIPTION
2652 + "The number of frames that have been received by
2653 + this port from its segment. Note that a frame
2654 + received on the interface corresponding to this
2655 + port is only counted by this object if and only if
2656 + it is for a protocol being processed by the local
2657 + bridging function, including bridge management
2658 + frames."
2659 + REFERENCE
2660 + "IEEE 802.1D-1990: Section 6.6.1.1.3"
2661 + ::= { dot1dTpPortEntry 3 }
2662 +
2663 +dot1dTpPortOutFrames OBJECT-TYPE
2664 + SYNTAX Counter
2665 + ACCESS read-only
2666 + STATUS mandatory
2667 + DESCRIPTION
2668 + "The number of frames that have been transmitted
2669 + by this port to its segment. Note that a frame
2670 + transmitted on the interface corresponding to this
2671 + port is only counted by this object if and only if
2672 + it is for a protocol being processed by the local
2673 + bridging function, including bridge management
2674 + frames."
2675 + REFERENCE
2676 + "IEEE 802.1D-1990: Section 6.6.1.1.3"
2677 + ::= { dot1dTpPortEntry 4 }
2678 +
2679 +dot1dTpPortInDiscards OBJECT-TYPE
2680 + SYNTAX Counter
2681 + ACCESS read-only
2682 + STATUS mandatory
2683 + DESCRIPTION
2684 + "Count of valid frames received which were
2685 + discarded (i.e., filtered) by the Forwarding
2686 + Process."
2687 + REFERENCE
2688 + "IEEE 802.1D-1990: Section 6.6.1.1.3"
2689 + ::= { dot1dTpPortEntry 5 }
2690 +-- The Static (Destination-Address Filtering) Database
2691 +
2692 +-- Implementation of this group is optional.
2693 +
2694 +dot1dStaticTable OBJECT-TYPE
2695 + SYNTAX SEQUENCE OF Dot1dStaticEntry
2696 + ACCESS not-accessible
2697 + STATUS mandatory
2698 + DESCRIPTION
2699 + "A table containing filtering information
2700 + configured into the bridge by (local or network)
2701 + management specifying the set of ports to which
2702 + frames received from specific ports and containing
2703 + specific destination addresses are allowed to be
2704 + forwarded. The value of zero in this table as the
2705 + port number from which frames with a specific
2706 + destination address are received, is used to
2707 + specify all ports for which there is no specific
2708 + entry in this table for that particular
2709 + destination address. Entries are valid for
2710 + unicast and for group/broadcast addresses."
2711 + REFERENCE
2712 + "IEEE 802.1D-1990: Section 6.7.2"
2713 + ::= { dot1dStatic 1 }
2714 +
2715 +dot1dStaticEntry OBJECT-TYPE
2716 + SYNTAX Dot1dStaticEntry
2717 + ACCESS not-accessible
2718 + STATUS mandatory
2719 + DESCRIPTION
2720 + "Filtering information configured into the bridge
2721 + by (local or network) management specifying the
2722 + set of ports to which frames received from a
2723 + specific port and containing a specific
2724 + destination address are allowed to be forwarded."
2725 + REFERENCE
2726 + "IEEE 802.1D-1990: Section 6.7.2"
2727 + INDEX { dot1dStaticAddress, dot1dStaticReceivePort }
2728 + ::= { dot1dStaticTable 1 }
2729 +
2730 +Dot1dStaticEntry ::=
2731 + SEQUENCE {
2732 + dot1dStaticAddress
2733 + MacAddress,
2734 + dot1dStaticReceivePort
2735 + INTEGER,
2736 + dot1dStaticAllowedToGoTo
2737 + OCTET STRING,
2738 + dot1dStaticStatus
2739 + INTEGER
2740 + }
2741 +
2742 +dot1dStaticAddress OBJECT-TYPE
2743 + SYNTAX MacAddress
2744 + ACCESS read-write
2745 + STATUS mandatory
2746 + DESCRIPTION
2747 + "The destination MAC address in a frame to which
2748 + this entry's filtering information applies. This
2749 + object can take the value of a unicast address, a
2750 + group address or the broadcast address."
2751 + REFERENCE
2752 + "IEEE 802.1D-1990: Section 3.9.1, 3.9.2"
2753 + ::= { dot1dStaticEntry 1 }
2754 +
2755 +dot1dStaticReceivePort OBJECT-TYPE
2756 + SYNTAX INTEGER
2757 + ACCESS read-write
2758 + STATUS mandatory
2759 + DESCRIPTION
2760 + "Either the value '0', or the port number of the
2761 + port from which a frame must be received in order
2762 + for this entry's filtering information to apply.
2763 + A value of zero indicates that this entry applies
2764 + on all ports of the bridge for which there is no
2765 + other applicable entry."
2766 + ::= { dot1dStaticEntry 2 }
2767 +
2768 +dot1dStaticAllowedToGoTo OBJECT-TYPE
2769 + SYNTAX OCTET STRING
2770 + ACCESS read-write
2771 + STATUS mandatory
2772 + DESCRIPTION
2773 + "The set of ports to which frames received from a
2774 + specific port and destined for a specific MAC
2775 +
2776 + address, are allowed to be forwarded. Each octet
2777 + within the value of this object specifies a set of
2778 + eight ports, with the first octet specifying ports
2779 + 1 through 8, the second octet specifying ports 9
2780 + through 16, etc. Within each octet, the most
2781 + significant bit represents the lowest numbered
2782 + port, and the least significant bit represents the
2783 + highest numbered port. Thus, each port of the
2784 + bridge is represented by a single bit within the
2785 + value of this object. If that bit has a value of
2786 + '1' then that port is included in the set of
2787 + ports; the port is not included if its bit has a
2788 + value of '0'. (Note that the setting of the bit
2789 + corresponding to the port from which a frame is
2790 + received is irrelevant.) The default value of
2791 + this object is a string of ones of appropriate
2792 + length."
2793 + ::= { dot1dStaticEntry 3 }
2794 +
2795 +dot1dStaticStatus OBJECT-TYPE
2796 + SYNTAX INTEGER {
2797 + other(1),
2798 + invalid(2),
2799 + permanent(3),
2800 + deleteOnReset(4),
2801 + deleteOnTimeout(5)
2802 + }
2803 + ACCESS read-write
2804 + STATUS mandatory
2805 + DESCRIPTION
2806 + "This object indicates the status of this entry.
2807 + The default value is permanent(3).
2808 + other(1) - this entry is currently in use but
2809 + the conditions under which it will
2810 + remain so are different from each of the
2811 + following values.
2812 + invalid(2) - writing this value to the object
2813 + removes the corresponding entry.
2814 + permanent(3) - this entry is currently in use
2815 + and will remain so after the next reset
2816 + of the bridge.
2817 + deleteOnReset(4) - this entry is currently in
2818 + use and will remain so until the next
2819 + reset of the bridge.
2820 + deleteOnTimeout(5) - this entry is currently
2821 + in use and will remain so until it is
2822 + aged out."
2823 +
2824 + ::= { dot1dStaticEntry 4 }
2825 +
2826 +-- Traps for use by Bridges
2827 +
2828 +-- Traps for the Spanning Tree Protocol
2829 +
2830 +newRoot TRAP-TYPE
2831 + ENTERPRISE dot1dBridge
2832 + DESCRIPTION
2833 + "The newRoot trap indicates that the sending agent
2834 + has become the new root of the Spanning Tree; the
2835 + trap is sent by a bridge soon after its election
2836 + as the new root, e.g., upon expiration of the
2837 + Topology Change Timer immediately subsequent to
2838 + its election. Implementation of this trap is
2839 + optional."
2840 + ::= 1
2841 +
2842 +topologyChange TRAP-TYPE
2843 + ENTERPRISE dot1dBridge
2844 + DESCRIPTION
2845 + "A topologyChange trap is sent by a bridge when
2846 + any of its configured ports transitions from the
2847 + Learning state to the Forwarding state, or from
2848 + the Forwarding state to the Blocking state. The
2849 + trap is not sent if a newRoot trap is sent for the
2850 + same transition. Implementation of this trap is
2851 + optional."
2852 + ::= 2
2853 +
2854 +END
2855 diff -ruN net-snmp-5.1.2-orig/mibs/GNOME-SMI.txt net-snmp-5.1.2-5/mibs/GNOME-SMI.txt
2856 --- net-snmp-5.1.2-orig/mibs/GNOME-SMI.txt 1970-01-01 01:00:00.000000000 +0100
2857 +++ net-snmp-5.1.2-5/mibs/GNOME-SMI.txt 2005-03-13 16:17:21.000000000 +0100
2858 @@ -0,0 +1,72 @@
2859 +GNOME-SMI DEFINITIONS ::= BEGIN
2860 +
2861 +IMPORTS
2862 + MODULE-IDENTITY,
2863 + OBJECT-IDENTITY,
2864 + enterprises
2865 + FROM SNMPv2-SMI;
2866 +
2867 +gnome MODULE-IDENTITY
2868 + LAST-UPDATED "200312070000Z"
2869 + ORGANIZATION "GNOME project"
2870 + CONTACT-INFO
2871 + "GNU Network Object Model Environment project
2872 +
2873 + see http://www.gnome.org for contact persons of a particular
2874 + area or subproject of GNOME.
2875 +
2876 + Administrative contact for MIB module:
2877 +
2878 + Jochen Friedrich
2879 + Buedingerstr. 30b
2880 + 63546 Hammersbach
2881 + Germany
2882 +
2883 + email: jochen@scram.de"
2884 + DESCRIPTION
2885 + "The Structure of GNOME."
2886 +
2887 + -- revision history
2888 +
2889 + REVISION "9809010000Z" -- September 01, 1998
2890 + DESCRIPTION
2891 + "Initial version."
2892 +
2893 + REVISION "200312070000Z" -- December 07, 2003
2894 + DESCRIPTION
2895 + "Added gnomeSysadmin subtree for GNOME project system administration.
2896 + Updated contact info."
2897 +
2898 + ::= { enterprises 3317 } -- assigned by IANA
2899 +
2900 +gnomeProducts OBJECT-IDENTITY
2901 + STATUS current
2902 + DESCRIPTION
2903 + "gnomeProducts is the root OBJECT IDENTIFIER from
2904 + which sysObjectID values are assigned."
2905 + ::= { gnome 1 }
2906 +
2907 +gnomeMgmt OBJECT-IDENTITY
2908 + STATUS current
2909 + DESCRIPTION
2910 + "gnomeMgmt defines the subtree for production GNOME related
2911 + MIB registrations."
2912 + ::= { gnome 2 }
2913 +
2914 +gnomeTest OBJECT-IDENTITY
2915 + STATUS current
2916 + DESCRIPTION
2917 + "gnomeTest defines the subtree for testing GNOME related
2918 + MIB registrations."
2919 + ::= { gnome 3 }
2920 +
2921 +gnomeSysadmin OBJECT-IDENTITY
2922 + STATUS current
2923 + DESCRIPTION
2924 + "gnomeSysadmin defines the subtree for GNOME related Sysadmin
2925 + MIB registrations."
2926 + ::= { gnome 4 }
2927 +
2928 +-- more to come if necessary.
2929 +
2930 +END
2931 diff -ruN net-snmp-5.1.2-orig/mibs/Makefile.in net-snmp-5.1.2-5/mibs/Makefile.in
2932 --- net-snmp-5.1.2-orig/mibs/Makefile.in 2004-06-18 20:11:15.000000000 +0200
2933 +++ net-snmp-5.1.2-5/mibs/Makefile.in 2005-03-13 16:17:21.000000000 +0100
2934 @@ -43,11 +43,15 @@
2935 UCDMIBS = UCD-SNMP-MIB.txt UCD-DEMO-MIB.txt UCD-IPFWACC-MIB.txt \
2936 UCD-DLMOD-MIB.txt UCD-DISKIO-MIB.txt
2937
2938 +EXTRAMIBS = BGP4-MIB.txt BRIDGE-MIB.txt GNOME-SMI.txt OSPF-MIB.txt \
2939 + OSPF-TRAP-MIB.txt RIPv2-MIB.txt SOURCE-ROUTING-MIB.txt \
2940 + LM-SENSORS-MIB.txt
2941 +
2942 DEFAULTMIBS = @default_mibs_install@
2943
2944 MIBS = $(V1MIBS) $(V2MIBS) $(V3MIBS) $(RFCMIBS) \
2945 $(AGENTMIBS) $(IANAMIBS) \
2946 - $(NETSNMPMIBS) $(UCDMIBS) $(DEFAULTMIBS)
2947 + $(NETSNMPMIBS) $(UCDMIBS) $(DEFAULTMIBS) $(EXTRAMIBS)
2948
2949 all: standardall
2950
2951 diff -ruN net-snmp-5.1.2-orig/mibs/OSPF-MIB.txt net-snmp-5.1.2-5/mibs/OSPF-MIB.txt
2952 --- net-snmp-5.1.2-orig/mibs/OSPF-MIB.txt 1970-01-01 01:00:00.000000000 +0100
2953 +++ net-snmp-5.1.2-5/mibs/OSPF-MIB.txt 2005-03-13 16:17:21.000000000 +0100
2954 @@ -0,0 +1,2723 @@
2955 +OSPF-MIB DEFINITIONS ::= BEGIN
2956 +
2957 + IMPORTS
2958 + MODULE-IDENTITY, OBJECT-TYPE, Counter32, Gauge32,
2959 + Integer32, IpAddress
2960 + FROM SNMPv2-SMI
2961 + TEXTUAL-CONVENTION, TruthValue, RowStatus
2962 + FROM SNMPv2-TC
2963 + MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
2964 + mib-2 FROM RFC1213-MIB;
2965 +
2966 +-- This MIB module uses the extended OBJECT-TYPE macro as
2967 +-- defined in [9].
2968 +
2969 +ospf MODULE-IDENTITY
2970 + LAST-UPDATED "9501201225Z" -- Fri Jan 20 12:25:50 PST 1995
2971 + ORGANIZATION "IETF OSPF Working Group"
2972 + CONTACT-INFO
2973 + " Fred Baker
2974 + Postal: Cisco Systems
2975 + 519 Lado Drive
2976 + Santa Barbara, California 93111
2977 + Tel: +1 805 681 0115
2978 + E-Mail: fred@cisco.com
2979 +
2980 + Rob Coltun
2981 + Postal: RainbowBridge Communications
2982 + Tel: (301) 340-9416
2983 + E-Mail: rcoltun@rainbow-bridge.com"
2984 + DESCRIPTION
2985 + "The MIB module to describe the OSPF Version 2
2986 + Protocol"
2987 + ::= { mib-2 14 }
2988 +
2989 +-- The Area ID, in OSPF, has the same format as an IP Address,
2990 +-- but has the function of defining a summarization point for
2991 +-- Link State Advertisements
2992 +
2993 +AreaID ::= TEXTUAL-CONVENTION
2994 + STATUS current
2995 + DESCRIPTION
2996 + "An OSPF Area Identifier."
2997 + SYNTAX IpAddress
2998 +
2999 +
3000 +-- The Router ID, in OSPF, has the same format as an IP Address,
3001 +-- but identifies the router independent of its IP Address.
3002 +
3003 +RouterID ::= TEXTUAL-CONVENTION
3004 + STATUS current
3005 + DESCRIPTION
3006 + "A OSPF Router Identifier."
3007 + SYNTAX IpAddress
3008 +
3009 +
3010 +-- The OSPF Metric is defined as an unsigned value in the range
3011 +
3012 +Metric ::= TEXTUAL-CONVENTION
3013 + STATUS current
3014 + DESCRIPTION
3015 + "The OSPF Internal Metric."
3016 + SYNTAX Integer32 (0..'FFFF'h)
3017 +
3018 +BigMetric ::= TEXTUAL-CONVENTION
3019 + STATUS current
3020 + DESCRIPTION
3021 + "The OSPF External Metric."
3022 + SYNTAX Integer32 (0..'FFFFFF'h)
3023 +
3024 +-- Status Values
3025 +
3026 +Status ::= TEXTUAL-CONVENTION
3027 + STATUS current
3028 + DESCRIPTION
3029 + "The status of an interface: 'enabled' indicates that
3030 + it is willing to communicate with other OSPF Routers,
3031 + while 'disabled' indicates that it is not."
3032 + SYNTAX INTEGER { enabled (1), disabled (2) }
3033 +
3034 +-- Time Durations measured in seconds
3035 +
3036 +PositiveInteger ::= TEXTUAL-CONVENTION
3037 + STATUS current
3038 + DESCRIPTION
3039 + "A positive integer. Values in excess are precluded as
3040 + unnecessary and prone to interoperability issues."
3041 + SYNTAX Integer32 (0..'7FFFFFFF'h)
3042 +
3043 +HelloRange ::= TEXTUAL-CONVENTION
3044 + STATUS current
3045 + DESCRIPTION
3046 + "The range of intervals on which hello messages are
3047 + exchanged."
3048 + SYNTAX Integer32 (1..'FFFF'h)
3049 +
3050 +UpToMaxAge ::= TEXTUAL-CONVENTION
3051 + STATUS current
3052 + DESCRIPTION
3053 + "The values that one might find or configure for
3054 + variables bounded by the maximum age of an LSA."
3055 + SYNTAX Integer32 (0..3600)
3056 +
3057 +
3058 +-- The range of ifIndex
3059 +
3060 +InterfaceIndex ::= TEXTUAL-CONVENTION
3061 + STATUS current
3062 + DESCRIPTION
3063 + "The range of ifIndex."
3064 + SYNTAX Integer32
3065 +
3066 +
3067 +-- Potential Priorities for the Designated Router Election
3068 +
3069 +DesignatedRouterPriority ::= TEXTUAL-CONVENTION
3070 + STATUS current
3071 + DESCRIPTION
3072 + "The values defined for the priority of a system for
3073 + becoming the designated router."
3074 + SYNTAX Integer32 (0..'FF'h)
3075 +
3076 +TOSType ::= TEXTUAL-CONVENTION
3077 + STATUS current
3078 + DESCRIPTION
3079 + "Type of Service is defined as a mapping to the IP Type of
3080 + Service Flags as defined in the IP Forwarding Table MIB
3081 +
3082 + +-----+-----+-----+-----+-----+-----+-----+-----+
3083 + | | | |
3084 + | PRECEDENCE | TYPE OF SERVICE | 0 |
3085 + | | | |
3086 + +-----+-----+-----+-----+-----+-----+-----+-----+
3087 +
3088 + IP TOS IP TOS
3089 + Field Policy Field Policy
3090 +
3091 + Contents Code Contents Code
3092 + 0 0 0 0 ==> 0 0 0 0 1 ==> 2
3093 + 0 0 1 0 ==> 4 0 0 1 1 ==> 6
3094 + 0 1 0 0 ==> 8 0 1 0 1 ==> 10
3095 + 0 1 1 0 ==> 12 0 1 1 1 ==> 14
3096 + 1 0 0 0 ==> 16 1 0 0 1 ==> 18
3097 + 1 0 1 0 ==> 20 1 0 1 1 ==> 22
3098 + 1 1 0 0 ==> 24 1 1 0 1 ==> 26
3099 + 1 1 1 0 ==> 28 1 1 1 1 ==> 30
3100 +
3101 + The remaining values are left for future definition."
3102 + SYNTAX Integer32 (0..30)
3103 +
3104 +
3105 +-- OSPF General Variables
3106 +
3107 +-- These parameters apply globally to the Router's
3108 +-- OSPF Process.
3109 +
3110 +ospfGeneralGroup OBJECT IDENTIFIER ::= { ospf 1 }
3111 +
3112 +
3113 + ospfRouterId OBJECT-TYPE
3114 + SYNTAX RouterID
3115 + MAX-ACCESS read-write
3116 + STATUS current
3117 + DESCRIPTION
3118 + "A 32-bit integer uniquely identifying the
3119 + router in the Autonomous System.
3120 +
3121 + By convention, to ensure uniqueness, this
3122 + should default to the value of one of the
3123 + router's IP interface addresses."
3124 + REFERENCE
3125 + "OSPF Version 2, C.1 Global parameters"
3126 + ::= { ospfGeneralGroup 1 }
3127 +
3128 +
3129 + ospfAdminStat OBJECT-TYPE
3130 + SYNTAX Status
3131 + MAX-ACCESS read-write
3132 + STATUS current
3133 + DESCRIPTION
3134 + "The administrative status of OSPF in the
3135 + router. The value 'enabled' denotes that the
3136 + OSPF Process is active on at least one inter-
3137 + face; 'disabled' disables it on all inter-
3138 + faces."
3139 + ::= { ospfGeneralGroup 2 }
3140 +
3141 + ospfVersionNumber OBJECT-TYPE
3142 + SYNTAX INTEGER { version2 (2) }
3143 + MAX-ACCESS read-only
3144 + STATUS current
3145 + DESCRIPTION
3146 + "The current version number of the OSPF proto-
3147 + col is 2."
3148 + REFERENCE
3149 + "OSPF Version 2, Title"
3150 + ::= { ospfGeneralGroup 3 }
3151 +
3152 +
3153 + ospfAreaBdrRtrStatus OBJECT-TYPE
3154 + SYNTAX TruthValue
3155 + MAX-ACCESS read-only
3156 + STATUS current
3157 + DESCRIPTION
3158 + "A flag to note whether this router is an area
3159 + border router."
3160 + REFERENCE
3161 + "OSPF Version 2, Section 3 Splitting the AS into
3162 + Areas"
3163 + ::= { ospfGeneralGroup 4 }
3164 +
3165 +
3166 + ospfASBdrRtrStatus OBJECT-TYPE
3167 + SYNTAX TruthValue
3168 + MAX-ACCESS read-write
3169 + STATUS current
3170 + DESCRIPTION
3171 + "A flag to note whether this router is config-
3172 + ured as an Autonomous System border router."
3173 + REFERENCE
3174 + "OSPF Version 2, Section 3.3 Classification of
3175 + routers"
3176 + ::= { ospfGeneralGroup 5 }
3177 +
3178 + ospfExternLsaCount OBJECT-TYPE
3179 + SYNTAX Gauge32
3180 + MAX-ACCESS read-only
3181 + STATUS current
3182 + DESCRIPTION
3183 + "The number of external (LS type 5) link-state
3184 + advertisements in the link-state database."
3185 + REFERENCE
3186 + "OSPF Version 2, Appendix A.4.5 AS external link
3187 + advertisements"
3188 + ::= { ospfGeneralGroup 6 }
3189 +
3190 +
3191 + ospfExternLsaCksumSum OBJECT-TYPE
3192 + SYNTAX Integer32
3193 + MAX-ACCESS read-only
3194 + STATUS current
3195 + DESCRIPTION
3196 + "The 32-bit unsigned sum of the LS checksums of
3197 + the external link-state advertisements con-
3198 + tained in the link-state database. This sum
3199 + can be used to determine if there has been a
3200 + change in a router's link state database, and
3201 + to compare the link-state database of two
3202 + routers."
3203 + ::= { ospfGeneralGroup 7 }
3204 +
3205 +
3206 + ospfTOSSupport OBJECT-TYPE
3207 + SYNTAX TruthValue
3208 + MAX-ACCESS read-write
3209 + STATUS current
3210 + DESCRIPTION
3211 + "The router's support for type-of-service rout-
3212 + ing."
3213 + REFERENCE
3214 + "OSPF Version 2, Appendix F.1.2 Optional TOS
3215 + support"
3216 + ::= { ospfGeneralGroup 8 }
3217 +
3218 + ospfOriginateNewLsas OBJECT-TYPE
3219 + SYNTAX Counter32
3220 + MAX-ACCESS read-only
3221 + STATUS current
3222 + DESCRIPTION
3223 + "The number of new link-state advertisements
3224 + that have been originated. This number is in-
3225 + cremented each time the router originates a new
3226 + LSA."
3227 + ::= { ospfGeneralGroup 9 }
3228 +
3229 +
3230 + ospfRxNewLsas OBJECT-TYPE
3231 + SYNTAX Counter32
3232 + MAX-ACCESS read-only
3233 + STATUS current
3234 + DESCRIPTION
3235 + "The number of link-state advertisements re-
3236 + ceived determined to be new instantiations.
3237 + This number does not include newer instantia-
3238 + tions of self-originated link-state advertise-
3239 + ments."
3240 + ::= { ospfGeneralGroup 10 }
3241 +
3242 + ospfExtLsdbLimit OBJECT-TYPE
3243 + SYNTAX Integer32 (-1..'7FFFFFFF'h)
3244 + MAX-ACCESS read-write
3245 + STATUS current
3246 + DESCRIPTION
3247 + "The maximum number of non-default AS-
3248 + external-LSAs entries that can be stored in the
3249 + link-state database. If the value is -1, then
3250 + there is no limit.
3251 +
3252 + When the number of non-default AS-external-LSAs
3253 + in a router's link-state database reaches
3254 + ospfExtLsdbLimit, the router enters Overflow-
3255 + State. The router never holds more than
3256 + ospfExtLsdbLimit non-default AS-external-LSAs
3257 + in its database. OspfExtLsdbLimit MUST be set
3258 + identically in all routers attached to the OSPF
3259 + backbone and/or any regular OSPF area. (i.e.,
3260 + OSPF stub areas and NSSAs are excluded)."
3261 + DEFVAL { -1 }
3262 + ::= { ospfGeneralGroup 11 }
3263 +
3264 + ospfMulticastExtensions OBJECT-TYPE
3265 + SYNTAX Integer32
3266 + MAX-ACCESS read-write
3267 + STATUS current
3268 + DESCRIPTION
3269 + "A Bit Mask indicating whether the router is
3270 + forwarding IP multicast (Class D) datagrams
3271 + based on the algorithms defined in the Multi-
3272 + cast Extensions to OSPF.
3273 +
3274 + Bit 0, if set, indicates that the router can
3275 + forward IP multicast datagrams in the router's
3276 + directly attached areas (called intra-area mul-
3277 + ticast routing).
3278 +
3279 + Bit 1, if set, indicates that the router can
3280 + forward IP multicast datagrams between OSPF
3281 + areas (called inter-area multicast routing).
3282 +
3283 + Bit 2, if set, indicates that the router can
3284 + forward IP multicast datagrams between Auto-
3285 + nomous Systems (called inter-AS multicast rout-
3286 + ing).
3287 +
3288 + Only certain combinations of bit settings are
3289 + allowed, namely: 0 (no multicast forwarding is
3290 + enabled), 1 (intra-area multicasting only), 3
3291 + (intra-area and inter-area multicasting), 5
3292 + (intra-area and inter-AS multicasting) and 7
3293 + (multicasting everywhere). By default, no mul-
3294 + ticast forwarding is enabled."
3295 + DEFVAL { 0 }
3296 + ::= { ospfGeneralGroup 12 }
3297 +
3298 + ospfExitOverflowInterval OBJECT-TYPE
3299 + SYNTAX PositiveInteger
3300 + MAX-ACCESS read-write
3301 + STATUS current
3302 + DESCRIPTION
3303 + "The number of seconds that, after entering
3304 + OverflowState, a router will attempt to leave
3305 + OverflowState. This allows the router to again
3306 + originate non-default AS-external-LSAs. When
3307 + set to 0, the router will not leave Overflow-
3308 + State until restarted."
3309 + DEFVAL { 0 }
3310 + ::= { ospfGeneralGroup 13 }
3311 +
3312 +
3313 + ospfDemandExtensions OBJECT-TYPE
3314 + SYNTAX TruthValue
3315 + MAX-ACCESS read-write
3316 + STATUS current
3317 + DESCRIPTION
3318 + "The router's support for demand routing."
3319 + REFERENCE
3320 + "OSPF Version 2, Appendix on Demand Routing"
3321 + ::= { ospfGeneralGroup 14 }
3322 +
3323 +
3324 +-- The OSPF Area Data Structure contains information
3325 +-- regarding the various areas. The interfaces and
3326 +-- virtual links are configured as part of these areas.
3327 +-- Area 0.0.0.0, by definition, is the Backbone Area
3328 +
3329 +
3330 + ospfAreaTable OBJECT-TYPE
3331 + SYNTAX SEQUENCE OF OspfAreaEntry
3332 + MAX-ACCESS not-accessible
3333 + STATUS current
3334 + DESCRIPTION
3335 + "Information describing the configured parame-
3336 + ters and cumulative statistics of the router's
3337 + attached areas."
3338 + REFERENCE
3339 + "OSPF Version 2, Section 6 The Area Data Struc-
3340 + ture"
3341 + ::= { ospf 2 }
3342 +
3343 +
3344 + ospfAreaEntry OBJECT-TYPE
3345 + SYNTAX OspfAreaEntry
3346 + MAX-ACCESS not-accessible
3347 + STATUS current
3348 + DESCRIPTION
3349 + "Information describing the configured parame-
3350 + ters and cumulative statistics of one of the
3351 + router's attached areas."
3352 + INDEX { ospfAreaId }
3353 + ::= { ospfAreaTable 1 }
3354 +
3355 +OspfAreaEntry ::=
3356 + SEQUENCE {
3357 + ospfAreaId
3358 + AreaID,
3359 + ospfAuthType
3360 + Integer32,
3361 + ospfImportAsExtern
3362 + INTEGER,
3363 + ospfSpfRuns
3364 + Counter32,
3365 + ospfAreaBdrRtrCount
3366 + Gauge32,
3367 + ospfAsBdrRtrCount
3368 + Gauge32,
3369 + ospfAreaLsaCount
3370 + Gauge32,
3371 + ospfAreaLsaCksumSum
3372 + Integer32,
3373 + ospfAreaSummary
3374 + INTEGER,
3375 + ospfAreaStatus
3376 + RowStatus
3377 + }
3378 +
3379 + ospfAreaId OBJECT-TYPE
3380 + SYNTAX AreaID
3381 + MAX-ACCESS read-only
3382 + STATUS current
3383 + DESCRIPTION
3384 + "A 32-bit integer uniquely identifying an area.
3385 + Area ID 0.0.0.0 is used for the OSPF backbone."
3386 + REFERENCE
3387 + "OSPF Version 2, Appendix C.2 Area parameters"
3388 + ::= { ospfAreaEntry 1 }
3389 +
3390 +
3391 + ospfAuthType OBJECT-TYPE
3392 + SYNTAX Integer32
3393 + -- none (0),
3394 + -- simplePassword (1)
3395 + -- md5 (2)
3396 + -- reserved for specification by IANA (> 2)
3397 + MAX-ACCESS read-create
3398 + STATUS obsolete
3399 + DESCRIPTION
3400 + "The authentication type specified for an area.
3401 + Additional authentication types may be assigned
3402 + locally on a per Area basis."
3403 + REFERENCE
3404 + "OSPF Version 2, Appendix E Authentication"
3405 + DEFVAL { 0 } -- no authentication, by default
3406 + ::= { ospfAreaEntry 2 }
3407 +
3408 + ospfImportAsExtern OBJECT-TYPE
3409 + SYNTAX INTEGER {
3410 + importExternal (1),
3411 + importNoExternal (2),
3412 + importNssa (3)
3413 + }
3414 + MAX-ACCESS read-create
3415 + STATUS current
3416 + DESCRIPTION
3417 + "The area's support for importing AS external
3418 + link- state advertisements."
3419 + REFERENCE
3420 + "OSPF Version 2, Appendix C.2 Area parameters"
3421 + DEFVAL { importExternal }
3422 + ::= { ospfAreaEntry 3 }
3423 +
3424 +
3425 + ospfSpfRuns OBJECT-TYPE
3426 + SYNTAX Counter32
3427 + MAX-ACCESS read-only
3428 + STATUS current
3429 + DESCRIPTION
3430 + "The number of times that the intra-area route
3431 + table has been calculated using this area's
3432 + link-state database. This is typically done
3433 + using Dijkstra's algorithm."
3434 + ::= { ospfAreaEntry 4 }
3435 +
3436 +
3437 + ospfAreaBdrRtrCount OBJECT-TYPE
3438 + SYNTAX Gauge32
3439 + MAX-ACCESS read-only
3440 + STATUS current
3441 + DESCRIPTION
3442 + "The total number of area border routers reach-
3443 + able within this area. This is initially zero,
3444 + and is calculated in each SPF Pass."
3445 + ::= { ospfAreaEntry 5 }
3446 +
3447 + ospfAsBdrRtrCount OBJECT-TYPE
3448 + SYNTAX Gauge32
3449 + MAX-ACCESS read-only
3450 + STATUS current
3451 + DESCRIPTION
3452 + "The total number of Autonomous System border
3453 + routers reachable within this area. This is
3454 + initially zero, and is calculated in each SPF
3455 + Pass."
3456 + ::= { ospfAreaEntry 6 }
3457 +
3458 +
3459 + ospfAreaLsaCount OBJECT-TYPE
3460 + SYNTAX Gauge32
3461 + MAX-ACCESS read-only
3462 + STATUS current
3463 + DESCRIPTION
3464 + "The total number of link-state advertisements
3465 + in this area's link-state database, excluding
3466 + AS External LSA's."
3467 + ::= { ospfAreaEntry 7 }
3468 +
3469 +
3470 + ospfAreaLsaCksumSum OBJECT-TYPE
3471 + SYNTAX Integer32
3472 + MAX-ACCESS read-only
3473 + STATUS current
3474 + DESCRIPTION
3475 + "The 32-bit unsigned sum of the link-state ad-
3476 + vertisements' LS checksums contained in this
3477 + area's link-state database. This sum excludes
3478 + external (LS type 5) link-state advertisements.
3479 + The sum can be used to determine if there has
3480 + been a change in a router's link state data-
3481 + base, and to compare the link-state database of
3482 + two routers."
3483 + DEFVAL { 0 }
3484 + ::= { ospfAreaEntry 8 }
3485 +
3486 + ospfAreaSummary OBJECT-TYPE
3487 + SYNTAX INTEGER {
3488 + noAreaSummary (1),
3489 + sendAreaSummary (2)
3490 + }
3491 + MAX-ACCESS read-create
3492 + STATUS current
3493 + DESCRIPTION
3494 + "The variable ospfAreaSummary controls the im-
3495 + port of summary LSAs into stub areas. It has
3496 + no effect on other areas.
3497 +
3498 + If it is noAreaSummary, the router will neither
3499 + originate nor propagate summary LSAs into the
3500 + stub area. It will rely entirely on its de-
3501 + fault route.
3502 +
3503 + If it is sendAreaSummary, the router will both
3504 + summarize and propagate summary LSAs."
3505 + DEFVAL { noAreaSummary }
3506 + ::= { ospfAreaEntry 9 }
3507 +
3508 +
3509 + ospfAreaStatus OBJECT-TYPE
3510 + SYNTAX RowStatus
3511 + MAX-ACCESS read-create
3512 + STATUS current
3513 + DESCRIPTION
3514 + "This variable displays the status of the en-
3515 + try. Setting it to 'invalid' has the effect of
3516 + rendering it inoperative. The internal effect
3517 + (row removal) is implementation dependent."
3518 + ::= { ospfAreaEntry 10 }
3519 +
3520 +
3521 +-- OSPF Area Default Metric Table
3522 +
3523 +-- The OSPF Area Default Metric Table describes the metrics
3524 +-- that a default Area Border Router will advertise into a
3525 +-- Stub area.
3526 +
3527 +
3528 + ospfStubAreaTable OBJECT-TYPE
3529 + SYNTAX SEQUENCE OF OspfStubAreaEntry
3530 + MAX-ACCESS not-accessible
3531 + STATUS current
3532 + DESCRIPTION
3533 + "The set of metrics that will be advertised by
3534 + a default Area Border Router into a stub area."
3535 + REFERENCE
3536 + "OSPF Version 2, Appendix C.2, Area Parameters"
3537 + ::= { ospf 3 }
3538 +
3539 +
3540 + ospfStubAreaEntry OBJECT-TYPE
3541 + SYNTAX OspfStubAreaEntry
3542 + MAX-ACCESS not-accessible
3543 + STATUS current
3544 + DESCRIPTION
3545 + "The metric for a given Type of Service that
3546 + will be advertised by a default Area Border
3547 + Router into a stub area."
3548 + REFERENCE
3549 + "OSPF Version 2, Appendix C.2, Area Parameters"
3550 + INDEX { ospfStubAreaId, ospfStubTOS }
3551 + ::= { ospfStubAreaTable 1 }
3552 +
3553 +OspfStubAreaEntry ::=
3554 + SEQUENCE {
3555 + ospfStubAreaId
3556 + AreaID,
3557 + ospfStubTOS
3558 + TOSType,
3559 + ospfStubMetric
3560 + BigMetric,
3561 + ospfStubStatus
3562 + RowStatus,
3563 + ospfStubMetricType
3564 + INTEGER
3565 + }
3566 +
3567 + ospfStubAreaId OBJECT-TYPE
3568 + SYNTAX AreaID
3569 + MAX-ACCESS read-only
3570 + STATUS current
3571 + DESCRIPTION
3572 + "The 32 bit identifier for the Stub Area. On
3573 + creation, this can be derived from the in-
3574 + stance."
3575 + ::= { ospfStubAreaEntry 1 }
3576 +
3577 +
3578 + ospfStubTOS OBJECT-TYPE
3579 + SYNTAX TOSType
3580 + MAX-ACCESS read-only
3581 + STATUS current
3582 + DESCRIPTION
3583 + "The Type of Service associated with the
3584 + metric. On creation, this can be derived from
3585 + the instance."
3586 + ::= { ospfStubAreaEntry 2 }
3587 +
3588 +
3589 + ospfStubMetric OBJECT-TYPE
3590 + SYNTAX BigMetric
3591 + MAX-ACCESS read-create
3592 + STATUS current
3593 + DESCRIPTION
3594 + "The metric value applied at the indicated type
3595 + of service. By default, this equals the least
3596 + metric at the type of service among the inter-
3597 + faces to other areas."
3598 + ::= { ospfStubAreaEntry 3 }
3599 +
3600 +
3601 + ospfStubStatus OBJECT-TYPE
3602 + SYNTAX RowStatus
3603 + MAX-ACCESS read-create
3604 + STATUS current
3605 + DESCRIPTION
3606 + "This variable displays the status of the en-
3607 + try. Setting it to 'invalid' has the effect of
3608 + rendering it inoperative. The internal effect
3609 + (row removal) is implementation dependent."
3610 + ::= { ospfStubAreaEntry 4 }
3611 +
3612 + ospfStubMetricType OBJECT-TYPE
3613 + SYNTAX INTEGER {
3614 + ospfMetric (1), -- OSPF Metric
3615 + comparableCost (2), -- external type 1
3616 + nonComparable (3) -- external type 2
3617 + }
3618 + MAX-ACCESS read-create
3619 + STATUS current
3620 + DESCRIPTION
3621 + "This variable displays the type of metric ad-
3622 + vertised as a default route."
3623 + DEFVAL { ospfMetric }
3624 + ::= { ospfStubAreaEntry 5 }
3625 +
3626 +-- OSPF Link State Database
3627 +
3628 +-- The Link State Database contains the Link State
3629 +-- Advertisements from throughout the areas that the
3630 +-- device is attached to.
3631 +
3632 +
3633 + ospfLsdbTable OBJECT-TYPE
3634 + SYNTAX SEQUENCE OF OspfLsdbEntry
3635 + MAX-ACCESS not-accessible
3636 + STATUS current
3637 + DESCRIPTION
3638 + "The OSPF Process's Link State Database."
3639 + REFERENCE
3640 + "OSPF Version 2, Section 12 Link State Adver-
3641 + tisements"
3642 + ::= { ospf 4 }
3643 +
3644 +
3645 + ospfLsdbEntry OBJECT-TYPE
3646 + SYNTAX OspfLsdbEntry
3647 + MAX-ACCESS not-accessible
3648 + STATUS current
3649 + DESCRIPTION
3650 + "A single Link State Advertisement."
3651 + INDEX { ospfLsdbAreaId, ospfLsdbType,
3652 + ospfLsdbLsid, ospfLsdbRouterId }
3653 + ::= { ospfLsdbTable 1 }
3654 +
3655 +OspfLsdbEntry ::=
3656 + SEQUENCE {
3657 + ospfLsdbAreaId
3658 + AreaID,
3659 + ospfLsdbType
3660 + INTEGER,
3661 + ospfLsdbLsid
3662 + IpAddress,
3663 + ospfLsdbRouterId
3664 + RouterID,
3665 + ospfLsdbSequence
3666 + Integer32,
3667 + ospfLsdbAge
3668 + Integer32,
3669 + ospfLsdbChecksum
3670 + Integer32,
3671 + ospfLsdbAdvertisement
3672 + OCTET STRING
3673 + }
3674 + ospfLsdbAreaId OBJECT-TYPE
3675 + SYNTAX AreaID
3676 + MAX-ACCESS read-only
3677 + STATUS current
3678 + DESCRIPTION
3679 + "The 32 bit identifier of the Area from which
3680 + the LSA was received."
3681 + REFERENCE
3682 + "OSPF Version 2, Appendix C.2 Area parameters"
3683 + ::= { ospfLsdbEntry 1 }
3684 +
3685 +-- External Link State Advertisements are permitted
3686 +-- for backward compatibility, but should be displayed in
3687 +-- the ospfExtLsdbTable rather than here.
3688 +
3689 + ospfLsdbType OBJECT-TYPE
3690 + SYNTAX INTEGER {
3691 + routerLink (1),
3692 + networkLink (2),
3693 + summaryLink (3),
3694 + asSummaryLink (4),
3695 + asExternalLink (5), -- but see ospfExtLsdbTable
3696 + multicastLink (6),
3697 + nssaExternalLink (7)
3698 + }
3699 + MAX-ACCESS read-only
3700 + STATUS current
3701 + DESCRIPTION
3702 + "The type of the link state advertisement.
3703 + Each link state type has a separate advertise-
3704 + ment format."
3705 + REFERENCE
3706 + "OSPF Version 2, Appendix A.4.1 The Link State
3707 + Advertisement header"
3708 + ::= { ospfLsdbEntry 2 }
3709 +
3710 + ospfLsdbLsid OBJECT-TYPE
3711 + SYNTAX IpAddress
3712 + MAX-ACCESS read-only
3713 + STATUS current
3714 + DESCRIPTION
3715 + "The Link State ID is an LS Type Specific field
3716 + containing either a Router ID or an IP Address;
3717 + it identifies the piece of the routing domain
3718 + that is being described by the advertisement."
3719 + REFERENCE
3720 + "OSPF Version 2, Section 12.1.4 Link State ID"
3721 + ::= { ospfLsdbEntry 3 }
3722 + ospfLsdbRouterId OBJECT-TYPE
3723 + SYNTAX RouterID
3724 + MAX-ACCESS read-only
3725 + STATUS current
3726 + DESCRIPTION
3727 + "The 32 bit number that uniquely identifies the
3728 + originating router in the Autonomous System."
3729 + REFERENCE
3730 + "OSPF Version 2, Appendix C.1 Global parameters"
3731 + ::= { ospfLsdbEntry 4 }
3732 +
3733 +-- Note that the OSPF Sequence Number is a 32 bit signed
3734 +-- integer. It starts with the value '80000001'h,
3735 +-- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h
3736 +-- Thus, a typical sequence number will be very negative.
3737 +
3738 + ospfLsdbSequence OBJECT-TYPE
3739 + SYNTAX Integer32
3740 + MAX-ACCESS read-only
3741 + STATUS current
3742 + DESCRIPTION
3743 + "The sequence number field is a signed 32-bit
3744 + integer. It is used to detect old and dupli-
3745 + cate link state advertisements. The space of
3746 + sequence numbers is linearly ordered. The
3747 + larger the sequence number the more recent the
3748 + advertisement."
3749 + REFERENCE
3750 + "OSPF Version 2, Section 12.1.6 LS sequence
3751 + number"
3752 + ::= { ospfLsdbEntry 5 }
3753 +
3754 +
3755 + ospfLsdbAge OBJECT-TYPE
3756 + SYNTAX Integer32 -- Should be 0..MaxAge
3757 + MAX-ACCESS read-only
3758 + STATUS current
3759 + DESCRIPTION
3760 + "This field is the age of the link state adver-
3761 + tisement in seconds."
3762 + REFERENCE
3763 + "OSPF Version 2, Section 12.1.1 LS age"
3764 + ::= { ospfLsdbEntry 6 }
3765 +
3766 + ospfLsdbChecksum OBJECT-TYPE
3767 + SYNTAX Integer32
3768 + MAX-ACCESS read-only
3769 + STATUS current
3770 + DESCRIPTION
3771 + "This field is the checksum of the complete
3772 + contents of the advertisement, excepting the
3773 + age field. The age field is excepted so that
3774 + an advertisement's age can be incremented
3775 + without updating the checksum. The checksum
3776 + used is the same that is used for ISO connec-
3777 + tionless datagrams; it is commonly referred to
3778 + as the Fletcher checksum."
3779 + REFERENCE
3780 + "OSPF Version 2, Section 12.1.7 LS checksum"
3781 + ::= { ospfLsdbEntry 7 }
3782 +
3783 +
3784 + ospfLsdbAdvertisement OBJECT-TYPE
3785 + SYNTAX OCTET STRING (SIZE (1..65535))
3786 + MAX-ACCESS read-only
3787 + STATUS current
3788 + DESCRIPTION
3789 + "The entire Link State Advertisement, including
3790 + its header."
3791 + REFERENCE
3792 + "OSPF Version 2, Section 12 Link State Adver-
3793 + tisements"
3794 + ::= { ospfLsdbEntry 8 }
3795 +
3796 +
3797 +-- Address Range Table
3798 +
3799 +-- The Address Range Table acts as an adjunct to the Area
3800 +-- Table; It describes those Address Range Summaries that
3801 +-- are configured to be propagated from an Area to reduce
3802 +-- the amount of information about it which is known beyond
3803 +-- its borders.
3804 +
3805 + ospfAreaRangeTable OBJECT-TYPE
3806 + SYNTAX SEQUENCE OF OspfAreaRangeEntry
3807 + MAX-ACCESS not-accessible
3808 + STATUS obsolete
3809 + DESCRIPTION
3810 + "A range if IP addresses specified by an IP
3811 + address/IP network mask pair. For example,
3812 + class B address range of X.X.X.X with a network
3813 + mask of 255.255.0.0 includes all IP addresses
3814 + from X.X.0.0 to X.X.255.255"
3815 + REFERENCE
3816 + "OSPF Version 2, Appendix C.2 Area parameters"
3817 + ::= { ospf 5 }
3818 + ospfAreaRangeEntry OBJECT-TYPE
3819 + SYNTAX OspfAreaRangeEntry
3820 + MAX-ACCESS not-accessible
3821 + STATUS obsolete
3822 + DESCRIPTION
3823 + "A range if IP addresses specified by an IP
3824 + address/IP network mask pair. For example,
3825 + class B address range of X.X.X.X with a network
3826 + mask of 255.255.0.0 includes all IP addresses
3827 + from X.X.0.0 to X.X.255.255"
3828 + REFERENCE
3829 + "OSPF Version 2, Appendix C.2 Area parameters"
3830 + INDEX { ospfAreaRangeAreaId, ospfAreaRangeNet }
3831 + ::= { ospfAreaRangeTable 1 }
3832 +
3833 +OspfAreaRangeEntry ::=
3834 + SEQUENCE {
3835 + ospfAreaRangeAreaId
3836 + AreaID,
3837 + ospfAreaRangeNet
3838 + IpAddress,
3839 + ospfAreaRangeMask
3840 + IpAddress,
3841 + ospfAreaRangeStatus
3842 + RowStatus,
3843 + ospfAreaRangeEffect
3844 + INTEGER
3845 + }
3846 +
3847 + ospfAreaRangeAreaId OBJECT-TYPE
3848 + SYNTAX AreaID
3849 + MAX-ACCESS read-only
3850 + STATUS obsolete
3851 + DESCRIPTION
3852 + "The Area the Address Range is to be found
3853 + within."
3854 + REFERENCE
3855 + "OSPF Version 2, Appendix C.2 Area parameters"
3856 + ::= { ospfAreaRangeEntry 1 }
3857 +
3858 +
3859 + ospfAreaRangeNet OBJECT-TYPE
3860 + SYNTAX IpAddress
3861 + MAX-ACCESS read-only
3862 + STATUS obsolete
3863 + DESCRIPTION
3864 + "The IP Address of the Net or Subnet indicated
3865 + by the range."
3866 + REFERENCE
3867 + "OSPF Version 2, Appendix C.2 Area parameters"
3868 + ::= { ospfAreaRangeEntry 2 }
3869 +
3870 +
3871 + ospfAreaRangeMask OBJECT-TYPE
3872 + SYNTAX IpAddress
3873 + MAX-ACCESS read-create
3874 + STATUS obsolete
3875 + DESCRIPTION
3876 + "The Subnet Mask that pertains to the Net or
3877 + Subnet."
3878 + REFERENCE
3879 + "OSPF Version 2, Appendix C.2 Area parameters"
3880 + ::= { ospfAreaRangeEntry 3 }
3881 +
3882 + ospfAreaRangeStatus OBJECT-TYPE
3883 + SYNTAX RowStatus
3884 + MAX-ACCESS read-create
3885 + STATUS obsolete
3886 + DESCRIPTION
3887 + "This variable displays the status of the en-
3888 + try. Setting it to 'invalid' has the effect of
3889 + rendering it inoperative. The internal effect
3890 + (row removal) is implementation dependent."
3891 + ::= { ospfAreaRangeEntry 4 }
3892 +
3893 +
3894 + ospfAreaRangeEffect OBJECT-TYPE
3895 + SYNTAX INTEGER {
3896 + advertiseMatching (1),
3897 + doNotAdvertiseMatching (2)
3898 + }
3899 + MAX-ACCESS read-create
3900 + STATUS obsolete
3901 + DESCRIPTION
3902 + "Subnets subsumed by ranges either trigger the
3903 + advertisement of the indicated summary (adver-
3904 + tiseMatching), or result in the subnet's not
3905 + being advertised at all outside the area."
3906 + DEFVAL { advertiseMatching }
3907 + ::= { ospfAreaRangeEntry 5 }
3908 +
3909 +
3910 +
3911 +-- OSPF Host Table
3912 +
3913 +-- The Host/Metric Table indicates what hosts are directly
3914 +-- attached to the Router, and what metrics and types of
3915 +-- service should be advertised for them.
3916 +
3917 + ospfHostTable OBJECT-TYPE
3918 + SYNTAX SEQUENCE OF OspfHostEntry
3919 + MAX-ACCESS not-accessible
3920 + STATUS current
3921 + DESCRIPTION
3922 + "The list of Hosts, and their metrics, that the
3923 + router will advertise as host routes."
3924 + REFERENCE
3925 + "OSPF Version 2, Appendix C.6 Host route param-
3926 + eters"
3927 + ::= { ospf 6 }
3928 +
3929 +
3930 + ospfHostEntry OBJECT-TYPE
3931 + SYNTAX OspfHostEntry
3932 + MAX-ACCESS not-accessible
3933 + STATUS current
3934 + DESCRIPTION
3935 + "A metric to be advertised, for a given type of
3936 + service, when a given host is reachable."
3937 + INDEX { ospfHostIpAddress, ospfHostTOS }
3938 + ::= { ospfHostTable 1 }
3939 +
3940 +OspfHostEntry ::=
3941 + SEQUENCE {
3942 + ospfHostIpAddress
3943 + IpAddress,
3944 + ospfHostTOS
3945 + TOSType,
3946 + ospfHostMetric
3947 + Metric,
3948 + ospfHostStatus
3949 + RowStatus,
3950 + ospfHostAreaID
3951 + AreaID
3952 + }
3953 +
3954 + ospfHostIpAddress OBJECT-TYPE
3955 + SYNTAX IpAddress
3956 + MAX-ACCESS read-only
3957 + STATUS current
3958 + DESCRIPTION
3959 + "The IP Address of the Host."
3960 + REFERENCE
3961 + "OSPF Version 2, Appendix C.6 Host route parame-
3962 + ters"
3963 + ::= { ospfHostEntry 1 }
3964 +
3965 +
3966 + ospfHostTOS OBJECT-TYPE
3967 + SYNTAX TOSType
3968 + MAX-ACCESS read-only
3969 + STATUS current
3970 + DESCRIPTION
3971 + "The Type of Service of the route being config-
3972 + ured."
3973 + REFERENCE
3974 + "OSPF Version 2, Appendix C.6 Host route parame-
3975 + ters"
3976 + ::= { ospfHostEntry 2 }
3977 +
3978 +
3979 + ospfHostMetric OBJECT-TYPE
3980 + SYNTAX Metric
3981 + MAX-ACCESS read-create
3982 + STATUS current
3983 + DESCRIPTION
3984 + "The Metric to be advertised."
3985 + REFERENCE
3986 + "OSPF Version 2, Appendix C.6 Host route parame-
3987 + ters"
3988 + ::= { ospfHostEntry 3 }
3989 +
3990 + ospfHostStatus OBJECT-TYPE
3991 + SYNTAX RowStatus
3992 + MAX-ACCESS read-create
3993 + STATUS current
3994 + DESCRIPTION
3995 + "This variable displays the status of the en-
3996 + try. Setting it to 'invalid' has the effect of
3997 + rendering it inoperative. The internal effect
3998 + (row removal) is implementation dependent."
3999 + ::= { ospfHostEntry 4 }
4000 +
4001 +
4002 + ospfHostAreaID OBJECT-TYPE
4003 + SYNTAX AreaID
4004 + MAX-ACCESS read-only
4005 + STATUS current
4006 + DESCRIPTION
4007 + "The Area the Host Entry is to be found within.
4008 + By default, the area that a subsuming OSPF in-
4009 + terface is in, or 0.0.0.0"
4010 + REFERENCE
4011 + "OSPF Version 2, Appendix C.2 Area parameters"
4012 + ::= { ospfHostEntry 5 }
4013 +
4014 +
4015 +-- OSPF Interface Table
4016 +
4017 +-- The OSPF Interface Table augments the ipAddrTable
4018 +-- with OSPF specific information.
4019 +
4020 + ospfIfTable OBJECT-TYPE
4021 + SYNTAX SEQUENCE OF OspfIfEntry
4022 + MAX-ACCESS not-accessible
4023 + STATUS current
4024 + DESCRIPTION
4025 + "The OSPF Interface Table describes the inter-
4026 + faces from the viewpoint of OSPF."
4027 + REFERENCE
4028 + "OSPF Version 2, Appendix C.3 Router interface
4029 + parameters"
4030 + ::= { ospf 7 }
4031 +
4032 +
4033 + ospfIfEntry OBJECT-TYPE
4034 + SYNTAX OspfIfEntry
4035 + MAX-ACCESS not-accessible
4036 + STATUS current
4037 + DESCRIPTION
4038 + "The OSPF Interface Entry describes one inter-
4039 + face from the viewpoint of OSPF."
4040 + INDEX { ospfIfIpAddress, ospfAddressLessIf }
4041 + ::= { ospfIfTable 1 }
4042 +
4043 +OspfIfEntry ::=
4044 + SEQUENCE {
4045 + ospfIfIpAddress
4046 + IpAddress,
4047 + ospfAddressLessIf
4048 + Integer32,
4049 + ospfIfAreaId
4050 + AreaID,
4051 + ospfIfType
4052 + INTEGER,
4053 + ospfIfAdminStat
4054 + Status,
4055 + ospfIfRtrPriority
4056 + DesignatedRouterPriority,
4057 + ospfIfTransitDelay
4058 + UpToMaxAge,
4059 + ospfIfRetransInterval
4060 + UpToMaxAge,
4061 + ospfIfHelloInterval
4062 + HelloRange,
4063 + ospfIfRtrDeadInterval
4064 + PositiveInteger,
4065 + ospfIfPollInterval
4066 + PositiveInteger,
4067 + ospfIfState
4068 + INTEGER,
4069 + ospfIfDesignatedRouter
4070 + IpAddress,
4071 + ospfIfBackupDesignatedRouter
4072 + IpAddress,
4073 + ospfIfEvents
4074 + Counter32,
4075 + ospfIfAuthType
4076 + INTEGER,
4077 + ospfIfAuthKey
4078 + OCTET STRING,
4079 + ospfIfStatus
4080 + RowStatus,
4081 + ospfIfMulticastForwarding
4082 + INTEGER,
4083 + ospfIfDemand
4084 + TruthValue
4085 + }
4086 +
4087 + ospfIfIpAddress OBJECT-TYPE
4088 + SYNTAX IpAddress
4089 + MAX-ACCESS read-only
4090 + STATUS current
4091 + DESCRIPTION
4092 + "The IP address of this OSPF interface."
4093 + ::= { ospfIfEntry 1 }
4094 +
4095 + ospfAddressLessIf OBJECT-TYPE
4096 + SYNTAX Integer32
4097 + MAX-ACCESS read-only
4098 + STATUS current
4099 + DESCRIPTION
4100 + "For the purpose of easing the instancing of
4101 + addressed and addressless interfaces; This
4102 + variable takes the value 0 on interfaces with
4103 + IP Addresses, and the corresponding value of
4104 + ifIndex for interfaces having no IP Address."
4105 + ::= { ospfIfEntry 2 }
4106 + ospfIfAreaId OBJECT-TYPE
4107 + SYNTAX AreaID
4108 + MAX-ACCESS read-create
4109 + STATUS current
4110 + DESCRIPTION
4111 + "A 32-bit integer uniquely identifying the area
4112 + to which the interface connects. Area ID
4113 + 0.0.0.0 is used for the OSPF backbone."
4114 + DEFVAL { '00000000'H } -- 0.0.0.0
4115 + ::= { ospfIfEntry 3 }
4116 +
4117 + ospfIfType OBJECT-TYPE
4118 + SYNTAX INTEGER {
4119 + broadcast (1),
4120 + nbma (2),
4121 + pointToPoint (3),
4122 + pointToMultipoint (5)
4123 + }
4124 + MAX-ACCESS read-create
4125 + STATUS current
4126 + DESCRIPTION
4127 + "The OSPF interface type.
4128 +
4129 + By way of a default, this field may be intuited
4130 + from the corresponding value of ifType. Broad-
4131 + cast LANs, such as Ethernet and IEEE 802.5,
4132 + take the value 'broadcast', X.25 and similar
4133 + technologies take the value 'nbma', and links
4134 + that are definitively point to point take the
4135 + value 'pointToPoint'."
4136 + ::= { ospfIfEntry 4 }
4137 +
4138 +
4139 + ospfIfAdminStat OBJECT-TYPE
4140 + SYNTAX Status
4141 + MAX-ACCESS read-create
4142 + STATUS current
4143 + DESCRIPTION
4144 + "The OSPF interface's administrative status.
4145 + The value formed on the interface, and the in-
4146 + terface will be advertised as an internal route
4147 + to some area. The value 'disabled' denotes
4148 + that the interface is external to OSPF."
4149 + DEFVAL { enabled }
4150 + ::= { ospfIfEntry 5 }
4151 +
4152 + ospfIfRtrPriority OBJECT-TYPE
4153 + SYNTAX DesignatedRouterPriority
4154 + MAX-ACCESS read-create
4155 + STATUS current
4156 + DESCRIPTION
4157 + "The priority of this interface. Used in
4158 + multi-access networks, this field is used in
4159 + the designated router election algorithm. The
4160 + value 0 signifies that the router is not eligi-
4161 + ble to become the designated router on this
4162 + particular network. In the event of a tie in
4163 + this value, routers will use their Router ID as
4164 + a tie breaker."
4165 + DEFVAL { 1 }
4166 + ::= { ospfIfEntry 6 }
4167 +
4168 +
4169 + ospfIfTransitDelay OBJECT-TYPE
4170 + SYNTAX UpToMaxAge
4171 + MAX-ACCESS read-create
4172 + STATUS current
4173 + DESCRIPTION
4174 + "The estimated number of seconds it takes to
4175 + transmit a link state update packet over this
4176 + interface."
4177 + DEFVAL { 1 }
4178 + ::= { ospfIfEntry 7 }
4179 +
4180 +
4181 + ospfIfRetransInterval OBJECT-TYPE
4182 + SYNTAX UpToMaxAge
4183 + MAX-ACCESS read-create
4184 + STATUS current
4185 + DESCRIPTION
4186 + "The number of seconds between link-state ad-
4187 + vertisement retransmissions, for adjacencies
4188 + belonging to this interface. This value is
4189 + also used when retransmitting database descrip-
4190 + tion and link-state request packets."
4191 + DEFVAL { 5 }
4192 + ::= { ospfIfEntry 8 }
4193 +
4194 +
4195 + ospfIfHelloInterval OBJECT-TYPE
4196 + SYNTAX HelloRange
4197 + MAX-ACCESS read-create
4198 + STATUS current
4199 + DESCRIPTION
4200 + "The length of time, in seconds, between the
4201 + Hello packets that the router sends on the in-
4202 + terface. This value must be the same for all
4203 + routers attached to a common network."
4204 + DEFVAL { 10 }
4205 + ::= { ospfIfEntry 9 }
4206 +
4207 +
4208 + ospfIfRtrDeadInterval OBJECT-TYPE
4209 + SYNTAX PositiveInteger
4210 + MAX-ACCESS read-create
4211 + STATUS current
4212 + DESCRIPTION
4213 + "The number of seconds that a router's Hello
4214 + packets have not been seen before it's neigh-
4215 + bors declare the router down. This should be
4216 + some multiple of the Hello interval. This
4217 + value must be the same for all routers attached
4218 + to a common network."
4219 + DEFVAL { 40 }
4220 + ::= { ospfIfEntry 10 }
4221 +
4222 +
4223 + ospfIfPollInterval OBJECT-TYPE
4224 + SYNTAX PositiveInteger
4225 + MAX-ACCESS read-create
4226 + STATUS current
4227 + DESCRIPTION
4228 + "The larger time interval, in seconds, between
4229 + the Hello packets sent to an inactive non-
4230 + broadcast multi- access neighbor."
4231 + DEFVAL { 120 }
4232 + ::= { ospfIfEntry 11 }
4233 +
4234 +
4235 + ospfIfState OBJECT-TYPE
4236 + SYNTAX INTEGER {
4237 + down (1),
4238 + loopback (2),
4239 + waiting (3),
4240 + pointToPoint (4),
4241 + designatedRouter (5),
4242 + backupDesignatedRouter (6),
4243 + otherDesignatedRouter (7)
4244 + }
4245 + MAX-ACCESS read-only
4246 + STATUS current
4247 + DESCRIPTION
4248 + "The OSPF Interface State."
4249 + DEFVAL { down }
4250 + ::= { ospfIfEntry 12 }
4251 +
4252 +
4253 + ospfIfDesignatedRouter OBJECT-TYPE
4254 + SYNTAX IpAddress
4255 + MAX-ACCESS read-only
4256 + STATUS current
4257 + DESCRIPTION
4258 + "The IP Address of the Designated Router."
4259 + DEFVAL { '00000000'H } -- 0.0.0.0
4260 + ::= { ospfIfEntry 13 }
4261 +
4262 +
4263 + ospfIfBackupDesignatedRouter OBJECT-TYPE
4264 + SYNTAX IpAddress
4265 + MAX-ACCESS read-only
4266 + STATUS current
4267 + DESCRIPTION
4268 + "The IP Address of the Backup Designated
4269 + Router."
4270 + DEFVAL { '00000000'H } -- 0.0.0.0
4271 + ::= { ospfIfEntry 14 }
4272 +
4273 + ospfIfEvents OBJECT-TYPE
4274 + SYNTAX Counter32
4275 + MAX-ACCESS read-only
4276 + STATUS current
4277 + DESCRIPTION
4278 + "The number of times this OSPF interface has
4279 + changed its state, or an error has occurred."
4280 + ::= { ospfIfEntry 15 }
4281 +
4282 +
4283 + ospfIfAuthKey OBJECT-TYPE
4284 + SYNTAX OCTET STRING (SIZE (0..256))
4285 + MAX-ACCESS read-create
4286 + STATUS current
4287 + DESCRIPTION
4288 + "The Authentication Key. If the Area's Author-
4289 + ization Type is simplePassword, and the key
4290 + length is shorter than 8 octets, the agent will
4291 + left adjust and zero fill to 8 octets.
4292 +
4293 + Note that unauthenticated interfaces need no
4294 + authentication key, and simple password authen-
4295 + tication cannot use a key of more than 8 oc-
4296 + tets. Larger keys are useful only with authen-
4297 + tication mechanisms not specified in this docu-
4298 + ment.
4299 +
4300 + When read, ospfIfAuthKey always returns an Oc-
4301 + tet String of length zero."
4302 + REFERENCE
4303 + "OSPF Version 2, Section 9 The Interface Data
4304 + Structure"
4305 + DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0
4306 + ::= { ospfIfEntry 16 }
4307 +
4308 + ospfIfStatus OBJECT-TYPE
4309 + SYNTAX RowStatus
4310 + MAX-ACCESS read-create
4311 + STATUS current
4312 + DESCRIPTION
4313 + "This variable displays the status of the en-
4314 + try. Setting it to 'invalid' has the effect of
4315 + rendering it inoperative. The internal effect
4316 + (row removal) is implementation dependent."
4317 + ::= { ospfIfEntry 17 }
4318 +
4319 +
4320 + ospfIfMulticastForwarding OBJECT-TYPE
4321 + SYNTAX INTEGER {
4322 + blocked (1), -- no multicast forwarding
4323 + multicast (2), -- using multicast address
4324 + unicast (3) -- to each OSPF neighbor
4325 + }
4326 + MAX-ACCESS read-create
4327 + STATUS current
4328 + DESCRIPTION
4329 + "The way multicasts should forwarded on this
4330 + interface; not forwarded, forwarded as data
4331 + link multicasts, or forwarded as data link uni-
4332 + casts. Data link multicasting is not meaning-
4333 + ful on point to point and NBMA interfaces, and
4334 + setting ospfMulticastForwarding to 0 effective-
4335 + ly disables all multicast forwarding."
4336 + DEFVAL { blocked }
4337 + ::= { ospfIfEntry 18 }
4338 +
4339 +
4340 + ospfIfDemand OBJECT-TYPE
4341 + SYNTAX TruthValue
4342 + MAX-ACCESS read-create
4343 + STATUS current
4344 + DESCRIPTION
4345 + "Indicates whether Demand OSPF procedures (hel-
4346 + lo supression to FULL neighbors and setting the
4347 + DoNotAge flag on proogated LSAs) should be per-
4348 + formed on this interface."
4349 + DEFVAL { false }
4350 + ::= { ospfIfEntry 19 }
4351 +
4352 +
4353 + ospfIfAuthType OBJECT-TYPE
4354 + SYNTAX INTEGER (0..255)
4355 + -- none (0),
4356 + -- simplePassword (1)
4357 + -- md5 (2)
4358 + -- reserved for specification by IANA (> 2)
4359 + MAX-ACCESS read-create
4360 + STATUS current
4361 + DESCRIPTION
4362 + "The authentication type specified for an in-
4363 + terface. Additional authentication types may
4364 + be assigned locally."
4365 + REFERENCE
4366 + "OSPF Version 2, Appendix E Authentication"
4367 + DEFVAL { 0 } -- no authentication, by default
4368 + ::= { ospfIfEntry 20 }
4369 +
4370 +
4371 +-- OSPF Interface Metric Table
4372 +
4373 +-- The Metric Table describes the metrics to be advertised
4374 +-- for a specified interface at the various types of service.
4375 +-- As such, this table is an adjunct of the OSPF Interface
4376 +-- Table.
4377 +
4378 +-- Types of service, as defined by RFC 791, have the ability
4379 +-- to request low delay, high bandwidth, or reliable linkage.
4380 +
4381 +-- For the purposes of this specification, the measure of
4382 +-- bandwidth
4383 +
4384 +-- Metric = 10^8 / ifSpeed
4385 +
4386 +-- is the default value. For multiple link interfaces, note
4387 +-- that ifSpeed is the sum of the individual link speeds.
4388 +-- This yields a number having the following typical values:
4389 +
4390 +-- Network Type/bit rate Metric
4391 +
4392 +-- >= 100 MBPS 1
4393 +-- Ethernet/802.3 10
4394 +-- E1 48
4395 +-- T1 (ESF) 65
4396 +-- 64 KBPS 1562
4397 +-- 56 KBPS 1785
4398 +-- 19.2 KBPS 5208
4399 +-- 9.6 KBPS 10416
4400 +
4401 +-- Routes that are not specified use the default (TOS 0) metric
4402 +
4403 + ospfIfMetricTable OBJECT-TYPE
4404 + SYNTAX SEQUENCE OF OspfIfMetricEntry
4405 + MAX-ACCESS not-accessible
4406 + STATUS current
4407 + DESCRIPTION
4408 + "The TOS metrics for a non-virtual interface
4409 + identified by the interface index."
4410 + REFERENCE
4411 + "OSPF Version 2, Appendix C.3 Router interface
4412 + parameters"
4413 + ::= { ospf 8 }
4414 +
4415 + ospfIfMetricEntry OBJECT-TYPE
4416 + SYNTAX OspfIfMetricEntry
4417 + MAX-ACCESS not-accessible
4418 + STATUS current
4419 + DESCRIPTION
4420 + "A particular TOS metric for a non-virtual in-
4421 + terface identified by the interface index."
4422 + REFERENCE
4423 + "OSPF Version 2, Appendix C.3 Router interface
4424 + parameters"
4425 + INDEX { ospfIfMetricIpAddress,
4426 + ospfIfMetricAddressLessIf,
4427 + ospfIfMetricTOS }
4428 + ::= { ospfIfMetricTable 1 }
4429 +
4430 +OspfIfMetricEntry ::=
4431 + SEQUENCE {
4432 + ospfIfMetricIpAddress
4433 + IpAddress,
4434 + ospfIfMetricAddressLessIf
4435 + Integer32,
4436 + ospfIfMetricTOS
4437 + TOSType,
4438 + ospfIfMetricValue
4439 + Metric,
4440 + ospfIfMetricStatus
4441 + RowStatus
4442 + }
4443 +
4444 + ospfIfMetricIpAddress OBJECT-TYPE
4445 + SYNTAX IpAddress
4446 + MAX-ACCESS read-only
4447 + STATUS current
4448 + DESCRIPTION
4449 + "The IP address of this OSPF interface. On row
4450 + creation, this can be derived from the in-
4451 + stance."
4452 + ::= { ospfIfMetricEntry 1 }
4453 +
4454 + ospfIfMetricAddressLessIf OBJECT-TYPE
4455 + SYNTAX Integer32
4456 + MAX-ACCESS read-only
4457 + STATUS current
4458 + DESCRIPTION
4459 + "For the purpose of easing the instancing of
4460 + addressed and addressless interfaces; This
4461 + variable takes the value 0 on interfaces with
4462 + IP Addresses, and the value of ifIndex for in-
4463 + terfaces having no IP Address. On row crea-
4464 + tion, this can be derived from the instance."
4465 + ::= { ospfIfMetricEntry 2 }
4466 +
4467 +
4468 + ospfIfMetricTOS OBJECT-TYPE
4469 + SYNTAX TOSType
4470 + MAX-ACCESS read-only
4471 + STATUS current
4472 + DESCRIPTION
4473 + "The type of service metric being referenced.
4474 + On row creation, this can be derived from the
4475 + instance."
4476 + ::= { ospfIfMetricEntry 3 }
4477 +
4478 +
4479 + ospfIfMetricValue OBJECT-TYPE
4480 + SYNTAX Metric
4481 + MAX-ACCESS read-create
4482 + STATUS current
4483 + DESCRIPTION
4484 + "The metric of using this type of service on
4485 + this interface. The default value of the TOS 0
4486 + Metric is 10^8 / ifSpeed."
4487 + ::= { ospfIfMetricEntry 4 }
4488 +
4489 + ospfIfMetricStatus OBJECT-TYPE
4490 + SYNTAX RowStatus
4491 + MAX-ACCESS read-create
4492 + STATUS current
4493 + DESCRIPTION
4494 + "This variable displays the status of the en-
4495 + try. Setting it to 'invalid' has the effect of
4496 + rendering it inoperative. The internal effect
4497 + (row removal) is implementation dependent."
4498 + ::= { ospfIfMetricEntry 5 }
4499 +
4500 +
4501 +-- OSPF Virtual Interface Table
4502 +
4503 +-- The Virtual Interface Table describes the virtual
4504 +-- links that the OSPF Process is configured to
4505 +-- carry on.
4506 +
4507 + ospfVirtIfTable OBJECT-TYPE
4508 + SYNTAX SEQUENCE OF OspfVirtIfEntry
4509 + MAX-ACCESS not-accessible
4510 + STATUS current
4511 + DESCRIPTION
4512 + "Information about this router's virtual inter-
4513 + faces."
4514 + REFERENCE
4515 + "OSPF Version 2, Appendix C.4 Virtual link
4516 + parameters"
4517 + ::= { ospf 9 }
4518 +
4519 +
4520 + ospfVirtIfEntry OBJECT-TYPE
4521 + SYNTAX OspfVirtIfEntry
4522 + MAX-ACCESS not-accessible
4523 + STATUS current
4524 + DESCRIPTION
4525 + "Information about a single Virtual Interface."
4526 + INDEX { ospfVirtIfAreaId, ospfVirtIfNeighbor }
4527 + ::= { ospfVirtIfTable 1 }
4528 +
4529 +OspfVirtIfEntry ::=
4530 + SEQUENCE {
4531 + ospfVirtIfAreaId
4532 + AreaID,
4533 + ospfVirtIfNeighbor
4534 + RouterID,
4535 + ospfVirtIfTransitDelay
4536 + UpToMaxAge,
4537 + ospfVirtIfRetransInterval
4538 + UpToMaxAge,
4539 + ospfVirtIfHelloInterval
4540 + HelloRange,
4541 + ospfVirtIfRtrDeadInterval
4542 + PositiveInteger,
4543 + ospfVirtIfState
4544 + INTEGER,
4545 + ospfVirtIfEvents
4546 + Counter32,
4547 + ospfVirtIfAuthType
4548 + INTEGER,
4549 + ospfVirtIfAuthKey
4550 + OCTET STRING,
4551 + ospfVirtIfStatus
4552 + RowStatus
4553 + }
4554 +
4555 + ospfVirtIfAreaId OBJECT-TYPE
4556 + SYNTAX AreaID
4557 + MAX-ACCESS read-only
4558 + STATUS current
4559 + DESCRIPTION
4560 + "The Transit Area that the Virtual Link
4561 + traverses. By definition, this is not 0.0.0.0"
4562 + ::= { ospfVirtIfEntry 1 }
4563 +
4564 +
4565 + ospfVirtIfNeighbor OBJECT-TYPE
4566 + SYNTAX RouterID
4567 + MAX-ACCESS read-only
4568 + STATUS current
4569 + DESCRIPTION
4570 + "The Router ID of the Virtual Neighbor."
4571 + ::= { ospfVirtIfEntry 2 }
4572 +
4573 +
4574 + ospfVirtIfTransitDelay OBJECT-TYPE
4575 + SYNTAX UpToMaxAge
4576 + MAX-ACCESS read-create
4577 + STATUS current
4578 + DESCRIPTION
4579 + "The estimated number of seconds it takes to
4580 + transmit a link- state update packet over this
4581 + interface."
4582 + DEFVAL { 1 }
4583 + ::= { ospfVirtIfEntry 3 }
4584 +
4585 +
4586 + ospfVirtIfRetransInterval OBJECT-TYPE
4587 + SYNTAX UpToMaxAge
4588 + MAX-ACCESS read-create
4589 + STATUS current
4590 + DESCRIPTION
4591 + "The number of seconds between link-state ad-
4592 + vertisement retransmissions, for adjacencies
4593 + belonging to this interface. This value is
4594 + also used when retransmitting database descrip-
4595 + tion and link-state request packets. This
4596 + value should be well over the expected round-
4597 + trip time."
4598 + DEFVAL { 5 }
4599 + ::= { ospfVirtIfEntry 4 }
4600 +
4601 +
4602 + ospfVirtIfHelloInterval OBJECT-TYPE
4603 + SYNTAX HelloRange
4604 + MAX-ACCESS read-create
4605 + STATUS current
4606 + DESCRIPTION
4607 + "The length of time, in seconds, between the
4608 + Hello packets that the router sends on the in-
4609 + terface. This value must be the same for the
4610 + virtual neighbor."
4611 + DEFVAL { 10 }
4612 + ::= { ospfVirtIfEntry 5 }
4613 +
4614 +
4615 + ospfVirtIfRtrDeadInterval OBJECT-TYPE
4616 + SYNTAX PositiveInteger
4617 + MAX-ACCESS read-create
4618 + STATUS current
4619 + DESCRIPTION
4620 + "The number of seconds that a router's Hello
4621 + packets have not been seen before it's neigh-
4622 + bors declare the router down. This should be
4623 + some multiple of the Hello interval. This
4624 + value must be the same for the virtual neigh-
4625 + bor."
4626 + DEFVAL { 60 }
4627 + ::= { ospfVirtIfEntry 6 }
4628 +
4629 +
4630 + ospfVirtIfState OBJECT-TYPE
4631 + SYNTAX INTEGER {
4632 + down (1), -- these use the same encoding
4633 + pointToPoint (4) -- as the ospfIfTable
4634 + }
4635 + MAX-ACCESS read-only
4636 + STATUS current
4637 + DESCRIPTION
4638 + "OSPF virtual interface states."
4639 + DEFVAL { down }
4640 + ::= { ospfVirtIfEntry 7 }
4641 +
4642 +
4643 + ospfVirtIfEvents OBJECT-TYPE
4644 + SYNTAX Counter32
4645 + MAX-ACCESS read-only
4646 + STATUS current
4647 + DESCRIPTION
4648 + "The number of state changes or error events on
4649 + this Virtual Link"
4650 + ::= { ospfVirtIfEntry 8 }
4651 +
4652 +
4653 + ospfVirtIfAuthKey OBJECT-TYPE
4654 + SYNTAX OCTET STRING (SIZE(0..256))
4655 + MAX-ACCESS read-create
4656 + STATUS current
4657 + DESCRIPTION
4658 + "If Authentication Type is simplePassword, the
4659 + device will left adjust and zero fill to 8 oc-
4660 + tets.
4661 +
4662 + Note that unauthenticated interfaces need no
4663 + authentication key, and simple password authen-
4664 + tication cannot use a key of more than 8 oc-
4665 + tets. Larger keys are useful only with authen-
4666 + tication mechanisms not specified in this docu-
4667 + ment.
4668 +
4669 + When read, ospfVifAuthKey always returns a
4670 + string of length zero."
4671 + REFERENCE
4672 + "OSPF Version 2, Section 9 The Interface Data
4673 + Structure"
4674 + DEFVAL { '0000000000000000'H } -- 0.0.0.0.0.0.0.0
4675 + ::= { ospfVirtIfEntry 9 }
4676 +
4677 +
4678 + ospfVirtIfStatus OBJECT-TYPE
4679 + SYNTAX RowStatus
4680 + MAX-ACCESS read-create
4681 + STATUS current
4682 + DESCRIPTION
4683 + "This variable displays the status of the en-
4684 + try. Setting it to 'invalid' has the effect of
4685 + rendering it inoperative. The internal effect
4686 + (row removal) is implementation dependent."
4687 + ::= { ospfVirtIfEntry 10 }
4688 +
4689 +
4690 + ospfVirtIfAuthType OBJECT-TYPE
4691 + SYNTAX INTEGER (0..255)
4692 + -- none (0),
4693 + -- simplePassword (1)
4694 + -- md5 (2)
4695 + -- reserved for specification by IANA (> 2)
4696 + MAX-ACCESS read-create
4697 + STATUS current
4698 + DESCRIPTION
4699 + "The authentication type specified for a virtu-
4700 + al interface. Additional authentication types
4701 + may be assigned locally."
4702 + REFERENCE
4703 + "OSPF Version 2, Appendix E Authentication"
4704 + DEFVAL { 0 } -- no authentication, by default
4705 + ::= { ospfVirtIfEntry 11 }
4706 +
4707 +
4708 +-- OSPF Neighbor Table
4709 +
4710 +-- The OSPF Neighbor Table describes all neighbors in
4711 +-- the locality of the subject router.
4712 +
4713 + ospfNbrTable OBJECT-TYPE
4714 + SYNTAX SEQUENCE OF OspfNbrEntry
4715 + MAX-ACCESS not-accessible
4716 + STATUS current
4717 + DESCRIPTION
4718 + "A table of non-virtual neighbor information."
4719 + REFERENCE
4720 + "OSPF Version 2, Section 10 The Neighbor Data
4721 + Structure"
4722 + ::= { ospf 10 }
4723 +
4724 +
4725 + ospfNbrEntry OBJECT-TYPE
4726 + SYNTAX OspfNbrEntry
4727 + MAX-ACCESS not-accessible
4728 + STATUS current
4729 + DESCRIPTION
4730 + "The information regarding a single neighbor."
4731 + REFERENCE
4732 + "OSPF Version 2, Section 10 The Neighbor Data
4733 + Structure"
4734 + INDEX { ospfNbrIpAddr, ospfNbrAddressLessIndex }
4735 + ::= { ospfNbrTable 1 }
4736 +
4737 +OspfNbrEntry ::=
4738 + SEQUENCE {
4739 + ospfNbrIpAddr
4740 + IpAddress,
4741 + ospfNbrAddressLessIndex
4742 + InterfaceIndex,
4743 + ospfNbrRtrId
4744 + RouterID,
4745 + ospfNbrOptions
4746 + Integer32,
4747 + ospfNbrPriority
4748 + DesignatedRouterPriority,
4749 + ospfNbrState
4750 + INTEGER,
4751 + ospfNbrEvents
4752 + Counter32,
4753 + ospfNbrLsRetransQLen
4754 + Gauge32,
4755 + ospfNbmaNbrStatus
4756 + RowStatus,
4757 + ospfNbmaNbrPermanence
4758 + INTEGER,
4759 + ospfNbrHelloSuppressed
4760 + TruthValue
4761 + }
4762 +
4763 + ospfNbrIpAddr OBJECT-TYPE
4764 + SYNTAX IpAddress
4765 + MAX-ACCESS read-only
4766 + STATUS current
4767 + DESCRIPTION
4768 + "The IP address this neighbor is using in its
4769 + IP Source Address. Note that, on addressless
4770 + links, this will not be 0.0.0.0, but the ad-
4771 + dress of another of the neighbor's interfaces."
4772 + ::= { ospfNbrEntry 1 }
4773 +
4774 +
4775 + ospfNbrAddressLessIndex OBJECT-TYPE
4776 + SYNTAX InterfaceIndex
4777 + MAX-ACCESS read-only
4778 + STATUS current
4779 + DESCRIPTION
4780 + "On an interface having an IP Address, zero.
4781 + On addressless interfaces, the corresponding
4782 + value of ifIndex in the Internet Standard MIB.
4783 + On row creation, this can be derived from the
4784 + instance."
4785 + ::= { ospfNbrEntry 2 }
4786 +
4787 +
4788 + ospfNbrRtrId OBJECT-TYPE
4789 + SYNTAX RouterID
4790 + MAX-ACCESS read-only
4791 + STATUS current
4792 + DESCRIPTION
4793 + "A 32-bit integer (represented as a type IpAd-
4794 + dress) uniquely identifying the neighboring
4795 + router in the Autonomous System."
4796 + DEFVAL { '00000000'H } -- 0.0.0.0
4797 + ::= { ospfNbrEntry 3 }
4798 +
4799 +
4800 + ospfNbrOptions OBJECT-TYPE
4801 + SYNTAX Integer32
4802 + MAX-ACCESS read-only
4803 + STATUS current
4804 + DESCRIPTION
4805 + "A Bit Mask corresponding to the neighbor's op-
4806 + tions field.
4807 +
4808 + Bit 0, if set, indicates that the system will
4809 + operate on Type of Service metrics other than
4810 + TOS 0. If zero, the neighbor will ignore all
4811 + metrics except the TOS 0 metric.
4812 +
4813 + Bit 1, if set, indicates that the associated
4814 + area accepts and operates on external informa-
4815 + tion; if zero, it is a stub area.
4816 +
4817 + Bit 2, if set, indicates that the system is ca-
4818 + pable of routing IP Multicast datagrams; i.e.,
4819 + that it implements the Multicast Extensions to
4820 + OSPF.
4821 +
4822 + Bit 3, if set, indicates that the associated
4823 + area is an NSSA. These areas are capable of
4824 + carrying type 7 external advertisements, which
4825 + are translated into type 5 external advertise-
4826 + ments at NSSA borders."
4827 + REFERENCE
4828 + "OSPF Version 2, Section 12.1.2 Options"
4829 + DEFVAL { 0 }
4830 + ::= { ospfNbrEntry 4 }
4831 +
4832 +
4833 + ospfNbrPriority OBJECT-TYPE
4834 + SYNTAX DesignatedRouterPriority
4835 + MAX-ACCESS read-create
4836 + STATUS current
4837 + DESCRIPTION
4838 + "The priority of this neighbor in the designat-
4839 + ed router election algorithm. The value 0 sig-
4840 + nifies that the neighbor is not eligible to be-
4841 + come the designated router on this particular
4842 + network."
4843 + DEFVAL { 1 }
4844 + ::= { ospfNbrEntry 5 }
4845 +
4846 +
4847 + ospfNbrState OBJECT-TYPE
4848 + SYNTAX INTEGER {
4849 + down (1),
4850 + attempt (2),
4851 + init (3),
4852 + twoWay (4),
4853 + exchangeStart (5),
4854 + exchange (6),
4855 + loading (7),
4856 + full (8)
4857 + }
4858 + MAX-ACCESS read-only
4859 + STATUS current
4860 + DESCRIPTION
4861 + "The State of the relationship with this Neigh-
4862 + bor."
4863 + REFERENCE
4864 + "OSPF Version 2, Section 10.1 Neighbor States"
4865 + DEFVAL { down }
4866 + ::= { ospfNbrEntry 6 }
4867 +
4868 +
4869 + ospfNbrEvents OBJECT-TYPE
4870 + SYNTAX Counter32
4871 + MAX-ACCESS read-only
4872 + STATUS current
4873 + DESCRIPTION
4874 + "The number of times this neighbor relationship
4875 + has changed state, or an error has occurred."
4876 + ::= { ospfNbrEntry 7 }
4877 +
4878 +
4879 + ospfNbrLsRetransQLen OBJECT-TYPE
4880 + SYNTAX Gauge32
4881 + MAX-ACCESS read-only
4882 + STATUS current
4883 + DESCRIPTION
4884 + "The current length of the retransmission
4885 + queue."
4886 + ::= { ospfNbrEntry 8 }
4887 +
4888 +
4889 + ospfNbmaNbrStatus OBJECT-TYPE
4890 + SYNTAX RowStatus
4891 + MAX-ACCESS read-create
4892 + STATUS current
4893 + DESCRIPTION
4894 + "This variable displays the status of the en-
4895 + try. Setting it to 'invalid' has the effect of
4896 + rendering it inoperative. The internal effect
4897 + (row removal) is implementation dependent."
4898 + ::= { ospfNbrEntry 9 }
4899 +
4900 +
4901 + ospfNbmaNbrPermanence OBJECT-TYPE
4902 + SYNTAX INTEGER {
4903 + dynamic (1), -- learned through protocol
4904 + permanent (2) -- configured address
4905 + }
4906 + MAX-ACCESS read-only
4907 + STATUS current
4908 + DESCRIPTION
4909 + "This variable displays the status of the en-
4910 + try. 'dynamic' and 'permanent' refer to how
4911 + the neighbor became known."
4912 + DEFVAL { permanent }
4913 + ::= { ospfNbrEntry 10 }
4914 +
4915 +
4916 + ospfNbrHelloSuppressed OBJECT-TYPE
4917 + SYNTAX TruthValue
4918 + MAX-ACCESS read-only
4919 + STATUS current
4920 + DESCRIPTION
4921 + "Indicates whether Hellos are being suppressed
4922 + to the neighbor"
4923 + ::= { ospfNbrEntry 11 }
4924 +
4925 +
4926 +-- OSPF Virtual Neighbor Table
4927 +
4928 +-- This table describes all virtual neighbors.
4929 +-- Since Virtual Links are configured in the
4930 +-- virtual interface table, this table is read-only.
4931 +
4932 + ospfVirtNbrTable OBJECT-TYPE
4933 + SYNTAX SEQUENCE OF OspfVirtNbrEntry
4934 + MAX-ACCESS not-accessible
4935 + STATUS current
4936 + DESCRIPTION
4937 + "A table of virtual neighbor information."
4938 + REFERENCE
4939 + "OSPF Version 2, Section 15 Virtual Links"
4940 + ::= { ospf 11 }
4941 +
4942 +
4943 + ospfVirtNbrEntry OBJECT-TYPE
4944 + SYNTAX OspfVirtNbrEntry
4945 + MAX-ACCESS not-accessible
4946 + STATUS current
4947 + DESCRIPTION
4948 + "Virtual neighbor information."
4949 + INDEX { ospfVirtNbrArea, ospfVirtNbrRtrId }
4950 + ::= { ospfVirtNbrTable 1 }
4951 +
4952 +OspfVirtNbrEntry ::=
4953 + SEQUENCE {
4954 + ospfVirtNbrArea
4955 + AreaID,
4956 + ospfVirtNbrRtrId
4957 + RouterID,
4958 + ospfVirtNbrIpAddr
4959 + IpAddress,
4960 + ospfVirtNbrOptions
4961 + Integer32,
4962 + ospfVirtNbrState
4963 + INTEGER,
4964 + ospfVirtNbrEvents
4965 + Counter32,
4966 + ospfVirtNbrLsRetransQLen
4967 + Gauge32,
4968 + ospfVirtNbrHelloSuppressed
4969 + TruthValue
4970 + }
4971 +
4972 + ospfVirtNbrArea OBJECT-TYPE
4973 + SYNTAX AreaID
4974 + MAX-ACCESS read-only
4975 + STATUS current
4976 + DESCRIPTION
4977 + "The Transit Area Identifier."
4978 + ::= { ospfVirtNbrEntry 1 }
4979 +
4980 +
4981 + ospfVirtNbrRtrId OBJECT-TYPE
4982 + SYNTAX RouterID
4983 + MAX-ACCESS read-only
4984 + STATUS current
4985 + DESCRIPTION
4986 + "A 32-bit integer uniquely identifying the
4987 + neighboring router in the Autonomous System."
4988 + ::= { ospfVirtNbrEntry 2 }
4989 +
4990 +
4991 + ospfVirtNbrIpAddr OBJECT-TYPE
4992 + SYNTAX IpAddress
4993 + MAX-ACCESS read-only
4994 + STATUS current
4995 + DESCRIPTION
4996 + "The IP address this Virtual Neighbor is us-
4997 + ing."
4998 + ::= { ospfVirtNbrEntry 3 }
4999 +
5000 +
5001 + ospfVirtNbrOptions OBJECT-TYPE
5002 + SYNTAX Integer32
5003 + MAX-ACCESS read-only
5004 + STATUS current
5005 + DESCRIPTION
5006 + "A Bit Mask corresponding to the neighbor's op-
5007 + tions field.
5008 +
5009 + Bit 1, if set, indicates that the system will
5010 + operate on Type of Service metrics other than
5011 + TOS 0. If zero, the neighbor will ignore all
5012 + metrics except the TOS 0 metric.
5013 +
5014 + Bit 2, if set, indicates that the system is
5015 + Network Multicast capable; ie, that it imple-
5016 + ments OSPF Multicast Routing."
5017 + ::= { ospfVirtNbrEntry 4 }
5018 + ospfVirtNbrState OBJECT-TYPE
5019 + SYNTAX INTEGER {
5020 + down (1),
5021 + attempt (2),
5022 + init (3),
5023 + twoWay (4),
5024 + exchangeStart (5),
5025 + exchange (6),
5026 + loading (7),
5027 + full (8)
5028 + }
5029 + MAX-ACCESS read-only
5030 + STATUS current
5031 + DESCRIPTION
5032 + "The state of the Virtual Neighbor Relation-
5033 + ship."
5034 + ::= { ospfVirtNbrEntry 5 }
5035 +
5036 +
5037 + ospfVirtNbrEvents OBJECT-TYPE
5038 + SYNTAX Counter32
5039 + MAX-ACCESS read-only
5040 + STATUS current
5041 + DESCRIPTION
5042 + "The number of times this virtual link has
5043 + changed its state, or an error has occurred."
5044 + ::= { ospfVirtNbrEntry 6 }
5045 +
5046 +
5047 + ospfVirtNbrLsRetransQLen OBJECT-TYPE
5048 + SYNTAX Gauge32
5049 + MAX-ACCESS read-only
5050 + STATUS current
5051 + DESCRIPTION
5052 + "The current length of the retransmission
5053 + queue."
5054 + ::= { ospfVirtNbrEntry 7 }
5055 +
5056 +
5057 + ospfVirtNbrHelloSuppressed OBJECT-TYPE
5058 + SYNTAX TruthValue
5059 + MAX-ACCESS read-only
5060 + STATUS current
5061 + DESCRIPTION
5062 + "Indicates whether Hellos are being suppressed
5063 + to the neighbor"
5064 + ::= { ospfVirtNbrEntry 8 }
5065 +
5066 +-- OSPF Link State Database, External
5067 +
5068 +-- The Link State Database contains the Link State
5069 +-- Advertisements from throughout the areas that the
5070 +-- device is attached to.
5071 +
5072 +-- This table is identical to the OSPF LSDB Table in
5073 +-- format, but contains only External Link State
5074 +-- Advertisements. The purpose is to allow external
5075 +-- LSAs to be displayed once for the router rather
5076 +-- than once in each non-stub area.
5077 +
5078 + ospfExtLsdbTable OBJECT-TYPE
5079 + SYNTAX SEQUENCE OF OspfExtLsdbEntry
5080 + MAX-ACCESS not-accessible
5081 + STATUS current
5082 + DESCRIPTION
5083 + "The OSPF Process's Links State Database."
5084 + REFERENCE
5085 + "OSPF Version 2, Section 12 Link State Adver-
5086 + tisements"
5087 + ::= { ospf 12 }
5088 +
5089 +
5090 + ospfExtLsdbEntry OBJECT-TYPE
5091 + SYNTAX OspfExtLsdbEntry
5092 + MAX-ACCESS not-accessible
5093 + STATUS current
5094 + DESCRIPTION
5095 + "A single Link State Advertisement."
5096 + INDEX { ospfExtLsdbType, ospfExtLsdbLsid, ospfExtLsdbRouterId }
5097 + ::= { ospfExtLsdbTable 1 }
5098 +
5099 +OspfExtLsdbEntry ::=
5100 + SEQUENCE {
5101 + ospfExtLsdbType
5102 + INTEGER,
5103 + ospfExtLsdbLsid
5104 + IpAddress,
5105 + ospfExtLsdbRouterId
5106 + RouterID,
5107 + ospfExtLsdbSequence
5108 + Integer32,
5109 + ospfExtLsdbAge
5110 + Integer32,
5111 + ospfExtLsdbChecksum
5112 + Integer32,
5113 + ospfExtLsdbAdvertisement
5114 + OCTET STRING
5115 + }
5116 +
5117 + ospfExtLsdbType OBJECT-TYPE
5118 + SYNTAX INTEGER {
5119 + asExternalLink (5)
5120 + }
5121 + MAX-ACCESS read-only
5122 + STATUS current
5123 + DESCRIPTION
5124 + "The type of the link state advertisement.
5125 + Each link state type has a separate advertise-
5126 + ment format."
5127 + REFERENCE
5128 + "OSPF Version 2, Appendix A.4.1 The Link State
5129 + Advertisement header"
5130 + ::= { ospfExtLsdbEntry 1 }
5131 +
5132 +
5133 + ospfExtLsdbLsid OBJECT-TYPE
5134 + SYNTAX IpAddress
5135 + MAX-ACCESS read-only
5136 + STATUS current
5137 + DESCRIPTION
5138 + "The Link State ID is an LS Type Specific field
5139 + containing either a Router ID or an IP Address;
5140 + it identifies the piece of the routing domain
5141 + that is being described by the advertisement."
5142 + REFERENCE
5143 + "OSPF Version 2, Section 12.1.4 Link State ID"
5144 + ::= { ospfExtLsdbEntry 2 }
5145 +
5146 +
5147 + ospfExtLsdbRouterId OBJECT-TYPE
5148 + SYNTAX RouterID
5149 + MAX-ACCESS read-only
5150 + STATUS current
5151 + DESCRIPTION
5152 + "The 32 bit number that uniquely identifies the
5153 + originating router in the Autonomous System."
5154 + REFERENCE
5155 + "OSPF Version 2, Appendix C.1 Global parameters"
5156 + ::= { ospfExtLsdbEntry 3 }
5157 +
5158 +-- Note that the OSPF Sequence Number is a 32 bit signed
5159 +-- integer. It starts with the value '80000001'h,
5160 +-- or -'7FFFFFFF'h, and increments until '7FFFFFFF'h
5161 +-- Thus, a typical sequence number will be very negative.
5162 + ospfExtLsdbSequence OBJECT-TYPE
5163 + SYNTAX Integer32
5164 + MAX-ACCESS read-only
5165 + STATUS current
5166 + DESCRIPTION
5167 + "The sequence number field is a signed 32-bit
5168 + integer. It is used to detect old and dupli-
5169 + cate link state advertisements. The space of
5170 + sequence numbers is linearly ordered. The
5171 + larger the sequence number the more recent the
5172 + advertisement."
5173 + REFERENCE
5174 + "OSPF Version 2, Section 12.1.6 LS sequence
5175 + number"
5176 + ::= { ospfExtLsdbEntry 4 }
5177 +
5178 +
5179 + ospfExtLsdbAge OBJECT-TYPE
5180 + SYNTAX Integer32 -- Should be 0..MaxAge
5181 + MAX-ACCESS read-only
5182 + STATUS current
5183 + DESCRIPTION
5184 + "This field is the age of the link state adver-
5185 + tisement in seconds."
5186 + REFERENCE
5187 + "OSPF Version 2, Section 12.1.1 LS age"
5188 + ::= { ospfExtLsdbEntry 5 }
5189 +
5190 +
5191 + ospfExtLsdbChecksum OBJECT-TYPE
5192 + SYNTAX Integer32
5193 + MAX-ACCESS read-only
5194 + STATUS current
5195 + DESCRIPTION
5196 + "This field is the checksum of the complete
5197 + contents of the advertisement, excepting the
5198 + age field. The age field is excepted so that
5199 + an advertisement's age can be incremented
5200 + without updating the checksum. The checksum
5201 + used is the same that is used for ISO connec-
5202 + tionless datagrams; it is commonly referred to
5203 + as the Fletcher checksum."
5204 + REFERENCE
5205 + "OSPF Version 2, Section 12.1.7 LS checksum"
5206 + ::= { ospfExtLsdbEntry 6 }
5207 +
5208 +
5209 + ospfExtLsdbAdvertisement OBJECT-TYPE
5210 + SYNTAX OCTET STRING (SIZE(36))
5211 + MAX-ACCESS read-only
5212 + STATUS current
5213 + DESCRIPTION
5214 + "The entire Link State Advertisement, including
5215 + its header."
5216 + REFERENCE
5217 + "OSPF Version 2, Section 12 Link State Adver-
5218 + tisements"
5219 + ::= { ospfExtLsdbEntry 7 }
5220 +
5221 +
5222 +-- OSPF Use of the CIDR Route Table
5223 +
5224 +ospfRouteGroup OBJECT IDENTIFIER ::= { ospf 13 }
5225 +
5226 +-- The IP Forwarding Table defines a number of objects for use by
5227 +-- the routing protocol to externalize its information. Most of
5228 +-- the variables (ipForwardDest, ipForwardMask, ipForwardPolicy,
5229 +-- ipForwardNextHop, ipForwardIfIndex, ipForwardType,
5230 +-- ipForwardProto, ipForwardAge, and ipForwardNextHopAS) are
5231 +-- defined there.
5232 +
5233 +-- Those that leave some discretion are defined here.
5234 +
5235 +-- ipCidrRouteProto is, of course, ospf (13).
5236 +
5237 +-- ipCidrRouteAge is the time since the route was first calculated,
5238 +-- as opposed to the time since the last SPF run.
5239 +
5240 +-- ipCidrRouteInfo is an OBJECT IDENTIFIER for use by the routing
5241 +-- protocol. The following values shall be found there depending
5242 +-- on the way the route was calculated.
5243 +
5244 +ospfIntraArea OBJECT IDENTIFIER ::= { ospfRouteGroup 1 }
5245 +ospfInterArea OBJECT IDENTIFIER ::= { ospfRouteGroup 2 }
5246 +ospfExternalType1 OBJECT IDENTIFIER ::= { ospfRouteGroup 3 }
5247 +ospfExternalType2 OBJECT IDENTIFIER ::= { ospfRouteGroup 4 }
5248 +
5249 +-- ipCidrRouteMetric1 is, by definition, the primary routing
5250 +-- metric. Therefore, it should be the metric that route
5251 +-- selection is based on. For intra-area and inter-area routes,
5252 +-- it is an OSPF metric. For External Type 1 (comparable value)
5253 +-- routes, it is an OSPF metric plus the External Metric. For
5254 +-- external Type 2 (non-comparable value) routes, it is the
5255 +-- external metric.
5256 +
5257 +-- ipCidrRouteMetric2 is, by definition, a secondary routing
5258 +-- metric. Therefore, it should be the metric that breaks a tie
5259 +-- among routes having equal metric1 values and the same
5260 +-- calculation rule. For intra-area, inter-area routes, and
5261 +-- External Type 1 (comparable value) routes, it is unused. For
5262 +-- external Type 2 (non-comparable value) routes, it is the metric
5263 +-- to the AS border router.
5264 +
5265 +-- ipCidrRouteMetric3, ipCidrRouteMetric4, and ipCidrRouteMetric5 are
5266 +-- unused.
5267 +
5268 +--
5269 +-- The OSPF Area Aggregate Table
5270 +--
5271 +-- This table replaces the OSPF Area Summary Table, being an
5272 +-- extension of that for CIDR routers.
5273 +
5274 + ospfAreaAggregateTable OBJECT-TYPE
5275 + SYNTAX SEQUENCE OF OspfAreaAggregateEntry
5276 + MAX-ACCESS not-accessible
5277 + STATUS current
5278 + DESCRIPTION
5279 + "A range of IP addresses specified by an IP
5280 + address/IP network mask pair. For example,
5281 + class B address range of X.X.X.X with a network
5282 + mask of 255.255.0.0 includes all IP addresses
5283 + from X.X.0.0 to X.X.255.255. Note that if
5284 + ranges are configured such that one range sub-
5285 + sumes another range (e.g., 10.0.0.0 mask
5286 + 255.0.0.0 and 10.1.0.0 mask 255.255.0.0), the
5287 + most specific match is the preferred one."
5288 + REFERENCE
5289 + "OSPF Version 2, Appendix C.2 Area parameters"
5290 + ::= { ospf 14 }
5291 +
5292 +
5293 + ospfAreaAggregateEntry OBJECT-TYPE
5294 + SYNTAX OspfAreaAggregateEntry
5295 + MAX-ACCESS not-accessible
5296 + STATUS current
5297 + DESCRIPTION
5298 + "A range of IP addresses specified by an IP
5299 + address/IP network mask pair. For example,
5300 + class B address range of X.X.X.X with a network
5301 + mask of 255.255.0.0 includes all IP addresses
5302 + from X.X.0.0 to X.X.255.255. Note that if
5303 + ranges are range configured such that one range
5304 + subsumes another range (e.g., 10.0.0.0 mask
5305 + 255.0.0.0 and 10.1.0.0 mask 255.255.0.0), the
5306 + most specific match is the preferred one."
5307 + REFERENCE
5308 + "OSPF Version 2, Appendix C.2 Area parameters"
5309 + INDEX { ospfAreaAggregateAreaID, ospfAreaAggregateLsdbType,
5310 + ospfAreaAggregateNet, ospfAreaAggregateMask }
5311 + ::= { ospfAreaAggregateTable 1 }
5312 +
5313 +
5314 +OspfAreaAggregateEntry ::=
5315 + SEQUENCE {
5316 + ospfAreaAggregateAreaID
5317 + AreaID,
5318 + ospfAreaAggregateLsdbType
5319 + INTEGER,
5320 + ospfAreaAggregateNet
5321 + IpAddress,
5322 + ospfAreaAggregateMask
5323 + IpAddress,
5324 + ospfAreaAggregateStatus
5325 + RowStatus,
5326 + ospfAreaAggregateEffect
5327 + INTEGER
5328 + }
5329 +
5330 + ospfAreaAggregateAreaID OBJECT-TYPE
5331 + SYNTAX AreaID
5332 + MAX-ACCESS read-only
5333 + STATUS current
5334 + DESCRIPTION
5335 + "The Area the Address Aggregate is to be found
5336 + within."
5337 + REFERENCE
5338 + "OSPF Version 2, Appendix C.2 Area parameters"
5339 + ::= { ospfAreaAggregateEntry 1 }
5340 +
5341 +
5342 + ospfAreaAggregateLsdbType OBJECT-TYPE
5343 + SYNTAX INTEGER {
5344 + summaryLink (3),
5345 + nssaExternalLink (7)
5346 + }
5347 + MAX-ACCESS read-only
5348 + STATUS current
5349 + DESCRIPTION
5350 + "The type of the Address Aggregate. This field
5351 + specifies the Lsdb type that this Address Ag-
5352 + gregate applies to."
5353 + REFERENCE
5354 + "OSPF Version 2, Appendix A.4.1 The Link State
5355 + Advertisement header"
5356 + ::= { ospfAreaAggregateEntry 2 }
5357 +
5358 +
5359 + ospfAreaAggregateNet OBJECT-TYPE
5360 + SYNTAX IpAddress
5361 + MAX-ACCESS read-only
5362 + STATUS current
5363 + DESCRIPTION
5364 + "The IP Address of the Net or Subnet indicated
5365 + by the range."
5366 + REFERENCE
5367 + "OSPF Version 2, Appendix C.2 Area parameters"
5368 + ::= { ospfAreaAggregateEntry 3 }
5369 +
5370 +
5371 + ospfAreaAggregateMask OBJECT-TYPE
5372 + SYNTAX IpAddress
5373 + MAX-ACCESS read-only
5374 + STATUS current
5375 + DESCRIPTION
5376 + "The Subnet Mask that pertains to the Net or
5377 + Subnet."
5378 + REFERENCE
5379 + "OSPF Version 2, Appendix C.2 Area parameters"
5380 + ::= { ospfAreaAggregateEntry 4 }
5381 +
5382 +
5383 + ospfAreaAggregateStatus OBJECT-TYPE
5384 + SYNTAX RowStatus
5385 + MAX-ACCESS read-create
5386 + STATUS current
5387 + DESCRIPTION
5388 + "This variable displays the status of the en-
5389 + try. Setting it to 'invalid' has the effect of
5390 + rendering it inoperative. The internal effect
5391 + (row removal) is implementation dependent."
5392 + ::= { ospfAreaAggregateEntry 5 }
5393 +
5394 +
5395 + ospfAreaAggregateEffect OBJECT-TYPE
5396 + SYNTAX INTEGER {
5397 + advertiseMatching (1),
5398 + doNotAdvertiseMatching (2)
5399 + }
5400 + MAX-ACCESS read-create
5401 + STATUS current
5402 + DESCRIPTION
5403 + "Subnets subsumed by ranges either trigger the
5404 + advertisement of the indicated aggregate (ad-
5405 + vertiseMatching), or result in the subnet's not
5406 + being advertised at all outside the area."
5407 + DEFVAL { advertiseMatching }
5408 + ::= { ospfAreaAggregateEntry 6 }
5409 +
5410 +
5411 +-- conformance information
5412 +
5413 +ospfConformance OBJECT IDENTIFIER ::= { ospf 15 }
5414 +
5415 +ospfGroups OBJECT IDENTIFIER ::= { ospfConformance 1 }
5416 +ospfCompliances OBJECT IDENTIFIER ::= { ospfConformance 2 }
5417 +
5418 +-- compliance statements
5419 +
5420 + ospfCompliance MODULE-COMPLIANCE
5421 + STATUS current
5422 + DESCRIPTION
5423 + "The compliance statement "
5424 + MODULE -- this module
5425 + MANDATORY-GROUPS {
5426 + ospfBasicGroup,
5427 + ospfAreaGroup,
5428 + ospfStubAreaGroup,
5429 + ospfIfGroup,
5430 + ospfIfMetricGroup,
5431 + ospfVirtIfGroup,
5432 + ospfNbrGroup,
5433 + ospfVirtNbrGroup,
5434 + ospfAreaAggregateGroup
5435 + }
5436 + ::= { ospfCompliances 1 }
5437 +
5438 +
5439 +-- units of conformance
5440 +
5441 + ospfBasicGroup OBJECT-GROUP
5442 + OBJECTS {
5443 + ospfRouterId,
5444 + ospfAdminStat,
5445 + ospfVersionNumber,
5446 + ospfAreaBdrRtrStatus,
5447 + ospfASBdrRtrStatus,
5448 + ospfExternLsaCount,
5449 + ospfExternLsaCksumSum,
5450 + ospfTOSSupport,
5451 + ospfOriginateNewLsas,
5452 + ospfRxNewLsas,
5453 + ospfExtLsdbLimit,
5454 + ospfMulticastExtensions,
5455 + ospfExitOverflowInterval,
5456 + ospfDemandExtensions
5457 + }
5458 + STATUS current
5459 + DESCRIPTION
5460 + "These objects are required for OSPF systems."
5461 + ::= { ospfGroups 1 }
5462 +
5463 +
5464 + ospfAreaGroup OBJECT-GROUP
5465 + OBJECTS {
5466 + ospfAreaId,
5467 + ospfImportAsExtern,
5468 + ospfSpfRuns,
5469 + ospfAreaBdrRtrCount,
5470 + ospfAsBdrRtrCount,
5471 + ospfAreaLsaCount,
5472 + ospfAreaLsaCksumSum,
5473 + ospfAreaSummary,
5474 + ospfAreaStatus
5475 + }
5476 + STATUS current
5477 + DESCRIPTION
5478 + "These objects are required for OSPF systems
5479 + supporting areas."
5480 + ::= { ospfGroups 2 }
5481 +
5482 +
5483 + ospfStubAreaGroup OBJECT-GROUP
5484 + OBJECTS {
5485 + ospfStubAreaId,
5486 + ospfStubTOS,
5487 + ospfStubMetric,
5488 + ospfStubStatus,
5489 + ospfStubMetricType
5490 + }
5491 + STATUS current
5492 + DESCRIPTION
5493 + "These objects are required for OSPF systems
5494 + supporting stub areas."
5495 + ::= { ospfGroups 3 }
5496 +
5497 +
5498 + ospfLsdbGroup OBJECT-GROUP
5499 + OBJECTS {
5500 + ospfLsdbAreaId,
5501 + ospfLsdbType,
5502 + ospfLsdbLsid,
5503 + ospfLsdbRouterId,
5504 + ospfLsdbSequence,
5505 + ospfLsdbAge,
5506 + ospfLsdbChecksum,
5507 + ospfLsdbAdvertisement
5508 + }
5509 + STATUS current
5510 + DESCRIPTION
5511 + "These objects are required for OSPF systems
5512 + that display their link state database."
5513 + ::= { ospfGroups 4 }
5514 +
5515 +
5516 + ospfAreaRangeGroup OBJECT-GROUP
5517 + OBJECTS {
5518 + ospfAreaRangeAreaId,
5519 + ospfAreaRangeNet,
5520 + ospfAreaRangeMask,
5521 + ospfAreaRangeStatus,
5522 + ospfAreaRangeEffect
5523 + }
5524 + STATUS obsolete
5525 + DESCRIPTION
5526 + "These objects are required for non-CIDR OSPF
5527 + systems that support multiple areas."
5528 + ::= { ospfGroups 5 }
5529 +
5530 +
5531 + ospfHostGroup OBJECT-GROUP
5532 + OBJECTS {
5533 + ospfHostIpAddress,
5534 + ospfHostTOS,
5535 + ospfHostMetric,
5536 + ospfHostStatus,
5537 + ospfHostAreaID
5538 + }
5539 + STATUS current
5540 + DESCRIPTION
5541 + "These objects are required for OSPF systems
5542 + that support attached hosts."
5543 + ::= { ospfGroups 6 }
5544 +
5545 +
5546 + ospfIfGroup OBJECT-GROUP
5547 + OBJECTS {
5548 + ospfIfIpAddress,
5549 + ospfAddressLessIf,
5550 + ospfIfAreaId,
5551 + ospfIfType,
5552 + ospfIfAdminStat,
5553 + ospfIfRtrPriority,
5554 + ospfIfTransitDelay,
5555 + ospfIfRetransInterval,
5556 + ospfIfHelloInterval,
5557 + ospfIfRtrDeadInterval,
5558 + ospfIfPollInterval,
5559 + ospfIfState,
5560 + ospfIfDesignatedRouter,
5561 + ospfIfBackupDesignatedRouter,
5562 + ospfIfEvents,
5563 + ospfIfAuthType,
5564 + ospfIfAuthKey,
5565 + ospfIfStatus,
5566 + ospfIfMulticastForwarding,
5567 + ospfIfDemand
5568 + }
5569 + STATUS current
5570 + DESCRIPTION
5571 + "These objects are required for OSPF systems."
5572 + ::= { ospfGroups 7 }
5573 +
5574 +
5575 + ospfIfMetricGroup OBJECT-GROUP
5576 + OBJECTS {
5577 + ospfIfMetricIpAddress,
5578 + ospfIfMetricAddressLessIf,
5579 + ospfIfMetricTOS,
5580 + ospfIfMetricValue,
5581 + ospfIfMetricStatus
5582 + }
5583 + STATUS current
5584 + DESCRIPTION
5585 + "These objects are required for OSPF systems."
5586 + ::= { ospfGroups 8 }
5587 +
5588 +
5589 + ospfVirtIfGroup OBJECT-GROUP
5590 + OBJECTS {
5591 + ospfVirtIfAreaId,
5592 + ospfVirtIfNeighbor,
5593 + ospfVirtIfTransitDelay,
5594 + ospfVirtIfRetransInterval,
5595 + ospfVirtIfHelloInterval,
5596 + ospfVirtIfRtrDeadInterval,
5597 + ospfVirtIfState,
5598 + ospfVirtIfEvents,
5599 + ospfVirtIfAuthType,
5600 + ospfVirtIfAuthKey,
5601 + ospfVirtIfStatus
5602 + }
5603 + STATUS current
5604 + DESCRIPTION
5605 + "These objects are required for OSPF systems."
5606 + ::= { ospfGroups 9 }
5607 +
5608 +
5609 + ospfNbrGroup OBJECT-GROUP
5610 + OBJECTS {
5611 + ospfNbrIpAddr,
5612 + ospfNbrAddressLessIndex,
5613 + ospfNbrRtrId,
5614 + ospfNbrOptions,
5615 + ospfNbrPriority,
5616 + ospfNbrState,
5617 + ospfNbrEvents,
5618 + ospfNbrLsRetransQLen,
5619 + ospfNbmaNbrStatus,
5620 + ospfNbmaNbrPermanence,
5621 + ospfNbrHelloSuppressed
5622 + }
5623 + STATUS current
5624 + DESCRIPTION
5625 + "These objects are required for OSPF systems."
5626 + ::= { ospfGroups 10 }
5627 +
5628 +
5629 + ospfVirtNbrGroup OBJECT-GROUP
5630 + OBJECTS {
5631 + ospfVirtNbrArea,
5632 + ospfVirtNbrRtrId,
5633 + ospfVirtNbrIpAddr,
5634 + ospfVirtNbrOptions,
5635 + ospfVirtNbrState,
5636 + ospfVirtNbrEvents,
5637 + ospfVirtNbrLsRetransQLen,
5638 + ospfVirtNbrHelloSuppressed
5639 + }
5640 + STATUS current
5641 + DESCRIPTION
5642 + "These objects are required for OSPF systems."
5643 + ::= { ospfGroups 11 }
5644 +
5645 +
5646 + ospfExtLsdbGroup OBJECT-GROUP
5647 + OBJECTS {
5648 + ospfExtLsdbType,
5649 + ospfExtLsdbLsid,
5650 + ospfExtLsdbRouterId,
5651 + ospfExtLsdbSequence,
5652 + ospfExtLsdbAge,
5653 + ospfExtLsdbChecksum,
5654 + ospfExtLsdbAdvertisement
5655 + }
5656 + STATUS current
5657 + DESCRIPTION
5658 + "These objects are required for OSPF systems
5659 + that display their link state database."
5660 + ::= { ospfGroups 12 }
5661 +
5662 +
5663 + ospfAreaAggregateGroup OBJECT-GROUP
5664 + OBJECTS {
5665 + ospfAreaAggregateAreaID,
5666 + ospfAreaAggregateLsdbType,
5667 + ospfAreaAggregateNet,
5668 + ospfAreaAggregateMask,
5669 + ospfAreaAggregateStatus,
5670 + ospfAreaAggregateEffect
5671 + }
5672 + STATUS current
5673 + DESCRIPTION
5674 + "These objects are required for OSPF systems."
5675 + ::= { ospfGroups 13 }
5676 +
5677 +END
5678 diff -ruN net-snmp-5.1.2-orig/mibs/OSPF-TRAP-MIB.txt net-snmp-5.1.2-5/mibs/OSPF-TRAP-MIB.txt
5679 --- net-snmp-5.1.2-orig/mibs/OSPF-TRAP-MIB.txt 1970-01-01 01:00:00.000000000 +0100
5680 +++ net-snmp-5.1.2-5/mibs/OSPF-TRAP-MIB.txt 2005-03-13 16:17:21.000000000 +0100
5681 @@ -0,0 +1,443 @@
5682 +OSPF-TRAP-MIB DEFINITIONS ::= BEGIN
5683 +
5684 + IMPORTS
5685 + MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, IpAddress
5686 + FROM SNMPv2-SMI
5687 + MODULE-COMPLIANCE, OBJECT-GROUP
5688 + FROM SNMPv2-CONF
5689 + ospfRouterId, ospfIfIpAddress, ospfAddressLessIf, ospfIfState,
5690 + ospfVirtIfAreaId, ospfVirtIfNeighbor, ospfVirtIfState,
5691 + ospfNbrIpAddr, ospfNbrAddressLessIndex, ospfNbrRtrId,
5692 + ospfNbrState, ospfVirtNbrArea, ospfVirtNbrRtrId, ospfVirtNbrState,
5693 + ospfLsdbType, ospfLsdbLsid, ospfLsdbRouterId, ospfLsdbAreaId,
5694 + ospfExtLsdbLimit, ospf
5695 + FROM OSPF-MIB;
5696 +
5697 + ospfTrap MODULE-IDENTITY
5698 + LAST-UPDATED "9501201225Z" -- Fri Jan 20 12:25:50 PST 1995
5699 + ORGANIZATION "IETF OSPF Working Group"
5700 + CONTACT-INFO
5701 + " Fred Baker
5702 + Postal: Cisco Systems
5703 + 519 Lado Drive
5704 + Santa Barbara, California 93111
5705 + Tel: +1 805 681 0115
5706 + E-Mail: fred@cisco.com
5707 +
5708 + Rob Coltun
5709 + Postal: RainbowBridge Communications
5710 + Tel: (301) 340-9416
5711 + E-Mail: rcoltun@rainbow-bridge.com"
5712 + DESCRIPTION
5713 + "The MIB module to describe traps for the OSPF
5714 + Version 2 Protocol."
5715 + ::= { ospf 16 }
5716 +
5717 +-- Trap Support Objects
5718 +
5719 +-- The following are support objects for the OSPF traps.
5720 +
5721 +ospfTrapControl OBJECT IDENTIFIER ::= { ospfTrap 1 }
5722 +ospfTraps OBJECT IDENTIFIER ::= { ospfTrap 2 }
5723 +
5724 + ospfSetTrap OBJECT-TYPE
5725 + SYNTAX OCTET STRING (SIZE(4))
5726 + MAX-ACCESS read-write
5727 + STATUS current
5728 + DESCRIPTION
5729 + "A four-octet string serving as a bit map for
5730 + the trap events defined by the OSPF traps. This
5731 + object is used to enable and disable specific
5732 + OSPF traps where a 1 in the bit field
5733 + represents enabled. The right-most bit (least
5734 + significant) represents trap 0."
5735 + ::= { ospfTrapControl 1 }
5736 +
5737 +
5738 + ospfConfigErrorType OBJECT-TYPE
5739 + SYNTAX INTEGER {
5740 + badVersion (1),
5741 + areaMismatch (2),
5742 + unknownNbmaNbr (3), -- Router is Dr eligible
5743 + unknownVirtualNbr (4),
5744 + authTypeMismatch(5),
5745 + authFailure (6),
5746 + netMaskMismatch (7),
5747 + helloIntervalMismatch (8),
5748 + deadIntervalMismatch (9),
5749 + optionMismatch (10) }
5750 + MAX-ACCESS read-only
5751 + STATUS current
5752 + DESCRIPTION
5753 + "Potential types of configuration conflicts.
5754 + Used by the ospfConfigError and ospfConfigVir-
5755 + tError traps."
5756 + ::= { ospfTrapControl 2 }
5757 +
5758 +
5759 + ospfPacketType OBJECT-TYPE
5760 + SYNTAX INTEGER {
5761 + hello (1),
5762 + dbDescript (2),
5763 + lsReq (3),
5764 + lsUpdate (4),
5765 + lsAck (5) }
5766 + MAX-ACCESS read-only
5767 + STATUS current
5768 + DESCRIPTION
5769 + "OSPF packet types."
5770 + ::= { ospfTrapControl 3 }
5771 +
5772 +
5773 + ospfPacketSrc OBJECT-TYPE
5774 + SYNTAX IpAddress
5775 + MAX-ACCESS read-only
5776 + STATUS current
5777 + DESCRIPTION
5778 + "The IP address of an inbound packet that can-
5779 + not be identified by a neighbor instance."
5780 + ::= { ospfTrapControl 4 }
5781 +
5782 +
5783 +-- Traps
5784 +
5785 +
5786 + ospfIfStateChange NOTIFICATION-TYPE
5787 + OBJECTS {
5788 + ospfRouterId, -- The originator of the trap
5789 + ospfIfIpAddress,
5790 + ospfAddressLessIf,
5791 + ospfIfState -- The new state
5792 + }
5793 + STATUS current
5794 + DESCRIPTION
5795 + "An ospfIfStateChange trap signifies that there
5796 + has been a change in the state of a non-virtual
5797 + OSPF interface. This trap should be generated
5798 + when the interface state regresses (e.g., goes
5799 + from Dr to Down) or progresses to a terminal
5800 + state (i.e., Point-to-Point, DR Other, Dr, or
5801 + Backup)."
5802 + ::= { ospfTraps 16 }
5803 +
5804 +
5805 + ospfVirtIfStateChange NOTIFICATION-TYPE
5806 + OBJECTS {
5807 + ospfRouterId, -- The originator of the trap
5808 + ospfVirtIfAreaId,
5809 + ospfVirtIfNeighbor,
5810 + ospfVirtIfState -- The new state
5811 + }
5812 + STATUS current
5813 + DESCRIPTION
5814 + "An ospfIfStateChange trap signifies that there
5815 + has been a change in the state of an OSPF vir-
5816 + tual interface.
5817 + This trap should be generated when the inter-
5818 + face state regresses (e.g., goes from Point-
5819 + to-Point to Down) or progresses to a terminal
5820 + state (i.e., Point-to-Point)."
5821 + ::= { ospfTraps 1 }
5822 +
5823 +
5824 + ospfNbrStateChange NOTIFICATION-TYPE
5825 + OBJECTS {
5826 + ospfRouterId, -- The originator of the trap
5827 + ospfNbrIpAddr,
5828 + ospfNbrAddressLessIndex,
5829 + ospfNbrRtrId,
5830 + ospfNbrState -- The new state
5831 + }
5832 + STATUS current
5833 + DESCRIPTION
5834 + "An ospfNbrStateChange trap signifies that
5835 + there has been a change in the state of a non-
5836 + virtual OSPF neighbor. This trap should be
5837 + generated when the neighbor state regresses
5838 + (e.g., goes from Attempt or Full to 1-Way or
5839 + Down) or progresses to a terminal state (e.g.,
5840 + 2-Way or Full). When an neighbor transitions
5841 + from or to Full on non-broadcast multi-access
5842 + and broadcast networks, the trap should be gen-
5843 + erated by the designated router. A designated
5844 + router transitioning to Down will be noted by
5845 + ospfIfStateChange."
5846 + ::= { ospfTraps 2 }
5847 +
5848 +
5849 + ospfVirtNbrStateChange NOTIFICATION-TYPE
5850 + OBJECTS {
5851 + ospfRouterId, -- The originator of the trap
5852 + ospfVirtNbrArea,
5853 + ospfVirtNbrRtrId,
5854 + ospfVirtNbrState -- The new state
5855 + }
5856 + STATUS current
5857 + DESCRIPTION
5858 + "An ospfIfStateChange trap signifies that there
5859 + has been a change in the state of an OSPF vir-
5860 + tual neighbor. This trap should be generated
5861 + when the neighbor state regresses (e.g., goes
5862 + from Attempt or Full to 1-Way or Down) or
5863 + progresses to a terminal state (e.g., Full)."
5864 + ::= { ospfTraps 3 }
5865 + ospfIfConfigError NOTIFICATION-TYPE
5866 + OBJECTS {
5867 + ospfRouterId, -- The originator of the trap
5868 + ospfIfIpAddress,
5869 + ospfAddressLessIf,
5870 + ospfPacketSrc, -- The source IP address
5871 + ospfConfigErrorType, -- Type of error
5872 + ospfPacketType
5873 + }
5874 + STATUS current
5875 + DESCRIPTION
5876 + "An ospfIfConfigError trap signifies that a
5877 + packet has been received on a non-virtual in-
5878 + terface from a router whose configuration
5879 + parameters conflict with this router's confi-
5880 + guration parameters. Note that the event op-
5881 + tionMismatch should cause a trap only if it
5882 + prevents an adjacency from forming."
5883 + ::= { ospfTraps 4 }
5884 +
5885 +
5886 + ospfVirtIfConfigError NOTIFICATION-TYPE
5887 + OBJECTS {
5888 + ospfRouterId, -- The originator of the trap
5889 + ospfVirtIfAreaId,
5890 + ospfVirtIfNeighbor,
5891 + ospfConfigErrorType, -- Type of error
5892 + ospfPacketType
5893 + }
5894 + STATUS current
5895 + DESCRIPTION
5896 + "An ospfConfigError trap signifies that a pack-
5897 + et has been received on a virtual interface
5898 + from a router whose configuration parameters
5899 + conflict with this router's configuration
5900 + parameters. Note that the event optionMismatch
5901 + should cause a trap only if it prevents an ad-
5902 + jacency from forming."
5903 + ::= { ospfTraps 5 }
5904 +
5905 +
5906 + ospfIfAuthFailure NOTIFICATION-TYPE
5907 + OBJECTS {
5908 + ospfRouterId, -- The originator of the trap
5909 + ospfIfIpAddress,
5910 + ospfAddressLessIf,
5911 + ospfPacketSrc, -- The source IP address
5912 + ospfConfigErrorType, -- authTypeMismatch or
5913 + -- authFailure
5914 + ospfPacketType
5915 + }
5916 + STATUS current
5917 + DESCRIPTION
5918 + "An ospfIfAuthFailure trap signifies that a
5919 + packet has been received on a non-virtual in-
5920 + terface from a router whose authentication key
5921 + or authentication type conflicts with this
5922 + router's authentication key or authentication
5923 + type."
5924 + ::= { ospfTraps 6 }
5925 +
5926 +
5927 + ospfVirtIfAuthFailure NOTIFICATION-TYPE
5928 + OBJECTS {
5929 + ospfRouterId, -- The originator of the trap
5930 + ospfVirtIfAreaId,
5931 + ospfVirtIfNeighbor,
5932 + ospfConfigErrorType, -- authTypeMismatch or
5933 + -- authFailure
5934 + ospfPacketType
5935 + }
5936 + STATUS current
5937 + DESCRIPTION
5938 + "An ospfVirtIfAuthFailure trap signifies that a
5939 + packet has been received on a virtual interface
5940 + from a router whose authentication key or au-
5941 + thentication type conflicts with this router's
5942 + authentication key or authentication type."
5943 + ::= { ospfTraps 7 }
5944 +
5945 +
5946 + ospfIfRxBadPacket NOTIFICATION-TYPE
5947 + OBJECTS {
5948 + ospfRouterId, -- The originator of the trap
5949 + ospfIfIpAddress,
5950 + ospfAddressLessIf,
5951 + ospfPacketSrc, -- The source IP address
5952 + ospfPacketType
5953 + }
5954 + STATUS current
5955 + DESCRIPTION
5956 + "An ospfIfRxBadPacket trap signifies that an
5957 + OSPF packet has been received on a non-virtual
5958 + interface that cannot be parsed."
5959 + ::= { ospfTraps 8 }
5960 +
5961 + ospfVirtIfRxBadPacket NOTIFICATION-TYPE
5962 + OBJECTS {
5963 + ospfRouterId, -- The originator of the trap
5964 + ospfVirtIfAreaId,
5965 + ospfVirtIfNeighbor,
5966 + ospfPacketType
5967 + }
5968 + STATUS current
5969 + DESCRIPTION
5970 + "An ospfRxBadPacket trap signifies that an OSPF
5971 + packet has been received on a virtual interface
5972 + that cannot be parsed."
5973 + ::= { ospfTraps 9 }
5974 +
5975 +
5976 + ospfTxRetransmit NOTIFICATION-TYPE
5977 + OBJECTS {
5978 + ospfRouterId, -- The originator of the trap
5979 + ospfIfIpAddress,
5980 + ospfAddressLessIf,
5981 + ospfNbrRtrId, -- Destination
5982 + ospfPacketType,
5983 + ospfLsdbType,
5984 + ospfLsdbLsid,
5985 + ospfLsdbRouterId
5986 + }
5987 + STATUS current
5988 + DESCRIPTION
5989 + "An ospfTxRetransmit trap signifies than an
5990 + OSPF packet has been retransmitted on a non-
5991 + virtual interface. All packets that may be re-
5992 + transmitted are associated with an LSDB entry.
5993 + The LS type, LS ID, and Router ID are used to
5994 + identify the LSDB entry."
5995 + ::= { ospfTraps 10 }
5996 +
5997 +
5998 + ospfVirtIfTxRetransmit NOTIFICATION-TYPE
5999 + OBJECTS {
6000 + ospfRouterId, -- The originator of the trap
6001 + ospfVirtIfAreaId,
6002 + ospfVirtIfNeighbor,
6003 + ospfPacketType,
6004 + ospfLsdbType,
6005 + ospfLsdbLsid,
6006 + ospfLsdbRouterId
6007 + }
6008 + STATUS current
6009 + DESCRIPTION
6010 + "An ospfTxRetransmit trap signifies than an
6011 + OSPF packet has been retransmitted on a virtual
6012 + interface. All packets that may be retransmit-
6013 + ted are associated with an LSDB entry. The LS
6014 + type, LS ID, and Router ID are used to identify
6015 + the LSDB entry."
6016 + ::= { ospfTraps 11 }
6017 +
6018 +
6019 + ospfOriginateLsa NOTIFICATION-TYPE
6020 + OBJECTS {
6021 + ospfRouterId, -- The originator of the trap
6022 + ospfLsdbAreaId, -- 0.0.0.0 for AS Externals
6023 + ospfLsdbType,
6024 + ospfLsdbLsid,
6025 + ospfLsdbRouterId
6026 + }
6027 + STATUS current
6028 + DESCRIPTION
6029 + "An ospfOriginateLsa trap signifies that a new
6030 + LSA has been originated by this router. This
6031 + trap should not be invoked for simple refreshes
6032 + of LSAs (which happesn every 30 minutes), but
6033 + instead will only be invoked when an LSA is
6034 + (re)originated due to a topology change. Addi-
6035 + tionally, this trap does not include LSAs that
6036 + are being flushed because they have reached
6037 + MaxAge."
6038 + ::= { ospfTraps 12 }
6039 +
6040 +
6041 + ospfMaxAgeLsa NOTIFICATION-TYPE
6042 + OBJECTS {
6043 + ospfRouterId, -- The originator of the trap
6044 + ospfLsdbAreaId, -- 0.0.0.0 for AS Externals
6045 + ospfLsdbType,
6046 + ospfLsdbLsid,
6047 + ospfLsdbRouterId
6048 + }
6049 + STATUS current
6050 + DESCRIPTION
6051 + "An ospfMaxAgeLsa trap signifies that one of
6052 + the LSA in the router's link-state database has
6053 + aged to MaxAge."
6054 + ::= { ospfTraps 13 }
6055 +
6056 +
6057 + ospfLsdbOverflow NOTIFICATION-TYPE
6058 + OBJECTS {
6059 + ospfRouterId, -- The originator of the trap
6060 + ospfExtLsdbLimit
6061 + }
6062 + STATUS current
6063 + DESCRIPTION
6064 + "An ospfLsdbOverflow trap signifies that the
6065 + number of LSAs in the router's link-state data-
6066 + base has exceeded ospfExtLsdbLimit."
6067 + ::= { ospfTraps 14 }
6068 +
6069 +
6070 + ospfLsdbApproachingOverflow NOTIFICATION-TYPE
6071 + OBJECTS {
6072 + ospfRouterId, -- The originator of the trap
6073 + ospfExtLsdbLimit
6074 + }
6075 + STATUS current
6076 + DESCRIPTION
6077 + "An ospfLsdbApproachingOverflow trap signifies
6078 + that the number of LSAs in the router's link-
6079 + state database has exceeded ninety percent of
6080 + ospfExtLsdbLimit."
6081 + ::= { ospfTraps 15 }
6082 +
6083 +
6084 +-- conformance information
6085 +
6086 +ospfTrapConformance OBJECT IDENTIFIER ::= { ospfTrap 3 }
6087 +
6088 +ospfTrapGroups OBJECT IDENTIFIER ::= { ospfTrapConformance 1 }
6089 +ospfTrapCompliances OBJECT IDENTIFIER ::= { ospfTrapConformance 2 }
6090 +
6091 +-- compliance statements
6092 +
6093 + ospfTrapCompliance MODULE-COMPLIANCE
6094 + STATUS current
6095 + DESCRIPTION
6096 + "The compliance statement "
6097 + MODULE -- this module
6098 + MANDATORY-GROUPS { ospfTrapControlGroup }
6099 +
6100 +
6101 + GROUP ospfTrapControlGroup
6102 + DESCRIPTION
6103 + "This group is optional but recommended for all
6104 + OSPF systems"
6105 + ::= { ospfTrapCompliances 1 }
6106 +
6107 +
6108 +-- units of conformance
6109 +
6110 + ospfTrapControlGroup OBJECT-GROUP
6111 + OBJECTS {
6112 + ospfSetTrap,
6113 + ospfConfigErrorType,
6114 + ospfPacketType,
6115 + ospfPacketSrc
6116 + }
6117 + STATUS current
6118 + DESCRIPTION
6119 + "These objects are required to control traps
6120 + from OSPF systems."
6121 + ::= { ospfTrapGroups 1 }
6122 +
6123 +
6124 +END
6125 diff -ruN net-snmp-5.1.2-orig/mibs/RIPv2-MIB.txt net-snmp-5.1.2-5/mibs/RIPv2-MIB.txt
6126 --- net-snmp-5.1.2-orig/mibs/RIPv2-MIB.txt 1970-01-01 01:00:00.000000000 +0100
6127 +++ net-snmp-5.1.2-5/mibs/RIPv2-MIB.txt 2005-03-13 16:17:21.000000000 +0100
6128 @@ -0,0 +1,530 @@
6129 + RIPv2-MIB DEFINITIONS ::= BEGIN
6130 +
6131 + IMPORTS
6132 + MODULE-IDENTITY, OBJECT-TYPE, Counter32,
6133 + TimeTicks, IpAddress FROM SNMPv2-SMI
6134 + TEXTUAL-CONVENTION, RowStatus FROM SNMPv2-TC
6135 + MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
6136 + mib-2 FROM RFC1213-MIB;
6137 +
6138 + -- This MIB module uses the extended OBJECT-TYPE macro as
6139 + -- defined in [9].
6140 +
6141 + rip2 MODULE-IDENTITY
6142 + LAST-UPDATED "9407272253Z" -- Wed Jul 27 22:53:04 PDT 1994
6143 + ORGANIZATION "IETF RIP-II Working Group"
6144 + CONTACT-INFO
6145 + " Fred Baker
6146 + Postal: Cisco Systems
6147 + 519 Lado Drive
6148 + Santa Barbara, California 93111
6149 + Tel: +1 805 681 0115
6150 + E-Mail: fbaker@cisco.com
6151 +
6152 + Postal: Gary Malkin
6153 + Xylogics, Inc.
6154 + 53 Third Avenue
6155 + Burlington, MA 01803
6156 +
6157 + Phone: (617) 272-8140
6158 + EMail: gmalkin@Xylogics.COM"
6159 + DESCRIPTION
6160 + "The MIB module to describe the RIP2 Version 2 Protocol"
6161 + ::= { mib-2 23 }
6162 +
6163 + -- RIP-2 Management Information Base
6164 +
6165 + -- the RouteTag type represents the contents of the
6166 + -- Route Domain field in the packet header or route entry.
6167 + -- The use of the Route Domain is deprecated.
6168 +
6169 + RouteTag ::= TEXTUAL-CONVENTION
6170 + STATUS current
6171 + DESCRIPTION
6172 + "the RouteTag type represents the contents of the Route Domain
6173 + field in the packet header or route entry"
6174 + SYNTAX OCTET STRING (SIZE (2))
6175 +
6176 +--4.1 Global Counters
6177 +
6178 +-- The RIP-2 Globals Group.
6179 +-- Implementation of this group is mandatory for systems
6180 +-- which implement RIP-2.
6181 +
6182 +-- These counters are intended to facilitate debugging quickly
6183 +-- changing routes or failing neighbors
6184 +
6185 +rip2Globals OBJECT IDENTIFIER ::= { rip2 1 }
6186 +
6187 + rip2GlobalRouteChanges OBJECT-TYPE
6188 + SYNTAX Counter32
6189 + MAX-ACCESS read-only
6190 + STATUS current
6191 + DESCRIPTION
6192 + "The number of route changes made to the IP Route
6193 + Database by RIP. This does not include the refresh
6194 + of a route's age."
6195 + ::= { rip2Globals 1 }
6196 +
6197 + rip2GlobalQueries OBJECT-TYPE
6198 + SYNTAX Counter32
6199 + MAX-ACCESS read-only
6200 + STATUS current
6201 + DESCRIPTION
6202 + "The number of responses sent to RIP queries
6203 + from other systems."
6204 + ::= { rip2Globals 2 }
6205 +
6206 +--4.2 RIP Interface Tables
6207 +
6208 +-- RIP Interfaces Groups
6209 +-- Implementation of these Groups is mandatory for systems
6210 +-- which implement RIP-2.
6211 +
6212 +-- The RIP Interface Status Table.
6213 +
6214 + rip2IfStatTable OBJECT-TYPE
6215 + SYNTAX SEQUENCE OF Rip2IfStatEntry
6216 + MAX-ACCESS not-accessible
6217 + STATUS current
6218 + DESCRIPTION
6219 + "A list of subnets which require separate
6220 + status monitoring in RIP."
6221 + ::= { rip2 2 }
6222 +
6223 + rip2IfStatEntry OBJECT-TYPE
6224 + SYNTAX Rip2IfStatEntry
6225 + MAX-ACCESS not-accessible
6226 + STATUS current
6227 + DESCRIPTION
6228 + "A Single Routing Domain in a single Subnet."
6229 + INDEX { rip2IfStatAddress }
6230 + ::= { rip2IfStatTable 1 }
6231 +
6232 + Rip2IfStatEntry ::=
6233 + SEQUENCE {
6234 + rip2IfStatAddress
6235 + IpAddress,
6236 + rip2IfStatRcvBadPackets
6237 + Counter32,
6238 + rip2IfStatRcvBadRoutes
6239 + Counter32,
6240 + rip2IfStatSentUpdates
6241 + Counter32,
6242 + rip2IfStatStatus
6243 + RowStatus
6244 + }
6245 +
6246 + rip2IfStatAddress OBJECT-TYPE
6247 + SYNTAX IpAddress
6248 + MAX-ACCESS read-only
6249 + STATUS current
6250 + DESCRIPTION
6251 + "The IP Address of this system on the indicated
6252 + subnet. For unnumbered interfaces, the value 0.0.0.N,
6253 + where the least significant 24 bits (N) is the ifIndex
6254 + for the IP Interface in network byte order."
6255 + ::= { rip2IfStatEntry 1 }
6256 +
6257 + rip2IfStatRcvBadPackets OBJECT-TYPE
6258 + SYNTAX Counter32
6259 + MAX-ACCESS read-only
6260 + STATUS current
6261 + DESCRIPTION
6262 + "The number of RIP response packets received by
6263 + the RIP process which were subsequently discarded
6264 + for any reason (e.g. a version 0 packet, or an
6265 + unknown command type)."
6266 + ::= { rip2IfStatEntry 2 }
6267 +
6268 + rip2IfStatRcvBadRoutes OBJECT-TYPE
6269 + SYNTAX Counter32
6270 + MAX-ACCESS read-only
6271 + STATUS current
6272 + DESCRIPTION
6273 + "The number of routes, in valid RIP packets,
6274 + which were ignored for any reason (e.g. unknown
6275 + address family, or invalid metric)."
6276 + ::= { rip2IfStatEntry 3 }
6277 +
6278 + rip2IfStatSentUpdates OBJECT-TYPE
6279 + SYNTAX Counter32
6280 + MAX-ACCESS read-only
6281 + STATUS current
6282 + DESCRIPTION
6283 + "The number of triggered RIP updates actually
6284 + sent on this interface. This explicitly does
6285 + NOT include full updates sent containing new
6286 + information."
6287 + ::= { rip2IfStatEntry 4 }
6288 +
6289 + rip2IfStatStatus OBJECT-TYPE
6290 + SYNTAX RowStatus
6291 + MAX-ACCESS read-create
6292 + STATUS current
6293 + DESCRIPTION
6294 + "Writing invalid has the effect of deleting
6295 + this interface."
6296 + ::= { rip2IfStatEntry 5 }
6297 +
6298 +-- The RIP Interface Configuration Table.
6299 +
6300 + rip2IfConfTable OBJECT-TYPE
6301 + SYNTAX SEQUENCE OF Rip2IfConfEntry
6302 + MAX-ACCESS not-accessible
6303 + STATUS current
6304 + DESCRIPTION
6305 + "A list of subnets which require separate
6306 + configuration in RIP."
6307 + ::= { rip2 3 }
6308 +
6309 + rip2IfConfEntry OBJECT-TYPE
6310 + SYNTAX Rip2IfConfEntry
6311 + MAX-ACCESS not-accessible
6312 + STATUS current
6313 + DESCRIPTION
6314 + "A Single Routing Domain in a single Subnet."
6315 + INDEX { rip2IfConfAddress }
6316 + ::= { rip2IfConfTable 1 }
6317 +
6318 + Rip2IfConfEntry ::=
6319 + SEQUENCE {
6320 + rip2IfConfAddress
6321 + IpAddress,
6322 + rip2IfConfDomain
6323 + RouteTag,
6324 + rip2IfConfAuthType
6325 + INTEGER,
6326 + rip2IfConfAuthKey
6327 + OCTET STRING (SIZE(0..16)),
6328 + rip2IfConfSend
6329 + INTEGER,
6330 + rip2IfConfReceive
6331 + INTEGER,
6332 + rip2IfConfDefaultMetric
6333 + INTEGER,
6334 + rip2IfConfStatus
6335 + RowStatus,
6336 + rip2IfConfSrcAddress
6337 + IpAddress
6338 + }
6339 +
6340 + rip2IfConfAddress OBJECT-TYPE
6341 + SYNTAX IpAddress
6342 + MAX-ACCESS read-only
6343 + STATUS current
6344 + DESCRIPTION
6345 + "The IP Address of this system on the indicated
6346 + subnet. For unnumbered interfaces, the value 0.0.0.N,
6347 + where the least significant 24 bits (N) is the ifIndex
6348 + for the IP Interface in network byte order."
6349 + ::= { rip2IfConfEntry 1 }
6350 +
6351 + rip2IfConfDomain OBJECT-TYPE
6352 + SYNTAX RouteTag
6353 + MAX-ACCESS read-create
6354 + STATUS obsolete
6355 + DESCRIPTION
6356 + "Value inserted into the Routing Domain field
6357 + of all RIP packets sent on this interface."
6358 + DEFVAL { '0000'h }
6359 + ::= { rip2IfConfEntry 2 }
6360 +
6361 + rip2IfConfAuthType OBJECT-TYPE
6362 + SYNTAX INTEGER {
6363 + noAuthentication (1),
6364 + simplePassword (2),
6365 + md5 (3)
6366 + }
6367 + MAX-ACCESS read-create
6368 + STATUS current
6369 + DESCRIPTION
6370 + "The type of Authentication used on this
6371 + interface."
6372 + DEFVAL { noAuthentication }
6373 + ::= { rip2IfConfEntry 3 }
6374 +
6375 + rip2IfConfAuthKey OBJECT-TYPE
6376 + SYNTAX OCTET STRING (SIZE(0..16))
6377 + MAX-ACCESS read-create
6378 + STATUS current
6379 + DESCRIPTION
6380 + "The value to be used as the Authentication Key
6381 + whenever the corresponding instance of
6382 + rip2IfConfAuthType has a value other than
6383 + noAuthentication. A modification of the corresponding
6384 + instance of rip2IfConfAuthType does not modify
6385 + the rip2IfConfAuthKey value. If a string shorter
6386 + than 16 octets is supplied, it will be left-
6387 + justified and padded to 16 octets, on the right,
6388 + with nulls (0x00).
6389 +
6390 + Reading this object always results in an OCTET
6391 + STRING of length zero; authentication may not
6392 + be bypassed by reading the MIB object."
6393 + DEFVAL { ''h }
6394 + ::= { rip2IfConfEntry 4 }
6395 +
6396 + rip2IfConfSend OBJECT-TYPE
6397 + SYNTAX INTEGER {
6398 + doNotSend (1),
6399 + ripVersion1 (2),
6400 + rip1Compatible (3),
6401 + ripVersion2 (4),
6402 + ripV1Demand (5),
6403 + ripV2Demand (6)
6404 + }
6405 + MAX-ACCESS read-create
6406 + STATUS current
6407 + DESCRIPTION
6408 + "What the router sends on this interface.
6409 + ripVersion1 implies sending RIP updates compliant
6410 + with RFC 1058. rip1Compatible implies
6411 + broadcasting RIP-2 updates using RFC 1058 route
6412 + subsumption rules. ripVersion2 implies
6413 + multicasting RIP-2 updates. ripV1Demand indicates
6414 + the use of Demand RIP on a WAN interface under RIP
6415 + Version 1 rules. ripV2Demand indicates the use of
6416 + Demand RIP on a WAN interface under Version 2 rules."
6417 + DEFVAL { rip1Compatible }
6418 + ::= { rip2IfConfEntry 5 }
6419 +
6420 + rip2IfConfReceive OBJECT-TYPE
6421 + SYNTAX INTEGER {
6422 + rip1 (1),
6423 + rip2 (2),
6424 + rip1OrRip2 (3),
6425 + doNotRecieve (4)
6426 + }
6427 + MAX-ACCESS read-create
6428 + STATUS current
6429 + DESCRIPTION
6430 + "This indicates which version of RIP updates
6431 + are to be accepted. Note that rip2 and
6432 + rip1OrRip2 implies reception of multicast
6433 + packets."
6434 + DEFVAL { rip1OrRip2 }
6435 + ::= { rip2IfConfEntry 6 }
6436 +
6437 + rip2IfConfDefaultMetric OBJECT-TYPE
6438 + SYNTAX INTEGER ( 0..15 )
6439 + MAX-ACCESS read-create
6440 + STATUS current
6441 + DESCRIPTION
6442 + "This variable indicates the metric that is to
6443 + be used for the default route entry in RIP updates
6444 + originated on this interface. A value of zero
6445 + indicates that no default route should be
6446 + originated; in this case, a default route via
6447 + another router may be propagated."
6448 + ::= { rip2IfConfEntry 7 }
6449 +
6450 + rip2IfConfStatus OBJECT-TYPE
6451 + SYNTAX RowStatus
6452 + MAX-ACCESS read-create
6453 + STATUS current
6454 + DESCRIPTION
6455 + "Writing invalid has the effect of deleting
6456 + this interface."
6457 + ::= { rip2IfConfEntry 8 }
6458 +
6459 + rip2IfConfSrcAddress OBJECT-TYPE
6460 + SYNTAX IpAddress
6461 + MAX-ACCESS read-create
6462 + STATUS current
6463 + DESCRIPTION
6464 + "The IP Address this system will use as a source
6465 + address on this interface. If it is a numbered
6466 + interface, this MUST be the same value as
6467 + rip2IfConfAddress. On unnumbered interfaces,
6468 + it must be the value of rip2IfConfAddress for
6469 + some interface on the system."
6470 + ::= { rip2IfConfEntry 9 }
6471 +
6472 +--4.3 Peer Table
6473 +
6474 +-- Peer Table
6475 +
6476 +-- The RIP Peer Group
6477 +-- Implementation of this Group is Optional
6478 +
6479 +-- This group provides information about active peer
6480 +-- relationships intended to assist in debugging. An
6481 +-- active peer is a router from which a valid RIP
6482 +-- updated has been heard in the last 180 seconds.
6483 +
6484 + rip2PeerTable OBJECT-TYPE
6485 + SYNTAX SEQUENCE OF Rip2PeerEntry
6486 + MAX-ACCESS not-accessible
6487 + STATUS current
6488 + DESCRIPTION
6489 + "A list of RIP Peers."
6490 + ::= { rip2 4 }
6491 +
6492 + rip2PeerEntry OBJECT-TYPE
6493 + SYNTAX Rip2PeerEntry
6494 + MAX-ACCESS not-accessible
6495 + STATUS current
6496 + DESCRIPTION
6497 + "Information regarding a single routing peer."
6498 + INDEX { rip2PeerAddress, rip2PeerDomain }
6499 + ::= { rip2PeerTable 1 }
6500 +
6501 + Rip2PeerEntry ::=
6502 + SEQUENCE {
6503 + rip2PeerAddress
6504 + IpAddress,
6505 + rip2PeerDomain
6506 + RouteTag,
6507 + rip2PeerLastUpdate
6508 + TimeTicks,
6509 + rip2PeerVersion
6510 + INTEGER,
6511 + rip2PeerRcvBadPackets
6512 + Counter32,
6513 + rip2PeerRcvBadRoutes
6514 + Counter32
6515 + }
6516 +
6517 + rip2PeerAddress OBJECT-TYPE
6518 + SYNTAX IpAddress
6519 + MAX-ACCESS read-only
6520 + STATUS current
6521 + DESCRIPTION
6522 + "The IP Address that the peer is using as its source
6523 + address. Note that on an unnumbered link, this may
6524 + not be a member of any subnet on the system."
6525 + ::= { rip2PeerEntry 1 }
6526 +
6527 + rip2PeerDomain OBJECT-TYPE
6528 + SYNTAX RouteTag
6529 + MAX-ACCESS read-only
6530 + STATUS current
6531 + DESCRIPTION
6532 + "The value in the Routing Domain field in RIP
6533 + packets received from the peer. As domain suuport
6534 + is deprecated, this must be zero."
6535 + ::= { rip2PeerEntry 2 }
6536 +
6537 + rip2PeerLastUpdate OBJECT-TYPE
6538 + SYNTAX TimeTicks
6539 + MAX-ACCESS read-only
6540 + STATUS current
6541 + DESCRIPTION
6542 + "The value of sysUpTime when the most recent
6543 + RIP update was received from this system."
6544 + ::= { rip2PeerEntry 3 }
6545 +
6546 + rip2PeerVersion OBJECT-TYPE
6547 + SYNTAX INTEGER ( 0..255 )
6548 + MAX-ACCESS read-only
6549 + STATUS current
6550 + DESCRIPTION
6551 + "The RIP version number in the header of the
6552 + last RIP packet received."
6553 + ::= { rip2PeerEntry 4 }
6554 +
6555 + rip2PeerRcvBadPackets OBJECT-TYPE
6556 + SYNTAX Counter32
6557 + MAX-ACCESS read-only
6558 + STATUS current
6559 + DESCRIPTION
6560 + "The number of RIP response packets from this
6561 + peer discarded as invalid."
6562 + ::= { rip2PeerEntry 5 }
6563 +
6564 +
6565 + rip2PeerRcvBadRoutes OBJECT-TYPE
6566 + SYNTAX Counter32
6567 + MAX-ACCESS read-only
6568 + STATUS current
6569 + DESCRIPTION
6570 + "The number of routes from this peer that were
6571 + ignored because the entry format was invalid."
6572 + ::= { rip2PeerEntry 6 }
6573 +
6574 +-- conformance information
6575 +
6576 +rip2Conformance OBJECT IDENTIFIER ::= { rip2 5 }
6577 +
6578 +rip2Groups OBJECT IDENTIFIER ::= { rip2Conformance 1 }
6579 +rip2Compliances OBJECT IDENTIFIER ::= { rip2Conformance 2 }
6580 +
6581 +-- compliance statements
6582 +rip2Compliance MODULE-COMPLIANCE
6583 + STATUS current
6584 + DESCRIPTION
6585 + "The compliance statement "
6586 + MODULE -- this module
6587 + MANDATORY-GROUPS {
6588 + rip2GlobalGroup,
6589 + rip2IfStatGroup,
6590 + rip2IfConfGroup,
6591 + rip2PeerGroup
6592 + }
6593 + GROUP rip2GlobalGroup
6594 + DESCRIPTION
6595 + "This group defines global controls for RIP-II systems."
6596 + GROUP rip2IfStatGroup
6597 + DESCRIPTION
6598 + "This group defines interface statistics for RIP-II systems."
6599 + GROUP rip2IfConfGroup
6600 + DESCRIPTION
6601 + "This group defines interface configuration for RIP-II systems."
6602 + GROUP rip2PeerGroup
6603 + DESCRIPTION
6604 + "This group defines peer information for RIP-II systems."
6605 + ::= { rip2Compliances 1 }
6606 +
6607 +-- units of conformance
6608 +
6609 +rip2GlobalGroup OBJECT-GROUP
6610 + OBJECTS {
6611 + rip2GlobalRouteChanges,
6612 + rip2GlobalQueries
6613 + }
6614 + STATUS current
6615 + DESCRIPTION
6616 + "This group defines global controls for RIP-II systems."
6617 + ::= { rip2Groups 1 }
6618 +rip2IfStatGroup OBJECT-GROUP
6619 + OBJECTS {
6620 + rip2IfStatAddress,
6621 + rip2IfStatRcvBadPackets,
6622 + rip2IfStatRcvBadRoutes,
6623 + rip2IfStatSentUpdates,
6624 + rip2IfStatStatus
6625 + }
6626 + STATUS current
6627 + DESCRIPTION
6628 + "This group defines interface statistics for RIP-II systems."
6629 + ::= { rip2Groups 2 }
6630 +rip2IfConfGroup OBJECT-GROUP
6631 + OBJECTS {
6632 + rip2IfConfAddress,
6633 + rip2IfConfAuthType,
6634 + rip2IfConfAuthKey,
6635 + rip2IfConfSend,
6636 + rip2IfConfReceive,
6637 + rip2IfConfDefaultMetric,
6638 + rip2IfConfStatus,
6639 + rip2IfConfSrcAddress
6640 + }
6641 + STATUS current
6642 + DESCRIPTION
6643 + "This group defines interface configuration for RIP-II systems."
6644 + ::= { rip2Groups 3 }
6645 +rip2PeerGroup OBJECT-GROUP
6646 + OBJECTS {
6647 + rip2PeerAddress,
6648 + rip2PeerDomain,
6649 + rip2PeerLastUpdate,
6650 + rip2PeerVersion,
6651 + rip2PeerRcvBadPackets,
6652 + rip2PeerRcvBadRoutes
6653 + }
6654 + STATUS current
6655 + DESCRIPTION
6656 + "This group defines peer information for RIP-II systems."
6657 + ::= { rip2Groups 4 }
6658 +END
6659 diff -ruN net-snmp-5.1.2-orig/mibs/SOURCE-ROUTING-MIB.txt net-snmp-5.1.2-5/mibs/SOURCE-ROUTING-MIB.txt
6660 --- net-snmp-5.1.2-orig/mibs/SOURCE-ROUTING-MIB.txt 1970-01-01 01:00:00.000000000 +0100
6661 +++ net-snmp-5.1.2-5/mibs/SOURCE-ROUTING-MIB.txt 2005-03-13 16:17:21.000000000 +0100
6662 @@ -0,0 +1,452 @@
6663 +SOURCE-ROUTING-MIB DEFINITIONS ::= BEGIN
6664 +
6665 +IMPORTS
6666 + Counter, Gauge
6667 + FROM RFC1155-SMI
6668 + dot1dBridge, dot1dSr
6669 + FROM BRIDGE-MIB
6670 + OBJECT-TYPE
6671 + FROM RFC-1212;
6672 +
6673 +-- groups in the SR MIB
6674 +
6675 +-- dot1dSr is imported from the Bridge MIB
6676 +
6677 +dot1dPortPair OBJECT IDENTIFIER ::= { dot1dBridge 10 }
6678 +
6679 +-- the dot1dSr group
6680 +
6681 +-- this group is implemented by those bridges that
6682 +-- support the source route bridging mode, including Source
6683 +-- Routing and SRT bridges.
6684 +
6685 +dot1dSrPortTable OBJECT-TYPE
6686 + SYNTAX SEQUENCE OF Dot1dSrPortEntry
6687 + ACCESS not-accessible
6688 + STATUS mandatory
6689 + DESCRIPTION
6690 + "A table that contains information about every
6691 + port that is associated with this source route
6692 + bridge."
6693 + ::= { dot1dSr 1 }
6694 +
6695 +dot1dSrPortEntry OBJECT-TYPE
6696 + SYNTAX Dot1dSrPortEntry
6697 + ACCESS not-accessible
6698 + STATUS mandatory
6699 + DESCRIPTION
6700 + "A list of information for each port of a source
6701 + route bridge."
6702 + INDEX { dot1dSrPort }
6703 +
6704 + ::= { dot1dSrPortTable 1 }
6705 +
6706 +Dot1dSrPortEntry ::=
6707 + SEQUENCE {
6708 + dot1dSrPort
6709 + INTEGER,
6710 + dot1dSrPortHopCount
6711 + INTEGER,
6712 + dot1dSrPortLocalSegment
6713 + INTEGER,
6714 + dot1dSrPortBridgeNum
6715 + INTEGER,
6716 + dot1dSrPortTargetSegment
6717 + INTEGER,
6718 + dot1dSrPortLargestFrame
6719 + INTEGER,
6720 + dot1dSrPortSTESpanMode
6721 + INTEGER,
6722 + dot1dSrPortSpecInFrames
6723 + Counter,
6724 + dot1dSrPortSpecOutFrames
6725 + Counter,
6726 + dot1dSrPortApeInFrames
6727 + Counter,
6728 + dot1dSrPortApeOutFrames
6729 + Counter,
6730 + dot1dSrPortSteInFrames
6731 + Counter,
6732 + dot1dSrPortSteOutFrames
6733 + Counter,
6734 + dot1dSrPortSegmentMismatchDiscards
6735 + Counter,
6736 + dot1dSrPortDuplicateSegmentDiscards
6737 + Counter,
6738 + dot1dSrPortHopCountExceededDiscards
6739 + Counter,
6740 + dot1dSrPortDupLanIdOrTreeErrors
6741 + Counter,
6742 + dot1dSrPortLanIdMismatches
6743 + Counter
6744 + }
6745 +
6746 +dot1dSrPort OBJECT-TYPE
6747 + SYNTAX INTEGER (1..65535)
6748 + ACCESS read-only
6749 + STATUS mandatory
6750 + DESCRIPTION
6751 + "The port number of the port for which this entry
6752 +
6753 + contains Source Route management information."
6754 + ::= { dot1dSrPortEntry 1 }
6755 +
6756 +dot1dSrPortHopCount OBJECT-TYPE
6757 + SYNTAX INTEGER
6758 + ACCESS read-write
6759 + STATUS mandatory
6760 + DESCRIPTION
6761 + "The maximum number of routing descriptors allowed
6762 + in an All Paths or Spanning Tree Explorer frames."
6763 + ::= { dot1dSrPortEntry 2 }
6764 +
6765 +dot1dSrPortLocalSegment OBJECT-TYPE
6766 + SYNTAX INTEGER
6767 + ACCESS read-write
6768 + STATUS mandatory
6769 + DESCRIPTION
6770 + "The segment number that uniquely identifies the
6771 + segment to which this port is connected. Current
6772 + source routing protocols limit this value to the
6773 + range: 0 through 4095. (The value 0 is used by
6774 + some management applications for special test
6775 + cases.) A value of 65535 signifies that no segment
6776 + number is assigned to this port."
6777 + ::= { dot1dSrPortEntry 3 }
6778 +
6779 +dot1dSrPortBridgeNum OBJECT-TYPE
6780 + SYNTAX INTEGER
6781 + ACCESS read-write
6782 + STATUS mandatory
6783 + DESCRIPTION
6784 + "A bridge number uniquely identifies a bridge when
6785 + more than one bridge is used to span the same two
6786 + segments. Current source routing protocols limit
6787 + this value to the range: 0 through 15. A value of
6788 + 65535 signifies that no bridge number is assigned
6789 + to this bridge."
6790 + ::= { dot1dSrPortEntry 4 }
6791 +
6792 +dot1dSrPortTargetSegment OBJECT-TYPE
6793 + SYNTAX INTEGER
6794 + ACCESS read-write
6795 + STATUS mandatory
6796 + DESCRIPTION
6797 + "The segment number that corresponds to the target
6798 + segment this port is considered to be connected to
6799 + by the bridge. Current source routing protocols
6800 + limit this value to the range: 0 through 4095.
6801 +
6802 + (The value 0 is used by some management
6803 + applications for special test cases.) A value of
6804 + 65535 signifies that no target segment is assigned
6805 + to this port."
6806 + ::= { dot1dSrPortEntry 5 }
6807 +
6808 +-- It would be nice if we could use ifMtu as the size of the
6809 +-- largest frame, but we can't because ifMtu is defined to be
6810 +-- the size that the (inter-)network layer can use which can
6811 +-- differ from the MAC layer (especially if several layers of
6812 +-- encapsulation are used).
6813 +
6814 +dot1dSrPortLargestFrame OBJECT-TYPE
6815 + SYNTAX INTEGER
6816 + ACCESS read-write
6817 + STATUS mandatory
6818 + DESCRIPTION
6819 + "The maximum size of the INFO field (LLC and
6820 + above) that this port can send/receive. It does
6821 + not include any MAC level (framing) octets. The
6822 + value of this object is used by this bridge to
6823 + determine whether a modification of the
6824 + LargestFrame (LF, see [14]) field of the Routing
6825 + Control field of the Routing Information Field is
6826 + necessary.
6827 +
6828 + 64 valid values are defined by the IEEE 802.5M SRT
6829 + Addendum: 516, 635, 754, 873, 993, 1112, 1231,
6830 + 1350, 1470, 1542, 1615, 1688, 1761, 1833, 1906,
6831 + 1979, 2052, 2345, 2638, 2932, 3225, 3518, 3812,
6832 + 4105, 4399, 4865, 5331, 5798, 6264, 6730, 7197,
6833 + 7663, 8130, 8539, 8949, 9358, 9768, 10178, 10587,
6834 + 10997, 11407, 12199, 12992, 13785, 14578, 15370,
6835 + 16163, 16956, 17749, 20730, 23711, 26693, 29674,
6836 + 32655, 35637, 38618, 41600, 44591, 47583, 50575,
6837 + 53567, 56559, 59551, and 65535.
6838 +
6839 + An illegal value will not be accepted by the
6840 + bridge."
6841 + ::= { dot1dSrPortEntry 6 }
6842 +
6843 +dot1dSrPortSTESpanMode OBJECT-TYPE
6844 + SYNTAX INTEGER {
6845 + auto-span(1),
6846 + disabled(2),
6847 + forced(3)
6848 + }
6849 + ACCESS read-write
6850 + STATUS mandatory
6851 + DESCRIPTION
6852 + "Determines how this port behaves when presented
6853 + with a Spanning Tree Explorer frame. The value
6854 + 'disabled(2)' indicates that the port will not
6855 + accept or send Spanning Tree Explorer packets; any
6856 + STE packets received will be silently discarded.
6857 + The value 'forced(3)' indicates the port will
6858 + always accept and propagate Spanning Tree Explorer
6859 + frames. This allows a manually configured
6860 + Spanning Tree for this class of packet to be
6861 + configured. Note that unlike transparent
6862 + bridging, this is not catastrophic to the network
6863 + if there are loops. The value 'auto-span(1)' can
6864 + only be returned by a bridge that both implements
6865 + the Spanning Tree Protocol and has use of the
6866 + protocol enabled on this port. The behavior of the
6867 + port for Spanning Tree Explorer frames is
6868 + determined by the state of dot1dStpPortState. If
6869 + the port is in the 'forwarding' state, the frame
6870 + will be accepted or propagated. Otherwise, it
6871 + will be silently discarded."
6872 + ::= { dot1dSrPortEntry 7 }
6873 +
6874 +dot1dSrPortSpecInFrames OBJECT-TYPE
6875 + SYNTAX Counter
6876 + ACCESS read-only
6877 + STATUS mandatory
6878 + DESCRIPTION
6879 + "The number of Specifically Routed frames, also
6880 + referred to as Source Routed Frames, that have
6881 + been received from this port's segment."
6882 + ::= { dot1dSrPortEntry 8 }
6883 +
6884 +dot1dSrPortSpecOutFrames OBJECT-TYPE
6885 + SYNTAX Counter
6886 + ACCESS read-only
6887 + STATUS mandatory
6888 + DESCRIPTION
6889 + "The number of Specifically Routed frames, also
6890 + referred to as Source Routed Frames, that this
6891 + port has transmitted on its segment."
6892 + ::= { dot1dSrPortEntry 9 }
6893 +
6894 +dot1dSrPortApeInFrames OBJECT-TYPE
6895 + SYNTAX Counter
6896 + ACCESS read-only
6897 + STATUS mandatory
6898 + DESCRIPTION
6899 + "The number of All Paths Explorer frames, also
6900 + referred to as All Routes Explorer frames, that
6901 + have been received by this port from its segment."
6902 + ::= { dot1dSrPortEntry 10 }
6903 +
6904 +dot1dSrPortApeOutFrames OBJECT-TYPE
6905 + SYNTAX Counter
6906 + ACCESS read-only
6907 + STATUS mandatory
6908 + DESCRIPTION
6909 + "The number of all Paths Explorer Frames, also
6910 + referred to as All Routes Explorer frames, that
6911 + have been transmitted by this port on its
6912 + segment."
6913 + ::= { dot1dSrPortEntry 11 }
6914 +
6915 +dot1dSrPortSteInFrames OBJECT-TYPE
6916 + SYNTAX Counter
6917 + ACCESS read-only
6918 + STATUS mandatory
6919 + DESCRIPTION
6920 + "The number of spanning tree explorer frames that
6921 + have been received by this port from its segment."
6922 + ::= { dot1dSrPortEntry 12 }
6923 +
6924 +dot1dSrPortSteOutFrames OBJECT-TYPE
6925 + SYNTAX Counter
6926 + ACCESS read-only
6927 + STATUS mandatory
6928 + DESCRIPTION
6929 + "The number of spanning tree explorer frames that
6930 + have been transmitted by this port on its
6931 + segment."
6932 + ::= { dot1dSrPortEntry 13 }
6933 +
6934 +dot1dSrPortSegmentMismatchDiscards OBJECT-TYPE
6935 + SYNTAX Counter
6936 + ACCESS read-only
6937 + STATUS mandatory
6938 + DESCRIPTION
6939 + "The number of explorer frames that have been
6940 + discarded by this port because the routing
6941 + descriptor field contained an invalid adjacent
6942 + segment value."
6943 + ::= { dot1dSrPortEntry 14 }
6944 +
6945 +dot1dSrPortDuplicateSegmentDiscards OBJECT-TYPE
6946 + SYNTAX Counter
6947 + ACCESS read-only
6948 + STATUS mandatory
6949 + DESCRIPTION
6950 + "The number of frames that have been discarded by
6951 + this port because the routing descriptor field
6952 + contained a duplicate segment identifier."
6953 + ::= { dot1dSrPortEntry 15 }
6954 +
6955 +dot1dSrPortHopCountExceededDiscards OBJECT-TYPE
6956 + SYNTAX Counter
6957 + ACCESS read-only
6958 + STATUS mandatory
6959 + DESCRIPTION
6960 + "The number of explorer frames that have been
6961 + discarded by this port because the Routing
6962 + Information Field has exceeded the maximum route
6963 + descriptor length."
6964 + ::= { dot1dSrPortEntry 16 }
6965 +
6966 +dot1dSrPortDupLanIdOrTreeErrors OBJECT-TYPE
6967 + SYNTAX Counter
6968 + ACCESS read-only
6969 + STATUS mandatory
6970 + DESCRIPTION
6971 + "The number of duplicate LAN IDs or Tree errors.
6972 + This helps in detection of problems in networks
6973 + containing older IBM Source Routing Bridges."
6974 + ::= { dot1dSrPortEntry 17 }
6975 +
6976 +dot1dSrPortLanIdMismatches OBJECT-TYPE
6977 + SYNTAX Counter
6978 + ACCESS read-only
6979 + STATUS mandatory
6980 + DESCRIPTION
6981 + "The number of ARE and STE frames that were
6982 + discarded because the last LAN ID in the routing
6983 + information field did not equal the LAN-in ID.
6984 + This error can occur in implementations which do
6985 + only a LAN-in ID and Bridge Number check instead
6986 + of a LAN-in ID, Bridge Number, and LAN-out ID
6987 + check before they forward broadcast frames."
6988 + ::= { dot1dSrPortEntry 18 }
6989 +
6990 +-- scalar object in dot1dSr
6991 +
6992 +dot1dSrBridgeLfMode OBJECT-TYPE
6993 + SYNTAX INTEGER {
6994 + mode3(1),
6995 + mode6(2)
6996 + }
6997 + ACCESS read-write
6998 + STATUS mandatory
6999 + DESCRIPTION
7000 + "Indicates whether the bridge operates using older
7001 + 3 bit length negotiation fields or the newer 6 bit
7002 + length field in its RIF."
7003 + ::= { dot1dSr 2 }
7004 +
7005 +-- The Port-Pair Database
7006 +
7007 +-- Implementation of this group is optional.
7008 +
7009 +-- This group is implemented by those bridges that support
7010 +-- the direct multiport model of the source route bridging
7011 +-- mode as defined in the IEEE 802.5 SRT Addendum to
7012 +-- 802.1d.
7013 +
7014 +-- Bridges implementing this group may report 65535 for
7015 +-- dot1dSrPortBridgeNumber and dot1dSrPortTargetSegment,
7016 +-- indicating that those objects are not applicable.
7017 +
7018 +dot1dPortPairTableSize OBJECT-TYPE
7019 + SYNTAX Gauge
7020 + ACCESS read-only
7021 + STATUS mandatory
7022 + DESCRIPTION
7023 + "The total number of entries in the Bridge Port
7024 + Pair Database."
7025 + ::= { dot1dPortPair 1 }
7026 +
7027 +-- the Bridge Port-Pair table
7028 +
7029 +-- this table represents port pairs within a bridge forming
7030 +-- a unique bridge path, as defined in the IEEE 802.5M SRT
7031 +-- Addendum.
7032 +
7033 +dot1dPortPairTable OBJECT-TYPE
7034 + SYNTAX SEQUENCE OF Dot1dPortPairEntry
7035 + ACCESS not-accessible
7036 + STATUS mandatory
7037 + DESCRIPTION
7038 + "A table that contains information about every
7039 +
7040 + port pair database entity associated with this
7041 + source routing bridge."
7042 + ::= { dot1dPortPair 2 }
7043 +
7044 +dot1dPortPairEntry OBJECT-TYPE
7045 + SYNTAX Dot1dPortPairEntry
7046 + ACCESS not-accessible
7047 + STATUS mandatory
7048 + DESCRIPTION
7049 + "A list of information for each port pair entity
7050 + of a bridge."
7051 + INDEX { dot1dPortPairLowPort, dot1dPortPairHighPort }
7052 + ::= { dot1dPortPairTable 1 }
7053 +
7054 +Dot1dPortPairEntry ::=
7055 + SEQUENCE {
7056 + dot1dPortPairLowPort
7057 + INTEGER,
7058 + dot1dPortPairHighPort
7059 + INTEGER,
7060 + dot1dPortPairBridgeNum
7061 + INTEGER,
7062 + dot1dPortPairBridgeState
7063 + INTEGER
7064 + }
7065 +
7066 +dot1dPortPairLowPort OBJECT-TYPE
7067 + SYNTAX INTEGER (1..65535)
7068 + ACCESS read-write
7069 + STATUS mandatory
7070 + DESCRIPTION
7071 + "The port number of the lower numbered port for
7072 + which this entry contains port pair database
7073 + information."
7074 + ::= { dot1dPortPairEntry 1 }
7075 +
7076 +dot1dPortPairHighPort OBJECT-TYPE
7077 + SYNTAX INTEGER (1..65535)
7078 + ACCESS read-write
7079 + STATUS mandatory
7080 + DESCRIPTION
7081 + "The port number of the higher numbered port for
7082 + which this entry contains port pair database
7083 + information."
7084 + ::= { dot1dPortPairEntry 2 }
7085 +
7086 +dot1dPortPairBridgeNum OBJECT-TYPE
7087 + SYNTAX INTEGER
7088 +
7089 + ACCESS read-write
7090 + STATUS mandatory
7091 + DESCRIPTION
7092 + "A bridge number that uniquely identifies the path
7093 + provided by this source routing bridge between the
7094 + segments connected to dot1dPortPairLowPort and
7095 + dot1dPortPairHighPort. The purpose of bridge
7096 + number is to disambiguate between multiple paths
7097 + connecting the same two LANs."
7098 + ::= { dot1dPortPairEntry 3 }
7099 +
7100 +dot1dPortPairBridgeState OBJECT-TYPE
7101 + SYNTAX INTEGER {
7102 + enabled(1),
7103 + disabled(2),
7104 + invalid(3)
7105 + }
7106 + ACCESS read-write
7107 + STATUS mandatory
7108 + DESCRIPTION
7109 + "The state of dot1dPortPairBridgeNum. Writing
7110 + 'invalid(3)' to this object removes the
7111 + corresponding entry."
7112 + ::= { dot1dPortPairEntry 4 }
7113 +
7114 +END
7115 diff -ruN net-snmp-5.1.2-orig/net-snmp-config.in net-snmp-5.1.2-5/net-snmp-config.in
7116 --- net-snmp-5.1.2-orig/net-snmp-config.in 2004-06-17 15:39:28.000000000 +0200
7117 +++ net-snmp-5.1.2-5/net-snmp-config.in 2005-03-13 16:17:21.000000000 +0100
7118 @@ -113,13 +113,13 @@
7119 #################################################### client lib
7120 --libs)
7121 # use this one == --netsnmp-libs + --external-libs
7122 - echo $NSC_LDFLAGS $NSC_LIBDIR -lnetsnmp $NSC_LIBS
7123 + echo $NSC_LDFLAGS $NSC_LIBDIR -lnetsnmp $NSC_LIBS @WRAPLIBS@
7124 ;;
7125 --netsnmp-libs)
7126 echo $NSC_LIBDIR -lnetsnmp
7127 ;;
7128 --external-libs)
7129 - echo $NSC_LDFLAGS $NSC_LIBS
7130 + echo $NSC_LDFLAGS $NSC_LIBS @WRAPLIBS@
7131 ;;
7132 #################################################### agent lib
7133 --base-agent-libs)
7134 @@ -130,13 +130,13 @@
7135 ;;
7136 --agent-libs)
7137 # use this one == --netsnmp-agent-libs + --external-libs
7138 - echo $NSC_LDFLAGS $NSC_LIBDIR $NSC_BASE_AGENT_LIBS $NSC_AGENTLIBS
7139 + echo $NSC_LDFLAGS $NSC_LIBDIR $NSC_BASE_AGENT_LIBS $NSC_AGENTLIBS @WRAPLIBS@
7140 ;;
7141 --netsnmp-agent-libs)
7142 echo $NSC_LIBDIR $NSC_BASE_AGENT_LIBS
7143 ;;
7144 --external-agent-libs)
7145 - echo $NSC_LDFLAGS $NSC_AGENTLIBS
7146 + echo $NSC_LDFLAGS $NSC_AGENTLIBS @WRAPLIBS@
7147 ;;
7148 ####################################################
7149 --version)
7150 @@ -409,7 +409,7 @@
7151 echo "Ack. Can't create $tmpfile."
7152 exit 1
7153 fi
7154 - cmd="@CC@ $cflags @CFLAGS@ @DEVFLAGS@ -I. -I@includedir@ -o $outname $tmpfile $cfiles $NSC_LDFLAGS -L$NSC_EXEC_PREFIX/lib -lnetsnmpagent -lnetsnmphelpers -lnetsnmpmibs -lnetsnmp $NSC_AGENTLIBS $ldflags"
7155 + cmd="@CC@ $cflags @CFLAGS@ @DEVFLAGS@ -I. -I@includedir@ -o $outname $tmpfile $cfiles $NSC_LDFLAGS -L$NSC_EXEC_PREFIX/lib -lnetsnmpagent -lnetsnmphelpers -lnetsnmpmibs -lnetsnmp $NSC_AGENTLIBS @WRAPLIBS@ $ldflags"
7156 echo "running: $cmd"
7157 `$cmd`
7158 if test "x$norm" != "x1" ; then
7159 diff -ruN net-snmp-5.1.2-orig/perl/agent/netsnmp_request_infoPtr.pm net-snmp-5.1.2-5/perl/agent/netsnmp_request_infoPtr.pm
7160 --- net-snmp-5.1.2-orig/perl/agent/netsnmp_request_infoPtr.pm 2002-09-19 22:38:24.000000000 +0200
7161 +++ net-snmp-5.1.2-5/perl/agent/netsnmp_request_infoPtr.pm 2005-03-13 16:17:21.000000000 +0100
7162 @@ -4,6 +4,7 @@
7163
7164 1;
7165 __END__
7166 +
7167 =head1 NAME
7168
7169 NetSNMP::agent::netsnmp_request_infoPtr - Perl extension for request information
7170 diff -ruN net-snmp-5.1.2-orig/snmplib/Makefile.in net-snmp-5.1.2-5/snmplib/Makefile.in
7171 --- net-snmp-5.1.2-orig/snmplib/Makefile.in 2004-03-04 14:41:19.000000000 +0100
7172 +++ net-snmp-5.1.2-5/snmplib/Makefile.in 2005-03-13 16:17:21.000000000 +0100
7173 @@ -178,11 +178,11 @@
7174
7175 # how to build the libraries.
7176 libnetsnmp.$(LIB_EXTENSION)$(LIB_VERSION): ${TOBJS}
7177 - $(LIB_LD_CMD) libnetsnmp.$(LIB_EXTENSION)$(LIB_VERSION) ${TOBJS}
7178 + $(LIB_LD_CMD) libnetsnmp.$(LIB_EXTENSION)$(LIB_VERSION) ${TOBJS} @CRYPTOLIBS@
7179 $(RANLIB) libnetsnmp.$(LIB_EXTENSION)$(LIB_VERSION)
7180
7181 libsnmp.$(LIB_EXTENSION)$(LIB_VERSION): ${TOBJS}
7182 - $(LIB_LD_CMD) libsnmp.$(LIB_EXTENSION)$(LIB_VERSION) ${TOBJS}
7183 + $(LIB_LD_CMD) libsnmp.$(LIB_EXTENSION)$(LIB_VERSION) ${TOBJS} @CRYPTOLIBS@
7184 $(RANLIB) libsnmp.$(LIB_EXTENSION)$(LIB_VERSION)
7185
7186 #
7187 diff -ruN net-snmp-5.1.2-orig/snmplib/snmpUDPDomain.c net-snmp-5.1.2-5/snmplib/snmpUDPDomain.c
7188 --- net-snmp-5.1.2-orig/snmplib/snmpUDPDomain.c 2004-07-07 14:21:32.000000000 +0200
7189 +++ net-snmp-5.1.2-5/snmplib/snmpUDPDomain.c 2005-03-13 16:17:21.000000000 +0100
7190 @@ -233,18 +233,6 @@
7191 netsnmp_transport_free(t);
7192 return NULL;
7193 }
7194 -#ifdef SO_BSDCOMPAT
7195 - /*
7196 - * Patch for Linux. Without this, UDP packets that fail get an ICMP
7197 - * response. Linux turns the failed ICMP response into an error message
7198 - * and return value, unlike all other OS's.
7199 - */
7200 - {
7201 - int one = 1;
7202 - setsockopt(t->sock, SOL_SOCKET, SO_BSDCOMPAT, (void *) &one,
7203 - sizeof(one));
7204 - }
7205 -#endif /*SO_BSDCOMPAT */
7206 /*
7207 * SO_REUSEADDR will allow multiple apps to open the same port at
7208 * the same time. Only the last one to open the socket will get
7209 diff -ruN net-snmp-5.1.2-orig/snmplib/snmpUDPIPv6Domain.c net-snmp-5.1.2-5/snmplib/snmpUDPIPv6Domain.c
7210 --- net-snmp-5.1.2-orig/snmplib/snmpUDPIPv6Domain.c 2004-07-22 19:45:00.000000000 +0200
7211 +++ net-snmp-5.1.2-5/snmplib/snmpUDPIPv6Domain.c 2005-03-13 16:17:21.000000000 +0100
7212 @@ -249,17 +249,6 @@
7213 netsnmp_transport_free(t);
7214 return NULL;
7215 }
7216 -#ifdef SO_BSDCOMPAT
7217 - /*
7218 - * Patch for Linux. Without this, UDP packets that fail get an ICMP
7219 - * response. Linux turns the failed ICMP response into an error message
7220 - * and return value, unlike all other OS's.
7221 - */
7222 - {
7223 - int one = 1;
7224 - setsockopt(t->sock, SOL_SOCKET, SO_BSDCOMPAT, &one, sizeof(one));
7225 - }
7226 -#endif /*SO_BSDCOMPAT */
7227
7228 /*
7229 * Try to set the send and receive buffers to a reasonably large value, so
7230 diff -ruN net-snmp-5.1.2-orig/snmplib/snmp_logging.c net-snmp-5.1.2-5/snmplib/snmp_logging.c
7231 --- net-snmp-5.1.2-orig/snmplib/snmp_logging.c 2004-03-31 03:06:08.000000000 +0200
7232 +++ net-snmp-5.1.2-5/snmplib/snmp_logging.c 2005-03-13 16:17:21.000000000 +0100
7233 @@ -860,13 +860,14 @@
7234 } else {
7235 strcpy(sbuf, "");
7236 }
7237 - newline = string[strlen(string) - 1] == '\n'; /* XXX - Eh ? */
7238
7239 if (logh->imagic)
7240 printf( "%s%s", sbuf, string);
7241 else
7242 fprintf(stderr, "%s%s", sbuf, string);
7243
7244 + newline = string[strlen(string) - 1] == '\n'; /* XXX - Eh ? */
7245 +
7246 return 1;
7247 }
7248
7249 diff -ruN net-snmp-5.1.2-orig/snmplib/winservice.mc net-snmp-5.1.2-5/snmplib/winservice.mc
7250 --- net-snmp-5.1.2-orig/snmplib/winservice.mc 2002-04-20 09:30:21.000000000 +0200
7251 +++ net-snmp-5.1.2-5/snmplib/winservice.mc 2005-03-13 16:17:21.000000000 +0100
7252 @@ -1,11 +1,11 @@
7253 -;//Message catalog for Windows Serivce Support routines
7254 -;//To support event logging functionality
7255 -;//By Raju Krishnappa(raju_krishnappa@yahoo.com)
7256 -
7257 -;//Message ID descriptions
7258 -
7259 -MessageId=100
7260 -SymbolicName=DISPLAY_MSG
7261 -Language=English
7262 -%1.
7263 -.
7264 +;//Message catalog for Windows Serivce Support routines
7265 +;//To support event logging functionality
7266 +;//By Raju Krishnappa(raju_krishnappa@yahoo.com)
7267 +
7268 +;//Message ID descriptions
7269 +
7270 +MessageId=100
7271 +SymbolicName=DISPLAY_MSG
7272 +Language=English
7273 +%1.
7274 +.
7275 diff -ruN net-snmp-5.1.2-orig/snmplib/winservice.rc net-snmp-5.1.2-5/snmplib/winservice.rc
7276 --- net-snmp-5.1.2-orig/snmplib/winservice.rc 2002-04-20 09:30:21.000000000 +0200
7277 +++ net-snmp-5.1.2-5/snmplib/winservice.rc 2005-03-13 16:17:21.000000000 +0100
7278 @@ -1,2 +1,2 @@
7279 -LANGUAGE 0x9,0x1
7280 -1 11 MSG00001.bin
7281 +LANGUAGE 0x9,0x1
7282 +1 11 MSG00001.bin
Personal OpenWRT clone
This page took 0.382518 seconds and 5 git commands to generate.