RE: Inconsistent results installing package.

RE: AXP 1.5 upgrade

2013-04-04T00:01:52Z

Hi Carlos, Your application will not be affected by the upgrade process as long as you are upgrading the host. We do recommend that when moving from one major release to another, in the case 1.5 to 1.6, that you repackage your application with the latest SDK and then upgrade the application as well. The AXP Developer Guide has more detailed information. In terms of backing up the virtual instance data, assuming you've configured it for access, you can console in, tar up your files and use curl to ftp them to your ftp server. Thanks, Brett

RE: axp application started with failure: License expired

2013-01-08T01:13:01Z

Hi Vijay, Please attach your certificate with your response or email it to: axp-response@cisco.com . Thanks, Brett

RE: AXP with SRE

2012-12-10T19:30:26Z

Hi Safiye, If you purchased an AXP license with the service module, please let us know your sales order number and we can look into potentially migrating that license to SRE-V. As I mentioned earlier the SRE-V product is the next generation virtualization platform after AXP. To try out SRE-V now, you can download the platform from http://developer.cisco.com/web/srev/documentation , and install it onto the service module via the router CLI . You can download the vSphere client by entering the service-module IP into a browser and downloading it from web page. Then simply start up the client and log into it with that same IP. The default user ID for logging in is 'root' and the password is blank. I've provided a sample configuration for SRE-V below. If you have technical questions regarding SRE-V, please post them in the 'SRE-V Technical Questions' forum at http://developer.cisco.com/web/srev/community . Sample Router Configuration interface SM1/0 ip address 192.168.1.100 255.255.255.0 service-module ip address 192.168.1.1 255.255.255.0 service-module ip default-gateway 192.168.1.100 interface SM1/1 switchport mode trunk Thanks, Brett

RE: AXP with SRE

2012-12-07T18:35:55Z

Hi Safiye, The issue you are seeing is most likely caused by the developer certificate you packaged with your application. Most likely it doesn't allow the package to be installed on the SM-SRE-710-K9 hardware because that SKU is not specified in the certifcate. Since you're already using an SM-SRE-710-k9 service module, we strongly recommend that you move to our next generation product, SRE-V which is the Service Ready Engine Virtualization. This platform includes VMware ESXi so that you can install your own OS into a virtual machine. As a result you won't have any issues with porting your application as you might experience with AXP. In addition there are no developer certificates as with AXP that would lead to issue that you are currently experiencing. Finally as you know AXP is EOS/EOL and we are not accepting new partners onto the product as specified in the AXP technical center at: http://developer.cisco.com/web/axp. You can download the SRE-V platform and documentation from http://developer.cisco.com/web/srev . Thanks, Brett

RE: errors while trying to connect to the console

2012-07-05T21:38:44Z

Hi Carlos, If logging into the console was working earlier from the VM prompt, and you haven't made any changes, please try reloading the VM and see if that resolves the issue. Exactly what version of AXP are you using? You can type 'show software version' on the AXP prompt to get that information. Thanks, Brett

RE: errors while trying to connect to the console

2012-07-05T19:08:37Z

Hi Carlos, The “connect console” command will fail if there has not been a console link created in the post-install script. This link should be created in the script and this script should be referenced via the –post-install link in the packaging script. You can read about how to configure this access in the AXP Developer Guide in section Accessing the Guest Operating System. Regarding the other errors you are seeing, I suggest that you download/install the latest AXP 1.6.2 release since there are many bug fixes since the 1.5.0 release. Please note that AXP has been announced as end-of-life and that we strongly recommend that you migrate to its replacement product Service Ready Engine Virtualization (SRE-V). You can read more about this product and download files at http://developer.cisco.com/web/srev/docs . Thanks, Brett

RE: Clean Software Installation

2012-04-10T19:40:28Z

Hi Safiye, Nice job. If you were trying to install the platfrom again and the clean install was failing another option would be to clear the cache on the service module via the command "software remove all", then retry the installation. Thanks, Brett

RE: Clean Software Installation

2012-04-09T18:48:28Z

Hi Safiye, Regarding the error message you are seeing: "Error: The package contains only add-ons, which is not valid for clean-install", a clean install requires that the AXP platform is being installed alone or bundled with another package. Is the VoiceLogger.13.0.pkg bundled with the AXP platform? If not, you can bundle using the pkg_bundle.sh script located in the tools directory of the SDK. If this response does not answer your question, please respond with details of what you are trying to do along with the version of AXP that you are using. Thanks, Brett

