cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1831
Views
0
Helpful
1
Replies

SYSMGR-STANDBY-6-SERVICE_STARTED:

healyj4
Level 1
Level 1

Hi,

IHAC whose MDS streams the following, seen on 2 switches so far:

2011 Mar 18 06:06:59 mds %SYSMGR-STANDBY-6-SERVICE_STARTED: Service "System Manager (core-client)" in vdc 1 started with PID(26690).
2011 Mar 18 06:07:00 mds %SYSMGR-STANDBY-6-SUBPROC_SUCCESS_EXIT: "System Manager (core-client)" (PID 26690) has successfully exited with exit code SYSMGR_EXITCODE_SUCCESS (0).
2011 Mar 18 06:08:33 mds %SYSMGR-STANDBY-6-SERVICE_STARTED: Service "System Manager (core-server)" in vdc 1 started with PID(26709).
2011 Mar 18 06:08:33 mds %SYSMGR-STANDBY-6-SUBPROC_SUCCESS_EXIT: "System Manager (core-server)" (PID 26709) has successfully exited with exit code SYSMGR_EXITCODE_SUCCESS (0).
2011 Mar 18 06:10:00 mds %SYSMGR-STANDBY-6-SERVICE_STARTED: Service "System Manager (core-client)" in vdc 1 started with PID(26711).
2011 Mar 18 06:10:00 mds%SYSMGR-STANDBY-6-SUBPROC_SUCCESS_EXIT: "System Manager (core-client)" (PID 26711) has successfully exited with exit code SYSMGR_EXITCODE_SUCCESS (0).
2011 Mar 18 06:11:33 mds %SYSMGR-STANDBY-6-SERVICE_STARTED: Service "System Manager (core-server)" in vdc 1 started with PID(26728).
2011 Mar 18 06:11:33 mds %SYSMGR-STANDBY-6-SUBPROC_SUCCESS_EXIT: "System Manager (core-server)" (PID 26728) has successfully exited with exit code SYSMGR_EXITCODE_SUCCESS (0).
2011 Mar 18 06:13:00 mds %SYSMGR-STANDBY-6-SERVICE_STARTED: Service "System Manager (core-client)" in vdc 1 started with PID(26735).
2011 Mar 18 06:13:00 mds %SYSMGR-STANDBY-6-SUBPROC_SUCCESS_EXIT: "System Manager (core-client)" (PID 26735) has successfully exited with exit code SYSMGR_EXITCODE_SUCCESS (0).

Any ideas of the meaning/switch impact.

Thanks and rgds,

Jim.

1 Reply 1

kenk
Cisco Employee
Cisco Employee

Hello Healyj4,


The messages are informational (not indicative of a problem).


These messages are informational only and if you do not want to include
informational and debugging messages in the logfile,
then please configure:
  
     logging logfile messages 5  ( this is the default )

If the above does not resolve the issue, I would recommend opening a Service Request with the
appropriate TAC team.

Regards,

Ken