The IP ROUTER port (IPRTR)

[18:45:45] ABILIS_CPX: D P PO:900

PO:900 ------------------------------------------------------------------------
IPRTR  LOG:NO         TYPE:USER       MCAU:NO         ps:2048       DFTTTL:64  
       maxroute:500   tracerec:100    R-ID:AUTO (192.168.000.253)   NAT:NO
       ACL:NO         ACLBYPASS:#
       COS:DISABLED   COSDFT:NORMAL   COSBALANCE:NO   NORMRATE:50   LOWRATE:50 
       PPP-DNS-PRI:000.000.000.000    PPP-DNS-SEC:000.000.000.000
       DEF-LOCAL-AD:0     DEF-STATIC-AD:1     DEF-OSPF-AD:110   DEF-RIP-AD:120 

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:

• setting "LOG:DS+E", activates the extended logging functions for Events Log and System Log
• setting "LOG:STA", activates the extended logging functions for System Log, SNMP traps generation and periodic detection of alarm states;

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:

• Suppose the current value of the parameter is "LOG:DSTA", by setting "LOG:-A", the periodic detection of eventual alarm states is removed, leaving unchanged all the remaining options; in such way the final value of the parameter will be "LOG:DST";
• Suppose the current value of the parameter is "LOG:ST", by setting "LOG:+DA", the logging function of the events on the Events Log and the periodic alarm detection are added to the already activated options; in such way the final value of the parameter will be "LOG:DSTA".

The changes made on this parameter are immediately activated, without the need of initialization commands.

This parameter sets how the port behaves if data compression is activated.

The port connected to the X.25 network is defined NETWORK port; the one connected to the user device USER port.

The NETWORK port sends compressed data and expands the received ones; the USER port compresses the received data and sends the expanded ones.

The IPRTR can be only a USER port.

It affects only X.25 communications.

If MCAU is set to NO, Abilis CPX transports, without any changes, the cause and diagnostic code of the CLEAR packets; it also uses the F0 cause code and the suitable diagnostic one for all the CLEAR packets internally generated.

If MCAU is set to YES, Abilis CPX forces the cause code of the CLEAR packet sent to the value 00 (DTE originated), either for the external CLEAR and the internal ones.

The changes made on this parameter are immediately activated, without the need of initialisation commands.

This parameter affects only X.25 communications, because it sets the maximum X.25 packet size.

It sets the default TTL (Time To Live) of IP datagrams internally generated by the Abilis CPX, such as ICMP messages or RIP, UDP, TCP, TELNET, SNMP, SNTP and DNS ports datagrams.

It sets the maximum number of routing that the homonym table can store.

If the table will be full, no more routings can be added and an informative message will be shown in the System Log.

It sets the maximum number of records in the TCP/IP events trace. The trace is handled circularly, that is, once its maximum has been reached, the less recent events are progressively deleted, in order to free place to the more recent ones.

If the parameter is set to 0, the TCP/IP tracing function is not active.

It shows the Router ID address.
AUTO: This value is obtained considering the first IP port of the homonym table, whose address is not 0.0.0.0. This value means that no IP port has got the needed characteristics.

Eventual changes made on the IP ports table will affect this parameter value.

It indicates the side of the IPRTR when remote hosts connects to R-ID IP address.

This information is required by NAT in order to determine if the IP address must be translated or not.

When configured as NO, means that NAT is not configured.
When configured as INSIDE, means that R-ID address in in the INSIDE IPPort.
When configured as OUTSIDE, means that R-ID address in in the OUTSIDE IPPort.

This parameter can be set only when R-ID is not set as AUTO.

It activates the IP Access List service and choose the operating mode.

The service IP access list is a security procedure for filtering traffic in transit to and from Abilis CPX, depending on the address and services requested. Datagrams are filtered according to their header and not to their content. There are two way of filtering:

"STD" (Standard): datagrams are filtered by their source and destination addresses (address filtering);

"EXT" (Extended): datagrams are filtered by their source and destination addresses but also by the internet protocol. For TCP and UDP protocols even the port logic number is checked (that is the service requested).

If this parameter is set to "NO" the service IP access list is disabled.

It sets the IP address (source and/or destination) of the IP datagram received that will be managed without considering filters eventually defined in the IP Access List.

The value "#" stands for "no IP address", that is the IP access list service will NOT be applied to any IP datagrams.

The value "*" stands for "any IP address", that is the IP access list service will be applied to any IP datagrams.

It activates/deactivates the IP classes of service. Class of service is a feature used to assign different priorities to specific paths of IP datagrams.
The assignment of this priority is done by IPRTR upon reception of every IP datagram, using the informations present in the IPACL.

It sets the Class of IP service default value.

The IP classes of service available are:

Class of service	Meaning
LOW	Class of service "low"
NORMAL	Class of service "normal"
HIGH	Class of service "high"

It activates/deactivates the balance functionality of the IP classes of service. This procedure provides an acceptable service to each class; by avoiding that higher priority classes are too prevalent respect the lower ones. The user, through the parameters NORMRATE: and LOWRATE:, can set the percentage balance ratio.

It sets the percentage balance ratio between resources allocated for the classes with "NORMAL" priority and the ones with "HIGH" priority.

It sets the percentage balance ratio between resources allocated for the classes with "LOW" priority and the ones with "NORMAL" priority.

it is the IP address of the primary DNS server.
This information is provided by local PPPs to remote PPPs

When set to 0.0.0.0 means that no primary DNS server is present.

it is the IP address of the secondary DNS server.
This information is provided by local PPPs to remote PPPs

When set to 0.0.0.0 means that no secondary DNS server is present.

Default administrative distance for local-connected routes.

When IPRTR gets routing from different routings protocol, must give them a specific priority. This is needed because it is possible to have routings gained from different routing protocols, but that are the same (e.g. in case of IPRTR receives the same NET/MASK information from RIP and OSPF).
When this situation occurs, IPRTR will use the routing protocol with the better distance (the lower is the distance, the better is the protocol).
This parameter can be overridden in case of current routing is present into IPRTR administrative distance table.

Default administrative distance for static routes.

