Routine Software Update Oct From HP

HP Networking Switches Maintenance Software

Products: HP E5500 Switch Series

Description: A new software update is now available.

JE099A - HP E5500-24 SI Switch

JE100A - HP E5500-48 SI Switch

JE101A - HP E5500-24 Switch

JE103A - HP E5500-48 Switch

JE105A - HP E5500-24-PoE Switch

JE107A - HP E5500-48-PoE Switch

JE109A - HP E5500-24-SFP Switch

JE102A - HP E5500-24 Switch (TAA)

JE104A - HP E5500-48 Switch (TAA)

JE106A - HP E5500-24-PoE Switch (TAA)

JE108A - HP E5500-48-PoE Switch (TAA)

JE110A - HP E5500-24-SPF Switch (TAA)

The software version is 3.2.2p22.

The product release notes are located at:http://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/?docId=c03931722

HP Network Security Maintenance Software

Products: HP Switch Services Modules

Description: A new software update is now available.

JD245A - HP 9500 VPN Firewall Module

JD249A - HP 7500 Advanced VPN Firewall Module

JD250A - HP 6600 Firewall Processing Router Module

JD251A - HP 8800 Firewall Processing Module

JD255A - HP 5820 VPN Firewall Module

JC635A - HP 12500 VPN Firewall Module

The software version is R3177.

The product release notes are located at: http://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/?docId=c03925016

Certification Path for HP wireless (ASE Wireless)

ATA >>>>> (Accredited Technical Associate optional )>>>>>AIS >>>>>ASE Wireless 2 Paper (HP0-Y43 and Y44)

Part 1 :- HP Wireless MSM Controller 720 Basic Configuration and Screenshots

HP is having comware v5 based controller and MSM based controller, Basic difference is MSR controller are Pure HP basic system(GUI basic) and comware controller are 3com devices like 810 series (CLI)

(BYOD setup are mostly working in comware suite)  

MSM Home page

Controller > Network > Interfaces  

By default devices will have 2 internet port and 4 Lan ports

   Internet (Outside) <<<<Wireless controller >>>>(inside port) LAN port

Management > Network discovery > By default it will only enable for Lan ports in this case Access Network port (LAN port). We need to client on internet network for enabling auto discovery of Access point. Otherwise it won’t able to find the AP’s in network

Once the access point are activated. We can find it on Controlled AP’s section.

Note :- MSM controller are based on centralized architecture and all the wireless traffic wil go thought controller

   

Controller port we can see on Network >Ports >

VSC is screen, We can setup what kind of authentication like Open ,WEP, WAP , Radius server OR WAP2

Controller  >> VSC > Virtual AP >(Default virtual AP will not enable for SSID, We need click it for Broadcasting the SSID

VSC >Radius Authentication

VSC>

Default we should not change this option (Wireless Mobility is licensed one for L2/L3 roaming)

Block User: - will block user which is misconfigured or unwanted users which is not authorized (It will drop user traffic in AP it self

Consider the user at Home :- if you click this option user traffic will allowed to network ap will allow the traffic via default Vlan which is configured on Controller  

Also ways configure BLOCK USER option

VSC’s Network tree (it will show total controllers and controlled Access points)

In this screen you see the VSC setup Parameters (SSID’s)

VSC Profile we can see the Total SSID group which is configured in Controller with authentication parameter  

Sonicwall Group vpn client setup

Sonicwall Group VPN = Easy Vpn in Cisco

Setups for basic setup of Sonicwall

Create >>>> Network object (= Host 192.168.1.1)
Create >>>>Network services( =Port 8080)
Create >>>>Firewall Zones (DMZ or Internet)
Create >>>>Map interface to Zones
Create >>>>Firewall rule and allow or deny traffic

Notes :- Sonicwall is based on zone base security and object based.


Screenshot

 Public ip address of sonicwall outside interface X0 or X1

Some of configuration, We can configure the Pre-share key also.

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.

John Chambers (God of Networking)

John Chambers, Cisco Systems Inc. chairman and chief executive officer, challenged the audience attending DISA's 2011 Customer & Industry Forum Aug. 16 to embrace change and innovation, view collaboration as fundamental, and think outside of the box to develop new ideas. This is all to transform business, break down silos, and alter culture and processes



http://www.youtube.com/watch?v=keh-Zla06P0