Configuring P2MP Network Attributes

Procedure

1. Disable OSPF from checking the network mask.

   The OSPF neighbor relationship cannot be established between the devices with different mask lengths on the P2MP network. After OSPF is disabled from checking the network mask, the OSPF neighbor relationship can be properly established.

   1. Run system-view

      The system view is displayed.

   2. Run interface interface-type interface-number

      The interface view is displayed.

   3. Run ospf network-type p2mp

      The network type of the OSPF interface is configured.

      A P2MP network is forcibly changed from another other type of network. For details, see Configuring Network Types for OSPF Interfaces.

   4. Run ospf p2mp-mask-ignore

      OSPF is disabled from checking the network mask on the P2MP network.

   5. Run commit

      The configuration is committed.

2. (Optional) Configure the device to filter the LSA packets to be sent.

   When multiple links exist between two devices, you can configure the local device to filter the LSA packets to be sent. This can reduce unnecessary LSA retransmission attempts and save bandwidth resources.

   1. Run system-view

      The system view is displayed.

   2. Run ospf [ process-id ]

      The OSPF process view is displayed.

   3. Based on the basic ACL:

      1. Run filter-lsa-out peer ip-address { all | { summary [ acl { acl-number | acl-name } ] | ase [ acl { acl-number | acl-name } ] | nssa [ acl { acl-number | acl-name } ] } ^* }

         The local router is configured to filter the LSA packets to be sent on the P2MP network.

      2. Run quit

         Return to the system view.

      3. Run acl { name basic-acl-name { basic | [ basic ] number basic-acl-number } | [ number ] basic-acl-number } [ match-order { config | auto } ]

         The basic ACL view is displayed.

      4. Run rule [ rule-id ] [ name rule-name ] { deny | permit } [ fragment-type { fragment | non-fragment | non-subseq | fragment-subseq | fragment-spe-first } | source { source-ip-address { source-wildcard | 0 | src-netmask } | any } | time-range time-name | vpn-instance vpn-instance-name ] ^*

         The rule for the basic ACL is configured.

         When the rule command is run to configure rules for a named ACL, only the source address range specified by source and the time period specified by time-range are valid as the rules.

         When a filtering policy of a routing protocol is used to filter routes:

         • If the action specified in an ACL rule is permit, a route that matches the rule will be received or advertised by the system.

         • If the action specified in an ACL rule is deny, a route that matches the rule will not be received or advertised by the system.

         • If a route has not matched any ACL rules, the route will not be received or advertised by the system.

         • If an ACL does not contain any rules, all routes matching the route-policy that references the ACL will not be received or advertised by the system.

         • In the configuration order, the system first matches a route with a rule that has a smaller number and then matches the route with a rule with a larger number. Routes can be filtered using a blacklist or a whitelist:

           Route filtering using a blacklist: Configure a rule with a smaller number and specify the action deny in this rule to filter out the unwanted routes. Then, configure another rule with a larger number in the same ACL and specify the action permit in this rule to receive or advertise the other routes.

           Route filtering using a whitelist: Configure a rule with a smaller number and specify the action permit in this rule to permit the routes to be received or advertised by the system. Then, configure another rule with a larger number in the same ACL and specify the action deny in this rule to filter out unwanted routes.

   4. Run commit

      The configuration is committed.