When IPRTR gets routing from different routings protocol, must give them a specific priority. This is needed because it is possible to have routings gained from different routing protocols, but that are the same (e.g. in case of IPRTR receives the same NET/MASK informations from RIP and OSPF).
When this situation occurs, IPRTR will use the routing protocol with the better distance (the lower is the distance, the better is the protocol).
This parameter can be overridden in case of current routing is present into IPRTR administrative distance table.

Default administrative distance for OSPF routes.

When IPRTR gets routing from different routings protocol, must give them a specific priority. This is needed because it is possible to have routings gained from different routing protocols, but that are the same (e.g. in case of IPRTR receives the same NET/MASK information from RIP and OSPF).
When this situation occurs, IPRTR will use the routing protocol with the better distance (the lower is the distance, the better is the protocol).
This parameter can be overridden in case of current routing is present into IPRTR administrative distance table.

Default administrative distance for RIP routes.

When IPRTR gets routing from different routings protocol, must give them a specific priority. This is needed because it is possible to have routings gained from different routing protocols, but that are the same (e.g. in case of IPRTR receives the same NET/MASK in formations from RIP and OSPF).
When this situation occurs, IPRTR will use the routing protocol with the better distance (the lower is the distance, the better is the protocol).
This parameter can be overridden in case of current routing is present into IPRTR administrative distance table.

[18:45:45] ABILIS_CPX: D IPS

PO:900 ------------------------------------------------------------------------
IPRTR  ROUTINGS TABLE Diagnostics
       -----------|---State---|-Current%--|--Current--|---Peak----|----Max----|
       ROUTINGS   |  OVERFLOW |          2|         50|        100|       2500|
       ------------------------------------------------------------------------
       --- Cleared 000:00:04:41 ago, on 03/12/2002 at 11:23:01 ----------------
       ROUTER Statistics
       -----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|       
       DGM        |1264600    |1224330    |HDR-ERR    |0          |           |
       ADDR-ERR   |0          |           |FRW-DGM    |           |0          |
       UNK-PROT   |0          |           |DISCARDS   |0          |0          |
       LOCAL-DGM  |1264571    |           |NO-ROUT    |           |0          |
       REAS-TOUT  |0          |           |REAS-REQD  |32         |           |
       REAS-OK    |12         |           |REAS-FAIL  |4          |           |
       FRAG-OK    |           |16         |FRAG-FAIL  |           |0          |
       FRAG-CREATE|           |32         |ROUT-DISC  |0          |           |
       ------------------------------------------------------------------------
       ICMP Statistics
       -----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
       MSG        |59         |77         |ERR        |0          |           |
       DEST-UNREAC|11         |5          |T-EXCEED   |27         |0          |
       PARM-PROB  |0          |0          |SRC-QUENCH |0          |0          |
       REDIRECT   |0          |0          |ECHO       |13         |59         |
       ECHO-REP   |8          |13         |TSTAMP     |0          |0          |
       TSTAMP-REP |0          |0          |ADMASK     |0          |0          |
       ADMASK-REP |0          |0          |
       ------------------------------------------------------------------------

Indicates the state of the routing table, depending on the number of routings present into table.

Possible routing table states are:

• NORMAL (routings used are less than 60%).
• WARNING (routings used went over 60%. A DANGER_IN message will be written in the system LOG. To go back to normal, routings must decrease to 55%).
• DANGER (routings used went over 80%. To go back to warning, routings must decrease to 75%. A DANGER_OUT message will be written in the system LOG).
• OVERFLOW (routings used reached 100%. An OVERFLOW message will be written in the system LOG).

Indicates the current PERCENTAGE of routings present into routing table.

Indicates the current NUMBER of routings present into routing table.

Indicates the maximum number of routings reached from start-up into table.

This information indicate the MAXROUTE parameter present into IPRTR port.

The counter DGM (INPUT) is incremented every time an IP datagram is received, while the DGM (OUTPUT) one every time an IP datagram is sent.

The counter HDR-ERR (INPUT) is incremented every time an IP datagram is received, but it has an error in its header (Bad Checksum and/or elapsed TTL and/or wrong version and/or etc.).

The counter ADDR-ERR (INPUT) is incremented every time an IP datagram, whose destination address is not valid, is received.

The counter FRW-DGM (OUTPUT) is incremented every time an IP datagram is received and forwarded to the IP port, where it can be immediately transmitted or queued.

The counter UNK-PROT (INPUT) is incremented every time an IP datagram, whose protocol value is unknown, is received.

The counter DISCARDS (INPUT) is incremented every time an IP datagram is discarded owing to the absence of free buffers.

The counter DELIVERS (INPUT) is incremented every time an IP datagram is really delivered to a X.25 channels, a "LAN" or "LINK" port.

The counter NO-ROUT (INPUT) is incremented every time an IP datagram is discarded because the proper IP routing was missing.

The counter REAS-TOUT (INPUT) shows how many times the IP fragment reassembling procedure was aborted. The already received fragments are lost because the waiting timeout of the missing ones ran over.

The counter REAS-REQD (INPUT) shows the number of IP fragments received.

The counter REAS-OK (INPUT) is incremented every time an IP datagram is correctly reassembled.

The counter REAS-FAIL (INPUT) is incremented every time an error occurs during an IP datagram reassembling.

The counter FRAG-OK (OUTPUT) is incremented every time an IP datagram is correctly fragmented.

The counter FRAG-FAIL (OUTPUT) is incremented every time an IP datagram has not been fragmented because the flag "don't fragment" was set.

The counter FRAG-CREATE (OUTPUT) shows the number of IP fragments created by the fragmentation.

The counter ROUT-DISC (INPUT) is incremented every time the IP routing is discarded.

The counter MSG (INPUT) is incremented every time an ICMP message is received, while the MSG (OUTPUT) every time it is sent.

The counter ERR (INPUT) is incremented every time a bad ICMP message is received (i.e. bad Checksum field).

The counter DEST-UNRICH (INPUT) is incremented every time an "Unreachable destination" ICMP message is received, while the DEST-UNRINCH (OUTPUT) one every time it is sent.

The counter T-EXCEED (INPUT) is incremented every time a "Time Exceeded" ICMP message is received, while the T-EXCEED (OUTPUT) one every time it is sent.

