MDS 9513 clockcard DFM alert

Answered Question
Nov 7th, 2008

Under DFM - Alerts and Activities I'm getting a Utilization alert saying Clockcard is not present. When I go into the device it indeed says it is not present but I'm not given the option to uncheck it so that it won't be monitored. How do I get rid of this alert? See attached.

I have this problem too.
0 votes
Correct Answer by Joe Clarke about 8 years 3 weeks ago

Yeah, it looks like those subclasses are now missing from the FRU list. You shouldn't see any more events for those components moving forward.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Joe Clarke Sun, 11/09/2008 - 11:07

This is currently not doable from within the UI. However, if you have DFM 2.0.10 or higher, you should have some bulk management scripts under NMSROOT/objects/smarts/utils.

Copy the *ManagedStateProcess.asl files to *ManagedStateCard.asl, then modify the scripts so that all instances of "Processor" and "Proc" are replaced with "Card". Then, copy the *StateProc.ksh or .bat files to *StateCard.ksh or .bat, and again change all occurrences of "Processor" and "Proc" to "Card". Then, you will be able to use the instructions found at http://SERVER/help/dfm_newui/bulk_manage.html to unmanage the card you want.

Joe Clarke Sun, 11/09/2008 - 11:27

Actually, given that this is DFM 2.0, it would be better to do:

NMSROOT/objects/smarts/bin/dmctl -s DFM invoke Card::CARD-123.133.5.146/25751 unmanage true

Than, on Solaris:

NMSROOT/objects/smarts/utils/apply.ksh

Or Windows:

NMSROOT\objects\smarts\utils\apply.bat

nancyrawls Mon, 11/10/2008 - 07:49

Found dmctl.exe. What exactly is the command I need to run and what does it do?

Thanks.

Joe Clarke Mon, 11/10/2008 - 09:02

NMSROOT\objects\smarts\bin\dmctl.exe -s DFM invoke Card::CARD-123.133.5.146/25751 unmanage true

Then:

NMSROOT\objects\smarts\utils\apply.bat

This will unmanage the card in question within DFM.

nancyrawls Mon, 11/10/2008 - 10:04

dmctl> -s DFM invoke Card::CARD-123.133.5.146/25751

Invalid command '-s' -- try again.

Joe Clarke Mon, 11/10/2008 - 10:07

You have run dmctl interactivly. If you ran the command exactly how I wrote it, you should see the dmctl prompt. However, from this prompt, you can do:

invoke Card::CARD-123.133.5.146/25751 unmanage true

Then exit from dmctl, and run the apply.bat command.

nancyrawls Mon, 11/10/2008 - 10:21

dmctl> invoke Card::CARD-123.133.5.146/25751 unmanage true

Not attached.

Joe Clarke Mon, 11/10/2008 - 10:23

It sounds like you just ran dmctl without any arguments. In that case, you would first need to run:

attach DFM

nancyrawls Mon, 11/10/2008 - 10:58

Our tried that with our admin account and it says Permission denied. Is there a default account I can use? It probably wasn't changed. Thanks.

Joe Clarke Mon, 11/10/2008 - 11:03

Exit the dmctl prompt, then run the following command:

NMSROOT\objects\smarts\bin\dmctl -s DFM

What output do you get?

nancyrawls Mon, 11/10/2008 - 11:43

That path is not the path I have therfore it didn't work. I did try running the same command from where my files are located and get the same thing - it's asking for a user id and password:

C:\Program Files\CSCOpx\objects\smarts\bin>dmctl -s DFM

Server DFM User: cisco

cisco's Password: XXXXX

dmctl: Could not attach to 'DFM': Login to Domain Manager failed; permission de

ied

Joe Clarke Mon, 11/10/2008 - 11:45

This is typically admin/admin. However, you can find the value in C:\Program Files\CSCOpx\objects\smarts\conf\clientConnect.conf. This command must succeed for you to accomplish what you want.

nancyrawls Mon, 11/10/2008 - 11:50

Finally! I think that did it. Now I will run the .bat file. I'll let you know how it goes.

Thanks.

Joe Clarke Mon, 11/10/2008 - 12:26

What output do you get for:

dmctl -s DFM getInstances Card_Fault_CiscoEntityFRU

nancyrawls Mon, 11/10/2008 - 12:29

We might be okay. The event just cleared when I ran the same command for the other card. Output:

I-Card_Fault_CiscoEntityFRU-CARD-123.133.187.1/1000

I-Card_Fault_CiscoEntityFRU-CARD-123.133.187.1/2000

I-Card_Fault_CiscoEntityFRU-CARD-123.133.187.1/3000

I-Card_Fault_CiscoEntityFRU-CARD-123.133.190.1/1000

I-Card_Fault_CiscoEntityFRU-CARD-123.133.190.1/2000

I-Card_Fault_CiscoEntityFRU-CARD-123.133.190.1/3000

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.145/22

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.145/23

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.145/24

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.145/25

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.145/25750

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.145/25751

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.145/26

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.145/28

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.145/29

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.145/35

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.145/36

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.146/22

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.146/23

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.146/24

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.146/25

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.146/26

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.146/28

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.146/29

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.146/35

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.146/36

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.147/22

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.147/23

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.147/24

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.147/25

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.147/25750

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.147/25751

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.147/26

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.147/28

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.147/29

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.147/35

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.147/36

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.148/22

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.148/23

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.148/24

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.148/25

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.148/25750

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.148/25751

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.148/26

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.148/28

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.148/29

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.148/35

I-Card_Fault_CiscoEntityFRU-CARD-123.133.5.148/36

I-Card_Fault_CiscoEntityFRU-CARD-123.170.0.5/2000

I-Card_Fault_CiscoEntityFRU-CARD-123.170.0.5/3000

I-Card_Fault_CiscoEntityFRU-CARD-123.170.0.5/4000

Correct Answer
Joe Clarke Mon, 11/10/2008 - 12:31

Yeah, it looks like those subclasses are now missing from the FRU list. You shouldn't see any more events for those components moving forward.

Actions

This Discussion