Hi, > config-synch is your friend here. it provides a knob to duplicate certain > configs (namely vpc related bits) across n5k chassis to reduce the number of > touchpoints for the access-layer configuration. > its pretty handy at times, though its worth playing with in the lab to > understand how the pieces fit together, how to troubleshoot it, and how to > remove/add config snippets in case something goes pear shaped.
When using config-sync make sure that you are running a recent NX-OS version where bug CSCua17122 (http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCua17122) has been fixed. Otherwise you might see the following on both N5k's simultaneously... ----- 8< ----- n5k(config-if)# copy run st [####################################### ] 97%2013 Apr 12 16:27:13.583 n5k %SYSMGR-2-SERVICE_CRASHED: Service "port-profile" (PID 2955) hasn't caught signal 6 (core will be saved). Broadcast message from root (console) (Fri Apr 12 16:27:21 2013): The system is going down for reboot NOW! ----- 8< ----- ...and your whole cluster disappears for several minutes. This should be fixed in: - 5.1(3)N2(1b) - 5.2(1)N1(1a) - 6.0(2)N1(1) Cheers, Sander _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