The counter PARM-PROB (INPUT) is incremented every time a "Parameter Problem" ICMP message is received, while the PARM-PROB (OUTPUT) one every time it is sent.

The counter SRC-QUENCH (INPUT) is incremented every time a "Source Quench" ICMP message is received, while the SRC-QUENCH (OUTPUT) one every time it is sent.

The counter REDIRECT (INPUT) is incremented every time a "Redirect" ICMP message is received, while the REDIRECT (OUTPUT) one every time it is sent.

The counter ECHO (INPUT) is incremented every time a "Echo Request" ICMP message is received, while the ECHO (OUTPUT) one every time it is sent.

The counter ECHO-REP (INPUT) is incremented every time a "Echo Reply" ICMP message is received, while the ECHO-REP (OUTPUT) one every time it is sent.

The counter TSTAMP (INPUT) is incremented every time a "Timestamp Request" ICMP message is received, while the TSTAMP (OUTPUT) one every time it is sent.

The counter TSTAMP-REP (INPUT) is incremented every time a "Timestamp Reply" ICMP message is received, while the TSTAMP-REP (OUTPUT) one every time it is sent.

The counter ADMASK (INPUT) is incremented every time a "Address mask Request" ICMP message is received, while the ADMASK (OUTPUT) one every time it is sent.

The counter ADMASK -REP (INPUT) is incremented every time a "Address mask Reply" ICMP message is received, while the ADMASK -REP (OUTPUT) one every time it is sent.

[16:20:42] ABILIS_CPX:d ipp

IPRTR (PO:900) parameters:  R-ID:AUTO (010.000.000.001)

IPP:0  - Verso_router_a_Milano:10.0.0.50/32 -----------------------------------
ACT    IPADD:010.000.000.001                       MTU:1500                    
       MASK :255.255.255.000 NAT:NO      SRCV:NO   outbuf:50                   
       IFTYPE:LAN            REDIS:YES             RP:NO                       
       BRD:NET               LOWPO:155   HIDE:NO   FAIRQUEUE:YES               
       SPEEDLIMIT:YES        LOSPEED:128           HISPEED:10000               

IPP:1  ------------------------------------------------------------------------
ACT    IPADD:192.168.001.200 NEIGH:000.000.000.000 MTU:1500       FRAG:FRF12   
       MASK :255.255.255.000 NAT:NO      SRCV:NO   outbuf:50      FRAGSIZE:128 
       IFTYPE:LINK           REDIS:YES             RP:NO    
       ENC:RAW-IP            LOWPO:1     HIDE:NO   FAIRQUEUE:YES
       SPEEDLIMIT:NO

IPP:2  ------------------------------------------------------------------------
ACT    IPADD:192.168.002.200 NEIGH:000.000.000.000 MTU:1500
                             NAT:NO      SRCV:NO   outbuf:50
       IFTYPE:PPP            REDIS:YES             RP:NO
                             LOWPO:541   HIDE:NO   FAIRQUEUE:YES
       SPEEDLIMIT:NO

IPP:3  ------------------------------------------------------------------------
ACT    IPADD:192.168.003.200 NEIGH:000.000.000.000 MTU:1500
       MASK :255.255.255.000 NAT:NO      SRCV:NO   outbuf:50
       IFTYPE:X25BSVC        REDIS:YES             RP:NO
       CDI:NO                            HIDE:NO   FAIRQUEUE:YES
       CDO:NO                DT:0        TB:6      RTY:INC        NRTY:NOMAX   

IPP:4  ------------------------------------------------------------------------
ACT    IPADD:192.168.004.200 NEIGH:000.000.000.000 MTU:1500
       MASK :255.255.255.000 NAT:NO      SRCV:NO   outbuf:50
       IFTYPE:X25PVC         REDIS:YES             RP:NO
       PVC:NONE                          HIDE:NO   FAIRQUEUE:YES

IPP:5  ------------------------------------------------------------------------
ACT    IPADD:192.168.005.200 NEIGH:000.000.000.000 MTU:1500       FRAG:NO
       MASK :255.255.255.000 NAT:NO      SRCV:NO   outbuf:50
       IFTYPE:LINK           REDIS:YES             RP:NO
       ENC:FR-IETF           LOWPO:101   HIDE:NO   FAIRQUEUE:YES
       SPEEDLIMIT:NO

IPP:6  ------------------------------------------------------------------------
ACT    IPADD:192.168.006.200 NEIGH:000.000.000.000 MTU:1500
       MASK :255.255.255.000 NAT:NO      SRCV:NO   outbuf:50
       IFTYPE:LINK           REDIS:YES             RP:NO
       ENC:FR-CISCO          LOWPO:102   HIDE:NO   FAIRQUEUE:YES
       SPEEDLIMIT:NO
       KEEPALIVE:YES         KA-DELAY:10           KA-LIMIT:6                  

IPP:7  ------------------------------------------------------------------------
ACT    IPADD:192.168.007.200 NEIGH:000.000.000.000 MTU:1500
       MASK :255.255.255.000 NAT:NO      SRCV:NO   outbuf:50
       IFTYPE:LINK           REDIS:YES             RP:NO
       ENC:HDLC-CISCO        LOWPO:2     HIDE:NO   FAIRQUEUE:YES
       SPEEDLIMIT:NO
       KEEPALIVE:NO	   
	   
IPP:10 ------------------------------------------------------------------------
ACT    IPADD:192.168.010.200
       MASK :255.255.255.000
       IFTYPE:VIRTUAL        REDIS:YES             RP:NO
       BRD:NET               P-IPP:0     HIDE:NO
	   
IPP:62 ------------------------------------------------------------------------
ACT    IPADD:192.168.062.200                       MTU:1500
       MASK :255.255.255.000 NAT:NO      SRCV:NO   outbuf:50
       IFTYPE:LAN            REDIS:YES             RP:RIP,OSPF
       BRD:NET               LOWPO:NONE  HIDE:NO   FAIRQUEUE:YES
       SPEEDLIMIT:NO
       - RIP section ----------------------------------------------------------
       RIPSEND:RIP2B    RIPRECV:BOTH     RIPNU:YES    RIPMETRIC:1              
       - OSPF section ---------------------------------------------------------
       OAREA:#                   ONETTYPE:BN     OPRIO:0      OCOST:1          
       ORXMT:5      OTRDEL:1     OHELLO:10       ODEAD:60     omax-nei:5       

