Print Download PDF Send Feedback

Previous

Next

vsx_util view_vs_conf

Description

Compares the configuration of all Virtual Devices on the Management Server and the actual configuration on the VSX Gateway or VSX Cluster Members.

Syntax

vsx_util view_vs_conf

Required Input

Example

Expert@MGMT:0]# vsx_util show_interfaces

Enter Security Management Server/main Domain Management Server IP address (Hit 'ENTER' for 'localhost'): 172.16.16.240

Enter Administrator Name: admin

Enter Administrator Password:

 

Select VSX gateway/cluster object name:

1) VSX_Cluster_1

2) VSX_Cluster_2

3) VSX_GW

4) VSX_GW_2

Select: 1

 

Select Virtual Device object name:

1) VS1

2) VS2

3) VS3

4) VSX_Cluster

Select: 1

 

Type: Virtual System

 

Interfaces configuration table:

 

+---------------------------------------------------+-----+-------------------+

|Interfaces |Mgmt |VSX GW(s) |

+----------+----------------------------------------+-----+---------+---------+

|Name |IP / Mask length | |mem 1 |mem2 |

+----------+----------------------------------------+-----+---------+---------+

|eth2 |v4 10.0.0.0/24 v6 2001:db8::abc::1/64 | V | V | V |

|eth3 |v4 10.10.10.10/24 v6 2001:db8::3121/64 | V | V | V |

+----------+----------------------------------------+-----+---------+---------+

 

 

Interfaces Table Legend:

 

V - Interface exists on the gateway and matches management information (if defined on the management).

- - Interface does not exist on the gateway.

N/A - Fetching Virtual Device configuration from the gateway failed.

!IP - Interface exists on the gateway, but there is an IP address mismatch.

!MASK - Interface exists on the gateway, but there is a Net Mask mismatch.

 

Routing table:

 

+----------------------------------------------------------+-----+-------------+

|Ipv4 Routes |Mgmt |VSX GW(s) |

+--------------------------+--------------------+----------+-----+------+------+

|Destination / Mask Length |Gateway             |Interface |     |mem1 |mem2 |

+--------------------------+--------------------+----------+-----+------+------+

|2.2.2.0/24                |                    |eth2      |  V  |  V   |  V   |

|3.3.3.0/24                |                    |eth3      |  V  |  V   |  V   |

+--------------------------+--------------------+----------+-----+------+------+

+--------------------------+--------------------+----------+-----+------+------+

 

+----------------------------------------------------------+-----+-------------+

|Ipv6 Routes                                               |Mgmt |VSX GW(s)    |

+--------------------------+--------------------+----------+-----+------+------+

|Destination / Mask Length |Gateway             |Interface |     |mem1 |mem2 |

+--------------------------+--------------------+----------+-----+------+------+

|2001:db8::abc::/64        |                    |eth2      |  V  | !NH  | !NH  |

|2001:db8:0a::/64          |                    |eth3      |  V  | !NH  | !NH  |

+--------------------------+--------------------+----------+-----+------+------+

|2001:db8::1ffe:0:0:0/112  |                    |eth2      |  -  |  V   |  V   |

|2001:db8::fd9a:0:1:0/112  |                    |eth3      |  -  |  V   |  V   |

+--------------------------+--------------------+----------+-----+------+------+

 

Routing Table Legend:

 

V - Route exists on the gateway and matches management information (if defined on the management).

- - Route does not exist on the gateway.

N/A - Fetching Virtual Device configuration from the gateway failed.

!NH - Route exists on the gateway, but there is a Next Hop mismatch.

 

Note: Routes can be created automatically on the gateways by the Operating System.

Therefore, routes that appear on all gateways, but are not defined on the management,

do not necessarily indicate a problem.

 

Logging details are available at /opt/CPsuite-R80.20/fw1/log/vsx_util_20181025_18_11.log

 

[Expert@MGMT:0]#