netgo

What is basic BGP community concept?

This instruction is good reference. In fact, I will analysis this instruction. BGP community is used for filtering and tagging information over routing information. Therefore, routing table information will be controlled by these condistions. Thus I can select the routing information to advertise or update in the table.

1. Pre-requiste (Basic BGP configuration)

This is my environment for this post.

S1

S2

S3

S4

interface Ethernet1/1

no switchport

ip address 100.12.1.11/16

no shutdown

!

interface loopback0

ip address 1.1.1.1/32

!

interface loopback1

ip address 11.11.11.11/32

!

router bgp 1

router-id 1.1.1.1

log-neighbor-changes

address-family ipv4 unicast

network 1.1.1.1/32

network 11.11.11.11/32

neighbor 100.12.2.11

remote-as 2

update-source Ethernet1/1

address-family ipv4 unicast

interface Ethernet1/1

no switchport

ip address 100.12.2.11/16

no shutdown

interface Ethernet1/2

no switchport

ip address 100.23.2.12/16

no shutdown

!

interface loopback0

ip address 2.2.2.2/32

!

interface loopback1

ip address 22.22.22.22/32

!

router bgp 2

router-id 2.2.2.2

log-neighbor-changes

address-family ipv4 unicast

network 2.2.2.2/32

network 22.22.22.22/32

neighbor 100.12.1.11

remote-as 1

update-source Ethernet1/1

address-family ipv4 unicast

neighbor 100.23.3.12

remote-as 3

update-source Ethernet1/2

address-family ipv4 unicast

interface Ethernet1/2

no switchport

ip address 100.23.3.12/16

no shutdown

interface Ethernet1/3

no switchport

ip address 100.34.3.13/16

no shutdown

!

interface loopback0

ip address 3.3.3.3/32

!

interface loopback1

ip address 33.33.33.33/32

!

router bgp 3

router-id 3.3.3.3

log-neighbor-changes

address-family ipv4 unicast

network 3.3.3.3/32

network 33.33.33.33/32

neighbor 100.23.2.12

remote-as 2

update-source Ethernet1/2

address-family ipv4 unicast

neighbor 100.34.4.13

remote-as 4

update-source Ethernet1/3

address-family ipv4 unicast

interface Ethernet1/3

no switchport

ip address 100.34.4.13/16

no shutdown

!

interface loopback0

ip address 4.4.4.4/32

!

interface loopback1

ip address 44.44.44.44/32

!

router bgp 4

router-id 4.4.4.4

log-neighbor-changes

address-family ipv4 unicast

network 4.4.4.4/32

network 44.44.44.44/32

neighbor 100.34.3.13

remote-as 3

update-source Ethernet1/3

address-family ipv4 unicast

For nexus, "address-family ipv4 unicast" in neighbor parameter and "address-familiy ipv4 unicast" in global parameter are necessary to advertise to the peer. After configure these, I can verify the routing table and BGP information. From S2,

From S3,

From S4,

I can confirm that the information from S1 such as "1.1.1.1" and "11.11.11.11" are advertised to S2, S3 and S4.

2. Configure send community

To use the BGP community, I have to configure "send community". There are 2 types, standard and extended. In this struction, the extended community has more information such as VPN services.

I will added the configuration like below.

S1

S2

S3

S4

router bgp 1

neighbor 100.12.2.11

address-family ipv4 unicast

send-community both

router bgp 2

neighbor 100.12.1.11

address-family ipv4 unicast

send-community both

neighbor 100.23.3.12

address-family ipv4 unicast

send-community both

router bgp 3

neighbor 100.23.2.12

address-family ipv4 unicast

send-community both

neighbor 100.34.4.13

address-family ipv4 unicast

send-community both

router bgp 4

neighbor 100.34.3.13

address-family ipv4 unicast

send-community both

Please note that there are any differences of routing table after these configuration above.

3. Configure Route-map in and out

To use the BGP community, the route-map is necessary. This route-map affect the routing table. In S3, I will add "route-map" configuration.

