IMC 5.1 (E0202) : adding vlan devices list empty

[karon69]

Hi!
i've recently installed IMC 5.1 (E0202) solution on a RedHat server.
i added all my Nortel/Avaya switches but i can't select any switch for adding vlan,
the devices list is completely empty.
can anyone help me ?
thanks.

[LindsayHill]

If it's a new install, why did you choose 5.1? You should install 7.0 E0202.

That said, I'm not sure that Avaya is supported for VLAN management.

[karon69]

thank you for your reply. we bought imc a year ago. i'll try with this version

if it's ok, can we use our 5.1 license key with this new one ?

[LindsayHill]

Yes, you can use the same licenses. 

You will need to upgrade to 5.2 first, then go to 7.0.

It sounds like you haven't really used it, or done much configuration though - so it might be easier to just do a clean installation of 7.0 E0202.

[karon69]

yes effectivively i prefer to make a clean installation.
i hope that our switches will be supported for vlan management.

thank you!

[karon69]

i've installed imc 7 and our avaya switches are not recognized in the devices list for vlan management :(

[LindsayHill · Accepted solution]

Log a support case, ask them to confirm the level of support for Avaya, and ask them to add support for it in a future version. (No guarantees, but if you don't ask, you'll never get)

[karon69]

i thought about that, but didn't know if it was possible. i'll try it. thanks for your support.

[lionel-ditparis]

hi, i have the same problem, i can't backup my nortel switch, my snmp are goods but nothing.

see picture 1

with any HP products i can backup the config easyly.

see picture 2.

any idea ?

[LindsayHill]

Do you have the right Telnet credentials set?

What does the imccfgbakdm log file say?

From a quick look, that sysOID matches the NortelERS adapter, which supports TFTP + CLI backup of the startup config.

Don't worry about that other bit you've shown on the screenshot with Trap Destinations.

[lionel-ditparis]

Back up configuration files. Total: 0, startup files: 0, running files: 0.     TEST ISC(10.10.44.169) Nortel ERS2526T Startup 2014-08-21 09:38:30 Failed to telnet the device. -- TEST ISC(10.10.44.169) Nortel ERS2526T Running 2014-08-21 09:38:30 Adapter does not support. --       2014-08-21 09:38:12 Starting to backup configuration files.  

cli password and telnet password are the same, i can manage this device by telnet.

[LindsayHill]

Which IMC version do you have?

What file transfer mode do you have for that device?

In IMC, at the same place as where you configure the Telnet credentials for the device, there's a Test button - can you try running that? Does it succeed?

[lionel-ditparis]

hi, here is the log file.

thanks for your time.

[lionel-ditparis]

iMC PLAT 7.0 (E0202P03)

tftp works via telnet commands, see picture.

[lionel-ditparis]

i tried all authentification mode and not one succed.

my hp devices are by SSH so i never tried telnet. but i think nortel devices only accept telnet connection.

[LindsayHill]

The problematic line is here:
2014-08-21 09:38:26.717 [ERROR (1)] [THREAD(5484)] [CTclExecutor::exec_impl()] Failed to exec cmd: C:/Program Files/iMC/server/bin/../../server/conf/adapters/ICC/Nortel networks/NortelERS/initialize.tcl, error message: C:/Program Files/iMC/server/bin/../../server/conf/adapters/ICC/Nortel networks/NortelERS/initialize.tcl(12): error: wrong # args: should be "set varName ?newValue?"

Looking at initialize.tcl, it contains these lines:
set username_prompt Enter Username:
set password_prompt Enter Password:

That should be something like

set username_prompt "Enter Username:"

- so that the variable is one parameter.

You could fix it yourself, or you could use the copy from here: https://github.com/NetOpsCommunity/imc-netops/tree/master/adapters/ICC/Nortel%20networks/NortelERS

That directory includes an updated adapter for handling some of the Avaya-branded gear.

[lionel-ditparis]

ok i am going to copy this files and restart imc to take effect

[LindsayHill]

Let us know how you get on. You don't need to restart IMC if you're changing a TCL file, as they always get re-read. You do need to re-start IMC if you're changing the XML files though.

[lionel-ditparis]

same problèm:

2014-08-21 10:56:16 Back up configuration files. Total: 0, startup files: 0, running files: 0.     TEST ISC(10.10.44.169) Nortel ERS2526T Startup 2014-08-21 10:56:15 The device does not support the features. -- TEST ISC(10.10.44.169) Nortel ERS2526T Running 2014-08-21 10:56:15 The device does not support the features. --       2014-08-21 10:56:07

Starting to backup configuration files.

2014-08-21 10:56:14.149 [WARNING (2023)] [THREAD(932)] [CScriptTool::getDevAdapterNameFromDB()] reader no data, sql: select vendor_name,adapter_name from tbl_dev_adapter where component_name = 'ICC' and dev_id = 1737 and adapter_type = 1
2014-08-21 10:56:14.150 [INFO (0)] [THREAD(932)] [CComponentAdapter::parseVendorAdapter()] Begin to parse ...
2014-08-21 10:56:14.151 [INFO (0)] [THREAD(932)] [CComponentAdapter::parseVendorAdapter()] Finished to parse!
2014-08-21 10:56:14.152 [WARNING (2001)] [THREAD(932)] [CComponentAdapter::getSupportAdapter()] Device Vrp can not match,devID=1737,devSeries=N/A,devVRPVer=N/A,devReleaseNo=N/A,devCategoryID=1
2014-08-21 10:56:14.152 [WARNING (1)] [THREAD(932)] [CComponentAdapter::discoverDeviceAdapter()] fail to call getSupportAdapter(),devID=1737
2014-08-21 10:56:14.183 [WARNING (2023)] [THREAD(932)] [CScriptTool::getDevAdapterNameFromDB()] reader no data, sql: select vendor_name,adapter_name from tbl_dev_adapter where component_name = 'ICC' and dev_id = 1737 and adapter_type = 0
2014-08-21 10:56:14.183 [INFO (0)] [THREAD(932)] [CComponentAdapter::parseVendorAdapter()] Begin to parse ...
2014-08-21 10:56:14.184 [INFO (0)] [THREAD(932)] [CComponentAdapter::parseVendorAdapter()] Finished to parse!
2014-08-21 10:56:14.184 [WARNING (2001)] [THREAD(932)] [CComponentAdapter::getSupportAdapter()] Device Vrp can not match,devID=1737,devSeries=N/A,devVRPVer=N/A,devReleaseNo=N/A,devCategoryID=1
2014-08-21 10:56:14.184 [WARNING (1)] [THREAD(932)] [CComponentAdapter::discoverDeviceAdapter()] fail to call getSupportAdapter(),devID=1737

[LindsayHill]

Can you synchronise the device, then run a backup again, and post a copy of the imccfgbakdm log file.

[lionel-ditparis]

here it is, same problem

[LindsayHill]

From a quick look, it's not the same problem. You're not seeing the same errors in your log files. It seems like it's missing some data in the logs as to what's actually going on - sometimes different processes update the file at different times, and the logs get out of sync (e.g. you can see this where the log entries go from 10:12:52.643 to 10:12:49.919).

Do you have any more updates to this log file?

And you said you tried different authentication methods - did you set it back to the original method?

[lionel-ditparis]

no more updates for this log file.

yes i set it back to the original method and the test is KO.

when i say same problem, i mean that the backup don't work :)

[lionel-ditparis]

when i do the test from the right panel "Action"  =>  "Telnet SSH /Proxy"  i have a new window who tries to connect in command line but stays waiting the "Ctrl-Y" command to have acces to the login et password screen.

maybe that's the problem...

[LindsayHill]

The Ctrl+Y stuff can cause some problems. Part of the changes in those updated adapter files I posted on Github are related to trying to work around it. I cannot understand why a company continues to require something as daft as Ctrl+Y, but that's another story.

But your most recent logs didn't show any attempt to actually try and connect to the device. You could probably check that with Wireshark. This could be because there's some issue with the modified adapter files, or because something else is going on (e.g. those changes cause issues with the other files, and now IMC doesn't think there is any valid adapter.

My next step would probably be to remove/re-add the device from IMC, as it does sometimes seem to have issues with caching invalid adapter information.

I'm certain that this can be made to work - there is nothing fundamentally unusual about what you're trying to do. But I'm reaching the limits of what I can do via a message board, and really need access to the system. You should be engaging a consultant, and/or HP Support. ( I don't know whether support can help or not, as I don't know what the official support status of that Nortel device is).