To manage Network Injectors: |
|
When the RCS is running, this function lets you create monitoring and injection rules and send them to the Network Injector.
During installation, this function lets you create a new Network Injector "object" that creates the logical connection between the RCS Console and single hardware device.
With this function you can:
NOTE: an agent need not be installed to create an injection rule.
For interface element descriptions See "Shared interface elements and actions".
For a description of injection rule data see "Injection rule data".
For further information on injection rules see "What you should know about Network Injector and its rules".
To learn more about Network Injector Appliance installation see "Network Injector Appliance installation"
To learn more about Tactical Network Injector installation see "Tactical Control Center installation"see "Network Injector Appliance installation"
Selected Network Injector data is described below:
Data | Description |
---|---|
Name Description |
User's descriptions. |
Version |
Software version. To view the software versions of all the components see "System monitoring (Monitor)". |
Address |
Device IP address. |
Port |
4444. 4444. To view all ports to be opened on the firewall see "Ports to be opened on the firewall" |
Monitor via NC |
If enabled, Network Controller acquires the Network Injector status every 30 seconds. If not enabled, Network Injector continues sniffing and injection operations, but the Network Controller does not check its status. Used when connections to Network Injector are down for any reason once installed at ISP, or for tactical use. |
Log |
Last messages logged. NOTE: Tactical Network Injector log updates depend on the frequency with which the operator enables synchronization. To view log file content see "System logs".
|
RCS8.2 | User's and Installation Guide | © COPYRIGHT 2012