cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
31
Views
0
Helpful
4
Replies
Cisco Employee

XR NED: Aborting because ASR9K reports: The Configuration Namespace is locked by another agent.

 

Hi,

 

 

My customer is testing a relatively simple L2VPN Service, but it appears he has run into an issue with the XR NED. 

 

 

Apparently the NSO commit is aborted because the ASR9K PE router is reporting: "Can not enter exclusive mode. The Configuration Namespace is locked by another agent.”  You can see this in the output of the “commit | details” command:

 

 

admin@ncs(config-pe-device-ASRT-01-LAB)# commit | details

entering validate phase for running...

  validate: run pre-trans-lock service callbacks...

  validate: run transforms and transaction hooks... ok

  validate: pre-trans-lock service callbacks done

  validate: grabbing transaction lock... ok

  validate: creating rollback file... ok

  validate: run transforms and transaction hooks... ok

  validate: mark inactive... ok

  validate: pre validate... ok

  validate: run validation over the change set...

  validate: validation over the change set done

  validate: run dependency-triggered validation...

  validate: dependency-triggered validation done

  validate: check configuration policies...

  validate: configuration policies done

entering write phase for running...

  cdb: write_start

entering prepare phase for running...

  cdb: prepare

  ncs-internal-device-mgr: prepare

  ncs: prepare: calculating southbound diffs...

  ncs: prepare: calculating southbound diffs done

  ncs: device ASRT-01-LAB: send NED prepare

  ncs: device ASRT-03-LAB: send NED prepare

  ncs: prepare: device ASRT-01-LAB: NED error reply: Network Element Driver error ned_external_error for device ASRT-01-LAB: ned_prepare_cli: config exclusive

Thu Mar 24 09:29:07.042 CDT

Current Configuration Session  Line       User     Date                     Lock

00000001-0054c15d-00000000     vty0       mikesau  Thu Mar 24 09:27:28 2016

 

Can not enter exclusive mode. The Configuration Namespace is locked by another agent.

 

  ncs: device ASRT-03-LAB: send NED abort

  ncs: device ASRT-01-LAB: send NED abort

entering abort phase for running...

  cdb: abort

Aborted: Network Element Driver error ned_external_error for device ASRT-01-LAB: ned_prepare_cli: config exclusive

Thu Mar 24 09:29:07.042 CDT

Current Configuration Session  Line       User     Date                     Lock

00000001-0054c15d-00000000     vty0       mikesau  Thu Mar 24 09:27:28 2016

Can not enter exclusive mode. The Configuration Namespace is locked by another agent.

admin@ncs(config-pe-device-ASRT-01-LAB)#

 

This has happened repeatedly.  The customer has confirmed that no users are actively connected to the ASR9K in question. He’s done this by connecting to the 9K and running the following commands:

 

RP/0/RSP0/CPU0:ASRT-01-LAB#show users
Thu Mar 24 09:47:12.495 CDT
   Line            User                 Service  Conns   Idle        Location
*  vty0            mikesau              ssh          0  00:00:00     24.220.16.127

RP/0/RSP0/CPU0:ASRT-01-LAB#show line
Thu Mar 24 09:47:14.799 CDT
   Tty             Speed     Overruns             Acc I/O
   aux0/RSP0/CPU0    9600          0/0                 -/-       
   con0/RSP0/CPU0    9600          0/0                 -/-       
*  vty0               0          0/0                 -/-       
   vty1               0          0/0                 -/-       
   vty2               0          0/0                 -/-       
   vty3               0          0/0                 -/-       
   vty4               0          0/0                 -/-       
   vty100             0          0/0                 -/-       
   vty101             0          0/0                 -/-       
   vty102             0          0/0                 -/-       
   vty103             0          0/0                 -/-       
   vty104             0          0/0                 -/-       
   vty105             0          0/0                 -/-       

RP/0/RSP0/CPU0:ASRT-01-LAB#show ssh

Thu Mar 24 09:47:22.550 CDT

SSH version : Cisco-2.0

id  pty     location          state         userid          host            ver       authentication

---------------------------------------------------------------------------------------------------------------

Incoming sessions

0   vty0    0/RSP0/CPU0     SESSION_OPEN    mikesau     24.220.16.127          v2       password

Outgoing sessions

RP/0/RSP0/CPU0:ASRT-01-LAB#

 

I also asked him to try and move into config mode using the “exclusive” keyword.  It worked, the configuration is not locked:

 

RP/0/RSP0/CPU0:ASRT-01-LAB#configure exclusive

Thu Mar 24 10:29:32.123 CDT

RP/0/RSP0/CPU0:ASRT-01-LAB(config)#

 

Has anyone seen this sort of behavior before? FWIW, I can commit the same service to my ASR9Ks without any issue.

 

 

Regards,

Michael Bonnett, Jr.

 

Everyone's tags (4)
1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: XR NED: Aborting because ASR9K reports: The Configuration Namespace is locked by another agent.

 

Closing the loop on this issue.  It turns out it was a customer error. 

 

 

The customer misconfigured the management address on one of their ASR9Ks.  Accordingly, when NSO attempted to configure the service, it was making two SSH connections to the same router and only able to achieve the config exclusive lock on the first connection.  :-)

 

 

-Michael

 

4 REPLIES 4
Cisco Employee

Re: XR NED: Aborting because ASR9K reports: The Configuration Namespace is locked by another agent.

 

Hi,

 

 

Have you checked the NED raw traces? They would give you a step/by/step understanding of what is going on. Also, make sure you run the latest NED.

 

 

Roque

 

Cisco Employee

Re: XR NED: Aborting because ASR9K reports: The Configuration Namespace is locked by another agent.

 

Thanks, Roque.  I’ll have the customer enable traces and take a look. 

 

 

Does the DevNet portal have the latest NED?  The customer is using cisco-ios 4.0.4.

 

 

-Michael

 

Cisco Employee

Re: XR NED: Aborting because ASR9K reports: The Configuration Namespace is locked by another agent.

 

Correction.  Make that NED cisco-iosxr-4.1.

 

 

-Michael

 

 

Cisco Employee

Re: XR NED: Aborting because ASR9K reports: The Configuration Namespace is locked by another agent.

 

Closing the loop on this issue.  It turns out it was a customer error. 

 

 

The customer misconfigured the management address on one of their ASR9Ks.  Accordingly, when NSO attempted to configure the service, it was making two SSH connections to the same router and only able to achieve the config exclusive lock on the first connection.  :-)

 

 

-Michael

 

Content for Community-Ad
August's Community Spotlight Awards
This widget could not be displayed.