Page tree
Skip to end of metadata
Go to start of metadata

FireMon has released Lumeta Enterprise Edition 3.3.5.1! This software release provides enhanced support for IPv6 host acquisition, and is recommended for Lumeta Enterprise Edition customers for whom IPv6 discovery is critically important.

Lumeta Enterprise Edition 3.3.5.1
Upgrade PathUser Center DownloadUpgrade MethodUpgrade Procedure

FROM release

TO release . . .

About the Package & Validation CodeGUI

CLI


Lumeta Enterprise Command Center 3.3.5

Lumeta Enterprise
Command Center 3.3.5.1

Available now on the Downloads page of the FireMon User Center

This update package upgrades the Lumeta
Enterprise Command Center, Enterprise Scout, and Portal. FireMon recommends upgrading all of these to version 3.3.5.1

This 3.3.5.1 package is compatible with
Lumeta Cloud Scout 1.1 for AWS and Azure

(tick)(tick)


Follow the Upgrading to Lumeta Enterprise Edition 3.3.5x upgrade procedure.




Lumeta Enterprise Scout
3.3.5

Lumeta Enterprise
Scout
3.3.5.1
(tick)(tick)

Lumeta Enterprise Portal
3.3.5

Lumeta Enterprise
Portal 3.3.5.1
(error)(tick)

Forward DNS Lookups

Now a device on your network with an IPv4 address and hostname can report its related IPv6 address to Lumeta (and vice versa). Two devices sharing the same name––one of them with an IPv4 address and the other with IPv6––can both be reported out by Lumeta. You can use the checkboxes to specify which related hosts you want to retrieve (i.e., all related, IPv4-related, IPv6-related, or none). This enables Lumeta to discover and profile more IPv6 hosts.

To support this host acquisition capability, we've added a new option to the Settings > Zones > DNS tab. This "Use host names to find related IP addresses" checkbox will enable you to target a host whose name is associated with multiple IPv4 and IPv6 records and use the discovered host name to retrieve any IPv4 or IPv6 addresses associated with that name.

If, for example, you were to target the zone collector to 172.18.1.1  and choose "find related" in the DNS configuration, shown below, and use internal DNS server 172.16.53.5, the zone would find not only 172.18.1.1 but also 2600:802:460:425::1 and 172.18.1.254.

Results as shown in the DNS and Routing Indices dashboard. Notice that the new feature reports IPv6 addresses in addition to the related IPv4 addresses.



Results as shown in the All Devices report:



To control the "Use host name to find related IP addresses" checkbox from your Lumeta Command Center CLI, use the commands:

TO . . .RUN the CLI command . . .EXAMPLE
Find related IPs (check the box)


collector dns collectorname forwardqueries { true | false }

collector dns LUM-980 DNS forwardqueries true
Return to default (clear the box)collector dns LUM-980 DNS forwardqueries false
Show configuration statuscollector list name collectorname [ dns ]collector list name LUM-980 DNS 172.16.53.5

BGP IPv6 only interface, router ID

Lumeta requires a 32-bit router ID to establish a connection to a BGP peer and uses the scanning/collector interface's current IPv4 interface to serve in that capacity. This release's enhancement is to provide a near-term process for when the current interface  is not an IPv4 but an IPv6 address.

  1. Use the first available IPv4 address of the scanning interface as the BGP Router ID.  
  2. If there isn't one (like on an IPv6-only interface), use the discoveryagent.bgpRouterId property to make the connection  
  3. Otherwise, use 1.1.1.1

Backward Compatibility

Older Enterprise Scouts are not compatible with 3.3.5.1 Command Centers and must be upgraded to the 3.3.5.1 version. 


  • No labels