Juniper Networks
Log in
|
How to Buy
|
Contact Us
|
United States (Change)
Choose Country
Close

Choose Country

North America

  • United States

Europe

  • Deutschland - Germany
  • España - Spain
  • France
  • Italia - Italy
  • Россия - Russia
  • United Kingdom

Asia Pacific

  • Asean Region (Vietnam, Indonesia, Singapore, Malaysia)
  • Australia
  • 中国 - China
  • India
  • 日本 - Japan
  • 대한민국 - Korea
  • 台灣 - Taiwan
Solutions
Products & Services
Company
Partners
Support
Education
Community
Security Intelligence Center

Technical Documentation

Support
Technical Documentation
Content Explorer New
 
Enterprise MIBs
 
EOL Documentation
 
Feature Explorer Login required New
 
File Format Help
 
Glossary
 
Portable Libraries
 
 
Home > Support > Technical Documentation > JunosE Software > aggregate-address
Print
Rate and give feedback:  Feedback Received. Thank You!
Rate and give feedback: 
Close
This document helped resolve my issue.  Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  
E-mail: 
Submitting...

aggregate-address

Syntax

[ no ] aggregate-address { address mask | ipv6Prefix }
[ as-set | summary-only | attribute-map attributeMapTag |
advertise-map advertiseMapTag | suppress-map suppressMapName ]*

Release Information

Command introduced before JunosE Release 7.1.0.

Description

Creates an aggregate entry in a BGP routing table. The no version removes the aggregate.

Options

  • address—Aggregate IPv4 address
  • mask—Aggregate IPv4 mask
  • ipv6Prefix—Aggregate IPv6 prefix
  • as-set—If the as-set option is not specified, the path attributes of the aggregate route are set in the same way as locally originated routes, except that the atomic_aggregate and aggregator attributes are added. If the as-set option is used, the path attributes of the aggregate route are determined by combining the path attributes of the aggregated routes as described in RFC 4271—A Border Gateway Protocol 4 (BGP-4). If the as-set option is used, the path attributes of the aggregate route may change whenever one of the aggregated routes changes, causing the aggregate route to be readvertised.
  • summary-only—Filters all more specific routes from updates. summary-only not only creates the aggregate route but also suppresses advertisements of more-specific routes to all neighbors. If you only want to suppress advertisements to certain neighbors, you may use the neighbor distribute-list command, with caution. If a more-specific route leaks out, all BGP speakers will prefer that route over the less-specific aggregate you are generating (using longest-match routing). Alternatively, you can use the suppress-map keyword to suppress specific routes.
  • attributeMapTag—String of up to 32 characters that identifies the route map used to set the attributes of the aggregate route
  • advertiseMapTag—String of up to 32 characters that identifies the route map used to set the routes to create AS-SET origin communities in the range
  • suppressMapName—String of up to 32 characters that identifies a route map that filters routes to be suppressed
  • *—Indicates that one or more parameters can be repeated multiple times in a list in the command line

Mode

Address Family Configuration, Router Configuration

Published: 2012-06-28

 
  • About Juniper
  • Investor Relations
  • Press Releases
  • Newsletters
  • Juniper Offices
  • Green Networking
  • Resources
  • How to Buy
  • Partner Locator
  • Image Library
  • Visio Templates
  • Security Center
  • Community
  • Forums
  • Blogs
  • Junos Central
  • Social Media
  • Developers
  • Support
  • Technical Documentation
  • Knowledge Base (KB)
  • Software Downloads
  • Product Licensing
  • Contact Support
Site Map / RSS Feeds / Careers / Accessibility / Feedback / Privacy & Policy / Legal Notices
Copyright© 1999-2012 Juniper Networks, Inc. All rights reserved.
Help
|
My Account
|
Log Out