Sponsored Content
Special Forums IP Networking Best tool to monitor VPN IPSEC Tunneling Post 302930348 by DGPickett on Friday 2nd of January 2015 01:19:25 PM
Old 01-02-2015
You mean the VPN is disconnecting even though connectivity seems fine?
 

9 More Discussions You Might Find Interesting

1. Cybersecurity

IPSec - VPN using shared key

Hello! I have some trouble trying to configure a VPN with two gateways. One of them uses IPSec with a single key, 256bits length, specified in /etc/ipsec.secrets. As FreeSwan manual page says, if i put esp=3des-md5-96, will be used a "64bit IV key (internally generated), a 192bit 3des ekey and a... (3 Replies)
Discussion started by: eNTer
3 Replies

2. UNIX for Dummies Questions & Answers

Tool to monitor user activity

Hello, Does any one knows any tools or method to monitor users all activities on Solaris 8, including command and its result. Similar to 'script' ??? Thanks nana (3 Replies)
Discussion started by: nana
3 Replies

3. UNIX for Advanced & Expert Users

Tunneling

Hello, I am within a LAN system and I need to be able to tunnel out (and recv UDP) packets. Currently the router automatically drops UDP packets. My PC cant see the outside world, nor ping, but it can connect via SSH to a server on the "edge" of the network which can see everything. I... (2 Replies)
Discussion started by: ErNci
2 Replies

4. Solaris

ssh tunneling

Hi, I have tried the following: on PC1 (win xp) I have created ssh connection with port forwarding (local 8888 to remote 8888) to server1. >From server1 I have created another ssh connection with port forwarding to server2(local 8888 to remote 1521). When I try to connect to oracle... (3 Replies)
Discussion started by: goran00
3 Replies

5. UNIX for Advanced & Expert Users

tool to monitor throughput

Was wonder if there was a tool or program I could run to measure throughput on our CentoS 4.x server. Our current dedicated host provider is charging us by how much throughput we are using and I just want to see if their numbers add up to whatever I get using a throughput tool of some kind. ... (6 Replies)
Discussion started by: mcraul
6 Replies

6. AIX

Tool to monitor the performance of the system ..

Dear experts , Pls advice for any good Tool to monitor the CPU and performance of AIX the system .. to keep monitoring to show me the utilization of that system .. (12 Replies)
Discussion started by: Mr.AIX
12 Replies

7. IP Networking

IPSec VPN Routing

Hello, I'm trying to setup a gateway VPN between two routers across an unsecured network between two local networks. The routers are both linux and I'm using the ipsec tools, racoon and setkey. So far hosts from either local net can successfully ping hosts on the other local net without issue. ... (0 Replies)
Discussion started by: salukibob
0 Replies

8. IP Networking

VPN IPSec Openswan