IPP:63 ------------------------------------------------------------------------
NEW    IPADD:000.000.000.000 NEIGH:000.000.000.000 MTU:1500       FRAG:NO
       MASK :255.255.255.255 NAT:NO      SRCV:NO   outbuf:50
       IFTYPE:LINK           REDIS:YES             RP:NONE
       ENC:RAW-IP            LOWPO:NONE  HIDE:NO   FAIRQUEUE:YES
       SPEEDLIMIT:NO   
	   
[16:20:46] ABILIS_CPX: 

This identifier is used into IP routings to refer to the same port.

It can also be used to refer to the port during configurating operation of the IP ports table.

As it can be seen from the example, the IP ports table can contain "empty places" and it never get compacted. A new IP port can be added only if its ID is not already in use.

When the IPRTR port receives a X.25 SVC call, coming from the Connection Oriented Router (COR), the search of the port matching the content of the "Calling address" field starts from port 0. Therefore if one or more IP ports match the incoming call, the call will be forwarded to the port with the smallest ID value.

In order to avoid unexpected behaviours, mainly due to inconsistencies between the addresses of the IP networks linked, it is absolutely necessary to avoid these situations of ambiguity.

It indicates if the IPP is currently active or not.
When set to ACT, means that IPP was already present when CPX booted.
When set to NEW, means that IPP is simply added in configuration, but IPP cannot be used.

To make IPP status from NET to ACT, a CPX reboot is reaquired.

It sets the IP address of the port. The allowed values are shown in the following table:

HEX:	00000000	01000000 - 7EFFFFFF	80000000 - DFFFFFFF
DDN:	0.0.0.0	1.0.0.0 - 126.255.255.255	128.0.0.0 - 223.255.255.255

IP addresses of D class and class E and are not currently supported.

For IP ports of type WAN ("LINK", "X25BSVC", "X25PVC"), is possible to avoid the assignment of an IP address leaving setting the value to 0.0.0.0. In this case, the obtained configurations are known as "half-router" where WAN unnumbered links are used.

In the configurations of WAN unnumbered links, the possibilities of using the RIP protocol are limited and sometime is not possible at all. For the complete understanding of thematic related to the use of protocols of dynamic routing such as RIP, refer to the relative banns of the IETF, that is to the RFC (Request for Comment).

It establishes the mask to be used by IP port.

In case of a "LAN" port, the mask MUST absolutely coincide with the value of the mask used by all the LAN stations. Parameter "MASK:" it can be only set to values that contain a consecutive sequence of bit set to 1, estimated starting from the more meaningful bit to the less meaningful one.

By doing the "logical And" between the value contained in parameter "MASK:" with the value contained in parameter IPADD: we have the value of the network associated to IP port, and will be the value exported like NET in the routing table, obviously if parameter REDIS: is set to "YES".

Abilis CPX executes a validity check for the networks identified with parameters IPADD: and MASK: of IP ports, that is the networks must be different and not overlapped.

It sets the connection type.

Value	Description
X25PVC	Permanent X.25 connection.
X25BSVC	Switched X.25 connection.
LINK	non-X.25 synchronous link, which uses the ports type SYNC, MLM, ML, LAPB or FR.
LAN	Ethernet link type, Fast Ethernet or Token Ring, used by the port type IPLAN.
PPP	PPP point to point protocol.
VIRTUAL	The use of virtual enables the possibility to simulate more IPPorst with different network addresses on the same primary IPPort.

The parameter is displayed and configurable only if the connection type currently set in the parameter IFTYPE: is "LINK", "PPP" or "LAN", because in these case the lower level port is specified.

If the connection type is "LINK", the lower level CPX port type can only be SYNC, MLM, ML, LAPB or FR.

If the connection type is "PPP", the lower level CPX port type can only be PPP.

IF the connection type is "LAN", the lower level CPX port type can only be IPLAN.

The parameter is displayed and configurable only if the connection type currently set in the parameter IFTYPE: is "X25PVC", because in this case the PVC connection identifier is specified.

The parameter is visualized and configurable only if the connection type set in the parameter IFTYPE: is "LINK", "PPP" or "X25BSVC" or "X25PVC", because the IP address of the neighbour router is specified.

The value of "NEIGH:" must be set to the value "router-id" of the neighbour router and, at the same time, the parameter MASK: must correspond to the mask used by network containing the "router-id".

In order to use protocol RIP with unnumbered links, that is if parameter IPADD: of the port in object is set to 0.0.0.0., this parameter must correctly set.

If numbered links are used (IPADD: not 0.0.0.0.), the value of parameter "NEIGH:" can be 0.0.0.0. or it must be a valid address for the network identified by IPAPP and MASK.

If unnumbered links are used (IPADD:0.0.0.0) without the protocol RIP, the value of "NEIGH:" it can be 0.0.0.0.

It sets the maximum size of the IP datagram that can be sent without fragmentation.

It shows the number of buffers available in the transmission queue. Every buffer can contain only one IP datagram.

The default value is a good trade-off between buffering ability and the maximum delays permissible for an efficient communication; normally it is not necessary to modify it.

For the complete understanding of thematic related to buffering and the delays refer to the relative banns of the IETF, that is to the RFC (Request for Comment).

The parameter is displayed and configurable only if the connection type currently set in the parameter IFTYPE: is "LINK", because in these cases it is possible to select and apply datagrams fragmentation.

It sets Maximum size of a frame fragment generated during the fragmentation procedure.

The parameter is displayed and configurable only if the connection type currently set in the parameter IFTYPE: is "LINK", and if the parameter FRAG: is set to "FRF12" or "ABILIS".

If it is set to "YES", the IP port will automatically add a new routing (connected type) to the IP routing table. The values NET:, MASK:, METRIC: and IPP: of routing will be obtained from the IP port configuration, particularly the NET: field of the routing will be obtained doing the "local And" between the current values of parameters IPADD: and MASK: of the IP port.

If the parameter is set to "NO" the connected routing won't be created.

It sets whether the connected routing has to be hidden to the other routers during RIP updating.