RE: sftp & AXP 1.6.2

2012-04-06T18:27:39Z

Hi Ashish, We've reproduced this issue and have filed a bug. Our engineering and marketing teams will review it for prioritization and so forth. More information is available in your filed service request #621198571. Thanks, Brett

RE: Inconsistent results installing package.

2012-02-27T20:59:30Z

Tom, Before I discuss the rpm installation failure issue I just wanted to mention that you can bundle everything together with the AXP platform and do one installation which would be a huge timesaver in your case. The script that bundles packages together is located in the sdk tools directory and is called axp_bundle.sh. You can read more about bundling in the AXP Developer Guide section 'Bundling Tool'. The install.log and messages.log files are showing errors in the rpm database during the install of each rpm. Since we cannot reproduce that error in our labs, I'm going to now assume that this error is causing the installation of each rpm to fail. As I mentioned earlier via research I've done removing and then rebuilding the rpm database should resolve that issue. As a result I would suggest writing a script that will install the rpms and check for errors after each install and if one has occurred rebuild the rpm database and then reattempt the installation. The script would therefore manage the rpm installation rather than the AXP host. I've written such a script below as an example that would be added to or replace the post-install.sh script that gets called when the installation has been completed. Note that the rpm files are now located in the directory called "third_party_rpms" since that name directory change will cause the AXP host to not attempt to install the rpms itself. Although this script is merely an example, and is not tested, you're certainly welcome to use, modify and of course test it for your own needs. #! /bin/sh ln -s /bin/bash /bin/console theDir="third_party_rpms" rpms="python-urlgrabber-3.1.0-2.noarch.rpm libtalloc-2.0.1-11.el5.i386.rpm libtiff-3.8.2-7.el5_6.7.i386.rpm samba3x-3.5.4-0.83.el5.i386.rpm python-sqlite-1.1.7-1.2.1.i386.rpm libtdb-1.2.1-6.el5.i386.rpm iproute-2.6.18-7.el5.i386.rpm tftp-server-0.49-2.el5.centos.i386.rpm logrotate-3.7.4-12.i386.rpm ethtool-5-1.el5.i386.rpm mcstrans-0.2.7-1.el5.i386.rpm module-init-tools-3.3-0.pre3.1.37.el5.i386.rpm yum-metadata-parser-1.1.2-2.el5.i386.rpm tcp_wrappers-7.6-40.7.el5.i386.rpm libpng-1.2.10-7.1.el5_5.3.i386.rpm samba3x-winbind-3.5.4-0.83.el5.i386.rpm perl-5.8.8-32.el5_6.3.i386.rpm libsysfs-2.0.0-6.i386.rpm expat-1.95.8-8.2.1.i386.rpm mingetty-1.07-5.2.2.i386.rpm MAKEDEV-3.23-1.2.i386.rpm zlib-1.2.3-3.i386.rpm glibc-common-2.5-24.i386.rpm libvolume_id-095-14.16.el5.i386.rpm psmisc-22.2-6.i386.rpm gdbm-1.8.0-26.2.1.i386.rpm vixie-cron-4.1-77.el5_4.1.i386.rpm libsmbclient-3.0.33-3.29.el5_6.2.i386.rpm centos-release-5-2.el5.centos.i386.rpm samba3x-client-3.5.4-0.83.el5.i386.rpm libxml2-2.6.26-2.1.2.1.i386.rpm libjpeg-6b-37.i386.rpm libgpg-error-1.4-2.i386.rpm xinetd-2.3.14-13.el5.i386.rpm db4-4.3.29-9.fc6.i386.rpm samba3x-common-3.5.4-0.83.el5.i386.rpm udev-095-14.16.el5.i386.rpm rpm-python-4.4.2-48.el5.i386.rpm rsync-3.0.6-4.el5.i386.rpm gnutls-1.4.1-3.el5_4.8.i386.rpm binutils-2.17.50.0.6-6.el5.i386.rpm cups-libs-1.3.7-26.el5_6.1.i386.rpm yum-3.2.8-9.el5.centos.1.noarch.rpm openldap-2.3.43-12.el5_6.7.i386.rpm libgcrypt-1.4.4-5.el5.i386.rpm python-2.4.3-21.el5.i386.rpm python-elementtree-1.2.6-5.i386.rpm cyrus-sasl-lib-2.1.22-5.el5_4.3.i386.rpm" for theRpm in $rpms do rpm -ivh --nodeps /$theDir/$theRpm if [ $? ne 0 ]; then rm -f /var/lib/rpm/_db.* rpm --rebuilddb rpm -ivh --nodeps /$theDir/$theRpm fi done

