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
First Previous Next Last

Forums

« Back to Technical Questions

Development authorization is not valid before 2008-01-01

Combination View Flat View Tree View
Threads [ Previous | Next ]
Post New Thread
Development authorization is not valid before 2008-01-01
Answer
10/9/08 12:53 PM
I am trying to install an application in my AXP using:
"software install add url ftp://10.0.0.11/test_app.1.0.pkg"
and it returns me the following message:

Validating new manifest file /dwnld/pkgdata/test_app.1.0.pkg from package /dwnld/pkgdata/test_app.1.0.pkg
Validation Failed: Development authorization is not valid before 2008-01-01T00:00:00+00:00
Package signature validation failed for test_app.1.0.pkg

Then i am trying the following:
myAXP-blade> sho clock
04:38:11.646 EEST Fri May 05 2006
myAXP-blade> conf t
Enter configuration commands, one per line. End with CNTL/Z.
myAXP-blade(config)> clock timezone America/New_York
Save the change to startup configuration and reload the module for the new timezone to take effect.
myAXP-blade> show clock
21:41:35.904 EDT Thu May 04 2006

I am trying also to set an ntp server (nist1.columbiacountyga.gov 68.216.79.113 Columbia County, Georgia) but i get the following message:

WARNING!!! Could not reach 68.216.79.113 using NTP.
WARNING!!! 68.216.79.113 might not have been configured as
WARNING!!! NTP server.
WARNING!!! NTP Server 68.216.79.113 Will be entered in the NTP List

Is there any "clock set" functionality in order to set manually the date/time?

Thanks in advance
George
Flag

Re: Development authorization is not valid before 2008-01-01
Answer
10/9/08 9:13 PM as a reply to George K.
George,

You can do the following to correct date / time on AXP blade

Step 1 On the router:
a. Configure the ISR as an NTP master server.

configure terminal
ntp master

b. (Optional) ntp server {hostname|ip-address}
This step is optional, but recommended. Use this command to set an external server as the source for providing clock synchronization.

c. Configure the correct time zone on the router.

clock timezone zone
copy running-config startup-config
exit

Step 2 On the Cisco AXP service module:
a. Configure the Cisco AXP service module’s NTP server to point to the source router providing the clock synchronization.

configure terminal
ntp server router-ip address
end
write memory or copy running-config startup-config

b. Configure the time zone on the Cisco AXP service module to be the same as the source router time zone. Reload the module for the new time zone to take effect.

configure terminal
clock timezone
end
write memory or copy running-config startup-config
reload
Flag

Re: Development authorization is not valid before 2008-01-01
Answer
10/10/08 12:26 PM as a reply to George K.
Thank you very much for your reply.
It solved the "clock" issue.

George
Flag

Collateral


No files available