If the parameter is set to "NO", the routing will be insert in the RIP updates sent to other router, otherwise it won't be inserted.

IP networks support two kind of broadcast:

• limited, -1 (255.255.255.255);

• direct, <net><-1> (ex 192.168.0.255 in case that MASK:255.255.255.0).

For both type the Abilis CPX doesn't route, as the RFC 1812 requires. However it is possible that Abilis CPX has to send broadcast datagram on IP port in the following cases:

• internally generated by "local protocols", such as RIP.

• datagram received from others and it could not be identified as broadcast until it reached its destination. This situation usually happens when dealing with sub-networks.

The parameter "BRD:" set how the Abilis CPX behaves during broadcast transmission:

Value	Meaning
NO	eventual datagrams are discarded;
NET	broadcasts are sent as "directs", <net><-1> (i.g. 192.168.0.255);
LAN	broadcasts are sent as "limited", 255.255.255.255;

The parameter is displayed and configurable only if the connection type currently set in the parameter IFTYPE: is "LAN".

It activates the functionality of balancing the traffic queues according to the modality "fair queuing".
Priority is divided in 3 classes: HIGH, NORMAL, LOW. For more details see IP classes of service.

The parameter is displayed and configurable only if the connection type currently set in the parameter IFTYPE: is "X25BSVC".

It specifies the X.25 called address of the incoming call must have to be accepted by the IP port in object.

• if the parameter is set to "NO", the IP port do not accept any incoming call.

• if it contains only the character "*", the X.25 called address of the incoming call can have any value.

• if it contains a numeric value, the X.25 called address of the incoming call must match this value.

The character "*" can be used as well as a prefix of a sequence of digits with the meaning of " any number of digits and any sequence". The character "*" cannot be used inside or at the end of a sequence of digits. For example "123*" and "12*123" are not allowed.

The parameter is displayed and configurable only if the connection type currently set in the parameter IFTYPE: is "X25BSVC".

It specifies the X.25 called address of the outgoing call.

• if the parameter is set to "NO", the IP port do not make outgoing call.

• if it contains a numeric value, the X.25 called address of the outgoing call will correspond to this value.

The parameter is displayed and configurable only if the connection type currently set in the parameter IFTYPE: is "X25BSVC".

It specifies the maximum idle time interval after which the connection will be teared down:

• if the parameter is set to 0, the BSVC connection stays on.

• if the parameter is set to a value higher than 0, the BSVC connection will be teared down after DT seconds from the last received/sent datagram.

The parameter is displayed and configurable only if the connection type currently set in the parameter IFTYPE: is "X25BSVC".

It sets the minimal time interval to wait between the failed call attempt and the next try.

The parameter is displayed and configurable only if the connection type currently set in the parameter IFTYPE: is "X25BSVC".

It sets the call retry mode:

Value	Meaning
LIN	Time interval to be waited between a call attempt and the next one is constant and configurable through the parameter TB:
INC	Time interval to be waited between a call attempt and the next one is doubled at every try starting from the one set in the parameter IPP_TB:

"#TB"

The parameter is displayed and configurable only if the connection type currently set in the parameter IFTYPE: is "X25BSVC".

It sets the maximum number of call retries:

• if the parameter is set to 0, no calls are placed.

• if the parameter is set to NOMAX, calls are repeated indefinitely.

• if the parameter is set to a value higher than 0, once the this value run over, the BSVC connection will reach the state X25WAITING.

Indicates if NAT is activated on this IPPort, and in which side this IPPort is set.
NAT side information is strictly needed, because is used by NAT to determine the type of IP address conversion that should be made on the INCOMING/OUTGOING IP datagram passing throught this interface.
When NAT is set as INSIDE, means that this IPPort is connected with an INSIDE network.
When NAT is set as OUTSIDE, means that this IPPort is connected with an OUTSIDE network.

In case of NAT port is not active, this parameter is not used by IPRTR.

Used to activate IP address source checking.
When this parameter is activated, IPRTR checks into its internal routing table, if it has a valid routing to reach the sender of the IP datagram being checked.

If a routing to reach the sender host is present in IP routing table, but the outgoing IPPort is different from the IPPort that received the datagram, IPRTR consider source validate check as a failure, and datagram is discarded.

Used to activate/deactivate speed limitation.
Speed limit is a feature that allows IPRTR to reduce the rate of its outgoing datagrams on a specific IPPort.
The reason of this limitation could happen because IPRTR can be used as a gateway into a LAN that allow an Internet access to the hosts present on this LAN. Could happen that IPRTR is connected to the Internet passing through another gateway that is connected with CPX by LAN. This could cause that CPX's IPRTR sends datagrams to the gateway directly connected to the Internet using LAN bandwidth, without considering that the gateway is connected to the Internet using a slower line. In this situation the gateway could fill all its outgoing buffers and discard some datagrams.
With SPEEDLIMIT solution, we can force IPPort to limit it is transfer rate to the bandwidth of the line between gateway connected to the Internet and the ISP, in order to avoid this lost datagrams.
In this way we have a direct control on IPPort's outgoing buffers, and eventually, increase their number as required.

Speed of next interface (KByte/sec). This speed is the bandwidth to reduce the IPPort interface where IPRTR is going to send datagrams.

Current speed of IPPort interface (KByte/sec). This speed is the real bandwidth of the IPPort interface where IPRTR is going to send datagrams.

Indicates the type of encapsulation of the IPPort. Possible values are:

• RAW-IP: datagrams are sent as IP datagrams, without encapsulation.

• FR-IETF: datagrams are encapsulated into standard IETF Frame-Relay (0x03CC).

• FR-CISCO: datagrams are encapsulated into CISCO Frame-Relay protocol.

• HDLC-CISCO: datagrams are encapsulated into CISCO HDLC protocol.

Keep Alive activation. It is used to indicate that Keep-alive feature is active on this IPPort.
This parameter is used by IPRTR only if the encapsulation type is CISCO (FR or HDLC, see ENC: parameter for more details).

CISCO Keep Alive interval. Is the interval to wait after a Keep-Alive requests before submitting next request.
If in this interval, an answer from remote host is received, previous request is considered successfull.
If no answers arrives in this interval, the keep-alive counter for LINK-DOWN is increased. After consecutive KA-LIMIT failures, IPPort state is set to DOWN.

