BGP AS number not configured

[Daniel Roesen]

The FUEL Contrail plugin allows to specify the BGP AS number for Contrail to use. Unfortunately, this AS number is not really configured in Contrail but the default AS 64512 is used instead. This is using the most current FUEL Contrail plugin with FUEL 8.0 but we have seen this problem since we started with FUEL 6 and Contrail 2.0.

[Daniel Roesen (daniel-roesen)]

Code in plugin looks OK for me regarding handoff of the parameter to Contrail (but I'm not a Puppet guy):

./deployment_scripts/puppet/modules/contrail/manifests/provision/control.pp

  exec { 'prov_control_bgp':
    command => "python /opt/contrail/utils/provision_control.py \
--api_server_ip ${contrail::contrail_mgmt_vip} --api_server_port 8082 \
--oper add --host_name ${::fqdn} --host_ip ${contrail::address} --router_asn ${contrail::asnum} \
--admin_user '${contrail::neutron_user}' --admin_tenant_name '${contrail::service_tenant}' --admin_password '${contrail::service_token}' \
&& touch /opt/contrail/prov_control_bgp-DONE",
    creates => '/opt/contrail/prov_control_bgp-DONE',
  }

AS number is taken from attributes and passed to /opt/contrail/utils/provision_control.py.
Guess we need to find out wether ${contrail::asnum} correctly contains the user-specified ASN,
or the default 64512.

[Olesia Tsvigun (otsvigun)]

Verified at Fuel ISO#8.0 and fuel-plugin-contrail 4.0.0

[Daniel Roesen (daniel-roesen)]

The fix is working on general Contrail AS number, but the gateway routers still have default AS64512 configured as peer AS. Thus, BGP sessions won't come up. So fix is "incomplete".

Perhaps it also might make sense to differentiate between BGP AS Contrail operates as (global AS configuration which is now correctly taken care of) and the BGP AS the physical world in form of the gateway routers operate under. Shoudn't this be a second parameter to the FUEL plugin?

[Oleksandr Martsyniuk (omartsyniuk)]

Hi Daniel,

enabling eBGP for gateway routers is possible, but this requires adding a new parameter to plugin settings.
You may deploy an environment with iBGP peers only and use Contrail Web UI to change the peers parameters.

[Daniel Roesen (daniel-roesen)]

Hi,

slight misunderstanding I guess. The lab backbone is using AS65512. Contrail
uses 64512 by default. We're specifying 65512 in Contrail Plugin options, but
(after fix) this is only transferred to Contrail's global config as the ASN
under which Contrail controllers operate. But the GW routers are still being
configured with the default remote ASN 65412 instead of 65512 as we specified.
So the GW routers will see incoming BGP sessions from AS65512 peers which try
to contact 65412 GWs... the GW routers identify themselves as 65512 and thus
the Contrail controllers close the BGP due to incorrect peer ASN.

Best regards,
Daniel

[Daniel Roesen (daniel-roesen)]

OK looks like the fix for the gateway ASN problem got committed in
https://github.com/openstack/fuel-plugin-contrail/commit/114536ef2e7c569300019844e0ca57d278e27791

Things seem to be working OK now. Thanks!