Problem Statement: SNMP TRAPS/ ALERTS DELIVERY

                   SNMP MIB space ...for RTOS 

                   SNMP ALERTS/TRAPS...UNIX...syslog ...integration  viz. syslog to snmp and vice versa!!
                  

Opportunity A) :   A MIB tree or space (classifiable events and traps)...catering to RTOS ...while given the nature of RTOS as
                classified ...with the advent of WMD's ...integratable with many a RTOS,
                scope and ability to exploit SNMP for such devices ..that fall under the
                scope or scanner of RTOS (say update the embedded OS ...upon discovery of a bug or
                a forgotten to be implemented catch!!)

Opportunity b) :: the following offers the idea scope or possibility or scenario for implementing delivery
                     of traps to multiple hosts (over WLL or email/pager kind of expansion of user-list to
                     mutiple hosts spread across geographical regions ...a potential solution being implementing
                     a smtp/pager based gateway for wrapping the datagrams ...snmp monitoring host or server ...
                     a embedded smpt daemon or authenticated gateway via email-server-host with !!)....given 
                     the context of emergence of wireless lan or wan ...this may not sound logical though!! 

                     ...refer to 'opportunity_XML_RSS_exploitation.txt'

Opportunity c) : SNMP ALERTS/TRAPS...UNIX...syslog ...integration  viz. syslog to snmp and vice versa!!

    
                 deriving from opportunity b) ...on the lines of syslog ...ability to implement various
                 levels or alert mechanism ...based on the priority of trap/alert.

opportunity d): Snmp over blootooth for device monitoring/management


                given the scope of advantages of blootooth over tcp/ip [vulnerabilities spoofing/phising]
                viz. range and broadcast decryptabilities.

Opportunity e): A snmp based product for SAN-fabric's management.

                viz. customize or extend the MIB, OID schema in SNMP context, use device's,hosts that support tcp/ip, San
                     kind of router's ...those that have insider information on the SAN and can report the same on the LAN.
                     thus effectively leverage the opportunity for the SAN-fabric management by simply customizing or
                     leveraging the SNMP architecture


                applying suitable use-case ...modelling and rationalization

                objects or devices that support tcp/ip ...those participating in a SaN fabric ...those offering
                scope ...snmp MIB database , loggable ...raise alarm over a tcp/ip host management.

                

                eg: host's that have their-lun's carved out of a san ...if the boot-disk happen's to be a san based lun.

               

               
            

Note: The above problem statement having been encountered in various scenarios
      and detailed in various 'Proof of concepts' as mentioned in 
      
       http://uk.geocities.com/ravivenkatus/projects.pdf
       http://ravishankarkv.tripod.com/projects.pdf
        ....apply appropriate
      'use-case' modeling, rationalize and arrive at a workable and feasible 
       solution both commercially and techinically viable.