!

router bgp 1

neighbor 100.12.2.11

address-family ipv4 unicast

route-map to-remote-as2 out

end

!

"route-map to-remote-as2 out" mean that routing information to transfer out will be controlled with this route-map. Therefore, after this configuration, the routing table will be changed. "1.1.1.1" and "11.11.11.11" are removed.

Now, I will add the policy to set community.

ip prefix-list ip-prefix-1 seq 10 permit 1.1.1.1/32
ip prefix-list ip-prefix-2 seq 10 permit 11.11.11.11/32
route-map to-remote-as2 permit 10
  match ip address prefix-list ip-prefix-1
  set community 12:130
route-map to-remote-as2 permit 20
  match ip address prefix-list ip-prefix-2
  set community 12:150

I check the routing table from S4. "1.1.1.1" and "11.11.11.11" will be updated.

And I can see more detail. I can see the community values are changed on each.

So far, I learn how to set the community with BGP. From now, I will handle how to get the community and use this. This is so similar with above. I will add configure into the S2.

!

router bgp 2

neighbor 100.12.1.11

address-family ipv4 unicast

route-map from-remote-as1 in

end

!

After configure this, the routing table will be changed. "1.1.1.1" and "11.11.11.11" are removed again.

Now, I will add some configuration to get community and use it in S2.

ip community-list expanded community-1 seq 1 permit "12:130"

ip community-list expanded community-2 seq 1 permit "12:150"

route-map from-remote-as1 permit 10

match community community-1

set local-preference 130

route-map from-remote-as1 permit 20

match community community-2

set local-preference 150

These configuration effect S2 routing table like below.

However, it does not effect S3 and S4, even if the community value is left.

Reference

[ 1 ] https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/28784-bgp-community.html

[ 2 ] http://www.ciscopress.com/articles/article.asp?p=2756480&seqNum=12

[ 3 ] https://blog.naver.com/happy_jhyo/221291791846

저작자표시 비영리 변경금지

'Network Engineering > Basic Learning' 카테고리의 다른 글

How does the OSPF cost work? (0)	2019.07.18
How to work BGP synchronize and next hop self with Nexus? (0)	2019.07.11
How does the multicast (PIM sparse mode) work with MSDP? (0)	2019.06.07
How SSL/TLS handshake can be done? (0)	2018.12.18
How to calculate sequence number of the TCP/IP packets? (0)	2018.12.17

How to outbound external connection of GN3 devices over remote server?

I use GNS3 simulator to study network feature sometimes. There is many instruction over internet. In this post, I will introduce how to use NAT fuction to connect to interet for outbound traffic.

1. Pre-requisite.

I have local GNS3 client and remote server over Packet.net and AWS Baremetal cloud. In my case, my remote server is the Linux (Ubuntu 16.04) host. After then, I uploaded CiscoNX v9000 in my remote server.

This is the my environment to re-produce in this post.

2. About NAT appliance (DHCP feature).

In GNS3, there is NAT appliance. It has the role to connect the physical interface on remote server virtually. This NAT appliance offers DHCP feature to assign IP address. This IP address determined the next hop against the Cisco switch/router. Thus, the Cisco switch/router should have DHCP feature.

feature dhcp

ip route 0.0.0.0/0 192.168.122.1

no ip dhcp relay

no ipv6 dhcp relay

interface Ethernet1/1

no switchport

ip address dhcp

no shutdown

After this configuration, I can verify the interface status with "show ip int br" command

And "ip route 0.0.0.0/0 192.168.122.1" is written. In the Linux host (remote server), I can see the interfaces like below.

With this interfaces, the packet will transfer to external side. I can see the masqurade rule in "iptables table" like below.

Now, I can send traffic to outside on switch 1. Please noteh that it is not possible on switch 2.

switch 1(config)# ip domain-lookup

switch 1(config)# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=53 time=19.257 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=53 time=2.484 ms

3. Configuration NAT Inside and Outside

