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

errors while trying to connect to the console

Combination View Flat View Tree View
Threads [ Previous | Next ]
Post New Thread
toggle
errors while trying to connect to the console
Answer
7/5/12 7:01 PM
Hi, I am facing an issue and do not know where to find info to even start attacking the problem.
 
I have an SRE module with ACP 1.5.0 installed and being used as a production system. Whenever I try to connect to the console on the AXP app, I am receiven the following error:
 

quanta-vc-2(exec-java)# connect console 
Unable to start the console

 

Also when I open a session to the SRE module I start
receiving this messages on the command line (even if I not execute any command)
regularly about every minute:
 
ERROR sysdb misc allocation (Success) fixtab_deref negative
refcount (-11768 @0x402c68c8)
 
Finally, when I run show running config on the module, I am
getting this error message at the end of the output:
 
ERROR: com.cisco.aesop.platform.conf_hostname@4ca04ca:
com.cisco.aesop.sysdb.nativeSysdbException: attr_relse: attribute reference
invalid

 
Thanks in advance for any help you can provide.
Carlos Alegria
Flag

RE: errors while trying to connect to the console
Answer
7/5/12 7:08 PM as a reply to Carlos Alegria.
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
Flag

RE: errors while trying to connect to the console
Answer
7/5/12 7:41 PM as a reply to Brett Tiller.
Hi Brett,

Thanks a lot for your answer.

Regarding the "unable to connect console" command. The system was working fine till now, and suddenly stopped working.

The thing is that we have this version on a production system and to make an upgrade we need to have a planned shutdown support window, etc.. I would like to know if there is a workaround to hits while we consider and setup the time we need for making an upgrade on the system.

Thanks,
Carlos Alegria
Flag

RE: errors while trying to connect to the console
Answer
7/5/12 9:38 PM as a reply to Carlos Alegria.
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
Flag

Collateral


No files available