CISCO Max Alive Count value. When IPPort state is UP, it indicates the number of consecutive failure attempts before considering link as DOWN.
This parameter is also used to indicate the number of consecutive successful attempts before considering link as UP when IPPort was previously DOWN.

Primary IPPort number in case of virtual port. When we create an IPPort with IFTYPE:VIRTUAL, we have to indicate also which is the primary IPPort used. This information will be used by IPRTR when has to forward datagrams on the virtual IPPort.

This parameter is used to activade/deactivate routing protocols on this interface.
It is bitmapped and means that it can contain "NO", "RIP", "OSPF" settings and also "RIP,OSPF" together.
When RIP or OSPF protocol will be selected, the specific parameter section will be activated.

It sets the metric associated to IP port according to meant and the rules prescribed by the routing algorithm RIP.

The metric is a general concept related to the IP routing. For its complete understanding refer to the relative banns of the IETF, that is to the RFC (Request for Comment).

Generally in the context of IP routing, it represents the number of hops that the packet must cross in order to reach the destination network, reason for which the corrected minimal value is 1.

To the aim to process a specific strategy of routing preferences, it remains however the possibility to assign to IP ports an arbitrary metric.

Even if it is possible to assign metric 0, such assignment must be ABSOLUTELY avoided because it can cause problems with protocol RIP.

If in the network is present a router on which the protocol RIP is active, whose table contains a routing with metric 0, it is opportune to correct the value or to deactivate the RIP.

It sets the protocol used for sending RIP updates.

Value	Meaning
RIP1	RIP version 1. RIP V1 do not support sub-networks
RIP2B	RIP version 2 through Ethernet broadcast frames
RIP2M	RIP version 2 through Ethernet multicast frames; actually not supported
NO	NO RIP updates are sent

It sets the protocol accepted for receiving RIP updates.

Value	Meaning
RIP1	only RIPV1 updates are accepted
RIP2	only RIPV2 updates are accepted
BOTH	both RIPV1 and RIPV2 updates are accepted
NO	RIP updates eventually accepted are ignored

It sets whether RIP updates have to be sent regularly or only in case of variations.

If the parameter is set to "NO", updates are sent only if the routing table is changed, otherwise they are sent regularly according to the RIP port.

Setting the value "#" indicates that there is no AREA configured. Setting a value between 0.0.0.0 and 255.255.255.255, will make the following options:

• if the specified Area Id value is present into OSPF area table cnfg will save it as a "valid" value.
• if the specified Area Id value is NOT present into OSPF area table cnfg will NOT save it and will output the message "AREA xxx.xxx.xxx.xxx not defined". The setting fails.

Indicates to OSPF protocol which type of network has the interface.

Defines the type of the connected network from the following range:

• BN - broadcast network.
• NBMA - non-broadcast network yet still multi-access.
• PP - point-to-point.
• PMP - Point-to-multipoint networks.
• UPP - unnumbered point-to-point.

The values is cross-checked with IPP_IFTYPE:

IPP_IFTYPE	IPP_OSPF_NETTYPE
LAN	BN, NBMA, PP, PMP
X25PVC	PP, UPP
X25BSVC	PP, UPP
LINK	PP, UPP
PPP	PP, UPP
VIRTUAL	PP, UPP or BN, NBMA, PP, PMP depending on the IFTYPE of the PRI-IPP

Config executes cross-check between iftype and nettype to guarantee that the above table is satisfied.

When changes occur to IFTYPE, the NETTYPE is immediately verified and, if the current NETTYPE value is not acceptable, config will force it to the valid default value, which is:

• BN for LAN, and for VIRTUAL whose PRI-IPP is LAN.
• PP for PPP/LINK/X25xxx, and for VIRTUAL whose PRI-IPP is PPP/LINK/X25xxx.

When two routers attached to a network both attempt to become Designated Router, the one with the highest Interface Priority takes precedence. If there is still a tie, the router with the highest Router ID takes precedence.
A router whose Interface Priority is set to 0 is ineligible to become Designated Router on the attached network. Interface Priority is only configured for interfaces to multi-access networks. A router whose Interface Priority is set to 0 is ineligible to become Designated Router on the attached network.

The cost of sending a data packet on the interface, expressed in the link state metric. This is advertised as the link cost for this interface in the router links (RL LSA) advertisement. The cost of an interface must be greater than zero.

The number of seconds between link state advertisement retransmissions, for adjacencies belonging to this interface. Also used when retransmitting Database Description and Link State Request Packets. This should be well over the expected round-trip delay between any two routers on the attached network. The setting of this value should be conservative or needless retransmissions will result. It will need to be larger on low speed serial lines and virtual links.

The estimated number of seconds it takes to transmit a Link State Update Packet over this interface. Link state advertisements contained in the update packet must have their age incremented by this amount before transmission. This value should take into account the transmission and propagation delays of the interface.

The length of time, in seconds, between the Hello Packets that the router sends on the interface. This value is advertised in the router's Hello Packets. It must be the same for all routers attached to a common network. The smaller the Hello Interval, the faster topological changes will be detected, but more OSPF routing protocol traffic will ensue. Sample value for a X.25 PDN network: 30 seconds. Sample value for a local area network: 10 seconds.

The value of this parameter must be less than a value of the ODEAD interval.
We recommend you to use relation 1 to 6-10 (6-10 HELLO intervals are equal to ODEAD interval).

After ceasing to hear a router's Hello Packets, the number of seconds before its neighbors declare the router down. This is also advertised in the router's Hello Packets in their Router Dead Interval field. This value again must be the same for all routers attached to a common network.

This should be some multiple of the HELLO interval (say 6-10 times).

Maximum OSPF neighbours for the interface. This parameter is visible only for LAN interfaces (IFTYPE:LAN).
This value must be set equal or greater than the sum of neighbours configured in the OSPF neighbours table and the neighbours detected by the Hello protocol.
For interfaces with a "not-LAN" IFTYPE (e.g. IFTYPE:LINK,PPP,X25) OMAX-NEI is forced to 1 and hidden from configuration.

