Hi Vivekananthan, I guess here ESB acts as the SNMP Manager? Also can you explain how the communications happens, protocol details, are you planning to use any libs etc,
Perhaps a flow diagram will help. On Mon, Mar 6, 2017 at 10:01 PM, Vivekananthan Sivanayagam < vivekanant...@wso2.com> wrote: > > > H > > i All, > > Currently, I am implementing the SNMP connector which used to monitor and > configure the network components such as servers, routers, switches or > printers through the WSO2 ESB and supports SNMP Version 2. > > *About SNMP:* > > Simple Network Management Protocol (SNMP) is an Internet-standard protocol > for managing devices on IP networks. Using SNMP, the Network operators can > be able to manage their network elements, identify the problem and can > configure the remote system. > > Let us take a simple example to understand SNMP, consider a Network with > four printers, and we need to shut down the Printer 1(P1), using a > management protocol like SNMP we can easily figure out the right device and > do shut down. For that, we can succeed with SNMPSet operation which is used > to set/write values in the Managed Device. Basically, it is used to > configure Network Elements. > > There are two major things we need to get to know when talking about SNMP. > > *SNMP Manager:* A manager or management system is a separate entity > that is responsible for communicating with the SNMP agent implemented > network devices. > > *SNMP Agent:* The agent is a program that is packaged within the > network element. Enabling the agent allows it to collect the management > information database from the device locally and makes it available to the > SNMP manager. > > *Note*: If we assign the SNMP Manager to write permission for the SNMP > Agent, the SNMP Manager can also send a configuration request to the Agent > (using a Set message) to change a local parameter. > > *Understanding the Management Information Base (MIB)* > > When an SNMPManager requests information from an SNMPAgent, the SNMP Agent > retrieves the current value of the requested information from the > Management Information Base (MIB). The MIB defines the managed objects that > an SNMP manager monitors (or sometimes configures) on an SNMP agent. > > *SNMP Connector Operation:* > > snmpGet: The GET operation is a request sent by the manager to the managed > device. It is performed to retrieve one or more values from the managed > device. > SnmpGetBulk: The GETBULK operation is used to retrieve voluminous data > from large MIB table. > snmpGetNext : > > The > GET NEXT operation retrieves the value of the next OID in the MIB tree. > snmpSet: This operation is used by the managers to modify or assign the > value of the Managed device. > > > Thanks, > Vivek. > > Vivekananthan Sivanayagam > Associate Software Engineer | WSO2 > E:vivekanant...@wso2.com > M:+94752786138 <075%20278%206138> > -- Best Regards, Malaka Silva Associate Director / Architect M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware https://wso2.com/signature http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> https://store.wso2.com/store/ Don't make Trees rare, we should keep them with care
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