Switch 1 can send the packet to outside, however switch 2 can not. Because "192.168.122.0/24" network can only be masquraded in the remote server. This is the reason why the switch 1 has NAT feature. In this instruction, there is the explation for Cisco NAT concept.

Inside source translation is for inside --> outside traffic. Outside source translation is for outside --> inside traffic. At first, I will make the direction on Cisco switch 1.

feature nat

interface Ethernet1/1
  no switchport
  ip address dhcp
  ip nat outside
  no shutdown

interface Ethernet1/2
  no switchport
  ip address 172.12.1.12/16
  ip nat inside
  no shutdown

4. Create Rule (NAT Policy) for outbound traffic.

In this post, I handle only outbound traffic. The main factor is that IP address for all traffic to outside should be changed with Switch 1 interface ethernet 1/1 IP address. In this post, It will be useful. I want all traffic to be sent.

ip access-list 1
10 permit ip any any

ip nat inside source list 1 interface Ethernet1/1 overload

5. Configure inside network (Switch 2).

So far, I made NAT firewall. From this part, it can assume internet network. However, I only use single switch/router simply.

ip route 0.0.0.0/0 172.12.1.12

interface Ethernet1/2

no switchport

ip address 172.12.2.12/16

no shutdown

This is normal configuration. There is nothing special. After default configuration. I can verify the outbound connection like below over switch 2.

It works now.

Reference

[ 1 ] https://docs.gns3.com/1c2Iyiczy6efnv-TS_4Hc7p11gn03-ytz9ukgwFfckDk/index.html

[ 2 ] https://docs.gns3.com/appliances/cisco-nxosv9k.html

[ 3 ] https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/interfaces/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_Interfaces_Configuration_Guide_7x/b_Cisco_Nexus_9000_Series_NX-OS_Interfaces_Configuration_Guide_7x_chapter_01100.html#concept_F5BFDE98ABA749859F5AD710AC61EFCD

[ 4 ] https://onlyit.tistory.com/entry/How-to-use-a-nat-node-in-gns3

저작자표시 비영리 변경금지

'Network Engineering > OpenSource' 카테고리의 다른 글

How to configure Simple Internal BGP with Route Reflector over FRRouting (include Installation)? (0)	2020.06.03
How to configure Internal BGP and Router Reflector with Bird? (0)	2020.05.11
How to configure External BGP with Bird? (0)	2020.05.10
How to Configuration VXLAN in Ubuntu 16.04 (0)	2018.08.16
How to Configure “ipvsadm” in Ubuntu (0)	2018.08.10

How does the multicast (PIM sparse mode) work with MSDP?

In this post, I will generate the multicast environment with Nx9000v on GNS3. I will handle the multicast with PIM sparse mode.

1. Pre-requiste for Test environments

I will produce this environment to generate the multicast.

Before I make Multicast environment, I need to prepare NAT for outbound traffic and Multicast test scripts. This is the sample configuration for NAT outbound traffic.

conf t

feature dhcp

feature nat

!

ip nat translation max-entries 1023

!

no ip dhcp relay

no ipv6 dhcp relay

!

inter eth 1/9

no sw

ip add dhcp

ip nat out

no shut

exit

inter et 1/7

no sw

ip add 100.15.5.17/16

ip nat ins

no shut

exit

inter et 1/8

no sw

ip add 100.25.5.18/16

ip nat ins

no shut

exit

!

ip acc 1

10 per ip any any

exit

!

ip nat inside source list 1 interface et1/9 overload

ip route 10.0.0.0/24 100.15.1.17

ip route 10.0.0.0/24 100.25.2.18

ip route 20.0.0.0/24 100.15.1.17

ip route 20.0.0.0/24 100.25.2.18

ip route 100.0.0.0/8 100.15.1.17

ip route 100.0.0.0/8 100.25.2.18

ip route 1.1.1.1/32 100.15.1.17

ip route 1.1.1.1/32 100.25.2.18

ip route 2.2.2.2/32 100.15.1.17