If IFTYPE is changed from LAN to "not-LAN", the OMAX-NEI value will be automatically hidden and internally forced to 1. At the opposite (from not-LAN to LAN), the OMAX-NEI value will be displayed and set with the default value of 5, which can be later changed as desired.

Each neighbour needs about 50 kbytes of the system RAM! Don't set unnecessary high values.

[18:45:45] ABILIS_CPX: D S IPP

PO:900 ------------------------------------------------------------------------
IPRTR  IPP:0  -----------------------------------------------------------------
              IFTYPE:LAN                     LOWPO:155    STATE:LINKREADY      
       IPP:1  -----------------------------------------------------------------
              IFTYPE:LINK     ENC:RAW-IP     LOWPO:1      STATE:LINKREADY
       IPP:2  -----------------------------------------------------------------
              IFTYPE:PPP      ENC:NONE       LOWPO:541    STATE:LINKREADY
       IPP:3  -----------------------------------------------------------------
              IFTYPE:X25BSVC  CDI:2376003115              STATE:X25READY
                              CDO:23760031                                     
       IPP:4  -----------------------------------------------------------------
              IFTYPE:X25PVC   PVC:NONE                    STATE:X25READY
       IPP:5  -----------------------------------------------------------------
              IFTYPE:LINK     ENC:FR-IETF    LOWPO:101    STATE:LINKREADY
       IPP:6  -----------------------------------------------------------------
              IFTYPE:LINK     ENC:FR-CISCO   LOWPO:102    STATE:LINKDOWN
       IPP:7  -----------------------------------------------------------------
              IFTYPE:LINK     ENC:HDLC-CISCO LOWPO:2      STATE:LINKREADY
       IPP:10 -----------------------------------------------------------------
              IFTYPE:VIRTUAL                 P-IPP:0      STATE:LINKREADY
       IPP:63 -----------------------------------------------------------------
              IFTYPE:LINK     ENC:RAW-IP     LOWPO:NONE   STATE:LINKNOTPRESENT

[18:45:45] ABILIS_CPX: D SE IPP

PO:900 ------------------------------------------------------------------------
IPRTR  --- Cleared 025:04:52:02 ago, on 14/04/2000 at 11:12:50 ----------------
       IPP:0  - Verso_router_a_Milano:192.200.121.10/32 -----------------------
       TYPE: LAN
       -----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
       SEG        |0          |0          |CHAR       |67257102   |78524106   |
       DG         |1266162    |1225718    |ICMP       |84         |93         |
       TCP        |513580     |606189     |UDP        |752498     |619436     |
       BRD        |0          |           |CAL        |0          |0          |
       RST        |0          |           |LONG       |0          |           |
       SHORT      |0          |           |LOST-LOOP  |           |0          |
       LOST-BUF   |           |0          |LOST-OTH   |           |0          |
       B-VER      |0          |           |B-ICMP     |0          |           |
       B-LEN      |0          |           |NO-ROUTE   |0          |           |
       B-FCS      |0          |           |UNK-PROT   |0          |           |
       TTL-EXP    |           |0          |LOST-INC-DG|0          |           |
       LOST-ACC   |0          |           |B-FR-HDR   |          0|           |
       SLARP-FRM  |          0|          0|SLARP-CHAR |          0|          0|
       SLARP-KEEP |          0|          0|SLARP-DOWN |          0|           |
       IPP-DOWN   |          1|           |SP-LIM-OVFL|           |          0|
       ------------------------------------------------------------------------
       IPP:1  -----------------------------------------------------------------
       IFTYPE:LINK     ENC:RAW-IP
       -----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
       SEG        |          0|          0|CHAR       |      18927|      11668|
       DG         |        198|        143|ICMP       |          0|          0|
       TCP        |        122|        143|UDP        |         76|          0|
       BRD        |          0|           |CAL        |          0|          0|
       RST        |          0|           |LONG       |          0|          0|
       SHORT      |          0|           |LOST-LOOP  |           |          0|
       LOST-BUF   |           |          0|LOST-OTH   |           |          0|
       B-VER      |          0|           |B-ICMP     |          0|           |
       B-LEN      |          0|           |NO-ROUTE   |          0|           |
       B-FCS      |          0|           |UNK-PROT   |          0|           |
       TTL-EXP    |           |          0|LOST-INC-DG|          0|           |
       LOST-ACC   |          0|           |B-FR-HDR   |          0|           |
       SLARP-FRM  |          0|          0|SLARP-CHAR |          0|          0|
       SLARP-KEEP |          0|          0|SLARP-DOWN |          0|           |
       IPP-DOWN   |          1|           |SP-LIM-OVFL|           |          0|
       ------------------------------------------------------------------------
       IPP:10 -----------------------------------------------------------------
       IFTYPE:VIRTUAL  on P-IPP:0
       ------------------------------------------------------------------------

[18:10:37] ABILIS_CPX: D SE IPP:1

PO:900 ------------------------------------------------------------------------
IPRTR  --- Cleared 000:03:19:20 ago, on 16/06/2000 at 14:51:20 ----------------
       IPP:1  -----------------------------------------------------------------
       IFTYPE:LINK     ENC:RAW-IP
       -----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
       SEG        |          0|          0|CHAR       |      18927|      11668|
       DG         |        198|        143|ICMP       |          0|          0|
       TCP        |        122|        143|UDP        |         76|          0|
       BRD        |          0|           |CAL        |          0|          0|
       RST        |          0|           |LONG       |          0|          0|
       SHORT      |          0|           |LOST-LOOP  |           |          0|
       LOST-BUF   |           |          0|LOST-OTH   |           |          0|
       B-VER      |          0|           |B-ICMP     |          0|           |
       B-LEN      |          0|           |NO-ROUTE   |          0|           |
       B-FCS      |          0|           |UNK-PROT   |          0|           |
       TTL-EXP    |           |          0|LOST-INC-DG|          0|           |
       LOST-ACC   |          0|           |B-FR-HDR   |          0|           |
       SLARP-FRM  |          0|          0|SLARP-CHAR |          0|          0|
       SLARP-KEEP |          0|          0|SLARP-DOWN |          0|           |
       IPP-DOWN   |          1|           |SP-LIM-OVFL|           |          0|
       ------------------------------------------------------------------------

