There Is Lof Or Ral Alarms Sometimes Of E1 Interface; Not All Devices In A Network Can Be Network Managed; Device Cannot Be Configured Through Console; Memory Information Loss - Raisecom RC3000 User Manual

www.raisecom.com
If these are not the reasons, please contact us for technical support.

7.5 There is LOF or RAL alarms sometimes of E1 interface

Generally it is caused by clock asynchronous. In practice application, all RC3000s in one network
will synchronous with one clock (that is to say one master clock and several slave clocks), when all
devices synchronous with a nonexistent clock or trace clock each other, this phenomenon will
happen. Please check the clock configuration.
If these are not the reasons, please contact us for technical support.

7.6 Not all devices in a network can be network managed

If not all devices in a network can be managed, please check the followings:
a.
b.
c.
d.
e.
f.
If these are not the reasons why you cannot manage the device, please contact us for technical
support.

7.7 Device cannot be configured through CONSOLE

If the device cannot be configured through CONSOLE, please check the followings:
a.
b.
c.
d.
e.
f.
If these are not the reasons why you cannot configure the device, please contact us for technical
support.

7.8 Memory information loss

If the information saved in memory lost after RC3000 running for some time, check whether
EEPROM can save data normally, if not, please contact us for technical support.
Check the cables connected to all devices first.
Check the network topology.
Check the DIP-switches of device that cannot be managed, remember to set first bit
(CONSOLE control bit) OFF.
Check the network management configuration, make sure that time slot for network
management of all devices is the same (occupy time slot 0 or 1) and number of network
management channels is same with that of E1 direction.
When manage two RC3000-OPT devices, the network management topology should be
single E1 direction, otherwise you may not manage the remote device
Check the configuration of device ID and Baud rate, in a RC3000 network all devices must
have different ID and same baud rate, and when assistant network management channel is
used, the Baud rate must be 2400Bps.
Check that proper cable is used to connect to CONSOLE.
Check the configuration of Hyper Terminal (refer to appendix A: How to use Hyper Terminal)
Check the DIP-switches and see if the Console control bit ON.
In Hyper Terminal press <M> to display the menu if <ENTER> key is not effective.
When you press the <ENTER>, light of serial interface Tx will lighten and this indicates that
RC3000 receives data normally. Otherwise check other configuration.
Check serial interface
User Manual
47