ip route 2.2.2.2/32 100.25.2.18

ip route 3.3.3.3/32 100.15.1.17

ip route 3.3.3.3/32 100.25.2.18

ip route 4.4.4.4/32 100.15.1.17

ip route 4.4.4.4/32 100.25.2.18

end

!

Also I attach the multicast example below

2. Configuration for default environment.

2-1. Configure Core swtich/router

I will make full-mesh connectivity. There are four switch/router. I will name as s1, s2, s3 and s4. On those switch/router, I will run OSPF routing to announce loopback addresses for Router ID and RP point.

s1

s2

s3

s4

conf t
!
switchname s1
!
feature ospf
router ospf 1
router-id 1.1.1.1
exit
!
inter lo 0
ip add 1.1.1.1/32
ip router ospf 1 area 0.0.0.0
no shut
exit
!
inter et 1/7
no sw
ip add 100.15.1.17/16
no shut
exit
!
inter et 1/1
no sw
ip add 100.12.1.11/16
ip router ospf 1 area 0.0.0.0
no shut
exit
!
inter et 1/2
no sw
ip add 100.13.1.12/16
ip router ospf 1 area 0.0.0.0
no shut
exit
!
inter et 1/3
no sw
ip add 100.14.1.13/16
ip router ospf 1 area 0.0.0.0
no shut
exit
!
ip route 0.0.0.0/0 100.15.5.17
ip route 0.0.0.0/0 100.12.2.11 100
end
!

conf t
!
switchname s2
!
feature ospf
router ospf 1
router-id 2.2.2.2
exit
!
inter lo 0
ip add 2.2.2.2/32
ip router ospf 1 area 0.0.0.0
no shut
exit
!
inter et 1/8
no sw
ip add 100.25.2.18/16
no shut
exit
!
inter et 1/1
no sw
ip add 100.12.2.11/16
ip router ospf 1 area 0.0.0.0
no shut
exit
!
inter et 1/2
no sw
ip add 100.24.2.12/16
ip router ospf 1 area 0.0.0.0
no shut
exit
!
inter et 1/3
no sw
ip add 100.23.2.13/16
ip router ospf 1 area 0.0.0.0
no shut
exit
!
ip route 0.0.0.0/0 100.25.5.18
ip route 0.0.0.0/0 100.12.1.11 100
end
!

conf t
!
switchname s3
!
feature ospf
router ospf 1
router-id 3.3.3.3
exit
!
inter lo 0
ip add 3.3.3.3/32
ip router ospf 1 area 0.0.0.0
no shut
exit
!
inter et 1/1
no sw
ip add 100.34.3.11/16
ip router ospf 1 area 0.0.0.0
no shut
exit
!
inter et 1/2
no sw
ip add 100.13.3.12/16
ip router ospf 1 area 0.0.0.0
no shut
exit
!
inter et 1/3
no sw
ip add 100.23.3.13/16
ip router ospf 1 area 0.0.0.0
no shut
exit
!
ip route 0.0.0.0/0 1.1.1.1
ip route 0.0.0.0/0 2.2.2.2
!
vlan 10
name vlan10
exit
!
feature interface-vlan
inter vlan10
no shut
ip add 10.0.0.1/24
exit
!
inter et 1/7, et 1/8
sw mode ac
sw ac vlan 10
no shut
exit
!

----------------------------------
!
conf t
!
inter vlan 10
ip router ospf 1 area 0.0.0.0
exit
!
----------------------------------
conf t
!
feature pim
!
ip pim rp-address 99.99.99.99
!
inter eth 1/1, eth 1/2, eth 1/3
ip pim sparse-mode
exit
!
inter vlan 10
ip pim sparse-mode
exit
!

