Cisco Cisco Firepower Management Center 4000 Release Notes
Version 5.2.0.3
Sourcefire 3D System Release Notes
37
Features Introduced in Previous Versions
You can configure NAT policies in different ways to manage specific network
needs:
•
to expose an internal server to an external network
•
to allow an internal host or server to connect to an external application
•
to hide private network addresses from an external network by using a
block of IP addresses
•
to hide private network addresses from an external network using a limited
block of IP addresses and port translation
In previous versions, you could configure NAT through device-based NAT rules.
Policy-based NAT replaces that functionality. When you update managed devices
to Version 5.2, the device-based NAT rules for that device (formerly configured
under Devices > Device Management > Edit) become a NAT policy (under the Devices
> NAT tab on the Defense Center) with equivalent rules.
You can use policy-based NAT on Series 3 managed devices with a Control
You can use policy-based NAT on Series 3 managed devices with a Control
license enabled.
Clustered Stacking
In addition to the ability to create clustered configurations of managed devices,
you can now establish redundancy of networking functionality and configuration
data between two identically configured peer device stacks. Just as with paired
individual devices in a cluster, clustered stacks provide a backup option if one
stack fails. As in the existing clustering feature, all devices in the configuration
must have identical licenses and must have Control licenses. When you register
or unregister any device in a clustered stack with a Defense Center, the entire
clustered stack is registered or unregistered as a group.
All Series 3 devices that support stacking are supported for this feature. However,
All Series 3 devices that support stacking are supported for this feature. However,
stacked 3D9900 devices are not supported.
Drop BPDUs Support
The drop Bridge Protocol Data Units (BPDUs) configuration added in Version 5.2
allows you to set up an inline configuration that operates over a single physical
link. You can now configure a virtual switch with two logical interfaces; each
interface must have a different configured VLAN tag. Additionally, on a third-party
switch or other supported device, you must configure two VLANs and two logical
interfaces; each interface must be in a different VLAN but configured on the same
physical port.