Instead, if the device is found to belong to a VPN site and if the site connectivity includes eBGP, the discovered AS number is matched against the peer BGP AS number specified on the VPN site.
For devices assigned the role of Access, such as CE devices, AS number validation is not performed against the default domain AS. If the device being discovered already has roles, due to re-discovery, this behavior is seen only for devices assigned the role of Gateway or Core. This warning is for information purposes only and does not inhibit service provisioning using the discovered AS number.
If a device changes its Autonomous System membership, it must be re-discovered to ensure IP Service Activator is aware of the change.ĭuring device discovery, if the discovered AS number differs from the default Domain AS number, IP Service Activator raises a warning against the device (Code 1627): DeviceName ( DeviceManagementIPAddress) ASN on device does not match Domain ASN All BGP provisioning on a device will use the last discovered BGP AS number. IP Service Activator supports Multi-AS domains by actively discovering the BGP AS number configured into each device as it is discovered, or re-discovered, in the system.
A domain that contains devices belonging to different Autonomous Systems is referred to as a Multi-AS domain. IP Service Activator supports a default AS at the domain level but individual routers within this domain may have a different AS than the domain default. Each router managed by IP Service Activator has a BGP Autonomous System (AS) number.