conf t
!
switchname s4
!
feature ospf
router ospf 1
router-id 4.4.4.4
exit
!
inter lo 0
ip add 4.4.4.4/32
ip router ospf 1 area 0.0.0.0
no shut
exit
!
inter et 1/1
no sw
ip add 100.34.4.11/16
ip router ospf 1 area 0.0.0.0
no shut
exit
!
inter et 1/2
no sw
ip add 100.24.4.12/16
ip router ospf 1 area 0.0.0.0
no shut
exit
!
inter et 1/3
no sw
ip add 100.14.4.13/16
ip router ospf 1 area 0.0.0.0
no shut
exit
!
ip route 0.0.0.0/0 1.1.1.1
ip route 0.0.0.0/0 2.2.2.2
!
vlan 20
name vlan20
exit
!
feature interface-vlan
inter vlan20
no shut
ip add 20.0.0.1/24
exit
!
inter et 1/7
sw mode ac
sw ac vlan 20
no shut
exit
!

----------------------------------
!
conf t
!
inter vlan 20
ip router ospf 1 area 0.0.0.0
exit
!
----------------------------------
conf t
!
feature pim
!
ip pim rp-address 99.99.99.99
!
inter eth 1/1, eth 1/2, eth 1/3
ip pim sparse-mode
exit
!
inter vlan 20
ip pim sparse-mode
exit
!

In s1 and s2, there are 2 kinds of loopback addresses. One is for the switch/router ID, the other is for the RP address. For loopback address for RP, I will utilize "ghost loopback address" method. Please look at the loopback interface 1 in s1 and s2.

s1	s2
conf t ! feature pim ! inter lo 1 ip address 99.99.99.99/32 ip router ospf 1 area 0.0.0.0 ip ospf network point ip pim sparse-mode no shutdown exit ! ip pim rp-address 99.99.99.99 ! inter eth 1/1, eth 1/2, eth 1/3 ip pim sparse-mode exit !	conf t ! feature pim ! inter lo 1 ip address 99.99.99.99/24 ip router ospf 1 area 0.0.0.0 ip ospf network point ip pim sparse-mode no shutdown exit ! ip pim rp-address 99.99.99.99 ! inter eth 1/1, eth 1/2, eth 1/3 ip pim sparse-mode exit !

S1 is the main RP server in normal status. However, it will be changed to s2 when S1 is failed without IP address change. Because of this, I need MSDP (Multicast Source Discovery Protocol). I will handle in later. To announce the network with subnet of loopback interface into OSPF, "Point to Point" is necesary. Now I can see the routing table on S3 and S4 switch/router.

s3# show ip route ospf-1

s4# show ip route ospf-1

1.1.1.1/32, ubest/mbest: 1/0
    *via 100.13.1.12, Eth1/2, [110/41], 3d00h, ospf-1, intra
2.2.2.2/32, ubest/mbest: 1/0
    *via 100.23.2.13, Eth1/3, [110/41], 3d00h, ospf-1, intra
4.4.4.4/32, ubest/mbest: 1/0
    *via 100.34.4.11, Eth1/1, [110/41], 3d00h, ospf-1, intra
20.0.0.0/24, ubest/mbest: 1/0
    *via 100.34.4.11, Eth1/1, [110/80], 03:33:46, ospf-1, intra
99.99.99.0/24, ubest/mbest: 1/0
    *via 100.23.2.13, Eth1/3, [110/41], 00:44:41, ospf-1, intra
99.99.99.99/32, ubest/mbest: 1/0
    *via 100.13.1.12, Eth1/2, [110/41], 00:44:41, ospf-1, intra
100.12.0.0/16, ubest/mbest: 2/0
    *via 100.13.1.12, Eth1/2, [110/80], 3d00h, ospf-1, intra
    *via 100.23.2.13, Eth1/3, [110/80], 3d00h, ospf-1, intra
100.14.0.0/16, ubest/mbest: 2/0
    *via 100.13.1.12, Eth1/2, [110/80], 3d00h, ospf-1, intra
    *via 100.34.4.11, Eth1/1, [110/80], 3d00h, ospf-1, intra
