The two ends of an LSP are Up and can send Hello messages, but the peer end cannot receive them. Why

3

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.

Other related questions:
Logging in to the peer-end controller by using the peer-end heartbeat IP address
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.

Why are statistics on received and sent Hello messages both 0
Run the display mpls ldp interface command to check the interface status. The command output is displayed as follows: display mpls ldp interface LDP Interface Information in Public Network Codes:LAM(Label Advertisement Mode), IFName(Interface name) A '*' before an interface means the entity is being deleted. ------------------------------------------------------------------------------ IFName Status LAM TransportAddress HelloSent/Rcv ------------------------------------------------------------------------------ Vlanif10 Active DU 1.1.1.1 29574/29539 ------------------------------------------------------------------------------ In normal cases, the interface status is Active. If the interface status is Inactive, the interface cannot receive or send Hello messages. In most cases, the interface status is Inactive because the interface is shut down or no IP address is configured for the interface.

How to operate multi-view of TE series endpoints
The multi-view is displayed as the conference video at the local site. If you are in a conference, the multi-view will be shared to remote sites. The TE30 does not support multi-view. To set multi-view for a TE40, TE50, or TE60, perform the following operations: 1. Logging in to the web interface. Choose Device Control > Device Control and click the Multi-View tab. 2. Set Multi-view mode for any of the following: PiP, 2 panes, 3 panes (a), 3 panes (b). 3. Specify input sources for the multi-view mode you selected. 4. Choose Device Control > Device Control and click the Video Control tab. 5. In the Video Input Source area, set Video Source to Multi-View.

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. #

Why is multicast forwarding interrupted on an interface after the interface receives Hello messages
After static IGMP groups are configured on an interface, the device uses the PIM protocol to set up multicast forwarding entries. Multicast data can be forwarded through the interface as long as the interface is included in the downstream interface list in the corresponding multicast forwarding entry. If the source address of a received PIM Hello message is larger than the interface address, or the DR priority of the PIM Hello message is larger than the priority of the interface, the switch can no longer function as the DR. All data packets on a shared network segment are forwarded by the DR is no Assert election occurs. Therefore, the device considers that multicast data packets will be forwarded by the new DR and then prunes the downstream interface.

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