#SDN #Routing #Switching #Firewall #NAC #Proxy #Mail Gateway #SDWAN

This is one of the best feature which can be used by Network and security adminitrators. Today Firewall administrator deal with major challenege of  Auto Removal of Servers which are not part of  current policy . Because that server is decommisioned and because of any xyz reason not informed to security team . Problem occurs when the server with the same IP address is used by other application and because the secuirty admin is not aware of the same . The same old policy which is actually not required can be used by new application. This will also solve the problem of administrator adding or deleting 1000 of ipswhich ae vulnerable. As per my knowledge there are few firewall who uses the concept of Dynamic address grup. This is mainly usefull for VM environment wehre we use the concept of Tagging. This feature is best used in PaloAlto Firewall + VM environment. You can refer the below link to check the same..... https://docs.paloaltonetworks.com/pan-os/7-1/pan-os-admin/policy

openssl pkcs12 -export -out domain.name.pfx -inkey domain.name.key -in domain.name.crt

Reset switch to factory defaults If I’m not using brand new switch, I normally like to reset it back to factory defaults before doing anything. Use a pointy object (like paper clip) and press “Reset” and “Clear” buttons on the front of the switch at the same time. Release “Reset” button. When “Self Test” LED start to blink, release “Clear” button too. Now the switch should do it test routines. After that it should be back on factory defaults. IP-Address HP ProCurve Switch 2524# configure HP ProCurve Switch 2524(config)# vlan 1 HP ProCurve Switch 2524(vlan-1)# ip address 10.0.0.1 255.255.255.0 HP ProCurve Switch 2524(vlan-1)# wr mem HP ProCurve Switch 2524(vlan-1)# exit HP ProCurve Switch 2524(config)# exit HP ProCurve Switch 2524# Configure VLANs HP ProCurve Switch 2524# configure HP ProCurve Switch 2524(config)# vlan 1 HP ProCurve Switch 2524(vlan-1)# name "Default" HP ProCurve Switch 2524(vlan-1)# untag 2-6 HP ProCurve Switch 2524(vlan-1)# vlan 1

HP ProCurve CLI CheatSheet LOG log Display log events (most recent last) log -r Display log events (most recent first) log A12 Display log events of port a12 log A12 -r Display log events of port a12 (most recent first) log 192.168.0.1 Display log events of 192.168.0.1 MAC show mac A5 Show MAC-address of the device on port A5 show mac A4-A6 Show MAC-adresss of the devices on ports between A4 and A6 show mac 00112233-445566 Show which port device with MAC-address 00112233-445566 is connected VLAN show vlan Show information about vlans on this swtich show vlan ports A19 Show VLAN ID and status of specific ports (A19) show vlan Show ports on this vlan and port status configure vlan 19 Set switch to vlan 19 name SupportVLAN Name this vlan as “SupportVLAN” tag A12 Set port a12 as tagged on vlan 19 (First do vlan <19>) tag A12,A13 Set ports a12 and 13 tagged on vlan 19 (First do vlan <19>)

Problem When I first started in IT, I went and did my Cisco CCNA . So I learned that to connect Cisco switches and pass VLAN traffic between them, I needed to create a 'Trunk' to pass the VLAN traffic. Fast forward a few years, and I now work for an HP reseller. Very early on I came to realise that what HP called a 'trunk' was very different from what I had been taught. Below is an article I did a while ago about setting up HP Trunks. HP Networking 'ProCurve' - Trunking / Aggregating Ports I was in some HP/Wireless training last week and once again I was struggling with their terminology, so today I lined up a bunch of switches on the test bench and worked out the differences. Below you will find the following scenarios; Scenario 1 Configuring Cisco Catalyst Switches with VLANs. Scenario 2 Configuring HP Switches with VLANs. Scenario 3 Setting up HP Switches with Trunked VLANs Scenario 4 Setup VLANs via HP Trunks and Cisco Port Chann

http://www.certprepare.com/vlan-access-map