ICTThe ICT Unit is dedicated in creating quality and quantity in ICT facilities easy available for low prices. The highest level of virtualisation (and by this the highest level of redundancy) ever been accomplished.
They have made a redundant geographical spread AS-DNS-BGP-STP-XEN-HA-MOS-NDS-NAL-MAS-DM-NAS-MX-IM-IMAP-WIKI-VOIP-VC cluster that can run each application and can store all data. Really a impressive state-of-the-art borders moving and this way new frontiers creating technological platform on which we’re very proud to have it en being able to serve all Indus connected companies with.
By integration of those 18 main layers they have composed the most extended, high capacity capable and low priced ICT environment we offer to the companies we take care of. No shortage of processor power, storage, redundancy, security and type of applications.
Organizational plug and play in the most explicit way that’s what it does, and we’re proud of the functionality and cost saving of it. It make starting a new business in terms of ICT so easy for such a low cost level. Beneath many standard office/business applications (the full OpenOffice Suite) and wide range of telecom services, they support some well-wanted specific applications like AutoCad and others.
Offering the Indus connected companies the best quality and quantity in ICT for the lowest costprice is the motto of the ICT Unit. This platform is so state-of-the-art high-tech that it will be delivered to other big companies in dedicated or ASP model by a special dedicated Indus company for ICT model this market.
For in ICT engineering interested people: herby a little more specific information:
AS-DNS-BGP-STP-XEN-HA-MOS-NDS-NAL-MAS-DM-NAS-MX-IM-IMAP-WIKI-VOIP-VC
Building a redundant, secure and high performance network (even suitable for a secure medical data, travel or telecom environment), that’s based on 18 integrated yet divided functional focused overhead layers, which has the highest level of virtualization and redundancy every provided.
The only items to monitor and provide are updates, IP bandwidths, router backplane capacity, number of processors, number of hard drives and voice terminating contracts. All other functioning and performance facets can be seen as internal facets and are handled by the cluster components itself.
This cluster is so redundant that (self generated) service massages can be fix within a week (or longer, of course they will be fixed within 8 hours, but their failure doesn’t effect the functionality or performance), because the cluster just abandon the malfunctioning part and redirect to other parts (self healing). The cluster overhead is redundant by itself, even geographical, distributed over several servers and locations.
This is the most advanced design in availability and security available at this moment. The Solid Titanic system (yes, this time with iceberg raders, yes this time with front engines, and yes, without the arrogance of being unbeatable).
Many redundant system builders and suppliers ‘wants to walk a day in the kitchen’ with our team of network and system engineers lead by Paul R. Daemen. The online configuration environment with graphical interfaces and intensive use of XML is made by our team of programmers lead by Dennis J. Knol.
AS. The AS (autonomous system) is the name of an independent part of the internet, providing x (multiple) times redundancy and more direct routes (by less external hobs, hobs are hubs in the routes, hubs has of course more operational risks than lines). An AS has several both physical and vertical incoming routes from the internet to it. Line breaks or line routers issues doesn’t effect the function of an AS. AS is taking care of multiple redundancy in incoming internet traffic. There is a second AS configuration for secondary DNS, secondary NDS, secondary NAL and secondary MX use. So no single point of failure on incoming traffic and internet presence of any service. Of course AS has a distributed, multi homed, multi geographical location structure, build-in the AS design as part of the Internet.
DNS. The domain name system. Providing four times redundancy. The master is within the own AS. The three slaves are pulling the data from the master and are located in third party AS’es. The servers are not only geographical spread, but also AS spread and top level spread (each has a domain in an other top level). Making sure that a domain name always can be resolved. Short caching values so that eventual changes will be applied in seconds. So no single point of failure in the DNS. Of course DNS has a distributed, multi homed, multi geographical location structure. Each DNS system has highest level of general and zone security settings, preventing DOS (Denial Of Services) attacks and un-mentioned use of services and zone information.
BGP. The Border Ground Protocol. Taking care of redundant connection of outgoing internet traffic based on connection quality and bandwidth prices. BGP is taking care of redundancy in outgoing traffic and quality and price control (peering before transit). So no single point of failure to any destination.
STP. The spanning three protocol provides router redundancy. In our network a four times redundancy. Malfunctioning of a router or a fiber line will not effect the functionality nor performance of the network, because they check each other continuously plenary and all trust one other plenary only when checks results are clear. So no single point of failure in own routing hubs.
XEN. XEN is the lowest overhead (closes to the processors) there is possible. XEN is taking care checking processors and delivering only the well functioning ones to the higher level of XEN, which provides OS space. Any OS space. XEN is the controlling layer between hardware en OS’es. XEN provides on each server full virtualisation and provides on a range of servers server hardware redundancy in a fail proof distributed way (no single point of failure). Of course XEN has a distributed, multi homed, multi geographical location structure.
HA. XEN uses HA (High Availability) technology. It’s a socialistic monitoring layer of server quality. Sending a poison pill to any malfunctioning server. Providing direct replacement with same IP numbers on other servers. XEN request than NAL in a time frame of seconds for installation of all requested services.
MOS. XEN is capable of MOS (Multi Operation Systems). Any OS can run under XEN. XEN runs OS independent, just providing OS’es facilities to run complete virtual.
NDS. NDS (Novell Directory Service) is the authentication (who are you) and authorisation (these are your rights) layer. Made by Novell. The new name is E-Directory. The only company who really know what networks need and invent solutions. All other directory systems (like Microsoft Active Directory) are just bad copies of NAL. Of course NDS has a distributed, multi homed, multi geographical location structure.
NAL. NAL (Novell Application Launching) is the services/application installing layer. Capable of feeding a working installation of any OS or service or application in seconds. Of course NAL has a distributed, multi homed, multi geographical location structure.
MAS. Multi Application System. The cluster is capable of (by NAL) running multi applications under each desired OS. Distributed all over the cluster with processor load as automatic balancer.
DM. Data Mirroring. Because storage is based on I-SCSI (SCSI through IP), the routers duplicated each storage packet to two different geographical locations, making assure that even a fire or complete building lost doesn’t damage any data.
NAS. Network Attached Storage. Double redundant in present by DM. Based on the I-SCSI (SCSI through IP). Handling data storage in secure and disk efficient ways. Of course NAS has a distributed, multi homed, multi geographical location structure.
MX. Secondary MX settings in the DNS zone of each domain takes care of storage of mail when primary (which is already multiple redundant in the above mentioned ways) will be stored and automatically delivered after primary MX is available.
IM. Instant Messaging. No change of doing business these days without it. Only inter-company or MSN/Yahoo connected. Of course IM has a distributed, multi homed, multi geographical location structure.
IMAP. Email on database concept. Local independent email. Of course IMAP has a distributed, multi homed, multi geographical location structure and data is stored in NAS.
WIKI. Online knowledge sharing. Of course WIKI has a distributed, multi homed, multi geographical location structure and data is stored in NAS.
SMS. Short Massage Services. Text over mobile. The system handles it, connects it (after verification) to a mobile phone number, taking care of delivery worldwide. Of course SMS has a distributed, multi homed, multi geographical location structure and data is stored in NAS.
VOIP. Voice Over IP. A complete phone, voice conference, call storage system. Connected by a voice traffic control program to all phone connections worldwide the most efficient way. Of course VOIP has a distributed, multi homed, multi geographical location structure and conference call recordings can be stored in NAS.
VC. Video Conferencing. A client/server based environment. Operating in each internet browser. With several additional services. Like invitations, meeting planners, call storage, etc. Of course VC has a distributed, multi homed, multi geographical location structure and video meetings can be stored in NAS.
|
| Relevant documents |
 |
|
|
|
|
