Friday 18 September 2020

TOP 10 VLAN INTERVIEW QUESTIONS & ANSWERS

 

TOP 10 VLAN INTERVIEW QUESTION AND ANSWER

 

Question 1
What is the purpose of creating VLANS ?

> Broadcast control is the main purpose of creating vlans Other purpose of creating VLANs
>VLANs provides Network Security
>VLANs provides Segmention
>VLANs provides Flexibility - a user can easily move across the physical location and still remain in the same vlan.

Question 2
How to delete VLAN information on a switch ?

> VLAN information is not saved in running configuration or startup-configuration of the switch ; it is saved in a separate file "vlan.dat" in the flash memory of the switch.
>To delete the vlan database from flash memory
    delete flash:vlan.dat

Question 3
What are access ports and trunk ports ?

> Access ports carries single vlan traffic i.e Access ports are member of only one vlan.
> Trunk ports carries multiple vlans traffic i.e Trunk ports are member of multiple vlans.
> By default all vlans are allowed on the trunk . But we can manually allow or disallow certains vlans on the trunk.

Question 4
What is meant by Inter-Vlan Routing ?

> VLAN divides the broadcast domains so the hosts can communicate with the other hosts in the same vlan.
> When the hosts from one vlans wants to communicate with hosts in other vlan the traffic must be routed between them.
>This is known as Inter-Vlan Routing
> Inter-Vlan Routing can be achieve either by creating SVI or using Router-on Stick.

Question 5
What is the difference between ISL & IEEE 801.Q ?

>To achieve trunking on trunk ports we either need to use ISL (Inter-Switch Link) or IEEE 801.Q (dot1q)
> ISL is Cisco properitary dot1q is an Industry standard
> In ISL the original frame is encapsulated with 26 bytes header and 4 bytes FCS (Frame Check Sequence)
which makes total 30 bytes of overhead.
In dot1q - a 4 bytes TAG is inserted into the frame.
>While using ISL original frame is not modified . Whereas while using dot1q the original frame is modified ;hence CRC is re-calculated.
> ISL is not supported on CISCO NX-OS
dot1q is supported on CISCO NX-OS
> In ISL the native vlan frames are also encapsulated . Whereas in dot1q the native vlan frames goes untagged.

Question 6
What is the range of the vlan ?

> Vlan range 0 to 4096
> 0 & 4096 - Reserved
> 1 - Default Vlan
> 2 to 1001 - Normal Vlan Range.
> 1002 to 1005 - Reserved for Token Ring and FDDI VLANs
> 1006 to 4095 - Extended Vlan range. Used by service provider to allow provisioning of new vlans.

Question 7
Consider a scenario where two switches SW1 & SW2 are connected to each other and dot1q trunk is configured .On SW1 native vlan is not specified whereas on SW2 native vlan is
configured has VLAN 2. What will happen ??

> Native VLAN mismatch will occur.

Question 8
What is VTP and its modes ?

VTP i.e. VLAN Trunking Protocol is an optional parameter and which provides Centrailzed vlan management capability (vlan creation , deletion, modification,etc.)

Server Mode - Default mode
> On switch in Server mode we can create , modify
and delete VLANs.
> It can send & forward VTP advertisments.
> It gets synchronize with VLAN Configuration.
>In this mode VLAN configuration gets save in NVRAM i.e.start-up configuration of the switch.
Client Mode
> On switch in Client mode we cannot create ,
modify or delete VLANs.
> It can forward VTP advertisments.
> It gets synchronize with VLAN Configuration.
>In this mode VLAN configuration does not get save in NVRAM i.e. start-up configuration of the switch.
Transparent Mode
> On the switch in Transparent mode we can create , modify and delete local VLANs.
> It can forward VTP advertisments.
> It will not synchronize with VLAN Configuration.
>In this mode the VLAN configuration gets save in NVRAM i.e. start-up configuration of the switch.

