0 Replies Latest reply on Sep 18, 2008 5:18 AM by gmc_za

    RSD2 and DHCP questions

      I have 2 DHCP servers on the same subnet serving clients IP addreses. I've load RSD2 with the dhcp tick box enabled on the 2 servers. When clients get a DHCP IP they can get it from either DHCP server. I've noticed that some IP do not get detected as rogue and I think it might be due to the following.

      From the logs it looks like you can only have one active rogue sensor per subnet, so one of the dhcp sensors is active and the other is passive - this might explain why only half the clients are detected. Is this how it works?

      From the logs on one of the DHCP servers:

      09-18-08 11:39:42,730 [34392] INFO RSDSensor.ServerCom <> - Server communication initialized to URL: https://10.1.6.83:8444/rsdsensor/engine.sm


      09-18-08 11:39:42,730 [34392] INFO RSDSensor <> - Created a virtual sensor for 10.4.13.0 on interface HP NC7771 Gigabit Server Adapter.


      09-18-08 11:39:42,730 [34268] INFO RSDSensor <> - Virtual sensor 34268 initialized at network address: 10.1.0.0 on interface 'HP NC3163 Fast Ethernet NIC'


      09-18-08 11:39:42,730 [1824] INFO RSDSensor <> - Virtual sensor 1824 initialized at network address: 10.4.13.0 on interface 'HP NC7771 Gigabit Server Adapter'


      09-18-08 11:39:42,746 [28968] INFO Pipe <> - Pipe communication started on thread 28968
      09-18-08 11:39:44,136 [34268] INFO RSDSensor.ServerCom <> - Sending data to the server at https://10.1.6.83:8444/rsdsensor/engine.sm


      09-18-08 11:39:44,136 [1824] INFO RSDSensor.ServerCom <> - Sending data to the server at https://10.1.6.83:8444/rsdsensor/engine.sm


      09-18-08 11:39:44,152 [34268] WARN RSDSensor <> - Failover notification for virtual sensor 34268 on network 10.1.0.0:

      The server has changed the failover status. Ceasing operation and going to sleep.


      Anyone got any idea if this is how its supposed to work?