.. _example_protocols_bgp_import_import:

######
Import
######


.. sidebar:: Contents

  .. contents::
    :depth: 2
    :local:

Scenario to verify BGP **import vrf** functionality, with and without **route-map**
filtering, for both iBGP and eBGP sessions.

The ``import vrf main`` command allows routes learned via BGP in the main VRF to be
imported into another VRF (VRF1), making them available in the VRF1 routing table.
This is useful for service isolation where different VRFs need controlled access to
routes from the global routing table.

Optionally, an ``import route-map`` can be applied to filter which routes are imported
into the target VRF. This provides granular control over inter-VRF route leaking.

The test covers four scenarios:

- **iBGP import vrf**: Direct import without filtering (same AS).

- **eBGP import vrf**: Import via transit router without filtering (different AS).

- **iBGP import route-map**: Import with route-map filtering applied (same AS).

- **eBGP import route-map**: Import via transit with route-map filtering (different AS).

.. image:: topologyimportvrf.svg
  :width: 400

*******************
Test BGP Import VRF
*******************

Description
===========

Test BGP import vrf: basic (routes imported into VRF1) and route-map
(routes imported with filtering). Each variant tested with iBGP and eBGP.

Scenario
========

.. include:: import/testbgpimportvrf

.. raw:: html

  <hr>