Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi, we run Cisco Works LMS Suite 5th Edition and manage about 190 devices on an solaris8 based installation. On this plattform runs CS2.2, CM3.3, RME3.5, DFM1.2 and CV5.5.We enlarged our network infrastructure with an additional network segment (ospf...
Hi,we run Cisco Works LMS Suite and manage about 190 devices on an solaris based installation. In indefinable steps, the topology view indicates unreachable devices in red color, but the devices are working proberly. Sometimes it falsely shows one de...
Hi,we run Cisco Works LMS Suite and manage about 190 devices on an solaris based installation. In indefinable steps, the topology view indicates unreachable devices in red color, but the devices are working proberly. Sometimes it falsely shows one de...
I have installed CiscoWorks, 5th Edition on a brandnew Solaris8+Patchcluster 04/01.With some windows clients i got access via http on port 1741. So far, so good. But when i try to access to some links, for example, "ServerConfiguration-Setup-Security...
Hey,has anybody experience in configuring and visualizing traps with DFM 1.2 ?Since some days i try to configure dfm 1.2 for receiving and visualizing traps that were sent from a catalyst 3548. The catalyst sends trap, such as traps when i do "sh run...
You are right! A falsely modified httpd.conf was the case of the bug.My first thought was, that the installation of DFM1.2 is the case, but only when i installed FH1.1 on the machine, the topolgy groups feature strikes. The installation of FH1.1 modi...
I had the same problem. When i tried to open the configuration dialog for creating topology groups, the page was unavailable.I located the problem at the Device Fault Manager module.When Device Fault Manager module and Campus Manager module is instal...
I have added the community strings of area 1 to the configuration of the ABR. Now, the ABR is configured with two different community strings, one of area 0 and one of area 1.-> ANI server have discovered the devices in area 1.But why ??
The values for all SNMP communities are set to 59 sec. timeout and max. 5 times of retry.Are there any other values that stand in relation to CM3.3? How does the CM3.3 discover the state of a device?
