Network Bridge Not Passing Commands

[MarkHenry]

Have recently been running into the same issue on various site with using 5500NB.

Bridges just stop passing commands to the adjacent network. These sites are all < 1 year.

When connecting to the network, Toolkit has the ability to communicate through the bridge to the other network.

Scans as normal but when logging commands on diagnostic utility they are not being passed through.

Opening the bridge from the network, the GUI it shows that the send to adjacent network enabled.

Power cycle doesn't rectify but by un-ticking send to adjacent network then saving and then re-tick and save.

Once that done unit then bridge starts operating as expected.

[DarrenMullighan]

Hi Mark,

Apologies for the delay, I have been off work for the past 3 weeks.

Based off your assessment of the bridge, my initial thoughts are that there is something wrong with the internals of the unit.

It is odd to me that you can scan the adjacent network over the bridge (assuming reliably and that the data comes through in a consistent manner), but that commands do not traverse the bridge over a longer period of time after reenabling the send commands to adjacent network option.

Whats the period of time roughly before the bridges fail to transfer commands?

[sesa59140_bridg]

Hi Mark,

In addition to Darren's reply, Does the NB continue to work properly after your re-programme sequence or does it fail again?

Cheers

Steve Dunn

[sesa59140_bridg]

Hi Mark,

Another thought, Does this Bridge return to bad behavior after a Power cycle?

Cheers

Steve Dunn

[MarkHenry]

Hi Darren & Steve,

This issue has occurred at multiple sites. The bridge continues to operate for months normally and then stops after re-ticking the send to adjacent network. One one site it happened 3 times. We have replaced this bridge now.

When failed we are able to open the network through the bridge correctly and scan, only the bridge doesn't pass commands onto the other network. Toolkit shows that the send to adjacent network is ticked when opening from the network.

[MarkHenry]

Hi Steve,

once re-ticked, the unit works correctly after restore from a power cycle. Disconnected both sides of the bridge to power cycle to confirm operation.

[PeterLags]

is local SAL enabled on the device you are connecting to the network and all PCI type devices? inc NAC/SHAC, Device Formally known as WISER, enabled devices, CNI, PCI ....

if any device has this disabled it causes bridges to stop passing commands originating from that device as the bridge believes the cmd has already passed through one network.

toolkit originated commands will still work however as they are directed commands with the network routing included

- I believe you need the diagnostic utility to check and enable this