The IEEE BRIDGE port

Revised for CPX 4.7.0.

Configuration of the BRIDGE port
Statistics of the BRIDGE port
SNMP TRAPS generated for BRIDGE ports

BRIDGE is a module that introduces bridging functionalities in Abilis CPX. In this version it allows bridging of IEEE 802.3 frames only and only between pre-configured MAC addresses (future versions may allow bridging of any Ethernet types as well as other LAN frames (e.g. 802.5). Furthermore MAC addresses self-learning and spanning tree protocol could be added.

The main goal of the Abilis CPX BRIDGE driver is to provide a quick and reliable solution for customers with simple network topology, typically a star topology, who need to transport SNA 802.2/802.3 traffic through an IP backbone, with an alternative method to the much more complicated DLSw.

The Abilis CPX BRIDGE driver is however not limited to an IP backbone, it may use ANY backbone protocol supported in Abilis CPX through the ML/MLM drivers.
Three formats of the bridged packets can be selected:

Abilis proprietary with a low overhead fragmentation technique
ANSI, as per T1.618a
ANSI with fragmentation, as per T1.618a

Bridging is not a complete replacement for DLSw, but under some circumstances it can fully satisfy user needs:

The traffic is only LAN-to-LAN (in cpx limited to Ethernet 802.3 LANs)
The traffic, considering the acknowledgments overhead, remains "reasonably small". This has an impact on performances but also on "costs" if the transport network is paid by the volume of exchanged data.
The transport network is reliable (small packet loss) and offers low delays, usually smaller than SNA IEEE 802.2 protocol timeouts.
The topology of the SNA connections is of star type, i.e. from branch offices to central site. Although mesh topology is still possible, the deployment of large configurations will be cumbersome and error prone because of the huge amount of links that will be configured and the possibility of loops in the paths.

Configuration of the BRIDGE port

The BRIDGE port is labelled within the Abilis CPX with the acronym "BRIDGE" and it is provided with the parameters described in this section.

Here is an example on how to show the BRIDGE parameters. Shown values are examples.

[15:42:35] ABILIS_CPX:D P PO:BRIDGE

PO:170 - Not Saved (SAVE CONF), Not Refreshed (INIT) --------------------------
BRIDGE ------------------------------------------------------------------------
       LOG:ALL+E     ACT:YES    LOWPO:58           MODE:STAR    LAN-PROT:IEEE
       L-MAC:*                                     M-MAC:#
       SAP:*                                       RXPADREMOVE:YES
       - Links ----------------------------------------------------------------
       Lnk:1   ST:RUNNING   LOWPO:NONE       ENC:ABILIS     FRAGSIZE:800
               RXQUEUE:10   TXQUEUE:30
               R-MAC:
       ------------------------------------------------------------------------
       Lnk:3   ST:RUNNING   LOWPO:503        ENC:ABILIS     FRAGSIZE:800
               RXQUEUE:10   TXQUEUE:30
               R-MAC:
       ------------------------------------------------------------------------
       Lnk:4   ST:NEW       LOWPO:504        ENC:ABILIS     FRAGSIZE:800
               RXQUEUE:10   TXQUEUE:30
               R-MAC: 00-40-F4-0A-AF-35  00-C0-CA-14-3D-8E  02-01-01-01-01-04  
                      02-01-01-01-01-FF  
       ------------------------------------------------------------------------

To activate changes made on the parameters displayed by low case characters, it is needed to restart the system; on the contrary for activating changes made on high case parameters it is enough to execute the initialization command INIT PO:xxx, where "xxx" is the BRIDGE port number.

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 and/or restarted.

There is also the possibility to restart the port. Restarting a port means to reinitialize it like at start-up.
When a port is restarted, ALL the parameters are reloaded. In order to restart the BRIDGE port, the command is R PO:xxx, where "xxx" is the BRIDGE port number.

Detail of the BRIDGE port parameter

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:

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.

ACT:	BRIDGE activation
NO	NO, YES

It activates the BRIDGE functionalities above mentioned. If the parameter is set to "NO", even if the BRIDGE port is configured and active, it won't carry out any functionality within the system.

LOWPO:	Identifier of the Abilis CPX lower ETH100 port
NONE	NONE, TYPE-XXX

It sets the Abilis CPX lower level port. It can only be an ETH100 port.

Value "NONE" isolates the BRIDGE port from CPX lower ethernet-100 port.

MODE:	Behaviour of frames exchange among LAN and Links
STAR	STAR, MESH

Indicates which is the behaviour used by BRIDGE upon receiving frames:

STAR: BRIDGE port works in "star" mode, that is data traffic can take place only between LAN and LinkS, and not between LINK and LINK.
Broadcasts received from a link are sent only to the LAN, while broadcasts received from LAN are "copied" to all the links.
MESH: BRIDGE port works in "mesh" mode, that is data traffic can take place between LAN and LinkS, and also between LINK and LINK.
Broadcasts received from LAN are "copied" to all the links, as in "star" mode, but broadcasts received from a link are sent to the LAN and to all the other LINKS.

LAN-PROT:	Bridging protocol frames
IEEE	IEEE

Selects if bridging is allowed only for IEEE frames or for ALL Ethernet frames types.
Currently BRIDGE allows traffic on only IEEE frames.

L-MAC:	Local MAC addresses accepted
*	#, *, ListName

It is used as a filter to determine which frames can be accepted from ETH100 port.

* BRIDGE accepts frames from ETH100 from ANY source MAC addresses.
# BRIDGE doesn't accept any frame because no list is configured.
listname BRIDGE accepts frames from ETH100 only if the source MAC address is present in the <listname> list of MAC addresses. BRIDGE increment a counter for frames that are discarded because of this filter (L-MAC-DENY).

M-MAC:	Multicast MAC addresses
#	#, ListName

This list is used to indicate to ETH100 which multicast can be received by BRIDGE.

# BRIDGE doesn't accept any MULTICAST frame because list is not configured.
listname BRIDGE accepts MULTICAST frames from ETH100 only if the source MAC address is present in the <listname> list of MULTICAST MAC addresses.

SAP:	Filter on SAP
*	#, *, 00..FF, 'ListName'

This is a filter in order to allow specific SAP value. Filter as applied for both source and destination SAP.

* BRIDGE accepts frames with ANY SAP value.
# BRIDGE doesn't accept any frame because no SAP list nor SAP value is configured.
value BRIDGE accept only frames with SAP <value> configured.
listname BRIDGE accepts frames only if the SAP is present in the <listname> list of SAP values.

RXPADREMOVE:	Remove padding in frames received from LAN
*	NO, YES

This parameter allow to activate/deactivate padding removal in frames received from LAN.

Lnk:	Link identifier
	1 - 256

It identifies the LINK where the parameters refers to.

ST:	Link State
DELETED	NEW, DELETED, RUNNING

Status of the LINK configuration.

NEW: LINK is added in BRIDGE configuration, but it is not yet operative (BRIDGE needs to be restarted).

DELETED: LINK is removed from BRIDGE configuration, but it is still present into BRIDGE port, even if no more used (BRIDGE needs to be restarted to completely remove it from memory).

RUNNING: LINK is present in configuration and working. This is the only status where BRIDGE can send/receive datagrams on this LINK.

LOWPO:	Lower link port
NONE	NONE, TYPE-XXX

Identifier of the lower Abilis CPX port used by the link.
It defines the Link port of the lower level, which can only be MLM or ML type.
If no Link port is required, the value "NONE" must be set.

ENC:	Encapsulation method
ABILIS	ABILIS, ANSI, ANSI-FRAG

Indicates the type of encapsulation performed on the LINK port.

ABILIS Abilis proprietary protocol is used, which have fragmentation capabilities always active.
ANSI Ethernet frame is encapsulated according to ANSI T1.617a annex F,
ANSI-FRAG Ethernet frame is encapsulated according to ANSI T1.617a annex F, multiprotocol encapsulation over frame relay, with fragmentation specified in chapter F.5.3, without the T.618 address.

FRAGSIZE:	Maximum length of fragments
800	32 - 1518

Defines the length of the sent fragment, for those encapsulations that provide fragmentation. The parameter regulates only "sent frames", while BRIDGE must always be ready to receive fragments of any size.

RXQUEUE:	Receive queue size
10 - 255	10

Defines the size, in kbytes, of the receive queue of the link.
Frames received from the link and destined to the lan are "parked" in this queue.
Frame received from the link and destined to another link (MESH mode) are directly put into the link TX queue, without transiting through the link rx buffers.

TXQUEUE:	Transmit queue size
10 - 255	30

Defines the size, in kbytes, of the transmit queue of the link.
Frames destined to the link are "parked" in this queue, regardless is they are received from LAN or from another LINK.

R-MAC:	Remote MAC address
<empty>	00-00-00-00-00-00 - FF-FF-FF-FF-FF-FF

List of remote MACs present to the other side of the link.
This information is very important because is used to indicate to ETH100 port which MAC addresses are allowed to be received.

Statistics of the BRIDGE port

Example on how to show state and statistics of BRIDGE ports through the command D S:

[12:35:43] ABILIS_CPX: D S PO:BRIDGE

PO:170 ------------------------------------------------------------------------
BRIDGE STATE:READY               LINKs:SOME-READY          DOWN:0
       ------------------------------------------------------------------------
       Lan:1     ST:READY        DOWN:0
       Lnk:1     ST:DOWN1        DOWN:0
       Lnk:2     ST:DOWN1        DOWN:0
       Lnk:3     ST:READY        DOWN:0
       -----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
       CHR        |          0|          0|FRM        |          0|          0|
       ERROR      |          0|          0|
       ------------------------------------------------------------------------

Example on how to show extended statistics of BRIDGE ports through the command D SE:

[14:22:12] ABILIS_CPX: D SE PO:BRIDGE

PO:170 ------------------------------------------------------------------------
BRIDGE --- Cleared 000:00:00:00 ago, on 20/07/2004 at 14:22:17 ----------------
       - Lan   1 -|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
       CHR        |          0|          0|FRM        |          0|          0|
       LONG       |          0|           |SHORT      |          0|           |
       L-MAC-DENY |          0|           |R-MAC-DENY |          0|           |
       SAP-DENY   |          0|           |NODEST     |          0|           |
       - Lnk   1 -|-----------|-----------|-----------|-----------|-----------|
       CHR        |          0|          0|FRM        |          0|          0|
       LONG       |          0|           |SHORT      |          0|           |
       L-MAC-DENY |          0|           |R-MAC-DENY |          0|           |
       SAP-DENY   |          0|           |NODEST     |          0|           |
       NOBUF      |          0|          0|BAD-FMT    |          0|           |
       BAD-FRAG   |          0|           |
       - Lnk   2 -|-----------|-----------|-----------|-----------|-----------|
       CHR        |          0|          0|FRM        |          0|          0|
       LONG       |          0|           |SHORT      |          0|           |
       L-MAC-DENY |          0|           |R-MAC-DENY |          0|           |
       SAP-DENY   |          0|           |NODEST     |          0|           |
       NOBUF      |          0|          0|BAD-FMT    |          0|           |
       BAD-FRAG   |          0|           |
       - Lnk   3 -|-----------|-----------|-----------|-----------|-----------|
       CHR        |          0|          0|FRM        |          0|          0|
       LONG       |          0|           |SHORT      |          0|           |
       L-MAC-DENY |          0|           |R-MAC-DENY |          0|           |
       SAP-DENY   |          0|           |NODEST     |          0|           |
       NOBUF      |          0|          0|BAD-FMT    |          0|           |
       BAD-FRAG   |          0|           |
       ------------------------------------------------------------------------

The information "Cleared DDD:HH:MM:SS ago, at DD/MM/YYYY HH:MM:SS", referred by the extended statistics, shows the time interval elapsesed 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").

Detail of statistics of BRIDGE ports

STATE:	Current state of the BRIDGE port
	DOWN, READY, ERR

It shows the current state of the BRIDGE port.

Driver	States	Meaning	Values shown in:
Driver	States	Meaning	System Log	Debug Log	Display LCD
BRIDGE	DOWN	The BRIDGE port driver is down.	dn
	READY	The BRIDGE port driver is ready.	RD
	ERR	Software error, contact Abilis assistance	NA

LINKs:	Current global state of links of BRIDGE port
	ALL-DOWN, ALL-READY, SOME-READY, NO-LINKS

Indicates the current global state of links of BRIDGE port drvers.

Driver	States	Meaning	Values shown in:
Driver	States	Meaning	System Log	Debug Log	Display LCD
BRIDGE Links	ALL-DOWN	All links of the BRIDGE port driver are down.	dn
	ALL-READY	All links of the BRIDGE port driver are ready.	rd
	SOME-READY	Some links of the BRIDGE port driver are ready.	RD
	NO-LINKs	No links are avaiable for the BRIDGE port driver.	np
	ERR	Software error, contact Abilis assistance	NA

DOWN:	Number of times that BRIDGE went into DOWN state
	0 - 4294967295

This counter shows the total number of times that BRIDGE went into DOWN state from a READY state.

Lan:	LAN identifier
	1 - 256

Identifier used to specify to which LAN of the BRIDGE port driver, diagnostic informations refer to.

ST:	Current LAN state
	NONE, LINK-NP, LINK-ERR, DOWN1, READY, UNDEFINED

Indicates th current sate of a specific LAN of the BRIDGE port driver.

Driver	States	Meaning	Values shown in:
Driver	States	Meaning	System Log	Debug Log	Display LCD
BRIDGE Lan	NONE	Link doesn't exists.	dn
	LINK-NP	Down state: unable to establish the connection.	np
	LINK-ERR	Down state: unable to establish the connection.	dn
	DOWN1	Down state: lower layer is DOWN.	DN
	READY	Channel is ready.	RD
	UNDEFINED	State undefined.	dn
	ERR	Software error, contact Abilis assistance	NA

DOWN:	Number of times that a LAN went into DOWN1 state
	0 - 4294967295

This counter shows the total number of times that a LAN of the BRIDGE port driver went into DOWN1 state.

Lnk:	Link identifier
	1 - 256

Identifier used to specify to which Link of the BRIDGE port driver, diagnostic informations refer to.

ST:	Current Link state
	NONE, LINK-NP, LINK-ERR, DOWN1, READY, UNDEFINED

Indicates th current sate of a specific Link of the BRIDGE port driver.

Driver	States	Meaning	Values shown in:
Driver	States	Meaning	System Log	Debug Log	Display LCD
BRIDGE Link	NONE	Link doesn't exists.	dn
	LINK-NP	Down state: unable to establish the connection.	np
	LINK-ERR	Down state: unable to establish the connection.	dn
	DOWN1	Down state: lower layer is DOWN.	DN
	READY	Channel is ready.	RD
	UNDEFINED	State undefined.	dn
	ERR	Software error, contact Abilis assistance	NA

DOWN:	Number of times that a Link went into DOWN1 state
	0 - 4294967295

This counter shows the total number of times that a Link of the BRIDGE port driver went into DOWN1 state.

CHR:	Number of received/sent characters
	0 - 4294967295

The counter CHR (INPUT) is incremented every time a frame is received from every LAN and Link.
The counter CHR (OUTPUT) is incremented every time a frame is sent to every LAN and Link.
This counter is the sum of the CHR specific statistics of LAN and of the CHR specific statistics of Link present into BRIDGE.
The counter is incremented for every frame by the amount of characters present into it.

FRM:	Number of received/sent frame
	0 - 4294967295

The counter FRM (INPUT) is incremented every time a frame is received from every LAN and Link.
The counter FRM (OUTPUT) is incremented every time a frame is sent to every LAN and Link.
This counter is the sum of the FRM specific statistics of LAN and of the FRM specific statistics of Link present into BRIDGE.

ERROR:	Number of errors received/sent
	0 - 4294967295

This counter has a sum of all the errors counted into specific statistics for LAN and Link.

Detail of statistics of LAN of BRIDGE ports

CHR	Number of received/sent characters
	0 - 4294967295

The counter CHR (INPUT) is incremented every time a frame is received from the specific LAN.
The counter CHR (OUTPUT) is incremented every time a frame is sent to the specific LAN.
The counter is incremented for every frame by the amount of characters present into it.

FRM	Number of received/sent frames
	0 - 4294967295

The counter FRM (INPUT) is incremented every time a frame is received from the specific LAN.
The counter FRM (OUTPUT) is incremented every time a frame is sent to the specific LAN.

LONG	Number of frames received and lost due to length
	0 - 4294967295

This counter is incremented for every frame received and lost due to length greater than allowed size.

SHORT	Number of frames received and lost due to length
	0 - 4294967295

This counter is incremented for every frame received and lost due to length smalled than minimum size required to analyse the frame.

L-MAC-DENY	Number of frames discarded to LOCAL MAC filter
	0 - 4294967295

This counter is incremented for every frame received from ETH100 port with a MAC address not present (for more details see L-MAC:).

R-MAC-DENY	Number of frames LOST due to MAC filtering
	0 - 4294967295

This counter is incremented for every frame received from a LAN and its source MAC address is not present into R-MAC: list.
This is a filter used to avoid traffic possible only in a single direction.

SAP-DENY	Number of frames LOST due to SAP filter
	0 - 4294967295

This counter is incremented every time a frame received from LAN contains a SAP value that is not allowed to be received due to SAP filter (for more details see SAP:).

NODEST	Number of frames LOST due to a MAC address destination unknown
	0 - 4294967295

This counter is incremented every time a frame is received from LAN and BRIDGE has no information about where to send that frame.

Detail of statistics of Link of BRIDGE ports

CHR	Number of received/sent characters
	0 - 4294967295

The counter CHR (INPUT) is incremented every time a frame is received from the specific Link.
The counter CHR (OUTPUT) is incremented every time a frame is sent to the specific Link.
The counter is incremented for every frame by the amount of characters present into it.

FRM	Number of received/sent frames
	0 - 4294967295

The counter FRM (INPUT) is incremented every time a frame is received from the specific Link.
The counter FRM (OUTPUT) is incremented every time a frame is sent to the specific Link.

LONG	Number of frames received and lost due to length
	0 - 4294967295

This counter is incremented for every frame received and lost due to length greater than allowed size.

SHORT	Number of frames received and lost due to length
	0 - 4294967295

This counter is incremented for every frame received and lost due to length smalled than minimum size required to analyse the frame.

L-MAC-DENY	Number of frames discarded to LOCAL MAC filter
	0 - 4294967295

This counter is incremented for every frame received from ETH100 port with a MAC address not present (for more details see L-MAC:).

R-MAC-DENY	Number of frames LOST due to MAC filtering
	0 - 4294967295

This counter is incremented for every frame received from a Link and its source MAC address is not present into R-MAC: list.
This is a filter used to avoid traffic possible only in a single direction.

SAP-DENY	Number of frames LOST due to SAP filter
	0 - 4294967295

This counter is incremented every time a frame received from Link contains a SAP value that is not allowed to be received due to SAP filter (for more details see SAP:).

NODEST	Number of frames LOST due to a MAC address destination unknown
	0 - 4294967295

This counter is incremented every time a frame is received from Link and BRIDGE has no information about where to send that frame.

NOBUF:	Frames lost due to a receiving/sending queue full
	0 - 4294967295

This counter is incremented every time the use of queues is required and no space is available to store frames.
The counter NOBUF (INPUT) is incremented every time a frame is received from a Link and receiving queue is full.
The counter NOBUF (OUTPUT) is incremented every time a frame is sent to a Link and sending queue is full.

BAD-FMT:	Frames lost due to a frame bad format
	0 - 4294967295

This counter is incremented every time the frame format is different from expected.
It could be due also to a misconfiguration of ENC protocols between 2 links.

BAD-FRAG:	Error during fragmentation/reassemply phase
	0 - 4294967295

The counter BAD-FRAG (INPUT) is incremented every time there is a missing fragment when reassembly whole datagram.
The counter BAD-FRAG (OUTPUT) is incremented every time is needed a frame fragmentation and ENC: parameter doesn't allow it.

SNMP TRAPS generated for BRIDGE ports

The SNMP Agent of Abilis CPX is able to generate traps owing to meaningful state changes pertinent either to the BRIDGE port itself and to LANs and to Links of the BRIDGE port driver.

SNMP traps generated for global state changes pertinent to all Links of the BRIDGE port

The traps listed below are generated when at least the "T" options are set in the LOG: parameter, corresponding to the basic SNMP traps generation functionality provided for BRIDGE ports.

Trap own code	Mnemonic of the trap	SNMP variables shown in the trap	Description
66	cxTrapBdgDown	cxPortIndex, cxPortType, cxBdgDiagState, cxBdgDiagLinksState, sysUpTime	The SNMP Agent of the Abilis CPX generates this kind of trap every time the BRIDGE port currently running goes to DOWN state.
67	cxTrapBdgReady	cxPortIndex, cxPortType, cxBdgDiagState, cxBdgDiagLinksState, sysUpTime	The SNMP Agent of the Abilis CPX generates this kind of trap every time the BRIDGE port currently running goes to READY state.
68	cxTrapBdgAllLinksDown	cxPortIndex, cxPortType, cxBdgDiagState, cxBdgDiagLinksState, sysUpTime	The SNMP Agent of the Abilis CPX generates this kind of trap every time all links of the BRIDGE port currently running are in DOWN state.

SNMP traps generated for state changes pertinent to LANs of the BRIDGE port

The traps listed below are generated when at least the "T" options are set in the LOG: parameter, corresponding to the basic SNMP traps generation functionality provided for BRIDGE ports.

Trap own code	Mnemonic of the trap	SNMP variables shown in the trap	Description
69	cxTrapBdgLanDown	cxPortIndex, cxPortType, cxBdgDiagLanIndex, cxBdgDiagLanState, sysUpTime	The SNMP Agent of the Abilis CPX generates this kind of trap every time the LAN of the BRIDGE port currently running goes to DOWN state.
70	cxTrapBdgLanReady	cxPortIndex, cxPortType, cxBdgDiagLanIndex, cxBdgDiagLanState, sysUpTime	The SNMP Agent of the Abilis CPX generates this kind of trap every time the LAN of the BRIDGE port currently running goes to READY state.

SNMP traps generated for a single Link of the BRIDGE port

The traps listed below are generated only when the "T+E" options are set in the LOG: parameter, i.e. it is required an extension of the basic SNMP traps generation functionality.

Trap own code	Mnemonic of the trap	SNMP variables shown in the trap	Description
71	cxTrapBdgLinkDown	cxPortIndex, cxPortType, cxBdgDiagLinkIndex, cxBdgDiagLinkState, sysUpTime	The SNMP Agent of the Abilis CPX generates this kind of trap every time a LINK of the BRIDGE port currently running goes to DOWN state.
72	cxTrapBdgLinkReady	cxPortIndex, cxPortType, cxBdgDiagLinkIndex, cxBdgDiagLinkState, sysUpTime	The SNMP Agent of the Abilis CPX generates this kind of trap every time a LINK of the BRIDGE port currently running goes to READY state.

Detail of the SNMP variables shown in the BRIDGE port traps

cxPortIndex	BRIDGE port which the SNMP trap refers to
	0 - 999

This variable stores the CPX port number, which the SNMP trap refers to.

cxPortType	Type and description of the BRIDGE port, which the trap refers to
	type - description

This variable shows either the port type which the trap refers to (in this case BRIDGE) and the description eventually associated to it.

cxBdgDiagState	Current state of the BRIDGE port driver, which the trap refers to
	down(0), ready(1)

This variable shows the current state of the BRIDGE 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 BRIDGE driver
down(0)	DOWN
ready(1)	READY

cxBdgDiagLinksState	Current global state for Links of BRIDGE port driver, which the trap refers to
	all_down(0), some_ready(1), all_ready(2), no_links(3)

This variable shows the current global state for Links of BRIDGE 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 BRIDGE driver
all_down(0)	ALL-DOWN
some_ready(1)	SOME-READY
all_ready(2)	ALL-READY
no_links(3)	NO-LINKs

cxBdgDiagLanIndex	Index of the BRIDGE port LAN, which the trap refers to
	1 - 256

This variable shows the index of the BRIDGE port LAN which the trap refers to.

cxBdgDiagLanState	Current state of the BRIDGE port LAN, which the trap refers to
	none(0), link_not_present(1), link_error(2), down1(3), ready(4), undefined(5)

This variable shows the current state of the LAN of the BRIDGE port, 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 LAN
none(0)	NONE
link_not_present(1)	LINK-NP
link_error(2)	LINK-ERR
down1(3)	DOWN1
ready(4)	READY
undefined(5)	UNDEFINED

cxBdgDiagLinkIndex	Index of the BRIDGE port LINK, which the trap refers to
	1 - 256

This variable shows the index of the BRIDGE port LINK which the trap refers to.

cxBdgDiagLinkState	Current state of the BRIDGE port LINK, which the trap refers to
	none(0), link_not_present(1), link_error(2), down1(3), ready(4), undefined(5)

This variable shows the current state of the Link of the BRIDGE port, 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 Link
none(0)	NONE
link_not_present(1)	LINK-NP
link_error(2)	LINK-ERR
down1(3)	DOWN1
ready(4)	READY
undefined(5)	UNDEFINED

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.

Print this page