Snospfnbroptions, Snospfnbrpriority, Snospfnbrstate – Brocade Unified IP MIB Reference (Supporting FastIron Release 07.5.00) User Manual

Page 548

Advertising
background image

520

Unified IP MIB Reference

53-1002549-02

OSPF neighbor table

snOspfNbrOptions
brcdIp.1.2.4.7.1.1.6
Syntax: Integer32

Read-only

The bit mask that is set corresponding to the neighbor’s options field:

Bit 0 – The system will operate on Type of Service metrics other than
TOS 0. The neighbor will ignore all metrics except for the TOS 0 metric.

Bit 1 – The associated area accepts and operates on external
information; it is a stub area.

Bit 2 – The system is capable of routing IP Multicast datagrams. It
implements the multicast extensions to OSPF.

Bit 3 – The associated area is an NSSA. These areas are capable of
carrying type 7 external advertisements, which are translated into type
5 external advertisements at NSSA borders.

Default: Bit 0

snOspfNbrPriority
brcdIp.1.2.4.7.1.1.7
Syntax:
DesignatedRouterPri
ority32

Read-only

Specifies the priority of this interface. This object is used in the designated
router election algorithm for multi-access networks.
Valid values: 0 – 255
Default: 1. A value of 0 signifies that the router is not eligible to become the
designated router on this particular network.
If two or more routers have the same priority value, then the router with the
highest router ID becomes the designated router. The router with the next
highest router ID becomes the backup designated router.

snOspfNbrState
brcdIp.1.2.4.7.1.1.8
Syntax: Integer

Read-only

Shows the state of the communication between the Layer 3 Switch and the
neighbor:

down(1) – There has been no recent information received from the
neighbor.

attempt(2) – This state is only valid for neighbors attached to
non-broadcast networks. It indicates that no recent information has
been received from the neighbor.

init(3) – A hello packet has recently been seen from the neighbor.
However, bidirectional communication has not yet been established
with the neighbor. (The router itself did not appear in the neighbor's
hello packet.) All neighbors in this state (or higher) are listed in the hello
packets sent from the associated interface.

twoWay(4) – Communication between the two routers is bidirectional.
This is the most advanced state before beginning adjacency
establishment. The Designated Router and Backup Designated Router
are selected from the set of neighbors in the two-way state or greater.

exchangeStart(5) – The first step in creating an adjacency between the
two neighboring routers. The goal of this step is to decide which router
is the master, and to decide upon the initial Database Description (DD)
sequence number. Neighbor communications in this state or greater
are called adjacencies.

exchange(6) – The router is describing its entire link-state database by
sending DD packets to the neighbor. Each DD packet has a DD
sequence number, and is explicitly acknowledged. Only one DD packet
can be outstanding at any time. In this state, link-state request packets
can also be sent asking for the neighbor's more recent advertisements.
All adjacencies that are in the exchange state or greater are used by the
flooding procedure. In fact, these adjacencies are fully capable of
transmitting and receiving all types of OSPF routing protocol packets.

loading(7) – Link-state request packets are sent to the neighbor asking
for the more recent advertisements that have been discovered (but not
yet received) in the exchange state.

full(8) – The neighboring routers are fully adjacent. These adjacencies
will now appear in router links and network link advertisements.

Default: down(1)

Name, OID, and syntax

Access

Description

Advertising