Skip to content

9‐2.Editing Flow Files

Jump to bottom
Yusuke Ogawa edited this page Apr 14, 2025 · 12 revisions

What you can do with this procedure

  • Edit communication flow settings in a Flow file

Procedure

  • Edit Flow file
  1. Open the exported Flow file in Excel, edit and save
    image

[A]. Auto-numbered, not editable

  • However, if numbers are missing, they can be added manually

[B]. Source device name, required

[C]. Destination device Name, required

[D]. TCP/UDP/ICMP, etc. Manual entry allowed.

[E]. Service name + port name. Manual entry allowed.

[F]. Maximum bandwidth (Mbps)

[G]. Input for manual routing path configuration.

  • If left blank, the automatic routing path will be used.
  • The device name entered will be added to the next hop device. To add multiple devices, separate them with a comma “,” (e.g. 'DEVCE-Y','DEVCE-Z')
  • For example, if source: DEVICE-A, destination: DEVICE-B and you enter 'DEVICE-X', the route will be DEVICE-A->DEVICE-X->DEVICE-B

[H]. Automatic routing path configuration Not editable.

  • Blank means the next hop of the source device is the destination device
  • entered in the master file when the Flow file is reflected in the master file
  • Automatically calculated next hop is shown separated by commas ","

Automatic routing path configuration has the following limitations in ver 2.5.0

  • Routing with L3 instance identification is not possible
  • Pathway weighting is not available
  • Unable to recognize VPN as a route
  • Routing disabling is not possible (e.g., 2NIC servers with no routing)

The handling of data in the Flow file has the following limitations in ver 2.5.0

  • Synchronizing device rename to the master file does not change the device name in the Flow file
  • Even if the NW configuration information in the master file is changed, it is not automatically reflected in the automatic routing of the flow file. If you want to recalculate the automatic routing path based on the updated NW configuration information, you need to perform the procedure to reflect the FLOW file to the master file again.

Author

  • Yusuke Ogawa - Security Architect, Cisco | CCIE#17583

License

SPDX-License-Identifier: Apache-2.0

Copyright 2023 Cisco Systems, Inc. and its affiliates

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Clone this wiki locally