• Category Archives Synology
  • Updating Synology DSM

    9zi7chg

    I have two Synology boxes, an older DS212 and a DS1815+ that I use for my lab and other purposes. They were in need of an update andI thought I would put together a simple post about upgrading Synology to the latest DSM. This process covers updating from Synology DSM 5.2-5592 Update 2 to Synology DSM 6.0-7321 Update 6

    Synology Update 6 release brought a ton of new features and fixes, you can read more about that here.

    Some highlights

    • MailPlus / MailPlus Server – all new private cloud mail server
    • New Collaboration Tools – SpreadSheets and Note station
    • SSD Cache – Greater support for SSD cache
    • Data Protection – snapshot replication
    • Virtual DSM & Docker – Containers (This is probably the feature I am looking forward to the most)
    • Cloud & File Syncing – more
    • 64 Bit Architecture
    • Modularization
    • New Accessibility Features

    Now onto the upgrade process..

    Continue reading  Post ID 351


  • Log Insight: Content Pack for Synology DSM

    9zi7chg

    Logging is a critical component of a an IT infrastructure. Almost all products have logs that give you valuable data. I think logs and analytics of those logs are all too often an overlooked part of ongoing operations.  The logs themselves are full of data but only useful if they are looked at analyzed.

    Products like VMware Log Insight, Splunk and others can give you insight into this data and logs to isolate issues and find quick resolutions and consolidate information across multiple products.

    I am a big fan of Synology NAS units, I have a small 2 bay Synology in my lab and have been working with Log Insight for a while now. Using Log Insight, I can have my logs from Synology DSM sent directly to my VMware Log Insight Appliance.

    Let’s take a look at the setup. Its actually very easy to set up.

    First we will add the content pack to Log Insight.

      1. Navigate to the Log Insight Login page either via name or IP address. Log into Log Insight appliance.

      2. In the upper right corner, click the menu button as shown in the screenshot. -> Click Content Packs

      3. Click Marketplace on the Left Hand Menu Under Content Pack MarketPlace

      4. Find Synology DSM Content Pack – You may have to scroll down, take a look through all of the available content packs as you may have other products that have content packs available.
      Click Synology DSM – A Pop Up will open in page

      5. Click Install on the Synology DSM Content Pack as shown below.
      6. You will get a notification that Synology DSM Content Pack has been installed.
      Next you will need to set up your Synology to send logs to the VMware Log Insight Appliance.
      7. Log into your Synology Web Manager GUI
      8. Click the Synology Main Menu in the upper Right hand corner

       9. Click the Log Center Icon

      10. Click Log Sending on the left hand menu and enter the IP or name of your Log Insight appliance. I chose IP for my lab.

      11. Your Synology should now be sending logs to your Log Insight appliance. It may take a few minutes to start seeing data in the Dashboards.

      12. Log into Log Insight – Click on Dashboards. Using the drop down menu on the left as shown in the screenshot below, click Synology DSM under Content Pack Dashboards

      I decided in order to show some data to throw some bad logins into my Synology. You can see those represented by the light blue, dark blue logins were a success.

      I will dive more into this and other content packs as well as more advanced functions and features in a future post.


    1. VMware vSphere 5.1 Known Issues : Updated 9/17/2012

      9zi7chg

      VMware released vSphere 5.1 at VMworld 2012 in San Francisco and with any new product release there are usually bumps on the road, compatibility issues and things that just don’t work. VMware vSphere 5.1 is no exception.

      I have been part of many beta tests for other companies as well as several vSphere editions going back to 3.x. Not every configuration and product can be tested. The beta process does catch a lot of issues. The day software goes live without any issues every time, a lot of people will be without work..

      I have decided to catalog a few of the known issues with the vSphere 5.1 release.

      Perhaps the larges issue is that VMware View and vSphere 5.1 are not compatible yet.

      Last Updated 09/30/2012

      vSphere 5.1 and VMware View (all versions of View) 

      VMware vSphere 5.1 is not currently supported with any versions of VMware View.

      Do not upgrade vSphere above the supported versions listed in the VMware View 5.1 Release Notes.

      vSphere 5.1 is in the process of being certified against VMware View. To be alerted when this article is updated, click Subscribe to Document on the link above in the actions box

      VMware vSphere 5.1 and Cisco UCS

      Read Chad Sakacc’s post for more details. vSphere 5.1 support on Cisco UCS, the VMEM needs a new vSphere 5.1 specific .vib.

      VMware vSphere 5.1 KB articles

      VMware complied several of the 5.1 KB articles in a recent blog post on VMware Support Insider blog

      More VMware vSphere 5.1 KB articles  ** Added 9/17/2012 **

      VMware has compiled more vSphere 5.1 KB articles that you may have missed. This one features a few of the Single Sign-On (SSO) issues that have been common for some of you

      vCenter Server Services hang on startup after upgrading to vCenter Server 5.1 

      From the VMware KB article: Follow the link for resolution

      • After upgrading to vCenter Server 5.1, the VMware VirtualCenter Server service fails to start
      • The VMware VirtualCenter Server service will not successfully stop or start.
      • The vpxd log files show the following:
        • The final log in the vpxd.log file shows:
          CoreDump: Writing minidump
      • You see a backtrace near the very bottom of the vpxd.log file which begins with the following:

      2012-09-13T11:53:46.802+02:00 [04468 info ‘vmmoVm’ opID=SWI-c5103928] [VmMo::SetComputeCompatibilityDirty] vm vm-5345 is marked dirty
      2012-09-13T11:53:46.786+02:00 [05112 warning ‘win32vpxdOsLayer_win32’ opID=SWI-56f04b9c] [VpxUnhandledException] Backtrace

      Increased Restart time with vCenter Server 5.1

      This issue only impacts the start/re-start time for vCenter Server. It does not affect the ongoing operations after vCenter Server has started. In fact, due to improvements to the vCenter Server database, the use of vSphere Web Client, the Inventory Service cache, customers will notice significant performance improvements in vCenter Server 5.1.

      VMware vSphere 5.1 and EMC VMAX arrays.

      Sphere 5.1 changes the behavior of VAAI Hardware Accelerated Locking (aka ATS) to no longer work with transient (sometimes on/sometimes off) ATS behavior, and older (i.e. non-current) versions of Enginuity will fail to create VMFS-5.

      VMware vSphere 5.1 and EMC PowerPath V/E 

                **** Updated 09/26/2012 Resolved *** – Fix is out.

      PowerPath/VE customers, hold off vSphere 5.1 upgrades (GA was yesterday).   Hotfix P02 from EMC is in days, and so is the expected VMware fix, follow the above link for more details on Chad Sakac’s blog post

      VMware vSphere 5.1 and Synology DSM 4.1   ** Blog updated on 9/18/2012 **

      Kendrick Coleman found an issue with the most recent release of DSM 4.1 and vSphere 5.1

      It’s possible to mount both NFS and iSCSI datastores, but when you try to build or power on a VM, everything begins to halt when it needs to write to disk. If everything runs in memory (like mounting an ISO and beginning an OS installation), but when it comes to install the OS to disk, it begins to crawl. I checked the vmkernel log and here is what is shown. You can see that after I power on the VM, it gets binded to a port but when it tries to read from disk, there are all sorts of errors 

      Update Manager 5.1 reports the compliance status as Incompatible when scanning or remediating ESXi 5.x hosts that belong to an HA cluster 

      I personally ran into this issue when upgrading my lab – see Update Manager 5.1 Release Notes

      CA Signed SSL Certificates may cause trouble with the upgrade process of vCenter.

      From Michael Webster’s blog at http://longwhiteclouds.com/

      I have heard unconfirmed reports of difficulties with the upgrade process of vCenter particularly with registering Inventory Service and SSO with vCenter when using CA Signed SSL Certificates. As I’m using CA Signed Certificates in my lab environment I will update this article when I have completed my upgrade.

      Troubleshooting SSL certificate updates and Single Sign On (2033240)
      vCenter Single Sign On installer reports: Error 29155. Identity source discovery error (2034374)

      ESXi cannot distinguish between EagerZeroedThick & LazyZeroedThick
      From Cormac Hogan’s Blog

      ESXi cannot distinguish between thick provision lazy zeroed and thick provision eager zeroed virtual disks on NFS datastores with Hardware Acceleration support

       When you use NFS datastores that support Hardware Acceleration, the vSphere Client allows you to create virtual disks in Thick Provision Lazy Zeroed (zeroedthick) or Thick Provision Eager Zeroed (eagerzeroedthick) format. However, when you check the disk type on the Virtual Machine Properties dialog box, the Disk Provisioning section always shows Thick Provision Eager Zeroed as the disk format no matter which format you selected during the disk creation. ESXi does not distinguish between lazy zeroed and eager zeroed virtual disks on NFS datastores.

      VMware vSphere 5.1 iPXE problems with AutoDeploy

       If you are having issues with IPXE and AutoDeploy please read Gabe’s Virtual World

      VMware Support Insider: ALERT: Full disk on vShield Edge 5.1.x fails with error: VIX_E_DISK_FULL ERROR

      Added 09/30/2012

      VMware has become aware of an issue whereby vCloud Networking and Security 5.1 release can go into an Edge disk full state approximately 14 days after the first edge is deployed.

      Symptoms include:

      • In vCloud Director, attempting a reconfig fails with this error:VIX_E_DISK_FULL
      • In vCloud Director, when looking at Edge Gateways, you receive this error:Edge VM backing the edge gateway is unreachable

      For further updates and more information on this alert, refer to KB article:
      Full disk on vShield Edge 5.1.x fails with error: VIX_E_DISK_FULL ERROR (2035939)

      Links for more information
      vSphere 5.1 Important Upgrade Considerations by Michael Webster VCDX #66 

      As with any upgrade please carefully consider especially before implementing in production. Reach out to your partners and trusted advisers for guidance so they can evaluate your environment to minimize issues.