Tuesday, April 26, 2011

Can't copy running-config startup-config on N7K running n7000-s1-dk9.5.1.1a.bin

My buddy here flipped me a jewel of a TAC case, I am really glad for the opportunity! We have a N7K that won't allow us to copy running-config startup-config after enabling TACACS on it.

N7k# copy running-config startup-config
Configuration update aborted: another request for config change is already in progress
#
bootflash:///n7000-s1-kickstart.5.1.1a.bin

4 comments:

  1. I'm supposed to talk with the TAC Engineer in an hour or so, buton my own, I've found this:

    https://209.46.39.130/thread/2062170

    ReplyDelete
  2. SO yeah, it turns out we are hitting CSCtj44206. The bug is 100% match.

    N&K# sh log | in KERN
    2011 Feb 17 14:34:28 N7K Feb 17 14:34:27 %KERN-3-SYSTEM_MSG: dev_add_pack - kernel
    2011 Mar 31 01:04:22 N7K Mar 31 01:04:22 %KERN-2-SYSTEM_MSG: Utaker overflowed. Size -40/5242880 - kernel

    ReplyDelete
  3. It was great to watch him troubleshoot this. First the Engineer wanted to see if interfal file systems were full, check buffers and locked processes. . . here are commands he used:

    # sh system internal flash

    # sh sys inte dir /isan

    # sh sys inte dir /sys

    # sh sys internal mts buffers summ

    # sh sys internal sysmgr startup-config state

    # show system internal dir /var/sysmgr

    # sh sys inte mts buff summ

    and finally to find the bug:

    sh log | in KERN

    ReplyDelete
  4. Also a separate bug that is VERY close to this:
    CSCtj83417

    ISSD fails or 'copy failed (error-id 0x401E0000)' error
    Symptom:
    ISSU fails or attempts to save the config cause the following syslog messages:

    %SYSMGR-2-CFGWRITE_ABORTED: Configuration copy aborted.
    %SYSMGR-3-CFGWRITE_FAILED: Configuration copy failed (error-id 0x401E0000).

    Conditions:
    This issue is caused when a service that needs to resolve IP addresses (such as TACACS or syslog) is running and the 'no ip domain-lookup' command has been configured.

    Workaround:
    1) Disable the affected feature (eg, TACACS), if possible. Go to step 2, regardless.
    2) Enable DNS resolution with the 'ip domain-lookup' command.
    3) Renable the affected feature. If this is not possible (eg, syslog) then multisupervisor systems will require a 'system switchover' and single supervisor systems will require a reload.

    ReplyDelete