How to configure Version Control Repository Manager.

[User_Feo]

Hello!

I am having a heck of a time configuring  the Version Control Repository Manager.  Can some one please point in the right direction?

Thanks,

Alberto

[Bart_Heungens]

Hi,

Where do you have a problem with the configuration?

First you have to logon to the VCRM console

Then you have to upload at least on PSP Proliant Support Pack in it via the Upload functionality

And that is it... Shouldn't be too hard...

Afterwards you have to connect to the VCA Version Control Agent on a remote server and configure it so that it connects to the VCRM server.

One important thing there to know is that you must enter a username and password to connect to the VCRM server. And this account can't be the administrator account of that server, for security purposes...

So you should create a local account on the server where VCRM is running (or use a domain account) for use inside the VCA...

Kr,

Bart

[User_Feo]

Thanks Bart, potentially my challenge is your first suggestion ....  How do I login into the VCRM console?  Since, i do not see an opition after the installation was completed.

I have installed the VCRM app, which I've downloaded from HP and created a repository.  I installed the VCRM on the same server as SIM, is that a best practice?

Thnaks,

Alberto

[Bart_Heungens]

That is already a good start. Yes VCRM is mostly installed on the SIM server since it is not taking that much resources...

You can access the VCRM console via the SMH System Management Homepage via the green icon on your desktop or via https://servername:2381. You have to logon with OS credentials and then you will find a shortcut to the VCRM pages...

[dajdza]

Hello Bart,

I need also a little bit help with VCRM.

Some information about the HW and SW. Its a VM with SLES11 on that we installed HP SIM 7.2.

Once i get lucky and VCRM work it, but now i got some erros they drive me crazy!

Inside the log of VCRM I got this Error:

Entry Details 
Severity  Error  
Date / Time  
Message The Linux Version Control Repository Manager could not process the HTTP request because it contained invalid data. 
Additional Data 
HTTP_ACCEPT:text/html, application/xhtml+xml, */*
HTTP_ACCEPT_ENCODING:gzip, deflate
HTTP_ACCEPT_LANGUAGE:de-DE
HTTP_APPNAME:vcrepository
HTTP_CONNECTION:Keep-Alive
HTTP_COOKIE:JSESSIONID=91C0C9D7429030F75B432101D500E936; Compaq-HMMD=0001-f02807e3-723c-4e12-a21e-4643e7b1d697-1364887317351759; mx-time-zone=Africa/Ceuta; HPSMH-browser-check=done for this session; curlocation-root=?chppath=Home%3A%3AVersion%20Control&chppage=HP%20Linux%20Version%20Control%20Repository%20Manager&chpurl=/cgi-bin/vcrepository/cgi&chptarget=undefined
HTTP_HOST:192.168.10.105:2381
HTTP_HPSMH_AUTHLEVEL:4
HTTP_HPSMH_SESSIONDIR:/opt/hp/hpsmh/session/0001
HTTP_HPSMH_USER:root
HTTP_HPSMH_USERTYPE:osuser
HTTP_LOGLEVEL:0
HTTP_REFERER:https://192.168.10.105:2381/cgi-bin/vcrepository/cgi
HTTP_USERLEVEL:4
HTTP_USERNAME:root
HTTP_USER_AGENT:Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)
HTTP_VCREPOSITORY_PROP::11;READ_ONLY:11;:11;OPER_READ_WRITE:11;:11;

/cgi-bin/vcrepository/cgi 

Also on the VCA i got this message:

Software Status  

Overall Software Status:    Status cannot be calculated because a Version Control Repository Manager has not been named. Click on change settings to specify a Version Control Repository Manager. 

Is this configuration ok?

 

I think a made configuration mistake at the beginning.... but where?

Its just exasperating...

Yours and anybodys else help is really appreciated. Thank you!

Sorry for my grammar.

Regards

[dajdza]

Hello again,

I made a new custime Basline with HP SUM and VCRM show´s me now all that pretty stuff. Unfortunately there is another Problem. When i go to

Deploy > Software/Firmware Baseline > Manager SW FW Basline

there wase nothing, so I go to "Select Default Version Control Repository" and see this:

on "configure" I set by Name and put it the server name hp-sim-suse11 thats the host name of this maschine.

If i want to assign a server to this Basline it says now baseline... logical because at >>

Deploy > Software/Firmware Baseline > Manager SW FW Basline

there is also no baseline.

What i am missing here?

Also the VCA Problem still exists, here some SS:

Thank you very much!

[dajdza]

Ok, got it also :D

I was changing the Setting on the VCA and by Computername i type hp-sim-suse11, Unfortunately i just can login as root although i got a normal user but it didn not work... Maybe i need to create one on hp sim not just on the linux maschine.

Whatever, now i got this 

SNMP and WBEM are installed on this maschine, under ps aux | grep snmp i got 

hp-sim-suse11:/opt/hp/vcagent/etc # ps aux|grep snmp
root      2758  0.0  0.1  24976  7956 ?        Sl   09:14   0:04 /usr/sbin/snmpd -r -A -LF i /var/log/net-snmpd.log -p /var/run/snmpd.pid
root     32166  0.0  0.0   2408   472 pts/0    S+   12:53   0:00 grep snmp

[dajdza]

anyone?

[xismsou]

Hi,

This problem seem occur because the vca cannot collect info from the snmp-agent

due certainly acces right

Verify your snmpd.conf file and add entry view systemview included .1 80

You also can read this

http://bizsupport1.austin.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=120&prodSeriesId=3927988&prodTypeId=18964&objectID=c02260387&printver=true

Regards

[dajdza]

Hi xismsou, thanks for your answer!

I changed the snmpd.conf to this:

but it still don't work... I restarted the snmp service, also the hp smh, but with no effects..

maybe I got some unnecessary packets installed? Screenings below

###########################################################################
#
# snmpd.conf
#
#   - created by the snmpconf configuration program
#
###########################################################################
# SECTION: System Information Setup
#
#   This section defines some of the information reported in
#   the "system" mib group in the mibII tree.

# syslocation: The [typically physical] location of the system.
#   Note that setting this value here means that when trying to
#   perform an snmp SET operation to the sysLocation.0 variable will make
#   the agent return the "notWritable" error code.  IE, including
#   this token in the snmpd.conf file will disable write access to
#   the variable.
#   arguments:  location_string

syslocation  aaa

# syscontact: The contact information for the administrator
#   Note that setting this value here means that when trying to
#   perform an snmp SET operation to the sysContact.0 variable will make
#   the agent return the "notWritable" error code.  IE, including
#   this token in the snmpd.conf file will disable write access to
#   the variable.
#   arguments:  contact_string

syscontact  "aaa"

# sysservices: The proper value for the sysServices object.
#   arguments:  sysservices_number

sysservices 76

###########################################################################
# SECTION: Access Control Setup
#
#   This section defines who is allowed to talk to your running
#   snmp agent.

# rouser: a SNMPv3 read-only user
#   arguments:  user [noauth|auth|priv] [restriction_oid]

rouser  noauth noauth 

# rocommunity: a SNMPv1/SNMPv2c read-only access community name
#   arguments:  community [default|hostname|network/bits] [oid]

rocommunity  public  

trapsess 192.168.10.105 public

trap2sink 192.168.10.105 public

view systemview included .1 80

##########################################################################
# SECTION: Monitor Various Aspects of the Running Host
#
#   The following check up on various aspects of a host.

# proc: Check for processes that should be running.
#     proc NAME [MAX=0] [MIN=0]
#   
#     NAME:  the name of the process to check for.  It must match
#            exactly (ie, http will not find httpd processes).
#     MAX:   the maximum number allowed to be running.  Defaults to 0.
#     MIN:   the minimum number to be running.  Defaults to 0.
#   
#   The results are reported in the prTable section of the UCD-SNMP-MIB tree
#   Special Case:  When the min and max numbers are both 0, it assumes
#   you want a max of infinity and a min of 1.

proc  snmpd 1 1

# disk: Check for disk space usage of a partition.
#   The agent can check the amount of available disk space, and make
#   sure it is above a set limit.  
#   
#    disk PATH [MIN=100000]
#   
#    PATH:  mount path to the disk in question.
#    MIN:   Disks with space below this value will have the Mib's errorFlag set.
#           Can be a raw byte value or a percentage followed by the %
#           symbol.  Default value = 100000.
#   
#   The results are reported in the dskTable section of the UCD-SNMP-MIB tree

disk  / 100000

# load: Check for unreasonable load average values.
#   Watch the load average levels on the machine.
#   
#    load [1MAX=12.0] [5MAX=12.0] [15MAX=12.0]
#   
#    1MAX:   If the 1 minute load average is above this limit at query
#            time, the errorFlag will be set.
#    5MAX:   Similar, but for 5 min average.
#    15MAX:  Similar, but for 15 min average.
#   
#   The results are reported in the laTable section of the UCD-SNMP-MIB tree

load  30 60 90

master agentx