RE: Inconsistent results installing package.

2012-02-23T22:56:50Z

Tom, I've run five separate tests to attempt to reproduce the issue and have not been able to do so. However, I have also been researching your issue based upon the messages in the logs you've provided. Next time you encounter this issue, I'd like you to try the commands below and let me know if it resolves it. Based upon my research I think the rpm files were probably installed; however, the rpm database was somehow corrupted, so deleting the database files and rebuilding the database might resolve the issue. 1. Access the wds guest environment shell. 2. type: rm -f /var/lib/rpm/__db.* 3. type: rpm --rebuilddb 4. type: yum Thanks, Brett

RE: Cannot upgrade OS or package, read only file system

2012-02-23T22:08:54Z

Tom, I've got the file and will hold onto it should you encounter this issue again. Glad things are working. Brett

RE: Inconsistent results installing package.

2012-02-23T02:46:58Z

Tom, Thanks for the files. I've run several tests so far following your steps, but have not yet reproduced the issue you are experiencing. I will continue investigating this issue and get back to you when I have more data to provide. Thanks, Brett

RE: Cannot upgrade OS or package, read only file system

2012-02-22T23:41:18Z

Tom, Thanks for posting the file. Unfortunately this file is only 29 bytes long, so I'm not sure if something occurred when you were uploading it or otherwise. Assuming the file you have on your workstation is much larger please repost it with a different name, assure the posted filesize makes sense, and then let me know the filename. Also I'd just like to confirm that you already tried rebooting the service module? Thanks, Brett

RE: Inconsistent results installing package.

2012-02-22T02:58:38Z

Hi Tom, We haven't had any luck so far reproducing the issue you are experiencing. Would you mind sharing your application package and payload files, .pkg and .prt1 with us? This way we can review them and test them in our lab. If you're ok with this, please upload them to the file server and let me know the name(s) when done. Thanks, Brett

RE: Inconsistent results installing package.

2012-02-22T00:38:37Z

Hi Tom, Please ignore my first question. The logs show that you had repackaged the application using the 1.6.2 SDK. Thanks, Brett

RE: Inconsistent results installing package.

2012-02-22T00:22:45Z

Hi Tom, I'm reviewing the files now. I don't see any reported issues during the packaging phase, however I have a few questions as I'm seeing a few unexpected error/warning messages during the installation of the third party rpms where the application installation of Yum fails. 1. Did you repackage the application using the 1.6.2 SDK? 2. When you used the previous release of AXP 1.5.3, did you experiencing any of the same failures when installing Yum? 3. You mentioned that as a work around reinstalling appears to resolve the issue. What are your complete workaround steps? Thanks, Brett

RE: Cannot upgrade OS or package, read only file system

2012-02-21T22:36:52Z

Hi Tom, On the service module on which the install is failing, please enter the command below and then retry the installation. I'm not sure that this command will resolve your issue, but I think it's worth trying. The command removes all of the downloaded files from the buffer which can sometimes cause strange errors during installation. software remove all Thanks, Brett

RE: Cannot upgrade OS or package, read only file system

2012-02-21T22:29:08Z

Hi Tom, Please send over the tech-support logs and the data showing your installation attempt along with the error message for one of these service modules on which the installation is failing. You can get the tech-support logs by sessioning into the service module and typing: copy tech-supp url ftp://@ . If the file is larger than 5 MB, please upload it to our ftp server and let me know the file name(s). I've provided the instructions below. Upload Instructions for External Users: Connect to ftp.cisco.com via anonymous ftp. Files must be uploaded into a folder called 'incoming', which is not visible to anonymous users If you are using a text-based ftp client, type the command "cd incoming" If you are using a GUI ftp client such as FileZilla, enter 'incoming' manually as the destination for the remote site Upload the file as normal. You will not be able to see it on the server, as commands to list the files in that folder have been disabled. You may see error messages related to that. NOTE: You cannot upload a file with the same name more than once as this creates the potential for other users to overwrite the files you have uploaded. If you need to re-upload the same file, either use a new filename or ask the Cisco employee you are working with to remove the file from the server. Thanks, Brett

RE: Inconsistent results installing package.

2012-02-21T22:20:37Z

Tom, Unfortunately I don't see the file on the server, so it must've been cleared. Please upload it again and let me know when it's ready. Thanks, Brett