Fadıl

IPsec Security Association Choices

The previous article did not have space to cover some basic choices you have to make when deciding how to run IPsec.

One of the choices is whether you wish to use the Authentication Header (AH) or Encapsulating Security Payload (ESP). Each of these is an IP protocol, just as TCP and UDP are. The protocol codes are 51 and 50, for AH and ESP respectively. Thus IPsec packets will normally have 50 or 51 in the IP protocol field, and there will be an AH or ESP header between the IP header and the payload data.

Failover technique is a network technique by providing two or more connection lines where when one path dies, then the connection still runs supported by another path. This failover technique is quite important when we want a reliable internet network connection.

Tutorial Failover 2 Internet Connection in Mikrotik which I will discuss this time a bit special because it is not like the usual failover. So here I will create an internet network using 2 connections, namely the main connection using Fiber Optic and backup connection with USB Modem. In general, the network topology as follows:

We will share with you a script that we can use to find the solution and the solution that we receive in the Mysql database.

Below is the simple script for monitoring MySQL error logs. You can set the cron jobs as per your need(eg. week, daily, hourly)

#!/bin/bash
SERNAME="techsoftcenter"
SERPUBIP="10.0.0.0"
SERVER="ip-10.0.0.0"
 
MAIL_LIST="[email protected]"
Error_log_location=/var/log
Alert_log_path=/opt/work/dblogs
 
sudo egrep -i 'Error' $Error_log_location/mysqld.log |sort -u > $Alert_log_path/mysqld_ALERTLOG.txt
 
if [ $? -eq 0 ]; then
sudo cat $Error_log_location/mysqld.log > $Alert_log_path/mysqld_archived_`date +%Y-%m-%d-%H:%M:%S`.log
 
if [ $? -eq 0 ]; then
 
sudo cat /dev/null > $Error_log_location/mysqld.log
 
else
 
echo "failed to empty file"
 
fi
 
else
 
echo "something went wrong after log file backup"
 
fi
 
cd /tmp/
cd /opt/work/dblogs/
 
FILE_TYPE="*.txt"
FILE_TYPE1="*.log"
 
find ${FILE_TYPE} -type f -mtime +1 -delete
find ${FILE_TYPE1} -type f -mtime +1 -delete
 
if [ -s "$Alert_log_path/mysqld_ALERTLOG.txt" ] ; then
cat $Alert_log_path/mysqld_ALERTLOG.txt | mutt -s "URGENT -ERROR in Mysql Alert Log File for $SERNAME ($SERPUBIP) at `date` " -- ${MAIL_LIST}
fi

Hope it helped.

/home/nfcuser — user created to drive NetFlow Analyzer, user working directory

configs — router configs for NFA use (it’s not happy with them)
exports — directory, sym link to directory where NFA drops exported CSV files. Don’t delete!
images — directory to dump screen capture GIF/JPEG saves into

/opt/CSCOnfa — Cisco Flow Data Analyzer

check.All — script to check Java, DisplayServer, UtilityServer are running
start.All — script to start DisplayServer, UtilityServer
stop.All — stops themcisco — mojo (ASN.1/SNMP toolset) — not for user use

NFADisplay — NFA Display UI

bin — programs, scripts, also *.class = Java classes

start.Display script — starts NFA Display screen (UI)

helpRuntimeJava

RuntimeJavaWin95

NFAServer — NFA DisplayServer (Display talks to)

AliasDefn — known AS’s, ports, protocols

[not well documented: see perhaps the UsePortText flag in the NFADS.resources file]

bin — programs, scripts

check.DisplayServer — script to check DisplayServer
DisplayServer — program
NFADS.resources — options for DisplayServer, MaxMB, UsePortText
start.DisplayServer — starts just DisplayServer
stop.DisplayServer — stops it

Cache — cached infoexported_files — where exported CSV files go, /home/nfcuser/exports sym link to this

logs — misc log files (server)

RouterGroup — tree file sets and router groups

util — utilities

mgmt_NFC.exp — expect script (is expect installed?).Appears to copy specified collected info to another directory. Looking at the script, from another machine. Probably used behind the scenes to bring in data from another DisplayServer.

NFAUtility — NFA UtilityServer (does all backend dirty work, talks to NFCGW)

bin — scripts, programs, Java classes

check.UtilityServer
start.UtilityServer
stop.UtilityServer

config — config files for UtilityServer

HostPreferences.txt — address à name translation
NFCCC.txt — NetFlow collectors and userid and port
RouterConfig.txt — address, SNMP community, tms/netflow

Conjecture when NFA looks at directory of router configs, it populates this file. (Not very documented?)

data — AS.txt_0, HostAliases.txt — purpose not clear, probably not user fileslogs — log files for UtilityServer

NFAU.log — log file

state — directory to hold .pid file for UtilityServeroriginals — directory of original config/script files (install probably put locations of things into them)

/opt/CSCOnfc — Cisco FlowCollector

Default IP Address

Mimosa backhaul radios can be accessed either via the wired interface or the 2.4 GHz wireless interface (if applicable). An internal bridge connects the two interfaces. Each interface is assigned a default IP address (see table below), and both addresses respond via either interface. The wired interface can either be set manually to a static IP or changed dynamically via DHCP. The wireless interface IP cannot be changed.