So you have a this nice multiplayer switch, and want to take advantages of all of the features it has to offer. Well there are two different types interface ports on these type of switches. SVIs (Switched Virtual Interface) and “routed” ports, fundamentally they are same and clients/users wouldn’t be able to tell if you were using/going through an SVI or a “routed” port. However they are different and in this post we’ll talk about these two and when and were it would be recommended to place an SVI or a routed port.
Just a short post about my recent Cisco exam, I was able to pass the 300-115 to renew all my lower CCNA certifications. The last time I took a Cisco exam was almost 3 years ago when I passed the CCNA Data Center certification. Overall the exam was fair although you will need multiple study resources to make sure you cover all the exam objectives.
The primary reason for doing this exam first instead of ROUTE or TSHOOT was I felt it was maybe the hardest one? Won’t really know until I take the other two.
The resources I used:
- The Official Cert Guide – CCNP Routing and Switching 300-115
- Chris Bryant Videos
- CCNP Subreddit
- Boson 300-115 Practice Exams
I “officially” started about three months ago, but was really off and on throughout 2018. During the last three months I did about an hour a day (Monday-Friday), the weekends I would shoot for 4 to 5 hours off and on during the day.
Not really in rush, so I’m probably going to wait until next winter, maybe ;)… I know it seems weird to drag this out and not just pass all of the exams but there are some personal/life goals this year I would like to at least start, in the meantime I hope this information is helpful and good luck!
So a single ISP isn’t cutting it anymore you need a backup just in case the primary fails and might as well add a second ASA into this design, more redundancy equals more up-time, right? On paper it sounds good but in the “real” world there probably is tipping point, more redundancy increases complexity. In this post we’ll aim to keep it simple, with setting up a Cisco ASA HA active/standby pair and then add in the second ISP. Let’s get started!
Let’s continue to talk about the Cisco Firepower Management Center, in this post we are going to look at sending connection events over to syslog. In this example I’m using Graylog which is an open source logging platform and although any syslog server would work, one of the problems with syslogs is there is little uniformity when you have different systems sending these logs. One of the things that Graylog can to do is extract the raw message and put each part of message into a separate searchable field. We’ll configure the FMC to send syslogs and then configure an extractor on Graylog. Continue reading “FMC Syslog with Graylog Extractor”
It’s the “S” word we don’t like to hear, and often times it has degraded networks or even took them down entirely. (All Systems Down – an older but classic story) It’s also one of those things that nobody really likes, we even had network companies, as well as IEEE try to replace it with something else. Remember the names like TRILL, and IEEE 802.1aq (SPB) or Cisco’s FabicPath technologies? You had all of these different flavors that showed a lot progress, but they never really took off for one reason or another. The funny part is this protocol we are all trying kill off is still alive and doing well, so let’s look at spanning tree in the meantime because you will likely run into it.