Logging in to the peer-end controller by using the peer-end heartbeat IP address

0

Logging in to the peer-end controller by using the peer-end heartbeat IP address:
1. Querying the heartbeat IP address:
Log in to the CLI in storage debug mode and enter ifconfig bond0. Note: If the heartbeat IP address remains unchanged, the default IP address of controller A is 192.168.2.10 and that of controller B is 192.168.2.11.
2. Logging in to the peer-end background using the peer-end heartbeat IP address:
Log in to the CLI in local debug mode, enter ssh admin@peer-end IP address, and enter the peer-end user name and password. Once the information is displayed indicating that a user has logged in, press Shift + 9 quickly.

Other related questions:
Must the IP addresses of the two peer ends on FR networks be in the same network segment
The IP addresses of two peer ends have no need to be configured in the same network segment if both ends are both AR routers.

How to determine whether the peer end transmits numbers using DTMF signals or FSK signals?
Connect the phone to the AT0 line. If the calling number is displayed immediately a call comes in, DTMF signals are used. If the calling number is displayed after the first ring and before the second ring, FSK signals are used.

The two ends of an LSP are Up and can send Hello messages, but the peer end cannot receive them. Why
If the two ends of an LSP are Up and can send Hello messages, but the peer end cannot receive the messages, the possible causes are as follows: Devices do not support sending of large packets, for example, the device can send packets whose maximum size is 180 bytes. To check whether the peer end can send large packets, ping the IP address of the peer end using large packets. Run the display cpu-defend statistics slot slot-id command to check whether Hello messages are dropped due to attack defense policies or Hello messages do not reach the cpu-defend module. Check whether statistics on MPLS-related ACL packets exist and ACLs are correctly delivered.

An AR router configured with ATM cannot interconnect with the Cisco router on the peer end
Check the configuration of the AR router and find that IPoA is configured.
# interface Atm0/0/0.1 p2p ip address 10.229.190.6 255.255.255.252 pvc 8/35 map ip 10.229.190.5 //Configure IPoA mapping on the pvc. # 

Check the configuration of the Cisco router and find that IPoEoA is configured.
 ! interface ATM0/0/0.1 point-to-point ip address xx.xx.xx.xx 255.255.255.252 ip nat outside atm route-bridged ip //Configure IPoEoA. pvc 8/35 encapsulation aal5snap ! !  

After the configuration of the AR router is modified from IPoA to IPoEoA, the AR router can ping the Cisco router successfully.
 # interface Virtual-Ethernet0/0/2 ip address 10.229.190.6 255.255.255.252 # interface Atm0/0/0.1 p2p pvc 8/35 map bridge Virtual-Ethernet 0/0/2 //Configure IPoEoA mapping on pvc. #

Method used to configure IPSec on the 3G interface of the AR
Huawei AR series routers can dynamically obtain IP addresses from a service provider to access public network using a 3G interface, and establish IPSec connections with the headquarters. This function applies to V200R002C00 and later versions and all models of the AR. For details, see Typical Configuration Examples.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top