Optivity Hell!

[jjling]

I am using Optivity NMS 9.1 (for windows)

We have a network with 6600 and 4400 Passports ,Accelars, Baystack LAN switches and 3 Com Hubs

I can ping everything from the Optivity Machine.

Ok .... I do not have the Preside MDM (Multiservice Data Manager ) needed to monitor and control the passports.

Does this mean that i cannot view any details whatsoever about my equipment using Optivity alone?

i can't even view the accelars and hubs using Autotopology.

Please help!

Jesse Ling
Network Design and Engineering
Information Technology and Telecommunications
Petrotrin
Trinidad
West Indies

 

[sysmanrick]

Hi:
Have you checked your SNMP community strings in Optivity and on the switches?
Make sure you have the current OIT modules integrated in 9.1 Optivity.
Have you tried Optivity Switch Manager to view your switches?

Try jdm(java device manager for switches) available on Nortel web site.

 

[jjling]

It is still not working....

89.85.70.18 -- i used as the seed (a xyplex router)

Subnet range 89.85.70.0 to 89.85.70.255

89.85.84.93 is the firewall...
i dont even know why it is going there

Any help please

This what i keep getting in autotopology

Initializing...
Auto Topology Daemon is running
Checking Database for Discovery Seeds
Create/Modify Discovery Seeds to begin Discovery
Use Seed Specification Dialog to create Seed
Click Start Discovery button/menu to start
Seed "PAP" modified by user "Administrator"
Processing Start Discovery request
Discovery started by user "Administrator"
Launching C:\Optivity\NMS\bin\toprt.exe
Initiate Router Discovery.. [1]
Start router 89.85.70.18 Fri Jan 11 12:50:08 2002
Timeout (snmp) 89.85.84.93 Fri Jan 11 12:50:28 2002
**************************
Router Discovery Completed
**************************
Got Subnet Topology trigger
Querying Optivity DB for new subnets..
None found, Subnet Discovery will NOT start
Querying Optivity DB for new devices..
None found, EndNode Discovery will NOT start
Topology End Notification is sent.

Jesse

 

[sysmanrick]

The error message appears to relate to SNMP community strings on your seed router.The Administrator login is not one I would I would use.Create a "ADMIN" user;ensure the user is set up in the Optivity Access table.Verify the SNMP community string on Optivity and the routers you are attempting to discover.
According to the error log message no router was "Seen" to be discovered.