Saturday, July 12, 2014

OTV Unicast-Mode Configuration Example Using OTV In Path Design - OTV Series Part 1

Note:- 100.100.100.100 is Redundant Unicast Adjacency Server In This Configuration Example & DC1-N7K-1 Is Primary Unicast Adj. Server In This Configuration Example.




Configuration Template Used In Demo:

DC1-N7K-2
+++++++++

!
en
!
conf t
!
vlan 100
 name OTV-SITE-VLAN
 exit
!
vlan 200
 name OTV-EXTEND-VLAN
 exit
!
int e1/9
 switchport
 switchport mode trunk
 switchport trunk allowed vlan 100,200
 no sh
 exit
!
feature interface-vlan
!
int vlan 200
 ip add 200.0.0.1/24
 no sh
 exit
!
end
!


DC2-N7K-2
+++++++++

!
en
!
conf t
!
vlan 100
 name OTV-SITE-VLAN
 exit
!
vlan 200
 name OTV-EXTEND-VLAN
 exit
!
int e1/18
 switchport
 switchport mode trunk
 switchport trunk allowed vlan 100,200
 no sh
 exit
!
feature interface-vlan
!
int vlan 200
 ip add 200.0.0.2/24
 no sh
 exit
!
end
!


DC1-N7K-1
+++++++++

!
en
!
conf t
!
vlan 100
 name OTV-SITE-VLAN
 exit
!
vlan 200
 name OTV-EXTEND-VLAN
 exit
!
system jumbo 9216
!
feature otv
!
int e1/5
 switchport
 switchport mode trunk
 switchport trunk allowed vlan 100,200
 no sh
 exit
!
otv site-identifier 0x01
!
otv site-vlan 100
 exit
!
interface overlay 1
 otv join-interface e1/1
 otv adjacency-server unicast-only
 otv use-adjacency-server 10.1.13.3 100.100.100.100 unicast-only
 otv extend-vlan 200
 no sh
 exit
!


DC2-N7K-1
+++++++++

!
en
!
conf t
!
vlan 100
 name OTV-SITE-VLAN
 exit
!
vlan 200
 name OTV-EXTEND-VLAN
 exit
!
system jumbo 9216
!
feature otv
!
int e1/12
 switchport
 switchport mode trunk
 switchport trunk allowed vlan 100,200
 no sh
 exit
!
otv site-identifier 0x02
!
otv site-vlan 100
 exit
!
interface overlay 1
 otv join-interface e1/10
 otv use-adjacency-server 10.1.13.3 100.100.100.100 unicast-only
 otv extend-vlan 200
 no sh
 exit
!


Further Readings:

http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/wan_otv/configuration/xe-3s/wan-otv-xe-3s-book/wan-otv-adj-server.html

http://www.cisco.com/c/en/us/products/collateral/switches/nexus-7000-series-switches/white_paper_c11-644634.html

http://www.cisco.com/en/US/docs/solutions/Enterprise/Data_Center/DCI/5.0/OTVunicast.pdf

https://supportforums.cisco.com/document/64881/troubleshooting-arp-issues-across-otv

https://supportforums.cisco.com/document/65531/otv-silent-host-connectivity-problem

HTH...
Deepak Arora
Evil CCIE

Sunday, July 6, 2014

Nexus 5K FEX, vPC & EvPC - All In One




Note: During the Video Demo the topology shown was little incorrect. Refer topology posted above during video demo.

N5K-1
+++++

!
en
!
conf t
!
vlan 100,200
 exit
!
feature vpc
!
feature lacp
!
feature fex
!
vpc domain 100
 role priority 1
 peer-keepalive dest 10.1.1.52 sou 10.1.1.51 vrf management
 exit
!
int e1/14-15
 channel-group 200 mode active
 no sh
 exit
!
interface port-channel 200
 switchport mode trunk
 vpc peer-link
 no sh
 exit
!
int e1/17
 channel-group 100
 no sh
 exit
!
int port-channel 100
 switchport mode fex
 fex associate 100
 vpc 100
 no sh
 exit
!
int e1/16
 channel-group 199
 no sh
 exit
!
int port-channel 199
 switchport mode fex
 fex associate 199
 vpc 199
 no sh
 exit
!
int e100/1/1,e109/1/1
 no sh
 channel-group 300
 exit
