The ETH100 ports represent the Fast Ethernet (10/100 Mbit/sec ) adapters drivers for TP wiring. They provide transmission and receiving services of frames over LAN, in other words they deal with the physical layer management and Media Access Control (MAC): collisions, retransmissions, MAC address filtering.
The Fast Ethernet driver supports IP, ARP protocols.
In the default configuration the ETH100 drivers automatically adjust speed, and if possible even the half/full duplex mode, to the one of the HUB port which it is connected to. However it is possible to force using only a fixed mode. This procedure could be necessary if some incompatibilities could arise during the "negotiation".
It is important to highlight that for a correct working of 10Mbit/sec links it is enough to use an UTP3 cable, while for 100Mbit/sec links, even if shorts (ten cms) it is needed to use the UTP5 cable or better.
The Fast Ethernet port is labelled within the Abilis CPX with the acronym "ETH100" and it is provided with the parameters described in this section.
Here is an example on how to display the ETH100 port parameters. Shown values are the default ones.
[15:03:33] ABILIS_CPX: D P PO:ETH100 PO:58 - Not Saved (SAVE CONF), Not Refreshed (INIT) -------------------------- ETH100 ------------------------------------------------------------------------ LOG:NO MODE:AUTO DUPLEX:HALF TPPOL:AUTO dma-rxbuf:25 dma-txbuf:25 ip-rxbuf:25 arp-rxbuf:5 pppoed-rxbuf:5 pppoes-rxbuf:25 ieee-rxbuf:25
To activate any change made on the lowercase parameters, the system has to be started again, on the contrary for the uppercase
parameters it is enough to submit the initialisation command INIT PO:.
Changes made on the parameter LOG: are immediately active.
The "Not Saved (SAVE CONF)" message is displayed every time the port configuration is modified but not saved with the SAVE CONF command.
The "Not Refreshed (INIT)" message is displayed every time the port configuration is modified but not refreshed with the INIT PO: command.
LOG: | Events logging activation and generation of alarm signals |
DS | NO, D, S, A, L, T, ALL, +E |
Usually this parameter makes possible to activate/deactivate logging functionalities of meaningful events of the port as well as the detection and signalling of alarms in case of critical events.
The following table shows the available options and the related functionalities usable by the parameter:
Option | Meaning |
---|---|
D | Recording of the driver state changes and/or the meaningful events in Debug Log |
S | Recording of the driver state changes and/or the meaningful events in the System Log |
A | Periodic detection of possible alarms. The detected alarms can be displayed the command ALARM VIEW or by the analogous command available on the UTILITY of the LCD display on the front panel |
L | On alarm detection, acoustic signal generation plus a message on the LCD display. This function depends on activation of alarms detection by the "A" option |
T | Generation by the Agent SNMP of Abilis CPX of SNMP traps corresponding to any change of the driver state and/or occurring of meaningful events |
Beside the already described options the following values are also allowed:
Option | Meaning |
---|---|
NO | It means that all the logging functionalities, alarms detection and generation, above mentioned, are disabled. |
ALL | It means that all the logging functionalities, alarms detection and generation, above mentioned, are enabled. |
+E | This option added to one or more of the previous ones, extends its (their) set of meaningful events. The value "ALL+E" activates all the options and extends the set of meaningful events. The value "NO+E" is meaningless so it is ignored. |
Options can be combined together.
Some examples:
By using the characters "+" and "-" as prefix of one or more options is possible to add or delete one or more functionalities without setting from the scratch the value of the parameters.
Some examples:
The changes made on this parameter are immediately activated, without the need of initialization commands.
MODE: | Speed selection and negotiation |
AUTO | AUTO, 10TP, 100TX |
It sets the link speed or the negotiation ("AUTO") mode.
Negotiation is made according to the Nways protocol, however if the counterpart does not support that protocol, adjusting is carried out trying alternatively the use of 10TP and 100TX. The faster will be choose.
The Nways protocol negotiates also the half/full duplex more, adjustment obtained by attempt, always uses the "HALF" duplex mode.
DUPLEX: | Transmission mode |
HALF | HALF, FULL |
It sets the transmission mode: "HALF" correspond to alternating bidirectional; "FULL" to simultaneous bidirectional.
Connections to HUBs always require the "HALF" mode, while the ones to SWITCHs (depending on the SWITCH itself) could accept the "FULL" mode.
This parameter is meaningful only if MODE: is set to "10TP" or "100TX"; while it is meaningless if MODE: is set to "AUTO".
TPPOL: | Polarity setting of signals in the TP cable |
AUTO | AUTO, NORMAL, REVERSE |
It sets the Fast Ethernet board to the real polarity of signals in the TP cable.
For a correct installation the polarity will always be normal, however it is possible to correct a wiring error via software.
The value "AUTO" activates the automatic recognition; while with values "NORMAL" and "REVERSE" the adjustments forced manually.
dma-rxbuf: | Number of receive buffers for DMA |
25 | 1 - 255 |
It sets the number of receive buffers for DMA.
dma-txbuf: | Number of transmit buffers for DMA |
1 | 1 - 255 |
It sets the number of transmit buffers for DMA.
ip-rxbuf: | Number of receive buffers for IP |
25 | 1 - 255 |
It sets the number of receive buffers for IP.
arp-rxbuf: | Number of receive buffers for ARP |
25 | 1 - 255 |
It sets the number of receive buffers for ARP.
pppoed-rxbuf: | Number of receive buffers for PPPOE Discovery protocol |
25 | 1 - 255 |
It sets the number of receive buffers for PPPOE Discovery protocol.
pppoes-rxbuf: | Number of receive buffers for PPPOE Session protocol |
25 | 1 - 255 |
It sets the number of receive buffers for PPPOE Session protocol.
ieee-rxbuf: | Number of receive buffers for IEEE Bridge |
25 | 1 - 255 |
It sets the number of receive buffers for IEEE Bridge.
How to check state and statistics of the ETH100 ports by the command D S.
[16:05:04] ABILIS_CPX: D S PO:ETH100 PO:58 ------------------------------------------------------------------------ ETH100 STATE:READY MAC-ADDR:00-80-48-CD-05-7B CARD:FL100TX MODE:AUT-100TX DUPLEX:AUT-HALF TPPOL:AUT-NORMAL IEEE-FILTER:OFF -----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---| SUCC | 16320| 571|CHAR | 1522126| 35033| BROADCAST | 18100| 61|MULTICAST | 0| 0| NOBUF | 41| |LOST-IP | 0| | LOST-ARP | 0| |LOST-RARP | 0| | | | |N-COLL | | 7| FCS | 0| |L-COLL | 0| 0| RX-OVR | 0| |E-COLL | | 0| TX-UND | | 0|DEFERRED | | 37| CARR | 0| |ALIGN | 0| | TBE | 41| 632|SHORT | 0| 0| QED | | 0|LONG | 0| 0| WDG-TOUT | 0| |RUNT | 0| | JBR-TOUT | 0| |HB-FAIL | 0| | GPT-TOUT | 0| |NEG-FAIL | 0| | BUS-ERR | 0| |LINK-FAIL | 3| | DSC-ERR | 0| |FILT-FAIL | 0| | MII-ERR | 0| |CARD-RESET | 2| | ------------------------------------------------------------------------
How to display extended statistics of the ETH100 ports by the command D SE.
[16:15:38] ABILIS_CPX: D SE PO:ETH100 PO:58 ------------------------------------------------------------------------ ETH100 --- Cleared 000:03:57:43 ago, on 22/07/2004 at 12:19:16 ---------------- -----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---| SUCC | 16320| 571|CHAR | 1522126| 35033| BROADCAST | 18100| 61|MULTICAST | 0| 0| NOBUF | 41| |LOST-IP | 0| | LOST-ARP | 0| |LOST-RARP | 0| | | | |N-COLL | | 7| FCS | 0| |L-COLL | 0| 0| RX-OVR | 0| |E-COLL | | 0| TX-UND | | 0|DEFERRED | | 37| CARR | 0| |ALIGN | 0| | TBE | 41| 632|SHORT | 0| 0| QED | | 0|LONG | 0| 0| WDG-TOUT | 0| |RUNT | 0| | JBR-TOUT | 0| |HB-FAIL | 0| | GPT-TOUT | 0| |NEG-FAIL | 0| | BUS-ERR | 0| |LINK-FAIL | 3| | DSC-ERR | 0| |FILT-FAIL | 0| | MII-ERR | 0| |CARD-RESET | 2| | ------------------------------------------------------------------------
The information "Cleared DDD:HH:MM:SS ago, at DD/MM/YYYY HH:MM:SS", referred by the extended statistics, shows the time interval elapsed from the last reset of statistics (by the format "days:hours:minutes:seconds") and date/time of its execution (by the format "day:month:year" and "hours:minutes:seconds").
STATE: | Current state of the ETH100 port driver |
DOWN, READY, TXDISABLED, HALTED, FAILED, NEGOTIATING, ERR |
It shows the current state of the ETH100 port driver.
Driver | States | Meaning | Values shown in: | ||
---|---|---|---|---|---|
System Log | Debug Log | Display LCD | |||
ETH100 | DOWN | Port is not active | DN | ||
READY | Port is active | RD | |||
TXDISABLED | The transmission has been disabled due to a fatal error | TD | |||
HALTED | Port halted because of a fatal error | HL | |||
FAILED | Port is not working because of an initialisation error | FL | |||
NEGOTIATING | Port is negotiating | NG | |||
ERR | Software error. Contact Abilis assistance. | NA |
MAC-ADDR: | MAC address of the driver ETHERNET |
6 hexadecimals spaced by ":" (colon) |
The parameter MAC-ADDR: shows the MAC (Media Access Control) address used by the ETH100 port driver. MAC addresses are usually made of a sequence of 6 octets (48bits) and they are displayed as a sequence of 6 hexadecimals separated by the character ":" (colon).
CARD: | Fast Ethernet board type |
FL100TX, FL100TX/WOL |
It shows the Fast Ethernet board type in use.
MODE: | Speed mode currently in use |
UNKNOWN, 10TP, 100TX |
The prefix "AUT-" means that the speed mode, currently used, is the result of the negotiation procedure.
The prefix "FIX-" means that the speed mode, currently used, was selected manually.
The value UNKNOWN means that the negotiation procedure is active but no valid signal has been yet detected, owing to, for example, the link absence.
DUPLEX: | Transmission mode in use |
UNKNOWN, HALF, FULL |
The prefix "AUT-" means that the transmission mode, currently used, is the result of the negotiation procedure.
The prefix "FIX-" means that the transmission mode, currently used, was selected manually.
The value UNKNOWN means that the negotiation procedure is active but no valid signal has been yet detected, owing to, for example, the link absence.
TPPOL: | Polarity in use |
UNKNOWN, NORMAL, REVERSE |
The prefix "AUT-" means that the polarity, currently used, has been adjusted automatically.
The prefix "FIX-" means that the polarity, currently used, was selected manually.
The value UNKNOWN means that the negotiation procedure is active but no valid signal has been yet detected, owing to, for example, the link absence.
In case of negotiated speed or manually set to 100TX, the polarity will be always displayed as UNKNOWN because it cannot be determinated.
IEEE-FILTER | |
.
SUCC: | Number of frames successfully received |
0 - 4.294.967.295 |
The counter SUCC (INPUT/OUTPUT) shows the number of frames successfully received/sent.
CHAR: | Number of received/sent characters |
0 - 4.294.967.295 |
The counter CHAR (INPUT/OUTPUT) shows the number of characters received/sent.
BROADCAST: | Number of "broadcast" frames received/sent |
0 - 4.294.967.295 |
The counter BROADCAST (INPUT/OUTPUT) is incremented every time a "broadcast" frame is received/sent.
The "broadcast" frames are sent to all the LAN Ethernet stations.
MULTICAST: | Number of "multicast" frames received/sent |
0 - 4.294.967.295 |
The counter MULTICAST (INPUT/OUTPUT) is incremented every time a "multicast" frame is received/sent.
The "multicast" frames are sent to a group of the LAN Ethernet stations.
NOBUF: | Number of frames discarded because of the unavailability of receiving buffer |
0 - 4.294.967.295 |
The counter NOBUF (INPUT) is incremented every time a frame is discarded because of the unavailability of receiving buffers.
High values of this parameter compared to the overall data exchanged could mean that the Abilis system is overloaded, so that it is convenient to contact the seller and consider to upgrade it.
LOST-IP: | Number of received frames discarded because of the unavailability of IP buffers |
0 - 4.294.967.295 |
The counter LOST-IP (INPUT) is incremented every time a received frames is discarded because of the unavailability of IP buffers.
LOST-ARP: | Number of received frames discarded because of the unavailability of ARP buffers |
0 - 4.294.967.295 |
The counter LOST-ARP (INPUT) is incremented every time a received frames is discarded because of the unavailability of ARP buffers.
LOST-RARP: | Number of received frames discarded because of the unavailability of RARP buffers |
0 - 4.294.967.295 |
The counter LOST-RARP (INPUT) is incremented every time a received frames is discarded because of the unavailability of RARP buffers.
N-COLL: | Number of "normal" collisions |
0 - 4.294.967.295 |
The counter N-COLL (OUTPUT) is incremented every time a "normal collision" occurs.
Collisions, in a Ethernet network, are an absolutely normal occurrence, but if their number grows up to the overall amount of data exchanged, then it should be considered the network segmentation, for example through a SWITCH.
LANs highly congested present a high number of "extended collisions" (E-COLL).
L-COLL: | Number of "late" collisions |
0 - 4.294.967.295 |
The counter L-COLL (OUTPUT) is incremented every time a "late collision" occurs, while a frame is sent or received.
Significative values of this parameter could mean:
hardware failures of one or more LAN stations;
wrong configuration of the modality half/full duplex in one or more LAN stations;
the LAN is too wide, segmentation has to be considered. The LAN collision domain is estimated about 2,5km for a 10Mbut/sec LAN while 250m for a 100Mbit/sec one.
E-COLL: | Number of "extended" collisions |
0 - 4.294.967.295 |
The counter E-COLL (OUTPUT) is incremented every time that 16 consecutive collisions for the same frame occur.
If the number of collisions grows up to the overall amount of data exchanged, then it should be considered the network segmentation, for example through a SWITCH.
FCS: | Number of received frames with a wrong FCS |
0 - 4.294.967.295 |
The counter FCS (INPUT) is incremented every time the FCS (or CRC) check procedure, of each frame, fails.
High values, especially if growing, of this counter could mean a bad quality of the transmission line, corrupting the received data; it surely points out errors into the received data. A bad quality turns into a performance lowering and into possible breaks out of the link.
RX-OVR: | Number of "overrun" occurred during reception |
0 - 4.294.967.295 |
The counter RX-OVR (INPUT) is incremented every time the communication board reports an "overrun" due to the received data. It occurs whenever the Ethernet driver, due to an excessive payload within the Abilis CPX, is not fast enough to take data from the communication board. Up to now, no Abilis CPX application gave such "overrun" problems, however if the value of this counter get more and more significative compared to the amount of data exchanged, it should be convenient to contact the seller and consider the Abilis CPX upgrade.
However, if high numbers of FCS are also detected, then it is more probable that the "overload" is caused by the excessive number of errors on the transmission line, which, as consequence, should be repaired.
TX-UND: | Number of "underrun" occurred during transmission |
0 - 4.294.967.295 |
The counter TX-UND (OUTPUT) is incremented every time the communication board reports an "underrun" due to the sent DATA. In the actual implementation this counter has to always be zero, however if other values would be displayed, please contact the technical support.
DEFERRED: | Number of deferred frames |
0 - 4.294.967.295 |
The counter DEFERRED (OUTPUT) is incremented every time a frame transmission is deferred.
This counter does not highlight particular problems.
CARR: | Number of "carrier loss" in TP links |
0 - 4.294.967.295 |
The counter CARR (INPUT) shows the number of "carrier loss" in TP links.
it is normal that this counter increments every time the TP link is missing. Growing values, not due to intentional disconnections, could mean:
bad quality of the transmission line;
the HUB, which the Abilis is connected to, doesn't work properly.
ALIGN: | Number of "align error" |
0 - 4.294.967.295 |
The counter ALIGN (INPUT) shows the number of received frames with an align error.
Non-zero values could stand for problems in LAN station, or for a bad transmission line quality.
TBE: | Number of times buffers have been completely emptied |
0 - 4.294.967.295 |
Only internal use
QED: | Number of times frames have been queued |
0 - 4.294.967.295 |
Only internal use.
SHORT: | Number of too short frames |
0 - 4.294.967.295 |
The counter SHORT (INPUT) is incremented every time the length of the received Ethernet frame is shorter than 64 bytes. Non-zero values could stand for problems in LAN station, or for a bad transmission line quality.
The counter SHORT (OUTPUT) is incremented every time the "higher level port", such as IPLAN, requests to send a frame whose length is shorter than 64 bytes.
In the actual implementation this counter has to always be zero, however if other values would be displayed, please contact the technical support.
LONG: | Number of too long frames |
0 - 4.294.967.295 |
The counter LONG (INPUT) is incremented every time the length of the received Ethernet frame is longer than 1518 bytes. Non-zero values could stand for problems in LAN station, or for a bad transmission line quality.
The counter LONG (OUTPUT) is incremented every time the "higher level port", such as IPLAN, requests to send a frame whose length is longer than 1518 bytes.
In the actual implementation this counter has to always be zero, however if other values would be displayed, please contact the technical support.
WDG-TOUT: | Number of "watchdog-timeouts" |
0 - 4.294.967.295 |
The counter WDG-TOUT (INPUT) shows the number of "watchdog-timeout" events.
The Fast Ethernet has its own "watchdog timer", which checks the frame receiving timings. If the frame receiving time is bigger that the allowed value, generally due to transmission errors, the "watchdog timer" will end the reception and signal this event to the driver.
Significative values could stand, most probably, for a bad transmission line quality, but they could also represent faults of the fast-ethernet adapter.
RUNT: | Number of "RUNT" frames |
0 - 4.294.967.295 |
The counter RUNT (INPUT) is incremented every time while a frame is received, a collision, inside the homonymous window (i.e. within the first 512 bytes), is detected.
The above mentioned frame is discarded.
JBR-TOUT: | Number of "jabber-timeouts" |
0 - 4.294.967.295 |
The counter JBR-TOUT (INPUT) shows the number of "jabber-timeout" events.
The "jobber timeout" is an embedded protection of the board to avoid that its transmission problem could halt all the LAN. Particularly if the frame transmission requires a too long time (for example for sending more than 2048 bytes), The transmitter is forcedly deactivated and the event is signalled to the driver which increments the counter JBR-TOUT.
A significative value of this parameter, especially if growing, could represent a faulty board, please contact the technical support.
HB-FAIL: | Number of "heartbeat-fails" |
0 - 4.294.967.295 |
This parameter is only valid for 10TP links.
This counter shows the number of "heartbeat-fails", that is the bad recognition of the "link pulses" of the 10TP links.
Non-zero values, especially if growing, could stand, most probably, for a bad transmission line quality, but they could also represent faults of the fast-ethernet board or of the HUB port.
GPT-TOUT: | Number of "general purpose timer timeout" |
0 - 4.294.967.295 |
The counter GPT-TOUT (INPUT) shows the number of "general purpose timer timeout" events occurred.
Only internal use.
NEG-FAIL: | Number of negotiation failures |
0 - 4.294.967.295 |
The counter NEG-FAIL (INPUT) shows the number of negotiation failures.
BUS-ERR: | Number of errors detected on the PCI bus |
0 - 4.294.967.295 |
The counter BUS-ERR (INPUT) shows the number of errors detected on the PCI bus.
A significative value of this parameter, especially if growing, could represent a CPX hardware problem, please contact the technical support.
LINK-FAIL: | Number of "link failures" |
0 - 4.294.967.295 |
The counter LINK-FAIL (INPUT) shows the number of "link failure" events occurred.
it is normal that this counter increments every time the TP link is missing. Growing values, not due to intentional disconnections, could mean:
bad quality of the transmission line;
the HUB, which the Abilis is connected to, doesn't work properly.
DSC-ERR: | Number of "descriptor errors" |
0 - 4.294.967.295 |
The counter DSC-ERR (INPUT) shows the number of "descriptor errors" occurred.
Only internal use.
FILT-FAIL: | Number of "filtering failures" |
0 - 4.294.967.295 |
The counter FILT-FAIL (INPUT) shows the number of "filtering failure" events.
Only internal use.
MII-ERR: | Number of "MII errors" |
0 - 4.294.967.295 |
The counter MII-ERR shows the number of "MII errors" occurred, that is physical errors detected on the MII interface.
Only internal use.
CARD-RESET: | Number of times that the board has been reinitialised |
0 - 4.294.967.295 |
Actually not in use.
Trap own code | Trap mnemonic | SNMP variables shown in the trap | Description |
---|---|---|---|
41 | cxTrapEth100Down | cxPortIndex, cxPortType, cxEth100DiagState, sysUpTime | The SNMP Agent of the Abilis CPX generates this kind of trap every time the ETH100 port driver leaves the READY state and reaches one of the following states: DOWN, TXDISABLED, HALTED, FAILED or NEGOTIATING |
42 | cxTrapEth100Ready | cxPortIndex, cxPortType, cxEth100DiagState, sysUpTime | The SNMP Agent of the Abilis CPX generates this kind of trap every time the ETH100 port driver leaves one of the following states: DOWN, TXDISABLED, HALTED, FAILED or NEGOTIATING and reaches the READY state |
cxPortIndex | Fast Ethernet port which the SNMP trap refers to |
0 - 999 |
This variable shows the CPX port number which the SNMP trap refers to.
cxPortType | Type and description of the Fast Ethernet port which the trap refers to |
type - description |
This variable shows either the port type which the trap refers to (in this case ETH100) and the description eventually associated to it.
cxEth100DiagState | Current state of the Fast Ethernet port driver which the trap refers to |
down(0), ready(1), txDisabled(2), halted(3), failed(4), negotiating(5) |
This variable shows the current state of the ETH100 port driver which the trap refers to. The following table shows the relationship among the state value stored in the SNMP variable and the ones obtained executing the command D S.
Value of the SNMP variable | Correspondent state of the ETH100 driver |
down(0) | DOWN |
ready(1) | READY |
txDisabled(2) | TXDISABLED |
halted(3) | HALTED |
failed(4) | FAILED |
negotiating(5) | NEGOTIATING |
sysUpTime | Elapsed time from the system start to the event occurrence |
0 - 4.294.967.295 or "ddd:hh:mm:ss" |
This variable stores the elapsed time (in cent of second) from the system start to the SNMP trap event occurrence.
This value is usually shown by the format days:hours:minutes:seconds.