IP port identifier.

Connection type used by the IP port.

Lower level port used by the IP port.

PVC connection identifier.

X.25 called address of the incoming call.

X.25 called address of the outgoing call.

It shows the current value of the IP port. The shown values depend on the connection type used by the IP port.

Driver	States	States	Values shown in:
			System Log	Debug Log	Display LCD
IPRTR (IP port of type "LAN", "LINK", "LINK-FR")	LINKDOWN	The lower level port (LOWPO:) is out of service
	LINKREADY	The lower level port (LOWPO:) is ready
	LINKNOTPRESENT	The lower level port (LOWPO:) is not present or not working
	HALTED	The IP port is halted or blocked owing to a fatal error
	FAILED	The IP port has not been activated because of an initialization error
	ERR	Software error. contact Abilis assistance.
IPRTR (IP port of type "X25BSVC")	X25READY	The Ip port is ready, the BSVC connection is closed
	X25CALLING	The IP port made a call and it is waiting for acknowledgement
	X25CALLED	The IP port received a call but it hadn't sent the acknowledgement
	X25CONNECTED	The IP port has established the BSVC connection and data are exchanged
	X25DELAYING	The IP port is in a wait state because the call try failed
	X25WAITING	The IP port has reached the maximum number of call retries.
	HALTED	The IP port is halted or blocked owing to a fatal error
	FAILED	The IP port has not been activated because of an initialization error
	ERR	Software error. contact Abilis assistance.
IPRTR (IP port of type "X25PVC")	X25READY	The IP port is ready to open the PVC connection.
	X25CONNECTED	The PVC connection is active and the IP port is exchanging data
	HALTED	The IP port is halted or blocked owing to a fatal error
	FAILED	The IP port has not been activated because of an initialization error
	ERR	Software error. contact Abilis assistance

IP port identifier.

Connection type used by the IP port.

The counter SEG (INPUT) is incremented every time the IP port receives a data packet from the Connection Oriented Router (COR). The counter SEG (OUTPUT) is incremented every time the IP port sends a data packet to the Connection Oriented Router (COR).

Segments are obtained by dividing the number of bytes by 64, according to the X.25 standard.

The counter CHAR (INPUT) is incremented every time a datagram is received, while the CHAR (OUTPUT) one every time it is sent.

The counter DG (INPUT) is incremented every time an IP datagram is received, while the DG (OUTPUT) one every time it is sent.

The counter ICMP (INPUT) is incremented every time an ICMP datagram is received, while the ICMP (OUTPUT) one every time it is sent.

The counter TCP (INPUT) is incremented every time an TCP datagram is received, while the TCP (OUTPUT) one every time it is sent.

The counter UDP (INPUT) is incremented every time an UDP datagram is received, while the UDP (OUTPUT) one every time it is sent.

The counter BRD (INPUT) shows the number of broadcasts received.

The counter CAL (INPUT) is incremented every time a Call Request X.25 is received, while the CAL (OUTPUT) one every time it is sent.

The counter RST (INPUT) is incremented every time a Reset X.25 is received.

The counter LONG (INPUT) is incremented every time a too long IP datagram is received.

The counter SHORT (INPUT) is incremented every time a too short IP datagram is received.

The counter LOST-LOOP (OUTPUT) is incremented every time a datagram is discarded because of a routing loop, probably caused by a bad routing.

Within IP networks, a datagram can't be rout to the port where it came from.

The counter LOST-BUT (OUTPUT) is incremented every time a datagram must be discarded because there is no free buffer.

The counter LOST-OTH (OUTPUT) is incremented every time a datagram must be discarded because of unknown causes. Typically, it happens when buffers are forcedly emptied by the execution of the command INIT IPP or INIT IPR

The counter B-VER (INPUT) is incremented every time a datagram, whose version field is bad, is received.

The counter B-ICMP (INPUT) is incremented every time is received an unknown ICMP datagram or the Checksum procedure fails.

The counter B-LEN (INPUT) is incremented every time is received a datagram with a bad length.

The counter NO-ROUTE (INPUT) is incremented every time a datagram is received, but there is no routing associated to its destination address.

The counter B-FCS (INPUT) is incremented every time a datagram is received but the Checksum verifying procedure fails.

The counter UNK-PROT (INPUT) is incremented every time a datagram is received, but its protocol is unknown.

The counter TTL-EXP (OUTPUT) is incremented every time a datagram is discarded because its TTL field expired, that is it reached the value "0".

The TTL field value is incremented by 1 before routing the datagram.

The counter LOST-INC-DG (INPUT) is incremented every time a datagram fragment is discarded because it is not possible to compose the datagram.

This statistic is not related to IP fragmentation (RFC 791).
This fragmentation is activated using FRAG: and FRAGSIZE: parameters.

The counter LOST-ACC (INPUT) is incremented every time a datagram is discarded because it doesn't match any of the IP access list currently configured or because it matches a "denied access list".

It is incremented in 2 cases:
- When incoming Frame-Relay header is not 0x03B1 (FRF12 fragmentation); - When incoming Frame-Relay header is not 0x03CC (complete frame);

The counter SLARP-FRM (INPUT) is incremented every time an IP datagram encapsulated into a CISCO SLARP frame is received, while the SLARP-FRM (OUTPUT) one every time it is sent: it is incremented by 1 for every frame received/sent.

The counter SLARP-CHR (INPUT) is incremented every time an IP datagram encapsulated into a CISCO SLARP frame is received, while the SLARP-CHR (OUTPUT) one every time it is sent: in this case the statistic will be increased by the number of BYTEs that the frames contains.

The counter SLARP-KEEP (INPUT) is incremented every time a CISCO SLARP keep-alive frame is received, while the SLARP-KEEP (OUTPUT) one every time it is sent: it is incremented by 1 for every frame received/sent.

The counter SLARP-DOWN is incremented every time KEEPALIVE has detected a DOWN condition.

The counter IPP-DOWN is incremented every time IPPort global state changed from UP to DOWN. One of the possible reason can could be that the lower layer went DOWN.

SP-LIM-OVFL indicates the number of time calculation for speed reduction that has overflown the time limit.

This value should stay 0, value > 0 may indicate sw errors, please contact Abilis assistance.