nx.os.and.cisco.nexus.switching.2nd.edition.1587143046

Libya# show ip ospf neighbor detail
Neighbor 192.168.1.2, interface address 192.168.1.41
In the area 0 via interface TenGigabitEthernet1/49
Neighbor priority is 1, State is FULL, 6 state changes
DR is 192.168.1.42 BDR is 192.168.1.41
Options is 0x42
Dead timer due in 00:00:37
Neighbor is up for 00:00:38
Index 1/1, retransmission queue length 0, number of
retransmission 1
First 0x0(0)/0x0(0) Next 0x0(0)/0x0(0)
Last retransmission scan length is 1, maximum is 1
Last retransmission scan time is 0 msec, maximum is 0
msec
! The output from NX-OS shows that the area is area
0.0.0.0
Egypt# show ip ospf ne detail
Neighbor 192.168.1.3, interface address 192.168.1.42
Process ID DataCenter1 VRF default, in area 0.0.0.0
via interface Ethernet1/18
State is FULL, 5 state changes, last change 00:05:49
Neighbor priority is 1
DR is 192.168.1.42 BDR is 192.168.1.41
Hello options 0x12, dbd options 0x52
Last non-hello packet received 00:01:46
Dead timer due in 00:00:33
In a data center’s distribution or aggregation layer, it is common to have multiple VLAN
interfaces that, in turn, need to be advertised to the network at large. By default, when OSPF
is enabled on the VLAN interface, it sends and receives hellos. If a neighbor is detected,
OSPF attempts to form an adjacency. Although this default behavior is wanted, there might
be designs where forming multiple OSPF adjacencies between the same pair of switches is
not wanted because of the potential impact of network convergence time and unnecessary
duplicate next hops. In configurations such as this, you can use the passive-interface
command, as demonstrated in Example 3-39. A passive interface accomplishes the
requirement of advertising the subnet via OSPF but also instructs the OSPF process to not
listen to hellos on the interfaces configured to be passive.
Example 3-39. OSPF Passive Interface with a Numeric Process ID
Click here to view code image
Congo# config t
Congo(config)# int vlan100