Hi all, I have installed Openswan and configured IPSec and works perfect, but for some unknown reasons it stop working. I see that the tunnels are up and established. The route to the destination are added. Everything by the book seems to be ok. But somehow when i start to ping the other side (... (4 Replies)
Discussion started by: ivancd
4 Replies

9. IP Networking

IPSec Openswan Site to Site VPN - Big Pain

Hi @all, I try to connect 2 LANs with IPSec/Openswan LAN 1: 192.168.0.0/24 LAN 2: 192.168.1.0/24 This is my Config: conn HomeVPN # # Left security gateway, subnet behind it, nexthop toward right. left=192.168.1.29 ... (1 Reply)
Discussion started by: bahnhasser83
1 Replies
cmcheckconf(1m) 														   cmcheckconf(1m)

NAME
cmcheckconf - check high availability cluster configuration and/or package configuration files SYNOPSIS
cmcheckconf [-v] [[-k|-K] -C cluster_ascii_file] [[-p pkg_reference_file] | [-P pkg_ascii_file]...] DESCRIPTION
cmcheckconf verifies the cluster configuration as specified by the cluster_ascii_file and/or the package configuration files specified by each pkg_ascii_file in the command. If the cluster has already been configured previously, the cmcheckconf command will compare the con- figuration in the cluster_ascii_file against the previously configuration information stored in the binary configuration file and validates the changes. The same rules apply to the pkg_ascii_file. It is not necessary to halt either the cluster or any of the packages to run the cmcheckconf command. Only a superuser, whose effective user ID is zero (see id(1) and su(1)), can verify the configuration. cmcheckconf verifies any configured external script program in each pkg_ascii_file for the package run and halt function by calling it with a "validate" parameter. A non-zero return value from any external script program will cause the command to fail. If the cluster_ascii_file specifies a quorum server as the cluster tie-breaker service, the quorum server must be running and all nodes in the cluster configuration must be authorized to access it. If more than one IP address is specified for the quorum server, the quorum server must be reachable from all configured nodes through all the IP addresses. Otherwise the cmcheckconf command will fail. If the cluster_ascii_file specifies the lock lun devices as the cluster tie breaking service, all nodes must be accessing the same physical device. The lock lun device file must be a block device file. The cluster must be down before you can modify a cluster tie-breaking ser- vice. Options cmcheckconf supports the following options: -v Verbose output will be displayed. -k Using the -k option means that cmcheckconf only checks disk connectivity to the LVM volume group that are identified in the ASCII file. This option does not exist on Linux. Omitting the -k option (the default behavior) means that cmcheckconf tests the connectivity of all LVM volume groups on all the cluster nodes. Using -k can result in significantly faster operation of the command. -k must be used with -C and can not be used with -K -K Using the -K option means that cmcheckconf only checks disk connectivity for cluster lock volume groups. For all other LVM volume groups no connectivity will be checked. This option does not exist on Linux. Omitting the -K option (the default behavior) means that cmcheckconf tests the connectivity of all LVM volume groups on all the cluster nodes. Using -K can result in significantly faster operation of the command. -K can be used only when cluster is already configured and is used with -C -K can not be used with -k. -C cluster_ascii_file Name of the cluster ASCII file to use. This file can be created by either the cmquerycl command or cmgetconf command. See cmquerycl(1m) or cmgetconf(1m). This is a required parameter if the cluster has never been configured before. If not specified, the local cluster configuration is used. -P pkg_ascii_file... Name of the package configuration file(s) to use. A package configuration template file can be created by using the cmmakepkg command and must be customized to include specific information for the package. See cmmakepkg(1m). A configu- ration file for an existing package can be generated by using the cmgetconf command. See cmgetconf(1m). Once a package configuration file is generated from the existing configuration using cmgetconf, it can be modified to reflect the desired changes for that package. The package configuration file will be scanned for the purpose of validation. -p pkg_reference_file Name of the file containing a list of package configuration file(s) to be used. This file may be necessary if the number of pkg_ascii_file names given with multiple -P options do not fit on the command line. This option cannot be used with the -P option. RETURN VALUE
Upon completion, cmcheckconf returns one of the following values: 0 Successful completion. 1 Command failed. EXAMPLES
The high availability environment contains an ASCII cluster configuration file, and two packages, pkg1 and pkg2, specified in ASCII files pkg1.config and pkg1.config. To verify the cluster configuration and package files, do the following: cmcheckconf -C clusterA.config -P pkg1.config -P pkg2.config To verify the cluster configuration while restricting the connectivity check to the volume groups specified in the clusterA.config file, cmcheckconf -k -C clusterA.config -P pkg1.config -P pkg2.config To verify the cluster configuration while restricting the connectivity check to the cluster lock volume groups, cmcheckconf -K -C clusterA.config -P pkg1.config -P pkg2.config To specify a long list of package configuration files do the following: cmcheckconf -C clusterA.config -p myfile where myfile contains: pkg1.config pkg2.config pkg3.config The cluster is up and running, with both packages pkg1, pkg2 running as well. The package configuration file pkg1.config contains the changes to the package pkg1. To verify the package configuration changes made for pkg1, do the following: cmcheckconf -P pkg1.config AUTHOR
cmcheckconf was developed by HP. SEE ALSO
cmapplyconf(1m), cmdeleteconf(1m), cmgetconf(1m), cmmakepkg(1m), cmquerycl(1m). Requires Optional Serviceguard Software cmcheckconf(1m)
All times are GMT -4. The time now is 10:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy