Monday, March 15, 2010

EEM

A post on techexams.net prompted me to look farther into this.  It is a pretty handy little scripting tool built into the IOS.  I played with a basic one in GNS3 today:


event manager applet ISR_CISCO
 event syslog pattern "Interface FastEthernet0/0, changed state to down"
 action 1.0 cli command "enable"
 action 2.0 cli command "conf t"
 action 3.0 cli command "interface fa0/0"
 action 4.0 cli command "no shut"
 action 5.0 cli command "ip address 192.168.0.1 255.255.255.0"


This will track if fa0/0 goes down, and if it does it will perform a no shut on it...and assign it an IP address.  Ya, I was just playing, but take a look:


Router(config)#int fa0/0
Router(config-if)#shut
Router(config-if)#
*Mar  1 00:04:06.723: %LINK-5-CHANGED: Interface FastEthernet0/0, changed state to administratively down
*Mar  1 00:04:07.723: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to down
*Mar  1 00:04:08.299: %SYS-5-CONFIG_I: Configured from console by vty0
*Mar  1 00:04:10.051: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up
*Mar  1 00:04:11.051: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up
Router(config-if)#
Router(config-if)#
Router(config-if)#
Router(config-if)#exit
Router(config)#exit
Router#w
*Mar  1 00:04:17.815: %SYS-5-CONFIG_I: Configured from console by consolsh ip int b
Interface                  IP-Address      OK? Method Status                Protocol
FastEthernet0/0            192.168.0.1     YES manual up                    up
FastEthernet0/1            unassigned      YES unset  administratively down down




Pretty slick...heres a link. I will have to come back to this sometime. But I can see its usefulness.
Cisco EEM

Saturday, March 13, 2010

Saturday!

Well I am finishing off the 642-642 CBTNuggets today, and purchasing stuff of ebay for my CCIE home rack.  I am planning on using INE's topology, so I am building around that.  Here's what I am getting:

Device Type WAN LAN
R1 2620XM (2) WIC-1T FE
R2 2620XM (2) WIC-1T FE
R3 2611XM NM-4A/S (2)FE
R4 3640 (2) WIC-1T (2)FE
R5 3640 NM-4T (2)FE
R6 3640 (1) WIC-1T (2)FE

SW1 3550
SW2 3550
SW3 3550
SW4 3550
BB1 2620XM NM-8A/S
BB2 2509 (1) AUI Trans octal
BB3 2509 1 (1) AUI Trans octal

Rack-28U




If its yellow I already have it.  The white ones I still need to get.  I am planning on selling (if he still wants it), my current desktop rack (12U) and 24-port 2950 to a co-worker.  I am pretty stoked, I think that its going to be a cool journey.

Friday, March 12, 2010

Juniper SRX 240's

Well we got a pair of these bad boys at work....We clustered them and have them configured for stateful failover.  I am happy to say that for about 3 months I have been immersed in Junos.  All in all, it is a pretty decent operating system.  Coming from Cisco, the information is kind-of similiar, but not really (if that makes any sense).  I did learn through the process that a firm understanding of the technology is needed to be successful.  For a while, I was approaching these guys from a "Cisco" perspective; but I finally accepted the Juniper way of doing things, and it all seemed to work out.  They fail over nicely.  The one HUGE complaint I have is their misrepresented "dynamic" vpn.  First off, every users needs their own IKE gateway, ipsec policy, dynamic-vpn gateway, and vpn acl.  It is ALOT of administrative overhead to get someone configured.  They say this all will be fixed with version 11 next year...we are on 10.1.  Anywho...in order for the "dynamic IPSEC vpn to work...you have to have HTTPS enabled on the external interface they are coming in on.....ridiculous...it make it impossible to NAT anything through 443 on that same IP.  Yet I digress.  They are now working, and will probably be implemented in 2 months after we do VSS on our core switches next month.  Back out to transfer my homebrew into the fermenter :)