Setting the Peer Type

Each peer group must have a peer type before any BGP sessions for members of that peer group are allowed to come up and before the Adj-RIBs-Out table of that peer group can be filled. You can use the neighbor peer-type command to explicitly configure a peer type for a peer group.

Alternatively, you can implicitly configure the peer type of a peer group by either of the following methods:

• Configure a remote AS for the peer group.
• Assign a peer with a configured remote AS as a member of the peer group.

In both of these implicit cases, the remote AS is combined with the local AS, the configured confederation ID, and the configured confederation peers to determine the peer type of the peer group.

neighbor peer-type

• Use to specify a peer type for a peer group.
• This command is supported only for peer groups; it is not available for individual peers.
• Use the internal keyword to specify that peers must be in the same AS or, if confederations are employed, in the same sub-AS in the same confederation.
• Use the external keyword to specify that peers must be in a different AS.
• Use the confederation keyword to specify that peers must be in a different sub-AS in the same confederation. Use this keyword only if confederations are employed.
• This command takes effect immediately. If the command changes the peer type of the peer group, all BGP sessions for members of that peer group are automatically bounced.
• All the members of the peer group inherit the characteristic configured with this command. It cannot be overridden for a specific peer, because the command applies only to peer groups.
• Example

  host1(config-router)#neighbor promispeers peer-type internal

• Use the no version to remove the configuration from the peer group.
• See neighbor peer-type

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.