First, when i make a discovery with a seed device in Campus Manager, some devices are not discovered. If i look for seed device neighbors, i can see more devices that ones that are put into inventory, i mean, not all neighbors are discovered. The devices are reachable by ping. Why are not all devices discovered although ciscoworks detect them as neighbors???? There is no filter applied.
Second, my ciscoworks is very slow. The sm_server is using 80% of CPU load. What can i do??? i have read about it, but i cannot find a workaround.
The Device Discovery process will only move SNMP reachable devices into DCR for management by other applications. So, click on the number next to Device Discovery on the Campus Manager Homepage, and see what the status of the missing devices is. If the devices don't even show up there, check your discovery filters under Campus Manager > Admin > Device Discovery > Discovery Filters, and make sure hey are not being filtered out.
As for sm_server, this process is part of DFM. If it's taking 80% of the CPU it could be doing real work (i.e. polling devices for events, rediscovering devices, etc.) or there may be a problem. The first thing you should do is find out how many managed ports and interfaces are in DFM. To do that, run:
The total number of ports+interfaces cannot exceed 45,000. The total number of ports+interfaces instrumented for connectivity or performance cannot exceed 6,750. If you find that you have more objects in DFM than is supported, you will need to disable auto-manage mode under DFM > Device Management > Device Selector, then remove some devices from DFM.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...