100.24.0.0/16, ubest/mbest: 2/0
    *via 100.23.2.13, Eth1/3, [110/80], 3d00h, ospf-1, intra
    *via 100.34.4.11, Eth1/1, [110/80], 3d00h, ospf-1, intra

1.1.1.1/32, ubest/mbest: 1/0
    *via 100.14.1.13, Eth1/3, [110/41], 3d00h, ospf-1, intra
2.2.2.2/32, ubest/mbest: 1/0
    *via 100.24.2.12, Eth1/2, [110/41], 3d00h, ospf-1, intra
3.3.3.3/32, ubest/mbest: 1/0
    *via 100.34.3.11, Eth1/1, [110/41], 3d00h, ospf-1, intra
10.0.0.0/24, ubest/mbest: 1/0
    *via 100.34.3.11, Eth1/1, [110/80], 03:34:26, ospf-1, intra
99.99.99.0/24, ubest/mbest: 1/0
    *via 100.24.2.12, Eth1/2, [110/41], 00:45:13, ospf-1, intra
99.99.99.99/32, ubest/mbest: 1/0
    *via 100.14.1.13, Eth1/3, [110/41], 00:45:13, ospf-1, intra
100.12.0.0/16, ubest/mbest: 2/0
    *via 100.14.1.13, Eth1/3, [110/80], 3d00h, ospf-1, intra
    *via 100.24.2.12, Eth1/2, [110/80], 3d00h, ospf-1, intra
100.13.0.0/16, ubest/mbest: 2/0
    *via 100.14.1.13, Eth1/3, [110/80], 3d00h, ospf-1, intra
    *via 100.34.3.11, Eth1/1, [110/80], 3d00h, ospf-1, intra
100.23.0.0/16, ubest/mbest: 2/0
    *via 100.24.2.12, Eth1/2, [110/80], 3d00h, ospf-1, intra
    *via 100.34.3.11, Eth1/1, [110/80], 3d00h, ospf-1, intra

In red text above, "100.100.100.100" is the RP address for multicast. At this time, the destination should be s1. It will be changed to s2 by "100.100.100.0/24", when s1 is failed.

2-2. Configure the Host (PC, Labtop) network.

s3 and s4 is the gateway for each host network. In my scenario, I will use "10.0.0.0/24" for PC1 and "20.0.0.0/24" for PC2.

I have already done for the gateway above.

S3

S4

!

conf t

!

inter vlan 10

ip router ospf 1 area 0.0.0.0

exit

!

inter eth 1/1, eth 1/2, eth 1/3

ip pim sparse-mode

exit

!

inter vlan 10

ip pim sparse-mode

exit

!

conf t

!

inter vlan 20

ip router ospf 1 area 0.0.0.0

exit

!

inter eth 1/1, eth 1/2, eth 1/3

ip pim sparse-mode

exit

!

inter vlan 20

ip pim sparse-mode

exit

!

Now I will configure the PC network interface. In my case I will use "Ubuntu Desktop". In this instruction, I can see how to install "ubuntu" in GNS3. After installation, I can open the console like below.

After login, I can set the network interface like below. I need to update file in "/etc/network/interfaces".

After set both of hosts, I can send ICMP packet each other.

However, there is one more thing necessary. To Join and receive the multicast packet. I need to define the IGMP version on Linux host sometimes. This instruction will be helpful.

echo "2" >> /proc/sys/net/ipv4/conf/<interface>/force_igmp_version

In my case, Host 2 and Host 3 will be receiver, therefore it will be like below

3. Configuraton for Multicast environment.

3-1. Configure for default multicast

In fact, I have already done for multicast routing, if you follow sample configuration. This instruction will be helpful to understand how to configure.

S1

S2

S3

S4

conf t

!

feature pim

!

inter lo 1

ip address 99.99.99.99/32

ip router ospf 1 area 0.0.0.0

ip ospf network point

ip pim sparse-mode

no shutdown

exit

!

ip pim rp-address 99.99.99.99

!

inter eth 1/1, eth 1/2, eth 1/3

ip pim sparse-mode

exit

!

conf t

