Skip to main content

Updates – Netapp, HP, Coradiant

Our netapp (one of the nodes) is still crashing even after upgrading from ONTAP 7.3 to 7.3.1 . So far there is no advice from netapp on the issues. Obviously I am not happy since this has been going on for 7 weeks now. I just had a meeting with my Netapp rep, and he introduced and assured me the support would be better. I hope this is the case as its been pretty bad so far. Speaking of bad support the HP support is pretty much the worst support of any company on the market. I’ve had so many support issues just trying to get licenses and upgrades for all the HP (Mercury) software that we own for QA. Its been very painful. I’m trying to switch off HP support (aside from software upgrades) but we shall see.

Finally got the Coradiant box hooked up in Geneva, and I just did an upgrade this morning to the newest OS. Its working well. I have no idea what’s in the release notes, but I will soon find out 


Anonymous said…
Why do you say "I have no idea what's in the release notes"?

Unknown said…
Because I didn't get the release notes, but I have them now. Nothing too exciting in it. I hope to test Truesight Edge in the next month or two.
Anonymous said…
Yeah, I'd rather have good support than a lunch with HP to talk about why their support is underwhelming.
Unknown said…
All I got was a stinking phone call.. :)

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): (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