| According to mib-ii, ifOperStatus is the current operational state of
the interface, ifAdminStatus is the desired state of the interface.
In version 4.1 of DEChub900, the ifTable is only updated at init time.
This problem is known and scheduled to be addressed in the next
release.
When you assign a particular slot as ip services and a module is in
fact in that slot, the desired state of the interface, ifAdminStatus
becomes "up" meaning that the interface is ready to pass packets. If
no module is present in the slot that you assigned as ip services, the
ifAdminStatus will indicate that the interface is "down" meaning that
the interface is not ready to pass packets. If a device is present but
not capable of providing ip services then the ifAdminStatus and
ifOperStatus will both indicate "down" not ready to pass packets. In
the DEChub900 console for that interface you will see "not configured".
The mib object ifOperStatus is not updated, this problem is known and
will be addressed.
The expected behavior of ifOperStatus in the case of an interface that
is assigned to provide ip services for the hub, is that if a device is
in the slot and is operational then ifOperStatus will indicate the
current operational state is "up" meaning ready to pass packets. If a
device is not present in the slot that is assigned to provide ip
services for the hub then the current state of the interface is "down"
meaning that it is not ready to pass packets.
As for the OBM, we have no way to tell if the OBM is connected. We
know that the OBM will receive packets and if it is connected and
assigned an ip address then packets will be transmitted otherwise
they will be dropped. So the OBM is always "up" for both the
ifAdminStatus and ifOperStatus.
Denise
|
| -.1 is correct in saying that the current MAM implementations
do not utilize ifAdminStatus and ifOperStatus. However, -.1
does not exactly what we have implemented for the next (V5)
release. A better summary would be:
If an IP address has been assigned, ifAdminStatus is Up.
If the interface is operational, ifOperStatus is Up.
The only caveat would be that for the OBM interface, assigning
an address will cause both ifAdminStatus and ifOperStatus to
go Up.
Note that the MAM assigns if interface indices as follows:
ifIndex 1 - OBM interface
ifIndex 2 - In-band IP Service interface via module in Hub Slot 1
ifIndex 3 - " " Hub Slot 2
...
ifIndex 9 - In-band IP Service interface via module in Hub Slot 8
Here are the details for V5 IPS configuration:
When a user configures in-band IP Services, the ifAdminStatus for the
MAM's interface to the IP server module is set to Up, and the
ifOperStatus is set to Down.
The MAM then begins to configure the IP server. If this operation
is successful, ifOperStatus for that interface is set to Up.
The state of IP Services for each IP server module is displayed
in Show Current Settings, under "Other Info". If the ifOperStatus
is not up, the reason is derived from the state of the module.
ifAdminStatus Server Module State ifOperStatus Display
------------------------------------------------------------------
Down or Test any any [none]
Up slot empty any Not Present
Up not responding any Not Present
Up not up any Not Active
Up up, no HLAP support any Not Supported
Up up, no IPS support any Not Supported
Up up Down or Test Not Active
Up up Up Active
Up IPS addr duplicate Up Duplicate Addrs
- Dotsie
|