Enhance TWAMP Light functionality with server/controller functionality (249255)
TWAMP(Two-Way Active Measurement Protocol) Light is a simplified architecture within the TWAMP standard. Its purpose is to measure the round trip IP performance between any two devices within a network that supports the protocol. Now FortiOS operates in more than just the role of responder/reflector.The server/controller functionality has been added.
More information about interface status available from GUI (240285)
The following information is added to the ‘hover’ details for each port on the GUI FortiGate faceplate:
- MAC address
- Tx/Rx bytes
- Tx/Rx packets
- Tx/Rx errors
In addition, optional columns are added to the interface list to allow users to see all of the above information.
Virtual WAN link fixes (255122)
The firmware now has the following fixes or improvements to Virtual WAN links (VWL):
- Better support for dynamic interfaces (PPPoE and DHCP).
- It can remove dynamically added routes, and restore these routes once the interfaces are not members.
- It can count pppoe interface sessions.
- It can generate a proute for a PPPoE interface. In this proute, the gateway is specified, while the outgoingĀ (PPPoE)interface will not set.
- Adjust the route policy for a manual mode VWL service
- Support HTTP monitor by version 1.1, which obsoletes version 1.0’s behavior.
- Apply multiple dst and src new feature for one policy to VWL.
Improvements to CLI usability:
- It hides interfaces that are being used in a policy or a zone
- There is a check when adding an interface to a static route. This check will raise an error if the interface is a member of a VWL.
- Updates a proute, if based on config change, if the associated link-monitor dies.
- Fix some inappropriate messages.
- Revised the minimum value of interval for a link-monitor object. The new value is 1, so it can be compatible with V5.0. When the timeout is 1, and interval is 1.
I’m running FortiOS 5.6.7 on FG-1500D’s. We have virtual wire pairs set up for our VDOM’s that run in transparent mode, with no port channeling. One of the SFP’s is twinax (connecting to a Cisco Firepower) and the other is fiber (going into a Cisco switch). Does that cause issues, or is the Fortigate OK with media not being exactly the same on both ports?
I like to keep things identical for standardization sake. It won’t break anything though.