3Com 3031 Command Reference Manual page 792

792 C 8: MPLS B
HAPTER ASIC
peer allow-as-loop
C C
ONFIGURATION OMMANDS
If you bind an OSPF procedure to a nonexistent VPN instance, the command
fails in executing and the system prompts the information "Specified vpn
instance not configured".
When a VPN instance is deleted, all OSPF procedures associated to it will be
deleted. For example, suppose VPN instance vpn1 includes OSPF procedures 1,
2 and 3. If VPN instance vpn1 is deleted, the OSPF procedures 1, 2 and 3 will all
be deleted.
For the related command, see network.
Example
Enable the default OSPF procedure 1.
[3Com] router id 10.110.1.8
[3Com] ospf
Enable OSPF procedure 120 and run OSPF protocol.
[3Com] router id 10.110.1.8
[3Com] ospf 120
[3Com-ospf-120]
Enable OSPF procedure 100, specify its route ID as 2.2.2.2 and bind it to the VPN
instance vpn1.
[3Com] ospf 100 router-id 2.2.2.2 vpn-instance vpn1
[3Com-ospf-100]
Syntax
peer { group-name | peer-address } allow-as-loop asn-limit
undo peer { group-name | peer-address } allow-as-loop asn-limit
View
BGP view, MBGP IPv4-family view
Parameter
group-name: Name of the peer group
ip-address: specified IP address of peer.
asn-limit: The maximum number allowed in received route updates of the local
autonomous system number AS.
Description
Using the peer allow-as-loop command, you can enable route loop detection in
the received route updates in hub&spoke networking mode. Using the undo peer
allow-as-loop command, you can prohibit loop to occur in the received route
updates.
By default, loop information is prohibited in the received route update
information.