pjhtech Tools
Cross-vendor · Multiple platforms

Network Commands Compared: FortiGate, MikroTik, Junos and Cisco

Quick answer #

Use this table to find a starting command when moving between network operating systems. Match the task first, then check the platform and routing context. The commands inspect related information; their output and scope are not identical. A short interface summary, for example, does not replace physical error counters or optical diagnostics.

Scope: FortiOS 7.4 family, RouterOS v7, Junos OS operational mode and Cisco IOS XE. Basic read-only inspection. Output, availability and routing context vary; not a configuration translator or a claim about every platform.

Interface overview #

PlatformStarting commandOpen next
FortiGate
Read-only
get system interface physical
FortiGate interface, ARP and error counter commands
MikroTik RouterOS v7
Read-only
/interface/print
MikroTik Ethernet Commands: Link, Errors and SFP Status
Junos OS
Read-only
show interfaces terse
Junos Interface Errors and Optical Power Commands
Cisco IOS XE
Read-only
show ip interface brief
Cisco IOS XE Interface Commands: Status, Errors and Drops

These views answer different parts of “what interfaces are present and usable?” Cisco's brief IP view emphasizes IP addressing and status; it does not show all switching or transceiver details. RouterOS running flags also need interpretation in the context of the interface type. Follow the linked reference for counters and hardware-specific observations.

IPv4 routing information #

PlatformStarting commandOpen next
FortiGate
Read-only
get router info routing-table all
FortiGate route lookup and policy route commands
MikroTik RouterOS v7
Read-only
/ip/route/print
MikroTik Route Commands: Routing Tables and Policy Rules
Junos OS
Read-only
show route table inet.0
Junos Route Lookup and VRF Routing Table Commands
Cisco IOS XE
Read-only
show ip route
Cisco IOS XE Route Lookup: Routing Table, VRF and CEF Commands

Do not assume each listing contains only installed forwarding entries. Route state, candidate selection and forwarding-table programming are separate observations, and the platforms expose them differently. Read the flags and table name. A route in the default context does not establish that a client in another VRF or routing instance uses it. FortiGate VDOM selection and policy routing also matter. Narrow a large table to the destination using the detailed reference.

BGP session overview #

PlatformStarting commandOpen next
FortiGate
Read-only
get router info bgp summary
FortiGate BGP commands for neighbors and route verification
MikroTik RouterOS v7
Read-only
/routing/bgp/session/print
MikroTik BGP Commands: Sessions, Prefixes and Routes
Junos OS
Read-only
show bgp summary
Junos BGP Troubleshooting: Neighbors and Advertised Routes
Cisco IOS XE
Read-only
show ip bgp summary
Cisco IOS XE BGP Commands: Neighbors, Prefixes and Advertisements

Check the intended peer, address family, routing context and uptime. Established proves that the BGP session reached its working protocol state; it does not prove that the expected prefix was accepted, selected or forwarded. Continue with received and advertised route evidence, then inspect the routing and forwarding state.

Use the correct CLI family #

Run Junos inspection commands in operational mode and Cisco commands at an EXEC privilege level that permits them. Select the intended FortiGate VDOM. RouterOS examples use absolute menu paths. None of these table entries requests a configuration change, but a full route listing can still be substantial on a busy router.

UniFi and EdgeOS have separate references in the Ubiquiti collection. Neither should inherit a Cisco or generic Linux command merely because the task sounds similar. For packet capture, use the platform's dedicated reference: acceleration, capture point and diagnostic side effects differ too.

Sources

Documentation reviewed: 8 October 2026