Cool Solutions

Configuring NSS Volume as a Content Repo on OES Satellite Server



By:

July 15, 2013 3:56 pm

Reads: 1034

Comments:3

Score:0

Overview

In a remote location/office if there is an OES Server, the same server could be utilized to host ZEN Satellite Server and the Content Repo on an NSS Volume. This will help in optimizing the hardware resource and network bandwidth.

Below are the steps and configurations for achieving this solution.

NOTE: We have tested this solution on the following platforms:

OES2 SP2 as Satellite Server with ZENworks 11.2.3 ‘A’ as Primary Server.

OES11 SP1 as Satellite Server with ZENworks 11.2.4 and ZENworks 11.3 as Primary Server.

Pre-requisites

  1. OES Server should be up and running.
  2. NSS volumes mounted on OES Server.
  3. ZCM Primary Server should be up and running.
  4. Ensure that a few bundles are created and available in ZCM Primary Server.

    For example: Google Talk, Novell Messenger, etc.

Configurations to be made at Primary Server (ZCM)

  1. Discover and deploy Adaptive Agent on the OES Server using ZCM.
  2. Through ZCM Configuration, add OES as the Satellite Server following the steps below:

    Go to ZCM Configuration -> Server Hierarchy -> Action -> Configure Satellite Server.

  3. Browse and select the OES Server which is going to be added as the Satellite Server in Device to promote.

    Select the Content role from the Satellite Server Roles list.

  4. Click on Configure, go to the server settings tab.

    Under “Port for content and collection HTTP requests” configure the port number as 82 or any other number than 80, because port 80 will be used by OES Services.

    NOTE: The default port number is 80, hence configure any port number other than 80 and ensure the port number specified is already not in use.

  5. In the Content replication tab, select “Use Parent Primary Server only” as the content replication method.

    Optional: If required we can create a closest server rule (Network Environment/Location) for agents to pull content from the Satellite Server.

  6. Save the changes, the Satellite Server is added successfully to the ZCM.
  7. Go to the configuration tab, select the satellite server which has been configured.
  8. Click on Details of the Satellite server and navigate to the Content tab.

    Select the bundles/policies which need to be included for content replication.

    For example: Dynamic-Local-User Policy, Filr bundles are included for content replication.

  9. The above selected bundles/policies are included for content replication.
  10. Go to Configuration -> Server Hierarchy -> click on the “arrow mark” which navigates to the satellite server, as shown below.
  11. Select the Satellite Server and select the option “Configure Satellite Server” from the dropdown list of the Action tab as shown below.
  12. Click on Configure for the “Content” Role.
  13. Select the edit option to configure the interval for content replication or create a new schedule by adding a new interval.
  14. Click on Edit, to configure the interval, throttle rate, duration and Schedule Type for content.
  15. This activity will ensure the selected bundles/policies are replicated to the Satellite Server.

Verification Steps on the OES Server:

  1. Check the privileges of the content repo folder in the default location of ZENworks.
  2. After the content replication schedule, go to the following directory to check that the content is replicated successfully from Primary to Satellite Server.
    blr-cit-166:/var/opt/novell/zenworks/content-repo/content # ls  –lrt
    total 0
    drwxr-xr-x 2 root root 104 Jun  7 09:47 b4  (Content replicated directory)
    drwxr-xr-x 2 root root 104 Jun  7 09:47 48  (Content replicated directory)

Configurations to be made on the Satellite Server i.e OES Server

  1. Stop the ZENworks Adaptive Agent on the Satellite Server using the command below:
  2. Create user defined content repo under NSS mounted volume.

    eg: /media/nss/VOL1/zendata/content-repo/

    Content repo is the user defined directory under /media/nss/VOL1/zendata

  3. Copy the content data from the default location to the mounted volume /media/nss/VOL1/zendata/content-repo/

    cp /var/opt/novell/zenworks/content-repo /media/nss/VOL1/zendata

  4. Rename the content-repo directory from this path: /var/opt/novell/zenworks/content-repo to /var/opt/novell/zenworks/content-repo-backup
  5. Create softlink using the following command:

    ln -s /media/nss/VOL1/zendata/content-repo/ /var/opt/novell/zenworks/content-repoThe softlink should look like below:

         blr-cit-66:/var/opt/novell/zenworks # ls -lrt
         total 172
        drwxr-xr-x 2   root  root     48         Feb  6 11:47 rm
        drwxr-xr-x 2   root  root     48         May 15 16:16 puppet
        drwxr-xr-x 3   root  root     80         May 15 16:16 adm
      -rw-r--r-- 1        root  root   146056  May 15 16:16 zentruststore
       drwxr-xr-x 5    root  root    136        May 15 16:27 work
       lrwxrwxrwx 1 root  root     37         May 15 17:29 content-repo ->  /media/nss/VOL1/zendata/content-repo/
  6. Start the Adaptive Agent on the Satellite Server.
  7. Assign the bundle to any managed device.

Verification to confirm the content is getting replicated from Satellite Server to Managed Device

  1. Check the zmd-message.logs to ensure that the content is replicated successfully from the satellite Server to the managed device.

    Logs are present in the following location on the windows managed device:

    C:\Program Files (x86)\Novell\ZENworks\logs\LocalStore

