Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
TetraWiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Category:NFC
(section)
Category
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Training on NFC Project KT Final. Dated 06 Dec 2024 - Tetra Support Staff - Raviraj== {{#ev:youtube|jH61YI-0PM0|640}} '''Video summary:''' "RAVIRAJ NFC KT FINAL" -- the wrap-up session of the NFC KT series, re-walking the full mail architecture (KSMG -> IMSVA -> Postfix -> MTA -> mailbox for inbound; the reverse for outbound) and the KVM base-machine layout at each site (JTC and Kota each run 3 base machines -- two paired MTA/LDAP/mailbox/proxy nodes plus a dedicated archive/AR machine; Hyderabad separates internet-facing servers, KSMG/IMSVA/Postfix, from intranet servers including a RocketChat VM), before going deeper into day-to-day maintenance procedures than the earlier KT videos. Explains the manual PCS cluster failover procedure step by step: check cluster status to see which node (mailbox1/mailbox2) is currently live and confirm both nodes are online, then standby the active node and un-standby the other to force a controlled switch -- only done in response to a real connectivity/overload issue, not routinely. Covers the DA-domain bypass procedure: if NFC's local email gateway can't reach a particular DA (government) domain, editing Postfix's transport config to comment out that domain's local-gateway routing so mail for it goes via the internet path (IMSVA) instead. Reiterates the with-attachment/without-attachment/internal-only sender group model and the DRBD up-to-date-disk check that only applies at JTC/Kota (not Hyderabad, which is active-active NAS replication). Adds new maintenance detail: daily ClamAV signature updates (main.cvd, bytecode.cvd, daily.cvd) pushed via script to the MTA antivirus scanning layer across all three sites, and confirms SSL certificates and RocketChat are both maintained without downtime as part of routine operations. Functions as a consolidated review/summary of the architecture and procedures already covered piecemeal in the earlier NFC KT videos, rather than introducing an unrelated topic.
Summary:
Please note that all contributions to TetraWiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
TetraWiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)