Question 9
What are the requirements for VTP messages to
exchange between two switches ?

> The link between the 2 switches should be
trunk.
> The domain name configured on both switches should be same .
Note - the domain name is case sensitive.
>The password set (if any) for the vtp domain should match at both switches.

Question 10
What is VTP Pruning ?

>VTP Pruning is a feature in Cisco switches, which stops VLAN update information traffic from being sent down trunk links if the updates are not needed.
>If the VLAN traffic is needed later, VTP will dynamically add the VLAN back to the trunk link.
>It helps in increasing the available bandwidth by reducing unnecessary flooded traffic.

                                               BEST OF LUCK !!!!

amartechstuff

Sunday 13 September 2020

BGP NOTES

 BGP NOTES

BGP CHAPTER 1- CONCEPT

https://networkengineerstuff.blogspot.com/2020/04/bgp-concept.html

 




BGP Chapter 2 - Basic Configuration of BGP

https://networkengineerstuff.blogspot.com/2020/04/bgp-chapter-2-basic-configuration-of-bgp.html

 




BGP CHAPTER 3 - ROUTER ID


https://networkengineerstuff.blogspot.com/2020/04/bgp-chapter-3-router-id.html



BGP CHAPTER 4 - BGP CONFIGURATION USING LOOPBACK INTERFACES

https://networkengineerstuff.blogspot.com/2020/04/bgp-chapter-4-bgp-configuration-using.html

 




BGP CHAPTER 5- UNDERSTANDING NETWORK ADVERTISEMENT IN BGP

https://networkengineerstuff.blogspot.com/2020/04/bgp-chapter-5-understanding-network.html

 


  


BGP CHAPTER 6 - IBGP Neighborship using loopback interfaces

https://networkengineerstuff.blogspot.com/2020/04/bgp-chapter-6-ibgp-neighborship-using.html

 


 

BGP CHAPTER 7 - SHUTTING BGP NEIGHBOR

https://networkengineerstuff.blogspot.com/2020/04/bgp-chapter-7-shutting-bgp-neighbor.html



BGP CHAPTER 8 -Reading BGP Table

https://networkengineerstuff.blogspot.com/2020/04/bgp-chapter-8-reading-bgp-table.html



 

BGP CHAPTER 9 - BGP MESSAGES

https://networkengineerstuff.blogspot.com/2020/05/bgp-chapter-9-bgp-messages.html


 

BGP CHAPTER 10- BGP NEIGHBOR STATES

https://networkengineerstuff.blogspot.com/2020/05/bgp-chapter-10-bgp-neighbor-states.html


 

BGP CHAPTER 11 - Autosummary in BGP

https://networkengineerstuff.blogspot.com/2020/05/bgp-chapter-11-autosummary-in-bgp.html




 

BGP CHAPTER 12 - BGP SYNCHRONIZATION RULE


https://networkengineerstuff.blogspot.com/2020/05/bgp-chapter-12-bgp-synchronization-rule.html
                            
BGP CHAPTER 13 - Next Hop Self in BGP

https://networkengineerstuff.blogspot.com/2020/05/bgp-chapter-13-next-hop-self-in-bgp.html


BGP CHAPTER 14 - Understanding BGP Attributes


https://networkengineerstuff.blogspot.com/2020/05/bgp-chapter-14-understanding-bgp.html


BGP CHAPTER 15 - BGP - AS PATH PREPEND


https://networkengineerstuff.blogspot.com/2020/05/bgp-chapter-15-bgp-as-path-prepend.html
                                     
BGP CHAPTER 16 - BGP - LOCAL PREFERENCE

https://networkengineerstuff.blogspot.com/2020/05/bgp-chapter-16-bgp-local-preference.html

                                    
BGP CHAPTER 17- BGP ATTRIBUTE - WEIGHT

https://networkengineerstuff.blogspot.com/2020/05/bgp-chapter-17-bgp-attribute-weight.html

 

 

