Spectrum rediscover device does not work for Chassis Manager by design?

[Joern Henrichs]

Hello dear Community!

Is anybody of you aware, that the rediscover device action does not affect whatever or not a device is included in Chassis Manager?
I have a database from a banking customer, grown over the years, which has been upgrades multiple times.
We wondered why some (Cisco) devices showed up in Chassis Manager and some not, while all had the EntityMIBApp which is the determining criteria according to the Documentation. We tried rediscovering a couple of times, but finally we opened an support ticket. Support/Engineeering told us that this is by design and we have to remodel all devices which are not in the Chassis Manager.
We have 272 Cisco Devices in the database (all of them with the EntityMIBApp model) and only 32 show up in the Chassis Manager - means effectively we have to remodel the whole database.
Has/had anyone else this problem and how do/did you deal with it?
Could PM please comment on this?

On the other hand - is there an manual solution (preferable somthing easy to automate - like creating associations in the SSdb) to solve this? 

Cheers,
Joern

------------------------------
Senior System Engineer
Computacenter AG & Co. oHG
Berlin
------------------------------

[Mukunda Naresh]

Hello Joern, 

Populating Chassis Module and adding/removing to/from Chassis Manager depends upon the EnableEntityModuleModeling ( 0x12e5f ) attribute value to "Yes" Or "No" and also reconfigure model action.

• If you do not want DX NetOps Spectrum to identify a device model as a chassis device, set the value of this attribute to "No" and reconfigure the model will remove the Chassis Module from Chassis Manager.

Reconfigure model action should add the Device Chassis modules under Chassis Manager after enabling the EnableEntityModuleModeling ( 0x12e5f ) attribute value to "Yes". 

As you mentioned some devices not populating Chassis modules, So kindly request you to verify below attributes on the problematic devices where chassis modules not displayed under Chassis Manager and see whether ChassisMgr (0x12e4f) attribute value must be equal to the Device EntityMIBApp model handle or not.[Verify ChassisMgr (0x12e4f) attribute value points to correct EntityMIBApp model handle using the Locator search -> All Application Models -> search for device EntityMIBApp application -> Attributes Tab -> Model Handle value ]                                                                                         .

In case ChassisMgr (0x12e4f) attribute value points other than the model handle of EntityMIBApp then there may be chance of corruption of device models in database. In this case, you need to remodel those devices to avoid this problem. You can cross verify by coping the ChassisMgr (0x12e4f) attribute value into the Locator search -> Models -> By Model Handle and see it points to which application model handle.   


Attribute Name                          AttrID                Value

EnableEntityModuleModeling  ( 0x12e5f )            Yes
ChassisMgr                                (0x12e4f)         < EntityMIBApp model handle > ( Go to Locator search -> All Application Models -> search for device                                                                                          EntityMIBApp application )  

Regards

Mukund

[Joern Henrichs]

Hi Mukund,

I am reliefed that you confirmed that reconfigure model is indeed supposed to get a model into Chassis Manager if there is a EntityMibApp and the funktion is enabled.
You are right with your assumption, that the ChassisMgr Attribute does not point to the EntityMibApp model. Instead it points to a CATStackApp model.

As ChassisMgr is a read-only attribute, we don't have a chance to fix this ourself (other then remodel).
However, we noticed on an other landscape we had models where the ChassisMgr attribute was 0x0 and a rediscover model wrote the correct model handle into the attribute.
Shouldn't this also work if the attribute points to an wrong model?

Cheers,
Joern

------------------------------
Senior System Engineer
Computacenter AG & Co. oHG
Berlin
------------------------------

[Mukunda Naresh]

Hi Joern, 

If ChassisMgr attribute points to empty ( 0x0/NULL ) which means during discovery or reconfigure model time EntityMibApp model handle will be assigned to it. Once model handle value is present for ChassisMgr attribute then the same value will be used for finding the Chassis device and adding them to Chassis Manager.

If ChassisMgr attribute value points to wrong model handle then it won't initiate a request for finding the Chassis device.

Regards
Mukund

[Joern Henrichs]

Hi Mukund,

 

I understand that this is the way it works currently.

But if the ChassisMgr attribute is pointing to a wrong model Spectrum does not add the device to the Chassis Manager.

So Spectrum detects, that the attribute is not populated correctly. What is missing at this point is to reset the attribute to 0x0 (and go back to the point where discovery is filling the attribute).

The functionality is there – it is just not used, which creates problem for customer like me where something went wrong in the past.

 

Cheers,

Joern

 

Joern Henrichs

Senior System Engineer, Digital Infrastructure

Digital Operations & Service Centers

 

Mariendorfer Damm 1, 12099 Berlin, Germany

Computacenter AG & Co. oHG

T: [phone]

E: [e-mail]

www.computacenter.com | LinkedIn | Xing | YouTube | Twitter

 

