02-08-2007 09:23 AM
i have problem to view link between 2 switch 3560 in topology services capus manager.it cannot display layer 2 view
02-08-2007 10:03 AM
What version of Campus Manager? Do the devices appear on the map as green with the correct switch icon?
When debugging topo problems with Campus, you should verify that CDP information is correct on the two devices. You can also enable core, corex, and topo debugging under Campus Manager > Admin > Campus Data Collection > Debugging Options, run a new Data Collection, and scan the ani.log for references to your devices.
02-12-2007 01:31 AM
my campus manager 's version is 4.0.3. Devices appear on the map as green but not with correct switch icon. CDP informations are correct and i enable core and corex but my problems persist
02-12-2007 03:39 AM
please help me all my devices are set in Unconnected Devices View.i cannot view link between device.
02-12-2007 05:08 AM
Green icon means SNMP connectivty is OK.
You verified CDP tables on the device and they seem OK.
A few things that I have seen that could block ciscoworks from discovering the topology are:
* Unique hostname for devices
* Defined view for SNMP limits to MIB2
All devices must have a unique hostname. If you have 5 devices called switch then ciscoworks campus cannot distinguish between them.
Ciscoworks needs more then MIB2, it also needs access to the private enterprise ciscomibs.
You may wish to publish here the logfiles of the discovery.
Cheers,
Michel
02-12-2007 06:32 AM
All devices have not the same hostname.each device has its own hostname.but i don't understand :access to the private entreprise
ciscomibs.the file Discovery.log content:2007/02/12 14:05:25 main MESSAGE DiscoveryMain: Properties will be read from C:\PROGRA~1\CSCOpx\campus\etc\cwsi\DiscoveryStatus.properties
2007/02/12 14:05:28 main MESSAGE DBConnection: Created new Database connection [hashCode = 2549855]
Common trust user is: admin
User name in Security context is: admin
log4j:ERROR No appenders could be found for category (CTM.common).
log4j:ERROR Please initialize the log4j system properly.
2007/02/12 14:05:32 main MESSAGE DCRDevWrapper: Fetching DCRDeviceIDs
2007/02/12 14:05:50 main MESSAGE DCRDevWrapper: Finished fetching DCRDeviceIDs
2007/02/12 14:05:50 main MESSAGE DCRDevWrapper: Fetching DCRDevices
2007/02/12 14:05:50 main MESSAGE DCRDevWrapper: Finished fetching DCRDevices
com.cisco.nm.lib.snmp.futureapi.SnmpReqTimeoutException: SnmpRequestTimeout on 10.1.2.240 while performing SnmpGet at index = -1
at com.cisco.nm.lib.snmp.futureapi.SnmpFuture.value(SnmpFuture.java:175)
at com.cisco.nm.ani.server.devdiscovery.DevdiscoverySMFConfigSnmpParam.isDCRCredValid(DevdiscoverySMFConfigSnmpParam.java:131)
at com.cisco.nm.ani.server.devdiscovery.DevdiscoverySMFConfigSnmpParam.processForVersion2(DevdiscoverySMFConfigSnmpParam.java:104)
at com.cisco.nm.ani.server.devdiscovery.DevdiscoverySMFConfigSnmpParam.apply(DevdiscoverySMFConfigSnmpParam.java:59)
at com.cisco.nm.ani.server.framework.EvalSMFApply.apply(EvalSMFApply.java:101)
at com.cisco.nm.ani.server.frontend.EvalPair.apply(EvalPair.java:107)
at com.cisco.nm.ani.server.frontend.EvalTask.run(EvalTask.java:45)
at java.lang.Thread.run(Thread.java:479)
02-12-2007 10:37 PM
Access to the private entreprise mibs is given when you enable SNMP access unless a view is defined like here below.
snmp-server community public view restict RO
snmp-server view restict mib-2 included
Because now you can only read MIB2 and not the cdp table so Campus can't make out the topology.
if you add
snmp-server view myview cisco included
it should work again.
Anyway I think you should try to do an snmp walk on one of the switches where you have a problem.
Open the device center for the IP of the switch. Under Tools there is snmpwalk.
See if you can get the CDP table.
Cheers,
Michel
02-12-2007 06:34 AM
(suite)com.cisco.nm.lib.snmp.futureapi.SnmpReqTimeoutException: SnmpRequestTimeout on 192.168.170.22 while performing SnmpGet at index = -1
at com.cisco.nm.lib.snmp.futureapi.SnmpFuture.value(SnmpFuture.java:175)
at com.cisco.nm.ani.server.devdiscovery.DevdiscoverySMFConfigSnmpParam.isDCRCredValid(DevdiscoverySMFConfigSnmpParam.java:131)
at com.cisco.nm.ani.server.devdiscovery.DevdiscoverySMFConfigSnmpParam.processForVersion2(DevdiscoverySMFConfigSnmpParam.java:104)
at com.cisco.nm.ani.server.devdiscovery.DevdiscoverySMFConfigSnmpParam.apply(DevdiscoverySMFConfigSnmpParam.java:59)
at com.cisco.nm.ani.server.framework.EvalSMFApply.apply(EvalSMFApply.java:101)
at com.cisco.nm.ani.server.frontend.EvalPair.apply(EvalPair.java:107)
at com.cisco.nm.ani.server.frontend.EvalTask.run(EvalTask.java:45)
at java.lang.Thread.run(Thread.java:479)
2007/02/12 14:06:09 EvalTask-Devdiscovery-01 WARNING DevdiscoverySMFGetDeviceType: SNMP unreachable device at: 192.168.14.1 will not remap SMFFactory
com.cisco.nm.lib.snmp.futureapi.SnmpReqTimeoutException: SnmpRequestTimeout on 192.168.254.7 while performing SnmpGet at index = -1
at com.cisco.nm.lib.snmp.futureapi.SnmpFuture.value(SnmpFuture.java:175)
at com.cisco.nm.ani.server.devdiscovery.DevdiscoverySMFConfigSnmpParam.isDCRCredValid(DevdiscoverySMFConfigSnmpParam.java:131)
at com.cisco.nm.ani.server.devdiscovery.DevdiscoverySMFConfigSnmpParam.processForVersion2(DevdiscoverySMFConfigSnmpParam.java:104)
at com.cisco.nm.ani.server.devdiscovery.DevdiscoverySMFConfigSnmpParam.apply(DevdiscoverySMFConfigSnmpParam.java:59)
at com.cisco.nm.ani.server.framework.EvalSMFApply.apply(EvalSMFApply.java:101)
at com.cisco.nm.ani.server.frontend.EvalPair.apply(EvalPair.java:107)
at com.cisco.nm.ani.server.frontend.EvalTask.run(EvalTask.java:45)
at java.lang.Thread.run(Thread.java:479)
2007/02/12 14:06:19 EvalTask-Devdiscovery-14 WARNING DevdiscoverySMFGetDeviceType: SNMP unreachable device at: 192.168.210.100 will not remap SMFFactory
2007/02/12 14:06:26 EvalTask-Devdiscovery-12 WARNING DevdiscoverySMFGetDeviceType: SNMP unreachable device at: 10.1.2.240 will not remap SMFFactory
2007/02/12 14:06:27 EvalTask-Devdiscovery-10 WARNING DevdiscoverySMFGetDeviceType: SNMP unreachable device at: 192.168.254.7 will not remap SMFFactory
2007/02/12 14:06:27 EvalTask-Devdiscovery-09 WARNING DevdiscoverySMFGetDeviceType: SNMP unreachable device at: 192.168.170.22 will not remap SMFFactory
2007/02/12 14:06:30 EvalTask-Devdiscovery-11 WARNING DevdiscoverySMFGetDeviceType: SNMP unreachable device at: 192.168.124.1 will not remap SMFFactory
2007/02/12 14:06:30 EvalTask-Devdiscovery-16 WARNING DevdiscoverySMFGetDeviceType: SNMP unreachable device at: 10.1.2.181 will not remap SMFFactory
2007/02/12 14:06:31 main MESSAGE DiscoveryMain: Properties will be read from C:\PROGRA~1\CSCOpx\campus\etc\cwsi\DiscoveryStatus.properties
2007/02/12 14:06:31 main MESSAGE DiscoveryMain: Properties will be read from C:\PROGRA~1\CSCOpx\campus\etc\cwsi\DiscoveryStatus.properties
2007/02/12 14:06:31 main MESSAGE DCRDevWrapper: Closing DCRProxy
02-12-2007 09:40 AM
This appears to be from the discovery.log. When I asked you to enable core and corex debugging, you need to look through the ani.log for the devices in question. Any errors there may explain why a link is missing.
That said, there does appear to be quite a few devices that are not SNMP-reachable in your network. You may want to verify your SNMP credentials are correct in DCR and in the Campus Manager > Admin > Device Discovery > SNMP Settings page.
02-12-2007 10:19 AM
I have the same problem with CM 3.3. Catalyst 2960 appear green on the map, but with a incorrect icon. It seems to be a version problem, CM 3.3 don' t recognize new catalyst models
02-12-2007 10:57 AM
No, Campus Manager 3.3 does not support nor will support the Cat2960 series switches.
02-13-2007 01:13 AM
I use switch Catalyst Express 500 and they is not thus finds in the MDF database.I chose Unknown device you think that it is that the problems. In my ani.log file i found:
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: Cannot map portIfIndex 10101 of device 192.168.254.4
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: 192.168.254.4 is an unknown device
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: Cannot map portIfIndex 10102 of device 192.168.254.4
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: 192.168.254.4 is an unknown device
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: Cannot map portIfIndex 10119 of device 192.168.254.1
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: 192.168.254.1 is an unknown device
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: Cannot map portIfIndex 10120 of device 192.168.254.1
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: 192.168.254.1 is an unknown device
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: Cannot map portIfIndex 10123 of device 192.168.254.1
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: 192.168.254.1 is an unknown device
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: Cannot map portIfIndex 10124 of device 192.168.254.1
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: 192.168.254.1 is an unknown device
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: Cannot map portIfIndex 10125 of device 192.168.254.1
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: 192.168.254.1 is an unknown device
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: Cannot map portIfIndex 10127 of device 192.168.254.1
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: 192.168.254.1 is an unknown device
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: Cannot map portIfIndex 10101 of device 192.168.254.3
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: 192.168.254.3 is an unknown device
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: Cannot map portIfIndex 10101 of device 192.168.254.9
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: 192.168.254.9 is an unknown device
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: Cannot map portIfIndex 10102 of device 192.168.254.9
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: 192.168.254.9 is an unknown device
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: Cannot map portIfIndex 10101 of device 192.168.254.11
2007/02/13 00:00:51 Discovery ani WARNING TopoSMFGenerateCdpTopology: 192.168.254.11 is an unknown device
02-13-2007 05:07 AM
Supported Devices Table for Campus Manager 4.0.3 (With LMS 2.5.1)
Cheers,
Michel
02-13-2007 07:02 AM
I check for Devices Table for Campus Manager 4.0.3 but it don't have there a Catalyst Express 500.what must I make now ? I have already the product LMS.
02-13-2007 10:59 AM
The Catalyst Express 500 is not currently slated to be supported by LMS. It is managed by Cisco Network Assistant instead. CNA is freely downloadable from Cisco.com from the switch software page at http://tools.cisco.com/support/downloads/go/MDFTree.x?butype=switches .
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide