I am on my way to Interop which is being held in Las Vegas. For those of you who don’t know about Interop, it’s defined as ” an independently organized conference and exhibition designed to empower information technology professionals to make smart business decisions.” -Interop
Vendors from all over the board will be there. This will be my first time attending and I will be posting updates on the event, so stay tuned!
My first day will include 2 workshops:
“Advanced wireshark” and “A structured approach to Network Troubleshooting”
Brain storming is something that you should do quite often. Find a whiteboard and start drawing. Even a piece of paper will do. Get others involved in your brainstorm. Developing new services or improving upon existing services will greatly benefit from this. We can’t be content with the “if its not broken, then don’t fix it” mentality.
With that said, here’s a diagram that came from a brainstorm/whiteboard session. This came out of my lab gen to replace our aging Juniper m7i with some Brocade icx 6610’s. There’s an old school Enterasys DFE in there as well that simulated our building distribution router.
Trying to come up with the best option. I may need a bigger white board.
After an exhaustive search of a WAN switch, we finally made our minds up to go with the brocade ICX series. We are primarily an
enterasys extreme networks shop, but we are on a budget, like most other public education institutions. In my experience, I have seen many shops stick to what they know, cough, cough cisco, but is that always going to be the best price/solution? The brocade command line is very similar to cisco, so for you peep’s out there looking for an alternative to cisco, take a look at the brocade ICX lineup.
Now on to the good stuff. I’ve listed a few pointers to get ssh properly setup on an ICX 6610. You can also view more icx 6610 commands in my brocade ICX 6610 part 2 article.
//This command enables ssh on the icx 6610
(config)#crypto key generate dsa
//We can then setup a local account to use for ssh, but we first want to mask passwords
(config)#enable user password-masking
(config)#username yourusername password
//The next command enables the brocade to use the local user for ssh login
(config)#aaa authentication login default local
//We can then further secure by which IP’s are allowed to ssh
(config)#ip ssh client yourclientip
//Here is how we disable ssh.
(config)#crypto key zeroize dsa
I successfully completed the 4 day F5 LTM configuring v11 course. I am very happy with the amount of information covered and the teacher was very knowledgeable. Now that I’m back at work, I have already applied some of the knowledge I’ve obtained.
I was assisting another individual with setting up an http monitor that was using a send/receive string. We were having issues in getting the monitor to work. We struggled in where the CR/LF characters needed to be and how many to use. Each version of LTM seems to operate a little different and we found that out from the SOL10655 publication on the askf5 knowledge base. After going through some additional docs, we still couldn’t get the monitor to work. After trial and error, the monitor finally started working after we changed the HTTP version from 1.1 to 1.0.
Send String: GET /your/page/page.html HTTP/1.0\r\n Host: anynamewilldo\r\n\r\n
Today I’m starting a 4 day F5 online training course. The course will be going over how to setup and configure their BIG-IP LTM (local traffic manager) product. The LTM main feature is load balancing application traffic. For those of you who aren’t familiar with F5, they offer an extensive line of application delivery service products. The LTM is just one of their many product offerings. F5 offers some great introductory study material on their F5 support site. I would recommend starting there if you’re interested on learning about LTM.
Hi, my name is Javier Solis and I’m currently the network and infrastructure supervisor at Purdue University Northwest. I have been engrossed in the world of IT since the start of my freshmen year of high school back in 1998. I have also been blessed to carry two core full-time jobs since the start of my career as an IT student worker at the former Purdue University Calumet campus in Hammond Indiana.
My first full-time job was at a WISP (wireless Internet service provider) in Northwest Indiana. We were small in the eyes of the local telcom providers such as ATT and Comcast, but pretty large for a shop run by just a few employees. We heavily ran the Motorola canopy wireless line of gear and primarily used Mikrotik routers. Then I had the opportunity to move up to Wisconsin under contract by the same WISP to manage and deploy a 2.5 square mile municipal WiFi cloud mostly on my own. It proved to be quite a task, but I learned a great deal.
Five and a half years after working at that WISP, I took an offer to work as a full time network administrator back at Purdue University Calumet. Five and a half years working at the Purdue Calumet Hammond campus, there was a unification/merger with the Purdue North Central Westville regional campus. I’ve since been serving in a supervisory role at Purdue University Northwest for over two years and I am responsible for the network administration team, infrastructure team, and daily operations of firewall and VPN services. It’s funny how we find ourselves back where we started, but I’m learning more than ever. I enjoy sharing my experiences with others and I hope you’ll enjoy this blog. I also look forward to hearing from anyone out there. You can also find me on twitter at @javi_isolis.