The event viewer can not communicate to either of my sensors, although the post office port s are the same. The sensors are still talking to the director on that same port..do I .change the post office port for the event viewer and sensors? I get the sync sent but no reply from the sensors.
Here's what I have found out. First thing was I hadn't applied my changes when configuring the sensors thru the manager. Once I did that I saw the Event Viewer machine. Happens to be my workstation. The snoop on the sensors show my machine sending the request on port 45000 and the sensor sending it back out to the director instead of my machine. How do I configure the sensors to send to 2 hosts?
Instructions are after: "To configure remote hosts to receive alarms, follow these steps"
If you are configuring through the Unix Director and not IDM then you will need to add the information for your workstation to the Hosts, Organizations, Routes, and Destinations configurations in the System Files configuration for your sensor.
You will want to add your IEV machine using the above instructions.
If your workstation is using DHCP then you will need to update this every time your workstation ip address changes.
If you are no longer using the Unix Director you can remove the entries for Unix Director.
I have added the new IEV machine using the IDM. Removed the old Unix director from that sensor. I can see when I do the snoop -d command on the sensor, traffic from my machine and from the sensor, but in the event viewer, when I look at the device status it still states no sync recvd. I even added a static route on my machine to that sensor. All the services are running and I've rebooted the sensor twice. I can ping the workstation from the sensor.
Replace ievhostid, and ievorgid with the numerical values for the IEV machine
Execute this from within the bin directory for IEV.
Is there a firewall or router between the IEV and your sensor? If so you may need to sniff the network between your firewall/router and IEV to ensure that the firewall/router is letting the UDP port 45000 traffic from the sensor reach your IEV machine.
IT could be that the firewall lets the packets from IEV reach the sensor, but may not be letting the packets from the sensor reach the IEV machine.
The sensors iprb0 interface set on the same network as my workstation...
There addresses are 172.25.0.xxx, the workstation is 172.25.4.xxx. No router or firewall in the way, although the default gateway for both is the firewall. I can ping and tracert to each sensor and visa versa. I will try and get you those output files. The command on the IEV machine resulted in a timeout.
I can see when I snoop the interface...sensor192---> 172.25.4.xxx 45000 udp etc
Then directly after that line ..172.25.4.xxx ---> sensor192 45000 udp etc.
Seems like the sensor is seeing a syn and responding, but I don't think my machine is reading it, or the port is opening correctly.
BenefitsDocumentationPrerequisiteImage Download LinksLimitationsSupported PlatformsLicense RequirementsTopologyStep-By-Step ConfigurationConfigure Virtual ServiceActivate the virtual service and configure guest IPsConfiguring UTD (Service Plane)Configurin...
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...