Blogs

When changing the guest OS password of root, you may encounter an Authentication token manipulation error. This message occurs because the /etc/shadow file is not present. You can add the shadow file by entering 'pwconv', then the root password can be set. See the example below.

bash-3.2# passwd
Changing password for user root.
passwd: Authentication token manipulation error

bash-3.2# pwconv
bash-3.2# passwd
Changing password for user root. ...Read More

 

In addition to bug fixes, AXP 1.6.2 adds support for the new SM-SRE-710-K9 and SM-SRE-910-K9 service modules. Additionally, the expiration check of the authorization bundle is no longer enforced in AXP 1.6.2. The authorization bundle, which is provided by Cisco Developer Network, grants permission to run applications on the AXP platform. In addition to security information, the authorization bundle also contains an expiration date. Starting from AXP 1.6.2, the check on this expiration date ...Read More

 

The AXP upgrade process provides key features such as automatic deletion of previously installed files that are not included in the upgrade package. However, in order to not delete previously installed files, the upgrade process requires that previously installed files be included in the upgrade package which can lead to bloated packages. To simply the package and reduce package size, users can create a patch to modify only intended files. For example, if the initial installed package contai ...Read More

 

AXP version 1.6.1 has added support for Simple Network Management Protocol SNMPv2c. SNMP commands used in Cisco AXP are similar to Cisco IOS software SNMP commands. The AXP User Guide provides examples of traps generated by agents in SNMP that are utilized by Cisco AXP. Please review the AXP User Guide section 'System Management using SNMP and CDP' along with the Command Reference Guide for more information.
...Read More

 

In addition to bug fixes, the AXP 1.5.2 maintenance release builds upon AXP 1.5.1- see the blog 'AXP 1.5.1 Release - A Giant Leap Forward' - by adding support for two new service modules. The SRE 700 has a 1.86 GHz cpu, 4 GB Ram, and a 500 GB HD. The SRE 900 offers Raid 1 support, has a 1.86 GHz dual core cpu, 4 GB RAM and 2x500 GB HD. Raid-1 and linear raid can be selected as options at install time. This new hardware runs on the new Cisco Generation 2 routers which require IOS re ...Read More

 

AXP takes a huge step forward by adding new hardware support and software features. I¿ll discuss many of the new hardware and features below.
...Read More

 

After downloading the provided AXP gzipped tar files for your service module, if you are using a windows environment, you might decide to untar the files with WinZip. If this choice is made, caution must be taken because WinZip has a 'TAR file smart CR/LF Conversion ...Read More

 

Showing 7 results.
Items per Page 20
of 1

Forums

Combination View Flat View Tree View
toggle
hi,
AXP had been en of sale because we want to use SM-SRE-710-K9 module for Cisco AXP function. We suppose that this is possible. I install sre with this command service-module sm 1/0 install url ftp://user:pass@ip/axp-k9.sme.1.6.2.pkg. so far there is any problem. But we develop an application with linux-ubuntu. When I want to install, I get a error like

Trying Third Party verification
Validating new manifest file /dwnld/pkgdata/VoiceLogger.21.0.pkg from package /dwnld/pkgdata/***.pkg
Validation Failed: Package "***.pkg" is not allowed to run on platform "SM-SRE-710-K9"
ERROR get_pkg_listemoticonackage signature validation failed for ***.pkg
Package signature validation failed for ***.pkg

What is the meaning of this error?
Please answer me, as soon as possible
Thanks for your support.

RE: AXP with SRE
Answer
12/7/12 6:35 PM as a reply to Safiye turgut.
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: AXP with SRE
Answer
12/10/12 12:31 PM as a reply to Safiye turgut.
 
Hi 
 
Thanks for your  reply
 
In the datasheets we saw that SM-SRE-710-K9 supports Cisco AXP, so we bought it.  The pkg is created by us.  For  this, I think there is a any license. Maybe I ask basic questions, but  I want to understand fully.
 
 

RE: AXP with SRE
Answer
12/10/12 7:30 PM as a reply to Safiye turgut.
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

Collateral


No files available