Model Limitations for Real BGP Payload Support
The following protocol features are not currently supported for sending BGP payload between a simulation and a real router:
- BGP 4-byte autonomous system numbers (RFC 4893)
- Multiprotocol extensions for BGP (RFC 4760)
- BGP peering with IPv6 neighbors
- Routing updates with IPv6 prefixes
- BGP communities. If the model detects a simulated packet that includes communities information, it will stop the simulation.
- BGP RFCs other than RFC 4271 (except the confederations and reflectors features of RFC 5065 and RFC 4456, as mentioned in Table 26)
- Certain fields of supported BGP messages, as listed in Table 27
Table 27: Unsupported Fields in BGP Messages
| BGP Message | Field | Subfield | Comments |
|---|---|---|---|
| OPEN | Optional Parameters | When a real router includes this field, the message is simply ignored by deserialization and is not set in the simulated packet | |
| NOTIFICATION | Data | Serialization The BGP model does not support this field, therefore it is never included when serializing Deserialization Ignored and not included in the simulated packet |
|
| UPDATE | Path Attributes | ATOMIC_AGGREGATE | |
| AGGREGATOR |