Skip to main content

NHS @ NHRP

Hub Router configure

 HUB(config)#interface Tunnel1 
HUB(config-if)# ip address 10.10.10.1 255.255.255.0 
HUB(config-if)# tunnel source FastEthernet0/0 
HUB(config-if)# tunnel mode gre multipoint 
HUB(config-if)#ip nhrp map multicast dynamic
HUB(config-if)#ip nhrp authentication OutBox 
HUB(config-if)# ip nhrp network-id 100
SPOKE Router
interface Tunnel1
Spoke_01(config-if)# ip address 10.10.10.2 255.255.255.0 
Spoke_01(config-if)#tunnel source FastEthernet0/0
Spoke_01(config-if)#tunnel mode gre multipoint 
Spoke_01(config-if)# ip nhrp authentication OutBox
Spoke_01(config-if)# ip nhrp network-id 100

 Spoke_01(config-if)#ip nhrp map 10.10.10.1 203.81.1.2
*Apr  5 03:33:03.307: NHRP: Tunnel1: Cache add for target 10.10.10.1/32 next-hop 10.10.10.1
*Apr  5 03:33:03.311:            203.81.1.2
*Apr  5 03:33:03.331: NHRP: Inserted subblock node for cache: Target Inserted subblock node for cache: Target 10.10.10.1/32nhop 10.10.10.1
*Apr  5 03:33:03.335: NHRP: Converted internal static cache entry for 10.10.10.1/32 interface Tunnel1 to external

 Spoke_01(config-if)#ip nhrp nhs 10.10.10.1

*Apr  5 03:34:23.247: NHRP: Setting 'used' flag on cache entry with nhop: 10.10.10.1
*Apr  5 03:34:23.251: NHRP: NHRP successfully mapped '10.10.10.1' to NBMA 203.81.1.2

 After Spoke router add NHRP NHS config it send request to HUB router.

 *Apr  5 04:15:54.963: NHRP: Setting 'used' flag on cache entry with nhop: 10.10.10.1
*Apr  5 04:15:54.967: NHRP: NHRP successfully mapped '10.10.10.1' to NBMA 203.81.1.2
*Apr  5 04:15:54.971: NHRP: Send Registration Request via Tunnel1 vrf 0, packet size: 106
*Apr  5 04:15:54.971:  src: 10.10.10.2, dst: 10.10.10.1
*Apr  5 04:15:54.971:  (F) afn: AF_IP(1), type: IP(800), hop: 255, ver: 1
*Apr  5 04:15:54.971:      shtl: 4(NSAP), sstl: 0(NSAP)
*Apr  5 04:15:54.971:      pktsz: 106 extoff: 52
*Apr  5 04:15:54.971:  (M) flags: "unique nat ", reqid: 1
*Apr  5 04:15:54.971:      src NBMA: 203.81.2.2
*Apr  5 04:15:54.971:      src protocol: 10.10.10.2, dst protocol: 10.10.10.1
*Apr  5 04:15:54.971:  (C-1) code: no error(0)
*Apr  5 04:15:54.971:        prefix: 32, mtu: 17916, hd_time: 7200
*Apr  5 04:15:54.971:        addr_len: 0(NSAP), subaddr_len: 0(NSAP), proto_len: 0, pref: 0
*Apr  5 04:15:55.063: NHRP: Receive Registration Reply via Tunnel1 vrf 0, packet size: 126
*Apr 
Spoke_01(config-if)#5 04:15:55.067:  (F) afn: AF_IP(1), type: IP(800), hop: 255, ver: 1
*Apr  5 04:15:55.067:      shtl: 4(NSAP), sstl: 0(NSAP)
*Apr  5 04:15:55.067:      pktsz: 126 extoff: 52
*Apr  5 04:15:55.071:  (M) flags: "unique nat ", reqid: 1
*Apr  5 04:15:55.071:      src NBMA: 203.81.2.2
*Apr  5 04:15:55.071:      src protocol: 10.10.10.2, dst protocol: 10.10.10.1
*Apr  5 04:15:55.075:  (C-1) code: no error(0)
*Apr  5 04:15:55.075:        prefix: 32, mtu: 17916, hd_time: 7200
*Apr  5 04:15:55.075:        addr_len: 0(NSAP), subaddr_len: 0(NSAP), proto_len: 0, pref: 0

 HUB Router
