02-08-2010 10:02 AM - edited 03-04-2019 07:26 AM
any one have an Idea why DS3 will be acting this way
Thanks
Feb 1 12:40:59.560: %ENTITY_ALARM-6-INFO: ASSERT MAJOR Se4/0 Receiver has remote alarm
Feb 1 12:41:01.560: %LINK-3-UPDOWN: Interface Serial4/0, changed state to down
Feb 1 12:41:01.560: %ENTITY_ALARM-6-INFO: ASSERT MAJOR Se4/0 Physical Port Link Down
Feb 1 12:41:01.560: %ENTITY_ALARM-6-INFO: CLEAR MAJOR Se4/0 Receiver has remote alarm
Feb 1 12:41:01.560: %ENTITY_ALARM-6-INFO: CLEAR MAJOR Se4/0 Physical Port Link Down
02-08-2010 10:58 AM
Because the remote is sending remote alarm. So check the remote to know why.
02-08-2010 12:14 PM
the only thing that I c different is that the remote side on the int level there is no keepalive, everyting else is ok.. could it be the reason why it bounsing ?
02-08-2010 12:46 PM
No.
However you should have keepalive unless proven otherwise.
02-09-2010 07:51 PM
Call the ISP to find out why the circuit is bouncing.
I would also check the interface for any errors, it could be taking a lot of errors and causing it to go down, however, in the logs it shows remote side so chances are it is an issue with the ISP side. If they push back as them to install a DS3 monitor inline. This works much like a packet capture.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: