It’s shame that it took me 2 hours to find out why my Syslog Collector is not working. But I would like to share my experience with everyone including how to debug it.
Syslog collector has two parts.
Part running on vCenter
Syslog Collector must be installed first.
It is very important to configure your firewall so your syslog can go through.
the Syslog collector can use 3 different protocol. TCP,UDP,SSL. You can enable all of them.
make sure you have space for this log collector
that’s will install plug-in directly into your vCenter.
Feel free to use your DOMAIN/SERVICE_ACCOUNT to replace local administrator. But you need to make sure that service_account has local admin rights first.
By using different account will make better view in the TASK Manager to see how much memory it consumes.
You can replace SSL certificate with local CA certificate if you really…
View original post 288 more words
Disclaimer – These are not all my ideas, simply a collection of ideas from people I have met over the year including some very smart folks from Softscape (former company), ICI and others.
When faced with a problem, error message, basically anything not working here are some tips to get you back quickly.
- Make a list. Scott Lowe just presented on the ProfessionalVMware.com #vBrownBag (http://professionalvmware.com/?p=2931) and focused on the importance of tracking tasks so you are not bouncing back and forth and losing focus. If nothing else, the below points might make a good list for you to walk through to ensure you are getting the right things done in a timely manner.
- Collect as much information you can about the problem. Albert Einstein once said “If I had one hour to save the world, I would spend 55 minutes defining the problem and only five minutes finding the solution” and this should be a lesson for all of us in technology. We need to understand the problem before we can solve it. What is the operating system, patch level, software application and patch level, when did the problem start, what has changed since it started are all good data points to start with.
- Open a support ticket with the vendor. This was a great bit of advice I received from Brad Maltz (@bmaltz), chances are you are likely going to sit on hold, or have to wait for a support engineer to respond to your request so once you have collected as much information as you can, get the support case rolling. While you are spending time troubleshooting you are also moving up the support queue to someone who might be able to help. Worst case scenario, by the time they get back to you, you just close the case because you figured it out.
- Give the customer (remember internal IT departments you are an IT service provider, even if its just for one company) an specific time you will get back to them with an update. Be clear about what the problem is, what system or systems are affected and that the next response may be nothing more than an update that you have no update. Set a reminder in your calendar to send the update as well, you don’t want to promise an update at 10A and then not follow through. I have worked through issues where I sent 3 or 4 emails stating that the system was still down and working towards a resolution and that we would respond again within the next hour (or some other time interval that is appropriate for the problem). Give yourself enough time to hopefully find an answer, but not so short that you keep stopping your work and not so long that the customer is just left wondering.
- What do the logs say? If something isn’t working, in theory there should be a log file with errors in it someplace (though I have certainly run into a few system crashes that happened so quickly the only error was that Windows didn’t shutdown properly). Make sure you have a good system to collect and analyze log files.
- What does the knowledge base say? Just about every technology company publishes a knowledge base or KB where you can look up error messages, codes or type in symptoms. Chances are you are not the first person in the world to run into this error/problem. If the companies KB doesn’t have anything, search the GKB (aka google.com). In addition to the KB, customer support forums are also a great place to look.
- Check with your team. The 5 steps above should have taken you no more than 10-15 minutes (collect info, open a ticket, review logs, search the KB), if you haven’t yet heard back from technical support ask your team. Remember you are not on an island alone, even if you are a single IT person shop there are others you can lean on. Maybe there are people the affected department who have been at the company longer than you, if its a system thats been in place for a while they may have had this happen to them before and can tell you who helped them fix it the first time.
- Check in the social-media-o-sphere. If you are in technology and not taking advantage of social media and the many smart, open and helpful people out there, then I hope this blog post will have you start looking into it. LinkedIn and Twitter are my go to places if I am just beyond stumped.
- Review the original project documentation. There are certainly (many) times this may not exist, and if you find yourself thinking that YOU don’t have any documentation for your projects maybe its a good time to start. Typically a consultant/vendor would provide a scope of work, project outline or similar documentation that should state what you are doing with this platform, why you are doing it and what is likely to go wrong in the environment given the design.
- Panic. Just kidding…. well kind of… no – I am kidding (Still crack up over that comment Rob). In all seriousness though, if by now you have not found a solution its probably time to start reaching out to local consultants/experts for the system or systems you are having problems with. It may also be at this point that you realize a system restore is the only viable option and its time to break out the DR/backup and recovery plan so you can get the systems back online.
- Document and share it. Thanks to Edward Henry (@NetworkN3rd) for the tip and reminder. Once you have solved the problem, make sure to document the information you collected, the symptoms and how you resolved it. If it happened once, it will probably happen again. Share with your team, share via your online resources (customer forums, Twitter, blogs etc…) as others may see a problem, or similar problem in the future.
What do you think of the steps above? Do you use similar steps? What tips do you have?
Wanna be VMware geek since 3.5, VCP5-DV, Social Enterprise advocate, All around IT rock star, fantasy sports guru, dad, husband. VCAP-DCD next? Connect with me at http://www.linkedin.com/in/jonathanfrappier and https://twitter.com/jfrappier