BGP CHAPTER 18- BGP ATTRIBUTE - MED

 https://networkengineerstuff.blogspot.com/2021/01/bgp-chapter-18-bgp-attribute-med.html


 

BGP CHAPTER 19- BGP PATH SELECTION

https://networkengineerstuff.blogspot.com/2021/02/bgp-chapter-19-bgp-path-selection.html 


 

BGP CHAPTER 20- BGP AUTHENTICATION

https://networkengineerstuff.blogspot.com/2021/03/bgp-chapter-20-bgp-authentication.html 


 

TO BE CONTD....

amartechstuff








 

 

Friday 11 September 2020

ICMP headers

 

As already explained, the headers differs a little bit from ICMP type to ICMP type. Most of the ICMP types are possible to group by their headers. Because of this, we will discuss the basic header form first, and then look at the specifics for each group of types that should be discussed.

 

ICMP Headers

 

All packets contain some basic values from the IP headers discussed previously in this chapter. The headers have previously been discussed at some length, so this is just a short listing of the headers, with a few notes about them.

 

Version - This should always be set to 4.

 

Internet Header Length - The length of the header in 32 bit words.

 

Type of Service - See above. This should be set to 0, as this is the only legit setting according to RFC 792 - Internet Control Message Protocol.

 

Total Length - Total length of the header and data portion of the packet, counted in octets.

 

Identification, Flags and Fragment offsets - Ripped from the IP protocol.

 

Time To Live - How many hops this packet will survive.

 

Protocol - which version of ICMP is being used (should always be 1).

 

Header Checksum - See the IP explanation.

 

Source Address - The source address from whom the packet was sent. This is not entirely true, since the packet can have another source address, than that which is located on the machine in question. The ICMP types that can have this effect will be noted if so.

 

Destination Address - The destination address of the packet.

 

There are also a couple of new headers that are used by all of the ICMP types. The new headers are as follows, this time with a few more notes about them:

 

Type - The type field contains the ICMP type of the packet. This is always different from ICMP type to type. For example ICMP Destination Unreachable packets will have a type 3 set to it. For a complete listing of the different ICMP types, see the ICMP types appendix. This field contains 8 bits total.

 

Code - All ICMP types can contain different codes as well. Some types only have a single code, while others have several codes that they can use. For example, the ICMP Destination Unreachable (type 3) can have at least code 0, 1, 2, 3, 4 or 5 set. Each code has a different meaning in that context then. For a complete listing of the different codes, see the ICMP types appendix. This field is 8 bits in length, total. We will discuss the different codes a little bit more in detail for each type later on in this section.

 

Checksum - The Checksum is a 16 bit field containing a one's complement of the ones complement of the headers starting with the ICMP type and down. While calculating the checksum, the checksum field should be set to zero.

 

At this point the headers for the different packets start to look different also. We will describe the most common ICMP Types one by one, with a brief discussion of its headers and different codes.

 

Wednesday 9 September 2020

UDP Headers

The UDP header can be said to contain a very basic and simplified TCP header. It contains destination-, source-ports, header length and a checksum as seen in the image below.

 

UDP Headers

 

Source port - bit 0-15. This is the source port of the packet, describing where a reply packet should be sent. This can actually be set to zero if it doesn't apply. For example, sometimes we don't require a reply packet, and the packet can then be set to source port zero. In most implementations, it is set to some port number.

 

Destination port - bit 16-31. The destination port of the packet. This is required for all packets, as opposed to the source port of a packet.

 

Length - bit 32-47. The length field specifies the length of the whole packet in octets, including header and data portions. The shortest possible packet can be 8 octets long.

 

Checksum - bit 48-63. The checksum is the same kind of checksum as used in the TCP header, except that it contains a different set of data. In other words, it is a one's complement of the one's complement sum of parts of the IP header, the whole UDP header, the UDP data and padded with zeroes at the end when necessary.