Skip to main content

Been a bit crazy

I have been travelling quite a bit for work, I spent some productive time in Geneva, and Munich. I have been gone for about 3 weeks total. I had a nice weekend in Amsterdam as well.

The weeks consisted of a datacenter move, some engineering and upgrades, and fixing some issues in our other offices as well. Overall the trip was good, but a bit too long of course. Made some good progress communicating with our core development team, and nailing down a lot of things on the table. I'm happy to be back, and looking forward to the big push coming to a new product launch. There is always a big project on the horizon that we work towards.

I've also been trying to beef up and implement for centralized storage in order to properly utilize our ESXi implementations. We have a homegrown NAS for NFS in one office, an older AX150i in another office, and I'm looking to get some more storage in the other office. I wish we could afford to put netapps everywhere and replicate... maybe next year :)

Speaking of Netapps, it seems that the upgrade about 11 days ago from 7.3.1 to 7.3.1P3 has finally fixed the weekly crashing issues we have been having for the last 4 months. It took a long time to get it fixed, but glad it seems to be fixed.

I have one last sonicwall I am trying to get upgraded with the sonicwall trade-in program, then i'll be fully single firewall platform finally. Should make things easier to manage and to train the staff on. They are also great products and nice to work with. UTM is the way to go.

Anyone have any comments on good replacement tools for acrobat pro (editing PDFs). Please spare me the mac user comments.

Comments

Popular posts from this blog

Misunderstanding "Open Tracing" for the Enterprise

When first hearing of the OpenTracing project in 2016 there was excitement, finally an open standard for tracing. First, what is a trace? A trace is following a transaction from different services to build an end to end picture. The latency of each transaction segment is captured to determine which is slow, or causing performance issues. The trace may also include metadata such as metrics and logs, more on that later. Great, so if this is open this will solve all interoperability issues we have, and allow me to use multiple APM and tracing tools at once? It will help avoid vendor or project lock-in, unlock cloud services which are opaque or invisible? Nope! Why not? Today there are so many different implementations of tracing providing end to end transaction monitoring, and the reason why is that each project or vendor has different capabilities and use cases for the traces. Most tool users don't need to know the implementation details, but when manually instrumenting wi

NPM is Broken

As someone who bought and implemented NPM solutions, covered them as an analyst, and now watches the industry, one cannot help but notice that NPM(D) is broken. According to Gartner themselves, the data center is rapidly changing, the data center is going away, m aybe not as quickly as Capp states, but it’s happening. This is apparent by the massive public cloud growth posted by Amazon, Microsoft, and Google in their infrastructure businesses. This means that traditional appliance-based NPMD offerings will not work, nor will traditional ways of collecting packet data. Many of the flow offerings do not handle the new types of flows which these services generate, but most importantly they do not understand the internet, which is the most important part of assuring services in cloud hosted environments. The network itself is not just moving to overlay a-la NSX and ACI, it's moving inside of orchestrated containers, and new proxy/load balancing systems typically built off component

F5 Persistence and my 6 week battle with support

We've been having issues with persistence on our F5's since we launched our new product. We have tried many different ways of trying to get our clients to stick on a server. Of course the first step was using a standard cookie persistence which the F5 was injecting. All of our products which use SSL is being terminated on the F5, which makes cookie work fine even for SSL traffic. After we started seeing clients going to many servers, we figured it would be safe to use a JSESSIONID cookie which is a standard Java application server cookie that is always unique per session. We implemented the following Irule (slightly modified in order to get more logging): http://devcentral.f5.com/Default.aspx?tabid=53&view=topic&postid=1171255 (registration is free) when HTTP_REQUEST { # Check if there is a JSESSIONID cookie if {[HTTP::cookie "JSESSIONID"] ne ""}{ # Persist off of the cookie value with a timeout of 2 hours (7200 seconds) p