Hi all,
 
Anybody knows the exact procedure or approach to obtain authorization bundle ?
What are the inputs in order to get the bundle ?
 
 
Regards,
Zoebir Bong

Hi Raghavendra,


From the link you stated, should I provide Cisco public key or private key.
I know the way to generate private key as stated in AXP Developer Guide.

Do you have any Cisco email address for me to send them my public/private key ?

Thanks,
Zoebir

Hi Zoebir,

We can provide you with a private/public key in addition to the authorization bundle if you prefer. The e-mail you will send opens a channel to our martketing team where you'll let them know of the product you are creating and other needs. They'll provide more detail.

If you are just beginning to work with AXP, we recommend that you review our next generation virtualization product, Service Ready Engine Virtualization (SRE-V). With this product, authorization bundles, packaging and application porting are not required. You can learn more about this product at http://developer.cisco.com/web/srev and www.cisco.com/go/ucse.

Thanks,

Brett

Hi Zoebir,

That's correct, the SRE-V product does not currently support router event notification. For now I suggest you continue with your plans to use AXP. When you contact our marketing team via ask-axp-pm@cisco.com, please let them know of your functional needs as well. BTW

Thanks,

Brett

Hi all,
 
Thanks Anurag for helping me getting authorization bundle.
 
I faced some issue during packaging build.
 
My development machine is on Ubuntu 10.04 Desktop.
* Linux gs21 2.6.32-31-generic #61-Ubuntu SMP Fri Apr 8 18:24:35 UTC 2011 i686 GNU/Linux
 
 I attached my core.log for analysis.
 
My print out of pkg_build.sh is as following:

SLIM Packaging Utility. (C) 2007-2010 Cisco Systems, Inc
Checking dependencies...
 
WARNING: If an application from AXP 1.0/1.1 is repackaged to be installed
         on AXP 1.5, please make sure to increment the application version
  - Fixing Script Path: bin/post-install.sh -> ./bin/post-install.sh
Generated swap option: OFF
Generated share timezones option:  ON
Generated shutdown timeout option: 30
INFO: 16mb will be added to the application's memory requirements to support
      the application's tmpfs file system (/tmp)
Creating project directories...
Generated Application UUID: e5d40c1f-7226-45bc-b35f-813d782d1f67
Preparing configuration for the core packaging tool...
Creating runtime signatures...
Generating a list of files to package...
Preparing package manifest...
Processing manifest file information...
Error: exiting (102 main /home/zoebir/work/cemnet/DTWAN/2-AXP_IMPL/sdk/axp-sdk.1.6.1/lib/pkg/scripts/utils/files_notin_compfilelist.sh)
Invoking core SLIM packaging utilities...
SLIM packaging core log file saved to: /home/zoebir/work/cemnet/DTWAN/2-AXP_IMPL/project/myhelloworld_proj/package/tmp/core.log
Renaming MyHelloWorld.pkg -> MyHelloWorld.1.0.pkg


My print output of pkg_check.sh :

Library Dependency Checker Utility. (C) 2007-2009 Cisco Systems, Inc
Checking dependencies...
pkg_check.sh: Utility 'lddlibc4' not found. Packaging cannot continue.
pkg_check.sh: Please install 'lddlibc4' and try again



Eventhough it had error, .pkg and .prt1 files are created. I tried to install the package on AXP and it showed no error during installation.
But it failed to start application (reason stated on AXP when executing "show state"). 


Qns 1: Why I can still install package on AXP even there is an error during packaging ?
Qns 2: Does failure in staring application relates to packaging error ? new issue ?
 
P.S. I modify original example HelloWorld by printing additional date information.

Please advise.


Thanks and Regards,
Zoebir

Attachments:

Hi Zoebir,

The reason your package is still being created is that there are several scripts that are called to created the package, and in this case an unexpected error occurred in a branch script that did not cause the main script to fail. This error is not being shown in the core.log file you provided which means your system is most likely reporting this error since it was not captured in our log. Try removing files/directories after the package directory, 'rm -rf package/*' and see if this resolves your packaging issue.

Regarding the pkg_checker.sh script, you are missing a required library and need to install the corresponding rpm file into your development environment if you want to use this script.

When you say that the application did not run, does the virtual instance start? Please post the data from the 'show state' command. If the VI is not running, then as Raghavendra pointed out you can check the messages.log file for errors. If you are not able to resolve this issue we'll need to review the system logs to determine to cause of the failure. You can get them by typing on the service module:

'copy tech-support url ftp://ip/dir/filename'

Thanks,

Brett