No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade
Knowledge Base

AR1833E Negotiates with Opposite Partner's Device G.SHDSL Link

Publication Date:  2012-07-27  |   Views:  114  |   Downloads:  0  |   Author:  Ling Chuan  |   Document ID:  EKB0000262214

Contents

Issue Description

AR1833E device and upstream partner C device establish EBGP neighbor relation through G.SHDSL link. Restart AR1833E and it is found that the interface state is up, but it cannot ping opposite device and BGP neighbor cannot be built.

Alarm Information

Null

Handling Process

Execute the following command under G.SHDSL interface:
[tp-cpe-hua1833-B5-19-Atm2/0]un activate
[tp-cpe-hua1833-B5-19-Atm2/0]activate
or:
[tp-cpe-hua1833-B5-19-Atm2/0]shut
[tp-cpe-hua1833-B5-19-Atm2/0]un shut
The device will re-negotiate G.SHDSL link with the peer.
The link is activated and established. BGP neighbor is established.

Root Cause

After AR1833Erestarts, it detects that the interface state of opposite device is up. It does not negotiate and the sate is up. Actually the link is not set up. It is required that the command line should distribute re-negotiate G.SHDSL link to activate the link again.

Suggestions

For the connection with other enterprises, there is difference on the realization. It is required to check the state of the device to ensure that the configuration can be correctly distributed and the service can be reachable.