Configuración bgp
PART 1
Attribute Types Must be supported and propagated Must be supported; propagation optional
packetlife.net
About BGP Type Path Vector eBGP AD 20 iBGP AD 200 Standard RFC 4271Protocols IP Transport TCP/179 Authentication MD5 Terminology Autonomous System (AS)
A logical domain under the control of a single entity
Well-known Mandatory
Well-known Discretionary OptionalTransitive
Marked as partial if unsupported by neighbor Deleted if unsupported by neighbor Attributes
Optional Nontransitive
Name Type
Description
Aggregator OT AS Path WM Atomic Aggregate WDCluster ID ON Community OT Local Preference WD Multiple Exit ON Discriminator (MED) Next Hop WM Origin WM Originator ID ON Weight O
ID and AS of router which performed summarization List ofautonomous systems which the advertisement has traversed Includes ASes which have been dropped due to route aggregation Originating cluster Route tag Metric for internal neighbors to reach externaldestinations (default 100) Metric for external neighbors to reach the local AS (default 0) External peer in neighboring AS Origin type (IGP, EGP, or unknown) Identifies a route reflector Cisco proprietary, notcommunicated to peers (default 0) Path Selection
External BGP (eBGP)
BGP adjacencies which span autonomous system boundaries
Internal BGP (iBGP)
BGP adjacencies formed within a singleautonomous system
Synchronization Requirement
A route must be known by an IGP before it may be advertised to BGP peers
Packet Types Open Keepalive Update Notification
Neighbor States
PreferenceAttribute
Description
Idle
Neighbor is not responding Attempting to connect TCP session established Open message sent Response received
1 Weight 2 Local Preference 3 Self-originated 4 ASPath 5 Origin 6 MED 7 External 8 IGP Cost 9 eBGP Peering 10 Router ID
Administrative preference Communicated between peers within an AS Prefer paths originated locally Minimize AS hops Prefer...
Regístrate para leer el documento completo.