Skip to main content

OSPF Interview questions - Part 1


What is the protocol number of OSPF?





89





What is the multicast address of OSPF messages?





  • 224.0.0.5 for OSPF All-routers multicast
  • 224.0.0.6 for OSPF All-Designated routers multicast




What are the OSPF hello packet timers?





Hello packets are sent every 10 seconds with the Dead timer being 40 seconds





Is it mandatory to have OSPF process ID the same on adjacent routers to form OSPF neighborship?





No





What is the impact of interface MTU mismatch on adjacent OSPF routers?





MTU is not checked during the formation of neighbor adjacency. However, mismatched MTU values impede in the successful exchange of Database Description (DD) packets and thereby prevent the neighbors from reaching the "FULL" neighborship state.





What are the types of OSPF LSAs?





  • Type 1 - Router LSA
  • Type 2 - Network LSA
  • Type 3 - Summary LSA
  • Type 4 - ASBR Summary LSA
  • Type 5 - External LSA
  • Type 6 - Multicast OSPF (MOSPF) LSA
  • Type 7 - Not-So-Stubby-Area (NSSA)LSA
  • Type 8 - External Attribute LSA for BGP




Who generates Type-1 LSA?





Type 1 LSAs (router link states) are created by each router in the area to describe itself, its interfaces and neighbors.





What OSPF network types does DR/BDR election occur?





DR and BDR election occurs only on NBMA and Broadcast network types





Where are Type 2 LSAs created?





Type 2 - Network LSAs are only created for networks where a DR has been elected.





Who generates Type 4 LSA?





Type 4 LSA's are generated by ABRs which have an ASBR in the area it touches with. Type 4 LSA is created by ABR to describe the ASBR and its cost to reach it.





What does a Type 3 LSA contain?





Type 3 LSA's contain the minimum information including:





  • i. The subnet
  • ii. The mask
  • iii. The cost which is known by the ABR to reach it




What mechanism does OSPF provide to reduce excessive traffic due to LSA re-flooding in large networks?





The LSA aging process can be disabled by setting the LSA - "Do Not Age" bit. This is an interface configuration as below. Post enabling this command, the periodic LSA re-flooding won't be necessary.






interface fa0/0
ip ospf flood-reduction






How can you prevent DR election on broadcast links (Ethernet)? / How can you prevent Type 2 LSAs being generated on broadcast links?





Configure the link as "point-to-point" OSPF network type.. This prevents DR election and Type 2 LSA generation.


Labels:

Comments

Post a Comment

Popular posts from this blog

Checkpoint - Exporting Objects in CSV format

Be it a Network Operations Manager, Security Architect or a Security Auditor, the people up the hierarchy always harangue the Security Engineers to compile the list of firewall objects or rules or policies or the traffic statistics and so on.. This can turn out to be quite hectic especially if there are no built in features to systematically provide the output in a "layman-readable" format. Come, Checkpoint's "Object Explorer..."  which not only provides the output in the "layman-readable" format, but also provides in-built filtering mechanisms, thereby ensuring that the Security Engineer doesn't have to rely on Google for building his scarce Microsoft Excel data filtering skills. The following screenshots will show how easy it is, with Checkpoint R80.10 to generate the firewall configuration inventory. On the SmartConsole Unified Portal, navigate to Menu >> Open Object Explorer... Select the Categories you wish to see in your output: Click o
Post a Comment
Read more

MITRE ATT&CK - Kerberos Vulnerabilities and Security

From the previous post, the summary of Kerberos authentication process is as below: For the initial authentication, the user’s client machine sends a request to the KDC  Authentication Service (AS) . The request includes details like the user’s username, and the date and time. All information except the username is encrypted using the hash of the user’s password. The KDC AS uses the username to look up its copy of the user’s password hash and uses it to decrypt the rest of the request. If the decryption is successful, that means the client used the correct password hash and the user has successfully authenticated. Once the user is authenticated, the KDC AS sends the user’s client a  ticket granting ticket   (TGT) . The TGT includes a unique session key and a timestamp that specifies how long that session is valid (normally 8 or 10 hours). Importantly, before sending the TGT, the KDC encrypts it using the password hash for a special account, the  KRBTGT account.  That password hash is s
2 comments
Read more

Tejas Jain - GCP Constraints & Random Facts

1.  Google Cloud Interconnect Security Cloud Interconnect does not encrypt the connection between your on-premises network and Google's network. Cloud VPN cannot be used with Dedicated Interconnect For additional security, use application-level encryption or your own VPN 2. While using Cloud CDN, the default time-to-live (TTL) for content caching is 3600 seconds = 60 mins 3. Cloud NAT sends only the translation logs and error logs to Cloud Logging service. 4. GCP Dedicated Interconnect - On Premises network device requirements:     10-Gbps circuits, single mode fiber or 100-Gbps circuits, single mode fiber     IPv4 link local addressing     LACP, even if you are using single circuit     EBGP-4 with multi-hop     802.1Q VLANs 5. While using Cloud VPN, the recommended MTU to be configured on the peer VPN  gateway = 1460 bytes 6. Each instance must have at least one network interface. The maximum number of network instances per instance is 8, depending on the instance's machine
1 comment
Read more