Device discovery failed in ANM

Answered Question
Dec 17th, 2009

Hi,


I've got the following error message when I want to import a 6506 in 12.2(33)SXI2 with an ACE module.

I've tried in ANM 2.2 and 3.0 = same problem.


Can someone help me ?


Device discovery failed: Exception occured for model:VlanModel
Exception occured for model:InterfaceModel
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort
com.cisco.nm.dice.pkgs.features.interfaces.dm.L2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort.


Thanks,


Greg.

Correct Answer by jlamousn about 7 years 2 months ago

The other error is the following defect


CSCte08994   Unable to import IOS device with "type tunnel" interface configured.



Joel Lamousnery



/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;}

Customer Support Engineer

Data Center - Application Networking Services

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
sujathab Fri, 12/18/2009 - 10:36

Hi Greg,


The error message you are seeing is likely triggered by some un-expected configuration on the cat6k.


It is likely your cat6k configuration has an interface defined as a switchport which has a subinterface  defined on it.
This is usually not allowed on most sup versions that we  have seen and hence is not modeled/ cannot be discovered in  ANM.

We have bug id CSCtd94658 opened for this issue.

You  could try to have your customer remove the subinterface indicated above and then  try the import into ANM.
Also,  they could maybe add back that interface if really required after the initial  import.
Since  Cat6k configs are not auto-sync'ed in ANM, they will be okay until they do a  manual sync.
This workaround in also documented in the release notes of CSCtd94658.

Thanks
Sujatha
========
aniortegr Mon, 12/21/2009 - 11:03

Hi,


Thanks for the answer.

I found it with the help of the TAC.


Now it is corrected but I've got another issue.


Device discovery failed: Exception occured for model:VlanModel

Exception occured for model:InterfaceModel

java.lang.NullPointerException

java.lang.NullPointerException

java.lang.NullPointerException.

do you have any idea ?

Thanks.

Correct Answer
jlamousn Mon, 12/28/2009 - 07:12

The other error is the following defect


CSCte08994   Unable to import IOS device with "type tunnel" interface configured.



Joel Lamousnery



/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin;}

Customer Support Engineer

Data Center - Application Networking Services

Actions

This Discussion