!
int port-channel 300
 switchport mode trunk
 switchport trunk allowed vlan 100,200
 spanning-tree port type edge trunk
 no sh
 exit
!
end
!
===========================================================

N5K-2
+++++

!
en
!
conf t
!
vlan 100,200
 exit
!
feature vpc
!
feature lacp
!
feature fex
!
vpc domain 100
 role priority 1
 peer-keepalive dest 10.1.1.51 sou 10.1.1.52 vrf management
 exit
!
int e1/14-15
 channel-group 200 mode active
 no sh
 exit
!
interface port-channel 200
 switchport mode trunk
 vpc peer-link
 no sh
 exit
!
int e1/16
 channel-group 100
 no sh
 exit
!
int port-channel 100
 switchport mode fex
 fex associate 100
 vpc 100
 no sh
 exit
!
int e1/17
 channel-group 199
 no sh
 exit
!
int port-channel 199
 switchport mode fex
 fex associate 199
 vpc 199
 no sh
 exit
!
int e100/1/1,e109/1/1
 no sh
 channel-group 300
 exit
!
int port-channel 300
 switchport mode trunk
 switchport trunk allowed vlan 100,200
 spanning-tree port type edge trunk
 no sh
 exit
!
end
!


Further Readings:
==============

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5500/sw/interfaces/7x/b_5500_Interfaces_Config_Guide_Release_7x/b_5500_Interfaces_Config_Guide_Release_7x_chapter_0101.html

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5500/sw/layer2/7x/b_5500_Layer2_Config_7x/b_5500_Layer2_Config_7x_chapter_01111.html

http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/mkt_ops_guides/513_n1_1/n5k_enhanced_vpc.html

http://www.cisco.com/c/en/us/support/docs/switches/nexus-5000-series-switches/116271-problem-vpc-00.html

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5500/sw/troubleshooting/guide/n5500_trouble/n5500_ts_vpc.html

HTH...
Deepak Arora
Evil CCIE

Wednesday, June 25, 2014

OSPF NSSA Route Optimization


Well if you like to design OSPF based networks, NSSA is one of key components that goes into it. Personally I don't prefer to include Stub Areas into the design unless I am very sure that it's not going to change since every now and than customers adds some sort of routing and mostly Static Routes into the network to make something work. Very good example would be proxies and firewalls. 

Now as per standard the Stub area doesn't allow you to redistribute. So adding NSSA into the design not only allow me take benefits of Stub based design by minimizing the LSDB size but still gives me flexibility of adding redistribution in future if requirement comes.

Now let me walk through different NSSA configuration options to you guys and show their effect on routing tables of NSSA Area Devices.

Here is the quick topology:





Let's start with basic NSSA configuration on R1 and see it's effect on R3's Routing table.

R1#sh run | s r o
router ospf 1
 log-adjacency-changes
 area 1 nssa
 redistribute eigrp 100 subnets
 network 1.1.1.1 0.0.0.0 area 0
 network 11.11.11.11 0.0.0.0 area 1
 network 12.0.0.1 0.0.0.0 area 0
 network 13.0.0.1 0.0.0.0 area 1



R3#sh ip ro os
     1.0.0.0/32 is subnetted, 1 subnets
O IA    1.1.1.1 [110/11] via 13.0.0.1, 00:01:07, FastEthernet0/1
     2.0.0.0/32 is subnetted, 1 subnets
O IA    2.2.2.2 [110/21] via 13.0.0.1, 00:01:07, FastEthernet0/1
     4.0.0.0/32 is subnetted, 1 subnets
O N2    4.4.4.4 [110/20] via 13.0.0.1, 00:01:02, FastEthernet0/1
     11.0.0.0/32 is subnetted, 1 subnets
O       11.11.11.11 [110/11] via 13.0.0.1, 00:10:10, FastEthernet0/1
     12.0.0.0/24 is subnetted, 1 subnets
O IA    12.0.0.0 [110/20] via 13.0.0.1, 00:01:07, FastEthernet0/1
     14.0.0.0/24 is subnetted, 1 subnets
O N2    14.0.0.0 [110/20] via 13.0.0.1, 00:01:02, FastEthernet0/1
     150.0.0.0/32 is subnetted, 1 subnets