HUB#
*Apr  5 04:15:54.807: NHRP: Receive Registration Request via Tunnel1 vrf 0, packet size: 106
*Apr  5 04:15:54.811:  (F) afn: AF_IP(1), type: IP(800), hop: 255, ver: 1
*Apr  5 04:15:54.815:      shtl: 4(NSAP), sstl: 0(NSAP)
*Apr  5 04:15:54.815:      pktsz: 106 extoff: 52
*Apr  5 04:15:54.815:  (M) flags: "unique nat ", reqid: 1
*Apr  5 04:15:54.815:      src NBMA: 203.81.2.2
*Apr  5 04:15:54.815:      src protocol: 10.10.10.2, dst protocol: 10.10.10.1
*Apr  5 04:15:54.815:  (C-1) code: no error(0)
*Apr  5 04:15:54.815:        prefix: 32, mtu: 17916, hd_time: 7200
*Apr  5 04:15:54.815:        addr_len: 0(NSAP), subaddr_len: 0(NSAP), proto_len: 0, pref: 0
*Apr  5 04:15:54.847: NHRP: Send Registration Reply via Tunnel1 vrf 0, packet size: 126
*Apr  5 04:15:54.847:  src: 10.10.10.1, dst: 10.10.10.2
*Apr  5 04:15:54.847:  (F) afn: AF_IP(1), type: IP(800), hop: 255, ver: 1
*Apr  5 04:15:54.847:      shtl: 4(NSAP), sstl: 0(NSAP)
*Apr  5 04:15:54.847:      pktsz: 126 extoff: 52
*Apr  5 04:15:54.847:  (M) flags: "unique nat ", reqid: 1
*Apr  5 04:15:54.847:      src NBMA: 203.81.2.2
*Apr  5 04:15:54.847:      src protocol: 10.10.10.2, dst protocol: 10.10.10.1
*Apr  5 04:15:54.847:  (C-1) code: no error(0)
*Apr
HUB#  5 04:15:54.847:        prefix: 32, mtu: 17916, hd_time: 7200
*Apr  5 04:15:54.847:        addr_len: 0(NSAP), subaddr_len: 0(NSAP), proto_len: 0, pref: 0

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

Access-list at SVI

SVI (Switch Virtual Interfaces) We use the SVI for inter vlan routing. In this scenario I will configure the access list with SVI. In this scenario I want to permit vlan 10 network to vlan 50 Server farm. Vlan 10 and vlan 20 can communicate each other. First create vlan and then interface vlan#. Switch(config)#vlan 10 Switch(config)#interface vlan 10 Switch(config-if)#ip address 192.168.10.254 255.255.255.0 Switch(config)#vlan 20 Switch(config)#interface vlan 20 Switch(config-if)#ip address 192.168.20.254 255.255.255.0 Switch(config)#vlan 50 Switch(config)#interface vlan 50 Switch(config-if)#ip address 192.168.50.254 255.255.255.0 when we finish the vlan interface create make sure the switch port are belong to each vlan. Port to vlan assign configure is Switch(config)#interface g0/1 Switch(config-if)#switchport access vlan 10 Switch(config)#interface g0/2 Switch(config-if)#switchport access vlan 20 Switch(config)#int...
1 comment
Read more

BGP Disable Connected Check and EBGP Multi Hop

Figure 1.1 In this scenario I use OSPF for TCP reachability. We can see the difference 'disable connected' check and 'EBGP multihop'. We can use both for EBGP neighbor connection with loopback address. Disable connected check This command used to disable the connection verification process for ebgp. Use for ebgp neighbor are directly connected and they using the loopback address for peering. It not increment TTL but neighbor must reachable at single hop. EBGP multihop This command can use for ebgp neighbor are not directly connected. It increment TTL. R1 router bgp 100  neighbor 2.2.2.2 remote-as 200  neighbor 2.2.2.2 disable-connected-check  neighbor 2.2.2.2 update-source Loopback0  neighbor 3.3.3.3 remote-as 300  neighbor 3.3.3.3 ebgp-multihop 2  neighbor 3.3.3.3 update-source Loopback0 R2 router bgp 200  neighbor 1.1.1.1 remote-as 100  neighbor 1.1.1.1 disable-connected-check  neighbor 1.1.1.1 update...
Post a Comment
Read more

How to setup AWS VPC Peering (VPC to VPC)

    Hi Everyone... ဒီကနေ့တော့ VPC Peering လုပ်တဲ့ အကြောင်းလေးပြောပြပေးသွားမှာပါ။ VPC peering ဘာလို့လုပ်တာလဲ ဘယ်အချိန်တွေမှာသုံးတာလဲဆိုတာကို ကြည့်ရအောင်... သိတဲ့ အတိုင်း ပဲ AWS networking မှာ VPC ကမပါမဖြစ်အရေးပါပါတယ် AWS account တခုရဲ့ AWS region တခုမှာ VPC 5ခုအများဆုံး ထားလို့ရပါတယ်... AZ မဟုတ်ပါဘူး အဲ့ဒါလေးတော့သတိထားရမှာပါ.. peering က one to one ဖြစ်တဲ့အတွက် VPC များလာရင်တော့ configuation complex ဖြစ်လာပါမယ်၊ နောက်တခုကတခြား AWS account တွေရဲ့ VPC နဲ့ချိတ်ဆက်သုံးချင်တာတွေလဲရှိနိုင်ပါတယ် အဲ့လို VPC တွေများလာမယ်ဆိုရင်တော့ Transit Gateway ကိုသုံးတာက ပိုစိတ်ချမ်းသာရပါတယ်။ VPC နည်းသေးတယ် နောင်လဲတိုးလာဖို့ မရှိသေးဘူးဆိုရင်တော့ အခုနည်းလမ်းက ပိုအဆင်ပြေပါတယ်. ဆိုတော့ Pubilc VPC နဲ့ Private VPC ဆိုပြီးရှိတယ်ဆိုပါစို့ Pubilc VPC ထဲက webserver က Private VPC ထဲ က database ကိုလှမ်းသုံးချင်တယ်ဆိုရင် အဲ့ဒီ VPC တွေကို peering လုပ်ပေးဖို့လိုပါတယ်.. Peering လုပ်မယ်ဆိုရင်တော့ VPC ထဲက peering connections ကိုရွေးရပါမယ်. ပြီးရင်တော့ Create peering connections ကို click ပါ၊ ဒီ box ကျလာရင်တော့ ...
Post a Comment
Read more