Number of frame received and try to be send on the same
port. This will occur when the relay agents are in BROADCAST
MODE. In normal operation, when the product is well configured,
this should not occur. This frame is discarded.
Parsed from file act.mib.txt
Company: None
Module: PRESTICOM7-MIB
Number of frame received and try to be send on the same
port. This will occur when the relay agents are in BROADCAST
MODE. In normal operation, when the product is well configured,
this should not occur. This frame is discarded.
Parsed from file CLEARTRAC7-MIB.mib
Module: CLEARTRAC7-MIB
Vendor: Verso Technologies Canada Inc. (previously was 'Presticom Inc.')
Module: CLEARTRAC7-MIB
[Automatically extracted from oidview.com]
statBootpCannotReceiveAndForwardOnTheSamePort OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of frame received and try to be send on the same port. This will occur when the relay agents are in BROADCAST MODE. In normal operation, when the product is well configured, this should not occur. This frame is discarded." ::= { statBootp 12 }
statBootpCannotReceiveAndForwardOnTheSamePort OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Number of frame received and try to be send on the same port. This will occur when the relay agents are in BROADCAST MODE. In normal operation, when the product is well configured, this should not occur. This frame is discarded." ::= { statBootp 12 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.727.7.2.20.21.1 | statBootpNbRequestReceived | 0 | 0 | Number of BOOTREQUEST frame received |
| 1.3.6.1.4.1.727.7.2.20.21.2 | statBootpNbRequestSend | 0 | 0 | Number of BOOTREQUEST frame send |
| 1.3.6.1.4.1.727.7.2.20.21.3 | statBootpNbReplyReceived | 0 | 0 | Number of BOOTREPLY frame received |
| 1.3.6.1.4.1.727.7.2.20.21.4 | statBootpNbReplySend | 0 | 0 | Number of BOOTREPLY frame send |
| 1.3.6.1.4.1.727.7.2.20.21.5 | statBootpReplyWithInvalidGiaddr | 0 | 0 | A BOOTREPLY was received but the giaddr (the gateway IP address) fields do not correspond of any IP address of your ports. This… |
| 1.3.6.1.4.1.727.7.2.20.21.6 | statBootpHopsLimitExceed | 0 | 0 | A BOOTREQUEST frame was received with its hops count that exceed the configured Max hops. This frame is discarded. |
| 1.3.6.1.4.1.727.7.2.20.21.7 | statBootpRequestReceivedOnPortBootpc | 0 | 0 | A BOOTREQUEST frame was received on the UDP port BOOTPC. That should never occur. This frame is discarded. |
| 1.3.6.1.4.1.727.7.2.20.21.8 | statBootpReplyReceivedOnPortBootpc | 0 | 0 | A BOOTREPLY frame was received on the UDP port BOOTPC. That could occur when a BOOTP/DHCP server is on the same LAN that we are. … |
| 1.3.6.1.4.1.727.7.2.20.21.9 | statBootpInvalidOpCodeField | 0 | 0 | A frame is received on BOOTPC or BOOTPS port with a invalid operation code field: It was not a BOOTREQUEST nor BOOTREPLY. This f… |
| 1.3.6.1.4.1.727.7.2.20.21.10 | statBootpCannotRouteFrame | 0 | 0 | Configuration problem: in the IP destination address list, which is configurable, we have an address that we cannot route (we do… |
| 1.3.6.1.4.1.727.7.2.20.21.11 | statBootpFrameTooSmallToBeABootpFrame | 0 | 0 | The frame have not the minimal length of a BOOTP frame, some fields are missing. This frame is discarded. |