O N2    150.0.0.1 [110/20] via 13.0.0.1, 00:01:02, FastEthernet0/1



> Now Let's add our first tweak into the equation:

R1#sh run | s r o
router ospf 1
 log-adjacency-changes
 area 1 nssa no-summary
 redistribute eigrp 100 subnets
 network 1.1.1.1 0.0.0.0 area 0
 network 11.11.11.11 0.0.0.0 area 1
 network 12.0.0.1 0.0.0.0 area 0
 network 13.0.0.1 0.0.0.0 area 1



R3#sh ip ro os
     4.0.0.0/32 is subnetted, 1 subnets
O N2    4.4.4.4 [110/20] via 13.0.0.1, 00:00:17, FastEthernet0/1
     11.0.0.0/32 is subnetted, 1 subnets
O       11.11.11.11 [110/11] via 13.0.0.1, 00:11:10, FastEthernet0/1
     14.0.0.0/24 is subnetted, 1 subnets
O N2    14.0.0.0 [110/20] via 13.0.0.1, 00:00:17, FastEthernet0/1
     150.0.0.0/32 is subnetted, 1 subnets
O N2    150.0.0.1 [110/20] via 13.0.0.1, 00:00:17, FastEthernet0/1
O*IA 0.0.0.0/0 [110/11] via 13.0.0.1, 00:00:22, FastEthernet0/1 


All Inter Area (IA) routes are replaced with single Inter Area Default Route.


> Now Let's add our Second tweak into the equation & remove First One:

R1(config)#router ospf 1
R1(config-router)#no area 1 nssa no-summary
R1(config-router)#area 1 nssa no-redistribution
R1(config-router)#end


R3#sh ip ro os
     1.0.0.0/32 is subnetted, 1 subnets
O IA    1.1.1.1 [110/11] via 13.0.0.1, 00:00:22, FastEthernet0/1
     2.0.0.0/32 is subnetted, 1 subnets
O IA    2.2.2.2 [110/21] via 13.0.0.1, 00:00:22, FastEthernet0/1
     11.0.0.0/32 is subnetted, 1 subnets
      11.11.11.11 [110/11] via 13.0.0.1, 00:02:43, FastEthernet0/1
     12.0.0.0/24 is subnetted, 1 subnets
O IA    12.0.0.0 [110/20] via 13.0.0.1, 00:00:22, FastEthernet0/1


With this tweak all my Inter Area (IA) routes are back but all my Redistributed/External Routes are gone.

What if I want best of both words to optimize LSDB size ?

R1(config)#router ospf 1
R1(config-router)#area 1 nssa no-redistribution no-summary
R1(config-router)#end


R3#sh ip ro os
     11.0.0.0/32 is subnetted, 1 subnets
O       11.11.11.11 [110/11] via 13.0.0.1, 00:03:56, FastEthernet0/1
O*IA 0.0.0.0/0 [110/11] via 13.0.0.1, 00:00:14, FastEthernet0/1


Now this looks really nice. But rule of thumb is that you should always verify end to end reachability. So let's verify that quickly:

R3#ping 2.2.2.2 so lo0

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds:
Packet sent with a source address of 3.3.3.3
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 24/36/52 ms

R3#ping 4.4.4.4 so lo0  < Exists in EIGRP World

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 4.4.4.4, timeout is 2 seconds:
Packet sent with a source address of 3.3.3.3
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/31/56 ms


HTH...
Deepak Arora
Evil CCIE

Cisco Exam Prices - Increased Again


Cisco has increased the prices again for certification exam including famous mammoth CCIE. The Lab Fee has been increased by 100$ and now is 1600$ where as written fee has been increased by 50$ and now is 400$.





HTH...
Deepak Arora
Evil CCIE

Friday, June 20, 2014

How To Bring Old "wr" Command Into Cisco Nexus To Save Configs - Quick Tip

Well I always use "wr" command short for "write" onto Cisco devices to save configurations. I am just too much use to with this syntax that I even don't remember when I used other command " copy run start" last time. :)

On the flip side Cisco Nexus Series platforms don't have "wr" command.

Well the way you can solve this problem is by creating an ALIAS for "copy run start" command and it should be helpful for Operations/Support Teams as well.

In Global configuration mode run the following command:

"cli alias name wr copy running-config startup-config

HTH....
Deepak Arora
Evil CCIE