By default, an MSDP peer permits all Source Active (SA) messages that pass the Reverse Path Forwarding (RPF) check, and forwards the SA messages to other MSDP peers. To control the transmission of SA messages among MSDP peers, configure filtering policies to filter SA messages to be created, received, or forwarded.
The system view is displayed.
Run acl { name advance-acl-name [ advance | [ advance ] number advance-acl-number ] | [ number ] advance-acl-number } [ match-order { config | auto } ]
An advanced ACL is created, and the advanced ACL view is displayed.
Run rule [ rule-id ] [ name rule-name ] { deny | permit } ip [ destination { destination-ip-address { destination-wildcard | 0 } | any } | source { source-ip-address { source-wildcard | 0 } | any } ] *
Rules are configured for the advanced ACL.
If a basic ACL is used, run the rule command and set the source parameter to the source address of multicast packets.
If an advanced ACL is used, run the rule command, set the source parameter to the source address of multicast packets, and set the destination parameter to a multicast group address.
Return to the system view.
The MSDP view is displayed.
The device is configured to filter the outgoing locally generated SA messages of a specified VPN instance.
If no ACL is specified, the device does not send any locally generated SA messages.
If an ACL is specified, the device sends only the locally generated SA messages that match the filtering policy.
The configuration is committed.
The system view is displayed.
An advanced ACL is created, and the advanced ACL view is displayed.
Rules are configured for the advanced ACL.
Return to the system view.
The MSDP view is displayed.
The device is configured to filter the locally generated SA messages to be sent to the specified peer.
If no ACL is specified, the device does not send any locally generated SA message to the specified peer. If an ACL is specified, the device sends only the locally generated SA messages that match the filtering policy to the specified peer.
The configuration is committed.
Both the import-source and peer sa-policy local-export commands can be used to configure a filtering policy for locally generated SA messages. If the import-source command is run in the MSDP view and the peer sa-policy local-export command is also run on the MSDP peer, the rule specified in the peer sa-policy local-export command preferentially takes effect.
The system view is displayed.
An advanced ACL is created, and the advanced ACL view is displayed.
Rules are configured for the advanced ACL.
In the rule command, set the source parameter to the source address of SA messages, and set the destination parameter to a multicast group address.
Return to the system view.
The MSDP view is displayed.
The device is configured to filter the SA messages to be received from a specified remote MSDP peer.
peer-address: specifies the IP address of a remote MSDP peer.
acl advanced-acl-number: specifies the name of an advanced ACL to be used as the filtering policy. The device uses the ACL to determine whether to accept the SA messages to be received from the specified remote MSDP peer.
If no ACL is specified, the device does not receive any (S, G) information from the peer specified by peer-address.
If an ACL is specified, the device accepts the matching SA messages received from the peer specified by peer-address.
The configuration is committed.
The system view is displayed.
An advanced ACL is created, and the advanced ACL view is displayed.
Rules are configured for the advanced ACL.
In the rule command, set the source parameter to the source address of SA messages, and set the destination parameter to a multicast group address.
Return to the system view.
The MSDP view is displayed.
The device is configured to filter the SA messages to be forwarded to the specified remote MSDP peer.
peer-address: specifies the IP address of a remote MSDP peer.
acl advanced-acl-number: specifies the name of an advanced ACL to be used as the filtering policy. The device uses the ACL to determine whether to forward SA messages to the specified remote MSDP peer.
If no ACL is specified, the device does not forward any SA messages to the specified remote MSDP peer.
If an ACL is specified, the device forwards only the matching SA messages to the remote MSDP peer specified by peer-address.
The configuration is committed.