![]() |
Fig 1.1- Palo-Alto Firewalls Category II |
![]() |
Fig 1.1- Palo Alto Firewalls |
Rich sent me a question about temporary traffic blackholing in networks where every router is running IGP (OSPF or IS-IS) and iBGP.
He started with a very simple network diagram:
Read more ...February 15th, 2020 Updated Comment: Back in July of 2017 I went thru the first “real” re-org in my career. Yes, of course I had been through other re-orgs. But none of them really significantly impacted my primary day to... Read More ›
The post A Career Planning Ride Along with Fish appeared first on Networking with FISH.
About a year ago I shared with you (Thinking Out Loud: My Career Planning) a little about my yearly career planning process. This time I’m going to bring you on a ride-along of this year’s annual Career Planning exercise.
First and foremost I must answer a common question that I was asked a lot after last year’s blog.
The Dream Job Question:
“Why do you even bother with the yearly career planning process? You are always saying that CPOC is your dream job come true”
Yes. Without a doubt CPOC really is my absolute dream job come true! I consider myself so truly fortunate, blessed and lucky to still be here with CPOC. Rocking 16 1/2 years with CPOC and the CPOC family at Cisco!
So that all being said… why do I still review every year? Like I mentioned in last year’s blog “over the years what I’ve seen is that my 1 year plan, 3 year plan, 5 year plan and 10 year plans have changed as I have changed.” So then reviewing every year is just taking the time to “check in” that the job I’m in is not Continue reading
This post has been sitting in the “drafts” folder for a while now. Clearly, since it's August and is therefore a little late to be deciding on a plan that is supposed to carry through all 12 months of 2017. Regardless, I think it's still worth sharing how I've attempted to increase the frequency of my blogging. My basic goal for 2017 is:
Create more content in 12 months than I ever have before in order to a) significantly build up the depth and breadth of knowledge on my blog, b) increase my skills as a writer, and c) continue to build this blog and the readership as a key part of my online persona and brand.
In order to achieve this goal, I've identified a couple of tactical objectives:
In order Continue reading
An end-user’s perspective on open hardware and software.
Hopefully, you have heard the news today! We couldn’t be more excited to announce the general availability of VMware AppDefense, our new security solution. AppDefense bolsters the micro-segmentations threat prevention capabilities delivered by NSX with data center endpoint threat detection and response. It’s no secret that organizations are spending more money than ever on security. It’s also no surprise that the only thing outpacing security spend are the losses due to security breaches. At VMware, we believe the struggle organizations face in gaining the upper-hand in this battle is due to a foundational architectural gap that creates misalignment between the infrastructure where security is applied and the applications that security is designed to protect.
NSX was the first step toward re-aligning network security policy with applications by leveraging the virtualization layer to enable micro-segmentation, as well as enhance the posture of other security solutions through integrations and features like service insertion and guest introspection. But applications are made up of both networks and data center endpoints like VMs. AppDefense is the other half of the puzzle. Whereas NSX prevents threats from moving freely throughout the network, AppDefense detects anything that does make it to an endpoint and can automatically Continue reading
Edge computing will require "a new kind of cloud," Michael Dell said.
AppDefense integrates with several technology partners including IBM Security, RSA, Carbon Black, SecureWorks, and Puppet.
The systems integrate Dell EMC hardware and VMware software.
Accenture, Sysco, Adidas, Medtronic, and Moody’s are early-access customers.
Last Friday, 25 August, a routing incident caused large-scale internet disruption. It hit Japanese users the hardest, slowing or blocking access to websites and online services for dozens of Japanese companies.
What happened is that Google accidentally leaked BGP prefixes it learned from peering relationships, essentially becoming a transit provider instead of simply exchanging traffic between two networks and their customers. This also exposed some internal traffic engineering that caused many of these prefixes to get de-aggregated and therefore raised their probability of getting accepted elsewhere.