DEBUG] [05/16/2013 11:07:32.602] [600] [ZenworksWindowsService] [76] [] [ClosestServers] [] [Role:Server ::COLLECTION:http://blr-cit-36.cit.labs.blr.novell.com:80/] [] [] 
 [DEBUG] [05/16/2013 11:07:32.602] [600] [ZenworksWindowsService] [76] [] [ClosestServers] [] [Role:Server ::COLLECTION:http://164.99.186.36:80/] [] [] 
 [DEBUG] [05/16/2013 11:07:32.602] [600] [ZenworksWindowsService] [76] [] [ClosestServers] [] [Role:Server ::CONTENT:http://blr-cit-66.labs.blr.novell.com:82/zenworks-content/] [] [] 
 [DEBUG] [05/16/2013 11:07:32.602] [600] [ZenworksWindowsService] [76] [] [ClosestServers] [] [Role:Server ::CONTENT:http://164.99.186.66:82/zenworks-content/] [] [] 

 [DEBUG] [05/16/2013 08:57:56.988] [600] [ZenworksWindowsService] [47] [] [ConnectMan-ping] [] [   Using uri: http://164.99.186.66:82/zenworks-content/c4097b9680b1384888af3ea61e217a8f.zc] [] [] 
 [DEBUG] [05/16/2013 08:57:56.988] [600] [ZenworksWindowsService] [47] [] [ConnectMan] [] [Marking location 164.99.186.66 Good at the request of module ZenCache] [] [] 
 [DEBUG] [05/16/2013 08:57:56.988] [600] [ZenworksWindowsService] [47] [] [ConnectMan] [] [   Setting location name 164.99.186.66 to status Good] [] [] 
 [DEBUG] [05/16/2013 08:57:56.988] [600] [ZenworksWindowsService] [47] [] [ConnectMan] [] [Marking location 164.99.186.66 Good at the request of module ZenCache] [] [] 
 [DEBUG] [05/16/2013 08:57:56.988] [600] [ZenworksWindowsService] [47] [] [ConnectMan] [] [   Setting location name 164.99.186.66 to status Good] [] [] 
 [DEBUG] [05/16/2013 08:57:56.988] [600] [ZenworksWindowsService] [47] [] [ConnectMan] [] [Marking location http://164.99.186.66:82/zenworks-content/c4097b9680b1384888af3ea61e217a8f.zc Good at the request of module ZenCache] [] [] 
 [DEBUG] [05/16/2013 08:57:56.988] [600] [ZenworksWindowsService] [47] [] [ConnectMan] [] [   Setting location name http://164.99.186.66:82/zenworks-content/c4097b9680b1384888af3ea61e217a8f.zc to status Good] [] [] 
 [DEBUG] [05/16/2013 08:57:56.988] [600] [ZenworksWindowsService] [47] [] [ConnectMan] [] [   Setting location http://164.99.186.66:82/zenworks-content/c4097b9680b1384888af3ea61e217a8f.zc, IP address 164.99.186.66, and host 164.99.186.66 to status: Good] [] [] 
 [DEBUG] [05/16/2013 08:57:56.988] [600] [ZenworksWindowsService] [47] [] [ConnectMan] [] [   Using location: http://164.99.186.66:82/zenworks-content/c4097b9680b1384888af3ea61e217a8f.zc, status: Good] [] [] 
 [DEBUG] [05/16/2013 08:57:56.988] [600] [ZenworksWindowsService] [47] [] [ConnectMan] [] [FindFirstContent() returning http://164.99.186.66:82/zenworks-content/c4097b9680b1384888af3ea61e217a8f.zc] [] []

The above logs indicate that the content got replicated successfully from Satellite server (164.99.186.66) to the managed device.

VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

Tags: ,
Categories: Open Enterprise Server, Technical, ZENworks

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

3 Comments

  1. By:warper2

    I am trying to see if this will work on an oes11 server that is running a gw 2012 po and secondary domain. The box was over kill for the site. Can we run a zcm satellite server on this box safely?

    VN:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)
    • By:kjhurni

      All our servers (except 2 now) are OES11/OES 11 SP1 that run groupwise, iPrint, file and function as ZCM Satellite repos with the Auth, Content, and Inventory Rollup roles (not imaging yet).

      However, we didn’t bother storing the content repo on NSS volume as it’s too much of a PITA and Novell’s support of NSS isn’t very useable, IMO.

      But since we’re on OES, we just made an EXT3 partition and we can enable NCP sharing if necessary which avoids a lot of the hassle with NSS mangling and ZCM, while still allowing NCP access if you need it.

      VN:F [1.9.22_1171]
      Rating: 0.0/5 (0 votes cast)
  2. By:kjhurni

    While the above solution is creative and may work, please note that Novell’s official support of NSS for content repo in ZCM requires that you use SAMBA. Since Novell CIFS and SAMBA cannot co-exist, sometimes you may wish to use CIFS on an OES2 server, which will preclude you from using the ZCM Content repo on NSS, as per the ZCM documentation.

    However, you can easily setup an EXT3 area for the content repo and NCP-enable it if you desire (and use CIFS as well).

    https://www.novell.com/documentation/zenworks11/zen11_sys_servers/data/bp0ej6k.html

    VN:F [1.9.22_1171]
    Rating: 0.0/5 (0 votes cast)

Comment

RSS