Skip to main content

Ipmonitor, spiceworks, and vendor maintenance

I'm happy that solarwinds has released a major upgrade to ipmonitor. Too bad they didn't notify me my maintenance expired about a month ago. I'm renewing it now, and looking forward to v10. This product is excellent, cheap, and does a great job with agentless monitoring. You can also tweak it to monitor pretty much anything as needed. Such a good deal for a great all around product.

Speaking of maintenance, I also just investigated and found out that our F5 Big-IP maintenance expired in April. Glad we have a HA pair in case of issues in the next little while, but I don't understand why vendors and resellers don't keep on top of customers. It's essentially free money they aren't going to get if they don't chase folks about it.

Vendors who do a good job with maintenance:

  • IBM
  • Oracle
  • Sybase
  • HP Software
  • Cisco

Vendors who are horrible with maintenance in my experience:

  • HP hardware
  • Dell
  • F5

What cisco does that's really cool is they integrate maintenance into other tools so when you have inventory such as HP Network Automation System (Formerly opsware nas) as well as Cisco's own Ciscoworks.

Another thing we do because we are cheap and love good free software is we leverage this awesome product called Spiceworks. I can't believe what you can do with the product, we've been using it for over a year now, and it's completely free:

  1. System inventory
  2. Hardware details and changes
  3. Software installs and changes
  4. Up/down monitoring
  5. Event log monitoring
  6. Disk monitoring (only used as a blanket monitor, non production)
  7. Exchange monitoring
  8. Antivirus definitions monitoring
  9. Active Directory integration
  10. Interface graphing (firewalls, routers, switches)
  11. Network mapping (relationships of devices and switches)

Its very easy to find a users system based on the login, its very easy to see changes in software and hardware, its also easy using this script:

This awesome script populates the inventory with the warranty expiration on dell devices. (including servers, printers, switches, desktops, and laptops)

Right now we have 5 collectors feeding one instance, so I can do global scanning and aggregate the results in a single repository.


It would be awesome if there was a centralized service I could sign-up for that monitored all software and hardware licenses and maintenance stuff from vendor companies then just notified me. I too have had minor crises when something wasn't renewed. I hate having to keep track of zillions of vendors and licenses. Why hasn't some smart company started to handle this. They could probably make good income just picking up a share of that "free money" the hardware and software companies are leaving on the table.
Unknown said…
Normally a good reseller would handle such notifications since they get a cut on the commissions. The problem I have is that none of mine have ever done a good job with that up until this point. Part of the problem is also that companies store the individuals name who made the purchase, and when they leave the company the data doesn't get delivered. I keep trying to get them to use my group email address, some vendors do this, while others do not. Pretty annoying to handle when I have this many vendors.
Unknown said…
I hope they let you renew your maintenance.

I think having maintenance integrated into the products is a good idea.

I'll having to bring this up at our next meeting. :)
Unknown said…
Yeah they all handled it, but it would be a good feature to have in the product. The helpdesk system we use JIRA does that well.
akp982 said…
If you can make it or know someone who can, Spiceworld London ( ) will be a great event to learn more about Spiceworks and meet up with some people.

It will also be the first place to get 4.5 training.

It will hopefully also been streamed so you maybe able to watch it where ever you are in the world.

There will be memebers of the Spiceworks team as well as lots of members of the community.

It will be a great day followed by hopefully a great afterparty.

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 with an API, t…

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)
# 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)

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, maybe 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 components or …