!

feature pim

!

inter lo 1

ip address 99.99.99.99/24

ip router ospf 1 area 0.0.0.0

ip ospf network point

ip pim sparse-mode

no shutdown

exit

!

ip pim rp-address 99.99.99.99

!

inter eth 1/1, eth 1/2, eth 1/3

ip pim sparse-mode

exit

!

conf t

!

feature pim

!

ip pim rp-address 99.99.99.99

!

inter eth 1/1, eth 1/2, eth 1/3

ip pim sparse-mode

exit

!

inter vlan 10

ip pim sparse-mode

exit

!

conf t

!

feature pim

!

ip pim rp-address 99.99.99.99

!

inter eth 1/1, eth 1/2, eth 1/3

ip pim sparse-mode

exit

!

inter vlan 20

ip pim sparse-mode

exit

!

Now, I can test multicast routing with sample script. I can get the result like below.

I success to send multicast traffic. However, I still leave MSDP. "99.99.99.99" is the RP which is S1. I worry the S1 fail situation. MSDP is one of good solution. Please read next step.

3-2. Configure for MSDP.

Before, I configure for MSDP. Any information was not shared each other. (S1 and S2 are peer connection for MSDP). I run command "show ip msdp route" and "show ip msdp sa-cache".

Because of this, the routing information should be registered again on S2, when S1 is failed. Now, I will follow this instruction. At first, I will MSDP configuration to share source information between s1 and s2.

In above, there is "ip msdp cache-sa-state" command for caching. However, there is no command in Nx9000v in my case. Therefore, my configuration should be below.

s1

s2

feature msdp

ip msdp originator-id loopback0

ip msdp peer 1.1.1.2 connect-source loopback0

feature msdp

ip msdp originator-id loopback0

ip msdp peer 1.1.1.1 connect-source loopback0

I can check the status with "show ip msdp summary"

I can also verify the status with again "show ip msdp route" and "show ip msdp sa-cache".

In fact, I can not understand this effect.

3-3. Verify the MSDP effect.

Before MSDP configuration, I will shutodown loopback 1 (RP) of S1 switch/router. In S2 switch/router, there is no multicast source information.

After sender request, the source information is updated. This is normal case

Now, I will configure MSDP. I will shutdown loopback 1 of switch/router S1 again. In S2,

Multicast routing information is updated directly.

Sample Configurations

Reference

[ 1 ] https://www.osboxes.org/ubuntu/#ubuntu-14_04-vmware

[ 2 ] https://docs.gns3.com/1RpM21DdgL2pCNtIrw6e9Yf52tRjYZIe46LMeESl-jy4/

[ 3 ] https://www.cisco.com/c/en/us/td/docs/ios/12_2/ip/configuration/guide/fipr_c/1cfmsdp.html#wp1000963

[ 4 ] https://createnetech.tistory.com/40?category=672584

[ 5 ] https://pymotw.com/2/socket/multicast.html

[ 6 ] https://sites.google.com/site/miclinuxcorner/technology/multicast-routing

[ 7 ] https://www.cisco.com/c/en/us/support/docs/ip/ip-multicast/9356-48.html#msdp

저작자표시 비영리 변경금지

'Network Engineering > Basic Learning' 카테고리의 다른 글

How does the OSPF cost work? (0)	2019.07.18
How to work BGP synchronize and next hop self with Nexus? (0)	2019.07.11
What is basic BGP community concept? (0)	2019.06.18
How SSL/TLS handshake can be done? (0)	2018.12.18
How to calculate sequence number of the TCP/IP packets? (0)	2018.12.17

netgo

What is basic BGP community concept?

'Network Engineering > Basic Learning' 카테고리의 다른 글

How to outbound external connection of GN3 devices over remote server?

'Network Engineering > OpenSource' 카테고리의 다른 글

How does the multicast (PIM sparse mode) work with MSDP?

'Network Engineering > Basic Learning' 카테고리의 다른 글

+ Recent posts

티스토리툴바