<mc type="body">

-----------------------------------
Computacenter AG & Co. oHG, mit Sitz in Kerpen
(Amtsgericht Köln HRA 18096)
Vertretungsberechtigte Gesellschafter:
Computacenter Aktiengesellschaft, mit Sitz in Köln (Amtsgericht Köln HRB 28384)
Vorstand: Tony Conophy
Aufsichtsrat: Michael Norris (Vorsitzender)
Computacenter Management GmbH, mit Sitz in Köln (Amtsgericht Köln HRB 28284)
Geschäftsführer: Dr. Karsten Freihube, Reiner Louis, Karl-Heinz Reitz

This email is confidential. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this mail in error, please tell us immediately by return email and delete the document.
 Datenschutzerklärung
-----------------------------------

</mc>

[Mukunda Naresh]

Hi Joern,

It looks like, manually EntityMIBApp applications might have been deleted for the devices due to which ChassisMgr attribute points to wrong model handle. There is NO manual way for resetting the ChassisMgr attribute to zero(0) since its read-only attribute and not at all a **** task. We already suggested you to remodel the problematic devices to avoid this issue/problem. Since you mentioned that major devices had this problem and remodel will create historical data lost.

I'm going to see If there is a feasibility for repairing or resetting that attribute in the SSdb file through SpectroSERVER debugging. 

I would request you to contact the Broadcom support team and open a new case for repairing the SSdb file and also attach the latest SSdb file to it for troubleshoot/analysis purpose.  Once the new case is created and assigned to me then I will start my analysis and update the case with my findings.

Note: Kindly request you to not to delete any spectrum application models manually. Whenever device model is deleted spectrum automatically deletes device corresponding application models. In case if you need some help then contact the Broadcom support team to assist you further. 

Regards

Mukund

[Joseph Ackley]

What happens if you right mouse click on the device model and select Reconfiguration -> Rediscovery SNMP MIBS?

Joe

[Joern Henrichs]

Hi Joe!

 

Thanks for your suggestion! Unfortunately nothing happens, as the models already have a EntityMibApp. only the ChassisMgr attribute points to the wrong model.

On the other hand – isn't "Rediscover SNMP MIBs" part of "Reconfigure model"?

 

Cheers,

Joern

 

Joern Henrichs

Senior System Engineer, Digital Infrastructure

Digital Operations & Service Centers

 

Mariendorfer Damm 1, 12099 Berlin, Germany

Computacenter AG & Co. oHG

T: [phone]

E: [e-mail]

www.computacenter.com | LinkedIn | Xing | YouTube | Twitter

 

<mc type="body">

-----------------------------------
Computacenter AG & Co. oHG, mit Sitz in Kerpen
(Amtsgericht Köln HRA 18096)
Vertretungsberechtigte Gesellschafter:
Computacenter Aktiengesellschaft, mit Sitz in Köln (Amtsgericht Köln HRB 28384)
Vorstand: Tony Conophy
Aufsichtsrat: Michael Norris (Vorsitzender)
Computacenter Management GmbH, mit Sitz in Köln (Amtsgericht Köln HRB 28284)
Geschäftsführer: Dr. Karsten Freihube, Reiner Louis, Karl-Heinz Reitz

This email is confidential. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this mail in error, please tell us immediately by return email and delete the document.
 Datenschutzerklärung
-----------------------------------

</mc>

[Joern Henrichs]

Hi Mukund,

 

I know there is no manual way for me to reset the attribute, as it is read only – otherwise I just would have done it and not bothered you and support with this.

While I am really thankful that you are going to look into fixing our database – I still think the product would be better if it fixes issues like that and it would require only minor changes, as all the functionality is already there. But of course I am saying that from a customer perspective.

 

Cheers!

Joern

 

Joern Henrichs

Senior System Engineer, Digital Infrastructure

Digital Operations & Service Centers

 

Mariendorfer Damm 1, 12099 Berlin, Germany

Computacenter AG & Co. oHG

T: [phone]

E: [e-mail]

www.computacenter.com | LinkedIn | Xing | YouTube | Twitter

 

<mc type="body">

-----------------------------------
Computacenter AG & Co. oHG, mit Sitz in Kerpen
(Amtsgericht Köln HRA 18096)
Vertretungsberechtigte Gesellschafter:
Computacenter Aktiengesellschaft, mit Sitz in Köln (Amtsgericht Köln HRB 28384)
Vorstand: Tony Conophy
Aufsichtsrat: Michael Norris (Vorsitzender)
Computacenter Management GmbH, mit Sitz in Köln (Amtsgericht Köln HRB 28284)
Geschäftsführer: Dr. Karsten Freihube, Reiner Louis, Karl-Heinz Reitz

This email is confidential. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this mail in error, please tell us immediately by return email and delete the document.
 Datenschutzerklärung
-----------------------------------

</mc>