Seven Time CCIE :- Neil Moore

http://blog.ine.com/2013/08/09/congratulations-to-neil-moore-7-x-ccie-10044/


Congratulations to Neil Moore on passing the CCIE Data Center Lab Exam, and becoming the first and only Seven Time CCIE in the world!

BGP Processes in Cisco Router

BGP Processes:

• BGP Open - responsible for BGP session establishment.
• BGP I/O - handles queuing and processing updates and keep alive packets.
• BGP Scanner - responsible for conditional route advertisements, route dampening, import and export of routes into VRF (MPLS), and confirms the reachability to the NEXT_HOP (the last one is handled now by BGP next-hop tracking).
• BGP Router - calculates the best path, establishes peers, sends and receives routes and interacts with RIB.

BGP command's

router bgp 100

 no synchronization

 bgp log-neighbor-changes

 bgp scan-time 20                

 network 1.1.1.1 mask 255.255.255.255

 timers bgp 5 15

 neighbor 10.1.1.2 remote-as 300

 neighbor 10.2.1.2 remote-as 100

 no auto-summary

Logs

*Mar  1 00:24:00.811: BGP: 10.2.1.2 sending KEEPALIVE (io)

*Mar  1 00:24:00.903: BGP: 10.2.1.2 received KEEPALIVE, length (excl. header) 0

*Mar  1 00:24:01.807: BGP: 10.1.1.2 sending KEEPALIVE (io)

R1#

*Mar  1 00:24:01.895: BGP: 10.1.1.2 received KEEPALIVE, length (excl. header) 0

R1#

*Mar  1 00:25:00.807: BGP: 10.2.1.2 sending KEEPALIVE (io)

*Mar  1 00:25:00.895: BGP: 10.2.1.2 received KEEPALIVE, length (excl. header) 0

*Mar  1 00:25:01.807: BGP: 10.1.1.2 sending KEEPALIVE (io)

R1#

*Mar  1 00:25:01.895: BGP: 10.1.1.2 received KEEPALIVE, length (excl. header) 0

R1#

*Mar  1 00:26:00.807: BGP: 10.2.1.2 sending KEEPALIVE (io)

*Mar  1 00:26:00.911: BGP: 10.2.1.2 received KEEPALIVE, length (excl. header) 0

*Mar  1 00:26:01.807: BGP: 10.1.1.2 sending KEEPALIVE (io)

R1#

*Mar  1 00:26:01.887: BGP: 10.1.1.2 received KEEPALIVE, length (excl. header) 0

R1#

*Mar  1 00:27:00.807: BGP: 10.2.1.2 sending KEEPALIVE (io)

*Mar  1 00:27:00.867: BGP: 10.2.1.2 received KEEPALIVE, length (excl. header) 0

*Mar  1 00:27:01.811: BGP: 10.1.1.2 sending KEEPALIVE (io)

R1#

*Mar  1 00:27:01.891: BGP: 10.1.1.2 received KEEPALIVE, length (excl. header) 0

R1#

*Mar  1 00:28:00.807: BGP: 10.2.1.2 sending KEEPALIVE (io)

*Mar  1 00:28:00.915: BGP: 10.2.1.2 received KEEPALIVE, length (excl. header) 0

*Mar  1 00:28:01.811: BGP: 10.1.1.2 sending KEEPALIVE (io)

R1#

*Mar  1 00:28:01.911: BGP: 10.1.1.2 received KEEPALIVE, length (excl. header) 0

R1#

*Mar  1 00:29:00.807: BGP: 10.2.1.2 sending KEEPALIVE (io)

*Mar  1 00:29:00.903: BGP: 10.2.1.2 received KEEPALIVE, length (excl. header) 0

*Mar  1 00:29:01.807: BGP: 10.1.1.2 sending KEEPALIVE (io)

R1#

*Mar  1 00:29:01.867: BGP: 10.1.1.2 received KEEPALIVE, length (excl. header) 0

Sonicwall Vpn Client Download (VPN Client v.4.7.3.0403)

Vpn Client software

http://help.mysonicwall.com/Applications/vpnclient/

Wireless Speed

Wireless speed

IEEE Standards Speed (mbps) Mhz

802.11a                   54 

80211b                    11                          2.4

802.11g                  54                          2.4

802.11n                 72.2

802.11ac               866.7

802.11ad                7000

Native vlan on Cisco

Cisco command's

switchport trunk allowed vlan remove/add 2-1001

switchport trunk allowed vlan add 2-3

HP command 

Interface gig 3/0/2
port link-type trunk
port trunk permit vlan 100 101
port trunk PVID vlan 12  (Equals to Native vlan command in cisco) 

Note:-


switchport trunk native vlan command for IOS switches to specify the native VLAN. Remember that the native VLAN must match on both sides of the trunk link for 802.1Q

By default, there is only a single VLAN for all ports. This VLAN is called default. You cannot rename or delete VLAN 1.

If you talk about a management VLAN is nothing more than a VLAN that is used for in-band management of your network switching devices.  In order to configure this on a switch you need to create a Switch Virtual Interface (SVI) that is mapped to that VLAN and then assign that virtual interface an IP address.  On a Cisco switch it would look like the following.

Interface Vlan99
ip address 192.16.10.1 255.255.255.0
exit

I also want to make something very clear.  Your management VLAN does not have to be the same as your Native VLAN.  Matter of fact, it is good practice to make sure that they are different.  Your management VLAN should only carry in-band management traffic and should not be the default VLAN.  By in-band management traffic I am referring to SSH or telnet (although telnet is not recommended because it is not secure).  Traffic such as BPDUs, PagP, CDP, use the native VLAN that is vlan 1.But if you change the native vlan then CDP/VTP/PagP will still use vlan 1 but the packets will be tagged.Only DTP uses the native vlan so if you changed the native vlan then DTP would use the new vlan to send frames.With PVST+ BPDUs obviously run on all vlans.