Muzamil Interview Prepration Notes
Muzamil Interview Prepration Notes
Muzamil Interview Prepration Notes
General Networking:
IP Routing:
1. Process Switching
2. Fast Switching
3. IP CEF
Link:
https://www.networkurge.com/2020/04/process-switching-vs-fast-switching-
vs.html#:~:text=Process%20switching%20refers%20to%20the,the%20running%20of
%20the%20process.
Internet Protocol
https://en.wikipedia.org › wiki › Internet_Protocol
The Internet Protocol (IP) is the network layer communications protocol in the Internet protocol suite
for relaying datagrams across network boundaries. Its routing function enables internetworking, and
essentially establishes the Internet.
Function
The Internet Protocol is responsible for addressing host interfaces, encapsulating data into
datagrams (including fragmentation and reassembly) and routing datagrams from a source host
interface to a destination host interface across one or more IP networks. [2] For these purposes, the
Internet Protocol defines the format of packets and
provides an addressing system.
Each datagram has two components: a header and
a payload. The IP header includes source IP address,
destination IP address, and other metadata needed to
route and deliver the datagram. The payload is the data
that is transported. This method of nesting the data
payload in a packet with a header is called
encapsulation.
Types:
There are 126 types but three and main
1- TCP
2- UDP
3- ICMP
TCP (Transmission Control Protocol)
The Transmission Control Protocol (TCP) is one of the main protocols of the Internet
protocol suite. It originated in the initial network implementation in which it
complemented the Internet Protocol (IP). Therefore, the entire suite is commonly
referred to as TCP/IP. TCP provides reliable, ordered, and error-checked delivery of a
stream of octets (bytes) between applications running on hosts communicating via an IP
network. Major internet applications such as the World Wide Web, email, remote
administration, and file transfer rely on TCP, which is part of the Transport Layer of the
TCP/IP suite. SSL/TLS often runs on top of TCP.
Network function
The Transmission Control Protocol provides a communication service at an
intermediate level between an application program and the Internet Protocol. It provides
host-to-host connectivity at the transport layer of the Internet model. An application does
not need to know the particular mechanisms for sending data via a link to another host,
such as the required IP fragmentation to accommodate the maximum transmission unit
of the transmission medium. At the transport layer, TCP handles all handshaking and
transmission details and presents an abstraction of the network connection to the
application typically through a network socket interface.
At the lower levels of the protocol stack, due to network congestion, traffic load
balancing, or unpredictable network behavior, IP packets may be lost, duplicated, or
delivered out of order. TCP detects these problems, requests re-transmission of lost
data, rearranges out-of-order data and even helps minimize network congestion to
reduce the occurrence of the other problems. If the data still remains undelivered, the
source is notified of this failure. Once the TCP receiver has reassembled the sequence
of octets originally transmitted, it passes them to the receiving application. Thus, TCP
abstracts the application's communication from the underlying networking details.
In computer networking, the User Datagram Protocol (UDP) is one of the core
communication protocols of the Internet protocol suite used to send messages
(transported as datagrams in packets) to other hosts on an Internet Protocol (IP)
network. Within an IP network, UDP does not require prior communication to set up
communication channels or data paths.
ICMP messages are typically used for diagnostic or control purposes or generated in
response to errors in IP operations (as specified in RFC 1122). ICMP errors are directed
to the source IP address of the originating packet.
Datagram:
Time to live:
Time to live (TTL) or hop limit is a mechanism which limits the lifespan or lifetime of data
in a computer or network. TTL may be implemented as a counter or timestamp attached
to or embedded in the data.
The Time to Live is an indication of an upper bound on the lifetime of an internet
datagram. It is set by the sender of the datagram and reduced at the points along the
route where it is processed. If the time to live reaches zero before the internet datagram
reaches its destination, the internet datagram is destroyed. The time to live can be
thought of as a self destruct time limit.
Routing Table:
Default Distance Value Table
Connected interface 0
Static route 1
Internal EIGRP 90
IGRP 100
OSPF 110
RIPv2 sends the entire routing table every 30 seconds, which can consume a lot of
bandwidth. RIPv2 uses multicast address of 224.0.0.9 to send routing updates, supports
authentication and triggered updates (updates that are sent when a change in the
network occurs).
As mentioned, OSPF currently supports 11 types of LSAs. Each LSA is used within specific boundaries of
an OSPF network.
Figure 2. LSA Type 1 Packets exchanged between OSPF routers within the same area
Figure 4. LSA Type 3 - An OSPF ABR router advertises the summarized route 192.168.2.0/24 to Area 0
Looking at the diagram above, ABR router R2 creates a Type 3 Summary LSA and floods it into Area 0.
In a similar way, ABR router R3 creates a Type 3 Summary LSA and floods it into Area 2. Type 3
Summary LSAs appear as O IA entries in the router routing table.
While LSA Type 4 packets are used by ABRs to advertise the ASBR route through their areas, it will not
be used by the ASBR itself within its local area (Area 1); ASBR uses LSA Type 1 to inform its neighbors
(R2 in this case) within its networks.
Figure 6. LSA Type 5 packets advertise the default route to all OSPF routers
This external route/prefix is redistributed in to the OSPF network by the ASBR (R1) and seen as O
E1 or E2 entries in other OSPF routers routing tables.
Figure 7. LSA Type 7 packets passing through an NSSA and being transformed into LSA Type 5 by the
ABR
In the above example, ABR R2 translates LSA Type 7 into a LSA Type 5 and floods it into the OSPF
network.
Stub area, also called stub area, the so-called stub area, means that the area does not
accept any external routes of non-OSPF network, if it wants to reach those external
routes, only Need to send it through the default route. This area supports 1, 2, and 3
LSAs.
Totally stubby area, it means that the area does not accept external routes and does
not accept the link information of other areas outside of their own area. If it wants to
reach the target network outside the area, it will send out the message through the
default route just like the stub area. It should be noted here that since the default route
is sent using Type 3 LSAs, the completely stub area does not allow ordinary Type 3
LSA packets, but it supports this type of LSA with default routes. This area supports
Type 1, Type 2 LSAs, and Type 3 LSAs with default routes.
No so stubby area, is usually referred to as the NSSA, this NSSA is actually derived
from the stub area, it means that in the case of a stub area, it also has to send external
routes to other areas ability. This area supports 1, 2, 3, and 7 LSAs. Note here that
there is another mode in the Totally stubby area zone, which is the NSSA of the
completely stub area mode. In fact, this mode allows the introduction of external routes
in a completely stub area environment. This area mode supports Class 1, Type 2 LSAs,
and Class 3 LSAs with default routes.
IP version: As discussed earlier, OSPFv2 supports IPv4 routed protocol whereas OSPFv3
supports the latest routed protocol version i.e. IPv6.
Multicast Address: OSPFv2 supports multicast addresses 224.0.0.5 and 224.0.0.6. On the
other hand, OSPFv3 supports multicast address FF02::5 and FF02::6
OSPF Instances: OSPFv2 doesn’t support multiples OSPF instances per interface,
whereas, OSPFv3 supports multiples OSPF instances per interface.
Authentication: OSPFv2 supports plain text and MD5 authentication. On the other hand,
OSPF v3 supports IPv6 authentication.
Subnets/Links: OSPFv2 runs on the network/subnets, whereas OSPFv3 runs on the links.
So, the adjacency is established over link local addresses in OSPFv3 and there is no
requirement of a network mask.
IP Unicast Routing: IPv4 unicast routing is enabled by default in OSPFv2. However, in
OSPFv3, The IPv6 Unicast routing has to be enabled using “IP Unicast-routing” global
configuration command, as it is not enable by default.
Flooding Scope: There is no flooding scope in OSPFv2. But flooding scope is present in
OSPFv3. The two bits of LSA called “S- bits” indicate flooding scope.
Header Size: The header size of OSPFv2 is 24 bytes. and that of OSPFv3 is 16 Bytes.
LSA Types: In addition to basic 7 LSA types present in OSPFv2, OSPFv3 has two more
LSA types. There is a variation in the name of LSA types 3 and 4 (shown in table below).
The two new LSA types are called “Link LSA” and “Intra-Area Prefix LSA”. The role of
“Link LSA” is to notify link-local addresses, as it is in link-local scope, so it is never
flooded. The role of “Intra-Area
NetFlow allows devices to analyze IP traffic and how it affects network availability and
performance. It uses QoS (Quality of Service) functions to optimize resource usage and
minimize latency and packet loss. NetFlow can also be used to control network resources by
giving higher priority to specific types of data and protocols used by your network.
https://network-king.net/netflow-vs-snmp-for-network-monitoring/
Switching
1 - Switch port configuration
2 - Vlan and Trunk
3 - VTP and VTP pruning
VTP
VLAN Trunk Protocol (VTP) reduces administration in a switched network. When you
configure a new VLAN on one VTP server, the VLAN is distributed through all switches in the
domain. This reduces the need to configure the same VLAN everywhere. VTP is a Cisco-
proprietary protocol that is available on most of the Cisco Catalyst series products.
VTP Pruning
VTP Pruning is the key element of VTP (VLAN Turning Protocol). It help improves
network performance and network bandwidth by decreasing unnecessary flooded
traffic i.e. broadcast, multicast, unknown and flooded unicast packets. In normal
operation, a switch needs to flood broadcast frames, multicast frames, or unicast
frames where the destination MAC address is unknown to all its ports. If the
neighboring switch doesn’t have any active ports in the source VLAN, this broadcast is
needless and excessive undesirable traffic may create problems on the network.
Related- VTP Interview Questions
This is disabled by default in Cisco switches. VTP pruning Cisco helps to send broadcasts
only to those trunk links that actually needs the information i.e. with VTP pruning
enabled, when the destination MAC address is unknown, frames are forwarded over a
trunk link only if the switch on the receiving end of the trunk link has ports in the
source VLAN pruning. It should only be enabled on VTP servers, all the clients in the
VTP domain will automatically enable VTP pruning. VLAN 1 can’t be pruned because it’s
an administrative VLAN
4 - Aggregating links
5 - STP
6 - RSTP and MST
7 - Inter Vlan Routing
8 - Cisco Express Forwarding
9- Campus Network Design
10 – HSRP
11 - VVRP
12- GLBP
13 - Cisco 6500 Supervisor Redundancy
14 - Campus services IP Telephony
15 - Campus Wireless Network
16 - Layer 2 Security Port security, 802.1X , DHCP Snooping
17 - IP Source Guard, DAI, ARP Inspection
18 - Switch security
19 - VACL
20 - Private Vlan
VLAN Trunk Protocol (VTP) reduces administration in a switched network. When you
configure a new VLAN on one VTP server, the VLAN is distributed through all switches in the
domain. This reduces the need to configure the same VLAN everywhere. VTP is a Cisco-
proprietary protocol that is available on most of the Cisco Catalyst series products.
Firewalls:
What is a Stateless Firewall?
This is similar to routers, and we need to create a policy for the same traffic in both
directions.
Like:
If one PC/user wants to access google.com, then one policy from the user to google.com
and 2nd policy from google.com to the user.
This type of firewall maintains the session table. If one user tries to access google.com, traffic
will go from inside to outside. When its reply comes from google.com, the firewall sends the
traffic to that user who had requested earlier because of the session table.
Philosophy Treats each packet in isolation Stateful firewalls maintain context about
and does not relates to active sessions and use “state information” to
connection state speed packet processing
PARAMETER STATELESS FIREWALL STATEFUL FIREWALL
Related terms Header info, IP address, port no State information, pattern matching etc.
etc.
HA feature overview
FortiADC appliances can be deployed as standalone units or as high availability (HA) clusters.
A cluster is two or more nodes. A node is an instance of the appliance/system. In a cluster, one node
is the primary node, also called the master node. The other members of the cluster are secondary
nodes, also called slave nodes.
The primary node has a special role. It has a one-to-many relationship with member nodes. Both
configuration updates and software updates are initiated by the primary node and pushed to member
nodes.
The system selects the primary node based on the following criteria:
Link health (if monitor ports links are down, the node is considered down)
Remote IP monitor health check results
Override setting (prefers priority to uptime)
Most available ports
Highest uptime value
Lowest device priority number (1 has greater priority than 2)
Highest-sorting serial number—Serial numbers are sorted by comparing each character from left to right,
where 9 and z are the greatest values. The system gives preference to higher values over lower values.
HA solutions depend on two types of communication among cluster members:
Synchronization—During initialization, the primary node pushes its configuration (with noted exceptions) to
member nodes. After initialization has completed, the nodes synchronize their session tables.
Heartbeats—A cluster node indicates to other nodes in the cluster that it is up and available. The absence of
heartbeat traffic indicates the node is not up and is unavailable.
There are two types of HA clusters:
Active-passive—Only the primary node is active, so it is the only node that receives traffic from adjacent
routers. Typically, there is one other node that is in standby mode. It assumes active status if the primary node
undergoes maintenance or otherwise becomes unavailable.
Active-active—All nodes receive traffic. Active-active deployments support load balancing and failover among
up to eight cluster members.
In an active-passive cluster, only the management IP address for the primary node is active. In an
active-passive cluster, you can log into a node only when it has primary node status and its IP
address is active. To access the user interface of an appliance in standby status (the active-passive
slave), you must use a console port connection.
In an active-active cluster, the IP addresses for all interfaces are unique, including the management
interface. When the appliance is in standalone mode, the physical port IP address is active; when it
is in HA mode, the address assigned to it in the HA node IP list address is active. You can log into
any node using the active IP address for its management port.
Tip: You can use the execute ha manage command to log into the console of a member node.
See the CLI reference.
Figure 72 shows an active-passive cluster in a single network path. In an active-passive cluster, the
primary node is the active node that handles all traffic. In the event that the primary node
experiences hardware failure or system maintenance, failover takes place. In failover, the standby
node becomes the primary node and processes the traffic that is forwarded along the network path.
The new primary node sends gratuitous ARP to notify the network to direct traffic for the virtual MAC
addresses (vMAC) to its network interfaces. It takes the IP addresses of the unresponsive node.
Forti Gate
Palo Alto
Fire Power
Cisco ISE