- CheckMates
- :
- CheckMates Toolbox
- :
- Scripts
- :
- show topology script
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
show topology script
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content



I created simple script to list topology of a gateway/cluster object. Scripts lists a table containing name and type of the interface, virtual IP + mask, cluster members IP + mask, zone, anti-spoofing mode, topology type, and comment.
This is an alternative to a table that is available in the SmartConsole -> GW object -> Network Management. Unfortunately this table lacks zone, anti-spoofing and topology information.
Script uses API (mgmt_cli) and has to be run on management server. You can name the script whatever you want, I use show-topo in the example. Running the script without an argument lists all gateways/clusters managed by management server. Spark gateways (SMB) are not supported, since API lacks support for this.
Version 1.2: Initial Check Mates version
Version 1.3: Removed limit for 50 interfaces
Usage
show-topo
Enjoy
Juraj
I created simple script to list topology of a gateway/cluster object. Scripts lists a table containing name and type of the interface, virtual IP + mask, cluster members IP + mask, zone, anti-spoofing mode, topology type, and comment.
This is an alternative to a table that is available in the SmartConsole -> GW object -> Network Management. Unfortunate
Disclaimer: Check Point does not provide maintenance services or technical or customer support for third party content provided on this Site, including in CheckMates Toolbox. See also our Third Party Software Disclaimer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content


I recommend to add environment checks. Btw, I created similar tools:
- One-liner for Address Spoofing Troubleshooting
- SmartConsole Extension: Show Interface Topology for Gateways
I recommend to add environment checks. Btw, I created similar tools:
- One-liner for Address Spoofing Troubleshooting
- SmartConsole Extension: Show Interface Topology for Gateways
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

I know. The author did not respond yet to my call from the last week. Before that, it will stay here. @JuPo, kind reminder, you need to answer my email, please
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content



- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Hi @JuPo ,
"limit-interfaces 0" in show simple-gateway and show simple-cluster seems not to do what it's intended to.
IMO this should be changed to 500 for simple-cluster and removed for simple-gateway since it does not have this argument at all.
Hi
@JuPo ,
"limit-interfaces 0" in show simple-gateway and show simple-cluster seems not to do what it's intended to.
IMO this should be changed to 500 for simple-cluster and removed for simple-gateway since it does not have this argument at all.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content



Hi @bernhard_m ,
you are right for a "simple-gateway" - it is a bug. For "simple-cluster" I believe that 0 used to be no limit (all interfaces listed).
Hi @bernhard_m ,
you are right for a "simple-gateway" - it is a bug. For "simple-cluster" I believe that 0 used to be no limit (all interfaces listed).
;- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

Hi @JuPo , in my test i had to change this line to "limit-interfaces 500". Otherwise the members interfaces were not included in /tmp/json...
