I built my CW2000 system on a dual-homed server, I intended it to be dual homed temporarily, one interface is on a management DMZ the other is on an Internal network.
CW2000 has took the internal network IP address as it's primary address, this is causing problems for example, syslogs received by devices on the DMZ interface are forwarded to the primary internal interface, and so they appear to have come from the source address of the DMZ interface and not the actual device creating the syslog.
Is there anyway of changing the primary interface CW2000 uses on a dual homed server?? Or do I need to remove the temporary interface and do a re-install?
Secondly, after upgrading to IE6 SP1 I can no longer connect to CW2000, is there an issue with this version of IE??
Check to see if one of the interfaces is built-in. if it is, you need to assign that one the address you want. It seems that by default, CW takes the built in address as the primary interface. Any slot based card is made the secondary.
You also must modify your gatekeeper file located in NMSRoot\lib\vbroker\gatekeeper.cfg
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...