3Com Switch 7750 Configuration Guide Guide

Troubleshooting MSDP Configuration 459
4 Configure a static RPF peer
# Configure Switch D and Switch F as static RPF peers of Switch C.
[SwitchC] ip ip-prefix list-df permit 192.168.0.0 16 greater-equal 16
less-equal 32
[SwitchC] msdp
[SwitchC-msdp] peer 192.168.3.1 connect-interface Vlan-interface101
[SwitchC-msdp] peer 192.168.1.2 connect-interface Vlan-interface110
[SwitchC-msdp] static-rpf-peer 192.168.3.1 rp-policy list-df
[SwitchC-msdp] static-rpf-peer 192.168.1.2 rp-policy list-df
[SwitchC-msdp] quit
# Configure Switch C as static an RPF peer of Switch D and Switch F. The
configuration
procedure on Switch F is similar to the configuration procedure on
Switch
D, so the configuration procedure on Switch F is omitted.
[SwitchD] ip ip-prefix list-c permit 192.168.0.0 16 greater-equal 16
less-equal 32
[SwitchD] msdp
[SwitchD-msdp] peer 192.168.3.2 connect-interface Vlan-interface101
[SwitchD-msdp] static-rpf-peer 192.168.3.2 rp-policy list-c
[SwitchD-msdp] quit
5 Verify the configuration
That no information is output after you carry out the display bgp peer command
means that the BGP peering relationships are not established between the
switches. When the multicast source S1 in PIM-SM1 sends multicast information,
receivers in PIM-SM2 and PIM-SM3 can receive the multicast data. You can use the
display msdp brief command to view the brief information of MSDP peering
relationships between the switches. The information about MSDP peering
relationships on Switch C, Switch D and Switch F is as follows:
[SwitchC] display msdp brief
MSDP Peer Brief Information
Peer’s Address State Up/Down time AS SA Count Reset Count
2.2.2.2 UP 01:07:08 ? 8 0
3.3.3.3 UP 00:16:39 ? 13 0
[SwitchD] display msdp brief
MSDP Peer Brief Information
Peer’s Address State Up/Down time AS SA Count Reset Count
1.1.1.1 UP 01:07:09 ? 8 0
[SwitchF] display msdp brief
MSDP Peer Brief Information
Peer’s Address State Up/Down time AS SA Count Reset Count
1.1.1.1 UP 00:16:40 ? 13 0
Troubleshooting
MSDP Configuration
MSDP Peer Always in
the Down State
Symptom
An MSDP peer is configured, but it is always in the down state.
Analysis
An MSDP peer relationship between the locally configured connect-interface
interface address and the configured peer address is based on a TCP connection. If
the address of local connect-interface interface is inconsistent with the peer
address configured on the peer router, no TCP connection can be established. If
there is no route between the two peers, no TCP connection can be established.