- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- WAN Routing
- >
- Re: MBGP route leaking from public to vpn-instance
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-29-2020 07:51 AM
тАО05-29-2020 07:51 AM
MBGP route leaking from public to vpn-instance
Hi,
I work on HPE 5500 and 5900 series and I would like to know if it's possible to route-leak multicast route, which are learned by (M)BGP protocol , from the global/public routing table to a vpn-instance routing table ?
I tried to use route-policy but it didn't work...
Has somebody got an idea with this problem ?
Thanks a lot !
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-31-2020 06:27 PM - edited тАО06-01-2020 06:06 PM
тАО05-31-2020 06:27 PM - edited тАО06-01-2020 06:06 PM
Re: MBGP route leaking from public to vpn-instance
Hi,
Its possible, can you please share issue in detail and config which you used?
Adding below link for your reference:
http://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-c04088674-2.pdf
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-02-2020 03:03 AM - edited тАО06-02-2020 03:12 AM
тАО06-02-2020 03:03 AM - edited тАО06-02-2020 03:12 AM
Re: MBGP route leaking from public to vpn-instance
Hi,
Yes of course.
The issue is : I would like to learn routes from mbgp protocol in to a vpn-instance. I saw on differents topics and doc, I can't do that. If I want to use MBGP, the multicast route can only be stored in the global routing-table.
But, I need to have this routes in my vpn-instance in order to receive multicast stream on the good interfaces. I saw it's possible to leak the routes which are in the global RT and learn from the mbgp protocol to the vpn-instance routing-table. (https://community.hpe.com/t5/wan-routing/route-leaking-between-vpn-instance-and-the-global-route-table/m-p/6427994#M286) But I can't do it.. May be I miss something..
You will find the config below :
ip vpn-instance OPE
import route-policy IMPORT-MULTICAST
#
ospf 1 router-id 65.1.0.0 vpn-instance OPE
non-stop-routing
import-route direct cost 5 type 1
import-route static cost 1
area 65.1.1.0
network 65.1.5.232 0.0.0.3
network 65.1.5.236 0.0.0.3
#
vlan 2
name CLIENT
description CLIENT
#
vlan 3
name SUPV
description SUPV
#
vlan 4
name SUPV_SEC
description SUPV_SEC
#
vlan 5
name WAN1
description WAN1
#
vlan 6
name WAN2
description WAN2
#
vlan 7
description VLAN_MULTICAST
#
igmp non-stop-routing
#
interface LoopBack0
ip address 65.1.254.253 255.255.255.255
#
interface Vlan-interface2
description Interface_lvl3_CLIENT
ip binding vpn-instance OPE
ip address 65.1.2.1 255.255.255.0
pim sm
pim passive
igmp enable
igmp version 3
igmp static-group 232.0.0.1 source 65.251.1.65
igmp static-group 232.0.0.2 source 65.251.1.73
igmp static-group 232.0.0.10 source 65.251.2.65
igmp static-group 232.0.0.11 source 65.251.2.73
#
interface Vlan-interface5
ip binding vpn-instance OPE
ip address 65.1.5.234 255.255.255.252
ospf cost 10
ospf network-type p2p
pim sm
#
interface Vlan-interface6
ip binding vpn-instance OPE
ip address 65.1.5.238 255.255.255.252
ospf cost 5
ospf network-type p2p
pim sm
#
interface Vlan-interface7
description VLAN_MULTICAST
ip address 65.1.5.226 255.255.255.252
pim sm
pim passive
igmp enable
igmp version 3
igmp static-group 232.0.0.74 source 65.251.1.65
igmp static-group 232.0.0.75 source 65.251.1.73
igmp static-group 232.0.0.146 source 65.251.2.65
igmp static-group 232.0.0.147 source 65.251.2.73
#
interface Ten-GigabitEthernet1/0/1
port link-mode bridge
description CLIENT
port access vlan 2
#
interface Ten-GigabitEthernet1/0/2
port link-mode bridge
description CLIENT
port access vlan 2
#
interface Ten-GigabitEthernet1/0/7
port link-mode bridge
port access vlan 7
#
interface Ten-GigabitEthernet1/0/10
port link-mode bridge
description WAN1
port link-type trunk
port trunk permit vlan 5
#
interface Ten-GigabitEthernet2/0/1
port link-mode bridge
description CLIENT
port access vlan 2
#
interface Ten-GigabitEthernet2/0/2
port link-mode bridge
description CLIENT
port access vlan 2
#
interface Ten-GigabitEthernet2/0/11
port link-mode bridge
description WAN2
port link-type trunk
port trunk permit vlan 6
#
bgp 6522
router-id 65.1.0.0
peer 65.1.5.225 as-number 6523
#
address-family ipv4 unicast
network 65.1.33.0 255.255.255.0
network 65.1.2.0 255.255.255.0
network 65.1.5.220 255.255.255.252
peer 65.1.5.225 enable
peer 65.1.5.225 route-policy IMPORT-MULTICAST import
#
address-family ipv4 multicast
network 65.1.33.0 255.255.255.0
network 65.1.2.0 255.255.255.0
network 65.1.5.220 255.255.255.252
peer 65.1.5.225 enable
peer 65.1.5.225 route-policy IMPORT-MULTICAST import
#
multicast routing
longest-match
#
multicast routing vpn-instance OPE
longest-match
#
pim non-stop-routing
#
pim
#
igmp
#
route-policy IMPORT-MULTICAST permit node 1
if-match ip address prefix-list MULTICAST_VRF
#
ip prefix-list MULTICAST_VRF index 5 permit 65.0.0.0 8 less-equal 32
ip prefix-list MULTICAST_VRF index 10 permit 0.0.0.0 0 less-equal 32
#
Thank you